You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/install-guides/armclang.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,16 +44,13 @@ Arm Compiler for Embedded FuSa must also be [downloaded separately](#download).
44
44
45
45
Individual compiler packages for all supported host platforms can be downloaded from the [Arm Product Download Hub](#pdh) or the [Arm Tools Artifactory](#artifactory).
46
46
47
-
Individual compiler packages for all supported host platforms can be downloaded from the [Arm Product Download Hub](https://developer.arm.com/downloads) or the [Arm Tools Artifactory](https://www.keil.arm.com/artifacts/).
48
-
49
47
### Product Download Hub {#pdh}
50
48
51
-
All compiler packages can be downloaded from the [Arm Product Download Hub](https://developer.arm.com/downloads) (requires login):
49
+
All compiler packages can be downloaded from the [Arm Product Download Hub](https://developer.arm.com/downloads) (requires login).
52
50
53
-
-[Arm Compiler for Embedded](https://developer.arm.com/downloads/view/ACOMPE)
54
-
-[Arm Compiler for Embedded FuSa](https://developer.arm.com/downloads/view/ACOMP616)
51
+
Download links to all available versions are given in the [Arm Compiler downloads index](https://developer.arm.com/documentation/ka005198).
55
52
56
-
These can either be used standalone or [integrated](#armds) into your Arm Development Studio installation.
53
+
All compiler versions can be used standalone or [integrated](#armds) into your Arm Development Studio installation.
57
54
58
55
See also: [What should I do if I want to download a legacy release of Arm Compiler?](https://developer.arm.com/documentation/ka005184)
Arm Compiler for Embedded and Arm Compiler for Embedded FuSa are license managed. License setup instructions are available in the [Arm Licensing install guide](/install-guides/license/).
121
+
`Arm Compiler for Embedded` and `Arm Compiler for Embedded FuSa` are license managed.
122
+
123
+
License setup instructions are available in the [Arm Licensing install guide](/install-guides/license/).
Copy file name to clipboardExpand all lines: content/install-guides/license/_index.md
+3-11Lines changed: 3 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,9 @@ multitool_install_part: false # Set to true if a sub-page of a multi-page arti
16
16
layout: installtoolsall # DO NOT MODIFY. Always true for tool install articles
17
17
---
18
18
19
-
Most Arm commercial tools are license managed. Arm is migrating to user-based licensing (UBL) which greatly simplifies license configuration. It is available for [Arm Success Kits](/install-guides/successkits/) as well as [Arm Development Studio](/install-guides/armds).
19
+
Most Arm commercial tools are license managed. Arm is migrating to user-based licensing (UBL) which greatly simplifies license configuration.
20
20
21
-
Success kits are available as `Hardware Success Kits` (`HSK`) or `Software Success Kits` (`SSK`). See the table below for tooling provided. SSK is a subset of HSK.
22
-
23
-
With UBL, you have unlimited access to all components in the success kit you have enabled. The license is cached locally for up to 7 days, enabling remote or traveling users to access tools without connecting to their license server.
21
+
A user-based license is cached locally for up to 7 days, enabling remote or traveling users to access tools without connecting to their license server.
24
22
25
23
Starting any UBL enabled tool when the server is available will renew the license for 7 more days. This renewal attempt is performed once per 24 hours.
26
24
@@ -52,10 +50,4 @@ Legacy product versions do not support UBL licensing and use FlexLM [floating li
52
50
53
51
## User-based Licensing Video Tutorials
54
52
55
-
In addition to the set up and install instructions below, a collection of video tutorials are available on the Arm Developer website:
56
-
57
-
*[Accessing the Arm License Portal](https://developer.arm.com/Additional%20Resources/Video%20Tutorials/User-based%20Licensing%20-%20Accessing%20the%20Arm%20License%20Portal)
58
-
*[Cloud-based Licenses and Activation Codes](https://developer.arm.com/Additional%20Resources/Video%20Tutorials/User-based%20Licensing%20-%20Cloud-based%20Licenses%20and%20Activation%20Codes)
59
-
*[Local License Server Setup](https://developer.arm.com/Additional%20Resources/Video%20Tutorials/User-based%20Licensing%20-%20Local%20License%20Server%20Setup)
*[Removal of Licenses and Decommissioning Server](https://developer.arm.com/Additional%20Resources/Video%20Tutorials/User-based%20Licensing%20-%20License%20Removal%20and%20Decommissioning%20Server)
53
+
In addition to the set up and install instructions below, a collection of video tutorials are available on [Arm Developer](https://developer.arm.com//Tools%20and%20Software/User-based%20Licensing).
Copy file name to clipboardExpand all lines: content/install-guides/license/ubl_license_enduser.md
+7-18Lines changed: 7 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,23 +15,17 @@ layout: installtoolsall # DO NOT MODIFY. Always true for tool install ar
15
15
16
16
A [Local License Server (LLS)](/install-guides/license/ubl_license_admin/) must first be set up by your license administration team.
17
17
18
-
{{% notice Notice%}}
19
-
A Software Success Kit is a subset of a Hardware Success Kit.
20
-
21
-
You should confirm which type of license is appropriate for your needs.
22
-
{{% /notice %}}
23
-
24
18
## Activate license on end user machine
25
19
26
-
The UBL license can be activated on the end user machine in different ways. Select the most appropriate for your needs.
20
+
The user-based license can be activated on the end user machine in different ways. Select the most appropriate for your needs.
27
21
28
22
*[Activate via environment variable](#envvar)
29
23
*[Activate within tools IDE](#ide)
30
24
*[Activate manually](#manual)
31
25
32
26
## Activate via environment variable {#envvar}
33
27
34
-
Create `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.
28
+
Create `ARMLM_ONDEMAND_ACTIVATION` environment variable referencing the product code and your internal license server. Contact your internal license administrators for information on your internal server.
@@ -84,7 +73,7 @@ You should see an output similar to:
84
73
Hardware Success Kit
85
74
Product code: HWSKT-STD0
86
75
Order Id: xxxxxxxx
87
-
License valid until: 2023-12-31
76
+
License valid until: 2025-12-31
88
77
Local cache expires in: 6 days and 23 hours
89
78
License server: https://internal.ubl.server
90
79
```
@@ -93,7 +82,7 @@ Hardware Success Kit
93
82
94
83
Your license is cached on your local machine, and is valid for 7 days.
95
84
96
-
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.
85
+
There will be an automatic attempt to refresh this license once per 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.
97
86
98
87
To manually refresh the license, you can deactivate and reactivate your license (when connected to your network). For example:
0 commit comments