Skip to main content

Design Hierarchy

 

Design Hierarchy

  • The hierarchy, or 'divide and conquer' strategy, entails breaking down a subsystem into sub-modules and then repeating the process on the sub-modules until the smaller parts' complexity is manageable. This method is similar to how large programmes are broken down into smaller and smaller parts before simple subroutines with well-defined functions and interfaces can be written in software. The architecture of a VLSI chip can be expressed in three domains, as we've seen.As a result, each domain's hierarchy structure can be represented separately. However, it is important for design simplicity that the hierarchies in different domains can be easily mapped into one another.

    Figure 1 demonstrates the structural decomposition of a CMOS four-bit adder into its components as an example of structural hierarchy. Decomposing the adder into one-bit adders, separate carry and sum circuits, and finally individual logic gates is possible.The design of a simple circuit understanding a well-defined Boolean function is much easier to manage at this lower level of the hierarchy than it is at the higher levels.

    Partitioning a complex device into its different functional blocks would provide useful guidelines for the actual realisation of these blocks on chip in the physical domain. To create a useful floorplan, the approximate shape and size (area) of each sub-module must obviously be estimated. Figure 2 shows a basic floorplan generated by hierarchical decomposition of a four-bit adder in the physical description (geometrical layout) domain. This physical view shows the adder's external geometry, input and output pin positions, and how pin locations enable certain signals (in this case, carry signals) to be moved from one sub-block to the next without the use of external routing. At lower levels of the physical hierarchy, the internal mask


  • Figure-1: Structural decomposition of a four-bit adder circuit, showing the hierarchy down to gate level.
    Figure-2: Hierarchical decomposition of a four-bit adder in physical (geometrical) description domain.



  • Figure- 3: Layout of a 16-bit adder, and the components (sub-blocks) of its physical hierarchy.

  • Figure-4: The structural hierarchy of a triangle generator chip
    Figure- 5: Physical layout of the triangle generator chip.
  • layout of each adder cell defines the locations and the connections of each transistor and wire. Figure 3 shows the full-custom layout of a 16-bit dynamic CMOS adder, and the sub-modules that describe the lower levels of its physical hierarchy. Here, the 16-bit adder consists of a cascade connection of four 4-bit adders, and each 4-bit adder can again be decomposed into its functional blocks such as the Manchester chain, carry/propagate circuits and the output buffers. Finally, Fig. 4 and Fig. 5 show the structural hierarchy and the physical layout of a simple triangle generator chip, respectively. Note that there is a corresponding physical description for every module in the structural hierarchy, i.e., the components of the physical view closely match this structural view.

Comments

Popular posts from this blog

Concepts of Regularity, Modularity and Locality

 By splitting the large structure into many sub-modules, the hierarchical design approach eliminates design complexity. To make the process easier, other design principles and approaches are usually needed. Regularity ensures that a large system's hierarchical decomposition can produce as many simple and identical blocks as possible.The design of array structures made up of similar cells, such as a parallel multiplication array, is a good example of regularity. Regularity can be seen at all levels of abstraction: uniformly sized transistors simplify the design at the transistor stage. Identical gate structures can be used at the logic level, and so on.A 2-1 MUX (multiplexer), a D-type edge-triggered flip flop, and a one-bit full adder are shown in Figure 7 as standard circuit-level designs. All of these circuits were created solely with inverters and tri-state buffers. This theory can be used to create a variety of different functions if the designer has a limited library of well-d...

Gate Array Design

The gate array (GA) comes after the FPGA because of the quick prototyping capability. As user programming is used to implement the design of the FPGA chip, metal mask design and processing is used to implement the design of the gate array. A two-step manufacturing process is needed for gate array implementation: The first phase, which uses generic (standard) masks, leaves each GA chip with an array of uncommitted transistors. These uncommitted chips can be saved for later customization after the metal interconnects between the array's transistors are defined (Fig. 1). Since the patterning of metallic interconnects is done at the end of the chip fabrication, the turn-around time can be still short, a few days to a few weeks. Figure 2 depicts a gate array chip's corner, which includes bonding pads on the left and bottom sides, diodes for I/O protection, nMOS and pMOS transistors for chip output driver circuits in the neighbouring areas of bonding pads, arrays of nMOS and pMOS tra...

Comparison Among Various Design Styles

   Testing and design verification Neither of these topics can be over-emphasised. If a fabricated device cannot be tested, it is worthless. However, 100% testing is virtually impossible with many modern VLSI designs, especially those containing significant amounts of RAM. A compromise must be reached in which the test strategy used shows that there is a good probability that the design is correct. Design for testability is virtually a subject in its own right, and is covered elsewhere. Verification of full custom designs is required to avoid the possibility that an error can be generated by the designer in translating from the desired schematic to layout form (though no design rule may have been broken). The risk (in terms of wasted time and fabrication costs) demands that efforts be made to establish that the schematic and the layout correspond to exactly equivalent circuits. Verification involves extracting (using an appropriate CAD tool) a netlist and a list of components ...