# Choosing a microcontroller for a project [duplicate]

Possible Duplicate:
How to choose a MCU platform?

I'm designing my first project that could possibly go in to production(as a university project) but I am now stuck on choosing a microcontroller for it. My main experience is with Atmel AVR so im tempted with choosing an AVR, however I don't feel that it would be future proof. What characteristics should I look for when choosing a microcontroller? How should I decide between a 8- (Atmel AVR), 16- (MSP430) or 32-bit(ARM Cortex M3) microcontroller?

## marked as duplicate by stevenvh, Leon Heller, Dean, Dave Tweed♦, W5VO♦Oct 15 '12 at 5:00

• It totally depends on your application. In general - the cheapest that fits your needs and capabilities. – miceuz Oct 14 '12 at 20:26
• @miceuz But I am unsure on things like flash size, number of pins, and peripherals. Does this mean that I'm not ready in the project to be choosing a microcontroller? If so how am I supposed to go about development of the project? As in my mind its a critical part of the project. – Dean Oct 14 '12 at 20:28
• what do you mean you are unsure about peripherals? So you have an idea like "I want to build a widget" and already are thinking about a production? You need at least to lay out the plan how will you build it - this will define your requirements. And then build a prototype on some platform you are fast on. – miceuz Oct 14 '12 at 20:35
• I'm glad that you brought up future proofness. Here is a recent thread with a very similar question. – Nick Alexeev Oct 14 '12 at 20:44
• Incorporate a webserver? Now this starts to get interesting... I'd even advise to look at Raspberry Pi... – ppeterka Oct 14 '12 at 20:57

There are quite some factors one needs to assess when going into production. EVen though a given microcontroller might not seem "future proof" because for example performance regarding possible future designs, its cost advantage might make it the preferred choice. $1 at 10000 pieces makes for$10000!