Klipper Error: mcu 'mcu' Has Deprecated Code — Fix It
If you updated Klipper in Mainsail or Fluidd and suddenly see a warning about deprecated code on your MCU and EBB board, this guide is for you.
The short version: updating Klipper on the host does not automatically update firmware on your physical boards. You need to recompile and flash both your toolhead board and your mainboard so protocol versions stay in sync.
Hardware in This Walkthrough
Section titled “Hardware in This Walkthrough”- Host: BTT CB1 or Raspberry Pi
- Mainboard: BTT Manta M8P V1.1
- Toolhead board: EBB2209 CAN
- CAN bootloader: Katapult (formerly CanBoot)
Why the Warning Happens
Section titled “Why the Warning Happens”Klipper has two parts:
- Host software running on Linux
- Firmware running on each microcontroller board
When the host updates but board firmware stays old, Klipper reports protocol mismatch/deprecated code until everything is aligned.
Before You Start
Section titled “Before You Start”I follow Esoterical’s CANBus guide for these steps. It has an updating section for both the toolhead and the mainboard. If you set up CAN with that guide, updating is the same commands again.
- SSH into your host.
- Back up your current config files.
- Keep your current board UUIDs handy from printer.cfg.
- Have physical access to the toolhead board in case you need a reset.
Phase 1: Update the EBB Toolhead (CAN)
Section titled “Phase 1: Update the EBB Toolhead (CAN)”1. Build Klipper Firmware for the EBB
Section titled “1. Build Klipper Firmware for the EBB”cd ~/klippermake menuconfigmake cleanmakeIn menuconfig, choose options that match your exact EBB model and bootloader settings.
2. Stop Klipper Before Flashing
Section titled “2. Stop Klipper Before Flashing”sudo service klipper stop3. Flash Over CAN
Section titled “3. Flash Over CAN”Use your EBB UUID from printer.cfg. If needed, discover devices with canbus_query first.
python3 ~/klipper/scripts/canbus_query.py can0python3 ~/katapult/scripts/flashtool.py -i can0 -u <your-ebb-uuid> -f ~/klipper/out/klipper.binIf the flash crashes
Section titled “If the flash crashes”On my EBB2209 the first flash attempt often fails with a long error partway through. That’s the board being finicky, not a bad build. This sequence fixes it every time for me:
- Stop Klipper again:
sudo service klipper stop - Press the up arrow so the flash command is ready to run.
- Go to the toolhead and press the reset button on the EBB twice, quickly.
- Run the flash command straight away.
When it works, the output ends with “Programming complete”, not “flash success”. That’s normal.
Confirm the board is back in Klipper mode, not Katapult mode:
python3 ~/klipper/scripts/canbus_query.py can0The UUID should show Application: Klipper.
Phase 2: Update the Mainboard (BTT Manta M8P)
Section titled “Phase 2: Update the Mainboard (BTT Manta M8P)”If your Manta is acting as a USB-to-CAN bridge, your menuconfig settings matter a lot. Wrong settings can break CAN communication.
Use this reference profile for M8P V1.1:
| Setting | Selection |
|---|---|
| Micro-controller | STMicroelectronics STM32 |
| Processor model | STM32G0B1 |
| Bootloader offset | 8KiB bootloader |
| Clock Reference | 8 MHz crystal |
| Communication interface | USB to CAN bus bridge (USB on PA11/PA12) |
| CAN bus interface | CAN bus (on PD12/PD13) |
Two settings are easy to miss below the table:
| Setting | Selection |
|---|---|
| Optimize stepper code for ‘step on both edges’ | Enabled |
| GPIO pins to set at micro-controller startup | (blank) |
Save, then build:
make cleanmakeCheck that out/klipper.bin is listed at the end of the build output.
Flash the mainboard through Katapult
Section titled “Flash the mainboard through Katapult”-
Stop Klipper:
sudo service klipper stop -
Put the board into Katapult mode using its UUID from
printer.cfg(the[mcu]section, not the EBB):Terminal window python3 ~/katapult/scripts/flashtool.py -i can0 -u YOUR_MAINBOARD_UUID -r -
Find the board’s USB path:
Terminal window ls /dev/serial/by-idYou’re looking for an entry containing
usb-katapult. -
If
usb-katapultisn’t listed, press the reset button on the mainboard twice, then runlsagain. That fixed it for me. -
Flash using that path:
Terminal window python3 ~/katapult/scripts/flashtool.py -f ~/klipper/out/klipper.bin -d /dev/serial/by-id/usb-katapult_YOUR_BOARD_ID -
Run
lsusb. You should see the CAN adapter again.
Then confirm the new firmware boots cleanly.
Verify Everything
Section titled “Verify Everything”Start Klipper again:
sudo service klipper startThen refresh Mainsail/Fluidd and confirm:
- Deprecated code warnings are gone
- MCU and CAN stats populate normally
- No recurring protocol shutdown errors
If errors remain, verify USB/CAN visibility from the host:
lsusbUpdating from Mainsail’s Update All only updates the host. You’ll see this warning again after any Klipper update that changes the MCU protocol, so bookmark this page.
When It Is Not Firmware Anymore
Section titled “When It Is Not Firmware Anymore”If you repeatedly see protocol shutdowns or flash instability even after clean reflashes and reset attempts, hardware failure is possible (especially from heat/stress over time).
Potential replacement paths:
- EBB2209 CAN Board: go.minimal3dp.com/ebb-can
- BTT Manta M8P V2.0: go.minimal3dp.com/btt-manta
Related Tools
Section titled “Related Tools”- FDM Cost Calculator: estimate the real cost of maintenance downtime
- Rotation Distance Calculator: recalibrate motion after firmware work
Watch the Full Video
Section titled “Watch the Full Video”If this walkthrough helped, save it in your printer maintenance notes so the next Klipper update cycle takes minutes instead of hours.
