Computer-on-module: Difference between revisions
→External links: {{Computer sizes}} |
|||
(19 intermediate revisions by 16 users not shown) | |||
Line 1: | Line 1: | ||
{{Short description|Type of single-board computer}} |
|||
{{Distinguish|Computer module}} |
{{Distinguish|Computer module}} |
||
<!-- {{Refimprove|date=September 2014}} --> |
<!-- {{Refimprove|date=September 2014}} --> |
||
A '''computer-on-module''' ('''COM''') is a type of [[single-board computer]] (SBC), a subtype of an [[embedded computer]] system. An extension of the concept of [[System on a chip|system on chip]] (SoC) and [[system in package]] (SiP), COM lies between a full-up [[computer]] and a [[microcontroller]] in nature. It is very similar to a [[system on module]] (SOM). |
A '''computer-on-module''' ('''COM''') is a type of [[single-board computer]] (SBC), a subtype of an [[embedded computer]] system. An extension of the concept of [[System on a chip|system on chip]] (SoC) and [[system in package]] (SiP), COM lies between a full-up [[computer]] and a [[microcontroller]] in nature. It is very similar to a [[system on module]] (SOM). |
||
== Design == |
== Design == |
||
⚫ | COMs are complete [[embedded computer]]s built on a single [[circuit board]].<ref name=icp_coms>[https://www.icp-deutschland.de/out/media/categories/files/Module-INFO.pdf Typical COM product line]</ref> The design is centered on a [[microprocessor]] with [[random-access memory|RAM]], [[input/output]] controllers and all other features needed to be a functional computer on the one board. However, unlike a single-board computer, the COM usually lacks the standard connectors for any input/output peripherals to be attached directly to the board. |
||
⚫ | COMs are complete [[embedded computer]]s built on a single [[circuit board]].<ref name=icp_coms>[https://www.icp-deutschland.de/out/media/categories/files/Module-INFO.pdf Typical COM product line]</ref> The design is centered on a [[microprocessor]] with [[RAM]], [[input/output]] controllers and all other features needed to be a functional computer on the one board. However, unlike a single-board computer, the COM usually lacks the standard connectors for any input/output peripherals to be attached directly to the board. |
||
The module usually needs to be mounted on a carrier board (or "baseboard") which breaks the bus out to standard peripheral connectors. Some COMs also include [[peripheral]] connectors. Some can be used without a carrier. |
The module usually needs to be mounted on a carrier board (or "baseboard") which breaks the bus out to standard peripheral connectors. Some COMs also include [[peripheral]] connectors. Some can be used without a carrier. |
||
Line 13: | Line 12: | ||
A COM solution offers a dense package computer system for use in small or specialized applications requiring low power consumption or small physical size as is needed in [[embedded system]]s. As a COM is very compact and highly integrated, even complex CPUs, including multi-core technology, can be realized on a COM. |
A COM solution offers a dense package computer system for use in small or specialized applications requiring low power consumption or small physical size as is needed in [[embedded system]]s. As a COM is very compact and highly integrated, even complex CPUs, including multi-core technology, can be realized on a COM. |
||
Some devices also incorporate [[field-programmable gate array]] (FPGA) components. FPGA-based functions can be added as [[Semiconductor intellectual property core|IP cores]] to the COM itself or to the carrier card. Using FPGA IP cores adds to the modularity of a COM concept |
Some devices also incorporate [[field-programmable gate array]] (FPGA) components. FPGA-based functions can be added as [[Semiconductor intellectual property core|IP cores]] to the COM itself or to the carrier card. Using FPGA IP cores adds to the modularity of a COM concept because I/O functions can be adapted to special needs without extensive rewiring on the [[printed circuit board]].<ref name=ts_com_fpga>[http://www.embeddedarm.com/products/computer-on-modules.php Technologic Systems FPGA based COM modules]</ref> |
||
A "computer-on-module" is also called a "[[System on module|system-on-module]]" (SOM).<ref> |
|||
[https://www.pcmag.com/encyclopedia/term/computer-on-module "computer-on-module"]. |
|||
PCMag Encyclopedia. |
|||
</ref><ref> |
|||
[https://www.criticallink.com/computer-on-module/ "Computer on Module"]. |
|||
[https://www.criticallink.com/system-on-module/ "System on Module (SOM)"]. |
|||
Critical Link definitions. |
|||
</ref><ref> |
|||
[https://www.arrow.com/en/research-and-events/articles/system-on-modules-and-small-board-computer-make-or-buy "Make or Buy: System on Modules and Small Board Computers"]. |
|||
</ref> |
|||
== History == |
== History == |
||
The terms "Computer-on-Module" and "COM" were coined by VDC Research Group, Inc. (formerly Venture Development Corporation) to describe this class of embedded computer boards. |
|||
Dr. Gordon Kruberg, founder and CEO of Gumstix, is credited for creating the first COM, predating the next recognizable COM entries by almost 18 months. |
|||
The terms "Computer-on-Module" and "COM" were coined by market researcher Venture Development Corp (VDC) and first appeared in VDC's report on the Global Market for Merchant Computer Boards in Real-time and Embedded Applications<ref name=vdc_report>[http://linuxdevices.org/ldfiles/misc/vdc-switch-fabric-architectures-report-excerpt-nov2001.jpg Global Market for Merchant Computer Boards in Real-time and Embedded Applications report]</ref>, published in November 2001. The terms became more prominent upon industry standardization of the [[COM Express]] format in 2005. |
|||
Gumstix ARM Linux Machine number is 373, established 9 September 2003, while Kontron's is 735, established 18 April 2005, and Keith & Koep's (now part of SECO<ref> |
|||
There is no clear "first Computer-on-Module" product, since numerous small component-like single board computers were already on the market<ref name=tiny_sbcs>[http://linuxdevices.org/ldfiles/misc/small-linux-capable-boards-prior-to-2005-v2.jpg COM-like Linux capable boards, announced prior to 2005]</ref><ref name=adlink_coms_history>{{cite web |
|||
[https://north.seco.com/en/company/news/details/garz-fricke-group-becomes-seco-northern-europe-and-seco-mind-germany "Garz & Fricke (incl. Keith & Koep) now part of SECO"] SECO Northern Europe</ref>) is 776, established 20 June 2005. Boards numbered below 373 were larger and single board computers as opposed to modules, for example, the Itsy, a tiny hand-held device based on the StrongARM. |
|||
|url = http://linuxdevices.org/ldfiles/misc/adlink-history-of-coms-june2013.jpg |
|||
|title = History of COMs |
|||
|publisher = [[ADLINK]]}}</ref> when VDC initially introduced the term. |
|||
The rapid development paradigm (COM + expansion board) Dr. Kruberg established has been at the heart of leading edge development since then and used at leading consumer products companies worldwide. |
|||
COM Express is just one of many standardized Computer-on-module formats. Other open-spec COM standards include [[SMARC]], [[Qseven]], [[Embedded System Module|ESM]], [[XTX]], and [[ETX (form factor)|eTX]]. Additionally, many manufacturers offer COMs with proprietary formats. |
|||
COM's have proven useful in launching entire industries{{citation needed|date=March 2022}} requiring rapid development efforts. For example, in 2005 Apple used a [[Gumstix]] COM to test the original iPhone concept. |
|||
Some proprietary COM formats have modified [[SODIMM]] and [[Mobile PCI Express Module|MXM]] edge-connector style designs, while others have arbitrary rectangular dimensions along with various types of high density board-to-board connectors |
|||
<ref>[https://www.gumstix.com/images/Launch.pdf Gumstix launch PR]</ref><ref>[http://linuxgizmos.com/tiny-compute-modules-crank-up-snapdragon-845-and-snapdragon-660/ Inforce Micro SoMs]</ref>. Notably, the [https://www.raspberrypi.org/products/compute-module-3/ Raspberry Pi Compute Module] is designed in a 200-pin SODIMM format. |
|||
== Benefits == |
== Benefits == |
||
⚫ | Using a carrier board is a benefit in many cases, as it can implement special I/O interfaces, memory devices, connectors or form factors. Separating the design of the carrier board and COM makes design concepts more modular, if needed. A carrier tailored to a special application may involve high design overhead by itself. If the actual processor and main I/O controllers are located on a COM, it is much easier, for example, to upgrade a CPU component to the next generation, without having to redesign a very specialized carrier as well. This can save costs and shorten development times. However, this only works if the board-to-board connection between the COM and its carrier remains compatible between upgrades. |
||
⚫ | Other benefits of using COM products instead of ground-up development include reducing [[time to market]] (TTM), risk reduction, cost savings, choice of a variety of CPUs, reduced requirements and time for customer design, and the ability to conduct both hardware and software development simultaneously.<ref name=matthewdoo>[https://www.toradex.com/products/computer-on-modules Computer on Modules - Technical Reference Manuals]</ref> |
||
⚫ | Using a carrier board is a benefit in many cases, as it can implement special I/O interfaces, memory devices, connectors or form factors. Separating the design of the carrier board and COM makes design concepts more modular, if needed. A carrier tailored to a special application may involve high design overhead by itself. If the actual processor and main I/O controllers are located on a COM, it is much easier, for example, to upgrade a CPU component to the next generation, without having to redesign a very specialized carrier as well. This can save costs and shorten development times. However, this only works if the board-to-board connection between the COM and its carrier remains compatible between upgrades. |
||
⚫ | Other benefits of using COM products instead of ground-up development include reducing [[time to market]] (TTM), risk reduction, cost savings, choice of a variety of CPUs, reduced requirements and time for customer design, and the ability to conduct both hardware and software development simultaneously |
||
== See also == |
== See also == |
||
Line 47: | Line 54: | ||
==References== |
==References== |
||
{{reflist}} |
{{reflist}} |
||
⚫ | |||
{{Z148}}<!-- {{No more links}} |
|||
==External links== |
|||
Please be cautious adding more external links. |
|||
*{{cite web |
|||
|title = gumstix Introduces Smallest Commercially Available Linux Boards and Computers |
|||
|url = https://www.gumstix.com/images/Launch.pdf |
|||
|date = May 14, 2004 |
|||
|language = en}} |
|||
*{{cite web |
|||
Wikipedia is not a collection of links and should not be used for advertising. |
|||
|url = https://hardware.slashdot.org/story/04/01/28/1645213/a-linux-machine-for-your-collar |
|||
|title = A Linux Machine For Your Collar |
|||
|website = [[Slashdot]] |
|||
|date = January 28, 2004 |
|||
|language = en}} |
|||
*{{cite book |
|||
Excessive or inappropriate links will be removed. |
|||
|title = Dogfight: How Apple and Google Went to War and Started a Revolution |
|||
|first = Fred |
|||
|last = Vogelstein |
|||
|year = 2013 |
|||
|isbn = 9780374711009 |
|||
|url = https://books.google.com/books?id=qDOdHNAb3aMC&q=gumstix |
|||
|language = en}} |
|||
{{Computer sizes}} |
|||
See [[Wikipedia:External links]] and [[Wikipedia:Spam]] for details. |
|||
⚫ | |||
If there are already suitable links, propose additions or replacements on |
|||
the article's talk page, or submit your link to the relevant category at |
|||
the Open Directory Project (dmoz.org) and link there using {{Dmoz}}. |
|||
--> |
|||
[[Category:Microcomputers]] |
[[Category:Microcomputers]] |
Latest revision as of 22:38, 8 May 2024
A computer-on-module (COM) is a type of single-board computer (SBC), a subtype of an embedded computer system. An extension of the concept of system on chip (SoC) and system in package (SiP), COM lies between a full-up computer and a microcontroller in nature. It is very similar to a system on module (SOM).
Design
[edit]COMs are complete embedded computers built on a single circuit board.[1] The design is centered on a microprocessor with RAM, input/output controllers and all other features needed to be a functional computer on the one board. However, unlike a single-board computer, the COM usually lacks the standard connectors for any input/output peripherals to be attached directly to the board.
The module usually needs to be mounted on a carrier board (or "baseboard") which breaks the bus out to standard peripheral connectors. Some COMs also include peripheral connectors. Some can be used without a carrier.
A COM solution offers a dense package computer system for use in small or specialized applications requiring low power consumption or small physical size as is needed in embedded systems. As a COM is very compact and highly integrated, even complex CPUs, including multi-core technology, can be realized on a COM.
Some devices also incorporate field-programmable gate array (FPGA) components. FPGA-based functions can be added as IP cores to the COM itself or to the carrier card. Using FPGA IP cores adds to the modularity of a COM concept because I/O functions can be adapted to special needs without extensive rewiring on the printed circuit board.[2]
A "computer-on-module" is also called a "system-on-module" (SOM).[3][4][5]
History
[edit]The terms "Computer-on-Module" and "COM" were coined by VDC Research Group, Inc. (formerly Venture Development Corporation) to describe this class of embedded computer boards.
Dr. Gordon Kruberg, founder and CEO of Gumstix, is credited for creating the first COM, predating the next recognizable COM entries by almost 18 months.
Gumstix ARM Linux Machine number is 373, established 9 September 2003, while Kontron's is 735, established 18 April 2005, and Keith & Koep's (now part of SECO[6]) is 776, established 20 June 2005. Boards numbered below 373 were larger and single board computers as opposed to modules, for example, the Itsy, a tiny hand-held device based on the StrongARM.
The rapid development paradigm (COM + expansion board) Dr. Kruberg established has been at the heart of leading edge development since then and used at leading consumer products companies worldwide.
COM's have proven useful in launching entire industries[citation needed] requiring rapid development efforts. For example, in 2005 Apple used a Gumstix COM to test the original iPhone concept.
Benefits
[edit]Using a carrier board is a benefit in many cases, as it can implement special I/O interfaces, memory devices, connectors or form factors. Separating the design of the carrier board and COM makes design concepts more modular, if needed. A carrier tailored to a special application may involve high design overhead by itself. If the actual processor and main I/O controllers are located on a COM, it is much easier, for example, to upgrade a CPU component to the next generation, without having to redesign a very specialized carrier as well. This can save costs and shorten development times. However, this only works if the board-to-board connection between the COM and its carrier remains compatible between upgrades.
Other benefits of using COM products instead of ground-up development include reducing time to market (TTM), risk reduction, cost savings, choice of a variety of CPUs, reduced requirements and time for customer design, and the ability to conduct both hardware and software development simultaneously.[7]
See also
[edit]References
[edit]- ^ Typical COM product line
- ^ Technologic Systems FPGA based COM modules
- ^ "computer-on-module". PCMag Encyclopedia.
- ^ "Computer on Module". "System on Module (SOM)". Critical Link definitions.
- ^ "Make or Buy: System on Modules and Small Board Computers".
- ^ "Garz & Fricke (incl. Keith & Koep) now part of SECO" SECO Northern Europe
- ^ Computer on Modules - Technical Reference Manuals
External links
[edit]- "gumstix Introduces Smallest Commercially Available Linux Boards and Computers" (PDF). May 14, 2004.
- "A Linux Machine For Your Collar". Slashdot. January 28, 2004.
- Vogelstein, Fred (2013). Dogfight: How Apple and Google Went to War and Started a Revolution. ISBN 9780374711009.