Unit
- Embedded system definition: A specialized computing system designed to perform dedicated functions within a larger mechanical or electrical system. Unlike general-purpose computers, these systems have constrained resources, real-time requirements, and are often deployed in harsh environments without user intervention.
- Firmware role: The software layer that directly interacts with hardware registers and peripherals. Firmware reads sensor data, controls actuators, manages communication protocols, and implements the core logic of the embedded product. It typically runs on microcontrollers (MCUs) with limited memory and processing power.
- Categories of embedded systems: Real-time systems where timing is critical (anti-lock brakes), event-driven systems that respond to external triggers (keyboard), and batch processing systems that collect data over time (environmental logger). Each category imposes different design constraints on the firmware.
- Key characteristics: Deterministic execution, low power consumption, reliability over long lifetimes, small memory footprint, and often no operating system. Firmware engineers must balance performance, memory usage, and power to meet product specifications.
- Common microprocessors and microcontrollers: ARM Cortex-M (M0, M3, M4), AVR (Arduino), PIC, RISC-V, and proprietary cores from manufacturers like TI, NXP, and STMicroelectronics. The choice depends on cost, performance, peripheral set, and ecosystem support.
- Development environment components: Cross-compiler (GCC for ARM), linker script to define memory layout, debugger/programmer (J-Link, ST-Link), and IDE (Keil, IAR, or VS Code with PlatformIO). For this course we focus on GCC-based toolchains due to their open-source nature.
- Firmware vs. software engineering: Firmware code must account for memory-mapped registers, interrupt latency, and hardware errata. Unlike application software, firmware cannot assume a stable OS or virtual memory. Every memory access can have side effects, making careful use of
volatileand memory barriers essential. - Safety and reliability: Many embedded systems are safety-critical (medical devices, automotive). Firmware must implement watchdog timers, ECC (error-correcting code) for memory, and fail-safe states. Industry standards like ISO 26262 (automotive) and IEC 62304 (medical) mandate rigorous testing and documentation.
- Boot process and startup code: The MCU executes a reset vector, initializes the stack pointer, and runs startup code that copies initialized data from flash to RAM, zeros BSS, and calls
main(). Understanding this sequence is critical for debugging early boot failures and managing memory layout. - Memory types and their roles: Flash memory stores code and constant data; RAM holds variables, stack, and heap; EEPROM or backup SRAM retains configuration across resets. Firmware engineers must manage these memory regions with care, especially when using linker scripts to define code and data placement for optimal performance and reliability.
- Interrupt handling fundamentals: Interrupts allow the CPU to respond to external events asynchronously. The firmware must configure the NVIC (Nested Vector Interrupt Controller), set interrupt priority, and write Interrupt Service Routines (ISRs) that are short and non-blocking. Proper use of volatile and critical sections prevents race conditions.
- Communication protocols in embedded systems: Common serial protocols include UART for debug logging, I2C for sensors and EEPROMs, and SPI for high-speed peripherals like displays and ADCs. Firmware must handle clock generation, data framing, and error checking. Writing low-level drivers to abstract hardware details is a common task for firmware engineers.
Code Example
C
// Simple firmware skeleton for STM32F4
#include 'stm32f4xx.h'
void delay(volatile uint32_t count) {
while (count--) { __NOP(); }
}
int main(void) {
// Enable GPIO clock for Port D
RCC->AHB1ENR |= RCC_AHB1ENR_GPIODEN;
// Configure PD12 as output (LED)
GPIOD->MODER |= (1 while (1) {
GPIOD->ODR ^= (1 delay(500000);
}
}This example toggles an LED by directly manipulating the GPIO output data register (ODR). The MODER register sets the pin mode to output. The delay loop is a simple busy-wait; production code would use a timer interrupt for efficiency.
Quick Revision
- Embedded systems are dedicated, resource-constrained computing platforms with real-time requirements.
- Firmware directly interfaces with hardware registers and peripherals.
- Key characteristics include deterministic execution, low power, and high reliability.
- Development uses cross-compilation and specialized toolchains like GCC for ARM.
- Safety-critical firmware must follow standards such as ISO 26262 and IEC 62304.