赛灵思
直播中

张华

7年用户 1419经验值
私信 关注
[问答]

实施过程中的两个警告

1.警告:NgdBuild:931  -  PLL_ADV类型的实例'U_clk_wiz_v1_6_CMP / pll_base_inst / PLL_ADV'上的SIM_DEVICE值已从'VIRTEX5'更改为'SPARTAN6',以更正此原语的后ngdbuild和时序仿真
为了使功能模拟正确,应在源网表或约束文件中以相同的方式更改SIM_DEVICE的值。
我正在使用核心的DCM,我无法摆脱这个警告。
2.警告:NgdBuild:443  -  SFF原语'U_WB_Filter1_CMP / U_Filt1_CMP / blk00000003 / blk0000002b'具有未连接的输出引脚。
U_Filt1_CMP是由coregen生成的fir过滤器,我在目录中包含了.ngc文件。
请帮忙
b

以上来自于谷歌翻译


以下为原文

1.  WARNING:NgdBuild:931 - The value of SIM_DEVICE on instance
   'U_clk_wiz_v1_6_CMP/pll_base_inst/PLL_ADV' of type PLL_ADV has been changed
   from 'VIRTEX5' to 'SPARTAN6' to correct post-ngdbuild and timing simulation
   for this primitive.  In order for functional simulation to be correct, the
   value of SIM_DEVICE should be changed in this same manner in the source
   netlist or constraint file.

I am using a DCM from core gen and I can't get rid of this warning.

2. WARNING:NgdBuild:443 - SFF primitive
   'U_WB_Filter1_CMP/U_Filt1_CMP/blk00000003/blk0000002b' has unconnected output
   pin.


U_Filt1_CMP is a fir filter generated by coregen and I have included .ngc file in the directory.  

please help

b

回帖(4)

黄淳

2018-10-8 11:26:55
看起来你为错误的设备系列生成了核心。
----------------------------是的,我这样做是为了谋生。

以上来自于谷歌翻译


以下为原文

Looks like you generated the core for the wrong device family.
----------------------------Yes, I do this for a living.
举报

王树林

2018-10-8 11:39:59
对于警告:NgdBuild:931:
=======================
此警告可以忽略,因为模拟中的PLL_BASE功能对于Virtex 5和Spartan 6是相同的.SIM_DEVICE仅影响DRP行为。
对于警告:NgdBuild:443:
=======================
解决方案1:如果您的设计使用IP核并且所讨论的SFF与此类核心相关联,则这可能是正常的。
在某些情况下,IP内核会使某些引脚浮动,期望它们在MAP期间会被修整。
有关更多详细信息,请参阅答案记录21718。解决方案2:如果所讨论的SFF原语是您设计的一部分的一部分,那么上游综合工具可能会以下游逻辑的方式优化设计
从这个SFF已经削减了你的设计。
请查阅您的综合报告,以确定是否发生了这种情况。

以上来自于谷歌翻译


以下为原文

For WARNING:NgdBuild:931:
=======================
This warning can be ignored, as the PLL_BASE functionality in simulation is the same for Virtex 5 and Spartan 6. The SIM_DEVICE only effects the DRP behavior.
 
For WARNING:NgdBuild:443:
=======================
 
Solution 1:
If your design uses IP cores and the SFF in question is associated with such a core, this may be normal.  In some scenarios, IP cores leave certain pins floating with the expectation that they will be trimmed during MAP.  Please consult Answer Record 21718 for more details.

Solution 2:
If the SFF primitive in question is part of a portion of your design which is critical, it is possible that the upstream synthesis tool is optimizing the design in such a way that the downstream logic from this SFF has been trimmed out of your design.  Please consult your synthesis report to determine if this is what is happening.
举报

折剑青

2018-10-8 11:52:33
谢谢大家。

以上来自于谷歌翻译


以下为原文

Thanks everybody.
举报

折剑青

2018-10-8 11:59:54
我最初做了,我认为这是问题,然而,当我重建核心指定正确的设备我得到相同的警告。
b

以上来自于谷歌翻译


以下为原文

I did at first and I thought that was the problem, however, when I rebuilt cores specifying correct device I got same warnings.
 
b
举报

更多回帖

发帖
×
20
完善资料,
赚取积分