07-01-2009 09:40 AM
In my design, when setting "keep hierarchy" to "yes" in XST property, it fails because of several multi-driven signals, while succeed when setting it to "no".
And the signals said to be driven by several sources are obviously unrelated to the sources.That is, A,B are said to be the sources of C, A has something to do with C, but B has not a little thing to do with C.It's rediculous.
Can anybody help me and point out where I am wrong? Thank you very much!
07-03-2009 12:43 AM
07-01-2009 10:56 AM
How complex is your design. Doesn it include any large Xilinx cores like MIG.
I was also getting strange errors when tried to synthesize a design with MIG and "keep hierarchy" = "yes. I've never resolved it and kept using "keep hierarchy" = "no".
Another question. Why do you want to use "keep hierarchy"="yes" in the first place.
07-01-2009 05:24 PM
There is a PCI Express Core in my design.
I don't want to use "keep hierarchy" = "yes", because this will cause a decrease of ability of my design. But in this case, if "no" there will be a failure, so I have to use "yes".
Any other idea?
07-01-2009 05:34 PM
Well, have you talked with Xilinx TechSupport about this error ?
XST documentation on "Keep Hierarchy" says that :
" XST can flatten the design to obtain better results by optimizing entity or module boundaries. Very often, merging the hierarchy blocks improves the fitting results (fewer PTerms and device macrocells, better frequency) because the optimization processes (collapsing, factorization) are applied globally on the entire logic. "
I'm still not sure exactly what abilities of your design will decrease.
07-01-2009 07:43 PM
As you say, if "yes", XST will not flatten design to optimize. I think this is just like XST will optimize the design on each part of it. But only that is not enough. For example, if you have a lot of good components, you'll not get a 100% good system when you use the components to form a whole system. So optimize the design on the component level when "yes" will decrease the performance, in my opinion.
What's your opinion?
07-01-2009 07:49 PM
Sorry, but I'm still missing your point. What do you mean by "performance" ?
Functionally, the design with "yes" and "no" options is the same. As the XST documentation explains, flattening the design makes it easier to meet timing.
07-01-2009 08:01 PM
07-01-2009 08:26 PM
07-03-2009 12:43 AM