3.01 RC2 Won’t Upgrade



  • I have updated all my machines to RC2 and all except the problem child have been upgraded regularly in the rrf3 path. I had one machine that was still on 3.0 beta12 and just tried to upgrade it 3 times. Says it completes properly asks to restart and does, but no go. It remains on beta12. Any hints much appreciated. I am on 2.0.7 dwc

    Board: Duet WiFi 1.02 or later
    Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0beta12 (2019-11-02b1)
    Duet WiFi Server Version: 1.23


  • Moderator

    Flash it with bossa?



  • With all the machines and all the upgrades I’ve done over years, thats never been necessary. Why now?


  • Moderator

    @4lathe said in 3.01 RC2 Won’t Upgrade:

    3.0beta12

    I think it's particular to Beta12.



  • Can I just copy it to the sd card and reboot?


  • administrators

    @4lathe said in 3.01 RC2 Won’t Upgrade:

    Can I just copy it to the sd card and reboot?

    Yes, then run M997.



  • @dc42 copied it to the sd card, restarted, m997 and same old 3.0 beta 12. Any other thoughts?

    2/27/2020, 11:09:05 AM m122
    === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0beta12 running on Duet WiFi 1.02 or later Board ID: 08DGM-95BNL-MGPSJ-6J1D0-3SD6L-1JZZX Used output buffers: 3 of 24 (15 max) === RTOS === Static ram: 25812 Dynamic ram: 97284 of which 96 recycled Exception stack ram used: 256 Never used ram: 7624 Tasks: NETWORK(ready,1036) HEAT(blocked,1184) MAIN(running,3664) IDLE(ready,200) Owned mutexes: === Platform === Last reset 00:01:55 ago, cause: software Last software reset at 2020-02-26 19:23, reason: User, spinning module GCodes, available RAM 7360 bytes (slot 2) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms, max retries 0 MCU temperature: min 29.0, current 29.5, max 29.8 Supply voltage: min 24.2, current 24.3, max 24.5, 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-02-27 11:09:03 Cache data hit count 399321780 Slowest loop: 2.27ms; fastest: 0.09ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 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 === 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: 2 allocated, 0 in use 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 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 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 200.45ms; fastest: 0.08ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 2 WiFi firmware version 1.23 WiFi MAC address 2c:3a:e8:0b:27:5b WiFi Vcc 3.39, reset reason Turned on by main processor WiFi flash size 4194304, free heap 24552 WiFi IP address 192.168.1.229 WiFi signal strength -66dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0


  • administrators

    I just realised, it's probably because you are running a 3.0beta version. That beta probably uses the old IAP to upload new firmware, and the old IAP can't handle the size of 3.01. Try upgrading to 3.0 release, then from there to 3.01RC2. When you upgrade to 3.0 release, make sure that you upload the Duet2CombinedIAP.bin file too.

    If you have a PanelDue connected, you can see the status on it during the upgrade.



  • Thank you so much! That was it.


Log in to reply