09-11-2017 12:31 PM
I was using Vivado 2015 version. In that the software was working fine.
Recently upgraded to Vivado 2017.2 version and it is having an evaluation license for 1 month.
I am using Microblaze processor along with 4 AXI Quad SPIs and few GPIOs.
In this the changes made in the .c file of the SDK is not reflected.
New .elf file is generated and I am able to associate it with .bit and the bitsream is also getting generated but still it is taking some old elf file and because of that whatever changes I do in .c file are not getting reflected at the output.
I created new project and tried. In that also same thing is happening. Whatever code I write in .c file has no output.
09-12-2017 12:54 AM
This issue is probably not in the .elf file but in the Hardware Platform. There is a known issue in SDK 2017.2. See AR#69489
Hope that helps,
05-25-2018 05:06 AM
Was this fixed in a later version? I saw in another forum post that apparently it is necessary to rerun implementation for Vivado to read the new elf file.
In both this thread and the link above, a workaround was suggested, but I haven't heard if Vivado was fixed. Does a newer version have a fixed version of write_bitstream that loads the new elf into the BRAM INIT strings?