NXP Semiconductors S32 User manual
S32 Debug Probe
User Guide
Document Number: S32DBGUG
Rev. 2.0, 02/2020
Contents
Chapter 1: Introduction...........................................................................................3
Introducing S32 Debug Probe..............................................................................................................................4
What is S32 Debug Probe?..................................................................................................................................4
Product highlights.....................................................................................................................................5
Debugging environment............................................................................................................................6
S32 Debug Probe benefits........................................................................................................................6
Target connections....................................................................................................................................6
Operating requirements.........................................................................................................................................6
Standard electrostatic precautions............................................................................................................ 6
Operating temperature.............................................................................................................................. 6
Electrical requirements............................................................................................................................. 6
Related documentation..........................................................................................................................................7
Chapter 2: Tasks...................................................................................................... 8
Connecting to Network.........................................................................................................................................9
Connecting S32 Debug Probe to network................................................................................................9
Customizing S32 Debug Probe..............................................................................................................10
Testing network communication............................................................................................................ 12
Connecting to Target System.............................................................................................................................12
Debug port connector information.........................................................................................................12
Connecting to target system...................................................................................................................12
Using S32 Debug Probe.....................................................................................................................................13
Debugging with S32 Debug Probe system............................................................................................14
Accessing S32 Debug Probe Remotely................................................................................................. 14
Chapter 3: Reference............................................................................................. 16
Hardware Specifications.....................................................................................................................................17
LEDs on S32 Debug Probe....................................................................................................................17
Host connectors on S32 Debug Probe...................................................................................................18
Target connectors on S32 Debug Probe................................................................................................ 18
S32 Debug Probe Setup Utility Commands...................................................................................................... 20
Connecting to S32 Debug Probe setup utility....................................................................................... 20
S32 Debug Probe setup utility commands and variables.......................................................................21
Network Administration..................................................................................................................................... 24
S32 Debug Probe network ports............................................................................................................24
Configuring S32 Debug Probe using netparam..................................................................................... 25
Using CCS to search for S32 Debug Probes.........................................................................................27
S32 Debug Probe Firmware...............................................................................................................................28
Boot loader..............................................................................................................................................28
Reprogramming S32 Debug Probe firmware images............................................................................ 28
Arm CoreSight Connector Information..............................................................................................................29
Troubleshooting...................................................................................................................................................31
Troubleshooting communication problems............................................................................................31
Troubleshooting power problems...........................................................................................................32
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
2 NXP Semiconductors
Introduction
Introducing S32 Debug Probe
The S32 Debug Probe allows your personal computer to communicate with NXP automotive microcontrollers and
processors via JTAG debug connection.
Note:
• 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?
•Operating requirements
•Related documentation
What is S32 Debug Probe?
The S32 Debug Probe uses advanced emulation technology to provide control and visibility into your target
embedded system.
Combined with S32 Design Studio, the S32 Debug Probe speeds the debugging process by letting you interactively
control 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. 2.0, 02/2020
4 NXP Semiconductors
Introduction
Product highlights
This section lists the S32 Debug Probe features.
The S32 Debug Probe has these features:
• Supports NXP automotive microcontrollers and processors.
Note: Go to the http://www.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
• 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
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 5
Introduction
Debugging environment
The S32 Debug Probe works with the S32 debugger to give you control over the emulation functions and your target
system.
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.
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 http://www.nxp.com/S32debugprobe.
For information on connecting to a target, see Connecting to target system on page 12 topic.
Operating requirements
Before setting up the system, ensure that the operating environment is prepared.
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.
• 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.
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 on page 19 topic.
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, see Electrical characteristics on page 19 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 Ethernet communications, the S32 Debug Probe can be powered from the external power
supply 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.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
6 NXP Semiconductors
Introduction
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.
Note:
• Other power supplies may look similar, but can damage the probe if the supply specifications differ from the
required specifications.
• Connect only the provided power supply to the S32 Debug Probe.
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.
Related documentation
The S32DS documentation explains how to install and configure the S32DS IDE and debugger and use the S32
Debug Probe.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 7
Tasks
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:
•Connecting S32 Debug Probe to network
•Customizing S32 Debug Probe
•Testing network communication
Connecting S32 Debug Probe to network
The S32 Debug Probe’s default operation is to acquire its network configuration automatically using DHCP and
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.
2. Connect the other end of the RJ45 cable into the RJ45 connector of the Ethernet network or host computer.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 9
Tasks
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 Probes on page 27 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 network server
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 on
page 24 topic.
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
S32 Debug Probe Configuration Console Access
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.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
10 NXP Semiconductors
Tasks
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.
Note: 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.
S32 Debug Probe Network Settings Customisation
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.
Note: For network setup, see netparam on page 21 topic for syntax and options. For more information on
installing the S32 Debug Probe on a network, see Network Administration on page 24 topic.
b) 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 you connect 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.
Assign a static IP address and hostname to the S32 Debug Probe.
If the S32 Debug Probe has a static IP address of 195.121.1.2 and a hostname of lab01, enter the 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.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 11
Tasks
• When you have finished entering all settings, type reset at the core> prompt. When the probe restarts, it will
use the new netparam parameters.
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.
Connecting to Target System
To use your S32 Debug Probe, you must have a prototype hardware or an evaluation board. This chapter explains
how to connect a S32 Debug Probe to the target system:
•Debug port connector information
•Connecting to target system
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. For the debug port connector specifications see Arm CoreSight Connector
Information on page 29 topic.
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.
Note:
• 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. 2.0, 02/2020
12 NXP Semiconductors
Tasks
Note: Pin 1 is clearly marked on the gray ribbon cable by a red line down one side of the cable and a small triangle in
the plastic socket.
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.
5. Gently (but firmly) press the connector onto the target system debug port header.
Using S32 Debug Probe
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 on page 14
•Accessing S32 Debug Probe Remotely on page 14
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 13
Tasks
Debugging with S32 Debug Probe system
This topic explains how to start debugging with the S32 Debug Probe.
Before starting debug with 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 configured 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.
Note: 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.
For more information specific to S32 Debug Probe operation see Run/Pause/Mixed mode states topic.
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.
Table 1: Probe modes
Mode Indication Details
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
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:
1. Open a telnet session.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
14 NXP Semiconductors
Tasks
2. Connect to the probe by entering the command:
telnet hostname | ip_address
Note: Use the host name or IP address of the probe. 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.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 15
Reference
Hardware Specifications
This chapter provides hardware specifications for the probe.
The following sections are covered in this chapter:
•LEDs on S32 Debug Probe on page 17
•Host connectors on S32 Debug Probe on page 18
•Target connectors on S32 Debug Probe on page 18
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.
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.
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.
• The LED is red when the target is in pause mode.
• The LED is orange when the target is in mixed mode.
• The LED is initially unlit and remains so until the TX/RX LED starts flashing.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 17
Reference
RJ45 Ethernet connector with link and activity indicators
The probe interface connects directly to 10/100 twisted pair networks. See Connecting to Network on page 9 topic for
more information on connecting to a network.
The S32 Debug Probe link and activity indicators are integrated into the RJ45 S32 Debug Probe connector. The
yellow indicator is turned on when the S32 Debug Probe is connected to any network, and flickers when data is
being transferred across the network. The green indicator is turned on when the S32 Debug Probe is connected to a
100BaseT network, and flickers when data is being transferred across the network.
Host connectors on S32 Debug Probe
The figure below shows the host connectors of the S32 Debug Probe.
RJ45 Ethernet connector
The Ethernet connector on the S32 Debug Probe is used to connect to a 10/100BaseT Ethernet.
USB connector
The USB port on the S32 Debug Probe acts as both a virtual serial device and virtual Ethernet device. The virtual
serial interface is used for configuring network communication, entering routing tables, and for diagnostics. The
virtual Ethernet device is used by the debugger to communicate with the S32 Debug Probe.
Target connectors on S32 Debug Probe
The figure below shows the target connectors of the S32 Debug Probe.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
18 NXP Semiconductors
Reference
Probe tip connector
The 30-pin debug port header is used to connect the probe to a debug port header on your target system.
Note: Ensure that Pin 1 of the probe tip is connected to the Pin 1 of the header.
The probe tip consists of a 6-inch or 12-inch ribbon cable with the appropriate debug adapter attached. The ribbon
cable has a red stripe down one side to indicate the location of pin 1.
Electrical characteristics
The probe affects the load on only those signals that are connected to the debug port connector. Loading depends
on the method used to connect the probe to the target system. See Connecting to target system on page 12 topic for
description of each connection method.
The probe affects the target processor and target electrical characteristics. Caution should be taken in designing the
target to accommodate the small signal delays associated with in-circuit emulator or other test equipment.
This table shows the electrical characteristics of the S32 Debug Probe.
Table 2: Electrical characteristics
Characteristics Value
Target voltage levels supported 1.2V to 3.3V; 5V tolerant
Probe power consumption from target Less than 50 mA to detect target power
USB Power Supply 5V, 500mA
Note: Bus powered USB hubs are not designed to provide 500mA to devices. The S32 Debug Probe must be directly
connected to a self-powered hub, PC, or the AC adapter included in the kit.
Physical considerations
This table shows the physical characteristics of the probe.
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
NXP Semiconductors 19
Reference
Table 3: Physicall characteristics
Characteristics Value
Environmental requirements
Operating temperature 0 to 40 ×C (32 to 104 ×F)
Storage temperature -40 to 70 ×C (-40 to 158 ×F)
Humidity 5% to 95% relative humidity, non-condensing
Physical probe dimensions
Length 5.5" (7.5" with cables)
Width 3.25"
Height 1.375"
Probe tip cable socket dimensions
Height (above board) 0.375" (0.95 cm)
Thickness 0.20" (0.51 cm)
Pin-to-pin spacing 0.1" (0.25 cm)
Width Number of Positions x 0.1" (0.25 cm) + 0.18" (0.46 cm)
S32 Debug Probe Setup Utility Commands
This chapter explains how to access the S32 Debug Probe internal setup utility.
It describes all available setup utility commands and arguments.
This chapter contains the following topics:
•Connecting to S32 Debug Probe setup utility on page 20
•S32 Debug Probe setup utility commands and variables on page 21
Note: The commands described in this chapter are for reference only. For detailed procedures on using these
commands, see specific chapter that covers the topic of interest.
Connecting to S32 Debug Probe setup utility
There are two methods for accessing the S32 Debug Probe internal setup utility:
• Connect to the S32 Debug Probe USB port. Use this method if the S32 Debug Probe is not connected to your
network. For more information, see Customizing S32 Debug Probe on page 10 topic.
• Telnet to the S32 Debug Probe through an existing Ethernet connection. Use this method if the S32 Debug
Probe probe is currently connected to your network.
Telnet is the Internet standard protocol for remote logins. Most TCP/IP networks provide a telnet program that you
can use to login across the network to another machine. Note that if you lose your Ethernet connection by improperly
configuring the S32 Debug Probe from a telnet session, then you will have to connect to the USB port to re-establish
network communications.
Telnet to the S32 Debug Probe through an existing Ethernet connection
To connect to the setup utility using the telnet port:
S32 Debug Probe, User Guide, Rev. 2.0, 02/2020
20 NXP Semiconductors
Other manuals for S32
1
Table of contents
Other NXP Semiconductors Measuring Instrument manuals
