RE: Peer address changes every time

Edvin — Fri, 04 May 2018 11:49:01 GMT

Hello,

The case that you linked to is really another use case, since you want the DFU target to use a different address because it has to bypass the central (phone) *thinking* it knows what services the device has.

Are you sure that you are sniffing the correct device? Do you recognize the advertising packets?

If you look at my screenshot below, you will see the highlighted area of the packet from ble_app_beacon (without modifications). As you can see, 01 02 03 04 at the end of the highlighted area are the APP_MAJOR_VALUE and APP_MINOR_VALUE from the top of main.c, and the rest of the highlighted area is the APP_BEACON_UUID.

Can you try to use the sniffing tool (nrf sniffer v2, requres only a DK) and see if you have a constant address, or if it is changing?

Best regards,

Edvin

RE: Peer address changes every time

Hammerfall — Fri, 20 Apr 2018 14:19:47 GMT

Small update

I tried to solve the problem but I have no real solution so far.

In the beacon example the advertiser is initialised with "NULL" as peer address.

m_adv_params.type        = BLE_GAP_ADV_TYPE_ADV_NONCONN_IND;
m_adv_params.p_peer_addr = NULL;    // Undirected advertisement.  				
m_adv_params.fp          = BLE_GAP_ADV_FP_ANY;
m_adv_params.interval    = NON_CONNECTABLE_ADV_INTERVAL;
m_adv_params.timeo       = 0;       // Never time out.

Declaring a peer address and set it in this section doesn't change anything. The address is still increasing.

Also using the sd_ble_gap_addr_set() function doesnt change this behavior.