DFU not detected, BTT board not detected, can't flash my BTT Octopus v1.1
Hi all, I'm trying to follow along with the RatOS configurator, I flash the Raspberry Pi, have RatOS up and running with the pretty dashboard
(this is my third time I keep re-flashing the Pi thinking I'm doing stuff in the wrong order... which I may have done)
I go into the configurator and klippy and moonraker are both green, I have the BTT Octopus v1.1 plugged in (from the start this time, so whilst the Pi was flashing). I follow the wizard, selecting my BTT Octopus v1.1, previously I've had the DFU boot option, but the system couldn't detect my BTT/DFU boot. This time round there is only the flash manually option (picture 1), I've tried pressing the restart button on my BTT, still no DFU option.
I go into the manual flash option, download the compile and download the firmware, put it onto a black SD card with 4kb allowance size, put this into the BTT board and turn everything off and on again, RatOS mainsail dashboard reappears (picture 3), I check the configurator and the BTT board still isn't detected and the check board status button does nothing (picture 2), however I do have a flash status light on my BTT board now... not sure if I ever had that before.
does anybody have any insight into where I'm going wrong/where I'm going wrong? I'm sure its me but I don't know what.
any help would be great as I've been playing around with this for a few days now and still stuck.
18 Replies
I've just tried another cable the red status light is no longer flashing but the board is still not detected
how are you powering the octopus board? Do you have everything other than power and USB disconnected from the octopus?
And how is the octopus connected to the pi, which usb ports?
thank you for replying, I've tried just power nothing else to the octopus board when I've tried flashing. And I've tried connected to the raspberry pi via the USB a's (tried a few, generally stick to the top or bottom in the corner, diagonally opposite the micro UBS power.
I have noticed watching some You tube videos that it could be my SD card being too big, got a smaller one on its way I'll try tomorrow, and when I downloaded the firmware, it downloaded as firmware.bin …. but none of my other downloads have the file extension showing. SO... I'm pretty sure I've tried to flash with firmware.bin.bin as well, I'll let you know if this is the issue
when I do try to flash again tomorrow (assuming my DFU option doesn't reappear) with the new smaller SD card and correct file name, is it okay to have it powered via the Raspberry Pi? via the USB a to USB c connection?
thanks again both
The reason i'm asking how you have your board connected is because you're saying how your board didn't want to boot into DFU mode either. So it sort of sounds like you didn't connect it correctly to the pi. You need to use the USB-C port on the Octopus for data communication.
it is connected by the USB C port on the octopus as shown in the diagrams, I've still got the jumper that the DFU boot process required in place, I've tried a few different cables since I lost the DFU boot option, and all of the USB A ports on the octopus. is it possible that I've tried to flash with the wrong firmware and this has, remove/over wrote/ corrupted the DFU boot process?
this is how the board is wire it still has the USB boot jumper suggested in the ratrig.dozuki assembly guide and the jumper suggested on the DFU boot option in the local.configurator. one question when my smaller (16gb) SD card arrives is it okay to flash whilst it's powered via the octopus, with RatOS turned off? it still says the octopus board is not detected in the configurator, its never detected the octopus which is why I'm assuming I need to do some sort of flashing first? or if the board is not being detected (and never has been detected) do I have a bigger problem?
I updated RatOS in the mailsail RatOS skin, and I now have the DFU boot option again🍾
this time after resetting the board its detected the DFU boot, i don't know what was different this time, after re-flashing the Pi, I only updated the RatOS, previously I updated RatOS and everything else, I complied all of the binaries in RatOS as before but did that before updating RatOS this time (basically pressing buttons hoping for the best)
I may have spoken too soon
or is this as far as I need to get before continuing to add drivers and wire everthing up?
just monologuing on here in case anybody else has the same issue, I pressed the Install Vcore Three config button, and it turned klipper off and klippy was asking for firmware resets which did nothing (I think this was getting to the MCU connection issues mentioned on here). So here's what works for me to get to a board being detected. Its in a different order to that described on the installation documents:
1. flash the raspberry pi as explained and get to RatOS and the configurator both being open and working
2. update RatOS firmware in the machine tab of RatOS - this makes the DFU boot option available for me, this is mentioned in the installation documentation below the control board and mainsail sections
3. update the other systems (klipper. moonraker etc.)
4. on the dashboard run the compile firmware script, I haven't seen this step mentioned anywhere, I might be missing it
5. go to the configurator, reset the control board and now when I check the DFU option it finds my Octopus board and I can DFU boot (i do have all the jumpers advised attached)
I think I'm done so I'm going to mark this as solved, thankl you both for the support
one question in case either of you see this, do I needc to worry about the octopus board being unresponsive
what do you mean?
the last image I shared, the board is detected when I try and flash it, but the configurator says its unresponsive, I'm hoping that's normal as there's nothing attached to the board?
No, that usually means it hasn't been flashed
This happens if your pi isn't connected to the internet when RatOS is used to flash a board on first run, ignore it and move on to mainsail, you should be good to go.
(this is fixed in 2.1)
this does nothing.
ah okay, thank you. I'll carry on setting up mainsail and wiring up my panel. thank you both
I get this message after flashing
Section 'gcode_shell_command copy_minion' is not a valid config section
You hard reset RatOS, very different issue. Please start your own thread (though for brevity, this will fix it:)