1 # SPDX-License-Identifier: GPL-2.0+
3 # (C) Copyright 2000 - 2013
9 This directory contains the source code for U-Boot, a boot loader for
10 Embedded boards based on PowerPC, ARM, MIPS and several other
11 processors, which can be installed in a boot ROM and used to
12 initialize and test the hardware or to download and run application
15 The development of U-Boot is closely related to Linux: some parts of
16 the source code originate in the Linux source tree, we have some
17 header files in common, and special provision has been made to
18 support booting of Linux images.
20 Some attention has been paid to make this software easily
21 configurable and extendable. For instance, all monitor commands are
22 implemented with the same call interface, so that it's very easy to
23 add new commands. Also, instead of permanently adding rarely used
24 code (for instance hardware test utilities) to the monitor, you can
25 load and run it dynamically.
31 In general, all boards for which a configuration option exists in the
32 Makefile have been tested to some extent and can be considered
33 "working". In fact, many of them are used in production systems.
35 In case of problems see the CHANGELOG file to find out who contributed
36 the specific port. In addition, there are various MAINTAINERS files
37 scattered throughout the U-Boot source identifying the people or
38 companies responsible for various boards and subsystems.
40 Note: As of August, 2010, there is no longer a CHANGELOG file in the
41 actual U-Boot source tree; however, it can be created dynamically
42 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
53 on the mailing list - please search the archive before asking FAQ's.
54 Please see https://lists.denx.de/pipermail/u-boot and
55 https://marc.info/?l=u-boot
57 Where to get source code:
58 =========================
60 The U-Boot source code is maintained in the Git repository at
61 https://source.denx.de/u-boot/u-boot.git ; you can browse it online at
62 https://source.denx.de/u-boot/u-boot
64 The "Tags" links on this page allow you to download tarballs of
65 any version you might be interested in. Official releases are also
66 available from the DENX file server through HTTPS or FTP.
67 https://ftp.denx.de/pub/u-boot/
68 ftp://ftp.denx.de/pub/u-boot/
74 - start from 8xxrom sources
75 - create PPCBoot project (https://sourceforge.net/projects/ppcboot)
77 - make it easier to add custom boards
78 - make it possible to add other [PowerPC] CPUs
79 - extend functions, especially:
80 * Provide extended interface to Linux boot loader
83 * ATA disk / SCSI ... boot
84 - create ARMBoot project (https://sourceforge.net/projects/armboot)
85 - add other CPU families (starting with ARM)
86 - create U-Boot project (https://sourceforge.net/projects/u-boot)
87 - current project page: see https://www.denx.de/wiki/U-Boot
93 The "official" name of this project is "Das U-Boot". The spelling
94 "U-Boot" shall be used in all written text (documentation, comments
95 in source files etc.). Example:
97 This is the README file for the U-Boot project.
99 File names etc. shall be based on the string "u-boot". Examples:
101 include/asm-ppc/u-boot.h
103 #include <asm/u-boot.h>
105 Variable names, preprocessor constants etc. shall be either based on
106 the string "u_boot" or on "U_BOOT". Example:
108 U_BOOT_VERSION u_boot_logo
109 IH_OS_U_BOOT u_boot_hush_start
115 Starting with the release in October 2008, the names of the releases
116 were changed from numerical release numbers without deeper meaning
117 into a time stamp based numbering. Regular releases are identified by
118 names consisting of the calendar year and month of the release date.
119 Additional fields (if present) indicate release candidates or bug fix
120 releases in "stable" maintenance trees.
123 U-Boot v2009.11 - Release November 2009
124 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree
125 U-Boot v2010.09-rc1 - Release candidate 1 for September 2010 release
131 /arch Architecture-specific files
132 /arc Files generic to ARC architecture
133 /arm Files generic to ARM architecture
134 /m68k Files generic to m68k architecture
135 /microblaze Files generic to microblaze architecture
136 /mips Files generic to MIPS architecture
137 /nds32 Files generic to NDS32 architecture
138 /nios2 Files generic to Altera NIOS2 architecture
139 /powerpc Files generic to PowerPC architecture
140 /riscv Files generic to RISC-V architecture
141 /sandbox Files generic to HW-independent "sandbox"
142 /sh Files generic to SH architecture
143 /x86 Files generic to x86 architecture
144 /xtensa Files generic to Xtensa architecture
145 /api Machine/arch-independent API for external apps
146 /board Board-dependent files
147 /cmd U-Boot commands functions
148 /common Misc architecture-independent functions
149 /configs Board default configuration files
150 /disk Code for disk drive partition handling
151 /doc Documentation (a mix of ReST and READMEs)
152 /drivers Device drivers
153 /dts Makefile for building internal U-Boot fdt.
154 /env Environment support
155 /examples Example code for standalone applications, etc.
156 /fs Filesystem code (cramfs, ext2, jffs2, etc.)
157 /include Header Files
158 /lib Library routines generic to all architectures
159 /Licenses Various license files
161 /post Power On Self Test
162 /scripts Various build scripts and Makefiles
163 /test Various unit test files
164 /tools Tools to build and sign FIT images, etc.
166 Software Configuration:
167 =======================
169 Configuration is usually done using C preprocessor defines; the
170 rationale behind that is to avoid dead code whenever possible.
172 There are two classes of configuration variables:
174 * Configuration _OPTIONS_:
175 These are selectable by the user and have names beginning with
178 * Configuration _SETTINGS_:
179 These depend on the hardware etc. and should not be meddled with if
180 you don't know what you're doing; they have names beginning with
183 Previously, all configuration was done by hand, which involved creating
184 symbolic links and editing configuration files manually. More recently,
185 U-Boot has added the Kbuild infrastructure used by the Linux kernel,
186 allowing you to use the "make menuconfig" command to configure your
190 Selection of Processor Architecture and Board Type:
191 ---------------------------------------------------
193 For all supported boards there are ready-to-use default
194 configurations available; just type "make <board_name>_defconfig".
196 Example: For a TQM823L module type:
199 make TQM823L_defconfig
201 Note: If you're looking for the default configuration file for a board
202 you're sure used to be there but is now missing, check the file
203 doc/README.scrapyard for a list of no longer supported boards.
208 U-Boot can be built natively to run on a Linux host using the 'sandbox'
209 board. This allows feature development which is not board- or architecture-
210 specific to be undertaken on a native platform. The sandbox is also used to
211 run some of U-Boot's tests.
213 See doc/arch/sandbox.rst for more details.
216 Board Initialisation Flow:
217 --------------------------
219 This is the intended start-up flow for boards. This should apply for both
220 SPL and U-Boot proper (i.e. they both follow the same rules).
222 Note: "SPL" stands for "Secondary Program Loader," which is explained in
223 more detail later in this file.
225 At present, SPL mostly uses a separate code path, but the function names
226 and roles of each function are the same. Some boards or architectures
227 may not conform to this. At least most ARM boards which use
228 CONFIG_SPL_FRAMEWORK conform to this.
230 Execution typically starts with an architecture-specific (and possibly
231 CPU-specific) start.S file, such as:
233 - arch/arm/cpu/armv7/start.S
234 - arch/powerpc/cpu/mpc83xx/start.S
235 - arch/mips/cpu/start.S
237 and so on. From there, three functions are called; the purpose and
238 limitations of each of these functions are described below.
241 - purpose: essential init to permit execution to reach board_init_f()
242 - no global_data or BSS
243 - there is no stack (ARMv7 may have one but it will soon be removed)
244 - must not set up SDRAM or use console
245 - must only do the bare minimum to allow execution to continue to
247 - this is almost never needed
248 - return normally from this function
251 - purpose: set up the machine ready for running board_init_r():
252 i.e. SDRAM and serial UART
253 - global_data is available
255 - BSS is not available, so you cannot use global/static variables,
256 only stack variables and global_data
258 Non-SPL-specific notes:
259 - dram_init() is called to set up DRAM. If already done in SPL this
263 - you can override the entire board_init_f() function with your own
265 - preloader_console_init() can be called here in extremis
266 - should set up SDRAM, and anything needed to make the UART work
267 - there is no need to clear BSS, it will be done by crt0.S
268 - for specific scenarios on certain architectures an early BSS *can*
269 be made available (via CONFIG_SPL_EARLY_BSS by moving the clearing
270 of BSS prior to entering board_init_f()) but doing so is discouraged.
271 Instead it is strongly recommended to architect any code changes
272 or additions such to not depend on the availability of BSS during
273 board_init_f() as indicated in other sections of this README to
274 maintain compatibility and consistency across the entire code base.
275 - must return normally from this function (don't call board_init_r()
278 Here the BSS is cleared. For SPL, if CONFIG_SPL_STACK_R is defined, then at
279 this point the stack and global_data are relocated to below
280 CONFIG_SPL_STACK_R_ADDR. For non-SPL, U-Boot is relocated to run at the top of
284 - purpose: main execution, common code
285 - global_data is available
287 - BSS is available, all static/global variables can be used
288 - execution eventually continues to main_loop()
290 Non-SPL-specific notes:
291 - U-Boot is relocated to the top of memory and is now running from
295 - stack is optionally in SDRAM, if CONFIG_SPL_STACK_R is defined and
296 CONFIG_SPL_STACK_R_ADDR points into SDRAM
297 - preloader_console_init() can be called here - typically this is
298 done by selecting CONFIG_SPL_BOARD_INIT and then supplying a
299 spl_board_init() function containing this call
300 - loads U-Boot or (in falcon mode) Linux
304 Configuration Options:
305 ----------------------
307 Configuration depends on the combination of board and CPU type; all
308 such information is kept in a configuration file
309 "include/configs/<board_name>.h".
311 Example: For a TQM823L module, all configuration settings are in
312 "include/configs/TQM823L.h".
315 Many of the options are named exactly as the corresponding Linux
316 kernel configuration options. The intention is to make it easier to
317 build a config tool - later.
319 - ARM Platform Bus Type(CCI):
320 CoreLink Cache Coherent Interconnect (CCI) is ARM BUS which
321 provides full cache coherency between two clusters of multi-core
322 CPUs and I/O coherency for devices and I/O masters
324 CONFIG_SYS_FSL_HAS_CCI400
326 Defined For SoC that has cache coherent interconnect
329 CONFIG_SYS_FSL_HAS_CCN504
331 Defined for SoC that has cache coherent interconnect CCN-504
333 The following options need to be configured:
335 - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
337 - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
342 Specifies that the core is a 64-bit PowerPC implementation (implements
343 the "64" category of the Power ISA). This is necessary for ePAPR
344 compliance, among other possible reasons.
346 CONFIG_SYS_FSL_TBCLK_DIV
348 Defines the core time base clock divider ratio compared to the
349 system clock. On most PQ3 devices this is 8, on newer QorIQ
350 devices it can be 16 or 32. The ratio varies from SoC to Soc.
352 CONFIG_SYS_FSL_PCIE_COMPAT
354 Defines the string to utilize when trying to match PCIe device
355 tree nodes for the given platform.
357 CONFIG_SYS_FSL_ERRATUM_A004510
359 Enables a workaround for erratum A004510. If set,
360 then CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and
361 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set.
363 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV
364 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional)
366 Defines one or two SoC revisions (low 8 bits of SVR)
367 for which the A004510 workaround should be applied.
369 The rest of SVR is either not relevant to the decision
370 of whether the erratum is present (e.g. p2040 versus
371 p2041) or is implied by the build target, which controls
372 whether CONFIG_SYS_FSL_ERRATUM_A004510 is set.
374 See Freescale App Note 4493 for more information about
377 CONFIG_A003399_NOR_WORKAROUND
378 Enables a workaround for IFC erratum A003399. It is only
379 required during NOR boot.
381 CONFIG_A008044_WORKAROUND
382 Enables a workaround for T1040/T1042 erratum A008044. It is only
383 required during NAND boot and valid for Rev 1.0 SoC revision
385 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY
387 This is the value to write into CCSR offset 0x18600
388 according to the A004510 workaround.
390 CONFIG_SYS_FSL_DSP_DDR_ADDR
391 This value denotes start offset of DDR memory which is
392 connected exclusively to the DSP cores.
394 CONFIG_SYS_FSL_DSP_M2_RAM_ADDR
395 This value denotes start offset of M2 memory
396 which is directly connected to the DSP core.
398 CONFIG_SYS_FSL_DSP_M3_RAM_ADDR
399 This value denotes start offset of M3 memory which is directly
400 connected to the DSP core.
402 CONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT
403 This value denotes start offset of DSP CCSR space.
405 CONFIG_SYS_FSL_SINGLE_SOURCE_CLK
406 Single Source Clock is clocking mode present in some of FSL SoC's.
407 In this mode, a single differential clock is used to supply
408 clocks to the sysclock, ddrclock and usbclock.
410 CONFIG_SYS_CPC_REINIT_F
411 This CONFIG is defined when the CPC is configured as SRAM at the
412 time of U-Boot entry and is required to be re-initialized.
415 Indicates this SoC supports deep sleep feature. If deep sleep is
416 supported, core will start to execute uboot when wakes up.
418 - Generic CPU options:
419 CONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN
421 Defines the endianess of the CPU. Implementation of those
422 values is arch specific.
425 Freescale DDR driver in use. This type of DDR controller is
426 found in mpc83xx, mpc85xx as well as some ARM core SoCs.
428 CONFIG_SYS_FSL_DDR_ADDR
429 Freescale DDR memory-mapped register base.
431 CONFIG_SYS_FSL_DDR_EMU
432 Specify emulator support for DDR. Some DDR features such as
433 deskew training are not available.
435 CONFIG_SYS_FSL_DDRC_GEN1
436 Freescale DDR1 controller.
438 CONFIG_SYS_FSL_DDRC_GEN2
439 Freescale DDR2 controller.
441 CONFIG_SYS_FSL_DDRC_GEN3
442 Freescale DDR3 controller.
444 CONFIG_SYS_FSL_DDRC_GEN4
445 Freescale DDR4 controller.
447 CONFIG_SYS_FSL_DDRC_ARM_GEN3
448 Freescale DDR3 controller for ARM-based SoCs.
451 Board config to use DDR1. It can be enabled for SoCs with
452 Freescale DDR1 or DDR2 controllers, depending on the board
456 Board config to use DDR2. It can be enabled for SoCs with
457 Freescale DDR2 or DDR3 controllers, depending on the board
461 Board config to use DDR3. It can be enabled for SoCs with
462 Freescale DDR3 or DDR3L controllers.
465 Board config to use DDR3L. It can be enabled for SoCs with
469 Board config to use DDR4. It can be enabled for SoCs with
472 CONFIG_SYS_FSL_IFC_BE
473 Defines the IFC controller register space as Big Endian
475 CONFIG_SYS_FSL_IFC_LE
476 Defines the IFC controller register space as Little Endian
478 CONFIG_SYS_FSL_IFC_CLK_DIV
479 Defines divider of platform clock(clock input to IFC controller).
481 CONFIG_SYS_FSL_LBC_CLK_DIV
482 Defines divider of platform clock(clock input to eLBC controller).
484 CONFIG_SYS_FSL_PBL_PBI
485 It enables addition of RCW (Power on reset configuration) in built image.
486 Please refer doc/README.pblimage for more details
488 CONFIG_SYS_FSL_PBL_RCW
489 It adds PBI(pre-boot instructions) commands in u-boot build image.
490 PBI commands can be used to configure SoC before it starts the execution.
491 Please refer doc/README.pblimage for more details
493 CONFIG_SYS_FSL_DDR_BE
494 Defines the DDR controller register space as Big Endian
496 CONFIG_SYS_FSL_DDR_LE
497 Defines the DDR controller register space as Little Endian
499 CONFIG_SYS_FSL_DDR_SDRAM_BASE_PHY
500 Physical address from the view of DDR controllers. It is the
501 same as CONFIG_SYS_DDR_SDRAM_BASE for all Power SoCs. But
502 it could be different for ARM SoCs.
504 CONFIG_SYS_FSL_DDR_INTLV_256B
505 DDR controller interleaving on 256-byte. This is a special
506 interleaving mode, handled by Dickens for Freescale layerscape
509 CONFIG_SYS_FSL_DDR_MAIN_NUM_CTRLS
510 Number of controllers used as main memory.
512 CONFIG_SYS_FSL_OTHER_DDR_NUM_CTRLS
513 Number of controllers used for other than main memory.
515 CONFIG_SYS_FSL_HAS_DP_DDR
516 Defines the SoC has DP-DDR used for DPAA.
518 CONFIG_SYS_FSL_SEC_BE
519 Defines the SEC controller register space as Big Endian
521 CONFIG_SYS_FSL_SEC_LE
522 Defines the SEC controller register space as Little Endian
525 CONFIG_SYS_INIT_SP_OFFSET
527 Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack
528 pointer. This is needed for the temporary stack before
531 CONFIG_XWAY_SWAP_BYTES
533 Enable compilation of tools/xway-swap-bytes needed for Lantiq
534 XWAY SoCs for booting from NOR flash. The U-Boot image needs to
535 be swapped if a flash programmer is used.
538 CONFIG_SYS_EXCEPTION_VECTORS_HIGH
540 Select high exception vectors of the ARM core, e.g., do not
541 clear the V bit of the c1 register of CP15.
544 Generic timer clock source frequency.
546 COUNTER_FREQUENCY_REAL
547 Generic timer clock source frequency if the real clock is
548 different from COUNTER_FREQUENCY, and can only be determined
552 CONFIG_TEGRA_SUPPORT_NON_SECURE
554 Support executing U-Boot in non-secure (NS) mode. Certain
555 impossible actions will be skipped if the CPU is in NS mode,
556 such as ARM architectural timer initialization.
558 - Linux Kernel Interface:
559 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
561 When transferring memsize parameter to Linux, some versions
562 expect it to be in bytes, others in MB.
563 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
567 New kernel versions are expecting firmware settings to be
568 passed using flattened device trees (based on open firmware
572 * New libfdt-based support
573 * Adds the "fdt" command
574 * The bootm command automatically updates the fdt
576 OF_TBCLK - The timebase frequency.
578 boards with QUICC Engines require OF_QE to set UCC MAC
581 CONFIG_OF_BOARD_SETUP
583 Board code has addition modification that it wants to make
584 to the flat device tree before handing it off to the kernel
586 CONFIG_OF_SYSTEM_SETUP
588 Other code has addition modification that it wants to make
589 to the flat device tree before handing it off to the kernel.
590 This causes ft_system_setup() to be called before booting
595 U-Boot can detect if an IDE device is present or not.
596 If not, and this new config option is activated, U-Boot
597 removes the ATA node from the DTS before booting Linux,
598 so the Linux IDE driver does not probe the device and
599 crash. This is needed for buggy hardware (uc101) where
600 no pull down resistor is connected to the signal IDE5V_DD7.
602 CONFIG_MACH_TYPE [relevant for ARM only][mandatory]
604 This setting is mandatory for all boards that have only one
605 machine type and must be used to specify the machine type
606 number as it appears in the ARM machine registry
607 (see https://www.arm.linux.org.uk/developer/machines/).
608 Only boards that have multiple machine types supported
609 in a single configuration file and the machine type is
610 runtime discoverable, do not have to use this setting.
612 - vxWorks boot parameters:
614 bootvx constructs a valid bootline using the following
615 environments variables: bootdev, bootfile, ipaddr, netmask,
616 serverip, gatewayip, hostname, othbootargs.
617 It loads the vxWorks image pointed bootfile.
619 Note: If a "bootargs" environment is defined, it will override
620 the defaults discussed just above.
622 - Cache Configuration:
623 CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
625 - Cache Configuration for ARM:
626 CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache
628 CONFIG_SYS_PL310_BASE - Physical base address of PL310
629 controller register space
634 Define this if you want support for Amba PrimeCell PL011 UARTs.
638 If you have Amba PrimeCell PL011 UARTs, set this variable to
639 the clock speed of the UARTs.
643 If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
644 define this to a list of base addresses for each (supported)
645 port. See e.g. include/configs/versatile.h
647 CONFIG_SERIAL_HW_FLOW_CONTROL
649 Define this variable to enable hw flow control in serial driver.
650 Current user of this option is drivers/serial/nsl16550.c driver
654 Only needed when CONFIG_BOOTDELAY is enabled;
655 define a command string that is automatically executed
656 when no character is read on the console interface
657 within "Boot Delay" after reset.
659 CONFIG_RAMBOOT and CONFIG_NFSBOOT
660 The value of these goes into the environment as
661 "ramboot" and "nfsboot" respectively, and can be used
662 as a convenience, when switching between booting from
665 - Serial Download Echo Mode:
667 If defined to 1, all characters received during a
668 serial download (using the "loads" command) are
669 echoed back. This might be needed by some terminal
670 emulations (like "cu"), but may as well just take
671 time on others. This setting #define's the initial
672 value of the "loads_echo" environment variable.
674 - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
676 Select one of the baudrates listed in
677 CONFIG_SYS_BAUDRATE_TABLE, see below.
679 - Removal of commands
680 If no commands are needed to boot, you can disable
681 CONFIG_CMDLINE to remove them. In this case, the command line
682 will not be available, and when U-Boot wants to execute the
683 boot command (on start-up) it will call board_run_command()
684 instead. This can reduce image size significantly for very
685 simple boot procedures.
687 - Regular expression support:
689 If this variable is defined, U-Boot is linked against
690 the SLRE (Super Light Regular Expression) library,
691 which adds regex support to some commands, as for
692 example "env grep" and "setexpr".
696 If this variable is defined, U-Boot will use a device tree
697 to configure its devices, instead of relying on statically
698 compiled #defines in the board file. This option is
699 experimental and only available on a few boards. The device
700 tree is available in the global data as gd->fdt_blob.
702 U-Boot needs to get its device tree from somewhere. This can
703 be done using one of the three options below:
706 If this variable is defined, U-Boot will embed a device tree
707 binary in its image. This device tree file should be in the
708 board directory and called <soc>-<board>.dts. The binary file
709 is then picked up in board_init_f() and made available through
710 the global data structure as gd->fdt_blob.
713 If this variable is defined, U-Boot will build a device tree
714 binary. It will be called u-boot.dtb. Architecture-specific
715 code will locate it at run-time. Generally this works by:
717 cat u-boot.bin u-boot.dtb >image.bin
719 and in fact, U-Boot does this for you, creating a file called
720 u-boot-dtb.bin which is useful in the common case. You can
721 still use the individual files if you need something more
725 If this variable is defined, U-Boot will use the device tree
726 provided by the board at runtime instead of embedding one with
727 the image. Only boards defining board_fdt_blob_setup() support
728 this option (see include/fdtdec.h file).
732 If this variable is defined, it enables watchdog
733 support for the SoC. There must be support in the SoC
734 specific code for a watchdog. For the 8xx
735 CPUs, the SIU Watchdog feature is enabled in the SYPCR
736 register. When supported for a specific SoC is
737 available, then no further board specific code should
741 When using a watchdog circuitry external to the used
742 SoC, then define this variable and provide board
743 specific code for the "hw_watchdog_reset" function.
745 CONFIG_SYS_WATCHDOG_FREQ
746 Some platforms automatically call WATCHDOG_RESET()
747 from the timer interrupt handler every
748 CONFIG_SYS_WATCHDOG_FREQ interrupts. If not set by the
749 board configuration file, a default of CONFIG_SYS_HZ/2
750 (i.e. 500) is used. Setting CONFIG_SYS_WATCHDOG_FREQ
751 to 0 disables calling WATCHDOG_RESET() from the timer
756 When CONFIG_CMD_DATE is selected, the type of the RTC
757 has to be selected, too. Define exactly one of the
760 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
761 CONFIG_RTC_MC13XXX - use MC13783 or MC13892 RTC
762 CONFIG_RTC_MC146818 - use MC146818 RTC
763 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
764 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
765 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
766 CONFIG_RTC_DS1339 - use Maxim, Inc. DS1339 RTC
767 CONFIG_RTC_DS164x - use Dallas DS164x RTC
768 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
769 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
770 CONFIG_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337
771 CONFIG_SYS_RV3029_TCR - enable trickle charger on
774 Note that if the RTC uses I2C, then the I2C interface
775 must also be configured. See I2C Support, below.
778 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO
780 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
781 chip-ngpio pairs that tell the PCA953X driver the number of
782 pins supported by a particular chip.
784 Note that if the GPIO device uses I2C, then the I2C interface
785 must also be configured. See I2C Support, below.
788 When CONFIG_IO_TRACE is selected, U-Boot intercepts all I/O
789 accesses and can checksum them or write a list of them out
790 to memory. See the 'iotrace' command for details. This is
791 useful for testing device drivers since it can confirm that
792 the driver behaves the same way before and after a code
793 change. Currently this is supported on sandbox and arm. To
794 add support for your architecture, add '#include <iotrace.h>'
795 to the bottom of arch/<arch>/include/asm/io.h and test.
797 Example output from the 'iotrace stats' command is below.
798 Note that if the trace buffer is exhausted, the checksum will
799 still continue to operate.
802 Start: 10000000 (buffer start address)
803 Size: 00010000 (buffer size)
804 Offset: 00000120 (current buffer offset)
805 Output: 10000120 (start + offset)
806 Count: 00000018 (number of trace records)
807 CRC32: 9526fb66 (CRC32 of all trace records)
811 When CONFIG_TIMESTAMP is selected, the timestamp
812 (date and time) of an image is printed by image
813 commands like bootm or iminfo. This option is
814 automatically enabled when you select CONFIG_CMD_DATE .
816 - Partition Labels (disklabels) Supported:
817 Zero or more of the following:
818 CONFIG_MAC_PARTITION Apple's MacOS partition table.
819 CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc.
820 CONFIG_EFI_PARTITION GPT partition table, common when EFI is the
821 bootloader. Note 2TB partition limit; see
823 CONFIG_SCSI) you must configure support for at
824 least one non-MTD partition type as well.
827 CONFIG_IDE_RESET_ROUTINE - this is defined in several
828 board configurations files but used nowhere!
830 CONFIG_IDE_RESET - is this is defined, IDE Reset will
831 be performed by calling the function
832 ide_set_reset(int reset)
833 which has to be defined in a board specific file
838 Set this to enable ATAPI support.
843 Set this to enable support for disks larger than 137GB
844 Also look at CONFIG_SYS_64BIT_LBA.
845 Whithout these , LBA48 support uses 32bit variables and will 'only'
846 support disks up to 2.1TB.
848 CONFIG_SYS_64BIT_LBA:
849 When enabled, makes the IDE subsystem use 64bit sector addresses.
853 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
854 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
855 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
856 maximum numbers of LUNs, SCSI ID's and target
859 The environment variable 'scsidevs' is set to the number of
860 SCSI devices found during the last scan.
862 - NETWORK Support (PCI):
864 Support for Intel 8254x/8257x gigabit chips.
867 Utility code for direct access to the SPI bus on Intel 8257x.
868 This does not do anything useful unless you set at least one
869 of CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC.
871 CONFIG_E1000_SPI_GENERIC
872 Allow generic access to the SPI bus on the Intel 8257x, for
873 example with the "sspi" command.
876 Support for National dp83815 chips.
879 Support for National dp8382[01] gigabit chips.
881 - NETWORK Support (other):
883 CONFIG_DRIVER_AT91EMAC
884 Support for AT91RM9200 EMAC.
887 Define this to use reduced MII inteface
889 CONFIG_DRIVER_AT91EMAC_QUIET
890 If this defined, the driver is quiet.
891 The driver doen't show link status messages.
894 Support for the Calxeda XGMAC device
897 Support for SMSC's LAN91C96 chips.
899 CONFIG_LAN91C96_USE_32_BIT
900 Define this to enable 32 bit addressing
903 Support for SMSC's LAN91C111 chip
906 Define this to hold the physical address
907 of the device (I/O space)
909 CONFIG_SMC_USE_32_BIT
910 Define this if data bus is 32 bits
912 CONFIG_SMC_USE_IOFUNCS
913 Define this to use i/o functions instead of macros
914 (some hardware wont work with macros)
916 CONFIG_SYS_DAVINCI_EMAC_PHY_COUNT
917 Define this if you have more then 3 PHYs.
920 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
922 CONFIG_FTGMAC100_EGIGA
923 Define this to use GE link update with gigabit PHY.
924 Define this if FTGMAC100 is connected to gigabit PHY.
925 If your system has 10/100 PHY only, it might not occur
926 wrong behavior. Because PHY usually return timeout or
927 useless data when polling gigabit status and gigabit
928 control registers. This behavior won't affect the
929 correctnessof 10/100 link speed update.
932 Support for Renesas on-chip Ethernet controller
934 CONFIG_SH_ETHER_USE_PORT
935 Define the number of ports to be used
937 CONFIG_SH_ETHER_PHY_ADDR
938 Define the ETH PHY's address
940 CONFIG_SH_ETHER_CACHE_WRITEBACK
941 If this option is set, the driver enables cache flush.
947 CONFIG_TPM_TIS_INFINEON
948 Support for Infineon i2c bus TPM devices. Only one device
949 per system is supported at this time.
951 CONFIG_TPM_TIS_I2C_BURST_LIMITATION
952 Define the burst count bytes upper limit
955 Support for STMicroelectronics TPM devices. Requires DM_TPM support.
957 CONFIG_TPM_ST33ZP24_I2C
958 Support for STMicroelectronics ST33ZP24 I2C devices.
959 Requires TPM_ST33ZP24 and I2C.
961 CONFIG_TPM_ST33ZP24_SPI
962 Support for STMicroelectronics ST33ZP24 SPI devices.
963 Requires TPM_ST33ZP24 and SPI.
966 Support for Atmel TWI TPM device. Requires I2C support.
969 Support for generic parallel port TPM devices. Only one device
970 per system is supported at this time.
972 CONFIG_TPM_TIS_BASE_ADDRESS
973 Base address where the generic TPM device is mapped
974 to. Contemporary x86 systems usually map it at
978 Define this to enable the TPM support library which provides
979 functional interfaces to some TPM commands.
980 Requires support for a TPM device.
982 CONFIG_TPM_AUTH_SESSIONS
983 Define this to enable authorized functions in the TPM library.
984 Requires CONFIG_TPM and CONFIG_SHA1.
987 At the moment only the UHCI host controller is
988 supported (PIP405, MIP405); define
989 CONFIG_USB_UHCI to enable it.
990 define CONFIG_USB_KEYBOARD to enable the USB Keyboard
991 and define CONFIG_USB_STORAGE to enable the USB
994 Supported are USB Keyboards and USB Floppy drives
997 CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the
998 txfilltuning field in the EHCI controller on reset.
1000 CONFIG_USB_DWC2_REG_ADDR the physical CPU address of the DWC2
1001 HW module registers.
1004 Define the below if you wish to use the USB console.
1005 Once firmware is rebuilt from a serial console issue the
1006 command "setenv stdin usbtty; setenv stdout usbtty" and
1007 attach your USB cable. The Unix command "dmesg" should print
1008 it has found a new device. The environment variable usbtty
1009 can be set to gserial or cdc_acm to enable your device to
1010 appear to a USB host as a Linux gserial device or a
1011 Common Device Class Abstract Control Model serial device.
1012 If you select usbtty = gserial you should be able to enumerate
1014 # modprobe usbserial vendor=0xVendorID product=0xProductID
1015 else if using cdc_acm, simply setting the environment
1016 variable usbtty to be cdc_acm should suffice. The following
1017 might be defined in YourBoardName.h
1020 Define this to build a UDC device
1023 Define this to have a tty type of device available to
1024 talk to the UDC device
1027 Define this to enable the high speed support for usb
1028 device and usbtty. If this feature is enabled, a routine
1029 int is_usbd_high_speed(void)
1030 also needs to be defined by the driver to dynamically poll
1031 whether the enumeration has succeded at high speed or full
1034 CONFIG_SYS_CONSOLE_IS_IN_ENV
1035 Define this if you want stdin, stdout &/or stderr to
1038 If you have a USB-IF assigned VendorID then you may wish to
1039 define your own vendor specific values either in BoardName.h
1040 or directly in usbd_vendor_info.h. If you don't define
1041 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
1042 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
1043 should pretend to be a Linux device to it's target host.
1045 CONFIG_USBD_MANUFACTURER
1046 Define this string as the name of your company for
1047 - CONFIG_USBD_MANUFACTURER "my company"
1049 CONFIG_USBD_PRODUCT_NAME
1050 Define this string as the name of your product
1051 - CONFIG_USBD_PRODUCT_NAME "acme usb device"
1053 CONFIG_USBD_VENDORID
1054 Define this as your assigned Vendor ID from the USB
1055 Implementors Forum. This *must* be a genuine Vendor ID
1056 to avoid polluting the USB namespace.
1057 - CONFIG_USBD_VENDORID 0xFFFF
1059 CONFIG_USBD_PRODUCTID
1060 Define this as the unique Product ID
1062 - CONFIG_USBD_PRODUCTID 0xFFFF
1064 - ULPI Layer Support:
1065 The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via
1066 the generic ULPI layer. The generic layer accesses the ULPI PHY
1067 via the platform viewport, so you need both the genric layer and
1068 the viewport enabled. Currently only Chipidea/ARC based
1069 viewport is supported.
1070 To enable the ULPI layer support, define CONFIG_USB_ULPI and
1071 CONFIG_USB_ULPI_VIEWPORT in your board configuration file.
1072 If your ULPI phy needs a different reference clock than the
1073 standard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to
1074 the appropriate value in Hz.
1077 The MMC controller on the Intel PXA is supported. To
1078 enable this define CONFIG_MMC. The MMC can be
1079 accessed from the boot prompt by mapping the device
1080 to physical memory similar to flash. Command line is
1081 enabled with CONFIG_CMD_MMC. The MMC driver also works with
1082 the FAT fs. This is enabled with CONFIG_CMD_FAT.
1085 Support for Renesas on-chip MMCIF controller
1087 CONFIG_SH_MMCIF_ADDR
1088 Define the base address of MMCIF registers
1091 Define the clock frequency for MMCIF
1093 - USB Device Firmware Update (DFU) class support:
1095 This enables the USB portion of the DFU USB class
1098 This enables support for exposing NAND devices via DFU.
1101 This enables support for exposing RAM via DFU.
1102 Note: DFU spec refer to non-volatile memory usage, but
1103 allow usages beyond the scope of spec - here RAM usage,
1104 one that would help mostly the developer.
1106 CONFIG_SYS_DFU_DATA_BUF_SIZE
1107 Dfu transfer uses a buffer before writing data to the
1108 raw storage device. Make the size (in bytes) of this buffer
1109 configurable. The size of this buffer is also configurable
1110 through the "dfu_bufsiz" environment variable.
1112 CONFIG_SYS_DFU_MAX_FILE_SIZE
1113 When updating files rather than the raw storage device,
1114 we use a static buffer to copy the file into and then write
1115 the buffer once we've been given the whole file. Define
1116 this to the maximum filesize (in bytes) for the buffer.
1117 Default is 4 MiB if undefined.
1119 DFU_DEFAULT_POLL_TIMEOUT
1120 Poll timeout [ms], is the timeout a device can send to the
1121 host. The host must wait for this timeout before sending
1122 a subsequent DFU_GET_STATUS request to the device.
1124 DFU_MANIFEST_POLL_TIMEOUT
1125 Poll timeout [ms], which the device sends to the host when
1126 entering dfuMANIFEST state. Host waits this timeout, before
1127 sending again an USB request to the device.
1129 - Journaling Flash filesystem support:
1131 Define these for a default partition on a NAND device
1133 CONFIG_SYS_JFFS2_FIRST_SECTOR,
1134 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
1135 Define these for a default partition on a NOR device
1138 See Kconfig help for available keyboard drivers.
1142 Define this to enable a custom keyboard support.
1143 This simply calls drv_keyboard_init() which must be
1144 defined in your board-specific files. This option is deprecated
1145 and is only used by novena. For new boards, use driver model
1150 Enable the Freescale DIU video driver. Reference boards for
1151 SOCs that have a DIU should define this macro to enable DIU
1152 support, and should also define these other macros:
1157 CONFIG_VIDEO_SW_CURSOR
1158 CONFIG_VGA_AS_SINGLE_DEVICE
1160 CONFIG_VIDEO_BMP_LOGO
1162 The DIU driver will look for the 'video-mode' environment
1163 variable, and if defined, enable the DIU as a console during
1164 boot. See the documentation file doc/README.video for a
1165 description of this variable.
1167 - LCD Support: CONFIG_LCD
1169 Define this to enable LCD support (for output to LCD
1170 display); also select one of the supported displays
1171 by defining one of these:
1175 HITACHI TX09D70VM1CCA, 3.5", 240x320.
1177 CONFIG_NEC_NL6448AC33:
1179 NEC NL6448AC33-18. Active, color, single scan.
1181 CONFIG_NEC_NL6448BC20
1183 NEC NL6448BC20-08. 6.5", 640x480.
1184 Active, color, single scan.
1186 CONFIG_NEC_NL6448BC33_54
1188 NEC NL6448BC33-54. 10.4", 640x480.
1189 Active, color, single scan.
1193 Sharp 320x240. Active, color, single scan.
1194 It isn't 16x9, and I am not sure what it is.
1196 CONFIG_SHARP_LQ64D341
1198 Sharp LQ64D341 display, 640x480.
1199 Active, color, single scan.
1203 HLD1045 display, 640x480.
1204 Active, color, single scan.
1208 Optrex CBL50840-2 NF-FW 99 22 M5
1210 Hitachi LMG6912RPFC-00T
1214 320x240. Black & white.
1216 CONFIG_LCD_ALIGNMENT
1218 Normally the LCD is page-aligned (typically 4KB). If this is
1219 defined then the LCD will be aligned to this value instead.
1220 For ARM it is sometimes useful to use MMU_SECTION_SIZE
1221 here, since it is cheaper to change data cache settings on
1222 a per-section basis.
1227 Sometimes, for example if the display is mounted in portrait
1228 mode or even if it's mounted landscape but rotated by 180degree,
1229 we need to rotate our content of the display relative to the
1230 framebuffer, so that user can read the messages which are
1232 Once CONFIG_LCD_ROTATION is defined, the lcd_console will be
1233 initialized with a given rotation from "vl_rot" out of
1234 "vidinfo_t" which is provided by the board specific code.
1235 The value for vl_rot is coded as following (matching to
1236 fbcon=rotate:<n> linux-kernel commandline):
1237 0 = no rotation respectively 0 degree
1238 1 = 90 degree rotation
1239 2 = 180 degree rotation
1240 3 = 270 degree rotation
1242 If CONFIG_LCD_ROTATION is not defined, the console will be
1243 initialized with 0degree rotation.
1247 Support drawing of RLE8-compressed bitmaps on the LCD.
1251 Enables an 'i2c edid' command which can read EDID
1252 information over I2C from an attached LCD display.
1255 CONFIG_PHY_CLOCK_FREQ (ppc4xx)
1257 The clock frequency of the MII bus
1259 CONFIG_PHY_RESET_DELAY
1261 Some PHY like Intel LXT971A need extra delay after
1262 reset before any MII register access is possible.
1263 For such PHY, set this option to the usec delay
1264 required. (minimum 300usec for LXT971A)
1266 CONFIG_PHY_CMD_DELAY (ppc4xx)
1268 Some PHY like Intel LXT971A need extra delay after
1269 command issued before MII status register can be read
1274 Define a default value for the IP address to use for
1275 the default Ethernet interface, in case this is not
1276 determined through e.g. bootp.
1277 (Environment variable "ipaddr")
1279 - Server IP address:
1282 Defines a default value for the IP address of a TFTP
1283 server to contact when using the "tftboot" command.
1284 (Environment variable "serverip")
1286 CONFIG_KEEP_SERVERADDR
1288 Keeps the server's MAC address, in the env 'serveraddr'
1289 for passing to bootargs (like Linux's netconsole option)
1291 - Gateway IP address:
1294 Defines a default value for the IP address of the
1295 default router where packets to other networks are
1297 (Environment variable "gatewayip")
1302 Defines a default value for the subnet mask (or
1303 routing prefix) which is used to determine if an IP
1304 address belongs to the local subnet or needs to be
1305 forwarded through a router.
1306 (Environment variable "netmask")
1308 - BOOTP Recovery Mode:
1309 CONFIG_BOOTP_RANDOM_DELAY
1311 If you have many targets in a network that try to
1312 boot using BOOTP, you may want to avoid that all
1313 systems send out BOOTP requests at precisely the same
1314 moment (which would happen for instance at recovery
1315 from a power failure, when all systems will try to
1316 boot, thus flooding the BOOTP server. Defining
1317 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
1318 inserted before sending out BOOTP requests. The
1319 following delays are inserted then:
1321 1st BOOTP request: delay 0 ... 1 sec
1322 2nd BOOTP request: delay 0 ... 2 sec
1323 3rd BOOTP request: delay 0 ... 4 sec
1325 BOOTP requests: delay 0 ... 8 sec
1327 CONFIG_BOOTP_ID_CACHE_SIZE
1329 BOOTP packets are uniquely identified using a 32-bit ID. The
1330 server will copy the ID from client requests to responses and
1331 U-Boot will use this to determine if it is the destination of
1332 an incoming response. Some servers will check that addresses
1333 aren't in use before handing them out (usually using an ARP
1334 ping) and therefore take up to a few hundred milliseconds to
1335 respond. Network congestion may also influence the time it
1336 takes for a response to make it back to the client. If that
1337 time is too long, U-Boot will retransmit requests. In order
1338 to allow earlier responses to still be accepted after these
1339 retransmissions, U-Boot's BOOTP client keeps a small cache of
1340 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
1341 cache. The default is to keep IDs for up to four outstanding
1342 requests. Increasing this will allow U-Boot to accept offers
1343 from a BOOTP client in networks with unusually high latency.
1345 - DHCP Advanced Options:
1346 You can fine tune the DHCP functionality by defining
1347 CONFIG_BOOTP_* symbols:
1349 CONFIG_BOOTP_NISDOMAIN
1350 CONFIG_BOOTP_BOOTFILESIZE
1351 CONFIG_BOOTP_NTPSERVER
1352 CONFIG_BOOTP_TIMEOFFSET
1353 CONFIG_BOOTP_VENDOREX
1354 CONFIG_BOOTP_MAY_FAIL
1356 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
1357 environment variable, not the BOOTP server.
1359 CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found
1360 after the configured retry count, the call will fail
1361 instead of starting over. This can be used to fail over
1362 to Link-local IP address configuration if the DHCP server
1365 CONFIG_BOOTP_DHCP_REQUEST_DELAY
1367 A 32bit value in microseconds for a delay between
1368 receiving a "DHCP Offer" and sending the "DHCP Request".
1369 This fixes a problem with certain DHCP servers that don't
1370 respond 100% of the time to a "DHCP request". E.g. On an
1371 AT91RM9200 processor running at 180MHz, this delay needed
1372 to be *at least* 15,000 usec before a Windows Server 2003
1373 DHCP server would reply 100% of the time. I recommend at
1374 least 50,000 usec to be safe. The alternative is to hope
1375 that one of the retries will be successful but note that
1376 the DHCP timeout and retry process takes a longer than
1379 - Link-local IP address negotiation:
1380 Negotiate with other link-local clients on the local network
1381 for an address that doesn't require explicit configuration.
1382 This is especially useful if a DHCP server cannot be guaranteed
1383 to exist in all environments that the device must operate.
1385 See doc/README.link-local for more information.
1387 - MAC address from environment variables
1389 FDT_SEQ_MACADDR_FROM_ENV
1391 Fix-up device tree with MAC addresses fetched sequentially from
1392 environment variables. This config work on assumption that
1393 non-usable ethernet node of device-tree are either not present
1394 or their status has been marked as "disabled".
1397 CONFIG_CDP_DEVICE_ID
1399 The device id used in CDP trigger frames.
1401 CONFIG_CDP_DEVICE_ID_PREFIX
1403 A two character string which is prefixed to the MAC address
1408 A printf format string which contains the ascii name of
1409 the port. Normally is set to "eth%d" which sets
1410 eth0 for the first Ethernet, eth1 for the second etc.
1412 CONFIG_CDP_CAPABILITIES
1414 A 32bit integer which indicates the device capabilities;
1415 0x00000010 for a normal host which does not forwards.
1419 An ascii string containing the version of the software.
1423 An ascii string containing the name of the platform.
1427 A 32bit integer sent on the trigger.
1429 CONFIG_CDP_POWER_CONSUMPTION
1431 A 16bit integer containing the power consumption of the
1432 device in .1 of milliwatts.
1434 CONFIG_CDP_APPLIANCE_VLAN_TYPE
1436 A byte containing the id of the VLAN.
1438 - Status LED: CONFIG_LED_STATUS
1440 Several configurations allow to display the current
1441 status using a LED. For instance, the LED will blink
1442 fast while running U-Boot code, stop blinking as
1443 soon as a reply to a BOOTP request was received, and
1444 start blinking slow once the Linux kernel is running
1445 (supported by a status LED driver in the Linux
1446 kernel). Defining CONFIG_LED_STATUS enables this
1451 CONFIG_LED_STATUS_GPIO
1452 The status LED can be connected to a GPIO pin.
1453 In such cases, the gpio_led driver can be used as a
1454 status LED backend implementation. Define CONFIG_LED_STATUS_GPIO
1455 to include the gpio_led driver in the U-Boot binary.
1457 CONFIG_GPIO_LED_INVERTED_TABLE
1458 Some GPIO connected LEDs may have inverted polarity in which
1459 case the GPIO high value corresponds to LED off state and
1460 GPIO low value corresponds to LED on state.
1461 In such cases CONFIG_GPIO_LED_INVERTED_TABLE may be defined
1462 with a list of GPIO LEDs that have inverted polarity.
1465 - drivers/i2c/ppc4xx_i2c.c
1466 - activate this driver with CONFIG_SYS_I2C_PPC4XX
1467 - CONFIG_SYS_I2C_PPC4XX_CH0 activate hardware channel 0
1468 - CONFIG_SYS_I2C_PPC4XX_CH1 activate hardware channel 1
1470 - drivers/i2c/s3c24x0_i2c.c:
1471 - activate this driver with CONFIG_SYS_I2C_S3C24X0
1472 - This driver adds i2c buses (11 for Exynos5250, Exynos5420
1473 9 i2c buses for Exynos4 and 1 for S3C24X0 SoCs from Samsung)
1474 with a fix speed from 100000 and the slave addr 0!
1478 CONFIG_SYS_NUM_I2C_BUSES
1479 Hold the number of i2c buses you want to use.
1481 CONFIG_SYS_I2C_DIRECT_BUS
1482 define this, if you don't use i2c muxes on your hardware.
1483 if CONFIG_SYS_I2C_MAX_HOPS is not defined or == 0 you can
1486 CONFIG_SYS_I2C_MAX_HOPS
1487 define how many muxes are maximal consecutively connected
1488 on one i2c bus. If you not use i2c muxes, omit this
1491 CONFIG_SYS_I2C_BUSES
1492 hold a list of buses you want to use, only used if
1493 CONFIG_SYS_I2C_DIRECT_BUS is not defined, for example
1494 a board with CONFIG_SYS_I2C_MAX_HOPS = 1 and
1495 CONFIG_SYS_NUM_I2C_BUSES = 9:
1497 CONFIG_SYS_I2C_BUSES {{0, {I2C_NULL_HOP}}, \
1498 {0, {{I2C_MUX_PCA9547, 0x70, 1}}}, \
1499 {0, {{I2C_MUX_PCA9547, 0x70, 2}}}, \
1500 {0, {{I2C_MUX_PCA9547, 0x70, 3}}}, \
1501 {0, {{I2C_MUX_PCA9547, 0x70, 4}}}, \
1502 {0, {{I2C_MUX_PCA9547, 0x70, 5}}}, \
1503 {1, {I2C_NULL_HOP}}, \
1504 {1, {{I2C_MUX_PCA9544, 0x72, 1}}}, \
1505 {1, {{I2C_MUX_PCA9544, 0x72, 2}}}, \
1509 bus 0 on adapter 0 without a mux
1510 bus 1 on adapter 0 with a PCA9547 on address 0x70 port 1
1511 bus 2 on adapter 0 with a PCA9547 on address 0x70 port 2
1512 bus 3 on adapter 0 with a PCA9547 on address 0x70 port 3
1513 bus 4 on adapter 0 with a PCA9547 on address 0x70 port 4
1514 bus 5 on adapter 0 with a PCA9547 on address 0x70 port 5
1515 bus 6 on adapter 1 without a mux
1516 bus 7 on adapter 1 with a PCA9544 on address 0x72 port 1
1517 bus 8 on adapter 1 with a PCA9544 on address 0x72 port 2
1519 If you do not have i2c muxes on your board, omit this define.
1521 - Legacy I2C Support:
1522 If you use the software i2c interface (CONFIG_SYS_I2C_SOFT)
1523 then the following macros need to be defined (examples are
1524 from include/configs/lwmon.h):
1528 (Optional). Any commands necessary to enable the I2C
1529 controller or configure ports.
1531 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
1535 The code necessary to make the I2C data line active
1536 (driven). If the data line is open collector, this
1539 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
1543 The code necessary to make the I2C data line tri-stated
1544 (inactive). If the data line is open collector, this
1547 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
1551 Code that returns true if the I2C data line is high,
1554 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
1558 If <bit> is true, sets the I2C data line high. If it
1559 is false, it clears it (low).
1561 eg: #define I2C_SDA(bit) \
1562 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
1563 else immr->im_cpm.cp_pbdat &= ~PB_SDA
1567 If <bit> is true, sets the I2C clock line high. If it
1568 is false, it clears it (low).
1570 eg: #define I2C_SCL(bit) \
1571 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
1572 else immr->im_cpm.cp_pbdat &= ~PB_SCL
1576 This delay is invoked four times per clock cycle so this
1577 controls the rate of data transfer. The data rate thus
1578 is 1 / (I2C_DELAY * 4). Often defined to be something
1581 #define I2C_DELAY udelay(2)
1583 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
1585 If your arch supports the generic GPIO framework (asm/gpio.h),
1586 then you may alternatively define the two GPIOs that are to be
1587 used as SCL / SDA. Any of the previous I2C_xxx macros will
1588 have GPIO-based defaults assigned to them as appropriate.
1590 You should define these to the GPIO value as given directly to
1591 the generic GPIO functions.
1593 CONFIG_SYS_I2C_INIT_BOARD
1595 When a board is reset during an i2c bus transfer
1596 chips might think that the current transfer is still
1597 in progress. On some boards it is possible to access
1598 the i2c SCLK line directly, either by using the
1599 processor pin as a GPIO or by having a second pin
1600 connected to the bus. If this option is defined a
1601 custom i2c_init_board() routine in boards/xxx/board.c
1602 is run early in the boot sequence.
1604 CONFIG_I2C_MULTI_BUS
1606 This option allows the use of multiple I2C buses, each of which
1607 must have a controller. At any point in time, only one bus is
1608 active. To switch to a different bus, use the 'i2c dev' command.
1609 Note that bus numbering is zero-based.
1611 CONFIG_SYS_I2C_NOPROBES
1613 This option specifies a list of I2C devices that will be skipped
1614 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS
1615 is set, specify a list of bus-device pairs. Otherwise, specify
1616 a 1D array of device addresses
1619 #undef CONFIG_I2C_MULTI_BUS
1620 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}
1622 will skip addresses 0x50 and 0x68 on a board with one I2C bus
1624 #define CONFIG_I2C_MULTI_BUS
1625 #define CONFIG_SYS_I2C_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
1627 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
1629 CONFIG_SYS_SPD_BUS_NUM
1631 If defined, then this indicates the I2C bus number for DDR SPD.
1632 If not defined, then U-Boot assumes that SPD is on I2C bus 0.
1634 CONFIG_SYS_RTC_BUS_NUM
1636 If defined, then this indicates the I2C bus number for the RTC.
1637 If not defined, then U-Boot assumes that RTC is on I2C bus 0.
1639 CONFIG_SOFT_I2C_READ_REPEATED_START
1641 defining this will force the i2c_read() function in
1642 the soft_i2c driver to perform an I2C repeated start
1643 between writing the address pointer and reading the
1644 data. If this define is omitted the default behaviour
1645 of doing a stop-start sequence will be used. Most I2C
1646 devices can use either method, but some require one or
1649 - SPI Support: CONFIG_SPI
1651 Enables SPI driver (so far only tested with
1652 SPI EEPROM, also an instance works with Crystal A/D and
1653 D/As on the SACSng board)
1657 Enables a software (bit-bang) SPI driver rather than
1658 using hardware support. This is a general purpose
1659 driver that only requires three general I/O port pins
1660 (two outputs, one input) to function. If this is
1661 defined, the board configuration must define several
1662 SPI configuration items (port pins to use, etc). For
1663 an example, see include/configs/sacsng.h.
1665 CONFIG_SYS_SPI_MXC_WAIT
1666 Timeout for waiting until spi transfer completed.
1667 default: (CONFIG_SYS_HZ/100) /* 10 ms */
1669 - FPGA Support: CONFIG_FPGA
1671 Enables FPGA subsystem.
1673 CONFIG_FPGA_<vendor>
1675 Enables support for specific chip vendors.
1678 CONFIG_FPGA_<family>
1680 Enables support for FPGA family.
1681 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
1685 Specify the number of FPGA devices to support.
1687 CONFIG_SYS_FPGA_PROG_FEEDBACK
1689 Enable printing of hash marks during FPGA configuration.
1691 CONFIG_SYS_FPGA_CHECK_BUSY
1693 Enable checks on FPGA configuration interface busy
1694 status by the configuration function. This option
1695 will require a board or device specific function to
1700 If defined, a function that provides delays in the FPGA
1701 configuration driver.
1703 CONFIG_SYS_FPGA_CHECK_CTRLC
1704 Allow Control-C to interrupt FPGA configuration
1706 CONFIG_SYS_FPGA_CHECK_ERROR
1708 Check for configuration errors during FPGA bitfile
1709 loading. For example, abort during Virtex II
1710 configuration if the INIT_B line goes low (which
1711 indicated a CRC error).
1713 CONFIG_SYS_FPGA_WAIT_INIT
1715 Maximum time to wait for the INIT_B line to de-assert
1716 after PROB_B has been de-asserted during a Virtex II
1717 FPGA configuration sequence. The default time is 500
1720 CONFIG_SYS_FPGA_WAIT_BUSY
1722 Maximum time to wait for BUSY to de-assert during
1723 Virtex II FPGA configuration. The default is 5 ms.
1725 CONFIG_SYS_FPGA_WAIT_CONFIG
1727 Time to wait after FPGA configuration. The default is
1730 - Configuration Management:
1734 If defined, this string will be added to the U-Boot
1735 version information (U_BOOT_VERSION)
1737 - Vendor Parameter Protection:
1739 U-Boot considers the values of the environment
1740 variables "serial#" (Board Serial Number) and
1741 "ethaddr" (Ethernet Address) to be parameters that
1742 are set once by the board vendor / manufacturer, and
1743 protects these variables from casual modification by
1744 the user. Once set, these variables are read-only,
1745 and write or delete attempts are rejected. You can
1746 change this behaviour:
1748 If CONFIG_ENV_OVERWRITE is #defined in your config
1749 file, the write protection for vendor parameters is
1750 completely disabled. Anybody can change or delete
1753 Alternatively, if you define _both_ an ethaddr in the
1754 default env _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
1755 Ethernet address is installed in the environment,
1756 which can be changed exactly ONCE by the user. [The
1757 serial# is unaffected by this, i. e. it remains
1760 The same can be accomplished in a more flexible way
1761 for any variable by configuring the type of access
1762 to allow for those variables in the ".flags" variable
1763 or define CONFIG_ENV_FLAGS_LIST_STATIC.
1768 Define this variable to enable the reservation of
1769 "protected RAM", i. e. RAM which is not overwritten
1770 by U-Boot. Define CONFIG_PRAM to hold the number of
1771 kB you want to reserve for pRAM. You can overwrite
1772 this default value by defining an environment
1773 variable "pram" to the number of kB you want to
1774 reserve. Note that the board info structure will
1775 still show the full amount of RAM. If pRAM is
1776 reserved, a new environment variable "mem" will
1777 automatically be defined to hold the amount of
1778 remaining RAM in a form that can be passed as boot
1779 argument to Linux, for instance like that:
1781 setenv bootargs ... mem=\${mem}
1784 This way you can tell Linux not to use this memory,
1785 either, which results in a memory region that will
1786 not be affected by reboots.
1788 *WARNING* If your board configuration uses automatic
1789 detection of the RAM size, you must make sure that
1790 this memory test is non-destructive. So far, the
1791 following board configurations are known to be
1794 IVMS8, IVML24, SPD8xx,
1795 HERMES, IP860, RPXlite, LWMON,
1798 - Access to physical memory region (> 4GB)
1799 Some basic support is provided for operations on memory not
1800 normally accessible to U-Boot - e.g. some architectures
1801 support access to more than 4GB of memory on 32-bit
1802 machines using physical address extension or similar.
1803 Define CONFIG_PHYSMEM to access this basic support, which
1804 currently only supports clearing the memory.
1807 CONFIG_NET_RETRY_COUNT
1809 This variable defines the number of retries for
1810 network operations like ARP, RARP, TFTP, or BOOTP
1811 before giving up the operation. If not defined, a
1812 default value of 5 is used.
1816 Timeout waiting for an ARP reply in milliseconds.
1820 Timeout in milliseconds used in NFS protocol.
1821 If you encounter "ERROR: Cannot umount" in nfs command,
1822 try longer timeout such as
1823 #define CONFIG_NFS_TIMEOUT 10000UL
1827 In the current implementation, the local variables
1828 space and global environment variables space are
1829 separated. Local variables are those you define by
1830 simply typing `name=value'. To access a local
1831 variable later on, you have write `$name' or
1832 `${name}'; to execute the contents of a variable
1833 directly type `$name' at the command prompt.
1835 Global environment variables are those you use
1836 setenv/printenv to work with. To run a command stored
1837 in such a variable, you need to use the run command,
1838 and you must not use the '$' sign to access them.
1840 To store commands and special characters in a
1841 variable, please use double quotation marks
1842 surrounding the whole text of the variable, instead
1843 of the backslashes before semicolons and special
1846 - Command Line Editing and History:
1847 CONFIG_CMDLINE_PS_SUPPORT
1849 Enable support for changing the command prompt string
1850 at run-time. Only static string is supported so far.
1851 The string is obtained from environment variables PS1
1854 - Default Environment:
1855 CONFIG_EXTRA_ENV_SETTINGS
1857 Define this to contain any number of null terminated
1858 strings (variable = value pairs) that will be part of
1859 the default environment compiled into the boot image.
1861 For example, place something like this in your
1862 board's config file:
1864 #define CONFIG_EXTRA_ENV_SETTINGS \
1868 Warning: This method is based on knowledge about the
1869 internal format how the environment is stored by the
1870 U-Boot code. This is NOT an official, exported
1871 interface! Although it is unlikely that this format
1872 will change soon, there is no guarantee either.
1873 You better know what you are doing here.
1875 Note: overly (ab)use of the default environment is
1876 discouraged. Make sure to check other ways to preset
1877 the environment like the "source" command or the
1880 CONFIG_DELAY_ENVIRONMENT
1882 Normally the environment is loaded when the board is
1883 initialised so that it is available to U-Boot. This inhibits
1884 that so that the environment is not available until
1885 explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL
1886 this is instead controlled by the value of
1887 /config/load-environment.
1889 - TFTP Fixed UDP Port:
1892 If this is defined, the environment variable tftpsrcp
1893 is used to supply the TFTP UDP source port value.
1894 If tftpsrcp isn't defined, the normal pseudo-random port
1895 number generator is used.
1897 Also, the environment variable tftpdstp is used to supply
1898 the TFTP UDP destination port value. If tftpdstp isn't
1899 defined, the normal port 69 is used.
1901 The purpose for tftpsrcp is to allow a TFTP server to
1902 blindly start the TFTP transfer using the pre-configured
1903 target IP address and UDP port. This has the effect of
1904 "punching through" the (Windows XP) firewall, allowing
1905 the remainder of the TFTP transfer to proceed normally.
1906 A better solution is to properly configure the firewall,
1907 but sometimes that is not allowed.
1909 CONFIG_STANDALONE_LOAD_ADDR
1911 This option defines a board specific value for the
1912 address where standalone program gets loaded, thus
1913 overwriting the architecture dependent default
1916 - Frame Buffer Address:
1919 Define CONFIG_FB_ADDR if you want to use specific
1920 address for frame buffer. This is typically the case
1921 when using a graphics controller has separate video
1922 memory. U-Boot will then place the frame buffer at
1923 the given address instead of dynamically reserving it
1924 in system RAM by calling lcd_setmem(), which grabs
1925 the memory for the frame buffer depending on the
1926 configured panel size.
1928 Please see board_init_f function.
1930 - Automatic software updates via TFTP server
1932 CONFIG_UPDATE_TFTP_CNT_MAX
1933 CONFIG_UPDATE_TFTP_MSEC_MAX
1935 These options enable and control the auto-update feature;
1936 for a more detailed description refer to doc/README.update.
1938 - MTD Support (mtdparts command, UBI support)
1939 CONFIG_MTD_UBI_WL_THRESHOLD
1940 This parameter defines the maximum difference between the highest
1941 erase counter value and the lowest erase counter value of eraseblocks
1942 of UBI devices. When this threshold is exceeded, UBI starts performing
1943 wear leveling by means of moving data from eraseblock with low erase
1944 counter to eraseblocks with high erase counter.
1946 The default value should be OK for SLC NAND flashes, NOR flashes and
1947 other flashes which have eraseblock life-cycle 100000 or more.
1948 However, in case of MLC NAND flashes which typically have eraseblock
1949 life-cycle less than 10000, the threshold should be lessened (e.g.,
1950 to 128 or 256, although it does not have to be power of 2).
1954 CONFIG_MTD_UBI_BEB_LIMIT
1955 This option specifies the maximum bad physical eraseblocks UBI
1956 expects on the MTD device (per 1024 eraseblocks). If the
1957 underlying flash does not admit of bad eraseblocks (e.g. NOR
1958 flash), this value is ignored.
1960 NAND datasheets often specify the minimum and maximum NVM
1961 (Number of Valid Blocks) for the flashes' endurance lifetime.
1962 The maximum expected bad eraseblocks per 1024 eraseblocks
1963 then can be calculated as "1024 * (1 - MinNVB / MaxNVB)",
1964 which gives 20 for most NANDs (MaxNVB is basically the total
1965 count of eraseblocks on the chip).
1967 To put it differently, if this value is 20, UBI will try to
1968 reserve about 1.9% of physical eraseblocks for bad blocks
1969 handling. And that will be 1.9% of eraseblocks on the entire
1970 NAND chip, not just the MTD partition UBI attaches. This means
1971 that if you have, say, a NAND flash chip admits maximum 40 bad
1972 eraseblocks, and it is split on two MTD partitions of the same
1973 size, UBI will reserve 40 eraseblocks when attaching a
1978 CONFIG_MTD_UBI_FASTMAP
1979 Fastmap is a mechanism which allows attaching an UBI device
1980 in nearly constant time. Instead of scanning the whole MTD device it
1981 only has to locate a checkpoint (called fastmap) on the device.
1982 The on-flash fastmap contains all information needed to attach
1983 the device. Using fastmap makes only sense on large devices where
1984 attaching by scanning takes long. UBI will not automatically install
1985 a fastmap on old images, but you can set the UBI parameter
1986 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT to 1 if you want so. Please note
1987 that fastmap-enabled images are still usable with UBI implementations
1988 without fastmap support. On typical flash devices the whole fastmap
1989 fits into one PEB. UBI will reserve PEBs to hold two fastmaps.
1991 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT
1992 Set this parameter to enable fastmap automatically on images
1996 CONFIG_MTD_UBI_FM_DEBUG
1997 Enable UBI fastmap debug
2002 Enable building of SPL globally.
2005 LDSCRIPT for linking the SPL binary.
2007 CONFIG_SPL_MAX_FOOTPRINT
2008 Maximum size in memory allocated to the SPL, BSS included.
2009 When defined, the linker checks that the actual memory
2010 used by SPL from _start to __bss_end does not exceed it.
2011 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
2012 must not be both defined at the same time.
2015 Maximum size of the SPL image (text, data, rodata, and
2016 linker lists sections), BSS excluded.
2017 When defined, the linker checks that the actual size does
2020 CONFIG_SPL_RELOC_TEXT_BASE
2021 Address to relocate to. If unspecified, this is equal to
2022 CONFIG_SPL_TEXT_BASE (i.e. no relocation is done).
2024 CONFIG_SPL_BSS_START_ADDR
2025 Link address for the BSS within the SPL binary.
2027 CONFIG_SPL_BSS_MAX_SIZE
2028 Maximum size in memory allocated to the SPL BSS.
2029 When defined, the linker checks that the actual memory used
2030 by SPL from __bss_start to __bss_end does not exceed it.
2031 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
2032 must not be both defined at the same time.
2035 Adress of the start of the stack SPL will use
2037 CONFIG_SPL_PANIC_ON_RAW_IMAGE
2038 When defined, SPL will panic() if the image it has
2039 loaded does not have a signature.
2040 Defining this is useful when code which loads images
2041 in SPL cannot guarantee that absolutely all read errors
2043 An example is the LPC32XX MLC NAND driver, which will
2044 consider that a completely unreadable NAND block is bad,
2045 and thus should be skipped silently.
2047 CONFIG_SPL_RELOC_STACK
2048 Adress of the start of the stack SPL will use after
2049 relocation. If unspecified, this is equal to
2052 CONFIG_SYS_SPL_MALLOC_START
2053 Starting address of the malloc pool used in SPL.
2054 When this option is set the full malloc is used in SPL and
2055 it is set up by spl_init() and before that, the simple malloc()
2056 can be used if CONFIG_SYS_MALLOC_F is defined.
2058 CONFIG_SYS_SPL_MALLOC_SIZE
2059 The size of the malloc pool used in SPL.
2062 Enable booting directly to an OS from SPL.
2063 See also: doc/README.falcon
2065 CONFIG_SPL_DISPLAY_PRINT
2066 For ARM, enable an optional function to print more information
2067 about the running system.
2069 CONFIG_SPL_INIT_MINIMAL
2070 Arch init code should be built for a very small image
2072 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
2073 Partition on the MMC to load U-Boot from when the MMC is being
2076 CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
2077 Sector to load kernel uImage from when MMC is being
2078 used in raw mode (for Falcon mode)
2080 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR,
2081 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS
2082 Sector and number of sectors to load kernel argument
2083 parameters from when MMC is being used in raw mode
2086 CONFIG_SPL_FS_LOAD_PAYLOAD_NAME
2087 Filename to read to load U-Boot when reading from filesystem
2089 CONFIG_SPL_FS_LOAD_KERNEL_NAME
2090 Filename to read to load kernel uImage when reading
2091 from filesystem (for Falcon mode)
2093 CONFIG_SPL_FS_LOAD_ARGS_NAME
2094 Filename to read to load kernel argument parameters
2095 when reading from filesystem (for Falcon mode)
2097 CONFIG_SPL_MPC83XX_WAIT_FOR_NAND
2098 Set this for NAND SPL on PPC mpc83xx targets, so that
2099 start.S waits for the rest of the SPL to load before
2100 continuing (the hardware starts execution after just
2101 loading the first page rather than the full 4K).
2103 CONFIG_SPL_SKIP_RELOCATE
2104 Avoid SPL relocation
2106 CONFIG_SPL_NAND_IDENT
2107 SPL uses the chip ID list to identify the NAND flash.
2108 Requires CONFIG_SPL_NAND_BASE.
2111 Support for a lightweight UBI (fastmap) scanner and
2114 CONFIG_SPL_NAND_RAW_ONLY
2115 Support to boot only raw u-boot.bin images. Use this only
2116 if you need to save space.
2118 CONFIG_SPL_COMMON_INIT_DDR
2119 Set for common ddr init with serial presence detect in
2122 CONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT,
2123 CONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE,
2124 CONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS,
2125 CONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE,
2126 CONFIG_SYS_NAND_ECCBYTES
2127 Defines the size and behavior of the NAND that SPL uses
2130 CONFIG_SYS_NAND_U_BOOT_OFFS
2131 Location in NAND to read U-Boot from
2133 CONFIG_SYS_NAND_U_BOOT_DST
2134 Location in memory to load U-Boot to
2136 CONFIG_SYS_NAND_U_BOOT_SIZE
2137 Size of image to load
2139 CONFIG_SYS_NAND_U_BOOT_START
2140 Entry point in loaded image to jump to
2142 CONFIG_SYS_NAND_HW_ECC_OOBFIRST
2143 Define this if you need to first read the OOB and then the
2144 data. This is used, for example, on davinci platforms.
2146 CONFIG_SPL_RAM_DEVICE
2147 Support for running image already present in ram, in SPL binary
2150 Image offset to which the SPL should be padded before appending
2151 the SPL payload. By default, this is defined as
2152 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
2153 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
2154 payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
2157 Final target image containing SPL and payload. Some SPLs
2158 use an arch-specific makefile fragment instead, for
2159 example if more than one image needs to be produced.
2161 CONFIG_SPL_FIT_PRINT
2162 Printing information about a FIT image adds quite a bit of
2163 code to SPL. So this is normally disabled in SPL. Use this
2164 option to re-enable it. This will affect the output of the
2165 bootm command when booting a FIT image.
2169 Enable building of TPL globally.
2172 Image offset to which the TPL should be padded before appending
2173 the TPL payload. By default, this is defined as
2174 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
2175 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
2176 payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
2178 - Interrupt support (PPC):
2180 There are common interrupt_init() and timer_interrupt()
2181 for all PPC archs. interrupt_init() calls interrupt_init_cpu()
2182 for CPU specific initialization. interrupt_init_cpu()
2183 should set decrementer_count to appropriate value. If
2184 CPU resets decrementer automatically after interrupt
2185 (ppc4xx) it should set decrementer_count to zero.
2186 timer_interrupt() calls timer_interrupt_cpu() for CPU
2187 specific handling. If board has watchdog / status_led
2188 / other_activity_monitor it works automatically from
2189 general timer_interrupt().
2192 Board initialization settings:
2193 ------------------------------
2195 During Initialization u-boot calls a number of board specific functions
2196 to allow the preparation of board specific prerequisites, e.g. pin setup
2197 before drivers are initialized. To enable these callbacks the
2198 following configuration macros have to be defined. Currently this is
2199 architecture specific, so please check arch/your_architecture/lib/board.c
2200 typically in board_init_f() and board_init_r().
2202 - CONFIG_BOARD_EARLY_INIT_F: Call board_early_init_f()
2203 - CONFIG_BOARD_EARLY_INIT_R: Call board_early_init_r()
2204 - CONFIG_BOARD_LATE_INIT: Call board_late_init()
2205 - CONFIG_BOARD_POSTCLK_INIT: Call board_postclk_init()
2207 Configuration Settings:
2208 -----------------------
2210 - MEM_SUPPORT_64BIT_DATA: Defined automatically if compiled as 64-bit.
2211 Optionally it can be defined to support 64-bit memory commands.
2213 - CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
2214 undefine this when you're short of memory.
2216 - CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default
2217 width of the commands listed in the 'help' command output.
2219 - CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to
2220 prompt for user input.
2222 - CONFIG_SYS_CBSIZE: Buffer size for input from the Console
2224 - CONFIG_SYS_PBSIZE: Buffer size for Console output
2226 - CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands
2228 - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
2229 the application (usually a Linux kernel) when it is
2232 - CONFIG_SYS_BAUDRATE_TABLE:
2233 List of legal baudrate settings for this board.
2235 - CONFIG_SYS_MEM_RESERVE_SECURE
2236 Only implemented for ARMv8 for now.
2237 If defined, the size of CONFIG_SYS_MEM_RESERVE_SECURE memory
2238 is substracted from total RAM and won't be reported to OS.
2239 This memory can be used as secure memory. A variable
2240 gd->arch.secure_ram is used to track the location. In systems
2241 the RAM base is not zero, or RAM is divided into banks,
2242 this variable needs to be recalcuated to get the address.
2244 - CONFIG_SYS_MEM_TOP_HIDE:
2245 If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,
2246 this specified memory area will get subtracted from the top
2247 (end) of RAM and won't get "touched" at all by U-Boot. By
2248 fixing up gd->ram_size the Linux kernel should gets passed
2249 the now "corrected" memory size and won't touch it either.
2250 This should work for arch/ppc and arch/powerpc. Only Linux
2251 board ports in arch/powerpc with bootwrapper support that
2252 recalculate the memory size from the SDRAM controller setup
2253 will have to get fixed in Linux additionally.
2255 This option can be used as a workaround for the 440EPx/GRx
2256 CHIP 11 errata where the last 256 bytes in SDRAM shouldn't
2259 WARNING: Please make sure that this value is a multiple of
2260 the Linux page size (normally 4k). If this is not the case,
2261 then the end address of the Linux memory will be located at a
2262 non page size aligned address and this could cause major
2265 - CONFIG_SYS_LOADS_BAUD_CHANGE:
2266 Enable temporary baudrate change while serial download
2268 - CONFIG_SYS_SDRAM_BASE:
2269 Physical start address of SDRAM. _Must_ be 0 here.
2271 - CONFIG_SYS_FLASH_BASE:
2272 Physical start address of Flash memory.
2274 - CONFIG_SYS_MONITOR_BASE:
2275 Physical start address of boot monitor code (set by
2276 make config files to be same as the text base address
2277 (CONFIG_SYS_TEXT_BASE) used when linking) - same as
2278 CONFIG_SYS_FLASH_BASE when booting from flash.
2280 - CONFIG_SYS_MONITOR_LEN:
2281 Size of memory reserved for monitor code, used to
2282 determine _at_compile_time_ (!) if the environment is
2283 embedded within the U-Boot image, or in a separate
2286 - CONFIG_SYS_MALLOC_LEN:
2287 Size of DRAM reserved for malloc() use.
2289 - CONFIG_SYS_MALLOC_F_LEN
2290 Size of the malloc() pool for use before relocation. If
2291 this is defined, then a very simple malloc() implementation
2292 will become available before relocation. The address is just
2293 below the global data, and the stack is moved down to make
2296 This feature allocates regions with increasing addresses
2297 within the region. calloc() is supported, but realloc()
2298 is not available. free() is supported but does nothing.
2299 The memory will be freed (or in fact just forgotten) when
2300 U-Boot relocates itself.
2302 - CONFIG_SYS_MALLOC_SIMPLE
2303 Provides a simple and small malloc() and calloc() for those
2304 boards which do not use the full malloc in SPL (which is
2305 enabled with CONFIG_SYS_SPL_MALLOC_START).
2307 - CONFIG_SYS_NONCACHED_MEMORY:
2308 Size of non-cached memory area. This area of memory will be
2309 typically located right below the malloc() area and mapped
2310 uncached in the MMU. This is useful for drivers that would
2311 otherwise require a lot of explicit cache maintenance. For
2312 some drivers it's also impossible to properly maintain the
2313 cache. For example if the regions that need to be flushed
2314 are not a multiple of the cache-line size, *and* padding
2315 cannot be allocated between the regions to align them (i.e.
2316 if the HW requires a contiguous array of regions, and the
2317 size of each region is not cache-aligned), then a flush of
2318 one region may result in overwriting data that hardware has
2319 written to another region in the same cache-line. This can
2320 happen for example in network drivers where descriptors for
2321 buffers are typically smaller than the CPU cache-line (e.g.
2322 16 bytes vs. 32 or 64 bytes).
2324 Non-cached memory is only supported on 32-bit ARM at present.
2326 - CONFIG_SYS_BOOTM_LEN:
2327 Normally compressed uImages are limited to an
2328 uncompressed size of 8 MBytes. If this is not enough,
2329 you can define CONFIG_SYS_BOOTM_LEN in your board config file
2330 to adjust this setting to your needs.
2332 - CONFIG_SYS_BOOTMAPSZ:
2333 Maximum size of memory mapped by the startup code of
2334 the Linux kernel; all data that must be processed by
2335 the Linux kernel (bd_info, boot arguments, FDT blob if
2336 used) must be put below this limit, unless "bootm_low"
2337 environment variable is defined and non-zero. In such case
2338 all data for the Linux kernel must be between "bootm_low"
2339 and "bootm_low" + CONFIG_SYS_BOOTMAPSZ. The environment
2340 variable "bootm_mapsize" will override the value of
2341 CONFIG_SYS_BOOTMAPSZ. If CONFIG_SYS_BOOTMAPSZ is undefined,
2342 then the value in "bootm_size" will be used instead.
2344 - CONFIG_SYS_BOOT_RAMDISK_HIGH:
2345 Enable initrd_high functionality. If defined then the
2346 initrd_high feature is enabled and the bootm ramdisk subcommand
2349 - CONFIG_SYS_BOOT_GET_CMDLINE:
2350 Enables allocating and saving kernel cmdline in space between
2351 "bootm_low" and "bootm_low" + BOOTMAPSZ.
2353 - CONFIG_SYS_BOOT_GET_KBD:
2354 Enables allocating and saving a kernel copy of the bd_info in
2355 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
2357 - CONFIG_SYS_MAX_FLASH_BANKS:
2358 Max number of Flash memory banks
2360 - CONFIG_SYS_MAX_FLASH_SECT:
2361 Max number of sectors on a Flash chip
2363 - CONFIG_SYS_FLASH_ERASE_TOUT:
2364 Timeout for Flash erase operations (in ms)
2366 - CONFIG_SYS_FLASH_WRITE_TOUT:
2367 Timeout for Flash write operations (in ms)
2369 - CONFIG_SYS_FLASH_LOCK_TOUT
2370 Timeout for Flash set sector lock bit operation (in ms)
2372 - CONFIG_SYS_FLASH_UNLOCK_TOUT
2373 Timeout for Flash clear lock bits operation (in ms)
2375 - CONFIG_SYS_FLASH_PROTECTION
2376 If defined, hardware flash sectors protection is used
2377 instead of U-Boot software protection.
2379 - CONFIG_SYS_DIRECT_FLASH_TFTP:
2381 Enable TFTP transfers directly to flash memory;
2382 without this option such a download has to be
2383 performed in two steps: (1) download to RAM, and (2)
2384 copy from RAM to flash.
2386 The two-step approach is usually more reliable, since
2387 you can check if the download worked before you erase
2388 the flash, but in some situations (when system RAM is
2389 too limited to allow for a temporary copy of the
2390 downloaded image) this option may be very useful.
2392 - CONFIG_SYS_FLASH_CFI:
2393 Define if the flash driver uses extra elements in the
2394 common flash structure for storing flash geometry.
2396 - CONFIG_FLASH_CFI_DRIVER
2397 This option also enables the building of the cfi_flash driver
2398 in the drivers directory
2400 - CONFIG_FLASH_CFI_MTD
2401 This option enables the building of the cfi_mtd driver
2402 in the drivers directory. The driver exports CFI flash
2405 - CONFIG_SYS_FLASH_USE_BUFFER_WRITE
2406 Use buffered writes to flash.
2408 - CONFIG_FLASH_SPANSION_S29WS_N
2409 s29ws-n MirrorBit flash has non-standard addresses for buffered
2412 - CONFIG_SYS_FLASH_QUIET_TEST
2413 If this option is defined, the common CFI flash doesn't
2414 print it's warning upon not recognized FLASH banks. This
2415 is useful, if some of the configured banks are only
2416 optionally available.
2418 - CONFIG_FLASH_SHOW_PROGRESS
2419 If defined (must be an integer), print out countdown
2420 digits and dots. Recommended value: 45 (9..1) for 80
2421 column displays, 15 (3..1) for 40 column displays.
2423 - CONFIG_FLASH_VERIFY
2424 If defined, the content of the flash (destination) is compared
2425 against the source after the write operation. An error message
2426 will be printed when the contents are not identical.
2427 Please note that this option is useless in nearly all cases,
2428 since such flash programming errors usually are detected earlier
2429 while unprotecting/erasing/programming. Please only enable
2430 this option if you really know what you are doing.
2432 - CONFIG_SYS_RX_ETH_BUFFER:
2433 Defines the number of Ethernet receive buffers. On some
2434 Ethernet controllers it is recommended to set this value
2435 to 8 or even higher (EEPRO100 or 405 EMAC), since all
2436 buffers can be full shortly after enabling the interface
2437 on high Ethernet traffic.
2438 Defaults to 4 if not defined.
2440 - CONFIG_ENV_MAX_ENTRIES
2442 Maximum number of entries in the hash table that is used
2443 internally to store the environment settings. The default
2444 setting is supposed to be generous and should work in most
2445 cases. This setting can be used to tune behaviour; see
2446 lib/hashtable.c for details.
2448 - CONFIG_ENV_FLAGS_LIST_DEFAULT
2449 - CONFIG_ENV_FLAGS_LIST_STATIC
2450 Enable validation of the values given to environment variables when
2451 calling env set. Variables can be restricted to only decimal,
2452 hexadecimal, or boolean. If CONFIG_CMD_NET is also defined,
2453 the variables can also be restricted to IP address or MAC address.
2455 The format of the list is:
2456 type_attribute = [s|d|x|b|i|m]
2457 access_attribute = [a|r|o|c]
2458 attributes = type_attribute[access_attribute]
2459 entry = variable_name[:attributes]
2462 The type attributes are:
2463 s - String (default)
2466 b - Boolean ([1yYtT|0nNfF])
2470 The access attributes are:
2476 - CONFIG_ENV_FLAGS_LIST_DEFAULT
2477 Define this to a list (string) to define the ".flags"
2478 environment variable in the default or embedded environment.
2480 - CONFIG_ENV_FLAGS_LIST_STATIC
2481 Define this to a list (string) to define validation that
2482 should be done if an entry is not found in the ".flags"
2483 environment variable. To override a setting in the static
2484 list, simply add an entry for the same variable name to the
2487 If CONFIG_REGEX is defined, the variable_name above is evaluated as a
2488 regular expression. This allows multiple variables to define the same
2489 flags without explicitly listing them for each variable.
2491 The following definitions that deal with the placement and management
2492 of environment data (variable area); in general, we support the
2493 following configurations:
2495 - CONFIG_BUILD_ENVCRC:
2497 Builds up envcrc with the target environment so that external utils
2498 may easily extract it and embed it in final U-Boot images.
2500 BE CAREFUL! The first access to the environment happens quite early
2501 in U-Boot initialization (when we try to get the setting of for the
2502 console baudrate). You *MUST* have mapped your NVRAM area then, or
2505 Please note that even with NVRAM we still use a copy of the
2506 environment in RAM: we could work on NVRAM directly, but we want to
2507 keep settings there always unmodified except somebody uses "saveenv"
2508 to save the current settings.
2510 BE CAREFUL! For some special cases, the local device can not use
2511 "saveenv" command. For example, the local device will get the
2512 environment stored in a remote NOR flash by SRIO or PCIE link,
2513 but it can not erase, write this NOR flash by SRIO or PCIE interface.
2515 - CONFIG_NAND_ENV_DST
2517 Defines address in RAM to which the nand_spl code should copy the
2518 environment. If redundant environment is used, it will be copied to
2519 CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE.
2521 Please note that the environment is read-only until the monitor
2522 has been relocated to RAM and a RAM copy of the environment has been
2523 created; also, when using EEPROM you will have to use env_get_f()
2524 until then to read environment variables.
2526 The environment is protected by a CRC32 checksum. Before the monitor
2527 is relocated into RAM, as a result of a bad CRC you will be working
2528 with the compiled-in default environment - *silently*!!! [This is
2529 necessary, because the first environment variable we need is the
2530 "baudrate" setting for the console - if we have a bad CRC, we don't
2531 have any device yet where we could complain.]
2533 Note: once the monitor has been relocated, then it will complain if
2534 the default environment is used; a new CRC is computed as soon as you
2535 use the "saveenv" command to store a valid environment.
2537 - CONFIG_SYS_FAULT_ECHO_LINK_DOWN:
2538 Echo the inverted Ethernet link state to the fault LED.
2540 Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR
2541 also needs to be defined.
2543 - CONFIG_SYS_FAULT_MII_ADDR:
2544 MII address of the PHY to check for the Ethernet link state.
2546 - CONFIG_NS16550_MIN_FUNCTIONS:
2547 Define this if you desire to only have use of the NS16550_init
2548 and NS16550_putc functions for the serial driver located at
2549 drivers/serial/ns16550.c. This option is useful for saving
2550 space for already greatly restricted images, including but not
2551 limited to NAND_SPL configurations.
2553 - CONFIG_DISPLAY_BOARDINFO
2554 Display information about the board that U-Boot is running on
2555 when U-Boot starts up. The board function checkboard() is called
2558 - CONFIG_DISPLAY_BOARDINFO_LATE
2559 Similar to the previous option, but display this information
2560 later, once stdio is running and output goes to the LCD, if
2563 - CONFIG_BOARD_SIZE_LIMIT:
2564 Maximum size of the U-Boot image. When defined, the
2565 build system checks that the actual size does not
2568 Low Level (hardware related) configuration options:
2569 ---------------------------------------------------
2571 - CONFIG_SYS_CACHELINE_SIZE:
2572 Cache Line Size of the CPU.
2574 - CONFIG_SYS_CCSRBAR_DEFAULT:
2575 Default (power-on reset) physical address of CCSR on Freescale
2578 - CONFIG_SYS_CCSRBAR:
2579 Virtual address of CCSR. On a 32-bit build, this is typically
2580 the same value as CONFIG_SYS_CCSRBAR_DEFAULT.
2582 - CONFIG_SYS_CCSRBAR_PHYS:
2583 Physical address of CCSR. CCSR can be relocated to a new
2584 physical address, if desired. In this case, this macro should
2585 be set to that address. Otherwise, it should be set to the
2586 same value as CONFIG_SYS_CCSRBAR_DEFAULT. For example, CCSR
2587 is typically relocated on 36-bit builds. It is recommended
2588 that this macro be defined via the _HIGH and _LOW macros:
2590 #define CONFIG_SYS_CCSRBAR_PHYS ((CONFIG_SYS_CCSRBAR_PHYS_HIGH
2591 * 1ull) << 32 | CONFIG_SYS_CCSRBAR_PHYS_LOW)
2593 - CONFIG_SYS_CCSRBAR_PHYS_HIGH:
2594 Bits 33-36 of CONFIG_SYS_CCSRBAR_PHYS. This value is typically
2595 either 0 (32-bit build) or 0xF (36-bit build). This macro is
2596 used in assembly code, so it must not contain typecasts or
2597 integer size suffixes (e.g. "ULL").
2599 - CONFIG_SYS_CCSRBAR_PHYS_LOW:
2600 Lower 32-bits of CONFIG_SYS_CCSRBAR_PHYS. This macro is
2601 used in assembly code, so it must not contain typecasts or
2602 integer size suffixes (e.g. "ULL").
2604 - CONFIG_SYS_CCSR_DO_NOT_RELOCATE:
2605 If this macro is defined, then CONFIG_SYS_CCSRBAR_PHYS will be
2606 forced to a value that ensures that CCSR is not relocated.
2609 Most IDE controllers were designed to be connected with PCI
2610 interface. Only few of them were designed for AHB interface.
2611 When software is doing ATA command and data transfer to
2612 IDE devices through IDE-AHB controller, some additional
2613 registers accessing to these kind of IDE-AHB controller
2616 - CONFIG_SYS_IMMR: Physical address of the Internal Memory.
2617 DO NOT CHANGE unless you know exactly what you're
2618 doing! (11-4) [MPC8xx systems only]
2620 - CONFIG_SYS_INIT_RAM_ADDR:
2622 Start address of memory area that can be used for
2623 initial data and stack; please note that this must be
2624 writable memory that is working WITHOUT special
2625 initialization, i. e. you CANNOT use normal RAM which
2626 will become available only after programming the
2627 memory controller and running certain initialization
2630 U-Boot uses the following memory types:
2631 - MPC8xx: IMMR (internal memory of the CPU)
2633 - CONFIG_SYS_GBL_DATA_OFFSET:
2635 Offset of the initial data structure in the memory
2636 area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually
2637 CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial
2638 data is located at the end of the available space
2639 (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE -
2640 GENERATED_GBL_DATA_SIZE), and the initial stack is just
2641 below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR +
2642 CONFIG_SYS_GBL_DATA_OFFSET) downward.
2645 On the MPC824X (or other systems that use the data
2646 cache for initial memory) the address chosen for
2647 CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must
2648 point to an otherwise UNUSED address space between
2649 the top of RAM and the start of the PCI space.
2651 - CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27)
2653 - CONFIG_SYS_OR_TIMING_SDRAM:
2656 - CONFIG_SYS_MAMR_PTA:
2657 periodic timer for refresh
2659 - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM,
2660 CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP,
2661 CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM,
2662 CONFIG_SYS_BR1_PRELIM:
2663 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
2665 - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
2666 CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM,
2667 CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM:
2668 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
2670 - CONFIG_PCI_INDIRECT_BRIDGE:
2671 Enable support for indirect PCI bridges.
2674 Chip has SRIO or not
2677 Board has SRIO 1 port available
2680 Board has SRIO 2 port available
2682 - CONFIG_SRIO_PCIE_BOOT_MASTER
2683 Board can support master function for Boot from SRIO and PCIE
2685 - CONFIG_SYS_SRIOn_MEM_VIRT:
2686 Virtual Address of SRIO port 'n' memory region
2688 - CONFIG_SYS_SRIOn_MEM_PHYxS:
2689 Physical Address of SRIO port 'n' memory region
2691 - CONFIG_SYS_SRIOn_MEM_SIZE:
2692 Size of SRIO port 'n' memory region
2694 - CONFIG_SYS_NAND_BUSWIDTH_16BIT
2695 Defined to tell the NAND controller that the NAND chip is using
2697 Not all NAND drivers use this symbol.
2698 Example of drivers that use it:
2699 - drivers/mtd/nand/raw/ndfc.c
2700 - drivers/mtd/nand/raw/mxc_nand.c
2702 - CONFIG_SYS_NDFC_EBC0_CFG
2703 Sets the EBC0_CFG register for the NDFC. If not defined
2704 a default value will be used.
2707 Get DDR timing information from an I2C EEPROM. Common
2708 with pluggable memory modules such as SODIMMs
2711 I2C address of the SPD EEPROM
2713 - CONFIG_SYS_SPD_BUS_NUM
2714 If SPD EEPROM is on an I2C bus other than the first
2715 one, specify here. Note that the value must resolve
2716 to something your driver can deal with.
2718 - CONFIG_SYS_DDR_RAW_TIMING
2719 Get DDR timing information from other than SPD. Common with
2720 soldered DDR chips onboard without SPD. DDR raw timing
2721 parameters are extracted from datasheet and hard-coded into
2722 header files or board specific files.
2724 - CONFIG_FSL_DDR_INTERACTIVE
2725 Enable interactive DDR debugging. See doc/README.fsl-ddr.
2727 - CONFIG_FSL_DDR_SYNC_REFRESH
2728 Enable sync of refresh for multiple controllers.
2730 - CONFIG_FSL_DDR_BIST
2731 Enable built-in memory test for Freescale DDR controllers.
2733 - CONFIG_SYS_83XX_DDR_USES_CS0
2734 Only for 83xx systems. If specified, then DDR should
2735 be configured using CS0 and CS1 instead of CS2 and CS3.
2738 Enable RMII mode for all FECs.
2739 Note that this is a global option, we can't
2740 have one FEC in standard MII mode and another in RMII mode.
2742 - CONFIG_CRC32_VERIFY
2743 Add a verify option to the crc32 command.
2746 => crc32 -v <address> <count> <crc32>
2748 Where address/count indicate a memory area
2749 and crc32 is the correct crc32 which the
2753 Add the "loopw" memory command. This only takes effect if
2754 the memory commands are activated globally (CONFIG_CMD_MEMORY).
2756 - CONFIG_CMD_MX_CYCLIC
2757 Add the "mdc" and "mwc" memory commands. These are cyclic
2762 This command will print 4 bytes (10,11,12,13) each 500 ms.
2764 => mwc.l 100 12345678 10
2765 This command will write 12345678 to address 100 all 10 ms.
2767 This only takes effect if the memory commands are activated
2768 globally (CONFIG_CMD_MEMORY).
2770 - CONFIG_SKIP_LOWLEVEL_INIT
2771 [ARM, NDS32, MIPS, RISC-V only] If this variable is defined, then certain
2772 low level initializations (like setting up the memory
2773 controller) are omitted and/or U-Boot does not
2774 relocate itself into RAM.
2776 Normally this variable MUST NOT be defined. The only
2777 exception is when U-Boot is loaded (to RAM) by some
2778 other boot loader or by a debugger which performs
2779 these initializations itself.
2781 - CONFIG_SKIP_LOWLEVEL_INIT_ONLY
2782 [ARM926EJ-S only] This allows just the call to lowlevel_init()
2783 to be skipped. The normal CP15 init (such as enabling the
2784 instruction cache) is still performed.
2787 Set when the currently-running compilation is for an artifact
2788 that will end up in the SPL (as opposed to the TPL or U-Boot
2789 proper). Code that needs stage-specific behavior should check
2793 Set when the currently-running compilation is for an artifact
2794 that will end up in the TPL (as opposed to the SPL or U-Boot
2795 proper). Code that needs stage-specific behavior should check
2798 - CONFIG_SYS_MPC85XX_NO_RESETVEC
2799 Only for 85xx systems. If this variable is specified, the section
2800 .resetvec is not kept and the section .bootpg is placed in the
2801 previous 4k of the .text section.
2803 - CONFIG_ARCH_MAP_SYSMEM
2804 Generally U-Boot (and in particular the md command) uses
2805 effective address. It is therefore not necessary to regard
2806 U-Boot address as virtual addresses that need to be translated
2807 to physical addresses. However, sandbox requires this, since
2808 it maintains its own little RAM buffer which contains all
2809 addressable memory. This option causes some memory accesses
2810 to be mapped through map_sysmem() / unmap_sysmem().
2812 - CONFIG_X86_RESET_VECTOR
2813 If defined, the x86 reset vector code is included. This is not
2814 needed when U-Boot is running from Coreboot.
2816 - CONFIG_SYS_NAND_NO_SUBPAGE_WRITE
2817 Option to disable subpage write in NAND driver
2818 driver that uses this:
2819 drivers/mtd/nand/raw/davinci_nand.c
2821 Freescale QE/FMAN Firmware Support:
2822 -----------------------------------
2824 The Freescale QUICCEngine (QE) and Frame Manager (FMAN) both support the
2825 loading of "firmware", which is encoded in the QE firmware binary format.
2826 This firmware often needs to be loaded during U-Boot booting, so macros
2827 are used to identify the storage device (NOR flash, SPI, etc) and the address
2830 - CONFIG_SYS_FMAN_FW_ADDR
2831 The address in the storage device where the FMAN microcode is located. The
2832 meaning of this address depends on which CONFIG_SYS_QE_FMAN_FW_IN_xxx macro
2835 - CONFIG_SYS_QE_FW_ADDR
2836 The address in the storage device where the QE microcode is located. The
2837 meaning of this address depends on which CONFIG_SYS_QE_FMAN_FW_IN_xxx macro
2840 - CONFIG_SYS_QE_FMAN_FW_LENGTH
2841 The maximum possible size of the firmware. The firmware binary format
2842 has a field that specifies the actual size of the firmware, but it
2843 might not be possible to read any part of the firmware unless some
2844 local storage is allocated to hold the entire firmware first.
2846 - CONFIG_SYS_QE_FMAN_FW_IN_NOR
2847 Specifies that QE/FMAN firmware is located in NOR flash, mapped as
2848 normal addressable memory via the LBC. CONFIG_SYS_FMAN_FW_ADDR is the
2849 virtual address in NOR flash.
2851 - CONFIG_SYS_QE_FMAN_FW_IN_NAND
2852 Specifies that QE/FMAN firmware is located in NAND flash.
2853 CONFIG_SYS_FMAN_FW_ADDR is the offset within NAND flash.
2855 - CONFIG_SYS_QE_FMAN_FW_IN_MMC
2856 Specifies that QE/FMAN firmware is located on the primary SD/MMC
2857 device. CONFIG_SYS_FMAN_FW_ADDR is the byte offset on that device.
2859 - CONFIG_SYS_QE_FMAN_FW_IN_REMOTE
2860 Specifies that QE/FMAN firmware is located in the remote (master)
2861 memory space. CONFIG_SYS_FMAN_FW_ADDR is a virtual address which
2862 can be mapped from slave TLB->slave LAW->slave SRIO or PCIE outbound
2863 window->master inbound window->master LAW->the ucode address in
2864 master's memory space.
2866 Freescale Layerscape Management Complex Firmware Support:
2867 ---------------------------------------------------------
2868 The Freescale Layerscape Management Complex (MC) supports the loading of
2870 This firmware often needs to be loaded during U-Boot booting, so macros
2871 are used to identify the storage device (NOR flash, SPI, etc) and the address
2874 - CONFIG_FSL_MC_ENET
2875 Enable the MC driver for Layerscape SoCs.
2877 Freescale Layerscape Debug Server Support:
2878 -------------------------------------------
2879 The Freescale Layerscape Debug Server Support supports the loading of
2880 "Debug Server firmware" and triggering SP boot-rom.
2881 This firmware often needs to be loaded during U-Boot booting.
2883 - CONFIG_SYS_MC_RSV_MEM_ALIGN
2884 Define alignment of reserved memory MC requires
2889 In order to achieve reproducible builds, timestamps used in the U-Boot build
2890 process have to be set to a fixed value.
2892 This is done using the SOURCE_DATE_EPOCH environment variable.
2893 SOURCE_DATE_EPOCH is to be set on the build host's shell, not as a configuration
2894 option for U-Boot or an environment variable in U-Boot.
2896 SOURCE_DATE_EPOCH should be set to a number of seconds since the epoch, in UTC.
2898 Building the Software:
2899 ======================
2901 Building U-Boot has been tested in several native build environments
2902 and in many different cross environments. Of course we cannot support
2903 all possibly existing versions of cross development tools in all
2904 (potentially obsolete) versions. In case of tool chain problems we
2905 recommend to use the ELDK (see https://www.denx.de/wiki/DULG/ELDK)
2906 which is extensively used to build and test U-Boot.
2908 If you are not using a native environment, it is assumed that you
2909 have GNU cross compiling tools available in your path. In this case,
2910 you must set the environment variable CROSS_COMPILE in your shell.
2911 Note that no changes to the Makefile or any other source files are
2912 necessary. For example using the ELDK on a 4xx CPU, please enter:
2914 $ CROSS_COMPILE=ppc_4xx-
2915 $ export CROSS_COMPILE
2917 U-Boot is intended to be simple to build. After installing the
2918 sources you must configure U-Boot for one specific board type. This
2923 where "NAME_defconfig" is the name of one of the existing configu-
2924 rations; see configs/*_defconfig for supported names.
2926 Note: for some boards special configuration names may exist; check if
2927 additional information is available from the board vendor; for
2928 instance, the TQM823L systems are available without (standard)
2929 or with LCD support. You can select such additional "features"
2930 when choosing the configuration, i. e.
2932 make TQM823L_defconfig
2933 - will configure for a plain TQM823L, i. e. no LCD support
2935 make TQM823L_LCD_defconfig
2936 - will configure for a TQM823L with U-Boot console on LCD
2941 Finally, type "make all", and you should get some working U-Boot
2942 images ready for download to / installation on your system:
2944 - "u-boot.bin" is a raw binary image
2945 - "u-boot" is an image in ELF binary format
2946 - "u-boot.srec" is in Motorola S-Record format
2948 By default the build is performed locally and the objects are saved
2949 in the source directory. One of the two methods can be used to change
2950 this behavior and build U-Boot to some external directory:
2952 1. Add O= to the make command line invocations:
2954 make O=/tmp/build distclean
2955 make O=/tmp/build NAME_defconfig
2956 make O=/tmp/build all
2958 2. Set environment variable KBUILD_OUTPUT to point to the desired location:
2960 export KBUILD_OUTPUT=/tmp/build
2965 Note that the command line "O=" setting overrides the KBUILD_OUTPUT environment
2968 User specific CPPFLAGS, AFLAGS and CFLAGS can be passed to the compiler by
2969 setting the according environment variables KCPPFLAGS, KAFLAGS and KCFLAGS.
2970 For example to treat all compiler warnings as errors:
2972 make KCFLAGS=-Werror
2974 Please be aware that the Makefiles assume you are using GNU make, so
2975 for instance on NetBSD you might need to use "gmake" instead of
2979 If the system board that you have is not listed, then you will need
2980 to port U-Boot to your hardware platform. To do this, follow these
2983 1. Create a new directory to hold your board specific code. Add any
2984 files you need. In your board directory, you will need at least
2985 the "Makefile" and a "<board>.c".
2986 2. Create a new configuration file "include/configs/<board>.h" for
2988 3. If you're porting U-Boot to a new CPU, then also create a new
2989 directory to hold your CPU specific code. Add any files you need.
2990 4. Run "make <board>_defconfig" with your new name.
2991 5. Type "make", and you should get a working "u-boot.srec" file
2992 to be installed on your target system.
2993 6. Debug and solve any problems that might arise.
2994 [Of course, this last step is much harder than it sounds.]
2997 Testing of U-Boot Modifications, Ports to New Hardware, etc.:
2998 ==============================================================
3000 If you have modified U-Boot sources (for instance added a new board
3001 or support for new devices, a new CPU, etc.) you are expected to
3002 provide feedback to the other developers. The feedback normally takes
3003 the form of a "patch", i.e. a context diff against a certain (latest
3004 official or latest in the git repository) version of U-Boot sources.
3006 But before you submit such a patch, please verify that your modifi-
3007 cation did not break existing code. At least make sure that *ALL* of
3008 the supported boards compile WITHOUT ANY compiler warnings. To do so,
3009 just run the buildman script (tools/buildman/buildman), which will
3010 configure and build U-Boot for ALL supported system. Be warned, this
3011 will take a while. Please see the buildman README, or run 'buildman -H'
3015 See also "U-Boot Porting Guide" below.
3018 Monitor Commands - Overview:
3019 ============================
3021 go - start application at address 'addr'
3022 run - run commands in an environment variable
3023 bootm - boot application image from memory
3024 bootp - boot image via network using BootP/TFTP protocol
3025 bootz - boot zImage from memory
3026 tftpboot- boot image via network using TFTP protocol
3027 and env variables "ipaddr" and "serverip"
3028 (and eventually "gatewayip")
3029 tftpput - upload a file via network using TFTP protocol
3030 rarpboot- boot image via network using RARP/TFTP protocol
3031 diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
3032 loads - load S-Record file over serial line
3033 loadb - load binary file over serial line (kermit mode)
3035 mm - memory modify (auto-incrementing)
3036 nm - memory modify (constant address)
3037 mw - memory write (fill)
3040 cmp - memory compare
3041 crc32 - checksum calculation
3042 i2c - I2C sub-system
3043 sspi - SPI utility commands
3044 base - print or set address offset
3045 printenv- print environment variables
3046 pwm - control pwm channels
3047 setenv - set environment variables
3048 saveenv - save environment variables to persistent storage
3049 protect - enable or disable FLASH write protection
3050 erase - erase FLASH memory
3051 flinfo - print FLASH memory information
3052 nand - NAND memory operations (see doc/README.nand)
3053 bdinfo - print Board Info structure
3054 iminfo - print header information for application image
3055 coninfo - print console devices and informations
3056 ide - IDE sub-system
3057 loop - infinite loop on address range
3058 loopw - infinite write loop on address range
3059 mtest - simple RAM test
3060 icache - enable or disable instruction cache
3061 dcache - enable or disable data cache
3062 reset - Perform RESET of the CPU
3063 echo - echo args to console
3064 version - print monitor version
3065 help - print online help
3066 ? - alias for 'help'
3069 Monitor Commands - Detailed Description:
3070 ========================================
3074 For now: just type "help <command>".
3077 Environment Variables:
3078 ======================
3080 U-Boot supports user configuration using Environment Variables which
3081 can be made persistent by saving to Flash memory.
3083 Environment Variables are set using "setenv", printed using
3084 "printenv", and saved to Flash using "saveenv". Using "setenv"
3085 without a value can be used to delete a variable from the
3086 environment. As long as you don't save the environment you are
3087 working with an in-memory copy. In case the Flash area containing the
3088 environment is erased by accident, a default environment is provided.
3090 Some configuration options can be set using Environment Variables.
3092 List of environment variables (most likely not complete):
3094 baudrate - see CONFIG_BAUDRATE
3096 bootdelay - see CONFIG_BOOTDELAY
3098 bootcmd - see CONFIG_BOOTCOMMAND
3100 bootargs - Boot arguments when booting an RTOS image
3102 bootfile - Name of the image to load with TFTP
3104 bootm_low - Memory range available for image processing in the bootm
3105 command can be restricted. This variable is given as
3106 a hexadecimal number and defines lowest address allowed
3107 for use by the bootm command. See also "bootm_size"
3108 environment variable. Address defined by "bootm_low" is
3109 also the base of the initial memory mapping for the Linux
3110 kernel -- see the description of CONFIG_SYS_BOOTMAPSZ and
3113 bootm_mapsize - Size of the initial memory mapping for the Linux kernel.
3114 This variable is given as a hexadecimal number and it
3115 defines the size of the memory region starting at base
3116 address bootm_low that is accessible by the Linux kernel
3117 during early boot. If unset, CONFIG_SYS_BOOTMAPSZ is used
3118 as the default value if it is defined, and bootm_size is
3121 bootm_size - Memory range available for image processing in the bootm
3122 command can be restricted. This variable is given as
3123 a hexadecimal number and defines the size of the region
3124 allowed for use by the bootm command. See also "bootm_low"
3125 environment variable.
3127 bootstopkeysha256, bootdelaykey, bootstopkey - See README.autoboot
3129 updatefile - Location of the software update file on a TFTP server, used
3130 by the automatic software update feature. Please refer to
3131 documentation in doc/README.update for more details.
3133 autoload - if set to "no" (any string beginning with 'n'),
3134 "bootp" will just load perform a lookup of the
3135 configuration from the BOOTP server, but not try to
3136 load any image using TFTP
3138 autostart - if set to "yes", an image loaded using the "bootp",
3139 "rarpboot", "tftpboot" or "diskboot" commands will
3140 be automatically started (by internally calling
3143 If set to "no", a standalone image passed to the
3144 "bootm" command will be copied to the load address
3145 (and eventually uncompressed), but NOT be started.
3146 This can be used to load and uncompress arbitrary
3149 fdt_high - if set this restricts the maximum address that the
3150 flattened device tree will be copied into upon boot.
3151 For example, if you have a system with 1 GB memory
3152 at physical address 0x10000000, while Linux kernel
3153 only recognizes the first 704 MB as low memory, you
3154 may need to set fdt_high as 0x3C000000 to have the
3155 device tree blob be copied to the maximum address
3156 of the 704 MB low memory, so that Linux kernel can
3157 access it during the boot procedure.
3159 If this is set to the special value 0xFFFFFFFF then
3160 the fdt will not be copied at all on boot. For this
3161 to work it must reside in writable memory, have
3162 sufficient padding on the end of it for u-boot to
3163 add the information it needs into it, and the memory
3164 must be accessible by the kernel.
3166 fdtcontroladdr- if set this is the address of the control flattened
3167 device tree used by U-Boot when CONFIG_OF_CONTROL is
3170 i2cfast - (PPC405GP|PPC405EP only)
3171 if set to 'y' configures Linux I2C driver for fast
3172 mode (400kHZ). This environment variable is used in
3173 initialization code. So, for changes to be effective
3174 it must be saved and board must be reset.
3176 initrd_high - restrict positioning of initrd images:
3177 If this variable is not set, initrd images will be
3178 copied to the highest possible address in RAM; this
3179 is usually what you want since it allows for
3180 maximum initrd size. If for some reason you want to
3181 make sure that the initrd image is loaded below the
3182 CONFIG_SYS_BOOTMAPSZ limit, you can set this environment
3183 variable to a value of "no" or "off" or "0".
3184 Alternatively, you can set it to a maximum upper
3185 address to use (U-Boot will still check that it
3186 does not overwrite the U-Boot stack and data).
3188 For instance, when you have a system with 16 MB
3189 RAM, and want to reserve 4 MB from use by Linux,
3190 you can do this by adding "mem=12M" to the value of
3191 the "bootargs" variable. However, now you must make
3192 sure that the initrd image is placed in the first
3193 12 MB as well - this can be done with
3195 setenv initrd_high 00c00000
3197 If you set initrd_high to 0xFFFFFFFF, this is an
3198 indication to U-Boot that all addresses are legal
3199 for the Linux kernel, including addresses in flash
3200 memory. In this case U-Boot will NOT COPY the
3201 ramdisk at all. This may be useful to reduce the
3202 boot time on your system, but requires that this
3203 feature is supported by your Linux kernel.
3205 ipaddr - IP address; needed for tftpboot command
3207 loadaddr - Default load address for commands like "bootp",
3208 "rarpboot", "tftpboot", "loadb" or "diskboot"
3210 loads_echo - see CONFIG_LOADS_ECHO
3212 serverip - TFTP server IP address; needed for tftpboot command
3214 bootretry - see CONFIG_BOOT_RETRY_TIME
3216 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
3218 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
3220 ethprime - controls which interface is used first.
3222 ethact - controls which interface is currently active.
3223 For example you can do the following
3225 => setenv ethact FEC
3226 => ping 192.168.0.1 # traffic sent on FEC
3227 => setenv ethact SCC
3228 => ping 10.0.0.1 # traffic sent on SCC
3230 ethrotate - When set to "no" U-Boot does not go through all
3231 available network interfaces.
3232 It just stays at the currently selected interface.
3234 netretry - When set to "no" each network operation will
3235 either succeed or fail without retrying.
3236 When set to "once" the network operation will
3237 fail when all the available network interfaces
3238 are tried once without success.
3239 Useful on scripts which control the retry operation
3242 npe_ucode - set load address for the NPE microcode
3244 silent_linux - If set then Linux will be told to boot silently, by
3245 changing the console to be empty. If "yes" it will be
3246 made silent. If "no" it will not be made silent. If
3247 unset, then it will be made silent if the U-Boot console
3250 tftpsrcp - If this is set, the value is used for TFTP's
3253 tftpdstp - If this is set, the value is used for TFTP's UDP
3254 destination port instead of the Well Know Port 69.
3256 tftpblocksize - Block size to use for TFTP transfers; if not set,
3257 we use the TFTP server's default block size
3259 tftptimeout - Retransmission timeout for TFTP packets (in milli-
3260 seconds, minimum value is 1000 = 1 second). Defines
3261 when a packet is considered to be lost so it has to
3262 be retransmitted. The default is 5000 = 5 seconds.
3263 Lowering this value may make downloads succeed
3264 faster in networks with high packet loss rates or
3265 with unreliable TFTP servers.
3267 tftptimeoutcountmax - maximum count of TFTP timeouts (no
3268 unit, minimum value = 0). Defines how many timeouts
3269 can happen during a single file transfer before that
3270 transfer is aborted. The default is 10, and 0 means
3271 'no timeouts allowed'. Increasing this value may help
3272 downloads succeed with high packet loss rates, or with
3273 unreliable TFTP servers or client hardware.
3275 tftpwindowsize - if this is set, the value is used for TFTP's
3276 window size as described by RFC 7440.
3277 This means the count of blocks we can receive before
3278 sending ack to server.
3280 vlan - When set to a value < 4095 the traffic over
3281 Ethernet is encapsulated/received over 802.1q
3284 bootpretryperiod - Period during which BOOTP/DHCP sends retries.
3285 Unsigned value, in milliseconds. If not set, the period will
3286 be either the default (28000), or a value based on
3287 CONFIG_NET_RETRY_COUNT, if defined. This value has
3288 precedence over the valu based on CONFIG_NET_RETRY_COUNT.
3290 memmatches - Number of matches found by the last 'ms' command, in hex
3292 memaddr - Address of the last match found by the 'ms' command, in hex,
3295 mempos - Index position of the last match found by the 'ms' command,
3296 in units of the size (.b, .w, .l) of the search
3298 zbootbase - (x86 only) Base address of the bzImage 'setup' block
3300 zbootaddr - (x86 only) Address of the loaded bzImage, typically
3301 BZIMAGE_LOAD_ADDR which is 0x100000
3303 The following image location variables contain the location of images
3304 used in booting. The "Image" column gives the role of the image and is
3305 not an environment variable name. The other columns are environment
3306 variable names. "File Name" gives the name of the file on a TFTP
3307 server, "RAM Address" gives the location in RAM the image will be
3308 loaded to, and "Flash Location" gives the image's address in NOR
3309 flash or offset in NAND flash.
3311 *Note* - these variables don't have to be defined for all boards, some
3312 boards currently use other variables for these purposes, and some
3313 boards use these variables for other purposes.
3315 Image File Name RAM Address Flash Location
3316 ----- --------- ----------- --------------
3317 u-boot u-boot u-boot_addr_r u-boot_addr
3318 Linux kernel bootfile kernel_addr_r kernel_addr
3319 device tree blob fdtfile fdt_addr_r fdt_addr
3320 ramdisk ramdiskfile ramdisk_addr_r ramdisk_addr
3322 The following environment variables may be used and automatically
3323 updated by the network boot commands ("bootp" and "rarpboot"),
3324 depending the information provided by your boot server:
3326 bootfile - see above
3327 dnsip - IP address of your Domain Name Server
3328 dnsip2 - IP address of your secondary Domain Name Server
3329 gatewayip - IP address of the Gateway (Router) to use
3330 hostname - Target hostname
3332 netmask - Subnet Mask
3333 rootpath - Pathname of the root filesystem on the NFS server
3334 serverip - see above
3337 There are two special Environment Variables:
3339 serial# - contains hardware identification information such
3340 as type string and/or serial number
3341 ethaddr - Ethernet address
3343 These variables can be set only once (usually during manufacturing of
3344 the board). U-Boot refuses to delete or overwrite these variables
3345 once they have been set once.
3348 Further special Environment Variables:
3350 ver - Contains the U-Boot version string as printed
3351 with the "version" command. This variable is
3352 readonly (see CONFIG_VERSION_VARIABLE).
3355 Please note that changes to some configuration parameters may take
3356 only effect after the next boot (yes, that's just like Windoze :-).
3359 Callback functions for environment variables:
3360 ---------------------------------------------
3362 For some environment variables, the behavior of u-boot needs to change
3363 when their values are changed. This functionality allows functions to
3364 be associated with arbitrary variables. On creation, overwrite, or
3365 deletion, the callback will provide the opportunity for some side
3366 effect to happen or for the change to be rejected.
3368 The callbacks are named and associated with a function using the
3369 U_BOOT_ENV_CALLBACK macro in your board or driver code.
3371 These callbacks are associated with variables in one of two ways. The
3372 static list can be added to by defining CONFIG_ENV_CALLBACK_LIST_STATIC
3373 in the board configuration to a string that defines a list of
3374 associations. The list must be in the following format:
3376 entry = variable_name[:callback_name]
3379 If the callback name is not specified, then the callback is deleted.
3380 Spaces are also allowed anywhere in the list.
3382 Callbacks can also be associated by defining the ".callbacks" variable
3383 with the same list format above. Any association in ".callbacks" will
3384 override any association in the static list. You can define
3385 CONFIG_ENV_CALLBACK_LIST_DEFAULT to a list (string) to define the
3386 ".callbacks" environment variable in the default or embedded environment.
3388 If CONFIG_REGEX is defined, the variable_name above is evaluated as a
3389 regular expression. This allows multiple variables to be connected to
3390 the same callback without explicitly listing them all out.
3392 The signature of the callback functions is:
3394 int callback(const char *name, const char *value, enum env_op op, int flags)
3396 * name - changed environment variable
3397 * value - new value of the environment variable
3398 * op - operation (create, overwrite, or delete)
3399 * flags - attributes of the environment variable change, see flags H_* in
3402 The return value is 0 if the variable change is accepted and 1 otherwise.
3405 Note for Redundant Ethernet Interfaces:
3406 =======================================
3408 Some boards come with redundant Ethernet interfaces; U-Boot supports
3409 such configurations and is capable of automatic selection of a
3410 "working" interface when needed. MAC assignment works as follows:
3412 Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
3413 MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
3414 "eth1addr" (=>eth1), "eth2addr", ...
3416 If the network interface stores some valid MAC address (for instance
3417 in SROM), this is used as default address if there is NO correspon-
3418 ding setting in the environment; if the corresponding environment
3419 variable is set, this overrides the settings in the card; that means:
3421 o If the SROM has a valid MAC address, and there is no address in the
3422 environment, the SROM's address is used.
3424 o If there is no valid address in the SROM, and a definition in the
3425 environment exists, then the value from the environment variable is
3428 o If both the SROM and the environment contain a MAC address, and
3429 both addresses are the same, this MAC address is used.
3431 o If both the SROM and the environment contain a MAC address, and the
3432 addresses differ, the value from the environment is used and a
3435 o If neither SROM nor the environment contain a MAC address, an error
3436 is raised. If CONFIG_NET_RANDOM_ETHADDR is defined, then in this case
3437 a random, locally-assigned MAC is used.
3439 If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses
3440 will be programmed into hardware as part of the initialization process. This
3441 may be skipped by setting the appropriate 'ethmacskip' environment variable.
3442 The naming convention is as follows:
3443 "ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc.
3448 U-Boot is capable of booting (and performing other auxiliary operations on)
3449 images in two formats:
3451 New uImage format (FIT)
3452 -----------------------
3454 Flexible and powerful format based on Flattened Image Tree -- FIT (similar
3455 to Flattened Device Tree). It allows the use of images with multiple
3456 components (several kernels, ramdisks, etc.), with contents protected by
3457 SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory.
3463 Old image format is based on binary files which can be basically anything,
3464 preceded by a special header; see the definitions in include/image.h for
3465 details; basically, the header defines the following image properties:
3467 * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
3468 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
3469 LynxOS, pSOS, QNX, RTEMS, INTEGRITY;
3470 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS,
3472 * Target CPU Architecture (Provisions for Alpha, ARM, Intel x86,
3473 IA64, MIPS, NDS32, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
3474 Currently supported: ARM, Intel x86, MIPS, NDS32, Nios II, PowerPC).
3475 * Compression Type (uncompressed, gzip, bzip2)
3481 The header is marked by a special Magic Number, and both the header
3482 and the data portions of the image are secured against corruption by
3489 Although U-Boot should support any OS or standalone application
3490 easily, the main focus has always been on Linux during the design of
3493 U-Boot includes many features that so far have been part of some
3494 special "boot loader" code within the Linux kernel. Also, any
3495 "initrd" images to be used are no longer part of one big Linux image;
3496 instead, kernel and "initrd" are separate images. This implementation
3497 serves several purposes:
3499 - the same features can be used for other OS or standalone
3500 applications (for instance: using compressed images to reduce the
3501 Flash memory footprint)
3503 - it becomes much easier to port new Linux kernel versions because
3504 lots of low-level, hardware dependent stuff are done by U-Boot
3506 - the same Linux kernel image can now be used with different "initrd"
3507 images; of course this also means that different kernel images can
3508 be run with the same "initrd". This makes testing easier (you don't
3509 have to build a new "zImage.initrd" Linux image when you just
3510 change a file in your "initrd"). Also, a field-upgrade of the
3511 software is easier now.
3517 Porting Linux to U-Boot based systems:
3518 ---------------------------------------
3520 U-Boot cannot save you from doing all the necessary modifications to
3521 configure the Linux device drivers for use with your target hardware
3522 (no, we don't intend to provide a full virtual machine interface to
3525 But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot).
3527 Just make sure your machine specific header file (for instance
3528 include/asm-ppc/tqm8xx.h) includes the same definition of the Board
3529 Information structure as we define in include/asm-<arch>/u-boot.h,
3530 and make sure that your definition of IMAP_ADDR uses the same value
3531 as your U-Boot configuration in CONFIG_SYS_IMMR.
3533 Note that U-Boot now has a driver model, a unified model for drivers.
3534 If you are adding a new driver, plumb it into driver model. If there
3535 is no uclass available, you are encouraged to create one. See
3539 Configuring the Linux kernel:
3540 -----------------------------
3542 No specific requirements for U-Boot. Make sure you have some root
3543 device (initial ramdisk, NFS) for your target system.
3546 Building a Linux Image:
3547 -----------------------
3549 With U-Boot, "normal" build targets like "zImage" or "bzImage" are
3550 not used. If you use recent kernel source, a new build target
3551 "uImage" will exist which automatically builds an image usable by
3552 U-Boot. Most older kernels also have support for a "pImage" target,
3553 which was introduced for our predecessor project PPCBoot and uses a
3554 100% compatible format.
3558 make TQM850L_defconfig
3563 The "uImage" build target uses a special tool (in 'tools/mkimage') to
3564 encapsulate a compressed Linux kernel image with header information,
3565 CRC32 checksum etc. for use with U-Boot. This is what we are doing:
3567 * build a standard "vmlinux" kernel image (in ELF binary format):
3569 * convert the kernel into a raw binary image:
3571 ${CROSS_COMPILE}-objcopy -O binary \
3572 -R .note -R .comment \
3573 -S vmlinux linux.bin
3575 * compress the binary image:
3579 * package compressed binary image for U-Boot:
3581 mkimage -A ppc -O linux -T kernel -C gzip \
3582 -a 0 -e 0 -n "Linux Kernel Image" \
3583 -d linux.bin.gz uImage
3586 The "mkimage" tool can also be used to create ramdisk images for use
3587 with U-Boot, either separated from the Linux kernel image, or
3588 combined into one file. "mkimage" encapsulates the images with a 64
3589 byte header containing information about target architecture,
3590 operating system, image type, compression method, entry points, time
3591 stamp, CRC32 checksums, etc.
3593 "mkimage" can be called in two ways: to verify existing images and
3594 print the header information, or to build new images.
3596 In the first form (with "-l" option) mkimage lists the information
3597 contained in the header of an existing U-Boot image; this includes
3598 checksum verification:
3600 tools/mkimage -l image
3601 -l ==> list image header information
3603 The second form (with "-d" option) is used to build a U-Boot image
3604 from a "data file" which is used as image payload:
3606 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
3607 -n name -d data_file image
3608 -A ==> set architecture to 'arch'
3609 -O ==> set operating system to 'os'
3610 -T ==> set image type to 'type'
3611 -C ==> set compression type 'comp'
3612 -a ==> set load address to 'addr' (hex)
3613 -e ==> set entry point to 'ep' (hex)
3614 -n ==> set image name to 'name'
3615 -d ==> use image data from 'datafile'
3617 Right now, all Linux kernels for PowerPC systems use the same load
3618 address (0x00000000), but the entry point address depends on the
3621 - 2.2.x kernels have the entry point at 0x0000000C,
3622 - 2.3.x and later kernels have the entry point at 0x00000000.
3624 So a typical call to build a U-Boot image would read:
3626 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
3627 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
3628 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \
3629 > examples/uImage.TQM850L
3630 Image Name: 2.4.4 kernel for TQM850L
3631 Created: Wed Jul 19 02:34:59 2000
3632 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3633 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
3634 Load Address: 0x00000000
3635 Entry Point: 0x00000000
3637 To verify the contents of the image (or check for corruption):
3639 -> tools/mkimage -l examples/uImage.TQM850L
3640 Image Name: 2.4.4 kernel for TQM850L
3641 Created: Wed Jul 19 02:34:59 2000
3642 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3643 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
3644 Load Address: 0x00000000
3645 Entry Point: 0x00000000
3647 NOTE: for embedded systems where boot time is critical you can trade
3648 speed for memory and install an UNCOMPRESSED image instead: this
3649 needs more space in Flash, but boots much faster since it does not
3650 need to be uncompressed:
3652 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz
3653 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
3654 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
3655 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \
3656 > examples/uImage.TQM850L-uncompressed
3657 Image Name: 2.4.4 kernel for TQM850L
3658 Created: Wed Jul 19 02:34:59 2000
3659 Image Type: PowerPC Linux Kernel Image (uncompressed)
3660 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
3661 Load Address: 0x00000000
3662 Entry Point: 0x00000000
3665 Similar you can build U-Boot images from a 'ramdisk.image.gz' file
3666 when your kernel is intended to use an initial ramdisk:
3668 -> tools/mkimage -n 'Simple Ramdisk Image' \
3669 > -A ppc -O linux -T ramdisk -C gzip \
3670 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
3671 Image Name: Simple Ramdisk Image
3672 Created: Wed Jan 12 14:01:50 2000
3673 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3674 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
3675 Load Address: 0x00000000
3676 Entry Point: 0x00000000
3678 The "dumpimage" tool can be used to disassemble or list the contents of images
3679 built by mkimage. See dumpimage's help output (-h) for details.
3681 Installing a Linux Image:
3682 -------------------------
3684 To downloading a U-Boot image over the serial (console) interface,
3685 you must convert the image to S-Record format:
3687 objcopy -I binary -O srec examples/image examples/image.srec
3689 The 'objcopy' does not understand the information in the U-Boot
3690 image header, so the resulting S-Record file will be relative to
3691 address 0x00000000. To load it to a given address, you need to
3692 specify the target address as 'offset' parameter with the 'loads'
3695 Example: install the image to address 0x40100000 (which on the
3696 TQM8xxL is in the first Flash bank):
3698 => erase 40100000 401FFFFF
3704 ## Ready for S-Record download ...
3705 ~>examples/image.srec
3706 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
3708 15989 15990 15991 15992
3709 [file transfer complete]
3711 ## Start Addr = 0x00000000
3714 You can check the success of the download using the 'iminfo' command;
3715 this includes a checksum verification so you can be sure no data
3716 corruption happened:
3720 ## Checking Image at 40100000 ...
3721 Image Name: 2.2.13 for initrd on TQM850L
3722 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3723 Data Size: 335725 Bytes = 327 kB = 0 MB
3724 Load Address: 00000000
3725 Entry Point: 0000000c
3726 Verifying Checksum ... OK
3732 The "bootm" command is used to boot an application that is stored in
3733 memory (RAM or Flash). In case of a Linux kernel image, the contents
3734 of the "bootargs" environment variable is passed to the kernel as
3735 parameters. You can check and modify this variable using the
3736 "printenv" and "setenv" commands:
3739 => printenv bootargs
3740 bootargs=root=/dev/ram
3742 => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3744 => printenv bootargs
3745 bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3748 ## Booting Linux kernel at 40020000 ...
3749 Image Name: 2.2.13 for NFS on TQM850L
3750 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3751 Data Size: 381681 Bytes = 372 kB = 0 MB
3752 Load Address: 00000000
3753 Entry Point: 0000000c
3754 Verifying Checksum ... OK
3755 Uncompressing Kernel Image ... OK
3756 Linux version 2.2.13 (
[email protected]) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:35:17 MEST 2000
3757 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3758 time_init: decrementer frequency = 187500000/60
3759 Calibrating delay loop... 49.77 BogoMIPS
3760 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
3763 If you want to boot a Linux kernel with initial RAM disk, you pass
3764 the memory addresses of both the kernel and the initrd image (PPBCOOT
3765 format!) to the "bootm" command:
3767 => imi 40100000 40200000
3769 ## Checking Image at 40100000 ...
3770 Image Name: 2.2.13 for initrd on TQM850L
3771 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3772 Data Size: 335725 Bytes = 327 kB = 0 MB
3773 Load Address: 00000000
3774 Entry Point: 0000000c
3775 Verifying Checksum ... OK
3777 ## Checking Image at 40200000 ...
3778 Image Name: Simple Ramdisk Image
3779 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3780 Data Size: 566530 Bytes = 553 kB = 0 MB
3781 Load Address: 00000000
3782 Entry Point: 00000000
3783 Verifying Checksum ... OK
3785 => bootm 40100000 40200000
3786 ## Booting Linux kernel at 40100000 ...
3787 Image Name: 2.2.13 for initrd on TQM850L
3788 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3789 Data Size: 335725 Bytes = 327 kB = 0 MB
3790 Load Address: 00000000
3791 Entry Point: 0000000c
3792 Verifying Checksum ... OK
3793 Uncompressing Kernel Image ... OK
3794 ## Loading RAMDisk Image at 40200000 ...
3795 Image Name: Simple Ramdisk Image
3796 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3797 Data Size: 566530 Bytes = 553 kB = 0 MB
3798 Load Address: 00000000
3799 Entry Point: 00000000
3800 Verifying Checksum ... OK
3801 Loading Ramdisk ... OK
3802 Linux version 2.2.13 (
[email protected]) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:32:08 MEST 2000
3803 Boot arguments: root=/dev/ram
3804 time_init: decrementer frequency = 187500000/60
3805 Calibrating delay loop... 49.77 BogoMIPS
3807 RAMDISK: Compressed image found at block 0
3808 VFS: Mounted root (ext2 filesystem).
3812 Boot Linux and pass a flat device tree:
3815 First, U-Boot must be compiled with the appropriate defines. See the section
3816 titled "Linux Kernel Interface" above for a more in depth explanation. The
3817 following is an example of how to start a kernel and pass an updated
3823 oft=oftrees/mpc8540ads.dtb
3824 => tftp $oftaddr $oft
3825 Speed: 1000, full duplex
3827 TFTP from server 192.168.1.1; our IP address is 192.168.1.101
3828 Filename 'oftrees/mpc8540ads.dtb'.
3829 Load address: 0x300000
3832 Bytes transferred = 4106 (100a hex)
3833 => tftp $loadaddr $bootfile
3834 Speed: 1000, full duplex
3836 TFTP from server 192.168.1.1; our IP address is 192.168.1.2
3838 Load address: 0x200000
3839 Loading:############
3841 Bytes transferred = 1029407 (fb51f hex)
3846 => bootm $loadaddr - $oftaddr
3847 ## Booting image at 00200000 ...
3848 Image Name: Linux-2.6.17-dirty
3849 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3850 Data Size: 1029343 Bytes = 1005.2 kB
3851 Load Address: 00000000
3852 Entry Point: 00000000
3853 Verifying Checksum ... OK
3854 Uncompressing Kernel Image ... OK
3855 Booting using flat device tree at 0x300000
3856 Using MPC85xx ADS machine description
3857 Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
3861 More About U-Boot Image Types:
3862 ------------------------------
3864 U-Boot supports the following image types:
3866 "Standalone Programs" are directly runnable in the environment
3867 provided by U-Boot; it is expected that (if they behave
3868 well) you can continue to work in U-Boot after return from
3869 the Standalone Program.
3870 "OS Kernel Images" are usually images of some Embedded OS which
3871 will take over control completely. Usually these programs
3872 will install their own set of exception handlers, device
3873 drivers, set up the MMU, etc. - this means, that you cannot
3874 expect to re-enter U-Boot except by resetting the CPU.
3875 "RAMDisk Images" are more or less just data blocks, and their
3876 parameters (address, size) are passed to an OS kernel that is
3878 "Multi-File Images" contain several images, typically an OS
3879 (Linux) kernel image and one or more data images like
3880 RAMDisks. This construct is useful for instance when you want
3881 to boot over the network using BOOTP etc., where the boot
3882 server provides just a single image file, but you want to get
3883 for instance an OS kernel and a RAMDisk image.
3885 "Multi-File Images" start with a list of image sizes, each
3886 image size (in bytes) specified by an "uint32_t" in network
3887 byte order. This list is terminated by an "(uint32_t)0".
3888 Immediately after the terminating 0 follow the images, one by
3889 one, all aligned on "uint32_t" boundaries (size rounded up to
3890 a multiple of 4 bytes).
3892 "Firmware Images" are binary images containing firmware (like
3893 U-Boot or FPGA images) which usually will be programmed to
3896 "Script files" are command sequences that will be executed by
3897 U-Boot's command interpreter; this feature is especially
3898 useful when you configure U-Boot to use a real shell (hush)
3899 as command interpreter.
3901 Booting the Linux zImage:
3902 -------------------------
3904 On some platforms, it's possible to boot Linux zImage. This is done
3905 using the "bootz" command. The syntax of "bootz" command is the same
3906 as the syntax of "bootm" command.
3908 Note, defining the CONFIG_SUPPORT_RAW_INITRD allows user to supply
3909 kernel with raw initrd images. The syntax is slightly different, the
3910 address of the initrd must be augmented by it's size, in the following
3911 format: "<initrd addres>:<initrd size>".
3917 One of the features of U-Boot is that you can dynamically load and
3918 run "standalone" applications, which can use some resources of
3919 U-Boot like console I/O functions or interrupt services.
3921 Two simple examples are included with the sources:
3926 'examples/hello_world.c' contains a small "Hello World" Demo
3927 application; it is automatically compiled when you build U-Boot.
3928 It's configured to run at address 0x00040004, so you can play with it
3932 ## Ready for S-Record download ...
3933 ~>examples/hello_world.srec
3934 1 2 3 4 5 6 7 8 9 10 11 ...
3935 [file transfer complete]
3937 ## Start Addr = 0x00040004
3939 => go 40004 Hello World! This is a test.
3940 ## Starting application at 0x00040004 ...
3951 Hit any key to exit ...
3953 ## Application terminated, rc = 0x0
3955 Another example, which demonstrates how to register a CPM interrupt
3956 handler with the U-Boot code, can be found in 'examples/timer.c'.
3957 Here, a CPM timer is set up to generate an interrupt every second.
3958 The interrupt service routine is trivial, just printing a '.'
3959 character, but this is just a demo program. The application can be
3960 controlled by the following keys:
3962 ? - print current values og the CPM Timer registers
3963 b - enable interrupts and start timer
3964 e - stop timer and disable interrupts
3965 q - quit application
3968 ## Ready for S-Record download ...
3969 ~>examples/timer.srec
3970 1 2 3 4 5 6 7 8 9 10 11 ...
3971 [file transfer complete]
3973 ## Start Addr = 0x00040004
3976 ## Starting application at 0x00040004 ...
3979 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
3982 [q, b, e, ?] Set interval 1000000 us
3985 [q, b, e, ?] ........
3986 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
3989 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
3992 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
3995 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
3997 [q, b, e, ?] ...Stopping timer
3999 [q, b, e, ?] ## Application terminated, rc = 0x0
4005 Over time, many people have reported problems when trying to use the
4006 "minicom" terminal emulation program for serial download. I (wd)
4007 consider minicom to be broken, and recommend not to use it. Under
4008 Unix, I recommend to use C-Kermit for general purpose use (and
4009 especially for kermit binary protocol download ("loadb" command), and
4010 use "cu" for S-Record download ("loads" command). See
4011 https://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3.
4012 for help with kermit.
4015 Nevertheless, if you absolutely want to use it try adding this
4016 configuration to your "File transfer protocols" section:
4018 Name Program Name U/D FullScr IO-Red. Multi
4019 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
4020 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
4026 Starting at version 0.9.2, U-Boot supports NetBSD both as host
4027 (build U-Boot) and target system (boots NetBSD/mpc8xx).
4029 Building requires a cross environment; it is known to work on
4030 NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
4031 need gmake since the Makefiles are not compatible with BSD make).
4032 Note that the cross-powerpc package does not install include files;
4033 attempting to build U-Boot will fail because <machine/ansi.h> is
4034 missing. This file has to be installed and patched manually:
4036 # cd /usr/pkg/cross/powerpc-netbsd/include
4038 # ln -s powerpc machine
4039 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
4040 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
4042 Native builds *don't* work due to incompatibilities between native
4043 and U-Boot include files.
4045 Booting assumes that (the first part of) the image booted is a
4046 stage-2 loader which in turn loads and then invokes the kernel
4047 proper. Loader sources will eventually appear in the NetBSD source
4048 tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
4049 meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
4052 Implementation Internals:
4053 =========================
4055 The following is not intended to be a complete description of every
4056 implementation detail. However, it should help to understand the
4057 inner workings of U-Boot and make it easier to port it to custom
4061 Initial Stack, Global Data:
4062 ---------------------------
4064 The implementation of U-Boot is complicated by the fact that U-Boot
4065 starts running out of ROM (flash memory), usually without access to
4066 system RAM (because the memory controller is not initialized yet).
4067 This means that we don't have writable Data or BSS segments, and BSS
4068 is not initialized as zero. To be able to get a C environment working
4069 at all, we have to allocate at least a minimal stack. Implementation
4070 options for this are defined and restricted by the CPU used: Some CPU
4071 models provide on-chip memory (like the IMMR area on MPC8xx and
4072 MPC826x processors), on others (parts of) the data cache can be
4073 locked as (mis-) used as memory, etc.
4075 Chris Hallinan posted a good summary of these issues to the
4076 U-Boot mailing list:
4078 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
4080 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
4083 Correct me if I'm wrong, folks, but the way I understand it
4084 is this: Using DCACHE as initial RAM for Stack, etc, does not
4085 require any physical RAM backing up the cache. The cleverness
4086 is that the cache is being used as a temporary supply of
4087 necessary storage before the SDRAM controller is setup. It's
4088 beyond the scope of this list to explain the details, but you
4089 can see how this works by studying the cache architecture and
4090 operation in the architecture and processor-specific manuals.
4092 OCM is On Chip Memory, which I believe the 405GP has 4K. It
4093 is another option for the system designer to use as an
4094 initial stack/RAM area prior to SDRAM being available. Either
4095 option should work for you. Using CS 4 should be fine if your
4096 board designers haven't used it for something that would
4097 cause you grief during the initial boot! It is frequently not
4100 CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere
4101 with your processor/board/system design. The default value
4102 you will find in any recent u-boot distribution in
4103 walnut.h should work for you. I'd set it to a value larger
4104 than your SDRAM module. If you have a 64MB SDRAM module, set
4105 it above 400_0000. Just make sure your board has no resources
4106 that are supposed to respond to that address! That code in
4107 start.S has been around a while and should work as is when
4108 you get the config right.
4113 It is essential to remember this, since it has some impact on the C
4114 code for the initialization procedures:
4116 * Initialized global data (data segment) is read-only. Do not attempt
4119 * Do not use any uninitialized global data (or implicitly initialized
4120 as zero data - BSS segment) at all - this is undefined, initiali-
4121 zation is performed later (when relocating to RAM).
4123 * Stack space is very limited. Avoid big data buffers or things like
4126 Having only the stack as writable memory limits means we cannot use
4127 normal global data to share information between the code. But it
4128 turned out that the implementation of U-Boot can be greatly
4129 simplified by making a global data structure (gd_t) available to all
4130 functions. We could pass a pointer to this data as argument to _all_
4131 functions, but this would bloat the code. Instead we use a feature of
4132 the GCC compiler (Global Register Variables) to share the data: we
4133 place a pointer (gd) to the global data into a register which we
4134 reserve for this purpose.
4136 When choosing a register for such a purpose we are restricted by the
4137 relevant (E)ABI specifications for the current architecture, and by
4138 GCC's implementation.
4140 For PowerPC, the following registers have specific use:
4142 R2: reserved for system use
4143 R3-R4: parameter passing and return values
4144 R5-R10: parameter passing
4145 R13: small data area pointer
4149 (U-Boot also uses R12 as internal GOT pointer. r12
4150 is a volatile register so r12 needs to be reset when
4151 going back and forth between asm and C)
4153 ==> U-Boot will use R2 to hold a pointer to the global data
4155 Note: on PPC, we could use a static initializer (since the
4156 address of the global data structure is known at compile time),
4157 but it turned out that reserving a register results in somewhat
4158 smaller code - although the code savings are not that big (on
4159 average for all boards 752 bytes for the whole U-Boot image,
4160 624 text + 127 data).
4162 On ARM, the following registers are used:
4164 R0: function argument word/integer result
4165 R1-R3: function argument word
4166 R9: platform specific
4167 R10: stack limit (used only if stack checking is enabled)
4168 R11: argument (frame) pointer
4169 R12: temporary workspace
4172 R15: program counter
4174 ==> U-Boot will use R9 to hold a pointer to the global data
4176 Note: on ARM, only R_ARM_RELATIVE relocations are supported.
4178 On Nios II, the ABI is documented here:
4179 https://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf
4181 ==> U-Boot will use gp to hold a pointer to the global data
4183 Note: on Nios II, we give "-G0" option to gcc and don't use gp
4184 to access small data sections, so gp is free.
4186 On NDS32, the following registers are used:
4188 R0-R1: argument/return
4190 R15: temporary register for assembler
4191 R16: trampoline register
4192 R28: frame pointer (FP)
4193 R29: global pointer (GP)
4194 R30: link register (LP)
4195 R31: stack pointer (SP)
4196 PC: program counter (PC)
4198 ==> U-Boot will use R10 to hold a pointer to the global data
4200 NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
4201 or current versions of GCC may "optimize" the code too much.
4203 On RISC-V, the following registers are used:
4205 x0: hard-wired zero (zero)
4206 x1: return address (ra)
4207 x2: stack pointer (sp)
4208 x3: global pointer (gp)
4209 x4: thread pointer (tp)
4210 x5: link register (t0)
4211 x8: frame pointer (fp)
4212 x10-x11: arguments/return values (a0-1)
4213 x12-x17: arguments (a2-7)
4214 x28-31: temporaries (t3-6)
4215 pc: program counter (pc)
4217 ==> U-Boot will use gp to hold a pointer to the global data
4222 U-Boot runs in system state and uses physical addresses, i.e. the
4223 MMU is not used either for address mapping nor for memory protection.
4225 The available memory is mapped to fixed addresses using the memory
4226 controller. In this process, a contiguous block is formed for each
4227 memory type (Flash, SDRAM, SRAM), even when it consists of several
4228 physical memory banks.
4230 U-Boot is installed in the first 128 kB of the first Flash bank (on
4231 TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
4232 booting and sizing and initializing DRAM, the code relocates itself
4233 to the upper end of DRAM. Immediately below the U-Boot code some
4234 memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN
4235 configuration setting]. Below that, a structure with global Board
4236 Info data is placed, followed by the stack (growing downward).
4238 Additionally, some exception handler code is copied to the low 8 kB
4239 of DRAM (0x00000000 ... 0x00001FFF).
4241 So a typical memory configuration with 16 MB of DRAM could look like
4244 0x0000 0000 Exception Vector code
4247 0x0000 2000 Free for Application Use
4253 0x00FB FF20 Monitor Stack (Growing downward)
4254 0x00FB FFAC Board Info Data and permanent copy of global data
4255 0x00FC 0000 Malloc Arena
4258 0x00FE 0000 RAM Copy of Monitor Code
4259 ... eventually: LCD or video framebuffer
4260 ... eventually: pRAM (Protected RAM - unchanged by reset)
4261 0x00FF FFFF [End of RAM]
4264 System Initialization:
4265 ----------------------
4267 In the reset configuration, U-Boot starts at the reset entry point
4268 (on most PowerPC systems at address 0x00000100). Because of the reset
4269 configuration for CS0# this is a mirror of the on board Flash memory.
4270 To be able to re-map memory U-Boot then jumps to its link address.
4271 To be able to implement the initialization code in C, a (small!)
4272 initial stack is set up in the internal Dual Ported RAM (in case CPUs
4273 which provide such a feature like), or in a locked part of the data
4274 cache. After that, U-Boot initializes the CPU core, the caches and
4277 Next, all (potentially) available memory banks are mapped using a
4278 preliminary mapping. For example, we put them on 512 MB boundaries
4279 (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
4280 on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
4281 programmed for SDRAM access. Using the temporary configuration, a
4282 simple memory test is run that determines the size of the SDRAM
4285 When there is more than one SDRAM bank, and the banks are of
4286 different size, the largest is mapped first. For equal size, the first
4287 bank (CS2#) is mapped first. The first mapping is always for address
4288 0x00000000, with any additional banks following immediately to create
4289 contiguous memory starting from 0.
4291 Then, the monitor installs itself at the upper end of the SDRAM area
4292 and allocates memory for use by malloc() and for the global Board
4293 Info data; also, the exception vector code is copied to the low RAM
4294 pages, and the final stack is set up.
4296 Only after this relocation will you have a "normal" C environment;
4297 until that you are restricted in several ways, mostly because you are
4298 running from ROM, and because the code will have to be relocated to a
4302 U-Boot Porting Guide:
4303 ----------------------
4305 [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
4309 int main(int argc, char *argv[])
4311 sighandler_t no_more_time;
4313 signal(SIGALRM, no_more_time);
4314 alarm(PROJECT_DEADLINE - toSec (3 * WEEK));
4316 if (available_money > available_manpower) {
4317 Pay consultant to port U-Boot;
4321 Download latest U-Boot source;
4323 Subscribe to u-boot mailing list;
4326 email("Hi, I am new to U-Boot, how do I get started?");
4329 Read the README file in the top level directory;
4330 Read https://www.denx.de/wiki/bin/view/DULG/Manual;
4331 Read applicable doc/README.*;
4332 Read the source, Luke;
4333 /* find . -name "*.[chS]" | xargs grep -i <keyword> */
4336 if (available_money > toLocalCurrency ($2500))
4339 Add a lot of aggravation and time;
4341 if (a similar board exists) { /* hopefully... */
4342 cp -a board/<similar> board/<myboard>
4343 cp include/configs/<similar>.h include/configs/<myboard>.h
4345 Create your own board support subdirectory;
4346 Create your own board include/configs/<myboard>.h file;
4348 Edit new board/<myboard> files
4349 Edit new include/configs/<myboard>.h
4354 Add / modify source code;
4358 email("Hi, I am having problems...");
4360 Send patch file to the U-Boot email list;
4361 if (reasonable critiques)
4362 Incorporate improvements from email list code review;
4364 Defend code as written;
4370 void no_more_time (int sig)
4379 All contributions to U-Boot should conform to the Linux kernel
4380 coding style; see the kernel coding style guide at
4381 https://www.kernel.org/doc/html/latest/process/coding-style.html, and the
4382 script "scripts/Lindent" in your Linux kernel source directory.
4384 Source files originating from a different project (for example the
4385 MTD subsystem) are generally exempt from these guidelines and are not
4386 reformatted to ease subsequent migration to newer versions of those
4389 Please note that U-Boot is implemented in C (and to some small parts in
4390 Assembler); no C++ is used, so please do not use C++ style comments (//)
4393 Please also stick to the following formatting rules:
4394 - remove any trailing white space
4395 - use TAB characters for indentation and vertical alignment, not spaces
4396 - make sure NOT to use DOS '\r\n' line feeds
4397 - do not add more than 2 consecutive empty lines to source files
4398 - do not add trailing empty lines to source files
4400 Submissions which do not conform to the standards may be returned
4401 with a request to reformat the changes.
4407 Since the number of patches for U-Boot is growing, we need to
4408 establish some rules. Submissions which do not conform to these rules
4409 may be rejected, even when they contain important and valuable stuff.
4411 Please see https://www.denx.de/wiki/U-Boot/Patches for details.
4414 see https://lists.denx.de/listinfo/u-boot
4416 When you send a patch, please include the following information with
4419 * For bug fixes: a description of the bug and how your patch fixes
4420 this bug. Please try to include a way of demonstrating that the
4421 patch actually fixes something.
4423 * For new features: a description of the feature and your
4426 * For major contributions, add a MAINTAINERS file with your
4427 information and associated file and directory references.
4429 * When you add support for a new board, don't forget to add a
4430 maintainer e-mail address to the boards.cfg file, too.
4432 * If your patch adds new configuration options, don't forget to
4433 document these in the README file.
4435 * The patch itself. If you are using git (which is *strongly*
4436 recommended) you can easily generate the patch using the
4437 "git format-patch". If you then use "git send-email" to send it to
4438 the U-Boot mailing list, you will avoid most of the common problems
4439 with some other mail clients.
4441 If you cannot use git, use "diff -purN OLD NEW". If your version of
4442 diff does not support these options, then get the latest version of
4445 The current directory when running this command shall be the parent
4446 directory of the U-Boot source tree (i. e. please make sure that
4447 your patch includes sufficient directory information for the
4450 We prefer patches as plain text. MIME attachments are discouraged,
4451 and compressed attachments must not be used.
4453 * If one logical set of modifications affects or creates several
4454 files, all these changes shall be submitted in a SINGLE patch file.
4456 * Changesets that contain different, unrelated modifications shall be
4457 submitted as SEPARATE patches, one patch per changeset.
4462 * Before sending the patch, run the buildman script on your patched
4463 source tree and make sure that no errors or warnings are reported
4464 for any of the boards.
4466 * Keep your modifications to the necessary minimum: A patch
4467 containing several unrelated changes or arbitrary reformats will be
4468 returned with a request to re-formatting / split it.
4470 * If you modify existing code, make sure that your new code does not
4471 add to the memory footprint of the code ;-) Small is beautiful!
4472 When adding new features, these should compile conditionally only
4473 (using #ifdef), and the resulting code with the new feature
4474 disabled must not need more memory than the old code without your
4477 * Remember that there is a size limit of 100 kB per message on the
4478 u-boot mailing list. Bigger patches will be moderated. If they are
4479 reasonable and not too big, they will be acknowledged. But patches
4480 bigger than the size limit should be avoided.
projects / J-u-boot.git / blob