nRF5340 network cpu debugging

[ubat]

Dear service team,

 I'm running into issues trying to debug the nRF5340 network core:

Software

nRF Connect SDK v2.0.0, freshly installed
Visual Studio Code 1.67.2
nRF-Command-Line-Tools-10.15.4-x64.exe 

No changes to the installation or code after installation.

 

 Hardware

nRF5340-DK, 2.0.0, 2021.42

 

 It is possible to:

• Build and flash everything as desired
• Debug code on the application core, e.g. blinky

 

It is not possible to:

• Debug code, e.g. blinky on the network core.
  
  The application core is before loaded separately with 'empty' built for the application core.
   
  The blinky build for the network core will work nicely when flashed, but debugging instantly ends up in Disassembly 0x01004614, which corresponds to 'fault.c' lines 756 and following.
  'Enable Debug Options' is enabled.
  
  When trying other samples for the network core, like PRX, disassembly will also pop up, yet for different files.

 

As I need to develop a custom protocol, getting PRX up and going with debugging would be very helpful.

 

Trying the SES before, debugging would also work for the network core, but loading the firmware was not working except after a full recovery. I'd love to have a solution for Visual Studio.

 

Thank you!

Uli

[Einar Thorsrud]

Hi Uli,

I tested this now with nRF Connect SDK 2.0.0 and nRF Connect for VS Code v2022.6.22 and VS Code 1.67.2, so same as you. Using empty app core and blinky on the net core I am able to debug and step in the code on the network core. That is using J-Link SW version 7.66b, and I know there were issues for some time with older J-Link drivers. Can you try updating to the latest?

[ubat]

Hi Einar, 

thank you! Turns out, I was on JLinkARM.dll version: 7.58b. With the new version 7.66b, debugging is working, thank you!

First, it gave me a bluescreen. Then, one of the two boards didn't work. However, now it's working :D 

A small follow up question: can you please point me how to enable instruction trace on Visual Studio? This is what I'm used to from my other cortex projects on Keil: µVision Debugger (keil.com) 

For Nordic I can find this page, also for Keil: Debugging nRF52 series devices using Trace - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com)

The tracedata pins are connected, so the hardware seems capable of doing ETM trace, but I can't find any help how to view it with Visual Studio.

[Einar Thorsrud]

Hi Uli,

Good to hear you got it working.

We do not have support for ETM in VS Code, unfortunately. That does not necessarily mean that it is not possible, but we have not done it or worked on it, so I can unfortunately not provide any pointers.

[ubat]

Hi Einar,

thank you for the quick reply! That's too bad, I personaly absolutely love it. 

But I'm good for now, just glad that debugging is working.

Have a good time!