09-04-2018 11:03 AM
I have been reading various support replies related to updating block RAM, but am getting bogged down in what is for ISE only, and what will work in Vivado (I am using Vivado). I have a custom soft processor (not Microblaze) and am using readmemh in Verilog to load a .coe file that I build manually. All is working, but I must resynthesize the design each time I want to update the firmware. I have read through documentation for DATA2MEM, but as I see no reference to Vivado (only ISE). I have also seen a reference to a utility named 'updatemem'. I'm curious if someone has been down this path and can make a suggestion which direction I should continue my research.
09-07-2018 12:14 PM
With more research, it appears that in Vivado I would likely want to use the 'WRITEMEM' command. This command requires a .MMI file that specifies the BRAM location. Unfortunately, Vivado only puts BRAM information into the .MMI file for BRAM that is instantiated using the block diagram. My soft processor's RAM is an inferred RAM, and it does not appear in the auto-generated .MMI file.
Though the .MMI file is XML, it could be hand-build / modified. However, as Vivado is implementing my 16-bit wide x 32K program memory as sixteen 1-bit arrays, hand-writing the XML for manually creating a .MMI file is very cumbersome and error prone.
Has anyone been down this path, and perhaps found a simpler way to update BRAM for a custom soft processor post-synthesis?
09-12-2018 07:25 AM
Still stuck on this one... it seems that I need to use the TCL command 'UPDATEMEM' to merge my memory initialization file with a previously generated bitstream. However, for that I need a .MMI file that describes my memory block. As the memory block I need to update is instantiated in HDL (and not the IP Integrator Block Diagram Editor) it is not being automatically included in the system-generated .MMI file. I understand that I can use the TCL command 'WRITE_MMI' to specify a RAM (BRAM) to include in a .MMI, however for that I need the name of the BRAM. The WRITE_MMI example uses the BRAM name that is within a single block; my RAM is instantiated using 16 BRAMS (each one bit wide) by synthesis, so I am unsure how to format the 'WRITE_MMI' command using the name/location of all 16 BRAM blocks that make up my RAM. Any advice?
09-14-2018 02:51 PM