SW update for MIB2 infotainment system?

[MIB-Wiki]

@Chillout just pointed out, that one has to differentiate between:

MIB2 Toolbox (my product at GitHub.com/jilleb/mib2toolbox) which is all about customizing, and open for writing your own menus and scripts.

M.I.B. (which stands for More Incredible Bash), which is focused on patching a unit so it has all FECs and no component protection.

M.I.B includes patches for all (known) MHI2 FW versions.
Each FW patch includes an ifs-root-stage2 image with MIBROOT patched for:

1. FecContainer signature check
2. VCRN check
3. CP check

Install MIB Tool + Patch:

1. Prepare SD card - clean SD-Card (FAT32 formatted is requirement)
2. Extract all files of the M.I.B. to the root directory of SD-Card
3. Insert the SD card into slot SD1 of your MHI2 unit
4. Enter Engineering/Red Menu to start SW Update. Select UPDATE, select SD card, select "M.I.B. Launcher V1.0", START update.
   Installtion of M.I.B. on your Unit will start. The unit will restart three time until update process is finished.
   GEM will be activated as part of the installation.
   SVM error has to be cleared via M.I.B. function in GEM after installation
5. Enter GEM on your unit and have FUN!
   Select ==>>M.I.B.-More_Incredible_Bash<<==
6. Clear SVMs with MIB Tool
7. Install Patch from MIB Tool
   1. Backup with MIB Tool will be run automatically
8. addFec to FecContainer.fec (e.g. SKODA map Fec)

 

[Tell]

That feels as if it won't go wrong.

Will add to my notes.

I have been looking through the MIB files to see what was in them and noted each release was covered and the initial load files. Indeed it looks thougher.

Thank you. Got another month of note taking .

Will read through the other DEB forum on people loading up below 1447 for any other hints (1409 and 1376).

I added the TMC notes above since software upgrades can turn that off so needs to be put back to the 15 setting we use least in the UK via VCDS. That one was from @Walone on their firmware upgrade.

I worry about whether the 360' camera alignment settings are stored in the infotainment unit. I assume wherever they are they remain unaffected with the current map, user POIs, jukebox material etc still intact.

 

[Tell]

@MIB-Wiki have you got a video link to 8, 9 & 10 above.

What I found online looked a bit heavy on typing filename > etc. Is it more menu driven now or are you typing very precise text.

Got any YouTube videos to go in ?.

 

[MIB-Wiki]

No video available.

Did you check the README and look at the picture of the menu structure I included above?

All is run from SD within GEM. No way to input text or type.

Just install M.I.B on your unit and have a look. No need to make more notes and wait…
Will all be done in a few minutes .


Gesendet von iPhone mit Tapatalk

 

[Tell]

My understanding is that I can't install MIB with my current firmware 1338 so I can't look at the screens so once you have started you are a bit stuck since it disables navigation till you install it. So one needs to clarify what needs to be done.

Re above there are green screen PNGs which are far to small to read above. Microscopic. I had noticed you had edited them in. They need to be more readable.

Googles also taken to not wanting to translate now and OBDEleven is threating an annual Pro license but sign some money over today... dah dah others are saying if you got Pro you got a lifetime license now... but other than that. (will see whether that's being talked about elsewhere on the Forum)

Needs the green screens made readable or a link to where they are. Like does everything go on the SD card and it knows it's 1447 so will pick it up or do you put 1447 in a directory. Is it press and play or fiddle. Needs a generalised video like Andrew produced.

 

[MIB-Wiki]

Installation of M.I.B is always working.

Display in GEM is however limited to GEM version 4.1+

Not sure about GEM version of your MU.

The screenshot above should be possible to view in full also. At least the original file was big enough.


Gesendet von iPhone mit Tapatalk

 

[Tell]

Installation of M.I.B is always working.

Display in GEM is however limited to GEM version 4.1+

Not sure about GEM version of your MU.

The screenshot above should be possible to view in full also. At least the original file was big enough.


Gesendet von iPhone mit Tapatalk

Each image needs to be in it's own PNG. They appear as this... one blob. But I do think we would be getting somewhere if we could read that..

Suggestion put them in a word document on your server and link to them ... unless they already are.

 

[MIB-Wiki]

Check post on DEB. You can get the picture in full resolution there. Here it seems to be reduced in quality after saving.


Gesendet von iPhone mit Tapatalk

 

[Tell]

Have you got the link ?.

 

[Tell]

Did find a couple of files on other boards... probably old but give the gist

And the handy text readme.txt.

My old firmware issue (1338) of whether mib tool can be loaded revolves around which version of Gem I have. @jpmedia PMed me to say if my Gem was ver 4.10 then I could load it and Mib tool will work then offered to do the rest with the team you suggested. Will have a go later. Good if one sees a menu like that. Revised PM to say above 4.1 (yes we are 4.12st).

@Walone has a pesky SVM code he cant get rid of... yet to check whether I can get rid of mine. I get one every time I do a map update, so just left them. But we are told to get rid of them before Mib Tool, how critical ?. Once you get Mib Tools in it takes care of them for you.

Walone's:

1 Fault Found:
1556 - Internal Control Module Memory Check Sum Error
B2000 87 [009] - Missing message
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 24

Is that bad ?.

I'm not sure at which stage any previous retrofitters hanky panky will show up in blocking changes. Whether that can be seen in the backup or whether that's when you come to flash. That what Chillout warned about but ways around. Something only retrofit units need to worry about.

Thanks all.

 

[MIB-Wiki]

The picture above is from the putty interface, so that is the old solution (which is still available, but not used much anymore) where you run M.I.B via telnet interface on the unit. Of course, running this is independent from GEM version. But you need to have the D-Link adapter and PC with putty to run it.

The new GEM solution just runs from SD card only. Way easier to use.

Just update FW, all latest FWs (on all brands) have GEM >4.1.

Just follow the MEGA link, you will always find latest M.I.B version and Documentation there.

SVM code sometimes can get 0 this can not be removed. Maybe that is also the case here?
Having SVM error is not a problem towards functionality. It is just not nice. And the dealer might ask, where it is coming from.

Gesendet von iPhone mit Tapatalk

 

[Tell]

I'm encouraging you to provide the pages . I will take a photo when I get that far.

This is the documented main menu screen edited into above... the working "how to" in English:

The problem with the Mib Tool / DEB documentation is the implicit assumption that you load up Mib Tools after the firmware update.... Not that Mib Tools works with all least dependent on release of GEM.

Think you mean GEM>=4.1... my two maths degrees come in handy. JPMedia has now corrected himself inline with you . (greater than 4.1)

I will give it a go but I think I will take up @jpmedia offer of it on 1338 first then jumping to 1447 although if the backup of 1338 is an installable backup ?, then jumping to 1447 wouldn't be an issue since I would have a way back if the retrofitter hadn't fiddled with it to prevent user firm ware updates ?. (That which he said "after I do this you won't be able to install firmware yourself"... assuming that was an idol threat or doesn't apply thru mib tools GEM method although Chillout implied an issue may exist but can be got round).

 

[Walone]

@Walone has a pesky SVM code he cant get rid of... yet to check whether I can get rid of mine. I get one every time I do a map update, so just left them. But we are told to get rid of them before Mib Tool, how critical ?. Once you get Mib Tools in it takes care of them for you.

Walone's:

1 Fault Found:
1556 - Internal Control Module Memory Check Sum Error
B2000 87 [009] - Missing message
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001text
Fault Priority: 6
Fault Frequency: 1te
Reset counter: 24

Is that bad ?.

I'm not sure at which stage any previous retrofitters hanky panky will show up in blocking changes. Whether that can be seen in the backup or whether that's when you come to flash. That what Chillout warned about but ways around. Something only retrofit units need to worry about.

Thanks all.

I don't think it's a 'SVM' error, this is the text in full, note the reference to Mmx2 device;-

1 Fault Found:
1556 - Internal Control Module Memory Check Sum Error
B2000 87 [009] - Missing message
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 198
Mileage: 20061 km
Date: 2018.09.27
Time: 17:11:12

Voltage terminal 30: 12.2 V
Software module: status-SW_Status_Consistency: 00 08 00
Software module: status-SW_Status_Device: Mmx2Mmx2Mmx2M

This only showed up after I had the unit 'hacked' to enable map updates.

 

[MIB-Wiki]

What did you do to enable it?

You used M.I.B?


Gesendet von iPhone mit Tapatalk

 

[Tell]

Walone blames the error on the but one retrofitter (one back), the last one couldn't clear it. So it must sit in 5F ?. That's all they had to work on since it was sent to them.

 

[Walone]

What did you do to enable it?

You used M.I.B?


Gesendet von iPhone mit Tapatalk

I didn't do it, a retrofitter (Vagtec) did it, they came to my house and connected a laptop to the unit and updated the FEC's (all from a different VIN) but I only got 3 or 4 map updates before the FEC 'expired'.

 

[Tell]

I didn't do it, a retrofitter (Vagtec) did it, they came to my house and connected a laptop to the unit and updated the FEC's (all from a different VIN) but I only got 3 or 4 map updates before the FEC 'expired'.

Ditto me first time round. Same process was used on both of ours first time round. I hassled the guy and got them updated, Walone hassled but the guy played deaf as I remember. I've still got the original mod but FeCs updated... doesn't work with 192... Walone had the board's retrofitter associate (different guy and better) to sort them out but same 192 issue. Hence working to that upgrade .

We are moving forward...

 

[MIB-Wiki]

Well, 192 could not be expected by the modders, as of now there is now official support for seat in general.

Work around is to use e.g. SKODA map Fec. M.I.B is doing this.

Cleanest way is to update FW or reapply same one again via SWDL and patch with M.I.B afterwards.


Gesendet von iPhone mit Tapatalk

 

[Tell]

Working towards it... more of a cloudy day tomorrow so good for sitting in the car on it .

It was Chillout's bragging on Drive and Jose on the Spanish board that alerted me to the 192 solution. Jose says MIB Tools wasn't used. Used a retro-fitter. Taking the DIY route but @jpmedia has offered technical help, like saying no you can install MIB Tools on the existing firmware since GEM is compatible (we have both checked, GEM version 4.1+) so one can take a backup before moving onto 1447. I've distilled the translated German experiences on those DEB forum posts into the notes above. We will find out if the original retro-fitter left a trap.

Will improve the notes when one gets it working and put that in it's own thread and as a resource on the Seat board.

 

[jpmedia]

I don't think it's a 'SVM' error, this is the text in full, note the reference to Mmx2 device;-

1 Fault Found:
1556 - Internal Control Module Memory Check Sum Error
B2000 87 [009] - Missing message
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 198
Mileage: 20061 km
Date: 2018.09.27
Time: 17:11:12

Voltage terminal 30: 12.2 V
Software module: status-SW_Status_Consistency: 00 08 00
Software module: status-SW_Status_Device: Mmx2Mmx2Mmx2M

This only showed up after I had the unit 'hacked' to enable map updates.

THis error is related to a technisat conversion? meanin install 05xx software on 02 xx 03xx 04xx hW revision units?

If Technisat can be NAV CID CFG file, or conversion .if patched over sd update with right prepared files and later rerun fw update error gone away...