nRF5340 debug network core

RE: nRF5340 debug network core

Jordan Archer — Sun, 27 Jun 2021 19:29:48 GMT

Any response to this?

RE: nRF5340 debug network core

Simonr — Tue, 25 May 2021 07:04:35 GMT

There has not been any updates on the internal ticket as of yet, so it seems our team is stuck on this still. I'm very sorry it's been so long without any resolution. I've pinged them yet again for an update now.

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Fri, 21 May 2021 12:25:31 GMT

Hi,

Any updates?

RE: nRF5340 debug network core

Christoffer Brask — Thu, 22 Apr 2021 13:18:12 GMT

Thanks for the update, GDB is one of the most common debugging tools so it would be sad if nrf53 does not support this.

RE: nRF5340 debug network core

Simonr — Thu, 22 Apr 2021 09:57:43 GMT

Just another update again, still no resolution I'm afraid. GDB (that VSCode uses for debugging) is not able to reset the network core, and we're still investigating why that is.

Best regards,

Simon

RE: nRF5340 debug network core

Simonr — Fri, 16 Apr 2021 09:46:18 GMT

I thought I would be able to get back to you by the end of this week with something useful, but unfortunately I haven't heard back from the devs yet, so that doesn't seem to be the case. I'll keep pinging them, but I can't guarantee when I'll have some more information for you. Sorry about the delays on this case.

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Mon, 12 Apr 2021 13:53:52 GMT

Hi Simon,

I have tried to take the code from the remoteproc_mgr_boot function and place it in the beginning of SystemInit located in system_nrf5340_application.c

It still does not allow me to debug the net core...

RE: nRF5340 debug network core

Simonr — Mon, 12 Apr 2021 12:25:18 GMT

Hi again Christoffer

It's rather limited, but this is what I got for now. You can try moving the network startup earlier in the Zephyr boot process by running remoteproc_mgr_boot from here: https://github.com/zephyrproject-rtos/zephyr/blob/d06b8053b3677bf2c5c6cb39ff744606ecdb8bc6/boards/arm/nrf5340dk_nrf5340/nrf5340_cpunet_reset.c

You can try adding those lines into SystemInit instead, so that it will run as soon as possible.

Best regards,

Simon

RE: nRF5340 debug network core

Simonr — Thu, 08 Apr 2021 06:00:24 GMT

I'm sorry, but we've been somewhat stuck on this, and it was put on pause due to the Easter vacation. We've been able to recreate this issue in both PDKs and nRF5340 DKs, and the workaround seems to be moving the network core startup point earlier in the Zephyr boot process, and we're looking into how the Segger IDE does this.

I have pinged the devs again, so hopefully I'll hear back from them soon. Thank you for your patience!

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Wed, 07 Apr 2021 06:00:30 GMT

Any news?

RE: nRF5340 debug network core

Simonr — Wed, 17 Mar 2021 11:31:19 GMT

Hi again

I'm sorry about the delays, but I haven't been able to confirm how it's done in the SEGGER IDE yet, but it does indeed seem to be due to the network core being enabled too late after some testing with Visual Studio on our end. I'll get back to you with more details on how to edit this.

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Mon, 15 Mar 2021 09:23:39 GMT

Okay that was also what I thought would be the problem. How is this handled in Segger IDE? I have also looked at the following tutorial (link) to see if I could get the gdb commands. It looks like they don't reset the network core and link the app and net core together and flash both cores when launching the application project.

RE: nRF5340 debug network core

Simonr — Mon, 15 Mar 2021 08:45:26 GMT

I'm sorry, but it's taking some time to get to the bottom of this issue. One possible problem is that resetting the network core also resets the app core, which in turn shuts off the network core, only letting you come back once the app core has booted. If the time from startup to NET core enable is too long, you also might have some issues with the debugger timing out/detecting that the NET core is disabled.

In order to get it to debug from start it might be necessary to move the network core startup point earlier in the Zephyr boot process.

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Mon, 08 Mar 2021 12:16:20 GMT

I have been able to fix the reedback protection. system_nrf5340_application.c and system_nrf5340_network.c was missing nrf53_handle_approtect(). However I have still not found a way to debug the network core from the beginning.

RE: nRF5340 debug network core

Simonr — Mon, 08 Mar 2021 10:13:51 GMT

This is because the app core works differently than the NET core. Only the NET core auto-locks when a debug connection is lost.

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Mon, 08 Mar 2021 08:56:52 GMT

Simonr I tried to play with the empty app core project, ignoring the network core, and it seems like it is able to reset without reenabling readback protection. The big question is why does it work? Looking at the hex file, address 0x00FF8000 is not included.

RE: nRF5340 debug network core

Simonr — Mon, 08 Mar 2021 08:34:59 GMT

Currently waiting for some input from our SW team. There may be some KConfig stuff on top of the MDK that interacts with this. Awaiting confirmation/ more input, and will get back to you as soon as I know something. Thank you for your patience!

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Mon, 08 Mar 2021 07:14:38 GMT

Simonr Any progress? I have tried to set the register at compile time without any success.

RE: nRF5340 debug network core

Christoffer Brask — Thu, 04 Mar 2021 14:28:23 GMT

It is v.0.11.0

RE: nRF5340 debug network core

Simonr — Thu, 04 Mar 2021 14:24:46 GMT

Then it looks like the HW path is unlocked, and these macros shouldn't be necessary. I'm currently awaiting more input from our developers on this. Can you please confirm which version of the nRF5340 you're working with? I have assumed all along that it is an nRF5340 DK (v0.11.0).

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Wed, 03 Mar 2021 14:42:47 GMT

0x01FF8000: FA 50 FA 50 FF FF FF FF FF FF FF FF FF FF FF FF

I see that unprotected is 0x50FA50FA. Do you think this has something to do with endianess?

I don't find any macros for ENABLE_APPROTECT and ENABLE_APPROTECT_USER_HANDLING.

RE: nRF5340 debug network core

Simonr — Wed, 03 Mar 2021 12:44:41 GMT

Okay, looks like your network application isn't correctly handling the hardened AP protection then. After programming your application, could you check the value of NET_UICR->APPROTECT? This should be 0x01FF8000. This value will be used by the systeminit code to set up ap protection unless ENABLE_APPROTECT or ENABLE_APPROTECT_USER_HANDLING c macros are set.

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Tue, 02 Mar 2021 13:59:15 GMT

After recover: 0x01000000: 21010000 |...!|

After app flash: 0x01000000: 21010000 |...!|

After net flash: 0x01000000: 21010000 |...!|

After reset button: ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.

RE: nRF5340 debug network core

Simonr — Tue, 02 Mar 2021 13:49:35 GMT

Okay, the empty_app_core project should not cause any problems. Could you check if the network core is protected? This nrfjprog command should give you an inidication.

nrfjprog --memrd 0x01000000 --coprocessor CP_NETWORK

Please let me know what that returns.

I think there should be a more standard way to debug the network core, but I'll have to double check with my colleagues. I'll get back to you.

Best regards,

Simon

RE: nRF5340 debug network core

Christoffer Brask — Tue, 02 Mar 2021 10:51:01 GMT

I haven't changed the empty_app_core project. Do the SDK have a way to handle this, such that it is not reenabled after the device is reset?

I have observed the following:

After recovery, I can reflash the APP core as many times as I want until I manually do a reset on the button or remove the power. (nrfjprog --reset is used).

I can reflash the NET core as many times as i want until i manually do a reset, however the app core needs to be flashed once before I can flash the NET core without getting an error with readback protection.

Yesterday I found a way to attach a debug session to the network core by using the following procedure.

1) Recover device to remove app protection

2) Build, flash and reset app core

3) Build, flash and reset net core

4) Start debugging with attach to network core.

This is however still not ideal, as i can't observe the start up and restart the debug session without going through all the steps again.