Analog Devices VisualDSP 50 Licensing Guide Rev 14

							VisualDSP++ 5 Licensing Guide 6-7 Troubleshooting
Question: I have an evaluation license and was working with an 
emulator/simulator debug session until today, when I started receiving error 
messages. Why cant I connect to my emulator/simulator debug session any 
more?
Answer: An EZ-KIT Lite license incorporates an initial 90-day full 
license. Once the 90 days have passed, the evaluation license becomes 
restricted, prohibiting simulator and emulator debug sessions and restrict-
ing the amount of internal memory that is available for code (program 
memory). Refer to Licensing Overview for further details.
Question: I’m getting errors when trying to use VisualDSP++ with Remote 
Desktop. What could be the problem?
Answer: VisualDSP++ did not support connection through Remote Desk-
top before VisualDSP++ 5 and, in fact, actively disallowed it with 
node-locked licenses prior to this release. 
If you are using VisualDSP++ 4.5 or earlier, try using a single-session 
remote access application, such as VNC. However, note that we offer no 
support for this.
If you are using VisualDSP++ 5, you may still be unable to use remote 
desktop if you used the advanced option to copy over your 
license.dat 
file from an earlier version of tools during installation of the latest tools. If 
your 
license.dat was copied from an earlier release of the tools, we rec-
ommend that you rename you current 
license.dat file, which can be 
found in the System folder of your VisualDSP++ 5 installation, to 
license_old. Then you will need to reinstall your license number and 
obtain a new, VisualDSP++ 5 compatible, validation code. 
						

							Frequently Asked Questions (FAQs)
6-8 VisualDSP++ 5 Licensing GuideQuestion: I’m running VisualDSP++ on Windows Vista (or Windows 7) 
and having some problems with my license. I can’t find the license.dat file my 
colleague installed. What’s going on?
Answer: With the release of Windows Vista, Microsoft has introduced a 
new security feature called User Account Control (UAC). UAC is a frame-
work that, when enabled, provides a more secure operating environment 
for the user, which prohibits modification of critical system directories 
and files. One of these directories is the 
Program Files directory into 
which VisualDSP++ is installed when selecting the default setup options.
Licenses in VisualDSP++ are stored in a file called 
license.dat located 
within the 
System directory of your VisualDSP++ installation folder. 
When installing a new license with UAC enabled, changes to the 
license.dat file will be redirected to the current user’s VirtualStore 
directory. Because 
VirtualStore directories are specific to each user, this 
has the added side effect that other users on the machine will not have 
access to these licenses when using VisualDSP++. 
To solve this, manually copy the 
license.dat file from the first user’s 
VirtualStore directory into the \System directory. The 
VirtualStore is located in:
C:\Users\\AppData\Local\VirtualStore\Program 
Files\Analog Devices\VisualDSP x.y\System
.
where 
 is the name of the user who originally installed the 
license, and 
x.y is the version of VisualDSP++ into which the license was 
installed.
For details, refer to “Windows Vista Compatibility in VisualDSP++ 5.0 
Development Tools” (EE-330) at 
http://www.analog.com/en/processors-dsp/blackfin/products/appli-
cation-notes/resources/index.html
.  
						

							VisualDSP++ 5 Licensing Guide 6-9 Troubleshooting
If using Windows 7 or later, refer to DOC-1190 on the FAQ page at 
http://ez.analog.com. 
						

							Frequently Asked Questions (FAQs)
6-10 VisualDSP++ 5 Licensing Guide
VisualDSP++ Floating License Server-Specific FAQs
Question: The LMTOOLS are asking for a *.lic file, but can’t find one. Why 
not? I’ve already installed my serial number.
Answer: The LMTOOLS application accepts license files with both the 
.lic and .dat extension. By default, when browsing for a license file, 
LMTOOLS looks for files with a 
.lic extension. Simply change the Files 
of type field to the 
.dat extension and you should find your license.dat 
file.
Question: How do I check whether my FLEXnet service is running?
Answer: This can be checked by starting the FLEXnet LMTOOLS and 
clicking Perform Status Enquiry on the Server Status tab.
You can also check in the following way. Note the service name in the 
Service Name field of the Config Services tab. Then go to Administrative 
To o l s in the Windows Control Panel and start the Services program. In 
the list of services in the right-hand panel, check that the status of your 
service is Started. If it is not, go to the Start/Stop/Reread tab in 
LMTOOLS and click the Stop Server button and then click the Start 
Server button.
If this also fails, locate the debug log file indicated on the Config Services 
tab of LMTOOLS and send it to Support. For more information, refer to 
Licensing Support.
Question: How do I use FLEXnet Licensing with more than one product? 
Can I combine license.dat files?
Answer: Yes, FLEXnet can manage licensing for multiple products, and 
there are several ways to achieve this. Full details on using FLEXnet licens-
ing with more than one product is outside the scope of this document;  
						

							VisualDSP++ 5 Licensing Guide 6-11 Troubleshooting
refer to the section entitled “Managing Licenses from Multiple Vendors” 
in the FLEXnet Licensing End User’s Guide.
Should you require further assistance, contact Macrovision.
However, one method that has shown to be successful is to run the 
FLEXnet server on one machine, running only one license server system. 
In this case, ensure that each service run by LMTOOLS (including those 
for products other than VisualDSP++) uses the same version of the 
lmgrd.exe, and that lmgrd.exe is the latest version installed.
This can be done by renaming the existing 
lmgrd.exe in each vendor’s 
FLEXnet (formerly named FLEXlm) folder, to move it out of the way, and 
then copying in the latest version available to replace it. Alternatively, you 
can change the Path to the lmgrd.exe field on the Config Services tab in 
LMTOOLS for each service, so that it points to the most up-to-date 
lmgrd.exe file.
Question: How do I move my Floating License Server to a new machine?
Answer: Set up your new license server(s) and reinstall your client licenses 
to point to this new server (as outlined in Installing a Floating License 
Server). Re-register each serial number with the host ID of the new server 
(Registering and Validating Your License). Once you have done this, 
e-mail 
[email protected], requesting that the 
old machine(s) be removed from your registration history. Be sure to 
include all relevant serial numbers and host IDs. A registration history will 
be provided upon request.
Once your new server is up and running, disable the old server.
Question: I’ve upgraded to VisualDSP++ 5 and also need to upgrade 
my Server License software. Will I still be able to use older versions of 
VisualDSP++ with the new version of the server software? 
						

							Frequently Asked Questions (FAQs)
6-12 VisualDSP++ 5 Licensing GuideAnswer: The Floating License Server is compatible with all VisualDSP++ 
versions greater than and including VisualDSP++ 4.0. 
If anyone on your network is working with the ADSP-218x or 
ADSP-219x architectures and therefore needs to run VisualDSP++ 3.5 
for 16-bit Processors, refer to the following question/answer, or contact 
Support for assistance. For more information, refer to Licensing Support.
Question: You state that the latest version of the Floating License Server tools 
are not compatible with VisualDSP++ 3.5. However, I need to use 
VisualDSP++ 3.5 for 21xx on the same network as Im using 
VisualDSP++ 5. Is there a way around this?
Answer: There are a number of ways to do this; one example is given 
below. If this does not cover your particular circumstance, contact Sup-
port. For more information, refer to Licensing Support.
Example: If you have an existing installation of VisualDSP++ 3.5 that uses 
floating licenses, do the following:
1. Save the existing 
license.dat file on your server to a safe place, 
as a precaution. 
2. Disable and uninstall your license server tools.
Note that uninstalling the Floating License Server tools (formerly 
known as the License Server Manager) from Add/Remove pro-
grams leaves the install path, and your 
license.dat file, intact in 
the 
C:\Program Files\Analog Devices\VisualDSP\LMSERVER 
directory. This means that you can re-use your original 
license.dat file. 
3. In your 
license.dat file, comment out any license strings for any 
architectures other than 21xx. This can be done by placing a “
#” 
at the start of each line; for example: 
						

							VisualDSP++ 5 Licensing Guide 6-13 Troubleshooting
# FEATURE FRIO-FULL analogd 1.0 3-aug-2007 5 DDDDEEEEFFFF \
# VENDOR_STRING=ADI-111-11111-111111-10
# INCREMENT FRIO-FULL analogd 1.0 permanent 5 AAAABBBBCCCC\
# VENDOR_STRING=ADI-111-11111-111111-10
Note: License strings can be found after the line: 
# Begin FEATURE definitions”.
4. Install the latest version of the Floating License Server (currently 
version 5.0.1.x). Since your original 
license.dat file should still 
be in the 
C:\Program Files\Analog Devices\VisualDSP\LMSERVER 
directory, the new tools should detect it, and any further serial 
numbers installed through the VisualDSP++ License Manager will 
be appended to it.
5. Re-install any SHARC, TigerSHARC, or Blackfin serial numbers 
you wish to use. Be sure to register and validate them within 30 
days.
6. Use FLEXnet LMTOOLS to configure and run the License Server.
See Installing a Floating License Server for further details of how to per-
form the above procedure. If you have problems with the above procedure 
or have any questions, contact Support.
Question: I have to add additional licenses to the License Server. How do I do 
this?
Answer: The license server must be stopped first via the FLEXnet 
LMTOOLS STOP/START/READ utility in the Configure Services win-
dow. Then follow the procedure as outlined in Task 2: Installing a Server 
License. You must then restart the server. 
						

							Frequently Asked Questions (FAQs)
6-14 VisualDSP++ 5 Licensing GuideQuestion: How do I install both a node-locked license and floating license on 
the same machine?
Answer: Follow this procedure.
1. Install and validate (if necessary) your node-locked license on your 
client machine. Follow the procedure outlined in Installing a 
Node-Locked License.
2. Install and validate your floating license on your server machine. 
Follow the procedure outlined in Installing a Floating License 
Server.
3. Copy the “
# Begin FEATURE” section along with the node-locked 
license string from 
\System\license.dat on the 
client machine to the end of the “
# Begin FEATURE” section of the 
\VisualDSP\LMSERVER\license.dat file on your server machine.
4. Install the client 
license.dat file part of your floating license on 
the client machine by following the procedure outlined in Install-
ing a Floating License Server. This will replace your node-locked 
license.dat file with one that simply points to the server. The 
existing 
license.dat file will be renamed to license.bak so that 
the information contained in it is preserved.
Note: Users on other client machines may receive an error message 
regarding the node-locked license, should all floating licenses be in 
use at the time they try to check one out.
For further information, refer to Q&A article QA0000555 in the 
Processors and DSP Knowledge Base on the Analog Devices Web 
site at
http://www.analog.com/processors/knowledgebase. 
						

							VisualDSP++ 5 Licensing Guide 6-15 Troubleshooting
Question: I’m having trouble getting my floating license to work. My server 
machine and/or my client machine has a firewall running. Could this be the 
problem?
Answer: Yes. You may need to make some changes to your floating license 
setup in order to workaround this. Contact Support for further 
information.
Question: I’m installing a floating license and Corporate IS policies prohibit 
shared network folders on my server machine. Are there any alternatives to 
installing client licenses?
Answer: Yes. An alternative method of installing a client license, which 
doesn’t require the creation of a shared network folder or use of the Visu-
alDSP++ GUI, is to simply copy the 
\LMSERVER\client-license.dat file to each client 
machine’s 
\System folder, and rename it to license.dat.
Error Messages
This section describes:
General Error Messages
VisualDSP++ Floating License Server-Specific Errors
Warning Messages
General Error Messages
General error messages include:
Errors Issued in Message Boxes
Errors Issued in the Output Window or on the Command Line 
						

							Error Messages
6-16 VisualDSP++ 5 Licensing Guide Errors Issued in Message Boxes
Problem: The serial number has already been used and can be installed only 
once.
Solution: The serial number you are trying to install has already been 
installed on this machine. Note that evaluation and test drive serial 
numbers may only be installed once per machine. In addition, test drive 
serial numbers may not be installed if an evaluation license for the same 
architecture has already been installed on that machine. For further infor-
mation, refer to Licensing Overview.
Problem: The serial number already exists. You will need to register the serial 
number to receive a validation code. If you already have a validation code, 
select the serial number and click the Validate button.
Solution: VisualDSP++ found the serial number you entered; it is already 
in the 
licence.dat file. If you have already installed that serial number 
but have not yet registered it and received a validation code, follow the 
steps outlined in Registering and Validating Your License.
Problem: The serial number you entered is invalid. Please re-enter the num-
ber, ensuring that you type the number EXACTLY as shown on the 
registration card.
Solution: Ensure that you have typed in the correct serial number, exactly 
as given. If you continue to have problems, contact Support, sending your 
serial number and 
\System\license.dat file, if avail-
able. For more information, refer to Licensing Support.