Open asha77 opened 3 years ago
Can i ask why you want to set to DFU at step 8?
Just to check how it starting with and without jumper. Important note: on step 7 it starts OK from STM32cube, not from hard reset (power cycle reset button). Steps 8, 9 - made with hard reset.
You can use our prebuild to test the bootloader: https://github.com/FYSETC/FYSETC-S6/tree/main/firmware/Pre-builds, it is Marlin build, you can send "M105" command to test if board works ok. I double check my side, it works. And i recommend a hard reset after you flash firmware.
Hi,
I am experiencing the same scenario exactly. Did you ever resolve this?
Hi, after some manipulations i get board back to work. Unfortunately i not tried to reproduce this issue, i can't privide any clear instruction to fix it.
Compiling klipper for no bootloader solved the issue for me, it now works after a reboot.
I got this issue once again. yes, klipper with no bootloader option did it:
After restart S6 octoprint can communicate with klipper.
There is some info in the fysetc section on the klipper discord about flashing these boards.
Hi, i've got error with new bootloader and klipper firmware with S6 board. Firmware uploaded using STM32cube and DFU. Sequence:
I can repeat steps 1-7 to make it work again, but it is not expected scenario.
Please, advice what to do with that, thank you in advance.