Skip to main content

DFU / UF2 flashing: download, write and verify

Before flashing: download the correct file​

Normal typing and remapping do not require flashing. Before upgrading, confirm PCB markings, revision, layout and current wireless backend, and export your VIA / Vial keymap. Find the matching row in Downloads:

PCBFile and tool
G60, Kamilia, Command65 / PE, legacy Manta AVR, Skog Reboot, F60 rev1AVR .hex, QMK Toolbox
F60 rev2 / rev3 / rev M / F60w, Manta40 rev2 / Ortho.uf2, copy to the TinyUF2 drive

:::danger Firmware is not interchangeable Do not mix PCB revisions, Ortho / standard layouts, or Bluefruit / DuoChord / CH592 backends. A DuoChord nRF application .hex is also HEX but must not be flashed to AVR using QMK Toolbox. First migration from legacy BLE requires AVR first, nRF second. :::

Enter flashing mode​

  1. Connect a USB data cable. Prefer an already mapped Reset / QK_BOOT key in VIA / Vial.
  2. If default Bootmagic is enabled, unplug USB, hold Esc, reconnect USB, then release Esc after about 1 second. For special layouts, check the model manual first.
  3. Otherwise use the PCB's labelled RESET button according to the model instructions. Single / double press requirements vary by bootloader; the power key is not RESET.
  4. AVR DFU: QMK Toolbox reports a DFU device and normal typing stops. TinyUF2: a temporary USB drive appears. Do not continue until the expected device appears.

AVR: write HEX with QMK Toolbox​

  1. Download your platform's build from the official QMK Toolbox releases and open it. On Windows, follow the initial prompt to install flashing drivers.
  2. Click Open and select the matching AVR .hex. If asked for an MCU, select your board's controller (usually ATmega32U4; Skog Reboot uses AT90USB646 / AT90USB1286 depending on revision).
  3. Enter DFU as above, wait for Toolbox to report the device, then click Flash.
  4. Wait for erase, write and verification to finish without disconnecting power. The keyboard normally restarts; if it stays in DFU after successful completion, reconnect USB.
  5. Test typing and Fn layers in a text editor, then wireless if applicable.

TinyUF2: copy UF2 to the temporary drive​

  1. Enter TinyUF2 as above and wait for the USB drive.
  2. Copy the exactly matching .uf2 to it. QMK Toolbox is unnecessary; do not copy HEX or VIA JSON here.
  3. Wait for copying and automatic restart; the temporary drive disappears.
  4. Test typing, Fn layers and wireless if applicable. Restore a keymap backup only when compatible with the firmware.

If it fails​

  • No DFU device / UF2 drive: try another data cable and USB port; check Bootmagic or the mapped Reset key. Lack of typing alone does not prove bootloader entry.
  • Toolbox cannot see DFU: check flashing drivers and the official QMK flashing guide.
  • UF2 drive appears but typing fails after copying: recheck file, PCB revision and layout; do not try random models' firmware.
  • AVR updated but legacy BLE migration incomplete: continue the six-step migration, including the nRF application update.