FTDI FT232HL DRIVER

Sign up using Facebook. There must be something to fix because there are numerous examples of people reaching high transfer rates. Back in the early days before people understood the issues, adding a USB serial converter to something that worked fine on a local bus serial port could completely break its usability. As written on the message, no matter how many bytes sent at once, the delay is same. I have it set to , but often for timing sensitive stuff, I have it lower 2 Try a slower clockrate first just to test and make sure the device is communicating correctly I assume you did, I’m just adding this in case someone else hasn’t tried that yet. Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of service , privacy policy and cookie policy , and that your continued use of the website is subject to these policies.

Uploader: Mim
Date Added: 13 June 2012
File Size: 47.44 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 38395
Price: Free* [*Free Regsitration Required]

How are you delivering the data to the drivers?

Recent Posts

As written on the message, no matter how many bytes sent at once, the delay is same. By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies. Why are you looking only at SPI side of your bridge? If the chip is clocked slowly, then this will show at the higher frequencies as a larger gap between bytes.

  82562EZ PLC XP DRIVER DOWNLOAD

I’ve used sample code provided with sample-dynamic. There is is a small delay between bytes, but nowhere near as large as 64us. I’m still surprised some people can reach high transfer speeds out of the box and using the provided lib.

This is what it looked like on my logic analyzer when I output 6 bytes at once at a clock rate of 5MHz. Sign up using Email and Password. Also, delay between bytes should be a setting somewhere.

Here is some quick example code on how to send multiple data bytes in case it helps.

Also, I use master spi mode, write-only, there shouldn’t be any handshaking involved. In what size chunks? Are you sure that USB side is sending data fast enough? Here is the configuration fg232hl GCC Library and code from: I’ve contacted FTDI support, they asked me to update the libraries to latest one which I didthen they would not provide further support.

Here is the configuration used:. That’s often now understood, but SPI can involve coordination with other signals like selects, so it’s easy to imagine being hobbled by bus framing and unable to leverage the theoretical data rate that would apply to larger ft232ho.

Note that for SPI it doesn’t matter if the clock is stretched a little bit here and there since it is based on the edges of the clock signal read on one edge, propagate on the other. I have it set tobut often for timing sensitive stuff, I have it lower 2 Try a slower clockrate first just to test and make sure the device is communicating correctly I assume you did, I’m just adding this in case someone else hasn’t tried that yet.

  KWORLD ATSC 340U DRIVER

I imagined maybe playing with the channelConf. I tried to recreate the problem you describe, but I wasn’t able to exactly. If you make a single call, add the appropriate chip select enable and disable flags see below.

FTDI FTH USB 12Mbps results – Black Mesa Labs

If this is a custom board design, or you bought a discount FTH adapter board, make sure it has the correct system clock frequency. Latency timer really shouldn’t matter because that is simply a timeout before USB will send an incomplete packet.

Sign dtdi or log in Sign up using Google. However, between each byte, there is a 64uS delay so it means that no matter how high is the SPI clock, the data transfer takes minutes instead of seconds.

Here are some things to check. Post as a guest Name.

Sign up using Facebook. I did check with a logic analyser, the bytes are correctly sent out and the SPI clock match the settings. If you make multiple calls, make sure to add the chip select flags to the first and last calls in the series.

Back in the early days before people understood the issues, adding a USB serial converter to something that worked fine on fti local bus serial port could completely break its usability.