Scope
This guide addresses file interpretation for identified VAG Bosch EDC16 applications. It is not a programming protocol, a connection diagram or a rule that files from U1, U31, U34 and CP34 are interchangeable. First record the exact engine, controller and software identity. General integrity arithmetic and validation are covered in ECU checksums: identification and workflow.
Three questions that need separate answers
- What was obtained? Establish which memories/regions came from this ECU, which were supplied from a server, and which bytes are a container, padding or a tool transformation.
- What was checked? Record the checksum module, supported format, detected blocks and any program/calibration compatibility handling.
- What can the chosen method restore? Establish the writer's supported recovery operation and required data for the exact hardware/software and protocol.
A nominal file size, a checksum pass and a successful identification response do not answer all three questions.
Read method and file meaning
| Term or artefact | What the evidence establishes | What still needs checking |
|---|---|---|
| Virtual read | AutoTuner describes retrieving a corresponding original from its server using ECU identification. | That is not a byte-for-byte observation of an existing modified calibration in the ECU. |
| Real read / calibration file | A read can obtain data from the connected ECU. AutoTuner separately advertises OBD real-read and bench real-read protocols for named EDC16 applications. | Obtain the exact protocol's region/memory coverage; "real" does not itself mean complete. |
| Bench access and BDM access | Manufacturer tools describe distinct connection methods. EVC's BDM100 uses board pads on its supported MPC5xx hardware. | Record the actual method and instructions. A connector-based bench session and a board-pad BDM session are not interchangeable labels. |
| Vendor recovery archive | AutoTuner documents a separate boot/bench backup file and says an OBD read does not save that backup file. | Verify the actual archive contents and restoration support. Its illustrated TriCore iflash/dflash layout is not a memory map for a VAG MPC5xx EDC16. |
Sources: AutoTuner's bench-method definition, AutoTuner: meaning of the read/identify buttons, EDC16/PPD OBD release, EDC16 bench release, backup-file documentation, and EVC BDM100 hardware documentation. Coverage announcements are dated examples; use current instructions for the connected controller. The BDM100 list includes different VAG EDC16/EDC16+ processor, flash and EEPROM combinations, demonstrating why one file-length rule is insufficient.
A 2009 T5 read as an example, not a universal layout
Reported case, October 2020: a 2009 T5 1.9 TDI read using MPPS V13 with the EDC16U34 selection produced a nominally 2 MB file with many empty-looking areas and a data-area-only message. Read scope and correction during writing were discussed in replies. The report does not independently establish the installed ECU variant, engine code, complete software identity or validity of the proposed tune. NefMoto: EDC16 OBD flash possible without brick?.
File-review implication: examine the read report and format before interpreting blank-looking regions. Do not fill gaps with a donor image, assume every byte was read, or transplant the report's internal/external-memory explanation to another board. A larger file can represent the same limited coverage with padding; length alone cannot verify either completeness or corruption.
Checksum correction and compatibility are separate concerns
EVC describes EDC16/17 memory blocks for operating system, program and map data, with a compatibility structure connecting them. It explains that a data area can be programmed separately and that program changes require corresponding map-area programming, with implementation differences between ECUs. This supports checking the actual block dependencies; it does not make arbitrary program/calibration mixing safe. EVC: compatibility-test checksum.
EVC lists a Bosch EDC16 module, OLS285, separately from other controller modules. Its correction FAQ says some modules require the unmodified vehicle data as the project's original; otherwise detection or correction can fail. Establish actual detection and reports for the file instead of selecting a correction tool solely because its name contains "EDC16". EVC checksum-module list; EVC checksum-correction FAQ.
Reported case: in a related October 2020 NefMoto checksum question, a generic corrector found no checksum, and a WinOLS-corrected export was supplied while the calibration was criticised. Correction and calibration quality were separate issues; no successful or safe vehicle result is established.
A protocol checksum is not every integrity layer
A May 2026 NefMoto EDC16U31 protocol post describes a programming-validation routine and its author's implementation/testing claims. The text does not establish an exact VAG software match for any particular vehicle. A reported transfer/routine check must not be promoted to the sole checksum algorithm for all EDC16 files, nor to proof that cross-flashing is safe. Use evidence for the exact image, controller and writer.
Make the result reviewable
- Retain the appropriate original read and its provenance; record hardware/software IDs, protocol, file length, format and hash.
- Document which regions were read and which the writer will change. Keep calibration, program, EEPROM and container metadata distinct.
- Record editor/checksum module and writer versions, options and output reports. Investigate unsupported or unrecognised checks; a greyed-out button does not define another tool's behaviour.
- Review the exported bytes and explain changes caused by the intended edits, supported correction and documented writer transformations. Establish recovery with the supported tool before programming.
- After a write, use supported verification and diagnostic checks and confirm the intended identification. A valid integrity result does not validate torque, fuelling or hardware behaviour.
Not established
This is an editorial workflow; no ECU was read, flashed or recovery-tested for this article. The supplier documentation establishes its own tool behaviour and examples. The 2020 T5/checksum and 2026 U31 reports were reviewed as publicly indexed forum posts, and attachments were not validated. No universal memory offsets, security algorithm, checksum recipe or cross-flash compatibility is asserted. Reviewed 16 November 2026; the NefMoto pages could not be retrieved directly.