Occasional Contributor
Occasional ContributorI havent found any way for Ashling IDE to give me a reliable error free build, even using 24.1.1 "import niosv cmake project"
The only method that work consistently error free is by using niosv-shell with:-
> cmake -S ./sw/app_hal -G "Unix Makefiles" -B sw/app_hal/build
> make -C sw/app_hal/build
Nios2 was never this troublesome.The same software and the same hardware worked just fine, but there I was using Quartus 18, not Quartus 23.1.1.
Maybe I will try Nios2 with Quartus 23.1.1 tomorrow to see what happens
If you can get a NiosV Hello working on a MAX10 development board on Windows 10 with WSL V1 , I would love to know.
Occasional ContributorNios2 with the same design works ok on Quartus 23.1.1.
Occasional ContributorFinally I have something that almost works.
Use Ashling IDE 24.1.1 "import niosv cmake project" and build project.
Downloading the elf file works either with Asling IDE 'Run as' or NiosV command shell niosv-download!
It doesnt run from External Flash though I do know
elf2flash and
riscv32-unknown-elf-objcopy
both commands work because I verified them with a nios2 elf
I also get it working using internal flash for code storage and alt_load for writable sections.
So that just leaves the "niosv_g_bootloader.srec" which replaced Nios2 "boot_loader_cfi.srec".
Can we be certain "niosv_g_bootloader.srec" works with Generic QSPI??
Occasional ContributorGreat! - I confirmed "niosv_g_bootloader.srec" works just fine when using UFM internal flash to store software.
It doesnt work when using Generic QSPI.
Interestingly I notice that Nios 2 had a number of bootloaders . I used the one for CFI flash.
NiosV only has one for each version.Its not clear whether any of them support QSPI.
This is my last problem. Give me an answer to this and I can close this issue!
