A Comprehensive Evaluation Method and System for Chip Design Logic Based on Checklist Items
By using a chip design logic synthesis and evaluation system based on checklist items, a fully automated chip design process and quality assessment were achieved, solving the problems of insufficient automation and inconsistent environment configuration, and improving the quality and efficiency of logic synthesis.
Patent Information
- Application Number
- CN202611154111.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-31
- Publication Date
- 2026-11-10
AI Technical Summary
Existing technologies lack sufficient automation in chip design logic synthesis quality checks, have high costs for expanding check items, inconsistent environment configurations, and make it difficult to form a chip-level quality overview from module-level results.
A chip design logic comprehensive evaluation system based on checklist is adopted. Through code library management module, build control module, comprehensive execution module and evaluation report module, it realizes fully automated process and quality evaluation, registers check items and executes them in a unified environment, and generates chip-level quality overview.
It improves the efficiency of automated chip design processes, assists in the quality assessment of logic synthesis in the chip design field, and in turn improves the quality of source files and design constraint files.
Smart Images

Figure CN123070001A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of chip design technology, and in particular relates to a chip design logic synthesis and evaluation method and system based on checklist check items. Background Technology
[0002] As the scale and complexity of system-on-a-chip (SoC) integration increase, chip designs typically consist of multiple intellectual property cores and functional modules, and logic synthesis is completed through register-transfer level design files, design constraint files, and chip design software. Large-scale SoC projects often employ multiple code repositories to manage the top-level integration code, the code for each functional module, common dependency files, and the execution environment, respectively, to support parallel development and version control of different modules.
[0003] Existing technologies can already trigger continuous integration tasks using code repository events. For example, Chinese patent CN114880227A discloses a method in the chip industry that combines Git code repository hooks with Jenkins continuous integration to perform builds and checks in response to code changes; Chinese patent CN113255258B discloses a technical solution for logic synthesis of chip design documents and generation of netlists. However, in the logic synthesis quality assessment stage, existing solutions typically use a small number of pre-fixed parameters or independent check scripts. Adding new check dimensions requires modification of the main process or manual configuration, and it is difficult to unify the environmental parameters, output formats, and scoring criteria required by the check scripts, resulting in high costs for expanding check items and inconvenience in summarizing the check results of different functional modules.
[0004] Furthermore, when changes occur in the chip's top-level code and the code of individual functional modules, performing the same scope of logic synthesis and quality checks on both will increase unnecessary build overhead; if only local builds are performed but automatic evaluation and chip-level summarization corresponding to the modules are lacking, it will be difficult to reflect the impact of this change on the logic synthesis quality in a timely manner. Summary of the Invention
[0005] In view of this, this application aims to propose a chip design logic synthesis evaluation method and system based on checklist check items, in order to solve the problems of insufficient automation of existing logic synthesis quality checks, inconsistent check item expansion and environment configuration, and difficulty in forming a chip-level quality overview from module-level results.
[0006] To achieve the above objectives, the technical solution of this application is implemented as follows: Firstly, this application provides a chip design logic synthesis and evaluation system based on checklist items, including: The code repository management module is used to manage the chip's top-level integrated code, the code of each functional module, common dependency files and automated execution environment respectively using a multi-code repository structure, and to save register transfer level design files, design constraint files and checklist files in the corresponding code repositories; A control module is built to respond to codebase change callbacks, extract the changed codebase and branch information, determine whether to perform a chip-level full build or a functional module-level partial build, parse the manifest file in the top-level integrated codebase and pull the code of each functional module when performing the full build, and pull the changed functional module code when performing the partial build. The synthesis and execution module is used to schedule the chip design software to perform logic synthesis on the pulled code and generate a synthesis deliverable in a unified execution environment; The inspection item registration module is used to register inspection items according to a preset registration protocol, which at least defines the inspection item description, executable script, environment variable declaration, output format and scoring criteria. The evaluation report module is used to traverse the registered check items after logic synthesis, inject unified execution environment parameters and the current task running position into the corresponding executable script according to the environment variable declaration, independently execute each check item based on the synthesis deliverable, obtain the comprehensive score of the corresponding functional module according to the score and weight of each check item, and output an evaluation report containing the comprehensive score, deduction items, scores of each check item and the inspection process, as well as form a chip-level quality overview based on the comprehensive scores of each functional module.
[0007] Secondly, based on the same inventive concept, this application also provides a chip design logic synthesis and evaluation method based on checklist items, including: Register multiple checks used to evaluate the quality of chip logic synthesis; In response to code changes or proactively triggered operations, determine system-level or chip module-level build based on the changed codebase, and obtain the corresponding chip design files; The scheduling chip design software performs logic synthesis, generates logic synthesis deliverables, and after logic synthesis is completed, it iterates through the checklist and injects the runtime environment into the corresponding execution script based on the environment variables declared for each check item and the current task execution location. The execution scripts for each inspection item are executed separately to perform quality checks on the logic synthesis deliverables, obtain the scores and inspection details for each inspection item, calculate the total quality score of the chip module based on the scores and weights of each inspection item, and generate a chip module-level synthesis report and a chip-level quality overview.
[0008] Thirdly, based on the same inventive concept, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in the first aspect.
[0009] Fourthly, based on the same inventive concept, this application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions for causing the computer to perform the method as described in the first aspect.
[0010] Compared with existing technologies, the chip design logic synthesis and evaluation method and system based on checklist items described in this application have the following advantages: (1) This application manages chip-related files at each level based on the PolyRepo code structure and saves the checklis automated quality files to the code repository to achieve better version control. At the same time, it triggers the execution of the Jenkins pipeline based on GitLab and the execution of chip design tasks by triggering the LSF cluster to schedule the execution of the Jenkins pipeline. This can realize a complete fully automated logic synthesis process and quality assessment, improve the automation process of chip design, and improve efficiency.
[0011] (2) This application provides a registration agreement for check files. Checks that meet the agreement can be automatically registered in the system. Automatic checks can be performed after the logic synthesis task is completed, which helps to evaluate the quality of logic synthesis in the field of chip design, improve the quality of logic synthesis, and help to improve the quality of source files RTL and SDC. Attached Figure Description
[0012] The accompanying drawings, which form part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a schematic diagram of the check protocol registration process described in an embodiment of this application; Figure 2 This is a flowchart illustrating the automated quality assessment process described in the embodiments of this application; Figure 3 This is a schematic diagram of the hardware structure of the electronic device described in an embodiment of this application. Detailed Implementation
[0013] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.
[0014] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0015] The embodiments of this application are described in detail below with reference to the accompanying drawings.
[0016] In the following examples, "checklist" corresponds to "check item", "functional module" corresponds to "block", "register transfer level design file" corresponds to "RTL file", and "design constraint file" corresponds to "SDC file".
[0017] The system in this embodiment consists of several stages: code repository management, build triggering, logic synthesis, check item execution, and evaluation result output. The code repository uses Git for version control and employs a multi-repository structure to organize chip design files.
[0018] The multi-codebase structure includes a top-level integration codebase, multiple functional module sub-codebases, a common dependency codebase, and an execution environment codebase. The top-level integration codebase, which can be named Soc_top, stores the basic information of the intellectual property cores required for chip integration, global clock, cross-clock constraints, top-level register-transfer level design files, and manifest files. The functional module sub-codebases can correspond to processor modules, sensor hub modules, or other chip functional modules, and are used to store their respective register-transfer level design files, verification files, synthesis files, documentation, and checklist files. The common dependency codebase stores standard cells, process documents, design constraint templates, and general TCL or Python scripts. The execution environment codebase stores the unified environment information required for automated execution.
[0019] The manifest file in the top-level integrated codebase records the address, branch, or version information of each functional module's sub-codebase. During a full chip-level build, the build control module reads this manifest file to determine the functional module code that needs to be pulled.
[0020] Each code repository sets up a code change callback interface. When a code commit, merge, or other pre-defined change event occurs, the code repository triggers the continuous integration scheduler through the callback interface. The continuous integration scheduler can be implemented using Jenkins. The key parameters passed to the callback interface include the code repository address, code repository branch, committer, and commit information.
[0021] The build control module determines the build type corresponding to this change based on the code repository address and branch. When the change comes from the top-level integration code repository, it determines to perform a full chip-level build, pulls the top-level integration code and parses the manifest file, and then pulls all relevant functional module code based on the manifest file; when the change only comes from a functional module sub-code repository, it determines to perform a partial build of that functional module, and only pulls that functional module and its common dependency files required for the build.
[0022] After code retrieval is complete, the synthesis execution module loads the unified environment information from the execution environment code library and distributes the logic synthesis task to the chip design software via a cluster scheduling system. The cluster scheduling system can employ LSF cluster scheduling. The chip design software performs logic synthesis based on the register-transfer level design file, design constraint file, and synthesis script. Upon completion of the task, a synthesis deliverable is generated, including logs, reports, and a gate-level netlist.
[0023] After the logic synthesis task is completed, the evaluation report module reads the checklist file corresponding to the currently built object. The checklist directory contains multiple subdirectories for check items, each subdirectory corresponding to an independent quality inspection dimension, such as error log check items, power consumption check items, or external test feedback check items.
[0024] like Figure 1 As shown, the system maintains a unified checklist registration protocol. Checklist developers create checklist directories and scripts according to this protocol and place the checklists into the checklist directory of the corresponding code repository. The system traverses the checklist directory and registers checklists that meet the registration protocol.
[0025] The registration agreement includes inspection item descriptions, executable scripts, environment variable declarations, weights, output report locations, structured output formats, and scoring criteria. Inspection item descriptions explain the purpose of the inspection; executable scripts read the integrated deliverables and perform specific inspections; environment variable declarations list the environmental parameters the script depends on; weights are used in calculating the overall score of the functional modules; output report locations are used to locate detailed reports; and scoring criteria determine the scores for inspection items and the reasons for deductions.
[0026] In a structured output format, the inspection item script outputs a JSON structure. This JSON structure includes the relative path to the output report, a score field, a detail field, a positive scoring criteria field, and an attention items field. The score field represents the inspection item score within the range of 0 to 100; the detail field represents the inspection details; the positive scoring criteria field records the base score, current score, and description of the scoring item; and the attention items field records the category and severity of the deducted items.
[0027] Before executing each check item, the evaluation report module reads the environment variable declaration for that check item and generates a list of environment variables based on the environment parameters in the unified execution environment and the current task execution location, automatically injecting the required parameters into the check item script. Thus, the same check item can obtain the corresponding execution directory and environment parameters for the current task in both chip-level full builds and functional module-level partial builds.
[0028] The evaluation report module calls the executable scripts for each registered inspection item. Each inspection item independently scans logs, reports, gate-level netlists, or external test feedback, and returns inspection results according to the structured output format defined in the registration agreement. The evaluation report module parses the inspection results and saves the score, inspection process, detailed report location, and deductions for each inspection item.
[0029] After completing all the checks for a functional module, the system calculates the overall score for that functional module. Let there be a total of... The first inspection item, the... The original scores for each inspection item are The weight is The overall score is ,in, From 1 to The weight of each inspection item can be configured in the registration agreement, and the score for each item ranges from 0 to 100 points.
[0030] The system generates a comprehensive report for each functional module based on the results of each inspection item. The comprehensive report includes the overall score for the functional module, all deductions, the score for each inspection item, and the inspection process. It also provides drill-down information for querying detailed reports. For partial builds, the system updates the overall score and report for the functional modules that have undergone changes; for full chip-level builds, the system generates a comprehensive report for all functional modules.
[0031] After completing the functional module-level evaluation, the system summarizes the comprehensive scores of each functional module in the chip to form a chip-level quality overview. The chip-level quality overview is used to display the logic synthesis quality of different functional modules and to locate functional modules with low scores or serious deductions.
[0032] Example 1: A Logical Synthesis Quality Assessment System Based on Multiple Checklists Git is used to store RTL and SDC files, while the PolyRepo code structure is used to manage chip-related files at each level. Soc_top is the SOC integrated code repository, storing all global IP basic information, global clock, cross-clock constraints, etc. ip-cpu and ip-sensor-hub are the basic files for different blocks within the chip (blocks belong to different modules of the chip). Common-libs contains general files, including the infrastructure that each block must depend on. Verification-env stores environment information, including the environment information for automated execution.
[0033] According to the checklist protocol, register multiple checklist files, including external test system feedback check items (weights). ), and judge the current logical overall task quality item (weight) based on the Qor metric. )wait.
[0034] If the code changes, the GitLab callback interface triggers Jenkins to execute. Jenkins first parses the manifest file, pulls down the different block code, and performs logic synthesis tasks according to a unified environment. Specifically, this involves scheduling the LSF cluster, distributing the logic synthesis tasks to the specific chip design software, and outputting deliverables upon completion. Deliverables mainly include logs, reports, and gate-level netlists.
[0035] The automated execution script iterates through the check files under the check list, performs independent scans, and outputs the quality assessment of each check item. Basic information for each check item describes its function. The execution script stores the executable script code for each check item, and the environment information includes the environment variables that this execution script code depends on. Each time the script is executed, the environment variables are automatically injected based on the environment parameters in the unified verification environment and the current task execution location.
[0036] After scanning all check items, calculate the total score of the current CheckList. The calculation formula is: Let there be a total of The first rating item: The original score for the item is , No. The weight of the item is Output the current summation. , ( ).
[0037] After scanning the complete CheckList for a certain block, a comprehensive report for the current block is output, including the total score of the block, each attention item (deduction item), the score and process of each check, and detailed reports that can be queried by drilling down.
[0038] Example 2: Automated Quality Assessment System Based on Multiple Checklists and Logical Synthesis Git is used to store RTL and SDC files, while PolyRepo code structure is used to manage chip-related files at each level. A system callback interface is added to each code repository, and the system implements this callback interface to trigger Jenkins execution. The system needs to implement a callback function for each integrated code repository. This callback function includes determining the repository address and extracting key parameters for the current trigger based on information such as the repository address, repository branch, committer, and commit information. Based on this key information, the system determines the type of build to trigger. If the trigger is for the Soc_top (SOC integration code repository), the system parses the manifest file, pulls the full logic synthesis RTL code for quality assessment, and if only a single code repository is involved, the system pulls the corresponding code repository for quality assessment and updates the logic synthesis quality data and report for the corresponding block.
[0039] According to the checklist protocol, register multiple checklist files, including external test system feedback check items (weights). ), and judge the current logical overall task quality item (weight) based on the Qor metric. )wait.
[0040] The automated execution script schedules the LSF cluster to perform logical synthesis tasks. After execution, it iterates through the check files under the check list, performs independent scans, and outputs the quality assessment of each check item. The basic information of each check item describes its function. The execution script stores the executable script code for the check item, and the environment information includes the environment variables that the execution script code depends on. Each time the script is executed, the environment variables are automatically injected based on the environment parameters in the unified verification environment and the current task execution location.
[0041] After scanning all check items, calculate the total score for the current check list using the following formula: Assume there is a total The first rating item: The original score for the item is , No. The weight of the item is Output the current summation. , ( ).
[0042] After scanning the complete check list for a certain block, a comprehensive report for the current block is output, including the total score of the block, each attention item (deduction item), the score and process of each check, and detailed reports that can be queried by drilling down.
[0043] like Figure 2 As shown, based on the same inventive concept, this embodiment also provides a chip design logic comprehensive evaluation method based on checklist items, specifically including the following steps: Step S10: Register multiple check items used to evaluate the chip logic synthesis quality; Specifically, in this embodiment, multiple check items used to evaluate the chip logic synthesis quality are registered to the check list according to a preset check item registration protocol; in response to code submission operation or active triggering operation, a logic synthesis quality assessment task is generated, wherein each check item is configured with check item description information, execution script, environment variable declaration, output report location and scoring criteria.
[0044] Step S20: In response to code changes or proactively triggered operations, determine system-level build or chip module-level build based on the changed codebase, and obtain the corresponding chip design files; Specifically, in this embodiment, the code library that has been changed and the corresponding build type are determined based on the trigger information; when the system-level integration code library is changed, the system-level integration code library is obtained and the manifest file in it is parsed to obtain the RTL file, SDC file and dependency file corresponding to each chip module; when the chip module code library is changed, the RTL file, SDC file and dependency file corresponding to the changed chip module are obtained.
[0045] Step S30: Schedule the chip design software to perform logic synthesis, generate logic synthesis deliverables, and after logic synthesis is completed, iterate through the checklist and inject the runtime environment into the corresponding execution script according to the environment variables declared for each check item and the current task execution position. Specifically, in this embodiment, an automated execution engine creates a logic synthesis task corresponding to the build type and schedules the logic synthesis task to the cluster computing environment. The chip design software performs logic synthesis based on the acquired RTL file, SDC file, dependency file and unified verification environment, generating logic synthesis deliverables including logs, logic synthesis reports and gate-level netlists.
[0046] After the logic synthesis task is completed, the automated execution engine reads the checklist corresponding to the current object to be evaluated, traverses each check item under the checklist, and parses the execution script, environment variable declaration, scoring criteria and output format of each check item according to the check item registration protocol.
[0047] Step S40: Execute the execution script for each inspection item to perform quality checks on the logic synthesis deliverables, obtain the score and inspection details for each inspection item, calculate the total quality score of the chip module based on the score and weight of each inspection item, and generate a chip module-level synthesis report and a chip-level quality overview.
[0048] Specifically, in this embodiment, for each check item, a corresponding environment variable is generated based on the environment parameters in the unified verification environment and the current running position of the logic synthesis task, and the environment variable is injected into the execution environment of the check item; after the environment variable injection is completed, the execution script corresponding to each check item is executed independently to scan and perform quality checks on the logic synthesis deliverables.
[0049] Obtain the structured evaluation data output by the execution script for each inspection item. The structured evaluation data should include at least the inspection item score, inspection details, scoring basis, and deduction items. Determine the original score for each inspection item according to the scoring criteria corresponding to each inspection item.
[0050] Based on the original scores and corresponding weights of each inspection item, a weighted calculation is performed on all inspection items of the current chip module to obtain the total quality score of the current chip module. The scores, inspection process, deductions, and detailed report locations of each inspection item are then summarized.
[0051] Generate a comprehensive quality assessment report for the current chip module; when the assessment task involves multiple chip modules, further summarize the quality scores and inspection results of each chip module to form a chip-level quality overview and output automated quality assessment results.
[0052] It should be noted that the above description describes some embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0053] The methods described above are used to implement the corresponding methods in any of the foregoing embodiments and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0054] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, embodiments of this application also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the methods described in any of the above embodiments.
[0055] Figure 3 This embodiment illustrates a more specific hardware structure of an electronic device, which may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.
[0056] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.
[0057] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.
[0058] The input / output interface 1030 is used to connect input / output modules to realize information input and output. The input / output modules can be configured as components in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touch screens, microphones, various sensors, etc., and output devices may include displays, speakers, vibrators, indicator lights, etc.
[0059] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).
[0060] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.
[0061] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.
[0062] The electronic devices described above are used to implement the corresponding methods in any of the foregoing embodiments and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0063] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a non-transitory computer-readable storage medium that stores computer instructions for causing the computer to perform the methods described in any of the above embodiments.
[0064] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.
[0065] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to perform the methods described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0066] Although this application has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.
[0067] The embodiments of this application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the claims of this application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application should be included within the protection scope of this application.
Claims
1. A chip design logic synthesis and evaluation system based on checklist items, characterized in that, include: The code repository management module is used to manage the chip's top-level integrated code, the code of each functional module, common dependency files and automated execution environment respectively using a multi-code repository structure, and to save register transfer level design files, design constraint files and checklist files in the corresponding code repositories; A control module is built to respond to codebase change callbacks, extract the changed codebase and branch information, determine whether to perform a chip-level full build or a functional module-level partial build, parse the manifest file in the top-level integrated codebase and pull the code of each functional module when performing the full build, and pull the changed functional module code when performing the partial build. The synthesis and execution module is used to schedule the chip design software to perform logic synthesis on the pulled code and generate a synthesis deliverable in a unified execution environment; The inspection item registration module is used to register inspection items according to a preset registration protocol, which at least defines the inspection item description, executable script, environment variable declaration, output format and scoring criteria. The evaluation report module is used to traverse the registered check items after logic synthesis, inject unified execution environment parameters and the current task running position into the corresponding executable script according to the environment variable declaration, independently execute each check item based on the synthesis deliverable, obtain the comprehensive score of the corresponding functional module according to the score and weight of each check item, and output an evaluation report containing the comprehensive score, deduction items, scores of each check item and the inspection process, as well as form a chip-level quality overview based on the comprehensive scores of each functional module.
2. The system according to claim 1, characterized in that: The multi-codebase structure includes a top-level integrated codebase, sub-codebases corresponding to each functional module, a common dependency codebase, and an execution environment codebase. The top-level integrated codebase stores the chip's intellectual property core basic information, global clock information, cross-clock constraint information, and manifest files indicating the versions and locations of each sub-codebase. The sub-codebases store register transfer level design files, verification files, synthesis files, and checklist files for the corresponding functional modules. The common dependency codebase stores standard cells, process files, and general scripts. The execution environment codebase stores environment information for a unified execution environment.
3. The system according to claim 1, characterized in that: The build control module includes a continuous integration scheduler. The code repository change callback transmits at least one of the following to the continuous integration scheduler: code repository address, code repository branch, code committer and code commit information. The build control module identifies the code repository that has been changed and its level based on the code repository address and code repository branch.
4. The system according to claim 1, characterized in that: When the build control module detects a change in the top-level integrated code library, it determines to execute the chip-level full build. When it detects a change in the sub-code library of any functional module, it determines to execute the functional module-level partial build. After the partial build is completed, it updates the logic synthesis quality data and evaluation report of the corresponding functional module.
5. The system according to claim 1, characterized in that: The synthesis execution module distributes logic synthesis tasks to the chip design software through a cluster scheduling system. The synthesis deliverables include at least one of logic synthesis log, logic synthesis report, and gate-level netlist.
6. The system according to claim 1, characterized in that: Each inspection item corresponds to an inspection item list in the inspection checklist file. The inspection item list stores the inspection item description, executable script, environment variable declaration, output report location, and scoring criteria. The output format adopts a structured data format and includes at least the inspection item score, inspection details, positive scoring criteria, and deduction items.
7. The system according to claim 1, characterized in that: Before executing the check items, the evaluation report module generates an environment variable list based on the environment variable declaration, and injects the environment parameters of the unified execution environment and the current task's running directory into the environment variable list; after executing the check items, it parses the structured data output by the executable script according to the output format.
8. A chip design logic synthesis and evaluation method based on checklist items, characterized in that, include: Register multiple checks used to evaluate the quality of chip logic synthesis; In response to code changes or proactively triggered operations, determine system-level or chip module-level build based on the changed codebase, and obtain the corresponding chip design files; The scheduling chip design software performs logic synthesis, generates logic synthesis deliverables, and after logic synthesis is completed, it iterates through the checklist and injects the runtime environment into the corresponding execution script based on the environment variables declared for each check item and the current task execution location. The execution scripts for each inspection item are executed separately to perform quality checks on the logic synthesis deliverables, obtain the scores and inspection details for each inspection item, calculate the total quality score of the chip module based on the scores and weights of each inspection item, and generate a chip module-level synthesis report and a chip-level quality overview.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method as claimed in any one of claims 8.
10. A non-transitory computer-readable storage medium, characterized in that, in, The non-transitory computer-readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 8.
Citation Information
Patent Citations
Logic synthesis methods, apparatus, electronic devices and storage media
CN113255258B
Code warehouse management method and system applied to chip field
CN114880227A
