REJ10J0768-1000 E8 Emulator User's Manual R0E000080KCE00E Renesas Microcomputer Development Environment System Rev.10.00 Aug.
Notes regarding these materials 1. This document is provided for reference purposes only so that Renesas customers may select the appropriate Renesas products for their use. Renesas neither makes warranties or representations with respect to the accuracy or completeness of the information contained in this document nor grants any license to any intellectual property rights or any other rights of Renesas or any third party with respect to the information in this document. 2.
Introduction This manual describes the followings - E8 Emulator functions - Preparation before use - Debugger functions - Tutorial - Appendix: (Components of the E8 Emulator, Notes on High-performance Embedded Workshop, and Diagnostic Test Procedure) This manual does not intend to explain how to write C/C++ or assembly language programs, how to use any particular operating system or how best to tailor code for the individual devices. These issues are left to the respective manuals.
Document Conventions This manual uses the following typographic conventions: Table 1 Typographic Conventions Convention Meaning [Menu->Menu Option] Bold text with ‘->’ is used to indicate menu options (for example, [File->Save As...]). FILENAME.C Uppercase names are used to indicate filenames. “enter this string” Used to indicate text that must be entered (excluding the “” quotes). Key + Key Used to indicate required key presses.
IMPORTANT READ FIRST Before using this product, be sure to read the user’s manual (this user's manual) carefully. Keep this user’s manual, and refer to this when you have questions about this product. Emulator: The emulator in this document refers to the following products that are manufactured by Renesas Technology Corp.: (1) Emulator (2) User system interface cable The emulator herein does not include the customer’s user system and host machine.
Usage restrictions: This emulator has been developed as a means of supporting system development by users. Therefore, do not use it as a device used for equipment-embedded applications.
Precautions for Safety READ FIRST Before using this product, be sure to read the user’s manual (this user's manual) carefully. Keep this user’s manual, and refer to this when you have questions about this product.
DEFINITION OF SIGNAL WORDS Be sure to read and understand the warnings below before using this emulator. Note that these are the main warnings, not the complete list. This is the safety alert symbol. It is used to alert you to potential personal injury hazards. Obey all safety messages that follow this symbol to avoid possible injury or death. DANGER WARNING CAUTION CAUTION DANGER indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.
WARNING 1. Do not repair or remodel the emulator product by yourself for electric shock prevention and quality assurance. 2. Always switch OFF the host computer and user system before connecting or disconnecting any CABLES or PARTS. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator product or will result in PERSONAL INJURY. The USER PROGRAM will be LOST. 3.
Contents Contents 1 Section 1 Overview........................................................................................... 1 1.1 1.2 1.3 Warnings ...........................................................................................................................3 Environmental Conditions ................................................................................................4 Components .................................................................................................
5.2 5.3 5.4 5.5 5.1.1 Opening the [Configuration] Dialog Box ............................................................ 71 5.1.2 [General] Page ..................................................................................................... 72 Downloading a Program ................................................................................................... 74 5.2.1 Downloading a Program ...................................................................................... 74 5.2.
5.6 Using the Start/Stop Function................................................................................................89 5.6.1 Opening the [Start/Stop Function Setting] Dialog Box........................................89 5.6.2 Specifying the Routine to be Executed ................................................................89 5.6.3 Restrictions on the Start/Stop Function................................................................91 Section 6 Tutorial.....................................
E.1. E.2. E.3 System Setup to Execute the Check Program ................................................................... 143 Executing the Check Program........................................................................................... 143 When an Error Occurs.......................................................................................................
Section 1 Overview The High-performance Embedded Workshop is a Graphical User Interface intended to ease the development and debugging of applications written in C/C++ programming language and assembly language for Renesas microcomputers. Its aim is to provide a powerful yet intuitive way of accessing, observing and modifying the debugging platform in which the application is running.
The emulator has three activation modes: (1) A mode in which the emulator program is started after it has been downloaded to the target device: This mode is used when there is no emulator program in the flash memory of the target device. (2) A mode in which the emulator program is started without downloading it to the target device: This mode is used when there is an emulator program in the flash memory of the target device.
1.1 Warnings CAUTION READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. (1) Check all components against the component list provided at the side of the component box after unpacking the emulator. (2) Never place heavy objects on the casing. (3) Protect the emulator from excessive impacts and stresses. For details, refer to section 1.2, Environmental Conditions.
1.2 Environmental Conditions CAUTION Observe the conditions listed in tables 1.1 and 1.2 when using the emulator. Failure to do so will cause illegal operation in the user system, the emulator product, and the user program. Table 1.1 Environmental Conditions Item Specifications Temperature Operating: +10°C to +35°C Storage: –10°C to +50°C Humidity Operating: 35% RH to 80% RH, no condensation Storage: 35% RH to 80% RH, no condensation Vibration Operating: 2.45 m/s2 max. Storage: 4.9 m/s2 max.
1.3 Components Check all the components unpacking. For details on the E8 emulator components, refer to the component list provided at the side of the component box. If the components are not complete, contact our E-mail address for user registration or refer to the web site.
6
Section 2 E8 Emulator Functions This section describes the emulator functions. They differ according to the device supported by the emulator. 2.1 Overview Table 2.1 gives a functional overview of the emulator. Table 2.1 Emulator Functions No. Item 1 User program execution function Function • Executes a program with the operating frequency within a range guaranteed by devices.
Table 2.1 Emulator Functions (cont) No. 5 Item Memory access function Function • Downloading to RAM • Downloading to flash memory • Single-line assembly • Reverse assembly (disassembly) • Reading of memory • Writing to memory • Automatic updating of a display of selected variables during user program execution • FILL • Search • Move • Copy 6 General/control register access function Reads or writes the general/control register.
2.2 Trace Functions The branch source addresses, mnemonics, operands, and source lines are displayed. Since this function uses the trace buffer built into the device, a realtime trace can be acquired. Note: The MCUs which have no trace function cannot use this function.
2.3 Break Functions The E8 emulator has the following four break functions. (1) Hardware break function H8 R8C series Uses a break controller incorporated in the device. The access address, instruction fetch address, data, or bus cycle condition can be set. This function can also be set from the [Event] column in the [Source] window. For the setting, refer to section 5.3.1 Address Interrupt Breakpoints. Note: The MCUs which have no hardware break function cannot use this function.
2.4 Memory Access Functions The emulator has the following memory access functions. (1) Memory read/write function [Memory] window: The memory contents are displayed in the window. Only the amount specified when the [Memory] window is opened can be read. If the memory is written in the [Memory] window, a read in the range displayed in the [Memory] window will occur for updating the window. When the [Memory] window is not to be updated, change the setting in [Lock Refresh] from the popup menu.
(6) Other memory operation functions Other functions are as follows: • • • • • • • Memory fill Memory copy Memory save Memory verify Memory search Internal I/O display Displaying label and variable names and their contents Notes: 1. Memory access during user program execution: When memory is accessed from the memory window, etc. during execution of the user program, execution stops for the memory access and is then resumed. Therefore, realtime emulation cannot be performed. 2.
Section 3 Preparation before Use 3.1 Emulator Preparation Unpack the emulator and prepare it for use as follows: WARNING READ the reference sections shaded in Figure 3.1 before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. Reference Unpack the emulator Check the components against the component List provided at the side of the component box . Set up the emulator When the emulator is used first.
14
3.2 Emulator Hardware Configuration As shown in Figure 3.2, the emulator consists of an emulator, a USB cable, and a user system interface cable. The emulator is connected to the host computer via USB 1.1, and also to the USB port conforming to USB 2.0. Figure 3.
The names of each section of the emulator are explained next. Emulator Upper-side Panel: (a) (d) (c) (e) (b) Figure 3.3 Emulator Upper-side Panel (a) E8 logo plate: A pink plate dedicated for the emulator is provided to be easily distinguished from other E-series emulators. (b) Sliding switch cover: A cover to protect a switch for setting the emulator, which is closed to prevent incorrect operation. Be sure to close this cover during emulation. (c) ACTION LED: Marked ‘ACT’.
Emulator Host-side Panel: (a) Figure 3.4 Emulator Host-side Panel (a) Host-side connector: A USB connector for the host computer. Be sure to connect the provided USB cable. Emulator User-side Panel: (a) Figure 3.5 Emulator User-side Panel (a) User-side connector: A user system interface cable is connected.
Emulator Bottom Panel: (a) Figure 3.6 Emulator Bottom Panel (a) Seal for product management: The serial number, revision, and safety standard, etc. of the emulator are written to. The contents differ depending on the time when you purchased the product.
3.3 Emulator Software Configuration The following item is included with the emulator debugger when it is purchased: • E8 Emulator Debugger: R0E000080KCE00SR (CD) 3.3.1 CD Install the software as instructed by the displayed messages by inserting the included CD into the CD-ROM drive. The folders contain the files and programs listed below. Table 3.
3.4 Installing Emulator’s Debugger When the CD is inserted in the host computer’s CD drive, execute Setup.exe from the root directory of the CD.
3.5 Connecting the Emulator to the Host Computer This section describes how to connect the emulator to the host computer. For the position of each connector of the emulator, refer to section 3.2, Emulator Hardware Configuration. Notes: 1. When [Add New Hardware Wizard] is displayed, select the [Search for the best driver for your device. (Recommended)] radio button and then the [Specify a location] check box to select the path to be searched for drivers. The location must be specified as :\DRIVERS.
The emulator is connected to the host computer via the USB 1.1, and also to the USB port conforming to USB 2.0. Figure 3.7 shows the system configuration. Figure 3.
3.6 Connecting the Emulator to the User System Use the procedure below to connect the emulator to the user system with the user system interface cable, or to disconnect them when moving the emulator or the user system. 1. Check that the host computer is turned off or the emulator is not connected to the host computer with the USB cable. 2. Connect the user system interface cable to the user-side connector of the emulator. 3. Connect the USB cable to the host-side connector of the emulator. Figure 3.
(2) The pin assignments of the connector are shown in section 2 in the additional documents, Notes on Connecting the xxxxx. Figure 3.9 Connecting the User System Interface Cable to the User System Notes: 1. 2. 3. 4. 24 To connect the signals output from the connector, refer to the MCU pin alignment. To remove the user system interface cable from the user system, pull the tab on the connector upward. The range of frequencies that the emulator operates at is different according to the MCUs used.
3.7 Connecting System Ground WARNING Separate the frame ground from the signal ground at the user system. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator product or will result in PERSONAL INJURY. The emulator's signal ground is connected to the user system's signal ground. In the emulator, the signal ground and frame ground are connected. In the user system, connect the frame ground only; do not connect the signal ground to the frame ground (Figure 3.10).
3.8 System Check When the software is executed, use the procedure below to check that the emulator is connected correctly. Here, use the workspace for a tutorial provided on the product. Refer to section 4, Preparations for Debugging, for the other activating method to create a new project or use a workspace for the High-performance Embedded Workshop of the old version. 1. 2. 3. 4. Connect the emulator to the host computer. Connect the user system interface cable to the connector of the emulator.
When the [Open workspace] dialog box is opened, specify the following directory: \WorkSpace\Tutorial\E8\xxxx\Tutorial After the directory has been specified, select the following file and click the [Open] button. Figure 3.12 [Open Workspace] Dialog Box Note: The directory for a tutorial differs depending on the device.
6. The [Select Emulator mode] dialog box is displayed. Figure 3.13 [Emulator Setting] Dialog Box Select the device name in use from the [MCU Group] drop-down list box. Note: The [MCU Group] drop-down list box is not displayed in the H8/Tiny or H8/Super Low Power series. Select the device name in use from the [Device] drop-down list box. The following items are selected in the [Mode] group box. ⎯ Erase Flash and Connect This mode is used to erase data of the MCU flash memory and activate the debugger.
⎯ Program Flash This mode is used when the emulator is used as a flash memory programmer. It cannot be used for debugging programs. Register the load module in the workspace to download it. Note: It is necessary to input the ID code of the flash memory by the target device. For details, refer to the additional document, Notes on Connecting the xxxxx. ⎯ Debugging of CPU rewrite mode This mode is used to debug the program that rewrites the CPU.
7. The [Connecting] dialog box is displayed and the emulator connection is started. Figure 3.14 [Connecting] Dialog Box 8. When the version of the E8 firmware downloaded into the emulator is old, the message box shown in Figure 3.15 will be displayed. Figure 3.15 Dialog Box for confirming the E8 firmware download Note: When [OK] button is clicked, it starts downloading the E8 firmware. Do not connect/disconnect the USB cable until the download status dialog box closes.
9. When [Power supply is carried out. (MAX 300mA)] is not checked, the dialog box shown in Figure 3.17 will be displayed. Figure 3.16 Dialog Box of the Power-on Request Message 10. The dialog box for confirming the power supply status of the user system will be displayed. Figure 3.17 [Power Supply] Dialog Box When [Power supply is carried out. (MAX 300mA)] is checked, power will be supplied to the user system up to 300 mA. Then select 3.3 V or 5.0 V according to the power voltage of the user system.
11. When [Power supply is carried out. (MAX 300mA)] is not checked, power on the user system and click the [OK] button. 12. When "Connected" is displayed in the [Output] window of the High-performance Embedded Workshop, the emulator initiation is completed Figure 3.
Notes: 1. If the user system interface cable is disconnected from the connector on the user system, the following dialog box will appear. Figure 3.19 [Connector disconnected] Dialog Box 2. If the emulator is not properly initialized, one of the dialog boxes shown in figures 3.20 through 3.24 will appear. (a) The following dialog box is displayed when the flash memory cannot be erased. Exchange the MCU since the flash memory has been programmed more times than the limitation. Figure 3.
(c) The following dialog box is displayed when an incorrect ID code has been input. For the H8/Tiny, H8/ Super Low Power, R8C/10, 11, 12 and 13, if an ID code does not match, the flash memory will be completely erased. Figure 3.22 [ID code error!] Dialog Box (d) The following dialog box is displayed when the MCU cannot communicate with the emulator. Check the MCU settings. Figure 3.23 [Boot Failed!] Dialog Box 3. If an incorrect driver has been selected, the following dialog box will appear. Figure 3.
3.9 Uninstalling the Emulator’s Debugger Follow this procedure to remove the installed emulator’s debugger from the user’s host computer. As the installed product is known by the High-performance Embedded Workshop, uninstall the product on the High-performance Embedded Workshop screen. 1. 2. Activate the High-performance Embedded Workshop. Click the [Administration…] button in the [Welcome!] dialog box. Figure 3.25 [Welcome!] Dialog Box 3. The [Tools Administration] dialog box is opened. Figure 3.
Click the [+] mark at the left of [Debugger Components] in the [Registered components] list box to list the installed components. Then, highlight the product name to be uninstalled. Figure 3.27 Highlighting the Product to be Uninstalled Click the [Unregister] button. After the following message box is displayed, click the [Yes] button. Figure 3.28 [Unregistering this tool] Message Box This is the end of canceling the High-performance Embedded Workshop registration.
Figure 3.29 [Uninstall HEW Tool] Dialog Box Click the [Start] button to list the installed components. Figure 3.
Highlight the product name to be uninstalled and click the [Uninstall] button. This is the end of uninstallation. CAUTION A shared file may be detected while the program is being removed. If another product may be using the shared file, do not remove the file. If another product does not start up after the removal process, re-install that product.
Section 4 Preparations for Debugging 4.1 Method for Activating High-performance Embedded Workshop To activate the High-performance Embedded Workshop, follow the procedure listed below. 1. 2. 3. Connect the emulator to the host computer and the user system, then turn on the user system. Select [Renesas] -> [High-performance Embedded Workshop] -> [High-performance Embedded Workshop] from [Programs] in the [Start] menu of Windows® The [Welcome!] dialog box is displayed. Figure 4.
4.1.1 Creating the New Workspace (Toolchain Not Used) 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Create a new project workspace] radio button and click the [OK] button. Figure 4.2 [Welcome!] Dialog Box 2. The Project Generator is started. This section omits the description on the setting for the toolchain. If you have not purchased the toolchain, the following dialog box is displayed.
Figure 4.3 [New Project Workspace] Dialog Box [Workspace Name] edit box: Enter the new workspace name. Here, enter ‘test’. [Project Name] edit box: Enter the project name. When the project name is the same as the workspace name, it needs not be entered. [CPU family] drop-down list box: Select the target CPU family. M32C: Select [M16C/80, M32C] R8C, M16C: Select [M16C]. H8 Tiny/ Super Low Power: Select [H8S, H8/300]. [Tool chain] drop-down list box: Here, select [None].
3. The following dialog box is displayed. Figure 4.4 [Setting the Target System for Debugging] Dialog Box Select the target system for debugging and click the [Next] button. [Target system for debugging] M32C E8 SYSTEM: M16C E8 SYSTEM: R8C E8 SYSTEM: H8 Tiny/Super Low Power E8 SYSTEM 300H: H8 Tiny/Super Low Power E8 SYSTEM 300L: [Target MCU] M32C M16C R8C/Tiny H8/300H Tiny, H8/300H Super Low Power H8/300 Super Low Power 4. Set the configuration file name.
Figure 4.5 [Setting the Debugger Options] Dialog Box This is the end of the emulator setting. Click the [Finish] button to exit the Project Generator. The High-performance Embedded Workshop is activated. 5. After the High-performance Embedded Workshop has been activated, the emulator is automatically connected. For operation during connection, refer to section 3.8, System Check.
4.1.2 1. Creating the New Workspace (Toolchain Used) In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Create a new project workspace] radio button and click the [OK] button. Figure 4.6 [Welcome!] Dialog Box 2. 44 The Project Generator is started. If you have purchased the toolchain, the following dialog box is displayed.
Figure 4.
[Workspace Name] edit box: [Project Name] edit box: Enter the new workspace name. Here, enter ‘test’. Enter the project name. When the project name is the same as the workspace name, it needs not be entered. [CPU family] drop-down list box: Select the target CPU family. [Tool chain] drop-down list box: Select the target toolchain name when using the toolchain. Otherwise, select [None]. [Project type] list box: Select the project type to be used.
3. Make the required setting for the toolchain. Figure 4.8 [New Project-1/6-Select Target CPU. Toolchain version] Dialog Box Select your toolchain version, CPU series and click the [Next] button.
4. Make the required settings for the RTOS. Figure 4.9 [New Project-2/6-Select RTOS] Dialog Box Select the RTOS you use, type of startup file and click the [Next] button. Note: In the H8/Tiny or H8/Super Low Power series this dialog box will not be displayed.
5. Make the required settings for the heap area etc. Figure 4.10 [New Project-3/6-Setting the Contents of Files to be Generated] Dialog Box Set the heap size etc. and click the [Next] button. Note: In the H8/Tiny, H8/ Super Low Power series, the content of the dialog box will differ.
6. Make the required setting for the stack area. Figure 4.11 [New Project-4/6-Setting the Stack Area] Dialog Box Set the stack size and click the [Next] button.
7. When the tool chain settings have been completed, the following dialog box is displayed. Figure 4.12 [New Project-5/6-Setting the Target System for Debugging] Dialog Box Select the target system for debugging and click the [Next] button.
8. Set a configuration file name. The configuration file saves the settings of the High-performance Embedded Workshop except for the emulator. Figure 4.
9. Finally, confirm the file name you create. Figure 4.14 [New Project-7/7-Changing the File Names to be Created] Dialog Box The files which will be generated by the High-performance Embedded Workshop are displayed If you want to change the file name, select and click it then enter the new name. This is the end of the emulator settings. Exit the Project Generator following the instructions on the screen. The High-performance Embedded Workshop is activated.
10. After the High-performance Embedded Workshop has been activated, connect the emulator. However, it is not needed to connect the emulator immediately after the High-performance Embedded Workshop has been activated. To connect the emulator, use one of the methods (a) and (b) below. For operation during connection, refer to section 3.8, System Check. (a) Connecting the emulator after the setting at emulator activation Select [Debug settings] from the [Debug] menu to open the [Debug Settings] dialog box.
(b) Connecting the emulator without the setting at emulator activation The emulator can be easily connected by switching the session file that the setting for the emulator use has been registered. Figure 4.15 Selecting the Session File In the list box that is circled in Figure 4.15, select the session file name including the character string that has been set in the [Target name] text box in Figure 4.13, [New Project-6/7-Setting the Debugger Options] dialog box.
4.1.3 Selecting an Existing Workspace 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Browse to another project workspace] radio button and click the [OK] button. Figure 4.
2. The [Open Workspace] dialog box is displayed. Select a directory in which you have created a workspace. After that, select the workspace file (.hws) and press the [Open] button. Figure 4.17 [Open Workspace] Dialog Box 3. This activates the High-performance Embedded Workshop and recovers the state of the selected workspace at the time it was saved. When the saved state information of the selected workspace includes connection to the emulator, the emulator will automatically be connected.
4.2 Setting at E8 Emulator Activation 4.2.1 Setting at Emulator Activation When the emulator is activated, the command chain can be automatically executed. It is also possible to register multiple load modules to be downloaded. The registered load modules are displayed on the workspace window. 1. Select [Debug Settings…] from the [Debug] menu to open the [Debug Settings] dialog box. Figure 4.18 [Debug Settings] Dialog Box ([Target] Page) 2.
Figure 4.19 [Debug Settings] Dialog Box ([Options] Page) The command chain that is automatically executed at the specified timing is registered. The following three timings can be specified: • At connecting the emulator • Immediately before downloading • Immediately after downloading Specify the timing for executing the command chain in the [Command batch file load timing] drop-down list box.
4.2.2 Downloading a Program A download module is added under [Download modules] in the [Workspace] window. Open the load module of [Download modules] in the [Workspace] window by clicking the righthand mouse button and select [Download module] to start downloading the module. Figure 4.20 Download Menu of the [Workspace] Window ([Projects]) Notes: 1. When load modules are downloaded, select [Debug] -> [Download] -> [All DownLoad Modules]. 2.
4.2.3 Setting the Writing Flash Memory Mode The following describes the procedures when the emulator is used as the programming tool. The load module to be downloaded to the new workspace is registered and programmed. (a) Select the new project workspace. Figure 4.
(b) Select the target MCU and click the [Next] button. Figure 4.
(c) Set a configuration file name and click the [Finish] button. Figure 4.
(d) The [Emulator Setting] dialog box is displayed. Figure 4.24 [Select Emulator mode] Dialog Box Select the [Program Flash] mode. When the [Power Target from Emulator. (MAX 300mA)] check box is selected, power will be supplied to the user system up to 300 mA. Then select 3.3 V or 5.0 V according to the power voltage of the user system.
(e) When [Power supply is carried out. (MAX 300mA)] is not checked, the dialog box shown in Figure 4.25 will be displayed. Figure 4.25 Dialog Box of Power-on request message When [Power supply is carried out. (MAX 300mA)] is not checked, turn on the power to the user system. (f) Enter the ID code printed on the flash memory. Figure 4.26 [ID Code verification] Dialog Box Note: Opening the [ID Code verification] dialog box in Writing Flash memory mode depends on a target device.
(g) Select [Debug Setting…] from the [Debug] menu. Figure 4.
(h) Select the target MCU and then the download module with the [Add…] button. Figure 4.28 [Debug Setting] Dialog Box ([Target] Page) (i) The download file is displayed on [Project Files]. Figure 4.
(j) Select and download the file with the right-hand mouse button. Figure 4.30 Download Menu of the [Workspace] Window ([Project Files]) (k) The dialog box for sum checking is displayed and writing is completed. Figure 4.
(l) When the following dialog box is displayed, close and restart or exit the workspace. Figure 4.
70
Section 5 Debugging This section describes the debugging operations and their related windows and dialog boxes. For details on the common functions of the High-performance Embedded Workshop products, refer to the High-performance Embedded Workshop User’s Manual. 5.1 Setting the Environment for Emulation 5.1.1 Opening the [Configuration] Dialog Box Selecting [Setup -> Emulator -> System…] or clicking the [Emulator System] toolbar button ( opens the [Configuration] dialog box.
5.1.2 [General] Page Sets the emulator operation conditions. Figure 5.1 [Configuration] Dialog Box ([General] Page) Items that can be displayed in the sheet are listed below. [Device] combo box Displays the MCU name. [Emulation mode] combo box Selects the emulation mode at user program execution. Select Normal to perform normal emulation. Select No break to disable PC breakpoint or break condition settings during emulation.
[Flash memory synchronization] combo box Selects whether or not the contents of the flash memory are acquired by the emulator when the user program is stopped or the position where the PC break is set is put back as the original code. When the flash memory is not programmed by the user program, its contents need not be acquired by the emulator.
5.2 Downloading a Program This section describes how to download a program and view it as source code or assemblylanguage mnemonics. Note: After a break has been detected, the High-performance Embedded Workshop displays the location of the program counter (PC). In most cases, for example if an Elf/Dwarf2-based project is moved from its original path (at the build), the source file may not be automatically found.
5.2.2 Viewing the Source Code Select a source file name in the [Workspace] window and click [Open] in the popup menu to make the High-performance Embedded Workshop display the source file in the editor. It is also possible to display your source files by double-clicking on their names in the [Workspace] window. Figure 5.
In this window, the following items are shown on the left as line information. The first column (Line Number column) Line number The second column (Source address column): Address information The third column (Event column): Event information (break condition) The fourth column (S/W Breakpoints column): PC, bookmark, and breakpoint information The right window that shows the source is called as the [Source] window. • Line Number column A line number for the current source file is displayed.
To switch off a column in all source files 1. 2. 3. 4. Click the right-hand mouse button on the [Source] window or select the [Edit] menu. Click the [Define Column Format…] menu item. The [Global Editor Column States] dialog box is displayed. A check box indicates whether the column is enabled or not. If it is checked, the column is enabled. If the check box is gray, the column is enabled in some files and disabled in others. Deselect the check box of a column you want to switch off. 5.
5.3 Stopping Your Program This section describes how you can halt execution of your application's code. This section describes how to stop the program by setting an address match breakpoints at specific locations in your code. 5.3.1 Address Interrupt Breakpoints When you are trying to debug your program you will want to be able to stop the program running when it reaches a specific point or points in your code.
5.4 Using the Event Points The emulator has the event point function that performs breaking by specifying higher-level conditions along with the PC breakpoints standard for the High-performance Embedded Workshop. 5.4.1 PC Breakpoints When the instruction of the specified address is fetched, the user program is stopped. Up to 255 points can be set. 5.4.2 Break Conditions Break conditions can be used for higher-level conditions such as the data condition as well as specification of the single address.
This window displays and sets the breakpoints. Items that can be displayed in the sheet are listed below.
5.4.11 Go to Source Only enabled when one breakpoint is selected. Opens the [Source] window at the address of the breakpoint. 5.4.12 [Set Break] Dialog Box Figure 5.6 [Set Break] Dialog Box This dialog box specifies break conditions. A breakpoint address to be set is specified in the [Address] edit box. Up to 255 breakpoints can be specified. When [Address] is selected, if an overloaded function or class name including a member function is specified in address, the [Select Function] dialog box opens.
Notes on Setting the [Set Break] Dialog Box 1. When an odd address is set for the H8/Tiny and H8/ Super Low Power series, the address is rounded down to an even address. 2. A Breakpoint is accomplished by replacing instructions. Accordingly, it can be set only to the flash memory or RAM area. However, a software break cannot be set to the following addresses: ⎯ An area other than the flash memory or RAM ⎯ An area occupied by the E8 emulator program ⎯ An instruction in which Break Condition 1 is satisfied 3.
Notes on Setting the Break Condition: 1. When [Go to cursor], [Step In], [Step Over], or [Step Out] is selected, the settings of Break Condition 1 are disabled. 2. Setting of Break Condition 1 is disabled when an instruction to which a BREAKPOINT has been set is executed. 3. When step over function is used, the settings of BREAKPOINT and Break Condition 1 are disabled. Notes on Setting the Break Condition (for the R8C/Tiny Series): 1.
5.4.16 Disable Disables the selected break channel(s). When a break channel is disabled, a break will not occur even if specified conditions have been satisfied. 5.4.17 Delete Initializes the condition of the selected break channel. To retain the details of the break channel but not have it cause a break when its conditions are met, use the Disable option (see section 5.4.16, Disable). 5.4.18 Delete All Initializes conditions of all break channels. 5.4.
5.4.25 Deleting Break Conditions Select a break condition and choose [Delete] from the popup menu to remove the selected break condition. To retain the break condition but not have it cause an event when its conditions are met, use the [Disable] option (see section 5.4.24, Disabling Break Conditions). 5.4.26 Deleting All Break Conditions Choose [Delete All] from the popup menu to remove all break conditions. 5.4.
The [Address] group box sets address bus conditions. Option Description [Don’t care] check box Does not set address conditions. [Address] radio button Sets the use of the normal address bus as break conditions. [Only program fetched address after] radio button Sets a break after prefetched address execution as break conditions. [Address] edit box Sets the address bus value with a number or a symbol. [Mask] edit box Sets a value to be masked when [User mask] is selected.
5.5 Viewing the Trace Information For the description on the trace function, refer to section 2.2, Trace Functions. Note: The R8C/Tiny series MCUs do not have trace functions. 5.5.1 Opening the [Trace] Window To open the [Trace] window, choose [View -> Code -> Trace] or click the [Trace] toolbar button ( ). 5.5.2 Acquiring Trace Information The acquired trace information is displayed in the [Trace] window. Figure 5.
5.5.3 Clearing the Trace Information When [Clear] is selected from the popup menu, the trace buffer that stores the trace information becomes empty. If several [Trace] windows are open, all [Trace] windows will be cleared as they all access the same buffer. 5.5.4 Saving the Trace Information in a File Select [Save...] from the popup menu to open the [Save As] file dialog box, which allows the user to save the information displayed in the [Trace] window as a text file.
5.6 Using the Start/Stop Function The emulator executes the specified routine of the user program immediately before starting and immediately after halting program execution. This function is used to control the user system in synchronization with execution and halting of the user program. Note: The start/stop function is not supported in the H8/Tiny or H8/Super Low Power series, or the R8C/10, R8C/11, R8C/12, or R8C/13 group. 5.6.
If no specified routine is executed immediately before starting user program execution, do not select the [The specified routine is executed immediately before execution of the user’s program.] check box. When the [The specified routine is executed immediately after the stop of the user’s program.] check box is selected, the routine specified in the [starting address] combo box, which is below this check box, is executed immediately after halting user program execution.
5.6.3 Restrictions on the Start/Stop Function The start/stop function has the following restrictions. • Do not change the SFR used by the firmware. • When the watchdog timer is used, refresh the watchdog timer in the specified routine. • Do not set any breakpoints in the specified routine. • When a stack is used in the specified routine, be sure to use the user stack. • A register value is undefined when execution of the specified routine is started.
92
Section 6 Tutorial 6.1 Introduction This section describes the main functions of the emulator by using a tutorial program. The tutorial program is based on the C program that sorts ten random data items in ascending or descending order. The tutorial program performs the following actions: • The main function generates random data to be sorted. • The sort function sorts the generated random data in ascending order. • The change function then sorts the data in descending order. The file tutorial.
6.2 Running the High-performance Embedded Workshop To run the High-performance Embedded Workshop, refer to section 3.8, System Check. 6.3 Setting up the E8 Emulator This section describes the basic settings of the emulator.
6.4 Setting the [Configuration] Dialog Box • Select [Emulator] then [Systems…] from the [Setup] menu for the basic settings of the emulator. The [Configuration] dialog box is displayed. Figure 6.1 [Configuration] Dialog Box Note: The items that can be set in this dialog box differ depending on the product. For the settings for each product, refer to the online help.
Set options as follows: Table 6.1 [General] Page Options Option Value Device Select a device you use Emulation mode Normal (normal execution, default) User interface clock According to the system clock frequency, the maximum user interface clock is automatically set. Flash memory synchronization Disable (default) Click the [OK] button to set a configuration.
6.5 Checking the Operation of RAM Check that RAM is operating correctly. Display and edit the contents of the memory in the [Memory] window to check that the memory is operating correctly. Note: The memory can be installed on the board in some microcomputers. In this case, however, the above way of checking the operation of memory may be inadequate. It is recommended that a program for checking the memory be created.
Figure 6.3 [Memory] Window • Placing the mouse cursor on a point in the display of data in the [Memory] window and double-clicking allows the values at that point to be changed. Data can also be directly edited around the current position of the text cursor.
6.6 Downloading the Tutorial Program 6.6.1 Downloading the Tutorial Program Download the object program to be debugged. In this emulator, it is enabled to download the program and set the PC breakpoint in the internal flash memory area. For the method to set the PC breakpoint, refer to section 6.16.1, PC Break Function. • Select [Download module] from [Tutorial.x30] under [Download modules]. Figure 6.
6.6.2 Displaying the Source Program The High-performance Embedded Workshop allows the user to debug a user program at the source level. • Double-click [tutorial.c] under [C source file]. Figure 6.5 [Source] Window (Displaying the Source Program) Select the [Display] option from the [Setup] menu to set a font and size that are legible, if necessary.
6.7 Setting a PC Breakpoint A PC breakpoint is a simple debugging function. The [Source] window provides a very simple way of setting a PC breakpoint at any point in a program. For example, to set a PC breakpoint at the sort function call: • Select by double-clicking the [S/W Breakpoints] column on the line containing the sort function call. Figure 6.6 [Source] Window (Setting a PC Breakpoint) The symbol • will appear on the line containing the sort function. This shows that a PC breakpoint has been set.
6.8 Setting Registers Set values of the program counter and the stack pointer before executing the program. • Select [Registers] from the [CPU] submenu of the [View] menu. The [Register] window is displayed. Figure 6.
z To change the value of the program counter (PC), double-click the value area in the [Register] window with the mouse. The following dialog box is then displayed, and the value can be changed. Set the program counter to 0E612 in this tutorial program, and click the [OK] button. Figure 6.
6.9 Executing the Program Execute the program as described in the following: • To execute the program, select [Go] from the [Debug] menu, or click the [Go] button on the toolbar. Figure 6.9 [Go] Button When the program execution is started, ‘**RUNNING’ is displayed on the status bar.
Figure 6.
The user can see the cause of the break that occurred last time in the [Status] window. • Select [Status] from the [CPU] submenu of the [View] menu. After the [Status] window is displayed, open the [Platform] sheet, and check the Status of Cause of last break. Figure 6.11 [Status] Window Note: The items that can be set in this window differ depending on the product. For the settings for each product, refer to the online help.
6.10 Reviewing Breakpoints The user can see all the breakpoints set in the program in the [Eventpoint] window. • Select [Eventpoints] from the [Code] submenu of the [View] menu. The [Eventpoint] window is displayed. Select the [Breakpoint] sheet. Figure 6.12 [Eventpoint] Window The popup menu, opened by clicking the [Eventpoint] window with the right-hand mouse button, allows the user to set or change breakpoints, define new breakpoints, and delete, enable, or disable breakpoints.
6.11 Viewing Memory When the label name is specified, the user can view the memory contents that the label has been registered in the [Memory] window. For example, to view the memory contents corresponding to _main in word size: • Select [Memory …] from the [CPU] submenu of the [View] menu, enter _main in the [Display Address] edit box, enter 0000 and FFFF in the [Scroll Start Address] and [Scroll End Address] edit boxes, respectively. Figure 6.13 [Display Address] Dialog Box • Click the [OK] button.
6.12 Watching Variables As the user steps through a program, it is possible to watch that the values of variables used in the user program are changed. For example, set a watch on the long-type array a declared at the beginning of the program, by using the following procedure: • Click the left of displayed array a in the [Source] window to position the cursor. • Select [Instant Watch...] with the right-hand mouse button. The following dialog box will be displayed. Figure 6.
The user can also add a variable to the [Watch] window by specifying its name. • Click the [Watch] window with the right-hand mouse button and select [Add Watch…] from the popup menu. The following dialog box will be displayed. Enter variable i. Figure 6.17 [Add Watch] Dialog Box • Click the [OK] button. The [Watch] window will now also show the int-type variable i. Figure 6.
The user can click mark ‘+’ at the left side of array a in the [Watch] window to watch all the elements. Figure 6.
6.13 Stepping Through a Program The High-performance Embedded Workshop provides a range of step menu commands that allow efficient program debugging. Table 6.2 Step Option Menu Command Description Step In Executes each statement, including statements within functions. Step Over Executes a function call in a single step. Step Out Steps out of a function, and stops at the statement following the statement in the program that called the function.
6.13.2 Executing [Step Out] Command The [Step Out] command steps out of the called function and stops at the next statement of the calling statement in the main function. • To step out of the sort function, select [Step Out] from the [Debug] menu, or click the [Step Out] button on the toolbar. Note: It takes time to execute this function. When the calling source is clarified, use [Go To Cursor]. Figure 6.22 [Step Out] Button Figure 6.
6.13.3 Executing [Step Over] Command The [Step Over] command executes a function call as a single step and stops at the next statement of the main program. • To step through all statements in the change function at a single step, select [Step Over] from the [Debug] menu, or click the [Step Over] button on the toolbar. Figure 6.24 [Step Over] Button Figure 6.
6.14 Forced Breaking of Program Executions The High-performance Embedded Workshop can force a break in the execution of a program. • Cancel all breaks. • To execute the remaining sections of the main function, select [Go] from the [Debug] menu or the [Go] button on the toolbar. Figure 6.26 [Go] Button • The program goes into an endless loop. To force a break in execution, select [Halt] from the [Debug] menu or the [Halt] button on the toolbar. Figure 6.
6.15 Displaying Local Variables The user can display local variables in a function using the [Locals] window. For example, we will examine the local variables in the main function, which declares four local variables: a, j, i, and p_sam. • Select [Locals] from the [Symbol] submenu of the [View] menu. The [Locals] window is displayed. The [Locals] window shows the local variables in the function currently pointed to by the program counter, along with their values.
6.16 Break Function The emulator has PC and hardware break functions. With the High-performance Embedded Workshop, a PC breakpoint can be set using the [Breakpoint] sheet of the [Event] window, and a hardware break condition can be set using the [Breakcondition] sheet. An overview and setting of the break function are described below. 6.16.1 PC Break Function The emulator can set up to 255 PC breakpoints. Other methods for setting a PC breakpoint than in section 6.
• Click the [Event] window with the right-hand mouse button and select [Add…] from the popup menu. • Enter H'0E1F2 in the [Address] edit box. Figure 6.30 [Set Break] Dialog Box • Click the [OK] button.
The PC breakpoint that has been set is displayed in the [Eventpoint] window. Figure 6.31 [Eventpoint] Window (PC Breakpoint Setting) To stop the tutorial program at the PC breakpoint, the following procedure must be executed: • Close the [Eventpoint] window. • Set the program counter value (PC = H’0E6C6) that was set in section 6.8, Setting Registers, in the [Register] window. Click the [Go] button. • If program execution is failed, reset the device and execute again the procedures above.
The [Status] window displays the following contents. Figure 6.33 Displayed Contents of the [Status] Window (PC Break) Note: The items that can be set in this window differ depending on the product. For the settings for each product, refer to the online help.
6.17 Hardware Break Function A method is given below in which the address bus condition is set under Break Condition 1 as hardware break conditions. • Select [Eventpoints] from the [Code] submenu of the [View] menu. The [Eventpoint] window is displayed. • The PC breakpoint that has been previously set is deleted. Click the [Eventpoint] window with the right-hand mouse button and select [Delete All] from the popup menu to cancel all PC breakpoints that have been set.
• The [Break condition 1] dialog box is displayed. • Clear the [Don't care] check box in the [Address] group box. • Select the [Only program fetched address after] radio button and enter H'0E1F2 as the value in the [Address] edit box. Figure 6.35 [condition] Page ([Break condition 1] Dialog Box) Click the [OK] button. The first point display in the State line changes from Disable to Enable. The first point display in the Condition line changes from None to Address = H’0000e1f2(Tutorial.c/41)pcbefore.
The program runs and then stops at the condition specified under Break Condition 1. Figure 6.36 [Source] Window at Execution Stop (Break Condition 1) The [Status] window displays the following contents. Figure 6.37 Displayed Contents of the [Status] Window (Break Condition 1) Note: The items that can be set in this window differ depending on the product. For the settings for each product, refer to the online help.
6.18 Trace Functions The emulator has a branch-instruction trace function. The branch source addresses, mnemonics, operands, source lines, and labels are displayed for four branches. Note: The trace function uses the trace buffer housed in the device. Devices which have no trace function cannot use this function. 6.18.1 Displaying the Trace Window Select [Trace] from the [Code] submenu of the [View] menu. Run the program as shown in the example of section 6.16.1, PC Break Function.
6.19 Stack Trace Function The emulator uses the information on the stack to display the names of functions in the sequence of calls that led to the function to which the program counter is currently pointing. Note: This function can be used only when the load module that has the IEEE695-type debugging information is loaded. • Double-click the [S/W Breakpoints] column in the sort function and set a PC breakpoint. Figure 6.
• After the break in program execution, select [Stack Trace] from the [Code] submenu of the [View] menu to open the [Stack Trace] window. Figure 6.40 [Stack Trace] Window Figure 6.40 shows that the position of the program counter is currently at the selected line of the sort() function, and that the sort() function is called from the tutorial() function.
6.20 What Next? This tutorial has described the major features of the emulator and the use of the High-performance Embedded Workshop. Sophisticated debugging can be carried out by using the emulation functions that the emulator offers. This provides for effective investigation of hardware and software problems by accurately isolating and identifying the conditions under which such problems arise.
128
Appendix A Components of the E8 Emulator Table A.1 lists the components of the R8C E8 emulator. Table A.1 Components of the Emulator (R0E000080KCE00) Classification Hardware Software Component Appearance Quantity Remarks 1 R0E000080KCE00: Depth: 65 mm, Width: 97 mm, Height: 21 mm, Mass: 60.0 g User system interface cable 1 Length: 20 cm (connector part not included), Mass: 20.0 g USB cable 1 Length: 1.5 m, Mass: 52.
130
Appendix B Window Functions This section describes the window functions that can be used with the High-performance Embedded Workshop for E8 emulator. Here, the High-performance Embedded Workshop common functions are omitted, and only the emulation functions are described. Table B.1 Window Functions Menu View Option Shortcut Toolbar Button Remarks Disassembly Ctrl + D Opens the [Disassembly] window. Command Line Ctrl + L Opens the [Command Line] window.
Table B.1 Window Functions (cont) Menu Setup Option Radix Emulator Debug 132 Shortcut Toolbar Button Remarks Hexadecimal Uses a hexadecimal for displaying a radix in which the numerical values will be displayed and entered by default. Decimal Uses a decimal for displaying a radix in which the numerical values will be displayed and entered by default. Octal Uses an octal for displaying a radix in which the numerical values will be displayed and entered by default.
Table B.1 Window Functions (cont) Menu Option Shortcut Run… Debug (cont) Remarks Launches the [Run Program] dialog box allowing the user to enter the PC or PC breakpoint during executing the user program. Display PC Shift + Ctrl + Y Displays the current PC value. Step In F11 Executes a block of user program before breaking. Step Over F10 Executes a block of user program before breaking. If a subroutine call is reached, then the subroutine will not be entered.
Table B.1 Window Functions (cont) Menu 134 Option Shortcut Toolbar Button Remarks Download Modules Downloads the object program. Unload Modules Unloads the object program.
Appendix C Command-Line Functions The emulator supports the commands that can be used in the command-line window. For details, refer to the online help.
136
Appendix D Notes on High-performance Embedded Workshop 1. Note on Moving Source File Position after Creating Load Module When the source file is moved after creating the load module, the [Open] dialog box may be displayed to specify the source file during the debugging of the created load module. Select the corresponding source file and click the [Open] button. 2. Source-Level Execution ⎯ Source file Do not display source files that do not correspond to the load module in the program window.
⎯ Variable updating For updating of the content of the variable that has been registered in the [Watch] window, read the data after the break in user program execution. The realtime operation for the user program is disabled because the user program is temporarily stopped. 5. Line Assembly ⎯ Input radix Regardless of the Radix setting, the default for line assembly input is decimal.
10. Note on [Register] Window Operation During Program Execution The register value cannot be changed in the [Register] window during program execution. Even if the changed value is displayed, the register contents are not changed actually. 11 Using Register Contents Use the value contained in a CPU register by specifying the register name prefixed by the “#” character, e.g.
⎯ MEMORY_FILL command The [Format] specification in the [Copy Memory] dialog box is ignored. Memory is copied in a byte unit. 17. Note on Using the [Run Program] Dialog Box When [Run...] is selected from the [Debug] menu to specify the stop address, there is the following note: ⎯ When the breakpoint that has been set as Disable is specified as the stop address, note that the breakpoint becomes Enable when the user program stops.
24 Usage with Other Products To install the SuperH™ RISC engine C/C++ compiler package or H8, H8/300 series C/C++ compiler package after installing the emulator debugger for High-performance Embedded Workshop, select [High-performance Embedded Workshop] as the component to be installed in [Select Components] during installation of the compiler package. 25 Download of Load Modules When load modules are downloaded, select [Debug] -> [Download] -> [All DownLoad Modules].
142
Appendix E Diagnostic Hardware Program This manual describes the troubleshooting procedure that applies the check program for the E8 emulator. E.1. System Setup to Execute the Check Program (1) The following equipments are required to execute the check program. Do not connect the user system interface cable or the user system while the check program is running.
(2) Click the ‘START’ button appeared on the window. This starts execution of the check program showing the message ‘RUNNING’. Figure E.2 Running the Check Program (3) The message ‘FAIL’ or ‘PASS’ will be displayed. ‘PASS’ indicates that the emulator is working correctly. Click the ‘QUIT’ button to exit the check program. Figure E.
E.3 When an Error Occurs (1) If ‘FAIL’ is displayed during execution of the check program, a status number is also displayed at the right bottom of the window. (2) Click the ‘LOG’ button to create a log file. Figure E.4 ‘FAIL’ Message (3) Send a file ‘SCP_LOG.TXT’, which has been created in the folder where ‘E8SCP.EXE’ was executed, to our customer support center by e-mail. The e-mail address is written on the following website: Renesas Tool Homepage : http://www.renesas.com/fmwk.
146
E8 Emulator User's Manual Publication Date: Aug. 1, 2004 Aug. 1, 2007 Rev.1.00 Rev.10.00 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Microcomputer Tool Development Department Renesas Solutions Corp. © 2007. Renesas Technology Corp. and Renesas Solutions Corp., All rights reserved. Printed in Japan.
E8 Emulator User's Manual
