[FE training-materials-updates] labs/buildroot-basic: update for Buildroot 2017.08

[Thomas Petazzoni]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=77535bb58d94d8b7f4876d82aa7f43bf634f0efd

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

commit 77535bb58d94d8b7f4876d82aa7f43bf634f0efd
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Tue Oct 17 13:41:59 2017 +0200

    labs/buildroot-basic: update for Buildroot 2017.08
    
    Update to Buildroot 2017.08, use Linux 4.13 and U-Boot
    2017.07. Slightly adjust the U-Boot environment to work with U-Boot
    2017.07.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


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

77535bb58d94d8b7f4876d82aa7f43bf634f0efd
 labs/buildroot-basic/buildroot-basic.tex | 22 ++++++++++++----------
 1 file changed, 12 insertions(+), 10 deletions(-)

diff --git a/labs/buildroot-basic/buildroot-basic.tex b/labs/buildroot-basic/buildroot-basic.tex
index aba3043..4b2413e 100644
--- a/labs/buildroot-basic/buildroot-basic.tex
+++ b/labs/buildroot-basic/buildroot-basic.tex
@@ -42,7 +42,7 @@ git clone http://git.buildroot.net/git/buildroot.git
 \end{verbatim}
 
 In the worst case, if neither work, you can download the Buildroot
-tarball \code{buildroot-2016.5.tar.bz2} from
+tarball \code{buildroot-2017.08.tar.bz2} from
 \code{http://buildroot.org/downloads/} and extract it. However in this
 case, you won't be able to use {\em Git} to visualize your changes and
 keep track of them.
@@ -53,7 +53,7 @@ We're going to start a branch from the {\em 2016.05} Buildroot
 release, with which this training has been tested.
 
 \begin{verbatim}
-git checkout -b felabs 2016.05
+git checkout -b felabs 2017.08
 \end{verbatim}
 
 \section{Configuring Buildroot}
@@ -122,7 +122,7 @@ Now, let's do the configuration:
     hesitate however to look at the available options when you select
     \code{Buildroot toolchain} as the \code{Toolchain type}.
 
-  \item Select \code{Linaro 2016.02} as the
+  \item Select \code{Linaro 2017.02} as the
     \code{Toolchain}. Buildroot can either use pre-defined toolchains
     such as the Linaro one, or custom toolchains (either downloaded
     from a given location, or pre-installed on your machine). Note
@@ -152,8 +152,8 @@ Now, let's do the configuration:
 
   \item By default, the most recent Linux kernel version available at
     the time of the Buildroot release is used. In our case, we want to
-    use a specific version: \code{4.6}. So select \code{Custom
-      version} as the \code{Kernel version}, and enter \code{4.6} in
+    use a specific version: \code{4.13}. So select \code{Custom
+      version} as the \code{Kernel version}, and enter \code{4.13} in
     the \code{Kernel version} text field that appears.
 
   \item Now, we need to define which kernel configuration to
@@ -161,7 +161,7 @@ Now, let's do the configuration:
     the kernel sources themselves, called a {\em defconfig}. To
     identify which {\em defconfig} to use, you can look in the kernel
     sources directly, at
-    \url{http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/configs/?id=v4.6}. In
+    \url{http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/configs/?id=v4.13}. In
     practice, for this platform, it is not trivial to find which one
     to use: the AM335x processor is supported in the Linux kernel as
     part of the support for many other Texas Instruments processors:
@@ -183,8 +183,8 @@ Now, let's do the configuration:
     describe the hardware. The BeagleBone Black is in this situation,
     so you'll have to enable the \code{Build a Device Tree Blob}
     option. At
-    \url{http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/?id=v4.6},
-    you can see the list of all Device Tree files available in the 4.6
+    \url{http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/?id=v4.13},
+    you can see the list of all Device Tree files available in the 4.13
     Linux kernel (note: the Device Tree files for boards use the
     \code{.dts} extension). The one for the BeagleBone Black is
     \code{am335x-boneblack.dts}. Even if talking about Device Tree is
@@ -197,7 +197,7 @@ Now, let's do the configuration:
   \end{itemize}
 
 \item \code{Target packages} menu. This is probably the most important
-  menu, as this is the one where you can select amongst the 1800+
+  menu, as this is the one where you can select amongst the 2200+
   available Buildroot packages which ones should be built and
   installed in your system. For our basic system, enabling
   \code{Busybox} is sufficient and is already enabled by default, but
@@ -222,7 +222,7 @@ Now, let's do the configuration:
     recent enough U-Boot version, we are going to use the latter,
     called {\em Kconfig}.
 
-  \item You can keep using the default \code{2016.03} version as the
+  \item You can keep using the default \code{2017.07} version as the
     U-Boot version.
 
   \item Look at
@@ -413,6 +413,8 @@ on the SD card:
 \begin{verbatim}
 bootdir=
 bootpart=0:1
+devtype=mmc
+args_mmc=setenv bootargs console=${console} ${optargs} root=/dev/mmcblk0p2 rw rootfstype=${mmcrootfstype}
 uenvcmd=run loadimage;run loadramdisk;run findfdt;run loadfdt;run mmcloados
 \end{verbatim}
 }