11-05-2019 03:29 AM
We have a mix of floating and node-locked licenses. Some of the licenses for IPs are present either as floating or node-locked, but we have both node-locked and floating licenses for the Vivado tool.
The Vivado tool seems to checkout the floating license first, although there is a node-locked license available on that specific machine, making it unavailable for other machines which don't have a node locked license.
The "order" parameter in the floating license file seems to affect only the order amongst features in the that license file. Is that correct or am I missing something?
How can I make the node-locked license is checked-out before the floating license?
Thank you in advance.
11-05-2019 05:03 PM
Please take a look at the following AR for the licensing search order.
Where is the tool node locked license located?
11-06-2019 06:55 AM
Hello @vitor.schwambach ,
Please check the following AR: http://www.xilinx.com/support/answers/44024.html
From here you can see the order of which license takes precedence (please note that the "highest level of operation" (i.e. #1 rule) would only really apply to IP core licenses rather than software licenses, as software is always going to be just on or off and there are no other levels of operation)).
As you can read, your “oldest version limit” related license will always be used before one with a later version limit.
Therefore, if you have both older and newer Vivado/IP Core related licenses, you can use "sort" to prioritize the license you would like to be used first.
Just say you have an Embedded Edition Floating license and it is the license with the oldest version limit and it’s used before one with a later version limit (i.e. before your e.g. System Edition Floating license).
In this case, from this AR you can read that you can override the precedence specified in items 2, 3, and 4 of this Answer Record with the use of the "sort" directive. To use the sort directive, edit the applicable Increment lines of the license file and add "sort=1","sort=2", and so on. A lower sort value takes precedence over a higher value.
In this example, the Logic Edition increment will be used first, if available, for a license component that exists in both packages.
The same can be applied to your IP Core Floating and Node-Locked licenses.
If you have any trouble with this option or have any questions, please let me know.
Hope this helps.