SLUAAP5 july   2023 UCD3138 , UCD3138064 , UCD3138064A , UCD3138128 , UCD3138128A , UCD3138A , UCD3138A64

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Why Lockup Can Occur
  5. 2Reasons for Lockup
    1. 2.1 Wrong Code in the load.asm
    2. 2.2 Misoperation with TI GUI
    3. 2.3 zero_out_integrity_word Function Fails
    4. 2.4 PMBus Communication Fails
    5. 2.5 Unexpected Occurrences
  6. 3How to Avoid a Lockup
  7. 4Unlock with JTAG
    1. 4.1 Enable JTAG Functionality
    2. 4.2 New Target Configuration in CCS
    3. 4.3 Clear the Flash
  8. 5Summary
  9. 6References

2.2 Misoperation with TI GUI

If there is no bootloader in the application, but the Boot support is selected, a valid checksum at address 0x7f4 (or 0x7f8) can exist for the boot. Since there is no bootloader used, the checksum at 0x7f4 (or 0x7f8) cannot be cleared and can cause a lockup.

GUID-20230602-SS0I-PRJV-2WNL-7N8VVKFLZNR6-low.png Figure 2-1 Boot Support Selection