LIV4 firmware update with GSV frame error ?

[charliecortassa]

hi everybody,

i have some issue with the last update of the firmware for the liv4 4.6.3 : FreeRTOS V10.4.3_ARM , BINIMG_4.6.3_ARM, SWCFG_8606532, GNSSLIB_00000000_ARM

actually, i have configure the mode for GPS only constellation and RMC+ GSV frame only,

On my GSV message i don't have the SIgnal ID anymore, so the gsv is cut in 2 sequence of frame, i can't use it like that:

$$GPGSV,2,1,08,25,80,332,54,12,55,064,,32,41,253,52,28,36,305,53*77 -> the L1 I receve
$$GPGSV,2,2,08,11,24,079,53,24,18,136,54,06,17,042,52,14,17,042,*71
$$GPGSV,1,1,04,25,80,332,,32,41,253,,24,18,136,,06,17,042,*7D -> the L5 i receve

i don't have seen a config of register in the um3009-teseoliv4f-gnss-module--software-manual-stmicroelectronics.pdf,

maybe a new register is to be defined is to configure for set the band on my frame ? 

Can i have a release note for the firmware ?,actually is not maintened on the website 

Can i have acess to older firmware ? i found only the last on the website 

maybe it's a problem of NMEA standard ?

[GalaxyQuest]

Hi,

Could you please make sure for LIV4F, you are using NMEA 4.1 in Teseo Suite?

Secondly, NMEA standard stipulates certain message length. Since GSV is part of NMEA standard, it is necessary to split the message into multiple lines as shown below.

Could you please elaborate what you mean by "framing error"?

I see that the GSV lines have the appropriate delimiters, however, I noticed that in the data you had provided there seems to be missing data between 064 and 32. Is that what you refer to as framing error?

$$GPGSV,2,1,08,25,80,332,54,12,55,064,,32,41,253,52,28,36,305,53*77 -> the L1 I receve

What baud-rate are you running? 

What is your update rate?

[charliecortassa]

Hi, 

ty for your reply,

my teseo is NEMEA 4.1 and using a 9600 baudrate when using the RS port and the data transmit to I2C Bus is the same

the problem is that when I have changed the firmware, the frame wasn't at the same format -> it's missing the Signal ID that refering the Bandwith use , it's normaly in the Nmea 4.11 standard :

before 

$$GPGSV,3,1,11,25,80,333,52,12,55,064,,32,41,253,52,28,36,305,53,1*64 -> 1 means L1
$$GPGSV,3,2,11,11,24,079,51,24,18,136,24,06,17,042,51,,,,,1*56 -> 1 means L1
$$GPGSV,3,3,11,25,80,333,62,32,41,253,,24,18,136,63,06,17,042,62,8*69 -> 8 means L5

after 

$$GPGSV,2,1,08,25,80,332,54,12,55,064,,32,41,253,52,28,36,305,53*77 -> the L1 I receve
$$GPGSV,2,2,08,11,24,079,53,24,18,136,54,06,17,042,52,14,17,042,*71
$$GPGSV,1,1,04,25,80,332,,32,41,253,,24,18,136,,06,17,042,*7D -> the L5 i receve

Here a definition for signal ID (from gpsd man) :

the teseo picture before the update  : 

With new firmware, bagraph doesn't work.

Also, I have test have using $PSTMRF frame but doesn't like to work too.

Can i have acces to old firmware for my test ? 

Can i have a release note for the firmware ? 

or a config register whith new firmware who response to my need ?

[GalaxyQuest]

Hi Charlie,

I will message you directly and provide you with an older version of f/w.