Andrw0380 Posted October 7, 2019 Share Posted October 7, 2019 8 hours ago, Mieze said: As BrcmPatchRAM3.kext depends on BrcmFirmwareData.kext, it is clear which one is first but with regard to the injector kext, I'm not sure but from my point of view it makes sense to put it in the third position. Mieze 8 hours ago, onemanOSX said: In OC I have the kexts in this order : BrcmBluetoothInjector>BrcmFirmwareData>BrcmPatchRAM3/2 Thanks I originally had it in the 3rd spot and with this new update, put it first and both worked. Since this new update only has the injector instead of incorporating the firmware files as well, think it makes more sense to do it first since it's a service that brcmpatchram3 depends on. I wanted to confirm. Link to comment Share on other sites More sharing options...
Mieze Posted October 8, 2019 Share Posted October 8, 2019 Ok, here is the latest build, version 2.3.0d1, in which I changed two things: Added an option to enforce handshake mode by setting bpr_preresetdelay=0 in order to test, if your device supports this mode of operation. Everybody is encouraged to try it. Please let me know, if it works on your device or not. Register for PM event notifications earlier in startup as it seems to speed up firmware upload a little bit. Good luck testing! BrcmPatchRAM3-V2.3.0d1.zip 3 Link to comment Share on other sites More sharing options...
Mieze Posted October 8, 2019 Share Posted October 8, 2019 Try it and if it works, fine, if it doesn't we'll know one device which is different! Link to comment Share on other sites More sharing options...
Sherlocks Posted October 8, 2019 Share Posted October 8, 2019 Ok, here is the latest build, version 2.3.0d1, in which I changed two things: Added an option to enforce handshake mode by setting bpr_preresetdelay=0 in order to test, if your device supports this mode of operation. Everybody is encouraged to try it. Please let me know, if it works on your device or not. Register for PM event notifications earlier in startup as it seems to speed up firmware upload a little bit. Good luck testing! BrcmPatchRAM3-V2.3.0d1.zipthanks for hard work. i will try and remains log.what is handshake? when sleeping, can we wake up to use bt mouse on system?나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
vanquybn Posted October 8, 2019 Share Posted October 8, 2019 I have tried, The BrcmFirmwareRepo.kext is not work for my card BCM94352z but BrcmFirmwareData.kext Link to comment Share on other sites More sharing options...
speedyrazor Posted October 8, 2019 Share Posted October 8, 2019 Hi, I am using an HP Probook 440 G5 with a BCM20702A0. I have been previously using Mojave with no issue with Wifi or Bluetooth, using Rehabmans excellent guide 'HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch'. Upgraded to Catalina, Wifi is fine, but no detected Bluetooth anymore. I came across your thread here, after reading, added both 'BrcmFirmwareRepo.kext' and 'BrcmPatchRAM2.kext' in Library/Extensions. Ran 'sudo kextcache -i /', rebooted, but still no Bluetooth device detected. I have attached a screen grab of my System Info. Any help would be greatly appreciated. Thanks. Link to comment Share on other sites More sharing options...
SchillerX Posted October 8, 2019 Share Posted October 8, 2019 (edited) 7 hours ago, speedyrazor said: Hi, I am using an HP Probook 440 G5 with a BCM20702A0. I have been previously using Mojave with no issue with Wifi or Bluetooth, using Rehabmans excellent guide 'HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch'. Upgraded to Catalina, Wifi is fine, but no detected Bluetooth anymore. I came across your thread here, after reading, added both 'BrcmFirmwareRepo.kext' and 'BrcmPatchRAM2.kext' in Library/Extensions. Ran 'sudo kextcache -i /', rebooted, but still no Bluetooth device detected. I have attached a screen grab of my System Info. Any help would be greatly appreciated. Thanks. Same here, HP EliteBook 840 G4, update to Catalina 10.15 from the App Store went OK, Bluetooth is not working.Wireless Card: DW1830I tried to load BT firmware with headkaze BrcmPatchRam forkWhat I already tried so far: BrcmBluetoothInjector.kext BrcmFirmwareData.kext BrcmPatchRAM2.kextload the 3 kexts in /EFI/Clover/kexts/Other -> leads to no bluetooth available load the 3 kexts in /Library/Extensions then fix permissions and rebuild cache then restart -> BT shows and kinda scans devices.. but I cannot connect any device and something new I've noticed is that the physical BT indicator in my laptop flashes when it is scanning or trying to connect to something, never happened in previous macOS versions. Handoff works... BT firmware fails to load with kexts in /L/E I guess... Firmware Version: v5 c4096 Am I missing something else? Here's my boot log bootlog.txt Any help is appreciated, thanks. Edited October 8, 2019 by SchillerX image too big Link to comment Share on other sites More sharing options...
PAIDEIM Posted October 9, 2019 Share Posted October 9, 2019 I don't understand the first part of the 1st post. I copied the BrcmFirmwareData, BrcmPatchRAM2 and the BrcmBluetooth injector and paste them in EFI/CLOVER/kexts/Other. Am I supossed to do something more? DW1560 Thanks for your job Link to comment Share on other sites More sharing options...
Sherlocks Posted October 9, 2019 Share Posted October 9, 2019 (edited) On 10/8/2019 at 9:36 AM, Mieze said: Ok, here is the latest build, version 2.3.0d1, in which I changed two things: Added an option to enforce handshake mode by setting bpr_preresetdelay=0 in order to test, if your device supports this mode of operation. Everybody is encouraged to try it. Please let me know, if it works on your device or not. Register for PM event notifications earlier in startup as it seems to speed up firmware upload a little bit. Good luck testing! BrcmPatchRAM3-V2.3.0d1.zip here is log. system power off -> fresh boot. Spoiler Timestamp (process)[PID] 2019-10-09 10:25:28.824580+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware store start 2019-10-09 10:25:36.864702+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:25:36.865409+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 10:25:37.311096+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:25:37.315707+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 10:25:37.343663+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:25:37.378137+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 10:25:37.494576+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:25:37.494796+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20702A1_001.002.014.1483.1651_v5747". 2019-10-09 10:25:37.495429+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Decompressed firmware (29732 bytes --> 70201 bytes). 2019-10-09 10:25:37.540111+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-09 10:25:37.540415+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: start 2019-10-09 10:25:37.556734+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 10:25:37.650677+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: USB [ACD1B8E2A4D0 v274] "BCM20702A0" by "Broadcom Corp" 2019-10-09 10:25:37.650865+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Available composite configurations: 1. 2019-10-09 10:25:37.652825+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Set device configuration to configuration index 0 successfully. 2019-10-09 10:25:37.662525+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: USBDeviceShim::findFirstInterface 2019-10-09 10:25:37.662746+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: getValidatedInterface returns <private> 2019-10-09 10:25:37.662968+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Interface 0 (class ff, subclass 01, protocol 01) located. 2019-10-09 10:25:37.663204+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: set configuration and interface opened 2019-10-09 10:25:37.663399+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: findPipe: direction = 1, type = 3 2019-10-09 10:25:37.674045+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-09 10:25:37.674178+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: found matching endpoint 2019-10-09 10:25:37.674667+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: findPipe: direction = 0, type = 2 2019-10-09 10:25:37.685481+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-09 10:25:37.685670+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2 2019-10-09 10:25:37.685885+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2 2019-10-09 10:25:37.686101+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: found matching endpoint 2019-10-09 10:25:37.697385+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: got pipes 2019-10-09 10:25:37.708501+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Unknown" --> "Initialize". 2019-10-09 10:25:37.720570+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes). 2019-10-09 10:25:37.836581+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Firmware version: v4096. 2019-10-09 10:25:37.857918+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Initialize" --> "Firmware version". 2019-10-09 10:25:37.879200+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: getFirmware 2019-10-09 10:25:37.879648+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Retrieved cached firmware for "BCM20702A1_001.002.014.1483.1651_v5747". 2019-10-09 10:25:38.006832+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: DOWNLOAD MINIDRIVER complete (status: 0x00, length: 4 bytes). 2019-10-09 10:25:38.017672+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Firmware version" --> "Mini-driver complete". 2019-10-09 10:25:38.953655+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: END OF RECORD complete (status: 0x00, length: 4 bytes). 2019-10-09 10:25:38.966405+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Instruction write" --> "Firmware written". 2019-10-09 10:25:39.625650+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Vendor specific event. Ready to reset device. 2019-10-09 10:25:39.686402+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Firmware written" --> "Firmware written". 2019-10-09 10:25:39.720595+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: RESET complete (status: 0x00, length: 4 bytes). 2019-10-09 10:25:39.732967+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Firmware written" --> "Reset complete". 2019-10-09 10:25:39.762614+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Device reset. 2019-10-09 10:25:39.775138+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Device status 0x00000003. 2019-10-09 10:25:39.787200+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Reset complete" --> "Update complete". 2019-10-09 10:25:39.799822+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Firmware upgrade completed successfully. 2019-10-09 10:25:39.812116+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Processing time 2.261 seconds. next log : power off system. boot fresh win7, then reboot, boot 10.15 catalina. Spoiler Timestamp (process)[PID] 2019-10-09 10:31:37.787750+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware store start 2019-10-09 10:31:45.983464+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:31:45.993096+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 10:31:46.379022+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:31:46.381100+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 10:31:46.435850+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:31:46.537031+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 10:31:46.626346+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 10:31:46.635798+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20702A1_001.002.014.1483.1651_v5747". 2019-10-09 10:31:46.658997+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Decompressed firmware (29732 bytes --> 70201 bytes). 2019-10-09 10:31:46.659549+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-09 10:31:46.659640+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: start 2019-10-09 10:31:46.659858+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 10:31:46.765301+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: USB [ACD1B8E2A4D0 v274] "BCM20702A0" by "Broadcom Corp" 2019-10-09 10:31:46.765704+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Available composite configurations: 1. 2019-10-09 10:31:46.778784+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Set device configuration to configuration index 0 successfully. 2019-10-09 10:31:46.799491+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: USBDeviceShim::findFirstInterface 2019-10-09 10:31:46.810654+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: getValidatedInterface returns <private> 2019-10-09 10:31:46.811950+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Interface 0 (class ff, subclass 01, protocol 01) located. 2019-10-09 10:31:46.911996+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: set configuration and interface opened 2019-10-09 10:31:46.922671+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: findPipe: direction = 1, type = 3 2019-10-09 10:31:46.933834+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-09 10:31:46.935144+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: found matching endpoint 2019-10-09 10:31:46.967055+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: findPipe: direction = 0, type = 2 2019-10-09 10:31:46.979135+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-09 10:31:46.999386+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2 2019-10-09 10:31:47.000461+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2 2019-10-09 10:31:47.060226+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: found matching endpoint 2019-10-09 10:31:47.071428+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: got pipes 2019-10-09 10:31:47.082335+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Unknown" --> "Initialize". 2019-10-09 10:31:47.109848+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes). 2019-10-09 10:31:47.120942+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Firmware version: v5820. 2019-10-09 10:31:47.175855+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: State "Initialize" --> "Update not needed". 2019-10-09 10:31:47.209330+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: [0489:e07a]: Firmware upgrade not needed. 2019-10-09 10:31:47.221202+0900 localhost kernel[0]: (kernel) BrcmPatchRAM: Processing time 0.561 seconds. Edited October 9, 2019 by Sherlocks 1 Link to comment Share on other sites More sharing options...
DavideSuriano05 Posted October 9, 2019 Share Posted October 9, 2019 On 10/8/2019 at 12:27 PM, speedyrazor said: Hi, I am using an HP Probook 440 G5 with a BCM20702A0. I have been previously using Mojave with no issue with Wifi or Bluetooth, using Rehabmans excellent guide 'HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch'. Upgraded to Catalina, Wifi is fine, but no detected Bluetooth anymore. I came across your thread here, after reading, added both 'BrcmFirmwareRepo.kext' and 'BrcmPatchRAM2.kext' in Library/Extensions. Ran 'sudo kextcache -i /', rebooted, but still no Bluetooth device detected. I have attached a screen grab of my System Info. Any help would be greatly appreciated. Thanks. I have same problem but i have BCM94352Z. I put in Library/Extensions --> BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext , BrcmPatchRAM3.kext v. 2.03.1b1 Link to comment Share on other sites More sharing options...
Mieze Posted October 9, 2019 Share Posted October 9, 2019 Post kernel logs extracted with log show --predicate 'processID==0' --last 10m | grep BrcmPatch so that I can find out what is going on. 1 Link to comment Share on other sites More sharing options...
Mieze Posted October 9, 2019 Share Posted October 9, 2019 On 10/8/2019 at 8:18 AM, Sherlocks said: what is handshake? when sleeping, can we wake up to use bt mouse on system? What I call "handshake" is a mechanism which eliminates the need for boot parameter "bpr_preresetdelay" because it uses a message the BT controller sends to the host when it is ready to boot the uploaded firmware. In earlier versions this was decided by a fixed delay, "bpr_preresetdelay", which doesn't always work reliable causing BT to be unavailable after wakeup sometimes. I used to have this problem with my Dell Inspiron 13 5370. 1 Link to comment Share on other sites More sharing options...
speedyrazor Posted October 9, 2019 Share Posted October 9, 2019 17 minutes ago, Mieze said: Post kernel logs extracted with log show --predicate 'processID==0' --last 10m | grep BrcmPatch so that I can find out what is going on. Hi, running log show --predicate 'processID==0' --last 10m | grep BrcmPatch Shows nothing and produces no files. Link to comment Share on other sites More sharing options...
Mieze Posted October 9, 2019 Share Posted October 9, 2019 1 minute ago, speedyrazor said: Shows nothing and produces no files. Then there is no driver installed, or the driver doesn't load for some reason. Also keep in mind that it only extracts log entries of the last 10 minutes. Link to comment Share on other sites More sharing options...
speedyrazor Posted October 9, 2019 Share Posted October 9, 2019 2 minutes ago, Mieze said: Then there is no driver installed, or the driver doesn't load for some reason. Also keep in mind that it only extracts log entries of the last 10 minutes. Hmm, very odd, as I have in Library/Extensions: BrcmPatchRAM2.kext BrcmFirmwareRepo.kext BrcmFirmwareData.kext BrcmBluetoothInjector.kext And my Bluetooth is activated: Happy to provide any logs. Where can we go from here? Link to comment Share on other sites More sharing options...
Mieze Posted October 9, 2019 Share Posted October 9, 2019 3 minutes ago, speedyrazor said: BrcmFirmwareData.kext Remove it because you must only have one of both data kexts installed. BrcmFirmwareData.kext or BrcmFirmwareRepo.kext but not both! Try to load BrcmPatchRAM2.kext manually with sudo kextutil -v 5 /Library/Extensions/BrcmPatchRAM2.kext and check the output. Link to comment Share on other sites More sharing options...
Fuu Posted October 9, 2019 Share Posted October 9, 2019 On 10/8/2019 at 7:36 AM, Mieze said: Ok, here is the latest build, version 2.3.0d1, in which I changed two things: Added an option to enforce handshake mode by setting bpr_preresetdelay=0 in order to test, if your device supports this mode of operation. Everybody is encouraged to try it. Please let me know, if it works on your device or not. Register for PM event notifications earlier in startup as it seems to speed up firmware upload a little bit. Good luck testing! BrcmPatchRAM3-V2.3.0d1.zip Thanks for your hard work, my laptop get better power management with your patch, i'm using OpenCore 0.5.1 with BrcmBluetoothInjector.kext > BrcmFirmwareData.kext > BrcmPatchRAM3.kext 2 Link to comment Share on other sites More sharing options...
speedyrazor Posted October 9, 2019 Share Posted October 9, 2019 1 hour ago, Mieze said: Remove it because you must only have one of both data kexts installed. BrcmFirmwareData.kext or BrcmFirmwareRepo.kext but not both! Try to load BrcmPatchRAM2.kext manually with sudo kextutil -v 5 /Library/Extensions/BrcmPatchRAM2.kext and check the output. OK, after removing BrcmFirmwareData.kext, rebuilt cache, rebooted, then running 'log show --predicate 'processID==0' --last 10m | grep BrcmPatch', I get: Quote kevins-MacBook-ProBook:~ kevin$ log show --predicate 'processID==0' --last 10m | grep BrcmPatch 2019-10-09 14:35:21.953537+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Version 2.2.12 starting on OS X Darwin 19.0. 2019-10-09 14:35:21.953543+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Unknown new Darwin version 19.0, using possible compatible personality. 2019-10-09 14:35:23.978202+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: BrcmPatchRAMResidency does not appear to be available. 2019-10-09 14:35:24.102302+0100 0x461 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1483.1651_v5747.zhx" from resources. 2019-10-09 14:35:24.102629+0100 0x461 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29732 bytes --> 70201 bytes). 2019-10-09 14:35:24.102925+0100 0x461 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-09 14:35:24.102944+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: uploadFirmware could not open the device! 2019-10-09 14:35:24.102946+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Processing time 2.149 seconds. 2019-10-09 14:35:24.104418+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Version 2.2.12 starting on OS X Darwin 19.0. 2019-10-09 14:35:26.105537+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: BrcmPatchRAMResidency does not appear to be available. 2019-10-09 14:35:26.105621+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: uploadFirmware could not open the device! 2019-10-09 14:35:26.105629+0100 0x461 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Processing time 2.1 seconds. Link to comment Share on other sites More sharing options...
junaed.rx Posted October 9, 2019 Share Posted October 9, 2019 Log from fresh boot on Mojave 10.14.6: Spoiler ➜ ~ log show --predicate 'processID==0' --last 10m | grep BrcmPatch 2019-10-09 19:38:45.739770+0600 0x73 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Firmware store start 2019-10-09 19:38:46.370064+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: init 2019-10-09 19:38:46.370080+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: probe 2019-10-09 19:38:46.370084+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Version 2.3.0d1 starting on OS X Darwin 18.7. 2019-10-09 19:38:46.370096+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Device supports handshake. 2019-10-09 19:38:49.786347+0600 0x200 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 19:38:49.786442+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 19:38:49.938415+0600 0x200 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 19:38:49.938486+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 19:38:49.973035+0600 0x200 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 19:38:49.973105+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-09 19:38:49.994909+0600 0x200 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-09 19:38:49.994970+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM4350C5_003.006.007.0222.4689_v8785". 2019-10-09 19:38:49.995281+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Decompressed firmware (12582 bytes --> 31740 bytes). 2019-10-09 19:38:49.995494+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-09 19:38:49.995557+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: start 2019-10-09 19:38:49.995618+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:38:50.095819+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: USB [5800E3402E5A v274] "BCM2045A0" by "Broadcom Corp" 2019-10-09 19:38:50.095826+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Available composite configurations: 1. 2019-10-09 19:38:50.097301+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Set device configuration to configuration index 0 successfully. 2019-10-09 19:38:50.097308+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: USBDeviceShim::findFirstInterface 2019-10-09 19:38:50.097314+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: getValidatedInterface returns <private> 2019-10-09 19:38:50.097319+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Interface 0 (class ff, subclass 01, protocol 01) located. 2019-10-09 19:38:50.097338+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: set configuration and interface opened 2019-10-09 19:38:50.097341+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: findPipe: direction = 1, type = 3 2019-10-09 19:38:50.097345+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-09 19:38:50.097348+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: found matching endpoint 2019-10-09 19:38:50.097543+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: findPipe: direction = 0, type = 2 2019-10-09 19:38:50.097548+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-09 19:38:50.097552+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2 2019-10-09 19:38:50.097556+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2 2019-10-09 19:38:50.097559+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: found matching endpoint 2019-10-09 19:38:50.097742+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: got pipes 2019-10-09 19:38:50.097747+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: State "Unknown" --> "Initialize". 2019-10-09 19:38:50.100160+0600 0x135 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes). 2019-10-09 19:38:50.100167+0600 0x135 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Firmware version: v4096. 2019-10-09 19:38:50.100200+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: State "Initialize" --> "Firmware version". 2019-10-09 19:38:50.100206+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: getFirmware 2019-10-09 19:38:50.100212+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Retrieved cached firmware for "BCM4350C5_003.006.007.0222.4689_v8785". 2019-10-09 19:38:50.101333+0600 0x135 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: DOWNLOAD MINIDRIVER complete (status: 0x00, length: 4 bytes). 2019-10-09 19:38:50.101344+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: State "Firmware version" --> "Mini-driver complete". 2019-10-09 19:38:50.358346+0600 0x135 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: END OF RECORD complete (status: 0x00, length: 4 bytes). 2019-10-09 19:38:50.358361+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: State "Instruction write" --> "Firmware written". 2019-10-09 19:38:50.442366+0600 0x135 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Vendor specific event. Ready to reset device. 2019-10-09 19:38:50.442382+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: State "Firmware written" --> "Reset write". 2019-10-09 19:38:50.446351+0600 0x135 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: RESET complete (status: 0x00, length: 4 bytes). 2019-10-09 19:38:50.446367+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: State "Reset write" --> "Reset complete". 2019-10-09 19:38:50.447115+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Device reset. 2019-10-09 19:38:50.447227+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Device status 0x00000003. 2019-10-09 19:38:50.447233+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: State "Reset complete" --> "Update complete". 2019-10-09 19:38:50.447238+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: [0a5c:6412]: Firmware upgrade completed successfully. 2019-10-09 19:38:50.447264+0600 0x162 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Processing time 0.451 seconds. 2019-10-09 19:39:02.573731+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:02.573938+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:03.133253+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:03.133462+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:03.695029+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:03.695210+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:04.254084+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:04.254294+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:04.762455+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:04.762782+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:05.309979+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:05.310373+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:05.841591+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:05.842210+0600 0x436 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:33.258957+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:33.259142+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:33.774835+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:33.775053+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:34.278217+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:34.278450+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:34.799553+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:34.799836+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:35.344990+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:35.345343+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:35.903295+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:35.903452+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:36.461750+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:36.461988+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:37.018907+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:37.019097+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:37.564787+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:37.565119+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:38.065597+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:38.065839+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:38.621180+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:38.621509+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:39.148201+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:39.148546+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:39.709119+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:39.709442+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:40.270536+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:40.270862+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:40.814699+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:40.815027+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:41.373541+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:41.373742+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:41.934846+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:41.935183+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:42.440224+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:42.440490+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:42.997968+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:42.998321+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:43.561015+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:43.561403+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:44.116316+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:44.116628+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:44.618293+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:44.618621+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:45.144949+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:45.145285+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:45.691644+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:45.691981+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:46.248510+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:46.248811+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:46.789358+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:46.789570+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:47.327776+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:47.328098+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-09 19:39:47.887114+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-09 19:39:47.887601+0600 0x157 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: setPowerState: which = 0x1 ➜ ~ log show --predicate 'processID==0' --last 10m | grep BrcmPatch 1 Link to comment Share on other sites More sharing options...
SchillerX Posted October 9, 2019 Share Posted October 9, 2019 (edited) @Mieze Thanks for your great work. I've tried your kexts and here's my result. WiFi + BT Card: Dell Wireless 1830 A,B,G,N,AC WLAN+BT NGFF Card BCM943602BAED (GKCG2 For XPS 15 9550) Laptop: HP EliteBook 840 G4 macOS Catalina 10.15 Log: ➜ Alex uptime 9:25 up 32 mins, 2 users, load averages: 2.35 2.38 2.63 ➜ Alex log show --predicate 'processID==0' --last 32m | grep BrcmPatch 2019-10-09 08:56:37.234043-0500 0x1824 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d1 starting on OS X Darwin 19.0. 2019-10-09 08:56:39.234102-0500 0x1824 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: BrcmPatchRAMResidency does not appear to be available. 2019-10-09 08:56:39.328442-0500 0x1824 Default 0x0 0 0 kernel: (BrcmFirmwareData) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20703A1_001.001.005.0214.0422_v4518". 2019-10-09 08:56:39.329193-0500 0x1824 Default 0x0 0 0 kernel: (BrcmFirmwareData) BrcmPatchRAM: Decompressed firmware (43444 bytes --> 109080 bytes). 2019-10-09 08:56:39.329956-0500 0x1824 Default 0x0 0 0 kernel: (BrcmFirmwareData) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-09 08:56:39.430188-0500 0x1824 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: USB [441CA8E34E56 v274] "BCM920703 Bluetooth 4.1" by "Broadcom Corp" 2019-10-09 08:56:39.455410-0500 0x1824 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware upgrade not needed. 2019-10-09 08:56:39.455455-0500 0x1824 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.125 seconds. I had BT at this point or so I thought, the icon was there and then I put it to scan for new devices (magic trackpad 2) and tried to connect to already paired ones with no results, no new devices were shown and it was unable to connect to any of the other ones. Then I pressed option ⌥ + shift + click the Bluetooth icon in the status bar then Debug -> Reset the Bluetooth module. This made BT functional and it immediately scanned for the trackpad and paired with no problems, it now also connects to the other devices previously paired. Is there any bluetooth log I can check to see what's going on? BT information says my firmware is v5 c4518, is that ok? the logs show firmware upgrade was not needed Edited October 9, 2019 by SchillerX typos + specs 1 Link to comment Share on other sites More sharing options...
Mieze Posted October 9, 2019 Share Posted October 9, 2019 @SchillerX Firmware upgrades usually survive a warm boot so that there is no need to upgrade again. In order to get more logs, use the debug version of the kext and perform a cold boot. @speedyrazor Remove headkaze's kexts completely and try mine (BrcmPatchRAM3.kext, version 2.3.0d1) from this thread. Install BrcmPatchRAM3.kext, BrcmFirmwareRepo.kext and BrcmBluetoothInjector.kext to /L/E. Make sure that you don't mix headkaze's kexts with mine as this won't work. Link to comment Share on other sites More sharing options...
speedyrazor Posted October 9, 2019 Share Posted October 9, 2019 3 hours ago, Mieze said: @speedyrazor Remove headkaze's kexts completely and try mine (BrcmPatchRAM3.kext, version 2.3.0d1) from this thread. Install BrcmPatchRAM3.kext, BrcmFirmwareRepo.kext and BrcmBluetoothInjector.kext to /L/E. Make sure that you don't mix headkaze's kexts with mine as this won't work. FANTASTIC!! thats works, thank you so much. My Bluetooth is now working correctly again. Just to confirm I am using: BrcmPatchRAM3.kext BrcmFirmwareRepo.kext BrcmBluetoothInjector.kext In /L/E, all yours. Thanks again 1 Link to comment Share on other sites More sharing options...
barrrrt Posted October 9, 2019 Share Posted October 9, 2019 (edited) i am a bit confused. I did put the files in the Clover --- others folder and when I use the command you posted above I get the following response: 2019-10-09 23:29:25.083504+0200 0x170 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20702A1_001.002.014.1443.1572_v5668". 2019-10-09 23:29:25.083823+0200 0x170 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Decompressed firmware (29651 bytes --> 70012 bytes). 2019-10-09 23:29:25.084112+0200 0x170 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-09 23:29:25.084135+0200 0x170 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:216f]: USB [C48E8FF40E12 v274] "BCM20702A0" by "Broadcom Corp" 2019-10-09 23:29:25.086697+0200 0x170 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:216f]: continuousRead - Failed to queue read (0xe00002c2) But I used YOUR files... so.. shouldn't I get a response with anything like BrcmPatchRAM3? Edited October 9, 2019 by barrrrt Link to comment Share on other sites More sharing options...
Mieze Posted October 9, 2019 Share Posted October 9, 2019 I haven't been lazy today, here is version 2.3.0d2. I improved some details of the driver: Changed SDK and deployment target to 10.11 in order to maintain compatibility with older versions of macOS. In case you are upgrading from an earlier version I posted here in the thread during the last days, please make sure to replace all kexts with the new ones (BrcmPatchRAM3.kext, BrcmFirmwareRepo.kext or BrcmFirmwareData.kext, BrcmBluetoothInjector.kext). Mixing kexts of different versions won't work. Improved error handling so that the driver better recovers from error conditions during firmware upgrade. Good luck testing! Mieze BrcmPatchRAM3-V2.3.0d2.zip 7 Link to comment Share on other sites More sharing options...
Mieze Posted October 9, 2019 Share Posted October 9, 2019 @barrrrt Most likely you forgot to recreate the kernel cache or you've still got the old ones in the 10.15 folder? Link to comment Share on other sites More sharing options...
Recommended Posts