Upgrade gone bad

PRACTAC

I have a Duet3 6HC and a Duet Toolboard 1LC. I was upgrading to 3.4 from 3.3 and upgraded the 6HC with no issues. Started the upgrade on the Toolboard and thats when everything went south. I can not get my DWC to load. On my 6HC, I have 4 solid LED lights (no flashing lights) and on the toolboard, it flashes per normal. So far I have done the following:

-I have backed up my Pi and reimaged it, it did nothing,
-Attempted to flash the firmware directly to the 6hc via bossa , it shows successful, but nothing else happens. I have done this many times with the same outcome. I get a successful flash, and I also get a successful verify, but I can never connect to it via pronterface. as the comport is only showing BOSSA Program Port (COM4)

Does anyone have any other troubleshooting steps they can share so I can get my board operational? Much appreciated.

jens55

I just went through something similar and the problem was that the upgrade process changes the board IP number but as far as I know, that only applies to direct connected 6HC boards and not if you are using a pi. The steps for me where similar - upgraded with no issue but then could no longer connect to the web interface.
Good luck, it was very frustrating for me but thankfully there were patient people here that helped!

Phaedrux

How did you update the firmware initially? If you're using a Pi and SBC mode, then you use update the firmware with sudo apt update sudo apt upgrade only.

There was a bug fix in 3.4 that resulted in the MAC address being regenerated, which may result in the board getting a new DHCP address, however, if you are using an SBC, the Pi handles the networking.

Can you give us some clarification on your setup?

PRACTAC

@phaedrux
I did the initial upgrade via the raspberry pi with sudo apt update sudo apt upgrade for 6HC board. I do not use IP's (only http://name.local). Then I attempted the upgrade of the Toolboard via the DWC, by going into the firmware folder and right clicking the toolboard.bin file and upgrade firmware, It started the upgrade and the DWC, changed to a "connecting" screen, then I got a red popup at the bottom saying it could not connect. After about 20 min, I did notice that the LED's on the 6HC board were all lit and solid and the tool board was flashing per normal. After approx 20 min, I rebooted the printer and it went to the same screen and the same for the LED's. I used winscp to backup my my pi, then I formatted it, reimaged it with a new image from "https://pkg.duet3d.com/DuetPi.zip". I followed the instructions located (https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup) and was unsuccessful to go to duet3.local.
I then downloaded the "Duet3Firmware_MB6HC.bin" from the Duet Github, Powered down printer and removed power cable, put a jumper on the erase pins, connected a USB cable, removed the jumper from the erase pins, pressed the reset button, then checked my device manager and I saw "BOSSA Program Port (COM4)", so I started Bossa, mapped the Duet3Firmware_MB6HC.bin, checked "erase all", "Lock", and "boot to flash" then clicked "write". It was successful, then I clicked verify, it was successful. I then attempted to connect to pronterface, and it was unsuccessful no matter what speed I selected. I removed the USB cable from the mainboard and plugged it back in and nothing showed up in my device manager nor was I able to connect to pronterface. The only way I was able to see it in device manager is to add the jumper on the erase pins, and plug in the usb cable, then remove the jumper.

Hope that clears up any questions.

Phaedrux

Instead of pronterface can you try YAT to see if you can connect?

Can you try setting up an SD card to use in standalone mode in the Duet itself? The SD card would need a sys folder with the config files and the www folder with the files for DWC.

The default is for the Duet to get a DHCP address. You could check your router to find it and see if you can connect.

Alternatively, you can SSH into your pi or connect a screen and see what is going on there.

PRACTAC

@phaedrux I downloaded YAT and same as pronterface. I removed the raspberry pi and formatted a SD card, added the sys, and www folder inserted it into the 6HC and got nothing. I then redid the steps with the jumper on the erase pins, added the USB, removed the Jumper, pushed the reset button and got the Bossa Comport. So I mapped the same .bin file as above with the same boxes checked, as before, it was successful, clicked verify and it was successful. Exited Bossa to free up the com port for YAT and was connected, but got no replies from any of the commands I was submitting, such as M115 then tried to add the info for M587 in the even my "wpa_supplicant.conf" didnt work correctly and no replies.

Now onto the Raspberry pi. I reformatted the SD card, hardwired it to my LAN, got a valid, IP address, I can putty into it, and I can get to the WebUI I have tried with the 6HC board off, and then on and got the same results which I have included in a attachment (webui1.png)

PRACTAC

All, Just wanted to give a HUGE shoutout to @DHUSOLO for his assistance with the issues I was having with the upgrade to my Duet3 6HC. I am now fully functional thanks to him.

oliof

@practac Always great to hear things got resolved. It helps even more if the steps to resolution are documented for all to see (-: So what was the solution for you in the end?

dhusolo

@oliof in the end it was solved by reflashing the firmware with bossa. He was using a 10 foot cable. Told him to use a shorter USB cable and it worked.