REJ10J1130-0900 H8SX E6000H Emulator User’s Manual Renesas Microcomputer Development Environment System H8SX Family / H8SX/1650 Group H8SX/1520 Group H8SX/1544 Group HS1650EPH60HE Rev.9.00 Revision Date: Jun.
Keep safety first in your circuit designs! 1. Renesas Technology Corp. puts the maximum effort into making semiconductor products better and more reliable, but there is always the possibility that trouble may occur with them. Trouble with semiconductors may lead to personal injury, fire or property damage.
IMPORTANT INFORMATION READ FIRST • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. Emulator Product: Throughout this document, the term "emulator product" shall be defined as the following products produced only by Renesas Technology Corp. excluding all subsidiary products.
LIMITED WARRANTY Renesas warrants its emulator products to be manufactured in accordance with published specifications and free from defects in material and/or workmanship. Renesas, at its option, will repair or replace any emulator products returned intact to the factory, transportation charges prepaid, which Renesas, upon inspection, determine to be defective in material and/or workmanship. The foregoing shall constitute the sole remedy for any breach of Renesas' warranty.
State Law: Some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, so the above limitation or exclusion may not apply to you. This warranty gives you specific legal rights, and you may have other rights which may vary from state to state.
SAFETY PAGE READ FIRST • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. DEFINITION OF SIGNAL WORDS This is the safety alert symbol. It is used to alert you to potential personal injury hazards. Obey all safety messages that follow this symbol to avoid possible injury or death.
WARNING Observe the precautions listed below. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator product or will result in PERSONAL INJURY. The USER PROGRAM will be LOST. 1. Carefully handle the emulator product to prevent receiving an electric shock because the emulator product has a DC power supply. Do not repair or remodel the emulator product by yourself for electric shock prevention and quality assurance. 2.
Warnings on Emulator Usage Warnings described below apply as long as you use this emulator. Be sure to read and understand the warnings below before using this emulator. Note that these are the main warnings, not the complete list. WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES or PARTS. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator product or will result in PERSONAL INJURY. The USER PROGRAM will be LOST.
CAUTION Place the emulator station and evaluation chip board so that the trace cables are not bent or twisted. A bent or twisted cable will impose stress on the user interface leading to connection or contact failure. Make sure that the emulator station is placed in a secure position so that it does not move during use nor impose stress on the user interface.
CAUTION This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
Preface Thank you for purchasing the E6000H emulator. CAUTION Read this manual before using the emulator product. Incorrect operation or connection will damage the user system, the emulator product, and the user program. The E6000H emulator is an efficient software and hardware development support tool for application systems using the microcomputer developed by Renesas Technology Corp.
About This Manual This manual is comprised of two parts: Hardware Part and Debugger Part. Hardware Part: Preparation before use, hardware specifications, and troubleshooting procedure. Debugger Part: A peculiar debugging function to the emulator, tutorial, emulator software specification, and notes. This manual describes the debugging function for H8SX E6000H Emulator debugger that used with the High-performance Embedded Workshop.
Contents H8SX/1650 Hardware Part Section 1 Overview........................................................................................... 1 1.1 1.2 1.3 Notes on Usage .................................................................................................................1 Emulator Hardware Components ......................................................................................2 1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances).................
H8SX/1527 and H8SX/1527R Hardware Part Section 1 Overview ...........................................................................................1 1.1 1.2 1.3 Notes on Usage ................................................................................................................. 1 Emulator Hardware Components ...................................................................................... 2 1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances).........
H8SX/1544 Hardware Part Section 1 Overview........................................................................................... 1 1.1 1.2 1.3 Notes on Usage .................................................................................................................1 Emulator Hardware Components ......................................................................................2 1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances)..........................
4.3 Diagnostic Test Procedure Using the Diagnostic Program ............................................... 34 Debugger Part Section 1 Overview ...........................................................................................1 Section 2 Preparation before Use ......................................................................3 2.1 2.2 2.3 2.4 Method for Activating High-performance Embedded Workshop..................................... 3 2.1.1 Creating a New Workspace (Toolchain Not Used)....
3.7.10 Viewing the Source Line for an Event Point........................................................46 3.7.11 Setting a Data Condition for a Variable in the Source Program ..........................46 3.8 Viewing the Trace Information .........................................................................................47 3.8.1 Opening the [Trace] Window ..............................................................................47 3.8.2 Acquiring Trace Information ................................
4.12 Displaying Local Variables............................................................................................... 101 4.13 Stepping Through a Program ............................................................................................ 102 4.13.1 Executing the [Step In] Command....................................................................... 102 4.13.2 Executing the [Step Out] Command .................................................................... 104 4.13.
Section 6 Error Messages.................................................................................. 153 6.1 Error Messages of the Emulator........................................................................................153 6.1.1 Error Messages at Emulator Initiation .................................................................153 6.1.2 Error Messages during Emulation........................................................................155 Appendix A Menus ..............................
H8SX/1650 Hardware Part
Section 1 Overview 1.1 Notes on Usage CAUTION READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. 1. Check all components with the component list after unpacking the emulator. 2. Never place heavy objects on the casing. 3.
1.2 Emulator Hardware Components The emulator consists of an E6000H station and an evaluation chip board. By installing a user system interface board (option) on your host computer, the emulator can be connected in the same package as the device. PC interface (option) includes a PC interface board (PCI bus and PC card bus), a LAN adapter (connected with the network), and a USB adapter (connected with the USB interface).
1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances) The names of the components on the front/rear panel of the E6000H station are listed below. Front Panel: Figure 1.2 E6000H Station: Front Panel (a): POWER lamp: Is lit up while the E6000H station is supplied with power. (b): RUN lamp: Is lit up while the user program is running.
Rear Panel: Figure 1.3 E6000H Station: Rear Panel (a) Power switch: Turning this switch to I (input) supplies power to the emulator (E6000H station and evaluation chip board). (b) AC power connector: For an AC 100-V to 240-V power supply. (c) PC interface cable connector: For the PC interface cable that connects the host computer to the E6000H station. A PC interface board, PC card interface, LAN adapter, or USB adapter can be connected. Marked PC/IF.
1.2.2 Evaluation Chip Board Configuration The names of the components on the evaluation chip board of the emulator are listed below. Figure 1.4 Evaluation Chip Board (a) Station to evaluation chip board interface connector cover: This is a cover for protecting the connector that connects the E6000H station to the evaluation chip board. (b) Crystal oscillator terminals: For installing a crystal oscillator to be used as an external clock source for the MCU.
1.3 System Configuration The emulator must be connected to a host computer via the selected PC interface board (PCI bus or PC card bus), LAN adapter, or USB adapter. For details on the PC interface boards (available for PCI bus and PC card bus specifications), the LAN adapter, and the USB adapter, refer to the relevant descriptive documents. 1.3.1 System Configuration Using Various Interfaces (1) PC Interface Board Figure 1.5 shows the configuration of a system in which the PC interface board is used.
(3) USB Adapter Figure 1.7 shows the configuration of a system in which the USB adapter is used. A USB adapter can be used to connect the emulator to a host computer with the USB interface. E6000H emulator PCIF USB adapter Host computer USB cable PC interface cable Figure 1.
8
Section 2 Preparation before Use 2.1 Description on Emulator Usage This section describes the preparation before emulator usage. Figure 2.1 is a flowchart on preparation before use of the emulator. CAUTION Read this section and understand its contents before preparation. Incorrect operation will damage the user system and the emulator. The USER PROGRAM will be LOST. Reference: Connect the emulator. Set up the emulator on each OS. Start debugging. Described in this section.
2.2 Emulator Connection The following description covers connection of the emulator. 2.2.1 Connecting the Emulator to the User System WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator or will result in PERSONAL INJURY. The USER PROGRAM will be LOST. 1. Check that the emulator power switch is turned off.
2.2.3 Connection by the User System Interface Connectors WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES. Failure to do so will result in a FIRE HAZARD, and will damage the user system or emulator or result in PERSONAL INJURY. Also, the USER PROGRAM will be LOST. For correct connection, check the location of pin 1. Connect pin 1 on the user system connector to the connector installed at the bottom of the E6000H user system interface board.
Evaluation chip board Connector: WD-200P-VF85-N (manufactured by Japan Aviation Electronics Industry, Ltd.) Figure 2.2 Connection Using the Dedicated Connectors 18.0 40.0 Evaluation chip board User system Connector: WD-200P-VF85-N (manufactured by Japan Aviation Electronics Industry, Ltd.) Unit: mm Tolerance: ±1.0 mm Figure 2.
95.0 199 200 1 2 UCN2 199 1 2 UCN1 200 Hole for a connector (NTH) × 4 WD-200P-VF85-N Unit: mm Tolerance: ±0.1 mm Figure 2.4 Location for Mounting the Connector in the User System To design the foot pattern, refer to the catalog on WD-200P-VF85-N for dimensions.
2.2.4 Pin Arrangement on the User System Interface Connector Table 2.1 lists the pin arrangement on the user system interface connector of HS1650EPH60H. Table 2.1 Pin Arrangement on HS1650EPH60H User I/F 1 Pin No. Signal Name User I/F 1 Pin No.
Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No.
Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No.
Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No.
Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No.
Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No.
Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No.
Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name UCN2 173 ⎯ UCN2 187 MD0 174 ⎯ 188 MD1 175 ⎯ 189 MD2 176 ⎯ 190 ⎯ 177 VSS_85 191 ⎯ 178 ⎯ 192 ⎯ 179 ⎯ 193 VSS_3 180 ⎯ 194 VSS_2 181 VSS_86 195 ⎯ 182 ⎯ 196 EXTAL 183 ⎯ 197 VSS_87 184 ⎯ 198 ⎯ 185 ⎯ 199 ⎯ 186 ⎯ 200 ⎯ Note: Do not connect anything to pins indicated as ‘⎯’. Failure to do so will damage the emulator or result in a fire hazard.
2.2.5 Precautions on Connecting the User System When connecting the evaluation chip board to the user system, note the following: 1. Secure the E6000H station location. Place the E6000H station and evaluation chip board so that the trace cable is not bent or twisted, as shown below. A bent or twisted cable will impose stress on the user interface, leading to connection or contact failure.
2.2.6 Connecting the External Probe (Not Supported in this Emulator) CAUTION Check the external probe direction and connect the external probe to the emulator station correctly. Incorrect connection will damage the probe or connector. When an external probe is connected to the emulator probe connector on the E6000H evaluation chip board's rear panel, it enables external signal tracing and multibreak detection. Figure 2.5 shows the external probe connector. Pin No.
2.2.7 Selecting the Clock This emulator supports three types of clock for the MCUs listed in table 2.2: a crystal oscillator attached on the evaluation chip board, external clock input from the user system, and the emulator internal clock. The clock is specified with the [Configuration Properties] dialog box. Table 2.
Enlarged view Crystal oscillator X1 X2 Crystal oscillator terminals Evaluation chip board Figure 2.6 Installing the Crystal Oscillator External Clock: Follow the procedure listed below to select the external clock. 1. Check that the emulator power switch is turned off. (Check that the power LED is not lit.) 2. Connect the user system interface cable to the user system and supply a clock signal through the EXTAL pin from the user system. 3. Turn on the user system power and then the emulator power.
2.2.8 Connecting the System Ground CAUTION Separate the frame ground from the signal ground at the user system. When the frame ground is connected to the signal ground and the emulator is then connected to the user system, the emulator will malfunction. The emulator's signal ground is connected to the user system's signal ground via the evaluation chip board. In the E6000H station, the signal ground and frame ground are connected (figure 2.7).
The user system must be connected to an appropriate ground so as to minimize noise and the adverse effects of ground loops. When connecting the evaluation chip board and the user system, confirm that the ground pins of the evaluation chip board are firmly connected to the user system's ground. Figure 2.8 Connecting the Frame Ground 2.2.9 PC Interface Board Specifications For details on the PC interface board, LAN adapter, or USB adapter, refer to their description notes.
28
Section 3 Hardware Specifications 3.1 Environmental Conditions CAUTION Observe the conditions listed in table 3.1 when using the emulator. The following environmental conditions must be satisfied, otherwise the user system and the emulator will not operate normally. The USER PROGRAM will be LOST. Table 3.
3.2 Emulator External Dimensions and Mass Figures 3.1 shows the external dimensions and mass of the E6000H emulator. Figure 3.
3.3 User System Interface Circuit 3.3.1 User System Interface Circuit The circuits that interface the evaluation chip in the emulator to the user system include buffers and resistors. When connecting the emulator to a user system, adjust the user system hardware compensating for FANIN, FANOUT, and propagation delays. The AC timing values when using the emulator are shown in table 3.2. Note: The values with the emulator connected, in table 3.
T1 T2 T3 Bφ tAD A23 to A0 tCSD1 to tAS1 tASD tBSD tASD tAH1 tBSD tRWD tRWD RD/ tAS1 tRSD1 tRSD1 When read (RDNn =1) tRDS1 tRDH1 tAC6 tAA4 D15 to D0 tRWD tRWD RD/ tAS1 tRSD1 tRSD2 When read (RDNn =0) tRDS2 tAC4 tRDH2 tAA5 D15 to D0 tRWD tRWD RD/ tAS2 When written and tWRD1 tWRD2 tAH1 tWDS1 tWDD tWSW2 tWDH1 D15 to D0 (When written) Figure 3.
User system MCU Vcc MD control circuit Monitor circuit LPT16244 MD0 MD1 MD2 47 kΩ MD0 MD1 MD2 Vcc VHC244 _RES _STBY _NMI EPM7256 VHC14 47 kΩ _RES _STBY _NMI Figure 3.
User system MCU Voltage-follower circuit 2.3 kΩ Vcc Vcc Vss Vss NC VCL NC EMLE Vcc VHC244 EPM7256 LPT244 47 kΩ EXTAL XTAL EXTAL NC Figure 3.
User system MCU P10 to P17 P10 to P17 P20 to P27 P20 to P27 P30 to P37 P30 to P37 Note: The H8SX/1653 does not have P30 to P37. P40 to P43 P40 to P43 P50 to P57 P50 to P57 AVcc AVcc 0.022 μF AVss NC AVss 0.022 μF AVref AVref Figure 3.
User system MCU P60 to P65 PA0 PA2 P60 to P65 LPT16244 PA1 PA3 to PA7 PA1 PA3 to PA7 PB0 to PB3 PB0 to PB3 PD0 to PD7 PD0 to PD7 PE0 to PE7 PE0 to PE7 PF0 to PF7 PF0 to PF7 Note: The H8SX/1653 does not have PF5 to PF7. PH0 to PH7 PH0 to PH7 PI0 to PI7 PI0 to PI7 Figure 3.
Sub-MCU User system Vcc MD control circuit Monitoring circuit LPT16244 47 kΩ MD_CLK MD_CLK PM0-PM4 PM0-PM4 EPM7128 VBUS VBUS 1 kΩ DrVcc DrVcc Power-supply circuit USD- USD- USD+ USD+ DrVss DrVss MCU User system Vcc VHC244 EPM7128 UHC14 47 kΩ _RES _RES EPM7128 MCU User system SN74CB3Q3306A P23 P23 SN74CB3Q3306A P27 P27 MCU User system SN74CB3Q3306A P14 P14 Sub-MCU SN74CB3Q3306A TXD Figure 3.
User system Vcc Sub-MCU Monitoring circuit EPM7128 47 kΩ MD3 Vcc MD control circuit Monitoring circuit LPT16244 47 kΩ MD_CLK MD_CLK PM0-PM4 PM0-PM4 EPM7128 VBUS VBUS 1 kΩ DrVcc DrVcc Power-supply circuit USD- USD- USD+ USD+ DrVss DrVss MCU User system Vcc VHC244 EPM7128 UHC14 47 kΩ _RES _RES EPM7128 MCU User system SN74CB3Q3306A P23 P23 SN74CB3Q3306A P27 P27 MCU SN74CB3Q3306A P14 User system P14 Sub-MCU SN74CB3Q3306A TXD Figure 3.
Note: The power-supply circuits shown in figures 3.4 and 3.5 are turned on/off by the setting of the SW1 jumper pin on the user system interface board (HS1653ECN61H or HS1664ECH61H). Ensure that the jumper pin is inserted to [ON] when connecting the emulator (with the user system interface board attached) to the user system or supplying power to DrVCC. Otherwise the emulator product, user system interface board, and user system will be damaged. 3.4 3.4.
3.4.4 Control Input Signals (/RES, /NMI, /BREQ, /WAIT, and /STBY) The H8SX/1600-series MCU control input signals are /RES, /NMI, /BREQ, /WAIT, and /STBY. The /RES, /NMI, and /STBY signals are only valid when emulation was started with normal program execution (i.e., they are invalid when emulation was started with step execution). The /BREQ and /WAIT signals are valid during emulation with the display and modification of memory contents, execution, and step execution.
3.4.7 Emulator State and Internal Modules Operation of some internal modules depends on the emulator’s state. Table 3.4 shows the relation between the emulator’s state and operation of the internal modules. Table 3.
3.4.8 Differences in Values of Registers Note that certain general and control registers of both emulators are initialized whenever the system is activated or the evaluation chip is reset by a command. Table 3.
3.5 Notes Specific to the H8SX/1650 E6000H Emulator 3.5.1 Custom Device Function The maximum value selectable for the on-chip ROM with the custom device functions of the H8SX/1650 E6000H emulator is 2 Mbytes. Do not specify a value greater than 2 Mbytes. 3.5.2 Exception Processing of Sleep Instructions The emulator does not support exception processing of sleep instructions.
44
Section 4 Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000H diagnostic program. 4.1 System Set-Up for Diagnostic Program Execution To execute the diagnostic program, use the following hardware; do not connect the user system interface board and user system.
Figure 4.1 [Misc] Page 5. Turn on the E6000H emulator switch. Note: To execute the diagnostic program, firstly turn on the power of the emulator. The diagnostic program checks the initial state of the hardware. Therefore, after turning on the power, do not activate the Highperformance Embedded Workshop before executing the diagnostic program.
4.2 Test Item of the Diagnostic Program Table 4.1 shows the test items of this diagnostic program. Table 4.1 Test Items of the Diagnostic Program Test No.
4.3 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of the host computer, use the command prompt to change the current directory to :\Diag\1650, and enter the command below that corresponds to the PC interface board used to initiate the diagnostic program: 1. PCI bus interface board (HS6000EIC01H or HS6000EIC02H) > TM1650 –PCI (Enter) 2. PC card interface (HS6000EIP01H) > TM1650 –PCCD (Enter) 3.
The following messages are displayed during the test. There are 13 steps in this test. Message Description E6000H H8SX/1650 Emulator Tests V*.* Copyright (c) 2003 Renesas Technology Corp. Test program start message. x.x shows the version number. Loading driver .........................OK (Use PCI) Shows that the PC interface board is correctly installed in the host computer. Initializing driver ....................OK Searching for interface card ...........OK Checking emulator is connected .........
6. 7. 8. 9. 10. 11. 12. 13. 02) EMU 12Mhz MPU 12Mhz Sampling 20ns ......................OK 03) EMU 12Mhz MPU 12Mhz Sampling 1.6us .....................OK 04) EMU 12Mhz MPU 12Mhz Sampling 52us ......................OK 05) EMU 12Mhz MPU 12Mhz Sampling MPU .......................OK 06) EMU 12Mhz MPU 12Mhz Sampling MPU/2 .....................OK 07) EMU 12Mhz MPU 12Mhz Sampling MPU/4 .....................OK 08) EMU 12Mhz MPU 12Mhz Sampling MPU/8 .....................
H8SX/1527 and H8SX/1527R Hardware Part
Section 1 Overview 1.1 Notes on Usage CAUTION READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. 1. Check all components with the component list after unpacking the emulator. 2. Never place heavy objects on the casing. 3.
1.2 Emulator Hardware Components The emulator consists of an E6000H station and the E6000H’s front-end unit. By installing a user system interface cable (option) to your host computer, the emulator can be connected in the same package as the device. PC interface (option) includes a PC interface board (PCI bus and PC card bus), a LAN adapter (connected with the network), and a USB adapter (connected with the USB interface).
1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances) The names of the components on the front/rear panel of the E6000H station are listed below. Front Panel: Figure 1.2 E6000H Station: Front Panel (a) POWER lamp: Is lit up while the E6000H station is supplied with power. (b) RUN lamp: Is lit up while the user program is running.
Rear Panel: Figure 1.3 E6000H Station: Rear Panel (a) Power switch: Turning this switch to I (input) supplies power to the emulator (E6000H station and the E6000H’s front-end unit). (b) AC power connector: For an AC 100-V to 240-V power supply. (c) PC interface cable connector: For the PC interface cable that connects the host computer to the E6000H station. A PC interface board, PC card interface, LAN adapter, or USB adapter can be connected. Marked PC/IF.
1.2.2 Front-end Unit Configuration The names of the components on the front-end unit are listed below. (a) 124 UCN1 XTAL (b) (d) PCN2 (c) 5. 5 18 12. 5 30. 6 43. 6 162. 8 Unit:mm Tolerance: 0.2mm Note: The model name of the H8SX/1527R E6000H emulator is HS1527REPH60H. Figure 1.4 Configuration and Dimensions of the Emulator’s Front-end Unit (a) Crystal oscillator terminals: For installing a crystal oscillator to be used as an external clock source for the MCU.
1.3 System Configuration The emulator must be connected to a host computer via the selected PC interface board (PCI bus or PC card bus), LAN adapter, or USB adapter. For details on the PC interface boards (available for PCI bus and PC card bus specifications), the LAN adapter, and the USB adapter, refer to the relevant descriptive documents. 1.3.1 System Configuration Using Various Interfaces (1) PC Interface Board Figure 1.5 shows the configuration of a system in which the PC interface board is used.
(3) USB Adapter Figure 1.7 shows the configuration of a system in which the USB adapter is used. A USB adapter can be used to connect the emulator to a host computer with the USB interface. Figure 1.
8
Section 2 Preparation before Use 2.1 Description on Emulator Usage This section describes the preparation before emulator usage. Figure 2.1 is a flowchart on preparation before use of the emulator. CAUTION Read this section and understand its contents before preparation. Incorrect operation will damage the user system and the emulator. The USER PROGRAM will be LOST. Reference: Connect the emulator. Set up the emulator on each OS. Start debugging. Described in this section.
2.2 Emulator Connection The following description covers connection of the emulator. 2.2.1 Connecting the Emulator to the User System WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator or will result in PERSONAL INJURY. The USER PROGRAM will be LOST. 1. Check that the emulator power switch is turned off.
2.2.3 Precautions on Connecting the User System When connecting the emulator to the user system, note the following: 1. Secure the E6000H station location. Place the E6000H station and the E6000H’s front-end unit so that the trace cable is not bent or twisted, as shown below. A bent or twisted cable will impose stress on the user interface, leading to connection or contact failure.
2.2.4 Connecting the External Probe CAUTION Check the external probe direction and connect the external probe to the emulator station correctly. Incorrect connection will damage the probe or connector. When an external probe is connected to the external probe connector on the emulator’s front-end unit, it enables external signal tracing and multibreak detection. Figure 2.2 shows the external probe connector. Pin No.
2.2.5 Selecting the Clock This emulator supports three types of clock for the MCU: a crystal oscillator attached on the emulator’s frontend unit, external clock input from the user system, and the emulator internal clock. The clock is specified with the [Configuration] dialog box. This emulator can use a clock source (φ) running at up to 40.0 MHz as the H8SX/1527 clock input. The H8SX/1582 or H8SX/1527R can operate with clock sources (φ) running at up to 48.0 MHz.
Enlarged view Crystal oscillator Crystal oscillator terminals X1 X2 UCN1 XTAL PCN2 Note: The model name of the H8SX/1527R E6000H emulator is HS1527REPH60H. Figure 2.3 Installing the Crystal Oscillator External Clock: Follow the procedure listed below to select the external clock. 1. Check that the emulator power switch is turned off. (Check that the power LED is not lit.) 2.
2.2.6 Connecting the System Ground CAUTION Separate the frame ground from the signal ground at the user system. When the frame ground is connected to the signal ground and the emulator is then connected to the user system, the emulator will malfunction. The emulator's signal ground is connected to the user system's signal ground via the emulator’s front-end unit. In the E6000H station, the signal ground and frame ground are connected (figure 2.4).
The user system must be connected to an appropriate ground so as to minimize noise and the adverse effects of ground loops. When connecting the emulator’s front-end unit and the user system, confirm that the ground pins of the front-end unit are firmly connected to the user system’s ground. Figure 2.5 Connecting the Frame Ground 2.2.7 PC Interface Board Specifications For details on the PC interface board, LAN adapter, or USB adapter, refer to their description notes.
Section 3 Hardware Specifications 3.1 Environmental Conditions CAUTION Observe the conditions listed in table 3.1 when using the emulator. The following environmental conditions must be satisfied, otherwise the user system and the emulator will not operate normally. The USER PROGRAM will be LOST. Table 3.
3.2 Emulator External Dimensions and Mass Figure 3.1 shows the external dimensions and mass of the E6000H emulator. Figure 3.
3.3 User System Interface Circuit 3.3.1 User System Interface Circuit The circuits that interface the MCU in the emulator to the user system include the level-shifter circuits (for 5 V and 3.3 V) and resistors. When connecting the emulator to a user system, adjust the user system hardware compensating for FANIN, FANOUT, and propagation delays. The user system interface circuits connected to the user system are shown in figure 3.2.
User system interface cable MCU Vcc MD control circuit Monitor circuit VHC244 MD0 MD1 47 kΩ MD0 MD1 Vcc VHC244 EPM7256 LPT16244 VHC244 _RES _NMI Figure 3.
User system interface cable MCU Voltage-follower circuit 23 kΩ Vcc Vcc Vss Vss VCL NC Vcc 47 kΩ NC EMLE Vcc VHC244 EPM7256 LPT244 VHC244 EXTAL XTAL 47 kΩ EXTAL NC NC XTAL Figure 3.
Vcc User system interface cable MCU VHCT125 P10 to P17 P30 to P37 P60 to P67 PA0, PA4 to PA7 PB0 to PB2 PH0 to PH7 PI0 to PI7 PJ0 to PJ7 PK0 to PK7 47 kΩ P10 to P17 P30 to P37 P60 to P67 PA0, PA4 to PA7 PB0 to PB2 PH0 to PH7 PI0 to PI7 PJ0 to PJ7 PK0 to PK7 VHC125 Compression circuit 1 kΩ P40 to P47 P50 to P57 P40 to P47 P50 to P57 10 MΩ AVcc AVcc 0.022 μF AVss AVss 0.022 μF AVref AVref Figure 3.
Vcc User system interface cable MCU VHCT125 47 kΩ P20, P22 to P27 P20, P22 to P27 VHC125 CB3Q3306 Vcc User system interface cable MCU VHCT125 47 kΩ P21 P21 VHC125 CB3Q3306 CBTS3306 SUB MCU P21 Figure 3.
Vcc User system interface cable MCU VHCT125 47 kΩ PA1 to PA3 PD0 to PD7 PA1 to PA3 PD0 to PD7 VHC125 CBTS3306 SUB MCU PA1 to PA3 PD0 to PD7 Figure 3.
3.4 3.4.1 Support of the Target MCU Memory Space The architecture of the MCU allows for a 16-Mbyte memory space. (1) On-Chip I/O Area If an attempt is made to access the on-chip I/O area, the on-chip I/O area in the MCU installed in the emulator is accessed. To break user program execution when the on-chip I/O area is written to or accessed, use the hardware break or internal break.
3.4.4 Control Input Signals (/RES and /NMI) The MCU control input signals are /RES and /NMI. The /RES and /NMI signals are only valid when emulation was started with normal program execution (i.e., they are invalid when emulation was started with step execution). The input of the /RES or /NMI signal during execution or step execution can be disabled by a setting in the [Configuration] dialog box. 3.4.5 Watchdog Timer (WDT) When emulation is suspended (i.e.
3.4.7 Emulator State and Internal Modules Operation of some internal modules depends on the emulator’s state. Tables 3.3 and 3.4 show the relation between the emulator’s state and operation of the internal modules. Table 3.
3.4.8 Differences in Values of Registers Note that certain general and control registers of both emulators are initialized whenever the system is activated or the MCU is reset by a command. Table 3.
3.5 3.5.1 Notes Specific to the H8SX/1527 E6000H and H8SX/1527R E6000H Emulators Custom Device Function The maximum value selectable for the on-chip ROM with the custom device functions of the H8SX/1527 E6000H and H8SX/1527R E6000H emulators is 2 Mbytes. Do not specify a value greater than 2 Mbytes. 3.5.2 Non-availability of P2 Open-Drain Outputs In the emulator, port P2 pins cannot be set up as NMOS open-drain outputs by settings in register P2ODR. Do not set any bit in P2ODR to 1. 3.5.
30
Section 4 Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000H diagnostic program. 4.1 System Set-Up for Diagnostic Program Execution To execute the diagnostic program, use the following hardware; do not connect the user system interface board and user system.
Figure 4.1 [Misc] Page 5. Turn on the E6000H emulator switch. Note: To execute the diagnostic program, firstly turn on the power of the emulator. The diagnostic program checks the initial state of the hardware. Therefore, after turning on the power, do not activate the Highperformance Embedded Workshop before executing the diagnostic program.
4.2 Test Item of the Diagnostic Program (HS1527KEPH60H) Table 4.1 shows the test items of this diagnostic program. Table 4.1 Test Items of the Diagnostic Program Test No.
4.3 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of the host computer, use the command prompt to change the current directory to :\Diag\1527, and enter the command below that corresponds to the PC interface board used to initiate the diagnostic program: 1. PCI bus interface board (HS6000EIC01H or HS6000EIC02H) > TM1527 –PCI (Enter) 2. PC card interface (HS6000EIP01H) > TM1527 –PCCD (Enter) 3.
The following messages are displayed during the test. There are 15 steps in this test. Message Description H8SX/1527 E6000H Emulator Tests V*.* Copyright (c) 2003 Renesas Technology Corp. Test program start message. x.x shows the version number. Loading driver .........................OK (Use PCI) Shows that the PC interface board is correctly installed in the host computer. Initializing driver ....................OK Searching for interface card ...........OK Checking emulator is connected .........
6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 11) EMU 35.7Mhz MPU 35.7Mhz Sampling 20ns ..................OK 12) EMU 35.9Mhz MPU 35.9Mhz Sampling 20ns ..................OK 13) EMU f1Mhz MPU f2Mhz Sampling 20ns ......................SKIP Emulation Monitor 01) RESERVED 02) RESERVED 03) ASEST ..................................................OK G/A Break Function 01) Address Condition ......................................OK 02) Data Condition .........................................
4.4 Test Item of the Diagnostic Program (HS1527REPH60H) Table 4.2 shows the test items of this diagnostic program. Table 4.2 Test Items of the Diagnostic Program Test No.
4.5 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of the host computer, use the command prompt to change the current directory to :\Diag\1527R, and enter the command below that corresponds to the PC interface board used to initiate the diagnostic program: 1. PCI bus interface board (HS6000EIC01H or HS6000EIC02H) > TM1527R –PCI (Enter) 2. PC card interface (HS6000EIP01H) > TM1527R –PCCD (Enter) 3.
The following messages are displayed during the test. There are 15 steps in this test. Message Description H8SX/1527R E6000H Emulator Tests V*.* Copyright (c) 2005 Renesas Technology Corp. Test program start message. x.x shows the version number. Loading driver .........................OK (Use PCI) Shows that the PC interface board is correctly installed in the host computer. Initializing driver ....................OK Searching for interface card ...........OK Checking emulator is connected .........
6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 11) EMU 35.7Mhz MPU 35.7Mhz Sampling 20ns ..................OK 12) EMU 35.9Mhz MPU 35.9Mhz Sampling 20ns ..................OK 13) EMU f1Mhz MPU f2Mhz Sampling 20ns ......................SKIP Emulation Monitor 01) RESERVED 02) RESERVED 03) ASEST ..................................................OK G/A Break Function 01) Address Condition ......................................OK 02) Data Condition .........................................
H8SX/1544 Hardware Part
Section 1 Overview 1.1 Notes on Usage CAUTION READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. 1. Check all components with the component list after unpacking the emulator. 2. Never place heavy objects on the casing. 3.
1.2 Emulator Hardware Components The emulator consists of an E6000H station and the E6000H’s front-end unit. By installing a user system interface cable (option) to your host computer, the emulator can be connected in the same package as the device. PC interface (option) includes a PC interface board (PCI bus and PC card bus), a LAN adapter (connected with the network), and a USB adapter (connected with the USB interface).
1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances) The names of the components on the front/rear panel of the E6000H station are listed below. Front Panel: Figure 1.2 E6000H Station: Front Panel (a) POWER lamp: Is lit up while the E6000H station is supplied with power. (b) RUN lamp: Is lit up while the user program is running.
Rear Panel: Figure 1.3 E6000H Station: Rear Panel (a) Power switch: Turning this switch to I (input) supplies power to the emulator (E6000H station and the E6000H’s front-end unit). (b) AC power connector: For an AC 100-V to 240-V power supply. (c) PC interface cable connector: For the PC interface cable that connects the host computer to the E6000H station. A PC interface board, PC card interface, LAN adapter, or USB adapter can be connected. Marked PC/IF.
1.2.2 Front-end Unit Configuration The names of the components on the front-end unit are listed below. (a) 124 UCN1 XTAL (b) (d) HS1544EPH60H PCN2 (c) 5. 5 18 12. 5 30. 6 43. 6 162. 8 Unit:mm Tolerance: 0.2mm Figure 1.4 Configuration and Dimensions of the Emulator’s Front-end Unit (a) Crystal oscillator terminals: For installing a crystal oscillator to be used as an external clock source for the MCU.
1.3 System Configuration The emulator must be connected to a host computer via the selected PC interface board (PCI bus or PC card bus), LAN adapter, or USB adapter. For details on the PC interface boards (available for PCI bus and PC card bus specifications), the LAN adapter, and the USB adapter, refer to the relevant descriptive documents. 1.3.1 System Configuration Using Various Interfaces (1) PC Interface Board Figure 1.5 shows the configuration of a system in which the PC interface board is used.
(3) USB Adapter Figure 1.7 shows the configuration of a system in which the USB adapter is used. A USB adapter can be used to connect the emulator to a host computer with the USB interface. E6000H emulator PCIF USB adapter Host computer USB cable PC interface cable Figure 1.
8
Section 2 Preparation before Use 2.1 Description on Emulator Usage This section describes the preparation before emulator usage. Figure 2.1 is a flowchart on preparation before use of the emulator. CAUTION Read this section and understand its contents before preparation. Incorrect operation will damage the user system and the emulator. The USER PROGRAM will be LOST. Reference: Connect the emulator. Set up the emulator on each OS. Start debugging. Described in this section.
2.2 Emulator Connection The following description covers connection of the emulator. 2.2.1 Connecting the Emulator to the User System WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator or will result in PERSONAL INJURY. The USER PROGRAM will be LOST. 1. Check that the emulator power switch is turned off.
2.2.3 Precautions on Connecting the User System When connecting the emulator to the user system, note the following: 1. Secure the E6000H station location. Place the E6000H station and the E6000H’s front-end unit so that the trace cable is not bent or twisted, as shown below. A bent or twisted cable will impose stress on the user interface, leading to connection or contact failure.
2.2.4 Connecting the External Probe CAUTION Check the external probe direction and connect the external probe to the emulator station correctly. Incorrect connection will damage the probe or connector. When an external probe is connected to the external probe connector on the emulator’s front-end unit, it enables external signal tracing and multibreak detection. Figure 2.2 shows the external probe connector. Pin No.
2.2.5 Selecting the Clock This emulator supports three types of clock for the MCU: a crystal oscillator attached on the emulator’s frontend unit, external clock input from the user system, and the emulator internal clock. The clock is specified with the [Configuration] dialog box. This emulator can use a clock source (φ) running at up to 40.0 MHz as the H8SX/1544 clock input.
Enlarged view Crystal oscillator Crystal oscillator terminals X1 X2 UCN1 XTAL PCN2 Figure 2.3 Installing the Crystal Oscillator External Clock: Follow the procedure listed below to select the external clock. 1. Check that the emulator power switch is turned off. (Check that the power LED is not lit.) 2. Connect the user system interface cable to the user system and supply a clock signal through the EXTAL pin from the user system. 3. Turn on the user system power and then the emulator power.
2.2.6 Connecting the System Ground CAUTION Separate the frame ground from the signal ground at the user system. When the frame ground is connected to the signal ground and the emulator is then connected to the user system, the emulator will malfunction. The emulator's signal ground is connected to the user system's signal ground via the emulator’s front-end unit. In the E6000H station, the signal ground and frame ground are connected (figure 2.4).
The user system must be connected to an appropriate ground so as to minimize noise and the adverse effects of ground loops. When connecting the emulator’s front-end unit and the user system, confirm that the ground pins of the front-end unit are firmly connected to the user system's ground. Emulator power supply cable User system power supply cable Outlet Ground 100-V to 240-V AC power Figure 2.5 Connecting the Frame Ground 2.2.
Section 3 Hardware Specifications 3.1 Environmental Conditions CAUTION Observe the conditions listed in table 3.1 when using the emulator. The following environmental conditions must be satisfied, otherwise the user system and the emulator will not operate normally. The USER PROGRAM will be LOST. Table 3.
3.2 Emulator External Dimensions and Mass Figures 3.1 shows the external dimensions and mass of the E6000H emulator. Figure 3.
3.3 User System Interface Circuit 3.3.1 User System Interface Circuit The circuits that interface the MCU in the emulator to the user system include the level-shifter circuits (for 5 V and 3.3 V) and resistors. When connecting the emulator to a user system, adjust the user system hardware compensating for FANIN, FANOUT, and propagation delays. The user system interface circuits connected to the user system are shown in figure 3.2.
MCU User system interface cable Vcc MD control circuit Monitor circuit LVT16244 VHC244 MD0 MD1 MD2 4.7 kΩ MD0 MD1 MD2 Vcc VHC244 EPM7256 VHC14 VHC244 _RES _NMI _STBY Figure 3.2 User System Interface Circuits (1) 20 4.
User system interface cable MCU Voltage-follower circuit 3.3 V 23 kΩ Vcc Vcc Vss Vss NC VCL NC EMLE Vcc VHC244 EPM7256 LPT244 VHC244 EXTAL XTAL 4.7 kΩ EXTAL NC NC XTAL Figure 3.
VCC User system interface cable MCU 47 kΩ VHCT125 P11 to P13 P30 to P33 P61, P62 PA3 to PA7 PD0 to PD7 PE0 to PE7 PH0 to PH7 PI4 to PI7 P11 to P13 P30 to P33 P61, P62 PA3 to PA7 PD0 to PD7 PE0 to PE7 PH0 to PH7 PI4 to PI7 VHC125 Compression circuit P40 to P47 P50 to P55 P40 to P47 P50 to P55 10 MΩ Avcc Avcc 0.022 μF 27 kΩ Avss Avss 0.022 μF 27 kΩ AVref AVref RY Sub-MCU P56, P57 P56, P57 Figure 3.
VCC MCU User system interface cable 47 kΩ VHCT125 P24 to P27 P24 to P27 VHC125 CB3Q3306 VCC User system interface cable MCU 47 kΩ VHCT125 P10 P60 P10 P60 VHC125 3V CB3Q3306 1 kΩ LVC07 VCC User system interface cable MCU VHCT125 47 kΩ P14 to P17 P14 to P17 VHC125 3V PCA9306 1 kΩ Figure 3.
VCC User system interface cable MCU VHCT125 P20, P21, P23 P34 to P37 P63 to P67 PA0 to PA2 PI0 to PI3 PJ0 to PJ7 PK0 to PK7 47 kΩ P20, P21, P23 P34 to P37 P63 to P67 PA0 to PA2 PI0 to PI3 PJ0 to PJ7 PK0 to PK7 VHC125 Sub-MCU P20, P21, P23 P34 to P37 P63 to P67 PA0 to PA2 PI0 to PI3 PJ0 to PJ7 PK0 to PK7 VCC MCU User system interface cable 47 kΩ VHCT125 PF0 to PF4, PF6, PF7 PF0 to PF4, PF6, PF7 VHC125 CB3Q3306 Sub-MCU PF0 to PF4, PF6, PF7 VCC MCU 47 kΩ VHCT125 P22 P22 VHC125 3V CB3Q3306
VCC MCU 47 kΩ VHCT125 User system interface cable PF5 PF5 VHC125 CB3Q3306 3V CB3Q3306 1 kΩ LVC07 Sub-MCU PF5 Figure 3.
3.4 3.4.1 Support of the Target MCU Memory Space The architecture of the MCU allows for a 16-Mbyte memory space. (1) On-Chip I/O Area If an attempt is made to access the on-chip I/O area, the on-chip I/O area in the MCU installed in the emulator is accessed. To break user program execution when the on-chip I/O area is written to or accessed, use the hardware break or internal break.
3.4.4 Control Input Signals (/RES, /NMI, and /STBY) The MCU control input signals are /RES, /NMI, and /STBY. The /RES, /NMI, and /STBY signals are only valid when emulation was started with normal program execution (i.e., they are invalid when emulation was started with step execution). The input of the /RES, /NMI, or /STBY signal during execution or step execution can be disabled by a setting in the [Configuration] dialog box. 3.4.5 Watchdog Timer (WDT) When emulation is suspended (i.e.
3.4.7 Emulator State and Internal Modules Operation of some internal modules depends on the emulator’s state. Table 3.3 shows the relation between the emulator’s state and operation of the internal modules. Table 3.
3.4.8 Differences in Values of Registers Note that certain general and control registers of both emulators are initialized whenever the system is activated or the MCU is reset by a command. Table 3.
3.5.5 Port Registers (PORTx) ⎯Restriction (1) When the module pins are used as inputs In the emulator, undefined values are read from PORTx corresponding to the modules. In the actual MCU, however, reading PORTx allows reading the states of the pins. (2) When the module pins are used as outputs In the emulator, undefined values are read from PORTx corresponding to the modules when the value of the data direction registers is 0.
Section 4 Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000H diagnostic program. 4.1 System Set-Up for Diagnostic Program Execution To execute the diagnostic program, use the following hardware; do not connect the user system interface board and user system.
Figure 4.1 [Misc] Page 5. Turn on the E6000H emulator switch. Note: To execute the diagnostic program, firstly turn on the power of the emulator. The diagnostic program checks the initial state of the hardware. Therefore, after turning on the power, do not activate the Highperformance Embedded Workshop before executing the diagnostic program.
4.2 Test Item of the Diagnostic Program Table 4.1 shows the test items of this diagnostic program. Table 4.1 Test Items of the Diagnostic Program Test No.
4.3 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of the host computer, use the command prompt to change the current directory to :\Diag\1544, and enter the command below that corresponds to the PC interface board used to initiate the diagnostic program: 1. PCI bus interface board (HS6000EIC01H or HS6000EIC02H) > TM1544 –PCI (Enter) 2. PC card interface (HS6000EIP01H) > TM1544 –PCCD (Enter) 3.
The following messages are displayed during the test. There are 15 steps in this test. Message Description H8SX/1544 E6000H Emulator Tests V*.* Copyright (c) 2003 Renesas Technology Corp. Test program start message. x.x shows the version number. Loading driver .........................OK (Use PCI) Shows that the PC interface board is correctly installed in the host computer. Initializing driver ....................OK Searching for interface card ...........OK Checking emulator is connected .........
6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 10) EMU 4MHz MPU 32MHz Sampling 20ns ...............................OK 11) EMU 35.7MHz MPU 35.7MHz Sampling 20ns ...........................OK 12) EMU 35.9MHz MPU 35.9MHz Sampling 20ns ...........................OK Emulation Monitor 01) AUDRES ..........................................................SKIP 02) TRES ............................................................SKIP 03) ASEST ...........................................................
Debugger Part
Section 1 Overview The Debugger Part includes the following information. Table 1.1 Debugger Part Contents Section Title Content 2 Preparation before Use This section starts with creation of a workspace and ends with connection to the emulator. 3 Debugging This section describes this emulator ‘s peculiar debugging operation and the associated windows and dialog boxes. Refer to the High-performance Embedded Workshop user's manual about High-performance Embedded Workshop common functions as below.
2
Section 2 Preparation before Use 2.1 Method for Activating High-performance Embedded Workshop To activate the High-performance Embedded Workshop, follow the procedure listed below. 1. Connect the emulator to the host computer. 2. Connect the user system interface cable to the connector of the emulator if you use the user system interface cable. This is not necessary when you do not use the user system interface cable. Turn on the emulator.
2.1.1 Creating a New Workspace (Toolchain Not Used) 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Create a new project workspace] radio button and click the [OK] button. Figure 2.
2. Creation of a new workspace is started. The following dialog box is displayed. Figure 2.3 [New Project Workspace] Dialog Box [Workspace Name] edit box: Enter the new workspace name. [Project Name] edit box: Enter the project name. When the project name is the same as the workspace name, it needs not be entered. [Directory] edit box: Enter the directory name in which the workspace will be created. Click the [Browse…] button to select a directory. [CPU family] combo box: Select the target CPU family.
3. Select the target platform of the session file. The following dialog box is displayed. Figure 2.4 [New Project – Step 7] Dialog Box The target platform for the session file used when the High-performance Embedded Workshop is activated must be selected here. Check the box against the target platform and then click the [Next] button.
4. Set the configuration file name. The configuration file saves the state of High-performance Embedded Workshop except for the emulator. Figure 2.5 [New Project – Step 8] Dialog Box If multiple target platforms were selected in the [New Project – Step 7] dialog box shown in figure 2.5, set the name of a configuration file for each of them, each time clicking the [Next] button to proceed to the next target. Setting of the configuration file name is the end of the emulator settings.
2.1.2 Creating a New Workspace (Toolchain Used) 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select the [Create a new project workspace] radio button and click the [OK] button. Figure 2.
2. Creation of a new workspace is started. The following dialog box is displayed. Figure 2.7 [New Project Workspace] Dialog Box [Workspace Name] edit box: Enter the new workspace name. [Project Name] edit box: Enter the project name. When the project name is the same as the workspace name, it needs not be entered. [Directory] edit box: Enter the directory name in which the workspace will be created. Click the [Browse…] button to select a directory. [CPU family] combo box: Select the target CPU family.
3. Make the required setting for the toolchain. When the setting has been completed, the following dialog box is displayed. Figure 2.8 [New Project – Step 7] Dialog Box The target platform for the session file used when the High-performance Embedded Workshop is activated must be selected here. Check the box against the target platform and then click the [Next] button.
4. Set the configuration file name. The configuration file saves the state of High-performance Embedded Workshop except for the emulator. Figure 2.9 [New Project – Step 8] Dialog Box If multiple target platforms were selected in the [New Project – Step 7] dialog box shown in figure 2.9, set the configuration file name for each of them, each time clicking the [Next] button to proceed to the next target. Setting of the configuration file name is the end of the emulator settings.
2.1.3 Selecting an Existing Workspace 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Browse to another project workspace] radio button and click the [OK] button. Figure 2.10 [Welcome!] Dialog Box 2. The [Open Workspace] dialog box is displayed. Select a directory in which you have created a workspace. After that, select the workspace file (.hws) and click the [Open] button. Figure 2.11 [Open Workspace] Dialog Box 3.
2.2 Connecting the Emulator Select either of the following two ways to connect the emulator: (a) Connecting the emulator after the setting at emulator activation Select [Debug -> Debug Settings…] to open the [Debug Settings] dialog box. It is possible to register the download module or the command chain that is automatically executed at activation. When the dialog box is closed after setting the [Debug Settings] dialog box, the emulator will automatically be connected.
2.3 Re-connecting the Emulator When the emulator is disconnected, re-connection is possible by using the following methods. Select [Debug -> Connect] or click the [Connect] toolbar button ( ) to re-connect the emulator. Note: When re-connecting the emulator, the load module must be registered to the High-performance Embedded Workshop beforehand. 2.
Section 3 Debugging This section describes the debugging operations and their related windows and dialog boxes. 3.1 Setting the Environment for Emulation The method for setting the environment for emulation is described here. This environment must be set correctly before debugging is started. 3.1.1 Opening the [Configuration Properties] Dialog Box Selecting [Setup -> Emulator -> System…] or clicking the [Emulator System] toolbar button ( [Configuration Properties] dialog box. ) opens the Figure 3.
[General] page [Device] Selects the target MCU to be emulated. See the hardware manual for details. [Custom Device enable] Customizes the target MCU. Checking this box allows the user to make settings on the [Custom Device] page. [Mode] Selects the operating mode of the target MCU. [Clock] Selects the speed of the input clock of the target MCU. [Timer Resolution] Selects the resolution of the timer for use in execution time measurement and performance analysis. Select one of the following values.
3.1.2 Customizing the Settings for the Target MCU Selecting [Custom Device enable] in the [Configuration Properties] dialog box adds the [Custom Device] page to the dialog box. Figure 3.2 [Configuration Properties] Dialog Box ([Custom Device] Page) Use this page to customize the target MCU. This procedure is necessary when the target MCU currently in use is not included in the list of [Device]. The items are adopted by the device last selected.
3.1.3 Selecting the Interface to be Connected Checking [Change driver in start up] on the [Configuration Properties] dialog box allows a selection of the driver next time the emulator is connected. Figure 3.3 [Driver Details] Dialog Box [Driver]: Selects the driver that connects the High-performance Embedded Workshop and the emulator. [Details]: Sets the details of the driver being connected. [Interface]: The name of the interface to be connected. This should not be changed in this emulator.
3.1.4 Opening the [Memory Mapping] Dialog Box Selecting [Setup -> Emulator -> Memory Resource…] or clicking the [Emulator Memory Resource] toolbar button ( ) opens the [Memory Mapping] dialog box. Figure 3.4 [Memory Mapping] Dialog Box [Add...]: Displays the [Edit Memory Mapping] dialog box, allowing the user to modify the address range and attributes of a memory map. [Modify...
3.1.5 Changing the Memory Map Setting Clicking the [Add…] button on the [Memory Mapping] dialog box or clicking the [Modify…] button after selecting the information on the memory map setting you want to change opens the [Edit Memory Mapping] dialog box. Figure 3.5 [Edit Memory Mapping] Dialog Box Use this dialog box to change the address range and attributes of a memory map. [From]: Enter the start address of the map range. [To]: Enter the end address of the map range.
3.2 Downloading a Program This section describes how to download a program and view it as source code or assembly-language mnemonics. Note: After a break has occurred, the [Editor] window displays the location of the present program counter (PC). In most cases, for example if an Elf/Dwarf2-based project is moved from its original path, the source file may not be automatically found. In this case, a source file browser dialog box is displayed to allow you to manually locate the source file. 3.2.
In this window, the following items are shown on the left as information on lines. • 1st column (Line Number column): A line number for the source file • 2nd column (Source Address column): Address information for the source line • 3rd column (On Chip Break column): On-chip breaks • 4th column (S/W Breakpoints column): PC, bookmark, and breakpoint information The text area is displayed in the right part of the [Editor] window.
To switch off a column in all source files 1. Click the right-hand mouse button on the [Editor] window or select the [Edit] menu. 2. Click the [Define Column Format…] menu item. 3. The [Global Editor Column States] dialog box is displayed. 4. A check box indicates whether the column is enabled or not. If it is checked, the column is enabled. If the check box is gray, the column is enabled in some files and disabled in others. Deselect the check box of a column you want to switch off. 5.
3.2.3 Viewing the Assembly-Language Code If you have a source file open, right-click to open the pop-up menu and select the [View Disassembly] option to open a Disassembly view at the same address as the current Source view. It is also possible to view the disassembly using the new integrated [Disassembly view] in the source file.
3.2.4 Modifying the Assembly-Language Code You can modify the assembly-language code by double-clicking on the instruction that you want to change. The [Assembler] dialog box will be opened. Figure 3.9 [Assembler] Dialog Box The address, instruction code, and mnemonic are displayed. Enter a new instruction or edit the old instruction in the [Mnemonics] field. Pressing the [Enter] key will replace the memory content with the new instruction and move on to the next instruction.
3.3 Viewing the Current Status Choose [View -> CPU -> Status] or click the [View Status] toolbar button ( see the current status of the debugging platform. ) to open the [Status] window and Figure 3.11 [Status] Window The [Status] window has following three sheets: • [Memory] sheet Displays information about the current memory status including the memory mapping resources and the areas used by the currently loaded object file.
3.4 Reading and Displaying the Emulator Information Regularly Use the [Extended Monitor] window to know the changing information on the emulator no matter the user program is running or halted. Note: 3.4.1 The extended monitor function does not affect the execution of the user program since it monitors the user system or the signal output from the target MCU in the emulator by using the emulator’s hardware circuit.
3.4.2 Selecting Items to be Displayed Selecting [Properties…] from the popup menu displays the [Extended Monitor Configuration] dialog box. Figure 3.13 [Extended Monitor Configuration] Dialog Box This dialog box allows the user to set the items to be displayed in the [Extended Monitor] window. Note: The items that can be set in this window depend on the emulator in use. For details, refer to the online help.
3.5 Displaying Memory Contents in Realtime Use the [Monitor] window to monitor the memory contents during user program execution. In the Monitor function, the realtime operation is retained since the bus monitoring circuit of the emulator sets the read/write signal of the MCU as a trigger and holds the address bus and data bus values to update the displayed contents of the memory. Up to eight points or 256 bytes in total can be set by using the eight monitoring channels on the bus monitoring circuit.
[Name]: Decides the name of the monitor window. [Options]: Sets monitor conditions. [Address]: Sets the start address for monitoring. [Size]: Sets the range for monitoring. [Access]: Sets the access size to be displayed in the monitor window. [Auto-Refresh at rate]: Sets the interval for acquisition by monitoring (500 ms at minimum). [Reading the Initial Value]: Selects reading of the values in the monitored area when the monitor window is opened.
Figure 3.15 [Monitor] Window During user program execution, the display is updated according to the setting value of the auto-update interval. Note: Select [Refresh] from the popup menu when data is not displayed correctly after changing the address or content of memory. 3.5.2 Changing the Monitor Settings Selecting [Monitor Setting…] from the popup menu of the [Monitor] window displays the [Monitor Setting] dialog box, which allows the settings to be changed.
3.5.6 Hiding the [Monitor] Window When using the Monitor function to monitor the value of a variable from the [Watch] window, hide the [Monitor] window for the effective use of the screen. The current monitoring information is listed as the submenu when selecting [Display -> CPU -> Monitor]. The list consists of the [Monitor] window name and the address to start monitoring. When the left of the list is checked, the [Monitor] window is being displayed.
3.5.7 Managing the [Monitor] Window Selecting [Display -> CPU -> Monitor -> Windows Select…] displays the [Windows Select] dialog box. In this window, the current monitoring condition is checked and the new monitoring condition is added, edited, and deleted in succession. Selecting multiple monitoring conditions enables a temporary stop of update, hiding, and deletion. Figure 3.17 [Windows Select] Dialog Box [Add]: Adds a new monitoring condition.
3.6 Looking at Variables This section describes how you can look at variables in the source program. 3.6.1 [Watch] Window You can view any value in the [Watch] window. Figure 3.18 [Watch] Window The [R] mark shows that the value of the variable can be updated during user program execution. It is possible to recognize the method for updating the value during user program execution according to the color of the [R] mark.
Notes: 1. This function can be set per variable or per element or body for structures of data. 2. The color of an [R] in the [Name] column changes according to the monitoring settings. 3. A variable that is allocated to a register cannot be selected for monitoring. 4. The procedure to display or modify the contents of memory differs depending on the product. If the display of memory contents is updated during execution of the user program, realtime emulation may not be available.
3.7 Using the Event Points The emulator has the event point function to support breakpoints of the following three types. Software breakpoints: Execution of the user program stops when the instruction at the specified address is fetched. Up to 255 software breakpoints can be set. Any content at the specified address is replaced by a break instruction (a dedicated instruction for use with the emulator).
3.7.1 Setting a Software Breakpoint Use the [Software] sheet on the [Event] window to display, change, or add settings for software breakpoints. Select [Add...] or [Edit…] from the popup menu displayed on the [Software] sheet. The [Breakpoint Properties] dialog box (the [Software Break] page) will appear. Figure 3.
To add a new software breakpoint, select an empty line from the list box on the [Software Break] page and click the [Edit…] button. To change existing settings, select the software breakpoint that you want to change from the list box and click the [Edit…] button. The [Software Break] dialog box is displayed. Figure 3.21 [Software] Dialog Box ([Address] Page) Specify the breakpoint’s address in the [Address] edit box and click the [OK] button.
3.7.2 Setting an On-Chip Breakpoint Use the [On Chip] sheet on the [Event] window to display, change, or add settings for on-chip breakpoints. Select [Add...] or [Edit…] from the popup menu displayed on the [On Chip] sheet. The [Breakpoint Properties] dialog box (the [On Chip Break] page) will appear. Figure 3.22 [Breakpoint Properties] Dialog Box ([On Chip Break] Page) [Sequential Break]: Use this item to specify a sequential break consisted of on-chip breakpoints.
List box: Displays the current settings for each of the channels. If no setting has been made for a channel, only the channel number is displayed here. When a channel is used for the sequential break function, S is displayed next to the channel number. [Edit…]: Clicking this button opens the [On Chip Break Channel n] dialog box (n: channel number), which allows the user to set a break condition for a selected channel. [Reset]: Clears the settings made for the selected channel.
[Address]: Sets address bus conditions. [Don’t Care]: Selects no address bus condition. [Address]: Sets an address bus value. [Use mask]: Sets mask conditions. Set the mask bits if [Use mask] is selected. Masked bits satisfy this break condition regardless of their values. [Data]: Sets data bus conditions. [Don’t Care]: Selects no data bus condition. [Value]: Sets a data bus value. [Use mask]: Sets mask conditions. Set the mask bits if [Use mask] is selected.
3.7.3 Settings an On-Emulator Breakpoint Use the [On Emulator] sheet on the [Event] window to display, change, or add settings for on-emulator breakpoints. Select [Add...] or [Edit…] from the popup menu displayed on the [On Chip] sheet. The [Breakpoint Properties] dialog box (the [On Emulator Break] page) will appear. Figure 3.24 [Breakpoint Properties] Dialog Box ([On Emulator Break] Page) List box: Displays the current settings for each of the channels.
The user can set more complex break conditions in the [On Emulator Break Channel n] dialog box by a combination of conditions provided on pages [Address], [Data], [Bus/Area], [Probe], [Interrupt], and [Count]. Figure 3.
[Address]: Sets address conditions. [Don’t Care]: Selects no address bus condition. [Address]: Select this button to set the address bus value specified in [Start] as the break condition. [Range]: A break occurs in the range of the address bus values specified from [Start] (start address) to [End] (end address). [Outside Range]: Select this option to generate a break with an address bus outside the range set in [Range]. [f()…]: The address range of a function can be set by [Start] and [End].
[External 32bit]: Selects an external area with the 32-bit width where no emulation memory is allocated as the condition. [External 16bit]: Selects an external area with the16-bit width where no emulation memory is allocated as the condition. [External 8bit]: Selects an external area with the 8-bit width where no emulation memory is allocated as the condition. [Emulator 32bit]: Selects an external area with the 32-bit width where emulation memory is allocated as the condition.
3.7.8 Deleting an Event Point Select an event point and choose [Delete] from the popup menu to remove the selected event point. To retain the event point but not have it cause an event when its conditions are met, use the [Disable] option (see section 3.15.7, Disabling an Event Point). 3.7.9 Deleting All Event Points Choose [Delete All] from the popup menu to remove all event points. 3.7.
3.8 Viewing the Trace Information The emulator acquires the results of each instruction execution into the trace buffer as trace information and displays it in the [Trace] window. The conditions for the trace information acquisition can be specified in the [Trace Acquisition] dialog box. Since trace information in bus-cycles is acquired by the hardware circuit and stored in the trace buffer, the realtime operation is retained.
[R/W]: Whether access was read (RD) or write (WR) [SZ]: Selects the size of an access as B (byte), W (word), or L (longword). [Status]: Bus status during this cycle; DTC operation, PROG (prefetch), Data (CPU data access cycle), DMAC (DMAC cycle), or STACK (STACK cycle). [Area]: Memory area being accessed; ROM (on-chip ROM), RAM (on-chip RAM), I/O (onchip I/O), 8- 16-, or 32-bit EXT (external), or 8- 16-, or 32-bit EMU (emulation memory).
3.8.3 Specifying Trace Acquisition Conditions The capacity of the trace buffer is limited. When the buffer becomes full, the oldest trace information is overwritten. Setting the trace acquisition condition allows acquisition of useful trace information and effective use of the trace buffer. There are the following types of trace acquisition conditions.
(1) [Condition] page Figure 3.27 [Trace Acquisition Properties] Dialog Box ([Condition] Page) [Sequential Trace Stop]: Use this option to set a sequential trace stop by using channels 1 to 7. The sequential trace stop function allows trace acquisition to stop when the conditions of several channels are satisfied in the specified order. Two to seven pass points and one reset point are selectable as sequential trace stop conditions. The conditions are satisfied in the order of 1 to 7.
[Back]: Puts the setting back to the previous state at the time the dialog box has been displayed. List box: Displays the current settings for each of the channels. If no setting has been made for a channel, only the channel number is displayed here. When a channel is used for the sequential trace stop function, S is displayed next to the channel number. When a reset condition for a sequential trace stop is enabled, R is displayed next to channel 8. PtoP is for use in the Point to Point trace.
(2) [Other] page Figure 3.28 [Trace Acquisition] Dialog Box ([Other] Page) [When trace-buffer full]: Selects an action to take when the trace buffer becomes full. [No action]: Overwrites the oldest information in the trace buffer. [Stop trace]: Stops trace acquisition without stopping the user program execution. [Stop execution and trace]: Stops the user program execution. [Time measurement unit]: Selects the minimum time unit for the time stamping of the bus trace information.
[Clock/8]: Time stamping is in terms of the number of bus-clock cycles, i.e., is synchronized with 1/8 cycle of the system clock signal (φ). [Selection of the trace contents]: Selects whether or not to display time stamps, IRQs, or executed instructions. [Detailed time stamp]: Acquires 32-bit time stamp information. No IRQ or executed instruction is displayed. [Execute code,Irq]: Displays IRQs and executed instructions. Lower 16 bits of time stamps are fixed to 0.
(3) [Trace Acquisition Condition Channel n] dialog box Use this dialog box to set pass points and a reset point for a sequential trace stop, and conditions in the address range trace, address range conditional trace, conditional trace, Point to Point trace, execution time measurement, and a trigger output. Figure 3.
[None]: [Address]: Select this option if you do not want to take any of the actions listed above. This is useful for a trigger output or execution time measurement. Sets the start and end addresses of the range in the address range trace, address range conditional trace, or Point to Point trace. [Start]: Set the start address. [End]: Set the end address. [f()…]: The address range of a function can be set by [Start] and [End].
3.8.4 Searching for a Trace Record Use the [Trace Find] dialog box to search for a trace record. To open this dialog box, choose [Find...] from the popup menu. Figure 3.30 [Trace Find] Dialog Box The [Trace Find] dialog box has the following options: [General]: [Not designation]: Searches for information that does not match the conditions set in other pages when this box is checked. [Upward search]: Searches upwards when this box is checked. [Start PTR]: Enters a PTR value to start a search.
[R/W]: Select the type of access cycles. [Don't care]: Detects no read/write condition when this box is checked. [Setting]: Detects the specified read/write condition. [RD]: Read cycle [WR]: Write cycle [Area]: Select the area being accessed. [Don't care]: Detects no area condition when this box is checked. [Setting]: Detects the specified area condition.
Clicking the [OK] button after setting conditions in those pages stores the settings and starts searching. Clicking the [Cancel] button closes this dialog box without setting of conditions. When a trace record that matches the search conditions is found, the line for the trace record will be highlighted. When no matching trace record is found, a message dialog box will appear. Only the trace information that satisfies all the conditions set in above pages will be searched.
3.8.11 Extracting Records from the Acquired Information Use the filtering function to extract the records you need from the acquired trace information. The filtering function allows the trace information acquired by hardware to be filtered by software.
[InstructionAddress]: [Don't care]: Detects no address when this box is checked. [Value]: Detects the specified instruction address. Enter an address value. [Point]: Enter a single value as an instruction address. [Range]: Specify an instruction address range. [From]: Enter a single address value or the start of the instruction address range. [To]: Enter the end address of the instruction address range. [Data]: Set a data condition. [Don't care]: Detects no data when this box is checked.
[Area]: Select the area being accessed. [Don't care]: Detects no area condition when this box is checked. [Setting]: Detects the specified area condition. [INROM]: Detects accesses to the ROM area. [INRAM]: Detects accesses to the RAM area. [I/O]: Detects accesses to the I/O area. [EXT-32]: Detects accesses to the 32-bit EXT (external memory). [EXT-16]: Detects accesses to the 16-bit EXT (external memory). [EXT-8]: Detects accesses to the 8-bit EXT (external memory).
Set filtering conditions and then press the [OK] button. This starts filtering according to the conditions. Clicking the [Cancel] button closes the [Trace Filter] dialog box, which holds the settings at the time when the dialog box was opened. In filtering, only the trace information that satisfies one or more filtering conditions set in the above pages will be displayed in the [Trace] window.
3.8.13 Analyzing Statistical Information Choose [Statistic] from the popup menu to open the [Statistic] dialog box and analyze statistical information under the specified conditions. Figure 3.33 [Statistic] Dialog Box [Statistic Analysis]: Setting required for analysis of statistical information. [Default]: Sets a single input value or character string. [Range]: Sets the input value or character string as a range. [Item]: Sets the item for analysis.
This dialog box allows the user to analyze statistical information concerning the trace information. Set the target of analysis in [Item] and the input value or character string by [Start] and [End]. Click the [Result] button after setting a condition by pressing the [New] or [Add] button to analyze the statistical information and display its result in the [Result] list. Note: In this emulator, only [PTR] can be set as a range. Each of other items must be specified as a character string.
3.9 Analyzing Performance Use the performance analysis function to measure the rate of execution time. The performance analysis function does not affect the realtime operation because it measures the rate of execution time in the specified range by using the circuit for measurement of hardware performance included in the emulator. Select one of the following five modes according to the purpose of measurement. Table 3.
Table 3.
3.9.1 Opening the [Performance Analysis] Window Choose [View -> Performance -> Performance Analysis] or click the [PA] toolbar button ( [Select Performance Analysis Type] dialog box. ) to open the Figure 3.35 [Select Performance Analysis Type] Dialog Box Select [E6000H Performance Analysis] and then click the [OK] button to open the [Performance Analysis] window. Figure 3.
3.9.2 Setting Conditions for Measurement Conditions for measurement can be displayed and changed in the [Performance Analysis] window. Select a point where a condition is to be set, and then select [Set…] from the popup menu to display the [Performance Analysis Properties] dialog box. Select either from the following five modes as the condition by the [Measurement Method] option: Table 3.
(1) Time Of Specified Range Measurement Figure 3.38 Time Of Specified Range Settings [Range Name]: The name of the range to be measured [Range]: The range for the Time Of Specified Range Measurement [Start Address]: Address to start measurement [End Address]: Address to end measurement Measures the execution time and the execution count in the range between the start address and end address.
(2) Start Point To End Point Measurement Figure 3.39 Start Point To End Point Measurement Settings [Range Name]: The name of the range to be measured [Point]: The range for the Start Point To End Point Measurement [Start Address]: Address to start measurement [End Address]: Address to end measurement [Time Out Action]: The action to take when a timeout or count-out occurs. Disable: Disables setting of a timeout or count-out value.
Measures the execution time and the execution count in the range between start address and end address. Starts measurement with a detected program prefetch at the start address, and then stops with a detected program prefetch at the end address. The execution count is incremented every time the program is prefetched at the end address of the specified range. The execution time measured includes the time spent while being called from the specified range.
(4) Access Count Of Specified Range Measurement Figure 3.
(5) Called Count Of Specified Range Measurement Figure 3.42 Called Count Of Specified Range Measurement Settings [Range Name]: The name of the range to be measured [Range]: The range for the Called Count Of Specified Range Measurement [Start Address]: Start address [End Address]: End address [Call Range]: The range for the Called Count Of Specified Range Measurement. As the call range, specify the start and end addresses of the selected subroutine.
3.9.3 Starting Performance Data Acquisition Executing the user program clears the result of previous measurement and automatically starts measuring the rate of execution time according to the conditions that have been set. Stopping the user program displays the result of measurement in the [Performance Analysis] window. 3.9.4 Deleting a Measurement Condition Select [Reset] from the popup menu with a measurement condition selected to delete the condition. 3.9.
3.10 Profiling Function 3.10.1 Enabling the Profile Choose [View->Performance->Profile] to open the [Profile] window. Choose [Enable Profiler] from the popup menu of the [Profile] window. The item on the menu will be checked. 3.10.2 Specifying Measuring Mode You can specify whether to trace functions calls while profile data is acquired. When function calls are traced, the relations of function calls during user program execution are displayed as a tree diagram.
3.10.4 [List] Sheet Figure 3.43 [Profile] Window ([List] Sheet) This window displays the address and size of a function or a global variable, the number of times the function is called or the global variable is accessed, and profile data. When the column header is clicked, data are sorted in alphabetic or numeric ascending/descending order. Double-clicking the [Function/Variable] or [Address] column displays the source program of the address in the line.
3.10.5 [Tree] Sheet Figure 3.44 [Profile] Window ([Tree] Sheet) This window displays the relation of function calls in a tree structure. Displayed contents are the address, size, stack size, and number of function calls and execution cycles. The stack size and number of function calls are values when the function is called. The [Tree] sheet is only available when [Not trace the function call] is not checked in the popup menu of the [Profile] window.
• Not trace the function call Stops tracing function calls while profile data is acquired. This menu is used when acquiring profile data of the program in which functions are called in a special way, such as task switching in the OS. To display the relation of function calls in the [Tree] sheet of the [Profile] window, acquire profile data without selecting this menu.
3.11 [Profile-Chart] Window Figure 3.45 [Profile-Chart] Window This window displays the relation of calls for a specific function. This window displays the calling relation for the function specified in the [List] sheet or [Tree] sheet in the [Profile] window. The specified function is displayed in the middle, the calling function on the left side, and the called function on the right side. Values beside the calling and called functions show the number of times the function has been called.
• Multiple View If the [Profile-Chart] window is going to be opened when it has already been opened, selects whether another window is to be opened or the same window is to be used to display data. When a check mark is shown to the left side of the menu text, another window is opened. • Output Profile Information File… Displays the [Save Profile Information File] dialog box. Profiling results are saved in a profile information file (.pro extension).
3.12 RTOS Extension Function The RTOS extension function supports the debugging of RTOS tasks. The function is implemented by setting the IDs of RTOS tasks at particular addresses. This extends the following emulator functions. • Step operation • Tracing • Performance analysis • On-emulator break 3.12.1 [RTOS Support Function Configuration Properties] Dialog Box Select [Option -> Emulator -> RTOS Support Function] or click the [RTOS Support Function] toolbar button ( ).
[RTOS Support Function]: Sets up the RTOS extension function. [Don’t Care]: Disables the RTOS extension function. [TASK ID writing area]: Specifies the address where the task ID is written to in the RTOS. [TASK ID writing area] input edit box: Specifies the address where the task IDs are written. Set an address within the on-chip I/O area that does not contain I/O registers. [Setting...
3.12.3 Functions Made Available by [TASK Selection] (1) Display of the [TASK Selection] Settings Figure 3.47 [Status] Window [Platform] sheet: Includes information on the emulation environment, such as the CPU type and operating mode. [Selection TASK ID]: Displays the values set for [TASK Selection 1] to [TASK Selection 3] in the [RTOS Support Function Configuration Properties] dialog box. (2) Display of Trace Information ([Trace] Window) The [TASK] is added to the items for display.
3.12.4 Performance Measurement (Conditions for Measurement) The following conditions are included among those selectable under the [Measurement Method] option for measurement of execution. Setting the [Measurement Method] option: [Performance Analysis Properties] page: [TASK ID]: 3.12.5 Sets a condition for measurement. Allows specification of the values set for [TASK Selection 1] to [TASK Selection 3] in the [RTOS Support Function Configuration Properties] dialog box as conditions.
Section 4 Tutorial 4.1 Introduction This section describes the main functions of the emulator by using a tutorial program. The tutorial program is based on the C++ program that sorts ten random data items in ascending or descending order. The tutorial program performs the following actions: • The main function repeatedly calls the tutorial function to repeat sorting. • The tutorial function generates random data to be sorted and calls the sort and change functions in that order.
4.2 Running the High-performance Embedded Workshop Open a workspace by following the procedure listed in section 2.1.3, Selecting an Existing Workspace. Select the following directory. OS installation drive \Workspace\Tutorial\E6000H\1650 Note: The directory mentioned above cannot be specified depending on the version of the software. In such cases, specify the following directory instead.
4.3 Connecting the Emulator 4.3.1 Selecting a Session The selectable session depends on the emulator. Select the session suitable for the emulator in use. Table 4.
4.4 Downloading the Tutorial Program 4.4.1 Downloading the Tutorial Program Download the object program to be debugged. • Select [Download module] from [Tutorial.abs] of [Download modules]. Figure 4.
4.4.2 Displaying the Source Program The High-performance Embedded Workshop allows the user to debug a user program at the source level. • Double-click [Tutorial.cpp] under [C++ source file]. Figure 4.5 [Editor] Window (Displaying the Source Program) • Select a font and size that are legible if necessary. Initially the [Editor] window shows the start of the user program, but the user can use the scroll bar to scroll through the user program and look at the other statements.
4.5 Setting a Software Breakpoint A software breakpoint is a simple debugging function. The [Editor] window provides a very simple way of setting a software breakpoint at any point in a program. For example, to set a software breakpoint where the sort function is called: • Select by double-clicking the [S/W Breakpoints] column on the line containing the sort function call. Figure 4.6 [Editor] Window (Setting a Software Breakpoint) The symbol • will appear on the line containing the sort function.
4.6 Setting Registers Set a value in the program counter before executing the program. • Select [Registers] from the [CPU] submenu of the [View] menu or click the [Register] toolbar button ( display the [Register] window. ) to Figure 4.7 [Register] Window • To change the value of the program counter (PC), double-click on the PC value area in the [Register] window with the mouse. The following dialog box is then displayed, and the value can be changed.
4.7 Executing the Program Execute the program as described in the following: • To execute the program, select [Go] from the [Debug] menu, or click the [Go] button on the toolbar. Figure 4.9 [Go] Button While the program is executed, the current address bus value and the operating state of the MCU are displayed on the status bar.
Figure 4.
The user can see the cause of the break that occurred last time in the [Status] window. • Select [Status] from the [CPU] submenu of the [View] menu or click the [Status] toolbar button ( ). After the [Status] window is displayed, open the [Platform] sheet, and check the Status of Cause of last break. Figure 4.11 [Status] Window Note: The items that can be displayed in this window differ depending on the product. For the items that can be displayed, refer to section 3, Debugging, or the online help.
4.8 Reviewing Breakpoints The user can see all the breakpoints set in the program in the [Event] window. • Select [Eventpoints] from the [Code] submenu of the [View] menu or click the [Eventpoints] toolbar button ( ). The [Event] window is displayed. Select the [Software] sheet. Figure 4.12 [Event] Window The popup menu, opened by clicking the [Event] window with the right-hand mouse button, allows the user to set or change breakpoints, define new breakpoints, and delete, enable, or disable breakpoints.
4.9 Referring to Symbols The [Label] window can be used to display the information on symbols in modules. Select [Label] from the [Symbol] submenu of the [View] menu. The [Label] window is displayed so that the user can refer to the addresses of symbols in modules. Figure 4.
4.10 Viewing Memory When the label name is specified, the user can view the memory contents that the label has been registered in the [Memory] window. For example, to view the memory contents corresponding to _main in byte size: • Select [Memory …] from the [CPU] submenu of the [View] menu or click the [View Memory] toolbar button ( ) to open the [Format] dialog box. Enter _main in the [Begin] edit box and +ff in the [End] edit box, respectively, and select Byte in the [Format] combo box. Figure 4.
4.11 Watching Variables As the user steps through a program, it is possible to watch that the values of variables used in the user program are changed. For example, set a watch on the long-type array a declared at the beginning of the program, by the following procedure: • Click the left of displayed array a in the [Editor] window to place the cursor. • Select [Instant Watch...] with the right-hand mouse button. The following dialog box will be displayed. Figure 4.
The user can also add a variable to the [Watch] window by specifying its name. • Click the [Watch] window with the right-hand mouse button and select [Add Watch…] from the popup menu. The following dialog box will be displayed. Figure 4.18 [Add Watch] Dialog Box • Enter variable i to [Variable or expression] edit box and click the [OK] button. The [Watch] window will now also show the int-type variable i. Figure 4.
The user can click mark ‘+’ at the left side of array a in the [Watch] window to watch all the elements. Figure 4.
4.12 Displaying Local Variables The user can display local variables in a function by using the [Locals] window. For example, we will examine the local variables in the tutorial function, which declares local variables j, i, and p_sam. • Select [Locals] from the [Symbol] submenu of the [View] menu. The [Locals] window is displayed. The [Locals] window shows the local variables in the function currently pointed to by the program counter, along with their values.
4.13 Stepping Through a Program The High-performance Embedded Workshop provides a range of step menu commands that allow efficient program debugging. Table 4.2 Step Options Menu Command Description Step In Executes each statement, including statements within functions. Step Over Executes a function call in a single step. Step Out Steps out of a function, and stops at the statement following the statement in the program that called the function.
Figure 4.23 [Editor] Window (Step In) • The highlighted line moves to the first statement of the sort function in the [Editor] window.
4.13.2 Executing the [Step Out] Command The [Step Out] command steps out of the called function and stops at the next statement of the calling statement. • To step out of the sort function, select [Step Out] from the [Debug] menu, or click the [Step Out] button in the toolbar. Figure 4.24 [Step Out] Button Figure 4.25 [High-performance Embedded Workshop] Window (Step Out) The data of variable a displayed in the [Watch] window is sorted in the ascending order.
4.13.3 Executing the [Step Over] Command The [Step Over] executes a function call in a single step and stops at the next statement of the main program. • To step through all statements in the change function in a single step, select [Step Over] from the [Debug] menu, or click the [Step Over] button on the toolbar. Figure 4.26 [Step Over] Button Figure 4.27 [High-performance Embedded Workshop] Window (Step Over) The data of variable a displayed in the [Watch] window is sorted in the descending order.
4.14 Forced Breaking of Program Executions The High-performance Embedded Workshop can force a break during the execution of a program. • Cancel all the breakpoints. • To execute the remaining sections of the tutorial function, select [Go] from the [Debug] menu or the [Go] button on the toolbar. Figure 4.28 [Go] Button • The program goes into an endless loop. To force a break during execution, select [Halt] from the [Debug] menu or the [Halt] button on the toolbar. Figure 4.29 [Halt] Button 4.
4.16 Break Function The emulator provides break functions by software breaks, on-chip breaks, and on-emulator breaks. Software breakpoints, on-chip breakpoints, and on-emulator breakpoints can be set in the High-performance Embedded Workshop’s [Event] window. An overview and setting of the break function are described below. 4.16.1 Software Break Function The emulator can set up to 255 software breakpoints.
Figure 4.
• Click the [Edit…] button to display the [Software Break] dialog box. Figure 4.34 [Software Break] Dialog Box • Use the [Editor] window to refer to the address on the line that has ‘p_sam->s0=a[0];’ within the tutorial function and enter this address in the [Address] edit box. In this example, enter H’0000106E. Note: This dialog box differs depending on the product. For the items of each product, refer to section 3, Debugging, or the online help. • Click the [OK] button.
The software breakpoint that has been set is displayed in the [Event] window. Figure 4.35 [Event] Window (Software Breakpoint Setting) Note: The items that can be displayed in this window differ depending on the product. For the items that can be displayed, refer to section 3, Debugging, or the online help. • Close the [Event] window. • To stop the tutorial program at the breakpoint, select [Reset Go] from the [Debug] menu.
The program runs until it stops at the breakpoint that has been set. Figure 4.
The [Status] window displays the following contents: Figure 4.37 Displayed Contents of the [Status] Window (Software Break) Note: The items that can be displayed in this window differ depending on the product. For the items that can be displayed, refer to section 3, Debugging, or the online help.
4.16.2 On-Chip Break Function Setting of an on-chip breakpoint on channel 4 such that a break is triggered when the break condition has been satisfied five times is explained as an example of the use of on-chip breakpoints. Note: The channels on which the satisfaction count can be specified differ depending on the product. For details on each product, refer to section 3, Debugging, or the online help.
• Make the following settings in the group boxes on the [Address] page: Uncheck the [Don’t Care] checkbox. Then use the [Editor] window to refer to the address on the line that has ‘a[i]=j;’ within the tutorial function and enter this address in the [Address] edit box. In this example, enter H'0000105c. • Make the following settings in the boxes on the [Count] page: Uncheck the [Don’t Care] checkbox. Enter D’5 in the [Count] edit box. Note: The content of this dialog box differs depending on the product.
4.17 Trace Functions The trace functions of the emulator use the realtime trace buffer, which can store the information of up to 128-k bus cycles. The content of this buffer, which is constantly updated during execution, is displayed in the [Trace] window. Select [Trace] from the [Code] submenu of the [View] menu or click the [Trace] toolbar button ( the [Trace] window. ) to display Figure 4.
4.17.1 Displaying Trace Information by the Free Trace Function The free trace function allows continuous acquisition of trace information from the start of user program execution to the occurrence of a break. (1) All break conditions must be deleted. Clicking the right-hand mouse button on the [Trace] window displays a popup menu. Select [Acquisition…] from this menu to display the [Trace Acquisition Properties] dialog box. Ensure that [Free Trace] is checked and then click the [Close] button. Figure 4.
(2) Set a software breakpoint at the address on the line that has ‘p_sam->s0=a[0];’ within the tutorial function (refer to section 4.16.1, Software Break Function). (3) Select [Reset Go] from the [Debug] menu. Execution stops when the break condition is satisfied, and the [Trace] window then displays the trace information. Figure 4.
4.17.2 Displaying Trace Information by the Trace Stop Function While the trace stop function is in use, acquisition of trace information stops when a specified condition is satisfied. The user can check the program flow by the trace information without breaking the user program execution. (1) Delete all the break conditions that have been set. Uncheck [Free Trace] on the [Condition] page of the [Trace Acquisition Properties] dialog box (otherwise, the free trace mode will be selected).
(3) An address must be set as the condition. Uncheck [Don’t Care] on the [Address] page of the [Trace Acquisition Condition Channel 1] dialog box. Then use the [Editor] window to refer to the address on the line that includes ‘a[i]=j;’ within the tutorial function and enter this address in the [Start] edit box. In this example, enter H'00001048. This completes the setting of the address. Click the [OK] button to close the [Trace Acquisition Condition Channel 1] dialog box. Figure 4.
(4) Items that have been set are displayed in the list box on the [Condition] page of the [Trace Acquisition Properties] dialog box. Click the [Close] button on this dialog box. Figure 4.45 [Trace Acquisition Properties] Dialog Box (Trace Stop) (5) Select [Reset Go] from the [Debug] menu. The trace condition is satisfied, and the [Trace] window then displays the following contents. Figure 4.
4.17.3 Displaying Trace Information by the Conditional Trace Function The conditional trace function only acquires trace information at the address where a specified condition has been satisfied. This is useful for analyzing a program focused on reading from or writing to a specific address (e.g. a global variable or memory mapped I/O). (1) If the user program is running, select [Halt Program] from the [Debug] menu to halt the program. (2) Delete all the break conditions that have been set.
4.17.4 Statistics The number of times the on-chip RAM has been written to can be included in the acquired trace information. (1) Delete all the break conditions that have been set. Click [Reset All] on the [Condition] page of the [Trace Acquisition Properties] dialog box to cancel trace conditions. Check [Free Trace] on the [Condition] page of the [Trace Acquisition Properties] dialog box.
(5) Select [R/W] in the [Item] combo box and enter WR in the [Start] edit box. Then, click the [New] button. “R/W=WR” will be displayed in the [Condition] column of the [Result] list box. Figure 4.
(6) Then, select [Area] from the [Item] combo box and enter INRAM in the [Start] edit box. Then, click the [Add] button; the new condition is now added to the “R/W=WR” display in the [Condition] column of the [Result] list box, so that it now shows “R/W=WR & Area=INRAM”. This completes the setting of the conditions. Figure 4.
(7) To start statistical analysis of the specified condition, press the [Result] button. The number of write operations that satisfies the conditions and the PTR values will be displayed. Figure 4.51 [Statistic] Dialog Box (Result of Analysis) (8) Click the [Close] button to close the [Statistic] dialog box. (9) Delete the event points that have been set and clear the trace information. Clicking the right-hand mouse button on the [Event] window displays a popup menu.
4.17.5 Function Calls This mechanism is only used to collect trace information on the function calls. (1) Make the setting so that a break occurs at the address on the line that has ‘p_sam->s0=a[0];’ within the tutorial function (H’0000106e in this example) (for details, refer to section 4.16.1, Software Break Function). (2) Select [Reset Go] from the [Debug] menu. Execution stops when the break condition is satisfied, and the [Trace] window then displays the trace information.
4.18 Stack Trace Function The emulator uses the information on the stack to display the function call history. Notes: 1. This function can be used only when the load module that has the Dwarf2-type debugging information is loaded. Such load modules are supported in H8S, H8/300 C/C++ compiler V4.0 or later. 2. For details on the stack trace function, refer to the online help. • Double-click the [S/W Breakpoints] column in the sort function and set a software breakpoint. Figure 4.
• Select [Reset Go] from the [Debug] menu. • After the break in program execution, select [Stack Trace] from the [Code] submenu of the [View] menu to open the [Stack Trace] window. Figure 4.55 [Stack Trace] Window Figure 4.55 shows that the position of the program counter is currently at the selected line of the sort() function, and that the sort() function is called from the tutorial() function. To delete the software breakpoint, double-click the [S/W Breakpoints] column in the sort function again.
4.19 Performance Analysis Function Performance analysis by the emulator is available in the following modes: • Time Of Specified Range Measurement • Start Point To End Point Measurement • Start Range To End Range Measurement • Access Count Of Specified Range Measurement • Called Count Of Specified Range Measurement In this tutorial, we describe the Time Of Specified Range Measurement. 4.19.
(3) Select the line in the [Performance Analysis] window that has 1 in its [No] column and click the right-hand mouse button to display a popup menu. Select [Set…] from this popup menu to display the [Performance Analysis Properties] dialog box. Figure 4.58 [Performance Analysis Properties] Dialog Box (4)Select Time Of Specified Range Measurement from the [Measurement Method PA1] combo box. (5) The parameter settings are as follows. • Enter sort in the [Range Name] edit box.
Note: The addresses figured out in the [Input Function Range] dialog box are just for reference. In some cases, the end address of a function may be incorrect. Check the last instruction of the function in the [Disassembly] window to correct the value set in [End Address] so that it will be the address of the last instruction (in general, the last instruction of a function is a RTS instruction).
4.20 Profiling Function The profiling function allows the user measure the performance for each of the functions. (1) Select [Profile] from the [View] menu to open the [Profile] window. Figure 4.
(2) To enable the profiling function, click the right-hand mouse button on the [Profile] window to show the popup menu and select [Enable Profiler]. Figure 4.
(3) Set an on-chip breakpoint by an address condition at the line which includes “delete p_sam;” in the tutorial function (see section 4.16.2, On-Chip Break Function). Figure 4.64 [Editor] Window (Setting an On-Chip Breakpoint) (4) To use the profiling function for measurement, select [Reset Go] from the [Debug] menu.
(5) The [Profile] window is shown below. Figure 4.65 [Profile] Window ([List] Sheet) (6) Click the [Tree] tab on the [Profile] window to display the [Tree] sheet. Figure 4.
(7) Click the right-hand mouse button on the [Profile] window and select [View Profile-Chart] to open the [Profile-Chart] window. Figure 4.67 [Profile-Chart] Window (8) To disable the profiling function, uncheck [Enable Profiler] in the popup menu opened by clicking the righthand mouse button on the [Profile] window. Delete all the break conditions that have been set.
4.21 Monitor Function The emulator allows monitoring of the contents of specified addresses in memory during execution of the user program. In this example, we monitor the content of the address range where variable a of the tutorial function is stored. (1) Select the [CPU] submenu from the [View] menu. Selecting [Monitor Setting…] from the [Monitor] submenu displays the [Monitor Setting] dialog box. Figure 4.
(2) Set the items in the [Monitor Setting] dialog box as follows: • Enter monitor1 in the [Name] edit box. • Set the parameters in the [Options] group box as follows: (a) Use the [Watch] window to refer to the address on the line where variable a, which is defined within the tutorial function, is allocated and enter this address in the [Address] edit box. In this example, H’00FFB400 is entered. (b) Enter H’20 in the [Size (byte)] combo box. (c) Select BYTE (ASCII) from the [Access (Format)] combo box.
(3) Click the [OK] button to open the [Monitor] window. Figure 4.70 [Monitor] Window (4) Select [Reset Go] from the [Debug] menu. When the contents of the address range changes by execution, the updated values are in red (i.e. the color that was selected in the [Foreground] and [Background] combo boxes). Values will be displayed in black if they have not been updated or a certain period of time has elapsed since the last update. Figure 4.
140
Section 5 Software Specifications and Notes Specific to This Product This section describes the software specifications and notes specific to the H8SX E6000H emulator. 5.1 Supported Hardware This emulator software is specialized for the H8SX E6000H emulator. 5.2 Target Platforms The following debugging platforms can be selected in this emulator. The target MCUs to be emulated depend on the selected debugging platform. Table 5.
5.3 Memory Map • Some emulators may not support the memory mapping function. • Attributes of a memory map can be defined in units of blocks as shown in figure 5.1. • No_access Area may not be selectable as an attribute of a memory map depending on the emulator in use. • No memory exists when No_access Area is selected, even though it is defined as an internal memory area.
5.4 Displaying and Modifying the Contents of Memory 5.4.1 Displaying and Modifying the Contents of Memory during Execution The emulator accesses memory in the following two ways to display and modify the contents of memory during user program execution. Table 5.2 Access Types for Displaying and Modifying Contents of Memory Period Suspended Display Modification Automatically updates the display of the memory contents without stopping the user program execution.
5.4.3 Parallel Access Function The parallel access function is implemented by the DTC channels specialized for the debugger, which are not user resources. However, because the DTC channels are included in the user-resource DTC module, the parallel access function may not be available in the following cases depending on the state of the target MCU or the emulator settings: • When the DTC module is in the module stop state, the parallel access function is not available.
5.6 5.6.1 Event Functions Software Breakpoints • A software breakpoint is accomplished by replacing the instruction at the specified address with a special instruction. Accordingly, it can only be set to the RAM area including the emulation memory. However, it cannot be set to the following addresses: ⎯ An address whose memory content is H'5770 ⎯ Areas other than the CS areas (except for the on-chip ROM and RAM areas) • Do not modify the contents of the software breakpoints addresses by the user program.
5.6.3 On-Emulator Break • A break will occur several cycles after a condition is satisfied. • The states of IRQ15 to IRQ0 are ORed and this result is applied as the IRQ condition. • The address and data conditions are satisfied on the bus cycles where the values on the address bus or data bus match. Consider the following points when setting these conditions. • Longword access Longword data is read and written in a single bus cycle.
Table 5.
Table 5.
5.7 5.7.1 Trace Functions Displaying the Trace Information • The states of IRQ15 to IRQ0 are ORed and this result is applied as the IRQ condition. • The executed instructions and timestamp cannot be displayed together. 5.7.2 Specifying Trace Acquisition Conditions • The trace will stop several cycles after a condition is satisfied. • The state of IRQ15 to IRQ0 are ORed and this result is applied as the IRQ condition.
5.9 5.9.1 Performance Analysis Function Errors An error will be included in the measured performance as follows: • ±one-resolution error (±20-ns error when the measurement resolution is 20 ns) This error may occur when the user program execution starts or stops (breaks) or when the measurement start or end condition is satisfied. • Frequency stability of the crystal oscillating module for performance analysis: ±0.01% 5.9.
5.11 RTOS Extension Function 5.11.1 Input Values for the [TASK ID writing area] Input Edit Box Specify the address to which the task IDs are written. Set an integer multiple of eight within the on-chip I/O area that does not contain I/O registers. The address ranges for the on-chip I/O area are H’00FFEA00 to H’00FFFE00 and H’00FFFF20 to H’00FFFFFC. Table 5.6 shows examples of input values for the [TASK ID writing area] input edit box for particular debugging platforms. Table 5.
5.12 Input Format 5.12.1 Entering Masks Address bus conditions and data bus conditions can be input with masks. Addresses can be masked in 1-, 3-, or 4-bit units. When a bit is masked, it always satisfies the condition. To specify a mask for an address bus condition, specify the mask value in the [Mask] area. The mask for data conditions is similarly specified in the [Mask] area. To specify any further mask, specify 1 for the digits to be ignored. Examples of mask specification are listed below.
Section 6 Error Messages 6.1 6.1.1 Error Messages of the Emulator Error Messages at Emulator Initiation The emulator displays error messages in the format below if an error occurs at emulator initiation in the dedicated message dialog box when the High-performance Embedded Workshop is used. Table 6.1 lists error messages at emulator initiation.
Table 6.1 Error Messages at Initiation Error Message Description and Solution There is no configuration file. The configuration file that is required to initiate the emulator cannot be found. Exit and re-install the High-performance Embedded Workshop. Then re-connect the user system interface cable, turn on the power of the emulator, and reinitiate the High-performance Embedded Workshop. If the problem is not solved, contact us and describe the error occurrence in detail.
Table 6.1 Error Messages at Initiation (cont) Error Message Description and Solution Can’t find firmware file There is an error in the file that is required at emulator initiation. Exit the High-performance Embedded Workshop, re-connect the user system interface cable, turn on the power of the emulator, and re-initiate the High-performance Embedded Workshop. If the problem is not solved, contact us and describe the error occurrence in detail.
156
Appendix A Menus Table A.1 shows GUI menus. Table A.1 GUI Menus Toolbar Button Menu Option Shortcut View Command Line Ctrl + L Opens the [Command Line] window. Workspace Alt + K Opens the [Workspace] window. Output Alt + U Opens the [Output] window. Disassembly Ctrl + D Opens the [Disassembly] window. CPU Registers Ctrl + R Opens the [Register] window. Memory… Ctrl + M Opens the [Memory] window. IO Ctrl + I Opens the [IO] window. Status Ctrl + U Opens the [Status] window.
Table A.1 GUI Menus (cont) Menu Option View (cont) Graphic Performance Shortcut Toolbar Button Remarks Image… Shift + Ctrl + G Opens the [Image] window. Waveform… Shift + Ctrl + V Opens the [Waveform] window. Performance Analysis Shift + Ctrl + P Opens the [Performance Analysis] window. Profile Shift + Ctrl + F Opens the [Profile] window. Option Debug Debug Sessions… Opens the [Debug Sessions] dialog box to list, add, or remove the debug session.
Table A.1 GUI Menus (cont) Toolbar Button Menu Option Shortcut Debug (cont) Step In F11 Executes a block of user program before breaking. Step Over F10 Executes a block of user program before breaking. If a subroutine call is reached, then the subroutine will not be entered. Step Out Shift + F11 Executes the user program to reach the end of the current function. Step… Step Mode Remarks Launches the [Step Program] dialog box allowing the user to modify the settings for stepping.
Table A.1 GUI Menus (cont) Option Setup Customize… Customize the Highperformance Embedded Workshop application. Options… Sets option of the Highperformance Embedded Workshop application. Format Views… Configure fonts, colors, keywords and so on, for the window. Radix Hexadecimal Uses a hexadecimal for displaying a radix in which the numerical values will be displayed and entered by default.
Appendix B Command Lines Table B.1 lists the High-performance Embedded Workshop commands. Table B.1 High-performance Embedded Workshop Commands No.
Table B.1 High-performance Embedded Workshop Commands (cont) No.
Table B.1 High-performance Embedded Workshop Commands (cont) No.
Table B.1 High-performance Embedded Workshop Commands (cont) No.
Renesas Microcomputer Development Environment System User's Manual H8SX E6000H Emulator Publication Date: Rev.1.00, August 25, 2003 Rev.9.00, June 13, 2006 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Customer Support Department Global Strategic Communication Div. Renesas Solutions Corp. © 2006. 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.
H8SX E6000H Emulator User’s Manual 2-6-2, Ote-machi, Chiyoda-ku, Tokyo, 100-0004, Japan
