[FE training-materials-updates] Application debugging lab: partial update

[Michael Opdenacker]

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

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

commit f90e5c23b16dd2c780b8ed1f50e9768e31822dcc
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Fri Nov 3 14:02:32 2017 +0100

    Application debugging lab: partial update
    
    - Only updating explanations!
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

f90e5c23b16dd2c780b8ed1f50e9768e31822dcc
 .../sysdev-application-debugging.tex                   | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 9229798..6f94658 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -9,18 +9,21 @@ Create an \code{nfsroot} directory.
 
 \section{Debugging setup}
 
-For this lab, we will create a separate Buildroot build, with a
-slightly different configuration. Indeed, we want to use a different
-toolchain as the toolchain produced by Crosstool-NG currently has a
-non-functional {\em gdb}. And also because experimenting with multiple
-toolchains is good!
+Because of issues in {\em gdb} in the toolchain compiled by Crosstool-NG,
+we will use a different toolchain in this lab. We will also
+use a different version of Buildroot (which is known to make this lab
+work).
 
-Extract the Buildroot source code again from its tarball into
+Experimenting with multiple toolchains is also good experience!
+
+Download Buildroot 2016.02 and extract its tarball into
 \code{$HOME/embedded-linux-labs/debugging}. Then, copy the
 configuration of the previous Buildroot build (\code{.config} file)
 into the new Buildroot source directory.
 
-Then, in \code{menuconfig}, adjust the configuration as follows:
+Then, in \code{menuconfig}, configure the target architecture as
+done previously but configure the toolchain and target packages
+differently:
 
 \begin{itemize}
 \item In \code{Toolchain}:
@@ -176,4 +179,3 @@ During this lab, we learned that...
   symbols are available on the development host.
 
 \end{itemize}
-