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

PHY Failure

There are two types of failure with respect to PHY tuning. When Enable PHY Mode is checked, then these two failures can be encountered. Before starting this, learn about OSPI PHY Tuning and PHY Tuning Attack Vector.

The first being "PHY enabling failed!!! Continuing without PHY..." and second will be failure to compute the OTP (Optimal Tuning Point). The first one occurs, when the attack vector is flashed but not read correctly. So, this in turn points back to sections 5.3.1 and 5.3.2. The second one occurs when the PHY Tuning algorithm returns failure. To debug this, the following steps can be considered:

  1. By default, in flash_nor_ospi,c file, OSPI_phyTuneDDR is called. If the protocol used is configured in STR, then the function OSPI_phyTuneSDR must be called.
  2. To debug PHY tuning failure, TI recommends generating the PHY tuning graph. Please refer the FAQ here. Upon PHY failure, the graph can be used as a reference to see where the OTP point is marked.