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

Re: [Ftdi-usb-sio-devel] Linux thin client -> usb badge reader

[Thys M. <st...@gm...>]

you can un-compres the squashfs image, add the module (compiled for
your kernel version) and recompres. As long as you have a reasonably
close dev environment on another machine you should be able to pull it
off.
In short, I would:
- get a precompiled debian kernel of the same version than your image,
-  extract the ftdi module from it
- copy the image from the SD card to disk
- uncompress
- add the module
- fiddle with /etc/bashrc or similar in the image to load the module
with the VendorID/ProductID as previously noted
- squash
- copy the image back to the card
- test


On Mon, Jan 19, 2009 at 12:04 AM, Roeland Moors <ro...@mo...> wrote:
> It seems the module ftdi_sio is not on the system.
> The HP thin client uses a 64MB flash card with a debian live based
> image.
> It uses squashfs. /lib is read-only and no compile tools installed.
> Won't be easy to add it I'm afraid.
>
> The reader works fine on a normal (and newer) debian live image.
>
> On 17 Jan 2009, at 06:33, Thys Meintjes wrote:
>
>> I think your kernel may be to old for the following to work:
>> echo 0403 6001 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id, if so,
>> get the  ftdi_serial driver code, add the VendorID:Product id pair to
>> the header file,
>> recompile and modprobe as usual.
>>
>> Use lsusb -v,
>> udevmonitor (udevadm monitor --env)
>> udevinfo, etc. to investigate
>>
>> On Sat, Jan 17, 2009 at 1:11 AM, Roeland Moors <ro...@mo...>
>> wrote:
>>> I have a linux thin client where I would like to attach an usb badge
>>> reader.
>>> This badge reader should be available as a normal serial port.
>>>
>>> I have this in /proc/bus/usb/devices:
>>>
>>> T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
>>> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
>>> P:  Vendor=0403 ProdID=6001 Rev= 4.00
>>> S:  Manufacturer=FTDI
>>> S:  Product=USB <-> Serial
>>> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA
>>> I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>>> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
>>> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
>>>
>>> "Driver=(none)"
>>> Is there a kernel (2.6.15.7) module I need to load first?
>>>
>>> When removing and attaching the device I get this in dmesg
>>> usb 3-1: USB disconnect, address 3
>>> usb 3-1: new full speed USB device using uhci_hcd and address 4
>>>
>>> How to proceed? Any tips are welcome.
>>>
>>> Thanks,
>>>
>>> Roeland
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>> _______________________________________________
>>> Ftdi-usb-sio-devel mailing list
>>> Ftd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>>>
>>
>>
>>
>> --
>> Thys Meintjes
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>



-- 
Thys Meintjes

Re: [Ftdi-usb-sio-devel] Linux thin client -> usb badge reader

[Roeland M. <ro...@mo...>]

It seems the module ftdi_sio is not on the system.
The HP thin client uses a 64MB flash card with a debian live based  
image.
It uses squashfs. /lib is read-only and no compile tools installed.
Won't be easy to add it I'm afraid.

The reader works fine on a normal (and newer) debian live image.

On 17 Jan 2009, at 06:33, Thys Meintjes wrote:

> I think your kernel may be to old for the following to work:
> echo 0403 6001 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id, if so,
> get the  ftdi_serial driver code, add the VendorID:Product id pair to
> the header file,
> recompile and modprobe as usual.
>
> Use lsusb -v,
> udevmonitor (udevadm monitor --env)
> udevinfo, etc. to investigate
>
> On Sat, Jan 17, 2009 at 1:11 AM, Roeland Moors <ro...@mo...>  
> wrote:
>> I have a linux thin client where I would like to attach an usb badge
>> reader.
>> This badge reader should be available as a normal serial port.
>>
>> I have this in /proc/bus/usb/devices:
>>
>> T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
>> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
>> P:  Vendor=0403 ProdID=6001 Rev= 4.00
>> S:  Manufacturer=FTDI
>> S:  Product=USB <-> Serial
>> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA
>> I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
>> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
>>
>> "Driver=(none)"
>> Is there a kernel (2.6.15.7) module I need to load first?
>>
>> When removing and attaching the device I get this in dmesg
>> usb 3-1: USB disconnect, address 3
>> usb 3-1: new full speed USB device using uhci_hcd and address 4
>>
>> How to proceed? Any tips are welcome.
>>
>> Thanks,
>>
>> Roeland
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Ftdi-usb-sio-devel mailing list
>> Ftd...@li...
>> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>>
>
>
>
> -- 
> Thys Meintjes

Re: [Ftdi-usb-sio-devel] Linux thin client -> usb badge reader

[Thys M. <st...@gm...>]

I think your kernel may be to old for the following to work:
echo 0403 6001 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id, if so,
get the  ftdi_serial driver code, add the VendorID:Product id pair to
the header file,
recompile and modprobe as usual.

Use lsusb -v,
udevmonitor (udevadm monitor --env)
udevinfo, etc. to investigate

On Sat, Jan 17, 2009 at 1:11 AM, Roeland Moors <ro...@mo...> wrote:
> I have a linux thin client where I would like to attach an usb badge
> reader.
> This badge reader should be available as a normal serial port.
>
> I have this in /proc/bus/usb/devices:
>
> T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
> P:  Vendor=0403 ProdID=6001 Rev= 4.00
> S:  Manufacturer=FTDI
> S:  Product=USB <-> Serial
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA
> I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
>
> "Driver=(none)"
> Is there a kernel (2.6.15.7) module I need to load first?
>
> When removing and attaching the device I get this in dmesg
> usb 3-1: USB disconnect, address 3
> usb 3-1: new full speed USB device using uhci_hcd and address 4
>
> How to proceed? Any tips are welcome.
>
> Thanks,
>
> Roeland
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>



-- 
Thys Meintjes

[Ftdi-usb-sio-devel] Linux thin client -> usb badge reader

[Roeland M. <ro...@mo...>]

I have a linux thin client where I would like to attach an usb badge  
reader.
This badge reader should be available as a normal serial port.

I have this in /proc/bus/usb/devices:

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0403 ProdID=6001 Rev= 4.00
S:  Manufacturer=FTDI
S:  Product=USB <-> Serial
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 90mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms

"Driver=(none)"
Is there a kernel (2.6.15.7) module I need to load first?

When removing and attaching the device I get this in dmesg
usb 3-1: USB disconnect, address 3
usb 3-1: new full speed USB device using uhci_hcd and address 4

How to proceed? Any tips are welcome.

Thanks,

Roeland

[Ftdi-usb-sio-devel] new B&B 422 converter

[Thys M. <st...@gm...>]

Hi,

I've encountered a new B&B electronics device in the wild, it's a 422
converter Model 485USB9F-4W, and would like to report the product id
for inclusion in ftdi_sio.h.

I currently use the device using the /proc/ trick:
echo 0856 ac26 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id

Vendor ID (B&B) 0x0856
Product ID (485USB9F-4W)  0xac26


The B&B section may be expanded with the last  BANDB_USB9F_PID product ID

/*
 * Definitions for B&B Electronics products.
 */
#define BANDB_VID               0x0856  /* B&B Electronics Vendor ID */
#define BANDB_USOTL4_PID        0xAC01  /* USOTL4 Isolated RS-485 Converter */
#define BANDB_USTL4_PID         0xAC02  /* USTL4 RS-485 Converter */
#define BANDB_USO9ML2_PID       0xAC03  /* USO9ML2 Isolated RS-232 Converter */
#define BANDB_485USB9F_PID      0xAC26 /* 485USB9F-4W RS-422 Converter */


------------patch---------------
[thys@thys ftdi_sio]$ diff -c ftdi_sio.h ftdi_sio_patched.h
*** ftdi_sio.h  2008-12-01 16:50:18.000000000 +0200
--- ftdi_sio_patched.h  2009-01-15 15:25:04.000000000 +0200
***************
*** 360,365 ****
--- 360,366 ----
  #define BANDB_USOTL4_PID      0xAC01  /* USOTL4 Isolated RS-485 Converter */
  #define BANDB_USTL4_PID               0xAC02  /* USTL4 RS-485 Converter */
  #define BANDB_USO9ML2_PID     0xAC03  /* USO9ML2 Isolated RS-232 Converter */
+ #define BANDB_485USB9F_PID      0xAC26 /* 485USB9F-4W RS-422 Converter */

  /*
   * RM Michaelides CANview USB (http://www.rmcan.com)
------------patch---------------


Thanks and regards

-- 
Thys Meintjes

Re: [Ftdi-usb-sio-devel] Multiple serial ports on one adapter

[Toan P. <tph...@gm...>]

>From my study of the ftdi kernel driver recently, the ftdi driver
supports multiple ports.
Here is a confirmation of the ftdi driver cleaning up all the ports
upon disconnection.


static void destroy_serial(struct kref *kref)
{
	struct usb_serial *serial;
	struct usb_serial_port *port;
	int i;

	serial = to_usb_serial(kref);

	dbg("%s - %s", __FUNCTION__, serial->type->description);

	serial->type->shutdown(serial);

	/* return the minor range that this device had */
	return_serial(serial);

	for (i = 0; i < serial->num_ports; ++i)
		serial->port[i]->open_count = 0;

	/* the ports are cleaned up and released in port_release() */
	for (i = 0; i < serial->num_ports; ++i)
		if (serial->port[i]->dev.parent != NULL) {
			device_unregister(&serial->port[i]->dev);
			serial->port[i] = NULL;
		}

	/* If this is a "fake" port, we have to clean it up here, as it will
	 * not get cleaned up in port_release() as it was never registered with
	 * the driver core */
	if (serial->num_ports < serial->num_port_pointers) {
		for (i = serial->num_ports; i < serial->num_port_pointers; ++i) {
			port = serial->port[i];
			if (!port)
				continue;
			port_free(port);
		}
	}

	usb_put_dev(serial->dev);

	/* free up any memory that we allocated */
	kfree (serial);
}


On Wed, Jan 7, 2009 at 9:39 AM, Fred Labrosse <ff...@ab...> wrote:
> All,
>
> I need to have multiple RS422 ports on one computer and was looking at buying
> a USB/serial adapter with multiple (2) serial ports. My application is to
> plug two SICK laser scanners (lms200) into the computer.
>
> I have essentially two questions.
>
> The kernel driver help seems to say that it only supports single port adapters
> and I have seen at least one report on the archive of the mailing list saying
> that the driver didn't work with a multiple port adapter.  Is that indeed the
> case?
>
> Second, is there a specific adapter that I should look at?  The one at
> <http://www.easysync.co.uk/index.html?lang=en-uk&target=d11.html> seems
> interesting.  Anybody has any experience with it?  The vendors explicitly say
> that it works with linux (related to the question above).
>
> TIA,
>
> Fred
>
> ------------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>

[Ftdi-usb-sio-devel] Multiple serial ports on one adapter

[Fred L. <ff...@ab...>]

All,

I need to have multiple RS422 ports on one computer and was looking at buying 
a USB/serial adapter with multiple (2) serial ports. My application is to 
plug two SICK laser scanners (lms200) into the computer.

I have essentially two questions.

The kernel driver help seems to say that it only supports single port adapters 
and I have seen at least one report on the archive of the mailing list saying 
that the driver didn't work with a multiple port adapter.  Is that indeed the 
case?

Second, is there a specific adapter that I should look at?  The one at 
<http://www.easysync.co.uk/index.html?lang=en-uk&target=d11.html> seems 
interesting.  Anybody has any experience with it?  The vendors explicitly say 
that it works with linux (related to the question above).

TIA,

Fred

Re: [Ftdi-usb-sio-devel] Adding FTDI provided PID for product

[Ekki P. (DF4OR) <ep...@pl...>]

On Monday 01 December 2008, Andrew Ewert wrote:
> Hi all,
>
> I don't know if this is the right place to ask this (terribly sorry if it
> isn't), but my company is developing a USB-to-Serial device based on the
> FTDI-245R chipset and I was wondering what it would take to get our PID
> (Using FTDI VID) added to the supported list for FTDI_SIO for native Linux
> support. I guess I'm at a loss for where else I would ask this question.

I recently had the same issue. 
Subscribe to the linux-usb mailing list, ask there.

I got the instructions to submit a patch, as described 
in /usr/src/linux/Documentation/SubmittingPatches

Submit the patch to the linux-usb list (if it isn't too long) and to the lkml.

HTH,
Ekki

[Ftdi-usb-sio-devel] Adding FTDI provided PID for product

[Andrew E. <an...@ew...>]

Hi all,

I don't know if this is the right place to ask this (terribly sorry if it
isn't), but my company is developing a USB-to-Serial device based on the
FTDI-245R chipset and I was wondering what it would take to get our PID
(Using FTDI VID) added to the supported list for FTDI_SIO for native Linux
support. I guess I'm at a loss for where else I would ask this question.

I have the following information:

Product Name: CANdapter
Product Description: Low cost CANBUS to USB-Serial converter
Manufacturing Company: Ewert Energy Systems
VID: 0x0403  (FTDI)
PID: 0x9F80  (Obtained from FTDI specifically for CANdapter)

Again, my apologies if this was the wrong place to ask this question. Any
feedback would be greatly appreciated.

Thanks!
Andrew

-- 
Andrew Ewert
Lead Software Engineer, CANdapter Project (http://www.candapter.com)
Lead Software Engineer, FreeBMS Battery Management System (
http://code.google.com/p/freebms)
Lead Software Engineer, CANTOP PHEV Display (http://cantop.sf.net)
Software Contributor, PriusPlus PHEV Conversion Project (
http://www.priusplus.org)
An...@Ew...

Re: [Ftdi-usb-sio-devel] VID and PID

[Steve D. <onr...@ya...>]

Did you already get a response on this?

If the device enumerates a new VID or PID then it must
be added in a few places.  check ftdi_sio.c
id_table_combined[], ftdi_chip_name[]
get_ftdi_divisor(),
ftdi_determine_type() for starters.

depending on which kernel version you are supporting
you will need to modify the appropriate driver source
since ftdi_sio.c has changed in linux releases.  

let me know if you have more questions and I'll see
what I can do.

/steverino2

--- Tim Henderson <tim...@ya...> wrote:

> My company has begun to make a device incorporating
> the FTDI 232R for communications.  We have a VID
> from USB.org and I have modified the Windows drivers
> to properly identify our product.  
> 
> Now I would like to get the product working with
> Ubuntu 8.04, and eventually also Red Hat and other
> distributions. 
> 
> How can I do this?  
> 
> Will the driver recognize VID and PID as parameters?
>  Or, must the VID and PID be included in the source
> code?
> 
> Thanks,
> 
> Tim Henderson
> Alti-2 Inc.
> 
> 
> 
>       
> 
>
-------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your
> Move Developer's challenge
> Build the coolest Linux based applications with
> Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source
> event anywhere in the world
>
http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
>
https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
> 

[Ftdi-usb-sio-devel] Device IDs for Epson DM-D110/M58DC (2x20 text display using FT232BM)

[Jan K. <jj...@gm...>]

Hello,

not sure if you are interested in adding this device to the ftdi_sio built-in 
device list. It's a text display intended for POS systems, but sure can be 
used for other purposes, too. The device is referred being a "DM-D110" in the 
attached manual, but "Model M58DC" on the device itself.

The vendor id is 0x1208, the product id 0x0780. From dmesg, manufacturer 
string is "SEIKO EPSON", product string is "USB Edition of DM-D110".

Btw: I tried the vendor= and product= module options for testing, but no use, 
I had to patch the sources to get it work. Are these options broken in 
2.6.25.16? What about the new_id node in sysfs?

Kind regards

	Jan
-- 
"I would rather spend 10 hours reading someone else's source code than
10 minutes listening to music waiting for technical support which isn't."
		-- Dr. Greg Wettstein, Roger Maris Cancer Center

[Ftdi-usb-sio-devel] VID and PID

[Tim H. <tim...@ya...>]

My company has begun to make a device incorporating the FTDI 232R for communications.  We have a VID from USB.org and I have modified the Windows drivers to properly identify our product.  

Now I would like to get the product working with Ubuntu 8.04, and eventually also Red Hat and other distributions. 

How can I do this?  

Will the driver recognize VID and PID as parameters?  Or, must the VID and PID be included in the source code?

Thanks,

Tim Henderson
Alti-2 Inc.



      

[Ftdi-usb-sio-devel] Strange behavior of ftdi module when communicating with device.

[Toan P. <tph...@gm...>]

Hi everyone,

I am not sure if this is the right place to post this message but I've been
experiencing an odd bug in the ftdi_sio kernel module.
After an usb device (using a FTDI 232RQ chip) is connected, it will then
periodically get disconnected and rediscovered after after
sometime when my application communicating with it.  Also, I found one can
easily replicate this problem by doing the following.

a.  Using Linux kernel 2.6.21.7, plug in a usb device having a FTDI 232RQ
chipset
b.  stty -F /dev/ttyUSB0 19200 # Set the proper speed to the device
c.  cat /etc/* > /dev/ttyUSB0
d.  dmesg # you'll see the module error messages and that it got closed and
re-open (rediscovered)

Again, this problem only occurred on my T2 SDE Linux using Kernel 2.6.21-7.
I tested this on my Ubuntu 7.1 box and it ran fine.

I am not sure if this is a kernel or kernel module bug fix that I am not
aware about.  Would someone comment on this strange behavior of the FTDI
USB-serial kernel module ?  thank you.

Toan

Re: [Ftdi-usb-sio-devel] build for 2.6.22 and 2.6.13

[Toan P. <tph...@gm...>]

Hi everyone,

I am not sure if this is the right place to post this message but I've been
experiencing an odd bug in the ftdi_sio kernel module.
After an usb device (using a FTDI 232RQ chip) is connected, it will then
periodically get disconnected and rediscovered after after
sometime when my application communicating with it.  Also, I found one can
easily replicate this problem by doing the following.

a.  Using Linux kernel 2.6.21.7, plug in a usb device having a FTDI 232RQ
chipset
b.  stty -F /dev/ttyUSB0 19200 # Set the proper speed to the device
c.  cat /etc/* > /dev/ttyUSB0
d.  dmesg # you'll see the module error messages and that it got closed and
re-open (rediscovered)

Again, this problem only occurred on my T2 SDE Linux using Kernel 2.6.21-7.
I tested this on my Ubuntu 7.1 box and it ran fine.

I am not sure if this is a kernel or kernel module bug fix that I am not
aware about.  Would someone comment on this strange behavior of the FTDI
USB-serial kernel module ?  thank you.

Toan

[Ftdi-usb-sio-devel] build for 2.6.22 and 2.6.13

[Steve D. <onr...@ya...>]

Hello, I am working on a build of ftdi_usb.c for 2 systems:

fedora 6 (2.6.22.14)
powerpc (2.6.13.4)

the code I'm working with so far is ftdi_usb.c 2 Feb 2006 with support for
FTDI 232R chip.

I have a USB com port adapter based on the FTDI 232RL chip, and this works
fine on my FC6 system.  so I know the module must have been built at some
point against linux distro 2.6.22.14 (FD6)

I'm sorry to say but IMO the makefiles that downloaded with the source were
messed up, probably rooted in linux 2.4  The builds I have attempted so far
are failing in various ways, given changes in makefiles, linux system usb
apis, etc. 

what is the best way to download source for specific linux distros?
I've been to linuxhq.com, which is fine, but only available are patch files.
Is there a way to download a know buildable source for a specific linux
version?

After that I can devise a suitable kernel module build makefile.

Thanks,
/steverino2 

Re: [Ftdi-usb-sio-devel] Long delay between break signal and first data bytes

[Peter K. <pet...@we...>]

Bill,

I tried tcsendbreak with a value of 1 (and other non zero) which 
resulted in no break beeing sent at all.
The problem here is, that the protocoll on the bus I am talking to does 
not allow a delay longer than a character after the break. Whatever I 
tried, it always caused a long break.
I even build a smal circuit that pulls the BUS Tx Signal to ground by 
using RTS. The interesting behaviour then is:

TX  ~~~,___,~~~~~~~||||
RTS ~~~,___,~~~~~~
            |<-.?.->|

Delay of about 50ms betwen raise of RTS and first data byte. The code 
does not implement any delays except for the RTS.

Not sure what this means? Is there anything in addition that I missed in 
programming the FTDI Driver?

Thanks for your patience.  Peter

Bill Ryder wrote:

 > Did you try tcsendbreak with a set value rather than 0?
 >
 > By default it may wait up to 500ms even though data isn't being sent 
for 500ms
 >
 > You can check it with strace -T yourTestProgram  - you'll see the 
duration of tcsendbreak in <>'s in the output.
 >

Re: [Ftdi-usb-sio-devel] Long delay between break signal and first data bytes

[Bill R. <bil...@gm...>]

Did you try tcsendbreak with a set value rather than 0?

By default it may wait up to 500ms even though data isn't being sent for
500ms

You can check it with strace -T yourTestProgram  - you'll see the duration
of tcsendbreak in <>'s in the output.



On Sat, Oct 25, 2008 at 3:38 AM, Peter Künnemann <pet...@we...>wrote:

> Hi,
> I am using an FTDI device on a linux system (2.6.24-21) USB Data are:
>
> FTDZIG54, TTL232R
>
> I am having some trouble to get tcsendbreak() working. I am expecting a
> break level for some milliseconds on the TX line followed by the data.
>
> The C code looks as follows:
> //
> int sync=0x55;
>
> tcsendbreak(handle,0)
> write(handle,&sync,1)
> ...
> //
> When I connect a scope to the tx line I can see something like:
>
> ~~~~.__,~~~~~~~~~~~~,_|||||
>     A break signal
>         some 500ms delay
>                     the data beeing sent
>
> I wonder how I would be able to send a break, immediately followed by my
> data. The problem is that other devices on the line do not expect such a
> long delay following the break signal.
>
> Any help regarding breaks and general serial programming for ftdi
> devices under linux would be very much appreciated.
> I have scaned the internet for some help but nothing apropriate was found
>
> regards, Peter
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>

[Ftdi-usb-sio-devel] Long delay between break signal and first data bytes

[Peter K. <pet...@we...>]

Hi,
I am using an FTDI device on a linux system (2.6.24-21) USB Data are:

FTDZIG54, TTL232R

I am having some trouble to get tcsendbreak() working. I am expecting a 
break level for some milliseconds on the TX line followed by the data.

The C code looks as follows:
//
int sync=0x55;

tcsendbreak(handle,0)
write(handle,&sync,1)
...
//
When I connect a scope to the tx line I can see something like:

~~~~.__,~~~~~~~~~~~~,_|||||
     A break signal
         some 500ms delay
                     the data beeing sent

I wonder how I would be able to send a break, immediately followed by my 
data. The problem is that other devices on the line do not expect such a 
long delay following the break signal.

Any help regarding breaks and general serial programming for ftdi 
devices under linux would be very much appreciated.
I have scaned the internet for some help but nothing apropriate was found

regards, Peter

[Ftdi-usb-sio-devel] ftdi-usb-sio driver under Uboot

[mike z. <ma...@gm...>]

Hello,

Anyone has the ftdi-usb-sio driver under Uboot?

Thanks,


Mike

[Ftdi-usb-sio-devel] Working with a FT232BM

[Juan P. G. C. <jua...@gm...>]

Hi,

I'm working with a bill acceptor and it is recognized as a ft232bm chip and
mounted in /dev/ttyUSB0.
I have tried all the examples in the official ftdi site but the bill
acceptor doesn't work.

Anyone has experience with this kind of device?

Thanks a lot,

Juan García

Re: [Ftdi-usb-sio-devel] ftdi-usb-sio driver under Uboot

[mike z. <ma...@gm...>]

 Hello,

 Anyone has the ftdi-usb-sio driver under Uboot?

 Thanks,

 Mike

Re: [Ftdi-usb-sio-devel] Error on install

[Bill R. <bil...@gm...>]

Your best bet would be to use google.

http://www.google.co.nz/search?hl=en&safe=off&q=kernel+build+howto+linpus&btnG=Search&meta=

I don't know anything about Linpus.



On Wed, Aug 27, 2008 at 5:15 AM, Mike Parkes <mi...@mi...>wrote:

> Tried to load the FTDI linux driver on my Acer Aspire One running Linpus
> and got the following:-
>
> [user@localhost temp]$ make
>
> /mnt/home/temp/Rules.make:24; /lib/modules/2.6.23.9lw/build/.config: No
> such file or directory
>
> make:***No rule to make target '/lib/modules/2.6.23.9lw/build/.config'.
> Stop
>
> [user@localhost temp]$
>
> I assume that as the installed linux is a "light" version I need to
> install something else first (ie I had to install 'make' to achieve the
> above !)
>
> Mike Parkes
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>

[Ftdi-usb-sio-devel] Error on install

[Mike P. <mi...@mi...>]

Tried to load the FTDI linux driver on my Acer Aspire One running Linpus 
and got the following:-

[user@localhost temp]$ make

/mnt/home/temp/Rules.make:24; /lib/modules/2.6.23.9lw/build/.config: No 
such file or directory

make:***No rule to make target '/lib/modules/2.6.23.9lw/build/.config'. 
Stop

[user@localhost temp]$

I assume that as the installed linux is a "light" version I need to 
install something else first (ie I had to install 'make' to achieve the 
above !)

Mike Parkes

[Ftdi-usb-sio-devel] New PIDs where to? Two diff. PIDs configured?

[Ekki P. (DF4OR) <ep...@pl...>]

Hello,
two questions, please:

1.) Is there a way to feed two 'vendor=0x.... product=0x....' pairs to 
ftdi_sio at the same time as parameters, where the PIDs are different? I have 
devices to connect which are currently not in the list of known PIDs of 
ftdi_sio, and I have to connect two of them at the same time. One each at a 
time works fine.
I tried with two pairs of parameters but only the last one seems to be 
recognized.


2.) Where can I send information on additional VID/PIDs to incorporate into 
ftdi_sio, so they will be known in a future version. 

Thanks,
Ekki

Re: [Ftdi-usb-sio-devel] FT232BM with different bcdDevice

[<am...@sy...>]

I played a little around with the Mprog utility from ftdi and discovered
that a ft232bm with an empty eeprom has the bcdDevice 0x400. As soon as
something (also the defaults) gets programmed in the eeprom with mprog the
bcdDevice changes to 0x200.

> I have a bunch of FT232BL here which is the lead free versions of the
> FT232BM. They have a
> different bcdDevice version then the kernel driver expects:
>
> ftdi_determine_type: bcdDevice = 0x200, bNumInterfaces = 1
>
> With that Version they are detected as FT8U232AM which does not work. When
> I force them to be
> detected as FT232BM they work fine.
> So now I'm not sure how to change the detection routine, without breaking
> detection for the
> other chips.
> This would work:
>
> --- ftdi_sio.c.orig	2008-08-14 10:18:40.000000000 +0200
> +++ ftdi_sio.c	2008-08-14 10:21:16.000000000 +0200
> @@ -825,6 +825,9 @@
>  			dbg("%s: something fishy - bcdDevice too low for multi interface
> device",
>  				__FUNCTION__);
>  		}
> +	} else if (version == 0x200) {
> +		// Assume its an FT232BL (lead free version of FT232BM)
> +		priv->chip_type = FT232BM;
>  	} else if (version < 0x200) {
>  		/* Old device.  Assume its the original SIO. */
>  		priv->chip_type = SIO;
>
> But since I did not found a list of all bcdDevice for all ftdi chips, I
> don't know if there is
> a FT8U232AM with the same bcdDevice and I need to make a complete
> different detection.
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ftdi-usb-sio-devel mailing list
> Ftd...@li...
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
>