Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Switchable maps
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Hardware image switching changes which external nonvolatile memory image the ECU can see. Depending on the ECU's memory map, this can change executable code, calibration data, or both; the dashboard switch does not itself identify the contents or guarantee that an engine can continue running while the image changes.

These examples describe particular products and ECU variants, not a universal pinout. Before selecting or modifying hardware, identify the ECU and software, memory device, socket, bus organisation, electrical interface and recovery method.

Two physical devices or two banks in one device

A dual-device adaptor selects one of two programmed memory devices on the ECU's address and data bus. The inactive device must not contend with the selected device. Flash command, reset, write-enable, output-enable and selection signals also need correct handling, including during programming. The implementation is board-specific: never assume that wiring the outputs of two devices together is sufficient.

A different method puts two complete images in a compatible higher-capacity device and uses an additional address bit to select the upper or lower bank. If the ECU presents a 32 KiB x8 window, a conceptual 64 KiB device can contain image A at byte offsets 0x0000–0x7FFF and image B at 0x8000–0xFFFF. The extra address bit selects the half while the ECU's lower address lines select bytes within it. The Microchip 27C256 datasheet describes a 32 KiB x8 EPROM; the AT27C512R datasheet describes a 64 KiB x8 device. This arithmetic illustrates the principle, not a general replacement or wiring instruction: pin assignments, programming voltage, operating voltage, access timing, byte/word layout and ECU socket connections must be checked against the exact parts.

The EcuVonix Dual EPROM instructions describe using two equal-capacity EPROMs or a single double-capacity EPROM. They recommend changing its selector with the ignition off, and note that some key-code arrangements can prevent starting after switching. Both images must fit the ECU hardware and corresponding immobiliser, coding and software version; not every system stores those items in the same memory.

EDC15P: a documented dual-flash board

A supplier's EDC15P dual-map board describes switching between two independent firmware images for its supported Bosch EDC15P applications using AM29F400BT flash. This is a specific third-party conversion, not an original Bosch feature or evidence that all EDC15 hardware uses the same device.

The Am29F400B device documentation describes 4 Mbit organised as 512 KiB in byte mode or 256 Kwords in word mode, with separate chip-enable, output-enable and write-enable signals and sector erase. Therefore two independent 4 Mbit devices have 512 KiB each, not 4 MiB each. Correct programming depends on the exact top- or bottom-boot variant, package, bus mode and supported programmer. The board, flash and ECU instructions determine which device receives a write and how the write is verified.

The supplier's manual for a stated EDC15P/VM+ board revision claims switching with the engine running. That claim applies only to the documented hardware and setup and is not independent validation for other boards, firmware combinations or operating conditions. The generic EPROM product above instead recommends ignition-off selection. Unless the exact system's live behaviour is documented and independently validated, switch with ignition off and allow the ECU to shut down fully.

ME7: a documented dual-flash board

Another supplier describes an AM29F400BT board for specified Bosch ME7.5 and ME7.1.1 petrol ECUs to select between two independent firmware images. The listing describes board installation and a selector input; neither those details nor any connector, voltage or pin assignments should be transferred to a different board or ECU. Verify exact ECU hardware, flash identification, compatibility and the board's own instructions before proceeding.

ME7 and EDC15 are not limited to external-chip solutions. For comparison, one ME7 software product describes software-based mode selection, with a configurable speed limit for its supported files. One EDC15 software product describes selecting up to three code blocks in supported 512 KiB and 1 MiB files. These products add software logic; their descriptions do not establish a general-purpose chip-switching technique or their exact lookup implementation.

Why running state matters

The processor may be executing code from the external device when it is switched. The ECU can also retain RAM values, control integrators and learned adaptations from the previous image. A physical electrical change is not automatically synchronised with the control loop, and loading one complete image does not automatically reset those states. Depending on design, a running switch can cause a stall, invalid calculation or abrupt torque change even when both images start and run independently.

For any solution advertised as live-switchable, verify its permitted engine conditions, exact firmware combinations, switching boundaries and behaviour under glitches or power loss. Test indication against the actual selected image and values. Never change a selector during a flash program or erase unless the manufacturer specifically documents that operation.

Practical checks

  1. Identify the ECU part number, processor, memory markings, software number, board revision and the claimed adaptor support.
  2. Verify image size, address layout, reset/boot behaviour, checksum requirements and compatibility with the vehicle and immobiliser. Reuse the known-good recovery file and documented recovery route.
  3. Check the exact device datasheets for voltage, package, speed, bus width and programming/erase behaviour. A device with twice the capacity is not automatically electrically or logically compatible.
  4. Check selector wiring, default, mechanical installation, bus isolation and programming path against the exact board documentation. Do not infer another product's pin assignments or switching voltage.
  5. Verify each selected image by an appropriate readback and independent identification. Test ignition-off changes, resets and selector faults before any validated live operation. Log fuelling, boost, requested/actual torque and relevant fault and protection channels under controlled conditions.

Evidence boundary: The product links are vendor descriptions; technical conclusions about a different ECU require its own hardware and software evidence. The illustrative addresses above are device offsets for the simple 32 KiB/64 KiB example, not an EDC15 or ME7 memory map.

Related method pages