Running micro-ESB concurrently with BLE

RE: Running micro-ESB concurrently with BLE

lbe — Wed, 18 Sep 2019 13:40:56 GMT

Hello everyone, I seem to have issues in making this work on NRF52832 DK, with SDK 15.0.0, running S132 v6.

The BLE part works fine, with the uart strings sent back and forth to a smartphone running the NRF toolbox.

As for the ESB part, I am not able to see any transmission.....as far as I understand from the description of the code, it is supposed to print something when the string is transmitted, but I don't see anything neithter on the transmitting side nor on the receiving side.

I read the commend of Manhdv below, but I never see error codes like NRF_ERROR_BUSY.....it just seems to me that the ESB simply never detects the strings from the uart terminal.

Any clue? I am running the original code found in the github, just modifiy the "include softdevice_handler.h" with "include nrf_sdh.h".

Thanks if advance.

RE: Running micro-ESB concurrently with BLE

Manhdv — Fri, 12 Oct 2018 10:50:54 GMT

I tested this timeslot api (code on github) with nrf52 (SDK15.1.0, softdevice s132 v6.1.0) and here are some notes for anyone wanna do the same:

- in function TIMESLOT_END_IRQHandler and TIMESLOT_END_IRQHandler, when you try to init, set base address or stop rx, disable esb module, you will receive some error codes like: NRF_ERROR_BUSY, you should handle these errors instead of using APP_ERROR_CHECK to prevent your app run in to reset, for example just bypass current timeslot and wait to the next timeslot.

- I use another board to transmit a RF package every 500ms, after few hours the RX board will run into an error: SOFTDEVICE: INVALID MEMORY ACCESS, sub-region 0x02 (illegal write access to the radio module). That's because the UESB_RX_HANDLE_IRQHandler did call outside of time slot. When reading the payload, function uesb_read_rx_payload(&payload); will try to disable radio interrupt, but the softdevice already take access to the radio module.

To fix this, I take the payload in function nrf_esb_event_handler when I receive event RX (tested), or may be change the priority UESB_RX_HANDLE_IRQPriority to 1 can fix it (not tested yet).

RE: Running micro-ESB concurrently with BLE

Darrew — Thu, 21 Jun 2018 08:59:49 GMT

According to the SoftDevice Specification (e.g. S130 v2.0):
"Important: To ensure reliable usage of the SoftDevice you must use the wrapper functions (i.e. sd_nvic_*) when the SoftDevice is enabled."

In esb_timeslot.c, NVIC_* functions are used. Could this be an issue?

RE: Running micro-ESB concurrently with BLE

Paul — Wed, 15 Jun 2016 08:07:23 GMT

Do you have similar code example for the nrf52?

RE: Running micro-ESB concurrently with BLE

hassan789 — Wed, 26 Aug 2015 23:02:48 GMT

I wish I could +1 this post!

RE: Running micro-ESB concurrently with BLE

Audun — Tue, 18 Aug 2015 00:14:55 GMT

Thanks for the feedback, David. I've added a couple of state figures and put the code on github.

RE: Running micro-ESB concurrently with BLE

David Edwin — Mon, 17 Aug 2015 10:49:36 GMT

Can the code be moved to github ? so it is easier to use and to refer to. A diagram for the state machine used in this example would alse be nice. It is a very good and useful example.