CN113094067A - Firmware updating method of IO module and IO module - Google Patents
Firmware updating method of IO module and IO module Download PDFInfo
- Publication number
- CN113094067A CN113094067A CN202110340713.2A CN202110340713A CN113094067A CN 113094067 A CN113094067 A CN 113094067A CN 202110340713 A CN202110340713 A CN 202110340713A CN 113094067 A CN113094067 A CN 113094067A
- Authority
- CN
- China
- Prior art keywords
- program
- firmware
- new
- module
- size
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a firmware updating method of an IO module, which comprises the steps of respectively storing a first program and a second program which are positioned in the same firmware in a first storage area and a second storage area of an MCU on-chip memory of the IO module, wherein the first storage area corresponds to a low-order address, and the second storage area corresponds to a high-order address; when the firmware updating condition of the IO module is triggered, executing a first program to realize the updating of the firmware. The first program and the first program are combined into one firmware, the firmware updating of the IO module can be completed through one-time deployment when the firmware is deployed, the maintenance is convenient, the maintenance cost is reduced, the firmware updating of the IO module is completed through one-time deployment, and the deployment workload and the deployment error are reduced.
Description
Technical Field
The invention relates to the field of embedded system control, in particular to a firmware updating method of an IO module and the IO module.
Background
In a DCS (distributed control system), a large number of IO modules are required to collect field data or to drive field devices. An IO (input/output) module in the DCS is an embedded terminal device based on a Microcontroller (MCU), a memory of the DCS is stored with firmware codes, the firmware types comprise boot loader (boot load) firmware and application firmware, and the boot loader firmware is an initialization program started when the IO module is powered on or reset and is used for carrying out corresponding initialization on the IO module. The application firmware is a program for realizing various functions of the IO module. With the update of the function of the IO module, the firmware of the IO module also needs to be updated.
In the prior art, BootLoader firmware and application firmware are developed and maintained in independent projects. When firmware is updated by the IO module, deployment needs to be performed twice, BootLoader firmware needs to be burnt and written to the IO module for the first deployment, namely BootLoader firmware codes are written into a starting address of a memory in the IO module, and application firmware needs to be burnt and written to the IO module for the second deployment, namely application firmware codes are written into an address behind the BootLoader firmware codes of the memory in the IO module. Because the BootLoader firmware and the application firmware are developed in independent projects and cannot be maintained uniformly, the maintenance cost is high, the deployment workload is increased and the deployment errors are increased due to twice deployment when the IO module firmware is updated.
Disclosure of Invention
The invention aims to overcome the defects that in the prior art, boot loader firmware and application firmware are developed in independent projects and cannot be maintained uniformly, so that the maintenance cost is high, and deployment workload and deployment errors are increased due to twice deployment during IO module firmware updating.
The invention solves the technical problems through the following technical scheme:
a firmware updating method of an IO module comprises the following steps:
respectively storing a first program and a second program which are positioned in the same firmware in a first storage area and a second storage area of an MCU on-chip memory of an IO module, wherein the first storage area corresponds to a low-order address, and the second storage area corresponds to a high-order address;
and when a firmware updating condition of the IO module is triggered, executing the first program to update the firmware.
Preferably, the executing the first program to update the firmware includes:
executing the first program to read an update flag, and erasing the contents of the second storage area when the update flag indicates that the firmware has an update, and reading a new second program and writing the new second program into the second storage area.
Preferably, the reading update flag includes:
the update flag is read from the non-volatile memory of the IO module.
Preferably, the erasing the content of the second storage area includes:
and erasing the content of a storage space after a second program starting address, wherein the second program starting address is equal to an offset address obtained by adding the size of the first program to the firmware storage starting address of the memory on the MCU chip, or is equal to the offset address obtained by adding the size of the first program to the size of the data boundary protection area to the firmware storage starting address of the memory on the MCU chip when the data boundary protection area exists between the first program and the second program.
Preferably, the reading the new second program and writing into the second storage area includes:
and reading new firmware from the nonvolatile memory of the IO module, and writing a second program included in the new firmware into the second storage area.
Preferably, the reading the new second program and writing into the second storage area includes:
reading the initial storage space of the initial address of the new second program and writing the initial storage space into the second storage area until the size of the written data after reading is equal to the size of the new second program;
wherein, the new second program starting address is equal to an offset address obtained by adding the size of the first program to a new firmware storage starting address, or, when a data boundary protection area exists between the first program and the new second program, is equal to an offset address obtained by adding the size of the first program to the size of the data boundary protection area to the new firmware storage starting address;
the size of the new second program is equal to the size of the new firmware minus the size of the first program, or, when a data boundary protection area exists between the first program and the new second program, the size of the new firmware minus the size of the first program minus the size of the data boundary protection area.
Preferably, the executing the first program to update the firmware further includes: after writing to the second memory area, the update flag and the original storage of the new second program are cleared.
An IO module comprises a micro control unit;
the on-chip memory of the micro control unit comprises a first memory area and a second memory area, wherein the first memory area and the second memory area are respectively used for storing a first program and a second program which are positioned in the same firmware, the first memory area corresponds to a low-order address, and the second memory area corresponds to a high-order address;
and the micro control unit executes the first program to update the firmware when the firmware update condition of the IO module is triggered.
Preferably, the micro control unit comprises an ARM Cortex-M architecture micro control unit.
Preferably, the IO module further includes a nonvolatile memory.
The positive progress effects of the invention are as follows: the first program and the second program are combined in one firmware for development, the first program and the second program are stored in the memory in a partition mode, the firmware updating of the IO module can be completed through one-time deployment during firmware updating, the first program and the second program are combined in one firmware for development, maintenance is facilitated, maintenance cost is reduced, the firmware updating of the IO module is completed through one-time deployment, and deployment workload and deployment errors are reduced.
Drawings
Fig. 1 is a flowchart illustrating a firmware updating method for an IO module according to embodiment 1 of the present invention.
Fig. 2 is a schematic diagram of address space partitioning of an MCU on-chip memory according to embodiment 1 of the present invention.
Fig. 3 is a hardware platform diagram according to embodiment 1 of the present invention.
Fig. 4 shows a frame format of firmware downloading in an application according to embodiment 1 of the present invention.
Fig. 5 is a schematic structural diagram of an IO module according to embodiment 2 of the present invention.
Detailed Description
The invention is further illustrated by the following examples, which are not intended to limit the scope of the invention.
Example 1
The present embodiment provides a firmware updating method for an IO module, as shown in fig. 1, including the following steps:
In the firmware updating method of the IO module according to the embodiment, the first program and the second program are merged into one firmware (which may also be referred to as one project) for development, and the first program and the second program are stored in a memory in a partitioned manner, so that firmware updating of the IO module can be completed through one-time deployment during firmware updating, and the first program and the second program are merged into one firmware for development, so that maintenance is facilitated, maintenance cost is reduced, firmware updating of the IO module is completed through one-time deployment, and deployment workload and deployment errors are reduced.
In an optional embodiment, in step 200, executing the first program to implement updating of the second program specifically includes: executing the first program to read the update flag, erasing the contents of the second storage area when the update flag indicates that the firmware has an update, and reading the new second program and writing the new second program into the second storage area. The new second program is the program to be updated to the second memory area of the MCU on-chip memory. It should be noted that the new second program is included in the new firmware, and the new firmware includes the first program in addition to the new second program. After the MCU downloads the new firmware to the non-volatile memory (e.g., Flash, PROM, EEPROM, EPROM) of the IO module, the update flag on the non-volatile memory is set, the update flag on the non-volatile memory is read when the first program is executed, the content of the second storage area is erased when the update flag indicates that the firmware is updated, and the new second program is read and written into the second storage area, so as to facilitate the firmware update operation.
In an optional embodiment, in step 200, reading the update flag specifically includes: the update flag is read from the non-volatile memory of the IO module. By reading the update flag from the non-volatile memory, normal operation of the IO module may not be affected.
In an optional implementation manner, in step 200, erasing the content of the second storage area specifically includes:
and erasing the content of the storage space after the second program starting address, wherein the second program starting address refers to the starting address of the second program in the on-chip memory and is also the starting address of the second storage area.
When the first program and the second program are adjacent (i.e. the data boundary protection area is not stored between the first program and the second program), the starting address of the second program is equal to the offset address obtained by adding the size of the first program to the starting address of the firmware storage of the MCU on-chip memory. The firmware storage start address refers to a start address of stored firmware, is a start address of the first storage area, and is also a start address of storing the first program.
Or when a data boundary protection area exists between the first program and the second program, the starting address of the second program is equal to an offset address obtained by adding the storage starting address of the firmware of the memory on the MCU chip, the size of the first program and the size of the data boundary protection area. As shown in fig. 2, a source file in a Bootloader program is designated to be placed in a storage space between a starting address of a physical address of Flash on an MCU chip and a starting address of an application program, and an application program code is stored in the storage space after the starting address of the application program, where the storage space constitutes a storage space after a starting address of a second program, the first program is the Bootloader program, the second program is the application program, and the size of the first program is the size of the Bootloader program. The second program start address, i.e. the application start address, can be obtained by the following algorithm:
and the second program starting address is equal to the size of the Flash firmware storage starting address + Bootloader program on the MCU chip.
When a data boundary protection region exists between the first program and the second program, the second program start address, i.e., the application start address, can be obtained by the following algorithm:
and the second program starting address is the storage starting address of the Flash firmware on the MCU chip, the size of the Bootloader program and the size of the data boundary protection area.
The initial address of the second program is calculated through the algorithm, so that the content of the corresponding address is clear, the firmware can be updated more conveniently, and the firmware updating efficiency is improved. The data boundary protection area is set to prevent the error of the updated data and ensure the accuracy of the updated data.
In an optional implementation manner, in step 200, reading the new second program and writing the new second program into the second storage area specifically includes: the new second firmware is read from the non-volatile memory of the IO module and written to the second storage area. For example, when the IO module is powered on or reset, the Bootloader program is first entered. The Bootloader program will first read the update flag storage address on the onboard Flash (which may also be called off-chip Flash, and may be used as a non-volatile memory). If the update flag is true, the BootLoader program will erase the storage space behind the second initial address of the Flash on the MCU chip. After the successful erasing, the BootLoader program obtains an offset address from the new firmware storage address of the onboard Flash plus the size of the BootLoader program plus the size of the data boundary protection area, the offset address is read from the storage space starting from the offset address in batches and written into a second storage area of the on-chip Flash of the MCU on the RAM until the new firmware size minus the size of the BootLoader program is completed, and then the data movement minus the size of the data boundary protection area is completed (off-chip Flash- > on-chip RAM- > on-chip Flash). By arranging the MCU off-chip memory, the firmware to be updated can be temporarily stored, and new second firmware is read from the MCU off-chip memory of the IO module and written into the second storage area when the firmware is updated, so that the firmware is updated, and the firmware updating operation is facilitated.
In an optional implementation manner, in step 200, reading the new second firmware and writing the new second firmware into the second storage area specifically includes:
and reading the initial storage space of the initial address of the new second program and writing the initial storage space into the second storage area until the size of the written data after reading is equal to that of the new second program.
Wherein the new second program start address refers to a start address of a second program on the non-volatile memory that needs to be updated to the MCU on-chip memory. When the first program and the new second program are in close proximity (i.e. no data boundary protection area is stored between the two) in the new firmware, the new second program start address is equal to the offset address obtained by adding the size of the first program to the new firmware storage start address. Or, when a data boundary protection area exists between the first program and the new second program, the new second program starting address is equal to an offset address obtained by adding the new firmware storage starting address to the size of the first program plus the size of the data boundary protection area.
When the first program and the new second program are immediately adjacent (i.e., no data boundary protection area is stored between them) in the new firmware, the size of the new second program is equal to the total size of the new firmware minus the firmware size of the first program. Or, when a data boundary protection region exists between the first program and the new second program, the size of the new second program is equal to the size of the new firmware minus the size of the first program minus the size of the new second program.
The new second program starting address and the size of the new second program obtained through the calculation can be used for updating the firmware more conveniently, and the firmware updating efficiency is improved.
In another optional embodiment, the firmware updating method further includes the following steps:
after writing to the second memory area, the update flag and the original storage of the new firmware are cleared. Specifically, after the new firmware is moved, the BootLoader program will clear the update flag of the off-chip Flash and the new firmware stored thereon, so as to facilitate the next update operation.
The specific application of the firmware updating method of the IO module of this embodiment is as follows:
the firmware updating method of the IO module of this embodiment is deployed on a hardware platform shown in fig. 3, the firmware updating method of the IO module is run on an arm port-M3/M4 kernel MCU, the MCU is connected to an ethernet control chip through a LocalBus bus, the ethernet control chip is connected to an ethernet through a PHY (port physical layer), when the MCU receives an update instruction sent from an external controller, the MCU obtains a new firmware through the ethernet, and since the MCU is in a running state at this time, the MCU writes the new firmware into a FLASH chip or other non-volatile memory stored on or off board through an SPI (serial peripheral interface) bus for temporary storage.
In order to implement that the BootLoader program and the application program are developed and designed in the same interior and stored in the same firmware, so that the firmware only needs to be deployed once, the firmware updating method of the IO module of the embodiment uses a distributed loading technology, the BootLoader program and the application program are stored in a partition mode in one firmware, the BootLoader program is stored in the front section of the address of the Flash memory on the armartex-M series MCU, and the application program is stored in the rear section of the address of the Flash memory on the armartex-M series MCU.
Wherein the size of the Bootloader program is determined by the actual size of the actual Bootloader. In order to realize data protection, a data boundary protection area may be added between the first program and the second program, and the size of the data boundary protection area is usually set manually, and may be any size such as 1024 bytes or 2048 bytes.
The BootLoader program and the application program are firmware developed in a software project, in order to enable the BootLoader program to enter the application program after the BootLoader program is completely run, jump among the programs is achieved through a program jump instruction, and the efficiency of program execution is improved. And the BootLoader program finishes firmware updating and finishes firmware downloading in the application program. The new firmware is stored in onboard Flash, which also stores an update flag.
The BootLoader program can only perform programming update on the application program of the firmware to be updated after erasing the internal application program code of the application program storage address, and does not update the BootLoader program.
The operation or execution characteristics of the firmware update method of the IO module are as follows:
when the IO module is powered on or reset, the Bootloader program is firstly entered. The Bootloader program will first read the storage address of the update mark on the onboard Flash. If the update flag is true. The BootLoader program can erase the memory space behind the initial address of the Flash physical address application program on the MCU chip. After the successful erasing, the BootLoader program obtains an offset address from the new firmware storage address of the onboard Flash plus the size of the BootLoader program plus the size of the boundary protection, reads an application program storage area written into the on-chip Flash of the MCU on the RAM in batches from the storage space starting from the offset address until the firmware size minus the size of the BootLoader program is completed, and then subtracts the data transfer (off-chip Flash- > on-chip RAM- > on-chip Flash) of the size of the data boundary protection area. And after the new firmware is moved, the BootLoader program can clear the update mark of the off-chip Flash and the new firmware. After the update flag and the new firmware are cleared, the BootLoader program enters the application program after the BootLoader program is completed. If the update flag is false, the BootLoader program is executed and enters the application program.
The application requires the implementation of the download of the new firmware and the storage of the new firmware in the off-chip Flash. And writing the update mark into the off-chip Flash after the new firmware is successfully stored. The frame format of the firmware download frame is shown in fig. 4. The frame head of the frame format is used for indicating the type of the frame, the functional code of the frame format is used for indicating the firmware downloading frame, the data length indicates the large length of the frame data, the address offset indicates the corresponding offset address in the MCU, the data indicates the content of the new firmware, and the CRC (cyclic redundancy check) 16 indicates the check code. After the update flag is written to the off-chip Flash, the application may perform a soft reset (restart). The firmware update is completed in the BootLoader program.
Example 2
An IO module of this embodiment, as shown in fig. 5, includes a micro control unit 1 (MCU). The on-chip memory of the micro control unit 1 comprises a first memory area and a second memory area, wherein the first memory area and the second memory area are respectively used for storing a first program and a second program which are positioned in the same firmware, the first memory area corresponds to a low-order address, and the second memory area corresponds to a high-order address; when the firmware update condition of the IO module is triggered, the micro control unit 1 executes the first program to update the firmware.
In an alternative embodiment, the micro-control unit 1 comprises a micro-control unit of the ARM Cortex-M architecture.
In an alternative embodiment, the IO module further includes a non-volatile memory 2. Such as Flash, PROM, EEPROM, EPROM.
In an alternative embodiment, the executing the first program to implement the updating of the firmware includes:
executing the first program to read an update flag, and erasing the contents of the second storage area when the update flag indicates that the firmware has an update, and reading a new second program and writing the new second program into the second storage area.
In an optional embodiment, the reading the update flag includes:
the update flag is read from the non-volatile memory of the IO module.
In an alternative embodiment, the erasing the content of the second storage area includes:
and erasing the content of a storage space after a second program starting address, wherein the second program starting address is equal to an offset address obtained by adding the size of the first program to the firmware storage starting address of the memory on the MCU chip, or is equal to the offset address obtained by adding the size of the first program to the size of the data boundary protection area to the firmware storage starting address of the memory on the MCU chip when the data boundary protection area exists between the first program and the second program.
In an alternative embodiment, the reading the new second program and writing to the second storage area includes:
and reading new firmware from the nonvolatile memory of the IO module, and writing a second program included in the new firmware into the second storage area.
In an alternative embodiment, the reading the new second program and writing to the second storage area includes:
reading the initial storage space of the initial address of the new second program and writing the initial storage space into the second storage area until the size of the written data after reading is equal to the size of the new second program;
wherein, the new second program starting address is equal to an offset address obtained by adding the size of the first program to a new firmware storage starting address, or, when a data boundary protection area exists between the first program and the new second program, is equal to an offset address obtained by adding the size of the first program to the size of the data boundary protection area to the new firmware storage starting address;
the size of the new second program is equal to the size of the new firmware minus the size of the first program, or, when a data boundary protection area exists between the first program and the new second program, the size of the new firmware minus the size of the first program minus the size of the data boundary protection area.
In an optional embodiment, the executing the first program to update the firmware further includes: after writing to the second memory area, the update flag and the original storage of the new second program are cleared.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and that the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the spirit and scope of the invention, and these changes and modifications are within the scope of the invention.
Claims (10)
1. A firmware update method for an IO module is characterized by comprising the following steps:
respectively storing a first program and a second program which are positioned in the same firmware in a first storage area and a second storage area of an MCU on-chip memory of an IO module, wherein the first storage area corresponds to a low-order address, and the second storage area corresponds to a high-order address;
and when a firmware updating condition of the IO module is triggered, executing the first program to update the firmware.
2. The method for updating firmware of an IO module according to claim 1, wherein the executing the first program to update the firmware includes:
executing the first program to read an update flag, and erasing the contents of the second storage area when the update flag indicates that the firmware has an update, and reading a new second program and writing the new second program into the second storage area.
3. The method for updating firmware of an IO module according to claim 2, wherein the reading the update flag includes:
the update flag is read from the non-volatile memory of the IO module.
4. The method for updating firmware of an IO module according to claim 2, wherein the erasing contents of the second storage area includes:
and erasing the content of a storage space after a second program starting address, wherein the second program starting address is equal to an offset address obtained by adding the size of the first program to the firmware storage starting address of the memory on the MCU chip, or is equal to the offset address obtained by adding the size of the first program to the size of the data boundary protection area to the firmware storage starting address of the memory on the MCU chip when the data boundary protection area exists between the first program and the second program.
5. The method for updating firmware of an IO module according to claim 2, wherein the reading of the new second program and the writing to the second storage area includes:
and reading new firmware from the nonvolatile memory of the IO module, and writing a second program included in the new firmware into the second storage area.
6. The method for updating firmware of an IO module according to claim 2, wherein the reading of the new second program and the writing to the second storage area includes:
reading the initial storage space of the initial address of the new second program and writing the initial storage space into the second storage area until the size of the written data after reading is equal to the size of the new second program;
wherein, the new second program starting address is equal to an offset address obtained by adding the size of the first program to a new firmware storage starting address, or, when a data boundary protection area exists between the first program and the new second program, is equal to an offset address obtained by adding the size of the first program to the size of the data boundary protection area to the new firmware storage starting address;
the size of the new second program is equal to the size of the new firmware minus the size of the first program, or, when a data boundary protection area exists between the first program and the new second program, the size of the new firmware minus the size of the first program minus the size of the data boundary protection area.
7. A firmware update method for an IO module according to claim 2, wherein the executing the first program to realize the update of the firmware further comprises: after writing to the second memory area, the update flag and the original storage of the new second program are cleared.
8. An IO module is characterized by comprising a micro control unit;
the on-chip memory of the micro control unit comprises a first memory area and a second memory area, wherein the first memory area and the second memory area are respectively used for storing a first program and a second program which are positioned in the same firmware, the first memory area corresponds to a low-order address, and the second memory area corresponds to a high-order address;
and the micro control unit executes the first program to update the firmware when the firmware update condition of the IO module is triggered.
9. An IO module as claimed in claim 8, wherein the micro-control unit comprises an ARM Cortex-M architecture micro-control unit.
10. An IO module as claimed in claim 8, wherein the IO module further comprises a non-volatile memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110340713.2A CN113094067A (en) | 2021-03-30 | 2021-03-30 | Firmware updating method of IO module and IO module |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110340713.2A CN113094067A (en) | 2021-03-30 | 2021-03-30 | Firmware updating method of IO module and IO module |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113094067A true CN113094067A (en) | 2021-07-09 |
Family
ID=76670929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110340713.2A Pending CN113094067A (en) | 2021-03-30 | 2021-03-30 | Firmware updating method of IO module and IO module |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113094067A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102915249A (en) * | 2012-11-02 | 2013-02-06 | 苏州科达科技股份有限公司 | Method and device for remotely realizing firmware updating |
| CN106095480A (en) * | 2016-05-31 | 2016-11-09 | 青岛海信宽带多媒体技术有限公司 | A kind of method and device of optical module firmware upgrading |
| US20170293484A1 (en) * | 2016-04-11 | 2017-10-12 | Endress+Hauser Conducta Gmbh+Co. Kg | Method for updating a firmware component and device of measurement and control technology |
| CN111356982A (en) * | 2018-11-30 | 2020-06-30 | 深圳市大疆创新科技有限公司 | Program processing method, program processing apparatus, and storage medium |
| CN111433739A (en) * | 2018-11-30 | 2020-07-17 | 深圳市大疆创新科技有限公司 | Program upgrading method and embedded device |
-
2021
- 2021-03-30 CN CN202110340713.2A patent/CN113094067A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102915249A (en) * | 2012-11-02 | 2013-02-06 | 苏州科达科技股份有限公司 | Method and device for remotely realizing firmware updating |
| US20170293484A1 (en) * | 2016-04-11 | 2017-10-12 | Endress+Hauser Conducta Gmbh+Co. Kg | Method for updating a firmware component and device of measurement and control technology |
| CN106095480A (en) * | 2016-05-31 | 2016-11-09 | 青岛海信宽带多媒体技术有限公司 | A kind of method and device of optical module firmware upgrading |
| CN111356982A (en) * | 2018-11-30 | 2020-06-30 | 深圳市大疆创新科技有限公司 | Program processing method, program processing apparatus, and storage medium |
| CN111433739A (en) * | 2018-11-30 | 2020-07-17 | 深圳市大疆创新科技有限公司 | Program upgrading method and embedded device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110231952B (en) | ECU program backup and cyclic upgrade control method and device | |
| US7664923B2 (en) | Method and system for updating software | |
| US9164756B2 (en) | Software updating process for an embedded device | |
| US5664194A (en) | Method for autonomously transferring code to a computer without accessing local memory by the central processing unit | |
| US7908466B2 (en) | Method and apparatus for booting a microprocessor system using boot code stored on a serial flash memory array having a random-access interface | |
| JP4668416B2 (en) | Protecting boot block code when enabling write access to the boot block | |
| WO2022007656A1 (en) | Bootloader software updating method and apparatus, embedded controller, and storage medium | |
| US8595716B2 (en) | Failsafe firmware updates | |
| CN110321170B (en) | Starting-up method | |
| CN112947977A (en) | Software online upgrading method and system | |
| US8036786B2 (en) | On-vehicle control apparatus | |
| CN113110891B (en) | Firmware loading method and device for solid state disk, computer equipment and storage medium | |
| CN112540725A (en) | Nonvolatile data storage method, embedded system and storage medium | |
| CN112667265A (en) | Method and device for updating bootstrap program | |
| CN110297726B (en) | Computer system with serial presence detection data and memory module control method | |
| CN111026417A (en) | Embedded equipment upgrading method and embedded equipment | |
| JP2001043101A (en) | Method and device for changing memory contents of controller | |
| US20030005212A1 (en) | Method and apparatus for dynamically modifying a stored program | |
| CN114816273B (en) | Norflash-oriented adaptive optimal configuration method, device and medium | |
| CN113094067A (en) | Firmware updating method of IO module and IO module | |
| CN116185299A (en) | Flash memory controller and related device and method | |
| CN105204896A (en) | BootLoader design method of digital storage oscilloscope | |
| JP3805195B2 (en) | Program rewriting apparatus and program rewriting method | |
| JP2012118904A (en) | Information processing apparatus | |
| JP2001117766A (en) | Information processor with patch function of mask rom |
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 |