8.5.1. Memory-Mapped I/O

These peripherals are often memory-mapped into the processor’s address space, enabling the CPU to control and interact with them through standard memory read/write operations.

Memory-mapped I/O is a technique used to integrate peripherals with the CPU's address space. By memory-mapping, the CPU can interact with external devices as if they were regular memory addresses. This means that when the CPU reads or writes to a specific address, it can communicate with peripherals instead of traditional memory. For example, writing to a specific address might turn on an LED connected to a GPIO pin.

Think of memory-mapped I/O like a remote control for your television. Instead of directly manipulating each button, when you press a button, a specific signal is sent that corresponds to the action you want to perform (like changing the channel). Similarly, the CPU sends signals to specified address locations which then control the connected peripherals.

The AHB bus ensures high-speed, low-latency data transfer between the processor and peripherals. For example, writing data to the GPIO register turns on or off specific pins, and writing to the timer register starts or stops the timer.

The AHB, or Advanced High-performance Bus, is designed to provide fast and efficient communication between the CPU and peripherals. This bus allows multiple devices to communicate with the processor simultaneously, reducing latency. When the CPU needs to control an output device, like turning an LED on or off, it writes a value to the GPIO register via the AHB. The AHB's speed allows for quick responses to control commands, which is crucial in real-time applications.

Imagine AHB as a highway where multiple cars (data packets) can travel at high speeds. Each car represents a command the CPU is sending to control a device (like turning on an LED). The more lanes (data paths) there are on the highway, the more cars can travel at once, making it quicker for all messages to reach their destinations.

Each of these peripherals (timers, GPIO, and 7-segment displays) can generate interrupts to notify the CPU of events such as the expiration of a timer or a change in input on the GPIO pin.

Interrupts are a key feature that allows peripherals to alert the CPU of important events. When a peripheral like a timer reaches a certain count, it generates an interrupt, signaling the CPU to pause its current task and handle the timer event. Similarly, if the state of a GPIO pin changes (like a button is pressed), an interrupt notifies the CPU that it needs to respond to this input. This mechanism ensures that critical events are addressed promptly, providing a responsive user experience in embedded systems.

Think of interrupts as doorbells. When someone presses your doorbell (the event), it signals you (the CPU) to stop what you are doing and answer the door. Likewise, interrupts let the CPU know that something needs its immediate attention, allowing it to react quickly to changing conditions.

--