Changes

Jump to: navigation, search

ConfigID (XELK)

1,162 bytes added, 09:48, 6 November 2017
Created page with "{{InfoBoxTop}} {{AppliesToAXELULite}} {{AppliesToSBCLynx}} {{InfoBoxBottom}} == Introduction == This article describes how the ConfigID is implement..."
{{InfoBoxTop}}
{{AppliesToAXELULite}}
{{AppliesToSBCLynx}}
{{InfoBoxBottom}}

== Introduction ==
This article describes how the [[ConfigID and UniqueID|ConfigID]] is implemented in the products supported by the [[Axel_Embedded_Linux_Kit_(XELK)|Axel Embedded Linux Kit (XELK)]].

==AXEL==
As AXEL is a system-on-module (SOM), the typical mechanism described [[ConfigID_and_UniqueID#ConfigID|here]] is used.

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

<pre class="board-terminal">
...
SOM ConfigID#: 00000003
SOM UniqueID#: df646299:0b0579d4
CB ConfigID#: 00000012
CB UniqueID#: da000011:0dd2e72d
Board: MX6Q-AxelLite on SBCX
...
</pre>

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.
116
edits

Navigation menu