bt_le_ext_adv_update_param() cannot change BDADDR

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Fri, 10 Mar 2023 11:02:44 GMT

I suggest you do as initially suggested:

[quote user="loquat"]I can achieve this by using multiple AdvertiseSets, but I would like to avoid this as it requires additional memory.[/quote]

Alternatively, you can stop, update and start advertising also if you want too like on the old nRF5 SDK.

But if you are using connectable advertisment then we need to follow the BT spec.

Kenneth

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Fri, 10 Mar 2023 08:04:05 GMT

No, that's not what I want to know.

Did you forget to set param->id to adv->id in the process of bt_le_ext_adv_update_param()?

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Tue, 07 Mar 2023 14:25:28 GMT

It is not allowed for most types of advertising.

When using legacy advertising commands the address that is used is the one set through "HCI LE Set Random Address command". In Core_v5.4, Vol 4, Part E, Section 7.8.4:

If the Host issues this command when any of advertising (created using legacy advertising commands), scanning, or initiating are enabled, the Controller shall return the error code Command Disallowed (0x0C).

When using extended advertising commands the address that is used is the one set through "LE Set Advertising Set Random Address command". In Core_v5.4, Vol 4, Part E, Section 7.8.52:

However, if the Host issues this command while the advertising set identified by the Advertising_Handle parameter is using connectable advertising and is enabled, the Controller shall return the error code Command Disallowed (0x0C).

Best regards,
Kenneth

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Thu, 02 Mar 2023 23:55:58 GMT

Core spec v5.1
LE Set Advertising Set Random Address command

want to do the same thing.
It seems that this command can be called even during Advertising.
(It seems that the setting will be reflected at the next enable.)

what should i do?

---------------------------------------------------------------------------------------------
I checked the source code.

zephyr/subsys/bluetooth/host/adv.c
int bt_le_ext_adv_update_param()
...
le_ext_adv_param_set()
    ...
    ////////////////////////////////////
    It looks like are setting BDADDR
    ////////////////////////////////////
   err = bt_id_set_adv_own_addr(adv, param->options, dir_adv,
                     &cp->own_addr_type);
      ...
      /* Set which local identity address we're advertising with */
      ///////////////////////////////////////////////
       BDADDR is not new addr but old(current) addr?
      ///////////////////////////////////////////////
      id_addr = &bt_dev.id_addr[adv->id];
      ...
      if (options & BT_LE_ADV_OPT_USE_IDENTITY) {
        if (id_addr->type == BT_ADDR_LE_RANDOM) {
          err = bt_id_set_adv_random_addr(adv, &id_addr->a);
        }

is something wrong?

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Sun, 26 Feb 2023 23:45:08 GMT

OK.Thanks.

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Sun, 26 Feb 2023 17:05:08 GMT

[quote user="loquat"]Is it possible during advertising?[/quote]

No.

Kenneth

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Sun, 26 Feb 2023 04:43:26 GMT

Is it possible to set a different addr for bt_id_reset?
Is it possible during advertising?

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Mon, 20 Feb 2023 08:44:02 GMT

[quote user="loquat"]Apparently, bt_id can only be set during adv_create and cannot be changed with update_param.[/quote]

So it's the same as old nRF5 SDK then.

[quote user="loquat"]What are the limitations of bt_id_reset()?[/quote]

/**
 * @brief Reset/reclaim an identity for reuse.
 *
 * The semantics of the @a addr and @a irk parameters of this function
 * are the same as with bt_id_create(). The difference is the first
 * @a id parameter that needs to be an existing identity (if it doesn't
 * exist this function will return an error). When given an existing
 * identity this function will disconnect any connections created using it,
 * remove any pairing keys or other data associated with it, and then create
 * a new identity in the same slot, based on the @a addr and @a irk
 * parameters.
 *
 * @note the default identity (BT_ID_DEFAULT) cannot be reset, i.e. this
 * API will return an error if asked to do that.
 *
 * @param id   Existing identity identifier.
 * @param addr Address to use for the new identity. If NULL or initialized
 *             to BT_ADDR_LE_ANY the stack will generate a new static
 *             random address for the identity and copy it to the given
 *             parameter upon return from this function (in case the
 *             parameter was non-NULL).
 * @param irk  Identity Resolving Key (16 bytes) to be used with this
 *             identity. If set to all zeroes or NULL, the stack will
 *             generate a random IRK for the identity and copy it back
 *             to the parameter upon return from this function (in case
 *             the parameter was non-NULL). If privacy
 *             @kconfig{CONFIG_BT_PRIVACY} is not enabled this parameter must
 *             be NULL.
 *
 * @return Identity identifier (>= 0) in case of success, or a negative
 *         error code on failure.
 */
int bt_id_reset(uint8_t id, bt_addr_le_t *addr, uint8_t *irk);

From errno.h I can find that the new identity (addr) you are trying to create is the same as the old.

Best regards,
Kenneth

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Sun, 19 Feb 2023 06:14:44 GMT

Apparently, bt_id can only be set during adv_create and cannot be changed with update_param.

I would like to use bt_id_reset() instead.
However, if the id is associated with adv_create(), calling bt_id_reset() will return an error (-120).
What are the limitations of bt_id_reset()?

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Thu, 16 Feb 2023 07:34:59 GMT

If you are doing something wrong when calling bluetooth api's you will get an error message. As long as there is no error message you are fine.

Kenneth

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Thu, 16 Feb 2023 00:39:35 GMT

Inside the bt_le_ext_adv_cb.sent() callback function, we are calling bt_le_ext_adv_update_param().
Is this a problem?

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Tue, 14 Feb 2023 08:32:21 GMT

I would assume you need to do this similiar to the nRF5 SDK; set address before advertisement start. I do not expect changing the address on the fly while advertising will work, but I suggest you simply try it, if it works then it works, if it doesn't then it doesn't.

Kenneth

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Mon, 13 Feb 2023 23:06:38 GMT

On nRF5 SDK,

call sd_ble_gap_addr_set() before sd_ble_gap_adv_start().

Example is not ExtendedAdvertising.

In AdvertiseExtension,
I'm thinking of using bt_le_ext_adv_update_param() and changing the id to change the BDADDR.
Am I wrong?
Please let me know if there is another way.

Changing bt_le_adv_param.options seems possible.
I was able to switch BDADDR between RandomStaticAddr and NonResolvablePrivateAddress by adding or removing BT_LE_ADV_OPT_USE_IDENTITY in bt_le_adv_param.options.

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Thu, 09 Feb 2023 10:03:16 GMT

How did you do this in nRF5 SDK? I would think the address could not be changed on the fly there either?

But to answer your question, the address can be changed using the bt_id_get() and bt_id_create() api:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/connectivity/bluetooth/api/gap.html#c.bt_id_create

Example usage:
https://github.com/nrfconnect/sdk-zephyr/blob/v2.6.99-ncs1-snapshot1/samples/bluetooth/peripheral_identity/src/peripheral_identity.c#L44
https://devzone.nordicsemi.com/f/nordic-q-a/79563/is-there-a-way-to-update-the-mac-address-after-enabling-bluetooth/329797

Kenneth

RE: bt_le_ext_adv_update_param() cannot change BDADDR

loquat — Wed, 08 Feb 2023 22:50:25 GMT

The purpose is to send multiple types of advertising.
I can achieve this by using multiple AdvertiseSets, but I would like to avoid this as it requires additional memory.

Also, I implemented the processing for multiple types of advertising for the nRF5 SDK, so I would like to use that processing.

RE: bt_le_ext_adv_update_param() cannot change BDADDR

Kenneth — Wed, 08 Feb 2023 15:43:25 GMT

Can you elaborate what you are trying to do here? If you enable private resolveable address you can configure how frequently the address is updated by this kconfig option (you may need to update to ncs v2.2 for this to work):
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_RPA_TIMEOUT

Kenneth