Re: [gpsd-users] Non functional SiRF

[Dominic Amann]

On 8 May 2018 at 15:49, Gary E. Miller <address@hidden> wrote:
>
> I happen to know people sucessfully using 3.17 with Yocto.  If you can
> send us the error log it can be fixed.

I think I am now one step beyond the last build failure:

Log data follows:
| DEBUG: Executing shell function do_compile
| scons: Reading SConscript files ...
| TypeError: expected a character buffer object:
|   File 
"/home/SENSOFT/damann/workspace/yocto/directfb-build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gpsd/3.17-r0/gpsd-3.17/SConstruct",
line 79:
|     from distutils import sysconfig
|   File 
"/home/SENSOFT/damann/workspace/yocto/directfb-build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/distutils/sysconfig.py",
line 22:
|     PREFIX = os.path.normpath(sys.prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
| ERROR: scons build execution failed.
| WARNING: 
/home/SENSOFT/damann/workspace/yocto/directfb-build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gpsd/3.17-r0/temp/run.do_compile.26165:1
exit 1 from
|   exit 1
| ERROR: Function failed: do_compile (log file is located at
/home/SENSOFT/damann/workspace/yocto/directfb-build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gpsd/3.17-r0/temp/log.do_compile.26165)
ERROR: Task 948
(/home/SENSOFT/damann/workspace/yocto/sources/meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd_3.17.bb,
do_compile) failed with exit code '1'


> Ouch.  Can you just capture the serial somehow?  The nice thing about
> gpspipe is it captures exactly what gpsd is seeing after it reconfigures
> your GPS.

Here is some of it piped through od -x
0000000 a2a0 3200 015c 0000 0000 0000 0000 0000
0000020 0000 0000 0000 0000 0000 0000 0000 0000
0000040 0000 d25d 3abd 0000 0000 0000 0000 0000
0000060 0000 0000 2915 c102 b3b0 a2a0 5b00 0029
0000100 0200 0704 12d0 6e09 0780 05e2 0c09 2703
0000120 d310 8260 1a04 ca01 d0fd 3888 00d3 2800
0000140 00b0 3600 1565 0000 9581 0000 0000 0000
0000160 0000 5103 0000 a404 0000 0000 0200 6602
0000200 3306 0000 0000 1b00 b6e8 0000 0000 0000
0000220 0d00 0000 0000 040a 0f08 b063 a0b3 00a2
0000240 43c6 0710 12d0 6e09 007f 420f 0003 0200
0000260 2101 001c 0d1f 03f9 0023 00c1 8400 00ad
0000300 020e 02ce 00e6 0000 0000 0000 0a16 01f1
0000320 00e0 00fa 8600 00ad 0420 0126 00cf 009b
0000340 8600 00ad 071a 0108 0181 0012 8200 00bf
0000360 0219 010a 0060 00d5 8400 00ad 0c03 0103
0000400 004b 00c9 8400 00ad 0710 007c 0068 0099
0000420 8400 00ad 0a01 0061 0062 0000 0000 0000
0000440 031d 00ad 0156 003a 8200 00bf 060a 0065
0000460 0047 00f6 8200 00ad 0b17 009d 0039 00e9
0000500 8600 00ad 09c1 02a9 0041 0000 0000 0000
0000520 0b04 0097 0051 0000 0000 0000 0912 007c
0000540 0021 0082 0000 26ac b06d a0b3 00a2 43c6


>
>> > You might also try using gpsctl to put the GPS into NMEA mode and
>> > then start gpsd with the -b flag so it does not overwrite your GPS
>> > settings.
>> >

Yes, and each subsequent time I turn off my gps, and then turn it back
on again, it seems gpsd re-acquires it and turns it into binary mode.

>
> One way to improve things is to only compile gpsd with the drivers that
> you need.  The way gpsd gets lost is when it can't figure out which driver
> the GPS needs.  TSIP is especially nasty and grabby.
>

It seems to pick the SiRF driver every time - which ought to be
correct. It just can't grok this chips' output.

-- 


It is not because things are difficult that we dare not venture. It is
because we dare not venture that they are difficult - Seneca.

Dominic Amann
M 416-270-4587