BLE Advertisement Issue in nRF Connect SDK v2.7.0 (DRGN-23231) – Any Cherry-Pick or Temporary Fix Available?

[Prashant Humbre]

Hello Nordic team,

I'm currently developing on the nRF5340 and recently encountered an issue related to BLE advertisements. After thorough debugging, I was able to confirm that the root cause lies within the nRF Connect SDK, not within my application code.

While investigating further, I found that the issue is documented in the Known Issues section of the nRF Connect SDK v2.7.0 release notes with the ID: DRGN-23231
Reference: Known Issues - nRF Connect SDK

I also noticed that this issue appears to have been resolved in nRF Connect SDK v2.8.0.

Due to the fact that our product is already in production, a full migration to v2.8.0 will require additional time for integration and validation. In the meantime, I’m looking for a temporary resolution.

Could you please let me know:

• Is there a cherry-pickable commit or patch from v2.8.0 that can be applied to nRF Connect SDK v2.7.0 to temporarily resolve this issue?

• Or is there any recommended workaround that can be used until we complete the migration?

Any support or guidance would be highly appreciated, as we are aiming to resolve this issue as soon as possible in our production environment.

Thanks in advance!

Regards,

Prashant Humbre

[Vidar Berg]

Hello Prashant,

The fix for the mentioned issue was implemented in the Softdevice controller library so it can't be patched directly, unfortunately. But does this issue you are observing occur after you have been in a connection, or was it only advertising at the time? 

Thanks,

Vidar

[Prashant Humbre]

Hello Vidar,

Thank you for your quick response and for clarifying that the fix is part of the SoftDevice Controller library.

To answer your question, the issue I am observing occurs after a connection has been established.

In my particular scenario, this mainly occurs when the mobile phone goes out of range from the device during the DFU process while data is being transferred. After this happens, the device fails to resume advertising properly, and the only recovery option we’ve found so far is to power cycle the device, which is not ideal for a product that is already in production.

Additionally, after reviewing the Nordic debug logs, I observed that the Disconnect event is not getting triggered when the mobile phone goes out of range. This might be contributing to the issue, as the device seems to remain in an inconsistent state after the connection is lost abruptly.

If there are any mitigation steps, configuration changes, or temporary workarounds that I can apply while still on nRF Connect SDK v2.7.0, it would be very helpful until we can complete a full migration to v2.8.0.

Thanks again for your support!

Best regards,
Prashant