The Beginners Guide has general help. Click here for the Beginners Guide
If you need Mac-specific help, you are at the right page.
If you need Mac-specific help, you are at the right page.
Join the Mailing list & search the archives for similar problem reports & how they were resolved, and/or ask the group. Please include enough info about the problem and situation so the community will be able to help you.
All FTDI devices now supported in Ubuntu 11.10, kernel 3.0.0-19 Refer to TN-101 if you need a custom VCP VID/PID in Linux VCP drivers are integrated into the kernel. Mac OS X 10.3 to 10.8: 2012-08-10: 2.2.18: 2.2.18: 2.2.18-Refer to TN-105 if you need a custom VCP VID/PID in MAC OS: Mac OS X 10.9 and above: 201 9-12-24-2.4.2. Dec 11, 2011 Log In Items are set in the Accounts preferences. Open System Preferences, click on the Accounts icon, then click on the LogIn Items tab. Locate the item in the list for the application you want to remove and click on the '-' button to delete it from the list. Some software use startup daemons or agents that are a new feature of the OS.
- 1 Welcome to the Mac OS X Installation Guide This document describes the procedure for installing the Mac OS X FTDIUSBSerial driver for FTDI's FT2232C, FT232BM, FT245BM, FT8U232AM and FT8U245AM devices. The driver is available for free download from the Drivers section of the FTDI€web€site.
- Jan 13, 2016 Hey Stephen, Sorry for not getting back sooner but thank you for the info on the driver install! Found out about a week later, that wasn't the issue at all, I just needed to make sure the R.I.C.E cable was connected before connecting to my Ascend saber, then the configuator would read the USB.
- 'How do you uninstall software' - that depends on the software creator(s). Some Macintosh software (the application, or folder containing the application and any related files, folders, etc.) can be merely dragged to the 'Dock' based trash can, and 'Finder's 'Finder, Empty Trash' menu item selected.
Not all functionality is supported on all radios. See Model Support
As of MacOS 10.9, signed packages are required by default. Apple charges for this capability, and requires use of their tooling to do it. For the time being, MacOS users may need to disable signed package checking for CHIRP. Instructions provided by Jim, K2SON:
- Locate the app in Finder.
- Right click (control-click if you don't have a 2 button mouse) on the app and click Open.
- You will get a dialog box about it being an unsigned app, click the Open button.
- Enter an Administrator userid and password.
- The app will now be flagged to allow it to be opened normally in the future.
Alternately, you can disable them for your entire system, although this has security implications that should not be ignored. Instructions for this provided by Tom, KD7LXL:
- Open your System Preferences
- Go to Security & Privacy, General tab.
- Click the lock
- Then choose Allow apps downloaded from: Anywhere.
As of 10.12 (Sierra) the UI for disabling app security was removed. The functionality is still there, but must be enabled from the command line.
To whitelist a single application (like an unzipped chirp-daily.app): - unzip chirp.zip
- control click on the unzipped application and select New Terminal at Folder. (Don't see that menu item? Instructions to enable it)
- run this command in the newly opened terminal window:
Alternately, you can disable them for your entire system, although this has security implications that should not be ignored. Run this command in a terminal:
references: single commandglobal
Unfortunately, Apple has made significant changes in 10.15 which cause major issues for independent software developers. CHIRP is significantly impacted and the future is unclear.
At the very least, Catalina users should use the 'unified' build of the app provided on the download page, which uses the system's 64-bit python runtime. Also note that there are significant limitations on what files unsigned applications can access which makes it very difficult to open, save, find, and otherwise organize image and CSV files with chirp. Please see issue #7147 for the current information about workarounds.
USB to serial cables are not merely wire, they contain small computer circuits at one end of the cable that respond as a USB device and convert the data to serial. These cables are not all the same, so the computer needs a software 'driver' so it can recognize the cable and speak to it correctly. You will need to install one of these 5 below.
FTDI cables¶
Note that with Mac OSX 10.9 'Mavericks', Apple provides their own driver for FTDI chipset. You may need to remove the OEM FTDI driver and use only the Apple FTDI driver, or you may need to disable the Apple FTDI driver and install the OEM FTDI drivers. YMMV.
http://www.ftdichip.com/Drivers/VCP.htm
Version 1.5.1 is available for Mac OS X on 64 bit, 32 bit and PPC machines.
Version 1.5.1 is available for Mac OS X on 64 bit, 32 bit and PPC machines.
Prolific PL-2303 cables - official drivers for the genuine Prolific cables¶
FYI: your cable, if using Prolific chipset, is more likely to be using a counterfeit chip than an original.
http://www.prolific.com.tw/US/CustomerLogin.aspx
Login as guest/ guest & look in the Support section. Specified to work with Mac OSX 10.6, 10.7, & 10.8.
Login as guest/ guest & look in the Support section. Specified to work with Mac OSX 10.6, 10.7, & 10.8.
Generic PL-2303 cables (counterfeit and/or “Generic”) If you aren't sure what kind of inexpensive cable you have, try this one first.¶
For Lion (10.7.x), Mountain Lion (10.8.x), and Mavericks (10.9.x):¶
You can try this one, which install open source pl2303 driver and remove any other driver versions:
http://1drv.ms/Nl68Ru At this web page you may need to right-click or control-click to link to get it to download. After downloading, you may need to control-right click, then open in order to bypass Mac Gatekeeper.
http://1drv.ms/Nl68Ru At this web page you may need to right-click or control-click to link to get it to download. After downloading, you may need to control-right click, then open in order to bypass Mac Gatekeeper.
For earlier versions of Mac OS X up to 10.5 Leopard. Also some reports of success with Snow Leopard, Lion:¶
RTSystems cables¶
for OSX 10.9.x (aka Mavericks):¶
see RTSystemsCablesAndMavericks
for OSX < 10.9.x:¶
https://www.rtsystemsinc.com/kb_results.asp?ID=9
http://www.rtsystems.us/downloads/MacDrivers/RTSystemUSBSerialDrivers.pkg.mpkg.zip
http://www.rtsystems.us/downloads/MacDrivers/RTSystemUSBSerialDrivers.pkg.mpkg.zip
Silicon Labs CP210x USB to UART Bridge VCP Drivers (including Kenwood TH-D72)¶
- http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
Macintosh OSX driver for the Intel and PowerPC Platforms versions 10.4, 10.5, 10.6, 10.7, 10.8, and 10.9.
- In many cases you need to connect the cable to the radio first, then power the radio on, while holding down some buttons. The exact procedure varies by radio.
- Some radios need to be put into a 'clone' mode to transfer to PC, some radios may need to be configured to use the mic/speaker jacks for PC transfer instead of for the speaker/mic. The exact procedure varies by radio.
- You will need to download from the radio to CHIRP first, before uploading anything to the radio. CHIRP creates a template from the radio download so it knows how to talk to the radio.
- If you want to download from one radio and upload those settings to another radio, first download from each radio to a separate “tab” of CHIRP. Then copy/paste from one tab to the other & upload back to the same radio that produced that tab. Do not try to upload to a radio directly from a tab that was not downloaded from that same radio.
- Many USB to serial cables include a counterfeit Prolific chip. This can cause connection problems because the official Prolific driver will ignore the counterfeit chip. Some people have reported success by using an older version of the Prolific driver, or a 3rd party driver.
- If you are using multiple USB cables, each will create a different “virtual port”, meaning that you will need to select the correct virtual port for your radio when connecting to your radio. CHIRP will give you this opportunity each time you download from the radio.
- If CHIRP won’t launch & won't run, you may have neglected to install the Python runtime. CHIRP needs that. Even though Mac OS X includes Python built-in, the runtime has to be installed is because it includes PyGTK and some other libraries that Chirp requires, in addition to Python itself: http://www.d-rats.com/download/OSX_Runtime/
- If your radio is not 'Supported', you can try downloading the newest Daily Build to see if support was recently added.
Dell 1110 driver mac os x. You can verify that the drivers are installed & working by connecting the USB cable to your Mac, then running “System Profiler”, or “System Information” (found in /Applications/Utilities ). When the USB cable is connected and drivers correctly installed, the cable will show up in the USB section of the System Profiler.
Another way to see that the driver is correctly installed is to open Terminal and type:
It will return a list of virtual serial ports including something similar to:
You may also type:
That will return a long list of kexts, including something similar to this at the bottom (most recently installed are listed last):
Look at the CHIRP log for clues.
Join the Mailing list & search the archives for similar problem reports & how they were resolved, and/or ask the group. Please include enough info about the problem and situation so the community will be able to help you.
Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the same way as it would access a standard COM port. This software is provided by Future Technology Devices International Limited ``as is' and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall future technology devices international limited be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
FTDI drivers may be used only in conjunction with products based on FTDI parts.
FTDI drivers may be distributed in any form as long as license information is not modified.
If a custom vendor ID and/or product ID or description string are used, it is the responsibility of the product manufacturer to maintain any changes and subsequent WHCK re-certification as a result of making these changes.
For more detail on FTDI Chip Driver licence terms, please click here.
FTDI drivers may be used only in conjunction with products based on FTDI parts.
FTDI drivers may be distributed in any form as long as license information is not modified.
If a custom vendor ID and/or product ID or description string are used, it is the responsibility of the product manufacturer to maintain any changes and subsequent WHCK re-certification as a result of making these changes.
For more detail on FTDI Chip Driver licence terms, please click here.
Currently Supported VCP Drivers:
Processor Architecture | |||||||||
Operating System | Release Date | x86 (32-bit) | x64 (64-bit) | PPC | ARM | MIPSII | MIPSIV | SH4 | Comments |
Windows* | 2017-08-30 | - | - | - | - | - | WHQL Certified. Includes VCP and D2XX. Available as a setup executable Please read the Release Notes and Installation Guides. | ||
Linux | - | - | - | - | - | - | - | - | All FTDI devices now supported in Ubuntu 11.10, kernel 3.0.0-19 Refer to TN-101 if you need a custom VCP VID/PID in Linux VCP drivers are integrated into the kernel. |
Mac OS X 10.3 to 10.8 | 2012-08-10 | 2.2.18 | 2.2.18 | 2.2.18 | - | - | - | - | Refer to TN-105 if you need a custom VCP VID/PID in MAC OS |
Mac OS X 10.9 and above | 2019-12-24 | - | 2.4.2 | - | - | - | - | - | This driver is signed by Apple |
Windows CE 4.2-5.2** | 2012-01-06 | 1.1.0.20 | - | - | 1.1.0.20 | 1.1.0.10 | 1.1.0.10 | 1.1.0.10 | |
Windows CE 6.0/7.0 | 2016-11-03 | 1.1.0.22 CE 6.0 CAT CE 7.0 CAT | - | - | 1.1.0.22 CE 6.0 CAT CE 7.0 CAT | 1.1.0.10 | 1.1.0.10 | 1.1.0.10 | For use of the CAT files supplied for ARM and x86 builds refer to AN_319 |
Windows CE 2013 | 2015-03-06 | 1.0.0 | 1.0.0 | VCP Driver Support for WinCE2013 |
*Includes the following version of of the Windows operating system: Windows 7, Windows Server 2008 R2 and Windows 8, 8.1, Windows server 2012 R2, Windows Server 2016 and Windows 10. Also, as Windows 8 RT is a closed system not allowing for 3rd party driver installation our Windows 8 driver will not support this variant of the OS. You must use the Windows RT build for this platform.
Ftdi Driver Install
**includes the following versions of Windows CE 4.2-5.2 based operating systems: Windows Mobile 2003, Windows Mobile 2003 SE, Windows Mobile 5, Windows Mobile 6, Windows Mobile 6.1 ,Windows Mobile 6.5Mac Os X Uninstall Ftdi Driver Update
No Longer Supported:
Processor Architecture | |||||||||
Operating System | Release Date | x86 (32-bit) | x64 (64-bit) | PPC | ARM | MIPSII | MIPSIV | SH4 | Comments |
Previous Windows Release | 2017-03-10 | 2.12.26 | 2.12.26 | WHQL Certified. Includes VCP and D2XX. Available as a setup executable Please read the Release Notes and Installation Guides. | |||||
Windows XP, Vista, Server 2003, Server 2008 | 2012-04-13 | 2.08.24 | 2.08.24 | - | - | - | - | - | WHQL Certified Also available as a setup executable Release notes This is FTDI's final release before Microsoft stopped certifying drivers for these versions of Windows. |
Windows 2000 | 2009-10-22 | 2.06.00 | - | - | - | - | - | - | WHQL Certified Available as setup executable Release notes |
Windows 98/ME | 2004-11-25 | 1.09.06 | - | - | - | - | - | - | Does not support FT2232 or FT4232 devices |
Windows 98/ME | 2004-03-12 | 1.0.3 | - | - | - | - | - | - | Only supports FT2232D devices |
Mac OS 9 Mac OS 8 | 2004-05-18 | - | - | 1.0f4 | - | - | - | - | |
Mac OS X 10.9 and above | 2015-04-15 | - | 2.3 | - | - | - | - | - | This driver is signed by Apple |
Linux | 2009-05-14 | 1.5.0 | 1.5.0 |