Bureaucrats, dave_user, Administrators
8,157
edits
Changes
→Introduction
== Introduction ==
As decribed on [[ConfigID_management_(BELK/BXELK)|ConfigID management]] page, these informations are stored inside a general purpouse purpose OTP area of the SoC.
This page describes a technical note shows how to fix to be done lock this OTP area on BORA systems that runs running BSP versions older than [[BELK/BXELK software components#BELK 4.1.2|BELK/BXELK-4.1.2]]
=== ConfigID programming ===
All the SoM Bora SOMs are shipped with ConfgID and UniqueID already programmed and locked. The OTP lock ensure that nobody can change this data (unattempted code execution, etc).
It is possibile to execute these operations only using the devel versions of u-boot with the following commands:
Starting from the BELK/BXELK-4.1.2 release this issue have been solved.
== Fix lock of Lock OTP areas area ==It is suggested to update the systems that runs running ''older BSP releases'' to the ''older then'' BELK 4.1.2 and perform performing the following fixing steps:
* program on internal storage or alternatively boot from the uSD using the u-boot devel version belk-4.1.2** devel version, for SD, are: [[mirror:bora/belk-4.1.2/belk-4.1.2_borax_mmc_devel_boot.bin|belk-4.1.2_bora_mmc_devel_boot.bin]] and [[mirror:bora/belk- that 4.1.2/belk-4.1.2_borax_mmc_devel_u-boot.img|belk-4.1.2_bora_mmc_devel_u-boot.img]]** u-boot can be found on downloaded from our [https://cloud.dave.eu/ws-mirror/bora/belk-4.1.2 mirror server] ** u- allowing boot 4.1.2 gives access to the OTP lock command to be executedcommands* execute run the command <code>configid som_lock 0</code>* program any your u-boot release version to restore the normal operations (''this is not required if previous operations have been executed using an external boot from SD'')
