Coventor recently announced the latest release of MEMS+, their MEMS EDA/CAD tool, and the timing was tough because it came just after I had an article involving process design kits (PDKs). And amongst the things that the latest MEMS+ release brings is movement towards MEMS PDKs (MPDKs).

MEMS devices are, of course, notorious for evading any attempts to rope in process and design options through standardization of any kind. Efforts continue, but it remains a challenge.

This means that any MEMS design involves a collaboration between a particular fab (captive or foundry) and the design folks to come up with a physical design that meets the requirements for a particular new sensor or actuator. And what’s done for some new design may have nothing to do with what has been done in the past. Materials may change, dimensions and shapes may change, and circuits and packages may change. Everything’s negotiable.

With the latest release of MEMS+, Coventor says that they’re enabling the use of PDKs for well-established sensors – IMUs, devices built on Leti’s MnNEMS process, and piezoelectric devices. The MPDK isn’t standardized, but then again, silicon circuit PDKs have also taken a long time to move towards standardization.

So Coventor is working, initially, with one fab and EDA company at a time, starting with XFAB and Cadence. You may recall from the silicon side that the first step away from incompatible PDKs for each tool/foundry combination was for a single foundry to unify its PDKs for all tools. So initially, for example, TSMC PDKs were different for Cadence, Synopsys, and Mentor tools, and then TSMC worked to unify the format.

But the result worked only at TSMC; GlobalFoundries and other fabs would have their own formats, even if unified across tools. This is the issue that the OpenPDK project has tackled since 2010.

This is the path that MPDKs are likely to take, according to Coventor. It would be nice if the lessons of the past allowed us to bypass some of the effort replication. For instance, if XFAB gets something going, it sure would be nice to use that as the basis for someone else, layering on change and generalizing rather than starting from scratch or even turning the XFAB-only MPDK into a similar-but-incompatible someone-else-only MPDK.

You can read more about this and the other new features in MEMS+ 6.0 in Coventor’s announcement.

Related

MEMS First Silicon Success

Some time back, AMFitzgerald and Silex, a MEMS consultancy and foundry, respectively, announced their “RocketMEMS” program in order to take steps to accelerate the notoriously slow MEMS design cycle. At the recent MEMS Executive Congress, they announced the first fruits of this labor. They had designed three pressure sensors: one…

Simulating the Whole Process

Back when discussion CMOS-compatible MEMS, I briefly mentioned a couple tools from Coventor that are used in MEMS design. But one of them actually has use for any semiconductor process. You might think it’s another TCAD tool, but actually, it isn’t. TCAD tools work with low-level physics to model small…

Tanner to Join Mentor: Outsider Gets a Crew

Way back in 2009, we took a look at Tanner – an EDA company marching to its own beat. They always seemed – and continue to seem – apart from the pack. We talk about the Big 3 in EDA – Synopsys, Cadence, and Mentor – and lots of little…