ROM

ROM stands for read-only memory, a type of semiconductor storage that retains data even when power is disconnected. Unlike RAM, which loses all contents when the machine shuts down, ROM holds its contents indefinitely because the data is physically hardwired into the chip during manufacturing. This makes ROM ideal for storing firmware, boot code, and other critical instructions that a device needs the moment it powers on.

The oldest ROM variants used a mask during the silicon fabrication process to set each bit permanently. This method remains common in high-volume production because the per-unit cost is very low, but it requires long lead times and cannot be changed after chips leave the factory. Later variants like EPROM (erasable programmable ROM) and EEPROM (electrically erasable programmable ROM) introduced rewritability at the cost of slower access and higher unit prices. EEPROM in particular became standard for devices that need firmware updates in the field without replacing hardware.

Flash memory, which emerged in the 1980s, is a type of non-volatile semiconductor storage closely related to EEPROM but with much faster read and write speeds and higher density. Modern embedded systems, microcontrollers, and consumer devices typically use Flash rather than traditional ROM because it offers the permanence of ROM with far more flexibility. The term ROM persists in industry parlance even though hardware engineers often mean Flash when they refer to ROM storage in contemporary designs.

On a typical microcontroller or SoC, ROM occupies a fixed portion of the addressable memory space. The CPU can read from ROM at the same speed as from RAM, but write operations are either impossible or require special unlock sequences. Access time for ROM is typically a few nanoseconds, matching or sometimes exceeding that of cached RAM, so the read-only limitation does not create a performance bottleneck for stored constants or code.

Common failure modes in ROM-based systems are rare because the data is static, but problems arise when the wrong firmware is programmed at manufacture or when a design requires mid-life updates that the mask ROM cannot accommodate. Engineers must verify content exhaustively before committing to a mask ROM run, since recalls are costly. This constraint has driven adoption of reprogrammable alternatives for nearly all new designs except very high-volume commodity products where the tooling investment justifies the inflexibility.