Electronic design automation data inspection method and electronic equipment

Abstract

The embodiment of the invention relates to an electronic design automation data checking method and electronic equipment. The method comprises the steps that to-be-checked electronic design automation data and a checking configuration file are obtained respectively; the checking configuration file comprises checking rules for checking the electronic design automation data, and the checking rules are editable rules; the check rule is structured data, and the structured data comprises a rule check function; and checking the to-be-checked electronic design automation data based on the rule checking function to generate a checking result. The checking configuration file is an editable rule, so that the checking rule for checking the electronic design automation data to be checked can be determined based on the editing operation of the user, and the checking rule in the configuration file can be flexibly adjusted according to the requirement of the user; according to the embodiment of the invention, the situation that the inspection content is relatively single and does not have expansibility in related technologies can be avoided, so that the inspection efficiency of the electronic design automation data can be improved.

Description

Technical Field

[0001] This application relates to the field of automated testing technologies, and particularly to an electronic design automation data checking method and an electronic device. Background Art

[0002] Electronic design automation (EDA), which is short for electronic design automation, refers to a design method that uses computer-aided design (CAD) software to complete the functional design, synthesis, verification, and physical design (including layout, wiring, layout, and design rule checking, etc.) of very large scale integration (VLSI) chips. By using EDA tools, the entire process of electronic products from circuit design, performance analysis to designing the printed circuit board (PCB) layout can be processed on a computer.

[0003] During the circuit design or the design process of the printed circuit board layout, in order to avoid quality problems or even accidents caused by design problems flowing into the production trial stage, it is necessary to conduct sufficient rule checking in the design stage. With the increase in the complexity of circuit design, the content to be checked gradually expands from design rules to process requirements and manufacturing requirements, etc. However, related technologies generally only check for a certain or certain types of specific rules, making the content of the related technologies relatively single for checking and not scalable, resulting in a low checking efficiency of the related technologies. Summary of the Invention

[0004] Embodiments of this application provide an electronic design automation data checking method and an electronic device.

[0005] According to the first aspect of the embodiments of this application, an electronic design automation data checking method is provided. The method includes:

[0006] Obtain the electronic design automation data to be checked and a check configuration file respectively;

[0007] Wherein, the check configuration file includes check rules for checking the electronic design automation data, and the check rules are editable rules; the check rules are structured data, and the structured data includes rule check functions;

[0008] Check the electronic design automation data to be checked based on the rule check function, and generate a check result.

[0009] The inspection configuration file in the embodiments of the present application includes inspection rules for inspecting electronic design automation data. Since the inspection rules are editable rules, users can edit the inspection rules as needed, which can improve the flexibility of adjusting the inspection rules in the inspection configuration file. For example, adding, deleting, or modifying the inspection rules can avoid the situation in related technologies where the inspection content is relatively single and not extensible, and thus can improve the inspection efficiency of the electronic design automation data to be inspected.

[0010] In another embodiment provided by the present application, the obtaining of the inspection configuration file includes:

[0011] Receiving an inspection task for instructing to perform an inspection on the electronic design automation data to be inspected; the inspection task includes a plurality of task inspection items;

[0012] Respectively obtaining target inspection rules matching the plurality of task inspection items;

[0013] Performing an inspection based on the task inspection items, the target inspection rules, and the inspection configuration file.

[0014] The embodiments of the present application can receive a create task operation initiated by a user and obtain the task inspection items that the user needs to inspect. Since each task inspection item can correspond to one or more inspection rules, by obtaining the inspection rules corresponding to the task inspection items, a configuration file can be generated based on the task inspection items and the inspection rules, so that the inspection configuration file can be flexibly configured according to the user's task inspection needs.

[0015] In another embodiment provided by the present application, the respectively obtaining inspection rules matching the plurality of task inspection items includes:

[0016] Obtaining the data type of the electronic design automation data to be inspected;

[0017] Based on the data type, obtaining a corresponding inspection rule set, and respectively obtaining target inspection rules matching the plurality of task inspection items from the inspection rule set.

[0018] The embodiments of the present application can support electronic design automation data of different data types, and different data types can correspond to different inspection rule sets. For example, a circuit schematic diagram corresponds to an inspection rule set for circuit schematic diagrams, and a PCB layout corresponds to an inspection rule set for PCB layouts. This facilitates calling corresponding inspection rules from the corresponding inspection rule sets based on the data type to improve the inspection efficiency.

[0019] In another embodiment provided by the present application, the method further includes:

[0020] Obtain the target operation of the user on the inspection profile; the target operation includes: rule modification, rule addition, or rule deletion;

[0021] When the target operation is rule modification, modify the corresponding inspection rule and re - establish the correspondence between the modified inspection rule and the rule inspection function in the inspection rule set;

[0022] Or, when the target operation is rule addition, add the corresponding inspection rule and establish an association relationship between the added inspection rule and the rule inspection function in the inspection rule set;

[0023] Or, when the target operation is rule deletion, delete the corresponding inspection rule.

[0024] In the embodiment of the present application, when it is necessary to modify the inspection rule, the corresponding inspection content in the inspection rule may be modified. Since different inspection contents need to call different rule inspection functions for inspection. Therefore, when modifying the inspection rule, it is necessary to re - establish the correspondence between the inspection functions in the inspection rule set. Similarly, when adding an inspection rule, it is necessary to establish an association relationship between the added inspection rule and the rule inspection function in the inspection rule set, so that when the data is inspected through the newly added inspection rule, the corresponding inspection function can be called. When the embodiment performs a deletion operation on the inspection rule, only the corresponding inspection rule needs to be deleted.

[0025] In another embodiment provided by the present application, the inspection result includes inspection non - compliant items;

[0026] The inspection of the to - be - inspected electronic design automation data to generate an inspection result includes:

[0027] Generate a detection result table based on the non - compliant items; wherein, the detection result table includes the content of the non - compliant items, and the content includes: one or several of the position information of components, non - compliant area information, connection relationship information, and error type information.

[0028] In the embodiment of the present application, when inspecting data, general users are more concerned about the inspection non - compliant items. Therefore, the embodiment can generate a detection result table for the inspection result of the non - compliant items and mark and display the specific content of the non - compliant items in the detection result table, so that users can quickly and specifically adjust according to the specific content of the non - compliant items, and thus can greatly improve the adjustment efficiency of users for the content of the non - compliant items.

[0029] In another embodiment provided by the present application, the method further includes:

[0030] Output the detection result table.

[0031] The embodiments of the present application can also output a detection result table to directly mark and display non - compliant items at corresponding positions on the interface diagram, enabling users to more intuitively see the problem areas, facilitating users to modify the EDA file in a timely manner, and thus improving the processing efficiency.

[0032] In another embodiment provided by the present application, the detection result table further includes a jump link;

[0033] The jump link is used to jump to the display interface diagram corresponding to the electronic design automation data to be inspected, and display the target non - compliant item at the target position in the display interface diagram.

[0034] Based on the above - mentioned detection result table containing non - compliant items, the embodiments of the present application can also add corresponding jump links to the non - compliant items. When a user performs a selection operation such as clicking on a target non - compliant item in the detection result table, by obtaining the target position of the target non - compliant item on the display interface diagram and displaying the target non - compliant item at the target position on the display interface diagram, users can more intuitively understand the problem situation in the EDA file.

[0035] In another embodiment provided by the present application, the electronic design automation data to be inspected includes a printed circuit board;

[0036] Based on the rule checking function, inspecting the electronic design automation data to be inspected to generate an inspection result includes:

[0037] Parsing the printed circuit board to obtain structured parsing data; wherein, the structured data includes one or more of component information, connection information between components, package information, via information, silk - screen information, trace information, or pad information in the printed circuit board;

[0038] Based on the rule checking function corresponding to the structured data, performing an inspection to generate an inspection result.

[0039] By parsing the PCB layout, the embodiments of the present application can obtain structured data, which facilitates inspecting the parsed data through various rules. When inspecting the PCB layout through various rules, it is not necessary to traverse all the data in the PCB layout, but only need to traverse the data in the parsed data corresponding to the rules.

[0040] In another embodiment provided by the present application, based on the rule checking function, inspecting the electronic design automation data to be inspected to generate an inspection result includes:

[0041] When inspecting the silk - screen information of the printed circuit board, obtaining the silk - screen information of each silk - screen layer in the printed circuit board from the structured parsing data;

[0042] Check each silk screen layer of the printed circuit board based on the target rule check function corresponding to the silk screen information, and generate a check result.

[0043] When performing basic silk screen inspection in the embodiments of the present application, by obtaining the silk screen data of each silk screen layer in the printed circuit board from the structured analysis data and calling the target rule check function to check each silk screen layer of the printed circuit board, a check result for inspecting the silk screen information of the printed circuit board can be quickly obtained.

[0044] According to a second aspect of the embodiments of the present application, there is provided an electronic design automation data inspection device, the device includes:

[0045] A data acquisition module, configured to respectively acquire the electronic design automation data to be inspected and an inspection configuration file; wherein, the inspection configuration file includes inspection rules for inspecting the electronic design automation data, and the inspection rules are editable rules; the inspection rules are structured data, and the structured data includes rule check functions;

[0046] An inspection module, configured to inspect the electronic design automation data to be inspected based on the rule check function, and generate an inspection result.

[0047] According to a third aspect of the embodiments of the present application, there is provided an electronic device. The electronic device includes:

[0048] A memory and a processor;

[0049] The memory is used to store program instructions for at least one processor;

[0050] A memory for storing instructions executable by the at least one processor;

[0051] Wherein, the at least one processor is configured to execute the program instructions to implement the method described in any one of the above.

[0052] According to a fourth aspect of the embodiments of the present application, there is provided a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the above method of the embodiments of the present application is implemented.

[0053] According to a fifth aspect of the embodiments of the present application, there is provided a computer program product, including a computer program, and when the computer program is executed by a processor, the above method of the embodiments of the present application is implemented. Description of the Drawings

[0054] In the following description of exemplary embodiments in conjunction with the drawings, more details, features and advantages of the present application are disclosed. In the drawings:

[0055] Figure 1 Schematic diagram of the system architecture for electronic design automation data checking provided by an exemplary embodiment of the present application;

[0056] Figure 2 Schematic diagram of the electronic design automation data checking process provided by an exemplary embodiment of the present application;

[0057] Figure 3 Schematic diagram of the PCB layout checking provided by an exemplary embodiment of the present application;

[0058] Figure 4 Schematic diagram of the PCB layout checking provided by another exemplary embodiment of the present application;

[0059] Figure 5 Schematic diagram of the process for structuring the checking rules provided by an exemplary embodiment of the present application;

[0060] Figure 6 Schematic diagram of the PCB layout parsing data provided by an exemplary embodiment of the present application;

[0061] Figure 7A Schematic diagram of the basic silk screen checking process provided by an exemplary embodiment of the present application;

[0062] Figure 7B Schematic diagram of the checking result browsing provided by an exemplary embodiment of the present application;

[0063] Figure 8 Flowchart of the electronic design automation data checking method provided by an exemplary embodiment of the present application;

[0064] Figure 9 Schematic block diagram of the functional modules of the electronic design automation data checking device provided by an exemplary embodiment of the present application;

[0065] Figure 10 Schematic block diagram of the electronic device provided by an exemplary embodiment of the present application;

[0066] Figure 11 Schematic block diagram of the computer system provided by an exemplary embodiment of the present application. Detailed implementation manners

[0067] Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Instead, these embodiments are provided to more thoroughly and completely understand the embodiments of the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not used to limit the protection scope of the present application.

[0068] It should be understood that the various steps described in the method embodiments of this application can be executed in different orders and / or executed in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this regard.

[0069] As used herein, the term "including" and its variations are open-ended, that is, "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts such as "first" and "second" mentioned in the embodiments of this application are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependent relationships.

[0070] It should be noted that the modifications of "one" and "multiple" mentioned in the embodiments of this application are illustrative rather than restrictive. Those skilled in the art should understand that, unless clearly stated otherwise in the context, it should be understood as "one or more".

[0071] The names of the messages or information exchanged between multiple devices in the embodiments of this application are only for illustrative purposes and are not used to limit the scope of these messages or information.

[0072] It can be understood that before using the technical solutions of the embodiments of this application, the types, usage scopes, usage scenarios, etc. of the personal information involved in the embodiments of this application should be informed to users and the authorization of users should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0073] In order to improve the efficiency of rule checking in the process of circuit design or printed circuit board layout design, and to solve the problems of single rule checking, poor scalability, and low efficiency of integrated tools in the field of electronic design automation, the embodiments of this application structure the electronic design automation data, checking rules and checking results, realize the automation of electronic design automation data checking, and at the same time support the custom extension of checking rules and the automatic annotation of checking results, which can cover a more comprehensive rule scope or automatic checking process, etc., and can greatly improve the checking efficiency of electronic design automation data.

[0074] As Figure 1 shown, Figure 1 is a schematic diagram of the system architecture for checking electronic design automation data provided by the embodiments of this application. The system architecture includes: WEB server 101, backend server 102 and execution machine 103. Among them:

[0075] A WEB server 101 is used to provide functions such as visual task submission, management, and status monitoring page viewing. For example, a user can send an inspection task, such as the electronic design automation data to be inspected, to the WEB server 101 through a terminal. The WEB server 101 can send monitoring page data or inspection result data, etc., to the terminal for display.

[0076] A backend server 102 is used to perform structured parsing on the electronic design automation data to be inspected and store the structured parsing data obtained from the structured parsing. It can also provide an interface to implement data interaction with the front end and manage the creation and consumption of tasks with an execution machine through a message queue.

[0077] An execution machine 103 is used to read an inspection configuration file according to an inspection task, obtain the content of an inspection rule according to the specified inspection content, including information such as a rule ID, a rule name, and a rule inspection function, etc., and perform an inspection on the electronic design automation data to be inspected through the corresponding rule inspection function and generate an inspection result.

[0078] In the embodiment, taking the inspection of an EDA file as an example for exemplary illustration, as Figure 1 shown, an inspection task can be received through the WEB server 101. Before the inspection, the EDA file can be first subjected to structured parsing through the backend server 102, and the EDA file can be subjected to rule inspection through the execution machine 103. In this way, file parsing and rule inspection can be separated and executed, avoiding the need to repeatedly perform file parsing when the same file is inspected multiple times, so as to improve the inspection efficiency.

[0079] It should be noted that the execution machine 103 can be an independent server, and the execution machine 103 can also be located in the backend server, which can be set according to needs, and the embodiment is not limited thereto.

[0080] Specifically, as Figure 2 shown, Figure 2 is a schematic diagram of the electronic design automation data inspection process provided by the embodiment of the present application. On a WEB (world wide web) page, a user-initiated create task operation can be received, and the EDA file and inspection rules that the user needs to inspect can be obtained, such as a circuit schematic diagram or a PCB layout, etc. Through file parsing, structured data can be obtained. For example, after parsing the PCB layout, component information and connection relationships between components in the PCB layout, etc., can be obtained.

[0081] Obtain the inspection rules for the EDA file. For example, the user can select from multiple preset inspection rules, and can also add or delete relevant inspection rules, etc. In this way, the inspection function corresponding to the inspection rule can be called to inspect the structured data obtained above through the inspection function to obtain the analysis result. For example, the inspection results corresponding to each inspection item can be obtained, including qualified items and unqualified items. For unqualified items, the results can be marked and located to specific problem elements, such as a problem with a certain pad, etc., which is convenient for the user to directly adjust or modify the EDA file.

[0082] In the embodiment, when inspecting the EDA file, it is necessary to parse the EDA file. For example, by parsing the circuit schematic diagram, the symbols and network information of the components can be obtained; by parsing the PCB layout, the basic information such as the symbols, networks, packages, vias, silkscreen, traces, and pads of the components can be obtained. The basic information includes but is not limited to various position information such as name, ID (identity, identification number), coordinate position, and the distance and angle between elements, etc. By storing the parsed data obtained above in the database, it is convenient for inspection calls during subsequent inspections.

[0083] As Figure 3 shown, Figure 3 is a schematic diagram of PCB layout inspection provided by an embodiment of the present application. Among them, the embodiment can have multiple inspection items and multiple inspection rules, and one inspection item can correspond to one or more inspection rules. For example, there can be N inspection items and M inspection rules, where both N and M are positive integers.

[0084] The embodiment can obtain the inspection items determined by the user, so that the EDA file can be inspected through the inspection rules corresponding to the inspection items. By obtaining the inspection results and marking the unqualified items, a result document is generated.

[0085] In the embodiment, when inspecting the EDA file through the inspection rules, specifically, it can be inspected by calling the corresponding inspection function. As Figure 4 shown, Figure 4 is a schematic diagram of inspecting the PCB layout provided by an embodiment of the present application.

[0086] Figure 4In this case, Inspection Rule 1, Inspection Rule 2, and Inspection Rule 3 are taken as examples for illustration. For example, in the embodiment, when the user inspects the PCB layout through Inspection Rule 1, Inspection Rule 2, and Inspection Rule 3, inspection functions corresponding to Inspection Rule 1, Inspection Rule 2, and Inspection Rule 3 can be obtained from the basic library functions. Exemplarily, for instance, Rule 1 is used to inspect the symbols and networks of components in the PCB. When inspecting the symbols of components, Inspection Function 1 needs to be called; when inspecting the networks in the PCB, Inspection Function 1 and Inspection Function 2 need to be called, so that the inspection results corresponding to Inspection Function 1 and Inspection Function 2 can be obtained respectively. Similarly, based on the inspection functions corresponding to other inspection rules, inspections can be carried out on the packages, vias, silkscreen, traces, or pads, etc. in the PCB layout, and the corresponding inspection results can be obtained.

[0087] In the embodiment, the detection results can adopt a unified structured data format, and this data structure includes inspection rules, problem element positions, inspection results, etc. The inspection rules can be automatically marked through the mapping relationship checklist result file. And the result file can be provided for the design tool to read and reverse-locate to the problem element.

[0088] In the embodiment provided by the present application, the inspection rules can be structured. For example, the execution machine can read the inspection configuration file according to the inspection task, obtain the content of the inspection rules according to the specified inspection content, including information such as rule ID, rule name, and rule inspection main function, and execute the inspection, that is, execute the inspection main function. Generally, the main function will be divided into multiple inspection functions according to the inspection content, and each inspection function can call the basic library function and inspection logic according to the inspection requirements to perform the inspection. Among them, the inspection task can achieve task distribution through the message queue, support cluster processing, making the design work and the inspection work relatively independent and not affecting each other.

[0089] Specifically, as Figure 5 shown, Figure 5 is the flow schematic diagram of the inspection rule structuring provided by the embodiment of the present application. The user can create a task to perform inspections on certain inspection items of the parsed EDA file. Creating a task can include inspection items, so that the inspection rules can be automatically matched according to the inspection items, and then the corresponding inspection functions can be called for inspection. In the embodiment, the user can set the configuration file as needed, that is, the inspection configuration file. For example, the rules can be adjusted, specifically by adjusting the inspection functions. For example, the corresponding inspection functions can be added, deleted, or modified.

[0090] It should be noted that the above user can refer to the executor of the inspection and / or the requester of the detection task.

[0091] In the embodiments, the inspection rules can adopt a unified structured configuration file. During inspection, the corresponding type can be selected according to the file information, and the inspection rule set can be assembled to achieve automatic rule matching. When creating an inspection rule, only by adding the corresponding content in the configuration, the connection relationship between the inspection rule and the inspection function can be established, realizing configurable management of inspection rules.

[0092] Among them, the inspection scope of the inspection rules can be not limited to design rules, but also include rules such as process design requirements, manufacturing requirements or safety regulations requirements. During automatic rule matching, the inspection rule set can be automatically matched according to the file information. For example, the circuit schematic diagram and the PCB layout respectively correspond to different inspection rule sets, so that the corresponding inspection rule set can be determined according to the file type in the file information. In addition, the inspection rule set can also include multiple subsets. For example, single-board and multi-board can respectively correspond to different subsets, etc. The embodiments are not limited thereto.

[0093] In terms of the scalability of the rules, the configuration file in the embodiments can be stored on the execution machine side. When it is necessary to modify, add or delete rules, it can be achieved by modifying the configuration file in the specified format and modifying or adding the corresponding inspection script, which has the characteristic of strong scalability.

[0094] In the embodiments provided by this application, combined Figure 3 As shown, according to the structured inspection result data, the inspection rule list can be automatically parsed and matched according to the mapping relationship, the result can be automatically marked, and the review result report can be automatically generated. At the same time, the structured result file can also be read by the inspection tool, and the review results are displayed in a list, including qualified items and unqualified items. Among the unqualified items, for example, information such as the coordinates, element type, display area or error type of the unqualified content can be included, which can directly reverse-locate to the unqualified element, facilitating the user to directly view.

[0095] Exemplarily, the unqualified items can be reflected in the inspection result document, showing which inspection items are unqualified and giving the reasons for the unqualified. The unqualified items in the result document can include jump links. The user can click on the unqualified item to jump to the corresponding position of, for example, the PCB layout, and the content of the unqualified item will be marked in the PCB layout, facilitating the user to timely discover and handle problems.

[0096] The embodiments provided in this application, for example, in the field of EDA, can automate rule checking, which can greatly improve the checking efficiency. The embodiments can encapsulate the complex checking process and execute it on the background service and the execution machine, which can reduce the dependence on tools. Especially for those who are not familiar enough with the tools, they only need to submit simply to achieve rule checking, which is beneficial to establishing a standardized review process. And the checking rules in the embodiments have the characteristics of strong scalability. When new rules need to be added, only the rule file and the corresponding configuration need to be added to the execution machine to achieve. The embodiments can echo in the design project by unifying the structured result data and automatically annotating the checking content and the checking result, which helps to quickly locate and fix problems.

[0097] As a specific implementation of the above embodiments, in the embodiments provided in this application, taking the inspection of five basic silk screens in the PCB layout as an example for illustration. Among them, the five basic silk screens of the PCB refer to the additional text information located on the front and back of the PCB, which is used to mark the single-board information and includes the single-board name, the manufacturer's LOGO, the barcode / QR code, the anti-static label, and the lead-free label. When a certain silk screen is missing, it may lead to PCB board modification. Specifically, the following process can be included:

[0098] (1) After the user creates a new inspection task, they can upload the engineering file, which is handed over to the background file parsing program to perform data structured parsing on the engineering design file to obtain design data such as devices, packages, and silk screens, and store these data. Specifically, reference can be made to Figure 6 as shown Figure 6 which is a schematic diagram of PCB layout parsing data provided by the embodiments of this application.

[0099] For example, Figure 6 in it, the PCB layout file can be parsed to obtain information such as PCB basic information, package list, device list, network list, and silk screen list. Among them, each package in the package list can include information such as name, outer frame, and pads. The outer frame can specifically also include information such as outer frame shape and outer frame size, and the pads can include information such as pad shape and pad size. Each device in the device list can specifically include information such as name, position, type, pins, and package name. Each network in the network list can specifically include information such as name, connection, via, and copper foil. Each layer of silk screen in the silk screen list can include information such as name, shape, and position. It can be specifically set or adjusted according to needs, and the embodiments are not limited thereto.

[0100] (2) The user can, according to needs, for example, select the basic silk screen as the inspection item. After starting the inspection, the inspection result can be viewed after the inspection is completed. The result overview can be displayed on the page. If the user needs to view the details, the result file can be exported and opened for viewing through a dedicated PCB tool.

[0101] In the embodiment, as Figure 7A shown Figure 7A is a schematic diagram of the basic silk screen inspection process provided by the embodiment of the present application. During the inspection process, the background can call the main inspection function according to the inspection items, and call the inspection sub-functions of the five basic silk screens according to the inspection requirements. Each sub-function performs the inspection by the following program: The silk screen layer can be specified. Among them, the PCB layer range for searching can be specified, and the search type can be of the Text (text) type. For example, the top (top) silk screen layer or the bottom (bottom) silk screen layer can be specified, etc. By reading the silk screen data of this layer from the structured data, searching is performed according to the specified range and type to obtain the search result; among them, the type of the search result including the basic silk screen name of the symbol is of the Text type. By traversing the search result and judging whether it meets the inspection rules. If it does not meet the inspection rules, it is deleted from the original result, that is, the search result; if it meets the inspection rules, the PCB layer and coordinates where the basic silk screen name of the Text type is located are obtained, which is convenient for directly jumping according to the PCB layer and coordinates on the result interface.

[0102] The embodiment can judge the above search result according to the quantity requirement. For example, if the quantity is greater than zero, it is determined that at least one basic silk screen exists; otherwise, if the quantity is less than zero, it is considered not to meet the requirements. If the inspection passes, the inspection result information can be integrated and merged into the inspection results of the five basic silk screens. In the embodiment, if there are multiple, they can be further confirmed, and the traversed text objects and their position information are encapsulated into the result file.

[0103] In the embodiment, the detailed information in the inspection result data can be viewed through the PCB tool. For each inspection result, the embodiment can automatically locate the problem point to achieve linkage, and can also confirm whether the inspection item meets the requirements according to the inspection result.

[0104] As shown in the figure Figure 7B is a schematic diagram of the inspection result browsing provided by the embodiment of the present application. The user can view the inspection result through the inspection result preview, and can select the specific inspection item to view in the list of inspection results. By receiving the click operation of the user on the target inspection item, by obtaining the PCB layer and coordinates detected by this inspection item, it jumps to the corresponding display interface for display. For example, when the user clicks Figure 7B the electrostatic inspection item in the five basic silk screen inspections, the electrostatic mark in the corresponding PCB layout diagram will be displayed on the display interface, and the detailed description of the inspection result will be displayed. This is convenient for the user to quickly locate the inspection item, which is convenient for operations such as verification or modification.

[0105] Based on the above embodiment, the embodiment of the present application also provides an electronic design automation data inspection method, asFigure 8 As shown, the method may include the following steps:

[0106] In step S810, the electronic design automation data to be inspected and the inspection configuration file are obtained respectively.

[0107] Among them, the inspection configuration file includes inspection rules for inspecting the electronic design automation data, and the inspection rules are editable rules. The inspection rules are structured data, and the structured data may include rule inspection functions;

[0108] In the embodiment, the electronic design automation data to be inspected, that is, the EDA file, may specifically be a circuit schematic diagram or a PCB layout, or may also be a related CDA design diagram, and the embodiment is not limited thereto.

[0109] Among them, the embodiment takes the electronic design automation data to be inspected as the PCB layout to be inspected as an example for illustration. The PCB refers to a substrate for supporting and connecting electronic components, and realizes the electrical connection between electronic components by printing conductive paths, pads and other features on an insulating substrate. The inspection configuration file may include inspection rules for inspecting the electronic design automation data determined based on the user's setting operation.

[0110] In the embodiment, for example, when it is necessary to inspect the EDA file, the user can configure the configuration file. The configuration file may include various inspection rules for inspecting the EDA file. The user can determine the inspection rules in the configuration file through addition, modification or deletion operations, so that the EDA file can be inspected through the inspection rules in the configuration file.

[0111] In the embodiment, a selection operation of the user on the interface may also be received. For example, the inspection items of the EDA file selected by the user are received, and the corresponding inspection rules are determined based on the inspection items, and then the inspection configuration file can be automatically generated.

[0112] In step S820, the electronic design automation data to be inspected is inspected based on the rule inspection function, and an inspection result is generated.

[0113] In the embodiment, the inspection configuration file includes inspection rules for inspecting the electronic design automation data. The user can edit the inspection rules, and the inspection rules are structured data. The structured data may include rule inspection functions, and the embodiment may be simply referred to as inspection functions. The inspection configuration file may specifically be an inspection script. When the inspection script is executed, the inspection function corresponding to the inspection rule can be called, and the EDA file is inspected through the inspection function, such as the silkscreen inspection in the PCB layout, etc.

[0114] In the embodiment, in combination with Figure 3As shown, the inspection configuration file may further include the correspondence between inspection rules and inspection functions. Based on this correspondence, the inspection function corresponding to the inspection rule can be obtained, and the corresponding inspection function can be called.

[0115] The electronic design automation data inspection method provided by the embodiments of the present application obtains the electronic design automation data to be inspected and the inspection configuration file, so that the inspection function corresponding to the inspection rule can be called based on the inspection configuration file, and the electronic design automation data to be inspected can be inspected through the inspection function to generate an inspection result. In the embodiment, since the inspection configuration file is an editable rule, the inspection rules that need to be used to inspect the electronic design automation data to be inspected can be determined based on the user's editing operation, and the inspection rules in the configuration file can be flexibly adjusted according to the user's needs, such as adding, deleting, or modifying the inspection rules. This can avoid the situation where the inspection content in the related art is relatively single and not extensible, so that the embodiments of the present application can improve the inspection efficiency of the electronic design automation data to be inspected.

[0116] Based on the above embodiments, in another embodiment provided by the present application, the above step S820 may specifically further include the following steps:

[0117] Step S821, receive an inspection task. Wherein, the inspection task is used to indicate to perform an inspection on the electronic design automation data to be inspected, and the inspection task includes one or more task inspection items.

[0118] In the embodiment, an operation of creating a task initiated by the user can be received, and the EDA file and task inspection items that the user needs to inspect can be obtained. For example, the user can upload the required EDA file on the display page and check the task inspection items on the page.

[0119] Step S822, respectively obtain the target inspection rules that match each task inspection item.

[0120] Step S823, perform an inspection based on the task inspection items, the target inspection rules, and the inspection configuration file.

[0121] In the embodiment, each task inspection item may correspond to one or more inspection rules. As shown in Figure 3 , inspection item 1 corresponds to inspection rule 1, and inspection item 2 corresponds to inspection rule 1 and inspection rule 2. That is, there is a correspondence between the task inspection items and the inspection rules. By obtaining the inspection rules corresponding to the task inspection items, an inspection configuration file can be generated based on the task inspection items and the inspection rules, so that the inspection configuration file can be flexibly configured according to the user's task inspection needs. Among them, each inspection rule is equivalent to an inspection program, which can perform an inspection on the EDA file in a certain aspect.

[0122] Based on the above embodiments, in another embodiment provided by the present application, in step S822, when obtaining the inspection rules that match multiple task inspection items respectively, the following steps may specifically be further included:

[0123] Step S8221, obtain the data type of the electronic design automation data to be inspected.

[0124] In the embodiment, it is possible to support electronic design automation data of different data types. For example, circuit schematics or PCB layouts, etc.

[0125] Step S8222, obtain the corresponding inspection rule set based on the data type, and respectively obtain the inspection rules that match multiple task inspection items from the inspection rule set.

[0126] In the embodiment, it is possible to support electronic design automation data of different data types, and different data types may correspond to different inspection rule sets. For example, the circuit schematic corresponds to the inspection rule set of the circuit schematic, and the PCB layout corresponds to the inspection rule set of the PCB layout. In this way, the corresponding inspection rules are called from the corresponding inspection rule set based on the data type to improve the inspection efficiency. Among them, the inspection rule set may include multiple inspection functions. For example, as shown in Figure 4 In the inspection rule set corresponding to the PCB layout, the inspection function corresponding to the inspection rule may be called from the basic library function.

[0127] Based on the above embodiments, in another embodiment provided by the present application, it is possible to obtain that the user can perform a target operation on the inspection configuration file, and the target operation may include: rule modification, rule addition, or rule deletion.

[0128] When the target operation is rule modification, modify the corresponding inspection rule, and re - establish the corresponding relationship between the modified inspection rule and the inspection function in the inspection rule set.

[0129] Or, when the target operation is rule addition, add the corresponding inspection rule, and establish an association relationship between the added inspection rule and the inspection function in the inspection rule set.

[0130] Or, when the target operation is rule deletion, delete the corresponding inspection rule.

[0131] In an embodiment, when it is necessary to modify the inspection rules, the corresponding inspection content in the inspection rules may be modified. Since different inspection contents need to call different inspection functions for inspection. Therefore, when modifying the inspection rules, it is necessary to re - establish the correspondence between the inspection functions in the inspection rule set. Similarly, when adding inspection rules, it is necessary to establish the association between the added inspection rules and the inspection functions in the inspection rule set, so that when the data is inspected through the newly added inspection rules, the corresponding inspection functions can be called. When performing a deletion operation on the inspection rules in the embodiment, only the corresponding inspection rules need to be deleted.

[0132] Based on the above - mentioned embodiment, in another embodiment provided by the present application, the above - mentioned inspection result includes inspection non - compliant items. When obtaining the inspection result, specifically, a detection result table can be generated based on the non - compliant items. The detection result table includes the display content of the non - compliant items, and the content includes one or several of the position information of the components, the non - compliant area information, the connection relationship information, and the error type information.

[0133] In an embodiment, when inspecting an EDA file, general users are concerned about the inspection non - compliant items in order to adjust the content corresponding to the inspection non - compliant items so that the inspection is qualified. Therefore, the embodiment can generate a detection result table for the inspection result of the inspection non - compliant items and output the detection result table. By sending the detection result table to the terminal and displaying the detection result table through the terminal, the specific content of the non - compliant items in the detection result table can be displayed, so that users can quickly and specifically adjust the content of the non - compliant items, which can greatly improve the adjustment efficiency of users for the content of the non - compliant items.

[0134] Based on the above - mentioned embodiment, in another embodiment provided by the present application, the above - mentioned inspection result includes inspection non - compliant items. In obtaining the inspection result, the target position of the inspection non - compliant items is associated in the inspection result. Based on the above - mentioned inspection result, the display interface diagram corresponding to the electronic design automation data to be inspected and the target position of the target non - compliant items are displayed on the terminal, and the target non - compliant items are displayed at the corresponding positions on the display interface diagram. By displaying the non - compliant items on the display interface of the EDA file, users can more intuitively see where the problems occur, which is convenient for users to modify the EDA file in a timely manner, thereby improving the processing efficiency.

[0135] In the embodiment provided by the present application, the above - mentioned inspection result may further include a jump link, which is used to jump to the display interface diagram corresponding to the electronic design automation data to be inspected and display the target non - compliant items at the target position in the display interface diagram.

[0136] In the embodiment, when it is necessary to display the target non - compliant item at the target position on the terminal display interface diagram, the selection operation of the target non - compliant item in the detection result table by the user can also be received. Among them, the selection operation includes operations such as clicking on the selected target non - compliant item in the detection result table. At this time, it can jump to the display interface diagram corresponding to the electronic design automation data to be inspected, and display the target non - compliant item at the target position in the display interface diagram.

[0137] In the embodiment, on the basis of displaying non - compliant items in the above - mentioned detection result table, corresponding jump links can be added to each non - compliant item. In this way, when the user performs a selection operation such as clicking on the target non - compliant item in the detection result table, by obtaining the target position of the target non - compliant item on the display interface diagram and displaying the target non - compliant item at the target position on the display interface diagram, the user can more intuitively understand the problems in the EDA file. For example, the target position can specifically be the coordinate information in the PCB layout, such as the electrostatic identification in the top silk - screen layer of the PCB layout.

[0138] Based on the above - mentioned embodiment, in the embodiment provided by the present application, the electronic design automation data to be inspected includes a printed circuit board, that is, a PCB layout. The above - mentioned step S820 can specifically further include the following steps:

[0139] Step S824: Analyze the printed circuit board to obtain structured analysis data.

[0140] Among them, the structured analysis data includes one or more of component information, connection information between components, package information, via information, silk - screen information, trace information, or pad information in the printed circuit board.

[0141] Step S825: Check based on the rule check function corresponding to the structured data to generate a check result.

[0142] In the embodiment, for example, by analyzing the PCB layout, structured data can be obtained, which is convenient for checking the analyzed data through various rules. When checking the PCB layout through various rules, it is not necessary to traverse all the data in the PCB layout, but only need to traverse the data in the analyzed data corresponding to the rules.

[0143] Based on the above - mentioned embodiment, when checking the basic silk - screen in the PCB layout, the above - mentioned step S820 can specifically further include the following steps:

[0144] Step S826: When checking the silk - screen information of the printed circuit board, obtain the silk - screen information of each silk - screen layer in the printed circuit board from the structured analysis data.

[0145] Step S827: Check each silk-screen layer of the printed circuit board based on the target rule check function corresponding to the silk-screen information, and generate a check result.

[0146] In the embodiment, when performing five basic silk-screen checks, the silk-screen data of each silk-screen layer in the printed circuit board can be obtained from the above-mentioned structured analysis data. And check each silk-screen layer of the printed circuit board based on the target rule check function corresponding to the silk-screen data. For example, according to the inspection items, the main inspection function can be called, and according to the inspection requirements, the inspection sub-functions of the five basic silk-screens can be called, and each sub-function is used to check the specified silk-screen layer.

[0147] In the embodiment of the present application, when performing basic silk-screen checks, by obtaining the silk-screen data of each silk-screen layer in the printed circuit board from the structured analysis data and calling the target rule check function to check each silk-screen layer of the printed circuit board, a check result for checking the silk-screen information of the printed circuit board can be quickly obtained.

[0148] In the case of dividing each functional module according to the corresponding functions, the embodiment of the present application provides an electronic design automation data inspection device, and the electronic design automation data inspection device can be located in the above-mentioned execution machine. Figure 9 It is a schematic block diagram of the functional modules of the electronic design automation data inspection device provided by an exemplary embodiment of the present application. As Figure 9 shown, the electronic design automation data inspection device includes:

[0149] A data acquisition module 10, configured to respectively acquire the electronic design automation data to be inspected and an inspection configuration file; wherein, the inspection configuration file includes inspection rules for inspecting the electronic design automation data, and the inspection rules are editable rules; the inspection rules are structured data, and the structured data includes rule check functions;

[0150] An inspection module 20, configured to inspect the electronic design automation data to be inspected based on the rule check function, and generate an inspection result.

[0151] In another embodiment provided by the present application, the data acquisition module is specifically configured to:

[0152] Receive an inspection task, where the inspection task is used to indicate to perform an inspection on the electronic design automation data to be inspected; the inspection task includes a plurality of task inspection items;

[0153] Respectively obtain target inspection rules that match the plurality of task inspection items;

[0154] Perform an inspection based on the task inspection items, the target inspection rules, and the inspection configuration file

[0155] In another embodiment provided by the present application, the data acquisition module is further specifically configured to:

[0156] Obtain the data type of the electronic design automation data to be inspected;

[0157] Based on the data type, obtain the corresponding set of inspection rules, and respectively obtain the target inspection rules that match the multiple task inspection items from the set of inspection rules.

[0158] In another embodiment provided by the present application, the device further includes an inspection configuration file adjustment module, which is specifically configured to:

[0159] Obtain the target operation of the user on the inspection configuration file; the target operation includes: rule modification, rule addition, or rule deletion;

[0160] When the target operation is rule modification, modify the corresponding rule inspection rule, and re - establish the correspondence between the modified inspection rule and the rule inspection function in the set of inspection rules;

[0161] When the target operation is rule addition, add the corresponding rule inspection rule, and establish an association relationship between the added inspection rule and the inspection function in the set of inspection rules;

[0162] When the target operation is rule deletion, delete the corresponding inspection rule.

[0163] In another embodiment provided by the present application, the inspection result includes inspection non - compliant items; the inspection module is specifically configured to:

[0164] Generate an inspection result table based on the non - compliant items; wherein, the inspection result table includes the content of the non - compliant items, and the content includes: one or several of the position information of components, non - compliant area information, connection relationship information, and error type information.

[0165] In another embodiment provided by the present application, the inspection result includes inspection non - compliant items; the inspection module is further specifically configured to:

[0166] Output the inspection result table.

[0167] In another embodiment provided by the present application, the inspection module is further specifically configured to:

[0168] The jump link is used to jump to the display interface diagram corresponding to the electronic design automation data to be inspected, and display the target non - compliant item at the target position in the display interface diagram.

[0169] In yet another embodiment provided by the present application, the electronic design automation data to be inspected includes a printed circuit board, and the inspection module is specifically further configured to:

[0170] Parse the printed circuit board to obtain structured parsing data; wherein, the structured data includes one or more of component information, connection information between components, package information, via information, silk screen information, trace information, or pad information in the printed circuit board;

[0171] Perform an inspection based on the rule inspection function corresponding to the structured data to generate an inspection result.

[0172] In yet another embodiment provided by the present application, the electronic design automation data to be inspected includes a printed circuit board, and the inspection module is specifically further configured to:

[0173] When performing a silk screen inspection on the printed circuit board, obtain the silk screen information of each silk screen layer in the printed circuit board from the structured parsing data;

[0174] Perform an inspection on each silk screen layer of the printed circuit board based on the target rule inspection function corresponding to the silk screen information to generate an inspection result.

[0175] The electronic design automation data inspection device provided by the embodiments of the present application obtains the electronic design automation data to be inspected and the inspection configuration file, so that the inspection function corresponding to the inspection rule can be called based on the inspection configuration file, and the electronic design automation data to be inspected is inspected through the inspection function to generate an inspection result. In the embodiment, since the inspection configuration file is an editable rule, the inspection rule that needs to be used to inspect the electronic design automation data to be inspected can be determined based on the editing operation of the user, and the inspection rule in the configuration file can be flexibly adjusted according to the needs of the user, such as adding, deleting, or modifying the inspection rule, which can avoid the situation in the related art where the inspection content is relatively single and not extensible, so that the embodiments of the present application can improve the inspection efficiency of the electronic design automation data to be inspected.

[0176] The embodiments of the present application further provide an electronic device, including: at least one processor; a memory for storing executable instructions of the at least one processor; wherein, the at least one processor is configured to execute the instructions to implement the above method of the embodiments of the present application.

[0177] Figure 10 It is a schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application. As Figure 10As shown, the electronic device 1800 includes at least one processor 1801 and a memory 1802 coupled to the processor 1801. The processor 1801 may execute the corresponding steps in the above method of the embodiments of the present application.

[0178] The above-mentioned processor 1801 may also be referred to as a central processing unit (CPU). It may be an integrated circuit chip with the ability to process signals. Each step in the above method of the embodiments of the present application may be completed by the integrated logic circuit in the hardware of the processor 1801 or by instructions in the form of software. The above-mentioned processor 1801 may be a general-purpose processor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in the memory 1802, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and other well-known storage media in the art. The processor 1801 reads the information in the memory 1802 and completes the steps of the above method in combination with its hardware.

[0179] In addition, when various operations / processes according to the embodiments of the present application are implemented through software and / or firmware, they can be installed from a storage medium or a network into a computer system with a dedicated hardware structure, such as Figure 11 the computer system 1900 shown. When various programs are installed in this computer system, it can execute various functions, including the functions described above, etc. Figure 11 It is a structural block diagram of a computer system provided for an exemplary embodiment of the present application.

[0180] The computer system 1900 is intended to represent computer devices of various forms of digital electronics, such as, laptop computers, desktop computers, workstations, personal digital assistants, servers, mainframe computers, and other suitable computers. The electronic devices can also represent various forms of mobile devices, such as, personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only examples and are not intended to limit the implementation of the embodiments of the present application described herein and / or claimed.

[0181] As Figure 11 shown, the computer system 1900 includes a computing unit 1901, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1902 or a computer program loaded from a storage unit 1908 into a random access memory (RAM) 1903. In the RAM 1903, various programs and data required for the operation of the computer system 1900 can also be stored. The computing unit 1901, the ROM 1902, and the RAM 1903 are connected to each other via a bus 1904. An input / output (I / O) interface 1905 is also connected to the bus 1904.

[0182] A plurality of components in the computer system 1900 are connected to the I / O interface 1905, including: an input unit 1906, an output unit 1907, a storage unit 1908, and a communication unit 1909. The input unit 1906 can be any type of device capable of inputting information into the computer system 1900. The input unit 1906 can receive input digital or character information and generate key signal inputs related to the user settings and / or function controls of the electronic device. The output unit 1907 can be any type of device capable of presenting information and can include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 1908 can include, but is not limited to, magnetic disks, optical disks. The communication unit 1909 allows the computer system 1900 to exchange information / data with other devices via a network such as the Internet and can include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chip set, such as a BluetoothTM device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0183] The computing unit 1901 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 1901 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1901 executes the various methods and processes described above. For example, in some embodiments, the above-described methods of the embodiments of the present application can be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as the storage unit 1908. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device via the ROM 1902 and / or the communication unit 1909. In some embodiments, the computing unit 1901 can be configured to execute the above-described methods of the embodiments of the present application in any other suitable manner (e.g., by means of firmware).

[0184] The embodiments of the present application also provide a computer-readable storage medium, wherein when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the above-described methods of the embodiments of the present application.

[0185] The computer-readable storage medium in the embodiments of the present application can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. The above computer-readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the above. More specifically, the above computer-readable storage medium can include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0186] The above computer-readable medium can be included in the above electronic device; or it can exist separately without being assembled into the electronic device.

[0187] The embodiments of the present application also provide a computer program product, including a computer program, wherein when the computer program is executed by a processor, the above-described methods of the embodiments of the present application are implemented.

[0188] In embodiments of the present application, computer program code for performing the operations of the embodiments of the present application may be written in one or more programming languages or combinations thereof. The above-mentioned programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network (including a local area network (LAN) or a wide area network (WAN)), or may be connected to an external computer.

[0189] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0190] The modules, components, or units described in the embodiments of the present application may be implemented in software or in hardware. Among them, the names of the modules, components, or units do not, in some cases, constitute a limitation on the modules, components, or units themselves.

[0191] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary hardware logic components that may be used include: field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard products (ASSP), system on a chip (SOC), complex programmable logic devices (CPLD), and so on.

[0192] The above description is only some embodiments of the present application and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the embodiments involved in the present application is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above application concept. For example, the technical solutions formed by mutually replacing the above features with (but not limited to) the technical features with similar functions in the embodiments of the present application.

[0193] Although some specific embodiments of the present application have been described in detail by way of examples, those skilled in the art should understand that the above examples are only for illustration and not for limiting the scope of the present application. Those skilled in the art should understand that the above embodiments can be modified without departing from the scope and spirit of the present application. The scope of the present application is defined by the appended claims.

Claims

1. An electronic design automation data checking method, characterized in that: The method comprises: respectively obtaining electronic design automation data to be checked and a check configuration file; Wherein, the inspection configuration file includes inspection rules for inspecting electronic design automation data, and the inspection rules are editable rules; the inspection rules are structured data, and the structured data includes rule inspection functions; The electronic design automation data to be checked is checked based on the rule checking function to generate a checking result.

2. The method according to claim 1, characterized in that: The obtaining of the inspection configuration file includes: receiving an inspection task, wherein the inspection task is used to instruct to perform an inspection on the electronic design automation data to be inspected; the inspection task includes a plurality of task inspection items; Respectively obtaining target inspection rules matching the multiple task inspection items; An inspection is performed based on the task inspection items, the target inspection rules, and the inspection configuration file.

3. The method according to claim 2, characterized in that The obtaining of inspection rules matching the plurality of task inspection items respectively includes: Acquire the data type of the electronic design automation data to be checked; A corresponding inspection rule set is acquired based on the data type, and target inspection rules matching the multiple task inspection items are respectively acquired from the inspection rule set.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Obtaining a target operation of the user on the inspection configuration file; the target operation includes: rule modification, rule addition or rule deletion; When the target operation is rule modification, modify the corresponding inspection rule, and re-establish the corresponding relationship between the modified inspection rule and the rule inspection function in the inspection rule set; Alternatively, when the target operation is rule addition, a corresponding check rule is added, and an association relationship is established between the added check rule and a rule check function in the check rule set; Alternatively, when the target operation is rule deletion, the corresponding inspection rule is deleted.

5. The method according to any one of claims 1 to 4, characterized in that: The inspection results include inspection failures; The step of checking the electronic design automation data to be checked and generating a check result includes: A test result table is generated based on the unqualified items; wherein the test result table includes the contents of the unqualified items, and the contents include: one or more of component location information, unqualified area information, connection relationship information and error type information.

6. The method according to claim 5, characterized in that The method further comprises: Output the detection result table.

7. The method according to claim 6, characterized in that The test result table also includes a jump link; The jump link is used to jump to the display interface diagram corresponding to the electronic design automation data to be checked, and display the target unqualified item at a target position in the display interface diagram.

8. The method according to any one of claims 1 to 7, characterized in that: The electronic design automation data to be checked includes a printed circuit board; Checking the electronic design automation data to be checked based on the rule checking function to generate a checking result; comprising: Parsing the printed circuit board to obtain structured parsed data; wherein the structured data includes one or more of component information in the printed circuit board, connection information between components, packaging information, via information, silk screen information, routing information or pad information; A check is performed based on the rule check function corresponding to the structured data to generate a check result.

9. The method according to claim 8, characterized in that The step of checking the electronic design automation data to be checked based on the rule checking function and generating a checking result comprises: When performing a silk-screen inspection on a printed circuit board, obtaining silk-screen information of each silk-screen layer in the printed circuit board from the structured parsed data; Each silk-screen layer of the printed circuit board is inspected based on the target rule inspection function corresponding to the silk-screen information to generate an inspection result.

10. An electronic device, characterized in that: include: Memory and processor; The memory is used to store program instructions for at least one processor; a memory for storing the at least one processor-executable instruction; The at least one processor is configured to execute the program instructions to implement the method according to any one of claims 1 to 9.

Images