summaryrefslogtreecommitdiff
path: root/docs/plat
diff options
context:
space:
mode:
authorDouglas Raillard <douglas.raillard@arm.com>2017-06-20 15:22:19 +0100
committerDouglas Raillard <douglas.raillard@arm.com>2017-06-29 11:02:54 +0100
commit7af4d2b6aeebbe621b3e7c54e09ecf38d130f266 (patch)
tree058e925f8245c8938b15ff59384ed761e0944e96 /docs/plat
parentaa5b843fe8f2d8cea80fd1c06e7fc6b7c18f265c (diff)
Fix various small issues in the documentation
Change some hard-to-convert constructs to cleaner ones. Fix a broken link. Change-Id: Ida70aa1da0af7a107b0e05eb20b8d46669a0380b Signed-off-by: Douglas Raillard <douglas.raillard@arm.com>
Diffstat (limited to 'docs/plat')
-rw-r--r--docs/plat/hikey.md184
-rw-r--r--docs/plat/hikey960.md215
-rw-r--r--docs/plat/nvidia-tegra.md8
3 files changed, 229 insertions, 178 deletions
diff --git a/docs/plat/hikey.md b/docs/plat/hikey.md
index a5e592bb..5e62a5bc 100644
--- a/docs/plat/hikey.md
+++ b/docs/plat/hikey.md
@@ -1,9 +1,9 @@
Description
====================
- HiKey is one of 96boards. Hisilicon Kirin6220 processor is installed on HiKey.
+HiKey is one of 96boards. Hisilicon Kirin6220 processor is installed on HiKey.
- More information are listed in [link](https://github.com/96boards/documentation/blob/master/ConsumerEdition/HiKey/Quickstart/README.md).
+More information are listed in [link](https://github.com/96boards/documentation/blob/master/ConsumerEdition/HiKey/Quickstart/README.md).
How to build
@@ -12,112 +12,136 @@ How to build
1. Code Locations
-----------------
- * ARM Trusted Firmware:
- [link](https://github.com/ARM-software/arm-trusted-firmware)
+ * ARM Trusted Firmware:
+ [link](https://github.com/ARM-software/arm-trusted-firmware)
- * edk2:
- [link](https://github.com/96boards-hikey/edk2/tree/testing/hikey960_v2.5)
+ * edk2:
+ [link](https://github.com/96boards-hikey/edk2/tree/testing/hikey960_v2.5)
- * OpenPlatformPkg:
- [link](https://github.com/96boards-hikey/OpenPlatformPkg/tree/testing/hikey960_v1.3.4)
+ * OpenPlatformPkg:
+ [link](https://github.com/96boards-hikey/OpenPlatformPkg/tree/testing/hikey960_v1.3.4)
- * l-loader:
- [link](https://github.com/96boards-hikey/l-loader/tree/testing/hikey960_v1.2)
+ * l-loader:
+ [link](https://github.com/96boards-hikey/l-loader/tree/testing/hikey960_v1.2)
- * uefi-tools:
- [link](https://github.com/96boards-hikey/uefi-tools/tree/testing/hikey960_v1)
+ * uefi-tools:
+ [link](https://github.com/96boards-hikey/uefi-tools/tree/testing/hikey960_v1)
- * atf-fastboot:
- [link](https://github.com/96boards-hikey/atf-fastboot/tree/master)
+ * atf-fastboot:
+ [link](https://github.com/96boards-hikey/atf-fastboot/tree/master)
2. Build Procedure
------------------
- * Fetch all the above repositories into local host.
- Make all the repositories in the same ${BUILD_PATH}.
-
- * Create the symbol link to OpenPlatformPkg in edk2.
- <br>`$cd ${BUILD_PATH}/edk2`</br>
- <br>`$ln -sf ../OpenPlatformPkg`</br>
-
- * Prepare AARCH64 && AARCH32 toolchain. Prepare python.
-
- * If your hikey hardware is built by CircuitCo, update _uefi-tools/platform.config_ first. _(optional)_
- <br>__Uncomment the below sentence. Otherwise, UEFI can't output messages on serial
- console on hikey.__</br>
- <br>`BUILDFLAGS=-DSERIAL_BASE=0xF8015000`</br>
- <br>If your hikey hardware is built by LeMarker, nothing to do.</br>
-
- * Build it as debug mode. Create your own build script file or you could refer to __build_uefi.sh__ in l-loader git repository.
- <br>`BUILD_OPTION=DEBUG`</br>
- <br>`export AARCH64_TOOLCHAIN=GCC5`</br>
- <br>`export UEFI_TOOLS_DIR=${BUILD_PATH}/uefi-tools`<br>
- <br>`export EDK2_DIR=${BUILD_PATH}/edk2`</br>
- <br>`EDK2_OUTPUT_DIR=${EDK2_DIR}/Build/HiKey/${BUILD_OPTION}_${AARCH64_TOOLCHAIN}`</br>
- <br>`# Build fastboot for ARM Trust Firmware. It's used for recovery mode.`</br>
- <br>`cd ${BUILD_PATH}/atf-fastboot`</br>
- <br>`CROSS_COMPILE=aarch64-linux-gnu- make PLAT=hikey DEBUG=1`</br>
- <br>`# Convert DEBUG/RELEASE to debug/release`</br>
- <br>`FASTBOOT_BUILD_OPTION=$(echo ${BUILD_OPTION} | tr '[A-Z]' '[a-z]')`</br>
- <br>`cd ${EDK2_DIR}`</br>
- <br>`# Build UEFI & ARM Trust Firmware`</br>
- <br>`${UEFI_TOOLS_DIR}/uefi-build.sh -b ${BUILD_OPTION} -a ../arm-trusted-firmware hikey`</br>
- <br>`# Generate l-loader.bin`</br>
- <br>`cd ${BUILD_PATH}/l-loader`</br>
- <br>`ln -sf ${EDK2_OUTPUT_DIR}/FV/bl1.bin`</br>
- <br>`ln -sf ${EDK2_OUTPUT_DIR}/FV/fip.bin`</br>
- <br>`ln -sf ${BUILD_PATH}/atf-fastboot/build/hikey/${FASTBOOT_BUILD_OPTION}/bl1.bin fastboot.bin`</br>
- <br>`python gen_loader.py -o l-loader.bin --img_bl1=bl1.bin --img_ns_bl1u=BL33_AP_UEFI.fd`</br>
- <br>`arm-linux-gnueabihf-gcc -c -o start.o start.S`</br>
- <br>`arm-linux-gnueabihf-ld -Bstatic -Tl-loader.lds -Ttext 0xf9800800 start.o -o loader`</br>
- <br>`arm-linux-gnueabihf-objcopy -O binary loader temp`</br>
- <br>`python gen_loader_hikey.py -o l-loader.bin --img_loader=temp --img_bl1=bl1.bin --img_ns_bl1u=fastboot.bin`</br>
-
- * Generate partition table for aosp. The eMMC capacity is either 4GB or 8GB. Just change "aosp-4g" to "linux-4g" for debian.
- <br>`$PTABLE=aosp-4g SECTOR_SIZE=512 bash -x generate_ptable.sh`</br>
+ * Fetch all the above repositories into local host.
+ Make all the repositories in the same ${BUILD_PATH}.
+
+ * Create the symbol link to OpenPlatformPkg in edk2.
+ ```shell
+ $cd ${BUILD_PATH}/edk2
+ $ln -sf ../OpenPlatformPkg
+ ```
+
+ * Prepare AARCH64 && AARCH32 toolchain. Prepare python.
+
+ * If your hikey hardware is built by CircuitCo, update _uefi-tools/platform.config_ first. _(optional)_
+ __Uncomment the below sentence. Otherwise, UEFI can't output messages on serial
+ console on hikey.__
+ ```shell
+ BUILDFLAGS=-DSERIAL_BASE=0xF8015000
+ ```
+ If your hikey hardware is built by LeMarker, nothing to do.
+
+ * Build it as debug mode. Create your own build script file or you could refer to __build_uefi.sh__ in l-loader git repository.
+ ```shell
+ BUILD_OPTION=DEBUG
+ export AARCH64_TOOLCHAIN=GCC5
+ export UEFI_TOOLS_DIR=${BUILD_PATH}/uefi-tools
+ export EDK2_DIR=${BUILD_PATH}/edk2
+ EDK2_OUTPUT_DIR=${EDK2_DIR}/Build/HiKey/${BUILD_OPTION}_${AARCH64_TOOLCHAIN}
+ # Build fastboot for ARM Trust Firmware. It's used for recovery mode.
+ cd ${BUILD_PATH}/atf-fastboot
+ CROSS_COMPILE=aarch64-linux-gnu- make PLAT=hikey DEBUG=1
+ # Convert DEBUG/RELEASE to debug/release
+ FASTBOOT_BUILD_OPTION=$(echo ${BUILD_OPTION} | tr '[A-Z]' '[a-z]')
+ cd ${EDK2_DIR}
+ # Build UEFI & ARM Trust Firmware
+ ${UEFI_TOOLS_DIR}/uefi-build.sh -b ${BUILD_OPTION} -a ../arm-trusted-firmware hikey
+ # Generate l-loader.bin
+ cd ${BUILD_PATH}/l-loader
+ ln -sf ${EDK2_OUTPUT_DIR}/FV/bl1.bin
+ ln -sf ${EDK2_OUTPUT_DIR}/FV/fip.bin
+ ln -sf ${BUILD_PATH}/atf-fastboot/build/hikey/${FASTBOOT_BUILD_OPTION}/bl1.bin fastboot.bin
+ python gen_loader.py -o l-loader.bin --img_bl1=bl1.bin --img_ns_bl1u=BL33_AP_UEFI.fd
+ arm-linux-gnueabihf-gcc -c -o start.o start.S
+ arm-linux-gnueabihf-ld -Bstatic -Tl-loader.lds -Ttext 0xf9800800 start.o -o loader
+ arm-linux-gnueabihf-objcopy -O binary loader temp
+ python gen_loader_hikey.py -o l-loader.bin --img_loader=temp --img_bl1=bl1.bin --img_ns_bl1u=fastboot.bin
+ ```
+
+ * Generate partition table for aosp. The eMMC capacity is either 4GB or 8GB. Just change "aosp-4g" to "linux-4g" for debian.
+ ```shell
+ $PTABLE=aosp-4g SECTOR_SIZE=512 bash -x generate_ptable.sh
+ ```
3. Setup Console
----------------
- * Install ser2net. Use telnet as the console since UEFI fails to display Boot Manager GUI in minicom. __If you don't need Boot Manager GUI, just ignore this section.__
- <br>`$sudo apt-get install ser2net`</br>
+ * Install ser2net. Use telnet as the console since UEFI fails to display Boot Manager GUI in minicom. __If you don't need Boot Manager GUI, just ignore this section.__
+ ```shell
+ $sudo apt-get install ser2net
+ ```
- * Configure ser2net.
- <br>`$sudo vi /etc/ser2net.conf`</br>
- <br>Append one line for serial-over-USB in below.</br>
- <br>_#ser2net.conf_</br>
- <br>`2004:telnet:0:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT banner`</br>
+ * Configure ser2net.
+ ```shell
+ $sudo vi /etc/ser2net.conf
+ ```
- * Open the console.
- <br>`$telnet localhost 2004`</br>
- <br>And you could open the console remotely, too.</br>
+ Append one line for serial-over-USB in below.
+ _#ser2net.conf_
+ ```shell
+ 2004:telnet:0:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT banner
+ ```
+
+ * Open the console.
+ ```shell
+ $telnet localhost 2004
+ ```
+
+ And you could open the console remotely, too.
4. Flush images in recovery mode
-----------------------------
- * Make sure Pin3-Pin4 on J15 are connected for recovery mode. Then power on HiKey.
+ * Make sure Pin3-Pin4 on J15 are connected for recovery mode. Then power on HiKey.
- * Remove the modemmanager package. This package may cause the idt tool failure.
- <br>`$sudo apt-get purge modemmanager`</br>
+ * Remove the modemmanager package. This package may cause the idt tool failure.
+ ```shell
+ $sudo apt-get purge modemmanager
+ ```
- * Run the command to download l-loader.bin into HiKey.
- <br>`$sudo python hisi-idt.py -d /dev/ttyUSB1 --img1 l-loader.bin`</br>
+ * Run the command to download l-loader.bin into HiKey.
+ ```shell
+ $sudo python hisi-idt.py -d /dev/ttyUSB1 --img1 l-loader.bin
+ ```
- * Update images. All aosp or debian images could be fetched from [link](https://builds.96boards.org/).
- <br>`$sudo fastboot flash ptable prm_ptable.img`</br>
- <br>`$sudo fastboot flash fastboot fip.bin`</br>
- <br>`$sudo fastboot flash boot boot.img`</br>
- <br>`$sudo fastboot flash cache cache.img`</br>
- <br>`$sudo fastboot flash system system.img`</br>
- <br>`$sudo fastboot flash userdata userdata.img`</br>
+ * Update images. All aosp or debian images could be fetched from [link](https://builds.96boards.org/).
+ ```shell
+ $sudo fastboot flash ptable prm_ptable.img
+ $sudo fastboot flash fastboot fip.bin
+ $sudo fastboot flash boot boot.img
+ $sudo fastboot flash cache cache.img
+ $sudo fastboot flash system system.img
+ $sudo fastboot flash userdata userdata.img
+ ```
5. Boot UEFI in normal mode
-----------------------------
- * Make sure Pin3-Pin4 on J15 are open for normal boot mode. Then power on HiKey.
+ * Make sure Pin3-Pin4 on J15 are open for normal boot mode. Then power on HiKey.
- * Reference [link](https://github.com/96boards-hikey/tools-images-hikey960/blob/master/build-from-source/README-ATF-UEFI-build-from-source.md)
+ * Reference [link](https://github.com/96boards-hikey/tools-images-hikey960/blob/master/build-from-source/README-ATF-UEFI-build-from-source.md)
diff --git a/docs/plat/hikey960.md b/docs/plat/hikey960.md
index 786a54b9..8442a189 100644
--- a/docs/plat/hikey960.md
+++ b/docs/plat/hikey960.md
@@ -1,9 +1,9 @@
Description
====================
- HiKey960 is one of 96boards. Hisilicon Hi3660 processor is installed on HiKey960.
+HiKey960 is one of 96boards. Hisilicon Hi3660 processor is installed on HiKey960.
- More information are listed in [link](http://www.96boards.org/documentation/ConsumerEdition/HiKey960/README.md).
+More information are listed in [link](http://www.96boards.org/documentation/ConsumerEdition/HiKey960/README.md).
How to build
@@ -12,123 +12,148 @@ How to build
1. Code Locations
-----------------
- * ARM Trusted Firmware:
- [link](https://github.com/ARM-software/arm-trusted-firmware)
+ * ARM Trusted Firmware:
+ [link](https://github.com/ARM-software/arm-trusted-firmware)
- * edk2:
- [link](https://github.com/96boards-hikey/edk2/tree/testing/hikey960_v2.5)
+ * edk2:
+ [link](https://github.com/96boards-hikey/edk2/tree/testing/hikey960_v2.5)
- * OpenPlatformPkg:
- [link](https://github.com/96boards-hikey/OpenPlatformPkg/tree/testing/hikey960_v1.3.4)
+ * OpenPlatformPkg:
+ [link](https://github.com/96boards-hikey/OpenPlatformPkg/tree/testing/hikey960_v1.3.4)
- * l-loader:
- [link](https://github.com/96boards-hikey/l-loader/tree/testing/hikey960_v1.2)
+ * l-loader:
+ [link](https://github.com/96boards-hikey/l-loader/tree/testing/hikey960_v1.2)
- * uefi-tools:
- [link](https://github.com/96boards-hikey/uefi-tools/tree/hikey960_v1)
+ * uefi-tools:
+ [link](https://github.com/96boards-hikey/uefi-tools/tree/hikey960_v1)
2. Build Procedure
------------------
- * Fetch all the above 5 repositories into local host.
- Make all the repositories in the same ${BUILD_PATH}.
-
- * Create the symbol link to OpenPlatformPkg in edk2.
- <br>`$cd ${BUILD_PATH}/edk2`</br>
- <br>`$ln -sf ../OpenPlatformPkg`</br>
-
- * Prepare AARCH64 toolchain.
-
- * If your hikey960 hardware is v1, update _uefi-tools/platform.config_ first. _(optional)_
- <br>__Uncomment the below sentence. Otherwise, UEFI can't output messages on serial
- console on hikey960 v1.__</br>
- <br>`BUILDFLAGS=-DSERIAL_BASE=0xFDF05000`</br>
- <br>If your hikey960 hardware is v2 or newer, nothing to do.</br>
-
- * Build it as debug mode. Create script file for build.
- <br>`BUILD_OPTION=DEBUG`</br>
- <br>`export AARCH64_TOOLCHAIN=GCC48`</br>
- <br>`export UEFI_TOOLS_DIR=${BUILD_PATH}/uefi-tools`<br>
- <br>`export EDK2_DIR=${BUILD_PATH}/edk2`</br>
- <br>`EDK2_OUTPUT_DIR=${EDK2_DIR}/Build/HiKey960/${BUILD_OPTION}_${AARCH64_TOOLCHAIN}`</br>
- <br>`cd ${EDK2_DIR}`</br>
- <br>`# Build UEFI & ARM Trust Firmware`</br>
- <br>`${UEFI_TOOLS_DIR}/uefi-build.sh -b ${BUILD_OPTION} -a ../arm-trusted-firmware hikey960`</br>
- <br>`# Generate l-loader.bin`</br>
- <br>`cd ${BUILD_PATH}/l-loader`</br>
- <br>`ln -sf ${EDK2_OUTPUT_DIR}/FV/bl1.bin`</br>
- <br>`ln -sf ${EDK2_OUTPUT_DIR}/FV/fip.bin`</br>
- <br>`ln -sf ${EDK2_OUTPUT_DIR}/FV/BL33_AP_UEFI.fd`</br>
- <br>`python gen_loader.py -o l-loader.bin --img_bl1=bl1.bin --img_ns_bl1u=BL33_AP_UEFI.fd`</br>
-
- * Generate partition table.
- <br>_Make sure that you're using the sgdisk in the l-loader directory._</br>
- <br>`$PTABLE=aosp-32g SECTOR_SIZE=4096 SGDISK=./sgdisk bash -x generate_ptable.sh`</br>
+ * Fetch all the above 5 repositories into local host.
+ Make all the repositories in the same ${BUILD_PATH}.
+
+ * Create the symbol link to OpenPlatformPkg in edk2.
+ ```shell
+ $cd ${BUILD_PATH}/edk2
+ $ln -sf ../OpenPlatformPkg
+ ```
+
+ * Prepare AARCH64 toolchain.
+
+ * If your hikey960 hardware is v1, update _uefi-tools/platform.config_ first. _(optional)_
+ __Uncomment the below sentence. Otherwise, UEFI can't output messages on serial
+ console on hikey960 v1.__
+ ```shell
+ BUILDFLAGS=-DSERIAL_BASE=0xFDF05000
+ ```
+ If your hikey960 hardware is v2 or newer, nothing to do.
+
+ * Build it as debug mode. Create script file for build.
+ ```shell
+ BUILD_OPTION=DEBUG
+ export AARCH64_TOOLCHAIN=GCC48
+ export UEFI_TOOLS_DIR=${BUILD_PATH}/uefi-tools
+ export EDK2_DIR=${BUILD_PATH}/edk2
+ EDK2_OUTPUT_DIR=${EDK2_DIR}/Build/HiKey960/${BUILD_OPTION}_${AARCH64_TOOLCHAIN}
+ cd ${EDK2_DIR}
+ # Build UEFI & ARM Trust Firmware
+ ${UEFI_TOOLS_DIR}/uefi-build.sh -b ${BUILD_OPTION} -a ../arm-trusted-firmware hikey960
+ # Generate l-loader.bin
+ cd ${BUILD_PATH}/l-loader
+ ln -sf ${EDK2_OUTPUT_DIR}/FV/bl1.bin
+ ln -sf ${EDK2_OUTPUT_DIR}/FV/fip.bin
+ ln -sf ${EDK2_OUTPUT_DIR}/FV/BL33_AP_UEFI.fd
+ python gen_loader.py -o l-loader.bin --img_bl1=bl1.bin --img_ns_bl1u=BL33_AP_UEFI.fd
+ ```
+
+ * Generate partition table.
+ _Make sure that you're using the sgdisk in the l-loader directory._
+ ```shell
+ $PTABLE=aosp-32g SECTOR_SIZE=4096 SGDISK=./sgdisk bash -x generate_ptable.sh
+ ```
3. Setup Console
----------------
- * Install ser2net. Use telnet as the console since UEFI will output window
- that fails to display in minicom.
- <br>`$sudo apt-get install ser2net`</br>
+ * Install ser2net. Use telnet as the console since UEFI will output window
+ that fails to display in minicom.
+ ```shell
+ $sudo apt-get install ser2net
+ ```
- * Configure ser2net.
- <br>`$sudo vi /etc/ser2net.conf`</br>
- <br>Append one line for serial-over-USB in below.</br>
- <br>_#ser2net.conf_</br>
- <br>`2004:telnet:0:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT banner`</br>
+ * Configure ser2net.
+ ```shell
+ $sudo vi /etc/ser2net.conf
+ ```
+ Append one line for serial-over-USB in _#ser2net.conf_
+ ```
+ 2004:telnet:0:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT banner
+ ```
- * Open the console.
- <br>`$telnet localhost 2004`</br>
- <br>And you could open the console remotely, too.</br>
+ * Open the console.
+ ```shell
+ $telnet localhost 2004
+ ```
+ And you could open the console remotely, too.
4. Boot UEFI in recovery mode
-----------------------------
- * Fetch that are used in recovery mode. The code location is in below.
- [link](https://github.com/96boards-hikey/tools-images-hikey960)
-
- * Generate l-loader.bin.
- <br>`$cd tools-images-hikey960`</br>
- <br>`$ln -sf ${BUILD_PATH}/l-loader/l-loader.bin`</br>
-
- * Prepare config file.
- <br>_$vi config_</br>
- <br>_# The content of config file_</br>
- <br>`./sec_user_xloader.img 0x00020000`</br>
- <br>`./sec_uce_boot.img 0x6A908000`</br>
- <br>`./l-loader.bin 0x1AC00000`</br>
-
- * Remove the modemmanager package. This package may causes hikey_idt tool failure.
- <br>`$sudo apt-get purge modemmanager`</br>
-
- * Run the command to download l-loader.bin into HiKey960.
- <br>`$sudo ./hikey_idt -c config -p /dev/ttyUSB1`</br>
-
- * UEFI running in recovery mode.
- <br>When prompt '.' is displayed on console, press hotkey 'f' in keyboard. Then Android fastboot app is running.</br>
- <br>The timeout of prompt '.' is 10 seconds.</br>
-
- * Update images.
- <br>`$sudo fastboot flash ptable prm_ptable.img`</br>
- <br>`$sudo fastboot flash xloader sec_xloader.img`</br>
- <br>`$sudo fastboot flash fastboot l-loader.bin`</br>
- <br>`$sudo fastboot flash fip fip.bin`</br>
- <br>`$sudo fastboot flash boot boot.img`</br>
- <br>`$sudo fastboot flash cache cache.img`</br>
- <br>`$sudo fastboot flash system system.img`</br>
- <br>`$sudo fastboot flash userdata userdata.img`</br>
-
- * Notice: UEFI could also boot kernel in recovery mode, but BL31 isn't loaded in
- recovery mode.
+ * Fetch that are used in recovery mode. The code location is in below.
+ [link](https://github.com/96boards-hikey/tools-images-hikey960)
+
+ * Generate l-loader.bin.
+ ```shell
+ $cd tools-images-hikey960
+ $ln -sf ${BUILD_PATH}/l-loader/l-loader.bin
+ ```
+
+ * Prepare config file.
+ ```shell
+ $vi config
+ # The content of config file
+ ./sec_user_xloader.img 0x00020000
+ ./sec_uce_boot.img 0x6A908000
+ ./l-loader.bin 0x1AC00000
+ ```
+
+ * Remove the modemmanager package. This package may causes hikey_idt tool failure.
+ ```shell
+ $sudo apt-get purge modemmanager
+ ```
+
+ * Run the command to download l-loader.bin into HiKey960.
+ ```shell
+ $sudo ./hikey_idt -c config -p /dev/ttyUSB1
+ ```
+
+ * UEFI running in recovery mode.
+ When prompt '.' is displayed on console, press hotkey 'f' in keyboard. Then Android fastboot app is running.
+ The timeout of prompt '.' is 10 seconds.
+
+ * Update images.
+ ```shell
+ $sudo fastboot flash ptable prm_ptable.img
+ $sudo fastboot flash xloader sec_xloader.img
+ $sudo fastboot flash fastboot l-loader.bin
+ $sudo fastboot flash fip fip.bin
+ $sudo fastboot flash boot boot.img
+ $sudo fastboot flash cache cache.img
+ $sudo fastboot flash system system.img
+ $sudo fastboot flash userdata userdata.img
+ ```
+
+ * Notice: UEFI could also boot kernel in recovery mode, but BL31 isn't loaded in
+ recovery mode.
5. Boot UEFI in normal mode
-----------------------------
- * Make sure "Boot Mode" switch is OFF for normal boot mode. Then power on HiKey960.
+ * Make sure "Boot Mode" switch is OFF for normal boot mode. Then power on HiKey960.
- * Reference [link](https://github.com/96boards-hikey/tools-images-hikey960/blob/master/build-from-source/README-ATF-UEFI-build-from-source.md)
+ * Reference [link](https://github.com/96boards-hikey/tools-images-hikey960/blob/master/build-from-source/README-ATF-UEFI-build-from-source.md)
diff --git a/docs/plat/nvidia-tegra.md b/docs/plat/nvidia-tegra.md
index b45fec6e..3cb16827 100644
--- a/docs/plat/nvidia-tegra.md
+++ b/docs/plat/nvidia-tegra.md
@@ -56,10 +56,12 @@ without changing any makefiles.
Preparing the BL31 image to run on Tegra SoCs
===================================================
-'CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf- make PLAT=tegra \
-TARGET_SOC=<target-soc e.g. t210|t132> SPD=<dispatcher e.g. tlkd> bl31'
+```shell
+CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf- make PLAT=tegra \
+TARGET_SOC=<target-soc e.g. t210|t132> SPD=<dispatcher e.g. tlkd> bl31
+```
-Platforms wanting to use different TZDRAM_BASE, can add 'TZDRAM_BASE=<value>'
+Platforms wanting to use different TZDRAM_BASE, can add `TZDRAM_BASE=<value>`
to the build command line.
The Tegra platform code expects a pointer to the following platform specific