fridtjof/qemu-cr16
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs/system/arm/aspeed: Document OTP memory options

Browse source 
Add documentation for the OTP memory module used by AST2600 and AST1030
SoCs, and describe options for using a pre-generated image or an
internal buffer. Include example commands for configuration and image
generation.

Signed-off-by: Kane-Chen-AS <kane_chen@aspeedtech.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Link: https://lore.kernel.org/qemu-devel/20250812094011.2617526-11-kane_chen@aspeedtech.com
Signed-off-by: Cédric Le Goater <clg@redhat.com>
This commit is contained in:
Kane-Chen-AS 2025-08-12 17:40:07 +08:00 • committed by Cédric Le Goater
parent 61dcc2c2db
commit ea82822b79
1 changed files with 31 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

31
docs/system/arm/aspeed.rst
View file

@ -243,6 +243,37 @@ under Linux), use :
-M ast2500-evb,bmc-console=uart3
OTP Option
^^^^^^^^^^
Both the AST2600 and AST1030 chips use the same One Time Programmable
(OTP) memory module, which is utilized for configuration, key storage,
and storing user-programmable data. This OTP memory module is managed
by the Secure Boot Controller (SBC). The following options can be
specified or omitted based on your needs.
* When the options are specified, the pre-generated configuration
file will be used as the OTP memory storage.
* When the options are omitted, an internal memory buffer will be
used to store the OTP memory data.
.. code-block:: bash
-blockdev driver=file,filename=otpmem.img,node-name=otp \
-global aspeed-otp.drive=otp \
The following bash command can be used to generate a default
configuration file for OTP memory:
.. code-block:: bash
if [ ! -f otpmem.img ]; then
for i in $(seq 1 2048); do
printf '\x00\x00\x00\x00\xff\xff\xff\xff'
done > otpmem.img
fi
Aspeed 2700 family boards (``ast2700-evb``)
==================================================================