-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Klipper and new bootloader #20
Comments
Can i ask why you want to set to DFU at step 8? |
Just to check how it starting with and without jumper. |
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. |
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.
The text was updated successfully, but these errors were encountered: