editor's blog
Subscribe Now

mCube’s New Low-Power Accel: What It Is and Isn’t

mCube made more noise recently with their announcement of a very small, low-power accelerometer. There were a number of aspects to the release; some intriguing, some… less so.

Let’s start with intrigue. The whole focus here is on a small device that can be used in space-constrained, power-stingy applications – like wearables. Obviously space is critical in any such device, but they point out that flexible circuit boards can enable more… well… flexible shape designs. And, while the accelerometer isn’t itself flexible, the closer you can come to an infinitesimal point on a flexible board, the more likely your connections are to remain intact. So, on flex boards, small=reliable.

They get the size by stacking a MEMS wafer with through-silicon vias (TSVs) over a CMOS wafer (all of which is then garnished with a cap wafer). This means that bond pads are needed only for actual connections to the outside world, not for intra-package die-to-die connections, which can take a lot of space.

mCube_figure.png 

Cost is also mitigated by using an old process with fully depreciated equipment. Right now, they’re at 180 nm; they could go to 150 without spiking the cost curve. In addition, all of the steps – from the different wafers to bonding them – are done in a single fab. This is as compared to other processes, where wafers have to be bundled up and sent to different fabs for different parts of the process.

They’ve also built in a couple key application-oriented features intended to go easy on battery life. First, you can tune the sample rate – fast for tablets and phones that need to be responsive enough for games (a couple thousand samples per second), slower (400 samp/s) for wearables. Second, they have power modes: a normal mode at 4.7 µA (50 Hz), a single-sample mode at 0.9 µA (25 Hz), and a “sniff mode” at 0.6 µA (6 Hz).

Sniff mode monitors for activity, sending an interrupt when detected. The threshold for what constitutes “active” can be tuned to suit the application.

So, functionally, this seems to compete pretty well. Which is really all that should matter. The less intriguing bits have to do with the marketing and what feels like playing a little loose with terminology. Any good marketer knows that it’s great if you can carve out for yourself a new market or “category” so that you have no competition. Problem is, too many folks have read that in their business books, and try it too often.

Here, mCube is trying to define the “IoMT” – Internet of Moving Things – as a separate thing. This suggests that, somehow, items with IMUs constitute this separate class of system. Sorry, but it just doesn’t work for me.

A little more worrisome is their use of the word “monolithic.” As in, they’re claiming a monolithic solution. First, “monolithic” literally means “from one stone.” This is not from one stone – it’s from three wafers. Monolithic would be if the MEMS and CMOS were fabricated out of the same wafer. (I won’t quibble about the cap wafer.)

They even use this to distinguish themselves from InvenSense, who uses what they call a “stacked” approach. They say that this distinction is significant enough to define the end of “Sensors 2.0” and the beginning of “Sensors 3.0.” Again, more new categories. Again, not working for me.

The only real difference here from InvenSense is that InvenSense inverts the MEMS wafer and bonds face-to-face (and does this in some other fab, by implication). mCube stacks bottom-to-top, connecting with TSVs. That has some benefits – don’t get me wrong – but it doesn’t feel to me like the revolutionary birth of a new category.

OK, kvetching over. You can find more information about the tiny new mCube accelerometer in their announcement.

Leave a Reply

featured blogs
Mar 14, 2024
Mathematics is a universal language, understood and appreciated in every corner of our ever-inquisitive world. March 14 is recognized as Pi (Ï) Day by mathematicians and enthusiasts worldwide to acknowledge the significance of Pi, which has been an unwavering ally in humanit...
Mar 14, 2024
We explain USB4 version 2.0, unpacking the specification's speed, exploring its use in AI accelerators, and laying out the USB4 v2 controller IC design process.The post With USB4 v2, Faster Speeds Is the Name of the Game appeared first on Chip Design....
Mar 5, 2024
Those clever chaps and chapesses at SiTime recently posted a blog: "Decoding Time: Why Leap Years Are Essential for Precision"...

featured video

Tackling Challenges in 3DHI Microelectronics for Aerospace, Government, and Defense

Sponsored by Synopsys

Aerospace, Government, and Defense industry experts discuss the complexities of 3DHI for technological, manufacturing, & economic intricacies, as well as security, reliability, and safety challenges & solutions. Explore DARPA’s NGMM plan for the 3DHI R&D ecosystem.

Learn more about Synopsys Aerospace and Government Solutions

featured paper

Reduce 3D IC design complexity with early package assembly verification

Sponsored by Siemens Digital Industries Software

Uncover the unique challenges, along with the latest Calibre verification solutions, for 3D IC design in this new technical paper. As 2.5D and 3D ICs redefine the possibilities of semiconductor design, discover how Siemens is leading the way in verifying complex multi-dimensional systems, while shifting verification left to do so earlier in the design process.

Click here to read more

featured chalk talk

Accessing AWS IoT Services Securely over LTE-M
Developing a connected IoT design from scratch can be a complicated endeavor. In this episode of Chalk Talk, Amelia Dalton, Harald Kröll from u-blox, Lucio Di Jasio from AWS, and Rob Reynolds from SparkFun Electronics examine the details of the AWS IoT ExpressLink SARA-R5 starter kit. They explore the common IoT development design challenges that AWS IoT ExpressLink SARA-R5 starter kit is looking to solve and how you can get started using this kit in your next connected IoT design.
Oct 26, 2023
18,200 views