BrcmPatchRAM - Upload firmware into Broadcom Bluetooth USB devices

[HansFranz]

Thank you for the input. I'll try disabling the SS-ports.

It works.

 

[RehabMan]

Thank you for the input. I'll try disabling the SS-ports.

It works.

FYI: The idea is to disable HSxx and SSxx ports that are not being used. Disabling all SSxx ports will disable USB3 speeds on your USB3 ports.

 

[slybobimous]

I have an Intel NUC DC3217BY with the BCM94360HMB (AW-CB160H) Combo card in it.
I was able to follow the guide for this model without issue:
http://www.tonymacx86.com/threads/success-scqs-intel-nuc-dc3217by-clover-el-capitan.176058/

I've been working through this post, any other one I can find, ...as well as:
http://www.tonymacx86.com/threads/guide-airport-pcie-half-mini-v2.104850/

I am stuck trying to get bluetooth to actually work. Its detected, listed in System Information, and the console logs show BRCMPatchRam2 loads, checks for firmware in the repo file (BCM20702A1_001.002.014.1443.1714_v5810.zhx) but the firmware upgrade is not needed. Bluetooth icon is available in System Prefs but scanning for devices or scanning from mobile devices for the NUC doesn't list anything. I did a little research before buying this particular card and wanted a combo since the NUC only has 3 USB ports. The combo card has 3 connectors and I have antennas on all. Wifi works fine, 5G patch applied and functional.

I thought maybe the hardware was bad but I installed Windows 10 and was able to detect and pair to my phone. I went back to 10.11.4 and then 10.11.5 and I'm then stuck in the same situation, everything looks to be working but I can't discover or pair anything. Any advice?

 

[RehabMan]

I have an Intel NUC DC3217BY with the BCM94360HMB (AW-CB160H) Combo card in it.
I was able to follow the guide for this model without issue:
http://www.tonymacx86.com/threads/success-scqs-intel-nuc-dc3217by-clover-el-capitan.176058/

I've been working through this post, any other one I can find, ...as well as:
http://www.tonymacx86.com/threads/guide-airport-pcie-half-mini-v2.104850/

I am stuck trying to get bluetooth to actually work. Its detected, listed in System Information, and the console logs show BRCMPatchRam2 loads, checks for firmware in the repo file (BCM20702A1_001.002.014.1443.1714_v5810.zhx) but the firmware upgrade is not needed. Bluetooth icon is available in System Prefs but scanning for devices or scanning from mobile devices for the NUC doesn't list anything. I did a little research before buying this particular card and wanted a combo since the NUC only has 3 USB ports. The combo card has 3 connectors and I have antennas on all. Wifi works fine, 5G patch applied and functional.

I thought maybe the hardware was bad but I installed Windows 10 and was able to detect and pair to my phone. I went back to 10.11.4 and then 10.11.5 and I'm then stuck in the same situation, everything looks to be working but I can't discover or pair anything. Any advice?

Firmware is only loaded on cold boot and on wake from sleep (eg. in situations where the firmware is not already on the device).

 

[slybobimous]

Firmware is only loaded on cold boot and on wake from sleep (eg. in situations where the firmware is not already on the device).

That makes sense that the firmware would be loaded in certain conditions, presumably at boot. Was there anything else you noticed in my logs or screenshots that seemed out of place?

 

[RehabMan]

That makes sense that the firmware would be loaded in certain conditions, presumably at boot. Was there anything else you noticed in my logs or screenshots that seemed out of place?

Does Windows load the same firmware?

 

[slybobimous]

Does Windows load the same firmware?

I was going down that road too. I used the Bluetooth Driver Package V12.0.1.650 (DriverVersion 12.0.1.653) for Windows 10 64bit.(WHQL) from asususa.com's support site during that test. I then took that package and identified the BCM20702A1_001.002.014.1443.1714.hex file in the inf ...which appeared to be the same as what you had in the BRCMFirmwareRepo. 12.0.0.9860 is what you have defined in the OSX-X-BrcmPatchRAM readme, is that still accurate? Im not sure if the firmware file version changed since the date stamp on that hex file was from Nov. 20th 2014 but it would be worth me trying to compress and add it just for the experience of it.

 

[RehabMan]

I was going down that road too. I used the Bluetooth Driver Package V12.0.1.650 (DriverVersion 12.0.1.653) for Windows 10 64bit.(WHQL) from asususa.com's support site during that test. I then took that package and identified the BCM20702A1_001.002.014.1443.1714.hex file in the inf ...which appeared to be the same as what you had in the BRCMFirmwareRepo. 12.0.0.9860 is what you have defined in the OSX-X-BrcmPatchRAM readme, is that still accurate? Im not sure if the firmware file version changed since the date stamp on that hex file was from Nov. 20th 2014 but it would be worth me trying to compress and add it just for the experience of it.

You can use Windows firmware just by restarting into OS X from Windows. Since firmware is already in the device, BrcmPatchRAM will not load new/different firmware.

 

[slybobimous]

You can use Windows firmware just by restarting into OS X from Windows. Since firmware is already in the device, BrcmPatchRAM will not load new/different firmware.

Im pretty sure the firmware on the device is the same in the windows driver package and in your latest repo.

I just booted into Windows 10, added the drivers and paired a BTaudio device. I then backed up a copy of C:\Windows\System32\Drivers\BCM20702A1_001.002.014.1443.1714.hex. I renamed it to 0b05_180a.hex (non-compressed) and placed in into the BrcmFirmwareRepo.kext\Contents\Resources directory. I deleted all of the original compressed firmware files as well. I then modified the BrcmPatchRAM2.kext\Contents\info.plist and removed the references for all "devices" except the 0b05_180a entry. Copied the kexts and cleared the caches. On reboot, I see similar console logs entries where it loads the non-compressed 0b05_180a.hex (confirmed it found and loaded the newer file), validates its IntelHex, FW update not needed, and then publishes the IOkit Personality. Same situation though, cant discover any devices. Based on that experiment I think I reduced the BrcmPatchRAM approach down to the most simplistic dictionary and ruled out a firmware-related problem.

 

[RehabMan]

Im pretty sure the firmware on the device is the same in the windows driver package and in your latest repo.

I just booted into Windows 10, added the drivers and paired a BTaudio device. I then backed up a copy of C:\Windows\System32\Drivers\BCM20702A1_001.002.014.1443.1714.hex. I renamed it to 0b05_180a.hex (non-compressed) and placed in into the BrcmFirmwareRepo.kext\Contents\Resources directory. I deleted all of the original compressed firmware files as well. I then modified the BrcmPatchRAM2.kext\Contents\info.plist and removed the references for all "devices" except the 0b05_180a entry. Copied the kexts and cleared the caches. On reboot, I see similar console logs entries where it loads the non-compressed 0b05_180a.hex (confirmed it found and loaded the newer file), validates its IntelHex, FW update not needed, and then publishes the IOkit Personality. Same situation though, cant discover any devices. Based on that experiment I think I reduced the BrcmPatchRAM approach down to the most simplistic dictionary and ruled out a firmware-related problem.

Sounds like an incompatible (with OS X) hardware/firmware...