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
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.