element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
NXP Semiconductors
  • Products
  • Manufacturers
  • NXP Semiconductors
  • More
  • Cancel
NXP Semiconductors
Blog Choosing the right MCU or MPU for your design
  • Blog
  • Forum
  • Documents
  • Events
  • Quiz
  • Polls
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join NXP Semiconductors to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: yoSoyTono
  • Date Created: 20 Jun 2018 7:12 PM Date Created
  • Views 4187 views
  • Likes 3 likes
  • Comments 4 comments
  • hardware
  • microprocessor
  • microcontroller
  • mcu
  • mpu
  • nxp
  • Architecture
  • software
Related
Recommended

Choosing the right MCU or MPU for your design

yoSoyTono
yoSoyTono
20 Jun 2018

Microcontrollers (MCUs) and Microprocessors (MPUs) are nowadays vital for a wide range of industrial and automotive applications: from motor control to infotainment systems and auto body control solutions. Therefore, selecting the right MCU or MPU for a product can be a huge hurdle, as not only engineers need to consider the technical features of the device but the cost and lead-times to build the business case for the proposed solution.

 

Both hardware and software engineers should first work out the high levels of the system (the block diagram and flowchart) and details (specifications and solution requirement) to collect enough information to make a rational decision for selecting the MCU or MPU. Choosing the appropriate device can reduce the Bill of Materials (BOM) cost —and lower the price of the Electronic Control Unit (ECU).

 

Normally, MCUs are used in cost-optimized solutions where tight control of BOM, power saving, and limited UI interaction are a must-have requirement. They tend to be utilized in low-power applications like remote controls, consumer electronics, and smart meters. While MPUs are ideal for rich UI OS-based (Linux, Android, or Windows CE) industrial and consumer applications, with intensive computing, high-speed connectivity, and high-performance applications.

image

 

Here are some ideas to consider when choosing the right MCU or MPU for your design:

1- List all hardware interfaces.

Enumerate all external interfaces that the device need to support using the general hardware block diagram. Include both communication (USB, Ethernet, I2C, SPI, UART...) and real-time input/output interfaces (digital to analog, analog to digital, PWM...)

 

2- Examine the software architecture.

Check the computing power requirements (architecture and frequency of the device) and estimate the magnitudes of each task —how long and often the task will need to run. Watchdog timers are a key feature to look in MCUs as they help to recover from failure situations, resetting the device as soon as it detects is unresponsive.

 

3- Identify the needed memory.

Estimate how much Flash, RAM, and ROM are needed for the application to perform correctly, using the software architecture and the communication peripherals, identifying which kind of memory interfaces the application will require; making sure the solution will not run out of the program or variable space. Also, leave room for future upgrades and next versions.

 

4- Check the Power Constraints.

Review the external voltage supply and current loads the device will power from to avoid malfunction. Double-check if the parts need to be low-power or not and the operational voltage levels of all components to decide how many source powers are needed.

 

5- Consider Functional Safety and Security reliability.

Analyze the electrostatic discharges, electro migrations, and electrical ground conditions and levels to increase robustness and safety levels against failures, as electrical connections in automotive environments can be physically quite long (because of how ECUs and equipment are positioned) drawing relatively large current, in addition to the parasitic noise generated.

 

6- Check the enhanced features.

Ease the development process by using the embedded MCU features, such as Zero Point Detection (ZPD) for automotive instrument cluster applications or Quad Position and Revolution Counter (QPRC) to implement jog-dial functions for audio and navigation applications. Check if the MCU has built-in software flexibility too for relocating internal modules to a different set of pins to increase flexibility during the PCB layout process. In another hand, some MCUs and MPUs have Graphic Processing Unit (GPU) dedicated to managing image processing and camera interfaces. Also look for Neural Network, Machine Learning capabilities, and Sensor Fusion too for leveraging Artificial Intelligence in your solution.

 

7- Study the Enablement for the MCU or MPU.

Solidify the choice of the device by mapping all available development kits, example codes, and documentation, but also compilers and debugging tools to ease the development process. Complete tool sets are usually offered for free and can be used for development processes and production intent.

 

8- Search for the right MCUs.

Use all above required features to check MCU or MPU options between suppliers and chipmakers. If available, get better advice from a support representative or FAE.

 

9- Confirm Prices and Availability.

Examine the piece cost of the device and how it will impact the overall price of the solution. Confirm how available the part is, the stocking options, and leading times (usually 6-12 weeks). Also, double check the part longevity program from the manufacturer to match the product lifecycle. Some manufacturers have roadmaps for new MCUs and MPUs available that support representatives or FAE can share.

 

 

Once you get your samples and start experimenting with the MCU or MPU, is always a good idea to test circuits and interfaces with the device, choosing high-risk parts and get them to work on the development kit. Trying out software and code variations to validate performance and ensure the selected MCU or MPU is right for your design.

  • Sign in to reply

Top Comments

  • michaelkellett
    michaelkellett over 7 years ago +2
    As is common with short articles of this kind one of the most important factors is not mentioned - the scale or planned production volume. I work on projects where the planned production volume may be…
  • michaelkellett
    michaelkellett over 7 years ago in reply to yoSoyTono

    It's good that your own MATLAB interfacing bits are not chargeable.

     

    If only the Mathworks was able to offer its xx-Coder products at a lower price.

     

    MK

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • yoSoyTono
    yoSoyTono over 7 years ago in reply to michaelkellett

    Hi Michael,

    Your insights about low-volume vs high-volume development end cost are totally right; definitely, engineers need to consider the volume as well to define the right devices to use depending on their case.

     

    About the tool sets, please note all the MATLAB toolboxes that NXP offers are free-of-charge, both NXP Software Development Kit (SDK) and NXP Compilers. I know you might argue the evaluation hardware (boards and shipping) can be costly, but NXP has really cheap development boards and evaluation kits. In the case of NXP Model-Based Design Toolboxes, all the support is also free-of-cost on their incredible and useful engineering community.

    I agree as well the tools from Mathworks (like MATLAB, Simulink, Matlab Coder, Simulink Coder, or Embedded Coder) need to be licensed, but they might have not an associated cost —depending on the customer/company history, as you pointed.

     

    Thank you for reading!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • michaelkellett
    michaelkellett over 7 years ago

    As is common with short articles of this kind one of the most important factors is not mentioned - the scale or planned production volume.

    I work on projects where the planned production volume may be 1 (as in a special purpose tester), a few hundred or, occasionally a few hundred thousand.

     

    At the low volume end the cost of development  will be far greater than the cost of parts so an important concern is familiarity, it will be far cheaper to design with a part you or your company has used before and has tools (and maybe code) for.

     

    Only at the high volume end will the choice be driven almost entirely by the component itself -and even then 'political' considerations like preferred suppliers may come into play.

     

    There is a comment in 7 with which I would very strongly disagree - in my experience there is no such thing as a free lunch and a "complete tool set" is a very big lunch indeed. A complete tool set will come with a price tag (which may be HUGE if you include things like Model Based Design) , it won't all come form the processor supplier and it won't be free.

     

    MK

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • yoSoyTono
    yoSoyTono over 7 years ago

    NXP has an Automotive MCUs and MPUs Product Map to ease finding and selecting the right Microcontroller or Microprocessor for your industrial and automotive design. Its latest version includes both software and hardware enablement, covering most of the above insights!

     

    Check the Automotive MCU and MPU Product Map and avoid unnecessary MCU/MPU hurdles!

    image

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube