Hello,

Unfortunately the FTDI driver source is confidential so there is no documentation on it apart from the D2XX Programmer’s Guide.

If you wanted to write your own kernel based driver then we could provide an NDA to give you access to the API for FTxxxx Devices.

The USB Host Controller would need to implement FTDI drivers. This is not an easy task.

Please note that we can only provide a table of the USB transfers under NDA (API for FTxxxx Devices) and unfortunately we cannot provide source code samples or support for writing drivers on a particular OS.

Is a table of USB requirement sufficient for your needs?
It requires previous hands on writing USB driver experience for your particular MCU/OS and requires extensive USB knowledge.
It's a difficult task and we don’t provide support for it.

Please contact your local support team for the NDA form.

The other route you may want to explore is LibFTDI which is an open source library/driver but is not created/supported by FTDI:

https://www.intra2net.com/en/developer/libftdi/

This third party solution already includes the source so may suit you if you as the driver source is also supplied and may give you more options.

Best Regards,
FTDI Community

Hello,

Unfortunately this is not something that we have any experience with.

Other FTDI community users may be able to help.

Best Regards,
FTDI Community

Hello everybody. I'm new to the FTDI community.
We have a controller that communicates with the computer via FTDI. We use the D2XX interface functions from the user mode program to communicate with the FTDI driver (device). Now I want to use the FTDI device from kernel mode (Windows), but we don't have any documentation related to the FTDI driver. Please tell me where to find or buy it. Thank you.

Yes, I know that the FT232 and FT245 can only be opened once. They provide a handle once opened.
This is why I only open it once and save the handle in shared memory so that other programs use it for read and write functions, but it doesn't work. I also have the same problem with the VCP driver

Hello,

When using the D2xx driver it can only be accessed by one handle at a time.

Note that FT245B is Not Recommended for New Designs (NRND) and is being made EOL.
See AN_559 Migrating from FT2xxB however the same limitation applies with the D2xx driver.

There could be other FTDI Community members who have experience with sharing a handle in shared memory but it's not something that FTDI support.

Best Regards,
FTDI Community

Hello FTDI Community 

Originally I had a DLL written in Visual Studio 6 ( win98 ) to communicate with an ISA card.
Several programs written in Visual Basic 6 can access this DLL and communicate simultaneously with the card. The DLL is written using mutex principles.
I replaced the bus part of the card with an Ftdi FT245. I rewrote the DLL to use D2xx driver. I can make the programs work, but only one at a time. I use the FT_Open, FT_Write, FT_Read, FT_Close functions.
I tried to share the handle in shared memory.
The other programs recover it well and do not open the port if it is already open, and uses the handle retrieved from shared memory to control the FT_Write, FT_Read functions, but these write and read functions return an error.

Thank you for your help

I need to use FT232H to control an I2C bus, on Windows 10, in a C++ application.
I'm using the AdaFruit FT232H Breakout (Product ID: 2264) on a Windows 10 PC.
Using the latest FTDI DLL.

I've got a Qwiic sensor board connected to the breakout board's Qwiic connector.
The sensor board and cable work fine with a Microchip MCP2221 USB-I2C adapter so they're AOK.
But I can't access the I2C sensor using the FT232H - library goes into an infinite loop.

I understand I should use the FTDI MPSSE library.
On your forum I found you have released LibMPSSE 1.0.3 to your website:
https://ftdichip.com/software-examples/mpsse-projects/

I downloaded the following and incorporated it into my project:
https://ftdichip.com/wp-content/uploads/2022/07/LibMPSSE_1.0.3.zip

Unfortunately, inside I2C_InitChannel, FTDI's libMPSEE software goes into an infinite loop in FT_InitChannel.
The call stack is attached.

Any idea what is going on???
Is there an updated version of the library with bugfixes?
Thanks in advance for any help,
Best Regards, Dave


PS: Here's the program output:
Hello World!
ftd2xx.dll loaded OK!
Found at least one channel on FT232H
Information on channel number 0:
                Flags=0x2
                Type=0x8
                ID=0x4036014
                LocId=0x22
                SerialNumber=FTP6SN3W
                Description=FT232H
                ftHandle=0x0 (0 unless channel is open)

Version Check
libmpsse: 00010001
libftd2xx: 00030216

handle=0xc586c8 status=0

>>> Goes into infinite loop inside I2C_InitChannel...

PS: With an older version of the library, the channel initialized but I could not access
the I2C device (it always reported FT_DEVICE_NOT_FOUND).

Hi,

My name is Joe. I have been doing embedded projects since 2001. I have used FTDI for my USB bridges to UART and SPI.

Cheers,
Joe

Tools: Vinculum ii IDE
Chip: 32pin VNC2
Application size has plenty of flash left, only at 227000 bytes.

For some reason when I write a single page of flash, the SPI device stops working...  any ideas?

Basically this is all I am doing, then after that the SPI stops working. Tried other page locations.  What is odd, is the flash write works. I can restart, and read the correct data from the flash.

flash_writePage(0x7ff, temp_string);

HI Petrov,

We are not sure when the next update for the library will be released, however, as the source code is available on the website, customers can make their own changes and rebuild the library for their own use.

Customers can also develop their own code using D2XX direct driver. You can have a look at Command Processor For MPSSE and MCU Host Bus Emulation Modes this will allow you to not rely on LibMPSSE.

Best Regards
FTDI Community