Yes, I had Klipper mainline v12 installed until it stopped working after 4-5 prints. After that, the mcu could no longer be found in lsusb and the error was there.
I have now tested a little more. I couldn’t flash the firmware from Artillery either. But what did work was katapult. I did the following:
H-RST button pressed on the board -> lsusb shows that it is in DFU mode
cd ~
git clone https://github.com/Arksine/CanBoot
pip3 install pyserial
cd CanBoot
make menuconfig
STM32F401 selected, rest default
make clean
make
sudo dfu-util -a 0 -D ~/CanBoot/out/canboot.bin --dfuse-address 0x08000000:force:mass-erase:leave -d 0483:df11
After that it was listed in lsusb again:
I then tried to install Klipper. This worked with the v10 from Artillery, with the v12 supposedly also, but there is no light on the extruder. Under ls /dev/serial/by-id/ it is listed as usb-Klipper_stm32f401xc_44001B000E51333037383638-if00, before the flash with klipper as usb-katapult_stm32f401xc_44001B000E51333037383638-if00. So it seems to have changed something. In Mainsail I now get a different error:
mcu 'rpi': Unable to connect
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer
I then tried to fix the problem according to these instructions RPi microcontroller - Klipper documentation (Install the rc script + Building the micro-controller code), but did not notice any change. This is stored in the printer.cfg of the printer:
[mcu rpi]
serial: /tmp/klipper_host_mcu
If I run ls in /tmp, klipper_host_mcu is not listed. I think if this problem is fixed, the stm32 should also work properly now that it is finally displayed in lsusb again. But how can I fix the problem with the ‘rpi’ mcu?