automatic firmware failed
Dear RatOs developer
following the last Klipper update, I have a problem with the automatic firmware update with my manta 8P v1.1
My solution is to choose dfu mode at http://ratos.local/configure?step=1
the manta 8P v1.1 is detected and I have a choice between automatic or dfu firmware, as the automatic function failed previously when updating klipper, I chose dfu mode and the new implemented firmware works .
Since firmware.config is not standard on my system, what is causing the automatic update to fail?
The only difference is
CONFIG_INITIAL_PINS="PC3"
TIA
14 Replies
Not sure. The output from dfu-util is very strange. Can you try running the board scripts manually over SSH and paste the output here?
pi@ratos:~ $ sudo ./printer_data/config/RatOS/boards/btt-manta-m8p-11/flash.sh
/home/pi/klipper /home/pi
Flashing /dev/btt-manta-m8p-11
Flashing out/klipper.bin to /dev/btt-manta-m8p-11
Entering bootloader on /dev/btt-manta-m8p-11
sudo dfu-util -p 1-1.4 -R -a 0 -s 0x8002000:leave -D out/klipper.bin
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/
dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
dfu-util: No DFU capable USB device available
Failed to flash to /dev/btt-manta-m8p-11: Error running dfu-util
If the device is already in bootloader mode it can be flashed with the
following command:
make flash FLASH_DEVICE=0483:df11
OR
make flash FLASH_DEVICE=1209:beba
If attempting to flash via 3.3V serial, then use:
make serialflash FLASH_DEVICE=/dev/btt-manta-m8p-11
make: *** [src/stm32/Makefile:111: flash] Error 255
Flashing failed.
As i made few experiment with canboot before ,maybe the bootloader is corrupted?
What about the compile part?
That would make sense yes
no issue
It does look like the board doesn't enter DFU mode when programatically commanded to enter the bootloader by klipper.
i will to reload the M8P_bootloader.bin from BTT will see
Entering bootloader on /dev/btt-manta-m8p-11This means the board (klipper) succesfully booted into the bootloader. So if it doesn't show up as a DFU device after that, that means the bootloader didn't enter DFU mode.
so i restore the bootloader with this cde "sudo dfu-util -d ,0483:df11 -R -a 0 -s 0x8000000:leave -D ./klipper/M8P_bootloader.bin"
pi@ratos:~ $ /home/pi/klipper /home/pi
Flashing /dev/btt-manta-m8p-11
Flashing out/klipper.bin to /dev/btt-manta-m8p-11
Entering bootloader on /dev/btt-manta-m8p-11
Device reconnect on /sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4/1-1.4:1.0 sudo dfu-util -p 1-1.4 -R -a 0 -s 0x8002000:leave -D out/klipper.bin
sudo dfu-util -p 1-1.4 -R -a 0 -s 0x8002000:leave -D out/klipper.bin
dfu-util 0.11-dev
dfu-util 0.11-dev
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device... be required in a future dfu-util release
Device ID 0483:df11 USB device...
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...#0 ...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a) = No error condition is present
Device returned transfer size 1024 flash] Error 25511 flashed with the
DfuSe interface name: "Internal Flash "
Downloading element to address = 0x08002000, size = 28872
Erase [=========================] 100% 28872 bytes
Erase done.
Download [=========================] 100% 28872 bytes
Download done.
File downloaded successfully
Yaaay 🙂
yes et voila, the issue was the boot loader
awesome 👍
i had the same issue with my voron 2.4r2 powered by Ratos, so the manta issue is fixed after replacement of the boot loader , only issue remaining is with my EBB SB2209 after the comand "sudo ./printer_data/config/RatOS/boards/btt-sb2209-10/compile.sh" following error -> Version: v0.11.0-304-gf7567a0d
Linking out/klipper.elf
cp: cannot stat '/home/pi/klipper/out/klipper.bin': No such file or directory
the flash portion is working only the compilation give me an issue sudo ./printer_data/config/RatOS/boards/btt-sb2209-10/flash.sh ok
no klipper.bin available
17:47
echo: Firmware binaries compiled successfully! You can find them in the firmware_binaries folder in the machine tab!
17:47
Command {compile_binaries} finished
17:47
make: *** [Makefile:101: out/board-link] Error 2
17:47
/bin/sh: 1: cannot create out/board-link: Permission denied
17:47
Compiling firmware for BTT manta-m8p v1.1
17:47
~/klipper ~/klipper
17:47
Running Command {compile_binaries}...:
17:47
echo: Compiling binaries.. This can take up to 10 minutes. Please do not turn off your Raspberry Pi!
17:47
COMPILE_FIRMWARE
well ~/klipper sudo make clean et voila compil and flash ok for my toolboard sb2209
as my sb2209 is working satis with ratos, how to update the RatOS git ? i ''m new with github