完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
你好
现在,我正在使用virtex-7-2000T。 基本上,有4个NAND PHY,它支持DDR接口。 因此,时序要求有点紧张。 因此,在我们在XDC中设置正确的约束之后,在0326实现时关闭时序。 但是,在0328,我们改变了RTL,而不是NAND PHY设计,VIVADO报告定时故障,大约-3ns。 但是,0326和0328具有完全相同的NAND PHY设计。 以下是带DDR接口的4个子模块。 u_core_top / u_pd_top / u_ncb_top / ndphy_ch_inst [0] .u_ndphy_ch_top_inst_ho.u_ndphy_ch_top_ho u_core_top / u_pd_top / u_ncb_top / ndphy_ch_inst [1] .u_ndphy_ch_top_inst.u_ndphy_ch_top u_core_top / u_pd_top / u_ncb_top / ndphy_ch_inst [2] .u_ndphy_ch_top_inst.u_ndphy_ch_top u_core_top / u_pd_top / u_ncb_top / ndphy_ch_inst [3] .u_ndphy_ch_top_inst_ho.u_ndphy_ch_top_ho 我在想是否有任何方法可以直接将0326 NAND_PHY复制到0328设计,包括loc,FF,路径等。我之前尝试过布局,但时机更糟。 我希望当NAND PHY完全相同时,我们可以获得一致的实现。 如果有人能解决我的问题,我们将不胜感激。 谢谢 陈平 2018年3月29日 以上来自于谷歌翻译 以下为原文 Hi, there Now, I am working virtex-7-2000T. Basically, there are 4 NAND PHY, which support DDR interface. So, the timing requirement is a little bit tight. So, after we setup the correct constrains in the XDC, the timing is closed on 0326 implementation. But, on 0328, we change the RTL, not NAND PHY design, VIVADO report timing failure, around -3ns. But, 0326 and 0328 have exact same design for NAND PHY. The following is the 4 sub-module with DDR interface. u_core_top/u_pd_top/u_ncb_top/ndphy_ch_inst[0].u_ndphy_ch_top_inst_ho.u_ndphy_ch_top_ho u_core_top/u_pd_top/u_ncb_top/ndphy_ch_inst[1].u_ndphy_ch_top_inst.u_ndphy_ch_top u_core_top/u_pd_top/u_ncb_top/ndphy_ch_inst[2].u_ndphy_ch_top_inst.u_ndphy_ch_top u_core_top/u_pd_top/u_ncb_top/ndphy_ch_inst[3].u_ndphy_ch_top_inst_ho.u_ndphy_ch_top_ho I am thinking whether there is any way for me to copy the 0326 NAND_PHY to 0328 design directly, including loc, FF, route path, etc. I try floorplan before, but timing is worse. I hope that we can get the consistent implementation when NAND PHY is exactly same. It is highly appreciated it if someone can solve my problem. thanks Ping Chen 2018.3.29 |
|
相关推荐
6个回答
|
|
嗨@chenpingx。
我可以建议有两种重用流可能会有所帮助。 第一个是增量编译流程。 对于设计迭代之间的较小变化,这更有用。 通过此流程,实施工具将使用先前的参考检查点来完成新版本的放置和路由。 “实施指南”在第94页上有更多内容: http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug904-vivado-implementation.pdf 还有分层设计流程。 有几个级别的重用,但您可以在物理上分隔要保持相同布局和布线的区域。 您可能看不到相同的QOR,因为物理分离将限制放置和路由选项。 以下“分层设计指南”提供了更多信息。 http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug905-vivado-hierarchical-design.pdf 在原帖中查看解决方案 以上来自于谷歌翻译 以下为原文 Hi @chenpingx. There are two reuse flows that I can suggest that might help. The first is the incremental compile flow. This is more useful with designs smaller changes between design iterations. With this flow, a previous reference checkpoint will be used by the implementation tools to complete the placement and routing of the new version. The Implementation Guide has more on this on page 94: http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug904-vivado-implementation.pdf There is also Hierarchical Design flows. There are several levels of reuse, but you could physically separate areas that you want to keep the same placement and routing. You might not see the same QOR though, as the physical separation will limit the placement and routing options. The below Hierarchical Design Guide has more information. http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug905-vivado-hierarchical-design.pdf View solution in original post |
|
|
|
嗨@chenpingx。
我可以建议有两种重用流可能会有所帮助。 第一个是增量编译流程。 对于设计迭代之间的较小变化,这更有用。 通过此流程,实施工具将使用先前的参考检查点来完成新版本的放置和路由。 “实施指南”在第94页上有更多内容: http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug904-vivado-implementation.pdf 还有分层设计流程。 有几个级别的重用,但您可以在物理上分隔要保持相同布局和布线的区域。 您可能看不到相同的QOR,因为物理分离将限制放置和路由选项。 以下“分层设计指南”提供了更多信息。 http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug905-vivado-hierarchical-design.pdf 以上来自于谷歌翻译 以下为原文 Hi @chenpingx. There are two reuse flows that I can suggest that might help. The first is the incremental compile flow. This is more useful with designs smaller changes between design iterations. With this flow, a previous reference checkpoint will be used by the implementation tools to complete the placement and routing of the new version. The Implementation Guide has more on this on page 94: http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug904-vivado-implementation.pdf There is also Hierarchical Design flows. There are several levels of reuse, but you could physically separate areas that you want to keep the same placement and routing. You might not see the same QOR though, as the physical separation will limit the placement and routing options. The below Hierarchical Design Guide has more information. http://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_4/ug905-vivado-hierarchical-design.pdf |
|
|
|
感谢您的回复。
我将尝试#2进行层次结构设计。 对于增量编译,我之前尝试过,更糟糕的是。 陈平 2018年4月6日 以上来自于谷歌翻译 以下为原文 thanks for reply. I will try #2 for hierarchy design. For incremental compile, I tried it before, even worse. Ping Chen 2018.4.6 |
|
|
|
@chenpingx,
你尝试过HD流吗? 此外,如果你可以通过增量编译流程分享显示不良结果的设计,那么我可以将它转发到Factory。 --Syed -------------------------------------------------- -------------------------------------------请注意 - 请标记答案 如果提供的信息有用,请“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢Kudos .------------------------ -------------------------------------------------- ------------------- 以上来自于谷歌翻译 以下为原文 @chenpingx, Did you try the HD flow? Also if you can share the design which is showing bad results with incremental compilation flow then I can forward it to Factory. --Syed --------------------------------------------------------------------------------------------- Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful. Give Kudos to a post which you think is helpful and reply oriented. --------------------------------------------------------------------------------------------- |
|
|
|
感谢你的信息。
更新状态。 应用LOC约束IDDR / ODDR后,获得良好的实现结果非常一致,只需-0.2 ns设置时序违规。 所以,我认为现在好了。 对于高清,我不尝试。 陈平 2018年4月10日 以上来自于谷歌翻译 以下为原文 thanks for your information. update the status. After applying the LOC constrains the IDDR/ODDR, it is quite consistent to get the good implementation result, just -0.2 ns setup timing violation. So, i think it is OK now. For HD, i don't try it. Ping Chen 2018.4.10 |
|
|
|
@chenpingx,
感谢更新。 为了关闭时间,我会要求您在计时板上发布新查询。 请通过标记@ marcbas的上述帖子“接受为解决方案”来关闭此主题 --Syed -------------------------------------------------- -------------------------------------------请注意 - 请标记答案 如果提供的信息有用,请“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢Kudos .------------------------ -------------------------------------------------- ------------------- 以上来自于谷歌翻译 以下为原文 @chenpingx, Thanks for the update. For closing on timing, i would request you to post the new query in timing board. Please close this thread by marking the above post of @marcb as "Accept as Solution" --Syed --------------------------------------------------------------------------------------------- Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful. Give Kudos to a post which you think is helpful and reply oriented. --------------------------------------------------------------------------------------------- |
|
|
|
只有小组成员才能发言,加入小组>>
2384 浏览 7 评论
2800 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2264 浏览 9 评论
3336 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2431 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
757浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
547浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
369浏览 1评论
1965浏览 0评论
684浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-25 05:18 , Processed in 1.447098 second(s), Total 87, Slave 71 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号