App T32start

T32Start
TRACE32 Online Help

TRACE32 Directory
TRACE32 Index
TRACE32 Debugger Getting Started ..............................................................................................
T32Start ..........................................................................................................................................
Abstract .......................................................................................................................................
Quick Start ..................................................................................................................................
First Steps
Debug Environment for a Single Core
Basic Configuration
Definition of the Start-up Script
12
Start of the TRACE32 Instance
13
Debug Environment for a Single Core with Power Debug II / Power Trace II
14
Basic Configuration
15
20
21
Debug Environment for Multicore Debugging (Single Device Solution)
22
Basic Configuration
24
Linkage of the TRACE32 Instances
29
32
Start of the TRACE32 Instances
33
Debug Environment for Multicore Debugging (Multi Device Solution)
34
Basic Configuration
35
40
44
45
Debug Environment for Multiprocessor Debugging
46
Basic Configuration
47
47
47
47
Software-only Debugging (Host MCI) .......................................................................................
48
Debug Environment for Setup 1 (Single Instance)
50
Debug Environment for Setup 2 (Integrated Server)
52
Debug Environment for Setup 3 (Dedicated Server)
54
Modification of Configuration Tree Items ................................................................................
56
Configuration Tree Item Types .................................................................................................
59
1989-2016 Lauterbach GmbH
T32Start
Complex Tree Items
59
Configuration Tree
59
Configuration Container and Configuration
60
Podbus Device Chain
60
Devices
62
Settings for the Host Interfaces
62
Relationship between Devices and TRACE32 Instances
65
TRACE32 Instances
67
Target Option
67
Advanced Settings and Default Advanced Settings
68
Show Start Environment Menu Action
71
Reset T32 History Menu Action
72
Create Start Link Menu Action
72
Global Settings Tree
73
Advanced Actions on Tree Items and Subtrees ......................................................................
74
Mouse Actions
74
Copy and Paste with the Clipboard
75
Load and Store based on Files
75
References to Environment Variables and Tree Items
76
Command Line Interpretation ...................................................................................................
77
Error Messages ..........................................................................................................................
78
T32Start
T32Start
Version 24-May-2016
Abstract
For Windows only.

Not for TRACE32-ICE and not for TRACE32-FIRE.
The main objective of T32Start is to ease the setup of multicore/multiprocessor debug environments.
To start a TRACE32 instance a so-called configuration file is required. The configuration file defines
primarily:
The host interface that is used to connect the LAUTERBACH device to the PC.
The environment variables that are required by the TRACE32 instance.
For details refer to Set up the Application Properties.
To debug multicore applications one TRACE32 instance has to be started for each core. Each
instance requires an adapted configuration file. Creating and managing all configuration files and
TRACE32 instances for a multicore debugging environment becomes quite complex. With
T32Start this work is easier to handle.
For detail about the multicore debugging concept of LAUTERBACH refer to Multicore
Debugging in ICD Debugger Users Guide, page 23 (debugger_user.pdf).
To debug multiprocessor applications one TRACE32 instance has to be started for each
processor. Each instance requires an adapted configuration file. Creating and managing all
configuration files and TRACE32 instances for a multiprocessor debugging environment
becomes quite complex. With T32Start this work is easier to handle.
For details on the multiprocessor debugging concept of LAUTERBACH refer to Multiprocessor
Debugging in ICD Debugger Users Guide, page 53 (debugger_user.pdf).
Using T32Start is also advisable if many different debugger configurations are used.
T32Start
Abstract
The draft below shows the flow of information between the debug environment and the TRACE32 instances.
Connection
Type
Target
System
Podbus Device
Chain
Podbus
Device
- Lauterbach Hardware Configuration

- Startup Scripts
- Multicore / Multiprocessor
- Generated TRACE32 Configuration Files

- Commandline Options
T32Start
Abstract
The T32Start features are:
The configurations are displayed in a tree, whose nodes can be edited easily.
Nodes and subtrees can be created, deleted, replaced, copied, pasted, loaded and saved by
keyboard inputs or drag and drop actions.
Multiple configurations can be constructed, saved and sorted into the tree.
New configurations for TRACE32 instances are copied from a Default Configuration.
The resulting configuration files and command line options can be viewed without starting up the
whole debug environment.
The started processes can be displayed and terminated if necessary.
T32Start can be controlled with command line parameters.
T32Start
Abstract
Quick Start
To start T32Start, do one of the following:
Click the Windows Start button, and then select T32Start.
Navigate to the TRACE32 system directory (by default c:\t32) and double-click the t32start.exe.
First Steps
t32start.exe is copied during the installation to the TRACE32 system directory.
When T32Start is started the first time, the following basic settings are displayed:
T32Start has already adapted some default settings. Open the Settings branch to display them.
Since the default settings are used as base for all user-created configurations it is recommended to adapt
them to your environment.
T32Start
Quick Start
Debug Environment for a Single Core

The following example describes how to start a TRACE32 instance to debug an ARM9 via a POWER
DEBUG INTERFACE / USB 2 interface.
Target
ARM9
Debug Cable
for ARM9
PC
POWER
DEBUG
INTERFACE
/USB 2
TRACE32 Instance for ARM9

USB
Interface
Power
Supply
T32Start
Quick Start
Basic Configuration
1.
Add a new Configuration. Use a right-click to open the context menu.
2.
Rename the Configuration by using the function key F2.
T32Start
Quick Start
3.
Create a Podbus Device Chain.

The Podbus Device Chain defines which LAUTERBACH devices are used for debugging.
4.
Add the POWER DEBUG INTERFACE / USB2 to the Podbus Device Chain.
T32Start
Quick Start
The correct name of your LAUTERBACH device can be read from the labelling.
Labelling of the
LAUTERBACH device
The LAUTERBACH device which provides the host interface has to be the first device in the Podbus
Device Chain.
5.
Assign a Core to the Power Debug USB II.
T32Start
10
Quick Start
6.
Open the Core branch to specify ARM as architecture for debugging.
Now the basic configuration is done.
T32Start
11
Quick Start

1.
Open the Advanced Settings branch to specify a Startup Script.
2.
Select File and open the file browser.

Select your start-up script if available.
T32Start
12
Quick Start

1.
Close the complete configuration tree.
2.
Start the TRACE32 instance to debug the ARM9.
T32Start
13
Quick Start
Debug Environment for a Single Core with Power Debug II / Power Trace II
The following example describes how to start a TRACE32 instance to debug an ARM9 that also provides
program and data flow information via the ETM trace port.
Target
ARM 9
ETM-Preprocessor to
Trace Connector
On-chip Debug
Interface
Debug Cable
for ARM 9
POWER
DEBUG II
PC
POWER
TRACE II

with ETM trace port
USB
Interface
Power
Supply
Power supply has to be connected to POWER DEBUG II only. Power (voltage)

is passed on by POWER DEBUG II to POWER TRACE II.
The power jack at the POWER TRACE II is reserved for future use only.
T32Start
14
Quick Start
Basic Configuration
1.
Add a new Configuration. Use a right-click to open the context menu.
2.
T32Start
15
Quick Start
3.

4.
Add the POWER DEBUG II to the Podbus Device Chain.
T32Start
16
Quick Start
Labelling of the
LAUTERBACH device
Device Chain.
5.
Add the POWER TRACE II to the Podbus Device Chain
T32Start
17
Quick Start
6.
Assign a Core to the Power Debug II.

The reason for this assignment is that the TRACE32 driver software/JTAG handler runs on the Power
Debug II module.
Because two devices are used for debugging, both of them have to be included in the Podbus
Device Chain.
7.
T32Start
18
Quick Start
Now the basic configuration of POWER DEBUG II is done.
T32Start
19
Quick Start

1.
Open the Advanced Settings branch to specify a Startup Script.
2.
Select File and open the file browser.

Select your start-up script if available.
T32Start
20
Quick Start

1.
2.
Start the TRACE32 instance to debug the ARM9.
T32Start
21
Quick Start
Debug Environment for Multicore Debugging (Single Device Solution)

The term Multicore Debugging is used if there are multiple cores on one chip which use a joint JTAG
interface for debugging. In the following example a debug environment is set-up to debug a chip that
contains an ARM9 and an Xpert Teak.
The term Single Device Solution is used if one LAUTERBACH device is used to debug all cores.
Precondition is that the debug cable contains licenses for all cores that should be debugged.
The debug cable used for the following example contains a license for the ARM9 plus a license for
OAK+Teak/JAM (See also the command VERSION).
T32Start
22
Quick Start
The following example describes how to start two TRACE32 instances
one to debug an ARM9
one to debug an Xpert Teak
on a multicore chip. Both cores are debugged via a joint JTAG interface by using a POWER DEBUG
INTERFACE / USB 2.
Target
ARM9
Xpert
Teak
Debug Cable with License

for ARM9 and OAK+Teak/JAM
PC
POWER
DEBUG
INTERFACE
/USB 2
USB
Interface
Power
Supply
TRACE32 Instance for Xpert Teak
T32Start
23
Quick Start
Basic Configuration
1.
Add a new Configuration.
2.
Re
T32Start
24
Quick Start
3.

4.
Add the POWER DEBUG INTERFACE / USB 2 to the Podbus Device Chain.
T32Start
25
Quick Start
Labelling of the
LAUTERBACH device
Device Chain.
5.
Assign the first Core to the Power Debug USB II.
T32Start
26
Quick Start
6.
7.
Assign the second core to the Power Debug USB II.
T32Start
27
Quick Start
8.
Open the Core2 branch to specify Teak as architecture for debugging.
Now the basic set-up to start two TRACE32 instances to debug an ARM9 and an XpertTeak via a joint JTAG
interface is done.
T32Start
28
Quick Start

A linkage between the TRACE32 instances is recommended for the following purposes:
Start/stop synchronization
The start/stop synchronization has to be prepared before the start of the TRACE32 instances by
configuring the Intercom Port for each core. This in independent of the implementation of the
start/stop synchronization. For details about the LAUTERBACH concept for the start/stop
synchronization refer to Installation in ICD Debugger Users Guide.
Communication between the TRACE32 instances

The individual TRACE32 instances can communicate via the INTERCOM command. This
communication has to be prepared before the start of the TRACE32 instances by configuring the
Intercom Port for each core.
T32Start
29
Quick Start
Intercom Port Configuration for the First Core

1.
Open the Advanced Settings branch for the first Core to configure the Intercom Port.
2.
Set Use Port.
The default Port Value is 10000.

T32Start
30
Quick Start
Intercom Port Configuration for the Second Core

1.
Open the Advanced Settings branch for Core 2 to configure the Intercom Port.
2.
Set Use Port.
Since Use Auto Increment Port is set to yes the Port Value for the second core is 10001.
T32Start
31
Quick Start

The definition of the start-up script is the same as for a single-core. Refer to chapter Definition of the
Start-up script for a single core.
T32Start
32
Quick Start

1.
2.
Start the TRACE32 instances to debug the ARM9 and XpertTeak in a multicore debugging
environment.
T32Start
33
Quick Start
Debug Environment for Multicore Debugging (Multi Device Solution)

The term Multicore Debugging is used if there are multiple cores on one chip which use a joint JTAG
interface for debugging. In the following example a debug environment is set-up to debug a chip that
contains an ARM9 and an Xpert Teak.
The term Multi Device Solution is used if independent debuggers are used to debug the cores of a
multicore chip via a joint JTAG interface.
The following example describes how to start two TRACE32 instances:
to debug an ARM9 via a POWER DEBUG INTERFACE / USB 2
to debug an Xpert Teak via a second POWER DEBUG INTERFACE / USB 2
on a multicore chip. Both cores are debugged via a joint JTAG interface.
Target
ARM9
Xpert
Teak
Joint JTAG Interface
PC
Debug Cable
for ARM9
POWER
DEBUG
INTERFACE
/USB 2
Debug Cable
for Xpert Teak
POWER
DEBUG
INTERFACE
/USB 2
Power
Supply
USB
Interface
AC/DC-adapter
T32Start
34
Quick Start
Basic Configuration
1.
Add a new Configuration.
2.
T32Start
35
Quick Start
3.

Add two
4.
Add two POWER DEBUG INTERFACE / USB 2 to the Podbus Device Chain.
T32Start
36
Quick Start
Labelling of the
LAUTERBACH device
Device Chain.
5.
Assign a Core to the first Power Debug USB II.
T32Start
37
Quick Start
6.
Open the Core branch to specify ARM as architecture.
7.
Assign a core to Power Debug USB II 2.
T32Start
38
Quick Start
8.
Open the Core branch to specify Teak as architecture.
Now the basic set-up to start two TRACE32 instances to debug an ARM9 and an XpertTeak via a joint JTAG
interface is done.
T32Start
39
Quick Start

A linkage between the TRACE32 instances is recommended for the following purposes:
Start/stop synchronization
The start/stop synchronization has to be prepared before the start of the TRACE32 instances by
configuring the Intercom Port for each core. This in independent of the implementation of the
start/stop synchronization. For details about the LAUTERBACH concept for the start/stop
synchronization refer to Start Stop Synchronization inICD Debugger Users Guide
(debugger_user.pdf).
Communication between the TRACE32 instances

The individual TRACE32 instances can communicate via the INTERCOM command. This
communication has to be prepared before the start of the TRACE32 instances by configuring the
Intercom Port for each core.
T32Start
40
Quick Start
Intercom Port Configuration for the Core assigned to the first Power Debug USB II
1.
Open the Advanced Settings branch for the Core assigned to the first Power Debug USB II to
configure the Intercom Port.
2.
Set Use Port.
The default Port Value is 10000.

T32Start
41
Quick Start
Intercom Port Configuration for the Core assigned to the second Power Debug USB II
1.
Open the Advanced Settings branch for the Core assigned to the second Power Debug
USB II 2 to configure the Intercom Port.
T32Start
42
Quick Start
2.
Set Use Port.
Since Use Auto Increment Port is set to yes the Port Value for the core assigned to the second
Power Debug USB II is 10001.
T32Start
43
Quick Start

T32Start
44
Quick Start

1.
Close the complete configuration path.
2.
Start the TRACE32 instances to debug the ARM9 and XpertTeak in a multicore debugging
environment.
T32Start
45
Quick Start
Debug Environment for Multiprocessor Debugging

The term Multiprocessor Debugging is used if there a multiple microcontrollers on the target. Each
microcontroller is debugged via its own JTAG interface.
The following example describes how to start two TRACE32 instances:
To debug an ARM9 via a POWER DEBUG INTERFACE / USB2
To debug an Xpert Teak via a second POWER DEBUG INTERFACE / USB2
Each microcontroller has its own JTAG interface.

Target
ARM9
PC
Debug Cable
for ARM9
POWER
DEBUG
INTERFACE
/USB 2
USB
Interface
Xpert
Teak
Debug Cable
for Xpert Teak
POWER
DEBUG
INTERFACE
/USB 2
Power
Supply

AC/DC-adapter
T32Start
46
Quick Start
Basic Configuration
The basic configuration is the same as for multi device solutions. Refer to chapter Basic COnfiguration
for multi device solutions.

Linkage of instances is the same as for multi device solutions. Refer to chapter Linkage of the TRACE32
Instances for multi device solutions.


Starting instances is the same as for multiprocessor debugging. Refer to chapter Start of the TRACE32
Instances for multiprocessor debugging.
T32Start
47
Quick Start
Software-only Debugging (Host MCI)

The Lauterbach TRACE32 Integrated Debug Environment supports debug sessions with and without
hardware. Without hardware means software-only debugging - without Lauterbach debugger hardware.
This chapter describes how to configure software-only debug environments in T32Start for use in
TRACE32 PowerView, the graphical user interface of TRACE32.
The TRACE32 PowerView instances can be set up in different ways.
1.
A single TRACE32 PowerView instance runs on the same host as the back-end, see Setup 1. This
configuration cant handle AMP debug scenarios.
2.
Multiple TRACE32 PowerView instances run on the same host as the back-end, see Setup 2.
3.
The TRACE32 PowerView instances run on a dedicated workstation; the back-end runs on another
host, see Setup 3.
The T32Start application assists you in configuring the desired setup. This way you do not need to manually
edit any config.t32 file. Simply choose the setup you need, and then follow the cross-reference at the bottom
of the chosen setup diagram.
Setup 1
Setup with a single TRACE32 PowerView instance running on the same host as the back-end:

For step-by-step instructions on how to configure the above setup in T32Start, see Debug Environment
for Setup 1 (Single Instance), page 50.
T32Start
48
Setup 2
Setup with multiple TRACE32 PowerView instances (AMP) running on the same host as the back-end:

for Setup 2 (Integrated Server), page 52.
Setup 3
Setup with multiple TRACE32 PowerView instances (AMP) running on another host:

for Setup 3 (Dedicated Server), page 54.
T32Start
49
Debug Environment for Setup 1 (Single Instance)

1.
In the T32Start window, right-click Configuration Tree, point to Add, and then select
Configuration.
A tree item named Configuration<number> is displayed.

2.
Press F2 to rename the new Configuration<number> tree item to a meaningful name, for
example, hostmci_setup1.
MCI Lib Debugger and Target

3.
Right-click the renamed tree item, point to Add, and then select MCI Lib Debugger.
4.
Click the little triangle next to MCI Lib Debugger to expand the tree node and navigate to Target.
5.
Right-click Target, and then select the target name you want from the Target drop-down list.
This completes the steps for setup 1. The remaining steps depend on your project, see Advanced Settings
below.
T32Start
50
Advanced Settings
6.
Configure the Advanced Settings as required by your environment.

For a description of the tree items under Advanced Settings, see Advanced Settings and
Default Advanced Settings.
7.
Click Save when you are done.
T32Start
51
Debug Environment for Setup 2 (Integrated Server)

1.
Configuration.
A new tree item named Configuration<number> is displayed.

2.
Press F2 to rename the tree item to a meaningful name, for example, hostmci_setup2.
MCI Server and Server Settings (Setup 2)

3.
Right-click the renamed tree item, point to Add, and then select MCI Server.
4.
Navigate from MCI Server to Server Settings by clicking the little triangles next to the tree items.
5.
Under Server Settings, make these settings:

-
Node Name / IP Address: Leave empty or type localhost
Port: Type any free port number
Dedicated: no
T32Start
52
MCI Server Debugger and Target (Setup 2)

6.
Click the MCI Server tree item, point to Add, and then select MCI Server Debugger.
7.
Click the little triangle next to MCI Server Debugger to navigate to Target.
8.
9.
Repeat the steps in this section for each MCI Server Debugger required for your project.
below.
Advanced Settings (Setup 2)
10.
For each MCI Server Debugger, configure the Advanced Settings as required for your project.
11.
T32Start
53
Debug Environment for Setup 3 (Dedicated Server)

1.
Configuration.
A tree item named Configuration<number> is displayed.

2.
Press F2 to rename the tree item to a meaningful name, for example, hostmci_setup3.
MCI Server and Server Settings (Setup 3)

3.
Right-click the renamed tree item, point to Add, and then select MCI Server.
4.
Navigate from MCI Server to Server Settings by clicking the little triangles next to the tree items.
5.
Under Server Settings, make these settings:

-
Node Name / IP Address: Type IP address of the workstation where t32mciserver runs
Port: Type any free port number
Dedicated: yes
T32Start
54
MCI Server Debugger and Target (Setup 3)

6.
Click the MCI Server tree item, point to Add, and then select MCI Server Debugger.
7.
Click the little triangle next to MCI Server Debugger to navigate to Target.
8.
9.
Repeat the steps in this section for each MCI Server Debugger required for your project.
below.
Advanced Settings (Setup 3)
10.
For each MCI Server Debugger, configure the Advanced Settings as required for your project.
11.
T32Start
55
Modification of Configuration Tree Items

1.
Buttons at the right side

A set of often used functions is provided by buttons at the right side of the T32Start window. Their
action is executed in the context of the selected tree item except the global functions Instances,
Save and Exit and Save. If a function is not possible to be executed for the selected item the button is
disabled.
2.
Context sensitive menu

Every tree item has a mouse menu with functions that can be performed on it and its subitems.
T32Start
56
3.
Double click on tree item

Boolean type tree items allow to change their state by a double click on the item.
4.
Text edit by single mouse click or F2 key

The display names of user created items and items for texts and numbers can be edited within the
tree. During the edit process the fixed prefix of these items is not displayed e.g. numeration, value
names.
T32Start
57
5.
Edit area at the bottom of the window

More complex tree item can be edited in an item type dependent input panel at the bottom of the
window. The edit area offers help informations and buttons to dialogs like file browsers.
T32Start
58
Configuration Tree Item Types
Complex Tree Items

T32Start allows to build complex configuration trees in a short time. The following UML diagram shows the
relationships and a classification of the complex tree items.
1
Configuration Tree
Settings
1
*
1
Configuration Container
*
Simulator
Configuration
1
Arbitrary Program
*
Serial Rom Monitor
PodBus Device Chain

Power Debug USB 2
...
Other
Devices
...
1
*
PodBus Device
Trace32 GUI
1
*
Power Trace
Core
Configuration Tree
The Configuration Tree is the root of the tree and contains Configurations or Configuration Container.
Both item types can be created and deleted from the tree. The Configuration Tree does also contain the
Settings tree, where default settings are stored.
T32Start
59
Configuration Container and Configuration

A Configuration is the top most startable item in the configuration tree. It contains other startable items e.g.
Podbus Device Chain or Simulator. When a Configuration is started, all startable subitems are started one
after the other. The start order is defined by the numeration of the items. Numerated items can be moved up
or down with the buttons in the device specific pull-down menu.
It is possible to organize Configurations in Configuration Containers. Configuration Container can have
other Configuration Container as subitems.
Podbus Device Chain

Several LAUTERBACH devices can be arranged in a Podbus Device Chain like it is displayed below.
Podbus is a proprietary bus used by LAUTERBACH to connect several devices.
Complex Multicore Debug Environment

Connection
Type
Multicore
Target
System
1
2
3
4
PodBus Device
Chain
PodBus
Device
PodBus Device
Chain order equals
order in T32Start
The order and type of LAUTERBACH devices has to be modelled as subitems in the Podbus Device
Chain.
T32Start
60
The device which contains the host interface has to be the first device in the Podbus Device Chain. The Up
and Down buttons can be used to change the device order.
Every device has a menu item Replace by to exchange it by a another device. While the exchange takes
place the settings of the device are kept if possible.
T32Start
61
Devices
Settings for the Host Interfaces
Parallel Port Settings

Option
Description
Port
Port number e.g. for LPT2 the port number is 2.
Access Mode
TRACE32 driver mode.

PARPORT is the most recommended option. Choose LPT if PARPORT
does not work.
Connection
Mode
Parallel port interface mode according to your BIOS settings. Valid

modes are: Standard, ECP, EPP.
T32Start
62
Ethernet Settings
The options Max UDP Packet Size, Packet Burst Limitation, Compression and Delay can be
useful when the net work connection is slow or many routers are involved.
Option
Description
Node Name /
IP Address
Network address for Podbus device
Max UDP
Packet Size
The network can have a limited UPD packet size below the default of
1024 bytes. Setup this value to limit the maximum packets the TRACE32
will send through the network.
Packet Burst
Limitation
Sends only very small packets.
Compression
If enabled reduces the packet size by compression.
Delay
Delay time between sending two UDP packets. This can avoid packet
order changing when connection is established through internet.
T32Start
63
PODBUS Interface Card for ISA

Option
Description
Port
IO Communication Port
USB Options
Option
Description
Node Name
Name of the connected device. This options is used if multiple USB

devices are connected to one PC
T32Start
64
Relationship between Devices and TRACE32 Instances
A TRACE32 instance (GUI) can control one or more devices.

Normally a TRACE32 instance controls the debug process for one core.
All Debug Devices and the PowerTrace Ethernet can have a Core as subitem.
If a multicore (single device solution) debug environment is configured, Debug Devices/Power Trace
Ethernet can have more then one core as subitem.
There are devices (e.g. Power Probe, Power Integrator) that can be used as add-ons for a debug process. In
this case they are controlled by the TRACE32 instance assigned to the debug process for a specific Core.
Therefore these add-on devices has to be linked to the appropriate Core.
In the following example the Power Probe is linked to the core assigned to the first Power Debug USB II.
T32Start
65
The Power Probe and the Power Integrator can also be used as stand-alone devices. In this case a
appropriate host interface is required.
T32Start
66
TRACE32 Instances
The following items are associated with a TRACE32 instance: Core, Simulator, Serial Rom Monitor and T32.
The settings to perform the start and setup for the started instance are derived from the values of the
subitems and items in the whole Configuration e.g. the position in the Podbus Device Chain or the
connection type of the first device in the chain.
Target Option
The Target subitem of a TRACE32 instance defines the executable to be started to support the target
architecture of the dedicated debug process.
T32Start
67
Advanced Settings and Default Advanced Settings
Not all TRACE32 settings have to be adapted for every TRACE32 instance. The settings are composed into
a subtree called Advanced Settings. Every time a new instance is create the Advanced Settings are
copied from the Default Advanced Settings located in the Settings tree.
Copy from template
Advanced Settings in detail:
Paths
Item
Description
Working Path
Active directory after starting the TRACE32 instance.
System Path
Directory, where the executable and system files of TRACE32 are

located.
Temp Path
Directory, where temporary files can be created.

The source files are copied to the temporary directory while debugging.
Help Path
Directory, where the pdf-files for the TRACE32 online help are located.
License File
File for the license keys to guarantee software maintenance.
Display
Item
Description
Title
Set the window title of the TRACE32 instance. Wild cards can be
included into the value e.g. for Core Number, Intercom Port, API Port,
T32Start
68
Small Font
Size
If true, small fonts are used.
Full Screen
If set to true, the TRACE32 instance is started in full screen mode.
Iconic
If true, the TRACE32 instance is iconic after starting.
MWI
Child windows are created on the desktop instead within the main
window.
Language
Setup the fonts used by TRACE32.
API Port and Intercom Port

Item
Description
Use Port
Lets the TRACE32 instance listen to the UDP port.
Use Auto
Increment Port
To ensure unique port numbers it is possible to assign an automatically

created port number to the TRACE32 instance. The Port numbers are
unique within a single Configuration then. API Ports and Intercom Ports
are treated as different increasing port sets.
Port Start
Value
When Use Auto Increment Port is false, the port number can be specified
here. If the TRACE32 instance is the first one to be started in the
Configuration, Port Start Value is the start value of the increasing port
number set.
Port Value
The field is read-only and displays the resulting port number.
T32Start
69
Startup Script
Item
Description
Source
When a TRACE32 instance starts, t32.cmm is executed either from the

working directory (see WorkingPath tree item) or the system directory
(see SystemPath tree item).
The behavior can be changed by passing a start-up script to the
TRACE32 instance which is executed then instead of t32.cmm. T32Start
support two types of start-up scripts:
File
Built-in Script
When File is chosen as Source, the file assigned to the File item will be
executed.
File
If the Source item is set to File, specify the start-up script here.
Parameters
Set the parameters that are passed to the command script from File or
Built-in Script.
Built-in Script
The start-up script can be edited and stored directly in T32Start. Select
the item and press the Edit button to edit the script.
This example is for demo purposes only, and assumes that the following settings are made in the
Startup Script tree item:
Source: File
Parameters: "Hello World" %COMPUTERNAME%
File: c:\t32\demo-start-up-script.cmm
When TRACE32 is started via T32Start, the parameters are passed to the specified PRACTICE start-up
script (*.cmm). In this example, the script is programmed to open an AREA.view window in TRACE32 and
display the parameters.
T32Start
Start-up script (demo)
TRACE32
%COMPUTERNAME% is an environment variable of Windows. For information about the environment variables
of T32Start, see References to Environment Variables and Tree Items, page 76.
Information for advanced users: The %LINE option together with ENTRY reads multiple parameters into one
PRACTICE macro. For more information, see ENTRY.
T32Start
70
Show Start Environment Menu Action
The context menu of a TRACE32 instance item offers a menu item Show Start Environment.
This opens a dialog, where the whole startup script and command line is visible. This is implemented mainly
for diagnostics purposes.
The Batch Job field shows the DOS command script which would have to be executed in order to start the
TRACE32 instance. The Configuration File field displays the configuration file contents. The shown file
names are valid also after closing T32Start.
T32Start
71
Reset T32 History Menu Action
Every TRACE32 instance has a unique ID which assigns the history and file names of temporary created
files to the TRACE32 instance. The Reset T32 History menu action allocates new IDs to the items and
subitems in order to reset the history and to disconnect multiplied TRACE32 instances items.
Create Start Link Menu Action
The Create Start Link menu action opens a dialog in order to create links to T32Start on the Windows
Desktop or Windows Start Menu.
After the link is executed, T32Start will appear and start the connected item and all subitems. After starting,
T32Start will be closed automatically based on the settings.
T32Start
72
Global Settings Tree

The Global Settings tree contains general settings.
Setting
Description
Delay between start of

multiple instances
Defines the time that T32Start wait between the start of two
TRACE32 instances.
Replace empty paths
When set to by program directory, T32Start suggest a TRACE32

installation in the current working directory when ever an item in
the Advanced Setting subtree is left empty. The option by standard
directory just suggests the settings from the Default Advanced
Settings.
Saving Location / Target

Type
Target Type Registry will store the entire Configuration Tree into
the Windows Registry under the HKEY_CURRENT_USER key.
Saving Location / File
When Target Type is File, T32Start stores the Configuration Tree to

the specified file. This will consume less memory in the registry
and makes it possible to share the settings between different user.
T32Start
73
Advanced Actions on Tree Items and Subtrees
Mouse Actions
The tree items can be modified by mouse actions with drag & drop.
Actions with two items involved: The possible actions take affect only on the two involved source
and destination item. The matrix below shows the four cases that are possible in this case. The
shift key switches between the move and copy mode. The append and replace mode is derived
by the program automatically depending on the concrete situation.
Source
Move
Copy
Replace
Destination
Add
Deep Replace: It is possible to replace none-deletable subtrees by a template tree. This can be
done by dragging the template tree and dropping it on the root of the tree, where the compatible
subtrees are to be replaced.
Deep Replace
of Working Path
in Example Configuration
T32Start
74
Copy and Paste with the Clipboard

Every tree item has menu items for transferring data from and to the Clipboard. The data is handled as
ASCII text. In contrast to the mouse actions, two methods for the paste command can be chosen. past and
add will add the clipboard data as subitems of the selected node. paste and replace will replace the tree
item.
Load and Store based on Files

Every tree item can be loaded and stored into or from a file. Analog to the copy and past function, the loaded
data can replace a tree item or it can be added as subitem.
T32Start
75
References to Environment Variables and Tree Items

Windows environment variables can be assigned to tree items designed to contain paths and file names. For
example, if the Windows environment variable %TEMP% is assigned to the tree item TempPath, then
TRACE32 and other applications share the users default temporary directory (See figure below). In addition
to the Windows environment variables, there is the T32Start environment variable %WORKINGDIR%. It points
to the initial working directory of T32Start.
Tree items can contain references to other tree items. The reference between a source item and a
destination item can be a relative or an absolute path.
For example, the reference %//Settings/CoreAdvancedOptions/Directories/SystemPath%
points to the tree item Default Advanced Settings > Paths > SystemPath. The substring // is interpreted
as root of the Configuration Tree. Delimiters are marked as single slash, and two dots return to the top
item.
To create a reference to another tree item in T32Start:
1.
Select the destination item you want.
2.
Click the Link to button to browse the entire tree.
3.
Navigate to the source item you want.
4.
Click OK to create the reference.
The absolute path of any item is displayed in the status line of T32Start. To copy the absolute path, right-click
the status line, and then select Copy ID.
TRACE32 uses the default

temporary directory of the
currently logged-on user.
T32Start
76
Command Line Interpretation

The Syntax of the command line parameters of T32Start is:
T32Start.exe [-QUIT] [[-RUNCFGFILE] <ConfigurationFile>] [-RUNITEM <ID>]
Command Line Option
Description
-QUIT
Closes T32Start after any action given by the other options.
-RUNCFGFILE
<ConfigurationFile>
Start the configuration saved in the file <ConfigurationFile>. Make

sure, that <ConfigurationFile> was derived from a tree item of the
type configuration.
<ConfigurationFile>
Adds the configuration saved in the file <ConfigurationFile> to the

configuration tree. Make sure, that <ConfigurationFile> was
derived from a tree item of the configuration type.
-RUNITEM <ID>
Starts a configuration or other startable items, that are already part

of the configuration tree. The parameter <ID> is the absolute
logical path to the tree item e.g. //Configuration1. This is the
recommended way to start configurations remotely.
T32Start
77
Command Line Interpretation
Error Messages
Problem / Error Message
Solution
Directory not found / File

not found
The consistency between the TRACE32 installation and the

Advanced Settings/Paths is lost. Check your installation and the
Path settings.
Loaded file is not of type

"Configuration"
The command line parameter <ConfigurationFile> points to a file

that was not saved from a tree item of type Configuration.
Invalid ID path
The command line parameter <ID> was not found or references to

an item that is not startable. Copy the right ID of a startable item
with the context menu at the status line.
Could not write to file
The Configuration tree could not be saved to the file. Specify a

writable file under Settings/Global Settings/Saving Location/File.
string reference contains

itself
File paths or directory path can refer to other tree items in order to
take their value. Circular references are not allowed. Correct the
references.
Cannot find configuration

path
A reference could not be resolved. Correct the references.
Cannot find env variable
The environment variable could not be found. Create an

environment variable with that name and restart T32Start or
correct the references.
Cannot find executable
Probably the wrong Target is selected in a TRACE32 instance item

(Core, Simulator, ). The executable for that target type is not
installed.
No T32 GUI appears when

Start is pressed without any
error message
Add TRACE32 instance tree items to the sub tree of the startable
item.
T32Start
78
Error Messages

App T32start

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

App T32start

Загружено:

Авторское право:

Доступные форматы

T32Start

TRACE32 Online Help

Quick Start ..................................................................................................................................

Debug Environment for a Single Core

Definition of the Start-up Script

Start of the TRACE32 Instance

Definition of the Start-up Script

Start of the TRACE32 Instance

Debug Environment for Multicore Debugging (Single Device Solution)

Linkage of the TRACE32 Instances

Definition of the Start-up Script

Start of the TRACE32 Instances

Debug Environment for Multicore Debugging (Multi Device Solution)

Linkage of the TRACE32 Instances

Definition of the Start-up Script

Start of the TRACE32 Instances

Debug Environment for Multiprocessor Debugging

Linkage of the TRACE32 Instances

Definition of the Start-up Script

Start of the TRACE32 Instances

Software-only Debugging (Host MCI) .......................................................................................

Debug Environment for Setup 1 (Single Instance)

Debug Environment for Setup 2 (Integrated Server)

Debug Environment for Setup 3 (Dedicated Server)

Modification of Configuration Tree Items ................................................................................

Configuration Tree Item Types .................................................................................................

1989-2016 Lauterbach GmbH

Complex Tree Items

Configuration Container and Configuration

Podbus Device Chain

Settings for the Host Interfaces

Relationship between Devices and TRACE32 Instances

Advanced Settings and Default Advanced Settings

Show Start Environment Menu Action

Reset T32 History Menu Action

Create Start Link Menu Action

Global Settings Tree

Advanced Actions on Tree Items and Subtrees ......................................................................

Copy and Paste with the Clipboard

Load and Store based on Files

References to Environment Variables and Tree Items

Command Line Interpretation ...................................................................................................

Error Messages ..........................................................................................................................

1989-2016 Lauterbach GmbH

For Windows only.

The environment variables that are required by the TRACE32 instance.

For details refer to Set up the Application Properties.

1989-2016 Lauterbach GmbH

- Lauterbach Hardware Configuration

- Generated TRACE32 Configuration Files

1989-2016 Lauterbach GmbH

The T32Start features are:

The started processes can be displayed and terminated if necessary.

T32Start can be controlled with command line parameters.

1989-2016 Lauterbach GmbH

Click the Windows Start button, and then select T32Start.

Debug Environment for a Single Core

TRACE32 Instance for ARM9

1989-2016 Lauterbach GmbH

Add a new Configuration. Use a right-click to open the context menu.

Rename the Configuration by using the function key F2.

1989-2016 Lauterbach GmbH

Create a Podbus Device Chain.