11-05-2013 10:39 AM
I have been battling this for a few days. I have a project in which I instantiate a microblaze MCS core that I created from the IP catalog.
After implementation, it doesn't generate the merged BMM file. I fiddled around for days with associating elf files and trying manual stuff (eg write_bmm). I gave up, and then noticed that the BMM file was being generated in the impl_0 folder now!
I was able to do a few things in SDK, but after I changed a setting in the MCS core (frequency change), the BMM stopped getting generated. Now, I cannot get it back.
Any thoughts? I found this record: http://forums.xilinx.com/t5/Vivado-TCL-Community/Write-bmm/td-p/336723. However, it claims to have a procedure that would work, but I still can use 'write_bmm'.
11-05-2013 01:14 PM
Are you using IPI? or just a standalone MCS core in Vivado?
If in IPI, try do a generate output products. If in Vivado, do a reset all on your builds.
open the run, and right clcik, and choose reset...
11-30-2013 09:07 AM
this is a bug in Vivado 2013.3 we have filed WebCase and there is no clean solution at the moment.
Wait for 2013.4 release, maybe for Christamas.
05-28-2014 12:04 AM
With the MicroBlaze MCs core, the export to SDK is done by the core itself, and the hardware description XML file can be found in the IP core subdirectory, for example project_1.srcs/soures_1/ip/microblaze_mcs_1/microblaze_mcs_1_sdk.xml.
See http://www.xilinx.com/support/documentation/sw_manuals/xilinx2014_1/pg116-microblaze-mcs.pdf (page 30-31) for details.