user constraint file of slice based bus macro in virtex 4

Jan 12, 2007 0 Replies

Hello,



Is there anyone doing partial reconfiguration in Virtex 4? I currently suffer from errors in the "active module" phase.



I made bus macros connecting two slices(for example: x0y2 and x2y2), and manually inserted the LOC constaint in ucf file like this: INST "bm16/bus4" LOC = "SLICE_X34Y6" ; INST "bm16/bus3" LOC = "SLICE_X34Y4" ; INST "bm16/bus2" LOC = "SLICE_X34Y2" ; INST "bm16/bus1" LOC = "SLICE_X34Y0" ;



when i activated reconfigurable module using command "ngdbuild -modular module -active [moduleName] ..\top\top.ngc", errors appeared:



ERROR:NgdBuild:630 - module 'bm16/bus1' is missing an AREA_GROUP property. WARNING:NgdBuild:885 - logical block 'bm16/bus1' with type 'bm_2b_v4_eastwest' is unexpanded and will be presumed to be a module. ERROR:NgdBuild:630 - module 'bm16/bus2' is missing an AREA_GROUP property. WARNING:NgdBuild:885 - logical block 'bm16/bus2' with type 'bm_2b_v4_eastwest' is unexpanded and will be presumed to be a module. ERROR:NgdBuild:630 - module 'bm16/bus3' is missing an AREA_GROUP property. WARNING:NgdBuild:885 - logical block 'bm16/bus3' with type 'bm_2b_v4_eastwest' is unexpanded and will be presumed to be a module. ERROR:NgdBuild:630 - module 'bm16/bus4' is missing an AREA_GROUP property. WARNING:NgdBuild:885 - logical block 'bm16/bus4' with type 'bm_2b_v4_eastwest' is unexpanded and will be presumed to be a module.



is there anything wrong with my constaint?



I refered several partial reconfiguration guides, in which bus macros had no AREA_GROUP property but INST properties. however, these guides are focused on vitex2 series. if anyone have virtex 4 partial reconfig tutorials, please let me know :-)



Perry



Join the Discussion

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

Didn't find your answer?

Ask the community — no account required