From: "tb93" <[EMAIL PROTECTED]>
> I am trying to get a ConnectTech WhiteHeat 4 port USB
> to serial converter to work properly on an embedded
> PPC platform running ppclinux 2.4.19-pre7.

The driver you are using is a basic version; I've just completed an
up to date version which will be released shortly once it's done QA.

> I compiled USB support, USB Serial Converter support,
> and USB ConnectTech WhiteHEAT Serial Driver support

Correct.

> into the kernel.Upon rebooting, the kernel log showed
> that the USB device was not claimed by any active
> driver. I then compiled "Support for hot-pluggable

This is sometimes misleading; the usb core can report not claimed
faster than the hotplugging system can load the usbserial and
whiteheat modules.

> I am not using hotplug support (I do not have any
> hotplug scripts loaded) in my configuration. Does the
> usb or usbserial driver require hotplug support to
> work?

Require, no. But as you've seen if they're not in, you'll have to load
the modules manually. This can be done with modprobe.

> With hotplug support on, I get the following log
> entries:
> Apr  8 02:37:08 (none) kernel: usbserial.c: Connect
> Tech - WhiteHEAT converter detected

Looks good.

> prior to plugging in the WhiteHeat, I had previously
> created 4 new dev nodes using:
> mknod /dev/ttyUSB0 c 188 0
> mknod /dev/ttyUSB0 c 188 1...
> chown root /dev/ttyUSB*
> chmod 660 /dev/ttyUSB*

[root@moll linux]# dir /dev/ttyUSB[0-3]
crw-rw----    1 root     uucp     188,   0 Sep 12 11:41 /dev/ttyUSB0
crw-rw----    1 root     uucp     188,   1 Aug 30  2001 /dev/ttyUSB1
crw-rw----    1 root     uucp     188,   2 Aug 30  2001 /dev/ttyUSB2
crw-rw----    1 root     uucp     188,   3 Aug 30  2001 /dev/ttyUSB3
[root@moll linux]# minicom -s
<change the serial port to /dev/ttyUSB0 and save as whiteheat-1>
[root@moll linux]# minicom whiteheat-1
<minicom running>

Assuming that your second mknod command meant ttyUSB1 instead of 0, I
see nothing wrong with your node creation. You might try chwoning the
group to uucp. Things work for me. :-)

> #  echo "test" > /dev/ttyUSB0cannot create
> /dev/ttyUSB0: Connection timed out

? This is odd. Certainly not what happens when you've forgotten to
load the modules.

> here are the pertinent listings from my /dev directory
> crw-rw----    1 root     root     188,   0 Apr  8
> 01:30 ttyUSB0
> crw-rw----    1 root     tty      188,   1 Aug  6
> 2002 ttyUSB1

Looks good, except perhaps try uucp instead of root/tty.

> Any thoughts on why minicom, microcom, and even
> redirect can't seem to even "see" the ttyUSBx nodes in
> my /dev directory?

Please contact myself or support ([EMAIL PROTECTED]) directly to open a
call. Otherwise I'll look at it in my CFT. :-)

> Tyrone Bekiares
> Senior Software Engineer
> Motorola, Inc.

I'm curious what you're using the WhiteHEAT for?

..Stu

--
We make multiport serial boards.
<http://www.connecttech.com>
(800) 426-8979




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to