[3.6.0-beta.1] installation issues (SOLVED) heads up only.

Mr.Crispin

As per the title

A few days ago, I decided to try out the new firmware.

I have a 6hc board with a LC1 Tool board, (standalone) I attempted to update to 3.6.0-beta from within DWC.

The system said it was updating and then at the normal reconnect after the update it wouldn't reconnect...

I tried cycling power a few times and Nada.

Upon connecting the board to my pc via USB the port listed itself as a "bossa" post instead of a USB device, I'm like W.T.F.

So i tried to re-flash via bossa flash tool x3 attempts all failed with no actual listed error. I redownloaded the .bin file from the repository in case it was a corrupted download. This didn't cure the issue.

I was able to successfully flash back to 3.5.3 no problem and that allowed me back into the printer via DWC, a second attempt to update via DWC resulted in the same issue.

After x3 attempts (and trying different USB cables which made no difference) via bossa I finally managed to get 3.6.0-beta.1 to upload and verify successfully. And I was able to upgrade the tool board from within DWC, no problem.

M122 attached

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.6.0-beta.1 (2024-09-24 10:07:51) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Used output buffers: 1 of 40 (29 max)
=== RTOS ===
Static ram: 136444
Dynamic ram: 126712 of which 444 recycled
Never used RAM 67952, free system stack 200 words
Tasks: NETWORK(1,ready,32.9%,180) ETHERNET(5,nWait 7,0.1%,324) HEAT(3,nWait 6,0.0%,356) Move(4,nWait 6,0.0%,333) TMC(4,nWait 6,3.1%,379) CanReceiv(6,nWait 1,0.0%,794) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,353) MAIN(1,running,63.5%,103) IDLE(0,ready,0.4%,29) USBD(3,blocked,0.0%,147), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:28 ago, cause: power up
Last software reset at 2024-10-09 20:46, reason: HardFault, none spinning, available RAM 67952, slot 1
Software reset code 0x0073 HFSR 0x80000000 CFSR 0x00000000 ICSR 0x00400803 BFAR 0x00000000 SP 0x2041b740 Task NETW Freestk 532 ok
Stack: 00000001 00000000 20415d9c 00000035 0000023c 0041dde9 00421794 61010000 2041aa80 004ba638 00000009 0000000a 0000000b 0000000c 0000000b 0003000c 00000000 2041aa80 20415e08 00000000 20415c44 e000e000 a5a5a5a5 a5a5a5a5 a5a5a5a5 0041e8fb 002dfff0
Error status: 0x00
MCU temperature: min 23.4, current 32.7, max 32.7
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, 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
Events: 0 queued, 0 completed
Date/time: 2024-10-10 11:56:08
Slowest loop: 2.60ms; fastest: 0.07ms
USB interrupts 2
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.5ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
no step interrupt scheduled
Driver 0: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 1: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 2: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 3: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 56463, writes 11 timeouts 0
Driver 5: standstill, SG min n/a, mspos 4, reads 56456, writes 18 timeouts 0
Phase step loop runtime (us): min=0, max=73, frequency (Hz): min=1633, max=2568
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering erHeater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x80000003
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 272, received 581, lost 0, ignored 0, errs 581, boc 0
Longest wait 1ms for reply type 6042, peak Tx sync delay 27193, free buffers 50 (min 49), ts 143/142/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 4.99ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 1 0 0
Socket states: 2 6 2 2 2 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

Kiolia

@Mr-Crispin I have a 6HC with 3HC toolboard, standalone mode. I have had almost the same exact experience twice, once when going from 3.4.x to 3.5.1 and once when going from 3.6.0-alpha5+1 to 3.6.0-beta.1. Somehow I was able to avoid it when going from 3.5.1 to the 3.6.0-alpha. I believe it helped to have my CANBoard unplugged when I updated the mainboard, but I will have to verify this next time I update.

The first time it happened, I had attempted to update mainboard and toolboard together; the second time it happened, I had tried to update the mainboard by itself, but still had the CANBoard plugged in. Both times were terrifying and made me think I'd bricked my 6HC.

As supplemental info, I got this message both times this happened to me, but it never appeared in the console log:

After this, the printer posted no further updates for 15-20 minutes, whereupon I restarted it, and from there the PanelDue would show the usual control screen, except with 0's in all values (as if it had not loaded config.g), and was completely nonresponsive on the console as well as inaccessible via DWC. I had to go through Bossa to reflash in both cases.

droftarts

@Kiolia @Mr-Crispin Thanks for reporting this. It looks like it may have got stuck trying to update the CAN board, but I don't know why. Can you check what bootloader version is installed on your expansion boards, by sending M122 B#, where # is the CAN address of the expansion board?

Otherwise, may be one for @chrishamm to investigate.

Ian

Kiolia

@droftarts My M122 B1:

M122 B1
Diagnostics for board 1:
Duet EXP3HC rev 1.02 or later firmware version 3.6.0-beta.1 (2024-09-24 08:51:17)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 170244, free system stack 202 words
Tasks: Move(3,nWait 7,0.0%,181) TMC(2,nWait 6,7.0%,95) HEAT(2,nWait 6,0.0%,133) CanAsync(5,nWait 4,0.0%,66) CanRecv(3,nWait 1,0.0%,79) CanClock(5,nWait 1,0.0%,69) MAIN(1,running,91.8%,322) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.1%,264), total 100.0%
Owned mutexes:
Last reset 00:00:27 ago, cause: power up
Last software reset data not available
Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00
Peak sync jitter -4/3, peak Rx sync delay 180, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 4273967492 ticks, disabled
VIN voltage: min 48.4, current 48.5, max 48.5
V12 voltage: min 12.4, current 12.4, max 12.5
MCU temperature: min 21.6C, current 24.0C, max 24.0C
Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 42950, writes 11 timeouts 0
Driver 1: pos 0, 551.0 steps/mm, standstill, SG min 0, mspos 4, reads 42945, writes 16 timeouts 0
Driver 2: pos 0, 551.0 steps/mm, standstill, SG min 0, mspos 4, reads 42946, writes 16 timeouts 0
Last sensors broadcast 0x00003018 found 4 9 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 446, send timeouts 0, received 255, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

and M122:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.6.0-beta.1 (2024-09-24 10:07:51) running on Duet 3 MB6HC v1.02 or 1.02a (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6J1F8-3SN6S-9VHBB
Used output buffers: 3 of 40 (36 max)
=== RTOS ===
Static ram: 136444
Dynamic ram: 121388 of which 396 recycled
Never used RAM 70468, free system stack 194 words
Tasks: NETWORK(2,nWait 7,24.3%,225) ETHERNET(5,nWait 7,0.0%,661) HEAT(3,nWait 6,0.0%,361) Move(4,nWait 6,0.0%,333) TMC(4,nWait 6,3.0%,386) CanReceiv(6,nWait 1,0.0%,794) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,353) MAIN(1,running,72.4%,440) IDLE(0,ready,0.2%,29) USBD(3,blocked,0.0%,142), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:39 ago, cause: power up
Last software reset at 2024-10-06 13:14, reason: User, Gcodes spinning, available RAM 70468, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 11.7, current 24.5, max 24.7
Supply voltage: min 48.2, current 48.3, max 48.5, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.3, max 12.8, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/16/0, gc cycles 0
Events: 0 queued, 0 completed
Date/time: 2024-10-15 07:36:02
Slowest loop: 22.41ms; fastest: 0.07ms
USB interrupts 3
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.8ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 252749.00/252749/0.00 252749.00/252749/0.00 252749.00/252749/0.00
next step interrupt due in 256 ticks, disabled
Driver 0: standstill, SG min n/a, mspos 4, reads 2735, writes 18 timeouts 0
Driver 1: standstill, SG min n/a, mspos 4, reads 2735, writes 18 timeouts 0
Driver 2: standstill, SG min n/a, mspos 4, reads 2735, writes 18 timeouts 0
Driver 3: standstill, SG min n/a, mspos 4, reads 2735, writes 18 timeouts 0
Driver 4: standstill, SG min n/a, mspos 4, reads 2735, writes 18 timeouts 0
Driver 5: standstill, SG min n/a, mspos 4, reads 2735, writes 18 timeouts 0
Phase step loop runtime (us): min=0, max=5, frequency (Hz): min=1973, max=2027
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering er=== GCodes ===
Movement locks held by null, 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
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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 904, received 1604, lost 0, ignored 0, errs 0, boc 0
Longest wait 3ms for reply type 6024, peak Tx sync delay 4, free buffers 50 (min 49), ts 500/499/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 26.17ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: establishingLink
Error counts: 0 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0 0
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 70:04:1d:be:ad:dc
Module reset reason: Power up, Vcc 0.00, flash size 16777216, free heap 223308
WiFi IP address 192.168.1.206
Signal strength -44dBm, channel 3, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

droftarts

@Kiolia said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)

It has got an older bootloader version on it (see https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_bootloader to update it), but I'm not sure if that's what caused the updated issue. Maybe update it and try and update, when you're feeling brave?!

EDIT: not much has changed with the bootloader over time, and 2.4 isn't that old, so I doubt it will make a difference.

Ian

Kiolia

@droftarts I can try updating the bootloader for the beta.2 release and see how it goes, but I don't see anything in the git release history to indicate changes related to update behavior or support for 3HC boards of my version ...
EDIT, saw your edit, haha. I will stick with unplugging the CANBoard for now.

BTW: I thought I saw other messages on the first incident, but I can't recall specifics. However, I remember them giving me a gut feeling this might be related to the CANBoard not restarting upon command?

Kiolia

@droftarts I walked away and remembered more about the additional error messages I saw the first time. At the time, I had the hot end and thermistor on the toolboard, and at least one message flashed about the heater being not detected (or disconnected or not found, something like that).

Mr.Crispin

Here is the output from my tool board.

But I dont think its going to be of any help as mine is listing : Bootloader ID: not available.

And i admit i have a little bit of hesitance to update the bootloader on an older toolboard, as i tried that a year or so ago on another v1.0 board which bricked it.

luckily duet3d granted a goodwill replacement on that board, but i dont want to push my luck

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.0 or earlier firmware version 3.6.0-beta.1 (2024-09-24 08:53:50)
Bootloader ID: not available
All averaging filters OK
Never used RAM 9264, free system stack 104 words
Tasks: Move(3,nWait 7,0.0%,140) TMC(2,delaying,3.6%,52) HEAT(2,nWait 6,0.3%,104) CanAsync(5,nWait 4,0.0%,48) CanRecv(3,nWait 1,0.0%,70) CanClock(5,nWait 1,0.0%,58) MAIN(1,running,91.3%,318) IDLE(0,ready,0.0%,40) AIN(2,delaying,4.7%,112), total 100.0%
Owned mutexes:
Last reset 00:28:34 ago, cause: software
Last software reset data not available
Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00
Peak sync jitter 4/9, peak Rx sync delay 216, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 3008825729 ticks, disabled
VIN voltage: min 22.9, current 23.4, max 24.0
MCU temperature: min 49.7C, current 55.5C, max 67.6C
Driver 0: pos 0, 395.0 steps/mm, standstill, SG min 2, read errors 0, write errors 1, ifcnt 28, reads 5439, writes 12, timeouts 0, DMA errors 0, CC errors 0
Last sensors broadcast 0x00000002 found 1 112 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 34425, send timeouts 0, received 15494, lost 0, ignored 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: none
I2C bus errors 4639, naks 4639, contentions 4639, other errors 4639

droftarts

@Mr-Crispin said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

Bootloader ID: not available

That definitely means it's on an old version of the bootloader, so worth updating.

And i admit i have a little bit of hesitance to update the bootloader on an older toolboard, as i tried that a year or so ago on another v1.0 board which bricked it.

I wonder if this, and the updating malfunctioning, are indicative of something else? Possibly CAN wiring, or CAN termination problems?

Ian

Mr.Crispin

@droftarts said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

@Mr-Crispin said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

Bootloader ID: not available

That definitely means it's on an old version of the bootloader, so worth updating.

And i admit i have a little bit of hesitance to update the bootloader on an older toolboard, as i tried that a year or so ago on another v1.0 board which bricked it.

I wonder if this, and the updating malfunctioning, are indicative of something else? Possibly CAN wiring, or CAN termination problems?

Ian

The bricking occurred on my other machine. And it has been updated with no issues (although not to 3.6 yet)

I dislike RJ11 connectors, I removed them on both of my 6hc boards and added JST-XH connectors with twisted pair silicone wire.

My day job is as a network installation engineer, including fibre optics, so im happy enough with my connections.