Refinement File Reuse via Path Translation in Coverage Grading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the verification of electronic designs, the process of incorporating a verified design into a larger design requires a new refinement file, which is typically manually edited from the previous design's refinement file, leading to inefficiencies and time consumption due to changes in design hierarchies that invalidate the original refinement file's pathnames.
Innovation Solution
A method and system for reusing a refinement file in coverage grading by obtaining mapping information to translate source paths of coverage entities from a first coverage model to a target path in a second or third coverage model, excluding specific entities from the calculation, and generating a new refinement file that automatically adjusts pathnames, thereby facilitating the reuse of the original refinement file.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a new refinement file is manually edited for each design incorporation, then coverage grading accuracy is maintained, but time consumption and manual effort increase significantly
Solution Approach 1:
The system performs preliminary actions by automatically generating refinement files through path translation before coverage grading is needed. The mapping information is prepared in advance, allowing the refinement file to be automatically created when a design is incorporated into a larger design, eliminating the need for manual editing while maintaining accuracy.
Solution Approach 2:
The system enables self-service by automatically translating paths and generating refinement files without human intervention. The translation process uses mapping information to automatically update pathnames, allowing the refinement file generation to serve itself rather than requiring manual editing, thus reducing time consumption while maintaining grading accuracy.
2Manufacturing precision
If manual editing of refinement files is performed, then path accuracy is ensured, but productivity decreases due to repetitive tasks
Solution Approach 1:
The system replaces the mechanical process of manual path editing with an automated translation mechanism. The translation process uses mapping information to automatically update paths in the refinement file, substituting manual mechanical editing with an automated system that maintains path accuracy while significantly improving verification productivity.
Solution Approach 2:
The system changes parameters by automatically translating pathnames from source to target paths using mapping information. This parameter transformation maintains the accuracy of path references while eliminating repetitive manual editing tasks, thereby improving productivity without sacrificing path accuracy.
3Adaptability or versatility
If refinement files are not reused, then design hierarchy changes are accommodated, but work efficiency decreases due to redundant file generation
Solution Approach 1:
The system enables universality by making refinement files reusable across different design hierarchies. The translation process allows a single refinement file to be adapted to multiple design contexts through automatic path translation, eliminating the need to generate separate refinement files for each design incorporation, thus improving work efficiency while maintaining adaptability.
Solution Approach 2:
The system uses mapping information as an intermediary to enable refinement file reuse. The mapping information acts as a mediator that translates paths between different design hierarchies, allowing the original refinement file to be reused while accommodating design hierarchy changes, thereby improving work efficiency without sacrificing adaptability.
Data Source
AI summary
A method for reuse of a refinement file in coverage grading, may include obtaining a refinement file that includes a listing of coverage entities of a first coverage model, for exclusion from a calculation of coverage grading of the first coverage model; obtaining mapping information to map a source path of each of the modules or instances of a module, that include one or more of said coverage entities in the first coverage model to a target path of each of said modules or instances of a module in a second coverage model; and using a processor, based on the refinement file and the mapping information, translating a source path of each of said coverage entities listed in the refinement file to a target path of a coverage entity of the coverage entities in the second coverage model.