EDIT:
It looks like I'm going to have to row back a bit here. With the nrf connect sdk 2.6.0 the examples run as it looks.
Only the build in the zephyr repo (3.6.99) leads to the faulty behaviour. How does that happen?
Edit2: I did some more research:
- Building both devices with zephyr repo data stream stops, which results in receive callback not being triggered.
- Building only the receiving device with ncs 2.6.0 results in BT_ISO_FLAGS_LOST in receive callback (which is at least called).
- Building both – receiving and sending device – with ncs 2.6.0 results in a working data transmission as far as i can tell.
Hey guys,
my goal is to transfer data from nrf52832 to nrf52840 via BLE ISO channel. Since my own implementation did not work as expected (Packets not received) I thought I give the examples a try: CENTRAL_ISO & PERIPHERAL_ISO
Unfortunately, I had to realize that the same problem occurs with the examples, both examples run on nrf52840 for now. What happens:
- Connection is established between central and peripheral.
- ISO channel is connected succesfully.
- Central starts data stream (all parameters from example left unchanged)
- Peripheral receives some data and prints messages to console.
- At some point (after few intervals) the peripheral is not receiving any more data, while central is still sending?
I checked with Segger's Sysview and saw that the BT TX thread is called periodically on the central, but the BT RX thread is not called on the peripheral after data reception has stopped.
I can improve reliability by increasing the interval, which results in a longer data stream before it is stopped.
How can I fix to this problem? Seems like a bug to me, because nrf52840 should support iso channels, right?
Thank you!
