Thread: Garmin Map 62s "System Software Missing"

Reflash the firmware as an RGN file. Use Updater.exe in preboot mode. Usually a device showing 'System Software Missing' will default to preboot anyway.

Thank you for your reply.
I just tried what you suggested and it started to load onto the unit but then came up with the below Garmin message.

The Garmin Device has returned an error status while receiving data packets.
This could be due to a malfunction in the Garmin device or an error in this application.
If this error continues to occur, please contact Garmin Tech Support.

Do you have any other suggestions?
cheers

At it's most serious, the message "System Software Missing" can indicate physical flash damage involving the region containing the firmware [Garmin calls it 'system software']. Mostly it's less insidious and only means data in the firmware region [rgn14] has become corrupt or has been erased in which case that's easily fixed by reflashing.

The error message you've got from Updater.exe is concerning if you've tried multiple times to flash and have used different USB cables, different USB ports or even another PC. Note: Use only directly connected [no hub] rear USB2 ports of the PC, not USB3.

If you've tried all the above then please post a link to the firmware you're using, maybe we can try something else.

Thank you,
I didn't have any luck loading files onto the unit but found that if I squeezed it while turning it on it loaded normally.
I opened it up to check if something was loose, looked fine. It then started like it should and ran for a few minutes before shutting down to "System Software Missing" Message again. I managed to do an update using Garmin web-updater, the update loaded but the unit still shut down after some time.
Will have a bit more of a play with it soon but thinking its most likely caused by physical damage.

To get the RGN file do I create it by running the Map62s latest GCD update through a RGN tool? Or is there a RGN file available somewhere to download? Just want to make sure I'm actually doing it properly.

Yes, best to just use RGN_Tool to make an RGN from a GCD. When you name an RGN use this convention XXXX01000xxx.RGN where 'XXXX' is the firmware's HWID and 'xxx' is the software version without the period. Any other naming forces the flash and if you use the wrong firmware that can be fatal. However, it seems like there's no problem with the firmware region of the flash chip so you probably don't need to re-flash it anyway.

The fact you need to squeeze it to have it boot up sounds like some physical damage, but not flash chip damage most likely tho'. Could be a dry joint or bad connection. Good luck.