Duet3 - firmware update with RPi

Via

Having a few issues with setup of new Duet3 so wanted to update firmware before posting about those just in case.

However seem to be in a bit of a loop regarding which way to do it correctly.

On firmware download page it says...
User of Duet 3 + attached SBC should install this release from the package server so as to get the corresponding updated version of Duet Control Server too.

On Installing and Updating wiki page it says...
the Duet 3 + Pi process is quite different. See Getting Started with Duet 3 for more information.

However the getting started with Duet 3 page says...
If using an attached RPi, you can update the firmware in Duet Web Control as usual

So is it just as usual? Or is there a different process to follow and if so where can I find out about this?

chrishamm

It is recommended to install firmware updates only via apt, i.e. the standard Linux utility for package management. If you find a problem and would like to try a new firmware build, you can install custom firmware files via the System page of DuetWebControl.

Via

@chrishamm I have done an apt update / upgrade however it is showing firmware as 3.0beta12

chrishamm

@Via Can you run M997 and check the firmware version once again?

Via

Just retried apt update and saying all up to date.

root@Daedalus:~# apt update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://pkg.duet3d.com stable InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
root@Daedalus:~#

Did M997 and gone nuts...


15/05/2020, 18:50:22 	Error: Bad command: Q0 @"Miscellaneous"
15/05/2020, 18:50:22 	Warning: heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 538C.
15/05/2020, 18:50:22 	Error: Bad command: Q0 @"Custom settings are not defined"
15/05/2020, 18:50:22 	Error: Bad command: Q0 @"Heater model parameters"
15/05/2020, 18:50:22 	Error: Bad command: Q0 @"Tools"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"Fans"
15/05/2020, 18:50:19 	Warning: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"Heaters"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"Z-Probe"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"Endstops"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"Axis Limits"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"Drives"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"General preferences"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"generated by RepRapFirmware Configuration Tool v2.1.8 on Thu May 14 2020 14:51:44 GMT+0100 (British "
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"executed by the firmware on start-up"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @"Configuration file for Duet 3 (firmware version 3)"
15/05/2020, 18:50:19 	Error: Bad command: Q0 @""
15/05/2020, 18:50:19 	Connection established
15/05/2020, 18:50:19 	Incompatible firmware, please upgrade as soon as possible
15/05/2020, 18:50:14 	Failed to upload dwc2settings.json
Operation failed (Reason: DCS is not started)
15/05/2020, 18:50:12 	M997
15/05/2020, 18:50:12 	Error: Could not flash the firmware binary after 3 attempts. Please install it manually via bossac.
15/05/2020, 18:50:04 	Warning: Firmware update imminent

Now saying incompatible firmware so guessing DWC is up to date but the firmware flash didn't go through.

A Former User

@Via said in Duet3 - firegrmware update with RPi:

15/05/2020, 18:50:12 Error: Could not flash the firmware binary after 3 attempts. Please install it manually via bossac.

ref update via usb https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

(or if you have the Duet connected to the pi via USB just run wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash)

Via

Cheers, got it done with bossa, hopefully was a one off so back to heaters now...

chrishamm

@Via You have to run apt-get upgrade to perform the actual software update, apt-get update only updates the package lists. But I'm glad to hear you've got it running again.

Danal

@Via said in Duet3 - firmware update with RPi:

On firmware download page it says...
User of Duet 3 + attached SBC should install this release from the package server so as to get the corresponding updated version of Duet Control Server too.
On Installing and Updating wiki page it says...
the Duet 3 + Pi process is quite different. See Getting Started with Duet 3 for more information.
However the getting started with Duet 3 page says...
If using an attached RPi, you can update the firmware in Duet Web Control as usual
So is it just as usual? Or is there a different process to follow and if so where can I find out about this?

I will see if I can't make that all make more sense... check in 24 hours.

Flex3D

i still have the same Fault. I was just using sudo apt-get upgrade and update. The Flash fails and now i'm a bit curious about if i need to make a hard reset with the Jumper, unplug the ribbon cable to the Pi, take a other usb to micro usb as a connection to the Duet micro usb port?
Bossa is already installed on the Pi Image.
When i will make the Reset, the ribbon cable must be unplugged from the Pi to the Duet and than i can power it like usual from the VIN, make the reset and after with the USB to micro USB cable i should flash it?
Sorry this is a bit wired for me and i'm stuck there before the sudo update and upgrade it seems to work like normal and now it doesn't read out any sensors.
It should not be possible to disassemble the whole Board again to just make a firmware upgrade and to reassemble it any time or is it?

22/05/2020, 16:41:56 Error: Bad command: Q0 @"Miscellaneous"
22/05/2020, 16:41:56 Error: Bad command: Q0 @"Custom settings are not defined"
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Tools"
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Fans"
22/05/2020, 16:41:53 Warning: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Heaters"
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Filament Sensor"
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Endstops"
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Axis Limits"
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Z-Probe"
22/05/2020, 16:41:53 Error: Driver 2 does not support x0 microstepping with interpolation
Driver 3 does not support x0 microstepping with interpolation
22/05/2020, 16:41:53 Error: Bad command: Q0 @"Drives"
22/05/2020, 16:41:53 Connection established
22/05/2020, 16:41:53 Bad command: Q0 @"Configuration file for Duet 3 (firmware version 3)"
22/05/2020, 16:41:53 Bad command: Q0 @"General preferences"
22/05/2020, 16:41:53 Bad command: Q0 @"generated by RepRapFirmware Configuration Tool v2.1.8 on Thu May 21 2020 14:04:30 GMT+0100 "
22/05/2020, 16:41:53 Bad command: Q0 @""
22/05/2020, 16:41:53 Bad command: Q0 @"executed by the firmware on start-up"
22/05/2020, 16:41:53 Incompatible firmware, please upgrade as soon as possible
22/05/2020, 16:41:44 m997
Error: Operation has been cancelled
22/05/2020, 16:41:44 Error: Could not flash the firmware binary after 3 attempts. Please install it manually via bossac.
m115 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_VERSION: 3.0beta12 ELECTRONICS: Duet 3 MB6HC FIRMWARE_DATE: 2019-11-02b1

jay_s_uk

RRF 3.0 RC beta12 had a fault for a lot of users where updating via the normal method didn't work.
Bossa is the only way to update to a higher version

A Former User

@Flex3D looks like you're still on the 3.0-beta12 the board likely shipped with, and its probably easier to connect the Duet3's micro USB port to the Pi and run the Bossa update, no need to disconnect the ribbon cable. The alternative would be to try and update to 3.0, them 3.1.0, then 3.1.1.

Seeing as you have functioning firmware (responds to M115) running the command below should send the command M999 P"ERASE" command to the duet and start bossa to flash the firmware found in the reprapfirmware package.

(or if you have the Duet connected to the pi via USB just run wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash)

or follow the documentation.

ref update via usb https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

Flex3D

@bearer said in Duet3 - firmware update with RPi:

@Flex3D looks like you're still on the 3.0-beta12 the board likely shipped with, and its probably easier to connect the Duet3's micro USB port to the Pi and run the Bossa update, no need to disconnect the ribbon cable. The alternative would be to try and update to 3.0, them 3.1.0, then 3.1.1.

Seeing as you have functioning firmware (responds to M115) running the command below should send the command M999 P"ERASE" command to the duet and start bossa to flash the firmware found in the reprapfirmware package.

(or if you have the Duet connected to the pi via USB just run wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash)

or follow the documentation.

ref update via usb https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

I bridged the erase function like told in dozuki to reset it first and gave it a reboot. Than i connected the duet to my PC and it now has issues to identify the duet board itself. I bought a new usb micro cable too, to be sure but it's not working at all. Bossa shows me an error.

At least the blinking red light is off now but it's not possible to flash anything with bossa at the PC or to enter any G-Code...

Phaedrux

Nothing shows up in device manager?

Do you have a USB hub, preferably powered, to put between the pc and duet?

Flex3D

@Phaedrux said in Duet3 - firmware update with RPi:

Nothing shows up in device manager?

Do you have a USB hub, preferably powered, to put between the pc and duet?

No, do you have a link to a good powered USB Hub?
Can't i get these firmware elsewise on the Duet? I i will try tomorrow those Command from @bearer with a erased Board if that may help.

Phaedrux

Pretty much any cheap usb hub would do. Also try other ports, or a different PC or laptop.

A Former User

@Flex3D said in Duet3 - firmware update with RPi:

At least the blinking red light is off now but it's not possible to flash anything with bossa at the PC or to enter any G-Code...

The blinking LED is normal when the firmware is running, and when erased it will not accept any G-Code, only the bossa programming. If the PC is having problems, then definitively try using the Pi instead I've had a lot more success with that - you can follow the dozuki or run the wget command, its all the same at the end of the day.

Flex3D

Flex3D 26 May 2020, 23:34
@bearer wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash was written to stdout, than i've made a reboot. The board fails to connect to DCS like before
By the Way, I bought a USB Powerhub which made no difference

Flex3D

@bearer what did you mean with lsusb? Command not found.

A Former User

@Flex3D said in Duet3 - firmware update with RPi:

what did you mean with lsusb? Command not found.

it just lists the usb devices on the pi (to be run in ssh shell or terminal. but as long as the script said it couldn't find /dev/ttyACM0 then odds are its a connectivity issue