The assembly flow¶ The assembly flow Overview What goes in and what comes out The flow at a glance The stages The pivot artefact: .chiplet The shared layer source of truth: .lyp What the assembly checks actually check Project layout Where to go next From die GDS to KiCad What you are producing Step 1: look at the GDS before converting it Step 2: say where the pads are Step 3: curate the pads Step 4: generate the footprint Step 5: generate the symbol A die with no GDS Interposer I/O pads Traceability properties Checking the result Next Designing the interposer Before you start Start from the template board Draw the outline Project text variables Register the project libraries Draw the schematic Place the dies Place the I/O pads Route Check while you design What is not checked here Next Exporting the assembly Running the export What happens when you press Run Headless The output tree File by file Deliverables and intermediates Checking the export Common failures Next Generating the assembly GDS What the converter consumes What it produces Running it From KiCad routing to fabrication geometry Cu pillars and bumps Flip-chip placement Sidecars written alongside the GDS After the conversion Verification stages Stage 1: KiCad design-time rules Stage 2: the 3Dblox export and check_3dblox Stage 3: the KLayout assembly DRC Stage 4: the pad-to-pillar alignment check Producer-side checks Where each stage sits in the flow What none of these stages cover Viewing and inspecting Opening the assembly in Chiplet Studio Opening the GDS in KLayout with named layers Walking DRC violations in the Marker Browser Viewing chiplet boundaries Related pages Reference design What the demo assembles Directory tree What each file is Walking the flow What the committed reports say Reproducibility What the demo demonstrates What it does not demonstrate Starting your own design