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 MAINTAINERS 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 /arm925t Files specific to ARM 925 CPUs
143 /arm926ejs Files specific to ARM 926 CPUs
144 /arm1136 Files specific to ARM 1136 CPUs
145 /ixp Files specific to Intel XScale IXP CPUs
146 /pxa Files specific to Intel XScale PXA CPUs
147 /s3c44b0 Files specific to Samsung S3C44B0 CPUs
148 /sa1100 Files specific to Intel StrongARM SA1100 CPUs
149 /lib Architecture specific library files
150 /avr32 Files generic to AVR32 architecture
151 /cpu CPU specific files
152 /lib Architecture specific library files
153 /blackfin Files generic to Analog Devices Blackfin architecture
154 /cpu CPU specific files
155 /lib Architecture specific library files
156 /x86 Files generic to x86 architecture
157 /cpu CPU specific files
158 /lib Architecture specific library files
159 /m68k Files generic to m68k architecture
160 /cpu CPU specific files
161 /mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
162 /mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs
163 /mcf532x Files specific to Freescale ColdFire MCF5329 CPUs
164 /mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs
165 /mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs
166 /lib Architecture specific library files
167 /microblaze Files generic to microblaze architecture
168 /cpu CPU specific files
169 /lib Architecture specific library files
170 /mips Files generic to MIPS architecture
171 /cpu CPU specific files
172 /mips32 Files specific to MIPS32 CPUs
173 /xburst Files specific to Ingenic XBurst CPUs
174 /lib Architecture specific library files
175 /nds32 Files generic to NDS32 architecture
176 /cpu CPU specific files
177 /n1213 Files specific to Andes Technology N1213 CPUs
178 /lib Architecture specific library files
179 /nios2 Files generic to Altera NIOS2 architecture
180 /cpu CPU specific files
181 /lib Architecture specific library files
182 /powerpc Files generic to PowerPC architecture
183 /cpu CPU specific files
184 /74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
185 /mpc5xx Files specific to Freescale MPC5xx CPUs
186 /mpc5xxx Files specific to Freescale MPC5xxx CPUs
187 /mpc8xx Files specific to Freescale MPC8xx CPUs
188 /mpc824x Files specific to Freescale MPC824x CPUs
189 /mpc8260 Files specific to Freescale MPC8260 CPUs
190 /mpc85xx Files specific to Freescale MPC85xx CPUs
191 /ppc4xx Files specific to AMCC PowerPC 4xx CPUs
192 /lib Architecture specific library files
193 /sh Files generic to SH architecture
194 /cpu CPU specific files
195 /sh2 Files specific to sh2 CPUs
196 /sh3 Files specific to sh3 CPUs
197 /sh4 Files specific to sh4 CPUs
198 /lib Architecture specific library files
199 /sparc Files generic to SPARC architecture
200 /cpu CPU specific files
201 /leon2 Files specific to Gaisler LEON2 SPARC CPU
202 /leon3 Files specific to Gaisler LEON3 SPARC CPU
203 /lib Architecture specific library files
204 /api Machine/arch independent API for external apps
205 /board Board dependent files
206 /common Misc architecture independent functions
207 /disk Code for disk drive partition handling
208 /doc Documentation (don't expect too much)
209 /drivers Commonly used device drivers
210 /examples Example code for standalone applications, etc.
211 /fs Filesystem code (cramfs, ext2, jffs2, etc.)
212 /include Header Files
213 /lib Files generic to all architectures
214 /libfdt Library files to support flattened device trees
215 /lzma Library files to support LZMA decompression
216 /lzo Library files to support LZO decompression
218 /post Power On Self Test
219 /rtc Real Time Clock drivers
220 /tools Tools to build S-Record or U-Boot images, etc.
222 Software Configuration:
223 =======================
225 Configuration is usually done using C preprocessor defines; the
226 rationale behind that is to avoid dead code whenever possible.
228 There are two classes of configuration variables:
230 * Configuration _OPTIONS_:
231 These are selectable by the user and have names beginning with
234 * Configuration _SETTINGS_:
235 These depend on the hardware etc. and should not be meddled with if
236 you don't know what you're doing; they have names beginning with
239 Later we will add a configuration tool - probably similar to or even
240 identical to what's used for the Linux kernel. Right now, we have to
241 do the configuration by hand, which means creating some symbolic
242 links and editing some configuration files. We use the TQM8xxL boards
246 Selection of Processor Architecture and Board Type:
247 ---------------------------------------------------
249 For all supported boards there are ready-to-use default
250 configurations available; just type "make <board_name>_config".
252 Example: For a TQM823L module type:
257 For the Cogent platform, you need to specify the CPU type as well;
258 e.g. "make cogent_mpc8xx_config". And also configure the cogent
259 directory according to the instructions in cogent/README.
262 Configuration Options:
263 ----------------------
265 Configuration depends on the combination of board and CPU type; all
266 such information is kept in a configuration file
267 "include/configs/<board_name>.h".
269 Example: For a TQM823L module, all configuration settings are in
270 "include/configs/TQM823L.h".
273 Many of the options are named exactly as the corresponding Linux
274 kernel configuration options. The intention is to make it easier to
275 build a config tool - later.
278 The following options need to be configured:
280 - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
282 - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
284 - CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)
285 Define exactly one, e.g. CONFIG_ATSTK1002
287 - CPU Module Type: (if CONFIG_COGENT is defined)
288 Define exactly one of
290 --- FIXME --- not tested yet:
291 CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
292 CONFIG_CMA287_23, CONFIG_CMA287_50
294 - Motherboard Type: (if CONFIG_COGENT is defined)
295 Define exactly one of
296 CONFIG_CMA101, CONFIG_CMA102
298 - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
299 Define one or more of
302 - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
303 Define one or more of
304 CONFIG_LCD_HEARTBEAT - update a character position on
305 the LCD display every second with
308 - Board flavour: (if CONFIG_MPC8260ADS is defined)
311 CONFIG_SYS_8260ADS - original MPC8260ADS
312 CONFIG_SYS_8266ADS - MPC8266ADS
313 CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
314 CONFIG_SYS_8272ADS - MPC8272ADS
316 - Marvell Family Member
317 CONFIG_SYS_MVFS - define it if you want to enable
318 multiple fs option at one time
319 for marvell soc family
321 - MPC824X Family Member (if CONFIG_MPC824X is defined)
322 Define exactly one of
323 CONFIG_MPC8240, CONFIG_MPC8245
325 - 8xx CPU Options: (if using an MPC8xx CPU)
326 CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
327 get_gclk_freq() cannot work
328 e.g. if there is no 32KHz
329 reference PIT/RTC clock
330 CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
333 - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
334 CONFIG_SYS_8xx_CPUCLK_MIN
335 CONFIG_SYS_8xx_CPUCLK_MAX
336 CONFIG_8xx_CPUCLK_DEFAULT
337 See doc/README.MPC866
339 CONFIG_SYS_MEASURE_CPUCLK
341 Define this to measure the actual CPU clock instead
342 of relying on the correctness of the configured
343 values. Mostly useful for board bringup to make sure
344 the PLL is locked at the intended frequency. Note
345 that this requires a (stable) reference clock (32 kHz
346 RTC clock or CONFIG_SYS_8XX_XIN)
348 CONFIG_SYS_DELAYED_ICACHE
350 Define this option if you want to enable the
351 ICache only when Code runs from RAM.
356 Specifies that the core is a 64-bit PowerPC implementation (implements
357 the "64" category of the Power ISA). This is necessary for ePAPR
358 compliance, among other possible reasons.
360 CONFIG_SYS_FSL_TBCLK_DIV
362 Defines the core time base clock divider ratio compared to the
363 system clock. On most PQ3 devices this is 8, on newer QorIQ
364 devices it can be 16 or 32. The ratio varies from SoC to Soc.
366 CONFIG_SYS_FSL_PCIE_COMPAT
368 Defines the string to utilize when trying to match PCIe device
369 tree nodes for the given platform.
371 CONFIG_SYS_PPC_E500_DEBUG_TLB
373 Enables a temporary TLB entry to be used during boot to work
374 around limitations in e500v1 and e500v2 external debugger
375 support. This reduces the portions of the boot code where
376 breakpoints and single stepping do not work. The value of this
377 symbol should be set to the TLB1 entry to be used for this
380 CONFIG_SYS_FSL_ERRATUM_A004510
382 Enables a workaround for erratum A004510. If set,
383 then CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and
384 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set.
386 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV
387 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional)
389 Defines one or two SoC revisions (low 8 bits of SVR)
390 for which the A004510 workaround should be applied.
392 The rest of SVR is either not relevant to the decision
393 of whether the erratum is present (e.g. p2040 versus
394 p2041) or is implied by the build target, which controls
395 whether CONFIG_SYS_FSL_ERRATUM_A004510 is set.
397 See Freescale App Note 4493 for more information about
400 CONFIG_A003399_NOR_WORKAROUND
401 Enables a workaround for IFC erratum A003399. It is only
402 requred during NOR boot.
404 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY
406 This is the value to write into CCSR offset 0x18600
407 according to the A004510 workaround.
409 CONFIG_SYS_FSL_DSP_M2_RAM_ADDR
410 This value denotes start offset of M2 memory
411 which is directly connected to the DSP core.
413 CONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT
414 This value denotes start offset of DSP CCSR space.
416 - Generic CPU options:
417 CONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN
419 Defines the endianess of the CPU. Implementation of those
420 values is arch specific.
422 - Intel Monahans options:
423 CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO
425 Defines the Monahans run mode to oscillator
426 ratio. Valid values are 8, 16, 24, 31. The core
427 frequency is this value multiplied by 13 MHz.
429 CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO
431 Defines the Monahans turbo mode to oscillator
432 ratio. Valid values are 1 (default if undefined) and
433 2. The core frequency as calculated above is multiplied
437 CONFIG_SYS_INIT_SP_OFFSET
439 Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack
440 pointer. This is needed for the temporary stack before
443 CONFIG_SYS_MIPS_CACHE_MODE
445 Cache operation mode for the MIPS CPU.
446 See also arch/mips/include/asm/mipsregs.h.
448 CONF_CM_CACHABLE_NO_WA
451 CONF_CM_CACHABLE_NONCOHERENT
455 CONF_CM_CACHABLE_ACCELERATED
457 CONFIG_SYS_XWAY_EBU_BOOTCFG
459 Special option for Lantiq XWAY SoCs for booting from NOR flash.
460 See also arch/mips/cpu/mips32/start.S.
462 CONFIG_XWAY_SWAP_BYTES
464 Enable compilation of tools/xway-swap-bytes needed for Lantiq
465 XWAY SoCs for booting from NOR flash. The U-Boot image needs to
466 be swapped if a flash programmer is used.
469 CONFIG_SYS_EXCEPTION_VECTORS_HIGH
471 Select high exception vectors of the ARM core, e.g., do not
472 clear the V bit of the c1 register of CP15.
474 CONFIG_SYS_THUMB_BUILD
476 Use this flag to build U-Boot using the Thumb instruction
477 set for ARM architectures. Thumb instruction set provides
478 better code density. For ARM architectures that support
479 Thumb2 this flag will result in Thumb2 code generated by
482 CONFIG_ARM_ERRATA_716044
483 CONFIG_ARM_ERRATA_742230
484 CONFIG_ARM_ERRATA_743622
485 CONFIG_ARM_ERRATA_751472
487 If set, the workarounds for these ARM errata are applied early
488 during U-Boot startup. Note that these options force the
489 workarounds to be applied; no CPU-type/version detection
490 exists, unlike the similar options in the Linux kernel. Do not
491 set these options unless they apply!
496 The frequency of the timer returned by get_timer().
497 get_timer() must operate in milliseconds and this CONFIG
498 option must be set to 1000.
500 - Linux Kernel Interface:
503 U-Boot stores all clock information in Hz
504 internally. For binary compatibility with older Linux
505 kernels (which expect the clocks passed in the
506 bd_info data to be in MHz) the environment variable
507 "clocks_in_mhz" can be defined so that U-Boot
508 converts clock data to MHZ before passing it to the
510 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
511 "clocks_in_mhz=1" is automatically included in the
514 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
516 When transferring memsize parameter to linux, some versions
517 expect it to be in bytes, others in MB.
518 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
522 New kernel versions are expecting firmware settings to be
523 passed using flattened device trees (based on open firmware
527 * New libfdt-based support
528 * Adds the "fdt" command
529 * The bootm command automatically updates the fdt
531 OF_CPU - The proper name of the cpus node (only required for
532 MPC512X and MPC5xxx based boards).
533 OF_SOC - The proper name of the soc node (only required for
534 MPC512X and MPC5xxx based boards).
535 OF_TBCLK - The timebase frequency.
536 OF_STDOUT_PATH - The path to the console device
538 boards with QUICC Engines require OF_QE to set UCC MAC
541 CONFIG_OF_BOARD_SETUP
543 Board code has addition modification that it wants to make
544 to the flat device tree before handing it off to the kernel
548 This define fills in the correct boot CPU in the boot
549 param header, the default value is zero if undefined.
553 U-Boot can detect if an IDE device is present or not.
554 If not, and this new config option is activated, U-Boot
555 removes the ATA node from the DTS before booting Linux,
556 so the Linux IDE driver does not probe the device and
557 crash. This is needed for buggy hardware (uc101) where
558 no pull down resistor is connected to the signal IDE5V_DD7.
560 CONFIG_MACH_TYPE [relevant for ARM only][mandatory]
562 This setting is mandatory for all boards that have only one
563 machine type and must be used to specify the machine type
564 number as it appears in the ARM machine registry
565 (see http://www.arm.linux.org.uk/developer/machines/).
566 Only boards that have multiple machine types supported
567 in a single configuration file and the machine type is
568 runtime discoverable, do not have to use this setting.
570 - vxWorks boot parameters:
572 bootvx constructs a valid bootline using the following
573 environments variables: bootfile, ipaddr, serverip, hostname.
574 It loads the vxWorks image pointed bootfile.
576 CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name
577 CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address
578 CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server
579 CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters
581 CONFIG_SYS_VXWORKS_ADD_PARAMS
583 Add it at the end of the bootline. E.g "u=username pw=secret"
585 Note: If a "bootargs" environment is defined, it will overwride
586 the defaults discussed just above.
588 - Cache Configuration:
589 CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot
590 CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot
591 CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
593 - Cache Configuration for ARM:
594 CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache
596 CONFIG_SYS_PL310_BASE - Physical base address of PL310
597 controller register space
602 Define this if you want support for Amba PrimeCell PL010 UARTs.
606 Define this if you want support for Amba PrimeCell PL011 UARTs.
610 If you have Amba PrimeCell PL011 UARTs, set this variable to
611 the clock speed of the UARTs.
615 If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
616 define this to a list of base addresses for each (supported)
617 port. See e.g. include/configs/versatile.h
619 CONFIG_PL011_SERIAL_RLCR
621 Some vendor versions of PL011 serial ports (e.g. ST-Ericsson U8500)
622 have separate receive and transmit line control registers. Set
623 this variable to initialize the extra register.
625 CONFIG_PL011_SERIAL_FLUSH_ON_INIT
627 On some platforms (e.g. U8500) U-Boot is loaded by a second stage
628 boot loader that has already initialized the UART. Define this
629 variable to flush the UART at init time.
633 Depending on board, define exactly one serial port
634 (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
635 CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
636 console by defining CONFIG_8xx_CONS_NONE
638 Note: if CONFIG_8xx_CONS_NONE is defined, the serial
639 port routines must be defined elsewhere
640 (i.e. serial_init(), serial_getc(), ...)
643 Enables console device for a color framebuffer. Needs following
644 defines (cf. smiLynxEM, i8042)
645 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
647 VIDEO_HW_RECTFILL graphic chip supports
650 VIDEO_HW_BITBLT graphic chip supports
651 bit-blit (cf. smiLynxEM)
652 VIDEO_VISIBLE_COLS visible pixel columns
654 VIDEO_VISIBLE_ROWS visible pixel rows
655 VIDEO_PIXEL_SIZE bytes per pixel
656 VIDEO_DATA_FORMAT graphic data format
657 (0-5, cf. cfb_console.c)
658 VIDEO_FB_ADRS framebuffer address
659 VIDEO_KBD_INIT_FCT keyboard int fct
660 (i.e. i8042_kbd_init())
661 VIDEO_TSTC_FCT test char fct
663 VIDEO_GETC_FCT get char fct
665 CONFIG_CONSOLE_CURSOR cursor drawing on/off
666 (requires blink timer
668 CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
669 CONFIG_CONSOLE_TIME display time/date info in
671 (requires CONFIG_CMD_DATE)
672 CONFIG_VIDEO_LOGO display Linux logo in
674 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
675 linux_logo.h for logo.
676 Requires CONFIG_VIDEO_LOGO
677 CONFIG_CONSOLE_EXTRA_INFO
678 additional board info beside
681 When CONFIG_CFB_CONSOLE_ANSI is defined, console will support
682 a limited number of ANSI escape sequences (cursor control,
683 erase functions and limited graphics rendition control).
685 When CONFIG_CFB_CONSOLE is defined, video console is
686 default i/o. Serial console can be forced with
687 environment 'console=serial'.
689 When CONFIG_SILENT_CONSOLE is defined, all console
690 messages (by U-Boot and Linux!) can be silenced with
691 the "silent" environment variable. See
692 doc/README.silent for more information.
695 CONFIG_BAUDRATE - in bps
696 Select one of the baudrates listed in
697 CONFIG_SYS_BAUDRATE_TABLE, see below.
698 CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale
700 - Console Rx buffer length
701 With CONFIG_SYS_SMC_RXBUFLEN it is possible to define
702 the maximum receive buffer length for the SMC.
703 This option is actual only for 82xx and 8xx possible.
704 If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE
705 must be defined, to setup the maximum idle timeout for
708 - Pre-Console Buffer:
709 Prior to the console being initialised (i.e. serial UART
710 initialised etc) all console output is silently discarded.
711 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
712 buffer any console messages prior to the console being
713 initialised to a buffer of size CONFIG_PRE_CON_BUF_SZ
714 bytes located at CONFIG_PRE_CON_BUF_ADDR. The buffer is
715 a circular buffer, so if more than CONFIG_PRE_CON_BUF_SZ
716 bytes are output before the console is initialised, the
717 earlier bytes are discarded.
719 'Sane' compilers will generate smaller code if
720 CONFIG_PRE_CON_BUF_SZ is a power of 2
722 - Safe printf() functions
723 Define CONFIG_SYS_VSNPRINTF to compile in safe versions of
724 the printf() functions. These are defined in
725 include/vsprintf.h and include snprintf(), vsnprintf() and
726 so on. Code size increase is approximately 300-500 bytes.
727 If this option is not given then these functions will
728 silently discard their buffer size argument - this means
729 you are not getting any overflow checking in this case.
731 - Boot Delay: CONFIG_BOOTDELAY - in seconds
732 Delay before automatically booting the default image;
733 set to -1 to disable autoboot.
734 set to -2 to autoboot with no delay and not check for abort
735 (even when CONFIG_ZERO_BOOTDELAY_CHECK is defined).
737 See doc/README.autoboot for these options that
738 work with CONFIG_BOOTDELAY. None are required.
739 CONFIG_BOOT_RETRY_TIME
740 CONFIG_BOOT_RETRY_MIN
741 CONFIG_AUTOBOOT_KEYED
742 CONFIG_AUTOBOOT_PROMPT
743 CONFIG_AUTOBOOT_DELAY_STR
744 CONFIG_AUTOBOOT_STOP_STR
745 CONFIG_AUTOBOOT_DELAY_STR2
746 CONFIG_AUTOBOOT_STOP_STR2
747 CONFIG_ZERO_BOOTDELAY_CHECK
748 CONFIG_RESET_TO_RETRY
752 Only needed when CONFIG_BOOTDELAY is enabled;
753 define a command string that is automatically executed
754 when no character is read on the console interface
755 within "Boot Delay" after reset.
758 This can be used to pass arguments to the bootm
759 command. The value of CONFIG_BOOTARGS goes into the
760 environment value "bootargs".
762 CONFIG_RAMBOOT and CONFIG_NFSBOOT
763 The value of these goes into the environment as
764 "ramboot" and "nfsboot" respectively, and can be used
765 as a convenience, when switching between booting from
771 When this option is #defined, the existence of the
772 environment variable "preboot" will be checked
773 immediately before starting the CONFIG_BOOTDELAY
774 countdown and/or running the auto-boot command resp.
775 entering interactive mode.
777 This feature is especially useful when "preboot" is
778 automatically generated or modified. For an example
779 see the LWMON board specific code: here "preboot" is
780 modified when the user holds down a certain
781 combination of keys on the (special) keyboard when
784 - Serial Download Echo Mode:
786 If defined to 1, all characters received during a
787 serial download (using the "loads" command) are
788 echoed back. This might be needed by some terminal
789 emulations (like "cu"), but may as well just take
790 time on others. This setting #define's the initial
791 value of the "loads_echo" environment variable.
793 - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
795 Select one of the baudrates listed in
796 CONFIG_SYS_BAUDRATE_TABLE, see below.
799 Monitor commands can be included or excluded
800 from the build by using the #include files
801 <config_cmd_all.h> and #undef'ing unwanted
802 commands, or using <config_cmd_default.h>
803 and augmenting with additional #define's
806 The default command configuration includes all commands
807 except those marked below with a "*".
809 CONFIG_CMD_ASKENV * ask for env variable
810 CONFIG_CMD_BDI bdinfo
811 CONFIG_CMD_BEDBUG * Include BedBug Debugger
812 CONFIG_CMD_BMP * BMP support
813 CONFIG_CMD_BSP * Board specific commands
814 CONFIG_CMD_BOOTD bootd
815 CONFIG_CMD_CACHE * icache, dcache
816 CONFIG_CMD_CONSOLE coninfo
817 CONFIG_CMD_CRC32 * crc32
818 CONFIG_CMD_DATE * support for RTC, date/time...
819 CONFIG_CMD_DHCP * DHCP support
820 CONFIG_CMD_DIAG * Diagnostics
821 CONFIG_CMD_DS4510 * ds4510 I2C gpio commands
822 CONFIG_CMD_DS4510_INFO * ds4510 I2C info command
823 CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd
824 CONFIG_CMD_DS4510_RST * ds4510 I2C rst command
825 CONFIG_CMD_DTT * Digital Therm and Thermostat
826 CONFIG_CMD_ECHO echo arguments
827 CONFIG_CMD_EDITENV edit env variable
828 CONFIG_CMD_EEPROM * EEPROM read/write support
829 CONFIG_CMD_ELF * bootelf, bootvx
830 CONFIG_CMD_ENV_CALLBACK * display details about env callbacks
831 CONFIG_CMD_ENV_FLAGS * display details about env flags
832 CONFIG_CMD_EXPORTENV * export the environment
833 CONFIG_CMD_EXT2 * ext2 command support
834 CONFIG_CMD_EXT4 * ext4 command support
835 CONFIG_CMD_SAVEENV saveenv
836 CONFIG_CMD_FDC * Floppy Disk Support
837 CONFIG_CMD_FAT * FAT command support
838 CONFIG_CMD_FDOS * Dos diskette Support
839 CONFIG_CMD_FLASH flinfo, erase, protect
840 CONFIG_CMD_FPGA FPGA device initialization support
841 CONFIG_CMD_FUSE * Device fuse support
842 CONFIG_CMD_GETTIME * Get time since boot
843 CONFIG_CMD_GO * the 'go' command (exec code)
844 CONFIG_CMD_GREPENV * search environment
845 CONFIG_CMD_HASH * calculate hash / digest
846 CONFIG_CMD_HWFLOW * RTS/CTS hw flow control
847 CONFIG_CMD_I2C * I2C serial bus support
848 CONFIG_CMD_IDE * IDE harddisk support
849 CONFIG_CMD_IMI iminfo
850 CONFIG_CMD_IMLS List all images found in NOR flash
851 CONFIG_CMD_IMLS_NAND * List all images found in NAND flash
852 CONFIG_CMD_IMMAP * IMMR dump support
853 CONFIG_CMD_IMPORTENV * import an environment
854 CONFIG_CMD_INI * import data from an ini file into the env
855 CONFIG_CMD_IRQ * irqinfo
856 CONFIG_CMD_ITEST Integer/string test of 2 values
857 CONFIG_CMD_JFFS2 * JFFS2 Support
858 CONFIG_CMD_KGDB * kgdb
859 CONFIG_CMD_LDRINFO * ldrinfo (display Blackfin loader)
860 CONFIG_CMD_LINK_LOCAL * link-local IP address auto-configuration
862 CONFIG_CMD_LOADB loadb
863 CONFIG_CMD_LOADS loads
864 CONFIG_CMD_MD5SUM * print md5 message digest
865 (requires CONFIG_CMD_MEMORY and CONFIG_MD5)
866 CONFIG_CMD_MEMINFO * Display detailed memory information
867 CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
869 CONFIG_CMD_MEMTEST * mtest
870 CONFIG_CMD_MISC Misc functions like sleep etc
871 CONFIG_CMD_MMC * MMC memory mapped support
872 CONFIG_CMD_MII * MII utility commands
873 CONFIG_CMD_MTDPARTS * MTD partition support
874 CONFIG_CMD_NAND * NAND support
875 CONFIG_CMD_NET bootp, tftpboot, rarpboot
876 CONFIG_CMD_NFS NFS support
877 CONFIG_CMD_PCA953X * PCA953x I2C gpio commands
878 CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command
879 CONFIG_CMD_PCI * pciinfo
880 CONFIG_CMD_PCMCIA * PCMCIA support
881 CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network
883 CONFIG_CMD_PORTIO * Port I/O
884 CONFIG_CMD_READ * Read raw data from partition
885 CONFIG_CMD_REGINFO * Register dump
886 CONFIG_CMD_RUN run command in env variable
887 CONFIG_CMD_SANDBOX * sb command to access sandbox features
888 CONFIG_CMD_SAVES * save S record dump
889 CONFIG_CMD_SCSI * SCSI Support
890 CONFIG_CMD_SDRAM * print SDRAM configuration information
891 (requires CONFIG_CMD_I2C)
892 CONFIG_CMD_SETGETDCR Support for DCR Register access
894 CONFIG_CMD_SF * Read/write/erase SPI NOR flash
895 CONFIG_CMD_SHA1SUM * print sha1 memory digest
896 (requires CONFIG_CMD_MEMORY)
897 CONFIG_CMD_SOFTSWITCH * Soft switch setting command for BF60x
898 CONFIG_CMD_SOURCE "source" command Support
899 CONFIG_CMD_SPI * SPI serial bus support
900 CONFIG_CMD_TFTPSRV * TFTP transfer in server mode
901 CONFIG_CMD_TFTPPUT * TFTP put command (upload)
902 CONFIG_CMD_TIME * run command and report execution time (ARM specific)
903 CONFIG_CMD_TIMER * access to the system tick timer
904 CONFIG_CMD_USB * USB support
905 CONFIG_CMD_CDP * Cisco Discover Protocol support
906 CONFIG_CMD_MFSL * Microblaze FSL support
907 CONFIG_CMD_XIMG Load part of Multi Image
910 EXAMPLE: If you want all functions except of network
911 support you can write:
913 #include "config_cmd_all.h"
914 #undef CONFIG_CMD_NET
917 fdt (flattened device tree) command: CONFIG_OF_LIBFDT
919 Note: Don't enable the "icache" and "dcache" commands
920 (configuration option CONFIG_CMD_CACHE) unless you know
921 what you (and your U-Boot users) are doing. Data
922 cache cannot be enabled on systems like the 8xx or
923 8260 (where accesses to the IMMR region must be
924 uncached), and it cannot be disabled on all other
925 systems where we (mis-) use the data cache to hold an
926 initial stack and some data.
929 XXX - this list needs to get updated!
931 - Regular expression support:
933 If this variable is defined, U-Boot is linked against
934 the SLRE (Super Light Regular Expression) library,
935 which adds regex support to some commands, as for
936 example "env grep" and "setexpr".
940 If this variable is defined, U-Boot will use a device tree
941 to configure its devices, instead of relying on statically
942 compiled #defines in the board file. This option is
943 experimental and only available on a few boards. The device
944 tree is available in the global data as gd->fdt_blob.
946 U-Boot needs to get its device tree from somewhere. This can
947 be done using one of the two options below:
950 If this variable is defined, U-Boot will embed a device tree
951 binary in its image. This device tree file should be in the
952 board directory and called <soc>-<board>.dts. The binary file
953 is then picked up in board_init_f() and made available through
954 the global data structure as gd->blob.
957 If this variable is defined, U-Boot will build a device tree
958 binary. It will be called u-boot.dtb. Architecture-specific
959 code will locate it at run-time. Generally this works by:
961 cat u-boot.bin u-boot.dtb >image.bin
963 and in fact, U-Boot does this for you, creating a file called
964 u-boot-dtb.bin which is useful in the common case. You can
965 still use the individual files if you need something more
970 If this variable is defined, it enables watchdog
971 support for the SoC. There must be support in the SoC
972 specific code for a watchdog. For the 8xx and 8260
973 CPUs, the SIU Watchdog feature is enabled in the SYPCR
974 register. When supported for a specific SoC is
975 available, then no further board specific code should
979 When using a watchdog circuitry external to the used
980 SoC, then define this variable and provide board
981 specific code for the "hw_watchdog_reset" function.
984 CONFIG_VERSION_VARIABLE
985 If this variable is defined, an environment variable
986 named "ver" is created by U-Boot showing the U-Boot
987 version as printed by the "version" command.
988 Any change to this variable will be reverted at the
993 When CONFIG_CMD_DATE is selected, the type of the RTC
994 has to be selected, too. Define exactly one of the
997 CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
998 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
999 CONFIG_RTC_MC13XXX - use MC13783 or MC13892 RTC
1000 CONFIG_RTC_MC146818 - use MC146818 RTC
1001 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
1002 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
1003 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
1004 CONFIG_RTC_DS164x - use Dallas DS164x RTC
1005 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
1006 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
1007 CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337
1008 CONFIG_SYS_RV3029_TCR - enable trickle charger on
1011 Note that if the RTC uses I2C, then the I2C interface
1012 must also be configured. See I2C Support, below.
1015 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO
1016 CONFIG_PCA953X_INFO - enable pca953x info command
1018 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
1019 chip-ngpio pairs that tell the PCA953X driver the number of
1020 pins supported by a particular chip.
1022 Note that if the GPIO device uses I2C, then the I2C interface
1023 must also be configured. See I2C Support, below.
1025 - Timestamp Support:
1027 When CONFIG_TIMESTAMP is selected, the timestamp
1028 (date and time) of an image is printed by image
1029 commands like bootm or iminfo. This option is
1030 automatically enabled when you select CONFIG_CMD_DATE .
1032 - Partition Labels (disklabels) Supported:
1033 Zero or more of the following:
1034 CONFIG_MAC_PARTITION Apple's MacOS partition table.
1035 CONFIG_DOS_PARTITION MS Dos partition table, traditional on the
1036 Intel architecture, USB sticks, etc.
1037 CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc.
1038 CONFIG_EFI_PARTITION GPT partition table, common when EFI is the
1039 bootloader. Note 2TB partition limit; see
1041 CONFIG_MTD_PARTITIONS Memory Technology Device partition table.
1043 If IDE or SCSI support is enabled (CONFIG_CMD_IDE or
1044 CONFIG_CMD_SCSI) you must configure support for at
1045 least one non-MTD partition type as well.
1048 CONFIG_IDE_RESET_ROUTINE - this is defined in several
1049 board configurations files but used nowhere!
1051 CONFIG_IDE_RESET - is this is defined, IDE Reset will
1052 be performed by calling the function
1053 ide_set_reset(int reset)
1054 which has to be defined in a board specific file
1059 Set this to enable ATAPI support.
1064 Set this to enable support for disks larger than 137GB
1065 Also look at CONFIG_SYS_64BIT_LBA.
1066 Whithout these , LBA48 support uses 32bit variables and will 'only'
1067 support disks up to 2.1TB.
1069 CONFIG_SYS_64BIT_LBA:
1070 When enabled, makes the IDE subsystem use 64bit sector addresses.
1074 At the moment only there is only support for the
1075 SYM53C8XX SCSI controller; define
1076 CONFIG_SCSI_SYM53C8XX to enable it.
1078 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
1079 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
1080 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
1081 maximum numbers of LUNs, SCSI ID's and target
1083 CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
1085 The environment variable 'scsidevs' is set to the number of
1086 SCSI devices found during the last scan.
1088 - NETWORK Support (PCI):
1090 Support for Intel 8254x/8257x gigabit chips.
1093 Utility code for direct access to the SPI bus on Intel 8257x.
1094 This does not do anything useful unless you set at least one
1095 of CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC.
1097 CONFIG_E1000_SPI_GENERIC
1098 Allow generic access to the SPI bus on the Intel 8257x, for
1099 example with the "sspi" command.
1102 Management command for E1000 devices. When used on devices
1103 with SPI support you can reprogram the EEPROM from U-Boot.
1105 CONFIG_E1000_FALLBACK_MAC
1106 default MAC for empty EEPROM after production.
1109 Support for Intel 82557/82559/82559ER chips.
1110 Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM
1111 write routine for first time initialisation.
1114 Support for Digital 2114x chips.
1115 Optional CONFIG_TULIP_SELECT_MEDIA for board specific
1116 modem chip initialisation (KS8761/QS6611).
1119 Support for National dp83815 chips.
1122 Support for National dp8382[01] gigabit chips.
1124 - NETWORK Support (other):
1126 CONFIG_DRIVER_AT91EMAC
1127 Support for AT91RM9200 EMAC.
1130 Define this to use reduced MII inteface
1132 CONFIG_DRIVER_AT91EMAC_QUIET
1133 If this defined, the driver is quiet.
1134 The driver doen't show link status messages.
1136 CONFIG_CALXEDA_XGMAC
1137 Support for the Calxeda XGMAC device
1140 Support for SMSC's LAN91C96 chips.
1142 CONFIG_LAN91C96_BASE
1143 Define this to hold the physical address
1144 of the LAN91C96's I/O space
1146 CONFIG_LAN91C96_USE_32_BIT
1147 Define this to enable 32 bit addressing
1150 Support for SMSC's LAN91C111 chip
1152 CONFIG_SMC91111_BASE
1153 Define this to hold the physical address
1154 of the device (I/O space)
1156 CONFIG_SMC_USE_32_BIT
1157 Define this if data bus is 32 bits
1159 CONFIG_SMC_USE_IOFUNCS
1160 Define this to use i/o functions instead of macros
1161 (some hardware wont work with macros)
1163 CONFIG_DRIVER_TI_EMAC
1164 Support for davinci emac
1166 CONFIG_SYS_DAVINCI_EMAC_PHY_COUNT
1167 Define this if you have more then 3 PHYs.
1170 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
1172 CONFIG_FTGMAC100_EGIGA
1173 Define this to use GE link update with gigabit PHY.
1174 Define this if FTGMAC100 is connected to gigabit PHY.
1175 If your system has 10/100 PHY only, it might not occur
1176 wrong behavior. Because PHY usually return timeout or
1177 useless data when polling gigabit status and gigabit
1178 control registers. This behavior won't affect the
1179 correctnessof 10/100 link speed update.
1182 Support for SMSC's LAN911x and LAN921x chips
1185 Define this to hold the physical address
1186 of the device (I/O space)
1188 CONFIG_SMC911X_32_BIT
1189 Define this if data bus is 32 bits
1191 CONFIG_SMC911X_16_BIT
1192 Define this if data bus is 16 bits. If your processor
1193 automatically converts one 32 bit word to two 16 bit
1194 words you may also try CONFIG_SMC911X_32_BIT.
1197 Support for Renesas on-chip Ethernet controller
1199 CONFIG_SH_ETHER_USE_PORT
1200 Define the number of ports to be used
1202 CONFIG_SH_ETHER_PHY_ADDR
1203 Define the ETH PHY's address
1205 CONFIG_SH_ETHER_CACHE_WRITEBACK
1206 If this option is set, the driver enables cache flush.
1210 Support TPM devices.
1213 Support for i2c bus TPM devices. Only one device
1214 per system is supported at this time.
1216 CONFIG_TPM_TIS_I2C_BUS_NUMBER
1217 Define the the i2c bus number for the TPM device
1219 CONFIG_TPM_TIS_I2C_SLAVE_ADDRESS
1220 Define the TPM's address on the i2c bus
1222 CONFIG_TPM_TIS_I2C_BURST_LIMITATION
1223 Define the burst count bytes upper limit
1225 CONFIG_TPM_ATMEL_TWI
1226 Support for Atmel TWI TPM device. Requires I2C support.
1229 Support for generic parallel port TPM devices. Only one device
1230 per system is supported at this time.
1232 CONFIG_TPM_TIS_BASE_ADDRESS
1233 Base address where the generic TPM device is mapped
1234 to. Contemporary x86 systems usually map it at
1238 Add tpm monitor functions.
1239 Requires CONFIG_TPM. If CONFIG_TPM_AUTH_SESSIONS is set, also
1240 provides monitor access to authorized functions.
1243 Define this to enable the TPM support library which provides
1244 functional interfaces to some TPM commands.
1245 Requires support for a TPM device.
1247 CONFIG_TPM_AUTH_SESSIONS
1248 Define this to enable authorized functions in the TPM library.
1249 Requires CONFIG_TPM and CONFIG_SHA1.
1252 At the moment only the UHCI host controller is
1253 supported (PIP405, MIP405, MPC5200); define
1254 CONFIG_USB_UHCI to enable it.
1255 define CONFIG_USB_KEYBOARD to enable the USB Keyboard
1256 and define CONFIG_USB_STORAGE to enable the USB
1259 Supported are USB Keyboards and USB Floppy drives
1261 MPC5200 USB requires additional defines:
1263 for 528 MHz Clock: 0x0001bbbb
1267 for differential drivers: 0x00001000
1268 for single ended drivers: 0x00005000
1269 for differential drivers on PSC3: 0x00000100
1270 for single ended drivers on PSC3: 0x00004100
1271 CONFIG_SYS_USB_EVENT_POLL
1272 May be defined to allow interrupt polling
1273 instead of using asynchronous interrupts
1275 CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the
1276 txfilltuning field in the EHCI controller on reset.
1278 CONFIG_USB_HUB_MIN_POWER_ON_DELAY defines the minimum
1279 interval for usb hub power-on delay.(minimum 100msec)
1282 Define the below if you wish to use the USB console.
1283 Once firmware is rebuilt from a serial console issue the
1284 command "setenv stdin usbtty; setenv stdout usbtty" and
1285 attach your USB cable. The Unix command "dmesg" should print
1286 it has found a new device. The environment variable usbtty
1287 can be set to gserial or cdc_acm to enable your device to
1288 appear to a USB host as a Linux gserial device or a
1289 Common Device Class Abstract Control Model serial device.
1290 If you select usbtty = gserial you should be able to enumerate
1292 # modprobe usbserial vendor=0xVendorID product=0xProductID
1293 else if using cdc_acm, simply setting the environment
1294 variable usbtty to be cdc_acm should suffice. The following
1295 might be defined in YourBoardName.h
1298 Define this to build a UDC device
1301 Define this to have a tty type of device available to
1302 talk to the UDC device
1305 Define this to enable the high speed support for usb
1306 device and usbtty. If this feature is enabled, a routine
1307 int is_usbd_high_speed(void)
1308 also needs to be defined by the driver to dynamically poll
1309 whether the enumeration has succeded at high speed or full
1312 CONFIG_SYS_CONSOLE_IS_IN_ENV
1313 Define this if you want stdin, stdout &/or stderr to
1317 CONFIG_SYS_USB_EXTC_CLK 0xBLAH
1318 Derive USB clock from external clock "blah"
1319 - CONFIG_SYS_USB_EXTC_CLK 0x02
1321 CONFIG_SYS_USB_BRG_CLK 0xBLAH
1322 Derive USB clock from brgclk
1323 - CONFIG_SYS_USB_BRG_CLK 0x04
1325 If you have a USB-IF assigned VendorID then you may wish to
1326 define your own vendor specific values either in BoardName.h
1327 or directly in usbd_vendor_info.h. If you don't define
1328 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
1329 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
1330 should pretend to be a Linux device to it's target host.
1332 CONFIG_USBD_MANUFACTURER
1333 Define this string as the name of your company for
1334 - CONFIG_USBD_MANUFACTURER "my company"
1336 CONFIG_USBD_PRODUCT_NAME
1337 Define this string as the name of your product
1338 - CONFIG_USBD_PRODUCT_NAME "acme usb device"
1340 CONFIG_USBD_VENDORID
1341 Define this as your assigned Vendor ID from the USB
1342 Implementors Forum. This *must* be a genuine Vendor ID
1343 to avoid polluting the USB namespace.
1344 - CONFIG_USBD_VENDORID 0xFFFF
1346 CONFIG_USBD_PRODUCTID
1347 Define this as the unique Product ID
1349 - CONFIG_USBD_PRODUCTID 0xFFFF
1351 - ULPI Layer Support:
1352 The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via
1353 the generic ULPI layer. The generic layer accesses the ULPI PHY
1354 via the platform viewport, so you need both the genric layer and
1355 the viewport enabled. Currently only Chipidea/ARC based
1356 viewport is supported.
1357 To enable the ULPI layer support, define CONFIG_USB_ULPI and
1358 CONFIG_USB_ULPI_VIEWPORT in your board configuration file.
1359 If your ULPI phy needs a different reference clock than the
1360 standard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to
1361 the appropriate value in Hz.
1364 The MMC controller on the Intel PXA is supported. To
1365 enable this define CONFIG_MMC. The MMC can be
1366 accessed from the boot prompt by mapping the device
1367 to physical memory similar to flash. Command line is
1368 enabled with CONFIG_CMD_MMC. The MMC driver also works with
1369 the FAT fs. This is enabled with CONFIG_CMD_FAT.
1372 Support for Renesas on-chip MMCIF controller
1374 CONFIG_SH_MMCIF_ADDR
1375 Define the base address of MMCIF registers
1378 Define the clock frequency for MMCIF
1380 - USB Device Firmware Update (DFU) class support:
1382 This enables the USB portion of the DFU USB class
1385 This enables the command "dfu" which is used to have
1386 U-Boot create a DFU class device via USB. This command
1387 requires that the "dfu_alt_info" environment variable be
1388 set and define the alt settings to expose to the host.
1391 This enables support for exposing (e)MMC devices via DFU.
1394 This enables support for exposing NAND devices via DFU.
1396 CONFIG_SYS_DFU_DATA_BUF_SIZE
1397 Dfu transfer uses a buffer before writing data to the
1398 raw storage device. Make the size (in bytes) of this buffer
1399 configurable. The size of this buffer is also configurable
1400 through the "dfu_bufsiz" environment variable.
1402 CONFIG_SYS_DFU_MAX_FILE_SIZE
1403 When updating files rather than the raw storage device,
1404 we use a static buffer to copy the file into and then write
1405 the buffer once we've been given the whole file. Define
1406 this to the maximum filesize (in bytes) for the buffer.
1407 Default is 4 MiB if undefined.
1409 - Journaling Flash filesystem support:
1410 CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
1411 CONFIG_JFFS2_NAND_DEV
1412 Define these for a default partition on a NAND device
1414 CONFIG_SYS_JFFS2_FIRST_SECTOR,
1415 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
1416 Define these for a default partition on a NOR device
1418 CONFIG_SYS_JFFS_CUSTOM_PART
1419 Define this to create an own partition. You have to provide a
1420 function struct part_info* jffs2_part_info(int part_num)
1422 If you define only one JFFS2 partition you may also want to
1423 #define CONFIG_SYS_JFFS_SINGLE_PART 1
1424 to disable the command chpart. This is the default when you
1425 have not defined a custom partition
1427 - FAT(File Allocation Table) filesystem write function support:
1430 Define this to enable support for saving memory data as a
1431 file in FAT formatted partition.
1433 This will also enable the command "fatwrite" enabling the
1434 user to write files to FAT.
1436 CBFS (Coreboot Filesystem) support
1439 Define this to enable support for reading from a Coreboot
1440 filesystem. Available commands are cbfsinit, cbfsinfo, cbfsls
1446 Define this to enable standard (PC-Style) keyboard
1450 Standard PC keyboard driver with US (is default) and
1451 GERMAN key layout (switch via environment 'keymap=de') support.
1452 Export function i8042_kbd_init, i8042_tstc and i8042_getc
1453 for cfb_console. Supports cursor blinking.
1456 Enables a Chrome OS keyboard using the CROS_EC interface.
1457 This uses CROS_EC to communicate with a second microcontroller
1458 which provides key scans on request.
1463 Define this to enable video support (for output to
1466 CONFIG_VIDEO_CT69000
1468 Enable Chips & Technologies 69000 Video chip
1470 CONFIG_VIDEO_SMI_LYNXEM
1471 Enable Silicon Motion SMI 712/710/810 Video chip. The
1472 video output is selected via environment 'videoout'
1473 (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
1476 For the CT69000 and SMI_LYNXEM drivers, videomode is
1477 selected via environment 'videomode'. Two different ways
1479 - "videomode=num" 'num' is a standard LiLo mode numbers.
1480 Following standard modes are supported (* is default):
1482 Colors 640x480 800x600 1024x768 1152x864 1280x1024
1483 -------------+---------------------------------------------
1484 8 bits | 0x301* 0x303 0x305 0x161 0x307
1485 15 bits | 0x310 0x313 0x316 0x162 0x319
1486 16 bits | 0x311 0x314 0x317 0x163 0x31A
1487 24 bits | 0x312 0x315 0x318 ? 0x31B
1488 -------------+---------------------------------------------
1489 (i.e. setenv videomode 317; saveenv; reset;)
1491 - "videomode=bootargs" all the video parameters are parsed
1492 from the bootargs. (See drivers/video/videomodes.c)
1495 CONFIG_VIDEO_SED13806
1496 Enable Epson SED13806 driver. This driver supports 8bpp
1497 and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
1498 or CONFIG_VIDEO_SED13806_16BPP
1501 Enable the Freescale DIU video driver. Reference boards for
1502 SOCs that have a DIU should define this macro to enable DIU
1503 support, and should also define these other macros:
1509 CONFIG_VIDEO_SW_CURSOR
1510 CONFIG_VGA_AS_SINGLE_DEVICE
1512 CONFIG_VIDEO_BMP_LOGO
1514 The DIU driver will look for the 'video-mode' environment
1515 variable, and if defined, enable the DIU as a console during
1516 boot. See the documentation file README.video for a
1517 description of this variable.
1521 Enable the VGA video / BIOS for x86. The alternative if you
1522 are using coreboot is to use the coreboot frame buffer
1529 Define this to enable a custom keyboard support.
1530 This simply calls drv_keyboard_init() which must be
1531 defined in your board-specific files.
1532 The only board using this so far is RBC823.
1534 - LCD Support: CONFIG_LCD
1536 Define this to enable LCD support (for output to LCD
1537 display); also select one of the supported displays
1538 by defining one of these:
1542 HITACHI TX09D70VM1CCA, 3.5", 240x320.
1544 CONFIG_NEC_NL6448AC33:
1546 NEC NL6448AC33-18. Active, color, single scan.
1548 CONFIG_NEC_NL6448BC20
1550 NEC NL6448BC20-08. 6.5", 640x480.
1551 Active, color, single scan.
1553 CONFIG_NEC_NL6448BC33_54
1555 NEC NL6448BC33-54. 10.4", 640x480.
1556 Active, color, single scan.
1560 Sharp 320x240. Active, color, single scan.
1561 It isn't 16x9, and I am not sure what it is.
1563 CONFIG_SHARP_LQ64D341
1565 Sharp LQ64D341 display, 640x480.
1566 Active, color, single scan.
1570 HLD1045 display, 640x480.
1571 Active, color, single scan.
1575 Optrex CBL50840-2 NF-FW 99 22 M5
1577 Hitachi LMG6912RPFC-00T
1581 320x240. Black & white.
1583 Normally display is black on white background; define
1584 CONFIG_SYS_WHITE_ON_BLACK to get it inverted.
1586 CONFIG_LCD_ALIGNMENT
1588 Normally the LCD is page-aligned (tyically 4KB). If this is
1589 defined then the LCD will be aligned to this value instead.
1590 For ARM it is sometimes useful to use MMU_SECTION_SIZE
1591 here, since it is cheaper to change data cache settings on
1592 a per-section basis.
1594 CONFIG_CONSOLE_SCROLL_LINES
1596 When the console need to be scrolled, this is the number of
1597 lines to scroll by. It defaults to 1. Increasing this makes
1598 the console jump but can help speed up operation when scrolling
1603 Support drawing of RLE8-compressed bitmaps on the LCD.
1607 Enables an 'i2c edid' command which can read EDID
1608 information over I2C from an attached LCD display.
1610 - Splash Screen Support: CONFIG_SPLASH_SCREEN
1612 If this option is set, the environment is checked for
1613 a variable "splashimage". If found, the usual display
1614 of logo, copyright and system information on the LCD
1615 is suppressed and the BMP image at the address
1616 specified in "splashimage" is loaded instead. The
1617 console is redirected to the "nulldev", too. This
1618 allows for a "silent" boot where a splash screen is
1619 loaded very quickly after power-on.
1621 CONFIG_SPLASHIMAGE_GUARD
1623 If this option is set, then U-Boot will prevent the environment
1624 variable "splashimage" from being set to a problematic address
1625 (see README.displaying-bmps and README.arm-unaligned-accesses).
1626 This option is useful for targets where, due to alignment
1627 restrictions, an improperly aligned BMP image will cause a data
1628 abort. If you think you will not have problems with unaligned
1629 accesses (for example because your toolchain prevents them)
1630 there is no need to set this option.
1632 CONFIG_SPLASH_SCREEN_ALIGN
1634 If this option is set the splash image can be freely positioned
1635 on the screen. Environment variable "splashpos" specifies the
1636 position as "x,y". If a positive number is given it is used as
1637 number of pixel from left/top. If a negative number is given it
1638 is used as number of pixel from right/bottom. You can also
1639 specify 'm' for centering the image.
1642 setenv splashpos m,m
1643 => image at center of screen
1645 setenv splashpos 30,20
1646 => image at x = 30 and y = 20
1648 setenv splashpos -10,m
1649 => vertically centered image
1650 at x = dspWidth - bmpWidth - 9
1652 - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
1654 If this option is set, additionally to standard BMP
1655 images, gzipped BMP images can be displayed via the
1656 splashscreen support or the bmp command.
1658 - Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
1660 If this option is set, 8-bit RLE compressed BMP images
1661 can be displayed via the splashscreen support or the
1664 - Do compresssing for memory range:
1667 If this option is set, it would use zlib deflate method
1668 to compress the specified memory at its best effort.
1670 - Compression support:
1673 If this option is set, support for bzip2 compressed
1674 images is included. If not, only uncompressed and gzip
1675 compressed images are supported.
1677 NOTE: the bzip2 algorithm requires a lot of RAM, so
1678 the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
1683 If this option is set, support for lzma compressed
1686 Note: The LZMA algorithm adds between 2 and 4KB of code and it
1687 requires an amount of dynamic memory that is given by the
1690 (1846 + 768 << (lc + lp)) * sizeof(uint16)
1692 Where lc and lp stand for, respectively, Literal context bits
1693 and Literal pos bits.
1695 This value is upper-bounded by 14MB in the worst case. Anyway,
1696 for a ~4MB large kernel image, we have lc=3 and lp=0 for a
1697 total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is
1698 a very small buffer.
1700 Use the lzmainfo tool to determinate the lc and lp values and
1701 then calculate the amount of needed dynamic memory (ensuring
1702 the appropriate CONFIG_SYS_MALLOC_LEN value).
1707 The address of PHY on MII bus.
1709 CONFIG_PHY_CLOCK_FREQ (ppc4xx)
1711 The clock frequency of the MII bus
1715 If this option is set, support for speed/duplex
1716 detection of gigabit PHY is included.
1718 CONFIG_PHY_RESET_DELAY
1720 Some PHY like Intel LXT971A need extra delay after
1721 reset before any MII register access is possible.
1722 For such PHY, set this option to the usec delay
1723 required. (minimum 300usec for LXT971A)
1725 CONFIG_PHY_CMD_DELAY (ppc4xx)
1727 Some PHY like Intel LXT971A need extra delay after
1728 command issued before MII status register can be read
1738 Define a default value for Ethernet address to use
1739 for the respective Ethernet interface, in case this
1740 is not determined automatically.
1745 Define a default value for the IP address to use for
1746 the default Ethernet interface, in case this is not
1747 determined through e.g. bootp.
1748 (Environment variable "ipaddr")
1750 - Server IP address:
1753 Defines a default value for the IP address of a TFTP
1754 server to contact when using the "tftboot" command.
1755 (Environment variable "serverip")
1757 CONFIG_KEEP_SERVERADDR
1759 Keeps the server's MAC address, in the env 'serveraddr'
1760 for passing to bootargs (like Linux's netconsole option)
1762 - Gateway IP address:
1765 Defines a default value for the IP address of the
1766 default router where packets to other networks are
1768 (Environment variable "gatewayip")
1773 Defines a default value for the subnet mask (or
1774 routing prefix) which is used to determine if an IP
1775 address belongs to the local subnet or needs to be
1776 forwarded through a router.
1777 (Environment variable "netmask")
1779 - Multicast TFTP Mode:
1782 Defines whether you want to support multicast TFTP as per
1783 rfc-2090; for example to work with atftp. Lets lots of targets
1784 tftp down the same boot image concurrently. Note: the Ethernet
1785 driver in use must provide a function: mcast() to join/leave a
1788 - BOOTP Recovery Mode:
1789 CONFIG_BOOTP_RANDOM_DELAY
1791 If you have many targets in a network that try to
1792 boot using BOOTP, you may want to avoid that all
1793 systems send out BOOTP requests at precisely the same
1794 moment (which would happen for instance at recovery
1795 from a power failure, when all systems will try to
1796 boot, thus flooding the BOOTP server. Defining
1797 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
1798 inserted before sending out BOOTP requests. The
1799 following delays are inserted then:
1801 1st BOOTP request: delay 0 ... 1 sec
1802 2nd BOOTP request: delay 0 ... 2 sec
1803 3rd BOOTP request: delay 0 ... 4 sec
1805 BOOTP requests: delay 0 ... 8 sec
1807 - DHCP Advanced Options:
1808 You can fine tune the DHCP functionality by defining
1809 CONFIG_BOOTP_* symbols:
1811 CONFIG_BOOTP_SUBNETMASK
1812 CONFIG_BOOTP_GATEWAY
1813 CONFIG_BOOTP_HOSTNAME
1814 CONFIG_BOOTP_NISDOMAIN
1815 CONFIG_BOOTP_BOOTPATH
1816 CONFIG_BOOTP_BOOTFILESIZE
1819 CONFIG_BOOTP_SEND_HOSTNAME
1820 CONFIG_BOOTP_NTPSERVER
1821 CONFIG_BOOTP_TIMEOFFSET
1822 CONFIG_BOOTP_VENDOREX
1823 CONFIG_BOOTP_MAY_FAIL
1825 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
1826 environment variable, not the BOOTP server.
1828 CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found
1829 after the configured retry count, the call will fail
1830 instead of starting over. This can be used to fail over
1831 to Link-local IP address configuration if the DHCP server
1834 CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
1835 serverip from a DHCP server, it is possible that more
1836 than one DNS serverip is offered to the client.
1837 If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1838 serverip will be stored in the additional environment
1839 variable "dnsip2". The first DNS serverip is always
1840 stored in the variable "dnsip", when CONFIG_BOOTP_DNS
1843 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
1844 to do a dynamic update of a DNS server. To do this, they
1845 need the hostname of the DHCP requester.
1846 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
1847 of the "hostname" environment variable is passed as
1848 option 12 to the DHCP server.
1850 CONFIG_BOOTP_DHCP_REQUEST_DELAY
1852 A 32bit value in microseconds for a delay between
1853 receiving a "DHCP Offer" and sending the "DHCP Request".
1854 This fixes a problem with certain DHCP servers that don't
1855 respond 100% of the time to a "DHCP request". E.g. On an
1856 AT91RM9200 processor running at 180MHz, this delay needed
1857 to be *at least* 15,000 usec before a Windows Server 2003
1858 DHCP server would reply 100% of the time. I recommend at
1859 least 50,000 usec to be safe. The alternative is to hope
1860 that one of the retries will be successful but note that
1861 the DHCP timeout and retry process takes a longer than
1864 - Link-local IP address negotiation:
1865 Negotiate with other link-local clients on the local network
1866 for an address that doesn't require explicit configuration.
1867 This is especially useful if a DHCP server cannot be guaranteed
1868 to exist in all environments that the device must operate.
1870 See doc/README.link-local for more information.
1873 CONFIG_CDP_DEVICE_ID
1875 The device id used in CDP trigger frames.
1877 CONFIG_CDP_DEVICE_ID_PREFIX
1879 A two character string which is prefixed to the MAC address
1884 A printf format string which contains the ascii name of
1885 the port. Normally is set to "eth%d" which sets
1886 eth0 for the first Ethernet, eth1 for the second etc.
1888 CONFIG_CDP_CAPABILITIES
1890 A 32bit integer which indicates the device capabilities;
1891 0x00000010 for a normal host which does not forwards.
1895 An ascii string containing the version of the software.
1899 An ascii string containing the name of the platform.
1903 A 32bit integer sent on the trigger.
1905 CONFIG_CDP_POWER_CONSUMPTION
1907 A 16bit integer containing the power consumption of the
1908 device in .1 of milliwatts.
1910 CONFIG_CDP_APPLIANCE_VLAN_TYPE
1912 A byte containing the id of the VLAN.
1914 - Status LED: CONFIG_STATUS_LED
1916 Several configurations allow to display the current
1917 status using a LED. For instance, the LED will blink
1918 fast while running U-Boot code, stop blinking as
1919 soon as a reply to a BOOTP request was received, and
1920 start blinking slow once the Linux kernel is running
1921 (supported by a status LED driver in the Linux
1922 kernel). Defining CONFIG_STATUS_LED enables this
1925 - CAN Support: CONFIG_CAN_DRIVER
1927 Defining CONFIG_CAN_DRIVER enables CAN driver support
1928 on those systems that support this (optional)
1929 feature, like the TQM8xxL modules.
1931 - I2C Support: CONFIG_SYS_I2C
1933 This enable the NEW i2c subsystem, and will allow you to use
1934 i2c commands at the u-boot command line (as long as you set
1935 CONFIG_CMD_I2C in CONFIG_COMMANDS) and communicate with i2c
1936 based realtime clock chips or other i2c devices. See
1937 common/cmd_i2c.c for a description of the command line
1940 ported i2c driver to the new framework:
1941 - drivers/i2c/soft_i2c.c:
1942 - activate first bus with CONFIG_SYS_I2C_SOFT define
1943 CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE
1944 for defining speed and slave address
1945 - activate second bus with I2C_SOFT_DECLARATIONS2 define
1946 CONFIG_SYS_I2C_SOFT_SPEED_2 and CONFIG_SYS_I2C_SOFT_SLAVE_2
1947 for defining speed and slave address
1948 - activate third bus with I2C_SOFT_DECLARATIONS3 define
1949 CONFIG_SYS_I2C_SOFT_SPEED_3 and CONFIG_SYS_I2C_SOFT_SLAVE_3
1950 for defining speed and slave address
1951 - activate fourth bus with I2C_SOFT_DECLARATIONS4 define
1952 CONFIG_SYS_I2C_SOFT_SPEED_4 and CONFIG_SYS_I2C_SOFT_SLAVE_4
1953 for defining speed and slave address
1955 - drivers/i2c/fsl_i2c.c:
1956 - activate i2c driver with CONFIG_SYS_I2C_FSL
1957 define CONFIG_SYS_FSL_I2C_OFFSET for setting the register
1958 offset CONFIG_SYS_FSL_I2C_SPEED for the i2c speed and
1959 CONFIG_SYS_FSL_I2C_SLAVE for the slave addr of the first
1961 - If your board supports a second fsl i2c bus, define
1962 CONFIG_SYS_FSL_I2C2_OFFSET for the register offset
1963 CONFIG_SYS_FSL_I2C2_SPEED for the speed and
1964 CONFIG_SYS_FSL_I2C2_SLAVE for the slave address of the
1967 - drivers/i2c/tegra_i2c.c:
1968 - activate this driver with CONFIG_SYS_I2C_TEGRA
1969 - This driver adds 4 i2c buses with a fix speed from
1970 100000 and the slave addr 0!
1972 - drivers/i2c/ppc4xx_i2c.c
1973 - activate this driver with CONFIG_SYS_I2C_PPC4XX
1974 - CONFIG_SYS_I2C_PPC4XX_CH0 activate hardware channel 0
1975 - CONFIG_SYS_I2C_PPC4XX_CH1 activate hardware channel 1
1979 CONFIG_SYS_NUM_I2C_BUSES
1980 Hold the number of i2c busses you want to use. If you
1981 don't use/have i2c muxes on your i2c bus, this
1982 is equal to CONFIG_SYS_NUM_I2C_ADAPTERS, and you can
1985 CONFIG_SYS_I2C_DIRECT_BUS
1986 define this, if you don't use i2c muxes on your hardware.
1987 if CONFIG_SYS_I2C_MAX_HOPS is not defined or == 0 you can
1990 CONFIG_SYS_I2C_MAX_HOPS
1991 define how many muxes are maximal consecutively connected
1992 on one i2c bus. If you not use i2c muxes, omit this
1995 CONFIG_SYS_I2C_BUSES
1996 hold a list of busses you want to use, only used if
1997 CONFIG_SYS_I2C_DIRECT_BUS is not defined, for example
1998 a board with CONFIG_SYS_I2C_MAX_HOPS = 1 and
1999 CONFIG_SYS_NUM_I2C_BUSES = 9:
2001 CONFIG_SYS_I2C_BUSES {{0, {I2C_NULL_HOP}}, \
2002 {0, {{I2C_MUX_PCA9547, 0x70, 1}}}, \
2003 {0, {{I2C_MUX_PCA9547, 0x70, 2}}}, \
2004 {0, {{I2C_MUX_PCA9547, 0x70, 3}}}, \
2005 {0, {{I2C_MUX_PCA9547, 0x70, 4}}}, \
2006 {0, {{I2C_MUX_PCA9547, 0x70, 5}}}, \
2007 {1, {I2C_NULL_HOP}}, \
2008 {1, {{I2C_MUX_PCA9544, 0x72, 1}}}, \
2009 {1, {{I2C_MUX_PCA9544, 0x72, 2}}}, \
2013 bus 0 on adapter 0 without a mux
2014 bus 1 on adapter 0 with a PCA9547 on address 0x70 port 1
2015 bus 2 on adapter 0 with a PCA9547 on address 0x70 port 2
2016 bus 3 on adapter 0 with a PCA9547 on address 0x70 port 3
2017 bus 4 on adapter 0 with a PCA9547 on address 0x70 port 4
2018 bus 5 on adapter 0 with a PCA9547 on address 0x70 port 5
2019 bus 6 on adapter 1 without a mux
2020 bus 7 on adapter 1 with a PCA9544 on address 0x72 port 1
2021 bus 8 on adapter 1 with a PCA9544 on address 0x72 port 2
2023 If you do not have i2c muxes on your board, omit this define.
2025 - Legacy I2C Support: CONFIG_HARD_I2C
2027 NOTE: It is intended to move drivers to CONFIG_SYS_I2C which
2028 provides the following compelling advantages:
2030 - more than one i2c adapter is usable
2031 - approved multibus support
2032 - better i2c mux support
2034 ** Please consider updating your I2C driver now. **
2036 These enable legacy I2C serial bus commands. Defining
2037 CONFIG_HARD_I2C will include the appropriate I2C driver
2038 for the selected CPU.
2040 This will allow you to use i2c commands at the u-boot
2041 command line (as long as you set CONFIG_CMD_I2C in
2042 CONFIG_COMMANDS) and communicate with i2c based realtime
2043 clock chips. See common/cmd_i2c.c for a description of the
2044 command line interface.
2046 CONFIG_HARD_I2C selects a hardware I2C controller.
2048 There are several other quantities that must also be
2049 defined when you define CONFIG_HARD_I2C.
2051 In both cases you will need to define CONFIG_SYS_I2C_SPEED
2052 to be the frequency (in Hz) at which you wish your i2c bus
2053 to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie
2054 the CPU's i2c node address).
2056 Now, the u-boot i2c code for the mpc8xx
2057 (arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node
2058 and so its address should therefore be cleared to 0 (See,
2059 eg, MPC823e User's Manual p.16-473). So, set
2060 CONFIG_SYS_I2C_SLAVE to 0.
2062 CONFIG_SYS_I2C_INIT_MPC5XXX
2064 When a board is reset during an i2c bus transfer
2065 chips might think that the current transfer is still
2066 in progress. Reset the slave devices by sending start
2067 commands until the slave device responds.
2069 That's all that's required for CONFIG_HARD_I2C.
2071 If you use the software i2c interface (CONFIG_SYS_I2C_SOFT)
2072 then the following macros need to be defined (examples are
2073 from include/configs/lwmon.h):
2077 (Optional). Any commands necessary to enable the I2C
2078 controller or configure ports.
2080 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
2084 (Only for MPC8260 CPU). The I/O port to use (the code
2085 assumes both bits are on the same port). Valid values
2086 are 0..3 for ports A..D.
2090 The code necessary to make the I2C data line active
2091 (driven). If the data line is open collector, this
2094 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
2098 The code necessary to make the I2C data line tri-stated
2099 (inactive). If the data line is open collector, this
2102 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
2106 Code that returns true if the I2C data line is high,
2109 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
2113 If <bit> is true, sets the I2C data line high. If it
2114 is false, it clears it (low).
2116 eg: #define I2C_SDA(bit) \
2117 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
2118 else immr->im_cpm.cp_pbdat &= ~PB_SDA
2122 If <bit> is true, sets the I2C clock line high. If it
2123 is false, it clears it (low).
2125 eg: #define I2C_SCL(bit) \
2126 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
2127 else immr->im_cpm.cp_pbdat &= ~PB_SCL
2131 This delay is invoked four times per clock cycle so this
2132 controls the rate of data transfer. The data rate thus
2133 is 1 / (I2C_DELAY * 4). Often defined to be something
2136 #define I2C_DELAY udelay(2)
2138 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
2140 If your arch supports the generic GPIO framework (asm/gpio.h),
2141 then you may alternatively define the two GPIOs that are to be
2142 used as SCL / SDA. Any of the previous I2C_xxx macros will
2143 have GPIO-based defaults assigned to them as appropriate.
2145 You should define these to the GPIO value as given directly to
2146 the generic GPIO functions.
2148 CONFIG_SYS_I2C_INIT_BOARD
2150 When a board is reset during an i2c bus transfer
2151 chips might think that the current transfer is still
2152 in progress. On some boards it is possible to access
2153 the i2c SCLK line directly, either by using the
2154 processor pin as a GPIO or by having a second pin
2155 connected to the bus. If this option is defined a
2156 custom i2c_init_board() routine in boards/xxx/board.c
2157 is run early in the boot sequence.
2159 CONFIG_SYS_I2C_BOARD_LATE_INIT
2161 An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is
2162 defined a custom i2c_board_late_init() routine in
2163 boards/xxx/board.c is run AFTER the operations in i2c_init()
2164 is completed. This callpoint can be used to unreset i2c bus
2165 using CPU i2c controller register accesses for CPUs whose i2c
2166 controller provide such a method. It is called at the end of
2167 i2c_init() to allow i2c_init operations to setup the i2c bus
2168 controller on the CPU (e.g. setting bus speed & slave address).
2170 CONFIG_I2CFAST (PPC405GP|PPC405EP only)
2172 This option enables configuration of bi_iic_fast[] flags
2173 in u-boot bd_info structure based on u-boot environment
2174 variable "i2cfast". (see also i2cfast)
2176 CONFIG_I2C_MULTI_BUS
2178 This option allows the use of multiple I2C buses, each of which
2179 must have a controller. At any point in time, only one bus is
2180 active. To switch to a different bus, use the 'i2c dev' command.
2181 Note that bus numbering is zero-based.
2183 CONFIG_SYS_I2C_NOPROBES
2185 This option specifies a list of I2C devices that will be skipped
2186 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS
2187 is set, specify a list of bus-device pairs. Otherwise, specify
2188 a 1D array of device addresses
2191 #undef CONFIG_I2C_MULTI_BUS
2192 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}
2194 will skip addresses 0x50 and 0x68 on a board with one I2C bus
2196 #define CONFIG_I2C_MULTI_BUS
2197 #define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
2199 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
2201 CONFIG_SYS_SPD_BUS_NUM
2203 If defined, then this indicates the I2C bus number for DDR SPD.
2204 If not defined, then U-Boot assumes that SPD is on I2C bus 0.
2206 CONFIG_SYS_RTC_BUS_NUM
2208 If defined, then this indicates the I2C bus number for the RTC.
2209 If not defined, then U-Boot assumes that RTC is on I2C bus 0.
2211 CONFIG_SYS_DTT_BUS_NUM
2213 If defined, then this indicates the I2C bus number for the DTT.
2214 If not defined, then U-Boot assumes that DTT is on I2C bus 0.
2216 CONFIG_SYS_I2C_DTT_ADDR:
2218 If defined, specifies the I2C address of the DTT device.
2219 If not defined, then U-Boot uses predefined value for
2220 specified DTT device.
2222 CONFIG_SOFT_I2C_READ_REPEATED_START
2224 defining this will force the i2c_read() function in
2225 the soft_i2c driver to perform an I2C repeated start
2226 between writing the address pointer and reading the
2227 data. If this define is omitted the default behaviour
2228 of doing a stop-start sequence will be used. Most I2C
2229 devices can use either method, but some require one or
2232 - SPI Support: CONFIG_SPI
2234 Enables SPI driver (so far only tested with
2235 SPI EEPROM, also an instance works with Crystal A/D and
2236 D/As on the SACSng board)
2240 Enables the driver for SPI controller on SuperH. Currently
2241 only SH7757 is supported.
2245 Enables extended (16-bit) SPI EEPROM addressing.
2246 (symmetrical to CONFIG_I2C_X)
2250 Enables a software (bit-bang) SPI driver rather than
2251 using hardware support. This is a general purpose
2252 driver that only requires three general I/O port pins
2253 (two outputs, one input) to function. If this is
2254 defined, the board configuration must define several
2255 SPI configuration items (port pins to use, etc). For
2256 an example, see include/configs/sacsng.h.
2260 Enables a hardware SPI driver for general-purpose reads
2261 and writes. As with CONFIG_SOFT_SPI, the board configuration
2262 must define a list of chip-select function pointers.
2263 Currently supported on some MPC8xxx processors. For an
2264 example, see include/configs/mpc8349emds.h.
2268 Enables the driver for the SPI controllers on i.MX and MXC
2269 SoCs. Currently i.MX31/35/51 are supported.
2271 - FPGA Support: CONFIG_FPGA
2273 Enables FPGA subsystem.
2275 CONFIG_FPGA_<vendor>
2277 Enables support for specific chip vendors.
2280 CONFIG_FPGA_<family>
2282 Enables support for FPGA family.
2283 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
2287 Specify the number of FPGA devices to support.
2289 CONFIG_SYS_FPGA_PROG_FEEDBACK
2291 Enable printing of hash marks during FPGA configuration.
2293 CONFIG_SYS_FPGA_CHECK_BUSY
2295 Enable checks on FPGA configuration interface busy
2296 status by the configuration function. This option
2297 will require a board or device specific function to
2302 If defined, a function that provides delays in the FPGA
2303 configuration driver.
2305 CONFIG_SYS_FPGA_CHECK_CTRLC
2306 Allow Control-C to interrupt FPGA configuration
2308 CONFIG_SYS_FPGA_CHECK_ERROR
2310 Check for configuration errors during FPGA bitfile
2311 loading. For example, abort during Virtex II
2312 configuration if the INIT_B line goes low (which
2313 indicated a CRC error).
2315 CONFIG_SYS_FPGA_WAIT_INIT
2317 Maximum time to wait for the INIT_B line to deassert
2318 after PROB_B has been deasserted during a Virtex II
2319 FPGA configuration sequence. The default time is 500
2322 CONFIG_SYS_FPGA_WAIT_BUSY
2324 Maximum time to wait for BUSY to deassert during
2325 Virtex II FPGA configuration. The default is 5 ms.
2327 CONFIG_SYS_FPGA_WAIT_CONFIG
2329 Time to wait after FPGA configuration. The default is
2332 - Configuration Management:
2335 If defined, this string will be added to the U-Boot
2336 version information (U_BOOT_VERSION)
2338 - Vendor Parameter Protection:
2340 U-Boot considers the values of the environment
2341 variables "serial#" (Board Serial Number) and
2342 "ethaddr" (Ethernet Address) to be parameters that
2343 are set once by the board vendor / manufacturer, and
2344 protects these variables from casual modification by
2345 the user. Once set, these variables are read-only,
2346 and write or delete attempts are rejected. You can
2347 change this behaviour:
2349 If CONFIG_ENV_OVERWRITE is #defined in your config
2350 file, the write protection for vendor parameters is
2351 completely disabled. Anybody can change or delete
2354 Alternatively, if you #define _both_ CONFIG_ETHADDR
2355 _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
2356 Ethernet address is installed in the environment,
2357 which can be changed exactly ONCE by the user. [The
2358 serial# is unaffected by this, i. e. it remains
2361 The same can be accomplished in a more flexible way
2362 for any variable by configuring the type of access
2363 to allow for those variables in the ".flags" variable
2364 or define CONFIG_ENV_FLAGS_LIST_STATIC.
2369 Define this variable to enable the reservation of
2370 "protected RAM", i. e. RAM which is not overwritten
2371 by U-Boot. Define CONFIG_PRAM to hold the number of
2372 kB you want to reserve for pRAM. You can overwrite
2373 this default value by defining an environment
2374 variable "pram" to the number of kB you want to
2375 reserve. Note that the board info structure will
2376 still show the full amount of RAM. If pRAM is
2377 reserved, a new environment variable "mem" will
2378 automatically be defined to hold the amount of
2379 remaining RAM in a form that can be passed as boot
2380 argument to Linux, for instance like that:
2382 setenv bootargs ... mem=\${mem}
2385 This way you can tell Linux not to use this memory,
2386 either, which results in a memory region that will
2387 not be affected by reboots.
2389 *WARNING* If your board configuration uses automatic
2390 detection of the RAM size, you must make sure that
2391 this memory test is non-destructive. So far, the
2392 following board configurations are known to be
2395 IVMS8, IVML24, SPD8xx, TQM8xxL,
2396 HERMES, IP860, RPXlite, LWMON,
2399 - Access to physical memory region (> 4GB)
2400 Some basic support is provided for operations on memory not
2401 normally accessible to U-Boot - e.g. some architectures
2402 support access to more than 4GB of memory on 32-bit
2403 machines using physical address extension or similar.
2404 Define CONFIG_PHYSMEM to access this basic support, which
2405 currently only supports clearing the memory.
2410 Define this variable to stop the system in case of a
2411 fatal error, so that you have to reset it manually.
2412 This is probably NOT a good idea for an embedded
2413 system where you want the system to reboot
2414 automatically as fast as possible, but it may be
2415 useful during development since you can try to debug
2416 the conditions that lead to the situation.
2418 CONFIG_NET_RETRY_COUNT
2420 This variable defines the number of retries for
2421 network operations like ARP, RARP, TFTP, or BOOTP
2422 before giving up the operation. If not defined, a
2423 default value of 5 is used.
2427 Timeout waiting for an ARP reply in milliseconds.
2431 Timeout in milliseconds used in NFS protocol.
2432 If you encounter "ERROR: Cannot umount" in nfs command,
2433 try longer timeout such as
2434 #define CONFIG_NFS_TIMEOUT 10000UL
2436 - Command Interpreter:
2437 CONFIG_AUTO_COMPLETE
2439 Enable auto completion of commands using TAB.
2441 Note that this feature has NOT been implemented yet
2442 for the "hush" shell.
2445 CONFIG_SYS_HUSH_PARSER
2447 Define this variable to enable the "hush" shell (from
2448 Busybox) as command line interpreter, thus enabling
2449 powerful command line syntax like
2450 if...then...else...fi conditionals or `&&' and '||'
2451 constructs ("shell scripts").
2453 If undefined, you get the old, much simpler behaviour
2454 with a somewhat smaller memory footprint.
2457 CONFIG_SYS_PROMPT_HUSH_PS2
2459 This defines the secondary prompt string, which is
2460 printed when the command interpreter needs more input
2461 to complete a command. Usually "> ".
2465 In the current implementation, the local variables
2466 space and global environment variables space are
2467 separated. Local variables are those you define by
2468 simply typing `name=value'. To access a local
2469 variable later on, you have write `$name' or
2470 `${name}'; to execute the contents of a variable
2471 directly type `$name' at the command prompt.
2473 Global environment variables are those you use
2474 setenv/printenv to work with. To run a command stored
2475 in such a variable, you need to use the run command,
2476 and you must not use the '$' sign to access them.
2478 To store commands and special characters in a
2479 variable, please use double quotation marks
2480 surrounding the whole text of the variable, instead
2481 of the backslashes before semicolons and special
2484 - Commandline Editing and History:
2485 CONFIG_CMDLINE_EDITING
2487 Enable editing and History functions for interactive
2488 commandline input operations
2490 - Default Environment:
2491 CONFIG_EXTRA_ENV_SETTINGS
2493 Define this to contain any number of null terminated
2494 strings (variable = value pairs) that will be part of
2495 the default environment compiled into the boot image.
2497 For example, place something like this in your
2498 board's config file:
2500 #define CONFIG_EXTRA_ENV_SETTINGS \
2504 Warning: This method is based on knowledge about the
2505 internal format how the environment is stored by the
2506 U-Boot code. This is NOT an official, exported
2507 interface! Although it is unlikely that this format
2508 will change soon, there is no guarantee either.
2509 You better know what you are doing here.
2511 Note: overly (ab)use of the default environment is
2512 discouraged. Make sure to check other ways to preset
2513 the environment like the "source" command or the
2516 CONFIG_ENV_VARS_UBOOT_CONFIG
2518 Define this in order to add variables describing the
2519 U-Boot build configuration to the default environment.
2520 These will be named arch, cpu, board, vendor, and soc.
2522 Enabling this option will cause the following to be defined:
2530 CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG
2532 Define this in order to add variables describing certain
2533 run-time determined information about the hardware to the
2534 environment. These will be named board_name, board_rev.
2536 CONFIG_DELAY_ENVIRONMENT
2538 Normally the environment is loaded when the board is
2539 intialised so that it is available to U-Boot. This inhibits
2540 that so that the environment is not available until
2541 explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL
2542 this is instead controlled by the value of
2543 /config/load-environment.
2545 - DataFlash Support:
2546 CONFIG_HAS_DATAFLASH
2548 Defining this option enables DataFlash features and
2549 allows to read/write in Dataflash via the standard
2552 - Serial Flash support
2555 Defining this option enables SPI flash commands
2556 'sf probe/read/write/erase/update'.
2558 Usage requires an initial 'probe' to define the serial
2559 flash parameters, followed by read/write/erase/update
2562 The following defaults may be provided by the platform
2563 to handle the common case when only a single serial
2564 flash is present on the system.
2566 CONFIG_SF_DEFAULT_BUS Bus identifier
2567 CONFIG_SF_DEFAULT_CS Chip-select
2568 CONFIG_SF_DEFAULT_MODE (see include/spi.h)
2569 CONFIG_SF_DEFAULT_SPEED in Hz
2573 Define this option to include a destructive SPI flash
2576 CONFIG_SPI_FLASH_BAR Ban/Extended Addr Reg
2578 Define this option to use the Bank addr/Extended addr
2579 support on SPI flashes which has size > 16Mbytes.
2581 - SystemACE Support:
2584 Adding this option adds support for Xilinx SystemACE
2585 chips attached via some sort of local bus. The address
2586 of the chip must also be defined in the
2587 CONFIG_SYS_SYSTEMACE_BASE macro. For example:
2589 #define CONFIG_SYSTEMACE
2590 #define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000
2592 When SystemACE support is added, the "ace" device type
2593 becomes available to the fat commands, i.e. fatls.
2595 - TFTP Fixed UDP Port:
2598 If this is defined, the environment variable tftpsrcp
2599 is used to supply the TFTP UDP source port value.
2600 If tftpsrcp isn't defined, the normal pseudo-random port
2601 number generator is used.
2603 Also, the environment variable tftpdstp is used to supply
2604 the TFTP UDP destination port value. If tftpdstp isn't
2605 defined, the normal port 69 is used.
2607 The purpose for tftpsrcp is to allow a TFTP server to
2608 blindly start the TFTP transfer using the pre-configured
2609 target IP address and UDP port. This has the effect of
2610 "punching through" the (Windows XP) firewall, allowing
2611 the remainder of the TFTP transfer to proceed normally.
2612 A better solution is to properly configure the firewall,
2613 but sometimes that is not allowed.
2618 This enables a generic 'hash' command which can produce
2619 hashes / digests from a few algorithms (e.g. SHA1, SHA256).
2623 Enable the hash verify command (hash -v). This adds to code
2626 CONFIG_SHA1 - support SHA1 hashing
2627 CONFIG_SHA256 - support SHA256 hashing
2629 Note: There is also a sha1sum command, which should perhaps
2630 be deprecated in favour of 'hash sha1'.
2635 This enables the RSA algorithm used for FIT image verification
2636 in U-Boot. See doc/uImage/signature for more information.
2638 The signing part is build into mkimage regardless of this
2642 - Show boot progress:
2643 CONFIG_SHOW_BOOT_PROGRESS
2645 Defining this option allows to add some board-
2646 specific code (calling a user-provided function
2647 "show_boot_progress(int)") that enables you to show
2648 the system's boot progress on some display (for
2649 example, some LED's) on your board. At the moment,
2650 the following checkpoints are implemented:
2652 - Detailed boot stage timing
2654 Define this option to get detailed timing of each stage
2655 of the boot process.
2657 CONFIG_BOOTSTAGE_USER_COUNT
2658 This is the number of available user bootstage records.
2659 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
2660 a new ID will be allocated from this stash. If you exceed
2661 the limit, recording will stop.
2663 CONFIG_BOOTSTAGE_REPORT
2664 Define this to print a report before boot, similar to this:
2666 Timer summary in microseconds:
2669 3,575,678 3,575,678 board_init_f start
2670 3,575,695 17 arch_cpu_init A9
2671 3,575,777 82 arch_cpu_init done
2672 3,659,598 83,821 board_init_r start
2673 3,910,375 250,777 main_loop
2674 29,916,167 26,005,792 bootm_start
2675 30,361,327 445,160 start_kernel
2677 CONFIG_CMD_BOOTSTAGE
2678 Add a 'bootstage' command which supports printing a report
2679 and un/stashing of bootstage data.
2681 CONFIG_BOOTSTAGE_FDT
2682 Stash the bootstage information in the FDT. A root 'bootstage'
2683 node is created with each bootstage id as a child. Each child
2684 has a 'name' property and either 'mark' containing the
2685 mark time in microsecond, or 'accum' containing the
2686 accumulated time for that bootstage id in microseconds.
2691 name = "board_init_f";
2700 Code in the Linux kernel can find this in /proc/devicetree.
2702 Legacy uImage format:
2705 1 common/cmd_bootm.c before attempting to boot an image
2706 -1 common/cmd_bootm.c Image header has bad magic number
2707 2 common/cmd_bootm.c Image header has correct magic number
2708 -2 common/cmd_bootm.c Image header has bad checksum
2709 3 common/cmd_bootm.c Image header has correct checksum
2710 -3 common/cmd_bootm.c Image data has bad checksum
2711 4 common/cmd_bootm.c Image data has correct checksum
2712 -4 common/cmd_bootm.c Image is for unsupported architecture
2713 5 common/cmd_bootm.c Architecture check OK
2714 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
2715 6 common/cmd_bootm.c Image Type check OK
2716 -6 common/cmd_bootm.c gunzip uncompression error
2717 -7 common/cmd_bootm.c Unimplemented compression type
2718 7 common/cmd_bootm.c Uncompression OK
2719 8 common/cmd_bootm.c No uncompress/copy overwrite error
2720 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
2722 9 common/image.c Start initial ramdisk verification
2723 -10 common/image.c Ramdisk header has bad magic number
2724 -11 common/image.c Ramdisk header has bad checksum
2725 10 common/image.c Ramdisk header is OK
2726 -12 common/image.c Ramdisk data has bad checksum
2727 11 common/image.c Ramdisk data has correct checksum
2728 12 common/image.c Ramdisk verification complete, start loading
2729 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
2730 13 common/image.c Start multifile image verification
2731 14 common/image.c No initial ramdisk, no multifile, continue.
2733 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
2735 -30 arch/powerpc/lib/board.c Fatal error, hang the system
2736 -31 post/post.c POST test failed, detected by post_output_backlog()
2737 -32 post/post.c POST test failed, detected by post_run_single()
2739 34 common/cmd_doc.c before loading a Image from a DOC device
2740 -35 common/cmd_doc.c Bad usage of "doc" command
2741 35 common/cmd_doc.c correct usage of "doc" command
2742 -36 common/cmd_doc.c No boot device
2743 36 common/cmd_doc.c correct boot device
2744 -37 common/cmd_doc.c Unknown Chip ID on boot device
2745 37 common/cmd_doc.c correct chip ID found, device available
2746 -38 common/cmd_doc.c Read Error on boot device
2747 38 common/cmd_doc.c reading Image header from DOC device OK
2748 -39 common/cmd_doc.c Image header has bad magic number
2749 39 common/cmd_doc.c Image header has correct magic number
2750 -40 common/cmd_doc.c Error reading Image from DOC device
2751 40 common/cmd_doc.c Image header has correct magic number
2752 41 common/cmd_ide.c before loading a Image from a IDE device
2753 -42 common/cmd_ide.c Bad usage of "ide" command
2754 42 common/cmd_ide.c correct usage of "ide" command
2755 -43 common/cmd_ide.c No boot device
2756 43 common/cmd_ide.c boot device found
2757 -44 common/cmd_ide.c Device not available
2758 44 common/cmd_ide.c Device available
2759 -45 common/cmd_ide.c wrong partition selected
2760 45 common/cmd_ide.c partition selected
2761 -46 common/cmd_ide.c Unknown partition table
2762 46 common/cmd_ide.c valid partition table found
2763 -47 common/cmd_ide.c Invalid partition type
2764 47 common/cmd_ide.c correct partition type
2765 -48 common/cmd_ide.c Error reading Image Header on boot device
2766 48 common/cmd_ide.c reading Image Header from IDE device OK
2767 -49 common/cmd_ide.c Image header has bad magic number
2768 49 common/cmd_ide.c Image header has correct magic number
2769 -50 common/cmd_ide.c Image header has bad checksum
2770 50 common/cmd_ide.c Image header has correct checksum
2771 -51 common/cmd_ide.c Error reading Image from IDE device
2772 51 common/cmd_ide.c reading Image from IDE device OK
2773 52 common/cmd_nand.c before loading a Image from a NAND device
2774 -53 common/cmd_nand.c Bad usage of "nand" command
2775 53 common/cmd_nand.c correct usage of "nand" command
2776 -54 common/cmd_nand.c No boot device
2777 54 common/cmd_nand.c boot device found
2778 -55 common/cmd_nand.c Unknown Chip ID on boot device
2779 55 common/cmd_nand.c correct chip ID found, device available
2780 -56 common/cmd_nand.c Error reading Image Header on boot device
2781 56 common/cmd_nand.c reading Image Header from NAND device OK
2782 -57 common/cmd_nand.c Image header has bad magic number
2783 57 common/cmd_nand.c Image header has correct magic number
2784 -58 common/cmd_nand.c Error reading Image from NAND device
2785 58 common/cmd_nand.c reading Image from NAND device OK
2787 -60 common/env_common.c Environment has a bad CRC, using default
2789 64 net/eth.c starting with Ethernet configuration.
2790 -64 net/eth.c no Ethernet found.
2791 65 net/eth.c Ethernet found.
2793 -80 common/cmd_net.c usage wrong
2794 80 common/cmd_net.c before calling NetLoop()
2795 -81 common/cmd_net.c some error in NetLoop() occurred
2796 81 common/cmd_net.c NetLoop() back without error
2797 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
2798 82 common/cmd_net.c trying automatic boot
2799 83 common/cmd_net.c running "source" command
2800 -83 common/cmd_net.c some error in automatic boot or "source" command
2801 84 common/cmd_net.c end without errors
2806 100 common/cmd_bootm.c Kernel FIT Image has correct format
2807 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
2808 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
2809 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
2810 102 common/cmd_bootm.c Kernel unit name specified
2811 -103 common/cmd_bootm.c Can't get kernel subimage node offset
2812 103 common/cmd_bootm.c Found configuration node
2813 104 common/cmd_bootm.c Got kernel subimage node offset
2814 -104 common/cmd_bootm.c Kernel subimage hash verification failed
2815 105 common/cmd_bootm.c Kernel subimage hash verification OK
2816 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
2817 106 common/cmd_bootm.c Architecture check OK
2818 -106 common/cmd_bootm.c Kernel subimage has wrong type
2819 107 common/cmd_bootm.c Kernel subimage type OK
2820 -107 common/cmd_bootm.c Can't get kernel subimage data/size
2821 108 common/cmd_bootm.c Got kernel subimage data/size
2822 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
2823 -109 common/cmd_bootm.c Can't get kernel subimage type
2824 -110 common/cmd_bootm.c Can't get kernel subimage comp
2825 -111 common/cmd_bootm.c Can't get kernel subimage os
2826 -112 common/cmd_bootm.c Can't get kernel subimage load address
2827 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
2829 120 common/image.c Start initial ramdisk verification
2830 -120 common/image.c Ramdisk FIT image has incorrect format
2831 121 common/image.c Ramdisk FIT image has correct format
2832 122 common/image.c No ramdisk subimage unit name, using configuration
2833 -122 common/image.c Can't get configuration for ramdisk subimage
2834 123 common/image.c Ramdisk unit name specified
2835 -124 common/image.c Can't get ramdisk subimage node offset
2836 125 common/image.c Got ramdisk subimage node offset
2837 -125 common/image.c Ramdisk subimage hash verification failed
2838 126 common/image.c Ramdisk subimage hash verification OK
2839 -126 common/image.c Ramdisk subimage for unsupported architecture
2840 127 common/image.c Architecture check OK
2841 -127 common/image.c Can't get ramdisk subimage data/size
2842 128 common/image.c Got ramdisk subimage data/size
2843 129 common/image.c Can't get ramdisk load address
2844 -129 common/image.c Got ramdisk load address
2846 -130 common/cmd_doc.c Incorrect FIT image format
2847 131 common/cmd_doc.c FIT image format OK
2849 -140 common/cmd_ide.c Incorrect FIT image format
2850 141 common/cmd_ide.c FIT image format OK
2852 -150 common/cmd_nand.c Incorrect FIT image format
2853 151 common/cmd_nand.c FIT image format OK
2855 - FIT image support:
2857 Enable support for the FIT uImage format.
2859 CONFIG_FIT_BEST_MATCH
2860 When no configuration is explicitly selected, default to the
2861 one whose fdt's compatibility field best matches that of
2862 U-Boot itself. A match is considered "best" if it matches the
2863 most specific compatibility entry of U-Boot's fdt's root node.
2864 The order of entries in the configuration's fdt is ignored.
2866 CONFIG_FIT_SIGNATURE
2867 This option enables signature verification of FIT uImages,
2868 using a hash signed and verified using RSA. See
2869 doc/uImage.FIT/signature.txt for more details.
2871 - Standalone program support:
2872 CONFIG_STANDALONE_LOAD_ADDR
2874 This option defines a board specific value for the
2875 address where standalone program gets loaded, thus
2876 overwriting the architecture dependent default
2879 - Frame Buffer Address:
2882 Define CONFIG_FB_ADDR if you want to use specific
2883 address for frame buffer. This is typically the case
2884 when using a graphics controller has separate video
2885 memory. U-Boot will then place the frame buffer at
2886 the given address instead of dynamically reserving it
2887 in system RAM by calling lcd_setmem(), which grabs
2888 the memory for the frame buffer depending on the
2889 configured panel size.
2891 Please see board_init_f function.
2893 - Automatic software updates via TFTP server
2895 CONFIG_UPDATE_TFTP_CNT_MAX
2896 CONFIG_UPDATE_TFTP_MSEC_MAX
2898 These options enable and control the auto-update feature;
2899 for a more detailed description refer to doc/README.update.
2901 - MTD Support (mtdparts command, UBI support)
2904 Adds the MTD device infrastructure from the Linux kernel.
2905 Needed for mtdparts command support.
2907 CONFIG_MTD_PARTITIONS
2909 Adds the MTD partitioning infrastructure from the Linux
2910 kernel. Needed for UBI support.
2915 Adds commands for interacting with MTD partitions formatted
2916 with the UBI flash translation layer
2918 Requires also defining CONFIG_RBTREE
2920 CONFIG_UBI_SILENCE_MSG
2922 Make the verbose messages from UBI stop printing. This leaves
2923 warnings and errors enabled.
2928 Adds commands for interacting with UBI volumes formatted as
2929 UBIFS. UBIFS is read-only in u-boot.
2931 Requires UBI support as well as CONFIG_LZO
2933 CONFIG_UBIFS_SILENCE_MSG
2935 Make the verbose messages from UBIFS stop printing. This leaves
2936 warnings and errors enabled.
2940 Enable building of SPL globally.
2943 LDSCRIPT for linking the SPL binary.
2945 CONFIG_SPL_MAX_FOOTPRINT
2946 Maximum size in memory allocated to the SPL, BSS included.
2947 When defined, the linker checks that the actual memory
2948 used by SPL from _start to __bss_end does not exceed it.
2949 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
2950 must not be both defined at the same time.
2953 Maximum size of the SPL image (text, data, rodata, and
2954 linker lists sections), BSS excluded.
2955 When defined, the linker checks that the actual size does
2958 CONFIG_SPL_TEXT_BASE
2959 TEXT_BASE for linking the SPL binary.
2961 CONFIG_SPL_RELOC_TEXT_BASE
2962 Address to relocate to. If unspecified, this is equal to
2963 CONFIG_SPL_TEXT_BASE (i.e. no relocation is done).
2965 CONFIG_SPL_BSS_START_ADDR
2966 Link address for the BSS within the SPL binary.
2968 CONFIG_SPL_BSS_MAX_SIZE
2969 Maximum size in memory allocated to the SPL BSS.
2970 When defined, the linker checks that the actual memory used
2971 by SPL from __bss_start to __bss_end does not exceed it.
2972 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
2973 must not be both defined at the same time.
2976 Adress of the start of the stack SPL will use
2978 CONFIG_SPL_RELOC_STACK
2979 Adress of the start of the stack SPL will use after
2980 relocation. If unspecified, this is equal to
2983 CONFIG_SYS_SPL_MALLOC_START
2984 Starting address of the malloc pool used in SPL.
2986 CONFIG_SYS_SPL_MALLOC_SIZE
2987 The size of the malloc pool used in SPL.
2989 CONFIG_SPL_FRAMEWORK
2990 Enable the SPL framework under common/. This framework
2991 supports MMC, NAND and YMODEM loading of U-Boot and NAND
2992 NAND loading of the Linux Kernel.
2994 CONFIG_SPL_DISPLAY_PRINT
2995 For ARM, enable an optional function to print more information
2996 about the running system.
2998 CONFIG_SPL_INIT_MINIMAL
2999 Arch init code should be built for a very small image
3001 CONFIG_SPL_LIBCOMMON_SUPPORT
3002 Support for common/libcommon.o in SPL binary
3004 CONFIG_SPL_LIBDISK_SUPPORT
3005 Support for disk/libdisk.o in SPL binary
3007 CONFIG_SPL_I2C_SUPPORT
3008 Support for drivers/i2c/libi2c.o in SPL binary
3010 CONFIG_SPL_GPIO_SUPPORT
3011 Support for drivers/gpio/libgpio.o in SPL binary
3013 CONFIG_SPL_MMC_SUPPORT
3014 Support for drivers/mmc/libmmc.o in SPL binary
3016 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR,
3017 CONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS,
3018 CONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION
3019 Address, size and partition on the MMC to load U-Boot from
3020 when the MMC is being used in raw mode.
3022 CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
3023 Sector to load kernel uImage from when MMC is being
3024 used in raw mode (for Falcon mode)
3026 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR,
3027 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS
3028 Sector and number of sectors to load kernel argument
3029 parameters from when MMC is being used in raw mode
3032 CONFIG_SPL_FAT_SUPPORT
3033 Support for fs/fat/libfat.o in SPL binary
3035 CONFIG_SPL_FAT_LOAD_PAYLOAD_NAME
3036 Filename to read to load U-Boot when reading from FAT
3038 CONFIG_SPL_FAT_LOAD_KERNEL_NAME
3039 Filename to read to load kernel uImage when reading
3040 from FAT (for Falcon mode)
3042 CONFIG_SPL_FAT_LOAD_ARGS_NAME
3043 Filename to read to load kernel argument parameters
3044 when reading from FAT (for Falcon mode)
3046 CONFIG_SPL_MPC83XX_WAIT_FOR_NAND
3047 Set this for NAND SPL on PPC mpc83xx targets, so that
3048 start.S waits for the rest of the SPL to load before
3049 continuing (the hardware starts execution after just
3050 loading the first page rather than the full 4K).
3052 CONFIG_SPL_NAND_BASE
3053 Include nand_base.c in the SPL. Requires
3054 CONFIG_SPL_NAND_DRIVERS.
3056 CONFIG_SPL_NAND_DRIVERS
3057 SPL uses normal NAND drivers, not minimal drivers.
3060 Include standard software ECC in the SPL
3062 CONFIG_SPL_NAND_SIMPLE
3063 Support for NAND boot using simple NAND drivers that
3064 expose the cmd_ctrl() interface.
3066 CONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT,
3067 CONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE,
3068 CONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS,
3069 CONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE,
3070 CONFIG_SYS_NAND_ECCBYTES
3071 Defines the size and behavior of the NAND that SPL uses
3074 CONFIG_SYS_NAND_U_BOOT_OFFS
3075 Location in NAND to read U-Boot from
3077 CONFIG_SYS_NAND_U_BOOT_DST
3078 Location in memory to load U-Boot to
3080 CONFIG_SYS_NAND_U_BOOT_SIZE
3081 Size of image to load
3083 CONFIG_SYS_NAND_U_BOOT_START
3084 Entry point in loaded image to jump to
3086 CONFIG_SYS_NAND_HW_ECC_OOBFIRST
3087 Define this if you need to first read the OOB and then the
3088 data. This is used for example on davinci plattforms.
3090 CONFIG_SPL_OMAP3_ID_NAND
3091 Support for an OMAP3-specific set of functions to return the
3092 ID and MFR of the first attached NAND chip, if present.
3094 CONFIG_SPL_SERIAL_SUPPORT
3095 Support for drivers/serial/libserial.o in SPL binary
3097 CONFIG_SPL_SPI_FLASH_SUPPORT
3098 Support for drivers/mtd/spi/libspi_flash.o in SPL binary
3100 CONFIG_SPL_SPI_SUPPORT
3101 Support for drivers/spi/libspi.o in SPL binary
3103 CONFIG_SPL_RAM_DEVICE
3104 Support for running image already present in ram, in SPL binary
3106 CONFIG_SPL_LIBGENERIC_SUPPORT
3107 Support for lib/libgeneric.o in SPL binary
3109 CONFIG_SPL_ENV_SUPPORT
3110 Support for the environment operating in SPL binary
3112 CONFIG_SPL_NET_SUPPORT
3113 Support for the net/libnet.o in SPL binary.
3114 It conflicts with SPL env from storage medium specified by
3115 CONFIG_ENV_IS_xxx but CONFIG_ENV_IS_NOWHERE
3118 Image offset to which the SPL should be padded before appending
3119 the SPL payload. By default, this is defined as
3120 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
3121 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
3122 payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
3125 Final target image containing SPL and payload. Some SPLs
3126 use an arch-specific makefile fragment instead, for
3127 example if more than one image needs to be produced.
3129 CONFIG_FIT_SPL_PRINT
3130 Printing information about a FIT image adds quite a bit of
3131 code to SPL. So this is normally disabled in SPL. Use this
3132 option to re-enable it. This will affect the output of the
3133 bootm command when booting a FIT image.
3138 [so far only for SMDK2400 boards]
3140 - Modem support enable:
3141 CONFIG_MODEM_SUPPORT
3143 - RTS/CTS Flow control enable:
3146 - Modem debug support:
3147 CONFIG_MODEM_SUPPORT_DEBUG
3149 Enables debugging stuff (char screen[1024], dbg())
3150 for modem support. Useful only with BDI2000.
3152 - Interrupt support (PPC):
3154 There are common interrupt_init() and timer_interrupt()
3155 for all PPC archs. interrupt_init() calls interrupt_init_cpu()
3156 for CPU specific initialization. interrupt_init_cpu()
3157 should set decrementer_count to appropriate value. If
3158 CPU resets decrementer automatically after interrupt
3159 (ppc4xx) it should set decrementer_count to zero.
3160 timer_interrupt() calls timer_interrupt_cpu() for CPU
3161 specific handling. If board has watchdog / status_led
3162 / other_activity_monitor it works automatically from
3163 general timer_interrupt().
3167 In the target system modem support is enabled when a
3168 specific key (key combination) is pressed during
3169 power-on. Otherwise U-Boot will boot normally
3170 (autoboot). The key_pressed() function is called from
3171 board_init(). Currently key_pressed() is a dummy
3172 function, returning 1 and thus enabling modem
3175 If there are no modem init strings in the
3176 environment, U-Boot proceed to autoboot; the
3177 previous output (banner, info printfs) will be
3180 See also: doc/README.Modem
3182 Board initialization settings:
3183 ------------------------------
3185 During Initialization u-boot calls a number of board specific functions
3186 to allow the preparation of board specific prerequisites, e.g. pin setup
3187 before drivers are initialized. To enable these callbacks the
3188 following configuration macros have to be defined. Currently this is
3189 architecture specific, so please check arch/your_architecture/lib/board.c
3190 typically in board_init_f() and board_init_r().
3192 - CONFIG_BOARD_EARLY_INIT_F: Call board_early_init_f()
3193 - CONFIG_BOARD_EARLY_INIT_R: Call board_early_init_r()
3194 - CONFIG_BOARD_LATE_INIT: Call board_late_init()
3195 - CONFIG_BOARD_POSTCLK_INIT: Call board_postclk_init()
3197 Configuration Settings:
3198 -----------------------
3200 - CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
3201 undefine this when you're short of memory.
3203 - CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default
3204 width of the commands listed in the 'help' command output.
3206 - CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to
3207 prompt for user input.
3209 - CONFIG_SYS_CBSIZE: Buffer size for input from the Console
3211 - CONFIG_SYS_PBSIZE: Buffer size for Console output
3213 - CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands
3215 - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
3216 the application (usually a Linux kernel) when it is
3219 - CONFIG_SYS_BAUDRATE_TABLE:
3220 List of legal baudrate settings for this board.
3222 - CONFIG_SYS_CONSOLE_INFO_QUIET
3223 Suppress display of console information at boot.
3225 - CONFIG_SYS_CONSOLE_IS_IN_ENV
3226 If the board specific function
3227 extern int overwrite_console (void);
3228 returns 1, the stdin, stderr and stdout are switched to the
3229 serial port, else the settings in the environment are used.
3231 - CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE
3232 Enable the call to overwrite_console().
3234 - CONFIG_SYS_CONSOLE_ENV_OVERWRITE
3235 Enable overwrite of previous console environment settings.
projects / karo-tx-uboot.git / blob