CN116701208A - Verification method, system, chip and device for kernel module in chip - Google Patents
Verification method, system, chip and device for kernel module in chip Download PDFInfo
- Publication number
- CN116701208A CN116701208A CN202310677765.8A CN202310677765A CN116701208A CN 116701208 A CN116701208 A CN 116701208A CN 202310677765 A CN202310677765 A CN 202310677765A CN 116701208 A CN116701208 A CN 116701208A
- Authority
- CN
- China
- Prior art keywords
- verification
- module
- chip
- tested
- kernel module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012795 verification Methods 0.000 title claims abstract description 353
- 238000000034 method Methods 0.000 title claims abstract description 49
- 230000015654 memory Effects 0.000 claims description 15
- 230000006870 function Effects 0.000 claims description 14
- 238000012360 testing method Methods 0.000 claims description 6
- 238000013075 data extraction Methods 0.000 claims description 4
- 238000012986 modification Methods 0.000 abstract description 6
- 230000004048 modification Effects 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 7
- 238000013461 design Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- 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/3684—Test management for test design, e.g. generating new test cases
-
- 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/3696—Methods or tools to render software testable
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a verification method, a verification system, a verification chip and verification equipment for a kernel module in a chip. The verification method of the kernel module in the chip comprises the following steps: acquiring module verification environment information of a core module to be tested in a chip, and acquiring a verification intermediate file for verifying the core module to be tested according to the verification environment information; newly creating a verification case in a chip verification environment of the SOC chip integrated with the kernel module to be tested, and performing configuration operation, starting operation and comparison operation on the kernel module to be tested according to a verification intermediate file in the verification case to obtain a comparison result of the kernel module to be tested; and judging whether the kernel module to be tested passes the verification or not based on the comparison result. The invention can effectively improve the efficiency of verifying the kernel module in the chip, reduce the workload of code modification, reduce the verification cost, reduce the modification of the chip verification environment, and realize the decoupling of the module verification environment and the chip verification environment.
Description
Technical Field
The present invention relates to the field of chip technologies, and in particular, to a method, a system, a chip, and an apparatus for verifying a kernel module in a chip.
Background
Various IPs (Intellectual Property, kernel modules) are integrated into a SoC (System on Chip) Chip, and after integrating the IPs onto the SoC, soC level verification needs to be performed on the IPs. The IP verification environment needs to be transplanted into the SOC verification environment during verification.
Because of the difference between the IP verification environment and the SOC verification environment, the architecture and the mechanism of the IP verification environment need to be firstly combed, then the architecture and the mechanism are modified aiming at the SOC verification environment and then are combined into the SOC verification environment, so that the workload of SOC level verification aiming at the IP is large, the verification time is long and the verification cost is high.
Disclosure of Invention
Based on this, it is necessary to address the above-mentioned problems and propose a verification method, system, chip and device for a kernel module in a chip.
A verification method of a kernel module in a chip comprises the following steps:
acquiring module verification environment information of a kernel module to be tested, and acquiring a verification intermediate file for verifying the kernel module to be tested according to the verification environment information;
newly creating a verification case in a chip verification environment of the SOC integrated with the core module to be tested, and performing configuration operation, starting operation and comparison operation on the core module to be tested according to the verification intermediate file in the verification case to obtain a comparison result of the core module to be tested;
and judging whether the kernel module to be tested passes verification or not based on the comparison result.
Wherein, the verification intermediate file includes: a register configuration file, a verification original file and a verification result file;
the steps of performing configuration operation, starting operation and verification operation on the kernel module to be tested according to the verification intermediate file in the verification use case include:
in the verification case, performing configuration operation and starting operation on the kernel module to be tested according to the register configuration file, so that the kernel module to be tested performs operation based on the verification original file to obtain actual operation data;
and comparing the actual operation data with the verification result file in the verification use case.
The step of performing configuration operation and starting operation on the kernel module to be tested according to the register configuration file in the verification case includes:
in the verification case, carrying out data extraction on the verification original file to obtain verification original data, and loading the extracted verification original data into a memory of the chip;
and carrying out corresponding configuration operation on the kernel module to be tested according to the register configuration file, and driving the kernel module to be tested which completes the configuration operation to read the verification original data in the memory for operation.
The step of performing corresponding configuration operation on the kernel module to be tested according to the register configuration file includes:
and extracting configuration operation data from the register configuration file, and reading and writing the register of the core module to be tested through the reading and writing function of the SOC chip.
The step of comparing the actual operation data with the verification result file in the verification case includes:
after the kernel module to be tested calculates to obtain actual operation data, the actual operation data is obtained from the memory;
analyzing the verification result file to obtain verification result data, and comparing the actual operation data with the verification result data.
The verification method of the kernel module in the chip further comprises the following steps:
and when the number of the verification scenes of the kernel module to be tested is multiple, acquiring module verification environment information corresponding to each verification scene, and executing the method according to the module verification environment information corresponding to each verification scene.
The verification method of the kernel module in the chip further comprises the following steps:
when the module verification environment changes, acquiring updated module verification environment information, and executing the method based on the updated module verification environment information;
when the chip verification environment changes, after the module verification environment information is acquired, a verification case is newly built in the updated chip verification environment, and the method is executed.
A verification system for a kernel module in a chip, comprising:
the file acquisition module is used for acquiring module verification environment information of the kernel module to be tested, and acquiring a verification intermediate file of the kernel module to be tested according to the verification environment information;
the use case module is used for creating a verification use case in a chip verification environment of the SOC chip integrated with the core module to be tested, and carrying out configuration operation, starting operation and verification operation on the core module to be tested according to the verification intermediate file in the verification use case to obtain a verification result of the core module to be tested;
and the judging module is used for judging whether the kernel module to be tested passes the verification or not based on the verification result.
A chip comprises at least one core module to be tested for implementing the steps of the method as described above.
A chip authentication device comprising at least one chip as described above.
The embodiment of the invention has the following beneficial effects:
the method comprises the steps of obtaining an authentication intermediate file adopted when the kernel module to be tested is authenticated in a module authentication environment, authenticating the kernel module to be tested in the chip authentication environment based on the same authentication intermediate file through a newly added authentication use case, extracting files required in the module authentication environment, configuring, starting and authenticating in the chip authentication environment, and directly authenticating in the chip authentication environment.
Furthermore, the invention realizes the verification operation of the kernel module to be tested in the chip verification environment by extracting the verification intermediate file in the module verification environment information for verifying the kernel module to be tested in the module verification environment and utilizing the verification intermediate file to perform the verification operation of the kernel module to be tested in the newly added verification use case in the chip verification environment, and does not need to transplant codes of the module verification environment into the chip verification environment, thereby realizing the decoupling of the module verification environment and the chip verification environment.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Wherein:
FIG. 1 is a flowchart of a first embodiment of a method for verifying a kernel module in a chip according to the present invention;
fig. 2 is a schematic diagram of an application scenario of a verification method of a kernel module in a chip provided by the invention;
FIG. 3 is a flowchart illustrating a second embodiment of a method for verifying a kernel module in a chip according to the present invention;
FIG. 4 is a flow chart of an embodiment of a verification system for a kernel module in a chip according to the present invention;
FIG. 5 is a schematic diagram of a chip according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an embodiment of a chip verification device provided by 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.
Referring to fig. 1 and fig. 2 in combination, fig. 1 is a flowchart illustrating a first embodiment of a method for verifying a kernel module in a chip according to the present invention. Fig. 2 is an application scenario schematic diagram of a verification method of a kernel module in a chip provided by the invention. The SOC chip is integrated with a plurality of IPs, each IP needs to be verified through an IP level verification environment in the early stage to detect the functions and the performances of the IP, and after the IP is integrated onto the SOC, the IP needs to be verified in the SOC level verification environment to detect whether the functions and the performances of the IP when being matched with other IPs meet the design requirements. Since there is a difference between the IP level authentication environment and the SOC level authentication environment, data of the IP level authentication environment cannot be directly applied to the SOC level authentication environment.
The verification method of the kernel module in the chip provided by the invention comprises the following steps:
s101: and acquiring module verification environment information of the kernel module to be tested in the chip, and acquiring a verification intermediate file for verifying the kernel module to be tested according to the verification environment information.
In a specific implementation scenario, verification is performed for each core module in the chip, which may be performed for the core modules sequentially or may be performed for multiple core modules simultaneously. Taking the kernel module to be verified as the kernel module to be tested, acquiring module verification environment information of a module verification environment of the kernel module to be tested, wherein the module verification environment information can be provided by a unit or department for carrying out IP level verification on the kernel module, or can be provided by a unit or department for carrying out IP level verification, and acquiring module verification environment information by the unit or department for carrying out SOC level verification through the module verification environment.
As shown in fig. 2, the core module under test (ip_dut) is verified under the module verification environment (ip_env) condition. And acquiring an authentication intermediate file used for authenticating the kernel module to be tested in the authentication environment information.
In one implementation scenario, validating the intermediate file includes: a register configuration file, a verification original file, and a verification result file. The register configuration file is used for indicating specific configuration operations of registers of the kernel module, such as partition setting of the registers, various parameter setting and the like. The verification original file is used to provide the data required for the kernel module operation. The verification result file is used for providing Golden results output by the kernel module when the IP level verification passes.
S102: and creating a verification case in a chip verification environment of the SOC chip integrated with the core module to be tested, and performing configuration operation, starting operation and comparison operation on the core module to be tested according to the verification intermediate file in the verification case to obtain a comparison result of the core module to be tested.
In a specific implementation scenario, a verification case is newly created in a chip verification environment of the SOC chip integrated with the core module to be tested, where the verification case is used to verify functions and performances of the core module to be tested in the chip verification environment. The verification use case is constructed based on the verification intermediate file, and can perform configuration operation, starting operation and verification operation on the kernel module to be tested based on the verification intermediate file. The configuration operation means that a register of the kernel module to be tested is configured so that the kernel module to be tested can have a function expected by a user, the starting operation means that the kernel module to be tested is driven to operate so as to obtain an operation result of the kernel module to be tested, the verification operation means that the operation result of the kernel module to be tested is detected, and whether the operation result meets the result expected by the user or not is judged.
In one implementation scenario, in the verification case, configuration operation and starting operation are performed on the kernel module to be tested according to the register configuration file, so that the kernel module to be tested performs operation based on the verification original file, and actual operation data is obtained. Specifically, the specific configuration operation to be executed by the register when the register is verified in the module verification environment of the kernel module to be tested is obtained according to the register configuration file, and the read-write of the register of the kernel module to be tested is realized through the read-write program of the chip, so that the configuration operation and the starting operation of the kernel module to be tested are realized.
And when the kernel module to be tested is started, carrying out operation on the data provided by the verification original file, and obtaining actual operation data by carrying out operation on the kernel module to be tested in a chip verification environment. And acquiring operation result data of the kernel module to be tested when the verification passes in the module verification environment according to the verification result file, and comparing the actual operation data with the operation result data to acquire a comparison result.
In the scenario shown in fig. 2, the intermediate file is applied to the chip verification environment (soc_env) through file parsing, and the chip verification environment (soc_env) verifies the core module under test (ip_dut) in the SOC chip (soc_dut) integrated with the core module under test through the Network On Chip (NOC). The data required by verification and the data output by operation of the kernel module to be tested (IP_DUT) are stored in the DDR. S103: and judging whether the kernel module to be tested passes the verification or not based on the comparison result.
In a specific implementation scenario, a comparison result of comparing actual operation data with operation result data is obtained, and if the actual operation data and the operation result data are matched, the verification of the core module to be tested in the chip verification environment is passed. If the two modules are not matched, the fact that the verification of the core module to be tested in the chip verification environment is not passed is indicated, and if the two modules are not matched, the fact that the function of the module in the chip is incorrect is indicated, and the chip design needs to be modified.
The verification intermediate file in the module verification environment information for verifying the kernel module to be tested in the module verification environment is extracted, and the verification intermediate file is utilized to verify the kernel module to be tested in the newly added verification use case in the chip verification environment, so that the verification operation of the kernel module to be tested in the chip verification environment is directly realized, and the code of the module verification environment is not required to be transplanted into the chip verification environment, so that the decoupling of the module verification environment and the chip verification environment is realized.
In other implementation scenarios, when the module verification environment of the kernel module to be tested changes, new module verification environment information is acquired according to the modified module verification environment, and the steps are executed based on the new module verification environment information, so that whether the kernel module to be tested can pass verification in the chip verification environment is judged.
In other implementation scenarios, when the chip verification environment of the chip changes, the steps are implemented in the verification case in the new chip verification environment based on the new module verification environment information, so as to judge whether the core module to be tested can pass the verification in the chip verification environment.
In other implementation scenarios, when a core module to be tested has a plurality of verification scenarios in a chip, corresponding module verification environment information can be obtained for each verification scenario, and the steps are executed for the module verification environment information corresponding to each verification scenario, so that whether the core module to be tested can pass through verification in each verification scenario of the chip verification environment is judged.
The steps are implemented without analyzing the mechanism and architecture of the module verification environment and transplanting the code of the module verification environment into the chip verification environment, so that the work of code adaptation and transplanting is not needed. The verification time is shortened, the code quantity of verification compilation is reduced, the verification efficiency is effectively improved, and the verification cost is also reduced. The framework and the structure of the whole chip verification environment do not need to be modified, and verification of the core module to be tested in the chip verification environment can be realized by only adding a required verification case (testcase). The decoupling of the module verification environment and the chip verification environment is realized, and when the chip verification environment is modified, the module verification environment does not need to be changed. When the module verification environment is modified, only new verification environment information is acquired according to the new module verification environment, and iteration of the module verification environment can be realized by verifying the module verification environment based on the new verification environment information.
Through the above description microcontrol, in this embodiment, the module verification environment is not required to be carded, and then the module verification environment is adapted to the chip verification environment and then is integrated into the chip verification environment, and finally the core module to be tested can be verified through the chip verification environment integrated into the module verification environment, but the core module to be tested is verified through the newly added verification use case in the chip verification environment, so that the efficiency of verifying the core module in the chip can be effectively improved, the workload of code modification is reduced, the verification cost is reduced, and the modification to the chip verification environment is reduced.
Referring to fig. 3, fig. 3 is a flowchart illustrating a second embodiment of a verification method for a kernel module in a chip according to the present invention.
S201: the method comprises the steps of operating a module verification environment of a kernel module to be tested, and obtaining register configuration information, verification original data information and verification result information generated in the operation process; and acquiring a register configuration file according to the register configuration information, acquiring a verification original file according to the verification original data information, and acquiring a verification result file according to the verification result information.
In a specific implementation scenario, a module verification environment of a kernel module to be tested is obtained, the module verification environment is operated, and register configuration information, verification original data information and verification result information are generated in the process of operating the module verification environment. The register configuration information refers to a configuration result of a register of the kernel module to be tested in a module verification environment, verification original data information is data adopted when the kernel module to be tested is verified in the module verification environment, and verification result information is Golden result output when the kernel module to be tested passes verification in the module verification environment.
In one implementation scenario, configuration operation information is obtained from a register read-write function of a module verification environment; extracting verification original data information from a function of loading original data of a module verification environment; and extracting verification result information from a result comparison function of the module verification environment.
And converting the register configuration information, the verification original data information and the verification result information into a format suitable for a chip verification environment. And acquiring a register configuration file according to the register configuration information, acquiring a verification original file according to the verification original data information, and acquiring a verification result file according to the verification result information.
S202: and creating a verification case in the chip verification environment.
In a specific implementation scenario, a verification case is created in the chip verification environment. The chip authentication environment does not need to be modified.
S203: in the verification use case, data extraction is carried out on the verification original file to obtain verification original data, and the extracted verification original data is loaded into a memory of the chip.
In a specific implementation scenario, data extraction is performed on an original verification file in a verification use case, so as to obtain original verification data corresponding to the original verification file, wherein the original verification data is data required by operation of a kernel module to be tested when the kernel module to be tested is verified. The extracted verification original data is loaded into a memory of the chip through a front door or a back door. The Memory may be SRAM (Static Random-Access Memory) or DDR SDRAM (Double Data Rate, synchronous Dynamic Random Access Memory Double Rate synchronous dynamic Random Access Memory).
S204: and extracting configuration operation data from the register configuration file, and reading and writing the register of the kernel module to be tested through the read-write function of the chip to realize the configuration operation matched with the configuration operation data on the kernel module to be tested.
In a specific implementation scenario, the configuration operation on the kernel module to be tested is implemented in the newly added verification case, configuration operation data is extracted from the register configuration file, the configuration operation matched with the configuration operation data is obtained, and the register of the kernel module to be tested is read and written through the read-write function of the chip, so that the configuration operation on the kernel module to be tested is implemented, and the kernel module to be tested is in the same state running in the module verification environment. Therefore, the operation of the kernel module to be tested in the chip verification environment can be realized without transplanting codes of the module verification environment into the chip verification environment.
S205: when the operation of the kernel module to be tested is finished, acquiring actual operation data from a memory; analyzing the verification result file to obtain verification result data, and comparing the actual operation data with the verification result data.
In a specific implementation scenario, after the operation of the kernel module to be tested is finished, outputting the result of the actual operation to a memory of the chip, acquiring actual operation data from a front door or a back door in the memory, analyzing the verification result file to acquire verification result data, wherein the verification result data is data which should be output when the kernel module to be tested passes the verification, comparing the actual operation data with the verification result data, and if the two are matched, indicating that the kernel module to be tested passes the verification in the chip verification environment. If the two modules are not matched, the fact that the verification of the core module to be tested in the chip verification environment is not passed is indicated, and if the two modules are not matched, the fact that the function of the module in the chip is incorrect is indicated, and the chip design needs to be modified.
As can be seen from the above description, in this embodiment, a verification case is newly created in the chip verification environment, configuration and starting of the kernel module to be tested are implemented in the verification case, and automatic comparison is performed on the operation result of the kernel module to be tested, so that it is not necessary to migrate the code of the module verification environment into the chip verification environment, so that the efficiency of verifying the kernel module in the chip is effectively improved, the workload of modifying the code is reduced, the verification cost is reduced, and the modification to the chip verification environment is reduced.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an embodiment of a verification system for a kernel module in a chip according to the present invention. The verification system 10 of the on-chip kernel module includes: a file acquisition module 11, a use case module 12 and a judgment module 13.
The file acquisition module 11 is used for acquiring module verification environment information of the kernel module to be tested, and acquiring a verification intermediate file of the kernel module to be tested according to the verification environment information; the use case module 12 is configured to create a verification use case in a chip verification environment of the SOC chip integrated with the core module to be tested, and perform configuration operation, starting operation and verification operation on the core module to be tested according to the verification intermediate file in the verification use case, so as to obtain a verification result of the core module to be tested; the judging module 13 is configured to judge whether the kernel module to be tested passes the verification based on the verification result.
The file obtaining module 11, the use case module 12 and the judging module 13 are configured to implement the method shown in any one of fig. 1 and fig. 2 in cooperation with each other.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a chip according to an embodiment of the invention. The chip 20 comprises at least one (2 in fig. 5, and may be a plurality in other implementation scenarios) core module 21 under test, and in other implementation scenarios, the core module 21 under test may comprise other core modules or memories, registers, arithmetic units, and so on. The chip 20 is capable of implementing the method described above and will not be described in detail here.
Referring to fig. 6, fig. 6 is a schematic structural diagram of an embodiment of a chip verification device according to the present invention. The chip authentication device comprises at least one chip 31, the at least one chip 31 being the chip shown in fig. 5. The chip authentication device 30 is capable of driving at least one chip 31 to implement the method as described above, and will not be described in detail here.
In the several embodiments provided by the present invention, it should be understood that the disclosed systems and methods may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of units is only one logical function division, and there may be other divisions in actual implementation, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described as separate units may or may not be physically separate, and units displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present invention may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: various media capable of storing program codes, such as a mobile storage device, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, and an optical disk.
Alternatively, the above-described integrated units of the present invention may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present invention may be embodied in essence or a part contributing to the prior art in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.
The methods disclosed in the method embodiments provided by the invention can be arbitrarily combined under the condition of no conflict to obtain a new method embodiment.
The features disclosed in the several product embodiments provided by the invention can be combined arbitrarily under the condition of no conflict to obtain new product embodiments.
The features disclosed in the embodiments of the method or the apparatus provided by the invention can be arbitrarily combined without conflict to obtain new embodiments of the method or the apparatus.
The foregoing is a further detailed description of the invention in connection with the preferred embodiments, and it is not intended that the invention be limited to the specific embodiments described. It will be apparent to those skilled in the art that several equivalent substitutions and obvious modifications can be made without departing from the spirit of the invention, and the same should be considered to be within the scope of the invention.
Claims (10)
1. A method for verifying a kernel module in a chip, comprising:
acquiring module verification environment information of a kernel module to be tested in a chip, and acquiring a verification intermediate file for verifying the kernel module to be tested according to the verification environment information;
newly creating a verification case in a chip verification environment of the SOC integrated with the core module to be tested, and performing configuration operation, starting operation and comparison operation on the core module to be tested according to the verification intermediate file in the verification case to obtain a comparison result of the core module to be tested;
and judging whether the kernel module to be tested passes verification or not based on the comparison result.
2. The method for verifying a kernel module in a chip as defined in claim 1, wherein the verifying an intermediate file comprises: a register configuration file, a verification original file and a verification result file;
the steps of performing configuration operation, starting operation and verification operation on the kernel module to be tested according to the verification intermediate file in the verification use case include:
in the verification case, performing configuration operation and starting operation on the kernel module to be tested according to the register configuration file, so that the kernel module to be tested performs operation based on the verification original file to obtain actual operation data;
and comparing the actual operation data with the verification result file in the verification use case.
3. The method for verifying a kernel module on a chip according to claim 2, wherein the step of performing a configuration operation and a start operation on the kernel module under test according to the register configuration file in the verification case includes:
in the verification case, carrying out data extraction on the verification original file to obtain verification original data, and loading the extracted verification original data into a memory of the chip;
and carrying out corresponding configuration operation on the kernel module to be tested according to the register configuration file, and driving the kernel module to be tested which completes the configuration operation to read the verification original data in the memory for operation.
4. A method for verifying a kernel module in a chip as defined in claim 3, wherein the step of performing a corresponding configuration operation on the kernel module to be tested according to the register configuration file comprises:
and extracting configuration operation data from the register configuration file, and reading and writing the register of the core module to be tested through the reading and writing function of the SOC chip.
5. The method for verifying a kernel module in a chip as defined in claim 2, wherein the step of comparing the actual operation data with the verification result file in the verification case comprises:
after the kernel module to be tested calculates to obtain actual operation data, the actual operation data is obtained from the memory;
analyzing the verification result file to obtain verification result data, and comparing the actual operation data with the verification result data.
6. The method for verifying a kernel module in a chip as defined in claims 1-5, wherein the method for verifying a kernel module in a chip further comprises:
when the number of verification scenes of the kernel module to be tested is multiple, module verification environment information corresponding to each verification scene is obtained, and the method according to any one of claims 1-5 is executed aiming at the module verification environment information corresponding to each verification scene.
7. The method for verifying a kernel module in a chip as defined in any one of claims 1-5, wherein the method for verifying a kernel module in a chip further comprises:
acquiring updated module verification environment information when the module verification environment changes, and executing the method according to any one of claims 1-5 based on the updated module verification environment information;
when the chip verification environment changes, after obtaining the module verification environment information, newly creating a verification case in the updated chip verification environment, and executing the method according to any one of claims 1-5.
8. A verification system for a kernel module in a chip, comprising:
the file acquisition module is used for acquiring module verification environment information of the kernel module to be tested, and acquiring a verification intermediate file of the kernel module to be tested according to the verification environment information;
the use case module is used for creating a verification use case in a chip verification environment of the SOC chip integrated with the core module to be tested, and carrying out configuration operation, starting operation and verification operation on the core module to be tested according to the verification intermediate file in the verification use case to obtain a verification result of the core module to be tested;
and the judging module is used for judging whether the kernel module to be tested passes the verification or not based on the verification result.
9. A chip comprising at least one core module to be tested for implementing the steps of the method according to any one of claims 1 to 7.
10. A chip authentication device comprising at least one chip as claimed in claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310677765.8A CN116701208A (en) | 2023-06-08 | 2023-06-08 | Verification method, system, chip and device for kernel module in chip |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310677765.8A CN116701208A (en) | 2023-06-08 | 2023-06-08 | Verification method, system, chip and device for kernel module in chip |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116701208A true CN116701208A (en) | 2023-09-05 |
Family
ID=87823343
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310677765.8A Pending CN116701208A (en) | 2023-06-08 | 2023-06-08 | Verification method, system, chip and device for kernel module in chip |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116701208A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117829043A (en) * | 2023-12-29 | 2024-04-05 | 上海先楫半导体科技有限公司 | Chip design verification platform, method, terminal, medium and system |
-
2023
- 2023-06-08 CN CN202310677765.8A patent/CN116701208A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117829043A (en) * | 2023-12-29 | 2024-04-05 | 上海先楫半导体科技有限公司 | Chip design verification platform, method, terminal, medium and system |
| CN117829043B (en) * | 2023-12-29 | 2024-07-23 | 上海先楫半导体科技有限公司 | Chip design verification platform, method, terminal, medium and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106940428B (en) | Chip verification method, device and system | |
| US9465718B2 (en) | Filter generation for load testing managed environments | |
| CN115841089A (en) | System-on-chip verification platform and verification method based on UVM | |
| CN111428431B (en) | Automatic test and recording method and system supporting EDA software | |
| CN113835945A (en) | Chip testing method, device, equipment and system | |
| CN116701208A (en) | Verification method, system, chip and device for kernel module in chip | |
| CN107480056B (en) | Software testing method and device | |
| CN114117977B (en) | Method suitable for automatically verifying processor system scene | |
| CN110750434A (en) | Interface testing method and device, electronic equipment and computer readable storage medium | |
| CN114218882A (en) | SoC chip inspection method, device and related equipment | |
| CN113704126A (en) | Verification method and device, computer storage medium and processor | |
| CN113032202A (en) | Chip verification method, system, device, computer equipment and storage medium | |
| CN110990207B (en) | BPS memory test method, system, terminal and storage medium based on Whitley platform | |
| CN117194230A (en) | FCT matching test method, device, equipment and medium for different versions of board cards | |
| CN112561690A (en) | Method, system, equipment and storage medium for testing credit card staging service interface | |
| CN114912397A (en) | Programmable logic device, prototype verification system, method, apparatus, and storage medium | |
| CN114168399A (en) | Signal processing unit testing method and system | |
| CN111258838B (en) | Verification component generation method, device, storage medium and verification platform | |
| CN109446091B (en) | Business entity object testing method and device | |
| CN106778301A (en) | Reliable cross-platform data storage method and system based on cocos2d x | |
| CN114443375A (en) | Test method and device, electronic device and computer readable storage medium | |
| CN106815136B (en) | Unit testing method and device | |
| CN117724989B (en) | Regression testing method and device for interface, terminal and storage medium | |
| CN112685317B (en) | Custom test method and device based on test pile | |
| CN115495388B (en) | Chip verification method, device, equipment and medium for AI reasoning chip |
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 |