DEVICEADDR and resolvable private addresses

RE: DEVICEADDR and resolvable private addresses

FormerMember — Wed, 02 Nov 2016 09:57:13 GMT

The device address in the two deviceaddr registers in FICR are random generated numbers. This post shows how to convert/extract the BLE-device address from the device address in FICR.

RE: DEVICEADDR and resolvable private addresses

will — Tue, 01 Nov 2016 16:38:58 GMT

The address appears to be a resolvable private address. This is what I read (in gdb) when I read the FICR:

(gdb) x/3wx 0x100000a0

0x100000a0: 0xffffffff 0x35eca783 0xe9814129

Based on the description in the documentation, the low 15 bits of 0x100000a8 are the upper two bytes of the device address. Thus, the device address as I read it (from least significant to most significant) is: 0x83 0xa7 0xec 0x35 0x29 0x41. This seems to me to indicate that the upper two bits are 0 1, which is a resolvable private address.

RE: DEVICEADDR and resolvable private addresses

FormerMember — Tue, 01 Nov 2016 06:19:16 GMT

The device address programmed to the chip during manufacturing is, as you know, as random static address, and that address should follow the rules for random static addresses defined in the Bluetooth core specification. According to the Bluetooth Core specification v. 4.2, vol. 6, part B, chapter 1.3.2.1, a random static address should have the following format:

@will: What is the address of your device?