Forum Discussion
Gui vs. Quartus command-line exectuables
When I run a command-line script such as quartus_map and it completes successfully, I would expect that when I open the project in the gui and run the fitter, quartus would detect that map has already completed and would not need to run again. However when doing these steps, quartus is re-running map. Why? Are there any options in the script that need to be used to signal the project that map is complete?
Here are commands I am using with Q15.1 quartus_map --read_settings_files=on --write_settings_files=off <project_name> --64bit quartus_cdb --read_settings_files=off --write_settings_files=off <project_name> --64bit --merge quartus_fit --read_settings_files=off --write_settings_files=off <project_name> --64bit quartus_sta <project_name> --64bit Some other observations: If I run the full compile in the gui, then run the quartus_fit command, the 2nd fit is successful. If I run the 4 commands above, then re-run the quartus_fit command, it is also successful. If I open the project using: quartus_sh -s project_open -revision <revname> <project_name> execute_module -tool fit This is also successful without re-running map. Thanks for all input.3 Replies
- Altera_Forum
Honored Contributor
Not sure of the exact answer and please file an SR, as it seems like a problem that the fitter doesn't detect this. (I'm guessing this flow isn't tested, as command line users tend to stay in command line).
That being said, I am guessing you're running the fitter from the Task Manager on the left. I close this down and never use it, as it tries to be smart and figure out if something needs to be re-run. If you go to Processing -> Start -> Fitter, there are no "smarts" and it runs the fitter, just like if you ran it from a script. If there was a problem with synthesis and the fitter can't be run, you get an error and it says to re-run synthesis, but if you already have it should just work. - Altera_Forum
Honored Contributor
bogus software defect?
- Altera_Forum
Honored Contributor
Probably, but you should have a simple workaround. Like I said, I would be surprised if this flow gets used/tested much, so doubtful others have run into it. Please file a Service Request so it can be fixed.