Our Firmware

Forking and modifying OpenFIRE: what to change, keeping up with upstream, and what the licence asks of a kit seller.

Firearms

Our Firmware · Deep Dive

Our Firmware

From user to maintainer.

Forking and modifying OpenFIRE: what to change, keeping up with upstream, and what the licence asks of a kit seller.

Photo: Raspberry Pi Pico, oblique view showing the BOOTSEL button by Phiarc · CC BY-SA 4.0

Search every volume:

?

How to search

sten gun
pages with both words
"sten gun"
the words together, as a phrase
sten OR sterling
either one (| works too)
sten -replica
leave out pages that mention “replica”

Without quotes, the last word also matches longer words that start with it (sten finds Stenophylla), and close word forms count (rifle finds rifles). Tick Exact words to match whole words only.

Whole deep dives are listed first, then the pages inside them.

    Volumes

    1. Vol 1 The Fork — What It Is For, What It Is Not, and Where in OpenFIRE Each Change Lands Why the light gun runs a private copy of OpenFIRE v6.2, the owner decisions that shape it, the v6.2 files every proposed change touches, the finding that settings travel between gun and App by name, and the whole change list on one page
    2. Vol 2 The Change List, Part 1 — Aiming, the Kit Camera, the Inertial Sensor Every change the sensing dives propose for the fork, one card each: where it came from, why it is worth making, what could go wrong, and the bench test that proves it — the calibration and filter fixes, the PixArt PAJ7025R3 driver, frame subtraction and bar lock, and the LSM6DSOX bridge
    3. Vol 3 The Change List, Part 2 — Trigger, Recoil, Ejection Port, Rumble, Display and the v6.2 Fixes The output side of the fork: the analog Hall trigger and its three-point calibration, a pulse ended at landing, the rule that the recoil and port stages never fire together, the hold-open state machine, quiet rumble that waits its turn, the ammo count, the vendor ID, and what to do with each of the twelve v6.2 findings
    4. Vol 4 Running the Fork — A Private Copy, Its Branches, the Pinned Toolchain, Upstream Merges and Releases Why the fork cannot be a GitHub fork, how its branches mirror TeamOpenFIRE's single-trunk releases, what to do with the board-header submodule, the build pinned down to the command line, how an upstream release is merged in, how fork versions are numbered without breaking the App, and what a release contains
    5. Vol 5 Testing the Fork — Host Tests, the ADP3450 on the Bench, and a Checklist Before Every Release Upstream compiles but does not test; the fork has to. What can be proved on the workstation with no hardware, how to instrument the firmware without spending a pin, the seven bench captures on the Analog Discovery Pro ADP3450 that cover every change, the serial flood and soak tests, and the release checklist
    6. Vol 6 What the Licence Demands of a Kit, the Vendor ID, and Whether to Write New Firmware The licences inside one OpenFIRE binary, file by file, and why GPL-3.0 governs it; what GPL-3.0 sections 5 and 6 require the day a kit is sold, quoted from the licence; why a light-gun kit is a User Product and what that means for the Pico 2; four routes to a USB vendor ID with their prices and what each breaks; and an honest case for and against writing firmware from scratch