par 13.1丢弃了一些交换机可能是bug？

如果使用-timing选项运行map，则放置由map完成。
由于成本表选项-t仅影响放置，因此交换机与PAR无关，PAR仅在此方案中进行路由。
我没有看到你的附件，所以我不太确定发生了什么，但它听起来并不比不一致的消息更严重。



以下为原文

If you are running map with the -timing option then the placement is done by map. Since the cost table option -t only affects placement, the switch is irrelevant to PAR which only does routing in this scenario. I don't see your attachment so I'm not quite sure what is going on, but it doesn't sound any more serious than inconsistent messaging.

感谢回复，
问题是何时不使用-timing。
在这种情况下，par将始终使用默认设置（-t 1）并忽略正在传递的-t参数。
我再次尝试附加示例项目。
本
test_par131.zip 73 KB



以下为原文

Thanks for replying,
The problem is when -timing is NOT used. In this case par will always use the default setting (-t 1) and disregards the -t argument that is being passed.
I try attaching the sample project once again.
Ben
            test_par131.zip ‏73 KB

在转到13.1版本时，Xilinx可能会忽略一些旧设备
对于较新的设备（自V4起），-timing选项不可用，地图将始终可用
放置以及切片包装。
所以对于那些设备，-t选项毫无意义
相提并论
您可能希望恢复为Spartan 3系列的旧版ISE。
12.4应该
工作得很好。
-  Gabor
-  Gabor



以下为原文

It's possible that Xilinx overlooked some of the older devices when going to version 13.1
For newer devices (since V4) the -timing option is not available and map will always do
the placement as well as slice packing.  So for those devices the -t option makes no sense
to par.  You may want to revert to an older version of ISE for the Spartan 3 series.  12.4 should
work well.
 
-- Gabor
-- Gabor

我有很多项目，我试图从10.1.03迁移，其中一切都按预期工作。
这些是嵌入式项目，出于某些原因我希望它们迁移。
我不能使用10.1和13.1之间的任何版本，因为我没有这些版本的许可证所以我宁愿等待修复。
这是我们支付许可证的软件，只要设备受到支持，这被证明是一个错误，我认为我们有权要求修复错误。
因此，使用旧版本是不可能的。
我可以解决这些问题，但只需要花费更多的时间进行成本表搜索并满足时间要求。
本



以下为原文

I have a number of projects which I am trying to migrate from 10.1.03 where everything works as expected. Those are embedded projects which for some good reasons I want them migrated. I can't use any version between 10.1 and 13.1 because I don't have the license for those versions so I would rather wait to get this fixed.
This is software for which we paid a licence and as long as the devices are supported and this proves to be a bug I think we have the right to request the bug to be fixed. So, using an older version is out of question.
I can workaround those problems but it just takes a lot more time to do a cost table search and to meet the timing.
Ben

这是我们支付许可证的软件，只要是设备
支持，这证明是我认为我们有权利的错误
请求修复错误。
当然你有这个权利。
但是不要指望立即修复错误。
所以，使用旧版本是不合适的
题。
不，这不对。
如果您是大批量客户，我相信您的客户代表会尽一切努力让您的项目再次发展。
即使你不是一个大狗客户，你的代理人也可能很好地制定12.4的短期许可证。
我不为Xilinx工作而且我不代表他们，但这对双方来说都是一个完全合理的解决方法，直到show-stopper问题得到解决。
在“闲暇时”，您可以下载12.4软件并（使用试用许可证）验证它是否可以满足您的项目需求。
这将为您提供一个经过验证的选项，可以向Xilinx提出解决方案。
当然，如果您的项目迁移没有特别紧迫，那么您可以等待错误修复在系统中运行。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

This is software for which we paid a licence and as long as the devices are supported and this proves to be a bug I think we have the right to request the bug to be fixed.

Of course you have that right.  But don't expect an immediate bug fix.

So, using an older version is out of question.

No, it's not.
 
If you are a high-volume customer, I'm sure your account rep will do whatever it takes to get your project moving again.  Even if you aren't a big-dog customer, your acct rep might very well work out a short-term license for 12.4, for example.  I don't work for Xilinx and I don't speak for them, but this would be an entirely reasonable workaround for both parties until the show-stopper problem is resolved.
 
In your 'spare' time, you might download the 12.4 software and (with a trial license) verify that it could meet your project needs.  This will give you a proven option to propose to Xilinx as a workaround.
 
Of course, if there is no particular urgency for your project migration, then you can afford to wait for the bug fix to work its way through the system.
 
-- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.

致所有可能感兴趣的人：
这证明是一个错误，一个变更请求正在等待，并承诺在13.3中修复
问候，
本



以下为原文

To all who may be interested:
this proved to be a bug and a change request is pending with a promise to be fixed in 13.3
Regards,
Ben

请注意，没有承诺在特定版本的工具中修复CR。
--------------------------------------------------
-----------------------不要忘记回答，kudo，并接受为解决方案.-------------
--------------------------------------------------
----------



以下为原文

Please be aware that no CRs are ever promised to be fixed in a specific version of the tools.
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------