|Reading time:||15 min|
|Last updated:||15 Sep 2023|
|15 Sep 2023|
This guide is intended to get you up and running with this tool quickly with the most common settings. For a thorough review of all options, refer to the official documentation.
A Local License Server (LLS) must first be set up by your license administration team.
A Software Success Kit is a subset of a Hardware Success Kit.
You should confirm which type of license is appropriate for your needs.
The UBL license can be activated on the end user machine in different ways. Select the most appropriate for your needs.
ARMLM_ONDEMAND_ACTIVATION environment variable referencing the Success Kit product code and your internal UBL license server. Contact your internal license administrators for information on your internal server.
A license will be automatically checked out whenever a UBL enabled tool is run, for example:
You can now confirm your license has been checked out .
The license can also be activated in the various Arm tool IDEs.
Arm Development Studio
Arm License Manager >
Manage Arm User-Based Licenses.
Activate with >
License Server, and enter the appropriate license server address. Click
Query to see what license types are available, and select the appropriate one from the pull down. Click
Open a command prompt, and navigate to the bin directory of any UBL enabled product.
Activate an appropriate success kit license with
armlm activate --server https://internal.ubl.server --product HWSKT-STD0
armlm activate --server https://internal.ubl.server --product SWSKT-STD0
To confirm you have checked-out a license, enter the command:
You should see an output similar to:
1 active product in your local cache: Hardware Success Kit Product code: HWSKT-STD0 Order Id: xxxxxxxx License valid until: 2023-12-31 Local cache expires in: 6 days and 23 hours License server: https://internal.ubl.server
Your license is cached on your local machine, and is valid for 7 days.
There will be an automatic attempt to refresh this timer on the first usage of a UBL enabled tool in a day. If that fails (for example, if tools are run whilst not connected to your network) the tools can still be used provided there is still time on the locally cached license.
To manually refresh the license, you can deactivate and reactivate your license (when connected to your network). For example:
armlm deactivate --server https://internal.ubl.server --product SWSKT-STD0 armlm reactivate --server https://internal.ubl.server --product SWSKT-STD0
Verify that you have refreshed successfully with:
How would you rate the overall quality of this tool quick-install guide?