Duet3+SBC random restart while printing "AssertionFailed"
-
I've been having random reboos in the printing for a couple of days now.
I'm using Duet3+SBC with RRF3.2 b1.
I also tried to downgrade to 3.1.1 but problem persists.
Publish 3 reports run this morning after rebooingRRF 3.2 b1
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKF0-3S86T-9A5YD Used output buffers: 1 of 40 (21 max) === RTOS === Static ram: 154820 Dynamic ram: 134956 of which 44 recycled Exception stack ram used: 272 Never used ram: 103124 Tasks: HEAT(blocked,303) CanReceiv(blocked,899) CanSender(blocked,372) CanClock(blocked,354) TMC(blocked,52) MAIN(running,1128) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:00:20 ago, cause: software Last software reset at 2020-10-24 08:12, reason: MemoryProtectionFault iaccViol, GCodes spinning, available RAM 102140, slot 2 Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000001 ICSR 0x0440f004 BFAR 0x00000000 SP 0x2045ff48 Task MAIN Stack: 00000000 00000008 4000c000 00000000 00000003 004264db 00000000 400f0027 00000008 20412934 00000000 2045ffbc 20417ee8 fffffff1 20417e9c 20412938 00000001 20417f64 00000003 00466f51 00466f22 210f024a 000003c0 00000004 00000001 20417f68 40078000 Error status: 0x020 MCU temperature: min 23.1, current 23.3, max 23.4 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0 Driver 0: position 0, standstill, reads 33038, writes 20 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 33038, writes 20 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 33042, writes 17 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 33041, writes 18 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 33043, writes 17 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 33043, writes 17 timeouts 0, SG min/max 0/0 Date/time: 2020-10-24 08:13:14 Slowest loop: 5.25ms; fastest: 0.14ms === 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 === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 3 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "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 doing "G4 S30" in state(s) 0 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 0.00ms; fastest: 5726623.00ms Responder states: HTTP sessions: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 95, send timeouts 95, longest wait 1ms for type 6021, free CAN buffers 48 === SBC interface === State: 0, failed transfers: 0 Last transfer: 18ms ago RX/TX seq numbers: 18708/618 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0-beta1+1 Daemon: Buffered code: G4 S30 ; delay running again or next command for at least 60 seconds ==> 32 bytes Executing macro daemon.g, started by system > Next stack level Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 31.32 RRF 3.1.1
122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKF0-3S86T-9A5YD Used output buffers: 1 of 40 (24 max) === RTOS === Static ram: 154604 Dynamic ram: 164252 of which 44 recycled Exception stack ram used: 272 Never used ram: 74044 Tasks: NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3512) CanSender(suspended,1488) CanClock(blocked,1452) TMC(blocked,192) MAIN(running,4488) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:00:35 ago, cause: software Last software reset at 2020-10-24 09:35, reason: Assertion failed, spinning module GCodes, available RAM 72892 bytes (slot 2) Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a80f BFAR 0x00000000 SP 0x2045fe9c Task MAIN Stack: 00000194 00484cd0 00463dbf 00000000 00000000 00000001 2044cff8 2044cfa8 2043f1a8 00000001 2043f120 Error status: 0 MCU temperature: min 25.2, current 25.8, max 26.0 Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0 Driver 0: standstill, reads 41315, writes 19 timeouts 0, SG min/max 0/0 Driver 1: standstill, reads 41315, writes 19 timeouts 0, SG min/max 0/0 Driver 2: standstill, reads 41318, writes 17 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 41317, writes 18 timeouts 0, SG min/max 0/0 Driver 4: standstill, reads 41319, writes 17 timeouts 0, SG min/max 0/0 Driver 5: standstill, reads 41319, writes 17 timeouts 0, SG min/max 0/0 Date/time: 2020-10-24 09:36:26 Slowest loop: 5.83ms; fastest: 0.14ms === 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 === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 3 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "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 doing "G4 S30" in state(s) 0 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 1.29ms; fastest: 0.01ms 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: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 156, longest wait 2ms for type 6018 === Linux interface === State: 0, failed transfers: 1 Last transfer: 21ms ago RX/TX seq numbers: 44842/1122 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Daemon: Buffered code: G4 S30 ; delay running again or next command for at least 60 seconds ==> 32 bytes Executing macro daemon.g, started by system > Next stack level Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 22.78 RRF 3.2 b1
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKF0-3S86T-9A5YD Used output buffers: 1 of 40 (22 max) === RTOS === Static ram: 154820 Dynamic ram: 134956 of which 24 recycled Exception stack ram used: 272 Never used ram: 103144 Tasks: HEAT(blocked,308) CanReceiv(blocked,901) CanSender(blocked,372) CanClock(blocked,356) TMC(blocked,49) MAIN(running,1140) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:00:06 ago, cause: software Last software reset at 2020-10-24 10:47, reason: AssertionFailed, GCodes spinning, available RAM 101936, slot 0 Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a80f BFAR 0x00000000 SP 0x2045fea4 Task MAIN Stack: 00000193 00485260 004666f3 a5a5a5a5 2042f5f4 20412b68 20445e20 20446590 2043f4f0 00000001 2043f468 2043f58c 2043f588 20412934 0046bb15 00000003 004328cf 2043efe8 000d880c 20435b68 000bd098 2043efe8 00000002 20435b68 000bd098 00000000 0000ea60 Error status: 0x020 MCU temperature: min 25.8, current 26.4, max 26.5 Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0 Driver 0: position 0, standstill, reads 29819, writes 19 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 29820, writes 19 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 29822, writes 17 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 29822, writes 18 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 29823, writes 17 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 29823, writes 17 timeouts 0, SG min/max 0/0 Date/time: 2020-10-24 10:48:19 Slowest loop: 5.12ms; fastest: 0.14ms === 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 === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 3 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "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 doing "G4 S5" in state(s) 0 0, running macro Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon* is doing "G4 S30" in state(s) 0 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 0.00ms; fastest: 5726623.00ms Responder states: HTTP sessions: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 38, send timeouts 38, longest wait 2ms for type 6021, free CAN buffers 48 === SBC interface === State: 0, failed transfers: 1 Last transfer: 17ms ago RX/TX seq numbers: 21208/197 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 72/184-0 === Duet Control Server === Duet Control Server v3.2.0-beta1+1 Trigger: Buffered code: G4 S5 Buffered code: M42 P6 S70 Buffered code: M400 ; wait for current moves to finish Buffered code: M18 ==> 112 bytes Executing macro config.g, started by system > Next stack level Daemon: Buffered code: G4 S30 ; delay running again or next command for at least 60 seconds ==> 32 bytes Executing macro daemon.g, started by system > Next stack level Code buffer space: 3912 Configured SPI speed: 8000000 Hz Full transfers per second: 19.92 I didn't change anything to config.g and tried to print old files as well, but the problem still happens.
Every help is welcome.Thanks, Marco
-
Can you include your config.g as well?
-
Hi @Phaedrux, I publish file. I have yet to check but I think it could be a similar issue to this:https://forum.duet3d.com/topic/19346/duet3-6hc-restart-loop-when-connecting-with-web-browser. Yesterday I formatted sd card and I reinstalled everything from scratch but after 20 minutes of printing the sbc disconnected and restarted.
-
@Phaedrux, I managed to do a test without the web page and the problem occurred again. Do you have any ideas about that?
-
Can you try sending M98 P"config.g" and posting the results please?
-
@Phaedrux, i can do it tomorrow evening.
Just out of curiosity is there a guide with listed error code matches? -
-
@Phaedrux, I saw that one, but I can't find the meaning of "AssertionFailed."
Sorry but if possible I would just like to know the meaning of the error since it appeared suddenly -
I've brought it to @DC42's attention, so we'll have to wait for his reply. I've never seen that one either.
-
@Phaedrux , ok, thanks
-
@Marco-Bona, were you using M701 or M702? There's a known issue in 3.2beta that causes assertion failures if you use those commands. It's fixed in the forthcoming 3.2beta3.
-
@dc42, I was using Rrf3.2b1. After formatting sd card I switched to stable firmware version Rrf3.1.1 which gave me the same error. I am not using M701 / M702 commands. Could you please give me a more detailed description regarding the meaning of the error? I can't find any explanation in the documentation.
-
@Phaedrux , I tried to send M98 P"config.g". Everything seems ok
-
An issue has recently been found with the SBC interface that may explain those errors. That issue has now been fixed, so it will be included in 3.2beta3.
-
@dc42, thanks.
When do you think you can release the next update? Is there anything I can do in the meantime to fix the problem? -
@Marco-Bona said in Duet3+SBC random restart while printing "AssertionFailed":
@dc42, thanks.
When do you think you can release the next update? Is there anything I can do in the meantime to fix the problem?Very soon I hope, I'm just waiting for @chrishamm to confirm whether DSF and DWC 3.2 are ready.
-
@dc42, can you confirm that the restart caused by "assertion failed" also occurs with firmware version RRF3.1.1?
I had never had these problems before.
I read in another thread that RRF3.2 b3 will be released next week, is there any solution to fix this problem currently?
Thanks
Marco -
"Assertion failed" means that an internal check on the correct operation of the firmware failed. This usually indicates a firmware bug, but it can also be caused by a hardware fault.
-
@dc42, if it was a hardware error how can i run a diagnostic to correct the error?
I'm not convinced it's a firmware issue. Yesterday I tried to format the sd card and after reinstalling firmware, it worked correctly, instead today the problem occurred. -
@dc42,I'm having another problem, I wanted to test with a newer firmware version, but I can't get the updates with "sudo apt-get update \ sudo apt-get upgrade". Do you have any idea?