NXP Semiconductors S32 User manual

NXP Semiconductors Document Number: S32DBGUG
User Guide Rev. 1, 10/2018
S32 Debug Probe User Guide
by: NXP Semiconductors

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
2
Contents
Chapter 1 Introducing S32 Debug Probe ....................................................... 4
1.1 What is S32 Debug Probe?.......................................................................................................4
1.1.1 Product highlights...............................................................................................................................5
1.1.2 Debugging environment......................................................................................................................6
1.1.3 S32 Debug Probe benefits..................................................................................................................6
1.1.4 Target connections.............................................................................................................................6
1.2 Operating requirements ............................................................................................................6
1.2.1 Standard electrostatic precautions......................................................................................................6
1.2.2 Operating temperature........................................................................................................................7
1.2.3 Electrical requirements .......................................................................................................................7
1.3 Related documentation..............................................................................................................9
Chapter 2 Connecting to Network ................................................................ 10
2.1 Connecting S32 Debug Probe to network.............................................................................10
2.2 Customizing S32 Debug Probe............................................................................................11
2.3 Testing network communication...........................................................................................13
Chapter 3 Connecting to Target System...................................................... 14
3.1 Debug port connector information........................................................................................14
3.2 Connecting to target system ................................................................................................14
3.2.1 Connecting probe tip to target............................................................................................................15
Chapter 4 Using S32 Debug Probe............................................................... 21
4.1 Debugging with S32 Debug Probe system...............................................................................21
4.1.1 Run/Pause/Mixed mode states......................................................................................................21
4.2 Accessing S32 Debug Probe Remotely ...................................................................................23
Chapter 5 Hardware Specifications.............................................................. 24
5.1 LEDs on S32 Debug Probe..................................................................................................24
5.1.1 Transmit/Receive indicator............................................................................................................25
5.1.2 Run/Pause indicator......................................................................................................................25
5.1.3 RJ45 Ethernet connector with link and activity indicators...............................................................26
5.2 Host connectors on S32 Debug Probe .................................................................................26
5.2.1 RJ45 Ethernet connector ..............................................................................................................27
5.2.2 USB connector .............................................................................................................................27
5.3 Target connectors on S32 Debug Probe...............................................................................27

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
3
5.3.1 Probe tip connector.......................................................................................................................28
5.3.2 Electrical characteristics................................................................................................................28
5.3.3 Physical considerations.................................................................................................................28
Chapter 6 S32 Debug Probe Setup Utility Commands................................ 30
6.1 Connecting to S32 Debug Probe setup utility........................................................................30
6.2 S32 Debug Probe setup utility commands and variables.......................................................30
6.2.1 Commands to configure communications......................................................................................31
6.2.2 Commands to troubleshoot communication...................................................................................32
Chapter 7 Network Administration ............................................................... 35
7.1 S32 Debug Probe network ports..............................................................................................35
7.2 Configuring S32 Debug Probe using netparam....................................................................35
7.2.1 Configuring dynamic IP address....................................................................................................36
7.2.2 Configuring static IP address.........................................................................................................36
7.2.3 Static routing.................................................................................................................................37
7.2.4 Changing existing route entry........................................................................................................37
7.2.5 Entering static routes.....................................................................................................................37
7.3 Using CCS to search for S32 Debug Probes .......................................................................38
7.3.1 Sample output...............................................................................................................................39
Chapter 8 S32 Debug Probe Firmware.......................................................... 40
8.1 Boot loader ........................................................................................................................40
8.1.1 Operating system..........................................................................................................................40
8.1.2 Shell software ...............................................................................................................................40
8.2 Reprogramming S32 Debug Probe firmware images............................................................40
8.2.1 Reprogramming Firmware through Ethernet Port...........................................................................44
Chapter 11 Arm®CoreSight™Connector Information ................................ 45
Chapter 12 Troubleshooting ......................................................................... 57
12.1 Troubleshooting communication problems...........................................................................57
12.1.1 Verify network communication.......................................................................................................57
12.1.2 View network connections.............................................................................................................58
12.2 Troubleshooting power problems........................................................................................58
Index............................................................................................................... 59

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
4
Introducing S32 Debug Probe
What is S32 Debug Probe?
Chapter 1
Introducing S32 Debug Probe
The S32 Debug Probe allows your personal computer to communicate with NXPautomotivemicrocontrollersand processors
via JTAG debug connection.
CAUTION
The S32 Debug Probe contains components that are subject to damage from electrostatic
discharge. Whenever you are using, handling, or transporting the S32 Debug Probe, or
connecting to or disconnecting from a target system, always use proper anti-static protection
measures, including static-free bench pads and grounded wrist straps.
This chapter explains:
•What is S32 Debug Probe? on page 4
•Operating requirements on page 6
•Related documentation on page 9
1.1 What is S32 Debug Probe?
The S32 Debug Probe uses advanced emulation technology to provide control and visibility into your target embedded
system.
CombinedwithS32 Design Studio, the S32 Debug Probe speeds thedebuggingprocess byletting youinteractivelycontrol
and examine the state of your target system.
The basic S32 Debug Probe system is composed of two parts:
•The S32 Debug Probe, which provides visibility into and control of your target system using a JTAG interface and
connects to your host computer through either USB or Ethernet.
•Arm 10 pin or 20 pin probe tip, which is designed to provide a physical and electrical interface to the target system
processor that you want to gain visibility into.

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
5
Introducing S32 Debug Probe
What is S32 Debug Probe?
Figure 1. S32 Debug Probe
1.1.1 Product highlights
This section lists the S32 Debug Probe features.
The S32 Debug Probe has these features:
•Supports NXP automotive microcontrollers and processors. Go to the nxp.com/S32debugprobe for the latest supported
NXP processors
•Supports all CPU core speeds
•Allows you to control and debug software running in-target, with minimal intrusion into the target system operation
•Allows you to debug code in cache, ROM, RAM, and flash memory
•Supports 10/100 Ethernet network connection
•Supports USB 2.0 high-speed connection
•USB powered
•Supports both big and little endian byte-order
•Software debug capabilities, usually part of host software like S32 Design Studio, include:
•Control instruction execution

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
6
Introducing S32 Debug Probe
•Display and modify target system memory
•Examine and modify any processor registers
•Run to breakpoints in ROM, RAM, or flash memory
•Single-step through source and assembly language code views
•Step into, over, or out of functions
•Collect and analyze real-time data
•Perform boundary scan testing with support from correct host-level software
•Program all onboard memories with support from correct host-level software
1.1.2 Debugging environment
The S32 Debug Probe works with the S32 debugger to give you control over the emulation functions and your target
system.
1.1.3 S32 Debug Probe benefits
The S32 Debug Probe provides these key benefits:
•Visibility: Allows you to observe registers and the current state of target system memory. You can halt program
execution at predefined states and examine the data for a particular program state.
•Control: Enables you to control the state of the target system by downloading code, manually modifying
processor registers and memory, single-stepping through the code, or setting breakpoints.
1.1.4 Target connections
The S32 Debug Probe connects to your target through the standard debug port for the processor family, and supports a
single target connection, based on the connected probe tip.
For details on processor list, go to nxp.com/S32debugprobe.
For information on connecting to a target, see Connecting to target system topic.
1.2 Operating requirements
Before setting up the system, ensure that the operating environment is prepared.
1.2.1 Standard electrostatic precautions
This instrument contains static-sensitive components that are subject to damage from electrostatic discharge.
Use standard precautions when transporting, handling, or using the instrument and the target, when
connecting/disconnecting the instrument and the target, and when removing the cover of the instrument.
It is recommended that you use the following precautions:
•Use wrist straps or heel bands with a 1Mohm resistor connected to ground.
•On the work surface and floor, use static conductive mats with a 1Mohm resistor connected to ground.

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
7
Introducing S32 Debug Probe
Operating requirements
•Keep high, static-producing items, such as non-ESD-approved plastics, tape, and packaging foam away from the
instrument and the target.
The above precautions should be considered as minimum requirements for a static-controlled environment.
1.2.2 Operating temperature
This section contains the operating temperature considerations for the S32 Debug Probe. For operating temperature of the S32
Debug Probe, see Physical considerations topic.
1.2.3 Electrical requirements
The S32 Debug Probe can be powered through a USB cable and does not require an external power supply.
It is designed to be plugged directly into a host computer, but can also work with self-powered hubs. For details on Bus-
powered hubs, seeElectrical characteristics topic. If your hub is not able to provide sufficient power, connect the S32 Debug
Probe directly to your host PC, or purchase a self-powered USB hub.
If you only plan to use Ethernetcommunications, the S32 Debug Probe can bepowered from theexternal powersupply
provided with your unit. It can use line voltages of 100-240 VAC (50/60 Hz).
NOTE
It is recommended to use a surge protector between the power supply and AC power.
1.2.3.1 Connecting power supply cable
This section explains how to connect the USB cable to the connector on the S32 Debug Probe.
Connect the power supply connector to the USB connector on the S32 Debug Probe as shown below.
CAUTION
Connect only the provided powersupply to the S32 Debug Probe. Other power supplies may look
similar, but can damage the probe if the supply specifications differ from the required specifications.

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
8
Introducing S32 Debug Probe
Figure 2. S32 Debug Probe with USB connector
1.2.3.2 Cycling power to system
When you need to apply or cycle power to the S32 Debug Probe, connect or disconnect the power cable from the
power source or from the probe.
After you have connected the probe to your target system, use the following sequence for applying or removing the power.
To turn the power on:
1. Turn on the S32 Debug Probe power.
2. Turn on the target system power.
To turn the power off:
1. Turn off the target system power.
2. Turn off the S32 Debug Probe power.

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
9
Introducing S32 Debug Probe
Related documentation
1.3 Related documentation
The S32DS documentation explains how to install and configure the S32DS IDE and debugger and use the S32
Debug Probe.

Connecting to Network
S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
10
Connecting S32 Debug Probe to network
Chapter 2
Connecting to Network
This chapter describes how to connect the S32 Debug Probe to an existing TCP/IP network.
The S32 Debug Probe is a device that may be configured for either using to acquire its IP configuration (the default method)
or through a static IP configuration.
This chapter explains:
•ConnectingS32 Debug Probe to network
•Customizing S32 Debug Probe
•Testing network communication
2.1 Connecting S32 Debug Probe to network
The S32Debug Probe’s default operation is to acquire its network configuration automatically using DHCPand attempt to
register its hostname with a name server.
The factory assigned host name is FSLXXYYZZ where XXYYZZ is the last three octets of the MAC address, provided on a
label on the bottom side of the probe. For example, if the probe's MAC address is 00:04:9f:00:77:31, the host name will be
FSL007731. The S32 Debug Probe can connect directly to a network using Ethernet (10/100BaseT) cables. To connect to
the Ethernet interface:
1. Plug one end of the supplied RJ45 cable (p/n 600-75499) into the RJ45 connector of the S32 Debug Probe.
Figure 3. S32 Debug Probe with Ethernet connector

Connecting to Network
S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
11
Connecting S32 Debug Probe to network
2. Connect the other end of the RJ45 cable into the RJ45 connector of the Ethernet network or host computer.
Figure 4. S32 Debug Probe with an RJ45 cable attached
NOTE
When you configure the debugger for the hardware connection, you will need to specify the S32
Debug Probe IP address or hostname. The CCS findcc utility is used to search any probe on the
local subnet. For more information, see Using CCS to search for S32 Debug Probe topic.
NOTE
Depending on the type and complexity of your network, your network administrator may need to
update network server tables so that the network accesses the S32 Debug Probe correctly.
Updating networkserver tables requires both a detailed knowledge of Ethernet address resolution
and network routing with write access permission to the server tables. For more information on
network administration, see Network administration topic.
2.2 Customizing S32 Debug Probe
The S32 Debug Probe acquires its network configuration automatically using DHCP. If you cannot use DHCP, you must
configure the probe for your network using static IP address resolution.
To manually configure the network settings of S32 Debug Probe for your network, access the probe configuration console
as described below and use the probe on-board setup utility netparam to change the probe network settings. The probe
netparam utility lets you select and modify network parameters that are saved in probe memory. Use netparam to configure
the probe to match the network address resolution and routing protocols.
If the probe needs to communicate with hosts on other subnets, you will need to configure the probe for one of the following
routing options:
•Default gateways
•Static routing tables
Customizing S32Debug Probe

Connecting to Network
S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
12
To access S32 Debug Probe configuration console:
1. Connect the other end of the USB cable to the USB connector of the S32 Debug Probe.
Figure 5. S32 Debug Probe with USB cable attached
2. Wait for the TX/RX LED to start flashing green.
3. Identify the serial port device assigned to the S32 Debug Probe. On Windows, go to Device Manager > Ports and
then select USB serial port from the ports list. On Linux, the device file is located at: /dev/ttyACM0.
4. When prompted, press Enter. The login banner should be displayed and the core> command-line prompt appears.
To customize the S32 Debug Probe network settings:
1. Change the S32 Debug Probe network settings.
a. At the core> prompt, enter the netparam command to view the current settings.
b. For network setup, see netparam topic for syntax and options. For more information on installing the S32 Debug
Probe on a network, see Network administration topic.
c. At the core> prompt, enter the netparam commands and required parameters.
2. At the core> prompt, enter reset to reboot the S32 Debug Probe to activate the new network settings.
NOTE
If youconnect to the S32 Debug Probe using telnet rather than the USB configuration console, you
may lose access when you change network settings, and will need to reconnect after the settings
have changed.
Example: Assign a static IP address and hostname to the S32 Debug Probe

Connecting to Network
S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
13
Testing network communication
If the S32 Debug Probe has a static IP address of195.121.1.2 and a hostname of lab01, enterthe following commands:
core> netparam static_ip_address 195.121.1.2
core> netparam bootconfig static:lab01
core> reset
The netparam utility copies its settings into non-volatile memory on the probe. Follow these rules while using the netparam
utility:
•Each time you enter a netparam command, wait for the core> prompt to re-appear before entering the next command.
The prompt indicates that the parameter change is logged.
•When you have finished entering all settings, type reset at the core> prompt. When the probe restarts, it will use the
new netparam parameters.
2.3 Testing network communication
The ping command is used to test the network communication.
You can use the ping command to ensure that the S32 Debug Probe can communicate with the host. To verify
communication, type the following at a host command prompt:
ping hostname | ip_address
where hostname is the name and ip_address is the IP address assigned to the S32 Debug Probe. If no output is
displayed on the screen, check the following:
•The physical connections are tight.
•The S32 Debug Probe address and netmask in the hosts file match those in S32 Debug Probe flash.
•The netmask used for the S32 Debug Probe and for the Ethernet Network Interface Card (NIC) are appropriate to the
class of the IP address.

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
14
Connecting to Target System
Connecting to Target System
Debug port connector information
Chapter 3
Connecting to Target System
To use your S32 Debug Probe, youmust have a prototype hardware or an evaluation board. This chapter explains how to
connect a S32 Debug Probe to the target system.
This chapter explains:
•Debug port connector information
•Connecting to target system
3.1 Debug port connector information
The S32 Debug Probe offers debugging capabilities without modifying any target system code or any special I/O port in the
target system for communication with a monitor program running on the target system.
Target system connections can be made using the debug ports. The S32 Debug Probe connects to the target system's
JTAG header using a probe tip adapter and ribbon cable. The S32 Debug Probe is a powerful development tool for use with
a wide variety of processors. The following topics describe the debug port connector specifications:
•Arm CoreSight connector information
3.2 Connecting to target system
The target system must have a debug port header that you can connect to the S32 Debug Probe.
Make sure that you properly align the S32 Debug Probe multi-pin socket connector with the multi-pin header on your target
system.
CAUTION
Failure to properly connect the S32 Debug Probe to the target may damage the probe or target. Verify all
connections before applying power.

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
15
Connecting to Target System
Connecting Probe Tip to Target
Figure 6. S32 Debug Probe - connecting probe tip to the probe
NOTE
Pin 1 is clearly marked on the gray ribboncable by a red line down one side of the cable and a
small triangle in the plastic socket.
3.2.1 Connecting probe tip to target
This section explains how to connect the S32 Debug Probe cable to the target debug port header. To connect the S32
Debug Probe cable to the target debug port header:
1. Turn off the power to the target system.
2. Make sure that the USB cable from the S32 Debug Probe is not connected to the host computer.
3. Connect the probe tip to the S32 Debug Probe.
4. Make sure that pin 1 of the gray ribbon cable connector aligns with pin 1 on the target's debug port header.

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
16
Connecting to Target System
Figure 7. S32 Debug Probe - connecting to target
5. Gently (but firmly) press the connector onto the target system debug port header.
Connecting Probe Tip to Target

Using S32 Debug Probe
S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
21
Chapter 4
Using S32 Debug Probe
Debugging with S32 Debug Probe system
This chapter provides system startup procedures and explains how S32 Debug Probe is accessed remotely. This
chapter contains the following topics:
•Debugging with S32 Debug Probe system
•Accessing S32 Debug Probe remotely
4.1 Debugging with S32 Debug Probe system
Before starting debugging with S32 Debug Probe, you need to install S32 Design Studio on your machine.
This topic explains how to start debugging with the S32 Debug Probe. Before starting debugwith the S32 Debug Probe,
make sure you have:
•Connected the S32 Debug Probe to your network or computer.
•Connected the S32 Debug Probe to the target system.
•Installed the debugger software such as S32 Design Studio and properly configure it to communicate with the S32
Debug Probe.
To start the S32 Debug Probe:
1. Apply power to the S32 Debug Probe.
2. Apply power to the target system.
3. Start the S32 debugger.
4. Configure the debugger for the S32 Debug Probe connection.
LEDs are provided to indicate the status of the S32 Debug Probe. For details on the LED indicators, see LEDs on S32
Debug Probe topic.
You are now ready to begin your debug session. Refer to the debugger documentation to become familiar with the
system operation.
The following topics provide information specific to S32 Debug Probe operation:
•Run/Pause/Mixed mode states
4.1.1 Run/Pause/Mixed mode states
When the host debugger is connected to the target using the S32 Debug Probe, the probe is always in one of the states:
run, pause, or mixed mode.
The three states (modes) are run, pause, or mixed mode. The on the probe will indicate the mode.
•Run mode - The Run/Pause LED will be green. In this mode, all target system processor cores execute the target code.
•Pause mode - The Run/Pause LED will be red. In this mode, all target system processor cores have stopped executing
the target code.
•Mixed mode - The Run/Pause LED will be orange. In this mode, some target system processor cores are in run mode
and others are in pause mode.

Using S32 Debug Probe
S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
23
Accessing S32 Debug Probe Remotely
4.2 Accessing S32 Debug Probe Remotely
You can remotely access the internal setup utility after you connect the probe to your network.
If the host computer is not physically located near the probe, remote access is useful when you need to:
•Reconfigure communications
•Reset the probe through your Ethernet connection
To remotely access the setup utility:
Open a telnet session and connect to the probe by entering the command:
telnet hostname | ip_address
Use the host name or IP address of theprobe. For static IP, the host name must be the same one you entered into the hosts
database file; see Connecting to network topic. To identify the IP address of any probe on the subnet, see Using CCS to
search for S32 Debug Probes topic.
The login banner is displayed, followed by the core > command-line prompt.

Using S32 Debug Probe
S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
24
LEDs on S32 Debug Probe
Chapter 5
Hardware Specifications
This chapter provides hardware specifications for the probe.
The following sections are covered in this chapter:
•LEDs on S32 Debug Probe
•Host connectors on S32 Debug Probe
•Target connectors on S32 Debug Probe
5.1 LEDs on S32 Debug Probe
This section lists the LEDs of the S32 Debug Probe.
The figure below shows the various LEDs of the S32 Debug Probe.
Figure 10. S32 Debug Probe - LED indicators

S32 Debug Probe User Guide, Rev.1, 10/2018
NXP Semiconductors
25
Hardware Specifications
Transmit/Receive Indicator
Figure 11. S32 Debug Probe - Ethernet and USB connector
5.1.1 Transmit/Receive indicator
The (labeled TX/RX) indicates the status of communication between the probe and the network/host as follows:
•The LED is red until the probe boot code starts running.
•The LED flashes orange (1 Hz) during configuration of the network/USB interface.
•The LED flashes green (1 Hz) after network/USB interface has is successfully configured. During firmware updates, the
LED flashes green at a higher frequency (5Hz).
NOTE
Do not remove power, unplug the network, or press the reset button during firmware updates.
•The LED flashes orange when the S32 Debug Probe is communicating with the target.
•The LED is unlit if the probe is not powered on.
5.1.2 Run/Pause indicator
The status LED (labeled RUN/PAUSE) indicates the state of the target as follows:
•The LED is off when no target power is detected.
•The LED is green when the target is in run mode.