RRF 3.5.4 - Hardfault bfarValid precise
-
Another Hardfault. Printer was idle at the time. This one had
Expansionspinning.M122
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF Used output buffers: 13 of 40 (36 max) === RTOS === Static ram: 103496 Dynamic ram: 124564 of which 12 recycled Never used RAM 10824, free system stack 198 words Tasks: NETWORK(2,nWait 7,11.9%,211) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,337) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,798) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,352) TMC(4,delaying,1.5%,101) MAIN(1,running,84.7%,665) IDLE(0,ready,1.1%,29) AIN(4,delaying,0.8%,259), total 100.0% Owned mutexes: === Platform === Last reset 00:00:28 ago, cause: software Last software reset at 2024-12-27 16:42, reason: HardFault bfarValid precise, Expansion spinning, available RAM 9544, slot 0 Software reset code 0x4072 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x0d392e38 SP 0x20011f80 Task NETW Freestk 448 ok Stack: 0d392e30 20033b0f 0000000a 00000001 20033b0f 0009e8e9 000a1478 61010000 2002c438 00000001 20012000 00000113 0009e8e9 2002c438 0002e74f 0d392e30 2002c401 20012050 a5a76ae7 00000000 00000113 2002c658 20031990 2002c670 2001eb00 a5a5a5a5 000305d9 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 21388, completed 21387, timed out 0, errs 0 MCU temperature: min 37.2, current 37.4, max 38.6 Supply voltage: min 24.3, current 24.4, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/300/128, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 105, reads 2532, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 107, reads 2531, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 2534, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 4, read errors 0, write errors 1, ifcnt 109, reads 2531, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 107, reads 2532, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 108, reads 2531, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 2534, writes 10, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2024-12-27 16:43:21 Cache data hit count 53217681 Slowest loop: 8.67ms; fastest: 0.16ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 2.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 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 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 262, received 817, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6034, peak Tx sync delay 6, free buffers 26 (min 25), ts 142/141/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 30.26ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 3 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.2.0 MAC address d8:bf:c0:14:e5:fc Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 39332 WiFi IP address 192.168.2.8 Signal strength -53dBm, channel 1, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
This post is deleted! -
@omtek thanks for your reports, I will look into them.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 I meant to update this post sooner to add that I don't know why it started, but it stopped just as mysteriously as it started; including the two reports above, I captured an additional five M122 reports over a 36-ish hour period. The last one was 29 December, and I haven't encountered the issue since. The printer has been on and active with a browser window open to the printer since then.
The two most recent changes made to the printer before the issue occurred was updating the PanelDue 7.0i firmware to 3.5.1 and replacing the toolboard umbilical cable with the newer style molded power-CAN cable from Mellow Fly. I don't know if that had anything to do with it, but I'd be lying if I didn't consider rolling back both those changes when these resets started occurring.
Collected M122s (the two M122 reports above are included in the attached file):
omtek-RRF3.5.4-Duet3Mini5Plus-HardFault-M122.txtLet me know if I can provide any other information.
~oM
-
@omtek have you changed your browser configuration at all? When I first investigated this issue, whether it occurred or not was related to the size of the HTTP header from the browser, which was affected by the number of languages it was configured to use.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 I built a new computer in the first week of December '24 and started using Microsoft Edge for DWC; prior to that I was using Google Chrome. I use Google Chrome on my S22U phone to access DWC, as well. This installation of Windows 11 Professional is only a few weeks old and was a fresh installation. I haven't installed any additional languages aside from 'English (United States)' in Windows and Edge just shows two instances of English ('English' and 'English (US)') under preferred languages.
-
Adding to this post as I just had another HardFault occur.
-
Printer had recently finished a print without error; printer was idle but bed and tool heaters were pre-soaking for new print
-
Prusaslicer 2.9.0 was in the middle of uploading g-code when the reset occurred.
This is the first HardFault that I have encountered since first posting in this thread.
M122 follows:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF Used output buffers: 3 of 40 (26 max) === RTOS === Static ram: 103496 Dynamic ram: 124556 of which 0 recycled Never used RAM 10844, free system stack 198 words Tasks: NETWORK(2,nWait 7,9.7%,241) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,349) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,798) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,1.5%,101) MAIN(1,running,86.5%,665) IDLE(0,ready,1.3%,29) AIN(4,delaying,0.9%,255), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:22 ago, cause: software Last software reset at 2025-02-22 01:04, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 9328, slot 2 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x3730302e SP 0x20011f70 Task NETW Freestk 444 ok Stack: ffffffff 20033e6c 00000002 00000000 00000000 3730302e 0002e638 01010000 00000000 20011807 000a26a3 004202c0 2002c438 00000000 2002c438 00000001 00000000 00000004 0002e8d5 2002c43c 2002c401 3730302e 85a74255 00000000 0000011c 2002c658 200321a8 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 18027, completed 18027, timed out 0, errs 0 MCU temperature: min 33.9, current 34.4, max 35.4 Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/300/128, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 142, reads 2039, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 143, reads 2038, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 2041, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 142, reads 2038, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 143, reads 2039, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 2, read errors 0, write errors 1, ifcnt 143, reads 2038, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 2041, writes 10, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2025-02-22 01:05:09 Cache data hit count 42967048 Slowest loop: 4.91ms; fastest: 0.16ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 2.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 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 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 214, received 694, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6031, peak Tx sync delay 3, free buffers 26 (min 25), ts 114/113/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 25.43ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.2.1 MAC address d8:bf:c0:14:e5:fc Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 35896 WiFi IP address 192.168.2.8 Signal strength -46dBm, channel 1, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0EDIT: I wanted to add that since the initial HardFault in December and last night, I updated Duet Wifi Server to 2.2.1.
-
-
@omtek thanks for reporting this. Please can you try with 3.6beta4 and see if you still get the hardfault
-
@T3P3Tony I wasn't planning on trying 3.6 until the RC phase as I have a SHT36MAX3 toolboard and a CannedERCF board on the printer and generally have to wait on Team Gloomy for their firmware updates before I can do any updating (and I'm compiling my own firmware for the CannedERCF).
Do you know if there is any way to induce (for lack of a better term) the HardFault? Two months is a long time to go between faults and unlike the series of HardFault restarts that started this post, I haven't encountered another one since last night.
-
@omtek i don't think these is a way to induce that hard fault other than by you being able to reproduce it.
