AFGS PAL Project
From Deos
Jump to navigationJump to search
Provide an initial and verified Deos Platform Abstraction Layer (PAL) as a means to support the AFGS_Program.
Description
The PAL has two spheres of influence:
- provides the Deos kernel with an interface to the "off chip" (i.e., non-CPU defined) hardware components (e.g., interrupt controllers, timers, etc.)
- implement AFGS product specific behaviors (e.g., execution rate monitor)
Tasks
Initial Budget: $114,808
YTD: $135,509
Current ETC: $0
Current EAC: $135,509
| Milestones | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| Initial Release | 18-APR-2006 | 18-APR-2006 | 18-APR-2006 | 100% |
| [1] Performance Enhanced Release | 14-FEB-2007 | 26-FEB-2007 | 26-FEB-2007 | 100% |
| [2] Full Functionality Release | 10-APR-2007 | 24-APR-2007 | 22-APR-2007 | 100% |
| [3] Verified Release | 05-JUN-2007 | 08-AUG-2007 | 10-AUG-2007 | 100% |
Tasks for Milestone [3] Verified Release
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 3.0 Formalize Requirements | 2.4 | Mike Horgan & Gary Kindorf | None | 80 | 129 | 129 | 0 |
| 3.1 Software life cycle audit #1 (Requirements) | 3.0 | Kelly Leonard | None | 16 | 6 | 6 | 0 |
| 3.2 Requirements review | 2.1 | Bill Cronk | None | 60 | 10 | 10 | 0 |
| 3.3 Test Case Developement | 2.1 | Bill Cronk | None | 40 | 24 | 24 | 0 |
| 3.4 Test Procedure Developement | 2.1, 2.3 | Mike Horgan & Bill Cronk | Software Verification Environment & Random Hardware States | 120 | 138 | 138 | 0 |
| 3.5 Software life cycle audit #2 (code and tests) | 3.4 | Kelly Leonard | None | 16 | 11 | 11 | 0 |
| 3.6 Code review | 3.2 | Bill Cronk | None | 80 | 40 | 40 | 0 |
| 3.7 Test Case Review | 3.2, 3.3 | Mike Horgan | None | 32 | 24 | 24 | 0 |
| 3.8 Test Procedure Review | 3.4, 3.7 | Rob Hubbard & Mike Horgan | None | 60 | 60 | 60 | 0 |
| 3.9 Software life cycle audit #3 | 3.8 | John Riedmann | None | 16 | 9 | 9 | 0 |
| 3.10 Requirements coverage analysis | 3.6, 3.7 | Bill Cronk | None | 8 | 8 | 8 | 0 |
| 3.11 Conformity inspection - SQA build Witness | 3.8, 3.10 | John Riedmann | None | 8 | 8 | 8 | 0 |
| 3.12 SCAT/ABC qualification | 3.8 | Bill Cronk | None | 8 | 8 | 8 | 0 |
| 3.13 Integration review | 3.11, 3.12 | Bill Cronk John Riedmann | None | 8 | 8 | 8 | 0 |
| 3.14 Run for score, including SQA witnessing, and test results review | 3.13 | Bill CronkMike HorganJohn Riedmann | None | 8 | 8 | 8 | 0 |
| 3.15 Structural coverage analysis | 3.14 | Rob Hubbard | None | 8 | 8 | 8 | 0 |
| 3.16 Verification audit | 3.15 | John Riedmann | None | 8 | 10 | 10 | 0 |
| 3.17 Certification documents: SAS, SLCECI, SCI | 3.15 | Mike Horgan | None | 40 | 20 | 20 | 0 |
| 3.18 Population of certification archive (PCA) | 3.17 | Mike Horgan | None | 8 | 8 | 8 | 0 |
| 3.19 Software conformity audit | 3.18 | John Riedmann | None | 8 | 7 | 7 | 0 |
| Totals | 632 | 537 | 537 | 0 | |||
Resolved Issues
Jitter
Using timer accuracy numbers from the 6300ESB spec. for the jitter value.
Software Verification Environment
The Boot and PAL have abandoned the emulator method and created a working software only environment in which to verify Boot and PAL. Test procedure development is now progressing. Refer to Boot - Software Verification Environment for history.
Mike's Availability
- Current Tasking
- Mike Horgan
- Boot/Pal/Application Integration Support with ALT
- Pal Code/Requirements Development
- Gary Kindorf
- Pal Code Development and Requirements Capture
- Rob Hubbard (Belcan/Kutta)
- Using the current requirements document in subversion (copied from PDMC project), create the AFGS PAL requirements shell document that contains references to the higher level requirements in deos-pal-software-requirements.
- Capture and document platform specific requirements in the AFGS Pal.
- Jingsong Pan (Belcan/Kutta)
- Work with Stephen Smith to set up emulators/targets for remote access.
- Once the emulators are in place, set up a test infrastructure for boot/pal verification through the emulators.
422/429 Interrupts
No root cause has been found as to why we have been unable to generate 422 or 429 interrupts. Perhaps as a consequence, the current polling implementation for 422/429 has been deemed acceptable.
