Category

Functional

Function

Device may enter lockup state during wake-up from LPM2, LPM3, and LPM4

Description

In rare cases, the device may enter lockup state during wake up from LPM2, LPM3, or LPM4. The device will remain in lockup state, unable to respond to interrupts or continue application execution, until a BOR reset occurs.

LPM0, LPM1, LPM3.5 and LPM4.5 are not affected by this behavior.

Workaround

1) Use LPM0 or LPM1. See device datasheet for details on wake up time and power consumption.

OR

2) Use LPM3.5 or LPM4.5 Note that only RTC or GPIO can wake from LPM3.5/4.5 and see device datasheet for details on wake up time and power consumption. When using LPM3.5/4.5 the Compute Through Power Loss (CTPL) Utility APIs, found in the FRAM Utilities download, can be used to configure device behavior prior to LPM entry and on wake-up.

OR

3) At the beginning of code, clear the FRLPMPWR bit in the GCCTL0 register, as shown below:

// PMM29 workaround. 
FRCTL0 = FRCTLPW;
GCCTL0 = FRPWR; //clear FRLPMPWR while keeping FRPWR set
FRCTL0_H = 0; //re-lock FRCTL
// End PMM29 workaround

This adds additional latency when waking from LPM to enter the ISR. To calculate the new wake up time with FRLPMPWR bit cleared, take the wake-up time for the low power mode used and add the t_{wake-up FRAM} value specified in the datasheet.
E.g. t_{wake-up workaround} = t_{wake-up LPM3} + t_{wake-up FRAM}