Commit 97673430 authored by Selvarasu Ganesan's avatar Selvarasu Ganesan Committed by Deepak Pandey
Browse files

docs/aemfvp-a: Update the explanation of the model terminals



Update the explanation of the model terminals and also add the
information about the log files that will be generated during boot.
Signed-off-by: Selvarasu Ganesan's avatarSelvarasu Ganesan <selvarasu.ganesan@arm.com>
Change-Id: Ib896e2477a7a1ddbc23567c5c939db813bd792f2
parent 7a967a4b
......@@ -220,24 +220,36 @@ Example commands for booting Busybox are listed below.
./model-scripts/aemfvp-a/boot.sh -p aemfvp-a -b [uefi|u-boot] -n true
Note: If the user stops autoboot while booting with U-Boot with Busybox and
enters the U-Boot command line console, the user must run the following
commands to continue the boot process or exit from the U-Boot command line
console.
Note: If the user stops autoboot while booting with U-Boot and enters the
U-Boot command line console, the user must run the following command to
continue the boot process.
::
run bootcmd
Command to exit from the command line console.
::
Ctrl + ]
telnet> close
When the script is executed, three terminal instances will be launched, one for
the SCP and two for the AP (Application Processor). The SCP will not be used in
booting of Armv-A Base AEM FVP. The AP will start booting Trusted Firmware-A,
followed by UEFI/U-Boot, and then BusyBox.
When the script is executed, four terminal instances will be launched. The
usage of each terminal can be seen below,
- Terminal-0 is the debug console for the AP (Application Processor) and
contains the booting logs of Trusted firmware-A, U-Boot, Linux, and
user-space applications.
- Terminal-1 is the debug console for the AP (Application Processor) and
contains the UEFI boot logs.
- Terminal-2 is the debug console that displays the localhost information.
- The fourth Terminal uses the GUI representation of the model, which
contains information about the overall executed instructions of the
CPUs and the status of each CPU in the clusters.
The AP will start booting Trusted Firmware-A, followed by UEFI/U-Boot, Linux,
and then BusyBox.
To run terminal-only mode on hosts without graphics/display:
......@@ -258,7 +270,13 @@ To stop the model, exit telnet:
Note: The boot logs can be found at ``<aemfvp-a_workspace>/aemfvp-a`` path after
booting busybox.
booting busybox. The following logs are generated in this path.
- uart0.log: Terminal-0 debug console logs are stored in the uart0.log
file. It is a symbolic link for uart0 log file with the latest timestamp.
- uart1.log: Terminal-1 debug console logs are stored in the uart1.log
file. It is a symbolic link for uart1 log file with the latest timestamp.
--------------
......
......@@ -227,10 +227,21 @@ Example commands to boot a Linux distribution are listed below.
./model-scripts/aemfvp-a/distro.sh -p aemfvp-a -d /absolute/path/to/fedora.satadisk
When the script is executed, three terminal instances will be launched, one for
the SCP and two for the AP (Application Processor). The SCP will not be used in
booting of Armv-A Base AEM FVP. The AP will start booting Trusted Firmware-A,
then UEFI, then Distribution.
When the script is executed, four terminal instances will be launched. The
usage of each terminal can be seen below,
- Terminal-0 is the debug console for the AP (Application Processor) and
contains the booting logs of Trusted firmware-A, Linux, and user-space
applications.
- Terminal-1 is the debug console for the AP (Application Processor) and
contains the UEFI boot logs.
- Terminal-2 is the debug console that displays the localhost information.
- The fourth Terminal uses the GUI representation of the model, which
contains information about the overall executed instructions of the
CPUs and the status of each CPU in the clusters.
The AP will start booting Trusted Firmware-A, followed by UEFI, Linux, and then
Distribution.
To run terminal-only mode on hosts without graphics/display:
......@@ -251,7 +262,12 @@ To stop the model, exit telnet:
Note: The boot logs can be found at ``<aemfvp-a_workspace>/aemfvp-a`` path after
booting distribution.
booting distribution. The following logs are generated in this path.
- uart0.log: Terminal-0 debug console logs are stored in the uart0.log
file. It is a symbolic link for uart0 log file with the latest timestamp.
- uart1.log: Terminal-1 debug console logs are stored in the uart1.log
file. It is a symbolic link for uart1 log file with the latest timestamp.
--------------
......
......@@ -85,7 +85,7 @@ This section explains the procedure to sync the software stack.
repo init \
-u https://git.gitlab.arm.com/arm-reference-solutions/arm-reference-solutions-manifest.git \
-m pinned-aemfvp-a.xml \
-b refs/tags/AEMFVP-A-2021.09.20
-b refs/tags/AEMFVP-A-2021.09.20 --depth=1
repo sync
......@@ -94,10 +94,9 @@ This section explains the procedure to sync the software stack.
repo init command will fail to complete. Refer to the `troubleshooting guide`_
for resolving this issue.
Note: To reduce the size of the commit history that is downloaded (and reduce
the time taken to download the platform software stack), append "--depth=1"
to the repo init command.
Note: To fetch the entire commit history that is being downloaded, remove
``--depth=1`` from the repo init command. This will increase the time taken
to download the platform software stack.
Verify prerequisites
====================
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment