BrcmPatchRAM - Upload firmware into Broadcom Bluetooth USB devices

[the-darkvoid]

Device request error 404f means the device was not reachable on the bus.

That seems to indicate a problem with your USB.

Currently I do not have USB dongles to try against BrcmPatchRAM myself, but I ordered some to do testing/development.

 

[gus305]

Thank you very much for your help and time dedicated to this case. I'll try to fix the usb issue on my end and see what happened.

 

[kaminoreal]

Sorry, v.0,7 is broken, you can check with kextlibs and see that 2 symbols are missing, they are printed in log when kext is loaded on 10.9/10.10(that I tested).
Not sure how we can mix in the snow support.

 

[the-darkvoid]

Kaminoreal,

v0.7 is working fine for me and other people on Yosemite.
Are you sure you haven't edited the .plist files?

 

[kaminoreal]

It still works but prints the errors in log, after it fails to load twice.
I used those form your git, precompiled, untouched.
Maybe something broken on my end...
Will double check.

 

[Skvo]

New devices

In order to support a new device, the firmware for the device needs to be extracted from existing Windows drivers.

A copy of the (current) latest Broadcom USB bluetooth drivers can be found here: http://drivers.softpedia.com/get/BL...etooth-Driver-6515800-12009860.shtml#download

Should you come across newer drivers than 12.0.0.9860, please let me know.

Broadcom Bluetooth 2070/20702 Drivers Version 12.0.0.9980
http://www.station-drivers.com/index.php/outils/func-startdown/1136/

 

[the-darkvoid]

Thanks skvo, I will check which firmwares are updated and commit any updates to github.

 

[the-darkvoid]

BrcmPatchRAM is now updated to v0.8.

Thanks to skvo for pointing out the availability of new firmware versions.

Version v0.8:

• This version of BrcmPatchRAM is using an event-driven continuous read model.
  Boot-up time with the bluetooth device plugged in should be significantly faster.
  
  
  The event-driven driver model is new and testing feedback is highly appreciated.
  Report any issues using the GitHub issues functionality on the BrcmPatchRAM repository.
  
  
  
• This release is extensively tested against:
  
  
  0930:0223 Toshiba 20702A NGFF
  0a5c:21e8 iOGEAR GBU521 USB Dongle
  0b05:17cb Asus BT-400 USB Dongle
  
  
  
• Updated 0930:0223 Toshiba 20702A NGFF firmware to v5770
• Updated 04ca:200a LiteOn (4352 combo) firmware to 5769

 

[the-darkvoid]

BrcmPatchRAM has now been updated to version 1.0 with the following new functionalities:

• Compatibility with:
  • OS X Snow Leopard (64-bit only)
  • OS X Lion (64-bit only)
  • OS X Mountain Lion
  • OS X Mavericks
  • OS X Snow Leopard
  
  
  
• Added dynamic IOKit personality publishing for devices not present by default in OS X,
  this makes it easier to add new devices to the configuration.
• Added DisplayName IOKit personality property to allow specifying a name to display in USB devices
• BrcmNonApple.kext is now replaced by dynamic IOKit personality publishing & DisplayName functionality.
  It is now removed.
• Added process timing output

With this release BrcmPatchRAM has reached v1.0, and should be stable.

 

[kaminoreal]

• Compatibility with:
• OS X Snow Leopard (64-bit only)

Tested and works just fine but with lowered OSBundleLibraries, otherwise wont load.
There might be one thing for you to check, alternative loading location(not from /S/L/E)/injection, FirmwareStore cause trouble.

With this release BrcmPatchRAM has reached v1.0, and should be stable.

Indeed.

Thank You!