nRF53 and debugging with SES

RE: nRF53 and debugging with SES

sread — Wed, 11 Dec 2019 23:47:30 GMT

My error was probably due to the debugger defaulting to the APP target.

It would be helpful to update the documentation to match J-Link Version V6.56 (2019-11-22) where 5340 programming support was added.

Thanks!

RE: nRF53 and debugging with SES

sread — Wed, 11 Dec 2019 23:28:45 GMT

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!

RE: nRF53 and debugging with SES

Kenneth — Wed, 11 Dec 2019 15:06:24 GMT

I have the same error message as you. Let me see what I can find out from the NCS team.

Kenneth

RE: nRF53 and debugging with SES

Marciano-PL — Wed, 11 Dec 2019 01:07:29 GMT

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.

Target/Connect J-Link
Target/Reset J-Link
Target/Download zephyr/zephyr.elf
Target/Verify zephyr/zephyr.elf
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.