Bug #5463
closedVUSB FTDI KEXT not loading in Mac High Sierra
0%
Description
Just purchased BaoFeng UV-5R (https://www.amazon.com/gp/product/B0772FYKK8/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1) that comes with what I think is the official BaoFeng USB connector. I run on iMac (2011) with latest Mac OS 10.13.2. My UV-5R has firmware BFB297. Installed latest CHIRP (daily 20171228) and Python runtime (CHIRP launches), then installed the current VCP driver (2.4.2). Authenticated and I see the VCP KEXT in my /Library/Extensions directory. I see the FTDIUSBSerialDriver Extension listed in System Info as an Identified Developer but it is not loaded. Kextstatus does not list it as loaded. I don't have cu.usbserial-xxxxxx in the /dev directory.
I have tried installing the driver twice (second time no authentication needed.) Nothing changes when I plug in the USB cable, (turn on the UV-5R after plugging in).
CHIRP does not show the usbserial as a port, it only shows dev/cu.Bluetooth-Incoming-Port, /dev/cu.lolita-SPPDev, /dev/cu.lolita-SPPDev-1 ports. I've tried all of these and the bluetooth "does not respond" and the other two are "busy".
I am assuming the problem is somehow related to the FTDIUSBSerialDriver KEXT not loading, could that be correct? Does CHIRP cause the load to occur?
Updated by Jeremy Taylor almost 7 years ago
CHIRP does not load the USB Drivers. The USB Drivers must be loaded before you start chirp.
Based on the price you paid you may have a counterfeit FTDI chip or Prolific chip in your cable. The real FTDI cables run about $20 each. The only reliable vendor for Baofeng PC03 FTDI cables on Amazon is BTECH.
You might try looking at these two sites to try and troubleshoot the driver issues.
To determine the chipset:
https://plugable.com/2011/07/12/installing-a-usb-serial-adapter-on-mac-os-x/
Drivers that worked for my fake prolific cable:
http://www.miklor.com/COM/UV_Drivers.php#mac
Updated by Rob McClure almost 7 years ago
Thanks Jeremy.
Oh what fun serial drivers on Macs for Chinese hardware is...
For me, a combination of a different serial cable my brother bought with his "version" of the UV-5R plus the Plugable site was the trick. I tried two other drivers without obtaining complete install success, including uninstalls. I could not get the serial interface (cu.xxx) into the /dev location until I used the driver for the latest Mac OS (Sierra, not High Sierra) from here: https://plugable.com/drivers/prolific/. I did install the driver with the radio and the working cable attached to the Mac - not sure if that makes a difference but before the driver install I did see USB Serial Driver in the USB System Information panel - a good sign but not sufficient to get the port to show up on Chrip - that took a driver that got the interface into /dev.
So it was the cable. Not sure which one he bought - we're working on determining that but it looks different than many of the cables on Amazon (including mine) that have an indented silver plate with the BaoFeng name inside. Those are no good it seems. His is a black sticker with no raised molding.
I'll likely just buy the BTech $20 cable but since the entire rig only cost $35... Oh well!
Now I need to learn how to use Chirp.. ;-)
Thanks again for the pointers.
Updated by Rob McClure almost 7 years ago
Rob McClure wrote:
Thanks Jeremy.
Oh what fun serial drivers on Macs for Chinese hardware is...For me, a combination of a different serial cable my brother bought with his "version" of the UV-5R plus the Plugable site was the trick. I tried two other drivers without obtaining complete install success, including uninstalls. I could not get the serial interface (cu.xxx) into the /dev location until I used the driver for the latest Mac OS (Sierra, not High Sierra) from here: https://plugable.com/drivers/prolific/. I did install the driver with the radio and the working cable attached to the Mac - not sure if that makes a difference but before the driver install I did see USB Serial Driver in the USB System Information panel - a good sign but not sufficient to get the port to show up on Chrip - that took a driver that got the interface into /dev.
So it was the cable. Not sure which one he bought - we're working on determining that but it looks different than many of the cables on Amazon (including mine) that have an indented silver plate with the BaoFeng name inside. Those are no good it seems. His is a black sticker with no raised molding.
I'll likely just buy the BTech $20 cable but since the entire rig only cost $35... Oh well!
Now I need to learn how to use Chirp.. ;-)Thanks again for the pointers.
Oh, let me ask. Does the FTDI cable from BTech use the same Prolific chip so should work with the driver I have installed?
Updated by Bernhard Hailer almost 5 years ago
- Status changed from New to Closed
- Priority changed from Urgent to Normal
- Model affected changed from (All models) to Baofeng UV-5R
Resolved.