Duet2 wifi stops printing at random stackanalyser points nowhere

sgerevini

Hello everyone,

I am having a bizarre problem with my duet2 wifi.

The printer stops at random points, and there is no useful message on the console, as the printer appears to be rebooted.

Trying to figure out what happened I came to an old post about the same problem and tried the steps shown:

M122 command -> get the software reset error part -> strip the stack line -> run stackanalyser -> get the message that points to the libc.a(lib_a-strnlen.o) -> can't find the libc.a or lib_a-strnlen.s under Symbols(3.4.3).

Now I am stuck without ideas to move forward.

Can someone throw me a light?

old post link:

M122

2024-10-20, 1:12:35 a.m. 	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.3 (2024-09-18 11:25:32) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJ3S0-7JTF0-3SD6K-1VF3G
Used output buffers: 3 of 26 (19 max)
=== RTOS ===
Static ram: 23376
Dynamic ram: 73364 of which 12 recycled
Never used RAM 16724, free system stack 172 words
Tasks: NETWORK(1,ready,17.8%,222) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,81.9%,744) IDLE(0,ready,0.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:10:20 ago, cause: software
Last software reset at 2024-10-20 01:01, reason: StuckInSpinLoop, Gcodes spinning, available RAM 13600, slot 0
Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200023ac Task MAIN Freestk 1035 ok
Stack: 0042a80b 00457e1c 610f0000 3f800000 409f4000 4204469c 3edbc06f 3331bb4c 00000000 20000b80 00000001 00000001 00000014 20004c80 40090000 0042aa8d 00000000 00000000 00008c86 0042b209 49f101c6 20000b80 3f317200 01d4bfff 388ab355 00008c86 20000b4c
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 30.7, current 31.1, max 32.2
Supply voltage: min 24.1, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed

Stackanalyser out:

Faulted at:
.debug_frame
 .debug_frame   0x0000208c       0x20 c:/program files (x86)/gnu arm embedded toolchain/10 2021.10/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc.a(lib_a-strnlen.o)
Error is at offset: 0x3edb9fe3

sgerevini

Only to update:

3.5.0-rc4 don't have this behaviour.

After I downgraded to it, I printed more than 10 hours without a failure.

I think this is something related to the latest version 3.5.3, maybe a bug.

Phaedrux

Have you tried the 3.6 beta release?