Related Manuals for Renesas TM V.3.20A
Summary of Contents for Renesas TM V.3.20A
- Page 1 TM V.3.20A Integrated Development Environment User’s Manual Rev. 1.00 May 01, 2003 REJ10J0018-0100Z...
- Page 2 These materials are intended as a reference to assist our customers in the selection of the Renesas Technology product best suited to the customer's application; they do not convey any license under any intellectual property rights, or any other rights, belonging to Renesas Technology Corporation, Renesas Solutions Corporation or a third party.
-
Page 3: Table Of Contents
Contents 1. Introduction 1.1 Operating Environment 1.2 Installation Method 1.2.1 Executing the Installer 1.2.2 Notes about TM Versions 1.2.3 Compiler and real time OS Combinations 1.2.4 Directories and Files Generated After Installation 1.3 Usage Precautions 1.3.1 Notes about File Names 1.3.2 Notes about Updating of Dependency Relations 1.3.3 Notes about Utility Software such as Virus Check Program 1.3.4 Notes about Network... - Page 4 4.1 Project Bar 4.1.1 Overview 4.1.2 Buttons 4.1.3 Menus 4.1.4 Dialog Boxs 4.1.4.1 Tools Information Dialog Box... 44 4.1.4.2 Customize Dialog Box... 47 4.1.4.3 Debug Tool Information Dialog Box... 50 4.1.4.4 Edit Tool Information Dialog Box... 51 4.1.4.5 Application Tool Information Dialog Box... 53 4.1.4.6 Current Directory Dialog Box ...
- Page 5 4.2.3.24 Online Manual ... 77 4.2.3.25 About Project Editor ... 78 4.3 Builder 4.3.1 Overview 4.3.2 Builder Window 4.3.3 Functional Description 4.3.3.1 To Execute Build ... 80 4.3.3.2 To Stop Building in the Middle ... 80 4.3.3.3 To Reexecute Previous Build... 80 4.3.3.4 To Jump to a Location in Error or Warning...
- Page 6 Figures Fig. 2-1 Example of Software Development Using the TM ... 17 Fig. 2-2 Project Name... 18 Fig. 2-3 Conceptual Diagram of the TM ... 19 Fig. 2-4 Project Bar ... 19 Fig. 2-5 Project Editor ... 20 Fig. 2-6 Builder... 20 Fig.
- Page 7 Fig. 4-3 EDITOR TOOL tab ... 45 Fig. 4-4 APPLICATION tab... 46 Fig. 4-5 Customize Dialog Box ... 47 Fig. 4-6 Setting tab ... 47 Fig. 4-7 Button tab... 48 Fig. 4-8 Inspector tab... 49 Fig. 4-9 Debug Tool Information Dialog Box ... 50 Fig.
- Page 8 Fig. 4-51 Inspector Startup Buttons... 84 Fig. 4-52 Specify Detail Conditions Dialog Box... 85 Fig. 4-53 Rearrange Entries... 87 Fig. 4-54 [Update] button ... 88 Fig. 4-55 Environment Setup Dialog Box (Action Tab)... 89 Fig. 4-56 Environment Setup Dialog Box (Preview Tab) ... 89...
-
Page 9: Introduction
1.1 Operating Environment The following lists the host computers and OS versions on which TM has been verified to run. Host Computer IBM PC/AT or compatible Note that the TM does not run on Windows 3.1, Windows NT 3.51 or earlier, and EWS. If your host computer or OS is not one of the above, please contact the manufacturer of your computer or OS to confirm whether the software running under the above conditions will also work on the computer and OS that you now have. -
Page 10: Installation Method
When you are installing the TM over an existing version of TM, the installer displays a message to that effect. To install TM V.3.20A on the same PC that has the version before V.2.xx already installed in it, specify a new directory to install, and not the directory in which the earlier version is installed. -
Page 11: Directories And Files Generated After Installation
1.2.4 Directories and Files Generated After Installation When you finished installing the TM, the directories shown below are created in the directory in which you’ve installed the TM, and the files listed below are copied into these directories. Directory manual Furthermore, the following files are copied into the directory where the OS is installed. -
Page 12: Usage Precautions
1.3 Usage Precautions 1.3.1 Notes about File Names The source program file names and work directory names are subject to the following limitations: No directory or file names that include kanji (2-byte characters) can be used. Only one instance of the period (.) can be used in a file name. No network path names can be used. -
Page 13: Makefile Of Library Source
1.3.6 Makefile of library source. A project can’t make it normally when makefile.dos of the compiler accessory is read with TM. Carry out Make in accordance with User’s Manual of the compiler from the Dos window when you change standard input and output library. -
Page 14: In The Case Of Mr79 (For 7900 Series)
When 16 was specified in the message size or designation was omitted. Compilation option Link library <Example> system { message_size = 16; When you put the source file of C besides “Working Directory” (.\). Compilation option When you put the assembler source file besides “Working Directory” (.\). Assembly option When you specify the output destination of the objects besides “Working Directory”... -
Page 15: In The Case Of Mr7700 (For 7700 Series)
When 16 was specified in the message size or designation was omitted, and STANDARD was specified in the interruption prohibition model or designation was omitted. Compilation option Link library <Example> system { message_size = 16; interrupt_model = STANDARD; When 16 was specified in the message size and or designation was omitted, and SHORT was specified in the interruption prohibition. -
Page 16: In The Case Of Mr32R (For M32R Series)
When 24 was specified in the message size and SHORT was specified in the interruption prohibition model. Compilation option Link library <Example> system { message_size = 24; interrupt_model = SHORT; When 16 was specified in the message size or designation was omitted, and STANDARD was specified in the interruption prohibition model or designation was omitted. -
Page 17: Overview
2.1 Integrated Development Environment The Integrated Development Environment, TM, has been devised to increase the efficiency of software development by integrating various tools such as the compiler, assembler, debugger, and editor into a common Graphical User Interface (GUI). The TM has the following three primary functions: Manages the software development process using the concept of a project Provides a seamless environment as a common GUI for various tools Based on static program analysis, supports problem identification and reverse engineering needed during... -
Page 18: Concept Of A Project
2.2 Concept of a Project The TM manages the software development process using the concept of a project. Following are managed as part of a project by the TM: Procedural information necessary to generate the final object (normally the executable object) Information on source files associated with development Information on compile, etc. -
Page 19: Roles Of Each Tool Working Under The Tm
Edit Source File Makefile Read Those included in TM V.3.20A ■ Project Bar The project Bar plays the central role of the TM, helping to accomplish a linked startup of each tool. To start the TM, you start the Project Bar. To exit the TM, you close the Project Bar. -
Page 20: Fig. 2-5 Project Editor
■ Project Editor Use the Project Editor to define or alter the source files, compile options, or generation procedure included in a project. The Project Editor works as an editor for the “makefile” handled by the GNU Make command. ■ Builder The Builder invokes the GNU Make command to build a project based on the “makefile (TMK file)”... -
Page 21: Fig. 2-7 Inspector
■ Inspector The Inspector provides a facility that based on the debug information included in the “absolute object file” generated by build, analyzes the locations where functions and variables are defined or referenced. Unlike a simple string search, the Inspector does the search based on the information embedded by the compiler. advantages accrue: Comments and other non-compiled parts are not searched Can be searched separately for references and definitions... -
Page 22: Fig. 2-8 Map Viewer
The Map Viewer allows you to examine memory mapping. When you are using other Renesas compiler products or some version of compilers other than these versions, you cannot use TM V.3.20A. In such a case, please use TM V2.01. Note that TM V.3.20A and TM V2.01 can coexist, so you can use either version as necessary. -
Page 23: Fig. 2-9 Stk Viewer
Any editor available on the market and you are accustomed to may be used after registering it to the TM. ■ Debugger In addition to the PDxx series debuggers available from Renesas, any third-party debugger may be used after registering it to the TM. The STK Viewer is included in the package as a Java installed in the \install directory \BIN directory when installing the compiler. -
Page 24: Directory Configuration
2.4 Directory Configuration This section describes how to configure the directory structure of the program when using the TM. When thinking of the directory structure, it is important to understand the exact meaning of the “working directory” and the form in which the source files registered to the project are entered “internally”... - Page 25 Example of a directory structure With the above concept taken into account, a directory structure like the one shown below may be conceived. C:\WORK \ModelA \ModelB \SRCA \SRCB \COMMON \HEAD G:\COMMON In this example, separate working directories, one for model A and one for model B, are prepared, in which a project is worked on.
-
Page 26: Quick Tour
3.1 Starting the TM and Registering the Editor Used When the TM has been installed normally, the TM can be started by selecting [Start] -> [Programs] -> [RENESAS- TOOL] -> [TM V.3.xx] -> [TM] from the Start menu. When the TM starts up, the Project Bar appears. -
Page 27: Fig. 3-4 Registering An Editor
The TM allows any editor available on the market to be registered for use in it. The Peggy editor has its trial use version included in the “Compilers and Assemblers” CD-ROM from Renesas. Or it can be purchased from the URL shown below. -
Page 28: Creating A Project
3.2 Creating a Project There are following three methods to create a project: Create a new project Read a project file of TM V2 or earlier version (MTM file) and convert it into TM V3 format project files Read an existing makefile and add additional information to create a project Because the TM can read in existing makefiles, a project can easily be created even when you are conventionally not using the TM. -
Page 29: Fig. 3-7 New Project Wizard (Step 2)
Choose the target chip and set a project name and the working directory. Fig. 3-7 New Project Wizard (Step 2) Next, choose the type of project. Fig. 3-8 New Project Wizard (Step Compiler) -
Page 30: Fig. 3-9 New Project Wizard (Step Finish)
Choose [A default startup program is used.] for the startup program, and the startup program that comes standard with the compiler is copied into the working directory. Click [Finish] on the above dialog box, and the basic project information is created. Registering files When the TM has finished creating initial project information, the Project Editor window appears. -
Page 31: Fig. 3-11 Example Of A Project
executed. If main.r30 is created from main.c, for example, write a statement as shown below. main.r30 : main.c nc30 -c main.c In such a case, display on the Project Editor should appear like the one shown below. Show command information on a selected file (item) on the right side of the window. The information will be displayed as shown above. -
Page 32: Fig. 3-12 Adding A File
Now, we’ll try adding a file to the project. Choose the final object and then [Add file] from the right-click menu. Choose the file to add. Before you can create the final object file “ModelA.x30,” you must have “main.r30” registered in your project. The TM knows the dependency relationship between “.C”... -
Page 33: Fig. 3-14 View After Registering Source Files
In this example, when you register “main.c,” the TM registers “main.r30” simultaneously with it, producing the following display. When you register the source files, be sure to choose basically the final object (absolute object). The file may be registered for other items. In such a case, consider the relationship between target and dependencies in the “makefile” of the GNU make command as you work on file registration. -
Page 34: Fig. 3-17 Option Setup Dialog Box
Definitions of the following are entered by default for each option, respectively: Compiler (nc30) Assembler (as30) Linker (ln30) Load module converter (lmc30) “CFLAGS” is a makefile macro, which defines the options used when compiling a program. Choose “CFLAGS” and press the [Mod] button, and the dialog box shown below appears. Use this dialog box to choose the options you want to choose. -
Page 35: Fig. 3-18 Creating A New Macro
Or when you want to use different compile options for each file, choose “nc30” press the [New] button. This creates a new macro named “CFLAGS1.” Choose options for this new macro and then the file for which you want the macro to be applied. -
Page 36: Fig. 3-21 Button For Adding Documents
Registering documents Specifications and other documents can be registered. For example, when you register development members and documents, the registered information can be displayed on a project view as shown below. Also, you can send a mail to a member or open a document by double-clicking on it. Fig. -
Page 37: Building A Project
3.3 Building a Project The Project Editor is an editor. Therefore, if the project has been changed, it must be saved before building. To save a project, press the [Save] button on the Project Editor. Next, press the [Build] button on the Project Bar. This invokes the Builder, and the Builder starts building the project. -
Page 38: Fig. 3-27 Buttons For Using The Inspector
Analyzing with the Inspector The Inspector allows for static program analysis by reading into it the final object “ModelA.x30” that has been built. Use one of the Project Bar buttons shown below to start the Inspector. The Inspector performs functional analysis on the string which is entered in the String box by Copy & Paste. For example, when you want to find locations where a variable system_code is used in the program, first enter that string into the String box on the Project Bar by Copy &... -
Page 39: Fig. 3-30 Showing Variable References
In this example, system_code is used in five locations. The variable can be previewed in the window located below by selecting one instance of system_code. (The variable cannot be edited in this window. Double-click the variable location you want to select, and the editor starts up.) The square boxes on the left side of the list are check boxes which can be used in place of a memo. -
Page 40: Fig. 3-32 Showing Function References
Choose the Debugger to use from this dialog box by checking it. When you are using the PD Debugger available from Renesas, choices to select are listed. When you are using a third-party debugger, press the [Add..] button and register the necessary items. -
Page 41: Reference Manual
4.1 Project Bar 4.1.1 Overview The Project Bar plays the central role of the TM. It accomplishes a linked invocation of each tool. To start the TM, start the Project Bar. To exit the TM, close the Project Bar. The Project Bar has the following functions: Start the Project Editor Start/register a debugger Start/register an editor... -
Page 42: Buttons
Detail Setup Button Specify the contents to be displayed on the Inspector. Stk Viewer Start Button Starts the STK Viewer included with Renesas compilers. The STK Viewer shows the amount of stack used. Map Viewer Start Starts the Map Viewer included with Renesas compilers. The Map Viewer... -
Page 43: Menus
Registers a debugger. Registers an editor. Registers an application. Starts the utility included with Renesas compilers. The Execute Utility dialogbox opens when you select a sub-menu. Please input a parameter of the utility in the dialog box. Shows help for the TM. -
Page 44: Dialog Boxs
Use the DEBUG TOOL tab to register a debugger and select the debugger that starts up when you press the debug button. The debuggers available from Renesas are automatically added to the debugger list according to the project files loaded. When you are using a third-party debugger, use the Add button to register it. -
Page 45: Fig. 4-3 Editor Tool Tab
Debugger List Shows registered debuggers. The user-registered debuggers are shown as “user:xxxx.” The debugger which has its check box checked is the debugger used in the current project. The debugger to use can be changed by clicking the check box of another debugger. Add button Adds a debugger. -
Page 46: Fig. 4-4 Application Tab
■ APPLICATION tab Use the APPLICATION tab to register an application and select the editor to use in the TM. A button for starting the registered application is added to the Project Bar. Application list Shows registered applications. Add button Adds an application. -
Page 47: Customize Dialog Box
4.1.4.2 Customize Dialog Box The Customize dialog box is provided for changing various settings of the Project Bar. From this dialog box, the following can be set: To show the Project Bar... To change buttons... For Inspector-related settings... ■ Setting tab Use the Setting tab to set the behavior of the Project Bar. -
Page 48: Fig. 4-7 Button Tab
■ Button tab Use the Button tab to show or hide each button on the Project Bar and change the order in which they are displayed. Button display view Check the check box of a button, and the button is displayed. Uncheck a button, and the button goes out. Upper button Moves the selected button on the list view one place forward. -
Page 49: Fig. 4-8 Inspector Tab
■ Inspector tab Use the Inspector tab to set Inspector-related settings. Auto Read from Clipboard Selects whether or not to automatically copy a copied string from the clipboard into the Inspector’s search string display box. Fig. 4-8 Inspector tab... -
Page 50: Debug Tool Information Dialog Box
4.1.4.3 Debug Tool Information Dialog Box The Debug Tool Information dialog box is provided for registering a debugger. ■ Name (essential) Enter a debugger name. ■ File Path (essential) Enter a path to the debugger’s execution file. The file can also be selected by clicking the Browse button. ■... -
Page 51: Edit Tool Information Dialog Box
4.1.4.4 Edit Tool Information Dialog Box The Edit Tool Information dialog box is provided for registering an editor. ■ Name (essential) Enter an editor name. ■ Default Editor check box Check this check box, and the editor you are registering is registered as the default editor to be used by the TM. When this button is unchecked, the editor is only registered. - Page 52 ■ Environment field This shows environment variables used by the editor. ■ Add button Click this button when you want to add an environment variable. The Environment Settings dialog ■ Delete button To delete any environment variable, select it from the list and click the Delete button. ■...
-
Page 53: Application Tool Information Dialog Box
4.1.4.5 Application Tool Information Dialog Box The Application Tool Information dialog box is provided for registering an application. ■ Name (essential) Enter an application name. ■ File Path (essential) Enter a path to the application’s execution file. The file can also be selected by clicking the Browse button. ■... - Page 54 ■ Modify button To modify any environment variable, select it from the list and click the Modify button. The Environment Settings dialog box opens. ■ OK button Click the OK button, and the contents you changed are reflected before closing the Application Information dialog box.
-
Page 55: Current Directory Dialog Box
4.1.4.6 Current Directory Dialog Box The Current Directory dialog box is provided for specifying the runtime directory. ■ Directory that contains the execution file The directory that contains the execution file of the tool to start is made the current directory. ■... -
Page 56: Environment Settings Dialog Box
4.1.4.7 Environment Settings Dialog Box The Environment Settings dialog box is provided for specifying environment variables. ■ Name (essential) Enter an environment variable name. ■ Value Specify the value of the environment variable. ■ OK button Click the OK button, and the contents you changed are reflected before closing the Environment Settings dialog box. ■... -
Page 57: Utility Execute Dialog Box
4.1.4.8 Utility Execute Dialog Box The Utility Execute Dialog Box starts the utility. ■ Parameter Specify the options for the utility. You can also use the Browse button to select the desired file path. ■ Detail For the automatically TM recognized tools, the Detail button is available. When you click on this button, the Option Settings dialog box appears, allowing you to set options. -
Page 58: Option Settings Dialog Box
4.1.4.9 Option Settings Dialog Box The Option Settings Dialog Box set a utility’s option. Choose an option you want to specify by checking its check box. If the option requires specifying one or more parameters, a Specify Parameter dialog box is displayed. From this dialog box, specify the necessary parameters. -
Page 59: Project Editor
4.2 Project Editor 4.2.1 Overview The Project Editor is a window in which you can view and edit a project. Use the Project Editor to define or change the source files or compile options or the project generation procedure included in the project. The Project Editor functions as an editor for makefiles handled by the GNU Make command. -
Page 60: Menus
4.2.2.1 Menus The Project Editor has the following menus available. ■ File menu The File menu has assigned to it the menu commands to load or save a project file or makefile, exit the Project Editor, and perform other file-related operations. Menu Menu command File (F) -
Page 61: Status Bar
■ Help menu The Help menu has assigned to it the menu commands to show the method for using the Project Editor or its version information. Menu Menu command Help (H) Help (H) Online Manual (M) About Project Editor(A) 4.2.2.2 Toolbar The toolbar has various buttons arranged on it that facilitate execution of frequently used commands. -
Page 62: Generation Procedure View
4.2.2.4 Generation Procedure View The generation procedure view shows information on project generation procedure (dependency relationship) in tree form. Shown below is an outline diagram of the generation procedure view. 4.2.2.5 Item Information View The item view shows detail information about the item selected on the generation procedure view. Shown below is an outline diagram of the item information view. -
Page 63: Document View
4.2.2.7 Document View The document view shows information about the documents. Shown below is an outline diagram of the document view. Fig. 4-21 Document View... -
Page 64: Method Of Operation
4.2.3 Method of Operation 4.2.3.1 Creating a New Project Create a new project. When you choose this menu command, a New Project dialog box appears. The New Project dialog box is a wizard- type dialog box. From this dialog box, set the necessary entries sequentially. From Target chip:, choose the target MCU for which you are creating a project. -
Page 65: Fig. 4-24 New Project - Step Compiler
Here, choose the type of project. When you finished selecting the type of project, click the [Next (N)] button. New Project - Step Compiler is displayed. Fig. 4-24 New Project - Step Compiler From Compiler package:, choose the compiler you use. An already installed product is automatically displayed in the [Compiler package] text box. -
Page 66: Fig. 4-25 New Project - Step Os
If you selected [ASM Project,] [C Project,] [Library Project,] or [Free Project] for the project type in New Project Step 2, you are brought to New Project Step - Complete. If you selected [Realtime OS + ASM Project] or [Realtime OS + C Project], New Project - Step OS is displayed. In this case, specify the startup program in New Project - Step OS. -
Page 67: Opening A Project
When you finished setting all entries on the New Project dialog box, the contents you’ve set are displayed here. If the contents shown here are correct, click the [Finish (F)] button. If incorrect, click the [Back (B)] button and reedit any entries that need to be corrected. 4.2.3.2 Opening a Project Open an existing project file. -
Page 68: Saving The Project By Specifying A Name
4.2.3.4 Saving the Project by Specifying a Name Save the project being worked on to another project file by specifying a file name. When you choose this menu command, a Save As dialog box is displayed. Specify any file name and folder in which you want to save the project. -
Page 69: Exiting The Application
A history of up to four projects is displayed. 4.2.3.7 Exiting the Application Exit the Project Editor. If the project being worked on has been edited, a message is displayed asking you to confirm whether or not to save. To save the project before closing it, click the [Yes] button. To close the project without saving it, click the [No] button. -
Page 70: Command
Specify the file name you want. Two or more file names can be specified. (File names can be specified in up to about 2,600 characters assuming that they are indicated with the absolute path.) Even a nonexistent file name can be specified. If the specified file has the same extension as that of the compiler or assembler’s default extension, the file is recognized as a source file and has the compiler or assembler’s execution code automatically added as a command. -
Page 71: Open
For Command, enter a command. The [Def macro ->] button adds a macro displayed by a macro browser to the command line. The [Dyn macro ->] button adds a special macro defined by make to the command line. Click the button, and a popup menu appears. -
Page 72: Properties
4.2.3.14 Properties Show properties of an item. Choose this menu command when an item on the generation procedure view is selected. A File Properties dialog box is displayed. Properties are displayed only when an existing file is specified. If necessary, edit Attributes. 4.2.3.15 Partial Build Build an item selected on the generation procedure view. -
Page 73: Macro Browser
4.2.3.17 Macro Browser Show a macro browser. When you choose this menu command, a Macro Browser dialog box is displayed. This dialog box shows a list of macros used in the project’s generation procedure. To add a new macro, click the [New] button. An Add Macro dialog box is displayed. The new macro is added below the last line of existing macros. -
Page 74: Option Browser
4.2.3.18 Option Browser Show an option browser. When you choose this menu command, an Option Browser dialog box is displayed. This dialog box shows a list of options used in the project’s generation procedure. To add a new option, choose the tool name you want to add and click the [New] button. An Option dialog box is displayed. -
Page 75: Adding Member Information
Choose an option you want to specify by checking its check box. If the option requires specifying one or more parameters, a Specify Parameter dialog box is displayed. From this dialog box, specify the necessary parameters. 4.2.3.19 Adding Member Information Add member information to the project. -
Page 76: Adding A Document
4.2.3.20 Adding a Document Add a document file to the project. When you choose this menu command, an Open File dialog box is displayed. Specify the document file you want to add to the project. When you choose a registered document file and then execute Open, the file is executed by the application associated with it by Windows. -
Page 77: Scan All Dependencies
This dialog box shows information on the project being worked on. With the Tool tab, you can specify whether or not to use any tool, such as a load module converter, not just normally used tools. To specify to use a tool, check its check box. The checked tool is displayed on the option browser. -
Page 78: About Project Editor
4.2.3.25 About Project Editor Show version information of the Project Editor. When you choose this menu command, a Project Editor Version Information dialog box is displayed. Fig. 4-45 Showing Project Editor Version This dialog box allows you to verify the version of the Project Editor. -
Page 79: Builder
4.3 Builder 4.3.1 Overview Builder is the window which does the practice of build and result indication. An error and warning place are indicated with the mark, and help and text editor can start it. 4.3.2 Builder Window Fig. 4-46 Builder Window... -
Page 80: Functional Description
4.3.3 Functional Description 4.3.3.1 To Execute Build The build operation can be executed in three ways: Build only the files selected with the Project Editor, build the entire project, or rebuild the entire project. For details on how to run, refer to the description of the Project Bar in earlier sections of this manual. -
Page 81: To Examine The Meaning Of An Error Or Warning
4.3.3.5 To Examine the Meaning of an Error or Warning Right-click the error or warning line to open a submenu and choose [Search for Help On] from that submenu. Help for the cross tool is invoked, with the error message entered in the keyword text box. Choose a keyword string from the list. Click the [View] button on the dialog box to verify the content of the error message. -
Page 82: To Search For An Error Or Warning
4.3.3.9 To Search for an Error or Warning When an error or warning occurs, it can be searched for in the upward or downward direction from the cursor position. You can search by error, by warning, or by error & warning. Furthermore, when the end of the file is reached during search, you can start searching from the beginning of the file again, by setting up environment settings accordingly. -
Page 83: To Change Operation Environment
4.3.3.12 To Change Operation Environment Choose [Action] - [Environment] from the menu bar. The Setting tab of the Environment dialog box allows you to set the following. Restore window condition The window position is restored next time the Builder starts up. Restore font The display font is restored next time the Builder starts up. -
Page 84: Inspector
4.4 Inspector 4.4.1 Overview Inspector is the window which indicates function information and variable information. Information on the made object is analyzed statically in the cause. Each information is classified with the tab, and indicated respectively in the list. A file name and a line number are outputted by each information, and it is possible that it opens with text editor. 4.4.2 Inspector Window 4.4.3 Starting the Inspector Use the Project Bar to start the Inspector and display various information. -
Page 85: To Show Information List
4.4.3.1 To Show Information List Click on either "Show function definition", "Show function reference", "Show variable definition ", " Show variable reference " on the project bar. The indication tab of the button which it clicked on becomes active. When a function or variable name are specified with [Insp:] box, a focusing tab is indicated, and only the information which corresponded to the specified name is indicated. -
Page 86: List Window
■ Specifying the type Selectable entries All types, signed int, unsigned int, signed char, unsigned char, signed short, unsigned short, signed long, unsigned long, float, double, void pointer, struct, union, enum, typedef, func, near pointer, far pointer, array, void ■ Specifying the storage class Selectable entries Not specify, global, static, inline... -
Page 87: To Check A Check Box
4.4.4.3 To Check a Check Box If, while a line mark area is displayed and any entry is selected, the focus is located in the list window, the check box for an entry can be checked or unchecked by one of the following operations performed. Checking from the menu bar Choose [Action] - [Set Line Select Mark] from the menu bar. -
Page 88: To Reanalyze After Loading The Latest Object
4.4.4.7 To Reanalyze after Loading the Latest Object If the object or project has been altered, the [Update] button on the toolbar is enabled. Click the [Update] button, and the Inspector loads the latest object and reanalyzes the project under the previous analysis conditions. 4.4.5 Preview Window 4.4.5.1 To Search for a String When the focus is located in the preview window, a Search for String dialog box is displayed by one of the following... -
Page 89: Action Tab
4.4.6.1 Action Tab ■ Restore window condition Restores the window position the next time the TM starts. ■ Restore font Restores the display font the next time the TM starts. ■ Auto set line mark Automatically checks line marks when opening the editor from the Inspector. ■... - Page 90 MEMO...
- Page 91 TM V.3.20A User’s Manual Rev. 1.00 May 01, 2003 REJ10J0018-0100Z COPYRIGHT ©2003 RENESAS TECHNOLOGY CORPORATION ALL RIGHTS RESERVED AND RENESAS SOLUTIONS CORPORATION ALL RIGHTS RESERVED...