ArmVirtPkg: ArmVirtQemu: expose only 64-bit entry point for v3.0+ SMBIOS

[mirror_edk2.git] / ArmPlatformPkg / ArmVExpressPkg / Scripts / uefi-aarch64-bootstrap / readme.html

<h1>AArch64 UEFI bootstraps</h1>\r
\r
<p>Copyright (c) 2011-2013 ARM Limited. All rights reserved.\r
See the <code>LICENSE.TXT</code> file for more information.</p>\r
\r
<p>Contents:</p>\r
\r
<ul>\r
<li>Introduction</li>\r
<li>Build</li>\r
<li>Use on ARMv8 RTSM and FVP models</li>\r
<li>Use on ARMv8 Foundation model</li>\r
</ul>\r
\r
<h2>Introduction</h2>\r
\r
<p>A bootstrap can be used to change the model state, like the Exception\r
Level (EL), before executing the UEFI binary.</p>\r
\r
<p>For the ARMv8 RTSM and FVP models this can be used to show/test the UEFI binary\r
starting at different exception levels. The ARMv8 models start at EL3 by\r
default.</p>\r
\r
<p>In the case of the Foundation model a bootstrap is required to jump to the\r
UEFI binary as loaded in RAM. This is required as the Foundation model cannot\r
load and execute UEFI binaries directly. The Foundation model can only load and\r
execute ELF binaries.</p>\r
\r
<h2>Build</h2>\r
\r
<p>Build the bootstraps using a AArch64 GCC cross-compiler. By default the\r
<code>Makefile</code> is configured to assume a GCC bare-metal toolchain:</p>\r
\r
<pre><code>PATH=$PATH:&lt;path/to/baremetal-tools/bin/&gt; make clean\r
PATH=$PATH:&lt;path/to/baremetal-tools/bin/&gt; make\r
</code></pre>\r
\r
<p>To build the bootstraps with a Linux GCC toolchain use the following\r
commands:</p>\r
\r
<pre><code>PATH=$PATH:&lt;path/to/aarch64-linux-gnu-tools/bin/&gt; make clean\r
PATH=$PATH:&lt;path/to/aarch64-linux-gnu-tools/bin/&gt; CROSS_COMPILE=&lt;gcc-prefix&gt; make\r
</code></pre>\r
\r
<p>The <code>gcc-prefix</code> depends on the specific toolchain distribution used. It can be\r
"aarch64-linux-gnu-" for example.</p>\r
\r
<p>This will result in four <code>axf</code> files:</p>\r
\r
<ul>\r
<li><p>uefi-bootstrap-el3 : The bootstrap jumps to the UEFI code in FLASH without\r
                 changing anything.</p></li>\r
<li><p>uefi-bootstrap-el2 : Setup EL3 and switch the model to EL2 before jumping to the\r
                 UEFI code in FLASH.</p></li>\r
<li><p>uefi-bootstrap-el1 : Setup EL3 and prepare to run at non-secure EL1. Switch to\r
                 non-secure EL1 and run the UEFI code in FLASH.</p></li>\r
<li><p>uefi-bootstrap-el3-foundation : The bootstrap jumps to the UEFI code in RAM\r
                 without changing anything. Only to be used with the\r
                 Foundation model. The Foundation model does not have\r
                 non-secure memory at address <code>0x0</code> and thus the UEFI image\r
                 should be pre-loaded into non-secure RAM at address\r
                 <code>0xA0000000</code>.</p></li>\r
</ul>\r
\r
<h2>Use on ARMv8 RTSM and FVP models</h2>\r
\r
<p>Add the '-a' option to the model start script and point to the required\r
bootstrap:</p>\r
\r
<pre><code>&lt; ... model start script as described in top-level readme file ... &gt;\r
 -a &lt;path/to/bootstrap-binary-file&gt;\r
</code></pre>\r
\r
<p>NOTE: The Foundation model bootstrap should not be used with these models.</p>\r
\r
<h2>Use on ARMv8 Foundation model</h2>\r
\r
<p>The Foundation model takes an option for an ELF file to be loaded as well as an\r
option to load a binary data blob into RAM. This can be used to run UEFI in the\r
following manner:</p>\r
\r
<pre><code>&lt;PATH_TO_INSTALLED_FOUNDATION_MODEL&gt;/Foundation_v8 --cores=2 --visualization\r
  --image=uefi-bootstrap-el3-foundation.axf --nsdata=RTSM_VE_FOUNDATIONV8_EFI.fd@0xA0000000\r
</code></pre>\r
\r
<p>NOTE: The RTSM version of the bootstraps and UEFI image will not work as\r
      expected on the Foundation model. Foundation model specific versions\r
      should be used.</p>\r