[bootlin/training-materials updates] master: labs/buildroot-appdev: update to Buildroot 2019.02, use the ARM toolchain gdbserver (5bb13060)

Thomas Petazzoni thomas.petazzoni at bootlin.com
Wed Mar 20 15:01:13 CET 2019

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


commit 5bb13060d049d1e73920317b362f02c43e6db86b
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Wed Mar 20 14:56:09 2019 +0100

    labs/buildroot-appdev: update to Buildroot 2019.02, use the ARM toolchain gdbserver
    No need to build our own, the ARM toolchain gdbserver is not broken
    like the Linaro toolchain one was.
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


 labs/buildroot-appdev/buildroot-appdev.tex | 25 ++++++++++++-------------
 1 file changed, 12 insertions(+), 13 deletions(-)

diff --git a/labs/buildroot-appdev/buildroot-appdev.tex b/labs/buildroot-appdev/buildroot-appdev.tex
index 8b2175ac..f9cfe0ca 100644
--- a/labs/buildroot-appdev/buildroot-appdev.tex
+++ b/labs/buildroot-appdev/buildroot-appdev.tex
@@ -104,19 +104,18 @@ again.
 Our application is simple and works, but what if you need to debug it?
 So let's set up remote debugging.
-Since we're using a {\em Linaro} toolchain, the easiest would be to
-use the \code{gdbserver} integrated with it. Unfortunately, in {\em
-  Linaro 2017.02}, the pre-built \code{gdbserver} is
-broken\footnote{We have reported a bug to Linaro about this,
-  \url{https://bugs.linaro.org/show_bug.cgi?id=3344}}. We will instead
-ask Buildroot to build its own \code{gdbserver}. In
-\code{Target packages}, \code{Debugging, profiling and benchmark},
-enable \code{gdb}, and keep only the \code{gdbserver} sub-option
-Rebuild with \code{make}, and reflash your system, or alternatively,
-just copy \code{output/target/usr/bin/gdbserver} to the target
-\code{/usr/bin/} directory using \code{scp}.
+The {\em ARM} toolchain is provided with a pre-compiled {\em
+  gdbserver}, so we'll simply use it. Enable the option
+\code{BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY}, and then force the
+re-installation of the toolchain using:
+make toolchain-external-arm-arm-reinstall
+Reflash your system, or alternatively, just copy
+\code{output/target/usr/bin/gdbserver} to the target \code{/usr/bin/}
+directory using \code{scp}.
 To do some appropriate debugging, we need to have debugging symbols
 available. So we need to do two things:

More information about the training-materials-updates mailing list