QUICK ANSWER
A microcontroller does one job and does it reliably. The CPU fetches instructions stored in on-chip flash memory, while RAM holds the runtime data the program needs at any given moment. Built-in peripherals, including timers, analog-to-digital converters (ADCs), and communication interfaces such as UART, SPI, and CAN, handle input and output tasks without burdening the CPU. Unlike a general-purpose processor that depends on external chips for memory and I/O, the MCU integrates compute, memory, and connectivity on a single device, reducing board area, power draw, and bill-of-materials cost.

what is microcontroller

Figure 1. Internal architecture of a microcontroller, showing the CPU core, flash and RAM memory, peripheral modules, and I/O connections to external sensors and actuators. Infineon Technologies AG.

How a microcontroller works and what it does

At its core, a microcontroller runs a continuous sequence: fetch an instruction from flash memory, decode it, execute it, then move on to the next. This fetch-decode-execute cycle repeats millions of times per second, governed by the CPU's clock signal. The firmware, the program the engineer writes and loads to the device, is stored permanently in non-volatile flash, so the MCU starts executing its task the instant power is applied. No operating system startup, no boot loader delay; just the code and the hardware working in step.

Peripherals are what transform a processor into a controller. Rather than constantly polling sensors or waiting idle for input, a well-designed MCU uses hardware interrupts: each peripheral generates an interrupt signal when it needs attention, briefly pausing the main program loop, handling the event in an interrupt service routine, and then returning execution to exactly where it left off. An ADC signals that a new voltage reading is ready; a timer fires at the end of a PWM period; a CAN controller raises a flag when a new message arrives on the bus. The CPU stays free for the control algorithm while the peripherals handle the I/O.

In control systems, timing is not a convenience; it is a design specification. A motor current loop must execute within microseconds; a safety monitor must detect a fault and respond before damage occurs. Microcontrollers meet this requirement through deterministic execution: given the same input, the same code path always takes the same number of clock cycles. This predictability is what makes the MCU the right choice for closed-loop control, where the gap between sensing and responding directly affects system stability, efficiency, and functional safety.

Think of the microcontroller as the nervous system of an embedded device. It reads signals from sensors over SPI or I2C, receives system-level commands over CAN or LIN, processes the data according to its control algorithm, and sends the appropriate response to actuators, displays, or other nodes on the network. In an automotive body control module, for example, a single MCU may simultaneously manage window-lift motors, seat heaters, and exterior lighting, each connected over a different interface and all coordinated in real time by the same processor core.

When not actively processing tasks, many microcontrollers can enter a low-power sleep mode to conserve energy, waking only when a timer expires or an external event occurs. Infineon's AURIX™ TC3xx family and TRAVEO™ T2G Body family include dedicated power-saving modes of this kind, making it possible to meet strict automotive energy budgets without sacrificing real-time responsiveness. If a fault occurs or a reset signal is received, the MCU restarts from the first instruction in program memory and resumes normal operation.

Types of microcontrollers

Microcontrollers are not a single category. They span a wide range of processing power, peripheral sets, and qualification levels. Understanding the type you need is the first step toward a well-matched design.

By processing architecture

A single-core microcontroller has one CPU that executes instructions sequentially. These devices are well suited to simple, low-power applications where cost and ease of development are the priorities.

Multi-core microcontrollers provide more than one CPU core, enabling multiple threads or processes to run simultaneously. This architecture handles demanding tasks, such as automotive sensor fusion or industrial motion control, that exceed the throughput of a single core. Infineon's AURIX™ family is a multi-core design, with up to six TriCore™ cores working in lockstep or independently to deliver both performance and functional safety.

Infineon's TRAVEO™ T2G Body High family is also a multi-core device, combining multiple Arm® Cortex®-M cores with display interface support and functional safety features. It is designed for automotive body electronics and instrument cluster applications where both real-time control and display rendering must run concurrently on separate cores.

Not sure which type fits your application? The [microcontroller selection guide] walks you through the decision, step by step.

Frequently asked questions

What is the difference between a microcontroller and a microprocessor?

The difference lies in integration. A microprocessor is a CPU alone, dependent on external chips for memory, storage, and input/output. A microcontroller integrates the CPU, flash memory, RAM, and peripherals onto a single chip, making it self-contained and purpose-built for one embedded application. A microprocessor typically runs a general-purpose operating system and handles many concurrent applications; a microcontroller runs fixed firmware that reads sensors, executes a control algorithm, and drives actuators.

Microcontrollers are classified by processing architecture, application domain, and processor core. By architecture, 8-bit MCUs suit simple, low-cost control tasks; 16-bit devices offer more memory and data-handling capacity; 32-bit MCUs support real-time operating systems, floating-point computation, and functional safety certification. By processor core, the Arm® Cortex®-M series is widely used in general-purpose and industrial designs, while Infineon's TriCore™ architecture in AURIX™ combines RISC, DSP, and real-time processing for demanding automotive applications.

Most microcontrollers operate at supply voltages between 1.8 V and 5 V. The exact range depends on the MCU family and process technology. Always verify the full voltage operating range, minimum startup voltage, and I/O voltage tolerance in the device datasheet before committing to a power architecture.

Yes. Purpose-built automotive microcontrollers are designed for safety-critical applications. Characteristics to look for include deterministic execution, redundant processing paths, built-in self-test, memory protection, and hardware safety management. Always verify the device qualification and functional safety documentation for the intended application.

Features of a microcontroller

The features of a microcontroller determine whether it fits your processing requirements, communication needs, and design constraints. Here is what each one means in practice.

Applications of a microcontroller

Microcontrollers are found in applications ranging from automotive safety systems to medical devices and renewable energy infrastructure. Common domains include:

  • Automotive body control: An MCU manages window lifts, seat motors, exterior lighting, and door locks from a single body control module over LIN and CAN networks.
  • Motor control: The MCU reads rotor position, calculates the voltage vector, and updates PWM outputs in real time.
  • ADAS and functional safety: Automotive-grade MCUs manage sensor fusion, safety monitoring, and emergency actuator commands.
  • Industrial automation and robotics: The MCU coordinates fieldbus communication, sensor sampling, actuator outputs, and programmed control logic.
  • IoT edge devices: Ultra-low-power MCUs run sensing, signal processing, and wireless protocol stacks on constrained energy budgets.
  • Medical devices: Microcontrollers acquire sensor data, execute control algorithms, and support portable or implantable designs.
  • Energy management: Smart meters, solar inverters, and efficient lighting systems use MCUs to monitor and control energy flows.

Choosing the right microcontroller

Selecting the right MCU depends on the specific requirements of your application. Work through these considerations before committing to a device.

  • Project requirements: Define the task first: sensor interface, motor control, IoT connectivity, or safety-critical control.
  • Processing power: Match bit width, clock speed, and acceleration features to the workload.
  • I/O pins and peripherals: Count GPIO pins, analog inputs, PWM outputs, and communication interfaces.
  • Memory: Estimate flash for firmware and RAM for runtime variables, buffers, and stack use.
  • Power source: For battery-powered designs, evaluate sleep modes, operating voltage, and wake-up time.
  • Clock speed: Balance processing performance against power consumption.
  • Physical size: Verify package and footprint compatibility with the PCB layout.
  • Operating temperature: Choose a rated range appropriate to the deployment environment.
  • Regulatory compliance: Verify applicable automotive, industrial, or medical requirements.
  • Supply availability: Confirm quantity, cost, and long-term product availability.

Microcontroller development tools and troubleshooting

A microcontroller is only as productive as its development ecosystem. Look for devices backed by an integrated development environment (IDE), a debugger, software libraries, and an active developer community. These resources reduce bring-up time and simplify troubleshooting when issues arise.

Infineon's AURIX™ family supports in-circuit emulators, JTAG and SWD debuggers, and dedicated development tools through AURIX™ Development Studio or AURIX™ Configuration Studio. Hardware abstraction layers and application frameworks further reduce the time from first power-on to running firmware.

Microcontroller vs. microprocessor

Microprocessors (MPUs) are designed for general-purpose computing. They rely on external chips for memory and I/O and run full operating systems handling many applications in parallel. Microcontrollers are built for dedicated control tasks in embedded systems, where integration, low power, deterministic timing, and cost-effectiveness are defining requirements.

See the full breakdown of when to use each: [Microcontroller vs microprocessor comparison]

Infineon microcontroller portfolio

Infineon offers a broad MCU portfolio spanning 32-bit devices, from automotive safety controllers to ultra-low-power industrial and IoT MCUs. The portfolio includes:

  • AURIX™: Automotive-qualified multicore microcontrollers for demanding embedded control applications and functional safety.
  • PSOC™ Automotive: Programmable system-on-chip devices integrating capacitive sensing for automotive HMI and smart-sensor applications, based on Arm® Cortex®-M cores.
  • TRAVEO™ T2G: Automotive microcontrollers designed for body electronics and cluster applications, with high connectivity, low-power operation, security, and multicore options.
  • PSOC™ 4 High Voltage: A one-chip automotive and industrial solution with high-voltage capability, analog front end, MCU, and connectivity for smart-sensor and battery-management designs.
  • PSOC™ Automotive Multitouch: Capacitive touch controllers for automotive touchscreens.
  • PSOC™: Programmable embedded system-on-chip solutions with programmable analog, digital, and interconnect resources, plus Infineon CAPSENSE™ capacitive sensing.
  • XMC™: A 32-bit MCU portfolio based on Arm® Cortex®-M cores for industrial motor control, power conversion, and IoT edge applications.
  • MOTIX™: System-on-chip solutions for motor control that integrate drive electronics and MCU functionality.
Explore AURIX™ automotive MCUs
Explore XMC™ industrial MCUs

Related content

 

Trademarks: AURIX™, XMC™, TRAVEO™, PSOC™, MOTIX™, TriCore™, and CAPSENSE™ are trademarks of Infineon Technologies AG. Arm®, Cortex®, and Helium™ are trademarks or registered trademarks of Arm Limited (or its subsidiaries). RISC-V® is a registered trademark of RISC-V International. All other trademarks are the property of their respective owners.