Simplest nRF53 dual-core ESB communication?

RE: Simplest nRF53 dual-core ESB communication?

AMarch01 — Mon, 17 Feb 2025 15:57:48 GMT

I didn't want to pollute your new request in case there are examples.
This case seems to indicate that you should just be able to access the device directly, with some additional notes on switching pin control.
nRF5340 Shared Peripherals between APP and NET cores - Nordic Q&A - Nordic DevZone - Nordic DevZone

This coincides with the function network_gpio_allow(void) in the empty_app_core project.

If directly accessing the device causes a fault, then maybe something like the following needs to be added to the network_gpio_allow() function, but I haven't tested it.

NRF_DCNF_S->EXTPERI[dev id].PROTECT=0x0;

RE: Simplest nRF53 dual-core ESB communication?

Sigurd — Fri, 14 Feb 2025 10:27:04 GMT

Hi!

You might find this example useful:

https://github.com/too1/ncs-esb-ble-mpsl-demo

It's using MPSL timeslots, so if you don't need BLE, only ESB , it can be simplified a bit.
It's based on nRF Connect SDK v2.6.0, but how the communication between the cores works, etc, also works for nRF Connect SDK v2.9.0

RE: Simplest nRF53 dual-core ESB communication?

AMarch01 — Thu, 13 Feb 2025 14:07:20 GMT

I took a look at the old SDK (1,17). I did see some setup functions for the SPU, but they don't have a lot of detail in them. They don't seem to indicate any way of changing the domain of access for the peripherals in question.
Did you make any headway? Perhaps you made a private query direct to Nordic?

If you have not looked at the old SDK and are curious what I was looking at, this is the file.
nRF5_SDK_17.1.0_ddde560\modules\nrfx\hal\nrf_spu.h

ugh... nevermind... same (or similar) file is in the nrf connect sdk as well.
Sorry to bother you.

RE: Simplest nRF53 dual-core ESB communication?

AMarch01 — Tue, 11 Feb 2025 14:31:30 GMT

I know one thing, I was just playing around with a simple ESB project on the nrf53... I couldn't get serial output. Turns out I needed to load the empty_app_core sample into the application core, then the net core could communicate with the outside world. I wasn't using the sysbuild thing I believe, but I just wanted what I had to work.

RE: Simplest nRF53 dual-core ESB communication?

AMarch01 — Mon, 10 Feb 2025 15:45:10 GMT

I was going through the ipc_service example to attempt to help you out because your candor suggested kindred spirt. It wasn't working for me, so I decided to "edgemecate" myself on sysbuild to figure out why the example wasn't working... then attempting to run through devacadamy to get a clue on sysbuild ...
Finally realized I was at work and this wasn't a priority for me ... but ...you know the saying "the thought that counts?" or in my case the road to hell is paved with good intentions.

Glad you learned something and thanks for your description. I hope you can move forward from here.
A M

RE: Simplest nRF53 dual-core ESB communication?

WesC — Fri, 07 Feb 2025 20:32:22 GMT

Take a look at this
https://github.com/droidecahedron/IPC_static_vring_bidir
this Send messages between two cores using the IPC service and static vrings backend.

It is designed to demonstrate how to integrate it with Zephyr both from a build perspective and code. There is an extra ipc instance that sends data back from one core to the other, highlighting that you swap the return path.