Upgrading to RFF 3.0RC2 issues

blt3dp

@Dougal1957 said in Upgrading to RFF 3.0RC2 issues:

@blt3dp IIRC DC did say to hold off doing the RC1 upgrade until DSF1.2.x.x was released and it would upgrade AIO but that was I think mainly so that the IAP Fit was put in the correct place. RC2 uses the same file so can be installed as per the old method

Which coincides with the documentation

Before you can update DSF, it is important to install the latest RepRapFirmware version first. If you are using recent DCS (>= 1.0.2.0) and RRF versions, you can put the updated Duet3Firmware.bin file in the /sys directory and run "M997". This will trigger a firmware update. For convenience, you can simply upload Duet3Firmware.bin on the System page of DWC2 and confirm the update.

But it didn't appear to work:

@Minion said in Upgrading to RFF 3.0RC2 issues:

So now uploading "Duet3Firmware_MB6HC.bin" as system file starts update without errors. However, after installation it still shows that Firmware is : RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12+1 (2019-11-11b1)

What am I missing here?

Dougal1957

@blt3dp I found this which may be your issue.

4th post in this thread https://forum.duet3d.com/topic/13381/reprapfirmware-3-0rc1-released/3 refers

blt3dp

@Dougal1957 said in Upgrading to RFF 3.0RC2 issues:

@blt3dp I found this which may be your issue.

4th post in this thread https://forum.duet3d.com/topic/13381/reprapfirmware-3-0rc1-released/3 refers

I've got DSF 1.2.1.0 installed.

Danal

(1) Be sure your Pi is on the beta feed.
(2) Do full upgrade
sudo apt-get update
sudo apt-get upgrade
(3) Maybe need to do specific upgraded for DSF. Maybe. Check version. If needed
sudo apt-get upgrade duetsoftwareframework
(4) Should be able to m997 and get to RC1
(5) Should now be able to use Web System upload to get to RC2.

KEY is beta feed and update Pi.

blt3dp

Looks like @chrishamm just updated the packages on the unstable, I was able to get to 3.0RC2 by running:

apt-get update
apt-get upgrade duetsoftwareframework

Dougal1957

@blt3dp it may be worth running a M997 you may find it updates to RC2+1

This post refers

Minion

apt-get update
apt-get upgrade duetsoftwareframework

seemed to be working for most part, until I got error:

Setting up duetcontrolserver (1.2.2.0) ...
Setting up duettools (1.2.2.0) ...
Setting up reprapfirmware (1.2.2.0-1) ...
[error] Failed to connect to Duet
   System.IO.IOException: Error 16. Cannot put line into event mode.
   at LinuxDevices.InputGpioPin..ctor(String devNode, Int32 pin, String consumerLabel) in /home/christian/duet/DuetSoftwareFramework/src/LinuxDevices/InputGpioPin.cs:line 60
   at DuetControlServer.SPI.DataTransfer.Init() in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 65
   at DuetControlServer.SPI.Interface.Init() in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 65
   at DuetControlServer.Program.Main(String[] args) in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 92

then did

apt reinstall reprapfirmware

and while

Setting up reprapfirmware (1.2.2.0-1) ...

no errors occured. So now I have:
DSF: 1.2.2.0
RRF: 1.2.2.0

Sent M997, said updating + restarts. M122 says I am still on "RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12+1 (2019-11-11b1) ".

Uploading "Duet3Firmware_MB6HC.bin" for either RC1 or RC2 as system file initializes update, restarts + M997 ....aaaand still says I am on 3.0beta12+1.

Whats up with that?

@Danal, if I am getting the "unstable" versions of DSF+RRF via apt-get upgrades means I am on "beta" feed, right?

A Former User

@Minion said in Upgrading to RFF 3.0RC2 issues:

, if I am getting the "unstable" versions of DSF+RRF via apt-get upgrades means I am on "beta" feed, right?

yeah, if you added the unstable apt source you'll get the beta

Minion

Well in that case I am confused about what am I doing wrong. Very open to suggestions

jay_s_uk

@Minion if you can't get it to upgrade, you'll have to use bossa to upgrade to the latest version. I rember @Danal mentioning he had to do that to go from beta 12 to RC1

deckingman

@Minion said in Upgrading to RFF 3.0RC2 issues:

Well in that case I am confused about what am I doing wrong. Very open to suggestions

Your issue sounds very much like this thread https://forum.duet3d.com/topic/13607/duet-3-standalone-rrf3-package/21

I'm not 100% sure but I think you need to get the file Duet3iap_sd_MB6HC.bin from 3.0Beta11 which will get you to RC1. Then you need Duet3_SDiap_MB6HC to get to RC2.

Minion

@jay_s_uk I'll start reading on how to do that, ty
@deckingman tried that, still same.

Ok, got some extra info I failed to mention which may be of relevance: I have two expansion boards attached to my duet. Those I managed to update to 3.0RC2 2019-12-28b4 - (that's what I get if I sent M115 B1 / M115 B2).

deckingman

@Minion that's the correct expansion board firmware.

dc42

@deckingman said in Upgrading to RFF 3.0RC2 issues:

@Minion said in Upgrading to RFF 3.0RC2 issues:

Well in that case I am confused about what am I doing wrong. Very open to suggestions

Your issue sounds very much like this thread https://forum.duet3d.com/topic/13607/duet-3-standalone-rrf3-package/21

I'm not 100% sure but I think you need to get the file Duet3iap_sd_MB6HC.bin from 3.0Beta11 which will get you to RC1. Then you need Duet3_SDiap_MB6HC to get to RC2.

It should also be possible to use Duet3iap_sd_MB6HC.bin to upgrade direct from beta 11 to RC2. Just make sure you have both IAP files in /sys. RRF will pick the one that it wants to use.

Minion

@dc42 got both IAP files in sys.

Now, while calling M997 to update, I actually get an error:

Error: Failed to create directory 0:/sys
Error: Failed to create folder 0:/sys while trying to open file 0:/sys/filaments.csv

Ideas anyone?

blt3dp

@Minion said in Upgrading to RFF 3.0RC2 issues:

0:/sys/filaments.csv

Maybe you can kind of work around it by going to the filaments section on the left and creating a filament to see if maybe it will create the filaments.csv for you? Unsure why the firmware update would need that but maybe that'll be enough to get past it?

Minion

@blt3dp now M997 finishes without errors, but still end up with same "3.0beta12+1".

Everything else seems to be updating without problems via apt-get update/upgrade.

Here's the list of files in my /sys/, maybe one of you can spot I am missing something or there's anything which doesn't belong there:

.      config.g     Duet3Bootloader_EXP.bin   Duet3Firmware_MB6HC.bin  Duet3iap_spi_MB6HC.bin  Duet3_SBCiap_MBP05.bin  filaments.csv  homey.g    pause.g   stop.g    tpre0.g
..     config.json  Duet3Bootloader_TOOL.bin  Duet3Firmware_MBP05.bin  Duet3iap_spi_MBP05.bin  Duet3_SDiap_MB6HC.bin   homeall.g      homez.g    resume.g  tfree0.g
bed.g  configOld.g  Duet3Firmware_EXP3HC.bin  Duet3iap_sd_MB6HC.bin    Duet3_SBCiap_MB6HC.bin  dwc2settings.json       homex.g        iap4e.bin  sleep.g   tpost0.g

Danal

There may be a solution that allows an M997, and you may want to continue to pursue it. If instead you just want to move on, consider bossa/bossac. Specifically, I also got stuck on that release on the 6HC, and also was able to upgrade expansion boards with M997.

I plugged a short USB cable from the Pi to the 6HC, installed the latest release of bossa on the Pi, and ran bossac from the Pi.

I do remember something about putting bossa on via apt-get, and then taking it off, and putting on a more current release, directly from the vendor's github page. So just start with https://github.com/shumatech/BOSSA to install bossa if you chose to go this way. The final commands were:

git clone https://github.com/shumatech/BOSSA
cd BOSSA
make bossac
~/BOSSA/bin/bossac -e -w -v -b /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin -R

gtj0

I think you still need --port=/dev/ttyUSBxon that bossac command. Anyway, that's how I have mine hooked up as well.

Danal

bossac will auto-scan! What a great tool.