1# 2# (C) Copyright 2000 - 2013 3# Wolfgang Denk, DENX Software Engineering, wd@denx.de. 4# 5# SPDX-License-Identifier: GPL-2.0+ 6# 7 8Summary: 9======== 10 11This directory contains the source code for U-Boot, a boot loader for 12Embedded boards based on PowerPC, ARM, MIPS and several other 13processors, which can be installed in a boot ROM and used to 14initialize and test the hardware or to download and run application 15code. 16 17The development of U-Boot is closely related to Linux: some parts of 18the source code originate in the Linux source tree, we have some 19header files in common, and special provision has been made to 20support booting of Linux images. 21 22Some attention has been paid to make this software easily 23configurable and extendable. For instance, all monitor commands are 24implemented with the same call interface, so that it's very easy to 25add new commands. Also, instead of permanently adding rarely used 26code (for instance hardware test utilities) to the monitor, you can 27load and run it dynamically. 28 29 30Status: 31======= 32 33In general, all boards for which a configuration option exists in the 34Makefile have been tested to some extent and can be considered 35"working". In fact, many of them are used in production systems. 36 37In case of problems see the CHANGELOG file to find out who contributed 38the specific port. In addition, there are various MAINTAINERS files 39scattered throughout the U-Boot source identifying the people or 40companies responsible for various boards and subsystems. 41 42Note: As of August, 2010, there is no longer a CHANGELOG file in the 43actual U-Boot source tree; however, it can be created dynamically 44from the Git log using: 45 46 make CHANGELOG 47 48 49Where to get help: 50================== 51 52In case you have questions about, problems with or contributions for 53U-Boot, you should send a message to the U-Boot mailing list at 54<u-boot@lists.denx.de>. There is also an archive of previous traffic 55on the mailing list - please search the archive before asking FAQ's. 56Please see http://lists.denx.de/pipermail/u-boot and 57http://dir.gmane.org/gmane.comp.boot-loaders.u-boot 58 59 60Where to get source code: 61========================= 62 63The U-Boot source code is maintained in the Git repository at 64git://www.denx.de/git/u-boot.git ; you can browse it online at 65http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary 66 67The "snapshot" links on this page allow you to download tarballs of 68any version you might be interested in. Official releases are also 69available for FTP download from the ftp://ftp.denx.de/pub/u-boot/ 70directory. 71 72Pre-built (and tested) images are available from 73ftp://ftp.denx.de/pub/u-boot/images/ 74 75 76Where we come from: 77=================== 78 79- start from 8xxrom sources 80- create PPCBoot project (http://sourceforge.net/projects/ppcboot) 81- clean up code 82- make it easier to add custom boards 83- make it possible to add other [PowerPC] CPUs 84- extend functions, especially: 85 * Provide extended interface to Linux boot loader 86 * S-Record download 87 * network boot 88 * PCMCIA / CompactFlash / ATA disk / SCSI ... boot 89- create ARMBoot project (http://sourceforge.net/projects/armboot) 90- add other CPU families (starting with ARM) 91- create U-Boot project (http://sourceforge.net/projects/u-boot) 92- current project page: see http://www.denx.de/wiki/U-Boot 93 94 95Names and Spelling: 96=================== 97 98The "official" name of this project is "Das U-Boot". The spelling 99"U-Boot" shall be used in all written text (documentation, comments 100in source files etc.). Example: 101 102 This is the README file for the U-Boot project. 103 104File names etc. shall be based on the string "u-boot". Examples: 105 106 include/asm-ppc/u-boot.h 107 108 #include <asm/u-boot.h> 109 110Variable names, preprocessor constants etc. shall be either based on 111the string "u_boot" or on "U_BOOT". Example: 112 113 U_BOOT_VERSION u_boot_logo 114 IH_OS_U_BOOT u_boot_hush_start 115 116 117Versioning: 118=========== 119 120Starting with the release in October 2008, the names of the releases 121were changed from numerical release numbers without deeper meaning 122into a time stamp based numbering. Regular releases are identified by 123names consisting of the calendar year and month of the release date. 124Additional fields (if present) indicate release candidates or bug fix 125releases in "stable" maintenance trees. 126 127Examples: 128 U-Boot v2009.11 - Release November 2009 129 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree 130 U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release 131 132 133Directory Hierarchy: 134==================== 135 136/arch Architecture specific files 137 /arc Files generic to ARC architecture 138 /arm Files generic to ARM architecture 139 /avr32 Files generic to AVR32 architecture 140 /blackfin Files generic to Analog Devices Blackfin architecture 141 /m68k Files generic to m68k architecture 142 /microblaze Files generic to microblaze architecture 143 /mips Files generic to MIPS architecture 144 /nds32 Files generic to NDS32 architecture 145 /nios2 Files generic to Altera NIOS2 architecture 146 /openrisc Files generic to OpenRISC architecture 147 /powerpc Files generic to PowerPC architecture 148 /sandbox Files generic to HW-independent "sandbox" 149 /sh Files generic to SH architecture 150 /sparc Files generic to SPARC architecture 151 /x86 Files generic to x86 architecture 152/api Machine/arch independent API for external apps 153/board Board dependent files 154/cmd U-Boot commands functions 155/common Misc architecture independent functions 156/configs Board default configuration files 157/disk Code for disk drive partition handling 158/doc Documentation (don't expect too much) 159/drivers Commonly used device drivers 160/dts Contains Makefile for building internal U-Boot fdt. 161/examples Example code for standalone applications, etc. 162/fs Filesystem code (cramfs, ext2, jffs2, etc.) 163/include Header Files 164/lib Library routines generic to all architectures 165/Licenses Various license files 166/net Networking code 167/post Power On Self Test 168/scripts Various build scripts and Makefiles 169/test Various unit test files 170/tools Tools to build S-Record or U-Boot images, etc. 171 172Software Configuration: 173======================= 174 175Configuration is usually done using C preprocessor defines; the 176rationale behind that is to avoid dead code whenever possible. 177 178There are two classes of configuration variables: 179 180* Configuration _OPTIONS_: 181 These are selectable by the user and have names beginning with 182 "CONFIG_". 183 184* Configuration _SETTINGS_: 185 These depend on the hardware etc. and should not be meddled with if 186 you don't know what you're doing; they have names beginning with 187 "CONFIG_SYS_". 188 189Previously, all configuration was done by hand, which involved creating 190symbolic links and editing configuration files manually. More recently, 191U-Boot has added the Kbuild infrastructure used by the Linux kernel, 192allowing you to use the "make menuconfig" command to configure your 193build. 194 195 196Selection of Processor Architecture and Board Type: 197--------------------------------------------------- 198 199For all supported boards there are ready-to-use default 200configurations available; just type "make <board_name>_defconfig". 201 202Example: For a TQM823L module type: 203 204 cd u-boot 205 make TQM823L_defconfig 206 207Note: If you're looking for the default configuration file for a board 208you're sure used to be there but is now missing, check the file 209doc/README.scrapyard for a list of no longer supported boards. 210 211Sandbox Environment: 212-------------------- 213 214U-Boot can be built natively to run on a Linux host using the 'sandbox' 215board. This allows feature development which is not board- or architecture- 216specific to be undertaken on a native platform. The sandbox is also used to 217run some of U-Boot's tests. 218 219See board/sandbox/README.sandbox for more details. 220 221 222Board Initialisation Flow: 223-------------------------- 224 225This is the intended start-up flow for boards. This should apply for both 226SPL and U-Boot proper (i.e. they both follow the same rules). 227 228Note: "SPL" stands for "Secondary Program Loader," which is explained in 229more detail later in this file. 230 231At present, SPL mostly uses a separate code path, but the function names 232and roles of each function are the same. Some boards or architectures 233may not conform to this. At least most ARM boards which use 234CONFIG_SPL_FRAMEWORK conform to this. 235 236Execution typically starts with an architecture-specific (and possibly 237CPU-specific) start.S file, such as: 238 239 - arch/arm/cpu/armv7/start.S 240 - arch/powerpc/cpu/mpc83xx/start.S 241 - arch/mips/cpu/start.S 242 243and so on. From there, three functions are called; the purpose and 244limitations of each of these functions are described below. 245 246lowlevel_init(): 247 - purpose: essential init to permit execution to reach board_init_f() 248 - no global_data or BSS 249 - there is no stack (ARMv7 may have one but it will soon be removed) 250 - must not set up SDRAM or use console 251 - must only do the bare minimum to allow execution to continue to 252 board_init_f() 253 - this is almost never needed 254 - return normally from this function 255 256board_init_f(): 257 - purpose: set up the machine ready for running board_init_r(): 258 i.e. SDRAM and serial UART 259 - global_data is available 260 - stack is in SRAM 261 - BSS is not available, so you cannot use global/static variables, 262 only stack variables and global_data 263 264 Non-SPL-specific notes: 265 - dram_init() is called to set up DRAM. If already done in SPL this 266 can do nothing 267 268 SPL-specific notes: 269 - you can override the entire board_init_f() function with your own 270 version as needed. 271 - preloader_console_init() can be called here in extremis 272 - should set up SDRAM, and anything needed to make the UART work 273 - these is no need to clear BSS, it will be done by crt0.S 274 - must return normally from this function (don't call board_init_r() 275 directly) 276 277Here the BSS is cleared. For SPL, if CONFIG_SPL_STACK_R is defined, then at 278this point the stack and global_data are relocated to below 279CONFIG_SPL_STACK_R_ADDR. For non-SPL, U-Boot is relocated to run at the top of 280memory. 281 282board_init_r(): 283 - purpose: main execution, common code 284 - global_data is available 285 - SDRAM is available 286 - BSS is available, all static/global variables can be used 287 - execution eventually continues to main_loop() 288 289 Non-SPL-specific notes: 290 - U-Boot is relocated to the top of memory and is now running from 291 there. 292 293 SPL-specific notes: 294 - stack is optionally in SDRAM, if CONFIG_SPL_STACK_R is defined and 295 CONFIG_SPL_STACK_R_ADDR points into SDRAM 296 - preloader_console_init() can be called here - typically this is 297 done by defining CONFIG_SPL_BOARD_INIT and then supplying a 298 spl_board_init() function containing this call 299 - loads U-Boot or (in falcon mode) Linux 300 301 302 303Configuration Options: 304---------------------- 305 306Configuration depends on the combination of board and CPU type; all 307such information is kept in a configuration file 308"include/configs/<board_name>.h". 309 310Example: For a TQM823L module, all configuration settings are in 311"include/configs/TQM823L.h". 312 313 314Many of the options are named exactly as the corresponding Linux 315kernel configuration options. The intention is to make it easier to 316build a config tool - later. 317 318 319The following options need to be configured: 320 321- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX. 322 323- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS. 324 325- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined) 326 Define exactly one, e.g. CONFIG_ATSTK1002 327 328- Marvell Family Member 329 CONFIG_SYS_MVFS - define it if you want to enable 330 multiple fs option at one time 331 for marvell soc family 332 333- 8xx CPU Options: (if using an MPC8xx CPU) 334 CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if 335 get_gclk_freq() cannot work 336 e.g. if there is no 32KHz 337 reference PIT/RTC clock 338 CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK 339 or XTAL/EXTAL) 340 341- 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU): 342 CONFIG_SYS_8xx_CPUCLK_MIN 343 CONFIG_SYS_8xx_CPUCLK_MAX 344 CONFIG_8xx_CPUCLK_DEFAULT 345 See doc/README.MPC866 346 347 CONFIG_SYS_MEASURE_CPUCLK 348 349 Define this to measure the actual CPU clock instead 350 of relying on the correctness of the configured 351 values. Mostly useful for board bringup to make sure 352 the PLL is locked at the intended frequency. Note 353 that this requires a (stable) reference clock (32 kHz 354 RTC clock or CONFIG_SYS_8XX_XIN) 355 356 CONFIG_SYS_DELAYED_ICACHE 357 358 Define this option if you want to enable the 359 ICache only when Code runs from RAM. 360 361- 85xx CPU Options: 362 CONFIG_SYS_PPC64 363 364 Specifies that the core is a 64-bit PowerPC implementation (implements 365 the "64" category of the Power ISA). This is necessary for ePAPR 366 compliance, among other possible reasons. 367 368 CONFIG_SYS_FSL_TBCLK_DIV 369 370 Defines the core time base clock divider ratio compared to the 371 system clock. On most PQ3 devices this is 8, on newer QorIQ 372 devices it can be 16 or 32. The ratio varies from SoC to Soc. 373 374 CONFIG_SYS_FSL_PCIE_COMPAT 375 376 Defines the string to utilize when trying to match PCIe device 377 tree nodes for the given platform. 378 379 CONFIG_SYS_PPC_E500_DEBUG_TLB 380 381 Enables a temporary TLB entry to be used during boot to work 382 around limitations in e500v1 and e500v2 external debugger 383 support. This reduces the portions of the boot code where 384 breakpoints and single stepping do not work. The value of this 385 symbol should be set to the TLB1 entry to be used for this 386 purpose. 387 388 CONFIG_SYS_FSL_ERRATUM_A004510 389 390 Enables a workaround for erratum A004510. If set, 391 then CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and 392 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set. 393 394 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV 395 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional) 396 397 Defines one or two SoC revisions (low 8 bits of SVR) 398 for which the A004510 workaround should be applied. 399 400 The rest of SVR is either not relevant to the decision 401 of whether the erratum is present (e.g. p2040 versus 402 p2041) or is implied by the build target, which controls 403 whether CONFIG_SYS_FSL_ERRATUM_A004510 is set. 404 405 See Freescale App Note 4493 for more information about 406 this erratum. 407 408 CONFIG_A003399_NOR_WORKAROUND 409 Enables a workaround for IFC erratum A003399. It is only 410 required during NOR boot. 411 412 CONFIG_A008044_WORKAROUND 413 Enables a workaround for T1040/T1042 erratum A008044. It is only 414 required during NAND boot and valid for Rev 1.0 SoC revision 415 416 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY 417 418 This is the value to write into CCSR offset 0x18600 419 according to the A004510 workaround. 420 421 CONFIG_SYS_FSL_DSP_DDR_ADDR 422 This value denotes start offset of DDR memory which is 423 connected exclusively to the DSP cores. 424 425 CONFIG_SYS_FSL_DSP_M2_RAM_ADDR 426 This value denotes start offset of M2 memory 427 which is directly connected to the DSP core. 428 429 CONFIG_SYS_FSL_DSP_M3_RAM_ADDR 430 This value denotes start offset of M3 memory which is directly 431 connected to the DSP core. 432 433 CONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT 434 This value denotes start offset of DSP CCSR space. 435 436 CONFIG_SYS_FSL_SINGLE_SOURCE_CLK 437 Single Source Clock is clocking mode present in some of FSL SoC's. 438 In this mode, a single differential clock is used to supply 439 clocks to the sysclock, ddrclock and usbclock. 440 441 CONFIG_SYS_CPC_REINIT_F 442 This CONFIG is defined when the CPC is configured as SRAM at the 443 time of U-Boot entry and is required to be re-initialized. 444 445 CONFIG_DEEP_SLEEP 446 Indicates this SoC supports deep sleep feature. If deep sleep is 447 supported, core will start to execute uboot when wakes up. 448 449- Generic CPU options: 450 CONFIG_SYS_GENERIC_GLOBAL_DATA 451 Defines global data is initialized in generic board board_init_f(). 452 If this macro is defined, global data is created and cleared in 453 generic board board_init_f(). Without this macro, architecture/board 454 should initialize global data before calling board_init_f(). 455 456 CONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN 457 458 Defines the endianess of the CPU. Implementation of those 459 values is arch specific. 460 461 CONFIG_SYS_FSL_DDR 462 Freescale DDR driver in use. This type of DDR controller is 463 found in mpc83xx, mpc85xx, mpc86xx as well as some ARM core 464 SoCs. 465 466 CONFIG_SYS_FSL_DDR_ADDR 467 Freescale DDR memory-mapped register base. 468 469 CONFIG_SYS_FSL_DDR_EMU 470 Specify emulator support for DDR. Some DDR features such as 471 deskew training are not available. 472 473 CONFIG_SYS_FSL_DDRC_GEN1 474 Freescale DDR1 controller. 475 476 CONFIG_SYS_FSL_DDRC_GEN2 477 Freescale DDR2 controller. 478 479 CONFIG_SYS_FSL_DDRC_GEN3 480 Freescale DDR3 controller. 481 482 CONFIG_SYS_FSL_DDRC_GEN4 483 Freescale DDR4 controller. 484 485 CONFIG_SYS_FSL_DDRC_ARM_GEN3 486 Freescale DDR3 controller for ARM-based SoCs. 487 488 CONFIG_SYS_FSL_DDR1 489 Board config to use DDR1. It can be enabled for SoCs with 490 Freescale DDR1 or DDR2 controllers, depending on the board 491 implemetation. 492 493 CONFIG_SYS_FSL_DDR2 494 Board config to use DDR2. It can be enabled for SoCs with 495 Freescale DDR2 or DDR3 controllers, depending on the board 496 implementation. 497 498 CONFIG_SYS_FSL_DDR3 499 Board config to use DDR3. It can be enabled for SoCs with 500 Freescale DDR3 or DDR3L controllers. 501 502 CONFIG_SYS_FSL_DDR3L 503 Board config to use DDR3L. It can be enabled for SoCs with 504 DDR3L controllers. 505 506 CONFIG_SYS_FSL_DDR4 507 Board config to use DDR4. It can be enabled for SoCs with 508 DDR4 controllers. 509 510 CONFIG_SYS_FSL_IFC_BE 511 Defines the IFC controller register space as Big Endian 512 513 CONFIG_SYS_FSL_IFC_LE 514 Defines the IFC controller register space as Little Endian 515 516 CONFIG_SYS_FSL_PBL_PBI 517 It enables addition of RCW (Power on reset configuration) in built image. 518 Please refer doc/README.pblimage for more details 519 520 CONFIG_SYS_FSL_PBL_RCW 521 It adds PBI(pre-boot instructions) commands in u-boot build image. 522 PBI commands can be used to configure SoC before it starts the execution. 523 Please refer doc/README.pblimage for more details 524 525 CONFIG_SPL_FSL_PBL 526 It adds a target to create boot binary having SPL binary in PBI format 527 concatenated with u-boot binary. 528 529 CONFIG_SYS_FSL_DDR_BE 530 Defines the DDR controller register space as Big Endian 531 532 CONFIG_SYS_FSL_DDR_LE 533 Defines the DDR controller register space as Little Endian 534 535 CONFIG_SYS_FSL_DDR_SDRAM_BASE_PHY 536 Physical address from the view of DDR controllers. It is the 537 same as CONFIG_SYS_DDR_SDRAM_BASE for all Power SoCs. But 538 it could be different for ARM SoCs. 539 540 CONFIG_SYS_FSL_DDR_INTLV_256B 541 DDR controller interleaving on 256-byte. This is a special 542 interleaving mode, handled by Dickens for Freescale layerscape 543 SoCs with ARM core. 544 545 CONFIG_SYS_FSL_DDR_MAIN_NUM_CTRLS 546 Number of controllers used as main memory. 547 548 CONFIG_SYS_FSL_OTHER_DDR_NUM_CTRLS 549 Number of controllers used for other than main memory. 550 551 CONFIG_SYS_FSL_HAS_DP_DDR 552 Defines the SoC has DP-DDR used for DPAA. 553 554 CONFIG_SYS_FSL_SEC_BE 555 Defines the SEC controller register space as Big Endian 556 557 CONFIG_SYS_FSL_SEC_LE 558 Defines the SEC controller register space as Little Endian 559 560- MIPS CPU options: 561 CONFIG_SYS_INIT_SP_OFFSET 562 563 Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack 564 pointer. This is needed for the temporary stack before 565 relocation. 566 567 CONFIG_SYS_MIPS_CACHE_MODE 568 569 Cache operation mode for the MIPS CPU. 570 See also arch/mips/include/asm/mipsregs.h. 571 Possible values are: 572 CONF_CM_CACHABLE_NO_WA 573 CONF_CM_CACHABLE_WA 574 CONF_CM_UNCACHED 575 CONF_CM_CACHABLE_NONCOHERENT 576 CONF_CM_CACHABLE_CE 577 CONF_CM_CACHABLE_COW 578 CONF_CM_CACHABLE_CUW 579 CONF_CM_CACHABLE_ACCELERATED 580 581 CONFIG_SYS_XWAY_EBU_BOOTCFG 582 583 Special option for Lantiq XWAY SoCs for booting from NOR flash. 584 See also arch/mips/cpu/mips32/start.S. 585 586 CONFIG_XWAY_SWAP_BYTES 587 588 Enable compilation of tools/xway-swap-bytes needed for Lantiq 589 XWAY SoCs for booting from NOR flash. The U-Boot image needs to 590 be swapped if a flash programmer is used. 591 592- ARM options: 593 CONFIG_SYS_EXCEPTION_VECTORS_HIGH 594 595 Select high exception vectors of the ARM core, e.g., do not 596 clear the V bit of the c1 register of CP15. 597 598 CONFIG_SYS_THUMB_BUILD 599 600 Use this flag to build U-Boot using the Thumb instruction 601 set for ARM architectures. Thumb instruction set provides 602 better code density. For ARM architectures that support 603 Thumb2 this flag will result in Thumb2 code generated by 604 GCC. 605 606 CONFIG_ARM_ERRATA_716044 607 CONFIG_ARM_ERRATA_742230 608 CONFIG_ARM_ERRATA_743622 609 CONFIG_ARM_ERRATA_751472 610 CONFIG_ARM_ERRATA_761320 611 CONFIG_ARM_ERRATA_773022 612 CONFIG_ARM_ERRATA_774769 613 CONFIG_ARM_ERRATA_794072 614 615 If set, the workarounds for these ARM errata are applied early 616 during U-Boot startup. Note that these options force the 617 workarounds to be applied; no CPU-type/version detection 618 exists, unlike the similar options in the Linux kernel. Do not 619 set these options unless they apply! 620 621 COUNTER_FREQUENCY 622 Generic timer clock source frequency. 623 624 COUNTER_FREQUENCY_REAL 625 Generic timer clock source frequency if the real clock is 626 different from COUNTER_FREQUENCY, and can only be determined 627 at run time. 628 629 NOTE: The following can be machine specific errata. These 630 do have ability to provide rudimentary version and machine 631 specific checks, but expect no product checks. 632 CONFIG_ARM_ERRATA_430973 633 CONFIG_ARM_ERRATA_454179 634 CONFIG_ARM_ERRATA_621766 635 CONFIG_ARM_ERRATA_798870 636 CONFIG_ARM_ERRATA_801819 637 638- Tegra SoC options: 639 CONFIG_TEGRA_SUPPORT_NON_SECURE 640 641 Support executing U-Boot in non-secure (NS) mode. Certain 642 impossible actions will be skipped if the CPU is in NS mode, 643 such as ARM architectural timer initialization. 644 645- Linux Kernel Interface: 646 CONFIG_CLOCKS_IN_MHZ 647 648 U-Boot stores all clock information in Hz 649 internally. For binary compatibility with older Linux 650 kernels (which expect the clocks passed in the 651 bd_info data to be in MHz) the environment variable 652 "clocks_in_mhz" can be defined so that U-Boot 653 converts clock data to MHZ before passing it to the 654 Linux kernel. 655 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of 656 "clocks_in_mhz=1" is automatically included in the 657 default environment. 658 659 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only] 660 661 When transferring memsize parameter to Linux, some versions 662 expect it to be in bytes, others in MB. 663 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes. 664 665 CONFIG_OF_LIBFDT 666 667 New kernel versions are expecting firmware settings to be 668 passed using flattened device trees (based on open firmware 669 concepts). 670 671 CONFIG_OF_LIBFDT 672 * New libfdt-based support 673 * Adds the "fdt" command 674 * The bootm command automatically updates the fdt 675 676 OF_CPU - The proper name of the cpus node (only required for 677 MPC512X and MPC5xxx based boards). 678 OF_SOC - The proper name of the soc node (only required for 679 MPC512X and MPC5xxx based boards). 680 OF_TBCLK - The timebase frequency. 681 OF_STDOUT_PATH - The path to the console device 682 683 boards with QUICC Engines require OF_QE to set UCC MAC 684 addresses 685 686 CONFIG_OF_BOARD_SETUP 687 688 Board code has addition modification that it wants to make 689 to the flat device tree before handing it off to the kernel 690 691 CONFIG_OF_SYSTEM_SETUP 692 693 Other code has addition modification that it wants to make 694 to the flat device tree before handing it off to the kernel. 695 This causes ft_system_setup() to be called before booting 696 the kernel. 697 698 CONFIG_OF_IDE_FIXUP 699 700 U-Boot can detect if an IDE device is present or not. 701 If not, and this new config option is activated, U-Boot 702 removes the ATA node from the DTS before booting Linux, 703 so the Linux IDE driver does not probe the device and 704 crash. This is needed for buggy hardware (uc101) where 705 no pull down resistor is connected to the signal IDE5V_DD7. 706 707 CONFIG_MACH_TYPE [relevant for ARM only][mandatory] 708 709 This setting is mandatory for all boards that have only one 710 machine type and must be used to specify the machine type 711 number as it appears in the ARM machine registry 712 (see http://www.arm.linux.org.uk/developer/machines/). 713 Only boards that have multiple machine types supported 714 in a single configuration file and the machine type is 715 runtime discoverable, do not have to use this setting. 716 717- vxWorks boot parameters: 718 719 bootvx constructs a valid bootline using the following 720 environments variables: bootdev, bootfile, ipaddr, netmask, 721 serverip, gatewayip, hostname, othbootargs. 722 It loads the vxWorks image pointed bootfile. 723 724 Note: If a "bootargs" environment is defined, it will overwride 725 the defaults discussed just above. 726 727- Cache Configuration: 728 CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot 729 CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot 730 CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot 731 732- Cache Configuration for ARM: 733 CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache 734 controller 735 CONFIG_SYS_PL310_BASE - Physical base address of PL310 736 controller register space 737 738- Serial Ports: 739 CONFIG_PL010_SERIAL 740 741 Define this if you want support for Amba PrimeCell PL010 UARTs. 742 743 CONFIG_PL011_SERIAL 744 745 Define this if you want support for Amba PrimeCell PL011 UARTs. 746 747 CONFIG_PL011_CLOCK 748 749 If you have Amba PrimeCell PL011 UARTs, set this variable to 750 the clock speed of the UARTs. 751 752 CONFIG_PL01x_PORTS 753 754 If you have Amba PrimeCell PL010 or PL011 UARTs on your board, 755 define this to a list of base addresses for each (supported) 756 port. See e.g. include/configs/versatile.h 757 758 CONFIG_SERIAL_HW_FLOW_CONTROL 759 760 Define this variable to enable hw flow control in serial driver. 761 Current user of this option is drivers/serial/nsl16550.c driver 762 763- Console Interface: 764 Depending on board, define exactly one serial port 765 (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2, 766 CONFIG_8xx_CONS_SCC1, ...), or switch off the serial 767 console by defining CONFIG_8xx_CONS_NONE 768 769 Note: if CONFIG_8xx_CONS_NONE is defined, the serial 770 port routines must be defined elsewhere 771 (i.e. serial_init(), serial_getc(), ...) 772 773 CONFIG_CFB_CONSOLE 774 Enables console device for a color framebuffer. Needs following 775 defines (cf. smiLynxEM, i8042) 776 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation 777 (default big endian) 778 VIDEO_HW_RECTFILL graphic chip supports 779 rectangle fill 780 (cf. smiLynxEM) 781 VIDEO_HW_BITBLT graphic chip supports 782 bit-blit (cf. smiLynxEM) 783 VIDEO_VISIBLE_COLS visible pixel columns 784 (cols=pitch) 785 VIDEO_VISIBLE_ROWS visible pixel rows 786 VIDEO_PIXEL_SIZE bytes per pixel 787 VIDEO_DATA_FORMAT graphic data format 788 (0-5, cf. cfb_console.c) 789 VIDEO_FB_ADRS framebuffer address 790 VIDEO_KBD_INIT_FCT keyboard int fct 791 (i.e. rx51_kp_init()) 792 VIDEO_TSTC_FCT test char fct 793 (i.e. rx51_kp_tstc) 794 VIDEO_GETC_FCT get char fct 795 (i.e. rx51_kp_getc) 796 CONFIG_VIDEO_LOGO display Linux logo in 797 upper left corner 798 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of 799 linux_logo.h for logo. 800 Requires CONFIG_VIDEO_LOGO 801 CONFIG_CONSOLE_EXTRA_INFO 802 additional board info beside 803 the logo 804 CONFIG_HIDE_LOGO_VERSION 805 do not display bootloader 806 version string 807 808 When CONFIG_CFB_CONSOLE_ANSI is defined, console will support 809 a limited number of ANSI escape sequences (cursor control, 810 erase functions and limited graphics rendition control). 811 812 When CONFIG_CFB_CONSOLE is defined, video console is 813 default i/o. Serial console can be forced with 814 environment 'console=serial'. 815 816 When CONFIG_SILENT_CONSOLE is defined, all console 817 messages (by U-Boot and Linux!) can be silenced with 818 the "silent" environment variable. See 819 doc/README.silent for more information. 820 821 CONFIG_SYS_CONSOLE_BG_COL: define the backgroundcolor, default 822 is 0x00. 823 CONFIG_SYS_CONSOLE_FG_COL: define the foregroundcolor, default 824 is 0xa0. 825 826- Console Baudrate: 827 CONFIG_BAUDRATE - in bps 828 Select one of the baudrates listed in 829 CONFIG_SYS_BAUDRATE_TABLE, see below. 830 CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale 831 832- Console Rx buffer length 833 With CONFIG_SYS_SMC_RXBUFLEN it is possible to define 834 the maximum receive buffer length for the SMC. 835 This option is actual only for 82xx and 8xx possible. 836 If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE 837 must be defined, to setup the maximum idle timeout for 838 the SMC. 839 840- Pre-Console Buffer: 841 Prior to the console being initialised (i.e. serial UART 842 initialised etc) all console output is silently discarded. 843 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to 844 buffer any console messages prior to the console being 845 initialised to a buffer of size CONFIG_PRE_CON_BUF_SZ 846 bytes located at CONFIG_PRE_CON_BUF_ADDR. The buffer is 847 a circular buffer, so if more than CONFIG_PRE_CON_BUF_SZ 848 bytes are output before the console is initialised, the 849 earlier bytes are discarded. 850 851 Note that when printing the buffer a copy is made on the 852 stack so CONFIG_PRE_CON_BUF_SZ must fit on the stack. 853 854 'Sane' compilers will generate smaller code if 855 CONFIG_PRE_CON_BUF_SZ is a power of 2 856 857- Autoboot Command: 858 CONFIG_BOOTCOMMAND 859 Only needed when CONFIG_BOOTDELAY is enabled; 860 define a command string that is automatically executed 861 when no character is read on the console interface 862 within "Boot Delay" after reset. 863 864 CONFIG_BOOTARGS 865 This can be used to pass arguments to the bootm 866 command. The value of CONFIG_BOOTARGS goes into the 867 environment value "bootargs". 868 869 CONFIG_RAMBOOT and CONFIG_NFSBOOT 870 The value of these goes into the environment as 871 "ramboot" and "nfsboot" respectively, and can be used 872 as a convenience, when switching between booting from 873 RAM and NFS. 874 875- Bootcount: 876 CONFIG_BOOTCOUNT_LIMIT 877 Implements a mechanism for detecting a repeating reboot 878 cycle, see: 879 http://www.denx.de/wiki/view/DULG/UBootBootCountLimit 880 881 CONFIG_BOOTCOUNT_ENV 882 If no softreset save registers are found on the hardware 883 "bootcount" is stored in the environment. To prevent a 884 saveenv on all reboots, the environment variable 885 "upgrade_available" is used. If "upgrade_available" is 886 0, "bootcount" is always 0, if "upgrade_available" is 887 1 "bootcount" is incremented in the environment. 888 So the Userspace Applikation must set the "upgrade_available" 889 and "bootcount" variable to 0, if a boot was successfully. 890 891- Pre-Boot Commands: 892 CONFIG_PREBOOT 893 894 When this option is #defined, the existence of the 895 environment variable "preboot" will be checked 896 immediately before starting the CONFIG_BOOTDELAY 897 countdown and/or running the auto-boot command resp. 898 entering interactive mode. 899 900 This feature is especially useful when "preboot" is 901 automatically generated or modified. For an example 902 see the LWMON board specific code: here "preboot" is 903 modified when the user holds down a certain 904 combination of keys on the (special) keyboard when 905 booting the systems 906 907- Serial Download Echo Mode: 908 CONFIG_LOADS_ECHO 909 If defined to 1, all characters received during a 910 serial download (using the "loads" command) are 911 echoed back. This might be needed by some terminal 912 emulations (like "cu"), but may as well just take 913 time on others. This setting #define's the initial 914 value of the "loads_echo" environment variable. 915 916- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined) 917 CONFIG_KGDB_BAUDRATE 918 Select one of the baudrates listed in 919 CONFIG_SYS_BAUDRATE_TABLE, see below. 920 921- Monitor Functions: 922 Monitor commands can be included or excluded 923 from the build by using the #include files 924 <config_cmd_all.h> and #undef'ing unwanted 925 commands, or adding #define's for wanted commands. 926 927 The default command configuration includes all commands 928 except those marked below with a "*". 929 930 CONFIG_CMD_AES AES 128 CBC encrypt/decrypt 931 CONFIG_CMD_ASKENV * ask for env variable 932 CONFIG_CMD_BDI bdinfo 933 CONFIG_CMD_BEDBUG * Include BedBug Debugger 934 CONFIG_CMD_BMP * BMP support 935 CONFIG_CMD_BSP * Board specific commands 936 CONFIG_CMD_BOOTD bootd 937 CONFIG_CMD_BOOTI * ARM64 Linux kernel Image support 938 CONFIG_CMD_CACHE * icache, dcache 939 CONFIG_CMD_CLK * clock command support 940 CONFIG_CMD_CONSOLE coninfo 941 CONFIG_CMD_CRC32 * crc32 942 CONFIG_CMD_DATE * support for RTC, date/time... 943 CONFIG_CMD_DHCP * DHCP support 944 CONFIG_CMD_DIAG * Diagnostics 945 CONFIG_CMD_DS4510 * ds4510 I2C gpio commands 946 CONFIG_CMD_DS4510_INFO * ds4510 I2C info command 947 CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd 948 CONFIG_CMD_DS4510_RST * ds4510 I2C rst command 949 CONFIG_CMD_DTT * Digital Therm and Thermostat 950 CONFIG_CMD_ECHO echo arguments 951 CONFIG_CMD_EDITENV edit env variable 952 CONFIG_CMD_EEPROM * EEPROM read/write support 953 CONFIG_CMD_EEPROM_LAYOUT* EEPROM layout aware commands 954 CONFIG_CMD_ELF * bootelf, bootvx 955 CONFIG_CMD_ENV_CALLBACK * display details about env callbacks 956 CONFIG_CMD_ENV_FLAGS * display details about env flags 957 CONFIG_CMD_ENV_EXISTS * check existence of env variable 958 CONFIG_CMD_EXPORTENV * export the environment 959 CONFIG_CMD_EXT2 * ext2 command support 960 CONFIG_CMD_EXT4 * ext4 command support 961 CONFIG_CMD_FS_GENERIC * filesystem commands (e.g. load, ls) 962 that work for multiple fs types 963 CONFIG_CMD_FS_UUID * Look up a filesystem UUID 964 CONFIG_CMD_SAVEENV saveenv 965 CONFIG_CMD_FDC * Floppy Disk Support 966 CONFIG_CMD_FAT * FAT command support 967 CONFIG_CMD_FLASH flinfo, erase, protect 968 CONFIG_CMD_FPGA FPGA device initialization support 969 CONFIG_CMD_FUSE * Device fuse support 970 CONFIG_CMD_GETTIME * Get time since boot 971 CONFIG_CMD_GO * the 'go' command (exec code) 972 CONFIG_CMD_GREPENV * search environment 973 CONFIG_CMD_HASH * calculate hash / digest 974 CONFIG_CMD_I2C * I2C serial bus support 975 CONFIG_CMD_IDE * IDE harddisk support 976 CONFIG_CMD_IMI iminfo 977 CONFIG_CMD_IMLS List all images found in NOR flash 978 CONFIG_CMD_IMLS_NAND * List all images found in NAND flash 979 CONFIG_CMD_IMMAP * IMMR dump support 980 CONFIG_CMD_IOTRACE * I/O tracing for debugging 981 CONFIG_CMD_IMPORTENV * import an environment 982 CONFIG_CMD_INI * import data from an ini file into the env 983 CONFIG_CMD_IRQ * irqinfo 984 CONFIG_CMD_ITEST Integer/string test of 2 values 985 CONFIG_CMD_JFFS2 * JFFS2 Support 986 CONFIG_CMD_KGDB * kgdb 987 CONFIG_CMD_LDRINFO * ldrinfo (display Blackfin loader) 988 CONFIG_CMD_LINK_LOCAL * link-local IP address auto-configuration 989 (169.254.*.*) 990 CONFIG_CMD_LOADB loadb 991 CONFIG_CMD_LOADS loads 992 CONFIG_CMD_MD5SUM * print md5 message digest 993 (requires CONFIG_CMD_MEMORY and CONFIG_MD5) 994 CONFIG_CMD_MEMINFO * Display detailed memory information 995 CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base, 996 loop, loopw 997 CONFIG_CMD_MEMTEST * mtest 998 CONFIG_CMD_MISC Misc functions like sleep etc 999 CONFIG_CMD_MMC * MMC memory mapped support 1000 CONFIG_CMD_MII * MII utility commands 1001 CONFIG_CMD_MTDPARTS * MTD partition support 1002 CONFIG_CMD_NAND * NAND support 1003 CONFIG_CMD_NET bootp, tftpboot, rarpboot 1004 CONFIG_CMD_NFS NFS support 1005 CONFIG_CMD_PCA953X * PCA953x I2C gpio commands 1006 CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command 1007 CONFIG_CMD_PCI * pciinfo 1008 CONFIG_CMD_PCMCIA * PCMCIA support 1009 CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network 1010 host 1011 CONFIG_CMD_PORTIO * Port I/O 1012 CONFIG_CMD_READ * Read raw data from partition 1013 CONFIG_CMD_REGINFO * Register dump 1014 CONFIG_CMD_RUN run command in env variable 1015 CONFIG_CMD_SANDBOX * sb command to access sandbox features 1016 CONFIG_CMD_SAVES * save S record dump 1017 CONFIG_SCSI * SCSI Support 1018 CONFIG_CMD_SDRAM * print SDRAM configuration information 1019 (requires CONFIG_CMD_I2C) 1020 CONFIG_CMD_SETGETDCR Support for DCR Register access 1021 (4xx only) 1022 CONFIG_CMD_SF * Read/write/erase SPI NOR flash 1023 CONFIG_CMD_SHA1SUM * print sha1 memory digest 1024 (requires CONFIG_CMD_MEMORY) 1025 CONFIG_CMD_SOFTSWITCH * Soft switch setting command for BF60x 1026 CONFIG_CMD_SOURCE "source" command Support 1027 CONFIG_CMD_SPI * SPI serial bus support 1028 CONFIG_CMD_TFTPSRV * TFTP transfer in server mode 1029 CONFIG_CMD_TFTPPUT * TFTP put command (upload) 1030 CONFIG_CMD_TIME * run command and report execution time (ARM specific) 1031 CONFIG_CMD_TIMER * access to the system tick timer 1032 CONFIG_CMD_USB * USB support 1033 CONFIG_CMD_CDP * Cisco Discover Protocol support 1034 CONFIG_CMD_MFSL * Microblaze FSL support 1035 CONFIG_CMD_XIMG Load part of Multi Image 1036 CONFIG_CMD_UUID * Generate random UUID or GUID string 1037 1038 EXAMPLE: If you want all functions except of network 1039 support you can write: 1040 1041 #include "config_cmd_all.h" 1042 #undef CONFIG_CMD_NET 1043 1044 Other Commands: 1045 fdt (flattened device tree) command: CONFIG_OF_LIBFDT 1046 1047 Note: Don't enable the "icache" and "dcache" commands 1048 (configuration option CONFIG_CMD_CACHE) unless you know 1049 what you (and your U-Boot users) are doing. Data 1050 cache cannot be enabled on systems like the 8xx or 1051 8260 (where accesses to the IMMR region must be 1052 uncached), and it cannot be disabled on all other 1053 systems where we (mis-) use the data cache to hold an 1054 initial stack and some data. 1055 1056 1057 XXX - this list needs to get updated! 1058 1059- Removal of commands 1060 If no commands are needed to boot, you can disable 1061 CONFIG_CMDLINE to remove them. In this case, the command line 1062 will not be available, and when U-Boot wants to execute the 1063 boot command (on start-up) it will call board_run_command() 1064 instead. This can reduce image size significantly for very 1065 simple boot procedures. 1066 1067- Regular expression support: 1068 CONFIG_REGEX 1069 If this variable is defined, U-Boot is linked against 1070 the SLRE (Super Light Regular Expression) library, 1071 which adds regex support to some commands, as for 1072 example "env grep" and "setexpr". 1073 1074- Device tree: 1075 CONFIG_OF_CONTROL 1076 If this variable is defined, U-Boot will use a device tree 1077 to configure its devices, instead of relying on statically 1078 compiled #defines in the board file. This option is 1079 experimental and only available on a few boards. The device 1080 tree is available in the global data as gd->fdt_blob. 1081 1082 U-Boot needs to get its device tree from somewhere. This can 1083 be done using one of the two options below: 1084 1085 CONFIG_OF_EMBED 1086 If this variable is defined, U-Boot will embed a device tree 1087 binary in its image. This device tree file should be in the 1088 board directory and called <soc>-<board>.dts. The binary file 1089 is then picked up in board_init_f() and made available through 1090 the global data structure as gd->blob. 1091 1092 CONFIG_OF_SEPARATE 1093 If this variable is defined, U-Boot will build a device tree 1094 binary. It will be called u-boot.dtb. Architecture-specific 1095 code will locate it at run-time. Generally this works by: 1096 1097 cat u-boot.bin u-boot.dtb >image.bin 1098 1099 and in fact, U-Boot does this for you, creating a file called 1100 u-boot-dtb.bin which is useful in the common case. You can 1101 still use the individual files if you need something more 1102 exotic. 1103 1104- Watchdog: 1105 CONFIG_WATCHDOG 1106 If this variable is defined, it enables watchdog 1107 support for the SoC. There must be support in the SoC 1108 specific code for a watchdog. For the 8xx and 8260 1109 CPUs, the SIU Watchdog feature is enabled in the SYPCR 1110 register. When supported for a specific SoC is 1111 available, then no further board specific code should 1112 be needed to use it. 1113 1114 CONFIG_HW_WATCHDOG 1115 When using a watchdog circuitry external to the used 1116 SoC, then define this variable and provide board 1117 specific code for the "hw_watchdog_reset" function. 1118 1119 CONFIG_AT91_HW_WDT_TIMEOUT 1120 specify the timeout in seconds. default 2 seconds. 1121 1122- U-Boot Version: 1123 CONFIG_VERSION_VARIABLE 1124 If this variable is defined, an environment variable 1125 named "ver" is created by U-Boot showing the U-Boot 1126 version as printed by the "version" command. 1127 Any change to this variable will be reverted at the 1128 next reset. 1129 1130- Real-Time Clock: 1131 1132 When CONFIG_CMD_DATE is selected, the type of the RTC 1133 has to be selected, too. Define exactly one of the 1134 following options: 1135 1136 CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx 1137 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC 1138 CONFIG_RTC_MC13XXX - use MC13783 or MC13892 RTC 1139 CONFIG_RTC_MC146818 - use MC146818 RTC 1140 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC 1141 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC 1142 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC 1143 CONFIG_RTC_DS1339 - use Maxim, Inc. DS1339 RTC 1144 CONFIG_RTC_DS164x - use Dallas DS164x RTC 1145 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC 1146 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC 1147 CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337 1148 CONFIG_SYS_RV3029_TCR - enable trickle charger on 1149 RV3029 RTC. 1150 1151 Note that if the RTC uses I2C, then the I2C interface 1152 must also be configured. See I2C Support, below. 1153 1154- GPIO Support: 1155 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO 1156 1157 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of 1158 chip-ngpio pairs that tell the PCA953X driver the number of 1159 pins supported by a particular chip. 1160 1161 Note that if the GPIO device uses I2C, then the I2C interface 1162 must also be configured. See I2C Support, below. 1163 1164- I/O tracing: 1165 When CONFIG_IO_TRACE is selected, U-Boot intercepts all I/O 1166 accesses and can checksum them or write a list of them out 1167 to memory. See the 'iotrace' command for details. This is 1168 useful for testing device drivers since it can confirm that 1169 the driver behaves the same way before and after a code 1170 change. Currently this is supported on sandbox and arm. To 1171 add support for your architecture, add '#include <iotrace.h>' 1172 to the bottom of arch/<arch>/include/asm/io.h and test. 1173 1174 Example output from the 'iotrace stats' command is below. 1175 Note that if the trace buffer is exhausted, the checksum will 1176 still continue to operate. 1177 1178 iotrace is enabled 1179 Start: 10000000 (buffer start address) 1180 Size: 00010000 (buffer size) 1181 Offset: 00000120 (current buffer offset) 1182 Output: 10000120 (start + offset) 1183 Count: 00000018 (number of trace records) 1184 CRC32: 9526fb66 (CRC32 of all trace records) 1185 1186- Timestamp Support: 1187 1188 When CONFIG_TIMESTAMP is selected, the timestamp 1189 (date and time) of an image is printed by image 1190 commands like bootm or iminfo. This option is 1191 automatically enabled when you select CONFIG_CMD_DATE . 1192 1193- Partition Labels (disklabels) Supported: 1194 Zero or more of the following: 1195 CONFIG_MAC_PARTITION Apple's MacOS partition table. 1196 CONFIG_DOS_PARTITION MS Dos partition table, traditional on the 1197 Intel architecture, USB sticks, etc. 1198 CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc. 1199 CONFIG_EFI_PARTITION GPT partition table, common when EFI is the 1200 bootloader. Note 2TB partition limit; see 1201 disk/part_efi.c 1202 CONFIG_MTD_PARTITIONS Memory Technology Device partition table. 1203 1204 If IDE or SCSI support is enabled (CONFIG_CMD_IDE or 1205 CONFIG_SCSI) you must configure support for at 1206 least one non-MTD partition type as well. 1207 1208- IDE Reset method: 1209 CONFIG_IDE_RESET_ROUTINE - this is defined in several 1210 board configurations files but used nowhere! 1211 1212 CONFIG_IDE_RESET - is this is defined, IDE Reset will 1213 be performed by calling the function 1214 ide_set_reset(int reset) 1215 which has to be defined in a board specific file 1216 1217- ATAPI Support: 1218 CONFIG_ATAPI 1219 1220 Set this to enable ATAPI support. 1221 1222- LBA48 Support 1223 CONFIG_LBA48 1224 1225 Set this to enable support for disks larger than 137GB 1226 Also look at CONFIG_SYS_64BIT_LBA. 1227 Whithout these , LBA48 support uses 32bit variables and will 'only' 1228 support disks up to 2.1TB. 1229 1230 CONFIG_SYS_64BIT_LBA: 1231 When enabled, makes the IDE subsystem use 64bit sector addresses. 1232 Default is 32bit. 1233 1234- SCSI Support: 1235 At the moment only there is only support for the 1236 SYM53C8XX SCSI controller; define 1237 CONFIG_SCSI_SYM53C8XX to enable it. 1238 1239 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and 1240 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID * 1241 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the 1242 maximum numbers of LUNs, SCSI ID's and target 1243 devices. 1244 CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz) 1245 1246 The environment variable 'scsidevs' is set to the number of 1247 SCSI devices found during the last scan. 1248 1249- NETWORK Support (PCI): 1250 CONFIG_E1000 1251 Support for Intel 8254x/8257x gigabit chips. 1252 1253 CONFIG_E1000_SPI 1254 Utility code for direct access to the SPI bus on Intel 8257x. 1255 This does not do anything useful unless you set at least one 1256 of CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC. 1257 1258 CONFIG_E1000_SPI_GENERIC 1259 Allow generic access to the SPI bus on the Intel 8257x, for 1260 example with the "sspi" command. 1261 1262 CONFIG_CMD_E1000 1263 Management command for E1000 devices. When used on devices 1264 with SPI support you can reprogram the EEPROM from U-Boot. 1265 1266 CONFIG_EEPRO100 1267 Support for Intel 82557/82559/82559ER chips. 1268 Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM 1269 write routine for first time initialisation. 1270 1271 CONFIG_TULIP 1272 Support for Digital 2114x chips. 1273 Optional CONFIG_TULIP_SELECT_MEDIA for board specific 1274 modem chip initialisation (KS8761/QS6611). 1275 1276 CONFIG_NATSEMI 1277 Support for National dp83815 chips. 1278 1279 CONFIG_NS8382X 1280 Support for National dp8382[01] gigabit chips. 1281 1282- NETWORK Support (other): 1283 1284 CONFIG_DRIVER_AT91EMAC 1285 Support for AT91RM9200 EMAC. 1286 1287 CONFIG_RMII 1288 Define this to use reduced MII inteface 1289 1290 CONFIG_DRIVER_AT91EMAC_QUIET 1291 If this defined, the driver is quiet. 1292 The driver doen't show link status messages. 1293 1294 CONFIG_CALXEDA_XGMAC 1295 Support for the Calxeda XGMAC device 1296 1297 CONFIG_LAN91C96 1298 Support for SMSC's LAN91C96 chips. 1299 1300 CONFIG_LAN91C96_USE_32_BIT 1301 Define this to enable 32 bit addressing 1302 1303 CONFIG_SMC91111 1304 Support for SMSC's LAN91C111 chip 1305 1306 CONFIG_SMC91111_BASE 1307 Define this to hold the physical address 1308 of the device (I/O space) 1309 1310 CONFIG_SMC_USE_32_BIT 1311 Define this if data bus is 32 bits 1312 1313 CONFIG_SMC_USE_IOFUNCS 1314 Define this to use i/o functions instead of macros 1315 (some hardware wont work with macros) 1316 1317 CONFIG_DRIVER_TI_EMAC 1318 Support for davinci emac 1319 1320 CONFIG_SYS_DAVINCI_EMAC_PHY_COUNT 1321 Define this if you have more then 3 PHYs. 1322 1323 CONFIG_FTGMAC100 1324 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet 1325 1326 CONFIG_FTGMAC100_EGIGA 1327 Define this to use GE link update with gigabit PHY. 1328 Define this if FTGMAC100 is connected to gigabit PHY. 1329 If your system has 10/100 PHY only, it might not occur 1330 wrong behavior. Because PHY usually return timeout or 1331 useless data when polling gigabit status and gigabit 1332 control registers. This behavior won't affect the 1333 correctnessof 10/100 link speed update. 1334 1335 CONFIG_SMC911X 1336 Support for SMSC's LAN911x and LAN921x chips 1337 1338 CONFIG_SMC911X_BASE 1339 Define this to hold the physical address 1340 of the device (I/O space) 1341 1342 CONFIG_SMC911X_32_BIT 1343 Define this if data bus is 32 bits 1344 1345 CONFIG_SMC911X_16_BIT 1346 Define this if data bus is 16 bits. If your processor 1347 automatically converts one 32 bit word to two 16 bit 1348 words you may also try CONFIG_SMC911X_32_BIT. 1349 1350 CONFIG_SH_ETHER 1351 Support for Renesas on-chip Ethernet controller 1352 1353 CONFIG_SH_ETHER_USE_PORT 1354 Define the number of ports to be used 1355 1356 CONFIG_SH_ETHER_PHY_ADDR 1357 Define the ETH PHY's address 1358 1359 CONFIG_SH_ETHER_CACHE_WRITEBACK 1360 If this option is set, the driver enables cache flush. 1361 1362- PWM Support: 1363 CONFIG_PWM_IMX 1364 Support for PWM modul on the imx6. 1365 1366- TPM Support: 1367 CONFIG_TPM 1368 Support TPM devices. 1369 1370 CONFIG_TPM_TIS_INFINEON 1371 Support for Infineon i2c bus TPM devices. Only one device 1372 per system is supported at this time. 1373 1374 CONFIG_TPM_TIS_I2C_BURST_LIMITATION 1375 Define the burst count bytes upper limit 1376 1377 CONFIG_TPM_ST33ZP24 1378 Support for STMicroelectronics TPM devices. Requires DM_TPM support. 1379 1380 CONFIG_TPM_ST33ZP24_I2C 1381 Support for STMicroelectronics ST33ZP24 I2C devices. 1382 Requires TPM_ST33ZP24 and I2C. 1383 1384 CONFIG_TPM_ST33ZP24_SPI 1385 Support for STMicroelectronics ST33ZP24 SPI devices. 1386 Requires TPM_ST33ZP24 and SPI. 1387 1388 CONFIG_TPM_ATMEL_TWI 1389 Support for Atmel TWI TPM device. Requires I2C support. 1390 1391 CONFIG_TPM_TIS_LPC 1392 Support for generic parallel port TPM devices. Only one device 1393 per system is supported at this time. 1394 1395 CONFIG_TPM_TIS_BASE_ADDRESS 1396 Base address where the generic TPM device is mapped 1397 to. Contemporary x86 systems usually map it at 1398 0xfed40000. 1399 1400 CONFIG_CMD_TPM 1401 Add tpm monitor functions. 1402 Requires CONFIG_TPM. If CONFIG_TPM_AUTH_SESSIONS is set, also 1403 provides monitor access to authorized functions. 1404 1405 CONFIG_TPM 1406 Define this to enable the TPM support library which provides 1407 functional interfaces to some TPM commands. 1408 Requires support for a TPM device. 1409 1410 CONFIG_TPM_AUTH_SESSIONS 1411 Define this to enable authorized functions in the TPM library. 1412 Requires CONFIG_TPM and CONFIG_SHA1. 1413 1414- USB Support: 1415 At the moment only the UHCI host controller is 1416 supported (PIP405, MIP405, MPC5200); define 1417 CONFIG_USB_UHCI to enable it. 1418 define CONFIG_USB_KEYBOARD to enable the USB Keyboard 1419 and define CONFIG_USB_STORAGE to enable the USB 1420 storage devices. 1421 Note: 1422 Supported are USB Keyboards and USB Floppy drives 1423 (TEAC FD-05PUB). 1424 MPC5200 USB requires additional defines: 1425 CONFIG_USB_CLOCK 1426 for 528 MHz Clock: 0x0001bbbb 1427 CONFIG_PSC3_USB 1428 for USB on PSC3 1429 CONFIG_USB_CONFIG 1430 for differential drivers: 0x00001000 1431 for single ended drivers: 0x00005000 1432 for differential drivers on PSC3: 0x00000100 1433 for single ended drivers on PSC3: 0x00004100 1434 CONFIG_SYS_USB_EVENT_POLL 1435 May be defined to allow interrupt polling 1436 instead of using asynchronous interrupts 1437 1438 CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the 1439 txfilltuning field in the EHCI controller on reset. 1440 1441 CONFIG_USB_DWC2_REG_ADDR the physical CPU address of the DWC2 1442 HW module registers. 1443 1444- USB Device: 1445 Define the below if you wish to use the USB console. 1446 Once firmware is rebuilt from a serial console issue the 1447 command "setenv stdin usbtty; setenv stdout usbtty" and 1448 attach your USB cable. The Unix command "dmesg" should print 1449 it has found a new device. The environment variable usbtty 1450 can be set to gserial or cdc_acm to enable your device to 1451 appear to a USB host as a Linux gserial device or a 1452 Common Device Class Abstract Control Model serial device. 1453 If you select usbtty = gserial you should be able to enumerate 1454 a Linux host by 1455 # modprobe usbserial vendor=0xVendorID product=0xProductID 1456 else if using cdc_acm, simply setting the environment 1457 variable usbtty to be cdc_acm should suffice. The following 1458 might be defined in YourBoardName.h 1459 1460 CONFIG_USB_DEVICE 1461 Define this to build a UDC device 1462 1463 CONFIG_USB_TTY 1464 Define this to have a tty type of device available to 1465 talk to the UDC device 1466 1467 CONFIG_USBD_HS 1468 Define this to enable the high speed support for usb 1469 device and usbtty. If this feature is enabled, a routine 1470 int is_usbd_high_speed(void) 1471 also needs to be defined by the driver to dynamically poll 1472 whether the enumeration has succeded at high speed or full 1473 speed. 1474 1475 CONFIG_SYS_CONSOLE_IS_IN_ENV 1476 Define this if you want stdin, stdout &/or stderr to 1477 be set to usbtty. 1478 1479 mpc8xx: 1480 CONFIG_SYS_USB_EXTC_CLK 0xBLAH 1481 Derive USB clock from external clock "blah" 1482 - CONFIG_SYS_USB_EXTC_CLK 0x02 1483 1484 If you have a USB-IF assigned VendorID then you may wish to 1485 define your own vendor specific values either in BoardName.h 1486 or directly in usbd_vendor_info.h. If you don't define 1487 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME, 1488 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot 1489 should pretend to be a Linux device to it's target host. 1490 1491 CONFIG_USBD_MANUFACTURER 1492 Define this string as the name of your company for 1493 - CONFIG_USBD_MANUFACTURER "my company" 1494 1495 CONFIG_USBD_PRODUCT_NAME 1496 Define this string as the name of your product 1497 - CONFIG_USBD_PRODUCT_NAME "acme usb device" 1498 1499 CONFIG_USBD_VENDORID 1500 Define this as your assigned Vendor ID from the USB 1501 Implementors Forum. This *must* be a genuine Vendor ID 1502 to avoid polluting the USB namespace. 1503 - CONFIG_USBD_VENDORID 0xFFFF 1504 1505 CONFIG_USBD_PRODUCTID 1506 Define this as the unique Product ID 1507 for your device 1508 - CONFIG_USBD_PRODUCTID 0xFFFF 1509 1510- ULPI Layer Support: 1511 The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via 1512 the generic ULPI layer. The generic layer accesses the ULPI PHY 1513 via the platform viewport, so you need both the genric layer and 1514 the viewport enabled. Currently only Chipidea/ARC based 1515 viewport is supported. 1516 To enable the ULPI layer support, define CONFIG_USB_ULPI and 1517 CONFIG_USB_ULPI_VIEWPORT in your board configuration file. 1518 If your ULPI phy needs a different reference clock than the 1519 standard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to 1520 the appropriate value in Hz. 1521 1522- MMC Support: 1523 The MMC controller on the Intel PXA is supported. To 1524 enable this define CONFIG_MMC. The MMC can be 1525 accessed from the boot prompt by mapping the device 1526 to physical memory similar to flash. Command line is 1527 enabled with CONFIG_CMD_MMC. The MMC driver also works with 1528 the FAT fs. This is enabled with CONFIG_CMD_FAT. 1529 1530 CONFIG_SH_MMCIF 1531 Support for Renesas on-chip MMCIF controller 1532 1533 CONFIG_SH_MMCIF_ADDR 1534 Define the base address of MMCIF registers 1535 1536 CONFIG_SH_MMCIF_CLK 1537 Define the clock frequency for MMCIF 1538 1539 CONFIG_GENERIC_MMC 1540 Enable the generic MMC driver 1541 1542 CONFIG_SUPPORT_EMMC_BOOT 1543 Enable some additional features of the eMMC boot partitions. 1544 1545 CONFIG_SUPPORT_EMMC_RPMB 1546 Enable the commands for reading, writing and programming the 1547 key for the Replay Protection Memory Block partition in eMMC. 1548 1549- USB Device Firmware Update (DFU) class support: 1550 CONFIG_USB_FUNCTION_DFU 1551 This enables the USB portion of the DFU USB class 1552 1553 CONFIG_CMD_DFU 1554 This enables the command "dfu" which is used to have 1555 U-Boot create a DFU class device via USB. This command 1556 requires that the "dfu_alt_info" environment variable be 1557 set and define the alt settings to expose to the host. 1558 1559 CONFIG_DFU_MMC 1560 This enables support for exposing (e)MMC devices via DFU. 1561 1562 CONFIG_DFU_NAND 1563 This enables support for exposing NAND devices via DFU. 1564 1565 CONFIG_DFU_RAM 1566 This enables support for exposing RAM via DFU. 1567 Note: DFU spec refer to non-volatile memory usage, but 1568 allow usages beyond the scope of spec - here RAM usage, 1569 one that would help mostly the developer. 1570 1571 CONFIG_SYS_DFU_DATA_BUF_SIZE 1572 Dfu transfer uses a buffer before writing data to the 1573 raw storage device. Make the size (in bytes) of this buffer 1574 configurable. The size of this buffer is also configurable 1575 through the "dfu_bufsiz" environment variable. 1576 1577 CONFIG_SYS_DFU_MAX_FILE_SIZE 1578 When updating files rather than the raw storage device, 1579 we use a static buffer to copy the file into and then write 1580 the buffer once we've been given the whole file. Define 1581 this to the maximum filesize (in bytes) for the buffer. 1582 Default is 4 MiB if undefined. 1583 1584 DFU_DEFAULT_POLL_TIMEOUT 1585 Poll timeout [ms], is the timeout a device can send to the 1586 host. The host must wait for this timeout before sending 1587 a subsequent DFU_GET_STATUS request to the device. 1588 1589 DFU_MANIFEST_POLL_TIMEOUT 1590 Poll timeout [ms], which the device sends to the host when 1591 entering dfuMANIFEST state. Host waits this timeout, before 1592 sending again an USB request to the device. 1593 1594- USB Device Android Fastboot support: 1595 CONFIG_USB_FUNCTION_FASTBOOT 1596 This enables the USB part of the fastboot gadget 1597 1598 CONFIG_CMD_FASTBOOT 1599 This enables the command "fastboot" which enables the Android 1600 fastboot mode for the platform's USB device. Fastboot is a USB 1601 protocol for downloading images, flashing and device control 1602 used on Android devices. 1603 See doc/README.android-fastboot for more information. 1604 1605 CONFIG_ANDROID_BOOT_IMAGE 1606 This enables support for booting images which use the Android 1607 image format header. 1608 1609 CONFIG_FASTBOOT_BUF_ADDR 1610 The fastboot protocol requires a large memory buffer for 1611 downloads. Define this to the starting RAM address to use for 1612 downloaded images. 1613 1614 CONFIG_FASTBOOT_BUF_SIZE 1615 The fastboot protocol requires a large memory buffer for 1616 downloads. This buffer should be as large as possible for a 1617 platform. Define this to the size available RAM for fastboot. 1618 1619 CONFIG_FASTBOOT_FLASH 1620 The fastboot protocol includes a "flash" command for writing 1621 the downloaded image to a non-volatile storage device. Define 1622 this to enable the "fastboot flash" command. 1623 1624 CONFIG_FASTBOOT_FLASH_MMC_DEV 1625 The fastboot "flash" command requires additional information 1626 regarding the non-volatile storage device. Define this to 1627 the eMMC device that fastboot should use to store the image. 1628 1629 CONFIG_FASTBOOT_GPT_NAME 1630 The fastboot "flash" command supports writing the downloaded 1631 image to the Protective MBR and the Primary GUID Partition 1632 Table. (Additionally, this downloaded image is post-processed 1633 to generate and write the Backup GUID Partition Table.) 1634 This occurs when the specified "partition name" on the 1635 "fastboot flash" command line matches this value. 1636 The default is "gpt" if undefined. 1637 1638 CONFIG_FASTBOOT_MBR_NAME 1639 The fastboot "flash" command supports writing the downloaded 1640 image to DOS MBR. 1641 This occurs when the "partition name" specified on the 1642 "fastboot flash" command line matches this value. 1643 If not defined the default value "mbr" is used. 1644 1645- Journaling Flash filesystem support: 1646 CONFIG_JFFS2_NAND 1647 Define these for a default partition on a NAND device 1648 1649 CONFIG_SYS_JFFS2_FIRST_SECTOR, 1650 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS 1651 Define these for a default partition on a NOR device 1652 1653- FAT(File Allocation Table) filesystem write function support: 1654 CONFIG_FAT_WRITE 1655 1656 Define this to enable support for saving memory data as a 1657 file in FAT formatted partition. 1658 1659 This will also enable the command "fatwrite" enabling the 1660 user to write files to FAT. 1661 1662CBFS (Coreboot Filesystem) support 1663 CONFIG_CMD_CBFS 1664 1665 Define this to enable support for reading from a Coreboot 1666 filesystem. Available commands are cbfsinit, cbfsinfo, cbfsls 1667 and cbfsload. 1668 1669- FAT(File Allocation Table) filesystem cluster size: 1670 CONFIG_FS_FAT_MAX_CLUSTSIZE 1671 1672 Define the max cluster size for fat operations else 1673 a default value of 65536 will be defined. 1674 1675- Keyboard Support: 1676 See Kconfig help for available keyboard drivers. 1677 1678 CONFIG_KEYBOARD 1679 1680 Define this to enable a custom keyboard support. 1681 This simply calls drv_keyboard_init() which must be 1682 defined in your board-specific files. This option is deprecated 1683 and is only used by novena. For new boards, use driver model 1684 instead. 1685 1686- Video support: 1687 CONFIG_VIDEO 1688 1689 Define this to enable video support (for output to 1690 video). 1691 1692 CONFIG_VIDEO_CT69000 1693 1694 Enable Chips & Technologies 69000 Video chip 1695 1696 CONFIG_VIDEO_SMI_LYNXEM 1697 Enable Silicon Motion SMI 712/710/810 Video chip. The 1698 video output is selected via environment 'videoout' 1699 (1 = LCD and 2 = CRT). If videoout is undefined, CRT is 1700 assumed. 1701 1702 For the CT69000 and SMI_LYNXEM drivers, videomode is 1703 selected via environment 'videomode'. Two different ways 1704 are possible: 1705 - "videomode=num" 'num' is a standard LiLo mode numbers. 1706 Following standard modes are supported (* is default): 1707 1708 Colors 640x480 800x600 1024x768 1152x864 1280x1024 1709 -------------+--------------------------------------------- 1710 8 bits | 0x301* 0x303 0x305 0x161 0x307 1711 15 bits | 0x310 0x313 0x316 0x162 0x319 1712 16 bits | 0x311 0x314 0x317 0x163 0x31A 1713 24 bits | 0x312 0x315 0x318 ? 0x31B 1714 -------------+--------------------------------------------- 1715 (i.e. setenv videomode 317; saveenv; reset;) 1716 1717 - "videomode=bootargs" all the video parameters are parsed 1718 from the bootargs. (See drivers/video/videomodes.c) 1719 1720 1721 CONFIG_VIDEO_SED13806 1722 Enable Epson SED13806 driver. This driver supports 8bpp 1723 and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP 1724 or CONFIG_VIDEO_SED13806_16BPP 1725 1726 CONFIG_FSL_DIU_FB 1727 Enable the Freescale DIU video driver. Reference boards for 1728 SOCs that have a DIU should define this macro to enable DIU 1729 support, and should also define these other macros: 1730 1731 CONFIG_SYS_DIU_ADDR 1732 CONFIG_VIDEO 1733 CONFIG_CMD_BMP 1734 CONFIG_CFB_CONSOLE 1735 CONFIG_VIDEO_SW_CURSOR 1736 CONFIG_VGA_AS_SINGLE_DEVICE 1737 CONFIG_VIDEO_LOGO 1738 CONFIG_VIDEO_BMP_LOGO 1739 1740 The DIU driver will look for the 'video-mode' environment 1741 variable, and if defined, enable the DIU as a console during 1742 boot. See the documentation file doc/README.video for a 1743 description of this variable. 1744 1745- LCD Support: CONFIG_LCD 1746 1747 Define this to enable LCD support (for output to LCD 1748 display); also select one of the supported displays 1749 by defining one of these: 1750 1751 CONFIG_ATMEL_LCD: 1752 1753 HITACHI TX09D70VM1CCA, 3.5", 240x320. 1754 1755 CONFIG_NEC_NL6448AC33: 1756 1757 NEC NL6448AC33-18. Active, color, single scan. 1758 1759 CONFIG_NEC_NL6448BC20 1760 1761 NEC NL6448BC20-08. 6.5", 640x480. 1762 Active, color, single scan. 1763 1764 CONFIG_NEC_NL6448BC33_54 1765 1766 NEC NL6448BC33-54. 10.4", 640x480. 1767 Active, color, single scan. 1768 1769 CONFIG_SHARP_16x9 1770 1771 Sharp 320x240. Active, color, single scan. 1772 It isn't 16x9, and I am not sure what it is. 1773 1774 CONFIG_SHARP_LQ64D341 1775 1776 Sharp LQ64D341 display, 640x480. 1777 Active, color, single scan. 1778 1779 CONFIG_HLD1045 1780 1781 HLD1045 display, 640x480. 1782 Active, color, single scan. 1783 1784 CONFIG_OPTREX_BW 1785 1786 Optrex CBL50840-2 NF-FW 99 22 M5 1787 or 1788 Hitachi LMG6912RPFC-00T 1789 or 1790 Hitachi SP14Q002 1791 1792 320x240. Black & white. 1793 1794 Normally display is black on white background; define 1795 CONFIG_SYS_WHITE_ON_BLACK to get it inverted. 1796 1797 CONFIG_LCD_ALIGNMENT 1798 1799 Normally the LCD is page-aligned (typically 4KB). If this is 1800 defined then the LCD will be aligned to this value instead. 1801 For ARM it is sometimes useful to use MMU_SECTION_SIZE 1802 here, since it is cheaper to change data cache settings on 1803 a per-section basis. 1804 1805 CONFIG_CONSOLE_SCROLL_LINES 1806 1807 When the console need to be scrolled, this is the number of 1808 lines to scroll by. It defaults to 1. Increasing this makes 1809 the console jump but can help speed up operation when scrolling 1810 is slow. 1811 1812 CONFIG_LCD_ROTATION 1813 1814 Sometimes, for example if the display is mounted in portrait 1815 mode or even if it's mounted landscape but rotated by 180degree, 1816 we need to rotate our content of the display relative to the 1817 framebuffer, so that user can read the messages which are 1818 printed out. 1819 Once CONFIG_LCD_ROTATION is defined, the lcd_console will be 1820 initialized with a given rotation from "vl_rot" out of 1821 "vidinfo_t" which is provided by the board specific code. 1822 The value for vl_rot is coded as following (matching to 1823 fbcon=rotate:<n> linux-kernel commandline): 1824 0 = no rotation respectively 0 degree 1825 1 = 90 degree rotation 1826 2 = 180 degree rotation 1827 3 = 270 degree rotation 1828 1829 If CONFIG_LCD_ROTATION is not defined, the console will be 1830 initialized with 0degree rotation. 1831 1832 CONFIG_LCD_BMP_RLE8 1833 1834 Support drawing of RLE8-compressed bitmaps on the LCD. 1835 1836 CONFIG_I2C_EDID 1837 1838 Enables an 'i2c edid' command which can read EDID 1839 information over I2C from an attached LCD display. 1840 1841- Splash Screen Support: CONFIG_SPLASH_SCREEN 1842 1843 If this option is set, the environment is checked for 1844 a variable "splashimage". If found, the usual display 1845 of logo, copyright and system information on the LCD 1846 is suppressed and the BMP image at the address 1847 specified in "splashimage" is loaded instead. The 1848 console is redirected to the "nulldev", too. This 1849 allows for a "silent" boot where a splash screen is 1850 loaded very quickly after power-on. 1851 1852 CONFIG_SPLASHIMAGE_GUARD 1853 1854 If this option is set, then U-Boot will prevent the environment 1855 variable "splashimage" from being set to a problematic address 1856 (see doc/README.displaying-bmps). 1857 This option is useful for targets where, due to alignment 1858 restrictions, an improperly aligned BMP image will cause a data 1859 abort. If you think you will not have problems with unaligned 1860 accesses (for example because your toolchain prevents them) 1861 there is no need to set this option. 1862 1863 CONFIG_SPLASH_SCREEN_ALIGN 1864 1865 If this option is set the splash image can be freely positioned 1866 on the screen. Environment variable "splashpos" specifies the 1867 position as "x,y". If a positive number is given it is used as 1868 number of pixel from left/top. If a negative number is given it 1869 is used as number of pixel from right/bottom. You can also 1870 specify 'm' for centering the image. 1871 1872 Example: 1873 setenv splashpos m,m 1874 => image at center of screen 1875 1876 setenv splashpos 30,20 1877 => image at x = 30 and y = 20 1878 1879 setenv splashpos -10,m 1880 => vertically centered image 1881 at x = dspWidth - bmpWidth - 9 1882 1883- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP 1884 1885 If this option is set, additionally to standard BMP 1886 images, gzipped BMP images can be displayed via the 1887 splashscreen support or the bmp command. 1888 1889- Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8 1890 1891 If this option is set, 8-bit RLE compressed BMP images 1892 can be displayed via the splashscreen support or the 1893 bmp command. 1894 1895- Do compressing for memory range: 1896 CONFIG_CMD_ZIP 1897 1898 If this option is set, it would use zlib deflate method 1899 to compress the specified memory at its best effort. 1900 1901- Compression support: 1902 CONFIG_GZIP 1903 1904 Enabled by default to support gzip compressed images. 1905 1906 CONFIG_BZIP2 1907 1908 If this option is set, support for bzip2 compressed 1909 images is included. If not, only uncompressed and gzip 1910 compressed images are supported. 1911 1912 NOTE: the bzip2 algorithm requires a lot of RAM, so 1913 the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should 1914 be at least 4MB. 1915 1916 CONFIG_LZMA 1917 1918 If this option is set, support for lzma compressed 1919 images is included. 1920 1921 Note: The LZMA algorithm adds between 2 and 4KB of code and it 1922 requires an amount of dynamic memory that is given by the 1923 formula: 1924 1925 (1846 + 768 << (lc + lp)) * sizeof(uint16) 1926 1927 Where lc and lp stand for, respectively, Literal context bits 1928 and Literal pos bits. 1929 1930 This value is upper-bounded by 14MB in the worst case. Anyway, 1931 for a ~4MB large kernel image, we have lc=3 and lp=0 for a 1932 total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is 1933 a very small buffer. 1934 1935 Use the lzmainfo tool to determinate the lc and lp values and 1936 then calculate the amount of needed dynamic memory (ensuring 1937 the appropriate CONFIG_SYS_MALLOC_LEN value). 1938 1939 CONFIG_LZO 1940 1941 If this option is set, support for LZO compressed images 1942 is included. 1943 1944- MII/PHY support: 1945 CONFIG_PHY_ADDR 1946 1947 The address of PHY on MII bus. 1948 1949 CONFIG_PHY_CLOCK_FREQ (ppc4xx) 1950 1951 The clock frequency of the MII bus 1952 1953 CONFIG_PHY_GIGE 1954 1955 If this option is set, support for speed/duplex 1956 detection of gigabit PHY is included. 1957 1958 CONFIG_PHY_RESET_DELAY 1959 1960 Some PHY like Intel LXT971A need extra delay after 1961 reset before any MII register access is possible. 1962 For such PHY, set this option to the usec delay 1963 required. (minimum 300usec for LXT971A) 1964 1965 CONFIG_PHY_CMD_DELAY (ppc4xx) 1966 1967 Some PHY like Intel LXT971A need extra delay after 1968 command issued before MII status register can be read 1969 1970- IP address: 1971 CONFIG_IPADDR 1972 1973 Define a default value for the IP address to use for 1974 the default Ethernet interface, in case this is not 1975 determined through e.g. bootp. 1976 (Environment variable "ipaddr") 1977 1978- Server IP address: 1979 CONFIG_SERVERIP 1980 1981 Defines a default value for the IP address of a TFTP 1982 server to contact when using the "tftboot" command. 1983 (Environment variable "serverip") 1984 1985 CONFIG_KEEP_SERVERADDR 1986 1987 Keeps the server's MAC address, in the env 'serveraddr' 1988 for passing to bootargs (like Linux's netconsole option) 1989 1990- Gateway IP address: 1991 CONFIG_GATEWAYIP 1992 1993 Defines a default value for the IP address of the 1994 default router where packets to other networks are 1995 sent to. 1996 (Environment variable "gatewayip") 1997 1998- Subnet mask: 1999 CONFIG_NETMASK 2000 2001 Defines a default value for the subnet mask (or 2002 routing prefix) which is used to determine if an IP 2003 address belongs to the local subnet or needs to be 2004 forwarded through a router. 2005 (Environment variable "netmask") 2006 2007- Multicast TFTP Mode: 2008 CONFIG_MCAST_TFTP 2009 2010 Defines whether you want to support multicast TFTP as per 2011 rfc-2090; for example to work with atftp. Lets lots of targets 2012 tftp down the same boot image concurrently. Note: the Ethernet 2013 driver in use must provide a function: mcast() to join/leave a 2014 multicast group. 2015 2016- BOOTP Recovery Mode: 2017 CONFIG_BOOTP_RANDOM_DELAY 2018 2019 If you have many targets in a network that try to 2020 boot using BOOTP, you may want to avoid that all 2021 systems send out BOOTP requests at precisely the same 2022 moment (which would happen for instance at recovery 2023 from a power failure, when all systems will try to 2024 boot, thus flooding the BOOTP server. Defining 2025 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be 2026 inserted before sending out BOOTP requests. The 2027 following delays are inserted then: 2028 2029 1st BOOTP request: delay 0 ... 1 sec 2030 2nd BOOTP request: delay 0 ... 2 sec 2031 3rd BOOTP request: delay 0 ... 4 sec 2032 4th and following 2033 BOOTP requests: delay 0 ... 8 sec 2034 2035 CONFIG_BOOTP_ID_CACHE_SIZE 2036 2037 BOOTP packets are uniquely identified using a 32-bit ID. The 2038 server will copy the ID from client requests to responses and 2039 U-Boot will use this to determine if it is the destination of 2040 an incoming response. Some servers will check that addresses 2041 aren't in use before handing them out (usually using an ARP 2042 ping) and therefore take up to a few hundred milliseconds to 2043 respond. Network congestion may also influence the time it 2044 takes for a response to make it back to the client. If that 2045 time is too long, U-Boot will retransmit requests. In order 2046 to allow earlier responses to still be accepted after these 2047 retransmissions, U-Boot's BOOTP client keeps a small cache of 2048 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this 2049 cache. The default is to keep IDs for up to four outstanding 2050 requests. Increasing this will allow U-Boot to accept offers 2051 from a BOOTP client in networks with unusually high latency. 2052 2053- DHCP Advanced Options: 2054 You can fine tune the DHCP functionality by defining 2055 CONFIG_BOOTP_* symbols: 2056 2057 CONFIG_BOOTP_SUBNETMASK 2058 CONFIG_BOOTP_GATEWAY 2059 CONFIG_BOOTP_HOSTNAME 2060 CONFIG_BOOTP_NISDOMAIN 2061 CONFIG_BOOTP_BOOTPATH 2062 CONFIG_BOOTP_BOOTFILESIZE 2063 CONFIG_BOOTP_DNS 2064 CONFIG_BOOTP_DNS2 2065 CONFIG_BOOTP_SEND_HOSTNAME 2066 CONFIG_BOOTP_NTPSERVER 2067 CONFIG_BOOTP_TIMEOFFSET 2068 CONFIG_BOOTP_VENDOREX 2069 CONFIG_BOOTP_MAY_FAIL 2070 2071 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip 2072 environment variable, not the BOOTP server. 2073 2074 CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found 2075 after the configured retry count, the call will fail 2076 instead of starting over. This can be used to fail over 2077 to Link-local IP address configuration if the DHCP server 2078 is not available. 2079 2080 CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS 2081 serverip from a DHCP server, it is possible that more 2082 than one DNS serverip is offered to the client. 2083 If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS 2084 serverip will be stored in the additional environment 2085 variable "dnsip2". The first DNS serverip is always 2086 stored in the variable "dnsip", when CONFIG_BOOTP_DNS 2087 is defined. 2088 2089 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable 2090 to do a dynamic update of a DNS server. To do this, they 2091 need the hostname of the DHCP requester. 2092 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content 2093 of the "hostname" environment variable is passed as 2094 option 12 to the DHCP server. 2095 2096 CONFIG_BOOTP_DHCP_REQUEST_DELAY 2097 2098 A 32bit value in microseconds for a delay between 2099 receiving a "DHCP Offer" and sending the "DHCP Request". 2100 This fixes a problem with certain DHCP servers that don't 2101 respond 100% of the time to a "DHCP request". E.g. On an 2102 AT91RM9200 processor running at 180MHz, this delay needed 2103 to be *at least* 15,000 usec before a Windows Server 2003 2104 DHCP server would reply 100% of the time. I recommend at 2105 least 50,000 usec to be safe. The alternative is to hope 2106 that one of the retries will be successful but note that 2107 the DHCP timeout and retry process takes a longer than 2108 this delay. 2109 2110 - Link-local IP address negotiation: 2111 Negotiate with other link-local clients on the local network 2112 for an address that doesn't require explicit configuration. 2113 This is especially useful if a DHCP server cannot be guaranteed 2114 to exist in all environments that the device must operate. 2115 2116 See doc/README.link-local for more information. 2117 2118 - CDP Options: 2119 CONFIG_CDP_DEVICE_ID 2120 2121 The device id used in CDP trigger frames. 2122 2123 CONFIG_CDP_DEVICE_ID_PREFIX 2124 2125 A two character string which is prefixed to the MAC address 2126 of the device. 2127 2128 CONFIG_CDP_PORT_ID 2129 2130 A printf format string which contains the ascii name of 2131 the port. Normally is set to "eth%d" which sets 2132 eth0 for the first Ethernet, eth1 for the second etc. 2133 2134 CONFIG_CDP_CAPABILITIES 2135 2136 A 32bit integer which indicates the device capabilities; 2137 0x00000010 for a normal host which does not forwards. 2138 2139 CONFIG_CDP_VERSION 2140 2141 An ascii string containing the version of the software. 2142 2143 CONFIG_CDP_PLATFORM 2144 2145 An ascii string containing the name of the platform. 2146 2147 CONFIG_CDP_TRIGGER 2148 2149 A 32bit integer sent on the trigger. 2150 2151 CONFIG_CDP_POWER_CONSUMPTION 2152 2153 A 16bit integer containing the power consumption of the 2154 device in .1 of milliwatts. 2155 2156 CONFIG_CDP_APPLIANCE_VLAN_TYPE 2157 2158 A byte containing the id of the VLAN. 2159 2160- Status LED: CONFIG_STATUS_LED 2161 2162 Several configurations allow to display the current 2163 status using a LED. For instance, the LED will blink 2164 fast while running U-Boot code, stop blinking as 2165 soon as a reply to a BOOTP request was received, and 2166 start blinking slow once the Linux kernel is running 2167 (supported by a status LED driver in the Linux 2168 kernel). Defining CONFIG_STATUS_LED enables this 2169 feature in U-Boot. 2170 2171 Additional options: 2172 2173 CONFIG_GPIO_LED 2174 The status LED can be connected to a GPIO pin. 2175 In such cases, the gpio_led driver can be used as a 2176 status LED backend implementation. Define CONFIG_GPIO_LED 2177 to include the gpio_led driver in the U-Boot binary. 2178 2179 CONFIG_GPIO_LED_INVERTED_TABLE 2180 Some GPIO connected LEDs may have inverted polarity in which 2181 case the GPIO high value corresponds to LED off state and 2182 GPIO low value corresponds to LED on state. 2183 In such cases CONFIG_GPIO_LED_INVERTED_TABLE may be defined 2184 with a list of GPIO LEDs that have inverted polarity. 2185 2186- CAN Support: CONFIG_CAN_DRIVER 2187 2188 Defining CONFIG_CAN_DRIVER enables CAN driver support 2189 on those systems that support this (optional) 2190 feature, like the TQM8xxL modules. 2191 2192- I2C Support: CONFIG_SYS_I2C 2193 2194 This enable the NEW i2c subsystem, and will allow you to use 2195 i2c commands at the u-boot command line (as long as you set 2196 CONFIG_CMD_I2C in CONFIG_COMMANDS) and communicate with i2c 2197 based realtime clock chips or other i2c devices. See 2198 common/cmd_i2c.c for a description of the command line 2199 interface. 2200 2201 ported i2c driver to the new framework: 2202 - drivers/i2c/soft_i2c.c: 2203 - activate first bus with CONFIG_SYS_I2C_SOFT define 2204 CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE 2205 for defining speed and slave address 2206 - activate second bus with I2C_SOFT_DECLARATIONS2 define 2207 CONFIG_SYS_I2C_SOFT_SPEED_2 and CONFIG_SYS_I2C_SOFT_SLAVE_2 2208 for defining speed and slave address 2209 - activate third bus with I2C_SOFT_DECLARATIONS3 define 2210 CONFIG_SYS_I2C_SOFT_SPEED_3 and CONFIG_SYS_I2C_SOFT_SLAVE_3 2211 for defining speed and slave address 2212 - activate fourth bus with I2C_SOFT_DECLARATIONS4 define 2213 CONFIG_SYS_I2C_SOFT_SPEED_4 and CONFIG_SYS_I2C_SOFT_SLAVE_4 2214 for defining speed and slave address 2215 2216 - drivers/i2c/fsl_i2c.c: 2217 - activate i2c driver with CONFIG_SYS_I2C_FSL 2218 define CONFIG_SYS_FSL_I2C_OFFSET for setting the register 2219 offset CONFIG_SYS_FSL_I2C_SPEED for the i2c speed and 2220 CONFIG_SYS_FSL_I2C_SLAVE for the slave addr of the first 2221 bus. 2222 - If your board supports a second fsl i2c bus, define 2223 CONFIG_SYS_FSL_I2C2_OFFSET for the register offset 2224 CONFIG_SYS_FSL_I2C2_SPEED for the speed and 2225 CONFIG_SYS_FSL_I2C2_SLAVE for the slave address of the 2226 second bus. 2227 2228 - drivers/i2c/tegra_i2c.c: 2229 - activate this driver with CONFIG_SYS_I2C_TEGRA 2230 - This driver adds 4 i2c buses with a fix speed from 2231 100000 and the slave addr 0! 2232 2233 - drivers/i2c/ppc4xx_i2c.c 2234 - activate this driver with CONFIG_SYS_I2C_PPC4XX 2235 - CONFIG_SYS_I2C_PPC4XX_CH0 activate hardware channel 0 2236 - CONFIG_SYS_I2C_PPC4XX_CH1 activate hardware channel 1 2237 2238 - drivers/i2c/i2c_mxc.c 2239 - activate this driver with CONFIG_SYS_I2C_MXC 2240 - enable bus 1 with CONFIG_SYS_I2C_MXC_I2C1 2241 - enable bus 2 with CONFIG_SYS_I2C_MXC_I2C2 2242 - enable bus 3 with CONFIG_SYS_I2C_MXC_I2C3 2243 - enable bus 4 with CONFIG_SYS_I2C_MXC_I2C4 2244 - define speed for bus 1 with CONFIG_SYS_MXC_I2C1_SPEED 2245 - define slave for bus 1 with CONFIG_SYS_MXC_I2C1_SLAVE 2246 - define speed for bus 2 with CONFIG_SYS_MXC_I2C2_SPEED 2247 - define slave for bus 2 with CONFIG_SYS_MXC_I2C2_SLAVE 2248 - define speed for bus 3 with CONFIG_SYS_MXC_I2C3_SPEED 2249 - define slave for bus 3 with CONFIG_SYS_MXC_I2C3_SLAVE 2250 - define speed for bus 4 with CONFIG_SYS_MXC_I2C4_SPEED 2251 - define slave for bus 4 with CONFIG_SYS_MXC_I2C4_SLAVE 2252 If those defines are not set, default value is 100000 2253 for speed, and 0 for slave. 2254 2255 - drivers/i2c/rcar_i2c.c: 2256 - activate this driver with CONFIG_SYS_I2C_RCAR 2257 - This driver adds 4 i2c buses 2258 2259 - CONFIG_SYS_RCAR_I2C0_BASE for setting the register channel 0 2260 - CONFIG_SYS_RCAR_I2C0_SPEED for for the speed channel 0 2261 - CONFIG_SYS_RCAR_I2C1_BASE for setting the register channel 1 2262 - CONFIG_SYS_RCAR_I2C1_SPEED for for the speed channel 1 2263 - CONFIG_SYS_RCAR_I2C2_BASE for setting the register channel 2 2264 - CONFIG_SYS_RCAR_I2C2_SPEED for for the speed channel 2 2265 - CONFIG_SYS_RCAR_I2C3_BASE for setting the register channel 3 2266 - CONFIG_SYS_RCAR_I2C3_SPEED for for the speed channel 3 2267 - CONFIF_SYS_RCAR_I2C_NUM_CONTROLLERS for number of i2c buses 2268 2269 - drivers/i2c/sh_i2c.c: 2270 - activate this driver with CONFIG_SYS_I2C_SH 2271 - This driver adds from 2 to 5 i2c buses 2272 2273 - CONFIG_SYS_I2C_SH_BASE0 for setting the register channel 0 2274 - CONFIG_SYS_I2C_SH_SPEED0 for for the speed channel 0 2275 - CONFIG_SYS_I2C_SH_BASE1 for setting the register channel 1 2276 - CONFIG_SYS_I2C_SH_SPEED1 for for the speed channel 1 2277 - CONFIG_SYS_I2C_SH_BASE2 for setting the register channel 2 2278 - CONFIG_SYS_I2C_SH_SPEED2 for for the speed channel 2 2279 - CONFIG_SYS_I2C_SH_BASE3 for setting the register channel 3 2280 - CONFIG_SYS_I2C_SH_SPEED3 for for the speed channel 3 2281 - CONFIG_SYS_I2C_SH_BASE4 for setting the register channel 4 2282 - CONFIG_SYS_I2C_SH_SPEED4 for for the speed channel 4 2283 - CONFIG_SYS_I2C_SH_BASE5 for setting the register channel 5 2284 - CONFIG_SYS_I2C_SH_SPEED5 for for the speed channel 5 2285 - CONFIG_SYS_I2C_SH_NUM_CONTROLLERS for number of i2c buses 2286 2287 - drivers/i2c/omap24xx_i2c.c 2288 - activate this driver with CONFIG_SYS_I2C_OMAP24XX 2289 - CONFIG_SYS_OMAP24_I2C_SPEED speed channel 0 2290 - CONFIG_SYS_OMAP24_I2C_SLAVE slave addr channel 0 2291 - CONFIG_SYS_OMAP24_I2C_SPEED1 speed channel 1 2292 - CONFIG_SYS_OMAP24_I2C_SLAVE1 slave addr channel 1 2293 - CONFIG_SYS_OMAP24_I2C_SPEED2 speed channel 2 2294 - CONFIG_SYS_OMAP24_I2C_SLAVE2 slave addr channel 2 2295 - CONFIG_SYS_OMAP24_I2C_SPEED3 speed channel 3 2296 - CONFIG_SYS_OMAP24_I2C_SLAVE3 slave addr channel 3 2297 - CONFIG_SYS_OMAP24_I2C_SPEED4 speed channel 4 2298 - CONFIG_SYS_OMAP24_I2C_SLAVE4 slave addr channel 4 2299 2300 - drivers/i2c/zynq_i2c.c 2301 - activate this driver with CONFIG_SYS_I2C_ZYNQ 2302 - set CONFIG_SYS_I2C_ZYNQ_SPEED for speed setting 2303 - set CONFIG_SYS_I2C_ZYNQ_SLAVE for slave addr 2304 2305 - drivers/i2c/s3c24x0_i2c.c: 2306 - activate this driver with CONFIG_SYS_I2C_S3C24X0 2307 - This driver adds i2c buses (11 for Exynos5250, Exynos5420 2308 9 i2c buses for Exynos4 and 1 for S3C24X0 SoCs from Samsung) 2309 with a fix speed from 100000 and the slave addr 0! 2310 2311 - drivers/i2c/ihs_i2c.c 2312 - activate this driver with CONFIG_SYS_I2C_IHS 2313 - CONFIG_SYS_I2C_IHS_CH0 activate hardware channel 0 2314 - CONFIG_SYS_I2C_IHS_SPEED_0 speed channel 0 2315 - CONFIG_SYS_I2C_IHS_SLAVE_0 slave addr channel 0 2316 - CONFIG_SYS_I2C_IHS_CH1 activate hardware channel 1 2317 - CONFIG_SYS_I2C_IHS_SPEED_1 speed channel 1 2318 - CONFIG_SYS_I2C_IHS_SLAVE_1 slave addr channel 1 2319 - CONFIG_SYS_I2C_IHS_CH2 activate hardware channel 2 2320 - CONFIG_SYS_I2C_IHS_SPEED_2 speed channel 2 2321 - CONFIG_SYS_I2C_IHS_SLAVE_2 slave addr channel 2 2322 - CONFIG_SYS_I2C_IHS_CH3 activate hardware channel 3 2323 - CONFIG_SYS_I2C_IHS_SPEED_3 speed channel 3 2324 - CONFIG_SYS_I2C_IHS_SLAVE_3 slave addr channel 3 2325 - activate dual channel with CONFIG_SYS_I2C_IHS_DUAL 2326 - CONFIG_SYS_I2C_IHS_SPEED_0_1 speed channel 0_1 2327 - CONFIG_SYS_I2C_IHS_SLAVE_0_1 slave addr channel 0_1 2328 - CONFIG_SYS_I2C_IHS_SPEED_1_1 speed channel 1_1 2329 - CONFIG_SYS_I2C_IHS_SLAVE_1_1 slave addr channel 1_1 2330 - CONFIG_SYS_I2C_IHS_SPEED_2_1 speed channel 2_1 2331 - CONFIG_SYS_I2C_IHS_SLAVE_2_1 slave addr channel 2_1 2332 - CONFIG_SYS_I2C_IHS_SPEED_3_1 speed channel 3_1 2333 - CONFIG_SYS_I2C_IHS_SLAVE_3_1 slave addr channel 3_1 2334 2335 additional defines: 2336 2337 CONFIG_SYS_NUM_I2C_BUSES 2338 Hold the number of i2c buses you want to use. If you 2339 don't use/have i2c muxes on your i2c bus, this 2340 is equal to CONFIG_SYS_NUM_I2C_ADAPTERS, and you can 2341 omit this define. 2342 2343 CONFIG_SYS_I2C_DIRECT_BUS 2344 define this, if you don't use i2c muxes on your hardware. 2345 if CONFIG_SYS_I2C_MAX_HOPS is not defined or == 0 you can 2346 omit this define. 2347 2348 CONFIG_SYS_I2C_MAX_HOPS 2349 define how many muxes are maximal consecutively connected 2350 on one i2c bus. If you not use i2c muxes, omit this 2351 define. 2352 2353 CONFIG_SYS_I2C_BUSES 2354 hold a list of buses you want to use, only used if 2355 CONFIG_SYS_I2C_DIRECT_BUS is not defined, for example 2356 a board with CONFIG_SYS_I2C_MAX_HOPS = 1 and 2357 CONFIG_SYS_NUM_I2C_BUSES = 9: 2358 2359 CONFIG_SYS_I2C_BUSES {{0, {I2C_NULL_HOP}}, \ 2360 {0, {{I2C_MUX_PCA9547, 0x70, 1}}}, \ 2361 {0, {{I2C_MUX_PCA9547, 0x70, 2}}}, \ 2362 {0, {{I2C_MUX_PCA9547, 0x70, 3}}}, \ 2363 {0, {{I2C_MUX_PCA9547, 0x70, 4}}}, \ 2364 {0, {{I2C_MUX_PCA9547, 0x70, 5}}}, \ 2365 {1, {I2C_NULL_HOP}}, \ 2366 {1, {{I2C_MUX_PCA9544, 0x72, 1}}}, \ 2367 {1, {{I2C_MUX_PCA9544, 0x72, 2}}}, \ 2368 } 2369 2370 which defines 2371 bus 0 on adapter 0 without a mux 2372 bus 1 on adapter 0 with a PCA9547 on address 0x70 port 1 2373 bus 2 on adapter 0 with a PCA9547 on address 0x70 port 2 2374 bus 3 on adapter 0 with a PCA9547 on address 0x70 port 3 2375 bus 4 on adapter 0 with a PCA9547 on address 0x70 port 4 2376 bus 5 on adapter 0 with a PCA9547 on address 0x70 port 5 2377 bus 6 on adapter 1 without a mux 2378 bus 7 on adapter 1 with a PCA9544 on address 0x72 port 1 2379 bus 8 on adapter 1 with a PCA9544 on address 0x72 port 2 2380 2381 If you do not have i2c muxes on your board, omit this define. 2382 2383- Legacy I2C Support: CONFIG_HARD_I2C 2384 2385 NOTE: It is intended to move drivers to CONFIG_SYS_I2C which 2386 provides the following compelling advantages: 2387 2388 - more than one i2c adapter is usable 2389 - approved multibus support 2390 - better i2c mux support 2391 2392 ** Please consider updating your I2C driver now. ** 2393 2394 These enable legacy I2C serial bus commands. Defining 2395 CONFIG_HARD_I2C will include the appropriate I2C driver 2396 for the selected CPU. 2397 2398 This will allow you to use i2c commands at the u-boot 2399 command line (as long as you set CONFIG_CMD_I2C in 2400 CONFIG_COMMANDS) and communicate with i2c based realtime 2401 clock chips. See common/cmd_i2c.c for a description of the 2402 command line interface. 2403 2404 CONFIG_HARD_I2C selects a hardware I2C controller. 2405 2406 There are several other quantities that must also be 2407 defined when you define CONFIG_HARD_I2C. 2408 2409 In both cases you will need to define CONFIG_SYS_I2C_SPEED 2410 to be the frequency (in Hz) at which you wish your i2c bus 2411 to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie 2412 the CPU's i2c node address). 2413 2414 Now, the u-boot i2c code for the mpc8xx 2415 (arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node 2416 and so its address should therefore be cleared to 0 (See, 2417 eg, MPC823e User's Manual p.16-473). So, set 2418 CONFIG_SYS_I2C_SLAVE to 0. 2419 2420 CONFIG_SYS_I2C_INIT_MPC5XXX 2421 2422 When a board is reset during an i2c bus transfer 2423 chips might think that the current transfer is still 2424 in progress. Reset the slave devices by sending start 2425 commands until the slave device responds. 2426 2427 That's all that's required for CONFIG_HARD_I2C. 2428 2429 If you use the software i2c interface (CONFIG_SYS_I2C_SOFT) 2430 then the following macros need to be defined (examples are 2431 from include/configs/lwmon.h): 2432 2433 I2C_INIT 2434 2435 (Optional). Any commands necessary to enable the I2C 2436 controller or configure ports. 2437 2438 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL) 2439 2440 I2C_PORT 2441 2442 (Only for MPC8260 CPU). The I/O port to use (the code 2443 assumes both bits are on the same port). Valid values 2444 are 0..3 for ports A..D. 2445 2446 I2C_ACTIVE 2447 2448 The code necessary to make the I2C data line active 2449 (driven). If the data line is open collector, this 2450 define can be null. 2451 2452 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA) 2453 2454 I2C_TRISTATE 2455 2456 The code necessary to make the I2C data line tri-stated 2457 (inactive). If the data line is open collector, this 2458 define can be null. 2459 2460 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA) 2461 2462 I2C_READ 2463 2464 Code that returns true if the I2C data line is high, 2465 false if it is low. 2466 2467 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0) 2468 2469 I2C_SDA(bit) 2470 2471 If <bit> is true, sets the I2C data line high. If it 2472 is false, it clears it (low). 2473 2474 eg: #define I2C_SDA(bit) \ 2475 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \ 2476 else immr->im_cpm.cp_pbdat &= ~PB_SDA 2477 2478 I2C_SCL(bit) 2479 2480 If <bit> is true, sets the I2C clock line high. If it 2481 is false, it clears it (low). 2482 2483 eg: #define I2C_SCL(bit) \ 2484 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \ 2485 else immr->im_cpm.cp_pbdat &= ~PB_SCL 2486 2487 I2C_DELAY 2488 2489 This delay is invoked four times per clock cycle so this 2490 controls the rate of data transfer. The data rate thus 2491 is 1 / (I2C_DELAY * 4). Often defined to be something 2492 like: 2493 2494 #define I2C_DELAY udelay(2) 2495 2496 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA 2497 2498 If your arch supports the generic GPIO framework (asm/gpio.h), 2499 then you may alternatively define the two GPIOs that are to be 2500 used as SCL / SDA. Any of the previous I2C_xxx macros will 2501 have GPIO-based defaults assigned to them as appropriate. 2502 2503 You should define these to the GPIO value as given directly to 2504 the generic GPIO functions. 2505 2506 CONFIG_SYS_I2C_INIT_BOARD 2507 2508 When a board is reset during an i2c bus transfer 2509 chips might think that the current transfer is still 2510 in progress. On some boards it is possible to access 2511 the i2c SCLK line directly, either by using the 2512 processor pin as a GPIO or by having a second pin 2513 connected to the bus. If this option is defined a 2514 custom i2c_init_board() routine in boards/xxx/board.c 2515 is run early in the boot sequence. 2516 2517 CONFIG_SYS_I2C_BOARD_LATE_INIT 2518 2519 An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is 2520 defined a custom i2c_board_late_init() routine in 2521 boards/xxx/board.c is run AFTER the operations in i2c_init() 2522 is completed. This callpoint can be used to unreset i2c bus 2523 using CPU i2c controller register accesses for CPUs whose i2c 2524 controller provide such a method. It is called at the end of 2525 i2c_init() to allow i2c_init operations to setup the i2c bus 2526 controller on the CPU (e.g. setting bus speed & slave address). 2527 2528 CONFIG_I2CFAST (PPC405GP|PPC405EP only) 2529 2530 This option enables configuration of bi_iic_fast[] flags 2531 in u-boot bd_info structure based on u-boot environment 2532 variable "i2cfast". (see also i2cfast) 2533 2534 CONFIG_I2C_MULTI_BUS 2535 2536 This option allows the use of multiple I2C buses, each of which 2537 must have a controller. At any point in time, only one bus is 2538 active. To switch to a different bus, use the 'i2c dev' command. 2539 Note that bus numbering is zero-based. 2540 2541 CONFIG_SYS_I2C_NOPROBES 2542 2543 This option specifies a list of I2C devices that will be skipped 2544 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS 2545 is set, specify a list of bus-device pairs. Otherwise, specify 2546 a 1D array of device addresses 2547 2548 e.g. 2549 #undef CONFIG_I2C_MULTI_BUS 2550 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68} 2551 2552 will skip addresses 0x50 and 0x68 on a board with one I2C bus 2553 2554 #define CONFIG_I2C_MULTI_BUS 2555 #define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}} 2556 2557 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1 2558 2559 CONFIG_SYS_SPD_BUS_NUM 2560 2561 If defined, then this indicates the I2C bus number for DDR SPD. 2562 If not defined, then U-Boot assumes that SPD is on I2C bus 0. 2563 2564 CONFIG_SYS_RTC_BUS_NUM 2565 2566 If defined, then this indicates the I2C bus number for the RTC. 2567 If not defined, then U-Boot assumes that RTC is on I2C bus 0. 2568 2569 CONFIG_SYS_DTT_BUS_NUM 2570 2571 If defined, then this indicates the I2C bus number for the DTT. 2572 If not defined, then U-Boot assumes that DTT is on I2C bus 0. 2573 2574 CONFIG_SYS_I2C_DTT_ADDR: 2575 2576 If defined, specifies the I2C address of the DTT device. 2577 If not defined, then U-Boot uses predefined value for 2578 specified DTT device. 2579 2580 CONFIG_SOFT_I2C_READ_REPEATED_START 2581 2582 defining this will force the i2c_read() function in 2583 the soft_i2c driver to perform an I2C repeated start 2584 between writing the address pointer and reading the 2585 data. If this define is omitted the default behaviour 2586 of doing a stop-start sequence will be used. Most I2C 2587 devices can use either method, but some require one or 2588 the other. 2589 2590- SPI Support: CONFIG_SPI 2591 2592 Enables SPI driver (so far only tested with 2593 SPI EEPROM, also an instance works with Crystal A/D and 2594 D/As on the SACSng board) 2595 2596 CONFIG_SH_SPI 2597 2598 Enables the driver for SPI controller on SuperH. Currently 2599 only SH7757 is supported. 2600 2601 CONFIG_SOFT_SPI 2602 2603 Enables a software (bit-bang) SPI driver rather than 2604 using hardware support. This is a general purpose 2605 driver that only requires three general I/O port pins 2606 (two outputs, one input) to function. If this is 2607 defined, the board configuration must define several 2608 SPI configuration items (port pins to use, etc). For 2609 an example, see include/configs/sacsng.h. 2610 2611 CONFIG_HARD_SPI 2612 2613 Enables a hardware SPI driver for general-purpose reads 2614 and writes. As with CONFIG_SOFT_SPI, the board configuration 2615 must define a list of chip-select function pointers. 2616 Currently supported on some MPC8xxx processors. For an 2617 example, see include/configs/mpc8349emds.h. 2618 2619 CONFIG_MXC_SPI 2620 2621 Enables the driver for the SPI controllers on i.MX and MXC 2622 SoCs. Currently i.MX31/35/51 are supported. 2623 2624 CONFIG_SYS_SPI_MXC_WAIT 2625 Timeout for waiting until spi transfer completed. 2626 default: (CONFIG_SYS_HZ/100) /* 10 ms */ 2627 2628- FPGA Support: CONFIG_FPGA 2629 2630 Enables FPGA subsystem. 2631 2632 CONFIG_FPGA_<vendor> 2633 2634 Enables support for specific chip vendors. 2635 (ALTERA, XILINX) 2636 2637 CONFIG_FPGA_<family> 2638 2639 Enables support for FPGA family. 2640 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX) 2641 2642 CONFIG_FPGA_COUNT 2643 2644 Specify the number of FPGA devices to support. 2645 2646 CONFIG_CMD_FPGA_LOADMK 2647 2648 Enable support for fpga loadmk command 2649 2650 CONFIG_CMD_FPGA_LOADP 2651 2652 Enable support for fpga loadp command - load partial bitstream 2653 2654 CONFIG_CMD_FPGA_LOADBP 2655 2656 Enable support for fpga loadbp command - load partial bitstream 2657 (Xilinx only) 2658 2659 CONFIG_SYS_FPGA_PROG_FEEDBACK 2660 2661 Enable printing of hash marks during FPGA configuration. 2662 2663 CONFIG_SYS_FPGA_CHECK_BUSY 2664 2665 Enable checks on FPGA configuration interface busy 2666 status by the configuration function. This option 2667 will require a board or device specific function to 2668 be written. 2669 2670 CONFIG_FPGA_DELAY 2671 2672 If defined, a function that provides delays in the FPGA 2673 configuration driver. 2674 2675 CONFIG_SYS_FPGA_CHECK_CTRLC 2676 Allow Control-C to interrupt FPGA configuration 2677 2678 CONFIG_SYS_FPGA_CHECK_ERROR 2679 2680 Check for configuration errors during FPGA bitfile 2681 loading. For example, abort during Virtex II 2682 configuration if the INIT_B line goes low (which 2683 indicated a CRC error). 2684 2685 CONFIG_SYS_FPGA_WAIT_INIT 2686 2687 Maximum time to wait for the INIT_B line to de-assert 2688 after PROB_B has been de-asserted during a Virtex II 2689 FPGA configuration sequence. The default time is 500 2690 ms. 2691 2692 CONFIG_SYS_FPGA_WAIT_BUSY 2693 2694 Maximum time to wait for BUSY to de-assert during 2695 Virtex II FPGA configuration. The default is 5 ms. 2696 2697 CONFIG_SYS_FPGA_WAIT_CONFIG 2698 2699 Time to wait after FPGA configuration. The default is 2700 200 ms. 2701 2702- Configuration Management: 2703 CONFIG_BUILD_TARGET 2704 2705 Some SoCs need special image types (e.g. U-Boot binary 2706 with a special header) as build targets. By defining 2707 CONFIG_BUILD_TARGET in the SoC / board header, this 2708 special image will be automatically built upon calling 2709 make / buildman. 2710 2711 CONFIG_IDENT_STRING 2712 2713 If defined, this string will be added to the U-Boot 2714 version information (U_BOOT_VERSION) 2715 2716- Vendor Parameter Protection: 2717 2718 U-Boot considers the values of the environment 2719 variables "serial#" (Board Serial Number) and 2720 "ethaddr" (Ethernet Address) to be parameters that 2721 are set once by the board vendor / manufacturer, and 2722 protects these variables from casual modification by 2723 the user. Once set, these variables are read-only, 2724 and write or delete attempts are rejected. You can 2725 change this behaviour: 2726 2727 If CONFIG_ENV_OVERWRITE is #defined in your config 2728 file, the write protection for vendor parameters is 2729 completely disabled. Anybody can change or delete 2730 these parameters. 2731 2732 Alternatively, if you define _both_ an ethaddr in the 2733 default env _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default 2734 Ethernet address is installed in the environment, 2735 which can be changed exactly ONCE by the user. [The 2736 serial# is unaffected by this, i. e. it remains 2737 read-only.] 2738 2739 The same can be accomplished in a more flexible way 2740 for any variable by configuring the type of access 2741 to allow for those variables in the ".flags" variable 2742 or define CONFIG_ENV_FLAGS_LIST_STATIC. 2743 2744- Protected RAM: 2745 CONFIG_PRAM 2746 2747 Define this variable to enable the reservation of 2748 "protected RAM", i. e. RAM which is not overwritten 2749 by U-Boot. Define CONFIG_PRAM to hold the number of 2750 kB you want to reserve for pRAM. You can overwrite 2751 this default value by defining an environment 2752 variable "pram" to the number of kB you want to 2753 reserve. Note that the board info structure will 2754 still show the full amount of RAM. If pRAM is 2755 reserved, a new environment variable "mem" will 2756 automatically be defined to hold the amount of 2757 remaining RAM in a form that can be passed as boot 2758 argument to Linux, for instance like that: 2759 2760 setenv bootargs ... mem=\${mem} 2761 saveenv 2762 2763 This way you can tell Linux not to use this memory, 2764 either, which results in a memory region that will 2765 not be affected by reboots. 2766 2767 *WARNING* If your board configuration uses automatic 2768 detection of the RAM size, you must make sure that 2769 this memory test is non-destructive. So far, the 2770 following board configurations are known to be 2771 "pRAM-clean": 2772 2773 IVMS8, IVML24, SPD8xx, TQM8xxL, 2774 HERMES, IP860, RPXlite, LWMON, 2775 FLAGADM, TQM8260 2776 2777- Access to physical memory region (> 4GB) 2778 Some basic support is provided for operations on memory not 2779 normally accessible to U-Boot - e.g. some architectures 2780 support access to more than 4GB of memory on 32-bit 2781 machines using physical address extension or similar. 2782 Define CONFIG_PHYSMEM to access this basic support, which 2783 currently only supports clearing the memory. 2784 2785- Error Recovery: 2786 CONFIG_PANIC_HANG 2787 2788 Define this variable to stop the system in case of a 2789 fatal error, so that you have to reset it manually. 2790 This is probably NOT a good idea for an embedded 2791 system where you want the system to reboot 2792 automatically as fast as possible, but it may be 2793 useful during development since you can try to debug 2794 the conditions that lead to the situation. 2795 2796 CONFIG_NET_RETRY_COUNT 2797 2798 This variable defines the number of retries for 2799 network operations like ARP, RARP, TFTP, or BOOTP 2800 before giving up the operation. If not defined, a 2801 default value of 5 is used. 2802 2803 CONFIG_ARP_TIMEOUT 2804 2805 Timeout waiting for an ARP reply in milliseconds. 2806 2807 CONFIG_NFS_TIMEOUT 2808 2809 Timeout in milliseconds used in NFS protocol. 2810 If you encounter "ERROR: Cannot umount" in nfs command, 2811 try longer timeout such as 2812 #define CONFIG_NFS_TIMEOUT 10000UL 2813 2814- Command Interpreter: 2815 CONFIG_AUTO_COMPLETE 2816 2817 Enable auto completion of commands using TAB. 2818 2819 CONFIG_SYS_PROMPT_HUSH_PS2 2820 2821 This defines the secondary prompt string, which is 2822 printed when the command interpreter needs more input 2823 to complete a command. Usually "> ". 2824 2825 Note: 2826 2827 In the current implementation, the local variables 2828 space and global environment variables space are 2829 separated. Local variables are those you define by 2830 simply typing `name=value'. To access a local 2831 variable later on, you have write `$name' or 2832 `${name}'; to execute the contents of a variable 2833 directly type `$name' at the command prompt. 2834 2835 Global environment variables are those you use 2836 setenv/printenv to work with. To run a command stored 2837 in such a variable, you need to use the run command, 2838 and you must not use the '$' sign to access them. 2839 2840 To store commands and special characters in a 2841 variable, please use double quotation marks 2842 surrounding the whole text of the variable, instead 2843 of the backslashes before semicolons and special 2844 symbols. 2845 2846- Command Line Editing and History: 2847 CONFIG_CMDLINE_EDITING 2848 2849 Enable editing and History functions for interactive 2850 command line input operations 2851 2852- Command Line PS1/PS2 support: 2853 CONFIG_CMDLINE_PS_SUPPORT 2854 2855 Enable support for changing the command prompt string 2856 at run-time. Only static string is supported so far. 2857 The string is obtained from environment variables PS1 2858 and PS2. 2859 2860- Default Environment: 2861 CONFIG_EXTRA_ENV_SETTINGS 2862 2863 Define this to contain any number of null terminated 2864 strings (variable = value pairs) that will be part of 2865 the default environment compiled into the boot image. 2866 2867 For example, place something like this in your 2868 board's config file: 2869 2870 #define CONFIG_EXTRA_ENV_SETTINGS \ 2871 "myvar1=value1\0" \ 2872 "myvar2=value2\0" 2873 2874 Warning: This method is based on knowledge about the 2875 internal format how the environment is stored by the 2876 U-Boot code. This is NOT an official, exported 2877 interface! Although it is unlikely that this format 2878 will change soon, there is no guarantee either. 2879 You better know what you are doing here. 2880 2881 Note: overly (ab)use of the default environment is 2882 discouraged. Make sure to check other ways to preset 2883 the environment like the "source" command or the 2884 boot command first. 2885 2886 CONFIG_ENV_VARS_UBOOT_CONFIG 2887 2888 Define this in order to add variables describing the 2889 U-Boot build configuration to the default environment. 2890 These will be named arch, cpu, board, vendor, and soc. 2891 2892 Enabling this option will cause the following to be defined: 2893 2894 - CONFIG_SYS_ARCH 2895 - CONFIG_SYS_CPU 2896 - CONFIG_SYS_BOARD 2897 - CONFIG_SYS_VENDOR 2898 - CONFIG_SYS_SOC 2899 2900 CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG 2901 2902 Define this in order to add variables describing certain 2903 run-time determined information about the hardware to the 2904 environment. These will be named board_name, board_rev. 2905 2906 CONFIG_DELAY_ENVIRONMENT 2907 2908 Normally the environment is loaded when the board is 2909 initialised so that it is available to U-Boot. This inhibits 2910 that so that the environment is not available until 2911 explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL 2912 this is instead controlled by the value of 2913 /config/load-environment. 2914 2915- Parallel Flash support: 2916 CONFIG_SYS_NO_FLASH 2917 2918 Traditionally U-Boot was run on systems with parallel NOR 2919 flash. This option is used to disable support for parallel NOR 2920 flash. This option should be defined if the board does not have 2921 parallel flash. 2922 2923 If this option is not defined one of the generic flash drivers 2924 (e.g. CONFIG_FLASH_CFI_DRIVER or CONFIG_ST_SMI) must be 2925 selected or the board must provide an implementation of the 2926 flash API (see include/flash.h). 2927 2928- DataFlash Support: 2929 CONFIG_HAS_DATAFLASH 2930 2931 Defining this option enables DataFlash features and 2932 allows to read/write in Dataflash via the standard 2933 commands cp, md... 2934 2935- Serial Flash support 2936 CONFIG_CMD_SF 2937 2938 Defining this option enables SPI flash commands 2939 'sf probe/read/write/erase/update'. 2940 2941 Usage requires an initial 'probe' to define the serial 2942 flash parameters, followed by read/write/erase/update 2943 commands. 2944 2945 The following defaults may be provided by the platform 2946 to handle the common case when only a single serial 2947 flash is present on the system. 2948 2949 CONFIG_SF_DEFAULT_BUS Bus identifier 2950 CONFIG_SF_DEFAULT_CS Chip-select 2951 CONFIG_SF_DEFAULT_MODE (see include/spi.h) 2952 CONFIG_SF_DEFAULT_SPEED in Hz 2953 2954 CONFIG_CMD_SF_TEST 2955 2956 Define this option to include a destructive SPI flash 2957 test ('sf test'). 2958 2959 CONFIG_SF_DUAL_FLASH Dual flash memories 2960 2961 Define this option to use dual flash support where two flash 2962 memories can be connected with a given cs line. 2963 Currently Xilinx Zynq qspi supports these type of connections. 2964 2965- SystemACE Support: 2966 CONFIG_SYSTEMACE 2967 2968 Adding this option adds support for Xilinx SystemACE 2969 chips attached via some sort of local bus. The address 2970 of the chip must also be defined in the 2971 CONFIG_SYS_SYSTEMACE_BASE macro. For example: 2972 2973 #define CONFIG_SYSTEMACE 2974 #define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000 2975 2976 When SystemACE support is added, the "ace" device type 2977 becomes available to the fat commands, i.e. fatls. 2978 2979- TFTP Fixed UDP Port: 2980 CONFIG_TFTP_PORT 2981 2982 If this is defined, the environment variable tftpsrcp 2983 is used to supply the TFTP UDP source port value. 2984 If tftpsrcp isn't defined, the normal pseudo-random port 2985 number generator is used. 2986 2987 Also, the environment variable tftpdstp is used to supply 2988 the TFTP UDP destination port value. If tftpdstp isn't 2989 defined, the normal port 69 is used. 2990 2991 The purpose for tftpsrcp is to allow a TFTP server to 2992 blindly start the TFTP transfer using the pre-configured 2993 target IP address and UDP port. This has the effect of 2994 "punching through" the (Windows XP) firewall, allowing 2995 the remainder of the TFTP transfer to proceed normally. 2996 A better solution is to properly configure the firewall, 2997 but sometimes that is not allowed. 2998 2999- Hashing support: 3000 CONFIG_CMD_HASH 3001 3002 This enables a generic 'hash' command which can produce 3003 hashes / digests from a few algorithms (e.g. SHA1, SHA256). 3004 3005 CONFIG_HASH_VERIFY 3006 3007 Enable the hash verify command (hash -v). This adds to code 3008 size a little. 3009 3010 CONFIG_SHA1 - This option enables support of hashing using SHA1 3011 algorithm. The hash is calculated in software. 3012 CONFIG_SHA256 - This option enables support of hashing using 3013 SHA256 algorithm. The hash is calculated in software. 3014 CONFIG_SHA_HW_ACCEL - This option enables hardware acceleration 3015 for SHA1/SHA256 hashing. 3016 This affects the 'hash' command and also the 3017 hash_lookup_algo() function. 3018 CONFIG_SHA_PROG_HW_ACCEL - This option enables 3019 hardware-acceleration for SHA1/SHA256 progressive hashing. 3020 Data can be streamed in a block at a time and the hashing 3021 is performed in hardware. 3022 3023 Note: There is also a sha1sum command, which should perhaps 3024 be deprecated in favour of 'hash sha1'. 3025 3026- Freescale i.MX specific commands: 3027 CONFIG_CMD_HDMIDETECT 3028 This enables 'hdmidet' command which returns true if an 3029 HDMI monitor is detected. This command is i.MX 6 specific. 3030 3031 CONFIG_CMD_BMODE 3032 This enables the 'bmode' (bootmode) command for forcing 3033 a boot from specific media. 3034 3035 This is useful for forcing the ROM's usb downloader to 3036 activate upon a watchdog reset which is nice when iterating 3037 on U-Boot. Using the reset button or running bmode normal 3038 will set it back to normal. This command currently 3039 supports i.MX53 and i.MX6. 3040 3041- bootcount support: 3042 CONFIG_BOOTCOUNT_LIMIT 3043 3044 This enables the bootcounter support, see: 3045 http://www.denx.de/wiki/DULG/UBootBootCountLimit 3046 3047 CONFIG_AT91SAM9XE 3048 enable special bootcounter support on at91sam9xe based boards. 3049 CONFIG_BLACKFIN 3050 enable special bootcounter support on blackfin based boards. 3051 CONFIG_SOC_DA8XX 3052 enable special bootcounter support on da850 based boards. 3053 CONFIG_BOOTCOUNT_RAM 3054 enable support for the bootcounter in RAM 3055 CONFIG_BOOTCOUNT_I2C 3056 enable support for the bootcounter on an i2c (like RTC) device. 3057 CONFIG_SYS_I2C_RTC_ADDR = i2c chip address 3058 CONFIG_SYS_BOOTCOUNT_ADDR = i2c addr which is used for 3059 the bootcounter. 3060 CONFIG_BOOTCOUNT_ALEN = address len 3061 3062- Show boot progress: 3063 CONFIG_SHOW_BOOT_PROGRESS 3064 3065 Defining this option allows to add some board- 3066 specific code (calling a user-provided function 3067 "show_boot_progress(int)") that enables you to show 3068 the system's boot progress on some display (for 3069 example, some LED's) on your board. At the moment, 3070 the following checkpoints are implemented: 3071 3072 3073Legacy uImage format: 3074 3075 Arg Where When 3076 1 common/cmd_bootm.c before attempting to boot an image 3077 -1 common/cmd_bootm.c Image header has bad magic number 3078 2 common/cmd_bootm.c Image header has correct magic number 3079 -2 common/cmd_bootm.c Image header has bad checksum 3080 3 common/cmd_bootm.c Image header has correct checksum 3081 -3 common/cmd_bootm.c Image data has bad checksum 3082 4 common/cmd_bootm.c Image data has correct checksum 3083 -4 common/cmd_bootm.c Image is for unsupported architecture 3084 5 common/cmd_bootm.c Architecture check OK 3085 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi) 3086 6 common/cmd_bootm.c Image Type check OK 3087 -6 common/cmd_bootm.c gunzip uncompression error 3088 -7 common/cmd_bootm.c Unimplemented compression type 3089 7 common/cmd_bootm.c Uncompression OK 3090 8 common/cmd_bootm.c No uncompress/copy overwrite error 3091 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX) 3092 3093 9 common/image.c Start initial ramdisk verification 3094 -10 common/image.c Ramdisk header has bad magic number 3095 -11 common/image.c Ramdisk header has bad checksum 3096 10 common/image.c Ramdisk header is OK 3097 -12 common/image.c Ramdisk data has bad checksum 3098 11 common/image.c Ramdisk data has correct checksum 3099 12 common/image.c Ramdisk verification complete, start loading 3100 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk) 3101 13 common/image.c Start multifile image verification 3102 14 common/image.c No initial ramdisk, no multifile, continue. 3103 3104 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS 3105 3106 -30 arch/powerpc/lib/board.c Fatal error, hang the system 3107 -31 post/post.c POST test failed, detected by post_output_backlog() 3108 -32 post/post.c POST test failed, detected by post_run_single() 3109 3110 34 common/cmd_doc.c before loading a Image from a DOC device 3111 -35 common/cmd_doc.c Bad usage of "doc" command 3112 35 common/cmd_doc.c correct usage of "doc" command 3113 -36 common/cmd_doc.c No boot device 3114 36 common/cmd_doc.c correct boot device 3115 -37 common/cmd_doc.c Unknown Chip ID on boot device 3116 37 common/cmd_doc.c correct chip ID found, device available 3117 -38 common/cmd_doc.c Read Error on boot device 3118 38 common/cmd_doc.c reading Image header from DOC device OK 3119 -39 common/cmd_doc.c Image header has bad magic number 3120 39 common/cmd_doc.c Image header has correct magic number 3121 -40 common/cmd_doc.c Error reading Image from DOC device 3122 40 common/cmd_doc.c Image header has correct magic number 3123 41 common/cmd_ide.c before loading a Image from a IDE device 3124 -42 common/cmd_ide.c Bad usage of "ide" command 3125 42 common/cmd_ide.c correct usage of "ide" command 3126 -43 common/cmd_ide.c No boot device 3127 43 common/cmd_ide.c boot device found 3128 -44 common/cmd_ide.c Device not available 3129 44 common/cmd_ide.c Device available 3130 -45 common/cmd_ide.c wrong partition selected 3131 45 common/cmd_ide.c partition selected 3132 -46 common/cmd_ide.c Unknown partition table 3133 46 common/cmd_ide.c valid partition table found 3134 -47 common/cmd_ide.c Invalid partition type 3135 47 common/cmd_ide.c correct partition type 3136 -48 common/cmd_ide.c Error reading Image Header on boot device 3137 48 common/cmd_ide.c reading Image Header from IDE device OK 3138 -49 common/cmd_ide.c Image header has bad magic number 3139 49 common/cmd_ide.c Image header has correct magic number 3140 -50 common/cmd_ide.c Image header has bad checksum 3141 50 common/cmd_ide.c Image header has correct checksum 3142 -51 common/cmd_ide.c Error reading Image from IDE device 3143 51 common/cmd_ide.c reading Image from IDE device OK 3144 52 common/cmd_nand.c before loading a Image from a NAND device 3145 -53 common/cmd_nand.c Bad usage of "nand" command 3146 53 common/cmd_nand.c correct usage of "nand" command 3147 -54 common/cmd_nand.c No boot device 3148 54 common/cmd_nand.c boot device found 3149 -55 common/cmd_nand.c Unknown Chip ID on boot device 3150 55 common/cmd_nand.c correct chip ID found, device available 3151 -56 common/cmd_nand.c Error reading Image Header on boot device 3152 56 common/cmd_nand.c reading Image Header from NAND device OK 3153 -57 common/cmd_nand.c Image header has bad magic number 3154 57 common/cmd_nand.c Image header has correct magic number 3155 -58 common/cmd_nand.c Error reading Image from NAND device 3156 58 common/cmd_nand.c reading Image from NAND device OK 3157 3158 -60 common/env_common.c Environment has a bad CRC, using default 3159 3160 64 net/eth.c starting with Ethernet configuration. 3161 -64 net/eth.c no Ethernet found. 3162 65 net/eth.c Ethernet found. 3163 3164 -80 common/cmd_net.c usage wrong 3165 80 common/cmd_net.c before calling net_loop() 3166 -81 common/cmd_net.c some error in net_loop() occurred 3167 81 common/cmd_net.c net_loop() back without error 3168 -82 common/cmd_net.c size == 0 (File with size 0 loaded) 3169 82 common/cmd_net.c trying automatic boot 3170 83 common/cmd_net.c running "source" command 3171 -83 common/cmd_net.c some error in automatic boot or "source" command 3172 84 common/cmd_net.c end without errors 3173 3174FIT uImage format: 3175 3176 Arg Where When 3177 100 common/cmd_bootm.c Kernel FIT Image has correct format 3178 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format 3179 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration 3180 -101 common/cmd_bootm.c Can't get configuration for kernel subimage 3181 102 common/cmd_bootm.c Kernel unit name specified 3182 -103 common/cmd_bootm.c Can't get kernel subimage node offset 3183 103 common/cmd_bootm.c Found configuration node 3184 104 common/cmd_bootm.c Got kernel subimage node offset 3185 -104 common/cmd_bootm.c Kernel subimage hash verification failed 3186 105 common/cmd_bootm.c Kernel subimage hash verification OK 3187 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture 3188 106 common/cmd_bootm.c Architecture check OK 3189 -106 common/cmd_bootm.c Kernel subimage has wrong type 3190 107 common/cmd_bootm.c Kernel subimage type OK 3191 -107 common/cmd_bootm.c Can't get kernel subimage data/size 3192 108 common/cmd_bootm.c Got kernel subimage data/size 3193 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT) 3194 -109 common/cmd_bootm.c Can't get kernel subimage type 3195 -110 common/cmd_bootm.c Can't get kernel subimage comp 3196 -111 common/cmd_bootm.c Can't get kernel subimage os 3197 -112 common/cmd_bootm.c Can't get kernel subimage load address 3198 -113 common/cmd_bootm.c Image uncompress/copy overwrite error 3199 3200 120 common/image.c Start initial ramdisk verification 3201 -120 common/image.c Ramdisk FIT image has incorrect format 3202 121 common/image.c Ramdisk FIT image has correct format 3203 122 common/image.c No ramdisk subimage unit name, using configuration 3204 -122 common/image.c Can't get configuration for ramdisk subimage 3205 123 common/image.c Ramdisk unit name specified 3206 -124 common/image.c Can't get ramdisk subimage node offset 3207 125 common/image.c Got ramdisk subimage node offset 3208 -125 common/image.c Ramdisk subimage hash verification failed 3209 126 common/image.c Ramdisk subimage hash verification OK 3210 -126 common/image.c Ramdisk subimage for unsupported architecture 3211 127 common/image.c Architecture check OK 3212 -127 common/image.c Can't get ramdisk subimage data/size 3213 128 common/image.c Got ramdisk subimage data/size 3214 129 common/image.c Can't get ramdisk load address 3215 -129 common/image.c Got ramdisk load address 3216 3217 -130 common/cmd_doc.c Incorrect FIT image format 3218 131 common/cmd_doc.c FIT image format OK 3219 3220 -140 common/cmd_ide.c Incorrect FIT image format 3221 141 common/cmd_ide.c FIT image format OK 3222 3223 -150 common/cmd_nand.c Incorrect FIT image format 3224 151 common/cmd_nand.c FIT image format OK 3225 3226- legacy image format: 3227 CONFIG_IMAGE_FORMAT_LEGACY 3228 enables the legacy image format support in U-Boot. 3229 3230 Default: 3231 enabled if CONFIG_FIT_SIGNATURE is not defined. 3232 3233 CONFIG_DISABLE_IMAGE_LEGACY 3234 disable the legacy image format 3235 3236 This define is introduced, as the legacy image format is 3237 enabled per default for backward compatibility. 3238 3239- FIT image support: 3240 CONFIG_FIT_DISABLE_SHA256 3241 Supporting SHA256 hashes has quite an impact on binary size. 3242 For constrained systems sha256 hash support can be disabled 3243 with this option. 3244 3245 TODO(sjg@chromium.org): Adjust this option to be positive, 3246 and move it to Kconfig 3247 3248- Standalone program support: 3249 CONFIG_STANDALONE_LOAD_ADDR 3250 3251 This option defines a board specific value for the 3252 address where standalone program gets loaded, thus 3253 overwriting the architecture dependent default 3254 settings. 3255 3256- Frame Buffer Address: 3257 CONFIG_FB_ADDR 3258 3259 Define CONFIG_FB_ADDR if you want to use specific 3260 address for frame buffer. This is typically the case 3261 when using a graphics controller has separate video 3262 memory. U-Boot will then place the frame buffer at 3263 the given address instead of dynamically reserving it 3264 in system RAM by calling lcd_setmem(), which grabs 3265 the memory for the frame buffer depending on the 3266 configured panel size. 3267 3268 Please see board_init_f function. 3269 3270- Automatic software updates via TFTP server 3271 CONFIG_UPDATE_TFTP 3272 CONFIG_UPDATE_TFTP_CNT_MAX 3273 CONFIG_UPDATE_TFTP_MSEC_MAX 3274 3275 These options enable and control the auto-update feature; 3276 for a more detailed description refer to doc/README.update. 3277 3278- MTD Support (mtdparts command, UBI support) 3279 CONFIG_MTD_DEVICE 3280 3281 Adds the MTD device infrastructure from the Linux kernel. 3282 Needed for mtdparts command support. 3283 3284 CONFIG_MTD_PARTITIONS 3285 3286 Adds the MTD partitioning infrastructure from the Linux 3287 kernel. Needed for UBI support. 3288 3289- UBI support 3290 CONFIG_CMD_UBI 3291 3292 Adds commands for interacting with MTD partitions formatted 3293 with the UBI flash translation layer 3294 3295 Requires also defining CONFIG_RBTREE 3296 3297 CONFIG_UBI_SILENCE_MSG 3298 3299 Make the verbose messages from UBI stop printing. This leaves 3300 warnings and errors enabled. 3301 3302 3303 CONFIG_MTD_UBI_WL_THRESHOLD 3304 This parameter defines the maximum difference between the highest 3305 erase counter value and the lowest erase counter value of eraseblocks 3306 of UBI devices. When this threshold is exceeded, UBI starts performing 3307 wear leveling by means of moving data from eraseblock with low erase 3308 counter to eraseblocks with high erase counter. 3309 3310 The default value should be OK for SLC NAND flashes, NOR flashes and 3311 other flashes which have eraseblock life-cycle 100000 or more. 3312 However, in case of MLC NAND flashes which typically have eraseblock 3313 life-cycle less than 10000, the threshold should be lessened (e.g., 3314 to 128 or 256, although it does not have to be power of 2). 3315 3316 default: 4096 3317 3318 CONFIG_MTD_UBI_BEB_LIMIT 3319 This option specifies the maximum bad physical eraseblocks UBI 3320 expects on the MTD device (per 1024 eraseblocks). If the 3321 underlying flash does not admit of bad eraseblocks (e.g. NOR 3322 flash), this value is ignored. 3323 3324 NAND datasheets often specify the minimum and maximum NVM 3325 (Number of Valid Blocks) for the flashes' endurance lifetime. 3326 The maximum expected bad eraseblocks per 1024 eraseblocks 3327 then can be calculated as "1024 * (1 - MinNVB / MaxNVB)", 3328 which gives 20 for most NANDs (MaxNVB is basically the total 3329 count of eraseblocks on the chip). 3330 3331 To put it differently, if this value is 20, UBI will try to 3332 reserve about 1.9% of physical eraseblocks for bad blocks 3333 handling. And that will be 1.9% of eraseblocks on the entire 3334 NAND chip, not just the MTD partition UBI attaches. This means 3335 that if you have, say, a NAND flash chip admits maximum 40 bad 3336 eraseblocks, and it is split on two MTD partitions of the same 3337 size, UBI will reserve 40 eraseblocks when attaching a 3338 partition. 3339 3340 default: 20 3341 3342 CONFIG_MTD_UBI_FASTMAP 3343 Fastmap is a mechanism which allows attaching an UBI device 3344 in nearly constant time. Instead of scanning the whole MTD device it 3345 only has to locate a checkpoint (called fastmap) on the device. 3346 The on-flash fastmap contains all information needed to attach 3347 the device. Using fastmap makes only sense on large devices where 3348 attaching by scanning takes long. UBI will not automatically install 3349 a fastmap on old images, but you can set the UBI parameter 3350 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT to 1 if you want so. Please note 3351 that fastmap-enabled images are still usable with UBI implementations 3352 without fastmap support. On typical flash devices the whole fastmap 3353 fits into one PEB. UBI will reserve PEBs to hold two fastmaps. 3354 3355 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT 3356 Set this parameter to enable fastmap automatically on images 3357 without a fastmap. 3358 default: 0 3359 3360 CONFIG_MTD_UBI_FM_DEBUG 3361 Enable UBI fastmap debug 3362 default: 0 3363 3364- UBIFS support 3365 CONFIG_CMD_UBIFS 3366 3367 Adds commands for interacting with UBI volumes formatted as 3368 UBIFS. UBIFS is read-only in u-boot. 3369 3370 Requires UBI support as well as CONFIG_LZO 3371 3372 CONFIG_UBIFS_SILENCE_MSG 3373 3374 Make the verbose messages from UBIFS stop printing. This leaves 3375 warnings and errors enabled. 3376 3377- SPL framework 3378 CONFIG_SPL 3379 Enable building of SPL globally. 3380 3381 CONFIG_SPL_LDSCRIPT 3382 LDSCRIPT for linking the SPL binary. 3383 3384 CONFIG_SPL_MAX_FOOTPRINT 3385 Maximum size in memory allocated to the SPL, BSS included. 3386 When defined, the linker checks that the actual memory 3387 used by SPL from _start to __bss_end does not exceed it. 3388 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE 3389 must not be both defined at the same time. 3390 3391 CONFIG_SPL_MAX_SIZE 3392 Maximum size of the SPL image (text, data, rodata, and 3393 linker lists sections), BSS excluded. 3394 When defined, the linker checks that the actual size does 3395 not exceed it. 3396 3397 CONFIG_SPL_TEXT_BASE 3398 TEXT_BASE for linking the SPL binary. 3399 3400 CONFIG_SPL_RELOC_TEXT_BASE 3401 Address to relocate to. If unspecified, this is equal to 3402 CONFIG_SPL_TEXT_BASE (i.e. no relocation is done). 3403 3404 CONFIG_SPL_BSS_START_ADDR 3405 Link address for the BSS within the SPL binary. 3406 3407 CONFIG_SPL_BSS_MAX_SIZE 3408 Maximum size in memory allocated to the SPL BSS. 3409 When defined, the linker checks that the actual memory used 3410 by SPL from __bss_start to __bss_end does not exceed it. 3411 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE 3412 must not be both defined at the same time. 3413 3414 CONFIG_SPL_STACK 3415 Adress of the start of the stack SPL will use 3416 3417 CONFIG_SPL_PANIC_ON_RAW_IMAGE 3418 When defined, SPL will panic() if the image it has 3419 loaded does not have a signature. 3420 Defining this is useful when code which loads images 3421 in SPL cannot guarantee that absolutely all read errors 3422 will be caught. 3423 An example is the LPC32XX MLC NAND driver, which will 3424 consider that a completely unreadable NAND block is bad, 3425 and thus should be skipped silently. 3426 3427 CONFIG_SPL_ABORT_ON_RAW_IMAGE 3428 When defined, SPL will proceed to another boot method 3429 if the image it has loaded does not have a signature. 3430 3431 CONFIG_SPL_RELOC_STACK 3432 Adress of the start of the stack SPL will use after 3433 relocation. If unspecified, this is equal to 3434 CONFIG_SPL_STACK. 3435 3436 CONFIG_SYS_SPL_MALLOC_START 3437 Starting address of the malloc pool used in SPL. 3438 When this option is set the full malloc is used in SPL and 3439 it is set up by spl_init() and before that, the simple malloc() 3440 can be used if CONFIG_SYS_MALLOC_F is defined. 3441 3442 CONFIG_SYS_SPL_MALLOC_SIZE 3443 The size of the malloc pool used in SPL. 3444 3445 CONFIG_SPL_FRAMEWORK 3446 Enable the SPL framework under common/. This framework 3447 supports MMC, NAND and YMODEM loading of U-Boot and NAND 3448 NAND loading of the Linux Kernel. 3449 3450 CONFIG_SPL_OS_BOOT 3451 Enable booting directly to an OS from SPL. 3452 See also: doc/README.falcon 3453 3454 CONFIG_SPL_DISPLAY_PRINT 3455 For ARM, enable an optional function to print more information 3456 about the running system. 3457 3458 CONFIG_SPL_INIT_MINIMAL 3459 Arch init code should be built for a very small image 3460 3461 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR, 3462 CONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS, 3463 Address and partition on the MMC to load U-Boot from 3464 when the MMC is being used in raw mode. 3465 3466 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION 3467 Partition on the MMC to load U-Boot from when the MMC is being 3468 used in raw mode 3469 3470 CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR 3471 Sector to load kernel uImage from when MMC is being 3472 used in raw mode (for Falcon mode) 3473 3474 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR, 3475 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS 3476 Sector and number of sectors to load kernel argument 3477 parameters from when MMC is being used in raw mode 3478 (for falcon mode) 3479 3480 CONFIG_SYS_MMCSD_FS_BOOT_PARTITION 3481 Partition on the MMC to load U-Boot from when the MMC is being 3482 used in fs mode 3483 3484 CONFIG_SPL_FS_LOAD_PAYLOAD_NAME 3485 Filename to read to load U-Boot when reading from filesystem 3486 3487 CONFIG_SPL_FS_LOAD_KERNEL_NAME 3488 Filename to read to load kernel uImage when reading 3489 from filesystem (for Falcon mode) 3490 3491 CONFIG_SPL_FS_LOAD_ARGS_NAME 3492 Filename to read to load kernel argument parameters 3493 when reading from filesystem (for Falcon mode) 3494 3495 CONFIG_SPL_MPC83XX_WAIT_FOR_NAND 3496 Set this for NAND SPL on PPC mpc83xx targets, so that 3497 start.S waits for the rest of the SPL to load before 3498 continuing (the hardware starts execution after just 3499 loading the first page rather than the full 4K). 3500 3501 CONFIG_SPL_SKIP_RELOCATE 3502 Avoid SPL relocation 3503 3504 CONFIG_SPL_NAND_BASE 3505 Include nand_base.c in the SPL. Requires 3506 CONFIG_SPL_NAND_DRIVERS. 3507 3508 CONFIG_SPL_NAND_DRIVERS 3509 SPL uses normal NAND drivers, not minimal drivers. 3510 3511 CONFIG_SPL_NAND_ECC 3512 Include standard software ECC in the SPL 3513 3514 CONFIG_SPL_NAND_SIMPLE 3515 Support for NAND boot using simple NAND drivers that 3516 expose the cmd_ctrl() interface. 3517 3518 CONFIG_SPL_UBI 3519 Support for a lightweight UBI (fastmap) scanner and 3520 loader 3521 3522 CONFIG_SPL_NAND_RAW_ONLY 3523 Support to boot only raw u-boot.bin images. Use this only 3524 if you need to save space. 3525 3526 CONFIG_SPL_COMMON_INIT_DDR 3527 Set for common ddr init with serial presence detect in 3528 SPL binary. 3529 3530 CONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT, 3531 CONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE, 3532 CONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS, 3533 CONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE, 3534 CONFIG_SYS_NAND_ECCBYTES 3535 Defines the size and behavior of the NAND that SPL uses 3536 to read U-Boot 3537 3538 CONFIG_SPL_NAND_BOOT 3539 Add support NAND boot 3540 3541 CONFIG_SYS_NAND_U_BOOT_OFFS 3542 Location in NAND to read U-Boot from 3543 3544 CONFIG_SYS_NAND_U_BOOT_DST 3545 Location in memory to load U-Boot to 3546 3547 CONFIG_SYS_NAND_U_BOOT_SIZE 3548 Size of image to load 3549 3550 CONFIG_SYS_NAND_U_BOOT_START 3551 Entry point in loaded image to jump to 3552 3553 CONFIG_SYS_NAND_HW_ECC_OOBFIRST 3554 Define this if you need to first read the OOB and then the 3555 data. This is used, for example, on davinci platforms. 3556 3557 CONFIG_SPL_OMAP3_ID_NAND 3558 Support for an OMAP3-specific set of functions to return the 3559 ID and MFR of the first attached NAND chip, if present. 3560 3561 CONFIG_SPL_RAM_DEVICE 3562 Support for running image already present in ram, in SPL binary 3563 3564 CONFIG_SPL_PAD_TO 3565 Image offset to which the SPL should be padded before appending 3566 the SPL payload. By default, this is defined as 3567 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined. 3568 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL 3569 payload without any padding, or >= CONFIG_SPL_MAX_SIZE. 3570 3571 CONFIG_SPL_TARGET 3572 Final target image containing SPL and payload. Some SPLs 3573 use an arch-specific makefile fragment instead, for 3574 example if more than one image needs to be produced. 3575 3576 CONFIG_FIT_SPL_PRINT 3577 Printing information about a FIT image adds quite a bit of 3578 code to SPL. So this is normally disabled in SPL. Use this 3579 option to re-enable it. This will affect the output of the 3580 bootm command when booting a FIT image. 3581 3582- TPL framework 3583 CONFIG_TPL 3584 Enable building of TPL globally. 3585 3586 CONFIG_TPL_PAD_TO 3587 Image offset to which the TPL should be padded before appending 3588 the TPL payload. By default, this is defined as 3589 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined. 3590 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL 3591 payload without any padding, or >= CONFIG_SPL_MAX_SIZE. 3592 3593- Interrupt support (PPC): 3594 3595 There are common interrupt_init() and timer_interrupt() 3596 for all PPC archs. interrupt_init() calls interrupt_init_cpu() 3597 for CPU specific initialization. interrupt_init_cpu() 3598 should set decrementer_count to appropriate value. If 3599 CPU resets decrementer automatically after interrupt 3600 (ppc4xx) it should set decrementer_count to zero. 3601 timer_interrupt() calls timer_interrupt_cpu() for CPU 3602 specific handling. If board has watchdog / status_led 3603 / other_activity_monitor it works automatically from 3604 general timer_interrupt(). 3605 3606 3607Board initialization settings: 3608------------------------------ 3609 3610During Initialization u-boot calls a number of board specific functions 3611to allow the preparation of board specific prerequisites, e.g. pin setup 3612before drivers are initialized. To enable these callbacks the 3613following configuration macros have to be defined. Currently this is 3614architecture specific, so please check arch/your_architecture/lib/board.c 3615typically in board_init_f() and board_init_r(). 3616 3617- CONFIG_BOARD_EARLY_INIT_F: Call board_early_init_f() 3618- CONFIG_BOARD_EARLY_INIT_R: Call board_early_init_r() 3619- CONFIG_BOARD_LATE_INIT: Call board_late_init() 3620- CONFIG_BOARD_POSTCLK_INIT: Call board_postclk_init() 3621 3622Configuration Settings: 3623----------------------- 3624 3625- CONFIG_SYS_SUPPORT_64BIT_DATA: Defined automatically if compiled as 64-bit. 3626 Optionally it can be defined to support 64-bit memory commands. 3627 3628- CONFIG_SYS_LONGHELP: Defined when you want long help messages included; 3629 undefine this when you're short of memory. 3630 3631- CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default 3632 width of the commands listed in the 'help' command output. 3633 3634- CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to 3635 prompt for user input. 3636 3637- CONFIG_SYS_CBSIZE: Buffer size for input from the Console 3638 3639- CONFIG_SYS_PBSIZE: Buffer size for Console output 3640 3641- CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands 3642 3643- CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to 3644 the application (usually a Linux kernel) when it is 3645 booted 3646 3647- CONFIG_SYS_BAUDRATE_TABLE: 3648 List of legal baudrate settings for this board. 3649 3650- CONFIG_SYS_CONSOLE_INFO_QUIET 3651 Suppress display of console information at boot. 3652 3653- CONFIG_SYS_CONSOLE_IS_IN_ENV 3654 If the board specific function 3655 extern int overwrite_console (void); 3656 returns 1, the stdin, stderr and stdout are switched to the 3657 serial port, else the settings in the environment are used. 3658 3659- CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE 3660 Enable the call to overwrite_console(). 3661 3662- CONFIG_SYS_CONSOLE_ENV_OVERWRITE 3663 Enable overwrite of previous console environment settings. 3664 3665- CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END: 3666 Begin and End addresses of the area used by the 3667 simple memory test. 3668 3669- CONFIG_SYS_ALT_MEMTEST: 3670 Enable an alternate, more extensive memory test. 3671 3672- CONFIG_SYS_MEMTEST_SCRATCH: 3673 Scratch address used by the alternate memory test 3674 You only need to set this if address zero isn't writeable 3675 3676- CONFIG_SYS_MEM_RESERVE_SECURE 3677 Only implemented for ARMv8 for now. 3678 If defined, the size of CONFIG_SYS_MEM_RESERVE_SECURE memory 3679 is substracted from total RAM and won't be reported to OS. 3680 This memory can be used as secure memory. A variable 3681 gd->arch.secure_ram is used to track the location. In systems 3682 the RAM base is not zero, or RAM is divided into banks, 3683 this variable needs to be recalcuated to get the address. 3684 3685- CONFIG_SYS_MEM_TOP_HIDE: 3686 If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header, 3687 this specified memory area will get subtracted from the top 3688 (end) of RAM and won't get "touched" at all by U-Boot. By 3689 fixing up gd->ram_size the Linux kernel should gets passed 3690 the now "corrected" memory size and won't touch it either. 3691 This should work for arch/ppc and arch/powerpc. Only Linux 3692 board ports in arch/powerpc with bootwrapper support that 3693 recalculate the memory size from the SDRAM controller setup 3694 will have to get fixed in Linux additionally. 3695 3696 This option can be used as a workaround for the 440EPx/GRx 3697 CHIP 11 errata where the last 256 bytes in SDRAM shouldn't 3698 be touched. 3699 3700 WARNING: Please make sure that this value is a multiple of 3701 the Linux page size (normally 4k). If this is not the case, 3702 then the end address of the Linux memory will be located at a 3703 non page size aligned address and this could cause major 3704 problems. 3705 3706- CONFIG_SYS_LOADS_BAUD_CHANGE: 3707 Enable temporary baudrate change while serial download 3708 3709- CONFIG_SYS_SDRAM_BASE: 3710 Physical start address of SDRAM. _Must_ be 0 here. 3711 3712- CONFIG_SYS_FLASH_BASE: 3713 Physical start address of Flash memory. 3714 3715- CONFIG_SYS_MONITOR_BASE: 3716 Physical start address of boot monitor code (set by 3717 make config files to be same as the text base address 3718 (CONFIG_SYS_TEXT_BASE) used when linking) - same as 3719 CONFIG_SYS_FLASH_BASE when booting from flash. 3720 3721- CONFIG_SYS_MONITOR_LEN: 3722 Size of memory reserved for monitor code, used to 3723 determine _at_compile_time_ (!) if the environment is 3724 embedded within the U-Boot image, or in a separate 3725 flash sector. 3726 3727- CONFIG_SYS_MALLOC_LEN: 3728 Size of DRAM reserved for malloc() use. 3729 3730- CONFIG_SYS_MALLOC_F_LEN 3731 Size of the malloc() pool for use before relocation. If 3732 this is defined, then a very simple malloc() implementation 3733 will become available before relocation. The address is just 3734 below the global data, and the stack is moved down to make 3735 space. 3736 3737 This feature allocates regions with increasing addresses 3738 within the region. calloc() is supported, but realloc() 3739 is not available. free() is supported but does nothing. 3740 The memory will be freed (or in fact just forgotten) when 3741 U-Boot relocates itself. 3742 3743- CONFIG_SYS_MALLOC_SIMPLE 3744 Provides a simple and small malloc() and calloc() for those 3745 boards which do not use the full malloc in SPL (which is 3746 enabled with CONFIG_SYS_SPL_MALLOC_START). 3747 3748- CONFIG_SYS_NONCACHED_MEMORY: 3749 Size of non-cached memory area. This area of memory will be 3750 typically located right below the malloc() area and mapped 3751 uncached in the MMU. This is useful for drivers that would 3752 otherwise require a lot of explicit cache maintenance. For 3753 some drivers it's also impossible to properly maintain the 3754 cache. For example if the regions that need to be flushed 3755 are not a multiple of the cache-line size, *and* padding 3756 cannot be allocated between the regions to align them (i.e. 3757 if the HW requires a contiguous array of regions, and the 3758 size of each region is not cache-aligned), then a flush of 3759 one region may result in overwriting data that hardware has 3760 written to another region in the same cache-line. This can 3761 happen for example in network drivers where descriptors for 3762 buffers are typically smaller than the CPU cache-line (e.g. 3763 16 bytes vs. 32 or 64 bytes). 3764 3765 Non-cached memory is only supported on 32-bit ARM at present. 3766 3767- CONFIG_SYS_BOOTM_LEN: 3768 Normally compressed uImages are limited to an 3769 uncompressed size of 8 MBytes. If this is not enough, 3770 you can define CONFIG_SYS_BOOTM_LEN in your board config file 3771 to adjust this setting to your needs. 3772 3773- CONFIG_SYS_BOOTMAPSZ: 3774 Maximum size of memory mapped by the startup code of 3775 the Linux kernel; all data that must be processed by 3776 the Linux kernel (bd_info, boot arguments, FDT blob if 3777 used) must be put below this limit, unless "bootm_low" 3778 environment variable is defined and non-zero. In such case 3779 all data for the Linux kernel must be between "bootm_low" 3780 and "bootm_low" + CONFIG_SYS_BOOTMAPSZ. The environment 3781 variable "bootm_mapsize" will override the value of 3782 CONFIG_SYS_BOOTMAPSZ. If CONFIG_SYS_BOOTMAPSZ is undefined, 3783 then the value in "bootm_size" will be used instead. 3784 3785- CONFIG_SYS_BOOT_RAMDISK_HIGH: 3786 Enable initrd_high functionality. If defined then the 3787 initrd_high feature is enabled and the bootm ramdisk subcommand 3788 is enabled. 3789 3790- CONFIG_SYS_BOOT_GET_CMDLINE: 3791 Enables allocating and saving kernel cmdline in space between 3792 "bootm_low" and "bootm_low" + BOOTMAPSZ. 3793 3794- CONFIG_SYS_BOOT_GET_KBD: 3795 Enables allocating and saving a kernel copy of the bd_info in 3796 space between "bootm_low" and "bootm_low" + BOOTMAPSZ. 3797 3798- CONFIG_SYS_MAX_FLASH_BANKS: 3799 Max number of Flash memory banks 3800 3801- CONFIG_SYS_MAX_FLASH_SECT: 3802 Max number of sectors on a Flash chip 3803 3804- CONFIG_SYS_FLASH_ERASE_TOUT: 3805 Timeout for Flash erase operations (in ms) 3806 3807- CONFIG_SYS_FLASH_WRITE_TOUT: 3808 Timeout for Flash write operations (in ms) 3809 3810- CONFIG_SYS_FLASH_LOCK_TOUT 3811 Timeout for Flash set sector lock bit operation (in ms) 3812 3813- CONFIG_SYS_FLASH_UNLOCK_TOUT 3814 Timeout for Flash clear lock bits operation (in ms) 3815 3816- CONFIG_SYS_FLASH_PROTECTION 3817 If defined, hardware flash sectors protection is used 3818 instead of U-Boot software protection. 3819 3820- CONFIG_SYS_DIRECT_FLASH_TFTP: 3821 3822 Enable TFTP transfers directly to flash memory; 3823 without this option such a download has to be 3824 performed in two steps: (1) download to RAM, and (2) 3825 copy from RAM to flash. 3826 3827 The two-step approach is usually more reliable, since 3828 you can check if the download worked before you erase 3829 the flash, but in some situations (when system RAM is 3830 too limited to allow for a temporary copy of the 3831 downloaded image) this option may be very useful. 3832 3833- CONFIG_SYS_FLASH_CFI: 3834 Define if the flash driver uses extra elements in the 3835 common flash structure for storing flash geometry. 3836 3837- CONFIG_FLASH_CFI_DRIVER 3838 This option also enables the building of the cfi_flash driver 3839 in the drivers directory 3840 3841- CONFIG_FLASH_CFI_MTD 3842 This option enables the building of the cfi_mtd driver 3843 in the drivers directory. The driver exports CFI flash 3844 to the MTD layer. 3845 3846- CONFIG_SYS_FLASH_USE_BUFFER_WRITE 3847 Use buffered writes to flash. 3848 3849- CONFIG_FLASH_SPANSION_S29WS_N 3850 s29ws-n MirrorBit flash has non-standard addresses for buffered 3851 write commands. 3852 3853- CONFIG_SYS_FLASH_QUIET_TEST 3854 If this option is defined, the common CFI flash doesn't 3855 print it's warning upon not recognized FLASH banks. This 3856 is useful, if some of the configured banks are only 3857 optionally available. 3858 3859- CONFIG_FLASH_SHOW_PROGRESS 3860 If defined (must be an integer), print out countdown 3861 digits and dots. Recommended value: 45 (9..1) for 80 3862 column displays, 15 (3..1) for 40 column displays. 3863 3864- CONFIG_FLASH_VERIFY 3865 If defined, the content of the flash (destination) is compared 3866 against the source after the write operation. An error message 3867 will be printed when the contents are not identical. 3868 Please note that this option is useless in nearly all cases, 3869 since such flash programming errors usually are detected earlier 3870 while unprotecting/erasing/programming. Please only enable 3871 this option if you really know what you are doing. 3872 3873- CONFIG_SYS_RX_ETH_BUFFER: 3874 Defines the number of Ethernet receive buffers. On some 3875 Ethernet controllers it is recommended to set this value 3876 to 8 or even higher (EEPRO100 or 405 EMAC), since all 3877 buffers can be full shortly after enabling the interface 3878 on high Ethernet traffic. 3879 Defaults to 4 if not defined. 3880 3881- CONFIG_ENV_MAX_ENTRIES 3882 3883 Maximum number of entries in the hash table that is used 3884 internally to store the environment settings. The default 3885 setting is supposed to be generous and should work in most 3886 cases. This setting can be used to tune behaviour; see 3887 lib/hashtable.c for details. 3888 3889- CONFIG_ENV_FLAGS_LIST_DEFAULT 3890- CONFIG_ENV_FLAGS_LIST_STATIC 3891 Enable validation of the values given to environment variables when 3892 calling env set. Variables can be restricted to only decimal, 3893 hexadecimal, or boolean. If CONFIG_CMD_NET is also defined, 3894 the variables can also be restricted to IP address or MAC address. 3895 3896 The format of the list is: 3897 type_attribute = [s|d|x|b|i|m] 3898 access_attribute = [a|r|o|c] 3899 attributes = type_attribute[access_attribute] 3900 entry = variable_name[:attributes] 3901 list = entry[,list] 3902 3903 The type attributes are: 3904 s - String (default) 3905 d - Decimal 3906 x - Hexadecimal 3907 b - Boolean ([1yYtT|0nNfF]) 3908 i - IP address 3909 m - MAC address 3910 3911 The access attributes are: 3912 a - Any (default) 3913 r - Read-only 3914 o - Write-once 3915 c - Change-default 3916 3917 - CONFIG_ENV_FLAGS_LIST_DEFAULT 3918 Define this to a list (string) to define the ".flags" 3919 environment variable in the default or embedded environment. 3920 3921 - CONFIG_ENV_FLAGS_LIST_STATIC 3922 Define this to a list (string) to define validation that 3923 should be done if an entry is not found in the ".flags" 3924 environment variable. To override a setting in the static 3925 list, simply add an entry for the same variable name to the 3926 ".flags" variable. 3927 3928 If CONFIG_REGEX is defined, the variable_name above is evaluated as a 3929 regular expression. This allows multiple variables to define the same 3930 flags without explicitly listing them for each variable. 3931 3932- CONFIG_ENV_ACCESS_IGNORE_FORCE 3933 If defined, don't allow the -f switch to env set override variable 3934 access flags. 3935 3936- CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC (OMAP only) 3937 This is set by OMAP boards for the max time that reset should 3938 be asserted. See doc/README.omap-reset-time for details on how 3939 the value can be calculated on a given board. 3940 3941- CONFIG_USE_STDINT 3942 If stdint.h is available with your toolchain you can define this 3943 option to enable it. You can provide option 'USE_STDINT=1' when 3944 building U-Boot to enable this. 3945 3946The following definitions that deal with the placement and management 3947of environment data (variable area); in general, we support the 3948following configurations: 3949 3950- CONFIG_BUILD_ENVCRC: 3951 3952 Builds up envcrc with the target environment so that external utils 3953 may easily extract it and embed it in final U-Boot images. 3954 3955- CONFIG_ENV_IS_IN_FLASH: 3956 3957 Define this if the environment is in flash memory. 3958 3959 a) The environment occupies one whole flash sector, which is 3960 "embedded" in the text segment with the U-Boot code. This 3961 happens usually with "bottom boot sector" or "top boot 3962 sector" type flash chips, which have several smaller 3963 sectors at the start or the end. For instance, such a 3964 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In 3965 such a case you would place the environment in one of the 3966 4 kB sectors - with U-Boot code before and after it. With 3967 "top boot sector" type flash chips, you would put the 3968 environment in one of the last sectors, leaving a gap 3969 between U-Boot and the environment. 3970 3971 - CONFIG_ENV_OFFSET: 3972 3973 Offset of environment data (variable area) to the 3974 beginning of flash memory; for instance, with bottom boot 3975 type flash chips the second sector can be used: the offset 3976 for this sector is given here. 3977 3978 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE. 3979 3980 - CONFIG_ENV_ADDR: 3981 3982 This is just another way to specify the start address of 3983 the flash sector containing the environment (instead of 3984 CONFIG_ENV_OFFSET). 3985 3986 - CONFIG_ENV_SECT_SIZE: 3987 3988 Size of the sector containing the environment. 3989 3990 3991 b) Sometimes flash chips have few, equal sized, BIG sectors. 3992 In such a case you don't want to spend a whole sector for 3993 the environment. 3994 3995 - CONFIG_ENV_SIZE: 3996 3997 If you use this in combination with CONFIG_ENV_IS_IN_FLASH 3998 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part 3999 of this flash sector for the environment. This saves 4000 memory for the RAM copy of the environment. 4001 4002 It may also save flash memory if you decide to use this 4003 when your environment is "embedded" within U-Boot code, 4004 since then the remainder of the flash sector could be used 4005 for U-Boot code. It should be pointed out that this is 4006 STRONGLY DISCOURAGED from a robustness point of view: 4007 updating the environment in flash makes it always 4008 necessary to erase the WHOLE sector. If something goes 4009 wrong before the contents has been restored from a copy in 4010 RAM, your target system will be dead. 4011 4012 - CONFIG_ENV_ADDR_REDUND 4013 CONFIG_ENV_SIZE_REDUND 4014 4015 These settings describe a second storage area used to hold 4016 a redundant copy of the environment data, so that there is 4017 a valid backup copy in case there is a power failure during 4018 a "saveenv" operation. 4019 4020BE CAREFUL! Any changes to the flash layout, and some changes to the 4021source code will make it necessary to adapt <board>/u-boot.lds* 4022accordingly! 4023 4024 4025- CONFIG_ENV_IS_IN_NVRAM: 4026 4027 Define this if you have some non-volatile memory device 4028 (NVRAM, battery buffered SRAM) which you want to use for the 4029 environment. 4030 4031 - CONFIG_ENV_ADDR: 4032 - CONFIG_ENV_SIZE: 4033 4034 These two #defines are used to determine the memory area you 4035 want to use for environment. It is assumed that this memory 4036 can just be read and written to, without any special 4037 provision. 4038 4039BE CAREFUL! The first access to the environment happens quite early 4040in U-Boot initialization (when we try to get the setting of for the 4041console baudrate). You *MUST* have mapped your NVRAM area then, or 4042U-Boot will hang. 4043 4044Please note that even with NVRAM we still use a copy of the 4045environment in RAM: we could work on NVRAM directly, but we want to 4046keep settings there always unmodified except somebody uses "saveenv" 4047to save the current settings. 4048 4049 4050- CONFIG_ENV_IS_IN_EEPROM: 4051 4052 Use this if you have an EEPROM or similar serial access 4053 device and a driver for it. 4054 4055 - CONFIG_ENV_OFFSET: 4056 - CONFIG_ENV_SIZE: 4057 4058 These two #defines specify the offset and size of the 4059 environment area within the total memory of your EEPROM. 4060 4061 - CONFIG_SYS_I2C_EEPROM_ADDR: 4062 If defined, specified the chip address of the EEPROM device. 4063 The default address is zero. 4064 4065 - CONFIG_SYS_I2C_EEPROM_BUS: 4066 If defined, specified the i2c bus of the EEPROM device. 4067 4068 - CONFIG_SYS_EEPROM_PAGE_WRITE_BITS: 4069 If defined, the number of bits used to address bytes in a 4070 single page in the EEPROM device. A 64 byte page, for example 4071 would require six bits. 4072 4073 - CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS: 4074 If defined, the number of milliseconds to delay between 4075 page writes. The default is zero milliseconds. 4076 4077 - CONFIG_SYS_I2C_EEPROM_ADDR_LEN: 4078 The length in bytes of the EEPROM memory array address. Note 4079 that this is NOT the chip address length! 4080 4081 - CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW: 4082 EEPROM chips that implement "address overflow" are ones 4083 like Catalyst 24WC04/08/16 which has 9/10/11 bits of 4084 address and the extra bits end up in the "chip address" bit 4085 slots. This makes a 24WC08 (1Kbyte) chip look like four 256 4086 byte chips. 4087 4088 Note that we consider the length of the address field to 4089 still be one byte because the extra address bits are hidden 4090 in the chip address. 4091 4092 - CONFIG_SYS_EEPROM_SIZE: 4093 The size in bytes of the EEPROM device. 4094 4095 - CONFIG_ENV_EEPROM_IS_ON_I2C 4096 define this, if you have I2C and SPI activated, and your 4097 EEPROM, which holds the environment, is on the I2C bus. 4098 4099 - CONFIG_I2C_ENV_EEPROM_BUS 4100 if you have an Environment on an EEPROM reached over 4101 I2C muxes, you can define here, how to reach this 4102 EEPROM. For example: 4103 4104 #define CONFIG_I2C_ENV_EEPROM_BUS 1 4105 4106 EEPROM which holds the environment, is reached over 4107 a pca9547 i2c mux with address 0x70, channel 3. 4108 4109- CONFIG_ENV_IS_IN_DATAFLASH: 4110 4111 Define this if you have a DataFlash memory device which you 4112 want to use for the environment. 4113 4114 - CONFIG_ENV_OFFSET: 4115 - CONFIG_ENV_ADDR: 4116 - CONFIG_ENV_SIZE: 4117 4118 These three #defines specify the offset and size of the 4119 environment area within the total memory of your DataFlash placed 4120 at the specified address. 4121 4122- CONFIG_ENV_IS_IN_SPI_FLASH: 4123 4124 Define this if you have a SPI Flash memory device which you 4125 want to use for the environment. 4126 4127 - CONFIG_ENV_OFFSET: 4128 - CONFIG_ENV_SIZE: 4129 4130 These two #defines specify the offset and size of the 4131 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be 4132 aligned to an erase sector boundary. 4133 4134 - CONFIG_ENV_SECT_SIZE: 4135 4136 Define the SPI flash's sector size. 4137 4138 - CONFIG_ENV_OFFSET_REDUND (optional): 4139 4140 This setting describes a second storage area of CONFIG_ENV_SIZE 4141 size used to hold a redundant copy of the environment data, so 4142 that there is a valid backup copy in case there is a power failure 4143 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be 4144 aligned to an erase sector boundary. 4145 4146 - CONFIG_ENV_SPI_BUS (optional): 4147 - CONFIG_ENV_SPI_CS (optional): 4148 4149 Define the SPI bus and chip select. If not defined they will be 0. 4150 4151 - CONFIG_ENV_SPI_MAX_HZ (optional): 4152 4153 Define the SPI max work clock. If not defined then use 1MHz. 4154 4155 - CONFIG_ENV_SPI_MODE (optional): 4156 4157 Define the SPI work mode. If not defined then use SPI_MODE_3. 4158 4159- CONFIG_ENV_IS_IN_REMOTE: 4160 4161 Define this if you have a remote memory space which you 4162 want to use for the local device's environment. 4163 4164 - CONFIG_ENV_ADDR: 4165 - CONFIG_ENV_SIZE: 4166 4167 These two #defines specify the address and size of the 4168 environment area within the remote memory space. The 4169 local device can get the environment from remote memory 4170 space by SRIO or PCIE links. 4171 4172BE CAREFUL! For some special cases, the local device can not use 4173"saveenv" command. For example, the local device will get the 4174environment stored in a remote NOR flash by SRIO or PCIE link, 4175but it can not erase, write this NOR flash by SRIO or PCIE interface. 4176 4177- CONFIG_ENV_IS_IN_NAND: 4178 4179 Define this if you have a NAND device which you want to use 4180 for the environment. 4181 4182 - CONFIG_ENV_OFFSET: 4183 - CONFIG_ENV_SIZE: 4184 4185 These two #defines specify the offset and size of the environment 4186 area within the first NAND device. CONFIG_ENV_OFFSET must be 4187 aligned to an erase block boundary. 4188 4189 - CONFIG_ENV_OFFSET_REDUND (optional): 4190 4191 This setting describes a second storage area of CONFIG_ENV_SIZE 4192 size used to hold a redundant copy of the environment data, so 4193 that there is a valid backup copy in case there is a power failure 4194 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be 4195 aligned to an erase block boundary. 4196 4197 - CONFIG_ENV_RANGE (optional): 4198 4199 Specifies the length of the region in which the environment 4200 can be written. This should be a multiple of the NAND device's 4201 block size. Specifying a range with more erase blocks than 4202 are needed to hold CONFIG_ENV_SIZE allows bad blocks within 4203 the range to be avoided. 4204 4205 - CONFIG_ENV_OFFSET_OOB (optional): 4206 4207 Enables support for dynamically retrieving the offset of the 4208 environment from block zero's out-of-band data. The 4209 "nand env.oob" command can be used to record this offset. 4210 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when 4211 using CONFIG_ENV_OFFSET_OOB. 4212 4213- CONFIG_NAND_ENV_DST 4214 4215 Defines address in RAM to which the nand_spl code should copy the 4216 environment. If redundant environment is used, it will be copied to 4217 CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE. 4218 4219- CONFIG_ENV_IS_IN_UBI: 4220 4221 Define this if you have an UBI volume that you want to use for the 4222 environment. This has the benefit of wear-leveling the environment 4223 accesses, which is important on NAND. 4224 4225 - CONFIG_ENV_UBI_PART: 4226 4227 Define this to a string that is the mtd partition containing the UBI. 4228 4229 - CONFIG_ENV_UBI_VOLUME: 4230 4231 Define this to the name of the volume that you want to store the 4232 environment in. 4233 4234 - CONFIG_ENV_UBI_VOLUME_REDUND: 4235 4236 Define this to the name of another volume to store a second copy of 4237 the environment in. This will enable redundant environments in UBI. 4238 It is assumed that both volumes are in the same MTD partition. 4239 4240 - CONFIG_UBI_SILENCE_MSG 4241 - CONFIG_UBIFS_SILENCE_MSG 4242 4243 You will probably want to define these to avoid a really noisy system 4244 when storing the env in UBI. 4245 4246- CONFIG_ENV_IS_IN_FAT: 4247 Define this if you want to use the FAT file system for the environment. 4248 4249 - FAT_ENV_INTERFACE: 4250 4251 Define this to a string that is the name of the block device. 4252 4253 - FAT_ENV_DEV_AND_PART: 4254 4255 Define this to a string to specify the partition of the device. It can 4256 be as following: 4257 4258 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1) 4259 - "D:P": device D partition P. Error occurs if device D has no 4260 partition table. 4261 - "D:0": device D. 4262 - "D" or "D:": device D partition 1 if device D has partition 4263 table, or the whole device D if has no partition 4264 table. 4265 - "D:auto": first partition in device D with bootable flag set. 4266 If none, first valid partition in device D. If no 4267 partition table then means device D. 4268 4269 - FAT_ENV_FILE: 4270 4271 It's a string of the FAT file name. This file use to store the 4272 environment. 4273 4274 - CONFIG_FAT_WRITE: 4275 This should be defined. Otherwise it cannot save the environment file. 4276 4277- CONFIG_ENV_IS_IN_MMC: 4278 4279 Define this if you have an MMC device which you want to use for the 4280 environment. 4281 4282 - CONFIG_SYS_MMC_ENV_DEV: 4283 4284 Specifies which MMC device the environment is stored in. 4285 4286 - CONFIG_SYS_MMC_ENV_PART (optional): 4287 4288 Specifies which MMC partition the environment is stored in. If not 4289 set, defaults to partition 0, the user area. Common values might be 4290 1 (first MMC boot partition), 2 (second MMC boot partition). 4291 4292 - CONFIG_ENV_OFFSET: 4293 - CONFIG_ENV_SIZE: 4294 4295 These two #defines specify the offset and size of the environment 4296 area within the specified MMC device. 4297 4298 If offset is positive (the usual case), it is treated as relative to 4299 the start of the MMC partition. If offset is negative, it is treated 4300 as relative to the end of the MMC partition. This can be useful if 4301 your board may be fitted with different MMC devices, which have 4302 different sizes for the MMC partitions, and you always want the 4303 environment placed at the very end of the partition, to leave the 4304 maximum possible space before it, to store other data. 4305 4306 These two values are in units of bytes, but must be aligned to an 4307 MMC sector boundary. 4308 4309 - CONFIG_ENV_OFFSET_REDUND (optional): 4310 4311 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to 4312 hold a redundant copy of the environment data. This provides a 4313 valid backup copy in case the other copy is corrupted, e.g. due 4314 to a power failure during a "saveenv" operation. 4315 4316 This value may also be positive or negative; this is handled in the 4317 same way as CONFIG_ENV_OFFSET. 4318 4319 This value is also in units of bytes, but must also be aligned to 4320 an MMC sector boundary. 4321 4322 - CONFIG_ENV_SIZE_REDUND (optional): 4323 4324 This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is 4325 set. If this value is set, it must be set to the same value as 4326 CONFIG_ENV_SIZE. 4327 4328- CONFIG_SYS_SPI_INIT_OFFSET 4329 4330 Defines offset to the initial SPI buffer area in DPRAM. The 4331 area is used at an early stage (ROM part) if the environment 4332 is configured to reside in the SPI EEPROM: We need a 520 byte 4333 scratch DPRAM area. It is used between the two initialization 4334 calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems 4335 to be a good choice since it makes it far enough from the 4336 start of the data area as well as from the stack pointer. 4337 4338Please note that the environment is read-only until the monitor 4339has been relocated to RAM and a RAM copy of the environment has been 4340created; also, when using EEPROM you will have to use getenv_f() 4341until then to read environment variables. 4342 4343The environment is protected by a CRC32 checksum. Before the monitor 4344is relocated into RAM, as a result of a bad CRC you will be working 4345with the compiled-in default environment - *silently*!!! [This is 4346necessary, because the first environment variable we need is the 4347"baudrate" setting for the console - if we have a bad CRC, we don't 4348have any device yet where we could complain.] 4349 4350Note: once the monitor has been relocated, then it will complain if 4351the default environment is used; a new CRC is computed as soon as you 4352use the "saveenv" command to store a valid environment. 4353 4354- CONFIG_SYS_FAULT_ECHO_LINK_DOWN: 4355 Echo the inverted Ethernet link state to the fault LED. 4356 4357 Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR 4358 also needs to be defined. 4359 4360- CONFIG_SYS_FAULT_MII_ADDR: 4361 MII address of the PHY to check for the Ethernet link state. 4362 4363- CONFIG_NS16550_MIN_FUNCTIONS: 4364 Define this if you desire to only have use of the NS16550_init 4365 and NS16550_putc functions for the serial driver located at 4366 drivers/serial/ns16550.c. This option is useful for saving 4367 space for already greatly restricted images, including but not 4368 limited to NAND_SPL configurations. 4369 4370- CONFIG_DISPLAY_BOARDINFO 4371 Display information about the board that U-Boot is running on 4372 when U-Boot starts up. The board function checkboard() is called 4373 to do this. 4374 4375- CONFIG_DISPLAY_BOARDINFO_LATE 4376 Similar to the previous option, but display this information 4377 later, once stdio is running and output goes to the LCD, if 4378 present. 4379 4380- CONFIG_BOARD_SIZE_LIMIT: 4381 Maximum size of the U-Boot image. When defined, the 4382 build system checks that the actual size does not 4383 exceed it. 4384 4385Low Level (hardware related) configuration options: 4386--------------------------------------------------- 4387 4388- CONFIG_SYS_CACHELINE_SIZE: 4389 Cache Line Size of the CPU. 4390 4391- CONFIG_SYS_DEFAULT_IMMR: 4392 Default address of the IMMR after system reset. 4393 4394 Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU, 4395 and RPXsuper) to be able to adjust the position of 4396 the IMMR register after a reset. 4397 4398- CONFIG_SYS_CCSRBAR_DEFAULT: 4399 Default (power-on reset) physical address of CCSR on Freescale 4400 PowerPC SOCs. 4401 4402- CONFIG_SYS_CCSRBAR: 4403 Virtual address of CCSR. On a 32-bit build, this is typically 4404 the same value as CONFIG_SYS_CCSRBAR_DEFAULT. 4405 4406 CONFIG_SYS_DEFAULT_IMMR must also be set to this value, 4407 for cross-platform code that uses that macro instead. 4408 4409- CONFIG_SYS_CCSRBAR_PHYS: 4410 Physical address of CCSR. CCSR can be relocated to a new 4411 physical address, if desired. In this case, this macro should 4412 be set to that address. Otherwise, it should be set to the 4413 same value as CONFIG_SYS_CCSRBAR_DEFAULT. For example, CCSR 4414 is typically relocated on 36-bit builds. It is recommended 4415 that this macro be defined via the _HIGH and _LOW macros: 4416 4417 #define CONFIG_SYS_CCSRBAR_PHYS ((CONFIG_SYS_CCSRBAR_PHYS_HIGH 4418 * 1ull) << 32 | CONFIG_SYS_CCSRBAR_PHYS_LOW) 4419 4420- CONFIG_SYS_CCSRBAR_PHYS_HIGH: 4421 Bits 33-36 of CONFIG_SYS_CCSRBAR_PHYS. This value is typically 4422 either 0 (32-bit build) or 0xF (36-bit build). This macro is 4423 used in assembly code, so it must not contain typecasts or 4424 integer size suffixes (e.g. "ULL"). 4425 4426- CONFIG_SYS_CCSRBAR_PHYS_LOW: 4427 Lower 32-bits of CONFIG_SYS_CCSRBAR_PHYS. This macro is 4428 used in assembly code, so it must not contain typecasts or 4429 integer size suffixes (e.g. "ULL"). 4430 4431- CONFIG_SYS_CCSR_DO_NOT_RELOCATE: 4432 If this macro is defined, then CONFIG_SYS_CCSRBAR_PHYS will be 4433 forced to a value that ensures that CCSR is not relocated. 4434 4435- Floppy Disk Support: 4436 CONFIG_SYS_FDC_DRIVE_NUMBER 4437 4438 the default drive number (default value 0) 4439 4440 CONFIG_SYS_ISA_IO_STRIDE 4441 4442 defines the spacing between FDC chipset registers 4443 (default value 1) 4444 4445 CONFIG_SYS_ISA_IO_OFFSET 4446 4447 defines the offset of register from address. It 4448 depends on which part of the data bus is connected to 4449 the FDC chipset. (default value 0) 4450 4451 If CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and 4452 CONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their 4453 default value. 4454 4455 if CONFIG_SYS_FDC_HW_INIT is defined, then the function 4456 fdc_hw_init() is called at the beginning of the FDC 4457 setup. fdc_hw_init() must be provided by the board 4458 source code. It is used to make hardware-dependent 4459 initializations. 4460 4461- CONFIG_IDE_AHB: 4462 Most IDE controllers were designed to be connected with PCI 4463 interface. Only few of them were designed for AHB interface. 4464 When software is doing ATA command and data transfer to 4465 IDE devices through IDE-AHB controller, some additional 4466 registers accessing to these kind of IDE-AHB controller 4467 is required. 4468 4469- CONFIG_SYS_IMMR: Physical address of the Internal Memory. 4470 DO NOT CHANGE unless you know exactly what you're 4471 doing! (11-4) [MPC8xx/82xx systems only] 4472 4473- CONFIG_SYS_INIT_RAM_ADDR: 4474 4475 Start address of memory area that can be used for 4476 initial data and stack; please note that this must be 4477 writable memory that is working WITHOUT special 4478 initialization, i. e. you CANNOT use normal RAM which 4479 will become available only after programming the 4480 memory controller and running certain initialization 4481 sequences. 4482 4483 U-Boot uses the following memory types: 4484 - MPC8xx and MPC8260: IMMR (internal memory of the CPU) 4485 - MPC824X: data cache 4486 - PPC4xx: data cache 4487 4488- CONFIG_SYS_GBL_DATA_OFFSET: 4489 4490 Offset of the initial data structure in the memory 4491 area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually 4492 CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial 4493 data is located at the end of the available space 4494 (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE - 4495 CONFIG_SYS_INIT_DATA_SIZE), and the initial stack is just 4496 below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR + 4497 CONFIG_SYS_GBL_DATA_OFFSET) downward. 4498 4499 Note: 4500 On the MPC824X (or other systems that use the data 4501 cache for initial memory) the address chosen for 4502 CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must 4503 point to an otherwise UNUSED address space between 4504 the top of RAM and the start of the PCI space. 4505 4506- CONFIG_SYS_SIUMCR: SIU Module Configuration (11-6) 4507 4508- CONFIG_SYS_SYPCR: System Protection Control (11-9) 4509 4510- CONFIG_SYS_TBSCR: Time Base Status and Control (11-26) 4511 4512- CONFIG_SYS_PISCR: Periodic Interrupt Status and Control (11-31) 4513 4514- CONFIG_SYS_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30) 4515 4516- CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27) 4517 4518- CONFIG_SYS_OR_TIMING_SDRAM: 4519 SDRAM timing 4520 4521- CONFIG_SYS_MAMR_PTA: 4522 periodic timer for refresh 4523 4524- CONFIG_SYS_DER: Debug Event Register (37-47) 4525 4526- FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM, 4527 CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP, 4528 CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM, 4529 CONFIG_SYS_BR1_PRELIM: 4530 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH) 4531 4532- SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE, 4533 CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM, 4534 CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM: 4535 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM) 4536 4537- CONFIG_SYS_MAMR_PTA, CONFIG_SYS_MPTPR_2BK_4K, CONFIG_SYS_MPTPR_1BK_4K, CONFIG_SYS_MPTPR_2BK_8K, 4538 CONFIG_SYS_MPTPR_1BK_8K, CONFIG_SYS_MAMR_8COL, CONFIG_SYS_MAMR_9COL: 4539 Machine Mode Register and Memory Periodic Timer 4540 Prescaler definitions (SDRAM timing) 4541 4542- CONFIG_SYS_I2C_UCODE_PATCH, CONFIG_SYS_I2C_DPMEM_OFFSET [0x1FC0]: 4543 enable I2C microcode relocation patch (MPC8xx); 4544 define relocation offset in DPRAM [DSP2] 4545 4546- CONFIG_SYS_SMC_UCODE_PATCH, CONFIG_SYS_SMC_DPMEM_OFFSET [0x1FC0]: 4547 enable SMC microcode relocation patch (MPC8xx); 4548 define relocation offset in DPRAM [SMC1] 4549 4550- CONFIG_SYS_SPI_UCODE_PATCH, CONFIG_SYS_SPI_DPMEM_OFFSET [0x1FC0]: 4551 enable SPI microcode relocation patch (MPC8xx); 4552 define relocation offset in DPRAM [SCC4] 4553 4554- CONFIG_SYS_USE_OSCCLK: 4555 Use OSCM clock mode on MBX8xx board. Be careful, 4556 wrong setting might damage your board. Read 4557 doc/README.MBX before setting this variable! 4558 4559- CONFIG_SYS_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only) 4560 Offset of the bootmode word in DPRAM used by post 4561 (Power On Self Tests). This definition overrides 4562 #define'd default value in commproc.h resp. 4563 cpm_8260.h. 4564 4565- CONFIG_SYS_PCI_SLV_MEM_LOCAL, CONFIG_SYS_PCI_SLV_MEM_BUS, CONFIG_SYS_PICMR0_MASK_ATTRIB, 4566 CONFIG_SYS_PCI_MSTR0_LOCAL, CONFIG_SYS_PCIMSK0_MASK, CONFIG_SYS_PCI_MSTR1_LOCAL, 4567 CONFIG_SYS_PCIMSK1_MASK, CONFIG_SYS_PCI_MSTR_MEM_LOCAL, CONFIG_SYS_PCI_MSTR_MEM_BUS, 4568 CONFIG_SYS_CPU_PCI_MEM_START, CONFIG_SYS_PCI_MSTR_MEM_SIZE, CONFIG_SYS_POCMR0_MASK_ATTRIB, 4569 CONFIG_SYS_PCI_MSTR_MEMIO_LOCAL, CONFIG_SYS_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START, 4570 CONFIG_SYS_PCI_MSTR_MEMIO_SIZE, CONFIG_SYS_POCMR1_MASK_ATTRIB, CONFIG_SYS_PCI_MSTR_IO_LOCAL, 4571 CONFIG_SYS_PCI_MSTR_IO_BUS, CONFIG_SYS_CPU_PCI_IO_START, CONFIG_SYS_PCI_MSTR_IO_SIZE, 4572 CONFIG_SYS_POCMR2_MASK_ATTRIB: (MPC826x only) 4573 Overrides the default PCI memory map in arch/powerpc/cpu/mpc8260/pci.c if set. 4574 4575- CONFIG_PCI_DISABLE_PCIE: 4576 Disable PCI-Express on systems where it is supported but not 4577 required. 4578 4579- CONFIG_PCI_ENUM_ONLY 4580 Only scan through and get the devices on the buses. 4581 Don't do any setup work, presumably because someone or 4582 something has already done it, and we don't need to do it 4583 a second time. Useful for platforms that are pre-booted 4584 by coreboot or similar. 4585 4586- CONFIG_PCI_INDIRECT_BRIDGE: 4587 Enable support for indirect PCI bridges. 4588 4589- CONFIG_SYS_SRIO: 4590 Chip has SRIO or not 4591 4592- CONFIG_SRIO1: 4593 Board has SRIO 1 port available 4594 4595- CONFIG_SRIO2: 4596 Board has SRIO 2 port available 4597 4598- CONFIG_SRIO_PCIE_BOOT_MASTER 4599 Board can support master function for Boot from SRIO and PCIE 4600 4601- CONFIG_SYS_SRIOn_MEM_VIRT: 4602 Virtual Address of SRIO port 'n' memory region 4603 4604- CONFIG_SYS_SRIOn_MEM_PHYS: 4605 Physical Address of SRIO port 'n' memory region 4606 4607- CONFIG_SYS_SRIOn_MEM_SIZE: 4608 Size of SRIO port 'n' memory region 4609 4610- CONFIG_SYS_NAND_BUSWIDTH_16BIT 4611 Defined to tell the NAND controller that the NAND chip is using 4612 a 16 bit bus. 4613 Not all NAND drivers use this symbol. 4614 Example of drivers that use it: 4615 - drivers/mtd/nand/ndfc.c 4616 - drivers/mtd/nand/mxc_nand.c 4617 4618- CONFIG_SYS_NDFC_EBC0_CFG 4619 Sets the EBC0_CFG register for the NDFC. If not defined 4620 a default value will be used. 4621 4622- CONFIG_SPD_EEPROM 4623 Get DDR timing information from an I2C EEPROM. Common 4624 with pluggable memory modules such as SODIMMs 4625 4626 SPD_EEPROM_ADDRESS 4627 I2C address of the SPD EEPROM 4628 4629- CONFIG_SYS_SPD_BUS_NUM 4630 If SPD EEPROM is on an I2C bus other than the first 4631 one, specify here. Note that the value must resolve 4632 to something your driver can deal with. 4633 4634- CONFIG_SYS_DDR_RAW_TIMING 4635 Get DDR timing information from other than SPD. Common with 4636 soldered DDR chips onboard without SPD. DDR raw timing 4637 parameters are extracted from datasheet and hard-coded into 4638 header files or board specific files. 4639 4640- CONFIG_FSL_DDR_INTERACTIVE 4641 Enable interactive DDR debugging. See doc/README.fsl-ddr. 4642 4643- CONFIG_FSL_DDR_SYNC_REFRESH 4644 Enable sync of refresh for multiple controllers. 4645 4646- CONFIG_FSL_DDR_BIST 4647 Enable built-in memory test for Freescale DDR controllers. 4648 4649- CONFIG_SYS_83XX_DDR_USES_CS0 4650 Only for 83xx systems. If specified, then DDR should 4651 be configured using CS0 and CS1 instead of CS2 and CS3. 4652 4653- CONFIG_ETHER_ON_FEC[12] 4654 Define to enable FEC[12] on a 8xx series processor. 4655 4656- CONFIG_FEC[12]_PHY 4657 Define to the hardcoded PHY address which corresponds 4658 to the given FEC; i. e. 4659 #define CONFIG_FEC1_PHY 4 4660 means that the PHY with address 4 is connected to FEC1 4661 4662 When set to -1, means to probe for first available. 4663 4664- CONFIG_FEC[12]_PHY_NORXERR 4665 The PHY does not have a RXERR line (RMII only). 4666 (so program the FEC to ignore it). 4667 4668- CONFIG_RMII 4669 Enable RMII mode for all FECs. 4670 Note that this is a global option, we can't 4671 have one FEC in standard MII mode and another in RMII mode. 4672 4673- CONFIG_CRC32_VERIFY 4674 Add a verify option to the crc32 command. 4675 The syntax is: 4676 4677 => crc32 -v <address> <count> <crc32> 4678 4679 Where address/count indicate a memory area 4680 and crc32 is the correct crc32 which the 4681 area should have. 4682 4683- CONFIG_LOOPW 4684 Add the "loopw" memory command. This only takes effect if 4685 the memory commands are activated globally (CONFIG_CMD_MEM). 4686 4687- CONFIG_MX_CYCLIC 4688 Add the "mdc" and "mwc" memory commands. These are cyclic 4689 "md/mw" commands. 4690 Examples: 4691 4692 => mdc.b 10 4 500 4693 This command will print 4 bytes (10,11,12,13) each 500 ms. 4694 4695 => mwc.l 100 12345678 10 4696 This command will write 12345678 to address 100 all 10 ms. 4697 4698 This only takes effect if the memory commands are activated 4699 globally (CONFIG_CMD_MEM). 4700 4701- CONFIG_SKIP_LOWLEVEL_INIT 4702 [ARM, NDS32, MIPS only] If this variable is defined, then certain 4703 low level initializations (like setting up the memory 4704 controller) are omitted and/or U-Boot does not 4705 relocate itself into RAM. 4706 4707 Normally this variable MUST NOT be defined. The only 4708 exception is when U-Boot is loaded (to RAM) by some 4709 other boot loader or by a debugger which performs 4710 these initializations itself. 4711 4712- CONFIG_SKIP_LOWLEVEL_INIT_ONLY 4713 [ARM926EJ-S only] This allows just the call to lowlevel_init() 4714 to be skipped. The normal CP15 init (such as enabling the 4715 instruction cache) is still performed. 4716 4717- CONFIG_SPL_BUILD 4718 Modifies the behaviour of start.S when compiling a loader 4719 that is executed before the actual U-Boot. E.g. when 4720 compiling a NAND SPL. 4721 4722- CONFIG_TPL_BUILD 4723 Modifies the behaviour of start.S when compiling a loader 4724 that is executed after the SPL and before the actual U-Boot. 4725 It is loaded by the SPL. 4726 4727- CONFIG_SYS_MPC85XX_NO_RESETVEC 4728 Only for 85xx systems. If this variable is specified, the section 4729 .resetvec is not kept and the section .bootpg is placed in the 4730 previous 4k of the .text section. 4731 4732- CONFIG_ARCH_MAP_SYSMEM 4733 Generally U-Boot (and in particular the md command) uses 4734 effective address. It is therefore not necessary to regard 4735 U-Boot address as virtual addresses that need to be translated 4736 to physical addresses. However, sandbox requires this, since 4737 it maintains its own little RAM buffer which contains all 4738 addressable memory. This option causes some memory accesses 4739 to be mapped through map_sysmem() / unmap_sysmem(). 4740 4741- CONFIG_USE_ARCH_MEMCPY 4742 CONFIG_USE_ARCH_MEMSET 4743 If these options are used a optimized version of memcpy/memset will 4744 be used if available. These functions may be faster under some 4745 conditions but may increase the binary size. 4746 4747- CONFIG_X86_RESET_VECTOR 4748 If defined, the x86 reset vector code is included. This is not 4749 needed when U-Boot is running from Coreboot. 4750 4751- CONFIG_SYS_MPUCLK 4752 Defines the MPU clock speed (in MHz). 4753 4754 NOTE : currently only supported on AM335x platforms. 4755 4756- CONFIG_SPL_AM33XX_ENABLE_RTC32K_OSC: 4757 Enables the RTC32K OSC on AM33xx based plattforms 4758 4759- CONFIG_SYS_NAND_NO_SUBPAGE_WRITE 4760 Option to disable subpage write in NAND driver 4761 driver that uses this: 4762 drivers/mtd/nand/davinci_nand.c 4763 4764Freescale QE/FMAN Firmware Support: 4765----------------------------------- 4766 4767The Freescale QUICCEngine (QE) and Frame Manager (FMAN) both support the 4768loading of "firmware", which is encoded in the QE firmware binary format. 4769This firmware often needs to be loaded during U-Boot booting, so macros 4770are used to identify the storage device (NOR flash, SPI, etc) and the address 4771within that device. 4772 4773- CONFIG_SYS_FMAN_FW_ADDR 4774 The address in the storage device where the FMAN microcode is located. The 4775 meaning of this address depends on which CONFIG_SYS_QE_FW_IN_xxx macro 4776 is also specified. 4777 4778- CONFIG_SYS_QE_FW_ADDR 4779 The address in the storage device where the QE microcode is located. The 4780 meaning of this address depends on which CONFIG_SYS_QE_FW_IN_xxx macro 4781 is also specified. 4782 4783- CONFIG_SYS_QE_FMAN_FW_LENGTH 4784 The maximum possible size of the firmware. The firmware binary format 4785 has a field that specifies the actual size of the firmware, but it 4786 might not be possible to read any part of the firmware unless some 4787 local storage is allocated to hold the entire firmware first. 4788 4789- CONFIG_SYS_QE_FMAN_FW_IN_NOR 4790 Specifies that QE/FMAN firmware is located in NOR flash, mapped as 4791 normal addressable memory via the LBC. CONFIG_SYS_FMAN_FW_ADDR is the 4792 virtual address in NOR flash. 4793 4794- CONFIG_SYS_QE_FMAN_FW_IN_NAND 4795 Specifies that QE/FMAN firmware is located in NAND flash. 4796 CONFIG_SYS_FMAN_FW_ADDR is the offset within NAND flash. 4797 4798- CONFIG_SYS_QE_FMAN_FW_IN_MMC 4799 Specifies that QE/FMAN firmware is located on the primary SD/MMC 4800 device. CONFIG_SYS_FMAN_FW_ADDR is the byte offset on that device. 4801 4802- CONFIG_SYS_QE_FMAN_FW_IN_REMOTE 4803 Specifies that QE/FMAN firmware is located in the remote (master) 4804 memory space. CONFIG_SYS_FMAN_FW_ADDR is a virtual address which 4805 can be mapped from slave TLB->slave LAW->slave SRIO or PCIE outbound 4806 window->master inbound window->master LAW->the ucode address in 4807 master's memory space. 4808 4809Freescale Layerscape Management Complex Firmware Support: 4810--------------------------------------------------------- 4811The Freescale Layerscape Management Complex (MC) supports the loading of 4812"firmware". 4813This firmware often needs to be loaded during U-Boot booting, so macros 4814are used to identify the storage device (NOR flash, SPI, etc) and the address 4815within that device. 4816 4817- CONFIG_FSL_MC_ENET 4818 Enable the MC driver for Layerscape SoCs. 4819 4820Freescale Layerscape Debug Server Support: 4821------------------------------------------- 4822The Freescale Layerscape Debug Server Support supports the loading of 4823"Debug Server firmware" and triggering SP boot-rom. 4824This firmware often needs to be loaded during U-Boot booting. 4825 4826- CONFIG_SYS_MC_RSV_MEM_ALIGN 4827 Define alignment of reserved memory MC requires 4828 4829Reproducible builds 4830------------------- 4831 4832In order to achieve reproducible builds, timestamps used in the U-Boot build 4833process have to be set to a fixed value. 4834 4835This is done using the SOURCE_DATE_EPOCH environment variable. 4836SOURCE_DATE_EPOCH is to be set on the build host's shell, not as a configuration 4837option for U-Boot or an environment variable in U-Boot. 4838 4839SOURCE_DATE_EPOCH should be set to a number of seconds since the epoch, in UTC. 4840 4841Building the Software: 4842====================== 4843 4844Building U-Boot has been tested in several native build environments 4845and in many different cross environments. Of course we cannot support 4846all possibly existing versions of cross development tools in all 4847(potentially obsolete) versions. In case of tool chain problems we 4848recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK) 4849which is extensively used to build and test U-Boot. 4850 4851If you are not using a native environment, it is assumed that you 4852have GNU cross compiling tools available in your path. In this case, 4853you must set the environment variable CROSS_COMPILE in your shell. 4854Note that no changes to the Makefile or any other source files are 4855necessary. For example using the ELDK on a 4xx CPU, please enter: 4856 4857 $ CROSS_COMPILE=ppc_4xx- 4858 $ export CROSS_COMPILE 4859 4860Note: If you wish to generate Windows versions of the utilities in 4861 the tools directory you can use the MinGW toolchain 4862 (http://www.mingw.org). Set your HOST tools to the MinGW 4863 toolchain and execute 'make tools'. For example: 4864 4865 $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools 4866 4867 Binaries such as tools/mkimage.exe will be created which can 4868 be executed on computers running Windows. 4869 4870U-Boot is intended to be simple to build. After installing the 4871sources you must configure U-Boot for one specific board type. This 4872is done by typing: 4873 4874 make NAME_defconfig 4875 4876where "NAME_defconfig" is the name of one of the existing configu- 4877rations; see boards.cfg for supported names. 4878 4879Note: for some board special configuration names may exist; check if 4880 additional information is available from the board vendor; for 4881 instance, the TQM823L systems are available without (standard) 4882 or with LCD support. You can select such additional "features" 4883 when choosing the configuration, i. e. 4884 4885 make TQM823L_defconfig 4886 - will configure for a plain TQM823L, i. e. no LCD support 4887 4888 make TQM823L_LCD_defconfig 4889 - will configure for a TQM823L with U-Boot console on LCD 4890 4891 etc. 4892 4893 4894Finally, type "make all", and you should get some working U-Boot 4895images ready for download to / installation on your system: 4896 4897- "u-boot.bin" is a raw binary image 4898- "u-boot" is an image in ELF binary format 4899- "u-boot.srec" is in Motorola S-Record format 4900 4901By default the build is performed locally and the objects are saved 4902in the source directory. One of the two methods can be used to change 4903this behavior and build U-Boot to some external directory: 4904 49051. Add O= to the make command line invocations: 4906 4907 make O=/tmp/build distclean 4908 make O=/tmp/build NAME_defconfig 4909 make O=/tmp/build all 4910 49112. Set environment variable KBUILD_OUTPUT to point to the desired location: 4912 4913 export KBUILD_OUTPUT=/tmp/build 4914 make distclean 4915 make NAME_defconfig 4916 make all 4917 4918Note that the command line "O=" setting overrides the KBUILD_OUTPUT environment 4919variable. 4920 4921 4922Please be aware that the Makefiles assume you are using GNU make, so 4923for instance on NetBSD you might need to use "gmake" instead of 4924native "make". 4925 4926 4927If the system board that you have is not listed, then you will need 4928to port U-Boot to your hardware platform. To do this, follow these 4929steps: 4930 49311. Create a new directory to hold your board specific code. Add any 4932 files you need. In your board directory, you will need at least 4933 the "Makefile" and a "<board>.c". 49342. Create a new configuration file "include/configs/<board>.h" for 4935 your board. 49363. If you're porting U-Boot to a new CPU, then also create a new 4937 directory to hold your CPU specific code. Add any files you need. 49384. Run "make <board>_defconfig" with your new name. 49395. Type "make", and you should get a working "u-boot.srec" file 4940 to be installed on your target system. 49416. Debug and solve any problems that might arise. 4942 [Of course, this last step is much harder than it sounds.] 4943 4944 4945Testing of U-Boot Modifications, Ports to New Hardware, etc.: 4946============================================================== 4947 4948If you have modified U-Boot sources (for instance added a new board 4949or support for new devices, a new CPU, etc.) you are expected to 4950provide feedback to the other developers. The feedback normally takes 4951the form of a "patch", i. e. a context diff against a certain (latest 4952official or latest in the git repository) version of U-Boot sources. 4953 4954But before you submit such a patch, please verify that your modifi- 4955cation did not break existing code. At least make sure that *ALL* of 4956the supported boards compile WITHOUT ANY compiler warnings. To do so, 4957just run the buildman script (tools/buildman/buildman), which will 4958configure and build U-Boot for ALL supported system. Be warned, this 4959will take a while. Please see the buildman README, or run 'buildman -H' 4960for documentation. 4961 4962 4963See also "U-Boot Porting Guide" below. 4964 4965 4966Monitor Commands - Overview: 4967============================ 4968 4969go - start application at address 'addr' 4970run - run commands in an environment variable 4971bootm - boot application image from memory 4972bootp - boot image via network using BootP/TFTP protocol 4973bootz - boot zImage from memory 4974tftpboot- boot image via network using TFTP protocol 4975 and env variables "ipaddr" and "serverip" 4976 (and eventually "gatewayip") 4977tftpput - upload a file via network using TFTP protocol 4978rarpboot- boot image via network using RARP/TFTP protocol 4979diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd' 4980loads - load S-Record file over serial line 4981loadb - load binary file over serial line (kermit mode) 4982md - memory display 4983mm - memory modify (auto-incrementing) 4984nm - memory modify (constant address) 4985mw - memory write (fill) 4986cp - memory copy 4987cmp - memory compare 4988crc32 - checksum calculation 4989i2c - I2C sub-system 4990sspi - SPI utility commands 4991base - print or set address offset 4992printenv- print environment variables 4993setenv - set environment variables 4994saveenv - save environment variables to persistent storage 4995protect - enable or disable FLASH write protection 4996erase - erase FLASH memory 4997flinfo - print FLASH memory information 4998nand - NAND memory operations (see doc/README.nand) 4999bdinfo - print Board Info structure 5000iminfo - print header information for application image 5001coninfo - print console devices and informations 5002ide - IDE sub-system 5003loop - infinite loop on address range 5004loopw - infinite write loop on address range 5005mtest - simple RAM test 5006icache - enable or disable instruction cache 5007dcache - enable or disable data cache 5008reset - Perform RESET of the CPU 5009echo - echo args to console 5010version - print monitor version 5011help - print online help 5012? - alias for 'help' 5013 5014 5015Monitor Commands - Detailed Description: 5016======================================== 5017 5018TODO. 5019 5020For now: just type "help <command>". 5021 5022 5023Environment Variables: 5024====================== 5025 5026U-Boot supports user configuration using Environment Variables which 5027can be made persistent by saving to Flash memory. 5028 5029Environment Variables are set using "setenv", printed using 5030"printenv", and saved to Flash using "saveenv". Using "setenv" 5031without a value can be used to delete a variable from the 5032environment. As long as you don't save the environment you are 5033working with an in-memory copy. In case the Flash area containing the 5034environment is erased by accident, a default environment is provided. 5035 5036Some configuration options can be set using Environment Variables. 5037 5038List of environment variables (most likely not complete): 5039 5040 baudrate - see CONFIG_BAUDRATE 5041 5042 bootdelay - see CONFIG_BOOTDELAY 5043 5044 bootcmd - see CONFIG_BOOTCOMMAND 5045 5046 bootargs - Boot arguments when booting an RTOS image 5047 5048 bootfile - Name of the image to load with TFTP 5049 5050 bootm_low - Memory range available for image processing in the bootm 5051 command can be restricted. This variable is given as 5052 a hexadecimal number and defines lowest address allowed 5053 for use by the bootm command. See also "bootm_size" 5054 environment variable. Address defined by "bootm_low" is 5055 also the base of the initial memory mapping for the Linux 5056 kernel -- see the description of CONFIG_SYS_BOOTMAPSZ and 5057 bootm_mapsize. 5058 5059 bootm_mapsize - Size of the initial memory mapping for the Linux kernel. 5060 This variable is given as a hexadecimal number and it 5061 defines the size of the memory region starting at base 5062 address bootm_low that is accessible by the Linux kernel 5063 during early boot. If unset, CONFIG_SYS_BOOTMAPSZ is used 5064 as the default value if it is defined, and bootm_size is 5065 used otherwise. 5066 5067 bootm_size - Memory range available for image processing in the bootm 5068 command can be restricted. This variable is given as 5069 a hexadecimal number and defines the size of the region 5070 allowed for use by the bootm command. See also "bootm_low" 5071 environment variable. 5072 5073 updatefile - Location of the software update file on a TFTP server, used 5074 by the automatic software update feature. Please refer to 5075 documentation in doc/README.update for more details. 5076 5077 autoload - if set to "no" (any string beginning with 'n'), 5078 "bootp" will just load perform a lookup of the 5079 configuration from the BOOTP server, but not try to 5080 load any image using TFTP 5081 5082 autostart - if set to "yes", an image loaded using the "bootp", 5083 "rarpboot", "tftpboot" or "diskboot" commands will 5084 be automatically started (by internally calling 5085 "bootm") 5086 5087 If set to "no", a standalone image passed to the 5088 "bootm" command will be copied to the load address 5089 (and eventually uncompressed), but NOT be started. 5090 This can be used to load and uncompress arbitrary 5091 data. 5092 5093 fdt_high - if set this restricts the maximum address that the 5094 flattened device tree will be copied into upon boot. 5095 For example, if you have a system with 1 GB memory 5096 at physical address 0x10000000, while Linux kernel 5097 only recognizes the first 704 MB as low memory, you 5098 may need to set fdt_high as 0x3C000000 to have the 5099 device tree blob be copied to the maximum address 5100 of the 704 MB low memory, so that Linux kernel can 5101 access it during the boot procedure. 5102 5103 If this is set to the special value 0xFFFFFFFF then 5104 the fdt will not be copied at all on boot. For this 5105 to work it must reside in writable memory, have 5106 sufficient padding on the end of it for u-boot to 5107 add the information it needs into it, and the memory 5108 must be accessible by the kernel. 5109 5110 fdtcontroladdr- if set this is the address of the control flattened 5111 device tree used by U-Boot when CONFIG_OF_CONTROL is 5112 defined. 5113 5114 i2cfast - (PPC405GP|PPC405EP only) 5115 if set to 'y' configures Linux I2C driver for fast 5116 mode (400kHZ). This environment variable is used in 5117 initialization code. So, for changes to be effective 5118 it must be saved and board must be reset. 5119 5120 initrd_high - restrict positioning of initrd images: 5121 If this variable is not set, initrd images will be 5122 copied to the highest possible address in RAM; this 5123 is usually what you want since it allows for 5124 maximum initrd size. If for some reason you want to 5125 make sure that the initrd image is loaded below the 5126 CONFIG_SYS_BOOTMAPSZ limit, you can set this environment 5127 variable to a value of "no" or "off" or "0". 5128 Alternatively, you can set it to a maximum upper 5129 address to use (U-Boot will still check that it 5130 does not overwrite the U-Boot stack and data). 5131 5132 For instance, when you have a system with 16 MB 5133 RAM, and want to reserve 4 MB from use by Linux, 5134 you can do this by adding "mem=12M" to the value of 5135 the "bootargs" variable. However, now you must make 5136 sure that the initrd image is placed in the first 5137 12 MB as well - this can be done with 5138 5139 setenv initrd_high 00c00000 5140 5141 If you set initrd_high to 0xFFFFFFFF, this is an 5142 indication to U-Boot that all addresses are legal 5143 for the Linux kernel, including addresses in flash 5144 memory. In this case U-Boot will NOT COPY the 5145 ramdisk at all. This may be useful to reduce the 5146 boot time on your system, but requires that this 5147 feature is supported by your Linux kernel. 5148 5149 ipaddr - IP address; needed for tftpboot command 5150 5151 loadaddr - Default load address for commands like "bootp", 5152 "rarpboot", "tftpboot", "loadb" or "diskboot" 5153 5154 loads_echo - see CONFIG_LOADS_ECHO 5155 5156 serverip - TFTP server IP address; needed for tftpboot command 5157 5158 bootretry - see CONFIG_BOOT_RETRY_TIME 5159 5160 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR 5161 5162 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR 5163 5164 ethprime - controls which interface is used first. 5165 5166 ethact - controls which interface is currently active. 5167 For example you can do the following 5168 5169 => setenv ethact FEC 5170 => ping 192.168.0.1 # traffic sent on FEC 5171 => setenv ethact SCC 5172 => ping 10.0.0.1 # traffic sent on SCC 5173 5174 ethrotate - When set to "no" U-Boot does not go through all 5175 available network interfaces. 5176 It just stays at the currently selected interface. 5177 5178 netretry - When set to "no" each network operation will 5179 either succeed or fail without retrying. 5180 When set to "once" the network operation will 5181 fail when all the available network interfaces 5182 are tried once without success. 5183 Useful on scripts which control the retry operation 5184 themselves. 5185 5186 npe_ucode - set load address for the NPE microcode 5187 5188 silent_linux - If set then Linux will be told to boot silently, by 5189 changing the console to be empty. If "yes" it will be 5190 made silent. If "no" it will not be made silent. If 5191 unset, then it will be made silent if the U-Boot console 5192 is silent. 5193 5194 tftpsrcp - If this is set, the value is used for TFTP's 5195 UDP source port. 5196 5197 tftpdstp - If this is set, the value is used for TFTP's UDP 5198 destination port instead of the Well Know Port 69. 5199 5200 tftpblocksize - Block size to use for TFTP transfers; if not set, 5201 we use the TFTP server's default block size 5202 5203 tftptimeout - Retransmission timeout for TFTP packets (in milli- 5204 seconds, minimum value is 1000 = 1 second). Defines 5205 when a packet is considered to be lost so it has to 5206 be retransmitted. The default is 5000 = 5 seconds. 5207 Lowering this value may make downloads succeed 5208 faster in networks with high packet loss rates or 5209 with unreliable TFTP servers. 5210 5211 tftptimeoutcountmax - maximum count of TFTP timeouts (no 5212 unit, minimum value = 0). Defines how many timeouts 5213 can happen during a single file transfer before that 5214 transfer is aborted. The default is 10, and 0 means 5215 'no timeouts allowed'. Increasing this value may help 5216 downloads succeed with high packet loss rates, or with 5217 unreliable TFTP servers or client hardware. 5218 5219 vlan - When set to a value < 4095 the traffic over 5220 Ethernet is encapsulated/received over 802.1q 5221 VLAN tagged frames. 5222 5223 bootpretryperiod - Period during which BOOTP/DHCP sends retries. 5224 Unsigned value, in milliseconds. If not set, the period will 5225 be either the default (28000), or a value based on 5226 CONFIG_NET_RETRY_COUNT, if defined. This value has 5227 precedence over the valu based on CONFIG_NET_RETRY_COUNT. 5228 5229The following image location variables contain the location of images 5230used in booting. The "Image" column gives the role of the image and is 5231not an environment variable name. The other columns are environment 5232variable names. "File Name" gives the name of the file on a TFTP 5233server, "RAM Address" gives the location in RAM the image will be 5234loaded to, and "Flash Location" gives the image's address in NOR 5235flash or offset in NAND flash. 5236 5237*Note* - these variables don't have to be defined for all boards, some 5238boards currently use other variables for these purposes, and some 5239boards use these variables for other purposes. 5240 5241Image File Name RAM Address Flash Location 5242----- --------- ----------- -------------- 5243u-boot u-boot u-boot_addr_r u-boot_addr 5244Linux kernel bootfile kernel_addr_r kernel_addr 5245device tree blob fdtfile fdt_addr_r fdt_addr 5246ramdisk ramdiskfile ramdisk_addr_r ramdisk_addr 5247 5248The following environment variables may be used and automatically 5249updated by the network boot commands ("bootp" and "rarpboot"), 5250depending the information provided by your boot server: 5251 5252 bootfile - see above 5253 dnsip - IP address of your Domain Name Server 5254 dnsip2 - IP address of your secondary Domain Name Server 5255 gatewayip - IP address of the Gateway (Router) to use 5256 hostname - Target hostname 5257 ipaddr - see above 5258 netmask - Subnet Mask 5259 rootpath - Pathname of the root filesystem on the NFS server 5260 serverip - see above 5261 5262 5263There are two special Environment Variables: 5264 5265 serial# - contains hardware identification information such 5266 as type string and/or serial number 5267 ethaddr - Ethernet address 5268 5269These variables can be set only once (usually during manufacturing of 5270the board). U-Boot refuses to delete or overwrite these variables 5271once they have been set once. 5272 5273 5274Further special Environment Variables: 5275 5276 ver - Contains the U-Boot version string as printed 5277 with the "version" command. This variable is 5278 readonly (see CONFIG_VERSION_VARIABLE). 5279 5280 5281Please note that changes to some configuration parameters may take 5282only effect after the next boot (yes, that's just like Windoze :-). 5283 5284 5285Callback functions for environment variables: 5286--------------------------------------------- 5287 5288For some environment variables, the behavior of u-boot needs to change 5289when their values are changed. This functionality allows functions to 5290be associated with arbitrary variables. On creation, overwrite, or 5291deletion, the callback will provide the opportunity for some side 5292effect to happen or for the change to be rejected. 5293 5294The callbacks are named and associated with a function using the 5295U_BOOT_ENV_CALLBACK macro in your board or driver code. 5296 5297These callbacks are associated with variables in one of two ways. The 5298static list can be added to by defining CONFIG_ENV_CALLBACK_LIST_STATIC 5299in the board configuration to a string that defines a list of 5300associations. The list must be in the following format: 5301 5302 entry = variable_name[:callback_name] 5303 list = entry[,list] 5304 5305If the callback name is not specified, then the callback is deleted. 5306Spaces are also allowed anywhere in the list. 5307 5308Callbacks can also be associated by defining the ".callbacks" variable 5309with the same list format above. Any association in ".callbacks" will 5310override any association in the static list. You can define 5311CONFIG_ENV_CALLBACK_LIST_DEFAULT to a list (string) to define the 5312".callbacks" environment variable in the default or embedded environment. 5313 5314If CONFIG_REGEX is defined, the variable_name above is evaluated as a 5315regular expression. This allows multiple variables to be connected to 5316the same callback without explicitly listing them all out. 5317 5318 5319Command Line Parsing: 5320===================== 5321 5322There are two different command line parsers available with U-Boot: 5323the old "simple" one, and the much more powerful "hush" shell: 5324 5325Old, simple command line parser: 5326-------------------------------- 5327 5328- supports environment variables (through setenv / saveenv commands) 5329- several commands on one line, separated by ';' 5330- variable substitution using "... ${name} ..." syntax 5331- special characters ('$', ';') can be escaped by prefixing with '\', 5332 for example: 5333 setenv bootcmd bootm \${address} 5334- You can also escape text by enclosing in single apostrophes, for example: 5335 setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off' 5336 5337Hush shell: 5338----------- 5339 5340- similar to Bourne shell, with control structures like 5341 if...then...else...fi, for...do...done; while...do...done, 5342 until...do...done, ... 5343- supports environment ("global") variables (through setenv / saveenv 5344 commands) and local shell variables (through standard shell syntax 5345 "name=value"); only environment variables can be used with "run" 5346 command 5347 5348General rules: 5349-------------- 5350 5351(1) If a command line (or an environment variable executed by a "run" 5352 command) contains several commands separated by semicolon, and 5353 one of these commands fails, then the remaining commands will be 5354 executed anyway. 5355 5356(2) If you execute several variables with one call to run (i. e. 5357 calling run with a list of variables as arguments), any failing 5358 command will cause "run" to terminate, i. e. the remaining 5359 variables are not executed. 5360 5361Note for Redundant Ethernet Interfaces: 5362======================================= 5363 5364Some boards come with redundant Ethernet interfaces; U-Boot supports 5365such configurations and is capable of automatic selection of a 5366"working" interface when needed. MAC assignment works as follows: 5367 5368Network interfaces are numbered eth0, eth1, eth2, ... Corresponding 5369MAC addresses can be stored in the environment as "ethaddr" (=>eth0), 5370"eth1addr" (=>eth1), "eth2addr", ... 5371 5372If the network interface stores some valid MAC address (for instance 5373in SROM), this is used as default address if there is NO correspon- 5374ding setting in the environment; if the corresponding environment 5375variable is set, this overrides the settings in the card; that means: 5376 5377o If the SROM has a valid MAC address, and there is no address in the 5378 environment, the SROM's address is used. 5379 5380o If there is no valid address in the SROM, and a definition in the 5381 environment exists, then the value from the environment variable is 5382 used. 5383 5384o If both the SROM and the environment contain a MAC address, and 5385 both addresses are the same, this MAC address is used. 5386 5387o If both the SROM and the environment contain a MAC address, and the 5388 addresses differ, the value from the environment is used and a 5389 warning is printed. 5390 5391o If neither SROM nor the environment contain a MAC address, an error 5392 is raised. If CONFIG_NET_RANDOM_ETHADDR is defined, then in this case 5393 a random, locally-assigned MAC is used. 5394 5395If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses 5396will be programmed into hardware as part of the initialization process. This 5397may be skipped by setting the appropriate 'ethmacskip' environment variable. 5398The naming convention is as follows: 5399"ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc. 5400 5401Image Formats: 5402============== 5403 5404U-Boot is capable of booting (and performing other auxiliary operations on) 5405images in two formats: 5406 5407New uImage format (FIT) 5408----------------------- 5409 5410Flexible and powerful format based on Flattened Image Tree -- FIT (similar 5411to Flattened Device Tree). It allows the use of images with multiple 5412components (several kernels, ramdisks, etc.), with contents protected by 5413SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory. 5414 5415 5416Old uImage format 5417----------------- 5418 5419Old image format is based on binary files which can be basically anything, 5420preceded by a special header; see the definitions in include/image.h for 5421details; basically, the header defines the following image properties: 5422 5423* Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD, 5424 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks, 5425 LynxOS, pSOS, QNX, RTEMS, INTEGRITY; 5426 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS, 5427 INTEGRITY). 5428* Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86, 5429 IA64, MIPS, NDS32, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; 5430 Currently supported: ARM, AVR32, Intel x86, MIPS, NDS32, Nios II, PowerPC). 5431* Compression Type (uncompressed, gzip, bzip2) 5432* Load Address 5433* Entry Point 5434* Image Name 5435* Image Timestamp 5436 5437The header is marked by a special Magic Number, and both the header 5438and the data portions of the image are secured against corruption by 5439CRC32 checksums. 5440 5441 5442Linux Support: 5443============== 5444 5445Although U-Boot should support any OS or standalone application 5446easily, the main focus has always been on Linux during the design of 5447U-Boot. 5448 5449U-Boot includes many features that so far have been part of some 5450special "boot loader" code within the Linux kernel. Also, any 5451"initrd" images to be used are no longer part of one big Linux image; 5452instead, kernel and "initrd" are separate images. This implementation 5453serves several purposes: 5454 5455- the same features can be used for other OS or standalone 5456 applications (for instance: using compressed images to reduce the 5457 Flash memory footprint) 5458 5459- it becomes much easier to port new Linux kernel versions because 5460 lots of low-level, hardware dependent stuff are done by U-Boot 5461 5462- the same Linux kernel image can now be used with different "initrd" 5463 images; of course this also means that different kernel images can 5464 be run with the same "initrd". This makes testing easier (you don't 5465 have to build a new "zImage.initrd" Linux image when you just 5466 change a file in your "initrd"). Also, a field-upgrade of the 5467 software is easier now. 5468 5469 5470Linux HOWTO: 5471============ 5472 5473Porting Linux to U-Boot based systems: 5474--------------------------------------- 5475 5476U-Boot cannot save you from doing all the necessary modifications to 5477configure the Linux device drivers for use with your target hardware 5478(no, we don't intend to provide a full virtual machine interface to 5479Linux :-). 5480 5481But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot). 5482 5483Just make sure your machine specific header file (for instance 5484include/asm-ppc/tqm8xx.h) includes the same definition of the Board 5485Information structure as we define in include/asm-<arch>/u-boot.h, 5486and make sure that your definition of IMAP_ADDR uses the same value 5487as your U-Boot configuration in CONFIG_SYS_IMMR. 5488 5489Note that U-Boot now has a driver model, a unified model for drivers. 5490If you are adding a new driver, plumb it into driver model. If there 5491is no uclass available, you are encouraged to create one. See 5492doc/driver-model. 5493 5494 5495Configuring the Linux kernel: 5496----------------------------- 5497 5498No specific requirements for U-Boot. Make sure you have some root 5499device (initial ramdisk, NFS) for your target system. 5500 5501 5502Building a Linux Image: 5503----------------------- 5504 5505With U-Boot, "normal" build targets like "zImage" or "bzImage" are 5506not used. If you use recent kernel source, a new build target 5507"uImage" will exist which automatically builds an image usable by 5508U-Boot. Most older kernels also have support for a "pImage" target, 5509which was introduced for our predecessor project PPCBoot and uses a 5510100% compatible format. 5511 5512Example: 5513 5514 make TQM850L_defconfig 5515 make oldconfig 5516 make dep 5517 make uImage 5518 5519The "uImage" build target uses a special tool (in 'tools/mkimage') to 5520encapsulate a compressed Linux kernel image with header information, 5521CRC32 checksum etc. for use with U-Boot. This is what we are doing: 5522 5523* build a standard "vmlinux" kernel image (in ELF binary format): 5524 5525* convert the kernel into a raw binary image: 5526 5527 ${CROSS_COMPILE}-objcopy -O binary \ 5528 -R .note -R .comment \ 5529 -S vmlinux linux.bin 5530 5531* compress the binary image: 5532 5533 gzip -9 linux.bin 5534 5535* package compressed binary image for U-Boot: 5536 5537 mkimage -A ppc -O linux -T kernel -C gzip \ 5538 -a 0 -e 0 -n "Linux Kernel Image" \ 5539 -d linux.bin.gz uImage 5540 5541 5542The "mkimage" tool can also be used to create ramdisk images for use 5543with U-Boot, either separated from the Linux kernel image, or 5544combined into one file. "mkimage" encapsulates the images with a 64 5545byte header containing information about target architecture, 5546operating system, image type, compression method, entry points, time 5547stamp, CRC32 checksums, etc. 5548 5549"mkimage" can be called in two ways: to verify existing images and 5550print the header information, or to build new images. 5551 5552In the first form (with "-l" option) mkimage lists the information 5553contained in the header of an existing U-Boot image; this includes 5554checksum verification: 5555 5556 tools/mkimage -l image 5557 -l ==> list image header information 5558 5559The second form (with "-d" option) is used to build a U-Boot image 5560from a "data file" which is used as image payload: 5561 5562 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \ 5563 -n name -d data_file image 5564 -A ==> set architecture to 'arch' 5565 -O ==> set operating system to 'os' 5566 -T ==> set image type to 'type' 5567 -C ==> set compression type 'comp' 5568 -a ==> set load address to 'addr' (hex) 5569 -e ==> set entry point to 'ep' (hex) 5570 -n ==> set image name to 'name' 5571 -d ==> use image data from 'datafile' 5572 5573Right now, all Linux kernels for PowerPC systems use the same load 5574address (0x00000000), but the entry point address depends on the 5575kernel version: 5576 5577- 2.2.x kernels have the entry point at 0x0000000C, 5578- 2.3.x and later kernels have the entry point at 0x00000000. 5579 5580So a typical call to build a U-Boot image would read: 5581 5582 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 5583 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \ 5584 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \ 5585 > examples/uImage.TQM850L 5586 Image Name: 2.4.4 kernel for TQM850L 5587 Created: Wed Jul 19 02:34:59 2000 5588 Image Type: PowerPC Linux Kernel Image (gzip compressed) 5589 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 5590 Load Address: 0x00000000 5591 Entry Point: 0x00000000 5592 5593To verify the contents of the image (or check for corruption): 5594 5595 -> tools/mkimage -l examples/uImage.TQM850L 5596 Image Name: 2.4.4 kernel for TQM850L 5597 Created: Wed Jul 19 02:34:59 2000 5598 Image Type: PowerPC Linux Kernel Image (gzip compressed) 5599 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 5600 Load Address: 0x00000000 5601 Entry Point: 0x00000000 5602 5603NOTE: for embedded systems where boot time is critical you can trade 5604speed for memory and install an UNCOMPRESSED image instead: this 5605needs more space in Flash, but boots much faster since it does not 5606need to be uncompressed: 5607 5608 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz 5609 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 5610 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \ 5611 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \ 5612 > examples/uImage.TQM850L-uncompressed 5613 Image Name: 2.4.4 kernel for TQM850L 5614 Created: Wed Jul 19 02:34:59 2000 5615 Image Type: PowerPC Linux Kernel Image (uncompressed) 5616 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB 5617 Load Address: 0x00000000 5618 Entry Point: 0x00000000 5619 5620 5621Similar you can build U-Boot images from a 'ramdisk.image.gz' file 5622when your kernel is intended to use an initial ramdisk: 5623 5624 -> tools/mkimage -n 'Simple Ramdisk Image' \ 5625 > -A ppc -O linux -T ramdisk -C gzip \ 5626 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd 5627 Image Name: Simple Ramdisk Image 5628 Created: Wed Jan 12 14:01:50 2000 5629 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 5630 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB 5631 Load Address: 0x00000000 5632 Entry Point: 0x00000000 5633 5634The "dumpimage" is a tool to disassemble images built by mkimage. Its "-i" 5635option performs the converse operation of the mkimage's second form (the "-d" 5636option). Given an image built by mkimage, the dumpimage extracts a "data file" 5637from the image: 5638 5639 tools/dumpimage -i image -T type -p position data_file 5640 -i ==> extract from the 'image' a specific 'data_file' 5641 -T ==> set image type to 'type' 5642 -p ==> 'position' (starting at 0) of the 'data_file' inside the 'image' 5643 5644 5645Installing a Linux Image: 5646------------------------- 5647 5648To downloading a U-Boot image over the serial (console) interface, 5649you must convert the image to S-Record format: 5650 5651 objcopy -I binary -O srec examples/image examples/image.srec 5652 5653The 'objcopy' does not understand the information in the U-Boot 5654image header, so the resulting S-Record file will be relative to 5655address 0x00000000. To load it to a given address, you need to 5656specify the target address as 'offset' parameter with the 'loads' 5657command. 5658 5659Example: install the image to address 0x40100000 (which on the 5660TQM8xxL is in the first Flash bank): 5661 5662 => erase 40100000 401FFFFF 5663 5664 .......... done 5665 Erased 8 sectors 5666 5667 => loads 40100000 5668 ## Ready for S-Record download ... 5669 ~>examples/image.srec 5670 1 2 3 4 5 6 7 8 9 10 11 12 13 ... 5671 ... 5672 15989 15990 15991 15992 5673 [file transfer complete] 5674 [connected] 5675 ## Start Addr = 0x00000000 5676 5677 5678You can check the success of the download using the 'iminfo' command; 5679this includes a checksum verification so you can be sure no data 5680corruption happened: 5681 5682 => imi 40100000 5683 5684 ## Checking Image at 40100000 ... 5685 Image Name: 2.2.13 for initrd on TQM850L 5686 Image Type: PowerPC Linux Kernel Image (gzip compressed) 5687 Data Size: 335725 Bytes = 327 kB = 0 MB 5688 Load Address: 00000000 5689 Entry Point: 0000000c 5690 Verifying Checksum ... OK 5691 5692 5693Boot Linux: 5694----------- 5695 5696The "bootm" command is used to boot an application that is stored in 5697memory (RAM or Flash). In case of a Linux kernel image, the contents 5698of the "bootargs" environment variable is passed to the kernel as 5699parameters. You can check and modify this variable using the 5700"printenv" and "setenv" commands: 5701 5702 5703 => printenv bootargs 5704 bootargs=root=/dev/ram 5705 5706 => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 5707 5708 => printenv bootargs 5709 bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 5710 5711 => bootm 40020000 5712 ## Booting Linux kernel at 40020000 ... 5713 Image Name: 2.2.13 for NFS on TQM850L 5714 Image Type: PowerPC Linux Kernel Image (gzip compressed) 5715 Data Size: 381681 Bytes = 372 kB = 0 MB 5716 Load Address: 00000000 5717 Entry Point: 0000000c 5718 Verifying Checksum ... OK 5719 Uncompressing Kernel Image ... OK 5720 Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:35:17 MEST 2000 5721 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 5722 time_init: decrementer frequency = 187500000/60 5723 Calibrating delay loop... 49.77 BogoMIPS 5724 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000] 5725 ... 5726 5727If you want to boot a Linux kernel with initial RAM disk, you pass 5728the memory addresses of both the kernel and the initrd image (PPBCOOT 5729format!) to the "bootm" command: 5730 5731 => imi 40100000 40200000 5732 5733 ## Checking Image at 40100000 ... 5734 Image Name: 2.2.13 for initrd on TQM850L 5735 Image Type: PowerPC Linux Kernel Image (gzip compressed) 5736 Data Size: 335725 Bytes = 327 kB = 0 MB 5737 Load Address: 00000000 5738 Entry Point: 0000000c 5739 Verifying Checksum ... OK 5740 5741 ## Checking Image at 40200000 ... 5742 Image Name: Simple Ramdisk Image 5743 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 5744 Data Size: 566530 Bytes = 553 kB = 0 MB 5745 Load Address: 00000000 5746 Entry Point: 00000000 5747 Verifying Checksum ... OK 5748 5749 => bootm 40100000 40200000 5750 ## Booting Linux kernel at 40100000 ... 5751 Image Name: 2.2.13 for initrd on TQM850L 5752 Image Type: PowerPC Linux Kernel Image (gzip compressed) 5753 Data Size: 335725 Bytes = 327 kB = 0 MB 5754 Load Address: 00000000 5755 Entry Point: 0000000c 5756 Verifying Checksum ... OK 5757 Uncompressing Kernel Image ... OK 5758 ## Loading RAMDisk Image at 40200000 ... 5759 Image Name: Simple Ramdisk Image 5760 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 5761 Data Size: 566530 Bytes = 553 kB = 0 MB 5762 Load Address: 00000000 5763 Entry Point: 00000000 5764 Verifying Checksum ... OK 5765 Loading Ramdisk ... OK 5766 Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:32:08 MEST 2000 5767 Boot arguments: root=/dev/ram 5768 time_init: decrementer frequency = 187500000/60 5769 Calibrating delay loop... 49.77 BogoMIPS 5770 ... 5771 RAMDISK: Compressed image found at block 0 5772 VFS: Mounted root (ext2 filesystem). 5773 5774 bash# 5775 5776Boot Linux and pass a flat device tree: 5777----------- 5778 5779First, U-Boot must be compiled with the appropriate defines. See the section 5780titled "Linux Kernel Interface" above for a more in depth explanation. The 5781following is an example of how to start a kernel and pass an updated 5782flat device tree: 5783 5784=> print oftaddr 5785oftaddr=0x300000 5786=> print oft 5787oft=oftrees/mpc8540ads.dtb 5788=> tftp $oftaddr $oft 5789Speed: 1000, full duplex 5790Using TSEC0 device 5791TFTP from server 192.168.1.1; our IP address is 192.168.1.101 5792Filename 'oftrees/mpc8540ads.dtb'. 5793Load address: 0x300000 5794Loading: # 5795done 5796Bytes transferred = 4106 (100a hex) 5797=> tftp $loadaddr $bootfile 5798Speed: 1000, full duplex 5799Using TSEC0 device 5800TFTP from server 192.168.1.1; our IP address is 192.168.1.2 5801Filename 'uImage'. 5802Load address: 0x200000 5803Loading:############ 5804done 5805Bytes transferred = 1029407 (fb51f hex) 5806=> print loadaddr 5807loadaddr=200000 5808=> print oftaddr 5809oftaddr=0x300000 5810=> bootm $loadaddr - $oftaddr 5811## Booting image at 00200000 ... 5812 Image Name: Linux-2.6.17-dirty 5813 Image Type: PowerPC Linux Kernel Image (gzip compressed) 5814 Data Size: 1029343 Bytes = 1005.2 kB 5815 Load Address: 00000000 5816 Entry Point: 00000000 5817 Verifying Checksum ... OK 5818 Uncompressing Kernel Image ... OK 5819Booting using flat device tree at 0x300000 5820Using MPC85xx ADS machine description 5821Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb 5822[snip] 5823 5824 5825More About U-Boot Image Types: 5826------------------------------ 5827 5828U-Boot supports the following image types: 5829 5830 "Standalone Programs" are directly runnable in the environment 5831 provided by U-Boot; it is expected that (if they behave 5832 well) you can continue to work in U-Boot after return from 5833 the Standalone Program. 5834 "OS Kernel Images" are usually images of some Embedded OS which 5835 will take over control completely. Usually these programs 5836 will install their own set of exception handlers, device 5837 drivers, set up the MMU, etc. - this means, that you cannot 5838 expect to re-enter U-Boot except by resetting the CPU. 5839 "RAMDisk Images" are more or less just data blocks, and their 5840 parameters (address, size) are passed to an OS kernel that is 5841 being started. 5842 "Multi-File Images" contain several images, typically an OS 5843 (Linux) kernel image and one or more data images like 5844 RAMDisks. This construct is useful for instance when you want 5845 to boot over the network using BOOTP etc., where the boot 5846 server provides just a single image file, but you want to get 5847 for instance an OS kernel and a RAMDisk image. 5848 5849 "Multi-File Images" start with a list of image sizes, each 5850 image size (in bytes) specified by an "uint32_t" in network 5851 byte order. This list is terminated by an "(uint32_t)0". 5852 Immediately after the terminating 0 follow the images, one by 5853 one, all aligned on "uint32_t" boundaries (size rounded up to 5854 a multiple of 4 bytes). 5855 5856 "Firmware Images" are binary images containing firmware (like 5857 U-Boot or FPGA images) which usually will be programmed to 5858 flash memory. 5859 5860 "Script files" are command sequences that will be executed by 5861 U-Boot's command interpreter; this feature is especially 5862 useful when you configure U-Boot to use a real shell (hush) 5863 as command interpreter. 5864 5865Booting the Linux zImage: 5866------------------------- 5867 5868On some platforms, it's possible to boot Linux zImage. This is done 5869using the "bootz" command. The syntax of "bootz" command is the same 5870as the syntax of "bootm" command. 5871 5872Note, defining the CONFIG_SUPPORT_RAW_INITRD allows user to supply 5873kernel with raw initrd images. The syntax is slightly different, the 5874address of the initrd must be augmented by it's size, in the following 5875format: "<initrd addres>:<initrd size>". 5876 5877 5878Standalone HOWTO: 5879================= 5880 5881One of the features of U-Boot is that you can dynamically load and 5882run "standalone" applications, which can use some resources of 5883U-Boot like console I/O functions or interrupt services. 5884 5885Two simple examples are included with the sources: 5886 5887"Hello World" Demo: 5888------------------- 5889 5890'examples/hello_world.c' contains a small "Hello World" Demo 5891application; it is automatically compiled when you build U-Boot. 5892It's configured to run at address 0x00040004, so you can play with it 5893like that: 5894 5895 => loads 5896 ## Ready for S-Record download ... 5897 ~>examples/hello_world.srec 5898 1 2 3 4 5 6 7 8 9 10 11 ... 5899 [file transfer complete] 5900 [connected] 5901 ## Start Addr = 0x00040004 5902 5903 => go 40004 Hello World! This is a test. 5904 ## Starting application at 0x00040004 ... 5905 Hello World 5906 argc = 7 5907 argv[0] = "40004" 5908 argv[1] = "Hello" 5909 argv[2] = "World!" 5910 argv[3] = "This" 5911 argv[4] = "is" 5912 argv[5] = "a" 5913 argv[6] = "test." 5914 argv[7] = "<NULL>" 5915 Hit any key to exit ... 5916 5917 ## Application terminated, rc = 0x0 5918 5919Another example, which demonstrates how to register a CPM interrupt 5920handler with the U-Boot code, can be found in 'examples/timer.c'. 5921Here, a CPM timer is set up to generate an interrupt every second. 5922The interrupt service routine is trivial, just printing a '.' 5923character, but this is just a demo program. The application can be 5924controlled by the following keys: 5925 5926 ? - print current values og the CPM Timer registers 5927 b - enable interrupts and start timer 5928 e - stop timer and disable interrupts 5929 q - quit application 5930 5931 => loads 5932 ## Ready for S-Record download ... 5933 ~>examples/timer.srec 5934 1 2 3 4 5 6 7 8 9 10 11 ... 5935 [file transfer complete] 5936 [connected] 5937 ## Start Addr = 0x00040004 5938 5939 => go 40004 5940 ## Starting application at 0x00040004 ... 5941 TIMERS=0xfff00980 5942 Using timer 1 5943 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0 5944 5945Hit 'b': 5946 [q, b, e, ?] Set interval 1000000 us 5947 Enabling timer 5948Hit '?': 5949 [q, b, e, ?] ........ 5950 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0 5951Hit '?': 5952 [q, b, e, ?] . 5953 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0 5954Hit '?': 5955 [q, b, e, ?] . 5956 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0 5957Hit '?': 5958 [q, b, e, ?] . 5959 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0 5960Hit 'e': 5961 [q, b, e, ?] ...Stopping timer 5962Hit 'q': 5963 [q, b, e, ?] ## Application terminated, rc = 0x0 5964 5965 5966Minicom warning: 5967================ 5968 5969Over time, many people have reported problems when trying to use the 5970"minicom" terminal emulation program for serial download. I (wd) 5971consider minicom to be broken, and recommend not to use it. Under 5972Unix, I recommend to use C-Kermit for general purpose use (and 5973especially for kermit binary protocol download ("loadb" command), and 5974use "cu" for S-Record download ("loads" command). See 5975http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3. 5976for help with kermit. 5977 5978 5979Nevertheless, if you absolutely want to use it try adding this 5980configuration to your "File transfer protocols" section: 5981 5982 Name Program Name U/D FullScr IO-Red. Multi 5983 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N 5984 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N 5985 5986 5987NetBSD Notes: 5988============= 5989 5990Starting at version 0.9.2, U-Boot supports NetBSD both as host 5991(build U-Boot) and target system (boots NetBSD/mpc8xx). 5992 5993Building requires a cross environment; it is known to work on 5994NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also 5995need gmake since the Makefiles are not compatible with BSD make). 5996Note that the cross-powerpc package does not install include files; 5997attempting to build U-Boot will fail because <machine/ansi.h> is 5998missing. This file has to be installed and patched manually: 5999 6000 # cd /usr/pkg/cross/powerpc-netbsd/include 6001 # mkdir powerpc 6002 # ln -s powerpc machine 6003 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h 6004 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST 6005 6006Native builds *don't* work due to incompatibilities between native 6007and U-Boot include files. 6008 6009Booting assumes that (the first part of) the image booted is a 6010stage-2 loader which in turn loads and then invokes the kernel 6011proper. Loader sources will eventually appear in the NetBSD source 6012tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the 6013meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz 6014 6015 6016Implementation Internals: 6017========================= 6018 6019The following is not intended to be a complete description of every 6020implementation detail. However, it should help to understand the 6021inner workings of U-Boot and make it easier to port it to custom 6022hardware. 6023 6024 6025Initial Stack, Global Data: 6026--------------------------- 6027 6028The implementation of U-Boot is complicated by the fact that U-Boot 6029starts running out of ROM (flash memory), usually without access to 6030system RAM (because the memory controller is not initialized yet). 6031This means that we don't have writable Data or BSS segments, and BSS 6032is not initialized as zero. To be able to get a C environment working 6033at all, we have to allocate at least a minimal stack. Implementation 6034options for this are defined and restricted by the CPU used: Some CPU 6035models provide on-chip memory (like the IMMR area on MPC8xx and 6036MPC826x processors), on others (parts of) the data cache can be 6037locked as (mis-) used as memory, etc. 6038 6039 Chris Hallinan posted a good summary of these issues to the 6040 U-Boot mailing list: 6041 6042 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)? 6043 From: "Chris Hallinan" <clh@net1plus.com> 6044 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET) 6045 ... 6046 6047 Correct me if I'm wrong, folks, but the way I understand it 6048 is this: Using DCACHE as initial RAM for Stack, etc, does not 6049 require any physical RAM backing up the cache. The cleverness 6050 is that the cache is being used as a temporary supply of 6051 necessary storage before the SDRAM controller is setup. It's 6052 beyond the scope of this list to explain the details, but you 6053 can see how this works by studying the cache architecture and 6054 operation in the architecture and processor-specific manuals. 6055 6056 OCM is On Chip Memory, which I believe the 405GP has 4K. It 6057 is another option for the system designer to use as an 6058 initial stack/RAM area prior to SDRAM being available. Either 6059 option should work for you. Using CS 4 should be fine if your 6060 board designers haven't used it for something that would 6061 cause you grief during the initial boot! It is frequently not 6062 used. 6063 6064 CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere 6065 with your processor/board/system design. The default value 6066 you will find in any recent u-boot distribution in 6067 walnut.h should work for you. I'd set it to a value larger 6068 than your SDRAM module. If you have a 64MB SDRAM module, set 6069 it above 400_0000. Just make sure your board has no resources 6070 that are supposed to respond to that address! That code in 6071 start.S has been around a while and should work as is when 6072 you get the config right. 6073 6074 -Chris Hallinan 6075 DS4.COM, Inc. 6076 6077It is essential to remember this, since it has some impact on the C 6078code for the initialization procedures: 6079 6080* Initialized global data (data segment) is read-only. Do not attempt 6081 to write it. 6082 6083* Do not use any uninitialized global data (or implicitly initialized 6084 as zero data - BSS segment) at all - this is undefined, initiali- 6085 zation is performed later (when relocating to RAM). 6086 6087* Stack space is very limited. Avoid big data buffers or things like 6088 that. 6089 6090Having only the stack as writable memory limits means we cannot use 6091normal global data to share information between the code. But it 6092turned out that the implementation of U-Boot can be greatly 6093simplified by making a global data structure (gd_t) available to all 6094functions. We could pass a pointer to this data as argument to _all_ 6095functions, but this would bloat the code. Instead we use a feature of 6096the GCC compiler (Global Register Variables) to share the data: we 6097place a pointer (gd) to the global data into a register which we 6098reserve for this purpose. 6099 6100When choosing a register for such a purpose we are restricted by the 6101relevant (E)ABI specifications for the current architecture, and by 6102GCC's implementation. 6103 6104For PowerPC, the following registers have specific use: 6105 R1: stack pointer 6106 R2: reserved for system use 6107 R3-R4: parameter passing and return values 6108 R5-R10: parameter passing 6109 R13: small data area pointer 6110 R30: GOT pointer 6111 R31: frame pointer 6112 6113 (U-Boot also uses R12 as internal GOT pointer. r12 6114 is a volatile register so r12 needs to be reset when 6115 going back and forth between asm and C) 6116 6117 ==> U-Boot will use R2 to hold a pointer to the global data 6118 6119 Note: on PPC, we could use a static initializer (since the 6120 address of the global data structure is known at compile time), 6121 but it turned out that reserving a register results in somewhat 6122 smaller code - although the code savings are not that big (on 6123 average for all boards 752 bytes for the whole U-Boot image, 6124 624 text + 127 data). 6125 6126On Blackfin, the normal C ABI (except for P3) is followed as documented here: 6127 http://docs.blackfin.uclinux.org/doku.php?id=application_binary_interface 6128 6129 ==> U-Boot will use P3 to hold a pointer to the global data 6130 6131On ARM, the following registers are used: 6132 6133 R0: function argument word/integer result 6134 R1-R3: function argument word 6135 R9: platform specific 6136 R10: stack limit (used only if stack checking is enabled) 6137 R11: argument (frame) pointer 6138 R12: temporary workspace 6139 R13: stack pointer 6140 R14: link register 6141 R15: program counter 6142 6143 ==> U-Boot will use R9 to hold a pointer to the global data 6144 6145 Note: on ARM, only R_ARM_RELATIVE relocations are supported. 6146 6147On Nios II, the ABI is documented here: 6148 http://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf 6149 6150 ==> U-Boot will use gp to hold a pointer to the global data 6151 6152 Note: on Nios II, we give "-G0" option to gcc and don't use gp 6153 to access small data sections, so gp is free. 6154 6155On NDS32, the following registers are used: 6156 6157 R0-R1: argument/return 6158 R2-R5: argument 6159 R15: temporary register for assembler 6160 R16: trampoline register 6161 R28: frame pointer (FP) 6162 R29: global pointer (GP) 6163 R30: link register (LP) 6164 R31: stack pointer (SP) 6165 PC: program counter (PC) 6166 6167 ==> U-Boot will use R10 to hold a pointer to the global data 6168 6169NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope, 6170or current versions of GCC may "optimize" the code too much. 6171 6172Memory Management: 6173------------------ 6174 6175U-Boot runs in system state and uses physical addresses, i.e. the 6176MMU is not used either for address mapping nor for memory protection. 6177 6178The available memory is mapped to fixed addresses using the memory 6179controller. In this process, a contiguous block is formed for each 6180memory type (Flash, SDRAM, SRAM), even when it consists of several 6181physical memory banks. 6182 6183U-Boot is installed in the first 128 kB of the first Flash bank (on 6184TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After 6185booting and sizing and initializing DRAM, the code relocates itself 6186to the upper end of DRAM. Immediately below the U-Boot code some 6187memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN 6188configuration setting]. Below that, a structure with global Board 6189Info data is placed, followed by the stack (growing downward). 6190 6191Additionally, some exception handler code is copied to the low 8 kB 6192of DRAM (0x00000000 ... 0x00001FFF). 6193 6194So a typical memory configuration with 16 MB of DRAM could look like 6195this: 6196 6197 0x0000 0000 Exception Vector code 6198 : 6199 0x0000 1FFF 6200 0x0000 2000 Free for Application Use 6201 : 6202 : 6203 6204 : 6205 : 6206 0x00FB FF20 Monitor Stack (Growing downward) 6207 0x00FB FFAC Board Info Data and permanent copy of global data 6208 0x00FC 0000 Malloc Arena 6209 : 6210 0x00FD FFFF 6211 0x00FE 0000 RAM Copy of Monitor Code 6212 ... eventually: LCD or video framebuffer 6213 ... eventually: pRAM (Protected RAM - unchanged by reset) 6214 0x00FF FFFF [End of RAM] 6215 6216 6217System Initialization: 6218---------------------- 6219 6220In the reset configuration, U-Boot starts at the reset entry point 6221(on most PowerPC systems at address 0x00000100). Because of the reset 6222configuration for CS0# this is a mirror of the on board Flash memory. 6223To be able to re-map memory U-Boot then jumps to its link address. 6224To be able to implement the initialization code in C, a (small!) 6225initial stack is set up in the internal Dual Ported RAM (in case CPUs 6226which provide such a feature like MPC8xx or MPC8260), or in a locked 6227part of the data cache. After that, U-Boot initializes the CPU core, 6228the caches and the SIU. 6229 6230Next, all (potentially) available memory banks are mapped using a 6231preliminary mapping. For example, we put them on 512 MB boundaries 6232(multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash 6233on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is 6234programmed for SDRAM access. Using the temporary configuration, a 6235simple memory test is run that determines the size of the SDRAM 6236banks. 6237 6238When there is more than one SDRAM bank, and the banks are of 6239different size, the largest is mapped first. For equal size, the first 6240bank (CS2#) is mapped first. The first mapping is always for address 62410x00000000, with any additional banks following immediately to create 6242contiguous memory starting from 0. 6243 6244Then, the monitor installs itself at the upper end of the SDRAM area 6245and allocates memory for use by malloc() and for the global Board 6246Info data; also, the exception vector code is copied to the low RAM 6247pages, and the final stack is set up. 6248 6249Only after this relocation will you have a "normal" C environment; 6250until that you are restricted in several ways, mostly because you are 6251running from ROM, and because the code will have to be relocated to a 6252new address in RAM. 6253 6254 6255U-Boot Porting Guide: 6256---------------------- 6257 6258[Based on messages by Jerry Van Baren in the U-Boot-Users mailing 6259list, October 2002] 6260 6261 6262int main(int argc, char *argv[]) 6263{ 6264 sighandler_t no_more_time; 6265 6266 signal(SIGALRM, no_more_time); 6267 alarm(PROJECT_DEADLINE - toSec (3 * WEEK)); 6268 6269 if (available_money > available_manpower) { 6270 Pay consultant to port U-Boot; 6271 return 0; 6272 } 6273 6274 Download latest U-Boot source; 6275 6276 Subscribe to u-boot mailing list; 6277 6278 if (clueless) 6279 email("Hi, I am new to U-Boot, how do I get started?"); 6280 6281 while (learning) { 6282 Read the README file in the top level directory; 6283 Read http://www.denx.de/twiki/bin/view/DULG/Manual; 6284 Read applicable doc/*.README; 6285 Read the source, Luke; 6286 /* find . -name "*.[chS]" | xargs grep -i <keyword> */ 6287 } 6288 6289 if (available_money > toLocalCurrency ($2500)) 6290 Buy a BDI3000; 6291 else 6292 Add a lot of aggravation and time; 6293 6294 if (a similar board exists) { /* hopefully... */ 6295 cp -a board/<similar> board/<myboard> 6296 cp include/configs/<similar>.h include/configs/<myboard>.h 6297 } else { 6298 Create your own board support subdirectory; 6299 Create your own board include/configs/<myboard>.h file; 6300 } 6301 Edit new board/<myboard> files 6302 Edit new include/configs/<myboard>.h 6303 6304 while (!accepted) { 6305 while (!running) { 6306 do { 6307 Add / modify source code; 6308 } until (compiles); 6309 Debug; 6310 if (clueless) 6311 email("Hi, I am having problems..."); 6312 } 6313 Send patch file to the U-Boot email list; 6314 if (reasonable critiques) 6315 Incorporate improvements from email list code review; 6316 else 6317 Defend code as written; 6318 } 6319 6320 return 0; 6321} 6322 6323void no_more_time (int sig) 6324{ 6325 hire_a_guru(); 6326} 6327 6328 6329Coding Standards: 6330----------------- 6331 6332All contributions to U-Boot should conform to the Linux kernel 6333coding style; see the file "Documentation/CodingStyle" and the script 6334"scripts/Lindent" in your Linux kernel source directory. 6335 6336Source files originating from a different project (for example the 6337MTD subsystem) are generally exempt from these guidelines and are not 6338reformatted to ease subsequent migration to newer versions of those 6339sources. 6340 6341Please note that U-Boot is implemented in C (and to some small parts in 6342Assembler); no C++ is used, so please do not use C++ style comments (//) 6343in your code. 6344 6345Please also stick to the following formatting rules: 6346- remove any trailing white space 6347- use TAB characters for indentation and vertical alignment, not spaces 6348- make sure NOT to use DOS '\r\n' line feeds 6349- do not add more than 2 consecutive empty lines to source files 6350- do not add trailing empty lines to source files 6351 6352Submissions which do not conform to the standards may be returned 6353with a request to reformat the changes. 6354 6355 6356Submitting Patches: 6357------------------- 6358 6359Since the number of patches for U-Boot is growing, we need to 6360establish some rules. Submissions which do not conform to these rules 6361may be rejected, even when they contain important and valuable stuff. 6362 6363Please see http://www.denx.de/wiki/U-Boot/Patches for details. 6364 6365Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>; 6366see http://lists.denx.de/mailman/listinfo/u-boot 6367 6368When you send a patch, please include the following information with 6369it: 6370 6371* For bug fixes: a description of the bug and how your patch fixes 6372 this bug. Please try to include a way of demonstrating that the 6373 patch actually fixes something. 6374 6375* For new features: a description of the feature and your 6376 implementation. 6377 6378* A CHANGELOG entry as plaintext (separate from the patch) 6379 6380* For major contributions, add a MAINTAINERS file with your 6381 information and associated file and directory references. 6382 6383* When you add support for a new board, don't forget to add a 6384 maintainer e-mail address to the boards.cfg file, too. 6385 6386* If your patch adds new configuration options, don't forget to 6387 document these in the README file. 6388 6389* The patch itself. If you are using git (which is *strongly* 6390 recommended) you can easily generate the patch using the 6391 "git format-patch". If you then use "git send-email" to send it to 6392 the U-Boot mailing list, you will avoid most of the common problems 6393 with some other mail clients. 6394 6395 If you cannot use git, use "diff -purN OLD NEW". If your version of 6396 diff does not support these options, then get the latest version of 6397 GNU diff. 6398 6399 The current directory when running this command shall be the parent 6400 directory of the U-Boot source tree (i. e. please make sure that 6401 your patch includes sufficient directory information for the 6402 affected files). 6403 6404 We prefer patches as plain text. MIME attachments are discouraged, 6405 and compressed attachments must not be used. 6406 6407* If one logical set of modifications affects or creates several 6408 files, all these changes shall be submitted in a SINGLE patch file. 6409 6410* Changesets that contain different, unrelated modifications shall be 6411 submitted as SEPARATE patches, one patch per changeset. 6412 6413 6414Notes: 6415 6416* Before sending the patch, run the buildman script on your patched 6417 source tree and make sure that no errors or warnings are reported 6418 for any of the boards. 6419 6420* Keep your modifications to the necessary minimum: A patch 6421 containing several unrelated changes or arbitrary reformats will be 6422 returned with a request to re-formatting / split it. 6423 6424* If you modify existing code, make sure that your new code does not 6425 add to the memory footprint of the code ;-) Small is beautiful! 6426 When adding new features, these should compile conditionally only 6427 (using #ifdef), and the resulting code with the new feature 6428 disabled must not need more memory than the old code without your 6429 modification. 6430 6431* Remember that there is a size limit of 100 kB per message on the 6432 u-boot mailing list. Bigger patches will be moderated. If they are 6433 reasonable and not too big, they will be acknowledged. But patches 6434 bigger than the size limit should be avoided. 6435