|
The April 2004 demo focuses exclusively
on CPU boot and boot commanding.
Demonstration Agenda
Goals of the Demonstration
-
PBC and SBC,
the FSW packages responsible for the CPU boot process,
are nearly complete and have essentially all
of their functionality.
The packages that make up the entire low-level infrastructure
used by a 1553 bus controller (ultimately, the Spacecraft)
to command the boot process, upload files,
and retrieve information about the boot process
on a flight CPU are in place:
ZLIB, FILE, CCSDS, CTDB, and PBC watchdog code.
-
Five out of five required boot and reboot conditions
run correctly:
cold boot in response to power on and power on reset signal,
cold boot in response to watchdog timeout,
warm reboot from a software command,
and warm reboot on a secondary boot exception.
-
Primary boot can be completed to a point
at which unit testing on a RAD750
under flight conditions is possible.
-
Data from the boot diagnostics area of crate SDRAM
can be captured and used to record errors
not otherwise reportable in telemetry.
-
The flight crate can be rebooted on a signal
from the Spacecraft over a discrete line.
-
The boot shell responds to commands
that allow selection of RTOS images and SBC executables.
It also responds to boot commands
that allow files to be uploaded and committed to EEPROM.
A total of five boot telecommands will be demonstrated.
-
The secondary boot process executes successfully.
SBC successfully initializes the RTOS,
creates an EEPROM file system,
and defines, installs, and initializes application modules.
|
