SPRUJ53B April 2024 – September 2024 TMS320F28P550SJ , TMS320F28P559SJ-Q1
The wait mode puts the CPU in a loop in the boot ROM code and does not branch to the user application code. The device can enter wait boot mode either through manually being set or because of some issue during boot up. Using wait boot mode is recommended when using a debugger to avoid any JTAG issues. There is an ESTOP provided for debugging during Wait boot.
Option | BOOTDEFx Value | Watchdog Status | Device Supported |
---|---|---|---|
0 (default) | 0x04 | Enabled | All |
1 | 0x24 | Disabled | All |
During boot ROM execution, there are situations where the CPU can enter a wait loop in the code. This state can occur for a variety of reasons. Table 4-20 details the address ranges that the CPU PC register value falls between if the CPU has entered one of these instances.
Following are the actions for entering wait boot mode:
Address Range | Description |
---|---|
0x3F B8B9-0x3F B8C0 | In Wait Boot Mode |
0x3F C7D0-0x3F C7D8 | In SCI Boot waiting on autobaud lock |
0x3F EDFE-0x3F EEC8 | In NMI Handler |
0x3F EEC9-0x3F EEF9 | In ITRAP ISR |
0x3F CB96-0x3F CB9A | In Parallel boot waiting for control signal |