ARINC 664
2120-314-633 "AFDX" tasks
Development of the ARINC 664 components for the Hosmer program, corresponding to the Rockwell Collins version 6 hardware.
Description
- Development of the library device driver to level A from Rockwell Collins source code.
- Modifications as needed to the legacy AFDX driver process
- Modifications as needed to the legacy AFDX tools
Lab Setup
There is an ARINC 664 board installed in Warhorse. It was purchased from Avionics Interface Technologies, and is a PCI-C664. The vendor provides an SDK that includes a Windows driver for the board, as well as an API DLL that we are accessing via Python scripts. The SDK has been archived at https://deos.ddci.com/svn/DDCI/maintainer-tools/arinc-664/pci-c664-bsp/. The board is compatible with the A615A-LDR software, for Target Data Loader, that was purchased from the same vendor. Note that the vendor has a later version of this board, the BSP for which is not compatible with our board. The board is not recognized as a network interface by Wireshark. The vendor provides tooling for their newer version of the board that can be used to capture packets in the PCAP format, but the tooling is not compatible with our board. They may provide a GUI tool for purchase that can be used to monitor the 664 bus, but we have set up a local network to monitor the bus from the host machines that correspond to the targets that can transmit and receive 664 packets. We can use conventional network cards to monitor 664 traffic because 664 uses Ethernet as the underlying protocol.
Hardware related Issues
The following affects PerformEsPost(), InterruptSignalTest() & ParityErrorTest() API functions:
- When a memory write is performed to Force SERR(BAR0.FS) in POST mode, BAR0.STS/CMD.SSE should be set but its not. [EP8343M platform]
- After forcing a system error with Force SERR(BAR0.FS) register. BAR0.STS/CMD.SSE is set, but it doesn't get cleared when writing a 1 in it. [Hosmer platform]
- [Edit 09-02-2013]: BAR0.STS/CMD should be written using CONFIG_ADDR & CONFIG_DATA registers from PCI configuration space. Library has been updated to account for this and test is now working as expected.
- After forcing a parity error with Force PERR(BAR0.FP) register. BAR0.STS/CMD.DPE is set, but it doesn't get cleared when writing a 1 in it. [Hosmer and EP8343M platform]
- [Edit 09-02-2013]: BAR0.STS/CMD should be written using CONFIG_ADDR & CONFIG_DATA registers from PCI configuration space. Library has been updated to account for this and test is now working as expected.
Questions/Discussion
About AFDX-Driver-CVT Qualification package:
- Tool successfully runs in the Elbert Windows Shell
- Tool fails in the Elbert bash shell
- Refer to https://deos.ddci.com/bugzilla/show_bug.cgi?id=8326
$ test-afdx-driver-cvt.py -v -d . Warning: Specified report directory (.) exists and will be overwritten Regression test is in progress. 171 test case functions to execute .afdx-driver-cvt Traceback (most recent call last): File "afdx-driver-cvt.py", line 368, in ? File "afdx-driver-cvt.py", line 202, in main File "afdx-driver-cvt.py", line 340, in versionFromFile IOError: [Errno 2] No such file or directory: '/tmp/afdxConfig-little.cfg' Traceback (most recent call last): File "/desk/bin/test-afdx-driver-cvt.py", line 95, in <module> main() File "/desk/bin/test-afdx-driver-cvt.py", line 92, in main common_regression.main() File "C:\elbert\desk/tests/test-afdx-driver-cvt/bin/common_regression.py", line 230, in main skipRegenStrings).run() File "C:\elbert\desk/tests/test-afdx-driver-cvt/bin/common_regression.py", line 762, in run eval(s)(self) File "C:\elbert\desk/tests/test-afdx-driver-cvt/bin/afdxDriverTestProcedures.py", line 136, in test1 testUtilObj.executeTestCase() File "C:\elbert\desk/tests/test-afdx-driver-cvt/bin/common_regression.py", line 546, in executeTestCase raise NameError, 'No CVT Tool In Path' # Crash the suite -- cannot do anything without the CVT NameError: No CVT Tool In Path
About ARINC664-Library-CVT:
- Tool fails due to "Known problems" as documented in the release-notes. It was agreed to show all failures so that the Hosmer Team takes their desired actions with the support of Rockwell Collins. Pending to create PCR to track this.
- [Edit 09-02-2013]: The Rockwell Collins esbin tool is a qualified tool. The version we are delivering with our DDS distribution, esbin 4.0.1, is qualified. UTAS will rely on this qualification for the verification of the binary configuration file that otherwise would have been provided by the CVT. This makes the CVT unnecessary, as agreed on teleconference held on July 26th, 2013, with UTAS, Rockwell Collins, and DDC-I/Avionyx.
Status and Meeting Minutes
- https://ddci.zapto.org/svn/DDCI/products/arinc664/library/program-management/
- mainline afdx-driver review status
- mainline arinc664-library review status
AFDX Driver Process Activities
| Description | Assignee | Status | Remarks |
| Requirements development | Done | ||
| Requirements review | Done | ||
| Code development | Done | ||
| Code review | Done | ||
| Test case development | Done | ||
| Test case review | Done | ||
| Test procedure development | Done | ||
| Test procedure review | Done | ||
| Software lifecycle audit | KL | Done | |
| Requirements coverage analysis, including Traceaid qualification | CC | Done | |
| Conformity inspection - SQA build witness | CC/KL | Done | |
| ABC qualification | CC | Done | |
| Integration review, including compiler assessment | CC | Done | |
| Run for score, including SQA witnessing and test results review | CC/KL | Done | |
| Structural coverage analysis | CC | Done | |
| Verification audit | KL | Done | |
| Open problem reports list | CC | Done | |
| SAS, SLCECI, SCI | CC | Done | |
| Population of certification archive | CC | Done | |
| Software conformity audit | KL | Done | |
| Update latest-verified link on FTP server | CC | Done |
ARINC 664 Library Activities
| Description | Assignee | Status | Remarks |
| Requirements development | Done | ||
| Requirements review | Done | ||
| Code development | Done | ||
| Code review | GK | Done | |
| Test case development | Done | ||
| Test case review | Done | ||
| Test procedure development | Done | ||
| Test procedure review | MH/GK | Done | |
| Software lifecycle audit | KL | Done | |
| Requirements coverage analysis, including Traceaid qualification | MH | Done | |
| Conformity inspection - SQA build witness | MH/KL | Done | |
| ABC qualification | MH | Done | |
| Integration review, including compiler assessment | MH/KL | Done | |
| Run for score, including SQA witnessing and test results review | MH/KL | Done | |
| Structural coverage analysis | MH | Done | |
| Verification audit | KL | Done | |
| Open problem reports list | MH | Done | |
| SAS, SLCECI, SCI | MH | Done | |
| Population of certification archive | MH | Done | |
| Software conformity audit | KL | Done | |
| Update latest-verified link on FTP server | MH | Done |
ARINC 664 Library CVT Activities
| Description | Assignee | Status | Remarks |
| TQD - General | Done | ||
| TQD - Operational requirements | Done | ||
| TQD - Operational environment | Done | ||
| TQD - User information | Done | ||
| TQD - Verification plan | Done | ||
| Code development | Done | See Questions/Discussion | |
| Test procedure development | Done |
