Internal hardware components of a computer — AQA A-Level Computer Science
Internal hardware components encompass the central processing unit (CPU), system buses, and primary storage that collectively execute instructions via the fetch-execute cycle. In AQA A-Level Computer Science, mastery requires understanding the precise interactions between internal processor registers, the control unit, the arithmetic logic unit, and the tri-bus architecture.
Internal hardware components of a computer explained
I/O controllers are hardware components that manage the communication between the CPU and input/output devices such as keyboards, printers, disk drives and network adapters.
Read the full explanation
Each device or group of devices typically has an I/O controller, which acts as an interface: it translates signals between the device's own format and the format used on the system buses, buffers data so that speeds can differ, and handles the signals needed to start, monitor and stop an operation. Because I/O devices are usually much slower than the CPU, the controller allows the processor to continue other work while data is transferred, often generating an interrupt when the operation completes. A useful way to explain this is to describe a printer controller that receives a print job from the CPU, stores it in a buffer, drives the printer mechanism, and signals the CPU when the job is finished.
Your focus
- I/O controllers.
Which command word is this?
Give a detailed, factual account of a mechanism or process (e.g. describe the role of the CIR during decoding) without needing to evaluate pros and cons.
Internal hardware components of a computer exam tips
Topic Overview
Internal hardware components form the computational core of a computer system, consisting of the Central Processing Unit (CPU), internal memory structures, and the system buses that connect them. Understanding these components requires analyzing how the Control Unit, Arithmetic Logic Unit, and dedicated registers coordinate instruction execution at the machine level.
This topic forms the fundamental bridge between low-level hardware design and high-level software execution in AQA A-Level Computer Science. Mastering processor architecture, the tri-bus system, and the differences between Von Neumann and Harvard models provides the essential foundation for subsequent units on assembly language, operating systems, and systems architecture.
Key Concepts
- →Processor Components: The Control Unit (orchestrates instruction execution and generates control signals), the ALU (performs arithmetic and logical bitwise operations), and the System Clock (synchronises internal operations).
- →Special-Purpose Registers: Program Counter (PC), Memory Address Register (MAR), Memory Data Register (MDR/MBR), Current Instruction Register (CIR), and the Accumulator (ACC).
- →The Tri-Bus Architecture: The system bus consists of three distinct transmission pathways: the unidirectional address bus, the bidirectional data bus, and the bidirectional control bus.
- →Architectural Models: Von Neumann architecture shares a single memory space and bus system for both instructions and data; Harvard architecture uses physically separate memories and buses for instructions and data.
- →Factors Affecting Performance: Clock speed, cache size and level (L1/L2/L3), number of physical cores, and word size/bus width.
Marking Points
- Defines an I/O controller as hardware that manages communication between the CPU and an input or output device
- Explains that the controller acts as an interface, translating signals between the device and the system buses
- Explains that the controller can buffer data to cope with the speed difference between the CPU and a device
- Gives an example such as a printer or disk controller and describes what it does for that device
Examiner Tips
- 💡Define the controller as an interface between a device and the system before giving any detail
- 💡Use one named example such as a printer controller to show the sequence of actions
- 💡Mention buffering explicitly when speed mismatch is relevant, as it is a key idea examiners look for
- 💡When explaining the fetch-execute cycle, use precise register abbreviations (PC, MAR, MDR/MBR, CIR) and refer explicitly to which bus transmits the address, data, or signal at each step.
- 💡Remember that data bus width determines word length and data transfer speed, while address bus width determines the maximum direct addressable memory capacity.
- 💡In comparison questions regarding Von Neumann versus Harvard architectures, always link your technical points to real-world applications, such as DSP audio processing versus general-purpose computing.
Common Mistakes
- Describes an I/O controller as the device itself, such as calling the keyboard the controller; correct it by stating the controller is the interface hardware between the device and the system
- Says the controller stores all program instructions; correct it by stating its role is managing input and output transfers, while programs are held in main memory
- States that the controller removes the need for the CPU to be involved at all; correct it by noting the controller often signals the CPU with an interrupt when an operation completes
- Believing that doubling the number of CPU cores automatically doubles overall processing speed, ignoring serial dependencies, inter-core communication overhead, and Amdahl's Law.
- Assuming the Harvard architecture is completely obsolete, whereas it is actively used in Digital Signal Processors (DSPs), embedded microcontrollers, and modern CPU split L1 caches.
- Confusing the Current Instruction Register (CIR) with the Program Counter (PC), failing to realise that the CIR holds the instruction currently being decoded, while the PC holds the address of the next instruction.
Revision Plan
- 1Step 1: Memorise the role and abbreviation of every CPU register and practice tracing their contents through the fetch-execute cycle using Register Transfer Notation.
- 2Step 2: Create a comparative table of the three system buses outlining their function, directionality, and typical control signals (e.g. Memory Read, Memory Write, Interrupt, Clock).
- 3Step 3: Contrast Von Neumann and Harvard architectures, focusing on the 'Von Neumann bottleneck' and Harvard's concurrent instruction-data access advantage.
- 4Step 4: Solve past paper calculation questions involving address bus width to memory capacity conversions and 6-to-9 mark architecture evaluation questions.
Exam Question Types
- 📋Register Transfer Notation / F-E Cycle Tracing: Step-by-step descriptions of register operations during the fetch, decode, or execute phase.
- 📋Bus Width and Addressing Calculations: Mathematical problems requiring you to compute addressable storage based on address bus lines or transfer throughput from data bus width.
- 📋Comparative Essay Questions (6 to 9 marks): Detailed evaluations comparing Von Neumann and Harvard architectures, or evaluating processor upgrade scenarios.
Command Word Expectations (AQA)
Give a detailed, factual account of a mechanism or process (e.g. describe the role of the CIR during decoding) without needing to evaluate pros and cons.
Clarify causes and effects, stating why a hardware feature exists and how it works (e.g. explain why the address bus width limits primary memory capacity).
Identify specific structural and functional similarities and differences between two components or architectures (e.g. compare Harvard and Von Neumann systems).
How Students Lose Marks (Examiner Pitfalls)
Step-by-Step Worked Solutions
Question: Describe the fetch stage of the fetch-execute cycle using Register Transfer Notation (RTN) and describe the state of the Program Counter at the end of this stage.
- 1.Step 1: Identify the initial step where the address of the next instruction is copied from the Program Counter to the Memory Address Register: MAR <- [PC].
- 2.Step 2: Show the simultaneous or subsequent increment of the Program Counter to point to the next consecutive memory address: PC <- [PC] + 1.
- 3.Step 3: Show the retrieval of the memory contents located at the address in MAR into the Memory Buffer/Data Register via the data bus: MBR <- [[MAR]].
- 4.Step 4: Show the instruction being loaded into the Current Instruction Register from the MBR for decoding: CIR <- [MBR].
- 5.Step 5: Conclude the state of the Program Counter: it now holds the memory address of the instruction following the one currently copied to the CIR.
Question: A processor has a 36-bit address bus and a 64-bit data bus. Calculate the maximum directly addressable memory capacity in GiB (Gibibytes), and explain the architectural benefit of having a 64-bit data bus over a 32-bit data bus.
- 1.Step 1: Determine total addressable memory locations: 2^36 addresses.
- 2.Step 2: Assume standard byte addressing (1 address = 1 byte): 2^36 bytes.
- 3.Step 3: Convert bytes to GiB by dividing by 2^30: 2^36 / 2^30 = 2^(36-30) = 2^6 = 64 GiB.
- 4.Step 4: Analyse the data bus width benefit: A 64-bit data bus transmits 8 bytes per clock transfer, compared to 4 bytes for a 32-bit bus.
- 5.Step 5: Conclude the architectural benefit: The increased bus width doubles the data throughput between primary memory and the processor per transfer, reducing memory bottlenecking.