esb, shockburst, running on nrf5340dk's

[mej7000]

I have 3 nrf boards connected. 2x nrf52832 and 1x nrf5340.

esb_tx is running on nrf52832(682782977)
esb_rx is running on nrf52832(682497942) & nrf5340(1050025410)

west build -b nrf5340dk_nrf5340_cpunet -p builds correctly and flashes without error

PS C:\nrf\esb_prx> west flash -d build_1
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner nrfjprog
There are multiple boards connected.
1. 1050025410
2. 682782977
Please select one with desired serial number (1-2): 1
-- runners.nrfjprog: Flashing file: build_1\zephyr\zephyr.hex
[ #################### ] 2.055s | Erase file - Done erasing
[ #################### ] 0.243s | Program file - Done programming
[ #################### ] 0.243s | Verify file - Done verifying
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050025410 flashed successfully.

esb_rx is working on the nrf52, but not on the nrf53.

... To be through, I powered down esb_tx_nrf52832(682782977) and flashed another nrf5340dk(1050077823) and programmed it to be esb_tx:

PS C:\nrf\esb_ptx> west flash -d build_1
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner nrfjprog
There are multiple boards connected.
1. 1050025410
2. 1050077823
3. 682497942
Please select one with desired serial number (1-3): 2
-- runners.nrfjprog: Flashing file: build_1\zephyr\zephyr.hex
[ #################### ] 2.044s | Erase file - Done erasing
[ #################### ] 0.235s | Program file - Done programming
[ #################### ] 0.236s | Verify file - Done verifying
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050077823 flashed successfully.

Although 1050077823 (nrf5340-esb_tx) flashed correctly. Blinky continues to run (as it already had) on nrf5340-esb_tx, which probably makes sense, but I'm not getting any kind of esb response from either (nrf52832 or nrf5340) esb-rx.

There is something I am not understanding about how to flash to nrf5340_CPUNET? Maybe it's flashing correctly, but esb needs to be called from CPUAPP to start it working?? I'm close, but missing something...

Ultimately the goal is to have a network of nrf5340's in a Star configuration. I see that there is shared memory between CPUAPP and CPUNET. I assume somehow it's used to pass data from CPUAPP to CPUNET for transmission/reception. I don't exactly understand how that works either, but I figure the first step is to get the esb Sample to work on nrf5340dk's without modification. But, if there are additional samples that target this use case I would be interested in reviewing those too.

The final configuration goal is to have the center of the star network also be running BLE-UART (so the central esb in the Star Network will relay the esb data from the nodes to a BLE app). I am assuming that there is no problem running both esb and BLE at the same time.

esb_prx_ptx.zip

[ovrebekk]

Hi Mike

The UART async adapter is an optional module that you only need if you are planning to use a CDC ACM (USB) comport, it is not necessary if you are using a physical UART. You can read more here. In other words I would just remove this altogether if you don't actually need it. 

The set ballback function typically fails when the UART ASYNC API is not properly enabled. Are you sure that CONFIG_UART_ASYNC_API is properly enabled in the configuration? 

Is it the PTX sample, PRX sample or both that you are struggling with? 

Best regards
Torbjørn

[mej7000]

Hi, It's the PRX. I'm focusing on getting the BLE UART working at this point.

[00:00:00.000,518] <inf> main: ESB PRX BLE Multiprotocol Example
[00:00:00.000,518] <inf> peripheral_uart: Initialize Bluetooth UART
[00:00:00.000,823] <err> peripheral_uart: Cannot initialize UART callback

CONFIG_UART_ASYNC_API=y is set in the prj.conf file and everything compiles without error.

CONFIG_BT_NUS_UART_ASYNC_ADAPTER wasn't in the prj.conf file, so it looks like it's not being used anyway. Enabling CONFIG_BT_NUS_UART_ASYNC_ADAPTER=y, caused a compile error so I took that out. It doesn't look like it's enabled in the peripheral_uart sample either. I tried taking the file out completely, but that didn't make a difference.

	if (IS_ENABLED(CONFIG_BT_NUS_UART_ASYNC_ADAPTER) && !uart_test_async_api(uart)) {
		/* Implement API adapter */
		uart_async_adapter_init(async_adapter, uart);
		uart = async_adapter;
	}

Peripheral_uart sample works as a standalone. At this point I think everything from the peripheral_uart sample has been incorporated, unchanged, into the demo. The Demo compiles fully, but there still seems to be something in the way I combined it with the demo that is causing "Cannot initialize UART callback". But since there are no errors I don't know what to change or where to look?

I attached the code. It builds fine for 52832 or 52840.

ncs-esb-ble-mpsl-demo-per-uart (2).zip

[ovrebekk]

Hi Mike

I am taking an early weekend so I won't have time to look into this today unfortunately. I will test your code on Monday and see if I can spot the issue. 

As a side note, the only real difference between the LBS service used in my sample and the NUS service is that the former configures the characteristics as 1 byte length while the later uses variable length characteristics. You could quite easily configure one to be similar to the other.

Do you actually need the UART functionality from the peripheral_uart example, or is it only the BLE functionality that you want to use? 
If yes, couldn't you just remove all the UART related code from the app_bt_uart module? 

The way I like to structure these examples is to have the app_bt_xxx modules handle Bluetooth related functionalities only. Any code interfacing sensors or other interfaces should run either from main.c, or from another module. 

Best regards
Torbjørn

[mej7000]

Hi, Thanks. Enjoy the weekend!

You are correct in that all I really want to do is pass a ~64 byte length to/from BLE (and relay those 64byes to/from shockburst). I had considered adapting bt_lbs, but initially thought incorporating peripheral_uart would be easier... I'll look at adapting bt_lbs.

In the meantime I've determined that either one of these settings prevent the callback function working correctly. Commenting out both of those and BLE UART works as expected, but I am unsure of why they're a problem.

CONFIG_CONSOLE_HANDLER=y
CONFIG_CONSOLE_GETCHAR=y

*** Booting nRF Connect SDK v2.5.1 ***
[00:00:00.000,518] <inf> main: ESB PRX BLE Multiprotocol Example
[00:00:00.000,549] <inf> peripheral_uart: Initialize Bluetooth UART
[00:00:00.000,854] <err> peripheral_uart: Cannot initialize UART callback

ncs-esb-ble-mpsl-demo-per-uart (3).zip

[ovrebekk]

Hi Mike

Good to hear that you got it working

I can see that the CONSOLE_HANDLER configuration selects (enables) the interrupt driven driver here. I assume this is why it prevents the async based code from working properly. 

Best regards
Torbjørn