Inconsistency in LDO Orbitool O2: Firmware serial vs RatOS.cfg #222
Description
What happened
The dynamically generated RatOS.cfg for the LDO Orbitool O2 expects a serial path with a -t0 suffix (/dev/RatOS/ldo-orbitool-o2-t0), but the board's own firmware.config and udev rules use the clean name ldo-orbitool-o2. This mismatch prevents Klipper from connecting to the toolboard.
What did you expect to happen
The serial: path in the generated RatOS.cfg should match the CONFIG_USB_SERIAL_NUMBER defined in the board configuration and the symlink created by the udev rules.
How to reproduce
Configure a printer with an LDO Orbitool O2 using the RatOS configurator.
Compile and flash the toolboard using the default RatOS board settings.
Observe that Klipper fails to find the MCU because it looks for the -t0 version.
Additional information
Technical details found during debugging:
Firmware Config: The file RatOS/boards/ldo-orbitool-o2/firmware.config sets CONFIG_USB_SERIAL_NUMBER="ldo-orbitool-o2".
Udev Rule: The file 98-ldo-orbitool-o2.rules creates a symlink to /dev/ldo-orbitool-o2.
The Conflict: The dynamic generator for RatOS.cfg) creates:
[mcu toolboard_t0]
serial: /dev/RatOS/ldo-orbitool-o2-t0
Verification: Running ls -l /dev/RatOS/ confirms the symlink exists as ldo-orbitool-o2, but Klipper fails because it specifically looks for the non-existent -t0 version defined in the auto-generated RatOS.cfg.
MCU Chip: STM32F042x6.