米6体育平台手机版

SLAZ283AA October 2012 – May 2021 MSP430F5435

1
2
3
4
5
1. 6
2. 7
  1. 8
3. 9
10
1. 11
2. 12
3. 13
4. 14
5. 15
6. 16
7. 17
8. 18
9. 19
10. 20
11. 21
12. 22
13. 23
14. 24
15. 25
16. 26
17. 27
18. 28
19. 29
20. 30
21. 31
22. 32
23. 33
24. 34
25. 35
26. 36
27. 37
28. 38
29. 39
30. 40
31. 41
32. 42
33. 43
34. 44
35. 45
36. 46
37. 47
38. 48
39. 49
40. 50
41. 51
42. 52
43. 53
44. 54
45. 55
46. 56
47. 57
48. 58
49. 59
50. 60
51. 61
52. 62
53. 63
54. 64
55. 65
56. 66
57. 67
58. 68
59. 69
60. 70
61. 71
62. 72
63. 73
64. 74
65. 75
66. 76
67. 77
68. 78
69. 79
70. 80
71. 81
72. 82
73. 83
74. 84
75. 85
76. 86
77. 87
78. 88
79. 89
80. 90
81. 91
82. 92
83. 93
84. 94
85. 95
86. 96
87. 97
88. 98
89. 99
90. 100
91. 101
92. 102
93. 103
94. 104
95. 105
96. 106
97. 107
98. 108
99. 109
100. 110
101. 111
102. 112
103. 113
104. 114
105. 115
106. 116
107. 117
108. 118
109. 119
110. 120
111. 121
112. 122
113. 123
114. 124
115. 125
116. 126
117. 127
118. 128
129

6.11 CPU20

CPU Module

Function

An unexpected Vacant Memory Access Flag (VMAIFG) can be triggered due to the CPU autoincrement of the MAB+2 outside the range of a valid memory block.

Description

The VMAIFG can be triggered under the following conditions:

1. If an interrupt is requested, fetched by the CPU, but lost before excution of the interrupt service routine.

OR

2. If a PC-modifying instruction (e.g. - ret, push, call, pop, jmp, br) is fetched from the last address of a section of memory (e.g.- FLASH, RAM) that is not continguous to a higher, valid section on the memory map.

Workaround

For case 1 - None.
For case 2 - If code is affected, edit the linker command file to make the last four bytes of affected memory sections unavailable.

Refer to the table below for compiler-specific fix implementation information.

IDE/Compiler	Version Number	Notes
IAR Embedded Workbench	IAR EW430 v6.40 or later
TI MSP430 Compiler Tools (Code Composer Studio)	Not affected
MSP430 GNU Compiler (MSP430-GCC)	Not affected

6.11 CPU20

Category

Function

Description

Workaround