On Mon, Jun 12, 2000 at 03:31:46PM -0400, Ian Soboroff wrote:
<nice summary about the PalmConnect snipped>
>
> 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?
Try contacting Palm :)
Seriously, it looks like the device needs some information to be sent
on its interrupt pipe to tell the Palm what baud, bits, etc. and that it
wants to do a sync.
Since the device is a vendor specific one, you can either sniff the
protocol by using an analyzer (a physical one, or one of the windows
ones that have been mentioned on this list) and determine what is
needed to be sent to the device in what order to get it to work. This
is what I had to do to get the HandSpring Visor to work. Only after I
got it barely running did HandSpring release the specs for the device
(although this was probably more due to the time it takes dealing with
a company instead of any other reason.)
Or try contacting Palm to get the specs on the device.
If you do either of the above, let me know and either make up a patch, or
give me the information and I'll add it to the module.
Hope this helps,
greg k-h
greg@(kroah|wirex).com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
