Bureaucrats, dave_user, Administrators
8,220
edits
Changes
no edit summary
{{Applies To Bora}}
{{Applies To BoraX}}
{{Applies To BoraLite}}
{{InfoBoxBottom}}
|2.0.0
|December 2016
|[[Bora_Embedded_Linux_Kit_(BELK )#BXELK_software_components#BELK_3.0.2_.2F_BXELK_1.0.1|3.0.1 2 / BXELK 1.0.01]]<br />[[Bora_Embedded_Linux_Kit_(BELK )#BXELK_software_components#BELK_4.0.0_.2F_BXELK_2.0.0|4.0.0 / BXELK 2.0.0]]
|Changed page name
|-
|2.1.0
|October 2019
|[[Bora_Embedded_Linux_Kit_(BELK)#BXELK_software_components#BELK_4.1.0|4.1.0]]
|Added BORA Lite
|-
|}
<section begin=BELK/>=Introduction=ConfigID management==
''ConfigID'' is a new feature of DAVE Embedded Systems products. It's main purpose is providing an automatic mechanism for the identification of the product model and configuration.
General information about ''ConfigID'' are provided [[ConfigID_and_UniqueID|here]]. The following sections details some Bora/BoraX specific information.
===ConfigID hardware implementation on Bora/BoraX/BoraLite===
BORA uses the first 32bytes OTP block on NOR SPI to store ConfigID (and its CRC32), UniqueID (and its CRC32)
==== ConfigID on BoraLite====For [[BORA Lite SOM | BORA Lite]] module configured for booting from NAND, the ConfigID is stored on internal I2C EPROM: see [[ConfigID_and_UniqueID#DAVE_Embedded_Systems.27_hardware_implementation | here]] for more information. ===ConfigID software implementation on Bora/BoraX/BoraLite===
U-Boot integrates the software routines for reading and displaying the ConfigID. Hereunder an example of SOM ConfigID at startup:
<pre>
root@axel-lite:~#
</pre>
<section end=BELK/>