RE: Random private resolvable Adress on nrf54l10

Iskailko — Wed, 30 Apr 2025 07:29:55 GMT

Hello, thanks a lot for your tips. Actually I found the issue was due to a not a correctly set CONFIG_BT_PRIVACY=y, as it was set to n although I've written it differently above.

RE: Random private resolvable Adress on nrf54l10

tesc — Wed, 30 Apr 2025 06:19:17 GMT

Hi,

Please note that most of the SDK support for nRF54L10 was added in nRF Connect SDK version 3.0.0, which was just recently released. I therefore highly recommend switching to that version of the SDK.

Please note also that for nRF54L you should use Zephyr Memory Storage (ZMS) instead of NVS. See Enabling Zephyr Memory Storage.

If you still see the same issue in nRF Connect SDK 3.0.0. Can you check both with nRF52832 as well as with nRF54L10, to identify if the issue is general for running the code on the newer SDK, or if it is specific to the nRF54L?

Also, if you still see the issue, can you share the code which starts the advertising? (Most likely this would be inside start_adv_casual())

Regards,
Terje