This article may be too technical for most readers to understand.(August 2021) |
Abbreviation | CAST-32A |
---|---|
Year started | 2014 |
Latest version | A November 2016 |
Organization | FAA |
Domain | Aviation |
Website | faa.gov |
CAST-32A, Multi-core Processors is a position paper, [1] by the Certification Authorities Software Team (CAST). It is not official guidance, but is considered informational by certification authorities such as the FAA and EASA. A key point is that Multi-core processor "interference can affect execution timing behavior, including worst case execution time (WCET)." [2]
The original document was published in 2014 by an "international group of certification and regulatory authority representatives." [3] The current revision A was released in 2016. "The Federal Aviation Administration (FAA) and European Aviation Safety Agency (EASA) worked with industry to quantify a set of requirements and guidance that should be met to certify and use multi-core processors in civil aviation, described e.g. in the FAA CAST-32A Position Paper and the EASA Use of MULticore proCessORs in airborne Systems (MULCORS) research report." [4] For applicants certifying under EASA, AMC 20-193 has now superseded CAST-32A since its release on 21 January 2022. It is expected that the FAA will release its Advisory Circular AC 20-193 guidance in 2023, which is expected to be almost identical to AMC 20-193. [5] [6]
One of the first mixed-criticality multicore avionics systems is expected to be certified sometime in 2020. [7] The objectives of the standard are applicable to software on multicore processors, including the operating system. [8] [9] However, the nature of the underlying processor hardware must be examined in detail to identify potential interference channels due to inter-core contention for shared resources. [10] Verification that multicore interference channels have been mitigated can be accomplished through the use of interference generators i.e. software tuned to create a heavy usage pattern on a shared resource. [11]
The paper presents ten objectives that must be met for Design Assurance Level (DAL) A or B. Six of the objectives apply for DAL C. The paper does not apply for DAL D or E. [1]
Objective | Applicable Design Assurance Levels |
---|---|
MCP Planning 1 | A, B, C |
MCP Resource Usage 1 | A, B, C |
MCP Resource Usage 2 | A, B |
MCP Planning 2 | A, B, C |
MCP Resource Usage 3 | A, B |
MCP Resource Usage 4 | A, B |
MCP Software 1 | A, B, C |
MCP Software 2 | A, B, C |
MCP Error Handling 1 | A, B |
MCP Accomplishment Summary 1 | A, B, C |
The Eclipse 500 is a very light jet (VLJ) originally produced by Eclipse Aviation of Albuquerque, New Mexico, United States. The company was founded in 1998 to develop the 1997 Williams V-Jet II demonstrator. The prototype first flew with Williams EJ22 turbofans on August 26, 2002. The engines were replaced by Pratt & Whitney Canada PW610Fs in 2004 and Eclipse Aviation won the Collier Trophy in February 2006 for the design. A provisional FAA type certification was received on 27 July 2006 and the first delivery occurred on 31 December 2006.
DO-178B, Software Considerations in Airborne Systems and Equipment Certification is a guideline dealing with the safety of safety-critical software used in certain airborne systems. It was jointly developed by the safety-critical working group RTCA SC-167 of the Radio Technical Commission for Aeronautics (RTCA) and WG-12 of the European Organisation for Civil Aviation Equipment (EUROCAE). RTCA published the document as RTCA/DO-178B, while EUROCAE published the document as ED-12B. Although technically a guideline, it was a de facto standard for developing avionics software systems until it was replaced in 2012 by DO-178C.
A hazard analysis is used as the first step in a process used to assess risk. The result of a hazard analysis is the identification of different types of hazards. A hazard is a potential condition and exists or not. It may, in single existence or in combination with other hazards and conditions, become an actual Functional Failure or Accident (Mishap). The way this exactly happens in one particular sequence is called a scenario. This scenario has a probability of occurrence. Often a system has many potential failure scenarios. It also is assigned a classification, based on the worst case severity of the end condition. Risk is the combination of probability and severity. Preliminary risk levels can be provided in the hazard analysis. The validation, more precise prediction (verification) and acceptance of risk is determined in the risk assessment (analysis). The main goal of both is to provide the best selection of means of controlling or eliminating the risk. The term is used in several engineering specialties, including avionics, food safety, occupational safety and health, process safety, reliability engineering.
ARP4761, Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment is an Aerospace Recommended Practice from SAE International. In conjunction with ARP4754, ARP4761 is used to demonstrate compliance with 14 CFR 25.1309 in the U.S. Federal Aviation Administration (FAA) airworthiness regulations for transport category aircraft, and also harmonized international airworthiness regulations such as European Aviation Safety Agency (EASA) CS–25.1309.
ARP4754, Aerospace Recommended Practice (ARP) ARP4754A, is a guideline from SAE International, dealing with the development processes which support certification of Aircraft systems, addressing "the complete aircraft development cycle, from systems requirements through systems verification." Revision A was released in December 2010. It was recognized by the FAA in AC 20-174 published November 2011. EUROCAE jointly issues the document as ED–79.
RTCA DO-254 / EUROCAE ED-80, Design Assurance Guidance for Airborne Electronic Hardware is a document providing guidance for the development of airborne electronic hardware, published by RTCA, Incorporated and EUROCAE. The DO-254/ED-80 standard was formally recognized by the FAA in 2005 via AC 20-152 as a means of compliance for the design assurance of electronic hardware in airborne systems. The guidance in this document is applicable, but not limited, to such electronic hardware items as
An electronic flight bag (EFB) is an electronic information management device that helps flight crews perform flight management tasks more easily and efficiently with less paper providing the reference material often found in the pilot's carry-on flight bag, including the flight-crew operating manual, navigational charts, etc. In addition, the EFB can host purpose-built software applications to automate other functions normally conducted by hand, such as take-off performance calculations. The EFB gets its name from the traditional pilot's flight bag, which is typically a heavy documents bag that pilots carry to the cockpit.
Integrated modular avionics (IMA) are real-time computer network airborne systems. This network consists of a number of computing modules capable of supporting numerous applications of differing criticality levels.
Lynx Software Technologies, Inc. is a San Jose, California software company founded in 1988. Lynx specializes in secure virtualization and open, reliable, certifiable real-time operating systems (RTOSes). Originally known as Lynx Real-Time Systems, the company changed its name to LynuxWorks in 2000 after acquiring, and merging with, ISDCorp, an embedded systems company with a strong Linux background. In May 2014, the company changed its name to Lynx Software Technologies.
ARINC 653 is a software specification for space and time partitioning in safety-critical avionics real-time operating systems (RTOS). It allows the hosting of multiple applications of different software levels on the same hardware in the context of an Integrated Modular Avionics architecture.
The enhanced avionics system is an integrated modular avionics suite and cockpit display system used on Dassault Falcon business jets since Falcon 900EX, and later used in other newer Falcon aircraft such as Falcon 2000EX and Falcon 7X.
DO-178C, Software Considerations in Airborne Systems and Equipment Certification is the primary document by which the certification authorities such as FAA, EASA and Transport Canada approve all commercial software-based aerospace systems. The document is published by RTCA, Incorporated, in a joint effort with EUROCAE, and replaces DO-178B. The new document is called DO-178C/ED-12C and was completed in November 2011 and approved by the RTCA in December 2011. It became available for sale and use in January 2012.
AC 25.1309–1 is an FAA Advisory Circular (AC) that identifies acceptable means for showing compliance with the airworthiness requirements of § 25.1309 of the Federal Aviation Regulations. Revision A was released in 1988. In 2002, work was done on Revision B, but it was not formally released; the result is the Rulemaking Advisory Committee-recommended revision B-Arsenal Draft (2002). The Arsenal Draft is "considered to exist as a relatively mature draft". The FAA and EASA have subsequently accepted proposals by type certificate applicants to use the Arsenal Draft on development programs.
The Advisory Circular AC 20-115( ), Airborne Software Development Assurance Using EUROCAE ED-12( ) and RTCA DO-178( ), identifies the RTCA published standard DO-178 as defining a suitable means for demonstrating compliance for the use of software within aircraft systems. The present revision D of the circular identifies ED-12/DO-178 Revision C as the active revision of that standard and particularly acknowledges the synchronization of ED-12 and DO-178 at that revision.
FAA Order 8110.105A, Simple and Complex Electronic Hardware Approval Guidance, supplements RTCA DO-254 by explaining how FAA aircraft certification staff can use that document "when working on certification projects". "The Order states specific topics of interest to the FAA that may go above and beyond content specific to DO-254." This order is recommended as a reference for developers applying under DO-254 for certification of electronic hardware designs, including those implemented in "custom micro-coded components".
The Boeing 737 MAX was initially certified in 2017 by the U.S. Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA). Global regulators grounded the plane in 2019 following fatal crashes of Lion Air Flight 610 and Ethiopian Airlines Flight 302. Both crashes were linked to the Maneuvering Characteristics Augmentation System (MCAS), a new automatic flight control feature. Investigations in both crashes determined that Boeing and the FAA favored cost-saving solutions, but ultimately produced a flawed design of the MCAS instead. The FAA's Organization Designation Authorization program, allowing manufacturers to act on its behalf, was also questioned for weakening its oversight of Boeing.
DO-297, Integrated Modular Avionics (IMA) Development Guidance and Certification Considerations is one of the primary document by which certification authorities such as the FAA and EASA approve Integrated Modular Avionics (IMA) systems for flight. The FAA Advisory Circular (AC) 20-170 refers to DO-297.
CAST-31, Technical Clarifications Identified for RTCA DO-254 / EUROCAE ED-80 is a Certification Authorities Software Team (CAST) Position Paper. It is an FAA publication that "does not constitute official policy or guidance from any of the authorities", but is provided for educational and informational purposes only for applicants for software and hardware certification.
The Certification Authorities Software Team (CAST) is an international group of aviation certification and regulatory authority representatives. The organization of has been a means of coordination among representatives from certification authorities in North and South America, Europe, and Asia, in particular, the FAA and EASA. The focus of the organization has been harmonization of Certification Authorities activities in part though clarification and improvement of the guidance provided by DO-178 and DO-254.
CAST-15, Merging High-Level and Low-Level Requirements is a Certification Authorities Software Team (CAST) Position Paper. It is an FAA publication that "does not constitute official policy or guidance from any of the authorities", but is provided to applicants for software and hardware certification for educational and informational purposes only.
{{cite book}}
: |journal=
ignored (help)