[BL training-materials-updates] Update Buildroot lab
Michael Opdenacker
michael.opdenacker at bootlin.com
Thu Oct 4 18:55:49 CEST 2018
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=02130e3ec1f49982ffb5fa57194a84bbb7cb2bd3
>---------------------------------------------------------------
commit 02130e3ec1f49982ffb5fa57194a84bbb7cb2bd3
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Thu Oct 4 18:55:49 2018 +0200
Update Buildroot lab
- Tested with Ubuntu 18.04 and the toolchain we built
- Upgrade to Buildroot 18.08
(18.02 is not recent enough, as it doesn't support
toolchains with Linux 4.16 headers yet)
- Re-order going further suggests. I prefer when
people do BR related tasks first
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
02130e3ec1f49982ffb5fa57194a84bbb7cb2bd3
labs/sysdev-buildroot/sysdev-buildroot.tex | 35 +++++++++++++++---------------
1 file changed, 18 insertions(+), 17 deletions(-)
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index 73ce683..361000a 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -11,7 +11,7 @@ go into it.
\section{Get Buildroot and explore the source code}
The official Buildroot website is available at
-\url{https://buildroot.org/}. Download the latest stable 2017.08.x
+\url{https://buildroot.org/}. Download the latest stable 2018.08
version which we have tested for this lab. Uncompress the tarball
and go inside the Buildroot source directory.
@@ -80,11 +80,12 @@ button whenever you need more details about a given option:
\item \code{Toolchain}: \code{Custom toolchain}
\item \code{Toolchain path}: use the toolchain you built:
\code{/home/<user>/x-tools/arm-cortexa5-linux-uclibcgnueabihf}
- \item \code{External toolchain gcc version}: \code{6.x}
- \item \code{External toolchain kernel headers series}: \code{4.10.x}
+ \item \code{External toolchain gcc version}: \code{8.x}
+ \item \code{External toolchain kernel headers series}: \code{4.16.x}
\item \code{External toolchain C library}: \code{uClibc/uClibc-ng}
\item We must tell Buildroot about our toolchain configuration, so
- select \code{Toolchain has WCHAR support?} and
+ select \code{Toolchain has WCHAR support?},
+ \code{Toolchain has SSP support?} and
\code{Toolchain has C++ support?}.
Buildroot will check these parameters anyway.
\end{itemize}
@@ -167,7 +168,7 @@ a new \code{nfsroot} directory that is going to hold our system,
exported over NFS. Go into this directory, and untar the rootfs using:
\begin{verbatim}
-sudo tar xvf ../buildroot-2017.08/output/images/rootfs.tar
+sudo tar xvf ../buildroot-2018.08/output/images/rootfs.tar
\end{verbatim}
Add our \code{nfsroot} directory to the list of directories exported
@@ -183,18 +184,6 @@ lab.
\begin{itemize}
-\item {\em Only for the 5 day course, covering flash storage}\\
- Flash the new system on the flash of the board
- \begin{itemize}
- \item First, in buildroot, select the UBIFS filesystem image type.
- \item You'll also need to provide buildroot some information on the
- underlying device that will store the filesystem. In our case, the
- logical eraseblock size is 124KiB, the minimum I/O unit size is
- 2048 and the Maximum logical eraseblock (LEB) count is 1000.
- \item Then, once the image has been generated, update your rootfs
- volume.
- \end{itemize}
-
\item Add dropbear (SSH server and client) to the list of packages
built by Buildroot and log to your target system using an ssh client
on your development workstation. Hint: you will have to set a
@@ -208,4 +197,16 @@ lab.
supported by Buildroot, so you'd better stick with the latest
version in the 2.8 series.
+\item {\em Only for the 5 day course, covering flash storage}\\
+ Flash the new system on the flash of the board
+ \begin{itemize}
+ \item First, in buildroot, select the UBIFS filesystem image type.
+ \item You'll also need to provide buildroot some information on the
+ underlying device that will store the filesystem. In our case, the
+ logical eraseblock size is 124KiB, the minimum I/O unit size is
+ 2048 and the Maximum logical eraseblock (LEB) count is 1000.
+ \item Then, once the image has been generated, update your rootfs
+ volume.
+ \end{itemize}
+
\end{itemize}
More information about the training-materials-updates
mailing list