Lesson 2 — Beginner

Von Neumann Architecture

Aaj ke har computer ka base Von Neumann architecture hai — jismein program aur data dono ek hi memory mein rehte hain. Is lesson mein hum dekhenge stored program concept kya hai, fetch cycle kaise chalta hai, registers kya karte hain, aur Harvard architecture se kya farak hai.

⏱ 14 min• Beginner• Introduction

Stored program concept

WHAT

Von Neumann architecture ka core idea — instructions (program) bhi data ki tarah usi memory mein store hote hain, same format mein. CPU ko bas address do, wo instruction bhi utha lega, data bhi. Isse program badalna = sirf memory mein naya likhna, hardware nahi badalna.

WHEN

Computer on hote hi boot program memory se hi chalta hai. Naya app install karte hi wo memory mein load hota hai aur chalne lagta hai — ye sab isi concept se possible hai.

WHERE

Har laptop, phone, server isi architecture par chalta hai. Pehle computers (ENIAC ke baad) mein aaya aur aaj bhi x86/ARM ka foundation yahi hai.

Pehle ke computers mein program badalne ke liye wiring dobara badalni padti thi. Von Neumann ne kaha — program ko bhi memory mein likh do, CPU usi tarah padh lega jaise data padhta hai. Isi se software ka concept janma.

Yaad rakho: Von Neumann ka ek hi memory hai — instructions aur data dono ke liye. Iska side effect hai Von Neumann bottleneck: dono ko ek hi bus se jaana padta hai, isliye instruction fetch aur data access compete karte hain.

Fetch-decode-execute cycle

Step 1 FETCH : PC ka address → MAR (Memory Address Register)
                Memory read → data MDR mein → IR (Instruction Register)
                PC = PC + 1 (agle instruction ki taraf)
Step 2 DECODE: Control Unit IR ka opcode padhta hai — kya karna hai
Step 3 EXECUTE: ALU/CU instruction perform karta hai
                (add, load, jump — jaisa opcode bole)
Step 4 RESULT: Result register ya memory mein store

Ye cycle clock ke saath baar baar chalta hai — GHz = billions cycles/sec
Interview gold: PC = future (next address), IR = present (current instruction), MAR/MDR = memory ke gatekeeper. Ye charon ke kaam har interview mein ek na ek baar zaroor aate hain.

Von Neumann ka structure — kya kaise judta hai

Major components :
1. CPU (CU + ALU + Registers)
2. Main Memory (instructions + data)
3. Input / Output devices
4. Bus system : address bus (one-way) + data bus (two-way) + control bus

Data flow (instruction ke liye) :
  PC → MAR → [Bus] → Memory → MDR → IR → Decode → Execute

Control flow :
  CU decide karta hai kab memory read, kab write, kab ALU op —
  ye control signals CONTROL BUS pe jaate hain

In sabka matlab: har cheez bus ke through ek doosre se baat karti hai. CPU seedhe memory ko unplug karke nahi poochta — address bus pe address jaata hai, control bus pe "padho/likho" ka signal jaata hai, data bus se data aata jaata hai.

Memory ko do tarike se access kar sakte ho — byte-addressable (har byte ka apna address, aaj kal standard) aur word-addressable (har word ka ek address, purane systems). Numericals mein address calculation isi par depend karta hai.

Von Neumann vs Harvard architecture

Parameter     | Von Neumann            | Harvard
--------------+------------------------+-------------------
Memory        | ek hi (shared)         | alag (instr + data)
Buses         | ek shared bus set      | alag buses
Fetch speed   | instruction aur data   | dono ek saath
              | turn se chalte hain    | fetch ho sakte hain
Cost          | sasta, simple          | zyada wires, mehnga
Use           | general purpose CPUs   | DSP, microcontrollers,
              | (PC, laptop)           | embedded (8051, ARM
              |                        | ke kuch cores)

Von Neumann bottleneck : ek hi memory-bandwidth par
  instruction bhi jaana, data bhi — isliye pipeline chadhne pe
  do ports ya split cache (L1I + L1D) banaye jaate hain
Exam trap: Question: "Harvard architecture mein program kahan store hota hai?" — alag instruction memory mein, data wali alag. Trap option: "program memory mein nahi hota" — galat, program bhi memory mein hota hai bas ALAG memory mein.

Aaj kal ke processors practical mein donon ka mix chalte hain — bahar se shared RAM (Von Neumann), andar se caches split (Harvard). Isliye donon concepts jaanna zaroori hai.

Exercise

Question: Instruction aur data ke liye alag-alag memory use karne wala architecture konsa hai? (von neumann / harvard)

Question: Fetch-decode-execute ke teeno steps comma se, order mein (fetch, decode, execute).

Question: MDR mein kya aata hai — memory ka address ya data?

Common mistakes

Desi example: Dhaba ka khana-banane wala cycle

Dhaba ki almari mein recipe bhi rakhi hai aur ingredients bhi — ek hi jagah (stored program). Har order pe wahi cycle chalta hai:

text
Fetch   : recipe uthai (next order ki)
Decode  : samjha kya banana hai
Execute : pakaya (ALU/CU ne)
Repeat  : agla order — tezi se
Almari = memory : recipe (program) + ingredients (data), dono ek jagah
Exam mapping (GATE / TCS / UGC)
  • GATE: PC/MAR/MDR/IR ke functions par short question aksar aata hai.
  • UGC-NET: "Stored program concept" ka inventor ya meaning poochha jaata hai.
  • TCS NQT: Von Neumann vs Harvard — classic difference question.
  • Trap: "PC stores current instruction address" — galat, woh IR/PC ka farak hai.
Lesson complete?

Von Neumann ka structure clear. Agla lesson — Instruction Set Architecture (ISA) — mein dekhenge CPU ko chalane wale instructions ka poora khel.

Popular courses: Data Science Course in Lucknow · AI Course in Lucknow · Python Course in Lucknow · Power BI Course · Data Analytics Course