Duet3 - firmware update with RPi
-
@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...
-
Nothing shows up in device manager?
Do you have a USB hub, preferably powered, to put between the pc and duet?
-
@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. -
Pretty much any cheap usb hub would do. Also try other ports, or a different PC or laptop.
-
@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 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 -
@bearer what did you mean with lsusb? Command not found.
-
@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
-
@bearer said in Duet3 - firmware update with RPi:
@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
I bought jesterday a new usb type B Cable so there should be no reason for. Else ones flying around here aren't working too.
-
@Phaedrux said in Duet3 - firmware update with RPi:
Pretty much any cheap usb hub would do. Also try other ports, or a different PC or laptop.
Seems not. Same issue like you have to use a USB Type C Charger to power up the Duet and RPi at the first Preconfig.
My new USB Power Hub with Power Plug makes no difference but seems to be USB 2.1 and has to low Voltage Output. -
it is possible there is something wrong with the board, but thats less likely as it was responding to dcs for the update.
you're connecting the micro usb port of the duet 3 to one of the full size usb
ba ports on the pi? the pi doesn't need drivers to see the serial port, which is why its often a better alternative to windows.you can install lsusb with
sudo apt install usbutils
but it should be present, and it most likely won't show anything of interest as the pi isn't detecting the duet.dmesg | tail -n 20
may be more relevant, shortly (a second or two) after plugging the usb cable in the duet. -
@bearer said in Duet3 - firmware update with RPi:
it is possible there is something wrong with the board, but thats less likely as it was responding to dcs for the update.
you're connecting the micro usb port of the duet 3 to one of the full size usb b ports on the pi? the pi doesn't need drivers to see the serial port, which is why its often a better alternative to windows.
you can install lsusb with
sudo apt install usbutils
but it should be present, and it most likely won't show anything of interest as the pi isn't detecting the duet.dmesg | tail -n 20
may be more relevant, shortly (a second or two) after plugging the usb cable in the duet.K, Thanks. I will sort that out tomorrow.
-
@bearer
It fails to connect longer.
I just followed the instructions and gave it a Reset with a jumper on erase. Any else i could do?
Can't I run it from its own Micro SD with its firmware and remove the Pi?
The powered usb Hub didn't help at all to flash it from a PC. I think 5 Volt on its output is still to low and it must be a usb 3 Hub with quick charge function which are quite expensive. -
@Flex3D said in Duet3 - firmware update with RPi:
t must be a usb 3 Hub with quick charge function
duet doesn't support usb3 nor quick charge, but depending on what is connected to the duet most usb ports should be able to power it (disconnect any displays if you think you have a power issue)
@Flex3D said in Duet3 - firmware update with RPi:
I just followed the instructions and gave it a Reset with a jumper on erase. Any else i could do?
if you didn't get a serial port before or after trying the reset jumper then there isn't much left to do.
@Flex3D said in Duet3 - firmware update with RPi:
Can't I run it from its own Micro SD with its firmware and remove the Pi?
not if the firmware erase was successful, then it will need flashing; if you had created your own topic I might not have suggested erasing the firmware based on the output of one of the earlier posts.
new problem, new topic, please.