MutexMaven
Leveraging VxWorks you effectively have 3 different ways this software gets updated.
Hot Patch -> Do it live! where you modify the RAM with compiled code so that the changes persist until next reboot.
Cold Patch -> Same as a hot patch, except this time you actually copy the contents into non-volatile memory. VxWorks has a really slim profile and thus this helps keep the size manageable to continue doing science experiments.
Full Updated -> Basically a clean install gets burned in.
The Cockpit XVS display is powered by VxWorks and provides a cool HMI to the pilot that's configurable. https://ntrs.nasa.gov/api/citations/20220006188/downloads/XV...
NASA actually makes all this publicly available information available on their NTRS server.
Primary and BFS Info: https://ntrs.nasa.gov/api/citations/20190000011/downloads/20... Orion BFS: https://ntrs.nasa.gov/api/citations/20230002185/downloads/FS...
The extensive use of simulators and emulators has been particularly critical, enabling parallel design and development workflows to compensate for the incredibly expensive and long-lead times of hardware. So this helped with bottlenecks in development too.
https://ntrs.nasa.gov/api/citations/20190000011/downloads/20...
You can read more about it below (when the server throwing errors). https://ntrs.nasa.gov/api/citations/20190000011/downloads/20... https://ntrs.nasa.gov/api/citations/20230002185/downloads/FS...