09-05-2017 12:23 PM
I can't get a *.mmi file.
I have the block design.
There is the Address Editor.
When I try to create *.mmi file from Tcl Console.
I get this.
CRITICAL WARNING: [Memdata 28-122] data2mem failed with a parsing error. Check the bmm file or the bmm_info_* properties on the BRAM components. The design BRAM components initialization strings have not been updated.
CRITICAL WARNING: [Memdata 28-147] Could not complete BRAM data initialization for processor. Please check to ensure any BMM and ELF files in the design have correct proper scoping specified. Design will proceed but BRAM initialization strings will not be populated with contents of the ELF file.
ERROR: [Common 17-69] Command failed: Failed to create the: D:/out.mmi The design contains processors. Verify processor instances and connectivity.
The goal is to get access to any microblaze's memory from any microblaze.
09-13-2017 04:59 AM
12-25-2017 05:45 AM
Hello! I have the same problem...
After synthesizing and implementing design, I opened design by
Then I sourced the script:
Then I tryed to get mmi file
And I get
no files matched glob patterns "type -f D:/test.mmi"
I tryed write_mem_info -force D:/test.mmi
ERROR: [Common 17-69] Command failed: Failed to create the: D:/test.mmi The design contains processors. Verify processor instances and connectivity.
Version of Vivado is 2017.3
12-25-2017 07:11 AM
06-15-2018 01:28 AM
In the OP's issue. This is most likely due to the fact that there are 3 microblaze_0 (ie with the same name). This is likely confusing the tool.
@daniel2016. For your issue, can you describe your system (maybe a screenshot too?)
06-18-2018 08:16 AM
Thanks. We don't use microblaze and neither use the SoC name into the design. We use Microzed board (loaded with Zynq 7020).
07-20-2018 03:09 AM
I have created a wiki article on the memdata flow in Vivado:
Hopefully, this will help some users here