Some issues arising from the introduction of esb timeslot in SDK:17.1

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

Kenneth — Mon, 20 Nov 2023 12:22:31 GMT

Hi again,

[quote user="kenyon"]As for kenneth, you said 2ms. Should it be added to TIMESLOT_BEGIN_IRQHandler? Because I don't see anything in here to disable or stop reception.[/quote]

My comment of minimum ~2ms was just to ensure that you don't stop reception when you receive a packet, it's a common mistake that I have seen in the past many times explains why the prx receive packets, but the ptx don't get an ack. It may be that this is not the problem here.

Kenneth

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

kenyon — Mon, 20 Nov 2023 12:09:29 GMT

hi Kenneth
two nRF52-devices.
I added the esb_timeslot file to the ble_app_uart routine of SDK17.1 and added it.
And I also tested that it couldn't answer ack. I guess this code will help us solve the problem better. As for kenneth, you said 2ms. Should it be added to TIMESLOT_BEGIN_IRQHandler? Because I don't see anything in here to disable or stop reception.

devzone.nordicsemi.com/.../08166.main.c devzone.nordicsemi.com/.../0181.esb_5F00_timeslot.c

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

Kenneth — Sun, 19 Nov 2023 18:30:10 GMT

Hi,

Are you communicating between two nRF52-devices or are you using a different peer device?

On the PRX, make sure you don't disable or stop reception when you receive a packet, since this will prevent the ack to be sent. On the PRX you should wait for instance 2ms after receiving a packet before stopping reception, do you do this?

Kenneth

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

kenyon — Fri, 17 Nov 2023 02:56:12 GMT

Hi kenneth
I can't guarantee that because my code comes with softdevice, it would be a lot of work to port my code to a routine with no softdevice.But I'm sure that both the esb_PTX and esb_PRX routines my device uses to run SDK17.1 are working fine.
In my code (with softdevice), I can set only PRX mode or only PTX mode. If PRX is set, messages are received correctly, but ack cannot be sent. Setting PTX will result in an error.

Kenyon

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

Kenneth — Thu, 16 Nov 2023 21:11:22 GMT

Hi,

Does running ESB directly (without softdevice) work as intended?

Kenneth

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

kenyon — Thu, 16 Nov 2023 12:06:14 GMT

hi kenneth！

You're talking about the software SES, right? I use Keil5, I don't know if I can get useful information in Keil5 debug. I can now only catch messages that my device cannot send (write txpayload error), but it can successfully receive messages from other devices. Therefore, whether the conversion of PTX and PRX is caused by the error of esb_timeslot file itself, I am a little powerless now and do not know where to check.T T

Best regard
kenyon

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

Kenneth — Tue, 14 Nov 2023 11:49:41 GMT

If you build using Debug instead of Release, then the window should contain more information about the error (e.g file name, line number and actual error code) and also the call stack. Also check out:
https://www.youtube.com/watch?v=uP8RYgYGRvI&list=PLx_tBuQ_KSqGHmzdEL2GWEOeix-S5rgTV&index=7

You can find from nrf_error.h that 4 means: NRF_ERROR_NO_MEM (so likely means that packets have not been sent successfully (no receiver was able to receive them)).

Kenneth

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

kenyon — Tue, 14 Nov 2023 03:52:00 GMT

I also tried to set the mode of ESB to PTX to actively send messages. It will eventually go into the bootloader after sending it a few times, and I'm guessing it failed in some APP_CHECK_ERROR. It looks like the ESB's state machine PTX and PRX transitions are not well coordinated, but I wonder where the logic is at fault

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

kenyon — Tue, 14 Nov 2023 03:11:18 GMT

hi kenneth

I tried to fix my own esb using the esb_timeslot section in the link.

But it's weird when it call
TIMESLOT_BEGIN_IRQHandler()

After receiving an ack message, the device changes the status to PTX and sends the message. err_code = nrf_esb_write_payload(&tx_payload); ", "return 04, causing the verification failure and entering the bootloader.

Why is that?
Looking forward to hearing from you! Thank you very much

RE: Some issues arising from the introduction of esb timeslot in SDK:17.1

Kenneth — Wed, 08 Nov 2023 12:20:34 GMT

Hello,

There is no official example in the nRF5 SDK showing this, but you can find an example here:
https://github.com/NordicPlayground/nrf51-ble-micro-esb-uart (it does nRF51 in the title, but it is updated to nRF52 and nRF5 SDK v17).

I suggest to study it for guideance.

Kenneth