基于linux的ise和基于windows的ise之间的区别

你好@ peter3swi
您使用的是哪个Windows版本？
你也检查了Windows中设计的行为模拟吗？
问候
罗希特
RegardsRohit -------------------------------------------------
---------------------------------------------请注意 - 请注明
答案为“接受为解决方案”，如果提供的信息是有帮助的。给予您认为有用并回复导向的帖子。感谢K--
--------------------------------------------------
----------------------



以下为原文

Hi @peter3swi
 
Which Windows version you are using? 
Also did you check the behavioral simulation of the design in Windows?
 
Regards
Rohit
Regards
Rohit
----------------------------------------------------------------------------------------------
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.
----------------------------------------------------------------------------------------------

谢谢你的回复。
Windows版本是7专业版，服务包1。
我知道没有行为差异，因为当我将时钟速度从100Mhz降低到60Mhz时，一切都有效，但数据吞吐量下降，这是目前不可接受的。
但是当速度为100Mhz时，根本没有任何作用，甚至基本的通信都没有。
如果有什么我可以尝试，请告诉我。
谢谢



以下为原文

Thanks for the response.
 
The windows version is 7 professional with service pack 1.
 
I know there is no behavior differences because when I slowed the clock speed down from 100Mhz to 60Mhz everything worked with the exception that the data throughput dropped, which is not acceptable at the moment.  But when the speed is 100Mhz then nothing works at all, not even the basic communication.
 
Please let me know if there is anything I can try.  Thanks
 
 

听起来你可能在设计中有无约束或不正确约束的路径。
当您运行Place＆amp; Route时，由于初始放置种子，结果会有一些随机性。
这些可能因Linux而异，甚至在完全无关的更改后也可能在同一平台下。
减慢时钟的事实似乎有助于计时。
如果您有Linux运行的时序报告，则应将其与Windows运行进行比较。
我还建议在Post Place＆amp; Route定时生成中启用无约束路径的报告。
这可以显示完全缺少约束的路径。
您仍需要检查现有约束以确保它们与系统的实际运行参数相匹配。
另一件需要检查的是Linux和Windows机器之间的所有项目参数都是相同的。
如果您复制了.xise文件，则应该是这种情况。
-  Gabor



以下为原文

It sounds like you might have unconstrained or improperly constrained paths in the design.  When you run Place&Route, there is a bit of randomness in the results due to initial placement seeds.  These can vary from Linux to Windows, or even under the same platform after making totally unrelated changes.  The fact that slowing down the clock helps seems to point to timing.  If you have the timing report from the Linux run, you should compare it to the Windows run.  I'd also suggest enabling the reporting of unconstrained paths in Post Place&Route timing generation.  That could show you paths that are missing constraints entirely.  You still need to go through the existing constraints to make sure they match the actual running parameters of your system.  Another thing to check is that all of your project parameters are the same between the Linux and Windows machines.  This should be the case if you copied the .xise file.
-- Gabor