FAQs Archive for Host Driver Software

The embedded tools company

Search FAQs

PDF document ( 140KB / 01-Oct-2020 )

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

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.

[Linux] I don't get a popup menu by a right-mouse button click?
Ref: 0349

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.


[Linux] I receive the error message regarding the shared library "libstdc++.so.5".
Ref: 0324

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.

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

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

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

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

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

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

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

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"

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

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!

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

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

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

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.

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

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

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.

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

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

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

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

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

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

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"?
Ref: 0364

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

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

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 release.
  • Windows 2000/ME/98 users: A new driver is available on TRACE32 releases issued after 2007-APR-18.

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

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

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:

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

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.

Copyright © 2020 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: 01-Oct-2020