nRF5340 simultaneously debugging on application and network cores

RE: nRF5340 simultaneously debugging on application and network cores

kpreiss — Fri, 29 Oct 2021 15:41:03 GMT

Ok, will it work with Segger Embedded Studio?

RE: nRF5340 simultaneously debugging on application and network cores

Marte Myrvold — Fri, 29 Oct 2021 11:09:16 GMT

Hi,

After my initial testing I see the same as you. It works once in a while, but most of the time I get error.

Debugging multi-core applications is not a feature of the VS Code extension yet, but I will add this as a feature request to the VS Code team.

In the meantime, debugging both cores can be achieved using a compound debug configuration as discussed here: https://github.com/Marus/cortex-debug/issues/404#issuecomment-888594384.

Best regards,

Marte

RE: nRF5340 simultaneously debugging on application and network cores

kpreiss — Wed, 27 Oct 2021 14:43:53 GMT

RE: nRF5340 simultaneously debugging on application and network cores

kpreiss — Wed, 27 Oct 2021 14:43:38 GMT

I cannot even connect to the application core again. I get the following error message when attempting to debug the app core after erasing and flashing....

RE: nRF5340 simultaneously debugging on application and network cores

kpreiss — Wed, 27 Oct 2021 13:47:21 GMT

can you try disconnecting from both debug sessions, then reconnecting? I got it to work ONCE after starting vscode, erase and flashing, then debugging. However, once I stop the debug sessions then try to restart, it doesn't work.....

RE: nRF5340 simultaneously debugging on application and network cores

Marte Myrvold — Wed, 27 Oct 2021 13:22:57 GMT

Hi,

Yes, I opened two VS Code windows and used one for the Beacon sample on the application core, and the other for the RPC Host sample on the network core.

Best regards,

Marte

RE: nRF5340 simultaneously debugging on application and network cores

kpreiss — Wed, 27 Oct 2021 12:35:05 GMT

Yes, I did do this. Are you launching two instances of VSCode to debug?

RE: nRF5340 simultaneously debugging on application and network cores

Marte Myrvold — Wed, 27 Oct 2021 09:23:14 GMT

Hi,

Did you specify that the nRF RPC Host sample should be the child image of the Beacon sample when creating the build configuration in VS Code? If not, the HCI RPMsg sample will become the child image of the sample. In multi-image builds, VS Code automatically programs the child images as well as the main image, so this would cause the HCI RPMsg sample to be programmed on the network core when you select that you want to debug the Beacon sample.

You can specify that the nRF RPC Host should be the child image by adding this as an Extra Cmake argument when creating the build configuration:

-DCONFIG_BT_RPC=y

Using this, I was able to debug both cores and test the application by first starting the debug session on the application core, then the debug session on the network core.

Best regards,

Marte

RE: nRF5340 simultaneously debugging on application and network cores

Marte Myrvold — Tue, 26 Oct 2021 13:43:12 GMT

Hi,

I am still investigating this issue. I will come back to you tomorrow.

Best regards,

Marte

RE: nRF5340 simultaneously debugging on application and network cores

kpreiss — Mon, 25 Oct 2021 14:20:46 GMT

Yes, the SIGTRAP error stops the program from running and the development board does not advertise. I have not tried other samples. I was trying to use the rpc_host functionality on the network core and it appears only a few samples support this feature. The beacon sample being one of them.

RE: nRF5340 simultaneously debugging on application and network cores

Marte Myrvold — Mon, 25 Oct 2021 13:29:53 GMT

Hi Kurt,

Does the SIGTRAP error stop your program for running? Is the device still advertising the Eddystone URL, or has it halted completely? Do you only see this with the Beacon sample, or do you see the same behavior with other samples as well?

Best regards,

Marte