1 / 4

Flight Crate Processing and Boot Code Readiness Review for EPU and SIU Systems

This document outlines the process for handling flight crates identified by Bay # and BAE S/N, detailing the steps for uploading application files, burning new PBC images, and testing EPU systems. Initial steps involve hooking up the flight crate as SIU, followed by file uploads and boot code modifications. A critical aspect is the development of a Python script, RecoverEPU.py, for managing file uploads to EPU. The process emphasizes the importance of verifying burn results and ensuring that operations maintain safety and telemetry insights, even in the event of unintended reboots during uploads.

wattan
Télécharger la présentation

Flight Crate Processing and Boot Code Readiness Review for EPU and SIU Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. HW setup For burning of SUROM, use this test setup: Mobile rack For verifying burn, use this test setup: Boot Code Readiness Review

  3. “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

  4. 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

More Related