001-fuzzer: using only PERFRAMECRC bitstream

We are going to use only PERFRAMECRC bitstream from now on because the
tools cannot create a DEBUGBITSTREAM for the zynq7 devices

Signed-off-by: Alessandro Comodi <acomodi@antmicro.com>
This commit is contained in:
Alessandro Comodi 2018-12-21 09:49:08 +01:00 committed by Karol Gugala
parent bc53d824fa
commit 82c6dad770
2 changed files with 4 additions and 8 deletions

View File

@ -1,5 +1,5 @@
part.yaml: design.debug.bit
${XRAY_TOOLS_DIR}/gen_part_base_yaml $< > $@
part.yaml: design.perframecrc.bit
${XRAY_TOOLS_DIR}/gen_part_base_yaml $< -f > $@
design.bit debug.perframecrc.bit design.debug.bit: ../generate.tcl
design.bit design.perframecrc.bit: ../generate.tcl
vivado -mode batch -source ../generate.tcl

View File

@ -22,13 +22,9 @@ write_checkpoint -force design.dcp
# Write a normal bitstream that will do a singe FDRI write of all the frames.
write_bitstream -force design.bit
# Write a debug bitstream which writes each frame individually followed by
# Write a perframecrc bitstream which writes each frame individually followed by
# the frame address. This shows where there are gaps in the frame address
# space.
set_property BITSTREAM.GENERAL.DEBUGBITSTREAM YES [current_design]
write_bitstream -force design.debug.bit
set_property BITSTREAM.GENERAL.DEBUGBITSTREAM NO [current_design]
set_property BITSTREAM.GENERAL.PERFRAMECRC YES [current_design]
write_bitstream -force design.perframecrc.bit
set_property BITSTREAM.GENERAL.PERFRAMECRC NO [current_design]