After going through all the install steps for your OS, run this as a simple test to make sure everything is installed correctly. See the rest of the page for some potential hiccups you may run into.

Go ahead and plug in your FT232H to a USB port on your PC.

Check pyftdi is installed correctly

Launch Python:

and enter these commands:

from pyftdi.ftdi import Ftdi

You should get a list of connected FTDI devices. Most likely, there will be only one.

If an FTDI device can not be found for some reason, you'll see something like this:

If you get

NotImplementedError: Operation not supported or unimplemented on this platform

Go back to the setup steps and Zadig your board if on Windows

Check environment variable within python

At the Python REPL, type

import os

if you get a KeyError it means you did not set the environment variable right

If you see some other errors, go back through the install process for your OS and make sure everything ran correctly.

If you have set it correctly, you'll get a value back

Now type in import board

You should get no errors at all, in which case you can continue onto the next steps!

Board not supported None

If you get

NotImplementedError: Board not supported None

that could mean you did not set the FT232H environmental variable or you don't have the latest python libraries or the FT232H is not plugged in.

BLINKA_FT232H environment variable set, but no FT232H device found

If you get this error, check your USB cable - it could be that you have a charge-only not charge+sync cable.

If you're running Windows, verify you ran Zadig to install the libusbK driver

The device has no langid

On Windows, if you get ValueError: The device has no langid on an open_from_url() call that may mean you dont have libusbk.dll placed in C:\Windows\System32

NotImplementedError: Operation not supported or unimplemented on this platform

If you're running Windows, run Zadig to select/install the libusbK driver on this device

pyftdi.ftdi.FtdiError: UsbError: [Errno 13] Access denied (insufficient permissions)

If you get this on a Mac, it could be you have conflicting ftdi drivers installed, you'll need to remove them!

Versions of OS X up to and including 10.8

The easiest way we found to do that is run

brew remove libftdi

This may have been installed by avrdude, open-ocd or other tools! You may have to --force uninstall it depending on what tools you are using.

For OS X versions 10.3 to 10.8, there is a procedure outlined in section 4.1 of Application Note AN 134 from FTDI:

In summary, start a terminal session:

Go -> Applications -> Utilities -> Terminal

and run the following commands:

cd /System/Library/Extensions
sudo rm -r FTDIUSBSerialDriver.kext
cd /Library/Receipts
sudo rm -r ftdiusbserialdriver.pkg
sudo rm -r ftdiusbserialdriverinstallerPostflight.pkg
sudo rm -r ftdiusbserialdriverinstallerPreflight.pkg

and then reboot the system for the changes to take effect.

Versions of OS X 10.9 through 10.13

For OS X versions 10.9 though 10.13, you can unload the kext driver by running the following command:

sudo kextunload -v -bundle

Please note, the system will automatically reload the kext driver upon restart, so this would need to be run each time before using the board.

You may want to use an alias or script to easily run this command.

This guide was first published on Sep 29, 2019. It was last updated on Apr 12, 2024.

This page (Post Install Checks) was last updated on Mar 08, 2024.

Text editor powered by tinymce.