Ticket #2304 (new defect)

Opened 10 years ago

Last modified 10 years ago

gllin or gps chip produces wrong time stamps

Reported by: keroami Owned by: openmoko-devel
Priority: normal Milestone:
Component: unknown Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

$ ln -s /usr/share/zoneinfo/Europe/Athens /etc/localtime
$ date
Mon Aug 17 01:38:22 EEST 2009
$ TZ=UTC date
Sun Aug 16 22:38:23 UTC 2009
$ gpspipe -r
...
$GPGGA,193856.00,0,00,*48
$GPRMC,193856.00,V
,160809*19
$GPGLL
,193859.00,V*27

That's 19:38, which is yet 3 hours from UTC in the wrong direction.
it'd be 20:38 had I used Europe/Amsterdam? and 22:38 without any /etc/localtime.

I don't know whether gllin/chip is fed the wrong time at startup to look at its satellites, or whether it is making a mistake itself.

Consequences are that otimed will use this wrong time after a while; the change can be found in /var/log/frameworkd.log at INFO level, and after the change the timestamps in that logfile used as prefix have changed.

Bye,
Kero.

gta01bv4
SHR 20090808
kernel 2.6.29-rc3
gllin 1.1

Change History

comment:1 Changed 10 years ago by lindi

I don't really wish to debug proprietary programs but maybe you should wait until you have 3D fix before you trust the timestamp?

comment:2 Changed 10 years ago by keroami

That exact remark was made by me, when I saw time set to 1st of January of some strange year (not 1970) by otimed from GPS.
That I could not reproduce, but this I could.

You suggest that when GPS gets a fix, times get right including the zone.
Unfortunately, it doesn't.

Note: See TracTickets for help on using tickets.