Bosch MED EEPROM Tool – checksum repair 1.0

New release thread for Bosch MED EEPROM Tool – checksum repair: discuss, share feedback, and get help.

Bosch MED EEPROM Tool – checksum repair​#

Solves P0601 checksum faults, restores EEPROM integrity, quick bench workflow

View attachment 3916

Highlights
• Corrects EEPROM CRC/P0601 errors automatically
• Reads, edits and rewrites 95080 / 95320 dumps in seconds
• Displays ECU identifiers (HW-/SW-/Part-No., VIN) for documentation
• Built-in backup / restore to protect original data
• Stand-alone Windows utility; no internet activation required

[ATTACH type="full" alt="MED9.5.10 tool main window showing EEPROM load and P0601 repair...​

Click to expand...

What's inside:

• Overview & screenshots
• Version history and compatibility
• Download link and setup notes

View full details and download — Bosch MED EEPROM Tool – checksum repair

This program doesn’t work; it doesn’t fix anything. Just a waste of time.

konstanti said:

This program doesn't work; it doesn't fix anything, so the time spent was wasted.

Click to expand...

Hello,

To determine exactly what isn't working, please clarify a few points:

1. What exactly are you loading — a full EEPROM dump (95080 / 95320), or is it a flash dump of the entire ECU?
2. What is the file size? For 95080, it is usually 1 KB (1024 bytes); for 95320, 4 KB (4096 bytes). If the size is different, the utility will not recognize the structure.
3. What did you use to read the EEPROM — which programmer (XPROG, Orange5, UPA, TNM, etc.) and in what mode?
4. Which specific ECU is it — the HW number and SW number from the unit's label?
5. After pressing "FIX EEPROM", does the program display any message, or does it simply save the file without changes?

The most common reasons why it “doesn't fix anything” are:

• Incorrect dump type — a flash dump (512 KB / 1 MB) was loaded instead of a separate EEPROM dump. The utility is designed specifically for an external 95xxx chip, not the internal flash.
• The dump is already correct — if the CRC in the file matches, the program makes no changes (there is nothing to fix).
• Wrong ECU — the tool is designed for Bosch MED 9.5.10 (VW 1.6 FSI / 2.0 FSI). If you have MED 17.x or another Bosch unit, the EEPROM structure is different and the utility will not process it.

Post the information above, and we’ll look into it specifically.

The EEPROM dump is a full 1 KB. I tried loading a 4 KB one, but the program does not accept it. It was read using ktag. I press Fix EEPROM; the dump is saved and a couple of bytes in it are changed, BUT the error remains exactly as it was p0601. I’m attaching a screenshot of the ECU.

konstanti said:

The EEPROM dump is a full 1 KB; I tried feeding it a 4 KB one, but the program does not accept it. Read with ktag, on...

Click to expand...

Thanks for the photo, the picture is clearer now. The unit is confirmed:

• VW Part: 06F 906 056 GN (SW-ref: 06F 906 056 EK)
• ECU: Bosch MED9.5.10, HW: H03
• Bosch Nr: 0 261 S02 344
• Engine: 2.0 FSI (BLR/BLY/BVY/BVZ)

The unit is indeed MED 9.5.10 — the utility is intended for it. Since the program changes a couple of bytes and saves the file, it must be recalculating the CRC. But P0601 remains — let’s dig further.

Main reasons why P0601 does not clear after EEPROM correction

1. The issue is not in the EEPROM, but in the internal flash
P0601 on MED 9.5.10 — this is Internal Control Module Memory Checksum Error. This error can be generated not only by a corrupted EEPROM (95080), but also by a damaged checksum in the main flash (internal/external processor flash). The utility only corrects the EEPROM — if the issue is in the flash, it will not help.

What to check:

• Read the KTAG-om full flash (internal + external) and check its checksum using WinOLS or ECM Titanium — see whether there is a CS error in the flash area.
• If the flash is damaged, it is that which needs to be restored (the original firmware for 06F 906 056 EK/GN).

2. Incorrect EEPROM reading/writing via KTAG
KTAG when reading the MED 9.5.10 EEPROM, it sometimes reads not a clean 95080 dump but a wrapped format. Check:

• The file size must be exactly 1024 bytes (1 KB). If it is 1025, 2048, or another size, the format is incorrect.
• Try reading the EEPROM directly from the 95080 chip using an SPI programmer (XPROG, Orange5, UPA, TNM5000) — this will provide a guaranteed clean dump without wrappers KTAG.

3. Hardware fault
If both the flash and EEPROM are correct, but P0601 does not clear, a fault is possible:

• The 95080 chip itself has degraded (does not retain data) — replace it with a new one and write the corrected dump
• An issue with the processor or bus — in that case, the unit must be replaced

Recommended procedure

1. Read the full flash (KTAG → MED9.5.10 → Full Read) and check the checksum of the flash section
2. If the flash CS is corrupted, restore the original 06F 906 056 EK firmware and recalculate the CS
3. If the flash is fine, read the EEPROM directly from the 95080 chip with a programmer (not via KTAG), run it through the utility, and write it back
4. Clear the errors using VCDS/ODIS, cycle the ignition 2–3 times

If possible, post both dumps here (flash + EEPROM), and we will look at exactly where the issue is.

The program does not load the EEPROM here.

konstanti said:

EEPROM attached

Click to expand...

Thanks, but I don't see an attached file in the message — perhaps it didn't upload.

Please attach the EEPROM dump again (in .bin, .ori or .hex format; the size must be exactly 1024 bytes for 95080).

Also, if possible, attach the full flash dump as well — this will allow us to immediately check exactly where the checksum error is: in the EEPROM or in the flash area.

I'm waiting for the files — we'll look into it specifically.

Password reguired ?? anyone know?