Constraint file import method, device, equipment and storage medium
By analyzing and matching signals in the constraint file and updating signal constraint rules in the constraint interface, the problem of repeated allocation of pins in IP cured wiring is solved, and the work efficiency and user experience is improved.
Patent Information
- Application Number
- CN202211151714.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-21
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-09-21
AI Technical Summary
When existing IPs cured wiring, they need to repeatedly assign pins to signals on the UI interface, resulting in increased workload and extended wiring time, and poor user experience.
By receiving the request signal to import the constraint file, parsing and matching the signals in the constraint file and the signals in the target constraint interface. If the match is successful, the signal constraint rules in the constraint interface will be updated to reduce repeated operations.
It reduces the workload of IP cured wiring, shortens wiring time, and improves user experience. Users can directly import existing constraint files, and there is no need to repeatedly allocate pins when generating authorization files.
Smart Images

Figure CN115544950B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of integrated circuit wiring layout, and in particular relates to a constraint file importing method, device, equipment and storage medium. Background Art
[0002] When HMIC_S IP (IP curing wiring tool software) generates IP for curing wiring, it is necessary to assign pins to signals on the UI interface. Only when the pins of all signals are assigned correctly can the wiring project of the generated IP run smoothly and be used normally. However, each time an IP is generated for curing wiring, it is necessary to repeat the process of assigning pins to signals on the UI interface, which increases the workload and wiring time of IP curing wiring and results in a poor user experience. Summary of the invention
[0003] Based on this, the present invention provides a constraint file importing method, device, equipment and storage medium, which solves the problem that in the existing IP solidification wiring, it is necessary to repeatedly assign pins to signals on the UI interface, which increases the workload and wiring time during IP solidification wiring and causes a poor user experience.
[0004] The present invention provides a method for importing a constraint file, the method comprising:
[0005] receiving a request signal for importing a constraint file, and acquiring the constraint file according to the request signal; wherein the constraint file is used to clarify constraint rule information;
[0006] Parsing the constraint file to obtain matching information, and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information, wherein the matching information is a signal identifier for identifying the signal; the signal in the constraint file corresponds to the signal in the target constraint interface;
[0007] If the signal in the constraint file matches the signal in the target constraint interface successfully, the constraint rule of the signal in the constraint interface is updated according to the target constraint rule information of the signal in the target constraint file.
[0008] Further, the acquiring the constraint file according to the request signal includes:
[0009] Generate a query request according to the request signal, and obtain feedback information according to the query request, wherein the feedback information is used to provide a storage path of the constraint file;
[0010] The feedback information is received, and the constraint file is read according to the storage path of the constraint file provided by the feedback information.
[0011] Further, the acquiring the constraint file according to the request signal includes:
[0012] Sending a path access entry and a storage path list according to the request signal; the path access entry is used to select a storage path of the constraint file in the storage path list;
[0013] The storage path of the constraint file selected in the path access entry is received, and the constraint file is read according to the storage path of the constraint file.
[0014] Further, the parsing of the constraint file to obtain matching information and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information is specifically as follows:
[0015] Parsing the constraint file to obtain the signal identifier in the constraint file;
[0016] According to the signal identifier in the constraint file, identifying whether the signal in the constraint file is the same as the signal in the target constraint interface;
[0017] If the signal in the constraint file is the same as the signal in the target constraint interface, the signal in the constraint file and the signal in the target constraint interface are matched successfully.
[0018] Further, after receiving a request signal for importing a constraint file, obtaining the constraint file according to the request signal, parsing the constraint file, obtaining matching information, and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information, the method further includes:
[0019] Detecting whether the constraint file exists in the storage path;
[0020] If the constraint file does not exist in the storage path, sending a first error prompt signal;
[0021] If the constraint file exists in the storage path, detect whether the type of the stored file is a preset file type; if the type of the stored file is a preset file type, read the constraint file; if the type of the stored file is not a preset file type, send a second error prompt signal.
[0022] Furthermore, if the signal in the constraint file matches the signal in the target constraint interface successfully, then after updating the target constraint rule information in the target constraint file to the constraint interface, it also includes:
[0023] After updating the constraint rules of the signal in the constraint interface according to the target constraint rule information in the target constraint file, the constraint file is updated.
[0024] Further, the receiving a request signal for importing a constraint file and obtaining the constraint file according to the request signal includes:
[0025] Acquire configuration information of the constraint interface according to the received request signal;
[0026] According to the configuration information, a storage path of the constraint file corresponding to the configuration information is selected, and the constraint file is read through the storage path of the constraint file.
[0027] The present invention also provides a constraint file importing device, the device comprising:
[0028] A constraint file acquisition module, used to receive a request signal for importing a constraint file, and acquire the constraint file according to the request signal; wherein the constraint file is used to explain constraint rule information;
[0029] A parsing module, used for parsing the constraint file, obtaining matching information, and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information, wherein the signal in the constraint file corresponds to the signal in the target constraint interface;
[0030] The import module is used to update the constraint rules of the signal in the constraint interface according to the target constraint rule information of the signal in the target constraint file if the signal in the constraint file matches the signal in the target constraint interface successfully.
[0031] The present invention also provides a computer device, the computer device comprising:
[0032] Memory: used to store computer programs;
[0033] Processor: used for executing the computer program to implement the constraint file importing method as described in any one of the above items.
[0034] The present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the constraint file importing method as described in any one of the above items.
[0035] The method for importing a constraint file provided by the present invention receives a request signal for importing a constraint file, obtains the constraint file according to the request signal; then parses the constraint file, obtains matching information, matches the signal in the constraint file with the signal in the target constraint interface according to the matching information, and if the signal in the constraint file matches the signal in the target constraint interface successfully, updates the constraint rules of the signal in the constraint interface according to the target constraint rule information of the signal in the target constraint file. A constraint file import function is added to the constraint interface, and the pin constraints in the constraint file are correctly fed back and updated to the signal in the user interface by analyzing the constraint file imported by the user. When generating an authorization file, there is no need to repeatedly assign pins to each signal on the interface, and the existing constraints can be directly imported, which reduces the workload, shortens the wiring time, and improves the user experience. The present invention also provides a constraint file import device, equipment and storage medium, which can also achieve the above effects. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0037] Figure 1 A flowchart of a method for importing a constraint file provided by an embodiment of the present invention;
[0038] Figure 2 A structural block diagram of a constraint file importing device provided by an embodiment of the present invention;
[0039] Figure 3 for Figure 2 The structural block diagram of the first constraint file acquisition module;
[0040] Figure 4 for Figure 2 The structural block diagram of the second constraint file acquisition module;
[0041] Figure 5 for Figure 2 The structural diagram of the parsing module;
[0042] Figure 6 A structural block diagram of another device for importing constraint files provided by an embodiment of the present invention;
[0043] Figure 7 for Figure 2 The structural block diagram of the third constraint file acquisition module;
[0044] Figure 8 A schematic diagram of the structure of a computer device disclosed in an embodiment of the present invention;
[0045] Fig. 9 The present invention is a schematic diagram of a computer storage medium disclosed in an embodiment of the present invention. DETAILED DESCRIPTION
[0046] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by technicians in the technical field to which this application belongs; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" in the specification and claims of this application and the above-mentioned drawings and any variations thereof are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order.
[0047] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0048] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.
[0049] In the following description, use of suffixes such as “module,” “part,” or “unit” used to refer to elements is merely for facilitating description of the present application, and has no specific meaning by itself.
[0050] like Figure 1 FIG. 1 is a flow chart of a method for importing a constraint file provided in an embodiment of the present invention, wherein the method comprises:
[0051] Step S1: receiving a request signal for importing a constraint file, and obtaining the constraint file according to the request signal; wherein the constraint file is used to clarify constraint rule information;
[0052] Step S2: parsing the constraint file to obtain matching information, and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information, wherein the matching information is a signal identifier for identifying the signal; the signal in the constraint file corresponds to the signal in the target constraint interface;
[0053] Step S3: If the signal in the constraint file matches the signal in the target constraint interface successfully, the constraint rule of the signal in the constraint interface is updated according to the target constraint rule information of the signal in the target constraint file.
[0054] Specifically, the constraint file establishes a connection between the defined port number and the IO port on the FPGA board, telling the software how to allocate the defined port number to generate the corresponding bit file. There are three types of constraint files in FPGA design: user design file, netlist constraint file and physical constraint file, which can complete timing constraints, pin constraints and area constraints. The relationship between the three types of constraint files is: the user writes the user design file in the design input stage, and then the user design file and the design are synthesized to generate the netlist constraint file, and finally the physical constraint file is generated after implementation. The user design file is an ASC binary file that describes the constraints of the logic design and can be edited with a text editor. The syntax of the netlist constraint file is the same as that of the user design file. The difference between the two is that the user design file is input by the user, and the netlist constraint file is automatically generated by the synthesis tool. When the two conflict, the user design file shall prevail, because the user design file has the highest priority. The physical constraint file can be divided into two parts: one part is the physical constraints generated by mapping, and the other part is the constraints input by the user. Similarly, the user constraint input has the highest priority. In this embodiment, a netlist constraint file is taken as an example for explanation. After receiving a request signal for importing a netlist constraint file, the netlist constraint file is obtained according to the request signal; then the obtained netlist constraint file is parsed, and matching information for matching the signal in the netlist constraint file with the signal in the target constraint interface is obtained by parsing the netlist constraint file. Then, the signal in the netlist constraint file is matched with the signal in the target constraint interface according to the matching information. If the match is successful, the pin position information of the signal constraint in the netlist constraint file is updated to the pin corresponding to the signal in the constraint interface, thereby realizing the feedback of information from the netlist constraint file to the constraint interface.
[0055] In some embodiments, obtaining the constraint file according to the request signal in step S1 includes: generating a query request according to the request signal, obtaining feedback information according to the query request, and the feedback information is used to provide a storage path of the constraint file; receiving the feedback information, and reading the constraint file according to the storage path of the constraint file provided by the feedback information.
[0056] Specifically, after receiving a request signal for importing a netlist constraint file, a query request is generated according to the request signal. In the present embodiment, the query request is a path bar that provides access to the storage path of the netlist constraint file. The user fills in the storage path of the netlist constraint file to be imported in the path bar and submits it. The netlist constraint file is read according to the storage path of the netlist constraint file filled in by the user in the path bar.
[0057] In some embodiments, the step S1 obtains the constraint file according to the request signal, including: sending a path access entry and a storage path list according to the request signal; the path access entry is used to select the storage path of the constraint file in the storage path list; receiving the storage path of the constraint file selected in the path access entry, and reading the constraint file according to the storage path of the constraint file.
[0058] Specifically, after receiving a request signal for importing a netlist constraint file, a path access entry and a storage path list are sent. The user enters the storage path list through the path access entry, and directly selects the storage path of the netlist constraint file in the storage path list according to the actual storage location of the netlist constraint file. After the selection is completed, click Submit to read the netlist constraint file according to the storage path of the netlist constraint file submitted by the user.
[0059] In some embodiments, the step S2 is to parse the constraint file, obtain matching information, and match the signal in the constraint file with the signal in the target constraint interface according to the matching information, specifically: parse the constraint file, obtain the signal identifier in the constraint file; identify whether the signal in the constraint file is the same as the signal in the target constraint interface according to the signal identifier in the constraint file; if the signal in the constraint file is the same as the signal in the target constraint interface, then the signal in the constraint file and the signal in the target constraint interface are matched successfully.
[0060] Specifically, the signal identifier selected in the present embodiment is the signal name. After obtaining the netlist constraint file, the netlist constraint file is parsed to obtain the signal name of the signal in the netlist constraint file and the pin position information of the signal constraint. Then, the signal name in the constraint file and the signal name in the constraint interface are compared. If the signal name in the constraint file and the signal name in the constraint interface are consistent, the pin of the signal constraint in the constraint interface is updated according to the pin position information of the signal constraint in the constraint file, and the correct pin is assigned to the signal in the constraint interface.
[0061] In some embodiments, after step S2 and before step S3, the method further includes:
[0062] Step S201: Detect whether the constraint file exists in the storage path; if the constraint file does not exist in the storage path, send a first error prompt signal; if the constraint file exists in the storage path, detect whether the type of the stored file is a preset file type; if the type of the stored file is a preset file type, read the constraint file; if the type of the stored file is not a preset file type, send a second error prompt signal.
[0063] In some embodiments, after step S3, the method further includes:
[0064] Step S4: after updating the constraint rules of the signal in the constraint interface according to the target constraint rule information in the target constraint file, the constraint file is updated.
[0065] Specifically, after matching the signals in the netlist constraint file and the signals in the constraint interface according to the matching information, and assigning corresponding pins to the signals in the constraint interface according to the pin position information of the constraints corresponding to the signals in the netlist constraint file, the pin information corresponding to the signals in the constraint interface is updated to the netlist constraint file. When used next time, the updated netlist constraint file can be directly imported into the constraint interface, which can reduce the workload when generating authorization files.
[0066] In some embodiments, the step S1 of receiving a request signal for importing a constraint file and obtaining the constraint file according to the request signal includes: obtaining configuration information of the constraint interface according to the received request signal; selecting a storage path of the constraint file corresponding to the configuration information according to the configuration information, and reading the constraint file through the storage path of the constraint file.
[0067] Specifically, after receiving the request signal, the constraint interface is directly accessed to obtain the configuration information of the constraint interface, the storage path of the default constraint file of the constraint interface is directly obtained according to the configuration information, and the default constraint file of the constraint interface is read according to the obtained storage path.
[0068] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0069] The method for importing a constraint file provided in this embodiment receives a request signal for importing a constraint file, obtains the constraint file according to the request signal, then parses the constraint file, obtains matching information, matches the signal in the constraint file with the signal in the target constraint interface according to the matching information, and if the signal in the constraint file matches the signal in the target constraint interface successfully, updates the constraint rules of the signal in the constraint interface according to the target constraint rule information of the signal in the target constraint file. A constraint file import function is added to the constraint interface, and by analyzing the constraint file imported by the user, the pin constraints in the constraint file are correctly fed back and updated to the signal in the user interface. At the same time, when generating an authorization file, there is no need to repeatedly assign pins to each signal on the interface, and the existing constraints can be directly imported, which reduces the workload, shortens the wiring time, and improves the user experience.
[0070] like Figure 2 , which is a structural block diagram of a constraint file importing device 200 provided in an embodiment of the present invention, the device 200 includes:
[0071] The constraint file acquisition module 201 is used to receive a request signal for importing a constraint file, and acquire the constraint file according to the request signal; wherein the constraint file is used to explain constraint rule information;
[0072] A parsing module 202, configured to parse the constraint file, obtain matching information, and match the signal in the constraint file with the signal in the target constraint interface according to the matching information, wherein the signal in the constraint file corresponds to the signal in the target constraint interface;
[0073] The import module 203 is used to update the constraint rules of the signal in the constraint interface according to the target constraint rule information of the signal in the target constraint file if the signal in the constraint file matches the signal in the target constraint interface successfully.
[0074] like Figure 3 As shown, Figure 2 A structural block diagram of a constraint file acquisition module 201, wherein the constraint file acquisition module 201 includes:
[0075] A first path acquisition module 20111, configured to generate a query request according to the request signal, and acquire feedback information according to the query request, wherein the feedback information is used to provide a storage path for the constraint file;
[0076] The first reading module 20112 is used to receive the feedback information, and read the constraint file according to the storage path of the constraint file provided by the feedback information.
[0077] like Figure 4 As shown, Figure 2 A structural block diagram of another constraint file acquisition module 201 of the constraint file importing device 200, wherein the constraint file acquisition module 201 includes:
[0078] A second path acquisition module 20121 is used to send a path access entry and a storage path list according to the request signal; the path access entry is used to select a storage path of the constraint file in the storage path list;
[0079] The second reading module 20122 is used to receive the storage path of the constraint file selected in the path access entry, and read the constraint file according to the storage path of the constraint file.
[0080] like Figure 5 As shown, Figure 2 The structural block diagram of the analysis module 202 in FIG. 2 includes:
[0081] A signal identification acquisition module 221 is used to parse the constraint file and acquire the signal identification in the constraint file;
[0082] An identification module 2022, configured to identify whether the signal in the constraint file is the same as the signal in the target constraint interface according to the signal identifier in the constraint file;
[0083] The matching success judgment module 2023 is used to judge that the signal in the constraint file is the same as the signal in the target constraint interface, and to judge that the signal in the constraint file and the signal in the target constraint interface are matched successfully.
[0084] like Figure 6 As shown, it is a structural block diagram of another constraint file importing device 200 provided in an embodiment of the present invention, and the device 200 also includes:
[0085] The detection module 204 is used to detect whether the constraint file exists in the storage path; if the constraint file does not exist in the storage path, a first error prompt signal is sent; if the constraint file exists in the storage path, whether the type of the storage file is a preset file type is detected; if the type of the storage file is the preset file type, the constraint file is read; if the type of the storage file is not the preset file type, a second error prompt signal is sent.
[0086] like Figure 6 As shown, the device 200 further includes: an updating module 205, which is used to update the constraint file after updating the constraint rules of the signal in the constraint interface according to the target constraint rule information in the target constraint file.
[0087] like Figure 7 As shown, Figure 2 Another structural block diagram of a constraint file acquisition module 201 is shown in FIG. 2 , wherein the constraint file acquisition module 201 includes:
[0088] The configuration information acquisition module 20131 is used to acquire the configuration information of the constraint interface according to the received request signal;
[0089] The third reading module 20132 is used to select a storage path of the constraint file corresponding to the configuration information according to the configuration information, and read the constraint file through the storage path of the constraint file.
[0090] For the specific definition of the device for importing the constraint files, please refer to the definition of the method for importing the constraint files mentioned above, which will not be repeated here. Each module in the above-mentioned device for importing the constraint files can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0091] like Figure 8 FIG. 1 is a schematic diagram of a computer device disclosed in an embodiment of the present invention. The computer device may include:
[0092] A memory 801 storing executable program codes;
[0093] A processor 802 connected to the memory 801;
[0094] The processor 802 calls the executable program code stored in the memory 801 to execute the steps in the method for importing the T constraint file of the present invention.
[0095] See also Fig. 9 The embodiment of the present invention discloses a computer storage medium 901, which stores computer instructions. When the computer instructions are called, they are used to execute the steps in the method for importing a constraint file of the present invention.
[0096] A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection with 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 thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or device.
[0097] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0098] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0099] The computer program code for performing the operation of the present application can be written in one or more programming languages or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent 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 can be connected to the user's computer through any type of network, including a local area network (Local Area Network; hereinafter referred to as: LAN) or a wide area network (Wide Area Network; hereinafter referred to as: WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).
[0100] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms "a", "said" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.
[0101] The word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.
[0102] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0103] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.
Claims
1. A method for importing a constraint file, characterized in that: The method comprises: receiving a request signal for importing a constraint file, and acquiring the constraint file according to the request signal; wherein the constraint file is used to clarify constraint rule information; Parsing the constraint file to obtain matching information, and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information, wherein the matching information is a signal identifier for identifying the signal; the signal in the constraint file corresponds to the signal in the target constraint interface; If the signal in the constraint file matches the signal in the target constraint interface successfully, updating the constraint rule of the signal in the constraint interface according to the target constraint rule information of the signal in the target constraint file; The step of parsing the constraint file, obtaining matching information, and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information is specifically as follows: Parsing the constraint file to obtain the signal identifier in the constraint file; According to the signal identifier in the constraint file, identifying whether the signal in the constraint file is the same as the signal in the target constraint interface; If the signal in the constraint file is the same as the signal in the target constraint interface, the signal in the constraint file and the signal in the target constraint interface are matched successfully; Wherein, the constraint file is a netlist constraint file, and the signal identifier is a signal name; After obtaining the netlist constraint file, the following steps are specifically performed: Parsing the netlist constraint file to obtain the signal name of the signal in the netlist constraint file and the pin position information of the signal constraint; Compare the signal names in the constraint file with the signal names in the constraint interface; If the signal name in the constraint file is consistent with the signal name in the constraint interface, the pins of the signal constraints in the constraint interface are updated according to the pin position information of the signal constraints in the constraint file, and the correct pins are assigned to the signals in the constraint interface.
2. A method for importing a constraint file according to claim 1, characterized in that: The obtaining the constraint file according to the request signal comprises: generating a query request according to the request signal, and obtaining feedback information according to the query request, wherein the feedback information is used to provide a storage path of the constraint file; The feedback information is received, and the constraint file is read according to the storage path of the constraint file provided by the feedback information.
3. A method for importing a constraint file according to claim 1 or 2, characterized in that: The obtaining the constraint file according to the request signal comprises: Sending a path access entry and a storage path list according to the request signal; the path access entry is used to select a storage path of the constraint file in the storage path list; The storage path of the constraint file selected in the path access entry is received, and the constraint file is read according to the storage path of the constraint file.
4. A method for importing a constraint file according to claim 3, characterized in that: After receiving a request signal for importing a constraint file, obtaining the constraint file according to the request signal, parsing the constraint file to obtain matching information, and before matching the signal in the constraint file with the signal in the target constraint interface according to the matching information, the method further includes: Detecting whether the constraint file exists in the storage path; If the constraint file does not exist in the storage path, sending a first error prompt signal; If the constraint file exists in the storage path, detecting whether the type of the stored file is a preset file type; If the type of the stored file is a preset file type, reading the constraint file; If the type of the stored file is not a preset file type, a second error prompt signal is sent.
5. A method for importing a constraint file according to claim 3, characterized in that: If the signal in the constraint file matches the signal in the target constraint interface successfully, then after updating the target constraint rule information in the target constraint file to the constraint interface, the method further includes: After updating the constraint rules of the signal in the constraint interface according to the target constraint rule information in the target constraint file, the constraint file is updated.
6. A method for importing a constraint file according to claim 1, characterized in that: The receiving a request signal for importing a constraint file, and acquiring the constraint file according to the request signal, comprises: Acquire configuration information of the constraint interface according to the received request signal; According to the configuration information, a storage path of the constraint file corresponding to the configuration information is selected, and the constraint file is read through the storage path of the constraint file.
7. A device for importing a constraint file, characterized in that: The device is used to implement the method for importing the constraint file according to claims 1-6, comprising: A constraint file acquisition module, used to receive a request signal for importing a constraint file, and acquire the constraint file according to the request signal; wherein the constraint file is used to explain constraint rule information; A parsing module, used for parsing the constraint file, obtaining matching information, and matching the signal in the constraint file with the signal in the target constraint interface according to the matching information, wherein the signal in the constraint file corresponds to the signal in the target constraint interface; The import module is used to update the constraint rules of the signal in the constraint interface according to the target constraint rule information of the signal in the target constraint file if the signal in the constraint file matches the signal in the target constraint interface successfully.
8. A computer device, comprising: Memory: used to store computer programs; Processor: used for executing the computer program to implement the method for importing a constraint file as described in any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for importing a constraint file as described in any one of claims 1 to 6 is implemented.
Citation Information
Patent Citations
Chip pin connection relation detection method and system
CN103728552A
IP core file generation method and device, equipment and medium
CN109857451A
FPGA pin distribution design method and device
CN110069892A
FPGA prototype design file processing method and device, equipment and medium
CN114239459A
Method and system for pin assignment
US20080109782A1
