Solved Beta 3.4 Toolboard 1.1 firmware update failed

[Pakue]

I ran into an issue updating a V1.1 toolboard to the latest beta release (3.4.0 beta 3). When uploading the .bin via the system page in DWC and updating via the prompt, the "Please wait while updates are being installed..." was stuck for >10min. The correct CAN address was selected (20) according to the command popup in the corner.

After resetting both boards the toolboard isn't reachable on neither addr 20 or 121.

Let me know if you need any infos.

Hardware:

• Duet 3 MB6HC v1.01 (3.4.0beta3) in SBC mode
• Toolboard V1.1 (before upgrade, 3.3beta3 as shipped)

M122:

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta3 (2021-08-24 13:57:45) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9F6-3SD6M-TB96T
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 151160
Dynamic ram: 62160 of which 792 recycled
Never used RAM 136560, free system stack 202 words
Tasks: SBC(resourceWait:,0.5%,296) HEAT(notifyWait,0.0%,320) Move(notifyWait,0.0%,300) CanReceiv(notifyWait,0.0%,693) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.1%,93) MAIN(running,88.2%,922) IDLE(ready,4.1%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:06:33 ago, cause: power up
Last software reset at 2021-09-13 12:07, reason: User, GCodes spinning, available RAM 135908, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 132
MCU temperature: min 48.5, current 53.8, max 55.0
Supply voltage: min 23.7, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 54714, writes 11 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 54708, writes 18 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 54708, writes 18 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 54712, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 54712, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 54712, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-09-15 09:43:01
Slowest loop: 999.64ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 6517, received 158, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 59433, free buffers 49 (min 48), ts 1970/1616/0
Tx timeouts 0,0,178,2,0,60 last cancelled message type 30 dest 127
=== SBC interface ===
State: 4, failed transfers: 1, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 14852/14852
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c460
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4-b3
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 9.58, max wait times: 1730.4ms/29.2ms
Codes per second: 0.05
Maximum length of RX/TX data transfers: 3112/1284

[dc42]

@pakue please try a factory reset of the tool board, by holding both buttons down while you turn on the power. After the blue VIN and red 5V LEDs on the tool board are lit, you can release the buttons. The tool board should attempt to download firmware from the main board. If it fails, the STATUS LED should flash one or more error codes.

[Pakue]

@dc42 Sorry, I forgot to add that to the post. Yes I tried that without success. The error code of the LEDs is:

long red, two short red. Afterwards the green LED flashes briefly, not sure if that is part of the error code.

[dc42]

@pakue please count the red flashes again, because 2 long/2 short doesn't make sense.

The green LED flashing normally means the board is asking the main board for firmware.

[Pakue]

@dc42 Here a video clip of the reset:
https://imgur.com/a/VPZSQgG

[dc42]

@pakue what does it do after the green flash?

[Pakue]

@dc42 No further flashes.

[Pakue]

@dc42 Is there serial output on some test points that would help in debugging?

[dc42]

@pakue I think we had better replace your tool board. Please email warranty@duet3d.com with a link to this thread.

Which country are you in?

[Pakue]

@dc42 Ok, I'll send an email with my infos.
I'm located in Germany.

[Pakue]

@dc42 I received the replacement board. Thank you for the quick help!
I'm guessing I'll wait with the firmware update until you had a change to look over the defect board?