If the executable fails, you can install the driver manually via Device Manager: Connect the FT231X to the computer.
Scroll down to find a message stating "System software from developer 'FTDI' was blocked from loading." Click and enter your administrator password. Restart your Mac to finalize the installation. FT231X Setup on Linux
Alternatively, use to right-click the "Unknown Device," select Update Driver , and browse to your extracted driver folder. 2. macOS
: Once installed, your device will appear under Ports (COM & LPT) . Make a note of the COM number (e.g., COM3) to use in your terminal software like Putty or the Arduino IDE. Future Technology Devices International Ltd. FT231X - FTDI ft231x usb uart driver link
Download the (look for the link in the comments or right-hand column, usually labeled as an .exe file like "Available as a setup executable").
Run the .exe file before plugging in your device to ensure proper configuration.
Modern macOS versions include native support for FTDI devices (AppleUSBFTDI). However, if you experience dropouts or need advanced configuration capabilities, installing the official VCP driver is recommended. Download the .dmg file from the FTDI site. Double-click the downloaded disk image to open it. If the executable fails, you can install the
This behavior is usually caused by Windows power management settings turning off the USB root hub to save energy.
Here’s a full write-up on the , including what the FT231X is, why drivers are needed, and where to find the official drivers.
the downloaded file and select "Run as Administrator". FT231X Setup on Linux Alternatively, use to right-click
The FTDI VCP driver is baked into the Linux kernel (as part of the ftdi_sio module).
Unplug the device, uninstall the existing driver from Device Manager, restart your PC, and install the latest executable version from the official link. Try a different USB port (preferably a USB 2.0 port instead of USB 3.0). 2. Device Disconnects and Reconnects Randomly
This error often points to a driver conflict or a faulty USB cable.
Open a terminal and run ls /dev/cu.* (Mac) or ls /dev/ttyUSB* (Linux) to verify that the system has assigned a communication path to the device.