Recommended JTAG Circuitry for Debug with Intel Xscale Microarchitecture

Similar documents
Intel I/O Processor Chipset with Intel XScale Microarchitecture

Intel 810 Embedded Client Reference Design DC/DC ATX Power Supply

ECC Handling Issues on Intel XScale I/O Processors

Intel IXP42X Product Line of Network Processors and IXC1100 Control Plane Processor PCI 16-Bit Read Implementation

Intel IXP42X Product Line of Network Processors and IXC1100 Control Plane Processor: Boot-Up Options

Intel PCI-X to Serial ATA Controller

Intel IXP400 Software: Integrating STMicroelectronics* ADSL MTK20170* Chipset Firmware

Running RAM RedBoot to Move Flash from Outbound Direct Addressing Window

Third Party Hardware TDM Bus Administration

Using the Intel IQ80310 Ethernet Connection Under RedBoot

Intel I/O Processor

Intel 6300ESB I/O Controller Hub (ICH)

Enabling DDR2 16-Bit Mode on Intel IXP43X Product Line of Network Processors

Intel C++ Compiler Documentation

Techniques for Lowering Power Consumption in Design Utilizing the Intel EP80579 Integrated Processor Product Line

Intel I/O Processor Software Conversion to Intel I/O Processor

RAID on Motherboard (ROMB) Considerations Using Intel I/O Processor

Intel NetStructure IPT Series on Windows

Continuous Speech Processing API for Linux and Windows Operating Systems

Intel Parallel Amplifier Sample Code Guide

Intel IXP42X Product Line of Network Processors and IXC1100 Control Plane Processor: Flash Programming

Embedded Intel486 SX Processor

How to Configure Intel X520 Ethernet Server Adapter Based Virtual Functions on SuSE*Enterprise Linux Server* using Xen*

Open FCoE for ESX*-based Intel Ethernet Server X520 Family Adapters

Getting Compiler Advice from the Optimization Reports

Intel IT Director 1.7 Release Notes

Intel Dialogic Global Call Protocols Version 4.1 for Linux and Windows

Intel IXP42X Product Line and IXC1100 Control Plane Processor: Using the Intel LXT973 Ethernet Transceiver

Product Change Notification

Intel 945(GM/GME)/915(GM/GME)/ 855(GM/GME)/852(GM/GME) Chipsets VGA Port Always Enabled Hardware Workaround

Introduction to Intel Fortran Compiler Documentation. Document Number: US

Product Change Notification

Product Change Notification

Product Change Notification

Product Change Notification

Intel Desktop Board DZ68DB

Continuous Speech Processing API for Host Media Processing

Intel Platform Controller Hub EG20T

Product Change Notification

Product Change Notification

Intel MPI Library for Windows* OS

Intel(R) Threading Building Blocks

Product Change Notification

Intel Platform Controller Hub EG20T

Using Intel Inspector XE 2011 with Fortran Applications

Product Change Notification

Product Change Notification

Product Change Notification

Intel Platform Controller Hub EG20T

Embedded Intel 855GME GMCH to Intel 852GM GMCH Design Respin

Product Change Notification

Intel 848P Chipset. Specification Update. Intel 82848P Memory Controller Hub (MCH) August 2003

Product Change Notification

Intel NetStructure SS7 Boards

Product Change Notification

Intel Desktop Board DG41CN

Using the Intel VTune Amplifier 2013 on Embedded Platforms

Product Change Notification

Intel Cache Acceleration Software for Windows* Workstation

Intel Desktop Board DG41RQ

Product Change Notification

Intel Desktop Board DH55TC

Intel Desktop Board D945GCLF2

Intel Desktop Board DG31PR

Intel Serial to Parallel PCI Bridge Evaluation Board

Product Change Notification

Installation Guide and Release Notes

Intel G31/P31 Express Chipset

Intel Desktop Board D946GZAB

Intel Desktop Board D975XBX2

How to Create a.cibd/.cce File from Mentor Xpedition for HLDRC

Intel Desktop Board D945GCCR

Sample for OpenCL* and DirectX* Video Acceleration Surface Sharing

Intel Desktop Board DP55SB

LED Manager for Intel NUC

INTEL PERCEPTUAL COMPUTING SDK. How To Use the Privacy Notification Tool

Product Change Notification

GAP Guided Auto Parallelism A Tool Providing Vectorization Guidance

Intel(R) Threading Building Blocks

Product Change Notification

How to Create a.cibd File from Mentor Xpedition for HLDRC

Native Configuration Manager API for Windows Operating Systems

OpenCL* and Microsoft DirectX* Video Acceleration Surface Sharing

Intel PXA27x Processor Family

Product Change Notification

Migration Guide: Numonyx StrataFlash Embedded Memory (P30) to Numonyx StrataFlash Embedded Memory (P33)

Intel Integrated Performance Primitives for Intel Architecture. Using Intel Integrated Performance Primitives in C++ Applications

Intel Desktop Board D915GUX Specification Update

Intel Desktop Board DP45SG

Intel Desktop Board D945GCLF

Intel Desktop Board D915GEV Specification Update

Intel X48 Express Chipset Memory Controller Hub (MCH)

Low Voltage Intel Pentium III Processor 512K Dual Processor Platform

Intel Desktop Board DH61SA

Product Change Notification

Global Call API for Host Media Processing on Linux

Performance Profiling Techniques on Intel XScale Microarchitecture Processors

Upgrading Intel Server Board Set SE8500HW4 to Support Intel Xeon Processors 7000 Sequence

Mobile Intel Pentium 4 Processor-M and Intel 852PM/GME/GMV Chipset Platform

Product Change Notification

Transcription:

Recommended JTAG Circuitry for Debug with Intel Xscale Microarchitecture Application Note June 2001 Document Number: 273538-001

Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked reserved or undefined. Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The Intel XScale microarchitecture may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an ordering number and are referenced in this document, or other Intel literature may be obtained by calling 1-800-548-4725 or by visiting Intel's website at http://www.intel.com. Copyright Intel Corporation, 2001 AlertVIEW, i960, AnyPoint, AppChoice, BoardWatch, BunnyPeople, CablePort, Celeron, Chips, Commerce Cart, CT Connect, CT Media, Dialogic, DM3, EtherExpress, ETOX, FlashFile, GatherRound, i386, i486, icat, icomp, Insight960, InstantIP, Intel, Intel logo, Intel386, Intel486, Intel740, IntelDX2, IntelDX4, IntelSX2, Intel ChatPad, Intel Create&Share, Intel Dot.Station, Intel GigaBlade, Intel InBusiness, Intel Inside, Intel Inside logo, Intel NetBurst, Intel NetStructure, Intel Play, Intel Play logo, Intel Pocket Concert, Intel SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel TeamStation, Intel WebOutfitter, Intel Xeon, Intel XScale, Itanium, JobAnalyst, LANDesk, LanRover, MCS, MMX, MMX logo, NetPort, NetportExpress, Optimizer logo, OverDrive, Paragon, PC Dads, PC Parents, Pentium, Pentium II Xeon, Pentium III Xeon, Performance at Your Command, ProShare, RemoteExpress, Screamline, Shiva, SmartDie, Solutions960, Sound Mark, StorageExpress, The Computer Inside, The Journey Inside, This Way In, TokenExpress, Trillium, Vivonic, and VTune are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others. *ARM and StrongARM are registered trademarks of ARM, Ltd. 2 Application Note

Contents Contents 1.0 Introduction...5 2.0 Requirements...5 3.0 JTAG Signals / Header...6 4.0 System Requirements...7 5.0 Hardware Requirements...8 5.1 Macraigor Raven* and Wind River Systems visionprobe* / visionice*...8 5.2 ARM* Multi-ICE*...8 6.0 References...9 Figures 1 JTAG Header...6 2 Example JTAG Signals at Power-Up...7 3 Example JTAG Signals at Debug Start-Up...7 4 Example Power-Up Circuit for ntrst...8 Tables Application Note 3

Contents Revision History Date Revision Description June 2001 001 Initial release. 4 Application Note

Introduction 1.0 Introduction Certain restrictions exist in order to use JTAG based debuggers with the Intel XScale microarchitecture (ARM* Architecture compliant). This is primarily due to the Tap Controller reset requirements of the Intel 80200 processor with Intel XScale microarchitecture and the reset requirements of specific JTAG debuggers. The following sections outline these requirements along with suggestions for circuitry to alleviate potential problems. 2.0 Requirements The Intel 80200 processor with Intel XScale microarchitecture, like many others, requires that ntrst (Tap Reset) is asserted low during power up for at least 32 core clock cycles. This is to ensure a fully initialized boundary scan chain. Failure to comply with this requirement may result in spurious behavior of the application. The ARM Multi-ICE JTAG debugger requires that ntrst is always weakly pulled high. This requirement stems from the fact that the debugger can only assert ntrst (drive low). Both reset signals coming from the Multi-ICE (ntrst and nsrst) are open collector and must be weakly pulled high in order to avoid unintentional resets (System or TAP). Application Note 5

JTAG Signals / Header 3.0 JTAG Signals / Header Figure 1 is the pin definition (20-pin standard ARM connector) for JTAG (See specific Product Design Guide for part number information). Figure 1. JTAG Header VTref 1 2 Vsupply ntrst 3 4 TDI 5 6 TMS 7 8 TCK 9 10 RTCK 11 12 TD0 13 14 nsrst 15 16 DBGRQ 17 18 DGBACK 19 20 A8982-01 The ARM Multi-ICE debugger along with the Macraigor Raven* and Wind River Systems visionprobe* / visionice* utilize this connector. The main difference to be noted is the specific implementation of ntrst for each debugger. The Macraigor Raven implementation actively drives ntrst (high and low). The Wind River Systems visionprobe / visionice can configure ntrst active or open collector (only drive low). ARM Multi-ICE is configured as open collector only. 6 Application Note

System Requirements 4.0 System Requirements In order to successfully invoke a debug session, the JTAG debug unit must be able to control ntrst and nsrst independently. The ntrst signal allows the debugger to get the TAP controller in a known state. The nsrst signal allows the debugger to control system/processor reset in order to download the debug handler via the JTAG interface. See Figure 2, Example JTAG Signals at Power-Up and Figure 3, Example JTAG Signals at Debug Start-Up. Figure 2. Note: Figure 2 and Figure 3 are examples and do not reflect actual signal timings. Example JTAG Signals at Power-Up VCC ntrst nsrst TCK TMS TDI TD0 A8978-01 Figure 3. Example JTAG Signals at Debug Start-Up VCC ntrst nsrst TCK TMS TDI TD0 A8979-01 Application Note 7

Hardware Requirements 5.0 Hardware Requirements Due to the conflicting requirements of Multi-ICE and the Intel 80200 processor, it is necessary to incorporate a circuit that can drive ntrst low at power up and weakly pull it high at all other times. This section details the circuits required for ntrst when using the Macraigor Raven, Wind River Systems visionprobe / visionice, and ARM Multi-ICE. Note: This section does not discuss circuitry needed for nsrst, due to varying system level requirements. 5.1 Macraigor Raven* and Wind River Systems visionprobe* / visionice* Both the Macraigor Raven and Wind River Systems visionprobe / visionice (when configured as active) do not require any special power-up circuitry. Simply, the requirement is that ntrst is weakly pulled down at the processor. It is suggested that the value of the pull-down resistor is 10kΩ or greater. The value of this resistor should be confirmed with the JTAG debugger manufacturer to ensure optimal performance. 5.2 ARM* Multi-ICE* The ARM Multi-ICE debugger requires special power-up circuitry due to the open collector implementation of the ntrst signal. This power-up circuit must ensure that ntrst is asserted (low)atpoweronandweaklypulledhighthereafter.seefigure 4, Example Power-Up Circuit for ntrst. This circuit is a universal solution and will work with other JTAG debug systems. Figure 4. Example Power-Up Circuit for ntrst ntrst-dgb 3.3 V 3.3 V 1 kω 3 MR# RESET# 2 220Ω ntrst 4 VCC 1 0.01µF MAX811S A8980-01 8 Application Note

References 6.0 References 1. Multi-ICE System Design Considerations Application Note 72 (http://www.arm.com/) 2. Intel 80310 I/O Processor Chipset with Intel XScale Microarchitecture Design Guide (http://developer.intel.com/design/iio/docs/iop310.htm) 3. Intel 80200 Processor Evaluation Platform Board Schematics (http://proto-cps.jf.intel.com/design/iio/docs/iop310.htm) 4. Max811/812 Datasheet (http://www.maxim-ic.com/) Application Note 9

References This page intentionally left blank. 10 Application Note