firmware update failed

PCR

The 3 mini is super easy to "unbrick"
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Duet_3_Mini_5_WiFi_Ethernet

TomW

@pcr WHEW, thanks! My board did not come with an SD card, or I dropped it when putting this kit together, do I need to put a fresh 8G card in before doing the above procedure?

PCR

@tomw don't think so.

TomW

@pcr No good. The mini5+ is "alive", I can connect to it via minicom over USB. It responds to reprap commands (e.g. M115, M114) but do a G28X and it complains of "Homing file homex.g not found".

Okay, at least it is "there", I have control over the board. It still won't allow the SBC to connect to it, "DCS is not started". So, that tells me that the SPI link is not operational?

Nothing was disturbed on the wiring, this was a software breakage. <sigh> /me writes a lot of code.

TomW

@tomw OH, and I did re-image the Pi4 with 2021-07-12-DuetPi.img

PCR

@tomw do you have now a SD card in the mini 5? If yes remove it

Rushmere3D

This post is deleted!

TomW

@pcr FINALLY, I've been able to restore the machine back to v3.3! That was a lot of work. There appears to be a problem with the 3.4.0beta6 release, it will not load into my Duet Mini5+ (with 2 driver expansion). The board rev is v1.01, no wifi connected / configured, Raspberry Pi3 Model A+ on the SBC link running the 2021-07-12-DuetPi.img.

I've had to run the SBC (Pi) in multi-user mode instead of graphical. The desktop package loads the raspberry too heavily! Response to DWC console commands is sluggish, at best.

Now, the goal was to get the M600 command working correctly. Previously, with v3.3 of DWC, the M600 would force an endless loop of pause.g and resume.g, it would never resume printing.

So, let's try this again:

I have a working RatRig v-core 3 printer to start.
As per INSTALLING AND UPDATING FIRMWARE, it instructs me to download "Download firmware zip bundle (named Duet2and3Firmware-3.xxx.zip)" ... There is no such file?

Apparently the instructions are in error or a file is missing or I'm following the wrong set of instructions?

This should be much easier to do. I've uploaded that 3.4.0beta6 several times into DWC firmware section and bricked the controller each time. Getting the controller back to v3.3 has required a fresh copy of the 2021-07-12-DuetPi.img into the SBC, crossed my fingers and uploaded the original Duet3Firmware_Mini5plus.uf2 via the USB cable.

Stephen6309

@tomw When using a Raspberry PI. all updates must be doen with sudo apt update and sudp apt upgrade. To use the current beta version switch to unstable. I use PuTTY to acces the PI.
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation

TomW

@stephen6309 Thank you Stephen, it worked a charm! Now running 3.4-b6. It is always something stupid, usually me

droftarts

@tomw somewhere on the updating firmware page, it says that firmware update is different if you use an SBC, and links to those instructions (on phone, too hard to see!). It also says that only release versions of firmware have the full zip file; beta and RC versions do not. It seems both of these points need to be a bit clearer!

Ian

TomW

M600 is now properly processed within the gcode stream.

I write code and know how hard it is write for another audience. It is hard to write "down to" someone less familiar with the given task. Yes, it is confusing.