Update to 3.3 killed Wifi - file (re)location issue?
-
I have updated my (genuine) Duet 2 Wifi from firmware version 3.2 to 3.3 by uploading the file Duet2and3Firmware-3.3.zip using DWC and confirming the dialog prompt. After the update, I could hear the printer re-starting and going through its homing cycle, but the web interface did not come back. M115 issued through a PanelDue showed the firmware version correctly as 3.3, so the update appeared to have succeeded. M552 showed "WiFi module is being started", even after more than 10 minutes of run time. The Wifi module LED was showing a permanent blue. Cycling the Wifi module state with M552 S-1 followed by M552 S1 did not help.
M587 should show the network list, but it didn't. Instead, I got the message "Failed to retrieve network list: another SPI transfer is pending". I have recently connected an accelerometer to my printer and connected it as described in the documentation, but I have not yet configured the firmware to use it. However, physically disconnecting the accelerometer did not resolve the issue either.
I then tried to reapply the Wifi firmware update using M997 S1, which gave me the error message "Error: M997: file 0:/firmware/DuetWifiServer.bin not found". Examining the SD card folder structure on my PC, I could see all of the firmware files still located in /sys/. Apparently, the file relocations mentioned in the release notes have not been performed automatically - the folder was not even created.
I then moved the firmware over to the new folder manually and reapplied the Wifi firmware update using M997 S1. This finally resolved the problem.
I don't know whether there is some bug in the update procedure or just a fluke - but maybe this will help somebody who ran into the same issue.
-
@vwegert I think a couple of things happened at the same time, which caused the problem:
- You uploaded the 3.3 zip file under 3.2, so files get put in the 'sys' folder
- The update to 3.3 went okay for firmware and DWC
- The WiFi firmware failed to update (it happens, there's no error checking in the ESP firmware update process)
- Now on 3.3, you tried to update the WiFi firmware again, but the firmware folder hasn't been created (it only happens if you subsequently upload a firmware zip or bin file in 3.3), so the firmware can't find a relevant file.
You found one workaround, which is to create a firmware folder and add files. You can also (since RRF 3.3beta2) use the 'P' parameter in M997 to provide the absolute path and filename to use. See: https://duet3d.dozuki.com/Wiki/Gcode#Section_M997_Perform_in_application_firmware_update
Ian
