# Printer halted due to 'mcu' configured for 400Mhz but running at 401Mhz! **URL:** \ **Category:** General Discussion\ **Created:** [September 8, 2024, 11:44am UTC](https://klipper.discourse.group/t/printer-halted-due-to-mcu-configured-for-400mhz-but-running-at-401mhz/18707 "2024-09-08T11:44:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Xavier67fr](https://avatars.discourse-cdn.com/v4/letter/x/f475e1/32.png) [@Xavier67fr](https://klipper.discourse.group/u/Xavier67fr)\ **Post date:** [September 8, 2024, 11:44am UTC](https://klipper.discourse.group/t/printer-halted-due-to-mcu-configured-for-400mhz-but-running-at-401mhz/18707/1 "2024-09-08T11:44:24Z")
### Basic Information: Printer Model: proforge 4 MCU / Printerboard: octopus max stm32h723xx) Version: v0.12.0-290-g14a83103c Load: 0.00, Awake: 0.00, Freq: 400 MHz, 0 Host / SBC klippy.log ### Describe your issue: Hi I could not find a solution reading at similar topics. I installed klipper on my Raspberry 5 4go with Kiauth without issue. I compile the Octopus EZ Max and loaded it. I systematically get the MCU issues at loading. I read in Klipper website to ignore this but as soon as I want to start a print , printer is halted with the same message . I do not know what to do to solve this. Printer halted due to ‘mcu’ configured for 400Mhz but running at 401Mhz! I recompiled again but nothing changed. I am stuck. Unable to print anything . Thank you if you can help. [klippy.log](https://klipper.discourse.group/uploads/short-url/4RjO8npimbJL5ngmvxF7JuOlU92.log) (114.8 KB) ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [September 8, 2024, 12:37pm UTC](https://klipper.discourse.group/t/printer-halted-due-to-mcu-configured-for-400mhz-but-running-at-401mhz/18707/2 "2024-09-08T12:37:32Z")
Please provide a Klipper log showing the issue. The log you provided only shows an incomplete / wrongly configured machine, e.g. wrong serial path and a config section `[tools_calibrate]` that does not exist in Klipper. ---
**Author:** ![Xavier67fr](https://avatars.discourse-cdn.com/v4/letter/x/f475e1/32.png) [@Xavier67fr](https://klipper.discourse.group/u/Xavier67fr)\ **Post date:** [September 8, 2024, 1:13pm UTC](https://klipper.discourse.group/t/printer-halted-due-to-mcu-configured-for-400mhz-but-running-at-401mhz/18707/3 "2024-09-08T13:13:16Z")
Problem is now solved. This was due to a specific file missing in config directory. ---
**Author:** ![BevanWeiss](https://avatars.discourse-cdn.com/v4/letter/b/c5a1d2/32.png) [@BevanWeiss](https://klipper.discourse.group/u/BevanWeiss)\ **Post date:** [September 9, 2024, 9:05am UTC](https://klipper.discourse.group/t/printer-halted-due-to-mcu-configured-for-400mhz-but-running-at-401mhz/18707/4 "2024-09-09T09:05:25Z")
> [@Xavier67fr](#): > > Printer halted due to ‘mcu’ configured for 400Mhz but running at 401Mhz! > [@Xavier67fr](#): > > Problem is now solved. This was due to a specific file missing in config directory. Please provide the details which connects ‘specific file missing in config’ solution with the error message you reported was the problem. ---
**Author:** ![Xavier67fr](https://avatars.discourse-cdn.com/v4/letter/x/f475e1/32.png) [@Xavier67fr](https://klipper.discourse.group/u/Xavier67fr)\ **Post date:** [September 9, 2024, 10:22am UTC](https://klipper.discourse.group/t/printer-halted-due-to-mcu-configured-for-400mhz-but-running-at-401mhz/18707/5 "2024-09-09T10:22:28Z")
The printer needed a supplier file tools\_calibrate.py in the config . I missed that one. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [October 9, 2024, 8:23pm UTC](https://klipper.discourse.group/t/printer-halted-due-to-mcu-configured-for-400mhz-but-running-at-401mhz/18707/6 "2024-10-09T20:23:10Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.