Part 7 answers: What does the back-end team need from me?
RTL is done when someone else can build a chip from it, not when simulation passes. This part packages mini_controller the way the back-end expects: constraints it can read, a release package that lists what it contains and what is known to be missing.
It stays on the front-end side throughout: what happens inside physical design, sign-off timing and DRC/LVS belongs to the PD, STA and DFT courses, linked from here and never retaught.
What | Detail |
|---|---|
Time | About 1.5 hours. |
You will build | A release folder with a README, a manifest and a constraints file a stranger can rebuild from. |
You are done when | A clean checkout rebuilds from your README alone, and every manifest line reports OK. |
Read an SDC constraints file and say what each block asks the tools to do.
Assemble a release package with RTL, constraints, docs and a version record.
Name what stays front-end and what the PD, STA and DFT courses own.
# | Lesson | What it covers | Level |
|---|---|---|---|
7.1 | The package list and who owns each item. | W | |
7.2 | Four constraint lines, and the slack arithmetic they drive. | W | |
7.3 | README, manifest and the stranger test. | W |
Lessons are in learning order: each one sets up the problem the next one solves. The glossary and the command cheat sheet are open to you throughout; if something fails, go to the troubleshooting table.
This course stays on the front-end start-up path and links out instead of repeating. These lessons build on or continue what this part teaches.