Tell

390 is here BTW the November 2024 release Waiting for the mods to pin this and unpin 370. This one.

I keep answering this one on Briskoda and SeatCupra. <=350 supports mib1 + mib2 in one release >350 supports only mib2. Mib1 release dropped The directories don't bear much resemblance to the names. Basically when mib2 high came out the mib2 high only stuff was put in the mib2 directory but it also uses what's in the mib1 directory for the overlap. Hence why the mib1 file has still got stuff in it. Audi always apparently released mib2 high like this. From 370 on Skoda and VW switched to this type of mib2 high only release. Mib1 high has bit the dust for now.

Probably just needs the menu toggling. Rings a bell on a Mib2. Sure it's not ACC covering it up. Whatever ACC covers up on a MIB2 on the display it does the same on Mib3 or just a menu that needs toggling to get it back up.

Those formatting programs date to before exfat and to using disk drives at the time on fat32 devices that only could see Fat32. Use to use disk drives with satellite TV boxes. You could put any disk drive onto your sat box (usb plug) but the inherent nature of fat32 is even if you fiddle with it, no file can be greater than 4gb within a much bigger drive. Hobbyist sat TV boxes. It still gets Firestick users that put storage on Firesticks since Amazon use Fat32. Upshot is you can't turn a Firestick into a useful media player if your video is greater than 4gb. 4k / HDR films tend to be way above this. Android TV on Nvidia and Chromecast 4k etc on the other hand support newer file formats. I stuff 1tb SSDs onto these in usb3 cases. Cunning of Amazon to limit Firesticks to fat32 although a cack handed way of doing with with ES Explorer is reported. Nvidia is my main home media player. Firestick for holidays and the Chromecast to play with. The development machine in old talk. The second mainframe sitting in the corner... Firesticks don't take useful disk packs. 🤣 https://en.m.wikipedia.org/wiki/Disk_pack Digress. Fat32 has had its day really for big storage, exFat replaced it. There were those fiddle programs that allowed its design bounds to be broken, but the 4gb individual file limit is still there. Solid state storage is now optimised for exFat over NTFS why it's the standard above NTFS. Why the big SDs and USBs come formatted in exFat. It's then a bit eccentric to format them to NTFS as some do if your hardware is fundamentally designed for exFat. You'd get away with the extended fat32 fudge programs on Vag mib3 on these drives because the source map fragment files are less than 4gb in size. They don't break the fat32 fundamental limit of how it indexes. The same way as SD TV series can play on the Firestick but no good for 4k where each episode is highly likely to be above 4gb 😉. The 4gb limit is in here https://en.m.wikipedia.org/wiki/File_Allocation_Table The achilles heel of Fat32. exFat took over.

Think yours are the Antipodean smaller files. Probably your Fat32 is working well since it's in the 4gb area. There are mods about of formatters which push the limits up of fat32. Google friendly AI system says this which I wouldn't disagree with... exFat is designed for solid state memory. I did do some timing on an SD card when this came up about mib2 high maps bridging the 33gb limit. There is a burst mode on some USB drives which is how they get different speeds. At the end of the day it's whatever works for you although keeping to Vag guidance makes it easier to give one set of instructions of how to do it. I quite like the idea of the stick with the data flashing light on it. Mib2 high I use the engineering menu so see the components parts go over as the map is updated. Not sure of whether anybody has mastered the mib3 swdl. Probably. In the meantime flashing LED on the USB does show some data traffic.

It is digital nothing is lost. If you do it directly you start thrashing the interface between the motherboard and the USB as it goes backwards and forwards unless UnRar uses a working directory then copies everything over once unzipped. 7zip doesn't. The built in Windows 10/11 are slow on unzipping which is why I stick to the Vag recommended process. I know Skoda drivers don't follow set rules like wanting to use NTFS when they shouldn't. 😉

If you are using MartiniBs current top post that is 24.06, so on your last question is whether your current downloaded maps over the air I take it are after 24.06 as shown on your screen. MartiniB's files are direct from the file server so if you use the VIN approach via the respective VAG website you may be served up old maps. Always best to use MartiniB's direct link since these are identified before they get wrapped in a web page. VW, Skoda and Seat they all use the same file so you use the first one that's works doesn't matter which branding its on. Seat currently only shows 2022 maps which is ridiculous. So yes you will have the latest downloadable files. I would have thought your contract ending in February would give you earlier files but you can read that off the menu. That then falls into presentation. 7zip is recommended, other unzipping programmes can add extra characters. Having downloaded the file as a zip. You make another directory where you are going to unzip it too. Open that up with the filemanager, blank one. Then go back to the download directory. Hangover the zipped file, right click, 7zip open. Highlight all elements than drag and drop to the empty directory. That is then a replica of what is going on your USB. After unzipping it, then drag and drop all of that onto the USB. Those multiple open screens can be done on Windows 10/11 by picking off the top right in the filemanagers. Use 7zio since some early versions of Windows 10 can add those random characters. Then put it in the car and follow those menu options to kick it off. Your download folder will have this in it Then all of this stuff is got to be in the root of your USB.... not one down if you see what I mean. I ball the PDFs. This is what happens people get it in the wrong level. You might be fine using the built in Filemanager opening up of the zip file but it's got to be as below in your root. You don't want to see OI_ blah, blah on the USB what's below is in the route. USB needs to be blank before the copy. As per the SKODA PDF https://www.seatcupra.net/forums/attachments/skoda-map-updates-mib3-pdf.36225/ But I open it up and copy out to a save area, then copy it out to the USB but as per the documentation that is what goes in the route and it's exFAT, there are NTFS lovies about but they really shouldn't be using NTFS on SD and USBs !. It's slower. On this bit: That's the incremental update with roll back restarts if it does roll back. Should take the 40 minutes on the EU maps.

exFat should be fine. That's the default format for large semi conductor memory. If it's a reversible stick with a connection at both end that is the preferred Briskoda advice you read on here if your PC / Laptop only has USB A. If it's got USB C then a USB C only stick is fine. It's the USB A / C adaptors that don't support data that are an issue. That's reported elsewhere. There are some USB sticks that have a flashy light on them where users like them since they see that it's doing something. That got the thumbs up from SeatCupra website of recent. That just brings us onto presentation. Mib3 is like mib2 high, an encryption signature is used to ensure the integrity of the upload. You can't poke about inside the files and resave them, quit is fine. You have to be careful that any inspection of the files is kept separate from what you are going to put into the car. Getting the files presented at the correct level is also important. That's in the documentation for the map uploads and radio logos. You mentioned Windows so that would be fine as far as Macs are concerned where CleanMyDrive needs to be used to take away Mac garbage that Macs leave on the USB drive. That's the encryption signature check that the files fail on if CleanMyDrive isn't used. The map upload can take a time and will only take place in the window that the unit is powered up. Restart points are used if the unit powers down. Why map updates can take several days dependent on how you use the car. The speed of the USB will also have a bearing on this obviously. So as to not re invent the circle I've used the best Briskoda / Seat Cupra advice on this thread. The first post has the PDFs for each of the VAG brands, which are all the same technique. Down the bottom of that post, you can see the level of success. It's a fair level of success. I suspect it's like mib2 high, presentation issues kick in and people have issues. You see that across the Vag brand on mib2 highs (that SLA encryption signature and presentation), once sorted out, no issue. https://www.seatcupra.net/forums/threads/updating-the-inbuilt-mib3-satnav-offline.472408/ As far as radio logos are concerned no luck with Seat it's not supported. Only VW and Skoda. Seat haven't argued the toss on that one well enough with the Vag contractors. Skoda owners are more fortunate.

You could try opening it in SQLite and if it looked like the other one. Failing that you'd have to deploy your SQL skills in a query 😏. Been a while. Presume bash tool isn't fussy about signatures and checksums else you'd be working those out. As far as mib2 high is concerned I just download the missing graphic to in fill a station which you can do... think you can do the same. The bash update must overwrite the built in ones of the mib2 high incanarnation on Audi. Mib3 as we know are stuffed on this except using these files which don't work on Seat... the poor relative of the Vag family. Under resourced.

Did you see that MartiniB edited in the rest of the links for the November 2024 release last Friday. Particularly Australia. # Australia 1.8 Gb VW portal: https://navigation-maps.volkswagen.com/vw-maps/AUS_12PR119_CT3WS-23131_Offline_Update.tar The one you were after. Comes up with the designator for June which is what you'd see with connected services... the other debate. So that the November release.

Yes do a new thread in your normal style in your name with the files inside etc text. I wanted to get the SeatCupra one posted up since it had started to go on the wrong thread and was incomplete. So having found that our friends had missed off the RoW, corrected that. On that one above I've got 2024 in the title should actually say 2025. Just the title out. Needs your exacting hand to get it totally it your style. Anyhow. We got there mib2 standard isn't dead yet. The cartography is TomTom, they haven't changed that and TMC for Trafficmaster doesn't work in the UK as we know, so the Briskoda fix for using Inrix on the last release of the HereMaps one, still reigns supreme if you put TMC ahead of newer maps as far as the UK is concerned. I just keep both in the car. Can swap if I feel like it. Yes so a nice new thread, in your name with your exacting eye is required to check mine. That then needs to be pinned together with the mib2 high one you reference. All should be done then on mib2 till June 2025. RoW mib3 is still to be found and the Vag links for the 2025 (November2024) release and that will be done. Seat people are already using your Skoda link for Europe. BTW anybody got a link to mib1 standard V5. Seat poster has lost their files.

@MartiniB the rest of the world is also there, the DLs so I've got this list (done a hack job of your normal post 😍). You can check where I've got it right. Needs your normal creation dates etc for you. # ECE AS(A1) 2024 (All Europe - needs the 32gb card) VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-AS_2310_V20.7z # ECE 1 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU1_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU1_2310_V20.7z # ECE 2 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU2_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU2_2310_V20.7z # ECE 3 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU3_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU3_2310_V20.7z # ECE 4 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL1_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL1_2310_V20.7z # ECE 5 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL2_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL2_2310_V20.7z # ECE 6 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL3_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL3_2310_V20.7z # ECE 7 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL4_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL4_2310_V20.7z # ROW 1 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM1_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM1_2310_V20.7z # ROW 2 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM2_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM2_2310_V20.7z # ROW 3 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM3_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM3_2310_V20.7z # MRM DL1 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM-DL1_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM-DL1_2310_V20.7z # MRM DL2 2024 VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM-DL2_2310_V20.7z VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM-DL2_2310_V20.7z ======= coverage ======= # ECE AS(A1) Albania, Andorra, Austria, Belarus, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Czech Republic, Cyprus, Denmark, Estonia, Finland, France, Faroe Islands, Germany, Gibraltar, Greece, Hungary, Iceland, Ireland, Ireland, Italy, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malta, Moldova, Monaco, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, San Marino, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Ukraine, United Kingdom, Vatican City State # ECE 1 Andorra, Belgium, Faroe Islands, France, Gibraltar, Iceland, Ireland, Ireland, Luxembourg, Monaco, Netherlands, Portugal, Spain, United Kingdom # ECE 2 Albania, Belarus, Bosnia and Herzegovina, Bulgaria, Cyprus, Denmark, Estonia, Finland, Greece, Kazakhstan, Kosovo, Latvia, Lithuania, Macedonia, Moldova, Montenegro, Norway, Romania, Russian Federation, Serbia, Sweden, Ukraine # ECE 3 Austria, Croatia, Czech Republic, Germany, Hungary, Italy, Liechtenstein, Malta, Poland, San Marino, Slovakia, Slovenia, Switzerland, Vatican City State # ECE 4 Andorra, Austria, Belgium, Croatia, Czech Republic, France, Germany, Hungary, Italy, Liechtenstein, Luxembourg, Malta, Monaco, Netherlands, Poland, San Marino, Slovakia, Slovenia, Switzerland, Vatican City State # ECE 5 Andorra, Austria, Belgium, Croatia, Czech Republic, Faroe Islands (land-use only), France, Germany, Hungary, Iceland, Ireland, Italy, Liechtenstein, Luxembourg, Malta, Monaco, Netherlands, Poland, San Marino, Slovakia, Slovenia, Switzerland, United Kingdom (incl. Isle of Man), Vatican City State # ECE 6 Andorra, Belgium, Denmark, Faroe Islands (land-use only), Finland, France, Germany, Iceland, Ireland, Luxembourg, Monaco, Netherlands, Norway, Sweden, United Kingdom (incl. Isle of Man) # ECE 7 Albania, Austria, Belarus, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, Estonia, Greece, Hungary, Italy, Kosovo, Latvia, Lithuania, Liechtenstein, Macedonia, F.Y.R.O., Malta, Moldova, Montenegro, Poland, Romania, San Marino, Serbia, Slovakia, Slovenia, Switzerland, Turkey, Ukraine, Vatican City State # ROW 1 Israel, Argentina, Brazil, Fr. Guyana *, Guadeloupe *, Martinique *, Mexico, Turkey * # ROW 2 India *, Chile * # ROW 3 Australia, New Zealand, Botswana *, Lesotho *, Mozambique *, Namibia *, South Africa, Swaziland *; Reunion *, Brunei, Indonesia *, Malaysia *, Philippines *, Singapore, Thailand, Egypt *, Algeria *, Bahrain *, Jordan *, Qatar *, Kuwait, Morocco, Oman *, Saudi Arbien *, Tunisia, United Arab Emirates * # MRM DL1 Argentina, Brazil, Mexico, French Guiana, Guadeloupe, Martinique # MRM DL2 Israel, Turkey

@MartiniB normal success screen on the all Europe map. Haven't checked the others yet. Not sure whether they might have messed the road top speed signs up (again). Seemed to be an indication from Cairus to that on a Seat post. Think he's reading another board which isn't the one linked to above. Something to look out for. I don't use these files myself.

It was Cairus that gave me that before it got edited to those links so he was ahead of that post. The files are 10 days old... so quite recent. Zipping date. I might claim the edit to get the rest 😍 what I told Seat guy to do last night. I found it worked and went to bed.

Oh yes I recognise one of the Seat posters there on the thanks line. It started off with all Europe. Thought I'd edit for EU1 and found it. Went to bed and the list was posted up at about 2:30am on the Seatcupra side. Youngsters...🤣

Eager beavers have produced these links following the edit. @MartiniB let you QA and publish them proper. Will check out the all Europe and the Europe 1 map later. Europa 1. https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU1_2310_V20.7z Europa 2 https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU2_2310_V20.7z Europa 3 https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU3_2310_V20.7z Europa 4 https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL1_2310_V20.7z Europa 5 https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL2_2310_V20.7z Europa 6 https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL3_2310_V20.7z Europa 7 https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL4_2310_V20.7z

You might find the other variants there. I found this by manufacturing the filename: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU1_2310_V20.7z # ECE 1 Andorra, Belgium, Faroe Islands, France, Gibraltar, Iceland, Ireland, Ireland, Luxembourg, Monaco, Netherlands, Portugal, Spain, United Kingdom Haven't tested it yet. Suspect it's fine.

@MartiniB eager beavers posted this up on the Seatcupra site haven't looked at it yet. https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-AS_2310_V20.7z Will have a look tomorrow although we have a gale so might not get out the door.

We don't dwell on the "outdated" bit. The Google map people think they have the latest maps but still on a production / validation cycle. So the material itself will go through a validation cycle if spotted as a road change / new build. That can vary by cartography company. Google can be very bad digitising private farm tracks. Loonies behind that. Google cars also go up them ignoring no though road signs. Saving grace round here is the camera gets knocked off the top of the vehicle on over hanging branches, so they stop and turn round, others they have got through and Google digitises a private farm track. My pet hate living here as hotel guests proceed up an unmade private farm track road between two made public roads. Have to jump to one side. Unlike Oz we don't drive on unmade roads in the UK... and not farm private tracks that cut between public roads... loony mappers and loony cartography companies put this stuff in. The speed of the road should get you on main roads but if farm tracks are put in at 60mph it fools the algorithm on route selection. How you get taken up silly cut through roads. The production cycle is then about six months which are those two dates. It can take 1-2 years to get new builds into digital maps. Proper cartography companies like Here Maps have them digitised in for complete new highways, then turn the changes on once they hear the road is build. The new estates can slip through un picked up. Traffic is monitored by probes from the mobile phone traffic. That one is how loonies manage to get non existent builders roads into digital maps. On housing estates the development company have one set of roads that are builders roads from the depo etc then once the estate is build the geography is changed. Careless mapping companies digitise the developers roads which never get taken out. Happens a lot. Roads go through people's front gardens or houses.... Builders roads should never be digitised in, only the finals roads. The road must be there since we have traffic, no the bulldozer driver phone in their back pocket. In the UK the gold plated standard is the Ordance Survey planning maps. Any development has to be on these Crown maps. The local authority planning / survey department use these as indeed private survey companies making applications for builds. The local authority allocate house numbers against them. Where the UK house number scheme is found and the post office, postcode / house number directory. Problem is they cost money for cartography companies to use and they are set in their international ways of one way of working fits all. Where GIS proxy solutions are used on house numbers in digital maps. They don't get them in the right place. Scatter them along roads equally spread. Another GIS solution used but not very good by some cartography companies. Early mib3 maps in the UK clearly had something wrong with them. They took you off road to house numbers. The company that translated the Here Maps cartography files didn't have a clue about GIS. You went off road to a house number. That has now been fixed. That issue was fixed two years back. So yes I wouldn't dwell too much on that six month cycle from file closure to distribution there is a long lead period before that. If the cartography company isn't doing their job well it's garbage in garbage out so any lead time is meaning less. So yes MartiniB is now using the YY.MM as the map designator that you'd read on these maps in the car so it falls into line. SQL can be used to inspect the files as above to check to find it. Before the kind soul told us how to do it we didn't know. I put a request out for somebody to say where it was in the file. They duly told me 👍 which means you can audit the materiel for how it will appear once installed. Useful when looking across what Vag sites are offering up.

YY.MM Those on connected services in Europe get the monthly updates over the air and quote that YY.MM if they have lost the update for whatever reason. Only recently we got told by a clever soul where the YY.MM was in those files since we had no way of placing the offline maps to the online ones. We know now. MartiniB in anycase loads those in his car. The issue was placing the maps provided in other Vag sites. Seat, VW which were old and which not. SQL Lite provides the answer but I'll take MartiniB's word. We know that Seat maps are hopelessly out of date offline... may have changed that now. Depends how good their library services are for filing away what they get given. Seat was very good once, better than VW. They had files that VW didn't in their filestore. South America. Skoda has lagged behind VW at times but seems on top of it now. MartiniB meticulous notes the stuff down. Those dates listed are a carrier over from his mib2 listings but he has now added the YY.MM which is the version release in traditional terms. Mib2 high is on 390 now, the 24.11 is the equivalent in mib3 (November 2024 release). You'd expect 25.05 to be the next release but we'll see. As for 390, it could be 410 but they have been known to leap much further forward at times.

Well they won't load in if the file is scrambled. Not sure of the mib3 behavior of how it re sees something it already has. You'd expect a delay whilst it read the files to check or maybe it shows nothing. Other than that you will be climbing into recent release cars to read their series release. You can do that on a Cupra Tavascan for me... think you should be seeing that before Europe. I reckon that has mib4. Think we might be seeing those releases that Audi have which you see on the Drive2 board that aren't the sequence of mib3s we recognise. Fun when a new mib is brought out. Throw this one out for MartiniB. I'm sticking with trusty mib2 high for the time being but a slick EV would be nice in 5 years time. Mib5 if Vag doesn't go bust by then. Might have to have a few years of no map updates to get to that point.

Tried the first one on MartiniBs list ?. MartiniB has his sniffing out program, evident he's not found the group of RoW November 2024 maps yet. Probably not loaded up into the Skoda filestore yet, which is why. Ozzie summer time drives at Xmas may have to be done with older maps till then. Few more days left in November for that or may be a late running release. On the positive side MartiniB said recently that these maps (Mib3) were only being release 12 monthly rather than the 6 monthly mib2 cycle to get you to buy the connect services contract for maps. The European November release popped out 🎉 which suggests they are keeping to the six monthly release. In some world markets the online connect services maps won't be released which is why one suspects you see the detailed release by country in the filestore of MartiniB's previous posts. It's just going to be late I guess. Somebody hasn't loaded them up yet or they haven't all been run off yet.

Well it was late last year about February as I recall.

Ah perhaps you need the trusty infotainment reboot. Long hold on the on/off but till you see the splash screen reappear. The units stay powered up after locking the car for 20 minutes. Old Vag rules. Why your infotainment stops running if listening to it with the engine off, doors closed. Leaving it off over night replicates the reboot procedure. As I hinted the firmware in these units can be problematic. Well we are all running different firmware in our vehicles, brand by mib2 firmware release. So what you are seeing may be different. I also get strange ones if I use way points at times. Programming bugs.

Google swdl mib2 high... but as said you have to be careful to keep the power up to the unit else if you loose that you are sunk. Retrofitter leave the door open since that keeps power to the head... battery charger or engine running as well. You fake the infotainment unit to keep running during the swdl process... mind you I've never tested it to destruction on loosing power. You wouldn't want to, map upgrade you can start again from fresh but a firmware half done you are sunk... that's the open up and short pins to get it back. That's on the net.