CN114020283A - Firmware burning method, burning circuit, device, equipment and readable storage medium - Google Patents
Firmware burning method, burning circuit, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN114020283A CN114020283A CN202111164916.7A CN202111164916A CN114020283A CN 114020283 A CN114020283 A CN 114020283A CN 202111164916 A CN202111164916 A CN 202111164916A CN 114020283 A CN114020283 A CN 114020283A
- Authority
- CN
- China
- Prior art keywords
- burning
- connector
- firmware
- voltage
- dongle
- 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
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000001012 protector Effects 0.000 claims abstract description 70
- 238000004891 communication Methods 0.000 claims abstract description 64
- 238000006243 chemical reaction Methods 0.000 claims abstract description 47
- 238000012544 monitoring process Methods 0.000 claims abstract description 32
- 238000004590 computer program Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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/61—Installation
Abstract
The application discloses a firmware burning method, a burning circuit, a burning device, equipment and a readable storage medium, wherein the method comprises the following steps: monitoring a connector in the burning circuit; after the fact that the software protector is inserted into the connector is monitored, the communication connection between the software protector and the target device is disconnected; and burning firmware to a voltage conversion chip in the burning circuit by using the software protector. And monitoring a connector in the burning circuit. When the software protector is detected to be inserted into the connector, the communication connection between the software protector and the target device is directly disconnected. I.e. only the communication connection between the dongle and the voltage conversion chip can be reserved, directly avoiding the I2C communication collision from the physical hardware point of view. Then, the firmware is burned on the voltage conversion chip by using the software protector, and the success rate of burning the firmware can be effectively improved due to the fact that I2C communication conflict is avoided.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a firmware burning method, a burning circuit, a burning apparatus, a device, and a readable storage medium.
Background
With the development of artificial intelligence and big data, the demand on a server is increasing, wherein an onboard power supply is an indispensable part of the server. The requirements for power supply software and hardware for board-mounted power supplies, in particular for CPU and DIMM (Dual-Inline-Memory-Modules) parts, are increasing. A mature on-board power supply is required to undergo multiple test verifications, which often involve a VR FW (voltage regulation firmware) version of burn-in upgrade and a later upgrade.
However, when a dongle (software protector) is used for online burning of VR FW at present, the VR FW cannot be burned in frequently, and the VR FW can be successfully burned in many times.
In summary, how to effectively solve the VR FW burning success rate and other problems is a technical problem that needs to be solved urgently by those skilled in the art.
Disclosure of Invention
The application aims to provide a firmware burning method, a burning circuit, a burning device, firmware burning equipment and a readable storage medium, and improve the VR FW burning success rate.
In order to solve the technical problem, the application provides the following technical scheme:
a firmware burning method comprises the following steps:
monitoring a connector in the burning circuit;
after the fact that the dongle is inserted into the connector is monitored, disconnecting the communication connection between the dongle and a target device;
and burning firmware to a voltage conversion chip in the burning circuit by using the software protector.
Preferably, the method further comprises the following steps:
and if the fact that the software protector is pulled out is monitored, the communication connection between the software protector and the target device is recovered.
Preferably, disconnecting the dongle from communication with the target device comprises:
turning off the operating voltage of the target I2C device by using a switch; wherein the target I2C device powers the target device.
Preferably, monitoring the connector in the burning circuit includes:
monitoring the voltage value of the connector;
determining that the dongle is inserted into the connector if the voltage value increases from a first voltage to a second voltage;
and if the voltage value is reduced from the second voltage to the first voltage, determining that the dongle is unplugged from the connector.
Preferably, the monitoring the voltage value of the connector includes:
and monitoring the voltage value of the connector by utilizing an automatic switching module connected with the connector.
A burning circuit, comprising:
the device comprises a connector, an automatic switching module, a voltage conversion chip and a target device;
the connector is connected with the automatic switching module;
the automatic switching module is used for monitoring the connector, and disconnecting the communication connection between the software protector and the target device after the software protector is inserted into the connector, so that the software protector can burn firmware on the voltage conversion chip.
Preferably, the automatic switching module is provided with a switch, and the switch is used for turning off the working voltage of the target I2C device; the target I2C device powers the target device.
A firmware burning device, comprising:
the connection monitoring module is used for monitoring a connector in the burning circuit;
the access control module is used for disconnecting the communication connection between the software protector and the target device after the software protector is monitored to be inserted into the connector;
and the firmware burning module is used for burning firmware to the voltage conversion chip in the burning circuit by using the software protector.
An electronic device, comprising:
a memory for storing a computer program;
and the processor is used for realizing the steps of the firmware burning method when the computer program is executed.
A readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the firmware burning method described above.
Monitoring a connector in a burning circuit by applying the method provided by the embodiment of the application; after the fact that the software protector is inserted into the connector is monitored, the communication connection between the software protector and the target device is disconnected; and burning firmware to a voltage conversion chip in the burning circuit by using the software protector.
The reason why the software protector is used for burning the firmware of the voltage conversion chip is that when the firmware is burnt to the voltage conversion chip, the I2C communication conflicts, so that the firmware cannot be burnt. Therefore, in the present application, in order to improve the success rate of burning firmware onto the voltage conversion chip, the connector in the burning circuit is first monitored. When the software protector is detected to be inserted into the connector, the communication connection between the software protector and the target device is directly disconnected. I.e. only the communication connection between the dongle and the voltage conversion chip can be reserved, directly avoiding the I2C communication collision from the physical hardware point of view. Then, the firmware is burned on the voltage conversion chip by using the software protector, and the success rate of burning the firmware can be effectively improved due to the fact that I2C communication conflict is avoided.
Accordingly, the embodiment of the present application further provides a recording circuit, a firmware recording device, an apparatus and a readable storage medium corresponding to the firmware recording method, which have the above technical effects and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments or related technologies of the present application, the drawings needed to be used in the description of the embodiments or related technologies are briefly introduced below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flowchart illustrating an implementation of a firmware burning method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a recording circuit according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a recording circuit;
FIG. 4 is a schematic diagram of another recording circuit according to an embodiment of the present application;
FIG. 5 is a schematic diagram illustrating a firmware burning device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating a firmware burning method according to an embodiment of the present application, the method including the following steps:
and S101, monitoring a connector in the burning circuit.
The software protector can be inserted into a connector in the burning circuit, so that communication connection between the software protector and the voltage conversion chip is formed, and firmware can be burnt to the voltage conversion chip through the communication connection software protector. The voltage conversion chip can be any VR which needs firmware burning, such as a CPU VR and a DIMM VR.
In an actual recording circuit, after the dongle is inserted into the connector, not only a communication connection between the dongle and the voltage conversion chip may be formed, but also a communication connection between the dongle and a CPU (processor), a BMC (baseboard management controller), and a CPLD (Complex Programmable Logic Device) may be formed, and the communication connection between the dongle and the CPU, the BMC, and the CPLD may cause communication interference to the communication connection between the dongle and the voltage conversion chip.
Therefore, in the embodiment of the present application, in order to improve the success rate of VR FW, it is proposed to monitor the connector in the burning circuit so as to effectively control the communication connection corresponding to the dongle. Communication connection between the software protector and other target devices which may cause interference is disconnected by reserving communication connection between the software protector and the voltage conversion chip, so that the success rate of burning firmware of the voltage conversion chip is guaranteed.
In a specific embodiment of the present application, the step S101 of monitoring the connector in the burning circuit may specifically include:
monitoring a voltage value of a connector;
step two, if the voltage value is increased from the first voltage to a second voltage, determining that the software protector is inserted into the connector;
and step two, if the voltage value is reduced from the second voltage to the first voltage, determining that the dongle is pulled out of the connector.
For convenience of description, the above three steps will be described in combination.
When the dongle is inserted into the connector, since the dongle signal has a phenomenon of being pulled up to a voltage (e.g., 3.3V (volt)) and thus can determine whether the dongle is inserted into the connector by monitoring the voltage value of the connector.
It should be noted that, in the present application, the first voltage is lower than the second voltage, and there is no sequential or primary and secondary limitation between the first voltage and the second voltage, the first voltage may specifically be a voltage corresponding to the dongle being inserted into the connector, and the second voltage may specifically be a voltage (e.g. 3.3V) corresponding to the dongle being inserted into the connector.
Specifically, the voltage value of the connector can be monitored in real time, and when the voltage value is increased from a first voltage to a second voltage, the software protector can be determined to be inserted into the connector; when the voltage value is reduced from the second voltage to the first voltage, the dongle can be determined to be unplugged from the connector. Determining that the dongle is not plugged into the connector when the voltage value remains at the first voltage; when the voltage value remains at the second voltage, it may be determined that the dongle remains plugged into the connector.
In practical applications, the voltage status of the connector, i.e. whether the dongle is inserted into the connector, can be monitored by the auto-switching module as shown in fig. 2. That is, the voltage value of the connector is monitored by the automatic switching module connected with the connector. The automatic switching module may be specifically a circuit with monitoring and switching functions, and the circuit may specifically include a voltage detector for detecting whether the dongle is inserted into the connector; and the change-over switch is used for disconnecting the communication connection between the software protector and the devices such as the BMC, the CPLD and the like after the software protector is inserted into the connector, and restoring the communication connection between the software protector and the devices such as the BMC, the CPLD and the like after the software protector is pulled out from the connector.
The I2C bus has three types of signals in the process of transmitting data: a start signal, an end signal and a response signal; start signal: when SCL is high level, SDA jumps from high level to low level to start transmitting data; an end signal: when SCL is high level, SDA jumps from low level to high level to finish transmitting data.
Of course, in practical applications, it may be monitored whether the dongle is inserted into the connector by using techniques such as image processing and infrared monitoring. For example, timed or real-time image capture of the connector, determining whether a dongle is inserted into the connector by identifying whether the dongle is present in the image; a monitoring infrared (including an infrared transmitter and an infrared receiver) is provided at the position of the insertion interface of the connector, and when the dongle is inserted into the connector so that the infrared is blocked, the infrared receiver generates a varying signal, thereby determining that the dongle is inserted into the connector.
S102, after the fact that the dongle is inserted into the connector is monitored, the communication connection between the dongle and the target device is disconnected.
When the software protector is detected to be inserted into the connector, the firmware burning of the voltage conversion chip is indicated, so that the communication connection between the software protector and the target device can be disconnected at the moment, and therefore I2C communication conflict is avoided, and the success rate of firmware burning is improved. The target device is a device which can interfere with firmware burning, such as a CPU, a BMC and a CPLD. For example, the following steps are carried out: as shown in fig. 3, the reason why the dongle is used to write the firmware into the voltage conversion chip is that when the dongle is used to write the firmware into the voltage conversion chip, the I2C communication conflicts, which results in the failure of writing. Specifically, the VR FW is burned by connecting an I2C connector (I2C connector) through a dongle, but the burned communication I2C is not only connected to the dongle, but also connected to the CPU, BMC, and CPLD. When dongle burns firmware to VR (voltage conversion chip), if CPLD, BMC, CPU have access or have access to CPU VR/DIMM VR, I2C communication conflict will be generated, resulting in unsuccessful burning.
In one embodiment of the present application, the disconnecting the dongle from the target device in step S102 includes: turning off the operating voltage of the target I2C device by using a switch; wherein the target I2C device powers the target device. Specifically, referring to fig. 4, a switch is set in fig. 4, and the operating voltage of the target I2C device can be turned off by the switch, so as to disconnect the operating voltages of the target I2C device and the target device, so that the target device cannot operate normally, i.e., the communication connection between the dongle and the target device can be disconnected.
In practical application, when the fact that the dongle is inserted into the connector is monitored, prompt information for disconnecting the communication connection between the dongle and the target device can be output externally in a light or sound or screen display mode, so that a user can disconnect the communication connection between the dongle and the target device in time, and the communication connection between the dongle and the target device can be disconnected by directly adopting a manual line removal mode or a manual control switch mode.
And S103, burning firmware to a voltage conversion chip in the burning circuit by using the software protector.
After the communication connection which can cause firmware burning interference is disconnected, firmware can be burnt to the voltage conversion chip by using the software protector. In the embodiment of the present application, how to burn firmware into the voltage conversion chip and what kind of firmware is burned are not limited.
At this time, since communication interference (especially, I2C communication interference) does not exist, the success rate of firmware burning can be greatly improved.
After the firmware is burned, the software protector can be pulled out from the connector, and in order to not interfere the normal work of the target device, the communication connection between the software protector and the target device can be recovered when the software protector can be detected to be pulled out. That is, when the dongle is detected to be unplugged, the communication connection between the dongle and the target device can be restored. Specifically, if the switch is used to disconnect the relevant communication connection and the dongle is pulled out, 3.3V of the dongle is pulled out, the switch does not work, and the I2C device operating voltage of the BMC and the CPLD is restored.
Monitoring a connector in a burning circuit by applying the method provided by the embodiment of the application; after the fact that the software protector is inserted into the connector is monitored, the communication connection between the software protector and the target device is disconnected; and burning firmware to a voltage conversion chip in the burning circuit by using the software protector.
The reason why the software protector is used for burning the firmware of the voltage conversion chip is that when the firmware is burnt to the voltage conversion chip, the I2C communication conflicts, so that the firmware cannot be burnt. Therefore, in the present application, in order to improve the success rate of burning firmware onto the voltage conversion chip, the connector in the burning circuit is first monitored. When the software protector is detected to be inserted into the connector, the communication connection between the software protector and the target device is directly disconnected. I.e. only the communication connection between the dongle and the voltage conversion chip can be reserved, directly avoiding the I2C communication collision from the physical hardware point of view. Then, the firmware is burned on the voltage conversion chip by using the software protector, and the success rate of burning the firmware can be effectively improved due to the fact that I2C communication conflict is avoided.
Corresponding to the above method embodiments, the present application further provides a burning circuit, and the burning circuit described below and the firmware burning method described above can be referred to correspondingly.
Referring to fig. 2, the burning circuit includes:
the device comprises a connector, an automatic switching module, a voltage conversion chip and a target device;
the connector is connected with the automatic switching module;
and the automatic switching module is used for monitoring the connector, and disconnecting the communication connection between the software protector and the target device after the software protector is inserted into the connector so that the software protector can burn firmware on the voltage conversion chip.
The automatic switching module is provided with a switch, and the switch is used for switching off the working voltage of the target I2C device; the target I2C device powers the target device.
The target device can be a CPU, a BMC or a CPLD. The voltage conversion chip can be any VR such as a CPU VR or a DIMM VR.
That is to say, an automatic switching module is added to the related burning circuit, so that only the dongle path is conducted when the dongle is automatically inserted, and other paths are conducted when the dongle is pulled out.
Specifically, when the dongle is inserted into the connector, the operating voltage of the I2C device connected to the BMC and the CPLD can be turned off by a switch due to the dongle signal pulling up to 3.3V. When the dongle is pulled out, 3.3V of the dongle is pulled out, the change-over switch does not work, and the working voltage of the I2C devices of the BMC and the CPLD is recovered. Therefore, the condition of I2C access conflict is not generated, and the fast read-write burning is realized.
Corresponding to the above method embodiments, the present application further provides a firmware burning apparatus, and the firmware burning apparatus described below and the firmware burning method described above may be referred to correspondingly.
Referring to fig. 5, the apparatus includes the following modules:
the connection monitoring module 101 is used for monitoring a connector in the burning circuit;
the access control module 102 is used for disconnecting the communication connection between the dongle and the target device after the dongle is monitored to be inserted into the connector;
and the firmware burning module 103 is used for burning firmware to the voltage conversion chip in the burning circuit by using the software protector.
The device provided by the embodiment of the application is applied to monitor the connector in the burning circuit; after the fact that the software protector is inserted into the connector is monitored, the communication connection between the software protector and the target device is disconnected; and burning firmware to a voltage conversion chip in the burning circuit by using the software protector.
The reason why the software protector is used for burning the firmware of the voltage conversion chip is that when the firmware is burnt to the voltage conversion chip, the I2C communication conflicts, so that the firmware cannot be burnt. Therefore, in the present application, in order to improve the success rate of burning firmware onto the voltage conversion chip, the connector in the burning circuit is first monitored. When the software protector is detected to be inserted into the connector, the communication connection between the software protector and the target device is directly disconnected. I.e. only the communication connection between the dongle and the voltage conversion chip can be reserved, directly avoiding the I2C communication collision from the physical hardware point of view. Then, the firmware is burned on the voltage conversion chip by using the software protector, and the success rate of burning the firmware can be effectively improved due to the fact that I2C communication conflict is avoided.
In one embodiment of the present application, the method further includes:
and the recovery module is used for recovering the communication connection between the software protector and the target device if the software protector is monitored to be pulled out.
In one embodiment of the present application, the path control module 102 is specifically configured to turn off the operating voltage of the target I2C device by using a switch; wherein the target I2C device powers the target device.
In a specific embodiment of the present application, the monitoring module 101 is connected, and is specifically configured to monitor a voltage value of the connector;
determining that the dongle is inserted into the connector if the voltage value increases from the first voltage to the second voltage;
and if the voltage value is reduced from the second voltage to the first voltage, determining that the dongle is pulled out of the connector.
In an embodiment of the present application, the connection monitoring module 101 is specifically configured to monitor a voltage value of the connector by using an automatic switching module connected to the connector.
Corresponding to the above method embodiment, the present application further provides an electronic device, and the electronic device described below and the firmware burning method described above may be referred to correspondingly.
Referring to fig. 6, the electronic device includes:
a memory 332 for storing a computer program;
the processor 322 is configured to implement the steps of the firmware burning method of the above-mentioned method embodiment when executing the computer program.
Specifically, referring to fig. 7, fig. 7 is a schematic diagram of a specific structure of an electronic device according to the present embodiment, which may generate relatively large differences due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, where the memory 332 stores one or more computer applications 342 or data 344. Memory 332 may be, among other things, transient or persistent storage. The program stored in memory 332 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the electronic device 301.
The electronic device 301 may also include one or more power sources 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341.
The electronic Device may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components, and is configured to perform the firmware burning method according to the above embodiments.
That is, the steps in the firmware burning method described above may be implemented by the structure of the electronic device.
Corresponding to the above method embodiment, the present application further provides a readable storage medium, and a readable storage medium described below and a firmware burning method described above may be referred to correspondingly.
A readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the steps of the firmware burning method of the above method embodiment.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. 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 steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it should also be noted that, herein, relationships such as first and second, etc., are intended only to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms include, or any other variation is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
The principle and the implementation of the present application are explained herein by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A firmware burning method is characterized by comprising the following steps:
monitoring a connector in the burning circuit;
after the fact that the dongle is inserted into the connector is monitored, disconnecting the communication connection between the dongle and a target device;
and burning firmware to a voltage conversion chip in the burning circuit by using the software protector.
2. The firmware burning method of claim 1, further comprising:
and if the fact that the software protector is pulled out is monitored, the communication connection between the software protector and the target device is recovered.
3. The firmware burning method of claim 1, wherein disconnecting the dongle from communication with the target device comprises:
turning off the operating voltage of the target I2C device by using a switch; wherein the target I2C device powers the target device.
4. The method of claim 1, wherein monitoring a connector in a burning circuit comprises:
monitoring the voltage value of the connector;
determining that the dongle is inserted into the connector if the voltage value increases from a first voltage to a second voltage;
and if the voltage value is reduced from the second voltage to the first voltage, determining that the dongle is unplugged from the connector.
5. The firmware burning method of claim 4, wherein the monitoring the voltage value of the connector comprises:
and monitoring the voltage value of the connector by utilizing an automatic switching module connected with the connector.
6. A burning circuit, comprising:
the device comprises a connector, an automatic switching module, a voltage conversion chip and a target device;
the connector is connected with the automatic switching module;
the automatic switching module is used for monitoring the connector, and disconnecting the communication connection between the software protector and the target device after the software protector is inserted into the connector, so that the software protector can burn firmware on the voltage conversion chip.
7. The burning circuit as claimed in claim 6, wherein the automatic switching module has a switch therein for turning off the operating voltage of the target I2C device; the target I2C device powers the target device.
8. A firmware burning device is characterized by comprising:
the connection monitoring module is used for monitoring a connector in the burning circuit;
the access control module is used for disconnecting the communication connection between the software protector and the target device after the software protector is monitored to be inserted into the connector;
and the firmware burning module is used for burning firmware to the voltage conversion chip in the burning circuit by using the software protector.
9. An electronic device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the firmware burning method according to any one of claims 1 to 5 when executing the computer program.
10. A readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the firmware burning method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111164916.7A CN114020283A (en) | 2021-09-30 | 2021-09-30 | Firmware burning method, burning circuit, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111164916.7A CN114020283A (en) | 2021-09-30 | 2021-09-30 | Firmware burning method, burning circuit, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114020283A true CN114020283A (en) | 2022-02-08 |
Family
ID=80055480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111164916.7A Pending CN114020283A (en) | 2021-09-30 | 2021-09-30 | Firmware burning method, burning circuit, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114020283A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117251183A (en) * | 2023-11-16 | 2023-12-19 | 苏州元脑智能科技有限公司 | Firmware burning method, main board, device, equipment, system and storage medium |
-
2021
- 2021-09-30 CN CN202111164916.7A patent/CN114020283A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117251183A (en) * | 2023-11-16 | 2023-12-19 | 苏州元脑智能科技有限公司 | Firmware burning method, main board, device, equipment, system and storage medium |
| CN117251183B (en) * | 2023-11-16 | 2024-02-20 | 苏州元脑智能科技有限公司 | Firmware burning method, main board, device, equipment, system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10860425B2 (en) | Method for recovering basic input/output system image file of a computer system and the computer system | |
| JP4464451B2 (en) | Microcontroller | |
| US20200290460A1 (en) | Method for processing throttle control signal, electronic speed regulator, controller, and mobile platform | |
| CN1074767A (en) | The method that computing machine, equipment and system thereof reconfigure | |
| CN112000351B (en) | Updating method, updating device, updating equipment and storage medium of BMC (baseboard management controller) firmware | |
| CN101373433A (en) | Method for updating BIOS and computer and system using the same | |
| CN103729220A (en) | Method and device for restoring BIOS (basic input output system) ROM (read only memory) by aid of EC (electronically controllable) ROM | |
| CN112612357B (en) | Abnormal power-off protection system, method and equipment for sub-nodes in server of whole cabinet | |
| CN114020283A (en) | Firmware burning method, burning circuit, device, equipment and readable storage medium | |
| CN110865822A (en) | Starting framework and method of Bootloader flash program for whole vehicle controller | |
| CN114003173A (en) | Power-down protection system of storage device and storage device | |
| CN111881074A (en) | Electronic system, host device and control method | |
| CN117331760A (en) | Equipment debugging method and device based on USB interface and storage medium | |
| CN100410893C (en) | Method and apparatus for master-controlled applied programm of self-repairing built-in equipment | |
| US8406069B2 (en) | Data writing method and writing device for an electronic erasable read only dynamic memory | |
| US10482053B2 (en) | Information processing apparatus with connection terminal for connecting to electronic devices having different functions | |
| CN112115000B (en) | Remote resetting method and system of system component power supply and BMC remote device | |
| CN116466968B (en) | Access method and device of main board flash memory and firmware burning method and device | |
| CN110908673A (en) | Digital power supply chip burning method | |
| CN104143350A (en) | Electronic apparatus | |
| CN214376428U (en) | Intelligent vehicle-mounted internet terminal mainboard, intelligent vehicle-mounted internet terminal and vehicle | |
| CN214897632U (en) | Detection device of nonvolatile memory | |
| CN116155389B (en) | Optical module debugging system and method | |
| CN114979925A (en) | Earphone type recognition device, earphone type recognition method, earphone type recognition device, and storage medium | |
| EP4131888A1 (en) | Method for searching for interrupted device, slave device, master device, and storage medium |
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 |