Does anyone have experience with the PalmConnect USB kit? it's a
serial-to-USB adapter that goes between the Palm cradle and a USB
jack. I haven't gotten my Pilot to sync over it, so I'm appealing for
help...
My machine is a Dell Latitude CS (no serial ports, hence need for USB,
a technology for making old, reliable interconnects expensive and
dodgy ;-) I'm running 2.2.16 with the 2.2 backport from the linux-usb
web page. My Pilot is running OS 3.3, with the HotSync set to Direct
Serial.
'modprobe usb-uhci' seems to work without a hitch, and it sees the
adapter fine:
(from dmesg)
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.228 $ time 09:13:06 Jun 8 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: Intel USB controller: setting latency timer to 0
usb-uhci.c: USB UHCI at I/O 0xece0, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1
usb.c: kmalloc IF c2b40ba0, numif 1
usb.c: new device strings: Mfr=0, Product=2, SerialNumber=1
usb.c: USB device number 1 default language ID 0x0
Product: USB UHCI Root Hub
SerialNumber: ece0
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: ganged power switching
hub.c: standalone hub
hub.c: global over-current protection
hub.c: power on to power good time: 2ms
hub.c: hub controller current requirement: 0mA
hub.c: port 1 is removable
hub.c: port 2 is removable
hub.c: local power source is good
hub.c: no over-current condition exists
hub.c: enabling power on all ports
usb.c: hub driver claimed interface c2b40ba0
hub.c: port 1 connection change
hub.c: portstatus 101, change 1, High Speed
hub.c: portstatus 103, change 0, High Speed
usb.c: USB new device connect, assigned device number 2
usb.c: kmalloc IF c2b403a0, numif 1
usb.c: new device strings: Mfr=1, Product=2, SerialNumber=3
usb.c: USB device number 2 default language ID 0x409
Manufacturer: Palm Computing, Inc.
Product: USB Serial Adaptor
SerialNumber: 00006978
usb.c: unhandled interfaces on device
usb.c: This device is not recognized by any installed USB driver.
Length = 18
DescriptorType = 01
USB version = 1.00
Vendor:Product = 0830:0080
MaxPacketSize0 = 8
NumConfigurations = 1
Device version = 1.00
Device Class:SubClass:Protocol = ff:00:00
Vendor class
Configuration:
bLength = 9
bDescriptorType = 02
wTotalLength = 0027
bNumInterfaces = 01
bConfigurationValue = 01
iConfiguration = 00
bmAttributes = 80
MaxPower = 94mA
Interface: 0
Alternate Setting: 0
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 00
bNumEndpoints = 03
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 02 (Bulk)
wMaxPacketSize = 0040
bInterval = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 02 (out)
bmAttributes = 02 (Bulk)
wMaxPacketSize = 0040
bInterval = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 83 (in)
bmAttributes = 03 (Interrupt)
wMaxPacketSize = 0008
bInterval = 01
Using the Vendor:Product pair, I then modprobe usb-serial:
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial support registered for Connect Tech - WhiteHEAT
usbserial.c: USB Serial support registered for Handspring Visor
usbserial.c: USB Serial support registered for FTDI SIO
usbserial.c: USB Serial support registered for Keyspan PDA
usbserial.c: USB Serial support registered for ZyXEL - omni.net lcd plus usb
usb.c: registered new driver serial
usbserial.c: Looking at Generic Vendor id=0830 Product id=0080
usbserial.c: descriptor matches
usbserial.c: found bulk in
usbserial.c: found bulk out
usbserial.c: found interrupt in
usbserial.c: Generic converter detected
usbserial.c: get_free_serial 1
usbserial.c: minor base = 0
usbserial.c: Generic converter now attached to ttyUSB0
usb.c: serial driver claimed interface c2b403a0
So far, so good. But when I try to run 'pilot-xfer -p /dev/ttyUSB0
...' it doesn't seem to connect (no beeps from the Pilot, pilot-xfer
just waits). My log fills up with messages of:
usbserial.c: generic_chars_in_buffer port 0
with the occasional
usbserial.c: data read - length = 64, data = 12 00 18 00 00 00 00 00 00 00 06 00 18 f0
00 00 78 c0 06 cf cc 80 e0 f8 9e fe e6 fe 1e 00 1e 00 1e 00 4a 75 2d e3 14 1f d4 8b 0f
25 87 e6 09 24 97 cf 05 5d c0 b4 1a c8 9d dc f6 05 a3 98 73 7e
(the data isn't the same each time.)
where do i go from here?
tia,
ian
--
----
Ian Soboroff [EMAIL PROTECTED]
University of MD Baltimore County http://www.cs.umbc.edu/~ian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
