New Contributor
New ContributorHello and thank you for your response,
I understand that the preloader generation process works best on Linux however I would like to carry out the process on Windows if at all possible. I already have a significant amount of the project set up on Windows and I believe it will be easier for people in my organization to follow my design example on Windows.
Thanks,
Campbell
Regular ContributorHi,
If you insist on using the Windows environment to build, then you might need to use version 19.1/19.3 to compile and build in Windows.
New ContributorI think this issue may extend beyond just the Preloader.
I tried to initialize a second on-chip memory component with a .hex file containing the HPS bare-metal application image. I converted the application-mkimage.bin file (which I confirmed works when booting from the SD card) to a .hex file with the following command in the Embedded Command Shell version 17.0:
$ arm-altera-eabi-objcopy -I binary -O ihex --adjust-vma -0xc0000000 application-mkimage.bin application.hex
When trying to recompile the project so that the preloader.hex and application.hex files are actually synthesized in the FPGA memory, I get the same error as before. When I rename application.hex so that Quartus can't find the memory initialization file, the error goes away.
Note that I was actually able to use the Altera Embedded Command Shell version 17.0 to generate the Preloader and convert it to a .hex file without errors.
I also tried changing the size of the on-chip memory component that contains the application.hex file to be much greater than the size of the file and still got the same error.
I have attached the application.hex file (converted to a text document) for anyone interested. The beginning and the end of the file are similar to the preloader.hex file that I couldn't synthesize in memory (these sections are missing from the preloader.hex file that did work without error)
