FW update not working - 2.05 to 3.0 - watchdog?

[sonderzug]

Hi all,

I'm trying to update my E3D Toolchanger's firmware after all, it hasn't been touched since the printer was assembled - never touch a running system - but since I was changing some hardware components around and am also missing some newer firmware features I'd tought I'd give it a go.
I'm already familiar with RRF3.x from other machines and aware of the necessary config changes.

I was following the guide on docs.duet3d.com but the firmware update is stuck pretty soon in the process.
With my first try, having uploaded all bin files from the 3.0 release to the /sys folder, it was giving me the obvious "iap4e.bin missing" error. I renamed the file accordingly and uploaded it separately. Then the update process would start when (re-)uploading firmware files, but never finish - the board will quickly issue a reset and start up again to no avail. Starting the update process manually with M997 S0:2 also results in the same.

I've noticed that the M122 status says "watchdog" as the cause for reset during the update, and I've not been able to find anything on this on the forum. Can anyone give me some pointers?

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet Ethernet 1.02 or later + DueX5
Board ID: 0JD0M-9P6M2-NWNS0-7JKD2-3SS6K-TB1ZJ
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 94372 of which 0 recycled
Exception stack ram used: 600
Never used ram: 10388
Tasks: NETWORK(ready,676) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3736) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:27 ago, cause: watchdog
Last software reset at 2023-07-05 15:57, reason: User, spinning module GCodes, available RAM 10468 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 39.3, current 40.5, max 40.7
Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/1023
Driver 1: standstill, SG min/max 0/1023
Driver 2: standstill, SG min/max 0/241
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max 33/443
Driver 8: standstill, SG min/max 19/1023
Driver 9: standstill, SG min/max 11/1023
Date/time: 2023-07-05 15:58:19
Cache data hit count 44605894
Slowest loop: 1.48ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 156, MaxWait: 502ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 23, completed moves: 23, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 4 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 51.57ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex

Thanks, best regards
Niklas

[droftarts]

@sonderzug Don't just rename the iap file from 3.0; use the version of the iap file that matches your current firmware version. In the case of 2.05.1, it is in the 'Duet2Firmware-2.05.1.zip' file here: https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1

Ian

[dc42]

@sonderzug if you get stuck then the best option if you have a Windows PC handy is to use the Erase jumper on the board and the Bossa program to upload firmware 3.4.5 or 3.4.6-rc.1 directly. You will also need to replace the contents of /www on the SD card with the contents of the corresponding DuetWebConbtrol-SD.zip file.

[sonderzug]

Thank both of you;

@droftarts good call about the iap4e.bin, this fixed my problem.
It seems a bit counterintuitive that to upgrade to 3.0, the iap.bin from 2.05.1 is needed, and the same goes for the update from 3.0 to 3.3 - this might be worth mentioning in the firmware update section in the docs where the different jumps in firmware version are described. It does mention to not just rename a file () but it says that each version comes with the matching file, which seems a bit twisted.

best regards, Niklas