Board flashing error
I am trying to flash the octopus on my V3.1 and i keep getting
Octopus V1.1 detected but is unresponsive.
Klipper doesn't seem to be running on your board, which may indicate faulty firmware or a faulty board. Please check your board and try flashing it again.
trying to flash after doesnt work and i once saw the start of a script error in red
Any ideas what to try
28 Replies
Try flashing via sd card?
tried it it doesnt seem to flash from it. Tried 3 sd cards too
this is the red error
Error
Could not flash firmware to Octopus V1.1: An error occured while attempting to run script: Running board script /home/pi/printer_data/config/RatOS/boards/btt-octopus-11/flash.sh\n\n /home/pi/klipper /home/pi/ratos-configurator Flashing /dev/btt-octopus-11 Flashing out/klipper.bin to /dev/btt-octopus-11 dfu-util 0.11-dev Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Flashing failed. /home/pi/ratos-configurator '}
with 1 sd card i get\
Version mismatch
The board is running version v0.11.0-219-g645a1b83 but you your pi is on version v0.11.0-219-g645a1b836. If you want to update your board click 'flash again' below.
that was fixed in a later version of ratos - please update it
i downlaoded fresh do i have to update via ratos web interface before configuring?
tried that, stil lcomes up with an error
still comes up with an error when doing SD card flashing or DFU flashing?
Yeah it says it’s detected but encountered an error says to try to reflash cycle through did or manual and still get the error
Octopus V1.1 detected but is unresponsive.
Klipper doesn't seem to be running on your board, which may indicate faulty firmware or a faulty board. Please check your board and try flashing it again.
this is the error
then on auto flash i get
Could not flash firmware to Octopus V1.1: An error occured while attempting to run script: Running board script /home/pi/printer_data/config/RatOS/boards/btt-octopus-11/flash.sh\n\n /home/pi/klipper /home/pi/ratos-configurator Flashing /dev/btt-octopus-11 Flashing out/klipper.bin to /dev/btt-octopus-11 dfu-util 0.11-dev Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Seems like flashing failed, but the device is still in DFU mode. Attempting to recover. Flashing out/klipper.bin to 0483:df11 dfu-util 0.11-dev Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Opening DFU capable USB device... Device ID 0483:df11 Device DFU version 011a Claiming USB DFU Interface... Setting Alternate Interface #0 ... Determining device status... DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations Clearing status Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present DFU mode device DFU version 011a Device returned transfer size 2048 DfuSe interface name: "Internal Flash " Downloading element to address = 0x08008000,
size = 31864 Erase [ ] 0% 0 bytes Erase [= ] 6% 2048 bytes Erase [=== ] 12% 4096 bytes Erase [==== ] 19% 6144 bytes Erase [====== ] 25% 8192 bytes Erase [======== ] 32% 10240 bytes Erase [========= ] 38% 12288 bytes Erase [=========== ] 44% 14336 bytes Erase [============ ] 51% 16384 bytes Erase [============== ] 57% 18432 bytes Erase [================ ] 64% 20480 bytes Erase [================= ] 70% 22528 bytes Erase [=================== ] 77% 24576 bytes Erase [==================== ] 83% 26624 bytes Erase [====================== ] 89% 28672 bytes Erase [======================== ] 96% 30720 bytes Erase [=========================] 100% 31864 bytes Erase done. Download [ ] 0% 0 bytes Download [= ] 6% 2048 bytes Download [=== ] 12% 4096 bytes Download [==== ] 19% 6144 bytes Download [====== ] 25% 8192 bytes Download [======== ] 32% 10240 bytes Download [========= ] 38% 12288 bytes Download [=========== ] 44% 14336 bytes Download [============ ] 51% 16384 bytes Download [============== ] 57% 18432 bytes Download [================ ] 64% 20480 bytes Download [================= ] 70% 22528 bytes Download [=================== ] 77% 24576 bytes Download [==================== ] 83% 26624 bytes Download [====================== ] 89% 28672 bytes Download [======================== ] 96% 30720 bytes Download [=========================] 100% 31864 bytes Download done. File downloaded successfully Submitting leave request... Transitioning to dfuMANIFEST state Resetting USB to switch back to Run-Time mode Flashing failed. /home/pi/ratos-configurator '}
Now im getting a 502 on the configure screen
is there a way to downgrade the octopus board with an earlier FW
as im currently getting Version mismatch
The board is running version v0.12.0-394-g7f89668d but you your pi is on version v0.12.0-394-g7f89668d6. If you want to update your board click 'flash again' below.
Did you update the configurator?
yes
and i got that when trying to flash the board after
Can you show us what version of the configurator you have?
ratos-configurator
v0.0.0-67-gc5b78c02-inferred
can i make sure im getting your advice right as it differs from the installation instructions
You want me to , from fresh SD card
set wifi up, update ratos,update configurator, set up board
The Web says to
set wifi up, set up board, update ratos, update configurator ( and everything else)
@miklschmidt is that the latest Rat-OS configurator?
No this is a branch he should not be on
This looks to be an error that was fixed a while ago. So normally the documentation is correct, but the RC versions may need to be updated before doing other steps
@tcsjc can you please post your moonraker.log?
im just running through with a fresh install.
@miklschmidt do you want it pre or post updates?
so my versions post update are
Beacon Surface Scanner
v2.0.0-18-g51826a8
crowsnest
v4.1.9-1-gd75a3ae
klipper
v0.12.0-394-g7f89668d
KlipperScreen
v0.4.5-24-g7431ad82
LinearMovementAnalysis
v1.0.0-0-g309a81c
mainsail
v2.13.0
moonraker
v0.9.3-3-gccfe32f2
RatOS
v2.0.2-36-g230929e
ratos-configurator
v2.0.2-deployment-1-gc5b78c02
RatOSTheme
v2.0.2-0-g515851d
timelapse
v0.0.1-143-gc7fff11
System
OS-Packages
i then get the error for board flash
Version mismatch
The board is running version v0.12.0-394-g7f89668d but you your pi is on version v0.12.0-394-g7f89668d6. If you want to update your board click 'flash again' below.
This is RatOS 2.0, i recommend you install 2.1
where
The board is running version v0.12.0-394-g7f89668d but you your pi is on version v0.12.0-394-g7f89668d6. is fixed 🙂@miklschmidt i havent made the jump to 2.1 as its RC and not in latest/stable. Unfortunately i just had to fresh install due to a failed SD as it was working before.. Does that mean i need to move all my 3.1's to RATOS2.1
The only thing left is the documentation, it is stable
No you can ignore the error (well, warning) and proceed, it's just cosmetic. 2.0 is dead at this point though. The release candidate is stable.
We will still look at updating 2.0 machines automatically once everything else is done though, however i'm not sure it makes much sense at this point.
i get this in updatemanager in 2.1
The Update Manager has not been initialized yet. This is normal when you start the system for the first time. Please click on the refresh button to initialize all components.
Yeah so everything is normal and you should click the refresh button.
@miklschmidt I set the board up outside of the printer as per instructions. Now I’ve installed it and wired everything it can’t see the octopus
Well then you know you done goofed somewhere during wiring as you already know it works as expected 🙂
any ideas where? dont think it can be power as it powers ok , what might interfere with usb board detection
shorts
double check all your wires
particularly endstops or anything you changed (ie, wire wasn't taken out of box and plugged in).