Difference between revisions of "ConfigID (XELK)"

From DAVE Developer's Wiki
Jump to: navigation, search
(No difference)

Latest revision as of 09:05, 19 May 2020

Info Box
Axel-lite 02.png Applies to Axel Lite
SBC-AXEL-02.png Applies to SBC AXEL

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.

200px-Emblem-important.svg.png NXP (former FSL) guarantees that processors UIDs (a.k.a. SOM UniqueID# on XELK BSP) 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. 200px-Emblem-important.svg.png