Rapid reprogramming terminal

BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates generally to memory loading apparatus and, in particular, to a light weight portable reprogramming and data verifier apparatus which may be used to load data into aircraft avionics and electronic warfare and countermeasure systems and then verify the accuracy of the data.
2. Description of the Prior Art
In the prior art there are memory loader and data verifier systems which provide the means for loading data into the avionics aboard military aircraft and thereby reprogram the aircraft avionics. These prior art memory loader and data verifier systems are also utilized to load data into the aircraft's electronic warfare and countermeasure systems. In addition, these prior art systems will verify that the data is loaded correctly into the aircraft's avionics and electronic warfare and countermeasure systems.
One such device of the prior art is the Memory Loader Verifier, Model ASM-607MLV manufactured by Texas Instruments, while another such device of the prior art is the Advanced Memory Loader Verifier, Model ASM-607AMLV also manufactured by Texas Instruments.
Each of these prior art devices load new data into the avionics and electronic warfare and countermeasure systems aboard the aircraft and then verify that the memories have been correctly loaded. The new data is loaded via an aircraft's multiplex data bus which generally meets the design requirements of military standard (MIL-STD)-1553. This, in turn, allows for the reprogramming of aircraft on-board avionics and electronic warfare systems.
While satisfactory for their intended purpose which is the reprogramming of military aircraft on board avionics and electronic warfare and countermeasures systems, these memory loader verifier (MLV) systems of the prior art leave something to be desired in that they often do not make use of state of the art high speed electronics which results in these prior art MLV systems having a slow operating speed, being susceptible to failure, and being bulky in size. Further, these prior art MLV systems are very expensive to produce.
With the above and other disadvantages known to prior art memory loader verifier systems the present invention was conceived and one of its objects is to provide a means whereby the avionics on board an aircraft can be reprogrammed.
Another object of the present invention is to provide a means whereby the electronic warfare and countermeasures systems on board an aircraft can be reprogrammed.
It is yet another object of the present invention to provide a portable, inexpensive and compact reprogramming terminal for reprogramming the avionics and electronic warfare and countermeasures systems on board an aircraft.
It is still another object of the present invention to verify that the data loaded from the reprogramming terminal is correctly loaded into the avionics and electronic warfare and countermeasures systems on board an aircraft.
A further object of the present invention is to provide a reprogramming terminal which uses high speed, state of the art electronics technology to allow for the rapid reprogramming of the avionics and electronic warfare and countermeasures systems on board an aircraft.
Various other objects and advantages of the present invention will become apparent to those skilled in the art as a more detailed description of the invention is set forth below.
SUMMARY OF THE INVENTION
The aforesaid and other objects of the invention are accomplished by a rapid reprogramming terminal adapted for communication with military aircraft MS-1553 multiplex data bus which includes generally five avionics and one electronic warfare bus on board each aircraft. The rapid reprogramming terminal of the present invention may be used to reprogram all electronic warfare and avionics systems on board the aircraft including the bus controllers for each avionics or electronic warfare bus on the aircraft and the remote terminals connected to each bus on the aircraft. The rapid reprogramming terminal includes a high speed digital signal processor which executes the functions required to reprogram a remote terminal or bus controller through software stored in an electrically erasable program read only memory (EEPROM). The information required to reprogram a remote terminal or bus controller is stored on an IC memory card which is electrically coupled to the digital signal processor. When the rapid reprogramming terminal establishes communications with either an avionics bus or electronic warfare bus by enabling certain discretes associated with the bus, the digital data required to reprogram, for example, a remote terminal connected to the avionics bus is transferred from the IC memory card through the digital signal processor in a parallel format to a 1553 communications interface controller/terminal. The 1553 communications interface terminal converts the digital data from the digital signal processor to Manchester encoded differential data for transfer via the MS-1553 multiplex data bus to the remote terminal or bus controller being reprogrammed. Data from a remote terminal or bus controller on the MS-1553 multiplex data bus is converted from Manchester encoded differential data to digital data in a parallel format and then transferred to the digital signal processor for processing.
The rapid reprogramming terminal of the present invention also provides for a verify operation whereby the data stored in the IC memory card is compared with the data stored in the bus controller or remote terminal being reprogrammed to verify that the data stored in the bus controller or remote terminal being reprogrammed is identical to the data in the IC memory card.

BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram illustrating the rapid reprogramming terminal interfacing with the 1553 multiplex data bus on board an aircraft;
FIGS. 2A and 2B are an illustration of the front panel and front panel electrical wiring diagram for the rapid reprogramming terminal of the present invention;
FIG. 3 is an electronics circuit diagram for the interface bus controller for the IEEE-488 bus.
FIG. 4 illustrates the bus coupling methods of the 1553 multiplex data bus to which the rapid reprogramming terminal is connected;
FIG. 5 is an example illustrating the Intel 32 bit Hexadecimal Object File Record Format used with the rapid reprogramming terminal of the present invention;
FIG. 6 is a simplified flow diagram illustrating the sequence of operation of the program modules for the software used by rapid reprogramming terminal of the present invention;
FIG. 7 illustrates the format of message transfers via the 1553 multiplex data bus interface aboard an aircraft;
FIG. 8A illustrates rapid reprogramming terminal to remote terminal data transfers;
FIG. 8B illustrates remote terminal to rapid reprogramming terminal data transfers;
FIG. 9A illustrates the format of activity message transfers via the 1553 multiplex data bus to and from a remote terminal being reprogrammed;
FIG. 9B illustrates the status response word format provided by a remote terminal for each message transaction via the 1553 multiplex data bus;
FIG. 9C illustrates the format of memory configuration messages transferred via the 1553 multiplex data bus to a remote terminal being reprogrammed;
FIG. 9D illustrates the format of enter load, exit load, enter verify and exit verify messages transferred via the 1553 multiplex data bus to a remote terminal being reprogrammed;
FIG. 9E illustrates the format of a header message transferred via the 1553 multiplex data bus to a remote terminal being reprogrammed;
FIG. 9F illustrates the format of a memory data load message transferred via the 1553 multiplex data bus to a remote terminal being reprogrammed;
FIG. 9G illustrates the format of a memory data verify message transferred via the 1553 multiplex data bus to a remote terminal being reprogrammed;
FIG. 9H illustrates the format of a trailer message transferred via the 1553 multiplex data bus to a remote terminal being reprogrammed;
FIG. 9I illustrates the format of a reprogram status message transferred via the 1553 multiplex data bus from a remote terminal being reprogrammed;
FIG. 9J illustrates the format of a RRT error message transferred via the 1553 multiplex data bus to a remote terminal being reprogrammed;
FIG. 10 is a flow chart illustrating the PROTOB.C module of the rapid reprogramming terminal software;
FIG. 11A illustrates the format of activity message transfers via the 1553 multiplex data bus to and from a bus controller being reprogrammed;
FIG. 11B illustrates the status response word format provided by a bus controller terminal for each message transaction via the 1553 multiplex data bus;
FIG. 11C illustrates the format of memory configuration messages transferred via the 1553 multiplex data bus to a bus controller being reprogrammed;
FIG. 11D illustrates the format of enter load, exit load, enter verify and exit verify messages transferred via the 1553 multiplex data bus to a bus controller being reprogrammed;
FIG. 11E illustrates the format of a header message transferred via the 1553 multiplex data bus to a bus controller being reprogrammed;
FIG. 11F illustrates the format of a memory data load message transferred via the 1553 multiplex data bus to a bus controller being reprogrammed;
FIG. 11G illustrates the format of a memory data verify message transferred via the 1553 multiplex data bus to a bus controller being reprogrammed;
FIG. 11H illustrates the format of a trailer message transferred via the 1553 multiplex data bus to a bus controller being reprogrammed;
FIG. 11I illustrates the format of a reprogram status message transferred via the 1553 multiplex data bus from a bus controller being reprogrammed;
FIG. 11J illustrates the format of a RRT error message transferred via the 1553 multiplex data bus to a remote terminal berg reprogrammed;
FIG. 12 is a flow chart illustrating the PROTOC.C module of the rapid reprogramming terminal software;
FIG. 13 is a detailed electrical schematic illustrating the power supply for the rapid reprogramming terminal;
FIGS. 14a and 14b are a detailed electrical schematic of the avionics interface of the rapid reprogramming terminal;
FIGS. 15a and 15b are a detailed electrical schematic of the electronic warfare interface of rapid reprogramming terminal;
FIGS. 16A-16H are a detailed electrical schematic of the control circuitry including the digital signal processor of the rapid reprogramming terminal;
FIG. 17 is an electronics circuit diagram of the discrete interface of the rapid reprogramming terminal;
FIGS. 18A-18G illustrate the read and write timing signals for certain electrical devices of the rapid reprogramming terminal; and
FIGS. 19A-19S is a flow chart for the rapid reprogramming terminal software.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
Referring to FIGS. 1, 16A, 16B, 16D and 16E, the rapid reprogramming terminal 20 of the present invention comprises a digital signal processor 21 which controls the communications interfaces of rapid reprogramming terminal 20, controls the discrete signals provided by and supplied to rapid reprogramming terminal 20 and effects the transfer of digital data to and from an IC memory card 22. Digital signal processor 21, in turn, receives it instructions from an EEPROM 23, provides addressing to EEPROM 23 and utilizes an internal RAM as storage for certain software and temporary storage of data and status bits. EEPROM 23 consist of four 64K.times.8 bit EEPROMs 240, 241, 244 and 246, FIG. 16D, configured in parallel which function as a single 64K.times.32 bit EEPROM. Programs are loaded into EEPROM memory under software control of digital signal processor 21, that is digital signal processor 21 provides addressing, data and control signals to EEPROM 23 under the direction of software stored in the internal random access memory of digital signal processor 21. Rapid reprogramming terminal 20 also includes IC memory card 22 which stores the digital data required to reprogram the aircraft on board avionics and electronic warfare and countermeasures systems. Data read from IC memory card 22 is masked to the least sixteen significant bits of each word since the remaining bits are floating and would be read as noise. It should be noted that the digital signal processor used in the preferred embodiment of the present invention is a Texas Instrument Model TMS320C30 Digital Signal Processor.
The 28 megahertz system clock signal for rapid reprogramming terminal 20 is provided by a system clock generator 27 and is supplied to the X2/CLKIN input of digital signal processor 21.
Programmable array logic devices 24 and 25 function as decoders for address and control signals supplied thereto to direct the operation of all external devices to digital signal processor 21. Device 24 is programmed to convert a primary address line input (A22 input) of device 24 and the control line inputs (/STRB, CARD0.sub.-- WP, CARDWP.sub.-- 1 MCS1/0 and R/W inputs) into control signals (/EEPROM, /MCS0, /MCS1, /RD and /WR) that control EEPROM 23 and memory cards zero and one of IC memory card 22.
At this time it should be noted that IC memory card 22 comprises a pair of identical IC memory cards with the first IC memory card (memory card zero) being electrically connected to an electrical connector 28 and the second IC memory card (memory card one) being electrically connected to an electrical connector 29.
Device 24 is programmed to convert alternate control signals /IOSTRB and XR/W provided by digital signal processor 21 into control signals that operate the parallel peripheral interface (PPI) ports PA0-PA7, PB0-PB7 and PC0-PC7 of three programmable peripheral interfaces 52, 54 and 56, FIG. 17; and the universal asynchronous receiver transmitter (UART) circuits 37 and 39, FIG. 16F; the 1553 communications interface controller 41, FIG. 16G; and the IEEE-488 bus controller 260, FIG. 3, of rapid reprogramming terminal 20. Software within digital signal processor 21 extends access time for the parallel peripheral interface ports PA0-PA7, PB0-PB7 and PC0-PB7 of programmable peripheral interfaces 52, 54 and 56; universal asynchronous receiver transmitter circuits 37 and 39; the 1553 communications interface controller 41; and the IEEE-488 bus controller 260 since processor 21 operates at a processing speed that is too fast for parallel peripheral interface ports PA0-PA7, PB0-PB7 and PC0-PB7 of programmable peripheral interfaces 52, 54 and 56; universal asynchronous receiver circuits 37 and 39; the 1553 communications interface controller 41; and the IEEE-488 bus controller 260.
PPI port PA0-PA7 of interface 56 is an output port designated to send control signals selecting the 1553 multiplex data bus 42 aboard the aircraft. The logic signals EW, AV1, AV2, AV3, AV4 and AV5 select which bus rapid reprogramming terminal 20 will pass data through. PPI port PB0-PB7 of interface 56 is an output port which is utilized to configure and turn on the 1553 multiplex data bus avionics and electronic warfare equipment, that is remote terminals 53 and bus controllers 55. PPI port PC0-PC7 of interface 56 is an output port which provides output control signals to control liquid crystal display 57 and Remote Terminal address signals to the RTAD0-RTAD4 and RTADP inputs of 1553 communications interface controller/terminal 41, FIG. 16G.
PPI port PA0-PA7 of interface 54 is an output port which provides control signals to a predetermined device within the aircraft's avionics or electronic warfare systems enabling access to the memory of the device to which data is being transferred. PPI port PA0-PA7 of interface 54 is also designated to send control signals to the avionics bus controller of 1553 multiplex data bus 42 preparing the bus controller for reprogramming by rapid reprogramming terminal 20.
PPI port PB0-PB7 of interface 54 is an output port which provides rapid reprogramming terminal generated control signals which power down the avionics bus controller allowing rapid reprogramming terminal 20 to upload data into the aircraft avionics and thereby reprogram the avionics.
PPI port PC0-PC3 of interface 54 is an input port which monitors fail signals provided by the aircraft avionics bus controller to determine whether the data has been correctly loaded into the avionics bus controller, that is PPI port PC0-PC3 of interface 54 is used to indicate an error in loading.
PPI port PC4-PC7 of interface 54 is an output port which is used to provide address and control signals to the first and second memory cards of IC memory card 22 via connectors 28 and 29.
PPI port PA0-PA7 of interface 52 is an input port used to monitor the aircraft type and thereby prevent data which is designated for loading in one type of aircraft from being loaded in a different type of aircraft.
PPI port PB0-PB7 of interface 52 is an input port used to monitor configuration of the aircraft to prevent data which is designated for loading in one configuration of the aircraft from being loaded in a different aircraft configuration. PPI ports PA0-PA7 and PB0-PB7 of interface 52 receive control signals from switches on the front panel 43, FIG. 2 so as to monitor the state of the switches on front panel 43.
PPI port PC0-PC7 of interface 52 is an output port for supplying ASCII characters to liquid crystal display 57 on front panel 43, FIG. 2.
The UART circuits 37 and 39 of rapid reprogramming terminal 20 respectively communicate with any RS-232 communications bus 71 and any RS-422 communications bus for the transfer of data to and from the IC memory card 22 via the rapid reprogramming terminal 20. As is best illustrated in FIG. 16F, UART circuits 37 and 39 are connected to drivers 250 and 254 and receivers 252 and 256 which match the interface characteristics of RS-232 and 422 buses.
Rapid reprogramming terminal also includes the 1553 communications interface terminal 41 of FIG. 16G which is used to translate the sixteen bit parallel data words provided by digital signal processor 21 into Manchester mark encoded Military Standard 1553 signals for use by 1553 multiplex data bus 42 and also to decode Manchester mark signals provided by bus 42 into sixteen bit parallel data words supplied to digital signal processor 21.
Referring to FIGS. 2A and 2B, there is shown the front panel 43 which includes a power switch 44, a down/verify/up switch 47 and an execute/skip switch 49. The power switch 44 when in the on position turns power on to rapid reprogramming terminal 20. The down/verify/up switch 47 when in the up position allows data to be loaded from rapid reprogramming terminal 20 to the aircraft avionics or electronic warfare system and when in the down position allows data to be loaded from the avionics or electronic warfare systems to rapid reprogramming terminal 20. The down/verify/up switch 48 when in the verify position allows for data already in the aircraft avionics and electronic warfare systems to be verified by rapid reprogramming terminal 20. When the message "Exec to continue" is displayed by liquid crystal display 57, execute/skip switch 49 is a momentary contact switch which when activated to the Exec position allows rapid reprogramming terminal 20 to begin loading data files. When in the manual mode and it is desired to load or skip a data file, that is load or not load the data file, an operator can press the exec/skip switch 49 to the exec position to load the data file or skip position to not load the data file.
Referring now to FIG. 17 there is shown the discrete interface circuit which comprises programmable peripheral interfaces 52, 54 and 56 providing the interface for the discrete logic signals to be provided by rapid reprogramming terminal 20 to the aircraft on board avionics and electronic warfare and countermeasures systems as well as the discrete logic signals provided from the avionics and electronic warfare and countermeasures systems to rapid reprogramming terminal 20. In addition, programmable peripheral interfaces 52 and 56 function as an interface between liquid crystal display 57, FIG. 2A, and digital signal processor 21.
The programmable interfaces 52, 54 and 56 may be a performance CMOS version of the industry standard 8255A general purpose programmable input/output device with which is compatible with any general purpose microprocessor. For example a Model 82C55A CMOS Programmable Peripheral Interface manufactured by Harris Corporation may be used as programmable interfaces 52, 54 and 56.
Referring to FIGS. 1, 2 and 17, the EW output of programmable interface 56 electrically couples the electronic warfare bus of 1553 multiplex data bus 42 to rapid reprogramming terminal 20 when the EW output of programmable interface 56 is at the logic one state. Similarly, the AV1, AV2, AV3, AV4 and AV5 outputs of interface 56 electrically couple the five avionics buses of bus 42 to rapid reprogramming terminal 20. It should be noted that a data transfer from rapid reprogramming terminal 20 to the EW bus, the AV1 bus, the AV2 bus, the AV3 bus, the AV4 bus or the AV5 bus of the aircraft can occur only when the EW, AV1, AV2, AV3, AV4 or AV5 output from interface 56 is at the logic one state.
It should further be noted the EW bus is a single channel 1553 bus, while the AV1 bus, the AV2 bus, the AV3 bus, the AV4 bus and the AV5 bus of the aircraft are two channel 1553 buses, that is the avionics buses are dual redundant buses. This allows bus controllers on the avionics buses of the aircraft to communicate with remote terminals on the bus through either of two channels.
Outputs PA6 and PA7 of interface 56 (lines PPI1A6 and PPI1A7) are spares.
The DIR/XFMR output configures the 1553 multiplex data bus 42 such that coupling is either provided directly as is best illustrated by FIG. 4 or via a transformer 60 as is also best illustrated by FIG. 4. When the DIR/XFMR output is at the logic one state the rapid reprogramming terminal 20 is coupled directly to the aircraft on board avionics and electronic warfare systems. When the DIR/XFMR output is at the logic zero state the coupling is through transformer 60. The GND/OPEN.sub.-- CT output of interface 56 when at the logic one state grounds the center tap of transformers 213 and 214, FIG. 15a while a logic 0 at the GND/OPEN.sub.-- CT output removes the ground from the center tap of transformers 213 and 214.
The RS422.sub.-- XMIT.sub.-- OFF output of interface 56 is connected to the /EN input of driver 254. A logic one at the /EN input of driver 254 tristates driver 254 such that driver 254 is disabled while a logic zero enables driver 254. This logic one signal is necessary since some RS-422 interfaces are half duplex requiring that there be a means whereby the transmit driver can be turned off.
The PB3 output (PPI1B3 line) of interface 56 is a spare.
The MSDRS.sub.-- ON.sub.-- OFF Output of interface 56 enables the Maintenance Signal Data Recording Set (MSDRS) aboard an aircraft with a logic zero enabling the MSDRS and a logic one disabling the MSDRS. This output is also currently being utilized with only the F/A-18 fighter aircraft.
The BOOT.sub.-- EN.sub.-- SMS output (PB3 output of interface 56) is utilized with an aircraft having a stores management system (SMS) requiring an input to enable a boot strap load operation. A logic one at this output enables the SMS boot strap load allowing data to be transferred from rapid reprogramming terminal 20 to the stores management system via an avionics system bus while a logic zero disables the SMS boot strap load.
The BOOT.sub.-- EN.sub.-- RDP output enables the radar data processor (RDP) boot strap load operation aboard an aircraft and is currently being utilized with only the F/A-18 fighter aircraft. When the BOOT.sub.-- EN.sub.-- RDP output is at the logic one state the radar data processor boot strap load is enabled allowing data to be transferred from rapid reprogramming terminal 20 to the radar data processor, while a logic zero disables the RDP boot strap load.
The PB7 output (PPI1B7 line) of interface 56 is a spare.
The PC0-PC4 outputs of interface 56 (address lines RTAD0-RTAD4) provide addressing to 1553 communications interface terminal 41 of FIG. 16G, while the PC5 output of interface 56 (RTADP parity line) provides a parity bit for address verification to 1553 communications interface terminal 41. The address provided by the PC0-PC4 outputs of interface 56 to controller/terminal 41 establishes a remote terminal address for rapid reprogramming terminal 20 when rapid reprogramming terminal 20 is used as a remote terminal.
The LCD.sub.-- CTRL/CHAR output of interface 56 is the register select for the liquid crystal display 57. When the LCD.sub.-- CTRL/CHAR output is at a logic one state a control register for liquid crystal display 57 is selected, while a logic zero at the LCD.sub.-- CTRL/CHAR output selects a character register for liquid crystal display 57.
When a character bit is written into liquid crystal display 57, the PC6 output of interface 56 is set at the logic one state. The character bit to be written into liquid crystal display 56 is then provided at the PC0-PC7 outputs of interface 52 (ASCII.sub.-- BIT0-ASCII.sub.-- BIT7). An enable pulse provided at the PC7 output of interface 56 (LCD.sub.-- ENABLE line) writes the character bit occurring at the PC0-PC7 outputs of interface 52 into liquid crystal display 56.
A logic one at the PA0 output (EW.sub.-- OSM.sub.-- EN line) of interface 54 enables the operating system memory of the electronic warfare system on board the aircraft, that is data may be loaded into the operating system software memory. Similarly, when the PA1 output (EW-UDM.sub.-- EN line) of interface 54 is at the logic one state data may be loaded into the user data memory of the electronic warfare system on board the aircraft.
The electronic warfare user data memory program enable discrete of interface 54 enables the erase and write functions of all user data memories, for examples EEPROMS, of all the electronic warfare equipment on the electronic warfare multiplex bus. In addition, upon initial activation the electronic warfare user data memory program enable discrete, if required, will cause the bus controller for the electronic warfare multiplex bus to start polling rapid reprogramming terminal 20 and upon deactivation will cause the bus controller to stop polling rapid reprogramming terminal 20. Further this program enable discrete is used to indicate to the bus controller that it is to resume its bus controller functions when the enable is released, that is driven to the logic zero state. The electronic warfare operating system memory has the same functions with respect to reprogrammable operating system memories in devices connected to the electronic warfare multiplex bus.
A logic one at the PA2 output (EXT.sub.-- PROC.sub.-- ON/OFF line) of interface 54 enables the external processor of an AN/ALQ-165 radar jammer on board the aircraft. The purpose of the AN/ALQ-165 external processor discrete is to limit power on time to less than one minute for load/verify of 32K data words of user data memory. It should be noted that the AN/ALQ-165 processor is currently incorporated on only the F/A-18 C/D fighter aircraft.
The AV.sub.-- EN1 and AV.sub.-- EN2 lines (AV Program Enable discretes) of interface 54, which are used for the avionics buses in the aircraft, may be connected to individual avionics equipment to control two program memory areas within the equipment or the AV-EN1 and AV.sub.-- EN2 outputs may be routed separately to avionics equipment on board the aircraft which does not require control of two memory areas. When the PA4 output (AV.sub.-- EN1 line) of interface 54 is at a logic one state the first memory areas of the aircraft avionics system are enabled, while a logic one at the PA5 output (AV.sub.-- EN2 line) of interface 54 enables the second memory areas of the aircraft avionics system.
The PPI2A3, PPI2A6 and PPI2A7 lines are spares.
The bus controller for the aircraft avionics buses is an AN/AYK-14 computer with each aircraft avionics system having up to four AN/AYK-14 computers. The Initiate Program Load (IPL), Initiate Program load Fail (IPL.sub.-- F) and Power Off/On (PWR OFF/ON) discretes, which are used to control an AN/AYK-14 are implemented between each AN/AYK-14 computer on board the aircraft and rapid reprogramming terminal 20. It should be noted that the AV reprogram enable discretes are not used with the AN/AYK-14 computers.
Logic ones at the PWR.sub.-- OFF 1, PWR.sub.-- OFF 2, PWR.sub.-- OFF 3 or PWR.sub.-- OFF 4 outputs of interface 52 will turn off one or more of the four AN/AYK-14 Avionics computer bus controllers, while a logic zero at one or more of these outputs will turn on one or more of the controllers. To transfer data from rapid reprogramming terminal 21 to one or more remote terminals 53 or an AN/AYK-14 Avionics computer bus controller 55, that is one or more avionics devices on board the aircraft, on any of the four avionics buses aboard the aircraft, power to the AN/AYK-14 controlling the bus must first be turned off.
After power is turned off a logic one at the PB4 output (IPL.sub.-- 1 line) of programmable interface 54 is required to load data from rapid reprogramming terminal 20 to the AN/AYK-14 avionics computer 55 via avionics bus number one of 1553 multiplex data bus 42. The PB0 output of interface 54 is next transitioned to the logic zero state, that is the PWR.sub.-- OFF/ON.sub.-- 1 line is set at a logic zero to turn power on.
The PB4 output (IPL.sub.-- 1 line) of programmable interface 54 is next set to a logic zero state allowing data to be loaded into the AN/AYK-14 avionics computer. The PB5 through PB7 outputs (IPL.sub.-- 2 through IPL.sub.-- 4 lines) operate in a similar manner with respect to avionics buses two through four bus of the 1553 multiplex data bus 42.
A logic one at the PC0 input (IPL.sub.-- FAIL.sub.-- 10 line of programmable interface 54 indicates that the program load for the AN/AYK-14 avionics computer 55 on avionics bus one has failed. Similarly, logic ones at the PC1 through PC3 inputs (IPL.sub.-- FAIL.sub.-- 2 through IPL.sub.-- FAIL.sub.-- 4 lines) indicate that program loads for the AN/AYK-14 avionics computers 55 on avionics buses two through four have failed.
The PC4-PC7 outputs of interface 54 are connected through the 54-56 terminals of connector 28 and the 54A-56A terminals of connector 29 to the A23-A25 address inputs of memory card zero and memory card one respectively of IC memory card 22.
The memory cards used in the present invention are Intel Series 2 Flash Memory Cards which conform to the Personal Computer Memory Card International Association (PCMCIA 2.0)/Japanese Electronics Industry Development Association (JEIDA 4.1) 68-pin standard. The three logic bits from the PC4-PC6 outputs of interface 54 when supplied to memory card zero and memory card one of IC memory card 22 allow for addressing of the eight pages of memory of each memory card of IC memory card 22 with each page of memory having 8 megabytes.
The PC7 output of interface 54 (MCS1/0 line) provides a logic signal which selects the memory card of IC memory card 22 to be accessed. The logic signal from the PC7 output of interface 54 is supplied to programmable array logic device 24 which decodes the signal and then provides a logic zero at the OUT4 output of device 24 (/MSC0 line) to enable memory card zero of IC memory card 22 or a logic zero at the OUT5 output of device 24 (/MSC1 line) to enable memory card one of IC memory card 22.
The PA0-PA4 inputs (FILTERED.sub.-- ACFT0 through FILTERED.sub.-- ACFT4 lines) of interface 52 provide signals from the aircraft to the rapid reprogramming terminal 20 which indicate the aircraft type. The FILTERED.sub.-- ACFT0 input is the least significant bit provided by the aircraft, while the FILTERED.sub.-- ACFT4 input is the most significant bit provided by the aircraft. For example a 1, 0, 1, 1, 0 respectively at the FILTERED.sub.-- ACFT0 through FILTERED.sub.-- ACFT4 inputs indicates that the aircraft is an F/A-18 fighter aircraft.
Switch 49, FIG. 2B, has a pair of momentary contacts, the first contact of which is connected to the PA6 input (EXEC.sub.-- SW line) of interface 52 and the second contact of which is connected to the PA7 input (SKIP.sub.-- SW) of interface 52. When switch 49 is activated to the EXEC position a logic zero pulse is provided to the PA6 input of interface 52 while activation of switch 49 to the SKIP position will result in a logic zero pulse at the PA7 input of interface 52.
The PB0-PB3 inputs (FILTERED.sub.-- CONFIG0 through FILTERED.sub.-- CONFIG3) of interface 52 provide signals from the aircraft to rapid reprogramming terminal 20 which indicate the aircraft avionics configuration such as whether the aircraft is an F/A-18A/B or F/A-18C/D.
The PB4 input (NO.sub.-- EXT.sub.-- BIT) of interface 52 is normally at the logic one state. An external bit connector may be connected to rapid reprogramming terminal 20 to provide a logic zero to the PB4 input of interface 52. This logic zero is supplied to digital signal processor 21 which then activates a test program (filename: ext.sub.-- bit.c of Appendix A) which is a self test verifying the integrity of rapid reprogramming terminal hardware.
The PB5 input (PPI3B5 line) of interface 52 is a spare.
The PB6 input (DOWNLOAD.sub.-- SW line) of interface 52 is connected to switch 47 such that whenever switch 47 is activated to the DOWN position a logic zero pulse is provided to the PB6 input of interface 56 which results in data being down loaded from, for example, an avionics remote terminal 53 to rapid reprogramming terminal 20. In a like manner, whenever switch 47 is activated to the UP position a logic zero is provided to the PB7 input of interface 56 which results in data being up loaded to, for example, an avionics bus controller 55 from rapid reprogramming terminal 20. Leaving switch 47 in a neutral position results in a verify operation occurring.
Referring to FIGS. 1, 16A, 16B, 16D, 16F and 17, the XFO output of digital signal processor 21 provides a hardware Reset (active high reset) for approximately 16 microseconds and then low again. The XFO output of digital signal processor 21 is connected to the RST inputs of UARTS 37 and 39, and the RESET input of all three programmable peripheral interfaces 52, 54 and 56 as well as the IN1 input of programmable array logic device 24.
The initialization of these peripherals configures the peripherals to accomplish specific functions. UART 37 is initialized as RS-232 Data Set Equipment (DSE) for the fastest baud rate the Data Terminal Equipment (DTE) will operate at allowing communications between rapid reprogramming terminal 20 and an external equipment such as an external computer. The second UART 39 is initialized as RS-422 Data Set Equipment also for the fastest baudrate the terminal will operate at to again allow communications between rapid reprogramming terminal 20 and RS-422 compatible equipment. Both UARTs 37 and 39 may be reconfigured for equipment loading, as specified by the IC memory card's contents, for those loads not transpiring over the MS-1553 bus. Programmable peripheral interfaces 52, 54 and 56 are configured to support discrete input or output functions as described in the rapid reprogramming terminal program of Appendix A. Programmable array logic device 24 decodes logic signals provided to the IN1-IN10 inputs thereof and then provides enable signals as well as read and write signals to memory card zero and memory card one of IC memory card 22 and EEPROMs 240, 241, 244 and 246 of EEPROM 23. Reprogrammable array logic device 24 also provides UARTs 37 and 39, FIG.16F, bus controller 260, FIG. 3, and controller 41, FIG. 16G.
Referring to FIGS. 3 and 16A the XFI output of digital signal processor 21 is connected to the PE input of transceiver 262 which along with transceiver 264 and bus controller 260 perform the interface function between digital signal processor 21 and an IEEE-488 bus and relieves processor 21 of the task of maintaining the IEEE-488 protocol. When the HS/PP line is high, transceiver 262 is in the high speed mode which causes data outputs B1-B8 of transceiver 262 (IEEE-488 .sub.-- DIO1 through IEEE-488 .sub.-- DIO8 lines) to be active high and active low. When the HS/PP line is low, transceiver 262 is in the parallel poll mode which requires the use of external pull up resistors connected to data outputs B1-B8 of transceiver 262 since data outputs B1-B8 of transceiver 262 transition to a tristate mode instead of an active high mode.
Referring to FIGS. 3, 16D and 16E, programmable array logic device 25 provides a logic zero /IEEE-488 .sub.-- SEL signal to the /CE input of bus controller 260 which allows access of the read and write registers of bus controller 260. Programmable array logic device 24 provides a logic zero /IOWR signal to the /WE input of bus controller 260 which allows data to be written into bus controller 260. Programmable array logic device 24 also provides a logic one IORD signal to the DBIN input of bus controller 260 which allows data to be read from bus controller 260 to digital signal processor 21.
Bus controller 260 provides at its /INT output a logic zero /INT1 signal which is supplied to digital signal processor 21 which is an interrupt to processor 21. The approximately one megahertz clock for bus controller 260 is provided by digital signal processor 21 at its CLKR0 output. The RS0-RS2 inputs of bus controller 260 receive address bits from digital signal processor 21 which determine the register of bus controller 260 digital signal processor 21 is addressing during a read or write operation. The D0-D7 terminals of bus controller 260 are bidirectional allowing bus controller 260 to receive data from digital signal processor 21 and transmit data to digital signal processor 21. The TE output of bus controller 260 provides a logic signal to the TE inputs of transceivers 262 and 264 to control the direction of transfer of transceivers 262 and 264 with a logic zero to the TE inputs of transceivers 262 and 264 causing transceivers 262 and 264 to function as receivers and a logic one causing transceivers 262 and 264 to function as transmitters. The /ACCGR input of bus controller 260 is connected to +5 VDC which prevents bus controller from participating in a DMA (Direct Memory Access) transfer to digital signal processor 21.
Transceiver 262 is bidirectional allowing transceiver to receive data at its B1-B8 terminals from an external device or transmit data to an external device. Transceiver 264 is also bidirectional allowing control signals to be transmitted and received by transceiver 262.
In accordance with the IEEE-488 standard the General Purpose Interface Bus allows up to 15 instruments or devices within a localized area to communicate with each other over a common bus. Each device on the IEEE-488 bus has a unique address to which it responds. Information is transmitted in byte serial bit format and may be either device-dependent data or interface messages, referred to as data or commands, respectively. Data may be sent by one device (the talker) and received by a number of other devices (listeners). One of the devices on the bus, designated the Controller in charge (Controller) may send interface control messages. Devices can be assigned to the bus as listeners or talkers by sending their unique talk or listen addresses. The control signals received and transmitted by transceiver 264 to the IEEE-488 bus are as follows:
TABLE I______________________________________Signal Description______________________________________DAV DATA VALID is a handshake signal controlled by a source to show acceptors when valid data is present on the bus.NDAC NOT DATA ACCEPTED is a handshake signal which the acceptor sets false when the acceptor latches data from the I/O lines.NRFD NOT READY FOR DATA is a handshake signal sent by the acceptor to indicate readiness for the next byte.ATN ATTENTION is a signal sent by the Controller in charge which when true (low) indicates that interface commands are being sent over the DIO lines and when false (high) indicates that the DIO lines are carrying data.IFC INTERFACE CLEAR is a signal sent by the system controller to set the interface system into a known quiescent state with the system controller becoming the Controller in charge.SRQ SERVICE REQUEST is a signal when set true (low) by a device indicates a need for service.EOI END OR IDENTITY is a signal which when ATN is high indicates the end of a message block and when ATN is low indicates that the controller is requesting a parallel poll./CONT This is a signal which indicates that a device is the Controller in charge.______________________________________
At this time it should be noted that the programmable array logic devices used in the preferred embodiment of the present invention are Advanced Micro Devices 28 Pin leadless chip carrier (LCC) TTL PALs Model No. PAL 20RA10. In it should be noted that the program listing for the software utilized by programmable array logic device 24 is set forth in Appendix B and the program listing for the software utilized by programmable array logic device 25 is set forth in Appendix C.
In addition, it should be noted that bus controller 260 is a Texas Instrument TMS9914A General Purpose Interface Bus Controller (GPIB) Controller, transceiver 262 is a Texas Instrument SN55ALS160 20 Pin LCC transceiver and transceiver 264 is a Texas Instrument SN55ALS161 20 Pin LCC transceiver.
Referring to FIGS. 1, 16B and 16C logic zero signals provided to the FSR0 and DR0 inputs of digital signal processor 21 indicate that memory card zero of IC memory card 22 is present, while logic zeros signals provided to the FSR1 and DR1 inputs of digital signal processor 21 indicate that memory card one of IC memory card 22 is present. For example, if a memory card is connected to connector 28 the /CARDO.sub.-- CD1 and /CARDO.sub.-- CD2 signal lines are active low.
There is also provided to the FSX0 and FSX1 inputs of digital signal processor 21 respectively by memory card zero and memory card one of IC memory card 22 a CARD0.sub.-- RDY/BSY signal and a CARD1.sub.-- RDY/BSY signal each of which when high indicate to digital signal processor 21 that the command previously supplied to the memory card is complete and when low indicate that the memory card is processing a command.
Memory cards zero and one of IC memory card 22 respectively provide CARD0.sub.-- WP and CARD1.sub.-- WP signals to digital signal processor 21 which when at the logic one state indicate to digital signal processor 21 that the memory card is write protected. Digital signal processor supplies to memory cards zero and one of IC memory card 22 respectively CARD0.sub.-- REG and CARD1.sub.-- REG signals which when supplied to the memory card at the logic zero state allows selection of the register set within the memory card and when high allows the selection of the memory plane within the memory card.
When the MCS1/0 signal line is high programmable array logic device sets the/MCS1 signal line to the logic zero state enabling memory card one of IC memory card 22. When the MCS1/0 signal line is low programmable array logic device sets the /MCS0 signal line to the logic zero state enabling memory card zero of IC memory card 22.
Addressing for memory cards zero and one of IC memory card 22 is provided by digital signal processor 21 through the A0-A25 terminals of connectors 28 and 29, while digital information is either read from or written into memory cards zero and one of IC memory card 22 through the DQ0-DQ15 terminals of connectors 28 and 29.
The system clock signal, which is 500 kilohertz, from the CLKR1 output of digital signal processor 21 is supplied to the TCKL0 and TCLK1 inputs of processor 21 to allow two 32 bit internal counter/timers within processor 21 to divide the system clock signal.
Referring to FIGS. 16B, 16D and 16E, programmable array logic device 24 provides a means whereby control signals from digital signal processor 21 are decoded to provide read, write and enable control signals for memory cards zero and one of IC memory card 22 and EEPROM 23 as well read and write signals to interfaces 52, 54 and 56; UART circuits 37 and 39 and bus controller 260.
Referring now to FIGS. 1, 16B, 16C and 16D the read (/RD), the write (/WR) and the EEPROM select (/EEPROM) signals are provided by programmable array logic device 24 to the four 64K.times.8 bit EEPROMs 240, 241, 244 and 246 of EEPROM 23 and the read (/RD), the write (/WR) and the memory card select (/MCS0 and/MCS1) signals to IC memory card 22 are provided by programmable array logic device 24. The read, the write and the EEPROM select signals provided to EEPROM 23 are active logic zero signals.
Addressing for EEPROMs 240, 241, 244 and 246 is provided by digital signal processor 21 through the A0-A15 inputs of EEPROMs 240, 241, 244 and 246, while digital information is either read from or written into EEPROMs 240, 241, 244 and 246 through the D0-D7 terminals of EEPROMs 240, 241, 244 and 246.
The A22 output of digital signal processor 21 provides a logic signal to the IN6 input of programmable array logic device 24 which determines whether IC memory card 22 or EEPROM 23 is being selected for a read or write operation with a logic zero indicating that the EEPROM 23 is selected and a logic one indicating that the IC memory card 22 is selected. The R/W signal provided from the R/W output of digital signal processor 21 to the IN3 input of programmable array logic device 24 indicates whether a read (logic one) or write (logic zero) operation is to be preformed by IC memory card 22 or EEPROM 23. The /STRB signal provided at the /STRB output of digital signal processor 21 to the IN3 input of programmable array logic device 24 indicates that the A22 and R/W signals are valid. The /STRB signal is active at the logic zero state.
The /EEPROM signal is supplied to the /CE input of EEPROMs 240, 241, 244 and 246 enabling EEPROMs 240, 241, 244 and 246. The /RD signal is supplied to the /OE inputs of EEPROMs 240, 241, 244 and 246 which in response to the /RD signal output data therefrom onto data lines D31-D0. The /WR signal is supplied to the /WE inputs of EEPROMs 240, 241, 244 and 246 which in response to the /WR signal stores data therein from data lines D31-D0.
The /IOSTRB signal provided from the /IOSTRB output of digital signal processor 21 to the IN5 input of programmable array logic device 25 indicates that the XR/W signal is valid and this /IOSTRB signal is active at the logic zero state. The XR/W signal which is provided from the XR/W output of digital signal processor 21 to the IN4 input of programmable array logic device 24 indicates whether a read or write operation is to be performed by programmable peripheral interfaces 52, 54 and 56 or universal asynchronous receiver transmitter (UART) circuits 37 and 39. When the XR/W signal is a logic one, the /IORD signal transitions to the logic zero state causing a read operation to be performed. When the XR/W signal is a logic zero, the /IOWR signal transitions to the logic zero state causing a write operation to be performed.
In addition, when the XR/W signal is a logic one and the /IOSTRB signal is a logic zero, the IORD signal provided at the OUT8 output of programmable array logic device 24 is an active logic one.
Referring to FIGS. 1, 16A, 16B and 17, digital signal processor 21 provides the eight bit data bytes, address and enable signals which selectively activate the outputs (PA0-PA7, PB0-PB7 and PC0-PC7) of programmable peripheral interfaces 52, 54 and 56. Specifically, the XD0-XD7 outputs of processor 21 provide digital data for the D0-D7 inputs of interfaces 52, 54 and 56, while the XA9 through XA12 outputs of processor 21 when decoded by programmable array logic device 25 determine which interface 52, 54 or 56 is to be enabled by providing a logic zero to the /CS (chip select) input of interface 52, 54 or 56.
Specifically, when the PPI1.sub.-- SEL line is to be at the logic zero state thereby enabling interface 56 address bits A12, A11, A10 and A9 will be respectively 0100. Similarly, when the PPI2.sub.-- SEL line is to be at the logic zero state thereby enabling interface 54 address bits A12, A11, A10 and A9 will be respectively 0101. In a like manner, when the PPI3.sub.-- SEL line is to be at the logic zero state thereby enabling interface 52 address bits A12, A11, A10 and A9 will be respectively 0110. The logic zero is supplied to the /CS input of interface 52, 54 or 56 enabling interface 52, 54 or 56. Interfaces 52, 54 and 56 each include three registers which are addressed by the XAO-AX1 outputs of digital signal processor 21. If the PA0 output (EW.sub.-- OSM.sub.-- EN line) of interface 54 is to be enabled, logic zeros will be provided from the XA0 and XA1 outputs of processor 21 to the A0 and A1 inputs of interface 54 and the DO input/output of interface 54 will be provided a logic one. Similarly, if the PB0 output (IPL.sub.-- 1 line) of interface 54 is to be enabled, a logic one will be provided from the XA0 output of processor 21 and a logic zero will be provided from the XA1 output of processor 21 respectively to the A0 and A1 inputs of interface 54 and the D4 input/output is provided with the logic signal to enable the PB0 output of interface 54. Likewise, if the IPL.sub.-- FAIL.sub.-- 1 input of interface 54 is to be read by digital signal processor 21, a logic zero will be provided from the XA0 output of processor 21 and a logic one will be provided from the XA1 output of processor 21 respectively to the A0 and A1 inputs of interface 54 and the DO input/output will be provided with the logic level of IPL.sub.-- FAIL.sub.--1 input.
The read and write signals for interfaces 52, 54 and 56 are provided by programmable array logic device 24. The read and write inputs to interfaces 52, 54 and 56 are active low, that is for digital signal processor 21 to read a logic signal provided to a programmable peripheral interface 52, 54 or 56 requires a logic zero at the /RD input of the interface. A logic zero at the /WR input of interface 52,54 or 56 transfers the logic zeros and ones at D0-D7 input/outputs of the interface to the PA0-PA7, PB0-PB7 or PC0-PC7 outputs of the interface depending upon the logic signals at the A0 and A1 inputs of the interface having data written therein.
Referring to FIGS. 3, 16A, 16B, 16E, 16F and 16G programmable array logic device 25 provides at its OUT1 output an active low /RS232.sub.-- SEL signal which is supplied to the /CSO input of UART 37 to enable UART 37. The /RS232.sub.-- SEL signal is active low whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0000. Similarly, programmable array logic device 25 provides at its OUT2 output an active low /RS422.sub.-- SEL signal which is supplied to the /CSO input of UART 39 to enable UART 39. The /RS422.sub.-- SEL signal is active low whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0001.
Programmable array logic device 25 provides at its OUT3 output an active low /MS1553.sub.-- SEL signal which is supplied to the /SELECT input of 1553 communications interface controller 41. The /MS1553.sub.-- SEL signal is active low whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0010 or 1XXX.
Programmable array logic device 25 provides at its OUT4 output an active low /MS1553.sub.-- REG signal which is supplied to the /MEM.sub.-- REG input of 1553 communications interface controller 41. The /MS1553.sub.-- REG signal is at the logic zero state whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0010. It should be noted that /MS1553.sub.-- REG signal is active low only when the /MS1553.sub.-- SEL signal is a logic zero. This logic zero /MS1553.sub.-- REG signal allows access to the register set of controller 41.
Whenever the address bits A12, A11, A10 and A9 are 1XXX the /MS1553.sub.-- SEL signal is active low and the /MS1553.sub.-- REG signal will be active at the logic one state. A logic one /MS1553.sub.-- REG signal allows access to the memory of controller 41.
Programmable array logic device 25 provides at its OUT5 output an active low /IEEE-488.sub.-- SEL signal which is supplied to the /CE input of bus controller 260 to enable bus controller 260. The /IEEE-488.sub.-- SEL signal is active low whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0011.
Programmable array logic device 25 provides at its OUT6, OUT7 and OUT8 outputs respectively active low signals PPI1.sub.-- SEL, PPI2.sub.-- SEL and PPI3.sub.-- SEL which enable interfaces 52, 54 and 56. The PPI1.sub.-- SEL signal is active low whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0100; the PPI2.sub.-- SEL signal is active low whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0101 and the PPI3.sub.-- SEL signal is active low whenever the address bits A12, A11, A10 and A9 provided by processor 21 are respectively 0110.
The 1553 communications interface controller 41 supplies an active low /READYD signal to the IN5 input of programmable array logic device 25; controller 41 supplies an active low /INT0 signal to the IN6 input of device 25 and digital signal processor 21 supplies the /IOSTRB signal to the IN7 input of device 25. The /READYD signal functions as an arbitrator allowing access to the memory of controller 41 by digital signal processor 21 and remote terminals or bus controllers on the 1553 multiplex data bus 42 aboard the aircraft. When /READYD signal is active low the /XRDY signal provided at the OUT9 output of device 25 is active low. This active low signal is supplied to /XRDY input of digital signal processor 21 indicating to processor 21 that processor 21 may now access the memory of controller 41.
The /INT.sub.-- ACK signal which is generated in response to the /INT0 signal supplied by controller 41 and which occurs at the OUT10 output of device 25 is not being used by rapid reprogramming terminal 20.
Whenever any of the select signals are active low, e.g. /RS232.sub.-- SEL signal, the /XRDY signal is active low. However, whenever the /MS1553.sub.-- SEL signal is low, the /READYD signal must be active low for the /XRDY signal to be active low.
The /IOSTRB signal is used to validate the address bits A12, A11, A10 and A9 provided by processor 21 thereby allowing programmable array logic device 25 to decode address bits A12, A11, A10 and A9 and then generate one of the select signals provided by device 25.
Referring now to FIGS. 2A and 13, there is shown the power supply 160 for rapid reprogramming terminal 20 which includes an electromagnetic interference filter 162 for providing a filtered 28 VDC signal (28 VDC.sub.-- FILTERED). Power supply 160 further includes a pair of DC to DC converters 166 and 168 with power supply 166 providing plus and minus 12 VDC and power supply 168 providing a plus 5 VDC.
Power supply 160 also provides the power for the backlighting for liquid crystal display 57. The backlighting for liquid crystal display 57 requires approximately 3.5 volts at between 300 to 400 milliamps. Plus 12 VDC is supplied through a 10 ohm resistor to the LED.sub.-- BRIGHT.sub.-- PWR output of supply 160 resulting in a DC voltage which is approximately 3.5 volts above the LED.sub.-- PWR.sub.-- RTN input of supply 160. Power supply 160 also provides a lower voltage differential between its LED.sub.-- PWR output and its LED.sub.-- PWR.sub.-- RTN input which may be used to dim the backlighting of liquid crystal display 57.
Referring now to FIGS. 1, 16B and 16f, there is shown the universal asynchronous receiver transmitter (UART) circuits 37 and 39 which in the preferred embodiment of the present invention are model number 82C52 CMOS serial control interfaces manufactured by Harris Corporation although it should be understood that any controller interface which is compatible with standard RS-232-C baud rates may be used as UARTS 37 and 39. UARTS 37 and 39 are used to communicate with devices external to rapid reprogramming terminal such as computer/data terminal 66 via the standard RS-232 and RS-422 serial communications protocol.
Digital data is supplied from the SD0 output of UART 37 through line driver 250 to computer 66 via the RS.sub.-- 232.sub.-- TX data transmission line. Similarly, digital data is supplied from computer 66 via the RS.sub.-- 232.sub.-- RX data receive line through line receiver 252 to the SDI input of UART 37. When rapid reprogramming terminal 20 is turned on, a data set ready signal (active logic one) is provided from the /DTR output of UART 37 through driver 250 via the RS.sub.-- 232.sub.-- DSR data line to computer 66 indicating to computer 66 that rapid reprogramming terminal 20 is powered up. Computer 66 provides a data terminal ready signal (active logic one) via RS.sub.-- 232.sub.-- DTR data line through receiver 252 to the /DSR input of UART 37 which indicates to rapid reprogramming terminal 20 that computer 66 is operational and ready to send or receive data. When computer 66 is ready to send data, computer 66 provides a request to send signal (active logic one) via RS.sub.-- 232.sub.-- RTS data line through receiver 252 to the /CTS input of UART 37 which indicates to rapid reprogramming terminal 20 that computer 66 is ready to transmit data. Rapid reprogramming terminal 20 responds with a clear to send signal provided from the /RTS output of UART 37 through driver 250 via the RS-232.sub.-- CTS data line to computer 66. When digital data from rapid reprogramming terminal 20 is to be provided to computer 66 the only requirement is that the data terminal ready signal be at the logic one state indicating that computer 66 is ready to receive data. The transmission of data to and from rapid reprogramming terminal 20 via the RS-422 data bus is similar to the transmission of data via the RS-232 data bus and therefore will not be discussed in detail.
UARTS 37 and 39 include read (/RD) and write (/WR) inputs and a chip select (/CS0) input. The /IORD read signal is provided by programmable array logic device 24 to UARTS 37 and 39 to read the receiver and status registers of UARTS 37 and 39, while the /IOWR write signal is provided by programmable array logic device 24 to UARTS 37 and 39 to write data into the transmitter and control registers of UARTS 37 and 39. The /CS0 input when at the logic zero state acts as an enable signal for the read and write operations of UARTS 37 and 39. The read operation for UARTS 37 and 39 reads the digital data stored in the UART into digital signal processor 21, while the write operation writes digital data from digital signal processor 21 into the UART. UARTS 37 and 39 also receive a 12 MHZ clock signal provided by an oscillator 40, FIG. 16H. It should also be noted that UARTS 37 and 39 are provided logic signals to the A0 and A1 inputs thereof which when decoded address four internal registers within UARTS 37 and 39. Specifically, when A1, A0 is 0,0 the buffer register which receives and sends data is addressed; when A1, A0 is 0,1 the control register (write only register which configures the UART transmitter and receiver circuits) is addressed with a write and the status register (read only register that is examined by the UART to determine errors) is addressed with a read; when A1, A0 is 1,0 the modem control register is addressed and when A1, A0 is 1,1 the baud rate is selected with a write operation and the modem status register is addressed with a read operation.
Rapid reprogramming terminal 20 also has five terminals EMU0-EMU3 and H3 for communicating with an emulator 67 which is connected to external computer 66. Emulator 67 may be used for debugging rapid reprogramming terminal 20 and for the initial loading of the RRT software program into the EEPROM 23 of rapid reprogramming terminal 20. It should be noted that the emulator used in the preferred embodiment of the present invention is a Texas Instrument Model No. TMS 320C30 XDS500 Emulator, although any IBM PC-XT/AT compatible TMS320C30 emulator may be used in the preferred embodiment of the present invention. It should be further noted that external computer 66 may be any IBM PC-XT/AT compatible computer.
Referring to FIGS. 1 and 14a, there is shown the avionics interface 170 of rapid reprogramming terminal 20 which includes a pair of differential line drivers 172 and 174 with driver 172 providing the unipolar differential signals +IPL.sub.-- 1, -IPL.sub.-- 1 through +IPL.sub.-- 4, -IPL.sub.-- 4 to the 1553 avionics buses one through four which are required to initiate program loading of the AN/AYK-14 avionics computers on buses one through four. Driver 174 provides the unipolar differential signals +AV.sub.-- EN1, -AV.sub.-- EN1 and +AV.sub.-- EN2, -AV.sub.-- EN2 to enable memory areas one and two of remote terminals 53 and bus controllers 55 on the 1553 avionics buses one through four.
The avionics interface 170 also includes a differential line receiver 176 which receives the unipolar differential signals +IPL.sub.-- FAIL.sub.-- 1, -IPL.sub.-- FAIL.sub.-- 1 through +IPL.sub.-- FAIL.sub.-- 4, -IPL.sub.-- FAIL.sub.-- 4 (indicative of an initiate program load failure to an AN/AYK-14 computer) and converts the signals to binary signals IPL.sub.-- FAIL.sub.-- 1 through IPL.sub.-- FAIL.sub.-- 4. Avionics interface 170 further includes a power driver 178 which has four inputs PWR.sub.-- OFF/ON.sub.-- 1 through PWR.sub.-- OFF/ON.sub.-- 4 respectively connected to the PWR.sub.-- OFF/ON.sub.-- 1 through PWR.sub.-- OFF/ON.sub.-- 4 outputs of interface 54, FIG. 17. When a five volt logic one signal is applied to the PWR.sub.-- OFF/ON.sub.-- 1 of driver 178 the OUT1 output of driver 178 is pulled to ground the coil in relay 180 is energized closing a normally open contact within relay 180 (NO1 to S1 is shorted) which turns off the AN/AYK-14 computer on avionics bus one. It should be noted that relays 182, 184 and 186 operate in an identical manner with respect to turning off the AN/AYK-14 computers on avionics buses two through four.
Referring to FIGS. 1 and 14b, when a logic one is provided from the AV1 output of interface 56, FIG. 17, to the IN1 input of power driver 188, the OUT1 output of driver 188 is driven to ground providing a ground to the coils of relays 192 and 200 thereby energizing the coils of relays 192 and 200. Energizing the coils of relays 192 and 200 connects the primary avionics bus one and the secondary avionics bus one on the aircraft to the rapid reprogramming terminal 20.
It should be noted that the 1553 multiplex data bus 42 is a dual redundant differential bus with differential data signals (+MUX.sub.-- BUS, -MUX.sub.-- BUS signals) that are Manchester mark encoded Military Standard 1553 signals. Thus, energizing any of the primary avionics bus relays 190, 192, 194, 196 and 198 allows data to be transmitted to and from the primary avionics bus associated with that particular relay. Similarly, energizing any of the secondary avionics relays 200, 202, 203, 204 and 206 allows data to be transmitted to and from the secondary avionics bus associated with that particular relay. For example, if the AN/AYK-14 computer on avionics bus number four is to be reprogrammed, a logic one is provided to the IN4 input of driver 188 which energizes the coils of relays 198 and 204 which allows rapid reprogramming terminal 20 to communicate with the AN/AYK-14 computer on avionics bus number four so that this AN/AYK-14 may be reprogrammed.
Referring to FIGS. 1, 15a and 17, there is shown the electronic warfare interface 211 of rapid reprogramming terminal 20 which includes a power driver 212 having an IN4 input which when supplied a logic one from the PA0 output of interface 56 results in a logic zero at the OUT4 output of driver 212. This logic zero when supplied to the COIL-input of relay 218 energizes the coil of relay 218. When the PB0 output of interface 56 (DIR/XFMR line) is at the logic one state the OUT1 output of driver 212 goes to ground energizing the coil of relay 217 closing normally open contacts one and two of relay 217. This allows Manchester encoded data from of 1553 communications interface controller 41 to pass through transformer 213, relays 217 and 218 to a remote terminal 53 or bus controller 55 on the electronics warfare bus.
Similarly, when the PB0 output of interface 56 is at the logic zero state the OUT1 output of driver 212 is open de-energizing the coil of relay 216 leaving the normally closed contacts one and two of relay 216 closed such that data provided from controller 41 will pass through transformer 213, relays 217 and 218 and a transformer 60, FIG. 4, to a remote terminal 53 or bus controller 55 on the electronics warfare bus.
It should be noted that whenever it is required to ground the center tap of transformers 213 and 214, a logic one is supplied to the GND/OPEN.sub.-- CT of driver 212 from the PB1 output of interface 56. This results in a ground at the OUT2 output of relay 214 energizing the coil of relay 214 which closes the normally open contacts one and two of relay 214. This brings the CT and GND terminals of transformer 213 and 214 to ground level, thus grounding the center tap of transformers 213 and 214. It should be further noted that the center tap of transformers 213 and 214 is generally grounded when coupling to the 1553 multiplex data bus 42 is through a pair of transformers 60 if the remote terminal 53 or bus controller 55 requires grounding.
Relays 220, 222 and 224 function in manner similar to relay 218. For example, if it is desired to reprogram the stores management system aboard an aircraft a logic one will be provided at the PB4 output (BOOT.sub.-- EN.sub.-- SMS line) of interface 56. A logic one at this output is supplied to the IN5 input of driver 212 resulting in a ground at the OUT5 output of driver 212. This energizes the coil of relay 220 closing normally open contact one of relay 220 enabling the stores management system boot loader allowing data to be transferred from rapid reprogramming terminal 20 to the stores management system aboard the aircraft.
Referring to FIG. 1, 15b and 17 operating system memory of all avionics EW equipment, user data memory of all avionics EW equipment and the AN/ALQ-165 radar jammer are respectively enabled by logic ones provided at the IN1, IN2 and IN3 inputs driver 226. This energizes either relay 228, 230 or 232, which respectively enables either the operating system memory of all avionics EW equipment, user data memory of all avionics EW equipment or the AN/ALQ-165 radar jammer which communicate via the electronic warfare bus aboard the aircraft.
Referring to FIGS. 1, 15a, 16a, 16b, 16g and 16h, when, for example, an aircraft avionics bus AN/AYK-14 computer is to be reprogrammed, the 1553 communications interface controller 41 will convert parallel data supplied to its D0-D15 inputs by digital signal processor to Manchester encoded differential data for transfer via the MS-1553 multiplex data bus to the AN/AYK-14 computer being reprogrammed. Since the MS-1553 multiplex data bus is a dual redundant bus having a primary and secondary data bus, Manchester encoded differential data will be provided at the TX.sub.-- RX.sub.-- A and /TX.sub.-- RX.sub.-- A outputs of controller 41 to transformer 213 as well as the TX.sub.-- RX.sub.-- B and /TX.sub.-- RX.sub.-- B outputs of controller 41 to transformer 214. Transformers 213 and 214 convert the Manchester encoded differential data to Manchester encoded differential data which is compatible with aircraft using isolation transformers (Long Stub Coupling Transformers, FIG. 4) and aircraft which do not use isolation transformers (Short Stub Direct Coupling, FIG. 4). The Manchester encoded differential data is next supplied through relays 216 and 217 to the NO1 and NO2 inputs of primary bus relays 190, 192, 194, 196, 198 and 218 and the NO1 and NO2 inputs of secondary bus relays 200, 202, 203, 204 and 206. When, for example, the AN/AYK-14 computer to be reprogrammed is coupled to the aircraft's Primary and Secondary Avionics Bus Number One, relays 192 and 200 are energized. This allows the Manchester encoded differential data to pass through relay 192 (primary bus relay) and relay 200 (secondary bus relay) to the AN/AYK-14 computer being reprogrammed.
The 1553 communications interface controller 41 used in the preferred embodiment of the present invention is a ILC Data Device Corporation Model BU-65190 ACE Series BC/RT/MT Advanced Communication Engine Integrated 1553 Terminal. The BU-65190 comprises an integrated interface between a host processor and a MIL-STD-1553 bus which provides bus controller, remote terminal and monitor terminal functions and is in compliance with MIL-STD 1553 and McAir electrical and protocol requirements.
The 1553 communications interface controller 41 has 32 internal registers of which 16 internal register are being utilized in the preferred embodiment of the present invention. The internal registers of controller 41 characterized the controller as a bus controller, remote terminal or monitor terminal.
The following table identifies the address for each of the internal registers of 1553 communications interface controller 41 which are used during the operation of controller 41.
TABLE II______________________________________ADDRESSINPUTS REGISTERA4 A3 A2 A1 A0 DESCRIPTION/ACCESSIBILITY______________________________________0 0 0 0 0 Interrupt Mask Register (RD/WR)0 0 0 0 1 Configuration Register 1 (RD/WR)0 0 0 1 0 Configuration Register 2 (RD/WR)0 0 0 1 1 Start/Reset Register (WR)0 0 0 1 1 Command Stack Pointer Register (RD)0 0 1 0 0 BC Control Word/RT Subaddress Control Word Register (RD/WR)0 0 1 0 1 Time Tag Register (RD/WR)0 0 1 1 0 Interrupt Status Register (RD)0 0 1 1 1 Configuration Register 3 (RD/WR)0 1 0 0 0 Configuration Register 4 (RD/WR)0 1 0 0 1 Configuration Register 5 (RD/WR)0 1 0 1 1 Monitro Data Stack Address Register (RD/WR)0 1 0 1 1 BC Frame Time Remaining Register (RD)0 1 1 0 1 BC Time Remaining to Next Message Register (RD/WR)0 1 1 0 1 BC Frame Time/RT Last Command/MT Trigger Word Register (RD/WR)0 1 1 1 0 RT Status Word Register (RD)0 1 1 1 1 RT BIT Word Register (RD)______________________________________
The /MS1553.sub.-- SEL and /MS1553.sub.-- REG logic signals provided by programmable array logic device 25, FIG. 16E are used to access the 16 internal registers of Table II. When the /MS1553.sub.-- SEL signal is active low, controller 41 is accessed with the logic state of the /MS1553.sub.-- REG signal determining whether the 16 internal register of controller 41 is being accessed or the 4K of controller internal memory is being accessed. A logic zero at the /MEM-REG input of controller 41 allows access to the 16 internal registers of controller 41, while a logic one at the /MEM-REG input of controller 41 allows access to the 4K of internal memory of controller 41.
Referring to Appendix D, Configuration Registers 2, 3, 4 and 5 are used when rapid reprogramming terminal 20 is powered on to initialize controller 41. Configuration Register 1 characterizes controller 41 as a bus controller, remote terminal or a monitor terminal when communicating with the MS-1553 multiplex data bus.
Whenever the bits of Configuration Register 1 are set at zero, that is data bits 15-0 are zero, controller 41 is functioning as a bus controller.
BC Control Word Register sets up controller 41 for Bus A (primary bus on the MS-1553 multiplex data bus) or Bus B (secondary bus on the MS-1553 multiplex data bus) operation. For primary bus operation bit 7 of the sixteen bit control word supplied to the D0-D15 inputs of controller 41 is set to the logic zero state. For secondary bus operation bit 7 of the sixteen bit control word supplied to the D0-D15 inputs of controller 41 is set to the logic one state.
The BC Frame Time Remaining Register, BC Message Time Remaining Register and the BC Frame Time Register are not used in the preferred Embodiment of the present invention. Digital signal processor 21 provides the timing requirements normally implemented by these registers. The RT Status Word Register is used to monitor the status of the remote terminal 53 communicating with controller 41.
Whenever Configuration Register 1 of controller 41 is set up to have a hexadecimal value of 8000 or 8F80 controller 41 is functioning as a remote terminal. It should be noted that data bit 15 of Configuration Register 1 is set at the logic one state when controller 41 is functioning as a remote terminal. The address for controller 41 when functioning as a remote terminal is supplied to the RTAD0-RTAD4 inputs thereof from interface 56.
When the control word provided to Configuration Register 1 has the hexadecimal value of 8F80 controller 41 is configured to operate on the primary and secondary buses on the MS-1553 multiplex data bus. This provides for an automatic operation with respect to certain status bits of a remote terminal status word.
When the control word provided to Configuration Register 1 has the hexadecimal value of 8000 controller 41 is configured to operate on, for example, the McAir bus. Operation of controller 41 on the McAir bus requires digital signal processor 21 to have direct control over remote terminal status word bits.
Whenever Configuration Register 1 of controller 41 is set up to have a hexadecimal value of 5600 controller 41 is functioning as a monitor terminal.
The Interrupt Mask Register is not used in the preferred embodiment of the present invention. When digital signal processor 21 provides control words hexadecimal 0004 and 0002 to the Start/Reset Register of controller 41, controller 41 first resets the Interrupt Status Register to hexadecimal 0000, controller then starts sending or receiving messages.
The BC/RT Command Stack Pointer Register is used for memory access of controller 41. The Command Stack Pointer Register, which is a read only register, allows Digital Signal Processor 21 to determine the pointer location in memory for the current or most recent message when controller 41 is functioning as a remote terminal or bus controller.
Controller 41 has a Stack A and a Stack B in memory with the controller of the present invention using only Stack A. The value of the command stack pointer is read from the Command Stack Pointer Register by digital signal processor. This identifies the current location in the command stack controller 41 is accessing. The command stack consist of 256 16 bit words with the starting address within controller 41 for the command stack being address zero (address lines XA0-XA11).
When, for example, controller 41 is operating as a remote terminal, reading the Command Stack Pointer Register provides the pointer location for the current or most recent message Block Status Word, Time Tag Word, Data Block Pointer and Receive Command Word. The Block Status Word, in turn, contains the message block status, the Time Tag Word is not used, the Data Block Pointer is the Data Block Address within memory and the Receive Command Word is the address of the location within the Look-up Table of the Data Block Pointer.
Rapid reprogramming terminal 20 utilizes a software program which comprises the modules illustrated in FIG. 6 and as well as the modules set forth in the table below:
TABLE III__________________________________________________________________________RRT.CMD RRT.MAP DSPINIT.ASM SYSINIT.ASMVECTORS.ASM RRT.H DAP.H BOOT.HBOOT.C SERIALIO.H SERIALIO.C DISPLAY.HDISPLAY.C PROGRAM.H PROGRAM.C BIT.HBASICBIT.C CARDHDRS.H RRT.sub.-- MAIN.H RRT.sub.-- MAIN.CEXT.sub.-- BIT.C CMDMODE.H CMDMODE.C UPLOAD.HUPLOAD.C DOWNLOAD.H DOWNLOAD.C COPY.HCOPY.C ERASE.H ERASE.C SWITCHES.HSWITCHES.C MS1553.C RRT.sub.-- BIT.C RRT.sub.-- MAIN.CWORDTYPE.H CONTROL.H CONTROL.C INITPROT.HINITPROT.C PROTOB.H PROTOB.C MSGS.sub.-- B.HMSGS.sub.-- B.C PROTOC.H PROTOC.C MSGS.sub.-- C.HMSGS.sub.-- C.C PROTOD.H PROTOD.C MSGS.sub.-- D.HMSGS.sub.-- D.C PROTOE.H PROTOD.C MSGS.sub.-- E.HMSGS.sub.-- E.C PROTOF.H PROTOD.C MSGS.sub.-- F.HMSGS.sub.-- F.C PROTOG.H PROTOD.C MSGS.sub.-- G.HMSGS.sub.-- G.C PROTOH.H PROTOD.C MSGS.sub.-- H.HMSGS.sub.-- H.C PROTOUL.H PROTOD.C MSGS.sub.-- UL.HMSGS.sub.-- UL.C PROTOU2.H PROTOD.C MSGS.sub.-- U2.HMSGS.sub.-- U2.C MEMCARD.H MEMCARD.C MS1553.HMS1553.C IEEE488.H IEEE488.C INTERPTS.HINTERPTS.C TIMER.H TIMER.C ERROR.HERROR.C__________________________________________________________________________
A complete program listing for each of the program modules of Table III is set forth in Appendix A.
The software of Appendix A includes three types of program modules the first module type being a filename.c module which is a C listing code, the second module type being a filename.asm module which is an assembly language code and the third module type being a filename.h module which are header files which contain definitions, structures and function prototypes for the filename.c modules.
The rrt.cmd file of the software of Appendix A is the linker command file which instructs the linker as to the placement of the software files in the memory of digital signal processor 21, while the rrt.map is the linker map file.
The dspinit.asm file initializes digital signal processor 21. The dspinit.asm file is the entry point for the rapid reprogramming terminal program of Appendix A. The dspinit.asm file establishes interrupt vectors, initializes internal registers within digital signal processor 21, calls an auto-initialization routine which moves variables from ROM to RAM within digital signal processor 21 for usage by processor 21, initializes internal control registers within processor 21, and calls a system initialization routine for rapid reprogramming terminal 20. A description of each section of the dspinit.asm file follows.
The Processor Global Declarations contain declarations of two types, defined globals which are labels defined by the dspinit.asm file and used by other modules and referenced globals which are labels used by the dspinit.asm file that were defined by another module.
The reset and interrupt vector specification contains values or references used to established vectored entry points throughout the rapid reprogramming terminal program. This section's "int-vecs" (interrupt vectors) are mapped into the lower part of program memory by the linker through its interpretation of the linker command file (rrt.cmd file).
The Stack, DMA, Timer 0, Timer 1, Serial Port 0 and Serial Port 1 sections of dspinit.asm contain references used to establish the location of internal registers of digital signal processor 21 throughout the program. These register locations are defined in the linker command file.
The data constants define values used in initializing the internal registers of the digital signal processor 21 with the specific function of each value being described in the module.
Once the stack pointer, frame pointer, cache, and interrupts are established for digital signal processor 21 an auto-initialization takes place. Auto-initialization is the process of moving variables defined in the ROM of processor 21 into the RAM of processor 21 where these variables can be manipulated. The location in the internal digital signal processor 21 RAM is established in the linker command file.
The defined data constants are then stored into their appropriate locations, completing the process of initializing the various Digital Signal Processor 21 internal control registers leaving only the initialization of the external system components prior to entering the main program.
The sysinit.asm file is the rapid reprogramming terminal initialization module of the software of Appendix A. The sysinit.asm file is the system initialization routine which performs a hardware reset and initializes the registers of all peripheral devices.
Hardware Reset is performed by taking a dedicated output discrete high (active high reset) and then low again. This discrete (XF0 output of digital signal processor 21) is connected to programmable array logic device 24 which inverts the logic one RESET signal to a logic zero RESET signal. The logic one RESET signal is also supplied to UARTS 37 and 39, all three programmable peripheral interfaces 52, 54 and 56, and both IC memory cards of IC memory card 22 while the logic zero /RESET signal is supplied to 1553 communications interface controller 41 and bus controller 260, initializing each of these peripherals of rapid reprogramming terminal 20.
The vectors.asm file is a file containing pointers to the location of interrupt routines in program memory and the code that performs the autoinitialization.
The rrt.h file is a universal program definition file; the dsp.h file comprises the definitions and structures for initializing the digital signal processor 21 and the system.h file comprises the system definitions and structures that relate to the peripherals external to digital signal processor 21 such as UARTS 37 and 39.
The boot.h file comprises definitions and function prototypes for the boot.c module.
The boot.c file is the boot-strap loader module. The boot.c file along with the program.c file are the update modules for the rapid reprogramming terminal program. The boot.c file of the rapid reprogramming terminal software functions to transfer data from a serial port such as the RS-232 port or an IC memory card of IC memory card 22 into the EEPROM 23 of rapid reprogramming terminal 20 and also reboots or starts the program. The program.c file displays an update prompt on a video screen 69 and/or the LCD display 57, transfers the boot.c code into the RAM of processor 21 for execution and then proceeds to upload a new program into program memory (the EEPROM 23) by executing the boot.c code using a modified form of the Hex-32 format designed by Intel Corporation.
The data contained in the modified Intel Hex-32 format represents 32 bit words with the most significant byte coming first. Once a proper record is received the data in the word oriented data record (type 00) is transferred to program memory.
It should be noted that for the purpose of loading the rapid reprogramming terminal software into rapid reprogramming terminal 20, the Intel format illustrated in FIG. 5 is modified by replacing the byte count with a word count. The Intel format of FIG. 5 is used as illustrated for all upload and download functions between data terminal 66 and IC memory card 22.
Referring to FIG. 5, the Intel 32-bit Hexadecimal Object file record format or the modified format each have a nine character (four field) prefix that defines the start of record, byte count or word count, load address, and record type and a two character checksum suffix. FIG. 5 illustrates the sample records of the Intel format. The six record types for the Intel HEX-32 format are 00 (data record), 01 (end of file record), 02 (extended segment address record), 03 (start segment address record), 04 (extended linear address record) and 05 (start linear address record).
The data record begins with a colon start character, which is followed by the word or byte count which is in hexadecimal notation, the address of the first data word or byte, and the record type which is "00". The data bytes are next in the data record. The checksum follows the data bytes and is the two's complement in binary of the preceding bytes in the record, including the word or byte count, address, record type and data bytes.
The end-of-file record also begins with the colon start character and is followed by the word or byte count (equal to "00"), the address (equal to "0000"), the record type (equal to "01") and the checksum, "FF".
The address contained in the extended segment address record is shifted left four places and added to the address to determine the absolute destination address. The address field for this record must contain ASCII zeros (Hexadecimal 30's). The extended segment address record defines bits 4 to 19 of the segment base address. This record type can appear randomly anywhere within the object file and affects the absolute memory address of subsequent data records in the file.
The start segment address record, which specifies bits 4-19 of the execution start address for the object file, is not used by rapid reprogramming terminal 20.
The extended linear address record specifies bits 16-31 of the destination address for the data records that follow. The address contained in this record is shifted left 16 places and added to the address to determine the absolute destination address, and can appear randomly anywhere within the object file. The address field for this record must contain ASCII zeros (Hexadecimal 30's).
The start linear address record, which specifies bits 16-31 of the execution start address for the object file, is not used by rapid reprogramming terminal 20.
It should be noted that the software of Appendix A is readable from EEPROM 23. With the exception of the boot.c file, the software of Appendix A is executable from EEPROM 23. The boot.c file is transferred to the RAM of processor 21 for execution since the boot.c code programs EEPROM 23 and cannot be read for execution from EEPROM 23. The program.c module transfers the boot.c module to the RAM of digital signal processor 21.
The serialio.h comprises the RS-232 and RS-422 driver definitions and function prototypes. The serialio.c file of the rapid reprogramming software is the RS-232 and RS-422 driver modules which contains routines used to transfer data to and from the RS-232 and RS-422 data buses.
The EIA RS-232 data bus protocol or interface is a conventional, well known, widely used and popular data bus protocol which provides an interface between data terminal equipment and data communications equipment using serial binary data exchange. It may typically be used to interface a computer such as data terminal 66 and a peripheral device such as a modem, mouse, drawing tablet or printer and typically uses a 25 pin DB-25 or a 9 pin DB-9 connector. It normally has a cable length limitation of 50 feet. The RS-232 interface standard specifies the electrical signal characteristics, connector pin assignments and functional interchange circuit descriptions for serial binary exchange.
The RS-422 is an EIA standard for serial transmission that extends the distances and speeds beyond the RS-232 standard.
The routines used by the serialio.c module for the RS-232 interface are a Get Byte routine which inputs data bytes by constructing the byte from nybles obtained from the Get Nyble routine; a Get Nyble routine which inputs data nybles obtained from ASCII characters returned by an RS232 Receive routine; a Put Byte routine which outputs bytes by constructing nybles and sending them through a Put Nyble routine; a Put Nyble routine which outputs nybles by constructing ASCII characters and then outputs the nybles through the RS232 Send routine; a RS232 Receive routine which inputs ASCII characters by first testing the UART status until a character is received and then getting the character from the RS232 Data routine and an RS232 Data routine which inputs ASCII characters directly from the UART receive register without testing any UART status bits other that those indicating if an error (overrun, parity, etc.) has occurred. Further, the serialio.c module for the RS-232 interface uses a RS232 Send routine which outputs ASCII characters by first testing for a busy (the RS-232 interface might be sending data) and if busy prevents a receive overrun and when not busy a receive is enabled and data is sent. The serialio.c module for the RS-232 interface also uses a String Send routine which outputs ASCII strings by first testing the busy status to ensure that each character can be sent.
The display.h file comprises the liquid crystal display driver definitions and function prototypes. The display.c module performs two functions with respect to liquid crystal display 57 in that it provides for the initialization of liquid crystal display 57 and for the alpha numeric display provided to the operator by liquid crystal display 57. The initialization function of the display.c module clears liquid crystal display 57 and sets up display 57. It should be noted that liquid crystal display 57 provides two lines of alpha numeric display characters with each line having twenty alpha numeric characters for display. The display function provides for two arguments for the function call, the second argument being the string of alpha numeric characters to be displayed by liquid crystal display and the first argument being the starting location of the string of alpha numeric characters to be displayed by liquid crystal display 57.
Three control characters, form feed (f), tab (t) and line feed (n), are used to facilitate displaying messages with the liquid crystal display. The form feed character (f) causes the display 57 to be cleared, the tab character (t) causes the remaining characters in the current line from the current location in the line to be cleared, and the line feed character (n) causes the remaining characters in the string to be displayed beginning at the start of the second line of liquid crystal display 57.
The program.h file is the prototype for the program.c (boot.c loader) function. The program.c file comprises the code for,transferring the boot.c file from EEPROM 23 into the RAM of digital signal processor 21. This allows rapid reprogramming terminal to reprogram the software of Appendix A with the exception of certain start up modules consisting of dspinit.asm, sysinit.asm, boot.c, serialio.c, display.c, program.c and basicbit.c.
The bit.h file comprises the rapid reprogramming terminal built in test functions definitions and function prototypes. The basicbit.c file provides for a rapid reprogramming terminal controller built-in-test function. The basicbit.c code tests the liquid crystal display 57, UARTs 37 and 39, bus controller 41, interfaces 52, 54 and 56, EEPROM 23 which consists of EEPROMs 240, 241, 244 and 246 and the IEEE-488 interface bus controller 260.
The ext.sub.-- bit.c module is a rapid reprogramming terminal system built in test function which again test the electronics components tested by the basicbit.c module as well as the remaining electronic components of rapid reprogramming terminal 20. The ext.sub.-- bit.c module provides for failure code display which identifies the failure to an operator on screen 69. The operator may then either skip the failure code displayed on screen 69 by activating switch 49 to the "skip" position or the operator may use switch 49 to continue with the system built in test function by activating switch 49 to the "exec" position. It should be noted that testing of rapid reprogramming terminal occurs upon turning on power (activating switch 44) to rapid reprogramming terminal 20.
The cardhdrs.h file comprises memory card format and definitions for Military Standard 2217 implemented by the software of Appendix A.
The rrt.sub.-- main.h file is a background executive function prototype for the rrt.sub.-- main.c file. The rrt.sub.-- main.c file provides rapid reprogramming terminal 20 with a means for polling the RS-232 and RS-422 interfaces and look for a sequence of ASCII characters (+++) from a data terminal such as data terminal 66, FIG. 1. Upon detecting the ASCII characters +++ rapid reprogramming terminal enters its command mode software. The rrt.sub.-- main.c file allows rapid reprogramming terminal 20 to test memory card 22 to see if the card is a program card. If the memory card 22 is a program card rapid reprogramming terminal may then update its software in EEPROM 23 from the code that is on the memory card. It should be noted that the boot.c file allows for reprogramming of rapid reprogramming terminal 20 either via the RS-232 interface or memory card 22.
The cmdmode.h file is the command mode function prototype for the cmdmode.c file.
The cmdmode.c module interfaces a keyboard 62 with rapid reprogramming terminal 20 to allow a user/operator to enter commands into the rapid reprogramming terminal 20. When the user enters "+++" into rapid reprogramming terminal 20 via keyboard 62 a Command Mode menu will appear on video screen 69. The Command Mode menu includes the following UP LOAD (U), DOWNLOAD (D), ERASE (E), PROGRAM (P), APPEND(A) COPY (C), VERIFY (V) and ESCAPE. When the user enters a "U" via the keyboard 62, digital data is transferred from an external computer 66 through either the RS-232 or RS-422 interfaces to IC memory card 22. Similarly, when the user enters a "D" via the keyboard 62, digital data is transferred from IC memory card 22 through either the RS-232 or RS-422 interfaces to external computer 66.
An "E" entered by the user via keyboard 62 erases IC memory card 22. Entering a "P" via keyboard 62 allows the user to enter a new program into EEPROM 23. The PROGRAM command functions in the same manner as the UPLOAD command. The Escape key on keyboard 62 allows the user to escape the Command Mode menu.
An "A" allows the user to transfer data from external computer 66 to IC memory card 22 as an addition to the data to IC memory card 22.
Entering a "C" allows the user to copy the contents of one IC memory card into the other erased IC memory card of IC memory card 22. Entering a "V" allows the user to verify the contents of one IC memory card are identical to the contents of the of the IC memory card of IC memory card 22.
It should be noted that IC Memory Card 22 may be either a library card which contains information for loading other equipment such as an AN/AYK-14 computer on an aircraft avionics bus or a program card which is used to reprogram rapid reprogramming terminal 20.
The upload.h file comprises the IC Memory Card upload/append function prototype and definitions. The upload.c file of the software of Appendix A is the module which uploads data from an external computer 66 through the RS-232 interface 71 and processor 21 to IC memory card 22. An upload prompt message is displayed on video screen 69 at the beginning of this module. The module tests the status of IC memory card 22 for changes, that is IC memory card 22 must be operating properly. The upload.c module then enters an infinite loop to process incoming records in an Intel Hex-32 format. All Intel Hex-32 record types are supported except types 03 and 05. Once a proper data record (type 00) is received the data in the byte oriented data record is transferred to IC memory card 22. The upload.c module is exited with the proper receipt of a type 01 record, that is an end of data record, and returns to the command mode. The upload.c also includes the append function.
The download.h file is the memory card data/file download function prototype. The download.c file is the module during which data is down loaded from IC memory card 22 through digital signal processor 21, the RS-232 interface 71 to computer 66. The download.c module displays a download prompt message on video screen 69 asking for the location of the data to download and then proceeds to download the data using the Intel Hex-32 format of FIG. 5. Upon completion of the down loading of data this module returns to the Command Mode. The user may identify a memory address range within either memory card one or two of IC memory card 22 from which data is to be downloaded. The user may also download a user specified file from memory card 22 by entering an "F" via keyboard 62.
The copy.h file comprises the memory card copy/verify function prototype and definitions. The copy.c file allows the user to transfer from one memory card of IC memory card 22 to a blank card which is the second card of IC memory card 22. The copied data may then be verified by entering a "V" via keyboard 62.
The erase.h module comprises the memory card erase function prototype. The erase.c module clears memory card one or two of IC memory card 22 by writing the erase command to each memory block within the memory card resulting in logic ones in each location in the memory of the card. The user must specify which of the two memory cards of IC memory card 22 is to be erased.
The switches.h file is the monitoring and library card processing function prototype. The switches.c module is the switch test and the interactive reprogram control module. The UP/VRFY/DOWN switch 47 of front panel 43 determines the mode of operation of rapid reprogramming terminal 20, while the EXEC/SKIP switch 49 determines whether a data file is to be uploaded or downloaded to equipment on the aircraft avionics or EW buses or verified or skipped. When the user activates switch 49 to the EXEC position, the software of Appendix A vectors from the rrt.sub.-- main.c module to the switches.c module. The switches.c module then determines whether an upload, download or verify operation is to be performed by rapid reprogramming terminal 20 depending upon the user selected position of switch 47 of front panel 43. If, for example, the user activates switch 47 to the download position and such an operation is not allowed with respect to the equipment being accessed by rapid reprogramming terminal 20 then liquid crystal display 57 displays a message to the user that the user may not initiate a download operation. The switches.c module looks for a cable from an aircraft to be reprogrammed as well as the aircraft identification and configuration which is then compared with information stored on IC memory card 22. If, for example, the aircraft identification is different from the identification stored on the IC memory card 22 then an error message is displayed on liquid crystal display 57. Rapid reprogramming terminal 20 also provides for a direct load capability, that is the aircraft's equipment may be reprogrammed when removed from the aircraft.
Switches.c loads a file manually by the user activating switch 49 to the EXEC position. Switches.c skips a file by the user activating switch 49 to the SKIP position. If automatic loading is permitted IC Memory Card 22 includes in its header a bit which allows for automatic loading. A prompt is then provided on screen 69, which indicates to the user to activate switch 49 to the EXEC position for an automatic load or activate switch 49 to the SKIP position for a manual load. If the user selects an automatic load all files are loaded without user participation. If the user selects a manual load, each file is loaded by the user by activating switch 49 to the EXEC position after the file is displayed to the user. If a data file is to be uploaded, downloaded or verified the switches.c file selects the proper bus, bus characteristics, and executes a protocol based upon the contents of a lookup table stored in IC memory card 22.
The wordtype.h file comprises MIL-STD-1553 word type definitions and structures.
The control.h file comprises MIL-STD-1553 bus control definitions and prototypes.
The switches.c module branches to the control.c module which controls the MS-1553 multiplex data bus 42 according to the data provided by IC memory card 22.
The control.c file is used to establish control of the 1553 multiplex data bus 42. The control.c module converts rapid reprogramming terminal 20 to a bus controller 55 and also converts the bus controller 55 to a remote terminal 55 when the bus controller 55 is to be reprogrammed as a remote terminal. The control.c module also converts bus controller 55 to a remote terminal when another remote terminal is being reprogrammed by rapid reprogramming terminal 55 functioning as a bus controller.
Another function performed by the control.c module is to quiet or inactivate the bus controller for the purpose of reprogramming a remote terminal 53. This operation generally takes place whenever the bus controller can not be converted to a remote terminal. For example, if rapid reprogramming terminal 20 is to reprogram an AN/ALQ-126B Defensive Electronic Counter Measures Set (a remote terminal on the electronics warfare bus) and the AN/ALR-67 Radar Warning Receiver (the bus controller on the electronic warfare bus) is active, the control.c module will quite the AN/ALR-67 Radar Warning Receiver to allow rapid reprogramming terminal 20 to reprogram the AN/ALQ-126B Defensive Electronic Counter Measures Set. It should be noted that the AN/ALR-67 Radar Warning Receiver can not be converted to a remote terminal.
The switches.c module enables a bus controller which was previously quieted by the control.c file by releasing the discrete enable, e.g. EW.sub.-- OSM.sub.-- EN and EW.sub.-- UDM.sub.-- EN discretes.
The control.c module takes the bus controller 55 that was previously converted to a remote terminal by the control.c module and reconverts it to a bus controller and also reconverts rapid reprogramming terminal 20 from a bus controller to it's initial remote terminal status.
The ms1553.c module of the software of appendix A includes a monitor function which determines if there is polling on the MS-1553 multiplex data bus 42.
The memcard.h file comprises the memory card driver definitions and function prototypes. The memcard.c file includes a memory.sub.-- card.sub.-- read driver for reading IC memory card 22. The card address is passed by the memory.sub.-- card.sub.-- read driver and the contents at this address is returned. The memory.sub.-- card.sub.-- read driver then uses a function address.sub.-- card.sub.-- page to select a page of the memory card and returns a system address to processor 21 which then uses the system address to obtain the data from the memory card. It should be noted that memory cards zero and one of IC memory card 22 each have eight pages of memory to store data. Each page stores eight megabytes at information.
The memcard.h file also includes a memory.sub.-- card.sub.-- write driver which writes data to the indicated IC memory card address and returns a status value. The memory.sub.-- card.sub.-- write driver uses address.sub.-- card.sub.-- page in the same manner as the memory.sub.-- card.sub.-- read driver. The memory.sub.-- card.sub.-- write driver also provides the required command to allow the data to be written into the memory card.
The memcard.h file includes an memory.sub.-- card.sub.-- erase driver that erases the entire contents of the IC memory card. The memory.sub.-- card.sub.-- erase driver provides the proper command to the memory card to allow the card to be erased to a state where all logic ones are stored in the memory card. The memcard.h file also includes a memory.sub.-- card.sub.-- status driver which waits until the memory card is ready or times out and returns a status indicating possible memory card errors. The memcard.h file includes a memory.sub.-- card.sub.-- size driver which obtains the size of the IC memory card from the card identification. The memcard.h file includes a memory.sub.-- card.sub.-- block driver which obtains the block size of the IC memory card. The memcard.h file includes a memory.sub.-- card.sub.-- ID driver which obtains the IC memory card manufacturer and card ID.
The ms1553.h file comprises the bus driver definitions and function prototypes. The ms1553.c file provides the drivers for MS-1553 multiplex data bus 42. The ms1553.c file includes an ms1553.sub.-- send driver which sends data over the MS-1553 multiplex data bus 42 when rapid reprogramming terminal 20 is set up to function as a bus controller. This driver uses two pointers with the first pointer pointing to the data to transferred via the MS-1553 multiplex data bus 42 and the second pointer points to the storage location of the status word sent from the remote terminal 53.
The ms1553.c file includes an ms1553.sub.-- receive driver which receives data over the MS-1553 multiplex data bus 42 when rapid reprogramming terminal 20 is set up to function as a bus controller. This driver sends a command to the remote terminal 53 for the remote terminal to send a message block to rapid reprogramming terminal 20.
The ms1553.c file includes an ms1553.sub.-- respond driver which allows rapid reprogramming terminal 20 to function as a remote terminal. The ms1553.sub.-- respond driver provides the information required by bus controller 41 to allow bus controller 41 to respond to polls initiated by a bus controller 55 on the MS-1553 multiplex data bus 42. The ms1553.sub.-- respond driver also allows bus controller 41 to send data to and receive data from the bus controller 55 controlling the bus.
The ms1553.c file includes a ms1553.sub.-- monitor driver which allows rapid reprogramming terminal 20 to monitor the MS-1553 multiplex data bus 42. Bus controller 41 is first set up to operate as a monitor terminal. Bus controller 41 then monitors the MS-1553 multiplex data bus 42 for activity on the bus 42. If there is activity on the MS-1553 multiplex data bus 42 then the ms1553.sub.-- monitor driver returns a value indicating an active bus. If there is no activity on the MS-1553 multiplex data bus 42 then the ms1553.sub.-- monitor driver returns a value indicating no activity on the bus.
The ms1553.c file includes a ms1553.sub.-- BC.sub.-- setup driver which initializes controller 41 as a bus controller; a ms1553.sub.-- RT.sub.-- setup driver which initializes controller 41 as a remote terminal and a ms1553.sub.-- MT.sub.-- setup driver which initializes controller 41 as a monitoring terminal.
The ms1553.c file includes a ms1553.sub.-- change.sub.-- bus.sub.-- channel driver which allows controller 41 to change operation to the alternate channel (either the primary or secondary bus).
The ieee488.h module provides the IEEE-488 bus driver function prototype. The ieee488.c module provides the bus driver function to communicate over the IEEE 488 bus which includes bus driver 260 and transceivers 262 and 264.
The interpts.h file provides interrupt vector function prototypes. The interpts.c file provides the interrupt vector functions and is currently not being used by rapid reprogramming terminal 20.
The timer.h file provides timer definitions and function prototypes. The timer.c file of the rapid reprogramming terminal software is the timer module which contains the timer routines used to set delays or timeouts.
The error.h file provides error definitions and function prototypes. The error.c file of the rapid reprogramming terminal software contains routines that display error messages.
Referring to FIG. 7, the format of message transfers on the 1553 multiplex data bus 42 will now be discussed. Bus Controller 41 is used to translate sixteen bit data words provided by processor 21 into Manchester mark encoded Military Standard 1553 signals for use by 1553 multiplex data bus 42 and also to decode Manchester mark signals provided by bus 42 into sixteen bit data words supplied to processor 21. A logic one is transmitted as a bipolar coded signal 1/0 or 0/1. A logic zero is the absence of a bipolar coded signal. A transition always occurs during the rising edge of a data clock signal. An absence of either pulse within a bit time is a Manchester error.
As is best illustrated by FIG. 7, the Command Word format for each Command Word transmitted by rapid reprogramming terminal 20 consists of a command sync waveform which is an invalid Manchester waveform. The width of the waveform is three bit times with the waveform being positive for the first one and one-half bit times, and then negative for the following one and one-half bit times.
The next five bits (Bit times 4 to 8, bits 11-15) following the sync waveform is the remote terminal address, with there being normally thirty addressable units per bus since the digital codes 00000 and 11111 are usually not used. The type of avionics or other equipment defined by these addresses vary by aircraft and selected bus.
Following the remote terminal address is the transmit/receive bit (Bit time 9, bit 10) which indicates the action required of the remote terminal 53. A logic zero indicates that the remote terminal 53 is to receive data, while a logic one indicates that the remote terminal 53 is to transmit data.
The subaddress field (Bit time 10 to 14, bits 5-9) follows the transmit/receive bit and identifies the type of message, for example an activity message. The subaddress values 00000 and 11111 are used for mode commands.
The data word count (Bit times 15 to 19, bits 0-4) follows the subaddress field and is a binary number indicating the data words to be either sent or received by the remote terminal 53. The remote terminal 53 may either send or receive a maximum of thirty two words in any one message block with all ones indicating a decimal count of thirty one and all zeros indicating a decimal count of thirty two.
The P bit (Bit time 20) of the command word is used for parity over the preceding sixteen bits and utilizes odd ones parity.
Status words are transmitted by a remote terminal 53 after receipt of rapid reprogramming terminal generated Command Word or following a rapid reprogramming terminal to remote terminal transfer.
The Status Word format for each Status Word transmitted by a remote terminal 53 consist of a status sync waveform which is an invalid Manchester waveform identical to the command sync waveform.
The next five bits (Bit times 4 to 8, bits 11-15) following the sync waveform is the address of the remote terminal 53 which is transmitting a status word.
Following the remote terminal 53 address is a message error bit (Bit time 9, bit 10) which indicates if some error was detected in the command or data words sent by rapid reprogramming terminal 20.
The status code field (Bit times 10 to 18, bits 1-9) follows the message error bit and is used to convey remote terminal status information to rapid reprogramming terminal 20.
The terminal flag (Bit time 19, bit 0) follows the status code and will be set to one to indicate that the status code field should be examined by rapid reprogramming terminal 20.
The P bit (Bit time 20) of the status word is used for parity over the preceding sixteen bits and utilizes odd ones parity.
Sequences of up to thirty two data words may be sent from a remote terminal 53 to rapid reprogramming terminal 20 or from rapid reprogramming terminal 20 to a remote terminal 53. Each data word consist of a data sync waveform (Bit times 1 to 3) which is an invalid Manchester waveform. The width of the waveform is three bit times with the waveform being negative for the first one and one-half bit times, and then positive for the following one and one-half bit times.
The sixteen message data bits (Bit times 4 to 19, bits 0-15) following the sync waveform are used for message data transmission.
The P bit (Bit time 20) of the data word is used for parity over the preceding sixteen bits and utilizes odd ones parity.
Referring to FIG. 8a during the transfer sequence from rapid reprogramming terminal 20 to a remote terminal 53, terminal 20 transmits a command word with its TR bit set to zero, followed immediately by from one to thirty two data words also generated by terminal 20. The remote terminal 53 next responds with a status word.
Referring to FIG. 8b during the transfer sequence from a remote terminal 53 to rapid reprogramming terminal 20, rapid reprogramming terminal 20 transmits a command word with its TR bit set to one. The remote terminal 53 responds with a status word followed by one to thirty two data words.
At this time it should be noted that the following discussion relates primarily to protocol B of Military Standard 2217(AS).
The messages utilized by rapid reprogramming terminal 20 to communicate with a remote terminal 53 being reprogrammed via the 1553 multiplex data bus 42 will now be discussed. It should be understood that the messages used by rapid reprogramming terminal 20 to communicate with any remote terminal 53 aboard the aircraft via the 1553 data bus are required to follow the message formats set forth in FIGS. 7 and 9.
The Activity Message of FIG. 9A is utilized by rapid reprogramming terminal 20 when reprogramming a remote terminal 53 to determine whether the remote terminal 53 is ready to receive data and allows the remote terminal 53 a request to send information to rapid reprogramming terminal 20 or receive information from rapid reprogramming terminal 20.
Referring to FIG. 9A the Command Word for the activity message follows the format set forth in FIG. 7. Bits 11-15 provide the address of the remote terminal 53 to receive the message, bit 10 is set at a logic one, the subaddress (bits 5-9) is set at 07 hexadecimal and the word count (bits 0-5) is one.
The status word response to the activity message follows the general format set forth in FIG. 7 supplemented by FIG. 9B. A status response word to the Activity and other messages is provided by a remote terminal 53 for each message transaction. The status response word follows data on a remote terminal receive type transaction and precedes the data on a remote terminal transmit type transaction. The rapid reprogramming terminal 20 allows a response time gap of approximately 12 usec. from the end of the last transmitted command word (transmit type message) or the end of the last transmitted data word (receive type message), to the start of the remote terminal status response word before declaring a no response error. The remote terminal 53 begins the status response word within a time period of approximately 2-10 usec. from the receipt of the end of the last command word (transmit type message) or the receipt of the end of the last data word (receive type message). The software for rapid reprogramming terminal ensures that the time from the end of the remote terminal transmission of the last data word (transmit type message) or the end of the last status response word (receive type message) to the beginning of the next command word is at least 8 usec.
Referring to FIG. 9B, the status response word bits comprise a terminal address (bits 11-15) which is remote terminal address of the remote terminal 53 being reprogrammed (referred to as YYYYY); a message error bit (bit 10); a service request bit (bit 8) and a busy bit (bit 3).
The busy bit is utilized by rapid reprogramming terminal 20 if it is set and when the remote terminal being reprogrammed is compatible with setting the busy bit, that is the remote recognizes the busy bit. The setting of this bit to a logic one indicates to the rapid reprogramming terminal 20 that it is necessary to suspend or slow down communications with the remote terminal 53. The first status response word received by the rapid reprogramming terminal 20 with the busy bit set to a logic one causes the rapid reprogramming terminal 20 to send only activity messages (normally every 10 msec.) until the busy bit is cleared (logic 0). As long as the busy bit is clear in the status response word from a remote terminal 53, rapid reprogramming terminal 20 assumes that the remote terminal 53 can support a continuous stream of identical messages within a time period, identified in the file's lookup table in IC memory card 22, from the end of one message to the start of the next command word. The continuous stream of identical messages is assumed to be either memory data load or memory data verify messages.
This continuous stream is maintained for a time period compatible with IC Memory Card 22 and remote terminal 53 data transfer capabilities and at a minimum, rapid reprogramming terminal 20 is capable of transferring 2K data words (in memory data load or memory data verify messages) per second when remote terminal 53 does not indicate a busy status during the transfer. Any data word transmitted after a status word with the busy bit set is ignored by rapid reprogramming terminal 20. If the remote terminal 53 being reprogrammed cannot set the busy bit in the remote terminal status response, then prior to each message transmission other than an activity message transmission, rapid reprogramming terminal 20 will command an activity message from the remote terminal 53 being reprogrammed and inspect the busy bit in the data word following the status response word to determine if the remote terminal 53 is ready to communicate with rapid reprogramming terminal 20.
The operation of rapid reprogramming terminal 20 after the busy bit has been set to a logic one and then cleared varies depending on the operation of the remote terminal 53. If the busy bit was set in the status response word for a transmit type command, after the busy bit is cleared (in the response to the activity message) the last transmit command will be repeated so that rapid reprogramming terminal 20 can receive data words that were ignored when the busy bit was set.
If the busy bit was set in the data word of the activity message which is only applicable when the busy bit is not set in the status response word, the data word for the first activity message with the busy bit cleared will be processed normally.
If the busy bit is set in the status response word for a receive type command, then two options (selectable by a flag in the look up table for the remote terminal being reprogrammed) are allowed. Rapid reprogramming terminal 20 assumes that the data words were not received by the remote terminal 52 and when the busy bit is cleared in the status response word for the activity message, the last received message will be repeated or rapid reprogramming terminal assumes that the data words were received by the remote terminal 53 and when the busy bit is cleared in the status response word for the activity message, the last received message will not be repeated.
Referring again to FIG. 9A, the remote terminal address (bits 11-15) for the status word response to the activity message is the address of the remote terminal 53 being reprogrammed. The message error bit (bit 10) may be a one or a zero since this bit is not utilized. The service request bit (bit 8) may normally be a one or zero since this bit is not utilized unless a data transfer is in progress. When the service request bit is not used, rapid reprogramming terminal 20 determines that the remote terminal 53 is requesting a message transaction based on the fact that the contents of bits 0 through 10 of the data word that follows are non-zero and will act upon that request only when a data transfer is in progress.
The busy bit (bit 3) if set to a logic one is used to indicate that the remote terminal 53 is not ready to process any messages from terminal 20 other than the activity message. Prior to the transmission of any other type messages to the remote terminal 53, rapid reprogramming terminal 20 will continue to send Activity Messages (approximately every 10 msec.) to the remote terminal 53 until the busy bit is cleared, or the number of sequential Activity Messages is exhausted as determined from a lookup table or a Reprogram Status Message is requested. Remote terminal 53 will respond to the busy bit (bit 15) in the data word that follows only when the busy bit in the status word is not set. Bits 9, 7, 6, 5, 4, 2 and 1 of the status word are not utilized and therefore may be either a one or a zero.
The terminal flag bit (bit 0) of the status word is used only when a data transfer from rapid reprogramming terminal 20 to a remote terminal 53 is in progress. Following a header message and proceeding an exit load message during a data transfer, if the terminal flag bit and the service request bit of the status word are set at a logic one state, rapid reprogramming terminal 20 will extract from a data word sent by the remote terminal 53 to rapid reprogramming terminal 20 the next command word to be sent by rapid reprogramming terminal 20 to the remote terminal 53. This command word is the command word for the reprogram status message.
Rapid reprogramming terminal will ignore the data word of the activity message when the busy bit is set to a logic one in the status response word provided by remote terminal 53; thus, the remote terminal 53 need not transmit the data word.
The busy bit (bit 15) in the data word for the activity message functions identically to the busy bit in the status word (bit 3). This bit is provided to accommodate a remote terminal 53 that does not utilize bit 3 of the status word to indicate it is busy. The busy bit and the remote terminal request bits (bits 0-10) of the data word will not be set simultaneously unless the remote terminal 53 requires sending a reprogram status message to rapid reprogramming terminal 20. The busy bit need not be set to a logic one state in order to send a reprogram status message to rapid reprogramming terminal 20. Rapid reprogramming terminal 20 will not honor the reprogram status message request until an activity message containing the request with the busy bit clear or at the logic zero state is received by terminal 20.
The request bits (bits 0-10) of the data word are utilized to allow the remote terminal 53 to request that rapid reprogramming terminal 20 send a specific command to the remote terminal 53. As a result of the remote terminal request, rapid reprogramming terminal 20 will transmit a command word with the remote terminal address defined in bits 11 through 15 of the command word and the contents of the activity message remote terminal request in bits 0-10 of the data word. The TR bit (bit 10) is set to 1 if remote terminal 53 is to transmit a message and will be set to 0 if remote terminal 53 is to receive a message. The subaddress bits (bits 5-9) of the data word indicate the subaddress of the message to be sent. The word count bits (bits 0-4) indicate the data word count for the message. Bits 11-14 are equal to a logic 0.
The activity messages prior to rapid reprogramming terminal 20 beginning a Load/Verify operation or a Verify operation will now be discussed. After the setting of the discretes, that is the setting of the outputs of programmable peripheral interfaces 52, 54 and 56 and the expiration of a 10 msec. wait period for the discrete to settle, the first messages commanded by rapid reprogramming terminal 20 are activity messages regardless of whether or not a lookup table for the remote terminal 53 indicates that activity messages are required for each and every transaction. A transaction, in turn, comprises a header message followed by a number of data transfer messages as indicated by the header message and a trailer message. Bits 11-14 of the activity message data word are never used by rapid reprogramming terminal 20. The digital information received in bits 0-10 of the data word for all activity messages commanded by rapid reprogramming terminal 20 before the first message of FIG. 9(D) are ignored by terminal 20. This operation is implemented to permit use of the activity message subaddress for other uses when reprogramming is not being performed, that is rapid reprogramming terminal 20 only assumes the activity message data is valid after reprogramming of a remote terminal 53 has begun by the setting of discretes and receipt of a valid load/verify message, FIG. 9D. The information received in bit 15 (busy bit) of the data word for all activity messages commanded by rapid reprogramming terminal 20 before the load/verify message, FIG. 9D, will only be used if the lookup table for the remote terminal 53 indicates that activity messages are required for every transaction and the busy bit is not set to a logic one in the status word response to the activity message. In this case the remote terminal 53 must ensure that bit 15 of the data word is valid or set to zero prior to receipt of the load/verify message, FIG. 9D.
In the manual mode, if the remote terminal lookup table indicates that memory configuration messages are supported, then there will be a memory configuration message commanded before the load/verify message, FIG. 9D, and rapid reprogramming terminal 20 will expect valid memory configuration data. Ignoring the activity message data word bits 0-14 precludes a remote terminal 53 from sending a reprogram status message prior to receipt of the load/verify message, FIG. 9D, from rapid reprogramming terminal 20; however, a reprogram status message would not be valid before reprogramming is initiated. Therefore a remote terminal 53 should not request a reprogram status message until after the remote terminal 53 receives a load/verify message, FIG. 9D.
Referring to FIG. 9C, the data word in the activity message provided prior to a memory configuration message is processed only when rapid reprogramming terminal 20 is required to check the busy bit status (check bit 15 of the data word of the activity message) of remote terminals 53 that do not use the busy bit in the status response word. The memory configuration message is utilized to read the current memory configuration of remote terminals 53. This message is only used when its use is indicated in a lookup table for the remote terminal 53. The command word and status word for the memory configuration message follow the format of FIG. 7. Each remote terminal 53 aboard an aircraft has up to two memories designated memory area one and memory area two. Data bits 0-15 of data word one of the memory configuration message represent the configuration of the data stored in memory area one. Unused data bits equal zero. Similarly, data bits 0-15 of data word two of the memory configuration message represent the configuration of the data stored in memory area two. Unused data bits equal zero. In the automatic mode of operation this message is used for the purpose of comparing a remote terminal's configuration stored in the IC memory card 22 with reported remote terminal configuration. If the reported value is the same as the value stored in the IC memory card 22, rapid reprogramming terminal 20 will not perform a load operation. However, if the reported value is different from the value stored in the IC memory card 22, rapid reprogramming terminal 20 will proceed with a load operation.
Referring to FIG. 9D, there is shown the format for the enter load, exit load, enter verify and exit verify messages. For the first enter load, exit load, enter verify or exit verify message, the data word in the activity message provided prior to a enter load, exit load, enter verify or exit verify message will be processed only when rapid reprogramming terminal 20 is required to check the busy bit status (check bit 15 of the data word of the activity message) of remote terminals 53 that do not use the busy bit (bit 3) in the status response word and in this case bits 0-14 of the data word will be ignored.
The transmit/receive bit (bit 10) in the command word for the enter load, exit load, enter verify and exit verify messages is a logic zero since the remote terminal 53 is to receive data. The terminal subaddress field (bits 5-9) in the command word is set at 1D hexadecimal. Each message enter load, exit load, enter verify and exit verify requires that an enable signal be provided by rapid reprogramming terminal 20 before a load or verify may be executed. A logic one at the EW.sub.-- OSM.sub.-- EN output of interface 54 enables the operating software memory of the electronic warfare system on board the aircraft. Similarly, a logic one at the EW-UDM.sub.-- EN output of interface 54 enables the user data memory of the electronic warfare system on board the aircraft. When the AV.sub.-- EN1 output of interface 54 is at a logic one state the first memory areas of the aircraft avionics system are enabled, while a logic one at the AV.sub.-- EN2 output of interface 54 enables the second memory areas of the aircraft avionics system.
Each field in the data is checked by the remote terminal 53 for compliance with the following prior to execution of a load or verify. The type and number fields are defined based on WRA nomenclature (e.g., RT-1079); however, if this creates a conflict, the system nomenclature (e.g., ALQ-126) is utilized instead. The preferred embodiment of the present invention uses WRA nomenclature.
Data word one (bits 0-15) is the type field consisting of the first two eight bit ASCII characters that represent the nomenclature of the remote terminal 53 being controlled. For example, for RT-1079 the two characters would be "R", "T".
Data word two (bits 0-15) is a number field for consisting of the third and fourth eight bit ASCII characters that represent the nomenclature of the remote terminal 53 being controlled. For example, for RT-1079 the two characters would be "1" "0".
Data word three (bits 0-15) is a number field two consisting of the last two eight bit ASCII characters that represent the nomenclature of the remote terminal 53 being controlled. For example, for RT-1079 the two characters would be "7", "9".
Data word four (bits 10-15) is the fill field which may be any bit pattern including zero and is to be defined by the individual remote terminal 53 being controlled. The fill field is required to be checked even if the field is defined as zero. The fill field is contained in a look up table for the remote terminal 53 being reprogrammed.
The load/verify bits (bits 8-9) are used to described whether a Load, Verify, or other type transaction will follow. The load/verify bits are coded as follows: L/V=01 indicates that a memory load follows; L/V=10 indicates that a memory verify follows; L/V=11 is not used and L/V=00 indicates that a enter load, enter verify, exit load or exit verify message is being sent for some reason other than a load or verify such as to quiet the bus controller for the remote terminal 53 being reprogrammed.
The control code (bits 0-7) of data word four are set as follows: bit 7 is a reprogram enable for memory area one and is equal to 80 hexadecimal; bit 6 is a reprogram enable for memory area two and is equal to 40 hexadecimal; bit 5 is a reprogram disable for memory area one and is equal to 20 hexadecimal and bit 4 is a reprogram disable for memory area two and is equal to 10 hexadecimal. Bit 3 of the control code (08 hexadecimal) indicates to the bus controller for a remote terminal 53 being reprogrammed to convert to a remote terminal so as to allow the remote terminal 53 to be reprogrammed. In addition, bit 3 converts a bus controller 55 which may only be reprogrammed as a remote terminal to a remote terminal for reprogramming. Bit 2 of the control code which is 04 hexadecimal tells the bus controller for remote terminal 53 to stop transmitting or receiving information so as to allow the remote terminal to be reprogrammed. The use of bit 2 of the control code in this manner is required because some bus controllers can not be converted to a remote terminal when reprogramming a remote terminal 53. Bit 1 of the control code which is 02 hexadecimal is utilized to have a bus controller when converted to a remote terminal revert back to a bus controller. Bit 0 of the control code which is 01 hexadecimal causes the remote terminal to begin executing starting at the address previously supplied via data word three or data word four of a header message.
The control code field is valid only if all other fields are correct and only if either the Avionics Reprogram Enable 1 (AV.sub.-- EN1 output of interface 54); or the EW UDM Reprogram Enable discrete (the EW-UDM.sub.-- EN output of interface 54) is present or the Avionics Reprogram Enable 2 (AV.sub.-- EN2 output of interface 54) or the EW OSM Reprogram Enable discrete (EW-OSM.sub.-- EN output of interface 54) is present. At the end of reprogramming, rapid reprogramming terminal 20 will maintain the active discrete for at least 100 msec after the transmission of a exit load or exit verify message that ends the reprogramming mode.
The following are the only valid control codes that can occur when rapid reprogramming terminal 20 is functioning as a bus controller during a load or verify. Any other code shall cause the remote terminal to not execute a load or verify.
Code 00000000 which is 00 hexadecimal indicates that no load or verify control action is to be taken.
Code 00000001 which is 01 hexadecimal will cause the remote terminal 53 to begin execution starting at the address previously supplied via data word three and data word four of the header message.
Code 00000010 which is 02 hexadecimal will cause the remote terminal 53 to revert back to a bus controller. Upon execution of this Code the message traffic shall be for rapid reprogramming terminal 20 functioning as a remote terminal.
Code 00010000 which is 10 hexadecimal will cause the remote terminal 53 to exit the reprogramming mode for memory area two. This code is only valid if the Avionics Reprogram Enable 2 or the EW OSM Reprogram Enable discrete is active.
Code 00100000 which is 20 hexadecimal will cause the remote terminal to exit the reprogramming mode for memory area one. This code shall only be valid if the Avionics Reprogram Enable 1 or EW UDM Reprogram Enable discrete is active.
Code 00110000 which is 30 hexadecimal is a combination of 10 hexadecimal and 20 hexadecimal for simultaneous memory areas one and two exit reprogramming mode.
Code 01000000 which is 40 hexadecimal will cause the remote terminal 53 to enter the reprogramming mode for memory area two. This code shall only be valid if the Avionics Reprogram Enable 2 or the EW OSM Reprogram Enable discrete is active.
Code 10000000 which is 80 hexadecimal will cause the remote terminal 53 to enter the reprogramming mode for memory area one. This code shall only be valid if the Avionics Reprogram Enable 1 or the EW UDM Reprogram Enable discrete is active.
Code 11000000 which is CO hexadecimal is a combination of 40H and 80H for simultaneous memory areas one and two enter reprogramming mode.
Referring to FIG. 9E there is shown the format for a header message which is used to pass load and verify parameters to the remote terminal 53 being reprogrammed. The data word in the activity message provided prior to a header message is processed only when rapid reprogramming terminal 20 is required to check the busy bit status (check bit 15 of the data word of the activity message) of remote terminals 53 that do not use the busy bit (bit 3) in the status response word.
The transmit/receive bit (bit 10) in the command word is at the logic zero state since the remote terminal 53 is to receive data and the terminal subaddress field (bits 5-9) is set at 14 hexadecimal. The transfer mode (bits 14-15) are used to describe the memory data load or memory data verify message data word content. The transfer mode bits are binary coded as follows: TM=00; TM=01; TM=10 and TM=11. When TM=00 which is the no transfer mode, the buffer transfer count contained in data word one and the initial load address contained in data word two have no meaning. This mode is used to transfer the program entry address contained in data word three and Page Number contained in data word four or is used as a preamble to the trailer message.
When TM=01, each sixteen bits of data transmitted in a data word will contain only eight bits of information in bits 0-7. When TM=10, each sixteen bits of data transmitted in a data word will contain sixteen bits of information in bits 0-15. When TM=11, the sixteen bits of data transmitted in each odd word (first is odd) contains the sixteen least significant bits of data in bits 0-15 and each even word (second is even) contains the sixteen most significant bits of data in bits 0-15.
The header type bits (bits 12-13) are used to describe the header and have no meaning when the transfer mode is 00. The header type are binary coded as follows: HT=00, HT=01, HT=10 and HT=11. When HT=00, the buffer transfer count equals the number of words to be transferred. When HT=01, the buffer transfer count equals number of messages to be transferred. HT=10 is undefined, while HT=11 reserved for internal use by digital signal processor 21 and therefore will not be transmitted on the 1553 multiplex data bus 42 aboard the aircraft.
The buffer transfer count (bits 0-11) is used to indicate the amount of data that will follow the header message. The buffer transfer count has no meaning when the transfer mode is 00. The range of the buffer transfer count is from one to four thousand ninety six words.
When HT=00 , the buffer transfer count is the total number of data words that will be transmitted in a transaction which includes the header message and trailer message. The data words are transmitted in 32-word messages since each transfer sequence is limited to thirty two data words (see FIG. 8) with the last message containing from one to thirty two data words. The maximum transfer for HT=00 is four thousand ninety six words using one hundred twenty eight memory data load or memory data verify messages.
When HT=01, the buffer transfer count is the number of memory data load or memory data verify messages that will follow the header message. Thus, the maximum data transfer per header message is 4096.times.32 data words per memory data load or memory data verify message which equals 131,072 sixteen bit words (128K). If paging (data word four, bits 0-1) is utilized for transfer modes 01 or 10, the maximum value of the buffer transfer count will be 2048 which results in 65,536 sixteen bit data words (64K) for transfer modes 01 and 10.
Data word two is the initial load address (bits 0-15) which is the sixteen or less least significant bits of the point in memory into which data is to be loaded or read. The maximum value (number of bits) used in the initial load address is compatible with the page size of remote terminals using paging. Unused bits equal zero.
Data word three is program entry address (bits 0-15) which has meaning only for transfer mode=00. The program entry address is the sixteen or less least significant bit of the point in memory at which the remote terminal 53 being reprogrammed is to begin execution after receipt of an execute command in a load/verify message, FIG. 9D, or when a transfer control is indicated in data word four. The load/verify message, FIG. 9(D), is only used with remote terminals which require this command. The maximum value (number of bits) used in the program entry address is compatible with the page size of remote terminals using paging. Unused bits equal zero.
Data word four is the page number (bits 3-15) representing up to the thirteen most significant bits for a paged memory address within the remote terminal 53. The page number applies to the program entry address for transfer mode=00 or the initial load address for transfer modes=01, 10 or 11. Unused bits shall equal 0. It should be noted that a page comprises 65,536 addresses in memory.
The transfer control bits 0-1 may be used to transfer control to a loaded program after a verify is processed or to an unaltered memory area after a load is completed, that is a remote terminal 53 has been reprogrammed. When the transfer control bits equal 01 this indicates to the remote terminal 53 being reprogrammed that this is the last header, memory data load or verify (up to 4096 messages), trailer or header, trailer transaction. When the transfer control bits equal 01 this indicates to the remote terminal 53 being reprogrammed that more data is to follow the current header, memory data load or verify (up to 4096 messages), trailer transaction or header, trailer transaction and control should not be transferred. For remote terminals 53 using paging and the program entry address, the transfer control will remain equal to 01 even for the last data transaction, until a transfer mode equals 00 message is used to supply the program entry address and page number. Transfer control equal to 10 indicates that control is to be transferred to the program entry address of data word three. When control is transferred, the transfer does not take place until after the trailer message and control is transferred only to non-reprogrammed areas or verified areas in memory. Transfer control equals 11 is invalid and bit 2 equals zero.
Referring to FIG. 9F there is shown the format for a memory data load message which is used to transfer the data to be loaded into the memory of a remote terminal 53 being reprogrammed. The data word in the activity message provided prior to a memory data verify message is processed only when rapid reprogramming terminal 20 is required to check the busy bit status (check bit 15 of the data word of the activity message) of remote terminals 53 that do not use the busy bit (bit 3) in the status response word.
The transmit/receive bit (bit 10) in the command word is at the logic zero state since the remote terminal 53 is to receive data and the terminal subaddress field (bits 5-9) is set at 15 hexadecimal, while the word count may vary from one to thirty two.
If the busy bit (bit 3) is set to a logic one in the status response word for a memory data load message and the remote terminal 53 is of the type that requires retransmission of the message, the memory data load message for which the busy bit has previously been set will be repeated after the busy bit (bit 15 of the data word) in the activity message is cleared or at the logic zero state. The number of data words will equal the word count in the memory data load message command word.
Referring to FIG. 9G, there is shown the format for a memory data verify message which is used to pass the data that rapid reprogramming terminal 20 will compare to the data stored in IC memory card 22. The data word in the activity message provided prior to a header message is processed only when rapid reprogramming terminal 20 is required to check the busy bit status (check bit 15 of the data word of the activity message) of remote terminals 53 that do not use the busy bit (bit 3) in the status response word.
The transmit/receive bit (bit 10) in the command word is at the logic zero state since the remote terminal 53 is to receive data and the terminal subaddress field (bits 5-9) is set at 15 hexadecimal, while the word count may vary from one to thirty two.
If the busy bit (bit 3) is set to a logic one in the status response word for a memory data verify message then any data words transmitted by the remote terminal 53 are ignored. After the busy bit is cleared in the status response word for the activity message, rapid reprogramming terminal 20 recommends a memory data verify message. The remote terminal 53 ensures that the data words transmitted are for the memory data verify message for which the busy bit was set, even if the data words were previously transmitted.
The number of data words will equal the word count in the memory data verify message command word.
Referring now to FIG. 9H, the trailer message is used to pass the data checksum and additional load or verify parameters to the remote terminal 53 being reprogrammed. The activity message shown prior to the trailer message will only be present when rapid reprogramming terminal 20 is required to check the busy bit status of remote terminals 53 that do not use the busy bit in the status response word.
The transmit/receive bit (bit 10) in the command word for the trailer message is a logic zero since the remote terminal 53 is to receive data and the terminal subaddress field (bits 5-9) in the control word is set at 16 hexadecimal.
Data word one contains the number of sub-pages and the first sub-page for remote terminals 53 utilizing paging or sub-paging. This word may also be used for internal register control. The fields of data word one represent the values to be used in the next header, memory data load or verify (up to 4096 messages), trailer transaction. For the first header, memory data load or verify (up to 4096 messages), trailer transaction the information will be transmitted prior to the memory data transaction via a header message, trailer message transaction in which the TM (transfer mode) field in data word one of the header is 00.
The sub-page/register count (bits 8-15) field in data word one may be used in lieu of or in conjunction with the page number field in data word four of the header message and is individual user definable. Unused bits equal zero. In the preferred embodiment of the present invention the sub-page field in data word one of the trailer message is used in conjunction with the data word four of the header message of FIG. 9E.
For purpose of illustrating the use of the sub-page field in the trailer message the following example is provided. In order to load 256K of memory into a remote terminal 53 with bank switching, 64K of address capability and a page size definition of 2048 words, the following approach may be used. To load 256K with sub-pages 2048 words long requires 128 header, memory data, memory data, trailer transactions (256K/2048=128). The 128 transactions consist of 32 transactions for each of the four banks of switching in remote terminal 53. Thus, for each 32 transactions the header message, data word four page number, FIG. 9(E), equals the bank number which would be incremented from zero to three. Within each group of 32 transactions the sub-page count would increment every transaction from zero to thirty one. For each transaction (assuming HT=01 for buffer transfer count equals the number of messages) the header data one buffer transfer count would be 64 (2048 words/32 words per message).
The first sub-page/register (bits 0-7) field may be used in lieu of or in conjunction with the page number field in data word four of the header message and may be defined by the user. Unused bits equal zero. Examples of use of this field are: specifying a processor register into which the page number field in data word four of the header message is to be loaded or specifying the initial sub-page count in the example set forth above to one so as to not reprogram the first 2048 memory locations (the first group of transactions would only be 31 transactions long (1 to 31) and the sub-page count for the first transaction would be set to one to indicate a starting address of 2048).
The data word two checksum (bits 0-15) is the checksum of an entire transaction, i.e., header, memory data, memory data, trailer transaction (when TM in header data word one is not equal to zero) or header, trailer transaction (when TM in header data one is equal to zero). The checksum is derived by a two's complement sixteen bit addition of every data word in the transaction (i.e., header, memory data, and trailer data words) with the exception of the checksum data word which is data word two of the trailer message. The two's complement sixteen bit addition is binary addition with the carry discarded, that is there is no end around carry (e.g., FFFF (hexadecimal)+1=0).
The remote terminal 53 being reprogrammed is responsible for comparing the checksum received from rapid reprogramming terminal 20 with the data words for both load and verify functions. The checksum value in data word two of the trailer message is the checksum that should be computed by the remote terminal 53. If the value computed does not match the value received from processor 21 for either a load or verify operation, an error is declared and a reprogram status message is requested by the remote terminal 53 being reprogrammed.
Referring to FIG. 9I, the activity message illustrated prior to the reprogram status message indicates that remote terminal 53 wants to provide to rapid reprogramming terminal 20 a reprogram status message (bits 5-9 of the data word of the activity message).
During a reprogramming operation the remote terminal 53 being reprogrammed may halt the operation and notify rapid reprogramming terminal 20 of an error by setting the busy bit (bit 3) in the status response word or the busy bit (bit 15) in the Activity Message data word. When rapid reprogramming terminal 20 receives the busy bit from remote terminal 53, it will continue to transmit activity messages until the busy bit is cleared. The service request by remote terminal 53 to transmit a reprogram status message will be honored after the first activity message response with the busy bit cleared. By this means remote terminal 53 can notify rapid reprogramming terminal 20 of the error.
The transmit/receive bit (bit 10) of the command word of the reprogram status message is set at a logic one since remote terminal 53 is to transmit and the subaddress (bits 5-9 of the command word) for this message is 17 hexadecimal.
The status flag (bit 15) of data word one is set to a logic one to indicate that the remainder of the data word should be processed by rapid reprogramming terminal 20, that is the reprogram status message contains valid data. If this bit is set to a logic zero, the reprogram status message will be ignored by rapid reprogramming terminal 20.
The status indicator (bit 14) defines the meaning of the remainder of the data word, that is an error code or a status code to be displayed by rapid reprogramming terminal 20.
When the status indicator equals zero this indicates that an error has occurred and the error code will be processed by rapid reprogramming terminal 20.
When the status indicator equals one this indicates that no error has occurred and the status code in bits 13-0 are to be displayed on liquid crystal display 57 as 4 hexadecimal characters (bits 15 and 14 of the display value are 0). With the status indicator equal to one the values of bits 13-0 will be used to indicate status or progress through the load or verify operation.
When SF equals one and SI equals one the status code bits 0-13 are display characters. When SF equals one and SI equals zero bits 0-13 represent error codes and the desired rapid reprogramming terminal 20 action. The error codes are 0001 (hexadecimal) which is an abort; 0002 (hexadecimal) which is a restart; 0003 (hexadecimal) which is a retry and 0004 (hexadecimal) which is a automatic retry.
The abort error code indicates to rapid reprogramming terminal 20 that the load operation or verify operation has been aborted and should not be retried. Rapid reprogramming terminal 20 will display the error code and wait for an operator response. On receiving the response from the operator, rapid reprogramming terminal 20 will abort the load of the remote terminal 53 being reprogrammed and continue with the load of the next remote terminal or bus controller to be reprogrammed if there is a requirement to reprogram another remote terminal or bus controller.
The restart status code indicates that an unrecoverable error has occurred in loading a remote terminal 53 and a reload of remote terminal 53 is desired. Rapid reprogramming terminal 20 will display the error code and wait for an operator response. On receiving the response from the operator, rapid reprogramming terminal 20 will restart the load of the remote terminal 53 being reprogrammed.
The retry status code indicates that an error has occurred in the last message sequence transaction and a repeat of the sequence is desired. Rapid reprogramming terminal 20 will display the error code and wait for an operator response. On receiving the response from the operator, rapid reprogramming terminal 20 will repeat the last transaction.
The automatic retry status code indicates that an error has occurred in the last message sequence transaction. After three consecutive retries, rapid reprogramming terminal 20 will display the error code and wait for an operator response. However, if the retry is successful before reception of the third consecutive error, an error message will not be displayed and operation will continue as normal. On receiving the response from the operator, rapid reprogramming terminal 20 will abort the load of the remote terminal 53 being reprogrammed and continue with the load of the next remote terminal or bus controller to be reprogrammed.
Referring to FIG. 9J, the activity message shown prior to the RRT error message is present only when rapid reprogramming terminal 20 is required to check the busy bit status of remote terminals 53 that do not use the busy bit in the status response word.
The RRT error message is utilized to inform the remote terminal 53 being reprogrammed that rapid reprogramming terminal 20 has detected an error in the load or verify. Data word one, bit 2 is an abort which is set to a logic one by rapid reprogramming terminal 20 to notify the remote terminal 53 that the load or verify has been aborted and no further retries will be made.
Bit 1 is a complete restart which is set to a logic one by rapid reprogramming terminal 20 to notify the remote terminal 53 that an unrecoverable error has occurred and all memory data load or memory data verify transactions will be restarted. Bit 0 is the transaction bit which is set to a logic one by rapid reprogramming terminal 20 to notify the remote terminal 53 that there was an error detected in the last header, memory data, trailer or header, trailer transaction and that the transaction will be repeated. The remaining bits (bits 3-15) of the data word are a logic zero.
Referring now to FIG. 10, the operation of rapid reprogramming terminal 20 when reprogramming a remote terminal 53 or a bus controller which reverts to a remote terminal during reprogramming will now be discussed.
When the lookup table indicates that the remote terminal 53 supports memory configuration as identified by the remote terminal's software, rapid reprogramming terminal 20 request a memory configuration message, FIG. 9C, from the remote terminal 53 being programmed. The memory configuration message describes the current memory contents for one or two memory areas of the remote terminal 53 being reprogrammed. Rapid reprogramming terminal 20 compares the received memory configuration to the current memory configuration for the remote terminal 53 stored in IC memory card 22 (program step 72). In automatic mode, if the remote terminal 53 already contains the current memory configuration, rapid reprogramming terminal 20 continues on to the next remote terminal 53 to be processed (program step 102). If the memory configuration message is not usable, rapid reprogramming terminal 20 will assume that the remote terminal 53 requires reprogramming. In manual mode, rapid reprogramming terminal 20 will display the memory configuration data and continue reprogramming for the selected remote terminal 53.
If the remote terminal 53 requires reprogramming of either or both memory areas, rapid reprogramming terminal 20 checks the old and new memory configurations to determine if the information in the IC memory card 22 is compatible with updating the old memory (program step 76) and will use a patch file if it exists. If a patch file does not exist or is not usable, rapid reprogramming terminal 20 checks to see if a complete file exists and checks to determine if this file will result in a newer revision level for the memory configuration. If the configuration message is not usable, no patch file should exist and rapid reprogramming terminal 20 uses the complete file for reprogramming the remote terminal 53. Rapid reprogramming terminal 20 will declare an error if the IC memory card 22 information is insufficient (program step 78). If the IC memory card 22 information is correct for reprogramming, rapid reprogramming terminal 20 sends a load message, FIG. 9D to enable the reprogramming function for either or both memory areas and depending upon remote terminal requirements memory areas one and two will be enabled simultaneously or sequentially (program step 80). The remote terminal 53 will next check the validity of the message utilizing internally stored information and the reprogram enable discretes if required.
Once the reprogramming mode is entered (program step 82 and 84), rapid reprogramming terminal 20 proceeds to load the new memory contents in blocks of varying size depending on the remote terminal 53 and update requirements. There will be no specific erasure commands from rapid reprogramming terminal 20. The remote terminal 53 being reprogrammed is responsible for erasure based on the directed write information. The reprogramming of a remote terminal 53 is conducted by a series of one or more header message (FIG. 9E), memory data load message (FIG. 9F), trailer message (FIG. 9H) transactions. If required, a header message, trailer message transaction will also be provided for paging or transfer of control functions. If the remote terminal 53 being reprogrammed is required to keep track of how many times a particular memory area has been reprogrammed, the remote terminal 53 being reprogrammed shall declare an abort error (bits 0-13 of the data word of the reprogram status message of FIG. 9I) if the predetermined memory write capability of the remote terminal 53 has been exceeded. The storage of this information within the remote terminal's memory shall not affect the validity of a memory verify procedure that is the remote terminal 53 being reprogrammed shall mask out this information during a verify operation.
After completion of the load (program step 84), rapid reprogramming terminal 20 will, if required, then provide transfer of control information to the remote terminal 53 using a header message, trailer message transaction (program step 86). Transfer of control prior to a verify via the control code bits (bits 0-7) of the data word four of FIG. 9I is not permitted. The transfer of control prior to a verify is not used to transfer control to a memory area of remote terminal 53 that has been loaded but not verified. If it is necessary to transfer control prior to the completion of a memory area load/verify, the two parts of the memory area are loaded/verified separately using the same technique as for sequentially loading memory areas 1 and 2. The transfer of control via the header message of FIG. 9E may be inhibited during the load.
After all required data for a particular memory area have been transferred rapid reprogramming terminal 20 will, via bit 4 or 5 of data word four of FIG. 9D disable the reprogramming function for that memory area.
When simultaneous reprogramming of memory areas one and two of a remote terminal 53 is utilized (program step 88), rapid reprogramming terminal loads the second memory area prior to the verify operation. When sequential memory area reprogramming or single memory area reprogramming is utilized, rapid reprogramming terminal 20 will at this time verify (program steps 92-96) the previously loaded memory area one load prior to the memory area two load operation. Rapid reprogramming terminal 20 performs the memory verify utilizing the same message transactions that are used for the memory load except that the rapid reprogramming terminal 20 receives the data from the remote terminal 53 being reprogrammed and compares the received data with data stored in IC memory card 22. The automatic verify after a load may be inhibited.
After completion of the verify (program step 96) rapid reprogramming terminal 20 will, if required, provide transfer of control information to the remote terminal 53 (program step 98) using either a header message, trailer message transaction or via the control code bits (bits 0-7) of the data word four of FIG. 9I. When sequential reprogramming of memory areas one and two is utilized, rapid reprogramming terminal 20 repeats the load/verify operations (program step 100) for the second memory area after reprogramming of the first memory area is complete.
Assuming there were no errors in reprogramming, rapid reprogramming terminal 20 will continue (program step 102) and reprogram the next remote terminal 53 on the 1553 multiplex data bus 42. If an error did occur, operator intervention is requested by a fault display. This concludes the discussion of protocol B of Military Standard 2217.
There is an individual memory file describing the operation of rapid reprogramming terminal 20 and containing the necessary data to reprogram each remote terminal 53 and each bus controller 55 on the 1553 multiplex data bus 42. The memory file contains a lookup table and reprogramming data for each remote terminal 53 and bus controller 55. A memory file is wholly contained in IC memory card 22.
The lookup table contains the digital information necessary for rapid reprogramming terminal 20 to communicate with the remote terminal 53 or bus controller 55 being reprogrammed. Unless otherwise specified all bits set to a logic one are active (i.e., RRT output is to be active) and all bits set to a logic zero are inactive (i.e., RRT output is to be inactive).
Referring to FIGS. 3 and 4, the specific bus connection for rapid reprogramming terminal 20 is a function of the type of aircraft on board avionics or electronic warfare equipment being reprogrammed. When rapid reprogramming terminal 20 selects a bus for connection terminal 20 will, based on aircraft type and configuration, selected the type of multiplex bus connection to be utilized.
At this time it should be noted that the cardhrds.h module includes the definition for the CARD.sub.-- HEADER.sub.-- TYPE structure which pertains to the contents of IC memory card 22. This structure definition of the cardhrds.h module has a thirty two bit word identified as Card Discretes which determines whether an automatic load to a remote terminal 53 or bus controller is permitted. Specifically, if bit 9 of this word is at the logic one state an automatic load is permitted. In addition, bit 8 of this thirty bit word when at the logic one state indicates that a copy from one memory card to the other memory card of IC memory card 22 is allowed; bit 5 allows an erasure of IC memory card 22; bit 6 allows a download to external computer 66; bit 7 allows an upload to IC memory card 22 and bit 4 determines whether the information in IC memory card 22 has been tested, verified and is releasable. The first four bits (bits 3-0) identify the security classification of IC memory card 22.
Referring now to the RRT program section cardhdrs.h module as well as FIGS. 3 and 4, the first three bits (bits 2-0) of the thirty two bit word identified as Discretes #1 in the LOOKUP.sub.-- TABLE.sub.-- TYPE structure in cardhdrs.h module of the RRT software program describe the aircraft multiplex bus to which rapid reprogramming terminal 20 will couple. When bits 2-0 are respectively 0,0,1, rapid reprogramming terminal 20 couples to primary Avionics Bus Number One; 0,1,0 couples rapid reprogramming terminal 20 to primary Avionics Bus Number Two; 0,1,1 couples rapid reprogramming terminal 20 to primary Avionics Bus Number Three; 1,0,0 couples rapid reprogramming terminal 20 to primary Avionics Bus Number Four and 1,0,1 couples rapid reprogramming terminal 20 to the Electronic Warfare Bus.
Bits 4,3 of the Discretes #1 word in the lookup table are the secondary bus identifiers with 0,0 coupling rapid reprogramming terminal 20 to secondary Avionics Bus Number One; 0,1 coupling rapid reprogramming terminal 20 to secondary Avionics Bus Number Two; 1,0 coupling rapid reprogramming terminal 20 to secondary Avionics Bus Number Three and 1,1 coupling rapid reprogramming terminal 20 to secondary Avionics Bus Number Four.
Bit 5 of the Discretes #1 word indicates whether the secondary avionics buses aboard the aircraft are usable with a logic one indicating that the buses are usable.
When bit 6 of the Discretes #1 word is a logic zero the aircraft uses a coupling transformer 60, FIG. 4, between the aircraft buses and rapid reprogramming terminal interface connectors. A logic one indicates that the aircraft uses direct coupling as is illustrated in FIG. 4. Data bit 7 of the same word is reserved for the center tap on data bus isolation transformers 213 and 214 with zero being an open center tap and one being a grounded center tap.
The next four bits (bits 11-8) of the Discretes #1 thirty two bit word set the PWR.sub.-- OFF/ON.sub.-- 1 through PWR.sub.-- OFF/ON.sub.-- 4 outputs of interface 54. Bit eight set at a logic one turns off the AYK-14 computer bus controller connected to avionics bus one, bit nine set at a logic one turns off the AYK-14 computer bus controller connected to avionics bus two, bit ten set at a logic one turns off the AYK-14 computer bus controller connected to avionics bus three and bit eleven set at a logic one turns off the AYK-14 computer bus controller connected to avionics bus four.
Bit twelve of the Discretes #1 word is used for enabling any external device such as the external processor of the AN/ALQ-165 radar jammer on board the F/A-18C/D fighter aircraft. The AN/ALQ-165 radar jammer is an electronic warfare bus controller which may be reprogrammed either in the aircraft or when removed from the aircraft. When the AN/ALQ-165 is removed from the aircraft, the power on time for example is generally limited to less than one minute for a load/verify of 32K data words of user data memory, since the aircraft's air conditioning system is not available to cool the AN/ALQ-165. The lookup table provides for reprogramming of the AN/ALQ-165 when removed from the aircraft by allowing for a maximum on time of between ten seconds and thirty minutes for the AN/ALQ-165, although it is desirable to allow the AN/ALQ-165 to be enabled for not more than one minute.
Bit thirteen is used for turning off the Maintenance Signal Data Recording Set (MSDRS) on board the F/A-18 aircraft; bit fourteen is used for enabling the loading software in the radar data processor currently being utilized with only the F/A-18 fighter aircraft and bit fifteen seven is used for enabling the loading software off the stores management system aboard the aircraft. Bit thirteen when set at a logic one state will turn off the MSDRS so it will not record the data transferred over the avionics bus while a remote terminal 53 or a bus controller 55 is being reprogrammed. Bits fourteen and fifteen when set to a logic one state respectively will enable the loading software in the radar data processor and the stores management system.
The first four bits (bits 3-0) of the next thirty two bit word (Discretes #2 in the cardhdrs.h module) in the lookup table set the IPL.sub.-- 1 through IPL.sub.-- 4 outputs of interface 54 for reprogramming the AYK-14 computers. When bit zero of the Discretes #2 word is a logic one the AYK-14 computer on avionics bus one is to be reprogrammed; when bit one of this word is a logic one the AYK-14 computer on avionics bus two is to be reprogrammed; when bit two of this word is a logic one the AYK-14 computer on avionics bus three is to be reprogrammed; and when bit three of this word is a logic one the AYK-14 computer on avionics bus four is to be reprogrammed. To reprogram any of the AYK-14 computers aboard an aircraft it is first required to turn off the power to the AYK-14 to be reprogrammed and then activate the initiate program load output of interface 54 to the AYK-14 of the computer to be reprogrammed before turning on the power to the AYK-14 computer to be reprogrammed. The AYK-14 will sense the initiate program load output is active which initiates the reprogramming of the AYK-14. A failure in the reprogramming of the AYK-14 results in a logic one at the initiate program load fail input of interface 54 when the fail input is connected to the AYK-14 being reprogrammed.
Bits four and five of the Discretes #2 word are respectively used for enabling the first and second memory areas of the remote terminals 53 within the aircraft avionics system; bit six is used for enabling the user data memories of all remote terminals 53 communicating on the electronic warfare multiplex bus and bit seven is used for enabling the operating software memories in remote terminals 53 connected to the electronic warfare multiplex bus.
The next four bits (bits 11-8) of the Discretes #2 word in the look up table determine which of the AYK-14 will be reprogrammed. When bit eight is a logic one the AYK-14 computer on avionics bus number one is to be reprogrammed; when bit nine is a logic one the AYK-14 computer on avionics bus number two is to be reprogrammed; when bit ten is a logic one the AYK-14 computer on avionics bus number three is to be reprogrammed and when bit eleven is a logic one the AYK-14 computer on avionics bus number four is to be reprogrammed.
The last bit (bit 15) of the Discrete #2 word in the lookup table determines if the Initiate Program Load Fail discretes will be used to indicate a failure when loading an AYK-14 computer. When this bit is a logic one the aircraft having the AYK-14 computer on board has the fail discrete wired and the fail discrete is being utilized by the aircraft.
The first three bits (bits 2-0) of the next word (Operational Status word) in the look up table determine the operational status of rapid reprogramming terminal 20. When bits 2-0 are respectively 0,0,1 rapid reprogramming terminal 20 operates as a remote terminal 53, the bus controller 55 converts to a remote terminal 53 and rapid reprogramming terminal 20 converts to the bus control 55. When bits 2-0 are respectively 0,1,0 rapid reprogramming terminal 20 operates as the bus controller 55. When bits 2-0 are respectively 0,1,1 rapid reprogramming terminal 20 operates as a remote terminal 53. When bits 2-0 are respectively 1,0,0 rapid reprogramming terminal 20 operates as a remote terminal 53, the bus controller 55 is quieted and rapid reprogramming terminal 20 converts to the bus control 55. Bits 6-3 are unused and bit 7 indicates that the AYK-14 computer is the normal bus controller 55.
Bits 12-8 of the Operational Status word provide the address of the remote terminal being reprogrammed.
Bits 3-0 of the next word identified as Operational Mode describe the operational mode of rapid reprogramming terminal. For example, when bits 3-0 are respectively 0,0,0,1 rapid reprogramming terminal 20 is in an operational mode by which rapid reprogramming terminal 20 is reprogramming a remote terminal 53 or a bus controller 55 which when being reprogrammed functions as a remote terminal 53. Likewise, when bits 3-0 are respectively 0,0,1,0 rapid reprogramming terminal 20 is in an operational mode by which rapid reprogramming terminal 20 is reprogramming a bus controller 55 such as the AN/ALR-67 Radar Warning Receiver which does not convert to a remote terminal.
When bits 3-0 of the Operational Mode word in the lookup table are respectively 0,0,1,1 rapid reprogramming terminal 20 may reprogram an AYK-14 computer having a serial interface module type B acting as a remote terminal; when bits 3-0 are respectively 0,1,0,0 rapid reprogramming terminal 20 may reprogram an AYK-14 computer having a serial interface module type B acting as a bus controller; when bits 3-0 are respectively 0,1,1,0 rapid reprogramming terminal 20 may reprogram an AYK-14 computer having a serial interface module type A and when bits 3-0 are respectively 0,1,1,1 rapid reprogramming terminal 20 may reprogram the High Speed Anti-Radiation Missile (HARM) Command Launch Computer. Likewise, when bits 3-0 are respectively 1,0,0,0 rapid reprogramming terminal 20 may reprogram the AYQ-9 and AYQ-15 Stores Management Systems' core memory; when bits 3-0 are respectively 1,0,0,1 rapid reprogramming terminal 20 may reprogram the AYQ-9 and AYQ-15 Stores Management Systems' EEPROM memory and when bits 3-0 are respectively 1,0,1,0 rapid reprogramming terminal 20 may reprogram the CP-1726/ASQ-194 Signal Data Computer. When bits 3-0 are respectively 1,0,1,1, rapid reprogramming terminal 20 may reprogram the Digital Map Computer and when bits 3-0 are respectively 1,1,0,0 rapid reprogramming terminal 20 may reprogram the Night Attack Display Computer.
Bit 4 of the Operational Mode word indicates if the system being reprogrammed uses paging to access its memory. Bits 7-5 of the Operational Mode Word are not used.
The next eight bits (bits 15-8) of the Operational Mode word provide for a delay of between 0 and 255 milliseconds between activity messages.
The first bit (bit 0) of the next word identified as Busy Bit and Memory word Usage in the lookup table determines whether the busy bit in the status word, FIG. 9A, provided by the remote terminal 53 is usable with a logic one indicating that the busy bit is usable. If the busy bit in the status word is usable then rapid reprogramming terminal 20 will monitor the status word provided by remote terminal 53 to determine whether remote terminal 53 can receive data from rapid reprogramming terminal 20. If the busy bit in the status word is not usable rapid reprogramming terminal 20 will issue activity messages, FIG. 9A to the remote terminal 53 to determine the busy status of the remote terminal 53, that is whether or not the remote terminal 53 can receive data from rapid reprogramming terminal 20. The seventh bit (bit 6) provides for a pause after rapid reprogramming terminal 20 sends a command word to the remote terminal 53. The eighth bit (bit 7) when at the logic zero state causes rapid reprogramming terminal 20 when functioning as a bus controller to repeat the last message whenever remote terminal 53 is busy.
Bits 15-0 of the next word identified as Automatic Busy Retry Count Before Error in the lookup table provides for the automatic mode retry count which is the number of times (between 0 and 65,535) rapid reprogramming terminal 20 can send activity messages to the remote terminal 53 being reprogrammed before rapid reprogramming terminal 20 declares an error. The sixteen bit value of this word is the total count of busy bits that may occur during a message transaction.
Bits 15-0 of the next word identified as Manual Busy Retry Count Before Error in the lookup table provide for the manual mode retry count which is the number of times (between 0 and 65,535) rapid reprogramming terminal 20 can retry reprogramming a remote terminal 53 before rapid reprogramming terminal 20 declares an error. The sixteen bit value of this word is the total count of busy bits that may occur during a message transaction.
It should be noted that the busy count for the manual retry mode is typically 3 and the busy count for the automatic retry mode is typically 256.
Bits 15-0 of the next three words identified as Nomenclature of RT in the lookup table provide for the WRA nomenclature (e.g., RT-1079 ) of the remote terminal 53 being reprogrammed.
Bits 15-0 of the next word identified as Memory Configuration Word 1 in the lookup table represents the configuration of the data stored in memory area one of the remote terminal 53 being reprogrammed. Similarly, bits 15-0 of the word identified as Memory Configuration Word 2 in the lookup table represent the configuration of the data stored in memory area two of the remote terminal 53 being reprogrammed. These two words in the lookup table contain the memory configuration message, FIG. 9C, data word one and data word two comparison information and are only used for remote terminals 53 and bus controllers 55 that allow the memory configuration message of FIG. 9C. At this time, it should that the user data memory in electronic warfare devices is equivalent to memory area one and operating software memory in electronic warfare devices is equivalent to memory area two.
Bits 7-2 of the next word identified as Memory Control in the lookup table provide the fill data bits (bits 15-10 of data word four) of the load/verify message of FIG. 9D.
Bit 8 of this Memory Control word allows for the transfer of control within the remote terminal 53 being reprogrammed to the program which was loaded once the data is verified as being loaded correctly. Bits 13-12 of this word provide a code which indicates whether either memory area one or memory area two or both memory areas are to be disabled, while bits 15-14 provide a code which indicates whether either memory area one or memory area two or both memory areas are to be enabled. It should be understood that bits 15-14 and 13-12 are software controlled enables and disables which are provided to the load/verify message of FIG. 9D.
Bits 1-0 of the next word identified as File and Control Type in the lookup table represent a code which indicates whether a single memory area is to be loaded or whether memory areas one and two are to be loaded in sequence or simultaneously. When bit 2 of this word is zero a verify is not permitted. When bit 3 of this word is a logic one a verify operation may be performed without a data load. Bits 7-4 provide for the aircraft configuration. Bits 15-10 provide fill data for word four of the reprogram control message, FIG. 11D, when communicating with a bus controller 55.
Bits 4-0 of the next word identified as BC and RRT addresses in the lookup table provide the remote terminal address for a bus controller 55 which can convert to a remote terminal when being reprogrammed.
Bits 12-8 of this word provide the address for rapid reprogramming terminal 20 when terminal 20 operates as a remote terminal 53.
The next three words identified as Nomenclature of BC in the lookup table provide for the WRA nomenclature (six ASCII characters) of bus controller 55 when rapid reprogramming terminal 20 is controlling a bus controller 55.
The messages of utilized by rapid reprogramming terminal 20 to communicate with a bus controller 55 being reprogrammed via the 1553 multiplex data bus 42 will now be discussed. It should be understood that the messages used by rapid reprogramming terminal 20 to communicate with any bus controller 55 aboard the aircraft via the 1553 data bus are required to follow the message formats set forth in FIGS. 7 and 11.
The Activity Message of FIG. 11A is utilized by bus controller 55 when being reprogrammed to determine whether rapid reprogramming terminal 20 (which is operating as a remote terminal) is ready to receive data and allows rapid reprogramming terminal 20 a request to send information to bus controller 55 or receive information from bus controller 55. The Activity Message of FIG. 11A allows rapid reprogramming terminal 20 to control the loading sequence when functioning as a remote terminal. The bus controller 55 commands this message at a periodic rate until a Header Message, FIG. 11E, Memory Data Message, FIG. 11F, Trailer Message, FIG. 11H transaction is begun. After receipt of a Header Message requiring data transfer (TM is not equal to zero), the bus controller 55 may utilize the Activity Message to control the transfer of Memory Data Messages or the bus controller 55 may utilize the Header Message information to internally control the number of Header Data Messages so long as the busy bit (bit 3) in the rapid reprogramming terminal Status Response Word, FIG. 11B, is checked by the bus controller 55. The bus controller 55 may also control the load or the verify (all the Header Message, Memory Data Message, Trailer Message transactions) without the use of the Activity Message by monitoring the TC bits (bits 0-1 of data word four) in the Header Message.
At this time it should be noted that the following discussion relates primarily to protocol C of Military Standard 2217(AS).
Referring to FIG. 11A the Command Word for the Activity Message follows the format set forth in FIG. 7. Bits 11-15 provide the address for rapid reprogramming terminal 20, bit 10 is set at a logic one, the subaddress (bits 5-9) is set at 07 hexadecimal and the word count (bits 0-5) is one.
The status word response to the Activity Message as well as the other messages follows the general format set forth in FIG. 7 supplemented by FIG. 11B. A Status Response Word to any of the messages is provided by a rapid reprogramming terminal 20 for each message transaction. The status response word follows data on a rapid reprogramming terminal receive type transaction and precedes the data on a rapid reprogramming terminal transmit type transaction. The bus controller 55 allows a response time gap of approximately 6.5 usec. from the end of the last transmitted command word (transmit type message) or the end of the last transmitted data word (receive type message), to the start of the rapid reprogramming terminal status response word before declaring a no response error. Rapid reprogramming terminal 20 begins the status response word within a time period of approximately 2-5 usec. from the receipt of the end of the last command word (transmit type message) or the receipt of the end of the last data word (receive type message). The bus controller 55 ensures that the time from the end of the rapid reprogramming terminal transmission of the last data word (transmit type message) or the end of the last status response word (receive type message) to the beginning of the next command word is at least 2 usec.
Referring to FIG. 11B, the status response word bits for each message comprises a terminal address (bits 11-15) which is remote terminal address of the remote terminal 53 being reprogrammed (referred to as ZZZZZ); a message error bit (bit 10) which is not used; a service request bit (bit 8) and a busy bit (bit 3).
The service request bit (bit 8) is set to one by rapid reprogramming terminal 20 in response to an activity message from the bus controller 55, otherwise this bit is zero.
The busy bit (bit 3) may be utilized by rapid reprogramming terminal 20 for the status response word for any command word from the bus controller 55. The setting of this bit to a logic one means that a message previously received by rapid reprogramming terminal 20 or internal rapid reprogramming terminal 20 requirements necessitates suspension or slow down communications with the bus controller 55. If rapid reprogramming terminal 20 sets the busy bit in the status response word, it may suppress transmission of the data words associated with each message. All additional message traffic other than the activity message is suspended until the busy bit is cleared (logic 0). While the bus controller 55 is waiting for the busy bit to clear, the activity message is sent every 10 to 100 milliseconds. As long as the busy bit is clear the bus controller 55 assumes that rapid reprogramming terminal 20 can support a continuous stream of identical messages within a 2 msec. time period from the end of one message to the start of the next command word. The continuous stream of identical messages is assumed to be either memory data load or memory data verify messages.
This continuous stream is maintained for a time period compatible with IC Memory Card 22 and internal memory capabilities of rapid reprogramming terminal 20. Rapid reprogramming terminal 20 utilizes the busy bit to suspend the continuous stream when required. As a minimum rapid reprogramming terminal 20 provides 2K data words in memory data load or memory data verify messages per second. Any data word transmitted after a status word with the busy bit set is ignored by rapid reprogramming terminal 20. The bus controller 55 ensures that the message for which rapid reprogramming terminal 20 initially replied with the busy bit set in the status response word will be transferred once the busy bit is cleared.
The Terminal Flag bit (bit 0) is set to a logic one by rapid reprogramming terminal if bit 10, 8 or 3 is set to one. Bits 9, 7, 6, 5, 4, 2 and 1 will always be zero in the status response word provided by rapid reprogramming terminal 20.
Referring again to FIG. 11A, the address (bits 11-15) for the status word response to the activity message is the address of rapid reprogramming terminal 20 when reprogramming a bus controller 55. The rapid reprogramming terminal address is the address assigned to each individual aircraft on the particular bus selected by the rapid reprogramming terminal switching network.
The status word response to the activity message includes the service request bit (bit 8) which rapid reprogramming terminal 20 sets to a logic one whenever the contents of bits 0 through 10 of the data word are other than zero. The bus controller 55 may utilize the service request bit to determine if it is necessary to examine bits 0 through 10 of the data word that follows. Since the contents of bits 0 through 10 of the data word control the state of the service request bit, it is not necessary for the bus controller 55 to process the service request bit.
The busy bit (bit 3) in the status response word when at the logic one state indicates that rapid reprogramming terminal 20 is not ready to process any message from the bus controller 55 other than the activity message. Prior to transmission of any other messages to rapid reprogramming terminal 20, the bus controller 55 will continue to send activity messages to rapid reprogramming terminal 20 every 10 to 100 milliseconds until the busy bit is cleared. The busy bit and the service request bit are not set simultaneously by rapid reprogramming terminal 20.
The data word in the activity message is transmitted by rapid reprogramming terminal 20 even when the busy bit (bit 3) is set in the status response word. The busy bit (bit 15) in the data word in the activity message is used to completely implement the busy response.
Bits 0-10 are utilized to allow rapid reprogramming terminal 20 to request that the bus controller 55 being reprogrammed send a specific message to rapid reprogramming terminal 20. As a result of this request by rapid reprogramming terminal 20 the bus controller 55 will transmit a command word with the address of rapid reprogramming terminal 20 in bits 11-15 of the command word.
The transmit/receive bit (bit 10 of the data word) is set to one when rapid reprogramming terminal 20 is to transmit a message and is set to one zero rapid reprogramming terminal 20 is to receive a message. The subaddress bits (bits 5-9) indicates the subaddress of the message to be provided by bus controller 55 to rapid reprogramming terminal 20, while the word count bits (bits 0-4) indicate the data word count for the message. The remaining bits (bits 11-14) of the data word are zero.
Referring to FIG. 11C, the activity message provided prior to the memory configuration message requests that the bus controller 55 provide to rapid reprogramming terminal 20 the memory configuration message. The memory configuration message is utilized to read the current memory configuration of the bus controller 55 being reprogrammed. This message is only used when its use is indicated in a lookup table for the bus controller 55. The command word and status word for the memory configuration message follow the format of FIG. 7. Each bus controller 55 aboard an aircraft has up to two memories designated memory area one and memory area two. Data bits 0-15 of data word one of the memory configuration message represent the configuration of the data stored in memory area one. Unused data bits equal zero. Similarly, data bits 0-15 of data word two of the memory configuration message represent the configuration of the data stored in memory area two. Unused data bits also equal zero. In the automatic mode of operation this message is used for the purpose of comparing a bus controller's configuration stored in the IC memory card 22 with reported bus controller configuration. If the reported value is the same as the value stored in the IC memory card 22, rapid reprogramming terminal 20 will not perform a load operation. However, if the reported value is different from the value stored in the IC memory card 22, rapid reprogramming terminal 20 will proceed with a load operation.
Referring to FIG. 11D, there is shown the format for the enter load, exit load, enter verify and exit verify messages. The activity message provided prior to the enter load, exit load, enter verify and exit verify messages requests that the bus controller 55 provide to rapid reprogramming terminal 20 the required enter load, exit load, enter verify or exit verify message.
The transmit/receive bit (bit 10) in the command word for the enter load, exit load, enter verify and exit verify messages is a logic one since rapid reprogramming terminal 20 which is operating as a remote terminal is to transmit data to the bus controller 55 being reprogrammed. The terminal subaddress field (bits 5-9) in the control word is set at 1D hexadecimal. Each message enter load, exit load, enter verify and exit verify requires that an enable signal be provided by rapid reprogramming terminal 20 before a load or verify may be executed. A logic one at the EW.sub.-- OSM.sub.-- EN output of interface 54 enables the operating software memory of the electronic warfare system on board the aircraft. Similarly, a logic one at the EW-UDM.sub.-- EN output of interface 54 enables the user data memory of the electronic warfare system on board the aircraft. When the AV.sub.-- EN1 output of interface 54 is at a logic one state the first memory areas of the aircraft avionics system are enabled, while a logic one at the AV.sub.-- EN2 output of interface 54 enables the second memory areas of the aircraft avionics system.
Each field in the data is checked by the remote terminal 53 for compliance with the following prior to execution of a load or verify. The type and number fields are defined based on WRA nomenclature (e.g., CP-1293); however, if this creates a conflict, the system nomenclature (e.g., ALR-67) is utilized instead. The preferred embodiment of the present invention uses WRA nomenclature.
Data word one (bits 0-15) is the type field consisting of the first two eight bit ASCII characters that represent the nomenclature of the bus controller 55 being controlled. For example, for CP-1293 the two characters would be "C", "P".
Data word two (bits 0-15) is a number field for consisting of the third and fourth eight bit ASCII characters that represent the nomenclature of the bus controller 55 being controlled. For example, for CP-1293 the two characters would be "1", "2".
Data word three (bits 0-15) is a number field two consisting of the last two eight bit ASCII characters that represent the nomenclature of the bus controller 55 being controlled. For example, for CP-1293 the two characters would be "9", "3".
Data word four (bits 10-15) is the fill field which may be any bit pattern including zero and is to be defined by the individual bus controller 55 being controlled. The fill field is required to be checked even if the field is defined as zero. The fill field is contained in a look up table for the bus controller 55 being reprogrammed.
The load/verify bits (bits 8-9) are used to described whether a Load, Verify, or other type transaction will follow. The load/verify bits are coded as follows: L/V=01 indicates that a memory load follows; L/V=10 indicates that a memory verify follows; L/V=11 is not used and L/V=00 indicates that a enter load, enter verify, exit load or exit verify message is being sent for some reason other than a load or verify such as to quiet a bus controller.
The control code (bits 0-7) of data word four are set as follows: bit 7 is a reprogram enable for memory area one and is equal to 80 hexadecimal; bit 6 is a reprogram enable for memory area two and is equal to 40 hexadecimal; bit 5 is a reprogram disable for memory area one and is equal to 20 hexadecimal and bit 4 is a reprogram disable for memory area two and is equal to 10 hexadecimal. Bit 3 of the control code is not used by rapid reprogramming terminal 20 when reprogramming bus controllers functioning as bus controllers. Bit 2 of the control code which is 02 hexadecimal tells the bus controller 55 to stop transmitting or receiving information on the bus so as to allow the bus controller 55 to be reprogrammed. The use of bit 2 of the control code in this manner is required because some bus controllers can not be converted to a remote terminal when reprogramming a remote terminal 53. Bit 1 of the control word which is 02 hexadecimal is utilized to have a bus controller when converted to a remote terminal revert back to a bus controller. Bit 0 of the control code which is 01 hexadecimal causes the bus controller 55 to begin executing starting at the address previously supplied via data word three or data word four of a header message.
The control code field is valid only if all other fields are correct and only if either the Avionics Reprogram Enable 1 (AV.sub.-- EN1 output of interface 54); or the EW UDM Reprogram Enable discrete (the EW-UDM.sub.-- EN output of interface 54) is present or the Avionics Reprogram Enable 2 (AV.sub.-- EN2 output of interface 54) or the EW OSM Reprogram Enable discrete (EW-OSM.sub.-- EN output of interface 54) is present. At the end of reprogramming, rapid reprogramming terminal 20 will maintain the active discrete for at least 100 msec after the transmission of an exit load or exit verify message that ends the reprogramming mode.
The following are the only valid control codes that can occur when rapid reprogramming terminal 20 is functioning as a remote terminal during a load or verify. Any other code shall cause the bus controller to not execute a load or verify.
Code 00000000 which is 00 hexadecimal indicates that no load or verify control action is to be taken.
Code 00000001 which is 01 hexadecimal will cause the bus controller 55 to begin execution starting at the address previously supplied via data word three and data word four of the header message.
Code 00000100 which is 04 hexadecimal will cause the bus controller 55 to stop communications on the bus. Once the bus controller 55 stops communications on the bus, communications activity on the bus will remain stopped until the Avionics Reprogram Enable 1/EW UDM Reprogram Enable discrete and the Avionics Reprogram Enable 2/EW OSM Reprogram Enable discrete are inactive.
Code 0000100 which is 08 hexadecimal will cause the bus controller 55 being reprogrammed to revert to a remote terminal. Upon execution of this reprogram control code the message traffic shall be for rapid reprogramming terminal 20 functioning as a bus controller using the messages illustrated in FIG. 9.
Code 00010000 which is 10 hexadecimal will cause the bus controller to exit the reprogramming mode for memory area two. This code shall only be valid if the Avionics Reprogram Enable 2 or EW OSM Reprogram Enable discrete is active.
Code 00100000 which is 20 hexadecimal will cause the bus controller to exit the reprogramming mode for memory area one. This code shall only be valid if the Avionics Reprogram Enable 1 or EW UDM Reprogram Enable discrete is active.
Code 00110000 which is 30 hexadecimal is a combination of 10 hexadecimal and 20 hexadecimal for simultaneous memory areas one and two exit reprogramming mode.
Code 01000000 which is 40 hexadecimal will cause the bus controller 55 to enter the reprogramming mode for memory area two. This code shall only be valid if the Avionics Reprogram Enable 2 or the EW OSM Reprogram Enable discrete is active.
Code 10000000 which is 80 hexadecimal will cause the bus controller 55 to enter the reprogramming mode for memory area one. This code shall only be valid if the Avionics Reprogram Enable 1 or the EW UDM Reprogram Enable discrete is active.
Code 11000000 which is CO hexadecimal is a combination of 40H and 80H for simultaneous memory areas one and two enter reprogramming mode.
Referring to FIG. 11E there is shown the format for a header message which is used to pass load and verify parameters to the bus controller 55 being reprogrammed. The activity message shown prior to the header message request that the bus controller 55 being reprogrammed command the header message from rapid reprogramming terminal 20. The activity message will not be used by bus controllers 55 which keep track of header, memory data, trailer message sequence, that is the bus controller automatically commands this message sequence without rapid reprogramming terminal 20 requesting each message.
The transmit/receive bit (bit 10) in the command word is at the logic one state since rapid reprogramming terminal 20 which is functioning as a remote terminal is to transmit data and the terminal subaddress field (bits 5-9) is set at 14 hexadecimal. The transfer mode (bits 14-15) are used to describe the memory data load or memory data verify message data word content. The transfer mode bits are binary coded as follows: TM=00; TM=01; TM=10 and TM=11. When TM=00 which is the no transfer mode, the buffer transfer count contained in data word one and the initial load address contained in data word two have no meaning. This mode is used to transfer the program entry address contained in data word three and Page Number contained in data word four or is used as a preamble to the trailer message.
When TM=01, each sixteen bits of data transmitted in a data word will contain only eight bits of information in bits 0-7. When TM=10, each sixteen bits of data transmitted in a data word will contain sixteen bits of information in bits 0-15. When TM=11, the sixteen bits of data transmitted in each odd word (first is odd) contains the sixteen least significant bits of data in bits 0-15 and each even word (second is even) contains the sixteen most significant bits of data in bits 0-15.
The header type bits (bits 12-13) are used to describe the header and have no meaning when the transfer mode is 00. The header type are binary coded as follows: HT=00, HT=01, HT=10 and HT=11. When HT=00, the buffer transfer count equals the number of words to be transferred. When HT=01, the buffer transfer count equals number of messages to be transferred. HT=10 is undefined, while HT=11 reserved for internal use by digital signal processor 20 and therefore will not be transmitted on the 1553 multiplex data bus 42 aboard the aircraft.
The buffer transfer count (bits 0-11) is used to indicate the amount of data that will follow the header message. The buffer transfer count has no meaning when the transfer mode is 00. The range of the buffer transfer count is from one to four thousand ninety six words.
When HT=00, the buffer transfer count is the total number of data words that will be transmitted in a transaction which includes the header message and trailer message. The data words are transmitted in 32-word messages since each transfer sequence is limited to thirty two data words (see FIG. 8) with the last message containing from one to thirty two data words. The maximum transfer for HT=00 is four thousand ninety six words using one hundred twenty eight memory data load or memory data verify messages.
When HT=01, the buffer transfer count is the number of memory data load or memory data verify messages that will follow the header message. Thus, the maximum data transfer per header message is 4096.times.32 data words per memory data load or memory data verify message which equals 131,072 sixteen bit words (128K). If paging (data word four, bits 0-1) is utilized for transfer modes 01 or 10, the maximum value of the buffer transfer count will be 2048 which results in 65,536 sixteen bit data words (64K) for transfer modes 01 and 10.
Data word two is the initial load address (bits 0-15) which is the sixteen or less least significant bits of the point in memory into which data is to be loaded or read. The maximum value (number of bits) used in the initial load address is compatible with the page size of remote terminals using paging. Unused bits equal zero.
Data word three is program entry address (bits 0-15) which has meaning only for transfer mode=00. The program entry address is the sixteen or less least significant bits of the point in memory at which the bus controller 55 being reprogrammed is to begin execution after receipt of an execute command in the load/verify message of FIG. 11D or when a transfer control is indicated in data word four. The load/verify message, FIG. 11D, is only used with bus controllers which require this command. The maximum value (number of bits) used in the program entry address is compatible with the page size of remote terminals using paging. Unused bits equal zero.
Data word four is the page number (bits 3-15) representing up to the thirteen most significant bits for a paged memory address within the bus controller 55. The page number applies to the program entry address for transfer mode=00 or the initial load address for transfer modes=01, 10 or 11. Unused bits shall equal 0. It should be noted that a page comprises 65,536 addresses in memory.
The transfer control bits 0-1 may be used to transfer control to a loaded program after a verify is processed or to an unaltered memory area after a load is completed, that is a bus controller 55 has been reprogrammed. When the transfer control bits equal 01 this indicates to the bus controller 55 being reprogrammed that this is the last header, memory data load or verify (up to 4096 messages), trailer or header, trailer transaction. When the transfer control bits equal 00 this indicates to the bus controller 55 being reprogrammed that more data is to follow the current header, memory data load or verify (up to 4096 messages), trailer transaction or header, trailer transaction and control should not be transferred. For bus controllers 55 using paging and the program entry address, the transfer control will remain equal to 01 even for the last data transaction, until a transfer mode equals 00 message is used to supply the program entry address and page number. Transfer control equal to 10 indicates that control is to be transferred to the program entry address of data word three. When control is transferred, the transfer does not take place until after the trailer message and control is transferred only to non-reprogrammed areas or verified areas in memory. Transfer control equals 11 is invalid and bit 2 equals zero.
Referring to FIG. 11F there is shown the format for a memory data load message which is used to transfer the data to be loaded into the memory of a bus controller 55 being reprogrammed. The activity message provided prior to a memory data load message is used only for bus controllers 55 that do not keep track of the number of memory data load messages required for each header, memory data, trailer transaction or for bus controllers that do not check the busy bit in the status response word, Fig. 11B, provided by rapid reprogramming terminal 20.
The transmit/receive bit (bit 10) in the command word is at the logic one state since the rapid reprogramming terminal 20 is to transmit and the terminal subaddress field (bits 5-9) is set at 15 hexadecimal, while the word count may vary from one to thirty two.
If the busy bit (bit 3) is set to a logic one in the status response word for a memory data load message, no data words would be required to be sent by rapid reprogramming terminal 20. After the busy bit is cleared in the status response word of the activity message, the bus controller 55 commands the memory data load message for which no data was received. The number of data words will equal the word count in the memory data load message command word.
Referring to FIG. 11G there is shown the format for a memory data verify message which is used to transfer the data that rapid reprogramming terminal 20 will compare to the data stored in IC memory card 22.
The transmit/receive bit (bit 10) in the command word is at the logic zero state since the rapid reprogramming terminal 20 is to transmit data and the terminal subaddress field (bits 5-9) is set at 15 hexadecimal, while the word count may vary from one to thirty two.
If the busy bit (bit 3) is set to a logic one in the status response word for a memory data verify message then bus controller 55 will retransmit the memory data verify message (i.e., same data words ) after the busy bit is cleared in the status response word of the activity message.
The number of data words will equal the word count in the memory data verify message command word.
Referring now to FIG. 11H, the trailer message is used to pass the data checksum and additional load or verify parameters to the bus controller 55 being reprogrammed. The activity message shown prior to the trailer message request that the bus controller 55 command the trailer message. The activity message provided prior to a trailer message is used only for bus controllers 55 that keep track of the header, memory data, trailer transaction, that is the bus controller 55 automatically commands this message sequence without rapid reprogramming terminal 20 requesting each message.
The transmit/receive bit (bit 10) in the command word for the trailer message is a logic one since rapid reprogramming terminal 20 is to receive data and the terminal subaddress field (bits 5-9) in the command word is set at 16 hexadecimal.
Data word one contains the number of sub-pages and the first sub-page for bus controllers 55 utilizing paging or sub-paging. This word may also be used for internal register control. The fields of data word one represent the values to be used in the next header, memory data load or verify (up to 4096 messages), trailer transaction. For the first header, memory data load or verify (up to 4096 messages), trailer transaction the information will be transmitted prior to the memory data transaction via a header message, trailer message transaction in which the TM (transfer mode) field in data word one of the header is 00.
The sub-page/register count (bits 8-15) field in data word one may be used in lieu of or in conjunction with the page number field in data word four of the header message and is individual user definable. Unused bits equal zero. In the preferred embodiment of the present invention the sub-page field in data word one of the trailer message is used in conjunction with the data word four of the header message of FIG. 11E.
For the purpose of illustrating the use of the sub-page field in the trailer message the following example is provided. In order to load 256K of memory into a bus controller 55 with bank switching, 64K of address capability and a page size definition of 2048 words, the following approach may be used. To load 256K with sub-pages 2048 words long requires 128 header, memory data, memory data, trailer transactions (256K/2048=128). The 128 transactions consist of 32 transactions for each of the four banks of switching in bus controller 55. Thus, for each 32 transactions the header message, data word four page number, FIG. 9E, equals the bank number which would be incremented from zero to three. Within each group of 32 transactions the sub-page count would increment every transaction from zero to thirty one. For each transaction (assuming HT=01 for buffer transfer count equals the number of messages) the header data one buffer transfer count would be 64 (2048 words/32 words per message).
The first sub-page/register (bits 0-7) field may be used in lieu of or in conjunction with the page number field in data word four of the header message and may be defined by the user. Unused bits equal zero. Examples of use of this field are: specifying a processor register into which the page number field in data word four of the header message is to be loaded or specifying the initial sub-page count in the example set forth above to one so as to not reprogram the first 2048 memory locations (the first group of transactions would only be 31 transactions long (1 to 31) and the sub-page count for the first transaction would be set to one to indicate a starting address of 2048).
The data word two checksum (bits 0-15) is the checksum of an entire transaction, i.e., header, memory data, memory data, trailer transaction (when TM in header data word one is not equal to zero) or header, trailer transaction (when TM in header data one is equal to zero). The checksum is derived by a two's complement sixteen bit addition of every data word in the transaction (i.e., header, memory data, and trailer data words) with the exception of the checksum data word which is data word two of the trailer message. The two's complement sixteen bit addition is binary addition with the carry discarded, that is there is no end around carry (e.g., FFFF (hexadecimal)+1=0).
The bus controller 55 being reprogrammed is responsible for comparing the checksum received from rapid reprogramming terminal 20 with the data words for both load and verify functions. The checksum value in data word two of the trailer message is the checksum that should be computed by the bus controller 55. If the value computed does not match the value received from processor 21 for either a load or verify operation, an error is declared and a reprogram status message is sent by bus controller 55.
Referring to FIG. 11I, the reprogram status message is used by the bus controller 55 to inform rapid reprogramming terminal 20 of an error condition.
The transmit/receive bit (bit 10) of the command word of the reprogram status message is set at a logic zero since rapid reprogramming terminal 55 is to receive information and the subaddress (bits 5-9 of the command word) for this message is 17 hexadecimal.
The status flag (bit 15) of data word one is set to a logic one to indicate that the remainder of the data word should be processed by rapid reprogramming terminal 20, that is the reprogram status message contains valid data. If this bit is set to a logic zero, the reprogram status message will be ignored by rapid reprogramming terminal 20.
The status indicator (bit 14) defines the meaning of the remainder of the data word, that is an error code or a status code to be displayed by rapid reprogramming terminal 20.
When the status indicator equals zero this indicates that an error has occurred and the error code will be processed by rapid reprogramming terminal 20.
When the status indicator equals one this indicates that no error has occurred and the status code in bits 13-0 are to be displayed on liquid crystal display 57 as 4 hexadecimal characters (bits 15 and 14 of the display value are 0). With the status indicator equal to one the values of bits 13-0 will be used to indicate status or progress through the load or verify operation.
When SF equals one and SI equals one the status code bits 0-13 are display characters. When SF equals one and SI equals zero bits 0-13 represent error codes and the desired rapid reprogramming terminal 20 action. The error codes are 0001 (hexadecimal) which is an abort; 0002 (hexadecimal) which is a restart; 0003 (hexadecimal) which is a retry and 0004 (hexadecimal) which is a automatic retry.
The abort error code indicates to rapid reprogramming terminal 20 that the load operation or verify operation has been aborted and should not be retried. Rapid reprogramming terminal 20 will display the error code and wait for an operator response. On receiving the response from the operator, rapid reprogramming terminal 20 will abort the load of the bus controller 55 being reprogrammed and continue with the load of the next bus controller or remote terminal to be reprogrammed if there is a requirement to reprogram another bus controller or remote terminal.
The restart status code indicates that an unrecoverable error has occurred in loading a bus controller 55 and a reload of bus controller 55 is desired. Rapid reprogramming terminal 20 will display the error code and wait for an operator response. On receiving the response from the operator, rapid reprogramming terminal 20 will restart the load of the bus controller 55 being reprogrammed.
The retry status code indicates that an error has occurred in the last message sequence transaction and a repeat of the sequence is desired. Rapid reprogramming terminal 20 will display the error code and wait for an operator response. On receiving the response from the operator, rapid reprogramming terminal 20 will repeat the last transaction.
The automatic retry status code indicates that an error has occurred in the last message sequence transaction. After three consecutive retries, rapid reprogramming terminal 20 will display the error code and wait for an operator response. However, if the retry is successful before reception of the third consecutive error, an error message will not be displayed and operation will continue as normal. On receiving the response from the operator, rapid reprogramming terminal 20 will abort the load of the bus controller 55 being reprogrammed and continue with the load of the next bus controller or remote terminal to be reprogrammed.
Referring to FIG. 11J, if an RRT error message occurs, the rapid reprogramming terminal 20 sets the busy bit in the status response word for all messages and may suppress transmission of any data words. The bus controller 55 will then poll rapid reprogramming terminal 20 with activity messages. When rapid reprogramming terminal 20 is ready for the bus controller 55 to command the RRT error message, it will clear the busy bit, set the service request bit in the status response to the activity message and transmit the data word requesting that the bus controller 55 command the RRT error message.
Data word one, bit 2 is an abort which is set to a logic one by rapid reprogramming terminal 20 to notify the bus controller 55 that the load or verify has been aborted and no further retries will be made.
Bit 1 is a complete restart which is set to a logic one by rapid reprogramming terminal 20 to notify the bus controller 55 that an unrecoverable error has occurred and all memory data load or memory data verify transactions will be restarted. Bit 0 is the transaction bit which is set to a logic one by rapid reprogramming terminal 20 to notify the bus controller 55 that there was an error detected in the last header, memory data, trailer or header, trailer transaction and that the transaction will be repeated. The remaining bits (bits 3-15) of the data word are a logic zero.
Referring now to FIG. 12, the operation of rapid reprogramming terminal 20 functioning as a remote terminal when reprogramming a bus controller 55 which does not revert to a remote terminal during reprogramming will now be discussed.
When the lookup table for the bus controller indicates that the bus controller 55 supports memory configuration as identified by the bus controller's software, rapid reprogramming terminal 20 request a memory configuration message, FIG. 11C, from the bus controller 53 being programmed. The memory configuration message describes the current memory contents for one or two memory areas of the bus controller 55 being reprogrammed. Rapid reprogramming terminal 20 compares the received memory configuration to the current memory configuration for the bus controller 55 stored in IC memory card 22 (program step 122). In automatic mode, if the bus controller 55 already contains the current memory configuration, rapid reprogramming terminal 20 continues on to the next remote terminal 53 or bus controller 55 to be processed (program step 152). If the memory configuration message is not usable, rapid reprogramming terminal 20 will assume that the bus controller 55 requires reprogramming. In manual mode, rapid reprogramming terminal 20 will display the memory configuration data and continue reprogramming for the selected bus controller 55.
If the bus controller 55 requires reprogramming of either or both memory areas, rapid reprogramming terminal 20 checks the old and new memory configurations to determine if the information in the IC memory card 22 is compatible with updating the old memory (program step 126) and will use a patch file if it exists. If a patch file does not exist or is not usable, rapid reprogramming terminal 20 checks to see if a complete file exists and checks to determine if this file will result in a newer revision level for the memory configuration. If the configuration message is not usable, no patch file should exist and rapid reprogramming terminal 20 uses the complete file for reprogramming the bus controller 55. Rapid reprogramming terminal 20 will declare an error if the IC memory card 22 information is insufficient (program step 128). If the IC memory card 22 information is correct for reprogramming, rapid reprogramming terminal 20 sends a load message, FIG. 11(D), to enable the reprogramming function for either or both memory areas and depending upon bus controller requirements memory areas one and two will be enabled simultaneously or sequentially (program step 130). The bus controller 55 will next check the validity of the message utilizing internally stored information and the reprogram enable discretes if required.
Once the reprogramming mode is entered (program step 132 and 134), rapid reprogramming terminal 20 proceeds to load the new memory contents in blocks of varying size depending on the bus controller 55 and update requirements. There will be no specific erasure commands from rapid reprogramming terminal 20. The bus controller 55 being reprogrammed is responsible for erasure based on the directed write information. The reprogramming of a bus controller 55 is conducted by a series of one or more header message (FIG. 11E), memory data load message (FIG. 11F), trailer message (FIG. 11H) transactions. If required, a header message, trailer message transaction will also be provided for paging or transfer of control functions. If the bus controller 55 being reprogrammed is required to keep track of how many times a particular memory area has been reprogrammed, the bus controller 55 being reprogrammed shall declare an abort error (bits 0-13 of the data word of the reprogram status message of FIG. 11I) if the predetermined memory write capability of the bus controller 55 has been exceeded. The storage of this information within the bus controller's memory shall not affect the validity of a memory verify procedure that is the bus controller 55 being reprogrammed shall mask out this information during a verify operation.
After completion of the load (program step 134), rapid reprogramming terminal 20 will, if required, then provide transfer of control information to the bus controller 55 using a header message, trailer message transaction (program step 136). Transfer of control prior to a verify via the control code bits (bits 0-7) of the data word four of FIG. 11I is not permitted. The transfer of control prior to a verify is not used to transfer control to a memory area of bus controller 55 that has been loaded but not verified. If it is necessary to transfer control prior to the completion of a memory area load/verify, the two parts of the memory area are loaded/verified separately using the same technique as for sequentially loading memory areas 1 and 2. The transfer of control via the header message of FIG. 11E may be inhibited during the load.
After all required data for a particular memory area have been transferred rapid reprogramming terminal 20 will, via bit 4 or 5 of data word four of FIG. 11D disable the reprogramming function for that memory area.
When simultaneous reprogramming of memory areas one and two of a bus controller 55 is utilized (program step 140), rapid reprogramming terminal loads the second memory area prior to the verify operation. When sequential memory area reprogramming or single memory area reprogramming is utilized, rapid reprogramming terminal 20 will at this time verify (program steps 142-146) the previously loaded memory area one load prior to the memory area two load operation. Rapid reprogramming terminal 20 performs the memory verify utilizing the same message transactions that are used for the memory load except that the rapid reprogramming terminal 20 receives the data from the bus controller 55 being reprogrammed and compares the received data with data stored in IC memory card 22. The automatic verify after a load may be inhibited.
After completion of the verify (program step 146) rapid reprogramming terminal 20 will, if required, provide transfer of control information to the remote terminal 53 (program step 148) using either a header message, trailer message transaction or via the control code bits (bits 0-7) of the data word four of FIG. 11I. When sequential reprogramming of memory areas one and two is utilized, rapid reprogramming terminal 20 repeats the load/verify operations (program step 150) for the second memory area after reprogramming of the first memory area is complete.
Assuming there were no errors in reprogramming, rapid reprogramming terminal 20 will continue (program step 152) and reprogram the next remote terminal 53 or bus controller 55 on the 1553 multiplex data bus 42. If an error did occur, operator intervention is requested by a fault display. This concludes the discussion of protocol C of Military Standard 2217.
Referring to FIGS. 19A-19S there is shown a flow chart for the software used by rapid reprogramming terminal 20 to reprogram bus controllers 55 and remote terminals 53 connected to the 1553 multiplex data bus 42.
Referring to FIG. 19A power to rapid reprogramming terminal 20 is turned on by activating switch 44 (program step 270), the digital signal processor 21 of rapid reprogramming terminal 20 is initialized during program step 272 and the system is initialized during program step 273. A built in test of the rapid reprogramming terminal controller board is performed during program step 276. Program step 276 which comprises the basicbit.c code test liquid crystal display 57, UARTs 37 and 39, bus controller 41, interfaces 52, 54 and 56, EEPROM 23 which consists of EEPROMs 240, 241, 244 and 246 and the IEEE-488 interface bus controller 260. The program next waits for user input (program step 278).
Referring to FIGS. 19B, 19C and 19D, the digital signal processor stack and interrupts are initialized during program step 282, variables are initialized by entering the autoinit routine (program step 284) and the digital signal processor timers, serial ports and external busses are initialized during program step 286. The software of Appendix A next enters the sysinit.asm module. It should be noted that the preferred embodiment does not use interrupts.
Referring to FIG. 19E, UARTs 37 and 39 are initialized during program step 300 bus controller 41 is initialized during program step 302, bus controller 260 is initialized during program step 304 and the parallel peripheral interface (PPI) ports PA0-PA7, PB0-PB7 and PC0-PC7 of programmable peripheral interfaces 52, 54 and 56 are initialized during program step 306. The software of Appendix A then enters the basicbit.c module.
Referring to FIG. 19F, a checksum test of program memory is performed during program step 310, the liquid crystal display 57 is tested during program step 312 and the RS-232 and RS-422 interfaces are tested during program step 314. During program step 316 a check is made to determine if there is an active data terminal 66 ready and switch 49 is activated to the SKIP position If the answer is "yes" the program.c module is entered which allows reprogramming of rapid reprogramming terminal 20. If the answer is "no" the software of Appendix A tests the MS-1553 interface and the IEEE-488 interface (program step 320). The software of Appendix A then enters the rrt.sub.-- main.c module.
Referring to FIG. 19G, during program step 326 the current version of the software of Appendix A is displayed to the user. During program step 328, there is a test to determine if a test connector is attached to rapid reprogramming terminal. If a test connector is attached, a message is displayed to the user indicating that a test connector is attached to rapid reprogramming terminal 20 (program step 346). The user may either move switch 49 to the EXEC position or the SKIP position (program step 348). If the user moves switch 49 to the EXEC position the ext.sub.-- bit.c module is entered and a self test of rapid reprogramming terminal 20 is initiated.
If the user moves switch 49 to the SKIP position rapid reprogramming terminal tests for a +++ via the RS-232 Bus (program step 330) or the RS-422 bus (program step 332). If the +++ is received by rapid reprogramming terminal 20, then software of Appendix A enters the cmdmode.c module. If rapid reprogramming terminal 20 does not receive a +++ memory cards zero and one of IC memory card 22 are tested (program step 336).
The software of Appendix A proceeds to program step 338 where is determined if switch 49 was moved to the EXEC position. If switch 49 was moved to the EXEC position a determination is made as to whether IC memory card 22 is a library card (program step 340) or program card (program step 342). If IC memory card 22 is a library card then the switches.c module is entered (program step 352). If IC memory card 22 is a program card then the program.c module is entered (program step 318). If however IC memory card 22 is neither a library card or a program card than an "erased" or "invalid card" message is provided to the user (program step 344).
Referring to FIGS. 19G, 19H and 19I if rapid reprogramming terminal 20 identifies IC memory card 22 as a program card (program step 342), the program.c module is entered (program step 318) and a "program mode" message is provided to the user (program step 354). If the user enters an abort ("N" or "Esc" from keyboard 62 or SKIP position from switch 49) the software exits the program.c module and returns to the module from which the program.c module was entered. If the user enters an execute ("Y" from keyboard 62 or EXEC position from switch 49) then the boot.c module is moved to the RAM of digital signal processor 21 (program step 362).
After the software of Appendix A enters the boot.c module, a message "loading record" is displayed to the user indicating that a record is being loaded. In addition an Activity Wheel is displayed to the user (program step 364). The boot.c module waits for a Intel Hex-32 format start of record provided via the RS-232 bus or the RS-422 bus or IC memory card 22 (program step 366). The record is next input into digital signal processor 21 (program step 368), followed by a checksum to verify the data in the record is correct (program step 370). If there is an error in the record an error message is displayed to the user (program step 378). If the record is correct, then the data is written in EEPROM 23, read to the digital signal processor 21 for verification and then verified by digital signal processor 21. An end of file record is then provided to digital program processor 21 resulting in the software of Appendix A entering the dspinit.asm module.
Referring to FIG. 19N, when rapid reprogramming terminal receives a +++, the software enters the cmdmode.c module (program step 334). A menu is then provided to the user on screen 69 a menu which provides to the user executable functions with respect to the manipulation of data in memory cards zero and one of IC memory card 22 (program step 462). When the user enters the characters "U" or "A", an upload (U) data to IC memory card 22 or an append (A) data to IC memory card 22 function is activated (program steps 464 and 470). When the user enters the character "D" a download (D) data from IC memory card 22 function is activated (program steps 466 and 472). When the-user enters the characters "C" or "V", a copy (C) data from one memory card to another memory card of IC memory card 22 or a verify (V) the copied data function is activated (program steps 468 and 474). When the user enters the character "E", an erase (E) data from IC memory card 22 function is activated (program steps 478 and 476). Entering the character "P" returns the software of Appendix A to the program.c module. The character "Esc" allows the user to return to the rrt.sub.-- main.c module.
Referring to FIG. 19J, when IC memory card 22 is a library card, indicating that a bus controller 55 or remote terminal 53 is to be reprogrammed, the software of Appendix A enters the switches.c module. During program step 382, the switches.c module determines if a cable is attached to rapid reprogramming terminal 20. If a cable is not attached then the software of Appendix A returns to the rrt.sub.-- main.c module. If a cable is attached then a determination is made as to whether Automode may be entered. Automode allows the automatic sequencing and subsequent transfer of the loadable files on IC memory card 22 to the bus controller 55 or remote terminal 53 being reprogrammed (program step 384). During program step 386 a file and a memory card is selected, the file name is displayed for the user and the user then selects the mode of operation, that the user will select an upload, download or verify operation.
During program step 390, the automode flag is checked. If the automode flag is set then the software of Appendix A proceeds to program step 395. During program step 395 the 1553 multiplex data bus 42 is configured (e.g. short stub or long stub), the bus is selected (avionics or electronics warfare bus) and controller 41 is set as a bus monitoring terminal. If automode is not selected by the user, then the user will process or skip the file by using switch 49. When the user moves switch 49 to the EXEC position the software proceeds to program step 395. When the user moves the switch 49 to the SKIP position the file is not loaded and the software of Appendix A returns to program step 386 selecting the next file for processing.
During program step 398, a determination is made as to whether there is an AN/AYK-14 computer which is active on the selected bus. If, for example, the selected bus is the electronics warfare bus, the software proceeds to program step 402 setting up the AN/ALR-67 Radar Warning Receiver which is the bus controller on the electronic warfare bus. If, for example, the selected bus is avionics bus one on bus 42 and the AYK-14 computer on this bus is active the software proceeds to program step 400. The AYK-14 is next powered off (the PB0 output of interface 54 is set to the logic one state). If the bus is still active, a message is displayed to the user to manually power off the AYK-14 computer. This manual turn off of an AYK-14 is required in certain military aircraft.
During program step 402, rapid reprogramming terminal 20 sets up the bus controller 41 for the protocol to be loaded. During program step 404 discretes MSDRS, RDP and SMS are set. For example, the aircraft memory storage data recording system records all data transfers on the 1553 multiplex data bus 42. When loading a remote terminal 53 or a bus controller 55 it is not required to record the data being loaded. Thus the PB6 output of interface 56 is set to the logic zero state turning off the aircraft memory storage data recording system.
During program step 406, rapid reprogramming terminal 20 determines if an AYK-14 computer is being loaded. If an AYK-14 computer is being loaded then the initiate program load discrete is set active (PB4-PB7 outputs of interface) and the selected AYK-14 computer is powered on. It should be noted that some military aircraft require a manual turn on of the AYK-14 computer and the user is advised of this requirement.
During program step 410, 412 or 414 the software enters the protocol for reprogramming the selected remote terminal 53 or bus controller 55 on the 1553 multiplex data bus 42. After the protocol is executed, a message is displayed and the discretes are cleared (program step 416). Rapid reprogramming terminal 20 next test to determine if another file to be loaded (program step 418). If the answer is "no" the software of Appendix A returns to the rrt.sub.-- main.c module. If the answer is "yes" then the switches.c module is repeated which loads another remote terminal 53 or bus controller 55 on the 1553 multiplex data bus 42.
Referring to FIG. 19K, there is shown the flow chart for the protob.c module which is used for reprogramming a remote terminal 53 when a bus controller reverts to a remote terminal. The program steps of the flow chart for the protoc.c module are identical to the program steps of the flow chart for the protob.c module and thus will not be discussed. Similarly, the program steps of the flow chart for the protod.c and protof.c modules are identical to the program steps of the flow chart for the protob.c module and thus will not be discussed.
The protob.c module is entered from the switches.c module (program step 410) to reprogram a remote terminal 53 on the 1553 multiplex data bus 42. Bus controller 41 was previously set up in control.c which was called by switches.c to function as a bus controller. Rapid reprogramming terminal first reads IC memory card 22 to determine whether an upload, download or verify operation is to be processed (program step 421). If an upload of data to the remote terminal 53 is required, the software of Appendix A proceeds to program step 424, performing an upload of data in the manner illustrated by FIG. 10. If a verify or download of data from the remote terminal is specified the software of Appendix A proceeds to program step 432, performing a verify or download of data.
If there is a simultaneous upload of data (program step 426) the software of Appendix A, the software of Appendix A will point to the next file to be loaded via the 1553 multiplex data bus 42, read IC memory card 22 and then load the file into the remote terminal 53 or bus controller 55 acting as a remote terminal being reprogrammed (program steps 428, 421, 422 and 424).
The software of Appendix A then proceeds to program step 430 to verify the file previously loaded. If there was a simultaneous load, the protob.c module software will verify consecutively each file that was loaded by rapid reprogramming terminal 20. If a file is loaded, followed by a verify then loading of the next file is sequential (program step 438).
When the last file has been loaded the software of rapid reprogramming terminal 20 exits the protob.c module via program step 440 returning to the switches.c module of Appendix A of FIG. 19J.
Referring to FIG. 19L, there is shown the flow chart for the protoe.c module which is used for reprogramming an AYK-14 computer when the AYK-14 computer is a bus controller. The protoe.c module allows for a loading of data, but does not provide for a verify operation. The AYK-14 computer performs the verification by examining the checksum provided by rapid reprogramming terminal 20 and if the checksum comparison is valid the AYK-14 computer assumes a correct load.
After entering the protoe.c module from the switches.c module (program step 412) rapid reprogramming terminal 20 reads the lookup table of IC memory card 22, loads the file and returns to the switches.c module (program steps 442-448). The program steps of the flow chart for the protog.c module are identical to the program steps of the flow chart for the protoe.c module and thus will not be discussed.
Referring to FIG. 19M, there is shown the flow chart for the protoh.c module which is used for reprogramming the High speed Anti-Radiation Missile (HARM) Command Launch Computer. After entering the protoh.c module from the switches.c module (program step 414), rapid reprogramming terminal 20 reads the lookup table of IC memory card 22, loads and then verifies the file and returns to the switches.c module (program steps 450-460).
Referring to FIG. 190, the software of Appendix A enters the upload.c module from the cmdmode.c module (program step 470). During program step 490, a determination is made as to whether an "upload" or "append" is to be processed by rapid reprogramming terminal 20. If an "append" is being processed a message "Append Mode" is displayed to the user and an address offset is setup at the end of the last file (program step 510). If an "upload is being processed a message "Upload Mode" is displayed to the user and the address offset is set to zero since the load from the beginning of IC memory card 22.
During program step 494, a message "Loading Record" is displayed to the user as well as an activity wheel. Rapid reprogramming terminal 20 next looks for a start of record, that is a colon, inputs the record and verifies the checksum (program steps 496, 498 and 500). If the record has errors, an error message is displayed to the user and the user must then respond with an "R" entered via keyboard 62 (program steps 500, 506 and 508).
If the checksum is correct then rapid reprogramming terminal 20 writes the data into IC memory card 22, determines whether the record is written and verified and if the answer is "yes" proceeds to look for the end of file record (program steps 500, 502, 504 and 505). When rapid reprogramming terminal 20 receives the end of file record 505, the software of Appendix exits the upload.c module and returns to the cmdmode.c module (program step 512).
Referring to FIG. 19P, the software of Appendix A enters the download.c module from the cmdmode.c module (program step 472). During program step 514, a message "Download Mode" is displayed to the user. During program step 516, a determination is made as to whether a download of data or a download of a file is to be processed by rapid reprogramming terminal 20. The user then responds via keyboard 62 indicating whether rapid reprogramming terminal 20 is to download data or a file. If the user enters an "A" then the software of Appendix A proceeds to program step 520. During program step 520, the user is asked address and size of the data block that rapid reprogramming terminal 20 is to download. If the user enters an "F" then the software of Appendix A proceeds to program step 518 displaying a file name so that the user may select the file he wants to download. The location and size of the selected file is then extracted by the software of Appendix A.
Rapid reprogramming terminal 20 next sends to data terminal 66 an ASCII colon (start of record), the data amount, address and record type (program step 526). Rapid reprogramming terminal 20 then retrieves the data from IC memory card 22, converts the data to ASCII data and sends the data to data terminal 66 (program step 528). Rapid reprogramming terminal 20 next calculates and sends the ASCII checksum to data terminal 66 (program step 530). This is followed by the end of file record (program step 524) and a return to the cmdmode.c module (program step 532).
Referring to FIG. 19Q, the software of Appendix A enters the copy.c module from the cmdmode.c module (program step 474). During program step 474, rapid reprogramming terminal 20 determines if a memory card copy or verify is to be processed. A "C" entered by the user via keyboard 62 results in a copy of data from one memory card to the other memory card of IC memory card 22. A "V" entered by the user via keyboard 62 results in a verify.
If a copy is selected, then a message "Copy Mode" is displayed to the user (program step 536), the user specifies the source card of IC memory card 22 (program step 538) and the memory card data is copied from the source card to the target card of IC memory card 22 (program step 540).
If a verify is selected, then a message "Verify Mode" is displayed to the user (program step 542, the user specifies the source card of IC memory card 22 (program step 544) and the data on the target card is compared with the source card data (program step 546). If the data on the target card is verified as being identical to the data on the source card than the user will be provided with a data verified message (program step 548). If an error occurs then an error message is provided to the user (program step 550). The software of Appendix A next returns to the cmdmode.c module (program step 554).
Referring to FIG. 19S, the software of Appendix A enters the erase.c module from the cmdmode.c module (program step 476). During program step 556, a message "Erase Mode" is displayed to the user, followed by a warning message (program steps 556 and 557). If the user decides to continue after the warning message, the user is asked which card of IC memory card 22 is to be erased (program steps 560 and 562). During program step 564 the user is again ask whether he wants to continue. If the answer is yes the selected card is erased (program step 577). The software of Appendix A next returns to the cmdmode.c module (program step 577).
In the best mode presently contemplated for the present invention, the program listings for the software modules of Table III are attached hereto and set forth as Appendix A. The Appendix A program listings are written in the C program language, a common, very popular and often used programming language.
From the foregoing description, it may readily be seen that the subject invention comprises a new, unique and exceedingly useful terminal for reprogramming the avionics and electronic warfare systems aboard an aircraft which constitutes a considerable improvement over the known prior art. Obviously many modifications and variations of the present invention are possible in light of the above teachings. It is, therefore, to be understood that within the scope of the appended claims, that the invention may be practiced otherwise than as specifically described. ##SPC1##

Number	Name	Date
4777595	Strecker et al.	Oct 1988
4805137	Grant et al.	Feb 1989
4821180	Gerety et al.	Apr 1989
4937777	Flood et al.	Jun 1990
4945473	Holtey et al.	Jul 1990
5048771	Siering	Sep 1991

Rapid reprogramming terminal

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

US Classifications

Field of Search

US

International Classifications

Abstract

Description

Claims

Parent Case Info

US Referenced Citations (6)

Continuation in Parts (1)