WO2020107469A1

WO2020107469A1 - Application processing method and apparatus and storage medium

Info

Publication number: WO2020107469A1
Application number: PCT/CN2018/118733
Authority: WO
Inventors: 杨小渊; 薛冰; 邹旭
Original assignee: 深圳市大疆创新科技有限公司
Priority date: 2018-11-30
Filing date: 2018-11-30
Publication date: 2020-06-04
Also published as: CN111356982A

Abstract

Provided in embodiments of the present invention are an application processing method and apparatus and a storage medium. In the embodiment of the present invention, a first application in a storage device of an embedded apparatus is replaced with a second application and a second bootloader in an upgrade firmware. The second application stores a start address of the second bootloader. The second bootloader is acquired according to the start address of the second bootloader, and a first bootloader in the storage device is replaced with the second bootloader, thereby realizing upgrading of an application and a bootloader. The second application comprises a header region. If the size of the second bootloader is greater than the size of the first bootloader, the second bootloader can occupy the header region of the second application, such that the second bootloader does not overwrite an effective executable code of the second application, thereby enabling normal operation of the upgraded second application, and accordingly enabling normal operation of the upgraded embedded apparatus.

Description

Program processing method, device and storage medium

Technical field

The embodiments of the present invention relate to the field of computers, and in particular, to a program processing method, device, and storage medium.

Background technique

With the development of computer technology, embedded systems have been widely used in electronic products, industrial equipment and other fields. In order to facilitate product maintenance, prolong the use of products and expand new product functions, it is necessary to upgrade embedded systems, including specific Bootstrap and application upgrades.

The boot programs and application programs in embedded systems are usually stored in a readable and writable storage device. The size of the current boot program for embedded systems is fixed. However, with the expansion of product functions or the reliability of boot programs, the original The boot program of the software can no longer meet the demand, and the original boot program needs to be expanded.

In the prior art, the application program is usually stored after the boot program. When the size of the new boot program exceeds the size of the original boot program, it will cause the new boot program to overwrite part of the storage area or all the storage occupied by the application program. Area, which causes the application to fail to run properly, and ultimately the embedded device to fail to run normally.

Summary of the invention

Embodiments of the present invention provide a program processing method, device, and storage medium to implement normal upgrade of an application program and a boot program in an embedded device, so as to prevent the boot program from covering the effective execution code of the application program, so that the upgraded application program can be normal Run, so that the upgraded embedded device can run normally.

A first aspect of an embodiment of the present invention is to provide a program processing method, which is applied to an embedded device, and a memory of the embedded device stores a first boot program and a first application program; the method includes:

Obtain firmware to be upgraded, where the firmware to be upgraded includes a second application program and a second boot program;

Replacing the first application program in the memory with the second application program and the second boot program, the second application program storing a start address of the second boot program, the first The start address of the second boot program is at a first preset position after the second application program, and the second application program includes a header area;

Acquiring the start address of the second boot program from the second application program, and acquiring the second boot program from the start address of the second boot program;

The first boot program is replaced with the second boot program, and the sizes of the first boot program and the head region are greater than or equal to the size of the second boot program.

A second aspect of an embodiment of the present invention is to provide a program processing method, which is applied to an embedded device, and a memory of the embedded device stores a first boot program and a first application program; the method includes:

Replacing the first application program in the memory with the second application program and the second boot program, the second application program storing a start address of the second boot program, the first The start address of the second boot program is at a preset position after the second application program;

Comparing the first boot program and the second boot program;

If the first boot program and the second boot program are the same, delete the second boot program after the second application program.

A third aspect of the embodiments of the present invention is to provide an embedded device, including: a memory and a processor;

The memory stores a first boot program and a first application program;

The processor is used to perform the following operations:

A fourth aspect of the embodiments of the present invention is to provide an embedded device, including: a memory and a processor;

The memory stores a first boot program and a first application program;

The processor is used to perform the following operations:

Comparing the first boot program and the second boot program;

When the first boot program and the second boot program are the same, delete the second boot program after the second application program.

A fifth aspect of the embodiments of the present invention is to provide a computer-readable storage medium on which a computer program is stored, which is executed by a processor to implement the method according to the first aspect.

In the program processing method, device and storage medium provided in this embodiment, by replacing the first application program in the memory of the embedded device with the second application program and the second boot program in the firmware to be upgraded, the second application program stores There is a start address of the second boot program, according to the start address of the second boot program, the second boot program is obtained, and the first boot program in the memory is replaced with the second boot program to implement the application program And bootloader upgrade. The second application program includes a head area. When the size of the second boot program is larger than the size of the first boot program, the second boot program may occupy the head area of the second application program to prevent the second boot program from being overwritten. The effective execution code of the second application program makes the upgraded second application program run normally, so that the upgraded embedded device can run normally.

BRIEF DESCRIPTION

In order to more clearly explain the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required in the description of the embodiments. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without paying any creative labor, other drawings can also be obtained based on these drawings.

1 is a schematic diagram of an embedded device and a controller provided by an embodiment of the present invention;

2 is a flowchart of a program processing method provided by an embodiment of the present invention;

3 is a schematic diagram of a memory of an embedded device provided by an embodiment of the present invention;

4 is a schematic diagram of a memory of an embedded device provided by an embodiment of the present invention;

5 is a schematic diagram of a memory of an embedded device provided by an embodiment of the present invention;

6 is a schematic diagram of a memory of an embedded device provided by an embodiment of the present invention;

7 is a schematic diagram of a memory of an embedded device provided by an embodiment of the present invention;

8 is a flowchart of a program processing method according to another embodiment of the present invention;

9 is a flowchart of a program processing method according to another embodiment of the present invention;

10 is a schematic diagram of a memory of an embedded device provided by an embodiment of the present invention;

11 is a schematic diagram of a memory of an embedded device provided by an embodiment of the present invention;

12 is a structural diagram of an embedded device provided by an embodiment of the present invention.

Reference mark:

21: Embedded device; 22: Controller; 31: Firmware to be upgraded;

110: embedded device; 111: memory; 112: processor;

113: Communication interface.

detailed description

The technical solutions in the embodiments of the present invention will be described clearly below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without making creative efforts fall within the protection scope of the present invention.

It should be noted that when a component is said to be "fixed" to another component, it can be directly on another component or it can also exist in a centered component. When a component is considered to be "connected" to another component, it can be directly connected to another component or there can be centered components at the same time.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field of the present invention. The terminology used in the description of the present invention herein is for the purpose of describing specific embodiments, and is not intended to limit the present invention. The term "and/or" as used herein includes any and all combinations of one or more related listed items.

The following describes some embodiments of the present invention in detail with reference to the accompanying drawings. In the case of no conflict, the following embodiments and the features in the embodiments can be combined with each other.

An embodiment of the present invention provides a program processing method. The program processing method is applied to embedded devices. As shown in FIG. 1, the embedded device 21 includes a processor, a memory, and a transceiver. The controller 22 includes a processor, a transceiver, and a network adapter. The controller 22 may specifically be a computer, a tablet computer, or the like.

2 is a flowchart of a program processing method provided by an embodiment of the present invention. As shown in FIG. 2, the method in this embodiment may include:

Step S201: Obtain firmware to be upgraded, where the firmware to be upgraded includes a second application program and a second boot program.

In this embodiment, the memory of the embedded device stores a first boot program and a first application program. The first boot program is recorded as the old boot program of the embedded device, and the first application program is recorded as the old application program of the embedded device. When the embedded device needs to upgrade the old boot program and/or the old boot program, the embedded device obtains firmware to be upgraded, and the firmware to be upgraded may include a new application program and a new boot program, or, The firmware to be upgraded may include only a new application program. Here, the new application program is recorded as the second application program, and the new boot program is recorded as the second boot program.

In this embodiment, the acquiring firmware to be upgraded includes receiving the firmware to be upgraded sent by a controller. As shown in FIG. 1, the controller 22 can communicate with a server through a network adapter, and the server sends the firmware to be upgraded to the controller 22, and the processor of the controller 22 sends the firmware to be upgraded to the embedded through the transceiver of the controller 22 Device 21, the processor of the embedded device 21 receives the firmware to be upgraded through the transceiver of the embedded device 21, and the firmware to be upgraded may specifically be a composite file of a new application program and a new boot program, or, the to-be-upgraded The firmware may specifically be a new application program.

In some embodiments, the controller 22 may not include a network adapter, that is, the controller 22 may generate the firmware to be upgraded, and send the generated firmware to be upgraded to the embedded device 21 through the transceiver.

In some other embodiments, the embedded device 21 may include a network adapter through which the embedded device 21 obtains the firmware to be upgraded from the server without receiving the firmware to be upgraded sent by the controller 22.

Step S202: Replace the first application program in the memory with the second application program and the second boot program, where the second application program stores a start address of the second boot program, The start address of the second boot program is at a first preset position after the second application program, and the second application program includes a header area.

FIG. 3 or FIG. 4 shows the memory of the embedded device 21. The memory of the embedded device 21 currently stores the boot program 1 and the application program 1. Boot program 1 is denoted as the first boot program, application program 1 is denoted as the first application program, the start address of boot program 1 is address A, application program 1 is after boot program 1, and the start address of application program 1 is address B , The program tail of the boot program 1 includes a jump execution code area, and the role of the jump execution code area is to directly jump to the fixed running address of the application program 1, that is, the start address of the application program 1.

As shown in FIG. 3 or FIG. 4, 31 represents the firmware to be upgraded received by the embedded device 21 from the controller 22, and the firmware to be upgraded 31 includes an application program 2 and a boot program 2, where the application program 2 is recorded as the second application Program, boot program 2 is denoted as the second boot program. After the processor of the embedded device 21 receives the firmware to be upgraded sent by the controller 22, the firmware to be upgraded is written into the memory of the embedded device 21. Specifically, the processor of the embedded device 21 transfers the embedded device 21 The application program 1 stored in the memory of is replaced with the firmware to be upgraded, that is, the application program 1 stored in the memory of the embedded device 21 is replaced with the application program 2 and the boot program 2. After the embedded device 21 is powered on again, the processor of the embedded device 21 starts to execute from the start address of the boot program 1, that is, address A, and when it reaches the jump execution code area of the boot program 1, jumps to the application program 2 The starting address is the address B.

As shown in FIG. 3 or FIG. 4, the start address of the boot program 2 is the address E, and the start address of the boot program 2 is a preset position after the tail address of the application 2, and the preset position is recorded as the first preset position. The start address of application 2 and application 1 are the same, both are address B. The start address of the boot program 2, ie, the length of address E relative to address B is y. The difference between application 2 and application 1 is that application 2 includes a header area, and the running address of application 2 is address D, that is, the effective execution code of application 2 starts from address D and starts from application 2 The part from the start address B of the application to the running address D of the application 2 is the header area of the application 2.

In this embodiment, the application program 2 stores the start address of the boot program 2, that is, the address E.

Step S203: Acquire the start address of the second boot program from the second application program, and acquire the second boot program from the start address of the second boot program.

After the processor of the embedded device 21 replaces the application program 1 with the application program 2 and the boot program 2, the start address of the boot program 2 is obtained from the application program 2 as the address E, and from the boot program 2 That is, the address E starts to acquire the boot program 2.

In this embodiment, obtaining the start address of the second boot program from the second application program includes the following feasible implementation manners:

A feasible implementation manner is that: the second application program includes a first area; and the first area stores a start address of the second boot program. The acquiring the start address of the second boot program from the second application includes: acquiring the start address of the second boot program from the first area of the second application.

As shown in FIG. 5, the application program 2 includes a first area, which is referred to as a copy boot program area, and an address E, which is a start address of the boot program 2, is stored in the copy boot program area. When the processor of the embedded device 21 executes from the boot program 1 to the application program 2, it reads the address E, which is the start address of the boot program 2, from the copy boot program area of the application program 2.

Another feasible implementation manner is that: the second application further includes a second area, the second area stores the running address of the second application, and the tail address of the second area is the first The starting address of an area. The acquiring the start address of the second boot program from the second application includes: determining the start address of the first area according to the second area; and according to the start of the first area Start address, the start address of the second boot program is obtained from the first area of the second application program.

As shown in FIG. 5, the application program 2 may further include a second area, which is referred to as a running address storage area, and the starting address of the running address storage area is address C. Optionally, the distance between address C and address B is x. The running address storage area stores an address D which is the running address of the application 2. The copy boot program area is behind the run address storage area. Optionally, the tail address of the run address storage area is the start address of the copy boot program area. When the processor of the embedded device 21 executes from the boot program 1 to the application program 2, the copy boot program area after the run address storage area is determined according to the run address storage area, and from the start address of the copy boot program area, from The start address of the boot program 2 in the copy boot program area is the address E.

Another feasible implementation manner is: the second application further includes a third area, the third area stores a start address of the second area, and the third area is in the second application Within the head area. The acquiring the start address of the second boot program from the second application includes: acquiring the start address of the second area from the third area; starting from the second area Start address, determine the start address of the first area; according to the start address of the first area, obtain the start address of the second boot program from the first area of the second application .

As shown in FIG. 5, the application 2 may further include a third area, which is referred to as a jump execution code area, a jump execution code area in the application 2 and a jump execution code in the boot program 1 described above The difference of the area is that the jump execution code area in the above boot program 1 is for jumping to the start address of the application 2, namely the address B, and the jump execution code area in the application 2 is for jumping to Application program 2 running address storage area or copy boot program area. Optionally, the jump execution code area in the application program 2 stores the start address of the running address storage area of the application program 2. The jump execution code area in the application 2 is in the head area of the application 2. When the processor of the embedded device 21 executes from the boot program 1 to the application program 2, it jumps from the jump execution code area in the application program 2 to the run address storage area, and determines the run address storage area according to the run address storage area Copy the boot program area, and read the start address of the boot program 2, namely the address E, from the copy boot program area according to the start address of the copy boot program area.

Another feasible implementation manner is: the second application program further includes a third area, the third area stores a start address of the first area, and the third area is in the second Within the head area of the application. The acquiring the start address of the second boot program from the second application includes: acquiring the start address of the first area from the third area; according to the start of the first area Start address, the start address of the second boot program is obtained from the first area of the second application program.

As shown in FIG. 5, the jump execution code area in the application 2 stores the start address of the copy boot area of the application 2. When the processor of the embedded device 21 executes from the boot program 1 to the application program 2, the jump execution code area in the application program 2 jumps to the start address of the copy boot program area, and according to the start of the copy boot program area Address, read the address E, which is the start address of the boot program 2, from the copy boot program area.

In some embodiments, the starting address of the third area is the starting address of the head area of the second application. As shown in FIG. 5, the start address of the jump execution code area in the application 2 is the address B which is the start address of the head area of the application 2.

Optionally, after the processor of the embedded device 21 obtains the start address of the boot program 2 as the address E according to any of the above methods, the boot program 2 is acquired from the start address of the boot program 2 as the address E .

In some of these embodiments, the first area further includes the length of the second boot program; the acquiring the second boot program from the start address of the second boot program includes: according to the The length of the second boot program is obtained from the start address of the second boot program. For example, the copy boot program area of the embedded device 21 may store both the start address of the boot program 2 and the length of the boot program 2, when the processor of the embedded device 21 reads the boot program 2 according to any of the above methods After the starting address is address E, the boot program 2 is obtained from the boot address 2 starting address E according to the length of the boot program 2. It can be understood that the processor of the embedded device 21 according to the boot program 2 The starting address is the address E and the length of the boot program 2, and the tail address of the boot program 2 can be determined. The tail address is the position where the processor of the embedded device 21 stops acquiring the boot program 2.

Step S204: Replace the first boot program with the second boot program, and the sizes of the first boot program and the head area are greater than or equal to the size of the second boot program.

After the processor of the embedded device 21 obtains the boot program 2, the original boot program 1 in the memory of the embedded device 21 is replaced with the boot program 2, that is, the boot program 1 is overwritten with the boot program 2.

In this embodiment, the size of the boot program 2 and the boot program 1 may be different, and the size of the boot program 2 may be larger than the boot program 1 or may be smaller than the boot program 1. In this embodiment, the size of the boot program 2 is larger than that of the boot program 1 as an example.

Since the size of the boot program 2 is larger than the size of the boot program 1, when the processor of the embedded device 21 overwrites the boot program 1 with the boot program 2, the boot program 2 will occupy the head area of the application 2, in In this embodiment, the sum of the size of the boot program 1 and the size of the head area of the application 2 is greater than or equal to the size of the boot program 2. As shown in FIG. 5, assuming that the size of the boot program 2 is larger than the size of the boot program 1 by x, after the boot program 2 is overwritten by the boot program 1, the boot program 2 will occupy the size of the head area of the app 2 as x Area. In this embodiment, x is less than or equal to the size of the head area of the application 2, so that the boot program 2 will not overwrite the effective execution code of the application 2, thereby affecting the normal operation of the application 2. For example, if x is smaller than the size of the head area of the application 2, after the boot program 2 is overwritten, the head area of the application 2 becomes smaller, for example, the area from address B to address D becomes It is the area from address C to address D. This embodiment does not limit the relationship between the size of the area from address B to address C and the size of the area from address C to address D.

In some embodiments, the starting address of the first area is the running address of the second application program. The second area is within the head area of the second application. The size of the storage space between the start address of the first boot program and the start address of the second area is greater than or equal to the size of the second boot program.

As shown in FIGS. 5 and 6, the start address of the copy boot program area of the application 2 is the address D which is the running address of the application 2. The running address storage area of the application 2 is in the header area of the application 2. In this case, if the size of the boot program 2 is larger than the size of the boot program 1, the boot program 2 may occupy part of the head area or the entire head area of the application program 2, specifically, the boot program 2 may not occupy the The running address storage area in the header area can also occupy the running address storage area. As shown in FIG. 5, when the boot program 2 does not occupy the running address storage area in the header area, from the start address of the boot program 1 which is address A to the start address of the running address storage area which is address C The size of the storage space must be greater than or equal to the size of the boot program 2. As shown in FIG. 6, when the boot program 2 can occupy the running address storage area in the header area, the storage space from the boot address of the boot program 1 to the address A to the boot address of the boot program 2 is the storage space The size must be greater than or equal to the size of bootloader 2.

In some other embodiments, the starting address of the first area is at a second preset position after the running address of the second application program. The second area is not within the head area of the second application. The size of the storage space between the start address of the first boot program and the running address of the second application program is greater than or equal to the size of the second boot program.

As shown in FIG. 7, the start address of the copy boot program area of the application 2 is a preset position after the address D, which is the running address of the application 2, and the preset position is recorded as the second preset position. Limit the distance from address D to the start address of the copy boot program area. The running address storage area of the application 2 is not in the header area of the application 2. In this case, the size of the storage space from the start address of the boot program 1 (address A) to the running address of the application program 2 (address D) must be greater than or equal to the size of the boot program 2, that is, the boot program 2 The head area of the application 2 can be occupied at most. The maximum value of the size of the boot program 2 is the sum of the size of the boot program 1 and the size of the head area of the application 2.

In some embodiments, the processor replacing the first boot program with the second boot program includes: comparing the first boot program and the second boot program; if the first boot program Unlike the second boot program, the first boot program is replaced with the second boot program. If the first boot program and the second boot program are the same, delete the second boot program after the second application program.

For example, when the processor of the embedded device 21 obtains the start address of the boot program 2 as the address E, the boot program 2 is acquired from the start address of the boot program 2 as the address E, and the boot program 2 and the embedded program are compared. The original boot program 1 in the memory of the device 21, if boot program 1 and boot program 2 are different, replace boot program 1 with boot program 2, if boot program 1 and boot program 2 are the same, delete boot after application program 2 Procedure 2.

In some embodiments, after the first boot program is replaced with the second boot program, the method further includes: deleting the second boot program after the second application program.

For example, boot program 1 and boot program 2 are different. After the processor of embedded device 21 replaces boot program 1 with boot program 2, boot program 2 after application program 2 may be further deleted.

In this embodiment, the size of the head area of the application 2 can be determined according to the sizes of the boot program 1 and the boot program 2, for example, when generating firmware to be upgraded, the application can be determined according to the sizes of the boot program 1 and the boot program 2 The size of the header area of program 2.

In addition, this embodiment is also applicable to the scenario of shrinking the boot program, not just expanding the boot program.

In this embodiment, by replacing the first application program in the memory of the embedded device with the second application program and the second boot program in the firmware to be upgraded, the second application program stores the starting address of the second boot program, according to The starting address of the second boot program is obtained, and the first boot program in the memory is replaced with the second boot program, thereby realizing the upgrade of the application program and the boot program. The second application program includes a head area. When the size of the second boot program is larger than the size of the first boot program, the second boot program may occupy the head area of the second application program to prevent the second boot program from being overwritten. The effective execution code of the second application program makes the upgraded second application program run normally, so that the upgraded embedded device can run normally.

An embodiment of the present invention provides a program processing method. 8 is a flowchart of a program processing method according to another embodiment of the present invention. As shown in FIG. 8, based on the embodiment shown in FIG. 2, after the first boot program is replaced with the second boot program, the method may further include:

Step S701: Starting from the start address of the second boot program, execute the second boot program.

As shown in FIG. 3, after the processor of the embedded device 21 replaces the original boot program 1 in the memory of the embedded device 21 with the boot program 2, if the embedded device 21 does not restart, the processor of the embedded device 21 will Start running application 2. If the embedded device 21 restarts, the processor of the embedded device 21 will execute the boot program 2 from the address A, which is the start address of the boot program 2.

Step S702: When executing the second boot program, obtain the running address of the second application program.

As shown in FIG. 3, the tail of the boot program 2 includes a get run address area and a jump execution code area, where the get run address area is used to get the run address of the application 2 (address D), and the jump execution code of the boot program 2 The area is used to jump directly to address D to start execution. In this embodiment, the jump execution code area is mainly assembly code, which directly changes the running address of the program.

In some embodiments, the second boot program stores the start address of the second area; the acquiring the running address of the second application program when executing the second boot program includes: When the second boot program is executed, the running address of the second application program is obtained from the second area according to the start address of the second area.

For example, the acquisition run address area at the end of the boot program 2 stores the start address of the second area described in the above embodiment, that is, the start address of the run address storage area, since the run address storage area stores the run address of the application 2 Address D, when the processor of the embedded device 21 executes the acquisition operation address area at the end of the boot program 2, it reads the start address of the operation address storage area from the acquisition operation address area, and according to the operation address storage area The starting address is the address D which is the running address of the application 2 is read from the running address storage area.

Step S703: Jump from the second boot program to the running address of the second application program, and execute the second application program.

When the processor of the embedded device 21 executes the jump execution code area at the end of the boot program 2, it jumps directly to the address D of the application program 2 to start execution of the application program 2. Optionally, the acquisition run address area at the end of the boot program 2 only needs to acquire the run address of the application program 2 before the processor of the embedded device 21 executes the jump execution code area at the tail of the boot program 2.

The jumping from the second boot program to the running address of the second application program, and executing the second application program includes: jumping from the second boot program to the running of the second application program Address, execute the second application program, and delete the second boot program after the second application program.

For example, since the application program 2 stores the start address of the boot program 2 as the address E, when the processor of the embedded device 21 executes the application program 2, the processor of the embedded device 21 may also delete the address according to the address E Bootloader 2 after application 2.

In this embodiment, the first boot program is replaced with a second boot program with a larger capacity, so that the boot program is repaired, replaced, and expanded. Starting from the start address of the second boot program, execute the second boot program, and when executing the second boot program, directly obtain the running address of the second application program, and jump directly from the second boot program to the The running address of the second application program is the starting address of the effective execution code, and executing the second application program improves the execution efficiency of the upgraded second application program.

An embodiment of the present invention provides a program processing method. The method is applied to an embedded device, and a memory of the embedded device stores a first boot program and a first application program. 9 is a flowchart of a program processing method according to another embodiment of the present invention. As shown in FIG. 9, the method may include:

Step S801: Obtain firmware to be upgraded, where the firmware to be upgraded includes a second application program and a second boot program.

As shown in FIG. 10, the memory of the embedded device 21 stores a first boot program and a first application program, the first boot program is specifically the boot program 2 in the above embodiment, and the first application program is specifically in the above embodiment的应用2。 Application 2. The address D represents the running address of the application program 2, that is, the starting address of the effective execution code of the application program 2. The storage space between the address C and the address D may be a partial header area remaining after the boot program 2 occupies a partial header area of the application 2.

Step S802: Replace the first application program in the memory with the second application program and the second boot program, where the second application program stores a start address of the second boot program, The start address of the second boot program is at a preset position after the second application program.

The firmware to be upgraded received by the embedded device 21 from the controller 22 includes the application program 3 and the boot program 2 shown in FIG. 10. After receiving the firmware to be upgraded sent by the controller 22, the processor of the embedded device 21 writes the firmware to be upgraded into the memory of the embedded device 21. Specifically, the processor of the embedded device 21 The application program 2 stored in the memory is replaced with the application program 3 and the boot program 2. After the embedded device 21 is powered on again, the processor of the embedded device 21 executes from the start address of the boot program 2 that is the address A, and the run address of the boot program 2 is obtained to obtain the run address of the application program 3 and the code is effectively executed The starting address of is the address D, and jump to the address D of the application 3 to start execution. The application program 3 stores the start address of the boot program 2, the start address of the boot program 2 is the address E, the start address of the boot program 2 is a preset position after the tail address of the application program 3, optionally, the boot program The starting address of 2 is the length of address E relative to address C is y.

Step S803: Acquire the start address of the second boot program from the second application program, and acquire the second boot program from the start address of the second boot program.

During execution of the address of the application 3 from the address D of the application 3, the processor of the embedded device 21 acquires the address E, which is the start address of the boot program 2, from the application 3, and acquires the boot program 2 from the address E.

Step S804: Compare the first boot program and the second boot program.

After acquiring the boot program 2 from the address E, the processor of the embedded device 21 compares the boot program currently stored in the memory of the embedded device 21 with the boot program 2.

Step S805: If the first boot program and the second boot program are the same, delete the second boot program after the second application program.

As shown in FIG. 10, since the boot program currently stored in the memory of the embedded device 21 and the boot program 2 are the same, the processor of the embedded device 21 deletes the boot program 2 after the application program 3.

Step S806: If the first boot program and the second boot program are different, replace the first boot program with the second boot program.

In other embodiments, if the boot program currently stored in the memory of the embedded device 21 is different from the boot program 2, the processor of the embedded device 21 may replace the boot program currently stored in the memory of the embedded device 21 For bootloader 2.

In some embodiments, as shown in FIG. 11, the memory of the embedded device 21 currently stores the boot program 1 and the application program 1. The processor of the embedded device 21 receives the firmware to be upgraded sent by the controller 22 includes the application program 3 and the boot program 2, and the processor of the embedded device 21 writes the application program 3 and the boot program 2 to the memory of the embedded device 21 Specifically, the processor of the embedded device 21 replaces the application program 1 with the application program 3 and the boot program 2. After the embedded device 21 is powered on again, the processor of the embedded device 21 starts to execute from the start address of the boot program 1, that is, address A, and when it reaches the jump execution code area of the boot program 1, jumps to the application 2 The starting address is the address B. The address B may be the starting address of the jump execution code area in the head area of the application 3, the jump execution code area in the head area of the application 3 stores the address C, and the processor slave address of the embedded device 21 B jumps directly to address C to start running. The address C may be the starting address of the running address storage area in the head area of the application 3, the running address storage area stores the running address of the application 3, that is, the address D, and the processor of the embedded device 21 starts from the running address The storage area obtains the address D of the running address of the application 3. The address D may specifically be the start address of the copy boot program area in the application 3, and the copy boot program area stores the address E, which is the start address of the boot program 2. Further, the processor of the embedded device 21 obtains the boot program 2 from the address E, and replaces the boot program 1 in the memory of the embedded device 21 with the boot program 2. When the embedded device 21 restarts, the processor of the embedded device 21 starts to execute from the start address of the boot program 2 which is the address A. The boot program 2 can obtain the running address of the application 3 which is the address D. The embedded device 21 The processor jumps directly from boot program 2 to address D and executes application program 3. The processor of the embedded device 21 may delete the boot program 2 after the application program 3 during the execution of the application program 3, or may delete the boot program 2 after the application program 3 after replacing the boot program 1 with the boot program 2.

In this embodiment, after acquiring the firmware to be upgraded through the embedded device, the first application currently stored in the memory of the embedded device is replaced with the second application and the second boot program in the firmware to be upgraded, and the second The start address of the second boot program is obtained from the application program. After the second boot program is obtained from the start address of the second boot program, the first boot program currently stored in the memory of the embedded device and the The second boot program, if the first boot program and the second boot program are the same, delete the second boot program after the second application program, to avoid that the processor of the embedded device runs the second application program every time, The second boot program after the second application program needs to be verified to improve the running speed of the embedded device.

An embodiment of the present invention provides an embedded device. FIG. 12 is a structural diagram of an embedded device provided by an embodiment of the present invention. As shown in FIG. 12, the embedded device 110 includes: a memory 111 and a processor 112. The memory 111 stores a first boot program and a first application program; the processor 112 is used to perform the following operations: obtain firmware to be upgraded, the firmware to be upgraded includes a second application program and a second boot program; the processor 112 stores the memory 111 The first application program in is replaced with the second application program and the second boot program, the second application program stores a start address of the second boot program, the second boot program The start address is at a first preset position after the second application program, and the second application program includes a header area; the processor 112 obtains the start of the second boot program from the second application program Address and obtain the second boot program from the start address of the second boot program; the processor 112 replaces the first boot program with the second boot program, the first boot program and all The size of the header area is greater than or equal to the size of the second boot program.

Optionally, the second application program includes a first area; the first area stores a start address of the second boot program.

Optionally, when the processor 112 obtains the start address of the second boot program from the second application program, it is specifically used to: obtain the first address from the first area of the second application program. The starting address of the bootloader.

Optionally, the second application program further includes a second area, the second area stores the running address of the second application program, and the tail address of the second area is the start of the first area address.

Optionally, when the processor 112 obtains the start address of the second boot program from the second application program, it is specifically used to: determine the start address of the first area according to the second area; Acquire the start address of the second boot program from the first area of the second application according to the start address of the first area.

Optionally, the second application further includes a third area, where the third area stores a start address of the second area, and the third area is in the head of the second application within the area.

Optionally, when the processor 112 obtains the start address of the second boot program from the second application program, it is specifically used to: obtain the start address of the second area from the third area; According to the start address of the second area, determine the start address of the first area; according to the start address of the first area, obtain the first address from the first area of the second application The starting address of the second bootloader.

Optionally, the starting address of the third area is the starting address of the head area of the second application.

Optionally, the starting address of the first area is the running address of the second application program.

Optionally, the second area is within the head area of the second application.

Optionally, the size of the storage space between the start address of the first boot program and the start address of the second area is greater than or equal to the size of the second boot program.

Optionally, the starting address of the first area is at a second preset position after the running address of the second application program.

Optionally, the second area is not within the head area of the second application.

Optionally, the size of the storage space between the start address of the first boot program and the running address of the second application program is greater than or equal to the size of the second boot program.

Optionally, the first area further includes the length of the second boot program; when the processor 112 acquires the second boot program from the start address of the second boot program, it is specifically used to: The length of the second boot program is obtained from the start address of the second boot program.

Optionally, after the processor 112 replaces the first boot program with the second boot program, it is also used to: execute the second boot program starting from the start address of the second boot program; When executing the second boot program, obtain the running address of the second application program; jump from the second boot program to the running address of the second application program, and execute the second application program.

Optionally, the second boot program stores the start address of the second area; when the processor 112 executes the second boot program, when acquiring the running address of the second application program, it is specifically used : When executing the second boot program, obtain the running address of the second application program from the second area according to the start address of the second area.

Optionally, the processor 112 jumps from the second boot program to the running address of the second application program, and when the second application program is executed, it is specifically used to: jump from the second boot program to Running address of the second application program, executing the second application program, and deleting the second boot program after the second application program.

Optionally, after the processor 112 replaces the first boot program with the second boot program, it is also used to: delete the second boot program after the second application program.

Optionally, when the processor 112 replaces the first boot program with the second boot program, it is specifically used to: compare the first boot program and the second boot program; if the first boot program Unlike the second boot program, the first boot program is replaced with the second boot program.

Optionally, the processor 112 is further configured to: if the first boot program and the second boot program are the same, delete the second boot program after the second application program.

Optionally, the embedded device 110 further includes: a communication interface 113; when the processor 112 acquires firmware to be upgraded, it is specifically used to: receive the firmware to be upgraded sent by the controller through the communication interface 113.

The specific principles and implementation manners of the embedded device provided by the embodiments of the present invention are similar to the foregoing embodiments, and details are not described herein again.

In this embodiment, by replacing the first application program in the memory of the embedded device with the second application program and the second boot program in the firmware to be upgraded, the second application program stores the starting address of the second boot program, according to The starting address of the second boot program is obtained, and the first boot program in the memory is replaced with the second boot program, thereby realizing the upgrade of the application program and the boot program. The second application program includes a head area. When the size of the second boot program is larger than the size of the first boot program, the second boot program may occupy the head area of the second application program to prevent the second boot program from covering The effective execution code of the second application program makes the upgraded second application program run normally, so that the upgraded embedded device can run normally.

An embodiment of the present invention provides an embedded device. As shown in FIG. 12, the embedded device 110 includes: a memory 111 and a processor 112; the memory 111 stores a first boot program and a first application program; the processor 112 is used to perform the following operations: obtain firmware to be upgraded, and the The firmware upgrade includes a second application program and a second boot program; replacing the first application program in the memory 111 with the second application program and the second boot program, the second application program storing the The start address of the second boot program, the start address of the second boot program is at a preset position after the second application program; the start of the second boot program is obtained from the second application program Address, and obtain the second boot program from the start address of the second boot program; compare the first boot program and the second boot program; when the first boot program and the second When the boot programs are the same, delete the second boot program after the second application program.

Optionally, the processor 112 is further configured to: when the first boot program and the second boot program are different, replace the first boot program with the second boot program.

The specific principles and implementation manners of the embedded device provided by the embodiments of the present invention are similar to the embodiment shown in FIG. 9 and will not be repeated here.

In addition, this embodiment also provides a computer-readable storage medium on which a computer program is stored, which is executed by a processor to implement the program processing method described in the above embodiment.

In the several embodiments provided by the present invention, it should be understood that the disclosed device and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a division of logical functions. In actual implementation, there may be other divisions, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium. The above software functional units are stored in a storage medium, and include several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute the method described in each embodiment of the present invention Partial steps. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Those skilled in the art can clearly understand that, for convenience and conciseness of description, only the above-mentioned division of each functional module is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated by different functional modules according to needs, that is, the device The internal structure of is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiments, and details are not described herein again.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, rather than limiting it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features can be equivalently replaced; and these modifications or replacements do not deviate from the essence of the corresponding technical solutions of the technical solutions of the embodiments of the present invention range.

Claims

A program processing method is applied to an embedded device, and a memory of the embedded device stores a first boot program and a first application program; characterized in that the method includes:

Obtain firmware to be upgraded, where the firmware to be upgraded includes a second application program and a second boot program;

Replacing the first application program in the memory with the second application program and the second boot program, the second application program storing a start address of the second boot program, the first The start address of the second boot program is at a first preset position after the second application program, and the second application program includes a header area;

Acquiring the start address of the second boot program from the second application program, and acquiring the second boot program from the start address of the second boot program;

The first boot program is replaced with the second boot program, and the sizes of the first boot program and the head region are greater than or equal to the size of the second boot program.
The method according to claim 1, wherein the second application program includes a first area; the first area stores a start address of the second boot program.
The method according to claim 2, wherein the acquiring the start address of the second boot program from the second application program comprises:

The start address of the second boot program is obtained from the first area of the second application program.
The method according to claim 2, wherein the second application program further includes a second area, the second area stores a running address of the second application program, and a tail address of the second area Is the starting address of the first area.
The method according to claim 4, wherein the acquiring the start address of the second boot program from the second application program comprises:

Determine the starting address of the first area according to the second area;

Acquire the start address of the second boot program from the first area of the second application according to the start address of the first area.
The method according to claim 4, wherein the second application further includes a third area, the third area stores a start address of the second area, and the third area is located in the Within the head area of the second application.
The method according to claim 6, wherein the acquiring the start address of the second boot program from the second application program comprises:

Acquiring the start address of the second area from the third area;

Determine the start address of the first area according to the start address of the second area;

Acquire the start address of the second boot program from the first area of the second application according to the start address of the first area.
The method according to claim 6 or 7, wherein the starting address of the third area is the starting address of the head area of the second application.
The method according to any one of claims 4-8, wherein the starting address of the first area is the running address of the second application program.
The method according to claim 9, wherein the second area is within the head area of the second application.
The method according to claim 10, wherein the size of the storage space between the start address of the first boot program and the start address of the second area is greater than or equal to the size of the second boot program .
The method according to any one of claims 4-8, wherein the starting address of the first area is at a second preset position after the running address of the second application program.
The method according to claim 12, wherein the second area is not within the head area of the second application.
The method according to claim 13, wherein the size of the storage space between the start address of the first boot program and the running address of the second application program is greater than or equal to the size of the second boot program .
The method according to any one of claims 2-14, wherein the first area further includes a length of the second boot program;

The acquiring the second boot program starting from the starting address of the second boot program includes:

According to the length of the second boot program, the second boot program is acquired starting from the start address of the second boot program.
The method according to any one of claims 4-7 and 10-13, wherein after the first boot program is replaced with the second boot program, the method further comprises:

Starting from the start address of the second boot program, executing the second boot program;

Acquiring the running address of the second application program when executing the second boot program;

Jump from the second boot program to the running address of the second application program, and execute the second application program.
The method according to claim 16, wherein the second boot program stores a start address of the second area;

The acquiring the running address of the second application program when executing the second boot program includes:

When the second boot program is executed, the running address of the second application program is obtained from the second area according to the start address of the second area.
The method according to claim 16 or 17, wherein the jump from the second boot program to the running address of the second application program to execute the second application program includes:

Jump from the second boot program to the running address of the second application program, execute the second application program, and delete the second boot program after the second application program.
The method according to any one of claims 1-15, wherein after replacing the first boot program with the second boot program, the method further comprises:

The second boot program after deleting the second application program.
The method according to any one of claims 1-19, wherein the processor replacing the first boot program with the second boot program includes:

Comparing the first boot program and the second boot program;

If the first boot program and the second boot program are different, the first boot program is replaced with the second boot program.
The method of claim 20, further comprising:

If the first boot program and the second boot program are the same, delete the second boot program after the second application program.
The method according to any one of claims 1-21, wherein the acquiring firmware to be upgraded comprises:

Receiving the firmware to be upgraded sent by the controller.
A program processing method is applied to an embedded device, and a memory of the embedded device stores a first boot program and a first application program; characterized in that the method includes:

Obtain firmware to be upgraded, where the firmware to be upgraded includes a second application program and a second boot program;

Replacing the first application program in the memory with the second application program and the second boot program, the second application program storing a start address of the second boot program, the first The start address of the second boot program is at a preset position after the second application program;

Acquiring the start address of the second boot program from the second application program, and acquiring the second boot program from the start address of the second boot program;

Comparing the first boot program and the second boot program;

If the first boot program and the second boot program are the same, delete the second boot program after the second application program.
The method of claim 23, further comprising:

If the first boot program and the second boot program are different, the first boot program is replaced with the second boot program.
An embedded device, which is characterized by comprising: a memory and a processor;

The memory stores a first boot program and a first application program;

The processor is used to perform the following operations:

Obtain firmware to be upgraded, where the firmware to be upgraded includes a second application program and a second boot program;

Replacing the first application program in the memory with the second application program and the second boot program, the second application program storing a start address of the second boot program, the first The start address of the second boot program is at a first preset position after the second application program, and the second application program includes a header area;

Acquiring the start address of the second boot program from the second application program, and acquiring the second boot program from the start address of the second boot program;

The first boot program is replaced with the second boot program, and the sizes of the first boot program and the head region are greater than or equal to the size of the second boot program.
The embedded device according to claim 25, wherein the second application program includes a first area; the first area stores a start address of the second boot program.
The embedded device according to claim 26, wherein when the processor obtains the start address of the second boot program from the second application program, it is specifically used to:

The start address of the second boot program is obtained from the first area of the second application program.
The embedded device according to claim 26, wherein the second application further comprises a second area, the second area stores an execution address of the second application, and the second area The tail address is the start address of the first area.
The embedded device according to claim 28, wherein when the processor obtains the start address of the second boot program from the second application program, it is specifically used to:

Determine the starting address of the first area according to the second area;

Acquire the start address of the second boot program from the first area of the second application according to the start address of the first area.
The embedded device according to claim 28, wherein the second application further comprises a third area, the third area stores a start address of the second area, and the third area is in Within the head area of the second application.
The embedded device according to claim 30, wherein when the processor obtains the start address of the second boot program from the second application program, it is specifically used to:

Acquiring the start address of the second area from the third area;

Determine the start address of the first area according to the start address of the second area;

Acquire the start address of the second boot program from the first area of the second application according to the start address of the first area.
The embedded device according to claim 30 or 31, wherein the starting address of the third area is the starting address of the head area of the second application.
The embedded device according to any one of claims 28-32, wherein the starting address of the first area is the running address of the second application program.
The embedded device according to claim 33, wherein the second area is within the head area of the second application.
The embedded device according to claim 34, wherein the size of the storage space between the start address of the first boot program and the start address of the second area is greater than or equal to the second boot program the size of.
The embedded device according to any one of claims 28 to 32, wherein the starting address of the first area is at a second preset position after the running address of the second application program.
The embedded device according to claim 36, wherein the second area is not within the head area of the second application.
The embedded device according to claim 37, wherein the size of the storage space between the start address of the first boot program and the running address of the second application program is greater than or equal to the second boot program the size of.
The embedded device according to any one of claims 26 to 38, wherein the first area further includes the length of the second boot program;

When the processor acquires the second boot program from the start address of the second boot program, it is specifically used to:

According to the length of the second boot program, the second boot program is acquired starting from the start address of the second boot program.
The embedded device according to any one of claims 28-31, 34, 35, 37, wherein after the processor replaces the first boot program with the second boot program, :

Starting from the start address of the second boot program, executing the second boot program;

Acquiring the running address of the second application program when executing the second boot program;

Jump from the second boot program to the running address of the second application program, and execute the second application program.
The embedded device according to claim 40, wherein the second boot program stores a start address of the second area;

When the processor executes the second boot program and obtains the running address of the second application program, it is specifically used to:

When the second boot program is executed, the running address of the second application program is obtained from the second area according to the start address of the second area.
The embedded device according to claim 40 or 41, wherein the processor jumps from the second boot program to the running address of the second application program, and when executing the second application program, Specifically used for:

Jump from the second boot program to the running address of the second application program, execute the second application program, and delete the second boot program after the second application program.
The embedded device according to any one of claims 25 to 39, wherein after the processor replaces the first boot program with the second boot program, the processor is further used to:

The second boot program after deleting the second application program.
The embedded device according to any one of claims 25 to 43, wherein when the processor replaces the first boot program with the second boot program, it is specifically used to:

Comparing the first boot program and the second boot program;

If the first boot program and the second boot program are different, the first boot program is replaced with the second boot program.
The embedded device according to claim 44, wherein the processor is further configured to:

If the first boot program and the second boot program are the same, delete the second boot program after the second application program.
The embedded device according to any one of claims 25 to 45, wherein the embedded device further comprises: a communication interface;

When the processor obtains the firmware to be upgraded, it is specifically used to:

Receiving the firmware to be upgraded sent by the controller through the communication interface.
An embedded device, which is characterized by comprising: a memory and a processor;

The memory stores a first boot program and a first application program;

The processor is used to perform the following operations:

Obtain firmware to be upgraded, where the firmware to be upgraded includes a second application program and a second boot program;

Replacing the first application program in the memory with the second application program and the second boot program, the second application program storing a start address of the second boot program, the first The start address of the second boot program is at a preset position after the second application program;

Acquiring the start address of the second boot program from the second application program, and acquiring the second boot program from the start address of the second boot program;

Comparing the first boot program and the second boot program;

When the first boot program and the second boot program are the same, delete the second boot program after the second application program.
The embedded device according to claim 47, wherein the processor is further configured to:

When the first boot program and the second boot program are different, the first boot program is replaced with the second boot program.
A computer-readable storage medium characterized in that a computer program is stored thereon, the computer program is executed by a processor to implement the method according to any one of claims 1-24.