Printer Model: Voron 2.4
MCU / Printerboard: Octopus Pro with H723 klippy.log
Fill out above information andin all cases attach yourklippy.logfile. Pasting yourprinter.cfgis not needed Be sure to check our Knowledge Base and in particular this and this post
Describe your issue:
Any restart of klipper I get this:
MCU 'mcu' shutdown: oids already allocated
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
I have to do a full power cycle to get it to work (i.e. the mcu has to be power cycled)
This looks like a logging statement from the python socketcan module. So it’s coming from the klippy server not the MCU, but it does appear it may be related to how you are connected to the MCU, is this over CAN as well? USB?
Not a Klipper Dev, so I can’t be sure. Also not sure where you are getting those release tags from, I run klipper from a clone of the GitHub Repo and I dont see gcba119db or gb17ae55f as commit hashes. But I am running of the master branch and there were some recent commits the last few days for optimizations for Can Bus and USB scheduling.
I’m not sure if you have found a solution for the issue.
The logs seem to indicate that the stm32h723 cpu was not able to reset itself. Double check that the chip on the board matches the chip you have compiled for. Otherwise, you may want to grab the latest code, make sure you haven’t made any code modifications, reflash all the boards, and upload that log here.