STM32F407 not installing firmware after katapult

[f8m8]

Hi, I'm trying to install Klipper on SKR PRO v1.2 which has STM32F407 on board. However I detected after installing klipper.bin, the board cannot be recognized by PC (windows and linux with different usb ports were checked). I thought it has sth to do with bootloader, so decided to install katapult to determine it. Now it has completely been dead. The only way the mcu was flashable was via sd card, and now the sd with the deployer.bin on it doesn't flash! Any help is much appreciated.

[Arksine]

It sounds like Klipper was built with an incorrect configuration. If you used the same configuration to build Katapult's deployer then your device is bricked. DFU doesn't work on the SKR Pro so you will need a programmer to recover.

I would recommend asking for assistance on the Klipper discord or discourse. You are likely going to need someone willing to give you live assistance.

[Arksine]

FWIW, to get you started, you'll need a programmer like the following: https://www.amazon.com/HiLetgo-Emulator-Downloader-Programmer-STM32F103C8T6/dp/B07SQV6VLZ/ref=sr_1_1_sspa?keywords=st-link+v2&sr=8-1-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1

Once you have it, you wire it up the the SWD pins on the board, close the boot0 jumper, reset, and use the following software to connect:

https://www.st.com/en/development-tools/stm32cubeprog.html

With that tool you can erase flash, back it up, and most importantly upload. There are likely plenty of tutorials out there, but as mentioned previously I think you will benefit most from having someone assist you live on Discord if possible.

[NAPCAL]

@Arksine Wouldn't using the boot0 jumper force it into USB DFU mode after clicking reset?

When I used an STLink on a board, selecting connect on the STCubeProgramer didn't require any other connections but to SWD pins.

[Arksine]

The SKR Pro has a design flaw that prevents it from entering DFU mode. IIRC it has to do with the capacitors on the crystal.