# Patent

## Title
Method and apparatus for designing systems using logic regions

## Abstract

A method for positioning components of a system onto a target device utilizing programmable logic devices (PLDs) is disclosed. A first location on the target device for a first logic region having a first component is determined. Determined properties of the first logic region are preserved. The first logic region is integrated with a second logic region having a second component in view of the determined properties.

## Background
FIELD OF THE INVENTION
The present invention relates to the field of programmable logic devices (PLDs). More specifically, the present invention relates to a method and apparatus for the placement of components onto PLDs and the designing of systems using logic regions.
BACKGROUND
To handle the complexity of designing large systems, the design task is often broken up into more manageable parts. Designers commonly use approaches such as modular, hierarchical, and incremental design, and require tools that support these approaches. Electronic design automation (EDA) tools are examples of some of the tools used to manage and optimize design and placement of large systems onto physical target devices. Of the tasks required in managing and optimizing design and placement, satisfying timing constraints of a system is often the most important and the most challenging. In order to satisfy timing constraints, many iterations are often required to determine how components in logic blocks are to be grouped and where these logic blocks are placed on the target device.
Automated placement algorithms in EDA tools perform the time-consuming task of manually mapping logic blocks to physical locations on their target device. However, even state of the art automated algorithms are sometimes incapable of producing solutions that are comparable to user defined manual placement. User defined manual placement techniques are often able to identify critical sections of logic that should be grouped together in order to meet timing constraints that automated algorithms are slow to or even sometimes unable to identify. In addition, many of the state of the art EDA tools utilize a design process that involves the design of modules that make up logic blocks and the integration of the modules into a system before optimizing the system. Systems using this design process may fail to meet performance requirements despite having individual modules that meet the performance requirements before integration. Furthermore, changes made to one module may affect the performance of other modules. Re-optimizing modules to meet system performance requirements often requires additional design iterations which is undesirable.
Thus, what is needed is an improved method and apparatus for design and placement of components on PLDs. This improved method and apparatus should utilize the positive attributes of manual user placement and automated placement of components on PLDs.
SUMMARY
A method and apparatus for placement of components of a system onto programmable logic devices (PLDs) is disclosed according to an embodiment of the present invention. The method and apparatus bridges the gap between manual user placement and automated placement of components on PLDs. A user is given the capability to define logic regions that group certain components of the system together. The components may be for example, digital logic, memory devices, or other components. The user may specify a size of a logic region. The user may also specify a location for the logic region. Sizes and/or locations are determined for logic regions having no specified sizes and/or locations. The determined sizes and/or locations allow the system to meet timing constraints. According to an embodiment of the present invention, a user may create logic regions having a hierarchy of arbitrary depth.
A method and apparatus for designing systems using logic regions is disclosed according to an embodiment of the present invention. The method and apparatus may utilize logic regions to optimize designs in order to meet system requirements such as timing constraints. The preservation of determined properties of the logic regions such as sizes of the logic regions, locations of the logic regions on a target device, and/or locations of the components on logic regions allows the logic regions and the performance characteristics of the logic regions to be used in subsequent designs. The preservation of determined properties of the logic regions for use in subsequent design facilitates efficient modular, hierarchical, incremental, and team-based design flow approaches.



BRIEF DESCRIPTION OF THE DRAWINGS
The features and advantages of the present invention are illustrated by way of example and are by no means intended to limit the scope of the present invention to the particular embodiments shown, and in which:
FIG. 1 illustrates a target device utilizing programmable logic devices (PLDs) according to an embodiment of the present invention;
FIG. 2 is a table that illustrates relative delays for each hierarchy level of the target device shown in FIG. 1 according to an embodiment of the present invention;
FIG. 3 illustrates the sizing of a logic region that includes predominantly logic circuits according to an embodiment of the present invention;
FIG. 4 illustrates the sizing of a logic region that includes predominantly memory circuitry according to an embodiment of the present invention;
FIG. 5 illustrates an example of a fixed parent logic region constraining the sizing of a child logic region according to an embodiment of the present invention;
FIG. 6 illustrates an example of a fixed child logic region constraining the sizing of a parent logic region according to an embodiment of the present invention;
FIG. 7 is a flow chart that illustrates a method for sizing logic regions according to an embodiment of the present invention;
FIG. 8 illustrates a graphical depiction of the restrictions on logic region mobility according to an embodiment of the present invention;
FIG. 9 illustrates graphical depictions of logic region extensions according to an embodiment of the present invention;
FIG. 10 illustrates a graphical depiction of bumping logic regions according to an embodiment of the present invention;
FIG. 11 illustrates a graphical depiction of a critical vector move according to an embodiment of the present invention;
FIG. 12 is a flow chart that illustrates a method for placing logic regions on a target device according to an embodiment of the present invention;
FIG. 13 is a flow chart illustrating a method for designing a target device, utilizing PLDs, for a system according to an embodiment of the present invention;
FIG. 14 is a flow chart illustrating a method for designing a target device utilizing preserved properties of previously designed logic regions;
FIG. 15 illustrates an exemplary modular design flow according to an embodiment of the present invention;
FIG. 16 illustrates an exemplary hierarchical design flow according to an embodiment of the present invention;
FIG. 17 illustrates an exemplary incremental design flow according to an embodiment of the present invention; and
FIG. 18 illustrates an exemplary team-based design flow according to an embodiment of the present invention.



DETAILED DESCRIPTION
According to an embodiment of the present invention, a user (designer) may define logic regions that group certain components of a system together. The components may be for example, digital logic, memory devices, or other components. The sizes of the logic regions may be determined by the user or by a sizing method. The placement of the logic regions may be determined by the user or by a placement method. FIG. 1 illustrates a target device 100 utilizing programmable logic devices (PLDs) according to an embodiment of the present invention. According to one embodiment, the target device 100 is a chip having a hierarchical structure that may take advantage of wiring locality properties of circuits formed therein. The lowest level of the hierarchy is a logic element (LE) (not shown). According to one embodiment of the target device 100, the LE may include a 4-input lookup table with a configurable flip-flop. Groups of 10 LEs form a logic-array block (LAB). A first group of LABs is shown as 110. LEs in a LAB are able to communicate with other LEs via LAB local interconnect lines (not shown).
Groups of 16 LABs and 1 embedded system block (ESB) 111 form a MegaLab. A first MegaLab is shown as 120. ESBs may be used to implement memory circuitry such as random access memories (RAMs), read only memories (ROMs), content addressable memories (CAMs), and other types of memory circuitry. Each LAB in a MegaLab is able to communicate with its adjacent neighboring LABs via the LAB local interconnect lines. Alternatively, communication may be sent via a MegaLab interconnect (not shown), which includes a set of continuous metal lines that span the width of the MegaLab. LEs within any LAB can directly drive the MegaLab interconnect. The signal then traverses the metal line to a local input line associated with the destination LAB, and then to any dependent LE.
Groups of 13 MegaLabs form an Octant. A first Octant is shown as 130. Each MegaLab in an Octant is able to communicate with other MegaLabs via a series of continuous vertical interconnect lines (V-lines) (not shown). Signals communicating across an Octant start from a source LE that directly drives a V-line. The signals traverse to the target MegaLab, switch onto the MegaLab interconnect, and make their way to the destination LE.
Two Octants are stacked vertically to form a Column. A first Column is shown as 140. Communication between Octants is made possible by a buffered switch (not shown) that connects the V-lines between two Octants together.
Groups of two Columns form a Half. A first Half is shown as 150 and a second Half is shown as 151. Continuous horizontal interconnect lines (H-lines) run across the width of the two Columns. Signals that traverse across the Half start at the source LE which can directly drive the H-line. From the H-line, the signal can drive an appropriate V-line in the target Octant and traverse its way to the destination LEs using the intra-Octant communication scheme. Two Halves are grouped side by side to form a Chip. The two Halves are connected to the buffered switch which may be used for communication between Halves.
Each level of the hierarchy described has delay characteristics. As communication is transmitted out of each level of hierarchy, a delay is incurred. FIG. 2 illustrates relative point-to point delays incurred at different points in the target device according to an embodiment of the present invention. As shown, as communication is transmitted to a next higher level of hierarchy, a larger delay is incurred. FIG. 1 illustrates an exemplary embodiment of a target device. It should be appreciated that the target device may include a plurality of Chips, such as target device 100 cascaded together. The target device may include programmable logic devices arranged in a manner different than that on the target device 100. The target device may also include components other than those described in reference to the target device 100.
According to an embodiment of the present invention, the user may assign a size to each logic region defined. Alternatively, the user may designate a logic region to be automatically sized. When a logic region is automatically sized, the size and shape of the logic region are determined by a sizing method according to an embodiment of the present invention. The method assumes that the logic region is to be sized such that it runs as efficiently as possible. According to an embodiment of the sizing method, a shape is found that will fit the components assigned to the logic region.
According to an embodiment of the sizing method where sizing is performed on a logic region with predominantly logic circuits, the following technique may be used. The term nLE represents a number of LEs assigned to a logic region to be automatically sized.
Let ALAB represent the number of LEs in a LAB. According to the embodiment of the target device shown in FIG. 1, ALAB equals 10.
Let AMLAB represent the number of LEs in a MegaLab. According to the embodiment of the target device shown in FIG. 1, AMLAB equals 160.
Let AOCT represent the number of LEs in an Octant. According to the embodiment of the target device shown in FIG. 1, AOCT equals 2,080.
Let ACOL represent the number of LEs in a Column. According to the embodiment of the target device shown in FIG. 1, ACOL equals 4,160.
Let AHALF represent the number of LEs in a Half. According to the embodiment of the target device shown in FIG. 1, AHALF equals 8,320.
Let ACHIP represent the number of LEs in a Chip. According to the embodiment of the target device shown in FIG. 1, ACHIP equals 16,640.
With reference to FIG. 3, the following process may be taken to determine a size and shape of a logic region. If nLE≦ALAB, then the size of the logic region equals 1 LAB. The arrow corresponding to reference number 301 illustrates the direction the logic region would extend to if the preceding condition were true.
If nLE≦AMLAB, then the size of the logic region equals [nLE/ALAB] horizontal LABs. The arrow corresponding to reference number 302 illustrates the direction the logic region would extend to if the preceding condition were true. According to an embodiment of the present invention, the size calculation is rounded up to a whole number.
If nLE≦AOCT, then the size of the logic region equals [nLE/AMLAB] vertical MegaLabs. The arrow corresponding to reference number 303 illustrates the direction the logic region would extend to if the preceding condition were true.
If nLE≦ACOL, then the size of the logic region equals [nLE/AMLAB] vertical MegaLabs. The arrow corresponding to the reference number 304 illustrates the direction the logic region would extend to if the preceding condition were true.
If nLE≦AHALF, then the size of the logic region equals 2 horizontal MegaLabs by [nLE/(2*AMLAB)] vertical MegaLabs. The arrow corresponding to the reference number 305 illustrates the direction the logic region would extend to if the preceding condition were true.
If nLE≦AHALF+ACOL, then the size of the logic region equals 3 horizontal MegaLabs by [nLE(3*AMLAB)] vertical MegaLabs. The arrow corresponding to reference number 306 illustrates the direction the logic region would extend to if the preceding condition were true.
If nLE≦ACHIP, then the size of the logic region equals 4 horizontal MegaLabs by [nLE/(4*AMLAB)] vertical MegaLabs. The arrow corresponding to reference number 307 illustrates the direction the logic region would extend to if the preceding condition were true.
According to an embodiment of the sizing method where sizing is performed on a logic region with primarily memory components, the following technique may be used. This is illustrated with reference to FIG. 4. As shown, the ESBs typically reside in a column. A size and shape of a logic region is created such that it includes a sufficient number of ESBs required for implementing the memory components. The arrow corresponding to reference number 408 illustrates the direction the logic region would extend to as more ESBs were required. The region is then extended to include just enough LAB columns to satisfy the requirement of the memory components. The arrow corresponding to reference number 409 illustrates the direction the logic region would extend to as more LEs were required.
In the event that a user has created hierarchies that include combinations of fixed-sized and automatically sized region, the sizing method of the present invention would take into account these new constraints. FIG. 5 illustrates an example of a parent logic region 510 that constrains the size of a child logic region. The parent logic region 510 has a fixed size determined by the user. The child logic region is to be automatically sized. If the child logic region includes primarily logic circuits, it would typically be sized to occupy a single Octant. However, an Octant sized child logic region would fall outside the parent logic region 510. Thus, the preferred dimension of the child logic region is reshaped such that it fits within its parent and is shown as 520.
Similarly, FIG. 6 illustrates an example of child logic regions 610 and 620 that constrain the size of a parent logic region. The child logic regions 610 and 620 have fixed sizes determined by the user. The parent logic region is to be automatically sized. If the parent logic region includes primarily logic circuits, it would typically be sized to occupy a subset of a Column. However, the sizing constraints for the child logic regions 610 and 620 would make this assignment illegal. The preferred dimension of the parent logic region is reshaped to comply with the fixed dimensions of the child logic regions 610 and 620 and is shown as 630.
According to an embodiment of the present invention, the user may also assign a size to a defined logic region and mark the region as a “soft region”. By marking the logic region as a soft region, a preference will be given to having the logic region confined within the assigned size. However, if after determining the placement of other logic regions in the system it is discovered that the logic region marked as a soft region cannot be confined within the assigned size or that by confining the logic region to the assigned size other requirements in the system cannot be met, components assigned to the logic region are permitted to be positioned outside the boundaries of the logic region. According to one embodiment, the sizing may be achieved by using the sizing method described.
FIG. 7 illustrates a method for sizing logic regions according to an embodiment of the present invention. At step 701, the logic regions are sorted in reverse topological order such that child regions are ordered before the parent logic regions.
At step 702, an initial size is determined for the logic region based on the LE and ESB required for components on the logic region.
At step 703, constraints of any child logic region of the logic region are determined.
At step 704, constraints of any parent logic region of the logic region are determined.
At step 705, the initial size of the logic region may be reshaped in response to the constraints of any child and/or parent logic region of the logic region. It should be appreciated that reshaping may not be required if no constraints exist or if the constraints do not affect the initial size of the logic region.
At step 706, it is determined whether a next logic region is to be evaluated. If a next logic region is to be evaluated, control proceeds to step 702. If a next logic region is not to be evaluated, control proceeds to step 707.
At step 707, extra spaces on the target device are distributed to the logic regions evaluated.
According to an embodiment of the present invention, the user may assign a location on the target device to each logic region defined. Alternatively, the user may designate a logic region to “float” or be automatically placed. For a logic region that is to be automatically placed, the location of placement of the logic region is determined by a placement method according to an embodiment of the present invention. The method finds initial feasible locations for the logic regions that serve as a starting solution that will be iteratively optimized. In an unconstrained design flow, the initial placement may simply scatter the logic regions across the target device. According to an embodiment of the placement method, the initial placement is feasible with respect to any constraints imposed by the architecture. For example, in the target device 100 shown in FIG. 1, the placement of ESBs are only legal in certain columns of the target device 100. It should be appreciated that the initial placement of the logic regions may be determined using other methods or techniques.
After the initial placement, the logic regions are moved to different locations on the target device. The placement method operates in accordance with a plurality of guidelines. A first guideline, according to an embodiment of the placement method, is that logic regions may not overlap each other. The constrained motion imposed by the first guideline prevents the undesirable consequence of having logic regions share LEs. Although steps may be taken to perturb logic regions to ensure an overlap free solution at the end of the placement process, such moves at the end of the placement process could have an undesirable effect on inter and intra logic region timing constraints. According to an embodiment of the present invention, floating regions may overlap under certain conditions.
According to an embodiment of the present invention, a region on the target device may be marked as “reserved”. The reserved region may be used, for example, for the placement of a designated component. According to an embodiment of the placement method, the first guideline not only prohibits the overlapping of logic regions, but also prohibits the placement of a logic region or any component not assigned a logic region onto a reserved region on the target device. It should be appreciated that a logic region itself may be marked as reserved in order to prevent components other than those assigned to the logic region to be placed in the logic region.
A second guideline, according to an embodiment of the placement method, is that if a region is created within a physical Column of the target device, the logic region will not be moved to span outside a single Column of the target device. FIG. 8 illustrates the possible locations that a logic region 800 may be moved to. The origin of the logic region 800, defined by its lower left corner, may be moved from a first position denoted by 801 to a plurality of positions denoted by 802–816. The constrained motion imposed by the second guideline provides the system with better predictability that the timing requirements within a logic region will be satisfied.
A third guideline, according to an embodiment of the placement method, is that a location of an extended region of a first logic region may be interchanged with a location of a second logic region given that both encapsulate all logic regions that they touch. Furthermore, both locations must be within the parent logic region of the first logic region. FIG. 9 illustrates the applicability of the third guideline. The move denoted by Swap 1 attempts to move the logic region 901 to a location occupied by 902. Notice that the locations of logic regions 901 and 902 cannot be swapped because they have different sizes. To make this move, the location of logic region 901 is extended outwards until it is the same size of logic region 902 as shown by dotted region 910. This extension also encapsulates the logic region 902 as shown by dotted region 920. The location of the extended region of the logic region 901, which also includes logic region 903, may now be swapped with the location of the logic region 902. The extension procedure of the third guideline is not always possible, however, as shown by the move denoted Swap 2. This swap attempts to move logic region 904 to the location occupied by 902. If the location of logic region 904 was extended to the size of 902 as shown by dotted region 930, it would intersect only a portion of the logic region 905.
A fourth guideline, according to an embodiment of the placement method, is that a plurality of logic regions may be moved or “bumped” in order for another logic region to be moved onto their location. FIG. 10 illustrates the applicability of the fourth guideline according to an embodiment of the present invention. The logic region 1001 attempts to move to the location shared by logic regions 1002 and 1003. The fact that logic regions 1002 and 1003 block a potential move is “remembered” by the placement method. A next time a move for logic regions 1002 and 1003 is selected, the logic regions 1002 and 1003 would be biased outwards to allow the move of 1001.
A fifth guideline, according to an embodiment of the placement method, is that a logic region is moved in the direction of the sum of all incoming and outgoing critical connections to other logic regions. FIG. 11 illustrates the applicability of the fifth guideline according to an embodiment of the present invention. Logic region 1104 has a plurality of critical connections to the logic regions 1105 and 1106. A vector is computed in the direction of the sum of all incoming and outgoing critical connections from the logic region 1104. All moves of the logic region 1104 are biased in the direction of the critical vector.
After logic regions are moved to a new location, a cost function associated with the move is evaluated. According to an embodiment of the placement method, the cost function includes components that costs the move based on the logic regions' ability to meet timing constraints and on routing resources required by the logic regions. The placement algorithm may also move around components within a logic region. Thus, the cost function may cost the simultaneous movement of logic regions on a target device and components within a logic region. It should be appreciated that the cost function may utilize other parameters to cost the move.
Moves that improve the cost function are always accepted. According to an embodiment of the placement method, some moves that worsen the cost function are also accepted to allow escape from a local minima. The probability that a move that worsen the cost function will be accepted is given by exp[−ΔC/T], where C is the cost function and T is an outside parameter. If a number of iterations or moves is sufficiently high, then the probability distribution function of the sampled states will reach equilibrium and converge to exp[−ΔC/T]. In equilibrium, high values of T imply that almost any state is equally likely to be visited. Similarly, for low values of T, the states visited are likely to be close to the globally minimum value of the cost function. T is initially set to a high value to allow the system to reach equilibrium. Afterwards, T is slowly lowered. According to an embodiment of the present invention, simulated annealing techniques are utilized to implement the placement method. Simulated annealing is a stochastic optimization technique for finding near-optimal solutions in high-dimensional spaces.
FIG. 12 is a flow chart that illustrates a method for placing logic regions on a target device according to an embodiment of the present invention. At step 1201, determine an initial placement of logic regions of a system to be implemented on a target device.
At step 1202, a cost function associated with the initial placement is evaluated.
At step 1203, new locations are determined for the logic regions. According to an embodiment of the present invention, the new locations are determined using the placement method described. The placement method determines new locations for the logic regions based upon previous locations.
At step 1204, a cost function associated with the logic regions' new locations is evaluated.
At step 1205, it is determined whether the new locations are acceptable. According to an embodiment of the present invention, if a random value between 0 and 1 is less than exp[−ΔC/T], the move is accepted. In this relationship, AC is the value of the cost function associated with logic regions at the new locations subtracted by the value of the cost function associated with logic regions at the previous locations and T is an outside value. According to an alternate embodiment of the present invention, the new locations are accepted only when they improve the cost function.
At step 1206, it is determined whether a predetermined number of iterations or moves have been considered. If the predetermined number of moves have not been considered, control returns to step 1203. If the predetermined number of moves have not been considered, control proceeds to step 1207.
At step 1207, the value T is updated.
At step 1208, it is determined whether the current placement of the logic regions satisfies timing constraints. If the current placement of the logic regions does not satisfy timing constraints, control returns to step 1203. If the current placement of the logic regions satisfies timing constraints, control proceeds to step 1209.
At step 1209, control terminates the process.
FIG. 13 is a flow chart illustrating a method for designing a target device utilizing PLDs for a system. At step 1301, define logic regions for components in the system.
At step 1302, size logic regions that are designated to be automatically sized. According to an embodiment of the present invention, this may be achieved by using the sizing method described.
At step 1303, determine an initial placement for the logic regions. The initial placement includes locations that are feasible for the components of the logic regions.
At step 1304, determine an initial placement for the components in each of the logic region.
At step 1305, it is determined whether initial placement of the components in each logic region is successful. If an initial placement of a component can not be made on the logic region, for example, due to the amount of resources available in the logic region, control returns to step 1303 where the initial placement is re-determined. If initial placement of components is successful, control proceeds to step 1306.
At step 1306, new locations of the logic regions are determined. According to an embodiment of the present invention, the new locations may be determined using the placement method described. It should be appreciated that new locations of components on each logic region may also be determined simultaneously.
At step 1307, it is determined whether the timing constraints of the system are satisfied with the positioning of the logic regions in the new locations. If the timing constraints are not satisfied, control proceeds to step 1306. If the timing constraints are satisfied, control proceeds to step 1308.
At step 1308, control terminates the process.
It should be appreciated that after a position is determined on a logic region for a component and a location is determined on a target device for a logic region, determined properties of the logic region may be preserved. For example, an atom-level netlist may be generated that includes specifications of the modules in terms of device primitives such as the logic elements described with reference to FIG. 1. Placement information may also be generated that includes the logic region's properties, assignment of logic elements or hierarchies of logic elements within the logic region. Information from the atom-level netlist and placement information may be used to preserve determined properties of a logic region for use in subsequent integration into an updated or different system.
According to an embodiment of the present invention, the determined properties of a logic region may be preserved a number of ways. For example, the determined properties of a logic region may be “locked”. When determined properties of a logic region are in a “locked” state, the location and size of the logic region are preserved on the target device during a design of an updated or different system. The determined properties of a logic region may be “back-annotated”. When determined properties of a logic region are in a “back-annotated” state, the location and size of the logic region as well as the position of components in the logic region are preserved on the target device during a design of an updated or different system. The determined properties of a logic region may also be “back-annotated and floating”. When determined properties of a logic region are in a “back-annotated and floating” state, the position of components in the logic region are preserved on the target device during a design of an updated or different system. The location of the logic region, however, may be moved. The determined properties of a logic region may be “locked hierarchically”. When determined properties of a logic region are in a “locked hierarchically” state, the components assigned to the logic region are preserved on the target device during a design of an updated or different system.
In order to support subsequent integration of logic regions with determined properties, the present invention includes an exporting and importing feature. The determined properties of a logic region included in the logic region's atom-level netlist and placement information may be imported into other projects. The exporting feature has the capability to narrow its “focus” from a complete project level down to any level desired in a design hierarchy. For example, in some instances, one may not wish to export all information related to a logic region, but only those pertaining to a specific entity:instance. In these instances, an export focus may be specified to include only regions (including ancestor regions) with nodes that are below the export focus, regions (including ancestor regions) with nodes that are pins, assignments whose source and target nodes are below the export focus, assignments made to nodes that below the export focus, or I/O standard assignments.
The importing feature includes a number of options. According to an embodiment of the present invention, the importing feature allows importing of any or all of the following information: logic region placement information, timing and logic options, and pin assignments. The import feature may also be used to update specific assignment and region settings while preserving other assignment and region settings in a logic region.
FIG. 14 is a flow chart illustrating a method for designing a target device, utilizing PLDs, for a system according to another embodiment of the present invention. At step 1401, a first position on a first logic region is determined for a first component. It should be appreciated that where a plurality of components are assigned to the first logic region, positions for the plurality of components may also be determined.
At step 1402 a first location on the target device is determined for the first logic region. According to an embodiment of the present invention, determining the first location for the first logic region may be achieved using the placement method described. It should be appreciated that step 1401 and 1402 may be performed sequentially or in parallel. It should also be appreciated that where the target device includes a plurality of logic regions, locations on the target device may also be determined for the logic regions.
At step 1403, determined properties of the first logic region are preserved. According to an embodiment of the present invention, preserving determined properties of the first logic region may include assigning the first location on the target device to the first logic region and/or assigning the first position on the first logic region to the first component. Preserving the determined properties of the first logic region may be achieved, for example, by generating an atom-level netlist and placement information. It should be appreciated that where properties of a plurality of logic regions are determined, that the properties of the plurality of logic regions may also be preserved.
At step 1404, the determined properties of the first logic region is imported to a top or higher level design. The determined properties include the preserved determined properties. According to an embodiment of the present invention, the determined property is first exported from its present level design.
At step 1405, the first logic region is integrated with a second logic region in view of the determined properties preserved at the top or higher level design. According to an embodiment of the present invention, integrating the first logic region with the second logic region includes determining a second location from available space on the target device for the second logic region. This may be achieved by using the placement method described. It should be appreciated that the first logic region may be integrated with the second logic region along with other logic regions on the target device.
FIGS. 7, and 12–14 illustrate flow charts describing methods for sizing a logic region, for placing a logic region on a target device, and designing a target device utilizing PLDs for a system. Some of the steps illustrated in these figures may be performed in an order other than that which is described. It should be appreciated that not all of the steps described are required to be performed, that additional steps may be added, and that some of the illustrated steps may be substituted with other steps.
The flexibility of being able to design, optimize, and verify the size and placement of a first logic region and being able to preserve determined properties of the first logic region for use in subsequent integration allows for improved modular, hierarchical, incremental, and team-based design flows. FIG. 15 illustrates an exemplary modular design flow. The design hierarchy includes a top-level design B, and the modules IP and A. The top-level design B instantiates modules IP and A and connections between modules IP and A. Using the modular design flow, a designer may design and optimize modules IP and A separately. Optimization places each module in a single logic region or in some hierarchy of logic regions. Optimization also places components in positions within the logic regions. The designer may preserve the determined properties of the logic regions corresponding to modules IP and A by placing the logic regions in a lock state, back-annotate state, and/or in a back-annotate floating state. The user may also choose to leave the regions floating or auto-size without locking or back-annotating. The preserved determined properties of the logic regions may be imported into system B and used for determining placement of the modules in the top-level design B.
FIG. 16 illustrates an exemplary hierarchical design flow. Hierarchical design G includes modules D, E, and F. Module E includes modules B from FIG. 15 and module C. Modules D, E, and F may be designed and optimized separately. Module E includes a hierarchy of modules, while modules D and F do not. A designer may compile modules D and F after design and optimization and generate an atom-level netlist and placement information for modules D and F. Generating the atom-level netlist and placement information for module E requires multiple steps. First, information including atom-level netlist and placement information for module B is generated and imported into module E. Next, design and optimization of module C is performed and the atom-level netlist and placement information is imported into module E. After optimization of module E is performed, the atom-level netlist and placement information for module E is imported into top-level design G along with the atom-level netlist and placement information for modules D and F and used for determining placement of the modules in the top-level design G.
FIG. 17 illustrates an exemplary incremental design flow. FIG. 17 shows an example where a designer implements the top-level design G from FIG. 16 while adding a module H. According to an embodiment of the present invention, module H may be added without affecting the synthesis and placement of the existing system shown in FIG. 16.
FIG. 18 illustrates an exemplary team-based design flow. In this example, the design of the system may be partitioned into modules I, J, and K. A top-level design of the system may be created by instantiating modules I, J, and K, specifying the connections between the modules, and creating timing assignment and placement constraints. If the approximate size requirement for each module is known, an area restrictions may be placed by creating a logic region for each module. The modules may be assigned to members of the team to be designed and optimized separately. Members of the team may create individual projects for each module and use the assignments created by the system designer. The determined properties of logic region(s) corresponding to the modules may be preserved to preserve performance of the modules or to help in the optimization of the overall design of the system. The modules along with the preserved properties of the modules may be imported into the top-level design in order to allow for a final top-level design compilation and verification/optimization.
It should be appreciated that embodiments of the present invention may improve the performance of designs that do not necessarily include individually optimized modules. The ability of logic region to group logic elements and provide relative placement is an improvement over pure place-and-route techniques. A number of strategies may be implemented to enhance performance. A logic region may be defined based on design hierarchy if the hierarchy closely resembles the structure of the circuit. These designs typically include tightly integrated modules, where the logic for each module is self-contained and modules communicate through well-defined interfaces. A logic region maybe defined based on critical paths if the critical paths are long and span multiple modules. Grouping together the logic elements on critical paths or modules having critical paths may lead to improved performance. Logic regions may be defined based on connections by grouping nodes with high fan-outs and high fan-ins together. This may reduce delays in connections and wiring congestion in the device.
In a preferred embodiment of the present invention, the methods described are performed in response to a processor executing sequences of instructions contained in a memory. Such instructions may be read into the memory, for example, from a computer-readable medium. In an alternate embodiment, hard-wire circuitry may be used in place of or in combination with software instructions to implement the methods described. Thus, the present invention is not limited to any specific combination of hardware circuitry and software.
In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than restrictive sense.

## Claims

1. A method for designing systems on target devices utilizing programmable logic devices (PLDs), comprising:
determining a first position for implementing a component on a first logic region defined by a first user and that groups together a first plurality of components identified by the first user on the PLD;
determining a first location on a target device for implementing the first logic region;
preserving information regarding the first position on the first logic region and the first location on the target device; and
integrating the first logic region with a second logic region defined by a second user and that groups together a second plurality of components identified by the second user in a separate designs in view of the information.

2. The method of claim 1, wherein preserving the information comprises assigning a size and the first location to the first logic region.

3. The method of claim 1, wherein preserving the information comprises assigning the first position on the first logic region to the component.

4. The method of claim 1, wherein preserving the information comprises:
assigning the first position on the first logic region to the component; and
assigning the first location to the first logic region.

5. The method of claim 1, wherein integrating the first logic region with a second logic region in view of the information comprises determining a second location from available space for the second logic region.

6. The method of claim 1, wherein determining the first location on the target device for implementing the first logic region comprises:
assigning an initial location to the first logic region;
moving the first logic region to a new location; and
evaluating a cost function associated with the first logic region in the new location.

7. The method of claim 6, wherein evaluating the cost function comprises:
determining a timing of the system associated with the first logic region in the new location; and
determining routing resources requirements associated with the first logic region in the new location.

8. The method of claim 1, wherein determining the first position on the first logic region for the component and determining the first location on the target device for the first logic region are performed concurrently.

9. The method of claim 8, wherein determining the first position on the first logic region for the component and determining the first location on the target device for the first logic region comprises:
assigning an initial location on the target device to the first logic region;
assigning an initial position on the first logic region to the component; and
evaluating a cost function as the first logic region and the component are moved.

10. A method for designing systems on target devices utilizing programmable logic devices (PLDs), comprising:
determining a first location on a target device for implementing a first logic region defined by a first user and that groups together a first plurality of components on the PLD;
preserving information regarding the first location on the target device; and
integrating the first logic region with a second logic region, defined by a second user in a separate design and that groups together a second plurality of components on the PLD in view of the information.

11. The method of claim 10, wherein preserving the information comprises assigning the first location to the first logic region.

12. The method of claim 10, wherein integrating the first logic region with the second logic region comprises determining a second location from available space for the second logic region.

13. The method of claim 12, wherein integrating the first logic region with the second logic region comprises determining a first position on the second logic region for the second component.

14. The method of claim 10, wherein integrating the first logic region with the second logic region comprises determining a first position on the first logic region for the first component.

15. The method of claim 10, wherein determining the first location on the target device for implementing the first logic region comprises:
assigning an initial location to the first logic region;
moving the first logic region to a new location; and
evaluating a cost function associated with the first logic region in the new location.

16. The method of claim 15, wherein evaluating the cost function comprises:
determining a timing of the system associated with the first logic region in the new location; and
determining routing resources requirements associated with the first logic region in the new location.

17. A method for designing systems on target devices utilizing programmable logic devices (PLDs), comprising:
determining a first position for implementing a first component on a first logic region defined by a first user and that groups together a first plurality of components on the PLD;
preserving information regarding the first position; and
integrating the first logic region with a second logic region, defined by a second user in a separate design and that groups together a second plurality of components on the PLD, in view of the information.

18. The method of claim 17, wherein preserving the information comprises assigning the first position on the first logic region to the first component.

19. The method of claim 17, wherein integrating the first logic region with the second logic region comprises:
determining a first location on a target device for the first logic region; and
determining a second location for the second logic region.

20. The method of claim 19, wherein determining the first location on the target device for implementing the first logic region and determining the second location on the target device for the second logic region are performed concurrently.

21. The method of claim 19, wherein determining the first location on the target device for the first logic region and determining the second location on the target device for the second logic region comprises:
assigning initial locations to the first and second logic regions;
moving the first and second logic regions to new locations; and
evaluating a cost function associated with the first and second logic regions in the new locations.

22. The method of claim 21, wherein evaluating the cost function comprises:
determining a timing of the system associated with the first and second logic regions in the new locations; and
determining routing resources requirements associated with the first and second logic regions in the new locations.

23. A computer-readable medium having stored thereon sequences of instructions, the sequences of instructions including instructions which, when executed by a processor, causes the processor to perform the steps of:
determining a first position on a first logic region for a component;
determining a first location on a target device utilizing a programmable logic device (PLD) for the first logic region;
preserving information regarding the first position on the first logic region and the first location on the target device for the first logic region; and
integrating the first logic region with a second logic region defined by a user in separate design in view of the information.

24. The computer-readable medium of claim 23, wherein preserving the information comprises assigning the first location to the first logic region.

25. The computer-readable medium of claim 23, wherein preserving the information comprises assigning the first position on the first logic region to the component.

26. The computer-readable medium of claim 23, wherein preserving the information comprises:
assigning the first position on the first logic region to the component; and
assigning the first location to the first logic region.

27. A method for designing systems on target devices utilizing programmable logic devices (PLDs), comprising:
optimizing placement of a first logic region defined by a first user and that groups together a first plurality of components on the PLD, at a first location on a target device;
preserving information regarding the first location on the target device;
optimizing placement of a second logic region, defined by a second user in a separate design and that groups together a second plurality of components on the PLD, at a second location on the target device, wherein optimizing the placement of the second logic region is performed separately from optimizing the placement of the first logic region; and
integrating the first logic region with the second logic region.

28. The method of claim 27, wherein preserving the information comprises assigning the first location to the first logic region.

29. The method of claim 27, wherein integrating the first logic region with the second logic region comprises determining a second location from available space for the second logic region.

30. A method for designing systems on target devices utilizing programmable logic devices (PLDs), comprising:
determining a first position for implementing a first component on a first logic region defined by a first user and that groups together a first plurality of components on the PLD in a first design;
determining a first location on a target device for implementing the first logic region in the first design;
preserving information in the first design regarding the first position on the first logic region and the first location on the target device;
determining a second position for implementing a second component on a second logic region defined by a second user and that groups together a second plurality of components on the PLD in a second design;
determining a second location on the target device for implementing the second logic region in the second design; and
integrating the first position for implementing the first component and the first location for the first logic region with the second position for implementing the second component and the second location for the second logic region in the second design utilizing the information in the first design.