Problems with the j-link debugger on nrf51 dongle

RE: Problems with the j-link debugger on nrf51 dongle

Sigurd — Wed, 24 Feb 2021 20:17:09 GMT

[quote userid="6103" url="~/f/nordic-q-a/71957/problems-with-the-j-link-debugger-on-nrf51-dongle/296095#296095"]It works now.[/quote]

Great!

[quote userid="6103" url="~/f/nordic-q-a/71957/problems-with-the-j-link-debugger-on-nrf51-dongle/296095#296095"]Wow, Can you please explain what was actually wrong?[/quote]

Could have been some bootloader or other code on the device that stopped your app from running.

[quote userid="6103" url="~/f/nordic-q-a/71957/problems-with-the-j-link-debugger-on-nrf51-dongle/296100#296100"]is it maybe possible to see the debug messages inside the uVision IDE? There is a window for it but it's always empty.[/quote]

I have not used that before, I think it requires Trace, and that is not supported by the nRF51.(might require a debugger with ETM support as well).

RE: Problems with the j-link debugger on nrf51 dongle

dragilla — Wed, 24 Feb 2021 17:02:13 GMT

Also, is it maybe possible to see the debug messages inside the uVision IDE? There is a window for it but it's always empty.

RE: Problems with the j-link debugger on nrf51 dongle

dragilla — Wed, 24 Feb 2021 16:39:29 GMT

For the teminal software I'm using "Termite". The nrfjprog --eraseall has helped!!! It works now. I can see a series of messages: APP:INFO:
FE F8 4C 29 99 31 12 71 D1 98 F2 96 E0 DB AB 15 þøL).1.q..ò.à.«.
APP:INFO:
APP:INFO:Random Vector:
APP:INFO:
98 7B 3B 28 9D 99 A0 97 6F 73 ED F0 AD 36 23 AF .{;(.. .osíð.6#¯
APP:INFO:

Wow, Can you please explain what was actually wrong?

RE: Problems with the j-link debugger on nrf51 dongle

dragilla — Wed, 24 Feb 2021 16:00:48 GMT

I'm using nrf connect to erase. But I will try with nrfprod and let you know. Thanks

RE: Problems with the j-link debugger on nrf51 dongle

Sigurd — Wed, 24 Feb 2021 15:56:12 GMT

Hi,

I have not tested tracing, but except for that, it looks correct.

1)What UART terminal software are you using ?

2) Try to use nrfjprog, and call "nrfjprog --eraseall" before you load the firmware, and see if that makes any difference.

RE: Problems with the j-link debugger on nrf51 dongle

dragilla — Wed, 24 Feb 2021 13:29:56 GMT

Here's my debug configuration in uViiosn, maybe you can spot something obvious:

photos.app.goo.gl/pZV8E3Swc73fFAHD6

RE: Problems with the j-link debugger on nrf51 dongle

dragilla — Wed, 24 Feb 2021 13:23:07 GMT

Hi, Thank you for your reply. I just compiled and run the example you mentioned and the program compiles and load with no problems. However in debug I still can't see any messages in neither UART nor RTT (using RTT viewer, external terminal and debug output in the IDE).

My problem must lie somewhere in the configuration of my IDE or the debugger maybe?

One thing worth noting (I think) - when I turn on the Trace option in my IDE, the device goes into HardFault_Handler immediately.

RE: Problems with the j-link debugger on nrf51 dongle

Sigurd — Wed, 24 Feb 2021 12:51:34 GMT

Hi,

Make sure that you have this in sdk_config.h

#define NRF_LOG_ENABLED 1

Take a look at how it's done in the pca10031(nRF51 dongle) RNG example project, in folder SDK_12\examples\peripheral\rng\pca10031\blank\arm5_no_packs