PD Tool Knowledge
PD tools maintain a design database that combines logical connectivity, physical geometry, timing models, constraints, and analysis results.
Strong tool usage means understanding what a command changes, which analysis view it uses, and how to validate the result.
Before resizing a cell, query its active timing arcs, physical location, fanout, transition, and role in every relevant scenario.
Physical Design flow
Follow each stage in sequence. Every stage produces information needed by the next.
PD Tool Knowledge—visualized
This technical view uses the actual structures and relationships associated with this stage, followed by its key terms.
Understand every concept
Database and views
What it is: Database and views is a core concept within PD Tool Knowledge. It describes the information, structure, or analysis engineers use at this stage of the Physical Design flow.
Why it matters: Understanding it helps you interpret the stage correctly, avoid incorrect assumptions, and connect the result to the next implementation or signoff step.
Where it fits: This topic belongs to module 8, PD Tool Knowledge, and its output supports the stages that follow.
Practical example: Engineer workflow: Learn object queries for cells, pins, nets, clocks, and shapes. Before resizing a cell, query its active timing arcs, physical location, fanout, transition, and role in every relevant scenario.
Reports and commands
What it is: Reports and commands is a core concept within PD Tool Knowledge. It describes the information, structure, or analysis engineers use at this stage of the Physical Design flow.
Why it matters: Understanding it helps you interpret the stage correctly, avoid incorrect assumptions, and connect the result to the next implementation or signoff step.
Where it fits: This topic belongs to module 8, PD Tool Knowledge, and its output supports the stages that follow.
Practical example: Engineer workflow: Read timing, congestion, power, and design-rule reports. Before resizing a cell, query its active timing arcs, physical location, fanout, transition, and role in every relevant scenario.
Flow automation
What it is: Flow automation is a core concept within PD Tool Knowledge. It describes the information, structure, or analysis engineers use at this stage of the Physical Design flow.
Why it matters: Understanding it helps you interpret the stage correctly, avoid incorrect assumptions, and connect the result to the next implementation or signoff step.
Where it fits: This topic belongs to module 8, PD Tool Knowledge, and its output supports the stages that follow.
Practical example: Engineer workflow: Apply controlled changes through reusable scripts. Before resizing a cell, query its active timing arcs, physical location, fanout, transition, and role in every relevant scenario.
Work through it step by step
- 1
Database and views
Learn object queries for cells, pins, nets, clocks, and shapes.
- 2
Reports and commands
Read timing, congestion, power, and design-rule reports.
- 3
Flow automation
Apply controlled changes through reusable scripts.
- 4
Database and views
Save checkpoints and compare quality-of-results after each stage.
Explore each topic
01Database and views
Understand the concept, connect it to the ASIC flow, study the report or behavior it produces, and apply it in a guided exercise. Check the result against the module goal before moving forward.
02Reports and commands
Understand the concept, connect it to the ASIC flow, study the report or behavior it produces, and apply it in a guided exercise. Check the result against the module goal before moving forward.
03Flow automation
Understand the concept, connect it to the ASIC flow, study the report or behavior it produces, and apply it in a guided exercise. Check the result against the module goal before moving forward.
Completion checklist
- ✓ Scripts are repeatable
- ✓ Commands use explicit collections
- ✓ Reports match the active views
- ✓ Checkpoints and logs are preserved
Practise with open-source tools
These are official third-party GitHub projects selected for this learning path.