CN114489831B - Configurable airborne software batch processing and curing method - Google Patents
Configurable airborne software batch processing and curing method Download PDFInfo
- Publication number
- CN114489831B CN114489831B CN202111641473.6A CN202111641473A CN114489831B CN 114489831 B CN114489831 B CN 114489831B CN 202111641473 A CN202111641473 A CN 202111641473A CN 114489831 B CN114489831 B CN 114489831B
- Authority
- CN
- China
- Prior art keywords
- curing
- name
- entering
- file
- configuration table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000001723 curing Methods 0.000 title claims abstract description 64
- 238000003672 processing method Methods 0.000 title description 2
- 238000000034 method Methods 0.000 claims abstract description 10
- 238000007711 solidification Methods 0.000 claims description 22
- 230000008023 solidification Effects 0.000 claims description 22
- 238000012795 verification Methods 0.000 claims description 5
- 238000013461 design Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application belongs to the field of airborne software curing, and relates to a configurable airborne software batch curing method. The method comprises the following steps: determining whether a configuration table exists, determining whether a target product name exists in the configuration table, determining whether a product in the configuration table has a target module name and a target module IP, determining whether a target module has an onboard software file name required to be loaded and a storage address of a file in a host, a file curing address, a configuration item name and a configuration item version, if not, adding the items, and if so, determining whether a loading option of each file meets the requirement, and setting a curing address range meeting the security check; and curing all files to corresponding module addresses in an Ethernet mode according to the curing address. The method and the device can edit and store the configuration items and the target addresses of the curing, flexibly select the configuration items of the onboard software to be cured, and facilitate curing personnel to maintain the curing history and manage the state.
Description
Technical Field
The application belongs to the field of airborne software curing, and particularly relates to a configurable airborne software batch curing method.
Background
In the field of onboard embedded software, a target file usually adopts a curing mode, and a plurality of files with a plurality of configuration items usually need to be cured, and in general, an engineering person is required to manually sequentially cure the plurality of configuration items, so that the curing method is time-consuming and easy to miss or make mistakes, and the previous operation needs to be repeated for the next curing.
Disclosure of Invention
In order to solve the above technical problems, the present application provides a configurable on-board software batch curing method, which mainly includes:
the first step, determining whether a configuration table exists, if so, entering the second step, and if not, entering the eighth step;
step two, determining whether the configuration table has a target product name, and if so, entering a step three; otherwise, entering a fifth step;
thirdly, determining whether a product in the configuration table has a target module name and a target module IP, if so, entering a fourth step, otherwise, entering a sixth step;
determining whether an onboard software file name to be loaded, a storage address of the file in a host, a file curing address, a configuration item name and a configuration item version exist in the target module, if not, entering a seventh step, otherwise, entering a ninth step;
fifthly, adding a target product name into the configuration table;
sixthly, adding a target module name and a target module IP under the target product name;
seventh, editing a configuration item name, a configuration item version, an onboard software file name, a storage address and a solidification address of a file in a host under the name of a target module, and entering a ninth step;
eighth, designing and editing a configuration table of the target product cured at this time, wherein the configuration table at least comprises a software configuration item name to be cured, a software configuration item version, a cured file name contained in the software configuration item, a target module name corresponding to the cured file, a target module IP (Internet protocol) and a target module resident product name, and entering a tenth step;
a ninth step of determining whether the loading options of each file meet the requirements by taking the file to be solidified as an option, if not, entering a tenth step, and if so, entering an eleventh step;
tenth, selecting files to be loaded, and canceling files not to be loaded;
eleventh, determining whether a curing address range conforming to the security check is set, if so, entering a thirteenth step, otherwise, entering a twelfth step;
a twelfth step of setting a curing address range conforming to the security check;
thirteenth, checking whether all addresses to be cured are safe, if the file curing addresses are not in the safe curing address range, entering a fourteenth step; if the address range is within the safe curing address range, a fifteenth step is entered;
fourteenth, giving files with curing addresses not in the verification range, and entering an eleventh step;
fifteenth, giving a check pass, sixteenth;
sixteenth, selecting to start curing, curing all files to corresponding module addresses in an Ethernet mode according to the curing address, and entering seventeenth after curing is completed;
seventeenth, recording the curing time and the configuration table information of the current curing as the history state of the current curing.
Preferably, in the fifth step, when a product name is added to the configuration table, the product name is expressed in a specific letter.
Preferably, in the eighth step, the data in the configuration table of the target product is stored in a tree-like manner.
Preferably, in the first step, the name of the target product stored in the configuration table by default is data in the configuration table information of the last curing.
Preferably, in the second step, the default stored destination module name and destination module IP in the configuration table are data in the configuration table with the destination product name that is cured last time.
Preferably, in the third step, the default stored onboard software file name in the configuration table, the storage address of the file in the host, the file curing address, the configuration item name and the configuration item version are all data in the configuration table with the target module name cured last time.
According to the method, the configuration items and the target addresses of the solidification can be edited and stored, the airborne software configuration items needing to be solidified can be flexibly selected, the solidification history log can be reserved, whether the solidification configuration information is normal or not can be checked, verification prompts can be given out when needed, the design of the man-machine operation method is convenient and quick, solidification efficiency is improved, solidification accuracy is guaranteed, unpredictable consequences caused by solidification errors are avoided, solidification history is recorded, and solidification history maintenance and state management are facilitated for solidification personnel.
Drawings
FIG. 1 is a flow chart of a configurable on-board software batch curing method in accordance with a preferred embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the following describes the technical solutions in the embodiments of the present application in more detail with reference to the drawings in the embodiments of the present application. In the drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are some, but not all, of the embodiments of the present application. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present application and are not to be construed as limiting the present application. All other embodiments, based on the embodiments herein, which would be apparent to one of ordinary skill in the art without undue burden are within the scope of the present application. Embodiments of the present application will be described in detail below with reference to the accompanying drawings.
The application provides a configurable on-board software batch curing method, as shown in fig. 1, mainly comprising the following steps:
the first step, determining whether a configuration table exists, if so, entering the second step, and if not, entering the eighth step.
The configuration table is shown in table 1.
Step two, determining whether the configuration table has a target product name, and if so, entering a step three; otherwise, the fifth step is entered.
Third, determining whether the product in the configuration table has the target module name and the target module IP, if so, entering a fourth step, otherwise, entering a sixth step.
And step four, determining whether the target module has the file name of the on-board software to be loaded and the storage address of the file in the host, the file curing address, the name of the configuration item and the version of the configuration item, if not, entering the seventh step, otherwise, entering the ninth step.
And fifthly, adding the name of the target product in the configuration table.
And sixthly, adding the name of the target module and the IP of the target module under the name of the target product.
And seventh, editing the configuration item name, the configuration item version, the onboard software file name, the storage address and the solidification address of the file in the host machine under the name of the target module, and entering a ninth step.
Eighth, designing and editing a configuration table of the target product cured at this time, wherein the configuration table at least comprises the names of the software configuration items to be cured, the versions of the software configuration items, the names of the cured files contained in the software configuration items, the names of the target modules corresponding to the cured files, the IP of the target modules and the names of the resident products of the target modules, and entering a tenth step.
And ninth, taking the files to be solidified as options, determining whether the loading options of each file meet the requirements, if not, entering the tenth step, and if so, entering the eleventh step.
And tenth, selecting files to be loaded, and canceling files not to be loaded.
Eleventh, determining whether a curing address range conforming to the security check is set, if so, entering a thirteenth step, otherwise, entering a twelfth step.
And twelfth, setting a curing address range conforming to the security check.
Thirteenth, checking whether all addresses to be cured are safe, if the file curing addresses are not in the safe curing address range, entering a fourteenth step; if within the secure cure address range, a fifteenth step is entered.
And fourteenth step, giving the file with the solidification address not in the verification range, and entering the eleventh step.
Fifteenth, a check is given, sixteenth.
Sixteenth, selecting to start curing, curing all files to corresponding module addresses in an Ethernet mode according to the curing address, and entering seventeenth after curing is completed.
Seventeenth, recording the curing time and the configuration table information of the current curing as the history state of the current curing.
In some alternative embodiments, in the fifth step, when a product name is added to the configuration table, the product name is expressed in a specific letter.
In some alternative embodiments, in the eighth step, the data in the configuration table of the target product is stored in a tree-like manner.
In some alternative embodiments, in the first step, the default stored target product name in the configuration table is the data in the configuration table information of the last curing.
In some optional embodiments, in the second step, the default stored destination module name and destination module IP in the configuration table are data in the configuration table with the destination product name that is cured last time.
In some optional embodiments, in the third step, the default stored onboard software file name in the configuration table and the storage address of the file in the host, the file curing address, the configuration item name, and the configuration item version are all data in the configuration table with the target module name that is cured last time.
According to the method, the configuration items and the target addresses of the solidification can be edited and stored, the airborne software configuration items needing to be solidified can be flexibly selected, the solidification history log can be reserved, whether the solidification configuration information is normal or not can be checked, verification prompts can be given out when needed, the design of the man-machine operation method is convenient and quick, solidification efficiency is improved, solidification accuracy is guaranteed, unpredictable consequences caused by solidification errors are avoided, solidification history is recorded, and solidification history maintenance and state management are facilitated for solidification personnel.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions easily conceivable by those skilled in the art within the technical scope of the present application should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (6)
1. A configurable on-board software batch curing method, comprising:
the first step, determining whether a configuration table exists, if so, entering the second step, and if not, entering the eighth step;
step two, determining whether the configuration table has a target product name, and if so, entering a step three; otherwise, entering a fifth step;
thirdly, determining whether a product in the configuration table has a target module name and a target module IP, if so, entering a fourth step, otherwise, entering a sixth step;
determining whether an onboard software file name to be loaded, a storage address of the file in a host, a file curing address, a configuration item name and a configuration item version exist in the target module, if not, entering a seventh step, otherwise, entering a ninth step;
fifthly, adding a target product name into the configuration table;
sixthly, adding a target module name and a target module IP under the target product name;
seventh, editing a configuration item name, a configuration item version, an onboard software file name, a storage address and a solidification address of a file in a host under the name of a target module, and entering a ninth step;
eighth, designing and editing a configuration table of the target product cured at this time, wherein the configuration table at least comprises a software configuration item name to be cured, a software configuration item version, a cured file name contained in the software configuration item, a target module name corresponding to the cured file, a target module IP (Internet protocol) and a target module resident product name, and entering a tenth step;
a ninth step of determining whether the loading options of each file meet the requirements by taking the file to be solidified as an option, if not, entering a tenth step, and if so, entering an eleventh step;
tenth, selecting files to be loaded, and canceling files not to be loaded;
eleventh, determining whether a curing address range conforming to the security check is set, if so, entering a thirteenth step, otherwise, entering a twelfth step;
a twelfth step of setting a curing address range conforming to the security check;
thirteenth, checking whether all addresses to be cured are safe, if the file curing addresses are not in the safe curing address range, entering a fourteenth step; if the address range is within the safe curing address range, a fifteenth step is entered;
fourteenth, giving files with curing addresses not in the verification range, and entering an eleventh step;
fifteenth, giving a check pass, sixteenth;
sixteenth, selecting to start curing, curing all files to corresponding module addresses in an Ethernet mode according to the curing address, and entering seventeenth after curing is completed;
seventeenth, recording the curing time and the configuration table information of the current curing as the history state of the current curing.
2. The configurable on-board software batch curing method of claim 1, wherein in a fifth step, when a product name is added to the configuration table, the product name is expressed in a specific letter.
3. The method of claim 1, wherein in the eighth step, the data in the configuration table of the target product is stored in a tree-like manner.
4. The method of claim 1, wherein in the first step, the default stored target product name in the configuration table is the data in the last-cured configuration table information.
5. The method of claim 1, wherein in the second step, the default stored destination module name and destination module IP in the configuration table are data in the configuration table with the destination product name that was last cured.
6. The method of claim 1, wherein in the third step, the default stored onboard software file name in the configuration table and the storage address of the file in the host, the file curing address, the configuration item name, and the configuration item version are all data in the configuration table with the target module name that was last cured.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111641473.6A CN114489831B (en) | 2021-12-29 | 2021-12-29 | Configurable airborne software batch processing and curing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111641473.6A CN114489831B (en) | 2021-12-29 | 2021-12-29 | Configurable airborne software batch processing and curing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114489831A CN114489831A (en) | 2022-05-13 |
| CN114489831B true CN114489831B (en) | 2024-03-19 |
Family
ID=81497104
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111641473.6A Active CN114489831B (en) | 2021-12-29 | 2021-12-29 | Configurable airborne software batch processing and curing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114489831B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902303A (en) * | 2012-12-26 | 2014-07-02 | 中国航空工业集团公司第六三一研究所 | Program solidifying method based on configuration table |
| WO2018121026A1 (en) * | 2016-12-26 | 2018-07-05 | 深圳创维数字技术有限公司 | Method and system for configuring set-top box |
| CN111694576A (en) * | 2020-05-22 | 2020-09-22 | 中国航空工业集团公司西安航空计算技术研究所 | Software deployment control method for integrated avionics system |
| CN112214415A (en) * | 2020-11-03 | 2021-01-12 | 中国航空工业集团公司西安航空计算技术研究所 | Trusted management method for executable files of airborne embedded system |
-
2021
- 2021-12-29 CN CN202111641473.6A patent/CN114489831B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902303A (en) * | 2012-12-26 | 2014-07-02 | 中国航空工业集团公司第六三一研究所 | Program solidifying method based on configuration table |
| WO2018121026A1 (en) * | 2016-12-26 | 2018-07-05 | 深圳创维数字技术有限公司 | Method and system for configuring set-top box |
| CN111694576A (en) * | 2020-05-22 | 2020-09-22 | 中国航空工业集团公司西安航空计算技术研究所 | Software deployment control method for integrated avionics system |
| CN112214415A (en) * | 2020-11-03 | 2021-01-12 | 中国航空工业集团公司西安航空计算技术研究所 | Trusted management method for executable files of airborne embedded system |
Non-Patent Citations (1)
| Title |
|---|
| 一种基于文件的嵌入式星载软件在轨升级方法;韦涌泉;董振辉;张红军;;单片机与嵌入式系统应用;20180501(第05期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114489831A (en) | 2022-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI570324B (en) | Method for configuring a wind energy installation, and wind energy installation | |
| CN103425551B (en) | Management method in database distributed backup set | |
| CN107203658B (en) | Ship system schematic diagram rapid design method based on CAD and PDM | |
| US20050165653A1 (en) | Method of manufacturing an item of build-to-order equipment | |
| CN104915262A (en) | Calibration system and method based on EXCEL data structure | |
| CN106301886A (en) | A kind of user operation auditing method and device | |
| US20140379649A1 (en) | Distributed storage system and file synchronization method | |
| CN114489831B (en) | Configurable airborne software batch processing and curing method | |
| CN102156744A (en) | Method for eliminating repetition of memory dialog list | |
| CN102622243A (en) | Method for executing solidified codes supporting various NAND flash memories | |
| JP6450865B2 (en) | Aggregate large amounts of time data from many overlapping sources | |
| US20150156340A1 (en) | Information processing system, information processing apparatus, and program | |
| CN111694576B (en) | Comprehensive avionics system software deployment control method | |
| CN111767533A (en) | Offline mode user authorization method, device, electronic device and storage medium | |
| CN102623066A (en) | Saving and acquisition method for solidification code parameter table | |
| CN103235988B (en) | The method of work of data base's integration supervising platform | |
| CN105183854A (en) | Scheduling method applicable to data unloading of database | |
| US20160124677A1 (en) | Optical cold storage | |
| CN111125743A (en) | Authority management method, system, computer device and computer readable storage medium | |
| CN106445837B (en) | Embedded device history record storage and loading management implementation method and device | |
| CN114860690A (en) | Data migration method, device, equipment and storage medium | |
| CN103870594A (en) | Method and device for managing and calibrating long-distance engineering project digital photos | |
| CN114528108A (en) | Serial number generation method, device, server and storage medium | |
| JP4836545B2 (en) | Screen creation device and program | |
| US9117059B2 (en) | Methods for administering an autonomous rights component, autonomous rights administration systems and devices carrying out the methods |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |