完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
你好,
我正在运行Linux(Ubuntu 64位),并且在Xilinx上遇到了一些问题。 Ise运行良好,但现代内核不支持xilinx电缆驱动程序(我使用3.0,但我听说它已经不支持以后的2.6内核)。 幸运的是,可以在这里找到一个好的工作和稳定的开源驱动程序: http://rmdir.de/~michael/xilinx/ 另一个问题是我仍然无法运行FPGA_editor。 我发现2008年的论坛消息说明我必须配置我的DISPLAY变量,但仍然没有成功: $ fpga_editor 没有协议指定没有协议指定没有协议指定没有协议指定Wind / U X-toolkit错误:wuDisplay:无法打开显示 $ export DISPLAY =:0 $ fpga_editor 无法注册服务:RPC:身份验证错误; 为什么=客户端凭证太难以注册(registryProg,registryVers,tcp)(以root身份) #fpga_editor 警告!!:XKEYSYMDB环境变量设置错误位置分段错误 #export XKEYSYMDB = / usr / share / X11 / XKeysymDB #fpga_editor 分段故障 那是我尝试过的,我放弃了。 关于如何让fpga_editor工作的任何想法? (是的,我也试过DISPLAY = 127.0.0.1:0) 以上来自于谷歌翻译 以下为原文 Hello, I am running Linux (Ubuntu 64 bit) and am having some problems with Xilinx. Ise is running nicely, however the xilinx cable driver is not supported for modern kernels (I am using 3.0, but I heard that it is already unsupported for later 2.6 kernels). Luckily a good working and stable open source driver can be found here: http://rmdir.de/~michael/xilinx/ Another problem is that I am still unable to run fpga_editor. I have found forum messages from 2008 stating that I have to configure my DISPLAY variable, but still no success.: $fpga_editor No protocol specified No protocol specified No protocol specified No protocol specified Wind/U X-toolkit Error: wuDisplay: Can't open display $export DISPLAY=:0 $fpga_editor Cannot register service: RPC: Authentication error; why = Client credential too weak unable to register (registryProg, registryVers, tcp) (as root) #fpga_editor Warning!!: XKEYSYMDB environment variable is set to a wrong location Segmentation fault #export XKEYSYMDB=/usr/share/X11/XKeysymDB #fpga_editor Segmentation fault That's af far as I have tried, I am giving up. Any ideas on how to get fpga_editor to work? (yes, I have also tried DISPLAY=127.0.0.1:0) |
|
相关推荐
19个回答
|
|
fransschreuder写道:
你好, 我正在运行Linux(Ubuntu 64位),并且在Xilinx上遇到了一些问题。 那是我尝试过的,我放弃了。 关于如何让fpga_editor工作的任何想法? 尝试使用支持的操作系统。 ----------------------------是的,我这样做是为了谋生。 以上来自于谷歌翻译 以下为原文 fransschreuder wrote:Try using a supported operating system. ----------------------------Yes, I do this for a living. |
|
|
|
我已经预料到这个不答案了,非常感谢帮助我
以上来自于谷歌翻译 以下为原文 I had already expected this non-answer, thanks a lot for helping me out |
|
|
|
fransschreuder写道:
我已经预料到这个不答案了,非常感谢帮助我 好吧,我们的目标是取悦:) ----------------------------是的,我这样做是为了谋生。 以上来自于谷歌翻译 以下为原文 fransschreuder wrote:Well, we aim to please :) ----------------------------Yes, I do this for a living. |
|
|
|
好吧,我真的想知道哪些Linux用户真正使用那些支持的操作系统,Red Hat企业以及Suse企业都已经过时了。
对于xilinx来说,建立一种民意调查以查看他们的客户实际使用的Linux发行版并在此基础上建立他们的支持将是一件好事。 好吧,无论如何,我们已经用消息污染了这个论坛,是否有人真的对我的问题有答案? 以上来自于谷歌翻译 以下为原文 Well, I am really wondering which share of the linux users is actually using those supported OSes, Red Hat enterprise as well as Suse enterprise are both rather outdated. It would be good for xilinx to build a kind of poll to see which linux distributions their customers are actually using and build their support on that. Well, anyway we are already polluting this forum with messages, does anyone actually have an answer to my question? |
|
|
|
同样的问题(Xubuntu 12.04 64b,ISE 14.1 FPGA编辑器)。
我跑了`gdb fpga_editor`来看看我是否比“分段故障”更有用了; 错误似乎是在对wuGetTextExtent()的函数调用中,也许这给了某人一个发生了什么的线索: 从/opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/fpga_editor...(找不到调试符号)读取符号...完成。 (gdb)r 启动程序:/opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/fpga_editor [使用libthread_db启用的线程调试] 使用主机libthread_db库“/lib/x86_64-linux-gnu/libthread_db.so.1”。 进程5411正在执行新程序:/opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/fpga_editor [使用libthread_db启用的线程调试] 使用主机libthread_db库“/lib/x86_64-linux-gnu/libthread_db.so.1”。 BFD:/opt/Xilinx/14.1/ISE_DS/ISE//lib/lin64/libisl_iostreams.so:版本计数(4792)与符号计数不匹配(4790) 进程5411正在执行新程序:/opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/_fpga_editor BFD:/opt/Xilinx/14.1/ISE_DS/ISE//lib/lin64/libisl_iostreams.so:版本计数(4792)与符号计数不匹配(4790) [使用libthread_db启用的线程调试] 使用主机libthread_db库“/lib/x86_64-linux-gnu/libthread_db.so.1”。 Wind / U错误(193):X-Resource:DefaultGUIFontSpec( - * - helvetica-medium-r-normal - * - 14- *)未完全指定此区域设置的字体集 警告!!:XKEYSYMDB环境变量设置为错误的位置 [新主题0x7fffdcdd8700(LWP 5417)] 编程从/opt/Xilinx/14.1/ISE_DS/ISE//lib/lin64/libgdi50.so接收信号SIGSEGV,分段fault.0x00007fffe26fb722在wuGetTextExtent()中 (GDB) 我记得在Ubuntu 10.04 32b上工作的FPGA编辑器(至少12.1); 也许这是一个仅影响64b计算机的问题。 我同意fransschreuder的说法,支持Ubuntu和其他主要Linux发行版会很好。 以上来自于谷歌翻译 以下为原文 Same problem here (Xubuntu 12.04 64b, ISE 14.1 FPGA Editor). I ran `gdb fpga_editor` to see if I got anything more useful than "Segmentation fault"; the error seems to be on a function call to wuGetTextExtent(), maybe that gives someone a clue of what's happening: Reading symbols from /opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/fpga_editor...(no debugging symbols found)...done.(gdb) rStarting program: /opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/fpga_editor [Thread debugging using libthread_db enabled]Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".process 5411 is executing new program: /opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/fpga_editor[Thread debugging using libthread_db enabled]Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".BFD: /opt/Xilinx/14.1/ISE_DS/ISE//lib/lin64/libisl_iostreams.so: version count (4792) does not match symbol count (4790)process 5411 is executing new program: /opt/Xilinx/14.1/ISE_DS/ISE/bin/lin64/_fpga_editorBFD: /opt/Xilinx/14.1/ISE_DS/ISE//lib/lin64/libisl_iostreams.so: version count (4792) does not match symbol count (4790)[Thread debugging using libthread_db enabled]Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".Wind/U Error (193): X-Resource: DefaultGUIFontSpec (-*-helvetica-medium-r-normal-*-14-*) does not fully specify a font set for this localeWarning!!: XKEYSYMDB environment variable is set to a wrong location [New Thread 0x7fffdcdd8700 (LWP 5417)]Program received signal SIGSEGV, Segmentation fault. 0x00007fffe26fb722 in wuGetTextExtent () from /opt/Xilinx/14.1/ISE_DS/ISE//lib/lin64/libgdi50.so(gdb) I remember FPGA Editor (at least 12.1) working on Ubuntu 10.04 32b; maybe it's a problem that only affects 64b computers. I agree with fransschreuder in that it would be nice that Ubuntu and other major Linux distributions were supported. |
|
|
|
嗨,
确实,如果它也会在Ubuntu上运行会很好。 但我认为在这种情况下,Canonical或者你应该责怪而不是Xilinx。 我们在Debian下运行10.1到14.1的所有Xilinx ISE版本。 最近我们没有问题地改为最新的64位Squeeze。 我刚检查了ISE 13.4和ISE 14.1,两者都在我们的服务器上使用lin64库。 因此,由于Ubuntu只是一些Debian变体,因此它是系统上安装的库及其版本的问题。 看看你能做些什么。 问候 Eilert 以上来自于谷歌翻译 以下为原文 Hi, indeed it would be nice if it would run on Ubuntu too. But I think in this case either Canonical or you are to blame rather than Xilinx. We have all versions of Xilinx ISE from 10.1 to 14.1 running under Debian. And lately we changed to the latest 64 bit Squeeze without problems. I just checked for ISE 13.4 and ISE 14.1, both are using the lin64 libs on our server. So, since Ubuntu is just some Debian variant, it's a problem of the libraries and their versions installed on your system. See what you can do about that. Regards Eilert |
|
|
|
由于Ubuntu上的库与Debian相同(它们是从Debian Wheezy导入到Ubuntu Precise),这应该不是问题。
无论如何,我的问题不在于ISE(如在Project Navigator中),而是在FPGA编辑器中。 我怀疑它与主题有关。 fpga编辑器能为你工作吗? 我记得它曾经工作2年前(Xilinx 12.1,Ubuntu 10.04,32位)。 来自gdb的信息似乎没有用(除了Xilinx开发人员之外)。 以上来自于谷歌翻译 以下为原文 Since the libraries are the same on Ubuntu than Debian (they are imported from Debian Wheezy to Ubuntu Precise), this shouldn't be a problem. Anyway, my problem is not with ISE (as in the Project Navigator), it's with FPGA Editor. I suspect it has to do with motif. Does fpga editor work for you? I remember it used to work 2 years ago (Xilinx 12.1, Ubuntu 10.04, 32 bits). The info from gdb doesn't seem very useful (except maybe for Xilinx developers). |
|
|
|
我有同样的问题。
希望有人能提出一些想法 以上来自于谷歌翻译 以下为原文 I am having the same issue. Hopefully someone can give some ideas |
|
|
|
嗨,
是的,fpga-editor在版本13.4和14.1中使用64位debian 6。 但是,我无法告诉我们,我们的系统管理员已经对库命名进行了调整,甚至添加了缺少的库。 我们过去曾遇到过fpga-editor的一些问题,但现在已经解决了。 亲切的问候 Eilert 以上来自于谷歌翻译 以下为原文 Hi, yes, fpga-editor works in version 13.4 and 14.1 with 64-bit debian 6. However, i can not tell wether our system admin has made tweaks to the library naming or even added missing libraries. We have had some issues with fpga-editor in the past but they are resolved now. Kind regards Eilert |
|
|
|
好的,这里有一些_not_工作的解决方案:
*导出DISPLAY =“$ {DISPLAY%。*}”替换:0.0:0 *安装libmotif4 *安装libmotif3(我在Ubuntu 10.04存储库中找到了一个古老的.deb包) *安装ia32-libs(顺便说一句,这是mb-gcc编译器所需要的;出于某种奇怪的原因,64位版本的二进制文件只是32位版本的二进制文件) *用sudo -H运行它(注意:不要这样做;用sudo运行每个命令通常是一个坏主意,因为没有它就无法运行;我这样做是因为我开始变得不耐烦了)。 使用此选项可以更快地进行段错误,因为似乎存在sudo解决方法的portmap的权限问题。 *安装libmotif3 32位并运行32位版本的FPGA Editor(相同的段错误)。 P.S。:在收到此消息后出现了段错误: 警告!!:XKEYSYMDB环境变量设置为错误的位置 (但是,根据fransschreuder的经验,修复似乎并没有解决问题) PS2:函数wuGetTextExtent()似乎是一个名为libgdi50.so的库的一部分,它似乎是Wind / U的一部分,它似乎是一种将程序从Windows移植到Linux的简单方法( 有点像Cygwin,但反过来说)。 显然,FPGA编辑器是唯一仍然依赖于该库的Xilinx应用程序...将它移植到其他东西(例如,Wine或其他东西)会很不错。 以上来自于谷歌翻译 以下为原文 Ok, here are some solutions that have _not_ worked: * export DISPLAY="${DISPLAY%.*}" to replace :0.0 with :0 * Install libmotif4 * Install libmotif3 (I found an ancient .deb package on Ubuntu 10.04 repositories) * Install ia32-libs (which are needed by the mb-gcc compiler, by the way; for some weird reason the binaries for the 64 bit version are just the ones for the 32 bit one) * Run it with sudo -H (note: don't do this; it's generally a bad idea to just run every command with sudo just because it doesn't work without it; I did this becaue I was starting to get impatient). With this option it segfaults much faster since there seems to be a permission problem with portmap that sudo workarounds. * Install libmotif3 for 32 bits and run the 32 bits version of FPGA Editor (same segfault). P.S.: The segfault appears just after I get this message: Warning!!: XKEYSYMDB environment variable is set to a wrong location (but, according to fransschreuder's experience, fixing that doesn't seem to workaround the problem) P.S.2: The function wuGetTextExtent() seems to be part of a library called libgdi50.so, which seems to be part of Wind/U, which seems to be some sort of application for porting programs from Windows to Linux in an easy way (sort of like Cygwin but the other way around). Apparently, FPGA Editor is the only Xilinx application that still relies on that library... it would be nice that it were ported to something else (say, Wine or something). |
|
|
|
很好,同样的问题在这里,我使用的是CentOS 6.3,它应该与RHEL 6.3二进制兼容。
根据这个线程,FPGA编辑器应该从版本11.1开始被替换:http://www.fpgarelated.com/usenet/fpga/show/69996-1.php 关于更换FPGA编辑器的评论是在2007年11月完成的,我在2012年没有看到任何替代品。 太糟糕了我没有RHEL 6.3但我没有看到为什么它应该在那里运行,因为CentOS和RHEL是二进制兼容的。 我正在浪费时间尝试使用这个软件,这真的令人沮丧并且花了很多钱...... 以上来自于谷歌翻译 以下为原文 Great, same problem here and I'm using CentOS 6.3 which should be binary compatible to RHEL 6.3. According to this thread FPGA Editor should have been replaced starting with version 11.1: http://www.fpgarelated.com/usenet/fpga/show/69996-1.php The comment about replacing FPGA Editor was made in november 2007 and I don't see any replacement in 2012. Too bad I don't have RHEL 6.3 but I don't see any reasons why it should be running there as CentOS and RHEL are binary compatible. I'm wasting hours when trying to use this software which is really frustrating and costs a lot of money... |
|
|
|
stmartin81写道:
很好,同样的问题在这里,我使用的是CentOS 6.3,它应该与RHEL 6.3二进制兼容。 根据这个线程,FPGA编辑器应该从版本11.1开始被替换:http://www.fpgarelated.com/usenet/fpga/show/69996-1.php 关于更换FPGA编辑器的评论是在2007年11月完成的,我在2012年没有看到任何替代品。 太糟糕了我没有RHEL 6.3但我没有看到为什么它应该在那里运行,因为CentOS和RHEL是二进制兼容的。 我正在浪费时间尝试使用这个软件,这真的令人沮丧并且花了很多钱...... 如果您为RHEL的成本而奋斗,那么“浪费的时间和金钱”可能会得到缓解。 当然,发行版“应该”是二进制兼容的,但你已经证明它们是完全不同的。 ----------------------------是的,我这样做是为了谋生。 以上来自于谷歌翻译 以下为原文 stmartin81 wrote:The "hours and money wasted" could've been mitigated had you just sprung for whatever RHEL costs. Sure, the distros "should' be binary compatible, but you've proven that they're sufficiently different. ----------------------------Yes, I do this for a living. |
|
|
|
分段错误似乎发生在字体查询期间/之后。
我发现了两个不同的解决方案。 或 安装xfonts-75dpi并重新启动X,或 将以下内容放入〜/ .Xresources文件中并重新启动X. * SystemFontSpec:-adobe-黑体介质-R-正常 - 14 - * - * - * - P - * - * - * * systemFont:-adobe信使介质-R-正常 - 12 - * - * - * - P - * - * - * wrt Wind / U:我怀疑xilinx会将fpga_editor移植到另一个工具箱。 Vivado的“Open Implemented Design”似乎是fpga_editor的替代品。 很遗憾,Vivado只支持7系列设备,并且具有完全不同的约束格式。 以上来自于谷歌翻译 以下为原文 The segmentation fault seems to happen during/after font query. I found two different solutions for this problem. Either
wrt Wind/U: I doubt that xilinx will port fpga_editor to another toolkit. The "Open Implemented Design" of Vivado seems to be the fpga_editor replacement. It is just a pity that Vivado does only support series 7 devices and has a completely different constraint format. |
|
|
|
我今天做了一件非常愚蠢的事:
*安装葡萄酒1.4 *使用winetricks安装Visual C ++ 2008运行时(也许Xilinx提供的安装程序也可以工作) *将Windows操作系统分区安装为只读(我安装了Xilinx 13.4的Windows分区,但我很少使用它,因为我的所有脚本主要用于Linux) *配置Wine以将Windows分区用作D: * wine'D: Xilinx 13.4 ISE_DS ISE bin nt fpga_editor.exe' 令人惊讶的是,一切似乎都像魅力一样。 该程序加载很快,我能够成功创建和保存硬宏没有任何明显的问题。 我认为使用Wine来运行安装在Windows分区上的程序并不是一个好主意(这就是我将它作为只读安装的原因),但在这种情况下它可以工作,所以使用Wine可能是个好主意 而不是风/ U. Wind / U项目似乎已经消失,而Wine正在积极开发中。 然而,正如voinauiw所提到的,Xilinx不太可能将FPGA编辑器移至Wine,因为在Vivado外出时,FPGA编辑器似乎已被弃用或几乎被抛弃。 以上来自于谷歌翻译 以下为原文 I did a very silly thing today: * Installed Wine 1.4 * Installed Visual C++ 2008 runtime using winetricks (maybe the installer provided by Xilinx would have worked too) * Mounted the Windows OS partition as read only (I have a Windows partition with Xilinx 13.4 installed, but I rarely use it since all my scripts are mainly intended for Linux) * Configured Wine to use the Windows partition as D: * wine 'D:Xilinx13.4ISE_DSISEbinntfpga_editor.exe' Surprisingly, everything seemed to work like a charm. The program loaded quickly and I was able to successfully create and save a hard macro without any apparent issue. I don't think it's a good idea to use Wine for running programs installed on a Windows partition (which is why I mounted it as read only), but in this case it worked, so maybe it would be a good idea to use Wine instead of Wind/U. The Wind/U project seems to have disappeared, while Wine is in active development. However, as voinauiw mentioned, it's unlikely that Xilinx moves FPGA Editor to Wine since FPGA Editor seems to be deprecated or nearly abandoned now that Vivado is out. |
|
|
|
我在Ubuntu 12.04 LTS 64bit-Intel上,我遇到了从Xilinx ISE 14.5运行FPGA编辑器的同样问题。
我唯一要做的就是使用synaptics进行intsall xfonts-75dpi和xfonts-100dpi。 然后重新启动comptuer。 但是我仍然拒绝连接,但它会运行正常。 非常感谢你。 这篇博客也有很多帮助:https://help.ubuntu.com/community/XilinxISE 以上来自于谷歌翻译 以下为原文 I am on Ubuntu 12.04 LTS 64bit-Intel and I HAD the same problem running the FPGA Editor from Xilinx ISE 14.5. The only thing I had to do was intsall xfonts-75dpi and xfonts-100dpi using synaptics. Then restart the comptuer. However I still get a connection refused but it will run ok. Thank you very much. This blog helped a lot too: https://help.ubuntu.com/community/XilinxISE |
|
|
|
我知道这是一个老线程,但我也遇到了fpga_editor的困难(Ubuntu 12.04)。
所以,我安装了libstdc ++ 5,xfonts-100dpi,xfonts-75dpi。 我准备在一台虚拟机中运行Xilinx ISE,并意识到 - 我没有在我的真实系统上安装libmotif4(openmotif),但却没有改进! 我的大问题是,我有libXm.so.2(由lesstif提供)并且历史上有一个从libXm.so.2到libXm.so.3的符号链接,用于预期它的某个应用程序。 *这与FPGA_EDITOR *无关。 如果您有该符号链接,请删除libXm.so.3,然后在较旧的Ubuntu版本上安装libmotif4(或libmotif3。)如果需要,可以安装较少的。 注销或重新启动(X服务器必须重新启动才能看到新字体)。 正如其他人所说的那样,fpga_editor仍然没有做一些rpc调用,并且在那里做任何事情,直到它超时,但似乎工作100%罚款。 以上来自于谷歌翻译 以下为原文 I know it's an old thread, but I was running into difficulty with fpga_editor as well (Ubuntu 12.04). So, I installed libstdc++5, xfonts-100dpi, xfonts-75dpi. I was getting ready to run Xilinx ISE in a virtual machine, and realized -- I did not have libmotif4 (openmotif) installed on my real system, but had lesstif instead! My big problem, I had libXm.so.2 (provided by lesstif) and historically had a symlink from libXm.so.2 to libXm.so.3 for some app that expected it. *THIS DOESN'T WORK WITH FPGA_EDITOR*. If you have that symlink, delete libXm.so.3, then install libmotif4 (or libmotif3 on older Ubuntu versions.) You can keep lesstiff installed if you want. Logout or reboot (the X server must restart to see the new fonts). As others have said, fpga_editor still fails to do some rpc call and sits there doing nothing until it times out, but then seems to work 100% fine. |
|
|
|
...再过几年,我可以确认fpga_editor仍可以在Ubuntu 16.04 x86-64上使用ISE 14.7进行工作。
总结一下我必须做的事情(在这个主题的先驱者的指导下): 1.安装字体: sudo apt-get install xfonts-75dpi xfonts-100dpi 2.注销并登录(或重启)。 这仍然是必需的。 3.我已经安装了libmotif4和libstdc ++ 5,不记得默认情况下,还是其他一些包。 我在.bashrc中: export DISPLAY =:0 5.当我启动fpga_editor时,我仍然收到以下消息: $ fpga_editor 无法注册服务:RPC:无法接收; errno =拒绝连接 无法注册(registryProg,registryVers,tcp) Wind / U错误(248):无法连接到服务器上的注册表 警告!!:XKEYSYMDB环境变量设置为错误的位置 无法注册服务:RPC:无法接收; errno =成功 但它确实在一点之后开始好起来,似乎工作正常。 它弹出以下错误对话框: 当我尝试通过点击“浏览”按钮打开一个ncd时,但是当我手动将路径粘贴到文本框中的ncd文件时,工作正常。 以上来自于谷歌翻译 以下为原文 ...and a few more years on, I can confirm that fpga_editor can still be coaxed to work, with ISE 14.7 on Ubuntu 16.04 x86-64. To summarize what I had to do (as guided by the pioneers in this thread): 1. Install fonts: sudo apt-get install xfonts-75dpi xfonts-100dpi2. LOG OUT AND LOG IN (or reboot). This is still REQUIRED. 3. I already had libmotif4 and libstdc++5 installed, don't remember if by default, or for some other package. 4. I have in my .bashrc: export DISPLAY=:0 5. I still get the following messages when I launch fpga_editor: $ fpga_editor Cannot register service: RPC: Unable to receive; errno = Connection refusedunable to register (registryProg, registryVers, tcp)Wind/U Error (248): Failed to connect to the registry on server It popped up the following error dialog: when I tried to open an ncd by hitting the Browse button, but worked just fine when I manually pasted the path to the ncd file in the textbox. |
|
|
|
由于这个帖子为我提供了很多帮助,我想分享我的结果:
我成功地在Docker容器中运行CentOS 6下的Xilinx ISE WebPack 14.7。 CentOS 6相当于RHEL 6,它是Xilinx支持的Linux发行版。 使用该方法的基本思想是不在Docker容器中安装IDE。 相反,它预计已安装在/ opt / Xilinx /下的主机上。 然后,该目录将在运行时传递到Docker容器中。 这种方法可以简化安装过程。 而且,特别是Docker容器变得更加轻盈。 Docker容器由提供的Makefile完全自动创建。 当然,先决条件是IDE至少运行到可以安装它,包括许可证管理器。 请在我的网站上找到gzipped tarball:http://homepages.hs-bremen.de/~***redereke/en/software/xilinx-docker/index.html 此版本(1.0)已在Lubuntu 1604 LTS下测试。 但它也应该在其他Ubuntu变种下运行。 可能每个基于Debian的系统都应该这样做。 剩余的已知限制:FPGA编辑器始终以大约70秒的延迟启动。 同时,stdout显示有关RPC访问问题的上述错误消息。 (顺便说一句:我通过设置:export XKEYSYMDB = / usr / share / X11 / XKeysymDB解决了XKEYSYMDB怪癖问题) 欢迎改进。 以上来自于谷歌翻译 以下为原文 Since this thread provided me with a lot of help, I would like to share my results: I succeeded in running the Xilinx ISE WebPack 14.7 under CentOS 6 in a Docker container. CentOS 6 is equivalent to RHEL 6, which is a Linux distribution supported by Xilinx. The basic idea of the approach used is to not install the IDE in the Docker container. Instead, it is expected to have been installed on the host under /opt/Xilinx/. This directory will then be handed into the Docker container at run-time. This approach eases the installation process a little. And, in particular, the Docker container becomes much more light-weight. The Docker container is created fully automatically by a Makefile supplied. A prerequisite is, of course, that the IDE runs at least so far that it can be installed, including the license manager. Please find the gzipped tarball on my Web site: http://homepages.hs-bremen.de/~***redereke/en/software/xilinx-docker/index.html This version (1.0) has been tested under Lubuntu 1604 LTS. But it should run under other Ubuntu variants, too. Probably, every Debian-based system should do. Remaining known limitation: the FPGA editor always starts with about 70 seconds delay. At the same time, stdout shows the above error message concerning a RPC access problem. (BTW: I solved the XKEYSYMDB quirk by setting: export XKEYSYMDB=/usr/share/X11/XKeysymDB ) Improvements are welcome. |
|
|
|
jan.bredereke写道:剩余的已知限制:FPGA编辑器总是以大约70秒的延迟开始。
同时,stdout显示有关RPC访问问题的上述错误消息。 (顺便说一句:我通过设置:export XKEYSYMDB = / usr / share / X11 / XKeysymDB解决了XKEYSYMDB怪癖)我依旧记得遇到了长启动延迟的解决方案。 如果我没记错的话,它与RPC错误有关,并且是由于某些进程试图注册打印机,由于“凭据太弱”或类似的情况,它无法执行。 我认为这可以通过安装某些东西或用sudo运行fpga_editor来解决,但无论解决方案是什么,我都忘了它因为我很少使用fpga_editor,所以我只需要等待70秒的价格才能启动它。 以上来自于谷歌翻译 以下为原文 jan.bredereke wrote:Remaining known limitation: the FPGA editor always starts with about 70 seconds delay. At the same time, stdout shows the above error message concerning a RPC access problem. (BTW: I solved the XKEYSYMDB quirk by setting: export XKEYSYMDB=/usr/share/X11/XKeysymDB )I vaguely remember coming across a solution to the long startup delay. If I recall correctly it was related to the RPC error, and was due to some process attempting to register a printer, which it failed to do due to "credentials being too weak" or something like that. I think this could be solved by installing something or running fpga_editor with sudo, but whatever the solution was I forgot about it because I rarely use fpga_editor anyway, so I just pay the price of waiting 70 seconds for it to start. |
|
|
|
只有小组成员才能发言,加入小组>>
2424 浏览 7 评论
2825 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2294 浏览 9 评论
3374 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2465 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
1207浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
590浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
452浏览 1评论
2006浏览 0评论
731浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-24 20:14 , Processed in 1.707917 second(s), Total 112, Slave 96 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号