Unable to update klipper on Sovol Zero toolhead MCU

[Blenky]

Basic Information:

Printer Model: Sovol SV08 Running a ZERO toolhead with BTT U2C Adapter
MCU / Printerboard: Sovol SV08 Silent 64-bit Mainboard with Advanced TMC2209 Drivers
Host / SBC CB1_Debian11_minimal_kernel5.16_20240319
klippy.log klippy.log (3.1 MB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…I recently installed a ZERO toolhead running EDDY NG on my SV08. It was working great until just recently when there was a klipper update. Now I am no longer able to update the toolhead MCU even after reflashing the firmware on the toolhead. I have backed kllipper to Version v0.13.0-264 and successfully update the main board MCU after reflashing the firmware but I was not successfull reflashing the TH MCU. Even though they all say they are at v0.13.0-264. Here is the error I am getting. I have good communication with the CAN adapter. But I do not get the TH UUID when I run a query. Any help is greatly appreciated.

[Blenky]

this is the error I am getting.

[cardoc]

Is the toolhead MCU still on Sovol’s bootloader or have you managed to get Katapult to flash?

[Blenky]

the ZERO toolhead comes with Katapult already on it but after I started experiencing porblems I have reflashed Katapult to it.

[cardoc]

Have you tried this?

sovol/printer_data/build/extra_mcu_update_fw.sh

Note the path and filename for the .bin file.

[Blenky]

Well I just discovered that by uninstalling EDDY NG and replacing the EDDY NG commands in printer.cfg with the ZERO commands for EDDY I get a clean startup. So now I an going to do all the updates to the latest klipper and if I get a clean start I will reinstall EDDY NG. I will report back

[Blenky]

I am still unable to update klipper to the toolhead MCU but no problem for the main MCU and I was following the esoterical guide and I used this script to troubleshoot the py files.

wget -qO - debug.esoterical.online | sh

You can see the file here. Hoping you can make any sense of it.

https://termbin.com/eid0

[Blenky]

I did try the extra_mcu_upate_fw.sh after changing the file locations and the UUIDs. I am not 100% which UUID I should be using for the bootloader. The default one is 61755fe321ac and the one I originally got from the 1st querry is 27ed790d8665. This is what I used to try and update it.
echo “Start extruder_mcu_update_fw.sh now!!!”

if [ -f /home/biqu/printer_data/build/extruder_mcu_klipper.bin ]; then

if [ -f /home/biqu/printer_data/build/flash_can.py ]; then
    echo "Found flash_can.py"
else
    echo "No flash_can.py found in /home/biqu/printer_data/build. Exiting..."
    exit 1
fi

echo "Get into bootloader ..."
python3 ~/printer_data/build/flash_can.py -i can0 -f ~/printer_data/build/extra_mcu_klipper.bin -u 27ed790d8665 &
check_pid=$!
sleep 5
kill $check_pid

bootloader_id="27ed790d8665"
echo "Using default UUID $bootloader_id for firmware update."

echo "Flashing MCU firmware with UUID: $bootloader_id"
python3 ~/printer_data/build/flash_can.py -i can0 -f ~/printer_data/build/extra_mcu_klipper.bin -u "$bootloader_id"

if [ $? -eq 0 ]; then
    echo "Firmware update completed successfully!"
else
    echo "Error: Firmware update failed."
    exit 1
fi

else
echo “No extruder_mcu_klipper.bin found in /home/biqu/printer_data/build. Exiting…”
exit 1
fi

[Blenky]

this is the only thing I see that I don’t like in the debug file. I am thinking I need to reflash the firmware to the toolhead with the ST Link. Thoughts?

[cardoc]

Is the klippy service running on the host computer?

[Blenky]

Not when I try to flash.

[Blenky]

All good now. I had to reflash the zero firmware .bin file to the toolhead and then was successful installing the latest klipper to it. Thanks for the help.