CN115544950A - Constraint file importing method, device, equipment and storage medium - Google Patents
Constraint file importing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115544950A CN115544950A CN202211151714.3A CN202211151714A CN115544950A CN 115544950 A CN115544950 A CN 115544950A CN 202211151714 A CN202211151714 A CN 202211151714A CN 115544950 A CN115544950 A CN 115544950A
- Authority
- CN
- China
- Prior art keywords
- constraint
- file
- constraint file
- signal
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000004590 computer program Methods 0.000 claims description 9
- 230000008676 import Effects 0.000 claims description 8
- 238000013475 authorization Methods 0.000 abstract description 4
- 238000013461 design Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000007711 solidification Methods 0.000 description 2
- 230000008023 solidification Effects 0.000 description 2
- UGVTYCQVZPDYRZ-ZHACJKMWSA-N 4-[(E)-[hydroxymethyl(methyl)amino]diazenyl]-1H-imidazole-5-carboxamide Chemical compound CN(CO)\N=N\C1=C(N=CN1)C(N)=O UGVTYCQVZPDYRZ-ZHACJKMWSA-N 0.000 description 1
- 101000615941 Homo sapiens Mannosyl-oligosaccharide 1,2-alpha-mannosidase IC Proteins 0.000 description 1
- 102100021770 Mannosyl-oligosaccharide 1,2-alpha-mannosidase IC Human genes 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/30—Circuit design
- G06F30/39—Circuit design at the physical level
- G06F30/394—Routing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2111/00—Details relating to CAD techniques
- G06F2111/04—Constraint-based CAD
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Evolutionary Computation (AREA)
- Geometry (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method, a device, equipment and a storage medium for importing a constraint file, wherein the method comprises the following steps: receiving a request signal for importing a constraint file, and acquiring the constraint file according to the request signal; analyzing the constraint file, acquiring matching information, and matching signals in the constraint file with signals in a target constraint interface according to the matching information; the signals in the constraint file correspond to the signals in the target constraint interface; and if the signals of the constraint file are successfully matched with the signals in the target constraint interface, updating the constraint rules of the signals in the constraint interface according to the target constraint rule information of the signals in the target constraint file. And through analyzing the constraint file imported by the user, the pin constraint in the constraint file is correctly fed back and updated to the signal of the user interface. The assignment of pins to the various signals on the interface is not repeated when generating the authorization file.
Description
Technical Field
The invention belongs to the technical field of integrated circuit wiring layout, and particularly relates to a constraint file importing method, device, equipment and storage medium.
Background
When the HMIC _ S IP (IP curing wiring tool software) generates the IP to perform curing wiring, pins need to be distributed to signals on a UI interface, only if the pins of all the signals are correctly distributed, the wiring project for generating the IP can run through and be normally used, but when the IP is generated to perform curing wiring each time, the process of distributing the pins to the signals on the UI interface needs to be repeated, the workload and the wiring time of the IP curing wiring are increased, and the user experience is poor.
Disclosure of Invention
Based on the above, the invention provides a method, a device, equipment and a storage medium for importing a constraint file, and solves the problems that in the existing IP solidification wiring process, pins need to be repeatedly allocated to signals on a UI interface, so that the workload and the wiring time length are increased in the IP solidification wiring process, and the user experience is poor.
The invention provides a method for importing a constraint file, which comprises the following steps:
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 for setting constraint rule information;
analyzing the constraint file, acquiring matching information, and matching signals in the constraint file with signals in a target constraint interface according to the matching information, wherein the matching information is a signal identifier for identifying signals; the signals in the constraint file correspond to the signals in the target constraint interface;
and if the signals in the constraint file are successfully matched with the signals in the target constraint interface, updating constraint rules of the signals in the constraint interface according to target constraint rule information of the signals in the target constraint file.
Further, the acquiring the constraint file according to the request signal includes:
generating a query request according to the request signal, and acquiring feedback information according to the query request, wherein the feedback information is used for providing a storage path of the constraint file;
and receiving the feedback information, and reading the constraint file according to the storage path of the constraint file provided by the feedback information.
Further, the acquiring the constraint file according to the request signal includes:
sending a path access entry and a storage path list according to the request signal; the path access entry is used for selecting a storage path of the constraint file in the storage path list;
and receiving the storage path of the constraint file selected from the path access entry, and reading the constraint file according to the storage path of the constraint file.
Further, the analyzing 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 specifically includes:
analyzing the constraint file to obtain a 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 according to the signal identification in the constraint file;
and if the signal in the constraint file is the same as the signal in the target constraint interface, successfully matching the signal in the constraint file with the signal in the target constraint interface.
Further, the receiving a request signal for importing a constraint file, after obtaining the constraint file according to the request signal, analyzing the constraint file, obtaining matching information, and before matching a signal in the constraint file with a signal in a target constraint interface according to the matching information, the method further includes:
detecting whether the constraint file exists in the storage path or not;
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 storage file is a preset file type; if the type of the storage file is a preset file type, reading the constraint file; and if the type of the storage file is not the preset file type, sending a second error prompt signal.
Further, if the signal of the constraint file is successfully matched with the signal in the target constraint interface, updating the target constraint rule information in the target constraint file to the constraint interface, and further including:
and updating the constraint file after updating the constraint rule of the signal in the constraint interface according to the target constraint rule information in the target constraint file.
Further, the receiving a request signal for importing a constraint file and acquiring the constraint file according to the request signal includes:
acquiring configuration information of the constraint interface according to the received request signal;
and 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.
The invention also provides a device for importing the constraint file, which comprises:
the constraint file acquisition module is used for 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 for setting constraint rule information;
the analysis module is used for analyzing the constraint file, acquiring matching information, and matching signals in the constraint file with signals in a target constraint interface according to the matching information, wherein the signals in the constraint file correspond to the signals in the target constraint interface;
and the import module is used for 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 if the signal in the constraint file is successfully matched with the signal in the target constraint interface.
The present invention also provides a computer apparatus, comprising:
a memory: for storing a computer program;
a processor: for executing the computer program to implement the method of importing a constraint file as defined in any of the preceding claims.
The invention also provides a computer-readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the method for importing a constraint file as defined in any of the above.
The method for importing the constraint file comprises the steps of receiving a request signal for importing the constraint file, and acquiring the constraint file according to the request signal; and then analyzing the constraint file, acquiring matching information, matching the signals in the constraint file with the signals in a target constraint interface according to the matching information, and updating constraint rules of the signals in the constraint interface according to target constraint rule information of the signals in the target constraint file if the signals in the constraint file are successfully matched with the signals in the target constraint interface. And adding a constraint file import function on the constraint interface, and correctly feeding back and updating the pin constraint in the constraint file to a signal of the user interface by analyzing the constraint file imported by the user. When the authorization file is generated, pins are not required to be repeatedly distributed to all signals on the interface, the existing constraints can be directly imported, the workload is reduced, the wiring time is shortened, and the user experience is improved. The invention also provides a device, equipment and a storage medium for importing the constraint file, and the effects can be realized.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flowchart of an import method of a constraint file according to an embodiment of the present invention;
fig. 2 is a block diagram of a structure of an import apparatus of a constraint file according to an embodiment of the present invention;
FIG. 3 is a block diagram of a first constraint file acquisition module in FIG. 2;
FIG. 4 is a block diagram of a second constraint file acquisition module in FIG. 2;
FIG. 5 is a block diagram of the parsing module of FIG. 2;
fig. 6 is a block diagram of a structure of another constraint file importing apparatus according to an embodiment of the present invention;
FIG. 7 is a block diagram of a third constraint file acquisition module in FIG. 2;
FIG. 8 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of a computer storage medium according to an embodiment of the disclosure.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising," "including," and "having," and any variations thereof in the description and claims of this application and the description of the above figures, are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for the convenience of description of the present application, and have no specific meaning in themselves.
As shown in fig. 1, a schematic flow diagram of a method for importing a constraint file according to an embodiment of the present invention is provided, where the method includes:
step S1: 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 for setting constraint rule information;
step S2: analyzing the constraint file, acquiring matching information, and matching signals in the constraint file with signals in a target constraint interface according to the matching information, wherein the matching information is a signal identifier for identifying signals; the signals in the constraint file correspond to the signals in the target constraint interface;
and step S3: and if the signals in the constraint file are successfully matched with the signals in the target constraint interface, updating constraint rules of the signals in the constraint interface according to target constraint rule information of the signals in the target constraint file.
Specifically, the constraint file associates the defined port number with the IO port on the FPGA board, and tells the software how to assign the defined port number to generate the corresponding bit file. There are 3 classes of constraint files in the FPGA design: the user design file, netlist constraint file and physical constraint file can complete timing constraint, pin constraint and region constraint. The relationship of the 3 types of constraint files is as follows: a user writes a user design file in a design input stage, then the user design file and the design are synthesized to generate a netlist constraint file, and finally the netlist constraint file is generated after the user design file and the design are realized. The user design file is an ASC binary file, describes the constraints of the logic design, and can be edited by a text editor. The syntax of the netlist constraint file is the same as the user design file, and the difference between the syntax and the user design file is as follows: the user design file is input by a user, and the netlist constraint file is automatically generated by the synthesis tool, and when the user design file and the netlist constraint file conflict with each other, the user design file is taken as the standard, 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 the mapping and the other part is the constraints input by the user, and the input by the user constraints has the highest priority. In this embodiment, a netlist constraint file is taken as an example for explanation, and after a request signal for importing the netlist constraint file is received, the netlist constraint file is obtained according to the request signal; and then analyzing the obtained netlist constraint file, obtaining matching information for matching the signal in the netlist constraint file with the signal in the target constraint interface by analyzing the netlist constraint file, matching the signal in the netlist constraint file with the signal in the target constraint interface according to the matching information, and updating the pin corresponding to the signal in the constraint interface by using the pin position information constrained by the netlist constraint file signal if the matching is successful, so as to realize the feedback from the netlist constraint file to the constraint interface information.
In some embodiments, the obtaining the constraint file according to the request signal in step S1 includes: generating a query request according to the request signal, and acquiring feedback information according to the query request, wherein the feedback information is used for providing a storage path of the constraint file; and receiving the feedback information, and reading the constraint file according to the storage path of the constraint file provided by the feedback information.
Specifically, after receiving a request signal for importing the netlist constraint file, a query request is generated according to the request signal, in this embodiment, the query request is a path bar providing a storage path for accessing the netlist constraint file, a user fills in the storage path of the netlist constraint file to be imported in the path bar and submits the storage path, and the netlist constraint file is read according to the storage path of the netlist constraint file filled in the path bar by the user.
In some embodiments, the obtaining the constraint file according to the request signal in step S1 includes: sending a path access entry and a storage path list according to the request signal; the path access entry is used for selecting a storage path of the constraint file in the storage path list; and receiving the storage path of the constraint file selected from the path access entry, and reading the constraint file according to the storage path of the constraint file.
Specifically, after receiving a request signal for importing the netlist constraint file, sending a path access entry and a storage path list, enabling a user to enter the storage path list through the path access entry, directly selecting a storage path of the netlist constraint file in the storage path list according to the actual storage position of the netlist constraint file, clicking to submit after the selection is finished, and reading the netlist constraint file according to the storage path of the netlist constraint file submitted by the user.
In some embodiments, the parsing the constraint file in step S2 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 specifically includes: analyzing the constraint file to obtain a 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 according to the signal identification in the constraint file; and if the signal in the constraint file is the same as the signal in the target constraint interface, successfully matching the signal in the constraint file with the signal in the target constraint interface.
Specifically, the signal identifier selected in this embodiment is a signal name, after the netlist constraint file is obtained, the netlist constraint file is analyzed to obtain a signal name of a signal in the netlist constraint file and pin position information of the signal constraint, then the signal name in the constraint file is compared with the signal name in the constraint interface, and if the signal name in the constraint file is consistent with the signal name in the constraint interface, 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, so that a correct pin is allocated to the signal in the constraint interface.
In some embodiments, after step S2, step S3 further comprises before:
step S201: detecting whether the constraint file exists in the storage path or not; 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 storage file is a preset file type; if the type of the storage file is a preset file type, reading the constraint file; and if the type of the storage file is not the preset file type, sending a second error prompt signal.
In some embodiments, after step S3, further comprising:
and step S4: and updating the constraint file after updating the constraint rule of the signal in the constraint interface according to the target constraint rule information in the target constraint file.
Specifically, after a signal in the netlist constraint file is matched with a signal in the constraint interface according to matching information, corresponding pins are distributed for the signal in the constraint interface according to pin position information of constraint corresponding to the signal in the netlist constraint file, the pin information corresponding to the signal in the constraint interface is updated to the netlist constraint file, and when the constraint file is used next time, the updated netlist constraint file is directly led into the constraint interface, so that the workload for generating the authorization file can be reduced.
In some embodiments, the receiving a request signal for importing a constraint file in step S1, and acquiring the constraint file according to the request signal includes: acquiring configuration information of the constraint interface according to the received request signal; and 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.
Specifically, after receiving the request signal, directly accessing the constraint interface, obtaining the configuration information of the constraint interface, directly obtaining the storage path of the default constraint file of the constraint interface according to the configuration information, and reading the default constraint file of the constraint interface according to the obtained storage path.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by functions and internal logic of the process, and should not limit the implementation process of the embodiments of the present invention in any way.
In the method for importing a constraint file provided in this embodiment, a request signal for importing a constraint file is received, and the constraint file is obtained according to the request signal; and then analyzing the constraint file, acquiring matching information, matching the signals in the constraint file with the signals in a target constraint interface according to the matching information, and updating constraint rules of the signals in the constraint interface according to target constraint rule information of the signals in the target constraint file if the signals in the constraint file are successfully matched with the signals in the target constraint interface. And adding a constraint file import function on the constraint interface, and correctly feeding back and updating the pin constraint in the constraint file into a signal of the user interface by analyzing the constraint file imported by the user. Meanwhile, when the authorization file is generated, pins are not repeatedly distributed to all signals on the interface, the existing constraints can be directly imported, the workload is reduced, the wiring time is shortened, and the user experience is improved.
As shown in fig. 2, a block diagram of a structure of an apparatus 200 for importing a constraint file according to an embodiment of the present invention is provided, where the apparatus 200 includes:
a constraint file obtaining module 201, configured to receive a request signal for importing a constraint file, and obtain the constraint file according to the request signal; wherein the constraint file is used for setting constraint rule information;
an analyzing module 202, configured to analyze the constraint file, obtain matching information, and match a signal in the constraint file with a signal in a target constraint interface according to the matching information, where the signal in the constraint file corresponds to the signal in the target constraint interface;
and the importing module 203 is configured to update 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 if the signal in the constraint file is successfully matched with the signal in the target constraint interface.
As shown in fig. 3, which is a block diagram of a structure of the constraint file obtaining module 201 in fig. 2, the constraint file obtaining module 201 includes:
a first path obtaining module 20111, configured to generate an inquiry request according to the request signal, and obtain feedback information according to the inquiry request, where the feedback information is used to provide a storage path of the constraint file;
a first reading module 20112, configured to receive the feedback information, and read the constraint file according to the storage path of the constraint file provided by the feedback information.
As shown in fig. 4, a block diagram of a structure of another constraint file obtaining module 201 of the constraint file importing apparatus 200 in fig. 2 is shown, where the constraint file obtaining module 201 includes:
a second path obtaining module 20121, configured to send a path access entry and a storage path list according to the request signal; the path access entry is used for selecting a storage path of the constraint file in the storage path list;
a second reading module 20122, configured 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.
As shown in fig. 5, which is a block diagram of the parsing module 202 in fig. 2, the parsing module 202 includes:
the signal identifier obtaining module 2021 is configured to analyze the constraint file to obtain a signal identifier in the constraint file;
an identifying 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;
a matching success judging module 2023, configured to judge that the signal in the constraint file is the same as the signal in the target constraint interface, and that the signal in the constraint file and the signal in the target constraint interface are successfully matched.
As shown in fig. 6, a block diagram of another constraint file importing apparatus 200 according to an embodiment of the present invention is provided, where the apparatus 200 further includes:
a detecting module 204, configured to detect 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 storage file is a preset file type; if the type of the storage file is a preset file type, reading the constraint file; and if the type of the storage file is not the preset file type, sending a second error prompt signal.
As shown in fig. 6, the apparatus 200 further includes: an updating module 205, configured to update the constraint file after updating the constraint rule of the signal in the constraint interface according to the target constraint rule information in the target constraint file.
As shown in fig. 7, which is a block diagram of another structure of the constraint file obtaining module 201 in fig. 2, the constraint file obtaining module 201 includes:
a configuration information obtaining module 20131, configured to obtain configuration information of the constraint interface according to the received request signal;
a third reading module 20132, configured to select, according to the configuration information, a storage path of the constraint file corresponding to the configuration information, and read the constraint file through the storage path of the constraint file.
For specific limitations of the importing apparatus of the seed constraint file, reference may be made to the above limitations on the importing method of the seed constraint file, and details are not described here. The modules in the device for importing the constraint file may be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
Fig. 8 is a schematic structural diagram of a computer device disclosed in the embodiment of the present invention, where the computer device may include:
a memory 801 in which executable program code is stored;
a processor 802 connected to the memory 801;
the processor 802 calls the executable program code stored in the memory 801 to execute the steps in the import method of the T-constraint file of the present invention.
Referring to fig. 9, an embodiment of the present invention discloses a computer storage medium 901, where the computer storage medium 901 stores computer instructions, and when the computer instructions are called, the computer instructions are used to execute the steps in the method for importing a constraint file according to the present invention.
The 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 electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, 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 disc Read Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
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.
Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the 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 the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
The word "if" as used herein may be interpreted as "at 8230; \8230;" or "when 8230; \8230;" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrase "if determined" or "if detected (a stated condition or event)" may be interpreted as "upon determining" or "in response to determining" or "upon detecting (a stated condition or event)" or "in response to detecting (a stated condition or event)", depending on the context.
In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method for importing a constraint file, the method comprising:
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 for setting constraint rule information;
analyzing the constraint file, acquiring matching information, and matching signals in the constraint file with signals in a target constraint interface according to the matching information, wherein the matching information is a signal identifier for identifying signals; the signals in the constraint file correspond to the signals in the target constraint interface;
and if the signals of the constraint file are successfully matched with the signals in the target constraint interface, updating the constraint rules of the signals in the constraint interface according to the target constraint rule information of the signals in the target constraint file.
2. The method for importing a constraint file according to claim 1, wherein the obtaining the constraint file according to the request signal comprises:
generating a query request according to the request signal, and acquiring feedback information according to the query request, wherein the feedback information is used for providing a storage path of the constraint file;
and receiving the feedback information, and reading the constraint file according to the storage path of the constraint file provided by the feedback information.
3. The method for importing the constraint file according to claim 1 or 2, wherein 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 for selecting a storage path of the constraint file in the storage path list;
and receiving the storage path of the constraint file selected from the path access entry, and reading the constraint file according to the storage path of the constraint file.
4. The method for importing a constraint file according to claim 3, wherein the analyzing the constraint file to obtain matching information, and matching a signal in the constraint file with a signal in a target constraint interface according to the matching information specifically comprises:
analyzing the constraint file to obtain a 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 according to the signal identification in the constraint file;
and if the signal in the constraint file is the same as the signal in the target constraint interface, successfully matching the signal in the constraint file with the signal in the target constraint interface.
5. The method according to claim 4, wherein before the receiving a request signal for importing a constraint file, acquiring the constraint file according to the request signal, analyzing the constraint file, acquiring matching information, and matching signals in the constraint file with signals in a target constraint interface according to the matching information, the method further comprises:
detecting whether the constraint file exists in the storage path or not;
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 storage file is a preset file type;
if the type of the storage file is a preset file type, reading the constraint file;
and if the type of the storage file is not the preset file type, sending a second error prompt signal.
6. The method for importing a constraint file according to claim 4, wherein if the signal of the constraint file is successfully matched with the signal in the target constraint interface, the method further comprises, after updating the target constraint rule information in the target constraint file to the constraint interface, the method further comprising:
and updating the constraint file after updating the constraint rule of the signal in the constraint interface according to the target constraint rule information in the target constraint file.
7. The method for importing a constraint file according to claim 1, wherein the receiving a request signal for importing a constraint file and obtaining the constraint file according to the request signal comprises:
acquiring configuration information of the constraint interface according to the received request signal;
and 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.
8. An apparatus for importing a constraint file, the apparatus comprising:
the constraint file acquisition module is used for 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 for setting constraint rule information;
the analysis module is used for analyzing the constraint file, acquiring matching information, and matching signals in the constraint file with signals in a target constraint interface according to the matching information, wherein the signals in the constraint file correspond to the signals in the target constraint interface;
and the import module is used for 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 if the signal in the constraint file is successfully matched with the signal in the target constraint interface.
9. A computer device, the computer device comprising:
a memory: for storing a computer program;
a processor: an import method for executing the computer program to implement the constraint file according to any of claims 1 to 7.
10. A computer-readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing the method for importing a constraint file according to any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211151714.3A CN115544950A (en) | 2022-09-21 | 2022-09-21 | Constraint file importing method, device, equipment and storage medium |
| PCT/CN2023/114682 WO2024060926A1 (en) | 2022-09-21 | 2023-08-24 | Constraint file import method and apparatus, device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211151714.3A CN115544950A (en) | 2022-09-21 | 2022-09-21 | Constraint file importing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115544950A true CN115544950A (en) | 2022-12-30 |
Family
ID=84727080
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211151714.3A Pending CN115544950A (en) | 2022-09-21 | 2022-09-21 | Constraint file importing method, device, equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115544950A (en) |
| WO (1) | WO2024060926A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024060926A1 (en) * | 2022-09-21 | 2024-03-28 | 深圳市紫光同创电子有限公司 | Constraint file import method and apparatus, device, and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6058252A (en) * | 1995-01-19 | 2000-05-02 | Synopsys, Inc. | System and method for generating effective layout constraints for a circuit design or the like |
| US20090150834A1 (en) * | 2007-12-11 | 2009-06-11 | Anil Bindu Lingambudi | Method of reusing constraints in pcb designs |
| CN103728552A (en) * | 2012-10-12 | 2014-04-16 | 苏州捷泰科信息技术有限公司 | Chip pin connection relation detection method and system |
| WO2014111969A1 (en) * | 2013-01-16 | 2014-07-24 | 株式会社図研 | Design method, program, memory medium, and designing device |
| CN109857451A (en) * | 2019-02-13 | 2019-06-07 | 广东高云半导体科技股份有限公司 | IP kernel document generating method, device, equipment and medium |
| CN114239459A (en) * | 2022-02-23 | 2022-03-25 | 苏州浪潮智能科技有限公司 | Processing method, device, equipment and medium for FPGA prototype design file |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6536017B1 (en) * | 2001-05-24 | 2003-03-18 | Xilinx, Inc. | System and method for translating a report file of one logic device to a constraints file of another logic device |
| CN109299503B (en) * | 2018-08-14 | 2023-02-17 | 珠海一微半导体股份有限公司 | LEF file generation method based on wiring blockage |
| CN110069892B (en) * | 2019-05-08 | 2023-07-25 | 山东浪潮科学研究院有限公司 | FPGA pin allocation design method and device |
| CN115544950A (en) * | 2022-09-21 | 2022-12-30 | 深圳市紫光同创电子有限公司 | Constraint file importing method, device, equipment and storage medium |
-
2022
- 2022-09-21 CN CN202211151714.3A patent/CN115544950A/en active Pending
-
2023
- 2023-08-24 WO PCT/CN2023/114682 patent/WO2024060926A1/en unknown
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6058252A (en) * | 1995-01-19 | 2000-05-02 | Synopsys, Inc. | System and method for generating effective layout constraints for a circuit design or the like |
| US20090150834A1 (en) * | 2007-12-11 | 2009-06-11 | Anil Bindu Lingambudi | Method of reusing constraints in pcb designs |
| CN103728552A (en) * | 2012-10-12 | 2014-04-16 | 苏州捷泰科信息技术有限公司 | Chip pin connection relation detection method and system |
| WO2014111969A1 (en) * | 2013-01-16 | 2014-07-24 | 株式会社図研 | Design method, program, memory medium, and designing device |
| CN109857451A (en) * | 2019-02-13 | 2019-06-07 | 广东高云半导体科技股份有限公司 | IP kernel document generating method, device, equipment and medium |
| CN114239459A (en) * | 2022-02-23 | 2022-03-25 | 苏州浪潮智能科技有限公司 | Processing method, device, equipment and medium for FPGA prototype design file |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024060926A1 (en) * | 2022-09-21 | 2024-03-28 | 深圳市紫光同创电子有限公司 | Constraint file import method and apparatus, device, and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024060926A1 (en) | 2024-03-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109002510B (en) | Dialogue processing method, device, equipment and medium | |
| CN108319575B (en) | Page component checking method, device, server and storage medium | |
| CN109408375B (en) | Method and device for generating interface document | |
| CN110321154B (en) | Micro-service interface information display method and device and electronic equipment | |
| CN113900958A (en) | Test case script generation method, system, medium and electronic device | |
| CN109558525B (en) | Test data set generation method, device, equipment and storage medium | |
| CN111694561A (en) | Interface management method, device, equipment and storage medium | |
| CN113467868B (en) | Method and device for creating equipment resources | |
| CN111538659B (en) | Interface testing method, system, electronic equipment and storage medium of business scene | |
| CN111666201A (en) | Regression testing method, device, medium and electronic equipment | |
| CN110688111A (en) | Configuration method, device, server and storage medium of business process | |
| CN114090671A (en) | Data import method and device, electronic equipment and storage medium | |
| CN112395843A (en) | PHP code-based service processing method, device, equipment and medium | |
| CN107797996B (en) | Entry translation method and device | |
| WO2024060926A1 (en) | Constraint file import method and apparatus, device, and storage medium | |
| CN116360735A (en) | Form generation method, device, equipment and medium | |
| CN115599386A (en) | Code generation method, device, equipment and storage medium | |
| CN111427577A (en) | Code processing method and device and server | |
| CN113836014A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN113238739A (en) | Plug-in development and data acquisition method, device, electronic equipment and medium | |
| CN113419711A (en) | Page guiding method and device, electronic equipment and storage medium | |
| CN111061522B (en) | Method, device, equipment and storage medium for generating front-end card assembly based on back end | |
| CN115408009A (en) | Code file generation method, device, equipment and storage medium | |
| CN109254774A (en) | The management method and device of code in software development system | |
| CN113609014A (en) | Interface field checking method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |