REJ10J1662-0300 SH-2A, SH-2 E200F Emulator Additional Document for User’s Manual Supplementary Information on Using the SH7286, SH7285, and SH7243 Renesas Microcomputer Development Environment System SuperH™ Family / SH7280 Group E200F for SH7280 Group R0E572800EMU00E Rev.3.00 Revision Date: Oct.
Rev. 3.00 Oct.
Notes regarding these materials 1. This document is provided for reference purposes only so that Renesas customers may select the appropriate Renesas products for their use. Renesas neither makes warranties or representations with respect to the accuracy or completeness of the information contained in this document nor grants any license to any intellectual property rights or any other rights of Renesas or any third party with respect to the information in this document. 2.
Rev. 3.00 Oct.
Contents Section 1 System Configuration ........................................................................1 1.1 1.2 Components of the Emulator ............................................................................................ 1 System Configuration ....................................................................................................... 5 Section 2 Connecting the Emulator to the User System....................................9 2.1 2.2 2.3 2.4 2.5 2.6 2.
4.2 Delay Time for the User System Interface........................................................................ 66 Rev. 3.00 Oct.
Section 1 System Configuration Section 1 System Configuration 1.1 Components of the Emulator The E200F emulator supports the SH7285 group (SH7285), SH7286 group (SH7286), and SH7243 group (SH7243). Table 1.1 lists the components of the emulator. Table 1.1 Components of the Emulator Classification Component Hardware Emulator main unit AC adapter Appearance Quantity 1 Remarks R0E0200F1EMU00: Depth: 185.0 mm, Width: 130.0 mm, Height: 45.0 mm, Mass: 321.
Section 1 System Configuration Table 1.1 Components of the Emulator (cont) Classification Component Hardware (cont) USB cable External probe Appearance Quantity Remarks 1 Length: 1500 mm, Mass: 50.
Section 1 System Configuration Table 1.2 Optional Components of the Emulator Classification Component Hardware Appearance Quantity Remarks External bus trace unit 1 R0E0200F1ETU00: Depth: 90.0 mm, Width: 125.0 mm, Height: 15.2 mm, Mass: 100 g Emulation memory unit (Memory capacity: 8 Mbytes or 16 Mbytes) 1 R0E0200F1MSR00 (8 Mbytes), R0E0200F1MSR01 (16 Mbytes): Depth: 90.0 mm, Width: 125.0 mm, Height: 15.
Section 1 System Configuration Table 1.2 Optional Components of the Emulator (cont) Classification Component Hardware (cont) Appearance Quantity Remarks SH7286 (PLQP0176KBA) user system interface board 1 R0E572860CFK00: Depth: 60.0 mm, Width: 90.0 mm, Height: 26.0 mm, Mass: 45 g SH7286 (PLQP0176LB-A) user system interface board 1 R0E572860CFL00: Depth: 60.0 mm, Width: 90.0 mm, Height: 26.0 mm, Mass: 45 g Expansion profiling unit 1 R0E0200F0EPU00: Depth: 98.0 mm, Width: 115.0 mm, Height: 15.
Section 1 System Configuration 1.2 System Configuration Figure 1.1 shows an example of the emulator system configuration. - When the EV-chip unit is not used: E200F Expansion profiling unit High-performance Embedded Workshop USB 2.0/1.1 H-UDI port connector User system H-UDI and AUD PC - When the EV-chip unit is not used: External bus trace unit Expanded profilling unit Trace cable High-performance Embedded Workshop Emulation memory unit EV-chip unit USB 2.0/1.
Section 1 System Configuration Table 1.
Section 1 System Configuration Notes: 1. When the EV-chip unit is not used, the H-UDI port connector must be installed on the user system. When designing the user system, refer to section 2.3, Connecting the Emulator to the User System by Using the H-UDI Port Connector. For this system configuration, note that the H-UDI and AUD pins of the MCU are occupied by the emulator. 2.
Section 1 System Configuration Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System Section 2 Connecting the Emulator to the User System 2.1 Connecting the Emulator to the User System When the emulator is connected to the user system, use the optional EV-chip unit, user system interface board, and trace cable. 2.
Section 2 Connecting the Emulator to the User System Figure 2.1 Connecting the Trace Cable to E200F when Using the EV-chip Unit Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System • Connect the EV-chip unit to the trace cable (CN1 side). Figure 2.2 Connecting the Trace Cable to the EV-chip Unit CAUTION Check the orientation of pin 1 before connecting parts. Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System 2.2.2 Connecting the E200F External Bus Trace Unit to the EV-chip Unit • When the external bus trace unit is used with the EV-chip unit, connect the external bus trace unit to the EV-chip unit as shown in figure 2.3. Figure 2.3 Connecting the External Bus Trace Unit to the EV-chip Unit Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System • After checking the location of pin 1, connect the EV-chip unit, external bus trace unit, and trace cable. Figure 2.4 Connecting the EV-chip Unit, External Bus Trace Unit, and Trace Cable CAUTION Check the orientation of pin 1 before connecting parts. Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System 2.2.3 Connecting the H-UDI/AUD Probe to the EV-chip Unit • Connect the H-UDI/AUD probe to the EV-chip unit as shown in figure 2.5. Figure 2.5 Connecting the H-UDI/AUD Probe to the EV-chip Unit CAUTION Check the orientation of pin 1 before connecting parts. Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System 2.2.4 Connecting the E200F Emulation Memory Unit to the EV-chip Unit • When the emulation memory unit is used with the EV-chip unit, connect the emulation memory unit to the EV-chip unit (figure 2.6). Figure 2.6 Connecting the Emulation Memory Unit to the EV-chip Unit Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System • After checking the location of pin 1, connect the EV-chip unit, emulation memory unit, and trace cable. Figure 2.7 Connecting the Emulation Memory Unit, EV-chip Unit, and Trace Cable CAUTION Check the orientation of pin 1 before connecting parts. Rev. 3.00 Oct.
Section 2 Connecting the Emulator to the User System 2.2.5 Connecting the E200F External Bus Trace Unit, Emulation Memory Unit, and EVchip Unit • When the external bus trace unit is used with the emulation memory unit and EV-chip unit, as shown in figure 2.8, connect them in the positions of (a), (b), and (c) for the external bus trace unit, emulation memory unit, and EV-chip unit, respectively.
Section 2 Connecting the Emulator to the User System 2.2.6 Connecting the EV-chip Unit to the User System Interface Board • After checking the location of pin 1, connect the EV-chip unit to the user system interface board. EV-chip unit Connector No. EV-Chip Unit Connector No. User I/F Connector 1 (CN3) User I/F Connector 2 (CN4) Board Connector No. UCN1 UCN2 Board Spacer User system Figure 2.
Section 2 Connecting the Emulator to the User System 2.2.7 Using the E200F Emulator as a Stand-Alone Unit • If you are using the E200F emulator unit without connecting it to a user system, refer to table 1.3 in section 1.2, System Configuration, and make connections as shown in figure 2.10 until the EV-chip unit becomes available. EV-chip unit When using the emulator as a stand-alone unit When connecting the emulator to the user system User system interface board User system Figure 2.
Section 2 Connecting the Emulator to the User System 2.3 Connecting the Emulator to the User System by Using the H-UDI Port Connector To connect the E200F emulator (hereinafter referred to as the emulator), the H-UDI port connector must be installed on the user system to connect the user system interface cable. When designing the user system, refer to the recommended circuit between the H-UDI port connector and the MCU.
Section 2 Connecting the Emulator to the User System 2.4 Installing the H-UDI Port Connector on the User System Table 2.2 shows the recommended H-UDI port connectors for the emulator. Table 2.2 Recommended H-UDI Port Connectors Connector Type Number Manufacturer Specifications 36-pin connector DX10M-36S Hirose Electric Co., Ltd.
Section 2 Connecting the Emulator to the User System Pin No. Signal Input/ Output*1 Pin No. Note Output 1 AUDCK 2 GND 3 AUDATA0 19 Output 4 GND 5 AUDATA1 6 GND 7 AUDATA2 8 GND 9 AUDATA3 10 GND 11 _AUDSYNC*2 Output 12 Output Output Input/ Output*1 TMS Input 20 GND 21 _TRST 22 (GND)*4 23 TDI 24 GND 25 TDO 26 GND 27 Output Signal *2 GND 29 UVCC GND 30 GND 13 N.C. 31 _RES*2 14 GND 32 GND 15 N.C. 33 GND *3 16 GND 34 GND 17 TCK 35 N.C.
Section 2 Connecting the Emulator to the User System 2.6 2.6.1 Recommended Circuit between the H-UDI Port Connector and the MCU Recommended Circuit (36-Pin Type) Figures 2.12 and 2.13 show recommended circuits for connection between the H-UDI and AUD port connectors (36 pins) and the MCU when the emulator is in use. Notes: 1. Do not connect anything to the N.C. pins of the H-UDI port connector. 2.
Section 2 Connecting the Emulator to the User System VCC = I/O power supply All pulled-up at 4.7 kΩ or more VCC VCC VCC VCC H-UDI port connector (36-pin type) 2 4 6 8 10 12 14 16 18 20 22 GND AUDCK GND AUDATA0 GND AUDATA1 GND AUDATA2 GND AUDATA3 GND AUDSYNC GND N.C. GND N.C. GND 28 30 32 34 36 GND GND GND GND GND AUDATA1 7 AUDATA2 9 AUDATA3 11 AUDSYNC 13 15 TCK TMS TDO 25 ASEBRKAK 27 /ASEBRK 29 UVCC 31 RES 33 GND 35 N.C.
Section 2 Connecting the Emulator to the User System VCC = I/O power supply All pulled-up at 4.7 kΩ or more VCC VCC VCC VCC H-UDI port connector (36-pin type) 2 4 6 8 10 12 14 16 18 20 22 24 26 GND AUDCK GND AUDATA0 GND GND GND AUDATA1 AUDATA2 AUDATA3 SH7285 or SH7243 1 AUDCK 3 AUDATA0 5 AUDATA1 7 AUDATA2 9 AUDATA3 11 AUDSYNC GND AUDSYNC GND N.C. GND N.C.
Section 2 Connecting the Emulator to the User System 2.7 Using the IC Socket to Mount an MCU on the User System Figure 2.14 shows an example of the external appearance of the configuration when the IC socket is used to mount an MCU on the user system using and the E200F emulator is connected in onchip debugging mode.
Section 2 Connecting the Emulator to the User System CAUTION 1. Check the orientation of pin 1 before connecting parts. 2. As the IC socket and IC top cover for mounting on the user system, we recommend the following products.
Section 2 Connecting the Emulator to the User System Rev. 3.00 Oct.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 3.1 Differences between the MCU and the Emulator 1. When the emulator system is initiated, it initializes the general registers and part of the control registers as shown in table 3.1. The initial values of the MCU are undefined. When the emulator is initiated from the workspace, a value to be entered is saved in a session. Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 4. Reset Signals The MCU reset signals are only valid during emulation started with clicking the GO or STEPtype button. If these signals are enabled on the user system in command input wait state, they are not sent to the MCU. Note: Do not break the user program when the _RES, _BREQ, or _WAIT signal is being low. A TIMEOUT error will occur.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 7. Memory Access to the External Flash Memory Area The emulator can download the load module to the external flash memory area (for details, refer to section 6.21, Download Function to the Flash Memory Area, in the SH-2A, SH-2 E200F Emulator User’s Manual). Neither memory write nor BREAKPOINT setting is enabled for the external flash memory area.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Note: Function 1 can be used when the AUD pins of the device are not connected to the emulator. The AUD pins are multiplexed with other pins. When the AUD function is used by the SH7286, SH7285, and SH7243 E200F emulator, AUD pins are used regardless of the settings of the pin function controller (PFC). Note that the AUD function can be used regardless of the above AUD pin settings in EV-chip unit debugging mode. 10.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 ⎯ Customization of the I/O-register definition file The internal I/O registers can be accessed from the [IO] window. However, note the following when accessing the SDMR register of the bus state controller. Before accessing the SDMR register, specify addresses to be accessed in the I/O-register definition file (SH7285.IO or SH7243.IO) and then activate the High-performance Embedded Workshop.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 16. MCU operation mode Boot or the User boot mode is not supported in this emulator. Rev. 3.00 Oct.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 3.2 Specific Functions for the Emulator when Using the SH7286, SH7285, and SH7243 In on-chip debugging mode, a reset must be input when the emulator is activated. 3.2.1 Event Condition Functions The emulator is used to set event conditions for the following three functions: • Break of the user program • Internal trace • Start or end of performance measurement Table 3.7 lists the types of Event Condition. Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Table 3.8 lists the combinations of conditions that can be set under Ch1 to Ch11 and the software trace. Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 The [Event Condition 11] dialog box is used to specify the count of [Event Condition 1] and becomes a reset point when the sequential condition is specified. Sequential Setting: Use the [Combination action(Sequential or PtoP)] dialog box to specify the sequential condition and the start or end of performance measurement. Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Table 3.9 Conditions to Be Set (cont) Classification Item Description [Ch1, 2, 3] list box (cont) Ch2 to Ch1 PA Sets the performance measurement period during the time from the satisfaction of the condition set in Event Condition 2 (start condition) to the satisfaction of the condition set in Event Condition 1 (end condition).
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Usage Example of Sequential Break Extension Setting: A tutorial program provided for the product is used as an example. For the tutorial program, refer to section 6, Tutorial, in the SH-2A, SH-2 E200F Emulator User’s Manual. The conditions of Event Condition are set as follows: 1. Ch1 Breaks address H’00001086 when the condition [Prefetch address break after executing] is satisfied. 2.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Figure 3.1 [Source] Window at Execution Halt (Sequential Break) If the sequential condition, performance measurement start/end, or point-to-point for the internal trace is set, conditions of Event Condition to be used will be disabled. Such conditions must be enabled from the popup menu by clicking the right mouse button on the [Event Condition] sheet. Notes: 1.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 6. If a condition of which intervals are satisfied closely is set, no sequential condition will be satisfied. • Set the Event conditions, which are satisfied closely, by the program counter with intervals of two or more instructions. • After the Event condition has been matched by accessing data, set the event condition by the program counter with intervals of 17 or more instructions. 7.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 3.2.2 Trace Functions The emulator supports the trace functions listed in table 3.10. Table 3.10 Trace Functions Function Internal Trace AUD Trace Branch trace Supported Supported Memory access trace Supported Supported Software trace Not supported Supported The internal and AUD traces are set in the [I-Trace/AUD-Trace acquisition] dialog box of the [Trace] window. Rev. 3.00 Oct.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Internal Trace Function: When [I-Trace] is selected for [Trace type] on the [Trace mode] page of the [I-Trace/AUD-Trace acquisition] dialog box, the internal trace can be used. Figure 3.2 [I-Trace/AUD-Trace acquisition] Dialog Box (Internal Trace Function) Rev. 3.00 Oct.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 The following three items can be selected as the internal trace from [Type] of [I-Trace mode]. Table 3.11 Information on Acquiring the Internal Trace Item Acquisition Information [M-Bus & Branch] Acquires the data and branch information on the M-bus. • Data access (read/write) • PC-relative access • Branch information [I-Bus] Acquires the data on the I-bus.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Using the Event Condition restricts the condition; the following three items are set as the internal trace conditions. Table 3.12 Trace Conditions of the Internal Trace Item Acquisition Information Trace halt Acquires the internal trace until the Event Condition is satisfied. (The trace content is displayed in the [Trace] window after a trace has been halted. No break occurs in the user program.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Set [I-Trace] as [Ch4 to Ch5 PtoP] in the [Combination action (Sequential or PtoP)] dialog box. When point-to-point and trace acquisition condition are set simultaneously, they are ANDed. Notes on Internal Trace: • Timestamp The timestamp is the clock counts of Bφ (48-bit counter). Table 3.13 shows the timing for acquiring the timestamp. Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 • Trace acquisition condition Do not set the trace-end condition for the SLEEP instruction and the branch instruction according to which the delay slot becomes the SLEEP instruction. When [I-BUS, M-Bus & Branch] is selected and the trace acquisition condition is set for the M-bus and I-bus with the Event Condition, set the M-bus condition and the I-bus condition for [Event Condition 1] and [Event Condition 2], respectively.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 AUD Trace Functions: This function is operational when the AUD pins of the MCU are connected to the emulator. Table 3.14 shows the AUD trace acquisition mode that can be set in each trace function. Table 3.14 AUD Trace Acquisition Mode Type Mode Description Continuous trace occurs Realtime trace When the next branching occurs while the trace information is being output, all the information may not be output.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Figure 3.3 [Trace mode] Page When the AUD trace function is used, select the [AUD function] radio button in the [Trace type] group box of the [Trace mode] page. Rev. 3.00 Oct.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 (a) Branch Trace Function The branch source and destination addresses and their source lines are displayed. Branch trace can be acquired by selecting the [Branch trace] check box in the [AUD function] group box of the [Trace mode] page. The branch type can be selected in the [AUD Branch trace] page. Figure 3.4 [AUD Branch trace] Page Rev. 3.00 Oct.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 (b) Window Trace Function Memory access in the specified range can be acquired by trace. Two memory ranges can be specified for channels A and B. The read, write, or read/write cycle can be selected as the bus cycle for trace acquisition. Setting Method: (i) Select the [Channel A] and [Channel B] check boxes in the [AUD function] group box of the [Trace mode] page. Each channel will become valid.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Note: When [M-BUS] or [I-BUS] is selected, the following bus cycles will be traced. • M-BUS: A bus cycle generated by the CPU is acquired. • I-BUS: A bus cycle generated by the CPU or DMA is acquired. (c) Software Trace Function Note: This function can be supported with SuperH C/C++ compiler (manufactured by Renesas Technology Corp.; including OEM and bundle products) V7.0 or later.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 7. The AUD trace is disabled while the profiling function is used. 8. If breaks occur immediately after executing non-delayed branch and TRAPA instructions and generating a branch due to exception or interrupt, a trace for one branch will not be acquired immediately before such breaks. However, this does not affect on generation of breaks caused by a BREAKPOINT and a break before executing instructions of Event Condition. 9.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 occur at this address. When the program halts with the break condition, the mark z disappears. 7. If you wish to use a BREAKPOINT (software break), specify the SH2A_SBSTK command to enable use of a user stack before setting a PC break. While enabled, extra four bytes of a user stack are used when a break occurs. The value of the stack pointer (R15) must be correctly set in advance because a user stack is to be used.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 (a) Specifying the measurement start/end conditions The measurement start/end conditions are specified by using Event Condition 1,2. The [Ch1,2,3] list box of the [Combination action] dialog box can be used. Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 For measurement tolerance, • The measured value includes tolerance. • Tolerance will be generated before or after a break. Note: When [Ch2 to Ch1 PA] or [Ch1 to Ch2 PA] is selected, to execute the user program, specify conditions set in Event Condition 2 and Event Condition 1 and one or more items for performance measurement. (b) Measurement item Items are measured with [Channel 1 to 4] in the [Performance Analysis] dialog box.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Table 3.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Notes: 1. In the non-realtime trace mode of the AUD trace, normal counting cannot be performed because the generation state of the stall or the execution cycle is changed. 2. If the internal ROM is not installed on the product, do not set the measurement item for the internal ROM area. 3. For SH7286, SH7285, and SH7243, do not set measurement items for the cache-miss counts, cacheable area, or non-cacheable area. 2.
Section 3 Software Specifications when Using the SH7286, SH7285, and SH7243 Rev. 3.00 Oct.
Section 4 User System Interface Circuits Section 4 User System Interface Circuits 4.1 User System Interface Circuits Figures 4.1 through 4.6 show user system interface circuits. Use them as a reference to determine the value of the pull-up resistance. SH7280 User system Vcc HD151015 EP1S10 EP1S10 CB3T16211 100 kΩ MD1 MD0 MD1 MD0 Vcc HD151015 EP1S10 EP1S10 CB3T16211 FWE 100 kΩ FWE Figure 4.1 User System Interface Circuits SH7280 User system _WDTOVF _WDTOVF Figure 4.
Section 4 User System Interface Circuits User system SH7280 Vcc HD151015 EP1S10 AHC14 AHC14 100 kΩ NMI NMI Vcc HD151015 LVC08 EP1S10 AHC14 AHC14 _RES _RES CN2 Figure 4.3 User System Interface Circuits Rev. 3.00 Oct.
Section 4 User System Interface Circuits SH7280 User system Vcc XTAL N.C. XTAL N.C. HD151015 EP1S10 LVTH16244 100 kΩ EXTAL EXTAL 3.3 V VCC VSS PLLVSS 0.01 μF 2200 pF 0.01 μF 2200 pF 1 μF 3.3 μF G6K_2G_DC3V VSS 3.3 V 1 μF PVCC VCC PLLVSS N.C. G6K_2G_DC3V 3.3 V AVCC AVCC AVSS AVREFVSS 0.01 μF 2200 pF 1 μF 3.3 μF 0.01 μF 2200 pF 1 μF 3.3 μF 1 μF G6K_2G_DC3V 3.3 V 1 μF AVREF AVREF VCL N.C. AVSS N.C. AVREFVSS N.C. VCL 0.1 μF Figure 4.
Section 4 User System Interface Circuits User system SH7280 PF(11:0) PF(11:0) AVcc DALC112S1 DA1, DA0 DA1, DA0 EP1S10 ASEBCK LVTH16244 ASEBRK N.C. Figure 4.5 User System Interface Circuits Rev. 3.00 Oct.
Section 4 User System Interface Circuits User system SH7280 Vcc PA23-PA21, PA14-PA10 PA8-PA6, PB19-PB15 PB9, PB6, PB3-PB0 PC15-0, PD31-PD20 PD15-PD0, PE15-PE13 PE7 PA23-PA21, PA14-PA10 PA8-PA6, PB19-PB15 PB9, PB6, PB3-PB0 PC15-0, PD31-PD20 PD15-PD0, PE15-PE13 PE7 100 kΩ EP1S10 CB3T16211 Vcc 100 kΩ PA5-PA0, PB12, PB11 PB8, PB7, PD19-PD16 PE15-PE13 EP1S10 Vcc 74V2G66 100 kΩ PA5-PA0, PB12, PB11 PB8, PB7, PD19-PD16 PE15-PE13 CB3T16211 Vcc 100 kΩ PA15, PA9, PB14, PB13 PB10, PE12-PE8 PE6-0 PA15, PA9
Section 4 User System Interface Circuits 3.3 V SH7280 User system MAX709R DrVCC 47 Ω DrVCC DrVSS N.C. DrVSS USBXTAL N.C. USBXTAL N.C. USBEXTAL 48 MHz USBEXTAL USD+ USD+ USD- USD- VBUS VBUS EP1S10 CB3T16211 100 kΩ 220 Ω Figure 4.7 User System Interface Circuits 4.2 Delay Time for the User System Interface Since the _RES and NMI signals are connected to the user system via the logic on the EV-chip unit, a delay time shown in table 4.
SH-2A, SH-2 E200F Emulator Additional Document for User's Manual Supplementary Information on Using the SH7286, SH7285, and SH7243 Publication Date: Rev.1.00, June 12, 2007 Rev.3.00, October 17, 2008 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Customer Support Department Global Strategic Communication Div. Renesas Solutions Corp. © 2008. Renesas Technology Corp., All rights reserved. Printed in Japan.
Sales Strategic Planning Div. Nippon Bldg., 2-6-2, Ohte-machi, Chiyoda-ku, Tokyo 100-0004, Japan RENESAS SALES OFFICES http://www.renesas.com Refer to "http://www.renesas.com/en/network" for the latest and detailed information. Renesas Technology America, Inc. 450 Holger Way, San Jose, CA 95134-1368, U.S.A Tel: <1> (408) 382-7500, Fax: <1> (408) 382-7501 Renesas Technology Europe Limited Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K.
SH-2A, SH-2 E200F Emulator Additional Document for User’s Manual Supplementary Information on Using the SH7286, SH7285, and SH7243
