Subtopic 3 of 7
7.3ROM family
The idea
The ROM family is read-mostly memory that keeps data without power, differing in how easily it can be rewritten.
Think of it like this: A printed book (ROM), a book you write in once (PROM), a book you can erase with a lamp (EPROM), with an eraser (EEPROM).
Why it exists
Firmware and boot code must survive power-off.
How it works
- ROM: programmed at manufacture.
- PROM: programmed once by the user.
- EPROM: erased by UV light, whole chip.
- EEPROM: erased electrically, byte by byte. Flash: erased by block.
Worked example: USB stick, SSD
Both use Flash.
Now play with it
- →Step through the five levels.
ROMmask-programmed
PROMone-time
EPROMUV erase
EEPROMbyte erase
Flashblock erase
- ROM: contents fixed at the factory, cheapest in volume
- PROM: user programs it once (fuses blown)
- EPROM: erase the whole chip with UV light, reprogram
- EEPROM: erase and write individual bytes electrically, in place
- Flash: electrically erased in blocks, dense and cheap (SSD, USB sticks)
Read-only family: how easily can the contents be changed?
Check yourself
Which can be erased electrically one byte at a time?
Remember: ROM < PROM < EPROM < EEPROM < Flash in rewrite flexibility.
Exam notes (the dense version)
ROM, PROM, EPROM (UV erase), EEPROM, Flash (block erase).
Previous year questions: Memory Hierarchy & Main Memory (16)
PYQs are grouped by topic, so this is the full set for Memory Hierarchy & Main Memory; try the ones that match this subtopic. Open all 16 on the topic page.