ftdi-usb-sio-devel — FTDI USB Device Driver development discussion list

Re: [Ftdi-usb-sio-devel] FT832BM Hardware Handshaking

[Thomas J. <tho...@in...>]

David,

> I am suffering from a little problem with my hardware
> handshaking using the FT832BM.  The DTR and RTS lines work fine
> when only one is ON but when I turn the second one on the first
> turns off.  e.g. I toggle RTS to ON I then toggle DTR to ON and
> RTS is automatically changes to OFF.
>
> Does anyone have any ideas what is causing this?
>
> I am currently using a 2.4.20-2mdk Mandrake kernel.

I just took a look at the source. It's a bug in the driver:
It brute-force overwrites the modem control register of the FTDI chip.

Those two functions (set_rts()/set_dtr()) should be combined to one
or at least ftdi_sio should keep track of the status of the flags.
I could fix it for you on the weekend if you can't do it yourself.

Thomas

[Ftdi-usb-sio-devel] FT832BM Hardware Handshaking

[David A. <da...@ah...>]

Hello, 
 
I am suffering from a little problem with my hardware 
handshaking using the FT832BM.  The DTR and RTS lines work fine 
when only one is ON but when I turn the second one on the first 
turns off.  e.g. I toggle RTS to ON I then toggle DTR to ON and 
RTS is automatically changes to OFF.   
 
Does anyone have any ideas what is causing this? 
 
I am currently using a 2.4.20-2mdk Mandrake kernel. 
 
 
Thank You, 
 
David Aitken  
           

Re: [Ftdi-usb-sio-devel] IBM R32' usb to a serial problem

[Wayne W. <wa...@co...>]

On Wed, 12 Feb 2003 10:33:31 -0000, Anna_NEXTECHS wrote:

>When I execute a minicom,  it shows messages..
># minicom
>** Parameter bits is public, but is marked prvate in global config file
>** Parameter parity is public, but is marked private in global config file
>** Parameter stopbits is public, but is marked private in global config file
>Device /dev/ttyUSB0 lock failed: Operation not permitted.
>#

minicom does work on RedHat, but what I would recommend is that you
create a new configuration just for USB0.  As superuser, invoke minicom -s
specify the port /dev/ttyUSB0 and the speed and hardware settings, and save 
the configuration as "usb0".  Then you can invoke it as "minicom usb0".

Also, make sure /dev/ttyUSB0 is chmod666 if you plan on running it as an
ordinary user.

Wayne

Re: [Ftdi-usb-sio-devel] IBM R32' usb to a serial problem

[Ian A. <ab...@me...>]

On Wed, 12 Feb 2003 10:33:31 -0000, Anna_NEXTECHS wrote:

>When I execute a minicom,  it shows messages..
># minicom
>** Parameter bits is public, but is marked prvate in global config file
>** Parameter parity is public, but is marked private in global config file
>** Parameter stopbits is public, but is marked private in global config file

Those look like you need to change minicom's global config file (should
be /etc/minicom.dfl in this case, as you haven't specified a port on the
command line).  You could try editing it manually and changing the
"pr"(ivate)s to "pu"(blic)s for those three lines.  Or delete the file
and run minicom -s again to recreate it.

>Device /dev/ttyUSB0 lock failed: Operation not permitted.
>#

The last time I attempted to get minicom to work on a Redhat system (7.3
I think) I failed to get it to work for any user except root, even after
setting the SUID bit.  Redhat patch minicom to use their own tty lock
library rather than the usual UUCP lock files.  You could try ditching
Redhat's version of minicom and building a version without Redhat's
patches.

Re: [Ftdi-usb-sio-devel] IBM R32' usb to a serial problem

[Thomas J. <tho...@in...>]

> I copied two fils from the gz file to /usr/src/linux-2.4.7-10/drivers/usb/serial.
> Then I compiled a kernel and modules. (I use a Redhat 8.0)

Are you sure you're using Redhat 8.0? 
Redhat 8.0 comes with kernel 2.4.18 by default,
your directory location shows kernel 2.4.7.

You should try kernel 2.4.20 for best results with ftdi_sio.

Thomas

Re: [Ftdi-usb-sio-devel] ftdi_sio data rate

[Thomas J. <tho...@in...>]

> I am using DLP-USB245M USB adapter  wich uses ftdi_sio  driver with Redhat
> Linux 2.4-18, Everything works fine with low data rates. But if my device
> starts sending data at 40KB/sec rate it seems that I start to loose some
> data. I also tested my setup on Windows 2000 and it seems that it works
> fine there. Can you please give me a hint if you can why it might be
> happenning? 
 
 My prototype for a project using a FT245BM arrived today.
I can confirm the data loss even at low data rates :-(
 
 It works perfectly under Windows, but the last byte seems lost
if transferred via linux (kernel 2.4.20).
 
 I'll investigate this one.
 
 Thomas

[Ftdi-usb-sio-devel] IBM R32' usb to a serial problem

[Anna_NEXTECHS <an...@ne...>]

SGVsbG8sDQoNCkkgaGF2ZSBhIElCTSBSMzIgbm90ZWJvb2sgd2l0aCBhIFVTQiBwb3J0LCB3aGlj
aCBtaWdodCBiZSBhIFVTQjEuMC4gDQpJIG5lZWQgdG8gdXNlIGEgbWluaWNvbSwNCnNvIEkgZG93
bmxvYWRlZCBmdGRpX3Npby0xLjIuMXRhci5neiBmcm9tIHlvdXIgc2l0ZS4NCkkgY29waWVkIHR3
byBmaWxzIGZyb20gdGhlIGd6IGZpbGUgdG8gL3Vzci9zcmMvbGludXgtMi40LjctMTAvZHJpdmVy
cy91c2Ivc2VyaWFsLg0KVGhlbiBJIGNvbXBpbGVkIGEga2VybmVsIGFuZCBtb2R1bGVzLiAoSSB1
c2UgYSBSZWRoYXQgOC4wKQ0KDQpBZnRlciByZWJvdGluZyB3aXRoIG5ldyBrZXJuZWwsIEkgdHJp
ZWQgdG8gdXNlIGEgbWluaWNvbS4NCkkgY29uZmlndXJlZCBhIG1pbmljb20gd2l0aCBiYXVkcmF0
ZSA5NjAwIGFuZCAvZGV2L3R0eVVTQjAuDQpXaGVuIEkgZXhlY3V0ZSBhIG1pbmljb20sICBpdCBz
aG93cyBtZXNzYWdlcy4uDQojIG1pbmljb20NCioqIFBhcmFtZXRlciBiaXRzIGlzIHB1YmxpYywg
YnV0IGlzIG1hcmtlZCBwcnZhdGUgaW4gZ2xvYmFsIGNvbmZpZyBmaWxlDQoqKiBQYXJhbWV0ZXIg
cGFyaXR5IGlzIHB1YmxpYywgYnV0IGlzIG1hcmtlZCBwcml2YXRlIGluIGdsb2JhbCBjb25maWcg
ZmlsZQ0KKiogUGFyYW1ldGVyIHN0b3BiaXRzIGlzIHB1YmxpYywgYnV0IGlzIG1hcmtlZCBwcml2
YXRlIGluIGdsb2JhbCBjb25maWcgZmlsZQ0KRGV2aWNlIC9kZXYvdHR5VVNCMCBsb2NrIGZhaWxl
ZDogT3BlcmF0aW9uIG5vdCBwZXJtaXR0ZWQuDQojDQoNCkNvdWxkIHlvdSBoZWxwIG1lPw0KSSdt
IGFmcmFpZCB0aGF0IGl0IGlzIG5vdCBlbm91Z2ggaW5mb3JtYXRpb24uDQoNCg0KQmVzdCBSZWdh
cmRzLA0KQW5uYQ0K

Re: [Ftdi-usb-sio-devel] CrystalFontz Devices

[Wayne W. <wa...@co...>]

The latest nightly build of LCDproc has a switch to allow the USB to work by
expressly removing O_NDELAY in the open().  To use it, specify USB=yes in the
CFontz section of the LCDd.conf configuration file.

This is about the extent of support for the 0.4.4 series of LCDproc, because
it will be frozen very soon.  I will be adding this is 0.5, and in 0.5 the
whole I/O subsystem will be addressed.  There's been lots of discussions
in the LCDproc mailing list based around how serial should be performed.

By the way, the Matrix Orbital driver of LCDproc also has O_NDELAY removed, 
and this has not shown to be a problem.  Their USb displays also use the
ftdi_sio driver.

Wayne

Re: [Ftdi-usb-sio-devel] CrystalFontz Devices

[Tom W. <tom...@bi...>]

Bill,

Thanks for looking into this.  I'll give the changes to 
lcd4linux and LCDproc a try.  I'm a little concerned about
the possability of a hang if the device isn't on-line.
Will need to play with the hardware and see what scenarios
would cause grief.

It is strange that the CF serial units with the v2.0 firmware
support 19.2kbitp/s but I haven't been seeing complaints about 
lcd4linux or LCDproc.  This is what originally lead me to
belive that it was a driver problem.

With the ability to pass modified vendor and product IDs being
a feature of the FTDI, I'm guessing that this and the OM displays
are just the start of a long list that are going to need to be
added to the driver for recognition.  If there is any information
that you want, beyond the IDs, you might want to note that in
driver README.  Hopefully, it might save some headaches.

Thanks again,

Tom
--
tom...@bi...
... Remaining time multiplied by distress is constant.

On Sun, Feb 09, 2003 at 11:01:56PM +1300, Bill Ryder wrote:
> 
> Hi there,
> 
> Crystal Fontz have sent me a 632 and 634 which I have working now.
> 
> The fix for the lcd4linux problem is to change the open call in the 
> CrystalFontz.c driver to read:
> 
>     fd=open(Port,O_RDWR|O_NOCTTY);
> 
> instead of
>     fd=open(Port,O_RDWR|O_NOCTTY|O_NDELAY);
> 
> There's an identical problem in LCDproc as well.
> 
> In theory if O_NDELAY is being used the application MUST check the 
> return code of write(2) and resend the data if it errors with an EGAIN 
> error. The code is not doing that.
> 
> Turning off O_NDELAY means this is not necessary (but there are other 
> side effects - like the open will hang until the device is online).
> 
> 
> 
> 
> 
> 
> Tom Webster wrote:
> 
> >Hi Bill,
> >
> >As long as the subject of additional devices has come up, you might
> >want to also add the CrystalFontz USB displays.  They are based on the
> >FT8U232AM (0x0403:0x6001) but have custom product ID's added:
> >
> >0x0403:0xFC08 is a 632 (16x2 Display)
> >0x0403:0xFC09 is a 634 (20x4 Display)
> >
> >I'm currently using the 1.2.1 driver in the kernel source tree along
> >with the 2.4.20 kernel.  It might be nice to add a comment indicating
> >that the 1.2.1 driver won't work with older kernels -- it would have
> >saved me a couple of days fighting with the 2.4.18 kernel.
> >
> >After angling the driver to accept the product code for my 632, I'm able
> >to talk to the display using Minicom (19.2k 8N1) and all seems fine.
> >
> >The latest version of lcd4linux will draw bars (offset and a little
> >mangled -- but it will draw them), but generally refuses to write text to
> >the display (this would seem to be the easy part). Mailing list traffic
> >indicates that there are known problems with the v2.0 firmware behaving
> >in an odd fashion. One person claims lcd4linux works right on his serial
> >634 (w/ 2.0FW) about 1 in 20 times.
> >
> >The latest version of LCDProc (and last night's CVS snapshot) thinks
> >it's running fine, but does nothing with the display.
> >
> >Not sure if this is an issue with the display programs or the driver
> >at this point.  It is a little odd that neither of the utility programs
> >works.
> >
> >The CF tech support person on their forums also indicated they had an
> >e-mail in to you regarding an offer of equipment to help resolve any
> >issues with the driver and their displays.  If you haven't seen it,
> >please let me know and I'll ping them again.
> >
> >Best regards,
> >
> >Tom
> >--
> >tom dot webster at bigfoot dot com
> >... Three things are certain: Death, taxes, and lost data. Guess which has
> >    occurred...
> >
> >
> >-------------------------------------------------------
> >This SF.NET email is sponsored by:
> >SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> >http://www.vasoftware.com
> >_______________________________________________
> >Ftdi-usb-sio-devel mailing list
> >Ftd...@li...
> >https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
> >
> >
> >  
> >
> 

Re: Re: [Ftdi-usb-sio-devel] Using Dlink DMI-128 ESU modem

[listuser <lis...@my...>]

> Make sure you get kernel 2.4.20 which includes 
> version  1.2.1 of the ftdi_sio driver.


Ok, I will upgrade the kernel and see.

Thanks

raj

Re: [Ftdi-usb-sio-devel] Using Dlink DMI-128 ESU modem

[Thomas J. <tho...@in...>]

> But when I tried setserial on /dev/(usb/)ttyUSB0 it  is not giving any details.
> Is there any thing I am missing here?

Depends on which version of the driver you are using.
The interface for setserial etc. wasn't in the version included with kernel 2.4.18.

Make sure you get kernel 2.4.20 which includes version 1.2.1 of the ftdi_sio driver.

> Can I use /dev/(usb/)ttyUSB0 in the same way as /dev/ttyS0? 

Theoretically yes.

Thomas

[Ftdi-usb-sio-devel] Using Dlink DMI-128 ESU modem

[listuser <lis...@my...>]

Hello all,

I have a Dlink DMI-128 ESU ISDN modem, with both serial and usb interfaces.=
 When I plugged in the usb interface linux  detected the 8U232AM USB <-> =
Serial interface and loded the moduels. The  /proc/bus/usb/devices also l=
ists the device. But when I tried setserial on /dev/(usb/)ttyUSB0 it  is =
not giving any details. Is there any thing I am missing here? Can I use /=
dev/(usb/)ttyUSB0 in the same way as /dev/ttyS0? Any one here tried makin=
g a dialin server using a usb ISDN modem?

Thanks in advance,

raj

Re: [Ftdi-usb-sio-devel] CrystalFontz Devices

[Bill R. <br...@pa...>]

Hi there,

Crystal Fontz have sent me a 632 and 634 which I have working now.

The fix for the lcd4linux problem is to change the open call in the 
CrystalFontz.c driver to read:

    fd=open(Port,O_RDWR|O_NOCTTY);

instead of
    fd=open(Port,O_RDWR|O_NOCTTY|O_NDELAY);

There's an identical problem in LCDproc as well.

In theory if O_NDELAY is being used the application MUST check the 
return code of write(2) and resend the data if it errors with an EGAIN 
error. The code is not doing that.

Turning off O_NDELAY means this is not necessary (but there are other 
side effects - like the open will hang until the device is online).






Tom Webster wrote:

>Hi Bill,
>
>As long as the subject of additional devices has come up, you might
>want to also add the CrystalFontz USB displays.  They are based on the
>FT8U232AM (0x0403:0x6001) but have custom product ID's added:
>
>0x0403:0xFC08 is a 632 (16x2 Display)
>0x0403:0xFC09 is a 634 (20x4 Display)
>
>I'm currently using the 1.2.1 driver in the kernel source tree along
>with the 2.4.20 kernel.  It might be nice to add a comment indicating
>that the 1.2.1 driver won't work with older kernels -- it would have
>saved me a couple of days fighting with the 2.4.18 kernel.
>
>After angling the driver to accept the product code for my 632, I'm able
>to talk to the display using Minicom (19.2k 8N1) and all seems fine.
>
>The latest version of lcd4linux will draw bars (offset and a little
>mangled -- but it will draw them), but generally refuses to write text to
>the display (this would seem to be the easy part). Mailing list traffic
>indicates that there are known problems with the v2.0 firmware behaving
>in an odd fashion. One person claims lcd4linux works right on his serial
>634 (w/ 2.0FW) about 1 in 20 times.
>
>The latest version of LCDProc (and last night's CVS snapshot) thinks
>it's running fine, but does nothing with the display.
>
>Not sure if this is an issue with the display programs or the driver
>at this point.  It is a little odd that neither of the utility programs
>works.
>
>The CF tech support person on their forums also indicated they had an
>e-mail in to you regarding an offer of equipment to help resolve any
>issues with the driver and their displays.  If you haven't seen it,
>please let me know and I'll ping them again.
>
>Best regards,
>
>Tom
>--
>tom dot webster at bigfoot dot com
>... Three things are certain: Death, taxes, and lost data. Guess which has
>    occurred...
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by:
>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>http://www.vasoftware.com
>_______________________________________________
>Ftdi-usb-sio-devel mailing list
>Ftd...@li...
>https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>
>
>  
>

Re: [Ftdi-usb-sio-devel] ft232bm

[Bill R. <br...@pa...>]

HI there,

Apparently the current driver works best with 2.4.20 and above.

There are problems using it with the 2.4.18 kernel.

Personally I only use 2.4.20 and above (currently using a mandrake 
2.4.21-pre4 kernel) for testing.

I never look at anything less than 2.4.20 due to my laptop requirements 
so anyone going there is possibly in for a world of pain.

I'm seeing some interesting issues with driver and some applications. I 
have just discovered for example that talking to the driver in O_NDELAY 
mode may cause problems if an application isn't checking for errors from 
write(2) calls. If a packet is in flight to the device it will return 
EINPROGRESS at a driver level which returns EAGAIN (which means try the 
call again). The Crystal Fontz driver in the 0.4.3 version of LCDproc 
does absolutely no error checking on write and so a LOT of packets are 
being thrown away. If the write call was checked the error could be 
handled in the app.

The easy fix for this is to open the device in a blocking mode which 
means all data should get through. (You just take the O_NDELAY flag out 
of the open call). If O_NDELAY is being used though the app should be 
checking for errors from writes so it can retry.

This also explains why the throughput through the device is o slow for 
some programs. Anything which makes  lots of small write calls will not 
be fast at all because they will keep having to wait for an inflight packet.

The fix is an urb pool for writing which I am working on how. (These 
cool displays from CrystalFontz are a great incentive :-). (I'm also 
incorporating other patches from other people which have been sitting in 
a queue for a while now - sorry about that.)







guido socher wrote:

>Hello,
>I designed a LCD display with the FT232BM (the new version from
>ftdi) and an AVR uC. 
>To my big surprise the whole thing worked right away with
>a standard  redhat 7.3 kernel (2.4.18). Very good, big thanks
>to all involved in the driver development!
>I have been following this list for a while and there seemed
>to be problems with some kernel versions. Can anybody
>summarize which versions have problems with the FT232BM (just the
>normal serial interface)?
>The plan is the write an article about the FT232BM and the usb
>lcd display in linuxfocus and it would be good to warn the readers
>about problems if there are any with respective kernel/driver versions.
>
>Thanks for your help
>
>Regards
> Guido
>
>  
>

Re: [Ftdi-usb-sio-devel] ftdi_sio data rate

[Thomas J. <tho...@in...>]

Krishnan,

> How are you able to send even 40KB? The spec says 3000 baud (in the virtual
> com
> port mode) - and I am seeing only that much. I am using 245BM.

The datasheet of the chip specifies up to 1M Byte / Sec as hardware limit.
The linux driver should not be affected by the 3.000 baud limit.
IIRC the D2XX doesn't suffer from the 3.000 baud limit, too.

Thomas

Fw: [Ftdi-usb-sio-devel] ftdi_sio data rate

[Thomas J. <tho...@in...>]

FYI

----- Original Message -----
From: "Sreekrishnan Venkateswaran" <sre...@us...>
To: "Thomas Jarosch" <tho...@in...>
Sent: Saturday, February 08, 2003 2:02 AM
Subject: Re: [Ftdi-usb-sio-devel] ftdi_sio data rate


>
>
>
>
> Hi,
>
> How are you able to send even 40KB? The spec says 3000 baud (in the virtual
> com
> port mode) - and I am seeing only that much. I am using 245BM.
>
> Regards,
> krishnan
>
>
>
>
>                       Thomas Jarosch
>                       <tho...@in...>             To:
ftd...@li...
>                       Sent by:                                   cc:
>                       ftd...@li...ur        Subject:  Re:
[Ftdi-usb-sio-devel] ftdi_sio data rate
>                       ceforge.net
>
>
>                       02/07/2003 06:47 PM
>
>
>
>
>
>
> > I am using DLP-USB245M USB adapter  wich uses ftdi_sio  driver with
> Redhat
> > Linux 2.4-18, Everything works fine with low data rates. But if my device
> > starts sending data at 40KB/sec rate it seems that I start to loose some
> > data. I also tested my setup on Windows 2000 and it seems that it works
> > fine there. Can you please give me a hint if you can why it might be
> > happenning?
>
> Have you tried using high data rates under Windows
> or did you just connect it?
>
> What kind of device is connected to the chip to strobe
> the RXF and RD# lines? Is it fast enough to handle
> the same amount of data when sending under Windows?
>
> Upgrading to kernel 2.4.20 might be worth a try
> as I contains the newest version of the ftdi_sio driver
> and I guess there were also some changes in the USB subsystem.
>
> > Do you think it is a problem with ftdi_sio driver or
> > usbserial? or maybe usbcore?
>
> IMHO it could only be a problem of the ftdi_sio driver
> as other bugs would have been found by a lot more people
> using high speed usb serial converters.
>
> Cheers,
> Thomas
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld  Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
>  https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>
>
>

[Ftdi-usb-sio-devel] >>>Last Chance...OVER 15.3 MILLION EMAIL ADDRESSES...PLUS $2,000 IN FREE SOFTWARE!

[lexandra <Inc...@ya...>]

WOULD YOU LIKE TO HAVE YOUR MESSAGE SEEN BY 
OVER 15.3 MILLION OPT-IN, TARGETED PROSPECTS DAILY?

Below contains all the information you will ever need to market 
your product or service on the Internet.

If you have a product, service, or message that you would like to get 
out to Thousands, Hundreds of Thousands, or even Millions of people, 
you have several options. Traditional methods include print advertising,
direct mail, radio, and television advertising. They are all effective, but 
they all have two catches: They're EXPENSIVE and TIME 
CONSUMING. Not only that, you only get ONE SHOT at making 
your message heard by the right people. Also, Internet Search Engine 
Submissions, Classified Ads, Newsgroup Postings simply DO NOT 
WORK effectively.

Now this has all changed!

Thanks to the top programmers in the world and their NEW EMAIL
TECHNOLOGY, You can send millions of email messages daily for 
FREE...Without getting terminated from your current Internet connection!

It's very simple to do and you can be increasing your sales within minutes 
of installing this new extraordinary software!

Besides...It's the only real way to advertise on the Internet that works...Period!

>>>WE WILL SUPPLY YOU WITH OVER 15.3 MILLION OPT-IN EMAIL 
ADDRESSES TO GET YOU STARTED RIGHT AWAY!

>>>PLUS FREE EMAIL ADDRESS DOWNLOADS FOR LIFE!

>>>ALSO, YOU WILL RECEIVE $2,000 WORTH OF EMAIL 
MARKETING SOFTWARE FREE!

Including......

BROADCAST EMAIL SENDING SOFTWARE...(send millions of email 
advertisements daily with a few clicks of your mouse, without getting 
your ISP trerminated. We used the same software to send you this email)

EMAIL EXTRACTION SOFTWARE...(retrieve new targeted email 
addresses daily. Hundreds of thousands of them)

LIST MANAGEMENT SOFTWARE...(keep your lists clean, opt-in 
and manage all your remove requests, leads, sales etc...)
 
and much...much more!

Hurry...This extraordinary offer ends soon!

To find out more information, Do not respond by email. Instead, click 
on the link below or copy and paste the exact web site address below 
into your Internet browser. 

http://www.vvorldvvideventures.com/504305/addresses.htm




______________________________________________________
Want to be removed from our email list?
You were sent this email because you used our Opt-in service.
We hope you enjoy reading our messages. However, if you'd rather 
not receive future e-mails from us, Click on the link below
http://www.vvorldvvideventures.com/504305/remove.htm 
Thank you for your cooperation
_______________________________________________________

Re: [Ftdi-usb-sio-devel] ftdi_sio data rate

[Thomas J. <tho...@in...>]

> I am using DLP-USB245M USB adapter  wich uses ftdi_sio  driver with Red=
hat
> Linux 2.4-18, Everything works fine with low data rates. But if my devi=
ce
> starts sending data at 40KB/sec rate it seems that I start to loose som=
e
> data. I also tested my setup on Windows 2000 and it seems that it works
> fine there. Can you please give me a hint if you can why it might be
> happenning?=20

Have you tried using high data rates under Windows
or did you just connect it?

What kind of device is connected to the chip to strobe
the RXF and RD# lines? Is it fast enough to handle
the same amount of data when sending under Windows?

Upgrading to kernel 2.4.20 might be worth a try
as I contains the newest version of the ftdi_sio driver
and I guess there were also some changes in the USB subsystem.

> Do you think it is a problem with ftdi_sio driver or=20
> usbserial? or maybe usbcore?

IMHO it could only be a problem of the ftdi_sio driver
as other bugs would have been found by a lot more people
using high speed usb serial converters.

Cheers,
Thomas

[Ftdi-usb-sio-devel] ftdi_sio data rate

[Ilya L. <il...@mo...>]

I am using DLP-USB245M USB adapter  wich uses ftdi_sio  driver with =
Redhat Linux 2.4-18,
Everything works fine with low data rates. But if my device starts =
sending data at 40KB/sec rate it seems that I start to loose some data. =
I also tested my setup on Windows 2000 and it seems that it works fine =
there.
Can you please give me a hint if you can why it might be happenning?  Do =
you think it is a problem with ftdi_sio driver or  usbserial? or maybe =
usbcore?

[Ftdi-usb-sio-devel] New features soon: BitBang and eeprom

[Thomas J. <tho...@in...>]

Hi all!

My ftdi_sio driver extensions have left alpha state.
They include the following:

- Enabling Bit Bang mode
- Reading the pins directly
- Reading the eeprom
- Writing the eeprom (with automatic checksum generation)
- Erasing the eeprom

The patch will be released as soon as the
code is clean enough (f.e. currently the 128 bytes for
the eeprom are passed via copy to the ioctl(). Not good...)
I think I'll be finished on the weekend.

I'll start working on an eeprom editor now which
will be included in the final release of the patch.
And also some example code on how to use the bit bang mode :-)

Cheers,
Thomas

Re: [Ftdi-usb-sio-devel] 245 BM baud rates

[Ian A. <ab...@me...>]

On Mon, 3 Feb 2003 17:40:29 -0000, Sreekrishnan Venkateswaran wrote:

>Does anyone know why the 245BM supports only a low 3000 baud while the 232BM supports
>1 Mbps?

I don't know.  The FT245BM datasheet mentions 3000 baud for the VCP
drivers and 1 MByte/sec (8 Mbits/sec) for the D2XX drivers.  It sounds a
bit strange.  I know the 245BM ignores the baud rate divisor, but
perhaps the VCP drivers use the baud rate as a throttle?  Or it could be
a typo.  (The VCP drivers and D2XX drivers are for Windows of course.)

>Where can I read documentation from FTDI that lists the various control URB
>commands for these chips that has been used in ftdi_sio.c (couldn't find that in their website).

The information is not in the datasheets.  You have to sign an NDA to
get the information - or just glean what you can from the Linux driver
sources (but this doesn't cover all the functions of the device, e.g.
reading/writing the serial EEPROM).

>What exactly is the difference between the D2XX interface and the COM interface? Again
>where is the documentation about the direct interface so that we could write a linux driver
>using that (and maybe a tty interface that is wrapped over this - this seems the right way
>for the 245BM since the serial settings are irrelavant anyway).

The VCP driver presents a Windows COMM interface and the D2XX driver and
DLL provide a different interface with more functions.  There is a
programmer's guide for the D2XX drivers and DLL at
<http://www.ftdichip.com/>, along with example code.  If you wanted to
implement something similar on Linux you'd need a bunch of custom ioctls
to implement the extra functions and a user-space library.

[Ftdi-usb-sio-devel] CrystalFontz Devices

[Tom W. <tom...@bi...>]

Hi Bill,

As long as the subject of additional devices has come up, you might
want to also add the CrystalFontz USB displays.  They are based on the
FT8U232AM (0x0403:0x6001) but have custom product ID's added:

0x0403:0xFC08 is a 632 (16x2 Display)
0x0403:0xFC09 is a 634 (20x4 Display)

I'm currently using the 1.2.1 driver in the kernel source tree along
with the 2.4.20 kernel.  It might be nice to add a comment indicating
that the 1.2.1 driver won't work with older kernels -- it would have
saved me a couple of days fighting with the 2.4.18 kernel.

After angling the driver to accept the product code for my 632, I'm able
to talk to the display using Minicom (19.2k 8N1) and all seems fine.

The latest version of lcd4linux will draw bars (offset and a little
mangled -- but it will draw them), but generally refuses to write text to
the display (this would seem to be the easy part). Mailing list traffic
indicates that there are known problems with the v2.0 firmware behaving
in an odd fashion. One person claims lcd4linux works right on his serial
634 (w/ 2.0FW) about 1 in 20 times.

The latest version of LCDProc (and last night's CVS snapshot) thinks
it's running fine, but does nothing with the display.

Not sure if this is an issue with the display programs or the driver
at this point.  It is a little odd that neither of the utility programs
works.

The CF tech support person on their forums also indicated they had an
e-mail in to you regarding an offer of equipment to help resolve any
issues with the driver and their displays.  If you haven't seen it,
please let me know and I'll ping them again.

Best regards,

Tom
--
tom dot webster at bigfoot dot com
... Three things are certain: Death, taxes, and lost data. Guess which has
    occurred...

[Ftdi-usb-sio-devel] 245 BM baud rates

[Sreekrishnan V. <sre...@us...>]

Hi,

Does anyone know why the 245BM supports only a low 3000 baud while the
232BM supports
1 Mbps? Where can I read documentation from FTDI that lists the various
control URB
commands for these chips that has been used in ftdi_sio.c (couldn't find
that in their website).

What exactly is the difference between the D2XX interface and the COM
interface? Again
where is the documentation about the direct interface so that we could
write a linux driver
using that (and maybe a tty interface that is wrapped over this - this
seems the right way
for the 245BM since the serial settings are irrelavant anyway).

Thanks!

Warm Regards,
krishnan

[Ftdi-usb-sio-devel] >>Last Chance...15.3 MILLION OPT-IN EMAIL ADDRESSES...PLUS $2,000 IN FREE EMAIL MARKETING SOFTWARE!

[Trelawiel<ema...@ya...>]

WOULD YOU LIKE TO HAVE YOUR MESSAGE SEEN BY 
OVER 15.3 MILLION OPT-IN, TARGETED PROSPECTS DAILY?

Below contains all the information you will ever need to market 
your product or service on the Internet.

If you have a product, service, or message that you would like to get 
out to Thousands, Hundreds of Thousands, or even Millions of people, 
you have several options. Traditional methods include print advertising,
direct mail, radio, and television advertising. They are all effective, but 
they all have two catches: They're EXPENSIVE and TIME 
CONSUMING. Not only that, you only get ONE SHOT at making 
your message heard by the right people. Also, Internet Search Engine 
Submissions, Classified Ads, Newsgroup Postings simply DO NOT 
WORK effectively.

Now this has all changed!

Thanks to the top programmers in the world and their NEW EMAIL
TECHNOLOGY, You can send millions of email messages daily for 
FREE...Without getting terminated from your current Internet connection!

It's very simple to do and you can be increasing your sales within minutes 
of installing this new extraordinary software!

Besides...It's the only real way to advertise on the Internet that works...Period!

>>>WE WILL SUPPLY YOU WITH OVER 15.3 MILLION OPT-IN EMAIL 
ADDRESSES TO GET YOU STARTED RIGHT AWAY!

>>>PLUS FREE EMAIL ADDRESS DOWNLOADS FOR LIFE!

>>>ALSO, YOU WILL RECEIVE $2,000 WORTH OF EMAIL 
MARKETING SOFTWARE FREE!

Including......

BROADCAST EMAIL SENDING SOFTWARE...(send millions of email 
advertisements daily with a few clicks of your mouse, without getting 
your ISP trerminated. We used the same software to send you this email)

EMAIL EXTRACTION SOFTWARE...(retrieve new targeted email 
addresses daily. Hundreds of thousands of them)

LIST MANAGEMENT SOFTWARE...(keep your lists clean, opt-in 
and manage all your remove requests, leads, sales etc...)
 
and much...much more!

Hurry...This extraordinary offer ends soon!

To find out more information, Do not respond by email. Instead, click 
on the link below or copy and paste the exact web site address below 
into your Internet browser. 

http://www.vvorldvvideventures.com/504305/addresses.htm




______________________________________________________
Want to be removed from our email list?
You were sent this email because you used our Opt-in service.
We hope you enjoy reading our messages. However, if you'd rather 
not receive future e-mails from us, Click on the link below
http://www.vvorldvvideventures.com/504305/remove.htm 
Thank you for your cooperation
_______________________________________________________

[Ftdi-usb-sio-devel] ft232bm

[guido s. <gu...@li...>]

Hello,
I designed a LCD display with the FT232BM (the new version from
ftdi) and an AVR uC. 
To my big surprise the whole thing worked right away with
a standard  redhat 7.3 kernel (2.4.18). Very good, big thanks
to all involved in the driver development!
I have been following this list for a while and there seemed
to be problems with some kernel versions. Can anybody
summarize which versions have problems with the FT232BM (just the
normal serial interface)?
The plan is the write an article about the FT232BM and the usb
lcd display in linuxfocus and it would be good to warn the readers
about problems if there are any with respective kernel/driver versions.

Thanks for your help

Regards
 Guido

-- 
The place for Linux documentation in your own language.
http://www.linuxfocus.org