米6体育平台手机版

SLAZ616AA August 2014 – August 2021 MSP430FR68891

1
2
3
4
5
1. 6
2. 7
  1. 8
  2. 9
3. 10
11
1. 12
2. 13
3. 14
4. 15
5. 16
6. 17
7. 18
8. 19
9. 20
10. 21
11. 22
12. 23
13. 24
14. 25
15. 26
16. 27
17. 28
18. 29
19. 30
20. 31
21. 32
22. 33
23. 34
24. 35
25. 36
26. 37
27. 38
28. 39
29. 40
30. 41
31. 42
32. 43
33. 44
34. 45
35. 46
36. 47
37. 48
38. 49
39. 50
40. 51
41. 52
42. 53
43. 54
44. 55
45. 56
46. 57
58

6.31 PMM24

PMM Module

Function

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

Description

The device may enter a lockup state during an interrupt-triggered wake up from LPM3 or LPM4. The device will remain in lockup state, unable to respond to the interrupt or continue application execution, until a power cycle brings it back to reset state.

LPM3.5 and LPM4.5 are not affected by this behavior.

Workaround

1) Use LPM2 instead of LPM3 or LPM4. Refer to the device specific datasheet for details on LPM2 wake up time and power consumption.

OR

2) If the application only uses RTC or GPIO as a wakeup source, use LPM3.5 or LPM4.5 instead. Refer to the device specific datasheet for details on LPM3.5/LPM4.5 wake up times and power consumption.
Note: When using LPM3.5/LPM4.5, the Compute Through Power Loss (CTPL) utility APIs (part of the FRAM software utilities) can be used to configure device behavior prior to LPM entry and on wake-up.

6.31 PMM24

Category

Function

Description

Workaround