Introduction / Context:
Early and many classic microprocessor systems rely on external memory ICs. Program code must live somewhere nonvolatile, and temporary data, stacks, and variables require RAM. This question asks if at least ROM/EPROM and RAM are needed in a minimal, practical design.
Given Data / Assumptions:
- We are considering general-purpose microprocessors (not self-contained microcontrollers).
- Program code must persist across power cycles (ROM/EPROM/Flash).
- Runtime data storage (stack, variables, buffers) needs RAM.
Concept / Approach:
A microprocessor typically lacks on-chip program and data memory (unlike many microcontrollers). The standard approach is to connect external nonvolatile memory for code and RAM for read/write storage. Even simple monitor programs and I/O routines require this split unless you boot from an on-chip ROM (which microprocessors generally do not provide).
Step-by-Step Solution:
Define the roles: nonvolatile for code, volatile for data/stack.Identify external memory buses in common microprocessors (address, data, control).Recognize that typical boot requires code fetch from ROM/EPROM/Flash.Conclude that at least one ROM/EPROM and one RAM device are required in a basic system.
Verification / Alternative check:
Reference evaluation boards for 8085/8086/6800-class devices: they include separate ROM and RAM ICs.
Why Other Options Are Wrong:
Incorrect: Would ignore the need for persistent code storage or working RAM.Applies only to Harvard-architecture CPUs: The need arises from external memory absence, not the Harvard/Von Neumann split.Valid only when interrupts are disabled: Interrupts are unrelated to basic memory requirements.
Common Pitfalls:
Confusing microprocessors with microcontrollers; the latter often integrate Flash and RAM on-chip.Assuming ROMless boot with serial loaders; you still need RAM to execute and code storage somewhere persistent.
Final Answer:
Correct
Discussion & Comments