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've setup a CCS project for the MSP430F5529 where I've linked to all of my source files because they are located in a directory above the directory where my project files exist. The project builds, loads and runs just fine. I can single step, step into, and step out of functions in different files and the debugger is able to track the PC in the source window. I'm having 2 serious issues though:
1) I'm not able to set and enable a breakpoint in the source window. I can set the breakpoint and it shows up in my breakpoint list but it's disabled, and when I try to enable it I get this error: No code is associated with "C:\projects\broken\ccs\Debug/C:/projects/broken/source/blink.c", line 32 in "C:\projects\broken\ccs\Debug\test.out"
2) To workaround issue 1 I'm setting and enabling breakpoints in the disassembly window and those breakpoints work OK. The only issue with that is that the source is not interleaving even though I enable source interleaving so it's really difficult to use that as a workaround.
To simplify and demonstrate the error I created an example LED blink test project in the directory C:\projects\broken\ccs then I moved and linked the blink.c file to the directory C:\projects\broken\source\blink.c.
I've attached the zipped up working and broken projects. They are identical except for the relative location of project files vs. source file.
Does anyone know the magic to fix this without moving the project root directory?
Hi Brian,
Are you using CCSv5 M8? There is a known issue with that build regarding linked files and source line breakpoints:
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/134993.aspx
ki
Yes, I'm using CCSv5 M8 so that's the same issue I'm seeing. I checked the status of the incident report and it looks to be fixed for the next release.
Thanks,
-Brian