cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
bhavanithya
Adventurer
Adventurer
643 Views
Registered: ‎06-04-2019

update_mem failed, Unknown Exception

Jump to solution

Hello all,

I designed a simple BRAM with a Zynq processor.

zynqbram.PNG

Address range for bmg is,

0x00_A000_0000 to 0x00_A03F_FFFF (4M)

Device: zcu111 ultrascale device.

 

data1.mem file,

@A0000000 DE412345

I ran my update mem script and I got the following output,

****** updatemem v2018.3.1 (64-bit)
  **** SW Build 2489853 on Tue Mar 26 04:20:25 MDT 2019
  **** IP Build 2486929 on Tue Mar 26 06:44:21 MDT 2019
    ** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.

source D:/Xilinx/Vivado/2018.3/scripts/updatemem/main.tcl -notrace
Command: update_mem -meminfo ./module1_wrapper1.mmi -data ./data1.mem -proc module1_i/zynq_ultra_ps_e_0 -bit ./Zynq_BRAM1.runs/impl_1/module1_wrapper.bit -out ./download2.bit -force -debug
0 Infos, 0 Warnings, 0 Critical Warnings and 1 Errors encountered.
update_mem failed
Unknown exception
INFO: [Common 17-206] Exiting updatemem at Mon Oct 14 13:57:28 2019...

debug option does not help much. I have no idea why the exception is caused. I attached the mmi file (in xml because it is throwing some error when I upload as mmi file). Please take a look. Any lead is appreciated.

Note: I tried a similar design in Microblaze, the updatemem worked. I wrote the mmi file for my zynq design manually referring the mmi file created for the microblaze design. I also attached the tcl script I used to generate the mmi file

 

 

Thanks,
Bhavanithya Thiraviaraja
-------------------------------------------------------------------------------
Please Kudo or Accept as a solution, if this post helped you.
--------------------------------------------------------------------------------
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
bhavanithya
Adventurer
Adventurer
563 Views
Registered: ‎06-04-2019

Yes it is 4MB which is quite big. I wanted to use DDR but BRAM was more simple for now.

Address range in the address editor is 0x00_A000_0000 to 0x00_A03F_FFFF. And in the mmi file

 <AddressSpace Name="module1_i_zynq_ultra_ps_e_0.module1_i_axi_bram_ctrl_0" Begin="0" End="4194303">

I changed the address in the mem file to @00000000 instead of @A0000000 (taken from the address editor), and now I am able to see the dumped strings... and also the data in the memory @A0000000 in SDK

sdkmemoryzynq.PNG

 

Thanks,
Bhavanithya Thiraviaraja
-------------------------------------------------------------------------------
Please Kudo or Accept as a solution, if this post helped you.
--------------------------------------------------------------------------------

View solution in original post

0 Kudos
3 Replies
bhavanithya
Adventurer
Adventurer
614 Views
Registered: ‎06-04-2019

I added the following lines at the end of the mmi file,

  <DRC>
    <Rule Name="RDADDRCHANGE" Val="false"/>
  </DRC>

as i found this in the sample mmi file provided in Xilinx Confluence page, the updatemem ran successfully but did not show any init_strings and the bit file is the same. What does this mean?

Thanks,
Bhavanithya Thiraviaraja
-------------------------------------------------------------------------------
Please Kudo or Accept as a solution, if this post helped you.
--------------------------------------------------------------------------------
0 Kudos
stephenm
Moderator
Moderator
571 Views
Registered: ‎09-12-2007

Your BRAM looks quite big. What address range did you specify here?

 

0 Kudos
bhavanithya
Adventurer
Adventurer
564 Views
Registered: ‎06-04-2019

Yes it is 4MB which is quite big. I wanted to use DDR but BRAM was more simple for now.

Address range in the address editor is 0x00_A000_0000 to 0x00_A03F_FFFF. And in the mmi file

 <AddressSpace Name="module1_i_zynq_ultra_ps_e_0.module1_i_axi_bram_ctrl_0" Begin="0" End="4194303">

I changed the address in the mem file to @00000000 instead of @A0000000 (taken from the address editor), and now I am able to see the dumped strings... and also the data in the memory @A0000000 in SDK

sdkmemoryzynq.PNG

 

Thanks,
Bhavanithya Thiraviaraja
-------------------------------------------------------------------------------
Please Kudo or Accept as a solution, if this post helped you.
--------------------------------------------------------------------------------

View solution in original post

0 Kudos