Ftdi drivers mac os
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PLEASE NOTE — When updating drivers, 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 . Drivers are available which allow FTDI devices to work with the following operating systems:
Windows 10 Windows Server 2008 R2 Windows Server 2008 Windows Server 2008 x64 Windows Vista x64 Windows Server 2003 Windows Server 2003 x64 Windows CE.NET (Version 4.2 and greater) Support for WinCE 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. If a VCP driver is required for Android please refer to the following application note: TN 132 Adding FTDI Devices VCP Driver Support to Android D3XX D3XX drivers are only suitable for FTDI’s Superspeed USB bridge services (e.g. FT60x series). C ontacting Technical Support For technical queries relating to drivers or any of our other products or services, please send an email to our Customer Engineering Support team in your region: Alternatively, please click here to access the list of regional office telephone numbers if you wish to call one of the regional support teams directly. Источник DriversPLEASE 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. Click here to download the Windows 7 to Windows 10 and Windows Server driver installer. The Windows driver installer contains both VCP and D2XX drivers. For Windows 11, download the driver installer for desktop and universal driver versions. Drivers are available which allow FTDI devices to work with the following operating systems:
Support for WinCEFTDI drivers are available for Windows CE 4.2-5.2, 6.0/7.0 and 2013. Support for older versions of Windows DesktopNOTE: 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 APIFor 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. Источник DriversD2XX Direct DriversThis page contains the D2XX drivers currently available for FTDI devices. Click here to download the Windows 7 to Windows 10 and Windows Server (see note * below) driver installer. The Windows driver installer contains both VCP and D2XX drivers. For Windows 11, download the driver installer for desktop and universal driver versions. 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 DriversD2XX 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 UpdatesOur Driver Updates
1.4.24 MIPS openwrt-uclibc | If unsure which ARM version to use, compare the output of readelf and file commands on a system binary with the content of release/build/libftd2xx.txt in each package. Please see the ReadMe, Release Notes and Video Install Guide | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Mac OS X 10.4 Tiger or later | 2021- 05-18 | – | 1.4.24 | 1.4.24 | – | – | If using a device with standard FTDI vendor 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. Please see the ReadMe, Release Notes and Video Install Guide | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows CE 4.2-5.2** | 2015-11-03 | 1.0.1.12 | – | 1.0.1.12 | 1.0.1.6 MIPS II 1.0.1.6 MIPS IV | 1.0.1.6 | – | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows CE 6.0/7.0 | 2015-11-03 | 1.0.1.12 1.0.1.6 MIPS IV | 1.0.1.6 | For use of the CAT files supplied for ARM and x86 builds refer to AN_319 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows CE 2013 | 1.0.0 | – | 1.0.0 | D2xx Driver Support for WinCE2013 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Android (Java D2XX) | 201 8 – 05 -09 | – | Java Driver 2.08 | Rooting of Android device is not required. 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.
Источник