Octopus V1.1 F446 detected but is unresponsive.
During the initial setup I have the Octopus board unrensponsive.
I’ve tried to flash again multiple times but nothing to do.
I’ve also tried deconnectin all the cables and removing the jumpers to try the Micro SD mode formatting an 8GB card with
sudo newfs_msdos -F 32 -c 8 -v FW /dev/disk6s1
But nothing to do: I get a fixed blue led near the card but nothing happens on startup or after pressing reset button.
Should I have to to reinstall this bootloader https://github.com/bigtreetech/BIGTREETECH-OCTOPUS-V1.0/tree/master/Firmware/DFU%20Update%20bootloader/bootloader with STM32 cube programmer?GitHub
BIGTREETECH-OCTOPUS-V1.0/Firmware/DFU Update bootloader/bootloader ...
This is Octopus open source material. Contribute to bigtreetech/BIGTREETECH-OCTOPUS-V1.0 development by creating an account on GitHub.
27 Replies
Post a debug zip, i won't be able to tell without one (you can download it from the sidebar in the configurator)
Did you forget to take off the boot0 jumper?
It seems like it keeps resetting to DFU
Solution
If not, the bootloader is dead, and then yeah you should try and flash it.
In past. Now I’m trying with everything disconnected and boot jumper on only one pin
That doesn't make much sense. Take it off.
The board won't boot klipper properly after a full reset when it's on.
I'm guessing that's your issue
it's been flashed (plenty of times), you're just repeatedly telling it to enter DFU mode each time it boots (which is often done programatically) 😄
Was just a place to keep it and don’t forget where it is 🙂
It worked 🥳
Ah so the bootloader was indeed broken. Configurator really should have an option to attempt that fix, could use Katapult for most of the supported boards too.
Glad you got it fixed! 🙂
I thought you had added that back in Rat-OS 2.0 days?
woot, bootloader flashing?
Yeah, didn't you add a default bootloader?
i've talked about implementing a way to flash the bootloader before, but never did it.
Or am I really losing my mind
no
I can't really add a "default" bootloader, it has to be compiled for and fit the specific mcu on the board
Ok, I'm just going crazy then. This was around the time I messed up my bootloader on the manta and you said "hold my beer"
I might have actually been drunk that time, i dno 😂😂
Anyways, you should be able to get the original bootloader from btt and others right?
yeah he already sorted it 🙂
Yeah, but I'm talking about integrating those original bootloaders with the configurator
Only a very limited subset are published
Seems like a simple job of using dfu to write it, right?
hence the mention of Katapult
which works on most STM boards as well as the rp2040
If it's the original precompiled one.. sorta, yes.
Sounds like a good plan then
Yeah, I recall asking btt for the original and they gave me the hex output
Katapult needs specific mcu configuration, then compilation, then flashing (and a lot of edge case handling)
Then we need to implement the interface for flashing a bootloader
Oof that sounds like a headache
yeah but it works
it's not difficult, just takes time
it's great for RP2040 specifically, allows you to flash initially without the stupid "mount as usb drive" stuff