You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @alanvgreen , @tcal-x ,
I just wanted to know if theres any way in which we can force the synthesis tool to use BRAMs for certain specific cfu storage variables instead of FFs or LUTRAMs. The issue is sometimes I hit an LUT resource usage limiit in 'place' under place & route, since I think all CFU storage is implemented as LUTRAMs. Please let me know about this soon.. This could be helpful for some large designs of mine.
Thanks,
Bala.
The text was updated successfully, but these errors were encountered:
Hi Bala, this is dependent on the synthesis tool. If you're writing the Verilog for the CFU directly, you probably need to add attributes to the declaration of the memory block. Please refer to the users manual for the synthesis tool you are using.
The VexRiscv has added some attributes; I'm not sure if they're supported by ALL tools or just some:
Hi @alanvgreen , @tcal-x ,
I just wanted to know if theres any way in which we can force the synthesis tool to use BRAMs for certain specific cfu storage variables instead of FFs or LUTRAMs. The issue is sometimes I hit an LUT resource usage limiit in 'place' under place & route, since I think all CFU storage is implemented as LUTRAMs.
Please let me know about this soon.. This could be helpful for some large designs of mine.
Thanks,
Bala.
The text was updated successfully, but these errors were encountered: