UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 60206

2014.1 Vivado - Removing ELF File after Implementation still populates the bitstream with the removed ELF File contents

Description

In my design, I associate an ELF File to my project, then run Implementation. 

After Implementation completes, I remove the ELF files from the project and then run write_bitstream.

After downloading the Bitstream on the FPGA, I see that the previously associated ELF File data is included in the bitstream.

The bitstream report also reports the association of the file.

I get the following message when I run write_bitstream after removing the ELF files from the Design Sources.

INFO: [Memdata 28-144] Successfully populated the BRAM INIT strings from the following elf files: ../hi.elf

Solution

This Behavior is incorrect since the write_bitstream operation should take the default bootloop file if no elf files are associated.

The Work around is to re-run Implementation after removing the ELF File. 

Associating a different ELF File also works during write_bitstream.

However, the default Bootloop association does not take place during write_bitstream in this case.

 

This issue is fixed in Vivado version 2014.2.

Linked Answer Records

Associated Answer Records

Answer Number Answer Title Version Found Version Resolved
60246 2014.1 Vivado - Synthesis and Implementation go out-of-date during ELF file Association N/A N/A
AR# 60206
Date Created 04/08/2014
Last Updated 06/20/2014
Status Active
Type Known Issues
Tools
  • Vivado Design Suite - 2013.4
  • Vivado Design Suite - 2014.1