iC6000 On-chip Analyzer

Parent Previous Next

       








Thank you for purchasing this product from iSYSTEM. This product has been carefully crafted to satisfy your needs. Should any questions arise, do not hesitate to contact your local distributor or iSYSTEM directly. Our technical support personnel will be happy to answer all your technical support questions.


All information, including contact information, is available on our web site www.isystem.com. Feel free also to explore our alternative products.


iSystem constantly yields for development and therefore certain pictures in this documentation may vary slightly from the actual product you received. The differences should be minor, but should you find more serious inconsistencies of the product with the documentation, please contact your local distributor for more information.


This document and all documents accompanying it are copyrighted by iSYSTEM and all rights are reserved. Duplication of these documents is allowed for personal use. For every other case a written consent from iSYSTEM is required.


Copyright © 2017 iSYSTEM, AG.

All rights reserved.

All trademarks are property of their respective owners.


www.isystem.com

iC6000 Base Unit

Ordering code

IC60000-1



The iC6000 Base Unit is a base platform connecting to the PC via the TCP/IP or USB 3.0 port. The iC6000 USB 3.0 port is backward compatible with USB 2.0 ports on the PC side.


The USB 3.0 connection provides best tool performance. Aurora interface is being used on modern multi-core microcontrollers running at high frequencies. Such microcontrollers typically feature an on-chip Nexus trace module, which outputs large amount of message-based information, providing detailed insight into microcontroller’s application behavior (code execution and data access). Message-based information is broadcasted to the external tool via Aurora, a Xilinx defined protocol, where it’s first stored in 8 GB fast storage memory acting as a FIFO and then uploaded to the PC via fast USB 3.0 interface. This ensures maximum possible analyzer (trace, profiler, coverage) session times and short upload times.


Make sure that the USB 3.0 cable delivered along the iC6000 is being used. It has been proven that many USB 3.0 specified cables don’t work reliably. When using a cable of your own selection, test it well in conjunction with the iC6000 before use.


TCP/IP communication could be used to access iC6000 from a distant PC or when a single iC6000 unit is shared between multiple PCs or users.


The iC6000 Base Unit features 8GB of analyzer storage buffer.


Depending on the target microcontroller architecture, iC6000 comes preconfigured with the according DTM module and according Aurora trace cable.


There are three status LEDs on the iC6000 Base Unit. The LEDs inform the user of the current status of the emulation system. Their meaning is:

– When lit, the unit is turned on

R – When lit, the target  application being controlled is running

F – When lit, the unit is free for communication, i.e. winIDEA can connect to it.





Power Supply

A round 3-pin power connector is located on the rear of the iC6000 base unit.



Power connector pinout, view from the rear of the Emulator

The iC6000 unit accepts a wide input voltage range from 10V to 24V DC, thus enabling the Emulator to work also with a 12V or 24V car battery. Power consumption is up to 15W (iC6000 without optional I/O module).


The necessary power supply (IC30000-PS) comes along the iC6000 unit.

IC30000-PS


An optional 12V power supply for Car (cigarette lighter) plug can be ordered under the IC30000-PS-CAR12V ordering code.

IC30000-PS-CAR12V


Note: Use only original iSYSTEM accessories for powering the iC6000. If you wish to use a power supply different from the delivered one, please consult with iSYSTEM first.


iC6000 System Power On / Power Off Sequence


In general, emulator and target must be in the same power state. Both must be on, or both off. Level translators on the DTM module go high-Z when either emulator or target (TAR_VREF) supply is off. Therefore, it is recommended to use Vref setting in winIDEA Hardware/Emulation options/Hardware/Debug I/O levels menu. Note, this is not applicable if using Hot Attach.


In practice, typically iC6000 and the target cannot be powered simultaneously. To prevent hardware damage due to incorrect power on or power off sequence of the system, next guide line must be followed: When powering the system, switch ON the iC6000 before the target; when shutting down the system, switch OFF the target before the iC6000!

If emulator is switched off but target is left on, forcing 5V through protection diodes on the DTM I/O pins could activate level-translation buffers in improper way. They in turn could drive excessive current through 47E resistors that would eventually be overheated and completely blown. The same can happen in reversed power state and emulator is set for internal 5V source, for example.

iC6000 DTM module

Typically, iC6000 comes prebuilt with one of the available DTM modules. User must specify target architecture and MCU trace port type at ordering.

The DTM module features protection and minimal electronic logic adjusting iC6000 to a specific target microcontroller debug and trace interface. This makes iC6000 base unit being universal for all target architectures featuring Aurora (serial) trace interface.


DTM Debug Interface

The device supports digital logic levels from 1.8V to 5V. Other levels are available on request. The DTM Debug Interface consists of debug signals, for example JTAG: TCK, TMS, TRST, TDI, TDO, RESET, and some general purpose I/O signals.

 

All signals have a 47E series termination/protection resistors and ESD protection devices. All inputs have 10K pull-up resistor, except TDO input that has a 10K pull-down. Bidirectional I/Os have pull-up resistors: TMS and TDI have 10K, RESET has a 1K. The latter is buffer-driven to prevent current flow into unpowered emulator DTM from a powered target board.

 

Debug signals are additionally protected with 100mA resettable fuses.

 

The TAR_VREF pin has a 100K input impedance. 


iC6000 DTM Aurora/JTAG (Tricore, MPC)

Ordering code

IC60022-1




This module supports Infineon Aurix (Tricore), Freescale MPC57xx and ST SPC57JTAG debug interface and serial Aurora trace protocol.

This module is required when connecting to the Aurix based target featuring 22-pin Samtec ERF8 series connector. The iC6000 connects to the target microcontroller through the 22-pin High-speed Aurora cable (IC60040-1).

Note: Targets based on Infineon Aurix family can feature two debug interfaces, either JTAG or DAP. The DAP has better throughput performance and has less physical signals comparing to the JTAG, which means it’s the preferred debug interface for Aurix family. When the iC6000 is to be connected through the JTAG debug interface, iC6000 DTM Aurora/JTAG module (IC60022-1) is required and when connecting to the DAP, iC6000 DTM Aurora/DAP module (IC60023-1) is required. Note that iC6000 DTM modules are not meant to be exchanged by the user. Appropriate DTM module must be specified at order time.

This module (IC60022-1) is also required when connecting to the MPC57xx/SPC57 based target featuring 34-pin Samtec ERF8 series connector. In this case, the iC6000 connects to the target microcontroller through the 34-pin High-speed Aurora cable (IC60041-1).


iC6000 DTM Aurora/DAP (TriCore)

Ordering code

IC60023-1





This module supports Infineon Aurix (Tricore) DAP debug interface and serial Aurora trace protocol. It’s required when connecting to the target featuring 22-pin Samtec ERF8 series connector. The iC6000 connects to the target microcontroller through the 22-pin High-speed Aurora cable (IC60040-1).

Note: Targets based on Infineon Aurix family can feature two debug interfaces, the JTAG or the DAP. The DAP has better throughput performance and has less physical signals comparing to the JTAG, which means it’s the preferred debug interface for Aurix family. When the iC6000 is to be connected through the JTAG debug interface, iC6000 DTM Aurora/JTAG module (IC60022-1) is required and when connecting to the DAP, iC6000 DTM Aurora/DAP module (IC60023-1) is required. Note that iC6000 DTM modules are not meant to be exchanged by the user. Appropriate DTM module must be specified at order time.

Both, 2-pin and 3-pin (Wide Mode) DAP debug interfaces are supported. DAP interface width is configurable setting in winIDEA IDE.




iC6000 I/O Module (optional)

Ordering code

IC60011




Through this module the iC6000 development and test system can connect to the analog and digital world around the microcontroller. It also allows building up a so called Hardware-In-the-Loop (HIL) test environment.


Analog and/or digital signals from the target can be measured, observed and traced along the program execution flow. At the same time, the iC6000 I/O module can generate analog and/or digital stimulus towards the target.


Module is optional and can be added to the iC6000 system at any time.

Features:

System Port: trigger output, 100ohm series termination.

Digital inputs: 8 channels, 10kOhm input impedance, 5V tolerant, ESD protected.

Digital outputs: 8 channels, 100ohm output series termination, ESD protected.

Analog inputs: 2 channels, 8-bit ADCs, 1MOhm input impedance, range is ±5.0V with 1:1 probe, ±50V with a 10:1 probe, 3ns acquisition time.
Power measurement probe uses these two inputs for power measurement.

Analog outputs: 2 channels, 8-bit DACs, ±4.5V bipolar output, ±7mA drive, 100 ohm output resistance.

Optional 10MHz temperature compensated precision oscillator TCXO for a high accuracy long duration trace/analyzer session measurements.

iC6000 with the I/O module assembled


All digital signals are 3.3V LVTTL compatible and are ESD protected.


All analog signals have a Schottky diode over- / undervoltage protection, except the Current Sense signals.


The maximum voltage on the Current Sense probe is 60V.


Nominal sampling rate is 1MSPS.


Connectors

iC6000 I/O Module Connectors’ Pinout

10-pin header for the System Port.

16-pin header for 8 digital inputs.

16-pin header for 8 digital outputs.

10-pin header for 2 analog outputs.

2 BNC connectors for 2 analog inputs.

10-pin header for Power Measurement Port.

All connectors, except the BNCs, are standard Berg 2.54mm / 100mils raster.


For analog inputs, standard scope probes can be used.


For more details on I/O module and its use, refer to a separate standalone document titled I/O Module user’s manual.


Grounding Wire Use

In case of the on-chip emulation, it has been proven that a development tool can be damaged at the moment when the emulator's debug connector is plugged into the target system when neither the target nor the emulator are powered up yet. At this point in time, there could be ground potential difference between the emulator and the target way over 1000V.  Such voltage difference is then discharged over the emulator and the target, which can destroy electronic components of the emulator and/or the target.


The voltage difference can be introduced by:

power supply (target, emulator), which does not have the power outlet ground connected with the power supply ground.

power outlets which have different ground potentials

PC, when iC6000 connects to the PC through the USB port

Connecting a dedicated grounding wire, which is shipped with the iC6000 unit, between the iC6000 system and the target before the target debug cable adapter is connected to the target, makes the complete development system even more robust and resistant to the mentioned electrical discharge problem - despite the fact the iC6000 development system features already a high quality protection on all connecting signals by default.

iC6000 with the grounding wire and the ground pin in the left bottom corner

The grounding wire connecting the target and iC6000

Licenses

As with all iSYSTEM tools, winIDEA license is required. Valid winIDEA license also includes iSYSTEM technical support service, either by phone or by e-mail support@isystem.com.


Besides winIDEA, at least one CPU architecture license is required in order to connect to the target microcontroller via debug interface. Advanced functionalities such as trace, profiling and code coverage become available via trace license.


iSYSTEM development tools feature a hardware based license scheme, which saves costs comparing to per-seat based licenses. All licenses are kept in iC6000 blue box, which conveniently allows moving iC6000 unit from one development seat to another.


In accordance with the order, iC6000 system ships with the CPU architecture, multi-core and/or trace license preprogrammed. After receiving the iC6000 system, only winIDEA (IDE) license needs to be requested from iSYSTEM. Note that iC6000 starts in 30 days evaluation period when being used for the first time. This gives user sufficient time to obtain winIDEA license init string before evaluation period expires.


CPU architecture, multi-core and trace license are programmed by the user if certain license is ordered after the initial iC6000 order.


Below picture shows the sticker, which can be found on iC6000 system, identifying which CPU architecture licenses were preprogrammed by the iSYSTEM test department. Below picture shows preprogrammed Cortex-M3 and MPC56xx licenses.

Communication

The iC6000 supports two types of communication: 10/100M Ethernet and USB 3.0. It is recommended to use USB3.0 interface since it provides the fastest transfer from the iC6000 development and test system to the PC where winIDEA IDE runs. This will guarantee a maximum performance of the iC6000 development and test system.


Specify the communication port through which the iC6000 unit connects to the PC in the Hardware/Hardware/Communication tab.


Hardware Configuration dialog, Communication page

Universal Serial Bus (USB) - select when the Emulator is attached to the PC's USB port. The Emulator is selected in the Device pull-down menu. When the Emulator is connected to the USB port of a computer for the first time, Windows will detect a new device and may prompt you for the driver for it. Specify the path to the USB directory in the winIDEA installation directory. If only one emulator is connected to the PC via the USB then the Device combo box can be left empty (recommended). In this case, if you exchange the emulator with another one, you don’t have to change the communication settings.

TCP/IP – This option sets the TCP/IP properties of the iC5700. See ‘Setting up TCP/IP communication’ section for more details on TCP/IP setup.

Use the 'Test' button to test the communication settings.

Communication test window

Setting up TCP/IP communication

If the Emulator is connected using the Ethernet, its TCP/IP settings must be configured on both sides: the Emulator and in winIDEA.


More information on configuring the Emulator and winIDEA can be found in the Hardware User’s Guide.

First step: Configuring the Emulator

The Emulator must be connected using USB port. The connection must be set up in the ‘Hardware/Communication’ tab. Then, select the ‘Hardware/Hardware Type’ tab and click on the ‘System Configuration…’ button.

System configuration options

The TCP/IP settings can be obtained from the DHCP server on the network. If such a server is not available, the settings can be set manually. In this case, in the TCP/IP Configuration window, the IP Address, the Subnet Mask and the TCP Port must be specified. The default gateway address must be specified, if the Emulator is used via a gateway. The IP Address, available for the Emulator to use, the Subnet Mask and the default gateway, if needed, are usually defined by your network administrator. The TCP Port can be any port between 1024 and 65535, which is not already used. By default, the TCP port 5313 is used. For the information, if this port address could cause any conflicts and for an alternative port address, also contact your network administrator. When the correct settings are entered, click on the ‘Apply changes’ button. This writes the changes to the Emulator.


The Emulator must be switched off and then on again in order for changes to take effect.


Emulator’s MAC address is written on the same sticker where you will also find device serial number as it is shown on the next picture.

Second step: Configuring communication

There are two ways of configuring TCP/IP in winIDEA: manually or by automatic discovery.

Manual Configuration

Select the Hardware/Communication tab.

Hardware/Communication tab

Select the TCP/IP button and enter the IP Address and the TCP Port, as entered above into the Emulator. Connect the Emulator to the Ethernet, if not already connected, and click on the ‘Test’ button. The communication should be up and running.

Configuration with Automatic Discovery

Select the Hardware/Communication tab.

Display of discovered emulators

First, select ‘TCP/IP’ type of communication. Then select the ‘Use global discovery on UDP port 58371’.

In the pull-down window all emulators found on the network will be shown. The correct emulator can be identified by its serial number. Select the emulator and press the ‘Test’ button to ensure the communication is possible.


To be able to easier identify your own emulator, you can specify an unique port number in the first step (the number can be any number between 1024 and 65535, that is not already used on your network for other purposes – note that on the other hand more emulators can have the same port number), uncheck the ‘Use global discovery’ option, and enter the port number, if the correct one is not entered already.


Troubleshooting communication

Troubleshooting TCP/IP

If the communication test fails, there could be a problem with the IP Address, the Subnet Mask, the Default gateway address or the TCP Port.


First, make sure the Subnet Mask is correct. The subnet mask should be the same in the TCP/IP configuration of your computer and in the Emulator.


To find out the TCP/IP settings of your computer, open the command prompt and type ‘ipconfig’. The computer will return something like this:

Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :

       IP Address. . . . . . . . . . . . : 210.121.92.121

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . : 210.121.92.65

Enter the same Subnet Mask and the Default Gateway data into Emulator.

Next, make sure, the IP Address is not already used by any other device. The easiest way to do that is to disconnect the Emulator from the Ethernet, open a command prompt and type in ‘ping <ip_address>’ where <ip_address> is the IP Address selected when configuring the Emulator, in the above example you would type in ‘ping 210.121.92.92’ (without quotes). The result should be ‘Request timed out…’. If the result of the command is anything else (like ‘Reply from…’), the IP is already taken and you should choose another one. If the result is correct, type in ‘ping <ip_address>  -w 500 –t’, in the above example this would mean ‘ping 210.121.92.92 –w 500 –t’ . This command pings the IP address every 500 milliseconds until you stop it with Control+C. You should constantly receive the information ‘Request timed out’. Then, while the ping command is running, connect the Emulator and turn it on. Now, in a few moments, a ping reply should occur, in the form of ‘Reply from <ip_address>’… If this is not the case, the IP was set wrong. Try setting the IP again or select another one. If this is the case and the Emulator still cannot communicate with winIDEA, the TCP Port setting is wrong. Please select another port, set it up in the Emulator and in winIDEA and try again. When the ping is not more required, stop it using the keyboard shortcut Control+C.


If more Emulators are connected to the Ethernet and have the same IP set, only one will be active. Every Emulator must have a unique IP.

Troubleshooting the USB


During winIDEA installation USB driver is also installed. Very rarely after you power on the emulator which you connected to PC Windows show error:

“USB device not recognized”

If this error is displayed you should:

Check cable or use another USB cable.

Connect emulator to another USB port

Connect emulator to a different USB port. The one that resides on a PCI or PCIe card.

Connect emulator to a PC via powered USB switch. In case a PC (usually a laptop) cannot provide enough power over USB port.

Trace Line Calibration

Note: Trace Line Calibration is only available with iC6000 parallel trace DTM (IC60020).

Majority of the modern embedded microcontrollers providing trace functionality, implements a so called message based trace port, where an individual trace message is broadcasted off the microcontroller through a relatively narrow physical trace port in multiple CPU cycles, at frequencies, which can be well over 100 MHz. Typically, the trace port is combined from trace data lines and a trace clock line, which is used to sample trace data lines on rising, falling or both edges (depending on the individual implementation).


At lower frequencies and good signal integrity we can consider the clock and data lines as pure digital signals, which are correctly phase aligned. As such, the external trace tool can capture them accurately without any problems.


Nowadays, capturing of the valid trace data becomes more and more challenging due to the various signal integrity issues (noise, skew, crosstalk, reflections, ground bounce…), which are introduced either due to the high frequency trace clock & data, due to the bad target PCB design or a combination of both. THE IC6000 has the ability to compensate for these issues via Trace Line Calibration functionality, which allows shifting threshold voltage and clock phase at the capture time of the trace data. When Trace Line Calibration is performed, it auto scans over these two dimensions and searches for valid and invalid settings and finds an optimum data eye.

Example


Let’s assume we have a Cortex-M3 based NXP LPC1768 microcontroller running at 95 MHz. At this frequency, some of the signal integrity issues will show up for sure. After the debug download, the application should be run. Next, the “Start” button in the “Hardware/Tools/ Trace Line Calibration” should be pressed, which starts the auto-scan. After a couple of seconds, the result of the scan is collected and recommended “Vref” and “Phase“ values are provided. Typically, the user just needs to press the “->” button to use the recommended values (or, if desired, enter them manually) and finally use the Apply button.


Configuration part of the Trace Line Calibration dialog


Newly applied values are stored upon Save Workspace and also used on the next debug download.


The following picture shows the result of the Trace Line Calibration and the corresponding timing view of signals on the trace port.


Good signal integrity at lower frequency with large “Data eyes”



Trace Line Calibration window – scan has been performed and applied.


X

invalid area

.

valid area

R

recommended

o

currently used


Higher frequency: Valid “Data eyes” shown on upper data signal and how the clock (lower) must be delayed.


Trace Port PCB Design Guidelines

This section contains some guidelines, which should be considered during the target PCB design to ensure the correct operation of the trace port (ETM, Nexus,…) and the external trace tool (iC6000, iTRACE GT). Note that the quality and timing of the trace port signals to the external trace tool are critical for correct and reliable trace operation.

All trace port lines on the PCB should be as short as possible (max ~2,5 cm),

Traces should run on the same layer, or layers with the same impedance.

Preferred layer impedance is 50 Ohm.

Connector’s ground pins should be connected directly to PCB’s GND plane.

Trace clock should be serially terminated by 47 Ohm resistor as close as possible to the driver. The value of the resistor may be changed depending on driver characteristics.

Trace clock should be clean of crosstalk – if possible with double distance to closest nets.

Trace clock should have only point-to-point connection – any stubs should be avoided.

It is strongly recommended also for other (data) lines to be point-to-point only. If any stubs are needed, they should be as short as possible, when longer are required, there should be a possibility to optionally disconnect them (e.g. by jumpers).

Trace port data bus inner crosstalk is not so important, but it is critical to isolate the whole bus from other signals (including from the trace port clock).


The following examples show, how the length of the trace lines is reflected in signal integrity and consequently in functionality.  One of typical evaluation boards was used, where the CPU is located on the upper piggyback board, which fits to the lower, larger measurement board.



Trace lines with short stubs






Trace Line Calibration result


Measured by oscilloscope



Trace lines with longer stubs (over connector to other board)






Trace Line Calibration result


Measured by oscilloscope


Emulation Notes

Above message can occur when using trace. It indicates that the DDR (trace storage RAM) input FIFO, which accepts trace data from the system domain, has overflowed, and some portion of the trace data will be missing. It doesn’t mean any hardware failure. Possible solutions:

lower the target CPU clock

increase Nexus clock divider, which yields lower Nexus clock, but at the same time Nexus is more prone to overflows then

changing the trace port width e.g. from 16 bit to 12 bit or from 12 bit to 4 bit reduces the Nexus information bandwidth. Note that possible port size varies depending on the target CPU.




Aurora Interface – guidelines and electrical characteristics


On the iC6000 side, Aurora interface lines are connected directly to the FPGA implementing physical Aurora interface. These lines exhibit the following characteristics:

Aurora receive data lanes (AGBT_TX marked on the target side):

To ensure interoperability between drivers and receivers of different vendors, AC coupling at the receiver input is used. 100nF AC coupling capacitors for connection to the transmitter are used at Aurora receiver input pins.


Aurora transmit data lanes (AGBT_RX marked on the target side):

This direction is normally not applicable for Nexus trace operation. iC6000 has no AC coupling capacitors on these lines. They must be located on the target (receiver) side.


Aurora clock lane (AGBT_CLK marked on the target side):

100 nF AC coupling capacitors are located on CLK output to protect drivers from possibly getting shorted. Target side has usually its own AC coupling.


Below list contains some guidelines, which should be considered during the target PCB design to ensure the correct operation of the Aurora trace port connecting to the iC6000. Note that the quality and timing of the trace port signals to the external trace tool are critical for correct and reliable trace operation.

All trace port lines on the PCB should be as short as possible (max 2,5 cm),

Traces should run on the same layer, or layers with the same impedance.

Preferred layer impedance is 50 Ohm.

Samtec connector ground pins should be connected directly to PCB’s GND plane.

Trace clock should have only point-to-point connection – any stubs should be strictly avoided.

It is strongly recommended also for other (data) lines to be point-to-point only. If any stubs are needed, they should be as short as possible, when longer are required, there should be a possibility to optionally disconnect them (e.g. by jumpers).

Trace port data bus inner crosstalk is not so important, but it is critical to isolate the whole bus from other signals (including from the Aurora trace port clock).


Target Connection

Different high-speed Aurora cables are available depending on the specific target architecture and the target debug connector. They are used to connect iC6000 development and test system to the target.


Typically, iC6000 comes prebuilt with one of the available Aurora cables. User must specify target architecture at order time.

Note: AGBT stands for Aurora GigaBit Trace.

Signal direction definition used throughout this document:


O

- output from the debugger to the target microcontroller

I

- input to the debugger from the target microcontroller


22-pin High-speed Aurora cable

This cable is delivered under the IC60040-1 ordering code and is required to connect to Infineon Aurix (Tricore) based target with Samtec 22-pin debug connector.

Ordering code

IC60040-1

The development tool connects to the target via a 22-pin Samtec connector through which the iC6000 connects to the microntroller DAP or JTAG debug interface and Aurora trace port. A target should feature a matching part, for example, Samtec part number: ASP-137969-01 (Samtec Series ERF8, Rugged High Speed Socket)

Target connector placement

It’s recommended to position the connector in a way that even-numbered signals are located at the edge of the PCB. In this case, debug tool Aurora cable connects to the target connector without being twisted.


The following pinout is valid on the target side:


Signal direction

Signal

Pin

Pin

Signal

Signal direction

I

TX0+

1

2

VREF

I

I

TX0-

3

4

TCK / DAP0

O / O

Ground

GND

5

6

TMS / DAP1

O / IO


Not Connected

7

8

TDI

O


Not Connected

9

10

TDO

I

Ground

GND

11

12

~TRST

O


Not Connected

13

14

CLK+

O


Not Connected

15

16

CLK-

O

Ground

GND

17

18

TGO

I


Not Connected

19

20

Not Connected

O


Not Connected

21

22

~PORST

IO

Samtec 22-pin AGBT target pinout

Blue colored signals are Aurora trace signals.


Besides the 22-pin Samtec connector featuring debug interface and Aurora trace port, the target can also feature a standard 10-pin DAP or 16-pin JTAG target debug connector, exposing only the debug interface without Aurora trace port. iC6000 can connect to this connector via a small adapter connecting at the end of the High-speed Aurora cable. Note that there is a different iC6000 DTM module for DAP and JTAG debug interface.

Infineon 10-pin DAP

An adapter (ordering code IASAM22TRICOREPIN10) must be ordered separately in order to connect to the target featuring 10-pin 1.27mm pitch target debug connector. This adapter can be used only in conjunction with the iC6000 DTM Aurora/DAP module (IC60023-1).

Ordering code

IASAM22TRICOREPIN10




IASAM22TRICOREPIN10

The following pinout is valid on the target side:


Signal direction

Signal

Pin

Pin

Signal

Signal direction

I

VREF

1

2

TMS / DAP1

O / IO

Ground

GND

3

4

TCK / DAP0

O / O

Ground

GND

5

6

TDO

I


Not Connected

7

8

~TRST

O

Ground

GND

9

10

~PORST

IO

10-pin Infineon DAP pinout

Infineon 16-pin JTAG

An adapter (ordering code IASAM22TRICOREPIN16) must be ordered separately in order to connect to a target featuring 16-pin 2.54mm pitch target debug connector. This adapter can be used only in conjunction with the iC6000 DTM Aurora/JTAG module (IC60022-1).



Ordering code

IASAM22TRICOREPIN16




IASAM22TRICOREPIN16

The following pinout is valid on the target side:


Signal direction

Signal

Pin

Pin

Signal

Signal direction

O / IO

TMS / DAP1

1

2

VREF

I

I

TDO

3

4

GND

Ground


Not Connected

5

6

GND

Ground

O

TDI

7

8

~PORST

IO

O

~TRST

9

10

Not Connected


O / O

TCK / DAP0

11

12

GND

Ground


Not Connected

13

14

Not Connected



Not Connected

15

16

Not Connected


16-pin Infineon JTAG target pinout


34-pin High-speed Aurora cable

This cable is delivered under the IC60041-1 ordering code and is required to connect to Freescale MPC57xx or ST SPC57 based target providing Samtec 34-pin debug connector.

Ordering code

IC60041-1

The development tool connects to the target via 34-pin Samtec connector. A target should feature a matching part, for example, Samtec part number: ASP-137973-01 (Samtec Series ERF8, Rugged High Speed Socket)

Target connector placement

It’s recommended to position the connector in a way that even-numbered signals are located at the edge of the PCB. This way, the debug tool Aurora cable connects to the target connector without being twisted.


The following pinout is valid on the target side:


Signal direction

Signal

Pin

Pin

Signal

Signal direction

I

AGBT TX_P0

1

2

VREF

I

I

AGBT TX_N0

3

4

TCK

O

Ground

GND

5

6

TMS

O


AGBT TX_P1

7

8

TDI

O


AGBT TX_N1

9

10

TDO

I

Ground

GND

11

12

~JCOMP

O


AGBT TX_P2

13

14

Not Connected



AGBT TX_N2

15

16

~EVTI0

O (not used)

Ground

GND

17

18

~EVTO0

I


AGBT TX_P3

19

20

~PORST

O


AGBT TX_N3

21

22

ESR0

IO

Ground

GND

23

24

GND

Ground


Not Connected

25

26

AGBT CLK_P

O


Not Connected

27

28

AGBT CLK_N

O

Ground

GND

29

30

GND

Ground


Not Connected

31

32

Not Connected



Not Connected

33

34

Not Connected


Samtec 34-pin AGBT target pinout

Blue colored signals are Aurora trace signals.


~JCOMP is an optional pin. Some microcontrollers don’t have this pin. Internally, this is actually JTAG TRST

which resets JTAG TAP state machine. Because JTAG TAP state machine can be reset also by TMS and TCK,

this pin is optional also for the debugger. If microcontroller has JCOMP pin but it is not connected to the target

debug connector then it must be set to non-active state in the target via a pull-up resistor. If not, then JTAG TAP

state machine remains in reset and debugging is not possible.

Besides the 34-pin Samtec connector featuring debug interface and Aurora trace port, the target can also feature a standard 14-pin JTAG target debug connector, exposing only the debug interface without Aurora trace port. iC6000 can connect to this connector via a small adapter connecting at the end of the High-speed Aurora cable.

Freescale/ST 14-pin JTAG

An adapter (ordering code IASAM34MPCPIN14) must be ordered separately in order to connect to a target featuring 14-pin 2.54mm pitch target debug connector. This adapter can be used only in conjunction with the iC6000 DTM Aurora/JTAG module (IC60022-1).


Ordering code

IASAM34MPCPIN14




IASAM34MPCPIN14

The following pinout is valid on the target side:


Signal direction

Signal

Pin

Pin

Signal

Signal direction

O

TDI

1

2

GND

Ground

I

TDO

3

4

GND

Ground

O

TCK

5

6

GND

Ground

O (not used)

~EVTI0

7

8

~PORST

O

IO

ESR0

9

10

TMS

O

I

VREF

11

12

GND

Ground


Not Connected

13

14

~JCOMP

O

14-pin Freescale/ST target pinout

Mandatory pins on the microcontroller side are GND, VDD, RESET, TMS, TDI, TDO and TCK.


~JCOMP is an optional pin. Some microcontrollers don’t have this pin. Internally, this is actually JTAG TRST which resets JTAG TAP state machine. Because JTAG TAP state machine can be reset also by TMS and TCK, this pin is optional also for the debugger. If microcontroller has JCOMP pin but it is not connected to the target debug connector then it must be set to non-active state in the target via a pull-up resistor. If not then JTAG TAP state machine remains in reset and debugging is not possible.


Notes:

Notes:



EU Declaration of Conformity (DoC)



We

iSYSTEM AG für Informatiksysteme

Carl-Zeiss-Str. 1

85247 Schwabhausen

Germany



declare that the DoC is issued under our sole responsibility and belongs to the following product:

Blue Box - debugger and analyzer solution

Type: iC3000, iC5000, iC5500, iC5700, iC6000, iTAG.2K



Identification allowing traceability:

Object of the declaration is identified by a product type and unique serial number for each individual device.



The object of declaration described above is in conformity with the relevant Union harmonization legislation:

EMC directive 2014/30/EU and RoHS directive 2011/65/EU


The following harmonized standards and technical specifications have been applied:

EN 55032: 2010

EN 55024: 2010

EN 61000 - 3 - 2: 2014

EN 61000 - 3 - 3: 2013


Signed for and on behalf of:



Schwabhausen, 21. March 2017



iSYSTEM AG f. Informatiksysteme - Carl-Zeiss-Str. 1 - 85247 Schwabhausen - USt-IdNr. DE128231221

Vorstand: Erol Simsek, Werner Fischer, Martin Gröstenberger - AG: München HRB 148751 - St-Nr.: 115/120/30027

Bank: Sparkasse Dachau BLZ 70051540 Account 904045 - IBAN: DE82700515400000904045 - BIC: BYLADEM1DAH

Troubleshooting

It is highly recommended to read the technical notes document for your specific microcontroller family before contacting iSYSTEM technical support. This document can be downloaded from www.isystem.com but typically it comes delivered with the development system. It contains all the information related to the debugging including some troubleshooting tips.
















Operating Environment:

Operating temperature:  between 10°C and 40°C

Humidity: 5% to 80% RH

Storage temperature:  between -10°C and 60°C


Dimensions: 155 x 160 x 55 mm


Note: Consult with iSYSTEM when using equipment outside of these parameters.




















Disclaimer: iSYSTEM assumes no responsibility for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time without notice, and does not make any commitment to update the information herein.

© iSYSTEM. All rights reserved.