Public

Thread: Metal- and Module Selection for Run3

9 Discord messages from ℹ️ - Information/⁉️-questions/threads/metal-and-module-selection-for-run3.md.

Category: ℹ️ - Information Parent channel: #⁉️-questions Thread ID: 1534999803979632691

Messages: 9

message-1534999803979632691

2026-08-06T19:01:12.186+00:00 — Lukas (@lukas_88179)

Content

Is the exact metal code and module selection for run 3 documented anywhere?

On the Crowd Supply page, I can only find the code `1P5M26ML`, so 5 metal layers, but I can't find any reference to `26ML` anywhere in the PDK.

From my understanding, all of the following modules must be specified for a gf180mcu run to be fully defined:
```
==============================================================================
| Metal Stack | Top Metal | MIM Layer | MIM Cap   | PHRES       | nVt NMOS   |
|=============|===========|===========|===========|=============|============|
| 1P5M        | 6KA       | no MIM    | no MIM    | no PHRES    | no nVtNMOS |
|             | 9KA       | Option A  | 1.5fF/um2 | 1000 ohm/sq | nVtNMOS    |
|             | 11KA      | Option B  | 1.0fF/um2 | 2000 ohm/sq |            |
|             | 30KA      |           | 2fF/um2   | 3000 ohm/sq |            |
==============================================================================
```
Has anyone come across this before or has any information about it?
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/2-ADBB4.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {}
}
</details>

message-1535002786226241636

2026-08-06T19:13:03.209+00:00 — tnt (@246tnt)

Content

26ML just mean it has 26 Mask Layers.
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/88d17af9d19ab43565b0c46751ef7d12-DFEE5.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {}
}
</details>

message-1535003172249014412

2026-08-06T19:14:35.244+00:00 — tnt (@246tnt)

Content

* 11KA
* MiM Option B
* 2 fF/um^2
* 1000 ohm/sq
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/88d17af9d19ab43565b0c46751ef7d12-DFEE5.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {}
}
</details>

message-1535004067732918506

2026-08-06T19:18:08.744+00:00 — Lukas (@lukas_88179)

Content

Thanks! Did you find that somewhere on the wafer.space site?
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/2-ADBB4.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {}
}
</details>

message-1535007129876959442

2026-08-06T19:30:18.816+00:00 — tnt (@246tnt)

Content

No, just from previous discussions here ...

Reactions

<details> <summary>Reactions data</summary>
[
  {
    "count": 1,
    "emoji": {
      "code": "thumbsup",
      "id": "",
      "imageUrl": "2026-08_media/1f44d-27259.svg",
      "isAnimated": false,
      "name": "👍"
    },
    "users": [
      {
        "avatarUrl": "2026-08_media/2-ADBB4.png",
        "color": null,
        "discriminator": "0000",
        "id": "1534980349673738311",
        "isBot": false,
        "name": "lukas_88179",
        "nickname": "Lukas"
      }
    ]
  }
]
</details><details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/88d17af9d19ab43565b0c46751ef7d12-DFEE5.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {}
}
</details>

message-1535352012021964941

2026-08-07T18:20:45.127+00:00 — namibj

Reply/reference

<details> <summary>Reference data</summary>
{
  "channelId": "1534999803979632691",
  "guildId": "1361349522684510449",
  "messageId": "1534999803979632691"
}
</details>

Content

oh, nvt NMOS is allowed as well.

Extraction for thin oxide ones is maybe still not available; but worse, there are no SPICE yet for thin oxide nvt NMOS.
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/f885abc0dddd0a33e4d4991b3c99091d-7ACD2.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {
    "mentions": [
      {
        "avatarUrl": "2026-08_media/2-ADBB4.png",
        "color": null,
        "discriminator": "0000",
        "id": "1534980349673738311",
        "isBot": false,
        "name": "lukas_88179",
        "nickname": "Lukas",
        "roles": []
      }
    ]
  }
}
</details>

message-1535465762494480414

2026-08-08T01:52:45.353+00:00 — Tim 'mithro' Ansell (@mithro_)

Content

There is no thin oxide on GF180MCU, only thick oxide and thicker oxide IIRC
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/9679bb77da48d47c905b398d98a83780-75B68.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {}
}
</details>

message-1535466001200578560

2026-08-08T01:53:42.265+00:00 — namibj

Content

well, yeah, afaik all the gf180 options never offer more than two thicknesses at once, thus if there's even a difference available, there'll be a "thin" and a "thick" with local meaning.
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/f885abc0dddd0a33e4d4991b3c99091d-7ACD2.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {}
}
</details>

message-1535466368936452277

2026-08-08T01:55:09.94+00:00 — Tim 'mithro' Ansell (@mithro_)

Reply/reference

<details> <summary>Reference data</summary>
{
  "channelId": "1534999803979632691",
  "guildId": "1361349522684510449",
  "messageId": "1535466001200578560"
}
</details>

Content

I think you might be right there.
<details> <summary>Other message metadata</summary>
{
  "author": {
    "avatarUrl": "2026-08_media/9679bb77da48d47c905b398d98a83780-75B68.png",
    "discriminator": "0000",
    "isBot": false
  },
  "message": {
    "mentions": [
      {
        "avatarUrl": "2026-08_media/f885abc0dddd0a33e4d4991b3c99091d-7ACD2.png",
        "color": null,
        "discriminator": "0000",
        "id": "262706220073222144",
        "isBot": false,
        "name": "namibj",
        "nickname": "namibj",
        "roles": []
      }
    ]
  }
}
</details>