Cannot debug ANNA B112 with nrf52840-DK as Jlink

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

JONATHAN LL — Wed, 15 Jun 2022 12:52:39 GMT

Hi,

Following the Debug out for the nRF52840 DK you should be able to detect the BLE8 Click as an external device and program it.

As long as you have not cut SB40 you don't need to connect VDD_nRF' to VDD_nRF together with jumpers.

building a simple sample like the minimal should work on the BLE8 Click even if you build of the nrf52840 DK.

Regards,
Jonathan

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

emlynkz — Fri, 11 Feb 2022 16:14:13 GMT

I tried 1.7.0 for the NCS version. Tried disabling MCU boot.

The example is hello_world. The board is a BLE8 Click by Mikroe electronics. It has a ANNA-B112 and we use it as a dev board for the the ANNA-B12.

This is my wiring and connection to the nRF52840-DK. In the SDK, I have tried a custom board that we use on our production ANNA-B112 boards, the ubx_evkannab1_nrf52832.

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

JONATHAN LL — Fri, 11 Feb 2022 10:56:26 GMT

Stil not able to replicate the issue, but could see if the issue stil presist if MCUBoot is not included. It might be a trigering factor for the issue you are seeing.

Can you test with a different NCS tag like 1.7.0 to see if the issue still occurs. Can you give me an example that consistently fails to debug.

Regards,
Jonathan

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

emlynkz — Wed, 09 Feb 2022 13:31:39 GMT

It still never reaches my breakpoint in main.

Resetting target
Run to 'main' timed out. Trying to pause program
[New Thread -1143358499]
[New Thread -82578198]

Thread
2 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread -1143358499]
add-symbol-file [redacted_path]/build/zephyr/zephyr.elf

That's what I get in my console.

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

JONATHAN LL — Wed, 09 Feb 2022 12:17:06 GMT

In VS code you have to manually add the symbol (.elf) file in the debugger console (SPM as example here):

add-symbol-file my-build/spm/zephyr/zephyr.elf

vscode does not load symbols for multi-image projects (mcuboot, spm, b0 etc) so this could be te issue you are seeing.

Regards,
Jonathan

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

emlynkz — Thu, 03 Feb 2022 18:12:12 GMT

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.

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

JONATHAN LL — Thu, 03 Feb 2022 16:34:57 GMT

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

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

emlynkz — Thu, 03 Feb 2022 15:38:22 GMT

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,

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

JONATHAN LL — Thu, 03 Feb 2022 15:27:24 GMT

[quote user="emlynkz"]Debugging doesn't work.[/quote]

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

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

emlynkz — Thu, 03 Feb 2022 13:40:41 GMT

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.

RE: Cannot debug ANNA B112 with nrf52840-DK as Jlink

JONATHAN LL — Thu, 03 Feb 2022 12:21:22 GMT

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