User Tools

Site Tools


Sidebar

* [[start]] * [[som|System on module]] * [[usomiq-beaglebone|Mentorel Beaglebone uSomIQ]] * [[usomiq|uSomIQ AM335x]] * [[somiq|SomIQ family]] * [[blueshark|BlueShark family]] * [[devkit|DevKits]] * [[usomiq-bone-cape|uSomIQ Bone Cape]] * [[somiqboard|Somiqboard]] * [[atoll|Atoll]] * [[expansion|Expansion boards]] * [[somiq-wlan|SomIQ-WLAN]] * [[os|OS support]] * [[ubuntu|Ubuntu Linux]] * [[sw-hints|SW hints]] * [[tslib|Tslib]] * [[qt-embedded|Qt embedded]] Follow us * [[http://twitter.com/mentorel|Twitter]] * [[http://www.linkedin.com/company/mentorel|LinkedIn]] * [[https://www.facebook.com/mentorel.company|Facebook]] * [[https://plus.google.com/105868322858146792212/posts|Google+]] * [[http://www.mentorel.com|MENTOREL home page]]

devkit

Development kits

The module will usually need to be mounted on a carrier board (or “baseboard”) which breaks the bus out to standard peripheral connectors. Some COMs also include peripheral connectors and/or can be used without a carrier.

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. On the other hand, this only works if the board-to-board connection between the COM and its carrier remains compatible between upgrades.

Somiqboard

Atoll Deluxe

devkit.txt · Last modified: 2013/03/12 16:38 (external edit)