IAR SYSTEMS I-jet User manual

IARprobesArm-9
IAR Debug Probes User
Guide
I-jet®, I-jet Trace, and I-scope™
for Arm Limited’s
Arm Cores

AFE1_AFE2-1:1
2
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
COPYRIGHT NOTICE
© 2012–2020 IAR Systems AB.
No part of this document may be reproduced without the prior written consent of IAR
Systems AB. The software described in this document is furnished under a license and
may only be used or copied in accordance with the terms of such a license.
DISCLAIMER
The information in this document is subject to change without notice and does not
represent a commitment on any part of IAR Systems. While the information contained
herein is assumed to be accurate, IAR Systems assumes no responsibility for any errors
or omissions.
In no event shall IAR Systems, its employees, its contractors, or the authors of this
document be liable for special, direct, indirect, or consequential damage, losses, costs,
charges, claims, demands, claim for lost profits, fees, or expenses of any nature or kind.
TRADEMARKS
IAR Systems, IAR Embedded Workbench, Embedded Trust, C-Trust, IAR Connect,
C-SPY, C-RUN, C-STAT, IAR Visual State, IAR KickStart Kit, I-jet, I-jet Trace,
I-scope, IAR Academy, IAR, and the logotype of IAR Systems are trademarks or
registered trademarks owned by IAR Systems AB.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
Arm, Cortex, Thumb, and TrustZone are registered trademarks of Arm Limited.
EmbeddedICE is a trademark of Arm Limited. uC/OS-II and uC/OS-III are trademarks
of Micrium, Inc. CMX-RTX is a trademark of CMX Systems, Inc. ThreadX is a
trademark of Express Logic. RTXC is a trademark of Quadros Systems. Fusion is a
trademark of Unicoi Systems.
Renesas Synergy is a trademark of Renesas Electronics Corporation.
Adobe and Acrobat Reader are registered trademarks of Adobe Systems Incorporated.
All other product names are trademarks or registered trademarks of their respective
owners.
EDITION NOTICE
Ninth edition: February 2020
Part number: IARprobesArm-9
This guide applies to version 8.50.x of IAR Embedded Workbench® for Arm.
Internal reference: Mym8.4, tut2009.1, INIT.

AFE1_AFE2-1:1
3
Contents
I-jet ............................................................................................................................. 5
Introduction ................................................................................................ 5
The I-jet in-circuit debugging probe .................................................... 6
Requirements ....................................................................................... 7
Supported core families ....................................................................... 7
Target connections ............................................................................... 7
Working with I-jet .................................................................................... 8
Setup and installation ........................................................................... 8
Connecting the target system ............................................................... 8
Updating the probe firmware ............................................................... 9
Technical specifications ....................................................................... 13
The I-jet package ................................................................................ 13
Model specifications .......................................................................... 13
JTAG timing specification ................................................................. 14
Hardware revision history .................................................................. 15
Target interface .................................................................................. 16
Indicators ............................................................................................ 20
Adapters ............................................................................................. 21
I-jet Trace ............................................................................................................. 37
Introduction .............................................................................................. 37
The I-jet Trace CM and I-jet Trace A/R/M in-circuit debugging
probes ................................................................................................. 37
Requirements ..................................................................................... 38
Target connections ............................................................................. 39
Working with I-jet Trace .................................................................... 39
Setup and installation ......................................................................... 40
Connecting the target system ............................................................. 40
Using Trace ........................................................................................ 41
Updating the probe firmware ............................................................. 41

AFE1_AFE2-1:1
4
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
Technical specifications ....................................................................... 42
The I-jet Trace package ...................................................................... 42
Model specifications .......................................................................... 42
Hardware revision history .................................................................. 44
Connectors ......................................................................................... 45
Indicators ............................................................................................ 47
Adapters ............................................................................................. 48
Designing target boards for ETM trace .............................................. 52
General PCB layout guidelines .......................................................... 53
I-scope .................................................................................................................... 57
Introduction .............................................................................................. 57
Reasons for using I-scope .................................................................. 57
Requirements for using I-scope ......................................................... 57
The I-scope probe ............................................................................... 57
Current and voltage measurement using I-scope ............................... 58
Working with I-scope ........................................................................... 60
Setup and Installation ......................................................................... 60
Technical specifications ....................................................................... 60
The I-scope package ........................................................................... 61
External characteristics ...................................................................... 61
I-scope probe specification ................................................................ 62

AFE1_AFE2-1:1
5
I-jet
●Introduction
●Working with I-jet
●Technical specifications
Introduction
These topics are covered:
●The I-jet in-circuit debugging probe
●Requirements
●Supported core families
●Target connections

AFE1_AFE2-1:1
6
Introduction
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
THE I-JET IN-CIRCUIT DEBUGGING PROBE
I-jet connects to the target board via a JTAG, SWD, or cJTAG connection, and to the
host computer via the USB port.
I-jet communicates using USB 2.0. (USB 1.0 is also supported but not recommended.)
The I-jet in-circuit debugging probe is also referred to as a debug probe, debug adapter,
or JTAG in-circuit emulator by different tool vendors.
C-SPY debugger
C-SPY driver
USB connection
I-jet
JTAG, SWD
or cJTAG

AFE1_AFE2-1:1
I-jet
7
I-jet streams the program counter, variables, and power measurement data to the host
computer to provide a view into program execution in real time. Besides the typical
JTAG debugging, I-jet is capable of providing power to the target board and measuring
it with sufficient accuracy to provide a power profile during program execution in real
time. This feature is referred to as power debugging.
For debugging Cortex devices, I-jet also supports the SWO (Serial Wire Output) feature,
which can be used for tracing the program execution and tracking variables at predefined
points in your code.
The I-jet in-circuit debugging probe has full support for on-chip trace—ETB
(Embedded Trace Buffer), MTB (Micro Trace Buffer), and TMC (Trace Memory
Controller).
REQUIREMENTS
I-jet needs to be controlled by the IAR C-SPY® Debugger which comes with the IAR
Embedded Workbench® IDE.
SUPPORTED CORE FAMILIES
These cores are currently supported:
●Arm7
●Arm9
●Arm11
●Cortex-M
●Cortex-R
●Cortex-A
TARGET CONNECTIONS
These interfaces are supported:
●MIPI-20 (part number SHF-110-01-L-D): JTAG, cJTAG, SWD, SWO, ETM
●MIPI-10 (part number SHF-105-01-L-D): JTAG, cJTAG, SWD, SWO
●ARM-20 (part number HTST-110-01-L-DV): JTAG, cJTAG, SWD, SWO
I-jet comes with a MIPI-20 connector on the front panel, with MIPI-20 and MIPI-10
cables, and a legacy ARM-20 adapter.
All other available I-jet adapters are also compatible with I-jet Trace.

AFE1_AFE2-1:1
8
Working with I-jet
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
Working with I-jet
These tasks are covered:
●Setup and installation
●Connecting the target system
●Updating the probe firmware
For information about debugging using I-jet, see the C-SPY® Debugging Guide for
Arm.
SETUP AND INSTALLATION
Software
Before you can use I-jet, you need to install IAR Embedded Workbench for Arm. For
information, see the Installation and Licensing Quick Reference Guide and the
Licensing Guide.
Probe setup
I-jet does not require any special driver software installation. Normally, all drivers for
I-jet are automatically installed as part of the IAR Embedded Workbench installation.
If you need to install the USB driver manually, navigate to \Program Files
\IAR Systems\Embedded Workbench x.x\arm\drivers\jet\USB\32-bit or
64-bit (depending on your system). Start the dpinst.exe application. This will
install the USB driver.
For information about using multiple I-jet probes on the same host computer, see the
C-SPY® Debugging Guide for Arm.
CONNECTING THE TARGET SYSTEM
Power-up your I-jet probe
1Connect I-jet to the target board using the cable that matches the target board connector
(MIPI-20 or MIPI-10). If a standard JTAG connector is used, you must first plug the
ADA-MIPI20-ARM20 adapter into the JTAG connector.
2Connect I-jet to the host computer using the USB micro cable.
Note: No harm is done if the above order is reversed.
To prevent damage, the target GND and the USB host GND must be at the same level.
When hot-plugging, make sure that the PC and the target board power supply are
connected to the same grounded wall outlet or a common grounded desktop power strip.

AFE1_AFE2-1:1
I-jet
9
Power up your evaluation board
If you have an evaluation board that is prepared for it, you can power the board via I-jet
through pin 19 on the standard ARM-20 connector, or pin 11/13 on the small MIPI-20
connector. Target power of up to 420 mA can be supplied from I-jet with overload
protection. Most of the IAR Systems KickStart Kits contain an evaluation board that can
be powered this way. Make sure that the power jumper found on most of these boards
matches your setup.
Note: The target board will get power via I-jet once you choose the Download and
Debug or Debug without Downloading command, but not before.
Note: The only way to use the power debugging feature is to power up your evaluation
board via I-jet.
UPDATING THE PROBE FIRMWARE
I-jet and I-jet Trace are designed so that firmware updates are not necessary unless new
features added to IAR Embedded Workbench for Arm require extra hardware support.
When a new version of IAR Embedded Workbench for Arm is released and a new
feature that requires new firmware is used, C-SPY displays a message in the DebugLog
window asking you to update the firmware.
Note: Support for new MCU devices is managed by software updates in IAR Embedded
Workbench for Arm, and has nothing to do with I-jet or I-jet Trace firmware.
For more information about firmware versions, see the release notes.
To update the probe firmware:
1In IAR Embedded Workbench, choose I-jet>EmuDiag to display the About to
Connect to an Emulator dialog box.
Select Connect to an EmulatorAutomatically and click Next.

AFE1_AFE2-1:1
10
Working with I-jet
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
2In the EmuDiag dialog box, click Update Firmware.

AFE1_AFE2-1:1
I-jet
11
3In the Open dialog box, browse to the arm\bin\jet\firmware\i-jet folder of
your IAR Embedded Workbench installation. In one of the subfolders, select the
firmware file that you want to use and click Open.

AFE1_AFE2-1:1
12
Working with I-jet
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
4The update log information is displayed in the EmuDiag dialog box.
5When the firmware update is complete, a message is displayed.

AFE1_AFE2-1:1
I-jet
13
Technical specifications
Reference information about:
●The I-jet package, page 13
●Model specifications, page 13
●JTAG timing specification, page 14
●Hardware revision history, page 15
●Target interface, page 16
●Indicators, page 20
●Adapters, page 21
THE I-JET PACKAGE
The I-jet package contains:
●The I-jet in-circuit debugging probe
●MIPI-20 JTAG cable
●MIPI-10 JTAG cable
●USB 2.0 Micro B cable
●ADA-MIPI20-ARM20 adapter
●Welcome letter
MODEL SPECIFICATIONS
These are the specifications of I-jet:
USB speed 480 Mbps (USB 2.0)
USB connection Micro-B
Target connection MIPI-20, MIPI-10
Adapters included ADA-MIPI20-ARM20
I-jet debug interface JTAG and SWD
JTAG/SWD maximum clock 32 MHz
SWO protocols supported Manchester and UART
SWO maximum speed 60 Mbps
Power supplied to target 420 mA max at 4.4 V-5 V
Over-current protection ~520 mA

AFE1_AFE2-1:1
14
Technical specifications
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
* <= 4 ns when the target board is connected
I-jet comes with a 20-pin MIPI connector—0.05 in × 0.05 (1.27 mm x 1.27 mm) pitch—
on the front panel. It includes two cables:
●A 6-inch cable with 20-pin MIPI connectors on both ends for the Cortex-M targets
with 20-pin MIPI headers. Pin 7 on each end is keyed with a white plug.
●A 6-inch cable with a 20-pin MIPI connector on one side (to connect to I-jet), and a
10-pin MIPI connector on the other side for connection to Cortex-M targets with
10-pin headers. Pin 7 on the 20-pin end is keyed with a white plug. A red stripe on
the cable indicates pin 1 (VTref).
JTAG TIMING SPECIFICATION
This figure shows the JTAG timing and parameters:
Target power measurement resolution ~160 uA
Target power measurement speed up to 200 ksps (kilo samples per second)
JTAG voltage range (auto-sensing) 1.65 V to 5.5 V
JTAG VTref measurement resolution ~2 mV
Current draw from VTref < 50 uA
JTAG clock rise/fall time (TCK) <= 2 ns*
Clock fall time <= 2 ns*

AFE1_AFE2-1:1
I-jet
15
In a JTAG device that fully complies to IEEE1149.1 standard, the TDI/TMS signals
should be sampled on the rising edge of TCK, and TDO should be sent on the falling
edge of TCK. I-jet takes advantage of these requirements and changes its TDI and TMS
signals on the falling edge of TCK and samples the TDO on the rising edge of TCK.
However, to accommodate target boards with long JTAG chains and fast JTAG clocks,
I-jet allows TDO to be as late as 50 ns after the rising edge of TCK.
Note: In the adaptive mode of operation, I-jet samples the TDO on the rising edge of
RTCK rather than TCK.
This table shows the timing specifications of the JTAG port measured at the end of its
MIPI-20 cable without connection to target (VTref set to 3.3 V). The only load on the
measured signals is the oscilloscope 3.9 pF probe.
1 Tsod is the maximum delay from the falling edge of TCK and a valid level on the I-jet
output signals, TDI and TMS. The target MCU will sample 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.
2 Tsid is the minimum setup time for the TDO input signal, relative to the rising edge of
TCK when I-jet samples this signal. Because the target MCU changes its TDO value on
the previous falling edge of TCK, there might not be enough time at very-high JTAG
speeds for the TDO to arrive before the positive edge of TCK. To compensate for any
TDO delays, I-jet configures itself automatically to delays introduced to the TDO by the
target board and will tolerate TDO delays of up to 50 ns after the positive edge of the
TCK.
HARDWARE REVISION HISTORY
These are the versions of I-jet:
Parameter Min Max Description
Ttckl 15.6 ns 250 us TCK LOW period
Ttckh 15.6 ns 250 us TCK HIGH period
Tsod1-- 2.0 ns TDI and TMS outputs valid from TCK
falling
Tsid23 ns before TCK to 50 ns
after TCK
-- TDO setup to TCK rising
Ttdo Ttckl -- TDO valid length
Table 1: I-jet JTAG port timing specifications
Version Change specification Date
Version A The first version April 2012
Table 2: I-jet versions

AFE1_AFE2-1:1
16
Technical specifications
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
Version, production date, and serial number can be found on the backside of the probe.
Note: In IAR Embedded Workbench, choose I-jet>EmuDiag to start the EmuDiag
application where you can diagnose the connection between the host computer, the
probe, and the board.
TARGET INTERFACE
This section contains descriptions of pinout, signals, and connectors. The following
cables are described in detail:
●The JTAG/SWD - MIPI-20 cable
●The JTAG/SWD - MIPI-10 cable
The JTAG/SWD - MIPI-20 cable
I-jet comes with a 6-inch cable with 20-pin MIPI connectors on both ends for the
Cortex-M devices with 20-pin MIPI headers. Pin 7 on each end is keyed with a white
plug:
The mating connector for a target board has the pitch size 0.05 in (1.27 mm). You can,
for example, use part number SHF-110-01-L-D.
Version B Added extra RAM to the SWO FIFO buffer to improve
SWO performance on older, slower PCs.
Optional board current measurement resolution at 16.3 uA
instead of 163 uA on I-jet Version A.
June 2017
Version Change specification Date
Table 2: I-jet versions (Continued)

AFE1_AFE2-1:1
I-jet
17
These are the MIPI-20 pin definitions:
Pin Signal Type Description
1 VTref Input The target reference voltage. Used by I-jet to check
whether the target has power, to create the
logic-level reference for the input comparators, and
to control the output logic levels to the target. It is
normally fed from JTAG I/O voltage.
2 SWDIO/TMS I/O, output JTAG mode set input of target CPU. This pin should
be pulled up on the target. Typically connected to
TMS of the target CPU.
3 This pin is a GND pin connected to GND in I-jet. It
should also be connected to GND in the target
system.
4SWCLK/TCKOutputJTAGclock signal to target CPU. It is recommended
that this pin is pulled to a defined state of the target
board. Typically connected to TCK of the target
CPU.
5 This pin is a GND pin connected to GND in I-jet. It
should also be connected to GND in the target
system.
6 SWO/TDO Input JTAG data output from target CPU. Typically
connected to TDO of the target CPU. When using
SWD, this pin is used as Serial Wire Output (SWO)
trace port. (Optional, but not required for SWD
communication.)
-- -- -- This pin (normally pin 7) does not exist.
8 TDI Output JTAG data input of target CPU. It is recommended
that this pin is pulled to a defined state on the target
board. Typically connected to TDI of the target CPU.
For CPUs which do not provide TDI (SWD-only
devices), this pin is not used (tri-stated).
9 This pin is a GND pin connected to GND in I-jet. It
should also be connected to GND in the target
system.
10 nRESET I/O Target CPU reset signal. Typically connected to the
RESET pin of the target CPU, which is typically called
nRST, nRESET, or RESET.
Table 3: MIPI-20 pin definitions

AFE1_AFE2-1:1
18
Technical specifications
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
11 TgtPwr Output This pin can be used for supplying 5 V power to the
target hardware from I-jet.
12 Not
used
TRACECLK Input Input trace clock.
13 TgtPwr Output This pin can be used for supplying 5 V power to the
target hardware from I-jet.
14 Not
used
TRACEDATA[0]
/
SWO2
Input Input Trace data pin 0. This pin can be used as
secondary SWO.
15 This pin is a GND pin connected to GND in I-jet. It
should also be connected to GND in the target
system.
16 Not
used
TRACEDATA[1]
/
nTRST
Input Input Trace data pin 1. This pin can be used as
nTRST.
17 This pin is a GND pin connected to GND in I-jet. It
should also be connected to GND in the target
system.
18 Not
used
TRACEDATA[2] Input Input Trace data pin 2.
19 This pin is a GND pin connected to GND in I-jet. It
should also be connected to GND in the target
system.
20 Not
used
TRACEDATA[3] Input Input Trace data pin 3.
Pin Signal Type Description
Table 3: MIPI-20 pin definitions (Continued)

AFE1_AFE2-1:1
I-jet
19
The JTAG/SWD - MIPI-10 cable
I-jet also comes with a 6-inch cable with a 20-pin MIPI connector on one side (to
connect to I-jet) and a 10-pin MIPI connector on the other side for connection to Cortex
devices with 10-pin headers. Pin 7 on each end is keyed with a white plug:
The mating connector for a target board has the pitch size 0.05 in (1.27 mm). You can,
for example, use part number SHF-105-01-L-D.
These are the MIPI-10 pin definitions:
Pin Signal Type Description
1 VTref Input The target reference voltage. Used by I-jet to check
whether the target has power, to create the logic-level
reference for the input comparators, and to control the
output logic levels to the target. It is normally fed from
JTAG I/O voltage.
2 SWDIO/TMS I/O, output JTAG mode set input of target CPU. This pin should be
pulled up on the target. Typically connected to TMS of the
target CPU.
3 GND GND Connected to logic GND on I-jet.
4 SWCLK/TCK Output JTAG clock signal to target CPU. It is recommended that
this pin is pulled to a defined state of the target board.
Typically connected to TCK of the target CPU.
5 GND GND Connected to logic GND on I-jet.
6 SWO/TDO Input JTAG data output from target CPU. Typically connected to
TDO of the target CPU. When using SWD, this pin is used
as Serial Wire Output (SWO) trace port. (Optional, not
required for SWD communication.)
7-- KEY KEYorGND.
Table 4: MIPI-10 pin definitions

AFE1_AFE2-1:1
20
Technical specifications
IAR Debug Probes User Guide
I-jet®, I-jet Trace, and I-scope™
INDICATORS
I-jet has three LED indicators on the top, marked TPWR, DBG, and USB. The
following indicators and their statuses are described in detail:
●The TPWR indicator (Target power)
●The DBG indicator (JTAG/SWD)
●The USB indicator
The TPWR indicator (Target power)
The DBG indicator (JTAG/SWD)
8 TDI/NC Output JTAG data input of target CPU. It is recommended that this
pin is pulled to a defined state on the target board. Typically
connected to TDI of the target CPU. For CPUs that do not
provide TDI (SWD-only devices), this pin is not used
(tri-stated).
9 GND GND GND and target detect presence.
10 nRESET Output nRESET or TRST.
Indicator status Description
Off Power to target is not provided by I-jet.
Green Power to target is provided by I-jet.
Yellow Warning. Power to target is above 420 mA.
Red Error. Overcurrent limit (520 mA) detected and power to target was
switched off for protection.
Table 5: TPWR indicator statuses
Indicator status Description
Off vTRef on JTAG header is too low.
Green vTRef is at or above 1.8 V.
Green blinking Indicates JTAG/SWD communication activity.
Table 6: DBG indicator statuses
Pin Signal Type Description
Table 4: MIPI-10 pin definitions (Continued)