| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Issue Date | Notes | ||
| 2024/02/01 | First DESK-MX9-L release | ||
Contents
ConfigIDEdit
This article describes how the ConfigID is implemented in the products supported by the DESK-MX9-L Linux Kit.
AURAEdit
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:
... SOM ConfigID#: 00000001 SOM UniqueID#: df646299:0b0579d4 CB ConfigID#: 00002001 CB UniqueID#: da000011:0dd2e72d ...
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.
 NXP guarantees that processors UIDs (a.k.a. SOM UniqueID# on DESK-MX9-L) to be unique over the whole MX9 family |