Renesas Emulator System SH7362 User Manual
  1. Manuals
  2. Brands
  3. Renesas Manuals
  4. Computer Hardware
  5. Emulator System SH7362
  6. User manual
Renesas Emulator System SH7362 User Manual

Renesas Emulator System SH7362 User Manual

Superh family e10a-usb emulator renesas microcomputer development environment system
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
To our customers,
Old Company Name in Catalogs and Other Documents
st
On April 1
, 2010, NEC Electronics Corporation merged with Renesas Technology
Corporation, and Renesas Electronics Corporation took over all the business of both
companies. Therefore, although the old company name remains in this document, it is a valid
Renesas Electronics document. We appreciate your understanding.
Renesas Electronics website:
Issued by: Renesas Electronics Corporation (http://www.renesas.com)
Send any inquiries to http://www.renesas.com/inquiry.
http://www.renesas.com
st
April 1
, 2010
Renesas Electronics Corporation

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Emulator System SH7362 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Renesas Emulator System SH7362

Summary of Contents for Renesas Emulator System SH7362

  • Page 1 On April 1 , 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding.
  • Page 2 Renesas Electronics. Renesas Electronics shall not be in any way liable for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for an application categorized as “Specific”...
  • Page 3 SuperH™ Family E10A-USB Emulator Additional Document for User’s Manual Supplementary Information on Using the SH7362 Renesas Microcomputer Development Environment System SuperH™ Family E10A-USB for SH7362 HS7362KCU01HE Rev.1.00 2007.08...
  • Page 5 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 7: 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 ... 2 Installing the H-UDI Port Connector on the User System ... 3 Pin Assignments of the H-UDI Port Connector ... 4 Recommended Circuit between the H-UDI Port Connector and the MPU...

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

    Section 1 Connecting the Emulator with the User System Components of the Emulator The E10A-USB emulator supports the SH7362. Table 1.1 lists the components of the emulator. Table 1.1 Components of the Emulator Classi- fication Component Hard- Emulator box ware User system interface cable User system interface...

  • Page 10: 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 an example of recommended connection between the connector and the MPU shown in this manual.

  • Page 11: 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 12: 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 13 Input/ SH7362 Signal Output Pin No. AUDCK Output Output AUDATA0 Output AUDATA1 Output AUDATA2 Output AUDATA3 /AUDSYNC Output N.C. N.C. Input Notes: 1. Input to or output from the user system. 2. The symbol (/) means that the signal is active-low. 3.
  • Page 14 Pin No. Signal /TRST /ASEBRK /BRKACK /RESETP /RESETA N.C. (GND) UVCC 10, 12, and 13 Notes: 1. Input to or output from the user system. 2. The symbol (/) means that the signal is active-low. 3. The emulator monitors the GND signal of the user system and detects whether or not the user system is connected.
  • Page 15 Input/ No. Signal Output N.C. N.C. MPMD (GND) N.C. /UCON (GND) Output AUDCK N.C. /ASEBRK/ Input/ BRKACK Output /RESETP Output /RESETA N.C. Output UVCC_AUD Output N.C. UVCC Output Input N.C. Input N.C. Input Notes: 1. Input to or output from the user system. 2.

  • Page 16: Recommended Circuit Between The H-Udi Port Connector And The Mpu

    Recommended Circuit between the H-UDI Port Connector and the 1.5.1 Recommended Circuit (36-Pin Type) Figure 1.5 shows a recommended circuit for connection between the H-UDI and AUD port connectors (36 pins) and the MPU when the emulator is in use. Notes: 1.
  • Page 17 When the circuit is connected as shown in figure 1.5, the switches of the emulator are set as SW2 = 1 and SW3 = 1. For details, refer to section 3.8, Setting the DIP Switches, in the SuperH Family E10A-USB Emulator User’s Manual. H-UDI port connector (36-pin type) AUDCK...

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

    3. When the voltage level of VccQ_SR (power supply for H-UDI and AUD) is 2.85 V and that of VccQ_MFI (power supply for /RESETA) is 1.8 V, a level-shift circuit is required as shown in the figure. 1.5.2 Recommended Circuit (14-Pin Type) Figure 1.6 shows a recommended circuit for connection between the H-UDI port connector (14 pins) and the MPU when the emulator is in use.
  • Page 19 When the circuit is connected as shown in figure 1.6, the switches of the emulator are set as SW2 = 1 and SW3 = 1. For details, refer to section 3.8, Setting the DIP Switches, in the SuperH Family E10A-USB Emulator User’s Manual. H-UDI port connector (14-pin type) TRST...

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

    1.5.3 Recommended Circuit (38-Pin Type) Figure 1.7 shows a recommended circuit for connection between the H-UDI and AUD port connectors (38 pins) and the MPU when the emulator is in use. Notes: 1. Do not connect anything to the N.C. pins of the H-UDI port connector. The MPMD pin must be 0 when the emulator is connected and 1 when the emulator is not connected, respectively.
  • Page 21 When the circuit is connected as shown in figure 1.7, the switches of the emulator are set as SW2 = 1 and SW3 = 1. For details, refer to section 3.8, Setting the DIP Switches, in the SuperH Family E10A-USB Emulator User’s Manual. VccQ_SR H-UDI port connector (38-pin type)
  • Page 22 Notes: 1. Do not use /RESETP in the emulator after the user system has been activated. When reset signals are used for debugging, use /RESETA. 2. Fix /RESETA as high level when it is not used. 3. When the voltage level of VccQ_SR (power supply for H-UDI and AUD) is 2.85 V and that of VccQ_MFI (power supply for /RESETA) is 1.8 V, a level-shift circuit is required as shown in the figure.

  • Page 23: Section 2 Software Specifications When Using The Sh7362

    Section 2 Software Specifications when Using the SH7362 Differences between the SH7362 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 actual SH7362 registers are undefined. When the emulator is initiated from the workspace, a value to be entered is saved in a session.
  • Page 24 3. Low-Power States (Sleep, Software Standby, Module Standby, U Standby, and R Standby) For low-power consumption, the SH7362 has sleep, software standby, module standby, U standby, and R standby states. The sleep, software standby, U Standby, and R Standby states are switched using the SLEEP instruction.
  • Page 25 7. Memory Access during User Program Break The emulator can download the program for the flash memory area (for details, refer to section 6.22, Download Function to the Flash Memory Area, in the SuperH Emulator User’s Manual). Other memory write operations are enabled for the RAM area. Therefore, an operation such as memory write or BREAKPOINT should be set only for the RAM area.
  • Page 26 11. MFI When the MFI boot mode is used, be sure to activate the emulator by setting the MFIINT signal as a trigger for the MFI transfer from the base-band side. 12. Memory Access during Break In the enabled MMU, when a memory is accessed and a TLB error occurs during break, it can be selected whether the TLB exception is controlled or the program jumps to the user exception handler in [TLB Mode] in the [Configuration] dialog box.
  • Page 27 The RCLK watchdog timer operates only when the user program is executed. Do not change the value of the frequency change register in the [IO] window or [Memory] window. The internal I/O registers can be accessed from the [IO] window. However, note the following when accessing the SDMR register of the bus-state controller.

  • Page 28: Specific Functions For The Emulator When Using The Sh7362

    Specific Functions for the Emulator when Using the SH7362 2.2.1 Event Condition Functions The emulator is used to set 12 event conditions (Ch1 to Ch12) and the software trace. Table 2.4 lists the conditions of Event Condition. Table 2.4 Types of Event Conditions Event Condition Type Address bus condition (Address) Data bus condition (Data)
  • Page 29 Table 2.5 Dialog Boxes for Setting Event Conditions Function Address Data ASID Dialog Condition Condition Condition (Address) (Data) (ASID) [Event Condition 1] dialog [Event Condition 2] dialog [Event Condition 3] dialog [Event Condition 4] dialog [Event Condition 5] dialog [Event Condition 6] dialog [Event...
  • Page 30 Table 2.5 Dialog Boxes for Setting Event Conditions (cont) Function Address Data ASID Dialog Condition Condition Condition (Address) (Data) (ASID) [Event Condition 9] dialog [Event Condition 10] dialog [Event Condition 11] dialog [Event Condition 12] dialog [Software trace] dialog Notes: O: Can be set in the dialog box.
  • Page 31 Sequential Setting: In the emulator, sequential setting of an Event Condition is enabled. Table 2.6 Sequential Event Conditions Type Event Condition [CPU 2 Channel Ch2 -> 1 Sequential Sequential Event] Page Ch4 -> 3 Ch6 -> 5 Ch11 -> 10 Many Ch3 ->...
  • Page 32 Table 2.6 Sequential Event Conditions (cont) Type Event Condition [CPU CPU Extend Sequential Event] Page (cont) [SystemBus SystemBus Ch9 -> 8 Sequential Sequential Event] Page Event Ch8 -> 9 SystemBus Extend Description Expands the [CPU Sequential Extend] page. The sequential setting is enabled with any combination.
  • Page 33 Sequential Break Extension Setting: Figure 2.1 [CPU Sequential Extend] Page (a) Indicates the channel name for setting conditions. (b) Selects a condition that is satisfied before the channel which sets up conditions. When a channel name is selected, it is required that the condition of the channel selected here must have already been satisfied.
  • Page 34 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 35 Figure 2.2 [Source] Window at Execution Halted (Sequential Break)

  • Page 36: Trace Functions

    2.2.2 Trace Functions The emulator supports the trace functions listed in table 2.7. Table 2.7 Trace Functions Function Branch trace Range memory access trace trace Software Table 2.8 shows the type numbers that the AUD function can be used. Table 2.8 Type Number and AUD Function Type Number HS0005KCU01H HS0005KCU02H...
  • Page 37 Branch Trace Functions: The branch source and destination addresses, their source lines, branch types, and types of accessed bus masters are displayed. [Setting Method] Select the check box in the [Branch] group box in the [Branch trace] page of the [Branch trace] dialog box that opens by double-clicking on the Ch12 (Branch) column of the [Eventpoint] window.
  • Page 38 Range Memory Access Trace Functions: The memory access within the specified range is acquired by a trace. The read cycle, write cycle, or read/write cycle can be selected as the bus type, ASID value, or bus cycle for trace acquisition. [Setting Method] (i) To open the [Event condition 5] or [Event condition 6] dialog box, double-click on the Ch5 (OA) or Ch6 (OA) column of the [Eventpoint] window.
  • Page 39 (iii) Open the [ASID] page, remove the check mark of the [Don’t care] check box, and enter the ASID value to be set. When the ASID value is not set as a condition, do not remove the check mark of the [Don’t care] check box.
  • Page 40 Software Trace Function: Note: This function can be supported with SHC/C++ compiler (manufactured by Renesas Technology Corp.; including OEM and bundle products) V6.0 or later. However, SHC/C++ compiler (including OEM and bundle products) V8.0 or later is needed when instructions other than those compatible with SH4 are output.
  • Page 41 AUD Trace Function: This function is operational when the AUD pin of the device is connected to the emulator. It is activated by selecting the [AUD trace] radio button in the [Trace type] group box of the [Trace mode] page. Set the trace condition to be used. [Restrictions] •...
  • Page 42 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 [Trace Mode 1] or [Trace Mode 2] group box in the [Trace Mode] page of the [Acquisition] dialog box.
  • Page 43 Notes on AUD Trace: 1. When the trace display is performed during user program execution, the mnemonics, operands, or source is not displayed. 2. The AUD branch trace function outputs the differences between newly output branch source addresses and previously output branch source addresses. The window trace function outputs the differences between newly output addresses and previously output addresses.
  • Page 44 Memory Output Trace Function: This function is activated by selecting the [Use Memory trace] radio button in the [Trace type] group box of the [Trace mode] page. In this function, write the trace data in the specified user memory range. Specify the start address to output a trace for the [Start] edit box in the [User memory area] group box, and the end address for the [End Address] edit box.
  • Page 45 To set the memory-output 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 [Trace Mode 1] or [Trace Mode 2] group box in the [Trace Mode] page of the [Acquisition] dialog box.

  • Page 46: Notes On Using The Jtag (H-Udi) Clock (Tck) And Aud Clock (Audck)

    Notes: 1. The memory range for which trace is output is the address on the system bus and not supported for the MMU or cache. 2. In the memory range for output, do not specify the ranges that the user program has been downloaded or the user program accesses.
  • Page 47 instructions cannot be set. For these cases, do not set BREAKPOINTs. Refer to the hardware manual for details. 7. When the [Normal] option is selected in the [Memory area] group box in the [General] page of the [Configuration] dialog box, a BREAKPOINT is set to a physical address or a virtual address according to the SH7362 MMU status during command input when the VPMAP_SET command setting is disabled.

  • Page 48: 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 49: Performance Measurement Function

    2.2.8 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. When a channel line on the [Performance Analysis] window is clicked with the right mouse button, the popup menu is displayed and the [Performance Analysis] dialog box is displayed by selecting [Setting].
  • Page 50 Note: For the command line syntax, refer to the online help. (a) Specifying the measurement start/end conditions Set the performance measurement conditions in the [Action] page after conditions have been set in the [Event Condition] dialog box that is opened by double-clicking Ch1 to Ch6 and Ch8 to Ch12 on the [Event Condition] sheet of the [Eventpoint] window.
  • Page 51 Table 2.11 Conditions Specified in the [Action] Page Item pa1_start_point pa1_end_point pa2_start_point pa2_end_point pa3_start_point pa3_end_point pa4_start_point pa4_end_point Description Specifies the conditions of Event Condition that has been set as the measurement start condition of performance channel 1. Specifies the conditions of Event Condition that has been set as the measurement end condition of performance channel 1.
  • Page 52 Figure 2.9 [Action] Page Note: PA1 or PA2 cannot be set for Ch8 and Ch9.
  • Page 53 (b) Measurement tolerance • The measured value includes tolerance. • Tolerance will be generated before or after a break. For details, see table 2.14. (c) Measurement items Items are measured in the [Performance Analysis] dialog box for each channel from Ch1 to Ch4.
  • Page 54 Table 2.12 Measurement Items Classification Type Disabled Cycle performance Instruction Branch Exception, interruption Measurement Item Option None Elapsed cycles Cycles executed in privileged mode Cycles for asserting the SR.BL bit Number of effective instructions issued Number of 2 instruction executed simultaneously Number of unconditional branch...
  • Page 55 Table 2.12 Measurement Items (cont) Classification Type Stalled performance cycle (cont) performance Instruction bus Instruction performance Measurement Item Option Cycles stalled in full- trace mode (with multi-counts) Cycles stalled in full- trace mode (without multi-counts) Number of UTLB miss for instruction fetch Number of UTLB miss for operand fetch Number of ITLB miss...
  • Page 56 Table 2.12 Measurement Items (cont) Classification Type Instruction bus Instruction performance (cont) (cont) Operand bus Access performance count Measurement Item Option Number of instruction cache miss Number of internal- RAM access for instruction fetch (XY-RAM or O-L memory) Number of I-L ILIF memory access for instruction fetch...
  • Page 57 Table 2.12 Measurement Items (cont) Classification Type Operand bus Access performance count (cont) (cont) Measurement Item Option Number of internal- RAM access for operand fetch (READ) (XY-RAM or O-L memory) Number of internal- RAM access for operand fetch (WRITE) (XY-RAM or O-L memory) Number of I-L ILRW...
  • Page 58 Table 2.12 Measurement Items (cont) Classification Type Operand bus Access performance miss count (cont) Waited cycle Measurement Item Option Number of operand cache miss (READ) Number of operand cache miss (WRITE) Number of U-RAM read-buffer miss Waited cycles for operand fetch (READ) Waited cycles for operand fetch...
  • Page 59 Table 2.12 Measurement Items (cont) Classification Type System bus System bus performance (only available for Ch3 and Ch4) Measurement Item Option Number of requests Number of responses Waited cycles for request Waited cycles for response Note The number of valid bus cycles (cells) is counted by the system bus clock.
  • Page 60 Table 2.13 shows the measurement items and methods that are mainly used. Table 2.13 Main Measurement Items Main Measurement Item Elapsed time Number of execution instructions Number of interrupts accepted Number of instruction fetches (for both cache and non-cache) Instruction-cache hit ratio Number of operand accesses (for both cache and non-cache) Operand-cache hit ratio (read)
  • Page 61 Each measurement condition is also counted when conditions in table 2.14 are generated. Table 2.14 Performance Measurement Conditions to be Counted Measurement Condition No caching due to the settings of TLB cacheable Cache-on counting Branch count Notes: 1. In the non-realtime trace mode of the AUD trace and memory output trace, normal counting cannot be performed because the generation state of the stall or the execution cycle is changed.
  • Page 63 Supplementary Information on Using the SH7362 Publication Date: Rev.1.00, August 20, 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 64 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 66 SuperH™ Family E10A-USB Emulator Additional Document for User’s Manual Supplementary Information on Using the SH7362 1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa 211-8668 Japan REJ10J1709-0100...

This manual is also suitable for:

E10a-usb

Table of Contents