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

Pages: [1] 2 3 ... 10
 on: June 11, 2021, 05:40:38 PM 
Started by Tycho - Last Post by FTDI Community

SPI modes 1 and 3 are not supported with our MPSSE engine.
If you require these modes, then you will need to consider FT4222H:


Best Regards,
FTDI Community

 on: June 10, 2021, 12:12:10 PM 
Started by Tycho - Last Post by Tycho

I'm getting wrong readout values if I increase the baud rate to 30 MBaud, see screenshots. I'm transmitting 0x1010 as MSB, CPOL=1, CPHA=0. At 5, 10 and 15 MBaud everything is ok, but at 30 MBaud, although the oscilloscope picture seems to be ok, there is a bit shift.

Are there any issues with FT232H SPI at high baud rates?

Thank you very much in advance!

 on: June 10, 2021, 11:45:40 AM 
Started by j.pflaum - Last Post by j.pflaum
I am building a software (in c) which on the one side connects to a device with a FT601 using FTD3XX library and on the other side to another software via TCP/socket communication.
I am using multiple threads - 1. TCP incoming data + USB outgoing data / 2. TCP outgoing data / 3. USB incoming data. Number 2 and 3 share a ring buffer.
For the USB incoming (asynchron read from USB) I used the FTDI data streamer demo app as a template:

 - SetStreamPipe
 - InitializeOverlapped
 - ReadPipeEx
 - Rerun:
    - GetOverlappedResult
    - ReadPipeEx

After a undefined time the GetOverlappedResult always throws an Timeout Error (FT_STATUS: 19 / GetLastError(): 121). Once the failure occures, it will always be there even after restart of both Computer and Device.

Can anyone explain to me, what is going on and what I am missing / doing wrong? Or how I can fix this?

Thank you and best regards

 on: June 09, 2021, 08:16:17 AM 
Started by LeNiCiDE - Last Post by LeNiCiDE
Thanks to FTDI support - the issue was with floating TEST pin. Pin was floating - this is the cause of problem. Heating up the device was successful solution because of this floating pin.
Read the datasheet carefully! (see attachment). Connecting this pin to GND solved the issue.

 on: June 08, 2021, 02:04:40 PM 
Started by vogl - Last Post by vogl
For abaout five  years we use successfully a FT4222H to implement a  USB-SPI and USB-GPIO bridge in a Windows 10  based system.
The version of the FTDI Windows driver was up to now

Recently some customers did a Windows update and the FTDI driver version changed to
With this version we cannot use the USB-GPIO bridge function.
The library call  „FT_CreateDeviceInfoList()“ recognizes only 1 device (the USB-SPI-bridge).
With the former driver 2 logical devices were recognized.

In the Windows device-manager both logical devices  „FT4222H Interface A“ and „FT4222H Interface B“ are shown regardless of the driver version.

This behaviour can be reproduced with the „gpio_write“-sample in LibFT4222-v1.4.4.

Any hints?

 on: June 07, 2021, 05:28:35 PM 
Started by EnsAltun - Last Post by FTDI Community

Yes that's correct, the RAM_G is just for loading assets like fonts and images and the other RAM areas (like RAM_DL, RAM_CMD and RAM_REGISTERS) are all separate areas of the memory map. Therefore the fullness of RAM_G won't cause EVE to slow down or cause it to work incorrectly.

Best Regards, FTDI Community

 on: June 07, 2021, 05:02:45 PM 
Started by LeNiCiDE - Last Post by FTDI Community

You are already in contact with our technical support team on this matter via email.

Please feel free to post any resolution here to help other community users.

There may also be other FTDI Community users who will be able to help you.

Best Regards,
FTDI Community

 on: June 07, 2021, 02:18:36 PM 
Started by LeNiCiDE - Last Post by LeNiCiDE

I've got strange behavior of my PCB. When I take the device and plug it in for the first time Windows can't recognize my board. If I reset the FT232 on RESET pin everything is ok. When I heat up the device with hot air the problem dissappears - FT232 is recognized by PC. What can cause that, I've tried various combinations I've even desoldered ADUM5020 and ADUM4160 from the board.

If the device is connected and I take out the cable, next connection can be established - sometimes it isn't. But when I move cable a little bit to disconnect only data pins (not power pin) device is recognized by PC (this trick with not fully disconnect cable works only if the device established connection with windows before cable movement).

Here is scope image of the reset pin after plugging in the cable - no connection established (blue RESET, yellow VCC on VCC pin of FT232):
"low_temp.png" (see attachment)
Here is scope image of reset pin after heat up with hot air and plugging the cable (connection established):
"high_temp.png" (see attachment)

Power seems OK.

 on: June 04, 2021, 04:35:27 PM 
Started by Tycho - Last Post by FTDI Community

FTDI devices use USB Bulk transfers and those are designed to transfer large amounts of data with error-free delivery, but with no guarantee of bandwidth.

You could try reducing the latency timer to 1ms to see if it helps.

Best Regards,
FTDI Community

 on: June 04, 2021, 10:31:52 AM 
Started by Tycho - Last Post by Tycho
If I understood it correctly, LibMPSSE DLL is built on top of FTD2XX.dll. This will not solve my problem because I already implemented SPI with FTD2XX.dll.

The question is: are the delays caused by USB bulk in general or is it wrong use of FTD2XX.dll on my side?

Pages: [1] 2 3 ... 10