Bureaucrats, dave_user, Administrators
8,154
edits
Changes
m
These It is possibile to execute these operations are permitted only by using the devel versions of u-boot with the following commands:
From Starting from the BELK/BXELK-4.1.2 release this functionality is restored and fully testedissue have been solved.
U0007 moved page BELK-TN-011: Fix Lock OTP Areas to BELK-TN-011: Lock OTP Areas
|1.0.0
|Sep 2020
|First public release
|}
== 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 nothing nobody can change this data (unattempted code execution, etc).
<pre>
configid som_configid <16 byte code>
== Older BSP issue ==
In older BSP, due to an a u-boot limitation, this OTP area is not ''really '' locked and therefore it is should be possible to overwrite its value. This can lead to , with possible identification errors during updates.
== Fix lock of Lock OTP areas area ==It is recommended suggested to update all the systems that runs running ''BSP releases'' ''older releases to update to the newer one and to perform then'' BELK 4.1.2 performing the follwing fixfollowing steps:
* program on the board (internal storage or alternatively boot from a different storage uSD using the u-boot devel version belk- eg4. the uSD) the 1.2** devel version of , 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-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 downloaded from our [https://cloud.dave.eu/ws-mirror/bora/belk-4.1.2 mirror server] ** u-boot 4.1.2 gives access to allow the user to perform the OTP lockcommands* execute run the following command <code>configid som_lock 0</code>* program the release version of 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'')
