无法在Vivado 2017.4中合成xczu9部分，但可以在2017.2中使用

嗨@caballes，
Vivado 2017.3及更高版本的工具需要新的LMGRD实用程序版本11.14才能正确提取浮动许可证。
请注意，主机上需要新的MSVCC可分发版本，特别是适用于Windows操作系统的MSVCC 2015。
我已附上以下文档以协助安装和设置过程。
我还包括了我们的版本限制兼容性图表，以及显示Vivado软件所需的许可证版本。
在您的情况下，您需要2017.12及更高版本的限制才能使用2017.4工具。
https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2017-3-Licensing-Changes/td-p/799675https://www.xilinx.com/support/answers/69969.html
https://www.xilinx.com/support/answers/33770.html
谢谢你，德文
在原帖中查看解决方案



以下为原文

Hi @caballes,
 
The Vivado 2017.3 and later tools require the new LMGRD utilities version 11.14 for the floating licenses to pull correctly.  Note that a new MSVCC distributable version is required on the host machine, specifically MSVCC 2015 for Windows operating systems. I have attached the documentation below to assist in the install and setup process. I have also included our version limit compatibility chart as well showing what version of the license is required for the Vivado software. In your case you would need a version limit of 2017.12 and higher to work with the 2017.4 tools.

https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2017-3-Licensing-Changes/td-p/799675
https://www.xilinx.com/support/answers/69969.html
https://www.xilinx.com/support/answers/33770.html
 
Thank you,
Devin
View solution in original post

嗨@caballes，
Vivado 2017.3及更高版本的工具需要新的LMGRD实用程序版本11.14才能正确提取浮动许可证。
请注意，主机上需要新的MSVCC可分发版本，特别是适用于Windows操作系统的MSVCC 2015。
我已附上以下文档以协助安装和设置过程。
我还包括了我们的版本限制兼容性图表，以及显示Vivado软件所需的许可证版本。
在您的情况下，您需要2017.12及更高版本的限制才能使用2017.4工具。
https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2017-3-Licensing-Changes/td-p/799675https://www.xilinx.com/support/answers/69969.html
https://www.xilinx.com/support/answers/33770.html
谢谢你，德文



以下为原文

Hi @caballes,
 
The Vivado 2017.3 and later tools require the new LMGRD utilities version 11.14 for the floating licenses to pull correctly.  Note that a new MSVCC distributable version is required on the host machine, specifically MSVCC 2015 for Windows operating systems. I have attached the documentation below to assist in the install and setup process. I have also included our version limit compatibility chart as well showing what version of the license is required for the Vivado software. In your case you would need a version limit of 2017.12 and higher to work with the 2017.4 tools.

https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2017-3-Licensing-Changes/td-p/799675
https://www.xilinx.com/support/answers/69969.html
https://www.xilinx.com/support/answers/33770.html
 
Thank you,
Devin

德文，
谢谢回复。
我还是卡住了。
我们的Linux许可证服务器正在运行Flexlm实用程序v11.14,1。
刚刚在今天早些时候证实了
由于我们使用Linux，我们不需要MSVCC更新，对吧？许可证管理器显示我们的基于证书的浮动许可证的版本限制为2018.10。
我试过两次重启机器但没有成功。
还有其他提示吗？
再次感谢。



以下为原文

Devin,
 
Thanks for the reply.  I'm still stuck.  Our Linux license server is running the Flexlm utilities v11.14,1.  Just confirmed that earlier today.  Since we are using Linux, we don't need the MSVCC update, right? The license manager shows that our Certificate based floating license has a version limit of 2018.10.   I tried rebooting the machine twice already with no success.  Any other hints?
 
Thanks again.   

嗨@ CABALLES，
1.您在Vivado 2017.4上使用哪个Linux版本？
2.运行“report_environment -file env.txt”tcl命令并提供要评估的env.txt文件。
3.提供您在合成阶段所面临的确切错误的快照。
4.提供您要定位的确切零件名称。
问候，
hemangd



以下为原文

Hi @caballes, 
 
1. Which linux version you are using for Vivado 2017.4?
2. Run "report_environment -file env.txt" tcl command and provide  env.txt file to evaluate. 
3. Provide the snapshot of  the exact error which you are facing in synthesis phase.
4. Provide the exact part name which you want to target.
 
Regards,
hemangd

你好@ CABALLES，
你可以打开航行到这个位置，例如：../ xilinx / Vivado_2017.3 / Vivado/2017.3 / bin / unwrapped / lnx64.o然后从这里运行这个命令：lmutil lmstat-a -c @（eglmutil lmstat
-a-c 2100 @ ANATOLI_PC）
然后请查看lmgrd是否已启动且xilinxd是否也已启用，然后查看服务器启动的flexlm实用程序的版本？
你看到lmgrd和xilinxd的v11.14吗？
你能确认吗？
亲切的问候，Anatoli Curran，Xilinx技术支持-----------------------------------------
--------------------------------不要忘记回复，工作，并接受解决方案.----
--------------------------------------------------
-------------------



以下为原文

Hello @caballes,
 
Can you please open navigate to the location such as e.g.: ../xilinx/Vivado_2017.3/Vivado/2017.3/bin/unwrapped/lnx64.o and then from here, please run this command: lmutil lmstat –a –c @ (e.g.lmutil lmstat –a –c 2100@ANATOLI_PC)
Then please see if lmgrd is UP and xilinxd is UP too and then, see what version of flexlm utilities the server is/was started with? Do you see v11.14 for both lmgrd and xilinxd?
 
Can you confirm on this please?
Kind Regards,
Anatoli Curran,
Xilinx Technical Support
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

你好@ CABALLES，
这个主题仍然是开放的，等着你。
如果您的问题已得到解答和/或您的问题已得到解决，请将已解决的问题标记为已接受的解决方案（有关详细信息，请访问此处：https：//forums.xilinx.com/t5/help/faqpage/faq-category
-id /解决方案＃）。
这样，主题即可完成。
如果没有解决/回答，请回复主题。
提前谢谢，祝你有个美好的一天。
亲切的问候，Anatoli Curran，Xilinx技术支持-----------------------------------------
--------------------------------不要忘记回复，工作，并接受解决方案.----
--------------------------------------------------
-------------------



以下为原文

Hello @caballes,
 
This topic is still open and is waiting for you.
 
If your question is answered and/or your issue is solved, please mark a response that resolved your issue, as Accepted Solution (more info on this can be found here: https://forums.xilinx.com/t5/help/faqpage/faq-category-id/solutions#solutions). This way, the topic can be completed then. 
 
If this is not solved/answered, please reply in the thread.
 
Thanks in advance and have a great day.
Kind Regards,
Anatoli Curran,
Xilinx Technical Support
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

谢谢您的帮助。
经过仔细审查后发现，我们的许可证服务器没有运行最新的Flexlm实用程序v11.14,1。
现在一切都在运转。



以下为原文

Thanks for the help.  After careful review, it turned out that our license server wasn't running the latest Flexlm utilities v11.14,1.  Everything's working now.