1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
59 string "Command execution tracer"
63 This option enables the possiblity to print all commands before
64 executing them and after all variables are evaluated (similar
65 to Bash's xtrace/'set -x' feature).
66 To enable the tracer a variable "xtrace" needs to be defined in
69 menu "Autoboot options"
75 This enables the autoboot. See doc/README.autoboot for detail.
78 bool "Stop autobooting via specific input key / string"
81 This option enables stopping (aborting) of the automatic
82 boot feature only by issuing a specific input key or
83 string. If not enabled, any input key will abort the
84 U-Boot automatic booting process and bring the device
85 to the U-Boot prompt for user input.
87 config AUTOBOOT_PROMPT
88 string "Autoboot stop prompt"
89 depends on AUTOBOOT_KEYED
90 default "Autoboot in %d seconds\\n"
92 This string is displayed before the boot delay selected by
93 CONFIG_BOOTDELAY starts. If it is not defined there is no
94 output indicating that autoboot is in progress.
96 Note that this define is used as the (only) argument to a
97 printf() call, so it may contain '%' format specifications,
98 provided that it also includes, sepearated by commas exactly
99 like in a printf statement, the required arguments. It is
100 the responsibility of the user to select only such arguments
101 that are valid in the given context.
103 config AUTOBOOT_ENCRYPTION
104 bool "Enable encryption in autoboot stopping"
105 depends on AUTOBOOT_KEYED
107 This option allows a string to be entered into U-Boot to stop the
108 autoboot. The string itself is hashed and compared against the hash
109 in the environment variable 'bootstopkeysha256'. If it matches then
110 boot stops and a command-line prompt is presented.
112 This provides a way to ship a secure production device which can also
113 be accessed at the U-Boot command line.
115 config AUTOBOOT_DELAY_STR
116 string "Delay autobooting via specific input key / string"
117 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
119 This option delays the automatic boot feature by issuing
120 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
121 or the environment variable "bootdelaykey" is specified
122 and this string is received from console input before
123 autoboot starts booting, U-Boot gives a command prompt. The
124 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
125 used, otherwise it never times out.
127 config AUTOBOOT_STOP_STR
128 string "Stop autobooting via specific input key / string"
129 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
131 This option enables stopping (aborting) of the automatic
132 boot feature only by issuing a specific input key or
133 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
134 variable "bootstopkey" is specified and this string is
135 received from console input before autoboot starts booting,
136 U-Boot gives a command prompt. The U-Boot prompt never
137 times out, even if CONFIG_BOOT_RETRY_TIME is used.
139 config AUTOBOOT_KEYED_CTRLC
140 bool "Enable Ctrl-C autoboot interruption"
141 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
144 This option allows for the boot sequence to be interrupted
145 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
146 Setting this variable provides an escape sequence from the
147 limited "password" strings.
149 config AUTOBOOT_STOP_STR_SHA256
150 string "Stop autobooting via SHA256 encrypted password"
151 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
153 This option adds the feature to only stop the autobooting,
154 and therefore boot into the U-Boot prompt, when the input
155 string / password matches a values that is encypted via
156 a SHA256 hash and saved in the environment.
158 config AUTOBOOT_USE_MENUKEY
159 bool "Allow a specify key to run a menu from the environment"
160 depends on !AUTOBOOT_KEYED
162 If a specific key is pressed to stop autoboot, then the commands in
163 the environment variable 'menucmd' are executed before boot starts.
165 config AUTOBOOT_MENUKEY
166 int "ASCII value of boot key to show a menu"
168 depends on AUTOBOOT_USE_MENUKEY
170 If this key is pressed to stop autoboot, then the commands in the
171 environment variable 'menucmd' will be executed before boot starts.
172 For example, 33 means "!" in ASCII, so pressing ! at boot would take
175 config AUTOBOOT_MENU_SHOW
176 bool "Show a menu on boot"
177 depends on CMD_BOOTMENU
179 This enables the boot menu, controlled by environment variables
180 defined by the board. The menu starts after running the 'preboot'
181 environmnent variable (if enabled) and before handling the boot delay.
182 See README.bootmenu for more details.
197 List and dump ACPI tables. ACPI (Advanced Configuration and Power
198 Interface) is used mostly on x86 for providing information to the
199 Operating System about devices in the system. The tables are set up
200 by the firmware, typically U-Boot but possibly an earlier firmware
201 module, if U-Boot is chain-loaded from something else. ACPI tables
202 can also include code, to perform hardware-specific tasks required
203 by the Operating Systems. This allows some amount of separation
204 between the firmware and OS, and is particularly useful when you
205 want to make hardware changes without the OS needing to be adjusted.
218 Print ".config" contents.
220 If this option is enabled, the ".config" file contents are embedded
221 in the U-Boot image and can be printed on the console by the "config"
222 command. This provides information of which options are enabled on
229 Print console devices and information.
234 Print information about available CPUs. This normally shows the
235 number of CPUs, type (e.g. manufacturer, architecture, product or
236 internal name) and clock frequency. Other information may be
237 available depending on the CPU driver.
243 Print GPL license text
248 Provides access to the Intel Power-Management Controller (PMC) so
249 that its state can be examined. This does not currently support
250 changing the state but it is still useful for debugging and seeing
259 config CMD_TLV_EEPROM
261 depends on I2C_EEPROM
263 Display and program the system EEPROM data block in ONIE Tlvinfo
264 format. TLV stands for Type-Length-Value.
266 config SPL_CMD_TLV_EEPROM
267 bool "tlv_eeprom for SPL"
268 depends on SPL_I2C_EEPROM
269 select SPL_DRIVERS_MISC_SUPPORT
271 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
281 Run the command stored in the environment "bootcmd", i.e.
282 "bootd" does the same thing as "run bootcmd".
288 Boot an application image from the memory.
291 bool "Support booting UEFI FIT images"
292 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
295 Support booting UEFI FIT images via the bootm command.
300 Boot the Linux zImage
304 depends on ARM64 || RISCV
307 Boot an AArch64 Linux Kernel image from memory.
310 bool "Support booting Linux OS images"
311 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
314 Support booting the Linux kernel directly via a command such as bootm
318 bool "Support booting NetBSD (non-EFI) loader images"
322 Support booting NetBSD via the bootm command.
324 config BOOTM_OPENRTOS
325 bool "Support booting OPENRTOS / FreeRTOS images"
328 Support booting OPENRTOS / FreeRTOS via the bootm command.
331 bool "Support booting Enea OSE images"
332 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
335 Support booting Enea OSE images via the bootm command.
338 bool "Support booting Plan9 OS images"
342 Support booting Plan9 images via the bootm command.
345 bool "Support booting RTEMS OS images"
349 Support booting RTEMS images via the bootm command.
352 bool "Support booting VxWorks OS images"
356 Support booting VxWorks images via the bootm command.
360 depends on EFI_LOADER
363 Boot an EFI image from memory.
365 config CMD_BOOTEFI_HELLO_COMPILE
366 bool "Compile a standard EFI hello world binary for testing"
367 depends on CMD_BOOTEFI && !CPU_V7M
370 This compiles a standard EFI hello world application with U-Boot so
371 that it can be used with the test/py testing framework. This is useful
372 for testing that EFI is working at a basic level, and for bringing
373 up EFI support on a new architecture.
375 No additional space will be required in the resulting U-Boot binary
376 when this option is enabled.
378 config CMD_BOOTEFI_HELLO
379 bool "Allow booting a standard EFI hello world for testing"
380 depends on CMD_BOOTEFI_HELLO_COMPILE
382 This adds a standard EFI hello world application to U-Boot so that
383 it can be used with the 'bootefi hello' command. This is useful
384 for testing that EFI is working at a basic level, and for bringing
385 up EFI support on a new architecture.
387 source lib/efi_selftest/Kconfig
393 Add an ANSI terminal boot menu command.
398 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
399 image into RAM, dump image structure information, etc. Those dtb/dtbo
400 files should be merged in one dtb further, which needs to be passed to
401 the kernel, as part of a boot process.
405 depends on ANDROID_BOOT_IMAGE
407 Android Boot Image manipulation commands. Allows one to extract
408 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
409 obtain corresponding meta-information from boot.img.
411 See doc/android/boot-image.rst for details.
414 bool "bootelf, bootvx"
418 Boot an ELF/vxWorks image from the memory.
421 bool "Flattened Device Tree utility commands"
425 Do FDT related setup before booting into the Operating System.
431 Start an application at a given address.
437 Run the command in the given environment variable.
443 Print header information for application image.
448 List all images found in flash
454 Extract a part of a multi-image.
457 bool "spl export - Export boot information for Falcon boot"
460 Falcon mode allows booting directly from SPL into an Operating
461 System such as Linux, thus skipping U-Boot proper. See
462 doc/README.falcon for full information about how to use this
465 config CMD_SPL_NAND_OFS
466 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
467 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
470 This provides the offset of the command line arguments for Linux
471 when booting from NAND in Falcon mode. See doc/README.falcon
472 for full information about how to use this option (and also see
473 board/gateworks/gw_ventana/README for an example).
475 config CMD_SPL_NOR_OFS
476 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
477 depends on CMD_SPL && SPL_NOR_SUPPORT
480 This provides the offset of the command line arguments or dtb for
481 Linux when booting from NOR in Falcon mode.
483 config CMD_SPL_WRITE_SIZE
484 hex "Size of argument area"
488 This provides the size of the command-line argument area in NAND
489 flash used by Falcon-mode boot. See the documentation until CMD_SPL
493 bool "fitImage update command"
494 depends on UPDATE_TFTP
496 Implements the 'fitupd' command, which allows to automatically
497 store software updates present on a TFTP server in NOR Flash
499 config CMD_THOR_DOWNLOAD
500 bool "thor - TIZEN 'thor' download"
503 Implements the 'thor' download protocol. This is a way of
504 downloading a software update over USB from an attached host.
505 There is no documentation about this within the U-Boot source code
506 but you should be able to find something on the interwebs.
509 bool "zboot - x86 boot command"
511 With x86 machines it is common to boot a bzImage file which
512 contains both a kernel and a setup.bin file. The latter includes
513 configuration information from the dark ages which x86 boards still
514 need to pick things out of.
516 Consider using FIT in preference to this since it supports directly
517 booting both 32- and 64-bit kernels, as well as secure boot.
518 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
522 menu "Environment commands"
525 bool "ask for env variable"
527 Ask for environment variable
545 Edit environment variable.
550 Allow for searching environment variables
556 Save all environment variables into the compiled-in persistent
562 depends on CMD_SAVEENV
564 Erase environment variables from the compiled-in persistent
567 config CMD_ENV_EXISTS
571 Check if a variable is defined in the environment for use in
574 config CMD_ENV_CALLBACK
575 bool "env callbacks - print callbacks and their associated variables"
577 Some environment variable have callbacks defined by
578 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
579 For example changing "baudrate" adjust the serial baud rate. This
580 command lists the currently defined callbacks.
583 bool "env flags -print variables that have non-default flags"
585 Some environment variables have special flags that control their
586 behaviour. For example, serial# can only be written once and cannot
587 be deleted. This command shows the variables that have special
590 config CMD_NVEDIT_EFI
591 bool "env [set|print] -e - set/print UEFI variables"
592 depends on EFI_LOADER
595 UEFI variables are encoded as some form of U-Boot variables.
596 If enabled, we are allowed to set/print UEFI variables using
597 "env" command with "-e" option without knowing details.
599 config CMD_NVEDIT_INFO
600 bool "env info - print or evaluate environment information"
602 Print environment information:
603 - env_valid : is environment valid
604 - env_ready : is environment imported into hash table
605 - env_use_default : is default environment used
607 This command can be optionally used for evaluation in scripts:
608 [-d] : evaluate whether default environment is used
609 [-p] : evaluate whether environment can be persisted
610 The result of multiple evaluations will be combined with AND.
614 menu "Memory commands"
619 Compute binary operations (xor, or, and) of byte arrays of arbitrary
620 size from memory and store the result in memory or the environment.
633 Add -v option to verify data against a crc32 checksum.
636 bool "eeprom - EEPROM subsystem"
638 (deprecated, needs conversion to driver model)
639 Provides commands to read and write EEPROM (Electrically Erasable
640 Programmable Read Only Memory) chips that are connected over an
643 config CMD_EEPROM_LAYOUT
644 bool "Enable layout-aware eeprom commands"
645 depends on CMD_EEPROM
647 (deprecated, needs conversion to driver model)
648 When enabled, additional eeprom sub-commands become available.
650 eeprom print - prints the contents of the eeprom in a human-readable
651 way (eeprom layout fields, and data formatted to be fit for human
654 eeprom update - allows user to update eeprom fields by specifying
655 the field name, and providing the new data in a human readable format
656 (same format as displayed by the eeprom print command).
658 Both commands can either auto detect the layout, or be told which
662 __weak int parse_layout_version(char *str)
663 - override to provide your own layout name parsing
664 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
666 - override to setup the layout metadata based on the version
667 __weak int eeprom_layout_detect(unsigned char *data)
668 - override to provide your own algorithm for detecting layout
671 - contains various printing and updating functions for common
672 types of eeprom fields. Can be used for defining
675 config EEPROM_LAYOUT_HELP_STRING
676 string "Tells user what layout names are supported"
677 depends on CMD_EEPROM_LAYOUT
678 default "<not defined>"
680 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
686 Infinite write loop on address range
693 Compute MD5 checksum.
698 depends on CMD_MD5SUM
700 Add -v option to verify data against an MD5 checksum.
705 Display memory information.
708 bool "md, mm, nm, mw, cp, cmp, base, loop"
713 mm - memory modify (auto-incrementing address)
714 nm - memory modify (constant address)
715 mw - memory write (fill)
718 base - print or set address offset
719 loop - initialize loop on address range
722 bool "Enable cyclic md/mw commands"
723 depends on CMD_MEMORY
725 Add the "mdc" and "mwc" memory commands. These are cyclic
730 This command will print 4 bytes (10,11,12,13) each 500 ms.
732 => mwc.l 100 12345678 10
733 This command will write 12345678 to address 100 all 10 ms.
738 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
740 random - fill memory with random data
745 Simple RAM read/write test.
749 config SYS_ALT_MEMTEST
750 bool "Alternative test"
752 Use a more complete alternative memory test.
754 config SYS_MEMTEST_START
755 hex "default start address for mtest"
758 This is the default start address for mtest for simple read/write
759 test. If no arguments are given to mtest, default address is used
762 config SYS_MEMTEST_END
763 hex "default end address for mtest"
766 This is the default end address for mtest for simple read/write
767 test. If no arguments are given to mtest, default address is used
776 Compute SHA1 checksum.
778 config SHA1SUM_VERIFY
780 depends on CMD_SHA1SUM
782 Add -v option to verify data against a SHA1 checksum.
785 bool "strings - display strings in memory"
787 This works similarly to the Unix 'strings' command except that it
788 works with a memory range. String of printable characters found
789 within the range are displayed. The minimum number of characters
790 for a sequence to be considered a string can be provided.
794 menu "Compression commands"
798 default y if CMD_BOOTI
801 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
806 default y if CMD_BOOTI
809 Support decompressing an LZ4 image from memory region.
813 default y if CMD_BOOTI
816 Uncompress a zip-compressed memory region.
820 select GZIP_COMPRESSED
822 Compress a memory region with zlib deflate method.
826 menu "Device access commands"
829 #depends on FLASH_CFI_DRIVER
832 ARM Ltd reference designs flash partition access
835 bool "adc - Access Analog to Digital Converters info and data"
839 Shows ADC device info and permit printing one-shot analog converted
840 data from a named Analog to Digital Converter.
845 depends on PARTITIONS
847 Read/modify/write the fields of Bootloader Control Block, usually
848 stored on the flash "misc" partition with its structure defined in:
849 https://android.googlesource.com/platform/bootable/recovery/+/master/
850 bootloader_message/include/bootloader_message/bootloader_message.h
852 Some real-life use-cases include (but are not limited to):
853 - Determine the "boot reason" (and act accordingly):
854 https://source.android.com/devices/bootloader/boot-reason
855 - Get/pass a list of commands from/to recovery:
856 https://android.googlesource.com/platform/bootable/recovery
857 - Inspect/dump the contents of the BCB fields
860 bool "bind/unbind - Bind or unbind a device to/from a driver"
863 Bind or unbind a device to/from a driver from the command line.
864 This is useful in situations where a device may be handled by several
865 drivers. For example, this can be used to bind a UDC to the usb ether
866 gadget driver from the command line.
869 bool "clk - Show clock frequencies"
872 Shows clock frequences by calling a sock_clk_dump() hook function.
873 This is depreated in favour of using the CLK uclass and accessing
874 clock values from associated drivers. However currently no command
878 bool "demo - Demonstration commands for driver model"
881 Provides a 'demo' command which can be used to play around with
882 driver model. To use this properly you will need to enable one or
883 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
884 Otherwise you will always get an empty list of devices. The demo
885 devices are defined in the sandbox device tree, so the easiest
886 option is to use sandbox and pass the -d point to sandbox's
893 Enables the command "dfu" which is used to have U-Boot create a DFU
894 class device via USB. This command requires that the "dfu_alt_info"
895 environment variable be set and define the alt settings to expose to
899 bool "dm - Access to driver model information"
902 Provides access to driver model data structures and information,
903 such as a list of devices, list of uclasses and the state of each
904 device (e.g. activated). This is not required for operation, but
905 can be useful to see the state of driver model for debugging or
909 bool "fastboot - Android fastboot support"
912 This enables the command "fastboot" which enables the Android
913 fastboot mode for the platform. Fastboot is a protocol for
914 downloading images, flashing and device control used on
915 Android devices. Fastboot requires either the network stack
916 enabled or support for acting as a USB device.
918 See doc/android/fastboot.rst for more information.
921 bool "flinfo, erase, protect"
923 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
926 flinfo - print FLASH memory information
928 protect - enable or disable FLASH write protection
937 config CMD_FPGA_LOADBP
938 bool "fpga loadbp - load partial bitstream (Xilinx only)"
941 Supports loading an FPGA device from a bitstream buffer containing
944 config CMD_FPGA_LOADFS
945 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
948 Supports loading an FPGA device from a FAT filesystem.
950 config CMD_FPGA_LOADMK
951 bool "fpga loadmk - load bitstream from image"
954 Supports loading an FPGA device from a image generated by mkimage.
956 config CMD_FPGA_LOADP
957 bool "fpga loadp - load partial bitstream"
960 Supports loading an FPGA device from a bitstream buffer containing
963 config CMD_FPGA_LOAD_SECURE
964 bool "fpga loads - loads secure bitstreams (Xilinx only)"
967 Enables the fpga loads command which is used to load secure
968 (authenticated or encrypted or both) bitstreams on to FPGA.
971 bool "fpgad - dump FPGA registers"
973 (legacy, needs conversion to driver model)
974 Provides a way to dump FPGA registers by calling the board-specific
975 fpga_get_reg() function. This functions similarly to the 'md'
979 bool "fuse - support for the fuse subssystem"
981 (deprecated - needs conversion to driver model)
982 This allows reading, sensing, programming or overriding fuses
983 which control the behaviour of the device. The command uses the
992 bool "GPT (GUID Partition Table) command"
994 select HAVE_BLOCK_DEVICE
995 select PARTITION_UUIDS
998 Enable the 'gpt' command to ready and write GPT style partition
1002 bool "GPT Random UUID generation"
1005 Enable the generation of partitions with random UUIDs if none
1008 config CMD_GPT_RENAME
1009 bool "GPT partition renaming commands"
1012 Enables the 'gpt' command to interchange names on two GPT
1013 partitions via the 'gpt swap' command or to rename single
1014 partitions via the 'rename' command.
1017 bool "ide - Support for IDE drivers"
1020 Provides an 'ide' command which allows accessing the IDE drive,
1021 reseting the IDE interface, printing the partition table and
1022 geting device info. It also enables the 'diskboot' command which
1023 permits booting from an IDE drive.
1026 bool "io - Support for performing I/O accesses"
1028 Provides an 'iod' command to display I/O space and an 'iow' command
1029 to write values to the I/O space. This can be useful for manually
1030 checking the state of devices during boot when debugging device
1034 bool "iotrace - Support for tracing I/O activity"
1036 Provides an 'iotrace' command which supports recording I/O reads and
1037 writes in a trace buffer in memory . It also maintains a checksum
1038 of the trace records (even if space is exhausted) so that the
1039 sequence of I/O accesses can be verified.
1041 When debugging drivers it is useful to see what I/O accesses were
1042 done and in what order.
1044 Even if the individual accesses are of little interest it can be
1045 useful to verify that the access pattern is consistent each time
1046 an operation is performed. In this case a checksum can be used to
1047 characterise the operation of a driver. The checksum can be compared
1048 across different runs of the operation to verify that the driver is
1051 In particular, when performing major refactoring of the driver, where
1052 the access pattern should not change, the checksum provides assurance
1053 that the refactoring work has not broken the driver.
1055 This works by sneaking into the io.h heder for an architecture and
1056 redirecting I/O accesses through iotrace's tracing mechanism.
1058 For now no commands are provided to examine the trace buffer. The
1059 format is fairly simple, so 'md' is a reasonable substitute.
1061 Note: The checksum feature is only useful for I/O regions where the
1062 contents do not change outside of software control. Where this is not
1063 suitable you can fall back to manually comparing the addresses. It
1064 might be useful to enhance tracing to only checksum the accesses and
1065 not the data read/written.
1075 bool "w1 - Support for Dallas 1-Wire protocol"
1077 Dallas 1-wire protocol support
1083 Load a binary file over serial line.
1089 Load an S-Record file over serial line
1094 MMC memory mapped support.
1098 config CMD_BKOPS_ENABLE
1099 bool "mmc bkops enable"
1103 Enable command for setting manual background operations handshake
1104 on a eMMC device. The feature is optionally available on eMMC devices
1105 conforming to standard >= 4.41.
1108 bool "Enable support for RPMB in the mmc command"
1109 depends on SUPPORT_EMMC_RPMB
1111 Enable the commands for reading, writing and programming the
1112 key for the Replay Protection Memory Block partition in eMMC.
1114 config CMD_MMC_SWRITE
1116 depends on MMC_WRITE
1119 Enable support for the "mmc swrite" command to write Android sparse
1127 select MTD_PARTITIONS
1129 MTD commands support.
1133 default y if NAND_SUNXI
1134 depends on MTD_RAW_NAND
1139 config CMD_NAND_TRIMFFS
1140 bool "nand write.trimffs"
1141 default y if ARCH_SUNXI
1143 Allows one to skip empty pages when flashing something on a NAND.
1145 config CMD_NAND_LOCK_UNLOCK
1146 bool "nand lock/unlock"
1148 NAND locking support.
1150 config CMD_NAND_TORTURE
1153 NAND torture support.
1162 NVM Express device support
1165 bool "onenand - access to onenand device"
1168 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1169 various useful features. This command allows reading, writing,
1170 and erasing blocks. It allso provides a way to show and change
1171 bad blocks, and test the device.
1176 Enable the 'osd' command which allows to query information from and
1177 write text data to a on-screen display (OSD) device; a virtual device
1178 associated with a display capable of displaying a text overlay on the
1179 display it's associated with..
1183 select HAVE_BLOCK_DEVICE
1184 select PARTITION_UUIDS
1186 Read and display information about the partition table on
1190 bool "pci - Access PCI devices"
1192 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1193 used on some devices to allow the CPU to communicate with its
1194 peripherals. Sub-commands allow bus enumeration, displaying and
1195 changing configuration space and a few other features.
1198 bool "pinmux - show pins muxing"
1199 default y if PINCTRL
1201 Parse all available pin-controllers and show pins muxing. This
1202 is useful for debug purpoer to check the pin muxing and to know if
1203 a pin is configured as a GPIO or as an alternate function.
1208 Poweroff/Shutdown the system
1211 bool "read - Read binary data from a partition"
1213 Provides low-level access to the data in a partition.
1215 config CMD_REMOTEPROC
1217 depends on REMOTEPROC
1219 Support for Remote Processor control
1222 bool "sata - Access SATA subsystem"
1225 SATA (Serial Advanced Technology Attachment) is a serial bus
1226 standard for connecting to hard drives and other storage devices.
1227 This command provides information about attached devices and allows
1228 reading, writing and other operations.
1230 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1231 Attachment, where AT refers to an IBM AT (Advanced Technology)
1232 computer released in 1984.
1235 bool "saves - Save a file over serial in S-Record format"
1237 Provides a way to save a binary file using the Motorola S-Record
1238 format over the serial line.
1241 bool "scsi - Access to SCSI devices"
1244 This provides a 'scsi' command which provides access to SCSI (Small
1245 Computer System Interface) devices. The command provides a way to
1246 scan the bus, reset the bus, read and write data and get information
1250 bool "sdram - Print SDRAM configuration information"
1252 Provides information about attached SDRAM. This assumed that the
1253 SDRAM has an EEPROM with information that can be read using the
1254 I2C bus. This is only available on some boards.
1258 depends on DM_SPI_FLASH || SPI_FLASH
1259 default y if DM_SPI_FLASH
1264 bool "sf test - Allow testing of SPI flash"
1267 Provides a way to test that SPI flash is working correctly. The
1268 test is destructive, in that an area of SPI flash must be provided
1269 for the test to use. Performance information is also provided,
1270 measuring the performance of reading, writing and erasing in
1271 Mbps (Million Bits Per Second). This value should approximately
1272 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1273 everything is working properly.
1276 bool "sspi - Command to access spi device"
1279 SPI utility command.
1281 config DEFAULT_SPI_BUS
1282 int "default spi bus used by sspi command"
1286 config DEFAULT_SPI_MODE
1287 hex "default spi mode used by sspi command (see include/spi.h)"
1292 bool "tsi148 - Command to access tsi148 device"
1294 This provides various sub-commands to initialise and configure the
1295 Turndra tsi148 device. See the command help for full details.
1298 bool "Enable UFS - Universal Flash Subsystem commands"
1301 "This provides commands to initialise and configure universal flash
1305 bool "universe - Command to set up the Turndra Universe controller"
1307 This allows setting up the VMEbus provided by this controller.
1308 See the command help for full details.
1312 select HAVE_BLOCK_DEVICE
1318 select USB_FUNCTION_SDP
1320 Enables the command "sdp" which is used to have U-Boot emulating the
1321 Serial Download Protocol (SDP) via USB.
1325 depends on USB_FUNCTION_ROCKUSB
1327 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1328 read/write info, image to/from devices. This enable rockusb command
1329 support to communication with rockusb device. for more detail about
1330 this command, please read doc/README.rockusb.
1332 config CMD_USB_MASS_STORAGE
1333 bool "UMS usb mass storage"
1334 select USB_FUNCTION_MASS_STORAGE
1336 USB mass storage support
1343 VirtIO block device support
1349 This provides commands to control the watchdog timer devices.
1355 Enable the command "axi" for accessing AXI (Advanced eXtensible
1356 Interface) busses, a on-chip interconnect specification for managing
1357 functional blocks in SoC designs, which is also often used in designs
1358 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1362 menu "Shell scripting commands"
1368 Echo args to console
1374 Return true/false on integer compare.
1380 Run script from memory
1386 Evaluate boolean and math expressions and store the result in an env
1388 Also supports loading the value at a memory location into a variable.
1389 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1393 menu "Android support commands"
1395 config CMD_AB_SELECT
1398 depends on ANDROID_AB
1400 On Android devices with more than one boot slot (multiple copies of
1401 the kernel and system images) this provides a command to select which
1402 slot should be used to boot from and register the boot attempt. This
1403 is used by the new A/B update model where one slot is updated in the
1404 background while running from the other slot.
1411 bool "Network commands"
1421 bootp - boot image via network using BOOTP/TFTP protocol
1425 depends on CMD_BOOTP
1427 Boot image via network using DHCP/TFTP protocol
1429 config BOOTP_BOOTPATH
1430 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1432 depends on CMD_BOOTP
1434 Even though the config is called BOOTP_BOOTPATH, it stores the
1435 path in the variable 'rootpath'.
1438 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1440 depends on CMD_BOOTP
1442 The primary DNS server is stored as 'dnsip'. If two servers are
1443 returned, you must set BOOTP_DNS2 to store that second server IP
1447 bool "Store 'dnsip2' from BOOTP/DHCP server"
1448 depends on BOOTP_DNS
1450 If a DHCP client requests the DNS server IP from a DHCP server,
1451 it is possible that more than one DNS serverip is offered to the
1452 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1453 server IP will be stored in the additional environment
1454 variable "dnsip2". The first DNS serverip is always
1455 stored in the variable "dnsip", when BOOTP_DNS is defined.
1457 config BOOTP_GATEWAY
1458 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1460 depends on CMD_BOOTP
1462 config BOOTP_HOSTNAME
1463 bool "Request & store 'hostname' from BOOTP/DHCP server"
1465 depends on CMD_BOOTP
1467 The name may or may not be qualified with the local domain name.
1469 config BOOTP_PREFER_SERVERIP
1470 bool "serverip variable takes precedent over DHCP server IP."
1471 depends on CMD_BOOTP
1473 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1475 With this option enabled, the 'serverip' variable in the environment
1476 takes precedence over DHCP server IP and will only be set by the DHCP
1477 server if not already set in the environment.
1479 config BOOTP_SUBNETMASK
1480 bool "Request & store 'netmask' from BOOTP/DHCP server"
1482 depends on CMD_BOOTP
1484 config BOOTP_NTPSERVER
1485 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1486 depends on CMD_BOOTP
1491 Selecting this will allow capturing all Ethernet packets and store
1492 them in physical memory in a PCAP formated file,
1493 later to be analyzed by PCAP reader application (IE. WireShark).
1496 bool "Send PXE client arch to BOOTP/DHCP server"
1498 depends on CMD_BOOTP && CMD_PXE
1500 Supported for ARM, ARM64, and x86 for now.
1502 config BOOTP_PXE_CLIENTARCH
1504 depends on BOOTP_PXE
1505 default 0x16 if ARM64
1509 config BOOTP_VCI_STRING
1511 depends on CMD_BOOTP
1512 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1513 default "U-Boot.armv8" if ARM64
1514 default "U-Boot.arm" if ARM
1521 tftpboot - boot image via network using TFTP protocol
1525 depends on CMD_TFTPBOOT
1527 TFTP put command, for uploading files to a server
1531 depends on CMD_TFTPBOOT
1533 Act as a TFTP server and boot the first received file
1535 config NET_TFTP_VARS
1536 bool "Control TFTP timeout and count through environment"
1537 depends on CMD_TFTPBOOT
1540 If set, allows controlling the TFTP timeout through the
1541 environment variable tftptimeout, and the TFTP maximum
1542 timeout count through the variable tftptimeoutcountmax.
1543 If unset, timeout and maximum are hard-defined as 1 second
1544 and 10 timouts per TFTP transfer.
1549 Boot image via network using RARP/TFTP protocol
1555 Boot image via network using NFS protocol.
1561 If set, allows 802.3(clause 22) MII Management functions interface access
1562 The management interface specified in Clause 22 provides
1563 a simple, two signal, serial interface to connect a
1564 Station Management entity and a managed PHY for providing access
1565 to management parameters and services.
1566 The interface is referred to as the MII management interface.
1572 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1573 The MDIO interface is orthogonal to the MII interface and extends
1574 it by adding access to more registers through indirect addressing.
1579 Send ICMP ECHO_REQUEST to network host
1584 Perform CDP network configuration
1589 Synchronize RTC via network
1594 Lookup the IP of a hostname
1596 config CMD_LINK_LOCAL
1600 Acquire a network IP address using the link-local protocol
1607 Allow control of L2 Ethernet switch commands. These are supported
1608 by the vsc9953 Ethernet driver at present. Sub-commands allow
1609 operations such as enabling / disabling a port and
1610 viewing/maintaining the filtering database (FDB)
1616 Boot image via network using PXE protocol
1621 Wait for wake-on-lan Magic Packet
1625 menu "Misc commands"
1628 bool "Enable 'bmp' command"
1629 depends on LCD || DM_VIDEO || VIDEO
1631 This provides a way to obtain information about a BMP-format image
1632 and to display it. BMP (which presumably stands for BitMaP) is a
1633 file format defined by Microsoft which supports images of various
1634 depths, formats and compression methods. Headers on the file
1635 determine the formats used. This command can be used by first loading
1636 the image into RAM, then using this command to look at it or display
1639 config CMD_BOOTCOUNT
1641 depends on BOOTCOUNT_LIMIT
1643 Enable the bootcount command, which allows interrogation and
1644 reset of the bootcounter.
1647 bool "Enable board-specific commands"
1649 (deprecated: instead, please define a Kconfig option for each command)
1651 Some boards have board-specific commands which are only enabled
1652 during developemnt and need to be turned off for production. This
1653 option provides a way to control this. The commands that are enabled
1654 vary depending on the board.
1656 config CMD_BLOCK_CACHE
1657 bool "blkcache - control and stats for block cache"
1658 depends on BLOCK_CACHE
1659 default y if BLOCK_CACHE
1661 Enable the blkcache command, which can be used to control the
1662 operation of the cache functions.
1663 This is most useful when fine-tuning the operation of the cache
1664 during development, but also allows the cache to be disabled when
1665 it might hurt performance (e.g. when using the ums command).
1668 bool "icache or dcache"
1670 Enable the "icache" and "dcache" commands
1672 config CMD_CONITRACE
1673 bool "conitrace - trace console input codes"
1675 Enable the 'conitrace' command which displays the codes received
1676 from the console input as hexadecimal numbers.
1679 bool "Enable clear screen command 'cls'"
1680 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1683 Enable the 'cls' command which clears the screen contents
1684 on video frame buffer.
1687 bool "efidebug - display/configure UEFI environment"
1688 depends on EFI_LOADER
1689 select EFI_DEVICE_PATH_TO_TEXT
1692 Enable the 'efidebug' command which provides a subset of UEFI
1693 shell utility with simplified functionality. It will be useful
1694 particularly for managing boot parameters as well as examining
1695 various EFI status for debugging.
1697 config CMD_EXCEPTION
1698 bool "exception - raise exception"
1699 depends on ARM || RISCV || X86
1701 Enable the 'exception' command which allows to raise an exception.
1708 Enable the 'led' command which allows for control of LEDs supported
1709 by the board. The LEDs can be listed with 'led list' and controlled
1710 with led on/off/togle/blink. Any LED drivers can be controlled with
1711 this command, e.g. led_gpio.
1718 Enable the 'date' command for getting/setting the time/date in RTC
1724 Run commands and summarize execution time.
1727 bool "gettime - read elapsed time"
1729 Enable the 'gettime' command which reads the elapsed time since
1730 U-Boot started running. This shows the time in seconds and
1731 milliseconds. See also the 'bootstage' command which provides more
1732 flexibility for boot timing.
1739 Print bytes from the hardware random number generator.
1741 # TODO: rename to CMD_SLEEP
1746 Delay execution for some time
1749 bool "support for multiprocessor"
1751 This provides an option to brinup
1752 different processors in multiprocessor
1758 Access the system timer.
1764 This provides basic access to the U-Boot's sound support. The main
1765 feature is to play a beep.
1767 sound init - set up sound system
1768 sound play - play a sound
1774 Boot image via local extlinux.conf file
1780 This provides access to the QEMU firmware interface. The main
1781 feature is to allow easy loading of files passed to qemu-system
1782 via -kernel / -initrd
1784 source "cmd/mvebu/Kconfig"
1787 bool "terminal - provides a way to attach a serial terminal"
1789 Provides a 'cu'-like serial terminal command. This can be used to
1790 access other serial ports from the system console. The terminal
1791 is very simple with no special processing of characters. As with
1792 cu, you can press ~. (tilde followed by period) to exit.
1795 bool "uuid, guid - generation of unique IDs"
1798 This enables two commands:
1800 uuid - generate random Universally Unique Identifier
1801 guid - generate Globally Unique Identifier based on random UUID
1803 The two commands are very similar except for the endianness of the
1808 source "cmd/ti/Kconfig"
1810 config CMD_BOOTSTAGE
1811 bool "Enable the 'bootstage' command"
1812 depends on BOOTSTAGE
1814 Add a 'bootstage' command which supports printing a report
1815 and un/stashing of bootstage data.
1817 menu "Power commands"
1819 bool "Enable Driver Model PMIC command"
1822 This is the pmic command, based on a driver model pmic's API.
1823 Command features are unchanged:
1824 - list - list pmic devices
1825 - pmic dev <id> - show or [set] operating pmic device (NEW)
1826 - pmic dump - dump registers
1827 - pmic read address - read byte of register at address
1828 - pmic write address - write byte to register at address
1829 The only one change for this command is 'dev' subcommand.
1831 config CMD_REGULATOR
1832 bool "Enable Driver Model REGULATOR command"
1833 depends on DM_REGULATOR
1835 This command is based on driver model regulator's API.
1836 User interface features:
1837 - list - list regulator devices
1838 - regulator dev <id> - show or [set] operating regulator device
1839 - regulator info - print constraints info
1840 - regulator status - print operating status
1841 - regulator value <val] <-f> - print/[set] voltage value [uV]
1842 - regulator current <val> - print/[set] current value [uA]
1843 - regulator mode <id> - print/[set] operating mode id
1844 - regulator enable - enable the regulator output
1845 - regulator disable - disable the regulator output
1847 The '-f' (force) option can be used for set the value which exceeds
1848 the limits, which are found in device-tree and are kept in regulator's
1849 uclass platdata structure.
1853 menu "Security commands"
1855 bool "Enable the 'aes' command"
1858 This provides a means to encrypt and decrypt data using the AES
1859 (Advanced Encryption Standard). This algorithm uses a symetric key
1860 and is widely used as a streaming cipher. Different key lengths are
1861 supported by the algorithm but this command only supports 128 bits
1865 bool "Enable the 'blob' command"
1867 This is used with the Freescale secure boot mechanism.
1869 Freescale's SEC block has built-in Blob Protocol which provides
1870 a method for protecting user-defined data across system power
1871 cycles. SEC block protects data in a data structure called a Blob,
1872 which provides both confidentiality and integrity protection.
1874 Encapsulating data as a blob
1875 Each time that the Blob Protocol is used to protect data, a
1876 different randomly generated key is used to encrypt the data.
1877 This random key is itself encrypted using a key which is derived
1878 from SoC's non-volatile secret key and a 16 bit Key identifier.
1879 The resulting encrypted key along with encrypted data is called a
1880 blob. The non-volatile secure key is available for use only during
1883 During decapsulation, the reverse process is performed to get back
1887 blob enc - encapsulating data as a cryptgraphic blob
1888 blob dec - decapsulating cryptgraphic blob to get the data
1892 blob enc src dst len km
1894 Encapsulate and create blob of data $len bytes long
1895 at address $src and store the result at address $dst.
1896 $km is the 16 byte key modifier is also required for
1897 generation/use as key for cryptographic operation. Key
1898 modifier should be 16 byte long.
1900 blob dec src dst len km
1902 Decapsulate the blob of data at address $src and
1903 store result of $len byte at addr $dst.
1904 $km is the 16 byte key modifier is also required for
1905 generation/use as key for cryptographic operation. Key
1906 modifier should be 16 byte long.
1909 bool "Support 'hash' command"
1912 This provides a way to hash data in memory using various supported
1913 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1914 saved to memory or to an environment variable. It is also possible
1915 to verify a hash against data in memory.
1918 bool "Support the 'hvc' command"
1919 depends on ARM_SMCCC
1921 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1922 development and testing.
1925 bool "Support the 'smc' command"
1926 depends on ARM_SMCCC
1928 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1929 development and testing.
1935 Add -v option to verify data against a hash.
1945 bool "Enable the 'tpm' command"
1946 depends on TPM_V1 || TPM_V2
1947 select CMD_TPM_V1 if TPM_V1
1948 select CMD_TPM_V2 if TPM_V2
1950 This provides a means to talk to a TPM from the command line. A wide
1951 range of commands if provided - see 'tpm help' for details. The
1952 command requires a suitable TPM on your board and the correct driver
1958 bool "Enable the 'tpm test' command"
1961 This provides a a series of tests to confirm that the TPMv1.x is
1962 working correctly. The tests cover initialisation, non-volatile RAM,
1963 extend, global lock and checking that timing is within expectations.
1964 The tests pass correctly on Infineon TPMs but may need to be adjusted
1971 menu "Firmware commands"
1973 bool "Enable crosec command"
1977 Enable command-line access to the Chrome OS EC (Embedded
1978 Controller). This provides the 'crosec' command which has
1979 a number of sub-commands for performing EC tasks such as
1980 updating its flash, accessing a small saved context area
1981 and talking to the I2C bus behind the EC (if there is one).
1984 menu "Filesystem commands"
1986 bool "Enable the 'btrsubvol' command"
1989 This enables the 'btrsubvol' command to list subvolumes
1990 of a BTRFS filesystem. There are no special commands for
1991 listing BTRFS directories or loading BTRFS files - this
1992 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1993 when BTRFS is enabled (see FS_BTRFS).
1996 bool "Enable the 'cbfs' command"
1999 Define this to enable support for reading from a Coreboot
2000 filesystem. This is a ROM-based filesystem used for accessing files
2001 on systems that use coreboot as the first boot-loader and then load
2002 U-Boot to actually boot the Operating System. Available commands are
2003 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2006 bool "Enable the 'cramfs' command"
2007 depends on FS_CRAMFS
2009 This provides commands for dealing with CRAMFS (Compressed ROM
2010 filesystem). CRAMFS is useful when space is tight since files are
2011 compressed. Two commands are provided:
2013 cramfsls - lists files in a cramfs image
2014 cramfsload - loads a file from a cramfs image
2017 bool "ext2 command support"
2020 Enables EXT2 FS command
2023 bool "ext4 command support"
2026 Enables EXT4 FS command
2028 config CMD_EXT4_WRITE
2030 bool "ext4 write command support"
2033 Enables EXT4 FS write command
2036 bool "FAT command support"
2039 Support for the FAT fs
2041 config CMD_FS_GENERIC
2042 bool "filesystem commands"
2044 Enables filesystem commands (e.g. load, ls) that work for multiple
2048 bool "fsuuid command"
2050 Enables fsuuid command for filesystem UUID.
2053 bool "jffs2 command"
2056 Enables commands to support the JFFS2 (Journalling Flash File System
2057 version 2) filesystem. This enables fsload, ls and fsinfo which
2058 provide the ability to load files, list directories and obtain
2059 filesystem information.
2062 bool "MTD partition support"
2065 MTD partitioning tool support.
2066 It is strongly encouraged to avoid using this command
2067 anymore along with 'sf', 'nand', 'onenand'. One can still
2068 declare the partitions in the mtdparts environment variable
2069 but better use the MTD stack and the 'mtd' command instead.
2071 config CMD_MTDPARTS_SPREAD
2072 bool "Padd partition size to take account of bad blocks"
2073 depends on CMD_MTDPARTS
2075 This enables the 'spread' sub-command of the mtdparts command.
2076 This command will modify the existing mtdparts variable by increasing
2077 the size of the partitions such that 1) each partition's net size is
2078 at least as large as the size specified in the mtdparts variable and
2079 2) each partition starts on a good block.
2081 config CMD_MTDPARTS_SHOW_NET_SIZES
2082 bool "Show net size (w/o bad blocks) of partitions"
2083 depends on CMD_MTDPARTS
2085 Adds two columns to the printed partition table showing the
2086 effective usable size of a partition, if bad blocks are taken
2089 config MTDIDS_DEFAULT
2090 string "Default MTD IDs"
2091 depends on MTD || SPI_FLASH
2093 Defines a default MTD IDs list for use with MTD partitions in the
2094 Linux MTD command line partitions format.
2096 config MTDPARTS_DEFAULT
2097 string "Default MTD partition scheme"
2098 depends on MTD || SPI_FLASH
2100 Defines a default MTD partitioning scheme in the Linux MTD command
2101 line partitions format
2104 bool "reiser - Access to reiserfs filesystems"
2106 This provides two commands which operate on a resierfs filesystem,
2107 commonly used some years ago:
2109 reiserls - list files
2110 reiserload - load a file
2113 bool "yaffs2 - Access of YAFFS2 filesystem"
2117 This provides commands for accessing a YAFFS2 filesystem. Yet
2118 Another Flash Filesystem 2 is a filesystem designed specifically
2119 for NAND flash. It incorporates bad-block management and ensures
2120 that device writes are sequential regardless of filesystem
2124 bool "zfs - Access of ZFS filesystem"
2126 This provides commands to accessing a ZFS filesystem, commonly used
2127 on Solaris systems. Two sub-commands are provided:
2129 zfsls - list files in a directory
2130 zfsload - load a file
2132 See doc/README.zfs for more details.
2136 menu "Debug commands"
2141 The bedbug (emBEDded deBUGger) command provides debugging features
2142 for some PowerPC processors. For details please see the
2143 documentation in doc/README.bedbug.
2146 bool "diag - Board diagnostics"
2148 This command provides access to board diagnostic tests. These are
2149 called Power-on Self Tests (POST). The command allows listing of
2150 available tests and running either all the tests, or specific tests
2154 bool "irq - Show information about interrupts"
2155 depends on !ARM && !MIPS && !SH
2157 This enables two commands:
2159 interrupts - enable or disable interrupts
2160 irqinfo - print device-specific interrupt information
2163 bool "kgdb - Allow debugging of U-Boot with gdb"
2166 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2167 over a serial link for debugging purposes. This allows
2168 single-stepping, inspecting variables, etc. This is supported only
2169 on PowerPC at present.
2172 bool "log - Generation, control and access to logging"
2175 This provides access to logging features. It allows the output of
2176 log data to be controlled to a limited extent (setting up the default
2177 maximum log level for emitting of records). It also provides access
2178 to a command used for testing the log system.
2181 bool "trace - Support tracing of function calls and timing"
2183 Enables a command to control using of function tracing within
2184 U-Boot. This allows recording of call traces including timing
2185 information. The command can write data to memory for exporting
2186 for analysis (e.g. using bootchart). See doc/README.trace for full
2190 bool "avb - Android Verified Boot 2.0 operations"
2191 depends on AVB_VERIFY
2194 Enables a "avb" command to perform verification of partitions using
2195 Android Verified Boot 2.0 functionality. It includes such subcommands:
2196 avb init - initialize avb2 subsystem
2197 avb read_rb - read rollback index
2198 avb write_rb - write rollback index
2199 avb is_unlocked - check device lock state
2200 avb get_uuid - read and print uuid of a partition
2201 avb read_part - read data from partition
2202 avb read_part_hex - read data from partition and output to stdout
2203 avb write_part - write data to partition
2204 avb verify - run full verification chain
2208 tristate "Enable UBI - Unsorted block images commands"
2211 UBI is a software layer above MTD layer which admits use of LVM-like
2212 logical volumes on top of MTD devices, hides some complexities of
2213 flash chips like wear and bad blocks and provides some other useful
2214 capabilities. Please, consult the MTD web site for more details
2215 (www.linux-mtd.infradead.org). Activate this option if you want
2216 to use U-Boot UBI commands.
2217 It is also strongly encouraged to also enable CONFIG_MTD to get full
2220 config CMD_UBI_RENAME
2221 bool "Enable rename"
2225 Enable a "ubi" command to rename ubi volume:
2226 ubi rename <oldname> <newname>
2229 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2231 default y if CMD_UBI
2234 UBIFS is a file system for flash devices which works on top of UBI.
projects / thirdparty / u-boot.git / blob