ID052210 ARM920T STM1001 1K-100K IEEE1149 - Datasheet Archive

 

System and Interface Design Reference Copyright © 2010 ARM. All rights reserved. ARM DUI 0499A (ID052210) DSTREAM System and

 

DSTREAM System and Interface Design Reference Copyright © 2010 ARM. All rights reserved. ARM DUI 0499A (ID052210 ID052210) DSTREAM System and Interface Design Reference Copyright © 2010 ARM. All rights reserved. Release Information The following changes have been made to this book. Change history Date Issue Confidentiality Change May 2010 A Non-Confidential First release. Proprietary Notice Words and logos marked with ® or TM are registered trademarks or trademarks of ARM in the EU and other countries, except as otherwise stated below in this proprietary notice. Other brands and names mentioned herein may be the trademarks of their respective owners. Neither the whole nor any part of the information contained in, or the product described in, this document may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this document is subject to continuous developments and improvements. All particulars of the product and its use contained in this document are given by ARM in good faith. However, all warranties implied or expressed, including but not limited to implied warranties of merchantability, or fitness for purpose, are excluded. This document is intended only to assist the reader in the use of the product. ARM shall not be liable for any loss or damage arising from the use of any information in this document, or any error or omission in such information, or any incorrect use of the product. Where the term ARM is used it means "ARM or any of its subsidiaries as appropriate". This product includes software developed by the Apache Software Foundation (see http://www.apache.org). Confidentiality Status This document is Non-Confidential. The right to use, copy and disclose this document may be subject to license restrictions in accordance with the terms of the agreement entered into by ARM and the party that ARM delivered this document to. Product Status The information in this document is final, that is for a developed product. Web Address http://www.arm.com ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential ii Conformance Notices This section contains conformance notices. Federal Communications Commission Notice This device is test equipment and consequently is exempt from part 15 of the FCC Rules under section 15.103 (c). Class A Important: This is a Class A device. In residential areas, this device may cause radio interference. The user should take the necessary precautions, if appropriate. CE Declaration of Conformity The system should be powered down when not in use. It is recommended that ESD precautions be taken when handling DSTREAM, RealView ICE, and RealView Trace equipment. The DSTREAM, RealView ICE, and RealView Trace modules generate, use, and can radiate radio frequency energy and may cause harmful interference to radio communications. There is no guarantee that interference will not occur in a particular installation. If this equipment causes harmful interference to radio or television reception, which can be determined by turning the equipment off or on, you are encouraged to try to correct the interference by one or more of the following measures: · ensure attached cables do not lie across the target board · reorient the receiving antenna · increase the distance between the equipment and the receiver · connect the equipment into an outlet on a circuit different from that to which the receiver is connected · consult the dealer or an experienced radio/TV technician for help Note It is recommended that wherever possible shielded interface cables be used. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential iii Contents DSTREAM System and Interface Design Reference Chapter 1 Chapter 2 Conventions and feedback System Design Guidelines 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 Chapter 3 Target Interface Connections 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 ARM DUI 0499A ID052210 ID052210 Using adaptive clocking to synchronize the JTAG port . 2-2 Reset signals . 2-5 ARM reset signals . 2-6 DSTREAM reset signals . 2-7 Example reset circuits . 2-8 ASIC guidelines . 2-9 ICs containing multiple devices . 2-10 Boundary scan test vectors . 2-11 PCB guidelines . 2-12 PCB connections . 2-13 Target interface logic levels . 2-14 Signal descriptions . 3-2 JTAG port timing characteristics . 3-3 Serial Wire Debug . 3-5 SWD connections . 3-6 SWD timing requirements . 3-7 Trace signals . 3-8 Supported target connectors . 3-10 Mictor 38 . 3-11 ARM JTAG 20 . 3-15 TI JTAG 14 . 3-18 ARM JTAG 14 . 3-21 CoreSight 10 . 3-24 CoreSight 20 . 3-26 Copyright © 2010 ARM. All rights reserved. Non-Confidential iv Contents 3.14 3.15 3.16 3.17 Chapter 4 The DSTREAM User I/O connector . 4-2 Designing the Target Board for Tracing 5.1 5.2 5.3 5.4 ARM DUI 0499A ID052210 ID052210 3-29 3-33 3-36 3-37 User I/O Connections 4.1 Chapter 5 MIPI 34 . I/O diagrams . Voltage domains . Series termination . Overview of high-speed design . PCB track impedance . Signal requirements . Probe modeling . Copyright © 2010 ARM. All rights reserved. Non-Confidential 5-2 5-3 5-4 5-6 v List of Tables DSTREAM System and Interface Design Reference Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 Table 3-7 Table 3-8 Table 3-9 Table 3-10 Table 3-11 Table 3-12 Table 3-13 Table 3-14 Table 3-15 Table 3-16 Table 3-17 Table 3-18 Table 4-1 Table 5-1 ARM DUI 0499A ID052210 ID052210 Change history . ii DSTREAM JTAG A timing requirements . 3-3 SWD timing requirements . 3-7 TRACECLK frequencies . 3-8 Mictor 38 interface pinout table . 3-12 Mictor 38 signals . 3-13 ARM JTAG 20 interface pinout table . 3-15 ARM JTAG 20 signals . 3-16 TI JTAG 14 interface pinout table . 3-18 TI JTAG 14 signals . 3-19 ARM JTAG 14 interface pinout table . 3-21 ARM JTAG 14 signals . 3-22 CoreSight 10 interface pinout table . 3-24 CoreSight 10 signals . 3-25 CoreSight 20 interface pinout table . 3-26 CoreSight 20 signals . 3-27 MIPI 34 interface pinout table . 3-29 MIPI 34 signals . 3-31 Typical series terminating resistor values . 3-37 User I/O pin connections . 4-2 Data setup and hold . 5-4 Copyright © 2010 ARM. All rights reserved. Non-Confidential vi List of Figures DSTREAM System and Interface Design Reference Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 Figure 3-15 Figure 3-16 Figure 3-17 Figure 3-18 Figure 3-19 Figure 3-20 Figure 4-1 Figure 5-1 ARM DUI 0499A ID052210 ID052210 Basic JTAG port synchronizer . 2-3 Timing diagram for the Basic JTAG synchronizer . 2-3 JTAG port synchronizer for single rising-edge D-type ASIC design rules . 2-4 Timing diagram for the D-type JTAG synchronizer . 2-4 Example reset circuit logic . 2-8 TAP Controllers serially chained within an ASIC . 2-10 Typical PCB connections . 2-13 Target interface logic levels . 2-14 JTAG port timing diagram . 3-3 Typical SWD connections . 3-6 SWD timing diagrams . 3-7 Clock waveforms . 3-8 Mictor 38 connector pinout . 3-11 ARM JTAG 20 connector pinout . 3-15 TI JTAG 14 connector pinout . 3-18 ARM JTAG 14 connector pinout . 3-21 CoreSight 10 connector pinout . 3-24 CoreSight 20 connector pinout . 3-26 MIPI 34 connector pinout . 3-29 Input . 3-33 Output . 3-33 Input/Output . 3-33 Reset output . 3-33 Reset output with feedback . 3-34 VTRef input . 3-34 VTRef input (decoupled) . 3-34 Ground . 3-34 AC Ground . 3-35 User I/O pin connections . 4-2 Track impedance . 5-3 Copyright © 2010 ARM. All rights reserved. Non-Confidential vii List of Figures Figure 5-2 ARM DUI 0499A ID052210 ID052210 Data waveforms . 5-4 Copyright © 2010 ARM. All rights reserved. Non-Confidential viii Chapter 1 Conventions and feedback The following describes the typographical conventions and how to give feedback: Typographical conventions The following typographical conventions are used: monospace Denotes text that can be entered at the keyboard, such as commands, file and program names, and source code. monospace Denotes a permitted abbreviation for a command or option. The underlined text can be entered instead of the full command or option name. monospace italic Denotes arguments to commands and functions where the argument is to be replaced by a specific value. monospace bold Denotes language keywords when used outside example code. italic Highlights important notes, introduces special terminology, denotes internal cross-references, and citations. bold Highlights interface elements, such as menu names. Also used for emphasis in descriptive lists, where appropriate, and for ARM® processor signal names. Feedback on this product If you have any comments and suggestions about this product, contact your supplier and give: · ARM DUI 0499A ID052210 ID052210 your name and company Copyright © 2010 ARM. All rights reserved. Non-Confidential 1-1 Conventions and feedback · the serial number of the product · details of the release you are using · details of the platform you are using, such as the hardware platform, operating system type and version · a small standalone sample of code that reproduces the problem · a clear explanation of what you expected to happen, and what actually happened · the commands you used, including any command-line options · sample output illustrating the problem · the version string of the tools, including the version number and build numbers. Feedback on content If you have comments on content then send an e-mail to errata@arm.com. Give: · the title · the number, ARM DUI 0499A · if viewing online, the topic names to which your comments apply · if viewing a PDF version of a document, the page numbers to which your comments apply · a concise explanation of your comments. ARM also welcomes general suggestions for additions and improvements. ARM periodically provides updates and corrections to its documentation on the ARM Information Center, together with knowledge articles and Frequently Asked Questions (FAQs). Other information · · ARM Technical Support Knowledge Articles, · ARM DUI 0499A ID052210 ID052210 ARM Information Center, http://infocenter.arm.com/help/index.jsp Keil Distributors, http://www.keil.com/distis. Copyright © 2010 ARM. All rights reserved. Non-Confidential 1-2 Chapter 2 System Design Guidelines The following topics provide information on developing ARM® architecture-based devices and Printed Circuit Boards (PCBs) that can be debugged using DSTREAM: · Using adaptive clocking to synchronize the JTAG port on page 2-2 · Reset signals on page 2-5 · ARM reset signals on page 2-6 · DSTREAM reset signals on page 2-7 · Example reset circuits on page 2-8 · ASIC guidelines on page 2-9 · ICs containing multiple devices on page 2-10 · Boundary scan test vectors on page 2-11 · PCB guidelines on page 2-12 · PCB connections on page 2-13 · Target interface logic levels on page 2-14. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-1 System Design Guidelines 2.1 Using adaptive clocking to synchronize the JTAG port ARM® architecture-based devices using only hard macrocells, for example ARM7TDMI® and ARM920T ARM920T, use the standard five-wire JTAG interface (TCK, TMS, TDI, TDO, and nTRST). Some target systems, however, require that JTAG events are synchronized to a clock in the system. To ensure a valid JTAG CLK setting, these systems often support an extra signal (RTCK) at the JTAG port: · an Application-Specific Integrated Circuit (ASIC) with single rising-edge D-type design rules, such as one based on an ARM7TDMI-STM processor · a system where scan chains external to the ARM macrocell must meet single rising-edge D-type design rules. The adaptive clocking feature of DSTREAM addresses this requirement. When adaptive clocking is enabled, DSTREAM issues a TCK signal and waits for the RTCK signal to come back. DSTREAM does not progress to the next TCK until RTCK is received. · Note If you use the adaptive clocking feature, transmission delays, gate delays, and synchronization requirements result in a lower maximum clock frequency than with non-adaptive clocking. Do not use adaptive clocking unless it is required by the hardware design. · If, when autoconfiguring a target, the DSTREAM unit receives pulses on RTCK in response to TCK it assumes that adaptive clocking is required, and enables adaptive clocking in the target configuration. If the hardware does not require adaptive clocking, the target is driven slower than it could be. You can disable adaptive clocking using controls on the JTAG settings dialog box. · If adaptive clocking is used, DSTREAM cannot detect the clock speed, and therefore cannot scale its internal timeouts. If the target clock frequency is very slow, a JTAG timeout might occur. This leaves the JTAG in an unknown state, and DSTREAM cannot operate correctly without reconnecting to the processor. JTAG timeouts are enabled by default. You can disable JTAG timeouts by deselecting the option JTAG Timeouts Enabled in the RVConfig utility. You can use adaptive clocking as an interface to targets with slow or widely varying clock frequency, such as battery-powered equipment that varies its clock speed according to processing demand. In this system, TCK might be hundreds of times faster than the system clock, and the debugger loses synchronization with the target system. Adaptive clocking ensures that the JTAG port speed automatically adapts to slow system speed. The following figure shows a circuit for a basic JTAG port synchronizer. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-2 System Design Guidelines TMS TMO TDI TDI TDO TDO RTCK TCK Q D nCLR Q D TCK ASIC nCLR nTRST nTRST CLK CLK Figure 2-1 Basic JTAG port synchronizer The following figure shows a partial timing diagram for the basic JTAG synchronizer. The delay can be reduced by clocking the flip-flops from opposite edges of the system clock, because the second flip-flop only provides better immunity to metastability problems. Even a single flip-flop synchronizer never completely misses TCK events, because RTCK is part of a feedback loop controlling TCK. TCK CLK RTCK Figure 2-2 Timing diagram for the Basic JTAG synchronizer It is common for an ASIC design flow and its design rules to impose a restriction that all flip-flops in a design are clocked by one edge of a single clock. To interface this to a JTAG port that is completely asynchronous to the system, it is necessary to convert the JTAG TCK events into clock enables for this single clock, and to ensure that the JTAG port cannot overrun this synchronization delay. The following figure shows one possible implementation of this circuit. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-3 System Design Guidelines TCKFalli ngEn TDI CKEN D Q IN TCKRisingEn TDO OUT Scan CKEN Chain Shift En RTCK TCK D Q nCLR D Q nCLR TAP Ctrl CKEN State TMS Machine nRESET D Q nCLR nTRST CLK TMS Figure 2-3 JTAG port synchronizer for single rising-edge D-type ASIC design rules The following figure shows a corresponding partial timing diagram, and how TCKFallingEn and TCKRisingEn are each active for exactly one period of CLK. It also shows how these enable signals gate the RTCK and TDO signals so that they only change state at the edges of TCK. TCK CLK TCKRisingEn TCKFallingEn RTCK TAPC State TDO Figure 2-4 Timing diagram for the D-type JTAG synchronizer 2.1.1 See also Concepts · Reset signals on page 2-5. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-4 System Design Guidelines 2.2 Reset signals There are two types of reset signals available on ARM® devices. The manner in which DSTREAM expects these signals to be wired is described in the following topics: · ARM reset signals on page 2-6 · DSTREAM reset signals on page 2-7. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-5 System Design Guidelines 2.3 ARM reset signals All ARM® processors have a main processor reset that might be called nRESET, BnRES, or HRESET. This is asserted by one or more of these conditions: · power on · manual push button · remote reset from the debugger (using DSTREAM) · watchdog circuit (if appropriate to the application). Any ARM processor including the JTAG interface has a second reset input called nTRST (TAP Reset). This resets the EmbeddedICE logic, the Test Access Port (TAP) controller, and the boundary scan cells. It is activated by remote JTAG reset (from DSTREAM). It is strongly recommended that both signals are separately available on the JTAG connector. If the nRESET and nTRST signals are linked together, resetting the system also resets the TAP controller. This means that: · · 2.3.1 it is not possible to debug a system from reset, because any breakpoints previously set are lost you might have to start the debug session from the beginning, because DSTREAM may not recover when the TAP controller state is changed. See also Concepts · DSTREAM reset signals on page 2-7 · ARM DUI 0499A ID052210 ID052210 Example reset circuits on page 2-8. Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-6 System Design Guidelines 2.4 DSTREAM reset signals The DSTREAM unit has two reset signals connected to the debug target hardware: · nTRST drives the JTAG nTRST signal on the ARM® processor. It is an output that is activated whenever the debug software has to re-initialize the debug interface in the target system. · nSRST is a bidirectional signal that both drives and senses the system reset signal on the target. By default, this output is driven LOW by the debugger to re-initialize the target system. The target hardware must pull the reset lines to their inactive state to assure normal operation when the JTAG interface is disconnected. In the DSTREAM unit, the strong pull-up/pull-down resistance is approximately 33, and the weak pull-up/pull-down resistance is approximately 4.7k. Because you can select the drive strength for nTRST and nSRST, target assemblies with a variey of different reset configurations can be supported. 2.4.1 See also Concepts · ARM reset signals on page 2-6 · Example reset circuits on page 2-8. Reference Using the Debug Hardware Configuration Utilities: · ARM DUI 0499A ID052210 ID052210 Advanced configuration, ./com.arm.doc.dui0498a/CIHGABDH.html. Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-7 System Design Guidelines 2.5 Example reset circuits The circuit in the following figure shows a typical reset circuit logic for the ARM® reset signals and the DSTREAM reset signals. VDD Signals from JTAG connector VDD RST nTRST 10K TAP RESET Open-drain reset devices e.g. STM1001 STM1001 VDD TRST ARM processor VDD RST 10K SYSTEM RESET nSRST RESET 100R 100nF Manual reset Gnd Gnd To other logic Figure 2-5 Example reset circuit logic 2.5.1 See also Concepts · ARM reset signals on page 2-6 · ARM DUI 0499A ID052210 ID052210 DSTREAM reset signals on page 2-7. Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-8 System Design Guidelines 2.6 ASIC guidelines ASIC guidelines are described in the following topics: · ICs containing multiple devices on page 2-10 · Boundary scan test vectors on page 2-11. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-9 System Design Guidelines 2.7 ICs containing multiple devices If your ASIC contains multiple devices that have a JTAG Test Access Port (TAP) controller, you must serially chain them so that DSTREAM can communicate with all of them simultaneously. The chaining can either be within the ASIC, or externally. Note There is no support in DSTREAM for multiplexing TCK, TMS, TDI, TDO, and RTCK between a number of different processors. 2.7.1 TAP controllers serially chained within the ASIC The JTAG standard originally described serially chaining multiple devices on a PCB. This concept can be extended to serially chaining multiple TAP controllers within an ASIC, as shown in the following figure: TDO TDI TDO TDI TCK nTRST TMS TAP Controller TDO TDI TCK nTRST TMS First Tap Device TAP Controller Second Tap Device TCK nTRST TMS Figure 2-6 TAP Controllers serially chained within an ASIC This configuration does not increase the package pin count. It does increase JTAG propagation delays, but this impact can be small if you put unaddressed TAP controllers into bypass mode. 2.7.2 TAP controllers serially chained externally You can use separate pins on the ASIC for each JTAG port, and serially chain them externally (for example on the PCB). This configuration can simplify device testing, and gives the greatest flexibility on the PCB. However, this is at the cost of many pins on the device package. 2.7.3 See also Concepts · Boundary scan test vectors on page 2-11. Other information · CoreSight Technology System Design Guide, - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-10 System Design Guidelines 2.8 Boundary scan test vectors If you use the JTAG boundary scan test methodology to apply production test vectors, you might want to have independent external access to each Test Access Port (TAP) controller. This avoids the requirement to merge test vectors for more than one block in the device. One solution to this is to adopt a hybrid, using a pin on the package that switches elements of the device into a test mode. This can be used to break the internal daisy chaining of TDO and TDI signals, and to multiplex out independent JTAG ports on pins that are used for another purpose during normal operation. 2.8.1 See also Concepts · ICs containing multiple devices on page 2-10. Other information · CoreSight Technology System Design Guide, - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-11 System Design Guidelines 2.9 PCB guidelines PCB guidelines on the physical and electrical connections present on the target board are described in the following topics: · PCB connections on page 2-13 · Target interface logic levels on page 2-14. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-12 System Design Guidelines 2.10 PCB connections The following figure shows a typical JTAG connection scheme: ARM Processor/ ASIC 10K 10K 10K 10K 10K VTREF TDI TMS TCK RTCK TDO TDI TMS TCK 22R RTCK 22R TDO nTRST nSRST Reset circuit TRST RESET DBGRQ DBGACK GND Gnd Gnd 10K DBGRQ DBGACK 10K Signals from JTAG connector 0R VDD Gnd Figure 2-7 Typical PCB connections · · DBGRQ and DBGACK are typically pulled down on the target. · If there is no RTCK signal provided on the processor, it can either be pulled to a fixed logic level or connected to the TCK signal to provide a direct loop-back. · All pull-up and pull-down resistors must be in the range 1K-100K 1K-100K. · The VTREF signal is typically connected directly to the VDD rail. If a series resistor is used to protect against short-circuits, it must have a value no greater than 100. · 2.10.1 Note The signals TDI, TMS, TCK, RTCK and TDO are typically pulled up on the target board to keep them stable when the debug equipment is not connected. To improve signal integrity, it is good practice to provide an impedance matching resistor on the TDO and RTCK outputs of the processor. The value of these resistors, added to the impedance of the driver must be approximately equal to 50. See also Concepts · ASIC guidelines on page 2-9 · Target interface logic levels on page 2-14. Reference · Chapter 3 Target Interface Connections · Chapter 5 Designing the Target Board for Tracing. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-13 System Design Guidelines 2.11 Target interface logic levels DSTREAM is designed to interface with a wide range of target system logic levels. It does this by adapting its output drive and input threshold to a reference voltage supplied by the target system. VTref feeds the reference voltage to the DSTREAM unit. This voltage is clipped internally at approximately 3.4V, and is used as the output high voltage (Voh) for logic 1s (ones) on TCK, TDI, and TMS. 0V is used as the output low voltage for logic 0s (zeroes). The input logic threshold voltage (Vi(th) for the TDO, RTCK, and nSRST inputs is 50% of the Voh level, and so is clipped to approximately 1.7V. The relationships of Voh and Vi(th) to VTref are shown in the following figure: 3.50 3.00 2.50 Voh & Vi(th) (V) 2.00 1.50 1.00 0.50 Voutput high Level - Voh Vinput threshold - Vi (th) 0.00 0 1 2 3 4 5 6 Target VTref (V) Figure 2-8 Target interface logic levels DSTREAM can adapt interface levels down to VTref of 1.2V. By default, the nTRST and nSRST signals are pulled-up by 4.7K resistors within DSTREAM and driven (strong) low during resets. This allows the reset signals to be driven by other open-drain devices or switches on the target board. The polarity and high/low drive strengths can be configured within the software. The input and output characteristics of the DSTREAM unit are compatible with logic levels from TTL-compatible, or CMOS logic in target systems. When assessing compatibility with other logic systems, the output impedance of all signals is approximately 50. 2.11.1 See also Concepts · ASIC guidelines on page 2-9 · PCB connections on page 2-13. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-14 System Design Guidelines Reference · Chapter 3 Target Interface Connections · Chapter 5 Designing the Target Board for Tracing. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 2-15 Chapter 3 Target Interface Connections The following topics provide descriptions of the interface connections on the DSTREAM unit: · Signal descriptions on page 3-2 · JTAG port timing characteristics on page 3-3 · Serial Wire Debug on page 3-5 · SWD connections on page 3-6 · SWD timing requirements on page 3-7 · Trace signals on page 3-8 · Supported target connectors on page 3-10 · Mictor 38 on page 3-11 · ARM JTAG 20 on page 3-15 · TI JTAG 14 on page 3-18 · ARM JTAG 14 on page 3-21 · CoreSight 10 on page 3-24 · CoreSight 20 on page 3-26 · MIPI 34 on page 3-29 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-1 Target Interface Connections 3.1 Signal descriptions Signal descriptions for JTAG, Serial Wire Debug and trace are described in the following topics: · JTAG port timing characteristics on page 3-3 · Serial Wire Debug on page 3-5 · Trace signals on page 3-8. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-2 Target Interface Connections 3.2 JTAG port timing characteristics You must consider the timing characteristics of a DSTREAM unit if you design a target device or board and want to be able to connect DSTREAM at a particular TCK frequency. The characteristics relate to the DSTREAM hardware. You must consider them in parallel with the characteristics of your target. The following figure shows the JTAG port timing and parameters: Tbscl Tbsch TCK Tbsod TMS and TDI Tbsis Tbsih TDO Figure 3-1 JTAG port timing diagram In a JTAG device that fully complies to IEEE1149 IEEE1149.1-2001, TDI and TMS are sampled on the rising edge of TCK, and TDO changes on the falling edge of TCK. To take advantage of these properties, DSTREAM samples TDO on the rising edge of TCK and changes its TDI and TMS signals on the falling edge of TCK. This means that with a fully compliant target, issues with minimum setup and hold times can always be resolved by decreasing the TCK frequency, because this increases the separation between signals changing and being sampled. Note There are no separate timing requirements for adaptive clocking mode, because the minimum Tbsch and Tbscl times are identical and are the same as for non-adaptive clocking. Tbsis and Tbsih are relative to RTCK rising, and not TCK rising, as RTCK is used to sample TDO in adaptive clocking mode. The only real timing difference is that in adaptive mode, DSTREAM samples TDO on the rising edge of RTCK and not TCK, so TDO timing is relative to RTCK. The following table shows the timing requirements for the JTAG signals on the DSTREAM probe: Table 3-1 DSTREAM JTAG A timing requirements Parameter Min Max Description Tbscl 500s TCK LOW period Tbsch 50ns 500s TCK HIGH period Tbsod - 6.0ns Tbsis 15.0ns - TDO setup to TCK (rising) Tbsih ARM DUI 0499A ID052210 ID052210 50ns 6.0ns - TDO hold from TCK (rising) Copyright © 2010 ARM. All rights reserved. Non-Confidential TDI and TMS valid from TCK (falling) 3-3 Target Interface Connections · Note The debug software enables you to change the TCK frequency. The TCK LOW:HIGH mark-space ratio is always 50:50. The other parameters must be considered with the specific values of Tbscl and Tbsch that you have chosen. The default values for an autoconfigured single-TAP system are, nominally, Tbscl=50ns and Tbsch=50ns. · · 3.2.1 Tbsod is the maximum delay between the falling edge of TCK and valid levels on the TDI and TMS DSTREAM output signals. The target samples these signals on the following rising edge of TCK and so the minimum setup time for the target, relative to the rising edge of TCK, is Tbscl­Tbsod. Tbsis is the minimum setup time for the TDO input signal, relative to the rising edge of TCK when DSTREAM samples this signal. The target changes its TDO value on the previous falling edge of TCK and so the maximum time for the target TDO level to become valid, relative to the falling edge of TCK, is Tbscl­Tbsis. See also Concepts · Signal descriptions on page 3-2 · Serial Wire Debug on page 3-5 · Trace signals on page 3-8. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-4 Target Interface Connections 3.3 Serial Wire Debug The Serial Wire Debug (SWD) connection to the Debug Access Port (DAP) is described in the following topics: · SWD connections on page 3-6 · ARM DUI 0499A ID052210 ID052210 SWD timing requirements on page 3-7. Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-5 Target Interface Connections 3.4 SWD connections The following figure shows a typical Serial Wire Debug (SWD) connection scheme: 10K 10K 10K 0R VDD Signals from SWD connector VTREF ARM Processor/ ASIC 22R SWDIO SWCLK 22R SWO SWDIO SWCLK SWO Reset circuit nSRST RESET GND Gnd Figure 3-2 Typical SWD connections · · All pull-up resistors must be in the range 1K-100K 1K-100K. · The VTREF signal is typically connected directly to the VDD rail. If a series resistor is used to protect against short-circuits, it must have a value no greater than 100. · 3.4.1 Note The SWDIO, SWCLK and SWO signals are typically pulled up on the target to keep them stable when the debug equipment is not connected. To improve signal integrity, it is good practice to provide an impedance matching resistor on the SWDIO and SWO outputs of the processor. The value of these resistors, added to the impedance of the driver must be approximately equal to 50. See also Concepts · JTAG port timing characteristics on page 3-3 · Serial Wire Debug on page 3-5 · SWD timing requirements on page 3-7 · Trace signals on page 3-8. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-6 Target Interface Connections 3.5 SWD timing requirements The interface uses only two lines, but for clarity the diagrams shown in the following figure separate the SWDIO line to show when it is driven by either the DSTREAM probe or target: Read cycle DSTREAM Probe output to SWDIO Stop Park Tos Tri-State Data Data Parity Start Thigh Tlo w DSTREAM Probe output to SWDCLK Tri-State Target output to SWDIO Acknowledge Tri-State Write cycle DSTREAM Probe output to SWDIO Stop Park Tri-State Tis Start Tih DSTREAM Probe output to SWDCLK Target output to SWDIO Tri-State Acknowledge Data Data Parity Tri-State Figure 3-3 SWD timing diagrams The probe writes data to SWDIO on the falling edge of SWDCLK. The probe reads data from SWDIO on the rising edge of SWDCLK. The target writes data to SWDIO on the rising edge of SWDCLK. The target reads data from SWDIO on the rising edge of SWDCLK. The following table shows the timing requirements for the Serial Wire Debug (SWD): Table 3-2 SWD timing requirements Parameter Min Max Description Thigh 500s SWDCLK HIGH period Tlow 10ns 500s SWDCLK LOW period Tos -5ns 5ns SWDIO Output skew to falling edge SWDCLK Tis 4ns - Input Setup time required between SWDIO and rising edge SWDCLK Tih 3.5.1 10ns 1ns - Input Hold time required between SWDIO and rising edge SWDCLK See also Concepts · JTAG port timing characteristics on page 3-3 · Serial Wire Debug on page 3-5 · SWD connections on page 3-6 · Trace signals on page 3-8. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-7 Target Interface Connections 3.6 Trace signals Data transfer is synchronized by the TRACECLK signal. See the following: · Clock frequency · Switching thresholds · Hot-plugging. 3.6.1 Clock frequency For capturing trace port signals synchronous to TRACECLK, the DSTREAM trace feature supports up to 600Mbps per trace signal using DDR clocking mode, or up to 480Mbps using SDR clocking mode. The following figure and table describe the timing for TRACECLK: Tperiod Twh Twl Figure 3-4 Clock waveforms Table 3-3 TRACECLK frequencies Parameter Description Tperiod (min) 2.08ns Clock period Twh (min) 1.0ns High pulse width Twl (min) 3.6.2 DSTREAM 1.0ns Low pulse width Switching thresholds The trace probe detects the target signaling reference voltage (VTref) and automatically adjusts its switching thresholds to VTref/2. For example, on a 3.3 volt target system, the switching thresholds are set to 1.65 volts. 3.6.3 Hot-plugging If you power-up the DSTREAM unit when it is plugged into an unpowered target, or if you plug an unpowered DSTREAM unit into a powered target, trace functionality is not damaged. If you connect an unpowered DSTREAM unit to a powered target, there is a maximum leakage current into the DSTREAM unit of ±10A on any of the debug or trace signals. 3.6.4 See also Concepts · Target interface logic levels on page 2-14 · Signal descriptions on page 3-2 · JTAG port timing characteristics on page 3-3 ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-8 Target Interface Connections · Serial Wire Debug on page 3-5. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-9 Target Interface Connections 3.7 Supported target connectors The target connectors supported by DSTREAM are described in the following topics: · Mictor 38 on page 3-11 · ARM JTAG 20 on page 3-15 · TI JTAG 14 on page 3-18 · ARM JTAG 14 on page 3-21 · CoreSight 10 on page 3-24 · CoreSight 20 on page 3-26 · MIPI 34 on page 3-29. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-10 Target Interface Connections 3.8 Mictor 38 The Mictor 38 connector is intended for high-speed trace capture of up to 16 bits of trace data and status/sync signals. It can also be used to connect to the debug signals of the target. Note This connector supports only one voltage domain. If the trace and debug signals of the target system use different logic levels, the target must be designed to use a separate debug connector. If a separate connector is used for the debug signals, the unused debug pins of the Mictor 38 connector can be left open circuit. The central earthing strip on the connector provides signal ground. This strip has five through-hole pins, and to achieve reliable trace operation these pins must be soldered directly to the ground plane of the target board. The following figure shows the Mictor 38 connector pinout: 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 Figure 3-5 Mictor 38 connector pinout Due to the construction of the Mictor cable, the signals on the probe itself are column-reversed (1-37, 37-1, 2-38, 38-2, and so on). Only take this into account if testing signals at the probe. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-11 Target Interface Connections The following table shows the Mictor 38 pinout as used on the target board: Table 3-4 Mictor 38 interface pinout table Pin ETMv2 ETMv1 I/O diagram Voltage domain 1 NC NC NC NA NA 2 NC NC NC NA NA 3 NC NC NC NA NA 4 NC NC NC NA NA 5 GND GND GND H NA 6 TRACECLK TRACECLK TRACECLK A B 7 DBGRQ DBGRQ DBGRQ B B 8 DBGACK DBGACK DBGACK A B 9 nSRST nSRST nSRST E B 10 EXTTRIG EXTTRIG EXTTRIG B B 11 TDO TDO TDO A B 12 VTREF VTREF VTREF F B 13 RTCK RTCK RTCK B B 14 VSUPPLY VSUPPLY VSUPPLY Reserved NA 15 TCK TCK TCK B B 16 TRACEDATA[7] TRACEPKT[7] TRACEPKT[7] A B 17 TMS TMS TMS B B 18 TRACEDATA[6] TRACEPKT[6] TRACEPKT[6] A B 19 TDI TDI TDI B B 20 TRACEDATA[5] TRACEPKT[5] TRACEPKT[5] A B 21 nTRST nTRST nTRST D B 22 TRACEDATA[4] TRACEPKT[4] TRACEPKT[4] A B 23 TRACEDATA[15] TRACEPKT[15] TRACEPKT[15] A B 24 TRACEDATA[3] TRACEPKT[3] TRACEPKT[3] A B 25 TRACEDATA[14] TRACEPKT[14] TRACEPKT[14] A B 26 TRACEDATA[2] TRACEPKT[2] TRACEPKT[2] A B 27 TRACEDATA[13] TRACEPKT[13] TRACEPKT[13] A B 28 TRACEDATA[1] TRACEPKT[1] TRACEPKT[1] A B 29 TRACEDATA[12] TRACEPKT[12] TRACEPKT[12] A B 30 Logic 0 TRACEPKT[0] TRACEPKT[0] A B 31 ARM DUI 0499A ID052210 ID052210 ETMv3/TPIU TRACEDATA[11] TRACEPKT[11] TRACEPKT[11] A B Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-12 Target Interface Connections Table 3-4 Mictor 38 interface pinout table (continued) Pin ETMv3/TPIU ETMv2 ETMv1 I/O diagram Voltage domain 32 Logic 0 PIPESTAT[3] TRACESYNC A B 33 TRACEDATA[10] A B 34 Logic 1 PIPESTAT[2] PIPESTAT[2] A B 35 TRACEDATA[9] TRACEPKT[9] TRACEPKT[9] A B 36 TRACECTL PIPESTAT[1] PIPESTAT[1] A B 37 TRACEDATA[8] TRACEPKT[8] TRACEPKT[8] A B 38 TRACEDATA[0] PIPESTAT[0] PIPESTAT[0] A B TRACEPKT[10] The following table describes the signals on the Mictor 38 interfaces: Table 3-5 Mictor 38 signals Signal Description TRACEPKT, TRACEDATA, PIPESTAT, TRACESYNC, TRACECTL Input These pins provide DSTREAM with ETM/TPIU trace data in the various formats shown above. You are advised to series terminate these signals close to the target processor. TRACECLK Input The Trace Clock pin provides DSTREAM with the clock signal necessary to sample all of the trace data signals above. You are advised to series terminate TRACECLK close to the target processor. TDI Output The Test Data In pin provides serial data to the target during debugging. TDI can be pulled HIGH on the target. TDO Input The Test Data Out pin receives serial data from the target during debugging. You are advised to series terminate TDO close to the target processor. TDO is typically pulled HIGH on the target. TMS Output The Test Mode Select pin is used to set the state of the Test Access Port (TAP) controller on the target. TMS can be pulled HIGH on the target to keep the TAP controller inactive when not in use. TCK Output The Test Clock pin is used to clock data into the TDI and TMS inputs of the target. TCK is typically pulled HIGH on the target. RTCK ARM DUI 0499A ID052210 ID052210 I/O Input The Return Test Clock pin is used to echo the test clock signal back to DSTREAM for use with adaptive mode clocking. If RTCK is generated by the target processor, you are advised to series terminate it. RTCK can be pulled HIGH or LOW on the target when not in use. Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-13 Target Interface Connections Table 3-5 Mictor 38 signals (continued) Signal Description nTRST Output The Test Reset pin can be used to reset the TAP controller of the processor to allow debugging to take place. nTRST is typically pulled HIGH on the target and pulled strong-LOW by DSTREAM to initiate a reset. The polarity and strength of nTRST is configurable. nSRST Input/Output The System Reset pin is used to fully reset the target. This signal can be initiated by DSTREAM or by the target board (which is then detected by DSTREAM). nSRST is typically pulled HIGH on the target and pulled strong-LOW to initiate a reset. The polarity and strength of nSRST is configurable. DBGRQ Output The Debug Request pin can be used to stop the target processor and put it into debug state. DBGRQ is rarely used by current systems and is usually pulled LOW on the target. DBGACK Input The Debug Acknowledge pin can be used to notify DSTREAM that a debug request has been received and the target processor is now in debug state. DBGACK is rarely used by current systems and is usually pulled LOW on the target. VTREF Input The Voltage Target Reference pin supplies DSTREAM with the debug rail voltage of the target to match its I/O logic levels. VTREF can be tied HIGH on the target. If VTREF is pulled HIGH by a resistor, its value must be no greater than 100. VSUPPLY - The Voltage Supply pin is not used by DSTREAM and must be left unconnected. GND 3.8.1 I/O - Ground. See also Concepts · Supported target connectors on page 3-10 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-14 Target Interface Connections 3.9 ARM JTAG 20 The ARM® JTAG 20 connector can be used in either standard JTAG (IEEE 1149.1) mode or Serial Wire Debug (SWD) mode. The following figure shows the ARM JTAG 20 connector pinout: 2 4 6 8 10 12 14 16 18 20 1 3 5 7 9 11 13 15 17 19 Figure 3-6 ARM JTAG 20 connector pinout The following table shows the ARM JTAG 20 pinout as used on the target board: Table 3-6 ARM JTAG 20 interface pinout table Pin I/O diagram Voltage domain 1 VTREF F A 2 NC NA NA 3 nTRST D A 4 GND H NA 5 TDI B A 6 GND H NA 7 TMS/SWDIO B/C A 8 GND H NA 9 TCK/SWCLK B A 10 GND H NA 11 RTCK A A 12 GND H NA 13 TDO/SWO A A 14 GND H NA 15 nSRST E A 16 GND H NA 17 ARM DUI 0499A ID052210 ID052210 Signal name DBGRQ B A Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-15 Target Interface Connections Table 3-6 ARM JTAG 20 interface pinout table (continued) Pin Signal name I/O diagram Voltage domain 18 GND H NA 19 DBGACK A A 20 GND H NA The following table describes the signals on the ARM JTAG 20 interfaces: Table 3-7 ARM JTAG 20 signals Signal Description TDI Output The Test Data In pin provides serial data to the target during debugging. TDI can be pulled HIGH on the target. TDO Input The Test Data Out pin receives serial data from the target during debugging. You are advised to series terminate TDO close to the target processor. TDO is typically pulled HIGH on the target. TMS Output The Test Mode Select pin is used to set the state of the Test Access Port (TAP) controller on the target. TMS can be pulled HIGH on the target to keep the TAP controller inactive when not in use. TCK Output The Test Clock pin is used to clock data into the TDI and TMS inputs of the target. TCK is typically pulled HIGH on the target. RTCK Input The Return Test Clock pin is used to echo the test clock signal back to DSTREAM for use with adaptive mode clocking. If RTCK is generated by the target processor, you are advised to series terminate it. RTCK can be pulled HIGH or LOW on the target when not in use. nTRST Output The Test Reset pin can be used to reset the TAP controller of the processor to allow debugging to take place. nTRST is typically pulled HIGH on the target and pulled strong-LOW by DSTREAM to initiate a reset. The polarity and strength of nTRST is configurable. nSRST Input/Output The System Reset pin is used to fully reset the target. This signal can be initiated by DSTREAM or by the target board (which is then detected by DSTREAM). nSRST is typically pulled HIGH on the target and pulled strong-LOW to initiate a reset. The polarity and strength of nSRST is configurable. DBGRQ Output The Debug Request pin can be used to stop the target processor and put it into debug state. DBGRQ is rarely used by current systems and is usually pulled LOW on the target. DBGACK ARM DUI 0499A ID052210 ID052210 I/O Input The Debug Acknowledge pin can be used to notify DSTREAM that a debug request has been received and the target processor is now in debug state. DBGACK is rarely used by current systems and is usually pulled LOW on the target. Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-16 Target Interface Connections Table 3-7 ARM JTAG 20 signals (continued) Signal Description SWDIO (SWD mode) Input/Output The Serial Wire Data I/O pin sends and receives serial data to and from the target during debugging. You are advised to series terminate SWDIO close to the target processor. SWCLK (SWD mode) Output The Serial Wire Clock pin clocks data into and out of the target during debugging. SWO (SWD mode) Input The Serial Wire Output pin can be used to provide trace data to DSTREAM. You are advised to series terminate SWO close to the target processor. VTREF Input The Voltage Target Reference pin supplies DSTREAM with the debug rail voltage of the target to match its I/O logic levels. VTREF can be tied HIGH on the target. If VTREF is pulled HIGH by a resistor, its value must be no greater than 100. GND 3.9.1 I/O - Ground. See also Concepts · Supported target connectors on page 3-10 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-17 Target Interface Connections 3.10 TI JTAG 14 The TI JTAG 14 connector can be used in either standard JTAG (IEEE 1149.1) mode or Serial Wire Debug (SWD) mode. The following figure shows the TI JTAG 14 connector pinout: 1 3 5 7 9 11 13 2 4 6 8 10 12 14 Figure 3-7 TI JTAG 14 connector pinout The following table shows the TI JTAG 14 pinout as used on the target board: Table 3-8 TI JTAG 14 interface pinout table Pin I/O diagram Voltage domain 1 TMS/SWDIO B A 2 nTRST D A 3 TDI B A 4 GND H NA 5 VTREF F A 6 NC I NA 7 TDO/SWO A A 8 GND H NA 9 RTCK A A 10 GND H NA 11 TCK/SWCLK B A 12 GND H NA 13 EMU0 B A 14 ARM DUI 0499A ID052210 ID052210 Signal name EMU1 A A Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-18 Target Interface Connections The following table describes the signals on the TI JTAG 14 interfaces: Table 3-9 TI JTAG 14 signals Signal Description TDI Output The Test Data In pin provides serial data to the target during debugging. TDI can be pulled HIGH on the target. TDO Input The Test Data Out pin receives serial data from the target during debugging. You are advised to series terminate TDO close to the target processor. TDO is typically pulled HIGH on the target. TMS Output The Test Mode Select pin is used to set the state of the Test Access Port (TAP) controller on the target. TMS can be pulled HIGH on the target to keep the TAP controller inactive when not in use. TCK Output The Test Clock pin is used to clock data into the TDI and TMS inputs of the target. TCK is typically pulled HIGH on the target. RTCK Input The Return Test Clock pin is used to echo the test clock signal back to DSTREAM for use with adaptive mode clocking. If RTCK is generated by the target processor, you are advised to series terminate it. RTCK can be pulled HIGH or LOW on the target when not in use. nTRST Output The Test Reset pin can be used to reset the TAP controller of the processor to allow debugging to take place. nTRST is typically pulled HIGH on the target and pulled strong-LOW by DSTREAM to initiate a reset. The polarity and strength of nTRST is configurable. EMU0 - The EMU0 pin is a general I/O pin but is not currently supported by DSTREAM. EMU0 can be pulled high, low or be left open-circuit on the target. EMU1 - The EMU1 pin is a general I/O pin but is not currently supported by DSTREAM. EMU0 can be pulled high, low or be left open-circuit on the target. SWDIO (SWD mode) Input/Output The Serial Wire Data I/O pin sends and receives serial data to and from the target during debugging. You are advised to series terminate SWDIO close to the target processor. SWCLK (SWD mode) Output The Serial Wire Clock pin clocks data into and out of the target during debugging. SWO (SWD mode) Input The Serial Wire Output pin can be used to provide trace data to DSTREAM. You are advised to series terminate SWO close to the target processor. VTREF Input The Voltage Target Reference pin supplies DSTREAM with the debug rail voltage of the target to match its I/O logic levels. VTREF can be tied HIGH on the target. If VTREF is pulled HIGH by a resistor, its value must be no greater than 100. GND ARM DUI 0499A ID052210 ID052210 I/O - Ground. Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-19 Target Interface Connections 3.10.1 See also Concepts · Supported target connectors on page 3-10 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-20 Target Interface Connections 3.11 ARM JTAG 14 The ARM® JTAG 14 connector can be used in either standard JTAG (IEEE 1149.1) mode or Serial Wire Debug (SWD) mode. The following figure shows the TI JTAG 14 connector pinout: 1 3 5 7 9 11 13 2 4 6 8 10 12 14 Figure 3-8 ARM JTAG 14 connector pinout The following table shows the ARM JTAG 14 pinout as used on the target board: Table 3-10 ARM JTAG 14 interface pinout table Pin I/O diagram Voltage domain 1 NC NA NA 2 GND H NA 3 nTRST D A 4 GND H NA 5 TDI B A 6 GND H NA 7 TMS/SWDIO B A 8 GND H NA 9 TCK/SWCLK B A 10 GND H NA 11 TDO/SWO A A 12 nSRST E A 13 VTREF F A 14 ARM DUI 0499A ID052210 ID052210 Signal name GND H NA Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-21 Target Interface Connections The following table describes the signals on the ARM JTAG 14 interfaces: Table 3-11 ARM JTAG 14 signals Signal Description TDI Output The Test Data In pin provides serial data to the target during debugging. TDI can be pulled HIGH on the target. TDO Input The Test Data Out pin receives serial data from the target during debugging. You are advised to series terminate TDO close to the target processor. TDO is typically pulled HIGH on the target. TMS Output The Test Mode Select pin is used to set the state of the Test Access Port (TAP) controller on the target. TMS can be pulled HIGH on the target to keep the TAP controller inactive when not in use. TCK Output The Test Clock pin is used to clock data into the TDI and TMS inputs of the target. TCK is typically pulled HIGH on the target. nTRST Output The Test Reset pin can be used to reset the TAP controller of the processor to allow debugging to take place. nTRST is typically pulled HIGH on the target and pulled strong-LOW by DSTREAM to initiate a reset. The polarity and strength of nTRST is configurable. nSRST Input/Output The System Reset pin is used to fully reset the target. This signal can be initiated by DSTREAM or by the target board (which is then detected by DSTREAM). nSRST is typically pulled HIGH on the target and pulled strong-LOW to initiate a reset. The polarity and strength of nSRST is configurable. SWDIO (SWD mode) Input/Output The Serial Wire Data I/O pin sends and receives serial data to and from the target during debugging. You are advised to series terminate SWDIO close to the target processor. SWCLK (SWD mode) Output The Serial Wire Clock pin clocks data into and out of the target during debugging. SWO (SWD mode) Input The Serial Wire Output pin can be used to provide trace data to DSTREAM. You are advised to series terminate SWO close to the target processor. VTREF Input The Voltage Target Reference pin supplies DSTREAM with the debug rail voltage of the target to match its I/O logic levels. VTREF can be tied HIGH on the target. If VTREF is pulled HIGH by a resistor, its value must be no greater than 100. GND 3.11.1 I/O - Ground. See also Concepts · Supported target connectors on page 3-10 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-22 Target Interface Connections Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-23 Target Interface Connections 3.12 CoreSight 10 The CORESIGHT 10 connector can be used in either standard JTAG (IEEE 1149.1) mode or Serial Wire Debug (SWD) mode. The following figure shows the CoreSight 10 connector pinout: 1 3 5 7 9 2 4 6 8 10 Figure 3-9 CoreSight 10 connector pinout Note A polarizing key is fitted only at the target end of the cable. The following table shows the CoreSight 10 pinout as used on the target board: Table 3-12 CoreSight 10 interface pinout table Pin I/O diagram Voltage domain 1 VTREF G A 2 TMS/SWDIO B/C A 3 GND H NA 4 TCK/SWCLK B A 5 GND H NA 6 TDO/SWO A A 7 KEY (NC) NA NA 8 TDI B A 9 GND H NA 10 ARM DUI 0499A ID052210 ID052210 Signal name nSRST E A Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-24 Target Interface Connections The following table describes the signals on the CoreSight 10 interfaces: Table 3-13 CoreSight 10 signals Signal Description TDI Output The Test Data In pin provides serial data to the target during debugging. TDI can be pulled HIGH on the target. TDO Input The Test Data Out pin receives serial data from the target during debugging. You are advised to series terminate TDO close to the target processor. TDO is typically pulled HIGH on the target. TMS Output The Test Mode Select pin is used to set the state of the Test Access Port (TAP) controller on the target. TMS can be pulled HIGH on the target to keep the TAP controller inactive when not in use. TCK Output The Test Clock pin is used to clock data into the TDI and TMS inputs of the target. TCK is typically pulled HIGH on the target. nSRST Input/Output The System Reset pin is used to fully reset the target. This signal can be initiated by DSTREAM or by the target board (which is then detected by DSTREAM). nSRST is typically pulled HIGH on the target and pulled strong-LOW to initiate a reset. The polarity and strength of nSRST is configurable. SWDIO (SWD mode) Input/Output The Serial Wire Data I/O pin sends and receives serial data to and from the target during debugging. You are advised to series terminate SWDIO close to the target processor. SWCLK (SWD mode) Output The Serial Wire Clock pin clocks data into and out of the target during debugging. SWO (SWD mode) Input The Serial Wire Output pin can be used to provide trace data to DSTREAM. You are advised to series terminate SWO close to the target processor. VTREF Input The Voltage Target Reference pin supplies DSTREAM with the debug rail voltage of the target to match its I/O logic levels. VTREF can be tied HIGH on the target. If VTREF is pulled HIGH by a resistor, its value must be no greater than 100. GND - Ground. KEY 3.12.1 I/O - This pin must not be present on the target connector. See also Concepts · Supported target connectors on page 3-10 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-25 Target Interface Connections 3.13 CoreSight 20 The CORESIGHT 20 connector can be used in either standard JTAG (IEEE 1149.1) mode or Serial Wire Debug (SWD) mode. It can also optionally capture up to 4 bits of parallel trace in Trace Port Interface Unit (TPIU) continuous mode. When this connector is configured to be a parallel trace source, pins 12 to 20 switch to their alternate trace functions. The following figure shows the CoreSight 20 connector pinout: 1 3 5 7 9 11 13 15 17 19 2 4 6 8 10 12 14 16 18 20 Figure 3-10 CoreSight 20 connector pinout Note A polarizing key is fitted only at the target end of the cable. The following table shows the CoreSight 20 pinout as used on the target board: Table 3-14 CoreSight 20 interface pinout table Pin I/O diagram Voltage domain 1 VTREF G A 2 TMS/SWDIO B/C A 3 GND H NA 4 TCK/SWCLK B A 5 GND H NA 6 TDO/SWO A A 7 KEY (NC) NA NA 8 TDI B A 9 GND H NA 10 nSRST E A 11 NC I NA 12 RTCK/TRACECLK A A 13 ARM DUI 0499A ID052210 ID052210 Signal name NC I NA Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-26 Target Interface Connections Table 3-14 CoreSight 20 interface pinout table (continued) Pin Signal name I/O diagram Voltage domain 14 SWO/TraceD0 E A 15 GND H NA 16 nTRST/TraceD1 E A 17 GND H NA 18 DBGRQ/TraceD2 A A 19 GND H NA 20 DBGACK /TraceD3 A A The following table describes the signals on the CoreSight 20 interfaces: Table 3-15 CoreSight 20 signals Signal Description TDI Output The Test Data In pin provides serial data to the target during debugging. TDI can be pulled HIGH on the target. TDO Input The Test Data Out pin receives serial data from the target during debugging. You are advised to series terminate TDO close to the target processor. TDO is typically pulled HIGH on the target. TMS Output The Test Mode Select pin is used to set the state of the Test Access Port (TAP) controller on the target. TMS can be pulled HIGH on the target to keep the TAP controller inactive when not in use. TCK Output The Test Clock pin is used to clock data into the TDI and TMS inputs of the target. TCK is typically pulled HIGH on the target. RTCK Input The Return Test Clock pin is used to echo the test clock signal back to DSTREAM for use with adaptive mode clocking. If RTCK is generated by the target processor, you are advised to series terminate it. RTCK can be pulled HIGH or LOW on the target when not in use. nTRST Output The Test Reset pin can be used to reset the TAP controller of the processor to allow debugging to take place. nTRST is typically pulled HIGH on the target and pulled strong-LOW by DSTREAM to initiate a reset. The polarity and strength of nTRST is configurable. nSRST Input/Output The System Reset pin is used to fully reset the target. This signal can be initiated by DSTREAM or by the target board (which is then detected by DSTREAM). nSRST is typically pulled HIGH on the target and pulled strong-LOW to initiate a reset. The polarity and strength of nSRST is configurable. DBGRQ ARM DUI 0499A ID052210 ID052210 I/O Output The Debug Request pin can be used to stop the target processor and put it into debug state. DBGRQ is rarely used by current systems and is usually pulled LOW on the target. Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-27 Target Interface Connections Table 3-15 CoreSight 20 signals (continued) Signal Description DBGACK Input The Debug Acknowledge pin can be used to notify DSTREAM that a debug request has been received and the target processor is now in debug state. DBGACK is rarely used by current systems and is usually pulled LOW on the target. SWDIO (SWD mode) Input/Output The Serial Wire Data I/O pin sends and receives serial data to and from the target during debugging. You are advised to series terminate SWDIO close to the target processor. SWCLK (SWD mode) Output The Serial Wire Clock pin clocks data into and out of the target during debugging. SWO (SWD mode) Input The Serial Wire Output pin can be used to provide trace data to DSTREAM. You are advised to series terminate SWO close to the target processor. SWO is configurable to be captured on pin 6 or 14. TraceD[0-3] Input The Trace Data [0-3] pins provide DSTREAM with TPIU continuous mode trace data from the target. You are advised to series terminate these signals close to the target processor. TRACECLK (Trace mode) Input The Trace Clock pin provides DSTREAM with the clock signal necessary to sample the trace data signals. You are advised to series terminate TRACECLK close to the target processor. VTREF Input The Voltage Target Reference pin supplies DSTREAM with the debug rail voltage of the target to match its I/O logic levels. VTREF can be tied HIGH on the target. If VTREF is pulled HIGH by a resistor, its value must be no greater than 100. GND - Ground. KEY 3.13.1 I/O - This pin must not be present on the target connector. See also Concepts · Supported target connectors on page 3-10 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-28 Target Interface Connections 3.14 MIPI 34 The MIPI 34 connector can be used in either standard JTAG (IEEE 1149.1) mode or Serial Wire Debug (SWD) mode. It can also capture up to 4-bits of parallel trace in Trace Port Interface Unit (TPIU) continuous mode. This connector supports separate voltage domains for the debug and trace signals. It is therefore necessary to supply the appropriate voltages to both of the VTREF pins. The following figure shows the MIPI 34 connector pinout: 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 Figure 3-11 MIPI 34 connector pinout Note A polarizing key is fitted only at the target end of the cable. The following table shows the MIPI 34 pinout as used on the target board: Table 3-16 MIPI 34 interface pinout table Pin I/O diagram Voltage domain 1 VTREF G A 2 TMS/SWDIO B A 3 GND H NA 4 TCK/SWCLK B A 5 GND H NA 6 TDO/SWO A A 7 KEY (NC) NA NA 8 TDI B A 9 ARM DUI 0499A ID052210 ID052210 Signal name GND H NA Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-29 Target Interface Connections Table 3-16 MIPI 34 interface pinout table (continued) Pin I/O diagram Voltage domain 10 nSRST E A 11 NC I NA 12 RTCK A A 13 NC I NA 14 TRST_PD D A 15 GND H NA 16 nTRST D A 17 GND H NA 18 DBGRQ B A 19 GND H NA 20 DBGACK A A 21 GND H NA 22 TRACECLK A B 23 GND H NA 24 TRACED0 A B 25 GND H NA 26 TRACED1 A B 27 GND H NA 28 TRACED2 A B 29 GND H NA 30 TRACED3 A B 31 GND H NA 32 TRACEEXT C B 33 GND H NA 34 ARM DUI 0499A ID052210 ID052210 Signal name VTREF F B Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-30 Target Interface Connections The following table describes the signals on the MIPI 34 interfaces: Table 3-17 MIPI 34 signals Signal Description TDI Output The Test Data In pin provides serial data to the target during debugging. TDI can be pulled HIGH on the target. TDO Input The Test Data Out pin receives serial data from the target during debugging. You are advised to series terminate TDO close to the target processor. TDO is typically pulled HIGH on the target. TMS Output The Test Mode Select pin is used to set the state of the Test Access Port (TAP) controller on the target. TMS can be pulled HIGH on the target to keep the TAP controller inactive when not in use. TCK Output The Test Clock pin is used to clock data into the TDI and TMS inputs of the target. TCK is typically pulled HIGH on the target. RTCK Input The Return Test Clock pin is used to echo the test clock signal back to DSTREAM for use with adaptive mode clocking. If RTCK is generated by the target processor, you are advised to series terminate it. RTCK can be pulled HIGH or LOW on the target when not in use. nTRST Output The Test Reset pin can be used to reset the TAP controller of the processor to allow debugging to take place. nTRST is typically pulled HIGH on the target and pulled strong-LOW by DSTREAM to initiate a reset. The polarity and strength of nTRST is configurable. TRST_PD Output The Test Reset (Pull-Down) pin can be used to reset the TAP controller of the processor to allow debugging to take place. TRST_PD is typically pulled LOW on the target (reset state) and pulled strong-HIGH by DSTREAM to enable debugging. The polarity and strength of TRST_PD is configurable. nSRST Input/Output The System Reset pin is used to fully reset the target. This signal can be initiated by DSTREAM or by the target board (which is then detected by DSTREAM). nSRST is typically pulled HIGH on the target and pulled strong-LOW to initiate a reset. The polarity and strength of nSRST is configurable. DBGRQ Output The Debug Request pin can be used to stop the target processor and put it into debug state. DBGRQ is rarely used by current systems and is usually pulled LOW on the target. DBGACK Input The Debug Acknowledge pin can be used to notify DSTREAM that a debug request has been received and the target processor is now in debug state. DBGACK is rarely used by current systems and is usually pulled LOW on the target. SWDIO (SWD mode) Input/Output The Serial Wire Data I/O pin sends and receives serial data to and from the target during debugging. You are advised to series terminate SWDIO close to the target processor. SWCLK (SWD mode) ARM DUI 0499A ID052210 ID052210 I/O Output The Serial Wire Clock pin clocks data into and out of the target during debugging. Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-31 Target Interface Connections Table 3-17 MIPI 34 signals (continued) Signal Description SWO (SWD mode) Input The Serial Wire Output pin can be used to provide trace data to DSTREAM. You are advised to series terminate SWO close to the target processor. TraceD[0-3] Input The Trace Data [0-3] pins provide DSTREAM with Trace Port Interface Unit (TPIU) continuous mode trace data from the target. You are advised to series terminate these signals close to the target processor. TRACECLK Input The Trace Clock pin provides DSTREAM with the clock signal necessary to sample the trace data signals. You are advised to series terminate TRACECLK close to the target processor. TRACEEXT Input The Trace Extension pin is a generic trace sideband pin. TRACEEXT is not currently supported by DSTREAM. TRACEEXT can be pulled high, low, or left unconnected on the target. VTREF Input The Voltage Target Reference pin supplies DSTREAM with the debug rail voltage of the target to match its I/O logic levels. VTREF can be tied HIGH on the target. If VTREF is pulled HIGH by a resistor, its value must be no greater than 100. GND - Ground. KEY 3.14.1 I/O - This pin must not be present on the target connector. See also Concepts · Supported target connectors on page 3-10 · I/O diagrams on page 3-33 · Voltage domains on page 3-36 · Series termination on page 3-37. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-32 Target Interface Connections 3.15 I/O diagrams The pin I/O circuit diagrams for the debug and trace connectors on the DSTREAM probe are: · Diagram A - Input · Diagram B - Output · Diagram C - Input/Output · Diagram D - Reset output · Diagram E - Reset output with feedback on page 3-34 · Diagram F - VTRef input on page 3-34 · Diagram G - VTRef input (decoupled) on page 3-34 · Diagram H - Ground on page 3-34 · Diagram I - AC Ground on page 3-35. 3.15.1 Diagram A - Input The input circuit diagram is shown in the following figure: 33R - - V REF/2 Figure 3-12 Input 3.15.2 Diagram B - Output The output circuit diagram is shown in the following figure: 33R Figure 3-13 Output 3.15.3 Diagram C - Input/Output The input/output circuit diagram is shown in the following figure: 33R - - V REF/2 - Figure 3-14 Input/Output 3.15.4 Diagram D - Reset output The reset output circuit diagram is shown in the following figure: 33R Strong driver 4K7 Weak driver Figure 3-15 Reset output ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-33 Target Interface Connections 3.15.5 Diagram E - Reset output with feedback The reset output with feedback circuit diagram is shown in the following figure: 33R Strong driver 4K7 Weak driver - - V REF/2 - Figure 3-16 Reset output with feedback 3.15.6 Diagram F - VTRef input The VTRef input circuit diagram is shown in the following figure: ~0.6V Target detect - - 33R - - Buffered VTREF 10K Figure 3-17 VTRef input 3.15.7 Diagram G - VTRef input (decoupled) The VTRef input (decoupled) circuit diagram is shown in the following figure: ~0.6V Target detect - - 33R - - 100nF Buffered VTREF 10K Figure 3-18 VTRef input (decoupled) 3.15.8 Diagram H - Ground The Ground circuit diagram is shown in the following figure: 100nF 33R Figure 3-19 Ground ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-34 Target Interface Connections 3.15.9 Diagram I - AC Ground The AC Ground circuit diagram is shown in the following figure: 100nF Figure 3-20 AC Ground 3.15.10 See also Concepts · Supported target connectors on page 3-10 · Voltage domains on page 3-36 · Series termination on page 3-37. Other information · ETMv1 and ETMv3 architecture pinouts , - ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-35 Target Interface Connections 3.16 Voltage domains The DSTREAM probe supports two separate voltage domains to work with debug and trace interfaces on differing voltage rails. Voltage domain A is used by the following connectors: · ARM JTAG 20 · TI JTAG 14 · ARM JTAG 14 · CoreSight 10 · CoreSight 20 · MIPI 34. Voltage domain B is used by the following connectors: · Mictor 38 · MIPI 34. The MIPI 34 connector is the only one which supports both voltage domains, and is equipped with two VTREF pins to achieve the correct logic levels. The VTREF A and VTREF B LEDs on the probe indicate when targets have been detected in the respective voltage domains. 3.16.1 See also Concepts · Supported target connectors on page 3-10 · Series termination on page 3-37. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-36 Target Interface Connections 3.17 Series termination Series (or source) termination is a technique employed in point-to-point signaling to ensure that no excessive overshoot or ringing occurs. This is achieved by reducing the source voltage by approximately 50% close to the driver. When the signal reaches the end of the transmission line, the high impedance of the receiver causes a reflection which approximately doubles the signal back to its original amplitude. When the reflection returns to the series terminating resistor, the potential across the resistor drops to zero which prevents any more current from entering the transmission line. From the perspective of the receiver, this gives a perfect 100% logic transition without any overshoot or ringing. It is recommended that all outputs from the target system be simulated to ensure that a reliable signal is delivered to the DSTREAM probe. Some overshoot/undershoot is acceptable but it is recommended to keep this below ~0.5V. Beyond this point, the clamping diodes at the receivers will start to cause high transient currents which in turn cause increased crosstalk, radio emissions and target power usage. The target signal impedance for use with DSTREAM is 50. The following table lists some typical series terminating resistor values for instances when the outputs cannot be simulated. Table 3-18 Typical series terminating resistor values Driver strength Typical series terminator 32mA 39 24mA 33 16mA 27 12mA 22 8mA 15 6mA 10 Best signal integrity, highest speed Worst signal integrity, lowest speed Some types of IC use "impedance matched" outputs to improve their signal integrity. This is usually achieved by using weaker drive transistors to slow down the edge transitions. This has the side effect of limiting the data throughput of the driver. To achieve the highest data rates with the best signal integrity, it is recommended to use a strong and fast driver and appropriate series terminating resistor. If it is determined that series terminating resistors are not required, it is recommended that 0 links be placed close to the driver as a fall-back option. When series terminating multiple signals, it is common to use small quad resistor packages. This saves board space and reduces parasitic effects without much risk of placement or tombstoning issues during production. 3.17.1 See also Concepts · Supported target connectors on page 3-10 · Voltage domains on page 3-36. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 3-37 Chapter 4 User I/O Connections The following topic describes the additional input and output connections provided in DSTREAM, and consists of: · The DSTREAM User I/O connector on page 4-2. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 4-1 User I/O Connections 4.1 The DSTREAM User I/O connector The User Input/Output (I/O) connector is situated on an end panel of the DSTREAM unit. The connector is a 10-way 2.54mm pitch Insulation Displacement Connector (IDC) header that mates with IDC sockets mounted on a ribbon cable, as shown in the following figure. Output 1 1 2 Output 2 Output 3 3 4 Output 4 Output 5 5 6 Input 1 Output 6 7 8 Input 2 +3.3V 9 10 GND Figure 4-1 User I/O pin connections Warning You must establish a common ground between the DSTREAM unit and the target hardware before you connect any of the User I/O signals. The following table shows the User I/O pin connections. Table 4-1 User I/O pin connections Pin I/O Description Pin 1 Output 1 Output This is a user output bit. It operates at a 3.3V swing, with a 100 series resistance. Pin 2 Output 2 Output This is a user output bit. It operates at a 3.3V swing, with a 100 series resistance. Pin 3 Output 3 Output This is a user output bit. It operates at a 3.3V swing, with a 100 series resistance. Pin 4 Output 4 Output This is a user output bit. It operates at a 3.3V swing, with a 100 series resistance. Pin 5 Output 5 Output This is a user output bit. It operates at a 3.3V swing, with a 100 series resistance. Pin 6 Input 1 Input This is a user input bit. It has a 100K weak pull-up to the unit internal +3.3V supply, and requires a Vih(min) of 2.0V and a Vil(max) of 0.8V. It can safely be driven by 5V logic levels, and has Electro Static Discharge (ESD) protection greater than the 2kV human body model. This pin is not currently supported. Pin 7 ARM DUI 0499A ID052210 ID052210 Signal Output 6 Output This is a user output bit. It operates at a 3.3V swing, with a 100 series resistance. Copyright © 2010 ARM. All rights reserved. Non-Confidential 4-2 User I/O Connections Table 4-1 User I/O pin connections (continued) Pin Signal I/O Description Pin 8 Input 2 Input This is a copy of the trigger input on the end panel of the DSTREAM unit. It has a 10k weak pull-up to the unit internal +3.3V supply, and requires a Vih(min) of 2.0V and a Vil(max) of 0.8V. It can safely be driven by 5V logic levels, and has ESD protection greater than the 2kV human body model. This pin is not currently supported. Pin 9 +3.3V Output This is intended as a voltage reference for external circuitry and is current limited to approximately 50mA. Pin 10 GND - - Note Input is not currently supported on the User I/O pin connections. 4.1.1 See also Reference Setting up the Hardware: · The DSTREAM unit on page 2-6. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 4-3 Chapter 5 Designing the Target Board for Tracing The following topics provide information on the properties of a target board that can be connected to the DSTREAM trace feature: · Overview of high-speed design on page 5-2 · PCB track impedance on page 5-3 · Signal requirements on page 5-4 · Probe modeling on page 5-6. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 5-1 Designing the Target Board for Tracing 5.1 Overview of high-speed design Failure to observe high-speed design rules when designing a target system containing an ARM® Embedded Trace Macrocell (ETM) trace port can result in incorrect trace data being captured. You must give serious consideration to high-speed signals when designing the target system. The signals coming from an ETM trace port can have very fast rise and fall times, even at relatively low frequencies. For example, a signal with a rise time of 1ns has an effective knee frequency of 500MHz and a signal with a rise time of 500ps has an effective knee frequency of 1GHz (fknee = 0.5/Tr). Note These principles apply to all of the trace port signals, but special care must taken with TRACECLK. You must make the following considerations for high-speed design: Avoid stubs Stubs are short pieces of track that tee off from the main track carrying the signal to, for example, a test point or a connection to an intermediate device. Stubs cause impedance discontinuities that affect signal quality and must be avoided. Special care must therefore be taken when ETM signals are multiplexed with other pin functions and where the PCB is designed to support both functions with differing tracking requirements. Minimize signal skew (balancing PCB track lengths) You must attempt to match the lengths of the PCB tracks carrying the trace port signals from the ASIC to the Mictor connector to within approximately 0.5 inches (12.5mm) of each other. Any greater differences directly impact the setup and hold time requirements. Minimize crosstalk Normal high-speed design rules must be observed. For example, do not run dynamic signals parallel to each other for any significant distance, keep them spaced well apart, and use a ground plane and so forth. Particular attention must be paid to the TRACECLK signal. If in any doubt, place grounds or static signals between the TRACECLK and any other dynamic signals. Use impedance matching and termination All PCB tracks carrying trace port signals must be impedance matched to approximately 50. Series termination is highly recommended on all high-speed signals. 5.1.1 See also Concepts · Series termination on page 3-37 · PCB track impedance on page 5-3 · Signal requirements on page 5-4 · Probe modeling on page 5-6. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 5-2 Designing the Target Board for Tracing 5.2 PCB track impedance Use the following formula only for microstrips (track on outer layer over a ground plane): 87 Impedance In = (E r + 1.41 ) 5.98h (0.81w + t) where: h w t Er Height above ground plane (inches) Trace width (inches), and 0.1 < w/h < 2 Trace thickness (inches) Relative permittivity of processor/prepreg, and 1 < Er < 15 The dimensions h, w, and t are shown in the following figure. w t h Ground plane Figure 5-1 Track impedance As an example, the following track (in microstrip form) has an impedance of 51.96: h 0.005 inch height above ground w 0.007 inch width track t 0.0014 inch thickness (1 oz. finished weight) Er 4.5 (FR4 laminate) Note As the track width increases, the impedance decreases. 5.2.1 See also Concepts · Series termination on page 3-37 · Overview of high-speed design on page 5-2 · Signal requirements on page 5-4 · Probe modeling on page 5-6. ARM DUI 0499A ID052210 ID052210 Copyright © 2010 ARM. All rights reserved. Non-Confidential 5-3 Designing the Target Board for Tracing 5.3 Signal requirements The data setup and hold requirements are described in the following: · Data setup and hold · Switching Thresholds. 5.3.1 Data setup and hold The following figure and table show the setup and hold timing of the trace signals with respect to TRACECLK. TRACECLK High Low DATA Tsh Thh Tsl Thl DDR TRACECLK Figure 5-2 Data waveforms Table 5-1 Data setup and hold Parameter DSTREAM Description Tsh (min) 0.75ns Data setup high Thh (min) 0.75ns Data hold high Tsl (min) 0.75ns Data setup low Thl (min) 0.75ns Data hold low Note DSTREAM supports DDR clocking mode. Data is output on each edge of the TRACECLK signal and TRACECLK (max)