Vasilik xxx

Pre-built (and tested) images are available from ftp://de/pub/u-boot/images/ Where we come from: =================== - start from 8xxrom sources - create PPCBoot project ( - clean up code - make it easier to add custom boards - make it possible to add other [Power PC] CPUs - extend functions, especially: * Provide extended interface to Linux boot loader * S-Record download * network boot * PCMCIA / Compact Flash / ATA disk / SCSI ...

boot - create ARMBoot project ( - add other CPU families (starting with ARM) - create U-Boot project ( - current project page: see Names and Spelling: =================== The "official" name of this project is "Das U-Boot".

Selection of Processor Architecture and Board Type: --------------------------------------------------- For all supported boards there are ready-to-use default configurations available; just type "make _defconfig".

Example: For a TQM823L module type: cd u-boot make TQM823L_defconfig Note: If you're looking for the default configuration file for a board you're sure used to be there but is now missing, check the file doc/README.scrapyard for a list of no longer supported boards.

Also, instead of permanently adding rarely used code (for instance hardware test utilities) to the monitor, you can load and run it dynamically.

Status: ======= In general, all boards for which a configuration option exists in the Makefile have been tested to some extent and can be considered "working".

At present, SPL mostly uses a separate code path, but the function names and roles of each function are the same. From there, three functions are called; the purpose and limitations of each of these functions are described below.

Some boards or architectures may not conform to this. lowlevel_init(): - purpose: essential init to permit execution to reach board_init_f() - no global_data or BSS - there is no stack (ARMv7 may have one but it will soon be removed) - must not set up SDRAM or use console - must only do the bare minimum to allow execution to continue to board_init_f() - this is almost never needed - return normally from this function board_init_f(): - purpose: set up the machine ready for running board_init_r(): i.e.

Vasilik xxx-42Vasilik xxx-83

Examples: U-Boot v2009.11 - Release November 2009 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release Directory Hierarchy: ==================== /arch Architecture specific files /arc Files generic to ARC architecture /arm Files generic to ARM architecture /avr32 Files generic to AVR32 architecture /blackfin Files generic to Analog Devices Blackfin architecture /m68k Files generic to m68k architecture /microblaze Files generic to microblaze architecture /mips Files generic to MIPS architecture /nds32 Files generic to NDS32 architecture /nios2 Files generic to Altera NIOS2 architecture /openrisc Files generic to Open RISC architecture /powerpc Files generic to Power PC architecture /sandbox Files generic to HW-independent "sandbox" /sh Files generic to SH architecture /sparc Files generic to SPARC architecture /x86 Files generic to x86 architecture /api Machine/arch independent API for external apps /board Board dependent files /common Misc architecture independent functions /configs Board default configuration files /disk Code for disk drive partition handling /doc Documentation (don't expect too much) /drivers Commonly used device drivers /dts Contains Makefile for building internal U-Boot fdt./examples Example code for standalone applications, etc./fs Filesystem code (cramfs, ext2, jffs2, etc.) /include Header Files /lib Library routines generic to all architectures /Licenses Various license files /net Networking code /post Power On Self Test /scripts Various build scripts and Makefiles /test Various unit test files /tools Tools to build S-Record or U-Boot images, etc.In fact, many of them are used in production systems.In case of problems see the CHANGELOG file to find out who contributed the specific port.

Leave a Reply