Migration from nRF24 to nRF5x

RE: Migration from nRF24 to nRF5x

Kenneth — Wed, 23 Nov 2022 10:40:36 GMT

[quote user="mej7000"]Therefore
pipe0's address = {0xE7, 0xE7, 0xE7, 0xE7,0xE7};
pipe1's address: = {0xC2, 0xC2, 0xC2, 0xC2,0xC2};
pipe2's address: = {0xC2, 0xC2, 0xC2, 0xC2,0xC3};
...
pipe7's address: = {0xC2, 0xC2, 0xC2, 0xC2,0xC8};[/quote]

Correct.

[quote user="mej7000"]In the example I can't find a line which sets the address length. Am I missing something or is there a default assumed that I can’t find?[/quote]

It can be controlled by calling esb_set_address_length(), I can see default values are in esb.c:

/* Default address configuration for ESB.

* Roughly equal to the nRF24Lxx defaults, except for the number of pipes,

* because more pipes are supported.

__ALIGN(4)

static struct esb_address esb_addr = {

.base_addr_p0 = {0xE7, 0xE7, 0xE7, 0xE7},

.base_addr_p1 = {0xC2, 0xC2, 0xC2, 0xC2},

.pipe_prefixes = {0xE7, 0xC2, 0xC3, 0xC4, 0xC5, 0xC6, 0xC7, 0xC8},

.addr_length = 5,

.num_pipes = CONFIG_ESB_PIPE_COUNT,

.rf_channel = 2,

.rx_pipes_enabled = 0xFF

};

[quote user="mej7000"] Is that general advice moving forward[/quote]

nRF Connect SDK (NCS) is the recommended SDK moving forward yes, I can see you have initially chosen to download the nRF5 SDK which is no longer recommended for new designs. Unfortunately our web page is not fully up to date, so it's easy mistake to download the old nRF5 SDK for development.

[quote user="mej7000"]Channel. I also don't see nrf_esb_set_rf_channel() in the example code. It isn't clear to me what values are acceptable. Is it the full channel (2440) or just the 40 or something else?[/quote]

See the following struct for a description of the rc_channel:

/* Enhanced ShockBurst address.

* Enhanced ShockBurst addresses consist of a base address and a prefix

* that is unique for each pipe. See @ref esb_addressing in the ESB user

* guide for more information.

struct esb_address {

uint8_t base_addr_p0[4]; /* Base address for pipe 0, in big endian. */

uint8_t base_addr_p1[4]; /* Base address for pipe 1-7, in big endian. */

uint8_t pipe_prefixes[8]; /* Address prefix for pipe 0 to 7. */

uint8_t num_pipes; /* Number of pipes available. */

uint8_t addr_length; /* Length of the address plus the prefix. */

uint8_t rx_pipes_enabled; /* Bitfield for enabled pipes. */

uint8_t rf_channel; /* Channel to use (between 0 and 100). */

};

The radio support 0 to 100, however radio regulations limit the channels to 2 to 81.

Kenneth

RE: Migration from nRF24 to nRF5x

mej7000 — Tue, 22 Nov 2022 18:27:11 GMT

Thanks Kenneth, I think I am getting a handle on this. Can you elaborate more on the base addresses and the prefix. I had read the documentation, but it still leaves me with questions. I could probably experiment and get it to work, but I would like to understand it better.

Does it mean that 1 byte is taken from the addr_prefix[8] array, but the particular byte to be appended is determined by the Pipe(0-7) that is being initialized?

uint8_t base_addr_0[4] = {0xE7, 0xE7, 0xE7, 0xE7};
uint8_t base_addr_1[4] = {0xC2, 0xC2, 0xC2, 0xC2};
uint8_t addr_prefix[8] = {0xE7, 0xC2, 0xC3, 0xC4, 0xC5, 0xC6, 0xC7, 0xC8 };

Therefore
pipe0's address = {0xE7, 0xE7, 0xE7, 0xE7,0xE7};
pipe1's address: = {0xC2, 0xC2, 0xC2, 0xC2,0xC2};
pipe2's address: = {0xC2, 0xC2, 0xC2, 0xC2,0xC3};
...
pipe7's address: = {0xC2, 0xC2, 0xC2, 0xC2,0xC8};
In the example I can't find a line which sets the address length. Am I missing something or is there a default assumed that I can’t find? I expected to see something like this in the example:

err_code = nrf_esb_set_address_length(5);
Regarding the nRF Connect SDK (NCS). I thought I was using that already. Is that general advice moving forward or do you see something in my question that leads you to believe I'm not using the right thing ?(which is very possible)
Channel. I also don't see nrf_esb_set_rf_channel() in the example code. It isn't clear to me what values are acceptable. Is it the full channel (2440) or just the 40 or something else?

Here is my transmitter (ESP32/Arduino IDE) setup:

/************************************************************************
18:10:18.093 -> SPI Frequency = 10 Mhz
18:10:18.093 -> Channel = 40 (~ 2440 MHz)
18:10:18.093 -> RF Data Rate = 1 MBPS
18:10:18.093 -> RF Power Amplifier = PA_LOW
18:10:18.093 -> RF Low Noise Amplifier = Enabled
18:10:18.127 -> CRC Length = 8 bits
18:10:18.127 -> Address Length = 5 bytes
18:10:18.127 -> Static Payload Length = 32 bytes
18:10:18.127 -> Auto Retry Delay = 1500 microseconds
18:10:18.127 -> Auto Retry Attempts = 15 maximum
18:10:18.127 -> Packets lost on
18:10:18.127 -> current channel = 0
18:10:18.127 -> Retry attempts made for
18:10:18.127 -> last transmission = 15
18:10:18.127 -> Multicast = Disabled
18:10:18.127 -> Custom ACK Payload = Disabled
18:10:18.127 -> Dynamic Payloads = Disabled
18:10:18.127 -> Auto Acknowledgment = Disabled
18:10:18.127 -> Primary Mode = TX
18:10:18.160 -> TX address = 0xc2c2c2c2c2
18:10:18.160 -> pipe 0 ( open ) bound = 0xc2c2c2c2c2
18:10:18.160 -> pipe 1 ( open ) bound = 0xe7e7e7e7e7
18:10:18.160 -> pipe 2 (closed) bound = 0xc3
18:10:18.160 -> pipe 3 (closed) bound = 0xc4
18:10:18.160 -> pipe 4 (closed) bound = 0xc5
18:10:18.160 -> pipe 5 (closed) bound = 0xc6
*************************************************************************/

---

Hello,

The prefix is always required yes, see:
https://infocenter.nordicsemi.com/topic/ps_nrf52840/radio.html#concept_mdy_kcj_4r

For all new development you should use the nRF Connect SDK (NCS), see:
nRF Connect SDK and nRF5 SDK statement

To get started with NCS check out:
https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

The nRF Connect SDK is using the zephyr RTOS. ESB is also supported in NCS:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_esb.html#

Kenneth

RE: Migration from nRF24 to nRF5x

Kenneth — Tue, 22 Nov 2022 12:09:23 GMT

Hello,

1. The prefix is always required yes, see:
https://infocenter.nordicsemi.com/topic/ps_nrf52840/radio.html#concept_mdy_kcj_4r

2. Correct, 250kbps not supported.

3. For all new development you should use the nRF Connect SDK (NCS), see:
nRF Connect SDK and nRF5 SDK statement

To get started with NCS check out:
https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

The nRF Connect SDK is using the zephyr RTOS. ESB is also supported in NCS:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_esb.html#

4. You can find an overview of the different nRF52-variants here:
https://infocenter.nordicsemi.com/topic/struct_nrf52/struct/nrf52.html

Typically there is no problem to use the nRF52840-DK for development, and later to swap to a different nRF52 variant if you find that you don't use all the ram, flash and features that is available in the nRF52840 in specific. The only thing you need to do is then to update the possible gpios you are using and build for the target nRF52-variant you intend to use.

Kenneth