Changes

|First public release

All the SoM 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).

These It is possibile to execute these operations are permitted only by using the devel versions of u-boot with the following commands:

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.

From Starting from the BELK/BXELK-4.1.2 release this functionality is restored and fully testedissue have been solved.

It is recommended suggested to update all the systems that runs ''older BSP releases to update '' to the newer one BELK 4.1.2 and to perform the follwing fixfollowing fixing steps:

* program on the board (or boot from a different storage - eg. the uSD) using the u-boot devel version of u-boot to allow the user to perform that can be found on our [https://cloud.dave.eu/ws-mirror/bora/belk-4.1.2 mirror server] - allowing the OTP lockcommand to be executed* execute the following command <code>configid som_lock 0</code>* program the release version of any 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'')