Rúbrica

ACTION 1: Use your preferred text editor to edit the .cdsinit file. For example, if you prefer to use VI editor, use:

% vi .cdsinit

ACTION 2: Append the following into the last line of this file. Close the file (:wq for VI editor) once it is done.

load "oaDBChecker.il"

Before appending, the last statement is:

ddsOpenLibManager()

After appending, the last two statements are:

ddsOpenLibManager() load "oaDBChecker.il"

Entering the load statement into .cdsinit ensures that the OADBChecker menu is always available on the CIW when you invoke Virtuoso.

ACTION 3: Invoke Virtuoso. In the UNIX command line, type:

% virtuoso –log CDS.log2 &

After all the windows are opened, you might want to close What's New in IC6.1.6 Overview by LMB File from the top menu of its window followed by selecting Close.

ACTION 4: Open the OADBChecker GUI form from the Tools menu of CIW.

The Innovus Interoperability Checker form will appear.

ACTION 5: LMB the Design tab and tick the box next to Design Library Checker.

LMB the browser buttons (red boxes with white arrow) to select the following:

Lib: zambezi45 Cell: LP_pll View: layout

In the Report File Name, edit it to become oaDBChecker_lppll.rpt.

ACTION 6: LMB the OK button near the bottom-right of the form to start the check.

ACTION 7: Close the form of Non-Default Rules Report by LMB the Close button at the bottom-right of the form.

ACTION 8: You can choose to browse the report, oaDBChecker_lppll.rpt, if you are familiar with the VI text editor. Else, you can close the report and use your preferred text editor to open and view the report. The results of the following checks will be skipped because these have done in the previous sections:

1) Checking of the pipeline character : Has impact on timing constraint 2) Presence of textDisplay object : No impact on MS-STA

3) Unsupported routing shapes : No impact on MS-STA ACTION 9: Scroll down the report until you see the following:

Checking for correct Bus information...PASSED.

This means that there is no bus annotation issue for the cellview.

ACTION 10: Scroll down the report to view the result of the interface bit check:

Checking for status of interface bit for all blocks in the current view...

INFO :Interface bit on terminal 'atbdec_h<1>' of cell 'pll_cp' is set to false.

INFO :Interface bit on terminal 'atbdec_h<0>' of cell 'pll_cp' is set to false.

INFO :Interface bit on terminal 'atbdec_h<0>' of cell 'pll_reg' is set to false.

…

Setting the Interface bit on terminal to false might affect the connectivity (If there is a connectivity issue, the generated Verilog netlist from Innovus might show missing connection). However, in this design, because you are not going to time any path between the two cellviews (pll_reg and pll_cp) so that the result does not impact MS-STA. In addition, because there is no bus annotation issue reported, it is okay that the interface bit of the bus bit terminal is false.

ACTION 11: Scroll down the report to view the results of NDR check:

Performing Check for completeness of all Constraint Groups (NDRs) in the design....

Checking 'catenaDesignRules' Constraint Group for valid layers, appropriate spacing values etc...

INFO : 'catenaDesignRules' Constraint Group is empty.

WARNING : NDR catenaDesignRules does not have valid layers defined, hence this NDR will not be usable in Innovus.

For MS-STA, this result does not matter because the STA does not involve any routing (re-routing) of nets.

ACTION 12: Scroll down the report to view the results of checking for the presence of mosaics:

Checking for presence of mosaics ...

INFO: Mosaics found in the design. The mosaics will be read in Innovus as scalar instances and will cause loss of connectivity on the instance terminals.

This section of the report indicates that there are mosaic instances in the design. Mosaics are not fully interoperable between Innovus and Virtuoso. View the layout to see the mosaics.

ACTION 13: Use Library Manager to open up the cellview. LMB the + sign on the left of

FracN_PLL_45 in the Library section to expand it. zambezi45 will appear. LMB zambezi45 to show the available cells in the Cell section. LMB LP_pll to display all its associated views in the View section.

RMB layout in the View section and select Open With… to invoke the Open File form.

Once the Open File form appears, select Open with Layout XL and LMB the OK button near the bottom-right of the form.

ACTION 14: From the top menu of the layout canvas, LMB Window followed by Workspaces and then select Floorplan. You will see Navigator and Property Editor appear on the left side of the layout canvas.

Window

Basic Classic Assistants Constraints Toolbars EAD

Workspaces Floorplan

ACTION 15: From the top menu of the layout canvas, LMB Tools and select Find/Replace... .

ACTION 16: In the Find/Replace form, use the red button (with white arrow) to select the following two fields:

Search for array in the current cellview.

LMB Zoom to Figure to enable the zooming to the found figure.

LMB Find.

The Figure Count field will show 2. It means that two mosaics are found by the tool.

ACTION 17: LMB Add Select of the Find/Replace form to highlight the figure found first.

You will see the tool zoom in and highlight the mosaic found first.

On the left side, the Navigator will indicate that the cell name of the mosaic is pll_bypclf. The Property Editor also shows some attributes of the mosaic. You might need to expand these to view the entire line.

ACTION 18: In the Find/Replace form, LMB Deselect All followed by the Next button.

Mosaic

ACTION 19: LMB Add Select of the Find/Replace form to highlight the figure found first.

You will see the tool zoom in and highlight the second found figure.

On the left side, the Navigator will indicate that the cell name of the mosaic is pll_bypclf, and the Property Editor also shows some attributes of the mosaic.

Because all the mosaics found are of the cell, pll_bypclf, and there is no timing path from or to this cell, you do not have to worry about the presence of these. Proceed to view the result of the next check.

ACTION 20: Scroll down the report to view results of the XL compliance check. The first and the last few statements are shown:

Checking for XL compliancy...

INFO : Shape ((118.83 517.505) (120.04 517.585)) on layer Metal3 found without net connection.

INFO : Shape ((119.96 515.96) (120.04 517.585)) on layer Metal4 found without net connection.

…

INFO : Shape ((197.585 411.835) (200.08 411.915)) on layer Metal4 found without net connection.

INFO : Shape ((200.0 395.88) (200.08 411.915)) on layer Metal4 found without net connection.

ACTION 21: On the layout window, view the wire shape pointed by the last statement of the report by zooming in (click the right mouse button, hold and draw a box) near the following coordinate:

X = 200.0 Y= 395.88

LMB the wire shape (highlighted if clicked) shown on the next page and type q to query the shape Mosaic

The Route Properties form will appear.

ACTION 22: LMB the Connectivity tab if not already selected.

You will see that the Route Net Name field is empty. This means that this wire has no connectivity information. It will be viewed as a floating net or wire when this cellview is opened in Innovus.

If you further trace this wire, you will notice that these shapes physically connect the terminal ndiv<2> of the pll_fbdiv block to terminal ndiv<2> of the LP_pll_dig_combo block.

Click this piece of wire to query.

Coordinate of lower-left corner of the wire is 200, 395.88.

ACTION 23: Move the mouse pointer to the layout window and type f to fit the window. LMB the block pll_fbdiv. Alternatively, you can LMB the block/instance using the Navigator.

ACTION 24: Under Connectivity of the top menu of the layout canvas, select Nets followed by Propagate.

The Propagate Nets form will appear.

Select this block.

Or click this line.

ACTION 25: LMB Cancel to close the Propagate Nets form.

ACTION 26: LMB the LP_pll_dig_combo block or select I1 (LP_pll_dig_combo) using Navigator.

ACTION 27: Under Connectivity of the top menu of the layout canvas, select Nets followed by Propagate.

The Propagate Nets form will appear.

You might have to scroll down the form to check the connection of terminal ndiv<2>. It can be seen that ndiv<2> terminal of the LP_pll_dig_combo block is not connected logically either.

Select this block.

Or click here.

ACTION 28: LMB Cancel to close the Propagate Nets form.

ACTION 29: Finally, take a quick look at the Final Summary of the OAChecker report:

Final Summary

For this cellview, you learned how to look for mosaics and wires that have no connectivity information.

ACTION 30: Close the text report. For VI editor, enter :q.

ACTION 31: Exit Virtuoso. LMB File in CIW and select Exit…. LMB Yes if prompted to exit Virtuoso.

In this module, you learned to run the OADBChecker to perform several checks on three cellviews and flag out issues that will affect timing analysis. Next module will cover fixing of these issues.