feat(process): add GF180MCU process variant#169
Merged
Conversation
GF180MCU is the GlobalFoundries open-source 180nm MCU PDK, distinct
from the existing c4m-gf180 variant ("gf180"). Both share the
GlobalFoundries 180nm node but use different cell libraries and IO
conventions, served by separate techno plugins on the backend
(techno-c4m-gf180 vs techno-gf180mcu).
- Add Process.GF180MCU = "gf180mcu" alongside GF180.
- Route it through port_for_process to SiliconPlatformPort (same
default as the other non-Sky130 processes).
Clarify the GF180 docstring to flag the variant distinction.
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add `Process.GF180MCU` = `"gf180mcu"` for the GlobalFoundries open-source 180nm MCU PDK, distinct from the existing `"gf180"` (c4m-gf180 variant). Both share the GF 180nm node but use different cell libraries and IO conventions; on the backend side they're served by separate techno plugins (`techno-c4m-gf180` vs `techno-gf180mcu`).
Changes
Why now
chipflow-backend has a techno-gf180mcu plugin coming in shortly. Without this enum entry, designs configured with `process = "gf180mcu"` in their chipflow.toml are rejected by chipflow-lib's pydantic validation before even reaching the backend.
Test plan