12-12-2012 06:37 PM
I took my EDK design and incorporated it as a submodule into my Top Level custom Verilog design. I was able to generate the bitstream etc and Export HW for SDK. I then tried making a project and Application in SDK using the system.bit & system.bmm files. But in SDK, when I tried Xilinx Tools -> Program FPGA I started getting this ELF Check error. I can only guess that putting the EDK module inside my Top Level module screwed up the path for the microblaze processor. However the .bmm file path looks correct : EdkTopAxi/AxiDMov2Mig_i//microblaze_0.
elfcheck -hw \
-mode bootload -mem BRAM -pe AxiDMov2Mig_i/microblaze_0 \
Xilinx EDK 14.3 Build EDK_P.40xd
Copyright (c) 1995-2012 Xilinx, Inc. All rights reserved.
Command Line: elfcheck -hw
system.xml -mode bootload -mem BRAM -pe AxiDMov2Mig_i/microblaze_0
ELF file : C:/Xilinx/14.3/ISE_DS/EDK/sw/lib/unknown_arch/unknown_bootloop.elf
Processor AxiDMov2Mig_i/microblaze_0 NOT present in the Hardware System
Internal Error: Processor AxiDMov2Mig_i/microblaze_0 NOT present in the Hardware
Programming the FPGA failed due to errors from elfcheck
12-13-2012 04:09 AM
If you added the EDK as a xmp file, then the tools will pull in the BMM file during NDGBuild (this creates the back annotated BMM file). So you should be using the back annotated BMM file in SDK not the BMM file. Can you verify that this is true.
If it is not generated, can you right click on Translate in ISE, and process properties, under other option add the -bm system.bmm
Also, can you review the created back annotated bmm file (will have the name xxx_bd.bmm). To see if the hierarchy is correct. If you are usign the edk submodule, this will need an edded layer of hierarchy that may not be getting generated correctly. Also, make sure the tag is correct for the same reason. This can be checked in the BMM file, after the ADDRESS_MAP. this should be similar to <ise_top><system_i>, basically, it should include the top level ise name in the tag too.
However, I would imagine this would cause a data2mem issue (http://www.xilinx.com/support/answers/51180.htm)