On Wed, Mar 8, 2017 at 10:48 PM, Pritish Gandhi <[email protected]> wrote: > Hi all, > I have a bunch of nrf52dk EVBs that I'm running the sample bleprph app on > and I noticed that all the device seems to have the same BD_ADDR (All > 0x0a's). Doesn't each device need to have a unique BD_ADDR and shouldn't > that come from the BLE controller? > I see that the bls_hs_startup_read_bd_addr() always returns with a BD_ADDR > of all 0xa's. Does that mean that this device requires us to self program > the BD_ADDR?
On nRF devices, reading the DEVICE field of FICR register is a good way to uniquely identify the device (Probably similar thing can be achieved on other Hardware platform as well. This can be then used in the advertisement packet. However, If I've understood correctly, the BD_ADDR on BLE device has to be a public address; i.e. a combination of OUI (24 bits) and remaining bits (another 24 bits) generated using IEEE 802-2001 specification. Thanks, Amit -- Sent from Bahamas, while drinking chi-chi and piña colada.
