using MicroBlaze SoC with OPB_DDR in ISE flow

A

Antti Lukats

Guest
Hi

A SoC done with EDK 6.1 using OPB_DDR core works OK in XPS but when the SoC
is used in ISE flow the Xilinx OPB_DDR doesnt pass translate stage with
error that asyn_fifo edif can not be loaded due to pin name mismatch!

how to make it work? there should be some fix, but can not find in Xilinx
answer database at least!

thanks!

Antti
http://xilinx.openchip.org
 
Can you check that the ddr_v1_00_b_virtex2_async_fifo.edn file
is located in the <proj>/implementation directory?

I think problem is when you do an export-to-projnav flow, XPS has
location pointers to all your wrapper NGC files, but not the BBD
specified netlists. So if you run projnav in a directory other
than <proj>/implementation, you won't pick up the BBD netlists.
It's just a matter of moving ddr_v1_00_b_virtex2_async_fifo.edn
to directory where you kick-off ngdbuild.

This is fixed in EDK.6.2i.


Antti Lukats wrote:
Hi

A SoC done with EDK 6.1 using OPB_DDR core works OK in XPS but when the SoC
is used in ISE flow the Xilinx OPB_DDR doesnt pass translate stage with
error that asyn_fifo edif can not be loaded due to pin name mismatch!

how to make it work? there should be some fix, but can not find in Xilinx
answer database at least!

thanks!

Antti
http://xilinx.openchip.org

--
/ 7\'7 Paulo Dutra (paulo.dutra@xilinx.com)
\ \ ` Xilinx hotline@xilinx.com
/ / 2100 Logic Drive http://www.xilinx.com
\_\/.\ San Jose, California 95124-3450 USA
 
"Paulo Dutra" <paulo.dutra@xilinx.com> wrote in message
news:407B22FE.1080307@xilinx.com...
Can you check that the ddr_v1_00_b_virtex2_async_fifo.edn file
is located in the <proj>/implementation directory?

I think problem is when you do an export-to-projnav flow, XPS has
location pointers to all your wrapper NGC files, but not the BBD
specified netlists. So if you run projnav in a directory other
than <proj>/implementation, you won't pick up the BBD netlists.
It's just a matter of moving ddr_v1_00_b_virtex2_async_fifo.edn
to directory where you kick-off ngdbuild.

This is fixed in EDK.6.2i.
Thanks!!!!

it was so simple !!

Antti
 

Welcome to EDABoard.com

Sponsor

Back
Top