AR# 59568
2014.1 - Vivado IP Integrator - How to handle ELF/BMM when using an IPI design added as a DCP in Vivado
Description
This Answer record describes the flow of how handle the ELF and BMM files in a Vivado project containing an IPI sub module added as a DCP (Design Check Point).
Note: For information on how to handle this flow with a Netlist/EDIF sub module, please see (Xilinx Answer 53064).
Solution
Please follow the steps below.
- Add the ELF and the BMM files as sources to the project.
In Project Mode:
In Non-Project Mode, the respective TCL commands are as follows:
add_files -norecurse test.elf
2. Associate the ELF file.
In Project Mode:
In Non-Project Mode, the respective TCL commands are seen below:
#Associate the ELF files
set_property MEMDATA.ADDR_MAP_CELLS {design_1_i/microblaze_0} [get_files test.elf]
3. Point to the respective hierarchy in the BMM file. This will ensure that the back-annotated (_bd) BMM file is created and placed in the impl_x folder.
set_property SCOPED_TO_REF {design_1_i} [get_files design_1.bmm]
4. Implement the Project:
synth_design -top design_1_wrapper -part xc7k325tffg900-2
place_design
route_design
In Project Mode, we can open the BRAM instances and check the properties to verify that the BRAM's are initialized:
Highlighted the found BRAM and in the cell properties, the INIT_xx should be populated with the information from the ELF file:
In Non-Project Mode, the respective TCL commands are seen below:
#Verify the INIT_xx was correctly initialized with ELF data
get_property INIT_00 [get_cells {PATH TO BRAM INSTANCE}]
Note: If either the back-annotated BMM file was not generated, or the INIT_xx was not populated, then please revisit steps 3 and 4 respectively and verify that the hierarchy is correct and that the names are correct.