SDAA516 August   2026 AM620-Q1 , AM623 , AM625-Q1 , AM62A1-Q1 , AM62A3-Q1 , AM62A7-Q1 , AM62D-Q1 , AM62L , AM62P-Q1 , DRA821U-Q1 , DRA829V-Q1 , TDA4AEN-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4APE-Q1 , TDA4VE-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VP-Q1 , TDA4VPE-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Purpose
    2. 1.2 Scope
  5. 2Detailed Description
    1. 2.1 AM62Ax QSPI Boot Overview
      1. 2.1.1 Boot Preconditions
      2. 2.1.2 Boot ROM Read Sequence
    2. 2.2 Flash Addressing Architecture
      1. 2.2.1 3-Byte Addressing Mode
      2. 2.2.2 4-Byte Addressing Mode
      3. 2.2.3 State Retention Behavior
    3. 2.3 Boot Compatibility Considerations
      1. 2.3.1 Boot ROM Expectations
      2. 2.3.2 Addressing-Mode Mismatch Mechanism
      3. 2.3.3 Start-Up Impact
    4. 2.4 Example Start-Up Investigation
      1. 2.4.1 External Failure Symptoms
      2. 2.4.2 Boot ROM Log Analysis
      3. 2.4.3 Memory Verification Using CCS
      4. 2.4.4 Image Comparison
      5. 2.4.5 QSPI Bus Analysis
      6. 2.4.6 Root Cause Confirmation
    5. 2.5 Debug Methodology
    6. 2.6 Mitigation and Design Recommendations
      1. 2.6.1 Preferred Solution: Flash Reset Synchronization
      2. 2.6.2 Alternative Solution: Driver-Level Mitigation
      3. 2.6.3 Applicability of the 0x6C Mitigation
      4. 2.6.4 Design Constraints for Large-Capacity Flash Applications
  6. 3Summary
  7. 4References

2.5 Debug Methodology

The following methodology is recommended whenever a start-up failure occurs during the Boot ROM stage.

  1. Step 1: Capture Boot ROM Logs
    • Determine whether the device enters a backup boot mode and collect Boot ROM logs using the appropriate TI utility.
  2. Step 2: Verify Authentication Errors
    • Determine whether the reported authentication failure is caused by a certificate issue or corrupted image data.
  3. Step 3: Inspect Boot ROM-Loaded Memory
    • Use CCS to inspect memory populated by the Boot ROM.
  4. Step 4: Compare Against the Original tiboot3.bin
    • Verify that the Boot ROM-loaded image exactly matches the programmed image.
  5. Step 5: Analyze QSPI Bus Timing
    • Capture QSPI transactions using a logic analyzer and verify protocol timing.
  6. Step 6: Verify Flash Addressing Configuration
    • Confirm the addressing mode retained by the Flash device after reset.