← Repair page
Failed admin logins, last 7 days. 5 failures / 15 min locks that IP for 30 min.
| IP | Fails | Last attempt | Status |
|---|
No failed login attempts in the last 7 days.
Firmware admin upload
Push a new firmware — this becomes the default one every repair-page visitor flashes.
Loading current firmware info…
Available firmware
Every uploaded file is kept — pick which one is active, or delete old ones.
| Version | File | Size | Uploaded |
|---|
No firmware uploaded yet.
Connection
Port
—
Bootloader ver.
—
Chip PID
—
Supported cmds
—
Board not showing up when you click Connect?
If no device is listed in the browser's picker, this computer probably doesn't have
the CP210x USB driver installed yet.
Mac, Linux, or a different version: silabs.com/software-and-tools/usb-to-uart-bridge-vcp-drivers
- Download the CP210x driver (official, Silicon Labs): CP210x_VCP_Windows.zip
- Install it, then unplug/replug the board's USB-C cable.
- Reload this page and try again.
Mac, Linux, or a different version: silabs.com/software-and-tools/usb-to-uart-bridge-vcp-drivers
Enter bootloader / reset
If Sync/Get ID keeps failing, toggle these two checkboxes and hit "Enter bootloader" again —
the working polarity depends on your bridge.
Firmware image
Drag & drop a .bin or .hex file here, or click to browse
No file loaded.
Dev firmware
Admin-only, separate from production. Pushed directly by whoever is iterating on the
firmware (see
Script/push_dev_firmware.sh) -- last 5 builds are kept.
Options
Erase mode
Flash
Idle
Log
STM32F103CBT6 · CP2102N USB-C bridge · AN3155 UART bootloader — runs entirely in your browser.
Bike registry
Every provisioned bike, its last known firmware, and health status.
Register a new bike →
0
Bikes flashed
Healthy—
On latest firmware—
| Bike ID | UUID | Firmware | Health | Last update | Registered |
|---|
No bikes provisioned yet.
Register a new bike
Connect a board already running firmware that supports the identification protocol, confirm its health, then assign it a fleet number. If this is a brand-new, never-flashed board, you'll be offered the option to flash it directly from this tab after clicking "Connect & identify".
This board did not respond to identification
Idle
UUID
—
Reported bike ID
—
Firmware version
—
Health
—
Change bike ID
Connect a board that's already registered to reassign its fleet/cargo number. This
writes the new ID to the board's own flash and updates the registry — the board's UUID
never changes, only which fleet number it's paired with. Use this to correct a
mis-typed ID or reassign a board, not for first-time registration (see Register bike).
UUID
—
Current bike ID
—
Firmware version
—
Health
—
Replace board
Retire an old or dead board and let a new board take over its fleet number. The old
board's UUID and full history stay in the registry, marked retired — nothing is
deleted. The old board does not need to be connected (it may be dead); only its bike ID
is needed.
Old UUID
—
Last firmware
—
Last health
—
New board
This board did not respond to identification
Expected for a replacement board that's brand-new/never-flashed. If you're sure
this is a blank board, flash it now with the latest available firmware, then it
will be identified and ready to take over the bike ID above.
Idle
New UUID
—
Firmware version
—
Health
—