Lost communication with MCU 'mcu' and corrupted firmware with 'v0.10.0-281-g7ce409d7

General Discussion
1

I have been having klipper mcu issues lately today it happen 2 time in a row, first one the error was

MCU 'mcu' shutdown: Missed scheduling of next digital out event

just now the second time it just lost communication,

Lost communication with MCU 'mcu'

not able to connect at all, I have to re-flash the firmware again to fix it, which this happen for the second time this week, sometime it just lost connection but firmware restart fix the issues but the firmware corruption have happen 2 time now, my connection are solid all connector are hot glued to prevent accidental removal

Printer: Ender 3 v2 with v4.2.2 board
Rasp Pi Zero 2 W connected via GPIO pin to Ender 3 board
klipper version v0.10.0-281-g7ce409d7

I rolled back the klipper version to commit ge3cbe7ea, it printing for 2hours have another 2 hours to go, we will see if I can reproduce the issues again, from the log issues only started to happen after I upgraded to g7ce409d7

pi@fluiddpi01:~/klipper_logs $ ls -l klippy.log.*.gz
-rw-r–r-- 1 pi pi 2420954 Mar 8 20:26 klippy.log.2.gz
-rw-r–r-- 1 pi pi 28582 Mar 7 13:04 klippy.log.3.gz
-rw-r–r-- 1 pi pi 909325 Mar 4 22:17 klippy.log.4.gz
-rw-r–r-- 1 pi pi 10258 Mar 3 23:58 klippy.log.5.gz ← issues start here
-rw-r–r-- 1 pi pi 1164371 Mar 3 21:17 klippy.log.6.gz
-rw-r–r-- 1 pi pi 944643 Feb 26 05:14 klippy.log.7.gz
pi@fluiddpi01:~/klipper_logs $ zgrep ^“Git version:” klippy.log.*z
klippy.log.2.gz:Git version: ‘v0.10.0-281-g7ce409d7’
klippy.log.3.gz:Git version: ‘v0.10.0-281-g7ce409d7’
klippy.log.4.gz:Git version: ‘v0.10.0-281-g7ce409d7’
klippy.log.4.gz:Git version: ‘v0.10.0-281-g7ce409d7’
klippy.log.4.gz:Binary file (standard input) matches
klippy.log.5.gz:Git version: ‘v0.10.0-263-ge3cbe7ea’
klippy.log.5.gz:Git version: ‘v0.10.0-263-ge3cbe7ea’
klippy.log.5.gz:Git version: ‘v0.10.0-263-ge3cbe7ea’
klippy.log.5.gz:Git version: ‘v0.10.0-281-g7ce409d7’
klippy.log.5.gz:Git version: ‘v0.10.0-281-g7ce409d7’
klippy.log.5.gz:Git version: ‘v0.10.0-281-g7ce409d7’ ← issues start here after upgrade
klippy.log.5.gz:Binary file (standard input) matches
klippy.log.6.gz:Git version: ‘v0.10.0-263-ge3cbe7ea’
klippy.log.7.gz:Git version: ‘v0.10.0-263-ge3cbe7ea’

klippy.zip (2.1 MB)

2

Unless I missed it, the attached log does not contain a
MCU 'mcu' shutdown: Missed scheduling of next digital out event
error.
Such error could be the consequence of a loaded host, which is not too unlikely with a Pi Zero, especially when using a webcam or causing other system loads.

The other errors look like connection attempts with a shutdown MCU.

3

the issues is aftter the second time of the error, it seem the board lost it firmware I have to reflash the board in order to fix this, is this normal? checking the load of the Pi Zero It never exceeded 40% load, it only running fluidd no webcam, I’m running ge3cbe7ea at the moment been printing since yesterday non-stop no issues so far

image
image888×414 22.4 KB

4

I do not know of any way how a board could lose its firmware during normal operation. This is why a dedicated flashing process is needed to write the firmware.

5

that is the thing bothering me at the moment, it happen 2 times both time I have to reflash else I’m wont able to connect to the board at all from fluidd only reflashing fixed it, at the moment ge3cbe7ea is stable I will refrain myself from updating it for now