[bootlin/training-materials updates] master: yocto: Fix a few typos in the STM32 variant of the YP training (ba08e064)

Maxime Chevallier maxime.chevallier at bootlin.com
Fri Oct 4 16:25:56 CEST 2019

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


commit ba08e064f05154daf1a2b6aba6ce632aaddf4b9e
Author: Maxime Chevallier <maxime.chevallier at bootlin.com>
Date:   Fri Oct 4 16:25:56 2019 +0200

    yocto: Fix a few typos in the STM32 variant of the YP training
    Signed-off-by: Maxime Chevallier <maxime.chevallier at bootlin.com>


 labs/yocto-custom-machine/yocto-custom-machine.tex       | 4 ++--
 labs/yocto-first-build-stm32/yocto-first-build-stm32.tex | 4 ++--
 labs/yocto-layer/yocto-layer.tex                         | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/labs/yocto-custom-machine/yocto-custom-machine.tex b/labs/yocto-custom-machine/yocto-custom-machine.tex
index 8651ca80..7340ac69 100644
--- a/labs/yocto-custom-machine/yocto-custom-machine.tex
+++ b/labs/yocto-custom-machine/yocto-custom-machine.tex
@@ -11,7 +11,7 @@ During this lab, you will:
 The machine file configures various hardware related settings. That's
 what we did in lab1, when we chose the \ifdefstring{\labboard}{discovery}
-{\code{stm32mp1-disco}} {\code{beaglebone}} one. While it
+{\code{stm32mp1}} {\code{beaglebone}} one. While it
 is not necessary to make our custom machine image here, we'll create a
 new one to demonstrate the process.
@@ -26,7 +26,7 @@ tune and is a part of the \code{stm32mp} SoC family. Add the following
 lines to your machine configuration file:
-include conf/machine/include/st-machine-common-stm32mp.inc
+require conf/machine/include/st-machine-common-stm32mp.inc
 DEFAULTTUNE = "cortexa7thf-neon-vfpv4"
 require conf/machine/include/tune-cortexa7.inc
diff --git a/labs/yocto-first-build-stm32/yocto-first-build-stm32.tex b/labs/yocto-first-build-stm32/yocto-first-build-stm32.tex
index 9cb84a2c..24135520 100644
--- a/labs/yocto-first-build-stm32/yocto-first-build-stm32.tex
+++ b/labs/yocto-first-build-stm32/yocto-first-build-stm32.tex
@@ -61,7 +61,7 @@ package work directory once a package is built.
 Don't forget to make the configuration aware of the OpenEmbedded and
 STM32MP layer. Edit the layer configuration file
 (\code{$BUILDDIR/conf/bblayers.conf}) and append the full path to the
-\code{meta-openembedded} and \code{meta-st-stm32mp} directory to the
+\code{meta-openembedded/meta-oe}, \code{meta-openembedded/meta-python} and \code{meta-st-stm32mp} directory to the
 \code{BBLAYERS} variable.
 \section{Build your first image}
@@ -83,7 +83,7 @@ root filesystem files. To generate the final image, You will find scripts in
 Execute it:
 sudo ./create_sdcard_from_flashlayout.sh \
 Flash the SD card with that image:
diff --git a/labs/yocto-layer/yocto-layer.tex b/labs/yocto-layer/yocto-layer.tex
index 6117c7f4..32ccb383 100644
--- a/labs/yocto-layer/yocto-layer.tex
+++ b/labs/yocto-layer/yocto-layer.tex
@@ -37,8 +37,8 @@ check, and adapt if needed, the global layer configuration file located in the
 \section{Integrate a layer to the build}
 To be fair, we already used and integrated a layer in our build configuration
-during the first lab, with \code{meta-ti}. This layer was responsible for
-BeagleBone Black support in Yocto. We have to do the same for our
+during the first lab, with \ifdefstring{\labboard}{discovery}
+{\code{meta-st-stm32}} {\code{meta-ti}}. This layer was responsible for \ifdefstring{\labboard}{discovery} {\code{stm32mp1 DK1}} {\code{BeagleBone Black}} support in Yocto. We have to do the same for our
 \code{meta-bootlinlabs} now.
 There is a file which contains all the paths of the layers we use. Try to find it

More information about the training-materials-updates mailing list