Unable to flash katapult

[MaestroLmpio]

Basic Information:

Printer Model: Ender5+ frame
MCU / Printerboard:btt octopus pro 429, EBB42 via CAN
Host / Rpi 4
n/a

After I long time not using the printer, I finally had time to update the thing.
with KIAUH I updated all.

then I wanted to flash the bootloader katapult, I followed the steps in the esoterical.online guide.

However when I run lsusb, I see my board in DFU mode, but it doesn’t send the bootloader, and gives me following message:

the output of lsusb -d 0483:df11 -v :

some one can give me a push in the right direction?

[MaestroLmpio]

Got the octopus working.

At the end I used the STMcubeProgrammer to flash the board. After that I could see ther serialbyID, and I was able to flash Klipper on it.

With the toolhead loading the bootloader was not a problem;

But here I have a problem with klipper, it doesn’t show a uuid after flashing klipper…

klippy.log (5.0 MB)

[EddyMI3D]

Please do not post screen copy images. When you use Putty, you can copy and paste text.
Don’t forget to use the Preformatted Text feature of the forum editor for this.

[Sineos]

I’m not sure what you are trying to achieve. What role do you intend the Octopus to have? Maybe see Setting Up udev rules for multiple canbus interfaces - #21 by Sineos

[MaestroLmpio]

Hi, the octopus is going to be the USB to CAN host.

RPI --usb → OCTOPUS --can–> EBB42

I had this working 2yrs ago, but by flashing klipper with SD card to the octopus and STMcubeProgrammer to flash the EBB.

Didn’t use the printer for a year, fired it up and clicked “update all”, which messed up everything.

I read about katapult that would make it possible to flash the EBB over CAN and the Ocotopus over USB. so I followed this guide:

Home

But for some reason the Octopus didn’t want to load the katapult bootloader, but by using the STMcubeProgrammer it worked. But like said in the previous post, I don’t see any UUID for application klipper after flashing the toolhead with the klipper.bin…

[Sineos]

Generally:

• The Octopus needs to be correctly flashed with a “USB to CAN Bridge” firmware configuration
• The Octopus does not get a CAN UUID
• The EBB needs a CAN firmware configuration
• Already successfully configured devices do not appear in a canbus_query. You may need to prevent Klipper from autostarting, power everything off and repower to use the command again.
• CAN UUIDs do not change with firmware updates. So if you updated correctly the old UUID should still be valid