Board cannot update firmware
-
Sounds like you file needs to be named exactly "DuetWiFiFirmware.bin" with the same exact capitalization.
Jeff
-
I have tried that, and it doesn't work. I have updated my old duet board using the downloaded file names before. I also doubt that is the issue, as if it was everyone else who downloaded the latest update would have this problem.
Does anyone know how to start from scratch and reupload firmware?
-
I used backup procedure #3 when I replaced my main CPU on the board. See link:
Jeff
-
If you upload new firmware via DWC and accept DWC's offer to install it, then DWC will do the file renaming for you. If you copy the new firmware file to the SD card any other way, then you need to rename the file to the correct name yourself.
-
If you upload new firmware via DWC and accept DWC's offer to install it, then DWC will do the file renaming for you. If you copy the new firmware file to the SD card any other way, then you need to rename the file to the correct name yourself.
That I did not know. How clever is it (just strip the last characters in the file name or inspect the binary header for what firmware type it is?)
-
I will be using the software in back up procedure 3 tonight to bring the board back to life… However I might suggest that incompatible firmware/DWC/wifiserver releases should come with a warning message to stop incompatible installs. Having the wiki is great, but it feels backwards to have to find important info in it after you make the mistake....
-
I will be using the software in back up procedure 3 tonight to bring the board back to life… However I might suggest that incompatible firmware/DWC/wifiserver releases should come with a warning message to stop incompatible installs. Having the wiki is great, but it feels backwards to have to find important info in it after you make the mistake....
You may actually have to downgrade the firmware and then update DWC and WiFIServer then upgrade as needed.
Jeff
-
I have tried that, and it doesn't work. I have updated my old duet board using the downloaded file names before. I also doubt that is the issue, as if it was everyone else who downloaded the latest update would have this problem.
If you send M997 manually then the file names in /sys must be exactly right, e.g. DuetWiFiFirmware.bin.
The general rule is:
1. Install new main firmware. This is always compatible with the previous version of DWC and DuetWiFiServer - although not necessarily compatible with much older versions of DWC.
2. Install the new DuetWiFiServer, if there is a new one.
3. Finally, install the new DWC.
In what way did it "not work" when you renamed the downloaded firmware file to DuetWiFiFirmware.bin and sent M997 S0 ?
-
It did exactly the same as explained above, if I try to upload it via the DWC it says 'error' in the loading bar (same as any upload including .stl files for printing), and if I upload it via usb I get the "DuetWifiFirmware.bin not found" message. This is with and without renaming the files.
-
See backup procedure #1 at https://duet3d.com/wiki/Updating_main_firmware.
-
Last night , experienced almost the same thing.
Updated in the wrong order via the web interface.
Could see a message that renaming failed in the web interface.
Adding the new DuetWifiFirmware.bin to the sd card in the sys folder then M997 S0 would wipe the DuetWifiFirmware.bin file and
gave the error :Firmware binary "DuetWiFiFirmware.bin" not found.
Procedure 3 did the trick, updated to the latest firmwares and webinterface now. -
Last night , experienced almost the same thing.
Updated in the wrong order via the web interface.
Could see a message that renaming failed in the web interface.
Adding the new DuetWifiFirmware.bin to the sd card in the sys folder then M997 S0 would wipe the DuetWifiFirmware.bin file and
gave the error :Firmware binary "DuetWiFiFirmware.bin" not found.
Procedure 3 did the trick, updated to the latest firmwares and webinterface now.Exactly the same for me as well. Renaming files did not work at all, no matter what interface I used. Quite a pain though, I feel like there should be a warning message for installing non-compatible firmwares.
-
Another in the heffalump trap!
I had loaded the Web Interface first. Fix was like procedure 1.
-
Power down and extracted the uSD card
-
Copy and rename the latest set of files
-
Reinserted card and powered on
-
Send the command on the web interface M997 S0 this upgraded the firmware
-
Then upgraded the WIFI server using the web server
Looking better - so back to rebuild the Ormerod 1. Such quiet motors - lovely.,
-
-
Another in the heffalump trap!
I had loaded the Web Interface first. Fix was like procedure 1.
-
Power down and extracted the uSD card
-
Copy and rename the latest set of files
-
Reinserted card and powered on
-
Send the command on the web interface M997 S0 this upgraded the firmware
-
Then upgraded the WIFI server using the web server
Looking better - so back to rebuild the Ormerod 1. Such quiet motors - lovely.,
Nice, I guess i was the odd ball out, I updated the web controller and interface no problem but couldn't update the firmware-had to rename it, and now all set.
Now I just need to figure out how to enable the configurator file I made. Commence the forum search!Edit:Nailed it! on to BLtouch
-
