If an application requires additional RAM, or if the system design is frozen, but there is a need to implement additional functionality, what are the available options? An MCU with a large embedded RAM might be an option, but, since most MCUs are RAM constrained, this would probably mean a more expensive device. If a larger MCU is being considered just for extra RAM, the customer is probably paying for extra features and peripherals that are not needed. A larger MCU would also require more board space. For an existing design, this would mean redesigning the entire system to accommodate the new MCU with additional on-chip memory. Another option is to consider external memories. Those with high pin-count parallel interfaces, while providing superior performance compared to serial interfaces, have their own trade-offs. The most significant is that parallel interface-based designs have larger PCB footprints and higher pin count requirements. These memories typically also have fairly high standby current consumption. The table shown compares the available options across the different parameters that affect design choice. While a Parallel interface-based RAM solution may be a fit for certain high-performance applications, a Serial interface-based RAM would be a better choice for power or board space constrained applications. In the case of applications that need a balance of throughput, footprint and power consumption, neither approach seems to be a good choice without any trade-offs. HYPERRAM^™ is an ideal memory, as it strikes a balance between density, performance, power consumption, and pin-count.