Here's a what if. Say your application is a straightforward industrial process that can be handled by an 8 bit MCU. However, when upset conditions occur then suddenly all sorts of interrupts happen, complex software decisions need to be made, real time response is required. Would it be feasible to design a system with a seperate MCU, maybe 32 bit, to deal with the more complex software environment, rather than trying to cram everything into a one big MCU? Especially considering that upsets should be very rare..
If you are as interrupt-intenseve as you say, you have two options:
1) A 16-bit microcontroller. Why? because you have extra proessing power and don't have the interrupt overhead of a 32-bit MCU
2) Go like you said - an 8-bit as a dedicated interrupt processor, interfacing to a larger 32-bit or 26-bit system controller. I see this a lot
Truchard will be presented the award at the 2014 Golden Mousetrap Awards ceremony during the co-located events Pacific Design & Manufacturing, MD&M West, WestPack, PLASTEC West, Electronics West, ATX West, and AeroCon.
In a bid to boost the viability of lithium-based electric car batteries, a team at Lawrence Berkeley National Laboratory has developed a chemistry that could possibly double an EV’s driving range while cutting its battery cost in half.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.