First post... I'm very new to Quartus and the FPGA world so be gentle. I've written a script to perform each step of the build step by step using the executables... quartus_map -blabla quartus_fit -blabla quartus_asm -blabla quartus_sta -t atclscript.tcl What I need to put between the executables is a touch of code to look at the return codes and exit the rest of the script if necessary. Any suggestions gretfully received. Witty.

just wondering if you have tried quartus_sh --flow instead of running each individual binary.

--- Quote Start --- just wondering if you have tried quartus_sh --flow instead of running each individual binary. --- Quote End --- Yes I had considered using quartus_sh --flow but I thought I may have more control by executing them individually with the potential of passing a unique tcl script to each one. For instance I'm running quartus_sta with a unique tcl file that produces our custom timing reports. I thought this was the way to go. Thanks.

i see. interestingly the example end to end flow manually runs TAN reports after a full compilation on page 10: http://www.altera.com/literature/hb/qts/qts_qii52002.pdf how about something like: quartus_map myproj | grep -c unsuccessfulthe count of unsuccessful will be 0 if you can continue to the next stage and > 0 if not. not sure if internal errors will trigger "unsuccessful", i'll check.

Note that in Assignments -> Settings -> TimeQuest you can manually add a .tcl file to be run as part of the TimeQuest step for compilation. There are also pre-flow Tcl scripts that can be run as part of any step. In general, these have been enough that I've never needed anything else outside of the commands to do what I want.

now there's the proper solution.

Handling Quartus executable return codes | Altera Community

12 Replies

Altera_Forum
Honored Contributor
16 years ago
The principle is it is hard to get return codes from the command-line-executable commands, but it is easy to get return codes from the Quartus-extented-Tcl commands.
So handle the return codes in the Tcl domain, like conditional jumpings and writing to a report file.

If you are working under Windows, Use Tcl, do Not use the command line.
If you are working under Linux, both will do.
Altera_Forum
Honored Contributor
16 years ago
--- Quote Start ---
The principle is it is hard to get return codes from the command-line-executable commands, but it is easy to get return codes from the Quartus-extented-Tcl commands.
So handle the return codes in the Tcl domain, like conditional jumpings and writing to a report file.

If you are working under Windows, Use Tcl, do Not use the command line.
If you are working under Linux, both will do.
--- Quote End ---

Riple,
After a lot of messing I've now gone fully over to quartus_sh using tcl scripts as you advise and wish I'd started that method when I first started with Quartus. Cheers.

Forum Discussion

Handling Quartus executable return codes

12 Replies

Recent Discussions

timing violation fix

Quartus Prime Lite 25.1 License Error - "Unable to checkout a license" (SALT_LICENSE_SERVER)

Quartus Prime Pro 26.1 - Where to find Documentation of new Signaltap features

Error (292014): Can't find valid feature line for core SLL_CA_HBC_T001_Hyperbus_Memory_Controller_10

Agilex 5 – Critical HSSI Error in JESD204B Example Design