完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
大家好:
我有一个关于成本表/额外成本表配置和真实PR策略的问题。 在我的项目中,LUT的使用率约为70 +%,并始终满足PR问题。 它报告: 警告:路由:464 - 路由器检测到非常密集,拥挤的设计。 路由器极不可能完成设计并满足您的时序要求...... blablablabla 我向同事或其他论坛寻求帮助,并被告知,不同的成本表/额外成本表映射了不同的PR策略。 在我更改配置后,是的,有时PR可以完成。 但每次,我只是盲目地循环所有组合,直到得到一个好的组合:10/11/12/13/14/15/20/21 /.../ 25/30 / ......有时我有 不幸的是,尝试超过50次测试。 那么有人可以给我一些建议: 1.成本表意味着什么? - 我被告知它意味着随机种子的数量,或某些方程的参数,对吧? 2.额外费用表意味着什么? - 它的范围从0到5,而5意味着最大的努力将用于PR? 3.一个固定的成本表设置&& 不同的额外成本表设置意味着“具有不同公关努力的固定公关策略”? 4.对于464号公路警告,我应该使用哪种方法? 是否有默认解决方案,或者我必须盲目地一遍又一遍地进行测试? 这个问题困扰了我很长一段时间,我真的很期待你的所有建议和帮助。 谢谢! 以上来自于谷歌翻译 以下为原文 Hi all: I have a question about cost-table/extra-cost-table configuration and real PR strategy. In my project, the LUT usage is about 70+%, and always meet PR issues. It reports: WARNING:Route:464 - The router has detected a very dense, congested design. It is extremely unlikely the router will be able to finish the design and meet your timing requirements...... blablablabla I asked help from colleagues or via other forums, and was told that, different cost-table/extra-cost-table maps different PR strategy. After I changed the configuration, yes, sometimes PR can finish. But everytime, I was just looping all the combinations blindly until got a good one: 10/11/12/13/14/15/20/21/.../25/30/...... Sometimes I had to try over 50 tests, unfortunatly. So could anyone please give me some advices that: 1. cost-table means what? -- I was told it means the number of random seeds, or parameters of some equation, right? 2. extra-cost-table means what? -- it ranges from 0 to 5, and 5 means the most effort will be used for PR? 3. one fixed cost-table setting && different extra-cost-table setting means "a fixed PR strategy with different PR effort"? 4. for the Route 464 warning, which stratery should I use? Is there a default solution, or I have to test over and over again blindly? This question bothers me quite a long time, and I am really expecting all your suggestions and help. Thanks! |
|
相关推荐
4个回答
|
|
这是什么设备?
对于拥挤的设计,而不是担心自己用成本表自动翻转所有开关,我建议尝试使用-cr选项的SmartXplorer(拥塞减少)。 您可以在以下位置找到更多信息: http://www.xilinx.com/support/documentation/white_papers/wp381_V6_Routing_Optimization.pdf http://www.xilinx.com/cn/support/documentation/sw_manuals/xilinx13_4/devref.pdf(第155页) 以上来自于谷歌翻译 以下为原文 What device is this? For a congested design, rather than worry about flipping all the switches yourself with cost tables, I'd recommend trying SmartXplorer with the -cr option (congestion reduction). You can find more information in these locations: http://www.xilinx.com/support/documentation/white_papers/wp381_V6_Routing_Optimization.pdf http://www.xilinx.com/support/documentation/sw_manuals/xilinx13_4/devref.pdf (page 155) |
|
|
|
成本表(map -t)只是放置的随机种子。
更多细节在这里: http://www.xilinx.com/support/answers/35534.htm 额外的成本表(-xt)被引入以允许传递一些算法参数,这些参数会使布局偏向拥塞减少。 此选项应作为减少拥塞的最后手段,因为时序结果可能会受到影响。 如果您正在运行多个策略和成本表(SmartXplorer)并且运行成功。 您可以尝试引导成功运行或锁定自动放置的某些电压部分,例如Block RAM(和其他大块)放置和时钟放置。 以上来自于谷歌翻译 以下为原文 Cost tables (map -t) are just random seeds to placement. More details here: http://www.xilinx.com/support/answers/35534.htm Extra cost tables (-xt) were intoduced to allow some algorithmic parameters to be passed that bias the placer towards congestion reduction. This option should be used as a last resort to reduce congestion as timing results will likely suffer. If you are running multiple strategies and cost tables (SmartXplorer) and have a successful run. You can try guiding from that successful run or locking in some of the volitile portions of the automatic placement such as Block RAM (and other big block) placement and Clock Placement. |
|
|
|
HI Kpatel:我正在使用V6。
而且我已经尝试过smartxplorer,无论我何时使用7默认策略或-cr选项,PR都会失败。 以上来自于谷歌翻译 以下为原文 HI Kpatel: I am using V6. And I have already tried smartxplorer, PR fail, no matter when I was using 7 default strategy, or -cr option. |
|
|
|
您好Bwade:您的意思是“使用-smartguide选项”?
如果是,我还没有尝试过这个解决方案。 我下次可以测试一下。 以及如何“锁定一些不稳定的部分”? 听起来像手动实施PR。 我在哪里可以找到相关文件? 嗨Kpatel和Bwade:再次感谢您的帮助。 以上来自于谷歌翻译 以下为原文 Hi Bwade: You mean "using -smartguide option"? If yes, I haven't tried this solution. I can test it next time. And how to "lock in some of the volatile portions"? Sounds like implementing PR manually. Where can I find related documents? Hi Kpatel and Bwade: Again, thanks for your help. |
|
|
|
只有小组成员才能发言,加入小组>>
2429 浏览 7 评论
2831 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2298 浏览 9 评论
3378 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2468 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
1345浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
596浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
460浏览 1评论
2013浏览 0评论
738浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-28 18:39 , Processed in 1.398788 second(s), Total 82, Slave 66 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号