Run Fc

Execution

Run from the fc/ directory:

cd $PROJECT_PATH/fc && mkdir -p scripts report output temp

Then launch fc_shell. Since this can take a long time, use background execution:

cd $PROJECT_PATH/fc/temp && nohup fc_shell -f ../scripts/flows/run_full.tcl > ../report/run_fc.log 2>&1 &
echo $! > /tmp/.fc_run_pid
echo "RUNNING" > /tmp/.fc_run_status

Then poll for completion by checking:

1. Whether the process is still running: kill -0 $(cat /tmp/.fc_run_pid) 2>/dev/null
2. Tail the log for progress markers: tail -20 $PROJECT_PATH/fc/report/run_fc.log
3. Look for completion: grep for "Fusion Compiler flow completed" or "Error" in the log

When using the Bash tool, set run_in_background: true if you expect the run to take more than a few minutes. You will be notified when it completes.

For smaller designs where the full flow may complete within 10 minutes, you can run directly:

cd $PROJECT_PATH/fc/temp && fc_shell -f ../scripts/flows/run_full.tcl 2>&1 | tee ../report/run_fc.log

Post-run

After completion, invoke /check-reports all to parse and present all report results.

Safety Rules

• NEVER modify RTL files in hdl/.
• NEVER delete existing report files. If re-running, the new run overwrites reports naturally.
• Always backup the .dlib before a fresh run.
• If the run fails mid-way, check the log for the last successful save_block to determine which checkpoint is valid.