Re: Bluetooth Address Type - Fixed (public)
Chettimada, Vinayak Kariappa
Hi Jie,
I have tested both on upstream master and v1.9.1 (on a nRF52 though), and my boards use the same identity address as assigned by the factory and used by the Zephyr Host.
I am afraid you may have erased the factory data on your board, which means the chip will not meet its full functional behaviour.
These factory data are unique for each chip, I advise you not to use such boards that miss factory data.
Starting Scanner/Advertiser Demo
[2017-10-28 06:56:23.121] [bt] [INF] hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[2017-10-28 06:56:23.127] [bt] [INF] hci_vs_init: HW Variant: nRF52x (0x0002)
[2017-10-28 06:56:23.131] [bt] [INF] hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.9 Build 99
[2017-10-28 06:56:23.140] [bt] [INF] show_dev_info: Identity: ef:0f:a3:d8:8f:24 (random)
[2017-10-28 06:56:23.145] [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0xffff
[2017-10-28 06:56:23.153] [bt] [INF] show_dev_info: LMP: version 5.0 (0x09) subver 0xffff
[2017-10-28 06:56:23.158] Bluetooth initialized
[2017-10-28 06:56:36.547] Starting Scanner/Advertiser Demo
[2017-10-28 06:56:36.551] [bt] [INF] hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[2017-10-28 06:56:36.557] [bt] [INF] hci_vs_init: HW Variant: nRF52x (0x0002)
[2017-10-28 06:56:36.561] [bt] [INF] hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 1.9 Build 99
[2017-10-28 06:56:36.570] [bt] [INF] show_dev_info: Identity: ef:0f:a3:d8:8f:24 (random)
[2017-10-28 06:56:36.575] [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0xffff
[2017-10-28 06:56:36.583] [bt] [INF] show_dev_info: LMP: version 5.0 (0x09) subver 0xffff
[2017-10-28 06:56:36.588] Bluetooth initialized
With the v1.9.1 tag:
[2017-10-28 06:59:30.383] Starting Scanner/Advertiser Demo
[2017-10-28 06:59:30.386] [bt] [INF] show_dev_info: Identity: ef:0f:a3:d8:8f:24 (random)
[2017-10-28 06:59:30.391] [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0xffff
[2017-10-28 06:59:30.399] [bt] [INF] show_dev_info: LMP: version 5.0 (0x09) subver 0xffff
[2017-10-28 06:59:30.405] Bluetooth initialized
[2017-10-28 06:59:42.718] Starting Scanner/Advertiser Demo
[2017-10-28 06:59:42.722] [bt] [INF] show_dev_info: Identity: ef:0f:a3:d8:8f:24 (random)
[2017-10-28 06:59:42.727] [bt] [INF] show_dev_info: HCI: version 5.0 (0x09) revision 0x0000, manufacturer 0xffff
[2017-10-28 06:59:42.735] [bt] [INF] show_dev_info: LMP: version 5.0 (0x09) subver 0xffff
[2017-10-28 06:59:42.741] Bluetooth initialized
Regards,
Vinayak
On 28 Oct 2017, at 04:14, Jie Zhou <zhoujie@...> wrote:
Still have the same issue where MAC address changes every time.
<image.png>I'm in version zephyr 1.9.1
On Thu, Oct 26, 2017 at 8:24 PM, Jie Zhou <zhoujie@...> wrote:
I see, I am using zephyr version 1.8.0. I will get back to you guys. Thanks everyone!
On Thu, Oct 26, 2017 at 8:14 PM, Johan Hedberg <johan.hedberg@...> wrote:
Hi Jie,
On Thu, Oct 26, 2017, Jie Zhou wrote:
> CONFIG_BT_PRIVACY=n is something I already tried, and it seems to still
> advertises with a temporary random static address. Here's the output of the
> scan/advertise the addition to the conf file changes nothing.
>
> [image: Inline image 1]
>
> The MAC address changes with every reset. Thanks for the advise on the
> public MAC address.
Have you built your nRF51 and Quark SE images from the latest master
branch? If not, please do so. It contains code to properly utilize the
factory programmed static random address in the controller.
Johan