Handling Quartus executable return codes

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

i see. interestingly the example end to end flow manually runs TAN reports after a full compilation on page 10:

quartus_map myproj | grep -c unsuccessful

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.

Thanks for the replies.

Just a comment, but just because the GUI seems strange, take the time to delve into it some. Lauching compiles makes perfect sense for a script, but the Quartus GUI has a lot of really nice things. Even something that seems good for text like the reports are nice in the GUI. The hierarchical utilization sections have +/- by each hierarchy so you can roll everything up and make it more readable. Going to the Fitter -> Resource Section -> Control SIgnals and being able to sort by hierarchy or Usage and you can find how many clock enables in a particular section, or all the asynchronous clears. Go to the Fitter RAM summary and sort by MLAB usage and find exactly which RAMs use MLABs, which use M9Ks, etc. Cross-probing is huge too. Double-click on an error in synthesis and that HDL file pops up at the line number with the error. Right-click Locate on that signal and you can find it in the Pin Planner to see where it's assigned, or in the Assignment Editor to see if it has any other assignments. Highlight a bunch of failing paths in TimeQuest, right-click Locate to Chip Planner, and you can see them drawn out across the die. There are all sorts of niceties that you would never find going through the text files.

Thanks Rysc.

here's a bash script if you didn't want to use quartus_sh --flow. looking at the exit code of the app was a better idea than grep -c unsuccessful. this one also catches internal errors.

#!/bin/bash
quartus_map myproj
out=$?
if  ; then
  quartus_fit myproj
  out=$?  
fi
if  ; then
  quartus_asm myproj
  out=$?
fi

Hi Witty. I think I have a solution to your task. You can write a Tcl script for the whole process of the compilation step by step and let the "quartus_sh -t xxxx.tcl" command run the script for you. You can use "[catch { } result]" command in the Tcl script file to capture the returned report for every step in the compilation process.