Renesas SuperH HS0720KCU01HE Addendum
  1. Manuals
  2. Brands
  3. Renesas Manuals
  4. Computer Hardware
  5. SuperH HS0720KCU01HE
  6. Addendum
Renesas SuperH HS0720KCU01HE Addendum

Renesas SuperH HS0720KCU01HE Addendum

E10a-usb emulator
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
REJ10J1465-0200
SuperH™ Family E10A-USB Emulator
Additional Document for User's Manual
Supplementary Information on Using the SH2A_custom_SoC
Renesas Microcomputer Development Environment System
SuperH™ Family / SH7200 Series
E10A-USB for SH2A_custom_SoC HS0720KCU01HE
Rev.2.00
Revision Date: Apr. 10, 2007

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SuperH HS0720KCU01HE and is the answer not in the manual?

Questions and answers

Related Manuals for Renesas SuperH HS0720KCU01HE

Summary of Contents for Renesas SuperH HS0720KCU01HE

  • Page 1 REJ10J1465-0200 SuperH™ Family E10A-USB Emulator Additional Document for User’s Manual Supplementary Information on Using the SH2A_custom_SoC Renesas Microcomputer Development Environment System SuperH™ Family / SH7200 Series E10A-USB for SH2A_custom_SoC HS0720KCU01HE Rev.2.00 Revision Date: Apr. 10, 2007...
  • Page 3 Please be sure to implement safety measures to guard against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a Renesas product, such as safety design for hardware and software including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging degradation or any other applicable measures.

  • Page 5: Table Of Contents

    Section 1 Connecting the Emulator with the User System ...1 Components of the Emulator ... 1 Connecting the Emulator with the User System ... 3 Installing the H-UDI Port Connector on the User System ... 4 Pin Assignments of the H-UDI Port Connector ... 5 Recommended Circuit between the H-UDI Port Connector and the MCU ...

  • Page 7: Section 1 Connecting The Emulator With The User System

    Components of the Emulator The E10A-USB emulator supports the SH2A_custom_SoC_1 and SH2A_custom_SoC_2. For the selection of the SH2A_custom_SoC_1 or SH2A_custom_SoC_2 when using the emulator, ask Renesas Technology Corp. via the sales office. Table 1.1 lists the components of the emulator.
  • Page 8 Table 1.1 Components of the Emulator Classi- fication Component Hard- Emulator box ware User system interface cable User system interface cable USB cable Soft- E10A-USB emulator setup program, ware SuperH Family E10A- USB Emulator User’s Manual, Supplementary Information on Using the SH2A_custom_SoC*, and Test program manual for HS0005KCU01H and...

  • Page 9: Connecting The Emulator With The User System

    Connecting the Emulator with the User System To connect the E10A-USB emulator (hereinafter referred to as the emulator), the H-UDI port connector must be installed on the user system to connect the user system interface cable. When designing the user system, refer to the recommended circuit between the H-UDI port connector and the MCU.

  • Page 10: Installing The H-Udi Port Connector On The User System

    Installing the H-UDI Port Connector on the User System Table 1.3 shows the recommended H-UDI port connectors for the emulator. Table 1.3 Recommended H-UDI Port Connectors Connector Type Number 36-pin connector DX10M-36S DX10M-36SE, DX10G1M-36SE 14-pin connector 2514-6002 38-pin connector 2-5767004-2 Note: When designing the 36-pin connector layout on the user board, do not connect any components under the H-UDI connector.

  • Page 11: Pin Assignments Of The H-Udi Port Connector

    2-5767004-2 Target system Figure 1.1 Restriction on Component Mounting Pin Assignments of the H-UDI Port Connector Figures 1.2 through 1.4 show the pin assignments of the 36-pin, 14-pin, and 38-pin H-UDI port connectors, respectively. Note: Note that the pin number assignments of the H-UDI port connector shown on the following pages differ from those of the connector manufacturer.
  • Page 12 (1) Pin Assignments of the 36-pin H-UDI Port Connector Note: The signal names are standard for the SH7200 series MCU. For the pin names of MCUs and recommended circuits for connection, ask Renesas Technology Corp. via the sales office. Input/Output...
  • Page 13 (2) Pin Assignments of the 14-pin H-UDI Port Connector Note: The signal names are standard for the SH7200 series MCU. For the pin names of MCUs and recommended circuits for connection, ask Renesas Technology Corp. via the sales office. Pin No.
  • Page 14 (3) Pin Assignments of the 38-pin H-UDI Port Connector Input/ No. Signal Output N.C. N.C. ASEMD# (GND) N.C. UCON# (GND) Output AUDCK N.C. ASEBRKAK#/ Input/ ASEBRK# Output Output RES# N.C. Output UVCC_AUD Output N.C. UVCC Output Input N.C. Input N.C. Input Notes: 1.

  • Page 15: Recommended Circuit Between The H-Udi Port Connector And The Mcu

    The connection between the H-UDI and AUD port connectors and MCUs differs according to the internal circuits of the MCU in use. The following shows an example, however, ask Renesas Technology Corp. via the sales office for the pull-up, pull-down, and required logic ICs.
  • Page 16 Figure 1.5 Recommended Circuit for Connection between the H-UDI Port Connector and MCU when the Emulator is in Use (36-Pin Type) Note: For the pin names of MCUs and recommended circuits for connection, ask Renesas Technology Corp. via the sales office.

  • Page 17: Recommended Circuit (14-Pin Type)

    The connection between the H-UDI port connector and MCUs differs according to the internal circuits of the MCU in use. The following shows an example, however, ask Renesas Technology Corp. via the sales office for the pull-up, pull-down, and required logic ICs.
  • Page 18 Figure 1.6 Recommended Circuit for Connection between the H-UDI Port Connector and MCU when the Emulator is in Use (14-Pin Type) Note: For the pin names of MCUs and recommended circuits for connection, ask Renesas Technology Corp. via the sales office.

  • Page 19: Recommended Circuit (38-Pin Type)

    The connection between the H-UDI and AUD port connectors and MCUs differs according to the internal circuits of the MCU in use. The following shows an example, however, ask Renesas Technology Corp. via the sales office for the pull-up, pull-down, and required logic ICs.
  • Page 20 Figure 1.7 Recommended Circuit for Connection between the H-UDI Port Connector and MCU when the Emulator is in Use (38-Pin Type) Note: For the pin names of MCUs and recommended circuits for connection, ask Renesas Technology Corp. via the sales office.

  • Page 21: Section 2 Software Specifications When Using The Sh2A_Custom_Soc

    Section 2 Software Specifications when Using the 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 as shown in table 2.1. 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.
  • Page 22 3. Low-Power States • When the emulator is used, the sleep state can be cleared with either the clearing function or with the [STOP] button, and a break will occur. • The memory must not be accessed or modified in software standby state. •...
  • Page 23 Table 2.3 Stopping Time by Memory Access (Reference) Method Condition H-UDI read/write Reading of one longword for the internal RAM Writing of one longword for the internal RAM Short break CPU clock: 160 MHz JTAG clock: 20 MHz Reading or writing of one longword for the external area 7.
  • Page 24 8. Operation while Cache is Enabled When cache is enabled, the emulator operates as shown in table 2.4. Table 2.4 Operation while Cache is Enabled Function Operation Memory write Searches for whether or not the address to be written hits the instruction and operand caches. •...
  • Page 25 AUD pins before executing the user program. When those registers are changed by the user program, note that the settings of the AUD pins will not be changed. For details of the setting methods and values, ask Renesas Technology Corp. via the sales office. 10. Using WDT The WDT does not operate during break.
  • Page 26 15. Contention between the Change of the FRQCR Register and the Debugging Functions The following notes are required for the user program for changing the multiplication rate of PLL circuit 1 to change the frequency: • Avoid contention between the change of the FRQCR register in the user program and the memory access from the [Memory] window, etc.

  • Page 27: Specific Functions For The Emulator When Using The Sh2A_Custom_Soc

    Specific Functions for the Emulator when Using the SH2A_custom_SoC 2.2.1 Event Condition Functions The emulator is used to set event conditions for the following three functions: • Break of the user program • Internal trace • Start or end of performance measurement Table 2.5 lists the types of Event Condition.
  • Page 28 Table 2.6 Dialog Boxes for Setting Event Conditions Function Address Bus Condition Dialog Box (Address) [Event Condition 1] [Event Condition 2] [Event Condition 3] [Event Condition 4] [Event Condition 5] [Event Condition 6] [Event Condition 7] [Event Condition 8] [Event Condition 9] [Event Ch10...
  • Page 29 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 and 11.
  • Page 30 Table 2.7 Conditions to Be Set (cont) Classification Item [Ch1, 2, 3] list box Ch1 to Ch2 PA (cont) [Ch4, 5] list box Sets the point-to-point of the internal trace (the start or end condition of trace acquisition) using Event Conditions 4 and 5. Don’t care I-Trace: Ch5 to Ch4 PtoP...
  • Page 31 Usage Example of Sequential Break Extension Setting: A tutorial program provided for the product is used as an example. For the tutorial program, refer to section 6, Tutorial, in the SuperH Family E10A-USB Emulator User’s Manual. The conditions of Event Condition are set as follows: 1.
  • Page 32 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.

  • Page 33: Trace Functions

    7. 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 102 bus clocks (Bφ).
  • Page 34 Table 2.9 shows the type numbers that the AUD function can be used. Table 2.9 Type Number and AUD Function Type Number HS0005KCU01H HS0005KCU02H The internal and AUD traces are set in the [Acquisition] dialog box of the [Trace] window. 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.
  • Page 35 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 [M-Bus & Branch] [I-Bus] [I-Bus, M-Bus & Branch] After selecting [Type] of [I-Trace mode], select the content to be acquired from [Acquisition]. Typical examples are described below (note that items disabled for [Acquisition] are not acquired).
  • Page 36 To restrict trace acquisition to access for only a specific address or specific function of a program, an Event Condition can be used. Typical examples are described below. • Example of halting a trace with a write access (M-bus) to H’FFF80000 by the user program as a condition (trace halt): Set the condition to be acquired on [I-Trace mode].
  • Page 37 Notes on Internal Trace: • Timestamp The timestamp is the clock counts of Bφ (48-bit counter). Table 2.12 shows the timing for acquiring the timestamp. Table 2.12 Timing for the Timestamp Acquisition Item Acquisition Information M-bus data access Branch I-bus Fetch Data access •...
  • Page 38 • 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, M-Bus & Branch] is selected and the trace acquisition condition is set for the M- bus and I-bus with Event Condition, set the M-bus condition and the I-bus condition for [Event Condition 1] and [Event Condition 2], respectively.
  • Page 39 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 Continuous...
  • Page 40 To set the AUD trace acquisition mode, click the [Trace] window with the right mouse button and select [Setting] from the pop-up menu to display the [Acquisition] dialog box. The AUD trace acquisition mode can be set in the [AUD mode1] or [AUD mode2] group box in the [Trace mode] page of the [Acquisition] dialog box.
  • Page 41 When the AUD trace function is used, select the [AUD function] radio button in the [Trace type] group box of the [Trace mode] page. (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.
  • Page 42 Figure 2.4 [AUD Branch trace] Page (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.
  • Page 43 [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. (ii) Open the [Window trace] page and specify the bus cycle, memory range, and bus type that are to be set for each channel.
  • Page 44 (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.

  • Page 45: Notes On Using The Jtag (H-Udi) Clock (Tck)

    8. For the result by software trace, a value in the [Data] item is not correct (that value is correct for window trace). 2.2.3 Notes on Using the JTAG (H-UDI) Clock (TCK) 1. Set the JTAG clock (TCK) frequency to lower than the frequency of the peripheral module clock.

  • Page 46: Notes On Setting The [Event Condition] Dialog Box And The Breakcondition_ Set Command

    2.2.5 Notes on Setting the [Event Condition] Dialog Box and the BREAKCONDITION_ SET Command 1. When [Go to cursor], [Step In], [Step Over], or [Step Out] is selected, the settings of Event Condition 3 are disabled. 2. When an Event Condition is satisfied, emulation may stop after two or more instructions have been executed.
  • Page 47 (a) Specifying the measurement start/end conditions The measurement start/end conditions are specified by using Event Condition 1,2. The [Ch1,2,3] list box of the [Combination action (Sequential or PtoP)] dialog box can be used. Table 2.14 Measurement Period Classification Item Selection in Ch2 to Ch1 the [Ch1, 2, 3] list box...
  • Page 48 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. (b) Measurement item Items are measured with [Channel 1 to 4] in the [Performance Analysis] dialog box.
  • Page 49 Table 2.15 Measurement Item Selected Name Disabled Elapsed time Branch instruction counts Number of execution instructions Number of execution 32bit-instructions Exception/interrupt counts Interrupt counts Data cache-miss counts Instruction cache-miss counts All area access counts All area instruction access counts All area data access counts Cacheable area access counts Cacheable area instruction access counts Non cacheable area data access counts...
  • Page 50 Notes: 1. In the non-realtime trace mode of the AUD trace, normal counting cannot be performed because the generation state of the stall or the execution cycle is changed. 2. If the internal ROM is not installed on the product, do not set the measurement item for the internal ROM area.
  • Page 51 Publication Date: Rev.1.00, September 7, 2007 Rev.2.00, April 10, 2007 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Customer Support Department Global Strategic Communication Div. Renesas Solutions Corp. ©2007. Renesas Technology Corp., All rights reserved. Printed in Japan.
  • Page 52 Nippon Bldg., 2-6-2, Ohte-machi, Chiyoda-ku, Tokyo 100-0004, Japan http://www.renesas.com RENESAS SALES OFFICES 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.
  • Page 54 SuperH™ Family E10A-USB Emulator Additional Document for User’s Manual Supplementary Information on Using the SH2A_custom_SoC...

This manual is also suitable for:

Superh sh7200 seriesSuperh e10a-usb

Table of Contents