在路由后物理选择设计期间遇到未放置的实例

好的 - 所以我猜这个故事的寓意是错误应该是我暗示设计中有问题。
我有一些控制寄存器逻辑错误导致有问题的实例被修剪。
我没有找到任何实际的消息表明情况，但我自己发现了错误。
一旦修复，我可以在不设置DONT_TOUCH属性的情况下运行phys opt，一切正常。
当我在综合后期和后期实现原理图中看到实例时，我感到很困惑。
我很感激帮助！
在原帖中查看解决方案



以下为原文

OK - so I guess the moral of the story is that the errors should have been my hint that there was something wrong in the design. I had some control register logic mistakes that were causing the instances in question to be trimmed. I didn't find any actual messages indicating that to be the case, but I found the errors on my own. Once fixed, I can run through phys opt without the DONT_TOUCH properties set, and everything works fine. I was confused when I saw the instances in post-synthesis and post-implementation schematics. I appreciate the help!View solution in original post

如果对相关的IO单元应用DONT_TOUCH =“是”，是否会发生任何变化？
不要忘记通过接受帖子作为解决方案来尽可能地关闭线程。



以下为原文

Does anything change if you apply a DONT_TOUCH = "yes" to the IO cell in question?
Don't forget to close a thread when possible by accepting a post as a solution.

@ rhc110again，
你能从.runs / impl_1文件夹共享runme.log文件吗？
检查设计中的所有单元格是否都放在place_design命令之后。
您也可以共享post opt dcp文件吗？
--Syed
--------------------------------------------------
-------------------------------------------请注意 - 请标记答案
如果提供的信息有用，请“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢Kudos .------------------------
--------------------------------------------------
-------------------



以下为原文

@rhc110again,

Can you share the runme.log file from .runs/impl_1 folder? Check if all the cells in design are placed after place_design command. 
 
Also is it possible for you to share the post opt dcp file?
 
--Syed
---------------------------------------------------------------------------------------------
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.
---------------------------------------------------------------------------------------------

@ jmcclusk，这就是诀窍。
如果我将DONT_TOUCH应用于5个实例中的每个实例，那么我可以运行我的实现和Tcl脚本。
显然，这引出了一些其他问题。
为什么会这样？
我将来可以避免它吗？
或者我现在的设计程序如下：1。
进行设计变更。
尝试综合和实施。
如果在路由后的phys opt和Tcl脚本中发现任何实例未被放置，则在它们上应用DONT_TOUCH。
转到第2步。



以下为原文

@jmcclusk,

That does the trick. If I apply DONT_TOUCH to each of the 5 instances, then I can run my implementation and Tcl script. This begs a few other questions, obviously. Why does this happen? Can I avoid it in the future? Or will is my design procedure now as follows:

1. Make design changes.
2. Try to synthesize and implement.
3. If any instances are found to be unplaced during post-route phys opt and Tcl script, then apply DONT_TOUCH on them.
4. Go to Step 2.

@syedz，
我附上了我的runme.log，我通过评论我在@ jmcclusk建议中添加的DONT_TOUCH属性重新创建了错误。
我不习惯附加任何dcp文件，除非你能保证我不包含任何源文件。
runme.log 2861 KB



以下为原文

@syedz,
 
I've attached my runme.log, which I recreated with the errors by commenting the DONT_TOUCH properties I added at @jmcclusk's recommendation.
 
I'm not comfortable attaching any dcp files, unless you can assure me they don't contain any source files.
            runme.log ‏2861 KB

好的 - 所以我猜这个故事的寓意是错误应该是我暗示设计中有问题。
我有一些控制寄存器逻辑错误导致有问题的实例被修剪。
我没有找到任何实际的消息表明情况，但我自己发现了错误。
一旦修复，我可以在不设置DONT_TOUCH属性的情况下运行phys opt，一切正常。
当我在综合后期和后期实现原理图中看到实例时，我感到很困惑。
我很感激帮助！



以下为原文

OK - so I guess the moral of the story is that the errors should have been my hint that there was something wrong in the design. I had some control register logic mistakes that were causing the instances in question to be trimmed. I didn't find any actual messages indicating that to be the case, but I found the errors on my own. Once fixed, I can run through phys opt without the DONT_TOUCH properties set, and everything works fine. I was confused when I saw the instances in post-synthesis and post-implementation schematics. I appreciate the help!