Mcu losing connection mid print after fresh install?

[Frega]

Hi! Im running Klipper in a MKS SKIPR for a year or two with 0 problems. Then I had that wonderful idea of updating it, since it had a outdated linux (buster) and klipper (0.10 or 0.11)

Everything went fine, flashed Linux into a new SD card, then downloaded Kiuah, installed Klipper, imported printer.cfg, made the new firmware for mcu, flashed it into the mcu and in a few hours I had Klipper running again.

Problem is now mid print it suddenly stops with message:

Lost communication with MCU 'mcu’ OR MCU ‘mcu’ shutdown: Missed scheduling of next digital out event

Any way of the ‘mcu’ beeing mislabeled? I’ve defined a [mcu ebb] that indeed is connected thru a usb port to the toolhead.

PS: the Host and main mcu are in the same PCB, they’re wired directly with a 100Ohm resistor inbetween, so there’s no way this is a faulty cable/connector

Basic Information:

Printer Model:
MCU / Printerboard: STM32F407 (MKS SKIPR)
Host / SBC: RK3328 armbian 64bits (MKS SKIPR)

klippy.log (4.2 MB)
klippy.log

…

[Frega]

Well just got my own record beaten, got an error while doing the adaptative meshing right before starting a print.

MCU ‘mcu’ shutdown: Missed scheduling of next digital out event

klippy (1).log (6.5 MB)

PS: Right before I ‘organized’ the cables next to the the board to avoid eletromagnetic interference and got a ‘unable to write tmc spi stepper y ‘GLOBALSCALER’, seems the TMC5160 cables were a little loose? This got me wondering now if the communication error can be because something like this?

[Frega]

Problem (likely) found, seems it was a grounding issue, the 220volt power cable between the wall socket and the psu didnt had a ground, I swapped the cable and didn’t had a problem since then.