1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
4 <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
6 <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Linux)">
7 <META NAME="AUTHOR" CONTENT=" ">
8 <META NAME="CREATED" CONTENT="20021129;9042700">
9 <META NAME="CHANGEDBY" CONTENT=" ">
10 <META NAME="CHANGED" CONTENT="20030121;16061100">
13 <H1>Example YAFFS Bootloader</H1>
15 <P>The YAFFS bootloader is LGPL to facilitate integration into
17 <H3>Software Modules</H3>
18 <P>The software is designed in a modular fashion to facilitate
19 integration and configuration.</P>
20 <P>The software comprises the following main sections:</P>
22 <LI><P>yaffs_flashif.c NAND integration functions (to be completed
24 <LI><P>nand_ecc.c: The ECC algorithms.</P>
25 <LI><P>yboot.c: Bootloader code to provide a file as a stream of
26 bytes in the bootloader.</P>
29 <LI><P>bootldtst.c: Test harness/example for bootloader.</P>
31 <P>The bootloader does not implement YAFFS. Instead it is a simple
32 set of routines which allows reading a file on a YAFFS device.</P>
33 <P>The file must be in the root directory of the device (eg.
34 "/boot/boot.bin") since the bootloader does not understand
35 directories. This limitation simplifies the bootloader and speeds up
37 <P>As shown here the bootloader is initialised, then provides the
38 boot file as a stream of bytes. It is simple enough to provide the
39 data in other formats.</P>
40 <P>$Id: yaffs_boot.html,v 1.1 2003-01-21 03:34:12 charles Exp $</P>