area group constraint problem

Nov 27, 2007 4 Replies

Hello together,



in my vhdl design for ISE 9.2 I want to partition the component instances of the submodules in my toplevel into defined areas of my fpga ic.



I have never done this but had seen some examples before, where it might have worked (e.g. projects with reconfiguration).



So I adapted my ucf-file accordingly by adding several area group constraints and assigned an instance for each area group like in this short example snippet:



AREA_GROUP "ag1" RANGE = SLICE_X0Y0:SLICE_X50Y50; INST instance_name_of_first_component_from_toplevel AREA_GROUP = ag1; AREA_GROUP "ag2" RANGE = SLICE_X51Y0:SLICE_X100Y50; INST instance_name_of_second_component_from_toplevel AREA_GROUP = ag2; ...



But now I'm getting an error (while implementation stage - don't know exactly at the moment). The error message says roughly, that the instances cannot be found (something like that) and i'm proposed to delete the relevant constraint to go on.



I use the label name of the component port map statement in my toplevel as the instance names inside the ucf.



Is this wrong or what's the problem? Any suggestions?



I can't post the exact error message at the moment, but it will be given later if it's necessary.


I have read, that it is possible to generate or extract such area constraints by using the floorplanner. Does anyone know a helpful and not too sparse tutorial for the floorplanner, especially for my purpose?


Thanks a lot. L. Schreiber


Make sure you include the path to the signals if there is a heirarchy.

---Matthew Hicks

Hi, An addendum to Matthew Hicks comment,

use "modulename_*" to define area group for all signals if you explode the hierarchy.

/MH

Ok, the error occured while translation in implementation phase.

Here is the exact error message from the translation report:

Reading NGO file "/home/schrl/ise/virtex2p/reconf_rs232/top.ngc" ...

Applying constraints in "top.ucf" to the design... ERROR:NgdBuild:753 - "top.ucf" Line 27: Could not find instance(s) stat_r' in the design. To suppress this error specify the correct instance name or remove the constraint.

I'm trying these first suggestions from M. Hicks and MH.

thx

Okay, last thursday i found the reason for this error. I have missablied the modular design flow.

That's why your proposals haven't solved the problem. Anyway, thanks for your rapid replies.

Now it works! :-)

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required