Professional Documents
Culture Documents
Int Tornado
Int Tornado
Int Tornado
TRACE32 Directory
TRACE32 Index
Overview .................................................................................................................................. 2
Installation ............................................................................................................................... 4
Installation of the Backend on Windows NT 4
Version 25-Oct-2019
Overview
The interface integrates the Tornado tool set (WindRiver Systems) and TRACE32. This chapter describes
the agentless version.
Architecture-independent information:
• “Debugger Basics - Training” (training_debugger.pdf): Get familiar with the basic features of a
TRACE32 debugger.
Architecture-specific information:
• “Processor Architecture Manuals”: These manuals describe commands that are specific for the
processor architecture supported by your debug cable. To access the manual for your processor
architecture, proceed as follows:
• “OS Awareness Manuals” (rtos_<os>.pdf): TRACE32 PowerView can be extended for operating
system-aware debugging. The appropriate OS Awareness manual informs you how to enable the
OS-aware debugging.
The interface consists of a program fragment, so called "Back End" ("trace32.dll" in Windows). This is
dynamically linked to the target server of Tornado. The back-ends available are:
The Tornado tools communicate with the target server, and the target server creates requests to the back-
end. The backend then builds socket based requests to the TRACE32 software. The requests are executed
and answered by the TRACE32 software. The answer goes exactly the same way backwards.
All requests are answered by the TRACE32 device, but not by the target resident debug agent! That
means, that the target debug agent is not needed and not used inside the target; however it does not disturb
the operation if present.
2. Copy the files "trace32.dll" and “trace32d.dll” (from the TRACE32 subdirectory
“demo\env\tornado\host\”) to your Tornado directory "${WIND_BASE}\host\x86-
win32\lib\backend".
3. Start Tornado
5. Click “New”
7. Edit your "config.t32" file of the TRACE32 installation: Add between two empty lines the following
entry, if not already there:
RCL=NETASSIST
PACKLEN=1024
When starting a target server (i.e. starting the backend), some requests to the target are performed to get
information. For this reason it is important to ensure a specific startup sequence.
3. Load your application into the debugger a/o target and start it.
4. Now you can start the target server with the appropriate backend.
Simple Example
The distribution contains a simple example, which is working in the TRACE32 Simulator, i.e. no target is
needed. This example may also serve as an installation verification.
Open Tornado and open the target server configuration dialog. Select the TRACE32 agentless connection.
Select the “Target Server Properties” -> “Core File and Symbols”. Select “File:” and point to the “vxworks” file
of the example. Click “Launch”.
As already mentioned, the TRACE32 backend has a complete different way of operation as the other back-
ends. While the wdb back-ends generate for each request a call to the target debug agent, the TRACE32
backend does not know any debug agent at all. For example, all memory requests are answered by the
debugger and could be done via the dual port memory, i.e. not affecting the application. So the TRACE32
backend can be used with agentless targets. However, you can leave your debug agent in the target and use
it for a second connection e.g. wdbserial. But be aware, that Tornado can be confused by using two debug
connections on the same target.
Simple memory reads and writes (e.g. "i" in the host resident windsh) can be done, while the application is
running in real time (when memory is mapped internal for dual port access). When using an ICD, for all
memory accesses the target is halted for a short period of time. Service calls or function calls are not
implemented. Debugging with the Tornado Debugger is not supported.
• Win32: Tornado recognizes the back-end only, if the file name is all in lower characters.