Short answer: An ECU checksum is a value calculated from the data in the engine computer's memory. The ECU uses it to confirm that its software is intact. When you change a map, the stored value no longer matches, so it must be corrected before the file is written. If it isn't, the ECU can reject the file or the car may not start.
A remap can have perfect maps and still fail because of this one step. This guide explains what the checksum does, how to check it before flashing, and which tools can correct it.
What is an ECU checksum?
A checksum is an error check. The ECU calculates a value from a block of its memory and compares it with a value stored alongside that data. If the two match, the ECU treats the data as intact.
Think of it as a running total of the memory's contents. Change even a small part of the data and the total changes too. The exact calculation varies by ECU, and many ECUs protect more than one block of memory.
The checksum doesn't judge whether a map is good. A dangerous map with a correct checksum will pass, and a good map with a wrong checksum will fail.
Why does a modified file need a correct checksum?
A modified file needs a new checksum because tuning changes the data the original value was calculated from. Even a small edit to one map makes the stored value out of date.
Correction means calculating a new value from the modified data and storing it where the ECU expects to find it. The ECU then sees matching values and accepts the software as intact.
This is one stage in a longer process. Our guide on how a chiptuning file is made shows where it fits: after the map changes and before writing the file.
What happens if the checksum is wrong?
The most common result is that the car won't start or the ECU refuses the file. What you see depends on the ECU and on the tool used to write the file.
Common signs after writing a file include:
- The engine cranks but doesn't start.
- The programming tool reports an error or refuses to write the file.
- The ECU stops communicating with the diagnostic or programming tool.
These signs don't prove the checksum is the cause. An interrupted write, low battery voltage or a file for the wrong software version can look the same.
If this happens, don't keep retrying with different files. Stabilise the battery voltage, confirm the tool still communicates with the ECU, and write your original backup if the tool allows it.
How to check a checksum before flashing
Check the checksum on your computer, after the last map edit and before you connect to the car. The exact menus differ by tool, but the order stays the same.
- Keep the original read untouched. Save a copy with the car, ECU type and software number in the file name.
- Finish every map change first. Any later edit makes the corrected checksum out of date.
- Open the modified file in your checksum tool. Choose the correct ECU type if the tool asks for it.
- Run the check. Read the result for each block if the tool reports more than one.
- Correct it and save a new file. Keep the uncorrected version separate so the two aren't confused.
- Check the saved file again. This confirms that the file you will write is the corrected one.
- Compare it with the original. Only the areas you meant to change, plus the checksum values, should differ.
Watch a short example of a checksum check in ECM Titanium: Is your ECU map OK?
Also avoid changing data outside the area the checksum routine expects. Some tools warn you about this, and HP Academy's checksum explainer notes that WinOLS does.
Which tools can correct a checksum?
Three kinds of tool can do it: your flashing tool, a map editor with a checksum module, or a standalone corrector. Before you rely on any of them, confirm that it supports your exact ECU.
| Tool type | Examples | How it fits the job |
|---|---|---|
| Flashing tool | Your read/write interface | Many modern tools correct the checksum automatically while writing. Check that yours does this for your ECU. |
| Map editor | ECM Titanium, WinOLS | Lets you edit maps and handle the checksum in one place, if a module or driver covers your ECU. |
| Standalone corrector | Checksum Corrector for ECU Files, Ultimate Checksum Corrector | Useful when your editor or flashing tool doesn't correct the file. You load the file and run the correction. |
| Hex editor | HxD (free) | Useful for inspecting a file and comparing it with the original. It doesn't know your ECU's checksum routine, so it isn't a corrector. |
If you're not sure your flashing tool corrects the file, use a separate check. Don't assume it happened because the write finished without an error.
Which ECUs need special attention?
Newer and more complex ECUs need the most care, because the same checksum routine doesn't work across every ECU family. Even two ECUs from one family can differ, so match the tool to the exact ECU and software version.
- Bosch EDC16: See our EDC16 Stage 1 remap guide for the map order. Correct the checksum after the final map change.
- Bosch EDC17: See our EDC17 chipping guide before you start. Confirm that your tool supports reading and writing your variant.
- Newer ECUs: Some use extra protection beyond a basic checksum, such as software signatures. A simple corrector may not be enough, so check the tool's support list first.
Pre-flash checklist
Go through this list before every write, even on an ECU you have tuned before.
- ☐ The original file is backed up in at least two places.
- ☐ The ECU type and software number match the modified file.
- ☐ All map changes are finished.
- ☐ The checksum is corrected and checked again in the saved file.
- ☐ The modified file differs from the original only where you intended.
- ☐ The battery is supported by a stable power supply.
- ☐ The laptop is plugged in, with sleep mode and updates turned off.
- ☐ Your tool supports this ECU and this read/write method.
- ☐ The car has no existing faults that could be confused with a tuning problem.
After writing, clear any stored faults, start the engine, and log data on a test drive. Keep the original file in case you need to go back.
Frequently asked questions
Does my flashing tool correct the checksum automatically?
Often, yes. Many modern tools do it during the write, but it depends on the tool and the ECU. Check the documentation for your exact setup.
Can a wrong checksum damage the ECU?
A wrong checksum usually stops the ECU from accepting or running the software. Recovery depends on the ECU and your tool. That is why you need an original backup and a tool that can write it back.
Do I need to correct the checksum after a small change?
Yes. Any change to protected data makes the stored value out of date, however small the change is.
Does a correct checksum mean my tune is safe?
No. It only shows that the ECU's integrity check will pass. Safe limits for boost, fuel and torque still have to be checked, for example by logging data on a test drive.
Is remapping legal?
It depends on your country and how the car is used. A remap can also affect your warranty, insurance and roadworthiness. Check the local rules, and never remove or disable emissions equipment on a car used on public roads.