ARINC 614-1989 Standard Firmware Loader for Avionics Shops《航空电子设备标准固件负荷》.pdf

《ARINC 614-1989 Standard Firmware Loader for Avionics Shops《航空电子设备标准固件负荷》.pdf》由会员分享，可在线阅读，更多相关《ARINC 614-1989 Standard Firmware Loader for Avionics Shops《航空电子设备标准固件负荷》.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、 ASTANDARD FIRMWARE LOADERFORAVIONICS SHOPSARINC REPORT 614PUBLISHED: SEPTEMBER 30, 1989AN A DOCUMENTPrepared byAIRLINES ELECTRONIC ENGINEERING COMMITTEEPublished byAERONAUTICAL RADIO, INC.2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401This document is based on material submitted by variousparticipants du

2、ring the drafting process. Neither AEEC norARINC has made any determination whether these materialscould be subject to valid claims of patent, copyright or otherproprietary rights by third parties, and no representation orwarranty, express or implied, is made in this regard. Any use ofor reliance on

3、 this document shall constitute an acceptancethereof “as is” and be subject to this disclaimer.Copyright 1998 byAERONAUTICAL RADIO, INC.2551 Riva RoadAnnapolis, Maryland 21401-7465 USAARINC REPORT 614 STANDARD FIRMWARE LOADER FOR AVIONICS SHOPSPublished: September 30, 1989Prepared by the Airlines El

4、ectronic Engineering CommitteeReport 614 Adopted by the Airlines Electronic Engineering Committee: February 21, 1989iiFOREWORDActivities of AERONAUTICAL RADIO, INC. (ARINC)and thePurpose of ARINC Reports and SpecificationsAeronautical Radio, Inc., is a corporation in which the United States schedule

5、d airlines are the principalstockholders. Other stockholders include a variety of other air transport companies, aircraft manufacturers and non-U.S. airlines.Activities of ARINC include the operation of an extensive system of domestic and overseas aeronauticalland radio stations, the fulfillment of

6、systems requirements to accomplish ground and airborne compatibility, theallocation and assignment of frequencies to meet those needs, the coordination incident to standard airbornecommunications and electronics systems and the exchange of technical information. ARINC sponsors the AirlinesElectronic

7、 Engineering Committee (AEEC), composed of airline technical personnel. The AEEC formulatesstandards for electronic equipment and systems for the airlines. The establishment of Equipment Characteristics is aprincipal function of this Committee.An ARINC Equipment Characteristic is finalized after inv

8、estigation and coordination with the airlines whohave a requirement or anticipate a requirement, with other aircraft operators, with the Military services havingsimilar requirements, and with the equipment manufacturers. It is released as an ARINC Equipment Characteristiconly when the interested air

9、line companies are in general agreement. Such a release does not commit any airline orARINC to purchase equipment so described nor does it establish or indicate recognition of the existence of anoperational requirement for such equipment, nor does it constitute endorsement of any manufacturers produ

10、ctdesigned or built to meet the Characteristic. An ARINC Characteristic has a twofold purpose, which is:(1) To indicate to the prospective manufacturers of airline electronic equipment the consideredopinion of the airline technical people, coordinated on an industry basis, concerning requisites ofne

11、w equipment, and(2) To channel new equipment designs in a direction which can result in the maximum possiblestandardization of those physical and electrical characteristics which influence interchangeabilityof equipment without seriously hampering engineering initiative.ARINC REPORT 614TABLE OF CONT

12、ENTSiiiITEM SUBJECT PAGE1.0 INTRODUCTION 11.1 Purpose 11.2 Scope 11.3 Description 11.4 Interchangeability 11.5 Related Documents 12.0 SYSTEM OVERVIEW 22.1 Introduction 22.2 Form Factor 22.2.1 Physical Size 22.2.2 Weight 22.2.3 Interface Connectors 22.3 Input Power 22.4 Media Standards 22.5 Operator

13、Interface 22.6 Operational Characteristics 22.6.1 Programmer Capability 22.6.2 Self-Test 22.6.3 Annunciations 22.6.3.1 System Failure 22.6.3.2 Card Test Failure 22.6.3.3 Operator Alert 22.7 Support 22.8 Environmental Considerations 33.0 HARDWARE CHARACTERISTICS 43.1 Controller Hardware 43.2 Firmware

14、 Loader Hardware 43.2.1 Control Signal Characteristics 43.2.1.1 Address Lines 43.2.1.2 Data Lines 43.2.1.3 Logic Control Lines 43.2.2 Power Supply Characteristics 43.2.2.1 Programmable Board Vcc 43.2.2.2 Programmable PROM Vcc 43.2.2.3 Power Control Buses (Vpp) 43.2.2.4 Auxiliary Power Supplies 43.2.

15、2.5 Power Supply Monitoring 53.3 Circuit Card Adapter 54.0 SOFTWARE CHARACTERISTICS AND INTERFACE PROTOCOL 64.1 Introduction 64.2 System Software 64.3 Application Software 64.4 Board/Module Information File 64.4.1 Interface Description 6-74.4.2 File Structure 74.4.2.1 The Board Section 74.4.2.2 The

16、PROM Section 84.5 Data File 84.5.1 Header Record 84.5.2 Data Records 84.5.3 End of File (EOF) Record 84.6 Controller/Firmware Loader Interface 84.7 Data Integrity 84.8 Standardized Identifier 8APPENDICESAPPENDIX 1 Firmware Loader Example Implementation 9APPENDIX 2 Interface Connector Definition 10-1

17、5APPENDIX 3 Program Command Codes 16-31APPENDIX 4 Program Example 32-36APPENDIX 5 Honeywell Standard File Format 37-47ARINC REPORT 614 Page 11.0 INTRODUCTION1.1 PurposeThis document describes the characteristics of a standardfirmware loader for avionic shops which is capable ofcopying digital inform

18、ation into memory devicesinstalled in circuit card assemblies, Line ReplaceableModules (LRMs) and On-Board Replaceable Modules(OBRMs). It contains the recommendations of the airtransport community concerning the design anddevelopment of firmware loader equipment.1.2 ScopeThis document concentrates i

19、ts guidance on firmwareloader equipment which will be used at the shop level tomaintain current generation and future avionicsequipment. It applies to circuit card assemblies, LRMsand OBRMs. It defines a standardized data format whichcould be used in future systems as new data loadingconcepts emerge

20、.1.3 DescriptionThe standard firmware loader consists of a controller,card/module programming hardware, system hardware,system software, application software and adapters. Itshould be capable of transferring digital information froma mass storage medium into circuit card assemblies andmodules produc

21、ed by any avionics manufacturer.1.4 InterchangeabilityInterchangeability is achieved by adhering to astandardized data format structured in accordance withAppendix 3 of this document. It should be usablewithout need for modification or change to any firmwareloader designed to meet the goals of this

22、Report. Thesystem design should be modular in concept and shouldbe designed to facilitate shop use.1.5 Related DocumentsARINC Report 607 Design Guidance for AvionicEquipment.ARINC REPORT 614 Page 22.0 SYSTEM OVERVIEW2.1 IntroductionThis section describes the physical criteria, input and outputinterf

23、aces, and operational characteristics of standard firmwareloader equipment. It should be noted that the characteristicscontained in this Report describe the minimum capabilities. Inall cases, the designer should consider the actual systemrequirements for each implementation.2.2 Form FactorThe form f

24、actor is only defined in general terms in order toencourage manufacturer innovation. It is recognized that asnewer technologies emerge it is likely that equipment size willbe reduced.2.2.1 Physical SizeThe equipment should be designed to be bench top portable, oroptionally rack mounted.2.2.2 WeightW

25、eight is not explicitly specified. It should, however, becompatible with the desire for portability.2.2.3 Interface ConnectorsThe interface between the firmware loader and the board/moduleto be programmed is through two 84-pin signal connectors andone 17-pin power connector. The connector part numbe

26、rs andpin designations are defined in Appendix 2 of this Report.2.3 Input PowerThe equipment should be designed to operate from 115/220 Vacat 50/60 Hz power, and plug into common receptacles (i.e.,house power). Current is not specified, however, it should bewell within the capabilities of the house

27、wiring.COMMENTARYDevelopers of firmware loader equipment shouldrecognize that some users may desire to operate from 115Vac at 400 Hz power.2.4 Media StandardsThe airlines desire one standard medium for the cardprogrammer, the computer industry standard 3.5 inch floppydisk. The preferred media should

28、 be compatible with MS-DOSversion 3.2 or higher.COMMENTARYIt is recognized that new technologies such as optical diskstorage and others may offer significant benefits in thefuture. Manufacturers designs should not preclude theuse of such technology when it is mature.2.5 Operator InterfaceThe operato

29、r input should be via a cathode ray tube (CRT) orother electronic display device and a keyboard. A hardcopyoutput can be made available.The operator interface should control the system through theelectronic display and keyboard. A series of menus shouldbe provided with the capability to enter the ne

30、cessaryinformation prior to moving on to the next step. The2.5 Operator Interface (contd)operator should be provided with the means necessary to run theprogrammer application process.2.6 Operational CharacteristicsTo a large extent operational characteristics will influence thedesign of firmware loa

31、der equipment. It should be possible forthe firmware loader to perform direct memory programmingwhere the program memory bit width is evenly divisible bydevice bit width of a given cad or module.2.6.1 Programmer capabilityThe firmware loader should be capable of holding multiplecircuit cards and/or

32、modules for individual programming from a“master” board or the standard floppy disk medium specified inSection 2.4.COMMENTARYThe basic firmware loader programs one board at a time.However, manufacturers are encouraged to be innovativeand offer products with additional programmingcapability. For exam

33、ple, multiple boards may beprogrammed concurrently. Software addressable logiccontrol lines can be used to enable this feature. Also,spare pins at the interface connector may be used toimplement board enable lines.2.6.2 Self-TestThe capability to test the operation of the firmware loader shouldbe in

34、herent to the unit. Self-test should be capable of verifyingthe integrity of the hardware and the proper operation of thesoftware.2.6.3 AnnunciationsThe firmware loader should provide discrete annunciation ofcertain critical conditions. The annunciation can be a lamp or amessage on the electronic di

35、splay.2.6.3.1 System FailureThis annunciation provides the user with an indication that thefirmware loader has failed. It should indicate the event that self-test has failed.2.6.3.2 Card Test FailureThis annunciation should indicate when a card test failure hasoccurred. It should indicate the event

36、of a device short circuit ora checksum or CRC error.2.6.3.3 Operator AlertThe annunciation provides aural and visual alert to the operatorwhen attention is required. This annunciation can be used inconjunction with any other indicator.2.7 SupportWhen selecting hardware, good long term vendor support

37、 isessential in order to maintain the integrity of the equipment overits useful life. Elements of good long-term support include: Availability of parts and repair beyond themanufacturers life of the equipment. World-wide support facilities. Trouble-shooting documentation.ARINC REPORT 614 Page 32.0 S

38、YSTEM OVERVIEW (contd)2.8 Environmental ConsiderationsThe typical operating environment of firmware loader equipmentwill be that of an avionics maintenance shop. It is recommendedthat the equipment be designed to meet the needs of the typicalshop environment.ARINC REPORT 614 Page 43.0 HARDWARE CHARA

39、CTERISTICS3.1 Controller HardwareThe controller should be a commercially available computer witha minimum of a 3.5 inch floppy disk drive, an electronic displayand keyboard. The controller should be capable of reading andwriting files compatible with the MS DOS version 3.2 or higheroperating system.

40、 As an option, a hard disk and a printer orother hard copy device can be provided.NOTE: Although a controller is specified in thisReport, it may be user supplied or integral to the firmwareloader.COMMENTARYFor the purpose of receiving information frommanufacturers, some users may desire a remote I/O

41、interface (e.g., modem) for use in electronic transfer ofdata.3.2 Firmware Loader HardwareThe firmware loader hardware should include all of the hardwarenecessary to interface the controller to the circuit card. Forexample, a circuit card may be necessary to interface thefirmware loader to the contr

42、oller. A standardized connectordefined in Section 2.2.3 provides the necessary outputs to theinterface adapter. The firmware loader should contain the powersupplies necessary to perform the programming operation.3.2.1 Control Signal CharacteristicsIt is recommended that data bus and control bus line

43、s interface toCMOS as well as TTL devices and provide all necessary signalsto access and program PROM devices. The data path to the cardshould be bi-directional and easy to interface with presenttechnology bus widths. Address lines, chip enables, outputenables and any other signals required to latch

44、 information orprovide control signals to the card should be provided bysoftware configurable control lines. A programmable clockshould be provided which operates at 1, 2, 4, and 8 MHz. TheInterface Connector Definition (Appendix 2) specifies the pinassignments for these signals.3.2.1.1 Address Line

45、sThirty-two general purpose LS-TTL/CMOS compatible tri-statecontrol lines should be provided. Device/card addressing linesA0 through A31 are designated for this purpose.COMMENTARYManufacturers comment that a high degree of integrity canbe achieved by optionally using bi-directional bus lines toprovi

46、de read-back capability.3.2.1.2 Data LinesThirty-two bi-directional LS-TTL/CMOS compatible tri-statebus lines should be provided. They should include pull-upresistors to 5 Vdc internal to the firmware loader equipment.Data lines D0 through D31 are designated for this purpose.3.2.1.3 Logic Control Li

47、nesSixteen bi-directional LS-TTL/CMOS compatible tri-state logiccontrol lines should be provided for control functions. They aredesignated TC0 through TC15.3.2.2 Power Supply CharacteristicsIn general, four types of DC power sources are necessary tooperate the firmware loader. Three of the power sou

48、rces areneeded to supply programming voltages. The programmingvoltages specified are for a minimum system and shouldtherefore be considered as a “per-board” specification.During programming, PROM devices use a Vpp higher than 5.0Vdc. In some cases, Vcc is also raised during programming. Toensure the

49、 widest possible application of the firmware loader,Vcc and Vpp to the PROMs should be programmable over arange wide enough to accommodate all present and anticipatedfuture PROM designs. Since other devices such as buffers,control logic, etc. may populate the board/module and needvoltages outside typical Vcc ranges, auxiliary power supplies arerecommended.3.2.2.1 Programmable Board VccA power source should be provided which is capable ofsupplying 0 to 7 Vdc at 5.0 amperes as a minimum. It isintended for use as Vcc for all devices other EPROMS.COMMENTARYIn some applicat