完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
|
嗨,
我不确定时间限制到底是做什么的。 例如,OFFSET OUT AFTER-在这种情况下,存在来自下游设备的输入时钟。 从FPGA到此下游设备的所有数据传输都应在此时钟的上升沿。 时钟周期为30ns,建立时间为10ns。 AFTER约束基本上表示从输入时钟到达输入引脚的时间到数据熄灭的时间的最大时间,时钟的上升沿可以是约束中指定的时间的最大值。 这看起来不是设置时间。 它也不是时候。 如何使用此AFTER约束指定设置和保持时间 其次,约束是否会影响pAR? 我正在读,它只是检查并且实际上没有改变PAR中的任何内容。 告诉别人请告诉我? 以上来自于谷歌翻译 以下为原文 Hi, I am a little unsure of what exactly the timing constraints actually do. For example the OFFSET OUT AFTER- IN this case there is an input clock coming from an downstream device. All data transfer from the FPGA to this downstrea device is to be on the rising edge of this clock. The clock period is 30ns, and the setup time is 10ns. The AFTER constraint basically says the maximum time from the time the time the input clock arrives on the input pin to the time the data goes out with the rising edge of the clock can be a maximum of the time specified in the constraint. This doesnt look to be setup time. It isnt hold time either. How do I specifiy the setup and hold times using this AFTER constraint Second, does the constraint affect pAR? I was reading that it is only to check and doesnt actually change anything in the PAR. COuld someone please let me know? |
|
相关推荐
5个回答
|
|
|
我想这个实现会受到时钟路径的影响,如果它通过内部结构元素(如MMCM等)进行路由。对于数据路径,理想情况下,路径实现可能不会受到约束的影响。
但是请通过在一些示例设计和检查中给出此约束来确认这一点。 另请阅读UG612 pg180了解详情 - http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/ug612.pdf 谢谢,AnirudhPS:请将此标记作为答案,以防它有助于解决您的问题。如果帖子引导您找到解决方案,请给予赞誉。 在原帖中查看解决方案 以上来自于谷歌翻译 以下为原文 The implementation I guess is affected for the clock path, if it is routed through an internal fabric element like MMCM etc. For the data path, ideally the path implementation might not be affected much with the constraints. However please confirm this by giving this constraint in some example design and check. Also read through UG612 pg180 for the details on this - http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/ug612.pdfThanks, Anirudh PS: Please MARK this as an answer in case it helped resolve your query.Give kudos in case the post guided you to a solution.View solution in original post |
|
|
|
|
|
嗨@roader
下面的文章讨论了OFFSET约束的总体目的,OFFSET约束覆盖的特定路径,以及OFFSET IN和OFFSET OUT约束之间的差异。 此外,定时报告的示例包括在OFFSET IN和OFFSET OUT约束的常见应用中 http://www.xilinx.com/support/documentation/white_papers/wp237.pdf 谢谢,维杰----------------------------------------------- ---------------------------------------------请将帖子标记为 一个答案“接受为解决方案”,以防它有助于解决您的查询。如果一个帖子引导到解决方案,请给予赞誉。 以上来自于谷歌翻译 以下为原文 Hi @roader The following paper discusses the overall purpose of OFFSET constraints, the specific paths that are covered by OFFSET constraints, and the differences between the OFFSET IN and OFFSET OUT constraints. Additionally, examples of timing reports are included with the common application of the OFFSET IN and OFFSET OUT constraints http://www.xilinx.com/support/documentation/white_papers/wp237.pdf Thanks,Vijay -------------------------------------------------------------------------------------------- Please mark the post as an answer "Accept as solution" in case it helped resolve your query. Give kudos in case a post in case it guided to the solution. |
|
|
|
|
|
我读过那篇论文。
但是,我的问题有点具体。 你能再看一遍吗? 以上来自于谷歌翻译 以下为原文 I have read that paper. However , my question is kind of specific . Could you please read it again? |
|
|
|
|
|
我想这个实现会受到时钟路径的影响,如果它通过内部结构元素(如MMCM等)进行路由。对于数据路径,理想情况下,路径实现可能不会受到约束的影响。
但是请通过在一些示例设计和检查中给出此约束来确认这一点。 另请阅读UG612 pg180了解详情 - http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/ug612.pdf 谢谢,AnirudhPS:请将此标记作为答案,以防它有助于解决您的问题。如果帖子引导您找到解决方案,请给予赞誉。 以上来自于谷歌翻译 以下为原文 The implementation I guess is affected for the clock path, if it is routed through an internal fabric element like MMCM etc. For the data path, ideally the path implementation might not be affected much with the constraints. However please confirm this by giving this constraint in some example design and check. Also read through UG612 pg180 for the details on this - http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/ug612.pdfThanks, Anirudh PS: Please MARK this as an answer in case it helped resolve your query.Give kudos in case the post guided you to a solution. |
|
|
|
|
|
你的时钟长30ns。
目标设备需要10ns才能进行设置。 因此,FPGA必须在时钟上升沿之后的20ns内准备好数据。 您可能需要花时间在电路板上进行传播 - 假设时钟需要0.3ns才能从下游设备传播,数据需要0.4ns才能传播回下游设备 - 您的20ns现在会下降到19.3。 OFFSET = OUT 19.3ns后; 使用ISE,无法在输出上指定保持要求 - 这是UCF约束语言(实际上是ISE定时引擎)的一个更重要的缺点。 是的,约束会影响地点和路线,除非所涉及的所有资源都是LOC到位置。 例如,如果您的时钟通过时钟引脚进入,则转到时钟缓冲器(带或不带DCM / PLL),然后转到IOB触发器,此路径中的任何内容都不能移动 - 所有资源都在 固定位置,它们之间有固定的路线。 因此,对于此路径,约束不会对放置产生任何影响 - 它们只会报告是否可以使用您描述的体系结构来满足时序。 Avrum 以上来自于谷歌翻译 以下为原文 Your clock is 30ns long. The destination device needs 10ns for setup. Therefore the FPGA must have the data ready no later than 20ns after the rising edge of the clock. You probably need to take out time for the propagation on the board - lets say the clock takes 0.3ns to propagate from the downstream device and the data takes 0.4ns to propagate back to the downstream devices - your 20ns now goes down to 19.3. OFFSET = OUT 19.3ns AFTER With ISE, there is no way to specify hold requirements on outputs - that is one of the more significant weaknesses of the UCF constraint language (really of the ISE timing engine). Yes, constraints will affect place and route, unless all the resources involved are LOC'ed to locations. For example, if your clock comes in on a clock pin, goes to a clock buffer (with or without a DCM/PLL) and then goes to an IOB flip-flop, nothing in this path can be moved - all the resources are in fixed locations with fixed routes between them. Therefore, for this path, the constraints will not have any effect on placement - they would just report whether the timing can be met with the architecture you describe. Avrum |
|
|
|
|
只有小组成员才能发言,加入小组>>
3118 浏览 7 评论
3407 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2873 浏览 9 评论
3966 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
3057 浏览 15 评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
1325浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
1167浏览 1评论
/9
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2025-12-2 02:50 , Processed in 0.613268 second(s), Total 82, Slave 65 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191

淘帖
1686
