2 # (C) Copyright 2000 - 2013
3 # Wolfgang Denk, DENX Software Engineering, wd@denx.de.
5 # SPDX-License-Identifier: GPL-2.0+
11 This directory contains the source code for U-Boot, a boot loader for
12 Embedded boards based on PowerPC, ARM, MIPS and several other
13 processors, which can be installed in a boot ROM and used to
14 initialize and test the hardware or to download and run application
17 The development of U-Boot is closely related to Linux: some parts of
18 the source code originate in the Linux source tree, we have some
19 header files in common, and special provision has been made to
20 support booting of Linux images.
22 Some attention has been paid to make this software easily
23 configurable and extendable. For instance, all monitor commands are
24 implemented with the same call interface, so that it's very easy to
25 add new commands. Also, instead of permanently adding rarely used
26 code (for instance hardware test utilities) to the monitor, you can
27 load and run it dynamically.
33 In general, all boards for which a configuration option exists in the
34 Makefile have been tested to some extent and can be considered
35 "working". In fact, many of them are used in production systems.
37 In case of problems see the CHANGELOG and CREDITS files to find out
38 who contributed the specific port. The boards.cfg file lists board
41 Note: There is no CHANGELOG file in the actual U-Boot source tree;
42 it can be created dynamically from the Git log using:
50 In case you have questions about, problems with or contributions for
51 U-Boot you should send a message to the U-Boot mailing list at
52 <u-boot@lists.denx.de>. There is also an archive of previous traffic
53 on the mailing list - please search the archive before asking FAQ's.
54 Please see http://lists.denx.de/pipermail/u-boot and
55 http://dir.gmane.org/gmane.comp.boot-loaders.u-boot
58 Where to get source code:
59 =========================
61 The U-Boot source code is maintained in the git repository at
62 git://www.denx.de/git/u-boot.git ; you can browse it online at
63 http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary
65 The "snapshot" links on this page allow you to download tarballs of
66 any version you might be interested in. Official releases are also
67 available for FTP download from the ftp://ftp.denx.de/pub/u-boot/
70 Pre-built (and tested) images are available from
71 ftp://ftp.denx.de/pub/u-boot/images/
77 - start from 8xxrom sources
78 - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
80 - make it easier to add custom boards
81 - make it possible to add other [PowerPC] CPUs
82 - extend functions, especially:
83 * Provide extended interface to Linux boot loader
86 * PCMCIA / CompactFlash / ATA disk / SCSI ... boot
87 - create ARMBoot project (http://sourceforge.net/projects/armboot)
88 - add other CPU families (starting with ARM)
89 - create U-Boot project (http://sourceforge.net/projects/u-boot)
90 - current project page: see http://www.denx.de/wiki/U-Boot
96 The "official" name of this project is "Das U-Boot". The spelling
97 "U-Boot" shall be used in all written text (documentation, comments
98 in source files etc.). Example:
100 This is the README file for the U-Boot project.
102 File names etc. shall be based on the string "u-boot". Examples:
104 include/asm-ppc/u-boot.h
106 #include <asm/u-boot.h>
108 Variable names, preprocessor constants etc. shall be either based on
109 the string "u_boot" or on "U_BOOT". Example:
111 U_BOOT_VERSION u_boot_logo
112 IH_OS_U_BOOT u_boot_hush_start
118 Starting with the release in October 2008, the names of the releases
119 were changed from numerical release numbers without deeper meaning
120 into a time stamp based numbering. Regular releases are identified by
121 names consisting of the calendar year and month of the release date.
122 Additional fields (if present) indicate release candidates or bug fix
123 releases in "stable" maintenance trees.
126 U-Boot v2009.11 - Release November 2009
127 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree
128 U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release
134 /arch Architecture specific files
135 /arm Files generic to ARM architecture
136 /cpu CPU specific files
137 /arm720t Files specific to ARM 720 CPUs
138 /arm920t Files specific to ARM 920 CPUs
139 /at91 Files specific to Atmel AT91RM9200 CPU
140 /imx Files specific to Freescale MC9328 i.MX CPUs
141 /s3c24x0 Files specific to Samsung S3C24X0 CPUs
142 /arm926ejs Files specific to ARM 926 CPUs
143 /arm1136 Files specific to ARM 1136 CPUs
144 /ixp Files specific to Intel XScale IXP CPUs
145 /pxa Files specific to Intel XScale PXA CPUs
146 /sa1100 Files specific to Intel StrongARM SA1100 CPUs
147 /lib Architecture specific library files
148 /avr32 Files generic to AVR32 architecture
149 /cpu CPU specific files
150 /lib Architecture specific library files
151 /blackfin Files generic to Analog Devices Blackfin architecture
152 /cpu CPU specific files
153 /lib Architecture specific library files
154 /m68k Files generic to m68k architecture
155 /cpu CPU specific files
156 /mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
157 /mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs
158 /mcf532x Files specific to Freescale ColdFire MCF5329 CPUs
159 /mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs
160 /mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs
161 /lib Architecture specific library files
162 /microblaze Files generic to microblaze architecture
163 /cpu CPU specific files
164 /lib Architecture specific library files
165 /mips Files generic to MIPS architecture
166 /cpu CPU specific files
167 /mips32 Files specific to MIPS32 CPUs
168 /xburst Files specific to Ingenic XBurst CPUs
169 /lib Architecture specific library files
170 /nds32 Files generic to NDS32 architecture
171 /cpu CPU specific files
172 /n1213 Files specific to Andes Technology N1213 CPUs
173 /lib Architecture specific library files
174 /nios2 Files generic to Altera NIOS2 architecture
175 /cpu CPU specific files
176 /lib Architecture specific library files
177 /openrisc Files generic to OpenRISC architecture
178 /cpu CPU specific files
179 /lib Architecture specific library files
180 /powerpc Files generic to PowerPC architecture
181 /cpu CPU specific files
182 /74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
183 /mpc5xx Files specific to Freescale MPC5xx CPUs
184 /mpc5xxx Files specific to Freescale MPC5xxx CPUs
185 /mpc8xx Files specific to Freescale MPC8xx CPUs
186 /mpc824x Files specific to Freescale MPC824x CPUs
187 /mpc8260 Files specific to Freescale MPC8260 CPUs
188 /mpc85xx Files specific to Freescale MPC85xx CPUs
189 /ppc4xx Files specific to AMCC PowerPC 4xx CPUs
190 /lib Architecture specific library files
191 /sh Files generic to SH architecture
192 /cpu CPU specific files
193 /sh2 Files specific to sh2 CPUs
194 /sh3 Files specific to sh3 CPUs
195 /sh4 Files specific to sh4 CPUs
196 /lib Architecture specific library files
197 /sparc Files generic to SPARC architecture
198 /cpu CPU specific files
199 /leon2 Files specific to Gaisler LEON2 SPARC CPU
200 /leon3 Files specific to Gaisler LEON3 SPARC CPU
201 /lib Architecture specific library files
202 /x86 Files generic to x86 architecture
203 /cpu CPU specific files
204 /lib Architecture specific library files
205 /api Machine/arch independent API for external apps
206 /board Board dependent files
207 /common Misc architecture independent functions
208 /disk Code for disk drive partition handling
209 /doc Documentation (don't expect too much)
210 /drivers Commonly used device drivers
211 /dts Contains Makefile for building internal U-Boot fdt.
212 /examples Example code for standalone applications, etc.
213 /fs Filesystem code (cramfs, ext2, jffs2, etc.)
214 /include Header Files
215 /lib Files generic to all architectures
216 /libfdt Library files to support flattened device trees
217 /lzma Library files to support LZMA decompression
218 /lzo Library files to support LZO decompression
220 /post Power On Self Test
221 /spl Secondary Program Loader framework
222 /tools Tools to build S-Record or U-Boot images, etc.
224 Software Configuration:
225 =======================
227 Configuration is usually done using C preprocessor defines; the
228 rationale behind that is to avoid dead code whenever possible.
230 There are two classes of configuration variables:
232 * Configuration _OPTIONS_:
233 These are selectable by the user and have names beginning with
236 * Configuration _SETTINGS_:
237 These depend on the hardware etc. and should not be meddled with if
238 you don't know what you're doing; they have names beginning with
241 Later we will add a configuration tool - probably similar to or even
242 identical to what's used for the Linux kernel. Right now, we have to
243 do the configuration by hand, which means creating some symbolic
244 links and editing some configuration files. We use the TQM8xxL boards
248 Selection of Processor Architecture and Board Type:
249 ---------------------------------------------------
251 For all supported boards there are ready-to-use default
252 configurations available; just type "make <board_name>_config".
254 Example: For a TQM823L module type:
259 For the Cogent platform, you need to specify the CPU type as well;
260 e.g. "make cogent_mpc8xx_config". And also configure the cogent
261 directory according to the instructions in cogent/README.
264 Configuration Options:
265 ----------------------
267 Configuration depends on the combination of board and CPU type; all
268 such information is kept in a configuration file
269 "include/configs/<board_name>.h".
271 Example: For a TQM823L module, all configuration settings are in
272 "include/configs/TQM823L.h".
275 Many of the options are named exactly as the corresponding Linux
276 kernel configuration options. The intention is to make it easier to
277 build a config tool - later.
280 The following options need to be configured:
282 - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
284 - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
286 - CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)
287 Define exactly one, e.g. CONFIG_ATSTK1002
289 - CPU Module Type: (if CONFIG_COGENT is defined)
290 Define exactly one of
292 --- FIXME --- not tested yet:
293 CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
294 CONFIG_CMA287_23, CONFIG_CMA287_50
296 - Motherboard Type: (if CONFIG_COGENT is defined)
297 Define exactly one of
298 CONFIG_CMA101, CONFIG_CMA102
300 - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
301 Define one or more of
304 - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
305 Define one or more of
306 CONFIG_LCD_HEARTBEAT - update a character position on
307 the LCD display every second with
310 - Board flavour: (if CONFIG_MPC8260ADS is defined)
313 CONFIG_SYS_8260ADS - original MPC8260ADS
314 CONFIG_SYS_8266ADS - MPC8266ADS
315 CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
316 CONFIG_SYS_8272ADS - MPC8272ADS
318 - Marvell Family Member
319 CONFIG_SYS_MVFS - define it if you want to enable
320 multiple fs option at one time
321 for marvell soc family
323 - MPC824X Family Member (if CONFIG_MPC824X is defined)
324 Define exactly one of
325 CONFIG_MPC8240, CONFIG_MPC8245
327 - 8xx CPU Options: (if using an MPC8xx CPU)
328 CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
329 get_gclk_freq() cannot work
330 e.g. if there is no 32KHz
331 reference PIT/RTC clock
332 CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
335 - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
336 CONFIG_SYS_8xx_CPUCLK_MIN
337 CONFIG_SYS_8xx_CPUCLK_MAX
338 CONFIG_8xx_CPUCLK_DEFAULT
339 See doc/README.MPC866
341 CONFIG_SYS_MEASURE_CPUCLK
343 Define this to measure the actual CPU clock instead
344 of relying on the correctness of the configured
345 values. Mostly useful for board bringup to make sure
346 the PLL is locked at the intended frequency. Note
347 that this requires a (stable) reference clock (32 kHz
348 RTC clock or CONFIG_SYS_8XX_XIN)
350 CONFIG_SYS_DELAYED_ICACHE
352 Define this option if you want to enable the
353 ICache only when Code runs from RAM.
358 Specifies that the core is a 64-bit PowerPC implementation (implements
359 the "64" category of the Power ISA). This is necessary for ePAPR
360 compliance, among other possible reasons.
362 CONFIG_SYS_FSL_TBCLK_DIV
364 Defines the core time base clock divider ratio compared to the
365 system clock. On most PQ3 devices this is 8, on newer QorIQ
366 devices it can be 16 or 32. The ratio varies from SoC to Soc.
368 CONFIG_SYS_FSL_PCIE_COMPAT
370 Defines the string to utilize when trying to match PCIe device
371 tree nodes for the given platform.
373 CONFIG_SYS_PPC_E500_DEBUG_TLB
375 Enables a temporary TLB entry to be used during boot to work
376 around limitations in e500v1 and e500v2 external debugger
377 support. This reduces the portions of the boot code where
378 breakpoints and single stepping do not work. The value of this
379 symbol should be set to the TLB1 entry to be used for this
382 CONFIG_SYS_FSL_ERRATUM_A004510
384 Enables a workaround for erratum A004510. If set,
385 then CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and
386 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set.
388 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV
389 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional)
391 Defines one or two SoC revisions (low 8 bits of SVR)
392 for which the A004510 workaround should be applied.
394 The rest of SVR is either not relevant to the decision
395 of whether the erratum is present (e.g. p2040 versus
396 p2041) or is implied by the build target, which controls
397 whether CONFIG_SYS_FSL_ERRATUM_A004510 is set.
399 See Freescale App Note 4493 for more information about
402 CONFIG_A003399_NOR_WORKAROUND
403 Enables a workaround for IFC erratum A003399. It is only
404 requred during NOR boot.
406 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY
408 This is the value to write into CCSR offset 0x18600
409 according to the A004510 workaround.
411 CONFIG_SYS_FSL_DSP_DDR_ADDR
412 This value denotes start offset of DDR memory which is
413 connected exclusively to the DSP cores.
415 CONFIG_SYS_FSL_DSP_M2_RAM_ADDR
416 This value denotes start offset of M2 memory
417 which is directly connected to the DSP core.
419 CONFIG_SYS_FSL_DSP_M3_RAM_ADDR
420 This value denotes start offset of M3 memory which is directly
421 connected to the DSP core.
423 CONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT
424 This value denotes start offset of DSP CCSR space.
426 CONFIG_SYS_FSL_DDR_EMU
427 Specify emulator support for DDR. Some DDR features such as
428 deskew training are not available.
430 - Generic CPU options:
431 CONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN
433 Defines the endianess of the CPU. Implementation of those
434 values is arch specific.
436 - Intel Monahans options:
437 CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO
439 Defines the Monahans run mode to oscillator
440 ratio. Valid values are 8, 16, 24, 31. The core
441 frequency is this value multiplied by 13 MHz.
443 CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO
445 Defines the Monahans turbo mode to oscillator
446 ratio. Valid values are 1 (default if undefined) and
447 2. The core frequency as calculated above is multiplied
451 CONFIG_SYS_INIT_SP_OFFSET
453 Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack
454 pointer. This is needed for the temporary stack before
457 CONFIG_SYS_MIPS_CACHE_MODE
459 Cache operation mode for the MIPS CPU.
460 See also arch/mips/include/asm/mipsregs.h.
462 CONF_CM_CACHABLE_NO_WA
465 CONF_CM_CACHABLE_NONCOHERENT
469 CONF_CM_CACHABLE_ACCELERATED
471 CONFIG_SYS_XWAY_EBU_BOOTCFG
473 Special option for Lantiq XWAY SoCs for booting from NOR flash.
474 See also arch/mips/cpu/mips32/start.S.
476 CONFIG_XWAY_SWAP_BYTES
478 Enable compilation of tools/xway-swap-bytes needed for Lantiq
479 XWAY SoCs for booting from NOR flash. The U-Boot image needs to
480 be swapped if a flash programmer is used.
483 CONFIG_SYS_EXCEPTION_VECTORS_HIGH
485 Select high exception vectors of the ARM core, e.g., do not
486 clear the V bit of the c1 register of CP15.
488 CONFIG_SYS_THUMB_BUILD
490 Use this flag to build U-Boot using the Thumb instruction
491 set for ARM architectures. Thumb instruction set provides
492 better code density. For ARM architectures that support
493 Thumb2 this flag will result in Thumb2 code generated by
496 CONFIG_ARM_ERRATA_716044
497 CONFIG_ARM_ERRATA_742230
498 CONFIG_ARM_ERRATA_743622
499 CONFIG_ARM_ERRATA_751472
501 If set, the workarounds for these ARM errata are applied early
502 during U-Boot startup. Note that these options force the
503 workarounds to be applied; no CPU-type/version detection
504 exists, unlike the similar options in the Linux kernel. Do not
505 set these options unless they apply!
510 The frequency of the timer returned by get_timer().
511 get_timer() must operate in milliseconds and this CONFIG
512 option must be set to 1000.
514 - Linux Kernel Interface:
517 U-Boot stores all clock information in Hz
518 internally. For binary compatibility with older Linux
519 kernels (which expect the clocks passed in the
520 bd_info data to be in MHz) the environment variable
521 "clocks_in_mhz" can be defined so that U-Boot
522 converts clock data to MHZ before passing it to the
524 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
525 "clocks_in_mhz=1" is automatically included in the
528 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
530 When transferring memsize parameter to linux, some versions
531 expect it to be in bytes, others in MB.
532 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
536 New kernel versions are expecting firmware settings to be
537 passed using flattened device trees (based on open firmware
541 * New libfdt-based support
542 * Adds the "fdt" command
543 * The bootm command automatically updates the fdt
545 OF_CPU - The proper name of the cpus node (only required for
546 MPC512X and MPC5xxx based boards).
547 OF_SOC - The proper name of the soc node (only required for
548 MPC512X and MPC5xxx based boards).
549 OF_TBCLK - The timebase frequency.
550 OF_STDOUT_PATH - The path to the console device
552 boards with QUICC Engines require OF_QE to set UCC MAC
555 CONFIG_OF_BOARD_SETUP
557 Board code has addition modification that it wants to make
558 to the flat device tree before handing it off to the kernel
562 This define fills in the correct boot CPU in the boot
563 param header, the default value is zero if undefined.
567 U-Boot can detect if an IDE device is present or not.
568 If not, and this new config option is activated, U-Boot
569 removes the ATA node from the DTS before booting Linux,
570 so the Linux IDE driver does not probe the device and
571 crash. This is needed for buggy hardware (uc101) where
572 no pull down resistor is connected to the signal IDE5V_DD7.
574 CONFIG_MACH_TYPE [relevant for ARM only][mandatory]
576 This setting is mandatory for all boards that have only one
577 machine type and must be used to specify the machine type
578 number as it appears in the ARM machine registry
579 (see http://www.arm.linux.org.uk/developer/machines/).
580 Only boards that have multiple machine types supported
581 in a single configuration file and the machine type is
582 runtime discoverable, do not have to use this setting.
584 - vxWorks boot parameters:
586 bootvx constructs a valid bootline using the following
587 environments variables: bootfile, ipaddr, serverip, hostname.
588 It loads the vxWorks image pointed bootfile.
590 CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name
591 CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address
592 CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server
593 CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters
595 CONFIG_SYS_VXWORKS_ADD_PARAMS
597 Add it at the end of the bootline. E.g "u=username pw=secret"
599 Note: If a "bootargs" environment is defined, it will overwride
600 the defaults discussed just above.
602 - Cache Configuration:
603 CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot
604 CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot
605 CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
607 - Cache Configuration for ARM:
608 CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache
610 CONFIG_SYS_PL310_BASE - Physical base address of PL310
611 controller register space
616 Define this if you want support for Amba PrimeCell PL010 UARTs.
620 Define this if you want support for Amba PrimeCell PL011 UARTs.
624 If you have Amba PrimeCell PL011 UARTs, set this variable to
625 the clock speed of the UARTs.
629 If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
630 define this to a list of base addresses for each (supported)
631 port. See e.g. include/configs/versatile.h
633 CONFIG_PL011_SERIAL_RLCR
635 Some vendor versions of PL011 serial ports (e.g. ST-Ericsson U8500)
636 have separate receive and transmit line control registers. Set
637 this variable to initialize the extra register.
639 CONFIG_PL011_SERIAL_FLUSH_ON_INIT
641 On some platforms (e.g. U8500) U-Boot is loaded by a second stage
642 boot loader that has already initialized the UART. Define this
643 variable to flush the UART at init time.
647 Depending on board, define exactly one serial port
648 (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
649 CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
650 console by defining CONFIG_8xx_CONS_NONE
652 Note: if CONFIG_8xx_CONS_NONE is defined, the serial
653 port routines must be defined elsewhere
654 (i.e. serial_init(), serial_getc(), ...)
657 Enables console device for a color framebuffer. Needs following
658 defines (cf. smiLynxEM, i8042)
659 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
661 VIDEO_HW_RECTFILL graphic chip supports
664 VIDEO_HW_BITBLT graphic chip supports
665 bit-blit (cf. smiLynxEM)
666 VIDEO_VISIBLE_COLS visible pixel columns
668 VIDEO_VISIBLE_ROWS visible pixel rows
669 VIDEO_PIXEL_SIZE bytes per pixel
670 VIDEO_DATA_FORMAT graphic data format
671 (0-5, cf. cfb_console.c)
672 VIDEO_FB_ADRS framebuffer address
673 VIDEO_KBD_INIT_FCT keyboard int fct
674 (i.e. i8042_kbd_init())
675 VIDEO_TSTC_FCT test char fct
677 VIDEO_GETC_FCT get char fct
679 CONFIG_CONSOLE_CURSOR cursor drawing on/off
680 (requires blink timer
682 CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
683 CONFIG_CONSOLE_TIME display time/date info in
685 (requires CONFIG_CMD_DATE)
686 CONFIG_VIDEO_LOGO display Linux logo in
688 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
689 linux_logo.h for logo.
690 Requires CONFIG_VIDEO_LOGO
691 CONFIG_CONSOLE_EXTRA_INFO
692 additional board info beside
695 When CONFIG_CFB_CONSOLE_ANSI is defined, console will support
696 a limited number of ANSI escape sequences (cursor control,
697 erase functions and limited graphics rendition control).
699 When CONFIG_CFB_CONSOLE is defined, video console is
700 default i/o. Serial console can be forced with
701 environment 'console=serial'.
703 When CONFIG_SILENT_CONSOLE is defined, all console
704 messages (by U-Boot and Linux!) can be silenced with
705 the "silent" environment variable. See
706 doc/README.silent for more information.
708 CONFIG_SYS_CONSOLE_BG_COL: define the backgroundcolor, default
710 CONFIG_SYS_CONSOLE_FG_COL: define the foregroundcolor, default
714 CONFIG_BAUDRATE - in bps
715 Select one of the baudrates listed in
716 CONFIG_SYS_BAUDRATE_TABLE, see below.
717 CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale
719 - Console Rx buffer length
720 With CONFIG_SYS_SMC_RXBUFLEN it is possible to define
721 the maximum receive buffer length for the SMC.
722 This option is actual only for 82xx and 8xx possible.
723 If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE
724 must be defined, to setup the maximum idle timeout for
727 - Pre-Console Buffer:
728 Prior to the console being initialised (i.e. serial UART
729 initialised etc) all console output is silently discarded.
730 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
731 buffer any console messages prior to the console being
732 initialised to a buffer of size CONFIG_PRE_CON_BUF_SZ
733 bytes located at CONFIG_PRE_CON_BUF_ADDR. The buffer is
734 a circular buffer, so if more than CONFIG_PRE_CON_BUF_SZ
735 bytes are output before the console is initialised, the
736 earlier bytes are discarded.
738 'Sane' compilers will generate smaller code if
739 CONFIG_PRE_CON_BUF_SZ is a power of 2
741 - Safe printf() functions
742 Define CONFIG_SYS_VSNPRINTF to compile in safe versions of
743 the printf() functions. These are defined in
744 include/vsprintf.h and include snprintf(), vsnprintf() and
745 so on. Code size increase is approximately 300-500 bytes.
746 If this option is not given then these functions will
747 silently discard their buffer size argument - this means
748 you are not getting any overflow checking in this case.
750 - Boot Delay: CONFIG_BOOTDELAY - in seconds
751 Delay before automatically booting the default image;
752 set to -1 to disable autoboot.
753 set to -2 to autoboot with no delay and not check for abort
754 (even when CONFIG_ZERO_BOOTDELAY_CHECK is defined).
756 See doc/README.autoboot for these options that
757 work with CONFIG_BOOTDELAY. None are required.
758 CONFIG_BOOT_RETRY_TIME
759 CONFIG_BOOT_RETRY_MIN
760 CONFIG_AUTOBOOT_KEYED
761 CONFIG_AUTOBOOT_PROMPT
762 CONFIG_AUTOBOOT_DELAY_STR
763 CONFIG_AUTOBOOT_STOP_STR
764 CONFIG_AUTOBOOT_DELAY_STR2
765 CONFIG_AUTOBOOT_STOP_STR2
766 CONFIG_ZERO_BOOTDELAY_CHECK
767 CONFIG_RESET_TO_RETRY
771 Only needed when CONFIG_BOOTDELAY is enabled;
772 define a command string that is automatically executed
773 when no character is read on the console interface
774 within "Boot Delay" after reset.
777 This can be used to pass arguments to the bootm
778 command. The value of CONFIG_BOOTARGS goes into the
779 environment value "bootargs".
781 CONFIG_RAMBOOT and CONFIG_NFSBOOT
782 The value of these goes into the environment as
783 "ramboot" and "nfsboot" respectively, and can be used
784 as a convenience, when switching between booting from
790 When this option is #defined, the existence of the
791 environment variable "preboot" will be checked
792 immediately before starting the CONFIG_BOOTDELAY
793 countdown and/or running the auto-boot command resp.
794 entering interactive mode.
796 This feature is especially useful when "preboot" is
797 automatically generated or modified. For an example
798 see the LWMON board specific code: here "preboot" is
799 modified when the user holds down a certain
800 combination of keys on the (special) keyboard when
803 - Serial Download Echo Mode:
805 If defined to 1, all characters received during a
806 serial download (using the "loads" command) are
807 echoed back. This might be needed by some terminal
808 emulations (like "cu"), but may as well just take
809 time on others. This setting #define's the initial
810 value of the "loads_echo" environment variable.
812 - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
814 Select one of the baudrates listed in
815 CONFIG_SYS_BAUDRATE_TABLE, see below.
818 Monitor commands can be included or excluded
819 from the build by using the #include files
820 <config_cmd_all.h> and #undef'ing unwanted
821 commands, or using <config_cmd_default.h>
822 and augmenting with additional #define's
825 The default command configuration includes all commands
826 except those marked below with a "*".
828 CONFIG_CMD_ASKENV * ask for env variable
829 CONFIG_CMD_BDI bdinfo
830 CONFIG_CMD_BEDBUG * Include BedBug Debugger
831 CONFIG_CMD_BMP * BMP support
832 CONFIG_CMD_BSP * Board specific commands
833 CONFIG_CMD_BOOTD bootd
834 CONFIG_CMD_CACHE * icache, dcache
835 CONFIG_CMD_CONSOLE coninfo
836 CONFIG_CMD_CRC32 * crc32
837 CONFIG_CMD_DATE * support for RTC, date/time...
838 CONFIG_CMD_DHCP * DHCP support
839 CONFIG_CMD_DIAG * Diagnostics
840 CONFIG_CMD_DS4510 * ds4510 I2C gpio commands
841 CONFIG_CMD_DS4510_INFO * ds4510 I2C info command
842 CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd
843 CONFIG_CMD_DS4510_RST * ds4510 I2C rst command
844 CONFIG_CMD_DTT * Digital Therm and Thermostat
845 CONFIG_CMD_ECHO echo arguments
846 CONFIG_CMD_EDITENV edit env variable
847 CONFIG_CMD_EEPROM * EEPROM read/write support
848 CONFIG_CMD_ELF * bootelf, bootvx
849 CONFIG_CMD_ENV_CALLBACK * display details about env callbacks
850 CONFIG_CMD_ENV_FLAGS * display details about env flags
851 CONFIG_CMD_EXPORTENV * export the environment
852 CONFIG_CMD_EXT2 * ext2 command support
853 CONFIG_CMD_EXT4 * ext4 command support
854 CONFIG_CMD_SAVEENV saveenv
855 CONFIG_CMD_FDC * Floppy Disk Support
856 CONFIG_CMD_FAT * FAT command support
857 CONFIG_CMD_FDOS * Dos diskette Support
858 CONFIG_CMD_FLASH flinfo, erase, protect
859 CONFIG_CMD_FPGA FPGA device initialization support
860 CONFIG_CMD_FUSE * Device fuse support
861 CONFIG_CMD_GETTIME * Get time since boot
862 CONFIG_CMD_GO * the 'go' command (exec code)
863 CONFIG_CMD_GREPENV * search environment
864 CONFIG_CMD_HASH * calculate hash / digest
865 CONFIG_CMD_HWFLOW * RTS/CTS hw flow control
866 CONFIG_CMD_I2C * I2C serial bus support
867 CONFIG_CMD_IDE * IDE harddisk support
868 CONFIG_CMD_IMI iminfo
869 CONFIG_CMD_IMLS List all images found in NOR flash
870 CONFIG_CMD_IMLS_NAND * List all images found in NAND flash
871 CONFIG_CMD_IMMAP * IMMR dump support
872 CONFIG_CMD_IMPORTENV * import an environment
873 CONFIG_CMD_INI * import data from an ini file into the env
874 CONFIG_CMD_IRQ * irqinfo
875 CONFIG_CMD_ITEST Integer/string test of 2 values
876 CONFIG_CMD_JFFS2 * JFFS2 Support
877 CONFIG_CMD_KGDB * kgdb
878 CONFIG_CMD_LDRINFO * ldrinfo (display Blackfin loader)
879 CONFIG_CMD_LINK_LOCAL * link-local IP address auto-configuration
881 CONFIG_CMD_LOADB loadb
882 CONFIG_CMD_LOADS loads
883 CONFIG_CMD_MD5SUM * print md5 message digest
884 (requires CONFIG_CMD_MEMORY and CONFIG_MD5)
885 CONFIG_CMD_MEMINFO * Display detailed memory information
886 CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
888 CONFIG_CMD_MEMTEST * mtest
889 CONFIG_CMD_MISC Misc functions like sleep etc
890 CONFIG_CMD_MMC * MMC memory mapped support
891 CONFIG_CMD_MII * MII utility commands
892 CONFIG_CMD_MTDPARTS * MTD partition support
893 CONFIG_CMD_NAND * NAND support
894 CONFIG_CMD_NET bootp, tftpboot, rarpboot
895 CONFIG_CMD_NFS NFS support
896 CONFIG_CMD_PCA953X * PCA953x I2C gpio commands
897 CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command
898 CONFIG_CMD_PCI * pciinfo
899 CONFIG_CMD_PCMCIA * PCMCIA support
900 CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network
902 CONFIG_CMD_PORTIO * Port I/O
903 CONFIG_CMD_READ * Read raw data from partition
904 CONFIG_CMD_REGINFO * Register dump
905 CONFIG_CMD_RUN run command in env variable
906 CONFIG_CMD_SANDBOX * sb command to access sandbox features
907 CONFIG_CMD_SAVES * save S record dump
908 CONFIG_CMD_SCSI * SCSI Support
909 CONFIG_CMD_SDRAM * print SDRAM configuration information
910 (requires CONFIG_CMD_I2C)
911 CONFIG_CMD_SETGETDCR Support for DCR Register access
913 CONFIG_CMD_SF * Read/write/erase SPI NOR flash
914 CONFIG_CMD_SHA1SUM * print sha1 memory digest
915 (requires CONFIG_CMD_MEMORY)
916 CONFIG_CMD_SOFTSWITCH * Soft switch setting command for BF60x
917 CONFIG_CMD_SOURCE "source" command Support
918 CONFIG_CMD_SPI * SPI serial bus support
919 CONFIG_CMD_TFTPSRV * TFTP transfer in server mode
920 CONFIG_CMD_TFTPPUT * TFTP put command (upload)
921 CONFIG_CMD_TIME * run command and report execution time (ARM specific)
922 CONFIG_CMD_TIMER * access to the system tick timer
923 CONFIG_CMD_USB * USB support
924 CONFIG_CMD_CDP * Cisco Discover Protocol support
925 CONFIG_CMD_MFSL * Microblaze FSL support
926 CONFIG_CMD_XIMG Load part of Multi Image
929 EXAMPLE: If you want all functions except of network
930 support you can write:
932 #include "config_cmd_all.h"
933 #undef CONFIG_CMD_NET
936 fdt (flattened device tree) command: CONFIG_OF_LIBFDT
938 Note: Don't enable the "icache" and "dcache" commands
939 (configuration option CONFIG_CMD_CACHE) unless you know
940 what you (and your U-Boot users) are doing. Data
941 cache cannot be enabled on systems like the 8xx or
942 8260 (where accesses to the IMMR region must be
943 uncached), and it cannot be disabled on all other
944 systems where we (mis-) use the data cache to hold an
945 initial stack and some data.
948 XXX - this list needs to get updated!
950 - Regular expression support:
952 If this variable is defined, U-Boot is linked against
953 the SLRE (Super Light Regular Expression) library,
954 which adds regex support to some commands, as for
955 example "env grep" and "setexpr".
959 If this variable is defined, U-Boot will use a device tree
960 to configure its devices, instead of relying on statically
961 compiled #defines in the board file. This option is
962 experimental and only available on a few boards. The device
963 tree is available in the global data as gd->fdt_blob.
965 U-Boot needs to get its device tree from somewhere. This can
966 be done using one of the two options below:
969 If this variable is defined, U-Boot will embed a device tree
970 binary in its image. This device tree file should be in the
971 board directory and called <soc>-<board>.dts. The binary file
972 is then picked up in board_init_f() and made available through
973 the global data structure as gd->blob.
976 If this variable is defined, U-Boot will build a device tree
977 binary. It will be called u-boot.dtb. Architecture-specific
978 code will locate it at run-time. Generally this works by:
980 cat u-boot.bin u-boot.dtb >image.bin
982 and in fact, U-Boot does this for you, creating a file called
983 u-boot-dtb.bin which is useful in the common case. You can
984 still use the individual files if you need something more
989 If this variable is defined, it enables watchdog
990 support for the SoC. There must be support in the SoC
991 specific code for a watchdog. For the 8xx and 8260
992 CPUs, the SIU Watchdog feature is enabled in the SYPCR
993 register. When supported for a specific SoC is
994 available, then no further board specific code should
998 When using a watchdog circuitry external to the used
999 SoC, then define this variable and provide board
1000 specific code for the "hw_watchdog_reset" function.
1003 CONFIG_VERSION_VARIABLE
1004 If this variable is defined, an environment variable
1005 named "ver" is created by U-Boot showing the U-Boot
1006 version as printed by the "version" command.
1007 Any change to this variable will be reverted at the
1012 When CONFIG_CMD_DATE is selected, the type of the RTC
1013 has to be selected, too. Define exactly one of the
1016 CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
1017 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
1018 CONFIG_RTC_MC13XXX - use MC13783 or MC13892 RTC
1019 CONFIG_RTC_MC146818 - use MC146818 RTC
1020 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
1021 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
1022 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
1023 CONFIG_RTC_DS164x - use Dallas DS164x RTC
1024 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
1025 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
1026 CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337
1027 CONFIG_SYS_RV3029_TCR - enable trickle charger on
1030 Note that if the RTC uses I2C, then the I2C interface
1031 must also be configured. See I2C Support, below.
1034 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO
1035 CONFIG_PCA953X_INFO - enable pca953x info command
1037 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
1038 chip-ngpio pairs that tell the PCA953X driver the number of
1039 pins supported by a particular chip.
1041 Note that if the GPIO device uses I2C, then the I2C interface
1042 must also be configured. See I2C Support, below.
1044 - Timestamp Support:
1046 When CONFIG_TIMESTAMP is selected, the timestamp
1047 (date and time) of an image is printed by image
1048 commands like bootm or iminfo. This option is
1049 automatically enabled when you select CONFIG_CMD_DATE .
1051 - Partition Labels (disklabels) Supported:
1052 Zero or more of the following:
1053 CONFIG_MAC_PARTITION Apple's MacOS partition table.
1054 CONFIG_DOS_PARTITION MS Dos partition table, traditional on the
1055 Intel architecture, USB sticks, etc.
1056 CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc.
1057 CONFIG_EFI_PARTITION GPT partition table, common when EFI is the
1058 bootloader. Note 2TB partition limit; see
1060 CONFIG_MTD_PARTITIONS Memory Technology Device partition table.
1062 If IDE or SCSI support is enabled (CONFIG_CMD_IDE or
1063 CONFIG_CMD_SCSI) you must configure support for at
1064 least one non-MTD partition type as well.
1067 CONFIG_IDE_RESET_ROUTINE - this is defined in several
1068 board configurations files but used nowhere!
1070 CONFIG_IDE_RESET - is this is defined, IDE Reset will
1071 be performed by calling the function
1072 ide_set_reset(int reset)
1073 which has to be defined in a board specific file
1078 Set this to enable ATAPI support.
1083 Set this to enable support for disks larger than 137GB
1084 Also look at CONFIG_SYS_64BIT_LBA.
1085 Whithout these , LBA48 support uses 32bit variables and will 'only'
1086 support disks up to 2.1TB.
1088 CONFIG_SYS_64BIT_LBA:
1089 When enabled, makes the IDE subsystem use 64bit sector addresses.
1093 At the moment only there is only support for the
1094 SYM53C8XX SCSI controller; define
1095 CONFIG_SCSI_SYM53C8XX to enable it.
1097 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
1098 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
1099 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
1100 maximum numbers of LUNs, SCSI ID's and target
1102 CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
1104 The environment variable 'scsidevs' is set to the number of
1105 SCSI devices found during the last scan.
1107 - NETWORK Support (PCI):
1109 Support for Intel 8254x/8257x gigabit chips.
1112 Utility code for direct access to the SPI bus on Intel 8257x.
1113 This does not do anything useful unless you set at least one
1114 of CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC.
1116 CONFIG_E1000_SPI_GENERIC
1117 Allow generic access to the SPI bus on the Intel 8257x, for
1118 example with the "sspi" command.
1121 Management command for E1000 devices. When used on devices
1122 with SPI support you can reprogram the EEPROM from U-Boot.
1124 CONFIG_E1000_FALLBACK_MAC
1125 default MAC for empty EEPROM after production.
1128 Support for Intel 82557/82559/82559ER chips.
1129 Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM
1130 write routine for first time initialisation.
1133 Support for Digital 2114x chips.
1134 Optional CONFIG_TULIP_SELECT_MEDIA for board specific
1135 modem chip initialisation (KS8761/QS6611).
1138 Support for National dp83815 chips.
1141 Support for National dp8382[01] gigabit chips.
1143 - NETWORK Support (other):
1145 CONFIG_DRIVER_AT91EMAC
1146 Support for AT91RM9200 EMAC.
1149 Define this to use reduced MII inteface
1151 CONFIG_DRIVER_AT91EMAC_QUIET
1152 If this defined, the driver is quiet.
1153 The driver doen't show link status messages.
1155 CONFIG_CALXEDA_XGMAC
1156 Support for the Calxeda XGMAC device
1159 Support for SMSC's LAN91C96 chips.
1161 CONFIG_LAN91C96_BASE
1162 Define this to hold the physical address
1163 of the LAN91C96's I/O space
1165 CONFIG_LAN91C96_USE_32_BIT
1166 Define this to enable 32 bit addressing
1169 Support for SMSC's LAN91C111 chip
1171 CONFIG_SMC91111_BASE
1172 Define this to hold the physical address
1173 of the device (I/O space)
1175 CONFIG_SMC_USE_32_BIT
1176 Define this if data bus is 32 bits
1178 CONFIG_SMC_USE_IOFUNCS
1179 Define this to use i/o functions instead of macros
1180 (some hardware wont work with macros)
1182 CONFIG_DRIVER_TI_EMAC
1183 Support for davinci emac
1185 CONFIG_SYS_DAVINCI_EMAC_PHY_COUNT
1186 Define this if you have more then 3 PHYs.
1189 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
1191 CONFIG_FTGMAC100_EGIGA
1192 Define this to use GE link update with gigabit PHY.
1193 Define this if FTGMAC100 is connected to gigabit PHY.
1194 If your system has 10/100 PHY only, it might not occur
1195 wrong behavior. Because PHY usually return timeout or
1196 useless data when polling gigabit status and gigabit
1197 control registers. This behavior won't affect the
1198 correctnessof 10/100 link speed update.
1201 Support for SMSC's LAN911x and LAN921x chips
1204 Define this to hold the physical address
1205 of the device (I/O space)
1207 CONFIG_SMC911X_32_BIT
1208 Define this if data bus is 32 bits
1210 CONFIG_SMC911X_16_BIT
1211 Define this if data bus is 16 bits. If your processor
1212 automatically converts one 32 bit word to two 16 bit
1213 words you may also try CONFIG_SMC911X_32_BIT.
1216 Support for Renesas on-chip Ethernet controller
1218 CONFIG_SH_ETHER_USE_PORT
1219 Define the number of ports to be used
1221 CONFIG_SH_ETHER_PHY_ADDR
1222 Define the ETH PHY's address
1224 CONFIG_SH_ETHER_CACHE_WRITEBACK
1225 If this option is set, the driver enables cache flush.
1229 Support TPM devices.
1232 Support for i2c bus TPM devices. Only one device
1233 per system is supported at this time.
1235 CONFIG_TPM_TIS_I2C_BUS_NUMBER
1236 Define the the i2c bus number for the TPM device
1238 CONFIG_TPM_TIS_I2C_SLAVE_ADDRESS
1239 Define the TPM's address on the i2c bus
1241 CONFIG_TPM_TIS_I2C_BURST_LIMITATION
1242 Define the burst count bytes upper limit
1244 CONFIG_TPM_ATMEL_TWI
1245 Support for Atmel TWI TPM device. Requires I2C support.
1248 Support for generic parallel port TPM devices. Only one device
1249 per system is supported at this time.
1251 CONFIG_TPM_TIS_BASE_ADDRESS
1252 Base address where the generic TPM device is mapped
1253 to. Contemporary x86 systems usually map it at
1257 Add tpm monitor functions.
1258 Requires CONFIG_TPM. If CONFIG_TPM_AUTH_SESSIONS is set, also
1259 provides monitor access to authorized functions.
1262 Define this to enable the TPM support library which provides
1263 functional interfaces to some TPM commands.
1264 Requires support for a TPM device.
1266 CONFIG_TPM_AUTH_SESSIONS
1267 Define this to enable authorized functions in the TPM library.
1268 Requires CONFIG_TPM and CONFIG_SHA1.
1271 At the moment only the UHCI host controller is
1272 supported (PIP405, MIP405, MPC5200); define
1273 CONFIG_USB_UHCI to enable it.
1274 define CONFIG_USB_KEYBOARD to enable the USB Keyboard
1275 and define CONFIG_USB_STORAGE to enable the USB
1278 Supported are USB Keyboards and USB Floppy drives
1280 MPC5200 USB requires additional defines:
1282 for 528 MHz Clock: 0x0001bbbb
1286 for differential drivers: 0x00001000
1287 for single ended drivers: 0x00005000
1288 for differential drivers on PSC3: 0x00000100
1289 for single ended drivers on PSC3: 0x00004100
1290 CONFIG_SYS_USB_EVENT_POLL
1291 May be defined to allow interrupt polling
1292 instead of using asynchronous interrupts
1294 CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the
1295 txfilltuning field in the EHCI controller on reset.
1297 CONFIG_USB_HUB_MIN_POWER_ON_DELAY defines the minimum
1298 interval for usb hub power-on delay.(minimum 100msec)
1301 Define the below if you wish to use the USB console.
1302 Once firmware is rebuilt from a serial console issue the
1303 command "setenv stdin usbtty; setenv stdout usbtty" and
1304 attach your USB cable. The Unix command "dmesg" should print
1305 it has found a new device. The environment variable usbtty
1306 can be set to gserial or cdc_acm to enable your device to
1307 appear to a USB host as a Linux gserial device or a
1308 Common Device Class Abstract Control Model serial device.
1309 If you select usbtty = gserial you should be able to enumerate
1311 # modprobe usbserial vendor=0xVendorID product=0xProductID
1312 else if using cdc_acm, simply setting the environment
1313 variable usbtty to be cdc_acm should suffice. The following
1314 might be defined in YourBoardName.h
1317 Define this to build a UDC device
1320 Define this to have a tty type of device available to
1321 talk to the UDC device
1324 Define this to enable the high speed support for usb
1325 device and usbtty. If this feature is enabled, a routine
1326 int is_usbd_high_speed(void)
1327 also needs to be defined by the driver to dynamically poll
1328 whether the enumeration has succeded at high speed or full
1331 CONFIG_SYS_CONSOLE_IS_IN_ENV
1332 Define this if you want stdin, stdout &/or stderr to
1336 CONFIG_SYS_USB_EXTC_CLK 0xBLAH
1337 Derive USB clock from external clock "blah"
1338 - CONFIG_SYS_USB_EXTC_CLK 0x02
1340 CONFIG_SYS_USB_BRG_CLK 0xBLAH
1341 Derive USB clock from brgclk
1342 - CONFIG_SYS_USB_BRG_CLK 0x04
1344 If you have a USB-IF assigned VendorID then you may wish to
1345 define your own vendor specific values either in BoardName.h
1346 or directly in usbd_vendor_info.h. If you don't define
1347 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
1348 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
1349 should pretend to be a Linux device to it's target host.
1351 CONFIG_USBD_MANUFACTURER
1352 Define this string as the name of your company for
1353 - CONFIG_USBD_MANUFACTURER "my company"
1355 CONFIG_USBD_PRODUCT_NAME
1356 Define this string as the name of your product
1357 - CONFIG_USBD_PRODUCT_NAME "acme usb device"
1359 CONFIG_USBD_VENDORID
1360 Define this as your assigned Vendor ID from the USB
1361 Implementors Forum. This *must* be a genuine Vendor ID
1362 to avoid polluting the USB namespace.
1363 - CONFIG_USBD_VENDORID 0xFFFF
1365 CONFIG_USBD_PRODUCTID
1366 Define this as the unique Product ID
1368 - CONFIG_USBD_PRODUCTID 0xFFFF
1370 Some USB device drivers may need to check USB cable attachment.
1371 In this case you can enable following config in BoardName.h:
1372 CONFIG_USB_CABLE_CHECK
1373 This enables function definition:
1374 - usb_cable_connected() in include/usb.h
1375 Implementation of this function is board-specific.
1377 - ULPI Layer Support:
1378 The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via
1379 the generic ULPI layer. The generic layer accesses the ULPI PHY
1380 via the platform viewport, so you need both the genric layer and
1381 the viewport enabled. Currently only Chipidea/ARC based
1382 viewport is supported.
1383 To enable the ULPI layer support, define CONFIG_USB_ULPI and
1384 CONFIG_USB_ULPI_VIEWPORT in your board configuration file.
1385 If your ULPI phy needs a different reference clock than the
1386 standard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to
1387 the appropriate value in Hz.
1390 The MMC controller on the Intel PXA is supported. To
1391 enable this define CONFIG_MMC. The MMC can be
1392 accessed from the boot prompt by mapping the device
1393 to physical memory similar to flash. Command line is
1394 enabled with CONFIG_CMD_MMC. The MMC driver also works with
1395 the FAT fs. This is enabled with CONFIG_CMD_FAT.
1398 Support for Renesas on-chip MMCIF controller
1400 CONFIG_SH_MMCIF_ADDR
1401 Define the base address of MMCIF registers
1404 Define the clock frequency for MMCIF
1406 - USB Device Firmware Update (DFU) class support:
1408 This enables the USB portion of the DFU USB class
1411 This enables the command "dfu" which is used to have
1412 U-Boot create a DFU class device via USB. This command
1413 requires that the "dfu_alt_info" environment variable be
1414 set and define the alt settings to expose to the host.
1417 This enables support for exposing (e)MMC devices via DFU.
1420 This enables support for exposing NAND devices via DFU.
1423 This enables support for exposing RAM via DFU.
1424 Note: DFU spec refer to non-volatile memory usage, but
1425 allow usages beyond the scope of spec - here RAM usage,
1426 one that would help mostly the developer.
1428 CONFIG_SYS_DFU_DATA_BUF_SIZE
1429 Dfu transfer uses a buffer before writing data to the
1430 raw storage device. Make the size (in bytes) of this buffer
1431 configurable. The size of this buffer is also configurable
1432 through the "dfu_bufsiz" environment variable.
1434 CONFIG_SYS_DFU_MAX_FILE_SIZE
1435 When updating files rather than the raw storage device,
1436 we use a static buffer to copy the file into and then write
1437 the buffer once we've been given the whole file. Define
1438 this to the maximum filesize (in bytes) for the buffer.
1439 Default is 4 MiB if undefined.
1441 - Journaling Flash filesystem support:
1442 CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
1443 CONFIG_JFFS2_NAND_DEV
1444 Define these for a default partition on a NAND device
1446 CONFIG_SYS_JFFS2_FIRST_SECTOR,
1447 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
1448 Define these for a default partition on a NOR device
1450 CONFIG_SYS_JFFS_CUSTOM_PART
1451 Define this to create an own partition. You have to provide a
1452 function struct part_info* jffs2_part_info(int part_num)
1454 If you define only one JFFS2 partition you may also want to
1455 #define CONFIG_SYS_JFFS_SINGLE_PART 1
1456 to disable the command chpart. This is the default when you
1457 have not defined a custom partition
1459 - FAT(File Allocation Table) filesystem write function support:
1462 Define this to enable support for saving memory data as a
1463 file in FAT formatted partition.
1465 This will also enable the command "fatwrite" enabling the
1466 user to write files to FAT.
1468 CBFS (Coreboot Filesystem) support
1471 Define this to enable support for reading from a Coreboot
1472 filesystem. Available commands are cbfsinit, cbfsinfo, cbfsls
1478 Define this to enable standard (PC-Style) keyboard
1482 Standard PC keyboard driver with US (is default) and
1483 GERMAN key layout (switch via environment 'keymap=de') support.
1484 Export function i8042_kbd_init, i8042_tstc and i8042_getc
1485 for cfb_console. Supports cursor blinking.
1488 Enables a Chrome OS keyboard using the CROS_EC interface.
1489 This uses CROS_EC to communicate with a second microcontroller
1490 which provides key scans on request.
1495 Define this to enable video support (for output to
1498 CONFIG_VIDEO_CT69000
1500 Enable Chips & Technologies 69000 Video chip
1502 CONFIG_VIDEO_SMI_LYNXEM
1503 Enable Silicon Motion SMI 712/710/810 Video chip. The
1504 video output is selected via environment 'videoout'
1505 (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
1508 For the CT69000 and SMI_LYNXEM drivers, videomode is
1509 selected via environment 'videomode'. Two different ways
1511 - "videomode=num" 'num' is a standard LiLo mode numbers.
1512 Following standard modes are supported (* is default):
1514 Colors 640x480 800x600 1024x768 1152x864 1280x1024
1515 -------------+---------------------------------------------
1516 8 bits | 0x301* 0x303 0x305 0x161 0x307
1517 15 bits | 0x310 0x313 0x316 0x162 0x319
1518 16 bits | 0x311 0x314 0x317 0x163 0x31A
1519 24 bits | 0x312 0x315 0x318 ? 0x31B
1520 -------------+---------------------------------------------
1521 (i.e. setenv videomode 317; saveenv; reset;)
1523 - "videomode=bootargs" all the video parameters are parsed
1524 from the bootargs. (See drivers/video/videomodes.c)
1527 CONFIG_VIDEO_SED13806
1528 Enable Epson SED13806 driver. This driver supports 8bpp
1529 and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
1530 or CONFIG_VIDEO_SED13806_16BPP
1533 Enable the Freescale DIU video driver. Reference boards for
1534 SOCs that have a DIU should define this macro to enable DIU
1535 support, and should also define these other macros:
1541 CONFIG_VIDEO_SW_CURSOR
1542 CONFIG_VGA_AS_SINGLE_DEVICE
1544 CONFIG_VIDEO_BMP_LOGO
1546 The DIU driver will look for the 'video-mode' environment
1547 variable, and if defined, enable the DIU as a console during
1548 boot. See the documentation file README.video for a
1549 description of this variable.
1553 Enable the VGA video / BIOS for x86. The alternative if you
1554 are using coreboot is to use the coreboot frame buffer
1561 Define this to enable a custom keyboard support.
1562 This simply calls drv_keyboard_init() which must be
1563 defined in your board-specific files.
1564 The only board using this so far is RBC823.
1566 - LCD Support: CONFIG_LCD
1568 Define this to enable LCD support (for output to LCD
1569 display); also select one of the supported displays
1570 by defining one of these:
1574 HITACHI TX09D70VM1CCA, 3.5", 240x320.
1576 CONFIG_NEC_NL6448AC33:
1578 NEC NL6448AC33-18. Active, color, single scan.
1580 CONFIG_NEC_NL6448BC20
1582 NEC NL6448BC20-08. 6.5", 640x480.
1583 Active, color, single scan.
1585 CONFIG_NEC_NL6448BC33_54
1587 NEC NL6448BC33-54. 10.4", 640x480.
1588 Active, color, single scan.
1592 Sharp 320x240. Active, color, single scan.
1593 It isn't 16x9, and I am not sure what it is.
1595 CONFIG_SHARP_LQ64D341
1597 Sharp LQ64D341 display, 640x480.
1598 Active, color, single scan.
1602 HLD1045 display, 640x480.
1603 Active, color, single scan.
1607 Optrex CBL50840-2 NF-FW 99 22 M5
1609 Hitachi LMG6912RPFC-00T
1613 320x240. Black & white.
1615 Normally display is black on white background; define
1616 CONFIG_SYS_WHITE_ON_BLACK to get it inverted.
1618 CONFIG_LCD_ALIGNMENT
1620 Normally the LCD is page-aligned (tyically 4KB). If this is
1621 defined then the LCD will be aligned to this value instead.
1622 For ARM it is sometimes useful to use MMU_SECTION_SIZE
1623 here, since it is cheaper to change data cache settings on
1624 a per-section basis.
1626 CONFIG_CONSOLE_SCROLL_LINES
1628 When the console need to be scrolled, this is the number of
1629 lines to scroll by. It defaults to 1. Increasing this makes
1630 the console jump but can help speed up operation when scrolling
1635 Support drawing of RLE8-compressed bitmaps on the LCD.
1639 Enables an 'i2c edid' command which can read EDID
1640 information over I2C from an attached LCD display.
1642 - Splash Screen Support: CONFIG_SPLASH_SCREEN
1644 If this option is set, the environment is checked for
1645 a variable "splashimage". If found, the usual display
1646 of logo, copyright and system information on the LCD
1647 is suppressed and the BMP image at the address
1648 specified in "splashimage" is loaded instead. The
1649 console is redirected to the "nulldev", too. This
1650 allows for a "silent" boot where a splash screen is
1651 loaded very quickly after power-on.
1653 CONFIG_SPLASHIMAGE_GUARD
1655 If this option is set, then U-Boot will prevent the environment
1656 variable "splashimage" from being set to a problematic address
1657 (see README.displaying-bmps and README.arm-unaligned-accesses).
1658 This option is useful for targets where, due to alignment
1659 restrictions, an improperly aligned BMP image will cause a data
1660 abort. If you think you will not have problems with unaligned
1661 accesses (for example because your toolchain prevents them)
1662 there is no need to set this option.
1664 CONFIG_SPLASH_SCREEN_ALIGN
1666 If this option is set the splash image can be freely positioned
1667 on the screen. Environment variable "splashpos" specifies the
1668 position as "x,y". If a positive number is given it is used as
1669 number of pixel from left/top. If a negative number is given it
1670 is used as number of pixel from right/bottom. You can also
1671 specify 'm' for centering the image.
1674 setenv splashpos m,m
1675 => image at center of screen
1677 setenv splashpos 30,20
1678 => image at x = 30 and y = 20
1680 setenv splashpos -10,m
1681 => vertically centered image
1682 at x = dspWidth - bmpWidth - 9
1684 - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
1686 If this option is set, additionally to standard BMP
1687 images, gzipped BMP images can be displayed via the
1688 splashscreen support or the bmp command.
1690 - Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
1692 If this option is set, 8-bit RLE compressed BMP images
1693 can be displayed via the splashscreen support or the
1696 - Do compresssing for memory range:
1699 If this option is set, it would use zlib deflate method
1700 to compress the specified memory at its best effort.
1702 - Compression support:
1705 Enabled by default to support gzip compressed images.
1709 If this option is set, support for bzip2 compressed
1710 images is included. If not, only uncompressed and gzip
1711 compressed images are supported.
1713 NOTE: the bzip2 algorithm requires a lot of RAM, so
1714 the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
1719 If this option is set, support for lzma compressed
1722 Note: The LZMA algorithm adds between 2 and 4KB of code and it
1723 requires an amount of dynamic memory that is given by the
1726 (1846 + 768 << (lc + lp)) * sizeof(uint16)
1728 Where lc and lp stand for, respectively, Literal context bits
1729 and Literal pos bits.
1731 This value is upper-bounded by 14MB in the worst case. Anyway,
1732 for a ~4MB large kernel image, we have lc=3 and lp=0 for a
1733 total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is
1734 a very small buffer.
1736 Use the lzmainfo tool to determinate the lc and lp values and
1737 then calculate the amount of needed dynamic memory (ensuring
1738 the appropriate CONFIG_SYS_MALLOC_LEN value).
1742 If this option is set, support for LZO compressed images
1748 The address of PHY on MII bus.
1750 CONFIG_PHY_CLOCK_FREQ (ppc4xx)
1752 The clock frequency of the MII bus
1756 If this option is set, support for speed/duplex
1757 detection of gigabit PHY is included.
1759 CONFIG_PHY_RESET_DELAY
1761 Some PHY like Intel LXT971A need extra delay after
1762 reset before any MII register access is possible.
1763 For such PHY, set this option to the usec delay
1764 required. (minimum 300usec for LXT971A)
1766 CONFIG_PHY_CMD_DELAY (ppc4xx)
1768 Some PHY like Intel LXT971A need extra delay after
1769 command issued before MII status register can be read
1779 Define a default value for Ethernet address to use
1780 for the respective Ethernet interface, in case this
1781 is not determined automatically.
1786 Define a default value for the IP address to use for
1787 the default Ethernet interface, in case this is not
1788 determined through e.g. bootp.
1789 (Environment variable "ipaddr")
1791 - Server IP address:
1794 Defines a default value for the IP address of a TFTP
1795 server to contact when using the "tftboot" command.
1796 (Environment variable "serverip")
1798 CONFIG_KEEP_SERVERADDR
1800 Keeps the server's MAC address, in the env 'serveraddr'
1801 for passing to bootargs (like Linux's netconsole option)
1803 - Gateway IP address:
1806 Defines a default value for the IP address of the
1807 default router where packets to other networks are
1809 (Environment variable "gatewayip")
1814 Defines a default value for the subnet mask (or
1815 routing prefix) which is used to determine if an IP
1816 address belongs to the local subnet or needs to be
1817 forwarded through a router.
1818 (Environment variable "netmask")
1820 - Multicast TFTP Mode:
1823 Defines whether you want to support multicast TFTP as per
1824 rfc-2090; for example to work with atftp. Lets lots of targets
1825 tftp down the same boot image concurrently. Note: the Ethernet
1826 driver in use must provide a function: mcast() to join/leave a
1829 - BOOTP Recovery Mode:
1830 CONFIG_BOOTP_RANDOM_DELAY
1832 If you have many targets in a network that try to
1833 boot using BOOTP, you may want to avoid that all
1834 systems send out BOOTP requests at precisely the same
1835 moment (which would happen for instance at recovery
1836 from a power failure, when all systems will try to
1837 boot, thus flooding the BOOTP server. Defining
1838 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
1839 inserted before sending out BOOTP requests. The
1840 following delays are inserted then:
1842 1st BOOTP request: delay 0 ... 1 sec
1843 2nd BOOTP request: delay 0 ... 2 sec
1844 3rd BOOTP request: delay 0 ... 4 sec
1846 BOOTP requests: delay 0 ... 8 sec
1848 - DHCP Advanced Options:
1849 You can fine tune the DHCP functionality by defining
1850 CONFIG_BOOTP_* symbols:
1852 CONFIG_BOOTP_SUBNETMASK
1853 CONFIG_BOOTP_GATEWAY
1854 CONFIG_BOOTP_HOSTNAME
1855 CONFIG_BOOTP_NISDOMAIN
1856 CONFIG_BOOTP_BOOTPATH
1857 CONFIG_BOOTP_BOOTFILESIZE
1860 CONFIG_BOOTP_SEND_HOSTNAME
1861 CONFIG_BOOTP_NTPSERVER
1862 CONFIG_BOOTP_TIMEOFFSET
1863 CONFIG_BOOTP_VENDOREX
1864 CONFIG_BOOTP_MAY_FAIL
1866 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
1867 environment variable, not the BOOTP server.
1869 CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found
1870 after the configured retry count, the call will fail
1871 instead of starting over. This can be used to fail over
1872 to Link-local IP address configuration if the DHCP server
1875 CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
1876 serverip from a DHCP server, it is possible that more
1877 than one DNS serverip is offered to the client.
1878 If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1879 serverip will be stored in the additional environment
1880 variable "dnsip2". The first DNS serverip is always
1881 stored in the variable "dnsip", when CONFIG_BOOTP_DNS
1884 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
1885 to do a dynamic update of a DNS server. To do this, they
1886 need the hostname of the DHCP requester.
1887 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
1888 of the "hostname" environment variable is passed as
1889 option 12 to the DHCP server.
1891 CONFIG_BOOTP_DHCP_REQUEST_DELAY
1893 A 32bit value in microseconds for a delay between
1894 receiving a "DHCP Offer" and sending the "DHCP Request".
1895 This fixes a problem with certain DHCP servers that don't
1896 respond 100% of the time to a "DHCP request". E.g. On an
1897 AT91RM9200 processor running at 180MHz, this delay needed
1898 to be *at least* 15,000 usec before a Windows Server 2003
1899 DHCP server would reply 100% of the time. I recommend at
1900 least 50,000 usec to be safe. The alternative is to hope
1901 that one of the retries will be successful but note that
1902 the DHCP timeout and retry process takes a longer than
1905 - Link-local IP address negotiation:
1906 Negotiate with other link-local clients on the local network
1907 for an address that doesn't require explicit configuration.
1908 This is especially useful if a DHCP server cannot be guaranteed
1909 to exist in all environments that the device must operate.
1911 See doc/README.link-local for more information.
1914 CONFIG_CDP_DEVICE_ID
1916 The device id used in CDP trigger frames.
1918 CONFIG_CDP_DEVICE_ID_PREFIX
1920 A two character string which is prefixed to the MAC address
1925 A printf format string which contains the ascii name of
1926 the port. Normally is set to "eth%d" which sets
1927 eth0 for the first Ethernet, eth1 for the second etc.
1929 CONFIG_CDP_CAPABILITIES
1931 A 32bit integer which indicates the device capabilities;
1932 0x00000010 for a normal host which does not forwards.
1936 An ascii string containing the version of the software.
1940 An ascii string containing the name of the platform.
1944 A 32bit integer sent on the trigger.
1946 CONFIG_CDP_POWER_CONSUMPTION
1948 A 16bit integer containing the power consumption of the
1949 device in .1 of milliwatts.
1951 CONFIG_CDP_APPLIANCE_VLAN_TYPE
1953 A byte containing the id of the VLAN.
1955 - Status LED: CONFIG_STATUS_LED
1957 Several configurations allow to display the current
1958 status using a LED. For instance, the LED will blink
1959 fast while running U-Boot code, stop blinking as
1960 soon as a reply to a BOOTP request was received, and
1961 start blinking slow once the Linux kernel is running
1962 (supported by a status LED driver in the Linux
1963 kernel). Defining CONFIG_STATUS_LED enables this
1966 - CAN Support: CONFIG_CAN_DRIVER
1968 Defining CONFIG_CAN_DRIVER enables CAN driver support
1969 on those systems that support this (optional)
1970 feature, like the TQM8xxL modules.
1972 - I2C Support: CONFIG_SYS_I2C
1974 This enable the NEW i2c subsystem, and will allow you to use
1975 i2c commands at the u-boot command line (as long as you set
1976 CONFIG_CMD_I2C in CONFIG_COMMANDS) and communicate with i2c
1977 based realtime clock chips or other i2c devices. See
1978 common/cmd_i2c.c for a description of the command line
1981 ported i2c driver to the new framework:
1982 - drivers/i2c/soft_i2c.c:
1983 - activate first bus with CONFIG_SYS_I2C_SOFT define
1984 CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE
1985 for defining speed and slave address
1986 - activate second bus with I2C_SOFT_DECLARATIONS2 define
1987 CONFIG_SYS_I2C_SOFT_SPEED_2 and CONFIG_SYS_I2C_SOFT_SLAVE_2
1988 for defining speed and slave address
1989 - activate third bus with I2C_SOFT_DECLARATIONS3 define
1990 CONFIG_SYS_I2C_SOFT_SPEED_3 and CONFIG_SYS_I2C_SOFT_SLAVE_3
1991 for defining speed and slave address
1992 - activate fourth bus with I2C_SOFT_DECLARATIONS4 define
1993 CONFIG_SYS_I2C_SOFT_SPEED_4 and CONFIG_SYS_I2C_SOFT_SLAVE_4
1994 for defining speed and slave address
1996 - drivers/i2c/fsl_i2c.c:
1997 - activate i2c driver with CONFIG_SYS_I2C_FSL
1998 define CONFIG_SYS_FSL_I2C_OFFSET for setting the register
1999 offset CONFIG_SYS_FSL_I2C_SPEED for the i2c speed and
2000 CONFIG_SYS_FSL_I2C_SLAVE for the slave addr of the first
2002 - If your board supports a second fsl i2c bus, define
2003 CONFIG_SYS_FSL_I2C2_OFFSET for the register offset
2004 CONFIG_SYS_FSL_I2C2_SPEED for the speed and
2005 CONFIG_SYS_FSL_I2C2_SLAVE for the slave address of the
2008 - drivers/i2c/tegra_i2c.c:
2009 - activate this driver with CONFIG_SYS_I2C_TEGRA
2010 - This driver adds 4 i2c buses with a fix speed from
2011 100000 and the slave addr 0!
2013 - drivers/i2c/ppc4xx_i2c.c
2014 - activate this driver with CONFIG_SYS_I2C_PPC4XX
2015 - CONFIG_SYS_I2C_PPC4XX_CH0 activate hardware channel 0
2016 - CONFIG_SYS_I2C_PPC4XX_CH1 activate hardware channel 1
2018 - drivers/i2c/i2c_mxc.c
2019 - activate this driver with CONFIG_SYS_I2C_MXC
2020 - define speed for bus 1 with CONFIG_SYS_MXC_I2C1_SPEED
2021 - define slave for bus 1 with CONFIG_SYS_MXC_I2C1_SLAVE
2022 - define speed for bus 2 with CONFIG_SYS_MXC_I2C2_SPEED
2023 - define slave for bus 2 with CONFIG_SYS_MXC_I2C2_SLAVE
2024 - define speed for bus 3 with CONFIG_SYS_MXC_I2C3_SPEED
2025 - define slave for bus 3 with CONFIG_SYS_MXC_I2C3_SLAVE
2026 If thoses defines are not set, default value is 100000
2027 for speed, and 0 for slave.
2029 - drivers/i2c/rcar_i2c.c:
2030 - activate this driver with CONFIG_SYS_I2C_RCAR
2031 - This driver adds 4 i2c buses
2033 - CONFIG_SYS_RCAR_I2C0_BASE for setting the register channel 0
2034 - CONFIG_SYS_RCAR_I2C0_SPEED for for the speed channel 0
2035 - CONFIG_SYS_RCAR_I2C1_BASE for setting the register channel 1
2036 - CONFIG_SYS_RCAR_I2C1_SPEED for for the speed channel 1
2037 - CONFIG_SYS_RCAR_I2C2_BASE for setting the register channel 2
2038 - CONFIG_SYS_RCAR_I2C2_SPEED for for the speed channel 2
2039 - CONFIG_SYS_RCAR_I2C3_BASE for setting the register channel 3
2040 - CONFIG_SYS_RCAR_I2C3_SPEED for for the speed channel 3
2041 - CONFIF_SYS_RCAR_I2C_NUM_CONTROLLERS for number of i2c buses
2045 CONFIG_SYS_NUM_I2C_BUSES
2046 Hold the number of i2c busses you want to use. If you
2047 don't use/have i2c muxes on your i2c bus, this
2048 is equal to CONFIG_SYS_NUM_I2C_ADAPTERS, and you can
2051 CONFIG_SYS_I2C_DIRECT_BUS
2052 define this, if you don't use i2c muxes on your hardware.
2053 if CONFIG_SYS_I2C_MAX_HOPS is not defined or == 0 you can
2056 CONFIG_SYS_I2C_MAX_HOPS
2057 define how many muxes are maximal consecutively connected
2058 on one i2c bus. If you not use i2c muxes, omit this
2061 CONFIG_SYS_I2C_BUSES
2062 hold a list of busses you want to use, only used if
2063 CONFIG_SYS_I2C_DIRECT_BUS is not defined, for example
2064 a board with CONFIG_SYS_I2C_MAX_HOPS = 1 and
2065 CONFIG_SYS_NUM_I2C_BUSES = 9:
2067 CONFIG_SYS_I2C_BUSES {{0, {I2C_NULL_HOP}}, \
2068 {0, {{I2C_MUX_PCA9547, 0x70, 1}}}, \
2069 {0, {{I2C_MUX_PCA9547, 0x70, 2}}}, \
2070 {0, {{I2C_MUX_PCA9547, 0x70, 3}}}, \
2071 {0, {{I2C_MUX_PCA9547, 0x70, 4}}}, \
2072 {0, {{I2C_MUX_PCA9547, 0x70, 5}}}, \
2073 {1, {I2C_NULL_HOP}}, \
2074 {1, {{I2C_MUX_PCA9544, 0x72, 1}}}, \
2075 {1, {{I2C_MUX_PCA9544, 0x72, 2}}}, \
2079 bus 0 on adapter 0 without a mux
2080 bus 1 on adapter 0 with a PCA9547 on address 0x70 port 1
2081 bus 2 on adapter 0 with a PCA9547 on address 0x70 port 2
2082 bus 3 on adapter 0 with a PCA9547 on address 0x70 port 3
2083 bus 4 on adapter 0 with a PCA9547 on address 0x70 port 4
2084 bus 5 on adapter 0 with a PCA9547 on address 0x70 port 5
2085 bus 6 on adapter 1 without a mux
2086 bus 7 on adapter 1 with a PCA9544 on address 0x72 port 1
2087 bus 8 on adapter 1 with a PCA9544 on address 0x72 port 2
2089 If you do not have i2c muxes on your board, omit this define.
2091 - Legacy I2C Support: CONFIG_HARD_I2C
2093 NOTE: It is intended to move drivers to CONFIG_SYS_I2C which
2094 provides the following compelling advantages:
2096 - more than one i2c adapter is usable
2097 - approved multibus support
2098 - better i2c mux support
2100 ** Please consider updating your I2C driver now. **
2102 These enable legacy I2C serial bus commands. Defining
2103 CONFIG_HARD_I2C will include the appropriate I2C driver
2104 for the selected CPU.
2106 This will allow you to use i2c commands at the u-boot
2107 command line (as long as you set CONFIG_CMD_I2C in
2108 CONFIG_COMMANDS) and communicate with i2c based realtime
2109 clock chips. See common/cmd_i2c.c for a description of the
2110 command line interface.
2112 CONFIG_HARD_I2C selects a hardware I2C controller.
2114 There are several other quantities that must also be
2115 defined when you define CONFIG_HARD_I2C.
2117 In both cases you will need to define CONFIG_SYS_I2C_SPEED
2118 to be the frequency (in Hz) at which you wish your i2c bus
2119 to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie
2120 the CPU's i2c node address).
2122 Now, the u-boot i2c code for the mpc8xx
2123 (arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node
2124 and so its address should therefore be cleared to 0 (See,
2125 eg, MPC823e User's Manual p.16-473). So, set
2126 CONFIG_SYS_I2C_SLAVE to 0.
2128 CONFIG_SYS_I2C_INIT_MPC5XXX
2130 When a board is reset during an i2c bus transfer
2131 chips might think that the current transfer is still
2132 in progress. Reset the slave devices by sending start
2133 commands until the slave device responds.
2135 That's all that's required for CONFIG_HARD_I2C.
2137 If you use the software i2c interface (CONFIG_SYS_I2C_SOFT)
2138 then the following macros need to be defined (examples are
2139 from include/configs/lwmon.h):
2143 (Optional). Any commands necessary to enable the I2C
2144 controller or configure ports.
2146 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
2150 (Only for MPC8260 CPU). The I/O port to use (the code
2151 assumes both bits are on the same port). Valid values
2152 are 0..3 for ports A..D.
2156 The code necessary to make the I2C data line active
2157 (driven). If the data line is open collector, this
2160 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
2164 The code necessary to make the I2C data line tri-stated
2165 (inactive). If the data line is open collector, this
2168 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
2172 Code that returns true if the I2C data line is high,
2175 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
2179 If <bit> is true, sets the I2C data line high. If it
2180 is false, it clears it (low).
2182 eg: #define I2C_SDA(bit) \
2183 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
2184 else immr->im_cpm.cp_pbdat &= ~PB_SDA
2188 If <bit> is true, sets the I2C clock line high. If it
2189 is false, it clears it (low).
2191 eg: #define I2C_SCL(bit) \
2192 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
2193 else immr->im_cpm.cp_pbdat &= ~PB_SCL
2197 This delay is invoked four times per clock cycle so this
2198 controls the rate of data transfer. The data rate thus
2199 is 1 / (I2C_DELAY * 4). Often defined to be something
2202 #define I2C_DELAY udelay(2)
2204 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
2206 If your arch supports the generic GPIO framework (asm/gpio.h),
2207 then you may alternatively define the two GPIOs that are to be
2208 used as SCL / SDA. Any of the previous I2C_xxx macros will
2209 have GPIO-based defaults assigned to them as appropriate.
2211 You should define these to the GPIO value as given directly to
2212 the generic GPIO functions.
2214 CONFIG_SYS_I2C_INIT_BOARD
2216 When a board is reset during an i2c bus transfer
2217 chips might think that the current transfer is still
2218 in progress. On some boards it is possible to access
2219 the i2c SCLK line directly, either by using the
2220 processor pin as a GPIO or by having a second pin
2221 connected to the bus. If this option is defined a
2222 custom i2c_init_board() routine in boards/xxx/board.c
2223 is run early in the boot sequence.
2225 CONFIG_SYS_I2C_BOARD_LATE_INIT
2227 An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is
2228 defined a custom i2c_board_late_init() routine in
2229 boards/xxx/board.c is run AFTER the operations in i2c_init()
2230 is completed. This callpoint can be used to unreset i2c bus
2231 using CPU i2c controller register accesses for CPUs whose i2c
2232 controller provide such a method. It is called at the end of
2233 i2c_init() to allow i2c_init operations to setup the i2c bus
2234 controller on the CPU (e.g. setting bus speed & slave address).
2236 CONFIG_I2CFAST (PPC405GP|PPC405EP only)
2238 This option enables configuration of bi_iic_fast[] flags
2239 in u-boot bd_info structure based on u-boot environment
2240 variable "i2cfast". (see also i2cfast)
2242 CONFIG_I2C_MULTI_BUS
2244 This option allows the use of multiple I2C buses, each of which
2245 must have a controller. At any point in time, only one bus is
2246 active. To switch to a different bus, use the 'i2c dev' command.
2247 Note that bus numbering is zero-based.
2249 CONFIG_SYS_I2C_NOPROBES
2251 This option specifies a list of I2C devices that will be skipped
2252 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS
2253 is set, specify a list of bus-device pairs. Otherwise, specify
2254 a 1D array of device addresses
2257 #undef CONFIG_I2C_MULTI_BUS
2258 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}
2260 will skip addresses 0x50 and 0x68 on a board with one I2C bus
2262 #define CONFIG_I2C_MULTI_BUS
2263 #define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
2265 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
2267 CONFIG_SYS_SPD_BUS_NUM
2269 If defined, then this indicates the I2C bus number for DDR SPD.
2270 If not defined, then U-Boot assumes that SPD is on I2C bus 0.
2272 CONFIG_SYS_RTC_BUS_NUM
2274 If defined, then this indicates the I2C bus number for the RTC.
2275 If not defined, then U-Boot assumes that RTC is on I2C bus 0.
2277 CONFIG_SYS_DTT_BUS_NUM
2279 If defined, then this indicates the I2C bus number for the DTT.
2280 If not defined, then U-Boot assumes that DTT is on I2C bus 0.
2282 CONFIG_SYS_I2C_DTT_ADDR:
2284 If defined, specifies the I2C address of the DTT device.
2285 If not defined, then U-Boot uses predefined value for
2286 specified DTT device.
2288 CONFIG_SOFT_I2C_READ_REPEATED_START
2290 defining this will force the i2c_read() function in
2291 the soft_i2c driver to perform an I2C repeated start
2292 between writing the address pointer and reading the
2293 data. If this define is omitted the default behaviour
2294 of doing a stop-start sequence will be used. Most I2C
2295 devices can use either method, but some require one or
2298 - SPI Support: CONFIG_SPI
2300 Enables SPI driver (so far only tested with
2301 SPI EEPROM, also an instance works with Crystal A/D and
2302 D/As on the SACSng board)
2306 Enables the driver for SPI controller on SuperH. Currently
2307 only SH7757 is supported.
2311 Enables extended (16-bit) SPI EEPROM addressing.
2312 (symmetrical to CONFIG_I2C_X)
2316 Enables a software (bit-bang) SPI driver rather than
2317 using hardware support. This is a general purpose
2318 driver that only requires three general I/O port pins
2319 (two outputs, one input) to function. If this is
2320 defined, the board configuration must define several
2321 SPI configuration items (port pins to use, etc). For
2322 an example, see include/configs/sacsng.h.
2326 Enables a hardware SPI driver for general-purpose reads
2327 and writes. As with CONFIG_SOFT_SPI, the board configuration
2328 must define a list of chip-select function pointers.
2329 Currently supported on some MPC8xxx processors. For an
2330 example, see include/configs/mpc8349emds.h.
2334 Enables the driver for the SPI controllers on i.MX and MXC
2335 SoCs. Currently i.MX31/35/51 are supported.
2337 - FPGA Support: CONFIG_FPGA
2339 Enables FPGA subsystem.
2341 CONFIG_FPGA_<vendor>
2343 Enables support for specific chip vendors.
2346 CONFIG_FPGA_<family>
2348 Enables support for FPGA family.
2349 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
2353 Specify the number of FPGA devices to support.
2355 CONFIG_SYS_FPGA_PROG_FEEDBACK
2357 Enable printing of hash marks during FPGA configuration.
2359 CONFIG_SYS_FPGA_CHECK_BUSY
2361 Enable checks on FPGA configuration interface busy
2362 status by the configuration function. This option
2363 will require a board or device specific function to
2368 If defined, a function that provides delays in the FPGA
2369 configuration driver.
2371 CONFIG_SYS_FPGA_CHECK_CTRLC
2372 Allow Control-C to interrupt FPGA configuration
2374 CONFIG_SYS_FPGA_CHECK_ERROR
2376 Check for configuration errors during FPGA bitfile
2377 loading. For example, abort during Virtex II
2378 configuration if the INIT_B line goes low (which
2379 indicated a CRC error).
2381 CONFIG_SYS_FPGA_WAIT_INIT
2383 Maximum time to wait for the INIT_B line to deassert
2384 after PROB_B has been deasserted during a Virtex II
2385 FPGA configuration sequence. The default time is 500
2388 CONFIG_SYS_FPGA_WAIT_BUSY
2390 Maximum time to wait for BUSY to deassert during
2391 Virtex II FPGA configuration. The default is 5 ms.
2393 CONFIG_SYS_FPGA_WAIT_CONFIG
2395 Time to wait after FPGA configuration. The default is
2398 - Configuration Management:
2401 If defined, this string will be added to the U-Boot
2402 version information (U_BOOT_VERSION)
2404 - Vendor Parameter Protection:
2406 U-Boot considers the values of the environment
2407 variables "serial#" (Board Serial Number) and
2408 "ethaddr" (Ethernet Address) to be parameters that
2409 are set once by the board vendor / manufacturer, and
2410 protects these variables from casual modification by
2411 the user. Once set, these variables are read-only,
2412 and write or delete attempts are rejected. You can
2413 change this behaviour:
2415 If CONFIG_ENV_OVERWRITE is #defined in your config
2416 file, the write protection for vendor parameters is
2417 completely disabled. Anybody can change or delete
2420 Alternatively, if you #define _both_ CONFIG_ETHADDR
2421 _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
2422 Ethernet address is installed in the environment,
2423 which can be changed exactly ONCE by the user. [The
2424 serial# is unaffected by this, i. e. it remains
2427 The same can be accomplished in a more flexible way
2428 for any variable by configuring the type of access
2429 to allow for those variables in the ".flags" variable
2430 or define CONFIG_ENV_FLAGS_LIST_STATIC.
2435 Define this variable to enable the reservation of
2436 "protected RAM", i. e. RAM which is not overwritten
2437 by U-Boot. Define CONFIG_PRAM to hold the number of
2438 kB you want to reserve for pRAM. You can overwrite
2439 this default value by defining an environment
2440 variable "pram" to the number of kB you want to
2441 reserve. Note that the board info structure will
2442 still show the full amount of RAM. If pRAM is
2443 reserved, a new environment variable "mem" will
2444 automatically be defined to hold the amount of
2445 remaining RAM in a form that can be passed as boot
2446 argument to Linux, for instance like that:
2448 setenv bootargs ... mem=\${mem}
2451 This way you can tell Linux not to use this memory,
2452 either, which results in a memory region that will
2453 not be affected by reboots.
2455 *WARNING* If your board configuration uses automatic
2456 detection of the RAM size, you must make sure that
2457 this memory test is non-destructive. So far, the
2458 following board configurations are known to be
2461 IVMS8, IVML24, SPD8xx, TQM8xxL,
2462 HERMES, IP860, RPXlite, LWMON,
2465 - Access to physical memory region (> 4GB)
2466 Some basic support is provided for operations on memory not
2467 normally accessible to U-Boot - e.g. some architectures
2468 support access to more than 4GB of memory on 32-bit
2469 machines using physical address extension or similar.
2470 Define CONFIG_PHYSMEM to access this basic support, which
2471 currently only supports clearing the memory.
2476 Define this variable to stop the system in case of a
2477 fatal error, so that you have to reset it manually.
2478 This is probably NOT a good idea for an embedded
2479 system where you want the system to reboot
2480 automatically as fast as possible, but it may be
2481 useful during development since you can try to debug
2482 the conditions that lead to the situation.
2484 CONFIG_NET_RETRY_COUNT
2486 This variable defines the number of retries for
2487 network operations like ARP, RARP, TFTP, or BOOTP
2488 before giving up the operation. If not defined, a
2489 default value of 5 is used.
2493 Timeout waiting for an ARP reply in milliseconds.
2497 Timeout in milliseconds used in NFS protocol.
2498 If you encounter "ERROR: Cannot umount" in nfs command,
2499 try longer timeout such as
2500 #define CONFIG_NFS_TIMEOUT 10000UL
2502 - Command Interpreter:
2503 CONFIG_AUTO_COMPLETE
2505 Enable auto completion of commands using TAB.
2507 Note that this feature has NOT been implemented yet
2508 for the "hush" shell.
2511 CONFIG_SYS_HUSH_PARSER
2513 Define this variable to enable the "hush" shell (from
2514 Busybox) as command line interpreter, thus enabling
2515 powerful command line syntax like
2516 if...then...else...fi conditionals or `&&' and '||'
2517 constructs ("shell scripts").
2519 If undefined, you get the old, much simpler behaviour
2520 with a somewhat smaller memory footprint.
2523 CONFIG_SYS_PROMPT_HUSH_PS2
2525 This defines the secondary prompt string, which is
2526 printed when the command interpreter needs more input
2527 to complete a command. Usually "> ".
2531 In the current implementation, the local variables
2532 space and global environment variables space are
2533 separated. Local variables are those you define by
2534 simply typing `name=value'. To access a local
2535 variable later on, you have write `$name' or
2536 `${name}'; to execute the contents of a variable
2537 directly type `$name' at the command prompt.
2539 Global environment variables are those you use
2540 setenv/printenv to work with. To run a command stored
2541 in such a variable, you need to use the run command,
2542 and you must not use the '$' sign to access them.
2544 To store commands and special characters in a
2545 variable, please use double quotation marks
2546 surrounding the whole text of the variable, instead
2547 of the backslashes before semicolons and special
2550 - Commandline Editing and History:
2551 CONFIG_CMDLINE_EDITING
2553 Enable editing and History functions for interactive
2554 commandline input operations
2556 - Default Environment:
2557 CONFIG_EXTRA_ENV_SETTINGS
2559 Define this to contain any number of null terminated
2560 strings (variable = value pairs) that will be part of
2561 the default environment compiled into the boot image.
2563 For example, place something like this in your
2564 board's config file:
2566 #define CONFIG_EXTRA_ENV_SETTINGS \
2570 Warning: This method is based on knowledge about the
2571 internal format how the environment is stored by the
2572 U-Boot code. This is NOT an official, exported
2573 interface! Although it is unlikely that this format
2574 will change soon, there is no guarantee either.
2575 You better know what you are doing here.
2577 Note: overly (ab)use of the default environment is
2578 discouraged. Make sure to check other ways to preset
2579 the environment like the "source" command or the
2582 CONFIG_ENV_VARS_UBOOT_CONFIG
2584 Define this in order to add variables describing the
2585 U-Boot build configuration to the default environment.
2586 These will be named arch, cpu, board, vendor, and soc.
2588 Enabling this option will cause the following to be defined:
2596 CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG
2598 Define this in order to add variables describing certain
2599 run-time determined information about the hardware to the
2600 environment. These will be named board_name, board_rev.
2602 CONFIG_DELAY_ENVIRONMENT
2604 Normally the environment is loaded when the board is
2605 intialised so that it is available to U-Boot. This inhibits
2606 that so that the environment is not available until
2607 explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL
2608 this is instead controlled by the value of
2609 /config/load-environment.
2611 - DataFlash Support:
2612 CONFIG_HAS_DATAFLASH
2614 Defining this option enables DataFlash features and
2615 allows to read/write in Dataflash via the standard
2618 - Serial Flash support
2621 Defining this option enables SPI flash commands
2622 'sf probe/read/write/erase/update'.
2624 Usage requires an initial 'probe' to define the serial
2625 flash parameters, followed by read/write/erase/update
2628 The following defaults may be provided by the platform
2629 to handle the common case when only a single serial
2630 flash is present on the system.
2632 CONFIG_SF_DEFAULT_BUS Bus identifier
2633 CONFIG_SF_DEFAULT_CS Chip-select
2634 CONFIG_SF_DEFAULT_MODE (see include/spi.h)
2635 CONFIG_SF_DEFAULT_SPEED in Hz
2639 Define this option to include a destructive SPI flash
2642 CONFIG_SPI_FLASH_BAR Ban/Extended Addr Reg
2644 Define this option to use the Bank addr/Extended addr
2645 support on SPI flashes which has size > 16Mbytes.
2647 - SystemACE Support:
2650 Adding this option adds support for Xilinx SystemACE
2651 chips attached via some sort of local bus. The address
2652 of the chip must also be defined in the
2653 CONFIG_SYS_SYSTEMACE_BASE macro. For example:
2655 #define CONFIG_SYSTEMACE
2656 #define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000
2658 When SystemACE support is added, the "ace" device type
2659 becomes available to the fat commands, i.e. fatls.
2661 - TFTP Fixed UDP Port:
2664 If this is defined, the environment variable tftpsrcp
2665 is used to supply the TFTP UDP source port value.
2666 If tftpsrcp isn't defined, the normal pseudo-random port
2667 number generator is used.
2669 Also, the environment variable tftpdstp is used to supply
2670 the TFTP UDP destination port value. If tftpdstp isn't
2671 defined, the normal port 69 is used.
2673 The purpose for tftpsrcp is to allow a TFTP server to
2674 blindly start the TFTP transfer using the pre-configured
2675 target IP address and UDP port. This has the effect of
2676 "punching through" the (Windows XP) firewall, allowing
2677 the remainder of the TFTP transfer to proceed normally.
2678 A better solution is to properly configure the firewall,
2679 but sometimes that is not allowed.
2684 This enables a generic 'hash' command which can produce
2685 hashes / digests from a few algorithms (e.g. SHA1, SHA256).
2689 Enable the hash verify command (hash -v). This adds to code
2692 CONFIG_SHA1 - support SHA1 hashing
2693 CONFIG_SHA256 - support SHA256 hashing
2695 Note: There is also a sha1sum command, which should perhaps
2696 be deprecated in favour of 'hash sha1'.
2698 - Freescale i.MX specific commands:
2699 CONFIG_CMD_HDMIDETECT
2700 This enables 'hdmidet' command which returns true if an
2701 HDMI monitor is detected. This command is i.MX 6 specific.
2704 This enables the 'bmode' (bootmode) command for forcing
2705 a boot from specific media.
2707 This is useful for forcing the ROM's usb downloader to
2708 activate upon a watchdog reset which is nice when iterating
2709 on U-Boot. Using the reset button or running bmode normal
2710 will set it back to normal. This command currently
2711 supports i.MX53 and i.MX6.
2716 This enables the RSA algorithm used for FIT image verification
2717 in U-Boot. See doc/uImage/signature for more information.
2719 The signing part is build into mkimage regardless of this
2723 - Show boot progress:
2724 CONFIG_SHOW_BOOT_PROGRESS
2726 Defining this option allows to add some board-
2727 specific code (calling a user-provided function
2728 "show_boot_progress(int)") that enables you to show
2729 the system's boot progress on some display (for
2730 example, some LED's) on your board. At the moment,
2731 the following checkpoints are implemented:
2733 - Detailed boot stage timing
2735 Define this option to get detailed timing of each stage
2736 of the boot process.
2738 CONFIG_BOOTSTAGE_USER_COUNT
2739 This is the number of available user bootstage records.
2740 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
2741 a new ID will be allocated from this stash. If you exceed
2742 the limit, recording will stop.
2744 CONFIG_BOOTSTAGE_REPORT
2745 Define this to print a report before boot, similar to this:
2747 Timer summary in microseconds:
2750 3,575,678 3,575,678 board_init_f start
2751 3,575,695 17 arch_cpu_init A9
2752 3,575,777 82 arch_cpu_init done
2753 3,659,598 83,821 board_init_r start
2754 3,910,375 250,777 main_loop
2755 29,916,167 26,005,792 bootm_start
2756 30,361,327 445,160 start_kernel
2758 CONFIG_CMD_BOOTSTAGE
2759 Add a 'bootstage' command which supports printing a report
2760 and un/stashing of bootstage data.
2762 CONFIG_BOOTSTAGE_FDT
2763 Stash the bootstage information in the FDT. A root 'bootstage'
2764 node is created with each bootstage id as a child. Each child
2765 has a 'name' property and either 'mark' containing the
2766 mark time in microsecond, or 'accum' containing the
2767 accumulated time for that bootstage id in microseconds.
2772 name = "board_init_f";
2781 Code in the Linux kernel can find this in /proc/devicetree.
2783 Legacy uImage format:
2786 1 common/cmd_bootm.c before attempting to boot an image
2787 -1 common/cmd_bootm.c Image header has bad magic number
2788 2 common/cmd_bootm.c Image header has correct magic number
2789 -2 common/cmd_bootm.c Image header has bad checksum
2790 3 common/cmd_bootm.c Image header has correct checksum
2791 -3 common/cmd_bootm.c Image data has bad checksum
2792 4 common/cmd_bootm.c Image data has correct checksum
2793 -4 common/cmd_bootm.c Image is for unsupported architecture
2794 5 common/cmd_bootm.c Architecture check OK
2795 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
2796 6 common/cmd_bootm.c Image Type check OK
2797 -6 common/cmd_bootm.c gunzip uncompression error
2798 -7 common/cmd_bootm.c Unimplemented compression type
2799 7 common/cmd_bootm.c Uncompression OK
2800 8 common/cmd_bootm.c No uncompress/copy overwrite error
2801 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
2803 9 common/image.c Start initial ramdisk verification
2804 -10 common/image.c Ramdisk header has bad magic number
2805 -11 common/image.c Ramdisk header has bad checksum
2806 10 common/image.c Ramdisk header is OK
2807 -12 common/image.c Ramdisk data has bad checksum
2808 11 common/image.c Ramdisk data has correct checksum
2809 12 common/image.c Ramdisk verification complete, start loading
2810 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
2811 13 common/image.c Start multifile image verification
2812 14 common/image.c No initial ramdisk, no multifile, continue.
2814 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
2816 -30 arch/powerpc/lib/board.c Fatal error, hang the system
2817 -31 post/post.c POST test failed, detected by post_output_backlog()
2818 -32 post/post.c POST test failed, detected by post_run_single()
2820 34 common/cmd_doc.c before loading a Image from a DOC device
2821 -35 common/cmd_doc.c Bad usage of "doc" command
2822 35 common/cmd_doc.c correct usage of "doc" command
2823 -36 common/cmd_doc.c No boot device
2824 36 common/cmd_doc.c correct boot device
2825 -37 common/cmd_doc.c Unknown Chip ID on boot device
2826 37 common/cmd_doc.c correct chip ID found, device available
2827 -38 common/cmd_doc.c Read Error on boot device
2828 38 common/cmd_doc.c reading Image header from DOC device OK
2829 -39 common/cmd_doc.c Image header has bad magic number
2830 39 common/cmd_doc.c Image header has correct magic number
2831 -40 common/cmd_doc.c Error reading Image from DOC device
2832 40 common/cmd_doc.c Image header has correct magic number
2833 41 common/cmd_ide.c before loading a Image from a IDE device
2834 -42 common/cmd_ide.c Bad usage of "ide" command
2835 42 common/cmd_ide.c correct usage of "ide" command
2836 -43 common/cmd_ide.c No boot device
2837 43 common/cmd_ide.c boot device found
2838 -44 common/cmd_ide.c Device not available
2839 44 common/cmd_ide.c Device available
2840 -45 common/cmd_ide.c wrong partition selected
2841 45 common/cmd_ide.c partition selected
2842 -46 common/cmd_ide.c Unknown partition table
2843 46 common/cmd_ide.c valid partition table found
2844 -47 common/cmd_ide.c Invalid partition type
2845 47 common/cmd_ide.c correct partition type
2846 -48 common/cmd_ide.c Error reading Image Header on boot device
2847 48 common/cmd_ide.c reading Image Header from IDE device OK
2848 -49 common/cmd_ide.c Image header has bad magic number
2849 49 common/cmd_ide.c Image header has correct magic number
2850 -50 common/cmd_ide.c Image header has bad checksum
2851 50 common/cmd_ide.c Image header has correct checksum
2852 -51 common/cmd_ide.c Error reading Image from IDE device
2853 51 common/cmd_ide.c reading Image from IDE device OK
2854 52 common/cmd_nand.c before loading a Image from a NAND device
2855 -53 common/cmd_nand.c Bad usage of "nand" command
2856 53 common/cmd_nand.c correct usage of "nand" command
2857 -54 common/cmd_nand.c No boot device
2858 54 common/cmd_nand.c boot device found
2859 -55 common/cmd_nand.c Unknown Chip ID on boot device
2860 55 common/cmd_nand.c correct chip ID found, device available
2861 -56 common/cmd_nand.c Error reading Image Header on boot device
2862 56 common/cmd_nand.c reading Image Header from NAND device OK
2863 -57 common/cmd_nand.c Image header has bad magic number
2864 57 common/cmd_nand.c Image header has correct magic number
2865 -58 common/cmd_nand.c Error reading Image from NAND device
2866 58 common/cmd_nand.c reading Image from NAND device OK
2868 -60 common/env_common.c Environment has a bad CRC, using default
2870 64 net/eth.c starting with Ethernet configuration.
2871 -64 net/eth.c no Ethernet found.
2872 65 net/eth.c Ethernet found.
2874 -80 common/cmd_net.c usage wrong
2875 80 common/cmd_net.c before calling NetLoop()
2876 -81 common/cmd_net.c some error in NetLoop() occurred
2877 81 common/cmd_net.c NetLoop() back without error
2878 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
2879 82 common/cmd_net.c trying automatic boot
2880 83 common/cmd_net.c running "source" command
2881 -83 common/cmd_net.c some error in automatic boot or "source" command
2882 84 common/cmd_net.c end without errors
2887 100 common/cmd_bootm.c Kernel FIT Image has correct format
2888 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
2889 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
2890 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
2891 102 common/cmd_bootm.c Kernel unit name specified
2892 -103 common/cmd_bootm.c Can't get kernel subimage node offset
2893 103 common/cmd_bootm.c Found configuration node
2894 104 common/cmd_bootm.c Got kernel subimage node offset
2895 -104 common/cmd_bootm.c Kernel subimage hash verification failed
2896 105 common/cmd_bootm.c Kernel subimage hash verification OK
2897 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
2898 106 common/cmd_bootm.c Architecture check OK
2899 -106 common/cmd_bootm.c Kernel subimage has wrong type
2900 107 common/cmd_bootm.c Kernel subimage type OK
2901 -107 common/cmd_bootm.c Can't get kernel subimage data/size
2902 108 common/cmd_bootm.c Got kernel subimage data/size
2903 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
2904 -109 common/cmd_bootm.c Can't get kernel subimage type
2905 -110 common/cmd_bootm.c Can't get kernel subimage comp
2906 -111 common/cmd_bootm.c Can't get kernel subimage os
2907 -112 common/cmd_bootm.c Can't get kernel subimage load address
2908 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
2910 120 common/image.c Start initial ramdisk verification
2911 -120 common/image.c Ramdisk FIT image has incorrect format
2912 121 common/image.c Ramdisk FIT image has correct format
2913 122 common/image.c No ramdisk subimage unit name, using configuration
2914 -122 common/image.c Can't get configuration for ramdisk subimage
2915 123 common/image.c Ramdisk unit name specified
2916 -124 common/image.c Can't get ramdisk subimage node offset
2917 125 common/image.c Got ramdisk subimage node offset
2918 -125 common/image.c Ramdisk subimage hash verification failed
2919 126 common/image.c Ramdisk subimage hash verification OK
2920 -126 common/image.c Ramdisk subimage for unsupported architecture
2921 127 common/image.c Architecture check OK
2922 -127 common/image.c Can't get ramdisk subimage data/size
2923 128 common/image.c Got ramdisk subimage data/size
2924 129 common/image.c Can't get ramdisk load address
2925 -129 common/image.c Got ramdisk load address
2927 -130 common/cmd_doc.c Incorrect FIT image format
2928 131 common/cmd_doc.c FIT image format OK
2930 -140 common/cmd_ide.c Incorrect FIT image format
2931 141 common/cmd_ide.c FIT image format OK
2933 -150 common/cmd_nand.c Incorrect FIT image format
2934 151 common/cmd_nand.c FIT image format OK
2936 - FIT image support:
2938 Enable support for the FIT uImage format.
2940 CONFIG_FIT_BEST_MATCH
2941 When no configuration is explicitly selected, default to the
2942 one whose fdt's compatibility field best matches that of
2943 U-Boot itself. A match is considered "best" if it matches the
2944 most specific compatibility entry of U-Boot's fdt's root node.
2945 The order of entries in the configuration's fdt is ignored.
2947 CONFIG_FIT_SIGNATURE
2948 This option enables signature verification of FIT uImages,
2949 using a hash signed and verified using RSA. See
2950 doc/uImage.FIT/signature.txt for more details.
2952 - Standalone program support:
2953 CONFIG_STANDALONE_LOAD_ADDR
2955 This option defines a board specific value for the
2956 address where standalone program gets loaded, thus
2957 overwriting the architecture dependent default
2960 - Frame Buffer Address:
2963 Define CONFIG_FB_ADDR if you want to use specific
2964 address for frame buffer. This is typically the case
2965 when using a graphics controller has separate video
2966 memory. U-Boot will then place the frame buffer at
2967 the given address instead of dynamically reserving it
2968 in system RAM by calling lcd_setmem(), which grabs
2969 the memory for the frame buffer depending on the
2970 configured panel size.
2972 Please see board_init_f function.
2974 - Automatic software updates via TFTP server
2976 CONFIG_UPDATE_TFTP_CNT_MAX
2977 CONFIG_UPDATE_TFTP_MSEC_MAX
2979 These options enable and control the auto-update feature;
2980 for a more detailed description refer to doc/README.update.
2982 - MTD Support (mtdparts command, UBI support)
2985 Adds the MTD device infrastructure from the Linux kernel.
2986 Needed for mtdparts command support.
2988 CONFIG_MTD_PARTITIONS
2990 Adds the MTD partitioning infrastructure from the Linux
2991 kernel. Needed for UBI support.
2996 Adds commands for interacting with MTD partitions formatted
2997 with the UBI flash translation layer
2999 Requires also defining CONFIG_RBTREE
3001 CONFIG_UBI_SILENCE_MSG
3003 Make the verbose messages from UBI stop printing. This leaves
3004 warnings and errors enabled.
3009 Adds commands for interacting with UBI volumes formatted as
3010 UBIFS. UBIFS is read-only in u-boot.
3012 Requires UBI support as well as CONFIG_LZO
3014 CONFIG_UBIFS_SILENCE_MSG
3016 Make the verbose messages from UBIFS stop printing. This leaves
3017 warnings and errors enabled.
3021 Enable building of SPL globally.
3024 LDSCRIPT for linking the SPL binary.
3026 CONFIG_SPL_MAX_FOOTPRINT
3027 Maximum size in memory allocated to the SPL, BSS included.
3028 When defined, the linker checks that the actual memory
3029 used by SPL from _start to __bss_end does not exceed it.
3030 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
3031 must not be both defined at the same time.
3034 Maximum size of the SPL image (text, data, rodata, and
3035 linker lists sections), BSS excluded.
3036 When defined, the linker checks that the actual size does
3039 CONFIG_SPL_TEXT_BASE
3040 TEXT_BASE for linking the SPL binary.
3042 CONFIG_SPL_RELOC_TEXT_BASE
3043 Address to relocate to. If unspecified, this is equal to
3044 CONFIG_SPL_TEXT_BASE (i.e. no relocation is done).
3046 CONFIG_SPL_BSS_START_ADDR
3047 Link address for the BSS within the SPL binary.
3049 CONFIG_SPL_BSS_MAX_SIZE
3050 Maximum size in memory allocated to the SPL BSS.
3051 When defined, the linker checks that the actual memory used
3052 by SPL from __bss_start to __bss_end does not exceed it.
3053 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
3054 must not be both defined at the same time.
3057 Adress of the start of the stack SPL will use
3059 CONFIG_SPL_RELOC_STACK
3060 Adress of the start of the stack SPL will use after
3061 relocation. If unspecified, this is equal to
3064 CONFIG_SYS_SPL_MALLOC_START
3065 Starting address of the malloc pool used in SPL.
3067 CONFIG_SYS_SPL_MALLOC_SIZE
3068 The size of the malloc pool used in SPL.
3070 CONFIG_SPL_FRAMEWORK
3071 Enable the SPL framework under common/. This framework
3072 supports MMC, NAND and YMODEM loading of U-Boot and NAND
3073 NAND loading of the Linux Kernel.
3075 CONFIG_SPL_DISPLAY_PRINT
3076 For ARM, enable an optional function to print more information
3077 about the running system.
3079 CONFIG_SPL_INIT_MINIMAL
3080 Arch init code should be built for a very small image
3082 CONFIG_SPL_LIBCOMMON_SUPPORT
3083 Support for common/libcommon.o in SPL binary
3085 CONFIG_SPL_LIBDISK_SUPPORT
3086 Support for disk/libdisk.o in SPL binary
3088 CONFIG_SPL_I2C_SUPPORT
3089 Support for drivers/i2c/libi2c.o in SPL binary
3091 CONFIG_SPL_GPIO_SUPPORT
3092 Support for drivers/gpio/libgpio.o in SPL binary
3094 CONFIG_SPL_MMC_SUPPORT
3095 Support for drivers/mmc/libmmc.o in SPL binary
3097 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR,
3098 CONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS,
3099 CONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION
3100 Address, size and partition on the MMC to load U-Boot from
3101 when the MMC is being used in raw mode.
3103 CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
3104 Sector to load kernel uImage from when MMC is being
3105 used in raw mode (for Falcon mode)
3107 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR,
3108 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS
3109 Sector and number of sectors to load kernel argument
3110 parameters from when MMC is being used in raw mode
3113 CONFIG_SPL_FAT_SUPPORT
3114 Support for fs/fat/libfat.o in SPL binary
3116 CONFIG_SPL_FAT_LOAD_PAYLOAD_NAME
3117 Filename to read to load U-Boot when reading from FAT
3119 CONFIG_SPL_FAT_LOAD_KERNEL_NAME
3120 Filename to read to load kernel uImage when reading
3121 from FAT (for Falcon mode)
3123 CONFIG_SPL_FAT_LOAD_ARGS_NAME
3124 Filename to read to load kernel argument parameters
3125 when reading from FAT (for Falcon mode)
3127 CONFIG_SPL_MPC83XX_WAIT_FOR_NAND
3128 Set this for NAND SPL on PPC mpc83xx targets, so that
3129 start.S waits for the rest of the SPL to load before
3130 continuing (the hardware starts execution after just
3131 loading the first page rather than the full 4K).
3133 CONFIG_SPL_NAND_BASE
3134 Include nand_base.c in the SPL. Requires
3135 CONFIG_SPL_NAND_DRIVERS.
3137 CONFIG_SPL_NAND_DRIVERS
3138 SPL uses normal NAND drivers, not minimal drivers.
3141 Include standard software ECC in the SPL
3143 CONFIG_SPL_NAND_SIMPLE
3144 Support for NAND boot using simple NAND drivers that
3145 expose the cmd_ctrl() interface.
3147 CONFIG_SPL_MPC8XXX_INIT_DDR_SUPPORT
3148 Set for the SPL on PPC mpc8xxx targets, support for
3149 arch/powerpc/cpu/mpc8xxx/ddr/libddr.o in SPL binary.
3151 CONFIG_SPL_COMMON_INIT_DDR
3152 Set for common ddr init with serial presence detect in
3155 CONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT,
3156 CONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE,
3157 CONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS,
3158 CONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE,
3159 CONFIG_SYS_NAND_ECCBYTES
3160 Defines the size and behavior of the NAND that SPL uses
3163 CONFIG_SYS_NAND_U_BOOT_OFFS
3164 Location in NAND to read U-Boot from
3166 CONFIG_SYS_NAND_U_BOOT_DST
3167 Location in memory to load U-Boot to
3169 CONFIG_SYS_NAND_U_BOOT_SIZE
3170 Size of image to load
3172 CONFIG_SYS_NAND_U_BOOT_START
3173 Entry point in loaded image to jump to
3175 CONFIG_SYS_NAND_HW_ECC_OOBFIRST
3176 Define this if you need to first read the OOB and then the
3177 data. This is used for example on davinci plattforms.
3179 CONFIG_SPL_OMAP3_ID_NAND
3180 Support for an OMAP3-specific set of functions to return the
3181 ID and MFR of the first attached NAND chip, if present.
3183 CONFIG_SPL_SERIAL_SUPPORT
3184 Support for drivers/serial/libserial.o in SPL binary
3186 CONFIG_SPL_SPI_FLASH_SUPPORT
3187 Support for drivers/mtd/spi/libspi_flash.o in SPL binary
3189 CONFIG_SPL_SPI_SUPPORT
3190 Support for drivers/spi/libspi.o in SPL binary
3192 CONFIG_SPL_RAM_DEVICE
3193 Support for running image already present in ram, in SPL binary
3195 CONFIG_SPL_LIBGENERIC_SUPPORT
3196 Support for lib/libgeneric.o in SPL binary
3198 CONFIG_SPL_ENV_SUPPORT
3199 Support for the environment operating in SPL binary
3201 CONFIG_SPL_NET_SUPPORT
3202 Support for the net/libnet.o in SPL binary.
3203 It conflicts with SPL env from storage medium specified by
3204 CONFIG_ENV_IS_xxx but CONFIG_ENV_IS_NOWHERE
3207 Image offset to which the SPL should be padded before appending
3208 the SPL payload. By default, this is defined as
3209 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
3210 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
3211 payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
3214 Final target image containing SPL and payload. Some SPLs
3215 use an arch-specific makefile fragment instead, for
3216 example if more than one image needs to be produced.
3218 CONFIG_FIT_SPL_PRINT
3219 Printing information about a FIT image adds quite a bit of
3220 code to SPL. So this is normally disabled in SPL. Use this
projects / karo-tx-uboot.git / blob