Debugging strategy: how to make the OB JLink on nrf52dk work seamlessly (across several programs...)

[MuRa]

Hello all

I am playing around with the nrf52dk for the last 14days, done some progress, namely the TWI is working and I can read the sensor and printing its values in the debugger inside, when the emStudio is working, without a problem, I have even started to use the RTT, indeed, JScope works all good...

The major problem I am having is with the " Debug terminal " within the emStudio. The JLink has to be reset all most every time after the programm has been flashed... how to make this stable? I am using basic nrf_log...  In addition, if you develop the RTT , do you even bother with this terminal? Or should I rather switch to the UART, putty and alike, what is the strategy usually with regard to the debugging processes ? However, I am not sure , can both be used at the same time :)

In previous setup the Arduino's pritnout and plotter was used and its design was just good enough to get the job done, indeed, the JScope looks much more sophisticated, faster, etc. however, I would like to have an option to define the thickness of the line in JScope, I still did not figure out how to use the zoom on y axis... 

So far I am running the program from the emStudio , and scanning is done in the JScope, however, can this be synchronized and automatically use the preview in JScope... etc.

Please let me know what kind of a strategy are you using when debugging? Maybe I am not using the code properly, and is this why the emStudio debugging terminal has issues, needs to be reset almost every time, a bit annoying ...  , or is something else , has any of you experienced similar issues? 

Best.

[MuRa]

Hello all, 

just to let you know that I have put the nrf_log out and now just using simple printf() etc and terminal debugger works ok... sorry, I am not really sure why would someone use the nrf_log at all ? Anyway, after several tries got the same problems again... wondering what is going on, it is really annoying to work in this way ... is there a way to do the reset etc before everything else, do I have clear the buffer, etc. 

Best.

Best.

[Edvin]

MuRa said:

... is there a way to do the reset etc before everything else, do I have clear the buffer, etc. 

I am not sure I understand what you mean by this? 

What is your printk() backend? UART or RTT?