Likes: 
Reply With QuoteProbably you misunderstood me just a tad there about what clearing nv would likely achieve. I didn't mean it would change anything in regard to a possible boot problem linked to your non-kosher usb setup, i was suggesting that if there is some corruption of nonvol memory which was preventing the unit updating from gupdate.gcd it maybe would correct by clearing nv. But of course you then need to actually re-attempt the upgrade which is what i was meaning by: 'your risk so your call'. Clearing nv in itself is virtually without risk and can only potentially benefit the unit.
That said, i do agree that it's best to leave it alone and don't risk the update. It may function fine until kingdom come as it is. Once you get used to updating the maps and files from the card it's quite easy. I have two like that as i said in the other thread, but fortunately i can update firmware np in them. Thanks for your patience, sorry we haven't been able to achieve very much for you. Cheers.
Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 11 to 12 of 12
-
25th February 2015, 06:27 AM #11Junior Member
- Join Date
- Feb 2015
- Location
- Canada
- Posts
- 8
- Rep Power
- 0
I did a "Clear Nonvol" and "Erase all user data" but that didn't change the boot process (but did no harm either).
I then used a variable resistor to change the voltage on the ID pin to see if I could get it to go into the normal power-connected boot mode where the green progress bar goes across the screen under the Garmin logo. When the "USB ID Volts" was below 2.43 the green progress bar did not appear and it went straight from the Garmin logo to the Nuvi copyright page (same as when the ID pin is grounded). When the USB ID voltage as above 2.48 it showed a green progress bar under the Garmin logo for a few seconds which was interrupted by the "waiting for computer" icon (same as leaving the ID pin open). So I suspect that there is no ID pin voltage that will cause the Nuvi go through its boot process without waiting for a USB connection. Perhaps the Garmin power supplies short the USB data pins in addition to having a pull-down resistor on the ID pin. That's something I can't do since the USB data pin traces were lifted off the PCB with the connector.
So... I think I'm going to declare the problem solved since the unit does everything it's supposed to and further attempts to update the firmware could just get me into more trouble.
Thanks again for all the help.
-
25th February 2015, 10:53 AM #12Garmin/GPS Systems GMod.
- Join Date
- Aug 2011
- Location
- Oz.
- Posts
- 6,335
- Rep Power
- 2502
'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
[Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].
Bookmarks