• State Not Answered
  • Replies 1 reply
  • Subscribers 89 subscribers
  • Views 54 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 360518
Options

Is there a change in the implementation of the connection interval update request between bare-metal SDKs v0.9.0 and v1.0.0

Aryeh Eiderman
Hi,
 
I see the different behavior of the function sd_ble_gap_conn_param_update when connected to Windows integrated Bluetooth.
 
Using bare-metal SDK v0.9.0 it succeeds on the first call.
Using bare-metal SDK v1.0.0 it occasionnaly returns NRF_ERROR_BUSY and requires retries.
 
Please, confirm this change.
 
(The related hardware is nRF54L15 DK.)
 
Thank you!
 
 
Best Regards,
Aryeh
Parents
  • 0

    Hi Aryeh,

    sd_ble_gap_conn_param_update will return NRF_ERROR_BUSY when a previous update procedure is still ongoing. The solution is to attempt sending the connection parameter update request more frequently. I can't see that there is an obvious change that were done that would cause this behavior. If you want me to investigate further, could you please provide the following:

    -Sniffer traces of both cases
    -Exact SoftDevice builds used
    -Application logs

    Best regards,
    Benjamin

Reply
  • 0

    Hi Aryeh,

    sd_ble_gap_conn_param_update will return NRF_ERROR_BUSY when a previous update procedure is still ongoing. The solution is to attempt sending the connection parameter update request more frequently. I can't see that there is an obvious change that were done that would cause this behavior. If you want me to investigate further, could you please provide the following:

    -Sniffer traces of both cases
    -Exact SoftDevice builds used
    -Application logs

    Best regards,
    Benjamin

Children
No Data
Related
Terms of service