Messages

1

Angstrom & OpenZaurus / qpegps with openzaurus 3.3.6-pre1

« on: August 01, 2004, 01:22:28 pm »

Additional notes if anyone is interested...

I installed the Sharp 3.10 ROM and then qpegps 0.9.1 - Same deal.. I run gpsd by hand with debug set to 3 and get all the previously mentioned "Unknown Exception" stuff.

I install OZ 3.2 and qpegps 0.9.1 - qpegps segfaults and won't run. gpsd appears to run, no different than the others there.

I'm trying various combinations, versions, etc.. In both the above cases the gpsd daemon was the one that came with qpegps. I didn't see it as part of either distribution but it is in the 3.3.5 and 3.3.6pre distributions it appears.

Oh, and "serial-modules" is a separate package in OZ 3.2  Don't know if that matters or not...

Ideas or suggestions are appreciated.. Even ones that start off "dude you're doing it all wrong, do it like this...."  

2

Angstrom & OpenZaurus / qpegps with openzaurus 3.3.6-pre1

« on: July 31, 2004, 09:00:13 am »

I realize this thread is a bit old, but...

SL5500, OZ 3.3.6Pre1

GPSD doesn't want to install because of a dependency on serial-modules. Read elsewhere that they are compiled into the kernel, so I overrode the dependeny and it installs. I run it by hand with a debug of 3 and start qpegps. In the debug window I get a lot of:

Unknown exception: "                     "Lat: 0.000000 Lon: 0.000000 Alt: 0.000000 Sat: 0 Mod: 0 Time:

Interspersed with the exact same thing but some non-ascii characters between the ""s.

I got this gpsd binary from the German site, copied it over the one in /usr/bin and get the exact same thing.

Haicom HI-303S CF GPS which acts as ttyS3 and I have made work only ONCE since purchasing it. Could not reproduce, not sure what I did then.

Since then I've installed/tried OZ 3.2, 3.3.5 and now 3.3.6Pre1. I tried the Sharp ROM, etc...

Not sure what I'm doing wrong but it sure is frustrating

GPSD is talking to the serial port, it's just like it can't decode what's coming down. Does it know about NMEA and SiRF and things like that or does it just take data from /dev/ttySx and make it available via TCP socket?

I start it with debug of 3 in one shell and try "statserial" in another. All lines low. "stty -a </dev/ttyS3" hangs at this point, the port isn't _open_. So I telnet localhost:2947 and then statserial will show me a bunch of pins high and the stty shows 4800bps. If I type "help" in the telnet window I see GPSD returned. In the shell window with gpsd running in debug mode plenty of the above errors.. I kill the telnet and run qpegps which appears to be fine with the running gpsd but doesn't work. The "gpsd" icon flashes between Green OK and Red ERR continuously. Like it can't decypher the data coming off the card either.

It's like the baud rate is wrong but I know the device is supposed to operate at 4800 and I've seen and confirmed this with stty -a < /dev/ttyS3    (I know serial comms, have installed/troubleshot hundreds of serial terminals and printers and can quote the pins of a serial DB25 from memory)

The more I look at it and think about it, the serial-modules dependency issue starts to smell fishy. Serial data is getting "scrambled" between point A and point B somehow it appears and it's the only thing I can think of. There's no cable to be pinned wrong or anything like that, so...

All I know is it's frustrating. I'm leaving for a trip in an hour and kind of wanted to play with/use the GPS on the way... Oh well, maybe next time

Thanks in advance!