NGIMS-FSW-34-WOA Work Order Authorizations (WOAs) for NGIMS Flight Software Build, Test, and Release Procedures Prepared By: Michael Paulkovich, Lead NGIMS Software Engineer for Hasso B. Niemann, Paul Mahaffy, NASA/GSFC Code 915 Laboratory for Planetary Atmospheres January 28, 2002 Rev 2 DOCUMENT CHANGE HISTORY revision Date Change 1 Feb 3 02 First CM version. Fix some typos. Add WOA Log. PURPOSE This document provides the set of WOAs for all phases of NGIMS Flight Software Build Procedures. Detailed explanations of the process and each event in the WOAs are provided in NGIMS-FSW-52-BP, "Flight Software Build Procedures." CONTENTS: WOA# Task FSW-1-xx Starting new FSW release FSW-2-xx Developing new FSW feature FSW-3-xx Development and test cycle FSW-4-xx Clean release for new load image FSW-5-xx Patching Current Version FSW-6-xx Generating Firmware Image FSW-7-xx Generating Alt Boot Image FSW-8-xx Uploading Alt Boot Image Numbering. To discriminate between Flight Software WOAs and others in the department, these are prefixed with "FSW." Then they are given a "Category Number" 1-8 (as above), followed by a sequence number starting with 01. For example, the first WOA for Developing new FSW feature is FSW-2-01. WOA LOG All NGIMS FSW WOAs are catalogued in the table below. WOA# WOA Date Task Related Documentation Generated with Task Document Name Doc %Compl FSW-1-01 FSW-2-01 FSW-3-01 07/2001 Starting new FSW release Develop new FSW feature: Adaptive Development and test cycle (Refer to CM Plan and ISO9000 Doc) 100% FSW-4-01 FSW-6-01 09/08/2001 09/08/2001 Clean rel. for new load image, v3.6.00 Generating Firmware Image, v3.6.00 GSFC/NGIMS-FSW-30: RDD, v3.6.00 GSFC/NGIMS-FSW-31: Test Report, v3.6.00 GSFC/NGIMS-FSW-32: Delivery Report, v3.6.00 GSFC/NGIMS-FSW-33: Margins Analysis v3.6.00 GSFC/NGIMS-FSW-28: Memory Map v3.6.00 100% 100% 100% 90% 50% E-005 10/12/2001 Burning flight PROMs n/a FSW-6-02 FSW-7-01 FSW-8-01 11/07/2001 11/07/2001 11/07/2001 Generating Firmware Image, v3.7.07 Generating Alt Boot Image, v3.7.07 Uploading Alt Boot Image, v3.7.07 GSFC/NGIMS-FSW-38: RDD, v3.7.07 GSFC/NGIMS-FSW-39: Test Report, v3.7.07 GSFC/NGIMS-FSW-40: Delivery Report, v3.7.07 GSFC/NGIMS-FSW-41: Margins Analysis v3.7.07 GSFC/NGIMS-FSW-44: Memory Map, v3.7.07 100% 100% 100% 50% 50% FSW-5-01 FSW-7-02 FSW-8-02 12/21/2001 12/21/2001 12/21/2001 Patching Current Version, v3.7.08 Generating Alt Boot Image, v3.7.08 Uploading Alt Boot Image, v3.7.08 GSFC/NGIMS-FSW-45: Test Report, v3.7.08 GSFC/NGIMS-FSW-46: Delivery Report, v3.7.08 GSFC/NGIMS-FSW-47: RDD, v3.7.08 100% 100% 100% FSW-5-02 FSW-7-03 FSW-8-02 01/07/2002 01/07/2002 01/07/2002 Patching Current Version, v3.7.09 Generating Alt Boot Image, v3.7.09 Uploading Alt Boot Image, v3.7.09 GSFC/NGIMS-FSW-48: Test Report, v3.7.09 GSFC/NGIMS-FSW-49: Delivery Report, v3.7.09 GSFC/NGIMS-FSW-50: RDD, v3.7.09 100% 100% 100% Work Order Authorization (WOA) and Continuation Sheet Starting new FSW release 1. WOA Title Starting new FSW release 2. WOA No. FSW-1-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description NGIMS FSW 8. Item Type 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description CVS Checkout for new release; build, verify rebuild properties. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 12a. WOA Plan Approval - Sig / Code / Date 12b. WOA Close-out Approval - Sig / Code / Date 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 1. CVS Checkout Previous Version Number: __.__.__ __ New Version Number: __.__.__ __ 2. Re-establish Executable File Attributes 3. Change version numbers in project, library. setprj line: __________________ setlib line: __________________ 4. Set new version number in "intvec" files intvec_firmware.asm: __ __ __ __ intvec.asm: : __ __ __ __ 5. Create Tartan Ada library 6. Make all 6.1 Verify rebuild properties Previous build file size: _____________ Current build file size: _____________ Verify No Diffs: Y___ N___ Work Order Authorization (WOA) and Continuation Sheet Developing new feature 1. WOA Title Developing new feature 2. WOA No. FSW-2-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description Feature: ______________________ 8. Item Type Flight Software 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description This task is to be performed when multiple programmers are involved in code enhancements, and a new feature (e.g. S/C Potential Compensation) is desired to be developed by one team independently, eventually to be merged in with all teams' efforts. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 11. Special Requirements/Support N/A 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 1. Create CVS branch branch name: ________________ 2. Checkout working directory 3. Once working, merge back into main CVS branch Work Order Authorization (WOA) and Continuation Sheet Development and test cycle 1. WOA Title Development and test cycle 2. WOA No. FSW-3-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description Develop, test, iterate, V&V, Approve for release task 8. Item Type Flight Software 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description This task is to be performed after a version has been released, and work is to continue on a new compilation of the source. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-01 (FSW Management Plan) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 11. Special Requirements/Support N/A 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 1. Recompile changes, do first link 2. Get the AMB addresses 3. Relink 4. Programmer tests 5. Code review and CVS check-in 6. Validation tests (see NGIMS-FSW-01, §2.3) V&V 1: ______________________ V&V 2: ______________________ Baseline Test Work Order Authorization (WOA) and Continuation Sheet Clean release for new load image 1. WOA Title Clean release for new load image 2. WOA No. FSW-4-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description NGIMS FSW 8. Item Type Flight Software 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description This task is to be performed when programmers are satisfied with a new recompiled version of the source code. Clean object libraries, rebuild code, do CM steps, and make new firmware or Alt Boot image. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 11. Special Requirements/Support N/A 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 0. Increment Version 1. CVS-review & clean-up 2. Build adascope version 2.1 Clean library 2.2 make all 3. Get AMB addresses 4. Final adascope link 5. Build firmware version PROM checksum: __ __ __ __ 6. Final firmware link 7. cvs_review & tag from CVS menu CVS Tag: build _ _ _ . 8. Make PROMs Actual PROM checksum: __ __ __ __ (If not making PROMs, but need Alt Boot image see WOA-FSW-7, then skip down to step 9) 9. Test 10. Build Reference Copy New version numbers in project, library: setprj line: __________________ setlib line: __________________ 11. createlib.cmd Do Events 2.2 through 9? compare *.i16 -- should be no differences. 12. Burn new Flight PROMs Work Order Authorization (WOA) and Continuation Sheet Patching Current Version 1. WOA Title Patching Current Version 2. WOA No. FSW-5-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description NGIMS FSW 8. Item Type Flight Software 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description This task is to be performed implement a software change that is not too "major" by modifying the currently compiled release of the software. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 11. Special Requirements/Support N/A 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 1. Analyze area to patch using Adascope version 2. Write patch for Adascope version Patch Number: _______________________ 3. Test patch with Adascope version 4. Analyze and patch using Load-Image version 5. Write and test patch as TC Patch script 6. Write patch as addendum to Alt Boot file FSW Version in EEPROM: __ __ __ __ FSW Version in RAM: __ __ __ __ EEPROM checksum: __ __ __ __ 7. Test addendum to Alt Boot file Work Order Authorization (WOA) and Continuation Sheet Generating Firmware Image 1. WOA Title Generating Firmware Image 2. WOA No. FSW-6-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description NGIMS FSW 8. Item Type Flight Software 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description This task is to be performed when PROMs with the new firmware are needed. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 11. Special Requirements/Support N/A 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 1. Generate the Adascope build 2. Final firmware link 3. cvs_review & tag. TAG: ___________ 4. Make PROMs New Version# at FFFE: __ __ __ __ New Checksum at FFFF: __ __ __ __ 5. Test 6. When done testing 7. Burn new Flight PROMs Work Order Authorization (WOA) and Continuation Sheet Generating Alt Boot Image 1. WOA Title Generating Alt Boot Image 2. WOA No. FSW-7-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description NGIMS FSW 8. Item Type Flight Software 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description This task is to be run when an Alt Boot image is to be generated for upload to EEPROM. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 11. Special Requirements/Support N/A 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 1. Build Alt Boot Image 2. Version, reboot count & checksum Version: __ __ __ __ EEPROM Checksum: __ __ __ __ Work Order Authorization (WOA) and Continuation Sheet Uploading Alt Boot Image 1. WOA Title Uploading Alt Boot Image 2. WOA No. FSW-8-__ __ 4. Open date Originator/Code/Phone 5. Close date 6. Project Contour NGIMS 7. Item Name/Description NGIMS FSW 8. Item Type Flight Software 8a. Item Configuration# / Rev FSW version: __.__.__ __ 9. Description This task is to be run when an Alt Boot image is to be uploaded to EEPROM. 10. Required Documents NGIMS-FSW-52-BP (Build Procedures) NGIMS-FSW-51 (Instrument Software Configuration Management Plan) 11. Special Requirements/Support N/A 11. Special Requirements/Support N/A 13. Event#. 14. Resp Code 15. Event Description Signature and Date 18. NCR# 19. Prod Dispos. Compl Date 16. Perf By 17. Insp by 1. Get Alt Boot script. Ensure "zero fill" of unused EEPROM addresses is included in script. 2. Test upload on breadboard if not already tested. 3. Obtain approval from Instrument Manager and Spacecraft Project management to modify instrument FSW / EEPROM. 4. Ensure that the Alt Boot script for the current (soon to be "previous") version in Flight EEPROM is available. Test that version with the breadboard FC. 5. Upload new Alt Boot image to Flight EEPROM and test. 6. If failed test, reverse the upload by uploading the "previous" version to Flight EEPROM. 7. If passed test, update the Flight Instrument Log and appropriate documents accordingly.