Difference between revisions of "DESK-MX8M-L/General/ConfigID"
(→ConfigID) |
|||
| Line 19: | Line 19: | ||
This article describes how the [[ConfigID and UniqueID|ConfigID]] is implemented in the products supported by the [[DESK-MX8M-L]] Linux Kit. | This article describes how the [[ConfigID and UniqueID|ConfigID]] is implemented in the products supported by the [[DESK-MX8M-L]] Linux Kit. | ||
| + | |||
| + | Moreover, a '''system''' is composed of the combination of a SOM and a carrier board. In this case, two ConfigIDs are used to identify the actual board configuration like it was a SOM+carrier board system. | ||
| + | |||
| + | For the sake of simplicity, the first ConfigID is denoted as ''SOM ConfigID'', while the second one is denoted as ''CB ConfigID'': | ||
===MITO 8M Mini=== | ===MITO 8M Mini=== | ||
As [[MITO 8M Mini SOM | MITO 8M Mini]] is a system-on-module (SOM), the typical mechanism described [[ConfigID_and_UniqueID#ConfigID|here]] is used. | As [[MITO 8M Mini SOM | MITO 8M Mini]] is a system-on-module (SOM), the typical mechanism described [[ConfigID_and_UniqueID#ConfigID|here]] is used. | ||
| − | |||
| − | |||
| − | |||
| − | |||
<pre class="board-terminal"> | <pre class="board-terminal"> | ||
| Line 41: | Line 41: | ||
As [[ORCA SOM | ORCA]] is a system-on-module (SOM), the typical mechanism described [[ConfigID_and_UniqueID#ConfigID|here]] is used. | As [[ORCA SOM | ORCA]] is a system-on-module (SOM), the typical mechanism described [[ConfigID_and_UniqueID#ConfigID|here]] is used. | ||
| − | |||
| − | |||
| − | |||
| − | |||
<pre class="board-terminal"> | <pre class="board-terminal"> | ||
Revision as of 17:06, 14 January 2022
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Version | Issue Date | Notes | |
| 1.0.0 | Jan 2022 | First DESK-MX8M release | |
ConfigID[edit | edit source]
This article describes how the ConfigID is implemented in the products supported by the DESK-MX8M-L Linux Kit.
Moreover, a system is composed of the combination of a SOM and a carrier board. In this case, two ConfigIDs are used to identify the actual board configuration like it was a SOM+carrier board system.
For the sake of simplicity, the first ConfigID is denoted as SOM ConfigID, while the second one is denoted as CB ConfigID:
MITO 8M Mini[edit | edit source]
As MITO 8M Mini is a system-on-module (SOM), the typical mechanism described here is used.
... SOM ConfigID#: 00000002 SOM UniqueID#: e317318f:1b1229d4 CB ConfigID#: 00001003 CB UniqueID#: fb000030:4d8eea2d Board: MX8MM-Mito8MMini on SBCX ...
ORCA[edit | edit source]
As ORCA is a system-on-module (SOM), the typical mechanism described here is used.
... SOM ConfigID#: 00000005 SOM UniqueID#: 0002aaff:8aefcecd CB ConfigID#: 00001001 CB UniqueID#: da000011:0dd2e72d Board: MX8MP-Mito8MPlus on SBC ORCA ...
Generally speaking[edit | edit source]
- SOM ConfigID is used to identify the configuration of the basic features of the SOM
- CB ConfigID is used to identify the peripherals and the I/O interfaces.
 NXP silicon manufacturer guarantees that processors UIDs (a.k.a. SOM UniqueID# on DESK-MX8M-L) to be unique over the whole MX8M family |
