FAQs Archive for Host Driver Software

• 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

• 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

TRACE32 firmware update

• 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
    

• 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
  

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

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

TRACE32 USB Driver installer for Windows and Linux (32bit and 64bit)

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

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

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

• 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
    

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

   e.g.  yum install xorg-x11-fonts-ISO8859-1-75dpi

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

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

TRACE32 USB Driver installer for Windows and Linux (32bit and 64bit)

• 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 and Linux (32bit and 64bit)