DESK-MX9-L/General/ConfigID
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Issue Date | Notes | ||
| TBD | |||
| Year/Month/Day | TBD | ||
Contents
ConfigID[edit | edit source]
This article describes how the ConfigID is implemented in the products supported by the DESK-MX9-L Linux Kit.
AURA[edit | edit source]
As AURA is a system-on-module (SOM), the typical mechanism described here is used.
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:
TBD: riportare il dump del ConfigID e dell'eventuale cb_config_id dal dump di u-boot
... 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 SOM
- CB ConfigID is used to identify the peripherals and the I/O interfaces.
TBD: verificare e documentare gli special case per gli UID derivati dal siliconaro e riportarli qui sotto
 TBD silicon manufacturer (e.g.NXP) guarantees that processors UIDs (a.k.a. SOM UniqueID# on DESK-MX9-L) to be unique over the whole MX9 family |
