Hello,

Which driver version is installed? The latest is 2.12.28.

Can you please test with our standard hardware to rule out any issues with OEM hardware?

See our Development Modules:

FT-X Breakout Modules
FT-X Development Modules

It looks like you are also into contact with our support team via email. Please continue to work with your local support team member and feel free to post any resolution here to help other users.

Best Regards,
FTDI Community

Hello Jason,

V2DIP1 gives access to USB Port2 but "UART to FT232 Host Sample Application ROM" is built to access USB Port 1.

You could consider editing the code and rebuilding for USB Port 2, or purchasing V2DIP2 which gives access to both ports.
However, consider the information below.

Vinculum-II is a very mature products and has been superseded by FT9xx.

Hosting FT232 devices with these older Vinculum-II products can be unreliable.
It takes a lot of the MCUs resources to run the FT232 device code (eg FT232Uart) so there can be performance issues.
I wouldn’t recommend using this product for this application because you will most likely run into problems.

The best solution we have is our FT90x MCU.

There are lots of other examples available:

AN_360 FT9xx Example Applications
FT90x Software Examples
FT9xx Software Examples

Take a look at FT90x UART to FT232 Host Bridge, there is already a software example which can host FTDI devices.
A video has been created which demonstrates this:

https://youtu.be/_vwOKFaOcJI

There are significant benefits of FT90x:

-Eclipse based IDE
-Source code for API drivers is provided
-Significant performance improvement
-Actively in development by R&D
-Improved documentation and software examples

We provide FT9xx Development Modules and a free FT9xx Toolchain for custom application development.

Best Regards,
FTDI Community

Hello,

Which FTDI chip part number do you have and what hardware circuit are you using?

You could try connecting it to a Windows PC via either VCP (e.g. a terminal) or D2xx to see if the hardware itself is sending back characters.

Loopback examples are suited to UART applications but if your chip is a parallel one (such as FT245R) then it needs to be connected to a suitable device (such as an FPGA or MCU) on the parallel side which will read the data and write it back in as the parallel interface does not directly allow loopback.

Also check for the RxD line (if UART) or the write strobe (if parallel) being held in the active state by the external circuit as this can result in data being sent to the PC.

Best Regards,
FTDI Community

Hello,

I noticed we are currently dealing with your questions via Email, please feel free to post any resolution here.

Best Regards,
FTDI  Community

Hello,

Would it be possible to see the section of code your application is getting stuck at?

You may want to look at the FT_Timeouts function in the API:
https://www.ftdichip.com/Support/Documents/ProgramGuides/D2XX_Programmer's_Guide(FT_000071).pdf

Best Regards,
FTDI Community

Hello Maxwell,

The VCP or D2XX drivers can be used to control the IC:

However note the data transfer rates:

• up to 1 Megabyte / second with the D2XX Direct Drivers.
• up to 300 kilobyte / second with the VCP Drivers.

Please see the FT245R Datasheet for more information.

TN_167 FTDI FIFO Basics also provides useful information.

So if you are using the VCP port via a terminal, simple read and writes are possible.
Note the FT245R is a FIFO slave which is controlled by a master.

You can test and evaluate using our UM245R.

Best Regards,
FTDI Community

Hello,

There is nothing in particular with FT230X (vs FT232R) which would cause this issue.
So there must be some issue with your custom PCB.

CTS/RTS flow control signals are used to avoid data loss at high speeds but would probably not avoid data corruption like you are seeing.
Have you wired them up as a test case anyway?

Best Regards,
FTDI Community

Hello,

Thanks for your post.

I believe that you have also contacted email support where we will continue to deal with your issue and post any resolution here.

Regards,
FTDI Community