12.07.2015 Views

ARM DS-5 Using the Debug Hardware Configuration Utilities

ARM DS-5 Using the Debug Hardware Configuration Utilities

ARM DS-5 Using the Debug Hardware Configuration Utilities

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring CoreSight systems6.17 Configuring CoreSight systems with multiple devices per JTAG-AP multiplexorportThe debug hardware unit does not support auto-detection of devices behind a JTAG-AP.Therefore, you must manually specify <strong>the</strong> JTAG scan chain attributes so that <strong>the</strong> unit can put <strong>the</strong>o<strong>the</strong>r devices into BYPASS.To debug CoreSight systems that have processors connected to <strong>the</strong> <strong>Debug</strong> Access Port (DAP)through JTAG-AP, debug hardware must know <strong>the</strong> pre-bits and post-bits for JTAG operations.The following figure shows a hypo<strong>the</strong>tical scan chain that could be connected to a JTAG-AP.PostScan-IR=5 (Sum of IR Lengths)PostScan-DR=2 (Device Count)PreScan-IR=23 (Sum of IR Lengths)PreScan-DR=3 (Device Count)<strong>Debug</strong>Port<strong>Debug</strong> Access Port (DAP)DAPInternalBusTCK0RTCK0PostScanCSTDICSTDOIR=2 IR=3 CorePreScanIR=5 IR=7 IR=11JTAG-APMUXCSTDITCKnRTCKnCSTDOFigure 6-15 Scan chain connected to a JTAG-APMultiple devices on <strong>the</strong> scan chain are connected in series, with data flowing serially from TDIto TDO. This means that debugging a given target in <strong>the</strong> chain requires that certain pre-scan andpost-scan bits are used to ensure that <strong>the</strong> o<strong>the</strong>r devices are not affected by <strong>the</strong> data directed at<strong>the</strong> target device, and that <strong>the</strong> data is positioned correctly in <strong>the</strong> serial scan for <strong>the</strong> target device.To debug this system, you must set <strong>the</strong> following four configuration items:• Pre-scan IR bits for Devices after <strong>the</strong> core on <strong>the</strong> JTAG-AP scanchain(JTAG_AP_IR_PRE_BITS)This is <strong>the</strong> total length of <strong>the</strong> JTAG instruction registers (IRs) for devices appearingbetween <strong>the</strong> processor being configured and <strong>the</strong> CSTDO input on <strong>the</strong> JTAG-AP port. In<strong>the</strong> figure above, <strong>the</strong> three devices that appear between <strong>the</strong> target processor and <strong>the</strong>CSTDO input on <strong>the</strong> JTAG-AP port have IR lengths 5, 7 and 11, respectively. Therefore,you must set this value to 23.• Post-scan IR bits for Devices before <strong>the</strong> core on <strong>the</strong> JTAG-AP scanchain(JTAG_AP_IR_POST_BITS)This is <strong>the</strong> total length of <strong>the</strong> JTAG IRs for devices appearing between <strong>the</strong> CSTDI outputon <strong>the</strong> JTAG-AP port and <strong>the</strong> processor being configured. In <strong>the</strong> figure above, <strong>the</strong> twodevices that appear between <strong>the</strong> CSTDI output on <strong>the</strong> JTAG-AP port and <strong>the</strong> processorbeing configured have IR lengths 2 and 3, respectively. Therefore, you must set this valueto 5.• Pre-scan DR bits for Devices after <strong>the</strong> core on <strong>the</strong> JTAG-AP scanchain(JTAG_AP_DR_PRE_BITS)This is <strong>the</strong> total number of devices appearing between <strong>the</strong> processor being configured and<strong>the</strong> CSTDO input on <strong>the</strong> JTAG-AP port. In <strong>the</strong> figure above, <strong>the</strong>re are three devices thatappear between <strong>the</strong> processor being configured and <strong>the</strong> CSTDO input on <strong>the</strong> JTAG-APport. Therefore, you must set this value to 3.• Post-scan DR bits for Devices before <strong>the</strong> core on <strong>the</strong> JTAG-AP scanchain(JTAG_AP_DR_POST_BITS)<strong>ARM</strong> DUI 0498F Copyright © 2010-2012 <strong>ARM</strong>. All rights reserved. 6-26ID021112Non-Confidential

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!