GO 6200 - SD card/map error

Joined
Jul 25, 2009
Messages
2
Country
<img src="/styles/default/custom/flags/gb.png" alt="United Kingdom" /> United Kingdom
TomTom Model(s)
GO 6200
My 6200 has just done an automatic software update. Application version 24.100.001.411 (0) (26/03/2024).

My device no longer sees or can use the maps previously stored on the SD card.

When connected to MyDrive Connect the 'Memory Card' icon shows blank as if no card is installed.

When looking in the 'about' section on the 6200 it shows free space on both internal memory and memory card (card is partially full implying a map is present). If I insert a newly formatted SD card which shows in the ‘about’ section when trying to add a map I get a ‘oops Something went wrong. Please try again’ message. For a small map I’m given the option to save to memory or SD card, for a large map no option is given. I continue to get the ‘oops’ message when trying to save to the SD card.

I have done a device reset but this has not resolved the issue.

Any help and advice appreciated.
 
Nothing you can do for it if you're unlucky enough to be in this situation, but TomTom is aware of it - ticket open.
From time to time, remind me to poke them about bug # DPND-13670 and we'll see if they are making any progress.
 
Nothing you can do for it if you're unlucky enough to be in this situation, but TomTom is aware of it - ticket open.
From time to time, remind me to poke them about bug # DPND-13670 and we'll see if they are making any progress.
Thanks for your advice. I've raised a ticket with tomtom and will update when progress is made.
 
Last edited:
Glad I found this thread, I thought it was just me! Exact same issue/behaviour but on Go Premium X. Unfortunately I was on holiday in USA when the update occurred & my (relied-upon) USA map was on the SD card. Luckily I had enough space on internal memory to download a smaller version of the map or I would have been scr**ed! I have also raised a support ticket.
 
I will latch on to this thread. Same here with the Go Premium X. Second time an update has screwed me with the mydrive connected thing also.
 
I'm afraid the issue persists with the 24.101.0002 build and the team is still looking into what's causing the memory card not being recognised.
 
I have the same problem, why do TOMTOM not have known bugs on their release notes?
 
Last edited:
I have the same problem, why do TOMTOM not have known bugs on their release notes?
Granted, that might be nice, but almost no company does this. That said, it's only possible if you KNOW you have a particular bug - which in this case, they didn't until it was already released. Stay tuned for 24.101.0003. No idea what the release date for that will be, but we're advised that TomTom has taken this up as a priority.
 
Granted, that might be nice, but almost no company does this. That said, it's only possible if you KNOW you have a particular bug - which in this case, they didn't until it was already released. Stay tuned for 24.101.0003. No idea what the release date for that will be, but we're advised that TomTom has taken this up as a priority.
I do not agree. Most of the software products I use at work have 'known issues' in their release notes. f.eks redhat : https://access.redhat.com/node/2385911/release-notes-and-known-issues

Here is a quote from a website on how to write release notes:

Reasons to have a list of known issues:

  • Issue may never be fixed, because newer major version of software is going to be released. That newer version may be incompatible with previous one, so some users may stuck with older version for some time (may be forever).
  • You can save the time of your customers, because they're no longer have to discover and examine defects themselves, probably writing bug reports.
  • You can reduce your customer's irritation caused by encountering defects by providing a description of defects and a way to avoid/mitigate them.
  • You make yourself a good reputation: you care about your product and your users.
As for citations from books on management or standards, I've never seen one.

Important exceptions:


  • Defects that imply some security risks. You should not give any information about vulnerabilities to potential attackers. Instead, you should fix such security-related defects ASAP.

I did read the relasenotes before upgrading my TomTom. If I have known that I was going to lose all the maps on my SD card, I would have waited.
 
I do not agree.
Open source software products vs. proprietary firmware products. Apples / Oranges. Would be curious what other devices you own that provide open bug lists in their release notes, if there are any release notes at all. For example, my Samsung TV gets occasional firmware updates, but I've never seen any bug lists, and don't expect to in the future.

You can read all of the TomTom release notes you like, but the bug being dealt with in this thread was unknown at the time of release, so without a crystal ball, they couldn't have reported it anyway. This bug was severe enough that had they known of it, they would have waited, too. They do occasionally run up against what they call 'blockers' to release.
 
Well here's the predictable response from support on my ticket - "please factory reset the device" LOL. I don't think that will help with a bug :)
 
My 6200 has just done an automatic software update. Application version 24.100.001.411 (0) (26/03/2024).

My device no longer sees or can use the maps previously stored on the SD card.

When connected to MyDrive Connect the 'Memory Card' icon shows blank as if no card is installed.

When looking in the 'about' section on the 6200 it shows free space on both internal memory and memory card (card is partially full implying a map is present). If I insert a newly formatted SD card which shows in the ‘about’ section when trying to add a map I get a ‘oops Something went wrong. Please try again’ message. For a small map I’m given the option to save to memory or SD card, for a large map no option is given. I continue to get the ‘oops’ message when trying to save to the SD card.

I have done a device reset but this has not resolved the issue.

Any help and advice appreciated.
Das Problem, genau wie Sie es beschreiben, habe ich auch mit meinem Go 6200.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Latest resources

Forum statistics

Threads
28,945
Messages
195,458
Members
67,918
Latest member
PeterSchip

Latest Threads

Back
Top