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

Question

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.

Turbo J · Accepted Answer

Cross Register said: pause debugging, and if I try to continue debugging t 
 Enabled Softdevice will always FAULT when you continue debugging, as it uses hardware timers (specified in SDS) to check whether it met BTLE/ANT+ timing requirements. These cannot be met when the MCU core is halted for debugging. This also is the reason why several interrupt priorities are not allowed for the application. 
 You only have printf()-style debugging available once softdevice was enabled, I recommend looking at NRF_LOG_XXX macros.

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

Top Replies