incompatible firmware v on duet3?



  • Hi, im trying to setup my new duet 3 board.

    after configuring the config.g at the website I uploaded it to my duet, but it gives me a wrong firmware warning -

    Can anyone tell me what to do? I have updated the RPI with get upgrade/update and downloaded the latest firmware

    this is the M122

    RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0beta12 running on Duet 3 MB6HC
    Board ID: 08DJM-956L2-G43S8-6J9D6-3SN6M-KU0UG
    Used output buffers: 1 of 32 (9 max)
    === RTOS ===
    Static ram: 122240
    Dynamic ram: 172336 of which 40 recycled
    Exception stack ram used: 216
    Never used ram: 98384
    Tasks: NETWORK(ready,2044) HEAT(blocked,1208) CanReceiv(suspended,3804) CanSender(suspended,1480) CanClock(blocked,1428) TMC(blocked,216) MAIN(running,4212) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:48 ago, cause: software
    Last software reset at 2020-10-16 13:09, reason: Unknown, spinning module Platform, available RAM 98320 bytes (slot 2)
    Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 not detected, interface speed: 37.5MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 42.5, current 42.9, max 43.0
    Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.0, current 12.0, max 12.0, under voltage events: 0
    Driver 0: standstill, reads 21489, writes 14 timeouts 0, SG min/max 0/0
    Driver 1: standstill, reads 21489, writes 14 timeouts 0, SG min/max 0/0
    Driver 2: standstill, reads 21490, writes 14 timeouts 0, SG min/max 0/0
    Driver 3: standstill, reads 21491, writes 14 timeouts 0, SG min/max 0/0
    Driver 4: standstill, reads 21495, writes 11 timeouts 0, SG min/max 0/0
    Driver 5: standstill, reads 21496, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2020-10-16 13:10:01
    Slowest loop: 6.25ms; fastest: 0.25ms
    === Move ===
    Hiccups: 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
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon* is idle in state(s) 0
    queue is idle in state(s) 0
    lcd is idle in state(s) 0
    spi is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 0.52ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 0 of 8
    - Ethernet -
    State: 0
    Socket states: 0 0 0 0 0 0 0 0
    === CAN ===
    Messages sent 164, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 1
    Last transfer: 19ms ago
    RX/TX seq numbers: 1375/1377
    SPI underruns 0, overruns 0
    Number of disconnects: 1
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.1.1
    Trigger:
    Finishing macro config.g, started by system
    > Next stack level
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 32.62
    


  • @Martin1454 said in incompatible firmware v on duet3?:

    3.0beta12

    please update to 3.1.1

    you need to update to 3.0 first
    see
    https://github.com/Duet3D/RepRapFirmware/releases/tag/3.0





  • Ah! thanks you guys, i'll give that a try!



  • @bearer
    So i tried the DWC way shown in your link - but
    the DWC interface have been stuck on "Please wait while updates are being installed..." for +24hours -

    What to do? I dont wanna risk bricking it by power cycling if thats a chance



  • @Martin1454 said in incompatible firmware v on duet3?:

    I dont wanna risk bricking it

    you can always recover using USB and bossa (unless something is damaged, the bootloader is in read only memory in the cpu)

    update taking more than a minute or so has failed so you can reset the board, and if you're unable to connect refer to https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3 just make sure to get the duet3 firmware file as the guide is written for duet 2.


  • Moderator

    @Martin1454 said in incompatible firmware v on duet3?:

    the DWC interface have been stuck on "Please wait while updates are being installed..." for +24hours -

    Give it a power cycle. You can't really brick it. Power back up and see if the update was applied. If not, try uploading the zip file again.

    Make sure you're uploading the entire zip file without extracting it.

    If it continues to fail, what version are you currently on? What version of DWC does it show?



  • @Phaedrux

    Duet Web Control 3.1.1
    DSF Version: 3.1.1

    note that I am using the Duet 3 with an RPI - And I have tried the sudo apt-update and upgrade - But I still get 3.1.1 / the message "duetsoftwareframework is already the newest version (3.1.1)." - Is there something I can do to downgrade to 3.0 first and then back up?


  • administrators

    Your best options are to upgrade the main firmware using Bossa, or to run the Duet in standalone mode with a USB connection and install the latest firmware from the SD card. Upgrading to 3.0 first isn't essential on the Duet 3.



  • @dc42 said in incompatible firmware v on duet3?:

    Your best options are to upgrade the main firmware using Bossa, or to run the Duet in standalone mode with a USB connection and install the latest firmware from the SD card. Upgrading to 3.0 first isn't essential on the Duet 3.

    What would you reccomend to upgrade to then?


  • administrators

    @Martin1454 said in incompatible firmware v on duet3?:

    @dc42 said in incompatible firmware v on duet3?:

    Your best options are to upgrade the main firmware using Bossa, or to run the Duet in standalone mode with a USB connection and install the latest firmware from the SD card. Upgrading to 3.0 first isn't essential on the Duet 3.

    What would you reccomend to upgrade to then?

    3.1.1 to bring it into line with the version of DSF on your Pi.


Log in to reply