<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Module 1: The Physical Design Landscape on Circuit Quest</title>
    <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/</link>
    <description>Recent content in Module 1: The Physical Design Landscape on Circuit Quest</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://circuit.quest/courses/rtl-to-gds-openlane/module-01/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From RTL to Silicon</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-01-flow-overview/01-from-rtl-to-silicon/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-01-flow-overview/01-from-rtl-to-silicon/</guid>
      <description>A design that passes every testbench is a description of correct behaviour, not a chip. This article draws the line between front-end verification and everything physical design still has to do.</description>
    </item>
    <item>
      <title>The Abstraction Stack</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-01-flow-overview/02-the-abstraction-stack/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-01-flow-overview/02-the-abstraction-stack/</guid>
      <description>The same design is described five different ways on its way to silicon: RTL, gates, placed and routed layout, mask polygons, transistors. Each layer exists to answer a question the others cannot.</description>
    </item>
    <item>
      <title>Why Physical Design Is Not Optional</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-01-flow-overview/03-why-physical-design-is-not-optional/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-01-flow-overview/03-why-physical-design-is-not-optional/</guid>
      <description>Timing closure, area, power and yield are not RTL-level concerns. They are where a functionally perfect design goes to fail, and this course exists to prevent that.</description>
    </item>
    <item>
      <title>Yosys and OpenROAD</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-02-open-source-eda-stack/01-yosys-and-openroad/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-02-open-source-eda-stack/01-yosys-and-openroad/</guid>
      <description>Yosys turns RTL into gates; OpenROAD turns gates into a routed, timed layout. Together they are the computational core the course runs on, and both are open source.</description>
    </item>
    <item>
      <title>Magic, Netgen and KLayout</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-02-open-source-eda-stack/02-magic-netgen-and-klayout/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-02-open-source-eda-stack/02-magic-netgen-and-klayout/</guid>
      <description>Magic edits and checks layout, Netgen confirms the layout matches the netlist, and KLayout independently verifies both. Their overlap is a signoff discipline, not redundancy.</description>
    </item>
    <item>
      <title>OpenLane as Orchestrator</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-02-open-source-eda-stack/03-openlane-as-orchestrator/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-02-open-source-eda-stack/03-openlane-as-orchestrator/</guid>
      <description>OpenLane does no physical design step itself. It is the scripted glue that runs Yosys, OpenROAD, Magic, Netgen and KLayout in the right order with the right files handed between them.</description>
    </item>
    <item>
      <title>What a PDK Contains</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-03-sky130-pdk/01-what-a-pdk-contains/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-03-sky130-pdk/01-what-a-pdk-contains/</guid>
      <description>A PDK is a fab&amp;rsquo;s own description of what its process can build and how to describe a design targeting it: SPICE models, multi-view standard cell libraries, and DRC and LVS rule decks, in one package.</description>
    </item>
    <item>
      <title>SKY130, Concretely</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-03-sky130-pdk/02-sky130-process-specifics/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-03-sky130-pdk/02-sky130-process-specifics/</guid>
      <description>SKY130 is a real, fabricable, mixed-signal 130 nm process with an open rule deck: a genuine node, not a toy, which is what makes it a realistic teaching target.</description>
    </item>
    <item>
      <title>Standard Cell Library Variants</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-03-sky130-pdk/03-standard-cell-library-variants/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-03-sky130-pdk/03-standard-cell-library-variants/</guid>
      <description>SKY130 ships the same logical cell set laid out and characterised several ways, hd, hs, ls and more, each a different area, speed and power trade, selected with one config line.</description>
    </item>
    <item>
      <title>Installing OpenLane and the SKY130 PDK</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-04-environment-setup/01-installing-openlane-and-the-pdk/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-04-environment-setup/01-installing-openlane-and-the-pdk/</guid>
      <description>A hands-on install of OpenLane through Docker and the SKY130 PDK through Volare, pinned to a known version, and why that pin is not optional.</description>
    </item>
    <item>
      <title>The OpenLane Directory Structure</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-04-environment-setup/02-the-openlane-directory-structure/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-04-environment-setup/02-the-openlane-directory-structure/</guid>
      <description>A tour of the OpenLane directory tree, where designs live, where the PDK is, and where run outputs land, ending with a first design folder built by hand.</description>
    </item>
    <item>
      <title>Running a First Design End to End</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-04-environment-setup/03-running-your-first-design-end-to-end/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-04-environment-setup/03-running-your-first-design-end-to-end/</guid>
      <description>The payoff: run a small counter through the complete, unmodified OpenLane flow with one command, watch every stage go by, and find the GDSII waiting at the end.</description>
    </item>
    <item>
      <title>config.json, Field by Field</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-05-flow-configuration/01-anatomy-of-a-design-config/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-05-flow-configuration/01-anatomy-of-a-design-config/</guid>
      <description>A field-by-field walk through a real config.json for the Module 1 counter: what each field does now, and which module teaches you to tune the ones that matter.</description>
    </item>
    <item>
      <title>The Flow, Stage by Stage</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-05-flow-configuration/02-the-ordered-flow-stages/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-05-flow-configuration/02-the-ordered-flow-stages/</guid>
      <description>The complete ordered list of every stage OpenLane runs, one sentence each, mapped to the module that teaches it in depth: the reference map for the rest of the course.</description>
    </item>
    <item>
      <title>Interactive Versus Autonomous Execution</title>
      <link>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-05-flow-configuration/03-interactive-vs-autonomous-flow-execution/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://circuit.quest/courses/rtl-to-gds-openlane/module-01/01-05-flow-configuration/03-interactive-vs-autonomous-flow-execution/</guid>
      <description>OpenLane&amp;rsquo;s interactive Tcl mode runs one stage at a time and lets you inspect real inputs and outputs between steps. It is the mode this course uses from Module 2 on, and here is why.</description>
    </item>
  </channel>
</rss>
