FAQs for Host Driver Software

The embedded tools company

Search FAQs

PDF document ( 190KB / 27-Mar-2022 )

[Linux] After release 2021/02 PowerView no longer starts with a Qt GUI on Ubuntu 16.04. What can I do?
Ref: 0570

Starting with release 2021/02 Qt4 is no longer supported and the Qt5 minimum is 5.6. But Ubuntu 16.04 Xenial comes with Qt-5.5.1, which is too old for PowerView.
If you have control over your Ubuntu installation either upgrade to a newer version (18.04 or later) or use external PPAs to update your Qt5 packages on Ubuntu 16.04.

[Linux] How do I enable icons on the pull down menus on Ubuntu?
Ref: 0396

On Ubuntu/Gnome the menu icons are off by default.
To enable the menu icons:
gconftool-2 --type Boolean --set /desktop/gnome/interface/menus_have_icons True

[Linux] How to add the TRACE32 font directory under Fedora distributions?
Ref: 0334

To add the TRACE32 font directory permanently to the system font directory list, you might do:

e.g. ln -s /opt/t32/fonts /etc/X11/fontpath.d/t32-fonts

Please don't forget to invoke the mkfontdir command inside the directory /opt/t32/fonts for building a fontdirectory file named fonts.dir .

[Linux] I receive the error message "Communication with Acrobat Reader failed".
Ref: 0343

If you use an Acrobat Reader version higher than 7 on a Linux host, you might receive the error message:

"Communication with Acrobat Reader failed - check if plugin <trace32.api> is started correctly"

In such case you need to update the plugin trace32.api on your host.
The newest plugin version is also available at the download link below:

[Linux] What are the prerequisites for the TRACE32 host driver(s) on Linux?
Ref: 0155

The TRACE32 host driver for Linux tries to be distribution independent and is currently only available for Linux/x86_64 (Linux/PPC and Linux/ARM64 on request).
Nevertheless there are some requirements inherited through the build environment.

From Release 2021/02 onwards the requirements for Linux/x86_64 are:
  • glibc >= 2.17
  • motif/openmotif >= 2.3.1 (for the Motif/CDE version)
  • Qt5 >= 5.6 (for the Qt version)
These requirements resolve for example to RHEL >= 7, Suse SLE >= 12 or Ubuntu >= 18.04

For releases 2018/02 to 2020/09 on Linux/x86 and Linux/x86_64 the requirements were:
  • glibc >= 2.12
  • X.org X11 >= 7.6
  • motif/openmotif >= 2.3.1 (for the Motif/CDE version)
  • Qt4 (not Qt5) >= 4.6.2 (for the Qt version)
These requirements resolve for example to RHEL >= 6, Suse SLE >= 11 or Ubuntu >= 10.10

For releases 2017/09 and earlier the requirements were:
  • glibc >= 2.5
  • X.org X11 >= 6.9
These requirements resolve for example to RHEL >= 5 or Suse >= 10.

In any case make sure you have all available X font packages (especially both the 75dpi and 100dpi versions) of your distribution installed to get the best possible display.

[Linux] What to do if I get a error message under Ubuntu regarding PCF bitmap fonts?
Ref: 0375

After installation of TRACE32 for Ubuntu and trying to use the TRACE32 fonts you might get an error message like:

FATAL ERROR from X-windows: XFT available, but not working with PCF bitmap fonts.
Please check your FontConfig configuration, possibly bitmap fonts are explicitly disabled.

To enable the PCF bitmap fonts please use the following settings inside Ubuntu:

# "Un-disable" bitmap fonts
sudo rm /etc/fonts/conf.d/70-no-bitmaps.conf
# Clear the font cache
# (path for the T32 font directory is an example, adjust according to your installation)
sudo fc-cache -f -v ~/t32/fonts

[Linux] What to do when a system library is missing?
Ref: 0298

Generally you will have to install the corresponding package (which contains the missing library), too.

  1. Fedora7:
    error while loading shared libraries: libXp.so.6: cannot open shared object file: No such file or directory
    yum install libXp # note the upper case "X" and lower case "p"

  2. RHEL5/64bit:
    /opt/t32/bin/pc_linux/t32mppc: error while loading shared libraries: libXmu.so.6: wrong ELF class: ELFCLASS64
    Not all necessary 32-bit packages are installed.
    The 32-bit "libXmu" package and all it's dependencies should be installed.

  3. Ubuntu 12.04/64bit:
    error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
    sudo apt-get install libjpeg62

  4. OpenSUSE 13.1/64bit:
    error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
    Install missing package libjpeg62 with YaST

    error while loading shared libraries: libXp.so.6: cannot open shared object file: No such file or directory
    Install missing package libXp6 with YaST

[Linux] What to do when a warning of a deprecated TRACE32 executable occurs?
Ref: 0480

Under Linux there were two executables for each architecture: "t32m*" and "t32m*-qt" in the past (before 29 June 2019).
With the new shared library mechanism, "t32m*-qt" is replaced by a notify bash script.

If you get a warning after a TRACE32 software update like
Warning: starting /home/t32/bin/pc_linux/t32marm-qt is deprecated, see https://www.lauterbach.com/3737

please replace the executable name "t32m*-qt" by the corresponding name "t32m*" (without " -qt ") in your start script or command line.

[Linux] Why isn't Linux booting after installing USB driver file 10-lauterbach.rules?
Ref: 0373

If a Linux system isn't booting anymore after the TRACE32 USB driver files 10-lauterbach.rules was installed, then please check, whether an irritating CR character is inside this file or not.
A check can be done with command:
cat -et /etc/udev/rules.d/10-lauterbach.rules
No ^M should be displayed at all.

In the directory /dev/lauterbach/trace32 you can find a lot of links from system devices which shouldn't exists there (e.g. audio, disk, dvd, ..)

# conversion steps
# if package tofrodos isn't already installed
sudo apt-get install tofrodos
cd /etc/udev/rules.d/
# converts all CF+LF pairs to LF
sudo fromdos -d 10-lauterbach.rules

[MacOS] What can I do if the USB interface is not working on MacOSX 10.11 El Capitan?
Ref: 0436

The minimum version for USB debuggers on OS X El Capitan is 10.11.4.

[Solaris] libm.so.2 not found.
Ref: 0300

error while loading shared libraries:
e.g. ld.so.1: t32marm: fatal: libm.so.2: open failed: No such file or directory killed

This happens when a TRACE32 executable built for Solaris 10 is used on Solaris 8.
Please request a Solaris 8 executable from Lauterbach.

As a temporary workaround, you can create a libm.so.2 soft link with:
ln -s /usr/lib/libm.so.1 /usr/lib/libm.so.2

[Windows] How do I proceed if I get the error message "Fixed width font t32sys not found"?
Ref: 0264

When you start TRACE32 the fonts are loaded. If you update your TRACE32 software and the update package includes TRACE32 fonts, these new fonts will not be activated as long as the old fonts are loaded. This happens even when old and new font file are identical.
Reboot your Windows PC.

[Windows] What is the minimum TRACE32 version that supports Windows 10?
Ref: 0483

The minimum TRACE32 version supporting Windows 10 is 09/2015

How do I start a hidden instance of TRACE32?
Ref: 0404

There are three ways to configure TRACE32 to start as a hidden instance by adding different SCREEN= options in the configuration file (e.g. config.t32). Choose one of the configuration options:

Option 1: The main window of TRACE32 remains hidden. However, dialogs and other window of TRACE32 can still be opened. This is useful, for example, if an error occurs during a regression test.
Option 2: The main window of TRACE32 and all other dialogs and windows of TRACE32 remain hidden - even if an error occurs.
Option 3: The main window of TRACE32 is added to the toolbar of the host computer. It can be fully displayed in case of an error.
Please refer for more information refer to "TRACE32 as a Hidden Instance" in the TRACE32 Installation Guide.

SYStem.Option.FREEZE seems not to have any influence on the timers/counters. Is it possible to let the timers/counters run even when a breakpoint is hit or the cores are halted?
Ref: 0416

The SYStem.Option.FREEZE setting just uses the debug related registers to influence the timer / counter behavior when the target enters the debug halted state.
QorIQ CPUs typically offer an additional register in the RCPM, called CTBHLTCR or TTBHLTCR.
If the corresponding bit for a specific core in this register
  • is set to 1, the SYStem.Option.FREEZE setting can handle both: To let the timers run or to freeze them during the core is in the debug halted state.
  • is set to 0, the timers will always be frozen in the debug halted state, regardless of the SYStem.Option.FREEZE setting.

What could be the reason for the "no response from InterCom" message?
Ref: 0393

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) as that could be the case in AMP Multicore debug sessions.

The "no response from InterCom" message appears if the default time-out of 500ms to acknowledge an InterCom command exceed. That typically happens if several PoverView Instances have to share the bandwidth of only one debug port. The needed bandwidth could be reduced by decreasing the update rate for each TRACE32 application.
   SETUP.URATE <time> or <frequency>
If that is not sufficient or the resulting update rate becomes unacceptable the InterCom acknowledge time-out could be increased since Build Revision 34366 with following command as well.
The default InterCom command acknowledge time-out has been hold as low as possible to keep PRACTICE execution performance, in case of non-existent InterCom participants, in an acceptable range!

What is the best way to connect to the TRACE32 harware remotely e.g. from home office?
Ref: 0307

Please refer to the following link:

What to do when a TRACE32 screen driver library is missing?
Ref: 0479

Since 26 June 2019 Lauterbach implemented a new screen driver model to support different GUI frameworks. The GUI specific software parts were split out into shared libraries (t32screen*).

If one of the following shared object files
  • t32screencde.so (for UNIX)
  • t32screenqt4.so (for UNIX)
  • t32screenqt5.so (for UNIX)
  • t32screenwin.dll (for Windows)
or a related shared library is missing, detailed troubleshooting and background information can be found under https://www.lauterbach.com/3737

Why are some or all client windows minimized, when switching virtual desktops?
Ref: 0402

Some window managers minimize the client windows when switching to other virtual desktops and back. In such a case add the line
to the screen section of your config file.

This workaround has some side effects:

When closing the main TRACE32 window, normally all entries of the client windows in the taskbar will be removed and only the entry of the main window will remain.
With activated workaround entries of client windows, which are closed before the main window, will remain in the task bar.

Why do I get a file version conflict after software update?
Ref: 0378

  • When the TRACE32 software for more than one processer architecture is installed in the same TRACE32 system directory, but not a software update for all architectures is done.

  • When the update package is used without a preceding TRACE32 software installation.
    The software update doesn´t contain a config file. If you create a copy of the original config file, please don´t forget to adapt the system directory in the config file.
    SYS=<new system directory>
    Otherwise the version of the executable won´t match with the rest of the TRACE32 files.

  • This problem can be encountered if you are updating from a software version older than November 2010 due to a change in the internal subdirectory structure of the update packages starting from software version November 2010.
    In software version from November 2010 and newer, the TRACE32 executables are located inside a subdirectory bin\<operating_systemtype> e.g. bin\windows64.

    We recommend to use the new directory structure and to possibly modify showrtcuts that are calling the TRACE32 executables directly from the installation directory (e.g. C:\T32)

Why do I get the error message "FATAL EROR from PODBUS-driver: could not get nodename"?
Ref: 0387

If you use a TRACE32 PowerDebug/USB module on a Mac OS-X host, you might receive the error message:

"FATAL EROR from PODBUS-driver: could not get nodename"

In this case the firmware version of the PowerDebug/USB module is too old.
Please use a Windows or Linux host to update at least to version V8.x.
The current firmware version and a PRACTICE script for updating is available on your Lauterbach TRACE32 Software DVD, in the directory files/demo/etc/hardware or can be download from

Why does the connection to my debugger via ethernet fail? It starts always as a "Serial Monitor" instead?
Ref: 0318

It looks like you set in the config file:

PBI=NET ; driver to run TRACE32 without HW

But this starts the TRACE32 software as a monitor program for connection via ethernet.
If you want to connect to a TRACE32 HW by ethernet you need to write the keyword to a second line instead:

NET          ; host interface to connect to TRACE32 HW

You can find a complete description in the installation manual "installation.pdf".

Copyright © 2023 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: 02-Jan-2023