Open odairgoncalvess opened 1 year ago
The leading zero is omitted from the log however it does not impact the internal representation of the UUID. The issue seems to be that Klipper did not jump to CanBoot when requested. This suggests that either CanBoot is not installed on the board or the version of Klipper on the board is not capable of performing the jump.
If you know CanBoot is installed you will need to manually enter the bootloader, presuming you enabled a method for doing so when you built CanBoot. After flashing the latest version of Klipper future updates should be able to perform the jump.
@odairgoncalvess If you are using the BTT U2C [STM32G0B1] version for your CAN bus interface then this firmware may help.
NOTE: this is not the firmware for the BTT U2C [STM32F072] version
@Arksine Thanks for the reply. The BTT42 board is with CanBoot and Klipper V0.11.0-86-g6026a99a. I will update manually by DFU and try in the next update.
@NAPCAL Thanks for the help. I'm not using the BTT U2C. I'm using the following hardware with CanBoot and CANbus: Orange Pi Zero2, MKS Monster8 V2 and BTT EBB42 V1.2.
It's work! Thank you!
I updated CanBoot v0.0.1-40 to v0.0.1-43 and it worked.
Hi. I cannot flash the klipper.bin file using the flash_can.py script. It seems that the script cannot recognize the UUID of my EBB42 V1.2 BTT and omits the most significant digit - which is the number zero.