SPRADS5 December   2025 AM625 , AM62A7 , AM62D-Q1 , AM62P , AM6442

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Terminology
  6. 3Understanding Boot Mode and Flash Compatibility
  7. 4Flash Integration and SysConfig Setup
    1. 4.1 FLASH Parameters
      1. 4.1.1 Recommended Approach
    2. 4.2 OSPI Parameters
  8. 5Common Bring-up Issues and Debugging
    1. 5.1 Boot Failure
    2. 5.2 Known Errata
    3. 5.3 Flash Initialization Failure
      1. 5.3.1 FLASH and OSPI SysConfig Values
      2. 5.3.2 Flash Device and Manufacture ID Read Failure
      3. 5.3.3 PHY Failure
    4. 5.4 Flash Read Failure
    5. 5.5 Flash Program Failure
  9. 6Checklist for Requesting OSPI and FLASH Support
  10. 7Summary
  11. 8References

5.4 Flash Read Failure

Flash read failures happen in some cases. They are as follows:

  1. A certain address range is used to map the flash contents when the OSPI controller is in DAC state. The available address range is shown in Figure 5-2. By default, 0x60000000 is selected. read failures happen when the MPU Region 0x60000000 is marked as cached. This is the region used for Direct Memory Mapping of the Flash. In software, this is achieved by setting the 7th bit, DAC bit, in register 0xFC40000 to 1. As a result, 0x60000000 does not need to be marked as "Cached".
  2. Read command set in the SysConfig is incorrect for the configured protocol. Some flashes have different read command for 3 byte and 4 bytes addressing.
  3. Suppose the data on the flash is 00h 01h 02h 03h… and the read values in the buffer are 01h 02h 03h 04h…. This points to section 5.3.1 where the dummy clocks for reading is off by a value of 1.
  4. DMA related issues include, data not being read correctly because the read buffer is not cache aligned.
FSS Memory Regions Figure 5-2 FSS Memory Regions