Neorv32 only runs blinky application even after making new executable file

[DS-567]

Hi, I have took a break of around 3 months from working with Neorv32 to get other hardware built. Now I have returned to using Neorv32 again and it seems the core will only run the blinky application.

I set up a new project as usual with the top minimal template, basically followed the general hardware setup and let it run the blinky example (default application image) to verify it was working. I then wrote a new C application, ran the makefile which was successful. First strange thing I noticed was the Vivado tools didn't automatically update the source files when the makefile was ran from Ubuntu. And when the bitstream was downloaded to the FPGA, it continued to run the blink application. I have noticed the application_image.vhd file has not been updated in Vivado but has been changed in my neorv32-main file structure, hence why it is running the blinky.

Has something changed with how executables are installed directly into IMEM or am I forgetting/doing some thing wrong?

Any suggestions?

[stnolting]

Hey @DS-567!

I think this is a Vivado issue... Can you open the IMEM image file in Vivado and check the header to see if the file was actually updated by the makefile?

How did you create the Vivado project? Do you reference the source files or are they copied into the project?

See here (this box should NOT be checked): https://digilent.com/reference/_media/vivado/getting_started/import_sources.png

[DS-567]

Thanks Stephan, that was the problem indeed! I had the copy sources into project option checked.

Thanks for your time and help :)