FAQs for Licenses

The embedded tools company

Search FAQs

PDF document ( 59KB / 16-Oct-2019 )

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.

License Issue after Software Update

Ref: 0277
After installing a Software Update, TRACE32 complains about an invalid license and switches to demo mode.

TRACE32 checks your maintenance contract on every start.

If the end-date of your maintenance contract is older than the revision of your just installed TRACE32 software, TRACE32 switches to a limited demo mode.

The demo mode gives every user the opportunity to receive and test Software Updates. If a user decides to use the Software Update, he must purchase or renew the software maintenance contract.

  • When purchasing a debug cable or a software maintenance contract, you get free software updates for one year.
  • Lauterbach strongly recommends to make a backup copy of the TRACE32 installation directory before applying a software update.

  • No Maintenance Contract for AutoFocus-II

    Ref: 0337
    What kind of Maintenance Contract do I need for the AutoFocus-II Preprocessor?

    You do not need any Maintenance Contract for any Preprocessor. The Maintenance Contract for the CPU family you want to trace is already in your debug cable.

    RLM Floating License Client Setup

    Ref: 0363
    How do I set up TRACE32 for floating licenses from our server?

    This FAQ entry is quite large, but please be aware:
    • As a TRACE32 end-user, normally you should not need to read this.
    • Floating Licenses servers and clients are normally set up by a "License Administrator".
    • In case you have none, or s/he is not available and you need to debug NOW, this FAQ entry shall help you to set up TRACE32 to check out floating licenses.

    If the configuration file tells your TRACE32 to use a software interface (such as GDB, GDI, CADI, MCD, etc.) for debugging, TRACE32 will automatically check for a valid license in a USB dongle or via Reprise Software's License Manager (RLM) if it can check out a floating license.
    • for Windows/64bit, Linux and Solaris versions, the Floating License "Client" is built into TRACE32.
    • for Windows/32bit, you need to download t32lm.dll and place it in the TRACE32 System (=installation) directory
      (please see the "Floating Licenses (Virtual Prototypes)" FAQ entry for a link to the file).

    The Floating License Client (RLM Client) needs to know which (RLM) Server to connect to actually get the license from.
    This is not difficult, two different possibilities (any one of them will do!) are:
    • (a) you can add an environment variable "RLM_LICENSE=<port>@<rlmserver>"
      Example environment variable:
    • (b) you can make a "client license file" (e.g. CLIENT.LIC - any name is ok, but it must end with *.LIC )
      and place this in the TRACE32 System directory.
      The CLIENT.LIC file consists only of one line of text that tells the client where to find the server:
      HOST  <rlmserver>  <something>  <port>
      • rlmserver : host name or IP address of your RLM Floating License Server
      • something : one word of "something", e.g. "00000000" - on the SERVER, this contains the RLM HostID, but on a CLIENT anything that does not contain spaces should do
      • port : port number of your RLM Floating License Server

      Example CLIENT.LIC file:
      HOST rlmsrv1.mycompany.intern  00000000  5600
      Each one of the alternatives (a) or (b) will tell your TRACE32 to get the license from the server "rlmsrv1.mycompany.intern", port 5600.

    Just in case you get TWO or THREE port numbers from your administrator(s):
    On the RLM license server machine always at least two server processes will be be running, and these make at least three ports available
    • <port>: the RLM master server port
      => your CLIENT.LIC file only needs this RLM master server port number.
      (The RLM master server will tell the RLM client where to look for the ISV port.)
    • <isv_port>: the "ISV" license server daemon port.
      => This "ISV daemon" does the actual license handling.
      If you have RLM-licensed products from one or more "independent software vendors" (ISVs), for each ISV, one of these daemons must be running.
      => The only case where you need this port number is if your RLM server is behind a firewall.
      Then the firewall admin needs both port numbers to let you connect to the license server.
    • <web_port>: the RLM master server has a built-in web server
      (so your admin or you can check license status using a normal web browser).
      => you have a nice administrator. To see the license status, just go to the web site "http : // <rlmserver> : <web_port> /" (without spaces), then click on the vendor and product names to access their license status page.

    RLM HostID

    Ref: 0317
    How do I get the RLM HostID?

    • To obtain the RLM Host ID, please install the RLM End-User Bundle on your license server and invoke ’rlmutil rlmhostid’ on a command line to obtain the RLM Host ID for your machine.
    • Newer RLM versions may print several 48bit Host IDs ("ether"), older versions print a 32bit Host ID.
    • Both are suitable for licensing.
    • You can also start the RLM server executable and use the Web interface - default port is either 9000 or 5454, depending on the RLM server version - then click on 'System Info'.
    • See also: http://www.lauterbach.com/rlmhostid.html

    Several Maintenance Contracts for one DebugCable

    Ref: 0336
    Why do I need up to five maintenance contracts for one debug cable?

    You require a maintenance contract for each Lauterbach debugging product inside your debug cable. A debug cable may contain the feature keys for up to five different CPU architectures. The debug support for one of these five independent CPU architectures is a separate debugging product.

    Sources for a maintenance contract (hardware-assisted tools)

    Ref: 0453
    Where can I store my maintenance key?

  • In debug cable, CombiProbe, uTrace, Nexus Adapter
  • One or more maintenance keys can directly be stored in the configuration file
    serial_number0 expiration_date0 license_code0
    serial_number1 expiration_date1 license_code1
  • Path to license file can be stored in configuration file
  • In license.t32, that has to be in the TRACE32 SYStem directory

    The most current license found in one of these sources is used.

  • 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: 16-Oct-2019