Thread: Which is the limitation to the SD/microSD card size for Garmin devices ?

Yes, Garmin tend to use the umbrella term 'software' for their unit firmware, which it is in fact of course, just a relatively small and specialised piece of sw more closely associated with the specific hardware than general software may be. Goddam confusing for many users and beats me why they [and others] do that.

The 4.90 fw is the latest version for 6x0, the other minor fw versions don't count for this puzzle, but on a side note some of my 3x0/6x0 units are running 'GPS SW VERSION 3.00' and others have V2.90 and those units aren't offered V3.00 for some reason. However it's immaterial anyway.

Perhaps we should look at the particular card you're using. Have you tried any others apart from the Kingston 8GB Class 10? I've really don't have a clue why this is happening for you. Even the 2014.40 shouldn't work either at 2.10GiB but we know it does on different brand and size cards regardless.

As to the Ford PCM, older ones had a known issue with corrosion to the connecting pins because of a dumb location letting moisture in. PM me if you want the solution. I won't tell you where the MMs grow though seeing you're from NH not MA. Nearly as many freaking' Deerfields in US as there are Springfields i think .....

Originally Posted by Neil

...
Perhaps we should look at the particular card you're using. Have you tried any others apart from the Kingston 8GB Class 10? I've really don't have a clue why this is happening for you. Even the 2014.40 shouldn't work either at 2.10GiB but we know it does on different brand and size cards regardless.

...

The saga continues...

Things have changed. I previously only had the 2015.10 gmapsupp.img installed, but decided to complete the update and copied over gmap3d.img to the internal memory and D3191130a.jcv (hope that was the right one) to \Garmin\JCV on the SD card. Now, the map isn't recognized. Removing them, the map is still gone. Switched from Kingston 8GB class 10 SD card to SanDisk 8GB class 4. Still no-go. Looks like I should've left things alone - but then, I'd still not have 3-D nor junction view capabilities - although that wouldn't be all that bad, 'cuz the 660 is my spare unit.

Can gmap3d.img be loaded onto the SD card, or does it have to be in main memory?

Guess I'll revert to just the lower states.

Side note: where's the best place to go to find out which gmap3d.img and which .jcv files are the right ones for my map selection? Is there a way to tell by sniffing into the gmap*.img file? I'm thinking I'd like to be able to find this info for future updates, not just this one.

Thanks.

========
Edit
========

I just confirmed that my 660 supports neither junction view nor 3-D. I think years ago, I tried loading it with both capabilities. Now I remember that it doesn't do either. I'm still curious about the inquiries, though.

They say that with age, memory is the second thing to go. I don't remember the first.

Originally Posted by Mr.Natural

.......... Looks like I should've left things alone............
Guess I'll revert to just the lower states.
................
They say that with age, memory is the second thing to go. I don't remember the first.

Lol. The first is the ability to stay focused on the task at hand ...... Now, ...... umm... what was the second again?

So your investigation killed the magic card. Nice work Sherlock.

If you have the gmap folder loaded to your PC, you can load most of NA except for the tiles which i've selected below [i.e. the reverse]. That will get it down to just under 2 GiB and is the image i loaded to 3x0/6x0 to check it would work when i couldn't get the full NA to show. You actually only need to lose a minimum of 181,993,473 bytes [~173.56 MiB] for it to be 1 byte under 2 GiB:



From memory of previous map versions, contiguous US mainland only will be ~1.5 to 1.6GiB, US + MX will be ~1.8GiB and US + CA + AL + MX northern Border States will be just below 2GiB. Maybe you could get all contig. US + MX + CA Border States under 2GiB as well.

Probably Garmin would say 16GB, or maximum of 32GB anyway because cards larger than 32GB are usually formatted in exFAT which isn't recognised by Garmin devices.

In fact the physical size of the card itself is of no real importance. It's other attributes which must be respected, most important ones: the format of the card [FAT16 or FAT32 only], the size of an individual image file [under 4GiB for the Astro 320] and the total amount of map tiles present on the unit and card in all maps including basemap [probably 4,000 maximum for Astro 320].

Even a 128GB card can be reformatted from exFAT to FAT32 with 3rd party software.

Best not to simultaneously enable two or more maps covering the same area, or even if they only have some overlaps. The Astro has only 1.7GB available for on-board storage but some is already in use, i'm unsure of the OEM Basemap size.

Note: I've moved your post to an existing thread. Another interesting one is here: [Only registered and activated users can see links. ].

@fishhard
Reformat the SDXC 64GB card from exFAT to FAT32 and it will work like an SDHC card. Use this:

Code:

Please Login or Register to see the links

Or google for other methods.