Firmware release workflow
A clear delivery path for OM0RX firmware builds, including version notes, hotfix visibility and browser-based install flow.
Case study
A specialist firmware and browser console project for the M32 Pocket: custom field-training firmware, guided flashing, USB configuration and release visibility in one place.
Project
A clear delivery path for OM0RX firmware builds, including version notes, hotfix visibility and browser-based install flow.
A Web Serial interface for device connection, settings, snapshots, status checks and firmware-specific configuration.
The console was added to MorseTrainerPro as a public tool while keeping the existing site header, footer and user experience intact.
The project clearly separates the community firmware from the official Morserino project and credits the original hardware and firmware work.
The useful work is the complete support layer: flashing, configuration, device status, release notes, update prompts and user guidance around a real hardware workflow.
Release information is written for operators, so users can see what changed before they flash a device.
The console is designed to continue being useful after flashing, not disappear once the firmware is installed.
The interface reflects the firmware: field training, callsign practice, SOTA/POTA training and device health checks.
Live deployment
The console lives inside MorseTrainerPro so users can reach it from the same training ecosystem that informed the firmware work.
Attribution
The OM0RX build is an unofficial community firmware and console project. It is not an official Morserino release, and users should flash custom firmware only when they understand the recovery path and risk. Credit for the original Morserino hardware, firmware and project foundation belongs to the Morserino team and original contributors.
Red Dingo can build the web layer around firmware, specialist devices and field tools.