[Bug 45986] Re: unable to bind to pilot
Matt Price
matt.price at utoronto.ca
Tue Sep 26 17:41:28 UTC 2006
Made some small diagnostic progress on this. still no joy with the
libusb direct method. However I can verify that it's possible to send
data across the /dev/ttyUSB* ports created by the visor module (if it's
not blacklisted). pilot-xfer still won't work; in fact, as far as I
can tell, just starting a pilot-xfer operation on a ttyUSB port will
cause the palm device to detach from the port. So I get odd sequences
of messages in dmesg:
[17187265.152000] usb 3-1: new full speed USB device using uhci_hcd and address 34
[17187265.324000] usb 3-1: configuration #1 chosen from 1 choice
[17187265.328000] visor 3-1:1.0: Handspring Visor / Palm OS converter detected
[17187265.328000] usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
[17187265.328000] usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB1
[17187275.156000] visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2
[17187275.156000] visor ttyUSB3: Handspring Visor / Palm OS converter now disconnected from ttyUSB3
[17187291.876000] usb 3-1: USB disconnect, address 34
note that the usb2/3 disconnect somehow comes right after the
attachment to 0/1! I think this is somehow caused by pilot-link.
However, I do think that some data comes across the line, because when I
try
cat /dev/ttyUSBx
and push the sync button, the cat process immediately ends, as though
it's received a ctrl-c over the line or something.
and finally, I can now get an effect from gpilotd. by adding several
new devices -- so that /dev/ttyUSB[0-3] are ALL being watched, I can
make my palm do a soft reset! that's something I guess. Here's the output of gpilotd:
d$ gpilotd
gpilotd-Message: gnome-pilot 2.0.14 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching tx (/dev/ttyUSB0)
gpilotd-Message: Watching usb1 (/dev/ttyUSB1)
gpilotd-Message: Watching tx-new (usb:)
gpilotd-Message: Watching usb2 (/dev/ttyUSB2)
gpilotd-Message: Watching usb3 (/dev/ttyUSB3)
gpilotd-Message: Found 4766, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0502, 0736
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 091e, 0004
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 115e, f100
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0100
gpilotd-Message: Using net FALSE
gpilotd-Message: Found 082d, 0200
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0300
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0c88, 0021
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0002
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0003
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0020
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0031
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0040
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0050
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0060
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0070
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0080
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 8001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 6601
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0038
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0066
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0095
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 009a
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00c9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00da
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00e9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0144
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0169
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 12ef, 0100
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=57600
at this pointthe palm resets itself.
don't know if any of this clarifies anything!
thanks again though,
Matt
--
unable to bind to pilot
https://launchpad.net/bugs/45986
More information about the desktop-bugs
mailing list