TRACE32 Software-only Debugger
- Floating Licenses
- RLMCloud - Does my Company Network allow the Cloud Access?
- Reprise License Server at Customer Site - How to Get Your RLM Host ID?
- Further Information
Lauterbach provides in addition to its hardware-based debug and trace tools pure software debuggers. These debuggers are used to debug RTL simulations / emulations and virtual targets in the presilicon phase of a project, and - relatively new - to debug the target via native host interfaces such as USB.
TRACE32 Software-Only Products are licensed via TRACE32 Floating Licenses.
- Virtual Targets
- XCP
- USB and Intel® DCI.DbC
- USB and Tessent Embedded Analytics
- TRACE32 Simulators
TRACE32 Software-only Debugger
In order to use a software-only tool one or more floating licenses are required. Lauterbach is using the license management software from Reprise Software for this purpose.
Floating licenses can be hosted on a Reprise license server at customer site. The license server is identified by a 8- or 12-digit hex number named RLM Host ID (Ethernet based).
Please note that Lauterbach does not support multi-server fail-over setups with multiple different RLM host IDs. Only one license server per delivered license file is allowed to be actively used.
Floating licenses can be hosted in the RLMCloud. Licenses are managed on basis of a 12-character RLM Host Id, which is assigned by Lauterbach. Its main component is a unique Company ID. A single company can use multiple cloud servers.
RLMCloud - Does my Company Network allow the Cloud Access?
To handle licenses from the RLMCloud TRACE32 communicates via TCP to the Reprise RLMCloud server. It is mandatory to open outgoing traffic to the domain name ls54.rlmcloud.com.
Since TRACE32 Release 2023/02 two transfer modes between TRACE32 and RLMCloud are available. Either the needed ports for information exchange (port 5053 and a customer specific one) are open for outgoing traffic towards ls54.rlmcloud.com, or the transmission is based on HTTPS, which means all traffic is routed through port 443. The HTTPS based transmission is only supported for Windows, Windows64 and Linux64.
The following utilities allow to check these transfer modes. The customer specific port for the rlmcloudping utility is port 5179.
rlmcloudping Utility for Windows
rlmcloudping Utility for Windows64
rlmcloudping Utility for Linux64
rlmcloudping Utility for Linux-AARCH64
rlmcloudping Utility for MacOSX64
Reprise License Server at Customer Site - How to Get Your RLM Host ID?
1. Download the RLM Server Software and the Lauterbach ISV server settings file
Reprise Software, Inc. - RLM End-User Bundle Download
Download Lauterbach ISV server settings file
(SHA1=e20a33b749d22d49e3441358bc208906f17d95eb)
2. Install the RLM Server Software on your RLM License Server Machine
3.1. Query the RLM host ID via a Web Browser
(Note: you need a running RLM server for this!)
Go to ” http://<your.license.server>:5054/
Click on “System Info”. Ethernet: xxxxxxxxxxxx displays the 12- or
8-digit RLM host ID.
Click on “System Info”. Ethernet: xxxxxxxxxxxx displays the 12- or
8-digit RLM host ID.
2. Install the RLM Server Software on your RLM License Server Machine
(Note: you need a running RLM server for this!)
If there is more than one value for the Ethernet ID, please send all of them. Lauterbach usually uses the first listed RLM host ID.
Open a command shell on your RLM License Server machine, and invoke the command
[/rlm_installation_path/]rlmutil.exe rlmhostid -ether
3.1.2. Query the RLM host ID via the rlmutil Utility on Linux
(Note: you need a running RLM server for this!)
If there is more than one value for the Ethernet ID, please send all of them. Lauterbach usually uses the first listed RLM host ID.
Open a command shell on your RLM License Server machine, and invoke the command
If there is more than one value for the Ethernet ID, please send all of them. Lauterbach usually uses the first listed RLM host ID.
Open a command shell on your RLM License Server machine, and invoke the command
[/rlm_installation_path/]rlmutil rlmhostid -ether
The result looks like this:
Further Information
