Skip to content

Flash and configure a companion

Confirm that the official flasher supports your exact board as a companion, then use this guide to back it up, flash it, and join your local mesh. Check the community directory for different local settings.

Before you erase

Erase Flash deletes the device's stored data

Erasing can remove the node identity/private key, name, contacts, channels, radio settings, and other saved configuration. An erased identity cannot be recovered unless you backed it up.

If this is not a brand-new device:

  1. Connect with the app or configuration tool that currently manages it.
  2. Record the board model, role, firmware version, device name, radio settings, and any settings you need to recreate.
  3. Export or securely record the device identity/private key using a supported backup method for that firmware. Store it as a secret; never post it in screenshots, chat, issues, or logs.
  4. Export contacts or channels if your app provides that option.

If you cannot back up an identity or configuration that matters, stop before Erase Flash and ask your local community for help.

Before you start

  • [ ] I selected the exact hardware model printed on or reported by the board.
  • [ ] I backed up everything I need from an existing device.
  • [ ] I have a known-good data USB cable and stable power.
  • [ ] I am using a browser with Web Serial support, such as current Chrome or Edge.
  • [ ] I know how to put this board back into DFU or bootloader mode if flashing fails.

USB serial drivers

Some boards require a USB serial driver before the browser can connect.

What flashing changes

Flashing replaces the installed firmware and, when Erase Flash is selected, deletes stored identity and configuration. The later setup writes the device name and local radio settings.

Flash the companion firmware

Use the official MeshCore Web Flasher. The flasher requires a browser that supports Web Serial.

  1. Connect the device by USB.
  2. Select the exact hardware model.
  3. Select Companion Radio (Bluetooth).
  4. Select the firmware version intended for that board.
  5. Click Enter DFU Mode. The flasher should report that it found a device in the expected mode.
  6. Recheck the hardware and firmware selections.
  7. Click Erase Flash, then wait for a successful erase message.
  8. Click Flash and wait for the completion message before disconnecting the device.

Recovery if flashing fails

Do not keep erasing. Leave the device connected, refresh the flasher, return the board to DFU mode, reselect the exact board and companion firmware, and retry Flash. If the board no longer appears, follow its documented bootloader recovery method or ask for help before trying another target.

Check the flash

The flasher reports completion, the board restarts as a companion, and the supported app can discover it. If any part is missing, use the recovery path before changing another setting.

Configure the companion

  1. Pair the node with the supported MeshCore app on your phone or computer.
  2. Give it a descriptive name that does not reveal a private location.
  3. Check your local community page for different settings.
  4. If none are listed, use the Canada defaults: USA/Canada (Recommended) (910.525 MHz / 62.5 kHz / SF7 / CR5).
  5. Save the settings and reconnect after the device restarts.

The optional Message Settings → Auto Reset Path preference affects how the app manages changing paths. Leave it at its default unless your local testing process calls for a different setting.

Verify before regular use

  1. Confirm the app reconnects and shows the expected device name and radio settings.
  2. Send a test message in the Public channel.
  3. A response such as Heard X Repeats indicates that at least one repeater reported hearing it. A plain Sent result is not proof that the settings are wrong; move to a known coverage area or ask the local community to help test.

Do not consider the setup complete until the saved settings survive a reboot and a local test succeeds.

After flashing

After the companion passes the reboot and local message check, find your community and keep the board-specific USB recovery method with the device record.

Sources