Bluetooth - BCM20702A0 Failed to write to bulk pipe

[5h4rk]

Hey, i have a problem with my bluetooth dongle. It seems that BrcmPatchRAM2 is loading the firmware in the Dongle, but there is a error while this process. Maybe i have a general USB Problem? What means "Failed to write to bulk pipe"? Has anyone a idea, thanks?


S/L/E BrcmFirmwareRepo.kext BrcmNonPatchRAM2.kext

OS X El Capitan 10.11.6

BCM20702A0:
Produkt-ID: 0x21ec
Hersteller-ID: 0x0a5c (Broadcom Corp.)
Version: 1.12
Seriennummer: 0019860023F6
Geschwindigkeit: Bis zu 12 MBit/s
Hersteller: Broadcom Corp

Syslog
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 15.6.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmFirmwareStore.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmPatchRAMResidency.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1460_v5556.zhx" from resources.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Decompressed firmware (29555 bytes --> 69721 bytes).
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Firmware is valid IntelHex firmware.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: USB [0019860023F6 v274] "BCM20702A0" by "Broadcom Corp"
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Firmware upgrade completed successfully.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Published new IOKit personality.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Processing time 0.130 seconds.
Aug 31 19:26:04 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 15.6.
Aug 31 19:26:04 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: USB [0019860023F6 v274] "BCM20702A0" by "Broadcom Corp"
Aug 31 19:26:32 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Failed to write to bulk pipe ("0xe00002ed (UNDEFINED)" 0xe00002ed).
Aug 31 19:26:33 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Not responding - Delaying next read.
Aug 31 19:26:33 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Failed to write to bulk pipe ("0xe00002d8 (UNDEFINED)" 0xe00002d8).
Aug 31 19:26:33 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: continuousRead - Failed to queue read (0xe00002d8)
Aug 31 20:30:06 Karmas-Mac-Pro com.apple.kextcache[747]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext

 

[RehabMan]

Hey, i have a problem with my bluetooth dongle. It seems that BrcmPatchRAM2 is loading the firmware in the Dongle, but there is a error while this process. Maybe i have a general USB Problem? What means "Failed to write to bulk pipe"? Has anyone a idea, thanks?


S/L/E BrcmFirmwareRepo.kext BrcmNonPatchRAM2.kext

OS X El Capitan 10.11.6

BCM20702A0:
Produkt-ID: 0x21ec
Hersteller-ID: 0x0a5c (Broadcom Corp.)
Version: 1.12
Seriennummer: 0019860023F6
Geschwindigkeit: Bis zu 12 MBit/s
Hersteller: Broadcom Corp

Syslog
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 15.6.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmFirmwareStore.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmPatchRAMResidency.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1460_v5556.zhx" from resources.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Decompressed firmware (29555 bytes --> 69721 bytes).
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Firmware is valid IntelHex firmware.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: USB [0019860023F6 v274] "BCM20702A0" by "Broadcom Corp"
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Firmware upgrade completed successfully.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Published new IOKit personality.
Aug 31 19:26:03 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Processing time 0.130 seconds.
Aug 31 19:26:04 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 15.6.
Aug 31 19:26:04 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: USB [0019860023F6 v274] "BCM20702A0" by "Broadcom Corp"
Aug 31 19:26:32 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Failed to write to bulk pipe ("0xe00002ed (UNDEFINED)" 0xe00002ed).
Aug 31 19:26:33 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Not responding - Delaying next read.
Aug 31 19:26:33 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Failed to write to bulk pipe ("0xe00002d8 (UNDEFINED)" 0xe00002d8).
Aug 31 19:26:33 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: continuousRead - Failed to queue read (0xe00002d8)
Aug 31 20:30:06 Karmas-Mac-Pro com.apple.kextcache[747]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext

Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

 

[5h4rk]

Well, here is my problem report with all requested datas.

 

[RehabMan]

Well, here is my problem report with all requested datas.

BrcmPatchRAM2 and BrcmFirmwareRepo are not even installed.

 

[5h4rk]

BrcmFirmwareRepo.kext and BrcmNonPatchRAM2.kext are in S/L/E. Is this wrong?

Karmas-Mac-Pro:Extensions karma$ ls -la | grep Brcm
drwxr-xr-x@   3 root  wheel   102 31 Aug 20:29 BrcmFirmwareRepo.kext
drwxr-xr-x@   3 root  wheel   102 31 Aug 20:29 BrcmNonPatchRAM2.kext

 

[RehabMan]

BrcmFirmwareRepo.kext and BrcmNonPatchRAM2.kext are in S/L/E. Is this wrong?

Karmas-Mac-Pro:Extensions karma$ ls -la | grep Brcm
drwxr-xr-x@   3 root  wheel   102 31 Aug 20:29 BrcmFirmwareRepo.kext
drwxr-xr-x@   3 root  wheel   102 31 Aug 20:29 BrcmNonPatchRAM2.kext

Your kextcache output does not list them.
The ioreg shows neither started.
Probably not installed correct.
Log is likely an old one from when they were installed (correctly).
Remove then re-install.

 

[5h4rk]

Okay, i tried the following:

removed kext from S/L/E
rebooted
reinstalled the kext with kextbeast
rebooted
-> Bluetooth was showing in the System Informations Settings and i was able zu receive a picture from a android mobile
i was happy, shutted the system down and went to bed
on the next day i booted the system and saw that OS X can't finding any bluetooth device Ò.o

Syslog looks like the firmware was loaded correct:

Sep  6 18:41:42 Karmas-Mac-Pro com.apple.kextd[45]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/BrcmPatchRAM2.kext"
Sep  6 18:41:43 Karmas-Mac-Pro com.apple.kextd[45]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/BrcmFirmwareRepo.kext"
Sep  6 18:41:43 Karmas-Mac-Pro com.apple.kextd[45]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/BrcmPatchRAM2.kext"
Sep  6 18:41:43 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 15.6.
Sep  6 18:41:43 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmFirmwareStore.
Sep  6 18:41:43 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmPatchRAMResidency.
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1460_v5556.zhx" from resources.
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Decompressed firmware (29555 bytes --> 69721 bytes).
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Firmware is valid IntelHex firmware.
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: USB [0019860023F6 v274] "BCM20702A0" by "Broadcom Corp"

kextcash looks also good:

IOKitWaitQuiet() timed out.
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext NullCPUPowerManagement.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_GPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AHCI_3rdParty_SATA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AtherosL1Ethernet.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ApplePCIIDE.kext
kext file:///System/Library/Extensions/AppleHDADisabler.kext/ is in hash exception list, allowing to load

after unplug and plug in again the dongle, i got this:

Sep  6 19:20:18 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Not responding - Delaying next read.
Sep  6 19:20:18 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Failed to write to bulk pipe ("0xe00002ed (UNDEFINED)" 0xe00002ed).
Sep  6 19:20:18 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: continuousRead - Failed to queue read (0xe00002d8)

 

[RehabMan]

Okay, i tried the following:

removed kext from S/L/E
rebooted
reinstalled the kext with kextbeast
rebooted
-> Bluetooth was showing in the System Informations Settings and i was able zu receive a picture from a android mobile
i was happy, shutted the system down and went to bed
on the next day i booted the system and saw that OS X can't finding any bluetooth device Ò.o

Syslog looks like the firmware was loaded correct:

Sep  6 18:41:42 Karmas-Mac-Pro com.apple.kextd[45]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/BrcmPatchRAM2.kext"
Sep  6 18:41:43 Karmas-Mac-Pro com.apple.kextd[45]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/BrcmFirmwareRepo.kext"
Sep  6 18:41:43 Karmas-Mac-Pro com.apple.kextd[45]: kext signature failure override allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/System/Library/Extensions/BrcmPatchRAM2.kext"
Sep  6 18:41:43 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 15.6.
Sep  6 18:41:43 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmFirmwareStore.
Sep  6 18:41:43 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmPatchRAMResidency.
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1460_v5556.zhx" from resources.
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Decompressed firmware (29555 bytes --> 69721 bytes).
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM: Firmware is valid IntelHex firmware.
Sep  6 18:41:48 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: USB [0019860023F6 v274] "BCM20702A0" by "Broadcom Corp"

kextcash looks also good:

IOKitWaitQuiet() timed out.
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext NullCPUPowerManagement.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_GPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AHCI_3rdParty_SATA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AtherosL1Ethernet.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ApplePCIIDE.kext
kext file:///System/Library/Extensions/AppleHDADisabler.kext/ is in hash exception list, allowing to load

after unplug and plug in again the dongle, i got this:

Sep  6 19:20:18 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Not responding - Delaying next read.
Sep  6 19:20:18 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: Failed to write to bulk pipe ("0xe00002ed (UNDEFINED)" 0xe00002ed).
Sep  6 19:20:18 Karmas-Mac-Pro kernel[0]: BrcmPatchRAM2: [0a5c:21ec]: continuousRead - Failed to queue read (0xe00002d8)

"Problem Reporting" files are incomplete.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

 

[5h4rk]

sorry

 

[RehabMan]

sorry

Your ioreg here shows no bluetooth on the USB bus. No sign that BrcmPatchRAM is even loaded. So the log you're showing must be from a different session, different configuration.