System-on-chip

SoC stands for system-on-chip. It describes integration at the system level: a design can combine a CPU, memory resources, input/output interfaces and specialized processing blocks. An internal interconnect lets the blocks communicate. (Arm: SoC development)

Arm lists GPUs, digital signal processors and AI accelerators among possible SoC blocks. The list is not mandatory for every product. Treat a manufacturer's block diagram as the inventory of that particular implementation, rather than assuming the acronym promises every feature. (Arm: SoC development)

SoC development can reuse intellectual-property blocks and interconnect standards. The CPU is one computation engine within this larger design, so identifying a CPU architecture does not identify all the memory, interfaces or accelerators in the finished SoC. (Arm: SoC development)

A chiplet architecture describes how a system is partitioned across cooperating dies. SoC describes integrated system functions. When comparing the two ideas, distinguish the functional block diagram from the physical die and package arrangement. (Arm: SoC development) (Arm: chiplets)

In a conceptual block diagram, put the CPU in one box, interfaces in another, and any accelerator in a third. Draw the internal connections between them. This is a way to read an SoC's functional organization, not a claim that every design has the same boxes or memory arrangement. (Arm: SoC development)

Next, check the documentation for the complete product. Do not read “system” as a promise that no supporting circuitry is required. Record which functions are integrated and which requirements still belong to the surrounding design.

Use these questions as a reading checklist, not as a device-selection recommendation. Exact manufacturer documentation takes priority over a general definition.

• Read the block diagram rather than assuming features from the acronym.
• Separate CPU architecture from the complete device implementation.
• Identify integrated memory resources and interface requirements.
• Check the software ecosystem and any surrounding hardware requirements.

For the broader explanation, understand the processing blocks within a system. This page defines the term; the companion guide connects it to the rest of the system.