Hello,

could you please email your schematic to support1@ftdichip.com? we can then review it for you to see if there is anything that could be causing your issue.

Best regards
FTDI Community

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,

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

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

Hello,

According to LibMPSSE-SPI User Guide when using our MPSSE library it's possible to run at 30Mhz:

uint32 ClockRate
This parameter takes the value of the clock rate of the SPI bus in hertz. Valid range for ClockRate is 0 to 30MHz.

So you can maybe try with our library which has source code provided for reference.

These also may be useful to you:

AN_114 Interfacing FT2232H Hi-Speed Devices To SPI Bus
AN_180 FT232H MPSSE Example – USB Current Meter using the SPI Interface

Other software examples exist:

https://ftdichip.com/software-examples/mpsse-projects/#usb-to-spi-interface

Also please also note, SPI modes 1 and 3 are not supported with our MPSSE engine.
So please check that your SPI device doesn’t work with these modes.

We also have a support office in Taiwan.

Best Regards,
FTDI Community

Hello,

When using our products in electrically noisy environments, you can try in section 5.1 Adjusting the Reset Pipe Retry Count of AN_107 Advanced Driver Options.

You can also edit the registry, opposed from editing the INF files which breaks driver signing.

Note that registry entry may need to be created:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FTDIBUS\Parameters\RetryResetCount
The default value is 50 so you can try increasing to see if it has an effect.
This can stop USB disconnects in electrically noisy environments.

The above might be something additional to try to see if it helps, otherwise modify your hardware to cope in electrically noisy environments might be the best way forward and check if you are using a USB certified and shielded cable.

Best Regards,
FTDI Community

Hi Scott,

The only vendor class devices supported by VNC2 are FTDI vendor class devices.

You should have a look at the FT90x series that is made by our sister company Bridgetek. FT90x is a programmable host controller, like VNC2, however it is open source so you can create your own software.

Best Regards
FTDI Community