Single Board Computer (SBC) offers a ready-to-use embedded development platform for building end-products. SBC accelerates time-to-market and minimizes development cost and risk. However, System on Module (SoM)/Computer on Module (CoM) is a more appropriate choice for building embedded products. I will attempt to defend my assertion using a fictional case presented below.
In continuation to my previous blog post, Harry (CTO of BestECG company) on being asked by the company’s CEO on why he chose SoM instead of SBC for embedded development of ECGs, Harry presented two major benefits of using SoM over SBC that makes the former better aligned to meet the demands of embedded market.
Design scalability
One of the critical challenges that Harry faced as a CTO was to keep pace with the rapid technological upgrades. With Moore’s Law in action, microprocessors and memory move to smaller process nodes within 2 years, which is less than the expected product life of an ECG machine. Customers’ demands, which include advanced performance, low power consumption, and compact machines, necessitate frequent design updates to the embedded platform. These design updates add to the development cost. By using pin-compatible SoMs for embedded development, Harry knocked-off platform obsolescence from his list of concerns.
The pin-compatible modules from Toradex enable plug-and-play for scaling-up platforms based on future technologies and market requirements. New modules can be easily connected to existing carrier boards, and the application software may need some minor updates. With SBCs, Harry would not have achieved platform scalability as the board comes with fixed computing and memory sections. In order to accommodate latest tech advances, he would need to use the new SBCs available in the market.
Design flexibility
SBCs come with fixed computing, memory, and I/O sections, all of which are integrated on a single printed circuit board (PCB). The I/Os, size & configuration are already fixed, so it not possible to customize the board as per the needs of the application. Harry’s options are limited to using the available SBCs, which come with standard I/Os, that may not have all the I/Os needed for the ECG machines. As per his design requirements, Harry can hook-up other peripherals to the SBC; however, such a solution is not flexible enough and will end up taking a lot of space, which would increase the platform’s size.
By using SoMs, Harry segregated the computing and memory section from the I/O section. The carrier board, which connects to the SoM, houses all I/Os needed for ECG machines. Harry designs and develops the carrier board as per his size and configuration requirements, and then connects a SoM to it. The entire platform, which has the least possible size, is tuned to his design requirements. The combination of an off-the-shelf SoM and a compatible carrier board offers a platform that is both flexible and scalable.
By choosing SoMs over SBCs as a replacement for chip-based development, Harry was able to make the embedded platform future-proof and customizable. SBCs are ideal for applications that may not have specific requirements in terms of size, I/O, and configuration. A decision to choose either SoM or SBC depends on the specific project requirements and sales volume.
Now, you may be thinking that there so many vendors of SoMs in the embedded market, then why did Harry choose Toradex as the preferred SoM vendor? Check out my next blog that elucidates why Toradex would be your ideal SoM partner.
**This is a work of fiction. Names, characters, businesses, places, events and incidents are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons, living or dead, or actual events is purely coincidental.
Author:
Prakash Mohapatra
, Product Manager, ToradexReply for:
Please login to leave a comment!
In recent years, we often hear about Make or Buy, Time to Market, Scalability, and Cost optimization. Customers very often are talking or considering the “buy solution” of a computer module when using these phrases. Before diving in into the details, we need some definition.
A Single Board Computer (SBC) is a complete computer on a single printed circuit board, including the clock, microprocessor, RAM, flash memory, Ethernet, and I/O controllers.
A Computer On Module (COM) or a “System-On-Module" (SoM) typically does not have I/O sockets for direct connection to peripherals. They must be plugged into the main board (often called Carrier Board or Base Board), which completes the I/O pathways to the outside world.
This approach is very common because an end customer can focus on developing the core competence (e.g., POS, factory automation, medical) as below:
It is easier said but the devil is in the detail. While an SBC is driven by the application itself, customers are developing the solution based on the requirements of the selected fitting SoM that varies in several circumstances. This section gives an overview of acronyms and major form factors. Major form factors are defined by SGET. SGETs major focus is Arm architecture, therefore we are looking carefully at SGETs initiatives.
Image
The Standardization Group for Embedded Technologies – or in short SGET – is an international not-for-profit association of companies and organizations that collaboratively develop independent specifications for embedded computer technology. SGET e.V. is a registered technical, scientific, and educational association organized under German law. The purpose is to provide a platform to define and market open industry standards for embedded technologies.
SGET Goals:
Since 2021, Renesas is a member of SGET e.V. It is important that Renesas and SGET share our experiences in MPU designs as well as get feedback from the field on what is required.
The SMARC® (“Smart Mobility ARChitecture”) is a versatile small form factor computer module in definition targeting applications that require low power, low costs, and high performance.
The modules will typically use Arm SoCs similar to or the same as those used in many familiar devices such as tablet computers and smartphones.
Two module sizes are defined: 82mm x 50mm and 82mm x 80mm.
Image
Figure 1. Comparison Between Full and Half Size SMARC ModulesThe idea of all Open Standard Modules™ is to create a new, future proof and versatile standard for small-size, low-cost embedded computer modules, combining the following key characteristics:
The Open Standard Module™ (OSM) specification allows for developing, producing, and distributing embedded modules for the most popular MCU32, Arm and even x86 architectures. For a growing number of IoT applications, this standard helps to combine the advantages of modular embedded computing with increasing requirements regarding costs, space, and interfaces. This standard also enables different form factors, such as SMARC and proprietary to be created, and help developers to easily scale their development.
Image
Figure 2. Form Factor Variation Based on OSM StandardMost used modules are still based on proprietary. Even OEM customers are developing and producing computer modules for themselves to separate the processing unit from the application and split development into two different groups. Proprietary solutions allow either to focus on a specific SoC without losing any features of an SoC or focus on specialties, which can be driven by the application or the focus of one major feature, e.g., shrinking the size.
The major benefit of using SoMs or SBCs, is the split of needed knowledge and resources. When buying a SoM or a SBC, MPU design knowledge is not needed as this is outsourced to an MPU specialist. The headache of fast interconnect, the high-speed connections, and the selection of fitting companion chips are gone.
Renesas provides two partner programs to support your development. The RZ Partner Ecosystem program delivers ready-to-go partner solutions based on RZ MPUs to accelerate your board development. On the other hand, the Preferred Partner Program is a hardware-centric partner program where our partners deliver ready-to-use hardware (incl. the BSP) featuring Renesas RZ family MPUs plus Renesas analog, sensors, and connectivity. With both our partner programs, customers can reduce the focus on the hardware and can focus on differentiating their products. Both partner programs deliver solutions and hardware for applications ranging from consumer solutions to all kinds of industrial applications including medical devices.
Visit the Renesas RZ Partner Ecosystem Solutions and Preferred Partner Program to find the right solution and right partner.