4 bool "Boot timing and reporting"
6 Enable recording of boot time while booting. To use it, insert
7 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
8 bootstage.h. Only a single entry is recorded for each ID. You can
9 give the entry a name with bootstage_mark_name(). You can also
10 record elapsed time in a particular stage using bootstage_start()
11 before starting and bootstage_accum() when finished. Bootstage will
12 add up all the accumulated time and report it.
14 Normally, IDs are defined in bootstage.h but a small number of
15 additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
18 Calls to show_boot_progress() will also result in log entries but
19 these will not have names.
22 bool "Boot timing and reported in SPL"
25 Enable recording of boot time in SPL. To make this visible to U-Boot
26 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
27 information when SPL finishes and load it when U-Boot proper starts
30 config BOOTSTAGE_REPORT
31 bool "Display a detailed boot timing report before booting the OS"
34 Enable output of a boot time report just before the OS is booted.
35 This shows how long it took U-Boot to go through each stage of the
36 boot process. The report looks something like this:
38 Timer summary in microseconds:
41 3,575,678 3,575,678 board_init_f start
42 3,575,695 17 arch_cpu_init A9
43 3,575,777 82 arch_cpu_init done
44 3,659,598 83,821 board_init_r start
45 3,910,375 250,777 main_loop
46 29,916,167 26,005,792 bootm_start
47 30,361,327 445,160 start_kernel
49 config BOOTSTAGE_USER_COUNT
50 int "Number of boot ID numbers available for user use"
53 This is the number of available user bootstage records.
54 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
55 a new ID will be allocated from this stash. If you exceed
56 the limit, recording will stop.
58 config BOOTSTAGE_RECORD_COUNT
59 int "Number of boot stage records to store"
62 This is the size of the bootstage record list and is the maximum
63 number of bootstage records that can be recorded.
66 bool "Store boot timing information in the OS device tree"
69 Stash the bootstage information in the FDT. A root 'bootstage'
70 node is created with each bootstage id as a child. Each child
71 has a 'name' property and either 'mark' containing the
72 mark time in microseconds, or 'accum' containing the
73 accumulated time for that bootstage id in microseconds.
78 name = "board_init_f";
87 Code in the Linux kernel can find this in /proc/devicetree.
89 config BOOTSTAGE_STASH
90 bool "Stash the boot timing information in memory before booting OS"
93 Some OSes do not support device tree. Bootstage can instead write
94 the boot timing information in a binary format at a given address.
95 This happens through a call to bootstage_stash(), typically in
96 the CPU's cleanup_before_linux() function. You can use the
97 'bootstage stash' and 'bootstage unstash' commands to do this on
100 config BOOTSTAGE_STASH_ADDR
101 hex "Address to stash boot timing information"
104 Provide an address which will not be overwritten by the OS when it
105 starts, so that it can read this information when ready.
107 config BOOTSTAGE_STASH_SIZE
108 hex "Size of boot timing stash region"
111 This should be large enough to hold the bootstage stash. A value of
112 4096 (4KiB) is normally plenty.
119 bool "Support for booting from NOR flash"
122 Enabling this will make a U-Boot binary that is capable of being
123 booted via NOR. In this case we will enable certain pinmux early
124 as the ROM only partially sets up pinmux. We also default to using
128 bool "Support for booting from NAND flash"
131 Enabling this will make a U-Boot binary that is capable of being
132 booted via NAND flash. This is not a must, some SoCs need this,
136 bool "Support for booting from ONENAND"
139 Enabling this will make a U-Boot binary that is capable of being
140 booted via ONENAND. This is not a must, some SoCs need this,
144 bool "Support for booting from QSPI flash"
147 Enabling this will make a U-Boot binary that is capable of being
148 booted via QSPI flash. This is not a must, some SoCs need this,
152 bool "Support for booting from SATA"
155 Enabling this will make a U-Boot binary that is capable of being
156 booted via SATA. This is not a must, some SoCs need this,
160 bool "Support for booting from SD/EMMC"
163 Enabling this will make a U-Boot binary that is capable of being
164 booted via SD/EMMC. This is not a must, some SoCs need this,
168 bool "Support for booting from SPI flash"
171 Enabling this will make a U-Boot binary that is capable of being
172 booted via SPI flash. This is not a must, some SoCs need this,
179 config ENV_IS_IN_DATAFLASH
180 bool "Environment in dataflash"
181 depends on !CHAIN_OF_TRUST
183 Define this if you have a DataFlash memory device which you
184 want to use for the environment.
190 These three #defines specify the offset and size of the
191 environment area within the total memory of your DataFlash placed
192 at the specified address.
194 config ENV_IS_IN_EEPROM
195 bool "Environment in EEPROM"
196 depends on !CHAIN_OF_TRUST
198 Use this if you have an EEPROM or similar serial access
199 device and a driver for it.
204 These two #defines specify the offset and size of the
205 environment area within the total memory of your EEPROM.
207 - CONFIG_SYS_I2C_EEPROM_ADDR:
208 If defined, specified the chip address of the EEPROM device.
209 The default address is zero.
211 - CONFIG_SYS_I2C_EEPROM_BUS:
212 If defined, specified the i2c bus of the EEPROM device.
214 - CONFIG_SYS_EEPROM_PAGE_WRITE_BITS:
215 If defined, the number of bits used to address bytes in a
216 single page in the EEPROM device. A 64 byte page, for example
217 would require six bits.
219 - CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS:
220 If defined, the number of milliseconds to delay between
221 page writes. The default is zero milliseconds.
223 - CONFIG_SYS_I2C_EEPROM_ADDR_LEN:
224 The length in bytes of the EEPROM memory array address. Note
225 that this is NOT the chip address length!
227 - CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW:
228 EEPROM chips that implement "address overflow" are ones
229 like Catalyst 24WC04/08/16 which has 9/10/11 bits of
230 address and the extra bits end up in the "chip address" bit
231 slots. This makes a 24WC08 (1Kbyte) chip look like four 256
234 Note that we consider the length of the address field to
235 still be one byte because the extra address bits are hidden
238 - CONFIG_SYS_EEPROM_SIZE:
239 The size in bytes of the EEPROM device.
241 - CONFIG_ENV_EEPROM_IS_ON_I2C
242 define this, if you have I2C and SPI activated, and your
243 EEPROM, which holds the environment, is on the I2C bus.
245 - CONFIG_I2C_ENV_EEPROM_BUS
246 if you have an Environment on an EEPROM reached over
247 I2C muxes, you can define here, how to reach this
250 #define CONFIG_I2C_ENV_EEPROM_BUS 1
252 EEPROM which holds the environment, is reached over
253 a pca9547 i2c mux with address 0x70, channel 3.
255 config ENV_IS_IN_FLASH
256 bool "Environment in flash memory"
257 depends on !CHAIN_OF_TRUST
259 Define this if you have a flash device which you want to use for the
262 a) The environment occupies one whole flash sector, which is
263 "embedded" in the text segment with the U-Boot code. This
264 happens usually with "bottom boot sector" or "top boot
265 sector" type flash chips, which have several smaller
266 sectors at the start or the end. For instance, such a
267 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
268 such a case you would place the environment in one of the
269 4 kB sectors - with U-Boot code before and after it. With
270 "top boot sector" type flash chips, you would put the
271 environment in one of the last sectors, leaving a gap
272 between U-Boot and the environment.
276 Offset of environment data (variable area) to the
277 beginning of flash memory; for instance, with bottom boot
278 type flash chips the second sector can be used: the offset
279 for this sector is given here.
281 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
285 This is just another way to specify the start address of
286 the flash sector containing the environment (instead of
289 CONFIG_ENV_SECT_SIZE:
291 Size of the sector containing the environment.
294 b) Sometimes flash chips have few, equal sized, BIG sectors.
295 In such a case you don't want to spend a whole sector for
300 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
301 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
302 of this flash sector for the environment. This saves
303 memory for the RAM copy of the environment.
305 It may also save flash memory if you decide to use this
306 when your environment is "embedded" within U-Boot code,
307 since then the remainder of the flash sector could be used
308 for U-Boot code. It should be pointed out that this is
309 STRONGLY DISCOURAGED from a robustness point of view:
310 updating the environment in flash makes it always
311 necessary to erase the WHOLE sector. If something goes
312 wrong before the contents has been restored from a copy in
313 RAM, your target system will be dead.
315 CONFIG_ENV_ADDR_REDUND
316 CONFIG_ENV_SIZE_REDUND
318 These settings describe a second storage area used to hold
319 a redundant copy of the environment data, so that there is
320 a valid backup copy in case there is a power failure during
321 a "saveenv" operation.
323 BE CAREFUL! Any changes to the flash layout, and some changes to the
324 source code will make it necessary to adapt <board>/u-boot.lds*
328 bool "Environment in an MMC device"
329 depends on !CHAIN_OF_TRUST
330 default y if ARCH_SUNXI
332 Define this if you have an MMC device which you want to use for the
335 CONFIG_SYS_MMC_ENV_DEV:
337 Specifies which MMC device the environment is stored in.
339 CONFIG_SYS_MMC_ENV_PART (optional):
341 Specifies which MMC partition the environment is stored in. If not
342 set, defaults to partition 0, the user area. Common values might be
343 1 (first MMC boot partition), 2 (second MMC boot partition).
348 These two #defines specify the offset and size of the environment
349 area within the specified MMC device.
351 If offset is positive (the usual case), it is treated as relative to
352 the start of the MMC partition. If offset is negative, it is treated
353 as relative to the end of the MMC partition. This can be useful if
354 your board may be fitted with different MMC devices, which have
355 different sizes for the MMC partitions, and you always want the
356 environment placed at the very end of the partition, to leave the
357 maximum possible space before it, to store other data.
359 These two values are in units of bytes, but must be aligned to an
362 CONFIG_ENV_OFFSET_REDUND (optional):
364 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
365 hold a redundant copy of the environment data. This provides a
366 valid backup copy in case the other copy is corrupted, e.g. due
367 to a power failure during a "saveenv" operation.
369 This value may also be positive or negative; this is handled in the
370 same way as CONFIG_ENV_OFFSET.
372 This value is also in units of bytes, but must also be aligned to
373 an MMC sector boundary.
375 CONFIG_ENV_SIZE_REDUND (optional):
377 This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
378 set. If this value is set, it must be set to the same value as
381 config ENV_IS_IN_NAND
382 bool "Environment in a NAND device"
383 depends on !CHAIN_OF_TRUST
385 Define this if you have a NAND device which you want to use for the
391 These two #defines specify the offset and size of the environment
392 area within the first NAND device. CONFIG_ENV_OFFSET must be
393 aligned to an erase block boundary.
395 - CONFIG_ENV_OFFSET_REDUND (optional):
397 This setting describes a second storage area of CONFIG_ENV_SIZE
398 size used to hold a redundant copy of the environment data, so
399 that there is a valid backup copy in case there is a power failure
400 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
401 aligned to an erase block boundary.
403 - CONFIG_ENV_RANGE (optional):
405 Specifies the length of the region in which the environment
406 can be written. This should be a multiple of the NAND device's
407 block size. Specifying a range with more erase blocks than
408 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
409 the range to be avoided.
411 - CONFIG_ENV_OFFSET_OOB (optional):
413 Enables support for dynamically retrieving the offset of the
414 environment from block zero's out-of-band data. The
415 "nand env.oob" command can be used to record this offset.
416 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
417 using CONFIG_ENV_OFFSET_OOB.
419 config ENV_IS_IN_NVRAM
420 bool "Environment in a non-volatile RAM"
421 depends on !CHAIN_OF_TRUST
423 Define this if you have some non-volatile memory device
424 (NVRAM, battery buffered SRAM) which you want to use for the
430 These two #defines are used to determine the memory area you
431 want to use for environment. It is assumed that this memory
432 can just be read and written to, without any special
436 bool "Environment in a UBI volume"
437 depends on !CHAIN_OF_TRUST
439 Define this if you have an UBI volume that you want to use for the
440 environment. This has the benefit of wear-leveling the environment
441 accesses, which is important on NAND.
443 - CONFIG_ENV_UBI_PART:
445 Define this to a string that is the mtd partition containing the UBI.
447 - CONFIG_ENV_UBI_VOLUME:
449 Define this to the name of the volume that you want to store the
452 - CONFIG_ENV_UBI_VOLUME_REDUND:
454 Define this to the name of another volume to store a second copy of
455 the environment in. This will enable redundant environments in UBI.
456 It is assumed that both volumes are in the same MTD partition.
458 - CONFIG_UBI_SILENCE_MSG
459 - CONFIG_UBIFS_SILENCE_MSG
461 You will probably want to define these to avoid a really noisy system
462 when storing the env in UBI.
464 config ENV_IS_NOWHERE
465 bool "Environment is not stored"
467 Define this if you don't want to or can't have an environment stored
473 hex "Environment Offset"
474 depends on !ENV_IS_IN_UBI
475 depends on !ENV_IS_NOWHERE
476 default 0x88000 if ARCH_SUNXI
478 Offset from the start of the device (or partition)
481 hex "Environment Size"
482 depends on !ENV_IS_NOWHERE
483 default 0x20000 if ARCH_SUNXI
485 Size of the environment storage area
488 string "UBI partition name"
489 depends on ENV_IS_IN_UBI
491 MTD partition containing the UBI device
493 config ENV_UBI_VOLUME
494 string "UBI volume name"
495 depends on ENV_IS_IN_UBI
497 Name of the volume that you want to store the environment in.
504 int "delay in seconds before automatically booting"
508 Delay before automatically running bootcmd;
509 set to 0 to autoboot with no delay, but you can stop it by key input.
510 set to -1 to disable autoboot.
511 set to -2 to autoboot with no delay and not check for abort
513 See doc/README.autoboot for details.
520 This is the library functionality to provide a text-based menu of
521 choices for the user to make choices with.
523 config CONSOLE_RECORD
524 bool "Console recording"
526 This provides a way to record console output (and provide console
527 input) through circular buffers. This is mostly useful for testing.
528 Console output is recorded even when the console is silent.
529 To enable console recording, call console_record_reset_enable()
532 config CONSOLE_RECORD_OUT_SIZE
533 hex "Output buffer size"
534 depends on CONSOLE_RECORD
535 default 0x400 if CONSOLE_RECORD
537 Set the size of the console output buffer. When this fills up, no
538 more data will be recorded until some is removed. The buffer is
539 allocated immediately after the malloc() region is ready.
541 config CONSOLE_RECORD_IN_SIZE
542 hex "Input buffer size"
543 depends on CONSOLE_RECORD
544 default 0x100 if CONSOLE_RECORD
546 Set the size of the console input buffer. When this contains data,
547 tstc() and getc() will use this in preference to real device input.
548 The buffer is allocated immediately after the malloc() region is
552 string "Board specific string to be added to uboot version string"
554 This options adds the board specific name to u-boot version.
556 config SILENT_CONSOLE
557 bool "Support a silent console"
559 This option allows the console to be silenced, meaning that no
560 output will appear on the console devices. This is controlled by
561 setting the environment vaariable 'silent' to a non-empty value.
562 Note this also silences the console when booting Linux.
564 When the console is set up, the variable is checked, and the
565 GD_FLG_SILENT flag is set. Changing the environment variable later
566 will update the flag.
568 config SILENT_U_BOOT_ONLY
569 bool "Only silence the U-Boot console"
570 depends on SILENT_CONSOLE
572 Normally when the U-Boot console is silenced, Linux's console is
573 also silenced (assuming the board boots into Linux). This option
574 allows the linux console to operate normally, even if U-Boot's
577 config SILENT_CONSOLE_UPDATE_ON_SET
578 bool "Changes to the 'silent' environment variable update immediately"
579 depends on SILENT_CONSOLE
580 default y if SILENT_CONSOLE
582 When the 'silent' environment variable is changed, update the
583 console silence flag immediately. This allows 'setenv' to be used
584 to silence or un-silence the console.
586 The effect is that any change to the variable will affect the
589 config SILENT_CONSOLE_UPDATE_ON_RELOC
590 bool "Allow flags to take effect on relocation"
591 depends on SILENT_CONSOLE
593 In some cases the environment is not available until relocation
594 (e.g. NAND). This option makes the value of the 'silent'
595 environment variable take effect at relocation.
597 config PRE_CONSOLE_BUFFER
598 bool "Buffer characters before the console is available"
600 Prior to the console being initialised (i.e. serial UART
601 initialised etc) all console output is silently discarded.
602 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
603 buffer any console messages prior to the console being
604 initialised to a buffer. The buffer is a circular buffer, so
605 if it overflows, earlier output is discarded.
607 Note that this is not currently supported in SPL. It would be
608 useful to be able to share the pre-console buffer with SPL.
610 config PRE_CON_BUF_SZ
611 int "Sets the size of the pre-console buffer"
612 depends on PRE_CONSOLE_BUFFER
615 The size of the pre-console buffer affects how much console output
616 can be held before it overflows and starts discarding earlier
617 output. Normally there is very little output at this early stage,
618 unless debugging is enabled, so allow enough for ~10 lines of
621 This is a useful feature if you are using a video console and
622 want to see the full boot output on the console. Without this
623 option only the post-relocation output will be displayed.
625 config PRE_CON_BUF_ADDR
626 hex "Address of the pre-console buffer"
627 depends on PRE_CONSOLE_BUFFER
628 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
629 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
631 This sets the start address of the pre-console buffer. This must
632 be in available memory and is accessed before relocation and
633 possibly before DRAM is set up. Therefore choose an address
636 We should consider removing this option and allocating the memory
637 in board_init_f_init_reserve() instead.
640 bool "Enable console multiplexing"
641 default y if DM_VIDEO || VIDEO || LCD
643 This allows multiple devices to be used for each console 'file'.
644 For example, stdout can be set to go to serial and video.
645 Similarly, stdin can be set to come from serial and keyboard.
646 Input can be provided from either source. Console multiplexing
647 adds a small amount of size to U-Boot. Changes to the environment
648 variables stdout, stdin and stderr will take effect immediately.
650 config SYS_CONSOLE_IS_IN_ENV
651 bool "Select console devices from the environment"
652 default y if CONSOLE_MUX
654 This allows multiple input/output devices to be set at boot time.
655 For example, if stdout is set to "serial,video" then output will
656 be sent to both the serial and video devices on boot. The
657 environment variables can be updated after boot to change the
658 input/output devices.
660 config SYS_CONSOLE_OVERWRITE_ROUTINE
661 bool "Allow board control over console overwriting"
663 If this is enabled, and the board-specific function
664 overwrite_console() returns 1, the stdin, stderr and stdout are
665 switched to the serial port, else the settings in the environment
666 are used. If this is not enabled, the console will not be switched
669 config SYS_CONSOLE_ENV_OVERWRITE
670 bool "Update environment variables during console init"
672 The console environment variables (stdout, stdin, stderr) can be
673 used to determine the correct console devices on start-up. This
674 option writes the console devices to these variables on console
675 start-up (after relocation). This causes the environment to be
676 updated to match the console devices actually chosen.
678 config SYS_CONSOLE_INFO_QUIET
679 bool "Don't display the console devices on boot"
681 Normally U-Boot displays the current settings for stdout, stdin
682 and stderr on boot when the post-relocation console is set up.
683 Enable this option to supress this output. It can be obtained by
684 calling stdio_print_current_devices() from board code.
686 config SYS_STDIO_DEREGISTER
687 bool "Allow deregistering stdio devices"
688 default y if USB_KEYBOARD
690 Generally there is no need to deregister stdio devices since they
691 are never deactivated. But if a stdio device is used which can be
692 removed (for example a USB keyboard) then this option can be
693 enabled to ensure this is handled correctly.
698 bool "Support swapping dtbs at a later point in boot"
701 It is possible during initial boot you may need to use a generic
702 dtb until you can fully determine the board your running on. This
703 config allows boards to implement a function at a later point
704 during boot to switch to the "correct" dtb.
707 bool "Support a FIT image embedded in the U-boot image"
709 This option provides hooks to allow U-boot to parse an
710 appended FIT image and enable board specific code to then select
711 the correct DTB to be used.
713 config DEFAULT_FDT_FILE
714 string "Default fdt file"
716 This option is used to set the default fdt file to boot OS.
718 config VERSION_VARIABLE
719 bool "add U-Boot environment variable vers"
722 If this variable is defined, an environment variable
723 named "ver" is created by U-Boot showing the U-Boot
724 version as printed by the "version" command.
725 Any change to this variable will be reverted at the
728 config BOARD_LATE_INIT
731 Sometimes board require some initialization code that might
732 require once the actual init done, example saving board specific env,
733 boot-modes etc. which eventually done at late.
735 So this config enable the late init code with the help of board_late_init
736 function which should defined on respective boards.
738 config DISPLAY_CPUINFO
739 bool "Display information about the CPU during start up"
740 default y if ARM || NIOS2 || X86 || XTENSA
742 Display information about the CPU that U-Boot is running on
743 when U-Boot starts up. The function print_cpuinfo() is called
746 config DISPLAY_BOARDINFO
747 bool "Display information about the board during start up"
748 default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
750 Display information about the board that U-Boot is running on
751 when U-Boot starts up. The board function checkboard() is called
754 menu "Start-up hooks"
756 config ARCH_EARLY_INIT_R
757 bool "Call arch-specific init soon after relocation"
760 With this option U-Boot will call arch_early_init_r() soon after
761 relocation. Driver model is running by this point, and the cache
762 is on. Note that board_early_init_r() is called first, if
763 enabled. This can be used to set up architecture-specific devices.
765 config ARCH_MISC_INIT
766 bool "Call arch-specific init after relocation, when console is ready"
768 With this option U-Boot will call arch_misc_init() after
769 relocation to allow miscellaneous arch-dependent initialisation
770 to be performed. This function should be defined by the board
771 and will be called after the console is set up, after relocaiton.
773 config BOARD_EARLY_INIT_F
774 bool "Call board-specific init before relocation"
777 Some boards need to perform initialisation as soon as possible
778 after boot. With this option, U-Boot calls board_early_init_f()
779 after driver model is ready in the pre-relocation init sequence.
780 Note that the normal serial console is not yet set up, but the
781 debug UART will be available if enabled.
785 menu "Security support"
788 bool # "Support hashing API (SHA1, SHA256, etc.)"
790 This provides a way to hash data in memory using various supported
791 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
792 and the algorithms it supports are defined in common/hash.c. See
793 also CMD_HASH for command-line access.
797 source "common/spl/Kconfig"
projects / u-boot / blob