CN115473807A - Firmware upgrading method, equipment, system and storage medium - Google Patents
Firmware upgrading method, equipment, system and storage medium Download PDFInfo
- Publication number
- CN115473807A CN115473807A CN202211008511.9A CN202211008511A CN115473807A CN 115473807 A CN115473807 A CN 115473807A CN 202211008511 A CN202211008511 A CN 202211008511A CN 115473807 A CN115473807 A CN 115473807A
- Authority
- CN
- China
- Prior art keywords
- area
- app
- firmware
- charging
- charging equipment
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a firmware upgrading method, equipment, a system and a storage medium, which relate to the technical field of computers, and the scheme comprises the following steps: in the APP operation area operation process of the charging equipment, under the condition that the charging equipment determines to upgrade the firmware of the charging equipment, the charging equipment acquires upgrade data of the firmware of the charging equipment from the charging equipment in a background mode. The charging equipment stores the upgrading data of the firmware in an APP backup area of the charging equipment. And when the charging equipment is determined to enter the BootLoader area from the APP operation area through the first operation and the APP backup area is detected to have the upgrade data, the charging equipment moves the upgrade data to the APP operation area. And the charging equipment upgrades the firmware of the charging equipment by using the upgrade data in the APP operation area. The scheme is used for realizing the remote upgrading of the firmware of the charging pile control board under the condition that the normal work of the charging pile is not influenced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a firmware upgrading method, device, system, and storage medium.
Background
In the prior art, when the board firmware of the charging pile of the robot is upgraded, a worker is usually required to go to the site to manually disassemble the machine so as to upgrade the firmware. Under the condition, the charging pile is usually in an off-line state in the upgrading process, and normal work between the charging pile and the robot is influenced. In addition, the staff need carry out manual upgrading to filling electric pile on the spot, can increase manpower and time cost, and can't realize the timely upgrading to the control panel.
Disclosure of Invention
The embodiment of the application provides a firmware upgrading method, equipment, a system and a storage medium, and the scheme is used for remotely upgrading the firmware of a charging pile control board under the condition that normal work of a charging pile is not influenced.
In a first aspect, an embodiment of the present application provides a firmware upgrade method, where the method includes: in the operation process of the APP operation area of the charging equipment, under the condition that the charging equipment determines to upgrade the firmware of the charging equipment, the charging equipment acquires upgrade data of the firmware of the charging equipment from the mobile equipment in a background mode. The charging equipment stores the upgrading data of the firmware in an APP backup area of the charging equipment. And when the charging equipment is determined to enter the BootLoader area from the APP operation area through the first operation and the APP backup area is detected to have the upgrade data, the charging equipment moves the upgrade data to the APP operation area. And the charging equipment upgrades the firmware of the charging equipment by using the upgrade data in the APP operation area.
The embodiment of the application provides a firmware upgrading method, wherein under the condition that firmware of charging equipment is determined to be upgraded, upgrading data of the firmware of the charging equipment is acquired from mobile equipment in a background mode in the running process of an APP (application program) running area of the charging equipment. Receiving the upgrading data through the background mode can avoid charging equipment from jumping to the BootLoader region from the APP operation region, does not influence the charging equipment to continue to carry out normal work through the APP operation region, and then stores the upgrading data in the APP backup region of the charging equipment instead of directly storing in the APP operation region, so that the newly received upgrading data can be prevented from erasing the old version upgrading data originally in the APP operation region. In this application, charging equipment enters the BootLoader area from the APP operation area through a first operation, and detects that the APP backup area has the upgrade data, and then moves the upgrade data to the APP operation area and utilizes the upgrade data to perform firmware upgrade, so that the scheme can realize the remote upgrade of the charging equipment under the condition that the normal work of the charging equipment is not influenced.
In a possible implementation manner of the present application, in the process of moving the upgrade data to the APP running region, the old version upgrade data originally stored in the APP running region is deleted, and then the upgrade data is moved to the APP running region.
In a possible implementation manner of the present application, in the process of moving the upgrade data to the APP running region, the upgrade data may be moved to the APP running region first, and then the old version upgrade data originally stored in the APP running region is deleted, or the old version upgrade data originally stored in the APP running region is set to an unavailable state.
In a possible implementation manner of the present application, before storing the upgrade data in the APP backup area of the charging device, the method provided in the embodiment of the present application further includes: and the charging equipment checks whether the chip model carried in the upgrade data is matched with the chip model of the charging equipment or not in the BootLoader area and/or whether the upgrade data is complete or not. In the method, the BootLoader area of the charging equipment needs to determine that the received complete upgrade data is received, and the upgrade data can be applied to the charging equipment, so that the change of the data in the transmission process can be detected, the error of the transmission data is prevented, or the transmission data is incomplete, and the reliability of the transmission data is ensured.
In a possible implementation manner of the present application, in an APP running region running process of a charging device, before determining to upgrade firmware of the charging device, the method provided in an embodiment of the present application further includes: the charging equipment runs the BootLoader area and determines whether the APP running area has the application program. In the case where there is no application program in the APP running area, the charging device continues to run the BootLoader area to wait for upgrade data from the mobile device, the application program representing a program that performs work for the charging device. And under the condition that the application program exists in the APP operation area, the charging equipment enters the APP operation area from the BootLoader area.
In a possible implementation manner of the present application, in a case that the charging device enters the BootLoader area, the method provided in the embodiment of the present application further includes: the method for detecting that the charging equipment enters the BootLoader area is a first operation or a second operation. And under the condition that the mode that the charging equipment enters the BootLoader area is the second operation, the charging equipment detects whether the APP running area has the application program in the BootLoader area again.
In one possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the charging equipment receives an upgrading instruction, and the upgrading instruction is used for indicating upgrading of the firmware. According to the upgrading instruction, the charging equipment updates the first flag bit in the APP operation area to a first indicator, and the first indicator is used for indicating upgrading of the firmware. And under the condition that the APP is in the operation area, updating a second flag bit in the BootLoader area of the charging equipment to a second indicator, wherein the second indicator indicates that the APP is in the operation area. And under the condition that the upgrade data is stored in the APP backup area, the charging equipment updates a third flag bit in the BootLoader area to a third indicator, wherein the third indicator indicates that the APP backup area stores the upgrade data.
In one possible implementation manner of the present application, the method provided in the embodiment of the present application further includes: the BootLoader area of the charging device further stores a fourth flag bit, and the fourth flag bit is used for indicating that the mode of the charging device entering the BootLoader area is the first operation or the second operation. Determining that a first operation of a charging device enters a BootLoader area from an APP operation area, and detecting that an APP backup area has upgrade data, including: the charging equipment enters a BootLoader area from the APP operation area, and acquires a fourth zone bit and a third zone bit from the BootLoader area. And under the condition that the fourth zone bit is a fourth indicator and the third zone bit is a third indicator, the charging equipment determines that the charging equipment enters the BootLoader region from the APP operation region through the first operation, and detects that the APP backup region has upgrade data, wherein the fourth indicator is used for indicating that the mode that the charging equipment enters the BootLoader region is the first operation. The charging equipment stores the flag bit, so that the flag bit of the charging equipment can be changed only through a special indicator, or the current states of different areas are represented through different indicators. And the flag bit is updated to a corresponding indicator, so that the charging equipment needs to update the firmware through the preset indicator, and the confusion of the program is avoided.
In a possible implementation manner of the present application, the charging device obtains upgrade data of a firmware of the charging device in a background manner, and the method provided in an embodiment of the present application further includes: the charging device acquires the upgrading data of the firmware from the mobile device through the Bluetooth communication connection between the charging device and the mobile device. Or the charging equipment acquires the upgrading data of the firmware from the mobile equipment through the serial communication connection between the charging equipment and the mobile equipment.
In a second aspect, an embodiment of the present application provides a device for firmware upgrade, where the device is applied to a charging device, a control module of the charging device has an APP share area, an APP running area, and a BootLoader area, and the device for firmware upgrade may implement the method in the first aspect or any possible implementation manner of the first aspect, and therefore may also implement beneficial effects in the first aspect or any possible implementation manner of the first aspect. The firmware upgrading apparatus may be a charging device, or may be an apparatus supporting the charging device to implement the method in the first aspect or any possible implementation manner of the first aspect, for example, a chip or a control circuit applied in the charging device. The firmware upgrading device can realize the method through software, hardware or corresponding software executed by hardware.
As an example, an embodiment of the present application provides an apparatus for firmware upgrade, where the apparatus for firmware upgrade is a charging device or a chip applied in the charging device, and the apparatus for firmware upgrade includes: the device comprises an obtaining unit, a first processing unit, a second processing unit and an upgrading unit, wherein the obtaining unit is used for obtaining upgrading data of firmware from the mobile device in a background mode under the condition that the upgrading of the firmware of the charging device is determined in the operation process of an APP operation area of the charging device. The first processing unit is used for storing the upgrading data in an APP backup area of the charging equipment. And the second processing unit is used for moving the upgrade data to the APP operation area under the condition that the charging equipment is determined to enter the BootLoader area from the APP operation area through the first operation and the APP backup area is detected to have the upgrade data. And the upgrading unit is used for upgrading the firmware by utilizing the upgrading data in the APP operation area.
In a possible implementation manner of the present application, before storing the upgrade data in the APP backup area of the charging device, the first processing unit is further configured to check the upgrade data in a BootLoader area in the charging device.
In a possible implementation manner of the present application, the obtaining unit is further configured to continue to run the BootLoader area when there is no application program in the APP running area, so as to wait for upgrade data from the mobile device.
In a possible implementation manner of the present application, the upgrading unit is further configured to, when the charging device performs the second operation, enter the BootLoader area, and detect whether the firmware of the charging device needs to be upgraded again.
In a third aspect, an embodiment of the present application provides a charging device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the computer program is executed by the processor, the charging device implements a method for upgrading firmware as described in any one of the possible implementation manners of the first aspect to the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program or an instruction is stored, and when the computer program or the instruction runs on a computer, the computer is caused to execute a firmware upgrade method as described in any one of the possible implementation manners of the first aspect to the first aspect.
In a fifth aspect, embodiments of the present application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform the first aspect or one of the firmware upgrade methods described in the various possible implementations of the first aspect.
In a sixth aspect, embodiments of the present application provide a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement the first aspect or the firmware upgrade method described in the various possible implementations of the first aspect. The communication interface is used for communicating with other modules outside the chip.
Drawings
Fig. 1 is a schematic diagram of a firmware upgrading system provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of a charging apparatus 100 according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of a method for upgrading firmware according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an apparatus for upgrading firmware according to an embodiment of the present disclosure.
Detailed Description
As shown in fig. 1, fig. 1 shows a schematic diagram of a firmware upgrade system provided in an embodiment of the present application, where the system includes: charging device 100, mobile device 200.
Optionally, the system may further include: the server 300, the server 300 is used to provide upgrade data of the firmware of the charging apparatus 100.
As an example, the charging device 100 in the embodiment of the present application may provide a charging service for the mobile device 200. For example, the charging device 100 may be a charging post or a charging dock, and the mobile device 200 may be a robot. Such as a cleaning robot, a delivery robot, etc., and the server 300 generally establishes a communication connection with the mobile device 200, and in practice, the server 300 stores a firmware upgrade update version therein, and can transmit upgrade data to the mobile device 200.
The communication module 110 in the charging device 100 may establish a communication connection, such as a bluetooth connection or a serial communication connection, with the communication module 210 in the mobile device 200, which is not limited in this embodiment of the present application.
The communication module 210 in the mobile device 200 may establish a wireless communication connection, such as a 4G connection or a WIFI connection, with the server 300, which is not limited in this embodiment.
Alternatively, as shown in fig. 2, the charging apparatus 100 includes: a communication module 110 and a control module 120. Wherein the communication module 110 is connected to the control module 120. The communication module 110 may be a wireless communication module, such as a bluetooth communication module, or a wired communication module, such as a serial communication module. The communication module 110 of the charging device 100 may establish a communication connection with a communication module of another device (such as the communication module 210 of the mobile device 200), where the communication connection may be a wired communication connection or a wireless communication connection.
As an example, in the embodiment of the present application, the control module 120 may be run in a memory chip in a Micro Controller Unit (MCU) in the charging device 100. Optionally, the Memory chip may be a Flash Memory (Flash) or a Static Random-Access Memory (SRAM), which is not limited in this embodiment of the present application.
As an example, the control module 120 may be divided into three regions, as shown in FIG. 1, including: a BootLoader area 121, an APP running area 122, and an APP backup area 123. It should be noted that the regions mentioned in the embodiments of the present application may be one type, and/or multiple types of programs, and may also be regions containing one type, and/or multiple types of programs.
In this embodiment, in order to enable the control module 120 to respond to the remote upgrade, a BootLoader area 121 is preset in the control module 120.
As an example, the BootLoader area 121 stores a boot program. The boot program may be executed before the application program in the APP execution region 122 after the first operation or the second operation of the charging device 100, and whether the program exists in the APP execution region 122 and the APP backup region 123 is detected. The boot program may also be used to receive upgrade data from the mobile device and to store the upgrade data in the APP backup area 123. The boot program may also be used to verify the integrity of the upgrade data. The boot program may also be used to verify the manner of operation of the charging device 100.
For example, the first operation in the embodiment of the present application may be a soft reset operation, and the second operation may be a reset operation of a power-up. The soft reset is usually a series of instructions to emulate the hardware reset function, and alternatively, the soft reset operation may be to define a function pointer to point the address to absolute address 0. The reset operation of the power-on is to give a reset signal to the reset terminal when the chip is powered on so as to indicate that the processor does not work in the power-on process, so that the situations of data errors and the like during operation are avoided.
As an example, the APP running area 122 stores an application program and an upgrade program. Among them, the application program is used to perform normal operation of the charging apparatus 100. It should be explained that the application program is an original firmware program in the charging device 100, and the application program is responsible for the normal operation of the charging device when the charging device receives the upgrade data of the firmware. The upgrade program is used to detect whether the firmware of the charging apparatus 100 needs to be upgraded. The upgrade program may also receive upgrade instructions issued by the mobile device. The upgrade program may also upgrade the firmware of the charging apparatus 100 using the upgrade data copied from the APP backup area 123.
As an example, the APP backup area 123 may be used to store upgrade data of firmware received by the BootLoader area 121, and it is understood that the upgrade data of firmware includes data for upgrading firmware.
Optionally, the mobile device 200 comprises: the device comprises a communication module and a processing module. The communication module may support the mobile device 200 to establish a communication connection with other devices (e.g., the charging device 100, the server 300). The processing modules are used to enable mobile device 200 to perform the relevant processing steps.
The communication module 110 of the charging device 100 may be used to support connection and communication between the charging device 100 and the mobile device 200 through wireless or wired communication technologies, for example, as shown in connection with fig. 1, the charging device 100 and the mobile device 200 may implement data exchange through respective communication modules.
As an example, the communication module of the charging device 100 may be a bluetooth chip, or may be a physical interface with a serial bus. The communication module of the mobile device 200 may be a bluetooth chip or a serial bus physical interface. Of course, the communication module of the mobile device 200 may further include a 4G chip or a WIFI chip to support data interaction between the mobile device 200 and the server 300. The embodiment of the present application does not limit this.
The charging device 100 can pair with the bluetooth chip of the charging device 100 through the bluetooth chip and establish a wireless communication connection, so as to implement wireless communication, service processing and data transmission between the charging device 100 and the mobile device 200 through the wireless connection. In general, a Bluetooth chip may support Basic Rate (BR)/Enhanced Rate (EDR) Bluetooth and Bluetooth Low Energy (BLE).
Of course, the Communication module may be a bluetooth chip, a Near Field Communication (NFC) chip, or a WiFi chip, which is not limited in this embodiment of the present invention.
The charging device 100 can be paired with the bluetooth chip of the charging device 100 through the bluetooth chip and establish wireless communication connection, and the charging device 100 and the mobile device 200 can also be connected through wired communication through serial bus physical interfaces each other. Specifically, for example, the charging device 100 is a charging pile, the mobile device 200 is a robot, a serial port bus physical interface is arranged at a butt joint of the charging pile and the robot, and after the robot and the charging pile are in butt joint, the robot and the charging pile can be connected through serial port bus physical interface.
It can be understood that serial port communication connection between the charging pile and the robot through the physical interface with the serial port bus is a wired communication mode. As an example, the serial communication connection may be a wired communication connection between a Central Processing Unit (CPU) in the charging device and the charging device 100 through a serial bus physical interface according to a set serial communication protocol, so as to perform data transmission. Optionally, according to different level standards used in the physical layer, the serial communication protocol may be an RS-232 standard or a TTL standard, which is not limited in this embodiment of the present application.
In the related art, when board card firmware upgrading is performed on a charging pile of a robot, a firmware program in a Flash memory (Flash) chip of an MCU is usually upgraded, and a BootLoader program in the Flash memory chip is used to upgrade and guide the firmware upgrading. Because there is only one APP area, the original firmware program in the flash memory chip needs to be covered with the new firmware program, thereby completing the firmware upgrade. Therefore, in the firmware upgrading process, the current working state of the charging pile is interrupted, and communication connection with the robot is recovered again until the firmware upgrading is completed. In addition, due to the upgrading operation, the original firmware program may be covered due to data errors of firmware upgrading, so that the charging pile cannot work. Based on the problems in the related art, the application provides a scheme for remotely upgrading the firmware of the charging pile control board under the condition that the normal work of the charging pile is not influenced.
In the embodiment of the present application, a specific structure of an execution main body of a method for upgrading firmware is not particularly limited in the embodiment of the present application, as long as communication can be performed by a method for upgrading firmware according to the embodiment of the present application by running a program in which a code of a method for upgrading firmware of the embodiment of the present application is recorded. For example, the execution subject of the firmware upgrade method provided by the embodiment of the present application may be a functional module capable of calling a program and executing the program in the charging apparatus 100, or a device, such as a chip, applied to firmware upgrade in the charging apparatus 100. The execution main body of the firmware upgrading method provided by the embodiment of the present application may be a functional module capable of calling a program and executing the program in the charging apparatus 100, or a device, such as a chip, applied to firmware upgrading in the charging apparatus 100. This is not limited in this application. The following embodiments describe the implementation subject of a firmware upgrading method as the charging device 100 and the mobile device 200.
As shown in fig. 3, fig. 3 is a schematic flowchart illustrating a method for upgrading firmware provided in an embodiment of the present application, where the method is applied to a charging device, and includes:
As an example, the communication connection established between the charging apparatus 100 and the charging apparatus 100 may be a wireless communication connection or a wired communication connection. For example, the wireless communication connection may be a bluetooth connection. For example, the wired communication connection may be a serial communication connection implemented by a physical interface having a serial bus.
As an example, the wireless communication connection established between the charging device 100 and the server 300 may be a WIFI connection, which is not limited in this embodiment.
For example, the charging device 100 according to fig. 2 in this embodiment may be the charging device 100 shown in fig. 1, the charging device 100 may be the mobile device 200 shown in fig. 1, and the server 300 may be the server 300 shown in fig. 1, which is not limited in this embodiment.
In the background mode in this application, that is, in the running process of the APP running area 122, the BootLoader area 121 receives new firmware (i.e., upgrade data of the firmware) from the background without affecting the normal operation of the charging device 100, and the charging device 100 does not need to jump to the BootLoader area 121. For example, the charging device 100 may obtain the upgrade data of the firmware of the charging device 100 from the charging device 100 in a background manner.
As an example, the charging apparatus 100 may acquire upgrade data of firmware from the server 300 through a wireless communication connection established with the server 300. The upgrade data of the firmware applied to the charging apparatus 100 may be any data that can provide the charging apparatus 100 with an optimized or new function.
As an example, the upgrade data of the firmware may solve the problem of compatibility in the charging apparatus 100, thereby optimizing the operation function of the charging apparatus 100. As an example, the upgrade data of the firmware may optimize an interactive function established between the charging apparatus 100 and the charging apparatus 100. Alternatively, the interactive function may be data communication between the charging apparatus 100 and the charging apparatus 100, real-time monitoring of the state of the robot, or the like.
Optionally, after the charging device 100 acquires the upgrade data of the firmware, the charging device 100 stores the upgrade data of the firmware in the APP backup area 123 of the charging device 100. This may prevent the received upgrade data from erasing the old version of the upgrade data originally stored in the APP running region 122 during the process of receiving the upgrade data. Therefore, this can be done to ensure that the received upgrade data of the firmware does not affect the normal operation of the application program in the APP operating region 122.
It is understood that the first operation is that the charging device 100 (such as the MCU) sends a reset instruction to the BootLoader area 121 through a software program, so that the charging device 100 enters the BootLoader area 121.
It can be understood that, when the charging device 100 enters the BootLoader area 121 from the APP running area 122 through the first operation and detects that the APP backup area 123 has the upgrade data, both of them are implemented, the boot program of the BootLoader area 121 moves the upgrade data to the APP running area 122. If one of the two cases is not implemented, the boot program of the BootLoader area 121 will not move the upgrade data to the APP running area 122.
As a possible implementation manner, the BootLoader area 121 is configured to erase an application program (i.e., an original firmware program) in the APP running area 122 by the charging device 100, and transfer upgrade data in the APP backup area 123 to the APP running area 122.
As a possible implementation manner, the BootLoader area 121 changes the application program in the APP running area 122 to an inoperable state by the charging device 100, and optionally, the inoperable state may be data annotation, or other methods that may make the application program inoperable.
As an example, an upgrade program is stored in the APP operating area 122, and the upgrade program may upgrade firmware of the charging apparatus 100 by using upgrade data moved from the APP backup area 123 into the APP operating area 122.
It should be explained that the upgrade data cannot be directly applied to the APP running region 122, and a new application program (such as new firmware) needs to be formed in the APP running region 122 to perform normal operation.
In the embodiment of the invention, the method comprises the following steps: the charging apparatus establishes a communication connection with the charging apparatus 100. In the running process of the APP running area 122 of the charging device, when the charging device determines to upgrade the firmware of the charging device, the charging device acquires upgrade data of the firmware of the charging device from the charging device 100 in a background manner. The charging device stores the upgrade data of the firmware in the APP backup area 123 of the charging device. When it is determined that the charging device enters the BootLoader area 121 from the APP running area 122 through the first operation and it is detected that the APP backup area 123 has the upgrade data, the charging device moves the upgrade data to the APP running area 122. The charging device upgrades the firmware of the charging device with the upgrade data in the APP operating area 122. Through the technical scheme, the remote upgrading method and the remote upgrading device are used for realizing the remote upgrading of the firmware of the charging pile control panel under the condition that the normal work of the charging pile is not influenced.
In a normal case, the charging device 100 is normally operated in the BootLoader area 121 when the charging device 100 starts to operate, and in a case that the charging device 100 is in the BootLoader area 121, the charging device 100 may determine that the APP operation area 122 of the charging device 100 does not store an application program. In the case where the APP operating region 122 of the charging device 100 does not store the application program and the APP operating region 122 of the charging device 100 stores the application program, the subsequent steps performed by the charging device 100 are generally different, and will be described separately as follows:
in one possible embodiment of the present application, before the charging device 100 executes step 402, in a case where the BootLoader area 121 in the charging device 100 determines that the APP running area 122 does not store an application program, the charging device 100 continues to run the BootLoader area 121 to wait for upgrade data from the charging device 100. It can be understood that, since there is no application program in the APP operating area 122 of the charging device 100, the charging device 100 itself cannot operate normally, and therefore, the charging device 100 is in the BootLoader area 121 at this time, and does not need to jump to the APP operating area 122. Until the charging device 100 detects that there is upgrade data, it is determined and the boot program in the BootLoader area 121 is responsible for receiving the upgrade data transmitted from the charging device 100.
For example, after receiving the upgrade data sent from the charging device 100, the BootLoader area 121 may store the upgrade data of the firmware in the APP backup area 123. In a case where it is determined that the charging device 100 enters the BootLoader area 121 and it is detected that the APP backup area 123 has the upgrade data, the charging device 100 moves the upgrade data to the APP running area 122. The charging apparatus 100 upgrades the firmware with the upgrade data in the APP operating region 122.
In a possible embodiment of the present application, in a case that the charging apparatus 100 executes step 402, if the upgrade program in the APP operating area 122 of the charging apparatus 100 determines that the firmware of the charging apparatus 100 does not need to be upgraded, the charging apparatus 100 continues to operate normally through the application program in the APP operating area 122.
In one possible embodiment of the present application, the charging device 100 determining that the firmware upgrade to the charging device 100 can be implemented by: the charging device 100 determines whether the firmware needs to be upgraded according to the first flag bit stored in the APP running region 122. As an example, the first flag bit is a first indicator, and the charging apparatus 100 determines that a firmware upgrade of the charging apparatus 100 is required.
As another example, in a case where the first flag bit is not the first indicator, such as the fifth indicator, then the charging apparatus 100 determines that a firmware upgrade to the charging apparatus 100 is not required. For example, the first indicator may be a sequence of at least one bit, such as 0 or 00, or 01. In the case that the first flag is not the first indicator, the first flag may also be a sequence of at least one bit, such as 1, 10, or 11.
It should be noted that, in the following embodiments, the relationship between the flag bit and the indicator may be a sequence formed by at least one bit, which are all according to the above description and will not be described in detail later.
In one possible implementation manner of the present application, the charging device 100 determines that the firmware upgrade to the charging device 100 may be implemented by: the charging apparatus 100 acquires the upgrade instruction, and the charging apparatus 100 determines to upgrade the firmware of the charging apparatus 100 according to the upgrade instruction. Alternatively, the upgrade instruction may be provided to the charging apparatus 100 by the charging apparatus 100, or may be input to the charging apparatus 100 by the user, for example, the charging apparatus 100 has an upgrade button, and in the case that the user determines that the firmware of the charging apparatus 100 needs to be upgraded, the user may trigger the upgrade button to determine that the firmware of the charging apparatus 100 is upgraded by the charging apparatus 100. Of course, alternatively, in a case where the charging device 100 may communicate with the server 300, if the server 300 detects that there is an updated version of the firmware of the charging device 100, the server 300 may send an upgrade instruction to the charging device 100 to trigger the charging device 100 to determine the firmware upgrade to the charging device 100. Optionally, in a case where the charging device 100 receives an upgrade instruction from the server 300, the charging device 100 may further send a prompt message to prompt the user whether to upgrade the firmware of the charging device 100, and in a case where an instruction agreeing to upgrade input by the user is detected, the charging device 100 determines to upgrade the firmware of the charging device 100. In the case where it is detected that the instruction input by the user does not agree with the upgrade, the charging apparatus 100 determines not to upgrade the firmware of the charging apparatus 100.
As an example, the prompting message sent by the charging device 100 may be a prompting message displayed on a display interface thereof, a prompting message sent in a voice playing manner, or a prompting message sent to the charging device 100 connected to the charging device 100 in a communication manner.
In a possible embodiment of the present application, after the charging device 100 acquires the upgrade instruction, the method provided in the embodiment of the present application may further include: the charging apparatus 100 updates the first flag bit stored in the APP operating region 122 to the first indicator. It is understood that, in a case where the charging apparatus 100 does not acquire the upgrade instruction, the first flag bit in the APP operating region 122 is a fifth indicator, that is, is used to indicate that the upgrade is not required.
In one possible implementation manner of the present application, before the charging device 100 acquires the upgrade data of the firmware of the charging device 100 from the charging device 100 in a background manner, the charging device 100 may acquire the upgrade data of the firmware from the server 300 if it is determined that the firmware of the charging device 100 needs to be upgraded.
In one possible implementation manner of the present application, the step 402 may be implemented by: the charging apparatus 100 acquires upgrade data of firmware from the charging apparatus 100 while maintaining a communication connection with the charging apparatus 100.
It is understood that the case where the charging apparatus 100 maintains communication with the charging apparatus 100 may be where the charging apparatus 100 is connected through bluetooth communication with the charging apparatus 100.
Alternatively, the charging apparatus 100 may obtain the upgrade data of the firmware from the charging apparatus 100 while maintaining the serial communication connection with the charging apparatus 100. For example, the charging device 100 may be connected to the charging device 100 in a serial communication manner, perform wired communication according to a set communication standard, and acquire firmware upgrade data from the charging device 100, in a case where the charging device 100 is normally operated in a state of establishing a bluetooth communication connection. This can achieve stability of data transmission.
In one possible embodiment of the present application, in order to prevent that the upgrade data received by the charging device 100 has a matching error, or the upgrade data is incomplete, and the content of the upgrade data is incorrect, resulting in an upgrade failure, the method provided in this embodiment of the present application may further include, before the charging device 100 stores the upgrade data in the APP backup area 123 of the charging device 100: the charging apparatus 100 verifies the upgrade data in the BootLoader area 121. Therefore, the upgrade data stored in the APP backup area 123 in this case is typically the upgrade data that passes the verification.
As a possible implementation manner, the charging device 100 checks the upgrade data in the BootLoader area 121, specifically: the charging device 100 checks in the BootLoader area 121 whether the chip model carried in the upgrade data matches the chip model of the charging device 100, and/or whether the upgrade data is complete. Therefore, it can be ensured that the BootLoader area 121 of the charging device 100 needs to determine that the received complete upgrade data is complete, and the upgrade data can be applied to the charging device 100, so that the change of the data in the transmission process can be detected, a data transmission error is prevented, or the transmission data is incomplete, and the reliability of the transmission data is ensured.
For example, verifying whether the chip model carried in the upgrade data matches the chip model of the charging device 100 may include: the version information of the upgrade data is acquired, where the version information may include a version number of the upgrade data, a chip model required by the upgrade data, and the like, the chip model of the charging device 100 is acquired, and it is determined whether the model required by the upgrade data matches the chip model of the charging device 100, where the chip models of the two are suitable, and the current model of the charging device 100 may meet the requirement that the upgrade data operates in the charging device 100.
For example, the specific steps of the charging device 100 verifying whether the upgrade data is complete may include the following:
and 1, checking and determining the integrity of each upgrading data packet in the received upgrading data.
Case 2, verify and determine the integrity of the entire upgrade data.
Optionally, the integrity of each upgrade data packet is checked and determined, in practice, if it is checked that the upgrade data packet a is not received, the charging device 100 sends the indication information of losing the upgrade data packet a to the charging device 100, and the charging device 100 resends the upgrade data packet a to the charging device 100, optionally, the number of resending may be one or three.
Optionally, the integrity of the entire upgrade data is checked and determined. This ensures that the charging device 100 receives the unmodified upgrade data, and ensures the secure transmission of the upgrade data of the firmware.
It should be noted that the process of storing the upgrade data in the APP backup area 123 of the charging device 100 by the BootLoader area 121 is executed in the background, and in the case that the charging device 100 is operating normally, the upgrade data of the firmware is stored in the APP backup area 123 without affecting the application program stored in the APP operating area 122.
In a possible embodiment of the present application, after the charging device 100 stores the upgrade data of the firmware in the APP backup area 123 of the charging device 100, the method provided in the embodiment of the present application may further include: the charging apparatus 100 may update the third flag bit stored in the BootLoader area 121 to the third indicator. The third indicator is used to indicate that the APP backup area 123 stores the upgrade data of the firmware. Of course, in the case where the BootLoader area 121 does not have the third flag bit, the charging device 100 may create the third flag bit in the BootLoader area 121 and then assign the third flag bit as the third indicator. Of course, in the case that the charging apparatus 100 does not store the upgrade data of the firmware in the APP backup area 123 of the charging apparatus 100, the third flag is generally used to indicate that the upgrade data of the firmware is not stored in the APP backup area 123. Therefore, after the subsequent charging device 100 jumps from the APP running area 122 to the BootLoader area 121, it is convenient to identify whether the APP backup area 123 stores the upgrade data of the firmware according to the third flag bit.
In one possible embodiment of the present application, after determining that the charging device 100 enters the BootLoader area 121 from the APP running area 122 through the first operation, the method provided in the embodiment of the present application may further include: charging equipment 100 enters BootLoader area 121 from APP running area 122, and charging equipment 100 determines whether the reset mode of charging equipment 100 is the first operation or the second operation according to the fourth flag bit stored in BootLoader area 121. As an example, in a case where the fourth flag bit is updated to the fourth indicator, the charging apparatus 100 determines that the charging apparatus 100 enters the BootLoader area 121 from the APP running area 122 through the first operation.
It can be understood that, in a normal case, the charging device 100 is in the APP running region 122 during normal operation, and the second operation is that the charging device 100 performs reset at the moment of powering on, so as to enter the BootLoader region 121. The first operation is that the charging apparatus 100 sends a reset instruction to the BootLoader area 121 through a software program, so that the charging apparatus 100 enters the BootLoader area 121.
In the case where the charging apparatus 100 performs the second operation, when the charging apparatus 100 enters the BootLoader area 121, it is redetected whether the firmware of the charging apparatus 100 needs to be upgraded. It is understood that if the reset operation is determined to be the second operation, step 402 is performed again. This is done to prevent the second operation from being performed during the upgrade data transfer, thereby making the transfer data incomplete.
It is to be understood that, in the case where it is determined that the charging apparatus 100 enters the BootLoader area 121 from the APP running area 122 through the first operation, and it is detected that the APP backup area 123 has the upgrade data, the charging apparatus 100 enters the BootLoader area 121, and the application program in the APP running area 122 stops running.
In a possible embodiment of the present application, in a case that it is determined that the charging device 100 enters the BootLoader area 121 from the APP running area 122 through the first operation, and it is detected that the APP backup area 123 has upgrade data, the method provided in the embodiment of the present application may further include: the charging device 100 enters the BootLoader area 121, and acquires the fourth flag bit and the third flag bit from the BootLoader area 121. In a case that the fourth flag bit is the fourth indicator and the third flag bit is the third indicator, the charging apparatus 100 moves the upgrade data to the APP operating region 122.
It should be noted that, in the above embodiment, the flag bit needs to be obtained, so that the flag bit of the charging apparatus 100 needs to be changed by a special indicator, or the current status of different areas is represented by different indicators.
It should be explained that, in the above embodiment, the flag bit needs to be updated to the corresponding indicator, so that the charging apparatus 100 needs to update the firmware by using the corresponding indicator, thereby avoiding confusion of the program.
It is understood that each device, such as the charging device 100, includes corresponding structures and/or software modules for performing each function in order to implement the functions described above. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed in hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The charging device 100 according to the above method may divide the functional units, for example, each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit. It should be noted that, in the embodiment of the present application, the division of the unit is schematic, and is only one logic function division, and when the actual implementation is realized, another division manner may be provided.
The method of the embodiment of the present application is described above with reference to fig. 1 to 3, and the apparatus for performing the method provided by the embodiment of the present application is described below. Those skilled in the art will understand that the method and the apparatus may be combined and referred to each other, and the apparatus for firmware upgrade provided in the embodiments of the present application may perform the steps performed by the charging device 100 and the charging device 100 respectively in the method for firmware upgrade described above.
In the case of using an integrated unit, fig. 4 shows a firmware upgrading apparatus according to the above embodiment, where the firmware upgrading apparatus may be the charging device 100 or an apparatus applied in the charging device 100, such as a chip or a processing circuit, and the firmware upgrading apparatus may include: an acquisition unit 501, a first processing unit 502, a second processing unit 503, and an upgrade unit 504.
In an alternative implementation, the firmware upgrading apparatus may further include a storage unit for storing program codes and data of the firmware upgrading apparatus.
In one example, the firmware upgrading apparatus is the charging apparatus 100, or a chip applied to the charging apparatus 100. An obtaining unit 501, configured to obtain, in a background manner, upgrade data of the firmware from the charging device 100 when it is determined that the firmware of the charging device 100 is upgraded in an operation process of the APP operation area 122 of the charging device 100. The first processing unit 502 is configured to store the upgrade data in the APP backup area 123 of the charging apparatus 100. The second processing unit 503 is configured to, when it is determined that the charging device 100 enters the BootLoader area 121 from the APP running area 122 through the first operation and detects that the APP backup area 123 has the upgrade data, move the upgrade data to the APP running area 122. An upgrade unit 504, configured to upgrade the firmware with the upgrade data in the APP running region 122.
In a possible implementation manner, before storing the upgrade data in the APP backup area 123 of the charging device 100, the first processing unit 502 is further configured to check the upgrade data in the BootLoader area 121 in the charging device 100.
In one possible implementation manner, the obtaining unit 502 is further configured to continue to run the BootLoader area 121 in a case where there is no application program in the APP running area 122, so as to wait for upgrade data from the charging device 100.
In one possible implementation manner, the upgrading unit 504 is further configured to, in a case that the charging apparatus 100 performs the second operation, enter the BootLoader area 121, and re-detect whether the firmware of the charging apparatus 100 needs to be upgraded.
The first processing unit 503 and the second processing unit 504 may be processors or controllers, and may be central processing units, general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination comprising one or more microprocessors, a digital signal processor and a microprocessor, or the like. The communication module may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module may be a memory.
Alternatively, the structure of the charging device 100 shown in fig. 2 may further include a memory, which may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disc storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory may be self-contained and coupled to the processor via a communication link. The memory may also be integral to the processor.
The memory is used for storing computer execution instructions for executing the scheme of the application and is controlled by the processor to execute. The processor is used for executing computer execution instructions stored in the memory, so as to realize a firmware upgrading method provided by the following embodiments of the application.
Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
In one aspect, a computer-readable storage medium is provided, having stored therein instructions that, when executed, implement the functions performed by the charging device 100 as in fig. 3.
In one aspect, a computer program product comprising instructions is provided, which when executed, implements the functions performed by the charging device 100 as in fig. 3.
In one aspect, the present embodiment provides a chip, which is applied in the charging device 100, and the chip includes at least one processor and a communication interface, and the communication interface is coupled with the at least one processor, and the processor is configured to execute instructions to implement the functions performed by the charging device 100 in fig. 3.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, special purpose computer, computer network, network appliance, user equipment, or other programmable device. The computer program or instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer program or instructions may be transmitted from one website site, computer, server 300, or data center to another website site, computer, server 300, or data center by wire or wirelessly. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as server 300, a data center, etc. that incorporates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, hard disk, magnetic tape; or optical media such as Digital Video Disks (DVDs); it may also be a semiconductor medium, such as a Solid State Drive (SSD).
While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations may be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include such modifications and variations.
Claims (10)
1. A firmware upgrading method is applied to charging equipment, a control module of the charging equipment is provided with an APP backup area, an APP operation area and a BootLoader area, and the method comprises the following steps:
in the running process of an APP running area of the charging equipment, under the condition that the firmware of the charging equipment is determined to be upgraded, obtaining upgrading data of the firmware in a background mode;
storing the upgrading data of the firmware in the APP backup area of the charging equipment;
when it is determined that the charging equipment enters the BootLoader area from the APP operation area through a first operation and the APP backup area is detected to have the upgrade data, moving the upgrade data to the APP operation area;
and upgrading the firmware by using the upgrading data in the APP operation area.
2. The method of claim 1, wherein before storing the upgrade data in an APP backup area of the charging device, the method further comprises:
and checking whether the chip model carried in the upgrading data is matched with the chip model of the charging equipment or not in the BootLoader area, and/or whether the upgrading data is complete or not.
3. The method of claim 1, wherein during the running of the APP running region of the charging device, before determining to upgrade firmware of the charging device, the method further comprises:
the BootLoader area is operated, and whether the APP operation area has an application program is determined; under the condition that no application program exists in the APP operation area, continuously operating the BootLoader area to wait for upgrade data from mobile equipment, wherein the application program represents a program for executing work for the charging equipment;
and entering the APP operation area from the BootLoader area under the condition that the application program exists in the APP operation area.
4. The method of claim 1, wherein if the charging device enters the BootLoader region, the method further comprises:
detecting whether the mode of the charging equipment entering the BootLoader area is the first operation or the second operation;
and under the condition that the mode that the charging equipment enters the BootLoader area is the second operation, the charging equipment redetects whether the APP running area has an application program in the BootLoader area.
5. The method according to any one of claims 1 to 4, further comprising:
receiving an upgrading instruction, wherein the upgrading instruction is used for indicating upgrading of the firmware;
updating a first flag bit in the APP operation area to a first indicator according to the upgrade instruction, wherein the first indicator is used for indicating upgrading of the firmware; and/or the presence of a gas in the gas,
under the condition that the APP operation area has the application program, updating a second flag bit in the BootLoader area to a second indicator, wherein the second indicator indicates that the APP operation area has the application program; and/or the presence of a gas in the gas,
and under the condition that the upgrade data is stored in the APP backup area, updating a third flag bit in the BootLoader area to a third indicator, wherein the third indicator indicates that the APP backup area stores the upgrade data.
6. The method of claim 5, further comprising:
a fourth flag bit is further stored in the BootLoader area, and the fourth flag bit is used for indicating that the mode of the charging equipment entering the BootLoader area is the first operation or the second operation;
the determining that the charging device enters a BootLoader region from the APP running region through the first operation and detects that the APP backup region has the upgrade data includes:
the charging equipment enters the BootLoader area from the APP operation area, and acquires a fourth zone bit and a third zone bit from the BootLoader area;
and if the fourth flag bit is a fourth indicator and the third flag bit is the third indicator, determining that the charging equipment enters a BootLoader area from the APP running area through the first operation, and detecting that the APP backup area has the upgrade data, wherein the fourth indicator is used for indicating that the charging equipment enters the BootLoader area in a mode of the BootLoader area as the first operation.
7. The method according to any one of claims 1 to 6, wherein the obtaining of the upgrade data of the firmware of the charging device in a background manner includes any one or more of:
the charging equipment acquires the upgrading data of the firmware from the mobile equipment through a Bluetooth communication connection between the charging equipment and the mobile equipment; or the like, or, alternatively,
and the charging equipment acquires the upgrading data of the firmware from the mobile equipment through serial communication connection with the mobile equipment.
8. The device for upgrading the firmware is applied to charging equipment, a control module of the charging equipment is provided with an APP backup area, an APP running area and a BootLoader area, and the method comprises the following steps:
the acquisition unit is used for acquiring the upgrading data of the firmware from the mobile equipment in a background mode under the condition that the firmware of the charging equipment is determined to be upgraded in the running process of the APP running area of the charging equipment;
the first processing unit is used for storing the upgrading data in the APP backup area of the charging equipment;
the second processing unit is used for moving the upgrade data to the APP operation area when the charging equipment is determined to enter the BootLoader area from the APP operation area through a first operation and the APP backup area is detected to have the upgrade data;
and the upgrading unit is used for upgrading the firmware by using the upgrading data in the APP operation area.
9. A charging device, comprising: at least one processor coupled to a communication interface for receiving or transmitting information, the at least one processor configured to execute instructions stored in a memory to perform the method of any of claims 1-7.
10. A computer-readable storage medium having stored thereon instructions which, when executed, implement the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211008511.9A CN115473807A (en) | 2022-08-22 | 2022-08-22 | Firmware upgrading method, equipment, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211008511.9A CN115473807A (en) | 2022-08-22 | 2022-08-22 | Firmware upgrading method, equipment, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115473807A true CN115473807A (en) | 2022-12-13 |
Family
ID=84365923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211008511.9A Pending CN115473807A (en) | 2022-08-22 | 2022-08-22 | Firmware upgrading method, equipment, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115473807A (en) |
-
2022
- 2022-08-22 CN CN202211008511.9A patent/CN115473807A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105912356B (en) | A kind of optical module firmware program on-line upgrading method for supporting version rollback | |
| US9513900B2 (en) | Peripheral device and method for updating firmware thereof | |
| CN109358887B (en) | On-line upgrading method, device and system for single chip microcomputer program | |
| CN105677398A (en) | Universal embedded computer software on-line upgrading method | |
| EP1494119A1 (en) | Network equipment and a method for monitoring the start up of a such an equipment | |
| CN111813428A (en) | Method and device for upgrading terminal firmware, electronic equipment and storage medium | |
| CN109002310A (en) | firmware upgrade method | |
| CN110633091A (en) | Electronic module and software wireless upgrading method thereof | |
| CN112925679A (en) | Firmware upgrading method, nonvolatile memory, computer storage medium and terminal | |
| CN114281394A (en) | Method, system, equipment and medium for fast on-line upgrading program | |
| US20190310842A1 (en) | Method for upgrading firmware of adapter, mobile terminal, and adapter thereof | |
| CN113760332A (en) | Software upgrading method and electronic equipment | |
| CN112181455B (en) | Online upgrading method of microcontroller, microcontroller and storage medium | |
| CN109308186A (en) | A kind of method and terminal of edition upgrading | |
| CN115473807A (en) | Firmware upgrading method, equipment, system and storage medium | |
| CN111552490A (en) | Method for online upgrading electric control system of battery charging and replacing cabinet | |
| CN115098301B (en) | Snapshot generation method and system for stateful application in cloud primary scene | |
| CN106445592A (en) | Long-distance multi-machine program upgrading method based on WIFI and CAN bus | |
| US11586504B2 (en) | Electronic apparatus and boot method thereof | |
| CN110457058A (en) | Control node online upgrading method, apparatus, host computer, system and electronic equipment | |
| CN114968301A (en) | Program updating method and system based on serial port communication | |
| CN112925546B (en) | Multistage verification method and system for preventing vehicle-mounted ECU from refreshing errors | |
| CN111813597A (en) | Air conditioner | |
| CN117311752A (en) | System upgrading method and device, electronic equipment and readable storage medium | |
| CN115914172A (en) | Method and device for modifying equipment address based on Bluetooth and electronic equipment |
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 |