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.

MSP430F5510: MSP430F5510

Part Number: MSP430F5510


I am looking at SYSRSTIV to determine the reset reason. In my test application I stop servicing the watchdog after 100 seconds.

I get the reset value of: 16h = WDT time out (PUC)

If I now call the TI library functions listed below and don't service the watchdog the reset reason changes to:

0Ch = SVSL (POR)

I am trying to understand why the reset reason is changing.

void ConfigMSP430()
{

//SVS Low side is turned off
PMM_disableSvsL(__MSP430_BASEADDRESS_PMM__);

//Monitor low side is turned off
PMM_disableSvmL(__MSP430_BASEADDRESS_PMM__);

//Monitor high side is turned off
PMM_disableSvmH(__MSP430_BASEADDRESS_PMM__);

//SVS High side is turned on
PMM_enableSvsH(__MSP430_BASEADDRESS_PMM__);

//Enable POR on SVS Event
PMM_enableSvsHReset(__MSP430_BASEADDRESS_PMM__);

//SVS high side Full perf mode,
PMM_SvsHEnabledInLPMFullPerf(__MSP430_BASEADDRESS_PMM__);

//stays on in LPM3,enhanced protect
//Wait until high side, low side settled
while ( 0 == PMM_getInterruptStatus(__MSP430_BASEADDRESS_PMM__,
SVSMLDLYIFG + SVSMHDLYIFG )
) ;

PMM_clearPMMIFGS(__MSP430_BASEADDRESS_PMM__);
}

  • Read SYSRSTIV multiple times until you get zero.

    I don't know where the SVSL event comes from; it looks as if your code disables SVSL. Anyway, try reading SYSRSTIV to clear it before letting the watchdog expire.
  • Hi Stephen,

    There is a possibility you are experiencing a known erratum PMM9. Please take a look through the MSP430F5510 Device Erratasheet and try the workarounds. There are also several E2E posts concerning this issue as well:

    Please take a look through these and let me know if the workarounds solve the issue. In the meantime, I'll try recreating the issue on my end. 

    Best regards, 

    Caleb Overbay

  • Hi Stephen,

    A quick update:

    I was able to recreate the issue with the code you've posted above. I then tried the suggested workarounds for PMM9 and no oonger observed the SVSL (POR) in the SYSRSTIV register.

    Best regards,
    Caleb Overbay

**Attention** This is a public forum