Gazell for nRF5340

RE: Gazell for nRF5340

ovrebekk — Mon, 27 May 2024 08:10:50 GMT

Hi Petri

Good to hear that you can use ESB as an alternative. The best of luck with your project 🙂

Best regards
Torbjørn

RE: Gazell for nRF5340

Petri Haavisto — Sat, 25 May 2024 02:23:01 GMT

Hi,

ESB looks quite suitable for my purposes and I will try that!

This is clear now. Thanks!

Best regards,

Petri

RE: Gazell for nRF5340

ovrebekk — Thu, 23 May 2024 10:53:54 GMT

Hi Petri

I did some digging internally, and it seems there was an attempt at some point to patch the gzll_glue layer to support the nRF5340, but this wasn't followed up properly and as such was never merged into the official repositories. At the moment there doesn't seem to be any plans to properly support Gazell in the nRF5340.

As an alternative, have you had a look at the ESB library?

ESB is essentially the lower layer protocol upon which Gazell is based, and supports the same type of addressing, ACK, ACK payload and retransmit mechanism. What it doesn't support is frequency jumping and device/host synchronization, and this would have to be added yourself if you need it. There is no proper pairing and encryption library for ESB either, like there is for Gazell.

The upside of using ESB is that you have more flexibility with regards to the payload length and packet timing, and you also have full access to the source code in case you want to make changes to the underlying protocol.

In addition to the official ESB PTX and PRX samples in the SDK you might also want to have a look at the sample below, which shows how ESB can be run in parallel with BLE using MPSL and timeslots, and also shows how you can establish communication between the appcore and netcore in order to have the ESB communication triggered from the appcore (the ESB code itself will always have to run on the netcore):
https://github.com/too1/ncs-esb-ble-mpsl-demo

Best regards
Torbjørn

RE: Gazell for nRF5340

Petri Haavisto — Wed, 22 May 2024 15:56:32 GMT

Thank you!

If Gazell on nRF5340 is not happening I would be grateful of any tips about alternative *equally simple* 2.4GHz radio solutions (not BLE) that might exist as samples for nRF5340. For example, if there would exist some simple proprietary protocol for exchanging data packets with acknowledgement.

Petri

RE: Gazell for nRF5340

ovrebekk — Wed, 22 May 2024 13:42:09 GMT

Hi Petri

I tried building it myself and see the same issue. It seems there is a lib provided for the nRF5340 netcore, but the gzll_glue layer does not support DPPI, which is required by the nRF5340.

I will do some digging internally and try to figure out what the plans are for supporting Gazell in the nRF5340 properly.

Best regards
Torbjørn

RE: Gazell for nRF5340

Petri Haavisto — Tue, 21 May 2024 14:01:37 GMT

I am not able to post the output. It is probably too long. Here are some key snippets. I have edited most of the output away.

---

Executing task: nRF Connect: Generate config nrf5340dk_nrf5340_cpunet for c:\Code\foo\radio_char\gzll_ack_payload_hos

-- Found BOARD.dts: C:/ncs/v2.6.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet.dts

-- Zephyr version: 3.5.99 (C:/ncs/v2.6.1/zephyr), build: v3.5.99-ncs1-1
[131/139] Building C object modules/nrf/subsys/gazell/CMakeFiles/..__nrf__subsys__gazell.dir/gzll_glue.c.obj
FAILED: modules/nrf/subsys/gazell/CMakeFiles/..__nrf__subsys__gazell.dir/gzll_glue.c.obj

In file included from C:/ncs/v2.6.1/modules/hal/nordic/nrfx/drivers/include/nrfx_ppi.h:38,from C:/ncs/v2.6.1/nrf/subsys/gazell/gzll_glue.c:14:
C:/ncs/v2.6.1/modules/hal/nordic/nrfx/hal/nrf_ppi.h:54:25: error: 'PPI_CHEN_CH0_Pos' undeclared here (not in a function); did you mean 'DPPIC_CHEN_CH0_Pos'?
54 | NRF_PPI_CHANNEL0 = PPI_CHEN_CH0_Pos, /**< Channel 0. */

[And then a lot of similar "undeclared" errors.]

* The terminal process terminated with exit code: 1.

RE: Gazell for nRF5340

Petri Haavisto — Tue, 21 May 2024 13:47:30 GMT

Hi,

I am building for the network core (target nrf5340dk_nrf5340_cpunet).

I am attaching the build output from VS Code extension below (I did not find a way to make an attachment so the text is pasted at the end of this message). It has a bunch of gcc errors due to PPI vs DPPI which is already in compilation, apparently due to nRF5340 being different in this respect. I don't know if there would be some other problems later also since the build stops at these gcc errors.

Petri

RE: Gazell for nRF5340

ovrebekk — Tue, 21 May 2024 11:59:05 GMT

Hi Petri

Did you try to build for the network core or the application core?

The radio is only available from the network core, and you need to build the Gazell application for this core specifically.

Best regards
Torbjørn