Every integration failure in this course is, underneath, an ownership failure: a signal nobody owned, a table two teams both edited, a handoff accepted on trust. This topic draws the lines before any of that can happen. It names what the integrator owns that nobody else does, what a block handoff must contain before it is accepted, and who plays each part on NanoSoC, so that every later lesson can say who fixes the bug it describes.
Lesson | After it you can... |
|---|---|
Say what the integrator owns versus the block owner, architect, verification, PD and software. | |
Demand the full collateral list and run the acceptance check before wiring a block in. | |
Route any NanoSoC symptom to its owner and prove the wiring table with a checker. |
Suggested order: top to bottom. Ownership first, because the handoff checklist is meaningless until you know who signs it; then the handoff; then the cast, which turns both into names on NanoSoC. The contracts topic next door (Contracts and Ownership) gives each handoff item its owner in a table.
Physical design and synthesis are blocked, and the block owner fixes it: constraints are handoff collateral. The integrator's part is to refuse the handoff, not to write the file.