JP3065707B2 - Design support system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

 [Object of the invention]

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a design support system for managing design data appearing in a design process in an integrated CAD system.

[0002]

2. Description of the Related Art In recent years, with the increase in scale of digital systems, various integrated CAD systems for improving design efficiency have been developed. In particular, recently, as a system that provides design support from the upper stage such as system design and function design, when hardware operation specifications expressed by software algorithms are input, the hardware configuration that realizes this algorithm is automatically CAD systems that generate target or semi-automatically have appeared. Normally, in these systems, the designer pays attention only to the processing algorithm that he or she wants to realize, without being conscious of the specific hardware configuration, and uses the same syntax as general-purpose programming to specify the hardware operation specifications. Can be described. The system inputs such a specification description and generates a hardware configuration according to the following procedure, for example. (1) Extract the order and parallelism of the operations included in the specification description and assign the operations to clock cycles (scheduling
ring). (2) Allocate operation units required to execute the operation (operation unit allocation). (3) Allocate a storage element necessary for storing the operation result (storage element allocation). (4) Sharing transfer paths that are not used at the same time as a bus (bus allocation). (5) Output the design result as a register transfer level description (RTL).

Heretofore, a method has been adopted in which a series of these processes are performed automatically without the intervention of a designer. However, in this method, there are many methods for allocating hardware resources such as arithmetic units, storage elements, buses, and the like from a hardware-independent level description, and a system that can automatically generate only one solution. Then, there is a problem that these designs cannot be trial and error.

[0004] As a method of solving such a problem, it is conceivable to allow a designer to intervene in the above-mentioned design process and to enable a design in accordance with the intention of the designer. Here, as a tool that enables the designer to intervene, for example, “interactive LSI functional logic design system Hermod” (VL
D88-25, The Institute of Electronics, Information and Communication Engineers, 1988) proposes a tool for displaying a design result on a drawing and a tool for correcting the design result while viewing the drawing.

In such an interactive design environment, not only the final design data but also the design data in the course of the process are stored, retrieved as needed, and the parameters are changed. It is frequently practiced to re-execute the above-mentioned CAD tools (1) to (5) or to make manual corrections to try various designs. therefore,
A mechanism that manages a large number of design data generated and stored is important. However, at present, such management is left to the designer such that the designer devises and saves the file name. In this, the number of data, the data
When the number of design stages (processes, states)
There is a problem that the burden on the designer becomes extremely large and the reliability is reduced. For example, it is difficult to determine the design stage of the stored design data. To check the stage of the design data, start the above-mentioned drawing display tool and check the status of all components, for example, schedule.
It is necessary to check whether the steps of the ring are allocated, whether the arithmetic units are allocated, and the storage elements are allocated. On the other hand, an operation error such as an attempt to allocate a storage element is likely to occur.

Further, in a system in which the data structure for storing design data in the course of the process is different in each process,
For example, as the input data of the storage element allocation tool (3), the output data of the arithmetic unit allocation tool (2) and the output data of the scheduling tool (1) are required. There are cases like this. In this case, the output data of (2) must be generated using the output data of (1) as an input. In other words, the data to be input to the tool
The data set must not only satisfy the condition that the data type (design stage) is correct, but also satisfy the condition that it is generated based on the same data. Therefore, when the number of tools and design data to be started in the design stage increases, there is a problem that the set of input data when starting the design support tool is likely to be erroneous. If the tool is started with an incorrect data set as input, the tool internally verifies that the input data set was generated based on the same data. However, there is a problem that the tool ends abnormally and the cause cannot be understood, or even if the tool ends normally, a completely incorrect design result is output, but the designer does not notice it.

[0007]

As described above, in the conventional design support system, the management of the design data generated in the design process is left to the designer.
When the number and types of data become enormous, the burden on the designer increases.
Also, which design data is from which design stage,
Since it is difficult to determine which design data is generated based on the same data, there is a problem that an operation mistake is likely to occur and a correct result is not output.

The present invention has been made in view of such circumstances, and an object of the present invention is to provide a design support system for automatically managing design data generated and stored in a design process. Is to do. [Configuration of the Invention]

[0009]

[0010]

A design support system according to the present invention is divided into a plurality of design stages using a plurality of design support tools for inputting at least one or more types of design data and generating new design data. A design data storage unit for storing design data generated by each design support tool, a design data type storage unit for storing the type of the design data, and input to each design support tool. A relational storage unit that stores in advance the types of design data that can be used, and a history storage unit that stores the history of execution of the design support tool together with the input design data and the generated design data. When a tool is specified, the type of design data that can be input to the design support tool is checked by the relation storage unit, and the design data belonging to this type is checked. By searching the data and searching the history storage unit to determine whether the design data is generated based on the same design data, a plurality of types of design data that can be input to the designated design support tool are obtained. A design support tool that requires the input of the design data is provided with a display unit that displays the data as a set of design data.

[0011]

[0012]

According to the present invention, when there are various types of data structures of design data, and some of the design support tools require input of a plurality of types of design data, the type of the design data is changed. After the design data type storage unit automatically stores the information on the type of design data required to execute each design support tool from the relation storage unit, the extracted design data is stored from the same design data. Since it is checked from the information in the history storage unit whether the data is generated, it is possible to display a plurality of sets of design data that can be input to the design support tool designated by the designer.

[0013]

An embodiment of the present invention will be described below with reference to the drawings. ○ Example 1

FIG. 1 is a block diagram showing the configuration of the design support system according to the first embodiment. The design data storage unit 1
The operation flow to be designed is shown in a directed graph form as shown in FIG. 3, and the allocated resources (arithmetic units, registers, etc.)
Alternatively, it is stored in the form of a table as shown in FIG. The designer can store design data to be stored here, and can retrieve data to be used in subsequent designs from here. The flowchart display unit 2 displays the directed graph in the design data storage unit 1 on a display as shown in FIG. The data path display section 3 displays a data path graph as shown in FIG. 7 on a display from the directed graph and the table in the design data storage section 1. The scheduling execution unit 4, the arithmetic unit allocation execution unit 5, and the storage element allocation execution unit 6
In each case, an execution step is assigned to an operation in the directed graph, an operation unit is assigned, and a register for holding the operation result is assigned. The RTL output unit 7 generates an operation specification description at the register transfer level from the design data at the stage when all the above allocations have been completed.

Each of the above parts provides design support.
The design stage of the design data in the design data storage unit 1 or the type of the design data shown in Table 1
The display as to whether it can be an input of a file is performed by each unit described below. The design status storage unit 8 stores the design data.
The design stage of the design data stored in the data storage unit 1 is stored for each design data in a 6-bit pattern as shown in FIG. The status setting unit 9 sets each bit of the design status storage unit 8 based on the execution status of the scheduling execution unit 4, the operation unit assignment execution unit 5, and the storage element assignment execution unit 6 according to the rule of FIG. set. The tool activation possibility determination unit 10 includes a design data storage unit 1
A tool (operation) that can be executed on the design data stored in the storage unit is determined based on the bit pattern of the design status storage unit 8 according to the algorithm shown in FIG. The display unit 11 outputs a message indicating which design stage the designated design data is based on the design status storage unit 8 on a display, and displays the possibility of tool activation. Based on the judgment unit 10, a list of tools (operations) that can be executed for the designated design data is displayed on the display. The instruction unit 12 selects and executes the above-mentioned tools using a keyboard or the like, and stores the design data storage unit 1.
Select the design data stored in.

[0016]

[Table 1]

Hereinafter, the operations of the above-described units and the respective drawings will be described in more detail. In the directed graph of FIG.
The node (represented by 0) represents an operation or input / output variable, and the edge (represented by-) represents the flow of data. The node has the following attributes: node id, operation type (in case of operation node),
Variable name or constant value (for variable or constant node),
It has a step (cycle) of executing an operation. 1 in FIG.
Numerals 5, 13, and 14 are variable nodes, and the others are operation nodes. Among the operation symbols, x indicates multiplication, + indicates addition, and-indicates subtraction.
The operation types I and O of the variable nodes indicate input and output data, respectively. The dashed line in FIG. 6, which is a display of FIG. 3 in the design data storage unit 1 on the display, indicates the division of the operation execution steps provided by the scheduling execution unit 4. Nodes 10 to 12 in FIG.
Is not assigned an execution step yet, so no dotted line is displayed. The tables shown in FIGS. 4 and 5 are generated by the arithmetic unit assignment execution unit 5 and the storage element assignment execution unit 6 after the scheduling execution unit 4 completes the processing. It shows the correspondence between the id and the hardware resource id assigned to it (in the case of a register, the operation node that outputs the operation result held by the register is made to correspond).

Now, consider the case where the design data storage unit 1 stores the directed graph of FIG. FIG. 12 shows a bit pattern in the design status storage unit 8 corresponding to the design data. The bit pattern for a directed graph for which no scheduling has been performed is al as shown in FIG.
The bit of bit number 0 in FIG. 12 is assigned to the status setting unit 9 when the scheduling execution unit 4 assigns an execution step to the node 6.
Is set to 1 (S91 in FIG. 9). However, it is assumed that scheduling is performed in order from a node having a small id.

Now, consider a case where a designer takes out the above design data and intends to proceed with the design. The designer instructs the design unit 12 to use this design data as a subsequent operation target. Then the tool activation possibility judgment unit
10 selects a set of executable tools based on the bit pattern of FIG. 12 according to the algorithm of FIG.
As a result, option C102 in FIG. 10 is selected, and the tool ids that can be activated among the tools in Table 1 are {1, 2, 3}.
Then, the display unit 11 outputs a message of the design stage of the design data as shown in FIG. 13 and displays a list of tools selected by the tool activation possibility determination unit 9 as a tool. Based on Table 1 showing the IDs, they are displayed on a display in a menu format as shown in FIG. This allows the designer
It is easy to understand that the design data to be designed is the design data at a stage where the scheduling is not completed, and that the scheduling must be performed first. Next, the designer specifies
In FIG. 13, when the menu (2) automatic scheduling is selected, the scheduling execution unit 4 is activated, and when the scheduling is completed up to the node 12 in FIG. 9 sets the bit of bit number 1 of the design status storage unit 8 to 1 in accordance with the rule of FIG. 9, and the bit pattern becomes as shown in FIG.

Here, the designer further activates the operation unit assignment execution unit 5 and the storage element assignment execution unit 6 with respect to the above design data, and for example, the design data shown in FIGS.
It is assumed that the data is stored in the design data storage unit 1. The data in FIG. 15 is in a stage where the registers for storing the operation results of the nodes 6 and 9 have not been allocated yet, and the corresponding bipper pattern of the design status storage unit 8 is as shown in FIG. It has become. Now, it is assumed that the designer has instructed the design unit 12 to use this design data as a subsequent operation target. In the same manner as in the above case, the tool activation possibility determination unit 10 executes the executable tool ids {1, 5, 6, 6 based on the bit pattern of FIG. 16 and according to the algorithm of FIG.
7｝ is selected (C106). As a result, the display unit 11 displays a design stage of the design data and a menu of tools that can be started on the display as shown in FIG. next,
In order for the designer to know the design state of the data path,
In this case, if menu (2) data path display is selected, the data path display section 3 is activated, and a data path graph as shown in FIG. 7 is displayed on the display (FIG. 15).
In FIG. 7, registers for the outputs of the nodes 6 and 9 are not assigned, and therefore, in FIG. 7, registers are assigned to these outputs on a one-to-one basis.) As described above, the designer can easily grasp that the design data in this case is in a stage where the storage element assignment has not been completed, and can easily perform operations that can be performed on the design data. it can.

In the above-described embodiment, the tool activation determination unit 10 displays the design stage of the design data and the executable tools on the menu via the display unit 11. First, the designer instructs the design data to activate the execution units 4 to 6 in the instruction unit 12, and in response to this, the tool activation determination unit 10 sets the design status for the design data. Storage unit 8
And outputs the status of the design data as a message to the display unit 11 or outputs an error message to the display unit 11 if the tool activation condition is not satisfied. There is also a method.

In the above-described embodiment, the display unit 11 displays a menu of a list of tools that can be activated to indicate which CAD tool the design data can be input. May be displayed in a table format as shown in FIG. 18.

In the above embodiment, the bit of the bit pattern in the design status storage section 8 is not reset to 0 after it is once set to 1, but it is, for example, stored in the design data in the operation unit assignment process. On the other hand, if the process of canceling all the processing unit assignments performed so far and returning to the design data before the execution of the processing unit assignment occurs, it indicates that it is the processing unit assignment process. The bit of bit number 2 is also returned to 0.

As described above, according to the first embodiment, for the design data extracted by the designer, the design stage and a tool that can be started with the data as input can be displayed. It was made. ○ Example 2

FIG. 2 is a block diagram showing the configuration of the design support system according to the second embodiment. Design data storage unit 1, arithmetic unit assignment execution unit 5, storage element assignment execution unit 6, R
The function of the TL output unit 7 is the same as in the first embodiment.

In the first embodiment, the design data has the common structure of the directed graph of FIG. 3 and the table of FIG. 4 or 5 at any design stage. In the design support system, the data structure is different at each design stage. For example, there are data types as shown in Table 2.

[0027]

[Table 2]

For this reason, the tool relation storage unit 13 stores the types of the various design data stored in the design data storage unit 1 and the design support tools shown in Table 3. The input / output relationship is stored in a directed graph as shown in FIG. In FIG. 19, a rectangular node indicates a tool, and a circular node indicates a type of design data. For example, tool 2 (memory element allocation)
Is input with data of types 1 and 2, ie, a scheduled flowchart and an operation unit assignment table (FIG. 5A), and outputs data of type 3, ie, a storage element assignment table. (FIG. 5B) is output.

[0029]

[Table 3]

As shown in FIG. 20A, the system status storage unit 14 stores the history of the execution of the design support tool as the name of the design data stored in the design data storage unit 1. And the type are associated with each other and stored as shown in FIG. FIG. 20 (a)
The input data and output data in the table indicate the data names of the data input and output when the tool was actually executed. If the tool status is 1, the tool is currently executed. Indicates that it is inside. For example, in the first line, the tool 1 (assignment of the arithmetic unit) is FG1,
This is executed by using P1 as an input, and indicates that data FU1 has been generated.

The instructing unit 16 instructs execution of a tool and instructs the system status storage unit 6 to display data that can be an input of a certain tool, display a tool execution history, and the like. This is the part where inquiry is made by keyboard or the like. Display 17
Is a part for displaying the result of the inquiry by the instruction unit 16 on the display. Tool executable data detector 15
Detects a set of design data stored in the design data storage unit 1 which can be an input of the tool designated by the instruction unit 16 and transfers it to the display unit 17.

Now, let us consider a case where design data as shown in FIG. 20B is stored in the design data storage unit 1. That is, the scheduled flow graph FG as shown in FIG.
1, FG2, arithmetic unit assignment table FU as shown in FIG.
1, FU2, FU3, a storage element allocation table R1 as shown in FIG. 5 (b), and the number of available operation units and types of constraints P1, P2 when executing tool 1 (operation unit allocation).
Shall exist.

Now, let us consider a case where the designer inquires of the system in the instruction unit 16 as to what kind of data to be input to the tool 2 (storage element allocation). The tool executable data detection unit 15 determines a set of data that can be an input of a designated tool based on information in the system state storage unit 14 and the tool relation storage unit 13. Figure
Follow the steps in the 22 flowcharts. First,
In S1, the specified tool id, i = 2, is input. In S2, a tool node having a code i = 2 (rectangular node) is obtained from the tool input / output relation graph of FIG. ―
C) The number K = 2 of n5 and its input data nodes n1 and n4 (circular nodes) and their types i ₁ = 1 and i ₂ = 2 are obtained. S3～S51, S52 is, i _1, i ₂ de - Fig those meet other combinations in matching condition (must be generated from data for example, two de - - data is identical de)
This is the step of selecting using the 19 tool input / output relation graph. In S3, the common ancestor u of the data nodes x and y
Is a data node (circular node) that follows the graph from the nodes x and y in the input direction and merges first. However, if there is a path from x (y) to y (x),
Let x (y) be a common ancestor. In the case of FIG. 19, node n1
To n4, f = 1 is obtained as a common ancestor of i ₁ = 1 and i ₂ = 2. As a result, the determination in S4 becomes NO, and the process proceeds to S51. In S51, information in the system status storage unit 14 as shown in FIG. 20 is checked. That is, a set of design data of the type i ₁ = 1, i ₂ = 2,
The data generated from the design data of the type f = 1 (or the design data itself of the type f = 1) is obtained, and L
And From FIG. 20B, assuming that i ₁ = 1, FG1,
FG2 is considered, and from the history of FIG. 20A, the data of the type i ₂ = 2 generated from the data of f = 1 is FU1
(Generated from FG1), FU2, and FU3 (both generated from FG2), L = ｛(FG1, FU1), (FG2, FU2), (F
G2, FU3)｝ is obtained. Therefore, the determination in S53 is NO, and the determination in S6 is YES because K = 2, and in S7, L '= ｛(FG1, FU1), (FG2, FU2),
(FG2, FU3)}, which is a set of data that can be input to tool 2 (storage element allocation). The display unit 17 displays this result on a display, for example, as shown in FIG. 23 (S21).

S8 to S21 of the flowchart of FIG.
If the input of the tool i specified in 1 is 3 or more, the matching conditions not checked in the above S3 to S51 and S52 (for example, if the inputs 2 and 3 are not generated from the same data, This part is selected by using the tool input / output relation graph of FIG. In the following, an example that goes through these steps will be described.

This time, the designer operates the instruction section 16 to make a tool.
Let us consider a case where the system is inquired about what kind of data exists as input data of the file 3 (RTL output). I = 3 at S1 in the flowchart of FIG.
Is input, and in S2, K = 3, i ₁ = 1, i ₂ = 2, i ₃ = 3 from the tool input / output relationship graph of FIG. 19, and in S3, as in the case of the above example, f = 1, the process proceeds to S4 and S51, and L = ｛(FG1, FU1), (FG2, FU2), (F
G2, FU3)｝ is obtained. Next, the determination in S53 is NO, and the determination in S6 is
Since K = 3, the result is NO, the process proceeds to S8, and j = 3. S
9 and thereafter, L ′ is a value obtained by adding data of type _ij to each element (list) of L, and _ij and i ₁ to
This is a step of successively finding what satisfies the matching condition between _ij-1 (S15) and outputting the final result. S9
Then, since j ≦ K = 3, the process proceeds to S10, and a set L ′ of data sets obtained by adding data of the type i ₃ = 3 to the elements of L is obtained. Data of type i ₃ = 3 is obtained from R1 in FIG.
L ′ = ｛(FG1, FU1, R1), (FG2, FU
2, R1), (FG2, FU3, R1)}. Next, from the loops of S11 to S17, a list is selected that matches between the l and j-th data of each list of L '. In S11, 1 = 1, S12 becomes YES, and S13
In FIG. 19, referring to the tool input / output relation graph of FIG.
f = 1 is obtained as a common ancestor of _l = 1, i ₃ = 3,
Proceeding to S14 and S15, of the L's, the first and third data generated from the common data are obtained from the history shown in FIG. 20 (a), and L '= Ｆ (FG1, FU1, R1)}. 20 (a), R1 is generated from FG1, and (FG2, FU2, R1),
This is because (FG2, FU3, R1) is not matched between FG2 and R1. Here, since L '≠ φ, S16 becomes NO, and the process proceeds to S17, where l = 2 and L
Move to the second and third consistency check of each list of (S
12 or later). S12, YES, in S13, from the graph of FIG. _{19, i 2 = 2, i} 3 = 3 - as a common ancestor (Bruno corresponds to the de-n4, n6), obtain f = 2. Therefore, S
14 is NO and the process proceeds to S15. In S15, from the list of L, a list in which the second and third data are generated from the same type f = 2 is selected. Since R1 is generated from FU1 based on the history shown in FIG. 20A, L ′ = ｛(FG1, F
U1, R1)}, and after S16 and S17, 1 = 3
And The determination in S12 is NO, and the inner loop is eliminated. Next, through S20 and S21, j = 4,
The determination in S9 is NO, and the final result L '= {(FG1, FU1, R1)} is output. Then, the display unit 17 displays this result on the display as shown in FIG.

In S53 or S16 of FIG. 22, if the set of candidate data combinations becomes empty,
Since there is no data set that can be an input of the specified tool i, the display unit 17 displays a message as shown in FIG. 25 on the display via S19, and displays the tool. i
Notify the designer that is not yet ready to run.
Furthermore, the data including the missing data type can be displayed (lower part of FIG. 25).

The following functions may be added to the above embodiment. In the instruction unit 16, a system state storage unit
An instruction to display a table as shown in FIG. 20 stored in 14 and a graph in FIG. 19 stored in the tool relation storage unit 13 is also possible, and the display unit 17 displays these on a display or the like. . This allows the designer to determine what kind of design data currently exists, and if there is no data set that can be used as an input for a tool, what kind of data To know if there is a shortage of data. The display unit 17 always displays the contents of the system state storage unit 6, so that, for example, when the tools 1 and 2 are continuously executed, the designer can obtain the information shown in FIG. To
In the tool execution process, tool 1 has already been completed,
It is possible to grasp the state of the system at that time, such as the fact that the data FU3 has been generated. Furthermore, if the designer wants to execute multiple tools continuously and wants to stop the execution halfway, it is necessary to determine what data has been generated and what processing has been completed. You can know.

Alternatively, the display unit 17 displays, from the inter-tool relation storage unit 13, data types necessary for inputting the tool specified by the instruction unit 16 and matching conditions to be satisfied. It may be. For example, in the case of the above-described embodiment, when the tool 3 is designated by the instruction unit 16, the display unit 17 may display a message as shown in FIG. 26 on the display.

The instruction unit 16 not only specifies a tool but also, for example, “executable input data when executing tool 1 as one of the inputs of data FG1”. The display unit 17 may display a result by designating a tool and a part of the input data, such as “display a set”.

In the above-described embodiment, the display unit 17 displays data that can be used as an input of the tool specified by the instruction unit 16.
Although only a set of data is displayed, a table of a set of data that can be an input for each tool can be always displayed as shown in FIG. As a result, the designer was able to read "All the data necessary to execute a certain tool has been collected, even during the execution of the tool when a plurality of tools are executed continuously. And the like.

As described above, according to the second embodiment, when a plurality of design data are required to activate the tool because the data structure is different at each stage, the tool specified by the designer is used. Thus, a set of design data that can be input to the tool can be displayed. ○ Example 3

In this embodiment, when the data structure is common in each design stage as in the first embodiment, the second embodiment is applied.
Design data that can be input can be displayed for the tool specified by the designer.

The block diagram showing the configuration of the design support system according to the present embodiment is almost the same as that of FIG. 2, but the scheduling execution unit 4 of the first embodiment is also provided as a tool.
In this case, the information stored in the tool relation storage unit 13 is
The shape is as shown in FIG. 28 instead of 19. System status storage
14 holds information as shown in FIG. 29, which associates each design data name with a design stage. In order to associate each design data with the design stage, a bit pattern as shown in FIG. 8 reset by the function of the status setting unit 9 in the first embodiment may be used. The history information as shown in FIG. 20A of the second embodiment is not always necessary.

Here, the tool id specified by the designer is represented by i
(Tools are, for example, those shown in Table 3 with id = 0; scheduling is added). The tool executable data detection unit 15 determines that the design stage of the design data that can be the input of the tool i is i based on the information of FIG. 28, and refers to FIG. Then, the design data of the design stage i is searched for and output as design data that can be input to the designated tool. The display unit 17 displays the output result on a display or the like in accordance with the instruction from the instruction unit 16, and the designer selects one of the design data displayed in this way and activates the designated tool. be able to.

For example, although FU1 created by inputting FG1 to tool 1 already exists, the designer forgets this and designates tool 2 again, and inputs FG1 as input data. There is a case where the waste of selecting is caused. In order to prevent this, history information as shown in FIG. 20A is stored in the system state storage unit 14, and the tool designated by the designer and the input data selected as the input are
If the tool executed in the past matches the input data and the data created as a result of the execution remains, the message "Executed and created data" is displayed. The message may be displayed on the display unit 17. Alternatively, at the stage of displaying data that can be input to a specified tool, data that has already been input and executed to that tool may be displayed. ○ Example 4

In this embodiment, when the data structure is different at each design stage as in the second embodiment, the data extracted by the designer is used.
A tool that can be started with the data as input
And the design data to be input at the same time.

A block diagram showing the configuration of the design support system according to the present embodiment is the same as FIG. Designator 16
When the user designates that certain data is taken out, the type of the data is first checked with reference to FIG.
Then, FIG. 19 stored in the tool relation storage unit 13.
, Select a tool (there may be a plurality of tools) to which data of that type can be input. For each tool selected in this way, the tool executable data detection unit 15 performs the processing shown in the flowchart of FIG. 22 to obtain a set of inputtable data. . Select only those that contain the specified data from the set obtained,
When displaying, data to be input other than the designated data is displayed. The state of the display unit 17 at this time is shown in FIG. Based on this, the designer can select a tool to be activated for the specified data, and can input other necessary data without errors or omissions.

In the above-described first to fourth embodiments, a system is described in which an abstract specification description is input without considering the hardware configuration and register-transfer level design data is generated. Similar functions can be realized in a design support system that supports work. For example,
In a system that generates logic circuit data from a register transfer level specification description, for example, (1)
Generating technology-independent functional circuit data (2)
Since the design stages such as generating technology-independent AND / OR circuit data and (3) generating technology-dependent circuit data, the design support tools (1) to (3) are executed. Then, the same processing as in the first to fourth embodiments can be performed on the design data generated there. That is, it can be applied to a general integrated CAD system that goes through a plurality of design stages.

[0049]

As described above, according to the present invention, even when a large number of design data of various design stages generated in the design process using the design support tool are stored, the data is once stored. When trying to retrieve and use the stored design data again, it is necessary to know which design process has passed through this design data, and to complete the design process, Further, the designer can be easily informed which design support tool needs to be executed or which design support tool can receive the design data. In addition, information on which design support tool is executable with respect to which combination of design data, and data necessary to execute the design support tool to be used are available. To inform the designer immediately about what kind of design data is missing or what kind of design data is lacking. Further, when there are conditions such as that the data x and y must be generated from the same data z, correct design data necessary for executing the design support tool is provided. Is shown to the designer. Therefore, the burden on the designer of managing the design data is reduced, and the data of the incorrect combination is
There is a great effect in practical use, such as an operation error of starting a tool using a tool, generation of an erroneous design result due to the operation error, and a design support system that can prevent a malfunction of the system.

[Brief description of the drawings]

FIG. 1 is a schematic configuration diagram of a design support system according to a first embodiment.

FIG. 2 is a schematic configuration diagram of a design support system according to a second embodiment.

FIG. 3 is a diagram showing an example of a directed graph representing an operation flow of a design target, which is stored in a design data storage unit 1;

FIG. 4 is a diagram showing an example of the contents of a design data storage unit 1 that stores resources allocated to nodes in a directed graph.

FIG. 5 is a diagram showing an example of the contents of a design data storage unit 1 that stores (a) an arithmetic unit (b) and storage elements (registers) allocated to nodes in a directed graph.

FIG. 6 is a diagram showing an example of a directed graph displayed on a display unit 11;

FIG. 7 is a view showing an example of a data path graph displayed on a display unit 11;

FIG. 8 is a bit pattern for storing a design stage of design data.

FIG. 9 is a diagram showing an operation of a status setting unit 9;

FIG. 10 is a diagram showing an operation of a tool activation possibility determination unit 10;

FIG. 11 is a bit pattern for design data for which no scheduling has been performed.

12 is a bit pattern for the directed graph of FIG. 3 (data in the process of scheduling).

13 is a diagram showing an example of a message output to the display unit 11 when design data indicated by the directed graph of FIG. 3 is designated as a subsequent operation target.

FIG. 14 is a bit pattern for design data for which scheduling has been completed.

FIG. 15 is a diagram showing an example of a directed graph of design data obtained by performing an operation on the design data shown in the directed graph of FIG. 3;

16 is a bit pattern for the directed graph of FIG. 15 (data in the process of allocating storage elements).

17 is a diagram showing an example of a message output to the display unit 11 when design data indicated by the directed graph in FIG. 15 is designated as a subsequent operation target.

18 is a diagram showing another example of a message output to the display unit 11 when design data indicated by the directed graph in FIG. 3 is designated as a subsequent operation target.

FIG. 19 is a diagram showing an input / output relationship between a type of design data and a design support tool.

FIG. 20 is a diagram showing contents stored in a system state storage unit 14; (A) The figure which shows an example of the log | history which the design support tool performed. (B) A diagram in which design data names are classified by type.

FIG. 21 is a diagram showing an example of a scheduled directed graph.

FIG. 22 is a diagram illustrating an operation of a tool executable data detection unit 15;

FIG. 23 is a diagram showing an example of a message output to the display unit 17 when inquiring of data to be input to tool 2 (storage element assignment).

FIG. 24: Data to be input to tool 3 (RTL output)
Message output to the display unit 17 when an inquiry is made
FIG.

FIG. 25 is a diagram showing an example of a message output to the display unit 17 when data to be a tool input does not exist (is insufficient).

FIG. 26 shows data to be input to tool 3 (RTL output).
Message output to the display unit 17 when an inquiry is made
The figure which shows another example of a dice.

FIG. 27 is a diagram showing an example of a message when a table of a set of data that can be an input of each tool is always displayed.

FIG. 28 is a view showing the input / output relationship between the type of design data and the design support tool when the data structure is common in each design stage.

FIG. 29 is a diagram in which design data names, which are storage contents of the system state storage unit 14 according to the third embodiment, are classified for each design stage.

FIG. 30: When the data structure is different at each design stage,
FIG. 9 is a diagram showing an example of a message output to the display unit 17 when design data is instructed as a subsequent operation target.

[Explanation of symbols]

 Reference Signs List 1 Design data storage unit 2 Flow graph display unit 3 Data path display unit 4 Scheduling execution unit 5 Computing unit allocation execution unit 6 Storage element allocation execution unit 7 RTL output unit 8 Design status storage unit 9 Status ―Status setting section 10 Tool activation possibility judgment section 11 Display section 12 Indicator section 13 Tool relation storage section 14 System status storage section 15 Tool executable data detection section 16 Indicator section 17 Display section

Claims (1)

(57) [Claims] 1. A design support means for performing a design work divided into a plurality of design stages, wherein at least one or more types of design data are input to generate a new type of design data. A plurality of design means corresponding to the work, design data storage means for storing design data generated by the design means, design data stored in the design data storage means and a type of the design data, A design data type storage means for storing, a relation storage means for storing in advance for each design means a type of design data which can be input to the design means, and a history of the execution of the design means. History storage means for storing together with design data inputted and design data generated by the design means, and the type of design data stored in the relation storage means On the condition that the type of the design data stored in the total data type storage means matches and that the data is generated based on the same design data determined from the history stored in the history storage means. Means for obtaining and displaying design data that can be input to designated design means as a set of design data for design means that require input of a plurality of types of design data. Characteristic design support system.