Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/21 ael <law_ence.dev@ntlworld.com>:
> I have just done another test. This because that garmin odd connector
> often fails to make proper contact. So in this case I first verified
> that I could use gpsbabel successfully with the old kernel, so
> confirming a proper connection.
>
> Then I just used
> $ gpsbabel -w -i garmin -f /dev/ttyUSB0 -o gpx -F test.gpx
> [ERROR] GPS_Packet_Read: Timeout. No data received.
> GARMIN:Can't init /dev/ttyUSB0
>
Hi ael,
I finally managed to find some time to test this on my own hardware on
2.6.38. I do not have a garmin gps, so I connect my ark3116 to a
second serial interface. I used the same gpsbabel command as you to
connect to my ark3116, and I could see data coming in on the second
port and if I sent a reply the other way, it is received by gpsbabel.
In short, everything seems to work as it should, which is not helping.
Your traces show that gpsbabel never receives anything in your case,
so somehow something is behaving different. I am running out of ideas.
Would it be possible for you to do a similar experiment with a second
serial port? That way we might learn if data actually makes it to the
serial output when sending or if data is received on the serial input
but not forwarded to the USB bus.
Another thing to try could be to use picoterm or some other terminal
program to send some characters to the gps (9600N8), to see what
happens, and then directly afterwards try the gpsbabel command again.
If the underlying problem has to do with somekind of timing mismatch,
or initialisation problem, this might help.
Thanks.
Groeten,
Bart
--
Bart Hartgers - New e-mail: bart.hartgers@gmail.com
Reply to: