nrf5340 debug network core?

RE: nrf5340 debug network core?

Håkon Alseth — Tue, 05 May 2020 10:12:16 GMT

Glad to hear it worked out 🙂 Let me know if you have more questions/issues.

Stay safe and take care!

Kind regards,

Håkon

RE: nrf5340 debug network core?

skxo — Tue, 05 May 2020 10:11:03 GMT

It works like a charm!

JLinkGDBServer -device nRF5340_xxAA_NET -autoconnect 1 -if SWD -speed 4000 -port 2331 -swoport 2332 -telnetport 2333

and I can do my multicore debug now, thanks!

on SEGGER J-Link GDB Server V6.70g Command Line Version

Regards

take care

RE: nrf5340 debug network core?

Håkon Alseth — Tue, 05 May 2020 10:00:08 GMT

[quote user="skxo"]I need SES for that and I am sorry but I don't want to use it. I prefer to just use command line to keep it simple.[/quote]

You input this to the GDB server:

JLinkGDBServer -device <device> -if swd -otheroptions

If this isn't a valid device, please update your segger drivers. I'm running 6.64b.

Kind regards,

Håkon

RE: nrf5340 debug network core?

skxo — Tue, 05 May 2020 09:17:32 GMT

"Try connecting to devices nRF5340_xxAA_APP and nRF5340_xxAA_NET, and it should select the appropriate core for you."

I need SES for that and I am sorry but I don't want to use it. I prefer to just use command line to keep it simple.

Is there any other solution please?

RE: nrf5340 debug network core?

Håkon Alseth — Tue, 05 May 2020 09:13:26 GMT

Hi,

[quote user="skxo"]It works well but how can you specify to connect to the second core? Even if you open 2 sessions, it connect to the app core (I can verify that by single stepping in one window, then I switch to the second session and my PC is updated)[/quote]

Try connecting to devices nRF5340_xxAA_APP and nRF5340_xxAA_NET, and it should select the appropriate core for you.

[quote user="skxo"]Does Nordic can provide JLinkScriptFile to connect to the second core of the nrf5340 please?[/quote]

I'll report this internally as a feature request.

Kind regards,

Håkon

RE: nrf5340 debug network core?

skxo — Tue, 05 May 2020 08:52:20 GMT

HI,

thank you for your support.

I tried with JLinkExe playing this command:

JLinkExe -device Cortex-M33 -autoconnect 1 -if SWD -speed 4000

It works well but how can you specify to connect to the second core? Even if you open 2 sessions, it connect to the app core (I can verify that by single stepping in one window, then I switch to the second session and my PC is updated)

I saw JLinkExe can add parameter like JLinkScriptFile to specify CoreSightAdress and other parameters.

Does Nordic can provide JLinkScriptFile to connect to the second core of the nrf5340 please?

Even if I open 2 sessions (for example):

JLinkGDBServer -device Cortex-M33 -autoconnect 1 -if SWD -speed 4000 -port 2331 -swoport 2332 -telnetport 2333

JLinkGDBServer -device Cortex-M33 -autoconnect 1 -if SWD -speed 4000 -port 2334 -swoport 2335 -telnetport 2336

I connect two session on the same core.

I need a way to specifically attach the second core, maybe using core id parameter ?

It would be great if Nordic can provide multi-cores debugging support four his multi-core SoC :-)

Cheers Stay healthy!

RE: nrf5340 debug network core?

Håkon Alseth — Tue, 05 May 2020 08:07:16 GMT

Hi sk,

We use segger jlink debuggers (in combination with Segger embedded studio nordic edition, Segger Ozone, or gdb directly). I had a chat with R&D, and it should be possible to debug both at the same time (I'm unfortunately not able to test this right now, as my nRF5340 kit is not within reach).

To debug both cores at the same time, you should be able to do so by opening two debug sessions (one for each core).

Kind regards,

Håkon

RE: nrf5340 debug network core?

skxo — Mon, 04 May 2020 11:37:58 GMT

Hi,

thank you for this information.

what setup/tool do you recommend to debug the two cores simultaneously please in that case?

Cheers

RE: nrf5340 debug network core?

Håkon Alseth — Mon, 04 May 2020 07:52:39 GMT

Hi,

The CPU cores are both Cortex M33 on the nRF5340, which is the same core as the nRF9160.

We do not support openocd, and it doesn't seem like the project officially supports neither nRF9160 or nRF5340?

The network core is started up from the application core, so you need to first boot up the net core via this register:

https://infocenter.nordicsemi.com/topic/ps_nrf5340/chapters/reset/doc/reset.html?cp=3_0_0_3_7_10_1#register.NETWORK.FORCEOFF

If you flash the app core with a simplistic firmware (zephyr/samples/hello_world), it will automatically boot up the net core via this file:

https://github.com/NordicPlayground/fw-nrfconnect-zephyr/blob/master/boards/arm/nrf5340_dk_nrf5340/nrf5340_cpunet_reset.c#L55

Kind regards,

Håkon