[bootlin/training-materials updates] master: Embedded Linux debugging and appdev: Buildroot updates (6dea699f)
Michael Opdenacker
michael.opdenacker at bootlin.com
Wed Mar 17 09:57:25 CET 2021
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/6dea699fe82099f0fd931ef05f46bb104fd59a8e
>---------------------------------------------------------------
commit 6dea699fe82099f0fd931ef05f46bb104fd59a8e
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Wed Mar 17 09:57:25 2021 +0100
Embedded Linux debugging and appdev: Buildroot updates
- Using the Bootlin toolchains shows that you don't
have to repeat the toolchain features.
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
6dea699fe82099f0fd931ef05f46bb104fd59a8e
.../sysdev-application-debugging.tex | 24 ++++++----------------
.../sysdev-application-development.tex | 2 +-
2 files changed, 7 insertions(+), 19 deletions(-)
diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index 238904a7..24a71916 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -18,7 +18,7 @@ it looks like a good idea to do your application debugging work
with a {\em glibc} toolchain first, and then switch to lighter libraries
once your application and software stack is production ready.
-Extract the Buildroot 2020.02.<n> sources into the current directory.
+Extract the Buildroot 2021.02.<n> sources into the current directory.
Then, in the \code{menuconfig} interface, configure the target
architecture as done previously but configure the toolchain and
@@ -28,21 +28,9 @@ target packages differently:
\item In \code{Toolchain}:
\begin{itemize}
\item \code{Toolchain type}: \code{External toolchain}
- \item \code{Toolchain}: \code{Custom Toolchain}
+ \item \code{Toolchain}: \code{Bootlin toolchains}
\item \code{Toolchain origin}: \code{Toolchain to be downloaded and installed}
- \item \code{Toolchain URL}:
-\code{https://toolchains.bootlin.com/downloads/releases/toolchains/armv7-eabihf/tarballs/armv7-eabihf--glibc--stable-2020.02-2.tar.bz2}\\
- You can easily choose such a toolchain on
- \url{https://toolchains.bootlin.com} by selecting the
- architecture, the C library and the compiler version you need.
- While you can try with other versions, the above toolchain
- is known to make this lab work.
- \item \code{External toolchain gcc version}: \code{8.x}
- \item \code{External toolchain kernel headers series}: \code{4.4.x}
- \item \code{External toochain C library}: \code{glibc/eglibc}
- \item Select \code{Toolchain has SSP support?}
- \item Select \code{Toolchain has RPC support?}
- \item Select \code{Toolchain has C++ support?}
+ \item \code{Bootlin toolchain variant}: \code{armv7-eabihf glibc stable 2020.08-1}
\item Select \code{Copy gdb server to the Target}
\end{itemize}
\item \code{Target packages}
@@ -58,7 +46,7 @@ target packages differently:
Now, build your root filesystem.
Go back to the \code{$HOME/__SESSION_NAME__-labs/debugging} directory
-and extract the \code{buildroot-2020.02.<n>/output/images/rootfs.tar}
+and extract the \code{buildroot-2021.02.<n>/output/images/rootfs.tar}
archive in the \code{nfsroot} directory.
Add this directory to the \code{/etc/exports} file and restart
@@ -81,7 +69,7 @@ you don't have the source code.
Update the PATH:
\footnotesize
\begin{verbatim}
-export PATH=$HOME/__SESSION_NAME__-labs/debugging/buildroot-2020.02.<n>/output/host/bin:$PATH
+export PATH=$HOME/__SESSION_NAME__-labs/debugging/buildroot-2021.02.<n>/output/host/bin:$PATH
\end{verbatim}
\normalsize
@@ -155,7 +143,7 @@ variable (on one line):
\begin{verbatim}
(gdb) set sysroot /home/<user>/__SESSION_NAME__-labs/debugging/
-buildroot-2020.02.<n>/output/staging
+buildroot-2021.02.<n>/output/staging
\end{verbatim}
Of course, replace \code{<user>} by your actual user name.
diff --git a/labs/sysdev-application-development/sysdev-application-development.tex b/labs/sysdev-application-development/sysdev-application-development.tex
index e248c581..d3a53a14 100644
--- a/labs/sysdev-application-development/sysdev-application-development.tex
+++ b/labs/sysdev-application-development/sysdev-application-development.tex
@@ -25,7 +25,7 @@ Let's add this directory to our \code{PATH}:
\footnotesize
\begin{verbatim}
-export PATH=$HOME/__SESSION_NAME__-labs/buildroot/buildroot-2020.02.X/output/host/usr/bin:$PATH
+export PATH=$HOME/__SESSION_NAME__-labs/buildroot/buildroot-2021.02.X/output/host/usr/bin:$PATH
\end{verbatim}
\normalsize
More information about the training-materials-updates
mailing list