ARM® DS-5™ v5 License Management Guide Copyright ©2011-2012 ARM. All rights reserved. ARM DUI 0577E (ID092812) ARM DS-5 License Management Guide Copyright ©2011-2012 ARM. All rights reserved. Release Information The following changes have been made to this book. Change History Date Issue Confidentiality Change 29th March 2011 A Non-Confidential First release 30 September 2011 B Non-Confidential Update 1 for DS-5 29 February 2012 C Non-Confidential Update 2 for DS-5 29 Jul 2012 D Non-Confidential Update 3 for DS-5 12 October 2012 E Non-Confidential Update 4 for DS-5 Proprietary Notice Words and logos marked with ® or ™ are registered trademarks or trademarks of ARM® in the EU and other countries, except as otherwise stated below in this proprietary notice. Other brands and names mentioned herein may be the trademarks of their respective owners. Neither the whole nor any part of the information contained in, or the product described in, this document may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this document is subject to continuous developments and improvements. All particulars of the product and its use contained in this document are given by ARM in good faith. However, all warranties implied or expressed, including but not limited to implied warranties of merchantability, or fitness for purpose, are excluded. This document is intended only to assist the reader in the use of the product. ARM shall not be liable for any loss or damage arising from the use of any information in this document, or any error or omission in such information, or any incorrect use of the product. Where the term ARM is used it means “ARM or any of its subsidiaries as appropriate”. Confidentiality Status This document is Non-Confidential. The right to use, copy and disclose this document may be subject to license restrictions in accordance with the terms of the agreement entered into by ARM and the party that ARM delivered this document to. Product Status The information in this document is final, that is for a developed product. Web Address http://www.arm.com ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. ii ID092812 Non-Confidential Contents ARM DS-5 License Management Guide Chapter 1 Conventions and feedback Chapter 2 Introduction 2.1 Supported platforms ................................................................................................ 2-2 2.2 Tool licensing schemes ........................................................................................... 2-3 2.3 Types of license ....................................................................................................... 2-4 2.4 Node-locked license scheme ................................................................................... 2-5 2.5 Floating license scheme .......................................................................................... 2-6 2.6 ARM License Manager ............................................................................................ 2-9 2.7 ARM web licensing portal ...................................................................................... 2-10 Chapter 3 Requesting Your License 3.1 Accessing the ARM web licensing portal from the License Manager ...................... 3-2 3.2 Information required for a license ............................................................................ 3-4 Chapter 4 Using a Node-Locked License 4.1 Installing a node-locked license using the ARM License Manager .......................... 4-2 4.2 Installing a node-locked license manually (Windows only) ...................................... 4-3 4.3 Installing a node-locked license manually (Unix/Linux only) .................................... 4-4 Chapter 5 Using a Floating License 5.1 Configuring the client licensing ................................................................................ 5-2 5.2 Using the ARM License Manager ............................................................................ 5-3 5.3 Using the Control Panel (Windows clients only) ...................................................... 5-4 5.4 Using the Command line (Unix/Linux clients only) .................................................. 5-5 Chapter 6 Frequently Asked Questions about Licensing 6.1 How does FlexNet find a license file? ...................................................................... 6-2 ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. iii ID092812 Non-Confidential Contents 6.2 Can I use FlexNet with more than one product? ..................................................... 6-3 6.3 How do I combine licenses? .................................................................................... 6-4 6.4 How do I find my product serial number? ................................................................ 6-5 6.5 How do I move my license to another computer? .................................................... 6-6 6.6 Do the ARM development tools support BORROW? .............................................. 6-7 6.7 Do ARM licenses support queuing? ........................................................................ 6-8 6.8 Why can I not find the lmhostid utility? .................................................................... 6-9 6.9 What is the format of a license entry? ................................................................... 6-10 Chapter 7 Troubleshooting client configuration 7.1 License apparently missing error ............................................................................. 7-2 7.2 My node-locked tools fail with FlexNet error -8: Invalid license key (inconsistent authentication code) ................................................................................................ 7-3 7.3 How can I change the order in which my license sources are accessed? ............... 7-4 7.4 How can I optimize floating license checkout times? ............................................... 7-5 7.5 Can I use a remote floating license server? ............................................................ 7-7 7.6 Why am I getting FlexNet error -15: Cannot connect to floating license server system? 7-8 Chapter 8 Troubleshooting server configuration 8.1 How can I run my FlexNet server more securely? ................................................... 8-2 8.2 Server debug log reports “Invalid license key (inconsistent authentication code)” .. 8-3 8.3 Can I define the order in which licenses in a mixed version license file are issued? 8-4 8.4 How can I tell how many floating licenses are in use? ............................................ 8-5 8.5 Server debug log reports “(armlmd) cannot open lock file” or “cannot communicate with lmgrd” ....................................................................................................................... 8-6 8.6 What version of the floating license server daemons must I use? ........................... 8-7 8.7 How can I limit user access to particular licensed features? ................................... 8-8 8.8 Why am I getting “DENIED” messages in the server log? ..................................... 8-10 8.9 How can I manage the size of the server debug log file? ...................................... 8-11 Chapter 9 Setting Up a Floating License Server 9.1 Installing the server software ................................................................................... 9-2 9.2 Installing a floating license ....................................................................................... 9-4 9.3 Starting a floating license server .............................................................................. 9-5 9.4 Shutting down a floating license server ................................................................... 9-8 Chapter 10 ARM License Manager Diagnostic Utility 10.1 armlmdiag utility ..................................................................................................... 10-2 Glossary ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. iv ID092812 Non-Confidential Chapter 1 Conventions and feedback The following describes the typographical conventions and how to give feedback: Typographical conventions The following typographical conventions are used: monospace Denotes text that can be entered at the keyboard, such as commands, file and program names, and source code. monospace Denotes a permitted abbreviation for a command or option. The underlined text can be entered instead of the full command or option name. monospace italic Denotes arguments to commands and functions where the argument is to be replaced by a specific value. monospace bold Denotes language keywords when used outside example code. italic Highlights important notes, introduces special terminology, denotes internal cross-references, and citations. bold Highlights interface elements, such as menu names. Also used for emphasis in descriptive lists, where appropriate, and for ARM® processor signal names. Feedback on this product If you have any comments and suggestions about this product, contact your supplier and give: • your name and company • the serial number of the product • details of the release you are using ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. 1-1 ID092812 Non-Confidential Conventions and feedback • details of the platform you are using, such as the hardware platform, operating system type and version • a small standalone sample of code that reproduces the problem • a clear explanation of what you expected to happen, and what actually happened • the commands you used, including any command-line options • sample output illustrating the problem • the version string of the tools, including the version number and build numbers. Feedback on content If you have comments on content then send an e-mail to [email protected]. Give: • the title • the number, ARM DUI 0577E • if viewing online, the topic names to which your comments apply • if viewing a PDF version of a document, the page numbers to which your comments apply • a concise explanation of your comments. ARM also welcomes general suggestions for additions and improvements. ARM periodically provides updates and corrections to its documentation on the ARM Information Center, together with knowledge articles and Frequently Asked Questions (FAQs). Other information • ARM Information Center, http://infocenter.arm.com/help/index.jsp • ARM Technical Support Knowledge Articles, http://infocenter.arm.com/help/topic/com.arm.doc.faqs • You can find documentation for using the ARM web licensing portal on the portal itself. ARM web licensing portal, https://silver.arm.com You can download the latest version of the Flexera Licensing End User Guide from the Tools Licensing section under ARM Technical Support Knowledge Articles. Ensure that you use the version compatible with the license utilities you are using. The document is also supplied as a PDF with your ARM product. See the Getting Started document of your ARM product for more information. • ARM Glossary, http://infocenter.arm.com/help/topic/com.arm.doc.aeg0014-/index.html • Flexera Software, http://www.flexerasoftware.com/ ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. 1-2 ID092812 Non-Confidential Chapter 2 Introduction The following topics give an overview of the license management software: • Supported platforms on page2-2 • Tool licensing schemes on page2-3 • Types of license on page2-4 • Node-locked license scheme on page2-5 • Floating license scheme on page2-6 • ARM License Manager on page2-9 • ARM web licensing portal on page2-10. ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. 2-1 ID092812 Non-Confidential Introduction 2.1 Supported platforms You must ensure that Eclipse for DS-5 is supported on your chosen platform before installing it. If you are also setting up one or more floating license servers, you must confirm that the license management utilities are supported on the server. 2.1.1 Client platforms Caution Attempting to use an unsupported client platform can result in unexpected behavior. Check the product documentation to confirm what specific operating system variants are supported. 2.1.2 Floating license server platforms Caution Attempting to use an unsupported server platform can result in licensing failures. Check the product documentation to confirm what specific operating system variants are supported. The floating license server platform is not required to be the same as the tools platform. For example, you might have your development tools installed on Windows and use a Linux floating license server. See your product documentation for further information. License management of floating licenses for ARM applications requires TCP/IP software to be installed, configured, and running on every relevant computer. ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. 2-2 ID092812 Non-Confidential Introduction 2.2 Tool licensing schemes Eclipse for DS-5 is license managed by FlexNet Publisher software from Flexera, that uses FlexNet technology. This means that a valid license file must be installed before DS-5 can be used. The following licensing schemes are available: • Node-locked license scheme on page2-5 • Floating license scheme on page2-6. The licensing scheme that is used is selected when the product is purchased. If you want to change the licensing scheme that you are using, you must contact ARM License Support. 2.2.1 Licensing options for remote working The following options are available for remote users: • Install a license server with a floating license. Remote users can check-out licenses from the server, provided that network access is available. • For a node-locked license, obtain a license that is registered to: — The host ID of the machine used by the remote user. — The MAC address of a USB Ethernet card. This card can then be plugged into any machine that has the ARM DS-5 tools installed. ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. 2-3 ID092812 Non-Confidential Introduction 2.3 Types of license A license is a text file containing information about the type of license, how long the license lasts and what applications it is used for. The following types of license are supported: Permanent A permanent license does not have an expiry date. Using the fromelf utility as an example, the format of a permanent license is: INCREMENT fromelf armlmd 5.0201105 permanent ... If you fulfill your license in May 2010 you can use 5.0 and any new patches that are released up to end of May 2011. If your license period is limited by a Service and Maintenance (S&M) agreement, and the period lapses, your version of the product, together with any patches you received within that period continues to function as normal. However, if you want to use a patch that is later than this date, you must purchase another S&M license. If you then purchase an additional two-year license, the new license includes: UPGRADE fromelf armlmd 5.0201305 permanent ... If you fulfill your license in May 2010, 5.0201305 gives a user three years entitlement to download and use patches. Term A term license has a specific expiry date. For example: INCREMENT fromelf armlmd 5.0201205 31-July-2012 ... This means you can use version 5.0 and any new patches to fromelf that are released before the end of May, but you get a license expiry error after the 31st July 2012. 2.3.1 See also • What is the format of a license entry? on page6-10. ARM DUI 0577E Copyright ©2011-2012 ARM. All rights reserved. 2-4 ID092812 Non-Confidential