Burn katapult firmware: No rp2040 in BOOTSEL mode was found

stevendejongnl commented 11 months ago

When I try to write the firmware to the hotkey pad I get an error.

~/katapult$ sudo make KCONFIG_CONFIG=config.hotkey flash FLASH_DEVICE=2e8a:000a --debug
GNU Make 4.3
Built for aarch64-unknown-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
Updating makefiles....
Updating goal targets....
 File 'flash' does not exist.
Must remake target 'flash'.
  Flashing out/katapult.uf2 
Loaded UF2 image with 21 pages
No rp2040 in BOOTSEL mode was found
Successfully remade target file 'flash'.

The device identifies itself as Bus 001 Device 009: ID 2e8a:000a Raspberry Pi Pico instead of Raspberry Pi RP2 Boot.

When I skip this step and do the rest. The whole klipper instance would not boot anymore when just adding the hotkey mcu to the printer.cfg:

[mcu hotkey]
serial: /dev/serial/by-id/usb-Raspberry_Pi_Pico_E66058919F823930-if00
restart_method: command

theminjus commented 11 months ago

Having similar issue , i have burn new loader , but klipper doesnt want to boot also mine is named as usb-Raspberry_Pi_Pico_E6625C4893418833-if00

llambion72 commented 10 months ago

I've started to install this hot key and i'va the same error. I can`t enable it.

vjeko2404 commented 10 months ago

I had the same issues but managed to get it working. Basically are the steps in readme correct and need to be execately followed. I missed one step during Katapult install and had above mentioned error. If your device identifies as usb-Raspberry_PiPico**** then the Katapult installation didn't worked well. Also, pay attention to "Press the boot button while inserting the USB Cable to put the Hotkey Pad into boot mode."

llambion72 commented 10 months ago

I've changed usb cable and now It works OK.

PeteUgrin commented 9 months ago

I had the same issues but managed to get it working. Basically are the steps in read me correct and need to be exacatly followed. I missed one step during Katapult install and had above mentioned error. If your device identifies as usb-Raspberry_PiPico**** then the Katapult installation didn't worked well. Also, pay attention to "Press the boot button while inserting the USB Cable to put the Hotkey Pad into boot mode."

Done it properly. Got the Katapult address and see the new mcu in the ssh. The problem starts when I include the hotkey.cfg. The printer just w8 to connect to the new mcu. When I comment out the include, the printer works fine. Got klipper 0.11.0. Might that be the problem? Or can it collide with the led effect?

Changed the cable. Did the installation step by step. Still wonder.

CBoismenu commented 9 months ago

Same problem for me it shows up has a Raspberry Pi Pico.

PeteUgrin commented 9 months ago

Got it! Problem solved! There are two buttons! One is boot and one is reset. Reset is bigger and better accessible. Boot button is smaller and way more hidden. Just do press the right one. Than everything works perfectly.

Also if you have klipper-led_effects installed, it will collide with the buttons LED setup in the hotkey cfg file. You will have to set up the hotkey LED effects via the klipper-led_effects.

https://github.com/julianschill/klipper-led_effect

stefi01 commented 8 months ago

thanks. there are two buttons, hard to find the button needed, it is around 5 oclock from the main ic and next to a jst plug but it worked.

FYSETC / Hotkey

Burn katapult firmware: No rp2040 in BOOTSEL mode was found #2