Installer

OpenHaldex Web Installer

Browser-based version flashing using ESP Web Tools. Select a release manifest, connect your ESP32-S3 over USB, and install the complete image set for that version.

Choose release and install

Select your target release. The install button will use that release manifest and flash the mapped binary parts (bootloader, partitions, firmware app, and LittleFS image).

Release version

If install button does not appear, ensure your browser supports Web Serial (Chromium-based recommended).

Supported browser and cable requirements

Use a Chromium-based browser with Web Serial support.
Use a real data-capable USB cable (not power-only).
Disconnect other serial tools before flashing.
Grant serial permissions when browser prompt appears.

Many install failures are caused by cable or port constraints. If flashing stalls, switch cable and USB port first, then retry before changing firmware files.

What gets flashed

Each manifest maps binary parts to fixed offsets. For `v0.9.3-beta`, expected layout is:

bootloader.bin @ 0x0000
partitions.bin @ 0x8000
firmware.bin @ 0x10000
littlefs.bin @ 0x790000

This matches current `partitions.csv` in repository. If partition map changes in future versions, use the version's own manifest and never reuse offsets from older releases.

Post-install validation

Power-cycle the device after flashing finishes.
Connect via AP or STA and open UI.
Check diagnostics page for CAN and controller health.
Verify setup mappings and generation selection.
Perform conservative road validation before aggressive tuning.

Common install failures and fixes

Symptom	Likely cause	Fix
Install button missing	Browser lacks Web Serial	Use Chromium-based browser and reload page.
Serial port not shown	Power-only cable or driver issue	Switch to known data cable and different USB port.
Flash starts then fails	Port contention or unstable connection	Close other serial tools and retry with shorter cable.
Boots but UI behaves unexpectedly	Mismatched or partial image set	Reflash full version manifest and validate settings.

Security and trust checks

Users should flash only manifests and binaries published under official project release paths. Maintainers should publish checksums alongside binaries and keep release notes linked to exact artifact set.

Compare release version in notes page and manifest before install.
Verify firmware source repository and release tag provenance.
Do not flash unsigned third-party bundles into production vehicles.

Maintainer notes for adding new releases

Add firmware assets under `release/firmware//`.
Add matching `release/manifests/.json` with correct offsets.
Add version option to selector on this page.
Add release row to release hub.
Publish release notes page and verify install flow end-to-end.

Try the OpenHaldex Firmware Demo

Preview the real OpenHaldex firmware UI in your browser with simulated live CAN traffic and interactive pages for tuning, diagnostics, logs, setup, and OTA workflows.

Open firmware demo