feature article
Subscribe Now

Letting Process Drive MEMS Design

MEMS is 20 years behind ICs.

So says MEMS consultant Alissa Fitzgerald of AMFitzgerald. A lot can happen in 20 years – and it could well be argued that MEMS doesn’t have 20 years to catch up. If it has a choice. And if it can even catch up completely.

The issue is the “one device, one process” component of Yole’s MEMS Law. This is something you would never see with ICs, especially in today’s fabless/foundry world. With ICs, the foundry has a process, it works a particular way, it has been thoroughly characterized twelve ways from Sunday, and those results have been incorporated into increasingly sophisticated models that EDA tools can use to predict with reasonable accuracy just what the results of a particular circuit will be.

And MEMS? It misses out on a number of those bullet points. First of all, for the most part, there is no such thing as a fixed process. The very essence of the MEMS Law is that you tweak the process to provide the desired sensor performance. In addition, while there are tools available from companies like Coventor, SoftMEMS, and Tanner to assist with MEMS design, Dr. Fitzgerald describes them more as “emulators” than “simulators,” since they can’t incorporate the fine process details into a final electrical result. So they’re useful, but they’re not at the same level that IC simulation tools are.

For example, she notes that sidewalls created by deep reactive ion etching (DRIE) are typically modeled as being vertical, when, in fact, they’re slightly angled. What might be intended as a rectangle (OK, a cube) is actually more like a trapezoid, and that difference has a measurable effect on something like a proof mass.

Today’s approach, then, is that designers use their best guesses as to how to configure a sensor, and then they build it and see how it works. Inevitably, it won’t be perfect, and so they go another round in classic “construct by correction” mode. And that’s just to get the sensor right – that’s not taking into account the co-design of the accompanying conditioning ASIC, which may itself have to be spun another round after the sensor is finally final.

The result? Well, consider that a sophisticated SoC with billions of transistors can be produced in around 18 months. A MEMS sensor with only a few moving parts (“only” being used advisedly) can take five years to see the light at the end of the tunnel. Five years isn’t egregious if you’re used to dealing with, say, the military/aerospace or even the automotive markets. They’re used to a ponderous, plodding pace. But there is a particular mismatch with the consumer-oriented market for items like phones and tablets, which are driving MEMS volumes and which last maybe six months before being replaced by a new and better version.

You could argue that the MEMS industry needs to achieve the kind of structure and modularity enjoyed in the IC industry, but that’s realistically not going to happen. Companies looking to differentiate their sensors are going to look to every advantage they can, whether it be the addition of new materials or a change in how those materials are processed. TSMC would never allow that for an IC customer, but it’s a degree of freedom needed for MEMS.

Which frankly raises the question, what does this mean, given that TSMC and other IC foundries are getting involved in MEMS? According to Silex, who bills itself as the largest pure-play MEMS foundry, the IC foundry guys are not typically developing their own proprietary ground-up technologies; they’re incorporating someone else’s completed process recipe – like Analog Devices’. So that raises the question as to whether they really plan to be MEMS-for-all-takers foundries or just cherry-pickers.

Silex’s particular solution to this problem stops short of standardizing the process itself, but it regularizes and modularizes the various process steps, making it easier to pull a process together without having to start from scratch. They call this their SmartBlocks approach.

To be clear, a block doesn’t indicate some functional element being added to a device; for instance, you wouldn’t have a cantilever as a block. Rather, it’s a collection of process steps. So at the lowest level, Silex has a library of process steps that it makes available to its customers. Those steps have been grouped together at a higher level to create the SmartBlocks process modules.

This means that a designer can work at a higher level using SmartBlocks, while still bringing in low-level process steps if needed. He or she can pull both from the SmartBlocks library and the process steps library; these blocks and steps can be arranged and rearranged to suit the new design – within limits.

The limits to the design process include mask layout rules; the allowed properties of various materials used, for example, as films; tolerances; and process step ordering restrictions. The latter is important in situations where, for example, a material is laid down that can’t tolerate high temperatures; that step can’t be followed by any high-temperature processing steps.

In the IC world, all of this data would be neatly bundled into process kit files; no such standardization exists here. The benefit of the SmartBlocks methodology is that one goes from what is essentially a “you can do anything” approach with no associated performance data to a “design within guidelines” approach that provides more predictable data to the designer.

To be clear, SmartBlocks isn’t a “product” that’s simply opened up to customers. Things still need enough manual attention that Silex works with each customer to craft the necessary process; SmartBlocks is what they use internally to make that process more predictable. As a result, you actually won’t see much about SmartBlocks on their website.

In the case of Silex’s recent announcement, they have partnered up with AMFitzgerald for actual sensor design, and Dr. Fitzgerald likens their newly-announced RocketMEMS process to that of a system designer specifying a transfer function to be designed by a circuit designer. The OEM in search of a sensor would specify all of the desired characteristics of the final sensor – performance, range, sensitivity, noise immunity, linearity, etc. – and AMFitzgerald would create the black box that meets those specs.

They would do so by leveraging the information and convenience of the SmartBlocks offering from Silex. They’ll be using that data to populate models for the simulation tools that they’ll use to validate their design prior to building. The expectation is that they can turn designs around much more quickly and accurately.

This takes a complex design flow, with lots of internal feedback loops, and makes it more unidirectional. The current approach is process-drives-design-drives-process-drives-design-drives… The goal here is to get to a simpler process-drives-design-period methodology. Which is how the IC industry works.

While AMFitzgerald and Silex will be working together in this mode, they ultimately see this as a way that the entire industry needs to work. Captive companies like ST and Freescale probably have such capabilities already in place in-house, but it’s not available to designers using foundries.

20 years is a lot of catching up to do. But rationalizing the MEMS design process could go a long way towards allowing a more nimble response to increasing demands from the rapidly growing range of systems wanting to use sensors, putting it much more in line with what IC designers can do today.


More info:

Silex/AMFitzgerald announcement

AMFitzgerald RocketMEMS program

Silex Microsystems

4 thoughts on “Letting Process Drive MEMS Design”

  1. It does not seem to be fair puting all MEMS designers into one box. Many but not all of them follow the approach of a “guess and build”. Especially those who gained a lot experience by developing commerical MEMS products are actually using sophisticated modelling techniques. It is true that these designers mostly work in captive fabs, and do usually not share their experience in the public domain. But certainly commerical design tools are able to address some of the issues mentioned in the article. I leave it up to everybody to check on this by simply googling for “sidewall angle mems model” or “mems ic design”.

  2. I’d like to provide some clarification and more context on the comment I originally made to Bryon. MEMS EDA tools can indeed accurately simulate mechanical and electrical performance, when high quality process data is available as an input. The main problem faced by MEMS designers, especially fabless ones, is that process-specific (and importantly, foundry-specific) data is not commonly made available. Furthermore, theory can not fill that gap – first-principles physics models have not yet been developed for many MEMS fabrication processes, so one can not usually input a process recipe and theoretically predict the resulting features. In the absence of process data, most MEMS devices can not be simulated to the accuracy enjoyed by IC designers. However, if efforts are made to measure and empirically characterize a process, and that data is made available to designers, simulation with powerful predictive capabilities that will reduce development time and cost is possible with today’s EDA tools. I invite the EDA vendors to add comments on their specific capabilities in this regard. There are MEMS manufacturers who are employing this approach of process-informed simulation with success, and SmartBlocks will enable AMFitzgerald to do it as well.

  3. As Principal Technologist at Coventor, I’d like to clarify the
    solutions available today and the trends we see in the MEMS industry. First, I appreciate Alissa’s updated remarks regarding EDA tools and their ability to significantly reduce time to market when process data is made available. The case of side wall angles as described in the article is a great example. In Coventor’s MEMS+ tool, the side wall angle is one of many parameters available in the MEMS models created for rapid design tradeoffs or for IC and system simulation. This parameterization enables fabless designers and MEMS designers at IDMs to rapidly evaluate and optimize the interdependencies between process sensitivity, design, and IC control circuitry. Rapid evaluation
    earlier in the design flow means shorter time to market.

    But Coventor’s offering goes beyond device and circuit solutions.
    SEMulator3D, for MEMS foundries and IDM’s, enables foundry
    technologists to accurately model their processes and share this data
    with their fabless customers. Leading MEMS foundries and large
    commercial foundries are adopting these tools and some now offer new
    design enablement methodologies which provide highly accurate 3D
    models showing the design-process technology interaction, prior to

    We agree with AMFitzgerald, that simulation tools armed with process
    specific data, do indeed provide a significant advantage over costly
    build, WAIT, and test methodologies. We agree with Alissa that the
    greater sharing of process data from the foundries will significantly
    move the MEMS industry forward.

Leave a Reply

featured blogs
Jun 1, 2023
In honor of Pride Month, members of our Synopsys PRIDE employee resource group (ERG) share thoughtful lessons on becoming an LGBTQIA+ ally and more. The post Pride Month 2023: Thoughtful Lessons from the Synopsys PRIDE ERG appeared first on New Horizons for Chip Design....
Jun 1, 2023
It's been 40 years since Jim Solomon, Richard Newton and Alberto Sangiovanni-Vincentelli co-founded SDA Systems, a physical IC design tools company that became Cadence. Most want to measure this year as the 35 th birthday of Cadence, marked by the merger of SDA Systems and EC...
May 8, 2023
If you are planning on traveling to Turkey in the not-so-distant future, then I have a favor to ask....

featured video

Synopsys Solution for RTL to Signoff Power Analysis

Sponsored by Synopsys

Synopsys’ industry-leading power analysis solution built on PrimePower technology that enables early RTL exploration, low power implementation and power signoff for design of energy-efficient SoCs.

Learn more about Synopsys’ Energy-Efficient SoCs Solutions

featured contest

Join the AI Generated Open-Source Silicon Design Challenge

Sponsored by Efabless

Get your AI-generated design manufactured ($9,750 value)! Enter the E-fabless open-source silicon design challenge. Use generative AI to create Verilog from natural language prompts, then implement your design using the Efabless chipIgnite platform - including an SoC template (Caravel) providing rapid chip-level integration, and an open-source RTL-to-GDS digital design flow (OpenLane). The winner gets their design manufactured by eFabless. Hurry, though - deadline is June 2!

Click here to enter!

featured chalk talk

Peltier Modules
Do you need precise temperature control? Does your application need to be cooled below ambient temperature? If you answered yes to either of these questions, a peltier module may be the best solution for you. In this episode of Chalk Talk, Amelia Dalton chats with Rex Hallock from CUI Devices about the limitations and unique benefits of peltier modules, how CUI Devices’ arcTEC™ structure can make a big difference when it comes to thermal stress and fatigue of peltier modules, and how you can get started using a peltier module in your next design.
Jan 3, 2023