Formats and contracts

Formats and contracts

• The .chiplet assembly file
  • What the format is for
  • File structure
  • The assembly block
  • The technologies block
  • The connection_stacks block
  • Paths and the ${VAR} convention
  • Validation rules
  • Reading and writing .chiplet files
  • Where to go next
• Components and optional blocks
  • The components block
  • Optional blocks
  • A complete example
  • Where to go next
• Coordinate frames
  • The rules in brief
  • The canonical frame
  • Position semantics
  • The anchor convention
  • Orientation and flip-chip mirroring
  • From a die-local coordinate to an assembly coordinate
  • The z-mounting rule
  • io_pads
  • The leak guard
  • The writer contract
  • The reader contract
  • Verification fixtures
  • Appendix: glossary of coordinate frames
  • Where to go next
• Boundary manifest
  • File location and auto-discovery
  • Producers and consumers
  • Schema
  • No z coordinate: single tier by design
  • Version policy
  • Why the boundary left the fabrication layer namespace
  • Example
• Pillar manifest
  • File location
  • Producers and consumers
  • Schema
  • Frame and semantics
  • Version policy
  • Example
  • Using it
• Interconnect methods manifest
  • File location
  • Schema
  • Example
  • How the exporter derives the file
  • One interconnect PDK, many methods
  • What the deck does with it
  • Version policy
• Pin lists
  • Shape
  • How pin lists are produced
  • What the ADK consumers read
• 3Dblox interoperability
  • What 3Dblox is
  • The shared core
  • Forward mapping, .chiplet to 3Dblox
  • What does not map, and why
  • Conventions that a naive converter gets wrong
  • The reverse direction
  • The 3dblox_ref proposed extension
  • One assembly, one authoritative placement source
  • The exporter in the ADK