Hi Gurpreet,

 

If you are using BlueZ 5.48 then, as stated in the instructions you don’t need to set the static address manually.

Instead you should just do:

 

sudo btmgmt --index 0

[hci0]# auto-power

 

Regards,

 

Carles

 

From: Gurpreet Singh <gurpreet@...>
Sent: 29 May 2018 19:51
To: Cufi, Carles <carles.cufi@...>
Cc: users@...
Subject: Re: [Zephyr-users] Unable to set Static Address on nRF52 using Zephyr v1.11.0

 

Hi Carles,

 

I should have mentioned that I did see those instructions at zephyr and have already updated my  /lib/systemd/system/bluetooth.service file. 

Thats the only real change I've noticed between the blog instructions and the zephyr instructions. 

 

Is there something else that I need to do as well? 

 

Gurpreet 

 

On Tue, May 29, 2018 at 1:47 AM, Cufi, Carles <Carles.Cufi@...> wrote:

Hi there,

 

If you are using a recent version of BlueZ then the sequence that you need to do is different from what’s on that blog post.

Here are updated instructions:

 

http://docs.zephyrproject.org/subsystems/bluetooth/devel.html#using-bluez-with-zephyr

http://docs.zephyrproject.org/subsystems/bluetooth/devel.html#testing-zephyr-based-controllers-with-bluez

 

I will update the blog post to reflect this since I see it’s still being used as a reference.

 

Carles

 

From: users@... <users@...> On Behalf Of Gurpreet Singh
Sent: 28 May 2018 18:40
To: users@...
Subject: [Zephyr-users] Unable to set Static Address on nRF52 using Zephyr v1.11.0

 

Hi,

I've been chugging along nicely with Zephyr v1.11.0 and the nRF52DK so far, being able to get it to scan and advertise using the hci_uart sample code and my Linux (ubuntu) computer. 

My linux is on BlueZ 5.48 and kernel ​4.15.0-22. This setup is just to get the ball rolling until we get sample boards from our manufacturer. 

I have run into an issue where setting the address on the chip is being rejected. 

I came across this post in the forum, but have been unable to find any clean resolution for it. 

For advertisements, you can see the all zero source mac address in the attached PCAP. 

Interestingly, the same error persists even when following the blog post on how to use the BLE controller with linux's BlueZ. (Step 5 in particular) ​

--- btmgmt
[hci1]# static-addr FF:02:03:04:05:FF
Set static address failed with status 0x0b (Rejected)
[hci1]# 

--- btmon
@ MGMT Command: Set Static Address (0x002b) plen 6 {0x0004} [hci1] 9585.454699
 Address: FF:02:03:04:05:FF (Static)
@ MGMT Event: Command Status (0x0002) plen 3 {0x0004} [hci1] 9585.454706
 Set Static Address (0x002b)
 Status: Rejected (0x0b)

To bring up the chip, I ran:

~ 11:49:30>sudo btattach -B /dev/ttyACM0 -S 1000000 -P h4
Attaching Primary controller to /dev/ttyACM0
Switched line discipline from 0 to 15
Device index 1 attached

The btmon log after this is in the attached txt file. 

Do you have any tips or suggestions on what I could do? 
Essentially, I would like to be able to program the BLE chip with a MAC address that uses the Mist OUI. 

Thanks in advance,

Gurpreet 

 

 

--

	Gurpreet Singh
	Member of Technical Staff
	Mist Systems
	e:	gurpreet@...   w:  www.mist.com
Sign up for a live demo of the world's first Virtual Network Assistant. Join Demo!