2. Support
  3. AR# 32127: LogiCORE IP Video Scaler v3.0 - Why do I get X_ARAMB36 Block RAM memory collisions when simulating the Video Scaler?

AR# 32127

|

LogiCORE IP Video Scaler v3.0 - Why do I get X_ARAMB36 Block RAM memory collisions when simulating the Video Scaler?

Description

Why do I get X_ARAMB36 Block RAM memory collisions when simulating the Video Scaler v1.0, v2.1, and v3.0?

Solution

At startup and whenever the read and write pointers for the line buffers are reset during the simulation of the Video Scaler, the following Memory Collision Errors are generated:

# Memory Collision Error on X_ARAMB36_INTERNAL :
video_scaler_wrap_tb.video_scaler_wrap_u.video_scaler_wrap_core_u.coef_ram_gen_bram_coefs.scaler1.
\Scaler_RTI_inst/Scaler_wrap0_inst/Scaler_wrap0_core_u/scaler_top_inst/Inst_scaler_v1/GenerateVariableCoefRAMs.
CoefMem/Mram_mem1 .INT_RAMB.chk_for_col_msg at simulation time 17428.500 ns.



These Memory Collision Errors from the Video Scaler can be safely ignored.
 
The reason they occur is that the read and write pointers of internal Block RAM memory are reset to zero when the line is being written to memory.
 
The core waits to read data, then after a line is written and the core does not use the data the Memory Collision Errors occur.

See (Xilinx Answer 31958) for a detailed list of LogiCORE IP Video Scaler Release Notes and Known Issues.

Linked Answer Records

Master Answer Records

Answer Number Answer Title Version Found Version Resolved
31958 LogiCORE IP Video Scaler - Release Notes and Known Issues N/A N/A

Associated Answer Records

Answer Number Answer Title Version Found Version Resolved
31958 LogiCORE IP Video Scaler - Release Notes and Known Issues N/A N/A
AR# 32127
Date 08/05/2014
Status Archive
Type General Article
IP
People Also Viewed