Firmware Upgrade

MartinMV

m552 s1
Turn off the current WiFi mode before selecting a new one
ok
Warning: VIN under-voltage event (9.3V)[Warning: 1 byte already buffered but not sent anymore.][Warning: 5 bytes already buffered but not sent anymore.]
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
m552
WiFi module is being started
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
Warning: VIN under-voltage event (9.4V)Warning: VIN under-voltage event (9.4V)
m587
m587
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m587
Failed to retrieve network list: another SPI transfer is pending
ok
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
m552
WiFi module is being started
ok
m552 s1
Turn off the current WiFi mode before selecting a new one
ok
m112
Emergency Stop! Reset the controller to continue.
ok
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
ok
m552
WiFi module is being started
ok
m552 s0
ok
m552
WiFi module is being started
ok
m552 s1
Turn off the current WiFi mode before selecting a new one
ok
m552 s0
m552 s0[Warning: 8 bytes already buffered but not sent anymore.]
m552
WiFi module is being started
ok
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: 08DGM-917DA-G4MS4-6JTD4-3SN6T-1TXV8
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 73064 of which 300 recycled
Never used RAM 17176, free system stack 168 words
Tasks: NETWORK(ready,7.9%,521) HEAT(suspended,0.0%,386) MAIN(running,91.9%,458) IDLE(ready,0.1%,29), total 99.9%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:22:59 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 0
MCU temperature: min 22.7, current 24.6, max 25.4
Supply voltage: min 2.0, current 26.5, max 26.5, under voltage events: 2, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 34982, standstill, SG min/max not available
Driver 1: position 34982, standstill, SG min/max not available
Driver 2: position 34982, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, 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.36ms; fastest: 0.13ms
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 2.3ms, 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 = -1 -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: 0.25ms; 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 16, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok

jay_s_uk

@MartinMV run

M552 S0

And then

M997 S1

And let us know if it updates ok

MartinMV

@jay_s_uk

does not work

m552 s0
ok
m977 s1
Warning: M977: Command is not supported
ok
m991 s1
Warning: M991: Command is not supported
ok
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok

jay_s_uk

@MartinMV in what way? You need to give a bit more information than "does not work" otherwise you ain't going to get any help

MartinMV

@jay_s_uk

why cant your firmware function when uploaded, are we in the stoneage here?
I mean you take premium prices for this shit and then it just should work every time.

MartinMV

@MartinMV

what about I send you my board and I get it back with the newest firmware installed at your cost?

jay_s_uk

@MartinMV ok, thanks for your input. Good luck getting your issue sorted

MartinMV

@jay_s_uk

I just followed your instructions and it bricked the device.

You want to fuck me now?
It will cost you more than my device in the future, I will not forget and tell everyone about your way damaging things and standing in for the repair.

Maybe I even will make a vid about it.

I hope you go broke with this kind of support.

jay_s_uk

@MartinMV I don't work here....

MartinMV

@jay_s_uk

you just closed two of my threads... if this is your hobby, then be it...

But however I have written to Duet3D and demand compensation for their moderator linikng files that bricked my board. Can t be that they not tested it and bricked another board 2 years before without removing the faulty firmware in the meantime.

droftarts

@MartinMV It sounds like the WiFi firmware didn't flash properly. This occasionally happens, and the RRF 3.3 update seems to be the most susceptible to this, because of the transition to putting the firmware files in the /firmware folder, rather than the /sys folder like older firmware versions. The main firmware is fine. Connect via USB, send

M552 S0
M997 S1 P"0:/sys/DuetWiFiServer.bin"

This will install the WiFi firmware that's in the sys folder. This should restore functionality.

Once that's done, please take a deep breath, and moderate your tone. We're all trying to help here.

Ian

Phaedrux

@MartinMV said in Firmware Upgrade:

@jay_s_uk

does not work

m552 s0
ok
m977 s1
Warning: M977: Command is not supported
ok
m991 s1
Warning: M991: Command is not supported
ok
M997 S1
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found
ok

If you send m115 what firmware version does it report?

Firmware 3.3 is a bit of a tricky one because it changes the location that firmware files are stored to a dedicated /firmware folder. Please check if that folder exists and that the files from the 3.3 zip file are present there.

chrishamm

@MartinMV said in Firmware Upgrade:

Error: M997: File 0:/firmware/DuetWiFiServer.bin not found

This message says it all, you can't update the WiFi server firmware without a firmware binary. Take out your microSD card, put it into a card reader, and check if the firmware directory exists on the root directory of the SD card. If it does, copy DuetWiFiServer.bin from https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.3/Duet2and3Firmware-3.5.3.zip to that folder. When that's done, put it back into the Duet, power-cycle it, and run M997 S1 via USB serial console. That should get it going again.

Also, keep it low, I'm not going to tolerate more offenses here. We're here to help and not to get insulted.

droftarts

@MartinMV I assume one of the above posts from forum admins/mods got you going again? It would be good if you could respond with what resolved the issue for you, so that other users that have the same issue can find this thread, and don't get stuck down the same rabbit hole that you did.

Did you manage to complete the firmware update to the latest version successfully?

Ian