Can I copy the ESB code from SDK v3.3.0-preview3 into SDK v2.9.0, and then get the functionality in esb_ptx_ble & esb_prx_ble?
Is there any way to achieve it quickly?
Can I copy the ESB code from SDK v3.3.0-preview3 into SDK v2.9.0, and then get the functionality in esb_ptx_ble & esb_prx_ble?
Is there any way to achieve it quickly?
Hello,
Not sure I understand what problem you are trying to solve here, there should be ESB example projects for the nRF52840 in both the nRF Connect SDK releases you are referring to.
Can I copy the ESB code from SDK v3.3.0-preview3 into SDK v2.9.0, and then get the functionality in esb_ptx_ble & esb_prx_ble?
There may be some api changes, but for most part I would expect it should be pretty straight forward possible yes.
Kenneth
Hello,
Using nRF Connect SDK v3.3.0, one device runs esb_ptx_ble and broadcasts 2 packets of data every 5-10ms, with 15 devices running esb_prx_ble,esb rx interval 7300ms,rx window 15ms, 30 seconds is a receiving cycle, and failure to receive a packet of data within the cycle is considered a failure; After running 15 devices for a few days, occasionally one device experiences dozens of consecutive cycles without receiving data. Why is that?
Hi Edvin,
Hi Edvin,
I encountered a similar issue during my tests using the nRF52840DK. You can open the esb_prx_ble_test_0917.log file and search for "HARD FAULT" to see the specific details.
Based on NCS v3.3.0.
Test Steps:
1. Burn esb_prx_ble_test.hex to the nRF52840DK.
2. View the logs using J-Link Viewer.
3. The nRF52840DK will scan for nearby BT devices (RSSI>=-50) and attempt to connect.
4. If the connection is successful, it will disconnect after 5 seconds.
5. Steps 3 and 4 will be automatically repeated.
esb_prx_ble_test.zip
Best regards,
Leo
Hi Edvin,
I encountered this bug again. It seems the logs are printed by the "ts_start_action" function and don't notify the outside world via the ESB_EVENT_TIMESLOT_FAILED event. Therefore, my application layer is unaware of the PPI error and doesn't reboot the device.
I'm using ESB + BLE central with several peripherals connected, which seems to make this bug more likely to be triggered.
Error log:
00> [09:52:57.440,979] <err> esb: gppi_channel_alloc failed with: -12
00> [09:52:57.440,979] <err> esb: Failed to initialize PPI
bridge-interconn-0812-1734.log
Best regards,
Leo
Hello,
I see. It is an MPSL assert. According to our SoftDevice Controller team, this is caused by a user of a timeslot overstaying it's granted timeslot. The good news is that this is currently a known issue, and it was fixed in this pull request:
https://github.com/nrfconnect/sdk-nrf/pull/29998
Can you try to apply this pull request and see if the issue goes away?
Best regards,
Edvin
Hi,
I've already used this code:https://github.com/nrfconnect/sdk-nrf/pull/29998
But I'm still encountering this issue. You can check my previous answers.
Best regards,
Leo
Hi,
I've already used this code:https://github.com/nrfconnect/sdk-nrf/pull/29998
But I'm still encountering this issue. You can check my previous answers.
Best regards,
Leo