SimVision: Using the Source Browser. Product Version 15.2 February 2016

Transcription

1 Product Version 15.2 February 2016

2 Cadence Design Systems, Inc. All rights reserved. Portions Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation. Used by permission. Cadence Design Systems, Inc. (Cadence), 2655 Seely Ave., San Jose, CA 95134, USA. Product SimVision contains technology licensed from, and copyrighted by: Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties and is Regents of the University of California, 1984, the Australian National University, Scriptics Corporation, and other parties. All rights reserved. Open SystemC, Open SystemC Initiative, OSCI, SystemC, and SystemC Initiative are trademarks or registered trademarks of Open SystemC Initiative, Inc. in the United States and other countries and are used with permission. STC, copyright 1994 Hewlett-Packard Company. ZLIB, copyright Jean-loup Gailly and Mark Adler. Trademarks: Trademarks and service marks of Cadence Design Systems, Inc. contained in this document are attributed to Cadence with the appropriate symbol. For queries regarding Cadence s trademarks, contact the corporate legal department at the address shown above or call All other trademarks are the property of their respective holders. Restricted Permission: This publication is protected by copyright law and international treaties and contains trade secrets and proprietary information owned by Cadence. Unauthorized reproduction or distribution of this publication, or any portion of it, may result in civil and criminal penalties. Except as specified in this permission statement, this publication may not be copied, reproduced, modified, published, uploaded, posted, transmitted, or distributed in any way, without prior written permission from Cadence. Unless otherwise agreed to by Cadence in writing, this statement grants Cadence customers permission to print one (1) hard copy of this publication subject to the following conditions: 1. The publication may be used only in accordance with a written agreement between Cadence and its customer. 2. The publication may not be modified in any way. 3. Any authorized copy of the publication or portion thereof must include all original copyright, trademark, and other proprietary notices and this permission statement. 4. The information contained in this document cannot be used in the development of like products or software, whether for internal or external use, and shall not be used for the benefit of any other party, whether or not for consideration. Disclaimer: Information in this publication is subject to change without notice and does not represent a commitment on the part of Cadence. Except as may be explicitly set forth in such agreement, Cadence does not make, and expressly disclaims, any representations or warranties as to the completeness, accuracy or usefulness of the information contained in this document. Cadence does not warrant that use of such information will not infringe any third party rights, nor does Cadence assume any liability for damages or costs of any kind that may result from use of such information. Restricted Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR and DFAR et seq. or its successor.

3 Contents Opening a Source Browser Window Navigating the Design Hierarchy Selecting Text in the Source Browser Accessing Design Objects and Values Opening a File in the Source Browser Displaying `include Files in the Source Browser Displaying `define Macros in the Source Browser Expanding and Collapsing Macro References Displaying Object Values Within Macro References Displaying a Macro Definition Expanding Macros with generate Statements Searching the Current Source File Searching All Design Source Files Editing a Source File Using the Design Files Sidebar Using Bookmarks in the Source Browser Running the Simulation with the Source Browser Setting Breakpoints Setting Probes Forcing and Releasing a Signal Value in the Source Browser Depositing a Signal Value in the Source Browser Running the Simulation Viewing the Call Stack For More Information Changing the Size of the Call Stack Repositioning the Call Stack February Product Version 15.2

4 Navigating the Call Stack Using the Call Stack to Display Variables in the Source Browser February Product Version 15.2

5 1 The Source Browser gives you access to the source code for your design. It recognizes the Verilog, SystemVerilog, VHDL, C, C++, and SystemC, and e languages, and it can color-code keywords, comments, and message strings that it detects in the source files. You cannot edit the source code directly in the Source Browser, because it would no longer represent the design snapshot currently loaded into the simulator. However, you can use the Source Browser to invoke a text editor, make changes to the source file, and then create a new snapshot and load it into the simulator. For More Information? Opening a Source Browser Window on page 6? Navigating the Design Hierarchy on page 7? Selecting Text in the Source Browser on page 8? Accessing Design Objects and Values on page 8? Opening a File in the Source Browser on page 10? Displaying `include Files in the Source Browser on page 10? Displaying `define Macros in the Source Browser on page 11? Searching the Current Source File on page 21? Searching All Design Source Files on page 24? Editing a Source File on page 25? Using the Design Files Sidebar on page 26? Using Bookmarks in the Source Browser on page 28 February Product Version 15.2

6 Video? SimVision Source Browser Introduction Opening a Source Browser Window To display a source file for a selected scope or design object:? Select a scope or object in any SimVision window and click Source Browser,. If you select nothing before you click the Source Browser button, the target Source Browser window opens to the debug scope, if you are attached to a simulator. All other Source Browser windows are empty when you open them, unless you send a scope or object to them. The Source Browser displays the source code associated with the selected scope, as shown in Figure 1-1 on page 6. Figure 1-1 Source Browser Window February Product Version 15.2

7 The standard toolbars and menus perform the common functions available in all SimVision windows, such as controlling the simulation. A navigation toolbar lets you move through the design hierarchy and open source files for the scopes that you select. You can also add a toolbar to search for text strings and line numbers within the source file. A call stack is displayed at the bottom of the window, showing the current call on the stack. The source file uses the following default colors to show the type of objects in the source file: Blue Green Red Language keywords Text strings, and objects that have been traced Comments You can change these default colors, as described in Source Browser Colors. Navigating the Design Hierarchy From the Source Browser, you can access the design hierarchy and the files associated with each module or block in the hierarchy, including SystemC processes, modules, and instances. Note: You cannot navigate a UDP with the Source Browser. To set the current debug scope:? Right-click a scope in the source code and choose Set Debug Scope from the pop-up menu. To navigate to another scope in the hierarchy:? Select a scope from the drop-down list in the Scope field. When you select a scope, the Source Browser adds its subscopes to the hierarchy, if any, and it displays the source code for the selected scope. To move up one level in the hierarchy:? Click the Scope Up button,. The Design Browser sidebar tracks the scope that is currently selected in the Source Browser. When you select a scope in the Source Browser, its name is displayed in bold in the Design Browser sidebar. If necessary, the Design Browser sidebar expands the scope tree to make the selected scope visible. February Product Version 15.2

8 As you move through the hierarchy, the Source Browser maintains a history of the scopes you have visited. By default, the Source Browser history list contains the 20 most-recently visited scopes. You can change the size of the history list in the Preferences form, as described in Source Browser. To move through the scope history:? Click Previous Scope,, to move back through the scope history. This button also has a drop-down list, so that you can jump to any scope in the list.? Click Next Scope,, to move forward through the scope history. This button also has a drop-down list, so that you can jump to any scope in the list. As you move through the hierarchy, the Source Browser maintains a list of the source files or design units that are related to the current scope, such as included files and VHDL units. To access a source file or design unit:? Select it from the drop-down list. This list is labeled Files for Verilog designs. It is labeled Units for VHDL designs. Selecting Text in the Source Browser The Source Browser defines the following mouse actions for selecting plain text: Double-click Control-triple-click Shift-click or drag Select a word Select a line Select all an area of text When you select an area of text in the Source Browser window, you select the signals and variables contained within that text area. See Accessing Design Objects and Values for more information. Accessing Design Objects and Values Design objects are underlined in the Source Browser. You can select objects in several ways:? Click the object.? Control-click to select multiple objects. February Product Version 15.2

9 ? Use the Select menu to select specific types of objects, such as scopes, signals and variables, and types of ports.? Drag the mouse over an area of text to select all of the objects in that area. After you select an object, you can:? Add it to other windows by clicking the window s Send To toolbar button, or by holding the left mouse button and dragging the objects to the other window? Jump to the definition of the object by right-clicking and choosing Go To Definition from the pop-up menu When you place the cursor over an object, the Source Browser pops up its full hierarchical name. If you have set a probe on the object, the Source Browser also displays the name of the database to which it is probed and its value at the current time. If you have not set a probe for the object, it is labeled Not probed, and its value is shown as Value Not Available at all times except the last simulation time. If you move the cursor to that time, all objects have a value, regardless of whether they have been probed. If the value of an object changes during the current clock cycle, the pop-up message indicates the signal transition at that time point. For example, if the signal transitions from 0 to 1 in the current clock cycle, the pop-up message shows b0 -> b1. You can turn off the display of signal transitions for all SimVision windows by disabling Display signal transition values in the Signal Options tab of the Preferences window. You can display object values on a separate line in between each line of source code. Signal transitions are displayed with the same annotation as in the pop-up message. Note: When Watch Live Data is enabled, updated until the simulation pauses or stops., values in the Source Browser are not You can display and hide object values in any of the following ways:? Toggle the Display or hide values,, in the Source Browser toolbar.? Enable or disable the View Display Values in the Source Browser menu.? Right-click anywhere in the source code area of the window and enable or disable Display Values from the pop-up menu.? Enable or disable Display Values in the Source Browser in the Source Browser tab of the Preferences window. Note: Changing the value annotation setting in the Source Browser also changes the setting of the preference. In addition, changing the setting in one Source Browser window updates the setting in all Source Browser windows. February Product Version 15.2

10 Opening a File in the Source Browser You can open any source file, regardless of whether it is part of your design. When you open a source file in this way, the file has no context within the design. Therefore, you cannot view the values of objects or expand macros in the source file. If you want to have access to this information, you must open the file as described in Opening a Source Browser Window. To open a source file: 1. Click Open Source,, or choose File Open Source File. SimVision opens the Open Source File form. The path shown in the Directory field is determined by the SIMVISION_WORKDIR environment variable. If you have not set this variable, the path is the last directory visited by any of the file browser forms. You can navigate to other directories to find the source file that you want to open. From the Files of type menu, you can choose the types of files that you want to display. 2. Select a file and click Open. Tip If the source file is going to take a long time to load, the Source Browser adds an Abort button to the status bar. Click this button if you do not want to load this source file. Displaying `include Files in the Source Browser You may want to see the source files that you include in your design. Files that you `include are underlined in the Source Browser. To open an `include file:? Double-click on the filename, and the Source Browser displays the file in the current window. You cannot edit files that you display in the Source Browser. If you were to change the source file, you would need to recompile the design and generate a new snapshot. To open a file for editing:? Choose File Open Source File and choose the file from the Open Source File form. February Product Version 15.2

11 If you make changes to the source file, be sure to reinvoke the simulation by choosing Simulation Reinvoke. This causes the simulator to recompile the design, generate a new snapshot, and load it into SimVision for simulation. For more information, see Reinvoking the Simulation. Displaying `define Macros in the Source Browser When debugging designs that contain define macros, it is often helpful to view a macro definition in the context of a macro reference. The Source Browser lets you expand macros in-place. When a macro is expanded, it is replaced with its contents, including argument substitution, and object values. Any signals, scopes, and macro references in the expanded macro are underlined. If there are nested macros (macros within macros) you can also expand the nested macros. For example, suppose you have defined the following macros: `define now $time `define message(sev, VERB, MSG) \ if (get_verbosity_level() > VERB) begin \ case (SEV) \ ERR: $display ( %0t: Error: %s, `now, MSG); \ default: $display( %0t: message: %s, `now, MSG); \ endcase \ end `define debug_message(verb, MSG) if (debug) begin \ `message(note, VERB, MSG) \ end `define debug(msg) `debug_message(low, MSG) `define STARTING Starting testbench module top; reg debug; const int LOW = 0; const int NOTE = 1; const int ERR = 2; initial begin debug(starting); end function get_verbosity_level; begin end endfunction // get_verbosity_level endmodule In this example, the debug macro calls the debug_message macro, which calls the message macro. When you expand the debug macro, you might want to see the substitutions only within the debug_message macro, or you might want to expand the macro through all levels to also see the substitutions within the message macro. Macro references are underlined in the Source Browser, similar to other design objects. When you hover the mouse cursor over a macro reference, the tick ( ) character is replaced February Product Version 15.2

12 with a plus sign (+), the macro instance is highlighted, and a tooltip pops up to show the macro definition, as shown in Figure 1-2 on page 12. Figure 1-2 Hovering Over a Macro Reference Tip The colors used to highlight macros are customizable in the Source Browser Colors Preferences page. For More Information? Expanding and Collapsing Macro References on page 12? Displaying Object Values Within Macro References on page 14? Displaying a Macro Definition on page 15? Expanding Macros with generate Statements on page 15 See Also? Displaying Macros with generate Statements in Debugging SystemVerilog Expanding and Collapsing Macro References You can expand a macro reference one level at a time, in any of the following ways:? Click the plus sign for the macro reference? Double-click the macro reference? Right-click over the macro reference and choose Expand Macro from the pop-up menu February Product Version 15.2

13 When you expand a macro, the + icon is changed to a - icon, so you can collapse the macro. The background area of the expanded macro is shaded to differentiate actual source code from expanded code Figure 1-3 on page 13 shows the debug macro expanded one level. In this example, the debug macro passes the value of LOW directly to debug_message for the first argument, and it substitutes the string defined by the STARTING macro for the second argument. Figure 1-3 Expanding a Macro One Level When you hover over the - sign in front of an expanded macro, a tooltip shows the original macro reference. Macro references within the expanded macro can be also be expanded in the same way, one level at a time, or you can expand the macro through all levels at once. To expand a macro reference through all levels:? Right-click the macro reference and choose Expand Macro Deep from the pop-up menu. Figure 1-4 on page 13 shows the debug macro expanded through all levels. Figure 1-4 Expanding a Macro Through All Levels When you hover the mouse cursor over the minus sign for an expanded macro, the Source Browser highlights the entire macro expansion and pops up a tooltip that displays the collapsed macro reference. February Product Version 15.2

14 You can collapse an expanded macro in either of the following ways:? Click the minus sign for the macro reference (the minus sign changes to a plus sign)? RIght-click within the expanded macro and choose Collapse Macro from the pop-up menu When you collapse an outer level of the macro, any expansions of the inner levels are preserved, and when the macro is re-expanded, the inner expansions are restored. Macro expansions are applied only to the current window. Therefore, if you open other Source Browser windows, the macros are not expanded in those windows. Furthermore, if you save the Source Browser window settings to a command file, as described in Saving and Restoring Your Debugging Environment, macro expansions are not saved. Displaying Object Values Within Macro References You can display object values within a macro reference. In addition, objects within the expanded portion of a macro are selectable, and you can send them to other SimVision windows. For example, to send objects within the debug macro to the Watch window:? Select the objects, or select an area of text, then right-click and choose Send To Watch Window or Send To New Watch Window. In this example, if the debug macro is expanded one level, as shown in Figure 1-3 on page 13, only LOW is sent to the Watch window. If the macro is expanded through all levels, as shown in Figure 1-4 on page 13, ERR, NOTE, LOW, and debug are sent to the window, as shown in Figure 1-5 on page 15. February Product Version 15.2

15 Figure 1-5 Sending Macro Objects to the Watch Window Displaying a Macro Definition When debugging a macro reference, you might also want to look at its definition. To jump to a macro definition:? Right-click the macro reference and choose Show Macro Definition from the pop-up menu. The macro definition is highlighted in blue, and a blue arrow points to the starting line number of the definition, as shown in Figure 1-6 on page 15. Figure 1-6 Jumping to a Macro Definition Expanding Macros with generate Statements Macros can contain generate statements, and generate statements can contain macros. The values of macros and of the contents of expanded macros always reflect the currently selected generate scope. For example, the following code defines a macro, gen2. This macro creates a buffer, i2a, and it uses a for loop to generate a set of buffers, bufs[0] to bufs[7]. It also uses a macro, `inbit, to specify a bit value of 1: `define inbit 1 b1 February Product Version 15.2

16 `define gen2 \ generate \ genvar g2; \ buf i2a(out[3], `inbit); \ for (g2=0; g2<8; g2++) begin : bufs \ buf i2b(out[g2], `inbit); \ end \ endgenerate module test; wire [7:0] out; `gen2 endmodule When you view this source code in the Source Browser, you can see the hierarchy in the Design Browser sidebar. It shows the test module at the top, bufs, and i2 below test, and the buffers 0 through 7 below bufs, as shown in.figure 1-7 on page 16 Figure 1-7 Displaying Generated Buffers in the Design Browser Sidebar When you expand macros in the Source Browser, you can then see the annotated values of the macros and variables, as shown in Figure 1-8 on page 17. February Product Version 15.2

17 Figure 1-8 Displaying Values for Objects in the test Scope Annotated values for objects in test When the test scope is selected, the Source Browser annotates the values for the data objects defined in that scope, that is, the declaration of out[7:0], the value of out[0] in i1, and the value of out[3] in i2a. The generate statement creates 8 buffers, from bufs[0] to bufs[7], each in a different generate scope. To see the values for the objects within each scope, you must select a generate scope from the Design Browser sidebar, as shown in Figure 1-9 on page 18. February Product Version 15.2

18 Figure 1-9 Displaying Values for Objects in bufs[0] Annotated values for bufs[0] Now consider the case in which the generate statement contains macro calls. In this example, the generate statement contains a nested for loop, and each for loop calls several macros: `define GENSIZE 8 `define mbuf1(gx) buf(out[gx], in[gx]) `define mbuf2(ga, gb) buf(out[ga], in[gb]) `define mg1 g1 `define mg2 g2 `define m0 0 module test; wire [`GENSIZE-1:0] in; wire [`GENSIZE-1:0] out; reg [`GENSIZE-1:0] reg_in; genvar g1, g2; generate for (g1 = 0; g1 <`GENSIZE; g1++) begin : bufs1 buf(out[`mg1], in[g1]); `mbuf1(`mg1); for(g2 = 0; g2 <`GENSIZE; g2++) begin : bufs2 buf(out[`mg2], in[`mg1]); `mbuf2(`mg1, `mg2); end end endgenerate February Product Version 15.2

19 buf(out[`m0], in[0]); `mbuf1(`m0); assign in = reg_in; initial begin reg_in = `GENSIZE b10; end endmodule When you select test in the Design Browser sidebar, you can see the values of data objects within the top-level scope, as shown in Figure 1-10 on page 19. Figure 1-10 Displaying Values in the Top-Level Scope Annotated values in test When you select a buffer under bufs1, you can see the values of the data objects in the outer for loop, but not in the inner for loop, as shown in Figure 1-11 on page 20. February Product Version 15.2

20 Figure 1-11 Displaying Values in the Outer for Loop Annotated values in the To see the values in the inner for loop, you must select a scope under bufs2, as shown in Figure 1-12 on page 21. February Product Version 15.2

21 Figure 1-12 Displaying Values in the Inner for Loop Annotated values in the innter for loop Searching the Current Source File To search for a string or a line number within the source file that is currently displayed in the Source Browser, you must add a search toolbar to the Source Browser window or use the Edit menu. To open the search toolbar:? Click Show Search,. From the toolbar, you can search for a text string or a line within the source file. To search for a text string:? Enter a search string in the Text Search field, and click Search Up,, or Search Down,, to find the next or previous occurrence of the string within the file. February Product Version 15.2

22 The string can include any of the following special characters: * Matches any number of characters? Matches a single character " Matches a word boundary, where a word boundary is any character except a letter, number, or the underscore. Because the quotation mark is a special character, you must use a literal string or a regular expression to search for strings that contain quotation marks. To specify a literal or a regular expression, begin the search string with one of the following patterns: ***= Treat the remainder of the search string as a literal. ***: Treat the remainder of the search string as a Tcl advanced regular expression. Tcl advanced regular expressions let you define complex search strings. Because SimVision keeps a history of the search strings that you enter, you can enter a partial string and press Tab. If the history contains one matching string, SimVision seeds the Search field with that string. If the history contains more than one matching string, it displays a list of those strings, and you can choose one. Tip You can also initiate a search by selecting some text in the Source Browser, pressing the right mouse button, and choosing Search for Selected Text from the pop-up menu. The following are some examples of searching for the string out: out <space>out "out "out" Returns strings that contain out, such as out, output, and inout. Returns strings that end with out, such as out and inout, but not output. Returns strings that begin with out, such as out and output. Returns only the word out. ***="out" Returns all occurrences of the quoted string "out". ***:\yout\y February Product Version 15.2

23 Returns only the word out, where \y is a Tcl word boundary indicator. ***:(\yout\y \Yout\y) ***:((ino outp)ut) Returns words that begin with out, and words that end with out; that is, it returns inout and output, but not out. Returns the words inout and output, but not out. To search for a text string by using the Text Search form: 1. Choose Edit Text Search, or click Ctrl-F. SimVision opens the Text Search form. 2. Enter a search string in the Find what field, including the special characters and patterns that you can use in the Text Search field. Note: If you select text before opening the Text Search form, the Fine what field is seeded with that text. The Text Search form also gives you the following options:? Disable Regular Expression to specify the exact string you want to find. When this button is disabled, special characters and patterns are treated like ordinary characters.? Enable Match Case if you want the search to be case-sensitive.? Enable Up or Down to control the direction of the search. 3. Click Find Next to find each occurrence. 4. Press Close to end the search. To search for a line within the source file:? Enter a line number in the Go To Line field and click Go,. The Source Browser displays a blue arrow in the left column of the source file at the specified line. To go to a line using the Edit menu:? Choose Edit Go To Line from the menu and enter a line number in the Go To Line form. To remove the Search toolbar:? Click Hide Search,. February Product Version 15.2

24 Searching All Design Source Files To search for a string in all of the source files that make up the design, including any simulator TCL scripts specified at startup with the input option: 1. From any SimVision window, choose Windows Tools Design File Search, or right-cick and choose Send to Design File Search. SimVision opens the window shown infigure 1-13 on page 24. Figure 1-13 Design File Search Window 2. Enter a grep-style search string in the Regular expression search field. 3. Enable Case sensitive, if you want the search to match the case of the text string. 4. In the Match files with pattern field, enter a glob-style pattern representing a file name, or partial name, to limit the search to a specific file or set of files. You can specify more than one pattern, separated by spaces. SimVision matches both patterns. For example, if you specify *.v *.vhd, SimVision returns all files with the.v or.vhd file extension. Note: SimVision can search Tcl files that are specified with the irun -input option. February Product Version 15.2

25 However, it cannot search Tcl files that are sourced by another method, such as a source command at the ncsim prompt. 5. Click Search, and SimVision returns the file name, line number, and text that matches the search string. 6. Click a row in the results list to display the file in a Source Browser window with the blue pointer located at the line number. When you open a source file in this way, the file has no context within the design. Therefore, you cannot view the values of objects or expand macros in the source file. If you want to have access to this information, you must open the file as described in Opening a Source Browser Window. Editing a Source File You cannot edit a source file directly in the Source Browser, because it would no longer represent the design snapshot currently loaded into the simulator. However, you can invoke a text editor, either from the Source Browser or outside of the SimVision environment, make the necessary changes, and then create a new snapshot and load it into the simulator. Note: If you used any compressed source files to create the design snapshot, you can view those source files, but you cannot edit them. For more information on using compressed files with Incisive Simulator, see Support for Compressed Files in the Irun User Guide. To invoke a text editor from the Source Browser:? Use the Scope toolbar to display the source code you want to edit, then click Edit Source,. The editor that you invoke depends on your preferences setting. See Source Browser for information on choosing an editor. To invoke a text editor from outside of the SimVision environment: 1. Copy the name of the currently displayed file to the clipboard, in any of the following ways:? Choose Edit Copy File Path.? Right-click anywhere in the source area and select Copy File Path from the pop-up menu.? Right-click over the Files text field and choose Copy File Path from the pop-up menu. 2. Paste the file name into a command to invoke your text editor. February Product Version 15.2

26 After you save the file and reselect the scope for the file, the Source Browser displays the Modified indicator in the Source Browser status bar, as shown in Figure 1-14 on page 26. Figure 1-14 Modified Indicator in the Source Browser Status Bar If you have edited the source file after creating the snapshot but before invoking SimVision, the Source Browser displays the Modified indicator, and it displays a message that objects might not line up correctly in the Source Browser as a result of the changes. To create a new snapshot and load it into the simulator:? Choose Simulation Reinvoke Simulator from the menu bar of any SimVision window. SimVision compiles and elaborates the design, loads the new snapshot into the simulator, and sets simulation time to 0. For more information, see Reinvoking the Simulation. Using the Design Files Sidebar The Design Files sidebar gives you access to all of the source files that make up the design. From this sidebar, you can open any file in the Source Browser window, search for a string within the files in the list, and filter the list to display only the files you are interested in. Important Opening a file in this way does not change the debug scope. This means that you cannot set breakpoints or show the values of objects in the source file. To change the scope, click Current execution point,, to go to the current debug scope, then select the scope as described in Navigating the Design Hierarchy on page 7. To open the Design Files sidebar:? Click the Design Files tab,, in the Source Browser window. The sidebar displays a list of the source files, grouped by directory, as shown in Figure 1-15 on page 27. February Product Version 15.2

27 Figure 1-15 Design Files Sidebar You can use the Filter field to specify which files appear in the list:? Enter a glob search pattern in the Field field. The file list is filtered as you type. Your filter expressions are saved in a drop-down list, so that you can easily re-apply the filter at a later time. Note: Using the tilde character (~) at the beginning of the filter pattern, shows all files and directories that do not match the specified pattern. For releases after 14.2, using a carot symbol (^) at the beginning of the filter pattern, makes the specified pattern case-sensitive. The default is case-insensitive.? Choose Filter file names or Filter directory names to specify whether the filter expression applies only to file names or directory names. To search for a string in the source files:? Click Search,, and SimVision opens the Design File Search window. Enter a search string, as described in Searching All Design Source Files on page 24. To display a file in the Source Browser window:? Click the file name in the file list. February Product Version 15.2

28 When it detects UVM objects in the design, SimVision adds a link in the Design Files sidebar, as shown in Figure 1-16 on page 28. Click this link to show or hide the UVM files. Figure 1-16 Design Files Sidebar with UVM Link Click to show or hide UVM files This link is synchronized with the Display UVM Base Classes preference in the Class Debug tab of the Preferences window. That is, when you enable the preference, UVM files are displayed in the Design Files sidebar, and when you click the link in the sidebar, it enables and disables the preference. Using Bookmarks in the Source Browser In the Source Browser, a bookmark saves the source file, line number, and scope displayed in the window. You can use the bookmark to restore the view at a later time. You create, rename, reorder, and delete bookmarks in the Bookmarks sidebar. Bookmarks are automatically saved when you exit SimVision and restored when you run SimVision again from the same design directory. February Product Version 15.2

29 By default, bookmarks are stored in a subdirectory of the working directory,./.simvision. However, if you want to share bookmarks among simulations that you run from many working directories, you can set a default bookmark directory, as follows: setenv SIMVISION_BOOKMARK_DIR directory The bookmarks are stored in $SIMVISION_BOOKMARK_DIR/.simvision, and they are restored from that location whenever you run SimVision. To create a bookmark from within the source code:? Right-click a scope, signal, or variable, and choose Bookmark This View. To open the Bookmarks sidebar: Click Bookmarks in the Source Browser sidebar, or choose View Manage Bookmarks from the menu bar. To create a bookmark in the Bookmarks sidebar:? Click Add a Bookmark,, in the sidebar, or choose View Add to Bookmarks from the menu bar. The Source Browser assigns a unique name to the bookmark, based on the source file name, line number, and scope. To rename a bookmark:? Double-click the bookmark to open a text area where you can edit the name; press Return to close the text area. To reorder the list of bookmarks:? Press and hold the middle mouse button over the bookmark, then drag the bookmark to a new location in the list. To delete a bookmark:? Select the bookmark and click Delete,. To return to a view that you have bookmarked:? Select the bookmark in the sidebar. The Properties window lists all of the bookmarks that you create. You can use the Properties window to rename and delete bookmarks. To manage Source Browser bookmarks in the Properties window: February Product Version 15.2

30 1. Click Properties,, in the Send To toolbar and select Bookmarks in the lefthand pane of the window, or click Display Bookmark Properties,, in the Bookmarks sidebar. 2. Select Source Browser in the Bookmarks tab of the Properties window. This displays the Source Browser bookmarks that you have created. 3. You can perform the following operations on bookmarks:? Double-click on a bookmark to edit its name.? Select one or more bookmarks and click Delete,, to delete the bookmarks.? Drag and drop bookmarks to change their order in the list.? Save your bookmarks by clicking Save,, and enter the name you want to give to the bookmark file. By default, bookmark files have the.svbk extension.? Load a bookmark file by clicking Load,, to load the bookmarks into your SimVision session. February Product Version 15.2

31 Running the Simulation with the Source Browser 2 The Source Browser lets you perform simulation functions, such as:? Setting breakpoints? Probing signals to a simulation database? Forcing and releasing signal? Depositing a value in a signal? Running the simulation During simulation, you can view the call stack in the Source Browser window. The call stack displays the calling sequence for Verilog, VHDL, and e code, and functions as a thread manager for SystemC processes. For More Information? Setting Breakpoints on page 31? Setting Probes on page 34? Forcing and Releasing a Signal Value in the Source Browser on page 34? Depositing a Signal Value in the Source Browser on page 35? Running the Simulation on page 35? Viewing the Call Stack on page 36 Setting Breakpoints The Source Browser provides shortcuts for setting line and signal breakpoints. You can set a breakpoint in any scope of the design, even if it is not the current scope. However, you cannot February Product Version 15.2

32 Running the Simulation with the Source Browser set a breakpoint on all lines of the source code. The Source Browser displays in black the line numbers for lines that can accept breakpoints; it displays in gray the line numbers for lines that cannot accept breakpoints. See Preparing Your Design for Simulation for information on making source line numbers available to SimVision To set a line breakpoint:? Double-click on the line number, or right-click a line number and choose one of the following pop-up menu entries: Break at Line Break at Line in Instance Break at Line in Object Same as double-clicking on the line number Applies to class objects only A red stop sign in the left column indicates that a breakpoint is set. You can set more than one type of breakpoint on the same line. However, the Source Browser displays only one stop sign. Hover the mouse pointer over the stop sign, and a tool tip shows you the breakpoints set on that line, as shown in Figure 2-1 on page 32. Figure 2-1 Line Breakpoint in the Source Browser To disable all breakpoints on a line:? Double-click on the line number or stop sign to disable all breakpoints set on the line. When disabled, the stop sign turns gray, as shown in Figure 2-2 on page 33. February Product Version 15.2

33 Running the Simulation with the Source Browser Figure 2-2 Disabled Line Breakpoint To disable or delete one or all breakpoints:? Right-click the breakpoint and choose one of the following pop-up menu entries: Delete all Breakpoints on Line <n> Disable all Breakpoints on Line <n> Delete Line Break in Instance Disable Line Break in Instance Delete Line Break in Object Disable Line Break in Object Delete Line Break Disable Line Break Applies to class objects only Applies to class objects only To set a signal breakpoint:? Select a signal and click Breakpoint,, or right-click and choose Break on Change. When you set a signal breakpoint, no breakpoint icon appears, but you can see the breakpoint definition in the Properties window, as described in Managing Breakpoints in the Properties Window. See Also? Setting and Managing Breakpoints February Product Version 15.2

34 Running the Simulation with the Source Browser Setting Probes The Source Browser provides the following shortcuts for setting probes:? Select an object and choose Send to Waveform Window from the pop-up menu. This menu choice performs the following operations:? Opens the default database, if you have not opened a default database already.? Sets a probe on the selected object.? Sends the object to the Waveform window. If a Waveform window is not opened, it opens one for you.? Select an object and choose Create Probe from the pop-up menu, or choose Simulation Create Probe from the menu bar. SimVision opens the Set Probe form, which you can use to create the probe. See Also? Creating and Managing Probes Forcing and Releasing a Signal Value in the Source Browser To force a signal to a particualr value: 1. Right-click over the signal or variable, thenchoose Set Force from the pop-up menu. The Source Browser opens the Force Value form. 2. In the Values field, specify the new value for the object. To release a force:? Right-click over the signal or variable, then choose Release Force from the pop-up menu. Se Also? Forcing and Releasing a Signal Value February Product Version 15.2

35 Running the Simulation with the Source Browser Depositing a Signal Value in the Source Browser To deposit a signal value:? Right-click over the signal or variable, then choose Deposit Value from the pop-up menu. See Also? Depositing a Signal Value Running the Simulation You can run the simulation from the Source Browser window, using either the simulation toolbar or the Simulation menu. If the current execution point is known, the Source Browser displays a yellow arrow next to the line of source code that is currently executing, as shown in Figure 2-3 on page 35. Otherwise, the arrow is displayed in gray at the last known execution point. Figure 2-3 Displaying the Current Execution Point The Source Browser may not know the current execution point for the following reasons:? For Verilog designs, it has stopped at the wire resolution phase of the simulation cycle.? For VHDL designs, it has stopped at the signal evaluation phase. February Product Version 15.2

36 Running the Simulation with the Source Browser If the current execution point is not displayed in the Source Browser window, you can quickly move to that point, by clicking Current Execution Point,, in the simulation toolbar. If the current execution point is not known, the Current Execution Point button is disabled. See Also? Controlling the Simulation Viewing the Call Stack Important This feature is available only in the target Source Browser window. Make sure you enable the target icon,, for the Source Browser window in which you want to view the call stack. During simulation, you can view the call stack in the Source Browser window. The call stack displays the calling sequence for Verilog, SystemVerilog, VHDL, and e code. It also functions as a thread manager for SystemC processes. For information on how to use this sidebar with SystemC, see Viewing the SystemC/C/C++ Call Stack in the SystemC Simulation User Guide. For information on how to use this tab with e, see Using the Source Browser with e Code. For Verilog, SystemVerilog, and VHDL, when simulation enters a task, function, process, or procedure, its name is added to the call stack. When the task, function, process, or procedure exits, its name is removed from the stack. If there is nothing on the call stack at the current execution point, the Source Browser displays (call stack empty). Note: For Verilog, the sidebar can display the call stack only for the currently executing task or function, and only if the debug scope is set to the scope in which it is executing. By default, the call stack is displayed at the bottom of the window, as shown in Figure 2-4 on page 37. Also by default, it displays only one line at a time. February Product Version 15.2

37 Running the Simulation with the Source Browser Figure 2-4 Call Stack at the Bottom of the Source Browser Window Call stack For More Information? Changing the Size of the Call Stack on page 38? Repositioning the Call Stack on page 38? Navigating the Call Stack on page 39? Using the Call Stack to Display Variables in the Source Browser on page 40 February Product Version 15.2

38 Running the Simulation with the Source Browser Changing the Size of the Call Stack To change the size of the call stack:? Drag the sash between the source area and the call stack area up (to make it larger), or down (to make it smaller). When you make the call stack larger, it displays navigation buttons, as shown in Figure 2-5 on page 38. Figure 2-5 Call Stack Navigation Buttons Call stack navigation buttons Repositioning the Call Stack To position the call stack in the Source Navigation sidebar: 1. Click the arrow,, in the upper left corner of the call stack, or disable View Callstack in Window, or press Ctrl-k. 2. Click the Call Stack tab,, in the sidebar to view the call stack. Tip If the sidebar is not visible, enable the Sidebar option in the View menu, then click the Call Stack tab. To return the call stack to the bottom of the window: February Product Version 15.2

39 Running the Simulation with the Source Browser? Click the arrow,, in the upper left corner of the Source Navigation sidebar, or enable View Callstack in Window, or press Ctrl-k. Navigating the Call Stack To move up the call stack:? Click Traverse Up,, choose View Callstack Up, or press Ctrl/Up arrow. To move down the call stack:? Click Traverse Down,, choose View Callstack Down, or press Ctrl/Down arrow. To jump to an arbitrary entry in the call stack:? Select the entry. When you select an entry in the call stack, the Source Browser points to its location in the source code. You can also position the call stack in the Source Browser sidebar, as shown in Figure 2-6 on page 40. February Product Version 15.2

40 Running the Simulation with the Source Browser Figure 2-6 Call Stack in the Source Browser Sidebar Using the Call Stack to Display Variables in the Source Browser The Call Stack window is a debugging tool that displays a list of functions, tasks, and procedures executed in the current process. You can use the call stack to view the values of local variables in those functions, tasks, and procedures. The call stack keeps track of the frames that are executed during a task or function call and lists each frame in the call stack window. Clicking the frames in the call stack displays the values of local variables, automatic variables, and parameters in the Source Browser. To use the call stack do the following: 1. Set a breakpoint on a signal in a task or function in the Source Browser. In Figure 2-7 on page 41, a breakpoint is set on line 7 in a task named myfunc. February Product Version 15.2

41 Running the Simulation with the Source Browser Figure 2-7 Setting a Breakpoint Set a breakpoint. 2. Run the simulation to the breakpoint and display the call stack by clicking the call stack tab, shown in Figure 2-8 on page 41. When you break on a task or function call, the call stack displays the frames that have executed. In the following figure, the call stack window is displaying two frames called by the myfunc task. Figure 2-8 Displaying the Call Stack The current frame Call stack tab Call stack area 3. Enable value annotation to display the variable values. When you enable value annotation, the values displayed in the source file are for the current frame. This lets you see the values of parameters being passed to methods, and to view the value of automatic variables and local variables in the selected frame. As you click each frame in the call stack, the corresponding line in the source file is highlighted. In the following figure, the frame my_mod is selected, and the value of the variable is shown above the highlighted source file line. February Product Version 15.2

42 Running the Simulation with the Source Browser Figure 2-9 Viewing Variable Values Enables value annotation The selected frame Annotated variable value February Product Version 15.2