System memory content editor

In order for the memory content editor to work, it needs to read and write to the memory. This means it needs an address port and data in and data out ports. So you can only use this option with single-port RAMs, which I understand can be limiting. If you're dual-port RAM is run off the same clock(or related clocks), you might be able to change it to use one port and time multiplex your address and data(basically running twice as fast and muxing all the control, address and data). If you have extra memory available, putting signaltap into the design is usually easier, since you don't have this limitation(you're just pumping the data into another memory).