Methods and systems for cross-probing in integrated circuit design

• US 20050268269A1
• Filed: 06/01/2005
• Published: 12/01/2005
• Est. Priority Date: 06/01/2004
• Status: Abandoned Application

• Current Assignee: Magma Design Automation (Synopsys Incorporated)
• Original Assignee: Tera Systems, Inc.
• Inventors: Coiley, Mark
• Application Number:
  US11/141,394
• Publication Number:
  US 20050268269A1
• Time in Patent Office: Days
• US Class Current: 716/113
• CPC Class Codes: G06F 30/30 Circuit design
• CPC Class Codes: G06F 30/31 Design entry, e.g. editors specifically adapted for circuit design
• CPC Class Codes: G06F 30/3312 Timing analysis

Abstract

When designing integrated circuits, RTL source code is received and converted into objects. Objects may include a reference to relevant lines of source RTL code. A graphical user interface (“GUI”) displays the RTL code in an RTL window. The GUI also displays one or more representations of the objects in additional windows. The GUI uses references between the objects and the RTL code to map between the RTL code window and the window(s) of the one or more representations. When a user highlights a portion of one window, the corresponding portions of other windows are automatically highlighted by the GUI. A tool in accordance with the invention optionally operates in conjunction with one or more analysis tools that automatically highlight portions of one or more windows to illustrate potential errors or timing issues. Timing diagrams showing timing delays between various elements of a block may also be displayed.

Claims

1. A method of cross-probing between multiple graphical representations of objects in an integrated circuit design, comprising:

(a) receiving source code for the integrated circuit design;

(b) generating instances of objects representative of the source code, wherein the objects include references to the associated source code;

(c) generating one or more graphical representations of the source code using the instances of objects; and

(d) linking a graphical representation of a particular object to another graphical representation of the particular object, using the reference to the corresponding source code within the particular object as a linking reference.

2. The method of claim 1, wherein the objects further include interconnection information between the objects.

3. The method of claim 1, wherein each of the objects represents functionality performed by a plurality of integrated circuit gates.

4. The method of claim 3, wherein each of the objects further includes gate level physical information corresponding to the gates represented by the objects.

5. The method of claim 3, wherein the objects comprise gate level objects.

6. The method of claim 1, wherein said step (c) comprises one or more of:

arranging the graphical representations of objects in a design layout;

generating a timing model of the design layout;

generating a schematic view of the design layout;

generating a floorplan and wiring view of the design layout; and

generating a net view of the design layout.

7. The method of claim 6, wherein said step (d) comprises linking the timing model to the design layout.

8. The method of claim 6, wherein said step (d) comprises linking the schematic view to the design layout.

9. The method of claim 1, wherein said step (c) comprises arranging the graphical representations of objects in at least one hierarchy tree.

10. The method of claim 9, wherein said step (d) comprises linking the source code to a logical hierarchy.

11. The method of claim 9, wherein said step (d) comprises linking the source code to a synthesis hierarchy.

12. The method of claim 9, wherein said step (d) comprises linking the source code to a physical hierarchy.

13. The method of claim 1, wherein a hierarchy of the graphical representation is dissimilar from a hierarchy of the source code.

14. The method of claim 1, wherein a hierarchy of a first graphical representation is dissimilar from a hierarchy of a second graphical representation.

15. The method of claim 1, further comprising:

(e) displaying a plurality of the multiple graphical representations of objects in the integrated circuit design; and

(f) highlighting a corresponding sub-set of the displayed plurality of the multiple graphical representations.

16. A method of designing integrated circuits, comprising:

(a) displaying source code for an integrated circuit design, wherein the source code defines objects having multiple levels of abstraction;

(b) displaying at least one representation of an object; and

(c) linking the source code and the at least one representation such that any action in one effects a related action in the other.

17. The method of claim 16, wherein said step (b) comprises:

displaying at least one diagram relating to the displayed source code.

18. The method of claim 17, wherein said step (b) further comprises:

displaying at least one physical layout diagram relating to the displayed source code.

19. The method of claim 18, wherein said step (b) further comprises:

displaying at least one hierarchy-level physical layout diagram.

20. The method of claim 18, wherein said step (b) further comprises:

displaying at least one leaf-level physical layout diagram.

21. The method of claim 17, wherein said step (b) comprises:

displaying at least one schematic diagram relating to the displayed source code;

wherein the schematic diagram includes the at least one representation.

22. The method of claim 21, wherein said step (b) further comprises:

displaying at least one schematic diagram showing at least one representation of connections between objects.

23. The method of claim 16, wherein said step (b) comprises displaying at least one timing report of the integrated circuit design.

24. The method of claim 23, wherein said step (b) further comprises:

displaying a schematic of at least one critical path of the integrated circuit design;

wherein the critical path includes the at least one representation.

25. The method of claim 23, wherein said step (b) further comprises:

displaying a slack produced by each element in at least one critical path of the integrated circuit design.

26. The method of claim 23, wherein said step (b) further comprises:

displaying a list of at least one critical path in the integrated circuit design.

27. The method of claim 23, wherein said step (c) comprises linking displays produced by steps (a) and (b) such that selecting a critical path in the timing report will, in at least one other display, highlight representations of each element in the critical path in sequence according to positions of the elements in the critical path.

28. The method of claim 16, wherein said step (c) comprises linking displays produced by steps (a) and (b) such that selecting a representation of an element in one of the displays will highlight a representation of the same element in at least one other display.

29. The method of claim 16, wherein said step (b) comprises:

displaying at least one of a logical hierarchy tree, a synthesis hierarchy tree, and a physical hierarchy tree.

30. A front-end integrated circuit design tool, comprising:

(a) a code manager that displays source code for an integrated circuit design;

(b) a hierarchy manager that displays at least one hierarchy of objects; and

(c) a timing manager that displays a timing report of the integrated circuit design,

wherein the managers are linked such that any action in one of the managers effects a related action in each of the other managers.

31. The circuit design tool of claim 30, further comprising:

(d) a diagram manager that displays at least one diagram relating to the displayed source code.

32. The circuit design tool of claim 31, wherein said diagram manager comprises:

a layout manager that displays at least one layout diagram relating to the displayed source code.

33. The circuit design tool of claim 32, wherein the at least one layout diagram shows at least one hierarchy-level node.

34. The circuit design tool of claim 32, wherein the at least one layout diagram shows at least one leaf-level node.

35. The circuit design tool of claim 34, wherein at least one leaf-level node is a conglomerate of gate-level logic components.

36. The circuit design tool of claim 34, wherein at least one leaf-level node is a gate-level logic component.

37. The design tool of claim 31, wherein said diagram manager comprises:

a schematic manager that displays at least one schematic diagram relating to the displayed source code.

38. The design tool of claim 37, wherein the at least one schematic diagram shows at least one representation of connections between objects.

39. The design tool of claim 30, wherein the timing manager displays a schematic of at least one critical path.

40. The design tool of claim 30, wherein the timing manager displays a slack produced by each element in the at least one critical path.

41. The design tool of claim 30, wherein the timing manager displays a list of at least one critical path in the integrated circuit design.

42. The design tool of claim 30, further comprising:

a selection highlighter that highlights a representation of at least one specific element in each of the managers when a representation of the at least one specific element is selected in any one of the managers.

43. The design tool of claim 30, further comprising:

a selection animator that highlights at least one representation of each element in a critical path in an appropriate time sequence in each of the managers when a critical path displayed by the timing manager is highlighted.

44. The design tool of claim 30, wherein said hierarchy manager displays at least one of a logical hierarchy, a synthesis hierarchy, and a physical hierarchy.

45. The design tool of claim 30, wherein said source code is one of the following:

Verilog, VHDL, systemC and System Verilog.

46. A method of cross-probing between multiple graphical representations of objects in an integrated circuit design, comprising:

(a) receiving source code for the integrated circuit design;

(b) generating instances of objects representative of the source code, wherein the objects include a naming convention that identifies the associated source code;

(c) generating one or more graphical representations of the source code using the instances of objects; and

(d) linking a graphical representation of a particular object to another graphical representation of the particular object, using the reference to the corresponding source code within the particular object as a linking reference.