[coldsync-hackers] USB + Palm m505 + Linux

[Sean Buckley <sean@redbug.uklinux.net>]

I thought I'd got the USB connection to my m505 working, after many 
attempts. I tried again today, and the connection wasn't working. After 
much trial and error I discovered the following:

When I first try to connect, the connection fails altogether. Running with 
debugging level 5 on sync, misc, IO and net, the output ends with:

...
Assuming 2400 bps (11) yes
Assuming 1200 bps (9) yes
Inside netsync_read()
Reading packet data
<<   90 01 00 00 00 00 00 00 00 20 00 00 00 08 00 00   | ......... ......
<<   01 00 00 00 00 00                                 | ......
netsync_read(ritual resp 1) returned 1
<<< 90 01 00 00 00 00 00 00 00 20 00 00 00 08 00 00   | ......... ......
<<< 01 00 00 00 00 00                                 | ......
Inside netsync_write()
Sending NetSync header (50 bytes)
NET --> 01 01 00 00 00 32                                 | .....2
Sending NetSync data
NET >>> 12 01 00 00 00 00 00 00 00 20 00 00 00 24 ff ff   | ......... ...$ÿÿ
NET >>> ff ff 3c 00 3c 00 00 00 00 00 00 00 00 00 c0 a8   | ÿÿ<.<.........À¨
NET >>> a5 1f 04 27 00 00 00 00 00 00 00 00 00 00 00 00   | ¥..'............
NET >>> 00 00                                             | ..
netsync_write(ritual stmt 2) returned 50
Inside netsync_read()
netsync_read: Reading packet header


After about 20 attempts to connect, I get a bit further.  The Palm beeps 
and displays the message "identifying user", but gets no further.  In this 
case, the debugging output finishes with:

...
System info:
	ROM version: 0x04000000
	Localization: 0x00010000
	product ID: 0x00030000
	DLP version: 1.2
	Product compatibility version: 3.0
	Max. record size: 65505 (0x0000ffe1)
Inside netsync_write()
Sending NetSync header (36 bytes)
NET --> 01 04 00 00 00 24                                 | .....$
Sending NetSync data
NET >>> 2d 01 0a 00 a3 40 00 00 00 00 00 00 00 00 00 04   | -...£@..........
NET >>> 01 02 00 00 01 04 00 00 00 00 00 04 73 6e 75 6d   | ............snum
NET >>> 00 02 00 00                                       | ....
Inside netsync_read()
netsync_read: Reading packet header


Showing ridiculously dogged determination, I then had another 20 or so 
attempts at synching.  Eventually it synched successfully, although 
coldsync never exits back to the shell prompt. The final effort ends with 
the following:

...
Inside netsync_read()
netsync_read: Reading packet header
Got header: cmd 0x01, xid 0xa6, len 0x00000004
Reading packet data
<<   af 00 00 00                                       | ¯...
===== Finished syncing
Calling io_drain()


Once it has synched successfully all further synchs are successful until 
the next reboot, when I have to go through the whole process again. It's 
almost as if it needs 40 or 50 attempted synchs before it notices that the 
device is actually there.

The visor module successfully recognises the device, and identifies it as 
an m505 every time I press the Hotsync button.

I'm running coldsync 2.2.5 on Linux kernel 2.4.8 (Mandrake 8.1), but the 
same happens with the 2.3.0 20011210 snapshot (except I get seg faults when 
it fails to connect).

Finally, I have the following in my .coldsyncrc:

listen serial {
	device: "/dev/ttyUSB1";
	protocol: simple;
	transient;
}

pda "My Palm" {
	snum: "L0PK17C13832-M";
	username: "Sean";
	userid: -1203939113;
	directory: "/home/sean/m505";
	default;
}

The userid seems a bit odd - it was the id suggested by coldsync -mI.


Sean.




This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.