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.
EEM19
EEM Module
Category
Debug
Function
DMA may corrupt data in debug mode
Description
When the DMA is enabled and the device is in debug mode, the data written by the DMA
may be corrupted when a breakpoint is hit or when the debug session is halted.
Workaround
This erratum has been addressed in MSPDebugStack version 3.5.0.1. It is also available
in released IDE EW430 IAR version 6.30.3 and CCS version 6.1.1 or newer.
If using an earlier version of either IDE or MSPDebugStack, do not halt or use breakpoints
during a DMA transfer.
Note
This erratum applies to debug mode only.
EEM23
EEM Module
Category
Debug
Function
EEM triggers incorrectly when modules using wait states are enabled
Description
When modules using wait states (USB, MPY, CRC and FRAM controller in manual mode)
are enabled, the EEM may trigger incorrectly. This can lead to an incorrect profile counter
value or cause issues with the EEMs data watch point, state storage, and breakpoint
functionality.
Workaround
None.
Note
This erratum affects debug mode only.
JTAG26
JTAG Module
Category
Debug
Function
LPMx.5 Debug Support Limitations
Advisory Descriptions
14
MSP430F6723 Microcontroller
SLAZ340AF – OCTOBER 2012 – REVISED MAY 2021
Copyright © 2021 Texas Instruments Incorporated
