gmane.comp.hardware.libftdi.general

RE: ftdi_eeprom link failure

xantares 09 — 2013-05-21T06:49:41



Hi,

Could we merge this ?
https://gitorious.org/libftdi/libftdi/commit/8b860ed08731ae6ab639973735b376de3694a199

M.
       

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: CPU Overhead?

Jim Paris — 2013-05-10T17:09:50

If all you need is to stream serial data, use the kernel driver:
   modprobe ftdi_sio
   cat /dev/ttyUSB0 > file
It's higher performance, lower overhead, and simpler.

-jim

Krishnendu Chatterjee wrote:

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: CPU Overhead?

Krishnendu Chatterjee — 2013-05-10T06:35:40

Hi,

I presume, you are going to run your application on ARM running Linux. If
so, D2XX driver cannot offer that kind of throughput. This is because
"overlapped I/O" is not supported by D2XX driver on Linux. And you need
overlapped I/O to sustain this kind of data rate. The reason is data fetch
from FT2232 occurs only when FT_Read is executed. But due to application
scheduling, your application, and hence the FT_Read function, may not be
executed for sometime. The on-board 4kB buffer of FT2232 will provide some
space to breath. But if it is full, and your application is not yet
scheduled, then you will loose data.

The way out is "overlapped I/O", which registers a number of transfers to
the operating system, which can execute in the background as a parallel
thread. These transfers are controlled by the device driver and interrupts.
Hence they are less likely to be affected by the scheduler.

Overlapped I/O is a Windows term. On Linux, they are replaced by
asynchronous I/O. The latest libFTDI offers asynchro

CPU Overhead?

Peter Witkowski — 2013-05-10T04:16:35

Hello,

I am writing an application that uses the FTDI FT2232H chip to read RS-485
data.  The data is coming in at a fairly high rate (6 Mbps baud rate with
an effective data rate of about 3.2 Mbps).  My application must read in the
data and then process it as quickly as possible.  Latency is frowned up,
however I can generally accept up to 250 ms.

I have interfaced with the device using the D2XX driver provided by FTDI.
Overall, the application works fine from a functional standpoint.  However,
the D2XX driver alone pulls about 45% CPU usage.  I have to run the
application on an embedded ARM processor, which runs at 720 Mhz, so I don't
have alot of horsepower per say.  I am using the FT_Read() function in a
loop to extract the data and then pass it along.  In a simple application I
wrote to test the driver, I extract the data in the loop and just write it
to a file.  This alone pulls the 45% CPU usage figure (numbers from the top
command) referenced earlier.

My problem is that I just received requirements

Re: ftdi_eeprom link failure

Hannes Weisbach — 2013-04-30T10:48:24

Am 30.04.2013 um 10:54 schrieb xantares 09:

It works, although I have to point CMake to the correct prefix of the library with -DCMAKE_PREFIX_PATH="/opt/local" (where MacPorts puts its stuff by default). Otherwise CMake uses the system library, which has the wrong architecture:
ld: warning: in /usr/local/lib/libintl.dylib, missing required architecture x86_64 in file.

A note for OS X users to use CMAKE_PREFIX_PATH in README.build when they have their libs elsewhere (i.e. use a packet manager) would be nice.

Best regards,
Hannes
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

RE: ftdi_eeprom link failure

xantares 09 — 2013-04-30T08:54:56

Here is a cleaner way ; detect libintl if separate from libc, could someone test this on osx:
https://gitorious.org/libftdi/libftdi/commit/8b860ed08731ae6ab639973735b376de3694a199

Regards,
M.



       

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

RE: ftdi_eeprom link failure

xantares 09 — 2013-04-30T08:19:14





Indeed, it does break the build on linux ; intl is shipped as part of libc6.
Intl should be treated as a conditional dependency of confuse.

Here is a patch.

Regards.

M.




       

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

ftdi_eeprom link failure

Hannes Weisbach — 2013-04-27T15:41:53

Hello libftdi-developers.

I wanted to compile libftdi1 under OS X 10.6.8 and I followed README.build to do so. However, ftdi_eeprom failed to link with the following error:
Linking C executable ftdi_eeprom
Undefined symbols:
  "_libintl_setlocale", referenced from:
      _cfg_init in libconfuse.a(confuse.o)
      _cfg_init in libconfuse.a(confuse.o)
  "_libintl_bindtextdomain", referenced from:
      _cfg_init in libconfuse.a(confuse.o)
  "_libintl_dgettext", referenced from:
      _cfg_include in libconfuse.a(confuse.o)
      _cfg_getopt in libconfuse.a(confuse.o)
      _cfg_getopt in libconfuse.a(confuse.o)
      _cfg_setopt in libconfuse.a(confuse.o)
      _cfg_setopt in libconfuse.a(confuse.o)
      _cfg_parse_internal in libconfuse.a(confuse.o)
      _cfg_parse_internal in libconfuse.a(confuse.o)

A bit of research suggested, that "-lintl" may be missing from the linker flags. So I added it and everything compiled and linked fine. I added the library to ftdi_eeprom/CMakeList.txt (see attached patch).

Re: Re: libftdi patches : [Patch 5/5] : Adding partial support for FT230X

Thomas Jarosch — 2013-04-26T12:43:45

Hi Uwe,

On Thursday, 11. April 2013 10:36:33 Uwe Bonnes wrote:

since you are more familiar with the eeprom code than myself,
do you see a problem with the new code? For me it looks ok,
though I don't have a device handy to test it.

Thomas


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: read/write timeout in C++ wrapper

Thomas Jarosch — 2013-04-26T12:42:35

Hi Jochen,

On Monday, 22. April 2013 12:27:36 Jochen Sprickerhof wrote:

thanks, applied! I've also made the get_xxx() functions const.

Cheers,
Thomas


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: API changes between 0.xx and 1.0?

Thomas Jarosch — 2013-04-26T12:39:26

Hi Chris,

On Tuesday, 23. April 2013 09:30:48 Chris Morgan wrote:

API changes are minimal. If you don't use the old, hackish async
mode interface (which you had to enable during compile time),
upgrading should be smooth.

Thomas


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: [PATCH] Typo in error message of ftdi_write_eeprom_location.

Thomas Jarosch — 2013-04-26T12:36:27

Hi Matthias,

On Tuesday, 16. April 2013 10:33:49 Matthias Brugger wrote:

somehow the patch didn't apply.

Nonetheless I've fixed this bug in several places now
and gave credit to you in the commit message.

Thanks,
Thomas


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: FT2232H shows up like FT4232H

Newell Jensen — 2013-04-24T16:33:30

Matthias,

Thanks for letting me know.  I will take a look into it.

Cheers,

Newell




--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: FT2232H shows up like FT4232H

Matthias Brugger — 2013-04-24T14:43:48

2013/4/23 Newell Jensen <newell.jensen< at >gmail.com>:

FTDI customer service worte me this message. It din't helped me, but
maybe it will help you:
"If the FT2232H appears as an FT4232H, it means that the VCCIO pins
are not all powered correctly. Please check your connections and
ensure that all VCCIO pins are powered. It is not sufficient to power
only some of them."

Cheers,
Matthias






--
motzblog.wordpress.com

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: FT2232H shows up like FT4232H

Newell Jensen — 2013-04-23T16:53:11

I just joined the mailing list and the email below has gone
unanswered.  I am also faced with this problem but I get this issue
intermittently.  That is, sometimes when I plug in the FT2232H mini
module, it sometimes comes up as FT2232H and other times it comes up
as FT4232H (he mentions FT4323H but mine comes up as FT4232H). When I
run:


$ lsusb -v


and take a look at the output I see distinct differences when it comes
up as FT2232H vs. FT4232H (obviously).  Has anyone else ran into this
issue before?  I can easily reproduce this.  I mean I guess I could
keep plugging and unplugging my mini module until it shows up as
FT2232H but this seems like something buggy to begin with that I would
like to wrap my head around.


Thanks.

********************************************************************

Hello all,

I have problem with my FT2232H chip:
I want to use it to communicate via sync FIFO. As the data sheet
suggests you have to reprogram the eeprom, but when using the tool
from libftdi I found that the ch

API changes between 0.xx and 1.0?

Chris Morgan — 2013-04-23T13:30:48

Hi.

I was wondering if there were any api changes between 0.xx and 1.0?
I'm starting to look at using libftdi and wasn't sure if I could start
using my distributions built in version of 0.19 and then seamlessly
upgrade to 1.0 or if I should start at the 1.0 version to avoid api
differences.

Chris

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

read/write timeout in C++ wrapper

Jochen Sprickerhof — 2013-04-22T10:27:36

Hi,

the C++ wrapper has no function to set the read/write timouts of the
ftdi_context. The attached patch fixes this. Would be great to have you
could merge it upstream.

Cheers Jochen


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: Why can not set DTR and RTS?

linux fddl — 2013-04-19T02:58:56

Addition, my libftdi is libftdi 0.17 and 0.19

2013/4/19 linux fddl <fddllinux< at >gmail.com>:

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: Why can not set DTR and RTS?

linux fddl — 2013-04-19T01:35:26

Thanks for your answer.


  In fact, I just try to set RTS and DTR high/low. It's just a test
code, [return f] just because I want to know whether there is any
error, hope to simplify my debug. I'm so sorry... This may wast your
time. Really sorry...
The really problem is I can not set RTS and DTR.


  The following code is a reducing one.


There is no error output from console.
Also the output is not what I want. For example, if I hope a
high/low/high/low level,
I can not see this from my board's pins.
But, but if I write datas, I can see the output from TX, though I'm
not sure whether it is right,
I think it's not the key.

I calls ftdi_set_bitmode() twice, but even calls any one of them,
still not work. I also tried to
call none of them, but ...

Other things I want to know is:
Do I need to config my chip(FTDI 232RL) with FT_Prog? For example, IO?
Or, should I use cbus?

-----------------------------------------------------------------------------------------------------------------------

#include <stdi

ftdi_convert_baudrate()

peter holly — 2013-04-18T19:16:55

Hi,
I have tried libftdi with 2 port FT2232C chip. Only problem I found was
that the ftdi_set_baudrate() function did not work with second port. The
port allways operated on highest baudrate. Looking closer on
ftdi_convert_baudrate() i found out that the ftdi->index is aplied only on
high speed devices. I have modified the code like this and it works fine.
Is that ok ?

if (ftdi->type == TYPE_2232H ||
        ftdi->type == TYPE_4232H ||
        ftdi->type == TYPE_232H )
    {
        *index = (unsigned short)(encoded_divisor >> 8);
    }
    else
    {
        *index = (unsigned short)(encoded_divisor >> 16);
    }
    *index &= 0xFF00;
    *index |= ftdi->index;

Best regards,
Peter Holly


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe< at >developer.intra2net.com

Re: Why can not set DTR and RTS?

Matthias Janke — 2013-04-18T10:28:50

Hm, ok I use ftdi_setflowctrl and it works for me. Just having a quick glance at
your code reveals the following line:

if (f = ftdi_setrts(ftdi, SIO_SET_DTR_HIGH))
return f;

which immediately returns after setting RTS high not touching DTR as the
following lines of that function suggests. (the assignment did work -> true) You
probably meant something like 

if ((f = ftdi_setrts(ftdi, SIO_SET_DTR_HIGH))!=0)
return f;

but that is just guessing. Reducing your code to the bare minimum, no option
parsing, no error handling, no DBG might help to reveal the cause of your problem.
But since you do error handling etc. , could you be a bit more verbose on the
actual result of your program? (console output, return values, expected output,
pin state on your board, ...) 

Cheers
Matthias 

Am Thu, 18 Apr 2013 16:54:14 +0800
schrieb linux fddl <fddllinux< at >gmail.com>: