I ma not able to write or edit on DUET 3 3.5.2 firmware

martin7404

After 2 weeks pause I powered my Duet controled printer with Duet 3 board and I am not able to uplad any file
get this kind of error

I think it is SD card
what is the less painfull way to get it up back to life

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.2 (2024-06-11 17:13:58) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6JKDA-3S86L-1BDB9
Used output buffers: 3 of 40 (31 max)
=== RTOS ===
Static ram: 155360
Dynamic ram: 120656 of which 488 recycled
Never used RAM 69488, free system stack 202 words
Tasks: NETWORK(1,ready,38.0%,155) ETHERNET(5,nWait 7,0.1%,318) HEAT(3,nWait 6,0.0%,323) Move(4,nWait 6,0.0%,335) CanReceiv(6,nWait 1,0.0%,794) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,9.3%,53) MAIN(1,running,51.9%,103) IDLE(0,ready,0.7%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:28:20 ago, cause: software
Last software reset at 2024-07-29 21:32, reason: User, Gcodes spinning, available RAM 69340, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 29.5, current 29.7, max 30.6
Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, 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 n/a, mspos 4, reads 27541, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 4, reads 27541, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 27541, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 27541, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 27542, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 27542, writes 0 timeouts 0
Date/time: 2024-07-29 22:00:33
Slowest loop: 536.11ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 42.1ms, write time 9.3ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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 2 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP is idle 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 0 clear 9325857
Extruder 0 sensor: ok
=== CAN ===
Messages queued 2726, received 6055, lost 0, errs 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 6, free buffers 50 (min 50), ts 1514/1514/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 557.27ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

M122 P104
Testing SD card write speed...
Error: Failed to write to file, error code 1. Card may be full.
Error: Failed to write to file. Card may be full.
Error: Failed to write to file, error code 1. Card may be full.
Error: Failed to flush data to file. Card may be full.
Error: M122: Failed to write to timing file

martin7404

Fixed it . It was 2 years old SD card. Good quality card. Formated a new one and created new structure witht the current firmware and config. back to printing