FAQs for Host Driver

TRACE32 Acrobat Reader Plugin (Linux platforms) (434K)

PBI=NET 11.22.33.44 ; driver to run TRACE32 without HW

PBI=
NET                 ; host interface to connect to TRACE32 HW
NODE=11.22.33.44

Section of the installation manual: (21K)

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

• Windows XP SP2 or higher

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

• Windows 2000 SP4
• UpdateRollup for Windows 2000 SP4 (KB891861)
• TRACE32 software version must be build 25715 or higher

• The new TRACE32 executable isn′t copied manual to an old previous installation directory.
  The internal subdirectory structure of the update packages has been changed since software version November 2010.
  Now the TRACE32 executables are inside a subdirectory bin\<operating_systemtype> e.g. bin\windows64.
  For older installations the executable must be moved manual to the TRACE32 system directory e.g. C:\t32 or the shortcut property must be corrected.
  
  We recommand to modify the shortcut property, due to the fact that this kind of subdirectory structure will be used from the installer in the future too.
  
  
• 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.

  OS=
  ID=T32
  SYS=<new system directory>
  tmp=C:\temp
  

  Otherwise the version of the executable doesn´t match with the rest of the TRACE32 files.

• Download and install the RLM End-User Bundle to obtain your License Server binary and use it to look up your RLM Host ID:
  http://www.reprisesoftware.com/enduser_downloads.htm
• 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 line of your Lauterbach License File: replace the placeholders with hostname and port.
• Configure your system boot scripts to automatically start the RLM License Server.
• Make a client license file (or set the corresponding RLM environment variable).
• For Windows 32bit clients only: Download and unpack the Floating License Client DLL (t32lm.dll) and copy it into the TRACE32 installation directory of your clients.

TRACE32 Floating License HowTo (printable) (43K)
Lauterbach Certificate (for RLMv7.0 and all later versions) (1K)
Lauterbach Client DLL for Windows 32 bit (RLMv4.0BL4 and later) (175K)

Reprise License Manager End-User Bundle Download

• 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
  

Example of one USB to Parallel Converter (from TU Chemnitz) (21K)

cat -et /etc/udev/rules.d/10-lauterbach.rules

# 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

e.g. ld.so.1: t32marm: fatal: libm.so.2: open failed: No such file or directory killed

su
ln -s /usr/lib/libm.so.1 /usr/lib/libm.so.2

• for WINDOWS: the current T32USB driver (see below)
• current TRACE32 software (at least April 2007)
• TRACE32 device firmware revision V8 or later

USB multi device update procedure (128K)
Windows USB driver package (all platforms) (79K)

• Access to UDP destination port 20000 from the Lauterbach.com IP address range 192.149.90.0/24.

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

• Entry for the IP access-list controlling the packets from Internet:

   permit udp   192.149.90.0   0.0.0.255   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   192.149.90.0   0.0.0.255
  

   SETUP.URATE <time> or <frequency>

   SETUP.INTERCOMACKTIMEOUT <time>

1. The TRACE32 software doesn′t find the TRACE32 system directory.
   • environment variable T32SYS isn′t set or points to a wrong directory
     e.g.

     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
     e.g.

     OS=
     SYS=/opt/t32/bin         // wrong, should be   SYS=/opt/t32
     

2. 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
   BOOT=
   NOLOCK
               // empty line necessary
   

   or give at least write access to the file boot.t32 via command

   e.g. chmod a+w boot.t32
   

The message basically means that the performance counters used by Windows XP on your machine performs buggy: The timers values are not monotonically increasing as they should for every timer.
This is a general problem with the platform you are using and is not just related to TRACE32.

TRACE32 is using the function QueryPerformanceCounter of the Windows API which is the only correct way to get a time value with microseconds accuracy. However with Windows XP and Windows 2003 running on a dual core CPU, a value returned by QueryPerformanceCounter can be smaller that a value just fetched before with QueryPerformanceCounter. When this happens the first time the message box pops up.
The problem can occur on any dual core CPU from any CPU manufacturer.

It is recommend to set option "/usepmtimer" in your boot.ini. (See Microsoft kb289022, kb833721, kb895980)
This option forces Windows to use a different timer (ACPI Power Management Timer) for microseconds accuracy which operates correct (monotonically increasing).
Why does Windows not always use "/usepmtimer" if this is so much better?
Well, the CPU needs a little bit more time to access this other timer. Anyway the option is nowadays recommend by AMD (and set when you install the AMD CPU driver).

If you are using TRACE32 inside a VMware virtual machine it is strongly recommended not to use option "/usepmtimer".
Details on the VMware Knowledge Base KB Article: 1011714

Note: On TRACE32 build 24984 to build 25568 the message "PerformanceCounter of my PC seems to be buggy" can appear by mistake. On this builds it is pretty likely that the message appears after one hour of continuous operation.

The problem is not fatal. It is not very likely that debugging won′t work because of this microseconds timer bug.

See also:

Article 895980 on Microsoft Support "Programs that use the QueryPerformanceCounter function may perform poorly in Windows Server 2000, in Windows Server 2003, and in Windows XP"
Article 1011714 on VMware Knowledge Base "QueryPerformanceCounter behaves improperly inside a virtual machine when /usepmtimer is used with some Windows HALs"

• glibc >= 2.3.4
• X.org X11 >= 6.8.2

• glibc >= 2.5
• X.org X11 >= 6.9

• 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
    or
  • usbdevfs mounted on /proc/bus/usb
  • hotplug package

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

su
grep -iq trace32 /etc/hotplug/usb.usermap || cat usb.usermap.trace32 >>/etc/hotplug/usb.usermap
install -m 0755 trace32 /etc/hotplug/usb/
exit

PBI=
USB

   xcopy D:\*.*  N:\TRACE32DVD_201011  /E /V /L                   // drive and directory name are only an example

   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

   setup.exe /s /f1"N:\TRACE32DVD_201011\bin\setup64\setup.iss"   // /s means silence installation mode

                    // empty line necessary
SCREEN=
FONT=NOCLEARTYPE
                    // empty line necessary

Error Message (20K)
t32start setting (6K)
Config file setting (5K)

• The running kernel does not support USB yet.
• USB not enabled during kernel configuration
• USB enabled as modules in the kernel configuration, but module autoload did fail or is not configured.
• usbdevfs is not mounted.
• usbdevfs is mounted, but not at /proc/bus/usb.
• Bad USB cable, use the original one or make sure it is at max. 3 meters long 28AWG/1PR 24AWG/2C.
• Old debugger firmware, you need V 6.5 or later.

TRACE32 firmware version

e.g.  multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
      /fastdetect /NoExecute=OptIn /3GB

• VMware Player 1.x only supports USB 1.1, limiting the transfer speed to 100..300 KB/s.
• VMware Player 2.x does support 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).

   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

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

Windows USB driver package (all platforms) (79K)

Microsoft KnowledgeBase Entry #978258

• 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

• 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

TRACE32 USB Driver installer for Windows XP/Vista/7 (32bit and 64bit) (604K)

To achieve this for USB devices, Microsoft does 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.

• If a device has (a) 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.
• 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.)

Administrators maintaining restricted user right environments have problems with user-triggered driver installations.

As a pre-requisite, they should use the most current installation package. E.g. the "t32usb_setup.exe" binary from this website is a self-extracting RAR archive that contains the Microsoft DPinst driver package pre-installation tool. This "DPinst" copies the USB driver to Windows driver store and allows "automatically install" for subsequent installations. This should already get rid of most "restricted environment" problems.

If you still have problems, we see two possibilities to further ameliorate 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. You need to test this with your specific version of Windows and your set of group policy settings, of course!
• (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 an 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 would work on Windows versions newer than XP. Also any added hub will change the USB tree and require additional installation.)