Unable to flash controller
My system seemed to go in the fritz today. I heard the part fan running full blast. This usually means that the controller has lost connection to the Raspi. I looked at the klipperscreen and it was blank. Tried to reboot but nothing happened. It was like there was no SD card in it. Having some practice with re-doing RatOS v2.1; I flashed a new card and started a new configuration. When it got to the controller setup, it could not connect. It was like it had no klipper running in it. I set it up in DFU mode and it find it then. I tried to flash and it looked like it worked but then after flashing it still could not connect. Believe me I tried several times. Having no luck, I then tried to reflash from command line. Again this seemed to work but after rebooting the controller, it just appears like there is no klipper running on the controller. I also tried to flash with an SD card. This also did not work. I am out of ideas. Attached are the debug files and some screen shots captured during troubleshooting. Any suggestions?
14 Replies
I have had it where it doesn't persist after reboot but otherwise acts fine. That's a corrupt bootloader
Rat-OS doesn't touch the bootloader, so that's why reflashing isn't helping
Is there a fix for that?
Never had to fix a boot loader before. Here is a document I found for an octopus 1.0 on the BTT GitHub site. Not sure if it’s the same procedure for a 1.1 or not. Proceed with caution https://github.com/bigtreetech/BIGTREETECH-OCTOPUS-V1.0/blob/master/Firmware/DFU%20Update%20bootloader/Octopus-DFU%20Update%20bootloader%20-%20en.pdf
GitHub
BIGTREETECH-OCTOPUS-V1.0/Firmware/DFU Update bootloader/Octopus-DFU...
This is Octopus open source material. Contribute to bigtreetech/BIGTREETECH-OCTOPUS-V1.0 development by creating an account on GitHub.
I asked btt for the original bootloader and then I manually flashed it with 0 offset
Have you tried disconnecting all the wires from the board (beside power to your pi if you use that) and using a new usb cable to see if something outside of the board is causing the problems by chance. Never seen a bad boot loader just bad boards unfortunately
I did try a different USB cable but there was no difference. i have not tried unhooking all the cables. Ugh...but worth a try. Looking thru the procedure to redo the bootload and it doesn't look to bad. I have done something like this in the past with Arduino and PIC processors.
I wish you luck. At a certain point might just be worth buying s new one but if it’s a bad switch or bed sensor causing it you would still be dealing with the same issue. Good luck and post back if you figure it out
I haven't heard PIC in awhile! 😂
Old school. My first programs stored on paper tape...
Well.... I reflashed the bootloader following the instructions in the link above. Pretty simple procedure actually. I then reran the RatOS configurator and reflashed Klipper in DFU mode. It now works! Yahoo!!! It has survived several reboots and power cycles. Wish I knew what took out the SD card and the Controller firmware but at least I now have a working printer. Thanks All.
Hooray! 🎉
congrats!
saved yourself some $$$
Thanks guys! now to get it back to "exactly" how it was configured. I had some files save but it did not reflect the changes made since recently after installing a BBT Filament sensor 2.0. Hopefully not too hard to recreate, especially since I only installed it a couple of weeks ago. I did find out that most people would recommend a BTT Octopus Pro H723 as a replacement controller.
Where did you find bootloader.hex file?
BTT GitHub. This is the octopus link https://github.com/bigtreetech/BIGTREETECH-OCTOPUS-V1.0/tree/master/Firmware/DFU%20Update%20bootloader/bootloader. Be very careful with this. Why do you think you need to do this? 99 out of a 100 times it’s something else wrong and not the boot loader. Good luck