01 Getting Started

Firmware update

OpenBLT updates, F7 full-erase cases, and DFU recovery.

8 min readUpdated 2026-08

Race Core F7 ships with firmware. Update it before the first start so you are on a known release, not a factory image from last year.

Normal update (OpenBLT)

  1. 01Close TunerStudio

    Only one process can own the USB serial port.

  2. 02Open the console

    From the rusEFI, FOME or Core EFI bundle that matches the firmware on the ECU. Select the Race Core COM port.

  3. 03Update firmware

    Use the bundle’s update action. The ECU reboots into the bootloader, takes the new image, and comes back.

  4. 04Reconnect TunerStudio

    If the signature changed, refresh the INI as described in Software setup.

When F7 needs a full erase

Some F767 units do not accept an incremental update and will sit in a half-updated state (USB enumerates, TunerStudio cannot connect, or the ECU reboots in a loop). The fix is a full chip erase and a clean DFU load — not another incremental update.

DFU recovery (STM32CubeProgrammer)

  1. 01Enter DFU

    Hold the BOOT0 / DFU procedure for this enclosure (see the service sticker) while applying +12 V, or use the console “reboot to DFU” if the USB stack is still alive.

  2. 02Confirm DFU device

    Windows Device Manager or `lsusb` should show an STM32 BOOTLOADER device, not a rusEFI serial port.

  3. 03CubeProgrammer

    Connect over USB, full chip erase, then program the F7 .hex / .bin from the same rusEFI, FOME or Core EFI bundle. Verify after write.

  4. 04Power cycle

    Disconnect USB and +12 V, then power normally. Console should now see a living ECU.

SWD (ST-Link on the 10-pin debug header) is the last-resort path. F767 units can behave oddly over SWD; prefer DFU.

Which file

FirmwareBoard / bundle
rusEFIProteus F7 — rusefi_bundle_proteus_f7.zip
FOMEFOME Proteus F7 release for this hardware
Core EFICore EFI F7 image as supplied with the unit
Do not flashProteus F4 / rusefi_bundle_proteus_f4.zip