upgrade 3.4 to 3.5 causes downgrade to 2.05

magnets99

Hi All,
I'm new to this but i have the seemingly impossible scenario that when upgrading past 3.4 the duet2 drops back to 2.05

I got a second hand Duet2 wifi based 3d printer (it appears to be in an ultimaker 2+ housing). The board silscreen says V1.03

It's very fancy with a bltouch, a water cooled block, pt100 temperature sensors and a remote direct drive, a filament sensor etc.
I'm super happy, but....

It had been sitting about for a while, it was running firmware 2.03 with wifi server 1.23 and DWC 2.1.7 (yes really).

I tidied it up and checked all the screws etc and printed out an ok'ish Benchy in PLA which took 2Hours and 7minutes. I'm using Orca slicer.

I want to tune it up to get better quality and faster so i figured i need to update the firmwares first.
I read the instructions thoroughly and (after soldering a 10K pullup resister onto the filament sensor) i upgraded to 2.05.1
This had a strange affect of downgrading the DWC to 2.0.4, duet wifi server remained at 1.23

I went through to firmware version 3
then on to 3.3

so far so good, the instructions say that after 3.3 i can just go straight to the latest. When i did the device reports:

[11:01:33:218] FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1␊
[11:01:33:218] ok␊
and i can no longer use the DWC as it just says connecting and "incompatable firmware at the bottom"

i tried this a few more times wiht the same result.
I figured there must be firmware bins hanging around that are getting pickled up instead. so i looked at the
sd car dcontents int he manual and deleted my files to match, there was now nothing in sys or firmwares that ended in BIN
after a few hiccups with the IAP i got it back to 3.3 then tried 3.5, same issue.
Next i went thourgh it all again but went to 3.4.
This worked, but when i tried to go to 3.5 from 3.4 it failed again.

To confirm:
I was on
Firmware 3.4.1 wifi 1.26 DWC 3.5.4

when i use the DWC OR the fallback method 1 to go to 3.5.4 (latest as of writing)

i then end up with an unusuable DWC, but cutecom reports
Firmware 2.05.1 wifi 1.02

Here is the log showing that:


[10:56:28:646] === Diagnostics ===␊
[10:56:28:646] RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later␊
[10:56:28:651] Board ID: 08DGM-9T6BU-FG3S8-6J1F4-3SN6K-KULMG␊
[10:56:28:651] Used output buffers: 1 of 26 (21 max)␊
[10:56:28:651] === RTOS ===␊
[10:56:28:651] Static ram: 23860␊
[10:56:28:651] Dynamic ram: 74160 of which 0 recycled␊
[10:56:28:651] Never used RAM 14060, free system stack 192 words␊
[10:56:28:651] Tasks: NETWORK(ready,13.2%,257) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,86.7%,458) IDLE(ready,0.1%,30), total 100.0%␊
[10:56:28:651] Owned mutexes: USB(MAIN)␊
[10:56:28:651] === Platform ===␊
[10:56:28:651] Last reset 00:01:22 ago, cause: software␊
[10:56:28:651] Last software reset details not available␊
[10:56:28:651] Error status: 0x00␊
[10:56:28:651] Aux0 errors 0,0,0␊
[10:56:28:651] Step timer max interval 0␊
[10:56:28:651] MCU temperature: min 38.3, current 38.7, max 38.7␊
[10:56:28:651] Supply voltage: min 0.4, current 0.4, max 0.4, under voltage events: 0, over voltage events: 0, power good: no␊
[10:56:28:651] Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0␊
[10:56:28:651] Events: 0 queued, 0 completed␊
[10:56:28:651] Driver 0: ok, SG min n/a␊
[10:56:28:651] Driver 1: ok, SG min n/a␊
[10:56:28:651] Driver 2: ok, SG min n/a␊
[10:56:28:651] Driver 3: ok, SG min n/a␊
[10:56:28:651] Driver 4: ok, SG min n/a␊
[10:56:28:651] Driver 5: ␊
[10:56:28:651] Driver 6: ␊
[10:56:28:651] Driver 7: ␊
[10:56:28:651] Driver 8: ␊
[10:56:28:651] Driver 9: ␊
[10:56:28:651] Driver 10: ␊
[10:56:28:651] Driver 11: ␊
[10:56:28:651] Date/time: 2024-12-26 10:56:28␊
[10:56:28:651] Cache data hit count 3450235364␊
[10:56:28:651] Slowest loop: 3.97ms; fastest: 0.13ms␊
[10:56:28:651] I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0␊
[10:56:28:651] === Storage ===␊
[10:56:28:651] Free file entries: 10␊
[10:56:28:651] SD card 0 detected, interface speed: 20.0MBytes/sec␊
[10:56:28:651] SD card longest read time 1.9ms, write time 0.0ms, max retries 0␊
[10:56:28:651] === Move ===␊
[10:56:28:651] DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000␊
[10:56:28:651] === MainDDARing ===␊
[10:56:28:651] Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1␊
[10:56:28:651] === AuxDDARing ===␊
[10:56:28:651] Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1␊
[10:56:28:651] === Heat ===␊
[10:56:28:651] Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0␊
[10:56:28:651] === GCodes ===␊
[10:56:28:651] Segments left: 0␊
[10:56:28:651] Movement lock held by null␊
[10:56:28:651] HTTP is idle in state(s) 0␊
[10:56:28:651] Telnet is idle in state(s) 0␊
[10:56:28:651] File is idle in state(s) 0␊
[10:56:28:651] USB is ready with "m122" in state(s) 0␊
[10:56:28:651] Aux is idle in state(s) 0␊
[10:56:28:651] Trigger is idle in state(s) 0␊
[10:56:28:651] Queue is idle in state(s) 0␊
[10:56:28:651] LCD is idle in state(s) 0␊
[10:56:28:651] Daemon is idle in state(s) 0␊
[10:56:28:651] Autopause is idle in state(s) 0␊
[10:56:28:651] Code queue is empty␊
[10:56:28:651] === Network ===␊
[10:56:28:651] Slowest loop: 201.63ms; fastest: 0.08ms␊
[10:56:28:651] Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions␊
[10:56:28:651] HTTP sessions: 1 of 8␊
[10:56:28:651] - WiFi -␊
[10:56:28:651] Network state is active␊
[10:56:28:651] WiFi module is connected to access point ␊
[10:56:28:651] Failed messages: pending 0, notready 0, noresp 2␊
[10:56:28:651] WiFi firmware version 1.26␊
[10:56:28:651] WiFi MAC address 80:7d:3a:15:a5:3a␊
[10:56:28:651] WiFi Vcc 3.40, reset reason Turned on by main processor␊
[10:56:28:651] WiFi flash size 4194304, free heap 26928␊
[10:56:28:651] WiFi IP address 192.168.1.31␊
[10:56:28:651] WiFi signal strength -65dBm, mode 802.11n, reconnections 0, sleep mode modem␊
[10:56:28:651] Clock register 00002002␊
[10:56:28:651] Socket states: 0 0 0 0 0 0 0 0␊
[10:56:28:651] ok␊
[10:59:46:335] Trying to connect at 230400 baud:  success␊
[10:59:52:114] Erasing 4096 bytes...␊
[10:59:52:205] Erasing 626688 bytes...␊
[10:59:54:221] Uploading file...␊
[10:59:56:546] 5% complete␊
[10:59:58:796] 10% complete␊
[11:00:01:113] 15% complete␊
[11:00:03:340] 20% complete␊
[11:00:05:640] 25% complete␊
[11:00:07:939] 30% complete␊
[11:00:10:230] 35% complete␊
[11:00:12:449] 40% complete␊
[11:00:14:737] 45% complete␊
[11:00:17:026] 50% complete␊
[11:00:19:312] 55% complete␊
[11:00:21:544] 60% complete␊
[11:00:23:847] 65% complete␊
[11:00:26:142] 70% complete␊
[11:00:28:433] 75% complete␊
[11:00:30:686] 80% complete␊
[11:00:33:011] 85% complete␊
[11:00:35:297] 90% complete␊
[11:00:37:577] 95% complete␊
[11:00:39:759] Upload successful␊
[11:00:39:862] Shutting down USB interface to update main firmware. Try reconnecting after 30 seconds.␊
[11:01:25:479] RepRapFirmware for Duet 2 WiFi/Ethernet Version 2.05.1 dated 2020-02-09b1␊
[11:01:25:479] ␊
[11:01:25:479] Executing config.g...HTTP is enabled on port 80␊
[11:01:25:479] FTP is disabled␊
[11:01:25:479] TELNET is disabled␊
[11:01:25:479] Done!␊
[11:01:25:479] RepRapFirmware for Duet 2 WiFi/Ethernet is up and running.␊
[11:01:25:479] WiFi module started␊
[11:01:25:479] WiFi module is connected to access point LaserBadger, IP address 192.168.1.31Bad command: RepRapFirmware fm115␊
[11:01:29:869] ok␊
[11:01:33:218] FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1␊
[11:01:33:218] ok␊

I've also noticed that on 3.3 i have wifi version 2.2.0 but from 3.4 onwards this drops to 1.26

Any ideas what's going on?

(this is all done with just the board active not the printer powered up, and i'm pretty sure my config file is all messed up but thats a different problem).

Phaedrux

I suggest starting with a fresh SD card, use Bossa to flash the firmware directly to 3.5.4 and then extract the DWC files for 3.5.4 directly to the WWW folder.

At that point you should be able to connect to DWC and upload the zip file release for 3.5.4 again just to make sure all the required files are present for your future updates.

Then you can bring over your config files from the original SD card.

magnets99

@Phaedrux
Thanks, if no one else has a better solution i'll have to do that.
I've got it back to 3.4 so i thought i'd work on fixing up the config.g file.

Phaedrux

What file exactly are you using to update?

You should be uploading this one as a zip file.

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

dc42

@magnets99 most likely you have an old version of the IAP file installed and that file is loading an old firmware file from the /sys folder, whereas 3.4 and later take the file from the /firmware folder. If you upgrade to 3.4 again, check that both DWC and RRF report version 3.4, delete any .bin files in /sys and upload the latest IAP file. That IAP file should be included in the zip file for the 3.5.4 release.

magnets99

@Phaedrux

yes that's the one i'm using.
it's the same one linked from the how to upgrade page

magnets99

@dc42

So that's what i figured was going on. but here is my entire file tree, and if i go to the DWC and upload Duet2and3Firmware-3.5.4.zip

tree.txt

bam, back to 2.05 :0(

even though i have deleted all contents of firmware and all .bin files in sys
(which is why i then had issues becuase i'd deleted the IAP and had to go and get it out of the main release.

magnets99

@dc42

hmmm actually, now that i think about it.
I started with an empty sd card at version 2.05.1 even if it was grabbing the wrong firmware from sys it should be version 3.
I will try again, but really slowly, deleting all firmwares each time.

magnets99

After clearing the sd card, but before loading the latest firmware
DWC shows 3.5.4
firmware 3.3 and wifi 2.20
which matches m122 output:

=== 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-9T6BU-FG3S8-6J1F4-3SN6K-KULMG
Used output buffers: 3 of 24 (19 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75248 of which 0 recycled
Never used RAM 15292, free system stack 184 words
Tasks: NETWORK(ready,13.9%,231) HEAT(delaying,0.0%,228) Move(notifyWait,0.1%,329) MAIN(running,85.6%,441) IDLE(ready,0.4%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:49 ago, cause: power up
Last software reset at 2024-12-26 14:42, reason: User, GCodes spinning, available RAM 16220, slot 0
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 29.7, current 35.7, max 35.9
Supply voltage: min 24.4, current 24.5, max 24.7, under voltage events: 0, 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 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, 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: 2024-12-26 18:39:21
Cache data hit count 4294967295
Slowest loop: 4.74ms; fastest: 0.17ms
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 5.4ms, 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 idle 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: 12.73ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 2.2.0
WiFi MAC address 80:7d:3a:15:a5:3a
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39048
WiFi IP address 192.168.1.31
WiFi signal strength -58dBm, mode 802.11n, reconnections 0, sleep mode none
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0

then after double checking there is nothing in firmware and only csv, json and g files in sys, i go to DWC and upload system files
with a freshly downloaded 3.5.4

it does a lot of the Uploading file gubbins (x of 78)
it then asks Install updates? and ticks install included wifi Firmware Update.
I click Yes
Please wait while updates are being installed.

conneciton lost...

panel due is showing a green progress percentage message

and we're back!
ok shift+f5 on the web page

oh my, this is looking good
DWC reports, 3.5.4 wifi 2.20 and dwc 3.5.4

M122 shows:

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S8-6J1F4-3SN6K-KULMG
....
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.0

wwwwOOOOOOOOOOOOOOOooo

Ok, so user error!
thank you both.
I think my issue was because i was starting at 2.x something...after i got to 3 i should have been deleting all the firmwares out of sys each time i upgraded.

Thank you both for your help! now to the config.g file!

magnets99

how do i mark this as solved?