Short guide how to run gllin with chroot

Ken Yale kyale at broadcom.com
Mon Sep 17 20:18:02 CEST 2007


Hello,
 
I sent a GLLIN rebuilt for the 2007.2 toolchain to Mickey, and I believe
he is testing it.  To run it, you'll need a named pipe /tmp/nmeaNP
unless you specifically disable named pipes with the -np option.  I
believe Sean and Broadcom legal folks are straightening out the SLA/EULA
for the GLLIN and OMGUI.
 
About these exceptions:
1)  src/hal_linux_tt.c:1043: glcb_ExceptionAssert:
        This is from a very old version of the GLLIN, and won't happen
in the 2007.2 build.
 
2)  early exit(3) in halInit()/674
        To overcome hardware problems, there is the gllin option
"-recover".
        The GLLIN will perform an early "exit(3);" call after this
recovery.
        It toggles GPIO lines to recover the GPS hardware, i.e. bring it
back to a sane state.
        In earlier GLLINs, this might have been one of the low-level
tests or training sequences with slighty different wording, and your
GLLIN operation instructions might have performed this step each time
you start the GLLIN as a safety measure.  This means that you'll always
have a cold start, so it is not encouraged for good GPS performance.
 
Best regards,
Ken Yale
 



________________________________

From: Bartlomiej Zdanowski [mailto:b.zdanowski at autoguard.pl] 
Sent: Sunday, September 16, 2007 22:51
To: Shawn Rutledge; List for OpenMoko community discussion
Subject: Re: Short guide how to run gllin with chroot


Hello.

Shawn Rutledge pisze: 

	Thanks, it's a convenient package.
	
	But I'm getting an error from gllin:
	  

	test_cmd_receive_count = 22
	gllin:  early exit(3) in halInit()/674
	gllin: -periodic[9] 1
	gllin: ../../../src/hal_linux_tt.c:1043: glcb_ExceptionAssert:
	Assertion `0' failed.

I've updated my article. What happens with gllin I can't excuse but
gllin is still working. Just invoke
tail -f /home/root/gps.txt
and you'll see new data incoming. This is the proof that gllin still
works. If you don't see new data there's a problem. First of all update
you Openmoko to latest release (especially to 2007.2 if you still have
2007.1). Check if it helps.

Best regards,


-- 
Bartlomiej Zdanowski
Programmer
Product Research & Development Department
AutoGuard S.A.

Place of registration: Regional Court for the Capital City of Warsaw
Registration no.: 0000287629
Share capital: 1 059 000 PLN
Polish VAT and tax ID no.: PL1132219747
Omulewska 27 street
04-128 Warsaw
Poland
phone +48 22 611 69 23
www.autoguard.pl

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/community/attachments/20070917/0bd017eb/attachment.htm 


More information about the community mailing list