1c609719bSwdenk# 2151ab83aSwdenk# (C) Copyright 2000 - 2005 3c609719bSwdenk# Wolfgang Denk, DENX Software Engineering, wd@denx.de. 4c609719bSwdenk# 5c609719bSwdenk# See file CREDITS for list of people who contributed to this 6c609719bSwdenk# project. 7c609719bSwdenk# 8c609719bSwdenk# This program is free software; you can redistribute it and/or 9c609719bSwdenk# modify it under the terms of the GNU General Public License as 10c609719bSwdenk# published by the Free Software Foundation; either version 2 of 11c609719bSwdenk# the License, or (at your option) any later version. 12c609719bSwdenk# 13c609719bSwdenk# This program is distributed in the hope that it will be useful, 14c609719bSwdenk# but WITHOUT ANY WARRANTY; without even the implied warranty of 15c609719bSwdenk# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 16c609719bSwdenk# GNU General Public License for more details. 17c609719bSwdenk# 18c609719bSwdenk# You should have received a copy of the GNU General Public License 19c609719bSwdenk# along with this program; if not, write to the Free Software 20c609719bSwdenk# Foundation, Inc., 59 Temple Place, Suite 330, Boston, 21c609719bSwdenk# MA 02111-1307 USA 22c609719bSwdenk# 23c609719bSwdenk 24c609719bSwdenkSummary: 25c609719bSwdenk======== 26c609719bSwdenk 2724ee89b9SwdenkThis directory contains the source code for U-Boot, a boot loader for 28e86e5a07SwdenkEmbedded boards based on PowerPC, ARM, MIPS and several other 29e86e5a07Swdenkprocessors, which can be installed in a boot ROM and used to 30e86e5a07Swdenkinitialize and test the hardware or to download and run application 31e86e5a07Swdenkcode. 32c609719bSwdenk 33c609719bSwdenkThe development of U-Boot is closely related to Linux: some parts of 3424ee89b9Swdenkthe source code originate in the Linux source tree, we have some 3524ee89b9Swdenkheader files in common, and special provision has been made to 36c609719bSwdenksupport booting of Linux images. 37c609719bSwdenk 38c609719bSwdenkSome attention has been paid to make this software easily 39c609719bSwdenkconfigurable and extendable. For instance, all monitor commands are 40c609719bSwdenkimplemented with the same call interface, so that it's very easy to 41c609719bSwdenkadd new commands. Also, instead of permanently adding rarely used 42c609719bSwdenkcode (for instance hardware test utilities) to the monitor, you can 43c609719bSwdenkload and run it dynamically. 44c609719bSwdenk 45c609719bSwdenk 46c609719bSwdenkStatus: 47c609719bSwdenk======= 48c609719bSwdenk 49c609719bSwdenkIn general, all boards for which a configuration option exists in the 50c609719bSwdenkMakefile have been tested to some extent and can be considered 51c609719bSwdenk"working". In fact, many of them are used in production systems. 52c609719bSwdenk 53c609719bSwdenkIn case of problems see the CHANGELOG and CREDITS files to find out 54c609719bSwdenkwho contributed the specific port. 55c609719bSwdenk 56c609719bSwdenk 57c609719bSwdenkWhere to get help: 58c609719bSwdenk================== 59c609719bSwdenk 60c609719bSwdenkIn case you have questions about, problems with or contributions for 61c609719bSwdenkU-Boot you should send a message to the U-Boot mailing list at 62c609719bSwdenk<u-boot-users@lists.sourceforge.net>. There is also an archive of 63c609719bSwdenkprevious traffic on the mailing list - please search the archive 64c609719bSwdenkbefore asking FAQ's. Please see 65c609719bSwdenkhttp://lists.sourceforge.net/lists/listinfo/u-boot-users/ 66c609719bSwdenk 67c609719bSwdenk 68c609719bSwdenkWhere we come from: 69c609719bSwdenk=================== 70c609719bSwdenk 71c609719bSwdenk- start from 8xxrom sources 7224ee89b9Swdenk- create PPCBoot project (http://sourceforge.net/projects/ppcboot) 73c609719bSwdenk- clean up code 74c609719bSwdenk- make it easier to add custom boards 75c609719bSwdenk- make it possible to add other [PowerPC] CPUs 76c609719bSwdenk- extend functions, especially: 77c609719bSwdenk * Provide extended interface to Linux boot loader 78c609719bSwdenk * S-Record download 79c609719bSwdenk * network boot 80c609719bSwdenk * PCMCIA / CompactFLash / ATA disk / SCSI ... boot 8124ee89b9Swdenk- create ARMBoot project (http://sourceforge.net/projects/armboot) 82c609719bSwdenk- add other CPU families (starting with ARM) 8324ee89b9Swdenk- create U-Boot project (http://sourceforge.net/projects/u-boot) 8424ee89b9Swdenk 8524ee89b9Swdenk 8624ee89b9SwdenkNames and Spelling: 8724ee89b9Swdenk=================== 8824ee89b9Swdenk 8924ee89b9SwdenkThe "official" name of this project is "Das U-Boot". The spelling 9024ee89b9Swdenk"U-Boot" shall be used in all written text (documentation, comments 9124ee89b9Swdenkin source files etc.). Example: 9224ee89b9Swdenk 9324ee89b9Swdenk This is the README file for the U-Boot project. 9424ee89b9Swdenk 9524ee89b9SwdenkFile names etc. shall be based on the string "u-boot". Examples: 9624ee89b9Swdenk 9724ee89b9Swdenk include/asm-ppc/u-boot.h 9824ee89b9Swdenk 9924ee89b9Swdenk #include <asm/u-boot.h> 10024ee89b9Swdenk 10124ee89b9SwdenkVariable names, preprocessor constants etc. shall be either based on 10224ee89b9Swdenkthe string "u_boot" or on "U_BOOT". Example: 10324ee89b9Swdenk 10424ee89b9Swdenk U_BOOT_VERSION u_boot_logo 10524ee89b9Swdenk IH_OS_U_BOOT u_boot_hush_start 106c609719bSwdenk 107c609719bSwdenk 10893f19cc0SwdenkVersioning: 10993f19cc0Swdenk=========== 11093f19cc0Swdenk 11193f19cc0SwdenkU-Boot uses a 3 level version number containing a version, a 11293f19cc0Swdenksub-version, and a patchlevel: "U-Boot-2.34.5" means version "2", 11393f19cc0Swdenksub-version "34", and patchlevel "4". 11493f19cc0Swdenk 11593f19cc0SwdenkThe patchlevel is used to indicate certain stages of development 11693f19cc0Swdenkbetween released versions, i. e. officially released versions of 11793f19cc0SwdenkU-Boot will always have a patchlevel of "0". 11893f19cc0Swdenk 11993f19cc0Swdenk 120c609719bSwdenkDirectory Hierarchy: 121c609719bSwdenk==================== 122c609719bSwdenk 1237152b1d0Swdenk- board Board dependent files 1247152b1d0Swdenk- common Misc architecture independent functions 125c609719bSwdenk- cpu CPU specific files 126983fda83Swdenk - 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs 12711dadd54Swdenk - arm720t Files specific to ARM 720 CPUs 12811dadd54Swdenk - arm920t Files specific to ARM 920 CPUs 129a85f9f21Swdenk - at91rm9200 Files specific to Atmel AT91RM9200 CPU 130983fda83Swdenk - imx Files specific to Freescale MC9328 i.MX CPUs 1311d9f4105Swdenk - s3c24x0 Files specific to Samsung S3C24X0 CPUs 13211dadd54Swdenk - arm925t Files specific to ARM 925 CPUs 13311dadd54Swdenk - arm926ejs Files specific to ARM 926 CPUs 1348ed96046Swdenk - arm1136 Files specific to ARM 1136 CPUs 13572a087e0SWolfgang Denk - at32ap Files specific to Atmel AVR32 AP CPUs 13611dadd54Swdenk - i386 Files specific to i386 CPUs 13711dadd54Swdenk - ixp Files specific to Intel XScale IXP CPUs 138983fda83Swdenk - mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs 13911dadd54Swdenk - mips Files specific to MIPS CPUs 140983fda83Swdenk - mpc5xx Files specific to Freescale MPC5xx CPUs 141983fda83Swdenk - mpc5xxx Files specific to Freescale MPC5xxx CPUs 142983fda83Swdenk - mpc8xx Files specific to Freescale MPC8xx CPUs 143983fda83Swdenk - mpc8220 Files specific to Freescale MPC8220 CPUs 144983fda83Swdenk - mpc824x Files specific to Freescale MPC824x CPUs 145983fda83Swdenk - mpc8260 Files specific to Freescale MPC8260 CPUs 146983fda83Swdenk - mpc85xx Files specific to Freescale MPC85xx CPUs 14711dadd54Swdenk - nios Files specific to Altera NIOS CPUs 1485c952cf0Swdenk - nios2 Files specific to Altera Nios-II CPUs 1490c8721a4SWolfgang Denk - ppc4xx Files specific to AMCC PowerPC 4xx CPUs 15011dadd54Swdenk - pxa Files specific to Intel XScale PXA CPUs 15111dadd54Swdenk - s3c44b0 Files specific to Samsung S3C44B0 CPUs 15211dadd54Swdenk - sa1100 Files specific to Intel StrongARM SA1100 CPUs 153c609719bSwdenk- disk Code for disk drive partition handling 154c609719bSwdenk- doc Documentation (don't expect too much) 1557152b1d0Swdenk- drivers Commonly used device drivers 156c609719bSwdenk- dtt Digital Thermometer and Thermostat drivers 157c609719bSwdenk- examples Example code for standalone applications, etc. 158c609719bSwdenk- include Header Files 15911dadd54Swdenk- lib_arm Files generic to ARM architecture 1607b64fef3SWolfgang Denk- lib_avr32 Files generic to AVR32 architecture 16111dadd54Swdenk- lib_generic Files generic to all architectures 16211dadd54Swdenk- lib_i386 Files generic to i386 architecture 16311dadd54Swdenk- lib_m68k Files generic to m68k architecture 16411dadd54Swdenk- lib_mips Files generic to MIPS architecture 16511dadd54Swdenk- lib_nios Files generic to NIOS architecture 16611dadd54Swdenk- lib_ppc Files generic to PowerPC architecture 167213bf8c8SGerald Van Baren- libfdt Library files to support flattened device trees 168c609719bSwdenk- net Networking code 169c609719bSwdenk- post Power On Self Test 170c609719bSwdenk- rtc Real Time Clock drivers 171c609719bSwdenk- tools Tools to build S-Record or U-Boot images, etc. 172c609719bSwdenk 173c609719bSwdenkSoftware Configuration: 174c609719bSwdenk======================= 175c609719bSwdenk 176c609719bSwdenkConfiguration is usually done using C preprocessor defines; the 177c609719bSwdenkrationale behind that is to avoid dead code whenever possible. 178c609719bSwdenk 179c609719bSwdenkThere are two classes of configuration variables: 180c609719bSwdenk 181c609719bSwdenk* Configuration _OPTIONS_: 182c609719bSwdenk These are selectable by the user and have names beginning with 183c609719bSwdenk "CONFIG_". 184c609719bSwdenk 185c609719bSwdenk* Configuration _SETTINGS_: 186c609719bSwdenk These depend on the hardware etc. and should not be meddled with if 187c609719bSwdenk you don't know what you're doing; they have names beginning with 188c609719bSwdenk "CFG_". 189c609719bSwdenk 190c609719bSwdenkLater we will add a configuration tool - probably similar to or even 191c609719bSwdenkidentical to what's used for the Linux kernel. Right now, we have to 192c609719bSwdenkdo the configuration by hand, which means creating some symbolic 193c609719bSwdenklinks and editing some configuration files. We use the TQM8xxL boards 194c609719bSwdenkas an example here. 195c609719bSwdenk 196c609719bSwdenk 197c609719bSwdenkSelection of Processor Architecture and Board Type: 198c609719bSwdenk--------------------------------------------------- 199c609719bSwdenk 200c609719bSwdenkFor all supported boards there are ready-to-use default 201c609719bSwdenkconfigurations available; just type "make <board_name>_config". 202c609719bSwdenk 203c609719bSwdenkExample: For a TQM823L module type: 204c609719bSwdenk 205c609719bSwdenk cd u-boot 206c609719bSwdenk make TQM823L_config 207c609719bSwdenk 208c609719bSwdenkFor the Cogent platform, you need to specify the cpu type as well; 209c609719bSwdenke.g. "make cogent_mpc8xx_config". And also configure the cogent 210c609719bSwdenkdirectory according to the instructions in cogent/README. 211c609719bSwdenk 212c609719bSwdenk 213c609719bSwdenkConfiguration Options: 214c609719bSwdenk---------------------- 215c609719bSwdenk 216c609719bSwdenkConfiguration depends on the combination of board and CPU type; all 217c609719bSwdenksuch information is kept in a configuration file 218c609719bSwdenk"include/configs/<board_name>.h". 219c609719bSwdenk 220c609719bSwdenkExample: For a TQM823L module, all configuration settings are in 221c609719bSwdenk"include/configs/TQM823L.h". 222c609719bSwdenk 223c609719bSwdenk 2247f6c2cbcSwdenkMany of the options are named exactly as the corresponding Linux 2257f6c2cbcSwdenkkernel configuration options. The intention is to make it easier to 2267f6c2cbcSwdenkbuild a config tool - later. 2277f6c2cbcSwdenk 2287f6c2cbcSwdenk 229c609719bSwdenkThe following options need to be configured: 230c609719bSwdenk 2312628114eSKim Phillips- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX. 232c609719bSwdenk 2332628114eSKim Phillips- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS. 2346ccec449SWolfgang Denk 2356ccec449SWolfgang Denk- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined) 2366ccec449SWolfgang Denk Define exactly one of 2376ccec449SWolfgang Denk CONFIG_ATSTK1002 2386ccec449SWolfgang Denk 239c609719bSwdenk 240c609719bSwdenk- CPU Module Type: (if CONFIG_COGENT is defined) 241c609719bSwdenk Define exactly one of 242c609719bSwdenk CONFIG_CMA286_60_OLD 243c609719bSwdenk--- FIXME --- not tested yet: 244c609719bSwdenk CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P, 245c609719bSwdenk CONFIG_CMA287_23, CONFIG_CMA287_50 246c609719bSwdenk 247c609719bSwdenk- Motherboard Type: (if CONFIG_COGENT is defined) 248c609719bSwdenk Define exactly one of 249c609719bSwdenk CONFIG_CMA101, CONFIG_CMA102 250c609719bSwdenk 251c609719bSwdenk- Motherboard I/O Modules: (if CONFIG_COGENT is defined) 252c609719bSwdenk Define one or more of 253c609719bSwdenk CONFIG_CMA302 254c609719bSwdenk 255c609719bSwdenk- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined) 256c609719bSwdenk Define one or more of 257c609719bSwdenk CONFIG_LCD_HEARTBEAT - update a character position on 258c609719bSwdenk the lcd display every second with 259c609719bSwdenk a "rotator" |\-/|\-/ 260c609719bSwdenk 2612535d602Swdenk- Board flavour: (if CONFIG_MPC8260ADS is defined) 2622535d602Swdenk CONFIG_ADSTYPE 2632535d602Swdenk Possible values are: 2642535d602Swdenk CFG_8260ADS - original MPC8260ADS 265180d3f74Swdenk CFG_8266ADS - MPC8266ADS 26654387ac9Swdenk CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR 26704a85b3bSwdenk CFG_8272ADS - MPC8272ADS 2682535d602Swdenk 269c609719bSwdenk- MPC824X Family Member (if CONFIG_MPC824X is defined) 270c609719bSwdenk Define exactly one of 271c609719bSwdenk CONFIG_MPC8240, CONFIG_MPC8245 272c609719bSwdenk 27375d1ea7fSwdenk- 8xx CPU Options: (if using an MPC8xx cpu) 27466ca92a5Swdenk CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if 27566ca92a5Swdenk get_gclk_freq() cannot work 2765da627a4Swdenk e.g. if there is no 32KHz 2775da627a4Swdenk reference PIT/RTC clock 27866ca92a5Swdenk CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK 27966ca92a5Swdenk or XTAL/EXTAL) 280c609719bSwdenk 28166ca92a5Swdenk- 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU): 28266ca92a5Swdenk CFG_8xx_CPUCLK_MIN 28366ca92a5Swdenk CFG_8xx_CPUCLK_MAX 28466ca92a5Swdenk CONFIG_8xx_CPUCLK_DEFAULT 28575d1ea7fSwdenk See doc/README.MPC866 28675d1ea7fSwdenk 28775d1ea7fSwdenk CFG_MEASURE_CPUCLK 28875d1ea7fSwdenk 28975d1ea7fSwdenk Define this to measure the actual CPU clock instead 29075d1ea7fSwdenk of relying on the correctness of the configured 29175d1ea7fSwdenk values. Mostly useful for board bringup to make sure 29275d1ea7fSwdenk the PLL is locked at the intended frequency. Note 29375d1ea7fSwdenk that this requires a (stable) reference clock (32 kHz 29466ca92a5Swdenk RTC clock or CFG_8XX_XIN) 29575d1ea7fSwdenk 2960b953ffcSMarkus Klotzbuecher- Intel Monahans options: 2970b953ffcSMarkus Klotzbuecher CFG_MONAHANS_RUN_MODE_OSC_RATIO 2980b953ffcSMarkus Klotzbuecher 2990b953ffcSMarkus Klotzbuecher Defines the Monahans run mode to oscillator 3000b953ffcSMarkus Klotzbuecher ratio. Valid values are 8, 16, 24, 31. The core 3010b953ffcSMarkus Klotzbuecher frequency is this value multiplied by 13 MHz. 3020b953ffcSMarkus Klotzbuecher 3030b953ffcSMarkus Klotzbuecher CFG_MONAHANS_TURBO_RUN_MODE_RATIO 3040b953ffcSMarkus Klotzbuecher 3050b953ffcSMarkus Klotzbuecher Defines the Monahans turbo mode to oscillator 3060b953ffcSMarkus Klotzbuecher ratio. Valid values are 1 (default if undefined) and 3070b953ffcSMarkus Klotzbuecher 2. The core frequency as calculated above is multiplied 3080b953ffcSMarkus Klotzbuecher by this value. 3090b953ffcSMarkus Klotzbuecher 3105da627a4Swdenk- Linux Kernel Interface: 311c609719bSwdenk CONFIG_CLOCKS_IN_MHZ 312c609719bSwdenk 313c609719bSwdenk U-Boot stores all clock information in Hz 314c609719bSwdenk internally. For binary compatibility with older Linux 315c609719bSwdenk kernels (which expect the clocks passed in the 316c609719bSwdenk bd_info data to be in MHz) the environment variable 317c609719bSwdenk "clocks_in_mhz" can be defined so that U-Boot 318c609719bSwdenk converts clock data to MHZ before passing it to the 319c609719bSwdenk Linux kernel. 320c609719bSwdenk When CONFIG_CLOCKS_IN_MHZ is defined, a definition of 321c609719bSwdenk "clocks_in_mhz=1" is automatically included in the 322c609719bSwdenk default environment. 323c609719bSwdenk 3245da627a4Swdenk CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only] 3255da627a4Swdenk 3265da627a4Swdenk When transfering memsize parameter to linux, some versions 3275da627a4Swdenk expect it to be in bytes, others in MB. 3285da627a4Swdenk Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes. 3295da627a4Swdenk 330213bf8c8SGerald Van Baren CONFIG_OF_LIBFDT / CONFIG_OF_FLAT_TREE 331f57f70aaSWolfgang Denk 332f57f70aaSWolfgang Denk New kernel versions are expecting firmware settings to be 333213bf8c8SGerald Van Baren passed using flattened device trees (based on open firmware 334213bf8c8SGerald Van Baren concepts). 335213bf8c8SGerald Van Baren 336213bf8c8SGerald Van Baren CONFIG_OF_LIBFDT 337213bf8c8SGerald Van Baren * New libfdt-based support 338213bf8c8SGerald Van Baren * Adds the "fdt" command 339213bf8c8SGerald Van Baren * The bootm command does _not_ modify the fdt 340213bf8c8SGerald Van Baren 341213bf8c8SGerald Van Baren CONFIG_OF_FLAT_TREE 342213bf8c8SGerald Van Baren * Deprecated, see CONFIG_OF_LIBFDT 343213bf8c8SGerald Van Baren * Original ft_build.c-based support 344213bf8c8SGerald Van Baren * Automatically modifies the dft as part of the bootm command 345213bf8c8SGerald Van Baren * The environment variable "disable_of", when set, 346213bf8c8SGerald Van Baren disables this functionality. 347f57f70aaSWolfgang Denk 348f57f70aaSWolfgang Denk CONFIG_OF_FLAT_TREE_MAX_SIZE 349f57f70aaSWolfgang Denk 350f57f70aaSWolfgang Denk The maximum size of the constructed OF tree. 351f57f70aaSWolfgang Denk 352f57f70aaSWolfgang Denk OF_CPU - The proper name of the cpus node. 353c2871f03SKumar Gala OF_SOC - The proper name of the soc node. 354f57f70aaSWolfgang Denk OF_TBCLK - The timebase frequency. 355c2871f03SKumar Gala OF_STDOUT_PATH - The path to the console device 356f57f70aaSWolfgang Denk 357e4f880edSKumar Gala CONFIG_OF_HAS_BD_T 358e4f880edSKumar Gala 359213bf8c8SGerald Van Baren * CONFIG_OF_LIBFDT - enables the "fdt bd_t" command 360213bf8c8SGerald Van Baren * CONFIG_OF_FLAT_TREE - The resulting flat device tree 361213bf8c8SGerald Van Baren will have a copy of the bd_t. Space should be 362213bf8c8SGerald Van Baren pre-allocated in the dts for the bd_t. 363e4f880edSKumar Gala 364e4f880edSKumar Gala CONFIG_OF_HAS_UBOOT_ENV 365e4f880edSKumar Gala 366213bf8c8SGerald Van Baren * CONFIG_OF_LIBFDT - enables the "fdt bd_t" command 367213bf8c8SGerald Van Baren * CONFIG_OF_FLAT_TREE - The resulting flat device tree 368213bf8c8SGerald Van Baren will have a copy of u-boot's environment variables 369e4f880edSKumar Gala 3704e253137SKumar Gala CONFIG_OF_BOARD_SETUP 3714e253137SKumar Gala 3724e253137SKumar Gala Board code has addition modification that it wants to make 3734e253137SKumar Gala to the flat device tree before handing it off to the kernel 3746705d81eSwdenk 3750267768eSMatthew McClintock CONFIG_OF_BOOT_CPU 3760267768eSMatthew McClintock 3770267768eSMatthew McClintock This define fills in the correct boot cpu in the boot 3780267768eSMatthew McClintock param header, the default value is zero if undefined. 3790267768eSMatthew McClintock 3806705d81eSwdenk- Serial Ports: 3816705d81eSwdenk CFG_PL010_SERIAL 3826705d81eSwdenk 3836705d81eSwdenk Define this if you want support for Amba PrimeCell PL010 UARTs. 3846705d81eSwdenk 3856705d81eSwdenk CFG_PL011_SERIAL 3866705d81eSwdenk 3876705d81eSwdenk Define this if you want support for Amba PrimeCell PL011 UARTs. 3886705d81eSwdenk 3896705d81eSwdenk CONFIG_PL011_CLOCK 3906705d81eSwdenk 3916705d81eSwdenk If you have Amba PrimeCell PL011 UARTs, set this variable to 3926705d81eSwdenk the clock speed of the UARTs. 3936705d81eSwdenk 3946705d81eSwdenk CONFIG_PL01x_PORTS 3956705d81eSwdenk 3966705d81eSwdenk If you have Amba PrimeCell PL010 or PL011 UARTs on your board, 3976705d81eSwdenk define this to a list of base addresses for each (supported) 3986705d81eSwdenk port. See e.g. include/configs/versatile.h 3996705d81eSwdenk 4006705d81eSwdenk 401c609719bSwdenk- Console Interface: 402c609719bSwdenk Depending on board, define exactly one serial port 403c609719bSwdenk (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2, 404c609719bSwdenk CONFIG_8xx_CONS_SCC1, ...), or switch off the serial 405c609719bSwdenk console by defining CONFIG_8xx_CONS_NONE 406c609719bSwdenk 407c609719bSwdenk Note: if CONFIG_8xx_CONS_NONE is defined, the serial 408c609719bSwdenk port routines must be defined elsewhere 409c609719bSwdenk (i.e. serial_init(), serial_getc(), ...) 410c609719bSwdenk 411c609719bSwdenk CONFIG_CFB_CONSOLE 412c609719bSwdenk Enables console device for a color framebuffer. Needs following 413c609719bSwdenk defines (cf. smiLynxEM, i8042, board/eltec/bab7xx) 414c609719bSwdenk VIDEO_FB_LITTLE_ENDIAN graphic memory organisation 415c609719bSwdenk (default big endian) 416c609719bSwdenk VIDEO_HW_RECTFILL graphic chip supports 417c609719bSwdenk rectangle fill 418c609719bSwdenk (cf. smiLynxEM) 419c609719bSwdenk VIDEO_HW_BITBLT graphic chip supports 420c609719bSwdenk bit-blit (cf. smiLynxEM) 421c609719bSwdenk VIDEO_VISIBLE_COLS visible pixel columns 422c609719bSwdenk (cols=pitch) 423c609719bSwdenk VIDEO_VISIBLE_ROWS visible pixel rows 424c609719bSwdenk VIDEO_PIXEL_SIZE bytes per pixel 425c609719bSwdenk VIDEO_DATA_FORMAT graphic data format 426c609719bSwdenk (0-5, cf. cfb_console.c) 427c609719bSwdenk VIDEO_FB_ADRS framebuffer address 428c609719bSwdenk VIDEO_KBD_INIT_FCT keyboard int fct 429c609719bSwdenk (i.e. i8042_kbd_init()) 430c609719bSwdenk VIDEO_TSTC_FCT test char fct 431c609719bSwdenk (i.e. i8042_tstc) 432c609719bSwdenk VIDEO_GETC_FCT get char fct 433c609719bSwdenk (i.e. i8042_getc) 434c609719bSwdenk CONFIG_CONSOLE_CURSOR cursor drawing on/off 435c609719bSwdenk (requires blink timer 436c609719bSwdenk cf. i8042.c) 437c609719bSwdenk CFG_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c) 438c609719bSwdenk CONFIG_CONSOLE_TIME display time/date info in 439c609719bSwdenk upper right corner 440602ad3b3SJon Loeliger (requires CONFIG_CMD_DATE) 441c609719bSwdenk CONFIG_VIDEO_LOGO display Linux logo in 442c609719bSwdenk upper left corner 443a6c7ad2fSwdenk CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of 444a6c7ad2fSwdenk linux_logo.h for logo. 445a6c7ad2fSwdenk Requires CONFIG_VIDEO_LOGO 446c609719bSwdenk CONFIG_CONSOLE_EXTRA_INFO 447c609719bSwdenk addional board info beside 448c609719bSwdenk the logo 449c609719bSwdenk 450c609719bSwdenk When CONFIG_CFB_CONSOLE is defined, video console is 451c609719bSwdenk default i/o. Serial console can be forced with 452c609719bSwdenk environment 'console=serial'. 453c609719bSwdenk 454a3ad8e26Swdenk When CONFIG_SILENT_CONSOLE is defined, all console 455a3ad8e26Swdenk messages (by U-Boot and Linux!) can be silenced with 456a3ad8e26Swdenk the "silent" environment variable. See 457a3ad8e26Swdenk doc/README.silent for more information. 458a3ad8e26Swdenk 459c609719bSwdenk- Console Baudrate: 460c609719bSwdenk CONFIG_BAUDRATE - in bps 461c609719bSwdenk Select one of the baudrates listed in 462c609719bSwdenk CFG_BAUDRATE_TABLE, see below. 4633bbc899fSwdenk CFG_BRGCLK_PRESCALE, baudrate prescale 464c609719bSwdenk 465c609719bSwdenk- Interrupt driven serial port input: 466c609719bSwdenk CONFIG_SERIAL_SOFTWARE_FIFO 467c609719bSwdenk 468c609719bSwdenk PPC405GP only. 469c609719bSwdenk Use an interrupt handler for receiving data on the 470c609719bSwdenk serial port. It also enables using hardware handshake 471c609719bSwdenk (RTS/CTS) and UART's built-in FIFO. Set the number of 472c609719bSwdenk bytes the interrupt driven input buffer should have. 473c609719bSwdenk 474109c0e3aSwdenk Leave undefined to disable this feature, including 475109c0e3aSwdenk disable the buffer and hardware handshake. 476c609719bSwdenk 4771d49b1f3Sstroese- Console UART Number: 4781d49b1f3Sstroese CONFIG_UART1_CONSOLE 4791d49b1f3Sstroese 4800c8721a4SWolfgang Denk AMCC PPC4xx only. 4811d49b1f3Sstroese If defined internal UART1 (and not UART0) is used 4821d49b1f3Sstroese as default U-Boot console. 4831d49b1f3Sstroese 484c609719bSwdenk- Boot Delay: CONFIG_BOOTDELAY - in seconds 485c609719bSwdenk Delay before automatically booting the default image; 486c609719bSwdenk set to -1 to disable autoboot. 487c609719bSwdenk 488c609719bSwdenk See doc/README.autoboot for these options that 489c609719bSwdenk work with CONFIG_BOOTDELAY. None are required. 490c609719bSwdenk CONFIG_BOOT_RETRY_TIME 491c609719bSwdenk CONFIG_BOOT_RETRY_MIN 492c609719bSwdenk CONFIG_AUTOBOOT_KEYED 493c609719bSwdenk CONFIG_AUTOBOOT_PROMPT 494c609719bSwdenk CONFIG_AUTOBOOT_DELAY_STR 495c609719bSwdenk CONFIG_AUTOBOOT_STOP_STR 496c609719bSwdenk CONFIG_AUTOBOOT_DELAY_STR2 497c609719bSwdenk CONFIG_AUTOBOOT_STOP_STR2 498c609719bSwdenk CONFIG_ZERO_BOOTDELAY_CHECK 499c609719bSwdenk CONFIG_RESET_TO_RETRY 500c609719bSwdenk 501c609719bSwdenk- Autoboot Command: 502c609719bSwdenk CONFIG_BOOTCOMMAND 503c609719bSwdenk Only needed when CONFIG_BOOTDELAY is enabled; 504c609719bSwdenk define a command string that is automatically executed 505c609719bSwdenk when no character is read on the console interface 506c609719bSwdenk within "Boot Delay" after reset. 507c609719bSwdenk 508c609719bSwdenk CONFIG_BOOTARGS 509c609719bSwdenk This can be used to pass arguments to the bootm 510c609719bSwdenk command. The value of CONFIG_BOOTARGS goes into the 511c609719bSwdenk environment value "bootargs". 512c609719bSwdenk 513c609719bSwdenk CONFIG_RAMBOOT and CONFIG_NFSBOOT 514c609719bSwdenk The value of these goes into the environment as 515c609719bSwdenk "ramboot" and "nfsboot" respectively, and can be used 516c609719bSwdenk as a convenience, when switching between booting from 517c609719bSwdenk ram and nfs. 518c609719bSwdenk 519c609719bSwdenk- Pre-Boot Commands: 520c609719bSwdenk CONFIG_PREBOOT 521c609719bSwdenk 522c609719bSwdenk When this option is #defined, the existence of the 523c609719bSwdenk environment variable "preboot" will be checked 524c609719bSwdenk immediately before starting the CONFIG_BOOTDELAY 525c609719bSwdenk countdown and/or running the auto-boot command resp. 526c609719bSwdenk entering interactive mode. 527c609719bSwdenk 528c609719bSwdenk This feature is especially useful when "preboot" is 529c609719bSwdenk automatically generated or modified. For an example 530c609719bSwdenk see the LWMON board specific code: here "preboot" is 531c609719bSwdenk modified when the user holds down a certain 532c609719bSwdenk combination of keys on the (special) keyboard when 533c609719bSwdenk booting the systems 534c609719bSwdenk 535c609719bSwdenk- Serial Download Echo Mode: 536c609719bSwdenk CONFIG_LOADS_ECHO 537c609719bSwdenk If defined to 1, all characters received during a 538c609719bSwdenk serial download (using the "loads" command) are 539c609719bSwdenk echoed back. This might be needed by some terminal 540c609719bSwdenk emulations (like "cu"), but may as well just take 541c609719bSwdenk time on others. This setting #define's the initial 542c609719bSwdenk value of the "loads_echo" environment variable. 543c609719bSwdenk 544602ad3b3SJon Loeliger- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined) 545c609719bSwdenk CONFIG_KGDB_BAUDRATE 546c609719bSwdenk Select one of the baudrates listed in 547c609719bSwdenk CFG_BAUDRATE_TABLE, see below. 548c609719bSwdenk 549c609719bSwdenk- Monitor Functions: 550602ad3b3SJon Loeliger Monitor commands can be included or excluded 551602ad3b3SJon Loeliger from the build by using the #include files 552602ad3b3SJon Loeliger "config_cmd_all.h" and #undef'ing unwanted 553602ad3b3SJon Loeliger commands, or using "config_cmd_default.h" 554602ad3b3SJon Loeliger and augmenting with additional #define's 555602ad3b3SJon Loeliger for wanted commands. 556c609719bSwdenk 557602ad3b3SJon Loeliger The default command configuration includes all commands 558602ad3b3SJon Loeliger except those marked below with a "*". 559602ad3b3SJon Loeliger 560602ad3b3SJon Loeliger CONFIG_CMD_ASKENV * ask for env variable 561602ad3b3SJon Loeliger CONFIG_CMD_AUTOSCRIPT Autoscript Support 562602ad3b3SJon Loeliger CONFIG_CMD_BDI bdinfo 563602ad3b3SJon Loeliger CONFIG_CMD_BEDBUG * Include BedBug Debugger 564602ad3b3SJon Loeliger CONFIG_CMD_BMP * BMP support 565602ad3b3SJon Loeliger CONFIG_CMD_BSP * Board specific commands 566602ad3b3SJon Loeliger CONFIG_CMD_BOOTD bootd 567602ad3b3SJon Loeliger CONFIG_CMD_CACHE * icache, dcache 568602ad3b3SJon Loeliger CONFIG_CMD_CONSOLE coninfo 569602ad3b3SJon Loeliger CONFIG_CMD_DATE * support for RTC, date/time... 570602ad3b3SJon Loeliger CONFIG_CMD_DHCP * DHCP support 571602ad3b3SJon Loeliger CONFIG_CMD_DIAG * Diagnostics 572602ad3b3SJon Loeliger CONFIG_CMD_DOC * Disk-On-Chip Support 573602ad3b3SJon Loeliger CONFIG_CMD_DTT * Digital Therm and Thermostat 574602ad3b3SJon Loeliger CONFIG_CMD_ECHO echo arguments 575602ad3b3SJon Loeliger CONFIG_CMD_EEPROM * EEPROM read/write support 576602ad3b3SJon Loeliger CONFIG_CMD_ELF * bootelf, bootvx 577602ad3b3SJon Loeliger CONFIG_CMD_ENV saveenv 578602ad3b3SJon Loeliger CONFIG_CMD_FDC * Floppy Disk Support 579602ad3b3SJon Loeliger CONFIG_CMD_FAT * FAT partition support 580602ad3b3SJon Loeliger CONFIG_CMD_FDOS * Dos diskette Support 581602ad3b3SJon Loeliger CONFIG_CMD_FLASH flinfo, erase, protect 582602ad3b3SJon Loeliger CONFIG_CMD_FPGA FPGA device initialization support 583602ad3b3SJon Loeliger CONFIG_CMD_HWFLOW * RTS/CTS hw flow control 584602ad3b3SJon Loeliger CONFIG_CMD_I2C * I2C serial bus support 585602ad3b3SJon Loeliger CONFIG_CMD_IDE * IDE harddisk support 586602ad3b3SJon Loeliger CONFIG_CMD_IMI iminfo 587602ad3b3SJon Loeliger CONFIG_CMD_IMLS List all found images 588602ad3b3SJon Loeliger CONFIG_CMD_IMMAP * IMMR dump support 589602ad3b3SJon Loeliger CONFIG_CMD_IRQ * irqinfo 590602ad3b3SJon Loeliger CONFIG_CMD_ITEST Integer/string test of 2 values 591602ad3b3SJon Loeliger CONFIG_CMD_JFFS2 * JFFS2 Support 592602ad3b3SJon Loeliger CONFIG_CMD_KGDB * kgdb 593602ad3b3SJon Loeliger CONFIG_CMD_LOADB loadb 594602ad3b3SJon Loeliger CONFIG_CMD_LOADS loads 595602ad3b3SJon Loeliger CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base, 59656523f12Swdenk loop, loopw, mtest 597602ad3b3SJon Loeliger CONFIG_CMD_MISC Misc functions like sleep etc 598602ad3b3SJon Loeliger CONFIG_CMD_MMC * MMC memory mapped support 599602ad3b3SJon Loeliger CONFIG_CMD_MII * MII utility commands 600602ad3b3SJon Loeliger CONFIG_CMD_NAND * NAND support 601602ad3b3SJon Loeliger CONFIG_CMD_NET bootp, tftpboot, rarpboot 602602ad3b3SJon Loeliger CONFIG_CMD_PCI * pciinfo 603602ad3b3SJon Loeliger CONFIG_CMD_PCMCIA * PCMCIA support 604602ad3b3SJon Loeliger CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network 605602ad3b3SJon Loeliger host 606602ad3b3SJon Loeliger CONFIG_CMD_PORTIO * Port I/O 607602ad3b3SJon Loeliger CONFIG_CMD_REGINFO * Register dump 608602ad3b3SJon Loeliger CONFIG_CMD_RUN run command in env variable 609602ad3b3SJon Loeliger CONFIG_CMD_SAVES * save S record dump 610602ad3b3SJon Loeliger CONFIG_CMD_SCSI * SCSI Support 611602ad3b3SJon Loeliger CONFIG_CMD_SDRAM * print SDRAM configuration information 612602ad3b3SJon Loeliger (requires CONFIG_CMD_I2C) 613602ad3b3SJon Loeliger CONFIG_CMD_SETGETDCR Support for DCR Register access 614602ad3b3SJon Loeliger (4xx only) 615602ad3b3SJon Loeliger CONFIG_CMD_SPI * SPI serial bus support 616602ad3b3SJon Loeliger CONFIG_CMD_USB * USB support 617602ad3b3SJon Loeliger CONFIG_CMD_VFD * VFD support (TRAB) 618602ad3b3SJon Loeliger CONFIG_CMD_BSP * Board SPecific functions 619602ad3b3SJon Loeliger CONFIG_CMD_CDP * Cisco Discover Protocol support 620602ad3b3SJon Loeliger CONFIG_CMD_FSL * Microblaze FSL support 621c609719bSwdenk 622c609719bSwdenk 623c609719bSwdenk EXAMPLE: If you want all functions except of network 624c609719bSwdenk support you can write: 625c609719bSwdenk 626602ad3b3SJon Loeliger #include "config_cmd_all.h" 627602ad3b3SJon Loeliger #undef CONFIG_CMD_NET 628c609719bSwdenk 629213bf8c8SGerald Van Baren Other Commands: 630213bf8c8SGerald Van Baren fdt (flattened device tree) command: CONFIG_OF_LIBFDT 631c609719bSwdenk 632c609719bSwdenk Note: Don't enable the "icache" and "dcache" commands 633602ad3b3SJon Loeliger (configuration option CONFIG_CMD_CACHE) unless you know 634c609719bSwdenk what you (and your U-Boot users) are doing. Data 635c609719bSwdenk cache cannot be enabled on systems like the 8xx or 636c609719bSwdenk 8260 (where accesses to the IMMR region must be 637c609719bSwdenk uncached), and it cannot be disabled on all other 638c609719bSwdenk systems where we (mis-) use the data cache to hold an 639c609719bSwdenk initial stack and some data. 640c609719bSwdenk 641c609719bSwdenk 642c609719bSwdenk XXX - this list needs to get updated! 643c609719bSwdenk 644c609719bSwdenk- Watchdog: 645c609719bSwdenk CONFIG_WATCHDOG 646c609719bSwdenk If this variable is defined, it enables watchdog 6477152b1d0Swdenk support. There must be support in the platform specific 648c609719bSwdenk code for a watchdog. For the 8xx and 8260 CPUs, the 649c609719bSwdenk SIU Watchdog feature is enabled in the SYPCR 650c609719bSwdenk register. 651c609719bSwdenk 652c1551ea8Sstroese- U-Boot Version: 653c1551ea8Sstroese CONFIG_VERSION_VARIABLE 654c1551ea8Sstroese If this variable is defined, an environment variable 655c1551ea8Sstroese named "ver" is created by U-Boot showing the U-Boot 656c1551ea8Sstroese version as printed by the "version" command. 657c1551ea8Sstroese This variable is readonly. 658c1551ea8Sstroese 659c609719bSwdenk- Real-Time Clock: 660c609719bSwdenk 661602ad3b3SJon Loeliger When CONFIG_CMD_DATE is selected, the type of the RTC 662c609719bSwdenk has to be selected, too. Define exactly one of the 663c609719bSwdenk following options: 664c609719bSwdenk 665c609719bSwdenk CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx 666c609719bSwdenk CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC 667c609719bSwdenk CONFIG_RTC_MC146818 - use MC146818 RTC 6681cb8e980Swdenk CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC 669c609719bSwdenk CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC 6707f70e853Swdenk CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC 6713bac3513Swdenk CONFIG_RTC_DS164x - use Dallas DS164x RTC 6724c0d4c3bSwdenk CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC 673c609719bSwdenk 674b37c7e5eSwdenk Note that if the RTC uses I2C, then the I2C interface 675b37c7e5eSwdenk must also be configured. See I2C Support, below. 676b37c7e5eSwdenk 677c609719bSwdenk- Timestamp Support: 678c609719bSwdenk 679c609719bSwdenk When CONFIG_TIMESTAMP is selected, the timestamp 680c609719bSwdenk (date and time) of an image is printed by image 681c609719bSwdenk commands like bootm or iminfo. This option is 682602ad3b3SJon Loeliger automatically enabled when you select CONFIG_CMD_DATE . 683c609719bSwdenk 684c609719bSwdenk- Partition Support: 685c609719bSwdenk CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION 686c609719bSwdenk and/or CONFIG_ISO_PARTITION 687c609719bSwdenk 688602ad3b3SJon Loeliger If IDE or SCSI support is enabled (CONFIG_CMD_IDE or 689602ad3b3SJon Loeliger CONFIG_CMD_SCSI) you must configure support for at least 690c609719bSwdenk one partition type as well. 691c609719bSwdenk 692c609719bSwdenk- IDE Reset method: 6934d13cbadSwdenk CONFIG_IDE_RESET_ROUTINE - this is defined in several 6944d13cbadSwdenk board configurations files but used nowhere! 695c609719bSwdenk 6964d13cbadSwdenk CONFIG_IDE_RESET - is this is defined, IDE Reset will 6974d13cbadSwdenk be performed by calling the function 6984d13cbadSwdenk ide_set_reset(int reset) 6994d13cbadSwdenk which has to be defined in a board specific file 700c609719bSwdenk 701c609719bSwdenk- ATAPI Support: 702c609719bSwdenk CONFIG_ATAPI 703c609719bSwdenk 704c609719bSwdenk Set this to enable ATAPI support. 705c609719bSwdenk 706c40b2956Swdenk- LBA48 Support 707c40b2956Swdenk CONFIG_LBA48 708c40b2956Swdenk 709c40b2956Swdenk Set this to enable support for disks larger than 137GB 710c40b2956Swdenk Also look at CFG_64BIT_LBA ,CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL 711c40b2956Swdenk Whithout these , LBA48 support uses 32bit variables and will 'only' 712c40b2956Swdenk support disks up to 2.1TB. 713c40b2956Swdenk 714c40b2956Swdenk CFG_64BIT_LBA: 715c40b2956Swdenk When enabled, makes the IDE subsystem use 64bit sector addresses. 716c40b2956Swdenk Default is 32bit. 717c40b2956Swdenk 718c609719bSwdenk- SCSI Support: 719c609719bSwdenk At the moment only there is only support for the 720c609719bSwdenk SYM53C8XX SCSI controller; define 721c609719bSwdenk CONFIG_SCSI_SYM53C8XX to enable it. 722c609719bSwdenk 723c609719bSwdenk CFG_SCSI_MAX_LUN [8], CFG_SCSI_MAX_SCSI_ID [7] and 724c609719bSwdenk CFG_SCSI_MAX_DEVICE [CFG_SCSI_MAX_SCSI_ID * 725c609719bSwdenk CFG_SCSI_MAX_LUN] can be adjusted to define the 726c609719bSwdenk maximum numbers of LUNs, SCSI ID's and target 727c609719bSwdenk devices. 728c609719bSwdenk CFG_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz) 729c609719bSwdenk 730c609719bSwdenk- NETWORK Support (PCI): 731682011ffSwdenk CONFIG_E1000 732682011ffSwdenk Support for Intel 8254x gigabit chips. 733682011ffSwdenk 734c609719bSwdenk CONFIG_EEPRO100 735c609719bSwdenk Support for Intel 82557/82559/82559ER chips. 736c609719bSwdenk Optional CONFIG_EEPRO100_SROM_WRITE enables eeprom 737c609719bSwdenk write routine for first time initialisation. 738c609719bSwdenk 739c609719bSwdenk CONFIG_TULIP 740c609719bSwdenk Support for Digital 2114x chips. 741c609719bSwdenk Optional CONFIG_TULIP_SELECT_MEDIA for board specific 742c609719bSwdenk modem chip initialisation (KS8761/QS6611). 743c609719bSwdenk 744c609719bSwdenk CONFIG_NATSEMI 745c609719bSwdenk Support for National dp83815 chips. 746c609719bSwdenk 747c609719bSwdenk CONFIG_NS8382X 748c609719bSwdenk Support for National dp8382[01] gigabit chips. 749c609719bSwdenk 75045219c46Swdenk- NETWORK Support (other): 75145219c46Swdenk 75245219c46Swdenk CONFIG_DRIVER_LAN91C96 75345219c46Swdenk Support for SMSC's LAN91C96 chips. 75445219c46Swdenk 75545219c46Swdenk CONFIG_LAN91C96_BASE 75645219c46Swdenk Define this to hold the physical address 75745219c46Swdenk of the LAN91C96's I/O space 75845219c46Swdenk 75945219c46Swdenk CONFIG_LAN91C96_USE_32_BIT 76045219c46Swdenk Define this to enable 32 bit addressing 76145219c46Swdenk 762f39748aeSwdenk CONFIG_DRIVER_SMC91111 763f39748aeSwdenk Support for SMSC's LAN91C111 chip 764f39748aeSwdenk 765f39748aeSwdenk CONFIG_SMC91111_BASE 766f39748aeSwdenk Define this to hold the physical address 767f39748aeSwdenk of the device (I/O space) 768f39748aeSwdenk 769f39748aeSwdenk CONFIG_SMC_USE_32_BIT 770f39748aeSwdenk Define this if data bus is 32 bits 771f39748aeSwdenk 772f39748aeSwdenk CONFIG_SMC_USE_IOFUNCS 773f39748aeSwdenk Define this to use i/o functions instead of macros 774f39748aeSwdenk (some hardware wont work with macros) 775f39748aeSwdenk 776c609719bSwdenk- USB Support: 777c609719bSwdenk At the moment only the UHCI host controller is 7784d13cbadSwdenk supported (PIP405, MIP405, MPC5200); define 779c609719bSwdenk CONFIG_USB_UHCI to enable it. 780c609719bSwdenk define CONFIG_USB_KEYBOARD to enable the USB Keyboard 78130d56faeSwdenk and define CONFIG_USB_STORAGE to enable the USB 782c609719bSwdenk storage devices. 783c609719bSwdenk Note: 784c609719bSwdenk Supported are USB Keyboards and USB Floppy drives 785c609719bSwdenk (TEAC FD-05PUB). 7864d13cbadSwdenk MPC5200 USB requires additional defines: 7874d13cbadSwdenk CONFIG_USB_CLOCK 7884d13cbadSwdenk for 528 MHz Clock: 0x0001bbbb 7894d13cbadSwdenk CONFIG_USB_CONFIG 7904d13cbadSwdenk for differential drivers: 0x00001000 7914d13cbadSwdenk for single ended drivers: 0x00005000 792fdcfaa1bSZhang Wei CFG_USB_EVENT_POLL 793fdcfaa1bSZhang Wei May be defined to allow interrupt polling 794fdcfaa1bSZhang Wei instead of using asynchronous interrupts 7954d13cbadSwdenk 79616c8d5e7SWolfgang Denk- USB Device: 79716c8d5e7SWolfgang Denk Define the below if you wish to use the USB console. 79816c8d5e7SWolfgang Denk Once firmware is rebuilt from a serial console issue the 79916c8d5e7SWolfgang Denk command "setenv stdin usbtty; setenv stdout usbtty" and 80016c8d5e7SWolfgang Denk attach your usb cable. The Unix command "dmesg" should print 80116c8d5e7SWolfgang Denk it has found a new device. The environment variable usbtty 80216c8d5e7SWolfgang Denk can be set to gserial or cdc_acm to enable your device to 80316c8d5e7SWolfgang Denk appear to a USB host as a Linux gserial device or a 80416c8d5e7SWolfgang Denk Common Device Class Abstract Control Model serial device. 80516c8d5e7SWolfgang Denk If you select usbtty = gserial you should be able to enumerate 80616c8d5e7SWolfgang Denk a Linux host by 80716c8d5e7SWolfgang Denk # modprobe usbserial vendor=0xVendorID product=0xProductID 80816c8d5e7SWolfgang Denk else if using cdc_acm, simply setting the environment 80916c8d5e7SWolfgang Denk variable usbtty to be cdc_acm should suffice. The following 81016c8d5e7SWolfgang Denk might be defined in YourBoardName.h 81116c8d5e7SWolfgang Denk 81216c8d5e7SWolfgang Denk CONFIG_USB_DEVICE 81316c8d5e7SWolfgang Denk Define this to build a UDC device 81416c8d5e7SWolfgang Denk 81516c8d5e7SWolfgang Denk CONFIG_USB_TTY 81616c8d5e7SWolfgang Denk Define this to have a tty type of device available to 81716c8d5e7SWolfgang Denk talk to the UDC device 81816c8d5e7SWolfgang Denk 81916c8d5e7SWolfgang Denk CFG_CONSOLE_IS_IN_ENV 82016c8d5e7SWolfgang Denk Define this if you want stdin, stdout &/or stderr to 82116c8d5e7SWolfgang Denk be set to usbtty. 82216c8d5e7SWolfgang Denk 82316c8d5e7SWolfgang Denk mpc8xx: 82416c8d5e7SWolfgang Denk CFG_USB_EXTC_CLK 0xBLAH 82516c8d5e7SWolfgang Denk Derive USB clock from external clock "blah" 82616c8d5e7SWolfgang Denk - CFG_USB_EXTC_CLK 0x02 82716c8d5e7SWolfgang Denk 82816c8d5e7SWolfgang Denk CFG_USB_BRG_CLK 0xBLAH 82916c8d5e7SWolfgang Denk Derive USB clock from brgclk 83016c8d5e7SWolfgang Denk - CFG_USB_BRG_CLK 0x04 83116c8d5e7SWolfgang Denk 83216c8d5e7SWolfgang Denk If you have a USB-IF assigned VendorID then you may wish to 83316c8d5e7SWolfgang Denk define your own vendor specific values either in BoardName.h 83416c8d5e7SWolfgang Denk or directly in usbd_vendor_info.h. If you don't define 83516c8d5e7SWolfgang Denk CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME, 83616c8d5e7SWolfgang Denk CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot 83716c8d5e7SWolfgang Denk should pretend to be a Linux device to it's target host. 83816c8d5e7SWolfgang Denk 83916c8d5e7SWolfgang Denk CONFIG_USBD_MANUFACTURER 84016c8d5e7SWolfgang Denk Define this string as the name of your company for 84116c8d5e7SWolfgang Denk - CONFIG_USBD_MANUFACTURER "my company" 84216c8d5e7SWolfgang Denk 84316c8d5e7SWolfgang Denk CONFIG_USBD_PRODUCT_NAME 84416c8d5e7SWolfgang Denk Define this string as the name of your product 84516c8d5e7SWolfgang Denk - CONFIG_USBD_PRODUCT_NAME "acme usb device" 84616c8d5e7SWolfgang Denk 84716c8d5e7SWolfgang Denk CONFIG_USBD_VENDORID 84816c8d5e7SWolfgang Denk Define this as your assigned Vendor ID from the USB 84916c8d5e7SWolfgang Denk Implementors Forum. This *must* be a genuine Vendor ID 85016c8d5e7SWolfgang Denk to avoid polluting the USB namespace. 85116c8d5e7SWolfgang Denk - CONFIG_USBD_VENDORID 0xFFFF 85216c8d5e7SWolfgang Denk 85316c8d5e7SWolfgang Denk CONFIG_USBD_PRODUCTID 85416c8d5e7SWolfgang Denk Define this as the unique Product ID 85516c8d5e7SWolfgang Denk for your device 85616c8d5e7SWolfgang Denk - CONFIG_USBD_PRODUCTID 0xFFFF 85716c8d5e7SWolfgang Denk 858c609719bSwdenk 85971f95118Swdenk- MMC Support: 86071f95118Swdenk The MMC controller on the Intel PXA is supported. To 86171f95118Swdenk enable this define CONFIG_MMC. The MMC can be 86271f95118Swdenk accessed from the boot prompt by mapping the device 86371f95118Swdenk to physical memory similar to flash. Command line is 864602ad3b3SJon Loeliger enabled with CONFIG_CMD_MMC. The MMC driver also works with 865602ad3b3SJon Loeliger the FAT fs. This is enabled with CONFIG_CMD_FAT. 86671f95118Swdenk 8676705d81eSwdenk- Journaling Flash filesystem support: 8686705d81eSwdenk CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE, 8696705d81eSwdenk CONFIG_JFFS2_NAND_DEV 8706705d81eSwdenk Define these for a default partition on a NAND device 8716705d81eSwdenk 8726705d81eSwdenk CFG_JFFS2_FIRST_SECTOR, 8736705d81eSwdenk CFG_JFFS2_FIRST_BANK, CFG_JFFS2_NUM_BANKS 8746705d81eSwdenk Define these for a default partition on a NOR device 8756705d81eSwdenk 8766705d81eSwdenk CFG_JFFS_CUSTOM_PART 8776705d81eSwdenk Define this to create an own partition. You have to provide a 8786705d81eSwdenk function struct part_info* jffs2_part_info(int part_num) 8796705d81eSwdenk 8806705d81eSwdenk If you define only one JFFS2 partition you may also want to 8816705d81eSwdenk #define CFG_JFFS_SINGLE_PART 1 8826705d81eSwdenk to disable the command chpart. This is the default when you 8836705d81eSwdenk have not defined a custom partition 8846705d81eSwdenk 885c609719bSwdenk- Keyboard Support: 886c609719bSwdenk CONFIG_ISA_KEYBOARD 887c609719bSwdenk 888c609719bSwdenk Define this to enable standard (PC-Style) keyboard 889c609719bSwdenk support 890c609719bSwdenk 891c609719bSwdenk CONFIG_I8042_KBD 892c609719bSwdenk Standard PC keyboard driver with US (is default) and 893c609719bSwdenk GERMAN key layout (switch via environment 'keymap=de') support. 894c609719bSwdenk Export function i8042_kbd_init, i8042_tstc and i8042_getc 895c609719bSwdenk for cfb_console. Supports cursor blinking. 896c609719bSwdenk 897c609719bSwdenk- Video support: 898c609719bSwdenk CONFIG_VIDEO 899c609719bSwdenk 900c609719bSwdenk Define this to enable video support (for output to 901c609719bSwdenk video). 902c609719bSwdenk 903c609719bSwdenk CONFIG_VIDEO_CT69000 904c609719bSwdenk 905c609719bSwdenk Enable Chips & Technologies 69000 Video chip 906c609719bSwdenk 907c609719bSwdenk CONFIG_VIDEO_SMI_LYNXEM 908eeb1b77bSwdenk Enable Silicon Motion SMI 712/710/810 Video chip. The 909eeb1b77bSwdenk video output is selected via environment 'videoout' 910eeb1b77bSwdenk (1 = LCD and 2 = CRT). If videoout is undefined, CRT is 911eeb1b77bSwdenk assumed. 912c609719bSwdenk 913eeb1b77bSwdenk For the CT69000 and SMI_LYNXEM drivers, videomode is 914eeb1b77bSwdenk selected via environment 'videomode'. Two diferent ways 915eeb1b77bSwdenk are possible: 916eeb1b77bSwdenk - "videomode=num" 'num' is a standard LiLo mode numbers. 917eeb1b77bSwdenk Following standard modes are supported (* is default): 918eeb1b77bSwdenk 919eeb1b77bSwdenk Colors 640x480 800x600 1024x768 1152x864 1280x1024 920eeb1b77bSwdenk -------------+--------------------------------------------- 921eeb1b77bSwdenk 8 bits | 0x301* 0x303 0x305 0x161 0x307 922eeb1b77bSwdenk 15 bits | 0x310 0x313 0x316 0x162 0x319 923eeb1b77bSwdenk 16 bits | 0x311 0x314 0x317 0x163 0x31A 924eeb1b77bSwdenk 24 bits | 0x312 0x315 0x318 ? 0x31B 925eeb1b77bSwdenk -------------+--------------------------------------------- 926c609719bSwdenk (i.e. setenv videomode 317; saveenv; reset;) 927c609719bSwdenk 928eeb1b77bSwdenk - "videomode=bootargs" all the video parameters are parsed 929eeb1b77bSwdenk from the bootargs. (See drivers/videomodes.c) 930eeb1b77bSwdenk 931eeb1b77bSwdenk 932a6c7ad2fSwdenk CONFIG_VIDEO_SED13806 933a6c7ad2fSwdenk Enable Epson SED13806 driver. This driver supports 8bpp 934a6c7ad2fSwdenk and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP 935a6c7ad2fSwdenk or CONFIG_VIDEO_SED13806_16BPP 936a6c7ad2fSwdenk 937682011ffSwdenk- Keyboard Support: 938682011ffSwdenk CONFIG_KEYBOARD 939682011ffSwdenk 940682011ffSwdenk Define this to enable a custom keyboard support. 941682011ffSwdenk This simply calls drv_keyboard_init() which must be 942682011ffSwdenk defined in your board-specific files. 943682011ffSwdenk The only board using this so far is RBC823. 944a6c7ad2fSwdenk 945c609719bSwdenk- LCD Support: CONFIG_LCD 946c609719bSwdenk 947c609719bSwdenk Define this to enable LCD support (for output to LCD 948c609719bSwdenk display); also select one of the supported displays 949c609719bSwdenk by defining one of these: 950c609719bSwdenk 951fd3103bbSwdenk CONFIG_NEC_NL6448AC33: 952c609719bSwdenk 953fd3103bbSwdenk NEC NL6448AC33-18. Active, color, single scan. 954c609719bSwdenk 955fd3103bbSwdenk CONFIG_NEC_NL6448BC20 956c609719bSwdenk 957fd3103bbSwdenk NEC NL6448BC20-08. 6.5", 640x480. 958fd3103bbSwdenk Active, color, single scan. 959fd3103bbSwdenk 960fd3103bbSwdenk CONFIG_NEC_NL6448BC33_54 961fd3103bbSwdenk 962fd3103bbSwdenk NEC NL6448BC33-54. 10.4", 640x480. 963c609719bSwdenk Active, color, single scan. 964c609719bSwdenk 965c609719bSwdenk CONFIG_SHARP_16x9 966c609719bSwdenk 967c609719bSwdenk Sharp 320x240. Active, color, single scan. 968c609719bSwdenk It isn't 16x9, and I am not sure what it is. 969c609719bSwdenk 970c609719bSwdenk CONFIG_SHARP_LQ64D341 971c609719bSwdenk 972c609719bSwdenk Sharp LQ64D341 display, 640x480. 973c609719bSwdenk Active, color, single scan. 974c609719bSwdenk 975c609719bSwdenk CONFIG_HLD1045 976c609719bSwdenk 977c609719bSwdenk HLD1045 display, 640x480. 978c609719bSwdenk Active, color, single scan. 979c609719bSwdenk 980c609719bSwdenk CONFIG_OPTREX_BW 981c609719bSwdenk 982c609719bSwdenk Optrex CBL50840-2 NF-FW 99 22 M5 983c609719bSwdenk or 984c609719bSwdenk Hitachi LMG6912RPFC-00T 985c609719bSwdenk or 986c609719bSwdenk Hitachi SP14Q002 987c609719bSwdenk 988c609719bSwdenk 320x240. Black & white. 989c609719bSwdenk 990c609719bSwdenk Normally display is black on white background; define 991c609719bSwdenk CFG_WHITE_ON_BLACK to get it inverted. 992c609719bSwdenk 9937152b1d0Swdenk- Splash Screen Support: CONFIG_SPLASH_SCREEN 994d791b1dcSwdenk 995d791b1dcSwdenk If this option is set, the environment is checked for 996d791b1dcSwdenk a variable "splashimage". If found, the usual display 997d791b1dcSwdenk of logo, copyright and system information on the LCD 998e94d2cd9Swdenk is suppressed and the BMP image at the address 999d791b1dcSwdenk specified in "splashimage" is loaded instead. The 1000d791b1dcSwdenk console is redirected to the "nulldev", too. This 1001d791b1dcSwdenk allows for a "silent" boot where a splash screen is 1002d791b1dcSwdenk loaded very quickly after power-on. 1003d791b1dcSwdenk 100498f4a3dfSStefan Roese- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP 100598f4a3dfSStefan Roese 100698f4a3dfSStefan Roese If this option is set, additionally to standard BMP 100798f4a3dfSStefan Roese images, gzipped BMP images can be displayed via the 100898f4a3dfSStefan Roese splashscreen support or the bmp command. 100998f4a3dfSStefan Roese 1010c29fdfc1Swdenk- Compression support: 1011c29fdfc1Swdenk CONFIG_BZIP2 1012c29fdfc1Swdenk 1013c29fdfc1Swdenk If this option is set, support for bzip2 compressed 1014c29fdfc1Swdenk images is included. If not, only uncompressed and gzip 1015c29fdfc1Swdenk compressed images are supported. 1016c29fdfc1Swdenk 1017c29fdfc1Swdenk NOTE: the bzip2 algorithm requires a lot of RAM, so 1018c29fdfc1Swdenk the malloc area (as defined by CFG_MALLOC_LEN) should 1019c29fdfc1Swdenk be at least 4MB. 1020d791b1dcSwdenk 102117ea1177Swdenk- MII/PHY support: 102217ea1177Swdenk CONFIG_PHY_ADDR 102317ea1177Swdenk 102417ea1177Swdenk The address of PHY on MII bus. 102517ea1177Swdenk 102617ea1177Swdenk CONFIG_PHY_CLOCK_FREQ (ppc4xx) 102717ea1177Swdenk 102817ea1177Swdenk The clock frequency of the MII bus 102917ea1177Swdenk 103017ea1177Swdenk CONFIG_PHY_GIGE 103117ea1177Swdenk 103217ea1177Swdenk If this option is set, support for speed/duplex 103317ea1177Swdenk detection of Gigabit PHY is included. 103417ea1177Swdenk 103517ea1177Swdenk CONFIG_PHY_RESET_DELAY 103617ea1177Swdenk 103717ea1177Swdenk Some PHY like Intel LXT971A need extra delay after 103817ea1177Swdenk reset before any MII register access is possible. 103917ea1177Swdenk For such PHY, set this option to the usec delay 104017ea1177Swdenk required. (minimum 300usec for LXT971A) 104117ea1177Swdenk 104217ea1177Swdenk CONFIG_PHY_CMD_DELAY (ppc4xx) 104317ea1177Swdenk 104417ea1177Swdenk Some PHY like Intel LXT971A need extra delay after 104517ea1177Swdenk command issued before MII status register can be read 104617ea1177Swdenk 1047c609719bSwdenk- Ethernet address: 1048c609719bSwdenk CONFIG_ETHADDR 1049c609719bSwdenk CONFIG_ETH2ADDR 1050c609719bSwdenk CONFIG_ETH3ADDR 1051c609719bSwdenk 1052c609719bSwdenk Define a default value for ethernet address to use 1053c609719bSwdenk for the respective ethernet interface, in case this 1054c609719bSwdenk is not determined automatically. 1055c609719bSwdenk 1056c609719bSwdenk- IP address: 1057c609719bSwdenk CONFIG_IPADDR 1058c609719bSwdenk 1059c609719bSwdenk Define a default value for the IP address to use for 1060c609719bSwdenk the default ethernet interface, in case this is not 1061c609719bSwdenk determined through e.g. bootp. 1062c609719bSwdenk 1063c609719bSwdenk- Server IP address: 1064c609719bSwdenk CONFIG_SERVERIP 1065c609719bSwdenk 1066c609719bSwdenk Defines a default value for theIP address of a TFTP 1067c609719bSwdenk server to contact when using the "tftboot" command. 1068c609719bSwdenk 1069*53a5c424SDavid Updegraff- Multicast TFTP Mode: 1070*53a5c424SDavid Updegraff CONFIG_MCAST_TFTP 1071*53a5c424SDavid Updegraff 1072*53a5c424SDavid Updegraff Defines whether you want to support multicast TFTP as per 1073*53a5c424SDavid Updegraff rfc-2090; for example to work with atftp. Lets lots of targets 1074*53a5c424SDavid Updegraff tftp down the same boot image concurrently. Note: the ethernet 1075*53a5c424SDavid Updegraff driver in use must provide a function: mcast() to join/leave a 1076*53a5c424SDavid Updegraff multicast group. 1077*53a5c424SDavid Updegraff 1078*53a5c424SDavid Updegraff CONFIG_BOOTP_RANDOM_DELAY 1079c609719bSwdenk- BOOTP Recovery Mode: 1080c609719bSwdenk CONFIG_BOOTP_RANDOM_DELAY 1081c609719bSwdenk 1082c609719bSwdenk If you have many targets in a network that try to 1083c609719bSwdenk boot using BOOTP, you may want to avoid that all 1084c609719bSwdenk systems send out BOOTP requests at precisely the same 1085c609719bSwdenk moment (which would happen for instance at recovery 1086c609719bSwdenk from a power failure, when all systems will try to 1087c609719bSwdenk boot, thus flooding the BOOTP server. Defining 1088c609719bSwdenk CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be 1089c609719bSwdenk inserted before sending out BOOTP requests. The 10906c33c785SWolfgang Denk following delays are inserted then: 1091c609719bSwdenk 1092c609719bSwdenk 1st BOOTP request: delay 0 ... 1 sec 1093c609719bSwdenk 2nd BOOTP request: delay 0 ... 2 sec 1094c609719bSwdenk 3rd BOOTP request: delay 0 ... 4 sec 1095c609719bSwdenk 4th and following 1096c609719bSwdenk BOOTP requests: delay 0 ... 8 sec 1097c609719bSwdenk 1098fe389a82Sstroese- DHCP Advanced Options: 10991fe80d79SJon Loeliger You can fine tune the DHCP functionality by defining 11001fe80d79SJon Loeliger CONFIG_BOOTP_* symbols: 1101fe389a82Sstroese 11021fe80d79SJon Loeliger CONFIG_BOOTP_SUBNETMASK 11031fe80d79SJon Loeliger CONFIG_BOOTP_GATEWAY 11041fe80d79SJon Loeliger CONFIG_BOOTP_HOSTNAME 11051fe80d79SJon Loeliger CONFIG_BOOTP_NISDOMAIN 11061fe80d79SJon Loeliger CONFIG_BOOTP_BOOTPATH 11071fe80d79SJon Loeliger CONFIG_BOOTP_BOOTFILESIZE 11081fe80d79SJon Loeliger CONFIG_BOOTP_DNS 11091fe80d79SJon Loeliger CONFIG_BOOTP_DNS2 11101fe80d79SJon Loeliger CONFIG_BOOTP_SEND_HOSTNAME 11111fe80d79SJon Loeliger CONFIG_BOOTP_NTPSERVER 11121fe80d79SJon Loeliger CONFIG_BOOTP_TIMEOFFSET 11131fe80d79SJon Loeliger CONFIG_BOOTP_VENDOREX 1114fe389a82Sstroese 11155d110f0aSWilson Callan CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip 11165d110f0aSWilson Callan environment variable, not the BOOTP server. 11175d110f0aSWilson Callan 1118fe389a82Sstroese CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS 1119fe389a82Sstroese serverip from a DHCP server, it is possible that more 1120fe389a82Sstroese than one DNS serverip is offered to the client. 1121fe389a82Sstroese If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS 1122fe389a82Sstroese serverip will be stored in the additional environment 1123fe389a82Sstroese variable "dnsip2". The first DNS serverip is always 1124fe389a82Sstroese stored in the variable "dnsip", when CONFIG_BOOTP_DNS 11251fe80d79SJon Loeliger is defined. 1126fe389a82Sstroese 1127fe389a82Sstroese CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable 1128fe389a82Sstroese to do a dynamic update of a DNS server. To do this, they 1129fe389a82Sstroese need the hostname of the DHCP requester. 11305d110f0aSWilson Callan If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content 11311fe80d79SJon Loeliger of the "hostname" environment variable is passed as 11321fe80d79SJon Loeliger option 12 to the DHCP server. 1133fe389a82Sstroese 1134a3d991bdSwdenk - CDP Options: 1135a3d991bdSwdenk CONFIG_CDP_DEVICE_ID 1136a3d991bdSwdenk 1137a3d991bdSwdenk The device id used in CDP trigger frames. 1138a3d991bdSwdenk 1139a3d991bdSwdenk CONFIG_CDP_DEVICE_ID_PREFIX 1140a3d991bdSwdenk 1141a3d991bdSwdenk A two character string which is prefixed to the MAC address 1142a3d991bdSwdenk of the device. 1143a3d991bdSwdenk 1144a3d991bdSwdenk CONFIG_CDP_PORT_ID 1145a3d991bdSwdenk 1146a3d991bdSwdenk A printf format string which contains the ascii name of 1147a3d991bdSwdenk the port. Normally is set to "eth%d" which sets 1148a3d991bdSwdenk eth0 for the first ethernet, eth1 for the second etc. 1149a3d991bdSwdenk 1150a3d991bdSwdenk CONFIG_CDP_CAPABILITIES 1151a3d991bdSwdenk 1152a3d991bdSwdenk A 32bit integer which indicates the device capabilities; 1153a3d991bdSwdenk 0x00000010 for a normal host which does not forwards. 1154a3d991bdSwdenk 1155a3d991bdSwdenk CONFIG_CDP_VERSION 1156a3d991bdSwdenk 1157a3d991bdSwdenk An ascii string containing the version of the software. 1158a3d991bdSwdenk 1159a3d991bdSwdenk CONFIG_CDP_PLATFORM 1160a3d991bdSwdenk 1161a3d991bdSwdenk An ascii string containing the name of the platform. 1162a3d991bdSwdenk 1163a3d991bdSwdenk CONFIG_CDP_TRIGGER 1164a3d991bdSwdenk 1165a3d991bdSwdenk A 32bit integer sent on the trigger. 1166a3d991bdSwdenk 1167a3d991bdSwdenk CONFIG_CDP_POWER_CONSUMPTION 1168a3d991bdSwdenk 1169a3d991bdSwdenk A 16bit integer containing the power consumption of the 1170a3d991bdSwdenk device in .1 of milliwatts. 1171a3d991bdSwdenk 1172a3d991bdSwdenk CONFIG_CDP_APPLIANCE_VLAN_TYPE 1173a3d991bdSwdenk 1174a3d991bdSwdenk A byte containing the id of the VLAN. 1175a3d991bdSwdenk 1176c609719bSwdenk- Status LED: CONFIG_STATUS_LED 1177c609719bSwdenk 1178c609719bSwdenk Several configurations allow to display the current 1179c609719bSwdenk status using a LED. For instance, the LED will blink 1180c609719bSwdenk fast while running U-Boot code, stop blinking as 1181c609719bSwdenk soon as a reply to a BOOTP request was received, and 1182c609719bSwdenk start blinking slow once the Linux kernel is running 1183c609719bSwdenk (supported by a status LED driver in the Linux 1184c609719bSwdenk kernel). Defining CONFIG_STATUS_LED enables this 1185c609719bSwdenk feature in U-Boot. 1186c609719bSwdenk 1187c609719bSwdenk- CAN Support: CONFIG_CAN_DRIVER 1188c609719bSwdenk 1189c609719bSwdenk Defining CONFIG_CAN_DRIVER enables CAN driver support 1190c609719bSwdenk on those systems that support this (optional) 1191c609719bSwdenk feature, like the TQM8xxL modules. 1192c609719bSwdenk 1193c609719bSwdenk- I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C 1194c609719bSwdenk 1195b37c7e5eSwdenk These enable I2C serial bus commands. Defining either of 1196b37c7e5eSwdenk (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will 1197b37c7e5eSwdenk include the appropriate I2C driver for the selected cpu. 1198c609719bSwdenk 1199b37c7e5eSwdenk This will allow you to use i2c commands at the u-boot 1200602ad3b3SJon Loeliger command line (as long as you set CONFIG_CMD_I2C in 1201b37c7e5eSwdenk CONFIG_COMMANDS) and communicate with i2c based realtime 1202b37c7e5eSwdenk clock chips. See common/cmd_i2c.c for a description of the 1203c609719bSwdenk command line interface. 1204c609719bSwdenk 1205bb99ad6dSBen Warren CONFIG_I2C_CMD_TREE is a recommended option that places 1206bb99ad6dSBen Warren all I2C commands under a single 'i2c' root command. The 1207bb99ad6dSBen Warren older 'imm', 'imd', 'iprobe' etc. commands are considered 1208bb99ad6dSBen Warren deprecated and may disappear in the future. 1209bb99ad6dSBen Warren 1210bb99ad6dSBen Warren CONFIG_HARD_I2C selects a hardware I2C controller. 1211c609719bSwdenk 1212b37c7e5eSwdenk CONFIG_SOFT_I2C configures u-boot to use a software (aka 1213b37c7e5eSwdenk bit-banging) driver instead of CPM or similar hardware 1214b37c7e5eSwdenk support for I2C. 1215c609719bSwdenk 1216b37c7e5eSwdenk There are several other quantities that must also be 1217b37c7e5eSwdenk defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C. 1218c609719bSwdenk 1219b37c7e5eSwdenk In both cases you will need to define CFG_I2C_SPEED 1220b37c7e5eSwdenk to be the frequency (in Hz) at which you wish your i2c bus 1221b37c7e5eSwdenk to run and CFG_I2C_SLAVE to be the address of this node (ie 1222b37c7e5eSwdenk the cpu's i2c node address). 1223c609719bSwdenk 1224b37c7e5eSwdenk Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c) 1225b37c7e5eSwdenk sets the cpu up as a master node and so its address should 1226b37c7e5eSwdenk therefore be cleared to 0 (See, eg, MPC823e User's Manual 1227b37c7e5eSwdenk p.16-473). So, set CFG_I2C_SLAVE to 0. 1228b37c7e5eSwdenk 1229b37c7e5eSwdenk That's all that's required for CONFIG_HARD_I2C. 1230b37c7e5eSwdenk 1231b37c7e5eSwdenk If you use the software i2c interface (CONFIG_SOFT_I2C) 1232b37c7e5eSwdenk then the following macros need to be defined (examples are 1233b37c7e5eSwdenk from include/configs/lwmon.h): 1234c609719bSwdenk 1235c609719bSwdenk I2C_INIT 1236c609719bSwdenk 1237b37c7e5eSwdenk (Optional). Any commands necessary to enable the I2C 1238c609719bSwdenk controller or configure ports. 1239c609719bSwdenk 1240b37c7e5eSwdenk eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL) 1241b37c7e5eSwdenk 1242c609719bSwdenk I2C_PORT 1243c609719bSwdenk 1244c609719bSwdenk (Only for MPC8260 CPU). The I/O port to use (the code 1245c609719bSwdenk assumes both bits are on the same port). Valid values 1246c609719bSwdenk are 0..3 for ports A..D. 1247c609719bSwdenk 1248c609719bSwdenk I2C_ACTIVE 1249c609719bSwdenk 1250c609719bSwdenk The code necessary to make the I2C data line active 1251c609719bSwdenk (driven). If the data line is open collector, this 1252c609719bSwdenk define can be null. 1253c609719bSwdenk 1254b37c7e5eSwdenk eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA) 1255b37c7e5eSwdenk 1256c609719bSwdenk I2C_TRISTATE 1257c609719bSwdenk 1258c609719bSwdenk The code necessary to make the I2C data line tri-stated 1259c609719bSwdenk (inactive). If the data line is open collector, this 1260c609719bSwdenk define can be null. 1261c609719bSwdenk 1262b37c7e5eSwdenk eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA) 1263b37c7e5eSwdenk 1264c609719bSwdenk I2C_READ 1265c609719bSwdenk 1266c609719bSwdenk Code that returns TRUE if the I2C data line is high, 1267c609719bSwdenk FALSE if it is low. 1268c609719bSwdenk 1269b37c7e5eSwdenk eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0) 1270b37c7e5eSwdenk 1271c609719bSwdenk I2C_SDA(bit) 1272c609719bSwdenk 1273c609719bSwdenk If <bit> is TRUE, sets the I2C data line high. If it 1274c609719bSwdenk is FALSE, it clears it (low). 1275c609719bSwdenk 1276b37c7e5eSwdenk eg: #define I2C_SDA(bit) \ 1277b37c7e5eSwdenk if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \ 1278b37c7e5eSwdenk else immr->im_cpm.cp_pbdat &= ~PB_SDA 1279b37c7e5eSwdenk 1280c609719bSwdenk I2C_SCL(bit) 1281c609719bSwdenk 1282c609719bSwdenk If <bit> is TRUE, sets the I2C clock line high. If it 1283c609719bSwdenk is FALSE, it clears it (low). 1284c609719bSwdenk 1285b37c7e5eSwdenk eg: #define I2C_SCL(bit) \ 1286b37c7e5eSwdenk if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \ 1287b37c7e5eSwdenk else immr->im_cpm.cp_pbdat &= ~PB_SCL 1288b37c7e5eSwdenk 1289c609719bSwdenk I2C_DELAY 1290c609719bSwdenk 1291c609719bSwdenk This delay is invoked four times per clock cycle so this 1292c609719bSwdenk controls the rate of data transfer. The data rate thus 1293b37c7e5eSwdenk is 1 / (I2C_DELAY * 4). Often defined to be something 1294b37c7e5eSwdenk like: 1295b37c7e5eSwdenk 1296b37c7e5eSwdenk #define I2C_DELAY udelay(2) 1297c609719bSwdenk 129847cd00faSwdenk CFG_I2C_INIT_BOARD 129947cd00faSwdenk 130047cd00faSwdenk When a board is reset during an i2c bus transfer 130147cd00faSwdenk chips might think that the current transfer is still 130247cd00faSwdenk in progress. On some boards it is possible to access 130347cd00faSwdenk the i2c SCLK line directly, either by using the 130447cd00faSwdenk processor pin as a GPIO or by having a second pin 130547cd00faSwdenk connected to the bus. If this option is defined a 130647cd00faSwdenk custom i2c_init_board() routine in boards/xxx/board.c 130747cd00faSwdenk is run early in the boot sequence. 130847cd00faSwdenk 130917ea1177Swdenk CONFIG_I2CFAST (PPC405GP|PPC405EP only) 131017ea1177Swdenk 131117ea1177Swdenk This option enables configuration of bi_iic_fast[] flags 131217ea1177Swdenk in u-boot bd_info structure based on u-boot environment 131317ea1177Swdenk variable "i2cfast". (see also i2cfast) 131417ea1177Swdenk 1315bb99ad6dSBen Warren CONFIG_I2C_MULTI_BUS 1316bb99ad6dSBen Warren 1317bb99ad6dSBen Warren This option allows the use of multiple I2C buses, each of which 1318bb99ad6dSBen Warren must have a controller. At any point in time, only one bus is 1319bb99ad6dSBen Warren active. To switch to a different bus, use the 'i2c dev' command. 1320bb99ad6dSBen Warren Note that bus numbering is zero-based. 1321bb99ad6dSBen Warren 1322bb99ad6dSBen Warren CFG_I2C_NOPROBES 1323bb99ad6dSBen Warren 1324bb99ad6dSBen Warren This option specifies a list of I2C devices that will be skipped 1325bb99ad6dSBen Warren when the 'i2c probe' command is issued (or 'iprobe' using the legacy 1326bb99ad6dSBen Warren command). If CONFIG_I2C_MULTI_BUS is set, specify a list of bus-device 1327bb99ad6dSBen Warren pairs. Otherwise, specify a 1D array of device addresses 1328bb99ad6dSBen Warren 1329bb99ad6dSBen Warren e.g. 1330bb99ad6dSBen Warren #undef CONFIG_I2C_MULTI_BUS 1331bb99ad6dSBen Warren #define CFG_I2C_NOPROBES {0x50,0x68} 1332bb99ad6dSBen Warren 1333bb99ad6dSBen Warren will skip addresses 0x50 and 0x68 on a board with one I2C bus 1334bb99ad6dSBen Warren 1335bb99ad6dSBen Warren #define CONFIG_I2C_MULTI_BUS 1336bb99ad6dSBen Warren #define CFG_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}} 1337bb99ad6dSBen Warren 1338bb99ad6dSBen Warren will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1 1339bb99ad6dSBen Warren 1340be5e6181STimur Tabi CFG_SPD_BUS_NUM 1341be5e6181STimur Tabi 1342be5e6181STimur Tabi If defined, then this indicates the I2C bus number for DDR SPD. 1343be5e6181STimur Tabi If not defined, then U-Boot assumes that SPD is on I2C bus 0. 1344be5e6181STimur Tabi 13450dc018ecSStefan Roese CFG_RTC_BUS_NUM 13460dc018ecSStefan Roese 13470dc018ecSStefan Roese If defined, then this indicates the I2C bus number for the RTC. 13480dc018ecSStefan Roese If not defined, then U-Boot assumes that RTC is on I2C bus 0. 13490dc018ecSStefan Roese 13500dc018ecSStefan Roese CFG_DTT_BUS_NUM 13510dc018ecSStefan Roese 13520dc018ecSStefan Roese If defined, then this indicates the I2C bus number for the DTT. 13530dc018ecSStefan Roese If not defined, then U-Boot assumes that DTT is on I2C bus 0. 13540dc018ecSStefan Roese 1355be5e6181STimur Tabi CONFIG_FSL_I2C 1356be5e6181STimur Tabi 1357be5e6181STimur Tabi Define this option if you want to use Freescale's I2C driver in 1358be5e6181STimur Tabi drivers/fsl_i2c.c. 1359be5e6181STimur Tabi 1360be5e6181STimur Tabi 1361c609719bSwdenk- SPI Support: CONFIG_SPI 1362c609719bSwdenk 1363c609719bSwdenk Enables SPI driver (so far only tested with 1364c609719bSwdenk SPI EEPROM, also an instance works with Crystal A/D and 1365c609719bSwdenk D/As on the SACSng board) 1366c609719bSwdenk 1367c609719bSwdenk CONFIG_SPI_X 1368c609719bSwdenk 1369c609719bSwdenk Enables extended (16-bit) SPI EEPROM addressing. 1370c609719bSwdenk (symmetrical to CONFIG_I2C_X) 1371c609719bSwdenk 1372c609719bSwdenk CONFIG_SOFT_SPI 1373c609719bSwdenk 1374c609719bSwdenk Enables a software (bit-bang) SPI driver rather than 1375c609719bSwdenk using hardware support. This is a general purpose 1376c609719bSwdenk driver that only requires three general I/O port pins 1377c609719bSwdenk (two outputs, one input) to function. If this is 1378c609719bSwdenk defined, the board configuration must define several 1379c609719bSwdenk SPI configuration items (port pins to use, etc). For 1380c609719bSwdenk an example, see include/configs/sacsng.h. 1381c609719bSwdenk 1382c609719bSwdenk- FPGA Support: CONFIG_FPGA_COUNT 1383c609719bSwdenk 1384c609719bSwdenk Specify the number of FPGA devices to support. 1385c609719bSwdenk 1386c609719bSwdenk CONFIG_FPGA 1387c609719bSwdenk 1388c609719bSwdenk Used to specify the types of FPGA devices. For example, 1389c609719bSwdenk #define CONFIG_FPGA CFG_XILINX_VIRTEX2 1390c609719bSwdenk 1391c609719bSwdenk CFG_FPGA_PROG_FEEDBACK 1392c609719bSwdenk 1393c609719bSwdenk Enable printing of hash marks during FPGA configuration. 1394c609719bSwdenk 1395c609719bSwdenk CFG_FPGA_CHECK_BUSY 1396c609719bSwdenk 1397c609719bSwdenk Enable checks on FPGA configuration interface busy 1398c609719bSwdenk status by the configuration function. This option 1399c609719bSwdenk will require a board or device specific function to 1400c609719bSwdenk be written. 1401c609719bSwdenk 1402c609719bSwdenk CONFIG_FPGA_DELAY 1403c609719bSwdenk 1404c609719bSwdenk If defined, a function that provides delays in the FPGA 1405c609719bSwdenk configuration driver. 1406c609719bSwdenk 1407c609719bSwdenk CFG_FPGA_CHECK_CTRLC 1408c609719bSwdenk Allow Control-C to interrupt FPGA configuration 1409c609719bSwdenk 1410c609719bSwdenk CFG_FPGA_CHECK_ERROR 1411c609719bSwdenk 1412c609719bSwdenk Check for configuration errors during FPGA bitfile 1413c609719bSwdenk loading. For example, abort during Virtex II 1414c609719bSwdenk configuration if the INIT_B line goes low (which 1415c609719bSwdenk indicated a CRC error). 1416c609719bSwdenk 1417c609719bSwdenk CFG_FPGA_WAIT_INIT 1418c609719bSwdenk 1419c609719bSwdenk Maximum time to wait for the INIT_B line to deassert 1420c609719bSwdenk after PROB_B has been deasserted during a Virtex II 1421c609719bSwdenk FPGA configuration sequence. The default time is 500 1422c609719bSwdenk mS. 1423c609719bSwdenk 1424c609719bSwdenk CFG_FPGA_WAIT_BUSY 1425c609719bSwdenk 1426c609719bSwdenk Maximum time to wait for BUSY to deassert during 1427c609719bSwdenk Virtex II FPGA configuration. The default is 5 mS. 1428c609719bSwdenk 1429c609719bSwdenk CFG_FPGA_WAIT_CONFIG 1430c609719bSwdenk 1431c609719bSwdenk Time to wait after FPGA configuration. The default is 1432c609719bSwdenk 200 mS. 1433c609719bSwdenk 1434c609719bSwdenk- Configuration Management: 1435c609719bSwdenk CONFIG_IDENT_STRING 1436c609719bSwdenk 1437c609719bSwdenk If defined, this string will be added to the U-Boot 1438c609719bSwdenk version information (U_BOOT_VERSION) 1439c609719bSwdenk 1440c609719bSwdenk- Vendor Parameter Protection: 1441c609719bSwdenk 1442c609719bSwdenk U-Boot considers the values of the environment 1443c609719bSwdenk variables "serial#" (Board Serial Number) and 14447152b1d0Swdenk "ethaddr" (Ethernet Address) to be parameters that 1445c609719bSwdenk are set once by the board vendor / manufacturer, and 1446c609719bSwdenk protects these variables from casual modification by 1447c609719bSwdenk the user. Once set, these variables are read-only, 1448c609719bSwdenk and write or delete attempts are rejected. You can 1449c609719bSwdenk change this behviour: 1450c609719bSwdenk 1451c609719bSwdenk If CONFIG_ENV_OVERWRITE is #defined in your config 1452c609719bSwdenk file, the write protection for vendor parameters is 145347cd00faSwdenk completely disabled. Anybody can change or delete 1454c609719bSwdenk these parameters. 1455c609719bSwdenk 1456c609719bSwdenk Alternatively, if you #define _both_ CONFIG_ETHADDR 1457c609719bSwdenk _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default 1458c609719bSwdenk ethernet address is installed in the environment, 1459c609719bSwdenk which can be changed exactly ONCE by the user. [The 1460c609719bSwdenk serial# is unaffected by this, i. e. it remains 1461c609719bSwdenk read-only.] 1462c609719bSwdenk 1463c609719bSwdenk- Protected RAM: 1464c609719bSwdenk CONFIG_PRAM 1465c609719bSwdenk 1466c609719bSwdenk Define this variable to enable the reservation of 1467c609719bSwdenk "protected RAM", i. e. RAM which is not overwritten 1468c609719bSwdenk by U-Boot. Define CONFIG_PRAM to hold the number of 1469c609719bSwdenk kB you want to reserve for pRAM. You can overwrite 1470c609719bSwdenk this default value by defining an environment 1471c609719bSwdenk variable "pram" to the number of kB you want to 1472c609719bSwdenk reserve. Note that the board info structure will 1473c609719bSwdenk still show the full amount of RAM. If pRAM is 1474c609719bSwdenk reserved, a new environment variable "mem" will 1475c609719bSwdenk automatically be defined to hold the amount of 1476c609719bSwdenk remaining RAM in a form that can be passed as boot 1477c609719bSwdenk argument to Linux, for instance like that: 1478c609719bSwdenk 1479fe126d8bSWolfgang Denk setenv bootargs ... mem=\${mem} 1480c609719bSwdenk saveenv 1481c609719bSwdenk 1482c609719bSwdenk This way you can tell Linux not to use this memory, 1483c609719bSwdenk either, which results in a memory region that will 1484c609719bSwdenk not be affected by reboots. 1485c609719bSwdenk 1486c609719bSwdenk *WARNING* If your board configuration uses automatic 1487c609719bSwdenk detection of the RAM size, you must make sure that 1488c609719bSwdenk this memory test is non-destructive. So far, the 1489c609719bSwdenk following board configurations are known to be 1490c609719bSwdenk "pRAM-clean": 1491c609719bSwdenk 1492c609719bSwdenk ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL, 1493c609719bSwdenk HERMES, IP860, RPXlite, LWMON, LANTEC, 1494c609719bSwdenk PCU_E, FLAGADM, TQM8260 1495c609719bSwdenk 1496c609719bSwdenk- Error Recovery: 1497c609719bSwdenk CONFIG_PANIC_HANG 1498c609719bSwdenk 1499c609719bSwdenk Define this variable to stop the system in case of a 1500c609719bSwdenk fatal error, so that you have to reset it manually. 1501c609719bSwdenk This is probably NOT a good idea for an embedded 1502c609719bSwdenk system where you want to system to reboot 1503c609719bSwdenk automatically as fast as possible, but it may be 1504c609719bSwdenk useful during development since you can try to debug 1505c609719bSwdenk the conditions that lead to the situation. 1506c609719bSwdenk 1507c609719bSwdenk CONFIG_NET_RETRY_COUNT 1508c609719bSwdenk 1509c609719bSwdenk This variable defines the number of retries for 1510c609719bSwdenk network operations like ARP, RARP, TFTP, or BOOTP 1511c609719bSwdenk before giving up the operation. If not defined, a 1512c609719bSwdenk default value of 5 is used. 1513c609719bSwdenk 1514c609719bSwdenk- Command Interpreter: 15158078f1a5SWolfgang Denk CONFIG_AUTO_COMPLETE 151604a85b3bSwdenk 151704a85b3bSwdenk Enable auto completion of commands using TAB. 151804a85b3bSwdenk 15198078f1a5SWolfgang Denk Note that this feature has NOT been implemented yet 15208078f1a5SWolfgang Denk for the "hush" shell. 15218078f1a5SWolfgang Denk 15228078f1a5SWolfgang Denk 1523c609719bSwdenk CFG_HUSH_PARSER 1524c609719bSwdenk 1525c609719bSwdenk Define this variable to enable the "hush" shell (from 1526c609719bSwdenk Busybox) as command line interpreter, thus enabling 1527c609719bSwdenk powerful command line syntax like 1528c609719bSwdenk if...then...else...fi conditionals or `&&' and '||' 1529c609719bSwdenk constructs ("shell scripts"). 1530c609719bSwdenk 1531c609719bSwdenk If undefined, you get the old, much simpler behaviour 1532c609719bSwdenk with a somewhat smaller memory footprint. 1533c609719bSwdenk 1534c609719bSwdenk 1535c609719bSwdenk CFG_PROMPT_HUSH_PS2 1536c609719bSwdenk 1537c609719bSwdenk This defines the secondary prompt string, which is 1538c609719bSwdenk printed when the command interpreter needs more input 1539c609719bSwdenk to complete a command. Usually "> ". 1540c609719bSwdenk 1541c609719bSwdenk Note: 1542c609719bSwdenk 1543c609719bSwdenk In the current implementation, the local variables 1544c609719bSwdenk space and global environment variables space are 1545c609719bSwdenk separated. Local variables are those you define by 15463b57fe0aSwdenk simply typing `name=value'. To access a local 1547c609719bSwdenk variable later on, you have write `$name' or 15483b57fe0aSwdenk `${name}'; to execute the contents of a variable 15493b57fe0aSwdenk directly type `$name' at the command prompt. 1550c609719bSwdenk 1551c609719bSwdenk Global environment variables are those you use 1552c609719bSwdenk setenv/printenv to work with. To run a command stored 1553c609719bSwdenk in such a variable, you need to use the run command, 1554c609719bSwdenk and you must not use the '$' sign to access them. 1555c609719bSwdenk 1556c609719bSwdenk To store commands and special characters in a 1557c609719bSwdenk variable, please use double quotation marks 1558c609719bSwdenk surrounding the whole text of the variable, instead 1559c609719bSwdenk of the backslashes before semicolons and special 1560c609719bSwdenk symbols. 1561c609719bSwdenk 1562aa0c71acSWolfgang Denk- Commandline Editing and History: 1563aa0c71acSWolfgang Denk CONFIG_CMDLINE_EDITING 1564aa0c71acSWolfgang Denk 1565aa0c71acSWolfgang Denk Enable editiong and History functions for interactive 1566aa0c71acSWolfgang Denk commandline input operations 1567aa0c71acSWolfgang Denk 1568a8c7c708Swdenk- Default Environment: 1569c609719bSwdenk CONFIG_EXTRA_ENV_SETTINGS 1570c609719bSwdenk 1571c609719bSwdenk Define this to contain any number of null terminated 1572c609719bSwdenk strings (variable = value pairs) that will be part of 15737152b1d0Swdenk the default environment compiled into the boot image. 15742262cfeeSwdenk 1575c609719bSwdenk For example, place something like this in your 1576c609719bSwdenk board's config file: 1577c609719bSwdenk 1578c609719bSwdenk #define CONFIG_EXTRA_ENV_SETTINGS \ 1579c609719bSwdenk "myvar1=value1\0" \ 1580c609719bSwdenk "myvar2=value2\0" 1581c609719bSwdenk 1582c609719bSwdenk Warning: This method is based on knowledge about the 1583c609719bSwdenk internal format how the environment is stored by the 15842262cfeeSwdenk U-Boot code. This is NOT an official, exported 1585c609719bSwdenk interface! Although it is unlikely that this format 15867152b1d0Swdenk will change soon, there is no guarantee either. 1587c609719bSwdenk You better know what you are doing here. 1588c609719bSwdenk 1589c609719bSwdenk Note: overly (ab)use of the default environment is 1590c609719bSwdenk discouraged. Make sure to check other ways to preset 1591c609719bSwdenk the environment like the autoscript function or the 1592c609719bSwdenk boot command first. 1593c609719bSwdenk 1594a8c7c708Swdenk- DataFlash Support: 15952abbe075Swdenk CONFIG_HAS_DATAFLASH 15962abbe075Swdenk 15972abbe075Swdenk Defining this option enables DataFlash features and 15982abbe075Swdenk allows to read/write in Dataflash via the standard 15992abbe075Swdenk commands cp, md... 16002abbe075Swdenk 16013f85ce27Swdenk- SystemACE Support: 16023f85ce27Swdenk CONFIG_SYSTEMACE 16033f85ce27Swdenk 16043f85ce27Swdenk Adding this option adds support for Xilinx SystemACE 16053f85ce27Swdenk chips attached via some sort of local bus. The address 16063f85ce27Swdenk of the chip must alsh be defined in the 16073f85ce27Swdenk CFG_SYSTEMACE_BASE macro. For example: 16083f85ce27Swdenk 16093f85ce27Swdenk #define CONFIG_SYSTEMACE 16103f85ce27Swdenk #define CFG_SYSTEMACE_BASE 0xf0000000 16113f85ce27Swdenk 16123f85ce27Swdenk When SystemACE support is added, the "ace" device type 16133f85ce27Swdenk becomes available to the fat commands, i.e. fatls. 16143f85ce27Swdenk 1615ecb0ccd9SWolfgang Denk- TFTP Fixed UDP Port: 1616ecb0ccd9SWolfgang Denk CONFIG_TFTP_PORT 1617ecb0ccd9SWolfgang Denk 161828cb9375SWolfgang Denk If this is defined, the environment variable tftpsrcp 1619ecb0ccd9SWolfgang Denk is used to supply the TFTP UDP source port value. 162028cb9375SWolfgang Denk If tftpsrcp isn't defined, the normal pseudo-random port 1621ecb0ccd9SWolfgang Denk number generator is used. 1622ecb0ccd9SWolfgang Denk 162328cb9375SWolfgang Denk Also, the environment variable tftpdstp is used to supply 162428cb9375SWolfgang Denk the TFTP UDP destination port value. If tftpdstp isn't 162528cb9375SWolfgang Denk defined, the normal port 69 is used. 162628cb9375SWolfgang Denk 162728cb9375SWolfgang Denk The purpose for tftpsrcp is to allow a TFTP server to 1628ecb0ccd9SWolfgang Denk blindly start the TFTP transfer using the pre-configured 1629ecb0ccd9SWolfgang Denk target IP address and UDP port. This has the effect of 1630ecb0ccd9SWolfgang Denk "punching through" the (Windows XP) firewall, allowing 1631ecb0ccd9SWolfgang Denk the remainder of the TFTP transfer to proceed normally. 1632ecb0ccd9SWolfgang Denk A better solution is to properly configure the firewall, 1633ecb0ccd9SWolfgang Denk but sometimes that is not allowed. 1634ecb0ccd9SWolfgang Denk 1635a8c7c708Swdenk- Show boot progress: 1636c609719bSwdenk CONFIG_SHOW_BOOT_PROGRESS 1637c609719bSwdenk 1638c609719bSwdenk Defining this option allows to add some board- 1639c609719bSwdenk specific code (calling a user-provided function 1640c609719bSwdenk "show_boot_progress(int)") that enables you to show 1641c609719bSwdenk the system's boot progress on some display (for 1642c609719bSwdenk example, some LED's) on your board. At the moment, 1643c609719bSwdenk the following checkpoints are implemented: 1644c609719bSwdenk 1645c609719bSwdenk Arg Where When 1646c609719bSwdenk 1 common/cmd_bootm.c before attempting to boot an image 1647c609719bSwdenk -1 common/cmd_bootm.c Image header has bad magic number 1648c609719bSwdenk 2 common/cmd_bootm.c Image header has correct magic number 1649c609719bSwdenk -2 common/cmd_bootm.c Image header has bad checksum 1650c609719bSwdenk 3 common/cmd_bootm.c Image header has correct checksum 1651c609719bSwdenk -3 common/cmd_bootm.c Image data has bad checksum 1652c609719bSwdenk 4 common/cmd_bootm.c Image data has correct checksum 1653c609719bSwdenk -4 common/cmd_bootm.c Image is for unsupported architecture 1654c609719bSwdenk 5 common/cmd_bootm.c Architecture check OK 1655c609719bSwdenk -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone) 1656c609719bSwdenk 6 common/cmd_bootm.c Image Type check OK 1657c609719bSwdenk -6 common/cmd_bootm.c gunzip uncompression error 1658c609719bSwdenk -7 common/cmd_bootm.c Unimplemented compression type 1659c609719bSwdenk 7 common/cmd_bootm.c Uncompression OK 1660c609719bSwdenk -8 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone) 1661c609719bSwdenk 8 common/cmd_bootm.c Image Type check OK 1662c609719bSwdenk -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX) 1663c609719bSwdenk 9 common/cmd_bootm.c Start initial ramdisk verification 1664c609719bSwdenk -10 common/cmd_bootm.c Ramdisk header has bad magic number 1665c609719bSwdenk -11 common/cmd_bootm.c Ramdisk header has bad checksum 1666c609719bSwdenk 10 common/cmd_bootm.c Ramdisk header is OK 1667c609719bSwdenk -12 common/cmd_bootm.c Ramdisk data has bad checksum 1668c609719bSwdenk 11 common/cmd_bootm.c Ramdisk data has correct checksum 1669c609719bSwdenk 12 common/cmd_bootm.c Ramdisk verification complete, start loading 1670c609719bSwdenk -13 common/cmd_bootm.c Wrong Image Type (not PPC Linux Ramdisk) 1671c609719bSwdenk 13 common/cmd_bootm.c Start multifile image verification 1672c609719bSwdenk 14 common/cmd_bootm.c No initial ramdisk, no multifile, continue. 1673c609719bSwdenk 15 common/cmd_bootm.c All preparation done, transferring control to OS 1674c609719bSwdenk 167563e73c9aSwdenk -30 lib_ppc/board.c Fatal error, hang the system 167663e73c9aSwdenk -31 post/post.c POST test failed, detected by post_output_backlog() 167763e73c9aSwdenk -32 post/post.c POST test failed, detected by post_run_single() 167863e73c9aSwdenk 1679566a494fSHeiko Schocher 34 common/cmd_doc.c before loading a Image from a DOC device 1680566a494fSHeiko Schocher -35 common/cmd_doc.c Bad usage of "doc" command 1681566a494fSHeiko Schocher 35 common/cmd_doc.c correct usage of "doc" command 1682566a494fSHeiko Schocher -36 common/cmd_doc.c No boot device 1683566a494fSHeiko Schocher 36 common/cmd_doc.c correct boot device 1684566a494fSHeiko Schocher -37 common/cmd_doc.c Unknown Chip ID on boot device 1685566a494fSHeiko Schocher 37 common/cmd_doc.c correct chip ID found, device available 1686566a494fSHeiko Schocher -38 common/cmd_doc.c Read Error on boot device 1687566a494fSHeiko Schocher 38 common/cmd_doc.c reading Image header from DOC device OK 1688566a494fSHeiko Schocher -39 common/cmd_doc.c Image header has bad magic number 1689566a494fSHeiko Schocher 39 common/cmd_doc.c Image header has correct magic number 1690566a494fSHeiko Schocher -40 common/cmd_doc.c Error reading Image from DOC device 1691566a494fSHeiko Schocher 40 common/cmd_doc.c Image header has correct magic number 1692566a494fSHeiko Schocher 41 common/cmd_ide.c before loading a Image from a IDE device 1693566a494fSHeiko Schocher -42 common/cmd_ide.c Bad usage of "ide" command 1694566a494fSHeiko Schocher 42 common/cmd_ide.c correct usage of "ide" command 1695566a494fSHeiko Schocher -43 common/cmd_ide.c No boot device 1696566a494fSHeiko Schocher 43 common/cmd_ide.c boot device found 1697566a494fSHeiko Schocher -44 common/cmd_ide.c Device not available 1698566a494fSHeiko Schocher 44 common/cmd_ide.c Device available 1699566a494fSHeiko Schocher -45 common/cmd_ide.c wrong partition selected 1700566a494fSHeiko Schocher 45 common/cmd_ide.c partition selected 1701566a494fSHeiko Schocher -46 common/cmd_ide.c Unknown partition table 1702566a494fSHeiko Schocher 46 common/cmd_ide.c valid partition table found 1703566a494fSHeiko Schocher -47 common/cmd_ide.c Invalid partition type 1704566a494fSHeiko Schocher 47 common/cmd_ide.c correct partition type 1705566a494fSHeiko Schocher -48 common/cmd_ide.c Error reading Image Header on boot device 1706566a494fSHeiko Schocher 48 common/cmd_ide.c reading Image Header from IDE device OK 1707566a494fSHeiko Schocher -49 common/cmd_ide.c Image header has bad magic number 1708566a494fSHeiko Schocher 49 common/cmd_ide.c Image header has correct magic number 1709566a494fSHeiko Schocher -50 common/cmd_ide.c Image header has bad checksum 1710566a494fSHeiko Schocher 50 common/cmd_ide.c Image header has correct checksum 1711566a494fSHeiko Schocher -51 common/cmd_ide.c Error reading Image from IDE device 1712566a494fSHeiko Schocher 51 common/cmd_ide.c reading Image from IDE device OK 1713566a494fSHeiko Schocher 52 common/cmd_nand.c before loading a Image from a NAND device 1714566a494fSHeiko Schocher -53 common/cmd_nand.c Bad usage of "nand" command 1715566a494fSHeiko Schocher 53 common/cmd_nand.c correct usage of "nand" command 1716566a494fSHeiko Schocher -54 common/cmd_nand.c No boot device 1717566a494fSHeiko Schocher 54 common/cmd_nand.c boot device found 1718566a494fSHeiko Schocher -55 common/cmd_nand.c Unknown Chip ID on boot device 1719566a494fSHeiko Schocher 55 common/cmd_nand.c correct chip ID found, device available 1720566a494fSHeiko Schocher -56 common/cmd_nand.c Error reading Image Header on boot device 1721566a494fSHeiko Schocher 56 common/cmd_nand.c reading Image Header from NAND device OK 1722566a494fSHeiko Schocher -57 common/cmd_nand.c Image header has bad magic number 1723566a494fSHeiko Schocher 57 common/cmd_nand.c Image header has correct magic number 1724566a494fSHeiko Schocher -58 common/cmd_nand.c Error reading Image from NAND device 1725566a494fSHeiko Schocher 58 common/cmd_nand.c reading Image from NAND device OK 1726c609719bSwdenk 1727566a494fSHeiko Schocher -60 common/env_common.c Environment has a bad CRC, using default 1728c609719bSwdenk 1729566a494fSHeiko Schocher 64 net/eth.c starting with Ethernetconfiguration. 1730566a494fSHeiko Schocher -64 net/eth.c no Ethernet found. 1731566a494fSHeiko Schocher 65 net/eth.c Ethernet found. 1732206c60cbSwdenk 1733566a494fSHeiko Schocher -80 common/cmd_net.c usage wrong 1734566a494fSHeiko Schocher 80 common/cmd_net.c before calling NetLoop() 1735566a494fSHeiko Schocher -81 common/cmd_net.c some error in NetLoop() occured 1736566a494fSHeiko Schocher 81 common/cmd_net.c NetLoop() back without error 1737566a494fSHeiko Schocher -82 common/cmd_net.c size == 0 (File with size 0 loaded) 1738566a494fSHeiko Schocher 82 common/cmd_net.c trying automatic boot 1739566a494fSHeiko Schocher 83 common/cmd_net.c running autoscript 1740566a494fSHeiko Schocher -83 common/cmd_net.c some error in automatic boot or autoscript 1741566a494fSHeiko Schocher 84 common/cmd_net.c end without errors 1742c609719bSwdenk 1743c609719bSwdenkModem Support: 1744c609719bSwdenk-------------- 1745c609719bSwdenk 174685ec0bccSwdenk[so far only for SMDK2400 and TRAB boards] 1747c609719bSwdenk 1748c609719bSwdenk- Modem support endable: 1749c609719bSwdenk CONFIG_MODEM_SUPPORT 1750c609719bSwdenk 1751c609719bSwdenk- RTS/CTS Flow control enable: 1752c609719bSwdenk CONFIG_HWFLOW 1753c609719bSwdenk 1754c609719bSwdenk- Modem debug support: 1755c609719bSwdenk CONFIG_MODEM_SUPPORT_DEBUG 1756c609719bSwdenk 1757c609719bSwdenk Enables debugging stuff (char screen[1024], dbg()) 1758c609719bSwdenk for modem support. Useful only with BDI2000. 1759c609719bSwdenk 1760a8c7c708Swdenk- Interrupt support (PPC): 1761a8c7c708Swdenk 1762a8c7c708Swdenk There are common interrupt_init() and timer_interrupt() 1763a8c7c708Swdenk for all PPC archs. interrupt_init() calls interrupt_init_cpu() 1764a8c7c708Swdenk for cpu specific initialization. interrupt_init_cpu() 1765a8c7c708Swdenk should set decrementer_count to appropriate value. If 1766a8c7c708Swdenk cpu resets decrementer automatically after interrupt 1767a8c7c708Swdenk (ppc4xx) it should set decrementer_count to zero. 1768a8c7c708Swdenk timer_interrupt() calls timer_interrupt_cpu() for cpu 1769a8c7c708Swdenk specific handling. If board has watchdog / status_led 1770a8c7c708Swdenk / other_activity_monitor it works automatically from 1771a8c7c708Swdenk general timer_interrupt(). 1772a8c7c708Swdenk 1773c609719bSwdenk- General: 1774c609719bSwdenk 1775c609719bSwdenk In the target system modem support is enabled when a 1776c609719bSwdenk specific key (key combination) is pressed during 1777c609719bSwdenk power-on. Otherwise U-Boot will boot normally 1778c609719bSwdenk (autoboot). The key_pressed() fuction is called from 1779c609719bSwdenk board_init(). Currently key_pressed() is a dummy 1780c609719bSwdenk function, returning 1 and thus enabling modem 1781c609719bSwdenk initialization. 1782c609719bSwdenk 1783c609719bSwdenk If there are no modem init strings in the 1784c609719bSwdenk environment, U-Boot proceed to autoboot; the 1785c609719bSwdenk previous output (banner, info printfs) will be 1786c609719bSwdenk supressed, though. 1787c609719bSwdenk 1788c609719bSwdenk See also: doc/README.Modem 1789c609719bSwdenk 1790c609719bSwdenk 1791c609719bSwdenkConfiguration Settings: 1792c609719bSwdenk----------------------- 1793c609719bSwdenk 1794c609719bSwdenk- CFG_LONGHELP: Defined when you want long help messages included; 1795c609719bSwdenk undefine this when you're short of memory. 1796c609719bSwdenk 1797c609719bSwdenk- CFG_PROMPT: This is what U-Boot prints on the console to 1798c609719bSwdenk prompt for user input. 1799c609719bSwdenk 1800c609719bSwdenk- CFG_CBSIZE: Buffer size for input from the Console 1801c609719bSwdenk 1802c609719bSwdenk- CFG_PBSIZE: Buffer size for Console output 1803c609719bSwdenk 1804c609719bSwdenk- CFG_MAXARGS: max. Number of arguments accepted for monitor commands 1805c609719bSwdenk 1806c609719bSwdenk- CFG_BARGSIZE: Buffer size for Boot Arguments which are passed to 1807c609719bSwdenk the application (usually a Linux kernel) when it is 1808c609719bSwdenk booted 1809c609719bSwdenk 1810c609719bSwdenk- CFG_BAUDRATE_TABLE: 1811c609719bSwdenk List of legal baudrate settings for this board. 1812c609719bSwdenk 1813c609719bSwdenk- CFG_CONSOLE_INFO_QUIET 1814c609719bSwdenk Suppress display of console information at boot. 1815c609719bSwdenk 1816c609719bSwdenk- CFG_CONSOLE_IS_IN_ENV 1817c609719bSwdenk If the board specific function 1818c609719bSwdenk extern int overwrite_console (void); 1819c609719bSwdenk returns 1, the stdin, stderr and stdout are switched to the 1820c609719bSwdenk serial port, else the settings in the environment are used. 1821c609719bSwdenk 1822c609719bSwdenk- CFG_CONSOLE_OVERWRITE_ROUTINE 1823c609719bSwdenk Enable the call to overwrite_console(). 1824c609719bSwdenk 1825c609719bSwdenk- CFG_CONSOLE_ENV_OVERWRITE 1826c609719bSwdenk Enable overwrite of previous console environment settings. 1827c609719bSwdenk 1828c609719bSwdenk- CFG_MEMTEST_START, CFG_MEMTEST_END: 1829c609719bSwdenk Begin and End addresses of the area used by the 1830c609719bSwdenk simple memory test. 1831c609719bSwdenk 1832c609719bSwdenk- CFG_ALT_MEMTEST: 1833c609719bSwdenk Enable an alternate, more extensive memory test. 1834c609719bSwdenk 18355f535fe1Swdenk- CFG_MEMTEST_SCRATCH: 18365f535fe1Swdenk Scratch address used by the alternate memory test 18375f535fe1Swdenk You only need to set this if address zero isn't writeable 18385f535fe1Swdenk 1839c609719bSwdenk- CFG_TFTP_LOADADDR: 1840c609719bSwdenk Default load address for network file downloads 1841c609719bSwdenk 1842c609719bSwdenk- CFG_LOADS_BAUD_CHANGE: 1843c609719bSwdenk Enable temporary baudrate change while serial download 1844c609719bSwdenk 1845c609719bSwdenk- CFG_SDRAM_BASE: 1846c609719bSwdenk Physical start address of SDRAM. _Must_ be 0 here. 1847c609719bSwdenk 1848c609719bSwdenk- CFG_MBIO_BASE: 1849c609719bSwdenk Physical start address of Motherboard I/O (if using a 1850c609719bSwdenk Cogent motherboard) 1851c609719bSwdenk 1852c609719bSwdenk- CFG_FLASH_BASE: 1853c609719bSwdenk Physical start address of Flash memory. 1854c609719bSwdenk 1855c609719bSwdenk- CFG_MONITOR_BASE: 1856c609719bSwdenk Physical start address of boot monitor code (set by 1857c609719bSwdenk make config files to be same as the text base address 1858c609719bSwdenk (TEXT_BASE) used when linking) - same as 1859c609719bSwdenk CFG_FLASH_BASE when booting from flash. 1860c609719bSwdenk 1861c609719bSwdenk- CFG_MONITOR_LEN: 18623b57fe0aSwdenk Size of memory reserved for monitor code, used to 18633b57fe0aSwdenk determine _at_compile_time_ (!) if the environment is 18643b57fe0aSwdenk embedded within the U-Boot image, or in a separate 18653b57fe0aSwdenk flash sector. 1866c609719bSwdenk 1867c609719bSwdenk- CFG_MALLOC_LEN: 1868c609719bSwdenk Size of DRAM reserved for malloc() use. 1869c609719bSwdenk 187015940c9aSStefan Roese- CFG_BOOTM_LEN: 187115940c9aSStefan Roese Normally compressed uImages are limited to an 187215940c9aSStefan Roese uncompressed size of 8 MBytes. If this is not enough, 187315940c9aSStefan Roese you can define CFG_BOOTM_LEN in your board config file 187415940c9aSStefan Roese to adjust this setting to your needs. 1875c609719bSwdenk 1876c609719bSwdenk- CFG_BOOTMAPSZ: 1877c609719bSwdenk Maximum size of memory mapped by the startup code of 1878c609719bSwdenk the Linux kernel; all data that must be processed by 1879c609719bSwdenk the Linux kernel (bd_info, boot arguments, eventually 1880c609719bSwdenk initrd image) must be put below this limit. 1881c609719bSwdenk 1882c609719bSwdenk- CFG_MAX_FLASH_BANKS: 1883c609719bSwdenk Max number of Flash memory banks 1884c609719bSwdenk 1885c609719bSwdenk- CFG_MAX_FLASH_SECT: 1886c609719bSwdenk Max number of sectors on a Flash chip 1887c609719bSwdenk 1888c609719bSwdenk- CFG_FLASH_ERASE_TOUT: 1889c609719bSwdenk Timeout for Flash erase operations (in ms) 1890c609719bSwdenk 1891c609719bSwdenk- CFG_FLASH_WRITE_TOUT: 1892c609719bSwdenk Timeout for Flash write operations (in ms) 1893c609719bSwdenk 18948564acf9Swdenk- CFG_FLASH_LOCK_TOUT 18958564acf9Swdenk Timeout for Flash set sector lock bit operation (in ms) 18968564acf9Swdenk 18978564acf9Swdenk- CFG_FLASH_UNLOCK_TOUT 18988564acf9Swdenk Timeout for Flash clear lock bits operation (in ms) 18998564acf9Swdenk 19008564acf9Swdenk- CFG_FLASH_PROTECTION 19018564acf9Swdenk If defined, hardware flash sectors protection is used 19028564acf9Swdenk instead of U-Boot software protection. 19038564acf9Swdenk 1904c609719bSwdenk- CFG_DIRECT_FLASH_TFTP: 1905c609719bSwdenk 1906c609719bSwdenk Enable TFTP transfers directly to flash memory; 1907c609719bSwdenk without this option such a download has to be 1908c609719bSwdenk performed in two steps: (1) download to RAM, and (2) 1909c609719bSwdenk copy from RAM to flash. 1910c609719bSwdenk 1911c609719bSwdenk The two-step approach is usually more reliable, since 1912c609719bSwdenk you can check if the download worked before you erase 1913c609719bSwdenk the flash, but in some situations (when sytem RAM is 1914c609719bSwdenk too limited to allow for a tempory copy of the 1915c609719bSwdenk downloaded image) this option may be very useful. 1916c609719bSwdenk 1917c609719bSwdenk- CFG_FLASH_CFI: 1918c609719bSwdenk Define if the flash driver uses extra elements in the 19195653fc33Swdenk common flash structure for storing flash geometry. 19205653fc33Swdenk 19215653fc33Swdenk- CFG_FLASH_CFI_DRIVER 19225653fc33Swdenk This option also enables the building of the cfi_flash driver 19235653fc33Swdenk in the drivers directory 192453cf9435Sstroese 19255568e613SStefan Roese- CFG_FLASH_QUIET_TEST 19265568e613SStefan Roese If this option is defined, the common CFI flash doesn't 19275568e613SStefan Roese print it's warning upon not recognized FLASH banks. This 19285568e613SStefan Roese is useful, if some of the configured banks are only 19295568e613SStefan Roese optionally available. 19305568e613SStefan Roese 193153cf9435Sstroese- CFG_RX_ETH_BUFFER: 193253cf9435Sstroese Defines the number of ethernet receive buffers. On some 193353cf9435Sstroese ethernet controllers it is recommended to set this value 193453cf9435Sstroese to 8 or even higher (EEPRO100 or 405 EMAC), since all 193553cf9435Sstroese buffers can be full shortly after enabling the interface 193653cf9435Sstroese on high ethernet traffic. 193753cf9435Sstroese Defaults to 4 if not defined. 1938c609719bSwdenk 1939c609719bSwdenkThe following definitions that deal with the placement and management 1940c609719bSwdenkof environment data (variable area); in general, we support the 1941c609719bSwdenkfollowing configurations: 1942c609719bSwdenk 1943c609719bSwdenk- CFG_ENV_IS_IN_FLASH: 1944c609719bSwdenk 1945c609719bSwdenk Define this if the environment is in flash memory. 1946c609719bSwdenk 1947c609719bSwdenk a) The environment occupies one whole flash sector, which is 1948c609719bSwdenk "embedded" in the text segment with the U-Boot code. This 1949c609719bSwdenk happens usually with "bottom boot sector" or "top boot 1950c609719bSwdenk sector" type flash chips, which have several smaller 1951c609719bSwdenk sectors at the start or the end. For instance, such a 1952c609719bSwdenk layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In 1953c609719bSwdenk such a case you would place the environment in one of the 1954c609719bSwdenk 4 kB sectors - with U-Boot code before and after it. With 1955c609719bSwdenk "top boot sector" type flash chips, you would put the 1956c609719bSwdenk environment in one of the last sectors, leaving a gap 1957c609719bSwdenk between U-Boot and the environment. 1958c609719bSwdenk 1959c609719bSwdenk - CFG_ENV_OFFSET: 1960c609719bSwdenk 1961c609719bSwdenk Offset of environment data (variable area) to the 1962c609719bSwdenk beginning of flash memory; for instance, with bottom boot 1963c609719bSwdenk type flash chips the second sector can be used: the offset 1964c609719bSwdenk for this sector is given here. 1965c609719bSwdenk 1966c609719bSwdenk CFG_ENV_OFFSET is used relative to CFG_FLASH_BASE. 1967c609719bSwdenk 1968c609719bSwdenk - CFG_ENV_ADDR: 1969c609719bSwdenk 1970c609719bSwdenk This is just another way to specify the start address of 1971c609719bSwdenk the flash sector containing the environment (instead of 1972c609719bSwdenk CFG_ENV_OFFSET). 1973c609719bSwdenk 1974c609719bSwdenk - CFG_ENV_SECT_SIZE: 1975c609719bSwdenk 1976c609719bSwdenk Size of the sector containing the environment. 1977c609719bSwdenk 1978c609719bSwdenk 1979c609719bSwdenk b) Sometimes flash chips have few, equal sized, BIG sectors. 1980c609719bSwdenk In such a case you don't want to spend a whole sector for 1981c609719bSwdenk the environment. 1982c609719bSwdenk 1983c609719bSwdenk - CFG_ENV_SIZE: 1984c609719bSwdenk 1985c609719bSwdenk If you use this in combination with CFG_ENV_IS_IN_FLASH 1986c609719bSwdenk and CFG_ENV_SECT_SIZE, you can specify to use only a part 1987c609719bSwdenk of this flash sector for the environment. This saves 1988c609719bSwdenk memory for the RAM copy of the environment. 1989c609719bSwdenk 1990c609719bSwdenk It may also save flash memory if you decide to use this 1991c609719bSwdenk when your environment is "embedded" within U-Boot code, 1992c609719bSwdenk since then the remainder of the flash sector could be used 1993c609719bSwdenk for U-Boot code. It should be pointed out that this is 1994c609719bSwdenk STRONGLY DISCOURAGED from a robustness point of view: 1995c609719bSwdenk updating the environment in flash makes it always 1996c609719bSwdenk necessary to erase the WHOLE sector. If something goes 1997c609719bSwdenk wrong before the contents has been restored from a copy in 1998c609719bSwdenk RAM, your target system will be dead. 1999c609719bSwdenk 2000c609719bSwdenk - CFG_ENV_ADDR_REDUND 2001c609719bSwdenk CFG_ENV_SIZE_REDUND 2002c609719bSwdenk 2003c609719bSwdenk These settings describe a second storage area used to hold 2004c609719bSwdenk a redundand copy of the environment data, so that there is 20053e38691eSwdenk a valid backup copy in case there is a power failure during 2006c609719bSwdenk a "saveenv" operation. 2007c609719bSwdenk 2008c609719bSwdenkBE CAREFUL! Any changes to the flash layout, and some changes to the 2009c609719bSwdenksource code will make it necessary to adapt <board>/u-boot.lds* 2010c609719bSwdenkaccordingly! 2011c609719bSwdenk 2012c609719bSwdenk 2013c609719bSwdenk- CFG_ENV_IS_IN_NVRAM: 2014c609719bSwdenk 2015c609719bSwdenk Define this if you have some non-volatile memory device 2016c609719bSwdenk (NVRAM, battery buffered SRAM) which you want to use for the 2017c609719bSwdenk environment. 2018c609719bSwdenk 2019c609719bSwdenk - CFG_ENV_ADDR: 2020c609719bSwdenk - CFG_ENV_SIZE: 2021c609719bSwdenk 2022c609719bSwdenk These two #defines are used to determin the memory area you 2023c609719bSwdenk want to use for environment. It is assumed that this memory 2024c609719bSwdenk can just be read and written to, without any special 2025c609719bSwdenk provision. 2026c609719bSwdenk 2027c609719bSwdenkBE CAREFUL! The first access to the environment happens quite early 2028c609719bSwdenkin U-Boot initalization (when we try to get the setting of for the 2029c609719bSwdenkconsole baudrate). You *MUST* have mappend your NVRAM area then, or 2030c609719bSwdenkU-Boot will hang. 2031c609719bSwdenk 2032c609719bSwdenkPlease note that even with NVRAM we still use a copy of the 2033c609719bSwdenkenvironment in RAM: we could work on NVRAM directly, but we want to 2034c609719bSwdenkkeep settings there always unmodified except somebody uses "saveenv" 2035c609719bSwdenkto save the current settings. 2036c609719bSwdenk 2037c609719bSwdenk 2038c609719bSwdenk- CFG_ENV_IS_IN_EEPROM: 2039c609719bSwdenk 2040c609719bSwdenk Use this if you have an EEPROM or similar serial access 2041c609719bSwdenk device and a driver for it. 2042c609719bSwdenk 2043c609719bSwdenk - CFG_ENV_OFFSET: 2044c609719bSwdenk - CFG_ENV_SIZE: 2045c609719bSwdenk 2046c609719bSwdenk These two #defines specify the offset and size of the 2047c609719bSwdenk environment area within the total memory of your EEPROM. 2048c609719bSwdenk 2049c609719bSwdenk - CFG_I2C_EEPROM_ADDR: 2050c609719bSwdenk If defined, specified the chip address of the EEPROM device. 2051c609719bSwdenk The default address is zero. 2052c609719bSwdenk 2053c609719bSwdenk - CFG_EEPROM_PAGE_WRITE_BITS: 2054c609719bSwdenk If defined, the number of bits used to address bytes in a 2055c609719bSwdenk single page in the EEPROM device. A 64 byte page, for example 2056c609719bSwdenk would require six bits. 2057c609719bSwdenk 2058c609719bSwdenk - CFG_EEPROM_PAGE_WRITE_DELAY_MS: 2059c609719bSwdenk If defined, the number of milliseconds to delay between 2060c609719bSwdenk page writes. The default is zero milliseconds. 2061c609719bSwdenk 2062c609719bSwdenk - CFG_I2C_EEPROM_ADDR_LEN: 2063c609719bSwdenk The length in bytes of the EEPROM memory array address. Note 2064c609719bSwdenk that this is NOT the chip address length! 2065c609719bSwdenk 20665cf91d6bSwdenk - CFG_I2C_EEPROM_ADDR_OVERFLOW: 20675cf91d6bSwdenk EEPROM chips that implement "address overflow" are ones 20685cf91d6bSwdenk like Catalyst 24WC04/08/16 which has 9/10/11 bits of 20695cf91d6bSwdenk address and the extra bits end up in the "chip address" bit 20705cf91d6bSwdenk slots. This makes a 24WC08 (1Kbyte) chip look like four 256 20715cf91d6bSwdenk byte chips. 20725cf91d6bSwdenk 20735cf91d6bSwdenk Note that we consider the length of the address field to 20745cf91d6bSwdenk still be one byte because the extra address bits are hidden 20755cf91d6bSwdenk in the chip address. 20765cf91d6bSwdenk 2077c609719bSwdenk - CFG_EEPROM_SIZE: 2078c609719bSwdenk The size in bytes of the EEPROM device. 2079c609719bSwdenk 2080c609719bSwdenk 20815779d8d9Swdenk- CFG_ENV_IS_IN_DATAFLASH: 20825779d8d9Swdenk 20835779d8d9Swdenk Define this if you have a DataFlash memory device which you 20845779d8d9Swdenk want to use for the environment. 20855779d8d9Swdenk 20865779d8d9Swdenk - CFG_ENV_OFFSET: 20875779d8d9Swdenk - CFG_ENV_ADDR: 20885779d8d9Swdenk - CFG_ENV_SIZE: 20895779d8d9Swdenk 20905779d8d9Swdenk These three #defines specify the offset and size of the 20915779d8d9Swdenk environment area within the total memory of your DataFlash placed 20925779d8d9Swdenk at the specified address. 20935779d8d9Swdenk 209413a5695bSwdenk- CFG_ENV_IS_IN_NAND: 209513a5695bSwdenk 209613a5695bSwdenk Define this if you have a NAND device which you want to use 209713a5695bSwdenk for the environment. 209813a5695bSwdenk 209913a5695bSwdenk - CFG_ENV_OFFSET: 210013a5695bSwdenk - CFG_ENV_SIZE: 210113a5695bSwdenk 210213a5695bSwdenk These two #defines specify the offset and size of the environment 210313a5695bSwdenk area within the first NAND device. 21045779d8d9Swdenk 2105e443c944SMarkus Klotzbuecher - CFG_ENV_OFFSET_REDUND 2106e443c944SMarkus Klotzbuecher 2107e443c944SMarkus Klotzbuecher This setting describes a second storage area of CFG_ENV_SIZE 2108e443c944SMarkus Klotzbuecher size used to hold a redundant copy of the environment data, 2109e443c944SMarkus Klotzbuecher so that there is a valid backup copy in case there is a 2110e443c944SMarkus Klotzbuecher power failure during a "saveenv" operation. 2111e443c944SMarkus Klotzbuecher 2112e443c944SMarkus Klotzbuecher Note: CFG_ENV_OFFSET and CFG_ENV_OFFSET_REDUND must be aligned 2113e443c944SMarkus Klotzbuecher to a block boundary, and CFG_ENV_SIZE must be a multiple of 2114e443c944SMarkus Klotzbuecher the NAND devices block size. 2115e443c944SMarkus Klotzbuecher 2116c609719bSwdenk- CFG_SPI_INIT_OFFSET 2117c609719bSwdenk 2118c609719bSwdenk Defines offset to the initial SPI buffer area in DPRAM. The 2119c609719bSwdenk area is used at an early stage (ROM part) if the environment 2120c609719bSwdenk is configured to reside in the SPI EEPROM: We need a 520 byte 2121c609719bSwdenk scratch DPRAM area. It is used between the two initialization 2122c609719bSwdenk calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems 2123c609719bSwdenk to be a good choice since it makes it far enough from the 2124c609719bSwdenk start of the data area as well as from the stack pointer. 2125c609719bSwdenk 2126c609719bSwdenkPlease note that the environment is read-only as long as the monitor 2127c609719bSwdenkhas been relocated to RAM and a RAM copy of the environment has been 2128c609719bSwdenkcreated; also, when using EEPROM you will have to use getenv_r() 2129c609719bSwdenkuntil then to read environment variables. 2130c609719bSwdenk 213185ec0bccSwdenkThe environment is protected by a CRC32 checksum. Before the monitor 213285ec0bccSwdenkis relocated into RAM, as a result of a bad CRC you will be working 213385ec0bccSwdenkwith the compiled-in default environment - *silently*!!! [This is 213485ec0bccSwdenknecessary, because the first environment variable we need is the 213585ec0bccSwdenk"baudrate" setting for the console - if we have a bad CRC, we don't 213685ec0bccSwdenkhave any device yet where we could complain.] 2137c609719bSwdenk 2138c609719bSwdenkNote: once the monitor has been relocated, then it will complain if 2139c609719bSwdenkthe default environment is used; a new CRC is computed as soon as you 214085ec0bccSwdenkuse the "saveenv" command to store a valid environment. 2141c609719bSwdenk 2142fc3e2165Swdenk- CFG_FAULT_ECHO_LINK_DOWN: 2143fc3e2165Swdenk Echo the inverted Ethernet link state to the fault LED. 2144fc3e2165Swdenk 2145fc3e2165Swdenk Note: If this option is active, then CFG_FAULT_MII_ADDR 2146fc3e2165Swdenk also needs to be defined. 2147fc3e2165Swdenk 2148fc3e2165Swdenk- CFG_FAULT_MII_ADDR: 2149fc3e2165Swdenk MII address of the PHY to check for the Ethernet link state. 2150c609719bSwdenk 2151c40b2956Swdenk- CFG_64BIT_VSPRINTF: 2152c40b2956Swdenk Makes vsprintf (and all *printf functions) support printing 2153c40b2956Swdenk of 64bit values by using the L quantifier 2154c40b2956Swdenk 2155c40b2956Swdenk- CFG_64BIT_STRTOUL: 2156c40b2956Swdenk Adds simple_strtoull that returns a 64bit value 2157c40b2956Swdenk 2158c609719bSwdenkLow Level (hardware related) configuration options: 2159dc7c9a1aSwdenk--------------------------------------------------- 2160c609719bSwdenk 2161c609719bSwdenk- CFG_CACHELINE_SIZE: 2162c609719bSwdenk Cache Line Size of the CPU. 2163c609719bSwdenk 2164c609719bSwdenk- CFG_DEFAULT_IMMR: 2165c609719bSwdenk Default address of the IMMR after system reset. 21662535d602Swdenk 21672535d602Swdenk Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU, 21682535d602Swdenk and RPXsuper) to be able to adjust the position of 21692535d602Swdenk the IMMR register after a reset. 2170c609719bSwdenk 21717f6c2cbcSwdenk- Floppy Disk Support: 21727f6c2cbcSwdenk CFG_FDC_DRIVE_NUMBER 21737f6c2cbcSwdenk 21747f6c2cbcSwdenk the default drive number (default value 0) 21757f6c2cbcSwdenk 21767f6c2cbcSwdenk CFG_ISA_IO_STRIDE 21777f6c2cbcSwdenk 21787f6c2cbcSwdenk defines the spacing between fdc chipset registers 21797f6c2cbcSwdenk (default value 1) 21807f6c2cbcSwdenk 21817f6c2cbcSwdenk CFG_ISA_IO_OFFSET 21827f6c2cbcSwdenk 21837f6c2cbcSwdenk defines the offset of register from address. It 21847f6c2cbcSwdenk depends on which part of the data bus is connected to 21857f6c2cbcSwdenk the fdc chipset. (default value 0) 21867f6c2cbcSwdenk 21877f6c2cbcSwdenk If CFG_ISA_IO_STRIDE CFG_ISA_IO_OFFSET and 21887f6c2cbcSwdenk CFG_FDC_DRIVE_NUMBER are undefined, they take their 21897f6c2cbcSwdenk default value. 21907f6c2cbcSwdenk 21917f6c2cbcSwdenk if CFG_FDC_HW_INIT is defined, then the function 21927f6c2cbcSwdenk fdc_hw_init() is called at the beginning of the FDC 21937f6c2cbcSwdenk setup. fdc_hw_init() must be provided by the board 21947f6c2cbcSwdenk source code. It is used to make hardware dependant 21957f6c2cbcSwdenk initializations. 21967f6c2cbcSwdenk 219725d6712aSwdenk- CFG_IMMR: Physical address of the Internal Memory. 219825d6712aSwdenk DO NOT CHANGE unless you know exactly what you're 219925d6712aSwdenk doing! (11-4) [MPC8xx/82xx systems only] 2200c609719bSwdenk 2201c609719bSwdenk- CFG_INIT_RAM_ADDR: 2202c609719bSwdenk 22037152b1d0Swdenk Start address of memory area that can be used for 2204c609719bSwdenk initial data and stack; please note that this must be 2205c609719bSwdenk writable memory that is working WITHOUT special 2206c609719bSwdenk initialization, i. e. you CANNOT use normal RAM which 2207c609719bSwdenk will become available only after programming the 2208c609719bSwdenk memory controller and running certain initialization 2209c609719bSwdenk sequences. 2210c609719bSwdenk 2211c609719bSwdenk U-Boot uses the following memory types: 2212c609719bSwdenk - MPC8xx and MPC8260: IMMR (internal memory of the CPU) 2213c609719bSwdenk - MPC824X: data cache 2214c609719bSwdenk - PPC4xx: data cache 2215c609719bSwdenk 221685ec0bccSwdenk- CFG_GBL_DATA_OFFSET: 2217c609719bSwdenk 2218c609719bSwdenk Offset of the initial data structure in the memory 2219c609719bSwdenk area defined by CFG_INIT_RAM_ADDR. Usually 222085ec0bccSwdenk CFG_GBL_DATA_OFFSET is chosen such that the initial 2221c609719bSwdenk data is located at the end of the available space 2222c609719bSwdenk (sometimes written as (CFG_INIT_RAM_END - 2223c609719bSwdenk CFG_INIT_DATA_SIZE), and the initial stack is just 2224c609719bSwdenk below that area (growing from (CFG_INIT_RAM_ADDR + 222585ec0bccSwdenk CFG_GBL_DATA_OFFSET) downward. 2226c609719bSwdenk 2227c609719bSwdenk Note: 2228c609719bSwdenk On the MPC824X (or other systems that use the data 2229c609719bSwdenk cache for initial memory) the address chosen for 2230c609719bSwdenk CFG_INIT_RAM_ADDR is basically arbitrary - it must 2231c609719bSwdenk point to an otherwise UNUSED address space between 2232c609719bSwdenk the top of RAM and the start of the PCI space. 2233c609719bSwdenk 2234c609719bSwdenk- CFG_SIUMCR: SIU Module Configuration (11-6) 2235c609719bSwdenk 2236c609719bSwdenk- CFG_SYPCR: System Protection Control (11-9) 2237c609719bSwdenk 2238c609719bSwdenk- CFG_TBSCR: Time Base Status and Control (11-26) 2239c609719bSwdenk 2240c609719bSwdenk- CFG_PISCR: Periodic Interrupt Status and Control (11-31) 2241c609719bSwdenk 2242c609719bSwdenk- CFG_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30) 2243c609719bSwdenk 2244c609719bSwdenk- CFG_SCCR: System Clock and reset Control Register (15-27) 2245c609719bSwdenk 2246c609719bSwdenk- CFG_OR_TIMING_SDRAM: 2247c609719bSwdenk SDRAM timing 2248c609719bSwdenk 2249c609719bSwdenk- CFG_MAMR_PTA: 2250c609719bSwdenk periodic timer for refresh 2251c609719bSwdenk 2252c609719bSwdenk- CFG_DER: Debug Event Register (37-47) 2253c609719bSwdenk 2254c609719bSwdenk- FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CFG_REMAP_OR_AM, 2255c609719bSwdenk CFG_PRELIM_OR_AM, CFG_OR_TIMING_FLASH, CFG_OR0_REMAP, 2256c609719bSwdenk CFG_OR0_PRELIM, CFG_BR0_PRELIM, CFG_OR1_REMAP, CFG_OR1_PRELIM, 2257c609719bSwdenk CFG_BR1_PRELIM: 2258c609719bSwdenk Memory Controller Definitions: BR0/1 and OR0/1 (FLASH) 2259c609719bSwdenk 2260c609719bSwdenk- SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE, 2261c609719bSwdenk CFG_OR_TIMING_SDRAM, CFG_OR2_PRELIM, CFG_BR2_PRELIM, 2262c609719bSwdenk CFG_OR3_PRELIM, CFG_BR3_PRELIM: 2263c609719bSwdenk Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM) 2264c609719bSwdenk 2265c609719bSwdenk- CFG_MAMR_PTA, CFG_MPTPR_2BK_4K, CFG_MPTPR_1BK_4K, CFG_MPTPR_2BK_8K, 2266c609719bSwdenk CFG_MPTPR_1BK_8K, CFG_MAMR_8COL, CFG_MAMR_9COL: 2267c609719bSwdenk Machine Mode Register and Memory Periodic Timer 2268c609719bSwdenk Prescaler definitions (SDRAM timing) 2269c609719bSwdenk 2270c609719bSwdenk- CFG_I2C_UCODE_PATCH, CFG_I2C_DPMEM_OFFSET [0x1FC0]: 2271c609719bSwdenk enable I2C microcode relocation patch (MPC8xx); 2272c609719bSwdenk define relocation offset in DPRAM [DSP2] 2273c609719bSwdenk 2274c609719bSwdenk- CFG_SPI_UCODE_PATCH, CFG_SPI_DPMEM_OFFSET [0x1FC0]: 2275c609719bSwdenk enable SPI microcode relocation patch (MPC8xx); 2276c609719bSwdenk define relocation offset in DPRAM [SCC4] 2277c609719bSwdenk 2278c609719bSwdenk- CFG_USE_OSCCLK: 2279c609719bSwdenk Use OSCM clock mode on MBX8xx board. Be careful, 2280c609719bSwdenk wrong setting might damage your board. Read 2281c609719bSwdenk doc/README.MBX before setting this variable! 2282c609719bSwdenk 2283ea909b76Swdenk- CFG_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only) 2284ea909b76Swdenk Offset of the bootmode word in DPRAM used by post 2285ea909b76Swdenk (Power On Self Tests). This definition overrides 2286ea909b76Swdenk #define'd default value in commproc.h resp. 2287ea909b76Swdenk cpm_8260.h. 2288ea909b76Swdenk 22895d232d0eSwdenk- CFG_PCI_SLV_MEM_LOCAL, CFG_PCI_SLV_MEM_BUS, CFG_PICMR0_MASK_ATTRIB, 22905d232d0eSwdenk CFG_PCI_MSTR0_LOCAL, CFG_PCIMSK0_MASK, CFG_PCI_MSTR1_LOCAL, 22915d232d0eSwdenk CFG_PCIMSK1_MASK, CFG_PCI_MSTR_MEM_LOCAL, CFG_PCI_MSTR_MEM_BUS, 22925d232d0eSwdenk CFG_CPU_PCI_MEM_START, CFG_PCI_MSTR_MEM_SIZE, CFG_POCMR0_MASK_ATTRIB, 22935d232d0eSwdenk CFG_PCI_MSTR_MEMIO_LOCAL, CFG_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START, 22945d232d0eSwdenk CFG_PCI_MSTR_MEMIO_SIZE, CFG_POCMR1_MASK_ATTRIB, CFG_PCI_MSTR_IO_LOCAL, 22955d232d0eSwdenk CFG_PCI_MSTR_IO_BUS, CFG_CPU_PCI_IO_START, CFG_PCI_MSTR_IO_SIZE, 22965d232d0eSwdenk CFG_POCMR2_MASK_ATTRIB: (MPC826x only) 22975d232d0eSwdenk Overrides the default PCI memory map in cpu/mpc8260/pci.c if set. 22985d232d0eSwdenk 2299bb99ad6dSBen Warren- CONFIG_SPD_EEPROM 2300bb99ad6dSBen Warren Get DDR timing information from an I2C EEPROM. Common with pluggable 2301bb99ad6dSBen Warren memory modules such as SODIMMs 2302bb99ad6dSBen Warren SPD_EEPROM_ADDRESS 2303bb99ad6dSBen Warren I2C address of the SPD EEPROM 2304bb99ad6dSBen Warren 2305bb99ad6dSBen Warren- CFG_SPD_BUS_NUM 2306bb99ad6dSBen Warren If SPD EEPROM is on an I2C bus other than the first one, specify here. 2307bb99ad6dSBen Warren Note that the value must resolve to something your driver can deal with. 2308bb99ad6dSBen Warren 23092ad6b513STimur Tabi- CFG_83XX_DDR_USES_CS0 23102ad6b513STimur Tabi Only for 83xx systems. If specified, then DDR should be configured 23112ad6b513STimur Tabi using CS0 and CS1 instead of CS2 and CS3. 23122ad6b513STimur Tabi 23132ad6b513STimur Tabi- CFG_83XX_DDR_USES_CS0 23142ad6b513STimur Tabi Only for 83xx systems. If specified, then DDR should be configured 23152ad6b513STimur Tabi using CS0 and CS1 instead of CS2 and CS3. 23162ad6b513STimur Tabi 2317c26e454dSwdenk- CONFIG_ETHER_ON_FEC[12] 2318c26e454dSwdenk Define to enable FEC[12] on a 8xx series processor. 2319c26e454dSwdenk 2320c26e454dSwdenk- CONFIG_FEC[12]_PHY 2321c26e454dSwdenk Define to the hardcoded PHY address which corresponds 23226e592385Swdenk to the given FEC; i. e. 2323c26e454dSwdenk #define CONFIG_FEC1_PHY 4 2324c26e454dSwdenk means that the PHY with address 4 is connected to FEC1 2325c26e454dSwdenk 2326c26e454dSwdenk When set to -1, means to probe for first available. 2327c26e454dSwdenk 2328c26e454dSwdenk- CONFIG_FEC[12]_PHY_NORXERR 2329c26e454dSwdenk The PHY does not have a RXERR line (RMII only). 2330c26e454dSwdenk (so program the FEC to ignore it). 2331c26e454dSwdenk 2332c26e454dSwdenk- CONFIG_RMII 2333c26e454dSwdenk Enable RMII mode for all FECs. 2334c26e454dSwdenk Note that this is a global option, we can't 2335c26e454dSwdenk have one FEC in standard MII mode and another in RMII mode. 2336c26e454dSwdenk 23375cf91d6bSwdenk- CONFIG_CRC32_VERIFY 23385cf91d6bSwdenk Add a verify option to the crc32 command. 23395cf91d6bSwdenk The syntax is: 23405cf91d6bSwdenk 23415cf91d6bSwdenk => crc32 -v <address> <count> <crc32> 23425cf91d6bSwdenk 23435cf91d6bSwdenk Where address/count indicate a memory area 23445cf91d6bSwdenk and crc32 is the correct crc32 which the 23455cf91d6bSwdenk area should have. 23465cf91d6bSwdenk 234756523f12Swdenk- CONFIG_LOOPW 234856523f12Swdenk Add the "loopw" memory command. This only takes effect if 2349602ad3b3SJon Loeliger the memory commands are activated globally (CONFIG_CMD_MEM). 235056523f12Swdenk 23517b466641Sstroese- CONFIG_MX_CYCLIC 23527b466641Sstroese Add the "mdc" and "mwc" memory commands. These are cyclic 23537b466641Sstroese "md/mw" commands. 23547b466641Sstroese Examples: 23557b466641Sstroese 23567b466641Sstroese => mdc.b 10 4 500 23577b466641Sstroese This command will print 4 bytes (10,11,12,13) each 500 ms. 23587b466641Sstroese 23597b466641Sstroese => mwc.l 100 12345678 10 23607b466641Sstroese This command will write 12345678 to address 100 all 10 ms. 23617b466641Sstroese 23627b466641Sstroese This only takes effect if the memory commands are activated 2363602ad3b3SJon Loeliger globally (CONFIG_CMD_MEM). 23647b466641Sstroese 23658aa1a2d1Swdenk- CONFIG_SKIP_LOWLEVEL_INIT 23668aa1a2d1Swdenk- CONFIG_SKIP_RELOCATE_UBOOT 23678aa1a2d1Swdenk 23688aa1a2d1Swdenk [ARM only] If these variables are defined, then 23698aa1a2d1Swdenk certain low level initializations (like setting up 23708aa1a2d1Swdenk the memory controller) are omitted and/or U-Boot does 23718aa1a2d1Swdenk not relocate itself into RAM. 23728aa1a2d1Swdenk Normally these variables MUST NOT be defined. The 23738aa1a2d1Swdenk only exception is when U-Boot is loaded (to RAM) by 23748aa1a2d1Swdenk some other boot loader or by a debugger which 23758aa1a2d1Swdenk performs these intializations itself. 23768aa1a2d1Swdenk 2377400558b5Swdenk 2378c609719bSwdenkBuilding the Software: 2379c609719bSwdenk====================== 2380c609719bSwdenk 2381c609719bSwdenkBuilding U-Boot has been tested in native PPC environments (on a 2382c609719bSwdenkPowerBook G3 running LinuxPPC 2000) and in cross environments 2383c609719bSwdenk(running RedHat 6.x and 7.x Linux on x86, Solaris 2.6 on a SPARC, and 2384c609719bSwdenkNetBSD 1.5 on x86). 2385c609719bSwdenk 2386c609719bSwdenkIf you are not using a native PPC environment, it is assumed that you 2387c609719bSwdenkhave the GNU cross compiling tools available in your path and named 2388c609719bSwdenkwith a prefix of "powerpc-linux-". If this is not the case, (e.g. if 2389c609719bSwdenkyou are using Monta Vista's Hard Hat Linux CDK 1.2) you must change 2390c609719bSwdenkthe definition of CROSS_COMPILE in Makefile. For HHL on a 4xx CPU, 2391c609719bSwdenkchange it to: 2392c609719bSwdenk 2393c609719bSwdenk CROSS_COMPILE = ppc_4xx- 2394c609719bSwdenk 2395c609719bSwdenk 2396c609719bSwdenkU-Boot is intended to be simple to build. After installing the 2397c609719bSwdenksources you must configure U-Boot for one specific board type. This 2398c609719bSwdenkis done by typing: 2399c609719bSwdenk 2400c609719bSwdenk make NAME_config 2401c609719bSwdenk 2402c609719bSwdenkwhere "NAME_config" is the name of one of the existing 24032628114eSKim Phillipsconfigurations; see the main Makefile for supported names. 240454387ac9Swdenk 2405c609719bSwdenkNote: for some board special configuration names may exist; check if 2406c609719bSwdenk additional information is available from the board vendor; for 24072729af9dSwdenk instance, the TQM823L systems are available without (standard) 24082729af9dSwdenk or with LCD support. You can select such additional "features" 2409c609719bSwdenk when chosing the configuration, i. e. 2410c609719bSwdenk 24112729af9dSwdenk make TQM823L_config 24122729af9dSwdenk - will configure for a plain TQM823L, i. e. no LCD support 2413c609719bSwdenk 2414c609719bSwdenk make TQM823L_LCD_config 2415c609719bSwdenk - will configure for a TQM823L with U-Boot console on LCD 2416c609719bSwdenk 2417c609719bSwdenk etc. 2418c609719bSwdenk 2419c609719bSwdenk 2420c609719bSwdenkFinally, type "make all", and you should get some working U-Boot 24217152b1d0Swdenkimages ready for download to / installation on your system: 2422c609719bSwdenk 2423c609719bSwdenk- "u-boot.bin" is a raw binary image 2424c609719bSwdenk- "u-boot" is an image in ELF binary format 2425c609719bSwdenk- "u-boot.srec" is in Motorola S-Record format 2426c609719bSwdenk 2427baf31249SMarian BalakowiczBy default the build is performed locally and the objects are saved 2428baf31249SMarian Balakowiczin the source directory. One of the two methods can be used to change 2429baf31249SMarian Balakowiczthis behavior and build U-Boot to some external directory: 2430baf31249SMarian Balakowicz 2431baf31249SMarian Balakowicz1. Add O= to the make command line invocations: 2432baf31249SMarian Balakowicz 2433baf31249SMarian Balakowicz make O=/tmp/build distclean 2434baf31249SMarian Balakowicz make O=/tmp/build NAME_config 2435baf31249SMarian Balakowicz make O=/tmp/build all 2436baf31249SMarian Balakowicz 2437baf31249SMarian Balakowicz2. Set environment variable BUILD_DIR to point to the desired location: 2438baf31249SMarian Balakowicz 2439baf31249SMarian Balakowicz export BUILD_DIR=/tmp/build 2440baf31249SMarian Balakowicz make distclean 2441baf31249SMarian Balakowicz make NAME_config 2442baf31249SMarian Balakowicz make all 2443baf31249SMarian Balakowicz 2444baf31249SMarian BalakowiczNote that the command line "O=" setting overrides the BUILD_DIR environment 2445baf31249SMarian Balakowiczvariable. 2446baf31249SMarian Balakowicz 2447c609719bSwdenk 2448c609719bSwdenkPlease be aware that the Makefiles assume you are using GNU make, so 2449c609719bSwdenkfor instance on NetBSD you might need to use "gmake" instead of 2450c609719bSwdenknative "make". 2451c609719bSwdenk 2452c609719bSwdenk 2453c609719bSwdenkIf the system board that you have is not listed, then you will need 2454c609719bSwdenkto port U-Boot to your hardware platform. To do this, follow these 2455c609719bSwdenksteps: 2456c609719bSwdenk 2457c609719bSwdenk1. Add a new configuration option for your board to the toplevel 245885ec0bccSwdenk "Makefile" and to the "MAKEALL" script, using the existing 245985ec0bccSwdenk entries as examples. Note that here and at many other places 24607152b1d0Swdenk boards and other names are listed in alphabetical sort order. Please 246185ec0bccSwdenk keep this order. 2462c609719bSwdenk2. Create a new directory to hold your board specific code. Add any 246385ec0bccSwdenk files you need. In your board directory, you will need at least 246485ec0bccSwdenk the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds". 246585ec0bccSwdenk3. Create a new configuration file "include/configs/<board>.h" for 246685ec0bccSwdenk your board 2467c609719bSwdenk3. If you're porting U-Boot to a new CPU, then also create a new 2468c609719bSwdenk directory to hold your CPU specific code. Add any files you need. 246985ec0bccSwdenk4. Run "make <board>_config" with your new name. 2470c609719bSwdenk5. Type "make", and you should get a working "u-boot.srec" file 2471c609719bSwdenk to be installed on your target system. 247285ec0bccSwdenk6. Debug and solve any problems that might arise. 2473c609719bSwdenk [Of course, this last step is much harder than it sounds.] 2474c609719bSwdenk 2475c609719bSwdenk 2476c609719bSwdenkTesting of U-Boot Modifications, Ports to New Hardware, etc.: 2477c609719bSwdenk============================================================== 2478c609719bSwdenk 2479c609719bSwdenkIf you have modified U-Boot sources (for instance added a new board 2480c609719bSwdenkor support for new devices, a new CPU, etc.) you are expected to 2481c609719bSwdenkprovide feedback to the other developers. The feedback normally takes 2482c609719bSwdenkthe form of a "patch", i. e. a context diff against a certain (latest 2483c609719bSwdenkofficial or latest in CVS) version of U-Boot sources. 2484c609719bSwdenk 2485c609719bSwdenkBut before you submit such a patch, please verify that your modifi- 2486c609719bSwdenkcation did not break existing code. At least make sure that *ALL* of 2487c609719bSwdenkthe supported boards compile WITHOUT ANY compiler warnings. To do so, 2488c609719bSwdenkjust run the "MAKEALL" script, which will configure and build U-Boot 2489c609719bSwdenkfor ALL supported system. Be warned, this will take a while. You can 24907152b1d0Swdenkselect which (cross) compiler to use by passing a `CROSS_COMPILE' 2491c609719bSwdenkenvironment variable to the script, i. e. to use the cross tools from 2492c609719bSwdenkMontaVista's Hard Hat Linux you can type 2493c609719bSwdenk 2494c609719bSwdenk CROSS_COMPILE=ppc_8xx- MAKEALL 2495c609719bSwdenk 2496c609719bSwdenkor to build on a native PowerPC system you can type 2497c609719bSwdenk 2498c609719bSwdenk CROSS_COMPILE=' ' MAKEALL 2499c609719bSwdenk 2500baf31249SMarian BalakowiczWhen using the MAKEALL script, the default behaviour is to build U-Boot 2501baf31249SMarian Balakowiczin the source directory. This location can be changed by setting the 2502baf31249SMarian BalakowiczBUILD_DIR environment variable. Also, for each target built, the MAKEALL 2503baf31249SMarian Balakowiczscript saves two log files (<target>.ERR and <target>.MAKEALL) in the 2504baf31249SMarian Balakowicz<source dir>/LOG directory. This default location can be changed by 2505baf31249SMarian Balakowiczsetting the MAKEALL_LOGDIR environment variable. For example: 2506baf31249SMarian Balakowicz 2507baf31249SMarian Balakowicz export BUILD_DIR=/tmp/build 2508baf31249SMarian Balakowicz export MAKEALL_LOGDIR=/tmp/log 2509baf31249SMarian Balakowicz CROSS_COMPILE=ppc_8xx- MAKEALL 2510baf31249SMarian Balakowicz 2511baf31249SMarian BalakowiczWith the above settings build objects are saved in the /tmp/build, log 2512baf31249SMarian Balakowiczfiles are saved in the /tmp/log and the source tree remains clean during 2513baf31249SMarian Balakowiczthe whole build process. 2514baf31249SMarian Balakowicz 2515baf31249SMarian Balakowicz 2516c609719bSwdenkSee also "U-Boot Porting Guide" below. 2517c609719bSwdenk 2518c609719bSwdenk 2519c609719bSwdenkMonitor Commands - Overview: 2520c609719bSwdenk============================ 2521c609719bSwdenk 2522c609719bSwdenkgo - start application at address 'addr' 2523c609719bSwdenkrun - run commands in an environment variable 2524c609719bSwdenkbootm - boot application image from memory 2525c609719bSwdenkbootp - boot image via network using BootP/TFTP protocol 2526c609719bSwdenktftpboot- boot image via network using TFTP protocol 2527c609719bSwdenk and env variables "ipaddr" and "serverip" 2528c609719bSwdenk (and eventually "gatewayip") 2529c609719bSwdenkrarpboot- boot image via network using RARP/TFTP protocol 2530c609719bSwdenkdiskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd' 2531c609719bSwdenkloads - load S-Record file over serial line 2532c609719bSwdenkloadb - load binary file over serial line (kermit mode) 2533c609719bSwdenkmd - memory display 2534c609719bSwdenkmm - memory modify (auto-incrementing) 2535c609719bSwdenknm - memory modify (constant address) 2536c609719bSwdenkmw - memory write (fill) 2537c609719bSwdenkcp - memory copy 2538c609719bSwdenkcmp - memory compare 2539c609719bSwdenkcrc32 - checksum calculation 2540c609719bSwdenkimd - i2c memory display 2541c609719bSwdenkimm - i2c memory modify (auto-incrementing) 2542c609719bSwdenkinm - i2c memory modify (constant address) 2543c609719bSwdenkimw - i2c memory write (fill) 2544c609719bSwdenkicrc32 - i2c checksum calculation 2545c609719bSwdenkiprobe - probe to discover valid I2C chip addresses 2546c609719bSwdenkiloop - infinite loop on address range 2547c609719bSwdenkisdram - print SDRAM configuration information 2548c609719bSwdenksspi - SPI utility commands 2549c609719bSwdenkbase - print or set address offset 2550c609719bSwdenkprintenv- print environment variables 2551c609719bSwdenksetenv - set environment variables 2552c609719bSwdenksaveenv - save environment variables to persistent storage 2553c609719bSwdenkprotect - enable or disable FLASH write protection 2554c609719bSwdenkerase - erase FLASH memory 2555c609719bSwdenkflinfo - print FLASH memory information 2556c609719bSwdenkbdinfo - print Board Info structure 2557c609719bSwdenkiminfo - print header information for application image 2558c609719bSwdenkconinfo - print console devices and informations 2559c609719bSwdenkide - IDE sub-system 2560c609719bSwdenkloop - infinite loop on address range 256156523f12Swdenkloopw - infinite write loop on address range 2562c609719bSwdenkmtest - simple RAM test 2563c609719bSwdenkicache - enable or disable instruction cache 2564c609719bSwdenkdcache - enable or disable data cache 2565c609719bSwdenkreset - Perform RESET of the CPU 2566c609719bSwdenkecho - echo args to console 2567c609719bSwdenkversion - print monitor version 2568c609719bSwdenkhelp - print online help 2569c609719bSwdenk? - alias for 'help' 2570c609719bSwdenk 2571c609719bSwdenk 2572c609719bSwdenkMonitor Commands - Detailed Description: 2573c609719bSwdenk======================================== 2574c609719bSwdenk 2575c609719bSwdenkTODO. 2576c609719bSwdenk 2577c609719bSwdenkFor now: just type "help <command>". 2578c609719bSwdenk 2579c609719bSwdenk 2580c609719bSwdenkEnvironment Variables: 2581c609719bSwdenk====================== 2582c609719bSwdenk 2583c609719bSwdenkU-Boot supports user configuration using Environment Variables which 2584c609719bSwdenkcan be made persistent by saving to Flash memory. 2585c609719bSwdenk 2586c609719bSwdenkEnvironment Variables are set using "setenv", printed using 2587c609719bSwdenk"printenv", and saved to Flash using "saveenv". Using "setenv" 2588c609719bSwdenkwithout a value can be used to delete a variable from the 2589c609719bSwdenkenvironment. As long as you don't save the environment you are 2590c609719bSwdenkworking with an in-memory copy. In case the Flash area containing the 2591c609719bSwdenkenvironment is erased by accident, a default environment is provided. 2592c609719bSwdenk 2593c609719bSwdenkSome configuration options can be set using Environment Variables: 2594c609719bSwdenk 2595c609719bSwdenk baudrate - see CONFIG_BAUDRATE 2596c609719bSwdenk 2597c609719bSwdenk bootdelay - see CONFIG_BOOTDELAY 2598c609719bSwdenk 2599c609719bSwdenk bootcmd - see CONFIG_BOOTCOMMAND 2600c609719bSwdenk 2601c609719bSwdenk bootargs - Boot arguments when booting an RTOS image 2602c609719bSwdenk 2603c609719bSwdenk bootfile - Name of the image to load with TFTP 2604c609719bSwdenk 2605c609719bSwdenk autoload - if set to "no" (any string beginning with 'n'), 2606c609719bSwdenk "bootp" will just load perform a lookup of the 2607c609719bSwdenk configuration from the BOOTP server, but not try to 2608c609719bSwdenk load any image using TFTP 2609c609719bSwdenk 2610c609719bSwdenk autostart - if set to "yes", an image loaded using the "bootp", 2611c609719bSwdenk "rarpboot", "tftpboot" or "diskboot" commands will 2612c609719bSwdenk be automatically started (by internally calling 2613c609719bSwdenk "bootm") 2614c609719bSwdenk 26154a6fd34bSwdenk If set to "no", a standalone image passed to the 26164a6fd34bSwdenk "bootm" command will be copied to the load address 26174a6fd34bSwdenk (and eventually uncompressed), but NOT be started. 26184a6fd34bSwdenk This can be used to load and uncompress arbitrary 26194a6fd34bSwdenk data. 26204a6fd34bSwdenk 262117ea1177Swdenk i2cfast - (PPC405GP|PPC405EP only) 262217ea1177Swdenk if set to 'y' configures Linux I2C driver for fast 262317ea1177Swdenk mode (400kHZ). This environment variable is used in 262417ea1177Swdenk initialization code. So, for changes to be effective 262517ea1177Swdenk it must be saved and board must be reset. 262617ea1177Swdenk 2627c609719bSwdenk initrd_high - restrict positioning of initrd images: 2628c609719bSwdenk If this variable is not set, initrd images will be 2629c609719bSwdenk copied to the highest possible address in RAM; this 2630c609719bSwdenk is usually what you want since it allows for 2631c609719bSwdenk maximum initrd size. If for some reason you want to 2632c609719bSwdenk make sure that the initrd image is loaded below the 2633c609719bSwdenk CFG_BOOTMAPSZ limit, you can set this environment 2634c609719bSwdenk variable to a value of "no" or "off" or "0". 2635c609719bSwdenk Alternatively, you can set it to a maximum upper 2636c609719bSwdenk address to use (U-Boot will still check that it 2637c609719bSwdenk does not overwrite the U-Boot stack and data). 2638c609719bSwdenk 2639c609719bSwdenk For instance, when you have a system with 16 MB 26407152b1d0Swdenk RAM, and want to reserve 4 MB from use by Linux, 2641c609719bSwdenk you can do this by adding "mem=12M" to the value of 2642c609719bSwdenk the "bootargs" variable. However, now you must make 26437152b1d0Swdenk sure that the initrd image is placed in the first 2644c609719bSwdenk 12 MB as well - this can be done with 2645c609719bSwdenk 2646c609719bSwdenk setenv initrd_high 00c00000 2647c609719bSwdenk 264838b99261Swdenk If you set initrd_high to 0xFFFFFFFF, this is an 264938b99261Swdenk indication to U-Boot that all addresses are legal 265038b99261Swdenk for the Linux kernel, including addresses in flash 265138b99261Swdenk memory. In this case U-Boot will NOT COPY the 265238b99261Swdenk ramdisk at all. This may be useful to reduce the 265338b99261Swdenk boot time on your system, but requires that this 265438b99261Swdenk feature is supported by your Linux kernel. 265538b99261Swdenk 2656c609719bSwdenk ipaddr - IP address; needed for tftpboot command 2657c609719bSwdenk 2658c609719bSwdenk loadaddr - Default load address for commands like "bootp", 2659dc7c9a1aSwdenk "rarpboot", "tftpboot", "loadb" or "diskboot" 2660c609719bSwdenk 2661c609719bSwdenk loads_echo - see CONFIG_LOADS_ECHO 2662c609719bSwdenk 2663c609719bSwdenk serverip - TFTP server IP address; needed for tftpboot command 2664c609719bSwdenk 2665c609719bSwdenk bootretry - see CONFIG_BOOT_RETRY_TIME 2666c609719bSwdenk 2667c609719bSwdenk bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR 2668c609719bSwdenk 2669c609719bSwdenk bootstopkey - see CONFIG_AUTOBOOT_STOP_STR 2670c609719bSwdenk 2671a3d991bdSwdenk ethprime - When CONFIG_NET_MULTI is enabled controls which 2672a3d991bdSwdenk interface is used first. 2673a3d991bdSwdenk 2674a3d991bdSwdenk ethact - When CONFIG_NET_MULTI is enabled controls which 2675a3d991bdSwdenk interface is currently active. For example you 2676a3d991bdSwdenk can do the following 2677a3d991bdSwdenk 2678a3d991bdSwdenk => setenv ethact FEC ETHERNET 2679a3d991bdSwdenk => ping 192.168.0.1 # traffic sent on FEC ETHERNET 2680a3d991bdSwdenk => setenv ethact SCC ETHERNET 2681a3d991bdSwdenk => ping 10.0.0.1 # traffic sent on SCC ETHERNET 2682a3d991bdSwdenk 2683a3d991bdSwdenk netretry - When set to "no" each network operation will 2684a3d991bdSwdenk either succeed or fail without retrying. 26856e592385Swdenk When set to "once" the network operation will 26866e592385Swdenk fail when all the available network interfaces 26876e592385Swdenk are tried once without success. 2688a3d991bdSwdenk Useful on scripts which control the retry operation 2689a3d991bdSwdenk themselves. 2690a3d991bdSwdenk 269128cb9375SWolfgang Denk tftpsrcport - If this is set, the value is used for TFTP's 2692ecb0ccd9SWolfgang Denk UDP source port. 2693ecb0ccd9SWolfgang Denk 269428cb9375SWolfgang Denk tftpdstport - If this is set, the value is used for TFTP's UDP 269528cb9375SWolfgang Denk destination port instead of the Well Know Port 69. 269628cb9375SWolfgang Denk 2697a3d991bdSwdenk vlan - When set to a value < 4095 the traffic over 2698a3d991bdSwdenk ethernet is encapsulated/received over 802.1q 2699a3d991bdSwdenk VLAN tagged frames. 2700c609719bSwdenk 2701c609719bSwdenkThe following environment variables may be used and automatically 2702c609719bSwdenkupdated by the network boot commands ("bootp" and "rarpboot"), 2703c609719bSwdenkdepending the information provided by your boot server: 2704c609719bSwdenk 2705c609719bSwdenk bootfile - see above 2706c609719bSwdenk dnsip - IP address of your Domain Name Server 2707fe389a82Sstroese dnsip2 - IP address of your secondary Domain Name Server 2708c609719bSwdenk gatewayip - IP address of the Gateway (Router) to use 2709c609719bSwdenk hostname - Target hostname 2710c609719bSwdenk ipaddr - see above 2711c609719bSwdenk netmask - Subnet Mask 2712c609719bSwdenk rootpath - Pathname of the root filesystem on the NFS server 2713c609719bSwdenk serverip - see above 2714c609719bSwdenk 2715c609719bSwdenk 2716c609719bSwdenkThere are two special Environment Variables: 2717c609719bSwdenk 2718c609719bSwdenk serial# - contains hardware identification information such 2719c609719bSwdenk as type string and/or serial number 2720c609719bSwdenk ethaddr - Ethernet address 2721c609719bSwdenk 2722c609719bSwdenkThese variables can be set only once (usually during manufacturing of 2723c609719bSwdenkthe board). U-Boot refuses to delete or overwrite these variables 2724c609719bSwdenkonce they have been set once. 2725c609719bSwdenk 2726c609719bSwdenk 2727c1551ea8SstroeseFurther special Environment Variables: 2728c1551ea8Sstroese 2729c1551ea8Sstroese ver - Contains the U-Boot version string as printed 2730c1551ea8Sstroese with the "version" command. This variable is 2731c1551ea8Sstroese readonly (see CONFIG_VERSION_VARIABLE). 2732c1551ea8Sstroese 2733c1551ea8Sstroese 2734c609719bSwdenkPlease note that changes to some configuration parameters may take 2735c609719bSwdenkonly effect after the next boot (yes, that's just like Windoze :-). 2736c609719bSwdenk 2737c609719bSwdenk 2738f07771ccSwdenkCommand Line Parsing: 2739f07771ccSwdenk===================== 2740f07771ccSwdenk 2741f07771ccSwdenkThere are two different command line parsers available with U-Boot: 27427152b1d0Swdenkthe old "simple" one, and the much more powerful "hush" shell: 2743f07771ccSwdenk 2744f07771ccSwdenkOld, simple command line parser: 2745f07771ccSwdenk-------------------------------- 2746f07771ccSwdenk 2747f07771ccSwdenk- supports environment variables (through setenv / saveenv commands) 2748f07771ccSwdenk- several commands on one line, separated by ';' 2749fe126d8bSWolfgang Denk- variable substitution using "... ${name} ..." syntax 2750f07771ccSwdenk- special characters ('$', ';') can be escaped by prefixing with '\', 2751f07771ccSwdenk for example: 2752fe126d8bSWolfgang Denk setenv bootcmd bootm \${address} 2753f07771ccSwdenk- You can also escape text by enclosing in single apostrophes, for example: 2754f07771ccSwdenk setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off' 2755f07771ccSwdenk 2756f07771ccSwdenkHush shell: 2757f07771ccSwdenk----------- 2758f07771ccSwdenk 2759f07771ccSwdenk- similar to Bourne shell, with control structures like 2760f07771ccSwdenk if...then...else...fi, for...do...done; while...do...done, 2761f07771ccSwdenk until...do...done, ... 2762f07771ccSwdenk- supports environment ("global") variables (through setenv / saveenv 2763f07771ccSwdenk commands) and local shell variables (through standard shell syntax 2764f07771ccSwdenk "name=value"); only environment variables can be used with "run" 2765f07771ccSwdenk command 2766f07771ccSwdenk 2767f07771ccSwdenkGeneral rules: 2768f07771ccSwdenk-------------- 2769f07771ccSwdenk 2770f07771ccSwdenk(1) If a command line (or an environment variable executed by a "run" 2771f07771ccSwdenk command) contains several commands separated by semicolon, and 2772f07771ccSwdenk one of these commands fails, then the remaining commands will be 2773f07771ccSwdenk executed anyway. 2774f07771ccSwdenk 2775f07771ccSwdenk(2) If you execute several variables with one call to run (i. e. 2776f07771ccSwdenk calling run with a list af variables as arguments), any failing 2777f07771ccSwdenk command will cause "run" to terminate, i. e. the remaining 2778f07771ccSwdenk variables are not executed. 2779f07771ccSwdenk 2780c609719bSwdenkNote for Redundant Ethernet Interfaces: 2781c609719bSwdenk======================================= 2782c609719bSwdenk 27837152b1d0SwdenkSome boards come with redundant ethernet interfaces; U-Boot supports 2784c609719bSwdenksuch configurations and is capable of automatic selection of a 27857152b1d0Swdenk"working" interface when needed. MAC assignment works as follows: 2786c609719bSwdenk 2787c609719bSwdenkNetwork interfaces are numbered eth0, eth1, eth2, ... Corresponding 2788c609719bSwdenkMAC addresses can be stored in the environment as "ethaddr" (=>eth0), 2789c609719bSwdenk"eth1addr" (=>eth1), "eth2addr", ... 2790c609719bSwdenk 2791c609719bSwdenkIf the network interface stores some valid MAC address (for instance 2792c609719bSwdenkin SROM), this is used as default address if there is NO correspon- 2793c609719bSwdenkding setting in the environment; if the corresponding environment 2794c609719bSwdenkvariable is set, this overrides the settings in the card; that means: 2795c609719bSwdenk 2796c609719bSwdenko If the SROM has a valid MAC address, and there is no address in the 2797c609719bSwdenk environment, the SROM's address is used. 2798c609719bSwdenk 2799c609719bSwdenko If there is no valid address in the SROM, and a definition in the 2800c609719bSwdenk environment exists, then the value from the environment variable is 2801c609719bSwdenk used. 2802c609719bSwdenk 2803c609719bSwdenko If both the SROM and the environment contain a MAC address, and 2804c609719bSwdenk both addresses are the same, this MAC address is used. 2805c609719bSwdenk 2806c609719bSwdenko If both the SROM and the environment contain a MAC address, and the 2807c609719bSwdenk addresses differ, the value from the environment is used and a 2808c609719bSwdenk warning is printed. 2809c609719bSwdenk 2810c609719bSwdenko If neither SROM nor the environment contain a MAC address, an error 2811c609719bSwdenk is raised. 2812c609719bSwdenk 2813c609719bSwdenk 2814c609719bSwdenkImage Formats: 2815c609719bSwdenk============== 2816c609719bSwdenk 2817c609719bSwdenkThe "boot" commands of this monitor operate on "image" files which 2818c609719bSwdenkcan be basicly anything, preceeded by a special header; see the 2819c609719bSwdenkdefinitions in include/image.h for details; basicly, the header 2820c609719bSwdenkdefines the following image properties: 2821c609719bSwdenk 2822c609719bSwdenk* Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD, 2823c609719bSwdenk 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks, 28247f70e853Swdenk LynxOS, pSOS, QNX, RTEMS, ARTOS; 28251f4bb37dSwdenk Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS). 28267b64fef3SWolfgang Denk* Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86, 28273d1e8a9dSwdenk IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; 28287b64fef3SWolfgang Denk Currently supported: ARM, AVR32, Intel x86, MIPS, NIOS, PowerPC). 2829c29fdfc1Swdenk* Compression Type (uncompressed, gzip, bzip2) 2830c609719bSwdenk* Load Address 2831c609719bSwdenk* Entry Point 2832c609719bSwdenk* Image Name 2833c609719bSwdenk* Image Timestamp 2834c609719bSwdenk 2835c609719bSwdenkThe header is marked by a special Magic Number, and both the header 2836c609719bSwdenkand the data portions of the image are secured against corruption by 2837c609719bSwdenkCRC32 checksums. 2838c609719bSwdenk 2839c609719bSwdenk 2840c609719bSwdenkLinux Support: 2841c609719bSwdenk============== 2842c609719bSwdenk 2843c609719bSwdenkAlthough U-Boot should support any OS or standalone application 28447152b1d0Swdenkeasily, the main focus has always been on Linux during the design of 2845c609719bSwdenkU-Boot. 2846c609719bSwdenk 2847c609719bSwdenkU-Boot includes many features that so far have been part of some 2848c609719bSwdenkspecial "boot loader" code within the Linux kernel. Also, any 2849c609719bSwdenk"initrd" images to be used are no longer part of one big Linux image; 2850c609719bSwdenkinstead, kernel and "initrd" are separate images. This implementation 28517152b1d0Swdenkserves several purposes: 2852c609719bSwdenk 2853c609719bSwdenk- the same features can be used for other OS or standalone 2854c609719bSwdenk applications (for instance: using compressed images to reduce the 2855c609719bSwdenk Flash memory footprint) 2856c609719bSwdenk 2857c609719bSwdenk- it becomes much easier to port new Linux kernel versions because 28587152b1d0Swdenk lots of low-level, hardware dependent stuff are done by U-Boot 2859c609719bSwdenk 2860c609719bSwdenk- the same Linux kernel image can now be used with different "initrd" 2861c609719bSwdenk images; of course this also means that different kernel images can 2862c609719bSwdenk be run with the same "initrd". This makes testing easier (you don't 2863c609719bSwdenk have to build a new "zImage.initrd" Linux image when you just 2864c609719bSwdenk change a file in your "initrd"). Also, a field-upgrade of the 2865c609719bSwdenk software is easier now. 2866c609719bSwdenk 2867c609719bSwdenk 2868c609719bSwdenkLinux HOWTO: 2869c609719bSwdenk============ 2870c609719bSwdenk 2871c609719bSwdenkPorting Linux to U-Boot based systems: 2872c609719bSwdenk--------------------------------------- 2873c609719bSwdenk 2874c609719bSwdenkU-Boot cannot save you from doing all the necessary modifications to 2875c609719bSwdenkconfigure the Linux device drivers for use with your target hardware 2876c609719bSwdenk(no, we don't intend to provide a full virtual machine interface to 2877c609719bSwdenkLinux :-). 2878c609719bSwdenk 2879c609719bSwdenkBut now you can ignore ALL boot loader code (in arch/ppc/mbxboot). 2880c609719bSwdenk 2881c609719bSwdenkJust make sure your machine specific header file (for instance 2882c609719bSwdenkinclude/asm-ppc/tqm8xx.h) includes the same definition of the Board 2883c609719bSwdenkInformation structure as we define in include/u-boot.h, and make 2884c609719bSwdenksure that your definition of IMAP_ADDR uses the same value as your 2885c609719bSwdenkU-Boot configuration in CFG_IMMR. 2886c609719bSwdenk 2887c609719bSwdenk 2888c609719bSwdenkConfiguring the Linux kernel: 2889c609719bSwdenk----------------------------- 2890c609719bSwdenk 2891c609719bSwdenkNo specific requirements for U-Boot. Make sure you have some root 2892c609719bSwdenkdevice (initial ramdisk, NFS) for your target system. 2893c609719bSwdenk 2894c609719bSwdenk 2895c609719bSwdenkBuilding a Linux Image: 2896c609719bSwdenk----------------------- 2897c609719bSwdenk 289824ee89b9SwdenkWith U-Boot, "normal" build targets like "zImage" or "bzImage" are 289924ee89b9Swdenknot used. If you use recent kernel source, a new build target 290024ee89b9Swdenk"uImage" will exist which automatically builds an image usable by 290124ee89b9SwdenkU-Boot. Most older kernels also have support for a "pImage" target, 290224ee89b9Swdenkwhich was introduced for our predecessor project PPCBoot and uses a 290324ee89b9Swdenk100% compatible format. 2904c609719bSwdenk 2905c609719bSwdenkExample: 2906c609719bSwdenk 2907c609719bSwdenk make TQM850L_config 2908c609719bSwdenk make oldconfig 2909c609719bSwdenk make dep 291024ee89b9Swdenk make uImage 2911c609719bSwdenk 291224ee89b9SwdenkThe "uImage" build target uses a special tool (in 'tools/mkimage') to 291324ee89b9Swdenkencapsulate a compressed Linux kernel image with header information, 291424ee89b9SwdenkCRC32 checksum etc. for use with U-Boot. This is what we are doing: 2915c609719bSwdenk 291624ee89b9Swdenk* build a standard "vmlinux" kernel image (in ELF binary format): 291724ee89b9Swdenk 291824ee89b9Swdenk* convert the kernel into a raw binary image: 291924ee89b9Swdenk 292024ee89b9Swdenk ${CROSS_COMPILE}-objcopy -O binary \ 292124ee89b9Swdenk -R .note -R .comment \ 292224ee89b9Swdenk -S vmlinux linux.bin 292324ee89b9Swdenk 292424ee89b9Swdenk* compress the binary image: 292524ee89b9Swdenk 292624ee89b9Swdenk gzip -9 linux.bin 292724ee89b9Swdenk 292824ee89b9Swdenk* package compressed binary image for U-Boot: 292924ee89b9Swdenk 293024ee89b9Swdenk mkimage -A ppc -O linux -T kernel -C gzip \ 293124ee89b9Swdenk -a 0 -e 0 -n "Linux Kernel Image" \ 293224ee89b9Swdenk -d linux.bin.gz uImage 293324ee89b9Swdenk 293424ee89b9Swdenk 293524ee89b9SwdenkThe "mkimage" tool can also be used to create ramdisk images for use 293624ee89b9Swdenkwith U-Boot, either separated from the Linux kernel image, or 293724ee89b9Swdenkcombined into one file. "mkimage" encapsulates the images with a 64 293824ee89b9Swdenkbyte header containing information about target architecture, 293924ee89b9Swdenkoperating system, image type, compression method, entry points, time 294024ee89b9Swdenkstamp, CRC32 checksums, etc. 294124ee89b9Swdenk 294224ee89b9Swdenk"mkimage" can be called in two ways: to verify existing images and 294324ee89b9Swdenkprint the header information, or to build new images. 2944c609719bSwdenk 2945c609719bSwdenkIn the first form (with "-l" option) mkimage lists the information 2946c609719bSwdenkcontained in the header of an existing U-Boot image; this includes 2947c609719bSwdenkchecksum verification: 2948c609719bSwdenk 2949c609719bSwdenk tools/mkimage -l image 2950c609719bSwdenk -l ==> list image header information 2951c609719bSwdenk 2952c609719bSwdenkThe second form (with "-d" option) is used to build a U-Boot image 2953c609719bSwdenkfrom a "data file" which is used as image payload: 2954c609719bSwdenk 2955c609719bSwdenk tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \ 2956c609719bSwdenk -n name -d data_file image 2957c609719bSwdenk -A ==> set architecture to 'arch' 2958c609719bSwdenk -O ==> set operating system to 'os' 2959c609719bSwdenk -T ==> set image type to 'type' 2960c609719bSwdenk -C ==> set compression type 'comp' 2961c609719bSwdenk -a ==> set load address to 'addr' (hex) 2962c609719bSwdenk -e ==> set entry point to 'ep' (hex) 2963c609719bSwdenk -n ==> set image name to 'name' 2964c609719bSwdenk -d ==> use image data from 'datafile' 2965c609719bSwdenk 296669459791SwdenkRight now, all Linux kernels for PowerPC systems use the same load 296769459791Swdenkaddress (0x00000000), but the entry point address depends on the 296869459791Swdenkkernel version: 2969c609719bSwdenk 2970c609719bSwdenk- 2.2.x kernels have the entry point at 0x0000000C, 297124ee89b9Swdenk- 2.3.x and later kernels have the entry point at 0x00000000. 2972c609719bSwdenk 2973c609719bSwdenkSo a typical call to build a U-Boot image would read: 2974c609719bSwdenk 297524ee89b9Swdenk -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 297624ee89b9Swdenk > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \ 297724ee89b9Swdenk > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz \ 297824ee89b9Swdenk > examples/uImage.TQM850L 297924ee89b9Swdenk Image Name: 2.4.4 kernel for TQM850L 2980c609719bSwdenk Created: Wed Jul 19 02:34:59 2000 2981c609719bSwdenk Image Type: PowerPC Linux Kernel Image (gzip compressed) 2982c609719bSwdenk Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 2983c609719bSwdenk Load Address: 0x00000000 298424ee89b9Swdenk Entry Point: 0x00000000 2985c609719bSwdenk 2986c609719bSwdenkTo verify the contents of the image (or check for corruption): 2987c609719bSwdenk 298824ee89b9Swdenk -> tools/mkimage -l examples/uImage.TQM850L 298924ee89b9Swdenk Image Name: 2.4.4 kernel for TQM850L 2990c609719bSwdenk Created: Wed Jul 19 02:34:59 2000 2991c609719bSwdenk Image Type: PowerPC Linux Kernel Image (gzip compressed) 2992c609719bSwdenk Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 2993c609719bSwdenk Load Address: 0x00000000 299424ee89b9Swdenk Entry Point: 0x00000000 2995c609719bSwdenk 2996c609719bSwdenkNOTE: for embedded systems where boot time is critical you can trade 2997c609719bSwdenkspeed for memory and install an UNCOMPRESSED image instead: this 2998c609719bSwdenkneeds more space in Flash, but boots much faster since it does not 2999c609719bSwdenkneed to be uncompressed: 3000c609719bSwdenk 300124ee89b9Swdenk -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz 300224ee89b9Swdenk -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 300324ee89b9Swdenk > -A ppc -O linux -T kernel -C none -a 0 -e 0 \ 300424ee89b9Swdenk > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux \ 300524ee89b9Swdenk > examples/uImage.TQM850L-uncompressed 300624ee89b9Swdenk Image Name: 2.4.4 kernel for TQM850L 3007c609719bSwdenk Created: Wed Jul 19 02:34:59 2000 3008c609719bSwdenk Image Type: PowerPC Linux Kernel Image (uncompressed) 3009c609719bSwdenk Data Size: 792160 Bytes = 773.59 kB = 0.76 MB 3010c609719bSwdenk Load Address: 0x00000000 301124ee89b9Swdenk Entry Point: 0x00000000 3012c609719bSwdenk 3013c609719bSwdenk 3014c609719bSwdenkSimilar you can build U-Boot images from a 'ramdisk.image.gz' file 3015c609719bSwdenkwhen your kernel is intended to use an initial ramdisk: 3016c609719bSwdenk 3017c609719bSwdenk -> tools/mkimage -n 'Simple Ramdisk Image' \ 3018c609719bSwdenk > -A ppc -O linux -T ramdisk -C gzip \ 3019c609719bSwdenk > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd 3020c609719bSwdenk Image Name: Simple Ramdisk Image 3021c609719bSwdenk Created: Wed Jan 12 14:01:50 2000 3022c609719bSwdenk Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 3023c609719bSwdenk Data Size: 566530 Bytes = 553.25 kB = 0.54 MB 3024c609719bSwdenk Load Address: 0x00000000 3025c609719bSwdenk Entry Point: 0x00000000 3026c609719bSwdenk 3027c609719bSwdenk 3028c609719bSwdenkInstalling a Linux Image: 3029c609719bSwdenk------------------------- 3030c609719bSwdenk 3031c609719bSwdenkTo downloading a U-Boot image over the serial (console) interface, 3032c609719bSwdenkyou must convert the image to S-Record format: 3033c609719bSwdenk 3034c609719bSwdenk objcopy -I binary -O srec examples/image examples/image.srec 3035c609719bSwdenk 3036c609719bSwdenkThe 'objcopy' does not understand the information in the U-Boot 3037c609719bSwdenkimage header, so the resulting S-Record file will be relative to 3038c609719bSwdenkaddress 0x00000000. To load it to a given address, you need to 3039c609719bSwdenkspecify the target address as 'offset' parameter with the 'loads' 3040c609719bSwdenkcommand. 3041c609719bSwdenk 3042c609719bSwdenkExample: install the image to address 0x40100000 (which on the 3043c609719bSwdenkTQM8xxL is in the first Flash bank): 3044c609719bSwdenk 3045c609719bSwdenk => erase 40100000 401FFFFF 3046c609719bSwdenk 3047c609719bSwdenk .......... done 3048c609719bSwdenk Erased 8 sectors 3049c609719bSwdenk 3050c609719bSwdenk => loads 40100000 3051c609719bSwdenk ## Ready for S-Record download ... 3052c609719bSwdenk ~>examples/image.srec 3053c609719bSwdenk 1 2 3 4 5 6 7 8 9 10 11 12 13 ... 3054c609719bSwdenk ... 3055c609719bSwdenk 15989 15990 15991 15992 3056c609719bSwdenk [file transfer complete] 3057c609719bSwdenk [connected] 3058c609719bSwdenk ## Start Addr = 0x00000000 3059c609719bSwdenk 3060c609719bSwdenk 3061c609719bSwdenkYou can check the success of the download using the 'iminfo' command; 3062c609719bSwdenkthis includes a checksum verification so you can be sure no data 3063c609719bSwdenkcorruption happened: 3064c609719bSwdenk 3065c609719bSwdenk => imi 40100000 3066c609719bSwdenk 3067c609719bSwdenk ## Checking Image at 40100000 ... 3068c609719bSwdenk Image Name: 2.2.13 for initrd on TQM850L 3069c609719bSwdenk Image Type: PowerPC Linux Kernel Image (gzip compressed) 3070c609719bSwdenk Data Size: 335725 Bytes = 327 kB = 0 MB 3071c609719bSwdenk Load Address: 00000000 3072c609719bSwdenk Entry Point: 0000000c 3073c609719bSwdenk Verifying Checksum ... OK 3074c609719bSwdenk 3075c609719bSwdenk 3076c609719bSwdenkBoot Linux: 3077c609719bSwdenk----------- 3078c609719bSwdenk 3079c609719bSwdenkThe "bootm" command is used to boot an application that is stored in 3080c609719bSwdenkmemory (RAM or Flash). In case of a Linux kernel image, the contents 3081c609719bSwdenkof the "bootargs" environment variable is passed to the kernel as 3082c609719bSwdenkparameters. You can check and modify this variable using the 3083c609719bSwdenk"printenv" and "setenv" commands: 3084c609719bSwdenk 3085c609719bSwdenk 3086c609719bSwdenk => printenv bootargs 3087c609719bSwdenk bootargs=root=/dev/ram 3088c609719bSwdenk 3089c609719bSwdenk => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 3090c609719bSwdenk 3091c609719bSwdenk => printenv bootargs 3092c609719bSwdenk bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 3093c609719bSwdenk 3094c609719bSwdenk => bootm 40020000 3095c609719bSwdenk ## Booting Linux kernel at 40020000 ... 3096c609719bSwdenk Image Name: 2.2.13 for NFS on TQM850L 3097c609719bSwdenk Image Type: PowerPC Linux Kernel Image (gzip compressed) 3098c609719bSwdenk Data Size: 381681 Bytes = 372 kB = 0 MB 3099c609719bSwdenk Load Address: 00000000 3100c609719bSwdenk Entry Point: 0000000c 3101c609719bSwdenk Verifying Checksum ... OK 3102c609719bSwdenk Uncompressing Kernel Image ... OK 3103c609719bSwdenk Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:35:17 MEST 2000 3104c609719bSwdenk Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 3105c609719bSwdenk time_init: decrementer frequency = 187500000/60 3106c609719bSwdenk Calibrating delay loop... 49.77 BogoMIPS 3107c609719bSwdenk Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000] 3108c609719bSwdenk ... 3109c609719bSwdenk 3110c609719bSwdenkIf you want to boot a Linux kernel with initial ram disk, you pass 31117152b1d0Swdenkthe memory addresses of both the kernel and the initrd image (PPBCOOT 3112c609719bSwdenkformat!) to the "bootm" command: 3113c609719bSwdenk 3114c609719bSwdenk => imi 40100000 40200000 3115c609719bSwdenk 3116c609719bSwdenk ## Checking Image at 40100000 ... 3117c609719bSwdenk Image Name: 2.2.13 for initrd on TQM850L 3118c609719bSwdenk Image Type: PowerPC Linux Kernel Image (gzip compressed) 3119c609719bSwdenk Data Size: 335725 Bytes = 327 kB = 0 MB 3120c609719bSwdenk Load Address: 00000000 3121c609719bSwdenk Entry Point: 0000000c 3122c609719bSwdenk Verifying Checksum ... OK 3123c609719bSwdenk 3124c609719bSwdenk ## Checking Image at 40200000 ... 3125c609719bSwdenk Image Name: Simple Ramdisk Image 3126c609719bSwdenk Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 3127c609719bSwdenk Data Size: 566530 Bytes = 553 kB = 0 MB 3128c609719bSwdenk Load Address: 00000000 3129c609719bSwdenk Entry Point: 00000000 3130c609719bSwdenk Verifying Checksum ... OK 3131c609719bSwdenk 3132c609719bSwdenk => bootm 40100000 40200000 3133c609719bSwdenk ## Booting Linux kernel at 40100000 ... 3134c609719bSwdenk Image Name: 2.2.13 for initrd on TQM850L 3135c609719bSwdenk Image Type: PowerPC Linux Kernel Image (gzip compressed) 3136c609719bSwdenk Data Size: 335725 Bytes = 327 kB = 0 MB 3137c609719bSwdenk Load Address: 00000000 3138c609719bSwdenk Entry Point: 0000000c 3139c609719bSwdenk Verifying Checksum ... OK 3140c609719bSwdenk Uncompressing Kernel Image ... OK 3141c609719bSwdenk ## Loading RAMDisk Image at 40200000 ... 3142c609719bSwdenk Image Name: Simple Ramdisk Image 3143c609719bSwdenk Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 3144c609719bSwdenk Data Size: 566530 Bytes = 553 kB = 0 MB 3145c609719bSwdenk Load Address: 00000000 3146c609719bSwdenk Entry Point: 00000000 3147c609719bSwdenk Verifying Checksum ... OK 3148c609719bSwdenk Loading Ramdisk ... OK 3149c609719bSwdenk Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:32:08 MEST 2000 3150c609719bSwdenk Boot arguments: root=/dev/ram 3151c609719bSwdenk time_init: decrementer frequency = 187500000/60 3152c609719bSwdenk Calibrating delay loop... 49.77 BogoMIPS 3153c609719bSwdenk ... 3154c609719bSwdenk RAMDISK: Compressed image found at block 0 3155c609719bSwdenk VFS: Mounted root (ext2 filesystem). 3156c609719bSwdenk 3157c609719bSwdenk bash# 3158c609719bSwdenk 31590267768eSMatthew McClintockBoot Linux and pass a flat device tree: 31600267768eSMatthew McClintock----------- 31610267768eSMatthew McClintock 31620267768eSMatthew McClintockFirst, U-Boot must be compiled with the appropriate defines. See the section 31630267768eSMatthew McClintocktitled "Linux Kernel Interface" above for a more in depth explanation. The 31640267768eSMatthew McClintockfollowing is an example of how to start a kernel and pass an updated 31650267768eSMatthew McClintockflat device tree: 31660267768eSMatthew McClintock 31670267768eSMatthew McClintock=> print oftaddr 31680267768eSMatthew McClintockoftaddr=0x300000 31690267768eSMatthew McClintock=> print oft 31700267768eSMatthew McClintockoft=oftrees/mpc8540ads.dtb 31710267768eSMatthew McClintock=> tftp $oftaddr $oft 31720267768eSMatthew McClintockSpeed: 1000, full duplex 31730267768eSMatthew McClintockUsing TSEC0 device 31740267768eSMatthew McClintockTFTP from server 192.168.1.1; our IP address is 192.168.1.101 31750267768eSMatthew McClintockFilename 'oftrees/mpc8540ads.dtb'. 31760267768eSMatthew McClintockLoad address: 0x300000 31770267768eSMatthew McClintockLoading: # 31780267768eSMatthew McClintockdone 31790267768eSMatthew McClintockBytes transferred = 4106 (100a hex) 31800267768eSMatthew McClintock=> tftp $loadaddr $bootfile 31810267768eSMatthew McClintockSpeed: 1000, full duplex 31820267768eSMatthew McClintockUsing TSEC0 device 31830267768eSMatthew McClintockTFTP from server 192.168.1.1; our IP address is 192.168.1.2 31840267768eSMatthew McClintockFilename 'uImage'. 31850267768eSMatthew McClintockLoad address: 0x200000 31860267768eSMatthew McClintockLoading:############ 31870267768eSMatthew McClintockdone 31880267768eSMatthew McClintockBytes transferred = 1029407 (fb51f hex) 31890267768eSMatthew McClintock=> print loadaddr 31900267768eSMatthew McClintockloadaddr=200000 31910267768eSMatthew McClintock=> print oftaddr 31920267768eSMatthew McClintockoftaddr=0x300000 31930267768eSMatthew McClintock=> bootm $loadaddr - $oftaddr 31940267768eSMatthew McClintock## Booting image at 00200000 ... 31950267768eSMatthew McClintock Image Name: Linux-2.6.17-dirty 31960267768eSMatthew McClintock Image Type: PowerPC Linux Kernel Image (gzip compressed) 31970267768eSMatthew McClintock Data Size: 1029343 Bytes = 1005.2 kB 31980267768eSMatthew McClintock Load Address: 00000000 31990267768eSMatthew McClintock Entry Point: 00000000 32000267768eSMatthew McClintock Verifying Checksum ... OK 32010267768eSMatthew McClintock Uncompressing Kernel Image ... OK 32020267768eSMatthew McClintockBooting using flat device tree at 0x300000 32030267768eSMatthew McClintockUsing MPC85xx ADS machine description 32040267768eSMatthew McClintockMemory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb 32050267768eSMatthew McClintock[snip] 32060267768eSMatthew McClintock 32070267768eSMatthew McClintock 32086069ff26SwdenkMore About U-Boot Image Types: 32096069ff26Swdenk------------------------------ 32106069ff26Swdenk 32116069ff26SwdenkU-Boot supports the following image types: 32126069ff26Swdenk 32136069ff26Swdenk "Standalone Programs" are directly runnable in the environment 32146069ff26Swdenk provided by U-Boot; it is expected that (if they behave 32156069ff26Swdenk well) you can continue to work in U-Boot after return from 32166069ff26Swdenk the Standalone Program. 32176069ff26Swdenk "OS Kernel Images" are usually images of some Embedded OS which 32186069ff26Swdenk will take over control completely. Usually these programs 32196069ff26Swdenk will install their own set of exception handlers, device 32206069ff26Swdenk drivers, set up the MMU, etc. - this means, that you cannot 32216069ff26Swdenk expect to re-enter U-Boot except by resetting the CPU. 32226069ff26Swdenk "RAMDisk Images" are more or less just data blocks, and their 32236069ff26Swdenk parameters (address, size) are passed to an OS kernel that is 32246069ff26Swdenk being started. 32256069ff26Swdenk "Multi-File Images" contain several images, typically an OS 32266069ff26Swdenk (Linux) kernel image and one or more data images like 32276069ff26Swdenk RAMDisks. This construct is useful for instance when you want 32286069ff26Swdenk to boot over the network using BOOTP etc., where the boot 32296069ff26Swdenk server provides just a single image file, but you want to get 32306069ff26Swdenk for instance an OS kernel and a RAMDisk image. 32316069ff26Swdenk 32326069ff26Swdenk "Multi-File Images" start with a list of image sizes, each 32336069ff26Swdenk image size (in bytes) specified by an "uint32_t" in network 32346069ff26Swdenk byte order. This list is terminated by an "(uint32_t)0". 32356069ff26Swdenk Immediately after the terminating 0 follow the images, one by 32366069ff26Swdenk one, all aligned on "uint32_t" boundaries (size rounded up to 32376069ff26Swdenk a multiple of 4 bytes). 32386069ff26Swdenk 32396069ff26Swdenk "Firmware Images" are binary images containing firmware (like 32406069ff26Swdenk U-Boot or FPGA images) which usually will be programmed to 32416069ff26Swdenk flash memory. 32426069ff26Swdenk 32436069ff26Swdenk "Script files" are command sequences that will be executed by 32446069ff26Swdenk U-Boot's command interpreter; this feature is especially 32456069ff26Swdenk useful when you configure U-Boot to use a real shell (hush) 32466069ff26Swdenk as command interpreter. 32476069ff26Swdenk 3248c609719bSwdenk 3249c609719bSwdenkStandalone HOWTO: 3250c609719bSwdenk================= 3251c609719bSwdenk 3252c609719bSwdenkOne of the features of U-Boot is that you can dynamically load and 3253c609719bSwdenkrun "standalone" applications, which can use some resources of 3254c609719bSwdenkU-Boot like console I/O functions or interrupt services. 3255c609719bSwdenk 3256c609719bSwdenkTwo simple examples are included with the sources: 3257c609719bSwdenk 3258c609719bSwdenk"Hello World" Demo: 3259c609719bSwdenk------------------- 3260c609719bSwdenk 3261c609719bSwdenk'examples/hello_world.c' contains a small "Hello World" Demo 3262c609719bSwdenkapplication; it is automatically compiled when you build U-Boot. 3263c609719bSwdenkIt's configured to run at address 0x00040004, so you can play with it 3264c609719bSwdenklike that: 3265c609719bSwdenk 3266c609719bSwdenk => loads 3267c609719bSwdenk ## Ready for S-Record download ... 3268c609719bSwdenk ~>examples/hello_world.srec 3269c609719bSwdenk 1 2 3 4 5 6 7 8 9 10 11 ... 3270c609719bSwdenk [file transfer complete] 3271c609719bSwdenk [connected] 3272c609719bSwdenk ## Start Addr = 0x00040004 3273c609719bSwdenk 3274c609719bSwdenk => go 40004 Hello World! This is a test. 3275c609719bSwdenk ## Starting application at 0x00040004 ... 3276c609719bSwdenk Hello World 3277c609719bSwdenk argc = 7 3278c609719bSwdenk argv[0] = "40004" 3279c609719bSwdenk argv[1] = "Hello" 3280c609719bSwdenk argv[2] = "World!" 3281c609719bSwdenk argv[3] = "This" 3282c609719bSwdenk argv[4] = "is" 3283c609719bSwdenk argv[5] = "a" 3284c609719bSwdenk argv[6] = "test." 3285c609719bSwdenk argv[7] = "<NULL>" 3286c609719bSwdenk Hit any key to exit ... 3287c609719bSwdenk 3288c609719bSwdenk ## Application terminated, rc = 0x0 3289c609719bSwdenk 3290c609719bSwdenkAnother example, which demonstrates how to register a CPM interrupt 3291c609719bSwdenkhandler with the U-Boot code, can be found in 'examples/timer.c'. 3292c609719bSwdenkHere, a CPM timer is set up to generate an interrupt every second. 3293c609719bSwdenkThe interrupt service routine is trivial, just printing a '.' 3294c609719bSwdenkcharacter, but this is just a demo program. The application can be 3295c609719bSwdenkcontrolled by the following keys: 3296c609719bSwdenk 3297c609719bSwdenk ? - print current values og the CPM Timer registers 3298c609719bSwdenk b - enable interrupts and start timer 3299c609719bSwdenk e - stop timer and disable interrupts 3300c609719bSwdenk q - quit application 3301c609719bSwdenk 3302c609719bSwdenk => loads 3303c609719bSwdenk ## Ready for S-Record download ... 3304c609719bSwdenk ~>examples/timer.srec 3305c609719bSwdenk 1 2 3 4 5 6 7 8 9 10 11 ... 3306c609719bSwdenk [file transfer complete] 3307c609719bSwdenk [connected] 3308c609719bSwdenk ## Start Addr = 0x00040004 3309c609719bSwdenk 3310c609719bSwdenk => go 40004 3311c609719bSwdenk ## Starting application at 0x00040004 ... 3312c609719bSwdenk TIMERS=0xfff00980 3313c609719bSwdenk Using timer 1 3314c609719bSwdenk tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0 3315c609719bSwdenk 3316c609719bSwdenkHit 'b': 3317c609719bSwdenk [q, b, e, ?] Set interval 1000000 us 3318c609719bSwdenk Enabling timer 3319c609719bSwdenkHit '?': 3320c609719bSwdenk [q, b, e, ?] ........ 3321c609719bSwdenk tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0 3322c609719bSwdenkHit '?': 3323c609719bSwdenk [q, b, e, ?] . 3324c609719bSwdenk tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0 3325c609719bSwdenkHit '?': 3326c609719bSwdenk [q, b, e, ?] . 3327c609719bSwdenk tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0 3328c609719bSwdenkHit '?': 3329c609719bSwdenk [q, b, e, ?] . 3330c609719bSwdenk tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0 3331c609719bSwdenkHit 'e': 3332c609719bSwdenk [q, b, e, ?] ...Stopping timer 3333c609719bSwdenkHit 'q': 3334c609719bSwdenk [q, b, e, ?] ## Application terminated, rc = 0x0 3335c609719bSwdenk 3336c609719bSwdenk 333785ec0bccSwdenkMinicom warning: 333885ec0bccSwdenk================ 333985ec0bccSwdenk 33407152b1d0SwdenkOver time, many people have reported problems when trying to use the 334185ec0bccSwdenk"minicom" terminal emulation program for serial download. I (wd) 334285ec0bccSwdenkconsider minicom to be broken, and recommend not to use it. Under 3343f07771ccSwdenkUnix, I recommend to use C-Kermit for general purpose use (and 334485ec0bccSwdenkespecially for kermit binary protocol download ("loadb" command), and 334585ec0bccSwdenkuse "cu" for S-Record download ("loads" command). 334685ec0bccSwdenk 334752f52c14SwdenkNevertheless, if you absolutely want to use it try adding this 334852f52c14Swdenkconfiguration to your "File transfer protocols" section: 334952f52c14Swdenk 335052f52c14Swdenk Name Program Name U/D FullScr IO-Red. Multi 335152f52c14Swdenk X kermit /usr/bin/kermit -i -l %l -s Y U Y N N 335252f52c14Swdenk Y kermit /usr/bin/kermit -i -l %l -r N D Y N N 335352f52c14Swdenk 335452f52c14Swdenk 3355c609719bSwdenkNetBSD Notes: 3356c609719bSwdenk============= 3357c609719bSwdenk 3358c609719bSwdenkStarting at version 0.9.2, U-Boot supports NetBSD both as host 3359c609719bSwdenk(build U-Boot) and target system (boots NetBSD/mpc8xx). 3360c609719bSwdenk 3361c609719bSwdenkBuilding requires a cross environment; it is known to work on 3362c609719bSwdenkNetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also 3363c609719bSwdenkneed gmake since the Makefiles are not compatible with BSD make). 3364c609719bSwdenkNote that the cross-powerpc package does not install include files; 3365c609719bSwdenkattempting to build U-Boot will fail because <machine/ansi.h> is 3366c609719bSwdenkmissing. This file has to be installed and patched manually: 3367c609719bSwdenk 3368c609719bSwdenk # cd /usr/pkg/cross/powerpc-netbsd/include 3369c609719bSwdenk # mkdir powerpc 3370c609719bSwdenk # ln -s powerpc machine 3371c609719bSwdenk # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h 3372c609719bSwdenk # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST 3373c609719bSwdenk 3374c609719bSwdenkNative builds *don't* work due to incompatibilities between native 3375c609719bSwdenkand U-Boot include files. 3376c609719bSwdenk 3377c609719bSwdenkBooting assumes that (the first part of) the image booted is a 3378c609719bSwdenkstage-2 loader which in turn loads and then invokes the kernel 3379c609719bSwdenkproper. Loader sources will eventually appear in the NetBSD source 3380c609719bSwdenktree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the 33812a8af187Swdenkmeantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz 3382c609719bSwdenk 3383c609719bSwdenk 3384c609719bSwdenkImplementation Internals: 3385c609719bSwdenk========================= 3386c609719bSwdenk 3387c609719bSwdenkThe following is not intended to be a complete description of every 3388c609719bSwdenkimplementation detail. However, it should help to understand the 3389c609719bSwdenkinner workings of U-Boot and make it easier to port it to custom 3390c609719bSwdenkhardware. 3391c609719bSwdenk 3392c609719bSwdenk 3393c609719bSwdenkInitial Stack, Global Data: 3394c609719bSwdenk--------------------------- 3395c609719bSwdenk 3396c609719bSwdenkThe implementation of U-Boot is complicated by the fact that U-Boot 3397c609719bSwdenkstarts running out of ROM (flash memory), usually without access to 3398c609719bSwdenksystem RAM (because the memory controller is not initialized yet). 3399c609719bSwdenkThis means that we don't have writable Data or BSS segments, and BSS 3400c609719bSwdenkis not initialized as zero. To be able to get a C environment working 3401c609719bSwdenkat all, we have to allocate at least a minimal stack. Implementation 3402c609719bSwdenkoptions for this are defined and restricted by the CPU used: Some CPU 3403c609719bSwdenkmodels provide on-chip memory (like the IMMR area on MPC8xx and 3404c609719bSwdenkMPC826x processors), on others (parts of) the data cache can be 3405c609719bSwdenklocked as (mis-) used as memory, etc. 3406c609719bSwdenk 34077152b1d0Swdenk Chris Hallinan posted a good summary of these issues to the 340843d9616cSwdenk u-boot-users mailing list: 340943d9616cSwdenk 341043d9616cSwdenk Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)? 341143d9616cSwdenk From: "Chris Hallinan" <clh@net1plus.com> 341243d9616cSwdenk Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET) 341343d9616cSwdenk ... 341443d9616cSwdenk 341543d9616cSwdenk Correct me if I'm wrong, folks, but the way I understand it 341643d9616cSwdenk is this: Using DCACHE as initial RAM for Stack, etc, does not 341743d9616cSwdenk require any physical RAM backing up the cache. The cleverness 341843d9616cSwdenk is that the cache is being used as a temporary supply of 341943d9616cSwdenk necessary storage before the SDRAM controller is setup. It's 342043d9616cSwdenk beyond the scope of this list to expain the details, but you 342143d9616cSwdenk can see how this works by studying the cache architecture and 342243d9616cSwdenk operation in the architecture and processor-specific manuals. 342343d9616cSwdenk 342443d9616cSwdenk OCM is On Chip Memory, which I believe the 405GP has 4K. It 342543d9616cSwdenk is another option for the system designer to use as an 342643d9616cSwdenk initial stack/ram area prior to SDRAM being available. Either 342743d9616cSwdenk option should work for you. Using CS 4 should be fine if your 342843d9616cSwdenk board designers haven't used it for something that would 342943d9616cSwdenk cause you grief during the initial boot! It is frequently not 343043d9616cSwdenk used. 343143d9616cSwdenk 343243d9616cSwdenk CFG_INIT_RAM_ADDR should be somewhere that won't interfere 343343d9616cSwdenk with your processor/board/system design. The default value 343443d9616cSwdenk you will find in any recent u-boot distribution in 34358a316c9bSStefan Roese walnut.h should work for you. I'd set it to a value larger 343643d9616cSwdenk than your SDRAM module. If you have a 64MB SDRAM module, set 343743d9616cSwdenk it above 400_0000. Just make sure your board has no resources 343843d9616cSwdenk that are supposed to respond to that address! That code in 343943d9616cSwdenk start.S has been around a while and should work as is when 344043d9616cSwdenk you get the config right. 344143d9616cSwdenk 344243d9616cSwdenk -Chris Hallinan 344343d9616cSwdenk DS4.COM, Inc. 344443d9616cSwdenk 3445c609719bSwdenkIt is essential to remember this, since it has some impact on the C 3446c609719bSwdenkcode for the initialization procedures: 3447c609719bSwdenk 3448c609719bSwdenk* Initialized global data (data segment) is read-only. Do not attempt 3449c609719bSwdenk to write it. 3450c609719bSwdenk 3451c609719bSwdenk* Do not use any unitialized global data (or implicitely initialized 3452c609719bSwdenk as zero data - BSS segment) at all - this is undefined, initiali- 34537152b1d0Swdenk zation is performed later (when relocating to RAM). 3454c609719bSwdenk 3455c609719bSwdenk* Stack space is very limited. Avoid big data buffers or things like 3456c609719bSwdenk that. 3457c609719bSwdenk 3458c609719bSwdenkHaving only the stack as writable memory limits means we cannot use 3459c609719bSwdenknormal global data to share information beween the code. But it 3460c609719bSwdenkturned out that the implementation of U-Boot can be greatly 3461c609719bSwdenksimplified by making a global data structure (gd_t) available to all 3462c609719bSwdenkfunctions. We could pass a pointer to this data as argument to _all_ 3463c609719bSwdenkfunctions, but this would bloat the code. Instead we use a feature of 3464c609719bSwdenkthe GCC compiler (Global Register Variables) to share the data: we 3465c609719bSwdenkplace a pointer (gd) to the global data into a register which we 3466c609719bSwdenkreserve for this purpose. 3467c609719bSwdenk 34687152b1d0SwdenkWhen choosing a register for such a purpose we are restricted by the 3469c609719bSwdenkrelevant (E)ABI specifications for the current architecture, and by 3470c609719bSwdenkGCC's implementation. 3471c609719bSwdenk 3472c609719bSwdenkFor PowerPC, the following registers have specific use: 3473c609719bSwdenk R1: stack pointer 3474c609719bSwdenk R2: TOC pointer 3475c609719bSwdenk R3-R4: parameter passing and return values 3476c609719bSwdenk R5-R10: parameter passing 3477c609719bSwdenk R13: small data area pointer 3478c609719bSwdenk R30: GOT pointer 3479c609719bSwdenk R31: frame pointer 3480c609719bSwdenk 3481c609719bSwdenk (U-Boot also uses R14 as internal GOT pointer.) 3482c609719bSwdenk 3483c609719bSwdenk ==> U-Boot will use R29 to hold a pointer to the global data 3484c609719bSwdenk 3485c609719bSwdenk Note: on PPC, we could use a static initializer (since the 3486c609719bSwdenk address of the global data structure is known at compile time), 3487c609719bSwdenk but it turned out that reserving a register results in somewhat 3488c609719bSwdenk smaller code - although the code savings are not that big (on 3489c609719bSwdenk average for all boards 752 bytes for the whole U-Boot image, 3490c609719bSwdenk 624 text + 127 data). 3491c609719bSwdenk 3492c609719bSwdenkOn ARM, the following registers are used: 3493c609719bSwdenk 3494c609719bSwdenk R0: function argument word/integer result 3495c609719bSwdenk R1-R3: function argument word 3496c609719bSwdenk R9: GOT pointer 3497c609719bSwdenk R10: stack limit (used only if stack checking if enabled) 3498c609719bSwdenk R11: argument (frame) pointer 3499c609719bSwdenk R12: temporary workspace 3500c609719bSwdenk R13: stack pointer 3501c609719bSwdenk R14: link register 3502c609719bSwdenk R15: program counter 3503c609719bSwdenk 3504c609719bSwdenk ==> U-Boot will use R8 to hold a pointer to the global data 3505c609719bSwdenk 3506d87080b7SWolfgang DenkNOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope, 3507d87080b7SWolfgang Denkor current versions of GCC may "optimize" the code too much. 3508c609719bSwdenk 3509c609719bSwdenkMemory Management: 3510c609719bSwdenk------------------ 3511c609719bSwdenk 3512c609719bSwdenkU-Boot runs in system state and uses physical addresses, i.e. the 3513c609719bSwdenkMMU is not used either for address mapping nor for memory protection. 3514c609719bSwdenk 3515c609719bSwdenkThe available memory is mapped to fixed addresses using the memory 3516c609719bSwdenkcontroller. In this process, a contiguous block is formed for each 3517c609719bSwdenkmemory type (Flash, SDRAM, SRAM), even when it consists of several 3518c609719bSwdenkphysical memory banks. 3519c609719bSwdenk 3520c609719bSwdenkU-Boot is installed in the first 128 kB of the first Flash bank (on 3521c609719bSwdenkTQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After 3522c609719bSwdenkbooting and sizing and initializing DRAM, the code relocates itself 3523c609719bSwdenkto the upper end of DRAM. Immediately below the U-Boot code some 3524c609719bSwdenkmemory is reserved for use by malloc() [see CFG_MALLOC_LEN 3525c609719bSwdenkconfiguration setting]. Below that, a structure with global Board 3526c609719bSwdenkInfo data is placed, followed by the stack (growing downward). 3527c609719bSwdenk 3528c609719bSwdenkAdditionally, some exception handler code is copied to the low 8 kB 3529c609719bSwdenkof DRAM (0x00000000 ... 0x00001FFF). 3530c609719bSwdenk 3531c609719bSwdenkSo a typical memory configuration with 16 MB of DRAM could look like 3532c609719bSwdenkthis: 3533c609719bSwdenk 3534c609719bSwdenk 0x0000 0000 Exception Vector code 3535c609719bSwdenk : 3536c609719bSwdenk 0x0000 1FFF 3537c609719bSwdenk 0x0000 2000 Free for Application Use 3538c609719bSwdenk : 3539c609719bSwdenk : 3540c609719bSwdenk 3541c609719bSwdenk : 3542c609719bSwdenk : 3543c609719bSwdenk 0x00FB FF20 Monitor Stack (Growing downward) 3544c609719bSwdenk 0x00FB FFAC Board Info Data and permanent copy of global data 3545c609719bSwdenk 0x00FC 0000 Malloc Arena 3546c609719bSwdenk : 3547c609719bSwdenk 0x00FD FFFF 3548c609719bSwdenk 0x00FE 0000 RAM Copy of Monitor Code 3549c609719bSwdenk ... eventually: LCD or video framebuffer 3550c609719bSwdenk ... eventually: pRAM (Protected RAM - unchanged by reset) 3551c609719bSwdenk 0x00FF FFFF [End of RAM] 3552c609719bSwdenk 3553c609719bSwdenk 3554c609719bSwdenkSystem Initialization: 3555c609719bSwdenk---------------------- 3556c609719bSwdenk 3557c609719bSwdenkIn the reset configuration, U-Boot starts at the reset entry point 3558c609719bSwdenk(on most PowerPC systens at address 0x00000100). Because of the reset 3559c609719bSwdenkconfiguration for CS0# this is a mirror of the onboard Flash memory. 35607152b1d0SwdenkTo be able to re-map memory U-Boot then jumps to its link address. 3561c609719bSwdenkTo be able to implement the initialization code in C, a (small!) 3562c609719bSwdenkinitial stack is set up in the internal Dual Ported RAM (in case CPUs 3563c609719bSwdenkwhich provide such a feature like MPC8xx or MPC8260), or in a locked 3564c609719bSwdenkpart of the data cache. After that, U-Boot initializes the CPU core, 3565c609719bSwdenkthe caches and the SIU. 3566c609719bSwdenk 3567c609719bSwdenkNext, all (potentially) available memory banks are mapped using a 3568c609719bSwdenkpreliminary mapping. For example, we put them on 512 MB boundaries 3569c609719bSwdenk(multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash 3570c609719bSwdenkon 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is 3571c609719bSwdenkprogrammed for SDRAM access. Using the temporary configuration, a 3572c609719bSwdenksimple memory test is run that determines the size of the SDRAM 3573c609719bSwdenkbanks. 3574c609719bSwdenk 3575c609719bSwdenkWhen there is more than one SDRAM bank, and the banks are of 35767152b1d0Swdenkdifferent size, the largest is mapped first. For equal size, the first 3577c609719bSwdenkbank (CS2#) is mapped first. The first mapping is always for address 3578c609719bSwdenk0x00000000, with any additional banks following immediately to create 3579c609719bSwdenkcontiguous memory starting from 0. 3580c609719bSwdenk 3581c609719bSwdenkThen, the monitor installs itself at the upper end of the SDRAM area 3582c609719bSwdenkand allocates memory for use by malloc() and for the global Board 3583c609719bSwdenkInfo data; also, the exception vector code is copied to the low RAM 3584c609719bSwdenkpages, and the final stack is set up. 3585c609719bSwdenk 3586c609719bSwdenkOnly after this relocation will you have a "normal" C environment; 3587c609719bSwdenkuntil that you are restricted in several ways, mostly because you are 3588c609719bSwdenkrunning from ROM, and because the code will have to be relocated to a 3589c609719bSwdenknew address in RAM. 3590c609719bSwdenk 3591c609719bSwdenk 3592c609719bSwdenkU-Boot Porting Guide: 3593c609719bSwdenk---------------------- 3594c609719bSwdenk 3595c609719bSwdenk[Based on messages by Jerry Van Baren in the U-Boot-Users mailing 35966aff3115Swdenklist, October 2002] 3597c609719bSwdenk 3598c609719bSwdenk 3599c609719bSwdenkint main (int argc, char *argv[]) 3600c609719bSwdenk{ 3601c609719bSwdenk sighandler_t no_more_time; 3602c609719bSwdenk 3603c609719bSwdenk signal (SIGALRM, no_more_time); 3604c609719bSwdenk alarm (PROJECT_DEADLINE - toSec (3 * WEEK)); 3605c609719bSwdenk 3606c609719bSwdenk if (available_money > available_manpower) { 3607c609719bSwdenk pay consultant to port U-Boot; 3608c609719bSwdenk return 0; 3609c609719bSwdenk } 3610c609719bSwdenk 3611c609719bSwdenk Download latest U-Boot source; 3612c609719bSwdenk 36136aff3115Swdenk Subscribe to u-boot-users mailing list; 36146aff3115Swdenk 3615c609719bSwdenk if (clueless) { 3616c609719bSwdenk email ("Hi, I am new to U-Boot, how do I get started?"); 3617c609719bSwdenk } 3618c609719bSwdenk 3619c609719bSwdenk while (learning) { 3620c609719bSwdenk Read the README file in the top level directory; 36217cb22f97Swdenk Read http://www.denx.de/twiki/bin/view/DULG/Manual ; 3622c609719bSwdenk Read the source, Luke; 3623c609719bSwdenk } 3624c609719bSwdenk 3625c609719bSwdenk if (available_money > toLocalCurrency ($2500)) { 3626c609719bSwdenk Buy a BDI2000; 3627c609719bSwdenk } else { 3628c609719bSwdenk Add a lot of aggravation and time; 3629c609719bSwdenk } 3630c609719bSwdenk 3631c609719bSwdenk Create your own board support subdirectory; 3632c609719bSwdenk 36336aff3115Swdenk Create your own board config file; 36346aff3115Swdenk 3635c609719bSwdenk while (!running) { 3636c609719bSwdenk do { 3637c609719bSwdenk Add / modify source code; 3638c609719bSwdenk } until (compiles); 3639c609719bSwdenk Debug; 3640c609719bSwdenk if (clueless) 3641c609719bSwdenk email ("Hi, I am having problems..."); 3642c609719bSwdenk } 3643c609719bSwdenk Send patch file to Wolfgang; 3644c609719bSwdenk 3645c609719bSwdenk return 0; 3646c609719bSwdenk} 3647c609719bSwdenk 3648c609719bSwdenkvoid no_more_time (int sig) 3649c609719bSwdenk{ 3650c609719bSwdenk hire_a_guru(); 3651c609719bSwdenk} 3652c609719bSwdenk 3653c609719bSwdenk 3654c609719bSwdenkCoding Standards: 3655c609719bSwdenk----------------- 3656c609719bSwdenk 3657c609719bSwdenkAll contributions to U-Boot should conform to the Linux kernel 36582c051651SDetlev Zundelcoding style; see the file "Documentation/CodingStyle" and the script 36592c051651SDetlev Zundel"scripts/Lindent" in your Linux kernel source directory. In sources 36602c051651SDetlev Zundeloriginating from U-Boot a style corresponding to "Lindent -pcs" (adding 36612c051651SDetlev Zundelspaces before parameters to function calls) is actually used. 3662c609719bSwdenk 36632c051651SDetlev ZundelSource files originating from a different project (for example the 36642c051651SDetlev ZundelMTD subsystem) are generally exempt from these guidelines and are not 36652c051651SDetlev Zundelreformated to ease subsequent migration to newer versions of those 36662c051651SDetlev Zundelsources. 36672c051651SDetlev Zundel 36682c051651SDetlev ZundelPlease note that U-Boot is implemented in C (and to some small parts in 36692c051651SDetlev ZundelAssembler); no C++ is used, so please do not use C++ style comments (//) 36702c051651SDetlev Zundelin your code. 3671c609719bSwdenk 3672c178d3daSwdenkPlease also stick to the following formatting rules: 3673180d3f74Swdenk- remove any trailing white space 3674180d3f74Swdenk- use TAB characters for indentation, not spaces 3675180d3f74Swdenk- make sure NOT to use DOS '\r\n' line feeds 3676180d3f74Swdenk- do not add more than 2 empty lines to source files 3677180d3f74Swdenk- do not add trailing empty lines to source files 3678180d3f74Swdenk 3679c609719bSwdenkSubmissions which do not conform to the standards may be returned 3680c609719bSwdenkwith a request to reformat the changes. 3681c609719bSwdenk 3682c609719bSwdenk 3683c609719bSwdenkSubmitting Patches: 3684c609719bSwdenk------------------- 3685c609719bSwdenk 3686c609719bSwdenkSince the number of patches for U-Boot is growing, we need to 3687c609719bSwdenkestablish some rules. Submissions which do not conform to these rules 3688c609719bSwdenkmay be rejected, even when they contain important and valuable stuff. 3689c609719bSwdenk 369090dc6704SwdenkPatches shall be sent to the u-boot-users mailing list. 3691c609719bSwdenk 3692c609719bSwdenkWhen you send a patch, please include the following information with 3693c609719bSwdenkit: 3694c609719bSwdenk 3695c609719bSwdenk* For bug fixes: a description of the bug and how your patch fixes 3696c609719bSwdenk this bug. Please try to include a way of demonstrating that the 3697c609719bSwdenk patch actually fixes something. 3698c609719bSwdenk 3699c609719bSwdenk* For new features: a description of the feature and your 3700c609719bSwdenk implementation. 3701c609719bSwdenk 3702c609719bSwdenk* A CHANGELOG entry as plaintext (separate from the patch) 3703c609719bSwdenk 3704c609719bSwdenk* For major contributions, your entry to the CREDITS file 3705c609719bSwdenk 3706c609719bSwdenk* When you add support for a new board, don't forget to add this 3707c609719bSwdenk board to the MAKEALL script, too. 3708c609719bSwdenk 3709c609719bSwdenk* If your patch adds new configuration options, don't forget to 3710c609719bSwdenk document these in the README file. 3711c609719bSwdenk 3712c609719bSwdenk* The patch itself. If you are accessing the CVS repository use "cvs 3713c609719bSwdenk update; cvs diff -puRN"; else, use "diff -purN OLD NEW". If your 3714c609719bSwdenk version of diff does not support these options, then get the latest 3715c609719bSwdenk version of GNU diff. 3716c609719bSwdenk 37176dff5529Swdenk The current directory when running this command shall be the top 37186dff5529Swdenk level directory of the U-Boot source tree, or it's parent directory 37196dff5529Swdenk (i. e. please make sure that your patch includes sufficient 37206dff5529Swdenk directory information for the affected files). 37216dff5529Swdenk 3722c609719bSwdenk We accept patches as plain text, MIME attachments or as uuencoded 3723c609719bSwdenk gzipped text. 3724c609719bSwdenk 372552f52c14Swdenk* If one logical set of modifications affects or creates several 372652f52c14Swdenk files, all these changes shall be submitted in a SINGLE patch file. 372752f52c14Swdenk 372852f52c14Swdenk* Changesets that contain different, unrelated modifications shall be 372952f52c14Swdenk submitted as SEPARATE patches, one patch per changeset. 373052f52c14Swdenk 373152f52c14Swdenk 3732c609719bSwdenkNotes: 3733c609719bSwdenk 3734c609719bSwdenk* Before sending the patch, run the MAKEALL script on your patched 3735c609719bSwdenk source tree and make sure that no errors or warnings are reported 3736c609719bSwdenk for any of the boards. 3737c609719bSwdenk 3738c609719bSwdenk* Keep your modifications to the necessary minimum: A patch 3739c609719bSwdenk containing several unrelated changes or arbitrary reformats will be 3740c609719bSwdenk returned with a request to re-formatting / split it. 3741c609719bSwdenk 3742c609719bSwdenk* If you modify existing code, make sure that your new code does not 3743c609719bSwdenk add to the memory footprint of the code ;-) Small is beautiful! 3744c609719bSwdenk When adding new features, these should compile conditionally only 3745c609719bSwdenk (using #ifdef), and the resulting code with the new feature 3746c609719bSwdenk disabled must not need more memory than the old code without your 3747c609719bSwdenk modification. 374890dc6704Swdenk 374990dc6704Swdenk* Remember that there is a size limit of 40 kB per message on the 375090dc6704Swdenk u-boot-users mailing list. Compression may help. 3751