No code for breakpoint at segger

RE: No code for breakpoint at segger

Gil — Thu, 05 Sep 2019 07:09:28 GMT

This issue can be closed

RE: No code for breakpoint at segger

Gil — Thu, 05 Sep 2019 07:08:57 GMT

Thanks RK, it's working.

I am new to segger so i was not aware of this option.

Thanks you very much

RE: No code for breakpoint at segger

ExAg — Tue, 03 Sep 2019 11:45:53 GMT

Hi RK

The "mqtt_simple" example project has no configurations at all (only "Common"). As described in the link I mentioned, you have to edit the prj.conf file to disable the code optimization.

And for the hint with "CONFIG_DEBUG_OPTIMIZATIONS=y" see here.

But for Gil your suggestion is probably the solution.

Regards

ExAg

RE: No code for breakpoint at segger

RK — Tue, 03 Sep 2019 11:40:11 GMT

Why don't you just change the build type from 'Release' to 'Debug' in the dropdown at the top left of Segger Embedded Studio .. or doesn't it have a Debug configuration?

RE: No code for breakpoint at segger

ExAg — Tue, 03 Sep 2019 11:08:39 GMT

Hi Gil

As I have just learned from my own problems, you should use "CONFIG_DEBUG_OPTIMIZATIONS=y" (not CONFIG_NO_OPTIMIZATIONS=y).

Regards

ExAg

RE: No code for breakpoint at segger

ExAg — Tue, 03 Sep 2019 07:28:10 GMT

Hi Gil

I would say this is because segger studio has enabled code optimization per default.

For nRF5160 projects, you have to add "CONFIG_NO_OPTIMIZATIONS=y" in the prj.conf file of your project: see also this thread.

regards

ExAg

RE: No code for breakpoint at segger

Amanda Hsieh — Mon, 02 Sep 2019 13:20:35 GMT

Hi Gil,

That means Invalid breakpoint. An invalid breakpoint is one where the breakpoint cannot be set; for example, no executable code is associated with the source code line where the breakpoint is set or the processor does not have enough hardware breakpoints.

If you check the SEGGER user guide/ Debugging windows, you can see the statements:

-Amanda H.