Cannot debug ANNA B112 with nrf52840-DK as Jlink

Hi,

Just want to clarify something: Are you able to debug the device with then nrf52 DK but not re-flash or otherwise erase or reset it?

If the device has been flashed with code that has DCDC enabled and the physical unit does not have that then you could brick the device, could this be what happend?


It is unclear to me if the device works or not after switching to nRF Connect SDK. 

Regards,
Jonathan

Hi,

Just want to clarify something: Are you able to debug the device with then nrf52 DK but not re-flash or otherwise erase or reset it?

If the device has been flashed with code that has DCDC enabled and the physical unit does not have that then you could brick the device, could this be what happend?


It is unclear to me if the device works or not after switching to nRF Connect SDK. 

Regards,
Jonathan

Hi,

I am able to erase, debug, flash and reflash with the nrf52840-DK using SES on the nrf5 SDK.
With the nrf52840-DK using both the newer SES and VsCode and the nrfConnect SDK I can only flash, reflash and erase. Debugging doesn't work.

The device is not bricked.

emlynkz said:

Debugging doesn't work.

Do you gett eany errors?

Does it work if you are not using the nrf52840 DK as a programmer\debugger wehn using NCS(nRF Connect SDK)?

Can you share some more info on the work enviroment?

Operating system
VS code version
NCS version

Thanks for the explanation.

Regards,
Jonathan

I get this as an error when the debug launches:

0x00004f80 in ?? ()
Program stopped, probably due to a reset and/or halt issued by debugger
add symbol table from file "c:/[REDACTED PATH TO PROJECT]/build/zephyr/zephyr.elf"
(y or n) [answered Y; input not from terminal]
Reading symbols from c:/[REDACTED PATH TO PROJECT]/build/zephyr/zephyr.elf...
Resetting target
Resetting target
Run to 'main' timed out. Trying to pause program

I tried another devkit of the same model as a programmer, and also a NINA-B111 as a programmer. All 3 have the exact same behavior.

NCS Version 1.8.0

VSCode version 1.63.2 with nRF connect extension pack v2021.9.1

EDIT: OS version is Windows 10 21H2 build 19044.1466

Thanks,

 This might be a bug that is fixed in cortex-debug 0.4.6 or later. Pleas update if you have an earlier version.

There is this case: Unable to use debugger in VS Code using nRF Connect - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

See Einars Comment:

In a nutshell: Leave "Enable debug options" unchecked for samples that does not use threads.

Update: A workaround is to be to start debugging by Run -> Start Debugging (or pressing F5) instead of starting by clicking the "Debug Application" icon within the nRF Connect for VS Code plugin.

 

Are you using the nRF Connect for Desktop app and using the toolchain manager? launching the SW from there?


Regards,
Jonathan

Yes, I am using the nRF Connect for desktop app, and the toolchain manager. I tried launching VSCode both from the toolchain manager and the start menu.

The cortex-debug version is v1.2.2.

The method to leave the option unchecked and pressing F5 doesn't work, as it never reaches my breakpoint in main, but it stops at random other files.