Teseo-LIV4F broken NMEA

[Joost123]

We recently had a batch of equipment assembled with the Teseo-LIV4F instead of LIV3, and I'm running into some real strange behaviour.

Whenever I try to disable the GPGSV frame the whole NMEA output breaks. It is not a problem with the receiving host as I have verified with an oscilloscope that the broken NMEA is really outputted by the LIV4F.

Commands I send:

$PSTMSETPAR,1201,0x4,2*7B
$PSTMSAVEPAR*58
$PSTMSRR*49

And the output starts to be like: (See concatinated GBS and GSV, the checksum and new line on GBS is missing)

$GNGBS,,,,,,,,,,,,,,,$GNRMC,,V,,,,,,,,,,N,V*37
$GNGGA,,,,,,0,00,0.0,,M,,M,,*56
$GNVTG,,T,,M,,N,,K,N*32
$GNGST,,,,,,,,*49
$GNGBS,,,1,01,25,,,39$BDGSV,1,1,01,25,,,39,,,,,,,,,,,,,1*79
$GNRMC,,V,,,,,,,,,,N,V*37
$GNGGA,,,,,,0,00,0.0,,M,,M,,*56
$GNVTG,,T,,M,,N,,K,N*32
$GNGST,,,,,,,,*49
$GNGBS,,,1,01,25,,,37$BDGSV,1,1,01,25,,,37,,,,,,,,,,,,,1*77
$GNRMC,,V,,,,,,,,,,N,V*37
$GNGGA,,,,,,0,00,0.0,,M,,M,,*56
$GNVTG,,T,,M,,N,,K,N*32
$GNGST,,,,,,,,*49

Enabling / Disabling different frames caused different types of broken output (missing identifiers or checksums). The frames seem to break in the same way for every output cycle.

In above example the output will work like normal again after re-enabling GPGSV:

$PSTMSETPAR,1201,0x4,1*78
$PSTMSAVEPAR*58
$PSTMSRR*49

Does anyone recognize this behaviour?
Reflashing firmware does not help (It makes the device work like expected again until I disable some frametypes)

I tested on 4.6.8.5.11 and 4.6.8.5.10:

$PSTMVER,FreeRTOS_V10.4.3_ARM*57
$PSTMVER,BINIMG_STA8041_4.6.8.5.11_ARM*34
$PSTMVER,SWCFG_86065331*62
$GPTXT,DEFAULT PVT CONFIGURATION*2A
$PSTMSWCONFIG,1,0,12,00000af005070a0a0e0d0c0b0a090608070203630e110404180c0155030000500fffff0f0714000affffffffffffffffffffffffffffffffffffffffffffffff*1D
$PSTMSWCONFIG,1,1,12,ffffffffffffffffffffffffffffffffffffffffffffffffffff010101000001094005ffffffffff449641095f53884000000000000000000000000000000000*4D
$PSTMSWCONFIG,1,2,12,ffffffff00000000ffffffff000000000000000000000000ffffffff000100000019000000000000ffffffffffffffffffffffffffffffff0000120005282000*13
$PSTMSWCONFIG,1,3,12,01323200050358020a0a0000fe03000010f08334d50300a42023c07e00000000000000005f5388402023c07e0000000000000000000000000000000012090000*1A
$PSTMSWCONFIG,1,4,12,120000009a106464ae618400000001000000000000000000000000000000000006000000ffffffff040000000100000000000080b004780503000000f0c3f7ff*45
$PSTMSWCONFIG,1,5,12,00000000ffffffff000000000c0a00020fb4a005f5310000010a1900330a0a1400510000810e000000001810000008000e01000000000000020f000000000000*13
$PSTMSWCONFIG,1,6,12,0000e803ffffffff0610000080ba8c014810c703ffffffff9abed2e6edf2fafb0000020205060101ff00ff00ff00ff00ff000000ff00ff000000000000000000*4D
$PSTMSWCONFIG,1,7,12,9a9999999999b93f000000000000e03f0000000000000000000000000000f03f4bc431896f754440f0f67e923d8d2c408c65456bb71b56404b0484b86d3da53e*1E
$PSTMSWCONFIG,1,8,12,0cb8df888b2f9c3e2b69a4292b1b503e0cb8df888b2f9c3e4b0484b86d3da53e000000000000000000000000000000005feffe78af8e44406c21c84109c32b40*4B
$PSTMSWCONFIG,1,9,12,00000000000024401d8f19a88c8f4440598b4f0130be2b4000000000000024407ac2120f289f44402315c616828c2b400000000000002440ace28dcc239f4440*11
$PSTMSWCONFIG,1,10,12,95826e2f698c2b4000000000000024400f0c0c120f0c0c120f0c0c120f0c0c1244454641554c542050565420434f4e46494755524154494f4e00000000000000*76
$PSTMSWCONFIG,1,11,12,00000000000000000000000000000000000000000000000000000000000000000000000000000000*26
$GNRMC,,V,,,,,,,,,,N,V*37
$GNGGA,,,,,,0,00,0.0,,M,,M,,*56
$GNVTG,,T,,M,,N,,K,N*32
$GNGST,,,,,,,,*49
$GNGBS,,,,,,,,,,*5F
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,1*33
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,3*31
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,4*36
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,1*33
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,3*31
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,4*36
$GNRMC,,V,,,,,,,,,,N,V*37
$GNGGA,,,,,,0,00,0.0,,M,,M,,*56
$GNVTG,,T,,M,,N,,K,N*32
$GNGST,,,,,,,,*49
$GNGBS,,,,,,,,,,*5F
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,1*33
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,3*31
$GNGSA,A,1,,,,,,,,,,,,,0.0,0.0,0.0,4*36

On the LIV3 devices all worked like expected.

Regards, help much apreciated.

[GalaxyQuest]

Hi @jori Can you please let me know what settings did you change that was reverted to the factory setting?

Just out of curiosity, when you made the changes to update the CDB, I am guessing you read back the CDB location to make sure, the setting was updated correctly, didn't you?

[jori]

First I updated the GPS modules with firmware STA8041_LIV4F_PVT_STD_4_6_8_5_11_UPG,
then, using Teseo-Suite Pro v7.5.3.1, I changed these settings:

102 -> C - NMEA port baud rate to 460800,

303 -> 0.2 - GNSS fix rate to 0.2

The devices have been working for a few weeks. There is no way I messed up the settings, the serial port of the microcontroller that communicates with the GPS module is set to 460800. The only way to receive messages from the GPS module is for its serial port to be at the same speed.In fact, that's exactly how it was recognized that there was a problem. When the device started up, not a single satellite was visible on the display. After several restarts, the situation repeated itself and the device was replaced with another one.