CN112216337B - Firmware parameter detection method, device and firmware setting method - Google Patents

Firmware parameter detection method, device and firmware setting method Download PDF

Info

Publication number
CN112216337B
CN112216337B CN202010954914.7A CN202010954914A CN112216337B CN 112216337 B CN112216337 B CN 112216337B CN 202010954914 A CN202010954914 A CN 202010954914A CN 112216337 B CN112216337 B CN 112216337B
Authority
CN
China
Prior art keywords
firmware
parameter
parameters
parameter setting
standard
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.)
Active
Application number
CN202010954914.7A
Other languages
Chinese (zh)
Other versions
CN112216337A (en
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.)
Shenzhen Tigo Semiconductor Co ltd
Original Assignee
Shenzhen Tigo Semiconductor 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 Shenzhen Tigo Semiconductor Co ltd filed Critical Shenzhen Tigo Semiconductor Co ltd
Priority to CN202010954914.7A priority Critical patent/CN112216337B/en
Publication of CN112216337A publication Critical patent/CN112216337A/en
Application granted granted Critical
Publication of CN112216337B publication Critical patent/CN112216337B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C29/00Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/56External testing equipment for static stores, e.g. automatic test equipment [ATE]; Interfaces therefor

Abstract

The application relates to a firmware parameter detection method, a device and a firmware setting method, wherein the firmware parameter detection method comprises the following steps: reading a parameter setting document and a corresponding standard file; acquiring firmware parameter information to be tested in a parameter setting document; obtaining standard firmware parameter information in a standard file; detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result; the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not. If the parameter setting document has no wrong firmware parameter information, the parameter setting is carried out on the firmware to be opened according to the parameter setting document, so that the accuracy of the parameter setting of the firmware is ensured, the firmware with the set parameters is not required to be subjected to parameter detection again, the manpower and material resources are saved, and the production efficiency is improved.

Description

Firmware parameter detection method, device and firmware setting method
Technical Field
The present disclosure relates to the field of solid state hard drives, and in particular, to a method and apparatus for detecting firmware parameters and a method for setting firmware parameters.
Background
Firmware (firmware) is a program written in flash memory or EROM, EPROM (programmable read only memory) in an Application Specific Integrated Circuit (ASIC) or Programmable Logic Device (PLD), and is colloquially understood to be "solidified software" and also translated as "firmware". Firmware is the software of the BIOS, which is the program code solidified inside the integrated circuit and is responsible for controlling and coordinating the functions of the integrated circuit, but is quite different from the ordinary software. The firmware parameter, also called a parameter quantity, is a variable. The solid state disk of the same series changes the information such as capacity, serial number, flash memory type and the like by modifying the firmware parameters, so that the solid state disk of different models is produced. Firmware download is also called card opening. And the firmware with the set parameters is downloaded to the solid state disk. The current industry detection method for firmware parameters is that a hardware engineer sets parameters according to the direction of a manufacturer, then a screenshot is saved, and the screenshot is referred to for setting parameters during production of a production line, which has the defects of low efficiency and incapability of ensuring whether the finally obtained firmware has wrong firmware parameters.
Disclosure of Invention
In order to solve the above technical problem of low efficiency of setting and detecting firmware parameters through artificial reference screenshot, the embodiment of the application provides a firmware parameter detection method, a device and a firmware setting method.
In a first aspect, an embodiment of the present application provides a firmware parameter detection method, where the firmware parameter detection method includes:
reading a parameter setting document and a corresponding standard file;
acquiring firmware parameter information to be tested in a parameter setting document;
obtaining standard firmware parameter information in a standard file;
detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result;
the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not.
Optionally, the firmware parameter information to be tested in the parameter setting document includes: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: fixing the fixed firmware parameters and fixing the fixed values corresponding to the fixed firmware parameters;
detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result, wherein the detection result comprises the following steps:
judging whether the firmware parameters set in the parameter setting document contain standard firmware parameters in the standard file, judging whether the set value of the first firmware parameter is the same as the fixed value of the corresponding fixed firmware parameter,
If the firmware parameters set in the parameter setting document do not all contain standard firmware parameters in the standard file, or if any set value of the first firmware parameters is different from the fixed value of the corresponding fixed firmware parameters, determining that the parameter setting document has wrong firmware parameter information to be tested,
the first firmware parameter is a firmware parameter corresponding to the fixed firmware parameter in the set firmware parameters.
Optionally, the standard firmware parameter information further includes: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters;
detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result, and further comprising:
if the firmware parameters set in the parameter setting document all contain standard firmware parameters in the standard file and the set values of all the first firmware parameters are the same as the fixed values of the corresponding fixed firmware parameters, judging whether the set values of the second firmware parameters meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file,
if any set value of the second firmware parameters does not meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file, judging that the parameter setting file has wrong firmware parameter information to be tested,
The second firmware parameter is a firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters.
Optionally, the firmware parameter information to be tested in the parameter setting document includes: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters;
detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result, wherein the detection result comprises the following steps:
judging whether the set value of the second firmware parameter meets the corresponding relation between the corresponding non-fixed firmware parameters in the standard file,
wherein the second firmware parameter is the firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters,
if any set value of the second firmware parameters does not meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file, judging that the parameter setting document has wrong firmware parameter information to be tested.
Optionally, fixing the firmware parameters includes: doPretest, supportATAPassthrough, doQC, enableAPSTA, enableWriteProtect, PCIeSpeedIndex and pcie lane index.
Optionally, the non-fixed firmware parameters include: pretestOption, enableEndToEnd and keepdtritosult;
the correspondence between interrelated non-fixed firmware parameters includes: pretestOption, enableEndToEnd and keepdtresult.
Optionally, the firmware parameter detection method further includes:
after judging whether the parameter setting document has wrong firmware parameter information, reading the next parameter setting document and a corresponding standard file, and detecting the firmware parameter information to be detected in the next parameter setting document according to the standard firmware parameter information in the standard file corresponding to the next parameter setting document to obtain a detection result corresponding to the next parameter setting document until all the parameter setting documents to be detected are detected.
In a second aspect, an embodiment of the present application provides a firmware parameter detection apparatus, including:
the reading module is used for reading the parameter setting document and the corresponding standard file;
the first acquisition module is used for acquiring the firmware parameter information to be tested in the parameter setting document;
the second acquisition module is used for acquiring standard firmware parameter information in the standard file;
The judging module is used for detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result;
the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not.
In a third aspect, an embodiment of the present application provides a firmware setting method, including: carrying out firmware parameter detection on the parameter setting document to be called according to the firmware parameter detection method of any one of the above steps;
if the parameter setting document to be called does not have wrong firmware parameter information, parameter setting is carried out on the firmware to be opened according to the parameter setting document to be called.
Optionally, parameter setting is performed on the firmware to be card-opened according to the parameter setting document to be called, including:
and respectively carrying out parameter setting on parameters of the same address in the firmware to be opened by addressing according to the firmware parameter information in the parameter setting document to be called.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor causes the processor to perform the steps of a firmware parameter detection method as in any one of the preceding claims.
In a fifth aspect, embodiments of the present application provide a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the steps of the firmware parameter detection method as in any of the preceding claims when the program is executed.
In a sixth aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor causes the processor to perform the steps of the firmware setting method as in any one of the preceding claims.
In a seventh aspect, embodiments of the present application provide a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the steps of the firmware setting method as in any of the preceding claims when the program is executed.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the technical scheme provided by the embodiment of the application, the parameter setting document and the corresponding standard file are read, and the firmware parameter information in the parameter setting document is detected according to the standard firmware parameter information in the standard file, so that whether the parameter setting document has wrong firmware parameter information or not is judged. If the parameter setting document has no wrong firmware parameter information, the parameter setting is carried out on the firmware to be opened according to the parameter setting document, the firmware parameter is automatically detected, the accuracy of the parameter setting of the firmware is ensured, the parameter detection is not needed to be carried out on the firmware with the set parameter again, the manpower and material resources are saved, and the production efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a flowchart of a firmware parameter detection method according to an embodiment;
FIG. 2 is a block diagram of a firmware parameter detection apparatus according to an embodiment;
fig. 3 is a block diagram of a computer device according to one embodiment.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present application based on the embodiments herein.
Fig. 1 is a flowchart of a firmware parameter detection method according to an embodiment. Referring to fig. 1, the firmware parameter detection method includes the steps of:
s100: and reading the parameter setting document and the corresponding standard file.
S200: and acquiring the parameter information of the firmware to be tested in the parameter setting document.
S300: and acquiring standard firmware parameter information in the standard file.
S400: and detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result.
And detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file so as to judge whether the parameter setting document has wrong firmware parameter information to be detected.
Specifically, firmware (Firmware) is a program written in EPROM (erasable programmable read only memory) or EEPROM (electrically erasable programmable read only memory).
Firmware refers to a device "driver" stored inside the device, through which the operating system can implement the running actions of a specific machine according to a standard device driver.
Firmware (firmware) is typically stored in an electrically erasable read-only memory EEPROM (Electrically Erasable Programmable ROM) or FLASH chip in the device, a program that can be upgraded by a user, typically by a specific refresh program. Generally, software that is the most Basic and bottom-level of a digital product can be called firmware, such as Basic Input/output System (BIOS) on a computer motherboard.
In the production process of the solid state disk, the firmware is required to be written into the solid state disk, so that the assembled solid state disk can realize various basic functions under the action of the firmware. Since firmware is a type of software, firmware needs to set specific firmware parameters to meet specific requirements. Thus, the setting of firmware parameters may be different for different needs and different vendors. In actual production, a case where a firmware parameter setting error may occur.
Before the firmware is downloaded into the solid state disk, various firmware parameter settings are required to be carried out on the firmware, and in order to ensure the correctness of the firmware parameters, whether the firmware parameters to be tested in the parameter setting document are correct or meet the requirements is required to be detected before the firmware parameter settings are carried out on the firmware. The parameter setting document is a document for parameter setting of firmware, and the computer device performs firmware parameter setting of firmware according to the parameter setting document. The parameters of each firmware in the parameter setting document are set by engineering personnel according to the actual production requirements and the direction of manufacturers. Thus, the firmware parameters in the parameter setting document may be inadvertently erroneous. It is necessary to detect the parameter setting document.
The standard file is a standard setting of firmware parameters well known in the industry. Each parameter setting document corresponds to a standard file. Typically, the number of standard firmware parameters in the standard file is no more than the firmware parameters in the parameter setting document. Therefore, the standard file detects only part of the firmware parameters (firmware parameters to be tested) in the parameter setting document.
Specifically, the standard file is used as a standard reference, and the firmware parameter information to be tested in the parameter setting file is compared with the standard firmware parameter information in the corresponding standard file. If the settings of each standard firmware parameter in the standard file have the same settings in the parameter setting document, it is determined that there is no erroneous firmware parameter information to be tested in the parameter setting document. If any one of the standard firmware parameters is set differently from the parameter setting document in the standard file, it is determined that there is erroneous firmware parameter information to be tested in the parameter setting document.
If the detection result is that the parameter setting document has no wrong firmware parameter information to be detected, outputting a success prompt, and if the detection result is that the parameter setting document has wrong firmware parameter information, outputting an error prompt. The error reporting prompt may be to pop up an error reporting window or button on the display screen and/or display error parameter information on the display screen. The error reporting prompt can also be a prompt for a worker through an audible and visual alarm.
The firmware parameter detection method is applied to the pre-test before the firmware is downloaded or set before the parameter setting is carried out on the firmware.
If the parameter setting document has no wrong parameter information of the firmware to be tested, the parameter setting is carried out on the firmware to be opened according to the parameter setting document, the firmware parameters are automatically detected, the accuracy of the parameter setting of the firmware is ensured, the firmware with the set parameters is not required to be subjected to parameter detection again, the manpower and material resources are saved, and the production efficiency is improved. The reliability of the firmware is also improved, and the productivity is optimized.
In a specific embodiment, the firmware parameter detection method can also be applied to loop automatic batch detection of various parameter setting documents.
Specifically, reading a current parameter setting document and a corresponding standard file;
detecting the firmware parameter information to be tested in the current parameter setting document according to the standard firmware parameter information in the standard file corresponding to the current parameter setting document so as to judge whether the current parameter setting document has wrong firmware parameter information to be tested;
judging whether a parameter setting document to be detected exists or not;
if the parameter setting document to be detected still exists, reading the next parameter setting document and the corresponding standard file, and detecting the firmware parameter information to be detected in the next parameter setting document according to the standard firmware parameter information in the standard file corresponding to the next parameter setting document, so as to judge whether the next parameter setting document has wrong firmware parameter information to be detected, and circulating in this way until all the parameter setting documents to be detected are detected or no parameter setting document to be detected exists.
In the embodiment, various different parameter setting documents are automatically detected in batches by circularly detecting various different parameter setting documents, so that the production efficiency is improved. Because the parameter setting documents are detected in advance before production, separate re-detection of each parameter setting document is no longer required in the actual production process so as not to delay the production progress.
In a specific embodiment, the firmware parameter information to be tested in the parameter setting document comprises: the set firmware parameters and the set values corresponding to the set firmware parameters.
The standard firmware parameters comprise standard firmware parameters and corresponding values.
The standard firmware parameter information includes: fixed firmware parameters and fixed values corresponding to the fixed firmware parameters. The standard firmware parameter information further includes: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters.
The firmware parameter information in the parameter setting document is set by an engineer according to the actual demand and the instruction of the manufacturer (software developer).
The standard firmware parameter information in the standard file is set according to standards known in the industry, and the standard firmware parameters include fixed firmware parameters and non-fixed firmware parameters.
The fixed firmware parameters are parameters which are inherent unchanged for realizing specific functions or specific support values, and the non-fixed firmware parameters can have a plurality of values, but the values of some non-fixed firmware parameters have corresponding relations or binding or corresponding relations.
For example: the non-fixed firmware parameters A, B, C have a correspondence, and when a=0, b=1, c=2; when a=1, b=2, c=3, and the like are similar to such correspondence.
Also for example: a=0, then B >1, c >2; when a=1, then B >2, c >3, and so on.
The correspondence relationship is not limited to a specific value, but may be a value range, a value formula, or the like.
In one embodiment, the firmware parameter information to be tested in the number setting document includes: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: fixed firmware parameters and fixed values corresponding to the fixed firmware parameters.
Step S400 specifically includes:
judging whether the firmware parameters set in the parameter setting document contain standard firmware parameters in the standard file or not, and judging whether the set value of the first firmware parameter is the same as the fixed value of the corresponding fixed firmware parameter or not;
If the firmware parameters set in the parameter setting document do not all contain standard firmware parameters in the standard file, or if any set value of the first firmware parameters is different from the fixed value of the corresponding fixed firmware parameters, judging that the parameter setting document has error firmware parameter information to be tested;
the first firmware parameter is a firmware parameter corresponding to the fixed firmware parameter in the set firmware parameters.
Specifically, if the standard firmware parameters only include fixed firmware parameters, the standard file is used as a standard, and whether the standard firmware parameter information included in the standard file exists in the parameter setting document or not is judged, and the settings are the same. Because the number of the firmware parameters contained in the parameter setting document is greater than that of the standard firmware parameters in the standard file, it is only necessary to detect whether the firmware parameters set in the parameter setting document contain all the standard firmware parameters in the standard file and determine whether the set value of the first firmware parameter contained in the parameter setting document is the same as the fixed value of the corresponding fixed firmware parameter in the standard file. The first firmware parameter is a firmware parameter corresponding to the fixed firmware parameter in the set firmware parameters.
If the firmware parameters set in the parameter setting document contain all standard firmware parameters (including all fixed firmware parameters) in the standard file, and the set value of the first firmware parameter contained in the parameter setting document is the same as the fixed value of the corresponding fixed firmware parameter in the standard file, determining that no error firmware parameter information to be tested exists in the parameter setting document.
If the firmware parameters set in the parameter setting document do not completely contain all the standard firmware parameters (do not contain all the fixed firmware parameters) in the standard file, or the set value of the first firmware parameter contained in the parameter setting document is not completely the same as the fixed value of the corresponding fixed firmware parameter in the standard file, determining that the firmware parameter information in the parameter setting document is wrong. The reason for the presence of erroneous firmware parameter information at this time is: and deleting part of standard firmware parameters in the parameter setting document, and/or, setting values of part of first firmware parameters in the parameter setting document are different from fixed values of corresponding standard firmware parameters in the standard document.
In one embodiment, if the standard firmware parameter information further includes: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters. Step S400 further includes:
If the firmware parameters set in the parameter setting document all contain standard firmware parameters in the standard file, and the set values of all the first firmware parameters are the same as the fixed values of the corresponding fixed firmware parameters,
judging whether the set value of the second firmware parameter meets the corresponding relation between the corresponding non-fixed firmware parameters in the standard file;
if any set value of the second firmware parameters does not meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file, judging that the parameter setting file has wrong firmware parameter information to be tested;
the second firmware parameter is a firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters.
Specifically, in the present embodiment, the firmware parameters set in the parameter setting document include a first firmware parameter and a second firmware parameter. The standard firmware parameters include fixed firmware parameters and non-fixed firmware parameters.
Taking the standard file as a standard, detecting whether the firmware parameters set in the parameter setting document contain all standard firmware parameters in the standard file, judging whether the set value of the first firmware parameter contained in the parameter setting document is the same as the fixed value of the corresponding fixed firmware parameter in the standard file, and judging whether the set value of the second firmware parameter contained in the parameter setting document meets the corresponding relation between the non-fixed firmware parameters which are related to each other in the standard file. The first firmware parameters are the firmware parameters which are set in the parameter setting document and are the same as the fixed firmware parameters; the second firmware parameter is a firmware parameter set in the same as the non-fixed firmware parameter in the parameter setting document.
If the firmware parameters set in the parameter setting document contain all standard firmware parameters in the standard file, the set values of the first firmware parameters contained in the parameter setting document are the same as the fixed values of the corresponding fixed firmware parameters in the standard file, and the set values of the second firmware parameters contained in the parameter setting document all meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file, then the fact that error firmware parameter information does not exist in the parameter setting document is judged. Otherwise, it is determined that there is erroneous firmware parameter information in the parameter setting document.
In one embodiment, if the firmware parameter information to be tested in the parameter setting document includes: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: the step S400 includes:
judging whether the set value of the second firmware parameter meets the corresponding relation between the corresponding non-fixed firmware parameters in the standard file;
if any set value of the second firmware parameters does not meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file, judging that the parameter setting file has wrong firmware parameter information to be tested;
The second firmware parameter is a firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters.
Specifically, if the standard firmware parameters only include the non-fixed firmware parameters, the standard file is used as a standard to determine whether the set value of the second firmware parameter in the parameter setting document meets the corresponding relation between the non-fixed firmware parameters associated with each other in the standard file. The second firmware parameter is a firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters. The firmware parameters set in the parameter setting document do not necessarily all have corresponding non-fixed firmware parameters in the standard file.
Because the number of firmware parameters contained in the parameter setting document is greater than the standard firmware parameters in the standard file, it is necessary to determine whether the set value of the second firmware parameter contained in the parameter setting document satisfies the correspondence between the corresponding interrelated non-fixed firmware parameters in the standard file.
If the set values of the second firmware parameters contained in the parameter setting document all meet the corresponding relation between the corresponding non-fixed firmware parameters which are associated with each other in the standard file, judging that the parameter setting document has no error firmware parameter information to be tested.
If the set values of the second firmware parameters contained in the parameter setting document do not all meet the corresponding relation between the corresponding non-fixed firmware parameters which are associated with each other in the standard file, judging that the parameter setting document has wrong firmware parameter information to be tested. The reason for the presence of erroneous firmware parameter information at this time is: and a part of the setting values of the second firmware parameters do not meet the corresponding correspondence relation between the corresponding non-fixed firmware parameters which are associated with each other in the standard file.
In one particular embodiment, fixing the firmware parameters includes: doPretest, supportATAPassthrough, doQC, enableAPSTA, enableWriteProtect, PCIeSpeedIndex and pcie lane index.
In one particular embodiment, the non-fixed firmware parameters include: pretestOption, enableEndToEnd and keepdtritosult. The correspondence between interrelated non-fixed firmware parameters includes: pretestOption, enableEndToEnd and keepdtresult.
Specifically, the standard firmware parameters include fixed firmware parameters and non-fixed firmware parameters, where DoPretest, supportATAPassthrough, doQC, enableAPSTA, enableWriteProtect, PCIeSpeedIndex and pcie lane index are both fixed firmware parameters. PretestOption, enableEndToEnd and keepdtresult are both non-fixed firmware parameters.
When the standard firmware parameters include only fixed firmware parameters, the standard firmware parameters include at least one of DoPretest, supportATAPassthrough, doQC, enableAPSTA, enableWriteProtect, PCIeSpeedIndex and pcie lane index. Of course, the fixed firmware parameters may also include FormFactor.
For software provided by different manufacturers, standard firmware parameters are different, and values are also different. The foregoing list only a portion of the fixed and non-fixed firmware parameters, and the present application is not so limited.
In a specific embodiment, taking firmware software provided by a certain manufacturer as an example, the value of doptest is 1, which indicates that a pre-test needs to be performed before downloading the firmware; the value of the FormFactor is 4, which means that the solid state disk interface is M.2; the suppatappasthreugh value is 1, the doqc value is 1, the enableappta value is 1, the enablewriteprotection value is 1, the pcie apeedindex value is 2, and the pcie lane index value is 2.
Correspondence relationship such as: if pretestoption=1, then enableendtend=0, keepdtresult=0.
If pretestoption=2, then enableendtend=1, keepdtresult=1.
If pretestoption=3, then enableendtend=1, keepdtresult=1.
The firmware parameters in the parameter setting document corresponding to the standard file must include all the standard firmware parameters of the standard file, the fixed firmware parameters in the parameter setting document must have the same values as those described above, and the non-fixed firmware parameters in the parameter setting document must have values satisfying the correspondence relationship described above, so that the parameter setting document can determine that there is no erroneous firmware parameter information.
Of course, other firmware parameters may also be included in the parameter settings document, such as: modelName represents the product type name, FWRevision represents the firmware version number, flashPatnum represents the Flash granule model, etc. firmware parameters that do not need to be detected.
The extensions of both the parameter setting document and the standard file may be. Ini.
Through the method and the device, the firmware parameter checking efficiency is improved, the reliability of the solid state disk firmware is further improved, and the production quality is improved.
Fig. 2 is a block diagram of a firmware parameter detection apparatus according to an embodiment. Referring to fig. 2, the apparatus includes:
a reading module 100, configured to read the parameter setting document and the corresponding standard file;
the first obtaining module 200 is configured to obtain firmware parameter information to be tested in the parameter setting document;
The second obtaining module 300 is configured to obtain standard firmware parameter information in a standard file;
the judging module 400 is configured to detect the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file, so as to obtain a detection result;
the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not.
In a specific embodiment, the firmware parameter information to be tested in the parameter setting document comprises: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: fixing the firmware parameters and fixing the fixed values corresponding to the fixing firmware parameters.
In this embodiment, the judging module 400 specifically includes:
a first judging unit for judging whether the firmware parameters set in the parameter setting document contain standard firmware parameters in the standard document;
the second judging unit is used for judging whether the set value of the first firmware parameter is the same as the fixed value of the corresponding fixed firmware parameter;
the first judging unit is used for judging that the parameter setting document has wrong firmware parameter information to be tested if the firmware parameters set in the parameter setting document do not all contain the standard firmware parameters in the standard document or if any set value of the first firmware parameters is different from the fixed value of the corresponding fixed firmware parameters;
The first firmware parameter is a firmware parameter corresponding to the fixed firmware parameter in the set firmware parameters.
On the basis of the above specific embodiment, the standard firmware parameter information further includes: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters.
The judging module 400 specifically further includes:
the third judging unit is used for judging whether the set value of the second firmware parameter meets the corresponding relation between the corresponding non-fixed firmware parameters in the standard file or not if the set value of the first firmware parameter is the same as the fixed value of the corresponding fixed firmware parameter and the set value of the firmware parameter set in the parameter setting document completely comprises the standard firmware parameters in the standard file;
the second judging unit is used for judging that the parameter setting document has wrong firmware parameter information to be tested if any set value of the second firmware parameters does not meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file;
the second firmware parameter is a firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters.
In a specific embodiment, the firmware parameter information to be tested in the parameter setting document comprises: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters.
The judging module 400 specifically includes:
a fourth judging unit, configured to judge whether the set value of the second firmware parameter meets a corresponding relationship between corresponding non-fixed firmware parameters associated with each other in the standard file;
a third judging unit, configured to judge that the parameter setting document has erroneous firmware parameter information to be tested if any one of the second firmware parameter setting values does not satisfy the corresponding relation between the corresponding non-fixed firmware parameters in the standard file;
the second firmware parameter is a firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters.
In a specific embodiment, the apparatus further comprises:
the loop module is used for sequentially jumping to the reading module 100 to read the next parameter setting document and the corresponding standard file after judging whether the parameter setting document has wrong firmware parameter information to be tested, the first acquisition module 200 acquires the firmware parameter information to be tested in the parameter setting document, the second acquisition module 300 acquires the standard firmware parameter information in the standard file, and the judging module 400 detects the firmware parameter information to be tested in the next parameter setting document according to the standard firmware parameter information in the standard file corresponding to the next parameter setting document, so as to obtain a detection result corresponding to the next parameter setting document until all the parameter setting documents to be detected are detected.
The application also provides a firmware setting method, which comprises the following steps: the firmware parameter detection method is used for carrying out firmware parameter detection on the parameter setting file to be called according to any one of the above methods, and if the parameter setting file to be called does not have wrong firmware parameter information to be detected, the parameter setting is carried out on the firmware to be opened according to the parameter setting file to be called.
The method is equivalent to pre-detecting the parameter setting file to be called by a firmware parameter detection method before parameter setting is carried out on the firmware, and the parameter setting file to be called meets the requirements and is used for parameter setting on the firmware.
In a specific embodiment, parameter setting is performed on firmware to be card-opened according to a parameter setting document to be called, including:
and respectively carrying out parameter setting on parameters of the same address in the firmware to be opened by addressing according to the firmware parameter information in the parameter setting document to be called.
Specifically, each firmware parameter in the parameter setting document is provided with a corresponding address, the address also exists in the firmware, and the parameter at the same address of the parameter setting document and the firmware is regarded as the same parameter, so that the set value or the value is the same. Therefore, the parameter setting of the firmware according to the firmware parameters in the parameter setting file is realized.
In a specific embodiment, the firmware setting apparatus includes:
the reading module 100 is used for reading the parameter setting document to be called and the corresponding standard file;
the first obtaining module 200 is configured to obtain firmware parameter information to be tested in a parameter setting document to be invoked;
the second obtaining module 300 is configured to obtain standard firmware parameter information in a standard file corresponding to the parameter setting document to be called;
the judging module 400 is configured to detect, according to standard firmware parameter information in a corresponding standard file, to-be-called firmware parameter information in a parameter setting document to obtain a detection result, where the detection result includes whether the to-be-called parameter setting document has erroneous to-be-detected firmware parameter information;
and the setting module is used for setting parameters of the firmware to be opened according to the parameter setting document to be called if the parameter setting document to be called does not have wrong parameter information of the firmware to be tested.
Fig. 3 is a block diagram of a computer device according to one embodiment. The computer device is connected with the processor, the memory, the network interface, the input device and the display screen through the system bus. The memory includes a nonvolatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system, and may also store a computer program that, when executed by a processor, causes the processor to implement a firmware parameter detection method and a firmware setting method. The internal memory may also store a computer program that, when executed by the processor, causes the processor to perform the firmware parameter detection method and the firmware setting method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 3 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of when executing the computer program: reading a parameter setting document and a corresponding standard file; acquiring firmware parameter information to be tested in a parameter setting document; obtaining standard firmware parameter information in a standard file; detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result; the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not.
The steps in the firmware parameter detection method described in any one of the above are also implemented when the processor executes the computer program.
In one embodiment, a computer device is provided comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of when executing the computer program: reading a parameter setting document to be called and a corresponding standard file; acquiring firmware parameter information to be tested in a parameter setting document to be called; acquiring standard firmware parameter information in a standard file corresponding to a parameter setting document to be called; detecting the parameter information of the firmware to be tested in the parameter setting document to be called according to the standard firmware parameter information in the corresponding standard file to obtain a detection result, wherein the detection result comprises whether the parameter setting document to be called has wrong parameter information of the firmware to be tested; if the parameter setting document to be called does not have wrong parameter information of the firmware to be detected, parameter setting is carried out on the firmware to be opened according to the parameter setting document to be called.
The processor, when executing the computer program, also implements the steps in the firmware setting method of any of the above.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of: reading a parameter setting document and a corresponding standard file; acquiring firmware parameter information to be tested in a parameter setting document; obtaining standard firmware parameter information in a standard file; detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result; the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not.
The computer program when executed by a processor also implements the steps of the firmware parameter detection method of any one of the above.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of: reading a parameter setting document to be called and a corresponding standard file; acquiring firmware parameter information to be tested in a parameter setting document to be called; acquiring standard firmware parameter information in a standard file corresponding to a parameter setting document to be called; detecting the parameter information of the firmware to be tested in the parameter setting document to be called according to the standard firmware parameter information in the corresponding standard file to obtain a detection result, wherein the detection result comprises whether the parameter setting document to be called has wrong parameter information of the firmware to be tested; if the parameter setting document to be called does not have wrong parameter information of the firmware to be detected, parameter setting is carried out on the firmware to be opened according to the parameter setting document to be called.
The computer program when executed by a processor also implements the steps in the firmware setting method of any of the above.
Those skilled in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, where the program may be stored in a non-volatile computer readable storage medium, and where the program, when executed, may include processes in the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely 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. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises 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. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is only a specific embodiment of the invention to enable those skilled in the art to understand or practice the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (9)

1. A method for detecting firmware parameters, the method comprising:
reading a parameter setting document and a corresponding standard file;
acquiring firmware parameter information to be tested in the parameter setting document;
acquiring standard firmware parameter information in the standard file;
detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result;
the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not;
the firmware parameter information to be tested in the parameter setting document comprises: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: fixing the firmware parameters and fixing the fixed values corresponding to the firmware parameters;
the step of detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result comprises the following steps:
judging whether the firmware parameters set in the parameter setting document contain standard firmware parameters in the standard file, judging whether the set value of the first firmware parameter is the same as the fixed value of the corresponding fixed firmware parameter,
If the firmware parameters set in the parameter setting document do not all contain the standard firmware parameters in the standard file, or if any set value of the first firmware parameters is different from the fixed value of the corresponding fixed firmware parameters, determining that the parameter setting document has wrong firmware parameter information to be tested,
the first firmware parameter is a firmware parameter corresponding to a fixed firmware parameter in the set firmware parameters.
2. The method of claim 1, wherein the standard firmware parameter information further comprises: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters;
the method comprises the steps of detecting the parameter information of the firmware to be detected in the parameter setting document according to the parameter information of the standard firmware in the standard file to obtain a detection result, and further comprises the following steps:
if the firmware parameters set in the parameter setting document all contain standard firmware parameters in the standard file and the set values of all the first firmware parameters are the same as the fixed values of the corresponding fixed firmware parameters, judging whether the set values of the second firmware parameters meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file,
If any set value of the second firmware parameters does not meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file, judging that the parameter setting file has wrong firmware parameter information to be tested,
the second firmware parameter is a firmware parameter corresponding to a non-fixed firmware parameter in the set firmware parameters.
3. The method of claim 1, wherein the firmware parameter information to be tested in the parameter setting document comprises: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: correspondence between non-fixed firmware parameters and interrelated non-fixed firmware parameters;
the step of detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result comprises the following steps:
judging whether the set value of the second firmware parameter meets the corresponding relation between the corresponding non-fixed firmware parameters in the standard file,
wherein the second firmware parameter is the firmware parameter corresponding to the non-fixed firmware parameter in the set firmware parameters,
If any set value of the second firmware parameters does not meet the corresponding relation between the corresponding non-fixed firmware parameters in the standard file, judging that the parameter setting file has wrong firmware parameter information to be tested.
4. The method of claim 1 or 2, wherein the fixed firmware parameters comprise: doPretest, supportATAPassthrough, doQC, enableAPSTA, enableWriteProtect, PCIeSpeedIndex and pcie lane index.
5. A method according to claim 2 or 3, wherein the non-fixed firmware parameters comprise: pretestOption, enableEndToEnd and keepdtritosult;
the correspondence between the interrelated non-fixed firmware parameters includes: pretestOption, enableEndToEnd and keepdtresult.
6. The method according to claim 1, wherein the method further comprises:
after judging whether the parameter setting document has wrong firmware parameter information, reading a next parameter setting document and a corresponding standard file, and detecting the firmware parameter information to be detected in the next parameter setting document according to the standard firmware parameter information in the standard file corresponding to the next parameter setting document to obtain a detection result corresponding to the next parameter setting document until all the parameter setting documents to be detected are detected.
7. A firmware parameter detection apparatus, the apparatus comprising:
the reading module is used for reading the parameter setting document and the corresponding standard file;
the first acquisition module is used for acquiring the firmware parameter information to be tested in the parameter setting document;
the second acquisition module is used for acquiring standard firmware parameter information in the standard file;
the judging module is used for detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result;
the detection result comprises firmware parameter information to be detected, whether the parameter setting document has errors or not;
the firmware parameter information to be tested in the parameter setting document comprises: the set firmware parameters and the set values corresponding to the set firmware parameters, and the standard firmware parameter information comprises: fixing the firmware parameters and fixing the fixed values corresponding to the firmware parameters;
the step of detecting the firmware parameter information to be detected in the parameter setting document according to the standard firmware parameter information in the standard file to obtain a detection result comprises the following steps:
judging whether the firmware parameters set in the parameter setting document contain standard firmware parameters in the standard file, judging whether the set value of the first firmware parameter is the same as the fixed value of the corresponding fixed firmware parameter,
If the firmware parameters set in the parameter setting document do not all contain the standard firmware parameters in the standard file, or if any set value of the first firmware parameters is different from the fixed value of the corresponding fixed firmware parameters, determining that the parameter setting document has wrong firmware parameter information to be tested,
the first firmware parameter is a firmware parameter corresponding to a fixed firmware parameter in the set firmware parameters.
8. A firmware setting method, the method comprising: the firmware parameter detection method according to any one of claims 1 to 6, wherein the firmware parameter detection is performed on a parameter setting document to be called;
and if the parameter setting document to be called does not have wrong firmware parameter information, parameter setting is carried out on the firmware to be opened according to the parameter setting document to be called.
9. The method of claim 8, wherein the parameter setting for the firmware to be carded according to the parameter setting document to be invoked comprises:
and respectively carrying out parameter setting on parameters of the same address in the firmware to be opened by addressing according to the firmware parameter information in the parameter setting document to be called.
CN202010954914.7A 2020-09-11 2020-09-11 Firmware parameter detection method, device and firmware setting method Active CN112216337B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010954914.7A CN112216337B (en) 2020-09-11 2020-09-11 Firmware parameter detection method, device and firmware setting method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010954914.7A CN112216337B (en) 2020-09-11 2020-09-11 Firmware parameter detection method, device and firmware setting method

Publications (2)

Publication Number Publication Date
CN112216337A CN112216337A (en) 2021-01-12
CN112216337B true CN112216337B (en) 2024-03-29

Family

ID=74049302

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010954914.7A Active CN112216337B (en) 2020-09-11 2020-09-11 Firmware parameter detection method, device and firmware setting method

Country Status (1)

Country Link
CN (1) CN112216337B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113342420A (en) * 2021-06-28 2021-09-03 杭州涂鸦信息技术有限公司 Firmware configuration method, device, equipment and storage medium
CN115250291B (en) * 2022-07-28 2024-03-22 中国银行股份有限公司 Parameter data verification method, device, equipment and readable storage medium

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104008089A (en) * 2013-02-25 2014-08-27 国际商业机器公司 Method and system used for validation for documentation
CN105190596A (en) * 2012-09-07 2015-12-23 美国化学协会 Automated composition evaluator
CN107301137A (en) * 2017-07-04 2017-10-27 福建中金在线信息科技有限公司 RSET interface realizing methods and device and electronic equipment and computer-readable recording medium
CN107797776A (en) * 2016-08-31 2018-03-13 京瓷办公信息系统株式会社 For handling the method and system of linearisation and non-linearization pdf document
CN207503200U (en) * 2015-05-18 2018-06-15 米沃奇电动工具公司 Power tool equipment and the external equipment suitable for communicating
CN108459921A (en) * 2018-02-23 2018-08-28 北京奇艺世纪科技有限公司 Collapse file memory method, device and electronic equipment
CN110231559A (en) * 2019-05-17 2019-09-13 航天科工防御技术研究试验中心 Fpga chip parameter test method and equipment based on FLASH technique
CN110457553A (en) * 2019-08-21 2019-11-15 屈东海 Batch file processing method, device, equipment and storage medium
CN110781664A (en) * 2019-10-12 2020-02-11 北京字节跳动网络技术有限公司 File repair method and device
CN110825401A (en) * 2018-08-08 2020-02-21 广达电脑股份有限公司 Method and device for setting input document by authentication firmware

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7168092B2 (en) * 2000-08-31 2007-01-23 Sun Microsystems, Inc. Configuring processing units
US20100049738A1 (en) * 2008-08-20 2010-02-25 Alok Mathur System and method for user interface diagnostic activity logging

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105190596A (en) * 2012-09-07 2015-12-23 美国化学协会 Automated composition evaluator
CN104008089A (en) * 2013-02-25 2014-08-27 国际商业机器公司 Method and system used for validation for documentation
CN207503200U (en) * 2015-05-18 2018-06-15 米沃奇电动工具公司 Power tool equipment and the external equipment suitable for communicating
CN107797776A (en) * 2016-08-31 2018-03-13 京瓷办公信息系统株式会社 For handling the method and system of linearisation and non-linearization pdf document
CN107301137A (en) * 2017-07-04 2017-10-27 福建中金在线信息科技有限公司 RSET interface realizing methods and device and electronic equipment and computer-readable recording medium
CN108459921A (en) * 2018-02-23 2018-08-28 北京奇艺世纪科技有限公司 Collapse file memory method, device and electronic equipment
CN110825401A (en) * 2018-08-08 2020-02-21 广达电脑股份有限公司 Method and device for setting input document by authentication firmware
CN110231559A (en) * 2019-05-17 2019-09-13 航天科工防御技术研究试验中心 Fpga chip parameter test method and equipment based on FLASH technique
CN110457553A (en) * 2019-08-21 2019-11-15 屈东海 Batch file processing method, device, equipment and storage medium
CN110781664A (en) * 2019-10-12 2020-02-11 北京字节跳动网络技术有限公司 File repair method and device

Also Published As

Publication number Publication date
CN112216337A (en) 2021-01-12

Similar Documents

Publication Publication Date Title
CN112216337B (en) Firmware parameter detection method, device and firmware setting method
CN107766236B (en) Test task automatic management method, device, equipment and storage medium
US7293204B2 (en) Computer peripheral connecting interface system configuration debugging method and system
CN110704304B (en) Application program testing method and device, storage medium and server
CN112540725A (en) Nonvolatile data storage method, embedded system and storage medium
CN105045671B (en) The method for upgrading system and device of a kind of intelligent terminal
CN114020682A (en) Chip working mode control method and device, chip and storage medium
CN109684205B (en) System testing method, device, electronic equipment and storage medium
CN110633196A (en) Automatic use case execution method and device of application program
CN111857882A (en) Extensible SSD (solid State disk) firmware loading method and device, computer equipment and storage medium
JPWO2020065804A1 (en) Eligibility automatic judgment system
CN115167886B (en) Automatic adaptation method, device, storage medium and electronic equipment
CN109426506B (en) Loading method for selecting read-only memory
CN116775501B (en) Software testing method, server, readable storage medium and chip system
CN106970809A (en) A kind of method and apparatus of safety upgrade file system
CN102609242B (en) Electronic installation and internal memory control method thereof and related computer readable get Storage Media
CN112559370A (en) Front-end-based React project unit testing method and related equipment
CN115422910A (en) Source code difference comparison method and related device
CN116820967A (en) Performance test method and device, computer equipment and storage medium
CN115758954A (en) Particle model adaptation degree parameter acquisition method, device, equipment and medium
CN114546733A (en) Firmware loading method, chip and electronic equipment
CN115640223A (en) Software product testing method, computer device and storage medium
JP4601968B2 (en) IC card and IC card program that eliminates data integrity check
CN115629786A (en) Method and device for upgrading capacitive screen firmware of mobile terminal
CN117093490A (en) Code processing method, device, computer equipment 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
GR01 Patent grant
GR01 Patent grant