A System on Module (SoM) is a board-level module that brings together core functions of an embedded computing system. It commonly combines a processor with memory and supporting circuitry. The exact contents vary: storage, power management, wireless functions and exposed interfaces must be checked for the particular module.
SoM, SoC and single-board computer
A System on Chip (SoC) is an integrated circuit. A SoM is a physical module that can contain an SoC alongside other components. A SoC does not necessarily contain every memory device, power supply or interface needed for a finished product.
A single-board computer typically provides a more complete board with usable peripheral connections. A SoM generally exposes connections intended for integration with a carrier board or another host assembly. Vendors use product terminology differently, so compare the block diagram and interfaces rather than relying on the label alone. Computer on Module and System on Module are often overlapping terms, not a universal division based on whether wireless radios are present.
What the carrier board does
The carrier board connects the module to the application's power input, external connectors and other circuitry. It may provide interfaces for displays, cameras, storage, sensors or industrial communications, depending on the product.
Follow the module's hardware design guide for connector pin assignments, supply sequencing, signal routing and mechanical requirements. Some modules use board-to-board connectors, others use edge connectors or soldered connections. There is no single connector arrangement shared by every SoM.
A module is different from a development kit
AMD's Kria KV260 Vision AI Starter Kit is described as a development platform for Kria K26 SOMs. AMD lists the kit assembly as a SOM, carrier card and thermal solution. This illustrates the distinction between the computing module and the larger platform used to evaluate it.
Check the precise kit contents and required accessories before ordering. A successful demonstration on a starter kit is a useful development step, but it does not replace validation of a custom carrier board, enclosure, software image or production configuration.
Interchangeability requires an explicit compatibility check
A matching outline or connector does not prove that two modules are interchangeable. Compare pin functions, voltage levels, supported interfaces, power demand, thermal requirements and software support. Even within a product family, an upgrade may need a different firmware image or configuration.
Where a module follows a published form-factor standard, identify the supported revision and the options actually implemented. The standard can help organize compatibility checks, but the application must still be assessed. Avoid promising a future processor upgrade without checking the supplier's documented migration path.
When a SoM can help product development
A module can reduce the amount of processor and memory circuitry the product team must design. Development boards and vendor software can also provide a starting point for application work. The benefit depends on how closely the module fits the product and how much integration remains.
Compare that benefit with unit cost, board space, connector cost, thermal design and dependence on the supplier's software and lifecycle. A custom processor board may suit some projects; a SoM may suit others. Neither choice automatically produces the lowest total cost or lowest power consumption.
Selection and validation checklist
- Define processing, memory, storage and interface requirements for the actual workload.
- Check operating temperature, supply requirements and peak power demand.
- Review carrier-board design files, connector availability and mechanical constraints.
- Confirm operating-system, driver and update support for the required peripherals.
- Plan thermal measurements with the intended enclosure and workload.
- Test boot, restart, power interruption and recovery behavior.
- Confirm lifecycle information and the support arrangements for the production part.
Document the exact module revision and software configuration used during testing. Retest affected functions after hardware substitutions or software updates rather than assuming that an earlier evaluation covers every change.
Preparing a sourcing request
Provide the manufacturer part number, module revision where relevant, quantity, temperature grade and delivery needs. State whether the requirement is for a production module, a development kit or associated carrier-board components.
Use our contact page for component sourcing inquiries. Availability, included accessories and documentation should be confirmed for the specific requested item.
