Duet 3 Standalone RRF3 Package?
-
If you got it to do something, try again with the RC2 file and un-renamed IAP.
-
hhmmm...
what now?sorry for picking on this...
-
No problem. At one point, my machine got "stuck" on Beta 12, and I couldn't get ANYTHING else to load.
My fix was to get the Pi fully updated... buy you are running stand-alone.
So let's headscratch for a moment.
-
tried it again...and still the filename issue pops up
-
Totally off topic: I like your logo.
OK, if it doesn't like the filename... I know those have changed over time. Perhaps see if you can get a prior release to load? And look at that releases notes to see the correct names at that point in time?
That MIGHT provide enough understanding to then march forward again. Not sure.
-
@Danal
thx for the logo..
Just tried RC1, same problem
-
this is my sys file listing...missing anxthing?
-
what does the error message say?
-
@Hornetrider As a very early adopter of Duet 3 with pre-production and prototype boards, I've been updating the Duet 3 firmware since around July 2019 - mostly beta versions. On several occasions, running M122 has reported a firmware version different from that which David said it should be. In every case, it has been an error on my part in somehow updating with the wrong file. On one particularity maddening occasion, it transpired that the synchronising software I run on my Synology NAS was doing something it shouldn't do and updating the firmware that I just downloaded to an older version which was stored on my NAS.
I don't have any concrete suggestions for you except to say create a blank folder on your PC and download the file again. Put this downloaded file into the blank folder. If your browser adds a (1) or something like that to the file name, rename the file so that it exactly matches Duet3Firmware_MB6HC.bin. Then delete the file from the sys directory and upload the one that you are sure is the right one (in that blank folder you just created). Then run M997 to instal it. If that doesn't work, I'm as stuck as you.
-
@deckingman
I have downloaded the files via browser {download directory, cleaned, renamed etc} and uploaded it via dwc.
Done the same also directly with the SD card.
Still same error.Tomorrow I will try it again....
Maybe I am just too used to RRF2. X and Duet 2Wifi...
Thx for all the help.
I'll keep you posted. -
@Hornetrider I guess that your current version of RRF does not work with the IAP being loaded into RAM. The IAP files attached to the RC2 release will only work that way though.
Please look back through the pre-releases on GitHub to find the appropriate IAP file where it would still be flashed. I don't remember the file name off hand but I can look that up tomorrow if you did not find it yourself. -
(if all else fails you should still be able to update by usb. ref https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware
i think bossac was part of the first image or dsf package, but you can update from your computer as well if you prefer) -
@bearer In my experience, if the firmware fails to update, then the red LED sync light stops flashing and all connections via the web interface stop.
-
Which is why I linked to the USB procedure as a last resort of sorts. As long as the bootloader isn't damaged then that should work, and the bootloader shouldn't be affected by the updates.
-
Hi Guys
thx for all the support. Finally I got it running.
As I had a pretty blank sys file directory it wasn't that easy.The solution was to get from 3.0Beta11 the file Duet3iap_sd_MB6HC.bin
with this I was able to run the update to 3.0RC1 and then to 3.0RC2.This was a DUET3 from November from my dealer.
As this was not kind of an easy Task, I could imagine that a lot of people would like that for the 3.0RC2 a budle of files should be created, so that the update could be done a bit easier for users not used to search github for all files.I assume there are a lot of boards out there in the shops that will have to be updated...
So, now I will do the fine tune on this one
-
@bearer Yes, I think we are sort of talking at cross purposes. My point about the sync led was that the OP would have a visual indication if the update had failed. Anyway, not to worry - the OP seems to have got it fixed.
-
@Danal said in Duet 3 Standalone RRF3 Package?:
@Hornetrider said in Duet 3 Standalone RRF3 Package?:
used this files right before my last post...
Still got the error and then tried it by renaming the IAP, and then something worked..kind of..Yeah, depending on what release you are coming FROM, there may be some renaming involved.
There should be no need to do any renaming. But you should have both the old and new IAP files present. They have different names deliberately because they are not compatible.
In standalone mode, to upgrade from any published version of RRF3 for Duet 3 RRF prior to 3.0RC1, file Duet3iap_sd_MB6HC.bin must be present in /sys.
To upgrade or downgrade from any published version of RRF3 for Duet 3 RRF at or after 3.0RC1, file Duet3_SDiap_MB6HC.bin must be present in /sys.
If you have used M505 to put the system files in a subdirectory of /sys, when you upload the IAP or firmware files you make sure that you are viewing /sys in DWC, because firmware files (unlike config.g, homing files etc.) must always go in /sys regardless of the M505 setting.
The requirements for upgrading/downgrading via an attached RPi are similar except that the IAP files are Duet3iap_sbc_MB6HC.bin (when upgrading from older firmware) and Duet3_SBCiap_MB6HC.bin (when upgrading/downgrading from 3.0RC1 or later). These files are normally installed by apt-get-upgrade.
