I am working on the channel sounding feature using two nRF54L15DK boards and faced an unexpected link disconnection while running the channel_sounding_ras_initiator and channel_sounding_ras_reflector samples from the nRF SDK. The examples can run for up to 5 minutes, but the disconnection happens much earlier in most cases.
Here is some information that might be helpful:
*** Booting nRF Connect SDK v2.9.99-989cde884ed8 *** *** Using Zephyr OS v3.7.99-6e9a5873c5df *** I: Starting Channel Sounding Initiator Sample I: SoftDevice Controller build revision: I: 5e 89 40 59 db 09 d7 b7 |^.@Y.... I: 04 e6 67 8d c1 e3 8c cc |..g..... I: 0c e1 9c d3 |.... I: HW Platform: Nordic Semiconductor (0x0002) I: HW Variant: nRF54Lx (0x0005) I: Firmware: Standard Bluetooth controller (0x00) Version 94.16521 Build 3607747417 I: Identity: CE:16:77:E3:B5:9A (random) I: HCI: version 6.0 (0x0e) revision 0x3063, manufacturer 0x0059 I: LMP: version 6.0 (0x0e) subver 0x3063
The console output for the initiator:
I: Estimated distance to reflector: I: - Round-Trip Timing method: 4.159620 meters (derived from 4 samples) I: - Phase-Based Ranging method: 2.634659 meters (derived from 35 samples) I: Subevent result callback 15 I: Ranging data ready 15 E: Error when getting ranging data with ranging counter 15 (err -128) I: Disconnected (reason 0x08) E: Timeout waiting for ranging data complete (err -11)
The console output for the reflector:
W: Not connected W: Failed to send indication: -128 I: Disconnected (reason 0x3D)
I also tried the Zephyr samples channel_sounding/connected_cs/initiator and channel_sounding/connected_cs/reflector and did not encounter the described disconnection.
Can it be the issue with the nRF SDK?
