FAQs for TRACE32 Software

The embedded tools company

Search FAQs

PDF document ( 69KB / 21-Nov-2019 )

How can I save the memory content in Intel HEX format? Using the command Data.SAVE.IntelHex the generated address field is incorrect.
Ref: 0487

By default, Data.SAVE.IntelHEX uses 20-bit address size. For 32-bit addressing the option "/TYPE4" needs to be added.

Data.SAVE.IntelHex dump.hex 0xA0000000--0xA0003fff /TYPE4

How can I send commands remote to TRACE32?
Ref: 0265

syntax: t32rem.exe <localhost or IP address of PC> [port=<n>] <cmd>

e.g. t32rem.exe my_pcname do testfile
e.g. t32rem.exe localhost port=20123 Data.List main

T32rem.exe (not automatically installed from CD) can be used to send commands remote to a running TRACE32 application.
Here in the example it starts testfile.cmm (only cmm extensions can be omitted in the command).
Use "localhost" or the TCP/IP address of the host where TRACE32 is running. The port nummer can be omitted if it is default (= 20000).
"RCL=NETASSIST" separated by empty lines above and below has to be activated in the config file. If you use "T32Start" for configuration you can activate "RCL" by setting "API Port, Use Port" to "yes".

I get the error message "entry near offset ... in file ... (use DUMP)" when loading an object file using the Data.LOAD command.
Ref: 0485

This error message can have the following reasons:
  • The object file is corrupted. Please try to re-compile the file.
  • The object file has been compiled for a different architecture that the one started with TRACE32 PowerView. You get this error message e.g. if <ou are loading an ELF file compiled for x86 on the TRACE32 PowerView for ARM.
  • The file has a format which is not supported by your TRACE32 version. This can happen e.g. if you are using a compiler version newer that the used TRACE32 software. Please try to update to latest TRACE32 release available on the web site or request an interim software update from support@lauterbach.com.
  • The object file has a format which is not yet supported by TRACE32 PowerView. Please contact the Lauterbach support and include the object file if possible.

I get the error message "Overlapping memory location" when loading an object file using the Data.LOAD command.
Ref: 0469

This error message means that there are sections in the object file that load code or data to the same addresses which is an error in the object file. TRACE32 handles this by loading these sections in the order they appear in the object file. The command sYmbol.List.MAP can be used to check in what order the sections were loaded and which code was loaded.

Instead of getting a significant error message, I'm getting an error in the following form: "error occured, id='...'".
Ref: 0468

The help.t32 file available in the TRACE32 installation directory is probably too old. This file is used to decode the error codes in significant error messages.

Is it possible to check the progress of the execution of a TRACE32 command through the Remote API?
Ref: 0458

There is no function in the Remote API that can check the progress of the execution of a TRACE32 command. You can however call the command within a PRACTICE script and check the execution state of the script using T32_GetPracticeState().

Is it possible to see the value of a C macro in TRACE32 PowerView?
Ref: 0467

Macros are generally not part of the DWARF debug information in the ELF file. The debugger can thus not know their values. But you can declare your macros in TRACE32:
sYmbol.CREATE.MACRO MACRO_1 <contents>
sYmbol.CREATE.MACRO MACRO_2 <contents>
You can display the list of manually created macros with:
Sometimes, the compiler can also export the macro information into the ELF file. This is done for the GCC compiler using the command line -g3 option which exports the macro information in the ".debug_macinfo" section. If you are loading such an ELF use then the /MACRO option to import the macro information to TRACE32.

Is it possible to use Eclipse as debugger user interface instead of TRACE32 PowerView?
Ref: 0482

Lauterbach offers a TRACE32 integration to Eclipse based on Target Communication Framework (TCF). TRACE32 PowerView can be configured as a TCF agent. This integration is useful to access the debug functionality of TRACE32 from within an Eclipse-based interface. Simultaneous usage of TRACE32 PowerView and Eclipse is also possible.
Please note that extended TRACE32 functionality like trace views, MMU views and OS-aware debugging is not supported by this integration.
You can find more information about the TRACE32 integration to Eclipse in the application note "TRACE32 as TCF Agent"

What loader option is required to convert CYGWIN paths to DOS paths?
Ref: 0260

Data.LOAD.Elf <filename>.elf /CYGDRIVE

What's the meaning of the error message: "FATAL ERROR from InterCom-driver: can not bind read socket"?
Ref: 0320

You are using InterCom communication for TRACE32 on your PC. This was activated by a setting in the active configuration for your TRACE32-SW. Either by the InterCom setting in the T32Start configuration or inside your TRACE32 config file (default name config.t32).

The InterCom communication is typically needed if two or more TRACE32 applications shall communicate together (via UDP). This is for example needed for multicore debugging or debugging coprocessors like eTPU or PCP.

The problem is caused by using the same InterCom port address by different applications. Maybe several TRACE32 executables or other applications. You can check the used ports by command: "netstat -a" on your PC.

For TRACE32 you can avoid this problem in the configuration of T32Start by "Use Auto Increment Port: Yes". If using a config file like config.t32 you need to set a different InterCom Port manually.

Why do I get the error message "Plugged debug cable is not suitable for CPU"?
Ref: 0448

In general you get the error message "Plugged debug cable is not suitable for CPU", when the started TRACE32 application is not supported by the debug cable plugged to your PowerDebug.
E.g. The "PowerPC-4xx Debug Cable" is not suitable for "TRACE32 for ARM" (t32marm.exe)
Please start the correct TRACE32 application or connect the correct debug cable to your PowerDebug.

As a special case, you also get the error message "Plugged debug cable is not suitable for CPU" if you use TRACE32 R.2018.02 or older and you use a new debug cable that is not yet supported by that version:
  • If your ARM debug cable has a serial number starting with "C18" or higher, it is the new "ARM Debug Cable V5" (shipped since 2018). Please ensure you use TRACE32 version R.2017.02 or higher.
  • If you use the Automotive PRO cable (LA-2707), ensure you use TRACE32 R.2018.02 or higher.
You can download a suitable version of TRACE32 at https://www.lauterbach.com/7373

Why does my terminal window (TERM) not work with COM port 10 or larger?
Ref: 0290

The cause of the problem is that the function CreateFile() of Windows accepts strings
"com1" - "com9" as names of devices and reject to do so for two and more digit numbers.
In order to open "com10" and above we actually have to feed
"\\.\com10" string to CreateFile().

TERM.METHOD COM \\.\com10 38400. 8 NONE 1STOP NONE

Why does TRACE32 no longer start the script t32.cmm?
Ref: 0447

TRACE32 build 99519 (August 2018) and newer start the following scripts automatically after the application start:
  1. TRACE32 first executes the file autostart.cmm from the TRACE32 system directory (usually C:\T32).
  2. autostart.cmm normally starts then the following scripts:
    • system-settings.cmm (from the TRACE32 system directory)
    • user-settings.cmm (from the user settings directory (on Windows %APPDATA%\TRACE32 or ~/.trace32 otherwise))
    • work-settings.cmm (from the current working directory)
  3. Finally TRACE32 executes additionally the file specified on the command line (or in T32Start).
If the file autostart.cmm does not exist in the TRACE32 system directory, TRACE32 build 99519 (and later) will fallback to the previous autostart-mechanism and start t32.cmm (if no start script was specified on the command line (or in T32Start))

The file autostart.cmm will be provided by Lauterbach and should not be changed, because every software update from Lauterbach will restore the file.

Individual settings should be added in the files system-settings.cmm, user-settings.cmm and work-settings.cmm (which will not be changed by Lauterbach).

Read more on https://www.lauterbach.com/2018

Copyright © 2019 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany   Impressum     Privacy Policy
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 05-Dec-2019