nRF53 and debugging with SES

[sread]

I have set up the NCS toolchain, followed the instructions to update the JLink DLL in SES, and successfully built/flashed a few examples to the app core (ie. debug/ppi_trace).

Now I am working on a test application that requires radio access. Ideally I'd like to develop exclusively on the network core so I don't have to do any IPC at this stage. When I follow the suggested procedures for debugging (selecting "nRF9160") I get "Download Failed" messages in SES with a "Failed to write memory" popup. I get the same result trying to program hci_rpmsg sample from zephyr for the net target with SES.

It seems I can use "west flash" from the folder after building with SES, but I am curious if debugging is supported for the net core. What am I missing?

[Marciano-PL]

So far it seems that reading memory from the Net core is neigh impossible while not halted. I have still managed to upload firmware through SES, but it takes more steps and debugging isn't the least bit reliable.

1. Target/Connect J-Link
2. Target/Reset J-Link
3. Target/Download zephyr/zephyr.elf
4. Target/Verify zephyr/zephyr.elf
5. Target/Attach Debugger

These steps will upload the firmware and enable you to debug (but only a couple of steps.) You can skip step 5 and reset the device and it will run. I've been using the printk function as my debugger for the time being. Also, J-Link now has an option for you to select nRF5340_xxAA_NET or ..._APP.

[sread]

Thanks for the tip, I was still on J-Link 6.54c as stated in the documentation.

After upgrading to 6.56c I have the correct target devices and I can debug after setting Debug > Debugger > Target Device to nRF5340_xxAA_NET. Much better!