ARINC 665-3-2005 LOADABLE SOFTWARE STANDARDS (1999 Includes Supplements 1-3)《可受载软件标准1999包括附录1到3》.pdf

《ARINC 665-3-2005 LOADABLE SOFTWARE STANDARDS (1999 Includes Supplements 1-3)《可受载软件标准1999包括附录1到3》.pdf》由会员分享，可在线阅读，更多相关《ARINC 665-3-2005 LOADABLE SOFTWARE STANDARDS (1999 Includes Supplements 1-3)《可受载软件标准1999包括附录1到3》.pdf（138页珍藏版）》请在麦多课文档分享上搜索。

1、 AN DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401-7435 LOADABLE SOFTWARE STANDARDS ARINC REPORT 665-3 PUBLISHED: August 12, 2005 This document is based on material submitted by various participants durin

2、g the drafting process. Neither AEEC nor ARINC has made any determination whether these materials could be subject to valid claims of patent, copyright or other proprietary rights by third parties, and no representation or warranty, express or implied, is made in this regard. Any use of or reliance

3、on this document shall constitute an acceptance thereof “as is” and be subject to this disclaimer. 2005 BY AERONAUTICAL RADIO, INC. 2551 RIVA ROAD ANNAPOLIS, MARYLAND 21401-7435 USA Prepared by the Airlines Electronic Engineering Committee Report 665 Adopted by the Airlines Electronic Engineering Co

4、mmittee September 22, 1999 Summary of Document Supplements Supplement Adoption Date Published Report 665-1 November 14, 2000 January 12, 2001 Report 665-2 August 23, 2002 August 30, 2002 Report 665-3 April 26, 2005 August 12, 2005 A description of the changes introduced by each supplement is include

5、d on Goldenrod paper at the end of this document. ARINC REPORT 665-3 LOADABLE SOFTWARE STANDARDS Published: August 12, 2005ii FOREWORD Aeronautical Radio, Inc., the AEEC, and ARINC Standards Aeronautical Radio, Inc. (ARINC) was incorporated in 1929 by four fledgling airlines in the United States as

6、a privately-owned company dedicated to serving the communications needs of the air transport industry. Today, the major U.S. airlines remain the Companys principal shareholders. Other shareholders include a number of non-U.S. airlines and other aircraft operators. ARINC sponsors aviation industry co

7、mmittees and participates in related industry activities that benefit aviation at large by providing technical leadership and guidance and frequency management. These activities directly support airline goals: promote safety, efficiency, regularity, and cost-effectiveness in aircraft operations. The

8、 Airlines Electronic Engineering Committee (AEEC) is an international body of airline technical professionals that leads the development of technical standards for airborne electronic equipment-including avionics and in-flight entertainment equipment-used in commercial, military, and business aviati

9、on. The AEEC establishes consensus-based, voluntary form, fit, function, and interface standards that are published by ARINC and are known as ARINC Standards. The use of ARINC Standards results in substantial benefits to airlines by allowing avionics interchangeability and commonality and reducing a

10、vionics cost by promoting competition. There are three classes of ARINC Standards: a) ARINC Characteristics Define the form, fit, function, and interfaces of avionics and other airline electronic equipment. ARINC Characteristics indicate to prospective manufacturers of airline electronic equipment t

11、he considered and coordinated opinion of the airline technical community concerning the requisites of new equipment including standardized physical and electrical characteristics to foster interchangeability and competition. b) ARINC Specifications Are principally used to define either the physical

12、packaging or mounting of avionics equipment, data communication standards, or a high-level computer language. c) ARINC Reports Provide guidelines or general information found by the airlines to be good practices, often related to avionics maintenance and support. The release of an ARINC Standard doe

13、s not obligate any airline or ARINC to purchase equipment so described, nor does it establish or indicate recognition or the existence of an operational requirement for such equipment, nor does it constitute endorsement of any manufacturers product designed or built to meet the ARINC Standard. In or

14、der to facilitate the continuous product improvement of this ARINC Standard, two items are included in the back of this volume: An Errata Report solicits any corrections to the text or diagrams in this ARINC Standard. An ARINC IA Project Initiation/Modification (APIM) form solicits any recommendatio

15、ns for addition of substantive material to this volume which would be the subject of a new Supplement. ARINC REPORT 665 TABLE OF CONTENTS iii 1.0 INTRODUCTION. 1 1.1 Purpose 1 1.2 Applicability. 1 1.3 Document Conventions. 1 1.3.1 Terminology 1 1.3.2 Field Formats . 1 1.3.3 Data Type. 2 1.4 File For

16、mat Evolution 2 1.4.1 File Format Version Definition. 2 1.4.2 File Expansion Points . 3 1.4.3 Support Tools and Loaders 3 1.4.4 Pointer Field Definition 3 1.5 Target Hardware ID Definition. 4 1.6 Electronic Distribution . 5 2.0 LOADABLE SOFTWARE PARTS . 6 2.1 Software Load PN . 6 2.1.1 Software Load

17、 PN Format 6 2.1.2 Manufacturers Code Assignment. 7 2.1.3 Check Characters in the Software PN 8 2.1.4 Commercial Software . 8 2.2 Software Load Content and Format. 8 2.2.1 Software Load Structure. 8 2.2.2 Software Load File Naming 9 2.2.2.1 Header File Name Extension . 9 2.2.2.2 Data File Name Exten

18、sions 9 2.2.2.3 Support File Name Extensions. 9 2.2.3 File Content and Format10 2.2.3.1 Header File Content and Format.10 2.2.3.1.1 Header File Length.12 2.2.3.1.2 Load File Format Version .12 2.2.3.1.3 Part Flags 12 2.2.3.1.3.1 Download Flag.12 2.2.3.1.3.2 Spare Flags .12 2.2.3.1.4 Pointer to Load

19、PN Length .12 2.2.3.1.5 Pointer to Number of Target HW IDs12 2.2.3.1.6 Pointer to Number of Data Files .13 2.2.3.1.7 Pointer to Number of Support Files 13 2.2.3.1.8 Pointer to User Defined Data13 ARINC REPORT 665 TABLE OF CONTENTS iv 2.2.3.1.9 Pointer to Load Type Description Length13 2.2.3.1.10 Poi

20、nter to Number of Target HW ID with Positions .13 2.2.3.1.11 Pointer to Load Check Value Length 13 2.2.3.1.12 Expansion Point No. 113 2.2.3.1.13 Load PN Length .13 2.2.3.1.14 Load PN .13 2.2.3.1.15 Expansion Point No. 214 2.2.3.1.16 Load Type Description Length14 2.2.3.1.17 Load Type Description .14

21、 2.2.3.1.18 Load Type ID14 2.2.3.1.19 Expansion Point No. 315 2.2.3.1.20 Number of Target HW IDs15 2.2.3.1.21 Target HW ID Length .15 2.2.3.1.22 Target Hardware ID15 2.2.3.1.23 Expansion Point No. 415 2.2.3.1.24 Number of Target HW ID with Positions .15 2.2.3.1.25 Target HW ID with Positions Length.

22、15 2.2.3.1.26 Target HW ID with Positions.16 2.2.3.1.27 Number of Target HW ID Positions 16 2.2.3.1.28 Position Length 16 2.2.3.1.29 Position 16 2.2.3.1.30 Expansion Point No. 516 2.2.3.1.31 Number of Data Files .16 2.2.3.1.32 Data File Pointer 17 2.2.3.1.33 Data File Name Length 17 2.2.3.1.34 Data

23、File Name 17 2.2.3.1.35 Data File PN Length.17 2.2.3.1.36 Data File PN.17 2.2.3.1.37 Data File Length.17 2.2.3.1.38 Data File CRC17 2.2.3.1.39 Data File Length in Bytes .18 2.2.3.1.40 Data File Check Value Length .18 2.2.3.1.41 Data File Check Value Type.18 2.2.3.1.42 Data File Check Value18 2.2.3.1

24、.43 Expansion Point No. 618 2.2.3.1.44 Number of Support Files.18 2.2.3.1.45 Support File Pointer18 2.2.3.1.46 Support File Name Length18 2.2.3.1.47 Support File Name .19 ARINC REPORT 665 TABLE OF CONTENTS v 2.2.3.1.48 Support File PN Length 19 2.2.3.1.49 Support File PN19 2.2.3.1.50 Support File Le

25、ngth19 2.2.3.1.51 Support File CRC .19 2.2.3.1.52 Support File Check Value Length.19 2.2.3.1.53 Support File Check Value Type19 2.2.3.1.54 Support File Check Value.20 2.2.3.1.55 Expansion Point No. 720 2.2.3.1.56 Expansion Point No. 820 2.2.3.1.57 User Defined Data20 2.2.3.1.58 Expansion Point No. 9

26、20 2.2.3.1.59 Load Check Value Length 20 2.2.3.1.60 Load Check Value Type .20 2.2.3.1.61 Load Check Value20 2.2.3.1.62 Header File CRC21 2.2.3.1.63 Load CRC 21 2.2.3.2 Data File and Format 21 2.2.3.3 Support File Content and Format21 2.2.4 Data and Support File Options.21 2.2.4.1 File Compression21

27、2.2.4.2 File Encryption 22 2.3 Optional Files.22 2.3.1 Batch File 22 2.3.1.1 Batch File Length24 2.3.1.2 Batch File Format Version.24 2.3.1.3 Spare24 2.3.1.4 Pointer to Batch File PN Length24 2.3.1.5 Pointer to Number of Target HW ID Load List-Blocks .24 2.3.1.6 Expansion Point 1.24 2.3.1.7 Batch Fi

28、le PN Length24 2.3.1.8 Batch File PN24 2.3.1.9 Comment Length 24 2.3.1.10 Comment 25 2.3.1.11 Number of Target HW ID Load-List Blocks25 2.3.1.12 Pointer to Next Target HW ID Load-List Block 25 2.3.1.13 THW ID POS Length.25 2.3.1.14 THW ID POS 25 2.3.1.15 Number of Loads for the Target HW ID POS 25 2

29、.3.1.16 Header File Name Length.25 ARINC REPORT 665 TABLE OF CONTENTS vi 2.3.1.17 Header File Name.25 2.3.1.18 Load PN Length26 2.3.1.19 Load PN26 2.3.1.20 Batch File CRC .26 3.0 LOADABLE SOFTWARE TRANSPORT MEDIA 27 3.1 Transport Media PN Assignment27 3.2 Transport Media Set Format, Content and Orga

30、nization 27 3.2.1 Transport Media Content and Structure.27 3.2.2 File Name Extensions28 3.2.3 File Content and Organization .29 3.2.3.1 List-of-Loads File Content and Organization .29 3.2.3.1.1 LOADS.LUM File Length30 3.2.3.1.2 Media File Format Version .30 3.2.3.1.3 Spare .30 3.2.3.1.4 Pointer to M

31、edia Set PN Length .30 3.2.3.1.5 Pointer to Number of Loads30 3.2.3.1.6 Pointer to User Defined Data30 3.2.3.1.7 Expansion Point No. 130 3.2.3.1.8 Media Set PN Length .30 3.2.3.1.9 Media Set PN.30 3.2.3.1.10 Media Sequence Number (X) .31 3.2.3.1.11 Number of Media Set Members (Y) 31 3.2.3.1.12 Numbe

32、r of Loads31 3.2.3.1.13 Load Pointer.31 3.2.3.1.14 Load PN Length .31 3.2.3.1.15 Load PN.31 3.2.3.1.16 Header File Name Length 32 3.2.3.1.17 Header File Name 31 3.2.3.1.18 Member Sequence Number .32 3.2.3.1.19 Number of Target HW IDs32 3.2.3.1.20 Target HW ID Length .32 3.2.3.1.21 Target HW ID .32 3

33、.2.3.1.22 Expansion Point No. 232 3.2.3.1.23 Expansion Point No. 332 3.2.3.1.24 User Defined Data33 3.2.3.1.25 LOADS.LUM File CRC .33 3.2.3.2 List-of-Files File Content and Format 33 3.2.3.2.1 FILES.LUM File Length 34 ARINC REPORT 665 TABLE OF CONTENTS vii 3.2.3.2.2 Media File Format Version .34 3.2

34、.3.2.3 Spare .34 3.2.3.2.4 Pointer to Media Set PN Length .34 3.2.3.2.5 Pointer to Number of Media Set Files.34 3.2.3.2.6 Pointer to User Defined Data34 3.2.3.2.7 Pointer to FILES.LUM Check Value Length34 3.2.3.2.8 Expansion Point No. 135 3.2.3.2.9 Media Set PN Length .35 3.2.3.2.10 Media Set PN.35

35、3.2.3.2.11 Media Sequence Number (X) .35 3.2.3.2.12 Number of Media Set Members (Y) 35 3.2.3.2.13 Number of Media Set Files.35 3.2.3.2.14 File Pointer.35 3.2.3.2.15 File Name Length.36 3.2.3.2.16 File Name.36 3.2.3.2.17 File Pathname Length 36 3.2.3.2.18 File Pathname36 3.2.3.2.19 File Member Sequen

36、ce No.36 3.2.3.2.20 File CRC36.36 3.2.3.2.21 File Check Value Length 37 3.2.3.2.22 File Check Value Type .37 3.2.3.2.23 File Check Value 37 3.2.3.2.24 Expansion Point No. 237 3.2.3.2.25 Expansion Point No. 337 3.2.3.2.26 User Defined Data37 3.2.3.2.27 FILES.LUM File Check Value Length .37 3.2.3.2.28

37、 FILES.LUM File Check Value Type 38 3.2.3.2.29 FILES.LUM File Check Value.38 3.2.3.2.30 FILES.LUM File CRC .38 3.2.3.3 List-of-Batch File Content and Organization38 3.2.3.3.1 BATCHES.LUM File Length .39 3.2.3.3.2 Media File Format Version .39 3.2.3.3.3 Spare .40 3.2.3.3.4 Pointer to Media Set PN Len

38、gth .40 3.2.3.3.5 Pointer to Number of Batches 40 3.2.3.3.6 Pointer to User Defined Data40 3.2.3.3.7 Expansion Point No. 140 3.2.3.3.8 Media Set PN Length .40 3.2.3.3.9 Media Set PN.40 ARINC REPORT 665 TABLE OF CONTENTS viii 3.2.3.3.10 Media Sequence Number (X) .40 3.2.3.3.11 Number of Media Set Mem

39、bers (Y) 41 3.2.3.3.12 Number of Batches.41 3.2.3.3.13 Batch Pointer41 3.2.3.3.14 Batch PN Length 41 3.2.3.3.15 Batch PN41 3.2.3.3.16 Batch File Name Length.41 3.2.3.3.17 Batch File Name.41 3.2.3.3.18 Member Sequence Number .42 3.2.3.3.19 Expansion Point No. 242 3.2.3.3.20 Expansion Point No. 342 3.

40、2.3.3.21 User Defined Data42 3.2.3.3.22 BATCHES.LUM File CRC 42 3.2.4 Media Set File Organization 42 3.2.4.1 Location of Load PN Files.43 3.2.4.1.1 Storage of ARINC 615 Parts 43 3.2.4.1.2 Storage of Boeing Legacy Compliant Parts 44 3.2.4.2 Media Set Parsing Rules.44 3.2.4.2.1 Search Within Primary R

41、oot Directory 44 3.2.4.2.2 Match File CRC Value44 3.2.4.2.3 Choose the First File Found in FILES.LUM 44 3.2.4.3 Directory Structure for Electronic Distribution45 3.3 Media Set Labeling 45 3.3.1 Label Content45 3.3.2 Label Format .47 3.4 Media Type Specific Items .48 3.4.1 Disk Sets .48 3.4.2 PC Card

42、 48 3.4.3 CD-ROM .49 3.4.4 Hard Disk.49 4.0 CYCLIC REDUNDANCY CODES (CRC) .50 4.1 CRC Definition .50 4.2 Rules for CRC Calculation .50 4.2.1 Bit Ordering .51 4.2.2 Bit Shifting .51 4.2.3 Transmission Bit Reflection .51 4.2.4 Process Bit Reflection .51 4.2.5 Post Process Bit Reflection .51 ARINC REPO

43、RT 665 TABLE OF CONTENTS ix 4.2.6 Initialization 51 4.2.7 Error Detection 51 4.2.8 Process Efficiency .52 4.2.9 CRC Examples52 4.3 CRC Parameters52 4.3.1 8-Bit CRC 52 4.3.2 16-Bit CRC 53 4.3.3 32-Bit CRC 54 4.4 CRC Conventions 54 4.4.1 CRC Self Reflection.54 4.4.2 File Size Limitations.54 5.0 INTEGR

44、ITY CHECK METHODS56 5.1 Integrity Check Methods.56 5.2 Data Check Value Enumeration .56 5.3 Integrity Check Types 56 5.3.1 Message Digest (MD) 5 Integrity Check 57 5.3.2 Secure Hash Algorithm-1 (SHA-1) Integrity Check 57 ATTACHMENTS 1 Manufacturers Code Assignments.58 APPENDICES A Load Structure .59

45、 B Media Set Structure .62 C File Formats.63 D Reserved68 E Manual Method for Calculating the “CC” Value 69 F Implementation for Multi-Standard Compatibility 70 G Acronyms and Abbreviations73 H Loadable Software Terminology.74 I Reference Guide83 J Request for Manufacturers Code Designator.84 K Calc

46、ulating Loadable Software Part CRC.85 L CRC Standard Reference Files for Software Data Loading95 ARINC Standard Errata Report ARINC IA Project Initiation/Modification (APIM) Guidelines for Submittal ARINC REPORT 665 - Page 1 1.0 INTRODUCTION 1.1 Purpose This document defines the aircraft industrys s

47、tandards for Loadable software Parts (LSPs)and software transport media parts (Media Sets). It describes the common principles and rules to be applied to any part of a data load system, to insure compatibility and inter-operability. It includes part numbering, content, labeling and formatting of an

48、LSP, and a Media Set containing LSPs. Loadable Software Airplane Parts (LSAP) is a subset of the LSP class of parts. All requirements for LSPs in this document also apply to LSAPs. Uniform software LSP and Media Set formats enable suppliers to employ common (standardized) loadable software processes

49、, procedures, and support tools. It is intended that software loaders, tools, processes and aircraft systems reference this standard for definition of loadable software part and software transport media content and format. This should be independent of any specific data load system, production process, or aircraft system that uses the LSP. 1.2 Applicability This standard is applicable to all loadabl