REJ10J1828-0100 SuperH™ Family E10A-USB Emulator Additional Document for User’s Manual Supplementary Information on Using the SH7147 Group Debugging MCU Board Renesas Microcomputer Development Environment System SuperH™ Family E10A-USB for SH7147 HS7147DBKCU01HE Rev.1.00 Revision Date: Apr.
Rev. 1.00 Apr.
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.
Rev. 1.00 Apr.
Contents Section 1 About the Emulator............................................................................1 1.1 1.2 Components of the Emulator ............................................................................................ 1 Connecting the Emulator with the SH7147 Group Debugging MCU Board .................... 3 Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board.....................................................................5 2.1 2.
Rev. 1.00 Apr.
Section 1 About the Emulator Section 1 About the Emulator 1.1 Components of the Emulator The E10A-USB emulator supports the SH7147 group debugging MCU board. Table 1.1 lists the components of the emulator. Rev. 1.00 Apr.
Section 1 About the Emulator Table 1.1 Components of the Emulator Classification Component Hardware Emulator box Appearance Quantity 1 Remarks HS0005KCU01H: Depth: 65.0 mm, Width: 97.0 mm, Height: 20.0 mm, Mass: 72.9 g or HS0005KCU02H: Depth: 65.0 mm, Width: 97.0 mm, Height: 20.0 mm, Mass: 73.7 g Software User system interface cable 1 14-pin type: Length: 20 cm, Mass: 33.1 g User system interface cable 1 36-pin type: Length: 20 cm, Mass: 49.
Section 1 About the Emulator 1.2 Connecting the Emulator with the SH7147 Group Debugging MCU Board Table 1.2 shows the type number of the emulator, the corresponding connector type, and the use of AUD function. Table 1.2 Type Number, AUD Function, and Connector Type Type Number Connector AUD Function HS0005KCU02H 36-pin connector Available HS0005KCU01H, HS0005KCU02H 14-pin connector Not available The H-UDI port connector has the 36-pin and 14-pin types as described below.
Section 1 About the Emulator Rev. 1.00 Apr.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 2.1 Differences between the MCU and the Emulator 1. When the emulator system is initiated, it initializes the general registers and part of the control registers. The initial values of the MCU are undefined. When the emulator is initiated from the workspace, a value to be entered is saved in a session. Table 2.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Note: Do not break the user program when the _RES, _BREQ, or _WAIT signal is being low. A TIMEOUT error will occur. If the _BREQ or _WAIT signal is fixed to low during break, a TIMEOUT will occur at memory access. (Some MCUs will incorporate no _BREQ or _WAIT.) 5. Data Transfer Controller (DTC) When the MCU incorporates a DTC, the DTC operates even when the emulator is used.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 8. Using WDT The WDT does not operate during break. 9. Loading Sessions Information in [JTAG clock] of the [Configuration] dialog box cannot be recovered by loading sessions. Thus the TCK value will be as follows: ⎯ When HS0005KCU01H or HS0005KCU02H is used: TCK = 2.5 MHz 10. [IO] Window ⎯ Display and modification For each watchdog timer register, there are two registers to be separately used for write and read operations.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 2.2 2.2.1 Specific Functions and Notes for the Emulator when Using the SH7147 Group Debugging MCU Board Selecting the Target MCU Select the target MCU for the emulator according to that in use. For details, refer to section 4, Preparations for Debugging, in the SuperH™ Family E10A-USB Emulator User’s Manual.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Table 2.5 lists the types of Event Condition. Table 2.5 Types of Event Condition Event Condition Type Description Address bus condition (Address) Sets a condition when the address bus (data access) value or the program counter value (before or after execution of instructions) is matched. Data bus condition (Data) Sets a condition when the data bus value is matched.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Table 2.6 lists the combinations of conditions that can be set under Ch1 to Ch10. Table 2.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Sequential Setting: Using the [Combination action (Sequential or PtoP)] dialog box specifies the sequential condition and the start or end of performance measurement. Table 2.7 Conditions to Be Set Classification Item [Ch1, 2, 3] list box Sets the sequential condition and the start or end of performance measurement using Event Conditions 1 to 3.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 2. If the start condition is satisfied after the end condition has been satisfied by the pointto-point of the internal trace, trace acquisition will be restarted. 3. When the start or end of performance measurement is used, the count for specifying the condition of Event Condition 1 must be once. Usage Example of Sequential Break Extension Setting: A tutorial program provided for the product is used as an example.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Figure 2.1 [Source] Window at Execution Halted (Sequential Break) If the sequential condition, performance measurement start/end, or point-to-point for the internal trace is set, conditions of Event Condition to be used will be disabled. Such conditions must be enabled from the popup menu by clicking the right mouse button on the [Event Condition] sheet. Notes: 1.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 5. If the settings of the Event condition or the sequential conditions are changed during execution of the program, execution will be suspended. (The number of clocks to be suspended during execution of the program is a maximum of about 52 bus clocks (Bφ). If the bus clock (Bφ) is 10.0 MHz, the program will be suspended for 5.2 μs.) 6.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Internal Trace Function: When [I-Trace] is selected for [Trace type] on the [Trace Mode] page of the [Acquisition] dialog box, the internal trace can be used. Figure 2.2 [Acquisition] Dialog Box (Internal Trace Function) Rev. 1.00 Apr.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board The following three items can be selected as the internal trace from [Type] of [I-Trace mode]. Table 2.10 Information on Acquiring the Internal Trace Item Acquisition Information [L-Bus & Branch] Acquires the data and branch information on the L-bus. • Data access (read/write) • Branch information • Instruction fetch [I-Bus] Acquires the data on the I-bus.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Using Event Condition restricts the condition; the following three items are set as the internal trace conditions. Table 2.11 Trace Conditions of the Internal Trace Item Acquisition Information Trace halt Acquires the internal trace until the Event Condition is satisfied. (The trace content is displayed in the [Trace] window after a trace has been halted. No break occurs in the user program.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Set the address condition as H’2000 in the [Event Condition 4] dialog box. Set [Ch4,5] as [I-Trace Ch5 to Ch4 PtoP] in the [Combination action (Sequential or PtoP)] dialog box. When point-to-point and trace acquisition condition are set simultaneously, they are ANDed. Notes on Internal Trace: • Timestamp The timestamp is twice the crystal oscillator or the external clock that is connected to or input to the target MCU.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board • Trace acquisition condition Do not set the trace end condition for the sleep instruction and the branch instruction according to which the delay slot becomes the sleep instruction. When [I-Bus, L-Bus & Branch] is selected and the trace acquisition condition is set for the Lbus and I-bus with Event Condition, set the L-bus condition and the I-bus condition for [Event Condition 1] and [Event Condition 2], respectively.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board AUD Trace Functions: This function is operational when the AUD pin of the device is connected to the emulator. Table 2.13 shows the AUD trace acquisition mode that can be set in each trace function. Table 2.13 AUD Trace Acquisition Mode Type Mode Description Continuous trace occurs Realtime trace When the next branch occurs while the trace information is being output, all the information may not be output.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Figure 2.3 [Trace mode] Page When the AUD trace function is used, select the [AUD function] radio button in the [Trace type] group box of the [Trace mode] page. Rev. 1.00 Apr.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board (a) Branch Trace Function The branch source and destination addresses and their source lines are displayed. Branch trace can be acquired by selecting the [Branch trace] check box in the [AUD function] group box of the [Trace mode] page. The branch type can be selected in the [AUD Branch trace] page. Figure 2.4 [AUD Branch trace] Page\ Rev. 1.00 Apr.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board (b) Window Trace Function Memory access in the specified range can be acquired by trace. Two memory ranges can be specified for channels A and B. The read, write, or read/write cycle can be selected as the bus cycle for trace acquisition. [Setting Method] (i) Select the [Channel A] and [Channel B] check boxes in the [AUD function] group box of the [Trace mode] page. Each channel will become valid.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board (c) Software Trace Function Note: This function can be supported with SHC/C++ compiler (manufactured by Renesas Technology Corp.; including OEM and bundle products) V7.0 or later. When a specific instruction is executed, the PC value at execution and the contents of one general register are acquired by trace. Describe the Trace(x) function (x is a variable name) to be compiled and linked beforehand.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 2.2.4 Note on Using the JTAG (H-UDI) Clock (TCK) 1. Set the JTAG clock (TCK) frequency as a value that is lower than the frequency of the peripheral clock (Pφ) and 1/4 or lower than the frequency of the bus clock (Bφ). 2. The initial value of the JTAG clock (TCK) is 2.5 MHz. 3. A value to be set for the JTAG clock (TCK) is initialized after executing [Reset CPU] or [Reset Go]. Thus the TCK value will be 2.5 MHz. 2.2.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 2.2.7 Performance Measurement Function The emulator supports the performance measurement function. 1. Setting the performance measurement conditions To set the performance measurement conditions, use the [Performance Analysis] dialog box and the PERFORMANCE_SET command.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Figure 2.6 [Performance Analysis] Dialog Box For measurement tolerance, • The measured value includes tolerance. • Tolerance will be generated before or after a break. Note: When [Ch2 to Ch1 PA] or [Ch1 to Ch2 PA] is selected, to execute the user program, specify conditions set in Event Condition 2 and Event Condition 1 and one or more items for performance measurement.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Table 2.15 Measurement Item Selected Name Option Disabled None Elapsed time AC (The number of execution cycles (Iφ) is set as the measurement item.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board 3. Initializing the measured result To initialize the measured result, select [Initialize] from the popup menu in the [Performance Analysis] window or specify INIT with the PERFORMANCE_ANALYSIS command. Rev. 1.00 Apr.
Section 2 Software Specifications when Using the SH7147 Group Debugging MCU Board Rev. 1.00 Apr.
SuperH™ Family E10A-USB Emulator Additional Document for User's Manual Supplementary Information on Using the SH7147 Group Debugging MCU Board Publication Date: Rev.1.00, April 4, 2008 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Customer Support Department Global Strategic Communication Div. Renesas Solutions Corp. ©2008. Renesas Technology Corp., All rights reserved. Printed in Japan.
Sales Strategic Planning Div. Nippon Bldg., 2-6-2, Ohte-machi, Chiyoda-ku, Tokyo 100-0004, Japan RENESAS SALES OFFICES http://www.renesas.com Refer to "http://www.renesas.com/en/network" for the latest and detailed information. Renesas Technology America, Inc. 450 Holger Way, San Jose, CA 95134-1368, U.S.A Tel: <1> (408) 382-7500, Fax: <1> (408) 382-7501 Renesas Technology Europe Limited Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K.
SuperH™ Family E10A-USB Emulator Additional Document for User’s Manual Supplementary Information on Using the SH7147 Group Debugging MCU Board
