nRF5340 network cpu debugging

RE: nRF5340 network cpu debugging

ubat — Wed, 08 Jun 2022 07:58:35 GMT

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!

RE: nRF5340 network cpu debugging

Einar Thorsrud — Wed, 08 Jun 2022 07:53:45 GMT

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.

RE: nRF5340 network cpu debugging

ubat — Tue, 07 Jun 2022 13:34:40 GMT

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.

RE: nRF5340 network cpu debugging

Einar Thorsrud — Tue, 07 Jun 2022 13:02:36 GMT

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?