[bootlin/training-materials updates] master: labs/sysdev-u-boot-beagleplay: misc fixes (a3eab62b)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/a3eab62b72f05f22ac40a602c5ee70882e93bf14

>---------------------------------------------------------------

commit a3eab62b72f05f22ac40a602c5ee70882e93bf14
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Wed Jul 26 11:34:30 2023 +0200

    labs/sysdev-u-boot-beagleplay: misc fixes
    
    - In English, we usually use "32 bit CPU" or "32-bit CPU"
      instead of "32 bits CPU"
      Example: https://en.wikipedia.org/wiki/32-bit_computing
    
    - Remove unnecessary spaces at the end of lines. That's
      distracting (my vim setup flags this).
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

a3eab62b72f05f22ac40a602c5ee70882e93bf14
 .../sysdev-u-boot-beagleplay.tex                   | 32 +++++++++++-----------
 1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/labs/sysdev-u-boot-beagleplay/sysdev-u-boot-beagleplay.tex b/labs/sysdev-u-boot-beagleplay/sysdev-u-boot-beagleplay.tex
index 51fc7b84..9e11df25 100644
--- a/labs/sysdev-u-boot-beagleplay/sysdev-u-boot-beagleplay.tex
+++ b/labs/sysdev-u-boot-beagleplay/sysdev-u-boot-beagleplay.tex
@@ -41,7 +41,7 @@ If the \code{USR/BOOT} key is pressed, then it will try to find a bootloader
 on the microSD.
 
 {\bf Warning}: In this tutorial we will boot exclusively on the SD card. Therefore
-we will \textbf{ALWAYS} press the \code{USR/BOOT} key during startup ! 
+we will \textbf{ALWAYS} press the \code{USR/BOOT} key during startup!
 
 Go to the \code{$HOME/__SESSION_NAME__-labs/bootloader} directory.
 
@@ -115,9 +115,9 @@ safety use cases. This domain is controlled by a Cortex-M4F processor.
 Finally, we have the WKUP domain which, as its name suggests, is used during
 deepsleep mode and is controlled by a Cortex-R5F processor.
 
-\textbf{Note :} The Cortex-R5F and the Cortex-M4F are 32 bits processors
-(in opposition to 64bits Cortex-A53 processors) and will therefore need
-a 32bits toolchain.
+\textbf{Note :} The Cortex-R5F and the Cortex-M4F are 32 bit processors
+(in opposition to 64 bit Cortex-A53 processors) and will therefore need
+a 32 bit toolchain.
 
 The purpose of the AM62x SoC boot process is to initialize all the required
 peripherals and processors in different steps we are about to describe :
@@ -139,11 +139,11 @@ will then load the complete U-Boot image.
 The Following Process Flow can be viewed at the following address :
 \url{https://u-boot.readthedocs.io/en/latest/board/ti/am62x_sk.html}
 
-\section{Get and install the 32 bits toolchain}
+\section{Get and install the 32 bit toolchain}
 
-As the AM62x is using 32bits processors we will need a specific toolchain 
-to perform cross-compilation of 32 bits firmware.
-Although we could use Crosstool-ng to compile this 32 bits toolchain, we will use
+As the AM62x is using 32 bit processors we will need a specific toolchain
+to perform cross-compilation of 32 bit firmware.
+Although we could use Crosstool-ng to compile this 32 bit toolchain, we will use
 a precompiled one in order to save compilation time.
 To do so, we will get this toolchain from the official ARM website\footnote{You can download precompiled ARM toolchains for other
 target architecture on the following link \url{https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads/}}.
@@ -158,7 +158,7 @@ Let's download and untar it:
 Doesn't forget to add \code{$HOME/x-tools/arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi/bin/}
 to your \code{PATH} environment variable.
 
-Now our 32 bits toolchain is installed into \code{$HOME/x-tools} directory !
+Now our 32 bit toolchain is installed into \code{$HOME/x-tools} directory !
 
 \section{Configure U-Boot for R5 Processor}
 
@@ -188,7 +188,7 @@ Basically, you need to:
 \item Specify the cross-compiler prefix
 (the part before \code{gcc} in the cross-compiler executable name):
 \bashcmd{$ export CROSS_COMPILE=arm-none-eabi-}
-and the architecture type (we are building for the R5, 32 bits Proc):
+and the architecture type (we are building for the R5, 32 bit Proc):
 \bashcmd{$ export ARCH=arm}
 
 \item Run \inlinebash{$ ls configs/ | grep am62x} to see all predefined
@@ -334,9 +334,9 @@ So the resulting make command is:
 
 % Several configuration parameters have to be passed to the Makefile:
 % \begin{itemize}
-% \item Specify the 32 bits cross-compiler prefix \code{CROSS_COMPILE=arm-none-eabi-}
-% \item Specify the 64 bits cross-compiler prefix \code{CROSS_COMPILE64=aarch64-linux-}
-% \item In order to indicates that our SoC supports both 64 and 32 bits builds,
+% \item Specify the 32 bit cross-compiler prefix \code{CROSS_COMPILE=arm-none-eabi-}
+% \item Specify the 64 bit cross-compiler prefix \code{CROSS_COMPILE64=aarch64-linux-}
+% \item In order to indicates that our SoC supports both 64 and 32 bit builds,
 %       we need to set \code{CFG_ARM64_core=y}
 % \item The AM62x SoC platform which is the k3 family is selected
 %       too with \code{PLATFORM=k3}
@@ -520,10 +520,10 @@ now be mounted on \code{/media/$USER/boot}.
 Now, copy the \code{tiboot3.bin} image into the SD card,
 \code{tiboot3.bin} is located in the
 \code{$HOME/__SESSION_NAME__-labs/bootloader/k3-image-gen}
-folder and contains the 32 bits binaries.
+folder and contains the 32 bit binaries.
 
 Next, copy both the \code{tispl.bin} and \code{u-boot.img} files.
-This time, the images contains 64 bits binaires, and therefore are contained
+This time, the images contains 64 bit binaires, and therefore are contained
 in the \code{$HOME/__SESSION_NAME__-labs/bootloader/build_uboot/a53}
 folder.
 
@@ -597,7 +597,7 @@ Press SPACE to abort autoboot in 2 seconds
 The code above shows us the main steps of the boot process.
 First we can see that the SPL bootloader as been loaded by the R5.
 Next the TF-A (ATF) is loaded and we jump into the normal boot world.
-Finally, the 64 bits U-Boot SPL is loaded which load U-Boot itself.
+Finally, the 64 bit U-Boot SPL is loaded which load U-Boot itself.
 
 \textbf{Note:} We can see that the R5 U-Boot SPL skips the 'tee'
 image. This is because we chose to not use OPTEE in order