Skip to content

Import

MRC Tuner Rom reads many source formats. A2L usually gives the most trustworthy result, because a definition file pins down map addresses, sizes and physical scaling.

A2L / DAMOS

The most reliable path. ASAM MCD-2 MC (A2L) is the standard description that ships with the ECU software.

  1. Import the ROM first and create a project.
  2. Choose Project ▸ Import A2L and select the .a2l, .dam or .damos file.
  3. The application resolves the addresses in the A2L against your ROM.

What is taken from the A2L:

A2L construct Use
RECORD_LAYOUT Byte size, byte order, signed/unsigned
STD_AXIS, COM_AXIS, FIX_AXIS Axis definition and axis scaling
COMPU_METHOD Factor that converts to physical values
ECU_ADDRESS Base address hint

Base address detection

A2L addresses are relative to a 24-bit or 32-bit base. The application tries a table of common ECU base addresses (MED17, EDC17, ME7, Simos, RH850, MPC …) and picks the one consistent with the ROM size. If needed, correct it manually via View ▸ Data Width and Byte Order.

Intel HEX and Motorola S-record

.hex, .s19, .s28 and .s37 files open directly. The application resolves record addresses, preserves gaps and converts the data into a byte array.

HEX output

Writing Intel HEX and S-record is available through the Lua API (writeIntelHex, writeSRecord). Project ▸ Export ROM offers only .bin and .rom.

Raw dumps

.bin, .rom, .ori and .mpc files are taken byte for byte. In a raw dump there is no record of where a map starts or ends. In that case:

  1. run Miscellaneous ▸ Auto-detect Maps, or
  2. import an A2L, or
  3. define maps by hand with Find ▸ Map when you know the address.

Auto-detection is a guess: review every map it finds.

WinOLS (.ols)

An .ols file is a complete container that includes the ROM data. Import brings across:

  • ROM data,
  • map name, description, address, dimensions, cell size and scaling,
  • axis definitions with their real breakpoint values,
  • vehicle/engine/ECU metadata.

OLS projects containing several firmware versions are imported as a single project with all versions.

Project ▸ Export OLS writes your project back to .ols.

KP map packs (.kp)

KP packs carry map definitions, not ROM data, so a project with ROM data must be open before importing. The application

  • resolves addresses against your ROM (scoring Tricore-style 0x80xxxxxx and flat file offsets),
  • drops entries that duplicate maps already in the project,
  • files new maps into folders grouped by name prefix.

Legacy 4.x packs do not always store dimensions; the application recovers columns × rows by matching the product against the cell count.

TunerPro (.xdf)

.xdf definition files can be imported and exported.

VAG containers (.frf, .sgo, .odx)

.frf, .sgo, .odx and .zip files containing them are supported. Encrypted content requires an external 32-byte AES key/IV file.

CSV and JSON map lists

Project ▸ Import CSV Map List defines map addresses in bulk from a list file; Export writes the list back out.

After importing

  • enable Miscellaneous ▸ Auto-scan to run map discovery after each import;
  • if the scaling looks wrong, fix factor and offset in the Map Properties dialog — the displayed values follow it directly.