How to map the hardware to its revision and to which firmware file to use
Mith more and more components having more than one revision it starts becoming important to identify what revision one owns and what firmware is suited for it. Here is an overview.
| badge | identifier | name | filename | notes |
| ----- | ---------- | ---- | -------- | ----- |
| | MREFPMOB20R02 | MNT Reform Motherboard 2.0 | `firmware-20_R3.bin` | badge can be found under the SSD, the firmware is R3 even though the badge says R02 because R3 is R2 modified by MNT (resistor bodge) |
 | MREFPMOB25R02 | MNT Reform Motherboard 2.5 | `firmware-25-R2.bin` | badge can be found under the SSD |
| | MREFPKBD20R01 | MNT Reform Keyboard 2.0 | `keyboard-2-standalone.hex` (standalone variant), `keyboard-2.hex` (built into reform) |
 | MREFPKBD20R02 | MNT Reform Keyboard 3.0 | `keyboard-3-standalone.hex` (standalone variant), `keyboard-3.hex` (built into reform) |
 | MREFPTBC20R01 | MNT Reform Trackball Module (ATmega32u2) | `Mouse.hex` |
 | MREFPTBC20R02 | MNT Reform Trackball Module 2 (rp2040) | firmware not yet built by CI |
| | MREFPOLE20R01 | MNT Reform Keyboard OLED Module | no firmware |
 | MREFPBAT20R01 | MNT Reform Battery Board (unprotected) | no firmware |
 | MREFPBAT20D02 | MNT Reform Battery Board (protected) | no firmware |
| | MREFPTBS20R01 | MNT Reform Trackball Sensor | no firmware |
issue