Duet 0.85 Reflashing after bricking

oldschoolPiratename

Hello All,

Long time follower here

Have old Kossel Mini 3 with Duet 0.85 firmware on board.

I wanted to update to
releases - 2.05.1 (not allowed to post links, but it is from Git Firmware Repository
today, but I guess I bricked my Duet 0.85.

Before bricking it, I was running

Firmware Name: RepRapFirmware for Duet
Firmware Electronics: Duet 0.85
Firmware Version: (cant remember version but I remember the date) (2019-11-09b1)
Web Interface Version: 1.21 ( something around here)

Could someone kindly point me to a procedure to update or reflash these old board?

Update I can connect to microcontroller onboard using Sam-ba 2.17.
I tried updating Duet2CombinedFirmware.bin as stated in Duet3d Documentation, but it didnt do the trick.

On board I still have all three LEDs permanently active (Blue, Red Yellow)
I tried copying DWC to SD card /www folder but without success.
In /sys/config file I reviewed ethernet settings. They are set correct. My thinking is programming process is unsuccessful and thus I have no access to the board over ethernet...

Again, any help is greatly appreciated.

Kind Regards,
OldschoolPirate

droftarts

@oldschoolPiratename Flashing the 0.85 is the same as current boards, ie use Bossa. I've never got Sam-ba to work. See https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware

Use the 'RepRapFirmware.bin' file from https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1 which will update the board to 1.26.1. Duet 0.6/0.85 can't run RRF 2.x.

Ian

oldschoolPiratename

Hi droftarts,

That did the trick!

I had to perform complete install of Bossa, not just run exe, for my system to find COM port, but afterwards it went on swimmingly.
I tried connecting to printer with Pronterface with no issues (over USB cable).

Now comes the second hurdle - DWC refuses to connect.

I set IP address and my PC has different IP in same range, and ping gets a reply, but I get
"IP Adress refused to connect" error in browser.

I could be that my LAN needs a bit tinkering and will work on this, but as a side question - is there a way to verify if DWC is properly deployed and running?

It is placed on SD card (in /www folder), along with /sys and /gcodes as described in SD Card file structure.
Technically, printer is up and running (according to Pronterface), but I am really partial about DWC. It is really a huge QOL improvement.

Just a side note, during this debugging session, printer is directly connected to my PC´s LAN port. I used this setup before, when trying out some tweaks, with no issues and I dont see why it shouldnt work now as well.

Do you have any hints for me at this point?

Thanks in advance for taking time to respond previously and for any information you can provide.

Kind Regards,

dc42

@oldschoolPiratename you can send M552 from Pronterface to check whether the network interface is enabled and what IP address it is using.

Have you extracted the DWC zip file from the 2.05.1/1.26.1 release into the /www folder of the SD card?

oldschoolPiratename

@dc42
@droftarts

Hello guys,

I tried it and got a reply.
So that worked.

After being sure that it is only Eth issue, I added a small switch in between, I remember that once I did a similar work-around at a LAN connection at my friend's house during a LAN party (yes, I am that old).

AND I got a reply from printer! DWC smiled at me.

I works like a charm now.
Interface is there, firmware updated and I am happy as I can be.

I would like to thank you both for your help and assistance.

Kind Regards,

P.S. If any of you two passes through Linz, let me know. I owe you a beer or few.