Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    SPI reset issue after upgrading Duet firmware

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    3
    197
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • alextundefined
      alext
      last edited by

      Hi,
      Is anyone able to take a look at the below and suggest why I'm getting the SPI reset issues? It seems to have started after I updated the Duet firmware, although that may be cooincidiental. It's happen twice now over an hour into two big prints and it's causing me a big headache, as well as wasted time and materials. The print just stops with status completed which is completely wrong. I have change the PSU for the SBC just in case there was a brown out issue but that didn't solve it.

      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (SBC mode)
      Board ID: 08DJM-956L2-G43S4-6J9D8-3S86J-9B56F
      Used output buffers: 1 of 40 (40 max)
      === RTOS ===
      Static ram: 153252
      Dynamic ram: 68568 of which 0 recycled
      Never used RAM 128468, free system stack 130 words
      Tasks: SBC(ready,0.7%,448) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.4%,214) CanReceiv(notifyWait,0.0%,771) CanSender(notifyWait,0.0%,334) CanClock(delaying,0.0%,347) TMC(notifyWait,7.9%,56) MAIN(running,91.0%,1044) IDLE(ready,0.0%,30), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 01:20:10 ago, cause: power up
      Last software reset at 2023-12-05 16:11, reason: AssertionFailed, GCodes spinning, available RAM 128660, slot 2
      Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x2041b50c Task MAIN Freestk 1675 ok
      Stack: 20419a84 00000000 0048a667 00460bbe 2042c230 20419a84 2042c294 00000000 00000001 00000000 00489257 2042c294 00000000 00000000 0048958f 2042c120 00000000 2042a558 2042c290 9f3ba088 2042c294 20419a84 00000000 9f3ba088 a5a5a5a5 a5a5a5a5 004896bb
      Error status: 0x04
      Aux0 errors 0,1,0
      Step timer max interval 137
      MCU temperature: min 13.5, current 30.5, max 33.4
      Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.1, current 12.2, 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 664, reads 39429, writes 26 timeouts 0
      Driver 1: standstill, SG min 0, mspos 536, reads 39431, writes 24 timeouts 0
      Driver 2: standstill, SG min 0, mspos 856, reads 39429, writes 26 timeouts 0
      Driver 3: standstill, SG min 0, mspos 360, reads 39429, writes 26 timeouts 0
      Driver 4: standstill, SG min 0, mspos 504, reads 39431, writes 24 timeouts 0
      Driver 5: standstill, SG min 0, mspos 600, reads 39431, writes 24 timeouts 0
      Date/time: 2023-12-08 16:16:08
      Slowest loop: 61.86ms; fastest: 0.04ms
      === 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 ===
      DMs created 125, segments created 16, maxWait 626999ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 5864, completed 5864, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], 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 doing "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 idle in state(s) 0
      Aux2 is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty
      === CAN ===
      Messages queued 48987, received 96229, lost 0, boc 0
      Longest wait 2ms for reply type 6023, peak Tx sync delay 383, free buffers 50 (min 48), ts 24055/24054/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      Transfer state: 5, failed transfers: 4, checksum errors: 0
      RX/TX seq numbers: 24073/24073
      SPI underruns 4, overruns 4
      State: 5, disconnects: 4, timeouts: 4 total, 4 by SBC, IAP RAM available 0x2ab5c
      Buffer RX/TX: 0/0-0, open files: 0
      === Duet Control Server ===
      Duet Control Server v3.4.6
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
      Full transfers per second: 6.80, max time between full transfers: 53.9ms, max pin wait times: 31.7ms/2.2ms
      Codes per second: 0.00
      Maximum length of RX/TX data transfers: 3575/64

      I'm also getting other errors in the logs.......

      08/12/2023, 16:06:07 Connection established
      08/12/2023, 16:05:45 Connection interrupted, attempting to reconnect...
      Network error
      08/12/2023, 16:02:11 Warning: SPI connection has been reset
      08/12/2023, 16:02:11 Connection to Duet established
      08/12/2023, 16:02:11 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
      08/12/2023, 16:00:35 Connection established
      08/12/2023, 15:31:10 Connection interrupted, attempting to reconnect...
      Network error

      Thanks in advance.

      chrishammundefined 1 Reply Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators @alext
        last edited by

        @alext Your SBC caused timeouts and that is typically a symptom of a very slow or a failing microSD card. It can also be caused by third-party applications attempting to perform too many concurrent IO requests. I suggest you replace that with an A1- or A2-rated card and check if the problem persists.

        Duet software engineer

        IndeX4Dundefined 1 Reply Last reply Reply Quote 0
        • IndeX4Dundefined
          IndeX4D @chrishamm
          last edited by

          @chrishamm did it work?

          1 Reply Last reply Reply Quote 0
          • droftartsundefined droftarts referenced this topic
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA