How do I figure out why GDB isn't breaking at main?

RE: How do I figure out why GDB isn't breaking at main?

FormerMember — Thu, 08 Jun 2017 06:31:36 GMT

Yes, how to debug with softdevice is another topic, so it would be nice if you could post a new question. Before doing so, I would recommend you to search the topic in existing questions, it is a widely discussed topic.

RE: How do I figure out why GDB isn't breaking at main?

Jandyman — Wed, 07 Jun 2017 14:52:35 GMT

It now appears that the problem is not so much a debugger problem as a problem with the SoftDevice transferring control to my app. If I unclick "Continue" in the Debug configuration options, I can see sensible (SoftDevice) code at low addresses. I can also disassemble my main function, it looks correct, and I can see my breakpoint in both the assembly window and the source window. So, it now appears that my question is "How do I debug problem with the SoftDevice transferring control to my app?". Should I file a new question?

RE: How do I figure out why GDB isn't breaking at main?

FormerMember — Wed, 07 Jun 2017 06:14:10 GMT

This problem typically occurs if flash and RAM settings for the project aren't set correctly. For GCC, these settings should be set in the linker script (.ld file).

S134 v.4.0.0 release notes:

Corresponding settings in the linker script:

MEMORY
{
  FLASH (rx) : ORIGIN = 0x1f000, LENGTH = 0x61000
  RAM (rwx) :  ORIGIN = 0x20002558, LENGTH = 0xdaa8
}