SPRUIW9C October 2021 – March 2024 TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-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 | Package 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-19 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 |
---|---|
0x3FB8B9 – 0x3FB8C0 | In Wait Boot Mode |
0x3FC7D0 – 0x3FC7D8 | In SCI Boot waiting on autobaud lock |
0x3FEDFE – 0x3FEEC8 | In NMI Handler |
0x3FEEC9 – 0x3FEEF9 | In ITRAP ISR |
0x3FCB96 - 0x3FCB9A | In Parallel boot waiting for control signal |