米6体育平台手机版

SLAZ105Z October 2012 – May 2021 CC430F6147

1Functional Advisories
2Preprogrammed Software Advisories
3Debug Only Advisories
4Fixed by Compiler Advisories
5Nomenclature, Package Symbolization, and Revision Identification
6Advisory Descriptions
1. 6.1 ADC39
2. 6.2 ADC42
3. 6.3 ADC69
4. 6.4 AES1
5. 6.5 BSL7
6. 6.6 BSL14
7. 6.7 COMP10
8. 6.8 CPU21
9. 6.9 CPU22
10. 6.10 CPU36
11. 6.11 CPU40
12. 6.12 CPU46
13. 6.13 CPU47
14. 6.14 DMA4
15. 6.15 DMA7
16. 6.16 DMA10
17. 6.17 EEM17
18. 6.18 EEM19
19. 6.19 EEM23
20. 6.20 JTAG26
21. 6.21 JTAG27
22. 6.22 LCDB5
23. 6.23 LCDB6
24. 6.24 PMM11
25. 6.25 PMM12
26. 6.26 PMM14
27. 6.27 PMM15
28. 6.28 PMM18
29. 6.29 PMM20
30. 6.30 PMM26
31. 6.31 PORT15
32. 6.32 PORT19
33. 6.33 PORT29
34. 6.34 RF1A1
35. 6.35 RF1A2
36. 6.36 RF1A3
37. 6.37 RF1A5
38. 6.38 RF1A6
39. 6.39 RF1A8
40. 6.40 SYS12
41. 6.41 SYS16
42. 6.42 UCS11
43. 6.43 USCI26
44. 6.44 USCI30
45. 6.45 USCI34
46. 6.46 USCI35
47. 6.47 USCI39
48. 6.48 USCI40
7Revision History

6.17 EEM17

EEM Module

Function

Wrong Breakpoint halt after executing Flash Erase/Write instructions

Description

Hardware breakpoints or Conditional Address triggered breakpoints on instructions that follow Flash Erase/Write instructions, stops the debugger at the actual Flash Erase/Write instruction even though the flash erase/write operation has already been executed. The hardware/conditional address triggered breakpoints that are placed on either the next two single opcode instructions OR the next double opcode instruction that follows the Flash Erase/Write instruction are affected by this erratum.

Workaround

None. Use other conditional/advanced triggered breakpoints to halt the debugger right after Flash erase/write instructions.

Note: This erratum affects debug mode only.

6.17 EEM17

Category

Function

Description

Workaround