Failed to upgrade firmware
-
Can you send M122 by USB terminal and post the response here?
At what point were you at when the power went out? What method were you using to update?
-
@phaedrux
The file system showed no files when lights went out. M122;
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JKF6-3S86R-1A7GL
Used output buffers: 1 of 24 (12 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75032 of which 188 recycled
Never used RAM 15320, free system stack 185 words
Tasks: NETWORK(ready,8.0%,521) HEAT(suspended,0.0%,330) MAIN(running,92.0%,305) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:29:54 ago, cause: power up
Last software reset at 2022-04-18 08:38, reason: User, GCodes spinning, available RAM 15496, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 31.2, current 31.3, max 31.8
Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 101.05ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with "m122" in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.02ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8- WiFi -
Network state is starting2
WiFi module is disabled
Failed messages: pending 0, notready 12, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok
- WiFi -
-
To clarify, the power went out a minute or so after starting.
-
It looks like the main firmware is at 3.3 and the wifi module isn't started, and perhaps needs the wifi firmware reflashed as well.
Try sending
M552 S-1
M552 S0
M552 S1and see what it says each time.
Then try sending M997 S1 to reflash the wifi module and see what it says.
-
@phaedrux Worked like a charm. Thank you very much. Wonder why isnt this in the documentation?
-
@brian However, i now have this error: Phaedrux MODERATOR 18 Apr 2022, 21:30
It looks like the main firmware is at 3.3 and the wifi module isn't started, and perhaps needs the wifi firmware reflashed as well.Try sending
M552 S-1
M552 S0
M552 S1and see what it says each time.
Then try sending M997 S1 to reflash the wifi module and see what it says.
-
Now after uploading files :
Error: M997 S0 Firmware binary "0:/firmware/Duet3CombinedFirmware.bin" not found.
Even after uploading this file?
-
@brian which version of DWC is currently running? You can find out on the Settings/General page.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 WDC 3.4.0 I was able to get it working by copying the file to the sd card and then running the upload again. Then right away had timeout issues as soon as a print started but been through that before so replaced M307 line, with M307 H1 A350 C500 D50 B1. Everything seems to v3.4 now. So hopefully all is well.
-
Now that you have access to DWC again the best way to insure you have all the correct files in the correct places for future updates is to upload the main firmware zip file to the system tab in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.0/Duet2and3Firmware-3.4.0.zip
Upload the zip file as is, do not extract it first. It will reflash all the firmwares and update all the DWC files. Next time you need to update firmware use the same technique of uploading the main release zip file for best results.
-
@phaedrux Thank you, i will do that.
