完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我正在开发一个部分重新配置的项目,它使用总线宏(我知道它们已被弃用;但它是项目使用的内容并且更改会使项目陷入困境)。
问题是 如果总线宏没有连接任何输出,则ISE Map(12.1)会抛出错误。 ISE无法识别信号的“保存”属性(属性s:字符串; dummy_output的属性:信号为“是”;) 我已尝试使用AR#30112中建议的解决方案但没有成功(也许我没有正确解释)。 是否有任何解决方案不涉及禁用“修剪未使用的逻辑”,也不添加大量的虚拟逻辑和输出信号? 以上来自于谷歌翻译 以下为原文 I'm working on a project on partial reconfiguration which uses bus macros (I know they're deprecated; but it's what the project uses and changing that would mess up the project too much). The problem is that
Is there any solution that does not involve disabling "trim unused logic" nor adding lots of dummy logic and output signals? |
|
相关推荐
8个回答
|
|
尝试使用UCF Save属性:
NET“net_name”S; 在原帖中查看解决方案 以上来自于谷歌翻译 以下为原文 Try it with a UCF Save property: NET "net_name" S; View solution in original post |
|
|
|
您可以尝试在MAP中使用“-u”选项。
它指示MAO不删除未使用的逻辑 以上来自于谷歌翻译 以下为原文 You could try using the "-u" option in MAP. It instructs MAO to not remove unused logic |
|
|
|
我不熟悉PR流程但不是Bus Macros硬宏(.nmc文件)?
在那种情况下,硬宏中的任何东西都不会被修剪掉。 你是否有连接宏的网络修剪问题? 你看到什么错误? 如果您让我们更深入地了解故障模式,那将会有很大帮助。 以上来自于谷歌翻译 以下为原文 I'm not that familiar with the PR flow but aren't Bus Macros hard macros (.nmc files)? In that case nothing in a hard macro ever gets trimmed. Are you having a trimming problem with a net connected to the macro? What error are you seeing? It would help a lot if you gave us more insight into the failure mode. |
|
|
|
shantesh:使用-u的问题是我不想在_all_我的设计中禁用逻辑修整,只在那些特定部分中。
但无论如何,谢谢; 这是我已经考虑过(和丢弃)的可能性。 bwade:这不是硬宏上的网络被修剪的; 它是连接硬宏输出的网络(并且没有连接到任何其他东西)正在被修剪。 自从我改变设计以来,我不确定具体的错误信息; 我认为就是这个(来自AR#30112): “ERROR:Pack:1195 - Symbol”“没有输出引脚连接。” (作为公交车宏)。 也就是说,Xilinx修剪了未连接的输出网络,然后抱怨没有任何输出的元素。 我现在正在使用的解决方法(似乎有效)正在为这些元素制作一些“虚拟逻辑”(将其中一个输出连接到另一个输入或输出引脚)。 尽管它以不必要的逻辑填充了设计,但它仍然有用。 以上来自于谷歌翻译 以下为原文 shantesh: The problem with using -u is that I don't want to disable logic trimming in _all_ my design, only in those specific parts. But thanks anyway; it's a possibility I have already considered (and discarded). bwade: It's not the nets on the hard macro itself being trimmed; it's the nets to which the hard macro outputs are connected (and which aren't connected to anything else) which is getting trimmed. I'm not sure about the specific error message since I changed the design; I think it's this one (from AR #30112): "ERROR:Pack:1195 - Symbol " This is, Xilinx trims the unconnected output nets and then complains about the element not having any output. The workaround I'm using right now (and which seems to work) is making some "dummy logic" for those elements (connecting one of their outputs to another input or to an output pin). It serves its purpose, although it fills the design with unnecessary logic. |
|
|
|
这可能是一个非常愚蠢的问题,但是如果你没有将任何东西连接到它们的输出,为什么还要这些总线宏呢?
------------------------------------------“如果它不起作用 模拟,它不会在板上工作。“ 以上来自于谷歌翻译 以下为原文 This might be a really silly question, but why do you want these Bus Macros if you aren't connecting anything to their outputs? ------------------------------------------ "If it don't work in simulation, it won't work on the board." |
|
|
|
尝试使用UCF Save属性:
NET“net_name”S; 以上来自于谷歌翻译 以下为原文 Try it with a UCF Save property: NET "net_name" S; |
|
|
|
库斯托,
请参阅“部分重新配置用户指南”的附录B. 这提供了有关如何从具有总线宏的旧PR流程迁移到新解决方案的建议。 使用简单的软宏,您可以有效地替换硬宏 - 它对HDL和设计结构的影响最小,但充分利用了新PR解决方案的自动化特性。 以下是PR用户指南12.3版本的链接:http://www.xilinx.com/support/documentation/sw_manuals/xilinx12_3/ug702.pdf thansk, 大卫。 以上来自于谷歌翻译 以下为原文 Cousteau, Take a look at Appendix B of the Partial Reconfiguration User Guide. This provides suggestions on how to migrate from the old PR flow with Bus Macros to the new solution. Using simple soft macros, you can replace the hard macros efficiently -- it has minimal impact on the HDL and structure of the design, but takes full advantage of the automated nature of the new PR solution. Here's a link to the 12.3 version of the PR User Guide: http://www.xilinx.com/support/documentation/sw_manuals/xilinx12_3/ug702.pdf thansk, david. |
|
|
|
按照bwade的建议在UCF上设置“S”属性已经解决了这个问题。
显然,我需要UCF _和_ VHDL上的“S”属性: - top.vhd --signal notrim:std_logic_vector(0到3);属性s:字符串; notrim的属性:signal是“yes”; - constraints.ucf --NET notrim S; NET notrim S; NET notrim S; NET notrim S; rcingham:嗯,这根本不是一个愚蠢的问题。 问题是_some_总线宏将有输出而其他人不会,我不知道是否只是删除总线宏将导致以后在重新配置后有半个总线宏,以及这是否是一个问题。 所以,为了确保,我留下了一些未连接的总线宏。 也许他们可以被删除。 以上来自于谷歌翻译 以下为原文 Putting an "S" attribute on the UCF as suggested by bwade has solved the problem. Apparently, I need that "S" attribute on both the UCF _and_ the VHDL: -- top.vhd -- signal notrim : std_logic_vector(0 to 3); attribute s : string; attribute s of notrim : signal is "yes"; -- constraints.ucf -- NET notrim<0> S; NET notrim<1> S; NET notrim<2> S; NET notrim<3> S; rcingham: Well, that's not a silly question at all. The problem is that _some_ bus macros will have outputs and others won't, and I don't know if just removing the bus macro would cause later having half a bus macro after reconfiguring, and whether this could be a problem. So, just to be sure, I leave some unconnected bus macros. Maybe they could just be removed. |
|
|
|
只有小组成员才能发言,加入小组>>
2322 浏览 7 评论
2734 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2217 浏览 9 评论
3295 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2369 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
655浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
463浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
222浏览 1评论
669浏览 0评论
1863浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-10-1 10:19 , Processed in 1.152477 second(s), Total 61, Slave 54 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号