riscy·logger firmware update

Flash the production build onto the device from your browser — no toolchain.

WebUSB · ISP bootloader
⚠ Updating may erase the keystroke log. The factory bootloader wipes the application flash and has no way to read the log back, so anything captured is likely lost. Read & save the log first on the readout page → open readout.

  1. Save the log

    Open the readout page, pull the log and download it. Skip only if you don't need it.

  2. Put the device in bootloader mode

    Unplug it. Hold the BOOT0 (PB8) button while plugging USB back in, then release. It re-enumerates as the WCH bootloader 4348:55E0 (it stops acting as a keyboard).

  3. One-time Windows driver

    The WCH bootloader ships no WinUSB descriptor, so a browser can't open it until you bind WinUSB once with Zadig. Do this only the first time (per machine).

    Show Zadig steps (Windows only)
    1. Download & run Zadig (zadig.akeo.ie) with the device in bootloader mode.
    2. Options → List All Devices.
    3. In the dropdown pick the WCH bootloader — USB ID 4348 55E0.
    4. Choose driver WinUSB, click Replace / Install Driver.
    5. If Windows later reloads WCH's own driver, just run Zadig again.
    Linux/macOS need no driver (add a udev rule for 4348:55e0 on Linux if access is denied).

  4. Flash it

    Pick the firmware below (the current production build is bundled) and hit Update firmware. The page erases the app region, writes and verifies the image, then reboots the device.

loading firmware.bin… — · sha256 —
Waiting for firmware…
✓ Done. The device is rebooting into the new firmware; it should re-enumerate as 1A86:FE00 and start acting as a keyboard again. To flash again, replug it in bootloader mode.

Everything runs locally in your browser — the firmware image never leaves your machine. Flashing talks to the chip's factory USB bootloader over WebUSB; the running logger is untouched by this page.