最近,PAR一直在显示消息“TASK FINISHED WITH 1 ERRORS”。
这在第3阶段和第4阶段之间发生一次或两次。设计永远不会完全路由到第5阶段。我的设计能够关闭时间(好,足够接近!)和完全路由。
这条消息的出现是最近的,虽然我无法找出原因。
谷歌搜索和
论坛搜索还没有帮助(虽然我可能只是做错了!)
我在Linux上使用64位ISE 13.2,并在V6 LX550T上构建,其中包含许多内部生成的时钟域,大量GTX端口以及相当积极的楼层规划。
偶尔我也会得到一个警告:在MAP期间放置:913,这似乎也是一个新的消息。
使用EDIF和完全路由的NCD分析planAhead中的设计显示没有网络通过警告消息中引用的SLICE,因此我也没有运气,但我认为自MAP和PAR以来值得一提
消息可能是相关的。
有没有人看过这个不起眼的PAR消息?
我是否应该花费更多的时间来追踪它,或者它是PAR barfs有时会发出的模糊和无害的消息之一(比如'pin bounce'消息)?
谢谢,
-acr4
以上来自于谷歌翻译
以下为原文
Recently, PAR has been displaying the message "TASK FINISHED WITH 1 ERRORS".
This occurs one or two
times, between Phase 3 and 4. The design is never fully routed until Phase 5. My design is able to close timing (well, close enough!) and fully route.
The occurance of this message is pretty recent, although I have been unable to isolate the cause. Google-search and forum-search haven' t helped yet either (although I may just be doing it wrong!)
I am using 64-bit ISE 13.2 on Linux, and building on a V6 LX550T with lots of internally-generated clock domains, lots of GTX ports, and fairly aggressive floor-planning.
Occasionally I also get a WARNING:Place:913 during MAP, which seems to also be a fairily new message. Analyzing the design in planAhead w/ an EDIF and fully-routed NCD shows that no nets route through the SLICE referenced in the warning message, so I'm having little luck there too, but I figured it was worth mentioning since the MAP and PAR messages may be related.
Has anyone seen this obscure PAR message? Should I spend any more time tracking it down or is it one of the obscure and h
ARMless messages that PAR barfs sometimes (like 'pin bounce' message)?
Thanks,
-acr4