Hello,
I have some code running on an NRF52832 using NRF Connect SDK 2.5.1 which initalizes my BLE with a random private resolvable adress so that I can easily reconnect to it.
When using the same code with an nrf54l10 and NRF Connect SDK 2.9 the BLE uses with a random static adress.
This is what my "init" function looks like:
int blep_init() {
int err = 0;
err = bt_conn_auth_cb_register(&conn_auth_callbacks);
if (err) {
LOG_ERR("Failed to register authorization callbacks (err %d)!", err);
return err;
}
if (!bt_is_ready()) {
err = bt_enable(NULL);
if (err) {
LOG_ERR("Bluetooth (Peripheral) init failed (err %d)", err);
return err;
}
}
LOG_INF("Bluetooth (Peripheral) initialized");
#if CONFIG_SETTINGS
settings_load();
#endif
// Update scan data with updated data
sd->type = BT_DATA_NAME_COMPLETE;
sd->data_len = strlen(bt_get_name());
sd->data = bt_get_name();
bt_set_bondable(true);
start_adv_casual();
return err;
}
And these are (some of the) configurations I use:
CONFIG_BT_CENTRAL=y CONFIG_BT=y CONFIG_BT_SCAN=y CONFIG_BT_SMP=y CONFIG_BT_PRIVACY=y CONFIG_BT_GATT_DM=y CONFIG_BT_GATT_CLIENT=y CONFIG_BT_SETTINGS=y CONFIG_BT_GATT_CACHING=n CONFIG_BT_DEVICE_NAME_DYNAMIC=y CONFIG_DEVICE_NAME_GATT_WRITABLE_ENCRYPT=y CONFIG_BT_SMP_ALLOW_UNAUTH_OVERWRITE=y CONFIG_BT_ID_UNPAIR_MATCHING_BONDS=y CONFIG_BT_BONDING_REQUIRED=y CONFIG_FLASH=y CONFIG_FLASH_PAGE_LAYOUT=y CONFIG_FLASH_MAP=y CONFIG_NVS=y CONFIG_SETTINGS=y
Were there some changes from NRF Connect SDK 2.5.1 to 2.9 that I need to consider to obtain the same adress type?
Thank you and Regards,
Vito
