What could be the problem?

=========================================================================

  • Design Hierarchy Analysis * ========================================================================= Analyzing hierarchy for entity in library (architecture ). ERROR:Xst - Xst_HdlConst_Imp::GetArrayValueByIndex : index out of range. ERROR:Xst - Unexpected error found while building hierarchy.
--
Total memory usage is 123236 kilobytes

Number of errors   :    2 (   0 filtered)
 Click to see the full signature
Reply to
Pablo
Loading thread data ...

Hi Pablo; Problem No.1: You are not able to read and understand error messages. Problem No.2: You have not understood that errors are caused by what's written in the source code.

Really now, how do you expect that anyone can help you with the error message when you do not provide the source code that caused the error?

When the message says "Index out of range", well, then there must be some index in your sources out of the allowed numerical range.

Have a nice synthesis Eilert

Pablo schrieb:

Reply to
backhus

what I don't understand is why ISE doesn't specify "the error signal/ constant". Usually, ise tells the "error line", but in this kind it doesn't specify anything about a source code (which contains 800 lines).

Reply to
Pablo

What I don't understand is how this design passed simulation tests without catching something as basic as an out of range index.

But anyway, if you can't find an error in an 800-line source file, split it into two (or more) smaller source files, and find out which one contains the error.

Repeat until error found.

- Brian

Reply to
Brian Drummond

Is this a source error though? The error message quoted was:

ERROR:Xst - Xst_HdlConst_Imp::GetArrayValueByIndex : index out of range. ERROR:Xst - Unexpected error found while building hierarchy.

This implies that something failed in a function called "GetArrayValueByIndex". This, combined with the lack of a line number, suggests to me that this is an internal run-time error from XST, not a source error, that is being reported.

Reply to
David Spencer

I think it's likely that there is a problem with the source ( maybe something not synthesizable which didn't get detected earlier) which is causing a late stage in the processing to give an error. I would think an industrial strength synthesizer would be able to give a better error message earlier.

Reply to
Muzaffer Kal

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.