cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
685 Views
Registered: ‎02-18-2019

BRAM Compilation Error (Unsupported RAM template / Unable to infer RAMs due to unsupported pattern.)

Jump to solution

Does anyone know how to remove these error messages ?

We have two designs that compile independently in separate projects. However, when we combine the designs into a single project then we get these error messages regarding the BRAM and cannot complete the compilation. Has anyone experienced a similar issue as we believe the code to be correct, and this is a Vivado issue ?

[Synth 8-2914] Unsupported RAM template ["c:/ADSrc/hdl-master/projects/adrv9009/xczu15/adrv9009_xczu15.srcs/sources_1/bd/system/ipshared/5843/SRC/bram_dp2.vhd":90]
[Synth 8-2914] Unsupported RAM template ["c:/ADSrc/hdl-master/projects/adrv9009/xczu15/adrv9009_xczu15.srcs/sources_1/bd/system/ipshared/5843/SRC/bram_dp2.vhd":90]
[Synth 8-5743] Unable to infer RAMs due to unsupported pattern.

Thank you for any insights.

0 Kudos
1 Solution

Accepted Solutions
markcurry
Scholar
Scholar
591 Views
Registered: ‎09-16-2009

Can you share the code lines in question?  At least the declaration and functional model of the RAM?  Without some code, there's not much we can offer to help.

Check the Synthesis Templates for RAMs within UG901.  Follow those guides closely for inferring your RAMs.

Regards,

Mark

View solution in original post

3 Replies
markcurry
Scholar
Scholar
592 Views
Registered: ‎09-16-2009

Can you share the code lines in question?  At least the declaration and functional model of the RAM?  Without some code, there's not much we can offer to help.

Check the Synthesis Templates for RAMs within UG901.  Follow those guides closely for inferring your RAMs.

Regards,

Mark

View solution in original post

anusheel
Moderator
Moderator
541 Views
Registered: ‎07-21-2014

@endurosat_xilinx_dpd 

Do you mean the same memory code without any changes in RTL and memory size fails when used in the bigger project? 

Thanks
Anusheel

0 Kudos
472 Views
Registered: ‎02-18-2019

 Thank you Mark for responding - our FPGA expert was able to solve the problem. He said it was a compiler issue but solved with a coding work around. If I can get his code I will post it as a solution. Thank you again.

0 Kudos