Files in /sys on RRF3



  • I have a new Duet 2 Maestro which I upgraded to 3.1.1 before installation. I also used the configtool to generate template configuration files. All is running well, but I now have a number of possibly obsolete files in the /sys directory. My problem is that I am not sure which files can safely be removed and which are needed/used.
    The only information I have found regarding what should to be in /sys is this dozuki page. However, that information does not seem to have been updated for RRF3; for example, the files tpre#.g, tpost#.g and tfree#.g are not mentioned; I guess this is because they were introduced with RRF3?
    A few questions:

    • Has iap4s.bin been replaced by DuetMaestroIAP.bin (rendering iap4s.bin obsolete)?

    • Does iap4s.bin/DuetMaestroIAP.bin have to be on the SD-card for the next firmware update to work, or will it be included in the upgrade?

    • The file start.g is not mentioned in the dozuki page. Are there other "magical" files that the firmware expects to find in /sys?

    • Is it safe to remove all *.bin files (including iap4s.bin)?


  • administrators

    @ÖrjanE said in Files in /sys on RRF3:

    • Has iap4s.bin been replaced by DuetMaestroIAP.bin (rendering iap4s.bin obsolete)?

    Yes. If you revert to RRF2 then you will need iap4s.bin again when you wish to upgrade/downgrade.

    • Does iap4s.bin/DuetMaestroIAP.bin have to be on the SD-card for the next firmware update to work, or will it be included in the upgrade?

    If you upgrade the firmware using the .zip file that is usually provided with major releases, then it will be included.

    • The file start.g is not mentioned in the dozuki page. Are there other "magical" files that the firmware expects to find in /sys?

    Thanks for pointing this out. I've added start.g to the documentation.

    • Is it safe to remove all *.bin files (including iap4s.bin)?

    In principle yes, however I suggest you leave them in /sys in case you want to re-flash them, or upgrade to a beta or RC version for which no .zip file is provided.



  • @dc42 said in Files in /sys on RRF3:

    • Is it safe to remove all *.bin files (including iap4s.bin)?

    In principle yes, however I suggest you leave them in /sys in case you want to re-flash them, or upgrade to a beta or RC version for which no .zip file is provided.

    Ok. I guess the relevant bin-files to keep are DuetMaestroFirmware.bin, DuetMaestroIAP.bin and DuetWiFiServer.bin. The others coming from the .zip seem to be for Duet3 or the other Duet2-cards.

    A follow up question;
    What is the role of config.json and dwc2settings.json, also present in the /sys directory? Are these ever read by the system from the SD-card or have they only been placed there as a backup? From what I can see, the live DWC-settings are stored in /www/dwc.json.


  • Moderator

    @ÖrjanE said in Files in /sys on RRF3:

    config.json

    This is produced by the configurator along with your config set. It can be reloaded into the configurator to let you make changes to your existing config. Be aware however that any manual edits done to config.g won't be reflected in config.json.



  • @ÖrjanE said in Files in /sys on RRF3:

    Ok. I guess the relevant bin-files to keep are DuetMaestroFirmware.bin, DuetMaestroIAP.bin and DuetWiFiServer.bin. The others coming from the .zip seem to be for Duet3 or the other Duet2-cards.

    DuetWifiServer.bin isn't something for a Duet 2 Maestro, its for the Duet 2 Wifi board so that one could be deleted also.


Log in to reply