Nexys 4 Board Vivado许可证收到错误

这是一个非常基本的问题，但我无法让我的新Nexys 4板进行编程。
我为Vivado生成了一个webpack .xml许可证，并使用许可证管理器激活它。
我正在尝试实现随板提供的演示项目，但是我收到以下错误：
[Common 17-345]找不到功能'Synthesis'和/或设备'xc7a100t'的有效许可证。
请运行Vivado License Manager以获取有关确定哪些功能和设备已获得系统许可的帮助。
我相信Vivado v14.2支持Nexys 4，xc7a100t芯片。
我该如何解决这个问题？
谢谢！



以下为原文

This is a very basic problem, but I am having trouble getting my new Nexys 4 board to program.  I generated a webpack .xml license for Vivado and activated it using the License Manager.  I am trying to implement the demo project that came with the board, but I am getting the following error:
 
[Common 17-345] A valid license was not found for feature 'Synthesis' and/or device 'xc7a100t'. Please run the Vivado License Manager for assistance in determining which features and devices are licensed for your system.
 
I believe Vivado v14.2 support the Nexys 4, xc7a100t chip. 
 
How should I try to resolve this?  Thanks!

webpack 2014.2支持Artix100t设备。
请确保您拥有运行2014.2的有效许可证。我猜您可能对许可证文件有版本限制以在2014年合成设计。请参阅http://forums.xilinx.com/t5/Installation-and
-Licensing / Vivado-2013-3-can-t-find-license / td-p / 380081获取更多信息.Regards，Krishna
--------------------------------------------------
---------------------------------------------请将帖子标记为
如果提供的信息能够回答您的问题/解决您的问题，请“接受为解决方案”。给予您认为有用的帖子。



以下为原文

The webpack 2014.2 supports Artix100t device. Please make sure that you have a valid license to run 2014.2.

I guess you may have a version limit on the license file to synthesize the design in 2014.2.

Please refer to http://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2013-3-can-t-find-license/td-p/380081 for more information.

Regards,
Krishna-----------------------------------------------------------------------------------------------
Please mark the post as "Accept as solution" if the information provided answers your query/resolves your issue.

Give Kudos to a post which you think is helpful.

所以这是许可管理器下面显示的内容，如果它有帮助：
我不认为它是版本限制，因为它到2015.07，对吧？



以下为原文

So this is what shows up under the license manager if it helps:
 

 
I don't think it's a version limit since it goes to 2015.07, right?

以下为原文

 

嗨，你能在tcl控制台中运行以下tcl命令并分享结果吗？1。
report_environment -file output.txt 2. xlicclientmgr -vThanks，Vinay
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi,

Can you run the below tcl commands in tcl console and share the outcome?

1. report_environment -file output.txt
2. xlicclientmgr -v

Thanks,
Vinay--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

这是你需要看到的输出吗？
report_environment -file output.txtINFO：[Common 17-635]现在获取报告信息。
这可能需要一些时间：[通用17-633]获取系统信息...信息：[通用17-632]获取软件环境信息...信息：[通用17-629]获取Vivado首选项...信息
：[Common 17-630]获取安装信息... INFO：[Common 17-628]获取DLL信息... INFO：[Common 17-631]获取许可证信息... INFO：[Common 17-634] Done
获取报告信息.xlicclientmgr -vWARNING：[Common 17-259]未知Tcl命令'xlicclientmgr -v'向OS shell发送命令以执行。如果不信任，则查看应用程序可信存储.U
D如果禁用。
。
fulfillmentType。
。
。
到期计数FulfillmentId ProductId。
。
6永久0 211458705 209855574查看1个履行记录中的1个。



以下为原文

Is this the output you need to see?
 
report_environment -file output.txt
INFO: [Common 17-635] Now fetching report information.  This may take some time.
INFO: [Common 17-633]     Fetching system information...
INFO: [Common 17-632]     Fetching software environment information...
INFO: [Common 17-629]     Fetching Vivado preferences...
INFO: [Common 17-630]     Fetching installation information...
INFO: [Common 17-628]     Fetching DLL information...
INFO: [Common 17-631]     Fetching license information...
INFO: [Common 17-634] Done fetching report information.
xlicclientmgr -v
WARNING: [Common 17-259] Unknown Tcl command 'xlicclientmgr -v' sending command to the OS shell for execution.
Viewing application trusted storage.

U if untrusted
. D if disabled
. . fulfillmentType
. . . Expiry   Count FulfillmentId                   ProductId

. . 6 permanent    0 211458705                       209855574

Viewed 1 of 1 fulfillment records.

嗨，在这里附上生成的output.txt。你会发现这是工作目录[pwd]。谢谢，Vinay
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi,

Attach the generated output.txt here.
You will find this is present working directory [pwd].

Thanks,
Vinay--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

附！
output.txt 66 KB



以下为原文

Attached!
            output.txt ‏66 KB

嗨，
从output.txt我们可以看到，对于许可证功能Vivado_WebPACK，主机ID不匹配。
您是否在生成基于激活的Vivado WebPack许可证时使用了Dongle？
加密狗是否还在插上机器？
问候，
肖恩
--------------------------------------------------
-----------------------不要忘记回答，kudo，并接受为解决方案.-------------
--------------------------------------------------
----------



以下为原文

Hi,
 
From the output.txt we can see that for license feature Vivado_WebPACK, Host ID does not match.
Were you using Dongle when you generated the Activation based Vivado WebPack license? Is the dongle still pluging on the machine?
 
Regards,
Sean
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

嗨，
您需要重新托管许可证。
为此，您将使用AR＃60525中的步骤将旧的Vivado WebPack许可证返回给Xilinx，然后生成一个新许可证。
问候，
肖恩
--------------------------------------------------
-----------------------不要忘记回答，kudo，并接受为解决方案.-------------
--------------------------------------------------
----------



以下为原文

Hi,
 
You need to re-host  the license. In order to do that you will return the old Vivado WebPack license to Xilinx with the steps in AR# 60525 and then generate a new one.
 
Regards,
Sean
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------