An embedded device software upgrade apparatus

Abstract

The utility model belongs to the field of aviation electromechanical technology relates to a kind of embedded device software upgrading device. Including microprocessor module, storage module, ethernet interface, ARINC429 communication interface, CAN communication interface, RS422 communication interface, RS232 interface, 1553B communication interface, watchdog module, RTC clock module, microprocessor module is the core of this upgrading device, and crosslinking with all remaining modules, the storage module is crosslinked with microprocessor module by parallel interface or SPI interface, and the relevant data and target code in software upgrading process are stored;The maintenance and upgrading operation of the software upgrading information are stripped in this upgrading device, and the equipment to be upgraded is actively upgraded and automatically completed throughout, supports the equipment to be upgraded to carry out data interaction with upgrading device by single point or network mode, and upgrading operation and maintenance are convenient, easy to large-scale application and extension.

Description

Technical Field

[0001] This utility model belongs to the field of aviation electromechanical technology and relates to an embedded device software upgrade device. Background Technology

[0002] As the complexity of aircraft electromechanical equipment increases, the complexity of airborne equipment software also grows. During the delivery and use of this equipment, the need for software upgrades (embedded software) is frequent, and even during the manufacturing process, there is a need for frequent software iterations. Current solutions primarily involve using maintenance computers to perform single-point or multi-point operational upgrades and maintenance. While this method can meet the software upgrade requirements, it has several problems, specifically as follows:

[0003] 1) Because it is necessary to upgrade the software of electromechanical equipment through maintenance computers, the work can only be carried out in a fixed location, which causes many inconveniences in the actual maintenance process;

[0004] 2) Existing upgrade methods require active maintenance of computers, which is inefficient, especially when facing large-scale equipment software upgrade needs, resulting in a large workload.

[0005] 3) Existing maintenance methods typically only configure interfaces for specific devices during the software upgrade and maintenance of electromechanical equipment. There is a lack of universal interfaces that can be used for upgrades across multiple devices, which often requires the use of specific maintenance computers for specific devices in actual use. Utility Model Content

[0006] Utility Model Purpose

[0007] The embedded device software upgrade device proposed in this utility model can effectively solve the problems existing in the current maintenance process.

[0008] This invention provides an embedded device software upgrade device. This device supports one or more device interfaces such as Ethernet, RS422, CAN, and ARINC429. Each interface can provide upgrades to the device to be upgraded via a single point or network. The device supports a web server, allowing a maintenance computer to access the device via the Ethernet interface for data upload and download. The embedded software device to be upgraded communicates with the upgrade device actively to obtain the upgrade method and the target program file to be upgraded, and completes the software upgrade. The upgrade device records upgrade information for all devices, facilitating future maintenance. This upgrade device separates software upgrade information maintenance from the upgrade operation itself. The device to be upgraded actively upgrades and completes the entire process automatically. It supports data interaction between the device to be upgraded and the upgrade device via a single point or network. The upgrade operation and maintenance are convenient, and it is easy to apply and expand on a large scale.

[0009] Technical solution

[0010] An embedded device software upgrade device includes a microprocessor module, a storage module, an Ethernet interface, an ARINC429 communication interface, a CAN communication interface, an RS422 communication interface, an RS232 interface, a 1553B communication interface, a watchdog module, and an RTC clock module. The microprocessor module is the core of this upgrade device and is interconnected with all other modules (or interfaces). The storage module is interconnected with the microprocessor module via a parallel interface or an SPI interface to store relevant data and target code during the software upgrade process. The Ethernet interface is interconnected with the microprocessor via an internal bus or a parallel bus for data interaction with the device to be upgraded or a maintenance host computer. The ARINC429 communication interface is interconnected with the microprocessor module via a parallel bus or an SPI interface for data interaction with the device to be upgraded. The CAN communication interface is interconnected with the microprocessor module via an internal bus or a parallel bus for data interaction with the device to be upgraded. The upgrade device is interconnected with the microprocessor module via a parallel bus or SPI interface for data interaction; the RS422 communication interface is interconnected with the microprocessor module via the microprocessor's internal bus or parallel bus for data interaction; the RS232 communication interface is interconnected with the microprocessor module via the microprocessor's internal bus or parallel bus for data interaction; the 1553B communication interface is interconnected with the microprocessor module via a parallel interface for data interaction; the watchdog module is interconnected with the microprocessor module's reset pin to monitor whether the upgrade device malfunctions, and resets the upgrade device when malfunctions occur; the RTC clock module is interconnected with the microprocessor module via an SPI interface or IIC interface to provide real-time clock information for the upgrade device.

[0011] Furthermore, an embedded device software upgrade device consists of a microprocessor module, a storage module, an Ethernet interface, an ARINC429 communication interface, a CAN communication interface, an RS422 communication interface, an RS232 communication interface, a 1553B communication interface, a watchdog module, and an RTC clock module.

[0012] Furthermore, the microprocessor module can be any one of ARM, DSP or PPC microprocessors;

[0013] Furthermore, the storage module consists of one or more FLASH storage chips;

[0014] Furthermore, the upgrade device includes one or more Ethernet interfaces, and the maintenance computer can interact with the upgrade device via the Ethernet interface in a single point or network manner, while the device to be upgraded can interact with the upgrade device via the network.

[0015] Furthermore, the upgrade device includes one or more ARINC429 communication interfaces to interact with the device to be upgraded.

[0016] Furthermore, the upgrade device includes one or more CAN communication interfaces to interact with the device to be upgraded via a network.

[0017] Furthermore, the upgrade device includes one or more RS422 communication interfaces to interact with the device to be upgraded via point-to-point communication.

[0018] Furthermore, the upgrade device includes one or more RS232 interfaces to interact with the device to be upgraded, and interacts with the device to be upgraded in a single-point communication manner.

[0019] Furthermore, the upgrade device includes one or more 1553B communication interfaces to interact with the device to be upgraded via a network.

[0020] Furthermore, the upgrade device includes a watchdog module to monitor the working status of the upgrade device and reset the upgrade device when an abnormality occurs.

[0021] Furthermore, the upgrade device includes a 1-channel RTC clock module to provide real-time clock information for the upgrade device.

[0022] The beneficial effects of this application are as follows:

[0023] To address the problems of limited maintenance computer interfaces, inconvenient fixed locations, and low efficiency due to the need for manual operation in current embedded software upgrade and maintenance processes, this utility model offers the following beneficial technical effects:

[0024] 1) The embedded software upgrade device described in this utility model is not targeted at any specific device, but has a rich set of upgrade interfaces that can basically cover the upgrade interface needs of common mainstream embedded devices.

[0025] 2) The embedded software upgrade device of this utility model has a built-in database that can cache data of multiple software versions of various devices;

[0026] 3) The embedded software upgrade device of this utility model can complete software upgrades without the intervention of a maintenance computer and supports portability;

[0027] 4) The embedded software upgrade device of this utility model supports batch upgrades for single or multiple different devices simultaneously, either at a single point or in a network.

[0028] 5) The embedded software upgrade device of this utility model supports the legality detection of the access of the device to be upgraded.

[0029] The embedded software upgrade device described in this utility model can meet the upgrade needs of most scenarios and has good application value. Attached Figure Description

[0030] Figure 1 : A schematic diagram of the device structure described in this utility model. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this utility model clearer, the technical solutions in the embodiments of this utility model will be described in more detail below with reference to the embodiments of this utility model. In the examples, the same or similar reference numerals denote the same or similar components or elements having the same or similar functions throughout. The described embodiments are some, but not all, embodiments of this utility model. The embodiments described below with reference to the embodiments are exemplary and intended to explain this utility model, and should not be construed as limiting this utility model. All other embodiments obtained by those skilled in the art based on the embodiments of this utility model without creative effort are within the scope of protection of this utility model. The embodiments of this utility model will be described in detail below with reference to their specific implementation.

[0032] This utility model proposes an embedded device software upgrade device. The device comprises a microprocessor module, a storage module, an Ethernet interface, an ARINC429 communication interface, a CAN communication interface, an RS422 communication interface, an RS232 interface, a 1553B communication interface, a watchdog module, and an RTC clock module. The microprocessor module is the core of this upgrade device, interconnected with all other modules (or interfaces). The storage module is interconnected with the microprocessor module via a parallel interface or an SPI interface to store relevant data and target code during the software upgrade process. The Ethernet interface is interconnected with the microprocessor via an internal bus or a parallel bus for data interaction with the device to be upgraded or a maintenance host computer. The ARINC429 communication interface is interconnected with the microprocessor module via a parallel bus or an SPI interface for data interaction with the device to be upgraded. The CAN... The communication interface is interconnected with the microprocessor module via a parallel bus or SPI interface for data interaction with the device to be upgraded; the RS422 communication interface is interconnected with the microprocessor module via an internal bus or parallel bus for data interaction with the device to be upgraded; the RS232 communication interface is interconnected with the microprocessor module via an internal bus or parallel bus for data interaction with the device to be upgraded; the 1553B communication interface is interconnected with the microprocessor module via a parallel interface for data interaction with the device to be upgraded; the watchdog module is interconnected with the reset pin of the microprocessor module to monitor whether the upgrade device is abnormal, and performs a reset operation on the upgrade device when abnormalities such as driver errors occur; the RTC clock module is interconnected with the microprocessor module via an SPI interface or an IIC interface to provide real-time clock information for the upgrade device.

[0033] In one possible example, an embedded device software upgrade device consists of a microprocessor module, a storage module, an Ethernet interface, an ARINC429 communication interface, a CAN communication interface, an RS422 communication interface, an RS232 communication interface, a 1553B communication interface, a watchdog module, and an RTC clock module.

[0034] In one possible instance, the microprocessor module can be any of an ARM, DSP, or PPC microprocessor;

[0035] In one possible instance, the storage module consists of one or more FLASH memory chips;

[0036] In one possible instance, the upgrade device includes one or more Ethernet interfaces, through which the maintenance computer can interact with the upgrade device via a single point or network, and the device to be upgraded can interact with the upgrade device via a network.

[0037] In one possible instance, the upgrade device includes one or more ARINC429 communication interfaces to interact with the device to be upgraded.

[0038] In one possible instance, the upgrade device includes one or more CAN communication interfaces to interact with the device to be upgraded via a network.

[0039] In one possible instance, the upgrade device includes one or more RS422 communication interfaces to interact with the device to be upgraded via point-to-point communication.

[0040] In one possible instance, the upgrade device includes one or more RS232 interfaces to interact with the device to be upgraded, and interacts with the device to be upgraded in a single-point communication manner.

[0041] In one possible instance, the upgrade device includes one or more 1553B communication interfaces to interact with the device to be upgraded via a network.

[0042] In one possible instance, the upgrade device includes a watchdog module for monitoring the operating status of the upgrade device and resetting the upgrade device when an abnormality occurs.

[0043] In one possible instance, the upgrade device includes a 1-channel RTC clock module to provide real-time clock information for the upgrade device.

[0044] Implementation example:

[0045] The specific implementation steps of an embedded device software upgrade device are as follows:

[0046] Step 1: The embedded device software upgrade device integrates a WEB server. The maintenance computer accesses the upgrade device through an Ethernet interface and sets the upgrade password for the device to be upgraded.

[0047] Step 2: The maintenance computer accesses the upgrade device via the Ethernet interface and adds the new software to the upgrade device's internal program database, including the program version and CRC code.

[0048] Step 3: The maintenance computer accesses the upgrade device via the Ethernet interface, adds the upgrade task, and specifies the software version to be upgraded, CRC code value, and device number that is allowed to be upgraded in the task.

[0049] Step 4: If the device to be upgraded supports an Ethernet communication interface, connect it to the upgrade device's Ethernet communication interface via a single point or network. If the device to be upgraded supports a CAN communication interface, connect it to the upgrade device's CAN communication interface via a single point or network. If the device to be upgraded supports an ARINC429 communication interface, connect it to the upgrade device's ARINC429 communication interface via a single point. If the device to be upgraded supports an RS422 communication interface, connect it to the upgrade device's RS422 communication interface via a single point. If the device to be upgraded supports an RS232 communication interface, connect it to the upgrade device's RS232 communication interface via a single point. If the device to be upgraded supports a 1553B communication interface, connect it to the upgrade device via a 1553B communication network.

[0050] Step 5: After the upgrade device and the upgrade unit are connected, actively upload the upgrade password and verify the upgrade. If the upgrade password is recognized, the upgrade process of this upgrade device is completed.

[0051] Step Six: After the device to be upgraded is authenticated by the upgrade device using the upgrade password, it actively sends the current device software version number, CRC code value, and device number to the upgrade device.

[0052] Step 7: When the upgrade device receives the upgrade request information of the device to be upgraded, it first checks the legality of the information of the device to be upgraded, and confirms whether the current device number, software version and CRC record are valid. If the information of the device to be upgraded is invalid, the upgrade request of the device is rejected and the information is recorded in the upgrade record.

[0053] Step 8: The information of the device to be upgraded is uploaded to the upgrade device. After passing the legality check of the upgrade device, the upgrade device searches the upgrade task list to see if there is a software upgrade task for the device with the corresponding device number. If not, the software upgrade request for the device is rejected.

[0054] Step 9: When there is a software upgrade task for the currently requesting device in the upgrade task list, the upgrade device requests the CRC code values ​​of each memory sector of the device to be upgraded. After receiving the CRC code values ​​of each memory sector returned by the device to be upgraded, the upgrade sector to be upgraded is confirmed, and the corresponding sector is selected for program data update.

[0055] Step 10: After receiving the upgrade data returned by the upgrade device, the upgrade device completes the program data update for the corresponding sector;

[0056] Step 11: After the upgrade device completes the update of all sector program data, it requests the program CRC code value of the device to be upgraded. After receiving the program CRC code value returned by the device to be upgraded, it compares it with the software version and CRC code value in the program library of the upgrade device. If they match, the software upgrade of the device is considered successful. If they do not match, the software upgrade of the device is considered to have failed. The upgrade device records the upgrade information to the storage device, and the software upgrade of the device ends.

[0057] Step 12: This upgrade device supports multiple devices to be upgraded simultaneously. When one device is being upgraded, the other devices can be added to the software upgrade network simultaneously by referring to Step 4.

[0058] Step 13: The maintenance computer downloads the upgrade record information from the upgrade device via the Ethernet interface.

[0059] Furthermore, unless otherwise defined, the technical or scientific terms used in this application description shall have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "upper," "lower," "left," "right," "center," "vertical," "horizontal," "inner," and "outer," etc., used in this application description to indicate relative direction or positional relationship are used only to indicate relative orientation or positional relationship, and do not imply that the device or component must have a specific orientation, or be constructed and operated in a specific orientation. When the absolute position of the described object changes, its relative positional relationship may also change accordingly, and therefore should not be construed as a limitation on this application. The terms "first," "second," "third," and similar terms used in this application description are used only for descriptive purposes to distinguish different components, and should not be construed as indicating or implying relative importance. The terms "a," "one," or "the," etc., used in this application description should not be construed as an absolute limitation on quantity, but should be construed as indicating the existence of at least one. The terms "including," "comprising," etc., used in this application description mean that the element or object preceding the word covers the element or object listed after the word and its equivalents, without excluding other elements or objects.

[0060] Furthermore, it should be noted that, unless otherwise explicitly specified and limited, terms such as “installation,” “connection,” and “linkage” used in the description of this application should be interpreted broadly. For example, a connection can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium; or it can be a connection within two components. Those skilled in the art can understand its specific meaning in this application according to the specific circumstances.

[0061] The above description is merely a specific embodiment of this utility model and is not intended to limit this utility model. Within the spirit and principles of this utility model, any person skilled in the art may use the above-disclosed technical content to make changes or modifications to equivalent embodiments for application in other fields. However, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of this utility model without departing from the technical solution of this utility model, as well as any modifications, equivalent substitutions, improvements, etc., should be included within the protection scope of this utility model.

Claims

1. An embedded device software upgrade device, characterized in that, The system includes a microprocessor module, a storage module, an Ethernet interface, an ARINC429 communication interface, a CAN communication interface, an RS422 communication interface, an RS232 interface, a 1553B communication interface, a watchdog module, and an RTC clock module. The microprocessor module is interconnected with all other modules. The storage module is interconnected with the microprocessor module via a parallel interface or an SPI interface to store relevant data and target code during the software upgrade process. The Ethernet interface is interconnected with the microprocessor via an internal bus or a parallel bus for data interaction with the device to be upgraded or the maintenance host computer. The ARINC429 communication interface is interconnected with the microprocessor module via a parallel bus or an SPI interface for data interaction with the device to be upgraded. The CAN communication interface is interconnected with the microprocessor module via a parallel bus or SPI interface to exchange data with the device to be upgraded; The RS422 communication interface connects to the microprocessor module via the microprocessor's internal bus or parallel bus to exchange data with the device to be upgraded; the RS232 communication interface connects to the microprocessor module via the microprocessor's internal bus or parallel bus to exchange data with the device to be upgraded. The 1553B communication interface is interconnected with the microprocessor module through a parallel interface for data exchange with the device to be upgraded; The watchdog module is interconnected with the microprocessor module's reset pin to monitor whether the upgrade device malfunctions. When an malfunction occurs, the upgrade device is reset. The RTC clock module is interconnected with the microprocessor module via an SPI or IIC interface to provide real-time clock information for the upgrade device.

2. The apparatus as claimed in claim 1, characterized in that, The microprocessor module can be any one of ARM, DSP or PPC microprocessors.

3. The apparatus as described in claim 1, characterized in that, The storage module consists of one or more FLASH storage chips.

4. The apparatus as claimed in claim 1, characterized in that, The upgrade device includes one or more Ethernet interfaces. The maintenance computer can interact with the upgrade device via the Ethernet interface in a single point or network manner, and the device to be upgraded can interact with the upgrade device via the network.

5. The apparatus as claimed in claim 1, characterized in that, The upgrade device includes one or more ARINC429 communication interfaces to interact with the device to be upgraded; the upgrade device also includes one or more CAN communication interfaces to interact with the device to be upgraded via a network.

6. The apparatus as claimed in claim 1, characterized in that, The upgrade device includes one or more RS422 communication interfaces for data interaction with the device to be upgraded via single-point communication; the upgrade device also includes one or more RS232 interfaces for data interaction with the device to be upgraded via single-point communication. The upgrade device includes one or more 1553B communication interfaces to interact with the device to be upgraded via a network.

Images