Book a demo

04 / 07 — HexxAvailable

The A2L aware hex editor for ECU flash images.

Named maps, not raw addresses, with checksums recomputed on save.

Bridge the chasm between raw memory bytes and engineering meaning. Open Intel HEX, Motorola S-record, and raw binary files, decode named maps via A2L descriptions, edit in physical units, and write checksum-safe output.

Request Hexx access See HELIX suite

In pilot with Tier-1 powertrain teams

Hexxecu_base.hex + engine.a2l Live
80A1C40000B000F00130017001B001F00230028
80A1C50000D001100150019001D002000240028
80A1C60000F00130017001A001E002100250029
80A1C70001100150018001C001F002300260029
80A1C8000140017001A001D002000240027002A
80A1C9000160019001C001F002200250028002B
80A1CA00018001B001E0020002300260028002B
80A1CB0001B001D001F0022002400270029002C
KFZW ignition map · °CRK
1000rpm →7000
KFZW[2,3] @ 0x80A1C66 · raw 0x001A × 0.75 = 19.6 °CRK CHECKSUM OK
Intel HEX · S19 · A2L-decoded · checksum recomputed on write
File formats
Intel HEX (.hex), S-record (.s19/.s37), BIN
Symbol resolution
ASAM A2L description pairing
Map types
Scalars, 1D curves, 2D maps
Safety
Checksum auto-detect + recompute on write

Capabilities

What Hexx does.

  1. D1

    A2L-Aware Memory Decoding

    Transform anonymous hexadecimal hex dumps into named calibration tables, conversion formulas, and physical units.

  2. D2

    Synchronized 3D Map Editing

    Rotate, reshape, and interpolate 3D calibration surfaces visually while underlying bytes update instantaneously in real time.

  3. D3

    Checksum-Safe Write Pipeline

    Hexx detects checksum regions in the image and recomputes them automatically when you write changes, then validates integrity before you flash.

  4. D4

    Direct Binary Comparison

    Byte-level and map-level visual diffing highlighting modified memory records, shifted addresses, and altered characteristics.

A2L MEMORY DECODING & MAP SPECIFICATION

Direct translation from raw hex offsets to physical calibration matrices.

Typical Bosch MED17 / MD1 Flash Memory Map

Hexx decodes raw hexadecimal flash dumps into named engineering maps using ASAM MCD-2 MC (A2L) description files:

Map Identifier Physical Function Flash Address Dimension Axes & Engineering Units
KFZW Ignition Timing Angle Base Map 0x0084E200 16 × 12 (16-bit) X: nmot_w (RPM) • Y: rl_w (Load %) • Z: °KW Crank Angle
KFMIRL Target Indicated Engine Load 0x00851840 16 × 16 (16-bit) X: nmot_w (RPM) • Y: ped_w (Pedal %) • Z: Indicated Torque (%)
LAMFA Target Lambda for Component Protection 0x00858910 8 × 12 (8-bit) X: nmot_w (RPM) • Y: tco (Coolant °C) • Z: λ Target (0.75 – 1.00)
KFLDHBN Maximum Permissible Boost Pressure 0x008621A0 12 × 16 (16-bit) X: nmot_w (RPM) • Y: pamb (Ambient mbar) • Z: Absolute Boost Limit (mbar)

Checksum detection & recompute on write

Hexx auto-detects checksum regions and recomputes them on write, then validates integrity before you flash:

  1. 01 Image in release_v4.2.hex 4,194,304 bytes
  2. 02 A2L matched 14,892 symbols engine_rev_c.a2l
  3. 03 Map edited KFZW · 6 cells 0x0084E200 – 0x0084E380
  4. 04 Checksum 0x9E4B21F0 → 0x4D81C3AA recomputed, written at 0x0087FFE0
  5. 05 Validated Flash-ready integrity check passed
Show the tool output
hexx_checksum_daemon
[hexx] ingested   release_v4.2.hex  (4,194,304 bytes)
[hexx] a2l match   engine_rev_c.a2l  (14,892 symbols)
[hexx] map edited  KFZW  0x0084E200 - 0x0084E380  |  6 cells modified
[hexx] region      flash sector 0x00800000 - 0x0087FFFF modified
[hexx] checksum    block region detected, recomputing
[hexx] old 0x9E4B21F0  ->  new 0x4D81C3AA   written at 0x0087FFE0
[hexx] validate    integrity check passed — image is flash-ready

Workflow

From input to decision.

  1. 01

    Ingest Binary

    Load S-records or HEX files alongside the corresponding A2L description file.

  2. 02

    Inspect & Edit

    Navigate named maps, tweak curves in engineering units (°C, mbar, RPM), or adjust raw bytes directly.

  3. 03

    Verify & Export

    Run automated integrity checks, recalculate checksums, and export flash-ready binary images.

Why it exists

A hex dump no one understands is a hazard.

Hexx gives embedded calibration engineers surgical control over every byte in flash memory without losing the high-level engineering context of labels, axes, and physical units.

Hexx is the hex & binary editing engine from the HELIX calibration suite, available as a focused standalone product. Every edit is applied against a Base/Reference dataset with batch updates and full change tracking.

Positioning

Hexx vs a plain hex editor.

A normal hex editor shows you bytes and leaves the address math to you.

CapabilityPlain hex editorHexx
A2L awarenessManual address mathAuto-decoded named characteristics
Map editingRaw byte nudging1D/2D cell editor in engineering units
Axes & limitsNoneBreakpoints, units, upper/lower limits enforced
ChecksumsManual or pluginAuto-detect + recompute on write
FormatsOften one at a timeIntel HEX / S19 / S37 / BIN
VisualizationHex rows onlyByte-trace viewer, 8/16/32-bit, memory regions
Change safetyNo validationReference diff + pre-flash validation
WorkflowStandalone toolPart of the HELIX calibration lifecycle

Questions

Asked by engineers, answered plainly.

What file formats does Hexx open and edit?

Hexx reads and writes Intel HEX (.hex), Motorola S-record (.s19, .s37) and raw binary (.bin) ECU images. It pairs any of these with an ASAM A2L (.a2l) description so addresses are decoded into named calibration characteristics. Files are written back in the same format with checksums recomputed.

How is Hexx different from a normal ECU hex editor?

A normal hex editor shows you bytes and leaves the address math to you. Hexx is A2L-aware: it decodes the image against your ECU description, surfaces named 1D and 2D calibration maps, and lets you edit them in physical engineering units with axis breakpoints, units, and upper/lower limits — instead of nudging raw bytes by hand. It also auto-detects checksum blocks and recomputes them on write.

Is Hexx an ECU checksum correction tool — does it keep the image valid after an edit?

Yes. Hexx detects checksum regions in the image and recomputes them automatically when you write changes, then validates integrity before you flash. Every edit is applied against a Base/Reference dataset with batch updates and full change tracking, so you can diff exactly what moved.

Can Hexx work fully offline?

Yes. Hexx is offline-first. It runs the backend and frontend locally with zero data egress — your ECU images, A2L files and calibration data never leave your machine. It can run as a web app against a local API or as part of the native HELIX desktop suite.

How does Hexx relate to HELIX?

Hexx is the hex & binary editing engine from the HELIX calibration suite, available as a focused standalone product. Inside HELIX it powers project-linked calibration editing across the full release lifecycle; standalone, it is a precision byte-and-map editor you can point at any HEX/A2L pair.

Next step

Ready to read every byte of your ECU?

A hex dump no one can read is not calibration. Pair any HEX/A2L image with Hexx and edit in engineering units — checksum-safe, reference-diffed, flash-ready.

Request Hexx access Talk to an engineer

By task

Where Hexx is used.

Go deeper

Guides and comparisons for Hexx.

Works with