MSP-EXP430FR5994: HW or SW breakpoints not working in CCS 12.7.0.00007 + msp430-gcc-9.3.0.31_win64 on Windows11

Dose the functions(you put the breaks) be called in the main function?

Yes, even breakpoints at the beginning of main() get ignored ; and run-to-line to the same lines work, on the other hand.

Hello,

Pascal Chambon said:

I have the same message "no code associated with..." when trying to force-enable these breakpoint

There appears to be some issue with the source code correlation. Would you be able to provide the project with the issue?

Thanks

ki

Yes, thanks, here is the code of the project

https://sharing.prolifik.net/MSP430-ECC_WITH_CCS_GCC.zip

I managed to make a breakpoint work once in main(), without reason, but the rest of the time I get this auto-disabling of hw/sw breakpoints and the error message mentioned above

Hello,

Thank you for the test case. Using CCS 12.7.0, I was able to import the project and load the executable to my FR5994 LaunchPad. I didn't see any issues with source line breakpoints:

Can you close the randombytes.c file in the editor, then see if you click on the "randombytes" function in the Modules view if that opens the correct file in the editor.

If you have never used the Modules view, please see: https://dev.ti.com/tirex/explore/node?node=A__APVIzRhtpuf-7AMAb9iu3w__ccs_devtools__FUz-xrs__LATEST

I tried the Modules panel, and indeed the files and functions of my code can be properly opened from here

When setting a breakpoint in a project-root C file, though, I just discovered that it it works.
It's as if having some C files in a "test/" subdirectory breaks their breakpoint system :??

Pascal Chambon said:

I tried the Modules panel, and indeed the files and functions of my code can be properly opened from here

Then the source code correlation appears to be ok.

Pascal Chambon said:

It's as if having some C files in a "test/" subdirectory breaks their breakpoint system :??

As you can see in my screenshot, I can set source line breakpoints in ./test/randombytes.c. 

In your latest screenshot, your CCS IDE looks a little different. For example, the tabs in the editor and some of the views have more rounded edges than the sharp square edges in my default CCS IDE environment. Are you using a different theme or perspective?

I'm using the default perspectives of EDIT and DEBUG, is it due to Windows 11 that panels are a bit different ??

Pascal Chambon said:

I'm using the default perspectives of EDIT and DEBUG

You mean the CCS Edit and CCS Debug?

Pascal Chambon said:

is it due to Windows 11 that panels are a bit different ??

I don't think so but I will need to check on a Windows 11 PC to confirm

Ki said:

I don't think so but I will need to check on a Windows 11 PC to confirm

Everything works (and looks) fine on Windows 11 also.

Can you try cleaning your environment and workspace (9.4.2 and 9.4.3): https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_troubleshooting.html#general-ide

Also try steps 9.7.3, 9.7.4, and 9.7.5?

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_troubleshooting.html#delete-the-debug-launch-configuration

Thanks

ki

Yes it's CCS EDIT/DEBUG perspectives that I use

I've tried all the manipulations/reset listed above, 9.4.2 and 9.4.3 and 9.7.3 and 9.7.4, and 9.7.5

The faulty project is now the only one enabled in my workspace, but I still have the breakpoint bug for non-root source files  :?

I've checked my PATH; no weird mingw/gcc installs are in it, so it's not this kind of conflict either

When I check the Modules view, I do not see the compare.c file or compare function listed. It does not look like it was used in the build. Or at least it does not exist in the debug symbols. So the error you see would be expected in this case.

I have the "compare.c" file and functions in my Modules tab, and the breakpoints work fine with them ;

It' only when I try to enable the breakpoints from test/* files, like le main() of test/test.c, that I get the error messages, whereas all these files/symbols too are well in the Modules tab.

It is really weird  :?

With the TI Compiler I have no problems though, it's only with GCC

Pascal Chambon said:

I have the "compare.c" file and functions in my Modules tab, and the breakpoints work fine with them ;

It' only when I try to enable the breakpoints from test/* files, like le main() of test/test.c, that I get the error messages, whereas all these files/symbols too are well in the Modules tab.

It is really weird  :?

It's weird, I have the reverse problem. I can't set breakpoints in compare.c and it is not visibile in the modules view. Hence I can't set breakpoints there also.

I have no issues setting breakpoints in test.c

Hm there is definitely something broken with GCC in CCS for MSP430, but even if not on the same files (and with differences in the Modules panel), we have a reproducible bug here.

What's the best way to escalate this?

Pascal Chambon said:

Hm there is definitely something broken with GCC in CCS for MSP430, but even if not on the same files (and with differences in the Modules panel), we have a reproducible bug here.

I'm not convinced there is a bug. I took a look at the example project you sent me and I don't see compare() ever called. Hence it would makes sense that it is not referenced in the debug symbols. Are you using a different example? I can step into various functions and CCS can find all the source and I can set source breakpoints in all of them. 

Ah, for compare.c I indeed modified the main() to call the compare() function, and thus test the breakpoint in it.

So in your case you probably have no bug, just the normal optimizing-out of unused functions

But on my side I can't get why main() - which IS called :D - gets this breakpoint error as if it was not available in symbols  :???

For us to debug the issue, I need a reproducible test case. I'm still befuddled why the source code correlation is not working.

The below video is what I am doing:

Have all your source files closed in the editor. Then when the program is loaded and run to main, it should open test.c and be halted in main. In the test.c that was opened by CCS, you cannot set a breakpoint on any source line like I am doing in the video? Your optimization setting is -Og, correct?