Yames
November 19, 2024, 9:50am
1
klippy (1).log (1.2 MB)
Fill out above information and in all cases attach your klippy.log file Pasting your printer.cfg is not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
…I am unable to date the MCU on my octopus pro V1.1 board from V0.10 to V0.12. I have followed the voron docs for this board so i am confident that the menuconfig option are correct. When flashing via serial (with the board in bootloader mode) I get “Error 255” and when trying serialflash I get “Error 1”… Abandoning this approach and copying the firmware.bin file onto an SD card and inserting it into the octopus board, when the board boots it still shows V0.10…
I am at a loss and any words of wisdom would be appreciated.
Also, are there any negative consequences for having the MCU running at older version? Klipper is happy to allow the mis-match, so is it just fine to continue printing?
Sineos
November 19, 2024, 11:55am
2
Please show your settings and the complete output of the flashing command
Yames
November 19, 2024, 1:41pm
6
and lastly serialflash. Sorry these are single posts, as i am new user the web page would only let me upload one at a time.
Sineos
November 19, 2024, 1:57pm
7
Try following approach (your settings seem correct if it really is a F429 MCU):
make clean
make distclean
make menuconfig
make
Put the board into the DFU mode and verify that it is actually in DFU mode with the lsusb command.
Then flash with:
make flash FLASH_DEVICE=1234:5678
Replace 1234:5678 with the device ID from the lsusb command.
Yames
November 19, 2024, 2:35pm
8
Sadly i got the same result
Sineos
November 19, 2024, 3:30pm
9
Please show the output of
sudo dfu-util -l
when the board is in DFU mode.
@Yames :
Are you using putty?
You can do text copy & paste. It’s better to read than a screen copy.
Yames
November 19, 2024, 3:45pm
13
I am using Git Bash
[sudo] password for pi:
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 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/
Found DFU: [0483:df11] ver=2200, devnum=4, cfg=1, intf=0, path="1-1.1.2", alt=3, name="@Device Feature/0xFFFF0000/01*004 e", serial="207631674730"
Found DFU: [0483:df11] ver=2200, devnum=4, cfg=1, intf=0, path="1-1.1.2", alt=2, name="@OTP Memory /0x1FFF7800/01*512 e,01*016 e", serial="207631674730"
Found DFU: [0483:df11] ver=2200, devnum=4, cfg=1, intf=0, path="1-1.1.2", alt=1, name="@Option Bytes /0x1FFFC000/01*016 e/0x1FFEC000/01*016 e", serial="207631674730"
Found DFU: [0483:df11] ver=2200, devnum=4, cfg=1, intf=0, path="1-1.1.2", alt=0, name="UNKNOWN", serial="207631674730"
Sineos
November 19, 2024, 4:19pm
14
This looks strange. Maybe the bootloader is burned?
If you feel brave, try installing Katapult:
git clone https://github.com/Arksine/katapult
cd katapult
make menuconfig #<------------- Use the same settings as for Klipper
make
Put the board into DFU and then issue:
sudo dfu-util -R -a 0 -s 0x08000000:force:mass-erase:leave -D ~/katapult/out/katapult.bin -d 0483:df11
Then try flashing Klipper as per the command above.
Yames
November 19, 2024, 4:34pm
15
i dont know if I am feeling that brave :). I am off to formnext so I wont be able to reply until Monday, but thank you for your help so far and ill try any suggestions when I return.
1 Like
mjfsch
November 20, 2024, 1:18pm
16
its likely this same issue, seems to be an issue with the bootloader.
same error will appear if you try and use dfu to install katapult
mjfsch
November 20, 2024, 1:52pm
17
did some searching as i have the same board.
the issue can be fixed by updating from dfu-util 0.9 to 0.11
you can do this by compiling a new version like this:
git clone git://git.code.sf.net/p/dfu-util/dfu-util
cd dfu-util
./autogen.sh
./configure # on most systems
sudo make install
dfu mode now works as expected
3 Likes
