Toolboard update confusion....

Chriss

Hi *,

I upgraded my mini5+ from 3.3b1 to 3.3b6, so I updated the DWC too. So far so cool.
I moved the firmware leftovers from 0:/sys to 0:/firmware. Next step was the update of my two toolboards (1.0). So I uploaded the bin file via the DWC. The DWC asked me for a firmware update, I confirmed. I checked the status of the first toolboard (two in total) and it was still on 3.3b1.
So I tried a "M997 B121" and the console answered with:

Error: M997: Firmware file Duet3Firmware_TOOL1LC.bin not found

I checked the content of the SD card and the file was located in 0:/firmware. I copied the file to 0:/sys/ and the upgrade worked as expected.

What's wrong here? My understanding? Maybe a caching issue with the browser? I have the impression from an update to 3.4b6 on a other printer with one toolboard that it was working as expected. :?

Cheers, Chriss

Phaedrux

I think the toolboard were looking in the old location because they were not yet updated.

How did you go from 3.3 b1 to 3.3 b6? Did you stop off at 3.3 final in between? When updating to 3.3 with the full zip file it should have updated the toolboards as well.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip

Also the 3.3 update is a tricky one because of the change to the /sys and /firmware folders. There are corner cases where things can get confused unfortunately. Usually uploading the 3.3 full zip file twice is enough to get everything in sync and should stay that way going forward. Barring that, manually placing the files needed as a work around as you have done is the way to go.

Chriss

@phaedrux Thanks Phaedrux, that made the behaviour clear to me. I was afraid that there was a bug or a unexpected behaviour in the firmware here. But this is logical behaviour from your point of view.

First of all, I had a typo in my initial post, it is 3.4.0beta6 not 3.3b6. (You guys are to fast. )

I did not thought a lot about the update process to be honest. I just uploaded the needed files via the DWC, I used the firmware images I had already on my other printer with a mini5+ running 3.4.0beta6, that triggered that behaviour I believe now. The move from /sys to /firmware was something my "above shoulder ringbuffer" has dropped already.

Confusion solved, thanks!

Cheers, Chriss