| View previous topic :: View next topic |
| Author |
Message |
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
 Posted: Wed Nov 03, 2004 8:55 am Post subject: [SOLVED] cannot sync my pda (zire 71) |
 |
|
Hi
since two days I'm working on this problem without success...
so my kernel is 2.4 and I'm using devfs (devfsd is running)
I've installed hotplug (started)
here is my kernel config about usb (I'm not sure that usb is well launched when starting:
| Code: | CONFIG_USB_IRDA=m
CONFIG_USB_AUERISDN=m
CONFIG_USB=m
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_UHCI=m
CONFIG_USB_UHCI_ALT=m
CONFIG_USB_OHCI=m
CONFIG_USB_AUDIO=m
CONFIG_USB_EMI26=m
CONFIG_USB_MIDI=m
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_HP8200e=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_KBD=mCONFIG_USB_WACOM=m
CONFIG_USB_KBTAB=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_DC2XX=m
CONFIG_USB_MDC800=m
CONFIG_USB_SCANNER=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_HPUSBSCSI=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_OV511=m
CONFIG_USB_PWC=m
CONFIG_USB_SE401=m
CONFIG_USB_STV680=m
# CONFIG_USB_W9968CF is not set
CONFIG_USB_VICAM=m
CONFIG_USB_DSBR=m
CONFIG_USB_DABUSB=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_KAWETH=m
CONFIG_USB_CATC=m
CONFIG_USB_CDCETHER=m
CONFIG_USB_USBNET=m
CONFIG_USB_USS720=mCONFIG_USB_SERIAL=m
# CONFIG_USB_SERIAL_DEBUG is not set
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_USA28=y# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_RIO500=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_TIGL=m
CONFIG_USB_BRLVGER=m
CONFIG_USB_LCD=m
CONFIG_USB_SPEEDTOUCH=m
# CONFIG_USB_GADGET is not set
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_MOUSE=m
CONFIG_USB_AIPTEK=m
|
I've tried to link /dev/pilot like this : | Code: |
rm -r /dev/pilot
ln -s /dev/usb/tts/0 /dev/pilot
$ pilot-xfer -p /dev/pilot -L
Unable to bind to port: /dev/pilot
Please use --help for more information |
I've tried to recreate the node (I'm not sure about 1 and 2) without success :
| Code: | # mknod /dev/pilot c 1 2
|
While syncing, i'm getting that :
| Code: | # lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 005: ID 0830:0060 Palm, Inc. Palm Tungsten T
|
I'm completely lost ! 
_________________
M6 go home
Last edited by poleta33 on Thu Nov 04, 2004 12:08 pm; edited 1 time in total |
|
| Back to top |
|
 |
hecatomb
Guru
Joined: 02 Sep 2004
Posts: 525
|
| Posted: Wed Nov 03, 2004 2:44 pm Post subject: |
|
|
Why have you removed the /dev/pilot device node?
Is there anything related in dmesg after trying to connect?
| http://wiki.pilot-link.org/book/view/37 wrote: | Physical connection
In order to confirm that we can communicate with the Palm handheld, we will use the following command:
pilot-xfer --port --list
If all goes well, that will display a list of databases on the palm device.
Cradle/Cable
Connect your cradle (or cable) to an appropriate port.
For USB, press the HotSync button on the Palm or the cradle _first_, a good rule of thumb is to count to three, before launching any pilot-link utilities. |
According to the kernel docu the original device nodes should look like this:
| Documentation/usb/usb-serial.txt wrote: | ...
If you are not using devfs:
The major number that the driver uses is 188 so to use the driver,
create the following nodes:
mknod /dev/ttyUSB0 c 188 0
mknod /dev/ttyUSB1 c 188 1
mknod /dev/ttyUSB2 c 188 2
mknod /dev/ttyUSB3 c 188 3
.
.
.
mknod /dev/ttyUSB254 c 188 254
mknod /dev/ttyUSB255 c 188 255
If you are using devfs:
The devices supported by this driver will show up as
/dev/usb/tts/{0,1,...}
When the device is connected and recognized by the driver, the driver
will print to the system log, which node(s) the device has been bound to.
... |
|
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Wed Nov 03, 2004 3:09 pm Post subject: |
|
|
I'm using devfs
and /dev/usb/tts/{0,1,...} exist
how can I see on which usb port (I've got two usb ports) my cradle is connected ???
_________________
M6 go home |
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Wed Nov 03, 2004 3:15 pm Post subject: |
|
|
my node was recreated during reboot 
| Code: | gva1080 root # ls -l /dev/pilot
total 0
lr-xr-xr-x 1 root root 14 Nov 3 2004 0 -> /dev/usb/tts/0
lr-xr-xr-x 1 root root 14 Nov 3 2004 1 -> /dev/usb/tts/1
|
so if I try to sync on /dev/pilot/0 or /dev/pilot/1, both fail...
grrrrr
_________________
M6 go home |
|
| Back to top |
|
|
hecatomb
Guru
Joined: 02 Sep 2004
Posts: 525
|
| Posted: Wed Nov 03, 2004 3:16 pm Post subject: |
|
|
As posted before:
| Documentation/usb/usb-serial.txt wrote: | ...
When the device is connected and recognized by the driver, the driver
will print to the system log, which node(s) the device has been bound to.
... |
Try dmesg | tail after pluging in the device. |
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Wed Nov 03, 2004 3:24 pm Post subject: |
|
|
| Code: | va1080 root # dmesg | tail
hub.c: new USB device 00:1f.2-2, assigned address 5
usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter detected
usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
visor.c: Bytes In = 0 Bytes Out = 0
usb.c: USB disconnect on device 00:1f.2-2 address 5
usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB0
usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB1
|
_________________
M6 go home |
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Wed Nov 03, 2004 3:30 pm Post subject: |
|
|
maybe is it a grant problem ?
/dev/usb/tts/0 and 1 are 555 ?...
_________________
M6 go home |
|
| Back to top |
|
|
hecatomb
Guru
Joined: 02 Sep 2004
Posts: 525
|
| Posted: Wed Nov 03, 2004 3:51 pm Post subject: |
|
|
I think the access rights are not related when connecting (recognition by the kernel).
Reading (--list) should also do its work!
| Code: | ...
hub.c: new USB device 00:1f.2-2, assigned address 5
...
usb.c: USB disconnect on device 00:1f.2-2 address 5
... |
Have manually pluged off the device? I hope so!
| drivers/usb/serial/visor.c wrote: | | Code: | ...
static void visor_close (struct usb_serial_port *port, struct file * filp)
{
...
/* Uncomment the following line if you want to see some statistics in your syslog */
/* dev_info (&port->dev, "Bytes In = %d Bytes Out = %d\n", bytes_in, bytes_out); */
}
... |
|
The visor_close call is invoked by the kernel when a user-space tool issues the close call on the device file (/dev/usb/tts/*).
So I guess pilot-xfer is acting on the correct device.
Strange! Have you played with the HotSync button as mentioned above? |
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Wed Nov 03, 2004 4:02 pm Post subject: |
|
|
I've tried to plug out and back in the cradle...
what seems strange is that my pda is connected to the two ports
| Code: | usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
usbserial.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) |
note that I don't have installed visor or packages with such a name
I'm really lost...
_________________
M6 go home |
|
| Back to top |
|
|
hecatomb
Guru
Joined: 02 Sep 2004
Posts: 525
|
| Posted: Wed Nov 03, 2004 4:18 pm Post subject: |
|
|
The driver in the kernel is called visor!!
Using google I found some messages like this:
| Quote: | ...
visor.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x: Number of ports: 2
visor.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x: port 1, is for Generic use and is bound to ttyUSB0
visor.c: Handspring Visor / Treo / Palm 4.0 / Clié 4.x: port 2, is for HotSync use and is bound to ttyUSB1
... |
Seems to be ok that there are two ports used!
I looked through the code further and the init is something like this (pseudocode):
| Code: | register new serial usb device
if this failes goto MARK
print a message like this: USB HandSpring Visor / Palm OS driver v2.1
return from init with 0 (= success)
MARK
deregister the new serial usb driver (cleanup)
return from init with not 0 (= failed) |
I can't see this info message (USB HandSpring Visor / Palm OS driver v2.1) in your output of dmesg!
Are you sure that the disconnect was because you unplugged the device or the driver itself (see pseudocode) did the disconnect? Please verify this! |
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Wed Nov 03, 2004 4:33 pm Post subject: |
|
|
I'm approaching !...
when I'm doing
| Code: | root# pilot-xfer -p /dev/pilot/1 -l
|
I can clearly see everything about my pda... but used from jpilot (or evolution) it doesn't work...
progressing !!!
I will try again tomorrow !
thanks !
_________________
M6 go home |
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Wed Nov 03, 2004 4:34 pm Post subject: |
|
|
the disconnect was due to me (I think) : when I see the sync is failing I stop it...
thanks a lot for your help !!
_________________
M6 go home |
|
| Back to top |
|
|
poleta33
Tux's lil' helper
Joined: 13 Oct 2004
Posts: 104
Location: Geneva (CH)
|
| Posted: Thu Nov 04, 2004 12:08 pm Post subject: |
|
|
yes !!! I've found the solution : it was a grant problem !
I should sync on /dev/pilot/1
my solution : | Code: | gva1080 root # chmod 0666 /dev/usb/tts/1
gva1080 root # chmod 0666 /dev/usb/tts/0
|
_________________
M6 go home |
|
| Back to top |
|
|
|
Portage & Programming
