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.
240 This is the library functionality to provide a text-based menu of
241 choices for the user to make choices with.
243 config CONSOLE_RECORD
244 bool "Console recording"
246 This provides a way to record console output (and provide console
247 input) through circular buffers. This is mostly useful for testing.
248 Console output is recorded even when the console is silent.
249 To enable console recording, call console_record_reset_enable()
252 config CONSOLE_RECORD_OUT_SIZE
253 hex "Output buffer size"
254 depends on CONSOLE_RECORD
255 default 0x400 if CONSOLE_RECORD
257 Set the size of the console output buffer. When this fills up, no
258 more data will be recorded until some is removed. The buffer is
259 allocated immediately after the malloc() region is ready.
261 config CONSOLE_RECORD_IN_SIZE
262 hex "Input buffer size"
263 depends on CONSOLE_RECORD
264 default 0x100 if CONSOLE_RECORD
266 Set the size of the console input buffer. When this contains data,
267 tstc() and getc() will use this in preference to real device input.
268 The buffer is allocated immediately after the malloc() region is
271 config DISABLE_CONSOLE
272 bool "Add functionality to disable console completely"
274 Disable console (in & out).
277 string "Board specific string to be added to uboot version string"
279 This options adds the board specific name to u-boot version.
286 All Messages with a loglevel smaller than the console loglevel will
287 be compiled in. The loglevels are defined as follows:
298 9 - debug hardware I/O
308 config SILENT_CONSOLE
309 bool "Support a silent console"
311 This option allows the console to be silenced, meaning that no
312 output will appear on the console devices. This is controlled by
313 setting the environment variable 'silent' to a non-empty value.
314 Note this also silences the console when booting Linux.
316 When the console is set up, the variable is checked, and the
317 GD_FLG_SILENT flag is set. Changing the environment variable later
318 will update the flag.
320 config SILENT_U_BOOT_ONLY
321 bool "Only silence the U-Boot console"
322 depends on SILENT_CONSOLE
324 Normally when the U-Boot console is silenced, Linux's console is
325 also silenced (assuming the board boots into Linux). This option
326 allows the linux console to operate normally, even if U-Boot's
329 config SILENT_CONSOLE_UPDATE_ON_SET
330 bool "Changes to the 'silent' environment variable update immediately"
331 depends on SILENT_CONSOLE
332 default y if SILENT_CONSOLE
334 When the 'silent' environment variable is changed, update the
335 console silence flag immediately. This allows 'setenv' to be used
336 to silence or un-silence the console.
338 The effect is that any change to the variable will affect the
341 config SILENT_CONSOLE_UPDATE_ON_RELOC
342 bool "Allow flags to take effect on relocation"
343 depends on SILENT_CONSOLE
345 In some cases the environment is not available until relocation
346 (e.g. NAND). This option makes the value of the 'silent'
347 environment variable take effect at relocation.
349 config PRE_CONSOLE_BUFFER
350 bool "Buffer characters before the console is available"
352 Prior to the console being initialised (i.e. serial UART
353 initialised etc) all console output is silently discarded.
354 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
355 buffer any console messages prior to the console being
356 initialised to a buffer. The buffer is a circular buffer, so
357 if it overflows, earlier output is discarded.
359 Note that this is not currently supported in SPL. It would be
360 useful to be able to share the pre-console buffer with SPL.
362 config PRE_CON_BUF_SZ
363 int "Sets the size of the pre-console buffer"
364 depends on PRE_CONSOLE_BUFFER
367 The size of the pre-console buffer affects how much console output
368 can be held before it overflows and starts discarding earlier
369 output. Normally there is very little output at this early stage,
370 unless debugging is enabled, so allow enough for ~10 lines of
373 This is a useful feature if you are using a video console and
374 want to see the full boot output on the console. Without this
375 option only the post-relocation output will be displayed.
377 config PRE_CON_BUF_ADDR
378 hex "Address of the pre-console buffer"
379 depends on PRE_CONSOLE_BUFFER
380 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
381 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
383 This sets the start address of the pre-console buffer. This must
384 be in available memory and is accessed before relocation and
385 possibly before DRAM is set up. Therefore choose an address
388 We should consider removing this option and allocating the memory
389 in board_init_f_init_reserve() instead.
392 bool "Enable console multiplexing"
393 default y if DM_VIDEO || VIDEO || LCD
395 This allows multiple devices to be used for each console 'file'.
396 For example, stdout can be set to go to serial and video.
397 Similarly, stdin can be set to come from serial and keyboard.
398 Input can be provided from either source. Console multiplexing
399 adds a small amount of size to U-Boot. Changes to the environment
400 variables stdout, stdin and stderr will take effect immediately.
402 config SYS_CONSOLE_IS_IN_ENV
403 bool "Select console devices from the environment"
404 default y if CONSOLE_MUX
406 This allows multiple input/output devices to be set at boot time.
407 For example, if stdout is set to "serial,video" then output will
408 be sent to both the serial and video devices on boot. The
409 environment variables can be updated after boot to change the
410 input/output devices.
412 config SYS_CONSOLE_OVERWRITE_ROUTINE
413 bool "Allow board control over console overwriting"
415 If this is enabled, and the board-specific function
416 overwrite_console() returns 1, the stdin, stderr and stdout are
417 switched to the serial port, else the settings in the environment
418 are used. If this is not enabled, the console will not be switched
421 config SYS_CONSOLE_ENV_OVERWRITE
422 bool "Update environment variables during console init"
424 The console environment variables (stdout, stdin, stderr) can be
425 used to determine the correct console devices on start-up. This
426 option writes the console devices to these variables on console
427 start-up (after relocation). This causes the environment to be
428 updated to match the console devices actually chosen.
430 config SYS_CONSOLE_INFO_QUIET
431 bool "Don't display the console devices on boot"
433 Normally U-Boot displays the current settings for stdout, stdin
434 and stderr on boot when the post-relocation console is set up.
435 Enable this option to suppress this output. It can be obtained by
436 calling stdio_print_current_devices() from board code.
438 config SYS_STDIO_DEREGISTER
439 bool "Allow deregistering stdio devices"
440 default y if USB_KEYBOARD
442 Generally there is no need to deregister stdio devices since they
443 are never deactivated. But if a stdio device is used which can be
444 removed (for example a USB keyboard) then this option can be
445 enabled to ensure this is handled correctly.
452 bool "Enable logging support"
455 This enables support for logging of status and debug messages. These
456 can be displayed on the console, recorded in a memory buffer, or
457 discarded if not needed. Logging supports various categories and
461 bool "Enable logging support in SPL"
464 This enables support for logging of status and debug messages. These
465 can be displayed on the console, recorded in a memory buffer, or
466 discarded if not needed. Logging supports various categories and
470 bool "Enable logging support in TPL"
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 int "Maximum log level to record"
483 This selects the maximum log level that will be recorded. Any value
484 higher than this will be ignored. If possible log statements below
485 this level will be discarded at build time. Levels:
496 9 - debug hardware I/O
498 config SPL_LOG_MAX_LEVEL
499 int "Maximum log level to record in SPL"
503 This selects the maximum log level that will be recorded. Any value
504 higher than this will be ignored. If possible log statements below
505 this level will be discarded at build time. Levels:
516 9 - debug hardware I/O
518 config TPL_LOG_MAX_LEVEL
519 int "Maximum log level to record in TPL"
523 This selects the maximum log level that will be recorded. Any value
524 higher than this will be ignored. If possible log statements below
525 this level will be discarded at build time. Levels:
536 9 - debug hardware I/O
539 bool "Allow log output to the console"
543 Enables a log driver which writes log records to the console.
544 Generally the console is the serial port or LCD display. Only the
545 log message is shown - other details like level, category, file and
546 line number are omitted.
548 config SPL_LOG_CONSOLE
549 bool "Allow log output to the console in SPL"
553 Enables a log driver which writes log records to the console.
554 Generally the console is the serial port or LCD display. Only the
555 log message is shown - other details like level, category, file and
556 line number are omitted.
558 config TPL_LOG_CONSOLE
559 bool "Allow log output to the console in SPL"
563 Enables a log driver which writes log records to the console.
564 Generally the console is the serial port or LCD display. Only the
565 log message is shown - other details like level, category, file and
566 line number are omitted.
569 bool "Provide a test for logging"
573 This enables a 'log test' command to test logging. It is normally
574 executed from a pytest and simply outputs logging information
575 in various different ways to test that the logging system works
576 correctly with various settings.
578 config LOG_ERROR_RETURN
579 bool "Log all functions which return an error"
582 When an error is returned in U-Boot it is sometimes difficult to
583 figure out the root cause. For example, reading from SPI flash may
584 fail due to a problem in the SPI controller or due to the flash part
585 not returning the expected information. This option changes
586 log_ret() to log any errors it sees. With this option disabled,
589 You can add log_ret() to all functions which return an error code.
593 config SUPPORT_RAW_INITRD
594 bool "Enable raw initrd images"
596 Note, defining the SUPPORT_RAW_INITRD allows user to supply
597 kernel with raw initrd images. The syntax is slightly different, the
598 address of the initrd must be augmented by it's size, in the following
599 format: "<initrd address>:<initrd size>".
601 config DEFAULT_FDT_FILE
602 string "Default fdt file"
604 This option is used to set the default fdt file to boot OS.
607 bool "Execute Misc Init"
608 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
609 default y if ARCH_OMAP2PLUS && !AM33XX
611 Enabling this option calls 'misc_init_r' function
613 config VERSION_VARIABLE
614 bool "add U-Boot environment variable vers"
617 If this variable is defined, an environment variable
618 named "ver" is created by U-Boot showing the U-Boot
619 version as printed by the "version" command.
620 Any change to this variable will be reverted at the
623 config BOARD_LATE_INIT
624 bool "Execute Board late init"
626 Sometimes board require some initialization code that might
627 require once the actual init done, example saving board specific env,
628 boot-modes etc. which eventually done at late.
630 So this config enable the late init code with the help of board_late_init
631 function which should defined on respective boards.
633 config DISPLAY_CPUINFO
634 bool "Display information about the CPU during start up"
635 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
637 Display information about the CPU that U-Boot is running on
638 when U-Boot starts up. The function print_cpuinfo() is called
641 config DISPLAY_BOARDINFO
642 bool "Display information about the board during early start up"
643 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
645 Display information about the board that U-Boot is running on
646 when U-Boot starts up. The board function checkboard() is called
649 config DISPLAY_BOARDINFO_LATE
650 bool "Display information about the board during late start up"
652 Display information about the board that U-Boot is running on after
653 the relocation phase. The board function checkboard() is called to do
657 bool "Include bounce buffer API"
659 Some peripherals support DMA from a subset of physically
660 addressable memory only. To support such peripherals, the
661 bounce buffer API uses a temporary buffer: it copies data
662 to/from DMA regions while managing cache operations.
664 A second possible use of bounce buffers is their ability to
665 provide aligned buffers for DMA operations.
668 bool "Call get_board_type() to get and display the board type"
670 If this option is enabled, checkboard() will call get_board_type()
671 to get a string containing the board type and this will be
672 displayed immediately after the model is shown on the console
675 menu "Start-up hooks"
677 config ARCH_EARLY_INIT_R
678 bool "Call arch-specific init soon after relocation"
680 With this option U-Boot will call arch_early_init_r() soon after
681 relocation. Driver model is running by this point, and the cache
682 is on. Note that board_early_init_r() is called first, if
683 enabled. This can be used to set up architecture-specific devices.
685 config ARCH_MISC_INIT
686 bool "Call arch-specific init after relocation, when console is ready"
688 With this option U-Boot will call arch_misc_init() after
689 relocation to allow miscellaneous arch-dependent initialisation
690 to be performed. This function should be defined by the board
691 and will be called after the console is set up, after relocation.
693 config BOARD_EARLY_INIT_F
694 bool "Call board-specific init before relocation"
696 Some boards need to perform initialisation as soon as possible
697 after boot. With this option, U-Boot calls board_early_init_f()
698 after driver model is ready in the pre-relocation init sequence.
699 Note that the normal serial console is not yet set up, but the
700 debug UART will be available if enabled.
702 config BOARD_EARLY_INIT_R
703 bool "Call board-specific init after relocation"
705 Some boards need to perform initialisation as directly after
706 relocation. With this option, U-Boot calls board_early_init_r()
707 in the post-relocation init sequence.
709 config LAST_STAGE_INIT
710 bool "Call board-specific as last setup step"
712 Some boards need to perform initialisation immediately before control
713 is passed to the command-line interpreter (e.g. for initializations
714 that depend on later phases in the init sequence). With this option,
715 U-Boot calls last_stage_init() before the command-line interpreter is
720 menu "Security support"
723 bool # "Support hashing API (SHA1, SHA256, etc.)"
725 This provides a way to hash data in memory using various supported
726 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
727 and the algorithms it supports are defined in common/hash.c. See
728 also CMD_HASH for command-line access.
731 bool "Build Android Verified Boot operations"
732 depends on LIBAVB && FASTBOOT
733 depends on PARTITION_UUIDS
735 This option enables compilation of bootloader-dependent operations,
736 used by Android Verified Boot 2.0 library (libavb). Includes:
737 * Helpers to process strings in order to build OS bootargs.
738 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
739 * Helpers to alloc/init/free avb ops.
742 bool # "Support hashing API (SHA1, SHA256, etc.)"
744 This provides a way to hash data in memory using various supported
745 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
746 and the algorithms it supports are defined in common/hash.c. See
747 also CMD_HASH for command-line access.
750 bool # "Support hashing API (SHA1, SHA256, etc.)"
752 This provides a way to hash data in memory using various supported
753 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
754 and the algorithms it supports are defined in common/hash.c. See
755 also CMD_HASH for command-line access.
759 menu "Update support"
762 bool "Auto-update using fitImage via TFTP"
765 This option allows performing update of NOR with data in fitImage
768 config UPDATE_TFTP_CNT_MAX
769 int "The number of connection retries during auto-update"
771 depends on UPDATE_TFTP
773 config UPDATE_TFTP_MSEC_MAX
774 int "Delay in mSec to wait for the TFTP server during auto-update"
776 depends on UPDATE_TFTP
783 bool "Support for a bloblist"
785 This enables support for a bloblist in U-Boot, which can be passed
786 from TPL to SPL to U-Boot proper (and potentially to Linux). The
787 blob list supports multiple binary blobs of data, each with a tag,
788 so that different U-Boot components can store data which can survive
789 through to the next stage of the boot.
792 bool "Support for a bloblist in SPL"
796 This enables a bloblist in SPL. If this is the first part of U-Boot
797 to run, then the bloblist is set up in SPL and passed to U-Boot
798 proper. If TPL also has a bloblist, then SPL uses the one from there.
801 bool "Support for a bloblist in TPL"
805 This enables a bloblist in TPL. The bloblist is set up in TPL and
806 passed to SPL and U-Boot proper.
809 hex "Size of bloblist"
813 Sets the size of the bloblist in bytes. This must include all
814 overhead (alignment, bloblist header, record header). The bloblist
815 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
816 proper), and this sane bloblist is used for subsequent stages.
819 hex "Address of bloblist"
821 default 0xe000 if SANDBOX
823 Sets the address of the bloblist, set up by the first part of U-Boot
824 which runs. Subsequent U-Boot stages typically use the same address.
828 source "common/spl/Kconfig"