feature article
Subscribe Now

Reconfigurable FPMA?

Could Baolab Be the Next Altera or Xilinx for MEMS?

Today we’re going into the world of imagination. Imagining what if, and then imagining what.

Is the phone ringing? Does your computer keep pinging because yet more… medical assistance is being proffered at cheap prices from overseas? Is your boss watching? These are all distractions that will hinder the process of imagining, so, if you can, let’s place ourselves in a professional setting: a cool, dark place where you can lie back and stretch out and open your mind… close your eyes… forget that I’m there in that chair next to you… ignore the timer on the end table… breathe easily… shuck those cares, like the meeting you’re supposed to be in right now… and just… imagine.

OK, here we go.

First: the big “what if” (which will become the big “what”): Imagine a MEMS sensor that can act as any of the traditional motion- and position-sensing devices for any axis. We’re talking linear acceleration… rotational acceleration… even magnetic and pressure. “What??” you ask, but be still, have a little faith (for the moment), and let your mind run with it and see where it goes.

Also imagine that this can be done using a standard CMOS process with no extra steps or materials. Proof masses are built out of metal using the standard metal stack.

Depending on what you’re used to, this, by itself, presents some interesting possibilities. If you’re used to individually-packaged sensors made with special materials, then some immediate benefits accrue. Obviously, using only a CMOS process opens up a wide range of manufacturing possibilities rather than the typical one-fab option. And if you want multiple sensors, you have to make sure they’re aligned (although calibration is supposed to correct for that). And, presumably, this should save space and cost.

Of course, CMOS-only MEMS has been around for a while, so that’s not hard to imagine. And, from a user standpoint, you can get multiple sensors co-packaged, which relieves you of alignment duties (while placing them on the pick-and-place machine that’s assembling the thing).

And you can, to some extent, integrate multiple sensors (say, for 3 axes) on a single chip – at least similar sensors, if the materials make a difference. Then the alignment issues go away. This is doable today also.

So using a CMOS-only process, bringing multiple axes of a sensor or two onto a single substrate… not much to imagine since it’s not news.

Putting all of the different sensors on a single die? That gets more interesting. Using the industry standard of proliferating axes (or is it degrees of freedom that get proliferated?), you get 3 for linear; 3 for rotational; 3 for magnetic; and 1 for pressure. That’s 10 monolithic axes, baby. You can now fuse those together at a low level to provide a single set of position vectors representing the consensus opinion of the sensors as to where you are. (I’m assuming that creative folks would still want the raw sensor data, too, since they’ll figure out something interesting and unusual to do with it.)

Of course, fusion is mostly done by software these days. But, since these things are all in one place, could that fusion be done in hardware in the accompanying ASIC, immediately following the conditioning circuits?

And, since we’re organizing this party on a single standard CMOS die, we might as well invite the ASIC itself to come and rub elbows with the sensors, eliminating yet another die or even a package. In fact, if we can restructure our MEMS technology to use fewer layers of metal, we might even be able to position the sensors on top of the ASIC circuitry, assuming we can restrict ASIC interconnect to the lower metal layers.

And, if some of the temperature and other environmental effects on the proof mass, which is made of metal, also affect the same metal in the circuitry, might there be some interesting self-compensation or auto-calibration tricks that could take advantage of this?

Now, if we’re dealing with a generic sensor, there has to be some way of making it act like an accelerometer or gyroscope or magnetometer or barometer. Partly, there’s the question of how you give it a chameleonic character, which we’ll come back to, but there’s also the question of range and sensitivity; they’ll be different for the different sensor functions.

So these have to be adjustable. Perhaps that could be done with surrounding circuitry that would hard-code which was which. While that’s not particularly flexible, you would get the benefits of a single template to configure for each sensor, adding to the benefits of integration.

Or perhaps it could be configured by software, although that could be tricky for something that needs to be functional at or near wake-up. In the latter case, maybe some kind of non-volatile memory? If programmed only once, a simple e-fuse OTP technology could be compatible with CMOS. If it had to be reprogrammed, then that would get a lot harder to integrate; it might have to rely on other in-system Flash or other NVM. Or perhaps a MEMS structure like a cantilever relying on stiction as memory. Might that be reliable enough? Small enough?

Taking this a bit further, if these things were really tiny, you could put a lot of them in a small space. Then you could take advantage of redundancy to improve yields, swapping out bad sensors for good. Or you could use multiple units as a single sensor: if you can average the response of two or more sensors, you can eliminate some noise in advance of any conditioning circuits.

But here’s where things can get more interesting yet. What if you could have an entire array of these things, not just configurable, but re-configurable? Like an FPGA, except with MEMS instead of logic. An FPMA – Field-Programmable MEMS Array. We all know what’s happened in the FPGA market, although, to be clear, it happened that way only once: a) the PAL architecture provided better speed and cost than prior technologies, and b) PALASM software made designing something less of a chore. These two events created a flourishing programmable logic market, upon which FPGAs were able to build. So an FPMA market would also need to benefit from cost, performance, and ease of use.

And, to be sure, one final driver: compelling applications. What would you build if you had an FPMA? Where is your imagination taking you now?

OK, so we’ve had our flight of fancy. Let’s starting bringing things back, as our time is almost up. There remains within this electromechanical fantasy one central assumption, the key initial what-if: the generic sensor. Now we must move from “what-if” to “what.” As in, “What the heck would such a beast look like?”

This whole dream sequence is brought to you courtesy of Baolab, who have outlined the scenarios that have been floating through your suggestible mind. The one thing they haven’t made clear is what the actual sensor looks like.

One tantalizing aspect is the ability to configure which axis is being served. Frankly, it’s easy to imagine how X and Y could be handled, but turning an X or Y into a Z? Not so obvious. It’s actually easier for me to picture a 3-in-1 sensor that does all three axes together (with Z having its own special implementation) than a single efficient sensor that could be X, Y, or Z.

Then there’s the other obvious question: how do you get a single unit to act on linear, rotational, magnetic, and pressure forces? They have a whitepaper that lays out at a high level the fact that they’re all forces. And if you can have a generic sensor that senses forces, then, well, there you are. You’re set.

Yeah, I know. That part is more or less self-evident. The big question is: How do you get one sensor to do all of that? We can do magnetics without magnetic materials, using Lorentz forces, so that’s one thing. But it’s not obvious how sensing Lorentz forces is the same as sensing lateral or Coriolis forces or air pressure.

So where does that leave us? It leaves us still in the realm of imagination. Baolab has tantalized us with the possibilities of what they call a NanoIMU (not sure if Memsense, who also makes a “Nano IMU” will take issue with that). But, as of this writing, I haven’t been made privy to the pièce de resistance – the actual “here’s how we do it.” Perhaps that’s intentional; secrets abound in our world. Usually they’re poorly kept, to be sure, but I haven’t unlocked this one.

So I’ll leave you to imagine how this might work, and we can talk about it some more in our next session.



Hey, one more thing: I just learned a little more about the “generic cell” that, frankly, raises more questions than it answers.

“The generic cell can do 1 axis: x and y cells are identical, just aligned at right-angles to each other on the wafer. z has a very similar geometry, but is arranged such that motion (and detection) is constrained in the lateral rather than the vertical direction.”

 OK… that sounds like two cells, not one.

“The cells themselves are very scalable too, each being constructed from multiple sub-structures, each comprising a moving element surrounded by fixed combs of capacitive detection conductors.”

Hmmm… sounds more like Lego block approach.

More for you to imagine and discuss in our next session.


More info:



2 thoughts on “Reconfigurable FPMA?”

  1. We described in vague terms (the only kind available to us) a generic IMU cell that could provide MEMS reconfigurability. What do you think the generic cell might look like? Or, from the last clues, is it off the mark to refer to it as a generic cell?

  2. Sensors convert some quality of the physical world into an analog signal. This signal may be used directly in an analog design and/or converted to digital for digital processing. But sensors, unlike transistors or logic gates, are as different as chalk and cheese. Each type is unique to what it is sensing. You start with the physics of the situation, not the analog output.

    Most sensors are singular in application. For example, MEMs measure acceleration, rotation and magnetic field in 1-3 axes, usually at one physical place in a system. This begs the question of whether you need an “array” of more than the 9 sensors mentioned.

    Other sensors, such as temperature and pressure tend to be located at the source of the sensing: where the temperature, etc. is to be measured. This argues against trying to put multiples of these sensors on a single chip.

    You need multiple sensors when there is a pattern to be sensed. Digital cameras are a good example, where each pixel is a light sensor in an image array. An array works because a lens can route the light of the image to the pixels on the chip.

    And there are advantages of doing analog processing on the signals from these pixel sensors. The signal to noise ratio of the individual pixels is never going to get better than right at the pixel. This is important for detecting weak sources, like a small laser spot at 5 meters. Local processing of an array of pixels implies possible value of a programmable array of analog processing elements at the pixels.

    Other examples of array-able sensors are a little harder to come by. You could make a case for an array of pressure sensors for detecting patterns of force, similar to skin. But this gets to be more of a mechanical problem of transmitting the force pattern to the sensor.

    But if you can convert the force to a pattern of light/dark or color on a pressure sensing material, then you can use your programmable pixel camera to look at the implied force patterns. And this may be a general method for sensing patterns of physical qualities, such as force/pressure, temperature, sound (pressure again), chemical composition, etc. This is actually a 2-stage sensor: one to convert the target physical quality to light/dark, and an imaging chip to convert the light/dark to analog.

    Sorry to be somewhat negative on MEMs arrays. Perhaps it is due to limited imagination on my part. If so, I am eager to be instructed.

Leave a Reply

featured blogs
Dec 1, 2020
If you'€™d asked me at the beginning of 2020 as to the chances of my replicating an 1820 Welsh dresser, I would have said '€œzero,'€ which just goes to show how little I know....
Dec 1, 2020
More package designers these days, with the increasing component counts and more complicated electrical constraints, are shifting to using a front-end schematic capture tool. As with IC and PCB... [[ Click on the title to access the full blog on the Cadence Community site. ]...
Dec 1, 2020
UCLA’s Maxx Tepper gives us a brief overview of the Ocean High-Throughput processor to be used in the upgrade of the real-time event selection system of the CMS experiment at the CERN LHC (Large Hadron Collider). The board incorporates Samtec FireFly'„¢ optical cable ...
Nov 25, 2020
[From the last episode: We looked at what it takes to generate data that can be used to train machine-learning .] We take a break from learning how IoT technology works for one of our occasional posts on how IoT technology is used. In this case, we look at trucking fleet mana...

featured video

Product Update: Broad Portfolio of DesignWare IP for Mobile SoCs

Sponsored by Synopsys

Get the latest update on DesignWare IP® for mobile SoCs, including MIPI C-PHY/D-PHY, USB 3.1, and UFS, which provide the necessary throughput, bandwidth, and efficiency for today’s advanced mobile SoCs.

Click here for more information about DesignWare IP for 5G Mobile

featured paper

Keys to quick success using high-speed data converters

Sponsored by Texas Instruments

Whether you’re designing an aerospace system, test and measurement equipment or automotive lidar AFE, hardware designers using high-speed data converters face tough challenges with high-frequency inputs, outputs, clock rates and digital interface. Issues might include connecting with your field-programmable gate array, being confident that your first design pass will work or determining how to best model the system before building it. In this article, we take a look at each of these challenges.

Click here to download the whitepaper

Featured Chalk Talk

Benefits of FPGAs & eFPGA IP in Futureproofing Compute Acceleration

Sponsored by Achronix

In the quest to accelerate and optimize today’s computing challenges such as AI inference, our system designs have to be flexible above all else. At the confluence of speed and flexibility are today’s new FPGAs and e-FPGA IP. In this episode of Chalk Talk, Amelia Dalton chats with Mike Fitton from Achronix about how to design systems to be both fast and future-proof using FPGA and e-FPGA technology.

Click here for more information about the Achronix Speedster7 FPGAs