IAR C-SPY Hardware Debugger Systems User Guide. for Renesas E30A/E30 Emulators

Transcription

1 IAR C-SPY Hardware Debugger Systems User Guide for Renesas E30A/E30 Emulators

2 COPYRIGHT NOTICE Copyright IAR Systems AB. No part of this document may be reproduced without the prior written consent of IAR Systems AB. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such a license. DISCLAIMER The information in this document is subject to change without notice and does not represent a commitment on any part of IAR Systems. While the information contained herein is assumed to be accurate, IAR Systems assumes no responsibility for any errors or omissions. In no event shall IAR Systems, its employees, its contractors, or the authors of this document be liable for special, direct, indirect, or consequential damage, losses, costs, charges, claims, demands, claim for lost profits, fees, or expenses of any nature or kind. TRADEMARKS IAR Systems, IAR Embedded Workbench, C-SPY, visualstate, From Idea To Target, IAR KickStart Kit, IAR PowerPac, IAR YellowSuite, IAR Advanced Development Kit, IAR, and the IAR Systems logotype are trademarks or registered trademarks owned by IAR Systems AB. J-Link is a trademark licensed to IAR Systems AB. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other product names are trademarks or registered trademarks of their respective owners. EDITION NOTICE Second edition: January 2009 Part number: CSR32CHW-2 Internal reference: IJOA

3 Contents Preface... v Who should read this guide...v How to use this guide...v What this guide contains...vi Other documentation...vi Document conventions...vi Typographic conventions...vii Naming conventions...vii Introduction to C-SPY hardware debugger systems... 1 Overview...1 Differences between the C-SPY drivers...2 The C-SPY E30A and E30 drivers...2 Getting started...3 Using the emulator... 5 General debugger options...5 Communication...6 Download...7 Hardware configuration...8 ID Code Verification dialog box...8 Emulator menu...9 Time measurement for E30A...9 Hardware Setup Download Firmware Events window Time Measurement Event dialog box (E30) Interval Time Measurement Event dialog box (E30A) Trace Event dialog box Data Break Event dialog box Trace window iii

4 Find In Trace window Find in Trace dialog box Interval Time Measurement window (E30A) Breakpoints Code breakpoints Execution Address Breakpoint dialog box Software Breakpoint dialog box Breakpoint Usage dialog box C-SPY use of breakpoints iv IAR C-SPY Hardware Debugger Systems User Guide

5 Preface Welcome to the IAR C-SPY Hardware Debugger Systems User Guide for Renesas E30A/E30 Emulators. The purpose of this guide is to provide you with detailed reference information that can help you use the features in the IAR C-SPY Hardware Debugger Systems. Who should read this guide You should read this guide if you want to get the most out of the features in the C-SPY hardware debugger systems. In addition, you should have a working knowledge of: The C or C++ programming language Application development for embedded systems The architecture and instruction set of the target processor (refer to the chip manufacturer's documentation) The operating system of your host machine. This guide also assumes that you already have a working knowledge of the target system you are using, as well as some working knowledge of the IAR C-SPY Debugger. For a quick introduction to the IAR C-SPY Debugger, see the tutorials available in the IAR Embedded Workbench IDE User Guide. How to use this guide This guide describes the C-SPY interface to the target system you are using; it does not describe the general features available in the IAR C-SPY Debugger or the hardware target board. To take full advantage of the whole debugger system, you must read this guide in combination with: The IAR Embedded Workbench IDE User Guide which describes the general features available in the C-SPY debugger The documentation supplied with the target board you are using. Note that additional features may have been added to the software after the IAR C-SPY Hardware Debugger Systems User Guide was produced. The release notes contain the latest information. v

6 What this guide contains What this guide contains Below is a brief outline and summary of the chapters in this guide. Introduction to C-SPY hardware debugger systems introduces you to the C-SPY drivers for the Renesas E30A and E30 emulators. The chapter briefly shows the difference in functionality provided by the different available C-SPY drivers. Using the emulator describes the setup options, and the menus and features provided by the emulator driver. Other documentation The complete set of IAR development tools for the target processor are described in a series of guides. For information about: The interface of the IAR Embedded Workbench IDE, refer to the IAR Embedded Workbench IDE User Guide Programming for the R32C IAR Compiler, refer to the IAR C/C++ Compiler Reference Guide for R32C Programming for the R32C IAR Assembler, refer to the R32C IAR Assembler Reference Guide Using the IAR XLINK Linker, the IAR XAR Library Builder, and the IAR XLIB Librarian, refer to the IAR Linker and Library Tools Reference Guide Using the IAR DLIB library, refer to the IAR Embedded Workbench IDE online help system. All of these guides are delivered in hypertext PDF or HTML format on the installation media. Some of them are also delivered as printed books. Recommended web sites: The Renesas web site, contains information and news about the target processors. The IAR Systems web site, holds application notes and other product information. Finally, the Embedded C++ Technical Committee web site, contains information about the Embedded C++ standard. Document conventions When, in this text, we refer to the programming language C, the text also applies to C++, unless otherwise stated. vi IAR C-SPY Hardware Debugger Systems User Guide

7 Preface When referring to a directory in your product installation, for example r32c\doc, the full path to the location is assumed, for example c:\program Files\IAR Systems\Embedded Workbench 5.n\r32c\doc. TYPOGRAPHIC CONVENTIONS This guide uses the following typographic conventions: Style computer parameter [option] a b c {a b c} bold italic Used for Source code examples and file paths. Text on the command line. Binary, hexadecimal, and octal numbers. A placeholder for an actual value used as a parameter, for example filename.h where filename represents the name of the file. An optional part of a command. Alternatives in a command. A mandatory part of a command with alternatives. Names of menus, menu commands, buttons, and dialog boxes that appear on the screen. A cross-reference within this guide or to another guide. Emphasis. An ellipsis indicates that the previous item can be repeated an arbitrary number of times. Identifies instructions specific to the IAR Embedded Workbench IDE interface. Identifies instructions specific to the command line interface. Identifies helpful tips and programming hints. Identifies warnings. Table 1: Typographic conventions used in this guide NAMING CONVENTIONS The following naming conventions are used for the products and tools from IAR Systems referred to in this guide: Brand name IAR Embedded Workbench for R32C IAR Embedded Workbench IDE for R32C Table 2: Naming conventions used in this guide Generic term IAR Embedded Workbench the IDE vii

8 Document conventions Brand name IAR C-SPY Debugger for R32C IAR C/C++ Compiler for R32C IAR Assembler for R32C IAR XLINK Linker IAR XAR Library builder IAR XLIB Librarian IAR DLIB Library Table 2: Naming conventions used in this guide (Continued) Generic term C-SPY, the debugger the compiler the assembler XLINK, the linker the library builder the librarian the DLIB library viii IAR C-SPY Hardware Debugger Systems User Guide

9 Introduction to C-SPY hardware debugger systems This guide introduces you to the IAR C-SPY hardware debugger systems and to how they differ from the IAR C-SPY Simulator. This guide assumes that you already have some working knowledge of the target system you are using, as well as some working knowledge of the IAR C-SPY Debugger. For a quick introduction, see the tutorials in the IAR Embedded Workbench IDE User Guide. Note that a few additional features might have been added to the software after this guide was produced. The release notes contain the latest information. Overview The IAR C-SPY Debugger consists of both a general part which provides a basic set of C-SPY features, and a driver. The C-SPY driver is the part that provides communication with and control of the target system. The driver also provides a user interface special menus, windows, and dialog boxes to the functions provided by the target system, for instance special breakpoints. This driver is automatically installed during the installation of IAR Embedded Workbench. The IAR C-SPY Debugger for the R32C/100 microcomputer family is available with drivers for the following target systems: Simulator Renesas E8a Emulator Renesas E30A Emulator Renesas E30 Emulator. For further details about the concepts that are related to the IAR C-SPY Debugger, see the IAR Embedded Workbench IDE User Guide. 1

10 The C-SPY E30A and E30 drivers DIFFERENCES BETWEEN THE C-SPY DRIVERS The following table summarizes the key differences between the C-SPY target systems: Feature Simulator E8a Emulator E30A Emulator E30 Emulator Data breakpoints x -- x x Code breakpoint (OP-fetch) x x x x Execution in real time -- x x x Simulated interrupts x Real interrupts -- x x x Cycle counter x -- x 1 x 1 Code coverage x Data coverage x Profiling x x Trace x x 2 Table 3: Differences between available debug support for different target systems 1. Not during single stepping. 2. Limited during branch source and destination information about data accesses, and a maximum of 512 recorded events. 3. Cycle counter statistics are not available. Contact your software distributor or IAR Systems representative for information about available C-SPY drivers. Below are general descriptions of the E30A and E30 Emulator drivers. Note: The E8a Emulator driver is described in the IAR C-SPY Hardware Debugger Systems User Guide for Renesas E8/E8a and E10A-USB Emulators. The C-SPY E30A and E30 drivers The C-SPY driver is the part that provides communication with and control of the target system. The driver also provides the user interface menus, windows, and dialog boxes to the functions provided by the target system, for instance, control of the available hardware breakpoints. 2 IAR C-SPY Hardware Debugger Systems User Guide

11 Introduction to C-SPY hardware debugger systems The C-SPY driver communicates with the E30A Emulator over a USB connection. The E30A Emulator, in turn, communicates with the New Single-wire Debugger (NSD) interface on the MCU. Host computer C-SPY Debugger C-SPY driver E30A Emulator USB connection Coaxial cable Figure 1: Communication overview GETTING STARTED NSD Port CPU Memory Target board This section demonstrates how to get started using C-SPY with the E30A Emulator. The application is built and downloaded to the target system, and then executed. To get started, use one of the example projects available. In the IAR Embedded Workbench IDE, choose Help>Startup Screen. Click on the Example applications button. In the Example Applications dialog box, select Tutorials and save it to a suitable location. In the Workspace window that appears, click on one of the projects. Running the application 1 Choose the Debug build configuration from the drop-down list at the top of the Workspace window. 2 Choose Project>Options>General Options>Target and select your device from the Device list. 3

12 The C-SPY E30A and E30 drivers 3 Choose Project>Options>Debugger>Setup and select the E30A Emulator from the Driver list. For more information about the options, see Using the emulator, page 5. Click OK to close the Options dialog box. 4 Choose Project>Make to compile and link the source code. 5 To start C-SPY, click the Debug button or choose Project>Debug. The Hardware Setup dialog box appears. Click OK. 6 When you are asked to reset the MCU, reset it and then click OK. C-SPY will download your application to the target system. 7 To open the Terminal I/O window, choose View>Terminal I/O. 8 Choose Debug>Go or click the Go button to start the execution. 9 Click the Stop button to stop the execution or wait until program exit is reached. 4 IAR C-SPY Hardware Debugger Systems User Guide

13 Using the emulator This chapter describes the options and settings needed for using the C-SPY E30A or E30 Emulator debugger system. The chapter also describes how to use the debugger. The application can be run in real time when using these features, which provides a powerful tool for locating problems in the application or the hardware. General debugger options Before you start the C-SPY debugger you must set up the options for the debugger system both C-SPY generic options and options required for the hardware system (C-SPY driver-specific options). Follow this procedure: 1 To open the Options dialog box, choose Project>Options. 2 Specify which device you are using on the General Options>Target page. 3 To set C-SPY generic options and select a C-SPY driver: Select Debugger from the Category list On the Setup page, select the appropriate C-SPY driver from the Driver list. For information about the settings Setup macros, Run to, and Device descriptions, as well as for information about the pages Extra Options and Plugins, see the IAR Embedded Workbench IDE User Guide. Note that a default device description file and linker command file is automatically selected depending on your selection of a device on the General Options>Target page. 4 To set the driver-specific options, select the appropriate driver from the Category list. Depending on which C-SPY driver you are using, a set of available options pages appears. For details about each page, see: Communication, page 6 Download, page 7. Note: For information about the C-SPY simulator, see the IAR Embedded Workbench IDE User Guide. 5 When you have set all the required options, click OK in the Options dialog box. 5

14 General debugger options COMMUNICATION With the options on the Communication page you can modify the behavior of the communication with the emulator. Figure 2: Emulator communication options USB Use this option if an emulator is connected to your host computer via a USB cable. If more than one emulator is connected, choose which one to use with the Serial No option. Log communication Use this option to log the communication between C-SPY and the target system to a file. To interpret the result, a detailed knowledge of the communication protocol is required. 6 IAR C-SPY Hardware Debugger Systems User Guide

15 Using the emulator DOWNLOAD The Download page contains the options related to downloading. Figure 3: Download page Verify download Select this option to check every byte after loading to verify the download and that the memory of the target hardware is writable and mapped in a consistent way. A warning message will be generated if there are any errors during download. Suppress download If you already have your application in memory, for instance when debugging a live target, select Suppress Download. The time-consuming downloading is then disabled. The implicit RESET performed at C-SPY startup is not disabled. 7

16 Hardware configuration Hardware configuration Before C-SPY is started for the first time in a new project, and when you change the device, the hardware must have been set up. If you have not set it up already by choosing Emulator>Hardware Setup, this dialog box will be displayed when you start the debugging session. Figure 4: Emulator Hardware Setup message Click OK to enter the Hardware Setup dialog box. See Hardware Setup, page 11. When the hardware setup is done and you click OK, the download of the debug file is started. If the debug file contains a memory area that is not defined in the hardware setup, several warnings will be displayed in the Debug Log window. The hardware setup is saved for each project and does not have to be set more than once. If you want to change the setup for a project, choose Hardware Setup from the Emulator menu. ID CODE VERIFICATION DIALOG BOX Some devices are read-protected with an ID code. If this is the case, a dialog box will be displayed. Figure 5: ID Code Verification dialog box 8 IAR C-SPY Hardware Debugger Systems User Guide

17 Using the emulator To be able to use a read-protected device, enter the correct seven bytes in hexadecimal notation. To protect the device, redefine the ID Code symbols in the extended linker command file. When the project is linked, this will reprogram the ID code in the internal flash ROM. Emulator menu The Emulator menu becomes available when you run the C-SPY E30A or the E30 driver. Figure 6: The Emulator menu Menu command Hardware Setup Download Firmware Events Trace Interval Time Measurement (E30A only) Breakpoint Usage Description Table 4: Description of Emulator menu commands TIME MEASUREMENT FOR E30A There are two separate time measurement debugging functions for the E30A driver: Execution time measurement Interval time measurement. Displays the Hardware Setup dialog box, in which the basic configuration for the emulator is done, see Hardware Setup, page 11. Opens the Download Firmware dialog box for selecting a firmware file to download to the target board, see Download Firmware, page 13. Opens the Events window where events can be viewed and modified, see Events window, page 14. Opens the Trace window where the recorded trace data is shown, see Trace window, page 21. Opens the Interval Time Measurement window where interval time measurement results are displayed and where time measurement points can be modified, see Interval Time Measurement window (E30A), page 25. Opens the Breakpoint Usage dialog box, which lists all activated breakpoints, see Breakpoint Usage dialog box, page 29. 9

18 Emulator menu Execution time measurement Execution time measurement uses two events one that defines a Time Start action and one that defines a Time End action to measure the program execution time from the start to the end of execution. The result in cycles will be displayed in the cycle counter register. These events are set up automatically from the context menu in the Events window, see Events window, page 14. Interval time measurement Interval time measurement measures the execution time in microseconds between two data accesses. You set up the events in the Interval Time Measurement Event dialog box and the measurement in the Interval Time Measurement window. See Interval Time Measurement Event dialog box (E30A), page 18 and Interval Time Measurement window (E30A), page 25, respectively. 10 IAR C-SPY Hardware Debugger Systems User Guide

19 Using the emulator HARDWARE SETUP In the Hardware Setup dialog box available from the Emulator menu you can configure the emulator debugger. Figure 7: Emulator Hardware Setup dialog box Note: This dialog box reflects the C-SPY E30A driver, some of the options are not available when using the C-SPY E30 driver. Clock Use the Clock options to set the CPU clock source: Option Xin Table 5: Emulator clock options Description Enter the frequency of the X in clock and specify the clock source: Generated uses a clock generated by the emulator Internal uses the target oscillator circuit board 11

20 Emulator menu Option PLL CCR Debug the program using the CPU rewrite mode Select this option if you are debugging the target system using the CPU Rewrite Mode. Note: When debugging in CPU Rewrite Mode, no software breakpoints can be set in the internal ROM area. Overwrite data in FLASH without erasing the FLASH area block If you select this option, writing to the flash memory area will merge the new data with the previous flash contents, and the addresses that are not being written to will keep their previous contents. E2 Data Flash is not erased on download Select this option if you want to preserve the contents of the E2 data flash memory. Memory map The Memory map list shows the emulation memory areas. These areas are set up in the *.mcu files in the..\r32c\config\renesas\e30a\r32c\ directory, or for the E30 driver in the..\r32c\config\renesas\e30\r32c\ directory. Monitor start address Use this option to specify the start address of the internal RAM area that is used by the debug monitor. Note: Approximately 1 Kbyte of the internal RAM will be used for other purposes, for instance to download your application. This means that you cannot specify a RAM area that overlaps the stack or an area that is accessed using DMA, but because the memory contents are saved before debugging starts it is not a problem otherwise. Emulator mode Description Table 5: Emulator clock options (Continued) Enter the frequency of the internal phase-locked loop of the target microcomputer. Enter the hexadecimal value of the internal clock control register of the target microcomputer. Use this option to specify debugging mode of the emulator debugger, choose between: Trace Enables the trace function. 12 IAR C-SPY Hardware Debugger Systems User Guide

21 Using the emulator RAM monitor Time measurement Enables the RAM-monitor function. Enables the time measurement functions. Note: The Emulator mode option is only available in the C-SPY E30A driver, not in the C-SPY E30 driver. This table lists the main differences between the modes: Debugging function Trace mode: Time Trace mode: MCU RAM monitor measurement Trace priority Execution mode mode priority Break, execution PC Yes Yes Yes Yes Break, data access Yes Yes Yes Yes Break, address area No No Yes No Break, data compare No Yes No No Trace Yes Yes No No Live watch No No Yes No Time measurement, execution time No No No Yes Time measurement, interval time Table 6: Emulator mode debugging functions Data acquisition interval of program execution Use this option to specify the (byte or word) data acquisition interval by the RAM monitor function during execution. The interval can be 1 10 milliseconds. This option can only be changed when the RAM monitor Emulator mode is selected. Factory Settings Click the Factory Settings button to restore the factory settings. DOWNLOAD FIRMWARE No No No Yes If you need to download new firmware, for example if you are changing the processor configuration or if you need to upgrade the firmware, choose the Emulator>Download Firmware command. The emulator firmware files have the filename extension.s and are located in subdirectories of the r32c\config\renesas\ directory of your product installation. 13

22 Emulator menu EVENTS WINDOW The Events window available from the Emulator menu is used for displaying and setting data break events, trace events, and RAM monitor events. Figure 8: Events window A total of 8 events, comprised of break events, trace events, and RAM monitor events in combination can be specified. Toolbar At the top of the window there is a toolbar: Operation Description Emulator mode Displays the selected emulator mode. E30A only. Edit settings Opens the Hardware Setup dialog box where you can change the emulator mode. E30A only. Trace area Displays the selected trace area, for more information see Trace Event dialog box, page 19. Trace mode Selects the trace mode to be used Save events to Saves the event log and the emulator mode setting to a file. E30A only. file Load events from file Table 7: Events window toolbar Loads the event log and the emulator mode setting from a file. E30A only. Choose between the following trace modes: MCU execution MCU execution with disassembler Gives priority to the MCU execution, and the trace range is 512 bytes. Gives priority to the MCU execution, and the trace range is 512 bytes. Includes disassembly. 14 IAR C-SPY Hardware Debugger Systems User Guide

23 Using the emulator Trace priority Trace priority with disassembler Gives priority to the trace data output, and the MCU execution is delayed. * Gives priority to the trace data output, and the MCU execution is delayed. Includes disassembly. * * For the trace priority and time measurement modes, pay attention to the following: 1) C-SPY will not automatically stop on breakpoints. When the CPU stops, you must click the Stop button to make C-SPY halt the execution. 2) If you do not want C-SPY to stop on main, disable the options Project>Options>Debugger>Run to main and Tools>Options>Stack>Stack pointer(s) not valid until program reaches main. The display area The Events window contains the following columns: Column The context menu Description Event The event number. Address The address of the event. Action The event type. Access The event access condition. Range The range condition. EQU means an address match event, IN means an address range event. Data Data used in data compare break. Mask Mask used in data compare break. Table 8: Events window columns If you right-click an emulator event in the Events window, a context menu appears with the following commands: Context menu command Edit Event Delete Event Description Edits the selected event. Note: Address match breaks cannot be edited from the Events window. Use the Breakpoints window (Edit>Breakpoints) to edit them. Deletes the selected event. Note: Address match breaks can not be deleted in the Events window. Use the Breakpoints window (Edit>Breakpoints) to delete them. Table 9: Description of Events window context menu commands 15

24 Emulator menu Context menu command New Trace Event New Data Break Event Description Opens the Trace Event dialog box, where you can create a new trace event. See Trace Event dialog box, page 19. Opens the Data Break Event dialog box, where you can create a new data break event. See Data Break Event dialog box, page 20. New RAM Monitor Event Creates a new RAM monitor event. The variable values displayed in the Live Watch window can be periodically updated by the RAM monitor function. In this case, the real-time capability of execution is not lost. The RAM monitor event must be set on event E5. New Execution Time Measurement Event New Interval Time Measurement Event Creates two events, one at event E0 that defines the Time Start action and one at event E4 that defines the Time End action, to use for execution time measurement. See Execution time measurement, page 10. E30A only. Opens the Interval Time Measurement dialog box where you can specify an interval time measurement event. See Interval time measurement, page 10. E30A only. Table 9: Description of Events window context menu commands (Continued) Note: Some types of events cannot be edited. They must be deleted and then created as new events. 16 IAR C-SPY Hardware Debugger Systems User Guide

25 Using the emulator TIME MEASUREMENT EVENT DIALOG BOX (E30) The Time Measurement Event dialog box available from the Events window context menu when you are using the C-SPY E30 Emulator allows you to measure the maximum, minimum, and average execution times in clock cycles and measurement counts of a specified memory section. The result of the measurement will be displayed in the cycle counters in the Register window. Figure 9: Time Measurement Event dialog box The Time Measurement Event dialog box contains the following options: Option Start address End address Access Table 10: Time Measurement Event dialog box options Description The start address of the time measurement. The end address of the time measurement. EXECUTE specifies an instruction execution event. The event is established when an instruction is executed from the specified address. READ or WRITE or R/W specifies a memory access event. The event is established when memory is accessed at the specified address or under conditions set for the specified address range. By specifying E0 as the start event and E4 as the end event, you can measure the execution time in a specified interval. 17

26 Emulator menu INTERVAL TIME MEASUREMENT EVENT DIALOG BOX (E30A) In the Interval Time Measurement Event dialog box available from the Events window context menu when you are using the C-SPY E30A Emulator you set up events to measure the execution times in microseconds between data accesses in a specified section of memory. Figure 10: Interval Time Measurement Event dialog box The Interval Time Measurement Event dialog box contains the following options: Option Address Description The address of the memory section to measure. Use the browse button to specify a predefined symbol instead of a hardwired address. Access READ, WRITE, or READ/WRITE specifies a data memory access type. Data compare Turns on data comparison. Data The data that triggers the event if matched. Mask The mask for the data comparison. Table 11: Interval Time Measurement Event dialog box options In the Interval Time Measurement window, you specify which of the events to use as start and stop events for the interval; see Interval Time Measurement window (E30A), page 25. The result of the measurement is also displayed in the Interval Time Measurement window. 18 IAR C-SPY Hardware Debugger Systems User Guide

27 Using the emulator TRACE EVENT DIALOG BOX In the Trace Event dialog box available from the Events window context menu you can set up and modify trace events. Figure 11: Trace Event dialog box A trace event can be either a branch or a data access, or a combination thereof. Trace Area Use these options to specify the trace area modes: Option Trace area Start address End address Access Table 12: Trace Area Description Selects the execution history that will be listed in the Trace window. Up to 512 cycles (branches or data accesses) can be listed with MCU Execution and up to 8,000,000 cycles with Trace priority. BREAK Lists trace cycles before the target application stops. BEFORE Lists trace cycles before the trace point. AFTER Lists trace cycles after the trace point. FULL Lists from the start until the trace memory is full. The address for the trace start condition when using the AFTER trace area. The address for the trace end condition when using the BEFORE trace area. The access condition for the event. 19

28 Emulator menu Trace Point The following Trace Point options are available: Option Access Range Address 1 Address 2 Table 13: Trace Point Description The access condition for the event. The trace point range condition. (addr) == Address1 Address match. The address matches Address1 below. Address1 <= (addr) <= Address2 Address range. The address is located between Address1 and Address2 below. The start address of the trace point address range or the address used for the trace point address match. Use the browse button to specify a predefined symbol instead of a hardwired address. Note that the browse button is not available in the C-SPY E30 driver. The end address of a trace point address range. Use the browse button to specify a predefined symbol instead of a hardwired address. Note that the browse button is not available in the C-SPY E30 driver. DATA BREAK EVENT DIALOG BOX In the Data Break Event dialog box available from the Events window context menu you can set up and modify data break events. Figure 12: Data Break Event dialog box 20 IAR C-SPY Hardware Debugger Systems User Guide

29 Using the emulator When you specify a break event for a memory access, you can specify the data to be compared with the data written to/read from a specified address. You can also specify mask bits for the comparison data. The Data Break Event dialog box contains the following options: Option Range Address 1 Address 2 Access Data compare Data Mask Description TRACE WINDOW A range condition. EQU means address match, IN means address range. The start address of the address range or the address used for the address match. The end address of an address range. The type of access that will trigger the event. The event is triggered when memory is accessed in this way at the specified address or under conditions set for the specified address range. Creates a data compare break. The data that should match to trigger the event. Mask for the data compare break. Table 14: Data Break Event dialog box options The Trace window available from the Emulator menu displays a recorded sequence of executed machine instructions. Figure 13: Trace window 21

30 Emulator menu Trace toolbar The following function buttons are available on the toolbar: Toolbar button Enable/Disable Clear trace data Toggle source Browse Find Save Edit settings Table 15: Trace toolbar commands The display area Description The Trace window contains the following columns: Enables and disables tracing. This button is not available in the Function trace window. Clears the trace buffer. Both the Trace window and the Function trace window are cleared. Toggles the Trace column between showing only disassembly or disassembly together with corresponding source code. Toggles browse mode on and off for a selected item in the Trace column. For more information about browse mode, see the IAR Embedded Workbench IDE User Guide. Opens the Find In Trace dialog box where you can perform a search; see Find in Trace dialog box, page 24. Opens a standard Save dialog box where you can save the recorded trace information to a text file, with tab-separated columns. Opens the Events window, where you can see and edit emulator events. See Events window, page 14. Trace window column Description Index A serial number for each row in the trace buffer. Trace The recorded sequence of executed machine instructions. TCNT Trace cycles, up to either 512 or 8,000,000 depending on used trace mode. Label Shows labels corresponding to address bus information. Src The state of the data bus. Dest The state of the address bus. Table 16: Trace window columns 22 IAR C-SPY Hardware Debugger Systems User Guide

31 Using the emulator Trace window column Size Status Description The size of the data access: B 8-bit W 16-bit L 32-bit Q 64-bit Shows the instruction status between the memory and I/O: JCnd Table 16: Trace window columns (Continued) For more information about using the trace system, see the IAR Embedded Workbench IDE User Guide. FIND IN TRACE WINDOW JMP (jump) is Branch information (also for RTS). The address in the Address column is the jump address. The address in the Data column is the branch instruction address. RD (read data) is Data access information. WD (write data) is Data access information. For conditional branches; 0 for jumps and 1 for non-jumps. The Find In Trace window available from the View>Messages menu displays the result of searches in the trace data. Figure 14: Find In Trace window The Find in Trace window looks like the Trace window, showing the same columns and data, but only those rows that match the specified search criteria. Double-clicking an item in the Find in Trace window brings up the same item in the Trace window. You specify the search criteria in the Find In Trace dialog box. For information about how to open this dialog box, see Find in Trace dialog box, page 24. For more information about using the trace system, see the IAR Embedded Workbench IDE User Guide. 23

32 Emulator menu FIND IN TRACE DIALOG BOX Use the Find in Trace dialog box available by choosing Edit>Find and Replace>Find or from the Trace window toolbar to specify the search criteria for advanced searches in the trace data. Note that the Edit>Find and Replace>Find command is context-dependent. It displays the Find in Trace dialog box if the Trace window is the current window or the Find dialog box if the editor window is the current window. Figure 15: Find in Trace dialog box The search results are displayed in the Find In Trace window available by choosing the View>Messages command, see Find In Trace window, page 23. In the Find in Trace dialog box, you specify the search criteria with the following settings: Text search A text field where you type the string you want to search for. Use the following options to fine-tune the search: Match Case Match whole word Only search in one column Searches only for occurrences that exactly match the case of the specified text. Otherwise specifying int will also find INT and Int. Searches only for the string when it occurs as a separate word. Otherwise int will also find print, sprintf and so on. Searches only in the column you selected from the drop-down menu. 24 IAR C-SPY Hardware Debugger Systems User Guide

33 Using the emulator Address Range Use the text fields to specify an address range. The trace data within the address range is displayed. If you also have specified a text string in the Text search field, the text string will be searched for within the address range. For more information about using the trace system, see the IAR Embedded Workbench IDE User Guide. INTERVAL TIME MEASUREMENT WINDOW (E30A) The Interval Time Measurement window available from the Emulator menu displays the time between data accesses in a specified section of memory. This window is also used for setting the time measurement points. Figure 16: Interval Time Measurement window Three check boxes allow you to specify up to three measurement points, numbered MP1 MP3. For every measurement point, you must specify a start event and a stop event. These events must be of the Interval Time Measurement Event type, see Interval Time Measurement Event dialog box (E30A), page 18. When you are done, click Set. Click the Clear button to clear the measurement data for the measurement point in question. The display area The Interval Time Measurement window contains the following columns: Column Description MP Identifies the measurement point. Min The fastest execution time for the measured interval, in microseconds. Max The slowest execution time for the measured interval, in microseconds. Average The average execution time for the measured interval, in microseconds. Table 17: Interval Time Measurement window columns 25

34 Breakpoints Column Description Count The number of times the time interval has been executed. Table 17: Interval Time Measurement window columns (Continued) Breakpoints This section describes issues related to breakpoints in the C-SPY hardware debugger systems. CODE BREAKPOINTS Code breakpoints are implemented as two different types of breakpoints. If you set a code breakpoint by right-clicking in the editor window, a default breakpoint will be set. For ROM memory, the default code breakpoint will be an execution address breakpoint if there are any free events to use. See Execution Address Breakpoint dialog box, page 26. If there are no free events, a software code breakpoint will be set. For RAM memory, the default code breakpoint will a software code breakpoint. See Software Breakpoint dialog box, page 28. These are considerably slower than the execution address breakpoints. If possible, use the execution address breakpoints, because they are much faster. EXECUTION ADDRESS BREAKPOINT DIALOG BOX To set an address breakpoint, right-click in the Breakpoints window and choose New Breakpoint>Address on the context menu. To modify an existing breakpoint, select it in the Breakpoints window and choose Edit on the context menu. 26 IAR C-SPY Hardware Debugger Systems User Guide

35 Using the emulator The Execution Address Breakpoint dialog box appears. Figure 17: Execution Address Breakpoint dialog box Break At Specify the location of the breakpoint in the Break At text box. Alternatively, click the Edit browse button to open the Enter Location dialog box; see the IAR Embedded Workbench IDE User Guide. Action You can optionally connect an action to a breakpoint. Specify an expression, for instance a C-SPY macro function, which is evaluated when the breakpoint is triggered and the condition is true. Conditions You can specify simple and complex conditions. Conditions Expression Condition true Condition changed Skip count Table 18: Breakpoint conditions Description A valid expression conforming to the C-SPY expression syntax. The breakpoint is triggered if the value of the expression is true. The breakpoint is triggered if the value of the expression has changed since it was last evaluated. The number of times that the breakpoint must be fulfilled before a break occurs (integer). 27

36 Breakpoints When an execution address breakpoint is triggered, there is no need for instruction rewrite/write back processing, which makes it fast. Up to eight address breakpoints can be set. They share events with data breaks, trace, the RAM monitor, and time measurement. SOFTWARE BREAKPOINT DIALOG BOX To set a software code breakpoint, right-click in the Breakpoints window and choose New Breakpoint>Software on the context menu. To modify an existing breakpoint, select it in the Breakpoints window and choose Edit on the context menu. The Software Breakpoint dialog box appears. Figure 18: Software Breakpoint dialog box Break At Specify the location of the breakpoint in the Break At text box. Alternatively, click the Edit browse button to open the Enter Location dialog box; see the IAR Embedded Workbench IDE User Guide. Action You can optionally connect an action to a breakpoint. Specify an expression, for instance a C-SPY macro function, which is evaluated when the breakpoint is triggered and the condition is true. 28 IAR C-SPY Hardware Debugger Systems User Guide

37 Using the emulator Conditions You can specify simple and complex conditions. Conditions Expression Condition true Condition changed Skip count Table 19: Breakpoint conditions Description A valid expression conforming to the C-SPY expression syntax. The breakpoint is triggered if the value of the expression is true. The breakpoint is triggered if the value of the expression has changed since it was last evaluated. The number of times that the breakpoint must be fulfilled before a break occurs (integer). When a software code breakpoint is set in the internal flash ROM of the target microcomputer, a number of instructions must be rewritten and processed every time it is triggered, which makes software code breakpoints slow. Up to 64 breakpoints can be set, both in RAM and ROM. BREAKPOINT USAGE DIALOG BOX The Breakpoint Usage dialog box available from the Emulator menu lists all active breakpoints. For more information, see the IAR Embedded Workbench IDE User Guide. C-SPY USE OF BREAKPOINTS When you set a breakpoint, C-SPY sets a breakpoint for internal use. To do this, the breakpoints in the emulator are used. The fact that C-SPY uses breakpoints is normally not a problem. However, one exception is C-SPY profiling, which requires many breakpoints. (The emulator has 64 software breakpoints and up to 8 hardware breakpoints.) C-SPY will set a breakpoint if: the C-SPY option Run to has been selected (one breakpoint is set temporarily after each reset) the stack plugin is being used (if the C-SPY option Run to has been selected, the breakpoint needed for that will be used also by the stack plugin) the linker option With runtime control modules has been selected (debug support for program termination and optionally file I/O). Exceeding the number of available breakpoints will cause the debugger to single step. This will significantly reduce the execution speed. You can prevent the debugger from using breakpoints in these situations by deselecting these options. 29