完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
你好,
我对ISE 14.1的Maper(Win-7 32位)有一个非常神秘的警告 MapLib:23 - 检测到信号FPGA_CFGMZ的短路信号 MapLib:23 - 检测到信号FPGA_CFGMZ的短路信号 确切的警告重复6次。 涉及的信号定义如下: 在TopLevelentity中: - //与配置夹层通信 FPGA_CFGMZ_LINK:inout std_logic_vector(16 downto 1); - //一般信号 然后,它们被用在内部模块中,其中信号被定义为 cfgmz_link:inout std_logic_vector(16 downto 1); - //来自Mezzanine的一般信号 分配完成如下: cfgmz_link => FPGA_CFGMZ_LINK, 在该内部模块中,信号3至16是输入,信号1和2是输出,用作: - // ---------------------------------------------- ---------------- - //控制Modulator-L4特有的信号 cfgmz_link(1) cfgmz_link(2) 然后,在同一个模块中: cfgmz_link_fp_testpoint_out(1) cfgmz_link_fp_testpoint_out(2) 而定义是: 信号cfgmz_link_fp_testpoint_out:std_logic_vector(16 downto 1); - //从配置夹层到前面板的信号 cfgmz_link_fp_testpoint 并将此信号定义为: cfgmz_link_fp_testpoint:out std_logic_vector(16 downto 1); - //从配置夹层到前面板的信号 应用于这些信号的值在包中定义为: 常数DEFAULT_CFGMZ_LINK_1:std_logic:='0'; - // CFGMZ_LINK信号1:默认值 常量DEFAULT_CFGMZ_LINK_2:std_logic:='0'; - // CFGMZ_LINK信号2:默认值 我检查过那些信号只在那里使用。 所以,我的问题是: 1-此警告的含义是什么? 没有与这些信号相关的其他警告/错误/信息,并且没有针对该警告的应答记录(并且查看生成的RTL无用) 2-在同一向量中混合输入/输出是否存在问题? (我必须这样定义,因为我在不同的系统中使用相同的模块,其中信号可以输入/输出,所以我不想为每种情况修改Toplevel) 3-这是ISE另一个“有趣”的警告吗? 4-信号是否正确定义为输出并连接到0或ISE是否会使输入和输出缓冲器短路? 谢谢 以上来自于谷歌翻译 以下为原文 Hello, I have a very cryptic warning with the Maper of ISE 14.1 (Win-7 32 bits) MapLib:23 - Short on signal FPGA_CFGMZ_LINK<1> detected MapLib:23 - Short on signal FPGA_CFGMZ_LINK<2> detected And the exact Warnings are repeated 6 times. The signal involved are defined as following : In the TopLevel entity : --// Communication with Configuration Mezzanine FPGA_CFGMZ_LINK : inout std_logic_vector (16 downto 1); --// General Signals Then, they are used in an internal module, where the signals are defined as cfgmz_link: inout std_logic_vector (16 downto 1); --// General Signals from Mezzanine The assignation is done as: cfgmz_link => FPGA_CFGMZ_LINK, In this internal module, signals 3 to 16 are inputs and signals 1 and 2 are outputs, and used as: --//-------------------------------------------------------------- --// Control of signals specific for Modulator-L4 cfgmz_link(1) <= DEFAULT_CFGMZ_LINK_1; cfgmz_link(2) <= DEFAULT_CFGMZ_LINK_2; Then, in the same module: cfgmz_link_fp_testpoint_out(1) <= cfgmz_link(1); cfgmz_link_fp_testpoint_out(2) <= cfgmz_link(2); And the definition is: signal cfgmz_link_fp_testpoint_out: std_logic_vector (16 downto 1); --// Signals from Configuration Mezzanine to Front Panel cfgmz_link_fp_testpoint <= cfgmz_link_fp_testpoint_out; And with this signal defined as: cfgmz_link_fp_testpoint : out std_logic_vector (16 downto 1); --// Signals from Configuration Mezzanine to Front Panel The values applied to those signals are defined in a package as: constant DEFAULT_CFGMZ_LINK_1: std_logic := '0'; --// CFGMZ_LINK signal 1: Default Value constant DEFAULT_CFGMZ_LINK_2: std_logic := '0'; --// CFGMZ_LINK signal 2: Default Value I have checked and those signals are only used there. So, my questions are: 1- What does this Warning means ? There are no other Warnings/Errors/Infos related to those signals and there is no Answer Record for that warning (and looking at the generated RTL is useless) 2- Is there a problem with the mixing of inputs/outputs in the same vector? (I have to define this like that because I use the same modules in different systems where the signals can be input/outputs so I do not want to modify the Toplevel for every case) 3- Is this another "funny" Warning from ISE? 4- Are the signals correctly defined as outputs and connected to 0 or ISE is shorting the input and output buffers? Thanks |
|
相关推荐
7个回答
|
|
谢谢,
我已经找到了解决办法,为每个系统独立定义这些线路上的引体向上.... 但这种检查有点不连贯,因为上拉不是短路...... 感谢2013年的最佳状态 Cordialement 何塞路易斯戈麦斯科斯塔 在原帖中查看解决方案 以上来自于谷歌翻译 以下为原文 Thanks, I have found a work-around, defining the Pull-ups on those lines independently for each system .... But this check seems a bit incoherent, as a Pull-Up is not a short circuit .... Thanks an have the best for 2013 Cordialement Jose Luis Gomez Costa View solution in original post |
|
|
|
最近在一个案例中看到了这条消息。
关于根本原因的细节不多,但是通过使用-ignore_keep_hierarchy选项在地图期间禁用保持层次结构约束来解决问题。 以上来自于谷歌翻译 以下为原文 This message was seen in a case recently. There are not a lot of details on the root cause but the problem was resolved by disabling keep hierarchy constraints during map by using the -ignore_keep_hierarchy option. |
|
|
|
对不起,但它不起作用
命令行:map -filter“G:/departments/te/groups/epc/projects/regfgc3/design/VS_Analog_INTK/FPGA/Schema_v3_xst/L4Modulator/xproj/iseconfig/filter.filter”-intstyle ise -p xc3s700an-fgg484-5 -timing -logic_opt on -ol high -xe n -t 1 -register_duplication on -cm speed -detail -ir off -ignore_keep_hierarchy -pr off -power off -o TOPLEVEL_map.ncd TOPLEVEL.ngd TOPLEVEL.pcf 同样在XST中: 保持等级:不 我已经使用手动放置和布线(FPGA编辑器)进行了检查,信号似乎已经过去了。 我将打开一个WebCase。 以上来自于谷歌翻译 以下为原文 Sorry, but It doesn't work Command Line: map -filter "G:/departments/te/groups/epc/projects/regfgc3/design/VS_Analog_INTK/FPGA/Schema_v3_xst/L4Modulator/xproj/iseconfig/filter.filter" -intstyle ise -p xc3s700an-fgg484-5 -timing -logic_opt on -ol high -xe n -t 1 -register_duplication on -cm speed -detail -ir off -ignore_keep_hierarchy -pr off -power off -o TOPLEVEL_map.ncd TOPLEVEL.ngd TOPLEVEL.pcf Also in XST: Keep hierarchy: NO I have checked with Manually Place and Route (FPGA Editor) and the signals seemed to be weel routed. I will open a WebCase. |
|
|
|
喜
可能是对FPGA_CFGMZ_LINK [1]和FPGA_CFGMZ_LINK [2]的一些限制导致了警告。 如果省略这些约束,则不会发生警告。 问候, saurav 以上来自于谷歌翻译 以下为原文 hi, may be some constraint on FPGA_CFGMZ_LINK[1] and FPGA_CFGMZ_LINK[2] were causing the warnings. If these constraints are omitted, the warnings do not occur. regards, saurav |
|
|
|
谢谢,
我已经找到了解决办法,为每个系统独立定义这些线路上的引体向上.... 但这种检查有点不连贯,因为上拉不是短路...... 感谢2013年的最佳状态 Cordialement 何塞路易斯戈麦斯科斯塔 以上来自于谷歌翻译 以下为原文 Thanks, I have found a work-around, defining the Pull-ups on those lines independently for each system .... But this check seems a bit incoherent, as a Pull-Up is not a short circuit .... Thanks an have the best for 2013 Cordialement Jose Luis Gomez Costa |
|
|
|
在仅输出引脚上定义上拉似乎会导致此消息
以上来自于谷歌翻译 以下为原文 Having a pullup defined on an output only pin seems to cause this message |
|
|
|
嗨,
是的,这似乎是个问题。 情况是我在TopLevel中有一个通用定义,然后根据应用程序,我使用输入(因此我需要上拉)或输出。 我更容易在一般模块中定义Pull-Up而不是每次都要重新定义(......这就是我现在正在做的事情)。 Cordialement 以上来自于谷歌翻译 以下为原文 Hi, Yes, this seemed to be the problem. The case is that I have a general definition in the TopLevel, and then depending on the applications, I use as inputs (therefore I need the Pull-up) or outputs. It was simpler for me to define the Pull-Up in a general module in stead of having to re-define every time (... that is what I am doing now). Cordialement |
|
|
|
只有小组成员才能发言,加入小组>>
2415 浏览 7 评论
2821 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2292 浏览 9 评论
3372 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2458 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
1079浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
579浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
438浏览 1评论
2000浏览 0评论
723浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-20 07:12 , Processed in 1.396048 second(s), Total 89, Slave 73 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号