Step 12.13 — Identify your Leviathan revision before you build anything¶
Step 13 of 37 · Chapter 12 — Software: Pi OS image, Klipper/Moonraker/Mainsail, firmware, printer.cfg
(no image — see text)
Parts: none.
Do: Read the revision printed on the mainboard silkscreen, and cross-check it against the ID you just read. They must agree:
Check
You have written down one MCU model, one clock reference and one offset, and you are not going to look at the other row again.
What you're looking at
Silkscreen is the printed lettering on the board itself. Which processor your Leviathan carries decides three fields of the firmware build: processor model, crystal frequency and where in flash the firmware starts. LDO's own documents disagree, so the board is the only authority.
| Silkscreen | MCU | Klipper/Katapult clock | Bootloader offset | Serial ID |
|---|---|---|---|---|
| Leviathan V1.1 / V1.2 | STM32F446 | 12 MHz crystal | 32 KiB | stm32f446xx |
| Leviathan V1.3 | STM32H743 | 25 MHz crystal | 128 KiB | stm32h743xx |
Use the row that matches your board in Step 12.14. If the silkscreen and the serial ID disagree, trust the serial ID and stop to ask in #ldo_motors.
Caution
Rev D+ / LDO: do not resolve this from paperwork. The Rev D wiring guide and the kit config header both say STM32F446 / Leviathan V1.1; the Leviathan repo README was changed on 2025-10-30 from "STM32F446" to "STM32H743", and LDO publishes two setup guides with different menuconfig values. The board itself is the only authority. src · src · src
Good stopping point · ~15 min since the last one
the bay has been powered once, both MCUs enumerate on /dev/serial/by-id/, both IDs are written down, and you have read the Leviathan's own silkscreen. Nothing has been flashed yet. Do not start a firmware build you cannot finish and flash in the same sitting.
Source: LDO Leviathan repo · LDO Leviathan V1.2 guide · LDO Leviathan V1.3 guide