ROM terminology: What is the common term for the process of entering or installing data/patterns into a ROM device (especially a PROM), as performed with a programmer?

Introduction / Context:
Read-Only Memories (ROMs) come in several forms: mask-programmed at the factory, one-time programmable PROMs, and erasable devices. The act of placing data into a PROM or EPROM with an external programmer is commonly referred to in industry shorthand as “burning” a ROM image, even though modern devices are not literally burned. Understanding the lingo helps when reading legacy documentation and tool instructions.

Given Data / Assumptions:

• We refer to user programming of PROM/EPROM/EEPROM with a device programmer.
• Colloquial yet widely used terminology is acceptable.
• Mask ROM (MROM) is programmed during fabrication and is not field-programmable.

Concept / Approach:
Entering data into a user-programmable ROM has long been called “burning” a ROM. While “programming” is the formal term, technician and manufacturing vernacular often uses “burn,” “ROM burn,” or “burn-in.” Note that strict reliability engineering uses “burn-in” to mean stress testing components; however, many exam contexts accept “burning” or “burning in” to mean programming a PROM. Among the provided choices, “burning in” best matches the intended meaning.

Step-by-Step Solution:

Verification / Alternative check:
Legacy EPROM/EEPROM programmer manuals describe the operation as programming/burning a device with a HEX image. Mask ROMs, by contrast, are defined at fabrication via masks, not burned by the user.

Why Other Options Are Wrong:
Configuration and addressing are operational behaviors, not the one-time image write step. Internal decoding is a ROM’s architectural feature. Masking at fabrication applies to MROM, not field programming.

Common Pitfalls:
Confusing “burn-in” (reliability stress) with “burning” a ROM. Despite the overlap, exam contexts frequently use “burning” to mean programming PROM/EPROM.

Final Answer:
Burning in