Once up-and-running, pylibftdi is designed to be very simple, but sometimesgetting it working in the first place can be more difficult.

1. Ftdi Cable Drivers
2. Ftdi Usb Driver Mac Os X
3. Ftdi Driver Installation Mac Os X
4. Ftdi Chip Drivers
5. Mac Os X Versions

Topic: FTDI USB drivers on mac os x 10.5??? (Read 11079 times) previous topic - next topic. Nek670 Guest; FTDI USB drivers on mac os x 10.5??? Jan 15, 2008, 09:36 pm. I have never installed USB drivers before on a MAC. I downloaded and installed the FTDIUSBSerialDriver104105106.pkg, I assume it will work on 10.75. I also downloaded the D2xx driver but I am not having any luck installing it. Terminal commands are giving problems. Any advice or help with installation of the drivers would be appreciated.

Error messages¶

FtdiError:unabletoclaimusbdevice.MakesurethedefaultFTDIdriverisnotinuse(-5)¶

This indicates a conflict with FTDI’s own drivers, and is (as far as I know)mainly a problem on Mac OS X, where they can be disabled (until reboot) byunloading the appropriate kernel module.

To install the driver on the MAC you simply click on the.mpkg that matches your version of OS X. With Lion and Mountain Lion, you will need to bypass the new Gatekeeper security function to install the pkg file. Simply press Cntrl-Clickwhen you select FTDIUSBSerialDriver104105106107.pkg. This will bring up a pop-up menu. First, download the “OS X FTDI Driver Control” app Here, extract and run the application: On the main screen, it should say that the FTDI driver is “ENABLED”, this means that the Mavericks driver is loaded and your DMX software does NOT work. To disable the driver, click the big button. Aliasing Serial Baud Rates in FTDI Drivers for Mac OS X For a recent project, I needed to interface my computer to an embedded device over a RS-422 connection at 3.2Mbaud. Since this is a nonstandard serial rate, I set out to find a way to configure a relatively cheap USB UART bridge that supported communications at this speed.

MacOS (Mavericks and later)¶

Starting with OS X Mavericks, OS X includes kernel drivers which will reservethe FTDI device by default. In addition, the FTDI-provided VCP driver willclaim the device by default. These need unloading before libftdi will be able`to communicate with the device:

Similarly to reload them:

Earlier versions of pylibftdi (prior to 0.18.0) included scripts forMacOS which unloaded / reloaded these drivers, but these complicated cross-platformpackaging so have been removed. If you are on using MacOS with programs whichneed these drivers on a frequent basis (such as the Arduino IDE when usingolder FTDI-based Arduino boards), consider implementing these yourself, along thelines of the following (which assumes ~/bin is in your path):

OS X Mountain Lion and earlier¶

Whereas Mavericks includes an FTDI driver directly, earlier versions of OS Xdid not, and if this issue occurred it would typically as a result ofinstalling some other program - for example the Arduino IDE.

As a result, the kernel module may have different names, but FTDIUSBSerialDriver.kextis the usual culprit. Unload the kernel driver as follows:

To reload the kernel driver, do the following:

If you aren’t using whatever program might have installed it, the drivercould be permanently removed (to prevent the need to continually unload it),but this is dangerous:

Diagnosis¶

Getting a list of USB devices

Mac OS X¶

Start ‘System Information’, then select Hardware > USB, and look for yourdevice. On the command line, system_profilerSPUSBDataType can be used.In the following example I’ve piped it into grep-C7FTDI, to print 7lines either side of a match on the string ‘FTDI’:

Linux¶

Use lsusb. Example from my laptop:

Where did my ttyUSB devices go?¶

When a pylibftdi.Device() is opened, any kernel device which was previouslypresent will become unavailable. On Linux for example, a serial-capable FTDIdevice will (via the ftdi_sio driver) create a device node such as/dev/ttyUSB0 (or ttyUSB1,2,3 etc). This device allows use of the FTDI deviceas a simple file in the Linux filesystem which can be read and written.Various programs such as the Arduino IDE (at least when communicating withsome board variants) and libraries such as PySerial will use this device.Once libftdi opens a device, the corresponding entry in /dev/ will disappear.Prior to pylibftdi version 0.16, the simplest way to get the device node toreappear would be to unplug and replug the USB device itself. Starting from0.16, this should no longer be necessary as the kernel driver (which exports/dev/ttyUSB…) is reattached when the pylibftdi device is closed. Thisbehaviour can be controlled by the auto_detach argument (which is defaultedto True) to the Device class; setting it to False reverts to the oldbehaviour.

Note that on recent OS X, libftdi doesn’t ‘steal’ the device, but insteadrefuses to open it. The kernel devices can be seen as/dev/tty.usbserial-xxxxxxxx, where xxxxxxxx is the device serial number.FTDI’s Application Note AN134 details this further (see section ‘UsingApple-provided VCP or D2XX with OS X 10.9 & 10.10’). See the section aboveunder Installation for further details on resolving this.

Gathering information¶

Starting with pylibftdi version 0.15, an example script to gather systeminformation is included, which will help in any diagnosis required.

Run the following:

this will output a range of information related to the versions of libftdilibusb in use, as well as the system platform and Python version, for example:

Introduction

In this tutorial, we’ll show you how to install FTDI drivers on multiple operating systems. Although this tutorial was written using Windows 7, Mac OS X 10.6, and Ubuntu 13.04, the process should be very similar, if not exactly the same, for other versions/variations of these operating systems.

Suggested Reading

Before you begin this tutorial, you should have the Arduino IDE installed on your computer. Check out our Installing Arduino tutorial for a step by step guide.

Here are some other tutorials and concepts you may want to familiarize yourself with before reading this tutorial:

Alright, let’s get to work! You can visit the next section to learn more about the FTDI Basic and why you need the FTDI drivers, or you can skip straight to the operating system of your choice!

Meet the FT232RL

The FT232RL is one of the more commonly used ICs used to convert USB signals to UART signals. This process is very handy in that it allows you communicate with and upload code to an Arduino or other microcontroller without the need for an external programmer. SparkFun carries a board called the FTDI Basic that conveniently breaks out the necessary pins on the FT232RL to perform these actions.

SparkFun’s 5V FTDI Basic. Notice the IC–FT232RL.

There are a few different flavors of the FTDI Basic:

If you are using a 5 volt device, you will need the 5 volt FTDI. If you have a 3.3 volt device, you guessed it, use a 3.3 volt FTDI. LilyPad boards all operate on 3.3V.

We also carry a complete breakout board for the FT232RL should you need access to more pins than the FTDI Basic provides.

Here is a list of some SparkFun products that require the use of an FTDI Basic, come with an FTDI Basic, or have an FT232RL chip on board:

• Arduino Pro 5V and 3.3V
• Arduino Pro Mini 5V and 3.3V
• Mega Pro 5V and 3.3V

There are also some legacy Arduino boards that use the FT232RL. The Arduino Diecimila and Duemilanove main boards along with the original Arduino Mega all use the FT232RL IC. If you have one of these older versions, you’ll want to use the FDTI drivers as well. For a complete list of all Arduino boards, check out this page. Newer versions of Arduino boards, such as the Uno, use a different communication IC, and they will not be covered in this tutorial.

Now that you know why the FTDI Baisic is important and what products it is used for, let’s learn how to install the drivers.

Windows - Quick and Easy

Ftdi Cable Drivers

1. By default, windows does not have FTDI drivers installed. If you plug in your FTDI, open the Arduino IDE, go to ‘Tools -> Serial Ports’, and see nothing, you need the drivers! Let’s go get them!

2. Download the FTDI Driver here.

3. Choose ‘Run,’ once it is has finished downloading, or find the file you just downloaded ‘CMD_v2.12.00_WHQL_Certified.exe’ and double-click it to run it.

4. Choose ‘Extract,’ and continue through the installation until it finishes.

5. If everything was successful, you should see some nice green check marks, indicating success! Note: You may need administrator privileges on your machine in order for this to run properly. If things didn’t work out, try the next section of this tutorial: Windows - In Depth.

6. Open up the Arduino IDE, and go to ‘Tools -> Serial Port’. If you now have a COM port, congratulations! Again, if something went wrong, either retry this tutorial or give Windows - In Depth a try!

Windows - In Depth

1. Plug in your FTDI using a USB cable. Windows doesn’t have the correct drivers, so let’s find them!

2. Navigate to the FTDI website, and choose the ‘VCP’ (Virtual Com Port) option near the bottom.

3. Now choose either the 32 bit version or the 64 bit version. Not sure which you have? The next steps will go over how to find that information. If you already know which version you are running, you may skip the next two steps.

4. Open the start menu, right-click on ‘Computer,’ and left-click on ‘Properties’.

5. Look under ‘System type,’ to see which version you have.

6. Now go back to the FTDI site, right-click on the correct version, and save it to your computer. Remember where the files are saved. We’ll need them in the next step.

7. Navigate to the folder containing the files. They will be inside of a .zip file, so you’ll need to extract them. Right-Click on the .zip file, and choose ‘Extract All…’ When the next window appears, as shown above, pay attention to where it is extracting the files. Make sure that ‘Show extracted files when complete’ is checked, and click ‘Extract’.

8. When the extraction is complete, the folder is opened. Again, take note of this folder location. This is the one containing the drivers.

9. We’re almost there! Open the start menu, right-click on ‘Computer’, and left-click on ‘Manage’. You will need administrator rights to do this. If you aren’t an administrator on your computer, talk to the person who is and have them enter their credentials.

10. Left-click on ‘Device Manager’ in the leftmost column. Here is where we see the offending hardware. It has an exclamation mark next to it.

11. Right-click on ‘FT232R USB UART,’ and left-click ‘Update Driver Software…’

12. Now choose ‘Browse my computer for driver software’.

13. Left-click ‘Browse,’ and navigate to the location of the extracted files. Choose the extracted folder. There is no need to search any further in the folder. Then left-click ‘OK’.

14. Make sure ‘Include subfolders’ is checked (very important!), and left-click ‘Next’.

15. After a moment, you will see a success message! Left-click ‘Close’.

16. The Device Manager page will refresh and you will see a new item with an exclamation mark named ‘USB Serial Port’. You will need to install a second driver for the same device. Follow the steps 1-15, as before, and use the same driver folder too!

17. Once those steps are complete, you will see another success message! Left-click ‘Close’.

18. The Device Manager Page will refresh again and show ‘USB Serial Port (COMxx),’ where xx = some number. Congratulations, you now have the proper FTDI drivers and can begin to use your device!

Note: You should only need to go through this process once. Every subsequent FTDI device you plug in should now have these drivers associated with it. However, if this is not the case, you can follow these instructions again for other devices.

Note: If you have more than one FTDI device plugged in to your computer at the same time, all of the devices will show up under this menu. To figure out which device is which, look under the ‘Serial Port’ menu. Take note of the names of each device. Then unplug the device you want to use. Go back to the ‘Serial Port’ menu. The device you unplugged should no longer be listed. That is the device you want. Plug it back in, and select the device that has now reappeared. You can also check the Com port number in the Device Manger to see which device is associated with each Com port.

Linux

1. Plug in the FTDI device to a USB cable.

2. When you download the Arduino IDE in Linux, the download comes with the FTDI drivers bundled with the IDE. However, if you just open Arduino from the desktop, you’ll notice that, if you click on ‘Tools’, the ‘Serial Port’ option is grayed out.

3. Linux includes the drivers necessary to use Arduino, and no additional install is needed. However, permissions might need to be configured. For current instructions on how to set up these permissions, visit this page.

   An alternative method is to run Arduino as root in the terminal with the following command:

   However, this method is encouraged only if you know what you are doing and should only be used as a last resort. You will also need to enter your administrative password to run as root.

4. Arduino should open, and this time the ‘Serial Port’ menu is available.

5. The FTDI device will show up under this menu. It should be named /dev/ttyUSB0. The number may vary depending on how many USB devices you have plugged into your computer. That’s all.

Note: If you have more than one FTDI device plugged in to your computer at the same time, all of the devices will show up under this menu. To figure out which device is which, look under the ‘Serial Port’ menu. Take note of the names of each device. Then unplug the device you want to use. Go back to the ‘Serial Port’ menu. The device you unplugged should no longer be listed. That is the device you want. Plug it back in, and select the device that has now reappeared.

Mac

1. Most of the time, when you install Arduino on Mac OS X, the drivers are installed automatically. However, if there was a problem with the installation and you don’t see any options that include ‘usbserial’ under the ‘Tools -> Serial Port’ menu, then you will need to install the drivers. You may also need to install the full FTDI drivers if you are running OSX 10.10 or later. The factory drivers are not complete.

2. OS X 10.9 (Mavericks) or above: Download this driver. Locate the file FTDIUSBSerialDriver_v2_3.dmg file that was downloaded to your computer, and double click on it to open run it.

   OS X 10.8 (Mountain Lion) or lower: Download this driver. Locate the file FTDIUSBSerialDriver_v2_2_18.dmgfile that was downloaded to your computer, and double click on it to open run it.

   If you are not sure which version of OS X you have, click on the apple icon in the upper-left corner of your screen and choose ‘About This Mac’. You will then see Version 10.X.Y–use the 10.X to determine your system version.

   If you are using the driver for OS X 10.8 (Mountain Lion) or older, you will see two files. Open up the driver file that corresponds with your operating system. For most users, it will be the second file:

3. Continue through the installation, and wait for it to finish. Then click ‘Close.’

4. Now open the Arduino IDE. Under ‘Tools -> Serial Port’ you will now see a ‘usbserial’ option. Congratulations, you’re all set!

Note: You should only need to go through this process once. Every subsequent FTDI device you plug in should now have these drivers associated with it. However, if this is not the case, you can follow these instructions again for other devices.

Note: If you have more than one FTDI device plugged in to your computer at the same time, all of the devices will show up under this menu. To figure out which device is which, look under the ‘Serial Port’ menu. Take note of the names of each device. Then unplug the device you want to use. Go back to the ‘Serial Port’ menu. The device you unplugged should no longer be listed. That is the device you want. Plug it back in, and select the device that has now reappeared.

Unidentified Developer Error

On newer versions of OS X, when you double-click the install packages inside the FTDI disk image, you may be presented with a very Windows-esque type error about not being able to open the files because they are not from an identified developers. This is very similar to the unsigned driver issue in Windows 8.

Quick Fix

To get around this, simply right-click the package you want to install, or press CTRL + click, if you don’t have a right-click. Then select open from the menu.

Ftdi Usb Driver Mac Os X

You will then be given another window asking if you are certain. Click Open, and proceed with the installation as stated above.

In-Depth Fix

For a more permanent fix, you can follow these instructions. However, this method is not suggested as it leaves your computer vulnerable.

Open your System Preferences.

Ftdi Driver Installation Mac Os X

Once open, click the Security & Privacy icon.

Under the General tab, you should see a section about allowing the running of downloaded applications from specific sources. In preveious version of OS X, the defualt was set to Anywhere. However, the defualt setting is now Mac App Store and identified developers.

To use the FTDI drivers, you’ll need to set this back to Anywhere. First, you may need to click on the little lock icon and enter your admin password to make these changes.

Note for educators: You may need to get you network administrator to come and unlock the computer in order to install these drivers.

Once unlocked, click the Anywhere option. Another obnoxious window may appear asking you if you’re sure you want to allow this. Click Allow from Anywhere. Or, you can follow the directions in this window, if you don’t want to make your Mac “less secure.”

You should now be able to install the FTDI drivers.

FTDI Drivers and OS X Yosemite

With Mac OS 10.9 (Mavericks) and later, Apple has built their own version of the FTDI VCP driver into the operating system (AN134). However, there seems to be some conflict between drivers from FTDIchip.com and the ones inherent to Apple. Luckily, there is a solution to this problem, and it comes from FTDI directly.

Quick Fix

If you are trying to use the FTDI VCP Driver in your applications, it will not work due to a conflict between the VCP and D2XX drivers. In order to get around this, the Apple supplied Driver must be uninstalled. Plug in the FTDI device in question, and type the following command in a Terminal window:

In-Depth Fix

If the above doesn’t work, you may have better luck using this script from FTDI.

Clicking on this file will bring up the Script Editor on all Macs. The script can be run by clicking on the run icon (black triangle). Again, make sure your FTDI device is connected.

Ftdi Chip Drivers

You can make this script into a clickable icon by exporting the script as an application. In the Script Editor, select Export… from the File pull down menu:

In the Export dialog, select Application as the File Format. You can choose any name for the application.

You should now have an automated Apple Script icon to use on your Mac. With the Apple supplied Drivers uninstalled, you may return to the top of this section and install the FTDI VCP Driver as needed. Repeat this process for any other FTDI devices you are using. You may need to repeat this every time you restart your computer.

Mac Os X Versions

If you receive this error, it means that the driver has been uninstalled already, and you will need to install the FTDI VCP Driver, as stated above.