Changing the content of nRF ESB payload

RE: Changing the content of nRF ESB payload

ovrebekk — Wed, 22 May 2019 11:59:39 GMT

Hi Winz

What does the printf retarget to?

If you are using the UART interface it could be that you are spending too much time pushing bytes to the UART interface, and that you are stuck in the interrupt for too long.
An alternative solution to this should be to set a flag in the ESB event, rather than run this code, and check the flag in your main loop. Then you can run the code from there in thread context, where it should not affect other parts of the system, and hopefully you can use printf without any issues.

The error codes you are referring to are defined in nrf_error.h

4 corresponds to NRF_ERROR_NO_MEM, which most likely means the internal buffers are full, and 9 corresponds to NRF_ERROR_INVALID_LENGTH.

Best regards
Torbjørn

RE: Changing the content of nRF ESB payload

Winz — Tue, 21 May 2019 07:42:45 GMT

Hi Torbjørn,

I found a workaround for this: either I don't print it (possible problem with printf? I can't use NRF_LOG in my application, so I use printf) OR flush, stop, then start the rx. Is it how it supposed to be processed?

*EDIT* Not really, the old data still resides in the Rx buffer..

Also, I would like to ask another question: upon writing payload using `nrf_esb_write_payload`, I sometimes receive NRF_SUCCESS on the return, but some other numbers like 4 and 9. May I know if it's documented somewhere?

Thank you,
Winz

RE: Changing the content of nRF ESB payload

Winz — Tue, 21 May 2019 07:36:51 GMT

Hi Torbjørn,

Sure, it's on its way to your private message

Thank you,
Winz

RE: Changing the content of nRF ESB payload

ovrebekk — Tue, 21 May 2019 07:30:29 GMT

Hi Winz

If this problem persists we can continue the discussion in this case, to avoid cluttering the other one too much.

Can you attach your main.c file, so I can have a look at the rest of the code also?

Best regards
Torbjørn