ConfigID (XUELK)

From DAVE Developer's Wiki
Jump to: navigation, search
Info Box
AXEL ULite-top.png Applies to AXEL ULite
SBC Lynx-top.png Applies to SBC Lynx

Introduction[edit | edit source]

This article describes how the ConfigID is implemented in the products supported by the AXEL ULite and SBC Lynx Embedded Linux Kit (XUELK).

AXEL ULite[edit | edit source]

As AXEL ULite is a system-on-module (SOM), the typical mechanism described here is used.

SBC Lynx[edit | edit source]

Of course, SBC Lynx is not composed of the combination of a SOM and a carrier board. Nevertheless, starting from XUELK 1.2.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:

U-Boot 2016.03-xuelk-2.0.0 (Sep 13 2017 - 23:42:07 +0200), Build: jenkins-XUELK_U4

CPU:   Freescale i.MX6UL rev1.2 528 MHz (running at 396 MHz)
SOM ConfigID#: 00000013
SOM UniqueID#: e6b3f362:042961d4
CB ConfigID#: 0000002f
CB UniqueID#: 00000000:00000000
Board: MX6UL SBC Lynx

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.

The complete list of supported SOM ConfigID/CB ConfigID combinations is detailed here.