Forum Discussion
Altera_Forum
Honored Contributor
11 years ago --- Quote Start --- Hi dsl, I think, that's it. If I check in QSys the "Enable non-default initialization file" check Box and browse to the according location, where I want my hex file to get from, it writes this (windows) path directly into the makefile. If I go to the makefile and change the line # Memory: onchip_rom MEM_1 := C:\Daten\CVS_TPDB\ws_tpdb\sw\ad_tpdb_0300_firmware\mem_init\ad_tpdb_qsys_onchip_rom into # Memory: onchip_rom MEM_1 := ad_tpdb_qsys_onchip_rom it's working. And again, this took me hours of my working time as I rely on the tools. I guess this is a bug and should be fixed because in a certain way i rely on the automazation and interaction of the tools that I'm using (especially if the task has been working in a former Version of the tools without any problems). Do you know, where this bug can be reported? Or where I can find a bug database which maybe already contains this one? Or maybe there is a misunderstanding from my side in the workflow of the tools. If so, can you please tell me what I have to do, so that I don't have to change any automatic generated makefiles? Thanks, Maik --- Quote End --- It really worries me that this is still not corrected (Quartus 14.0), I also lost a lot of time because of this bug. I mean, we are expected to put a path to the .hex file in QSYS and we are using Windows but the path should'nt be windows based? C'mon...