Skip to main content

IAR Embedded Workbench for Arm 9.70.x

I-jet — Interface

In this section:

The Interface options specify the interface between I-jet or I-jet Trace and the target system.

IijetInterfaceOpt_01_ARM.png
Probe config
Auto

The I-jet driver automatically identifies the target CPU. It uses the default probe configuration file, if there is one. This works best if there is only one CPU present.

From file

Specifies that the probe configuration file needs to be overridden, or that there are several target CPUs.

Explicit

Specify how to find the target CPU.

Interface

Selects the communication interface between the debug probe and the target system. Choose between:

JTAG

Uses the JTAG interface.

SWD

Uses the SWO interface, which uses fewer pins than JTAG. Select SWD if you want to use the serial-wire output (SWO) communication channel. Note that if you select stdout/stderr via SWO on the General Options>Library Configuration page, SWD is selected automatically. For more information about SWO settings, see SWO Trace Window Settings dialog box.

cJTAG

Uses the cJTAG interface.

Interface speed

Specifies the JTAG and SWD communication speed. Choose between:

Auto detect

Automatically uses the highest possible frequency for reliable operation.

Adaptive

Synchronizes the clock to the processor clock outside the core. Works only with Arm devices that have the RTCK JTAG signal available.

n MHz

If there are JTAG communication problems or problems in writing to target memory (for example during program download), these problems might be resolved if the speed is set to a lower frequency.

Probe configuration file
Override default

Specify a probe configuration file to be used instead of the default probe configuration file that comes with the product package.

Select

Specify how to find the target CPU.

Explicit probe configuration
Multi-target debug system

Specifies that the debug system consists of more than one CPU.

Target number (TAP or Multidrop ID)

If the debug system is a multi-drop SWD, specify the Multidrop ID (in hexadecimal notation) of the DAP where your CPU is located.

If the debug system is a JTAG scan chain, specify the Target number TAP (Test Access Port) position of the device you want to connect to. The TAP numbers start from zero and are counted from the TDO end (TAP number 0 is the one connected to the TDO line). If there are several CPUs at the TAP position, you also need to specify the CPU number on target.

Target with multiple CPUs

Specifies that the target has several CPUs.

CPU number on target

If the debug system is a multicore SWD, specify the CPU number on the DAP.

If the debug system is a JTAG scan chain and there are several CPUs at the TAP position, specify the CPU number on the TAP.

JTAG scan chain contains non-Arm devices

Enables JTAG scan chains that mix Arm devices with other devices like, for example, FPGA.

Preceding bits

Specify the number of IR bits preceding the Arm core to connect to.