IC6000 V1.4

_
V1.4
Hardware Reference
iC6000 On-Chip Analyzer
with Aurora protocol support
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  2014 iSYSTEM, AG.
All rights reserved.
All trademarks are property of their respective owners.
www.isystem.com
 iSYSTEM, December 2014
1/12
iC6000 Base Unit
Ordering code
IC60000
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.
 iSYSTEM, December 2014
2/12
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.
 iSYSTEM, December 2014
3/12
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
at ordering. The DTM module features protection and minimal electronic logic adjusting iC6000 to a specific
target microcontroller debug interface. This allows iC6000 base unit being universal for all target architectures
featuring Aurora 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
This module supports JTAG debug interface for Infineon Aurix (Tricore) family, Freescale MPC57xx devices
and ST SPC57 devices.
 iSYSTEM, December 2014
4/12
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 iC6000 is to be connected to the JTAG debug interface,
iC6000 DTM Aurora/JTAG module is required and when connecting to the DAP, iC6000 DTM Aurora/DAP
module is required. Note that iC6000 DTM modules are not meant to be exchanged by the user. Appropriate
DTM module must be ordered at order time.
 iC6000 DTM Aurora/DAP (TriCore)
Ordering code
IC60023
This module supports Infineon 2-pin and 3-pin (Wide Mode) DAP debug interface for Infineon Aurix (Tricore)
family.
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.
 iSYSTEM, December 2014
5/12
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 [email protected].
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.
 iSYSTEM, December 2014
6/12
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
I
- output from the debugger to the target microcontroller
- input to the debugger from the target microcontroller
 iSYSTEM, December 2014
7/12
 22-pin High-speed Aurora cable
This cable is delivered under the IC60040 ordering code and is required to connect to Infineon Aurix (Tricore)
based target with Samtec 22-pin debug connector.
Ordering code
IC60040
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
I
I
Ground
Ground
Ground
Signal
TX0+
TX0GND
Not Connected
Not Connected
GND
Not Connected
Not Connected
GND
Not Connected
Not Connected
Pin
1
3
5
7
9
11
13
15
17
19
21
Pin
2
4
6
8
10
12
14
16
18
20
22
Signal
VREF
TCK / DAP0
TMS / DAP1
TDI
TDO
~TRST
CLK+
CLKTGO
Not Connected
~PORST
Signal direction
I
O/O
O / IO
O
I
O
O
O
I
O
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 Highspeed 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).
 iSYSTEM, December 2014
8/12
Ordering code
IASAM22TRICOREPIN10
IASAM22TRICOREPIN10
The following pinout is valid on the target side:
Signal direction
I
Ground
Ground
Ground
Signal
VREF
GND
GND
Not Connected
GND
Pin
1
3
5
7
9
Pin
2
4
6
8
10
Signal
TMS / DAP1
TCK / DAP0
TDO
~TRST
~PORST
Signal direction
O / IO
O/O
I
O
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).
Ordering code
IASAM22TRICOREPIN16
IASAM22TRICOREPIN16
The following pinout is valid on the target side:
Signal direction
O / IO
I
O
O
O/O
Signal
TMS / DAP1
TDO
Not Connected
TDI
~TRST
TCK / DAP0
Not Connected
Not Connected
Pin
1
3
5
7
9
11
13
15
Pin
2
4
6
8
10
12
14
16
Signal
VREF
GND
GND
~PORST
Not Connected
GND
Not Connected
Not Connected
Signal direction
I
Ground
Ground
IO
Ground
16-pin Infineon JTAG target pinout
 iSYSTEM, December 2014
9/12
 34-pin High-speed Aurora cable
This cable is delivered under the IC60041 ordering code and is required to connect to Freescale MPC57xx or ST
SPC57 based target providing Samtec 34-pin debug connector.
Ordering code
IC60041
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
I
I
Ground
Ground
Ground
Ground
Ground
Signal
AGBT TX_P0
AGBT TX_N0
GND
AGBT TX_P1
AGBT TX_N1
GND
AGBT TX_P2
AGBT TX_N2
GND
AGBT TX_P3
AGBT TX_N3
GND
Not Connected
Not Connected
GND
Not Connected
Not Connected
Pin
1
3
5
7
9
11
13
15
17
19
21
23
25
27
29
31
33
Pin
2
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
Signal
VREF
TCK
TMS
TDI
TDO
~JCOMP
Not Connected
~EVTI0
~EVTO0
~PORST
ESR0
GND
AGBT CLK_P
AGBT CLK_N
GND
Not Connected
Not Connected
Signal direction
I
O
O
O
I
O
O (not used)
I
O
IO
Ground
O
O
Ground
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.
 iSYSTEM, December 2014
10/12
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).
Ordering code
IASAM34MPCPIN14
IASAM34MPCPIN14
The following pinout is valid on the target side:
Signal direction
O
I
O
O (not used)
IO
I
Signal
TDI
TDO
TCK
~EVTI0
ESR0
VREF
Not Connected
Pin
1
3
5
7
9
11
13
Pin
2
4
6
8
10
12
14
Signal
GND
GND
GND
~PORST
TMS
GND
~JCOMP
Signal direction
Ground
Ground
Ground
O
O
Ground
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.
 iSYSTEM, December 2014
11/12
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.
 iSYSTEM, December 2014
12/12

Download Report