FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Topics - FTDI Community

Pages: [1]
Complete our customer survey for your chance to win a Holy Stone HS175D drone worth £190!

Your opinion is extremely important to us, and we rely on customer feedback in order to continuously make improvements and ensure that we are addressing any issues. The responses we receive from our Annual Customer Survey are pivotal as part of this process. Plus, every entrant into the survey is entered into our prize draw, and one lucky winner will be awarded with a Holy Stone HS175D drone worth £190!*

Please follow this link to the Survey:  FTDI Survey

*Holystone and their respective logos are trademarks or registered trademarks of Holy Stone.  Holy Stone is not a participant in or sponsor of this promotion.

The promotion runs until 30th of September 2023.

Best Regards,
FTDI Community

FTDI News / Windows ARM64 driver
« on: February 03, 2022, 08:54:38 AM »

The Windows ARM64 driver is now available on our website:


You can find this on the VCP and D2xx driver pages under the ARM column.

This supports Windows 10 and Windows 11 only for ARM64 based Windows PCs.

It also works on Mac M1 running Parallels VM with Windows.

Please note that you need to manually install the driver through Device Manager --> Update Driver --> Browse my computer for drivers and point to the downloaded driver files.
Please refer to section 3.3 of the Windows 10/11 Installation Guide.
This has to be performed twice, once for the D2xx interface and then for the VCP interface (COM Port).
If the VCP interface does not appear after installing the D2XX interface, then either use Device Manager to “Scan for hardware changes” or unplug/replug the hardware.

If using Parallels VM on Mac M1 then please note the following:

The device driver files must be on Local disk (C:), as seen by Windows.
The desktop shown in the home window of Parallels is actually the same as the Mac desktop. Windows apps and files run from here, but the device driver files must be located on the “actual” PC.

Best Regards,
FTDI Community

Test and Review Area / Vinculum II Toolchain Patch V2.0.2-SP3
« on: October 25, 2021, 04:37:54 PM »
Hello All,

We have an update for some VNC2 drivers which include some improvements.

Please contact support1@ftdichip.com and we can send you the installer via SFTP.

Note that you must have V2.0.2-SP2 already installed which can be found here:


Vinculum II Installer V2.0.2-SP3.exe will be supplied which is a patch to update all the drivers and libraries (stdio, stdlib etc).

The changes are listed here in the patch readme:


This is patch Version 2.0.2-SP3 release of the Vinculum II Toolchain, comprising updated device drivers and libraries.

All ReadMe file information applies to the updates provided in V2.0.2-SP3.

*** This patch installer must be applied to an installation of V2.0.2-SP2 only. ***

There are no updates to compile, debug, or other build and configuration tools; sample code; VOS kernel; Vinco libraries; IDE; or documentation.

We welcome suggestions for new features or improvements to existing features.

The ReadMe files for previous releases are also available in the installation directory.
Drivers Readme

Fixed Issues:
- USBSlaveFT232.a fix enumeration issue;
    Add in latency timer get and set IOCTL functions,FTDI_SET_LATENCY_TIMER and FTDI_GET_LATENCY_TIMER were present but not implemented;
    Improve data flow so data is passed faster and more reliably to and from the host;
    Implement a dummy EEPROM to enable applications that require EEPROM checks to work.
- USBSlave.a correct remote wakeup behaviour when acting as a USB device and ensure correct ZLP generation for USB verification tests.
- BOMS.a implement changes for 64kB clusters on FAT16.
- FAT.a fix available cluster count.
- USBHostFT232.a correct baud rate settings for High-Speed devices. Added support for new FTDI devices.
- USBHost.a fix VOS_IOCTL_USBHOST_DEVICE_SET_CONFIGURATION to change the configuration of devices on USB host. Note: this will re-enumerate with the new configuration value.
- USBHostCDC code fix bitmaps for notifications.

- FAT library will not support ATAPI disks.
- FAT library does not support FAT12 format disks. Please use FAT16 or FAT32 format.
- FAT fat_fileCopy function will only copy files to a different disk from the source disk.
- USBHostFT232 driver does not assert RTS or DTR automatically when flow control is enabled.
    This must be done with an VOS_IOCTL_USBHOSTFT232_SET_RTS/DTR before data can be received.

Known Issues:
- N/A

Runtime Libraries Readme

Fixed Issues:
- Corrected return value of printf(), sprintf(), fprintf().

- N/A

Known Issues:
- N/A

Best Regards,
FTDI Community

Test and Review Area / LibMPSSE Beta
« on: March 04, 2021, 10:46:48 AM »
Hi Everyone,

We have a beta version of libMPSSE 1.0.2 which includes various improvements as well as a Linux 64-bit version.

This also adds support for our latest Power Delivery ICs (FT23xHP, FT223xHP, FT423xHP).

Please contact support1@ftdichip.com for this version before we release it to our website.

Let us know if you have any feedback please.

Best Regards,
FTDI Community

Test and Review Area / FT_PROG
« on: August 14, 2020, 09:25:27 AM »

We have created a new version of FT_PROG to fix programming issues with FT2232H/FT4232H.

This can be downloaded from our FTP server:

FT_Prog_v0.0.127.511 Installer.exe

Please let us know if there are any additional issues.

Best Regards,
FTDI Community

Test and Review Area / FTDIUSBSerialDriver_v2_4_4 (macOS)
« on: May 27, 2020, 03:42:14 PM »

Customers using macOS 10.15 Catalina have been experiencing signature issues with FTDI's VCP driver.
The following driver should resolve these issues:


Please let us know if you have any feedback on this driver by either posting here or emailing us at support1@ftdichip.com

Best Regards,
FTDI Community

Test and Review Area / LibFT260 v1.1.2 Beta
« on: September 04, 2019, 09:39:01 AM »

We have a new beta version of LibFT260 here. It adds a 64-bit DLL as well as some updates to the example code.


Please let us know if you have any feedback on this beta by either posting here or emailing us at support1@ftdichip.com

Best Regards, FTDI Community

Discussion - Drivers / HLK Studio Error
« on: October 03, 2017, 02:16:34 PM »
Some of our customers are having problems with Driver Reseller Rights for our submission ID 1152921504627044695.
When they open the .hlkx files in HLK Studio, the following error appears:

"Package (Shell_1152921504627044695.hlkx) with a version ( is not compatible with this instance of PackageManager.  This instance of Package Manager accepts versions,,,"

This appears to be a problem with the latest version of HLK Studio version 1703:


If you download 'Get the HLK Insider Preview' at the link above, the issue is resolved with this preview version.
Note: You need to be a member of the Windows Insider program to download this preview version.

Microsoft plan to release this updated version of HLK Studio.

FTDI Community

Discussion - Drivers / FTDI Driver Reseller Rights
« on: October 03, 2017, 02:03:49 PM »
Microsoft has moved to a new Hardware Dev Center for resell rights, replacing Sysdev:


A resell submission is now called Shipping Label.

We have some reseller guidance on the process which was kindly shared by another customer:

Reseller Guidance.pdf

Note: You need a Microsoft Azure Domain Account.

More information can be found on Microsoft’s website since it’s their process.
If you need additional support, contact Microsoft.

FTDI Community

Discussion - Drivers / Create a Project Using the D2XX Drivers
« on: October 03, 2017, 11:27:30 AM »
The user can create 32bit or 64bit dynamic or statically linked projects using the D2XX drivers.

Read more in TN_153 Instructions on Including the D2XX Driver in a Visual Studio Express 2013 Project

The necessary driver files can be downloaded here:

D2XX Drivers

Note: The current free version of Visual Studio is Visual Studio Community 2017.
It allows you to use for 30 days without a Microsoft account. However, after this period it asks you to sign in. You can create a free Microsoft account which will allow you to continue to use Visual Studio for free.

The following simple code can be used as a test:

#include "stdafx.h"
#include <windows.h>
#include "ftd2xx.h"
int main()
FT_HANDLE ftHandle;
FT_STATUS ftStatus;
ftStatus = FT_Open(0, &ftHandle);
ftStatus |= FT_SetUSBParameters(ftHandle, 4096, 4096); // Set USB transfer sizes
ftStatus |= FT_SetChars(ftHandle, false, 0, false, 0); // Disable event characters
ftStatus |= FT_SetTimeouts(ftHandle, 5000, 5000); // Set read/write timeouts to 5 sec
ftStatus |= FT_SetLatencyTimer(ftHandle, 16); // Latency timer at default 16ms
ftStatus |= FT_SetFlowControl(ftHandle, FT_FLOW_NONE, 0x11, 0x13); // No flow control
ftStatus |= FT_SetBaudRate(ftHandle, 9600); // Baud rate = 9600
ftStatus |= FT_SetDataCharacteristics(ftHandle, FT_BITS_8, FT_STOP_BITS_1,
if (ftStatus != FT_OK) printf("ftStatus not ok %d\n", ftStatus); //check for error
char data_out[12] = "Hello World";
DWORD w_data_len = 12;
DWORD data_written;
ftStatus = FT_Write(ftHandle, data_out, w_data_len, &data_written);
char data_in[12];
DWORD r_data_len = 12;
DWORD data_read;
ftStatus = FT_Read(ftHandle, data_in, r_data_len, &data_read);
if (ftStatus != FT_OK)
printf("ftStatus not ok %d\n", ftStatus);
printf("Data Read: %s\n", data_in);
ftStatus = FT_Close(ftHandle);
printf("Press Return To End Program");
return 0;

Test and Review Area / libMPSSE Beta
« on: October 03, 2017, 11:25:29 AM »
Hi Everyone,

We have a new beta version of our libMPSSE library below:


This has several updates compared to the release currently on the website including:
- Resolves issue with multi-byte reads on I2C
- Resolves issue with opening device on some USB3 ports (opens by Description instead of location ID)
- Sends I2C Stop condition if the Master terminates a transaction
- Improved clock granularity in I2C_CLOCK_HIGH_SPEED_MODE
- Fix for clock resolution issue on FT2232D

We are currently testing the beta and hope to release it soon but if you have any feedback on the new beta then please let us know.

Thanks, FTDI Community

Window CDM WHQL Certified Driver v.2.12.28 is now available!
This applies to the following Windows OS versions:

Windows 10 (32/64)
Windows 8.1 (32/64)
Windows 8 (32/64)
Windows 7 (32/64)
Windows Server 2016
Windows Server 2012 R2 x64
Windows Server 2008 R2 x64

Download here:

2.12.28 driver files
Setup Executable

This driver version is also on Windows Update so should install automatically if you are connected to the internet.

You can also refer to the Installation Guides

If you have any feedback, please let us know.

FTDI Community

Shared Projects / USB Current and Voltage Monitor
« on: September 21, 2017, 04:53:20 PM »
Hi Everyone,

Here is a small project that our Applications engineers designed using a UM232H module in MPSSE mode. It acts as a USB to I2C Master bridge to take readings from a Texas Instruments INA219 current and voltage monitor. It also provides a couple of GPIO input lines and (most importantly of course) a flashing LED!

It connects in-line with a USB device and tracks how much current it is drawing from the host as well as the voltage on the VBus line. The 0.1" connector on the rear panel can be used instead if you want to connect it to measure other circuits via jumper wires. This can be really useful when debugging your own circuits and checking how much power they will require.

A program written in Visual Basic NET displays the results on a scrolling chart with different range settings. You can modify the code to talk to other I2C sensors as well though.

Here are some pictures showing the meter itself and a chart showing a USB flash drive which was connected and enumerated accessing a file on the disk.

We have written a document on the project as well as publishing the source code, and you can find these at the links below:

Source Code

We hope this gives you some ideas for some projects of your own ...

Best Regards,
The FTDI Team

Pages: [1]