• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

Split iap binaries out of reprapfirmware

Scheduled Pinned Locked Moved
DSF Development
3
4
187
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    gtj0
    last edited by 27 Sept 2019, 21:35

    The reprapfirmware package contains both the main firmware files (which will change a lot) and the in-app upgrade binaries (which will hardly change at all). The main firmware files are also more likely to be modified and re-built by savvy users or developers. I think it'd make more sense to split the iap binaries into their own package so you could install the official version of them and maybe not install the firmware package at all if you're building your own.

    1 Reply Last reply Reply Quote 0
    • undefined
      chrishamm administrators
      last edited by 30 Sept 2019, 07:27

      Yes, that makes sense - I can put them back into the SD package.

      Duet software engineer

      1 Reply Last reply Reply Quote 0
      • undefined
        dc42 administrators
        last edited by 30 Sept 2019, 07:50

        If we put IAP in a separate package, how will we make sure that users update the IAP when they need to?

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • undefined
          chrishamm administrators
          last edited by 30 Sept 2019, 07:58

          We can add a dependency to the latest SD package from the RRF package.

          Duet software engineer

          1 Reply Last reply Reply Quote 1
          3 out of 4
          • First post
            3/4
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA