Request for Debugging Support: Teseo-LIV3FL GNSS Integration on OpenQ 8550 SOM via UART

[SM2025]

Hi,

We are currently working on integrating software support for the Teseo-LIV3FL GNSS module (specifically, the PNT-SG3FS part) on our OpenQ 8550 SOM Development Kit (https://www.lantronix.com/products/open-q-8550cs-som-development-kit/).

The GNSS module interfaces with the 8550 development kit via UART. We have updated the relevant DTSI files in our platform and verified that UART TX/RX communication is functioning correctly. However, when attempting to read the data from the GNSS module, the output appears to be unstructured or junk data. It also seems that the module is not acquiring a satellite fix. Here's a sample of the output we're observing:

# microcom -s 9600 /dev/ttyHS5
$PSTMVER,GNSSLIB_8.4.18.25_CP_ARM*07
$GPTXT,DEFAULT LIV3FL CONFIGURATION*12
$PSTMVER,OS20LIB_4.4.0_ARM*40
$PSTMVER,GPSAPP_2.11.0.1_CP_LIV3FL_ARM*48
$PSTMVER,BINIMG_4.6.15.1_CP_LIV3FL_ARM*4F
$PSTMVER,SWCFG_8306532d*33
$PSTMVER,STAGPSLIB_6.0.0_ARM*5A
$PSTMVER,STA8090_822bc043*61
$GPTXT,(C)2000-2018 ST Microelectronics*29
$GPTXT,DEFAULT LIV3FL CONFIGURATION*12
$PSTMSWCONFIG,1,0,12,000205f105070a0a0e0d0c0b0a090608070203630e110c04180c0155030110500f00000f071402050a40ffffffffffffffffffffffffffffffffffffffffffff*1E
$PSTMSWCONFIG,1,1,12,ffffffffffffffffffffffffffffffffffffffffffffffffffff010101000001094005ffffffffff5c1663095600980000000000000000000000000000000000*40
$PSTMSWCONFIG,1,2,12,ffffffff00010000ffffffff000000000000000000000000ffffffff000100000019000000000000fffffffffffffffffffffffffffffffff090c02b05282000*4D
$PSTMSWCONFIG,1,3,12,01323200050358020a0a0000fe03000010f083340d040104000002000000000000000000560098000000020000000000000000000000000000000000ac07730d*44
$PSTMSWCONFIG,1,4,12,120000009a106464ae6184002f0001000000000000000000000000000a00000007000000ffffffff050000000100000015000000b004780503000000f0c3f7ff*4C
$PSTMSWCONFIG,1,5,12,00000000ffffffff000000000c0a00020fb4a005f5a30000010a1900330a0a1400510000810e003300001810000008000e01000000000000020f000000000000*43
$PSTMSWCONFIG,1,6,12,0000e803ffffffff0610000080ba8c014810c703ffffffff9abed2e6edf2fafb0000020205060101ff00ff00ff00ff00ff00ff00ff00ff0000000000ffffffff*4D
$PSTMSWCONFIG,1,7,12,0000000000000000000000000000e03f0000000000000000000000000000f03fd3872ea86f754440938c9c853d8d2c403db83b6bb71b56404b0484b86d3da53e*40
$PSTMSWCONFIG,1,8,12,0cb8df888b2f9c3e2b69a4292b1b503e0cb8df888b2f9c3e4b0484b86d3da53e000000000000000000000000000000005feffe78af8e44406c21c84109c32b40*4B
$PSTMSWCONFIG,1,9,12,00000000000024401d8f19a88c8f4440598b4f0130be2b4000000000000024407ac2120f289f44402315c616828c2b400000000000002440ace28dcc239f4440*11
$PSTMSWCONFIG,1,10,12,95826e2f698c2b4000000000000024400f0c0c120f0c0c120f0c0c120f0c0c1244454641554c54204c495633464c20434f4e46494755524154494f4e00000000*7D
$PSTMSWCONFIG,1,11,12,00000000000000000000000000000000000000000000000000000000000000000000000000000000*26
$GPRMC,235942.990,V,0000.00000,N,00000.00000,E,,,020917,,,N*70
$GPGGA,235942.990,0000.00000,N,00000.00000,E,0,00,99.0,100.00,M,0.0,M,,*67
$GPVTG,,T,,M,,N,,K,N*2C
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GPGLL,0000.00000,N,00000.00000,E,235942.990,V,N*4A
$PSTMCFG,LMS,1,0,0,50.0,50.0,05,03,60.0,0.000000,0.000000,-2.671600*12
$PSTMCPU,32.18,-1,98*4B
$GPRMC,235944.000,V,0000.00000,N,00000.00000,E,,,020917,,,N*76
$GPGGA,235944.000,0000.00000,N,00000.00000,E,0,00,99.0,100.00,M,0.0,M,,*61
$GPVTG,,T,,M,,N,,K,N*2C
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GPGLL,0000.00000,N,00000.00000,E,235944.000,V,N*4C

The SYS_RSTn and Wake-up pins are enabled, and we have confirmed that VCC is drawing 3.3V and VCC_IO is at 1.8V.

Could you please advise on how we can further debug or resolve this issue?

[Karl Yamashita · Accepted solution]

Off the bat, you have no Lon/Lat values and also show V when it should be A. Time shows it's 2017 so it hasn't been updated. Until you get a lock onto some satellites, you're not going to get much valid data.

$GPRMC,235942.990,V,0000.00000,N,00000.00000,E,,,020917,,,N*70

Edit: I plugged in the time into a wrong conversion which indicated 2017, but that is not the case.

[SM2025]

Thanks for your response, @Karl Yamashita 

We connected an external GNSS simulator (Spirent GSS6300M) and initially received output that matched the simulator’s configuration.

However, after that initial success, the data no longer updates regardless of the configuration changes we make. Even when we disconnect the antenna from the EVK (which was connected to the simulator), the LAT/LONG data remains the same. Rebooting or resetting the device also has no effect.

Could this be a bug, or is there a known issue? We would appreciate your assistance in resolving this.

Here's the output.
/ # microcom -s 9600 /dev/ttyHS5
$PSTMVER,GNSSLIB_8.4.18.25_CP_ARM*07
$GPTXT,DEFAULT LIV3FL CONFIGURATION*12
$PSTMVER,OS20LIB_4.4.0_ARM*40
$PSTMVER,GPSAPP_2.11.0.1_CP_LIV3FL_ARM*48
$PSTMVER,BINIMG_4.6.15.1_CP_LIV3FL_ARM*4F
$PSTMVER,SWCFG_8306532d*33
$PSTMVER,STAGPSLIB_6.0.0_ARM*5A
$PSTMVER,STA8090_822bc043*61
$GPTXT,(C)2000-2018 ST Microelectronics*29
$GPTXT,DEFAULT LIV3FL CONFIGURATION*12
$PSTMSWCONFIG,1,0,12,000205f105070a0a0e0d0c0b0a090608070203630e110c04180c0155030110500f00000f071402050a40ffffffffffffffffffffffffffffffffffffffffffff*1E
$PSTMSWCONFIG,1,1,12,ffffffffffffffffffffffffffffffffffffffffffffffffffff010101000001094005ffffffffff5c1663095600980000000000000000000000000000000000*40
$PSTMSWCONFIG,1,2,12,ffffffff00010000ffffffff000000000000000000000000ffffffff000100000019000000000000fffffffffffffffffffffffffffffffff090c02b05282000*4D
$PSTMSWCONFIG,1,3,12,01323200050358020a0a0000fe03000010f083340d040104000002000000000000000000560098000000020000000000000000000000000000000000ac07730d*44
$PSTMSWCONFIG,1,4,12,120000009a106464ae6184002f0001000000000000000000000000000a00000007000000ffffffff050000000100000015000000b004780503000000f0c3f7ff*4C
$PSTMSWCONFIG,1,5,12,00000000ffffffff000000000c0a00020fb4a005f5a30000010a1900330a0a1400510000810e003300001810000008000e01000000000000020f000000000000*43
$PSTMSWCONFIG,1,6,12,0000e803ffffffff0610000080ba8c014810c703ffffffff9abed2e6edf2fafb0000020205060101ff00ff00ff00ff00ff00ff00ff00ff0000000000ffffffff*4D
$PSTMSWCONFIG,1,7,12,0000000000000000000000000000e03f0000000000000000000000000000f03fd3872ea86f754440938c9c853d8d2c403db83b6bb71b56404b0484b86d3da53e*40
$PSTMSWCONFIG,1,8,12,0cb8df888b2f9c3e2b69a4292b1b503e0cb8df888b2f9c3e4b0484b86d3da53e000000000000000000000000000000005feffe78af8e44406c21c84109c32b40*4B
$PSTMSWCONFIG,1,9,12,00000000000024401d8f19a88c8f4440598b4f0130be2b4000000000000024407ac2120f289f44402315c616828c2b400000000000002440ace28dcc239f4440*11
$PSTMSWCONFIG,1,10,12,95826e2f698c2b4000000000000024400f0c0c120f0c0c120f0c0c120f0c0c1244454641554c54204c495633464c20434f4e46494755524154494f4e00000000*7D
$PSTMSWCONFIG,1,11,12,00000000000000000000000000000000000000000000000000000000000000000000000000000000*26
$GPRMC,000237.100,V,3859.99441,N,11613.98111,E,,,120232,,,N*73
$GPGGA,000237.100,3859.99441,N,11613.98111,E,0,00,99.0,-35.18,M,0.0,M,,*7A
$GPVTG,,T,,M,,N,,K,N*2C
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GPGLL,3859.99441,N,11613.98111,E,000237.100,V,N*44
$PSTMCFG,LMS,1,0,0,50.0,50.0,05,03,60.0,0.000000,0.000000,-2.671600*12
$PSTMCPU,100.00,-1,98*72
$GPRMC,000238.000,V,3859.99441,N,11613.98111,E,,,120232,,,N*7D
$GPGGA,000238.000,3859.99441,N,11613.98111,E,0,00,99.0,-35.18,M,0.0,M,,*74
$GPVTG,,T,,M,,N,,K,N*2C
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GPGLL,3859.99441,N,11613.98111,E,000238.000,V,N*4A
$PSTMCPU,100.00,-1,98*72
$GPRMC,000239.000,V,3859.99441,N,11613.98111,E,,,120232,,,N*7C
$GPGGA,000239.000,3859.99441,N,11613.98111,E,0,00,99.0,-35.18,M,0.0,M,,*75
$GPVTG,,T,,M,,N,,K,N*2C
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GPGLL,3859.99441,N,11613.98111,E,000239.000,V,N*4B
$PSTMCPU,100.00,-1,98*72
$GPRMC,000240.000,V,3859.99441,N,11613.98111,E,,,120232,,,N*72
$GPGGA,000240.000,3859.99441,N,11613.98111,E,0,00,99.0,-35.18,M,0.0,M,,*7B
$GPVTG,,T,,M,,N,,K,N*2C
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GPGLL,3859.99441,N,11613.98111,E,000240.000,V,N*45
$PSTMCPU,100.00,-1,98*72
$GPRMC,000241.000,V,3859.99441,N,11613.98111,E,,,120232,,,N*73
$GPGGA,000241.000,3859.99441,N,11613.98111,E,0,00,99.0,-35.18,M,0.0,M,,*7A
$GPVTG,,T,,M,,N,,K,N*2C
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GNGSA,A,1,,,,,,,,,,,,,99.0,99.0,99.0*1E
$GPGLL,3859.99441,N,11613.98111,E,000241.000,V,N*44
$PSTMCPU,97.54,-1,98*4C

[Tesla DeLorean]

Who is Lantronix's contact person at ST Micro? You should probably determine that first, perhaps via purchasing.

Determine who is the FAE responsible for your account.

Open an online support request  https://ols.st.com/s/

GPS/GNSS devices don't like going back in time, or non-linear progression of time. If using simulators always COLD start a receiver in a way that clears all RTC, EEPROM or NVRAM data

[SM2025]

We got the GNSS module working and also got in touch with Lantronix's contact person at ST Micro. Thanks for your help. This thread can be closed.