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_RECORD_COUNT
50 int "Number of boot stage records to store"
53 This is the size of the bootstage record list and is the maximum
54 number of bootstage records that can be recorded.
56 config SPL_BOOTSTAGE_RECORD_COUNT
57 int "Number of boot stage records to store for SPL"
60 This is the size of the bootstage record list and is the maximum
61 number of bootstage records that can be recorded.
64 bool "Store boot timing information in the OS device tree"
67 Stash the bootstage information in the FDT. A root 'bootstage'
68 node is created with each bootstage id as a child. Each child
69 has a 'name' property and either 'mark' containing the
70 mark time in microseconds, or 'accum' containing the
71 accumulated time for that bootstage id in microseconds.
76 name = "board_init_f";
85 Code in the Linux kernel can find this in /proc/devicetree.
87 config BOOTSTAGE_STASH
88 bool "Stash the boot timing information in memory before booting OS"
91 Some OSes do not support device tree. Bootstage can instead write
92 the boot timing information in a binary format at a given address.
93 This happens through a call to bootstage_stash(), typically in
94 the CPU's cleanup_before_linux() function. You can use the
95 'bootstage stash' and 'bootstage unstash' commands to do this on
98 config BOOTSTAGE_STASH_ADDR
99 hex "Address to stash boot timing information"
102 Provide an address which will not be overwritten by the OS when it
103 starts, so that it can read this information when ready.
105 config BOOTSTAGE_STASH_SIZE
106 hex "Size of boot timing stash region"
109 This should be large enough to hold the bootstage stash. A value of
110 4096 (4KiB) is normally plenty.
117 bool "Support for booting from NOR flash"
120 Enabling this will make a U-Boot binary that is capable of being
121 booted via NOR. In this case we will enable certain pinmux early
122 as the ROM only partially sets up pinmux. We also default to using
126 bool "Support for booting from NAND flash"
129 Enabling this will make a U-Boot binary that is capable of being
130 booted via NAND flash. This is not a must, some SoCs need this,
134 bool "Support for booting from ONENAND"
137 Enabling this will make a U-Boot binary that is capable of being
138 booted via ONENAND. This is not a must, some SoCs need this,
142 bool "Support for booting from QSPI flash"
145 Enabling this will make a U-Boot binary that is capable of being
146 booted via QSPI flash. This is not a must, some SoCs need this,
150 bool "Support for booting from SATA"
153 Enabling this will make a U-Boot binary that is capable of being
154 booted via SATA. This is not a must, some SoCs need this,
158 bool "Support for booting from SD/EMMC"
161 Enabling this will make a U-Boot binary that is capable of being
162 booted via SD/EMMC. This is not a must, some SoCs need this,
166 bool "Support for booting from SPI flash"
169 Enabling this will make a U-Boot binary that is capable of being
170 booted via SPI flash. This is not a must, some SoCs need this,
176 int "delay in seconds before automatically booting"
180 Delay before automatically running bootcmd;
181 set to 0 to autoboot with no delay, but you can stop it by key input.
182 set to -1 to disable autoboot.
183 set to -2 to autoboot with no delay and not check for abort
185 If this value is >= 0 then it is also used for the default delay
186 before starting the default entry in bootmenu. If it is < 0 then
187 a default value of 10s is used.
189 See doc/README.autoboot for details.
192 bool "Enable boot arguments"
194 Provide boot arguments to bootm command. Boot arguments are specified
195 in CONFIG_BOOTARGS option. Enable this option to be able to specify
196 CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
197 will be undefined and won't take any space in U-Boot image.
200 string "Boot arguments"
201 depends on USE_BOOTARGS
203 This can be used to pass arguments to the bootm command. The value of
204 CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
205 this value will also override the "chosen" node in FDT blob.
207 config USE_BOOTCOMMAND
208 bool "Enable a default value for bootcmd"
210 Provide a default value for the bootcmd entry in the environment. If
211 autoboot is enabled this is what will be run automatically. Enable
212 this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
213 this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
214 won't take any space in U-Boot image.
217 string "bootcmd value"
218 depends on USE_BOOTCOMMAND
219 default "run distro_bootcmd" if DISTRO_DEFAULTS
221 This is the string of commands that will be used as bootcmd and if
222 AUTOBOOT is set, automatically run.
229 This is the library functionality to provide a text-based menu of
230 choices for the user to make choices with.
232 config CONSOLE_RECORD
233 bool "Console recording"
235 This provides a way to record console output (and provide console
236 input) through circular buffers. This is mostly useful for testing.
237 Console output is recorded even when the console is silent.
238 To enable console recording, call console_record_reset_enable()
241 config CONSOLE_RECORD_OUT_SIZE
242 hex "Output buffer size"
243 depends on CONSOLE_RECORD
244 default 0x400 if CONSOLE_RECORD
246 Set the size of the console output buffer. When this fills up, no
247 more data will be recorded until some is removed. The buffer is
248 allocated immediately after the malloc() region is ready.
250 config CONSOLE_RECORD_IN_SIZE
251 hex "Input buffer size"
252 depends on CONSOLE_RECORD
253 default 0x100 if CONSOLE_RECORD
255 Set the size of the console input buffer. When this contains data,
256 tstc() and getc() will use this in preference to real device input.
257 The buffer is allocated immediately after the malloc() region is
261 string "Board specific string to be added to uboot version string"
263 This options adds the board specific name to u-boot version.
270 All Messages with a loglevel smaller than the console loglevel will
271 be compiled in. The loglevels are defined as follows:
273 0 (KERN_EMERG) system is unusable
274 1 (KERN_ALERT) action must be taken immediately
275 2 (KERN_CRIT) critical conditions
276 3 (KERN_ERR) error conditions
277 4 (KERN_WARNING) warning conditions
278 5 (KERN_NOTICE) normal but significant condition
279 6 (KERN_INFO) informational
280 7 (KERN_DEBUG) debug-level messages
286 config SILENT_CONSOLE
287 bool "Support a silent console"
289 This option allows the console to be silenced, meaning that no
290 output will appear on the console devices. This is controlled by
291 setting the environment vaariable 'silent' to a non-empty value.
292 Note this also silences the console when booting Linux.
294 When the console is set up, the variable is checked, and the
295 GD_FLG_SILENT flag is set. Changing the environment variable later
296 will update the flag.
298 config SILENT_U_BOOT_ONLY
299 bool "Only silence the U-Boot console"
300 depends on SILENT_CONSOLE
302 Normally when the U-Boot console is silenced, Linux's console is
303 also silenced (assuming the board boots into Linux). This option
304 allows the linux console to operate normally, even if U-Boot's
307 config SILENT_CONSOLE_UPDATE_ON_SET
308 bool "Changes to the 'silent' environment variable update immediately"
309 depends on SILENT_CONSOLE
310 default y if SILENT_CONSOLE
312 When the 'silent' environment variable is changed, update the
313 console silence flag immediately. This allows 'setenv' to be used
314 to silence or un-silence the console.
316 The effect is that any change to the variable will affect the
319 config SILENT_CONSOLE_UPDATE_ON_RELOC
320 bool "Allow flags to take effect on relocation"
321 depends on SILENT_CONSOLE
323 In some cases the environment is not available until relocation
324 (e.g. NAND). This option makes the value of the 'silent'
325 environment variable take effect at relocation.
327 config PRE_CONSOLE_BUFFER
328 bool "Buffer characters before the console is available"
330 Prior to the console being initialised (i.e. serial UART
331 initialised etc) all console output is silently discarded.
332 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
333 buffer any console messages prior to the console being
334 initialised to a buffer. The buffer is a circular buffer, so
335 if it overflows, earlier output is discarded.
337 Note that this is not currently supported in SPL. It would be
338 useful to be able to share the pre-console buffer with SPL.
340 config PRE_CON_BUF_SZ
341 int "Sets the size of the pre-console buffer"
342 depends on PRE_CONSOLE_BUFFER
345 The size of the pre-console buffer affects how much console output
346 can be held before it overflows and starts discarding earlier
347 output. Normally there is very little output at this early stage,
348 unless debugging is enabled, so allow enough for ~10 lines of
351 This is a useful feature if you are using a video console and
352 want to see the full boot output on the console. Without this
353 option only the post-relocation output will be displayed.
355 config PRE_CON_BUF_ADDR
356 hex "Address of the pre-console buffer"
357 depends on PRE_CONSOLE_BUFFER
358 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
359 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
361 This sets the start address of the pre-console buffer. This must
362 be in available memory and is accessed before relocation and
363 possibly before DRAM is set up. Therefore choose an address
366 We should consider removing this option and allocating the memory
367 in board_init_f_init_reserve() instead.
370 bool "Enable console multiplexing"
371 default y if DM_VIDEO || VIDEO || LCD
373 This allows multiple devices to be used for each console 'file'.
374 For example, stdout can be set to go to serial and video.
375 Similarly, stdin can be set to come from serial and keyboard.
376 Input can be provided from either source. Console multiplexing
377 adds a small amount of size to U-Boot. Changes to the environment
378 variables stdout, stdin and stderr will take effect immediately.
380 config SYS_CONSOLE_IS_IN_ENV
381 bool "Select console devices from the environment"
382 default y if CONSOLE_MUX
384 This allows multiple input/output devices to be set at boot time.
385 For example, if stdout is set to "serial,video" then output will
386 be sent to both the serial and video devices on boot. The
387 environment variables can be updated after boot to change the
388 input/output devices.
390 config SYS_CONSOLE_OVERWRITE_ROUTINE
391 bool "Allow board control over console overwriting"
393 If this is enabled, and the board-specific function
394 overwrite_console() returns 1, the stdin, stderr and stdout are
395 switched to the serial port, else the settings in the environment
396 are used. If this is not enabled, the console will not be switched
399 config SYS_CONSOLE_ENV_OVERWRITE
400 bool "Update environment variables during console init"
402 The console environment variables (stdout, stdin, stderr) can be
403 used to determine the correct console devices on start-up. This
404 option writes the console devices to these variables on console
405 start-up (after relocation). This causes the environment to be
406 updated to match the console devices actually chosen.
408 config SYS_CONSOLE_INFO_QUIET
409 bool "Don't display the console devices on boot"
411 Normally U-Boot displays the current settings for stdout, stdin
412 and stderr on boot when the post-relocation console is set up.
413 Enable this option to supress this output. It can be obtained by
414 calling stdio_print_current_devices() from board code.
416 config SYS_STDIO_DEREGISTER
417 bool "Allow deregistering stdio devices"
418 default y if USB_KEYBOARD
420 Generally there is no need to deregister stdio devices since they
421 are never deactivated. But if a stdio device is used which can be
422 removed (for example a USB keyboard) then this option can be
423 enabled to ensure this is handled correctly.
430 bool "Enable logging support"
433 This enables support for logging of status and debug messages. These
434 can be displayed on the console, recorded in a memory buffer, or
435 discarded if not needed. Logging supports various categories and
439 bool "Enable logging support in SPL"
441 This enables support for logging of status and debug messages. These
442 can be displayed on the console, recorded in a memory buffer, or
443 discarded if not needed. Logging supports various categories and
447 int "Maximum log level to record"
451 This selects the maximum log level that will be recorded. Any value
452 higher than this will be ignored. If possible log statements below
453 this level will be discarded at build time. Levels:
464 config SPL_LOG_MAX_LEVEL
465 int "Maximum log level to record in SPL"
469 This selects the maximum log level that will be recorded. Any value
470 higher than this will be ignored. If possible log statements below
471 this level will be discarded at build time. Levels:
483 bool "Allow log output to the console"
487 Enables a log driver which writes log records to the console.
488 Generally the console is the serial port or LCD display. Only the
489 log message is shown - other details like level, category, file and
490 line number are omitted.
492 config LOG_SPL_CONSOLE
493 bool "Allow log output to the console in SPL"
497 Enables a log driver which writes log records to the console.
498 Generally the console is the serial port or LCD display. Only the
499 log message is shown - other details like level, category, file and
500 line number are omitted.
503 bool "Provide a test for logging"
507 This enables a 'log test' command to test logging. It is normally
508 executed from a pytest and simply outputs logging information
509 in various different ways to test that the logging system works
510 correctly with varoius settings.
512 config LOG_ERROR_RETURN
513 bool "Log all functions which return an error"
516 When an error is returned in U-Boot it is sometimes difficult to
517 figure out the root cause. For eaxmple, reading from SPI flash may
518 fail due to a problem in the SPI controller or due to the flash part
519 not returning the expected information. This option changes
520 log_ret() to log any errors it sees. With this option disabled,
523 You can add log_ret() to all functions which return an error code.
527 config SUPPORT_RAW_INITRD
528 bool "Enable raw initrd images"
530 Note, defining the SUPPORT_RAW_INITRD allows user to supply
531 kernel with raw initrd images. The syntax is slightly different, the
532 address of the initrd must be augmented by it's size, in the following
533 format: "<initrd address>:<initrd size>".
535 config DEFAULT_FDT_FILE
536 string "Default fdt file"
538 This option is used to set the default fdt file to boot OS.
540 config VERSION_VARIABLE
541 bool "add U-Boot environment variable vers"
544 If this variable is defined, an environment variable
545 named "ver" is created by U-Boot showing the U-Boot
546 version as printed by the "version" command.
547 Any change to this variable will be reverted at the
550 config BOARD_LATE_INIT
553 Sometimes board require some initialization code that might
554 require once the actual init done, example saving board specific env,
555 boot-modes etc. which eventually done at late.
557 So this config enable the late init code with the help of board_late_init
558 function which should defined on respective boards.
560 config DISPLAY_CPUINFO
561 bool "Display information about the CPU during start up"
562 default y if ARM || NIOS2 || X86 || XTENSA || M68K
564 Display information about the CPU that U-Boot is running on
565 when U-Boot starts up. The function print_cpuinfo() is called
568 config DISPLAY_BOARDINFO
569 bool "Display information about the board during early start up"
570 default y if ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
572 Display information about the board that U-Boot is running on
573 when U-Boot starts up. The board function checkboard() is called
576 config DISPLAY_BOARDINFO_LATE
577 bool "Display information about the board during late start up"
579 Display information about the board that U-Boot is running on after
580 the relocation phase. The board function checkboard() is called to do
583 menu "Start-up hooks"
585 config ARCH_EARLY_INIT_R
586 bool "Call arch-specific init soon after relocation"
588 With this option U-Boot will call arch_early_init_r() soon after
589 relocation. Driver model is running by this point, and the cache
590 is on. Note that board_early_init_r() is called first, if
591 enabled. This can be used to set up architecture-specific devices.
593 config ARCH_MISC_INIT
594 bool "Call arch-specific init after relocation, when console is ready"
596 With this option U-Boot will call arch_misc_init() after
597 relocation to allow miscellaneous arch-dependent initialisation
598 to be performed. This function should be defined by the board
599 and will be called after the console is set up, after relocaiton.
601 config BOARD_EARLY_INIT_F
602 bool "Call board-specific init before relocation"
604 Some boards need to perform initialisation as soon as possible
605 after boot. With this option, U-Boot calls board_early_init_f()
606 after driver model is ready in the pre-relocation init sequence.
607 Note that the normal serial console is not yet set up, but the
608 debug UART will be available if enabled.
610 config BOARD_EARLY_INIT_R
611 bool "Call board-specific init after relocation"
613 Some boards need to perform initialisation as directly after
614 relocation. With this option, U-Boot calls board_early_init_r()
615 in the post-relocation init sequence.
617 config LAST_STAGE_INIT
618 bool "Call board-specific as last setup step"
620 Some boards need to perform initialisation immediately before control
621 is passed to the command-line interpreter (e.g. for initializations
622 that depend on later phases in the init sequence). With this option,
623 U-Boot calls last_stage_init() before the command-line interpreter is
628 menu "Security support"
631 bool # "Support hashing API (SHA1, SHA256, etc.)"
633 This provides a way to hash data in memory using various supported
634 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
635 and the algorithms it supports are defined in common/hash.c. See
636 also CMD_HASH for command-line access.
640 menu "Update support"
643 bool "Auto-update using fitImage via TFTP"
646 This option allows performing update of NOR with data in fitImage
649 config UPDATE_TFTP_CNT_MAX
650 int "The number of connection retries during auto-update"
652 depends on UPDATE_TFTP
654 config UPDATE_TFTP_MSEC_MAX
655 int "Delay in mSec to wait for the TFTP server during auto-update"
657 depends on UPDATE_TFTP
661 source "common/spl/Kconfig"