[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [partial-reconfig] Problem with Bus macro in Virtex-II
Thanks for your answers friends,
Now I have curiosity of like using XDL to modify to bus macro, because
I tried to use xdl (xdl -ncd2xdl bm_4b_v2.nmc) but i couldn´t modify a bus
macro as I want. I have the xdl´s of bus macros(Virtex and virtex II).
Can you explain me how i adding a PIP for the TBUF of TNET(3)?, but i
don´t know!
Thanks in advance
John Edward ESquiagola Aranda
> John Williams wrote:
>
>> Hi John
>>
>> jedward@lme.usp.br wrote:
>>
>>> I am using ISE6.2i, and Virtex-II X2CV1000. When i use:
>>>
>>> "ngdbuild -modular initial top.ngc"
>>>
>>> The tool reports some errors with the bus macro, like this:
>>>
>>> Reading component libraries for design expansion...
>>> Loading device for application ngdbuild from file '2v1000.nph' in
>>> environment
>>> C:/Xilinx.
>>> Loading macro from file "E:\John\exemplo\top\inicial/bm_4b_v2.nmc".
>>> ERROR:NgdBuild:76 - File "E:\John\exemplo\top\inicial/bm_4b_v2.nmc"
>>> cannot
>>> be merged into block "BM_reconfig_1_to_capture_result"
>>> (TYPE="bm_4b_v2")because one or more pins on the block, including pin
>>> "LI<3>", were not found in the file.
>>
>>
>> There is a Xilinx answer record on this one:
>>
>> http://support.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=14848>>
>>
>>
>> Basically it's to do with signal vectors using the '< >' vs '( )'
>> synatx. If I remember rightly, I just hand edited the bus macro file
>> in hexedit, and changed the characters appropriately.
>
> A more appropriate way is to use the xdl command, to recompile the bus
> macro, e.g.
>
> xdl -ncd2xdl bm_4b_v2.nmc
> this will result in a human readable xdl file. Just now you can
> correct an error in the Virtex bus macro, adding a PIP for the TBUF of
> TNET(3) or may be TNET<3> or ... :-). Than compile it
>
> xdl -xdl2ncd bm_4b_v2.xdl
> Here, you obtain bm_4b_v2.ncd, simply rename it to bm_4b_v2.nmc. Well
> done, now you will have less problems with strange routing of the
> TNET(3).
>
> BTW, the Virtex Pro (bm_4b_v2p.nmc) suffers from this error too.
>
>
> Regards,
>
>
> --
> Dr. Thomas Reinemann www.uni-magdeburg.de/reineman
> IMAT Public key available
> Otto-von-Guericke-Universität Magdeburg
> Universitätsplatz 2
> 39106 Magdeburg, Germany
___________________________
partial-reconfig mailing list
partial-reconfig@itee.uq.edu.au
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/partial-reconfig/