Which ECU file should you upload? Full flash read, partial read, EEPROM or full backup
Full flash read, partial read, EEPROM or full backup? What each ECU file type is, how EcuPrime reacts to it, and which file to export from your tool before uploading.
Most problems with a tuning file service start before any map is touched: the file that gets uploaded is not the file the job needs. A read tool can save several different things from the same ECU - the main flash, only the calibration area, the external EEPROM, or a complete backup package - and only one of them is the starting point for a Stage 1 or any other software modification. This guide explains the four file types we see, how the EcuPrime platform reacts to each one, and what to export from your tool before you upload.
All figures below were measured on our live system on 2 October 2026. They refer to single ECU families or fixed platform rules, not the size of the whole library.
The short answer: upload the full flash read (ORI)
Tuning solutions are applied to the ECU processor's flash memory. The file you want is the complete, unmodified read of that flash - usually called the ORI (original) file. It contains the program code, the calibration data and the identification strings (hardware number, software number, part numbers) that let a platform recognise the ECU and find matching donor solutions.
If you only remember one rule: upload the original flash read exactly as your tool saved it, before anyone has edited it. Do not upload a file that has already been tuned, and do not upload an EEPROM or a whole tool package instead of the flash.
What a correct full read looks like
For most ECU families the full flash has a fixed size, so the file size is the first quick check. On 2 October 2026 we looked at the indexed donor files in our library for a few common families:
- Bosch EDC16C34: 493 of 503 indexed donor files are exactly 2,097,152 bytes (2 MB). The handful of other sizes are individual cases, not the normal full read.
- Bosch EDC17C46: all 52 indexed donor files are 2,097,152 bytes.
- Continental SID807: both 2 MB and 4 MB files appear (6 and 5 indexed files), so for this family size alone does not tell you which variant you have - the identification strings do.
If your EDC16C34 read is much smaller than 2 MB, treat it as a warning sign that the read did not complete. You can see which operations exist for these families on the Bosch EDC16C34 ECU page and the Continental SID807 ECU page.
Partial read: mostly empty, often only the calibration area
A partial read happens when the tool reads only one region of the flash (often the calibration area), or when a read was interrupted. The saved file can still have the expected size, but most of it is blank padding (0xFF or 0x00).
Blank space on its own is not proof of a bad read. Legitimate flash files contain large padded areas: when we measured live customer files in September 2026, a third of correctly recognised files were at least 80% blank. None of them, however, reached 95%. That is the threshold the platform uses: if a file is 95% or more blank, or the identification step reports a partial read, and no exact donor match proves otherwise, the upload is reported as a possible partial read rather than an "unsupported ECU".
The difference matters. "Unsupported" sends you looking for another service; "partial read" tells you the fix is on your side: read the ECU again in full and upload the new file. If the file does match a known donor, that match proves the read is complete and the warning is not shown.
EEPROM: useful, but not for tuning
Many ECUs have a small external or emulated EEPROM that stores immobiliser data, adaptations and counters. It is important for immobiliser work and for restoring an ECU, but it does not contain the engine calibration maps that a Stage 1 file changes.
The platform treats any upload of 64 KB or smaller as an EEPROM-sized file. When such a file cannot be identified, the message explains that tuning needs the full flash (ORI) file instead. Keep your EEPROM read safe - just don't send it as the tuning file.
Full backup or tool package: extract the flash first
Bench and boot-mode tools often save a complete backup: flash, EEPROM, sometimes data flash and other areas, all in one container or project file. These are excellent for recovery, but they are not a flash read in the format a tuning file service works on.
On 2 October 2026 the largest ECU flash file in our donor library is 16,777,216 bytes (16 MiB). An unidentified upload larger than that is treated as a full backup or tool package, and the message asks you to export only the FLASH (ORI) file from your tool and upload that.
Already-modified files
A file that has been tuned before is not an original. Applying a solution learned from an original file on top of someone else's modification can lead to a file nobody has validated. When identification suggests a file may already be modified, the platform does not process it as an ORI; it is flagged for expert review instead. If you have the original read from before the earlier tune, upload that one.
A checklist before you upload
1. Read the full flash, not only the calibration area, and keep your tool's original output untouched.
2. Check the file size against what is normal for the ECU family (for example 2 MB for EDC16C34).
3. Keep the EEPROM and any full backup in your own archive, separate from the tuning file.
4. If your tool saves a project or backup container, export only the flash (ORI) file.
5. Note the hardware and software numbers from the ECU label or in your tool - they help if expert review is needed.
6. Store a copy of the original read before you write anything back to the car.
What happens after the upload
When you upload a file, the platform identifies the ECU, compares it with donor solutions from the same family and shows which operations can be applied - this pre-analysis is free. Credits are used only when a file is successfully delivered; if a requested operation cannot be applied, the job is not delivered and the credit is returned. When a result cannot be verified against a donor, it is labelled for review rather than presented as confirmed.
Checksum correction is a separate step. Many ECU families are corrected inside the platform, but modern ECUs with RSA-signed software need an external tool; the platform detects these and shows a warning instead of writing a checksum it cannot confirm.
If you work with files for customers, our chiptuning file service page explains the whole workflow, and the Stage 1 solution page lists the ECU families with Stage 1 support. To see how your own read is recognised, create a free account and upload the original flash file.