Hi,

We will have a look through your details provided but here is a link to the latest beta and source code:
LibMPSSE

Best Regards, FTDI Community

Hello,

Which USB interface are you using?
If you are using the USB D2XX interfaces on this FT90x then this is possible.

See the D2XX examples here:

AN_360 FT9xx Example Applications

Also see the D2XX Programmer's Guide which provides software examples.

In your application running on the PC, calling FT_Write would write data to the FT90x via USB then you could read that data using D2XX_Read.
See section 2.35 D2XX Feature in AN_365 FT9xx API Programmers Manual.

If you need further support, feel free to [urlhttps://www.ftdichip.com/FTContact.htm]Contact Us[/url].

Best Regards,
FTDI Community

Hello,

Thanks, I have passed these on to the development team.

Best Regards,
FTDI Community

Hello,

Thank you for pointing this out, I will pass this on to the development team and hopefully they can take account of your suggestions for the next release.

Best Regards,
FTDI Community

Hello,

Yes, that is correct, but again you should be able to take the settings/configuration defined in those examples and utilise them in the library you are using.

The FT90x is our series of MCUs, you can find our more at the following:
https://www.ftdichip.com/MCU.html

Best Regards,
FTDI Community

Hello Rajesh,

USB suspend is controlled by the USB host telling the peripheral device to go to suspend.
The FTDI drivers do not force the FTxxx devices to go to suspend.
If the USB data bus is idle for >3ms the USB host should put the FTxxx into suspend.
To prevent this happening you should ensure there is always data within 3ms.

The 245 FIFO interface should only be written to when the TXE# pin is logic 0.

The TXE# pin will go to logic 1 and back to logic 0 for every byte latched in.

If the application on the PC never reads any data the buffer on the PC (64kbytes) and the buffer on the chip will become full.

When these buffers are full the TXE# line should remain at logic 1 until the application on the PC does a read to free up some space.

Some users report TXE# goes back to logic 0 after a brief period (actually matches latency timer).

This can result in data loss due to overrun.

To prevent this from happening the application on the PC should have set flow control for RTS_CTS flow control.

Although the hardware does not have RTS/CTS pins the driver does not know this, but it is now forced to monitor certain status bits, which allows the TXE# pin to be kept at logic 1 until space is made available.

Best Regards,
FTDI Community

Hello,

You can email in to support1@ftdichip.com.
Please quote this thread.

Best Regards,
FTDI Community

Hello,

If you can capture a USB analyser trace of the software executing and the FT_IO_Error happening we can investigate this occurrence further.

Best Regards,
BRT Community