This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F280039-Q1: Why WDOVERRIDE is not work in two project

Part Number: TMS320F280039-Q1


Tool/software:

Hi team,

I ask this for my customer.

In my customer's project, it has application project and bootloader project. Because of the Functional safety requirement, it need to keep the Watchdog enable when bootloader jump to application. 

So they use the  SysCtl_clearWatchdogOverride();  before bootloader jump to application, and then use below code jump to application. code will jump to 0x87000 and then jump to codestart and then jump to application main function, it isn't have reset in this process.

But in the codestart, it will disable the watchdog, so when code stop in application main(); function, they find the watchdog is disabled. that means the SysCtl_clearWatchdogOverride(); don't prevent the watchdog configuration register from being modified

Then they revise the code and the watchdog will not be disable.

Then they do other experiment, they use SysCtl_clearWatchdogOverride(); in one project, the WDOVERRIDE is work, it prevents the watchdog configuration register from being modified

So they want to check why is not work when code jump from bootloader project to application code, they don't do reset in this process.

BRs

Shuqing