Brcm20702 Hub Driver

15-09-2021

Brcm20702 Hub Driver

Brcm20702 Hub Driver Mac
Bcm20702a0 Hub Driver Kit

: systemprofiler SPUSBDataType USB: USB 3.0 Bus: Host Controller Driver: AppleUSBXHCIWPT PCI Device ID: 0x9cb1 PCI Revision ID: 0x0003 PCI Vendor ID: 0x8086 BRCM20702 Hub: Product ID: 0x4500 Vendor ID: 0x0a5c (Broadcom Corp.) Version: 1.00 Speed: Up to 12 Mb/sec Manufacturer: Apple Inc. Location ID: 0x14300000 / 2 Current Available (mA): 500. Amazon.com: Anker 4-Port USB 3.0 Hub, Ultra-Slim Data USB Hub with 2 ft Extended Cable Charging Not Supported, for MacBook, Mac Pro, Mac mini, iMac, Surface Pro, XPS, PC, Flash Drive, Mobile HDD: MP3 Players & Accessories. Launch a terminal/shell; ioreg -p IOUSB -w0; ioreg -p IOUSB -w0 -l: For more info +-o Root +-o Root Hub Simulation Simulation@14000000 +-o USB2.0 Hub @14100000. With their driver installed, the BCM20702A0 under 'Other Devices' disappeared and all the right things appeared under 'Bluetooth' in the Device Manager. Since BCM20702A0 under Other Devices showed up when I first plugged the Plugable adapter in, it appears that both the Best Buy Insignia one and the Plugable one use the same chip.

In case your USB to Serial is not working, you can try the followingsteps find and solve the problem.

0. Is the device connected and recognized¶

The first step is to actually check if the USB serial device isconnected to your mac and recognized by OS X as USB Device.

Make sure you have all cables plugged in and open System Info toverify your device is connected:

Alternatively, you can use the command line to list all USB devicesconnected to your mac:

This check is not dependent on any driver, and only verifies if OS X recognizes the device at USB level.If the device doesn’t show up, it is either a broken cable or broken chip.

Make sure you use a fully wired micro-USB cable!

Since the introduction of micro-USB, some USB cables are not fullywired. You might have a charge-only cable. In that case the device willnever work. You can check it, when you connect the device via this cableit will never pop-up in the lists above.

1. Remove Conflicting Driver¶

When you connect a device to you Mac, OS X searches for theappropriate driver via a matching algorithm. In case of a USB device,OS X uses the vendor id and product id of the device to load the rightdriver. However, if multiple drivers are registered for a certaindevice, the matching algorithm becomes arbitrary. You will confrontedwith not working devices or strange behavior.

In the newest 3.0+ drivers we avoid this by setting a higher priorityin the matching results, however, it might be better to have noconflicts at all.

To check which drivers are installed, run the following command in theterminal application:

This commands detects installed drivers. It is necessary to have adminrights, so the sudo command is necessary. Alternatively you can list thedirectories /Library/Extensions and /System/Library/Extensions,and search for the installed kexts.

If you install our drivers then they should be installed in one of thefollowing directories:

/Library/Extensions/osx-ch341.kext
/Library/Extensions/osx-pl2303.kext
/Library/Extensions/osx-cp2102.kext

For OS X 10.8 and earlier

/System/Library/Extensions/osx-ch341.kext
/System/Library/Extensions/osx-pl2303.kext

When no conflicting drivers are installed, the output on OS X 10.9+should look like:

In case you have found conflicting drivers, like theProlificUsbSerial.kext (Prolific) or usb.kext (Winchiphead), you shouldremove them. Execute the following steps in the terminal:

cd/<_path_where_conflicting_driver_is_located_>/
sudokextunload./<name>.kext
sudorm-rf<name>.kext

The kextunload command may fail if the driver is not loaded. It may benecessary to reboot the mac to be sure the kexts are not loaded into thekernel.

2. Test If the Driver is Loaded¶

Next step is to check if the driver is loaded. Connect your USB toserial cable to your mac and execute the following command in Terminal:sudokextstat|greprepleo

If you don’t see a driver, please make sure it is loaded by using thecommands:

cd/library/extensions/
sudokextload ./<name>.kext

Alternatively, rebooting your mac will also load the drivers. If youdon’t see the driver, it is possible you don’t own a supported device,or the driver is not loaded properly. Try to load the driver with theverbose command: sudokextutil-v6 ./<nameofkext>.kext in the directory/library/extensions, inspect the output of sudodmesg andcontact us via support@mac-usb-serial.com for further assistance.

Since OS X High Sierra, you need to explicitly allow the drivers in the Security & Privacy pane of System Preferences.You will get a dialog System Extension Blocked during installation, which alerts you to approve the driver.

In case the sudokextutil-v6 ./<nameofkext>.kext command shows the line:

You still need to approve the driver. This approval UI is only present in the Security & Privacy preferences panefor 30 minutes after the alert.The gatekeeper pane in System Preferences looks like:

Our Team Identifier for the gatekeeper is: C3V2MXS8TG (BJA Electronics). When you have approved the driver, you mightneed to reboot your machine. Click with a normal mouse, without emulating software. Apple is strict on this.

Until you approved the KEXT, future load attempts will cause the approval button in the Security & Privacy pane to reappear but will not triggeranother user alert. You can trigger it by these commands:

sudospctl--add--label'Repleo'
sudospctl--enable--label'Repleo'

You can verify the driver is allowed by:

In case this doesnot work, you can try to trigger the gatekeeper by loading the driver via kextutil, or rebooting your mac.

3. Test If the Device is Recognized¶

When the kext is loaded properly, it should instantiate the .cu and .ttyhandles. You can verify this using the terminal with the following tocommands:

sudodmesg|greprepleo
ls/dev|grepRepleo

The log files (via dmesg) shows is the driver is correctly allocated.The ls command shows if the .cu and .tty are loaded. If an erroroccurs it is also visible via the dmesg. Please contact us in case you see an error,and send us the dmesg output with this error for further assistance.

4. Test the Serial Interface with a Loopback¶

The last test is to verify the driver is really able to send and/orreceive data. Connect the RxD and TxD pin of the RS-233 connector, thiswill create a loopback. Any character transmitted from your Mac shouldalso be echoed into the terminal. Use a simple tool like CoolTerm to verify if data is transmitted.

In case no data is received, it is important that is not a hardwarefailure. Please test the setup using Windows or Linux to ensure thehardware is operating correctly. If the hardware is not the problem, youcan contact us for assistance.

Please include all the steps you did to determine the cause of theproblem.

03-10-2016, 06:19 AM

(05-04-2015, 04:42 PM)jackoalan Wrote: Hello!
I'm a developer running the master branch of Dolphin on OS X 10.10.

I was disappointed to discover that the GCN smash-adapter is unsupported (according to the wiki article)..
After some investigation, I determined that the cause of the problem is Apple's HID driver seizing the adapter, preventing dolphin's libusb integration from opening a handle to it.
I've written a codeless .kext file that pre-empts IOKit from loading the HID driver, instead leaving the adapter's endpoints open for any userspace application to use. No modification to dolphin necessary!!
It works on my system (seemingly without having to disable Gatekeeper signature-validation), although I want some verification from other OS X users first..
Installation instructions: