Home    Bloggers    Messages    Resources
Tw  |  Fb  |  In  |  Rss
Jim Turley

Can Readers Recognize MCUs?

Jim Turley
Newest First   Oldest First   Threaded View
<<   <   Page 2 / 2
Jim Turley
Jim Turley
2/7/2012 12:43:12 PM
User Rank
Blogger
Re: Recognizing an MCU
I don't have any better definitions than anyone else, but my gut feeling is that an MCU has:

a) a lot of on-chip I/O, especially I/O that's tailored to a certain application;

b) a fair amount of on-chip nonvolatile memory so that it can run without outside ROM;

c) a modest clock rate (definition of "modest" to change without notice);

d) a somewhat specialized instruction set that's good at bit-twiddling, timing, and/or interrupt handling.

e) is cheap and plentiful.

How's that for vague?

 

50%
50%
Curt Carpenter
Curt Carpenter
2/7/2012 12:11:44 PM
User Rank
Blogger
Recognizing an MCU
 

I think the Mad Hatter in Alice in Wonderland would say something like

"Why, whatever is the problem?  An MCU is whatever you WANT it to be of course!

More tea?" 

But as hard-nosed technologists, I suppose we're obliged to say something more like "there are multiple dimensions at play in the definition of an "MCU," and any discussion needs to begin with an effort to tease those factors out is some statistically-meaningful way..."

I'm frankly more in the Hatter's camp anymore (more fun!) but still, a few dimensions I think matter:

1)  Autonomy – is the device able to perform a complete function (sense/interpret/control) without any supporting hardware?

2) Hardware proximity – is device software tightly coupled to the device hardware (or is a typical program many steps removed from bit-twiddling through things like high-level languages, operating systems and so on.

3) Interface variety – does the device interact with the environment through a few (one or two) bus structures, or does it offer a rich mix of interface possibilities?

4) Documentation density – the ratio of mass of the device divided by the mass of the documentation that must be provided to USE the device in an effective design.

Item 4) is the most fun. The essential docs for the MCU I'm exploring right now runs to just on 700 pages. I recently read that the essential docs for the Intel Core2 Duo Processor spans five volumes and 3,800 pages.  Not sure about the mass ratios, but you get the idea!

 

100%
0%
northstar
northstar
2/7/2012 11:53:49 AM
User Rank
Program Manager
New processor category?
I think that you are right and the border between CPUs and MCUs is blurry. One thing that I would expect from MCUs is to have a different functionality and behavior from CPUs. What I want to say is that I expect that an application running on MCUs to be most of the time in a low-power mode (like Sleep or Deep Sleep) and to acting more interrupt driven (even an RTOS is involved). I would rate CPU something that will be too big (in terms of power of processing, power consumption and even size) to fit a dedicated action (like closing an window). But maybe it's time to think to propose a name for the increasing number of processors that are not a traditional MCU or CPU. Let's have a new category between them. What will be the best name for this category?

50%
50%
<<   <   Page 2 / 2
More Blogs from Jim Turley
The BeagleBoard is finding a home in development at all levels.
MCUs can differ in the instructions they offer, but how important is the instruction set to you as a programmer?
A development tool that automatically generates all of a project's software would be unwelcome.
flash poll
MC on twitter
like us on facebook
Microcontroller Central    About Us     Contact Us     Help     Register     Twitter     Facebook     RSS