• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 33 subscribers
  • Views 627 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP432E401Y: How to recover from watchdog resetting too quickly

Mike_d
Expert 1005 points
Part Number: MSP432E401Y


Hi,

I used the example from driverlib to test the watchdog and now the system is resetting too quickly to reprogram the device.  How do we recover from this?

Here's the example code.  It's resetting somewhere around every 250ms which I find odd based on the load value.  The CPU is running at 120MHz.

//
// Enable the Watchdog 0 peripheral
//
SysCtlPeripheralEnable(SYSCTL_PERIPH_WDOG0);
//
// Wait for the Watchdog 0 module to be ready.
//
while(!SysCtlPeripheralReady(SYSCTL_PERIPH_WDOG0))
{
}
//
// Check to see if the registers are locked, and if so, unlock them.
//
if(WatchdogLockState(WATCHDOG0_BASE) == true)
{
    WatchdogUnlock(WATCHDOG0_BASE);
}
//
// Initialize the watchdog timer.
//
WatchdogReloadSet(WATCHDOG0_BASE, 0xFEEFEE);
//
// Enable the reset.
//
WatchdogResetEnable(WATCHDOG0_BASE);
//
// Enable the watchdog timer.
//
WatchdogEnable(WATCHDOG0_BASE);
//
// Wait for the reset to occur.
//
while(1)
{
}

Regards,

-Mike

  • +1
    Guru 92251 points
    Mike_d said:
    How do we recover from this?

    See section 5.3 Executing Unlock Sequence in https://www.ti.com/lit/slaa777 for how to factory reset a MSP432E device.

    Since the procedure holds the device in reset until the unlock sequence has been executed, which erases the flash, EEPROM and user committed registers then should recover from the situation. I.e. the problematic program will be prevented from running.

  • +1 in reply to Chester Gillon
    TI__Genius 12740 points

    Mike,

    I was able to reproduce the behavior you described using the EXP432E401Y EVM. The example you pasted above causes a watchdog reset every 139mS and this prevents CCS from connecting to the device JTAG. I was also locked out of the board as you mentioned, but I was able to recover the board using the unlock procedure that Chester pointed out in his reply. After running the unlock sequence my EVM was completely erased and I was able to use CCS to reconnect to JTAG.

    Please let us know if you can try the JTAG unlock sequence again.

    -Ruben

  • 0 in reply to rperezti
    Expert 1005 points

    I found my issue, I have more than one XDS110 plugged in.  Can we specify which XDS110 to use?

  • 0 in reply to Mike_d
    TI__Genius 12740 points

    Mike, these command line utilities are described in this document www.ti.com/lit/sprui94. Unfortunately I don't see a way to specify a serial number for the dbgjtag.exe utility so you may have to connect to only one XDS110 when you are unlocking the device.