Downloading / Uploading projects and libraries


The announcement of the XH018 free and unlicensed PDK is really exciting. Combined with the Hydra and Raven projects (and their associated libraries), this is the first opportunity we’ve had for truly open silicon. The preferred method of editing projects seems to be to use the OpenGalaxy VNC client. Are there any plans to allow for alternate methods of development, such as using a local qflow toolchain?

Relatedly, are there any plans to allow users to download the PDKs and open IP for offline use? One big advantage of developing in an open fashion is the ability to share git repos. In particular, one can refer to a particular tag or commit to indicate that it is “fabrication tested and verified”. Similarly, storing one’s own commit history in local version control makes it easier to track changes and figure out exactly how you solved that one weird problem in the past.

Are there any plans to release the PDKs for download, and are there plans to include source repo links (or provide source hosting) on various libraries?


Hello Sean,

Thanks for your kind words about the efabless platform.

Currently, you can always use a local qflow toolchain, although it is largely up to you to edit the main setup file with pointers to technology files that you must download from the foundry (under NDA, implied). Part of the point of the efabless platform is to take many of the open-source EDA tools that distribute with open PDKs and demonstrate a system where they are configured for a specific foundry process using foundry rules. But that takes a lot of time and effort. If you want to use the open PDKs, using qflow is pretty simple, although the open PDKs are only compatible with MOSIS for a few processes (and use of SCMOS for TSMC processes was discontinued by MOSIS last year).

There are plans to allow users to download whatever part of any project is not proprietary to the foundry. Our most likely short-term response to that would be to set up a gitlab entry for the Raven sources (which are all verilog, and simulated using behavioral verilog, so nothing foundry-proprietary there).

The open PDKs are a bit hobbled by not having either SPICE models or a full set of useful IP, so we have some work to do there to bring them up to speed with the X-Fab PDKs we’ve made.

What is certainly true is that the more demand voiced by platform users, the higher priority a topic will get, so keep up the forum discussion!