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 candidate 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 /m68k Files generic to m68k architecture 140 /microblaze Files generic to microblaze architecture 141 /mips Files generic to MIPS architecture 142 /nds32 Files generic to NDS32 architecture 143 /nios2 Files generic to Altera NIOS2 architecture 144 /openrisc Files generic to OpenRISC architecture 145 /powerpc Files generic to PowerPC architecture 146 /riscv Files generic to RISC-V architecture 147 /sandbox Files generic to HW-independent "sandbox" 148 /sh Files generic to SH architecture 149 /x86 Files generic to x86 architecture 150/api Machine/arch independent API for external apps 151/board Board dependent files 152/cmd U-Boot commands functions 153/common Misc architecture independent functions 154/configs Board default configuration files 155/disk Code for disk drive partition handling 156/doc Documentation (don't expect too much) 157/drivers Commonly used device drivers 158/dts Contains Makefile for building internal U-Boot fdt. 159/examples Example code for standalone applications, etc. 160/fs Filesystem code (cramfs, ext2, jffs2, etc.) 161/include Header Files 162/lib Library routines generic to all architectures 163/Licenses Various license files 164/net Networking code 165/post Power On Self Test 166/scripts Various build scripts and Makefiles 167/test Various unit test files 168/tools Tools to build S-Record or U-Boot images, etc. 169 170Software Configuration: 171======================= 172 173Configuration is usually done using C preprocessor defines; the 174rationale behind that is to avoid dead code whenever possible. 175 176There are two classes of configuration variables: 177 178* Configuration _OPTIONS_: 179 These are selectable by the user and have names beginning with 180 "CONFIG_". 181 182* Configuration _SETTINGS_: 183 These depend on the hardware etc. and should not be meddled with if 184 you don't know what you're doing; they have names beginning with 185 "CONFIG_SYS_". 186 187Previously, all configuration was done by hand, which involved creating 188symbolic links and editing configuration files manually. More recently, 189U-Boot has added the Kbuild infrastructure used by the Linux kernel, 190allowing you to use the "make menuconfig" command to configure your 191build. 192 193 194Selection of Processor Architecture and Board Type: 195--------------------------------------------------- 196 197For all supported boards there are ready-to-use default 198configurations available; just type "make <board_name>_defconfig". 199 200Example: For a TQM823L module type: 201 202 cd u-boot 203 make TQM823L_defconfig 204 205Note: If you're looking for the default configuration file for a board 206you're sure used to be there but is now missing, check the file 207doc/README.scrapyard for a list of no longer supported boards. 208 209Sandbox Environment: 210-------------------- 211 212U-Boot can be built natively to run on a Linux host using the 'sandbox' 213board. This allows feature development which is not board- or architecture- 214specific to be undertaken on a native platform. The sandbox is also used to 215run some of U-Boot's tests. 216 217See board/sandbox/README.sandbox for more details. 218 219 220Board Initialisation Flow: 221-------------------------- 222 223This is the intended start-up flow for boards. This should apply for both 224SPL and U-Boot proper (i.e. they both follow the same rules). 225 226Note: "SPL" stands for "Secondary Program Loader," which is explained in 227more detail later in this file. 228 229At present, SPL mostly uses a separate code path, but the function names 230and roles of each function are the same. Some boards or architectures 231may not conform to this. At least most ARM boards which use 232CONFIG_SPL_FRAMEWORK conform to this. 233 234Execution typically starts with an architecture-specific (and possibly 235CPU-specific) start.S file, such as: 236 237 - arch/arm/cpu/armv7/start.S 238 - arch/powerpc/cpu/mpc83xx/start.S 239 - arch/mips/cpu/start.S 240 241and so on. From there, three functions are called; the purpose and 242limitations of each of these functions are described below. 243 244lowlevel_init(): 245 - purpose: essential init to permit execution to reach board_init_f() 246 - no global_data or BSS 247 - there is no stack (ARMv7 may have one but it will soon be removed) 248 - must not set up SDRAM or use console 249 - must only do the bare minimum to allow execution to continue to 250 board_init_f() 251 - this is almost never needed 252 - return normally from this function 253 254board_init_f(): 255 - purpose: set up the machine ready for running board_init_r(): 256 i.e. SDRAM and serial UART 257 - global_data is available 258 - stack is in SRAM 259 - BSS is not available, so you cannot use global/static variables, 260 only stack variables and global_data 261 262 Non-SPL-specific notes: 263 - dram_init() is called to set up DRAM. If already done in SPL this 264 can do nothing 265 266 SPL-specific notes: 267 - you can override the entire board_init_f() function with your own 268 version as needed. 269 - preloader_console_init() can be called here in extremis 270 - should set up SDRAM, and anything needed to make the UART work 271 - these is no need to clear BSS, it will be done by crt0.S 272 - must return normally from this function (don't call board_init_r() 273 directly) 274 275Here the BSS is cleared. For SPL, if CONFIG_SPL_STACK_R is defined, then at 276this point the stack and global_data are relocated to below 277CONFIG_SPL_STACK_R_ADDR. For non-SPL, U-Boot is relocated to run at the top of 278memory. 279 280board_init_r(): 281 - purpose: main execution, common code 282 - global_data is available 283 - SDRAM is available 284 - BSS is available, all static/global variables can be used 285 - execution eventually continues to main_loop() 286 287 Non-SPL-specific notes: 288 - U-Boot is relocated to the top of memory and is now running from 289 there. 290 291 SPL-specific notes: 292 - stack is optionally in SDRAM, if CONFIG_SPL_STACK_R is defined and 293 CONFIG_SPL_STACK_R_ADDR points into SDRAM 294 - preloader_console_init() can be called here - typically this is 295 done by selecting CONFIG_SPL_BOARD_INIT and then supplying a 296 spl_board_init() function containing this call 297 - loads U-Boot or (in falcon mode) Linux 298 299 300 301Configuration Options: 302---------------------- 303 304Configuration depends on the combination of board and CPU type; all 305such information is kept in a configuration file 306"include/configs/<board_name>.h". 307 308Example: For a TQM823L module, all configuration settings are in 309"include/configs/TQM823L.h". 310 311 312Many of the options are named exactly as the corresponding Linux 313kernel configuration options. The intention is to make it easier to 314build a config tool - later. 315 316- ARM Platform Bus Type(CCI): 317 CoreLink Cache Coherent Interconnect (CCI) is ARM BUS which 318 provides full cache coherency between two clusters of multi-core 319 CPUs and I/O coherency for devices and I/O masters 320 321 CONFIG_SYS_FSL_HAS_CCI400 322 323 Defined For SoC that has cache coherent interconnect 324 CCN-400 325 326 CONFIG_SYS_FSL_HAS_CCN504 327 328 Defined for SoC that has cache coherent interconnect CCN-504 329 330The following options need to be configured: 331 332- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX. 333 334- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS. 335 336- Marvell Family Member 337 CONFIG_SYS_MVFS - define it if you want to enable 338 multiple fs option at one time 339 for marvell soc family 340 341- 85xx CPU Options: 342 CONFIG_SYS_PPC64 343 344 Specifies that the core is a 64-bit PowerPC implementation (implements 345 the "64" category of the Power ISA). This is necessary for ePAPR 346 compliance, among other possible reasons. 347 348 CONFIG_SYS_FSL_TBCLK_DIV 349 350 Defines the core time base clock divider ratio compared to the 351 system clock. On most PQ3 devices this is 8, on newer QorIQ 352 devices it can be 16 or 32. The ratio varies from SoC to Soc. 353 354 CONFIG_SYS_FSL_PCIE_COMPAT 355 356 Defines the string to utilize when trying to match PCIe device 357 tree nodes for the given platform. 358 359 CONFIG_SYS_FSL_ERRATUM_A004510 360 361 Enables a workaround for erratum A004510. If set, 362 then CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and 363 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set. 364 365 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV 366 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional) 367 368 Defines one or two SoC revisions (low 8 bits of SVR) 369 for which the A004510 workaround should be applied. 370 371 The rest of SVR is either not relevant to the decision 372 of whether the erratum is present (e.g. p2040 versus 373 p2041) or is implied by the build target, which controls 374 whether CONFIG_SYS_FSL_ERRATUM_A004510 is set. 375 376 See Freescale App Note 4493 for more information about 377 this erratum. 378 379 CONFIG_A003399_NOR_WORKAROUND 380 Enables a workaround for IFC erratum A003399. It is only 381 required during NOR boot. 382 383 CONFIG_A008044_WORKAROUND 384 Enables a workaround for T1040/T1042 erratum A008044. It is only 385 required during NAND boot and valid for Rev 1.0 SoC revision 386 387 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY 388 389 This is the value to write into CCSR offset 0x18600 390 according to the A004510 workaround. 391 392 CONFIG_SYS_FSL_DSP_DDR_ADDR 393 This value denotes start offset of DDR memory which is 394 connected exclusively to the DSP cores. 395 396 CONFIG_SYS_FSL_DSP_M2_RAM_ADDR 397 This value denotes start offset of M2 memory 398 which is directly connected to the DSP core. 399 400 CONFIG_SYS_FSL_DSP_M3_RAM_ADDR 401 This value denotes start offset of M3 memory which is directly 402 connected to the DSP core. 403 404 CONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT 405 This value denotes start offset of DSP CCSR space. 406 407 CONFIG_SYS_FSL_SINGLE_SOURCE_CLK 408 Single Source Clock is clocking mode present in some of FSL SoC's. 409 In this mode, a single differential clock is used to supply 410 clocks to the sysclock, ddrclock and usbclock. 411 412 CONFIG_SYS_CPC_REINIT_F 413 This CONFIG is defined when the CPC is configured as SRAM at the 414 time of U-Boot entry and is required to be re-initialized. 415 416 CONFIG_DEEP_SLEEP 417 Indicates this SoC supports deep sleep feature. If deep sleep is 418 supported, core will start to execute uboot when wakes up. 419 420- Generic CPU options: 421 CONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN 422 423 Defines the endianess of the CPU. Implementation of those 424 values is arch specific. 425 426 CONFIG_SYS_FSL_DDR 427 Freescale DDR driver in use. This type of DDR controller is 428 found in mpc83xx, mpc85xx, mpc86xx as well as some ARM core 429 SoCs. 430 431 CONFIG_SYS_FSL_DDR_ADDR 432 Freescale DDR memory-mapped register base. 433 434 CONFIG_SYS_FSL_DDR_EMU 435 Specify emulator support for DDR. Some DDR features such as 436 deskew training are not available. 437 438 CONFIG_SYS_FSL_DDRC_GEN1 439 Freescale DDR1 controller. 440 441 CONFIG_SYS_FSL_DDRC_GEN2 442 Freescale DDR2 controller. 443 444 CONFIG_SYS_FSL_DDRC_GEN3 445 Freescale DDR3 controller. 446 447 CONFIG_SYS_FSL_DDRC_GEN4 448 Freescale DDR4 controller. 449 450 CONFIG_SYS_FSL_DDRC_ARM_GEN3 451 Freescale DDR3 controller for ARM-based SoCs. 452 453 CONFIG_SYS_FSL_DDR1 454 Board config to use DDR1. It can be enabled for SoCs with 455 Freescale DDR1 or DDR2 controllers, depending on the board 456 implemetation. 457 458 CONFIG_SYS_FSL_DDR2 459 Board config to use DDR2. It can be enabled for SoCs with 460 Freescale DDR2 or DDR3 controllers, depending on the board 461 implementation. 462 463 CONFIG_SYS_FSL_DDR3 464 Board config to use DDR3. It can be enabled for SoCs with 465 Freescale DDR3 or DDR3L controllers. 466 467 CONFIG_SYS_FSL_DDR3L 468 Board config to use DDR3L. It can be enabled for SoCs with 469 DDR3L controllers. 470 471 CONFIG_SYS_FSL_DDR4 472 Board config to use DDR4. It can be enabled for SoCs with 473 DDR4 controllers. 474 475 CONFIG_SYS_FSL_IFC_BE 476 Defines the IFC controller register space as Big Endian 477 478 CONFIG_SYS_FSL_IFC_LE 479 Defines the IFC controller register space as Little Endian 480 481 CONFIG_SYS_FSL_IFC_CLK_DIV 482 Defines divider of platform clock(clock input to IFC controller). 483 484 CONFIG_SYS_FSL_LBC_CLK_DIV 485 Defines divider of platform clock(clock input to eLBC controller). 486 487 CONFIG_SYS_FSL_PBL_PBI 488 It enables addition of RCW (Power on reset configuration) in built image. 489 Please refer doc/README.pblimage for more details 490 491 CONFIG_SYS_FSL_PBL_RCW 492 It adds PBI(pre-boot instructions) commands in u-boot build image. 493 PBI commands can be used to configure SoC before it starts the execution. 494 Please refer doc/README.pblimage for more details 495 496 CONFIG_SPL_FSL_PBL 497 It adds a target to create boot binary having SPL binary in PBI format 498 concatenated with u-boot binary. 499 500 CONFIG_SYS_FSL_DDR_BE 501 Defines the DDR controller register space as Big Endian 502 503 CONFIG_SYS_FSL_DDR_LE 504 Defines the DDR controller register space as Little Endian 505 506 CONFIG_SYS_FSL_DDR_SDRAM_BASE_PHY 507 Physical address from the view of DDR controllers. It is the 508 same as CONFIG_SYS_DDR_SDRAM_BASE for all Power SoCs. But 509 it could be different for ARM SoCs. 510 511 CONFIG_SYS_FSL_DDR_INTLV_256B 512 DDR controller interleaving on 256-byte. This is a special 513 interleaving mode, handled by Dickens for Freescale layerscape 514 SoCs with ARM core. 515 516 CONFIG_SYS_FSL_DDR_MAIN_NUM_CTRLS 517 Number of controllers used as main memory. 518 519 CONFIG_SYS_FSL_OTHER_DDR_NUM_CTRLS 520 Number of controllers used for other than main memory. 521 522 CONFIG_SYS_FSL_HAS_DP_DDR 523 Defines the SoC has DP-DDR used for DPAA. 524 525 CONFIG_SYS_FSL_SEC_BE 526 Defines the SEC controller register space as Big Endian 527 528 CONFIG_SYS_FSL_SEC_LE 529 Defines the SEC controller register space as Little Endian 530 531- MIPS CPU options: 532 CONFIG_SYS_INIT_SP_OFFSET 533 534 Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack 535 pointer. This is needed for the temporary stack before 536 relocation. 537 538 CONFIG_SYS_MIPS_CACHE_MODE 539 540 Cache operation mode for the MIPS CPU. 541 See also arch/mips/include/asm/mipsregs.h. 542 Possible values are: 543 CONF_CM_CACHABLE_NO_WA 544 CONF_CM_CACHABLE_WA 545 CONF_CM_UNCACHED 546 CONF_CM_CACHABLE_NONCOHERENT 547 CONF_CM_CACHABLE_CE 548 CONF_CM_CACHABLE_COW 549 CONF_CM_CACHABLE_CUW 550 CONF_CM_CACHABLE_ACCELERATED 551 552 CONFIG_SYS_XWAY_EBU_BOOTCFG 553 554 Special option for Lantiq XWAY SoCs for booting from NOR flash. 555 See also arch/mips/cpu/mips32/start.S. 556 557 CONFIG_XWAY_SWAP_BYTES 558 559 Enable compilation of tools/xway-swap-bytes needed for Lantiq 560 XWAY SoCs for booting from NOR flash. The U-Boot image needs to 561 be swapped if a flash programmer is used. 562 563- ARM options: 564 CONFIG_SYS_EXCEPTION_VECTORS_HIGH 565 566 Select high exception vectors of the ARM core, e.g., do not 567 clear the V bit of the c1 register of CP15. 568 569 COUNTER_FREQUENCY 570 Generic timer clock source frequency. 571 572 COUNTER_FREQUENCY_REAL 573 Generic timer clock source frequency if the real clock is 574 different from COUNTER_FREQUENCY, and can only be determined 575 at run time. 576 577- Tegra SoC options: 578 CONFIG_TEGRA_SUPPORT_NON_SECURE 579 580 Support executing U-Boot in non-secure (NS) mode. Certain 581 impossible actions will be skipped if the CPU is in NS mode, 582 such as ARM architectural timer initialization. 583 584- Linux Kernel Interface: 585 CONFIG_CLOCKS_IN_MHZ 586 587 U-Boot stores all clock information in Hz 588 internally. For binary compatibility with older Linux 589 kernels (which expect the clocks passed in the 590 bd_info data to be in MHz) the environment variable 591 "clocks_in_mhz" can be defined so that U-Boot 592 converts clock data to MHZ before passing it to the 593 Linux kernel. 594 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of 595 "clocks_in_mhz=1" is automatically included in the 596 default environment. 597 598 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only] 599 600 When transferring memsize parameter to Linux, some versions 601 expect it to be in bytes, others in MB. 602 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes. 603 604 CONFIG_OF_LIBFDT 605 606 New kernel versions are expecting firmware settings to be 607 passed using flattened device trees (based on open firmware 608 concepts). 609 610 CONFIG_OF_LIBFDT 611 * New libfdt-based support 612 * Adds the "fdt" command 613 * The bootm command automatically updates the fdt 614 615 OF_TBCLK - The timebase frequency. 616 OF_STDOUT_PATH - The path to the console device 617 618 boards with QUICC Engines require OF_QE to set UCC MAC 619 addresses 620 621 CONFIG_OF_BOARD_SETUP 622 623 Board code has addition modification that it wants to make 624 to the flat device tree before handing it off to the kernel 625 626 CONFIG_OF_SYSTEM_SETUP 627 628 Other code has addition modification that it wants to make 629 to the flat device tree before handing it off to the kernel. 630 This causes ft_system_setup() to be called before booting 631 the kernel. 632 633 CONFIG_OF_IDE_FIXUP 634 635 U-Boot can detect if an IDE device is present or not. 636 If not, and this new config option is activated, U-Boot 637 removes the ATA node from the DTS before booting Linux, 638 so the Linux IDE driver does not probe the device and 639 crash. This is needed for buggy hardware (uc101) where 640 no pull down resistor is connected to the signal IDE5V_DD7. 641 642 CONFIG_MACH_TYPE [relevant for ARM only][mandatory] 643 644 This setting is mandatory for all boards that have only one 645 machine type and must be used to specify the machine type 646 number as it appears in the ARM machine registry 647 (see http://www.arm.linux.org.uk/developer/machines/). 648 Only boards that have multiple machine types supported 649 in a single configuration file and the machine type is 650 runtime discoverable, do not have to use this setting. 651 652- vxWorks boot parameters: 653 654 bootvx constructs a valid bootline using the following 655 environments variables: bootdev, bootfile, ipaddr, netmask, 656 serverip, gatewayip, hostname, othbootargs. 657 It loads the vxWorks image pointed bootfile. 658 659 Note: If a "bootargs" environment is defined, it will overwride 660 the defaults discussed just above. 661 662- Cache Configuration: 663 CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot 664 CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot 665 CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot 666 667- Cache Configuration for ARM: 668 CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache 669 controller 670 CONFIG_SYS_PL310_BASE - Physical base address of PL310 671 controller register space 672 673- Serial Ports: 674 CONFIG_PL010_SERIAL 675 676 Define this if you want support for Amba PrimeCell PL010 UARTs. 677 678 CONFIG_PL011_SERIAL 679 680 Define this if you want support for Amba PrimeCell PL011 UARTs. 681 682 CONFIG_PL011_CLOCK 683 684 If you have Amba PrimeCell PL011 UARTs, set this variable to 685 the clock speed of the UARTs. 686 687 CONFIG_PL01x_PORTS 688 689 If you have Amba PrimeCell PL010 or PL011 UARTs on your board, 690 define this to a list of base addresses for each (supported) 691 port. See e.g. include/configs/versatile.h 692 693 CONFIG_SERIAL_HW_FLOW_CONTROL 694 695 Define this variable to enable hw flow control in serial driver. 696 Current user of this option is drivers/serial/nsl16550.c driver 697 698- Console Baudrate: 699 CONFIG_BAUDRATE - in bps 700 Select one of the baudrates listed in 701 CONFIG_SYS_BAUDRATE_TABLE, see below. 702 703- Autoboot Command: 704 CONFIG_BOOTCOMMAND 705 Only needed when CONFIG_BOOTDELAY is enabled; 706 define a command string that is automatically executed 707 when no character is read on the console interface 708 within "Boot Delay" after reset. 709 710 CONFIG_RAMBOOT and CONFIG_NFSBOOT 711 The value of these goes into the environment as 712 "ramboot" and "nfsboot" respectively, and can be used 713 as a convenience, when switching between booting from 714 RAM and NFS. 715 716- Pre-Boot Commands: 717 CONFIG_PREBOOT 718 719 When this option is #defined, the existence of the 720 environment variable "preboot" will be checked 721 immediately before starting the CONFIG_BOOTDELAY 722 countdown and/or running the auto-boot command resp. 723 entering interactive mode. 724 725 This feature is especially useful when "preboot" is 726 automatically generated or modified. For an example 727 see the LWMON board specific code: here "preboot" is 728 modified when the user holds down a certain 729 combination of keys on the (special) keyboard when 730 booting the systems 731 732- Serial Download Echo Mode: 733 CONFIG_LOADS_ECHO 734 If defined to 1, all characters received during a 735 serial download (using the "loads" command) are 736 echoed back. This might be needed by some terminal 737 emulations (like "cu"), but may as well just take 738 time on others. This setting #define's the initial 739 value of the "loads_echo" environment variable. 740 741- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined) 742 CONFIG_KGDB_BAUDRATE 743 Select one of the baudrates listed in 744 CONFIG_SYS_BAUDRATE_TABLE, see below. 745 746- Removal of commands 747 If no commands are needed to boot, you can disable 748 CONFIG_CMDLINE to remove them. In this case, the command line 749 will not be available, and when U-Boot wants to execute the 750 boot command (on start-up) it will call board_run_command() 751 instead. This can reduce image size significantly for very 752 simple boot procedures. 753 754- Regular expression support: 755 CONFIG_REGEX 756 If this variable is defined, U-Boot is linked against 757 the SLRE (Super Light Regular Expression) library, 758 which adds regex support to some commands, as for 759 example "env grep" and "setexpr". 760 761- Device tree: 762 CONFIG_OF_CONTROL 763 If this variable is defined, U-Boot will use a device tree 764 to configure its devices, instead of relying on statically 765 compiled #defines in the board file. This option is 766 experimental and only available on a few boards. The device 767 tree is available in the global data as gd->fdt_blob. 768 769 U-Boot needs to get its device tree from somewhere. This can 770 be done using one of the three options below: 771 772 CONFIG_OF_EMBED 773 If this variable is defined, U-Boot will embed a device tree 774 binary in its image. This device tree file should be in the 775 board directory and called <soc>-<board>.dts. The binary file 776 is then picked up in board_init_f() and made available through 777 the global data structure as gd->fdt_blob. 778 779 CONFIG_OF_SEPARATE 780 If this variable is defined, U-Boot will build a device tree 781 binary. It will be called u-boot.dtb. Architecture-specific 782 code will locate it at run-time. Generally this works by: 783 784 cat u-boot.bin u-boot.dtb >image.bin 785 786 and in fact, U-Boot does this for you, creating a file called 787 u-boot-dtb.bin which is useful in the common case. You can 788 still use the individual files if you need something more 789 exotic. 790 791 CONFIG_OF_BOARD 792 If this variable is defined, U-Boot will use the device tree 793 provided by the board at runtime instead of embedding one with 794 the image. Only boards defining board_fdt_blob_setup() support 795 this option (see include/fdtdec.h file). 796 797- Watchdog: 798 CONFIG_WATCHDOG 799 If this variable is defined, it enables watchdog 800 support for the SoC. There must be support in the SoC 801 specific code for a watchdog. For the 8xx 802 CPUs, the SIU Watchdog feature is enabled in the SYPCR 803 register. When supported for a specific SoC is 804 available, then no further board specific code should 805 be needed to use it. 806 807 CONFIG_HW_WATCHDOG 808 When using a watchdog circuitry external to the used 809 SoC, then define this variable and provide board 810 specific code for the "hw_watchdog_reset" function. 811 812 CONFIG_AT91_HW_WDT_TIMEOUT 813 specify the timeout in seconds. default 2 seconds. 814 815- U-Boot Version: 816 CONFIG_VERSION_VARIABLE 817 If this variable is defined, an environment variable 818 named "ver" is created by U-Boot showing the U-Boot 819 version as printed by the "version" command. 820 Any change to this variable will be reverted at the 821 next reset. 822 823- Real-Time Clock: 824 825 When CONFIG_CMD_DATE is selected, the type of the RTC 826 has to be selected, too. Define exactly one of the 827 following options: 828 829 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC 830 CONFIG_RTC_MC13XXX - use MC13783 or MC13892 RTC 831 CONFIG_RTC_MC146818 - use MC146818 RTC 832 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC 833 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC 834 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC 835 CONFIG_RTC_DS1339 - use Maxim, Inc. DS1339 RTC 836 CONFIG_RTC_DS164x - use Dallas DS164x RTC 837 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC 838 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC 839 CONFIG_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337 840 CONFIG_SYS_RV3029_TCR - enable trickle charger on 841 RV3029 RTC. 842 843 Note that if the RTC uses I2C, then the I2C interface 844 must also be configured. See I2C Support, below. 845 846- GPIO Support: 847 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO 848 849 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of 850 chip-ngpio pairs that tell the PCA953X driver the number of 851 pins supported by a particular chip. 852 853 Note that if the GPIO device uses I2C, then the I2C interface 854 must also be configured. See I2C Support, below. 855 856- I/O tracing: 857 When CONFIG_IO_TRACE is selected, U-Boot intercepts all I/O 858 accesses and can checksum them or write a list of them out 859 to memory. See the 'iotrace' command for details. This is 860 useful for testing device drivers since it can confirm that 861 the driver behaves the same way before and after a code 862 change. Currently this is supported on sandbox and arm. To 863 add support for your architecture, add '#include <iotrace.h>' 864 to the bottom of arch/<arch>/include/asm/io.h and test. 865 866 Example output from the 'iotrace stats' command is below. 867 Note that if the trace buffer is exhausted, the checksum will 868 still continue to operate. 869 870 iotrace is enabled 871 Start: 10000000 (buffer start address) 872 Size: 00010000 (buffer size) 873 Offset: 00000120 (current buffer offset) 874 Output: 10000120 (start + offset) 875 Count: 00000018 (number of trace records) 876 CRC32: 9526fb66 (CRC32 of all trace records) 877 878- Timestamp Support: 879 880 When CONFIG_TIMESTAMP is selected, the timestamp 881 (date and time) of an image is printed by image 882 commands like bootm or iminfo. This option is 883 automatically enabled when you select CONFIG_CMD_DATE . 884 885- Partition Labels (disklabels) Supported: 886 Zero or more of the following: 887 CONFIG_MAC_PARTITION Apple's MacOS partition table. 888 CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc. 889 CONFIG_EFI_PARTITION GPT partition table, common when EFI is the 890 bootloader. Note 2TB partition limit; see 891 disk/part_efi.c 892 CONFIG_MTD_PARTITIONS Memory Technology Device partition table. 893 894 If IDE or SCSI support is enabled (CONFIG_IDE or 895 CONFIG_SCSI) you must configure support for at 896 least one non-MTD partition type as well. 897 898- IDE Reset method: 899 CONFIG_IDE_RESET_ROUTINE - this is defined in several 900 board configurations files but used nowhere! 901 902 CONFIG_IDE_RESET - is this is defined, IDE Reset will 903 be performed by calling the function 904 ide_set_reset(int reset) 905 which has to be defined in a board specific file 906 907- ATAPI Support: 908 CONFIG_ATAPI 909 910 Set this to enable ATAPI support. 911 912- LBA48 Support 913 CONFIG_LBA48 914 915 Set this to enable support for disks larger than 137GB 916 Also look at CONFIG_SYS_64BIT_LBA. 917 Whithout these , LBA48 support uses 32bit variables and will 'only' 918 support disks up to 2.1TB. 919 920 CONFIG_SYS_64BIT_LBA: 921 When enabled, makes the IDE subsystem use 64bit sector addresses. 922 Default is 32bit. 923 924- SCSI Support: 925 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and 926 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID * 927 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the 928 maximum numbers of LUNs, SCSI ID's and target 929 devices. 930 931 The environment variable 'scsidevs' is set to the number of 932 SCSI devices found during the last scan. 933 934- NETWORK Support (PCI): 935 CONFIG_E1000 936 Support for Intel 8254x/8257x gigabit chips. 937 938 CONFIG_E1000_SPI 939 Utility code for direct access to the SPI bus on Intel 8257x. 940 This does not do anything useful unless you set at least one 941 of CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC. 942 943 CONFIG_E1000_SPI_GENERIC 944 Allow generic access to the SPI bus on the Intel 8257x, for 945 example with the "sspi" command. 946 947 CONFIG_EEPRO100 948 Support for Intel 82557/82559/82559ER chips. 949 Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM 950 write routine for first time initialisation. 951 952 CONFIG_TULIP 953 Support for Digital 2114x chips. 954 Optional CONFIG_TULIP_SELECT_MEDIA for board specific 955 modem chip initialisation (KS8761/QS6611). 956 957 CONFIG_NATSEMI 958 Support for National dp83815 chips. 959 960 CONFIG_NS8382X 961 Support for National dp8382[01] gigabit chips. 962 963- NETWORK Support (other): 964 965 CONFIG_DRIVER_AT91EMAC 966 Support for AT91RM9200 EMAC. 967 968 CONFIG_RMII 969 Define this to use reduced MII inteface 970 971 CONFIG_DRIVER_AT91EMAC_QUIET 972 If this defined, the driver is quiet. 973 The driver doen't show link status messages. 974 975 CONFIG_CALXEDA_XGMAC 976 Support for the Calxeda XGMAC device 977 978 CONFIG_LAN91C96 979 Support for SMSC's LAN91C96 chips. 980 981 CONFIG_LAN91C96_USE_32_BIT 982 Define this to enable 32 bit addressing 983 984 CONFIG_SMC91111 985 Support for SMSC's LAN91C111 chip 986 987 CONFIG_SMC91111_BASE 988 Define this to hold the physical address 989 of the device (I/O space) 990 991 CONFIG_SMC_USE_32_BIT 992 Define this if data bus is 32 bits 993 994 CONFIG_SMC_USE_IOFUNCS 995 Define this to use i/o functions instead of macros 996 (some hardware wont work with macros) 997 998 CONFIG_DRIVER_TI_EMAC 999 Support for davinci emac 1000 1001 CONFIG_SYS_DAVINCI_EMAC_PHY_COUNT 1002 Define this if you have more then 3 PHYs. 1003 1004 CONFIG_FTGMAC100 1005 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet 1006 1007 CONFIG_FTGMAC100_EGIGA 1008 Define this to use GE link update with gigabit PHY. 1009 Define this if FTGMAC100 is connected to gigabit PHY. 1010 If your system has 10/100 PHY only, it might not occur 1011 wrong behavior. Because PHY usually return timeout or 1012 useless data when polling gigabit status and gigabit 1013 control registers. This behavior won't affect the 1014 correctnessof 10/100 link speed update. 1015 1016 CONFIG_SH_ETHER 1017 Support for Renesas on-chip Ethernet controller 1018 1019 CONFIG_SH_ETHER_USE_PORT 1020 Define the number of ports to be used 1021 1022 CONFIG_SH_ETHER_PHY_ADDR 1023 Define the ETH PHY's address 1024 1025 CONFIG_SH_ETHER_CACHE_WRITEBACK 1026 If this option is set, the driver enables cache flush. 1027 1028- PWM Support: 1029 CONFIG_PWM_IMX 1030 Support for PWM module on the imx6. 1031 1032- TPM Support: 1033 CONFIG_TPM 1034 Support TPM devices. 1035 1036 CONFIG_TPM_TIS_INFINEON 1037 Support for Infineon i2c bus TPM devices. Only one device 1038 per system is supported at this time. 1039 1040 CONFIG_TPM_TIS_I2C_BURST_LIMITATION 1041 Define the burst count bytes upper limit 1042 1043 CONFIG_TPM_ST33ZP24 1044 Support for STMicroelectronics TPM devices. Requires DM_TPM support. 1045 1046 CONFIG_TPM_ST33ZP24_I2C 1047 Support for STMicroelectronics ST33ZP24 I2C devices. 1048 Requires TPM_ST33ZP24 and I2C. 1049 1050 CONFIG_TPM_ST33ZP24_SPI 1051 Support for STMicroelectronics ST33ZP24 SPI devices. 1052 Requires TPM_ST33ZP24 and SPI. 1053 1054 CONFIG_TPM_ATMEL_TWI 1055 Support for Atmel TWI TPM device. Requires I2C support. 1056 1057 CONFIG_TPM_TIS_LPC 1058 Support for generic parallel port TPM devices. Only one device 1059 per system is supported at this time. 1060 1061 CONFIG_TPM_TIS_BASE_ADDRESS 1062 Base address where the generic TPM device is mapped 1063 to. Contemporary x86 systems usually map it at 1064 0xfed40000. 1065 1066 CONFIG_TPM 1067 Define this to enable the TPM support library which provides 1068 functional interfaces to some TPM commands. 1069 Requires support for a TPM device. 1070 1071 CONFIG_TPM_AUTH_SESSIONS 1072 Define this to enable authorized functions in the TPM library. 1073 Requires CONFIG_TPM and CONFIG_SHA1. 1074 1075- USB Support: 1076 At the moment only the UHCI host controller is 1077 supported (PIP405, MIP405); define 1078 CONFIG_USB_UHCI to enable it. 1079 define CONFIG_USB_KEYBOARD to enable the USB Keyboard 1080 and define CONFIG_USB_STORAGE to enable the USB 1081 storage devices. 1082 Note: 1083 Supported are USB Keyboards and USB Floppy drives 1084 (TEAC FD-05PUB). 1085 1086 CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the 1087 txfilltuning field in the EHCI controller on reset. 1088 1089 CONFIG_USB_DWC2_REG_ADDR the physical CPU address of the DWC2 1090 HW module registers. 1091 1092- USB Device: 1093 Define the below if you wish to use the USB console. 1094 Once firmware is rebuilt from a serial console issue the 1095 command "setenv stdin usbtty; setenv stdout usbtty" and 1096 attach your USB cable. The Unix command "dmesg" should print 1097 it has found a new device. The environment variable usbtty 1098 can be set to gserial or cdc_acm to enable your device to 1099 appear to a USB host as a Linux gserial device or a 1100 Common Device Class Abstract Control Model serial device. 1101 If you select usbtty = gserial you should be able to enumerate 1102 a Linux host by 1103 # modprobe usbserial vendor=0xVendorID product=0xProductID 1104 else if using cdc_acm, simply setting the environment 1105 variable usbtty to be cdc_acm should suffice. The following 1106 might be defined in YourBoardName.h 1107 1108 CONFIG_USB_DEVICE 1109 Define this to build a UDC device 1110 1111 CONFIG_USB_TTY 1112 Define this to have a tty type of device available to 1113 talk to the UDC device 1114 1115 CONFIG_USBD_HS 1116 Define this to enable the high speed support for usb 1117 device and usbtty. If this feature is enabled, a routine 1118 int is_usbd_high_speed(void) 1119 also needs to be defined by the driver to dynamically poll 1120 whether the enumeration has succeded at high speed or full 1121 speed. 1122 1123 CONFIG_SYS_CONSOLE_IS_IN_ENV 1124 Define this if you want stdin, stdout &/or stderr to 1125 be set to usbtty. 1126 1127 If you have a USB-IF assigned VendorID then you may wish to 1128 define your own vendor specific values either in BoardName.h 1129 or directly in usbd_vendor_info.h. If you don't define 1130 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME, 1131 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot 1132 should pretend to be a Linux device to it's target host. 1133 1134 CONFIG_USBD_MANUFACTURER 1135 Define this string as the name of your company for 1136 - CONFIG_USBD_MANUFACTURER "my company" 1137 1138 CONFIG_USBD_PRODUCT_NAME 1139 Define this string as the name of your product 1140 - CONFIG_USBD_PRODUCT_NAME "acme usb device" 1141 1142 CONFIG_USBD_VENDORID 1143 Define this as your assigned Vendor ID from the USB 1144 Implementors Forum. This *must* be a genuine Vendor ID 1145 to avoid polluting the USB namespace. 1146 - CONFIG_USBD_VENDORID 0xFFFF 1147 1148 CONFIG_USBD_PRODUCTID 1149 Define this as the unique Product ID 1150 for your device 1151 - CONFIG_USBD_PRODUCTID 0xFFFF 1152 1153- ULPI Layer Support: 1154 The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via 1155 the generic ULPI layer. The generic layer accesses the ULPI PHY 1156 via the platform viewport, so you need both the genric layer and 1157 the viewport enabled. Currently only Chipidea/ARC based 1158 viewport is supported. 1159 To enable the ULPI layer support, define CONFIG_USB_ULPI and 1160 CONFIG_USB_ULPI_VIEWPORT in your board configuration file. 1161 If your ULPI phy needs a different reference clock than the 1162 standard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to 1163 the appropriate value in Hz. 1164 1165- MMC Support: 1166 The MMC controller on the Intel PXA is supported. To 1167 enable this define CONFIG_MMC. The MMC can be 1168 accessed from the boot prompt by mapping the device 1169 to physical memory similar to flash. Command line is 1170 enabled with CONFIG_CMD_MMC. The MMC driver also works with 1171 the FAT fs. This is enabled with CONFIG_CMD_FAT. 1172 1173 CONFIG_SH_MMCIF 1174 Support for Renesas on-chip MMCIF controller 1175 1176 CONFIG_SH_MMCIF_ADDR 1177 Define the base address of MMCIF registers 1178 1179 CONFIG_SH_MMCIF_CLK 1180 Define the clock frequency for MMCIF 1181 1182 CONFIG_SUPPORT_EMMC_BOOT 1183 Enable some additional features of the eMMC boot partitions. 1184 1185 CONFIG_SUPPORT_EMMC_RPMB 1186 Enable the commands for reading, writing and programming the 1187 key for the Replay Protection Memory Block partition in eMMC. 1188 1189- USB Device Firmware Update (DFU) class support: 1190 CONFIG_DFU_OVER_USB 1191 This enables the USB portion of the DFU USB class 1192 1193 CONFIG_DFU_MMC 1194 This enables support for exposing (e)MMC devices via DFU. 1195 1196 CONFIG_DFU_NAND 1197 This enables support for exposing NAND devices via DFU. 1198 1199 CONFIG_DFU_RAM 1200 This enables support for exposing RAM via DFU. 1201 Note: DFU spec refer to non-volatile memory usage, but 1202 allow usages beyond the scope of spec - here RAM usage, 1203 one that would help mostly the developer. 1204 1205 CONFIG_SYS_DFU_DATA_BUF_SIZE 1206 Dfu transfer uses a buffer before writing data to the 1207 raw storage device. Make the size (in bytes) of this buffer 1208 configurable. The size of this buffer is also configurable 1209 through the "dfu_bufsiz" environment variable. 1210 1211 CONFIG_SYS_DFU_MAX_FILE_SIZE 1212 When updating files rather than the raw storage device, 1213 we use a static buffer to copy the file into and then write 1214 the buffer once we've been given the whole file. Define 1215 this to the maximum filesize (in bytes) for the buffer. 1216 Default is 4 MiB if undefined. 1217 1218 DFU_DEFAULT_POLL_TIMEOUT 1219 Poll timeout [ms], is the timeout a device can send to the 1220 host. The host must wait for this timeout before sending 1221 a subsequent DFU_GET_STATUS request to the device. 1222 1223 DFU_MANIFEST_POLL_TIMEOUT 1224 Poll timeout [ms], which the device sends to the host when 1225 entering dfuMANIFEST state. Host waits this timeout, before 1226 sending again an USB request to the device. 1227 1228- Journaling Flash filesystem support: 1229 CONFIG_JFFS2_NAND 1230 Define these for a default partition on a NAND device 1231 1232 CONFIG_SYS_JFFS2_FIRST_SECTOR, 1233 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS 1234 Define these for a default partition on a NOR device 1235 1236- Keyboard Support: 1237 See Kconfig help for available keyboard drivers. 1238 1239 CONFIG_KEYBOARD 1240 1241 Define this to enable a custom keyboard support. 1242 This simply calls drv_keyboard_init() which must be 1243 defined in your board-specific files. This option is deprecated 1244 and is only used by novena. For new boards, use driver model 1245 instead. 1246 1247- Video support: 1248 CONFIG_FSL_DIU_FB 1249 Enable the Freescale DIU video driver. Reference boards for 1250 SOCs that have a DIU should define this macro to enable DIU 1251 support, and should also define these other macros: 1252 1253 CONFIG_SYS_DIU_ADDR 1254 CONFIG_VIDEO 1255 CONFIG_CFB_CONSOLE 1256 CONFIG_VIDEO_SW_CURSOR 1257 CONFIG_VGA_AS_SINGLE_DEVICE 1258 CONFIG_VIDEO_LOGO 1259 CONFIG_VIDEO_BMP_LOGO 1260 1261 The DIU driver will look for the 'video-mode' environment 1262 variable, and if defined, enable the DIU as a console during 1263 boot. See the documentation file doc/README.video for a 1264 description of this variable. 1265 1266- LCD Support: CONFIG_LCD 1267 1268 Define this to enable LCD support (for output to LCD 1269 display); also select one of the supported displays 1270 by defining one of these: 1271 1272 CONFIG_ATMEL_LCD: 1273 1274 HITACHI TX09D70VM1CCA, 3.5", 240x320. 1275 1276 CONFIG_NEC_NL6448AC33: 1277 1278 NEC NL6448AC33-18. Active, color, single scan. 1279 1280 CONFIG_NEC_NL6448BC20 1281 1282 NEC NL6448BC20-08. 6.5", 640x480. 1283 Active, color, single scan. 1284 1285 CONFIG_NEC_NL6448BC33_54 1286 1287 NEC NL6448BC33-54. 10.4", 640x480. 1288 Active, color, single scan. 1289 1290 CONFIG_SHARP_16x9 1291 1292 Sharp 320x240. Active, color, single scan. 1293 It isn't 16x9, and I am not sure what it is. 1294 1295 CONFIG_SHARP_LQ64D341 1296 1297 Sharp LQ64D341 display, 640x480. 1298 Active, color, single scan. 1299 1300 CONFIG_HLD1045 1301 1302 HLD1045 display, 640x480. 1303 Active, color, single scan. 1304 1305 CONFIG_OPTREX_BW 1306 1307 Optrex CBL50840-2 NF-FW 99 22 M5 1308 or 1309 Hitachi LMG6912RPFC-00T 1310 or 1311 Hitachi SP14Q002 1312 1313 320x240. Black & white. 1314 1315 CONFIG_LCD_ALIGNMENT 1316 1317 Normally the LCD is page-aligned (typically 4KB). If this is 1318 defined then the LCD will be aligned to this value instead. 1319 For ARM it is sometimes useful to use MMU_SECTION_SIZE 1320 here, since it is cheaper to change data cache settings on 1321 a per-section basis. 1322 1323 1324 CONFIG_LCD_ROTATION 1325 1326 Sometimes, for example if the display is mounted in portrait 1327 mode or even if it's mounted landscape but rotated by 180degree, 1328 we need to rotate our content of the display relative to the 1329 framebuffer, so that user can read the messages which are 1330 printed out. 1331 Once CONFIG_LCD_ROTATION is defined, the lcd_console will be 1332 initialized with a given rotation from "vl_rot" out of 1333 "vidinfo_t" which is provided by the board specific code. 1334 The value for vl_rot is coded as following (matching to 1335 fbcon=rotate:<n> linux-kernel commandline): 1336 0 = no rotation respectively 0 degree 1337 1 = 90 degree rotation 1338 2 = 180 degree rotation 1339 3 = 270 degree rotation 1340 1341 If CONFIG_LCD_ROTATION is not defined, the console will be 1342 initialized with 0degree rotation. 1343 1344 CONFIG_LCD_BMP_RLE8 1345 1346 Support drawing of RLE8-compressed bitmaps on the LCD. 1347 1348 CONFIG_I2C_EDID 1349 1350 Enables an 'i2c edid' command which can read EDID 1351 information over I2C from an attached LCD display. 1352 1353- Splash Screen Support: CONFIG_SPLASH_SCREEN 1354 1355 If this option is set, the environment is checked for 1356 a variable "splashimage". If found, the usual display 1357 of logo, copyright and system information on the LCD 1358 is suppressed and the BMP image at the address 1359 specified in "splashimage" is loaded instead. The 1360 console is redirected to the "nulldev", too. This 1361 allows for a "silent" boot where a splash screen is 1362 loaded very quickly after power-on. 1363 1364 CONFIG_SPLASHIMAGE_GUARD 1365 1366 If this option is set, then U-Boot will prevent the environment 1367 variable "splashimage" from being set to a problematic address 1368 (see doc/README.displaying-bmps). 1369 This option is useful for targets where, due to alignment 1370 restrictions, an improperly aligned BMP image will cause a data 1371 abort. If you think you will not have problems with unaligned 1372 accesses (for example because your toolchain prevents them) 1373 there is no need to set this option. 1374 1375 CONFIG_SPLASH_SCREEN_ALIGN 1376 1377 If this option is set the splash image can be freely positioned 1378 on the screen. Environment variable "splashpos" specifies the 1379 position as "x,y". If a positive number is given it is used as 1380 number of pixel from left/top. If a negative number is given it 1381 is used as number of pixel from right/bottom. You can also 1382 specify 'm' for centering the image. 1383 1384 Example: 1385 setenv splashpos m,m 1386 => image at center of screen 1387 1388 setenv splashpos 30,20 1389 => image at x = 30 and y = 20 1390 1391 setenv splashpos -10,m 1392 => vertically centered image 1393 at x = dspWidth - bmpWidth - 9 1394 1395- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP 1396 1397 If this option is set, additionally to standard BMP 1398 images, gzipped BMP images can be displayed via the 1399 splashscreen support or the bmp command. 1400 1401- Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8 1402 1403 If this option is set, 8-bit RLE compressed BMP images 1404 can be displayed via the splashscreen support or the 1405 bmp command. 1406 1407- Compression support: 1408 CONFIG_GZIP 1409 1410 Enabled by default to support gzip compressed images. 1411 1412 CONFIG_BZIP2 1413 1414 If this option is set, support for bzip2 compressed 1415 images is included. If not, only uncompressed and gzip 1416 compressed images are supported. 1417 1418 NOTE: the bzip2 algorithm requires a lot of RAM, so 1419 the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should 1420 be at least 4MB. 1421 1422- MII/PHY support: 1423 CONFIG_PHY_ADDR 1424 1425 The address of PHY on MII bus. 1426 1427 CONFIG_PHY_CLOCK_FREQ (ppc4xx) 1428 1429 The clock frequency of the MII bus 1430 1431 CONFIG_PHY_RESET_DELAY 1432 1433 Some PHY like Intel LXT971A need extra delay after 1434 reset before any MII register access is possible. 1435 For such PHY, set this option to the usec delay 1436 required. (minimum 300usec for LXT971A) 1437 1438 CONFIG_PHY_CMD_DELAY (ppc4xx) 1439 1440 Some PHY like Intel LXT971A need extra delay after 1441 command issued before MII status register can be read 1442 1443- IP address: 1444 CONFIG_IPADDR 1445 1446 Define a default value for the IP address to use for 1447 the default Ethernet interface, in case this is not 1448 determined through e.g. bootp. 1449 (Environment variable "ipaddr") 1450 1451- Server IP address: 1452 CONFIG_SERVERIP 1453 1454 Defines a default value for the IP address of a TFTP 1455 server to contact when using the "tftboot" command. 1456 (Environment variable "serverip") 1457 1458 CONFIG_KEEP_SERVERADDR 1459 1460 Keeps the server's MAC address, in the env 'serveraddr' 1461 for passing to bootargs (like Linux's netconsole option) 1462 1463- Gateway IP address: 1464 CONFIG_GATEWAYIP 1465 1466 Defines a default value for the IP address of the 1467 default router where packets to other networks are 1468 sent to. 1469 (Environment variable "gatewayip") 1470 1471- Subnet mask: 1472 CONFIG_NETMASK 1473 1474 Defines a default value for the subnet mask (or 1475 routing prefix) which is used to determine if an IP 1476 address belongs to the local subnet or needs to be 1477 forwarded through a router. 1478 (Environment variable "netmask") 1479 1480- Multicast TFTP Mode: 1481 CONFIG_MCAST_TFTP 1482 1483 Defines whether you want to support multicast TFTP as per 1484 rfc-2090; for example to work with atftp. Lets lots of targets 1485 tftp down the same boot image concurrently. Note: the Ethernet 1486 driver in use must provide a function: mcast() to join/leave a 1487 multicast group. 1488 1489- BOOTP Recovery Mode: 1490 CONFIG_BOOTP_RANDOM_DELAY 1491 1492 If you have many targets in a network that try to 1493 boot using BOOTP, you may want to avoid that all 1494 systems send out BOOTP requests at precisely the same 1495 moment (which would happen for instance at recovery 1496 from a power failure, when all systems will try to 1497 boot, thus flooding the BOOTP server. Defining 1498 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be 1499 inserted before sending out BOOTP requests. The 1500 following delays are inserted then: 1501 1502 1st BOOTP request: delay 0 ... 1 sec 1503 2nd BOOTP request: delay 0 ... 2 sec 1504 3rd BOOTP request: delay 0 ... 4 sec 1505 4th and following 1506 BOOTP requests: delay 0 ... 8 sec 1507 1508 CONFIG_BOOTP_ID_CACHE_SIZE 1509 1510 BOOTP packets are uniquely identified using a 32-bit ID. The 1511 server will copy the ID from client requests to responses and 1512 U-Boot will use this to determine if it is the destination of 1513 an incoming response. Some servers will check that addresses 1514 aren't in use before handing them out (usually using an ARP 1515 ping) and therefore take up to a few hundred milliseconds to 1516 respond. Network congestion may also influence the time it 1517 takes for a response to make it back to the client. If that 1518 time is too long, U-Boot will retransmit requests. In order 1519 to allow earlier responses to still be accepted after these 1520 retransmissions, U-Boot's BOOTP client keeps a small cache of 1521 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this 1522 cache. The default is to keep IDs for up to four outstanding 1523 requests. Increasing this will allow U-Boot to accept offers 1524 from a BOOTP client in networks with unusually high latency. 1525 1526- DHCP Advanced Options: 1527 You can fine tune the DHCP functionality by defining 1528 CONFIG_BOOTP_* symbols: 1529 1530 CONFIG_BOOTP_NISDOMAIN 1531 CONFIG_BOOTP_BOOTFILESIZE 1532 CONFIG_BOOTP_SEND_HOSTNAME 1533 CONFIG_BOOTP_NTPSERVER 1534 CONFIG_BOOTP_TIMEOFFSET 1535 CONFIG_BOOTP_VENDOREX 1536 CONFIG_BOOTP_MAY_FAIL 1537 1538 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip 1539 environment variable, not the BOOTP server. 1540 1541 CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found 1542 after the configured retry count, the call will fail 1543 instead of starting over. This can be used to fail over 1544 to Link-local IP address configuration if the DHCP server 1545 is not available. 1546 1547 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable 1548 to do a dynamic update of a DNS server. To do this, they 1549 need the hostname of the DHCP requester. 1550 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content 1551 of the "hostname" environment variable is passed as 1552 option 12 to the DHCP server. 1553 1554 CONFIG_BOOTP_DHCP_REQUEST_DELAY 1555 1556 A 32bit value in microseconds for a delay between 1557 receiving a "DHCP Offer" and sending the "DHCP Request". 1558 This fixes a problem with certain DHCP servers that don't 1559 respond 100% of the time to a "DHCP request". E.g. On an 1560 AT91RM9200 processor running at 180MHz, this delay needed 1561 to be *at least* 15,000 usec before a Windows Server 2003 1562 DHCP server would reply 100% of the time. I recommend at 1563 least 50,000 usec to be safe. The alternative is to hope 1564 that one of the retries will be successful but note that 1565 the DHCP timeout and retry process takes a longer than 1566 this delay. 1567 1568 - Link-local IP address negotiation: 1569 Negotiate with other link-local clients on the local network 1570 for an address that doesn't require explicit configuration. 1571 This is especially useful if a DHCP server cannot be guaranteed 1572 to exist in all environments that the device must operate. 1573 1574 See doc/README.link-local for more information. 1575 1576 - MAC address from environment variables 1577 1578 FDT_SEQ_MACADDR_FROM_ENV 1579 1580 Fix-up device tree with MAC addresses fetched sequentially from 1581 environment variables. This config work on assumption that 1582 non-usable ethernet node of device-tree are either not present 1583 or their status has been marked as "disabled". 1584 1585 - CDP Options: 1586 CONFIG_CDP_DEVICE_ID 1587 1588 The device id used in CDP trigger frames. 1589 1590 CONFIG_CDP_DEVICE_ID_PREFIX 1591 1592 A two character string which is prefixed to the MAC address 1593 of the device. 1594 1595 CONFIG_CDP_PORT_ID 1596 1597 A printf format string which contains the ascii name of 1598 the port. Normally is set to "eth%d" which sets 1599 eth0 for the first Ethernet, eth1 for the second etc. 1600 1601 CONFIG_CDP_CAPABILITIES 1602 1603 A 32bit integer which indicates the device capabilities; 1604 0x00000010 for a normal host which does not forwards. 1605 1606 CONFIG_CDP_VERSION 1607 1608 An ascii string containing the version of the software. 1609 1610 CONFIG_CDP_PLATFORM 1611 1612 An ascii string containing the name of the platform. 1613 1614 CONFIG_CDP_TRIGGER 1615 1616 A 32bit integer sent on the trigger. 1617 1618 CONFIG_CDP_POWER_CONSUMPTION 1619 1620 A 16bit integer containing the power consumption of the 1621 device in .1 of milliwatts. 1622 1623 CONFIG_CDP_APPLIANCE_VLAN_TYPE 1624 1625 A byte containing the id of the VLAN. 1626 1627- Status LED: CONFIG_LED_STATUS 1628 1629 Several configurations allow to display the current 1630 status using a LED. For instance, the LED will blink 1631 fast while running U-Boot code, stop blinking as 1632 soon as a reply to a BOOTP request was received, and 1633 start blinking slow once the Linux kernel is running 1634 (supported by a status LED driver in the Linux 1635 kernel). Defining CONFIG_LED_STATUS enables this 1636 feature in U-Boot. 1637 1638 Additional options: 1639 1640 CONFIG_LED_STATUS_GPIO 1641 The status LED can be connected to a GPIO pin. 1642 In such cases, the gpio_led driver can be used as a 1643 status LED backend implementation. Define CONFIG_LED_STATUS_GPIO 1644 to include the gpio_led driver in the U-Boot binary. 1645 1646 CONFIG_GPIO_LED_INVERTED_TABLE 1647 Some GPIO connected LEDs may have inverted polarity in which 1648 case the GPIO high value corresponds to LED off state and 1649 GPIO low value corresponds to LED on state. 1650 In such cases CONFIG_GPIO_LED_INVERTED_TABLE may be defined 1651 with a list of GPIO LEDs that have inverted polarity. 1652 1653- I2C Support: CONFIG_SYS_I2C 1654 1655 This enable the NEW i2c subsystem, and will allow you to use 1656 i2c commands at the u-boot command line (as long as you set 1657 CONFIG_CMD_I2C in CONFIG_COMMANDS) and communicate with i2c 1658 based realtime clock chips or other i2c devices. See 1659 common/cmd_i2c.c for a description of the command line 1660 interface. 1661 1662 ported i2c driver to the new framework: 1663 - drivers/i2c/soft_i2c.c: 1664 - activate first bus with CONFIG_SYS_I2C_SOFT define 1665 CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE 1666 for defining speed and slave address 1667 - activate second bus with I2C_SOFT_DECLARATIONS2 define 1668 CONFIG_SYS_I2C_SOFT_SPEED_2 and CONFIG_SYS_I2C_SOFT_SLAVE_2 1669 for defining speed and slave address 1670 - activate third bus with I2C_SOFT_DECLARATIONS3 define 1671 CONFIG_SYS_I2C_SOFT_SPEED_3 and CONFIG_SYS_I2C_SOFT_SLAVE_3 1672 for defining speed and slave address 1673 - activate fourth bus with I2C_SOFT_DECLARATIONS4 define 1674 CONFIG_SYS_I2C_SOFT_SPEED_4 and CONFIG_SYS_I2C_SOFT_SLAVE_4 1675 for defining speed and slave address 1676 1677 - drivers/i2c/fsl_i2c.c: 1678 - activate i2c driver with CONFIG_SYS_I2C_FSL 1679 define CONFIG_SYS_FSL_I2C_OFFSET for setting the register 1680 offset CONFIG_SYS_FSL_I2C_SPEED for the i2c speed and 1681 CONFIG_SYS_FSL_I2C_SLAVE for the slave addr of the first 1682 bus. 1683 - If your board supports a second fsl i2c bus, define 1684 CONFIG_SYS_FSL_I2C2_OFFSET for the register offset 1685 CONFIG_SYS_FSL_I2C2_SPEED for the speed and 1686 CONFIG_SYS_FSL_I2C2_SLAVE for the slave address of the 1687 second bus. 1688 1689 - drivers/i2c/tegra_i2c.c: 1690 - activate this driver with CONFIG_SYS_I2C_TEGRA 1691 - This driver adds 4 i2c buses with a fix speed from 1692 100000 and the slave addr 0! 1693 1694 - drivers/i2c/ppc4xx_i2c.c 1695 - activate this driver with CONFIG_SYS_I2C_PPC4XX 1696 - CONFIG_SYS_I2C_PPC4XX_CH0 activate hardware channel 0 1697 - CONFIG_SYS_I2C_PPC4XX_CH1 activate hardware channel 1 1698 1699 - drivers/i2c/i2c_mxc.c 1700 - activate this driver with CONFIG_SYS_I2C_MXC 1701 - enable bus 1 with CONFIG_SYS_I2C_MXC_I2C1 1702 - enable bus 2 with CONFIG_SYS_I2C_MXC_I2C2 1703 - enable bus 3 with CONFIG_SYS_I2C_MXC_I2C3 1704 - enable bus 4 with CONFIG_SYS_I2C_MXC_I2C4 1705 - define speed for bus 1 with CONFIG_SYS_MXC_I2C1_SPEED 1706 - define slave for bus 1 with CONFIG_SYS_MXC_I2C1_SLAVE 1707 - define speed for bus 2 with CONFIG_SYS_MXC_I2C2_SPEED 1708 - define slave for bus 2 with CONFIG_SYS_MXC_I2C2_SLAVE 1709 - define speed for bus 3 with CONFIG_SYS_MXC_I2C3_SPEED 1710 - define slave for bus 3 with CONFIG_SYS_MXC_I2C3_SLAVE 1711 - define speed for bus 4 with CONFIG_SYS_MXC_I2C4_SPEED 1712 - define slave for bus 4 with CONFIG_SYS_MXC_I2C4_SLAVE 1713 If those defines are not set, default value is 100000 1714 for speed, and 0 for slave. 1715 1716 - drivers/i2c/rcar_i2c.c: 1717 - activate this driver with CONFIG_SYS_I2C_RCAR 1718 - This driver adds 4 i2c buses 1719 1720 - CONFIG_SYS_RCAR_I2C0_BASE for setting the register channel 0 1721 - CONFIG_SYS_RCAR_I2C0_SPEED for for the speed channel 0 1722 - CONFIG_SYS_RCAR_I2C1_BASE for setting the register channel 1 1723 - CONFIG_SYS_RCAR_I2C1_SPEED for for the speed channel 1 1724 - CONFIG_SYS_RCAR_I2C2_BASE for setting the register channel 2 1725 - CONFIG_SYS_RCAR_I2C2_SPEED for for the speed channel 2 1726 - CONFIG_SYS_RCAR_I2C3_BASE for setting the register channel 3 1727 - CONFIG_SYS_RCAR_I2C3_SPEED for for the speed channel 3 1728 - CONFIF_SYS_RCAR_I2C_NUM_CONTROLLERS for number of i2c buses 1729 1730 - drivers/i2c/sh_i2c.c: 1731 - activate this driver with CONFIG_SYS_I2C_SH 1732 - This driver adds from 2 to 5 i2c buses 1733 1734 - CONFIG_SYS_I2C_SH_BASE0 for setting the register channel 0 1735 - CONFIG_SYS_I2C_SH_SPEED0 for for the speed channel 0 1736 - CONFIG_SYS_I2C_SH_BASE1 for setting the register channel 1 1737 - CONFIG_SYS_I2C_SH_SPEED1 for for the speed channel 1 1738 - CONFIG_SYS_I2C_SH_BASE2 for setting the register channel 2 1739 - CONFIG_SYS_I2C_SH_SPEED2 for for the speed channel 2 1740 - CONFIG_SYS_I2C_SH_BASE3 for setting the register channel 3 1741 - CONFIG_SYS_I2C_SH_SPEED3 for for the speed channel 3 1742 - CONFIG_SYS_I2C_SH_BASE4 for setting the register channel 4 1743 - CONFIG_SYS_I2C_SH_SPEED4 for for the speed channel 4 1744 - CONFIG_SYS_I2C_SH_NUM_CONTROLLERS for number of i2c buses 1745 1746 - drivers/i2c/omap24xx_i2c.c 1747 - activate this driver with CONFIG_SYS_I2C_OMAP24XX 1748 - CONFIG_SYS_OMAP24_I2C_SPEED speed channel 0 1749 - CONFIG_SYS_OMAP24_I2C_SLAVE slave addr channel 0 1750 - CONFIG_SYS_OMAP24_I2C_SPEED1 speed channel 1 1751 - CONFIG_SYS_OMAP24_I2C_SLAVE1 slave addr channel 1 1752 - CONFIG_SYS_OMAP24_I2C_SPEED2 speed channel 2 1753 - CONFIG_SYS_OMAP24_I2C_SLAVE2 slave addr channel 2 1754 - CONFIG_SYS_OMAP24_I2C_SPEED3 speed channel 3 1755 - CONFIG_SYS_OMAP24_I2C_SLAVE3 slave addr channel 3 1756 - CONFIG_SYS_OMAP24_I2C_SPEED4 speed channel 4 1757 - CONFIG_SYS_OMAP24_I2C_SLAVE4 slave addr channel 4 1758 1759 - drivers/i2c/zynq_i2c.c 1760 - activate this driver with CONFIG_SYS_I2C_ZYNQ 1761 - set CONFIG_SYS_I2C_ZYNQ_SPEED for speed setting 1762 - set CONFIG_SYS_I2C_ZYNQ_SLAVE for slave addr 1763 1764 - drivers/i2c/s3c24x0_i2c.c: 1765 - activate this driver with CONFIG_SYS_I2C_S3C24X0 1766 - This driver adds i2c buses (11 for Exynos5250, Exynos5420 1767 9 i2c buses for Exynos4 and 1 for S3C24X0 SoCs from Samsung) 1768 with a fix speed from 100000 and the slave addr 0! 1769 1770 - drivers/i2c/ihs_i2c.c 1771 - activate this driver with CONFIG_SYS_I2C_IHS 1772 - CONFIG_SYS_I2C_IHS_CH0 activate hardware channel 0 1773 - CONFIG_SYS_I2C_IHS_SPEED_0 speed channel 0 1774 - CONFIG_SYS_I2C_IHS_SLAVE_0 slave addr channel 0 1775 - CONFIG_SYS_I2C_IHS_CH1 activate hardware channel 1 1776 - CONFIG_SYS_I2C_IHS_SPEED_1 speed channel 1 1777 - CONFIG_SYS_I2C_IHS_SLAVE_1 slave addr channel 1 1778 - CONFIG_SYS_I2C_IHS_CH2 activate hardware channel 2 1779 - CONFIG_SYS_I2C_IHS_SPEED_2 speed channel 2 1780 - CONFIG_SYS_I2C_IHS_SLAVE_2 slave addr channel 2 1781 - CONFIG_SYS_I2C_IHS_CH3 activate hardware channel 3 1782 - CONFIG_SYS_I2C_IHS_SPEED_3 speed channel 3 1783 - CONFIG_SYS_I2C_IHS_SLAVE_3 slave addr channel 3 1784 - activate dual channel with CONFIG_SYS_I2C_IHS_DUAL 1785 - CONFIG_SYS_I2C_IHS_SPEED_0_1 speed channel 0_1 1786 - CONFIG_SYS_I2C_IHS_SLAVE_0_1 slave addr channel 0_1 1787 - CONFIG_SYS_I2C_IHS_SPEED_1_1 speed channel 1_1 1788 - CONFIG_SYS_I2C_IHS_SLAVE_1_1 slave addr channel 1_1 1789 - CONFIG_SYS_I2C_IHS_SPEED_2_1 speed channel 2_1 1790 - CONFIG_SYS_I2C_IHS_SLAVE_2_1 slave addr channel 2_1 1791 - CONFIG_SYS_I2C_IHS_SPEED_3_1 speed channel 3_1 1792 - CONFIG_SYS_I2C_IHS_SLAVE_3_1 slave addr channel 3_1 1793 1794 additional defines: 1795 1796 CONFIG_SYS_NUM_I2C_BUSES 1797 Hold the number of i2c buses you want to use. 1798 1799 CONFIG_SYS_I2C_DIRECT_BUS 1800 define this, if you don't use i2c muxes on your hardware. 1801 if CONFIG_SYS_I2C_MAX_HOPS is not defined or == 0 you can 1802 omit this define. 1803 1804 CONFIG_SYS_I2C_MAX_HOPS 1805 define how many muxes are maximal consecutively connected 1806 on one i2c bus. If you not use i2c muxes, omit this 1807 define. 1808 1809 CONFIG_SYS_I2C_BUSES 1810 hold a list of buses you want to use, only used if 1811 CONFIG_SYS_I2C_DIRECT_BUS is not defined, for example 1812 a board with CONFIG_SYS_I2C_MAX_HOPS = 1 and 1813 CONFIG_SYS_NUM_I2C_BUSES = 9: 1814 1815 CONFIG_SYS_I2C_BUSES {{0, {I2C_NULL_HOP}}, \ 1816 {0, {{I2C_MUX_PCA9547, 0x70, 1}}}, \ 1817 {0, {{I2C_MUX_PCA9547, 0x70, 2}}}, \ 1818 {0, {{I2C_MUX_PCA9547, 0x70, 3}}}, \ 1819 {0, {{I2C_MUX_PCA9547, 0x70, 4}}}, \ 1820 {0, {{I2C_MUX_PCA9547, 0x70, 5}}}, \ 1821 {1, {I2C_NULL_HOP}}, \ 1822 {1, {{I2C_MUX_PCA9544, 0x72, 1}}}, \ 1823 {1, {{I2C_MUX_PCA9544, 0x72, 2}}}, \ 1824 } 1825 1826 which defines 1827 bus 0 on adapter 0 without a mux 1828 bus 1 on adapter 0 with a PCA9547 on address 0x70 port 1 1829 bus 2 on adapter 0 with a PCA9547 on address 0x70 port 2 1830 bus 3 on adapter 0 with a PCA9547 on address 0x70 port 3 1831 bus 4 on adapter 0 with a PCA9547 on address 0x70 port 4 1832 bus 5 on adapter 0 with a PCA9547 on address 0x70 port 5 1833 bus 6 on adapter 1 without a mux 1834 bus 7 on adapter 1 with a PCA9544 on address 0x72 port 1 1835 bus 8 on adapter 1 with a PCA9544 on address 0x72 port 2 1836 1837 If you do not have i2c muxes on your board, omit this define. 1838 1839- Legacy I2C Support: 1840 If you use the software i2c interface (CONFIG_SYS_I2C_SOFT) 1841 then the following macros need to be defined (examples are 1842 from include/configs/lwmon.h): 1843 1844 I2C_INIT 1845 1846 (Optional). Any commands necessary to enable the I2C 1847 controller or configure ports. 1848 1849 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL) 1850 1851 I2C_ACTIVE 1852 1853 The code necessary to make the I2C data line active 1854 (driven). If the data line is open collector, this 1855 define can be null. 1856 1857 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA) 1858 1859 I2C_TRISTATE 1860 1861 The code necessary to make the I2C data line tri-stated 1862 (inactive). If the data line is open collector, this 1863 define can be null. 1864 1865 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA) 1866 1867 I2C_READ 1868 1869 Code that returns true if the I2C data line is high, 1870 false if it is low. 1871 1872 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0) 1873 1874 I2C_SDA(bit) 1875 1876 If <bit> is true, sets the I2C data line high. If it 1877 is false, it clears it (low). 1878 1879 eg: #define I2C_SDA(bit) \ 1880 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \ 1881 else immr->im_cpm.cp_pbdat &= ~PB_SDA 1882 1883 I2C_SCL(bit) 1884 1885 If <bit> is true, sets the I2C clock line high. If it 1886 is false, it clears it (low). 1887 1888 eg: #define I2C_SCL(bit) \ 1889 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \ 1890 else immr->im_cpm.cp_pbdat &= ~PB_SCL 1891 1892 I2C_DELAY 1893 1894 This delay is invoked four times per clock cycle so this 1895 controls the rate of data transfer. The data rate thus 1896 is 1 / (I2C_DELAY * 4). Often defined to be something 1897 like: 1898 1899 #define I2C_DELAY udelay(2) 1900 1901 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA 1902 1903 If your arch supports the generic GPIO framework (asm/gpio.h), 1904 then you may alternatively define the two GPIOs that are to be 1905 used as SCL / SDA. Any of the previous I2C_xxx macros will 1906 have GPIO-based defaults assigned to them as appropriate. 1907 1908 You should define these to the GPIO value as given directly to 1909 the generic GPIO functions. 1910 1911 CONFIG_SYS_I2C_INIT_BOARD 1912 1913 When a board is reset during an i2c bus transfer 1914 chips might think that the current transfer is still 1915 in progress. On some boards it is possible to access 1916 the i2c SCLK line directly, either by using the 1917 processor pin as a GPIO or by having a second pin 1918 connected to the bus. If this option is defined a 1919 custom i2c_init_board() routine in boards/xxx/board.c 1920 is run early in the boot sequence. 1921 1922 CONFIG_I2C_MULTI_BUS 1923 1924 This option allows the use of multiple I2C buses, each of which 1925 must have a controller. At any point in time, only one bus is 1926 active. To switch to a different bus, use the 'i2c dev' command. 1927 Note that bus numbering is zero-based. 1928 1929 CONFIG_SYS_I2C_NOPROBES 1930 1931 This option specifies a list of I2C devices that will be skipped 1932 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS 1933 is set, specify a list of bus-device pairs. Otherwise, specify 1934 a 1D array of device addresses 1935 1936 e.g. 1937 #undef CONFIG_I2C_MULTI_BUS 1938 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68} 1939 1940 will skip addresses 0x50 and 0x68 on a board with one I2C bus 1941 1942 #define CONFIG_I2C_MULTI_BUS 1943 #define CONFIG_SYS_I2C_NOPROBES {{0,0x50},{0,0x68},{1,0x54}} 1944 1945 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1 1946 1947 CONFIG_SYS_SPD_BUS_NUM 1948 1949 If defined, then this indicates the I2C bus number for DDR SPD. 1950 If not defined, then U-Boot assumes that SPD is on I2C bus 0. 1951 1952 CONFIG_SYS_RTC_BUS_NUM 1953 1954 If defined, then this indicates the I2C bus number for the RTC. 1955 If not defined, then U-Boot assumes that RTC is on I2C bus 0. 1956 1957 CONFIG_SOFT_I2C_READ_REPEATED_START 1958 1959 defining this will force the i2c_read() function in 1960 the soft_i2c driver to perform an I2C repeated start 1961 between writing the address pointer and reading the 1962 data. If this define is omitted the default behaviour 1963 of doing a stop-start sequence will be used. Most I2C 1964 devices can use either method, but some require one or 1965 the other. 1966 1967- SPI Support: CONFIG_SPI 1968 1969 Enables SPI driver (so far only tested with 1970 SPI EEPROM, also an instance works with Crystal A/D and 1971 D/As on the SACSng board) 1972 1973 CONFIG_SOFT_SPI 1974 1975 Enables a software (bit-bang) SPI driver rather than 1976 using hardware support. This is a general purpose 1977 driver that only requires three general I/O port pins 1978 (two outputs, one input) to function. If this is 1979 defined, the board configuration must define several 1980 SPI configuration items (port pins to use, etc). For 1981 an example, see include/configs/sacsng.h. 1982 1983 CONFIG_HARD_SPI 1984 1985 Enables a hardware SPI driver for general-purpose reads 1986 and writes. As with CONFIG_SOFT_SPI, the board configuration 1987 must define a list of chip-select function pointers. 1988 Currently supported on some MPC8xxx processors. For an 1989 example, see include/configs/mpc8349emds.h. 1990 1991 CONFIG_SYS_SPI_MXC_WAIT 1992 Timeout for waiting until spi transfer completed. 1993 default: (CONFIG_SYS_HZ/100) /* 10 ms */ 1994 1995- FPGA Support: CONFIG_FPGA 1996 1997 Enables FPGA subsystem. 1998 1999 CONFIG_FPGA_<vendor> 2000 2001 Enables support for specific chip vendors. 2002 (ALTERA, XILINX) 2003 2004 CONFIG_FPGA_<family> 2005 2006 Enables support for FPGA family. 2007 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX) 2008 2009 CONFIG_FPGA_COUNT 2010 2011 Specify the number of FPGA devices to support. 2012 2013 CONFIG_SYS_FPGA_PROG_FEEDBACK 2014 2015 Enable printing of hash marks during FPGA configuration. 2016 2017 CONFIG_SYS_FPGA_CHECK_BUSY 2018 2019 Enable checks on FPGA configuration interface busy 2020 status by the configuration function. This option 2021 will require a board or device specific function to 2022 be written. 2023 2024 CONFIG_FPGA_DELAY 2025 2026 If defined, a function that provides delays in the FPGA 2027 configuration driver. 2028 2029 CONFIG_SYS_FPGA_CHECK_CTRLC 2030 Allow Control-C to interrupt FPGA configuration 2031 2032 CONFIG_SYS_FPGA_CHECK_ERROR 2033 2034 Check for configuration errors during FPGA bitfile 2035 loading. For example, abort during Virtex II 2036 configuration if the INIT_B line goes low (which 2037 indicated a CRC error). 2038 2039 CONFIG_SYS_FPGA_WAIT_INIT 2040 2041 Maximum time to wait for the INIT_B line to de-assert 2042 after PROB_B has been de-asserted during a Virtex II 2043 FPGA configuration sequence. The default time is 500 2044 ms. 2045 2046 CONFIG_SYS_FPGA_WAIT_BUSY 2047 2048 Maximum time to wait for BUSY to de-assert during 2049 Virtex II FPGA configuration. The default is 5 ms. 2050 2051 CONFIG_SYS_FPGA_WAIT_CONFIG 2052 2053 Time to wait after FPGA configuration. The default is 2054 200 ms. 2055 2056- Configuration Management: 2057 CONFIG_BUILD_TARGET 2058 2059 Some SoCs need special image types (e.g. U-Boot binary 2060 with a special header) as build targets. By defining 2061 CONFIG_BUILD_TARGET in the SoC / board header, this 2062 special image will be automatically built upon calling 2063 make / buildman. 2064 2065 CONFIG_IDENT_STRING 2066 2067 If defined, this string will be added to the U-Boot 2068 version information (U_BOOT_VERSION) 2069 2070- Vendor Parameter Protection: 2071 2072 U-Boot considers the values of the environment 2073 variables "serial#" (Board Serial Number) and 2074 "ethaddr" (Ethernet Address) to be parameters that 2075 are set once by the board vendor / manufacturer, and 2076 protects these variables from casual modification by 2077 the user. Once set, these variables are read-only, 2078 and write or delete attempts are rejected. You can 2079 change this behaviour: 2080 2081 If CONFIG_ENV_OVERWRITE is #defined in your config 2082 file, the write protection for vendor parameters is 2083 completely disabled. Anybody can change or delete 2084 these parameters. 2085 2086 Alternatively, if you define _both_ an ethaddr in the 2087 default env _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default 2088 Ethernet address is installed in the environment, 2089 which can be changed exactly ONCE by the user. [The 2090 serial# is unaffected by this, i. e. it remains 2091 read-only.] 2092 2093 The same can be accomplished in a more flexible way 2094 for any variable by configuring the type of access 2095 to allow for those variables in the ".flags" variable 2096 or define CONFIG_ENV_FLAGS_LIST_STATIC. 2097 2098- Protected RAM: 2099 CONFIG_PRAM 2100 2101 Define this variable to enable the reservation of 2102 "protected RAM", i. e. RAM which is not overwritten 2103 by U-Boot. Define CONFIG_PRAM to hold the number of 2104 kB you want to reserve for pRAM. You can overwrite 2105 this default value by defining an environment 2106 variable "pram" to the number of kB you want to 2107 reserve. Note that the board info structure will 2108 still show the full amount of RAM. If pRAM is 2109 reserved, a new environment variable "mem" will 2110 automatically be defined to hold the amount of 2111 remaining RAM in a form that can be passed as boot 2112 argument to Linux, for instance like that: 2113 2114 setenv bootargs ... mem=\${mem} 2115 saveenv 2116 2117 This way you can tell Linux not to use this memory, 2118 either, which results in a memory region that will 2119 not be affected by reboots. 2120 2121 *WARNING* If your board configuration uses automatic 2122 detection of the RAM size, you must make sure that 2123 this memory test is non-destructive. So far, the 2124 following board configurations are known to be 2125 "pRAM-clean": 2126 2127 IVMS8, IVML24, SPD8xx, 2128 HERMES, IP860, RPXlite, LWMON, 2129 FLAGADM 2130 2131- Access to physical memory region (> 4GB) 2132 Some basic support is provided for operations on memory not 2133 normally accessible to U-Boot - e.g. some architectures 2134 support access to more than 4GB of memory on 32-bit 2135 machines using physical address extension or similar. 2136 Define CONFIG_PHYSMEM to access this basic support, which 2137 currently only supports clearing the memory. 2138 2139- Error Recovery: 2140 CONFIG_NET_RETRY_COUNT 2141 2142 This variable defines the number of retries for 2143 network operations like ARP, RARP, TFTP, or BOOTP 2144 before giving up the operation. If not defined, a 2145 default value of 5 is used. 2146 2147 CONFIG_ARP_TIMEOUT 2148 2149 Timeout waiting for an ARP reply in milliseconds. 2150 2151 CONFIG_NFS_TIMEOUT 2152 2153 Timeout in milliseconds used in NFS protocol. 2154 If you encounter "ERROR: Cannot umount" in nfs command, 2155 try longer timeout such as 2156 #define CONFIG_NFS_TIMEOUT 10000UL 2157 2158- Command Interpreter: 2159 CONFIG_SYS_PROMPT_HUSH_PS2 2160 2161 This defines the secondary prompt string, which is 2162 printed when the command interpreter needs more input 2163 to complete a command. Usually "> ". 2164 2165 Note: 2166 2167 In the current implementation, the local variables 2168 space and global environment variables space are 2169 separated. Local variables are those you define by 2170 simply typing `name=value'. To access a local 2171 variable later on, you have write `$name' or 2172 `${name}'; to execute the contents of a variable 2173 directly type `$name' at the command prompt. 2174 2175 Global environment variables are those you use 2176 setenv/printenv to work with. To run a command stored 2177 in such a variable, you need to use the run command, 2178 and you must not use the '$' sign to access them. 2179 2180 To store commands and special characters in a 2181 variable, please use double quotation marks 2182 surrounding the whole text of the variable, instead 2183 of the backslashes before semicolons and special 2184 symbols. 2185 2186- Command Line Editing and History: 2187 CONFIG_CMDLINE_PS_SUPPORT 2188 2189 Enable support for changing the command prompt string 2190 at run-time. Only static string is supported so far. 2191 The string is obtained from environment variables PS1 2192 and PS2. 2193 2194- Default Environment: 2195 CONFIG_EXTRA_ENV_SETTINGS 2196 2197 Define this to contain any number of null terminated 2198 strings (variable = value pairs) that will be part of 2199 the default environment compiled into the boot image. 2200 2201 For example, place something like this in your 2202 board's config file: 2203 2204 #define CONFIG_EXTRA_ENV_SETTINGS \ 2205 "myvar1=value1\0" \ 2206 "myvar2=value2\0" 2207 2208 Warning: This method is based on knowledge about the 2209 internal format how the environment is stored by the 2210 U-Boot code. This is NOT an official, exported 2211 interface! Although it is unlikely that this format 2212 will change soon, there is no guarantee either. 2213 You better know what you are doing here. 2214 2215 Note: overly (ab)use of the default environment is 2216 discouraged. Make sure to check other ways to preset 2217 the environment like the "source" command or the 2218 boot command first. 2219 2220 CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG 2221 2222 Define this in order to add variables describing certain 2223 run-time determined information about the hardware to the 2224 environment. These will be named board_name, board_rev. 2225 2226 CONFIG_DELAY_ENVIRONMENT 2227 2228 Normally the environment is loaded when the board is 2229 initialised so that it is available to U-Boot. This inhibits 2230 that so that the environment is not available until 2231 explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL 2232 this is instead controlled by the value of 2233 /config/load-environment. 2234 2235- Serial Flash support 2236 Usage requires an initial 'sf probe' to define the serial 2237 flash parameters, followed by read/write/erase/update 2238 commands. 2239 2240 The following defaults may be provided by the platform 2241 to handle the common case when only a single serial 2242 flash is present on the system. 2243 2244 CONFIG_SF_DEFAULT_BUS Bus identifier 2245 CONFIG_SF_DEFAULT_CS Chip-select 2246 CONFIG_SF_DEFAULT_MODE (see include/spi.h) 2247 CONFIG_SF_DEFAULT_SPEED in Hz 2248 2249 2250- TFTP Fixed UDP Port: 2251 CONFIG_TFTP_PORT 2252 2253 If this is defined, the environment variable tftpsrcp 2254 is used to supply the TFTP UDP source port value. 2255 If tftpsrcp isn't defined, the normal pseudo-random port 2256 number generator is used. 2257 2258 Also, the environment variable tftpdstp is used to supply 2259 the TFTP UDP destination port value. If tftpdstp isn't 2260 defined, the normal port 69 is used. 2261 2262 The purpose for tftpsrcp is to allow a TFTP server to 2263 blindly start the TFTP transfer using the pre-configured 2264 target IP address and UDP port. This has the effect of 2265 "punching through" the (Windows XP) firewall, allowing 2266 the remainder of the TFTP transfer to proceed normally. 2267 A better solution is to properly configure the firewall, 2268 but sometimes that is not allowed. 2269 2270- bootcount support: 2271 CONFIG_AT91SAM9XE 2272 enable special bootcounter support on at91sam9xe based boards. 2273 2274- Show boot progress: 2275 CONFIG_SHOW_BOOT_PROGRESS 2276 2277 Defining this option allows to add some board- 2278 specific code (calling a user-provided function 2279 "show_boot_progress(int)") that enables you to show 2280 the system's boot progress on some display (for 2281 example, some LED's) on your board. At the moment, 2282 the following checkpoints are implemented: 2283 2284 2285Legacy uImage format: 2286 2287 Arg Where When 2288 1 common/cmd_bootm.c before attempting to boot an image 2289 -1 common/cmd_bootm.c Image header has bad magic number 2290 2 common/cmd_bootm.c Image header has correct magic number 2291 -2 common/cmd_bootm.c Image header has bad checksum 2292 3 common/cmd_bootm.c Image header has correct checksum 2293 -3 common/cmd_bootm.c Image data has bad checksum 2294 4 common/cmd_bootm.c Image data has correct checksum 2295 -4 common/cmd_bootm.c Image is for unsupported architecture 2296 5 common/cmd_bootm.c Architecture check OK 2297 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi) 2298 6 common/cmd_bootm.c Image Type check OK 2299 -6 common/cmd_bootm.c gunzip uncompression error 2300 -7 common/cmd_bootm.c Unimplemented compression type 2301 7 common/cmd_bootm.c Uncompression OK 2302 8 common/cmd_bootm.c No uncompress/copy overwrite error 2303 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX) 2304 2305 9 common/image.c Start initial ramdisk verification 2306 -10 common/image.c Ramdisk header has bad magic number 2307 -11 common/image.c Ramdisk header has bad checksum 2308 10 common/image.c Ramdisk header is OK 2309 -12 common/image.c Ramdisk data has bad checksum 2310 11 common/image.c Ramdisk data has correct checksum 2311 12 common/image.c Ramdisk verification complete, start loading 2312 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk) 2313 13 common/image.c Start multifile image verification 2314 14 common/image.c No initial ramdisk, no multifile, continue. 2315 2316 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS 2317 2318 -30 arch/powerpc/lib/board.c Fatal error, hang the system 2319 -31 post/post.c POST test failed, detected by post_output_backlog() 2320 -32 post/post.c POST test failed, detected by post_run_single() 2321 2322 34 common/cmd_doc.c before loading a Image from a DOC device 2323 -35 common/cmd_doc.c Bad usage of "doc" command 2324 35 common/cmd_doc.c correct usage of "doc" command 2325 -36 common/cmd_doc.c No boot device 2326 36 common/cmd_doc.c correct boot device 2327 -37 common/cmd_doc.c Unknown Chip ID on boot device 2328 37 common/cmd_doc.c correct chip ID found, device available 2329 -38 common/cmd_doc.c Read Error on boot device 2330 38 common/cmd_doc.c reading Image header from DOC device OK 2331 -39 common/cmd_doc.c Image header has bad magic number 2332 39 common/cmd_doc.c Image header has correct magic number 2333 -40 common/cmd_doc.c Error reading Image from DOC device 2334 40 common/cmd_doc.c Image header has correct magic number 2335 41 common/cmd_ide.c before loading a Image from a IDE device 2336 -42 common/cmd_ide.c Bad usage of "ide" command 2337 42 common/cmd_ide.c correct usage of "ide" command 2338 -43 common/cmd_ide.c No boot device 2339 43 common/cmd_ide.c boot device found 2340 -44 common/cmd_ide.c Device not available 2341 44 common/cmd_ide.c Device available 2342 -45 common/cmd_ide.c wrong partition selected 2343 45 common/cmd_ide.c partition selected 2344 -46 common/cmd_ide.c Unknown partition table 2345 46 common/cmd_ide.c valid partition table found 2346 -47 common/cmd_ide.c Invalid partition type 2347 47 common/cmd_ide.c correct partition type 2348 -48 common/cmd_ide.c Error reading Image Header on boot device 2349 48 common/cmd_ide.c reading Image Header from IDE device OK 2350 -49 common/cmd_ide.c Image header has bad magic number 2351 49 common/cmd_ide.c Image header has correct magic number 2352 -50 common/cmd_ide.c Image header has bad checksum 2353 50 common/cmd_ide.c Image header has correct checksum 2354 -51 common/cmd_ide.c Error reading Image from IDE device 2355 51 common/cmd_ide.c reading Image from IDE device OK 2356 52 common/cmd_nand.c before loading a Image from a NAND device 2357 -53 common/cmd_nand.c Bad usage of "nand" command 2358 53 common/cmd_nand.c correct usage of "nand" command 2359 -54 common/cmd_nand.c No boot device 2360 54 common/cmd_nand.c boot device found 2361 -55 common/cmd_nand.c Unknown Chip ID on boot device 2362 55 common/cmd_nand.c correct chip ID found, device available 2363 -56 common/cmd_nand.c Error reading Image Header on boot device 2364 56 common/cmd_nand.c reading Image Header from NAND device OK 2365 -57 common/cmd_nand.c Image header has bad magic number 2366 57 common/cmd_nand.c Image header has correct magic number 2367 -58 common/cmd_nand.c Error reading Image from NAND device 2368 58 common/cmd_nand.c reading Image from NAND device OK 2369 2370 -60 common/env_common.c Environment has a bad CRC, using default 2371 2372 64 net/eth.c starting with Ethernet configuration. 2373 -64 net/eth.c no Ethernet found. 2374 65 net/eth.c Ethernet found. 2375 2376 -80 common/cmd_net.c usage wrong 2377 80 common/cmd_net.c before calling net_loop() 2378 -81 common/cmd_net.c some error in net_loop() occurred 2379 81 common/cmd_net.c net_loop() back without error 2380 -82 common/cmd_net.c size == 0 (File with size 0 loaded) 2381 82 common/cmd_net.c trying automatic boot 2382 83 common/cmd_net.c running "source" command 2383 -83 common/cmd_net.c some error in automatic boot or "source" command 2384 84 common/cmd_net.c end without errors 2385 2386FIT uImage format: 2387 2388 Arg Where When 2389 100 common/cmd_bootm.c Kernel FIT Image has correct format 2390 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format 2391 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration 2392 -101 common/cmd_bootm.c Can't get configuration for kernel subimage 2393 102 common/cmd_bootm.c Kernel unit name specified 2394 -103 common/cmd_bootm.c Can't get kernel subimage node offset 2395 103 common/cmd_bootm.c Found configuration node 2396 104 common/cmd_bootm.c Got kernel subimage node offset 2397 -104 common/cmd_bootm.c Kernel subimage hash verification failed 2398 105 common/cmd_bootm.c Kernel subimage hash verification OK 2399 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture 2400 106 common/cmd_bootm.c Architecture check OK 2401 -106 common/cmd_bootm.c Kernel subimage has wrong type 2402 107 common/cmd_bootm.c Kernel subimage type OK 2403 -107 common/cmd_bootm.c Can't get kernel subimage data/size 2404 108 common/cmd_bootm.c Got kernel subimage data/size 2405 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT) 2406 -109 common/cmd_bootm.c Can't get kernel subimage type 2407 -110 common/cmd_bootm.c Can't get kernel subimage comp 2408 -111 common/cmd_bootm.c Can't get kernel subimage os 2409 -112 common/cmd_bootm.c Can't get kernel subimage load address 2410 -113 common/cmd_bootm.c Image uncompress/copy overwrite error 2411 2412 120 common/image.c Start initial ramdisk verification 2413 -120 common/image.c Ramdisk FIT image has incorrect format 2414 121 common/image.c Ramdisk FIT image has correct format 2415 122 common/image.c No ramdisk subimage unit name, using configuration 2416 -122 common/image.c Can't get configuration for ramdisk subimage 2417 123 common/image.c Ramdisk unit name specified 2418 -124 common/image.c Can't get ramdisk subimage node offset 2419 125 common/image.c Got ramdisk subimage node offset 2420 -125 common/image.c Ramdisk subimage hash verification failed 2421 126 common/image.c Ramdisk subimage hash verification OK 2422 -126 common/image.c Ramdisk subimage for unsupported architecture 2423 127 common/image.c Architecture check OK 2424 -127 common/image.c Can't get ramdisk subimage data/size 2425 128 common/image.c Got ramdisk subimage data/size 2426 129 common/image.c Can't get ramdisk load address 2427 -129 common/image.c Got ramdisk load address 2428 2429 -130 common/cmd_doc.c Incorrect FIT image format 2430 131 common/cmd_doc.c FIT image format OK 2431 2432 -140 common/cmd_ide.c Incorrect FIT image format 2433 141 common/cmd_ide.c FIT image format OK 2434 2435 -150 common/cmd_nand.c Incorrect FIT image format 2436 151 common/cmd_nand.c FIT image format OK 2437 2438- legacy image format: 2439 CONFIG_IMAGE_FORMAT_LEGACY 2440 enables the legacy image format support in U-Boot. 2441 2442 Default: 2443 enabled if CONFIG_FIT_SIGNATURE is not defined. 2444 2445 CONFIG_DISABLE_IMAGE_LEGACY 2446 disable the legacy image format 2447 2448 This define is introduced, as the legacy image format is 2449 enabled per default for backward compatibility. 2450 2451- Standalone program support: 2452 CONFIG_STANDALONE_LOAD_ADDR 2453 2454 This option defines a board specific value for the 2455 address where standalone program gets loaded, thus 2456 overwriting the architecture dependent default 2457 settings. 2458 2459- Frame Buffer Address: 2460 CONFIG_FB_ADDR 2461 2462 Define CONFIG_FB_ADDR if you want to use specific 2463 address for frame buffer. This is typically the case 2464 when using a graphics controller has separate video 2465 memory. U-Boot will then place the frame buffer at 2466 the given address instead of dynamically reserving it 2467 in system RAM by calling lcd_setmem(), which grabs 2468 the memory for the frame buffer depending on the 2469 configured panel size. 2470 2471 Please see board_init_f function. 2472 2473- Automatic software updates via TFTP server 2474 CONFIG_UPDATE_TFTP 2475 CONFIG_UPDATE_TFTP_CNT_MAX 2476 CONFIG_UPDATE_TFTP_MSEC_MAX 2477 2478 These options enable and control the auto-update feature; 2479 for a more detailed description refer to doc/README.update. 2480 2481- MTD Support (mtdparts command, UBI support) 2482 CONFIG_MTD_DEVICE 2483 2484 Adds the MTD device infrastructure from the Linux kernel. 2485 Needed for mtdparts command support. 2486 2487 CONFIG_MTD_PARTITIONS 2488 2489 Adds the MTD partitioning infrastructure from the Linux 2490 kernel. Needed for UBI support. 2491 2492- UBI support 2493 CONFIG_UBI_SILENCE_MSG 2494 2495 Make the verbose messages from UBI stop printing. This leaves 2496 warnings and errors enabled. 2497 2498 2499 CONFIG_MTD_UBI_WL_THRESHOLD 2500 This parameter defines the maximum difference between the highest 2501 erase counter value and the lowest erase counter value of eraseblocks 2502 of UBI devices. When this threshold is exceeded, UBI starts performing 2503 wear leveling by means of moving data from eraseblock with low erase 2504 counter to eraseblocks with high erase counter. 2505 2506 The default value should be OK for SLC NAND flashes, NOR flashes and 2507 other flashes which have eraseblock life-cycle 100000 or more. 2508 However, in case of MLC NAND flashes which typically have eraseblock 2509 life-cycle less than 10000, the threshold should be lessened (e.g., 2510 to 128 or 256, although it does not have to be power of 2). 2511 2512 default: 4096 2513 2514 CONFIG_MTD_UBI_BEB_LIMIT 2515 This option specifies the maximum bad physical eraseblocks UBI 2516 expects on the MTD device (per 1024 eraseblocks). If the 2517 underlying flash does not admit of bad eraseblocks (e.g. NOR 2518 flash), this value is ignored. 2519 2520 NAND datasheets often specify the minimum and maximum NVM 2521 (Number of Valid Blocks) for the flashes' endurance lifetime. 2522 The maximum expected bad eraseblocks per 1024 eraseblocks 2523 then can be calculated as "1024 * (1 - MinNVB / MaxNVB)", 2524 which gives 20 for most NANDs (MaxNVB is basically the total 2525 count of eraseblocks on the chip). 2526 2527 To put it differently, if this value is 20, UBI will try to 2528 reserve about 1.9% of physical eraseblocks for bad blocks 2529 handling. And that will be 1.9% of eraseblocks on the entire 2530 NAND chip, not just the MTD partition UBI attaches. This means 2531 that if you have, say, a NAND flash chip admits maximum 40 bad 2532 eraseblocks, and it is split on two MTD partitions of the same 2533 size, UBI will reserve 40 eraseblocks when attaching a 2534 partition. 2535 2536 default: 20 2537 2538 CONFIG_MTD_UBI_FASTMAP 2539 Fastmap is a mechanism which allows attaching an UBI device 2540 in nearly constant time. Instead of scanning the whole MTD device it 2541 only has to locate a checkpoint (called fastmap) on the device. 2542 The on-flash fastmap contains all information needed to attach 2543 the device. Using fastmap makes only sense on large devices where 2544 attaching by scanning takes long. UBI will not automatically install 2545 a fastmap on old images, but you can set the UBI parameter 2546 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT to 1 if you want so. Please note 2547 that fastmap-enabled images are still usable with UBI implementations 2548 without fastmap support. On typical flash devices the whole fastmap 2549 fits into one PEB. UBI will reserve PEBs to hold two fastmaps. 2550 2551 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT 2552 Set this parameter to enable fastmap automatically on images 2553 without a fastmap. 2554 default: 0 2555 2556 CONFIG_MTD_UBI_FM_DEBUG 2557 Enable UBI fastmap debug 2558 default: 0 2559 2560- UBIFS support 2561 CONFIG_UBIFS_SILENCE_MSG 2562 2563 Make the verbose messages from UBIFS stop printing. This leaves 2564 warnings and errors enabled. 2565 2566- SPL framework 2567 CONFIG_SPL 2568 Enable building of SPL globally. 2569 2570 CONFIG_SPL_LDSCRIPT 2571 LDSCRIPT for linking the SPL binary. 2572 2573 CONFIG_SPL_MAX_FOOTPRINT 2574 Maximum size in memory allocated to the SPL, BSS included. 2575 When defined, the linker checks that the actual memory 2576 used by SPL from _start to __bss_end does not exceed it. 2577 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE 2578 must not be both defined at the same time. 2579 2580 CONFIG_SPL_MAX_SIZE 2581 Maximum size of the SPL image (text, data, rodata, and 2582 linker lists sections), BSS excluded. 2583 When defined, the linker checks that the actual size does 2584 not exceed it. 2585 2586 CONFIG_SPL_TEXT_BASE 2587 TEXT_BASE for linking the SPL binary. 2588 2589 CONFIG_SPL_RELOC_TEXT_BASE 2590 Address to relocate to. If unspecified, this is equal to 2591 CONFIG_SPL_TEXT_BASE (i.e. no relocation is done). 2592 2593 CONFIG_SPL_BSS_START_ADDR 2594 Link address for the BSS within the SPL binary. 2595 2596 CONFIG_SPL_BSS_MAX_SIZE 2597 Maximum size in memory allocated to the SPL BSS. 2598 When defined, the linker checks that the actual memory used 2599 by SPL from __bss_start to __bss_end does not exceed it. 2600 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE 2601 must not be both defined at the same time. 2602 2603 CONFIG_SPL_STACK 2604 Adress of the start of the stack SPL will use 2605 2606 CONFIG_SPL_PANIC_ON_RAW_IMAGE 2607 When defined, SPL will panic() if the image it has 2608 loaded does not have a signature. 2609 Defining this is useful when code which loads images 2610 in SPL cannot guarantee that absolutely all read errors 2611 will be caught. 2612 An example is the LPC32XX MLC NAND driver, which will 2613 consider that a completely unreadable NAND block is bad, 2614 and thus should be skipped silently. 2615 2616 CONFIG_SPL_RELOC_STACK 2617 Adress of the start of the stack SPL will use after 2618 relocation. If unspecified, this is equal to 2619 CONFIG_SPL_STACK. 2620 2621 CONFIG_SYS_SPL_MALLOC_START 2622 Starting address of the malloc pool used in SPL. 2623 When this option is set the full malloc is used in SPL and 2624 it is set up by spl_init() and before that, the simple malloc() 2625 can be used if CONFIG_SYS_MALLOC_F is defined. 2626 2627 CONFIG_SYS_SPL_MALLOC_SIZE 2628 The size of the malloc pool used in SPL. 2629 2630 CONFIG_SPL_OS_BOOT 2631 Enable booting directly to an OS from SPL. 2632 See also: doc/README.falcon 2633 2634 CONFIG_SPL_DISPLAY_PRINT 2635 For ARM, enable an optional function to print more information 2636 about the running system. 2637 2638 CONFIG_SPL_INIT_MINIMAL 2639 Arch init code should be built for a very small image 2640 2641 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION 2642 Partition on the MMC to load U-Boot from when the MMC is being 2643 used in raw mode 2644 2645 CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR 2646 Sector to load kernel uImage from when MMC is being 2647 used in raw mode (for Falcon mode) 2648 2649 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR, 2650 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS 2651 Sector and number of sectors to load kernel argument 2652 parameters from when MMC is being used in raw mode 2653 (for falcon mode) 2654 2655 CONFIG_SYS_MMCSD_FS_BOOT_PARTITION 2656 Partition on the MMC to load U-Boot from when the MMC is being 2657 used in fs mode 2658 2659 CONFIG_SPL_FS_LOAD_PAYLOAD_NAME 2660 Filename to read to load U-Boot when reading from filesystem 2661 2662 CONFIG_SPL_FS_LOAD_KERNEL_NAME 2663 Filename to read to load kernel uImage when reading 2664 from filesystem (for Falcon mode) 2665 2666 CONFIG_SPL_FS_LOAD_ARGS_NAME 2667 Filename to read to load kernel argument parameters 2668 when reading from filesystem (for Falcon mode) 2669 2670 CONFIG_SPL_MPC83XX_WAIT_FOR_NAND 2671 Set this for NAND SPL on PPC mpc83xx targets, so that 2672 start.S waits for the rest of the SPL to load before 2673 continuing (the hardware starts execution after just 2674 loading the first page rather than the full 4K). 2675 2676 CONFIG_SPL_SKIP_RELOCATE 2677 Avoid SPL relocation 2678 2679 CONFIG_SPL_NAND_BASE 2680 Include nand_base.c in the SPL. Requires 2681 CONFIG_SPL_NAND_DRIVERS. 2682 2683 CONFIG_SPL_NAND_DRIVERS 2684 SPL uses normal NAND drivers, not minimal drivers. 2685 2686 CONFIG_SPL_NAND_ECC 2687 Include standard software ECC in the SPL 2688 2689 CONFIG_SPL_NAND_SIMPLE 2690 Support for NAND boot using simple NAND drivers that 2691 expose the cmd_ctrl() interface. 2692 2693 CONFIG_SPL_UBI 2694 Support for a lightweight UBI (fastmap) scanner and 2695 loader 2696 2697 CONFIG_SPL_NAND_RAW_ONLY 2698 Support to boot only raw u-boot.bin images. Use this only 2699 if you need to save space. 2700 2701 CONFIG_SPL_COMMON_INIT_DDR 2702 Set for common ddr init with serial presence detect in 2703 SPL binary. 2704 2705 CONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT, 2706 CONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE, 2707 CONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS, 2708 CONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE, 2709 CONFIG_SYS_NAND_ECCBYTES 2710 Defines the size and behavior of the NAND that SPL uses 2711 to read U-Boot 2712 2713 CONFIG_SPL_NAND_BOOT 2714 Add support NAND boot 2715 2716 CONFIG_SYS_NAND_U_BOOT_OFFS 2717 Location in NAND to read U-Boot from 2718 2719 CONFIG_SYS_NAND_U_BOOT_DST 2720 Location in memory to load U-Boot to 2721 2722 CONFIG_SYS_NAND_U_BOOT_SIZE 2723 Size of image to load 2724 2725 CONFIG_SYS_NAND_U_BOOT_START 2726 Entry point in loaded image to jump to 2727 2728 CONFIG_SYS_NAND_HW_ECC_OOBFIRST 2729 Define this if you need to first read the OOB and then the 2730 data. This is used, for example, on davinci platforms. 2731 2732 CONFIG_SPL_RAM_DEVICE 2733 Support for running image already present in ram, in SPL binary 2734 2735 CONFIG_SPL_PAD_TO 2736 Image offset to which the SPL should be padded before appending 2737 the SPL payload. By default, this is defined as 2738 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined. 2739 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL 2740 payload without any padding, or >= CONFIG_SPL_MAX_SIZE. 2741 2742 CONFIG_SPL_TARGET 2743 Final target image containing SPL and payload. Some SPLs 2744 use an arch-specific makefile fragment instead, for 2745 example if more than one image needs to be produced. 2746 2747 CONFIG_FIT_SPL_PRINT 2748 Printing information about a FIT image adds quite a bit of 2749 code to SPL. So this is normally disabled in SPL. Use this 2750 option to re-enable it. This will affect the output of the 2751 bootm command when booting a FIT image. 2752 2753- TPL framework 2754 CONFIG_TPL 2755 Enable building of TPL globally. 2756 2757 CONFIG_TPL_PAD_TO 2758 Image offset to which the TPL should be padded before appending 2759 the TPL payload. By default, this is defined as 2760 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined. 2761 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL 2762 payload without any padding, or >= CONFIG_SPL_MAX_SIZE. 2763 2764- Interrupt support (PPC): 2765 2766 There are common interrupt_init() and timer_interrupt() 2767 for all PPC archs. interrupt_init() calls interrupt_init_cpu() 2768 for CPU specific initialization. interrupt_init_cpu() 2769 should set decrementer_count to appropriate value. If 2770 CPU resets decrementer automatically after interrupt 2771 (ppc4xx) it should set decrementer_count to zero. 2772 timer_interrupt() calls timer_interrupt_cpu() for CPU 2773 specific handling. If board has watchdog / status_led 2774 / other_activity_monitor it works automatically from 2775 general timer_interrupt(). 2776 2777 2778Board initialization settings: 2779------------------------------ 2780 2781During Initialization u-boot calls a number of board specific functions 2782to allow the preparation of board specific prerequisites, e.g. pin setup 2783before drivers are initialized. To enable these callbacks the 2784following configuration macros have to be defined. Currently this is 2785architecture specific, so please check arch/your_architecture/lib/board.c 2786typically in board_init_f() and board_init_r(). 2787 2788- CONFIG_BOARD_EARLY_INIT_F: Call board_early_init_f() 2789- CONFIG_BOARD_EARLY_INIT_R: Call board_early_init_r() 2790- CONFIG_BOARD_LATE_INIT: Call board_late_init() 2791- CONFIG_BOARD_POSTCLK_INIT: Call board_postclk_init() 2792 2793Configuration Settings: 2794----------------------- 2795 2796- CONFIG_SYS_SUPPORT_64BIT_DATA: Defined automatically if compiled as 64-bit. 2797 Optionally it can be defined to support 64-bit memory commands. 2798 2799- CONFIG_SYS_LONGHELP: Defined when you want long help messages included; 2800 undefine this when you're short of memory. 2801 2802- CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default 2803 width of the commands listed in the 'help' command output. 2804 2805- CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to 2806 prompt for user input. 2807 2808- CONFIG_SYS_CBSIZE: Buffer size for input from the Console 2809 2810- CONFIG_SYS_PBSIZE: Buffer size for Console output 2811 2812- CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands 2813 2814- CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to 2815 the application (usually a Linux kernel) when it is 2816 booted 2817 2818- CONFIG_SYS_BAUDRATE_TABLE: 2819 List of legal baudrate settings for this board. 2820 2821- CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END: 2822 Begin and End addresses of the area used by the 2823 simple memory test. 2824 2825- CONFIG_SYS_ALT_MEMTEST: 2826 Enable an alternate, more extensive memory test. 2827 2828- CONFIG_SYS_MEMTEST_SCRATCH: 2829 Scratch address used by the alternate memory test 2830 You only need to set this if address zero isn't writeable 2831 2832- CONFIG_SYS_MEM_RESERVE_SECURE 2833 Only implemented for ARMv8 for now. 2834 If defined, the size of CONFIG_SYS_MEM_RESERVE_SECURE memory 2835 is substracted from total RAM and won't be reported to OS. 2836 This memory can be used as secure memory. A variable 2837 gd->arch.secure_ram is used to track the location. In systems 2838 the RAM base is not zero, or RAM is divided into banks, 2839 this variable needs to be recalcuated to get the address. 2840 2841- CONFIG_SYS_MEM_TOP_HIDE: 2842 If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header, 2843 this specified memory area will get subtracted from the top 2844 (end) of RAM and won't get "touched" at all by U-Boot. By 2845 fixing up gd->ram_size the Linux kernel should gets passed 2846 the now "corrected" memory size and won't touch it either. 2847 This should work for arch/ppc and arch/powerpc. Only Linux 2848 board ports in arch/powerpc with bootwrapper support that 2849 recalculate the memory size from the SDRAM controller setup 2850 will have to get fixed in Linux additionally. 2851 2852 This option can be used as a workaround for the 440EPx/GRx 2853 CHIP 11 errata where the last 256 bytes in SDRAM shouldn't 2854 be touched. 2855 2856 WARNING: Please make sure that this value is a multiple of 2857 the Linux page size (normally 4k). If this is not the case, 2858 then the end address of the Linux memory will be located at a 2859 non page size aligned address and this could cause major 2860 problems. 2861 2862- CONFIG_SYS_LOADS_BAUD_CHANGE: 2863 Enable temporary baudrate change while serial download 2864 2865- CONFIG_SYS_SDRAM_BASE: 2866 Physical start address of SDRAM. _Must_ be 0 here. 2867 2868- CONFIG_SYS_FLASH_BASE: 2869 Physical start address of Flash memory. 2870 2871- CONFIG_SYS_MONITOR_BASE: 2872 Physical start address of boot monitor code (set by 2873 make config files to be same as the text base address 2874 (CONFIG_SYS_TEXT_BASE) used when linking) - same as 2875 CONFIG_SYS_FLASH_BASE when booting from flash. 2876 2877- CONFIG_SYS_MONITOR_LEN: 2878 Size of memory reserved for monitor code, used to 2879 determine _at_compile_time_ (!) if the environment is 2880 embedded within the U-Boot image, or in a separate 2881 flash sector. 2882 2883- CONFIG_SYS_MALLOC_LEN: 2884 Size of DRAM reserved for malloc() use. 2885 2886- CONFIG_SYS_MALLOC_F_LEN 2887 Size of the malloc() pool for use before relocation. If 2888 this is defined, then a very simple malloc() implementation 2889 will become available before relocation. The address is just 2890 below the global data, and the stack is moved down to make 2891 space. 2892 2893 This feature allocates regions with increasing addresses 2894 within the region. calloc() is supported, but realloc() 2895 is not available. free() is supported but does nothing. 2896 The memory will be freed (or in fact just forgotten) when 2897 U-Boot relocates itself. 2898 2899- CONFIG_SYS_MALLOC_SIMPLE 2900 Provides a simple and small malloc() and calloc() for those 2901 boards which do not use the full malloc in SPL (which is 2902 enabled with CONFIG_SYS_SPL_MALLOC_START). 2903 2904- CONFIG_SYS_NONCACHED_MEMORY: 2905 Size of non-cached memory area. This area of memory will be 2906 typically located right below the malloc() area and mapped 2907 uncached in the MMU. This is useful for drivers that would 2908 otherwise require a lot of explicit cache maintenance. For 2909 some drivers it's also impossible to properly maintain the 2910 cache. For example if the regions that need to be flushed 2911 are not a multiple of the cache-line size, *and* padding 2912 cannot be allocated between the regions to align them (i.e. 2913 if the HW requires a contiguous array of regions, and the 2914 size of each region is not cache-aligned), then a flush of 2915 one region may result in overwriting data that hardware has 2916 written to another region in the same cache-line. This can 2917 happen for example in network drivers where descriptors for 2918 buffers are typically smaller than the CPU cache-line (e.g. 2919 16 bytes vs. 32 or 64 bytes). 2920 2921 Non-cached memory is only supported on 32-bit ARM at present. 2922 2923- CONFIG_SYS_BOOTM_LEN: 2924 Normally compressed uImages are limited to an 2925 uncompressed size of 8 MBytes. If this is not enough, 2926 you can define CONFIG_SYS_BOOTM_LEN in your board config file 2927 to adjust this setting to your needs. 2928 2929- CONFIG_SYS_BOOTMAPSZ: 2930 Maximum size of memory mapped by the startup code of 2931 the Linux kernel; all data that must be processed by 2932 the Linux kernel (bd_info, boot arguments, FDT blob if 2933 used) must be put below this limit, unless "bootm_low" 2934 environment variable is defined and non-zero. In such case 2935 all data for the Linux kernel must be between "bootm_low" 2936 and "bootm_low" + CONFIG_SYS_BOOTMAPSZ. The environment 2937 variable "bootm_mapsize" will override the value of 2938 CONFIG_SYS_BOOTMAPSZ. If CONFIG_SYS_BOOTMAPSZ is undefined, 2939 then the value in "bootm_size" will be used instead. 2940 2941- CONFIG_SYS_BOOT_RAMDISK_HIGH: 2942 Enable initrd_high functionality. If defined then the 2943 initrd_high feature is enabled and the bootm ramdisk subcommand 2944 is enabled. 2945 2946- CONFIG_SYS_BOOT_GET_CMDLINE: 2947 Enables allocating and saving kernel cmdline in space between 2948 "bootm_low" and "bootm_low" + BOOTMAPSZ. 2949 2950- CONFIG_SYS_BOOT_GET_KBD: 2951 Enables allocating and saving a kernel copy of the bd_info in 2952 space between "bootm_low" and "bootm_low" + BOOTMAPSZ. 2953 2954- CONFIG_SYS_MAX_FLASH_BANKS: 2955 Max number of Flash memory banks 2956 2957- CONFIG_SYS_MAX_FLASH_SECT: 2958 Max number of sectors on a Flash chip 2959 2960- CONFIG_SYS_FLASH_ERASE_TOUT: 2961 Timeout for Flash erase operations (in ms) 2962 2963- CONFIG_SYS_FLASH_WRITE_TOUT: 2964 Timeout for Flash write operations (in ms) 2965 2966- CONFIG_SYS_FLASH_LOCK_TOUT 2967 Timeout for Flash set sector lock bit operation (in ms) 2968 2969- CONFIG_SYS_FLASH_UNLOCK_TOUT 2970 Timeout for Flash clear lock bits operation (in ms) 2971 2972- CONFIG_SYS_FLASH_PROTECTION 2973 If defined, hardware flash sectors protection is used 2974 instead of U-Boot software protection. 2975 2976- CONFIG_SYS_DIRECT_FLASH_TFTP: 2977 2978 Enable TFTP transfers directly to flash memory; 2979 without this option such a download has to be 2980 performed in two steps: (1) download to RAM, and (2) 2981 copy from RAM to flash. 2982 2983 The two-step approach is usually more reliable, since 2984 you can check if the download worked before you erase 2985 the flash, but in some situations (when system RAM is 2986 too limited to allow for a temporary copy of the 2987 downloaded image) this option may be very useful. 2988 2989- CONFIG_SYS_FLASH_CFI: 2990 Define if the flash driver uses extra elements in the 2991 common flash structure for storing flash geometry. 2992 2993- CONFIG_FLASH_CFI_DRIVER 2994 This option also enables the building of the cfi_flash driver 2995 in the drivers directory 2996 2997- CONFIG_FLASH_CFI_MTD 2998 This option enables the building of the cfi_mtd driver 2999 in the drivers directory. The driver exports CFI flash 3000 to the MTD layer. 3001 3002- CONFIG_SYS_FLASH_USE_BUFFER_WRITE 3003 Use buffered writes to flash. 3004 3005- CONFIG_FLASH_SPANSION_S29WS_N 3006 s29ws-n MirrorBit flash has non-standard addresses for buffered 3007 write commands. 3008 3009- CONFIG_SYS_FLASH_QUIET_TEST 3010 If this option is defined, the common CFI flash doesn't 3011 print it's warning upon not recognized FLASH banks. This 3012 is useful, if some of the configured banks are only 3013 optionally available. 3014 3015- CONFIG_FLASH_SHOW_PROGRESS 3016 If defined (must be an integer), print out countdown 3017 digits and dots. Recommended value: 45 (9..1) for 80 3018 column displays, 15 (3..1) for 40 column displays. 3019 3020- CONFIG_FLASH_VERIFY 3021 If defined, the content of the flash (destination) is compared 3022 against the source after the write operation. An error message 3023 will be printed when the contents are not identical. 3024 Please note that this option is useless in nearly all cases, 3025 since such flash programming errors usually are detected earlier 3026 while unprotecting/erasing/programming. Please only enable 3027 this option if you really know what you are doing. 3028 3029- CONFIG_SYS_RX_ETH_BUFFER: 3030 Defines the number of Ethernet receive buffers. On some 3031 Ethernet controllers it is recommended to set this value 3032 to 8 or even higher (EEPRO100 or 405 EMAC), since all 3033 buffers can be full shortly after enabling the interface 3034 on high Ethernet traffic. 3035 Defaults to 4 if not defined. 3036 3037- CONFIG_ENV_MAX_ENTRIES 3038 3039 Maximum number of entries in the hash table that is used 3040 internally to store the environment settings. The default 3041 setting is supposed to be generous and should work in most 3042 cases. This setting can be used to tune behaviour; see 3043 lib/hashtable.c for details. 3044 3045- CONFIG_ENV_FLAGS_LIST_DEFAULT 3046- CONFIG_ENV_FLAGS_LIST_STATIC 3047 Enable validation of the values given to environment variables when 3048 calling env set. Variables can be restricted to only decimal, 3049 hexadecimal, or boolean. If CONFIG_CMD_NET is also defined, 3050 the variables can also be restricted to IP address or MAC address. 3051 3052 The format of the list is: 3053 type_attribute = [s|d|x|b|i|m] 3054 access_attribute = [a|r|o|c] 3055 attributes = type_attribute[access_attribute] 3056 entry = variable_name[:attributes] 3057 list = entry[,list] 3058 3059 The type attributes are: 3060 s - String (default) 3061 d - Decimal 3062 x - Hexadecimal 3063 b - Boolean ([1yYtT|0nNfF]) 3064 i - IP address 3065 m - MAC address 3066 3067 The access attributes are: 3068 a - Any (default) 3069 r - Read-only 3070 o - Write-once 3071 c - Change-default 3072 3073 - CONFIG_ENV_FLAGS_LIST_DEFAULT 3074 Define this to a list (string) to define the ".flags" 3075 environment variable in the default or embedded environment. 3076 3077 - CONFIG_ENV_FLAGS_LIST_STATIC 3078 Define this to a list (string) to define validation that 3079 should be done if an entry is not found in the ".flags" 3080 environment variable. To override a setting in the static 3081 list, simply add an entry for the same variable name to the 3082 ".flags" variable. 3083 3084 If CONFIG_REGEX is defined, the variable_name above is evaluated as a 3085 regular expression. This allows multiple variables to define the same 3086 flags without explicitly listing them for each variable. 3087 3088- CONFIG_ENV_ACCESS_IGNORE_FORCE 3089 If defined, don't allow the -f switch to env set override variable 3090 access flags. 3091 3092- CONFIG_USE_STDINT 3093 If stdint.h is available with your toolchain you can define this 3094 option to enable it. You can provide option 'USE_STDINT=1' when 3095 building U-Boot to enable this. 3096 3097The following definitions that deal with the placement and management 3098of environment data (variable area); in general, we support the 3099following configurations: 3100 3101- CONFIG_BUILD_ENVCRC: 3102 3103 Builds up envcrc with the target environment so that external utils 3104 may easily extract it and embed it in final U-Boot images. 3105 3106BE CAREFUL! The first access to the environment happens quite early 3107in U-Boot initialization (when we try to get the setting of for the 3108console baudrate). You *MUST* have mapped your NVRAM area then, or 3109U-Boot will hang. 3110 3111Please note that even with NVRAM we still use a copy of the 3112environment in RAM: we could work on NVRAM directly, but we want to 3113keep settings there always unmodified except somebody uses "saveenv" 3114to save the current settings. 3115 3116BE CAREFUL! For some special cases, the local device can not use 3117"saveenv" command. For example, the local device will get the 3118environment stored in a remote NOR flash by SRIO or PCIE link, 3119but it can not erase, write this NOR flash by SRIO or PCIE interface. 3120 3121- CONFIG_NAND_ENV_DST 3122 3123 Defines address in RAM to which the nand_spl code should copy the 3124 environment. If redundant environment is used, it will be copied to 3125 CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE. 3126 3127Please note that the environment is read-only until the monitor 3128has been relocated to RAM and a RAM copy of the environment has been 3129created; also, when using EEPROM you will have to use env_get_f() 3130until then to read environment variables. 3131 3132The environment is protected by a CRC32 checksum. Before the monitor 3133is relocated into RAM, as a result of a bad CRC you will be working 3134with the compiled-in default environment - *silently*!!! [This is 3135necessary, because the first environment variable we need is the 3136"baudrate" setting for the console - if we have a bad CRC, we don't 3137have any device yet where we could complain.] 3138 3139Note: once the monitor has been relocated, then it will complain if 3140the default environment is used; a new CRC is computed as soon as you 3141use the "saveenv" command to store a valid environment. 3142 3143- CONFIG_SYS_FAULT_ECHO_LINK_DOWN: 3144 Echo the inverted Ethernet link state to the fault LED. 3145 3146 Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR 3147 also needs to be defined. 3148 3149- CONFIG_SYS_FAULT_MII_ADDR: 3150 MII address of the PHY to check for the Ethernet link state. 3151 3152- CONFIG_NS16550_MIN_FUNCTIONS: 3153 Define this if you desire to only have use of the NS16550_init 3154 and NS16550_putc functions for the serial driver located at 3155 drivers/serial/ns16550.c. This option is useful for saving 3156 space for already greatly restricted images, including but not 3157 limited to NAND_SPL configurations. 3158 3159- CONFIG_DISPLAY_BOARDINFO 3160 Display information about the board that U-Boot is running on 3161 when U-Boot starts up. The board function checkboard() is called 3162 to do this. 3163 3164- CONFIG_DISPLAY_BOARDINFO_LATE 3165 Similar to the previous option, but display this information 3166 later, once stdio is running and output goes to the LCD, if 3167 present. 3168 3169- CONFIG_BOARD_SIZE_LIMIT: 3170 Maximum size of the U-Boot image. When defined, the 3171 build system checks that the actual size does not 3172 exceed it. 3173 3174Low Level (hardware related) configuration options: 3175--------------------------------------------------- 3176 3177- CONFIG_SYS_CACHELINE_SIZE: 3178 Cache Line Size of the CPU. 3179 3180- CONFIG_SYS_CCSRBAR_DEFAULT: 3181 Default (power-on reset) physical address of CCSR on Freescale 3182 PowerPC SOCs. 3183 3184- CONFIG_SYS_CCSRBAR: 3185 Virtual address of CCSR. On a 32-bit build, this is typically 3186 the same value as CONFIG_SYS_CCSRBAR_DEFAULT. 3187 3188- CONFIG_SYS_CCSRBAR_PHYS: 3189 Physical address of CCSR. CCSR can be relocated to a new 3190 physical address, if desired. In this case, this macro should 3191 be set to that address. Otherwise, it should be set to the 3192 same value as CONFIG_SYS_CCSRBAR_DEFAULT. For example, CCSR 3193 is typically relocated on 36-bit builds. It is recommended 3194 that this macro be defined via the _HIGH and _LOW macros: 3195 3196 #define CONFIG_SYS_CCSRBAR_PHYS ((CONFIG_SYS_CCSRBAR_PHYS_HIGH 3197 * 1ull) << 32 | CONFIG_SYS_CCSRBAR_PHYS_LOW) 3198 3199- CONFIG_SYS_CCSRBAR_PHYS_HIGH: 3200 Bits 33-36 of CONFIG_SYS_CCSRBAR_PHYS. This value is typically 3201 either 0 (32-bit build) or 0xF (36-bit build). This macro is 3202 used in assembly code, so it must not contain typecasts or 3203 integer size suffixes (e.g. "ULL"). 3204 3205- CONFIG_SYS_CCSRBAR_PHYS_LOW: 3206 Lower 32-bits of CONFIG_SYS_CCSRBAR_PHYS. This macro is 3207 used in assembly code, so it must not contain typecasts or 3208 integer size suffixes (e.g. "ULL"). 3209 3210- CONFIG_SYS_CCSR_DO_NOT_RELOCATE: 3211 If this macro is defined, then CONFIG_SYS_CCSRBAR_PHYS will be 3212 forced to a value that ensures that CCSR is not relocated. 3213 3214- Floppy Disk Support: 3215 CONFIG_SYS_FDC_DRIVE_NUMBER 3216 3217 the default drive number (default value 0) 3218 3219 CONFIG_SYS_ISA_IO_STRIDE 3220 3221 defines the spacing between FDC chipset registers 3222 (default value 1) 3223 3224 CONFIG_SYS_ISA_IO_OFFSET 3225 3226 defines the offset of register from address. It 3227 depends on which part of the data bus is connected to 3228 the FDC chipset. (default value 0) 3229 3230 If CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and 3231 CONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their 3232 default value. 3233 3234 if CONFIG_SYS_FDC_HW_INIT is defined, then the function 3235 fdc_hw_init() is called at the beginning of the FDC 3236 setup. fdc_hw_init() must be provided by the board 3237 source code. It is used to make hardware-dependent 3238 initializations. 3239 3240- CONFIG_IDE_AHB: 3241 Most IDE controllers were designed to be connected with PCI 3242 interface. Only few of them were designed for AHB interface. 3243 When software is doing ATA command and data transfer to 3244 IDE devices through IDE-AHB controller, some additional 3245 registers accessing to these kind of IDE-AHB controller 3246 is required. 3247 3248- CONFIG_SYS_IMMR: Physical address of the Internal Memory. 3249 DO NOT CHANGE unless you know exactly what you're 3250 doing! (11-4) [MPC8xx systems only] 3251 3252- CONFIG_SYS_INIT_RAM_ADDR: 3253 3254 Start address of memory area that can be used for 3255 initial data and stack; please note that this must be 3256 writable memory that is working WITHOUT special 3257 initialization, i. e. you CANNOT use normal RAM which 3258 will become available only after programming the 3259 memory controller and running certain initialization 3260 sequences. 3261 3262 U-Boot uses the following memory types: 3263 - MPC8xx: IMMR (internal memory of the CPU) 3264 3265- CONFIG_SYS_GBL_DATA_OFFSET: 3266 3267 Offset of the initial data structure in the memory 3268 area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually 3269 CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial 3270 data is located at the end of the available space 3271 (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE - 3272 GENERATED_GBL_DATA_SIZE), and the initial stack is just 3273 below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR + 3274 CONFIG_SYS_GBL_DATA_OFFSET) downward. 3275 3276 Note: 3277 On the MPC824X (or other systems that use the data 3278 cache for initial memory) the address chosen for 3279 CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must 3280 point to an otherwise UNUSED address space between 3281 the top of RAM and the start of the PCI space. 3282 3283- CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27) 3284 3285- CONFIG_SYS_OR_TIMING_SDRAM: 3286 SDRAM timing 3287 3288- CONFIG_SYS_MAMR_PTA: 3289 periodic timer for refresh 3290 3291- FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM, 3292 CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP, 3293 CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM, 3294 CONFIG_SYS_BR1_PRELIM: 3295 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH) 3296 3297- SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE, 3298 CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM, 3299 CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM: 3300 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM) 3301 3302- CONFIG_PCI_ENUM_ONLY 3303 Only scan through and get the devices on the buses. 3304 Don't do any setup work, presumably because someone or 3305 something has already done it, and we don't need to do it 3306 a second time. Useful for platforms that are pre-booted 3307 by coreboot or similar. 3308 3309- CONFIG_PCI_INDIRECT_BRIDGE: 3310 Enable support for indirect PCI bridges. 3311 3312- CONFIG_SYS_SRIO: 3313 Chip has SRIO or not 3314 3315- CONFIG_SRIO1: 3316 Board has SRIO 1 port available 3317 3318- CONFIG_SRIO2: 3319 Board has SRIO 2 port available 3320 3321- CONFIG_SRIO_PCIE_BOOT_MASTER 3322 Board can support master function for Boot from SRIO and PCIE 3323 3324- CONFIG_SYS_SRIOn_MEM_VIRT: 3325 Virtual Address of SRIO port 'n' memory region 3326 3327- CONFIG_SYS_SRIOn_MEM_PHYS: 3328 Physical Address of SRIO port 'n' memory region 3329 3330- CONFIG_SYS_SRIOn_MEM_SIZE: 3331 Size of SRIO port 'n' memory region 3332 3333- CONFIG_SYS_NAND_BUSWIDTH_16BIT 3334 Defined to tell the NAND controller that the NAND chip is using 3335 a 16 bit bus. 3336 Not all NAND drivers use this symbol. 3337 Example of drivers that use it: 3338 - drivers/mtd/nand/ndfc.c 3339 - drivers/mtd/nand/mxc_nand.c 3340 3341- CONFIG_SYS_NDFC_EBC0_CFG 3342 Sets the EBC0_CFG register for the NDFC. If not defined 3343 a default value will be used. 3344 3345- CONFIG_SPD_EEPROM 3346 Get DDR timing information from an I2C EEPROM. Common 3347 with pluggable memory modules such as SODIMMs 3348 3349 SPD_EEPROM_ADDRESS 3350 I2C address of the SPD EEPROM 3351 3352- CONFIG_SYS_SPD_BUS_NUM 3353 If SPD EEPROM is on an I2C bus other than the first 3354 one, specify here. Note that the value must resolve 3355 to something your driver can deal with. 3356 3357- CONFIG_SYS_DDR_RAW_TIMING 3358 Get DDR timing information from other than SPD. Common with 3359 soldered DDR chips onboard without SPD. DDR raw timing 3360 parameters are extracted from datasheet and hard-coded into 3361 header files or board specific files. 3362 3363- CONFIG_FSL_DDR_INTERACTIVE 3364 Enable interactive DDR debugging. See doc/README.fsl-ddr. 3365 3366- CONFIG_FSL_DDR_SYNC_REFRESH 3367 Enable sync of refresh for multiple controllers. 3368 3369- CONFIG_FSL_DDR_BIST 3370 Enable built-in memory test for Freescale DDR controllers. 3371 3372- CONFIG_SYS_83XX_DDR_USES_CS0 3373 Only for 83xx systems. If specified, then DDR should 3374 be configured using CS0 and CS1 instead of CS2 and CS3. 3375 3376- CONFIG_RMII 3377 Enable RMII mode for all FECs. 3378 Note that this is a global option, we can't 3379 have one FEC in standard MII mode and another in RMII mode. 3380 3381- CONFIG_CRC32_VERIFY 3382 Add a verify option to the crc32 command. 3383 The syntax is: 3384 3385 => crc32 -v <address> <count> <crc32> 3386 3387 Where address/count indicate a memory area 3388 and crc32 is the correct crc32 which the 3389 area should have. 3390 3391- CONFIG_LOOPW 3392 Add the "loopw" memory command. This only takes effect if 3393 the memory commands are activated globally (CONFIG_CMD_MEMORY). 3394 3395- CONFIG_MX_CYCLIC 3396 Add the "mdc" and "mwc" memory commands. These are cyclic 3397 "md/mw" commands. 3398 Examples: 3399 3400 => mdc.b 10 4 500 3401 This command will print 4 bytes (10,11,12,13) each 500 ms. 3402 3403 => mwc.l 100 12345678 10 3404 This command will write 12345678 to address 100 all 10 ms. 3405 3406 This only takes effect if the memory commands are activated 3407 globally (CONFIG_CMD_MEMORY). 3408 3409- CONFIG_SKIP_LOWLEVEL_INIT 3410 [ARM, NDS32, MIPS, RISC-V only] If this variable is defined, then certain 3411 low level initializations (like setting up the memory 3412 controller) are omitted and/or U-Boot does not 3413 relocate itself into RAM. 3414 3415 Normally this variable MUST NOT be defined. The only 3416 exception is when U-Boot is loaded (to RAM) by some 3417 other boot loader or by a debugger which performs 3418 these initializations itself. 3419 3420- CONFIG_SKIP_LOWLEVEL_INIT_ONLY 3421 [ARM926EJ-S only] This allows just the call to lowlevel_init() 3422 to be skipped. The normal CP15 init (such as enabling the 3423 instruction cache) is still performed. 3424 3425- CONFIG_SPL_BUILD 3426 Modifies the behaviour of start.S when compiling a loader 3427 that is executed before the actual U-Boot. E.g. when 3428 compiling a NAND SPL. 3429 3430- CONFIG_TPL_BUILD 3431 Modifies the behaviour of start.S when compiling a loader 3432 that is executed after the SPL and before the actual U-Boot. 3433 It is loaded by the SPL. 3434 3435- CONFIG_SYS_MPC85XX_NO_RESETVEC 3436 Only for 85xx systems. If this variable is specified, the section 3437 .resetvec is not kept and the section .bootpg is placed in the 3438 previous 4k of the .text section. 3439 3440- CONFIG_ARCH_MAP_SYSMEM 3441 Generally U-Boot (and in particular the md command) uses 3442 effective address. It is therefore not necessary to regard 3443 U-Boot address as virtual addresses that need to be translated 3444 to physical addresses. However, sandbox requires this, since 3445 it maintains its own little RAM buffer which contains all 3446 addressable memory. This option causes some memory accesses 3447 to be mapped through map_sysmem() / unmap_sysmem(). 3448 3449- CONFIG_X86_RESET_VECTOR 3450 If defined, the x86 reset vector code is included. This is not 3451 needed when U-Boot is running from Coreboot. 3452 3453- CONFIG_SPL_AM33XX_ENABLE_RTC32K_OSC: 3454 Enables the RTC32K OSC on AM33xx based plattforms 3455 3456- CONFIG_SYS_NAND_NO_SUBPAGE_WRITE 3457 Option to disable subpage write in NAND driver 3458 driver that uses this: 3459 drivers/mtd/nand/davinci_nand.c 3460 3461Freescale QE/FMAN Firmware Support: 3462----------------------------------- 3463 3464The Freescale QUICCEngine (QE) and Frame Manager (FMAN) both support the 3465loading of "firmware", which is encoded in the QE firmware binary format. 3466This firmware often needs to be loaded during U-Boot booting, so macros 3467are used to identify the storage device (NOR flash, SPI, etc) and the address 3468within that device. 3469 3470- CONFIG_SYS_FMAN_FW_ADDR 3471 The address in the storage device where the FMAN microcode is located. The 3472 meaning of this address depends on which CONFIG_SYS_QE_FW_IN_xxx macro 3473 is also specified. 3474 3475- CONFIG_SYS_QE_FW_ADDR 3476 The address in the storage device where the QE microcode is located. The 3477 meaning of this address depends on which CONFIG_SYS_QE_FW_IN_xxx macro 3478 is also specified. 3479 3480- CONFIG_SYS_QE_FMAN_FW_LENGTH 3481 The maximum possible size of the firmware. The firmware binary format 3482 has a field that specifies the actual size of the firmware, but it 3483 might not be possible to read any part of the firmware unless some 3484 local storage is allocated to hold the entire firmware first. 3485 3486- CONFIG_SYS_QE_FMAN_FW_IN_NOR 3487 Specifies that QE/FMAN firmware is located in NOR flash, mapped as 3488 normal addressable memory via the LBC. CONFIG_SYS_FMAN_FW_ADDR is the 3489 virtual address in NOR flash. 3490 3491- CONFIG_SYS_QE_FMAN_FW_IN_NAND 3492 Specifies that QE/FMAN firmware is located in NAND flash. 3493 CONFIG_SYS_FMAN_FW_ADDR is the offset within NAND flash. 3494 3495- CONFIG_SYS_QE_FMAN_FW_IN_MMC 3496 Specifies that QE/FMAN firmware is located on the primary SD/MMC 3497 device. CONFIG_SYS_FMAN_FW_ADDR is the byte offset on that device. 3498 3499- CONFIG_SYS_QE_FMAN_FW_IN_REMOTE 3500 Specifies that QE/FMAN firmware is located in the remote (master) 3501 memory space. CONFIG_SYS_FMAN_FW_ADDR is a virtual address which 3502 can be mapped from slave TLB->slave LAW->slave SRIO or PCIE outbound 3503 window->master inbound window->master LAW->the ucode address in 3504 master's memory space. 3505 3506Freescale Layerscape Management Complex Firmware Support: 3507--------------------------------------------------------- 3508The Freescale Layerscape Management Complex (MC) supports the loading of 3509"firmware". 3510This firmware often needs to be loaded during U-Boot booting, so macros 3511are used to identify the storage device (NOR flash, SPI, etc) and the address 3512within that device. 3513 3514- CONFIG_FSL_MC_ENET 3515 Enable the MC driver for Layerscape SoCs. 3516 3517Freescale Layerscape Debug Server Support: 3518------------------------------------------- 3519The Freescale Layerscape Debug Server Support supports the loading of 3520"Debug Server firmware" and triggering SP boot-rom. 3521This firmware often needs to be loaded during U-Boot booting. 3522 3523- CONFIG_SYS_MC_RSV_MEM_ALIGN 3524 Define alignment of reserved memory MC requires 3525 3526Reproducible builds 3527------------------- 3528 3529In order to achieve reproducible builds, timestamps used in the U-Boot build 3530process have to be set to a fixed value. 3531 3532This is done using the SOURCE_DATE_EPOCH environment variable. 3533SOURCE_DATE_EPOCH is to be set on the build host's shell, not as a configuration 3534option for U-Boot or an environment variable in U-Boot. 3535 3536SOURCE_DATE_EPOCH should be set to a number of seconds since the epoch, in UTC. 3537 3538Building the Software: 3539====================== 3540 3541Building U-Boot has been tested in several native build environments 3542and in many different cross environments. Of course we cannot support 3543all possibly existing versions of cross development tools in all 3544(potentially obsolete) versions. In case of tool chain problems we 3545recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK) 3546which is extensively used to build and test U-Boot. 3547 3548If you are not using a native environment, it is assumed that you 3549have GNU cross compiling tools available in your path. In this case, 3550you must set the environment variable CROSS_COMPILE in your shell. 3551Note that no changes to the Makefile or any other source files are 3552necessary. For example using the ELDK on a 4xx CPU, please enter: 3553 3554 $ CROSS_COMPILE=ppc_4xx- 3555 $ export CROSS_COMPILE 3556 3557Note: If you wish to generate Windows versions of the utilities in 3558 the tools directory you can use the MinGW toolchain 3559 (http://www.mingw.org). Set your HOST tools to the MinGW 3560 toolchain and execute 'make tools'. For example: 3561 3562 $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools 3563 3564 Binaries such as tools/mkimage.exe will be created which can 3565 be executed on computers running Windows. 3566 3567U-Boot is intended to be simple to build. After installing the 3568sources you must configure U-Boot for one specific board type. This 3569is done by typing: 3570 3571 make NAME_defconfig 3572 3573where "NAME_defconfig" is the name of one of the existing configu- 3574rations; see boards.cfg for supported names. 3575 3576Note: for some board special configuration names may exist; check if 3577 additional information is available from the board vendor; for 3578 instance, the TQM823L systems are available without (standard) 3579 or with LCD support. You can select such additional "features" 3580 when choosing the configuration, i. e. 3581 3582 make TQM823L_defconfig 3583 - will configure for a plain TQM823L, i. e. no LCD support 3584 3585 make TQM823L_LCD_defconfig 3586 - will configure for a TQM823L with U-Boot console on LCD 3587 3588 etc. 3589 3590 3591Finally, type "make all", and you should get some working U-Boot 3592images ready for download to / installation on your system: 3593 3594- "u-boot.bin" is a raw binary image 3595- "u-boot" is an image in ELF binary format 3596- "u-boot.srec" is in Motorola S-Record format 3597 3598By default the build is performed locally and the objects are saved 3599in the source directory. One of the two methods can be used to change 3600this behavior and build U-Boot to some external directory: 3601 36021. Add O= to the make command line invocations: 3603 3604 make O=/tmp/build distclean 3605 make O=/tmp/build NAME_defconfig 3606 make O=/tmp/build all 3607 36082. Set environment variable KBUILD_OUTPUT to point to the desired location: 3609 3610 export KBUILD_OUTPUT=/tmp/build 3611 make distclean 3612 make NAME_defconfig 3613 make all 3614 3615Note that the command line "O=" setting overrides the KBUILD_OUTPUT environment 3616variable. 3617 3618User specific CPPFLAGS, AFLAGS and CFLAGS can be passed to the compiler by 3619setting the according environment variables KCPPFLAGS, KAFLAGS and KCFLAGS. 3620For example to treat all compiler warnings as errors: 3621 3622 make KCFLAGS=-Werror 3623 3624Please be aware that the Makefiles assume you are using GNU make, so 3625for instance on NetBSD you might need to use "gmake" instead of 3626native "make". 3627 3628 3629If the system board that you have is not listed, then you will need 3630to port U-Boot to your hardware platform. To do this, follow these 3631steps: 3632 36331. Create a new directory to hold your board specific code. Add any 3634 files you need. In your board directory, you will need at least 3635 the "Makefile" and a "<board>.c". 36362. Create a new configuration file "include/configs/<board>.h" for 3637 your board. 36383. If you're porting U-Boot to a new CPU, then also create a new 3639 directory to hold your CPU specific code. Add any files you need. 36404. Run "make <board>_defconfig" with your new name. 36415. Type "make", and you should get a working "u-boot.srec" file 3642 to be installed on your target system. 36436. Debug and solve any problems that might arise. 3644 [Of course, this last step is much harder than it sounds.] 3645 3646 3647Testing of U-Boot Modifications, Ports to New Hardware, etc.: 3648============================================================== 3649 3650If you have modified U-Boot sources (for instance added a new board 3651or support for new devices, a new CPU, etc.) you are expected to 3652provide feedback to the other developers. The feedback normally takes 3653the form of a "patch", i. e. a context diff against a certain (latest 3654official or latest in the git repository) version of U-Boot sources. 3655 3656But before you submit such a patch, please verify that your modifi- 3657cation did not break existing code. At least make sure that *ALL* of 3658the supported boards compile WITHOUT ANY compiler warnings. To do so, 3659just run the buildman script (tools/buildman/buildman), which will 3660configure and build U-Boot for ALL supported system. Be warned, this 3661will take a while. Please see the buildman README, or run 'buildman -H' 3662for documentation. 3663 3664 3665See also "U-Boot Porting Guide" below. 3666 3667 3668Monitor Commands - Overview: 3669============================ 3670 3671go - start application at address 'addr' 3672run - run commands in an environment variable 3673bootm - boot application image from memory 3674bootp - boot image via network using BootP/TFTP protocol 3675bootz - boot zImage from memory 3676tftpboot- boot image via network using TFTP protocol 3677 and env variables "ipaddr" and "serverip" 3678 (and eventually "gatewayip") 3679tftpput - upload a file via network using TFTP protocol 3680rarpboot- boot image via network using RARP/TFTP protocol 3681diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd' 3682loads - load S-Record file over serial line 3683loadb - load binary file over serial line (kermit mode) 3684md - memory display 3685mm - memory modify (auto-incrementing) 3686nm - memory modify (constant address) 3687mw - memory write (fill) 3688cp - memory copy 3689cmp - memory compare 3690crc32 - checksum calculation 3691i2c - I2C sub-system 3692sspi - SPI utility commands 3693base - print or set address offset 3694printenv- print environment variables 3695setenv - set environment variables 3696saveenv - save environment variables to persistent storage 3697protect - enable or disable FLASH write protection 3698erase - erase FLASH memory 3699flinfo - print FLASH memory information 3700nand - NAND memory operations (see doc/README.nand) 3701bdinfo - print Board Info structure 3702iminfo - print header information for application image 3703coninfo - print console devices and informations 3704ide - IDE sub-system 3705loop - infinite loop on address range 3706loopw - infinite write loop on address range 3707mtest - simple RAM test 3708icache - enable or disable instruction cache 3709dcache - enable or disable data cache 3710reset - Perform RESET of the CPU 3711echo - echo args to console 3712version - print monitor version 3713help - print online help 3714? - alias for 'help' 3715 3716 3717Monitor Commands - Detailed Description: 3718======================================== 3719 3720TODO. 3721 3722For now: just type "help <command>". 3723 3724 3725Environment Variables: 3726====================== 3727 3728U-Boot supports user configuration using Environment Variables which 3729can be made persistent by saving to Flash memory. 3730 3731Environment Variables are set using "setenv", printed using 3732"printenv", and saved to Flash using "saveenv". Using "setenv" 3733without a value can be used to delete a variable from the 3734environment. As long as you don't save the environment you are 3735working with an in-memory copy. In case the Flash area containing the 3736environment is erased by accident, a default environment is provided. 3737 3738Some configuration options can be set using Environment Variables. 3739 3740List of environment variables (most likely not complete): 3741 3742 baudrate - see CONFIG_BAUDRATE 3743 3744 bootdelay - see CONFIG_BOOTDELAY 3745 3746 bootcmd - see CONFIG_BOOTCOMMAND 3747 3748 bootargs - Boot arguments when booting an RTOS image 3749 3750 bootfile - Name of the image to load with TFTP 3751 3752 bootm_low - Memory range available for image processing in the bootm 3753 command can be restricted. This variable is given as 3754 a hexadecimal number and defines lowest address allowed 3755 for use by the bootm command. See also "bootm_size" 3756 environment variable. Address defined by "bootm_low" is 3757 also the base of the initial memory mapping for the Linux 3758 kernel -- see the description of CONFIG_SYS_BOOTMAPSZ and 3759 bootm_mapsize. 3760 3761 bootm_mapsize - Size of the initial memory mapping for the Linux kernel. 3762 This variable is given as a hexadecimal number and it 3763 defines the size of the memory region starting at base 3764 address bootm_low that is accessible by the Linux kernel 3765 during early boot. If unset, CONFIG_SYS_BOOTMAPSZ is used 3766 as the default value if it is defined, and bootm_size is 3767 used otherwise. 3768 3769 bootm_size - Memory range available for image processing in the bootm 3770 command can be restricted. This variable is given as 3771 a hexadecimal number and defines the size of the region 3772 allowed for use by the bootm command. See also "bootm_low" 3773 environment variable. 3774 3775 updatefile - Location of the software update file on a TFTP server, used 3776 by the automatic software update feature. Please refer to 3777 documentation in doc/README.update for more details. 3778 3779 autoload - if set to "no" (any string beginning with 'n'), 3780 "bootp" will just load perform a lookup of the 3781 configuration from the BOOTP server, but not try to 3782 load any image using TFTP 3783 3784 autostart - if set to "yes", an image loaded using the "bootp", 3785 "rarpboot", "tftpboot" or "diskboot" commands will 3786 be automatically started (by internally calling 3787 "bootm") 3788 3789 If set to "no", a standalone image passed to the 3790 "bootm" command will be copied to the load address 3791 (and eventually uncompressed), but NOT be started. 3792 This can be used to load and uncompress arbitrary 3793 data. 3794 3795 fdt_high - if set this restricts the maximum address that the 3796 flattened device tree will be copied into upon boot. 3797 For example, if you have a system with 1 GB memory 3798 at physical address 0x10000000, while Linux kernel 3799 only recognizes the first 704 MB as low memory, you 3800 may need to set fdt_high as 0x3C000000 to have the 3801 device tree blob be copied to the maximum address 3802 of the 704 MB low memory, so that Linux kernel can 3803 access it during the boot procedure. 3804 3805 If this is set to the special value 0xFFFFFFFF then 3806 the fdt will not be copied at all on boot. For this 3807 to work it must reside in writable memory, have 3808 sufficient padding on the end of it for u-boot to 3809 add the information it needs into it, and the memory 3810 must be accessible by the kernel. 3811 3812 fdtcontroladdr- if set this is the address of the control flattened 3813 device tree used by U-Boot when CONFIG_OF_CONTROL is 3814 defined. 3815 3816 i2cfast - (PPC405GP|PPC405EP only) 3817 if set to 'y' configures Linux I2C driver for fast 3818 mode (400kHZ). This environment variable is used in 3819 initialization code. So, for changes to be effective 3820 it must be saved and board must be reset. 3821 3822 initrd_high - restrict positioning of initrd images: 3823 If this variable is not set, initrd images will be 3824 copied to the highest possible address in RAM; this 3825 is usually what you want since it allows for 3826 maximum initrd size. If for some reason you want to 3827 make sure that the initrd image is loaded below the 3828 CONFIG_SYS_BOOTMAPSZ limit, you can set this environment 3829 variable to a value of "no" or "off" or "0". 3830 Alternatively, you can set it to a maximum upper 3831 address to use (U-Boot will still check that it 3832 does not overwrite the U-Boot stack and data). 3833 3834 For instance, when you have a system with 16 MB 3835 RAM, and want to reserve 4 MB from use by Linux, 3836 you can do this by adding "mem=12M" to the value of 3837 the "bootargs" variable. However, now you must make 3838 sure that the initrd image is placed in the first 3839 12 MB as well - this can be done with 3840 3841 setenv initrd_high 00c00000 3842 3843 If you set initrd_high to 0xFFFFFFFF, this is an 3844 indication to U-Boot that all addresses are legal 3845 for the Linux kernel, including addresses in flash 3846 memory. In this case U-Boot will NOT COPY the 3847 ramdisk at all. This may be useful to reduce the 3848 boot time on your system, but requires that this 3849 feature is supported by your Linux kernel. 3850 3851 ipaddr - IP address; needed for tftpboot command 3852 3853 loadaddr - Default load address for commands like "bootp", 3854 "rarpboot", "tftpboot", "loadb" or "diskboot" 3855 3856 loads_echo - see CONFIG_LOADS_ECHO 3857 3858 serverip - TFTP server IP address; needed for tftpboot command 3859 3860 bootretry - see CONFIG_BOOT_RETRY_TIME 3861 3862 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR 3863 3864 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR 3865 3866 ethprime - controls which interface is used first. 3867 3868 ethact - controls which interface is currently active. 3869 For example you can do the following 3870 3871 => setenv ethact FEC 3872 => ping 192.168.0.1 # traffic sent on FEC 3873 => setenv ethact SCC 3874 => ping 10.0.0.1 # traffic sent on SCC 3875 3876 ethrotate - When set to "no" U-Boot does not go through all 3877 available network interfaces. 3878 It just stays at the currently selected interface. 3879 3880 netretry - When set to "no" each network operation will 3881 either succeed or fail without retrying. 3882 When set to "once" the network operation will 3883 fail when all the available network interfaces 3884 are tried once without success. 3885 Useful on scripts which control the retry operation 3886 themselves. 3887 3888 npe_ucode - set load address for the NPE microcode 3889 3890 silent_linux - If set then Linux will be told to boot silently, by 3891 changing the console to be empty. If "yes" it will be 3892 made silent. If "no" it will not be made silent. If 3893 unset, then it will be made silent if the U-Boot console 3894 is silent. 3895 3896 tftpsrcp - If this is set, the value is used for TFTP's 3897 UDP source port. 3898 3899 tftpdstp - If this is set, the value is used for TFTP's UDP 3900 destination port instead of the Well Know Port 69. 3901 3902 tftpblocksize - Block size to use for TFTP transfers; if not set, 3903 we use the TFTP server's default block size 3904 3905 tftptimeout - Retransmission timeout for TFTP packets (in milli- 3906 seconds, minimum value is 1000 = 1 second). Defines 3907 when a packet is considered to be lost so it has to 3908 be retransmitted. The default is 5000 = 5 seconds. 3909 Lowering this value may make downloads succeed 3910 faster in networks with high packet loss rates or 3911 with unreliable TFTP servers. 3912 3913 tftptimeoutcountmax - maximum count of TFTP timeouts (no 3914 unit, minimum value = 0). Defines how many timeouts 3915 can happen during a single file transfer before that 3916 transfer is aborted. The default is 10, and 0 means 3917 'no timeouts allowed'. Increasing this value may help 3918 downloads succeed with high packet loss rates, or with 3919 unreliable TFTP servers or client hardware. 3920 3921 vlan - When set to a value < 4095 the traffic over 3922 Ethernet is encapsulated/received over 802.1q 3923 VLAN tagged frames. 3924 3925 bootpretryperiod - Period during which BOOTP/DHCP sends retries. 3926 Unsigned value, in milliseconds. If not set, the period will 3927 be either the default (28000), or a value based on 3928 CONFIG_NET_RETRY_COUNT, if defined. This value has 3929 precedence over the valu based on CONFIG_NET_RETRY_COUNT. 3930 3931The following image location variables contain the location of images 3932used in booting. The "Image" column gives the role of the image and is 3933not an environment variable name. The other columns are environment 3934variable names. "File Name" gives the name of the file on a TFTP 3935server, "RAM Address" gives the location in RAM the image will be 3936loaded to, and "Flash Location" gives the image's address in NOR 3937flash or offset in NAND flash. 3938 3939*Note* - these variables don't have to be defined for all boards, some 3940boards currently use other variables for these purposes, and some 3941boards use these variables for other purposes. 3942 3943Image File Name RAM Address Flash Location 3944----- --------- ----------- -------------- 3945u-boot u-boot u-boot_addr_r u-boot_addr 3946Linux kernel bootfile kernel_addr_r kernel_addr 3947device tree blob fdtfile fdt_addr_r fdt_addr 3948ramdisk ramdiskfile ramdisk_addr_r ramdisk_addr 3949 3950The following environment variables may be used and automatically 3951updated by the network boot commands ("bootp" and "rarpboot"), 3952depending the information provided by your boot server: 3953 3954 bootfile - see above 3955 dnsip - IP address of your Domain Name Server 3956 dnsip2 - IP address of your secondary Domain Name Server 3957 gatewayip - IP address of the Gateway (Router) to use 3958 hostname - Target hostname 3959 ipaddr - see above 3960 netmask - Subnet Mask 3961 rootpath - Pathname of the root filesystem on the NFS server 3962 serverip - see above 3963 3964 3965There are two special Environment Variables: 3966 3967 serial# - contains hardware identification information such 3968 as type string and/or serial number 3969 ethaddr - Ethernet address 3970 3971These variables can be set only once (usually during manufacturing of 3972the board). U-Boot refuses to delete or overwrite these variables 3973once they have been set once. 3974 3975 3976Further special Environment Variables: 3977 3978 ver - Contains the U-Boot version string as printed 3979 with the "version" command. This variable is 3980 readonly (see CONFIG_VERSION_VARIABLE). 3981 3982 3983Please note that changes to some configuration parameters may take 3984only effect after the next boot (yes, that's just like Windoze :-). 3985 3986 3987Callback functions for environment variables: 3988--------------------------------------------- 3989 3990For some environment variables, the behavior of u-boot needs to change 3991when their values are changed. This functionality allows functions to 3992be associated with arbitrary variables. On creation, overwrite, or 3993deletion, the callback will provide the opportunity for some side 3994effect to happen or for the change to be rejected. 3995 3996The callbacks are named and associated with a function using the 3997U_BOOT_ENV_CALLBACK macro in your board or driver code. 3998 3999These callbacks are associated with variables in one of two ways. The 4000static list can be added to by defining CONFIG_ENV_CALLBACK_LIST_STATIC 4001in the board configuration to a string that defines a list of 4002associations. The list must be in the following format: 4003 4004 entry = variable_name[:callback_name] 4005 list = entry[,list] 4006 4007If the callback name is not specified, then the callback is deleted. 4008Spaces are also allowed anywhere in the list. 4009 4010Callbacks can also be associated by defining the ".callbacks" variable 4011with the same list format above. Any association in ".callbacks" will 4012override any association in the static list. You can define 4013CONFIG_ENV_CALLBACK_LIST_DEFAULT to a list (string) to define the 4014".callbacks" environment variable in the default or embedded environment. 4015 4016If CONFIG_REGEX is defined, the variable_name above is evaluated as a 4017regular expression. This allows multiple variables to be connected to 4018the same callback without explicitly listing them all out. 4019 4020 4021Command Line Parsing: 4022===================== 4023 4024There are two different command line parsers available with U-Boot: 4025the old "simple" one, and the much more powerful "hush" shell: 4026 4027Old, simple command line parser: 4028-------------------------------- 4029 4030- supports environment variables (through setenv / saveenv commands) 4031- several commands on one line, separated by ';' 4032- variable substitution using "... ${name} ..." syntax 4033- special characters ('$', ';') can be escaped by prefixing with '\', 4034 for example: 4035 setenv bootcmd bootm \${address} 4036- You can also escape text by enclosing in single apostrophes, for example: 4037 setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off' 4038 4039Hush shell: 4040----------- 4041 4042- similar to Bourne shell, with control structures like 4043 if...then...else...fi, for...do...done; while...do...done, 4044 until...do...done, ... 4045- supports environment ("global") variables (through setenv / saveenv 4046 commands) and local shell variables (through standard shell syntax 4047 "name=value"); only environment variables can be used with "run" 4048 command 4049 4050General rules: 4051-------------- 4052 4053(1) If a command line (or an environment variable executed by a "run" 4054 command) contains several commands separated by semicolon, and 4055 one of these commands fails, then the remaining commands will be 4056 executed anyway. 4057 4058(2) If you execute several variables with one call to run (i. e. 4059 calling run with a list of variables as arguments), any failing 4060 command will cause "run" to terminate, i. e. the remaining 4061 variables are not executed. 4062 4063Note for Redundant Ethernet Interfaces: 4064======================================= 4065 4066Some boards come with redundant Ethernet interfaces; U-Boot supports 4067such configurations and is capable of automatic selection of a 4068"working" interface when needed. MAC assignment works as follows: 4069 4070Network interfaces are numbered eth0, eth1, eth2, ... Corresponding 4071MAC addresses can be stored in the environment as "ethaddr" (=>eth0), 4072"eth1addr" (=>eth1), "eth2addr", ... 4073 4074If the network interface stores some valid MAC address (for instance 4075in SROM), this is used as default address if there is NO correspon- 4076ding setting in the environment; if the corresponding environment 4077variable is set, this overrides the settings in the card; that means: 4078 4079o If the SROM has a valid MAC address, and there is no address in the 4080 environment, the SROM's address is used. 4081 4082o If there is no valid address in the SROM, and a definition in the 4083 environment exists, then the value from the environment variable is 4084 used. 4085 4086o If both the SROM and the environment contain a MAC address, and 4087 both addresses are the same, this MAC address is used. 4088 4089o If both the SROM and the environment contain a MAC address, and the 4090 addresses differ, the value from the environment is used and a 4091 warning is printed. 4092 4093o If neither SROM nor the environment contain a MAC address, an error 4094 is raised. If CONFIG_NET_RANDOM_ETHADDR is defined, then in this case 4095 a random, locally-assigned MAC is used. 4096 4097If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses 4098will be programmed into hardware as part of the initialization process. This 4099may be skipped by setting the appropriate 'ethmacskip' environment variable. 4100The naming convention is as follows: 4101"ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc. 4102 4103Image Formats: 4104============== 4105 4106U-Boot is capable of booting (and performing other auxiliary operations on) 4107images in two formats: 4108 4109New uImage format (FIT) 4110----------------------- 4111 4112Flexible and powerful format based on Flattened Image Tree -- FIT (similar 4113to Flattened Device Tree). It allows the use of images with multiple 4114components (several kernels, ramdisks, etc.), with contents protected by 4115SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory. 4116 4117 4118Old uImage format 4119----------------- 4120 4121Old image format is based on binary files which can be basically anything, 4122preceded by a special header; see the definitions in include/image.h for 4123details; basically, the header defines the following image properties: 4124 4125* Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD, 4126 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks, 4127 LynxOS, pSOS, QNX, RTEMS, INTEGRITY; 4128 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS, 4129 INTEGRITY). 4130* Target CPU Architecture (Provisions for Alpha, ARM, Intel x86, 4131 IA64, MIPS, NDS32, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; 4132 Currently supported: ARM, Intel x86, MIPS, NDS32, Nios II, PowerPC). 4133* Compression Type (uncompressed, gzip, bzip2) 4134* Load Address 4135* Entry Point 4136* Image Name 4137* Image Timestamp 4138 4139The header is marked by a special Magic Number, and both the header 4140and the data portions of the image are secured against corruption by 4141CRC32 checksums. 4142 4143 4144Linux Support: 4145============== 4146 4147Although U-Boot should support any OS or standalone application 4148easily, the main focus has always been on Linux during the design of 4149U-Boot. 4150 4151U-Boot includes many features that so far have been part of some 4152special "boot loader" code within the Linux kernel. Also, any 4153"initrd" images to be used are no longer part of one big Linux image; 4154instead, kernel and "initrd" are separate images. This implementation 4155serves several purposes: 4156 4157- the same features can be used for other OS or standalone 4158 applications (for instance: using compressed images to reduce the 4159 Flash memory footprint) 4160 4161- it becomes much easier to port new Linux kernel versions because 4162 lots of low-level, hardware dependent stuff are done by U-Boot 4163 4164- the same Linux kernel image can now be used with different "initrd" 4165 images; of course this also means that different kernel images can 4166 be run with the same "initrd". This makes testing easier (you don't 4167 have to build a new "zImage.initrd" Linux image when you just 4168 change a file in your "initrd"). Also, a field-upgrade of the 4169 software is easier now. 4170 4171 4172Linux HOWTO: 4173============ 4174 4175Porting Linux to U-Boot based systems: 4176--------------------------------------- 4177 4178U-Boot cannot save you from doing all the necessary modifications to 4179configure the Linux device drivers for use with your target hardware 4180(no, we don't intend to provide a full virtual machine interface to 4181Linux :-). 4182 4183But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot). 4184 4185Just make sure your machine specific header file (for instance 4186include/asm-ppc/tqm8xx.h) includes the same definition of the Board 4187Information structure as we define in include/asm-<arch>/u-boot.h, 4188and make sure that your definition of IMAP_ADDR uses the same value 4189as your U-Boot configuration in CONFIG_SYS_IMMR. 4190 4191Note that U-Boot now has a driver model, a unified model for drivers. 4192If you are adding a new driver, plumb it into driver model. If there 4193is no uclass available, you are encouraged to create one. See 4194doc/driver-model. 4195 4196 4197Configuring the Linux kernel: 4198----------------------------- 4199 4200No specific requirements for U-Boot. Make sure you have some root 4201device (initial ramdisk, NFS) for your target system. 4202 4203 4204Building a Linux Image: 4205----------------------- 4206 4207With U-Boot, "normal" build targets like "zImage" or "bzImage" are 4208not used. If you use recent kernel source, a new build target 4209"uImage" will exist which automatically builds an image usable by 4210U-Boot. Most older kernels also have support for a "pImage" target, 4211which was introduced for our predecessor project PPCBoot and uses a 4212100% compatible format. 4213 4214Example: 4215 4216 make TQM850L_defconfig 4217 make oldconfig 4218 make dep 4219 make uImage 4220 4221The "uImage" build target uses a special tool (in 'tools/mkimage') to 4222encapsulate a compressed Linux kernel image with header information, 4223CRC32 checksum etc. for use with U-Boot. This is what we are doing: 4224 4225* build a standard "vmlinux" kernel image (in ELF binary format): 4226 4227* convert the kernel into a raw binary image: 4228 4229 ${CROSS_COMPILE}-objcopy -O binary \ 4230 -R .note -R .comment \ 4231 -S vmlinux linux.bin 4232 4233* compress the binary image: 4234 4235 gzip -9 linux.bin 4236 4237* package compressed binary image for U-Boot: 4238 4239 mkimage -A ppc -O linux -T kernel -C gzip \ 4240 -a 0 -e 0 -n "Linux Kernel Image" \ 4241 -d linux.bin.gz uImage 4242 4243 4244The "mkimage" tool can also be used to create ramdisk images for use 4245with U-Boot, either separated from the Linux kernel image, or 4246combined into one file. "mkimage" encapsulates the images with a 64 4247byte header containing information about target architecture, 4248operating system, image type, compression method, entry points, time 4249stamp, CRC32 checksums, etc. 4250 4251"mkimage" can be called in two ways: to verify existing images and 4252print the header information, or to build new images. 4253 4254In the first form (with "-l" option) mkimage lists the information 4255contained in the header of an existing U-Boot image; this includes 4256checksum verification: 4257 4258 tools/mkimage -l image 4259 -l ==> list image header information 4260 4261The second form (with "-d" option) is used to build a U-Boot image 4262from a "data file" which is used as image payload: 4263 4264 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \ 4265 -n name -d data_file image 4266 -A ==> set architecture to 'arch' 4267 -O ==> set operating system to 'os' 4268 -T ==> set image type to 'type' 4269 -C ==> set compression type 'comp' 4270 -a ==> set load address to 'addr' (hex) 4271 -e ==> set entry point to 'ep' (hex) 4272 -n ==> set image name to 'name' 4273 -d ==> use image data from 'datafile' 4274 4275Right now, all Linux kernels for PowerPC systems use the same load 4276address (0x00000000), but the entry point address depends on the 4277kernel version: 4278 4279- 2.2.x kernels have the entry point at 0x0000000C, 4280- 2.3.x and later kernels have the entry point at 0x00000000. 4281 4282So a typical call to build a U-Boot image would read: 4283 4284 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 4285 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \ 4286 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \ 4287 > examples/uImage.TQM850L 4288 Image Name: 2.4.4 kernel for TQM850L 4289 Created: Wed Jul 19 02:34:59 2000 4290 Image Type: PowerPC Linux Kernel Image (gzip compressed) 4291 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 4292 Load Address: 0x00000000 4293 Entry Point: 0x00000000 4294 4295To verify the contents of the image (or check for corruption): 4296 4297 -> tools/mkimage -l examples/uImage.TQM850L 4298 Image Name: 2.4.4 kernel for TQM850L 4299 Created: Wed Jul 19 02:34:59 2000 4300 Image Type: PowerPC Linux Kernel Image (gzip compressed) 4301 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 4302 Load Address: 0x00000000 4303 Entry Point: 0x00000000 4304 4305NOTE: for embedded systems where boot time is critical you can trade 4306speed for memory and install an UNCOMPRESSED image instead: this 4307needs more space in Flash, but boots much faster since it does not 4308need to be uncompressed: 4309 4310 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz 4311 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 4312 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \ 4313 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \ 4314 > examples/uImage.TQM850L-uncompressed 4315 Image Name: 2.4.4 kernel for TQM850L 4316 Created: Wed Jul 19 02:34:59 2000 4317 Image Type: PowerPC Linux Kernel Image (uncompressed) 4318 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB 4319 Load Address: 0x00000000 4320 Entry Point: 0x00000000 4321 4322 4323Similar you can build U-Boot images from a 'ramdisk.image.gz' file 4324when your kernel is intended to use an initial ramdisk: 4325 4326 -> tools/mkimage -n 'Simple Ramdisk Image' \ 4327 > -A ppc -O linux -T ramdisk -C gzip \ 4328 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd 4329 Image Name: Simple Ramdisk Image 4330 Created: Wed Jan 12 14:01:50 2000 4331 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 4332 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB 4333 Load Address: 0x00000000 4334 Entry Point: 0x00000000 4335 4336The "dumpimage" is a tool to disassemble images built by mkimage. Its "-i" 4337option performs the converse operation of the mkimage's second form (the "-d" 4338option). Given an image built by mkimage, the dumpimage extracts a "data file" 4339from the image: 4340 4341 tools/dumpimage -i image -T type -p position data_file 4342 -i ==> extract from the 'image' a specific 'data_file' 4343 -T ==> set image type to 'type' 4344 -p ==> 'position' (starting at 0) of the 'data_file' inside the 'image' 4345 4346 4347Installing a Linux Image: 4348------------------------- 4349 4350To downloading a U-Boot image over the serial (console) interface, 4351you must convert the image to S-Record format: 4352 4353 objcopy -I binary -O srec examples/image examples/image.srec 4354 4355The 'objcopy' does not understand the information in the U-Boot 4356image header, so the resulting S-Record file will be relative to 4357address 0x00000000. To load it to a given address, you need to 4358specify the target address as 'offset' parameter with the 'loads' 4359command. 4360 4361Example: install the image to address 0x40100000 (which on the 4362TQM8xxL is in the first Flash bank): 4363 4364 => erase 40100000 401FFFFF 4365 4366 .......... done 4367 Erased 8 sectors 4368 4369 => loads 40100000 4370 ## Ready for S-Record download ... 4371 ~>examples/image.srec 4372 1 2 3 4 5 6 7 8 9 10 11 12 13 ... 4373 ... 4374 15989 15990 15991 15992 4375 [file transfer complete] 4376 [connected] 4377 ## Start Addr = 0x00000000 4378 4379 4380You can check the success of the download using the 'iminfo' command; 4381this includes a checksum verification so you can be sure no data 4382corruption happened: 4383 4384 => imi 40100000 4385 4386 ## Checking Image at 40100000 ... 4387 Image Name: 2.2.13 for initrd on TQM850L 4388 Image Type: PowerPC Linux Kernel Image (gzip compressed) 4389 Data Size: 335725 Bytes = 327 kB = 0 MB 4390 Load Address: 00000000 4391 Entry Point: 0000000c 4392 Verifying Checksum ... OK 4393 4394 4395Boot Linux: 4396----------- 4397 4398The "bootm" command is used to boot an application that is stored in 4399memory (RAM or Flash). In case of a Linux kernel image, the contents 4400of the "bootargs" environment variable is passed to the kernel as 4401parameters. You can check and modify this variable using the 4402"printenv" and "setenv" commands: 4403 4404 4405 => printenv bootargs 4406 bootargs=root=/dev/ram 4407 4408 => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 4409 4410 => printenv bootargs 4411 bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 4412 4413 => bootm 40020000 4414 ## Booting Linux kernel at 40020000 ... 4415 Image Name: 2.2.13 for NFS on TQM850L 4416 Image Type: PowerPC Linux Kernel Image (gzip compressed) 4417 Data Size: 381681 Bytes = 372 kB = 0 MB 4418 Load Address: 00000000 4419 Entry Point: 0000000c 4420 Verifying Checksum ... OK 4421 Uncompressing Kernel Image ... OK 4422 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 4423 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 4424 time_init: decrementer frequency = 187500000/60 4425 Calibrating delay loop... 49.77 BogoMIPS 4426 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000] 4427 ... 4428 4429If you want to boot a Linux kernel with initial RAM disk, you pass 4430the memory addresses of both the kernel and the initrd image (PPBCOOT 4431format!) to the "bootm" command: 4432 4433 => imi 40100000 40200000 4434 4435 ## Checking Image at 40100000 ... 4436 Image Name: 2.2.13 for initrd on TQM850L 4437 Image Type: PowerPC Linux Kernel Image (gzip compressed) 4438 Data Size: 335725 Bytes = 327 kB = 0 MB 4439 Load Address: 00000000 4440 Entry Point: 0000000c 4441 Verifying Checksum ... OK 4442 4443 ## Checking Image at 40200000 ... 4444 Image Name: Simple Ramdisk Image 4445 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 4446 Data Size: 566530 Bytes = 553 kB = 0 MB 4447 Load Address: 00000000 4448 Entry Point: 00000000 4449 Verifying Checksum ... OK 4450 4451 => bootm 40100000 40200000 4452 ## Booting Linux kernel at 40100000 ... 4453 Image Name: 2.2.13 for initrd on TQM850L 4454 Image Type: PowerPC Linux Kernel Image (gzip compressed) 4455 Data Size: 335725 Bytes = 327 kB = 0 MB 4456 Load Address: 00000000 4457 Entry Point: 0000000c 4458 Verifying Checksum ... OK 4459 Uncompressing Kernel Image ... OK 4460 ## Loading RAMDisk Image at 40200000 ... 4461 Image Name: Simple Ramdisk Image 4462 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 4463 Data Size: 566530 Bytes = 553 kB = 0 MB 4464 Load Address: 00000000 4465 Entry Point: 00000000 4466 Verifying Checksum ... OK 4467 Loading Ramdisk ... OK 4468 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 4469 Boot arguments: root=/dev/ram 4470 time_init: decrementer frequency = 187500000/60 4471 Calibrating delay loop... 49.77 BogoMIPS 4472 ... 4473 RAMDISK: Compressed image found at block 0 4474 VFS: Mounted root (ext2 filesystem). 4475 4476 bash# 4477 4478Boot Linux and pass a flat device tree: 4479----------- 4480 4481First, U-Boot must be compiled with the appropriate defines. See the section 4482titled "Linux Kernel Interface" above for a more in depth explanation. The 4483following is an example of how to start a kernel and pass an updated 4484flat device tree: 4485 4486=> print oftaddr 4487oftaddr=0x300000 4488=> print oft 4489oft=oftrees/mpc8540ads.dtb 4490=> tftp $oftaddr $oft 4491Speed: 1000, full duplex 4492Using TSEC0 device 4493TFTP from server 192.168.1.1; our IP address is 192.168.1.101 4494Filename 'oftrees/mpc8540ads.dtb'. 4495Load address: 0x300000 4496Loading: # 4497done 4498Bytes transferred = 4106 (100a hex) 4499=> tftp $loadaddr $bootfile 4500Speed: 1000, full duplex 4501Using TSEC0 device 4502TFTP from server 192.168.1.1; our IP address is 192.168.1.2 4503Filename 'uImage'. 4504Load address: 0x200000 4505Loading:############ 4506done 4507Bytes transferred = 1029407 (fb51f hex) 4508=> print loadaddr 4509loadaddr=200000 4510=> print oftaddr 4511oftaddr=0x300000 4512=> bootm $loadaddr - $oftaddr 4513## Booting image at 00200000 ... 4514 Image Name: Linux-2.6.17-dirty 4515 Image Type: PowerPC Linux Kernel Image (gzip compressed) 4516 Data Size: 1029343 Bytes = 1005.2 kB 4517 Load Address: 00000000 4518 Entry Point: 00000000 4519 Verifying Checksum ... OK 4520 Uncompressing Kernel Image ... OK 4521Booting using flat device tree at 0x300000 4522Using MPC85xx ADS machine description 4523Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb 4524[snip] 4525 4526 4527More About U-Boot Image Types: 4528------------------------------ 4529 4530U-Boot supports the following image types: 4531 4532 "Standalone Programs" are directly runnable in the environment 4533 provided by U-Boot; it is expected that (if they behave 4534 well) you can continue to work in U-Boot after return from 4535 the Standalone Program. 4536 "OS Kernel Images" are usually images of some Embedded OS which 4537 will take over control completely. Usually these programs 4538 will install their own set of exception handlers, device 4539 drivers, set up the MMU, etc. - this means, that you cannot 4540 expect to re-enter U-Boot except by resetting the CPU. 4541 "RAMDisk Images" are more or less just data blocks, and their 4542 parameters (address, size) are passed to an OS kernel that is 4543 being started. 4544 "Multi-File Images" contain several images, typically an OS 4545 (Linux) kernel image and one or more data images like 4546 RAMDisks. This construct is useful for instance when you want 4547 to boot over the network using BOOTP etc., where the boot 4548 server provides just a single image file, but you want to get 4549 for instance an OS kernel and a RAMDisk image. 4550 4551 "Multi-File Images" start with a list of image sizes, each 4552 image size (in bytes) specified by an "uint32_t" in network 4553 byte order. This list is terminated by an "(uint32_t)0". 4554 Immediately after the terminating 0 follow the images, one by 4555 one, all aligned on "uint32_t" boundaries (size rounded up to 4556 a multiple of 4 bytes). 4557 4558 "Firmware Images" are binary images containing firmware (like 4559 U-Boot or FPGA images) which usually will be programmed to 4560 flash memory. 4561 4562 "Script files" are command sequences that will be executed by 4563 U-Boot's command interpreter; this feature is especially 4564 useful when you configure U-Boot to use a real shell (hush) 4565 as command interpreter. 4566 4567Booting the Linux zImage: 4568------------------------- 4569 4570On some platforms, it's possible to boot Linux zImage. This is done 4571using the "bootz" command. The syntax of "bootz" command is the same 4572as the syntax of "bootm" command. 4573 4574Note, defining the CONFIG_SUPPORT_RAW_INITRD allows user to supply 4575kernel with raw initrd images. The syntax is slightly different, the 4576address of the initrd must be augmented by it's size, in the following 4577format: "<initrd addres>:<initrd size>". 4578 4579 4580Standalone HOWTO: 4581================= 4582 4583One of the features of U-Boot is that you can dynamically load and 4584run "standalone" applications, which can use some resources of 4585U-Boot like console I/O functions or interrupt services. 4586 4587Two simple examples are included with the sources: 4588 4589"Hello World" Demo: 4590------------------- 4591 4592'examples/hello_world.c' contains a small "Hello World" Demo 4593application; it is automatically compiled when you build U-Boot. 4594It's configured to run at address 0x00040004, so you can play with it 4595like that: 4596 4597 => loads 4598 ## Ready for S-Record download ... 4599 ~>examples/hello_world.srec 4600 1 2 3 4 5 6 7 8 9 10 11 ... 4601 [file transfer complete] 4602 [connected] 4603 ## Start Addr = 0x00040004 4604 4605 => go 40004 Hello World! This is a test. 4606 ## Starting application at 0x00040004 ... 4607 Hello World 4608 argc = 7 4609 argv[0] = "40004" 4610 argv[1] = "Hello" 4611 argv[2] = "World!" 4612 argv[3] = "This" 4613 argv[4] = "is" 4614 argv[5] = "a" 4615 argv[6] = "test." 4616 argv[7] = "<NULL>" 4617 Hit any key to exit ... 4618 4619 ## Application terminated, rc = 0x0 4620 4621Another example, which demonstrates how to register a CPM interrupt 4622handler with the U-Boot code, can be found in 'examples/timer.c'. 4623Here, a CPM timer is set up to generate an interrupt every second. 4624The interrupt service routine is trivial, just printing a '.' 4625character, but this is just a demo program. The application can be 4626controlled by the following keys: 4627 4628 ? - print current values og the CPM Timer registers 4629 b - enable interrupts and start timer 4630 e - stop timer and disable interrupts 4631 q - quit application 4632 4633 => loads 4634 ## Ready for S-Record download ... 4635 ~>examples/timer.srec 4636 1 2 3 4 5 6 7 8 9 10 11 ... 4637 [file transfer complete] 4638 [connected] 4639 ## Start Addr = 0x00040004 4640 4641 => go 40004 4642 ## Starting application at 0x00040004 ... 4643 TIMERS=0xfff00980 4644 Using timer 1 4645 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0 4646 4647Hit 'b': 4648 [q, b, e, ?] Set interval 1000000 us 4649 Enabling timer 4650Hit '?': 4651 [q, b, e, ?] ........ 4652 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0 4653Hit '?': 4654 [q, b, e, ?] . 4655 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0 4656Hit '?': 4657 [q, b, e, ?] . 4658 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0 4659Hit '?': 4660 [q, b, e, ?] . 4661 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0 4662Hit 'e': 4663 [q, b, e, ?] ...Stopping timer 4664Hit 'q': 4665 [q, b, e, ?] ## Application terminated, rc = 0x0 4666 4667 4668Minicom warning: 4669================ 4670 4671Over time, many people have reported problems when trying to use the 4672"minicom" terminal emulation program for serial download. I (wd) 4673consider minicom to be broken, and recommend not to use it. Under 4674Unix, I recommend to use C-Kermit for general purpose use (and 4675especially for kermit binary protocol download ("loadb" command), and 4676use "cu" for S-Record download ("loads" command). See 4677http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3. 4678for help with kermit. 4679 4680 4681Nevertheless, if you absolutely want to use it try adding this 4682configuration to your "File transfer protocols" section: 4683 4684 Name Program Name U/D FullScr IO-Red. Multi 4685 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N 4686 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N 4687 4688 4689NetBSD Notes: 4690============= 4691 4692Starting at version 0.9.2, U-Boot supports NetBSD both as host 4693(build U-Boot) and target system (boots NetBSD/mpc8xx). 4694 4695Building requires a cross environment; it is known to work on 4696NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also 4697need gmake since the Makefiles are not compatible with BSD make). 4698Note that the cross-powerpc package does not install include files; 4699attempting to build U-Boot will fail because <machine/ansi.h> is 4700missing. This file has to be installed and patched manually: 4701 4702 # cd /usr/pkg/cross/powerpc-netbsd/include 4703 # mkdir powerpc 4704 # ln -s powerpc machine 4705 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h 4706 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST 4707 4708Native builds *don't* work due to incompatibilities between native 4709and U-Boot include files. 4710 4711Booting assumes that (the first part of) the image booted is a 4712stage-2 loader which in turn loads and then invokes the kernel 4713proper. Loader sources will eventually appear in the NetBSD source 4714tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the 4715meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz 4716 4717 4718Implementation Internals: 4719========================= 4720 4721The following is not intended to be a complete description of every 4722implementation detail. However, it should help to understand the 4723inner workings of U-Boot and make it easier to port it to custom 4724hardware. 4725 4726 4727Initial Stack, Global Data: 4728--------------------------- 4729 4730The implementation of U-Boot is complicated by the fact that U-Boot 4731starts running out of ROM (flash memory), usually without access to 4732system RAM (because the memory controller is not initialized yet). 4733This means that we don't have writable Data or BSS segments, and BSS 4734is not initialized as zero. To be able to get a C environment working 4735at all, we have to allocate at least a minimal stack. Implementation 4736options for this are defined and restricted by the CPU used: Some CPU 4737models provide on-chip memory (like the IMMR area on MPC8xx and 4738MPC826x processors), on others (parts of) the data cache can be 4739locked as (mis-) used as memory, etc. 4740 4741 Chris Hallinan posted a good summary of these issues to the 4742 U-Boot mailing list: 4743 4744 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)? 4745 From: "Chris Hallinan" <clh@net1plus.com> 4746 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET) 4747 ... 4748 4749 Correct me if I'm wrong, folks, but the way I understand it 4750 is this: Using DCACHE as initial RAM for Stack, etc, does not 4751 require any physical RAM backing up the cache. The cleverness 4752 is that the cache is being used as a temporary supply of 4753 necessary storage before the SDRAM controller is setup. It's 4754 beyond the scope of this list to explain the details, but you 4755 can see how this works by studying the cache architecture and 4756 operation in the architecture and processor-specific manuals. 4757 4758 OCM is On Chip Memory, which I believe the 405GP has 4K. It 4759 is another option for the system designer to use as an 4760 initial stack/RAM area prior to SDRAM being available. Either 4761 option should work for you. Using CS 4 should be fine if your 4762 board designers haven't used it for something that would 4763 cause you grief during the initial boot! It is frequently not 4764 used. 4765 4766 CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere 4767 with your processor/board/system design. The default value 4768 you will find in any recent u-boot distribution in 4769 walnut.h should work for you. I'd set it to a value larger 4770 than your SDRAM module. If you have a 64MB SDRAM module, set 4771 it above 400_0000. Just make sure your board has no resources 4772 that are supposed to respond to that address! That code in 4773 start.S has been around a while and should work as is when 4774 you get the config right. 4775 4776 -Chris Hallinan 4777 DS4.COM, Inc. 4778 4779It is essential to remember this, since it has some impact on the C 4780code for the initialization procedures: 4781 4782* Initialized global data (data segment) is read-only. Do not attempt 4783 to write it. 4784 4785* Do not use any uninitialized global data (or implicitly initialized 4786 as zero data - BSS segment) at all - this is undefined, initiali- 4787 zation is performed later (when relocating to RAM). 4788 4789* Stack space is very limited. Avoid big data buffers or things like 4790 that. 4791 4792Having only the stack as writable memory limits means we cannot use 4793normal global data to share information between the code. But it 4794turned out that the implementation of U-Boot can be greatly 4795simplified by making a global data structure (gd_t) available to all 4796functions. We could pass a pointer to this data as argument to _all_ 4797functions, but this would bloat the code. Instead we use a feature of 4798the GCC compiler (Global Register Variables) to share the data: we 4799place a pointer (gd) to the global data into a register which we 4800reserve for this purpose. 4801 4802When choosing a register for such a purpose we are restricted by the 4803relevant (E)ABI specifications for the current architecture, and by 4804GCC's implementation. 4805 4806For PowerPC, the following registers have specific use: 4807 R1: stack pointer 4808 R2: reserved for system use 4809 R3-R4: parameter passing and return values 4810 R5-R10: parameter passing 4811 R13: small data area pointer 4812 R30: GOT pointer 4813 R31: frame pointer 4814 4815 (U-Boot also uses R12 as internal GOT pointer. r12 4816 is a volatile register so r12 needs to be reset when 4817 going back and forth between asm and C) 4818 4819 ==> U-Boot will use R2 to hold a pointer to the global data 4820 4821 Note: on PPC, we could use a static initializer (since the 4822 address of the global data structure is known at compile time), 4823 but it turned out that reserving a register results in somewhat 4824 smaller code - although the code savings are not that big (on 4825 average for all boards 752 bytes for the whole U-Boot image, 4826 624 text + 127 data). 4827 4828On ARM, the following registers are used: 4829 4830 R0: function argument word/integer result 4831 R1-R3: function argument word 4832 R9: platform specific 4833 R10: stack limit (used only if stack checking is enabled) 4834 R11: argument (frame) pointer 4835 R12: temporary workspace 4836 R13: stack pointer 4837 R14: link register 4838 R15: program counter 4839 4840 ==> U-Boot will use R9 to hold a pointer to the global data 4841 4842 Note: on ARM, only R_ARM_RELATIVE relocations are supported. 4843 4844On Nios II, the ABI is documented here: 4845 http://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf 4846 4847 ==> U-Boot will use gp to hold a pointer to the global data 4848 4849 Note: on Nios II, we give "-G0" option to gcc and don't use gp 4850 to access small data sections, so gp is free. 4851 4852On NDS32, the following registers are used: 4853 4854 R0-R1: argument/return 4855 R2-R5: argument 4856 R15: temporary register for assembler 4857 R16: trampoline register 4858 R28: frame pointer (FP) 4859 R29: global pointer (GP) 4860 R30: link register (LP) 4861 R31: stack pointer (SP) 4862 PC: program counter (PC) 4863 4864 ==> U-Boot will use R10 to hold a pointer to the global data 4865 4866NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope, 4867or current versions of GCC may "optimize" the code too much. 4868 4869On RISC-V, the following registers are used: 4870 4871 x0: hard-wired zero (zero) 4872 x1: return address (ra) 4873 x2: stack pointer (sp) 4874 x3: global pointer (gp) 4875 x4: thread pointer (tp) 4876 x5: link register (t0) 4877 x8: frame pointer (fp) 4878 x10-x11: arguments/return values (a0-1) 4879 x12-x17: arguments (a2-7) 4880 x28-31: temporaries (t3-6) 4881 pc: program counter (pc) 4882 4883 ==> U-Boot will use gp to hold a pointer to the global data 4884 4885Memory Management: 4886------------------ 4887 4888U-Boot runs in system state and uses physical addresses, i.e. the 4889MMU is not used either for address mapping nor for memory protection. 4890 4891The available memory is mapped to fixed addresses using the memory 4892controller. In this process, a contiguous block is formed for each 4893memory type (Flash, SDRAM, SRAM), even when it consists of several 4894physical memory banks. 4895 4896U-Boot is installed in the first 128 kB of the first Flash bank (on 4897TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After 4898booting and sizing and initializing DRAM, the code relocates itself 4899to the upper end of DRAM. Immediately below the U-Boot code some 4900memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN 4901configuration setting]. Below that, a structure with global Board 4902Info data is placed, followed by the stack (growing downward). 4903 4904Additionally, some exception handler code is copied to the low 8 kB 4905of DRAM (0x00000000 ... 0x00001FFF). 4906 4907So a typical memory configuration with 16 MB of DRAM could look like 4908this: 4909 4910 0x0000 0000 Exception Vector code 4911 : 4912 0x0000 1FFF 4913 0x0000 2000 Free for Application Use 4914 : 4915 : 4916 4917 : 4918 : 4919 0x00FB FF20 Monitor Stack (Growing downward) 4920 0x00FB FFAC Board Info Data and permanent copy of global data 4921 0x00FC 0000 Malloc Arena 4922 : 4923 0x00FD FFFF 4924 0x00FE 0000 RAM Copy of Monitor Code 4925 ... eventually: LCD or video framebuffer 4926 ... eventually: pRAM (Protected RAM - unchanged by reset) 4927 0x00FF FFFF [End of RAM] 4928 4929 4930System Initialization: 4931---------------------- 4932 4933In the reset configuration, U-Boot starts at the reset entry point 4934(on most PowerPC systems at address 0x00000100). Because of the reset 4935configuration for CS0# this is a mirror of the on board Flash memory. 4936To be able to re-map memory U-Boot then jumps to its link address. 4937To be able to implement the initialization code in C, a (small!) 4938initial stack is set up in the internal Dual Ported RAM (in case CPUs 4939which provide such a feature like), or in a locked part of the data 4940cache. After that, U-Boot initializes the CPU core, the caches and 4941the SIU. 4942 4943Next, all (potentially) available memory banks are mapped using a 4944preliminary mapping. For example, we put them on 512 MB boundaries 4945(multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash 4946on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is 4947programmed for SDRAM access. Using the temporary configuration, a 4948simple memory test is run that determines the size of the SDRAM 4949banks. 4950 4951When there is more than one SDRAM bank, and the banks are of 4952different size, the largest is mapped first. For equal size, the first 4953bank (CS2#) is mapped first. The first mapping is always for address 49540x00000000, with any additional banks following immediately to create 4955contiguous memory starting from 0. 4956 4957Then, the monitor installs itself at the upper end of the SDRAM area 4958and allocates memory for use by malloc() and for the global Board 4959Info data; also, the exception vector code is copied to the low RAM 4960pages, and the final stack is set up. 4961 4962Only after this relocation will you have a "normal" C environment; 4963until that you are restricted in several ways, mostly because you are 4964running from ROM, and because the code will have to be relocated to a 4965new address in RAM. 4966 4967 4968U-Boot Porting Guide: 4969---------------------- 4970 4971[Based on messages by Jerry Van Baren in the U-Boot-Users mailing 4972list, October 2002] 4973 4974 4975int main(int argc, char *argv[]) 4976{ 4977 sighandler_t no_more_time; 4978 4979 signal(SIGALRM, no_more_time); 4980 alarm(PROJECT_DEADLINE - toSec (3 * WEEK)); 4981 4982 if (available_money > available_manpower) { 4983 Pay consultant to port U-Boot; 4984 return 0; 4985 } 4986 4987 Download latest U-Boot source; 4988 4989 Subscribe to u-boot mailing list; 4990 4991 if (clueless) 4992 email("Hi, I am new to U-Boot, how do I get started?"); 4993 4994 while (learning) { 4995 Read the README file in the top level directory; 4996 Read http://www.denx.de/twiki/bin/view/DULG/Manual; 4997 Read applicable doc/*.README; 4998 Read the source, Luke; 4999 /* find . -name "*.[chS]" | xargs grep -i <keyword> */ 5000 } 5001 5002 if (available_money > toLocalCurrency ($2500)) 5003 Buy a BDI3000; 5004 else 5005 Add a lot of aggravation and time; 5006 5007 if (a similar board exists) { /* hopefully... */ 5008 cp -a board/<similar> board/<myboard> 5009 cp include/configs/<similar>.h include/configs/<myboard>.h 5010 } else { 5011 Create your own board support subdirectory; 5012 Create your own board include/configs/<myboard>.h file; 5013 } 5014 Edit new board/<myboard> files 5015 Edit new include/configs/<myboard>.h 5016 5017 while (!accepted) { 5018 while (!running) { 5019 do { 5020 Add / modify source code; 5021 } until (compiles); 5022 Debug; 5023 if (clueless) 5024 email("Hi, I am having problems..."); 5025 } 5026 Send patch file to the U-Boot email list; 5027 if (reasonable critiques) 5028 Incorporate improvements from email list code review; 5029 else 5030 Defend code as written; 5031 } 5032 5033 return 0; 5034} 5035 5036void no_more_time (int sig) 5037{ 5038 hire_a_guru(); 5039} 5040 5041 5042Coding Standards: 5043----------------- 5044 5045All contributions to U-Boot should conform to the Linux kernel 5046coding style; see the kernel coding style guide at 5047https://www.kernel.org/doc/html/latest/process/coding-style.html, and the 5048script "scripts/Lindent" in your Linux kernel source directory. 5049 5050Source files originating from a different project (for example the 5051MTD subsystem) are generally exempt from these guidelines and are not 5052reformatted to ease subsequent migration to newer versions of those 5053sources. 5054 5055Please note that U-Boot is implemented in C (and to some small parts in 5056Assembler); no C++ is used, so please do not use C++ style comments (//) 5057in your code. 5058 5059Please also stick to the following formatting rules: 5060- remove any trailing white space 5061- use TAB characters for indentation and vertical alignment, not spaces 5062- make sure NOT to use DOS '\r\n' line feeds 5063- do not add more than 2 consecutive empty lines to source files 5064- do not add trailing empty lines to source files 5065 5066Submissions which do not conform to the standards may be returned 5067with a request to reformat the changes. 5068 5069 5070Submitting Patches: 5071------------------- 5072 5073Since the number of patches for U-Boot is growing, we need to 5074establish some rules. Submissions which do not conform to these rules 5075may be rejected, even when they contain important and valuable stuff. 5076 5077Please see http://www.denx.de/wiki/U-Boot/Patches for details. 5078 5079Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>; 5080see https://lists.denx.de/listinfo/u-boot 5081 5082When you send a patch, please include the following information with 5083it: 5084 5085* For bug fixes: a description of the bug and how your patch fixes 5086 this bug. Please try to include a way of demonstrating that the 5087 patch actually fixes something. 5088 5089* For new features: a description of the feature and your 5090 implementation. 5091 5092* A CHANGELOG entry as plaintext (separate from the patch) 5093 5094* For major contributions, add a MAINTAINERS file with your 5095 information and associated file and directory references. 5096 5097* When you add support for a new board, don't forget to add a 5098 maintainer e-mail address to the boards.cfg file, too. 5099 5100* If your patch adds new configuration options, don't forget to 5101 document these in the README file. 5102 5103* The patch itself. If you are using git (which is *strongly* 5104 recommended) you can easily generate the patch using the 5105 "git format-patch". If you then use "git send-email" to send it to 5106 the U-Boot mailing list, you will avoid most of the common problems 5107 with some other mail clients. 5108 5109 If you cannot use git, use "diff -purN OLD NEW". If your version of 5110 diff does not support these options, then get the latest version of 5111 GNU diff. 5112 5113 The current directory when running this command shall be the parent 5114 directory of the U-Boot source tree (i. e. please make sure that 5115 your patch includes sufficient directory information for the 5116 affected files). 5117 5118 We prefer patches as plain text. MIME attachments are discouraged, 5119 and compressed attachments must not be used. 5120 5121* If one logical set of modifications affects or creates several 5122 files, all these changes shall be submitted in a SINGLE patch file. 5123 5124* Changesets that contain different, unrelated modifications shall be 5125 submitted as SEPARATE patches, one patch per changeset. 5126 5127 5128Notes: 5129 5130* Before sending the patch, run the buildman script on your patched 5131 source tree and make sure that no errors or warnings are reported 5132 for any of the boards. 5133 5134* Keep your modifications to the necessary minimum: A patch 5135 containing several unrelated changes or arbitrary reformats will be 5136 returned with a request to re-formatting / split it. 5137 5138* If you modify existing code, make sure that your new code does not 5139 add to the memory footprint of the code ;-) Small is beautiful! 5140 When adding new features, these should compile conditionally only 5141 (using #ifdef), and the resulting code with the new feature 5142 disabled must not need more memory than the old code without your 5143 modification. 5144 5145* Remember that there is a size limit of 100 kB per message on the 5146 u-boot mailing list. Bigger patches will be moderated. If they are 5147 reasonable and not too big, they will be acknowledged. But patches 5148 bigger than the size limit should be avoided. 5149