Duet 2 Wifi Random crashes



  • Hello everyone,

    I have recently completed wiring up my Duet 2 Wifi, and gotten quite a few test prints done, without issues. One of the first things I did was to upgrade the firmware to the latest version.

    I haven't done any other changes, but now I'm starting to get random "crashes" during prints. It's happened 4-5 times or so, and just now it happened two times a few minutes into the print. It's not stopping at the same point of the print, and I was also able to reprint using the same Gcode that caused an earlier crash, so it doesn't seem to be anything related to bad Gcode or something of the sort.

    This is M122 after the latest crash. I also ran M122 after all the other crashes, and they have so far all had the same software reset reason and code.

    Any idea what might cause it?

    Thanks so much for your help! much appreciated.

    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.0 running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9T6BU-FG3S4-6JTDJ-3SN6P-1SNZG
    Used output buffers: 3 of 24 (11 max)
    === RTOS ===
    Static ram: 28180
    Dynamic ram: 92776 of which 64 recycled
    Exception stack ram used: 264
    Never used ram: 9788
    Tasks: NETWORK(ready,36) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:01:41 ago, cause: software
    Last software reset at 2020-05-29 17:05, reason: Stack overflow, spinning module none, available RAM 9408 bytes (slot 1)
    Software reset code 0x4111 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80e BFAR 0xe000ed38 SP 0x2001ffb4 Task NETW
    Stack: 20002860 20002894 00455625 00000000 00000017 200029b8 20002a55 0000000a 00454c35 200028c4 200055f4
    Error status: 0
    MCU temperature: min 37.6, current 38.3, max 38.4
    Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-05-29 17:07:08
    Cache data hit count 170043159
    Slowest loop: 3.99ms; fastest: 0.13ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest read time 0.9ms, write time 0.0ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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, chamberHeaters = -1 -1 -1 -1
    === 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
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 15.83ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is active
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23
      WiFi MAC address b4:e6:2d:5f:bc:8c
      WiFi Vcc 3.34, reset reason Unknown
      WiFi flash size 4194304, free heap 25752
      WiFi IP address 192.168.99.103
      WiFi signal strength -54dBm, reconnections 0, sleep mode modem
      Socket states: 0 0 0 0 0 0 0 0


  • I believe the 3.1.1 update fixes this issue - there are a few other forums posts that led to the 3.1.1 release. I had this happen once while on 3.1.0, upgraded to 3.1.1 and so far have not had any further issues.

    "Stack overflow, spinning module none, available RAM 9408 bytes (slot 1)
    Software reset code 0x4111 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80e BFAR 0xe000ed38 SP 0x2001ffb4 Task NETW
    Stack: 20002860 20002894 00455625 00000000 00000017 200029b8 20002a55 0000000a 00454c35 200028c4 200055f4"

    Believe these are the tells that are solved with 3.1.1



  • Ahh good to hear, I will try upgrading to 3.1.1.
    I guess a stack overflow does indicate some sort of software related issue.


Log in to reply