Bureaucrats, dave_user, Administrators
8,157
edits
Changes
no edit summary
== Introduction ==
As decribed described on [[ConfigID_management_(BELK/BXELK)|ConfigID management]] page, these informations information are stored inside a general -purpose OTP area of the SoC.
This technical note shows how to fix lock this OTP area on BORA systems running BSP versions older than [[BELK/BXELK software components#BELK 4.1.2|BELK/BXELK-4.1.2]]
=== ConfigID programming ===
All Bora SOMs are shipped with ConfgID and UniqueID programmed and locked. The OTP lock ensure ensures 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:
In older BSP, due to a u-boot limitation, this OTP area is not ''really'' locked and therefore it should be possible to overwrite its value, with possible identification errors during updates.
Starting from the BELK/BXELK-4.1.2 release this issue have has been solved.
== Lock OTP area ==
It is suggested to update the systems running ''BSP releases'' ''older thenthan'' BELK 4.1.2 performing the following steps:
* program on internal storage or alternatively boot from uSD using the u-boot devel version belk-4.1.2
