Hello, Dialog team.
I use DA14695 and SDK 10.0.8.105 (latest). For some reasons, I need to know the current BD address of my device. When I set up my address type as PRIVATE_RANDOM_RESOLVABLE_ADDRESS, everything is ok. But when I change it to PRIVATE_CNTL, ble_gap_address_get() always return empty string (data inside the own_addr in the ble_dev_params_t structure is {0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}) and event BLE_EVT_GAP_AIR_OP_BDADDR never comes.
What shall I do to get my own BD address? Is it possible with PRIVATE_CNTL address type?
regards, Egor
Device:
Hi aectaan,
Can you please indicate if you have the LE privacy v1.2 enabled? If not, you should set the dg_configBLE_PRIVACY_1_2 macro to 1 in the confiurations files (custom_config_qspi.h / custom_config_ram.h) To use this feature, ble_gap_address_set() should be called using the PRIVATE_CNTL address type.
Thanks, PM_Dialog
Hi PmM_Dialog,
Yes, dg_configBLE_PRIVACY_1_2 macro set to 1, when I use PRIVATE_CNTL. And I call ble_gap_address_set() as below:
静态常量own_address_t own_addr = {
.addr_type = PRIVATE_RANDOM_RESOLVABLE_ADDRESS,
};
err = ble_gap_address_set(&own_addr, defaultBLE_ADDRESS_RENEW_DURATION);
Hi aectaan,
Thanks for your inputs. I have already escalated it internally. I’ll let you know as soon as I have a response from the Team.
Thanks, PM_Dialog
Hi PM_Dialog,
Just found mistake in previous own_address_t struct: it is
静态常量own_address_t own_addr = {
.addr_type = PRIVATE_CNTL,
}; when I use dg_configBLE_PRIVACY_1_2=1
Hi aectaan,
No problem - I have escalated the correct configuration (addr_type = PRIVATE_CNTL) according to your initial post. Again thanks for your feedback. I will revert back to you ASAP.
Thanks, PM_Dialog
Hi PM_Dialog,
Any updates?
Thanks, Egor
Hi aectaan,
Apologies for the delay but there are any updates from the Team yet. I’ll let you know as soon as I have any new on this.
Thanks, PM_Dialog
Hi Egor,
My apologies for my late response here. I got feedback and this is a known issue which does not affect the operation of the device BLE-wise. This will be addressed in future releases.
Thanks, PM_Dialog