[FE training-materials-updates] Fix path to toolchain
michael.opdenacker at free-electrons.com
michael.opdenacker at free-electrons.com
Tue Jun 5 15:21:43 CEST 2012
- Log -----------------------------------------------------------------
http://git.free-electrons.com/training-materials/commit/?id=ea4150b1fc4c748b6db6e503c2322dc72bac2483
commit ea4150b1fc4c748b6db6e503c2322dc72bac2483
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 5 15:22:05 2012 +0200
Fix path to toolchain
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 7b5e297..6766d14 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -60,7 +60,7 @@ Get back to the \code{src} directory.
As we said earlier, the DevKit8000 is very similar to the BeagleBoard, so we
will first compile a build for the BeagleBoard. The command to run is:
-\code{make TARGET_PRODUCT=beagleboard TARGET_TOOLS_PREFIX=~/android/linaro/android-toolchain-eabi/bin/arm-eabi- boottarball systemtarball userdatatarball -j8}
+\code{make TARGET_PRODUCT=beagleboard TARGET_TOOLS_PREFIX=~/felabs/android/linaro/android-toolchain-eabi/bin/arm-eabi- boottarball systemtarball userdatatarball -j8}
This will build three tarballs in \code{out/target/product/beagleboard}:
\code{boot.tar.bz2}, \code{system.tar.bz2}, \code{userdata.tar.bz2}, plus the images of Xloader,
http://git.free-electrons.com/training-materials/commit/?id=09f8d33200d6f0fd179e9feb93590f0c9f7ec161
commit 09f8d33200d6f0fd179e9feb93590f0c9f7ec161
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 5 15:19:05 2012 +0200
Add section for picocom and serial communication
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 8da2e24..7b5e297 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -12,8 +12,7 @@ After this lab, you will be able to:
Go to the \code{/home/<user>/felabs/android/linaro} directory.
-Install the \code{bzr}, \code{python-argparse},
-\code{python-parted} and \code{picocom} packages.
+Install the \code{bzr}, \code{python-argparse} and code{python-parted} packages.
\section{Download the source code}
@@ -44,14 +43,20 @@ repo init -u git://android.git.linaro.org/platform/manifest.git \
repo sync -j4
\end{verbatim}
-You will also need to download the associated Linaro toolchain at
-\url{http://goo.gl/Wn4dM}
+You will also need to download and extract the associated Linaro toolchain:
\footnote{The original URL is
\url{http://android-build.linaro.org/builds/~linaro-android/toolchain-4.6-2011.11/4/android-toolchain-eabi-linaro-4.6-2011.11-4-2011-11-15_12-22-49-linux-x86.tar.bz2}. We wanted to give you something much shorter
-to type.} and extract its contents.
+to type.}
+\begin{verbatim}
+cd ..
+wget http://goo.gl/Wn4dM
+tar jxf Wn4dM
+\end{verbatim}
\section{Build Android for the BeagleBoard}
+Get back to the \code{src} directory.
+
As we said earlier, the DevKit8000 is very similar to the BeagleBoard, so we
will first compile a build for the BeagleBoard. The command to run is:
@@ -75,13 +80,49 @@ sudo ./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc \
--boot out/target/product/beagleboard/boot.tar.bz2
\end{verbatim}
-Now, we can remove the SD card and insert it into its slot in the DevKit8000,
-and we can boot on it holding the boot key while switching the board on. On the
-serial port, you should see Android going through its booting process, until
+Once this command is over, you can remove the SD card and insert it
+into the corresponding slot on the Devkit8000 board.
+
+\section{Setting up serial communication with the board}
+
+To see the board boot, we need to read the first boot messages
+issued on the board's serial port.
+
+Your instructor will provide you with a special serial cable
+\footnote{This should be the same cable as for the Beagle and IGEPv2 boards}
+for the Devkit8000 board, together with a USB-to-serial adaptor for the connection
+with your laptop.
+
+When you plug in this adaptor, a serial port should appear on your workstation:
+\code{/dev/ttyUSB0}.
+
+You can also see this device appear by looking at the output of the \code{dmesg}
+command.
+
+To communicate with the board through the serial port, install a
+serial communication program, such as \code{picocom}:
+\footnote{\code{picocom} is one of the simplest utilities to access
+a serial console. \code{minicom} looks more featureful, but is also
+more complex to configure.}
+
+\begin{verbatim}
+sudo apt-get install picocom
+\end{verbatim}
+
+Run \code{picocom -b 115200 /dev/ttyUSB0}, to start serial
+communication on \code{/dev/ttyUSB0}, with a baudrate of 115200. If
+you wish to exit picocom, press \code{[Ctrl][a]} followed by
+\code{[Ctrl][x]}.
+
+\section{Booting the board}
+
+Once you inserted the SD card, you can boot the board by
+holding the \code{boot} key while switching the board on. On the
+serial port, you should see Android going through its boot process, until
you finally have a shell on the serial link.
-However, as you may have seen, while the system boots, you have no display at
-all, so we will need to fix this.
+However, as you may have seen, the system boots, but you have no display at
+all. We are going to fix this.
\section{Fix the blank screen}
http://git.free-electrons.com/training-materials/commit/?id=3d9b5b28b2a93166138a3f7617b06fe46a75a090
commit 3d9b5b28b2a93166138a3f7617b06fe46a75a090
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 5 14:40:13 2012 +0200
Add sudo before linaro-android-media-create
- Style improvements too
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index c3e8e4e..8da2e24 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -62,14 +62,14 @@ This will build three tarballs in \code{out/target/product/beagleboard}:
U-Boot, Linux kernel and its initramfs (which are also contained in
\code{boot.tar.bz2}).
-We then need to put these images on SD card so that we can boot on this system.
-Linaro developed a set of scripts that takes the three tarballs and aggregates
+We then need to put these images on an SD card so that we can boot on this system.
+Linaro developed a script that takes the three tarballs and aggregates
them to produce a ready-to-boot SD card. You can install it with the following
commands:
\begin{verbatim}
bzr branch lp:linaro-image-tools
-./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc \
+sudo ./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc \
--dev beagle --system out/target/product/beagleboard/system.tar.bz2 \
--userdata out/target/product/beagleboard/userdata.tar.bz2 \
--boot out/target/product/beagleboard/boot.tar.bz2
http://git.free-electrons.com/training-materials/commit/?id=aae51791c028964b5ffc97b4c75225e88c0d3213
commit aae51791c028964b5ffc97b4c75225e88c0d3213
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Jun 5 14:35:14 2012 +0200
Misc improvements
- Style improvements
- Explained why we're using Gingerbread
diff --git a/labs/android-boot/android-boot.tex b/labs/android-boot/android-boot.tex
index 3f4fc55..47eaa18 100644
--- a/labs/android-boot/android-boot.tex
+++ b/labs/android-boot/android-boot.tex
@@ -48,7 +48,7 @@ to the kernel version and compile the kernel!
A few minutes later, you have a kernel image in \code{arch/arm/boot}.
-\code{Boot your new kernel}
+\section{Boot your new kernel}
To run the emulator again, this time with your new kernel image, you
have to restore the environment that you had after building Android from
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 61f24bd..c3e8e4e 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -12,24 +12,29 @@ After this lab, you will be able to:
Go to the \code{/home/<user>/felabs/android/linaro} directory.
-Install the packages \code{bzr}, \code{python-argparse},
-\code{python-parted} and \code{picocom}.
+Install the \code{bzr}, \code{python-argparse},
+\code{python-parted} and \code{picocom} packages.
\section{Download the source code}
Linaro has been working for some time now on a optimized Android distribution,
-available on at least one chip of most major ARM vendors. At each release,
+available on at least one chip of most of the major ARM vendors. At each release,
Linaro also maintains an Android flavored Linux kernel corresponding to the latest
upstream Linux release.
-One of the platform supported by the Linaro's Android is the BeagleBoard, which
-is very similar to the DevKit8000 we use. Moreover, in the last kernel versions,
-the kernel needed for both of these cards have been unified, so we can boot the
-exact same kernel on both these boards. For these reasons, we will use this
+One of the platforms supported by the Linaro's Android is the BeagleBoard, which
+is very similar to the DevKit8000 we use. In particular, both boards have the
+same OMAP3530 CPU. Moreover, in the last kernel versions,
+the kernel needed for both of these boards have been unified, so we can boot the
+exact same kernel on both boards. For these reasons, we will use this
distribution as a starting point for the rest of the labs.
First, we need to download the source code. We will use the 11.11 release, which
-is based on Android 2.3 Gingerbread and Linux 3.1.1.
+is based on Android 2.3 Gingerbread and Linux 3.1.1
+\footnote{At the time of this writing, Linaro doesn't support Android 4.0 Ice Cream
+Sandwich on the Beagle board, and the port from \href{http://code.google.com/p/rowboat}
+{Rowboat project} doesn't seem to be fully stable either. We decided to stick
+with the most stable version for our hardware.}.
\begin{verbatim}
mkdir src
-----------------------------------------------------------------------
Summary of changes:
labs/android-boot/android-boot.tex | 2 +-
labs/android-new-board/android-new-board.tex | 86 ++++++++++++++++++++------
2 files changed, 67 insertions(+), 21 deletions(-)
More information about the training-materials-updates
mailing list