为了添加
FPGA图像加密,我修改了我的实现流程,使用bitgen而不是data2mem将ROM数据传入BRAM。
data2mem需要一个标识BRAM位置的.bmm文件。
多年来,我的data2mem方法对许多不同的FPGA系列都运行良好。
bitgen要求在ngdbuild阶段使用不包含LOCA
tiON信息的.bmm文件识别BRAM。
它可能使用.bmm中的'tag'信息注释.ncd。
如果没有注释,则在使用-bd选项调用时,bitgen将失败并显示错误消息。
当我使用带注释的.ncd文件时,生成的.bit文件不包含更新的BRAM信息。
没有错误或警告消息。
我的.mem文件被认为是正确的,因为它们使用data2mem。
有人对此有经验吗?
bitgen是否为此函数使用与data2mem相同的引擎?
有没有办法引出更冗长的bitgen处理来诊断这个失败?
对此棘手问题的任何帮助将不胜感激。
以上来自于谷歌翻译
以下为原文
In an effort to add FPGA image encryption I have modified my implementation flow to impart ROM data into BRAMs using bitgen rather than data2mem.
data2mem requires a .bmm file that identifies the LOCation of the BRAM. My data2mem methodology has worked flawlessly for many different FPGA families for many years.
bitgen requires that the BRAM be identified at the ngdbuild stage with a .bmm file that contains no LOCation information. It presumably annotates the .ncd with the 'tag' information in the .bmm. Without the annotation bitgen fails with error messages when invoked with the -bd option. When I use the annotated .ncd file the resulting .bit file contains no updated BRAM information. There are no error or warning messages.
My .mem files are presumed correct since they work with data2mem.
Does anyone have experience with this?
Does bitgen use the same engine as data2mem for this function?
Is there any way to elicit more verbose bitgen processing so as to diagnose this failure?
Any help on this nettlesome issue would be greatly appreciated.