Upload firmware?
-
When I run M997 S0, it says something like "please wait while firmware is being updated" - Then after a while is says "operation has been canceled" - No explanation.
What to do?
9/6/2020, 7:58:59 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 v0.6 version 3.0alpha running on Duet 3 version v0.6
Board ID: 08DGM-9T66A-G63SJ-6J9FJ-3SD6R-KS0ZA
Used output buffers: 2 of 32 (8 max)
=== RTOS ===
Static ram: 67772
Dynamic ram: 156016 of which 0 recycled
Exception stack ram used: 612
Never used ram: 168816
Tasks: NETWORK(ready,456) HEAT(blocked,1208) CanReceiv(suspended,3804) CanSender(suspended,1496) CanClock(blocked,1432) TMC(blocked,592) MAIN(running,3472) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 00:02:44 ago, cause: reset button
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 168424 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04429000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 42.7, current 43.2, max 44.1
Supply voltage: min 20.0, current 20.1, max 20.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 4336, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 4338, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 4339, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 4341, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 4345, writes 11 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 4347, writes 11 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 1.55ms; fastest: 0.29ms
=== 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 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
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: 25.26ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- Ethernet -
State: 5
Socket states: 5 2 2 2 2 0 0 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 164619ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
9/6/2020, 7:56:19 PM M997 S0
Operation has been cancelled
9/6/2020, 7:55:36 PM Connected to 192.168.1.229
- Ethernet -
-
to which firmware version are you upgrading?
3.0 and then 3.1.1 as described in the readme?
-
Nope
Trying 3.0 now. It pretty fast lost connection to the interface, and now I can't connect to it. How long is this supposed to take? - Looks like it's just gone. How long should I wait before I power cycle it?
-
Fark.... Powercycling did nothing, it is unreachable
Now what?
-
see
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3
To update via USB (using a Windows host):
-
That worked. Thanks.
