Difference between revisions of "BELK-TN-011: Lock OTP Areas"
m (U0007 moved page BELK-TN-011: Fix Lock OTP Areas to BELK-TN-011: Lock OTP Areas) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
{{Applies To Bora}} | {{Applies To Bora}} | ||
{{Applies To BoraX}} | {{Applies To BoraX}} | ||
| + | {{Applies To BoraLite}} | ||
| + | {{AppliesToBORA_TN}} | ||
| + | {{AppliesToBORA_Xpress_TN}} | ||
| + | {{AppliesToBORA Lite_TN}} | ||
{{InfoBoxBottom}} | {{InfoBoxBottom}} | ||
__FORCETOC__ | __FORCETOC__ | ||
| Line 19: | Line 23: | ||
== Introduction == | == Introduction == | ||
| − | As | + | As described on [[ConfigID_management_(BELK/BXELK)|ConfigID management]] page, these 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]] | 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 === | === ConfigID programming === | ||
| − | All Bora SOMs are shipped with ConfgID and UniqueID programmed and locked. The OTP lock | + | All Bora SOMs are shipped with ConfgID and UniqueID programmed and locked. The OTP lock 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: | It is possibile to execute these operations only using the devel versions of u-boot with the following commands: | ||
| Line 36: | Line 40: | ||
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. | 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 | + | Starting from the BELK/BXELK-4.1.2 release this issue has been solved. |
== Lock OTP area == | == Lock OTP area == | ||
| − | It is suggested to update the systems running ''BSP releases'' ''older | + | It is suggested to update the systems running ''BSP releases'' ''older than'' 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 | * program on internal storage or alternatively boot from uSD using the u-boot devel version belk-4.1.2 | ||
Latest revision as of 15:16, 21 December 2021
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
|
This technical note was validated against specific versions of hardware and software. What is described here may not work with other versions. |
|
History[edit | edit source]
| Version | Date | Notes |
|---|---|---|
| 1.0.0 | Sep 2020 | First release |
Introduction[edit | edit source]
As described on ConfigID management page, these 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-4.1.2
ConfigID programming[edit | edit source]
All Bora SOMs are shipped with ConfgID and UniqueID programmed and locked. The OTP lock 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:
configid som_configid <16 byte code> configid som_uniqueid <32 byte code> configid som_lock 0
Older BSP issue[edit | edit source]
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 has been solved.
Lock OTP area[edit | edit source]
It is suggested to update the systems running BSP releases older than 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
- devel version, for SD, are: belk-4.1.2_bora_mmc_devel_boot.bin and belk-4.1.2_bora_mmc_devel_u-boot.img
- u-boot can be downloaded from our mirror server
- u-boot 4.1.2 gives access to the OTP lock commands
- run the command
configid som_lock 0 - program 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)
