Quote Originally Posted by Butters View Post
After a bit of searching I've found some references to JEFF.BIN file, always regarding Drive Series devices. [...]
Thanks for informations. And thanks for your help: is very appreciate



Quote Originally Posted by Butters View Post
So for your Drive 40 attempting SD flash, Ldr.bin is being initiated but is unable to go too far and txt commands aren't being executed. When there's no files named Last_ID.bin and Update.log created in the card then the flash has failed. It seems that because this device has lost it's UID and HWID and has likely flash damage across multiple regions that it's not a candidate for recovery. Maybe it could be JTAG'ed by Garmin to reprogram the flash chip however they only offer a 'one for one' replacement service at a prohibitive price. Sorry but it might be only a candidate for parts now because it's very likely this is a hardware failure.
Is not a tragedy: is only a piece of plastic and of silicium.
But is very interesting try to understand how works this kind of dibolic devices.
Today, Garmin support propose me to repair for a cost equal to the 70% of the cost of a new device (new and better). Note that I wrote the word 'support' with the 's' in lower case...
No matter: for 20$, I bought an used Drive 40, with screen damaged: it may possible that, from 2 broken devices I obtain a working Drive (if I'm lucky)

Question 1: they are utility and documentation about jtag programming of Garmin device?
Question 2: is possible to connect a serial TTL i/f on the PCB to see something that is not a stupid message different from "SYSTEM SOFTWARE MISSING"?