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

    DWC report different firmware version than apt package manager

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    2
    3
    132
    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.
    • DonEsteundefined
      DonEste
      last edited by

      Hi, I currently have a Duet 3 mini 5+ alongside a Raspberry Pi 3b + and for some time now I have been receiving the following message when turning on my printer: "Warning: Incompatible firmware, please upgrade as soon as possible". Of course I tried to update the firmware using the package manager on the Raspberry, but it tells me that I have installed the latest firmware (3.3.0) being that DWC reports that I am using version 3.2.2.

      This is what I get when running an M112:

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus Ethernet (SBC mode)
      Board ID: LUR9T-W096U-D65J0-40KMS-1803Z-7MXNN
      Used output buffers: 1 of 40 (11 max)
      === RTOS ===
      Static ram: 98732
      Dynamic ram: 94468 of which 44 recycled
      Never used RAM 51972, free system stack 200 words
      Tasks: Linux(blocked,105) HEAT(blocked,315) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,106) MAIN(running,519) IDLE(ready,20) AIN(blocked,269)
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:16:07 ago, cause: power up
      Last software reset at 2021-08-01 22:22, reason: User, GCodes spinning, available RAM 51972, slot 0
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00430000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Aux1 errors 0,0,0
      Supply voltage: min 0.0, current 23.2, max 23.3, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 62381, writes 11, timeouts 0, DMA errors 0
      Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 13, reads 62379, writes 13, timeouts 0, DMA errors 0
      Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 13, reads 62378, writes 13, timeouts 0, DMA errors 0
      Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 13, reads 62378, writes 13, timeouts 0, DMA errors 0
      Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 13, reads 62379, writes 13, timeouts 0, DMA errors 0
      Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 13, reads 62379, writes 13, timeouts 0, DMA errors 0
      Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 13, reads 62378, writes 13, timeouts 0, DMA errors 0
      Date/time: 2021-08-02 19:23:11
      Cache data hit count 2299187756
      Slowest loop: 1.23ms; fastest: 0.08ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 0.0MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters = 0 -1, chamberHeaters = -1 -1
      Heater 1 is on, I-accum = 0.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 8696, send timeouts 8694, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
      === SBC interface ===
      State: 4, failed transfers: 1
      Last transfer: 4ms ago
      RX/TX seq numbers: 33930/33930
      SPI underruns 0, overruns 0
      Number of disconnects: 0, IAP RAM available 0x113e0
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.3.0
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz
      Full transfers per second: 35.11, max wait times: 14.8ms/0.0ms
      Codes per second: 0.07
      Maximum length of RX/TX data transfers: 3424/984
      

      And this is what I get when trying to update via apt:

      sudo apt-get upgrade duetsoftwareframework
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      duetsoftwareframework is already the newest version (3.3.0).
      Calculating upgrade... Done
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      

      It is nothing that prevents me from printing, in fact I have been with this problem for about a month, but I would like to solve it ... I hope you can help me 🙂

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Try using this method to get the firmware back in sync

        https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Duet_3_Mini_5_WiFi_Ethernet

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 1
        • DonEsteundefined
          DonEste
          last edited by

          Thank you very much, that fixed my problem.

          Thanks again 🙂

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