JSTAR Independent Test Capability (ITC) Core Flight System (CFS) Utilization October 26, 2015 Justin R Morris NASA IV&V Program Fairmont, WV 26554

Agenda 1.Introduction 2.Core Flight System (CFS) Utilization Independent Verification and Validation (IV&V) Software-only Simulator Build Server Simulation-to-Flight 1 (STF-1) CubeSat mission 2

Introduction Independent Verification and Validation Program (IV&V) – Fairmont, WV – Provide customers assurance that their safety and mission-critical software will operate reliably and safety and to advance the systems and software engineering principles 3

Introduction 4 Develop, maintain, and operate test environments and supporting tools for the IV&V Program that enables the dynamic analysis of software behaviors for multiple NASA missions – ITC Team = experts in test systems (simulations & test beds) – IV&V Project Team = experts in systems (Projects) Jon McBride Software Testing & Research (JSTAR) Laboratory JSTAR Lab is a shared resource within NASA's IV&V Program and is available for use by anyone supporting the IV&V Program Provide advanced testing and evaluation capabilities in support of verifying and validating NASA's critical software systems Explores and rapidly matures capabilities needed to meet the future challenges of NASA including Modeling and Simulations Robotics Applications Mission Flight Software Spacecraft Development Cutting-edge Tool Evaluations

IV&V IV&V performed on missions that utilized CFS – Requirements, Design, Code and Test – LRO – MMS – GPM 5

Software-Only Simulator GPM Operational Simulator (GO-SIM) 6 Components COTS Emulator Primary Instrument Simulations (GMI/DPR) GPM Ground System (ASIST) GPM Core Flight System Software GSFC Goddard Dynamic Simulator (GDS) NOS Middleware GPM Hardware Models Capabilities Load and run unmodified flight software binaries Execute test flight scripts Single-step debugging Inject errors via ground system and NOS middleware Stress system under test

7 7 ASIST Ground System with FEDS SpaceWire Router RAD 750 Emulator GPM FSW (CFS) SCOMM Simulator Dynamics Simulator (GDS) SpaceWire & SpaceWire TCP/IP KEY NOS Middleware Instrument Simulator (GMI) Instrument Simulator (GMI) Instrument Simulator (DPR) Software-Only Simulator GPM Operational Simulator (GO-SIM)

Build Server Objectives 1.Provide an automated means to exercise build system tests of Core Flight System (CFS) software 2.Support multiple target platforms – RAD750 and Linux 3.Setup a regression test suite 4.Enable efficiencies in IV&V’s testing efforts 8

System Architecture 9

Activity Flow 10 Source Code Checkout Configuration Changes (RegEx Replace Task) Make Task (build script, GNU make) Build Task (VxWorks / SB Unit) Configure ASIST (Generate needed files (.prc,.rdl)) Build ASIST Procedures Start ASIST Stop ASIST Start ASIST Linux? Run CFS Core on QEMU/RAD750 emulator Run CFS Core Executable Run pre-test cmds, ground test procs, and post-test cmds Stop CFS Core; Stop ASIST Log Test Results Build SuccessfulBuild Failed YES NO YES Failed Tasks or Tests? NO

Build Server Technologies 11 Technology/ProductOriginPurposeIntegration Method Atlassian BambooCOTSAutomated Build and Test Execution Virtual Machine Installation on Linux ASISTGOTS/GSFCGround Station used by CFS for executing build/integration tests Virtual Machine Installation on Linux ASIST WRAPPERITCASIST Ground System Automation Mostly new development for this task (Some parts leveraged from the ITC Framework) Bamboo CFS PluginITCPlugin allowing for CFS to be built by the Bamboo build server Integrated with Bamboo (Designed for reuse where possible) Core Flight System (CFS)GOTS/GSFCSoftware Under TestSource installed and built on Build Server Virtual Machine QEMU RAD750 ModelITCExecution of the CFS under the RAD750 Target running VxWorks QEMU RAD750 Model built and installed on Linux QEMU DEC Ethernet Tulip ModelITCEthernet connectivity to the RAD750/VxWorks kernel. Provides connection between VxWorks and ASIST QEMU Tulip model integrated with the QEMU RAD750 Model

Simulation-to-Flight 1 CubeSat Mission 12

Simulation-to-Flight (STF-1) STF-1 Mission Objectives Primary Objective – Demonstrate simulation technologies developed at IV&V on CubeSat. Result: Software Only SmallSat Simulator Secondary Objectives WVU Research into space weather Rad-hard materials Navigation instruments Camera

NOS 3 14 What is NOS 3 ? A software test bed for small satellites Based upon STF-1 hardware, but sufficiently generic Easily-interfaces to cFS FSW, but cFS not required Currently open-loop, closed loop planned Openly distributed solution Ready-to-Run (RTR) – Looking for Users! A collection of Linux executable and libraries What is it used for? FSW early-development – NOS 3 provides real-world inputs to FSW FSW V&V – Testing FSW, invalid inputs, behavior, stress conditions FSW Integration – Used for early-app development and payload team integration Mission Planning – Example: power analysis

STF-1 FSW Architecture 15

NOS 3 Details Thursday, October 29 at 1:05 p.m. – Zemerick – Walkthrough STF-1 mission and NOS 3 in detail 16

Conclusion Core Flight System (CFS) Utilization Independent Verification and Validation (IV&V) Software-only Simulator Build Server Simulation-to-Flight 1 (STF-1) CubeSat mission Questions / Demos / More Information 17