editor's blog
Subscribe Now

We Won’t Call You; Just Call Us

One of the challenges with sensors is that, at their most fundamental level, all they do is provide some value reflecting whatever it is they’re sensing. If you want to know that value, you have to go get the value. “You” typically being the main processor in the system.

That’s easy enough if it’s something you occasionally do under the direction of a program, but if you want the sensor to alert you when something happens, then you have to poll constantly so that you know when something changed. That can steal a lot of cycles from the processor, and can be a particular issue for smartphones that have lots of sensors.

I had a discussion about this with Bosch Sensortec’s Leopold Beer at the recent MEMS Executive Congress. He said that with their IMUs, polling still dominates, but that they’ve got a state machine in there that can be programmed to fire an interrupt; their interface supports both polling and interrupts.

For example, the unit has an auto-sleep mode, and can be programmed to wake itself up. You can program in thresholds and timing. You can have it fire an interrupt when changing between portrait and landscape modes; the angles and hysteresis levels are programmable. This relieves the application processor of some of the more mundane polling duties.

For more complex tasks like counting the number of steps you take when running, much more processing is required, so for those tasks the processor still has to go poll the sensor and do the data munging itself.

One solution is to have a separate sensor microcontroller that can manage multiple sensors to offload some of the application processor duties in a programmable way.

A dedicated microcontroller on the same die as the sensor might make sense for so-called “sensor fusion” applications – where the “sensed” state isn’t just the result of a single sensor or even sensor type, but the accumulation of data from numerous sensors synthesized into a single combined more “intelligent” state. It’s certainly possible from a technology standpoint; the only question is whether the cost is justified.

Something to watch for as sensors continue to populate the world…

Leave a Reply

featured blogs
Jan 27, 2020
Everybody writing software wants it to perform according to its specification and to be reliable. I hope that this is a safe assumption. There are 3 things to be done to achieve these goals: design well; implement carefully; test thoroughly. None of these are optional. A care...
Jan 27, 2020
I see switches everywhere: toggle switches, slider switches, rotary switches, pushbutton switches, magnetic switches, reed switches, mercury switches, smart switches, and'€¦ the list goes on....
Jan 24, 2020
[From the last episode: We looked at the different ways memory can be organized in different kinds of systems.] Let'€™s look at a scenario: you run a restaurant, but you'€™re short on funds to hire people. So you'€™re your own chief cook and bottle-washer. You do everyt...
Jan 23, 2020
Embedded design trends typically revolve around three main ideas: faster data rates, smaller form factors and cost-effective solutions. Those design trends drive the theme for the 2020 Embedded Tech Trends forum: The Business and Technology Forum for Critical and Intelligent ...

Featured Video

Automotive Trends Driving New SoC Architectures -- Synopsys

Sponsored by Synopsys

Today’s automotive trends are driving new design requirements for automotive SoCs targeting ADAS, gateways, connected cars and infotainment. Find out why it is essential to use pre-designed, pre-verified, reusable automotive-optimized IP to meet such new requirements and accelerate design time.

Drive Your Next Design to Completion Today with DesignWare IP® for Automotive SoCs