libftdi Archives

Subject: Re: FT232H Read returns zero byte

From: Ali Ebrahimi <ali.ebrahimi@xxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Mon, 25 Sep 2017 12:35:45 +0200
Thank you for the quick reply, Thomas.

Does this mean libftdi 1.x should not have this problem?

Also, would you please let me know if the sync fifo mode of 232h has been 
tested and if there is a working example?

Thank you again,
Ali

On Sep 25, 2017 11:04 AM, Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> wrote:
>
> Hello Ali, 
>
> On Monday, 25 September 2017 10:35:01 CEST Ali Ebrahimi wrote: 
> > I have a FT232H chip connected to a FPGA. It is set to comunicate using the 
> > sync fifo mode. I used to have a software on Linux written based on the 
> > D2XX driver to communicate with the chip and everything was fine except 
> > that the troughput was limited to less than 10 MB/s. 
> > Now I have switched to libftdi but ftdi_read_data() frequently (but not 
> > always) returns zero bytes. I have checked the mailing list archive and I 
> > guess my problem is very similar as the one discussed here: 
> > http://developer.intra2net.com/mailarchive/html/libftdi/2010/msg00295.html 
> > I checked the code of libftdi.c and the patch is not implemented there nor 
> > I 
> > can find any trace of it on the git.  Would you please let me knwo what has 
> > happened to this patch? Also I would appreciate other suggestions to fix 
> > the problem. 
>
> the fix was for libftdi 0.x only: 
>
> $ git show 3b92d479565a413c7b9f830c34c93886ba366347 
> commit 3b92d479565a413c7b9f830c34c93886ba366347 
> Author: Uwe Bonnes <bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 
> Date:   Fri Jun 25 17:41:28 2010 +0200 
>
>     Let ftdi_read_data() honor usb_read_timeout 
>
> Cheers, 
> Thomas 
>
>
> -- 
> libftdi - see http://www.intra2net.com/en/developer/libftdi for details. 
> To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   
>


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx  
Current Thread