nrf52810 Eclipse Debug Problems

[josh]

Hello,

I'm trying to port my application from the nrf52832 to the nrf52810. I'm using the Fanstel modules, originally was using BT832 and am now trying to bring the application up on the BT832A. I upgraded form SDK 12 to SDK 15 as it looks like some better support for converting 52832 projects to 52810 was brought in around SDK 14.

I started with the ble_app_hids_keyboard (PCA10040e) example, and added in my custom changes. I set everything up per the Eclipse tutorial for getting the project setup (the tutorial is a bit dated, so I also referenced the SDK 12 nrf52832 eclipse setup I have working). I also referenced the users guide for the nrf52810 and made sure to remove the -DDEVELOP_IN_NRF52832 switch from my makefile. Everything builds and flashes, but I don't see the device advertising. I'm guessing I've made an error somewhere in my port, but I can't get the debugger working correctly in eclipse to track it down.

Eclipse doesn't seem to be able to find the source files for debugging, although the disassembly is at least finding the symbols.

Here are my debug settings:

I'm guessing its some problem with my eclipse setup, but I'm not exactly sure how to track it down. Any advice would be appreciated, thanks!

[josh]

I sorted it out, I messed up the optimization flags, I saw the "-g3" and changed the 3 to a 0, when I should have changed the "-os" to "-o0". Once I switched it to "OPT = -O0 -g3" the debugging is working as expected.

On a side note, what does the "-g" option do in the optimizations? I'm not familiar with this switch...

[Sigurd]

josh said:

On a side note, what does the "-g" option do in the optimizations? I'm not familiar with this switch...

The -g flag tells the compiler to generate debugging information. The number behind it sets the level of debug information that should be generated.

option	description
-g0	no debug information
-g1	minimal debug information
-g	default debug information
-g3	maximal debug information