how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

run_ar — Tue, 13 Nov 2018 13:37:20 GMT

For sd_ble_gap_addr_set

The address type must be either @ref BLE_GAP_ADDR_TYPE_PUBLIC or @ref BLE_GAP_ADDR_TYPE_RANDOM_STATIC

If you want to use a private address you should use sd_ble_gap_privacy_set. See message sequence chart here.

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

Shawn N. — Thu, 08 Nov 2018 17:00:33 GMT

I am also running into this.

sd_ble_gap_addr_set

should accept

BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_NON_RESOLVABLE

addresses.

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

ntn — Thu, 08 Nov 2018 09:04:51 GMT

Hi, I stumbled upon this question again, 2 years later. One use case should be the eddystone application, where the address shall be changed constantly for privacy reason. I looked into Nordic Eddystone implementation and BLE_GAP_ADDR_TYPE_PUBLIC was used, which is wrong and should be private non resolvable address.

I however cannot manage to set the address to BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_NON_RESOLVABLE, even if I have set the MSB 2 bits to 0x00. Error number 12802 (BLE_ERROR_GAP_INVALID_BLE_ADDR). SD 6.1, SDK 15.2. Is there any example in SDK that managed to set address type to BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_NON_RESOLVABLE? Thanks!

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

run_ar — Fri, 25 Aug 2017 08:25:11 GMT

Yes, the using the timeslot api would work. Could it be possible to use a normal random static address? As long as you are non connectable I guess it shouldn't matter? And could you also elaborate on the usecase, i.e. why you need to use a private non resolvable address?

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

Marius Heil — Thu, 24 Aug 2017 09:39:35 GMT

Sadly no, I am currently still using v2 of the SoftDevice because it is compatible for both nRF51 and nRF52. Will have to find something later when I migrate. I will probably disable and enable advertising/scanning/etc using the timeslot API. Hopefully this works.

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

run_ar — Thu, 24 Aug 2017 09:31:01 GMT

Looks like you are right. Did you figure out a way to do this? if not, I will check if there is any other way to manually set a Private non resolvable address.

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

Marius Heil — Fri, 04 Aug 2017 14:07:45 GMT

Do I really have to use sd_ble_gap_privacy_set if I want to use BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_NON_RESOLVABLE? Or can I keep my code that works with version v2 by simply changing the GAP address myself using sd_ble_gap_addr_set?

I have just implemented a multi advertiser that can broadcast using different addresses, but no it seems like this functionality has been modified and this is no longer possible :-( Any workarounds? This was the only sensible method for broadcasting multiple messages,...

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

Moritz — Tue, 28 Feb 2017 16:45:03 GMT

The error you got was "NRF_ERROR_INVALID_ADDR (NRF_ERROR_BASE_NUM + 16)" So your program was stuck in an endless loop.

Your code needs to look like this to work.

ble_gap_privacy_params_t ble_gap_privacy_params = {0};
ble_gap_privacy_params.privacy_mode = BLE_GAP_PRIVACY_MODE_DEVICE_PRIVACY;
ble_gap_privacy_params.private_addr_type = BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE;
ble_gap_privacy_params.private_addr_cycle_s = BLE_GAP_DEFAULT_PRIVATE_ADDR_CYCLE_INTERVAL_S;
ble_gap_privacy_params.p_device_irk = NULL;
err_code = sd_ble_gap_privacy_set(&ble_gap_privacy_params);
APP_ERROR_CHECK(err_code);

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

run_ar — Wed, 01 Feb 2017 11:33:45 GMT

you don't have to do sd_ble_gap_privacy_get first. just initialize the struct to 0. Anyway it looks like you are using the correct parameters. How do verify if this works or not?

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

littlebei — Tue, 31 Jan 2017 03:32:18 GMT

I tried to use sd_ble_gap_privacy_set() to set a random private resolvable address. I added these code in gap_params_init():

	ble_gap_privacy_params_t *ble_gap_privacy_params;
	err_code = sd_ble_gap_privacy_get(ble_gap_privacy_params);
	APP_ERROR_CHECK(err_code);
	ble_gap_privacy_params->privacy_mode = BLE_GAP_PRIVACY_MODE_DEVICE_PRIVACY;
	ble_gap_privacy_params->private_addr_type = BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE;
	ble_gap_privacy_params->private_addr_cycle_s = BLE_GAP_DEFAULT_PRIVATE_ADDR_CYCLE_INTERVAL_S;
	ble_gap_privacy_params->p_device_irk = NULL;
	err_code = sd_ble_gap_privacy_set(ble_gap_privacy_params);
	APP_ERROR_CHECK(err_code);

No error or warning, but it still does not work.

RE: how to set ble gap address type to RANDOM_PRIVATE_RESOLVABLE

run_ar — Thu, 19 Jan 2017 11:46:50 GMT

For S132 v3 you need to use sd_ble_gap_privacy_set if you want to use a random private resolvable address. See ble_gap_privacy_params_t for details.