Guys:
I'm trying to establish USB communications between my PC (Red Hat 7.3,
linux-2.4.18-0.22) and an arm-linux target (CerfPod,
linux-2.4.9-rmk2-np1) using the SA1110. USB networking seems to work
fine (limited but successful testing), but usbserial does not.
Here's the info from usbview:
Unknown Device
Manufacturer: tbd
Serial Number: 00000000
Speed: 12Mb/s (full)
USB Version: 1.00
Device Class: ff(vend.)
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 8
Number of Configurations: 1
Vendor Id: fff0
Product Id: 0001
Revision Number: 0.01
Config Number: 1
Number of Interfaces: 1
Attributes: 40
MaxPower Needed: 0mA
Interface Number: 0
Name:
Alternate Number: 0
Class: ff(vend.)
Sub Class: 0
Protocol: 0
Number of Endpoints: 2
Endpoint Address: 82
Direction: in
Attribute: 2
Type: Bulk
Max Packet Size: 64
Interval: 0ms
If I run minicom on the arm-linux device, and I cat from /dev/ttyUSB0
on my PC, then when I press a key on the target I see data on the PC.
However, I am not able to send data from the PC through /dev/ttyUSB0
back to the arm-linux device. Instead, the process doing the write on
the PC just hangs forever. I have tried using both minicom and echo.
Here's some more information from the PC:
[bgat@mars bgat]$ uname -a
Linux mars 2.4.18-0.13 #1 Mon Apr 1 14:19:29 EST 2002 i686 unknown
[bgat@mars bgat]$ ls -l /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 0 Apr 15 11:06 /dev/ttyUSB0
[bgat@mars bgat]$ tail /var/log/messages
Apr 15 11:05:59 mars kernel: usb.c: registered new driver serial
Apr 15 11:05:59 mars kernel: usbserial.c: USB Serial support registered for Generic
Apr 15 11:05:59 mars kernel: usbserial.c: USB Serial Driver core v1.4
[arm-linux target plugged in...]]
Apr 15 11:06:22 mars kernel: hub.c: USB new device connect on bus2/2, assigned device
number 5
Apr 15 11:06:22 mars kernel: usbserial.c: Generic converter detected
Apr 15 11:06:22 mars kernel: usbserial.c: Generic converter now attached to ttyUSB0
(or usb/tts/0 for devfs)
Apr 15 11:06:26 mars /etc/hotplug/usb.agent: ... no modules for USB product fff0/1/1
... and from the arm-linux target:
usbchr: : using vendor=0xfff0, product=0x0001.
usbchr: : using harded 00000000 serial number.
usbctl: Started for usb-char
usbctl: zombie suspended --> [resume] --> zombie. Device in powered state.
usbctl: zombie --> [suspend] --> zombie suspended. Device in suspended state.
usbctl: zombie suspended --> [reset] --> default. Device in default state.
usbctl: Resetting
usbctl: default --> [address assigned] --> address. Device in address state.
usbep0: I have been assigned address: 5
usbctl: address --> [configure] --> configured. Device in configured state.
[root@CerfLinux /root]$ uname -a
Linux CerfLinux 2.4.9-ac10-rmk2-np1-cerf1 #143 Fri Apr 12 10:47:01 CDT 2002 armn
[root@CerfLinux /root]$ ls -l /dev/ttyUSB0
crw-r--r-- 1 root root 10, 240 Dec 31 16:05 /dev/ttyUSB0
I'm definitely a USB newbie, so I'm not sure even where to begin when
tracking this problem down. Nobody on the arm-linux mailing lists
seems to have any ideas. Suggestions?
Thanks!
b.g.
--
Bill Gatliff
[EMAIL PROTECTED]
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
