Teseo-LIV4 GNSS Firmware Update CRC Error

[JCharette]

I'm attempting to update the firmware for the LIV4 GNSS module, and everything seems to goes well until the CRC step, where it hangs for a few seconds then reports a failure. The module is no longer publishing any data, but when using the 'recovery' method for firmware updating, the module does communicate with Teseo_Suite, but it stops responding on the CRC step.  I'm using an FTDI and can see both RX and TX LEDs illuminate during the process,  but neither light up during the CRC step.  Any help with this would be greatly appreciated.

Thanks in advance, 

-Jake

[JCharette]

Thank you George, I very much appreciate you helping me fix the mess I created!

[edenariel]

Hi @GalaxyQuest – I'm in the same position as @JCharette , I've been testing the LIV4F using an X-STM32MP-GNSS2, and it kept shutting down unexpectedly after a few hours so I tried to update the firmware but I couldn't get Teseo-Suite to work – the firmware update function gave a DLL error. I've since resolved this (if anyone encounters this – you need to install the correct Visual C++ runtime), but updating doesn't work nor does it get me out of the state that attempting to use the Java updater left me in where it doesn't start or respond, and I get a CRC error when attempting to flash it in Teseo-Suite.

What do I need to do to recover from this state? Thank you very much for your help!

CC: @Francesco Virlinzi who I met at Embedded World yesterday – he asked me to email him, but I found this thread so thought it better to ask here instead since someone already had this fixed for them!

[GalaxyQuest]

Hi,

Just to clarify your situation with @JCharette , I am assuming you got into the case of LIV4F shutting down because of using Firmware update utility in X-CUBE-GNSS1 folder, can you please confirm?

For @JCharette I tried to use a Flashing tool used for LIV3 but that did not work either.

Let me check with @Francesco Virlinzi and see if we have a procedure to "unbrick" this device.

[edenariel]

Thanks @GalaxyQuest – that's exactly what happened! At the point I talked to @Francesco Virlinzi at Embedded World I didn't actually know that it would fail even after flashing correctly with Teseo Suite – I used the other tool specifically because Teseo Suite was giving me a DLL error. I managed to resolve that yesterday, but then I ended up in the CRC Error position @JCharette got into.

Because it can respond in recovery mode, it seems there must be some way to restore this thing – at least I hope there is! Thank you for your help!

[JCharette]

I was unfortunately unable to recover my module from that state, but it was some time ago, so maybe things have changed.  A friendly support person worked with me for a bit back then, but to no avail.  I'm a linux user, which is why I could not use TeseoSuite, but I did end up writing a python script to successfully handle flashing.  It's for the liv4, but may offer some insights for your module. I attached it as a text file. Good luck!

[GalaxyQuest]

Thanks @JCharette . I chatted with you, unfortunately @edenariel would need help from the product team to give you a special script (if they can identify the exact cause of issue).

Let me connect with @Francesco Virlinzi and get back to you.

[edenariel]

Thank you very much @GalaxyQuest