HL8548-G GPS issue : year 2000 when using SUPL

hello everyone.

I’m using a HL8548-G, and communicate with him through AT commands on UART1 port.
I get GPS data by PVT frames
I use GPS timestamp to synchronise Airprime RTS through “AT+CCLK” cmd.
I consider SUPL loaded after next GPS init.

I try to use SUPL config to make my GPS fix quicker but have some issues with this. It appears that GPS date goes to 17/07/2000, unless other GPS data (hour, geolocalisation) still Ok, when SUPL (with or without TLS) is loaded :

  • List item : 1rst case : After power supply : SUPL with TLS configurated ; 3D fix with correct Time so HL8 RTC is synchronised with AT+CCLK cmd ; then I restart HL8 ; starts GPS and its year goes to 2000.

  • List item : 2nd case : After power supply : SUPL with TLS configurated ; no 3D fix so no RTS synchronising ; then I restart HL8 ; starts GPS and its year is Ok.

  • List item : 3rd case : After power supply : SUPL without TLS configurated ; no 3D fix so no RTS synchronising ; When GPS is started, GPS directly goes to year 2000 bug.

  • List item : 3rd case : Trying back the 1rst case, I sent SUPLCFG with no TLS commands by other port (USB) while GPS already started and before a HL8 reset. After reset GPS time is Ok (2020) but it seems that SUPL didn’t success (3min for 3D GPS fix).

Does anyone as an idea or already met this kind of problem?

Best regards,

Denis Q

Here is my SUPL config with no TLS :
+GPSSUPLCFG: 0,“supl.google.com”,7276,1,0
+GPSSUPLCFG: 1,-1,1,1

1rst case selected log (SUPL with TLS) :
at+CGSN=?
OK
at+GPSSUPLCFG?
+GPSSUPLCFG: 0,“supl.google.com”,7275,1,0
+GPSSUPLCFG: 1,0,2,1
OK
at+CTZU=0
OK
+WDSI: 0
at+GPSPVT=1,5,3
OK
at+GPSCONF=10,0
OK
at+WDSS=0,“myAPN”
OK
at+WDSI=8191
OK
+SIM: 1
ats0=1
OK
+KSUP:0
at+KSLEEP=0
ok
at+KCERTSTORE?
OK
at+CCLK?
+CCLK: “04/01/01,00:01:05+00” (HL8 RTC : 00h:01m:05s:196ms Jan-01-2004 )
OK
at+CREG?
+CREG:0,2
OK
+PBREADY
at+CGDCONT=4,“IP”,“my APN”
OK
at+GPSSTART=0
OK
+GPSEVINIT: 1
+GPSEVSTART: 1
+GPSEVPOS: 0
+GPSPVT:0,00:00:00,00/00/0000,NO FIX,N 000 00’00.00",E 000 00’00.00",+0000m

+GPSPVT:0,13:34:06,27/06/2012,NO FIX,N 000 00’00.00",E 000 00’00.00",+0000m

+GPSEVPOS: 2
+GPSPVT:0,13:34:37,19/02/2020,2D FIX,N 048 51’35.52",E 002 11’02.96",-0047m
at+CCLK=“20/02/19,13:34:37+00”
OK
at+KTCPCFG?
OK
at+KCNXCFG?
OK
at+KCNXCFG=1,“GPRS”,“my APN”
OK
at+KCNXCFG?
+KCNXCFG: 1,“GPRS”,“my APN”,"","",“IPV4”,“0.0.0.0”,“0.0.0.0”,“0.0.0.0”,0
OK
at+KTCPCFG?
OK
at+KTCPCFG=1,0,“eu.airvantage.net”,8883,1
+KTCPCFG: 1
OK
at+KTCPCFG?
+KTCPCFG: 1,0,1,0,“eu.airvantage.net”,8883,3670,0,1,0
OK
at+KTCPCNX=1
OK
+KCNX_IND: 1,4,1
OK
at+KTCPSTAT=1
+KTCPSTAT: 2,-1,0,0
OK

at+KTCPSTAT=1
+KTCPSTAT: 3,-1,0,0
OK

(HL8 RTC : 13h:34m:47s:479ms Feb-19-2020 )
+GPSEVPOS: 3
+GPSPVT:0,13:34:52,19/02/2020,3D FIX,N 048 51’39.31",E 002 11’04.74",+0114m

+GPSPVT:0,14:11:59,19/02/2020,3D FIX,N 048 51’39.70",E 002 11’04.28",+0093m
at+GPSSTOP
OK
+GPSEVSTOP: 1
+GPSEVPOS: 0
OK
at+KTCPDEL=1
OK
at+KTCPSTAT=1
+KTCPSTAT: 4,-1,31,0
OK
+KTCP_NOTIF: 1,4
+KTCP_ACK: 1,0
+KCNX_IND: 1,5,30
at+CPOF
OK
at+CGSN=?
OK
at+GPSSUPLCFG?
+GPSSUPLCFG: 0,“supl.google.com”,7275,1,0
+GPSSUPLCFG: 1,0,2,1
OK
at+CTZU=0
OK
+WDSI: 0
at+GPSPVT=1,5,3
OK
at+GPSCONF=10,0
OK
at+WDSS=0,“myAPN”
OK
at+WDSI=8191
OK
+SIM: 1
ats0=1
OK
+KSUP:0
at+KSLEEP=0
ok
at+KCERTSTORE?
OK
at+CCLK?
+CCLK: “20/02/19,14:15:11+00”
OK
at+CREG?
+CREG:0,2
OK
+PBREADY
at+CGDCONT=4,“IP”,“my APN”
OK
at+GPSSTART=0
OK
+GPSEVINIT: 1
+GPSEVSTART: 1
+GPSEVPOS: 0
+GPSPVT:0,14:15:36,05/07/2000,NO FIX,N 000 00’00.00",E 000 00’00.00",-0047m

+GPSPVT:0,14:15:46,05/07/2000,3D FIX,N 048 51’38.90",E 002 11’03.35",+0073m
+GPSEVPOS: 3

Hi @dquintin,
This is known issue on HL8548-G. Module may show wrong date GNSS running with SUPL server. It only happens when SUPL is used. It will be fixed in the future. Please share if you have any concern and tick “Solution” if your question is answered
Thanks

1 Like

Ok thank you very much @Vianney.
I gonna try to build a patch for this.

Really curious that this known bug doesn’t appear on HL8 Embedded SW release note in “limitations/known bugs” … .

Hi @dquintin,
The issue was reported after Release note had been delivered so it is not there. Sorry for your inconvenience. Please share if you have any concern. Help us to tick “Solution” if your question is answered
Thanks