UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Observer fen1xl
Observer
2,444 Views
Registered: ‎03-23-2015

[Vivado 2017.2] Problem with *.mmi file

I can't get a *.mmi file.

 

I have the block design.

3x MicroBlaze System.png

There is the Address Editor.

Address Editor.png

 

When I try to create *.mmi file from Tcl Console.

 

write_mem_info D:/out.mmi

 

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.

Thanks.

0 Kudos
7 Replies
Moderator
Moderator
2,378 Views
Registered: ‎09-12-2007

Re: [Vivado 2017.2] Problem with *.mmi file

can you try with the attached script? 

source this from the tcl console, and use the command write_mem_info_int test.mmi for example

 

You will need to implment the design first

0 Kudos
Observer brainiac
Observer
2,146 Views
Registered: ‎02-19-2012

Re: [Vivado 2017.2] Problem with *.mmi file

Hello! I have the same problem...

After synthesizing and implementing design, I opened design by

open_run impl_1

Then I sourced the script:

source D:/workspace/write_mem_info.tcl

Then I tryed to get mmi file

write_mem_info_int D:/test.mmi

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

0 Kudos
Observer brainiac
Observer
2,134 Views
Registered: ‎02-19-2012

Re: [Vivado 2017.2] Problem with *.mmi file

I run write_mem_info_int test.mmi and script executed and file is empty
How to determine that everything is ok? I have project with 30% utilization of BRAM...
0 Kudos
Visitor daniel2016
Visitor
1,607 Views
Registered: ‎05-16-2018

Re: [Vivado 2017.2] Problem with *.mmi file

I have the same problem under both 2016.2 and 2018.1. Is there any solution on this?

0 Kudos
Moderator
Moderator
1,594 Views
Registered: ‎09-12-2007

Re: [Vivado 2017.2] Problem with *.mmi file

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?)

0 Kudos
Visitor daniel2016
Visitor
1,538 Views
Registered: ‎05-16-2018

Re: [Vivado 2017.2] Problem with *.mmi file

Thanks. We don't use microblaze and neither use the SoC name into the design. We use Microzed board (loaded with Zynq 7020).

 

0 Kudos
Moderator
Moderator
1,373 Views
Registered: ‎09-12-2007

Re: [Vivado 2017.2] Problem with *.mmi file

Hey Guys,

 

I have created a wiki article on the memdata flow in Vivado:

http://www.wiki.xilinx.com/Understanding+MEMDATA+flow+and+how+to+manually+create+MMI+file

 

Hopefully, this will help some users here

0 Kudos