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
31 bool "Boot timing and reported in TPL"
34 Enable recording of boot time in SPL. To make this visible to U-Boot
35 proper, enable BOOTSTAGE_STASH as well. This will stash the timing
36 information when TPL finishes and load it when U-Boot proper starts
39 config BOOTSTAGE_REPORT
40 bool "Display a detailed boot timing report before booting the OS"
43 Enable output of a boot time report just before the OS is booted.
44 This shows how long it took U-Boot to go through each stage of the
45 boot process. The report looks something like this:
47 Timer summary in microseconds:
50 3,575,678 3,575,678 board_init_f start
51 3,575,695 17 arch_cpu_init A9
52 3,575,777 82 arch_cpu_init done
53 3,659,598 83,821 board_init_r start
54 3,910,375 250,777 main_loop
55 29,916,167 26,005,792 bootm_start
56 30,361,327 445,160 start_kernel
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.
65 config SPL_BOOTSTAGE_RECORD_COUNT
66 int "Number of boot stage records to store for SPL"
69 This is the size of the bootstage record list and is the maximum
70 number of bootstage records that can be recorded.
73 bool "Store boot timing information in the OS device tree"
76 Stash the bootstage information in the FDT. A root 'bootstage'
77 node is created with each bootstage id as a child. Each child
78 has a 'name' property and either 'mark' containing the
79 mark time in microseconds, or 'accum' containing the
80 accumulated time for that bootstage id in microseconds.
85 name = "board_init_f";
94 Code in the Linux kernel can find this in /proc/devicetree.
96 config BOOTSTAGE_STASH
97 bool "Stash the boot timing information in memory before booting OS"
100 Some OSes do not support device tree. Bootstage can instead write
101 the boot timing information in a binary format at a given address.
102 This happens through a call to bootstage_stash(), typically in
103 the CPU's cleanup_before_linux() function. You can use the
104 'bootstage stash' and 'bootstage unstash' commands to do this on
107 config BOOTSTAGE_STASH_ADDR
108 hex "Address to stash boot timing information"
111 Provide an address which will not be overwritten by the OS when it
112 starts, so that it can read this information when ready.
114 config BOOTSTAGE_STASH_SIZE
115 hex "Size of boot timing stash region"
118 This should be large enough to hold the bootstage stash. A value of
119 4096 (4KiB) is normally plenty.
126 bool "Support for booting from NOR flash"
129 Enabling this will make a U-Boot binary that is capable of being
130 booted via NOR. In this case we will enable certain pinmux early
131 as the ROM only partially sets up pinmux. We also default to using
135 bool "Support for booting from NAND flash"
139 Enabling this will make a U-Boot binary that is capable of being
140 booted via NAND flash. This is not a must, some SoCs need this,
144 bool "Support for booting from ONENAND"
148 Enabling this will make a U-Boot binary that is capable of being
149 booted via ONENAND. This is not a must, some SoCs need this,
153 bool "Support for booting from QSPI flash"
156 Enabling this will make a U-Boot binary that is capable of being
157 booted via QSPI flash. This is not a must, some SoCs need this,
161 bool "Support for booting from SATA"
164 Enabling this will make a U-Boot binary that is capable of being
165 booted via SATA. This is not a must, some SoCs need this,
169 bool "Support for booting from SD/EMMC"
172 Enabling this will make a U-Boot binary that is capable of being
173 booted via SD/EMMC. This is not a must, some SoCs need this,
177 bool "Support for booting from SPI flash"
180 Enabling this will make a U-Boot binary that is capable of being
181 booted via SPI flash. This is not a must, some SoCs need this,
187 int "delay in seconds before automatically booting"
191 Delay before automatically running bootcmd;
192 set to 0 to autoboot with no delay, but you can stop it by key input.
193 set to -1 to disable autoboot.
194 set to -2 to autoboot with no delay and not check for abort
196 If this value is >= 0 then it is also used for the default delay
197 before starting the default entry in bootmenu. If it is < 0 then
198 a default value of 10s is used.
200 See doc/README.autoboot for details.
203 bool "Enable boot arguments"
205 Provide boot arguments to bootm command. Boot arguments are specified
206 in CONFIG_BOOTARGS option. Enable this option to be able to specify
207 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
208 will be undefined and won't take any space in U-Boot image.
211 string "Boot arguments"
212 depends on USE_BOOTARGS
214 This can be used to pass arguments to the bootm command. The value of
215 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
216 this value will also override the "chosen" node in FDT blob.
218 config USE_BOOTCOMMAND
219 bool "Enable a default value for bootcmd"
221 Provide a default value for the bootcmd entry in the environment. If
222 autoboot is enabled this is what will be run automatically. Enable
223 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
224 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
225 won't take any space in U-Boot image.
228 string "bootcmd value"
229 depends on USE_BOOTCOMMAND
230 default "run distro_bootcmd" if DISTRO_DEFAULTS
232 This is the string of commands that will be used as bootcmd and if
233 AUTOBOOT is set, automatically run.
236 bool "Enable preboot"
238 When this option is enabled, the existence of the environment
239 variable "preboot" will be checked immediately before starting the
240 CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
241 entering interactive mode.
243 This feature is especially useful when "preboot" is automatically
244 generated or modified. For example, the boot code can modify the
245 "preboot" when a user holds down a certain combination of keys.
248 string "preboot default value"
249 depends on USE_PREBOOT
251 This is the default of "preboot" environment variable.
258 This is the library functionality to provide a text-based menu of
259 choices for the user to make choices with.
261 config CONSOLE_RECORD
262 bool "Console recording"
264 This provides a way to record console output (and provide console
265 input) through circular buffers. This is mostly useful for testing.
266 Console output is recorded even when the console is silent.
267 To enable console recording, call console_record_reset_enable()
270 config CONSOLE_RECORD_OUT_SIZE
271 hex "Output buffer size"
272 depends on CONSOLE_RECORD
273 default 0x400 if CONSOLE_RECORD
275 Set the size of the console output buffer. When this fills up, no
276 more data will be recorded until some is removed. The buffer is
277 allocated immediately after the malloc() region is ready.
279 config CONSOLE_RECORD_IN_SIZE
280 hex "Input buffer size"
281 depends on CONSOLE_RECORD
282 default 0x100 if CONSOLE_RECORD
284 Set the size of the console input buffer. When this contains data,
285 tstc() and getc() will use this in preference to real device input.
286 The buffer is allocated immediately after the malloc() region is
289 config DISABLE_CONSOLE
290 bool "Add functionality to disable console completely"
292 Disable console (in & out).
295 string "Board specific string to be added to uboot version string"
297 This options adds the board specific name to u-boot version.
304 All Messages with a loglevel smaller than the console loglevel will
305 be compiled in. The loglevels are defined as follows:
316 9 - debug hardware I/O
326 config SILENT_CONSOLE
327 bool "Support a silent console"
329 This option allows the console to be silenced, meaning that no
330 output will appear on the console devices. This is controlled by
331 setting the environment variable 'silent' to a non-empty value.
332 Note this also silences the console when booting Linux.
334 When the console is set up, the variable is checked, and the
335 GD_FLG_SILENT flag is set. Changing the environment variable later
336 will update the flag.
338 config SILENT_U_BOOT_ONLY
339 bool "Only silence the U-Boot console"
340 depends on SILENT_CONSOLE
342 Normally when the U-Boot console is silenced, Linux's console is
343 also silenced (assuming the board boots into Linux). This option
344 allows the linux console to operate normally, even if U-Boot's
347 config SILENT_CONSOLE_UPDATE_ON_SET
348 bool "Changes to the 'silent' environment variable update immediately"
349 depends on SILENT_CONSOLE
350 default y if SILENT_CONSOLE
352 When the 'silent' environment variable is changed, update the
353 console silence flag immediately. This allows 'setenv' to be used
354 to silence or un-silence the console.
356 The effect is that any change to the variable will affect the
359 config SILENT_CONSOLE_UPDATE_ON_RELOC
360 bool "Allow flags to take effect on relocation"
361 depends on SILENT_CONSOLE
363 In some cases the environment is not available until relocation
364 (e.g. NAND). This option makes the value of the 'silent'
365 environment variable take effect at relocation.
367 config PRE_CONSOLE_BUFFER
368 bool "Buffer characters before the console is available"
370 Prior to the console being initialised (i.e. serial UART
371 initialised etc) all console output is silently discarded.
372 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
373 buffer any console messages prior to the console being
374 initialised to a buffer. The buffer is a circular buffer, so
375 if it overflows, earlier output is discarded.
377 Note that this is not currently supported in SPL. It would be
378 useful to be able to share the pre-console buffer with SPL.
380 config PRE_CON_BUF_SZ
381 int "Sets the size of the pre-console buffer"
382 depends on PRE_CONSOLE_BUFFER
385 The size of the pre-console buffer affects how much console output
386 can be held before it overflows and starts discarding earlier
387 output. Normally there is very little output at this early stage,
388 unless debugging is enabled, so allow enough for ~10 lines of
391 This is a useful feature if you are using a video console and
392 want to see the full boot output on the console. Without this
393 option only the post-relocation output will be displayed.
395 config PRE_CON_BUF_ADDR
396 hex "Address of the pre-console buffer"
397 depends on PRE_CONSOLE_BUFFER
398 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
399 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
401 This sets the start address of the pre-console buffer. This must
402 be in available memory and is accessed before relocation and
403 possibly before DRAM is set up. Therefore choose an address
406 We should consider removing this option and allocating the memory
407 in board_init_f_init_reserve() instead.
410 bool "Enable console multiplexing"
411 default y if DM_VIDEO || VIDEO || LCD
413 This allows multiple devices to be used for each console 'file'.
414 For example, stdout can be set to go to serial and video.
415 Similarly, stdin can be set to come from serial and keyboard.
416 Input can be provided from either source. Console multiplexing
417 adds a small amount of size to U-Boot. Changes to the environment
418 variables stdout, stdin and stderr will take effect immediately.
420 config SYS_CONSOLE_IS_IN_ENV
421 bool "Select console devices from the environment"
422 default y if CONSOLE_MUX
424 This allows multiple input/output devices to be set at boot time.
425 For example, if stdout is set to "serial,video" then output will
426 be sent to both the serial and video devices on boot. The
427 environment variables can be updated after boot to change the
428 input/output devices.
430 config SYS_CONSOLE_OVERWRITE_ROUTINE
431 bool "Allow board control over console overwriting"
433 If this is enabled, and the board-specific function
434 overwrite_console() returns 1, the stdin, stderr and stdout are
435 switched to the serial port, else the settings in the environment
436 are used. If this is not enabled, the console will not be switched
439 config SYS_CONSOLE_ENV_OVERWRITE
440 bool "Update environment variables during console init"
442 The console environment variables (stdout, stdin, stderr) can be
443 used to determine the correct console devices on start-up. This
444 option writes the console devices to these variables on console
445 start-up (after relocation). This causes the environment to be
446 updated to match the console devices actually chosen.
448 config SYS_CONSOLE_INFO_QUIET
449 bool "Don't display the console devices on boot"
451 Normally U-Boot displays the current settings for stdout, stdin
452 and stderr on boot when the post-relocation console is set up.
453 Enable this option to suppress this output. It can be obtained by
454 calling stdio_print_current_devices() from board code.
456 config SYS_STDIO_DEREGISTER
457 bool "Allow deregistering stdio devices"
458 default y if USB_KEYBOARD
460 Generally there is no need to deregister stdio devices since they
461 are never deactivated. But if a stdio device is used which can be
462 removed (for example a USB keyboard) then this option can be
463 enabled to ensure this is handled correctly.
470 bool "Enable logging support"
473 This enables support for logging of status and debug messages. These
474 can be displayed on the console, recorded in a memory buffer, or
475 discarded if not needed. Logging supports various categories and
479 bool "Enable logging support in SPL"
482 This enables support for logging of status and debug messages. These
483 can be displayed on the console, recorded in a memory buffer, or
484 discarded if not needed. Logging supports various categories and
488 bool "Enable logging support in TPL"
491 This enables support for logging of status and debug messages. These
492 can be displayed on the console, recorded in a memory buffer, or
493 discarded if not needed. Logging supports various categories and
497 int "Maximum log level to record"
501 This selects the maximum log level that will be recorded. Any value
502 higher than this will be ignored. If possible log statements below
503 this level will be discarded at build time. Levels:
514 9 - debug hardware I/O
516 config SPL_LOG_MAX_LEVEL
517 int "Maximum log level to record in SPL"
521 This selects the maximum log level that will be recorded. Any value
522 higher than this will be ignored. If possible log statements below
523 this level will be discarded at build time. Levels:
534 9 - debug hardware I/O
536 config TPL_LOG_MAX_LEVEL
537 int "Maximum log level to record in TPL"
541 This selects the maximum log level that will be recorded. Any value
542 higher than this will be ignored. If possible log statements below
543 this level will be discarded at build time. Levels:
554 9 - debug hardware I/O
556 config LOG_DEFAULT_LEVEL
557 int "Default logging level to display"
560 This is the default logging level set when U-Boot starts. It can
561 be adjusted later using the 'log level' command. Note that setting
562 this to a value abnove LOG_MAX_LEVEL will be ineffective, since the
563 higher levels are not compiled in to U-Boot.
574 9 - debug hardware I/O
577 bool "Allow log output to the console"
581 Enables a log driver which writes log records to the console.
582 Generally the console is the serial port or LCD display. Only the
583 log message is shown - other details like level, category, file and
584 line number are omitted.
586 config SPL_LOG_CONSOLE
587 bool "Allow log output to the console in SPL"
591 Enables a log driver which writes log records to the console.
592 Generally the console is the serial port or LCD display. Only the
593 log message is shown - other details like level, category, file and
594 line number are omitted.
596 config TPL_LOG_CONSOLE
597 bool "Allow log output to the console in SPL"
601 Enables a log driver which writes log records to the console.
602 Generally the console is the serial port or LCD display. Only the
603 log message is shown - other details like level, category, file and
604 line number are omitted.
607 bool "Provide a test for logging"
611 This enables a 'log test' command to test logging. It is normally
612 executed from a pytest and simply outputs logging information
613 in various different ways to test that the logging system works
614 correctly with various settings.
616 config LOG_ERROR_RETURN
617 bool "Log all functions which return an error"
620 When an error is returned in U-Boot it is sometimes difficult to
621 figure out the root cause. For example, reading from SPI flash may
622 fail due to a problem in the SPI controller or due to the flash part
623 not returning the expected information. This option changes
624 log_ret() to log any errors it sees. With this option disabled,
627 You can add log_ret() to all functions which return an error code.
631 config SUPPORT_RAW_INITRD
632 bool "Enable raw initrd images"
634 Note, defining the SUPPORT_RAW_INITRD allows user to supply
635 kernel with raw initrd images. The syntax is slightly different, the
636 address of the initrd must be augmented by it's size, in the following
637 format: "<initrd address>:<initrd size>".
639 config DEFAULT_FDT_FILE
640 string "Default fdt file"
642 This option is used to set the default fdt file to boot OS.
645 bool "Execute Misc Init"
646 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
647 default y if ARCH_OMAP2PLUS && !AM33XX
649 Enabling this option calls 'misc_init_r' function
651 config VERSION_VARIABLE
652 bool "add U-Boot environment variable vers"
655 If this variable is defined, an environment variable
656 named "ver" is created by U-Boot showing the U-Boot
657 version as printed by the "version" command.
658 Any change to this variable will be reverted at the
661 config BOARD_LATE_INIT
662 bool "Execute Board late init"
664 Sometimes board require some initialization code that might
665 require once the actual init done, example saving board specific env,
666 boot-modes etc. which eventually done at late.
668 So this config enable the late init code with the help of board_late_init
669 function which should defined on respective boards.
671 config DISPLAY_CPUINFO
672 bool "Display information about the CPU during start up"
673 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
675 Display information about the CPU that U-Boot is running on
676 when U-Boot starts up. The function print_cpuinfo() is called
679 config DISPLAY_BOARDINFO
680 bool "Display information about the board during early start up"
681 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
683 Display information about the board that U-Boot is running on
684 when U-Boot starts up. The board function checkboard() is called
687 config DISPLAY_BOARDINFO_LATE
688 bool "Display information about the board during late start up"
690 Display information about the board that U-Boot is running on after
691 the relocation phase. The board function checkboard() is called to do
695 bool "Include bounce buffer API"
697 Some peripherals support DMA from a subset of physically
698 addressable memory only. To support such peripherals, the
699 bounce buffer API uses a temporary buffer: it copies data
700 to/from DMA regions while managing cache operations.
702 A second possible use of bounce buffers is their ability to
703 provide aligned buffers for DMA operations.
706 bool "Call get_board_type() to get and display the board type"
708 If this option is enabled, checkboard() will call get_board_type()
709 to get a string containing the board type and this will be
710 displayed immediately after the model is shown on the console
713 menu "Start-up hooks"
715 config ARCH_EARLY_INIT_R
716 bool "Call arch-specific init soon after relocation"
718 With this option U-Boot will call arch_early_init_r() soon after
719 relocation. Driver model is running by this point, and the cache
720 is on. Note that board_early_init_r() is called first, if
721 enabled. This can be used to set up architecture-specific devices.
723 config ARCH_MISC_INIT
724 bool "Call arch-specific init after relocation, when console is ready"
726 With this option U-Boot will call arch_misc_init() after
727 relocation to allow miscellaneous arch-dependent initialisation
728 to be performed. This function should be defined by the board
729 and will be called after the console is set up, after relocation.
731 config BOARD_EARLY_INIT_F
732 bool "Call board-specific init before relocation"
734 Some boards need to perform initialisation as soon as possible
735 after boot. With this option, U-Boot calls board_early_init_f()
736 after driver model is ready in the pre-relocation init sequence.
737 Note that the normal serial console is not yet set up, but the
738 debug UART will be available if enabled.
740 config BOARD_EARLY_INIT_R
741 bool "Call board-specific init after relocation"
743 Some boards need to perform initialisation as directly after
744 relocation. With this option, U-Boot calls board_early_init_r()
745 in the post-relocation init sequence.
747 config LAST_STAGE_INIT
748 bool "Call board-specific as last setup step"
750 Some boards need to perform initialisation immediately before control
751 is passed to the command-line interpreter (e.g. for initializations
752 that depend on later phases in the init sequence). With this option,
753 U-Boot calls last_stage_init() before the command-line interpreter is
758 menu "Security support"
761 bool # "Support hashing API (SHA1, SHA256, etc.)"
763 This provides a way to hash data in memory using various supported
764 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
765 and the algorithms it supports are defined in common/hash.c. See
766 also CMD_HASH for command-line access.
769 bool "Build Android Verified Boot operations"
770 depends on LIBAVB && FASTBOOT
771 depends on PARTITION_UUIDS
773 This option enables compilation of bootloader-dependent operations,
774 used by Android Verified Boot 2.0 library (libavb). Includes:
775 * Helpers to process strings in order to build OS bootargs.
776 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
777 * Helpers to alloc/init/free avb ops.
780 bool # "Support hashing API (SHA1, SHA256, etc.)"
782 This provides a way to hash data in memory using various supported
783 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
784 and the algorithms it supports are defined in common/hash.c. See
785 also CMD_HASH for command-line access.
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 menu "Update support"
800 bool "Auto-update using fitImage via TFTP"
803 This option allows performing update of NOR with data in fitImage
806 config UPDATE_TFTP_CNT_MAX
807 int "The number of connection retries during auto-update"
809 depends on UPDATE_TFTP
811 config UPDATE_TFTP_MSEC_MAX
812 int "Delay in mSec to wait for the TFTP server during auto-update"
814 depends on UPDATE_TFTP
821 bool "Support for a bloblist"
823 This enables support for a bloblist in U-Boot, which can be passed
824 from TPL to SPL to U-Boot proper (and potentially to Linux). The
825 blob list supports multiple binary blobs of data, each with a tag,
826 so that different U-Boot components can store data which can survive
827 through to the next stage of the boot.
830 bool "Support for a bloblist in SPL"
834 This enables a bloblist in SPL. If this is the first part of U-Boot
835 to run, then the bloblist is set up in SPL and passed to U-Boot
836 proper. If TPL also has a bloblist, then SPL uses the one from there.
839 bool "Support for a bloblist in TPL"
843 This enables a bloblist in TPL. The bloblist is set up in TPL and
844 passed to SPL and U-Boot proper.
847 hex "Size of bloblist"
851 Sets the size of the bloblist in bytes. This must include all
852 overhead (alignment, bloblist header, record header). The bloblist
853 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
854 proper), and this sane bloblist is used for subsequent stages.
857 hex "Address of bloblist"
859 default 0xe000 if SANDBOX
861 Sets the address of the bloblist, set up by the first part of U-Boot
862 which runs. Subsequent U-Boot stages typically use the same address.
866 source "common/spl/Kconfig"