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