Difference between revisions of "ConfigID (XELK)"
| Line 29: | Line 29: | ||
*''SOM ConfigID'' is used to identify the configuration of the basic features of the board | *''SOM ConfigID'' is used to identify the configuration of the basic features of the board | ||
*''CB ConfigID'' is used to identify the peripherals and the I/O interfaces. | *''CB ConfigID'' is used to identify the peripherals and the I/O interfaces. | ||
| + | |||
| + | {{ImportantMessage|text=NXP (former FSL) guarantees that processors UIDs to be unique over the whole iMX6 family, olders i.MX and future i.MX products. This system was developed by FSL in early 2000 years.}} | ||
Revision as of 09:16, 8 June 2018
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
Introduction[edit | edit source]
This article describes how the ConfigID is implemented in the products supported by the Axel Embedded Linux Kit (XELK).
AXEL[edit | edit source]
As AXEL is a system-on-module (SOM), the typical mechanism described here is used.
SBC Axel[edit | edit source]
Of course, SBC Axel is not composed of the combination of a SOM and a carrier board. Nevertheless, starting from XELK 2.1.0, 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:
... SOM ConfigID#: 00000003 SOM UniqueID#: df646299:0b0579d4 CB ConfigID#: 00000012 CB UniqueID#: da000011:0dd2e72d Board: MX6Q-AxelLite on SBCX ...
Generally speaking
- SOM ConfigID is used to identify the configuration of the basic features of the board
- CB ConfigID is used to identify the peripherals and the I/O interfaces.
 NXP (former FSL) guarantees that processors UIDs to be unique over the whole iMX6 family, olders i.MX and future i.MX products. This system was developed by FSL in early 2000 years. |
