CN118069171A - Firmware processing method and device of intelligent terminal and firmware upgrading system - Google Patents

Firmware processing method and device of intelligent terminal and firmware upgrading system Download PDF

Info

Publication number
CN118069171A
CN118069171A CN202410222170.8A CN202410222170A CN118069171A CN 118069171 A CN118069171 A CN 118069171A CN 202410222170 A CN202410222170 A CN 202410222170A CN 118069171 A CN118069171 A CN 118069171A
Authority
CN
China
Prior art keywords
efuse
intelligent terminal
file
upgrade package
ota upgrade
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
Application number
CN202410222170.8A
Other languages
Chinese (zh)
Inventor
吴非
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Quectel Wireless Solutions Co Ltd
Original Assignee
Quectel Wireless Solutions Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Quectel Wireless Solutions Co Ltd filed Critical Quectel Wireless Solutions Co Ltd
Priority to CN202410222170.8A priority Critical patent/CN118069171A/en
Publication of CN118069171A publication Critical patent/CN118069171A/en
Pending legal-status Critical Current

Links

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
    • G06F8/63—Image based installation; Cloning; Build to order
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • G06F21/121—Restricting unauthorised execution of programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Signal Processing (AREA)
  • Technology Law (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a firmware processing method, a device, a system, electronic equipment and a computer readable storage medium of an intelligent terminal, wherein the method comprises the following steps: after the intelligent terminal is subjected to complete machine test and the complete machine test is determined to pass, acquiring an OTA upgrade package constructed by the eFuse file from a preset cloud; and programming the eFuse file of the OTA upgrade package to an intelligent terminal, and starting the intelligent terminal after programming is completed to determine the programming state of the eFuse file. According to the invention, the whole intelligent equipment can be tested firstly, the OTA upgrade package constructed by the eFuse file is obtained after the test is passed, and the eFuse firmware is automatically programmed through the OTA upgrade package, so that on one hand, the problem of resource waste caused by frequent CPU replacement after the test failure can be avoided, and on the other hand, the eFuse firmware can be quickly programmed, and the processing efficiency is improved.

Description

Firmware processing method and device of intelligent terminal and firmware upgrading system
Technical Field
The present invention relates to the technical field of firmware processing, and in particular, to a method and an apparatus for processing firmware of an intelligent terminal, and a firmware upgrade system.
Background
EFuses are a hardware blown security mechanism, primarily deployed on the CPU, to prevent an attacker from downloading and running non-factory signed firmware.
Because only one fuse can be programmed at a time by the eFuse, the function can greatly improve the operation efficiency of the chip and reduce the cost of testing and self-repairing. Therefore, before the intelligent terminal is subjected to the complete machine test, eFuses are generally packaged into production firmware, the eFuses are programmed into the intelligent terminal through USB wires at a station for programming the firmware (board level), and then the intelligent terminal is subjected to the complete machine test, and when faults occur, eFuses are blown to protect the CPU of the intelligent terminal.
However, the current common methods have the following technical problems: because the intelligent terminal safety requirement is that a USB port cannot be reserved after the complete machine is installed, eFuses can not be programmed through a USB line after the complete machine is tested, and the eFuses can be re-programmed only after the complete machine is re-disassembled. Therefore, once the problem of the CPU or the module is encountered in the whole machine testing stage, the CPU can only be returned to the supplier for disassembling the machine or directly replacing the CPU. This operation is not only time consuming and inefficient, but also results in a significant amount of CPU resource waste.
Disclosure of Invention
The invention provides a firmware processing method, a device and a firmware upgrading system of an intelligent terminal, wherein the method can test the whole intelligent equipment, acquire an OTA upgrading packet constructed by an eFuse file after the test is passed, and automatically burn eFuse firmware through the OTA upgrading packet, so that on one hand, the problem of resource waste caused by frequent CPU replacement after the test failure can be avoided, and on the other hand, eFuse firmware can be quickly burned, thereby improving the processing efficiency.
A first aspect of an embodiment of the present invention provides a firmware processing method of an intelligent terminal, where the method includes:
after the intelligent terminal is subjected to complete machine test and the complete machine test is determined to pass, acquiring an OTA upgrade package constructed by the eFuse file from a preset cloud;
And programming the eFuse file of the OTA upgrade package to the intelligent terminal, and starting the intelligent terminal after programming is completed to determine the programming state of the eFuse file.
In a possible implementation manner of the first aspect, the programming the eFuse file of the OTA upgrade package to the intelligent terminal includes:
Respectively extracting a file signature and a signature verification key from source codes of eFuse files of the OTA upgrade package;
signature verification is carried out on the file signature by adopting the signing verification key;
and after the signature verification is passed, the eFuse file of the OTA upgrade package is programmed to the intelligent terminal.
In a possible implementation manner of the first aspect, before the step of acquiring the OTA upgrade packet constructed by the eFuse file from the preset cloud, the method further includes:
respectively carrying out network detection, cloud communication detection and zone bit detection on the intelligent terminal;
When the network detection, the cloud communication detection and the zone bit detection pass, an OTA upgrade package is obtained from a preset cloud;
and prompting abnormality when any one of the network detection, the cloud communication detection or the zone bit detection fails.
In a possible implementation manner of the first aspect, the flag bit detection includes:
acquiring a zone bit value, wherein the zone bit value is a value of an eFuse zone bit issued by a preset cloud after the intelligent terminal is connected with the preset cloud;
If the marker bit value is the same as the preset value, determining that the marker bit is detected;
otherwise, if the flag bit value is different from the preset value, determining that the flag bit detection is not passed.
In one possible implementation manner of the first aspect, the acquiring the OTA upgrade package constructed by the eFuse file includes:
generating a file packet by utilizing the eFuse file and a preset data packet;
And compiling after adding a file signature and a signature verification key to the eFuse file of the file package to generate an OTA upgrade package. In a possible implementation manner of the first aspect, the starting the smart terminal after completing programming to determine the programming state of the eFuse file includes:
starting the intelligent terminal and determining whether a fuse register of a CPU of the intelligent terminal has a fuse;
if the fuse wire register of the CPU of the intelligent terminal has a fuse wire, determining that the programming state of the eFuse file is successful;
If the fuse wire register of the CPU of the intelligent terminal has no fuse wire, determining that the programming state of the eFuse file is failed, and re-programming the eFuse file of the OTA upgrade package to the intelligent terminal.
A second aspect of an embodiment of the present invention provides a firmware processing apparatus of an intelligent terminal, where the apparatus includes:
the upgrade package acquisition module is used for performing complete machine test on the intelligent terminal and acquiring an OTA upgrade package constructed by the eFuse file from a preset cloud after the complete machine test is determined to pass;
and the automatic programming module is used for programming the eFuse file of the OTA upgrade package to the intelligent terminal, and starting the intelligent terminal after programming is completed to determine the programming state of the eFuse file.
A third aspect of an embodiment of the present invention provides a firmware upgrade system for an intelligent terminal, the system including:
The POS machine is suitable for the firmware processing method of the intelligent terminal;
the cloud end is used for constructing an OTA upgrade package according to the eFuse file;
The POS machine is used for automatically updating eFuse firmware by adopting the OTA upgrade package.
Compared with the prior art, the firmware processing method and device for the intelligent terminal and the firmware upgrading system provided by the embodiment of the invention have the beneficial effects that: according to the invention, the whole intelligent equipment can be tested firstly, the OTA upgrade package constructed by the eFuse file is obtained after the test is passed, and the eFuse firmware is automatically programmed through the OTA upgrade package, so that on one hand, the problem of resource waste caused by frequent CPU replacement after the test failure can be avoided, and on the other hand, the eFuse firmware can be quickly programmed, and the processing efficiency is improved.
Drawings
Fig. 1 is a flow chart of a firmware processing method of an intelligent terminal according to an embodiment of the present invention;
Fig. 2 is a control flow chart of a firmware processing method of an intelligent terminal according to an embodiment of the present invention;
FIG. 3 is an operation flowchart of a firmware processing method of an intelligent terminal according to an embodiment of the present invention
Fig. 4 is a schematic structural diagram of a firmware processing device of an intelligent terminal according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a firmware upgrade system for an intelligent terminal according to an embodiment of the present invention;
fig. 6 is an operation flowchart of a firmware upgrade system for an intelligent terminal according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In order to solve the above-mentioned problem, the following detailed description and the explanation will be given for a firmware processing method of an intelligent terminal according to the embodiment of the present application.
Referring to fig. 1, a flowchart of a firmware processing method of an intelligent terminal according to an embodiment of the present invention is shown.
In one embodiment, the method is applicable to a smart terminal, which may be a POS machine (also known as a multifunction terminal reader). The safety requirement of the POS machine is that a USB port cannot be reserved after the POS machine is assembled, so that eFuses can not be programmed through a USB line after the test of the POS machine is finished, the eFuses can be programmed again only after the POS machine is disassembled again, and the operation is long in time consumption and low in efficiency. If the CPU is directly replaced and then tested, a great deal of CPU resource waste is caused.
In order to solve the technical problems, the invention discloses a firmware processing method of an intelligent terminal, which is suitable for detection equipment of the intelligent terminal.
As an example, the method for processing firmware of the intelligent terminal may include:
S11, performing complete machine test on the intelligent terminal, and acquiring an OTA upgrade package constructed by the eFuse file from a preset cloud after the complete machine test is determined to pass.
In one embodiment, the intelligent terminal (e.g., POS machine) may be first subjected to a complete machine test. The intelligent terminal can be subjected to complete machine test at the starting-up stage, and the test can be a conventional performance test. In one implementation, after the intelligent terminal is started, the intelligent terminal is controlled to run a built-in complete machine test program for testing.
After the test is completed or passed, an OTA upgrade package is obtained from a preset cloud, wherein the OTA upgrade package can be a data package constructed by an eFuse file.
It should be noted that the preset cloud end may be an OTA server, specifically may be a cloud end of an intelligent terminal, and the cloud end is responsible for providing a remote upgrade package.
Wherein, by way of example, the acquiring the OTA upgrade package constructed by the eFuse file includes:
S21, after the eFuse file compiled by the user is obtained, generating a file package by utilizing the eFuse file and a preset data package.
S22, compiling after adding the file signature and the signing verification key to the eFuse file of the file package to generate an OTA upgrade package.
Specifically, the eFuse file may be a file compiled by a technician or manager that can burn eFuses, e.g., capture file 1 compiled by a user to generate eFuses, and then make file 1 of eFuses into an upgrade package. In the manufacturing process, the file 1 can be put into a preset data packet. And the package may be signed during the manufacturing process to obtain its file signature and corresponding signing key. The file signature and its corresponding signing key may be placed in the source code of the production firmware, which is finally compiled to generate an OTA upgrade package, where the OTA upgrade package includes file 1 of the eFuse, and file 1 includes the file signature and the corresponding signing key.
After construction, the OTA upgrade package can be issued to a preset cloud end, and the preset cloud end adds corresponding eFuse flag bits to the OTA upgrade package. For example, its eFuse flag bit writes 1. The flag bit can be used for checking the OTA upgrade package before the subsequent extraction of the OTA upgrade package, and determining whether the OTA upgrade package with the extraction error exists or not.
In an actual operation mode, when the OTA upgrade package is constructed, the 'auto-upgrade eFuse program' and the 'auto-detect eFuse program' can be integrated into source codes of the production firmware to be compiled and generated into the production firmware. After the OTA upgrade package is sent to the intelligent terminal, the automatic eFuse programming and the automatic eFuse detection program can be forced to run. The eFuse program is automatically programmed, so that the intelligent terminal can download an OTA upgrade package of the eFuse file from a preset cloud end, eFuse upgrade is carried out on the intelligent terminal, and the intelligent terminal is automatically restarted after the eFuse upgrade is finished. The automatic eFuse detection program can detect whether the intelligent terminal is successfully programmed by adopting the OTA upgrade package.
Because the intelligent terminal needs to acquire the OTA upgrade package from the preset cloud, before acquiring the OTA upgrade package, whether the communication network is abnormal or not needs to be determined. As an example, before the step of obtaining the OTA upgrade package constructed by the eFuse file from the preset cloud, the method may further include the following steps:
S31, respectively carrying out network detection, cloud communication detection and zone bit detection on the intelligent terminal.
S32, when the network detection, the cloud communication detection and the zone bit detection pass, an OTA upgrade package is obtained from a preset cloud.
S33, prompting abnormality when the network detection, the cloud communication detection or the zone bit detection fails.
In an embodiment, the network detection may be to determine whether the intelligent terminal is connected to a network, for example, determine whether 4G, 5G, or wifi of the intelligent terminal is connected; the cloud communication detection may be to determine whether the intelligent terminal and a preset cloud or server can be connected; the flag bit detection may be to determine whether a value of an eFuse flag bit of a preset cloud or server is the same as a value added when the cloud builds an OTA upgrade package.
Specifically, the flag bit detection may include the following steps:
S41, acquiring a zone bit value, wherein the zone bit value is a value of an efuse zone bit issued by a preset cloud after the intelligent terminal is connected with the preset cloud.
S42, if the value of the zone bit is the same as the preset value, determining that the zone bit passes detection.
S43, otherwise, if the value of the zone bit is different from the preset value, determining that the zone bit detection is not passed.
The method comprises the steps that a value corresponding to a zone bit can be directly obtained, the value of the zone bit is obtained, after the intelligent terminal is connected with a preset cloud, the preset cloud adds the value of a corresponding eFuse zone bit to an OTA upgrade package, and the eFuse zone bit issued by the value is sent to the intelligent terminal. Referring to the above example, the eFuse flag bit has a written value of 1 and a flag bit has a value of 1.
Then judging whether the value of the flag bit is the same as a preset value, wherein the preset value is a value obtained by adding a corresponding eFuse flag bit to an OTA upgrade package by a preset cloud end, and if so, determining that the flag bit passes detection; otherwise, determining that the flag bit detection is not passed.
Specifically, the terminal is connected with the remote OTA server through the socket, and cloud communication detection can be to judge whether the socket can be communicated or not so as to determine whether the intelligent terminal can be communicated with a preset cloud or server or not.
If the network detection, the cloud communication detection and the flag bit detection are all passed, downloading an OTA upgrade package of the eFuse file from a preset cloud through the network.
If any one of network detection, cloud communication detection or zone bit detection fails, an abnormality is prompted. For example, if the network detection fails, a network abnormality may be prompted, and the network is checked and retried. Cloud communication detection is not passed, a server is prompted to be abnormal, and retries are carried out after inspection. If the flag bit detection is not passed, the eFuse flag bit is prompted to be abnormal, and the test is repeated.
S12, programming the eFuse file of the OTA upgrade package to the intelligent terminal, and starting the intelligent terminal after programming is completed to determine that programming of the eFuse file is successful.
After the OTA upgrade package is obtained, the eFuse file of the OTA upgrade package can be programmed into the intelligent terminal to finish programming of the eFuse file, whether programming is successful needs to be determined, and the intelligent terminal for programming the eFuse file can be started to determine whether programming is successful.
In an alternative embodiment, the programming the eFuse file of the OTA upgrade package to the intelligent terminal may include the following substeps:
s121, respectively extracting a file signature and a signature verification key from source codes of eFuse files of the OTA upgrade package.
S122, signature verification is carried out on the file signature by adopting the signing verification key.
And S123, after the signature verification is passed, burning the eFuse file of the OTA upgrade package to the intelligent terminal.
According to the content, when the OTA upgrade package is constructed, the file signature and the corresponding signature verification key are edited together to generate the OTA upgrade package.
Therefore, before programming, it is necessary to determine whether the signature of the OTA upgrade package is correct. Specifically, the file signature and the signing key may be extracted from the source code of the eFuse file of the OTA upgrade package, respectively. And then adopting the signing verification key to verify the signature of the file. And after the signature verification is passed, the eFuse file of the OTA upgrade package is programmed to the intelligent terminal so as to upgrade the eFuse in the intelligent terminal by using the OTA upgrade package.
If the signature verification is not passed, prompting that the signature of the OTA upgrade package is abnormal, and re-verifying after checking the network of the intelligent terminal, or re-acquiring the OTA upgrade package and verifying.
By signature verification, whether the adopted OTA upgrade package is abnormal or not can be determined, and the abnormal OTA upgrade package is prevented from being called to carry out upgrade processing, so that the efficiency of the upgrade processing is improved.
To determine whether the smart device successfully completed the programming of the eFuse file, in an alternative embodiment, the smart terminal is activated after the programming is completed to determine the programming status of the eFuse file, which may include the sub-steps of:
S124, starting the intelligent terminal and determining whether a fuse exists in a fuse register of a CPU of the intelligent terminal.
And S125, if the fuse wire register of the CPU of the intelligent terminal has a fuse wire, determining that the eFuse file writing state is successful.
And S126, if the fuse wire register of the CPU of the intelligent terminal has no fuse wire, determining that the eFuse file writing state is failed, and writing the eFuse file of the OTA upgrade package to the intelligent terminal again.
In accordance with the foregoing description, an "auto-detect eFuse program" is added to the OTA upgrade package when the OTA upgrade package is constructed. After the OTA upgrade package can be completed, the starting can be triggered, and whether the eFuse file is successfully programmed or not is judged. The program judges whether the fuse wire register of the CPU has the fuse wire or not by reading the fuse wire register of the CPU, if so, the program determines that the eFuse file is successfully programmed, and the intelligent terminal can be normally used subsequently. Otherwise, if the fuse register of the CPU is judged to have no fuse, the eFuse file is determined to be unsuccessfully programmed.
Referring to fig. 2, a control flow chart of a firmware processing method of an intelligent terminal according to an embodiment of the invention is shown.
Specifically, the control flow of the firmware processing method of the intelligent terminal comprises the following steps:
first, the user compiles in advance to generate an eFuse file that can be burned.
And secondly, manufacturing the eFuse file into an OTA upgrade package.
And thirdly, uploading the OTA upgrade package to a preset cloud.
Fourthly, starting the equipment to be detected, and starting a whole machine test program by a tester.
And fifthly, judging whether the whole machine test is passed or not, and starting an 'automatic programming eFuse program' built in the OTA upgrade package if the test is passed.
And sixthly, the 'automatic eFuse programming' downloads an OTA upgrade package of the eFuse file from a preset cloud end, and upgrades the eFuse file.
Seventh, automatically restarting the system after upgrading, and forcibly running an 'automatic eFuse program detection' after restarting.
Eighth, determine if eFuse is successfully programmed.
And ninth, finishing the successful programming of the eFuse file.
In the prior art, fuses are burned first and then tested, and if defective products return to the original factory for maintenance, the CPU of the fuses cannot be maintained and can only be scrapped. And after the test is finished, the fuse can not have the problem after no problem. The invention can ensure that after the machine is assembled into a whole machine, the eFuse file is automatically updated through OTA without problems, thereby reducing the number of scrapped CPU and avoiding the waste of CPU resources.
Referring to fig. 3, an operation flowchart of a firmware processing method of an intelligent terminal according to an embodiment of the present invention is shown.
Referring to fig. 3, in order to further describe different operation processes of the firmware processing method of the intelligent terminal, description is made for constructing an OTA upgrade package, automatic programming, and automatic detection, respectively.
Wherein, regarding to constructing the OTA upgrade package, the operation thereof comprises the following steps:
In the first step, a file 1 that generates "eFuses" is compiled.
In a second step, file 1 of eFuse is placed into a preset data packet.
Thirdly, compiling the preset data packet to generate an OTA upgrade packet, signing the OTA upgrade packet, and placing the signature and the signing verification key in the source code of the production firmware.
And fourthly, releasing the OTA upgrade package to a server or a preset cloud end, and writing an eFuse flag bit of the server into 1. And integrating the automatic updating eFuse program and the automatic detecting eFuse program into system source code to compile and generate production firmware.
With respect to building an auto-programming eFuse program, its operations include the steps of:
First, after the factory test program passes the test, the "auto programming eFuse program" is automatically run.
And secondly, judging whether a network is connected (whether 4G or wifi is connected), if not, prompting that the network is abnormal, and retrying after checking the network.
And thirdly, judging whether the OTA server can be connected or not if the OTA server has the connection, prompting the server to be abnormal if the OTA server cannot be connected, and retrying after checking.
Fourth, if the eFuse flag bit of the communication judging server is 1, if not, prompting that the eFuse flag bit is abnormal, and retrying after checking.
And fifthly, if the value is 1, downloading an OTA upgrade package of the eFuse file through a network.
And step six, judging whether the signature of the OTA upgrade package is correct, if not, prompting that the signature of the OTA upgrade package is abnormal, and checking the network and then re-verifying.
Seventh, if the signature is correct, the eFuse file is upgraded by using the OTA upgrade package.
With respect to building a sensing eFuse program, its operation includes the steps of:
first, the POS machine is started.
And secondly, automatically starting an 'automatic eFuse program', and judging whether the eFuse file is successfully programmed.
Third, if unsuccessful, prompt "eFuse not burned, do not commercial", and start "auto-burn eFuse program".
And fourthly, if successful, starting up normally. The invention burns the eFuse file after the whole machine test has no problem, so the CPU waste rate caused by the eFuse file is greatly reduced.
The invention can automatically burn eFuse files, and reduce the workload of manual operation.
The invention can automatically check whether the programming is successful, and reduces the programming error rate of eFuse files.
The invention reduces CPU waste rate, increases the success rate of programming eFuse files in factories, and brings good benefits to module suppliers, POS factories and chip former factories.
In this embodiment, the embodiment of the present invention provides a firmware processing method for an intelligent terminal, which has the following beneficial effects: according to the invention, the whole intelligent equipment can be tested firstly, the OTA upgrade package constructed by the eFuse file is obtained after the test is passed, and the eFuse firmware is automatically programmed through the OTA upgrade package, so that on one hand, the problem of resource waste caused by frequent CPU replacement after the test failure can be avoided, and on the other hand, the eFuse firmware can be quickly programmed, and the processing efficiency is improved.
The embodiment of the invention also provides a firmware processing device of the intelligent terminal, and referring to fig. 4, a schematic structural diagram of the firmware processing device of the intelligent terminal is shown.
As an example, the firmware processing device of the intelligent terminal may include:
The upgrade package acquisition module 401 is configured to perform a complete machine test on the intelligent terminal and acquire an OTA upgrade package constructed by an eFuse file from a preset cloud after the complete machine test is determined to pass;
And the automatic programming module 402 is configured to program the eFuse file of the OTA upgrade package to the intelligent terminal, and after programming is completed, start the intelligent terminal to determine the programming state of the eFuse file.
Optionally, the automatic programming module is further configured to:
Respectively extracting a file signature and a signature verification key from source codes of eFuse files of the OTA upgrade package;
signature verification is carried out on the file signature by adopting the signing verification key;
and after the signature verification is passed, the eFuse file of the OTA upgrade package is programmed to the intelligent terminal.
Optionally, the apparatus further comprises:
the detection module is used for respectively carrying out network detection, cloud communication detection and zone bit detection on the intelligent terminal;
The detection module is used for acquiring an OTA upgrade package from a preset cloud when the network detection, the cloud communication detection and the marker bit detection are all passed;
The detection abnormality module is used for prompting abnormality when any one of the network detection, the cloud communication detection or the zone bit detection fails.
Optionally, the flag bit detection includes
Acquiring a zone bit value, wherein the zone bit value is a value of an efuse zone bit issued by a preset cloud after the intelligent terminal is connected with the preset cloud;
If the marker bit value is the same as the preset value, determining that the marker bit is detected;
otherwise, if the flag bit value is different from the preset value, determining that the flag bit detection is not passed.
Optionally, the acquiring the OTA upgrade package constructed by the eFuse file includes:
After an eFuse file compiled by a user is acquired, generating a file package by utilizing the eFuse file and a preset data package;
and compiling after adding a file signature and a signature verification key to the eFuse file of the file package to generate an OTA upgrade package.
Optionally, the automatic programming module is further configured to:
starting the intelligent terminal and determining whether a fuse register of a CPU of the intelligent terminal has a fuse;
If the fuse wire register of the CPU of the intelligent terminal has a fuse wire, determining that the eFuse file writing state is successful;
If the fuse wire register of the CPU of the intelligent terminal has no fuse wire, determining that the eFuse file writing state is failed, and writing the eFuse file of the OTA upgrade package to the intelligent terminal again.
The embodiment of the invention also provides a firmware upgrading system for the intelligent terminal, and referring to fig. 5, a schematic structural diagram of the firmware upgrading system for the intelligent terminal is shown.
Among others, as an example, the firmware upgrade system for a smart terminal may include:
The POS machine is suitable for the firmware processing method of the intelligent terminal;
the cloud end is used for constructing an OTA upgrade package according to the eFuse file;
The POS machine is used for automatically updating eFuse firmware by adopting the OTA upgrade package.
Referring to fig. 6, an operation flowchart of a firmware upgrade system for an intelligent terminal according to an embodiment of the present invention is shown.
In one implementation, the cloud may be an OTA server that may obtain eFuse files of eFuse publishers and generate OTA upgrade packages using the eFuse files.
The POS machine can complete the whole machine test program first, and after the whole machine test program is completed, the eFuse program can be automatically programmed, and after the automatic programming is completed, the eFuse program is detected.
It will be clearly understood by those skilled in the art that, for convenience and brevity, the specific working process of the apparatus described above may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
Further, an embodiment of the present application further provides an electronic device, including: the system comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor is used for realizing the firmware processing method of the intelligent terminal according to the embodiment when executing the program.
Further, an embodiment of the present application also provides a computer-readable storage medium storing a computer-executable program for causing a computer to execute the firmware processing method of the intelligent terminal according to the above embodiment.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that changes and modifications may be made without departing from the principles of the invention, such changes and modifications are also intended to be within the scope of the invention.

Claims (10)

1. The firmware processing method of the intelligent terminal is characterized by comprising the following steps of:
after the intelligent terminal is subjected to complete machine test and the complete machine test is determined to pass, acquiring an OTA upgrade package constructed by the eFuse file from a preset cloud;
And programming the eFuse file of the OTA upgrade package to the intelligent terminal, and starting the intelligent terminal after programming is completed to determine the programming state of the eFuse file.
2. The method of claim 1, wherein programming the eFuse file of the OTA upgrade package to the intelligent terminal comprises:
Respectively extracting a file signature and a signature verification key from source codes of eFuse files of the OTA upgrade package;
signature verification is carried out on the file signature by adopting the signing verification key;
and after the signature verification is passed, the eFuse file of the OTA upgrade package is programmed to the intelligent terminal.
3. The method of claim 1, wherein before the step of obtaining the OTA upgrade package constructed by the eFuse file from the preset cloud, the method further comprises:
respectively carrying out network detection, cloud communication detection and zone bit detection on the intelligent terminal;
When the network detection, the cloud communication detection and the zone bit detection pass, an OTA upgrade package is obtained from a preset cloud;
and prompting abnormality when any one of the network detection, the cloud communication detection or the zone bit detection fails.
4. The firmware processing method of an intelligent terminal according to claim 3, wherein the flag bit detection includes:
acquiring a zone bit value, wherein the zone bit value is a value of an eFuse zone bit issued by a preset cloud after the intelligent terminal is connected with the preset cloud;
If the marker bit value is the same as the preset value, determining that the marker bit is detected;
otherwise, if the flag bit value is different from the preset value, determining that the flag bit detection is not passed.
5. The method for processing firmware of an intelligent terminal according to claim 1, wherein the acquiring an OTA upgrade package constructed by an eFuse file comprises:
After an eFuse file compiled by a user is acquired, generating a file package by utilizing the eFuse file and a preset data package;
and compiling after adding a file signature and a signature verification key to the eFuse file of the file package to generate an OTA upgrade package.
6. The method of firmware processing for an intelligent terminal of claim 1, wherein the starting the intelligent terminal after programming is completed to determine the programming status of the eFuse file comprises:
starting the intelligent terminal and determining whether a fuse register of a CPU of the intelligent terminal has a fuse;
if the fuse wire register of the CPU of the intelligent terminal has a fuse wire, determining that the programming state of the eFuse file is successful;
If the fuse wire register of the CPU of the intelligent terminal has no fuse wire, determining that the programming state of the eFuse file is failed, and re-programming the eFuse file of the OTA upgrade package to the intelligent terminal.
7. A firmware processing device of an intelligent terminal, the device comprising:
the upgrade package acquisition module is used for performing complete machine test on the intelligent terminal and acquiring an OTA upgrade package constructed by the eFuse file from a preset cloud after the complete machine test is determined to pass;
and the automatic programming module is used for programming the eFuse file of the OTA upgrade package to the intelligent terminal, and starting the intelligent terminal after programming is completed to determine the programming state of the eFuse file.
8. A firmware upgrade system for an intelligent terminal, the system comprising: the POS machine and the cloud end are in communication connection, and the POS machine is suitable for the firmware processing method of the intelligent terminal according to any one of claims 1-6;
the cloud end is used for constructing an OTA upgrade package according to the eFuse file;
The POS machine is used for automatically updating eFuse firmware by adopting the OTA upgrade package.
9. An electronic device, comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the firmware processing method of the intelligent terminal according to any of the claims 1-6 when executing the computer program.
10. A computer-readable storage medium storing a computer-executable program for causing a computer to execute the firmware processing method of the intelligent terminal according to any one of claims 1 to 6.
CN202410222170.8A 2024-02-28 2024-02-28 Firmware processing method and device of intelligent terminal and firmware upgrading system Pending CN118069171A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410222170.8A CN118069171A (en) 2024-02-28 2024-02-28 Firmware processing method and device of intelligent terminal and firmware upgrading system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410222170.8A CN118069171A (en) 2024-02-28 2024-02-28 Firmware processing method and device of intelligent terminal and firmware upgrading system

Publications (1)

Publication Number Publication Date
CN118069171A true CN118069171A (en) 2024-05-24

Family

ID=91108851

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410222170.8A Pending CN118069171A (en) 2024-02-28 2024-02-28 Firmware processing method and device of intelligent terminal and firmware upgrading system

Country Status (1)

Country Link
CN (1) CN118069171A (en)

Similar Documents

Publication Publication Date Title
US20030051235A1 (en) Method and apparatus for verifying and analyzing computer software installation
CN111522562B (en) Dishwasher software burning method, device and equipment thereof
CN103970564A (en) Automatic repairing and upgrading method of embedded operating system and embedded operating system with automatic repairing and upgrading functions
CN106648762B (en) Method and device for building development environment
CN110928556A (en) Automatic program burning method and device for railway vehicle, and testing method and system
CN108920168B (en) Bootloader method supporting simultaneous upgrading of multiple similar ECUs and having function of preventing program mismatching
EP2503459B1 (en) Complete and compatible function
CN110806884A (en) Method and device for repairing operating system fault
CN116932010A (en) System firmware upgrading method, device and server
CN112015587B (en) Method and device for enhancing reliability of operating system
CN111273928B (en) Bootloader design method for self-upgrading
CN116383090B (en) Automatic testing method and platform for kylin system migration tool
CN111918278A (en) Over-the-air upgrade checking method, device, medium and intelligent terminal equipment
CN118069171A (en) Firmware processing method and device of intelligent terminal and firmware upgrading system
CN114793196B (en) Firmware upgrading method, device, equipment and storage medium
CN116820528A (en) Firmware version upgrading method and device, chip and electronic equipment
CN111078476A (en) Network card drive firmware stability test method, system, terminal and storage medium
CN116301995A (en) Firmware upgrading method based on bootloader architecture
CN115455431A (en) Method, device, terminal and medium for automatic code security detection and vulnerability repair
CN115481405A (en) Safe starting and optimized upgrading method of embedded system
CN112596749A (en) Method and device for system power-on self-test and self-repair
CN116302021B (en) BootLoader program online upgrading method, control unit and new energy automobile
CN112565896B (en) System repairing method, terminal and storage medium
CN116719681A (en) Fault testing system and testing method
CN117112443A (en) BootLoader test method, device and system

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