You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This version of Xous is the MVP milestone for backer shipment. It is strongly recommended that all backers who receive their devices update to this version before personalizing their units, as there are several API-breaking fixes in this release compared to what was flashed in the factory several months ago.
While we are striving to stabilize all the APIs, we're still not at 1.0.0, which means we expect that we'll find bugs that could require breaking backward compatibility with provisioned/root-keyed devices. Breaking backward compatibility means requiring a JTAG-cable level "unbrick" process to bring things up to date, that would also wipe any data from the device. An example of a problem that could trigger such a change is if a major flaw is found in the root key enclave implementation -- as more people get their eyes and hands on the code base.
This version is tagged out to a "release" because it has also been pushed to the factory, so future units that roll off the production line will be shipped with software built using this particular code base. This corresponds to the bootstrap-mainboard repo version v0.7.4 state.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This version of Xous is the MVP milestone for backer shipment. It is strongly recommended that all backers who receive their devices update to this version before personalizing their units, as there are several API-breaking fixes in this release compared to what was flashed in the factory several months ago.
While we are striving to stabilize all the APIs, we're still not at 1.0.0, which means we expect that we'll find bugs that could require breaking backward compatibility with provisioned/root-keyed devices. Breaking backward compatibility means requiring a JTAG-cable level "unbrick" process to bring things up to date, that would also wipe any data from the device. An example of a problem that could trigger such a change is if a major flaw is found in the root key enclave implementation -- as more people get their eyes and hands on the code base.
This version is tagged out to a "release" because it has also been pushed to the factory, so future units that roll off the production line will be shipped with software built using this particular code base. This corresponds to the
bootstrap-mainboard
repo version v0.7.4 state.This discussion was created from the release v0.9.6 - backer shipment MVP.
Beta Was this translation helpful? Give feedback.
All reactions