1menu "Console"
2
3config MENU
4 bool
5 help
6 This is the library functionality to provide a text-based menu of
7 choices for the user to make choices with.
8
9config CONSOLE_RECORD
10 bool "Console recording"
11 help
12 This provides a way to record console output (and provide console
13 input) through circular buffers. This is mostly useful for testing.
14 Console output is recorded even when the console is silent.
15 To enable console recording, call console_record_reset_enable()
16 from your code.
17
18config CONSOLE_RECORD_INIT_F
19 bool "Enable console recording during pre-relocation init"
20 depends on CONSOLE_RECORD && SYS_MALLOC_F
21 default y
22 help
23 This option enables console recording during pre-relocation init.
24 CONFIG_SYS_MALLOC_F must be enabled to use this feature.
25
26config CONSOLE_RECORD_OUT_SIZE
27 hex "Output buffer size"
28 depends on CONSOLE_RECORD
29 default 0x400 if CONSOLE_RECORD
30 help
31 Set the size of the console output buffer. When this fills up, no
32 more data will be recorded until some is removed. The buffer is
33 allocated immediately after the malloc() region is ready.
34
35config CONSOLE_RECORD_IN_SIZE
36 hex "Input buffer size"
37 depends on CONSOLE_RECORD
38 default 0x100 if CONSOLE_RECORD
39 help
40 Set the size of the console input buffer. When this contains data,
41 tstc() and getc() will use this in preference to real device input.
42 The buffer is allocated immediately after the malloc() region is
43 ready.
44
45config DISABLE_CONSOLE
46 bool "Add functionality to disable console completely"
47 help
48 Disable console (in & out).
49
50config IDENT_STRING
51 string "Board specific string to be added to uboot version string"
52 help
53 This options adds the board specific name to u-boot version.
54
55config LOGLEVEL
56 int "loglevel"
57 default 4
58 range 0 10
59 help
60 All Messages with a loglevel smaller than the console loglevel will
61 be compiled in. The loglevels are defined as follows:
62
63 0 - emergency
64 1 - alert
65 2 - critical
66 3 - error
67 4 - warning
68 5 - note
69 6 - info
70 7 - debug
71 8 - debug content
72 9 - debug hardware I/O
73
74config SPL_LOGLEVEL
75 int
76 default LOGLEVEL
77
78config TPL_LOGLEVEL
79 int
80 default LOGLEVEL
81
82config SILENT_CONSOLE
83 bool "Support a silent console"
84 help
85 This option allows the console to be silenced, meaning that no
86 output will appear on the console devices. This is controlled by
87 setting the environment variable 'silent' to a non-empty value.
88 Note this also silences the console when booting Linux.
89
90 When the console is set up, the variable is checked, and the
91 GD_FLG_SILENT flag is set. Changing the environment variable later
92 will update the flag.
93
94config SILENT_U_BOOT_ONLY
95 bool "Only silence the U-Boot console"
96 depends on SILENT_CONSOLE
97 help
98 Normally when the U-Boot console is silenced, Linux's console is
99 also silenced (assuming the board boots into Linux). This option
100 allows the linux console to operate normally, even if U-Boot's
101 is silenced.
102
103config SILENT_CONSOLE_UPDATE_ON_SET
104 bool "Changes to the 'silent' environment variable update immediately"
105 depends on SILENT_CONSOLE
106 default y if SILENT_CONSOLE
107 help
108 When the 'silent' environment variable is changed, update the
109 console silence flag immediately. This allows 'setenv' to be used
110 to silence or un-silence the console.
111
112 The effect is that any change to the variable will affect the
113 GD_FLG_SILENT flag.
114
115config SILENT_CONSOLE_UPDATE_ON_RELOC
116 bool "Allow flags to take effect on relocation"
117 depends on SILENT_CONSOLE
118 help
119 In some cases the environment is not available until relocation
120 (e.g. NAND). This option makes the value of the 'silent'
121 environment variable take effect at relocation.
122
123config PRE_CONSOLE_BUFFER
124 bool "Buffer characters before the console is available"
125 help
126 Prior to the console being initialised (i.e. serial UART
127 initialised etc) all console output is silently discarded.
128 Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
129 buffer any console messages prior to the console being
130 initialised to a buffer. The buffer is a circular buffer, so
131 if it overflows, earlier output is discarded.
132
133 Note that this is not currently supported in SPL. It would be
134 useful to be able to share the pre-console buffer with SPL.
135
136config PRE_CON_BUF_SZ
137 int "Sets the size of the pre-console buffer"
138 depends on PRE_CONSOLE_BUFFER
139 default 4096
140 help
141 The size of the pre-console buffer affects how much console output
142 can be held before it overflows and starts discarding earlier
143 output. Normally there is very little output at this early stage,
144 unless debugging is enabled, so allow enough for ~10 lines of
145 text.
146
147 This is a useful feature if you are using a video console and
148 want to see the full boot output on the console. Without this
149 option only the post-relocation output will be displayed.
150
151config PRE_CON_BUF_ADDR
152 hex "Address of the pre-console buffer"
153 depends on PRE_CONSOLE_BUFFER
154 default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
155 default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
156 default 0x0f000000 if ROCKCHIP_RK3288
157 default 0x0f200000 if ROCKCHIP_RK3399
158 help
159 This sets the start address of the pre-console buffer. This must
160 be in available memory and is accessed before relocation and
161 possibly before DRAM is set up. Therefore choose an address
162 carefully.
163
164 We should consider removing this option and allocating the memory
165 in board_init_f_init_reserve() instead.
166
167config CONSOLE_MUX
168 bool "Enable console multiplexing"
169 default y if DM_VIDEO || VIDEO || LCD
170 help
171 This allows multiple devices to be used for each console 'file'.
172 For example, stdout can be set to go to serial and video.
173 Similarly, stdin can be set to come from serial and keyboard.
174 Input can be provided from either source. Console multiplexing
175 adds a small amount of size to U-Boot. Changes to the environment
176 variables stdout, stdin and stderr will take effect immediately.
177
178config SYS_CONSOLE_IS_IN_ENV
179 bool "Select console devices from the environment"
180 default y if CONSOLE_MUX
181 help
182 This allows multiple input/output devices to be set at boot time.
183 For example, if stdout is set to "serial,vidconsole" then output
184 will be sent to both the serial and video devices on boot. The
185 environment variables can be updated after boot to change the
186 input/output devices.
187
188config SYS_CONSOLE_OVERWRITE_ROUTINE
189 bool "Allow board control over console overwriting"
190 help
191 If this is enabled, and the board-specific function
192 overwrite_console() returns 1, the stdin, stderr and stdout are
193 switched to the serial port, else the settings in the environment
194 are used. If this is not enabled, the console will not be switched
195 to serial.
196
197config SYS_CONSOLE_ENV_OVERWRITE
198 bool "Update environment variables during console init"
199 help
200 The console environment variables (stdout, stdin, stderr) can be
201 used to determine the correct console devices on start-up. This
202 option writes the console devices to these variables on console
203 start-up (after relocation). This causes the environment to be
204 updated to match the console devices actually chosen.
205
206config SYS_CONSOLE_INFO_QUIET
207 bool "Don't display the console devices on boot"
208 help
209 Normally U-Boot displays the current settings for stdout, stdin
210 and stderr on boot when the post-relocation console is set up.
211 Enable this option to suppress this output. It can be obtained by
212 calling stdio_print_current_devices() from board code.
213
214config SYS_STDIO_DEREGISTER
215 bool "Allow deregistering stdio devices"
216 default y if USB_KEYBOARD
217 help
218 Generally there is no need to deregister stdio devices since they
219 are never deactivated. But if a stdio device is used which can be
220 removed (for example a USB keyboard) then this option can be
221 enabled to ensure this is handled correctly.
222
223config SPL_SYS_STDIO_DEREGISTER
224 bool "Allow deregistering stdio devices in SPL"
225 help
226 Generally there is no need to deregister stdio devices since they
227 are never deactivated. But if a stdio device is used which can be
228 removed (for example a USB keyboard) then this option can be
229 enabled to ensure this is handled correctly. This is very rarely
230 needed in SPL.
231
232config SYS_DEVICE_NULLDEV
233 bool "Enable a null device for stdio"
234 default y if SPLASH_SCREEN || SYS_STDIO_DEREGISTER
235 help
236 Enable creation of a "nulldev" stdio device. This allows silent
237 operation of the console by setting stdout to "nulldev". Enable
238 this to use a serial console under board control.
239
240endmenu
241
242menu "Logging"
243
244config LOG
245 bool "Enable logging support"
246 depends on DM
247 help
248 This enables support for logging of status and debug messages. These
249 can be displayed on the console, recorded in a memory buffer, or
250 discarded if not needed. Logging supports various categories and
251 levels of severity.
252
253if LOG
254
255config LOG_MAX_LEVEL
256 int "Maximum log level to record"
257 default 6
258 range 0 9
259 help
260 This selects the maximum log level that will be recorded. Any value
261 higher than this will be ignored. If possible log statements below
262 this level will be discarded at build time. Levels:
263
264 0 - emergency
265 1 - alert
266 2 - critical
267 3 - error
268 4 - warning
269 5 - note
270 6 - info
271 7 - debug
272 8 - debug content
273 9 - debug hardware I/O
274
275config LOG_DEFAULT_LEVEL
276 int "Default logging level to display"
277 default LOG_MAX_LEVEL
278 range 0 LOG_MAX_LEVEL
279 help
280 This is the default logging level set when U-Boot starts. It can
281 be adjusted later using the 'log level' command. Note that setting
282 this to a value above LOG_MAX_LEVEL will be ineffective, since the
283 higher levels are not compiled in to U-Boot.
284
285 0 - emergency
286 1 - alert
287 2 - critical
288 3 - error
289 4 - warning
290 5 - note
291 6 - info
292 7 - debug
293 8 - debug content
294 9 - debug hardware I/O
295
296config LOG_CONSOLE
297 bool "Allow log output to the console"
298 default y
299 help
300 Enables a log driver which writes log records to the console.
301 Generally the console is the serial port or LCD display. Only the
302 log message is shown - other details like level, category, file and
303 line number are omitted.
304
305config LOGF_FILE
306 bool "Show source file name in log messages by default"
307 help
308 Show the source file name in log messages by default. This value
309 can be overridden using the 'log format' command.
310
311config LOGF_LINE
312 bool "Show source line number in log messages by default"
313 help
314 Show the source line number in log messages by default. This value
315 can be overridden using the 'log format' command.
316
317config LOGF_FUNC
318 bool "Show function name in log messages by default"
319 help
320 Show the function name in log messages by default. This value can
321 be overridden using the 'log format' command.
322
323config LOGF_FUNC_PAD
324 int "Number of characters to use for function"
325 default 20
326 help
327 Sets the field width to use when showing the function. Set this to
328 a larger value if you have lots of long function names, and want
329 things to line up.
330
331config LOG_SYSLOG
332 bool "Log output to syslog server"
333 depends on NET
334 help
335 Enables a log driver which broadcasts log records via UDP port 514
336 to syslog servers.
337
338config SPL_LOG
339 bool "Enable logging support in SPL"
340 depends on LOG
341 help
342 This enables support for logging of status and debug messages. These
343 can be displayed on the console, recorded in a memory buffer, or
344 discarded if not needed. Logging supports various categories and
345 levels of severity.
346
347if SPL_LOG
348
349config SPL_LOG_MAX_LEVEL
350 int "Maximum log level to record in SPL"
351 depends on SPL_LOG
352 default 3
353 range 0 9
354 help
355 This selects the maximum log level that will be recorded. Any value
356 higher than this will be ignored. If possible log statements below
357 this level will be discarded at build time. Levels:
358
359 0 - emergency
360 1 - alert
361 2 - critical
362 3 - error
363 4 - warning
364 5 - note
365 6 - info
366 7 - debug
367 8 - debug content
368 9 - debug hardware I/O
369
370config SPL_LOG_CONSOLE
371 bool "Allow log output to the console in SPL"
372 default y
373 help
374 Enables a log driver which writes log records to the console.
375 Generally the console is the serial port or LCD display. Only the
376 log message is shown - other details like level, category, file and
377 line number are omitted.
378
379endif
380
381config TPL_LOG
382 bool "Enable logging support in TPL"
383 depends on LOG
384 help
385 This enables support for logging of status and debug messages. These
386 can be displayed on the console, recorded in a memory buffer, or
387 discarded if not needed. Logging supports various categories and
388 levels of severity.
389
390if TPL_LOG
391
392config TPL_LOG_MAX_LEVEL
393 int "Maximum log level to record in TPL"
394 depends on TPL_LOG
395 default 3
396 range 0 9
397 help
398 This selects the maximum log level that will be recorded. Any value
399 higher than this will be ignored. If possible log statements below
400 this level will be discarded at build time. Levels:
401
402 0 - emergency
403 1 - alert
404 2 - critical
405 3 - error
406 4 - warning
407 5 - note
408 6 - info
409 7 - debug
410 8 - debug content
411 9 - debug hardware I/O
412
413config TPL_LOG_CONSOLE
414 bool "Allow log output to the console in TPL"
415 default y
416 help
417 Enables a log driver which writes log records to the console.
418 Generally the console is the serial port or LCD display. Only the
419 log message is shown - other details like level, category, file and
420 line number are omitted.
421
422endif
423
424config LOG_ERROR_RETURN
425 bool "Log all functions which return an error"
426 help
427 When an error is returned in U-Boot it is sometimes difficult to
428 figure out the root cause. For example, reading from SPI flash may
429 fail due to a problem in the SPI controller or due to the flash part
430 not returning the expected information. This option changes
431 log_ret() to log any errors it sees. With this option disabled,
432 log_ret() is a nop.
433
434 You can add log_ret() to all functions which return an error code.
435
436config LOG_TEST
437 bool "Provide a test for logging"
438 depends on UNIT_TEST
439 default y if SANDBOX
440 help
441 This enables a 'log test' command to test logging. It is normally
442 executed from a pytest and simply outputs logging information
443 in various different ways to test that the logging system works
444 correctly with various settings.
445
446endif
447
448endmenu
449
450menu "Init options"
451
452config BOARD_TYPES
453 bool "Call get_board_type() to get and display the board type"
454 help
455 If this option is enabled, checkboard() will call get_board_type()
456 to get a string containing the board type and this will be
457 displayed immediately after the model is shown on the console
458 early in boot.
459
460config DISPLAY_CPUINFO
461 bool "Display information about the CPU during start up"
462 default y if ARC|| ARM || NIOS2 || X86 || XTENSA || M68K
463 help
464 Display information about the CPU that U-Boot is running on
465 when U-Boot starts up. The function print_cpuinfo() is called
466 to do this.
467
468config DISPLAY_BOARDINFO
469 bool "Display information about the board during early start up"
470 default y if ARC || ARM || M68K || MIPS || PPC || SANDBOX || XTENSA
471 help
472 Display information about the board that U-Boot is running on
473 when U-Boot starts up. The board function checkboard() is called
474 to do this.
475
476config DISPLAY_BOARDINFO_LATE
477 bool "Display information about the board during late start up"
478 help
479 Display information about the board that U-Boot is running on after
480 the relocation phase. The board function checkboard() is called to do
481 this.
482
483menu "Start-up hooks"
484
485config ARCH_EARLY_INIT_R
486 bool "Call arch-specific init soon after relocation"
487 help
488 With this option U-Boot will call arch_early_init_r() soon after
489 relocation. Driver model is running by this point, and the cache
490 is on. Note that board_early_init_r() is called first, if
491 enabled. This can be used to set up architecture-specific devices.
492
493config ARCH_MISC_INIT
494 bool "Call arch-specific init after relocation, when console is ready"
495 help
496 With this option U-Boot will call arch_misc_init() after
497 relocation to allow miscellaneous arch-dependent initialisation
498 to be performed. This function should be defined by the board
499 and will be called after the console is set up, after relocation.
500
501config BOARD_EARLY_INIT_F
502 bool "Call board-specific init before relocation"
503 help
504 Some boards need to perform initialisation as soon as possible
505 after boot. With this option, U-Boot calls board_early_init_f()
506 after driver model is ready in the pre-relocation init sequence.
507 Note that the normal serial console is not yet set up, but the
508 debug UART will be available if enabled.
509
510config BOARD_EARLY_INIT_R
511 bool "Call board-specific init after relocation"
512 help
513 Some boards need to perform initialisation as directly after
514 relocation. With this option, U-Boot calls board_early_init_r()
515 in the post-relocation init sequence.
516
517config BOARD_LATE_INIT
518 bool "Execute Board late init"
519 help
520 Sometimes board require some initialization code that might
521 require once the actual init done, example saving board specific env,
522 boot-modes etc. which eventually done at late.
523
524 So this config enable the late init code with the help of board_late_init
525 function which should defined on respective boards.
526
527config LAST_STAGE_INIT
528 bool "Call board-specific as last setup step"
529 help
530 Some boards need to perform initialisation immediately before control
531 is passed to the command-line interpreter (e.g. for initializations
532 that depend on later phases in the init sequence). With this option,
533 U-Boot calls last_stage_init() before the command-line interpreter is
534 started.
535
536config MISC_INIT_F
537 bool "Execute pre-relocation misc init"
538 help
539 Enabling this option calls the 'misc_init_f' function in the init
540 sequence just before DRAM is inited.
541
542config MISC_INIT_R
543 bool "Execute Misc Init"
544 default y if ARCH_KEYSTONE || ARCH_SUNXI || MPC85xx
545 default y if ARCH_OMAP2PLUS && !AM33XX
546 help
547 Enabling this option calls 'misc_init_r' function
548
549config ID_EEPROM
550 bool "Enable I2C connected system identifier EEPROM"
551 help
552 A number of different systems and vendors enable a vendor-specified
553 EEPROM that contains various identifying features.
554
555config PCI_INIT_R
556 bool "Enumerate PCI buses during init"
557 depends on PCI
558 help
559 With this option U-Boot will call pci_init() soon after relocation,
560 which will enumerate PCI buses. This is needed, for instance, in the
561 case of DM PCI-based Ethernet devices, which will not be detected
562 without having the enumeration performed earlier.
563
564endmenu
565
566endmenu
567
568menu "Security support"
569
570config HASH
571 bool
572 help
573 This provides a way to hash data in memory using various supported
574 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
575 and the algorithms it supports are defined in common/hash.c. See
576 also CMD_HASH for command-line access.
577
578config AVB_VERIFY
579 bool "Build Android Verified Boot operations"
580 depends on LIBAVB
581 depends on MMC
582 depends on PARTITION_UUIDS
583 help
584 This option enables compilation of bootloader-dependent operations,
585 used by Android Verified Boot 2.0 library (libavb). Includes:
586 * Helpers to process strings in order to build OS bootargs.
587 * Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
588 * Helpers to alloc/init/free avb ops.
589
590if AVB_VERIFY
591
592config AVB_BUF_ADDR
593 hex "Define AVB buffer address"
594 default FASTBOOT_BUF_ADDR
595 help
596 AVB requires a buffer for memory transactions. This variable defines the
597 buffer address.
598
599config AVB_BUF_SIZE
600 hex "Define AVB buffer SIZE"
601 default FASTBOOT_BUF_SIZE
602 help
603 AVB requires a buffer for memory transactions. This variable defines the
604 buffer size.
605
606endif
607
608config SCP03
609 bool "Build SCP03 - Secure Channel Protocol O3 - controls"
610 depends on OPTEE || SANDBOX
611 depends on TEE
612 help
613 This option allows U-Boot to enable and or provision SCP03 on an OPTEE
614 controlled Secured Element.
615
616config SPL_HASH
617 bool
618 help
619 This provides a way to hash data in memory using various supported
620 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
621 and the algorithms it supports are defined in common/hash.c. See
622 also CMD_HASH for command-line access.
623
624config TPL_HASH
625 bool
626 help
627 This provides a way to hash data in memory using various supported
628 algorithms (such as SHA1, MD5, CRC32). The API is defined in hash.h
629 and the algorithms it supports are defined in common/hash.c. See
630 also CMD_HASH for command-line access.
631
632config STACKPROTECTOR
633 bool "Stack Protector buffer overflow detection"
634 help
635 Enable stack smash detection through compiler's stack-protector
636 canary logic
637
638config SPL_STACKPROTECTOR
639 bool "Stack Protector buffer overflow detection for SPL"
640 depends on STACKPROTECTOR && SPL
641
642config TPL_STACKPROTECTOR
643 bool "Stack Protector buffer overflow detection for TPL"
644 depends on STACKPROTECTOR && TPL
645
646endmenu
647
648menu "Update support"
649
650config UPDATE_COMMON
651 bool
652 select DFU_WRITE_ALT
653
654config UPDATE_TFTP
655 bool "Auto-update using fitImage via TFTP"
656 depends on FIT
657 select UPDATE_COMMON
658 help
659 This option allows performing update of NOR with data in fitImage
660 sent via TFTP boot.
661
662config UPDATE_TFTP_CNT_MAX
663 int "The number of connection retries during auto-update"
664 default 0
665 depends on UPDATE_TFTP
666
667config UPDATE_TFTP_MSEC_MAX
668 int "Delay in mSec to wait for the TFTP server during auto-update"
669 default 100
670 depends on UPDATE_TFTP
671
672config UPDATE_FIT
673 bool "Firmware update using fitImage"
674 depends on FIT
675 depends on DFU
676 select UPDATE_COMMON
677 help
678 This option allows performing update of DFU-capable storage with
679 data in fitImage.
680
681config ANDROID_AB
682 bool "Android A/B updates"
683 help
684 If enabled, adds support for the new Android A/B update model. This
685 allows the bootloader to select which slot to boot from based on the
686 information provided by userspace via the Android boot_ctrl HAL. This
687 allows a bootloader to try a new version of the system but roll back
688 to previous version if the new one didn't boot all the way.
689
690endmenu
691
692menu "Blob list"
693
694config BLOBLIST
695 bool "Support for a bloblist"
696 help
697 This enables support for a bloblist in U-Boot, which can be passed
698 from TPL to SPL to U-Boot proper (and potentially to Linux). The
699 blob list supports multiple binary blobs of data, each with a tag,
700 so that different U-Boot components can store data which can survive
701 through to the next stage of the boot.
702
703config SPL_BLOBLIST
704 bool "Support for a bloblist in SPL"
705 depends on BLOBLIST
706 default y if SPL
707 help
708 This enables a bloblist in SPL. If this is the first part of U-Boot
709 to run, then the bloblist is set up in SPL and passed to U-Boot
710 proper. If TPL also has a bloblist, then SPL uses the one from there.
711
712config TPL_BLOBLIST
713 bool "Support for a bloblist in TPL"
714 depends on BLOBLIST
715 default y if TPL
716 help
717 This enables a bloblist in TPL. The bloblist is set up in TPL and
718 passed to SPL and U-Boot proper.
719
720config BLOBLIST_SIZE
721 hex "Size of bloblist"
722 depends on BLOBLIST
723 default 0x400
724 help
725 Sets the size of the bloblist in bytes. This must include all
726 overhead (alignment, bloblist header, record header). The bloblist
727 is set up in the first part of U-Boot to run (TPL, SPL or U-Boot
728 proper), and this sane bloblist is used for subsequent stages.
729
730config BLOBLIST_ADDR
731 hex "Address of bloblist"
732 depends on BLOBLIST
733 default 0xc000 if SANDBOX
734 help
735 Sets the address of the bloblist, set up by the first part of U-Boot
736 which runs. Subsequent U-Boot stages typically use the same address.
737
738config BLOBLIST_SIZE_RELOC
739 hex "Size of bloblist after relocation"
740 depends on BLOBLIST
741 default BLOBLIST_SIZE
742 help
743 Sets the size of the bloblist in bytes after relocation. Since U-Boot
744 has a lot more memory available then, it is possible to use a larger
745 size than the one set up by SPL. This bloblist is set up during the
746 relocation process.
747
748endmenu
749
750source "common/spl/Kconfig"
751
752config IMAGE_SIGN_INFO
753 bool
754 select SHA1
755 select SHA256
756 help
757 Enable image_sign_info helper functions.
758
759if IMAGE_SIGN_INFO
760
761config SPL_IMAGE_SIGN_INFO
762 bool
763 select SHA1
764 select SHA256
765 help
766 Enable image_sign_info helper functions in SPL.
767
768endif
769
