Jump to content
headkaze

BrcmPatchRAM2 for 10.15 Catalina (Broadcom bluetooth firmware upload)

382 posts in this topic

Recommended Posts

1 hour ago, MacKonsti said:

 

Hi @tonyx86 thanks for your message and suggestions; before this exercise, I wanted to test BTLE module that it works as expected, nevermind if it shows up OK on IOReg or System Info.

Unfortunately, it does not work.

Upon reboot, the device does see the neighbouring BT devices, when I tried to connect either Apple old Aluminum BT keyboard or my Logitech Anywhere MX2 BT mouse, it would not connect to them (pair).

Then all of a sudden, I lose all devices detected in System Preferences > Bluetooth list.

I switch off, on again after few seconds, nothing.

Despite kext loaded etc. the BT functionality is broken.

I suspect that, because I had booted before this test to Mojave where BT worked, the next reboot to Catalina had still BTLE module on and possibly pre-kept the detected devices?

I cannot know. What I see is that BCM20702A0 (from my Azurewave BCM94352HMB) does not work properly at all, in either /L/E/ or E/C/k/O :( despite being "detected" OK by the system.

Is this a firmware issue not being loaded OK from the kext? I am always getting v14 c4096... reminds me of pre-High-Sierra same problems, BTLE module seen by the system as hardware ID etc. but not connecting to ANY wireless device :(

 

 

Therefore to everyone, if on Catalina you see your BTLE module being detected OK but the firmware is not upgraded via BrcmFirmwareData.kext or BrcmFirmwareRepo.kext chances are that you will not connect (pair) any wireless device OK!

 

Something else is wrong with your config.  Can you run black.dragon74's gen_debug and post the problem reporting files?

Share this post


Link to post
Share on other sites
Advertisement
On 4/3/2020 at 7:29 AM, MacKonsti said:

I cannot know. What I see is that BCM20702A0 (from my Azurewave BCM94352HMB) does not work properly at all, in either /L/E/ or E/C/k/O :( despite being "detected" OK by the system.

 

When you place Brcm Bluetooth kexts in E/C/k/O, you must use BrcmFirmwareData.kext and NOT BrcmFirmwareRepo.kext.  BrcmFirmwareRepo.kext is to be used only when placing Brcm Bluetooth kexts in /L/E.

 

Remove BrcmFirmwareRepo.kext from E/C/k and replace with BrcmFirmwareData.kext.  Also, I have not tried using E/C/k/O and E/C/k/10.15 kext folders.  For this test, place all kexts in E/C/k/O and don't use E/C/k/10.15.

Share this post


Link to post
Share on other sites

I am building a Catalina, and I try to use 

- AirportBrcmFixup.kext

- BrcmBluetoothInjector.kext

- BrcmFirmwareData.kext

- BrcmPatchRAM3.kext

for my WiFi and Bluetooth card (BCM943224PCIEBT2) with a adaptor to replace my motherboard (MSI B450i Gaming AC)'s original one.

 

The WiFi is work good by the AirportBrcmFixup.kext , but the bluetooth is not work which is not show in my system.

 

I checked by the Hackintool, those kexts (BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext) are not install when system boot.

 

ref_1.png

ref_2.png

ref_3.png

Share this post


Link to post
Share on other sites
On 4/4/2020 at 4:49 PM, tonyx86 said:

When you place Brcm Bluetooth kexts in E/C/k/O, you must use BrcmFirmwareData.kext and NOT BrcmFirmwareRepo.kext.  BrcmFirmwareRepo.kext is to be used only when placing Brcm Bluetooth kexts in /L/E.

Remove BrcmFirmwareRepo.kext from E/C/k and replace with BrcmFirmwareData.kext.  Also, I have not tried using E/C/k/O and E/C/k/10.15 kext folders.  For this test, place all kexts in E/C/k/O and don't use E/C/k/10.15.

 

Hi @mansik not sure if you read the previous pages, try what @tonyx86 suggested, move all custom kexts to E/C/k/O and rebuild caches and restart... it worked for me flawlessly.

Edited by MacKonsti

Share this post


Link to post
Share on other sites
22 minutes ago, MacKonsti said:

 

Hi @mansik not sure if you read the previous pages, try what @tonyx86 suggested, move all custom kexts to E/C/k/O and rebuild caches and restart... it worked for me flawlessly.

@MacKonsti Thanks your reply..

Sorry, I didn't mentioned i am using OpenCore 0.5.6, I tried to remove all related kexts (Brcmxxxxx.kext), and add again. But after restart, its same.

Share this post


Link to post
Share on other sites

Hi Folks,

 

I have a bluetooth problem as well, and I'm trying to solved like 1 month now without success (and this is my 5th build).

 

So the thing is: I have a DW1560 (dell version of bcm94352z) and a Dell Latitude 5400 running Catalina 10.15.4

My bootloader is OpenCore 0.5.6.

 

The problem: The bluetooth is available, but searching is not working. I can see the device from my phone, I can pair with my magicmouse2 using cable, but the connection is poor and drops after ~10sec.

I've found a similiar forum thread, but no success there: https://www.tonymacx86.com/threads/dw1560-bluetooth-on-catalina-10-15-1.286412/

This exact problem existed with the same card in my previous build: Dell Latitude e5450 running Catalina 10.15.2 with Clover 5100.

However I don't think there is a HW failure because it works with a Windows VM.

 

I've found suspicious messages in the log but Google literally gave me nothing relevant:

2020-04-06 16:25:49.464384+0200 0x18f      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: END OF RECORD complete (status: 0x00, length: 4 bytes).
2020-04-06 16:25:49.469058+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: State "Instruction write" --> "Firmware written".
2020-04-06 16:25:49.518438+0200 0x18f      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: RESET complete (status: 0x00, length: 4 bytes).
2020-04-06 16:25:49.522104+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: State "Firmware written" --> "Reset complete".
2020-04-06 16:25:49.523829+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: Device reset.
2020-04-06 16:25:49.529529+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: Device status 0x00000003.
2020-04-06 16:25:49.543040+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: State "Reset complete" --> "Update complete".
2020-04-06 16:25:49.543245+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:21fb]: Firmware upgrade completed successfully.
2020-04-06 16:25:49.543675+0200 0x32a      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 1.308 seconds.
2020-04-06 16:26:10.455010+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:10.455317+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:11.014518+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:11.014745+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:11.576424+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:11.576736+0200 0x2a5      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:12.131987+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:12.132149+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:12.657499+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:12.657713+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
2020-04-06 16:26:13.217674+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
2020-04-06 16:26:13.217888+0200 0xe85      Default     0x0                  0      0    kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
[...setPowerState flips forever...]

 

I have installed the recent version of the necessary kexts, I have everything under OC/K (the base system is vanilla (SIP enabled)):

image.thumb.png.84c0c2257270b4948beba4d4005c16b6.png

 

The USB port patching is done: *EDIT: after one day sleep I reallized there is too many internal connector here... I'll update the post soon, but I don't think this is the problem.*

EDIT2: So I fixed it. Installed XHCI-unsupported, tried with SSDT and usbinjectall, no success. Went to USBPorts.kext method, works like a charm, altought I would prefer the SSDT one.

image.thumb.png.bc490494c146a82f6d1d534cccdb67dd.png

 

Device recognized, firmware is uploaded:

image.png.b424a95cdbe3e63a077a3ceb5e6668b2.png

 

 

Any help, idea, guidance would be really appreciated :)

Let me know if you need some more data for debugging.

 

Thank you,

cvigu

image.png

config.plist

opencore-2020-04-07-113052.txt

Edited by cvigu
stupid usb ports2

Share this post


Link to post
Share on other sites

I have upgraded to my Latitude E6410 to Catalina 10.15.4.  Bluetooth continues to work well with my Broadcom BCM 94352HMB and the kext installation listed below.  I am running CLOVER (Legacy) r5109.

  • CLOVER r5109 (Legacy): Inject Kexts = YES (not DETECT)
  • Kexts in E/C/k/O
    • BrcmFirmwareData.kext v2.5.1
    • BrcmPatchRAM3.kext v2.5.1
  • Kexts in /L/E
    • Lilu.kext v1.4.2
    • BrcmBluetoothInjector.kext v2.5.1
    • AirportBrcmFixup.kext v2.0.6
    • FakeSMC.kext v6.26
    • IntelMausiEthernet.kext v2.5.0
    • USBInjectAll.kext v0.7.1
    • VoodooPS2Controller.kext (Bronxteck) v6.0.0
    • ACPIBatteryManager.kext v1.90.1
    • FakeSMC_CPUSensor.kext v6.26
    • FakeSMC_GPUSensor.kext v6.26
Edited by tonyx86

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×