Segger Studio with nRF51422 - strange behavior in call stack during Debug

[Cross Register]

Hi everyone,

Recently, I downloaded the SEGGER Embedded Studio, release 4.18, and start the development of a Heart Rate Monitor using nRF51422 and SDK 10 (softdevice s310).

I was able to setup all the SDK files into the IDE project manually, because this version of SDK doesn't support SEGGER Studio, and compile my project and downloaded it into the PCA10028 kit without any trouble so far. (thanks to the community, it was very helpful!). Even though everything works fine for generate the code, burn the flash and run the application correctly, trying to debug is impossible probably because of some misplaced configuration.

When I start the debugging module the program pointer get to the main routine just fine, but when I run or continuing stepping, the call stack goes to an specific memory address and pause debugging, and if I try to continue debugging the PC goes to 0xFFFFFFFE and nothing happens anymore, like it completely lost this path.

Here is a print of the call stack:

The specific address are 0x0000011C, 0x000006B0, respectively.

Could someone help me? 

Thanks,

Vítor.

[awneil]

Cross Register said:

start the development

Why would you start anything on an nRF51 ?

Note that the nRF51 is not recommended for new BLE designs:

https://devzone.nordicsemi.com/f/nordic-q-a/42960/status-of-nrf51-products/169728#169728

It also doesn't have monitor-mode debug.

[Cross Register]

Hi Awneil,

Thanks for the advice, I noticed that everything about nRF51 are hidden in Nordic Website.

awneil said:

Why would you start anything on an nRF51 ?

We already have another project in production phase that uses nRF51, and the priority of this new project is validate others logics that doesn't have anything related to the radio by testing it in its final application. On a second moment, I'll focus on the radio logic (and convince the project manager to change the radio to nRF52).

Best regards,

Vitor.

[awneil]

I see.