Internal error during connect: read failed

[abstract moth]

checked all cables are connected correctly

[wind geyser]

What returns ls /dev/serial/by-id and lsusb?

Looks your pico isn't connected anymore

[abstract moth]

pi@V0:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@V0:~ $ ls /dev/serial/by-id
ls: cannot access '/dev/serial/by-id': No such file or directory
pi@V0:~ $ ls /dev/serial/by-id
usb-Klipper_rp2040_45503571288EFA78-if00
usb-Klipper_stm32f042x6_0E0006000C43564B39373620-if00
pi@V0:~ $

looks to be my ebb i think

[wind geyser]

Not sure the log say:
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_rp2040_45503571288EFA78-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Klipper_rp2040_45503571288EFA78-if00'

but the EBB should be there too

[abstract moth]

switched the printer on and off a few times and it turned on just now, i connected, i loaded filament which worked ok, started a print and during the heating on the bed it came up with lost communication with MCU EBBCan not sure if its the cable of the board now, toolhead homed fine, was in the centre of the bed when it threw the error

[wind geyser]

hmm, heating bed. I heard issues about power supplies not enough to power all stuff. But I don't know if it produces communication lost.

[abstract moth]

i've got an a/c bed so i dont think that would be the case, start macro heat hotend last too

[wind geyser]

Well idk , Something's bothering : EBB on usb, iirc it isn't recommanded

[abstract moth]

gonna try re-flashing