Bureaucrats, dave_user, Administrators
4,650
edits
Changes
Created page with "{{InfoBoxTop}} {{AppliesToSBCLynx}} {{InfoBoxBottom}} == Introduction == This article describes how the ConfigID is implemented in the products supp..."
{{InfoBoxTop}}
{{AppliesToSBCLynx}}
{{InfoBoxBottom}}
== Introduction ==
This article describes how the [[ConfigID and UniqueID|ConfigID]] is implemented in the products supported by the [AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)|AXEL ULite and SBC Lynx Embedded Linux Kit (XUELK)].
==AXEL ULite==
As AXEL ULite is a system-on-module (SOM), the typical mechanism described [ConfigID_and_UniqueID#ConfigID|here] is used.
==SBC Lynx==
Of course, Even though 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'':
<pre class="board-terminal">
U-Boot 2015.04-xuelk-1.2.1 (Apr 26 2017 - 09:20:00), Build: jenkins-XUELK_U-Boot-20
CPU: Freescale i.MX6UL rev1.1 at 396 MHz
...
SOM ConfigID#: 00000013
SOM UniqueID#: e6b3f362:042961d4
...
CB ConfigID#: 0000002f
CB UniqueID#: 00000000:00000000
Board: MX6UL SBC Lynx
...
</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.
{{AppliesToSBCLynx}}
{{InfoBoxBottom}}
== Introduction ==
This article describes how the [[ConfigID and UniqueID|ConfigID]] is implemented in the products supported by the [AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)|AXEL ULite and SBC Lynx Embedded Linux Kit (XUELK)].
==AXEL ULite==
As AXEL ULite is a system-on-module (SOM), the typical mechanism described [ConfigID_and_UniqueID#ConfigID|here] is used.
==SBC Lynx==
Of course, Even though 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'':
<pre class="board-terminal">
U-Boot 2015.04-xuelk-1.2.1 (Apr 26 2017 - 09:20:00), Build: jenkins-XUELK_U-Boot-20
CPU: Freescale i.MX6UL rev1.1 at 396 MHz
...
SOM ConfigID#: 00000013
SOM UniqueID#: e6b3f362:042961d4
...
CB ConfigID#: 0000002f
CB UniqueID#: 00000000:00000000
Board: MX6UL SBC Lynx
...
</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.