BrcmPatchRAM - Upload firmware into Broadcom Bluetooth USB devices

[Wowfunhappy]

A bit of an edge case, but is it possible to manually force brcmpatchram to work its magic at some arbitrary point after boot time?

For compatibility with some other software, I sometimes need to run sudo kextunload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport. When I later bring it back with sudo kextload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport, OS X says Bluetooth isn't available. I'm not sure if BrcmPatchRam is at fault, but it seems like a plausible theory that I need to tell brcmpatchram to re-run somehow.

 

[UtterDisbelief]

A bit of an edge case, but is it possible to manually force bcrmpatchram to work its magic at some arbitrary point after boot time?

For compatibility with some other software, I sometimes need to run sudo kextunload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport. When I later bring it back with sudo kextload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport, OS X still says Bluetooth isn't available. I'm not sure if BrcmPatchRam is at fault, but it seems like a plausible theory that I need to tell the kext to re-run somehow.

Hi there.

It depends on which model Broadcom wireless/BT chip you are using. Not all need this patching to the firmware as it uploads each boot.

For native BT macOS's own software handles it invisibly. For less common chipsets the process of patching is needed.

 

[Wowfunhappy]

It depends on which model Broadcom wireless/BT chip you are using. Not all need this patching to the firmware as it uploads each boot.

Thank you—I know from experience that mine does need patching! It's an AzureWave AW-CE123H, and it doesn't work at all without bcrmpatchram.

With bcrmpatchram, it works fine, except when I manually unload the broadcomm kext so the adapter can be used by other software. When I later reload the broadcomm kext, the adapter does not start working again as expected—I have to fully reboot my machine to bring it back. I'm hoping that there's a command (or something?) I can run to tell bcrmpatchram to re-perform its magic.

 

[UtterDisbelief]

Thank you—I know from experience that mine does need patching! It's an AzureWave AW-CE123H, and it doesn't work at all without bcrmpatchram.

With bcrmpatchram, it works fine, except when I manually unload the broadcomm kext so the adapter can be used by other software. When I later reload the broadcomm kext, the adapter does not start working again as expected—I have to fully reboot my machine to bring it back. I'm hoping that there's a command (or something?) I can run to tell bcrmpatchram to re-perform its magic.

Fair enough

You clearly have enough tech knowledge to play constructively with Terminal so you've got that angle sorted. The process you are using is a little similar to the new developments in getting Intel wireless to work. The system can't be left to load the necessary kext itself, we have to do that manually from a running desktop.

You don't state which macOS, but maybe you are up against Catalina security blocking the re-loading of the kext?

I believe the Azurewave is the BCM94352HMB mini card. This requires the BrcmPtachRam3.kext to work with Catalina.

Here's a little more information, if it helps. By one of our expert Moderators @CaseySJ .

 

[Wowfunhappy]

You don't state which macOS, but maybe you are up against Catalina security blocking the re-loading of the kext?

I'm actually all the way back on 10.9 (because I like 10.9!), which is also why I'm using the original bcrmpatchram rather than bcrmpatchram2/3.

(The reason I'm unloading the kext in the first place is to get VirtualHere to work—it can't take control of the BT adapter unless the default kext is unloaded first. This is reported to work properly on real Macs.)

I may just need to buy a new wifi/bt card that doesn't require bcrmpatchram...