Breakpoints for RAM code being bypassed

I am running Crossworks v2.1.1 and debugging an EFM32GG290 part using the OEM J-link on the dev kit. The Segger J-link DLL is v436l, and I am using the new Crossworks J-link DLL recently posted to resolve an issue with this particular EFM32GG-DK3750 kit.

Breakpoints on code in RAM are being ignored. The properties (e.g. address) of the breakpoint are accurate, and I can single step through the code in RAM. Any breakpoint on code running from flash works fine. I'm surely missing a simple setting, but I have yet to discern it with a reasonable amount of research.

Jon Elliott

January 16, 2012 11:56

Can you try setting the Debugger Options > Startup Completion Breakpoint project property to "main".

Bryan Audiffred

January 16, 2012 15:39

I had tried the Startup Completion property before, and the IDE would crash with an internal error when debug began. You mentioned "main", and this program has no main function, ie. APP_ENTRY_POINT in thumb_crt0.s was not a function named "main". I added a main function residing in flash that immediately called my entry point in RAM, and breakpoints are working properly. The problem is now effectively resolved, but I am not uncertain how.

Breakpoints for RAM code being bypassed

Comments

Didn't find what you were looking for?