Run Fc Step

Pre-run Checks

1. Verify the prerequisite checkpoint exists (except for init):
   • Check that $PROJECT_PATH/fc/${DESIGN_NAME}.dlib exists
   • The checkpoint block name should be present in the .dlib
2. Backup the .dlib before running (except for init which creates a new one):

   TIMESTAMP=$(date +%Y%m%d_%H%M%S)
   cp -a $PROJECT_PATH/fc/${DESIGN_NAME}.dlib $PROJECT_PATH/fc/backup_${STEP}_${TIMESTAMP}.dlib
   

Execution

cd $PROJECT_PATH/fc && mkdir -p scripts report output temp
cd $PROJECT_PATH/fc/temp && fc_shell -f ../scripts/flows/run_${STEP}.tcl 2>&1 | tee ../report/run_${STEP}.log

For longer steps (synthesis, clocktree, routing), consider using run_in_background: true or the nohup pattern:

cd $PROJECT_PATH/fc/temp && nohup fc_shell -f ../scripts/flows/run_${STEP}.tcl > ../report/run_${STEP}.log 2>&1 &
echo $! > /tmp/.fc_step_pid

Then poll for completion by checking if the process is still running and tailing the log.

Post-run Report Checks

After the step completes, check the appropriate reports:

Report to User

Present the report summary and ask whether to proceed to the next step.

For each step, highlight the critical checks:

• synthesis: Area utilization %, timing slack, any warnings
• clocktree: Setup and hold timing after CTS
• routing: DRC violations, shorts, opens, setup and hold timing
• dfm: DRC = 0, LVS clean, no antenna/short/open/floating violations
• output: Final timing (setup + hold), power, area utilization, DRC/LVS clean

Safety Rules

• NEVER modify RTL files.
• NEVER skip the backup step.
• NEVER delete reports.
• If a step fails, do not proceed to the next step. Report the error and suggest debugging steps.
• Check the run log for Error or FATAL messages.