Original FAA page; extracted words support search. Text reflow has not been reviewed.

Extracted text for finding words
This extraction supports search. Read the original page for complete notation and layout.
10/7/22 AC 20-152A
• The row corresponding to 10.2.2, “Hardware Design Standard” in Table A-1 should
also indicate HC2 for Level C. HDL Coding Standards are part of the Hardware
Design Standards.
• The row corresponding to 10.3.2.2 “Detailed Design Data” in Table A-1 should
indicate HC1 for Levels A, B, and C.
• The row corresponding to 10.4.2 “Hardware Review and Analysis Procedures” in
Table A-1 should also indicate HC2 for Level C to be consistent with row 10.4.3.
• The Top-Level drawing referenced in ED-80/DO-254, Appendix A, corresponds to
a Hardware Configuration Index (HCI) document. The HCI document completely
identifies the hardware configuration, the embedded logic, and the development life
cycle data. To support consistent and accurate replication of the custom device
(ED-80/DO-254, Section 7.1), the Top-Level Drawing includes the hardware life
cycle environment or refers to a Hardware Environment Configuration Index
(HECI) document.
5.11 Use of COTS IP in Custom Device Development
Section 5.11 addresses COTS IP that is instantiated within FPGAs/PLDs/ASICs during
the development of the custom device.
This section addresses COTS IP and its integration within custom devices and describes
objectives to support the demonstration of compliance with the applicable airworthiness
regulations for the hardware aspects of airborne systems and equipment certification.
Section 5.11.2, on “Applicability to COTS IP,” identifies COTS IP that are within the
scope of Section 5.11.
5.11.1 Background
IP refers to design functions (design modules or functional blocks, including IP
libraries) used to design and implement a part of or a complete custom device such as a
PLD, FPGA, or ASIC. IP is considered to be commercial-off-the-shelf intellectual
property, i.e., “COTS IP,” when it is a commercially available function, used by a
number of different users, in a variety of applications and installations. Custom IP,
developed for a few specific aircraft equipment, is not considered to be COTS IP.
COTS IP are available in various source formats. COTS IP are categorized as Soft IP,
Firm IP, or Hard IP based on the stage in the custom device design flow where the IP is
instantiated. A function can be a combination of source formats and each part needs to
be addressed. Definitions for Soft IP, Firm IP, and Hard IP can be found in the
Appendix A Glossary.
Figure 1 shows a “simplified” design flow of a PLD, FPGA, or ASIC, and where Soft
IP, Firm IP, and Hard IP are located in the design flow.
12