Bosch EDC15 is a family of diesel engine controllers, not one fixed memory layout or map-switch feature. On supported VAG EDC15P/P+/VM+ applications, two documented third-party approaches are (1) modifying software to select between calibration/code blocks within one flash image and (2) fitting a dual-flash adaptor that makes one of two complete external memory images visible to the ECU. These approaches change different things and should not be treated as interchangeable.
Scope: Examples below describe specific supplier products and engineering principles. They do not establish coverage of every EDC15 variant, an OEM Bosch feature, a particular binary's addresses or safe live switching. Identify the exact ECU hardware, software number, flash device, vehicle coding and the selected product's supported file before proceeding.
Start with the exact ECU and read
Record the manufacturer and vehicle part numbers, Bosch hardware number, software number, engine and injection system, transmission and drivetrain, memory part and the tool's read type and size. The Chip & Tune EDC15 tool description explicitly mentions pump-injector (PD) and distributor-pump (VP) layouts and 512 KB 29F400 or 1 MB 29F800 files. That is a statement of the vendor's advertised product scope, not a guarantee for every ECU with that memory marking.
The NorTuner EDC15 service explicitly requests an exact 512 KB full flash read and lists VAG EDC15P, P+ and VM+ while excluding other EDC15 variants and makes. It says a partial read may not work. These tools have different stated scope; never fill a partial read to the expected length and assume it is a complete, valid flash image. Reuse the known-good read and a documented recovery method for the exact controller.
Method 1: software selection of calibration/code blocks
Chip & Tune describes a patch that detects the PD or VP file layout, uses three code blocks as independent maps, copies missing blocks when required and adds switching logic. Each block is subsequently edited in a compatible calibration editor. Its input is pedals or the cruise-control lever; the vendor describes a tachometer indication of 1,000, 2,000 or 3,000 rpm at ignition-on for the active mode, and optional storage of selection in EEPROM. The vendor says to correct checksums using the user's own tools before flashing.
That documentation establishes the supplier's described behaviour; it does not disclose its exact patch addresses, register usage, copy boundaries, power-fail strategy, or every individual table that differs. A “code block” label does not prove that all executable code, diagnostic data or the entire ECU state is independently duplicated. The display is feedback, not proof that every expected lookup uses the intended data. Confirm the precise software version, selection procedure and included map definitions with the supplier.
Concrete contrasting example: an experimental extra-block option
The NorTuner product describes up to three modes selected using existing pedals. Its optional creation of additional code blocks is explicitly labelled experimental: it states that, for supported one- or two-block files, missing blocks are placed in free flash space if they fit, otherwise processing fails. The same page specifies a full 512 KB read and says its brake-based selector gives tachometer feedback; its cruise-control option is described as forthcoming. Its published sequence holds the accelerator with the ignition on and uses brake presses within an approximately seven-second selection window; the tachometer displays modes 1–3 and returns to normal after the window. This is a vendor-specific procedure and must be used only in the permitted conditions for the exact implementation. This is a separate product with its own constraints and must not be conflated with the Chip & Tune implementation.
In particular, three physical-looking repetitions in a file are not necessarily three driver modes. Different blocks can represent vehicle configurations or unused variants. The open-source VAGEDCSuite EDC15P6 parser contains heuristic block identification and separate gearbox-type detection. It is evidence of how that editor analyses some files, not an authoritative Bosch definition, an active-block trace, or proof that a block is switchable. Validate a candidate against that exact file and running control path.
Engineering interpretation: page-based addressing
On an ECU actually verified to use a Siemens/Infineon C167-family processor, its CPU manual documents four data page pointers (DPP0–DPP3). For standard direct or indirect long 16-bit data addresses, the selected DPP supplies the page and the remaining 14-bit offset identifies a byte within a 16 KiB page; extended instructions can override that addressing. Up to four such pages can be active at once. This is a CPU capability, not evidence that either commercial switch above changes DPP registers.
Hypothetical arithmetic only: with a standard access selecting DPP0, a page value of 0x20 and offset 0x1234, the conceptual physical address is (0x20 × 0x4000) + 0x1234 = 0x81234. If the page value became 0x24, the same offset would resolve to 0x91234. These are invented numbers to demonstrate page translation, not ECU addresses, a verified EDC15 map location or a modification recipe.
Where multiple DPPs, overrides, far references or copied RAM variables are involved, changing one page pointer alone would not necessarily switch a complete coherent calibration. Confirm actual processor, addressing modes, interrupts and all relevant consumers before concluding how a specific binary selects a block. The C167 programming manual describes page and segment override instructions; the MCU manual alone cannot identify what a tuner patched into a particular EDC15.
Method 2: physical dual-flash hardware
The Inovauto EDC15P board listing describes two independent firmware images for a supported EDC15P using AM29F400BT external flash. The accompanying board instructions identify EDC15P and VM+ versions and warn that their board firmware differs. For the stated board versions the vendor describes a +12 V selection input, the first flash as the normal programming target, and the second as the target when that input is energised. The same manual explicitly warns that +12 V must not be applied to the separate boot output. These signal descriptions are specific to that board, not ECU connector pin assignments. It claims switching while running for the stated board version; that vendor claim is not validation for another board, ECU, image pair or operating condition.
This arrangement can change executable code and other data stored in the chosen external flash as well as calibrations. The two images need matching hardware and vehicle compatibility; immobiliser, coding and learned data may reside elsewhere. Bus contention, selected-device programming, reset, supply, signal levels and input default are board-specific. The generic Dual EPROM manual instead recommends switching with ignition off. Until an exact implementation is proven safe for running changes, select at ignition-off and allow full ECU shutdown.
A 29F400 is 4 Mbit: the Am29F400B datasheet documents 512 KiB × 8 or 256 Kiwords × 16 organisations. Two 29F400 devices therefore hold two 512 KiB byte-mode images, not two 4 MiB images. Confirm device top/bottom boot suffix, package, bus mode, programming and exact ECU layout; component density alone is not a wiring or compatibility guide.
What needs to change together?
For a diesel mode, consider the complete requested quantity, torque and smoke-limiting path alongside air and boost control and injection timing or duration, as applicable to the engine. The actual active minimum, operating condition, temperature correction or fault response may be shared or located outside a selected block. Also consider gearbox coordination, pressure and temperature protection and hardware capacity. These are calibration dependencies to investigate; a vendor's product description is not a complete map inventory.
| Item to verify | Block-selection patch | Dual-flash adaptor |
|---|---|---|
| Input and feedback | Software interprets existing controls and reports a mode if implemented. | Board-specific electrical input selects the visible device; any ECU feedback depends on implementation. |
| Data selected | Vendor-defined blocks or selected data, with shared material still possible. | Contents of the selected external flash device, potentially including code. |
| Stored mode | Optional EEPROM persistence on the documented software example; check startup and invalid-state behaviour. | Determined by board input and electronics; do not assume EEPROM storage. |
| Programming and integrity | Verify each affected block, compatible definitions and checksums for the exact image. | Verify which device is selected for each write, and each complete image's identification and integrity. |
Verification and fault cases
- Document the exact ECU and software identity, original flash/read type, device markings, selector implementation, supported maps, default and intended recovery path. A file from a different vehicle or firmware is not a substitute for matching evidence.
- Build a mode matrix of requested quantity, limiters, injection and air functions, shared maps, corrections and protections. Verify definitions, axes, units and actual code references; check per-block and whole-image integrity as applicable.
- Prove which mode is active using supported logging, trace, readback or operating values in addition to the indicator. Confirm which physical flash is written before and after selection for a supported adaptor.
- Test initialisation, ignition cycling, rejected and repeated requests, invalid/floating input, power interruption, selection storage and any adaptations shared across modes. Preserve vehicle functions of reused pedals or cruise controls.
- Validate each calibration separately and transitions in a controlled environment. Log requested and actual boost, fuelling or injection quantity where available, air, temperatures, faults and intervention; retain appropriate engine and drivetrain safeguards.
Evidence note: The product pages are vendor descriptions. The generic C167 discussion explains an addressing mechanism; the specific behaviour of an EDC15 image must be established separately. Observe applicable road-use and emissions requirements.