Yeah, I can get coldsync to work correctly on my machine. I sorta figured out
the problem. If I launch pilot-link from the usbd.conf it will work for a
few read/writes, but then it can't read anymore and the Visor times out.
The output created by syslogd when I inserted output statements:
Jun 27 22:12:14 rusty lt-pilot-xfer: usb open
Jun 27 22:12:14 rusty lt-pilot-xfer: Reading data (5:1) ...
Jun 27 22:12:14 rusty lt-pilot-xfer: 10:1
Jun 27 22:12:14 rusty lt-pilot-xfer: Writing data (5:24) ...
Jun 27 22:12:14 rusty lt-pilot-xfer: Reading data (5:3) ...
Jun 27 22:12:14 rusty lt-pilot-xfer: Reading data (5:1) ...
Jun 27 22:12:14 rusty last message repeated 6 times
Jun 27 22:12:14 rusty lt-pilot-xfer: 14:1
Jun 27 22:12:14 rusty lt-pilot-xfer: Reading data (5:1) ...
Jun 27 22:12:14 rusty last message repeated 13 times
Jun 27 22:12:14 rusty lt-pilot-xfer: 2:1
Jun 27 22:12:14 rusty lt-pilot-xfer: Reading data (5:1) ...
Jun 27 22:12:14 rusty lt-pilot-xfer: Reading data (5:1) ...
Jun 27 22:12:44 rusty lt-pilot-xfer: -1:1
Jun 27 22:12:44 rusty lt-pilot-xfer: usb read error
Jun 27 22:12:44 rusty lt-pilot-xfer: Writing data (5:24) ...
Jun 27 22:12:44 rusty lt-pilot-xfer: Reading data (5:3) ...
Jun 27 22:12:44 rusty lt-pilot-xfer: -1:3
.... a few more of the last 4 lines and then fails the Visor will timeout.
Thanks,
--
Anish Mistry
On Wednesday 26 June 2002 05:15 pm, you wrote:
> I have my visor coldsyncing via usb on my 4.6-RC3 box just fine -- have
> you been able to get coldsync to work at all? If not, start by getting
> that to happen. The main pain I had was trying to hit the race condition
> of when ugen0.X is writable - the ugen driver is configured for so short a
> period of time after the sync button is pressed that I could never do it
> manually.
>
> I ended up putting a claus like this in my usbd.conf:
>
>
>
> device "Handspring Visor"
> vendor 0x082d
> product 0x0100
> release 0x0100
> #syncing
> attach "/usr/local/bin/coldsync -t usb -svv -l /tmp/usb.log -f
> /usr/home/fred/.coldsyncrc -md ${DEVNAME} "
>
> #initalize
> # attach "/usr/local/bin/coldsync -t usb -svv -l /tmp/usb.log -f
> /usr/home/fred/.coldsyncrc -mI ${DEVNAME}"
>
> #backup
> # attach "/usr/local/bin/coldsync -t usb -svv -l /tmp/usb.log -f
> /usr/home/fred/.coldsyncrc -mb /usr/home/fred/palmbak ROM"
>
>
> You need to do the 'initialze' like one time, and then comment it out and
> uncomment the syncing line. From then on out it worked (had to fiddle
> with a bunch of stuff including my coldsyncrc and /usr/local/etc/palms)
>
>
> Does this help at all?
>
>
> Fred
>
>
> On Sat, 22 Jun 2002, Anish Mistry wrote:
>
> > I am having some trouble reading data from a Handspring Visor Platinum.
What
> > I am trying to do is make the necessary modifications to pilot-link so
that
> > it will work with the usb on FreeBSD. My problem is that I can open a
> > connection to the /dev/ugen0.2 endpoint, but whenever I try to call a
read()
> > it returns with error 5 (Input/Output Error). I used the coldsync code as
a
> > base, but the read keeps failing. I can post the code, I just wanted to
see
> > if there were anyone with a similar problem. I have checked the
permissions
> > on the device nodes and they are fine, the same problem occurs when
running
> > as root.
> >
> > What I do:
> > 1) Press the HotSync Button on my crade
> > 2) Run ./pilot-xfer -p usb:/dev/ugen0 --sync /home/amistry/bk
> > 3) Watch it fail
> >
> > Thanks,
> >
> > --
> > Anish Mistry
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-hackers" in the body of the message
> >
>
> --
> Fred Clift - [EMAIL PROTECTED] -- Remember: If brute
> force doesn't work, you're just not using enough.
>
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
