RcTomcat1
commented
3 years ago mcu 'mcu': Timeout on connect
Did you try and reflash the bootloader as descriibed here: https://github.com/FYSETC/FYSETC-SPIDER/tree/main/bootloader Did you try and flash a self-compiled klipper.bin instead of the prebuild ones? It is just make menuconfig, selecting the right values followed by a make. Copy the newly created file to sd card and rename it.
I would try to reflash the bootloader so it supports a 32k offset + flash a selfbuild 32k offset firmware.bin afterwards
Hello maybe one of you can help me?
I bought a board on 2021 -06 -28 directly from the official FYSTEC store at Ali. It should have a 32kb bootloader.
I was able to flash klipper.bin with 64k bootloader offset onto the board by using an SD-Card. (so it was equiped with the old bootloader?)
Since I often had "internal server" erros I decided to rebuilt my system. I made the mistake of using the STMCubeprogrammer this time. I flashed the 32kb bootloader and the corresponding 32K-Uart-Klipper.bin (bootloaderoffset 0x08008000). After that I can no longer connect to Klipper. I tried the old bootloader( 0x10000) with 64k-uart-klipper.bin (0x08010000). I tried with no bootloader (-> offset 0x08000000)
The result is always the same. Klipper does not connect to the board. See Klippy.log --> klippy.txt
What can I do??????