UltraScale Architecture Memory Resources
ug573-ultrascale-memory-resources
ug573-ultrascale-memory-resources
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 1: Block RAM <strong>Resources</strong><br />
NO_CHANGE Mode<br />
In NO_CHANGE mode, the output latches remain unchanged during a write operation. As<br />
shown in Figure 1-4, data output remains the last read data and is unaffected by a write<br />
operation on the same port. These waveforms correspond to latch mode when the optional<br />
output pipeline register is not used. NO_CHANGE mode is the most power efficient.<br />
X-Ref Target - Figure 1-4<br />
CLK<br />
WE<br />
DIN<br />
XXXX 1111 2222 XXXX<br />
ADDR<br />
aa bb cc dd<br />
DOUT<br />
0000 MEM(aa) MEM(dd)<br />
EN<br />
Disable<br />
Read<br />
Write<br />
MEM(bb)=1111<br />
Write<br />
MEM(cc)=2222<br />
Read<br />
UG573_c1_04_060613<br />
Figure 1-4:<br />
NO_CHANGE Mode Waveforms<br />
Address Collision<br />
An address collision is when both block RAM ports access the same address location in the<br />
same clock cycle.<br />
• When both ports are reading, the operations complete successfully.<br />
• When both ports are writing different data, the memory location is written with<br />
non-deterministic data.<br />
• When one port is writing and the other port is reading:<br />
° The write port always successfully commits the data to memory.<br />
° The read data on write port is always correct (TDP).<br />
° The read port data is deterministic only for common clock designs (both clocks are<br />
driven by the same clock buffer) and the write port is in READ_FIRST mode. Under<br />
all other conditions, the read data on read port is not deterministic.<br />
<strong>UltraScale</strong> <strong>Architecture</strong> <strong>Memory</strong> <strong>Resources</strong> www.xilinx.com<br />
Send Feedback<br />
13<br />
UG573 (v1.2) February 24, 2015