Using the vbootrom image support and the boot ROM binary is
now passed via the -bios option, using the image located in
pc-bios/ast27x0_bootrom.bin.
Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
Reviewed-by: Nabih Estefan <nabihestefan@google.com>
---
docs/system/arm/aspeed.rst | 29 ++++++++++++++++++++++++++++-
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/docs/system/arm/aspeed.rst b/docs/system/arm/aspeed.rst
index 97fd6a0e7f..c87a2cf796 100644
--- a/docs/system/arm/aspeed.rst
+++ b/docs/system/arm/aspeed.rst
@@ -250,7 +250,14 @@ under Linux), use :
Booting the ast2700-evb machine
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Boot the AST2700 machine from the flash image, use an MTD drive :
+Boot the AST2700 machine from the flash image.
+
+There are two supported methods for booting the AST2700 machine with a flash image:
+
+Manual boot using ``-device loader``:
+
+It causes all 4 CPU cores to start execution from address ``0x430000000``, which
+corresponds to the BL31 image load address.
.. code-block:: bash
@@ -270,6 +277,26 @@ Boot the AST2700 machine from the flash image, use an MTD drive :
-drive file=${IMGDIR}/image-bmc,format=raw,if=mtd \
-nographic
+Boot using a virtual boot ROM (``-bios``):
+
+If users do not specify the ``-bios option``, QEMU will attempt to load the
+default vbootrom image ``ast27x0_bootrom.bin`` from either the current working
+directory or the ``pc-bios`` directory within the QEMU source tree.
+
+.. code-block:: bash
+
+ $ qemu-system-aarch64 -M ast2700-evb \
+ -drive file=image-bmc,format=raw,if=mtd \
+ -nographic
+
+The ``-bios`` option allows users to specify a custom path for the vbootrom
+image to be loaded during boot. This will load the vbootrom image from the
+specified path in the ${HOME} directory.
+
+.. code-block:: bash
+
+ -bios ${HOME}/ast27x0_bootrom.bin
+
Aspeed minibmc family boards (``ast1030-evb``)
==================================================================
--
2.43.0
Jamin,
On 4/17/25 05:12, Jamin Lin wrote:
> Using the vbootrom image support and the boot ROM binary is
> now passed via the -bios option, using the image located in
> pc-bios/ast27x0_bootrom.bin.
>
> Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
> Reviewed-by: Nabih Estefan <nabihestefan@google.com>
> ---
> docs/system/arm/aspeed.rst | 29 ++++++++++++++++++++++++++++-
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
> diff --git a/docs/system/arm/aspeed.rst b/docs/system/arm/aspeed.rst
> index 97fd6a0e7f..c87a2cf796 100644
> --- a/docs/system/arm/aspeed.rst
> +++ b/docs/system/arm/aspeed.rst
> @@ -250,7 +250,14 @@ under Linux), use :
> Booting the ast2700-evb machine
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Currently, we have 2 sections for the Aspeed boards :
1. Aspeed family boards (ast2500-evb, ast2600-evb, ast2700-evb, ast2700fc, bletchley-bmc, fuji-bmc, fby35-bmc, fp5280g2-bmc, g220a-bmc, palmetto-bmc, qcom-dc-scm-v1-bmc, qcom-firework-bmc, quanta-q71l-bmc, rainier-bmc, romulus-bmc, sonorapass-bmc, supermicrox11-bmc, supermicrox11spi-bmc, tiogapass-bmc, witherspoon-bmc, yosemitev2-bmc)
2. Aspeed minibmc family boards (ast1030-evb)
The first is quite big and relatively consistent for the AST2400, AST2500
and AST2600 SoCs. Since the AST2700 SoC boards boot differently, I think
it is time to introduce a new section for the ast2700 machines.
Thanks,
C.
> -Boot the AST2700 machine from the flash image, use an MTD drive :
> +Boot the AST2700 machine from the flash image.
> +
> +There are two supported methods for booting the AST2700 machine with a flash image:
> +
> +Manual boot using ``-device loader``:
> +
> +It causes all 4 CPU cores to start execution from address ``0x430000000``, which
> +corresponds to the BL31 image load address.
>
> .. code-block:: bash
>
> @@ -270,6 +277,26 @@ Boot the AST2700 machine from the flash image, use an MTD drive :
> -drive file=${IMGDIR}/image-bmc,format=raw,if=mtd \
> -nographic
>
> +Boot using a virtual boot ROM (``-bios``):
> +
> +If users do not specify the ``-bios option``, QEMU will attempt to load the
> +default vbootrom image ``ast27x0_bootrom.bin`` from either the current working
> +directory or the ``pc-bios`` directory within the QEMU source tree.
> +
> +.. code-block:: bash
> +
> + $ qemu-system-aarch64 -M ast2700-evb \
> + -drive file=image-bmc,format=raw,if=mtd \
> + -nographic
> +
> +The ``-bios`` option allows users to specify a custom path for the vbootrom
> +image to be loaded during boot. This will load the vbootrom image from the
> +specified path in the ${HOME} directory.
> +
> +.. code-block:: bash
> +
> + -bios ${HOME}/ast27x0_bootrom.bin
> +
> Aspeed minibmc family boards (``ast1030-evb``)
> ==================================================================
>
Hi Cedric,
> Cc: Troy Lee <troy_lee@aspeedtech.com>; nabihestefan@google.com
> Subject: Re: [PATCH v4 10/10] docs/system/arm/aspeed: Support vbootrom for
> AST2700
>
> Jamin,
>
> On 4/17/25 05:12, Jamin Lin wrote:
> > Using the vbootrom image support and the boot ROM binary is now passed
> > via the -bios option, using the image located in
> > pc-bios/ast27x0_bootrom.bin.
> >
> > Signed-off-by: Jamin Lin <jamin_lin@aspeedtech.com>
> > Reviewed-by: Nabih Estefan <nabihestefan@google.com>
> > ---
> > docs/system/arm/aspeed.rst | 29 ++++++++++++++++++++++++++++-
> > 1 file changed, 28 insertions(+), 1 deletion(-)
> >
> > diff --git a/docs/system/arm/aspeed.rst b/docs/system/arm/aspeed.rst
> > index 97fd6a0e7f..c87a2cf796 100644
> > --- a/docs/system/arm/aspeed.rst
> > +++ b/docs/system/arm/aspeed.rst
> > @@ -250,7 +250,14 @@ under Linux), use :
> > Booting the ast2700-evb machine
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
> Currently, we have 2 sections for the Aspeed boards :
>
> 1. Aspeed family boards (ast2500-evb, ast2600-evb, ast2700-evb, ast2700fc,
> bletchley-bmc, fuji-bmc, fby35-bmc, fp5280g2-bmc, g220a-bmc,
> palmetto-bmc, qcom-dc-scm-v1-bmc, qcom-firework-bmc, quanta-q71l-bmc,
> rainier-bmc, romulus-bmc, sonorapass-bmc, supermicrox11-bmc,
> supermicrox11spi-bmc, tiogapass-bmc, witherspoon-bmc, yosemitev2-bmc) 2.
> Aspeed minibmc family boards (ast1030-evb)
>
> The first is quite big and relatively consistent for the AST2400, AST2500 and
> AST2600 SoCs. Since the AST2700 SoC boards boot differently, I think it is time
> to introduce a new section for the ast2700 machines.
>
Thanks for review.
Will create a new section for the AST2700.
Jamin
>
> Thanks,
>
> C.
>
>
>
> > -Boot the AST2700 machine from the flash image, use an MTD drive :
> > +Boot the AST2700 machine from the flash image.
> > +
> > +There are two supported methods for booting the AST2700 machine with a
> flash image:
> > +
> > +Manual boot using ``-device loader``:
> > +
> > +It causes all 4 CPU cores to start execution from address
> > +``0x430000000``, which corresponds to the BL31 image load address.
> >
> > .. code-block:: bash
> >
> > @@ -270,6 +277,26 @@ Boot the AST2700 machine from the flash image,
> use an MTD drive :
> > -drive file=${IMGDIR}/image-bmc,format=raw,if=mtd \
> > -nographic
> >
> > +Boot using a virtual boot ROM (``-bios``):
> > +
> > +If users do not specify the ``-bios option``, QEMU will attempt to
> > +load the default vbootrom image ``ast27x0_bootrom.bin`` from either
> > +the current working directory or the ``pc-bios`` directory within the QEMU
> source tree.
> > +
> > +.. code-block:: bash
> > +
> > + $ qemu-system-aarch64 -M ast2700-evb \
> > + -drive file=image-bmc,format=raw,if=mtd \
> > + -nographic
> > +
> > +The ``-bios`` option allows users to specify a custom path for the
> > +vbootrom image to be loaded during boot. This will load the vbootrom
> > +image from the specified path in the ${HOME} directory.
> > +
> > +.. code-block:: bash
> > +
> > + -bios ${HOME}/ast27x0_bootrom.bin
> > +
> > Aspeed minibmc family boards (``ast1030-evb``)
> >
> ================================================================
> ==
> >
© 2016 - 2025 Red Hat, Inc.