FAQs for Host Driver

The embedded tools company

Search FAQs

PDF document ( 178KB / 17-Oct-2019 )

Communication with Acrobat Reader failed under Linux

Ref: 0343
What needs to be done ? I receive the error message regarding communication with Adobe Reader failed under Linux.

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 new plugin is also available at the download link below:

Config File PBI Parameters

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

It looks like you set in the config file:

PBI=NET ; driver to run TRACE32 without HW

But this starts the TRACE32-SW 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".

deprecated TRACE32 executable

Ref: 0480
What to do when a warning of a deprecated TRACE32 exectable 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.

ERROR about missing entrypoint EncodePointer information (Windows)

Ref: 0364
Why do I get under Windows XP the error message "The procedure entry point EncodePointer could not be located in dynamic link library KERNEL32.dll" ?

If you get one of the following Windows error messages during startup of the TRACE32 executable
  • "The procedure entry point EncodePointer could not be located in dynamic link library KERNEL32.dll" respectively
  • "Der Prozedureinsprungpunkt "EncodePointer" wurde in der DLL "KERNEL32.dll" nicht gefunden."
under Windows XP, then the PC operating system installation doesn't fulfill the following requisite:
  • Windows XP SP2 or higher

ERROR about missing entrypoint HeapSet information (WINDOWS)

Ref: 0359
Why do I get under Windows 2000 the error message "Entry point HeapSet information could not be found in dynamic Link library Kernel32.dll" ?

If you get one of the following Windows error messages during startup of the TRACE32 executable
  • "Entry point HeapSet information could not be found in dynamic Link library Kernel32.dll" respectively
  • "Der Prozedureinsprungpunkt "HeapSetInformation" wurde in der DLL "KERNEL32.dll" nicht gefunden."
under Windows 2000, then the PC operating system installation doesn't fulfill all of the following requisites:
  • Windows 2000 SP4
  • UpdateRollup for Windows 2000 SP4 (KB891861)
  • TRACE32 software version must be build 25715 or higher

File version conflict after software update or patch install

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

  • 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)

Fixed Width Font t32sys not found

Ref: 0264
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.

Floating Licenses (Virtual Prototypes)

Ref: 0303
How can I use TRACE32 for Virtual Prototypes with Floating Licenses?

TRACE32 versions from July 2008 and later support floating licenses for Virtual Prototype debugging.
  • Download and install the RLM License Administration Bundle to obtain your License Server binary and use it to look up your RLM Host ID:
  • Download the Lauterbach Certificate (lauterbach.set - for RLM this replaces the Daemon executable) and copy it into your RLM License Server installation directory.
  • Register your TRACE32 Serial Number together with your RLM Host ID.
  • When you receive your Lauterbach License File, copy it into the RLM License Server installation directory. Do NOT rename it.
  • Modify the first lines of your Lauterbach License File: replace localhost with the hostname and 5055 with the port you want to use.
  • Configure your system boot scripts to automatically start the RLM License Server.
  • Set the environment variable RLM_LICENSE=<port>@<hostname> of your RLM server.

Font Problems on Linux (Motif version)

Ref: 0158
What should I do if I get an error message about missing fonts during driver startup?

The host driver imposes several requirements for fixed fonts and font size. The font size requirement can lead to unexpected failure during startup, if one or more of the needed sizes are missing.
  • In addition to the default, FONT=SMALL and FONT=LARGE settings via config.t32, the driver supports 3 small variations of each setting.
  • On systems which use a mixed set of 8bit and 16bit menu fonts, and have only *-iso10646-* system fonts installed, no meaningful glyphs are rendered in the menu or softkeys of TRACE32 main window.

If this happens, please install the additional iso8859 system font package(s).
   e.g.  yum install xorg-x11-fonts-ISO8859-1-75dpi

Font Problems on Linux (Motif Version) II

Ref: 0334
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 .

Hidden Instance of TRACE32

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

For information about how to start TRACE32 as a hidden instance, refer to "TRACE32 as a Hidden Instance".

Interface Converter

Ref: 0333
Is it possible to use an interface converter for TRACE32?

Most available USB-to-Parallel converters can not be used to drive Parallel-Port TRACE32 tools from the PC USB interface.
Because the communication between TRACE32 and PC is timing- and latency-sensitive, and many applications in the market do not work with those converters, we do not investigate deeper about the possible reasons.
If you find 3rd party converters usable for TRACE32, please contact us.

We know one customer used a USB-to-Parallel interface converter (USB2PAR) successfully. We were told that debugging with it works, but - due to the conversion - downloading files to flash devices on the target is very slow:

Linux isn't booting anymore after installing USB driver

Ref: 0373
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.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

Mac OSX El Capitan

Ref: 0436
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:
  • boot into "Recovery mode" by immediately holding down Command + R keys when you hear the startup chime
  • open "Terminal" in the "Utilities" pulldown
  • enter "csrutil disable; reboot" and hit return
  • back in OS X 10.11 start the installation of qt-4.8
  • after qt installation boot into "Recovery mode" and open "Terminal" again
  • enter "csrutil enable; reboot" and hit return

* 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.

Minimized client windows with virtual desktops

Ref: 0402
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.

Minimum version supporting Windows 10

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

The minimum TRACE32 version supporting Windows 10 is 09/2015

Missing shared library "libstdc++.so.5"

Ref: 0324
What needs to be done? I receive the error message regarding the shared library "libstdc++.so.5".

If you have updated to a TRACE32-SW later than February 2009 on a Linux host or virt. machine - (VM) you might receive the error message:

"./t32marm: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory"

In such case you need to contact you system administrator to get this library from CD or via internet for your specific Linux machine type to install it on your host.

Here an example for details on Ubuntu and the related command:

sudo apt-get install libstdc++5 libstdc++5-3.3-dev

Starting with TRACE32 software DVD April 2010 and newer this effect doesn't occur anymore.

Missing shared library for Linux

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

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

Missing shared library for Solaris

Ref: 0300
What to do when a system library is missing ?

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

Missing shared library of new TRACE32 screen driver

Ref: 0479
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
  • 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

Multiple PODBUS USB devices

Ref: 0289
How can I use multiple USB devices with several TRACE32 instances?

More than one Lauterbach USB device can be used at the same time from the same host.
For each USB device, a TRACE32 instance needs to be started.

To use multiple USB devices with one PC or workstation, you need
  • for Windows: the current T32USB driver (see below)
  • current TRACE32 software (at least April 2007)
  • TRACE32 device firmware revision V8 or later (see below)
Please download the applicable packages here:

Network Preparation for Access by Lauterbach Support

Ref: 0209
What do I need to tell my network administrator if Lauterbach support wants direct access to my debugger?

There are cases when direct access to the TRACE32 debugger of the customer simplifies the support task for the engineers at Lauterbach a lot. But nowadays this involves usually at least 2 levels of network firewalls and various address and port translations.
What does you have to tell to your network administrator to properly configure the company firewall?
What we need:
  • Access to UDP destination port 20000 from the Lauterbach.com IP address range
What your network administrator needs to do:
  • Allow UDP destination port 20000 to debugger from Lauterbach.
  • Forward UDP destination port 20000 to debugger (if address NAT is involved).
  • Open the reverse path as well if the firewall does not do that automatically.
  • Make sure debugger firmware (VERSION.HARDWARE) is V6.9 or later (if port NAT is involved).
Simple Cisco example:
  • Entry for the IP access-list controlling the packets from Internet:
    •  permit udp   host   Your.Debugger.IP.address   eq 20000
  • Entry for the IP access-list controlling the packets to the Internet:
    •  permit udp   host   Your.Debugger.IP.address   eq 20000

No menu icons with Gnome on Ubuntu

Ref: 0396
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

No Response from InterCom

Ref: 0393
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.
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!

No TRACE32 window comes up on Unix

Ref: 0246
Why is no TRACE32 main window coming up under Unix ?

No TRACE32 main window is displayed due to one of the following reasons:
  • The TRACE32 software doesn't find the TRACE32 system directory.
    • environment variable T32SYS isn't set or points to a wrong directory
      export T32SYS=/opt/t32/bin/pc_linux        // wrong
      export T32SYS=/opt/t32                     // correct
    • SYS definition inside the TRACE32 configuration file (default name config.t32) is commented, omitted or points to a wrong or not existing directory
      SYS=/opt/t32/bin         // wrong, should be   SYS=/opt/t32
  • The hostdriver t32cde tries to open the file boot.t32 with write access and will fail, when the TRACE32 system directory respectively the file boot.t32 is write protected.
    This is a kind of file semaphore mechanism to avoid problems when several instances will boot and create Trace32 boot images at the same time.
    Please add the following lines inside the used TRACE32 configuration file (default name: config.t32):
                // empty line necessary
                // empty line necessary
    or give at least write access to the file boot.t32 via command
    e.g. chmod a+w boot.t32

PCF Bitmap Font disabled on Ubuntu

Ref: 0375
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

PerformanceCounter of PC seems to be buggy

Ref: 0356
TRACE32 says the PerformanceCounter of my PC seems to be buggy. What does this mean?

Popup menu problem under Ubuntu 10.04

Ref: 0349
Why doesn't occur a popup menu by a right-mouse button click ?

Under Ubuntu 10.04 context sensitive popup menus don't occur due to a Xserver bug.

Update to a newer xserver-common package, version 2:1.7.6-1ubuntu7.4 or later.
For 64bit kernel the additional package xserver-xorg-core, version 2:1.7.6-2ubuntu7.5 or later must be installed too.


Prerequisites for Linux

Ref: 0155
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:
  • glibc >= 2.12
  • X.org X11 >= 7.6
  • motif/openmotif >= 2.3.1 (for the Motif 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 are:
  • 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.

Prerequisites for QT GUI

Ref: 0405
What are the prerequisites for the Trace32 QT host driver(s) on Linux?

The minimum requirements for the Qt GUI are:
  • Kernel:  2.6.32
  • libc:    2.11.1
  • Qt libs: 4.6.2
Minimum versions of some popular Linux distributions:
Distribution       minimum release      required packages
  • Ubuntu             10.04               libqtcore4, libqtgui4
  • Debian              6.0                libqtcore4, libqtgui4
  • Mint                9.0                libqtcore4, libqtgui4
  • RedHat RHEL         6.1                qt, qt-x11
  • CentOS              6.0                qt, qt-x11
  • Fedora             13                  qt, qt-x11
  • SUSE SLE           11-SP1              libqt4
  • openSUSE           11.3                libqt4

Prerequisites for USB on Linux

Ref: 0156
How do I use USB with the TRACE32 host driver(s) on Linux?

In addition to the generic requirements, USB needs:
  • kernel >= 2.4 for FullSpeed USB support (12 MBit/s)
  • kernel >= 2.4.22 for HighSpeed USB support (480 MBit/s)
  • filesystem supporting USB devices
    • udev filesystem needs kernel >= 2.6
    • usbdevfs mounted on /proc/bus/usb
    • hotplug package
The udev or hotplug setup is no strict requirement, but highly recommended if you want to avoid running the TRACE32 executables as root all the time.

udev method:
cp bin/pc_linux/udev.conf/10-lauterbach.rules /etc/udev/rules.d

hotplug method:

To enable proper Trace32 hotplugging, change to the directory on the CD (or with an extracted update) with the Linux executables and issue the follwing commands in a shell:
grep -iq trace32 /etc/hotplug/usb.usermap || cat usb.usermap.trace32 >>/etc/hotplug/usb.usermap
install -m 0755 trace32 /etc/hotplug/usb/

You can verify proper operation with the t32usbchecker tool coming with the CD or update.
Minimum settings in config.t32 to use USB:
NOTE: USB can only be used with the host-based executables (name matches t32m*), NOT with t32cde.


Ref: 0421
Where is t32tcpusb, mentioned in the training manual?

If you don't find these files on your Lauterbach DVD, please download binaries for Linux and Windows here:

Sending Commands Remote via t32rem.exe

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

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".

Silent installation on Windows

Ref: 0374
How can I realize a silent installation under Windows?

1. For a simple software roll out of a company unique TRACE32 software installation
a network mount/drive will be used and the content of the TRACE32 DVD should
be in a special directory on a server
   xcopy D:\*.*  N:\TRACE32DVD_201011  /E /V /L         // drive and directory name are only an example

2. Record once a TRACE32 installation with the following instructions inside a command shell window:
   cd N:\TRACE32DVD_201011\bin\setup64                  // drive name N: and the directory is only an
                                                        // example and must be replaced by the actual
                                                        // user-defined values
   setup.exe /r /f1"N:\TRACE32DVD_201011\bin\setup64\setup.iss"
                                                        // /r stands for enabling recording the
                                                        // installation process
                                                        // /f1 defines the file which will contain the
                                                        // recorded installation actions
Step through the complete TRACE32 installation process.

3. Start a silence TRACE32 installation with the following instruction on a different PC:
   setup.exe /s /f1"N:\TRACE32DVD_201011\bin\setup64\setup.iss"   // /s means silence installation mode

A) If InstallShield didn't work correctly with a record file on the network drive, please use the following default place C:\rul\setup.iss instead.
B) If the silent installation fails during USB driver installation, please check whether the file
bin\windows*\drivers\dpinst.xml contains a line <quietInstall/>.
   <?xml version="1.0"?>
     <dpinstTitle>TRACE32 USB Device Driver Installation</dpinstTitle>

Switch off cleartype font usage

Ref: 0293
How can I reactivate the old fashioned font usage ?

Since 2008 cleartype fonts are used as default.

Please add the following lines inside the used TRACE32 configuration file (default name: config.t32) to use the old fonts:
                    // empty line necessary
                    // empty line necessary

UDP InterCom Port Collision

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

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). Please see the screenshots.

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.

USB Debugger not detected by Linux

Ref: 0157
Why is my USB debugger not detected at all by Linux?

There are a few possible reasons:
  • The currently running Linux kernel does not yet support USB
  • USB support was not enabled during Linux kernel configuration
  • USB "kernel module" support was enabled, but module auto-load failed or is not set up properly
  • usbdevfs is not mounted
  • usbdevfs is mounted, but not at /proc/bus/usb
  • using a bad USB cable: please try the original one which came with your debugger, or use 28AWG/1PR 24AWG/2C, not longer than 3 meters
  • the firmware of the debugger is too old: you need V6.5 or later
  • insufficient rights to access the USB device: please try again as root ("sudo", "su -s", or log in as root), and check with "lsusb" if you can see the device at all (Lauterbach USB devices have VendorID 0897).
  • udev.rules were not set up properly to assign the necessary directories and rights to the uSB device

USB Debugger not detected by Windows

Ref: 0279
Why is my USB debugger not detected at all by Windows or doesn't work anymore?

We've had reports that Intel 82801 USB controllers under some circumstances may cause trouble with USB 2.0 devices.
The problems should (this is unconfirmed) be fixed with the 82801F chipset series.

Plugging in a USB2.0 device to the PC (e.g. "CPU Switch Lite USB 2.0" from Lindy) could cause the effect that running other USB2.0 devices - e.g. PowerDebug Usb 2, or e.g. a USB2.0 memory stick - couldn't be accessed any more, or were not recognized from Windows anymore next time they were used.
USB1.0 devices - e.g. keyboard, mouse,... - seem not to be affected. Some issues concerning cable lengths were reported too.

In the case of "CPU Switch Lite USB 2.0" from Lindy, the problems stopped instantly when a separate USB cable was used than the USB cable that is part of the combined KVM cable (USB+VGA).
Noteworthy is the fact that the KVM USB cable part was used for keyboard and mouse functionality only.

USB problem under MacOSX

Ref: 0387
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

Using 3 GB RAM for TRACE32 task under Windows

Ref: 0211
How can I permit 3 GB memory allocation for the TRACE32 task under Windows?

The Windows system file boot.ini must be modified.
Please add boot switch /3GB.
e.g.  multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
      /fastdetect /NoExecute=OptIn /3GB
Without special bootswitch /3GB the linker option -LARGEADDRESSAWARE will be ignored!

Using TRACE32 via USB with VMware

Ref: 0278
What can I do if the USB interface is not working properly or very slowly with VMware?

These problems are caused by VMware virtualizing the USB interface.
  • VMware Player 1.x only supports USB 1.1, limiting the transfer speed to 100..300 KB/s.
  • VMware Player 2.x and later supports USB 2.0 and thus allows USB speeds up to 1.500KB/s.
    To use USB 2.0 you need to update your VMX file (virtualHW.version = "6" and ehci.present = "true").
  • If this does not help, please use TRACE32 with "real" PC hardware.
  • If your PC and TRACE32 tool have an ethernet interface available you can use ethernet together with VMware. Transfer speeds will be lower than with real hardware, too, but not as low as with USB (we observed speeds up to 50% of real hardware).
  • If you use a Virtualized Desktop environment (e.g. VMware View), added latency can also severely degrade USB performance.

WARNING about obsolete Driver (Windows only)

Ref: 0266
Why does TRACE32 warn about an obsolete driver?

You have seen this message:
   WARNING: Found active PODBUS USB device using obsolete driver.
   Please update the driver for your Lauterbach PODBUS USB Controller.
   Different USB ports may use different driver versions!
   Please see http://www.lauterbach.com/faq_hostdriver.html
   FALLBACK: connecting PODBUS USB device NUMBER=1 via obsolete driver
The USB driver you are using for TRACE32 supports an obsolete interface class that could conflict with other USB drivers.
Please note:
  • Using the old driver does not affect the functionality of your Lauterbach device or software.
  • The warning is a precaution to avoid potential problems with other USB driver software.
  • Windows Vista/XP/2003 users: Please update the driver with your latest Lauterbach CD.
  • Windows 2000/ME/98 users: A new driver is available on CDs issued after 2007-APR-18.

The new USB driver is also available at the download link below:

Windows 7 "loses" PodBus/USB device after one hour idle time

Ref: 0344
Why does my PodBus/USB device connected to Windows 7 not work anymore after some time ?

From the Microsoft Knowledge base entry with a hotfix for this problem:
"You connect a USB device to a computer that is running Windows 7 or Windows Server 2008 R2. When the computer is idle for more than one hour, the USB device may not work any longer. When this problem occurs, the USB device is not displayed in Device Manager."

Title: "USB devices that are connected to a computer may not work after the computer is idle for more than one hour Windows 7 or in Windows Server 2008 R2"

Windows 7 does not install TRACE32 USB driver

Ref: 0328
Why does Windows 7 report "installation failed" when I connect TRACE32 to USB?

When Windows 7 detects a new device and does not find a driver pre-installed or online, it reports failure (incorrectly: the TRACE32 USB driver is fully compatible with Windows 7).

How to install the driver using "TRACE32 USB Driver installer for Windows":
  • Download the "TRACE32 USB Driver installer" (t32usb_setup.exe, see link below)
  • Start the installer by double-clicking on t32usb_setup.exe
  • Follow the installation wizard

How to install the driver manually:
  • connect your TRACE32 USB Power Device and wait for the "install failed" bubble note
  • open "Device Manager" (e.g. run "devmgmt.msc")
  • right-click "Lauterbach PODBUS USB Controller"
  • select "update driver software"
  • select "search on this computer"
  • "browse" to your TRACE32 installation directory (or on the Lauterbach DVD to "bin/windows/driver")
  • "continue" to install the driver
Note_1: The installer (link below) is a self-extracting RAR file that contains the driver files and the Microsoft "Driver Package Installer" (DPinst) binaries for Windows 32bit and 64bit. (Lauterbach added "dpinstselect.exe", a small program to auto-invoke dpinst32.exe or dpinst64.exe depending on your Windows platform.)
Note_2: Due to a certificate problem (not caused by Lauterbach), with the 2010-05-28 version of the installer archive on some Windows 7 64bit installations the driver installation would succeed, but then the driver would not start. This problem has been fixed in the 2010-06-24 version of the driver binary. If you are affected, please downlod the current t32usb_setup.exe below.

Installer downloads:

Windows USB driver installation per USB port

Ref: 0348
Why do I have to install a Lauterbach PODBUS USB driver for each USB port?

Microsft Windows needs a way to assign the proper type of device driver to an instance of a device.
To achieve this for USB devices, prior to Windows 7, Microsoft did not use the USB VendorID/ProductID/bcdDevice fields, but either (a) the USB Serial Number or (b) the exact device position in the USB tree.
  • (a) If a device has a "USB Serial Number" set, each individual USB device instance used on a given PC requires an extra driver installation. In other words, if you e.g. swap a device with a co-worker, you need to install a driver.
  • (b) Without a "USB Serial Number", Windows wants a driver installed _once_ for each USB port where a certain type of device is used. (E.g. swapping devices with a co-worker does not need additional driver installation.)
  • The USB device design choice was to go for a maximum of one driver installation _once_ per (_used_!) USB port. Then you don't need to install additional drivers for any Lauterbach PodBus device with a different serial number.
  • Administrators maintaining restricted user right environments have problems with user-triggered driver installations.
  • As one pre-requisite, please use the most current installation package. E.g. the "t32usb_setup.exe" binary from this website (see download link below) is a self-extracting RAR archive that contains the Microsoft "DPinst" driver package pre-installation tool. "DPinst" copies the USB driver to the "Windows Driver Store" and allows subsequent installations to be "automatic". This should already get rid of most "restricted environment" problems.
If you still have problems, we see two possibilities to further improve the situation:
  • (1) Allow "standard users" to install the Lauterbach driver by adding the embedded driver certificate to the "Trusted Vendor" certificate store (group settings). This should enable restricted user to install the driver. (Of course you need to test this with your specific version of Windows and your set of group policy settings.)
  • (2) If all affected Host PCs are identical, a System Administrator can configure one "Template Machine" with all ports installed, and export its USB enumeration tree for the PodBus USB device type from the Registry. After installing the Lauterbach PODBUS USB driver once on a hardware- and OS-identical target machine, the administrator could then import the enumeration subtree.
    (For e.g. XP the subtree would be "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0897&Pid_0002". It is unknown if this also works on newer Windows versions. Also any added hub will change the USB tree and require additional installation.)

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: 17-Oct-2019