1. EPU load – same as SIU load except…
Procedure will be performed in building 33
Hardware involved:
Mobile computing rack
LAT Control Rack (a.k.a. VSC rack)
Target CPU
Additional EGSE (GASU, EM SIU) for burn verification
Software
All version information is contained in LAT-TD
Burn PBC V from FSW B0-6-1 into BAE750 SUROM
FSW B0-6-1 will be burned into ee1 (upper bank) of SIB
LICOS, L , used to upload FSW objects and monitor/control process
All software objects made available on linux computers in the mobile rack. Includes:
FSW distribution of uploadable objects from B0-6-1
LICOS L (new tag created specifically for EPUs)
All necessary scripts
January 11, 2005
Boot Code Readiness Review

2. Boot Code Readiness Review
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”
Test PBC by rebooting crate
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
January 11, 2005
Boot Code Readiness Review

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

4. Boot Code Readiness Review
References
LATDoc Number
Title
LAT-TD
Flight Crate Procedure for Burning EPU PBC into RAD750 SUROM
LAT-TD
Flight Crate Procedure for Burning SIU PBC into RAD750 SUROM
LAT-DS
GLAST Electronics Boxes, DAQ Electronics, SIU Box Assembly
LAT-TD
Procedure for Uploading Files to SIB EEPROMs over 1553
January 11, 2005
Boot Code Readiness Review