[3.4.1-rc2] update fail

jay_s_uk

@supertb1 no need to delete the contents of the SD card. Just use fallback 2 which I think is erase and bossa

supertb1

@jay_s_uk Ok rolled back to RC1, I think I will wait till you guys get 3.4.2 up before I do that again, lol big ole pain in the butt to reach down into my enclosure with a tweezers trying to land that jumper, I think my next enclosure design is going to have an external jumper point.

supertb1

@jay_s_uk ! 3.4.1 fail.jpg @T3P3Tony @Phaedrux
This is the second time this new board has done this with the latest update. I used the DWC to install Duet2and3Firmware-3.4.1.zip in my older unit and it worked fine. when I uploaded the same file using DWC in on my newer board it bricked the main board. I purchased the Duet 3 6HC on April 1 2022 from filastruder. What information can I give you to help troubleshoot this problem.
I am able to flash the board using BOSSA with the new Duet3Firmware_MB6HC.bin and that worked fine.
3.4.1 fail.jpg

Phaedrux

Can you please provide the results of sending M122 and M122 B# in the gcode console where # is the canbus address of your expansion boards?

supertb1

@phaedrux
6/5/2022, 10:04:17 PM M122 B51.0
Diagnostics for board 51:
Duet EXP1HCL firmware version 3.4.1 (2022-06-01 21:14:32)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52288, free system stack 194 words
Tasks: Move(notifyWait,0.0%,152) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,72) TMC(notifyWait,34.5%,360) CLSend(notifyWait,0.0%,152) MAIN(running,63.7%,409) IDLE(ready,0.0%,30) AIN(notifyWait,1.8%,265), total 100.0%
Last reset 00:02:14 ago, cause: power up
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 5.00, error threshold: 10.00, encoder type rotaryQuadrature, reverse polarity: no, position 1, raw count = 0, tuning mode: 0, tuning error: 0x1, collecting data: no
Control loop runtime (ms): min=0.003, max=0.011, frequency (Hz): min=10870, max=17442
Driver 0: pos 0, 81.7 steps/mm,not tuned, SG min 0, mspos 8, reads 27185, writes 23 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -4/4, peak Rx sync delay 186, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.3, current 24.3, max 24.4
V12 voltage: min 12.2, current 12.2, max 12.2
MCU temperature: min 23.8C, current 26.8C, max 26.8C
Last sensors broadcast 0x00000000 found 0 44 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1109, send timeouts 0, received 1220, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
6/5/2022, 10:04:10 PM M122 B50.0
Diagnostics for board 50:
Duet EXP1HCL firmware version 3.4.1 (2022-06-01 21:14:32)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52288, free system stack 200 words
Tasks: Move(notifyWait,0.0%,152) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,72) TMC(notifyWait,34.5%,360) CLSend(notifyWait,0.0%,152) MAIN(running,63.7%,409) IDLE(ready,0.0%,30) AIN(notifyWait,1.8%,265), total 100.0%
Last reset 00:02:08 ago, cause: power up
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 5.00, error threshold: 10.00, encoder type rotaryQuadrature, reverse polarity: no, position 1, raw count = 0, tuning mode: 0, tuning error: 0x1, collecting data: no
Control loop runtime (ms): min=0.003, max=0.011, frequency (Hz): min=11538, max=17442
Driver 0: pos 0, 80.5 steps/mm,not tuned, SG min 0, mspos 8, reads 58946, writes 23 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -6/7, peak Rx sync delay 188, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.3, current 24.3, max 24.4
V12 voltage: min 12.1, current 12.1, max 12.1
MCU temperature: min 24.4C, current 26.4C, max 26.7C
Last sensors broadcast 0x00000000 found 0 198 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1059, send timeouts 0, received 1165, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
6/5/2022, 10:04:01 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J9F2-3SD6J-9B9AT
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 96272 of which 0 recycled
Never used RAM 103400, free system stack 200 words
Tasks: NETWORK(ready,25.1%,251) ETHERNET(notifyWait,0.0%,173) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,92) MAIN(running,66.8%,1101) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:58 ago, cause: power up
Last software reset at 2022-06-05 16:14, reason: User, GCodes spinning, available RAM 103400, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 126
MCU temperature: min 21.3, current 33.0, max 33.0
Supply voltage: min 24.2, current 24.2, max 24.3, 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
Driver 0: standstill, SG min 0, mspos 8, reads 5515, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 5519, writes 11 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 5519, writes 11 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 5519, writes 11 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 5516, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 5519, writes 11 timeouts 0
Date/time: 2022-06-05 22:04:00
Slowest loop: 2.61ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.6ms, 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 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
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
=== Filament sensors ===
Extruder 0 sensor: no data received
=== CAN ===
Messages queued 1080, received 1914, lost 0, boc 0
Longest wait 6ms for reply type 6018, peak Tx sync delay 6, free buffers 50 (min 49), ts 594/593/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 4.56ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8

Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

Phaedrux

So it looks like you're all up to date on 3.4.1 now. Assuming that's only after updating with bossa.

Can you upload the zip file again now? Does it still produce an error? Is the only place you see the error on the PanelDue? What firmware version is the PanelDue?

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

dc42

@supertb1 FWIW that error "Operation 3 failed after 5 retries" comes from the IAP when it tries to update the firmware. It means that an operation to write a block of firmware to flash memory failed. My guess is that the prior Erase operation didn't fully erase the flash memory. You fixed that with the Ease jumper and Bossa.

The only suggestion I have is that you check that you have the latest version of the IAP file for the MB6HC in the /firmware folder on the SD card.

If this issue comes up more often, I will modify the IAP to restart the whole process form scratch the first time an irrecoverable error like this happens.

supertb1

@dc42 in what release was the last "in app programmer" published?
How do I check what version IAP I have?

supertb1

@phaedrux I updated the paneldue7i to the latest version and then ran the Duet2and3Firmware-3.4.1.zip again, it worked fine this time.

dc42

@supertb1 said in [3.4.1-rc2] update fail:

@dc42 in what release was the last "in app programmer" published?

In release 3.4.1, however I don;t think there were any changes between 3.4.0 and 3.4.1. If you uploaded the 3.4.1 zip file then you should already have the latest version.

How do I check what version IAP I have?

It can only be checked by date and file size at present.

supertb1

@dc42 so it is in the .ZIP file, I'm not sure what is going on with this new board, it has been giving me issues since RC1. It always comes up with error: "Operation 3 failed after 5 retries". while my 2 year old board has never given me any troubles.

supertb1

@dc42 Is there a way to install the IAP separate from the .zip file for issues like this?

dc42

@supertb1 yes, just upload it the same way that you upload a firmware binary, and it will appear in the /firmware folder.

supertb1

@dc42 so you unzip the file and upload the DuetAPI.xml?

Phaedrux

@supertb1 said in [3.4.1-rc2] update fail:

@dc42 so you unzip the file and upload the DuetAPI.xml?

No. The zip file should be uploaded intact. Do not unzip it first unless you want to upload a single specific file.

supertb1

@dc42
I tried to update to the latest firmware and it did the same thing listed below. Is there a way to make it not do that? or would it be advisable to not update this particular board?

***FWIW that error "Operation 3 failed after 5 retries" comes from the IAP when it tries to update the firmware. It means that an operation to write a block of firmware to flash memory failed. My guess is that the prior Erase operation didn't fully erase the flash memory. You fixed that with the Ease jumper and Bossa.

The only suggestion I have is that you check that you have the latest version of the IAP file for the MB6HC in the /firmware folder on the SD card.

If this issue comes up more often, I will modify the IAP to restart the whole process form scratch the first time an irrecoverable error like this happens.******

Phaedrux

What was the update method used this time?

supertb1

@phaedrux I tried to upload the update zip file to the web interface, and it failed the third step just like it did before, I used the second fall back process and now am in the process to getting back on the web interface to install the tool board firmware updates manually. this being as big a head ache as this board has been on firmware updates I am trying to figure out if there are any reasons why I should update it in the future or if I should just wait until like update 4.0 before I reset the board and use bossa again. Any thoughts... Is there something that I should be doing outside the norm with this particular board?

Phaedrux

When and where did you purchase this Duet?

supertb1

@Phaedrux I purchased the Duet 3 6HC on April 1 2022 from filastruder. Board ID: 08DJM-956BA-NA3TJ-6J9F2-3SD6J-9B9AT
Invoice c30699537694791.1. Is there a way to confirm that this board is actually a Duet3D manufactured board? I would be very interested to find out if this board was a knock off or if somehow there was some kind of defect/ different design/explanation for why this board does not behave like the other duet board I have.