Stella BSP Project
This is a new Deos Board Support Package (BSP) based off of a previous Stella baseline.
Stella has altered their platform hardware from GRB-0020-1000 to GRB-0030-1000. The most likely changes are to the previous baseline's Deos Boot and PAL components.
Overview
The Certifiable Compact Dual Frequency receiver (CCPDF) provides reliable navigation information in conformance with aeronautical standards. It is a GNSS OEM sensor card compliant to the DO-229D standard. The certification authority for this project is the United States Federal Aviation Administration (FAA), which is responsible for the Technical Standard Orders (TSO) for airborne navigation sensors using Global Positioning System (GPS), augmented by the Satellite Based Augmentation System (SBAS).
A CCPDF customer is the third party system that commands the receiver and/or uses its results. This could be a host card that physically mates with the receiver, or it could be a system that is connected through an external RS232/RS422 connection, or that is connected using one of the other connections. Thus, the “user” is not the pilot, but an electronic system that is interacting with the receiver. That system may or may not provide certain controls to the pilot. For instance, although the user can command the receiver to exclude satellites, this does not imply that the pilot can do so, merely that the navigation software driving the receiver can do so.
Preconditions
- The customer provides us with a GRB-0030-1000 development board and power supply.
- Ethernet is available
- JTAG is available
- Watchdogs are disabled
Effort Assumptions
- The only changes the customer desires is to the Stella BSP. All other software remains the same.
- A Denali development environment will be trivially obtained by installing per the previous baseline's run-for-score instructions.
- Configuration component changes will be zero, or too small to worry about.
- The DDS distribution will be assembled by starting with the previously shipped DDS and patching in the updated BSP packages.
Effort Estimate Summary
- Note To convert effort estimates in hours to calendar days, use this formula:
days = task_estimate_hours * 0.5
Rationale: An Engineer's time-on-task will likely be no higher than 25%. That is, it will take him 4 times longer to complete when measured in calendar time. We also assume each calendar day has 8 working hours available. Thus, if an Engineer is given a task that is estimated to require 2 hours of effort, it will require 1 calendar day to complete.
| Task | Estimate (Hours) | Remarks |
| Update and Verify Boot | 256 | |
| Update and Verify PAL | 163 | |
| DDS Resurrection and Integration Testing | 24 | Relevant DDS is DDS_20120110_amber_denali_heartos |
Boot Component
| Description | Assignee | Status | Estimate (Hours) | Remarks |
| Requirements Development | TBD | Pending | 40 | |
| Requirements Review | TBD | Pending | 10 | |
| Code Development | TBD | Pending | 80 | |
| Code Review | TBD | Pending | 10 | |
| Test Case Development | TBD | Pending | 10 | |
| Test Case Review | TBD | Pending | 5 | |
| Test Procedure Development | TBD | Pending | 20 | |
| Test Procedure Review | TBD | Pending | 10 | |
| Executable Object Code Analysis | TBD | Pending | 4 | |
| Software Lifecycle Audit | SQA | Pending | 8 | |
| Document Build and Test Environments | TBD | Pending | 1 | |
| Requirements Coverage Analysis, including Traceaid Qualification | TBD | Pending | 4 | |
| Compiler Assessment | TBD | Pending | 4 | |
| ABC Tool Qualification | TBD | Pending | 4 | |
| Structural Coverage Analysis | TBD | Pending | 8 | |
| Conformity Inspection - SQA Build Witness | SQA | Pending | 2 | |
| Integration Review | TBD | Pending | 4 | |
| Run for Score, including SQA Witnessing, and Test Results Review | TBD | Pending | 2 | |
| Verification Audit | SQA | Pending | 4 | |
| Open Problem Reports List | TBD | Pending | 4 | |
| Report Document Development (SLCECI, SCI, SAS) | TBD | Pending | 8 | |
| Report Document Review | TBD | Pending | 2 | |
| Population of Certification Archive (PCA) | TBD | Pending | 8 | |
| Software Conformity Audit | SQA | Pending | 4 |
PAL Component
| Description | Assignee | Status | Estimate (Hours) | Remarks |
| Requirements Development | TBD | Pending | 20 | |
| Requirements Review | TBD | Pending | 5 | |
| Code Development | TBD | Pending | 40 | |
| Code Review | TBD | Pending | 5 | |
| Test Case Development | TBD | Pending | 5 | |
| Test Case Review | TBD | Pending | 2 | |
| Test Procedure Development | TBD | Pending | 10 | |
| Test Procedure Review | TBD | Pending | 5 | |
| Executable Object Code Analysis | TBD | Pending | 4 | |
| Software Lifecycle Audit | SQA | Pending | 8 | |
| Document Build and Test Environments | TBD | Pending | 1 | |
| Requirements Coverage Analysis, including Traceaid Qualification | TBD | Pending | 4 | |
| Compiler Assessment | TBD | Pending | 4 | |
| ABC Tool Qualification | TBD | Pending | 4 | |
| Structural Coverage Analysis | TBD | Pending | 8 | |
| Conformity Inspection - SQA Build Witness | SQA | Pending | 2 | |
| Integration Review | TBD | Pending | 4 | |
| Run for Score, including SQA Witnessing, and Test Results Review | TBD | Pending | 2 | |
| Verification Audit | SQA | Pending | 4 | |
| Open Problem Reports List | TBD | Pending | 4 | |
| Report Document Development (SLCECI, SCI, SAS) | TBD | Pending | 8 | |
| Report Document Review | TBD | Pending | 2 | |
| Population of Certification Archive (PCA) | TBD | Pending | 8 | |
| Software Conformity Audit | SQA | Pending | 4 |
References
Notes
These are some semi-random scribbles recorded from email conversations.
- Regarding when hardware will be available.
Matt: Has the engineering team there tried to run the existing software on the new board?
Patricia: No, this is not yet done, as the board design is finished now and prototyping is just
starting. The board can be sent to you around mid May.
- Regarding being able to cross check our Boot setting with Kozio's as well as verify that our transition logic works.
Matt: On the prior project, the Deos Boot Loader had the ability to transition to "Kozio" software.
Will this still be the case, and if so, would it be possible to get a copy of the Kozio image?
Patricia: This will still be the case. Kozio image can be provided.
- Regarding updated technical documents:
Matt: Have any other documents changed as a side-effect of these changes? For example, we were also using these
documents to help us implement the Deos Boot and PAL software:
ccpdf-ydd-129-system-architecture-design.docx
ccpdf-yrd-0025-system-requirements-document v1.1.pdf
Patricia: These documents are not affected by the HW redesign. But the documents are updated during the project.
Updated documents are attached. YDD-129 does not exist (any more). But I attached the YDD-53 and HWSPEC-100
that should provide you with the necessary information.
- Regarding the PAL's Ethernet initialization requirements:
Matt: The new hardware design indicates TSEC1 is no longer used and TSEC0 used only in certain installation scenarios.
Is it safe to assume that our Deos Boot/PAL software can continue to initialize these devices?
Patricia: These devices are also disabled on the current hardware. The double check by the HW Engineer
confirmed that there is no change needed for the DEOS Boot/PAL for TSEC1 and TSEC2.
- Regarding requirements applicability then versus now:
Matt: We want to note that our previous delivery *did not* implement any of the implied or explicit requirements in these sections: 3.2.6 "GPIO" 6.3.3 "Normal Operation" 6.3.4 "Monitoring the VCO status and re-initializing the VCO selection" 6.6 "AFE LNA power-up" 6.7 "Front-end ADCs" Can we assume these sections can be ignored as a source for Deos Boot/PAL requirements? Patricia: The scope of the Boot Loader (or PAL) has not changed, so the chapters which are ignored before can still be ignored.
