Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

RE: Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

Hieu — Mon, 16 Dec 2024 11:53:32 GMT

Hi,

[quote user="Ben_Squar3d"]I don't get it sorry.[/quote]

Oh, I meant I misunderstood the origin of the issue when I read your opening post. It's nothing important now.

[quote user="Ben_Squar3d"]While it is possible to to so with nrf52, it is not easily possible with nrf53 it seems, so we'll stick to the workaround we have.[/quote]

Right. This approach does seem like too much for debugging, if you have a different workaround.

I will close this ticket then. If you have further questions on the topic, please feel free to reopen it any time.

Best regards,

Hieu

RE: Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

Ben_Squar3d — Mon, 16 Dec 2024 10:54:38 GMT

Hi,

Thank you for your answer. It seems a bit too complicated indeed.

We managed to use additionnal timers instead of looking for the missing event.

[quote userid="9456" url="~/f/nordic-q-a/117124/alternative-of-radio-notifications-api-in-ncs-2-7-0-with-nrf5340-cpuapp/515013"]Finally, I first read your opening post as you were using Radio Notification is 2.6.1, but it was removed in 2.7.0. I have seen now that isn't the case. Do you need Radio Notification or something like that for a new issue? If so, there might be other approaches as well.[/quote]

I don't get it sorry. We were working with nrf52 + ncs<2.70 at first and when migrating to ncs 2.7.0, we were using additionnal timers to workaround the missing event. This introduces new issues and the right fix would have been to retrive the event again. While it is possible to to so with nrf52, it is not easily possible with nrf53 it seems, so we'll stick to the workaround we have. Thank you for your answers

Best regards

RE: Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

Hieu — Mon, 16 Dec 2024 03:51:15 GMT

Hi,

The netcore image is automatically built, but you have access to its source code. It is the hci_ipc "sample" in the Zephyr part of the SDK.

You should be able to add your own sequence of functions to setup a DPPI channel connecting the RADIO events to IPC tasks early in the main function. You should use nrfx drivers for this, so that new channels are allocated, and the drivers have knowledge of the channel. This way, if other parts of the SDK are using DPPI or IPC, they won't get affected.

With NCS 2.7.0, sysbuild is supported, so it becomes even easier for you to maintain your own copy of hci_ipc, and just reconfigure the project so that the remote target is now the modified copy of hci_ipc instead.
In NCS 2.8.0 and 2.9.0, sysbuild support is even more mature. If you are committed to using sysbuild, you should consider moving to 2.9.0.
The complicated part with this is that you will need to understand the "automatic" build of hci_ipc enough to replicate it.

On the other hand, learning to do all that isn't trivial. I honestly have only done slightly similar things enough to know it is theoretically possible but haven't tried it myself.

What do you need the Radio Notification for? If it's only for debugging, then perhaps just modify the original hci_ipc sample directly is a better approach. Later, you can just discard all your changes with git.

Finally, I first read your opening post as you were using Radio Notification is 2.6.1, but it was removed in 2.7.0. I have seen now that isn't the case. Do you need Radio Notification or something like that for a new issue? If so, there might be other approaches as well.

RE: Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

Ben_Squar3d — Fri, 13 Dec 2024 10:11:33 GMT

Hi,

Thank you for trying.

[quote userid="9456" url="~/f/nordic-q-a/117124/alternative-of-radio-notifications-api-in-ncs-2-7-0-with-nrf5340-cpuapp/514773"]That however does still require firmware setup on cpunet. Is this possible in your setup?[/quote]

Difficult to say from the knowledge I have. For now, I didn't work with cpunet, only cpu app and sysbuild. The cpunet image is automatically generated. What setup make it possible to tweak cpunet?

RE: Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

Hieu — Thu, 12 Dec 2024 14:38:49 GMT

Hi,

My apology, I missed the fact that the Radio Test sample is solely on cpunet.

It should be possible to setup DPPI to connect an event from one core to a task in the other via IPC in between. I can try to work up a proof of concept if I cannot find one already done somewhere, though that might take some time.
That however does still require firmware setup on cpunet. Is this possible in your setup?

RE: Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

Ben_Squar3d — Wed, 11 Dec 2024 08:31:16 GMT

Hi,

Thank you for these example. However, the radio test sample is meant to be build for the cpunet, that have access to NRF_RADIO register. Do you confirm I can't access this register with cpuapp ? If so, what is the alternative to be able to catch NRF_RADIO_EVENT_END event or equivalent with ncs2.7.0 and nrf5340 cpuapp?

Thank you for your help.

RE: Alternative of radio notifications API in NCS 2.7.0 with nrf5340 cpuapp

Hieu — Tue, 10 Dec 2024 05:22:35 GMT

Hi Ben_Squar3d,

On the nRF5340, you can use the DPPI peripheral to connect events between the two cores.

This is demonstrated in the nrfx_gppi driver sample (it is compatible with both PPI, DPPI, and nRF54's GPPI).
It is also used in the Radio Test sample.

Note that there is a difference with the DPPI, in that each EVENT source or TASK sink can only connect to one DPPI channel; compared to the PPI on nRF52 SoCs, where each EVENT or TASK can be connected to multiple PPI channels.

Hieu