JP2002215701A - Eda library control method, edition number verifying method, and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily obtain a library of the newest edition, and easily execute investigation of the edition of an EDA library being used. SOLUTION: This method comprises a process 103 for selecting cells based on necessary functions and performance for a semiconductor integrated circuit to be developed for forming a cell list, and storing the name of the sort of an LSI as a file name, and a process 105 for obtaining a necessary library from an EDA library data base based on the names of the cells written in the cell list as conditions for searching. The EDA libraries of the newest edition for the cells used for development of the LSI can be totally and easily obtained from cell list data bases for respective sorts of LSI's.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to an EDA library management method and a version number verification method.

[0002]

2. Description of the Related Art In order to design a system LSI, various design automation tools (hereinafter referred to as EDA tools) or systems are required. The EDA tool is a program realized by a computer for designing an LSI.
In order to use the A tool, an EDA library in which functions of functional blocks and timing information are described is required.

[0003] One system LSI includes an inverter and two
In recent years, it is composed of blocks composed of standard logic cells such as input NAND and flip-flops, memory blocks such as SRAM and ROM, analog blocks such as A / D converters and D / A converters, and I / O blocks of input / output parts. In addition, I / O such as MCU core and DSP core
System LSIs are often designed using functional blocks called P (Intellectual Property) and VC (Virtual Component).

[0004] Such an EDA library is managed in a database for each tool of each cell. That is, E
As shown in the EDA library configuration diagram of FIG. 3, the DA library manages an EDA library of each tool such as simulation and layout for each cell. Therefore, when developing an LSI, the necessary tools EDA of the necessary cells are obtained from the EDA library database.
The library was selected and acquired. For example, a desired cell is narrowed down by a characteristic, a cell name, or the like, and a necessary tool alone or the E of all tools is narrowed down in the narrowed down cell.
I had a DA library. As described above, the EDA library of the necessary tool of the cell required for each LSI to be developed is acquired and managed.

[0005]

However, according to the conventional EDA library management method, the EDA library is acquired and managed for each tool in each cell for each LSI development environment. When it is changed, it is becoming difficult to always update the version number of the acquired EDA library to the latest version. For example, EDA of a logic simulation of a cell
Even if the library is updated, there is a problem that the EDA library of the logic simulation of the development environment is not updated.

Further, since it takes a lot of man-hours to check whether the version number of the EDA library managed in the development environment is the latest version, the version number cannot be checked, and the EDA library of the old version number is unaware. In some cases, there arises a problem that a failure occurs in the developed LSI by performing development using the.

SUMMARY OF THE INVENTION The present invention solves the above-mentioned conventional problems. An EDA library management method which makes it easy to obtain the latest version of a library and can easily check the version of an EDA library used. And to provide a version number verification method.

[0008]

In order to achieve this object, an EDA library management method according to claim 1 of the present invention creates a cell list listing cells used for developing a semiconductor integrated circuit device. Obtaining an EDA library of the cells listed in the cell list from an EDA library database;
Outputting the library as a development library for the semiconductor integrated circuit device.

In order to achieve this object, an EDA library management method according to a second aspect of the present invention provides the EDA library management method according to the first aspect in which the functions and performances required for the semiconductor integrated circuit device to be developed are also reduced. Then, the cell list is created by selecting a cell, and the file name of the cell list is used as the type name of the semiconductor integrated circuit device to be developed.

In order to achieve this object, an EDA library management method according to a third aspect of the present invention is the same as the EDA library management method according to the first aspect.
When reacquiring the A library, the cell list is created by extracting the cell names used in the EDA library of the semiconductor integrated circuit device under development.

In order to achieve this object, an EDA library version number verification method according to a fourth aspect of the present invention is to provide an EDA library database having the latest version corresponding to each cell of the EDA library used for development. And the ED of the cell used for the development
A step of comparing the description contents of the EDA library of the cells obtained from the A library and the EDA library database, and, if the comparison results match, the cell using the version number of the EDA library obtained from the EDA library database for development If the comparison result does not match the step of outputting as the version number of the EDA library of E,
If the comparison result matches the description of the old EDA library in the DA library database and the comparison result matches, it notifies that the EDA library used is not the latest version number, and if the comparison does not match the EDA library Notifying that the EDA library of the cell corresponding to the database does not exist.

In order to achieve this object, a method for verifying the version of an EDA library according to claim 5 of the present invention provides a method for verifying the latest version of the EDA library corresponding to each cell of the EDA library used for development. And the ED of the cell used for the development
A step of comparing the description contents of the EDA library of the cells obtained from the A library and the EDA library database, and, if the comparison results match, the cell using the version number of the EDA library obtained from the EDA library database for development If the comparison result does not match the step of outputting as the version number of the EDA library of E,
Outputting the EDA library of the latest version number of the corresponding cell when the comparison result does not match with the description content of the old EDA library in the DA library database.

In order to achieve this object, a method for verifying the version number of an EDA library according to claim 6 of the present invention uses an EDA library database which is the latest version corresponding to each cell of the EDA library used for development. And the ED of the cell used for the development
A step of comparing the description contents of the EDA library of the cell obtained from the A library and the EDA library database, and, if the comparison results match, the cell using the version number of the EDA library obtained from the EDA library database for development If the comparison result does not match the step of outputting as the version number of the EDA library of E,
Outputting the EDA library of the latest version of the corresponding cell when the comparison result matches with the description content of the old EDA library in the DA library database.

In order to achieve this object, an EDA library management method and a version verification method according to claim 7 of the present invention provide an EDA library management method according to claim 1 and an EDA according to claims 5 and 6. In the library version number verification method, in the EDA library management method and the version number verification method for managing an EDA library database on a network, the output of the EDA library for each cell is performed using a network file transfer protocol.

In order to achieve this object, an EDA library version number verification method according to claim 8 of the present invention is provided.
In the EDA library version number verification method according to the fifth and sixth aspects, the version number is notified using an electronic mail.

In order to achieve this object, the storage medium for the EDA library management method and the version number verification method according to the ninth aspect of the present invention is a computer-readable recording medium, A program for executing the EDA library management method or the EDA library version number verification method according to claim 2 or claim 3 or claim 4 or claim 5 or claim 6 or claim 7 or claim 8 is recorded.

As described above, it is possible to provide an EDA library management method and a verification method capable of easily acquiring the latest version of the library and easily checking the version of the used EDA library.

[0018]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below.
This will be described with reference to the drawings. (Embodiment 1) FIG. 1 shows a flowchart of an EDA library management method according to Embodiment 1 of the present invention.

First, the LSI product name 101 to be developed is
(102). Next, the cells used in the LSI to be developed are listed, and an LSI type cell list 104 as shown in the conceptual diagram of the LSI type cell list in FIG. 2 is created. At this time, the listed LSI type cell list 104 stores the LSI type name as a file name in the second temporary storage device (10).
3). Finally, an LSI using the LSI product name as the file name
A required EDA library is obtained from the EDA library database using the cell name written in the cell list 104 by type as a search condition (105), and is output as the development EDA library 106 of the LSI to be developed.

Next, the procedure for creating an LSI type-specific cell list will be described. When developing an LSI, create an LSI product type cell list of cells required for development, and
An EDA library of a required cell is acquired using the cell name written in the I-type-specific cell list. In the EDA library database, as shown in the EDA library configuration diagram of FIG. 3, an EDA library for a logic simulation tool and an ED for a logic synthesis tool are provided for one cell.
It has a plurality of EDA libraries such as the A library. L
At the time of SI development, EDA libraries of all or some of these tools are selected and acquired.

At this time, in order to manage the LSI type-specific cell list, the LSI type name may be used as the file name of the LSI type cell list. This will be described with reference to FIG. FIG. 4 shows an example of an LSI by selecting a cell to be used.
It is a flowchart which creates the cell list used in development.

First, a cell to be used is searched based on functions and performance required for an LSI to be developed (401), and a necessary cell is selected from the cell and written into an LSI type cell list (402). The name of the LSI type to be developed is input as the file name of the LSI type-specific cell list (403). At this time, it is checked whether the input LSI type name already exists in the LSI type cell list database (4.
04) If it does not exist, it is registered in the LSI type cell list database as a new LSI type cell list (405). If there is, it is checked whether or not all the cells required at this time already exist in the corresponding LSI type cell list (406), and if there is, the processing is terminated without registering in the LSI type cell list. (4
07) If it does not exist, it is registered as a new cell in the LSI type cell list (408).

A method for creating a cell list for each type using an EDA library for each LSI type already used for development will be described with reference to FIG. FIG. 5 is a flowchart for creating a cell list for each type using an EDA library for each LSI type.

First, a type-specific EDA library to be used is designated (501). Next, the specified type E
The LSI type name of the LSI using the DA library is input (502). EDA by type specified in 501
The library is read (503), and all cell names included in the read type-specific EDA library are extracted (504). Check if the LSI type name exists in the LSI type cell list database (50
5) If not, the LSI type-specific cell list extracted in 504 with the LSI type name as a file name is registered in the LSI type-specific cell list database (507). If the relevant LSI type name already exists, it is selected whether or not it is necessary to completely replace the cell list of the relevant LSI type in the database (506).
The corresponding LSI type cell list in the I type cell list database is replaced with the LSI type cell list extracted in 504 (508), and if no replacement is necessary, the process is terminated without any processing (509).

Here, it is naturally possible to directly create an LSI type-specific cell list without using the above two methods. (Embodiment 2) Hereinafter, Embodiment 2 of the present invention will be described.
This will be described with reference to the drawings.

FIG. 6 shows an ED according to the second embodiment of the present invention.
It is a flowchart which shows the A library version number verification method. First, the EDA library (601) used for development is decomposed into cell units (602). Next, to assign a number to each of the decomposed cells and distinguish them from each other, 0 is first substituted into a variable serving as a counter (603), and 1 is sequentially added to the counter (604). The cells of the EDA library used for the development corresponding to the counter number
(605). The EDA library database is searched using the cell name as a search condition, and the EDA library of the corresponding cell is obtained (606). If it cannot be obtained (No in 607), the fact that the corresponding cell does not exist in the EDA library database is described in the version number verification result file as shown in C of the version number verification result file in FIG. 8 (621). If you can get (60
7 Yes), the obtained EDA library of the corresponding cell is stored in the second temporary storage area (608), and the description contents of the EDA library in the first and second temporary storage areas are compared (7). 609). If they match (61
0 Yes), the version number of the EDA library obtained from the EDA library database is described in the version number verification result file as shown in FIG. 8A (620). If they do not match (610 No), the EDA library database of the previous version is searched and the EDA of the corresponding cell is searched.
The library is acquired (611). If it cannot be acquired here (612 No), the ED is obtained as shown in FIG.
The fact that there is no corresponding version number in the A library is described in the version number verification result file (621). When the old EDA library of the corresponding cell can be obtained (612 Y
es) The EDA library obtained from the EDA library database is stored in the second temporary storage area (61).
3) ED of the first temporary storage area and the second temporary storage area
The description contents of the A library are compared (614). If they match (615 Yes), then E as shown in FIG.
The version number of the EDA library acquired from the DA library database is described in the version number verification result file with a note that the version number is not the latest version number (622). If they do not match (615), the steps 611 to 615 of searching the EDA library database of the previous version and acquiring the corresponding cell are repeated. This leads to the result of 621 or 622. Finally, a version number verification result file is output (62
4).

At this time, the EDA of the latest version number of a cell having a cell or a cell whose version number is not the latest version but whose matching version number is unknown is present.
It is also possible to output a library. FIG. 7 is a flow chart for outputting an EDA library of the latest version of a cell having a cell or a cell whose version number is not the latest version but whose matching version number is unknown.

The version number is verified, and a cell or a cell having a version number that is not the latest version exists but a cell whose matching version number is unknown is stored in a third temporary storage area (731). The EDA library database is searched using the cell name stored in the device as a search condition, and the latest version E of the corresponding cell is searched.
The DA library can be acquired (732), and the latest version of the EDA library can be output (733).

In this embodiment, a number is added by a counter to distinguish each cell, but the method of distinguishing each cell is arbitrary. In the first and second embodiments, as shown in the configuration diagram of the EDA library management using the network in FIG.
It can also be realized by accessing the DA library management system. Further, when outputting the EDA library in the first and second embodiments, the EDA library can be transmitted by ftp, and the verification result of the version number in the second embodiment can be transmitted by e-mail.

A computer readable program for executing the EDA library management method of the first embodiment or the EDA library version number verification method of the second embodiment is created, and this program is recorded on a recording medium. The EDA library management program of the present invention can be executed by a computer as shown in the block diagram of the computer.

By searching for cells used for development using the LSI type cell list by the above method, the LSI type cell list database
An EDA library of the latest version of a cell used for SI development can be easily and collectively acquired.

The EDA library used in the LSI development is compared with the EDA library registered in the EDA library database by managing the version number in the EDA library database, and the version of the EDA library used in the LSI development is compared. The number can be easily checked.

[0033]

As described above, by searching the cells used for development using the cell list for each LSI type, the latest version number of the cells used for the development of the LSI can be obtained from the cell list database for each LSI type. The EDA library can be easily and collectively acquired.

The EDA library used in the LSI development is compared with the EDA library registered in the EDA library database by managing the version number in the EDA library database, and the version of the EDA library used in the LSI development is compared. The number can be easily checked.

[Brief description of the drawings]

FIG. 1 is a flowchart of an EDA library management method according to a first embodiment of the present invention.

FIG. 2 is a conceptual diagram of an LSI type-specific cell list.

FIG. 3 is a configuration diagram of an EDA library.

FIG. 4 is a flowchart for creating a cell list used in LSI development by selecting a cell to be used;

FIG. 5 is a flowchart for creating a cell list for each type using an EDA library for each LSI type;

FIG. 6 is a flowchart showing an EDA library version number verification method according to the second embodiment of the present invention.

FIG. 7 is a flowchart of outputting an EDA library of the latest version of a cell whose cell or cell having a non-latest version exists but whose matching version number is unknown.

FIG. 8 is a version number verification result file.

FIG. 9 is a configuration diagram of EDA library management using a network.

FIG. 10 is a configuration diagram of a computer device that executes an EDA library management program.

[Explanation of symbols]

 101 LSI product name 104 LSI product type cell list 106 LSI development library 601 EDA library used for development 701 EDA library used for development

Claims (9)

[Claims] 1. A step of creating a cell list listing cells used in the development of a semiconductor integrated circuit device; a step of acquiring an EDA library of cells listed in the cell list from an EDA library database; Outputting the EDA library as a development library for a semiconductor integrated circuit device. 2. A cell list is created by selecting cells based on functions and performance required for a semiconductor integrated circuit device to be developed, and a file name of the cell list and a product name of the semiconductor integrated circuit device to be developed. 2. The EDA library management method according to claim 1, wherein: 3. An EDA of a semiconductor integrated circuit device whose cell list is under development when reacquiring an EDA library during development.
2. The EDA library management method according to claim 1, wherein a cell name used in the library is extracted and created. 4. A step of obtaining, from an EDA library database, the latest version of an EDA library corresponding to each cell of the EDA library used for development, and an EDA library of the cell used for development and the EDA library database. ED of cell obtained from
Comparing the description contents of the A library; and, if the comparison results match, outputting the version number of the EDA library obtained from the EDA library database as the version number of the EDA library of the cell used for development. If the comparison result does not match, it is compared with the description of the old EDA library in the EDA library database, and if the comparison result matches, it is notified that the EDA library used is not the latest version, and the comparison is performed. Notifying that the EDA library of the corresponding cell does not exist in the EDA library database when the IDs do not match. 5. A step of obtaining, from an EDA library database, the latest version of an EDA library corresponding to each cell of an EDA library used for development; and an EDA library of the cells used for development and the EDA library database. ED of cell obtained from
Comparing the description contents of the A library; and, if the comparison results match, outputting the version number of the EDA library obtained from the EDA library database as the version number of the EDA library of the cell used for development. If the comparison result does not match, the EDA library is compared with the description content of the old EDA library in the EDA library database, and if the comparison result does not match, the step of outputting the EDA library of the latest version of the corresponding cell is performed. E to have
DA library version verification method. 6. A step of obtaining, from an EDA library database, the latest version of an EDA library corresponding to each cell of the EDA library used for development, and an EDA library of the cell used for development and the EDA library database. ED of cell obtained from
Comparing the description contents of the A library; and, if the comparison results match, outputting the version number of the EDA library obtained from the EDA library database as the version number of the EDA library of the cell used for development. Outputting the EDA library of the latest version number of the corresponding cell when the comparison result does not match, comparing with the description content of the old EDA library in the EDA library database when the comparison result matches. Library version verification method. 7. An EDA library management method and a version number verification method for managing an EDA library database on a network, wherein the output of the EDA library for each cell is performed using a network file transfer protocol. A library management method and the EDA library version number verification method according to claim 5 or 6. 8. The EDA library version number verification method according to claim 4, wherein the EDA library version number is notified by e-mail. 9. A recording medium which can be read by a computer, wherein the recording medium is a computer readable recording medium, wherein the computer readable recording medium is a computer readable recording medium.
9. A recording medium storing a program for executing the EDA library management method or the EDA library version number verification method according to claim 8.