Firmware V4.00 on new Marine Devices
Dear list Garmin recently released a major firmware update (v 4.0) for the Echomap and newest GPSmap marine series. http://newsroom.garmin.com/press-release/marine/garmin-gpsmap-and-echomap-pr oduct-lines-receive-new-features After the firmware update my current charts fail with a map format not supported error on those devices. However one of my old charts which was produced with mkgmap-r3316 in mid-2014 still works. I want to track down the problem. Can someone point me to a download-link for mkgmap-r3316 (both binaries and default style from this release) so I can try to reconstruct a map that does not produce the error? Regards Jürgen
Hi Jürgen, see link below. The jar file contains also the style files. http://files.mkgmap.org.uk/download/246/mkgmap.jar Gerd From: rheinskipper1000@gmx.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 2 Feb 2015 16:06:55 +0100 Subject: [mkgmap-dev] Firmware V4.00 on new Marine Devices Dear list Garmin recently released a major firmware update (v 4.0) for the Echomap and newest GPSmap marine series.http://newsroom.garmin.com/press-release/marine/garmin-gpsmap-and-echomap-pr... After the firmware update my current charts fail with a “map format not supported” error on those devices. However one of my old charts which was produced with mkgmap-r3316 in mid-2014 still works. I want to track down the problem. Can someone point me to a download-link for mkgmap-r3316 (both binaries and default style from this release) so I can try to reconstruct a map that does not produce the error? RegardsJürgen _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thank you Gerd for your very fast reply. Is it really enough to exchange just the mkgmap.jar but keep the libraries to completely go back to r3316. Unfortunately I was not able to find the problem, yet. If I make maps with this mkgmap-r3316 they do not run on any current marine device with firmware 4.00 or 4.20. I made maps using my style and my options but also with default style and default options. No matter what I try, there will be the map not supported message on the Echomap 50s. But amazingly this old map, I made with r3316 in 2014 runs perfectly: <https://drive.google.com/file/d/0B77DBX0gCRYsOE8zT29OdkVVX1U/view?usp=shari ng> https://drive.google.com/file/d/0B77DBX0gCRYsOE8zT29OdkVVX1U/view?usp=sharin g Regards Jürgen Von: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] Im Auftrag von Gerd Petermann Gesendet: Montag, 2. Februar 2015 16:16 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Firmware V4.00 on new Marine Devices Hi Jürgen, see link below. The jar file contains also the style files. http://files.mkgmap.org.uk/download/246/mkgmap.jar Gerd _____ From: rheinskipper1000@gmx.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 2 Feb 2015 16:06:55 +0100 Subject: [mkgmap-dev] Firmware V4.00 on new Marine Devices Dear list Garmin recently released a major firmware update (v 4.0) for the Echomap and newest GPSmap marine series. http://newsroom.garmin.com/press-release/marine/garmin-gpsmap-and-echomap-pr oduct-lines-receive-new-features After the firmware update my current charts fail with a map format not supported error on those devices. However one of my old charts which was produced with mkgmap-r3316 in mid-2014 still works. I want to track down the problem. Can someone point me to a download-link for mkgmap-r3316 (both binaries and default style from this release) so I can try to reconstruct a map that does not produce the error? Regards Jürgen _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Jürgen, I did not download that old map because I have no idea what to look for. Maybe the problem is in the OSM data, not in the program? Do you have a backup of an older *.pbf file to try that? Gerd From: rheinskipper1000@gmx.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 5 Feb 2015 15:10:27 +0100 Subject: Re: [mkgmap-dev] Firmware V4.00 on new Marine Devices Thank you Gerd for your very fast reply. Is it really enough to exchange just the mkgmap.jar but keep the libraries to completely go back to r3316. Unfortunately I was not able to find the problem, yet. If I make maps with this mkgmap-r3316 they do not run on any current marine device with firmware 4.00 or 4.20. I made maps using my style and my options but also with default style and default options. No matter what I try, there will be the “map not supported” message on the Echomap 50s. But amazingly this old map, I made with r3316 in 2014 runs perfectly:https://drive.google.com/file/d/0B77DBX0gCRYsOE8zT29OdkVVX1U/view?usp=sharin... RegardsJürgen Von: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] Im Auftrag von Gerd Petermann Gesendet: Montag, 2. Februar 2015 16:16 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Firmware V4.00 on new Marine Devices Hi Jürgen, see link below. The jar file contains also the style files. http://files.mkgmap.org.uk/download/246/mkgmap.jar Gerd From: rheinskipper1000@gmx.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 2 Feb 2015 16:06:55 +0100 Subject: [mkgmap-dev] Firmware V4.00 on new Marine DevicesDear list Garmin recently released a major firmware update (v 4.0) for the Echomap and newest GPSmap marine series.http://newsroom.garmin.com/press-release/marine/garmin-gpsmap-and-echomap-pr... After the firmware update my current charts fail with a “map format not supported” error on those devices. However one of my old charts which was produced with mkgmap-r3316 in mid-2014 still works. I want to track down the problem. Can someone point me to a download-link for mkgmap-r3316 (both binaries and default style from this release) so I can try to reconstruct a map that does not produce the error? RegardsJürgen _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I don´t have old OSM data. But I tried bounding boxes from very different parts of the world. Even tiny maps with only one tile do not work. It´s very unlikely that there are new errors in OSM data all over the world that can cause this problem. Rumors say that Garmin wants to block several third party marine maps in their latest firmware. Users already found a way to downgrade their devices to make OSM maps work again (Garmin says, downgrades are not allowed): <http://www.boote-forum.de/showpost.php?p=3756044&postcount=39> http://www.boote-forum.de/showpost.php?p=3756044&postcount=39 Jürgen Von: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] Im Auftrag von Gerd Petermann Gesendet: Donnerstag, 5. Februar 2015 15:30 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Firmware V4.00 on new Marine Devices Hi Jürgen, I did not download that old map because I have no idea what to look for. Maybe the problem is in the OSM data, not in the program? Do you have a backup of an older *.pbf file to try that? Gerd _____ From: <mailto:rheinskipper1000@gmx.de> rheinskipper1000@gmx.de To: <mailto:mkgmap-dev@lists.mkgmap.org.uk> mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 5 Feb 2015 15:10:27 +0100 Subject: Re: [mkgmap-dev] Firmware V4.00 on new Marine Devices Thank you Gerd for your very fast reply. Is it really enough to exchange just the mkgmap.jar but keep the libraries to completely go back to r3316. Unfortunately I was not able to find the problem, yet. If I make maps with this mkgmap-r3316 they do not run on any current marine device with firmware 4.00 or 4.20. I made maps using my style and my options but also with default style and default options. No matter what I try, there will be the map not supported message on the Echomap 50s. But amazingly this old map, I made with r3316 in 2014 runs perfectly: <https://drive.google.com/file/d/0B77DBX0gCRYsOE8zT29OdkVVX1U/view?usp=shari ng> https://drive.google.com/file/d/0B77DBX0gCRYsOE8zT29OdkVVX1U/view?usp=sharin g Regards Jürgen Von: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] Im Auftrag von Gerd Petermann Gesendet: Montag, 2. Februar 2015 16:16 An: <mailto:mkgmap-dev@lists.mkgmap.org.uk> mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Firmware V4.00 on new Marine Devices Hi Jürgen, see link below. The jar file contains also the style files. http://files.mkgmap.org.uk/download/246/mkgmap.jar Gerd _____ From: rheinskipper1000@gmx.de To: mkgmap-dev@lists.mkgmap.org.uk Date: Mon, 2 Feb 2015 16:06:55 +0100 Subject: [mkgmap-dev] Firmware V4.00 on new Marine Devices Dear list Garmin recently released a major firmware update (v 4.0) for the Echomap and newest GPSmap marine series. http://newsroom.garmin.com/press-release/marine/garmin-gpsmap-and-echomap-pr oduct-lines-receive-new-features After the firmware update my current charts fail with a map format not supported error on those devices. However one of my old charts which was produced with mkgmap-r3316 in mid-2014 still works. I want to track down the problem. Can someone point me to a download-link for mkgmap-r3316 (both binaries and default style from this release) so I can try to reconstruct a map that does not produce the error? Regards Jürgen _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list <mailto:mkgmap-dev@lists.mkgmap.org.uk> mkgmap-dev@lists.mkgmap.org.uk <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I have found an old copy of mkgmap-r3316 (complete distribution). I have uploaded it and it is here: http://files.mkgmap.org.uk/download/248/mkgmap-r3316.zip
On 05/02/15 14:10, RheinSkipper wrote:
But amazingly this old map, I made with r3316 in 2014 runs perfectly:
https://drive.google.com/file/d/0B77DBX0gCRYsOE8zT29OdkVVX1U/view?usp=sharin...
That map appears to have been created with the patch in this post: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2012q1/014157.html (ie the 0x170401 instead of 0x110301) So probably with the same patch, the latest might work too. Try this: http://files.mkgmap.org.uk/download/249/mkgmap.jar ..Steve
That map appears to have been created with the patch in this post: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2012q1/014157.html
(ie the 0x170401 instead of 0x110301)
So probably with the same patch, the latest might work too. Try this: http://files.mkgmap.org.uk/download/249/mkgmap.jar
..Steve
I generally apply the marine patch to all of my maps. Sorry, I forgot to mention this. The marine patch is always necessary. Is there any newer information available concerning the marine header than this: http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/TRE_Subfile_Format The marine maps are different at offset 0x44 and 0x45. But the wiki says 0x45 is unknown and 0x44 means draw priority ?!? I already thought that different patch values might be necessary for the new devices. But that´s not really possible because this old map still works with the well known patch. Only new ones don´t. We are not alone with this problem. This map created with cgpsmapper also does not work anymore with firmware 4.xx (it is also marine patched): www.waterways.cz Regards Jürgen
Hi
Only new ones don´t.
If you are sure it is the same version, same patch and same options, then all I can suggest is that they are looking at the timestamps in the file. See if this works on a small map: http://files.mkgmap.org.uk/download/250/mkgmap.jar ..Steve
Hi Jürgen, could you please test this map: http://files.mkgmap.org.uk/download/251/gmapsupp-marine.7z This a map from OSM data but recompiled with cgpsmapper. It uses different parameters in TRE than maps from waterways.cz. -- Best regards, Andrzej
could you please test this map: http://files.mkgmap.org.uk/download/251/gmapsupp-marine.7z
This a map from OSM data but recompiled with cgpsmapper. It uses different parameters in TRE than maps from waterways.cz.
-- Best regards, Andrzej
Hi Andrzej as I do not have an Echomap myself I have to wait for a user who tests the maps for me. This may take until Monday. But what I can say for now is that this map is not even recognized in Homeport on my PC. Jürgen
Hi Jürgen, I would gladly investigate problem but have no affected device. I will wait patiently, thanks. My map works in HomePort, but I haven't prepared gmapsupp.img for this. You can correct img with gmaptool, like in this example: http://www.gmaptool.eu/en/content/map-visible-basecamp -- Best regards, Andrzej
Hi Jürgen, any news about my test file? Garmin has released new update for some models of echoMAP: http://www8.garmin.com/support/download_details.jsp?id=4749 I'm trying to download this update: http://www8.garmin.com/support/download_details.jsp?id=4763 but link to exe is broken. Maybe you have a copy? -- Best regards, Andrzej
any news about my test file?
Achim (the guy with the Echomap) cannot test it within the next two weeks. But I asked him not to forget to test it, anyway. I am also curious about the test maps even though we meanwhile have a solution for the problem.
I'm trying to download this update: http://www8.garmin.com/support/download_details.jsp?id=4763
but link to exe is broken. Maybe you have a copy?
Sorry, I don´t have a copy, as my Gpsmap 526 as not updated anymore. But I´m sure, Garmin will fix the link soon. Jürgen
Hi, see this post: http://www.boote-forum.de/showpost.php?p=3760543&postcount=42 It seems that version 4.0 of firmware was affected and bug remains after upgrade from 4.0 to 4.2. But when upgrading form 3.40 to 4.20 directly, OSM maps work correctly. -- Best regards
see this post: http://www.boote-forum.de/showpost.php?p=3760543&postcount=42
It seems that version 4.0 of firmware was affected and bug remains after upgrade from 4.0 to 4.2. But when upgrading form 3.40 to 4.20 directly, OSM maps work correctly.
That post is from the guy who does the testing of our maps on his Echomap. Unfortunately he is ill at the moment and cannot go to his office where he has his device for testing. So our latest test maps could not be tried out. He got some information from Garmin. They say the problem is a firmware bug and they are working to eliminate it completely in a future release. Until then downgrading to 3.40 and upgrading directly to 4.20 seems to be the solution. We will never know if this was really a bug. Perhaps they wanted to lock third party maps but changed their policy after a shit storm was starting. Anyway I think there is no need for us to further investigate. Thanks a lot to all of you who helped on this problem. Regards Jürgen
Hi Jürgen,
Achim (the guy with the Echomap) cannot test it within the next two weeks. But I asked him not to forget to test it, anyway. I am also curious about the test maps even though we meanwhile have a solution for the problem.
Would be interesting to know which maps works. But I rather don't expect Achim to flash back buggy firmware, which is ok for me. The most important is that free maps work again. Thanks for investigating the problem. -- Best regards, Andrzej
Would be interesting to know which maps works. But I rather don't expect Achim to flash back buggy firmware, which is ok for me. The most important is that free maps work again. Thanks for investigating the problem.
-- Best regards, Andrzej
Meanwhile Achim flashed 4.00 on his Echomap again and tried all the test maps. None of the test maps worked: - the map made with cGPSmapper - Steve´s test map - the map I made with the mkgmap-r3316 distribution using my style and options - the map I made with the mkgmap-r3316 distribution using default style and options (only marine patch applied) Yes, it would have been interesting to know why this old map (made using r3316 in 2014) worked but all the others don´t. But I stop investigating here as the problem can be solved by updating the device from 3.40 to 4.20 directly. Regards, Jürgen
participants (6)
-
A drian -
Andrzej Popowski -
Gerd Petermann -
Malcolm Herring -
RheinSkipper -
Steve Ratcliffe