This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Peer address changes every time

Hello everybody.

I just startet developing with nrf products and I'm facing a problem there.

I'm currently developing a System based on the ble_app_uart_c example. I'm using the S132 Softdevice 5.0 with the SDK 14.2.

I modified the code so it prints me out the RSSI and the peer address of every advertisement. The only Advertiser nearby ia another Development Kit of the same type which is running the ble_abb_beacon example. Now everytime I get an advertisement event I get another peer address. The address is incrementing with every event.

I found the following post with the same issue

https://devzone.nordicsemi.com/f/nordic-q-a/6900/dfu-device-address-changes

Now the solution there doesn't seem to work for the 14.2 SDK since the mentioned c-File doesn't exist.

Where can I disable the increments in the 14.2 SDK?

Also what about other devices besides the nrf products? If I turn on the Bluetooth on my notebook for example I get the same Issue: The peer address is incrementing continuously. Is this a commong thing with bluetooth devices? Are there better options for searching and selecting devices rather than the peer address?

Thank you so much for your help.

Best wishes

Parents
  • 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

Reply
  • 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

Children
No Data
Related