[FE training-materials-updates] Misc flash slides layout improvements
Michael Opdenacker
michael.opdenacker at free-electrons.com
Tue Oct 27 11:40:57 CET 2015
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=c0849c906c20e2f58c8f8fe8c15a1d82be54a540
>---------------------------------------------------------------
commit c0849c906c20e2f58c8f8fe8c15a1d82be54a540
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Tue Oct 27 11:40:57 2015 +0100
Misc flash slides layout improvements
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
c0849c906c20e2f58c8f8fe8c15a1d82be54a540
.../sysdev-flash-filesystems.tex | 51 ++++++++++------------
1 file changed, 24 insertions(+), 27 deletions(-)
diff --git a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 7b935f0..08ac4f2 100644
--- a/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/slides/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -27,7 +27,7 @@
\begin{frame}
\frametitle{NAND flash chips: how they work ?}
\begin{itemize}
- \item Encode bits with Voltage levels
+ \item Encode bits with voltage levels
\item Start with all bits set to 1
\item Programming implies changing some bits from 1 to 0
\item Restoring bits to 1 is done via the ERASE operation
@@ -79,7 +79,7 @@
\begin{frame}
\frametitle{NAND flash: ECC}
\begin{itemize}
- \item ECC partly address the reliability problem on NAND flash
+ \item ECC partly addresses the reliability problem on NAND flash
\item Operates on blocks (usually 512 or 1024 bytes)
\item ECC data are stored in the OOB area
\item Three algorithms:
@@ -88,7 +88,7 @@
\item Reed-Solomon: can fixup several bits per block
\item BCH: can fixup several bits per block
\end{itemize}
- \item BCH and Reed-Solomon strengths depends on the size allocated
+ \item BCH and Reed-Solomon strength depends on the size allocated
for ECC data, which in turn depends on the OOB size
\item NAND manufacturers specify the required ECC strength in their
datasheets: ignoring these requirements might compromise data
@@ -100,7 +100,7 @@
\frametitle{The MTD subsystem (1)}
\begin{itemize}
\item MTD stands for {\em Memory Technology Devices}
- \item Generic subsystem dealing with all type of storage media that
+ \item Generic subsystem dealing with all types of storage media that
are not fitting in the block subsystem
\item Supported media types: RAM, ROM, NOR flash, NAND flash,
Dataflash
@@ -117,7 +117,7 @@
\item \code{flags}: information about device type and capabilities
\end{itemize}
\item Various kind of MTD users: file-systems, block device emulation
- layers, user space interfaces, ...
+ layers, user space interfaces...
\end{itemize}
\end{frame}
@@ -174,7 +174,7 @@
(those filled with \code{0xff})
\item \code{nand erase <offset> <size>} erase a NAND region
\item \code{nand erase.part <part>} erase a NAND partition
- \item more commands for debugging purpose
+ \item More commands for debugging purpose
\end{itemize}
\end{itemize}
\end{frame}
@@ -217,7 +217,7 @@
\begin{frame}
\frametitle{U-Boot: using MTD partitions}
\begin{itemize}
- \item U-Boot provides a way to define mtd partitions on top of flash
+ \item U-Boot provides a way to define MTD partitions on top of flash
devices
\item Using partitions eases the manipulation of flash devices, which might
be particularly error prone
@@ -228,9 +228,9 @@
\begin{itemize}
\item \code{devid}: device identifier retrieved with
\code{nand info} or \code{flinfo}
- \item \code{mtdid}: mtd identifier (should match linux MTD device
+ \item \code{mtdid}: mtd identifier (should match Linux MTD device
name)
- \item \code{mtdid} is displayed when booting the linux kernel
+ \item \code{mtdid} is displayed when booting the Linux kernel
\end{itemize}
\item \code{mtdparts} defines the partitions for the different devices
\end{itemize}
@@ -247,7 +247,7 @@
\begin{itemize}
\item \code{mtdparts} format: \code{<mtdid>:<partition>[,partition]}
\item \code{partition} format: \code{<size>[@offset](<name>)[ro]}
- \item \code{mtdid} is the MTD device name assigned by linux
+ \item \code{mtdid} is the MTD device name assigned by Linux
\item \code{mtdid} is displayed at boot (and can be retrieved using
\code{dmesg})
\end{itemize}
@@ -263,13 +263,17 @@ Creating 5 MTD partitions on "omap2-nand.0":
\end{verbatim}
\end{frame}
-\begin{frame}
+\begin{frame}[fragile]
\frametitle{U-Boot: defining MTD partitions (2)}
\begin{itemize}
- \item Example:\\
- \code{mtdids=nand0=omap2-nand.0}
- \code{mtdparts=mtdparts=omap2-nand.0:512k(X-Loader)ro,1536k(U-Boot)ro,512k(Environment),4m(Kernel),-(RootFS)}
- \item We've just defined 5 partitions in the \code{omap2-nand.0} device:
+ \item Example:
+ {\tiny
+ \begin{verbatim}
+mtdids=nand0=omap2-nand.0
+mtdparts=mtdparts=omap2-nand.0:512k(X-Loader)ro,1536k(U-Boot)ro,512k(Environment),4m(Kernel),-(RootFS)
+ \end{verbatim}
+ }
+ \item This defines 5 partitions in the \code{omap2-nand.0} device:
\begin{itemize}
\item \code{1st stage bootloader} (512 KiB, read-only)
\item \code{U-Boot} (1536 KiB, read-only)
@@ -362,7 +366,7 @@ static struct mtd_partition igep2_flash_partitions[] = {
\begin{itemize}
\item MTD partitions can fortunately be defined through the kernel
command line.
- \item U-Boot and linux are using the same syntax to describe the MTD
+ \item U-Boot and Linux are using the same syntax to describe the MTD
partitions
\item Directly pass the \code{mtdparts} environment variable defined in
u-boot to the kernel cmdline
@@ -658,8 +662,7 @@ vol_alignment=1
\begin{frame}
\frametitle{U-Boot: UBI tools}
- \begin{itemize}
- \item Grouped under the \code{ubi} command
+ Grouped under the \code{ubi} command
\begin{itemize}
\item \code{ubi part <part-name>} attach an MTD partition to the UBI
layer
@@ -678,7 +681,6 @@ vol_alignment=1
\item \code{ubi writevol <src-addr> <vol-name> <size>}
\end{itemize}
\end{itemize}
- \end{itemize}
\end{frame}
\begin{frame}
@@ -701,8 +703,7 @@ vol_alignment=1
\begin{frame}
\frametitle{Linux: UBI target tools (2)}
- \begin{itemize}
- \item UBI volume management:
+ UBI volume management:
\begin{itemize}
\item \code{ubimkvol /dev/ubi<UBI-device-id> -N <name> -s <size>} create
a new volume. Use \code{-m} in place of \code{-s <size>} if you want
@@ -716,14 +717,11 @@ vol_alignment=1
\item \code{ubirename /dev/ubi<UBI-device-id>_<UBI-vol-id> <old-name> <new-size>}
rename a UBI volume
\end{itemize}
- \end{itemize}
\end{frame}
\begin{frame}
\frametitle{Linux: UBIFS host tools}
- \begin{itemize}
- \item UBIFS filesystems images can be created using the
- \code{mkfs.ubifs} utility
+ UBIFS filesystems images can be created using \code{mkfs.ubifs}
\begin{itemize}
\item \code{mkfs.ubifs -m 4096 -e 252KiB -c 1000 -r rootfs/ ubifs.img}
\begin{itemize}
@@ -743,7 +741,6 @@ vol_alignment=1
on the host)
\end{itemize}
\end{itemize}
- \end{itemize}
\end{frame}
\begin{frame}
@@ -893,6 +890,6 @@ vol_alignment=1
\item Creating partitions in your internal flash storage
\item Creating a UBI image with several volumes and flashing it from
U-Boot
- \item Manipulating UBI volumes from linux
+ \item Manipulating UBI volumes from Linux
\end{itemize}
}
More information about the training-materials-updates
mailing list