Requires Chrome or Edge over HTTPS or localhost. WebSerial is not supported in Firefox or Safari.
Step 1: Select an .ablp pattern file.
Step 2: Upload. The blaster pauses HID output during transfer. The USB port is requested (first time only) and released automatically when the upload finishes.
Update the blaster's firmware over USB. Requires Chrome or Edge — WebSerial is not supported in Firefox or Safari.
Step 1: Read the device identity (optional — Check for Update does this automatically too).
Step 2: Check whether an update is available.
Step 3: Install the update. The blaster reboots into update mode automatically.
Streams a locally-picked envelope.bin straight to
the device, bypassing the update server. Used to test the
error states with tampered or wrong-key firmware. Not for
normal updates.
Update the dock's firmware directly over the dock's own USB CDC ACM serial port. The port is requested the first time you click "Update Dock" below — do not select the blaster/nRF bridge port when the picker appears, that is a different serial device.
Step 1: Select a signed dock .bin file.
Step 2: Update the dock. The dock reboots into the new image automatically (MCUBoot TEST mode; auto-reverts if the new image does not confirm itself on first boot).
Updates nrf_main's own application image via its custom recovery loader (MCUBoot-based, plain-signed single-slot). This is a SEPARATE flow from the STM32 firmware update and the Dock update above — it uses nrf_main's own recovery-mode USB serial port, which is a DIFFERENT device than the blaster bridge port.
Step 1: Nothing to do — this page downloads the
current official nrf_main firmware for you and checks it against its
published SHA-256 before anything is written to your blaster. The
file picker below is an optional override, for an operator who wants
to supply their own signed image (.bin).
Manual fallback — you should not need this. Use it only if you are
installing offline, or if your browser blocks the automatic download:
nrf_main-p33rma-f8534619-54ff6731.bin
(81,318 bytes). To check the download by hand, its SHA-256 is
54ff673120e075df46e9145012bb76738759698f46094cb9aae491f785cfe078.
Step 2: Save the current settings, then send the reboot-to-recovery command over the existing blaster bridge connection. The update erases this unit's stored settings (radio channel, ext slots, watchdog enable), so they are read now and written back automatically in Step 4.
If your blaster is already stuck in recovery mode, skip Step 2. You are in that situation if the browser's port picker already offers an "Arkade Recovery" device, or if the "Refresh device info" button at the top of this page cannot find your unit at all. In that case just pick the image in Step 1 and go straight to Step 3. Warning: your saved settings cannot be preserved when you skip Step 2 — reading them needs the normal firmware to be running, and on a stuck unit it is not. Radio channel, ext slots and watchdog enable will go back to their factory defaults after the update, so set them again once your blaster is working.
Step 3: The device reboots and re-enumerates as a DIFFERENT USB serial device ("Arkade Recovery"). Click below and pick that device in the browser's port picker — do not re-select the original blaster/bridge port.
Step 4: Stream the image. The device applies it and reboots back into the app automatically, then the settings saved in Step 2 are written back — no further clicks needed.
The nRF chip restarts the STM32 if it stops responding for 60 s (300 s during a firmware update). Changing it here is saved on the nRF immediately and survives power cycles.
Warning: main and dock MUST share identical values for all 6 params below. A mismatch on ANY of them kills the RF link between the blaster and the dock.
The bridge and dock ports are requested on demand — the first Read pops the dock picker once (skip it to read main-only), then reuses it; each port is released immediately after every action.
Step 1: Read the current values from both ends.
Note: these reads return each device's live (RAM) values,
not what is saved in flash — a unit that lost its persisted config still
reads correctly until it is power cycled. The only proof a value is
persisted is to power cycle and Read again. Apply always ends with
esb_save, even when you edited nothing.
| Param | main | dock | Match | New value (hex bytes) |
|---|
Step 2: Apply edited values. Writes to BOTH ends (or main-only with a loud warning if the dock picker was skipped), then persists with esb_save.