FAQs for Host Driver Software
|[Linux] How do I enable icons on the pull down menus on Ubuntu?|
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?|
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".|
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?
The TRACE32 host driver for Linux tries to be distribution independent and is currently only available for Linux/x86 and Linux/x86_64 (Linux/PPC and Linux/ARM on request).
Nevertheless there are some requirements inherited through the build environment.
Starting with release 2018/02 on Linux/x86 and Linux/x86_64 these are:
Release 2019/09 introduced official Qt5 support for Linux/x86_64 with these additional requirements:
For releases 2017/09 and earlier the requirements are:
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?|
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?|
Generally you will have to install the corresponding package (which contains the missing library), too.
|[Linux] What to do when a warning of a deprecated TRACE32 executable occurs?|
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?|
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.rulesNo ^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?|
The minimum version for USB debuggers on OS X El Capitan is 10.11.4.
If the Qt4.8 libraries area not installed, follow these steps:
* Notes regarding OS X 10.11 El Capitan:
Installation of qt-4.8 must be done with "System Integrity Protection" disabled, otherwise it won't succeed.
|[Solaris] libm.so.2 not found.|
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:
su 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"?|
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?|
The minimum TRACE32 version supporting Windows 10 is 09/2015
|How do I start a hidden instance of TRACE32?|
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.
SCREEN= INVISIBLEOption 2: The main window of TRACE32 and all other dialogs and windows of TRACE32 remain hidden - even if an error occurs.
SCREEN=OFFOption 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.
SCREEN= VICONPlease refer for more information refer to "TRACE32 as a Hidden Instance" in the TRACE32 Installation Guide.
|What could be the reason for the "no response from InterCom" message?|
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.
SETUP.INTERCOMACKTIMEOUT <time>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 to do when a TRACE32 screen driver library is missing?|
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
|Why are some or all client windows minimized, when switching virtual desktops?|
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?|
|Why do I get the error message "FATAL EROR from PODBUS-driver: could not get nodename"?|
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?|
It looks like you set in the config file:
PBI=NET 18.104.22.168 ; driver to run TRACE32 without HWBut 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:
PBI= NET ; host interface to connect to TRACE32 HW NODE=22.214.171.124You can find a complete description in the installation manual "installation.pdf".
Copyright © 2020 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany
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: 10-Jan-2020