This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I'm debugging a MSP430F5529 application with Code Composer Studio V5.2.18.
I've added a breakpoint with the "Watch on data address range" option like this :
In run mode the target is not halted when the RAM memory within the range of 0x2444 and 0x2484 changes.
What am I doing wrong?
Is the CCS not working with this kind of breakpoints?
The breakpoints with options : Watchpoint ( write/read) or code fetch are working fine.
Is there a problem in the EEM module of the MSP430F5529 ?
I 'm using a MSP-FET430UIF connected to the targets JTAG.
My coding is using the rts430x_lc_ld_eabi.lib and the USB Version_4_20_00 library.
Has anyone an idee what goes wrong with he breakpoint?
Greetings,
Eddy Stroobants
Hi Eddy,
Thanks for posting. It could perhaps be one of the F5529 erratum on the EEM: www.ti.com/lit/pdf/slaz314 so you may want to check those. However, I'm also wondering if you could be running into an issue with the old MSP430.DLL version that comes with CCSv5.2. If you look at the notes for different release versions on this page: http://processors.wiki.ti.com/index.php/MSP_Debug_Stack?keyMatch=msp debug stack&tisearch=Search-EN You can see in the "known issues" for DLLv2 version 2.4.9.1 on CCS version 4.2.4 there was an issue with range breakpoints. I know that is older than the version you are using, but I'm wondering if you might want to try to use a newer version of CCS (CCSv6 is now the latest one) to see if this might fix your issue.
-Katie
Hi Katie,
hi all,
The MSP430F5529 erratum did not give me any reason for having the breakpoint problem.
I was wondering if the EEM registers and debug settings is cleared during a POR, BOR or PUC of the target device.
Trying to simulate this by bringing the /reset NMI pin low of the microcontroller but when the MSP-FET jtag is connected , the reset pin isn't working (disabled)?
best regards,
Eddy
Hi Eddy,
Were you able to see if the newer version of CCS (CCSv6) resolves the issue, per my second point? You can test this while still maintaining your CCSv5 installation - this is what I do to keep multiple different versions of CCS installed on the same system:
1. Go download and start installing the latest CCS v6
2. When prompted about the install location, change it from the default. The default install location is C:\ti. But this is where you already likely have CCSv5 installed. So instead, make a folder with a name like C:\ti_6_1 (for installing CCSv6.1 for example) so that you can differentiate the two installs - tell the installer to put your CCSv6 there.
Now you can have both CCS versions installed on the same PC and choose to run one or the other. This will let you see if it is the old DLL version included with CCSv5 that is causing your issue.
Regards,
Katie
**Attention** This is a public forum