Could you use a PCI-Express IDE adaptor card in a modern PC to do this?

I notice you can get IDE SSD's now. Would it be better to clone your existing disk onto one of these and then try to update it (after unlocking). Nothing mechanical to go wrong and potentially faster operation (although I suspect it doesn't need to be that fast)

Quote:

Could you use a PCI-Express IDE adaptor card in a modern PC to do this?

Hi Cudman, et Al.,

Seems like you did go through same journey as I did.
The MUINFIEEE is the key - it tells the unit which SLOT to load and can be manipulated a bit...

Did you have 40GB HDD too?
The partitioning by default contains 3 regions maps uploaded by default, but only one region by default enabled.
Which slot did you have enabled by default?

I did a bit of RE on MUINFIEEE and by all the looks the info about which regions are enabled is stored within the unit, not on HDD. There is additional flash on the board (in fact I've disassembled the unit).

If you guys could provide info as shown on "HLDF Information Form" that would be amazing.
There is "Main CPU SW / Boot Version:" value and the latest firmware version I've seen so far was 0660. Feeling is that firmware might vary between markets too (character support).

For those who managed to open HDD and would be willing to share their MUINFIEEE from all slots, together with info which region/slot is by default enabled, that could help RE and to understand the content of MUINFIEEE.

The biggest problem for us in mainland Europe is that LR decided to put some close by countries in different regions and by default only one region is enabled.

Hint - there's also a way to load newer maps, but... where I got stuck is character encoding. Seems like the old ones were all in simple encoding and new ones use UTF8. This breaks search and display on the map for anything with local characters.

Another problem is that newer maps are much bigger and that what puts us to square one, as bigger map won't fit limits of the files (FAT32) and essentially needs to be split into regions and that drives the need to be able to enable more slots, as otherwise there is problem of which maps/countries to put on the HDD (for those traveling across Europe).

I had to put it on backburner for the moment but happy to discuss with someone who wants to invest their time too.

Best!

Quote:

Seems like you did go through same journey as I did.

Quote:

Did you have 40GB HDD too?

Quote:

Which slot did you have enabled by default?

Quote:

If you guys could provide info as shown on "HLDF Information Form" that would be amazing.

Quote:

to understand the content of MUINFIEE.BIN

Quote:

there's also a way to load newer maps

Quote:

Another problem is that newer maps are much bigger and that what puts us to square one, as bigger map won't fit limits of the files (FAT32)

Quote:

while some people knew how it worked, and kept if for themselves.

Do we have someone more versed on legal side to make sure we're not running into trouble with LR?
Human viewpoint is... LR doesn't give a s$#$ about owning older cars, especially these from 2010-2012 - these are completely unsupported ones for years, official last release from LR was what - 2014?
Can we therefore tinker with it and share? It doesn't impact LR revenue at all... though am unsure if someone wouldn't try to make an issue out of it.

All below is just for educational purposes.

On technical side - looking at other forums, getting MMM2 2017 maps wasn't something which I've seen as a victory, so not much to share... was focused on getting both slot unlock identified, as well as getting the newer maps properly working.
None of that has been achieved and on other forums every time some questions were asked, (i.e. Disco4), conversation was shut down - no one was interested in... So whilst watching others - difficult to write everywhere - hey help needed...

Back to key element - yes, KFE was tried but that is where the fonts problem and encoding lies - seems like at least 0660 doesn't have UTF8 support.
Fonts are within Loading.kwi in unkown format, well - some format which is more close to automotive than anything on IT side of the world (not a Type1 or TTF). There are also some bitmap fonts embedded in Loading.kwi.
It was beyond my knowledge and time I could spend on to learn and then share.

Plan B was and in fact is... to translate all names on maps into Latin fonts and then all should work, but... that includes translating indexes as well and that gets tricky, as Kiwi documentation (non-proprietary portion) can be found online, the indexes format - means a bit of work - again beyond what I could spend time on so far... awaiting autumn months and long evenings to come back to it.

To add to slots:
- Slot6 is Middle-East - interesting selection of countries
- Slot7 is South Africa
These maps were loaded on the drive, just hidden in the panel.
I've seen somewhere also list of what the rest of slots covered or was supposed to over - that was APAC and they had weird splits into regions there. Nothing we would be concerned with.

In my case WEU was only enabled though the EEU and RUS slots were visible, requiring key to be provided.

The key to unlock the slot is somehow linked to region and year of map and MUINFIEEE has at least date as starting bytes embedded.

I was able to manipulate MUINFIEEE from SLOT3 in a way that head loaded on the start map from SLOT3, but then going into map selection and selecting already enabled slot WEU it loaded content of the other SLOT, i.e. SLOT4 or SLOT5. It was down to manipulating one of the first bytes. Unfortunately forgot to write it down - it was so obvious at the time and now I don't remember as it was a good half a year ago. It was though 0x05 or around - I'd need to try again.

MUINFIEEE and Update are different only in a way that MUINFIEEE has additional 0 padding.
Additionally looking at its content, as you've found too - it starts with the date (0x00-0x03), then there is 00 and 0x05 is SLOT#-3 (WEU is 00, EEU is 03, etc.). Same as 0x2c (again SLOT#-3)

Visible slots have at 0x2e, value of "04", whilst hidden "08".
Section of 0x0a - 0x0f and 0x24-0x29 seems to be the same

The last byte seems to be 04 for hidden slots and some values for visible ones - not sure if follows any logic.

If I'd have enough examples of the content of these MUINFIEEE files for slots with description, I could approach to understand how it is built. Unfortunately with just one example I came up with number of conclusions, but could go past that point as the rest is a blind try& fail.

On HW side, the CPU is TX49 (Toshiba MIPS) - disassemble with couple of tools went south. Instruction set seems to be different and couldn't make anything out of it - again beyond my knowledge though if there's someone here who played with RE - maybe can help. It should be around SH4/SH2 but nothing conclusive was produced - again this is where my experience is short.

Would you be willing to share your MUINFIEEE?
I'll find a way to share the loading.kwi.
Please check if your loading.kwi in SLOT0 and other slots, especially SLOT3 is different or the same - the best is if you could get checksum of it.

Re newer map versions. Well, let's refrain from sharing links here as there are copyrights on the map data.
I have concluded that other manufacturer and cars that are compatible with the MMM2 map format are:

Jaguar 2009-2011 XF and XK, XKR
Volvo V70 2008-2011, XC60 2009-2010, XC70 2008-2011, S80 2007-2011
Subary Legacy/Outback 2007-, Impreza 2008-, Forester 2007-
Mazda 3 2005-2009, 5 2005-2010, 6 2005-2012, GGI 2005-2009, CX5 7 9 2005-2011, RX-8 2005-2011

Following along with interest.

A thought that occurs to me, while removing the HD and updating the maps sounds like it works, I understand its a lot of work to extract the head units on these cars.

We clearly have some clever people on here who have RE how the data is stored in the HD, would it not be possible to do something similar to the factory map update tool, and work out what format and data files need to be stored on that HD, and it it is a firewire interface have an adaptor to connect and update the device that way. Although it might work out more expensive way of updating as you need to have a HD and interfece etc, once you have it it could be used to update maps regularly, however you get hold of the map data?

@Cudman, could you PM me the details you mention in your previous post please.

Thanks
James

To those who would unlock the HDD, would be great if you could provide your MUINFIEE files to run some additional analysis - more examples better as there needs to be a patter - just need to discover it. There needs to be a relatively simple logic around it.

The problem with newer maps is that the moment screen is scrolled towards countries were characters missing in firmware (no support for UTF8) like i.e. Poland and other Slavic countries, their local characters as are used in names destroys the display of the map (no town/street names are visible anymore and as almost every town or surrounding has a town/village name with a character it blanks out majority of the map).

German/French/Nordic/Spanish/Italian characters were there as do not essentially require UTF8 encoding and did exist in previous versions.

No one so far as per my understanding managed to get European maps running properly (talking about beyond what MMM2/2017 maps are) and about what originally was WEU/EEU region countries.

In regards to slots, my aim was to enable 2 slots and be able to switch between them easily. Reason? Full Europe won't fit into even compressed alldata.kwi due to FAT32 filesize limits. And as such, Europe has to be split. I didn't try to force load alldata.kwi split into parts as it seems like this part of code is missing in LR/Volvo Navis. Hence the need to be able to switch between slots - depending where one is moving.

I might settle with just cut down version of Europe as am not traveling that much across... so it was just what I was aiming for when originally thought it won't be that complicated.

I didn't manage to go over the hurdle of getting myself together into trying to write some lines of code to transcribe names and indexes. Indexes might be the more tricky option.

Other ways I've tried was to disassemble loading.kwi but neither IDA nor Ghindra recognize this platform.

In terms of HDD layout and external connection. By all looks most of the crowd believes it is Firewire interface. The layout of the hard drive can be create by Map tools which come together with SDD.

The latest firmware can be potentially obtained with SDD (VBF file), but seems like is downloaded only when SDD is connected to the car. This I didn't have a chance to test. Weirdly other VBF including newer navi files are by default downloaded by SDD. Only these old ones seem to be missing.

Format of the files to be put on HDD, even if one would manage to connect is unknown as probably no one had access to dealer version of disks.
Maps itself these days are not that expensive, well 50 quid I'd spare as called by other brands. Volvo gives it away. It's only LR which plays funky.

If there's anyone who would be willing to share some SDD knowledge - potentially we could manage to get latest firmware.
Potentially, there might be some late 2014 version of firmware which would support UTF8, as newer (IAM2.1) head supports UTF8 already and majority of the code smells to be similar if not same hence there is slight chance that there exist proper firmware with UTF8 support and that would resolve problem with maps transcoding.

This all seems right up my street so I'm following with interest from a technical side.. And the fact my maps are as old as Moses. 2011 4.4 TDV8 Vogue SE - 'Black Betty'
2000 4.0 P38 HSE - 'Green Goblin' - Gone.
Audi..Mini..BMW..

So I have not got my FFRR and its got a 2011 map in it.
I really would like to update, but dont fancy taking the dash apart to get the display unit out to remove the HDD and update that way.

I have a copy of SDD, and it has the map update software on it. I have run this with a USB drive connected and it builds a number of partitions and directory structure.

Now I'm think that the dealer update tool is just an external hard drive that has both USB and firewire connectivity on it. Its still possible to get such devices, so with that and a made up lead maybe its possible to update using the factory method.

But what I need to get to the next stage is a copy of the dealer update disk for the hard drive satnav.
Hopefully should then be able to build a newer set of maps from another car. But without a copy of the dealer update there is no point in getting the usb/firewire drive

So what is required now is a copy of the dealer update disk. If anyone has access or a copy they could share?

PM me if you wish to remain anonymous in providing if it will cause you issue.

And maybe we can then come up with a way of updating the sat nav that usual by many.

Thanks
James 2011 Range Rover Autobiography TDV8 Buckingham Blue

Hi, has there been any progress on this? I'm happy to help if others are interested in finding a way to maintain an up to date sat nav map on these cars? Mine is a 2012 with single view and maps from 2011. Only 11 years out of date! I'm a developer so could help debug the map data and quite willing to try things on my car. Cheers James
2012 RR L322 Vogue in Orkney Grey
Previous 2003 RR Vogue

No progress made, as would need some more souls interested and actively participating to move forward - I've potentially reached limits of knowledge/time effort spent on it. Majority of important findings is already above - if one is happy to engage in development of maps transcoding - happy to work on it together.

Quote:

So what is required now is a copy of the dealer update disk. If anyone has access or a copy they could share?

The best would be to have that disk to see how files are laid out.
The biggy is from where/how to download latest firmware, as if this would have UTF8 support then no firmware modification would be needed and any new maps could be used. Biggest worry is that even the latest one might not have that UTF8 support and then we're in square one.

Otherwise, the way to go would need to be towards maps transcoding to use Latin only characters - any volunteer to write transcoder? Am happy to share knowledge about format, etc. with someone who has skills to write that piece of software.
The content is split into two - names, directly and index, which needs to be updated (index is the more difficult portion, though documented).