Step 12.20 — Re-read and record both serial paths¶
Step 20 of 37 · Chapter 12 — Software: Pi OS image, Klipper/Moonraker/Mainsail, firmware, printer.cfg
(no image — see text)
Parts: none.
Do:
ls /dev/serial/by-id/
Check
Exactly two lines, both containing usb-Klipper_, one stm32g0b1xx and one stm32f446xx/stm32h743xx. No katapult entries left.
What you're looking at
Both boards should now be back under their usb-Klipper_… names with no usb-katapult_… left; a board still showing katapult never actually received its firmware. Mainsail's Machine → DEVICES → SERIAL panel shows the same list from the browser.
Copy both full paths — including the -if00 suffix — somewhere you can paste from. You need them twice in the next few steps.
Caution
If ls /dev/serial/by-id/* comes back empty on a machine that was working a moment ago, that is the first thing to investigate — a known udev failure mode on older Pi OS releases. On MainsailOS 3.x you should not hit it; if you do, check dmesg | tail for USB enumeration errors before touching the config (survey §4.3). src
Good stopping point · ~20 min since the last one
both boards flashed, both serial paths re-read and recorded, and both come back after a reboot. This is the safest stopping point in the chapter: hardware and firmware agree and nothing is edited yet.
Source: LDO Klipper-ID guide · LDO wiring guide § Determining the USB ID of your mainboard and toolboards