iSystem iC5000 Application guide

_ V3.2
Hardware Reference
iC5000 On-Chip Analyzer
iSYSTEM, January 2012 1/41
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 2012 iSYSTEM, GmbH.
All rights reserved.
All trademarks are property of their respective owners.
www.isystem.com

iSYSTEM, January 2012 2/41
iC5000 Base Unit
The iC5000 base unit is the heart of the iC5000 on-chip emulation system.
There are three status LEDs on the iC5000 Base Unit. The status 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.
Powering the emulator
A round 3-pin power connector is located on the rear of the iC5000 base unit.
Power connector pinout, view from the rear of the Emulator
The iC5000 unit accepts a wide input voltage range from 12V to 24V DC, thus enabling the Emulator to work
also with a 12V or 24V car battery. The necessary power supply is delivered beside the iC5000 unit.
Note: Use only original iSYSTEM accessories for powering the iC5000. If you wish to use a power supply
different from the delivered one, please consult with iSYSTEM first.
Ordering code IC50000 or IC50000-1

iSYSTEM, January 2012 3/41
iC5000 Debug/Trace Module (JTAG/BDM)
iC5000 Base Unit in conjunction with the iC50020 Debug/Trace module is a universal on-chip emulation
platform. Additionally, a connecting cable (40-pin flat cable), a target specific cable adapter and architecture
specific license is required to debug the target based on a specific architecture.
Valid input voltage range for all debug signals is between 1.8 - 5.5V
Note: Typically, IC50000 and IC50020 module already come assembled together when delivered to the user.
The user only needs to connect a specific cable adapter via 40-pin flat cable, through which then the
development system connects to the target.
iC5000 Development system for Cortex-M3 based target including also optional IO module
Ordering code IC50020

iSYSTEM, January 2012 4/41
40-pin flat cable used to connect architecture specific debug cable adapters to the iC5000 Debug/Trace module.
16-bit Nexus (IC50152) and 16-bit ETM (IC50115) cable adapters come with two flat cables (30-pin and 40-pin)
pre-attached. With these, 40-pin flat cable, which is shipped next to the Debug/Trace module (IC50020), is not
required. Note that these two debug cable adapters require iC5000 Debug/Trace module revision D or newer.
Note that they cannot be connected to the older revisions.
iC5000 I/O Module (IOM2)
• System Port: inter-emulator synchronization and 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. (Available on rev. C and later)
• Analog outputs: 2 channels, 8-bit DACs, ±4.5V bipolar output, ±7mA drive, 100ohm output resistance.
• Optional 10MHz temperature compensated precision oscillator TCXO for a high accuracy long duration
trace/analyzer session measurements.
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.
Ordering code IC50011

iSYSTEM, January 2012 5/41
The maximum voltage on the Current Sense probe is 60V.
Nominal sampling rate is 1MSPS.
Connectors
iC5000 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 (rev. C and later).
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.

iSYSTEM, January 2012 6/41
Using grounding wire
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 iC5000 connects to the PC through the USB port
Connecting a dedicated grounding wire, which is shipped with the iC5000 unit, between the iC5000 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 iC5000
development system features already a high quality protection on all connecting signals by default.
iC5000 with the grounding wire and the ground pin in the left bottom corner

iSYSTEM, January 2012 7/41
The grounding wire connecting the target and iC5000
Licenses
iC5000 introduces a new licensing model. 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
[e-mail].
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. Make sure that the target debug connector to which ic5000 system connects, exposes
microcontroller trace port (ETM, Nexus, …) when trace functionality is required.
iSYSTEM development tools feature a hardware based license scheme, which saves costs comparing to per-seat
based licenses. All licenses are kept in the iC5000 development system, which conveniently allows moving
iC5000 unit from one development seat to another.
When new iC5000 system is shipped from iSYSTEM, CPU architecture and trace licenses are preprogrammed
by the iSYSTEM test department. With such a new system, only winIDEA license needs to be requested from
iSYSTEM after receiving the iC5000 system. Additional CPU architecture license, which are purchased later,
must be programmed by the user.
Below picture shows the sticker, which can be found on iC5000 system, identifying which CPU architecture
licenses were preprogrammed by the iSYSTEM test department. Below picture shows preprogrammed Cortex-
M3 and MPC56xx licenses.

iSYSTEM, January 2012 8/41
Communication
iC5000 supports two types of communication: 10/100M Ethernet and USB 1.1/2.0. It is recommended to use
USB2.0 interface since it provides the fastest transfer from the iC5000 development system to the PC where
winIDEA IDE runs. This will guarantee a maximum performance of the iC5000 development system.
Specify the communication port through which the iC5000 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 prompt you for the driver for it. Specify the path to the
USB directory in the winIDEA installation directory or the distribution CD. If only one emulator is
connected to a PC via USB then 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 communication settings.
•TCP/IP – This option sets the TCP/IP properties of the iC5000. 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

iSYSTEM, January 2012 9/41
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 an alternate option – either through the serial port, through the parallel
port or through USB. 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.
If you want winIDEA to use these settings, press the “Use this communication settings” button. Then, close the
System configuration window.
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.

iSYSTEM, January 2012 10/41
Second step: Configuring
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
If the “Use this communication settings” button was used when configuring the Emulator, these settings should
already be set as required. If this option was not used, 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.

iSYSTEM, January 2012 11/41
Display of discovered emulators
First, select ‘TCP/IP’ type of communication. Then select the ‘Use global discovery on UDP port 58371’ and
press the Refresh button.
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 (for
example, as shown above, 23456; 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, enter the port number, if the correct one is not entered
already, and press the refresh button. Now, only the emulators on the network that use this port will be shown.
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.

iSYSTEM, January 2012 12/41
Trace Line Calibration
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. IC5000 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.

iSYSTEM, January 2012 13/41
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.

iSYSTEM, January 2012 14/41
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 (iC5000, 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.
•Mictor 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

iSYSTEM, January 2012 15/41
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.
•IC50000-1 (ordering code) has higher trace storage bandwidth than IC50000.

iSYSTEM, January 2012 16/41
Debug Cable Adapters
Various cable adapters are available depending on the specific target architecture and the target debug connector.
They are used to connect iC5000 development system to the target.
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
•20-pin 2.54mm Cortex Debug Cable Adapter
This adapter is delivered under the IC50111 ordering code. Note that another adapter comes along under this
ordering code and that is 20-pin 2.54mm ARM Cable Adapter.
Ordering code IC50111
This adapter is used to connect the iC5000 development system to the Cortex-M3 based target. It connects to
Debug/Trace module (IC50020) on one side and to the target debug connector on the other side. It can be used
for targets featuring 20-pin 2.54 pitch target debug connector with Cortex-M3 pinout.
The following pinout is valid on the target side:
Signal
direction
Signal description
Signal Pin
Pin Signal Signal description
Signal
direction
I Reference voltage
VTref 1 2 SWDIO/TMS
SWD/JTAG I/O
Ground GND 3 4 SWCLK/TCK
SWD/JTAG O
Ground GND 5 6 SWO/TDO SWD/JTAG I
Ground GND 7 8 NC/TDI SWD/JTAG O
Ground GND 9 10 nSRST System Reset I/O
Ground GND 11
12 TRCLK Trace Clock I
Ground GND 13
14 TRD0 Trace Data 0 I
Ground GND 15
16 TRD1 Trace Data 1 I
Ground GND 17
18 TRD2 Trace Data 2 I
Ground GND 19
20 TRD3 Trace Data 3 I
20-pin Cortex-M3 pinout
Note: 20-pin 2.54mm Cortex-M3 Cable Adapter features resettable fuses on pins 1, 2, 4, 6, 8 and 10. These
protect debug signals against overcurrent. These fuses cycle back to a conductive state after the excessive current
fades away.

iSYSTEM, January 2012 17/41
•20-pin 2.54mm ARM Cable Adapter
This adapter is delivered under the IC50111 ordering code. Note that another adapter comes along under this
ordering code and that is 20-pin 2.54mm Cortex-M3 Cable Adapter.
Ordering code IC50111
This adapter is used to connect the iC5000 development system to the Cortex-M3 or ARM7/ARM9 based target.
It connects to Debug/Trace module (IC50020) on one side and to the target debug connector on the other side. It
can be used for targets featuring 20-pin 2.54 pitch target debug connector with ARM pinout.
The following pinout is valid on the target side:
Signal
direction
Signal description Signal Pin
Pin
Signal
Signal description Signal
direction
I Reference voltage VTref 1 2 NC Not Connected
O Debug JTAG nTRST 3 4 GND Ground
O Debug JTAG TDI 5 6 GND Ground
O Debug JTAG TMS 7 8 GND Ground
O Debug JTAG TCK 9 10
GND Ground
I Return TCK RTCK 11
12
GND Ground
I Debug JTAG TDO 13
14
GND Ground
I/O System Reset nSRST 15
16
GND Ground
O Debug request DBGRQ 17
18
GND Ground
I Debug Acknowledge
DBACK 19
20
GND Ground
20-pin ARM pinout
Note: 20-pin 2.54mm ARM Cable Adapter features resettable fuses on all pins except for pin 11 and 19. These
fuses protect debug signals against overcurrent and cycle back to a conductive state after the excessive current
fades away.

iSYSTEM, January 2012 18/41
Texas Instruments Microcontrollers
Note that targets based on Texas Instruments (TI) ARM microcontroller may feature Texas Instruments ARM
14-pin target debug connector with TI proprietary pinout.
A dedicated adapter is available for Texas Instruments ARM 14-pin pinout and can be ordered separately under
IAPIN20ARM14TI ordering code. Make sure you don’t mix up Texas Instruments pinout with standard 14-pin
2.54mm ARM pinout (cable adapter IC50112).
Double check the pinout of the target debug connector with the iC5000 cable adapter pinout before connecting
iC5000 to the target for the first time.
Ordering code IAPIN20ARM14TI
With this adapter, the following pinout is valid on the target side:
Signal
direction
Signal description Signal Pin
Pin
Signal
Signal description Signal
direction
Output Standard JTAG TMS 1 2 nTRST
Standard JTAG Output
Output Standard JTAG TDI 3 4 GND Ground
Input Reference voltage VTref 5 6 n.c. Not connected
Input Standard JTAG TDO 7 8 GND Ground
Input Return TCK RTCK 9 10
GND Ground
Output Standard JTAG TCK 11 12
GND Ground
Input Debug Acknowledge
BERR 13 14
nSRST
System Reset In/Out
ARM7 14-pin TI target connector
A jumper is present on the adapter. If this jumper is set, the SYSTEM RESET line is connected to pin 14 on the
target side. If SYSTEM RESET is not needed, then this jumper should be removed.

iSYSTEM, January 2012 19/41
•14-pin 2.54mm ARM Cable Adapter
Ordering code IC50112
IC50112 ARM Cable Adapter is used to connect the iC5000 development system to the ARM7/ARM9 based
target. It connects to Debug/Trace module (IC50020) on one side and to the target debug connector on the other
side. It can be used for targets featuring 14-pin 2.54 pitch target debug connector with ARM pinout.
The following pinout is valid on the target side:
Signal
direction
Signal description Signal Pin
Pin
Signal
Signal description Signal
direction
Not Connected NC 1 2 GND Ground
O Debug JTAG nTRST 3 4 GND Ground
O Debug JTAG TDI 5 6 GND Ground
O Debug JTAG TMS 7 8 GND Ground
O Debug JTAG TCK 9 10
GND Ground
I Debug JTAG TDO 11
12
nSRST
System Reset I/O
I Reference voltage VTref 13
14
GND Ground
14-pin ARM pinout
Note: 14-pin 2.54mm ARM Cable Adapter features resettable fuses on all pins. These fuses protect debug
signals against overcurrent and cycle back to a conductive state after the excessive current fades away.

iSYSTEM, January 2012 20/41
•20-pin 1.27mm Cortex Debug Cable Adapter
Ordering code IC50113
IC50113 Cortex-M3 Adapter Board is used to connect the iC5000 development system to the Cortex-M3 based
target. It connects to Debug/Trace module (IC50020) on one side and to the target debug connector on the other
side. It can be used for targets featuring 20-pin 1.27mm pitch target debug connector with Cortex-M3 pinout.
The following pinout is valid on the target side:
Signal
direction
Signal description
Signal Pin
Pin Signal Signal description
Signal
direction
I Reference voltage
VTref 1 2 SWDIO/TMS
SWD/JTAG I/O
Ground GND 3 4 SWCLK/TCK
SWD/JTAG O
Ground GND 5 6 SWO/TDO SWD/JTAG I
Ground GND 7 8 NC/TDI SWD/JTAG O
Ground GND 9 10 nSRST System Reset I/O
Ground GND 11
12 TRCLK Trace Clock I
Ground GND 13
14 TRD0 Trace Data 0 I
Ground GND 15
16 TRD1 Trace Data 1 I
Ground GND 17
18 TRD2 Trace Data 2 I
Ground GND 19
20 TRD3 Trace Data 3 I
20-pin Cortex-M3 pinout
Note: 20-pin 1.27mm Cortex-M3 Cable Adapter features resettable fuses on pins 1, 2, 4, 6, 8 and 10. These
protect debug signals against overcurrent and cycle back to a conductive state after the excessive current fades
away. Signals on pins 12, 14, 16, 18 and 20 are protected via 47 ohm serial resistors.