wafer.space Community - announcements

@everyone - If you are participating in the GF180MCU Run #1 shuttle, please make sure you have created your project on both https://test-platform.wafer.space (and the soon to exist https://platform.wafer.space) with identical project name ASAP! Doing so will allow me to transfer files & precheck runs between the two systems and potentially allow up to 6 precheck runs happen in parallel. If you are expecting a free slot, please make sure your project exists and I have your email address so I can cross check the final slot count and usage.

Welcome to wafer.space …

Platform for wafer.space low cost silicon manufacturing.

16

@everyone - If you are participating in the GF180MCU Run #1 shuttle you should have gotten an email about being added to a Google Group (either an invite or a directly added). This email group will get updates about the progress of the shuttle and other important information. If you have not received the email and you think you are part of the shuttle, please reach out ASAP!

9

3

Tim 'mithro' Ansell

@everyone - If you are participating in the GF180MCU Run #1 shuttle you should have gotten an email about being added to a Google Group (either an invite or a directly added). This email group will get updates about the progress of the shuttle and other important information. If you have not received the email and you think you are part of the shuttle, please reach out ASAP!

Could you please send a test email through the group - that would help to setup mailbox filters.

ReJ aka Renaldas Zioma

Could you please send a test email through the group - that would help to setup mailbox filters.

There will be a real email in the next few hours. I'll put the notification here too.

1

@everyone - People on the mailing list should have just received an email title "Late changing updates -- Initial GDS is still due today, final GDS TBD -- wafer.space GF180MCU Run #1" which explains the following:

Earlier today we got feedback from GF that a number of DRC errors types we were planning to waive can not be waived. Leo (@Leo Moser (mole99)) is currently hard at work updating both the template and precheck to fix these issues. The first set of DRC error fixes require changes to the seal ring and I/O pads generated by the template and Librelane. As these are part of the user design, everyone will need to pull the latest version and update their design. The precheck will be updated to verify these errors have been corrected in your submitted design. All designs will also need to be 100% antenna DRC clean. The precheck is being updated to include these antenna checks. The template's LibreLane and OpenROAD tooling should already be fixing antenna issues and producing DRC clean results. Lastly, the final DRC error fixes require changes to the fill generation. We hope that we are able to accommodate these changes and still meet density targets in all designs. As these are again part of the user design, everyone will need to pull the latest version of the fill generation and update their design. The precheck will again be updated to verify the fixed fill has been generated in your submitted design. I'm requesting everyone create their project on https://platform.wafer.space website and upload at least an initial GDS before the upcoming deadline. As we do not yet know the amount of impact from the updates nor the effect delays will have on our planned timeline with GF, I am not yet setting a new deadline for the final GDS but it is likely to be sometime next week.

Welcome to wafer.space …

Platform for wafer.space low cost silicon manufacturing.

7

ReJ aka Renaldas Zioma

Could you please send a test email through the group - that would help to setup mailbox filters.

You should have an email now

4

@Tim 'mithro' Ansell @Leo Moser (mole99) has the “fixed” version of the project template been released yet?

asc

@Tim 'mithro' Ansell @Leo Moser (mole99) has the “fixed” version of the project template been released yet?

No, I'm working on the issues. It will probably take until next week.

3

Leo Moser (mole99)

No, I'm working on the issues. It will probably take until next week.

Just to clarify, does that mean deadline is not tomorrow?

18:02

Or deadline tomorrow, but we update our designs (final time) once the new template arrives

18:03

Sorry for asking dumb question, but I am not sure how to interpret the email

The final GDS-in deadline will be at a later date (TBA). The deadline to create a project on the platform and submit an initial GDS remains 3 December AoE. You will be required to update your GDS with the changes I'm currently working on.

2

18:05

I hope that clears things up :)

Thanks for clarfication!

@Leo Moser (mole99) Is there an antenna rule DRC checker? Our GDS is analog circuitry, so it's highly likely to have antenna rule violations. Therefore, we want to check it as soon as possible.

Noritsuna Imamura

@Leo Moser (mole99) Is there an antenna rule DRC checker? Our GDS is analog circuitry, so it's highly likely to have antenna rule violations. Therefore, we want to check it as soon as possible.

Yes, there is a KLayout antenna check: https://github.com/wafer-space/gf180mcu/blob/main/gf180mcuD/libs.tech/klayout/tech/drc/rule_decks/antenna.drc Make sure to enable deep mode for the best performance. I will integrate this script into the precheck.

2

1

Leo Moser (mole99)

Yes, there is a KLayout antenna check: https://github.com/wafer-space/gf180mcu/blob/main/gf180mcuD/libs.tech/klayout/tech/drc/rule_decks/antenna.drc Make sure to enable deep mode for the best performance. I will integrate this script into the precheck.

The antenna check gets run with the GUI DRC check automatically, but the results are stored in a different file adjacent to the one displayed in the DRC viewer, you can also open it from there. For speed, I run the drc from the python script klayout/tech/drc/run_drc.py, as it it supports running checks in parallel

@Leo Moser (mole99) @Tim 'mithro' Ansell Update/Questions from the MOSbiusV3 team: Yesterday we submitted a GDS to the test-platform and platform. It was able to download the GDS but it looks like the tests did not run since it did not find a top cell. As you know we are doing a full custom design (many thanks to Leo for helping Andrew @asc with the padframe); is there a convention we should follow for the top cell naming, for the GDS file, for anything else? I also noticed the platform website offers a Project ID and Manufacturing ID; do they need to be put on the chip. There is a QR code in the lower right corner. Right now it reads 0000 so I am guessing it is a place holder. Should we change it? How? I just uploaded our first version to meet the deadline. The toplevel cell is called chip_top. We will be making more changes in the next few days but this GDS has everything + filling so it should pass the large majority of the DRC checks without errors. Fingers crossed. Thanks, -- Peter Kinget

peterkinget

@Leo Moser (mole99) @Tim 'mithro' Ansell Update/Questions from the MOSbiusV3 team: Yesterday we submitted a GDS to the test-platform and platform. It was able to download the GDS but it looks like the tests did not run since it did not find a top cell. As you know we are doing a full custom design (many thanks to Leo for helping Andrew @asc with the padframe); is there a convention we should follow for the top cell naming, for the GDS file, for anything else? I also noticed the platform website offers a Project ID and Manufacturing ID; do they need to be put on the chip. There is a QR code in the lower right corner. Right now it reads 0000 so I am guessing it is a place holder. Should we change it? How? I just uploaded our first version to meet the deadline. The toplevel cell is called chip_top. We will be making more changes in the next few days but this GDS has everything + filling so it should pass the large majority of the DRC checks without errors. Fingers crossed. Thanks, -- Peter Kinget

@peterkinget - I saw the checks, the "top" cell the system found has a weird name like $$$CONTEXT_INFO$$$?

05:20

The precheck will replace the QR Code marker object with the real QRCode

2

Tim 'mithro' Ansell

@peterkinget - I saw the checks, the "top" cell the system found has a weird name like $$$CONTEXT_INFO$$$?

Let's see what happens with the file we just uploaded and take it from there.

@peterkinget - It seems to have detected the top cell as chip_top for that.

1

05:22

Hopefully there will be a precheck run available for you when you wake up tomorrow

Nice

peterkinget

@Leo Moser (mole99) @Tim 'mithro' Ansell Update/Questions from the MOSbiusV3 team: Yesterday we submitted a GDS to the test-platform and platform. It was able to download the GDS but it looks like the tests did not run since it did not find a top cell. As you know we are doing a full custom design (many thanks to Leo for helping Andrew @asc with the padframe); is there a convention we should follow for the top cell naming, for the GDS file, for anything else? I also noticed the platform website offers a Project ID and Manufacturing ID; do they need to be put on the chip. There is a QR code in the lower right corner. Right now it reads 0000 so I am guessing it is a place holder. Should we change it? How? I just uploaded our first version to meet the deadline. The toplevel cell is called chip_top. We will be making more changes in the next few days but this GDS has everything + filling so it should pass the large majority of the DRC checks without errors. Fingers crossed. Thanks, -- Peter Kinget

$$$CONTEXT_INFO$$$ is used by KLayout to store PCell information. See this discussion for more: https://www.klayout.de/forum/discussion/1060/compliance-check-export-stream Please save the final layout without PCell information.

Compliance check export stream

We just overcome an issue about a user error causing an issue to open the exported gds in another GDS tool.

Leo Moser (mole99)

$$$CONTEXT_INFO$$$ is used by KLayout to store PCell information. See this discussion for more: https://www.klayout.de/forum/discussion/1060/compliance-check-export-stream Please save the final layout without PCell information.

It looks like they must have done that with the final layout as that name is gone now.

Yes, we saved without the Pcell information for the latest submission.

Leo Moser (mole99)

Yes, there is a KLayout antenna check: https://github.com/wafer-space/gf180mcu/blob/main/gf180mcuD/libs.tech/klayout/tech/drc/rule_decks/antenna.drc Make sure to enable deep mode for the best performance. I will integrate this script into the precheck.

does the updated precheck enable deep mode for the newly-added antenna checks, or is that still disabled by default? How does one enable it?

BreakingTaps

does the updated precheck enable deep mode for the newly-added antenna checks, or is that still disabled by default? How does one enable it?

Yes it does. But make sure to use version 1.4.0 at least, and update the PDK.

rad, thanks! and cheers for all the hard work behind the scenes to make everything work, and answering all our questions here ❤️

2

Thanks, I appreciate it

Can't wait to see all of the cool designs!

2

Short question, do we have a new gds-in deadline for the updated designs, yet (with new pdk and template)? Don't mean to hurry, just checking if I missed something.

Thorben

Short question, do we have a new gds-in deadline for the updated designs, yet (with new pdk and template)? Don't mean to hurry, just checking if I missed something.

There will be an announcement later day or early tomorrow. Just waiting for @Leo Moser (mole99) to finish updating a few things.

2

Clean GDS deadline now - 17th Dec @ 11:59pm AoE First, thank you all for being patient with us while we work through these initial teething problems! The new deadline for DRC clean GDS is 17th Dec @ 11:59pm AoE. Your GDS must be uploaded and have passed the precheck before this deadline. Given the upcoming end of year holidays, we don't expect the deadline to be extended again. @Leo Moser (mole99) has made what are hopefully the last changes needed to both the gf180mcu-project-template and the gf180mcu-precheck. Please make sure you are using the latest versions of both of these resources and see the latest pinned comments in Discord in #project-template channel. To help everyone meet the deadline, platform.wafer.space is being updated with a bunch of new ultra fast runners (Intel Core Ultra 7 265 Arrow Lake), allowing at least 14 prechecks to run at once. We will continue to monitor discord and try to help @everyone as much as possible! (edited)

Event Time Announcer - wafer.space GF180MCU Run #1 - Clean GDS Subm...

Event Time Announcer shows time for wafer.space GF180MCU Run #1 - Clean GDS Submission Deadline in locations all over the world. In UTC it happens on Wednesday, December 17, 2025 at 11:59:00 pm.

5

4

2

1

Tim 'mithro' Ansell pinned a message to this channel. 12/10/2025 12:28

@everyone - https://platform.wafer.space is going down for ~1 hour (but hopefully less) while I upgrade it to the latest code. I'll restart any currently running checks after the update.

Welcome to wafer.space …

Platform for wafer.space low cost silicon manufacturing.

Tim 'mithro' Ansell

@everyone - https://platform.wafer.space is going down for ~1 hour (but hopefully less) while I upgrade it to the latest code. I'll restart any currently running checks after the update.

https://platform.wafer.space/ is now up and running again with a shiny new coat of paint and some ultrafast precheck runners that have very high single thread performance and can handle a total of 14 concurrent tasks at once.

Welcome to wafer.space …

Platform for wafer.space low cost silicon manufacturing.

3

5

1

18:32

You'll also have manufacturing check history now and the ability to download the output of precheck

18:34

There is also some project metadata you can now set like license, if the project is public and a repo url.

urish started a thread. 12/11/2025 18:50

@everyone - Under 12 hours left (17th Dec @ 11:59pm AoE -- See the countdown or See in your local time). Please make sure that you have clicked the big green "Submit to Manufacturing" button on your design to confirm we have the right version to be manufactured. (edited)

wafer.space GF180MCU Run #1 - Clean GDS Submission Deadline

Event Time Announcer - wafer.space GF180MCU Run #1 - Clean GDS Subm...

Event Time Announcer shows time for wafer.space GF180MCU Run #1 - Clean GDS Submission Deadline in locations all over the world. In UTC it happens on Wednesday, December 17, 2025 at 11:59:00 pm.

7

Tim 'mithro' Ansell pinned a message to this channel. 12/17/2025 23:56

@everyone

The submission deadline has now passed! Congratulations to everyone on the fantastic submissions. If all goes well, the submission was the last active action required of you. The next steps are as follows:

We will stitch the reticle over the weekend. If we identify any violations that were not flagged by the precheck, we will contact you in time to resolve the issue.

The final reticle will be stitched on Monday and sent to GF for validation. GF will then run their proprietary DRC deck on the reticle. If any violations are identified that were not caught by the open source DRC decks, we will contact you to resolve the issue.

We have rerun the latest precheck on all designs: some showed issues with the latest version 1.5.5. We have contacted the project authors, and they still have the opportunity to submit an updated design over the weekend. If any of the other project authors catch a chip-breaking bug in their design, they will also have the chance to submit one final update - please only do so if it is important. Now that the projects are submitted, please make sure to update:

The project description.
The project visibility.
The project URL (if applicable).
And the project license.

This allows us to promote both wafer.space and all the great open source designs on this shuttle.

18