An instruction cycle (sometimes called fetch-decode-execute cycle) is the basic operation cycle of a computer. It is the process by which a computer retrieves a program instruction from its memory, determines what actions the instruction requires, and carries out those actions. This cycle is repeated continuously by the central processing unit (CPU), from bootup to when the computer is shut down.
In simpler CPUs, the instruction cycle is executed sequentially: each instruction is completely processed before the next one is started. In most modern CPUs, the instruction cycle is instead executed concurrently in parallel, as an instruction pipeline: the next instruction starts being processed before the previous instruction is finished, which is possible because the cycle is broken up into separate steps.
- Program counter (PC) - an incrementing counter that keeps track of the memory address of the instruction that is to be executed next or in other words, holds the address of the instruction to be executed next.
- Memory address register (MAR) - holds the address of a memory block to be read from or written to.
- Memory data register (MDR) - a two-way register that holds data fetched from memory (and ready for the CPU to process) or data waiting to be stored in memory. (This is also known as the memory buffer register (MBR).)
- Instruction register (IR) - a temporary holding ground for the instruction that has just been fetched from memory.
- Control unit (CU) - decodes the program instruction in the IR, selecting machine resources such as a data source register and a particular arithmetic operation, and coordinates activation of those resources.
- Arithmetic logic unit (ALU) - performs mathematical and logical operations.
Each computer's CPU can have different cycles based on different instruction sets, but will be similar to the following cycle:
- Fetching the instruction: The next instruction is fetched from the memory address that is currently stored in the program counter (PC), and stored in the instruction register (IR). At the end of the fetch operation, the PC points to the next instruction that will be read at the next cycle.
- Decode the instruction: During this cycle the encoded instruction present in the IR (instruction register) is interpreted by the decoder.
- Read the effective address: In case of a memory instruction (direct or indirect) the execution phase will be in the next clock pulse. If the instruction has an indirect address, the effective address is read from main memory, and any required data is fetched from main memory to be processed and then placed into data registers (Clock Pulse: T3). If the instruction is direct, nothing is done at this clock pulse. If this is an I/O instruction or a Register instruction, the operation is performed (executed) at clock Pulse.
- Execute the instruction: The control unit of the CPU passes the decoded information as a sequence of control signals to the relevant function units of the CPU to perform the actions required by the instruction such as reading values from registers, passing them to the ALU to perform mathematical or logic functions on them, and writing the result back to a register. If the ALU is involved, it sends a condition signal back to the CU. The result generated by the operation is stored in the main memory, or sent to an output device. Based on the condition of any feedback from the ALU, Program Counter may be updated to a different address from which the next instruction will be fetched.
The cycle is then repeated.
Initiating the cycle
The cycle starts immediately when power is applied to the system using an initial PC value that is predefined for the system architecture (in Intel IA-32 CPUs, for instance, the predefined PC value is
0xfffffff0). Typically this address points to instructions in a read-only memory (ROM) (not the random access memory or RAM) which begins the process of loading the operating system. (That loading process is called booting.) 
Fetch the Instruction
Step 1 of the Instruction Cycle is called the Fetch Cycle. This step is the same for each instruction.
1) The CPU sends PC to the MAR and sends a READ command on the control bus
2) In response to the read command (with address equal to PC), the memory returns the data stored at the memory location indicated by PC on the databus.
3) The CPU copies the data from the databus into its MDR (also known as MBR (see section Circuits Used above))...
4) A fraction of a second later, the CPU copies the data from the MDR to the Instruction Register (IR)
5) The PC is incremented so that it points to the following instruction in memory. This step prepares the CPU for the next cycle.
The Control Unit fetches the instruction's address from the Memory Unit
Decode the Instruction
Step 2 of the instruction Cycle is called the Decode Cycle. The decoding process allows the CPU to determine what instruction is to be performed, so that the CPU can tell how many operands it needs to fetch in order to perform the instruction. The opcode fetched from the memory is decoded for the next steps and moved to the appropriate registers. The decoding is done by the CPU's Control Unit.
Read the effective address
Step 3 is deciding which operation it is. If this is a Memory operation - in this step the computer checks if it's a direct or indirect memory operation:
- Direct memory instruction - Nothing is being done.
- Indirect memory instruction - The effective address is being read from the memory.
If this is a I/O or Register instruction - the computer checks its kind and executes the instruction.
Execute the Instruction
Step 4 of the Instruction Cycle is the Execute Cycle. Here, the function of the instruction is performed. If the instruction involves arithmetic or logic, the Arithmetic Logic Unit is utilized. This is the only stage of the instruction cycle that is useful from the perspective of the end user. Everything else is overhead required to make the execute stage happen.
- Bosky Agarwal (2004). "Instruction Fetch Execute Cycle" (PDF). Retrieved 2012-10-14.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>