New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth Firmware MAC Address Issue #860
Comments
I can confim this too.
|
The new Bluetooth firmware seems to be ignoring the MAC address programmed into its OTP- the address you have now is a default for that chip (4343 A1 ...). Fortunately there is a way to set a MAC address using hciattach. Here is a modified version of the /usr/bin/btuart script that should set the MAC address correctly. If you want to try it, download it to the home directory of user
To return to the shipping version, which I recommend before updating the pi-bluetooth package, run:
|
Thx, modified btuart indeed works as expected here, bt mac now is the good one. |
Cool, thanks. This workaround solves my problems too. |
See: raspberrypi/firmware#860 (comment) Also, use sh instead of bash - one less unecessary bash dependency.
See: raspberrypi/firmware#860 (comment) Also, use sh instead of bash - one less unecessary bash dependency.
While upgrading from Jessie to Stretch, I found the latest Bluetooth firmware has a weird issue with the MAC Address it initializes the bluetooth adapter with.
With bluez-firmware version 1.2-3+rpi2, the mac address is set to 43:43:A1:12:1F:AC. This may be constant across hardware seeing I've found reference to it on the internet [1]. Besides that, this weird MAC address breaks bluetooth PAN because the bnep adapter gets rejected as a valid device when adding it to bridge. This is because the mac address is actually a multicast address (bit 1 is set in the first octet) and thus fails the 'is_valid_ether_addr' check in the kernel.
With bluez-firmware version 1.2-3+rpi1, the mac address is what it was originally (with a proper B8:27:EB: prefix). However, this version of the firmware doesn't seem to work correctly with the rest of the bluetooth stack in Stretch.
Thanks,
Logan
[1] https://www.raspberrypi.org/forums/viewtopic.php?t=148305&start=100
The text was updated successfully, but these errors were encountered: