米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.86 SYS2

SYS Module

Function

Protection weakness in BSL flash address range

Description

If the BSL Protection is enabled, just the lowest 16 bytes of the secured BSL part should be usable as entry area (jump table). Instead, this entry window (not secured from readout by CPU) can be also be seen on other addresses - address locations affected are dependent on the selected size of the BSL.

Example: for BSLSIZE = 0, memory is reflected into 0x01600 to 0x0160F & 0x01700 to 0x0170F

Similarly, if RAM space is assigned as BSL area and secured, the mechanism can be observed. Only the area 0x01C00 to 0x01C0F should be protected, but the following RAM areas are also secured and no longer accessible: 0x01D00 to 0x01D0F, 0x01E00 to 0x01E0F, 0x01F00 to 0x01F0F, 0x02000 to 0x0200F... 0x02B00 to 0x02B0F.

Any access to locations affected by errata leads to a security reset.

Workaround

- Do not use RAM as secured area for BSL
or
- Do not put sensitive user code/data in the additional BSL entry address windows.

6.86 SYS2

Category

Function

Description

Workaround