flash_can.py not going into boot loader mode

[treaves]

I'm trying to upgrade Klipper on a Manta M8P board that was already running successfully. The latest version of Klipper requires the MCU's be updated as well.

I'm following the steps I found in a closed ticket that I thought were to be able to do this. When I run the python3 ~/katapult/scripts/flash_can.py -r -u your-uuid command, it does not report an error and the Bus 001 Device 005: ID 1d50:606f OpenMoko, Inc. Geschwister Schneider CAN adapter device disappears. But nothing ever shows up in /dev/serial/by-id/. I also see this in the dmesg output: [ 284.055674] usb 1-1.4: USB disconnect, device number 5 [ 284.056028] gs_usb 1-1.4:1.0 can0: Couldn't shutdown device (err=-19)

Has anyone overcome this issue?

[Bazeone]

I'm having the same issue with an Octopus STM32F446. It was working fine 2 version ago. Same problem with flashtool.py and flash_can.py.

Sending bootloader jump command... Bootloader request command sent Flash Success INFO:root:Socket Write Error, closing

[Bazeone]

working on v0.0.1-75-g90eb71b6.

[Arksine]

An issue was introduced recently when some deprecated code was removed, as mentioned it should be fixed now. The OP appeared to have some kind of driver issue, hopefully BTT resolved that.

[Igor-Yavych]

@Arksine I still have the same issue. OpenMoko device disappears from the lsusb list, but does not enter DFU mode. It ends up in some kind of limbo. Board: Manta M8P v2 Katapult: Latest Klipper: Latest

[Igor-Yavych]

Configuring Katapult to use USB on PA11/PA12 for Manta M8P v2 (when it's used as a CAN bridge) and then requesting bootloader via flashtool will somewhat work (unlike when it's set to canbus) and will allow Manta to be flashed via serial, but not via DFU. Pretty much all guides out there flash Katapult set to CAN bus interface for Manta for some reason.