Drivers
PLEASE NOTE – When editing driver INF files, refer to the following document: AN_107 – Advanced Driver Options
New drivers are now available to support the FT4222H – for D2XX drivers please click here.
Windows Driver Installer (VCP & D2XX), please click here.
Drivers are available which allow FTDI devices to work with the following operating systems:
Windows Certified | Others | Legacy |
---|---|---|
Windows 10 (32/64) | Linux | Windows Vista (32/64) |
Windows 8.1 (32/64) | MAC OSX | Windows XP (32/64) |
Windows 8 (32/64) | Windows CE (Version 4.2 and greater) | Windows 2000 |
Windows 7 (32/64) | Windows RT | Windows ME |
Windows Server 2016 | Android | MAC OS9 |
Windows Server 2012 R2 x64 | Windows 98 | |
Windows Server 2008 R2 x64 | MAC OS8 |
Support for WinCE
FTDI drivers are available for Windows CE 4.2-5.2, 6.0/7.0 and 2013.
Support for older versions of Windows Desktop
NOTE: Microsoft have ended support for certifying XP and VISTA through their WHCK test program. From revision 2.12.24 with Device Guard Support, the driver will not load on XP or VISTA.
Differences in Driver API
For most of these operating systems two types of driver are available: Virtual COM Port (VCP) drivers and direct (D2XX) drivers. The VCP driver emulates a standard PC serial port such that the USB device may be communicated with as a standard RS232 device. The D2XX driver allows direct access to a USB device via a DLL interface.
To locate the drivers you want to install for a device, select which of the driver types you wish to use (VCP or D2XX) and then locate the appropriate operating systems. With the exception of Windows 98 and Windows ME, all devices are supported in each driver package.
Drivers
D2XX Direct Drivers
This page contains the D2XX drivers currently available for FTDI devices.
For Virtual COM Port (VCP) drivers, please click here .
Installation guides are available from the Installation Guides page of the Documents section of this site for selected operating systems.
D2XX Drivers
D2XX drivers allow direct access to the USB device through a DLL. Application software can access the USB device through a series of DLL function calls.
The functions available are listed in the D2XX Programmer’s Guide document which is available from the
Documents section of this site.
Programming examples using the D2XX drivers and DLL can be found in the Projects section of this site.
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.
Currently Supported D2XX Drivers:
Subscribe to Our Driver Updates
Our Driver Updates
Processor Architecture | |||||||
Operating System | Release Date | x86 (32-bit) | x64 (64-bit) | ARM | MIPS | SH4 | Comments |
---|---|---|---|---|---|---|---|
Windows* | 201 7 – 0 8-30 | 2.12.28 | 2.12.28 | – | – | – | WHQL Certified.Includes VCP and D2XX. Available as a setup executable Please read the Release Notes and Installation Guides. |
Windows RT | 2014-07-04 | 1.0.2 | – | 1.0.2 | – | – | A guide to support the driver (AN_271) is available here |
Linux | 2020-12-21 | 1.4.22 | 1.4.22 | 1.4.22 ARMv5 soft-float |
1.4.22 MIPS openwrt-uclibc
and file commands on a system binary with the content of
release/build/libftd2xx.txt in each package.
ReadMe
Video Install Guide
10.4 Tiger or later
and product identifiers, install
D2xxHelper
to prevent mac OS from
claiming the device as a serial port (locking out D2XX programs).
This will prevent the device being used
with the VCP driver as a standard COM port.
ReadMe
Video Install Guide
1.0.1.6 MIPS IV
1.0.1.6 MIPS IV
AN_319
2.08
Refer to technical note
TN_147.
Refer to
AN_357 for FT4222H-specific help.
*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.
**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.5
*** Suitable for Raspberry Pi, please check which instruction set your model implements.
NOTE: Microsoft have ended support for certifying XP and VISTA through their WHCK test program. As such current builds will still work on XP and VISTA but are not Microsoft certified.
Drivers
Virtual COM Port Drivers
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 This page contains the VCP drivers currently available for FTDI devices.
For D2XX Direct drivers, please click here.
Installation guides are available from the Installation Guides page of the Documents section of this site for selected operating systems.
VCP Drivers
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.
Currently Supported VCP Drivers:
Subscribe to Our Driver Updates
Our Driver Updates
Processor Architecture | |||||||||
Operating System | Release Date | x86 (32-bit) | x64 (64-bit) | PPC | ARM | MIPSII | MIPSIV | SH4 | Comments |
---|---|---|---|---|---|---|---|---|---|
Windows* | 201 7 – 0 8-30 | 2.12.28 | 2.12.28 | – | – | – | – | – | 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 | 201 9 – 12 – 24 | – | 2.4.4 | – | – | – | – | – | This driver is signed by Apple |
Windows CE 4.2-5.2** | 2012-01-0 6 | 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.
**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.5