![]() ![]() However, if I now try to use quartus_cdb -update_mif, it always tells me, that it does not find the onchip rom hex file and tells me thta it cannot locate the path. In the end, the project compiles without error in the end. Of course, I have to adjust some paths in order to get from the Linux file system to the Windows file system. ![]() So I went back to the Windows Quartus 11.1, and opened the project. However, for productive usage, I need a correct onchip rom initialisation file so that the Nios starts without me downloading the elf file. Once I downloaded the elf file from which I converted the hex file for rom initialization, the processor started and worked fine. The Nios processor just did not start to run ciorrectly. It worked quiet well, except the fact that my onchip_rom initilisation somehow didn't worked. I took a project, that I initially developed with Quartus 11.1 under Windows, and opened it under Quartus 11.1 under Linux. ![]() Recently, I tried to use Qusrtus under Linux. I used to update my NIOS2 onchip rom (containing the Nios program) via the quartus_cdb -update_mif + quartus_asm procedure. ![]() The question I have is the following: Where is quartus_cdb -update_mif getting the information from, where the memory initialisation files are located and is there a way to set/overwrite this location?įor the ones who are interested, why this question arises, read on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |