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.

Messages - FTDI Community

Pages: [1] 2 3 ... 56
Discussion - Software / Re: FTD2XX_NET.DLL - how do I make it work?
« on: March 23, 2023, 04:19:37 PM »
Hi Nebr,

MX-Series II is an OEM device that is not made by FTDI, but it does seem to be using one of our chips inside. the issue may be that the device is using a custom driver. could you please send me a USBView screenshot of the device plugged in please and i can check the VID/PID.

You can also reference our C# examples. They can be found on our website here: C# Examples.

Best Regards
FTDI Community


JTAG and I2C re controlled by the MPSSE engine which is not configurable in the EEPROM.

MPSSE mode is enabled with FT_SetBitMode API command. See the D2XX Programmer’s Guide for more information.

The only JTAG support can be found here:

(Note this also includes I2C support)

There are two options to use JTAG modes with the MPSSE engine:

1.   Use FTCJTAG DLL library. Example code is provided with the download (This code is no longer supported by FTDI)
2.   Use D2XX drivers direct. Example code is shown at the link above, further down the page (JTAG). AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information.

Option b is the best option to use the D2XX drivers direct (no dependency on our library).

Unfortunately we don’t support OpenOCD. However there might be information online about it or other FTDI Community users can help.

Best Regards,
FTDI Community


FT260 can't act like standard HID class devices (keyboard, game controller, etc).

The FT260 supports 3 modes:
-   USB-HID to I²C
-   HID-over-I²C, supports Microsoft’s HID-over-I²C protocol.

The first two modes are general data bridge via HID class.

In HID-over-I²C mode, the FT260 needs to configure a interrupt to communicate the attached device.
This would use a built in driver for this. This is a defined protocol and the I2C device would need to support this too. This can be used for touchscreens for example.

The “HID-over-I²C” protocol is defined by Microsoft, and you can check the following link for the specification:


Best Regards,
FTDI Community

Discussion - Software / Re: Using same MPSSE channel for SPI and GPIO
« on: March 17, 2023, 04:29:58 PM »

This can only be done when using D2xx direct and not using LibMPSSE.

When using LibMPSSE, GPIOL[0:3] can only be used as SPI chip selects.
When using LibMPSSE, there is no way to control GPIOL[0:3] as GPIO.
LibMPSSE demonstrates controlling the higher line bytes (GPIOH) while using SPI on the lower line bytes using the following functions:
If you want to control some of the unused lower line bytes on the same ADBUS as SPI then see AN_411 FTx232H MPSSE I2C Master Example in C which demonstrates GPIO usage with MPSSE using D2xx direct (not using LibMPSSE).
This could be used as a base to understand using both SPI/GPIO in the same code.
OK this example is for I2C but the same principles apply to SPI.

Best Regards,
FTDI Community

Discussion - Drivers / Re: FT260 MACOS Lib
« on: March 10, 2023, 04:21:22 PM »

This information is incorrect.

FT260 can only be accessed via HID class drivers.

FT260 can't be used with VCP or D2xx drivers which are USB Vendor Class drivers. Other FTDI ICs can use these drivers.

If you are looking for I2C Master and UART interfaces then you can consider the other alternative USB Vendor Class devices which means that they use standard FTDI VCP / D2xx drivers.

FT2232HQ / FT2232HL / FT2232H-56Q
These are dual channel USB ICs which means one channel can be used for UART (VCP or D2xx) and one channel can be used as I2C master (D2xx only).

Quad channel IC also available which would give an additional two channels which can be used for GPIO/I2C Master/UART: FT4232H-56Q / FT4232HQ / FT4232HL

You can find these ICs and associated development modules on our website.

Best Regards,
FTDI Community

Discussion - Hardware / Re: SPI Slave
« on: March 07, 2023, 04:33:07 PM »

If you use FT4222_SPISlave_Write() to write SPI slave data it will append 0x00 in every time the API FT4222_SPISlave_Write() is called.

You can also try to replace FT4222_SPISlave_Write() with FT_Write() as it does not append 0x00 at the beginning.

There are only two USB FIFOs to store the data from PC Host and each FIFO is 512 bytes (but status bytes occupy 2 bytes).
When the API FT_Write() is called, it will send a bulk transfer.
If the transfer size is <512 , it will be treated a short packet transfer and occupy one USB buffer.
If the transfer size is >=512 and <=1024, it will be treated two packets transfer and occupy two USB buffers.
SPI Slave is a passive transfer.
Also make sure the SPI Master sends the clock and do not let the buffer overflow.

Best Regards,
FTDI Community

Discussion - Drivers / Re: FT260 MACOS Lib
« on: March 03, 2023, 03:55:33 PM »

LibFT260 library is only available for Windows.

If you want to control FT260 on Macos or Linux then you will need to use raw HID class commands.

See AN_394 User Guide for FT260 which includes software examples.

Best Regards,
FTDI Community


We're working with you on this issue via email and we can post the final resolution on this forum once we know.

This will be more helpful for other community users rather than speculating what the issue is without knowing the root cause.

Best Regards,
FTDI Community


You are already are in contact with us via email and we'll reach out to you again to review your code.

We had a similar issue reported in the past and although it looked to be an issue with Windows Update and the 64-bit dll it turned out not to be the case as the application software was opening the wrong interface.

Best Regards,
FTDI Community


Please ensure that you are opening the correct interface.

For example, FT4222H in Mode 0:

Interface A is for SPI/I2C control.
Interface B is for GPIO control.

If you open the wrong interface in your software this can lead to issues.

It's worthwhile checking your mode configuration and application software as uninstalling Windows Security patches should not be the solution.

Best Regards,
FTDI Community


Which version of the D2xx driver and LibFT4222 library are you using?

Which version of FT4222H IC are you using?

If you can send an email to your local technical support team we can take a look into your issue further:


Best Regards,
FTDI Community

Discussion - Software / Re: New to USB, need help to learn how to use FT260
« on: February 22, 2023, 04:17:06 PM »

You should browse to the appropriate area like here:

FTDI Community >General Category >Discussion - Software

Then you need to click on New Topic at the top. Make sure you have logged in.

Alternatively you can send an email to your local support office:


Best Regards,
FTDI Community

General Discussion / Re: FTDI Chips as a USB Host
« on: February 22, 2023, 04:06:26 PM »

Unfortunately we don't have any video tutorials. There may be some online of people using VNC2. For most of the precompiled firmware there are application notes that walk you through how to set the device up. They can be found here:


We have quite extensive documentation for VNC2, that can all be found on our website. These should be able to help you. If you go to the product page for VNC2, on our website https://ftdichip.com/products/vnc2-48q1c/, you can find most of the documentation.

Best Regards

FTDI Community


FT602 can support resolutions up to 1920x1080@60 frames per second. as per the FT602 SuperSpeed USB3.0 IC Datasheet, Section 4.

The twelve bytes of header 0x0000_820C, 0xBABE_FACE, 0xBABE_FACE are UVC Payload header. First word also could (and should) be 0x0000_820C or 0x0000_830C - with FID bit in Bit field header toggling each new frame. As PTS and SCR bits are cleared, and header length is 12 bytes.
Size of frame after that header is also important. It should be 38400 of 32-bit YUY2 data words for 320x240; 153600 for 640x480 and so on. Calculation assumes that each YUY2 32-bit data word contains two pixels, so (320/2)*240 = 38400.

Before the start of each frame the user should send 0x0000_0055 in 32-bit DATA bus with 0x1 on 4-bit BE bus.

Best Regards

FTDI Community

Discussion - Software / Re: New to USB, need help to learn how to use FT260
« on: February 15, 2023, 03:36:16 PM »

unfortunately, FT260 cannot act as a game controller or a game controller. However it is a HID device.

FT260 can be programmed either by using raw HID commands, or its dedicated library LibFT260. There are code examples for LibFT260 available in the library download which is available on the FTDI website. https://ftdichip.com/software-examples/.

we also have some useful documentation for FT260 that you can have a look at:

User Guide for FT260
User Guide for LibFT260

Best Regards

FTDI Community

Pages: [1] 2 3 ... 56