40 likes | 168 Views
Process. Hook up flight crate as SIU Upload FSW B0-6-1 application files into ee1 “SIU” application files Upload and burn new PBC image Upload and burn serial number image FOR THIS SPECIFIC CRATE (identified by Bay # and BAE S/N) Boot code is for EPU FSW build is still “SIU”
E N D
Process • Hook up flight crate as SIU • Upload FSW B0-6-1 application files into ee1 • “SIU” application files • Upload and burn new PBC image • Upload and burn serial number image FOR THIS SPECIFIC CRATE (identified by Bay # and BAE S/N) • Boot code is for EPU • FSW build is still “SIU” • Remove “SIU” application files; add “EPU” application files • Hook up flight crate as EPU (see next slide) • Test PBC burn by booting EPU and dumping memory from EPU Boot Code Readiness Review
HW setup For burning of SUROM, use this test setup: Mobile rack For verifying burn, use this test setup: Boot Code Readiness Review
“Fixing” the first flight crate • State of first flight crate has been duplicated in the lab • Shows identical behavior • Develop a script, RecoverEPU.py, to upload the missing files to the SIB. • Tricky bit: using LICOS to upload files to an EPU (not SIU) • Repeat “Burn Verification test” in TD-07831 Boot Code Readiness Review
Options for other two flight crates • Do nothing • Repeat procedure exactly as before, no changes • Repeat procedure with one change: • Upload ALL files (SIU and EPU) to crate before burning PBC • Last step in process is now PBC burn • If crate reboots during an upload, we can still bring it up as an SIU through 1553 and view the telemetry • This doesn’t make the PBC burn any more or less safe than before • It does give us some breadcrumbs (in the form of telemetry) to follow if the crate reboots spontaneously • Other? • Use Corelis Boot Code Readiness Review