RRF3.5 crash Duet 3 6HC
-
@damaged_goods
Can you connect via USB?
If so post the results of M122 and M98 P"0:sys/config.g"
If not maybe try a new SD card and/or restore from a backup.
It sounds like config.g might have an issue. -
How did you try to update the firmware?
-
@Phaedrux I downloaded the file from github and uploaded it through dwc. Just after it started uploading it lost connection, although I still had internet, and after leaving it for about 1 hour trying to reconnect on its own I turned it off and restarted.
Now it will not load config and ethernet connection seems off. I've tried new ethernet cables but no data light at router and no light at the board.
I also copied config.g from backup and replaced the possibly faulty one. No change. -
Take a look through this page and see how far you can get.
https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond
Let us know what LED lights are lit.
You can't brick a board from a firmware update, so worst case you can erase the firmware and re-flash over USB, but the board has to be seen by your device to flash to first.
-
@Phaedrux Thank you. I will try it over the next few days. I has been very disheartening. I just got it working well and was aiming for higher. Silly me.
-
@OwenD I did all that you suggested without luck. I cannot connect to the board by any means it seems.
-
I wondered what a Bossa port was. I saw it when I was trying to connect to the board through YAT. I did not touch the Erase button.
@Phaedrux If a port called Bossa port is shown then the firmware has been erased. Perhaps you pressed the Erase button. You need to re-install firmware via USB. See the "Fall-back procedure #2" section in Installing and Updating Firmware.
-
Yes, if you see a bossa port, you'll need to reflash the firmware.
-
@Phaedrux It appears the flash is corrupted so I downloaded the version 3.5.0 beta 2 zip file. If I try and load zip file into the Duet Bossa I get an error that " file operation exceeds flash size". What am I missing?
-
@damaged_goods said in RRF3.5 crash Duet 3 6HC:
What am I missing?
Following the directions.
https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2
Use this firmware file.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet3Firmware_MB6HC.bin
-
@Phaedrux Sorry for my ignorance but I downloaded the duet bossa but cannot find the exe file.
-
https://github.com/Duet3D/BOSSA/releases/download/1.9.1a-duet3d/Bossa.exe
Did you download that?
-
@Phaedrux After multiple loading failures it thankfully loaded. I now have the board showing up on the computer.
-
So you were able to get it flashed?
-
@Phaedrux Yes although it did freeze several times and would not complete. I just prayed, ended the task and tried again. I reinstalled the sys file from backup and all seems back to normal.
Any idea what might have happened? I would like to attempt future firmware upgrades but now I am a little scared. -
Please send M122 and M122 B# where # is the canbus address of your expansion boards and copy and paste here.
Also check your DWC version.
Uploading the 3.4.5 zip file to the system tab in DWC should work.
You're not using an SBC are you?
-
@Phaedrux 2/20/2023, 10:41:54 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6JTDJ-3SJ6M-T83BA
Used output buffers: 3 of 40 (25 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 97040 of which 160 recycled
Never used RAM 100712, free system stack 200 words
Tasks: NETWORK(ready,23.1%,176) ETHERNET(notifyWait,0.3%,443) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,333) TMC(notifyWait,7.9%,91) MAIN(running,68.4%,1083) IDLE(ready,0.3%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:12:35 ago, cause: power up
Last software reset at 2023-03-02 01:46, reason: AssertionFailed, Platform spinning, available RAM 100424, slot 2
Software reset code 0x4120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xf069b60c Task M��� Freestk 4294967295 ok
Stack: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 131
MCU temperature: min 17.4, current 34.2, max 35.6
Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, 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 0, mspos 8, reads 12817, writes 16 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 12819, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 12819, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 12820, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 12820, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 12818, writes 16 timeouts 0
Date/time: 2023-02-20 10:41:56
Slowest loop: 1171.63ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.5ms, write time 154.2ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
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
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 6798, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 3778/0/0
Tx timeouts 0,0,3777,0,0,3019 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 1171.52ms; 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: 2 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 2 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0DWC 3.4.0 is installed at this time
I have no idea what an SBC is
-
@damaged_goods said in RRF3.5 crash Duet 3 6HC:
DWC 3.4.0 is installed at this time
Ok, so with firmware 3.4.5 flashed to the board your DWC version should now be updated to match. You didn't include the M122 for the expansion board, so it's probably not matched to 3.4.5 yet either.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip
Upload that zip file to the system tab in DWC and that should get everything updated.
-
@Phaedrux Thank you for your assistance. I really appreciate it!
I did not include an expansion board M122 because I don't believe I have one.
Thank you again. Hopefully I won't be bothering you any time soon.
