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
381 default y if CMD_BOOTEFI_SELFTEST
383 This adds a standard EFI hello world application to U-Boot so that
384 it can be used with the 'bootefi hello' command. This is useful
385 for testing that EFI is working at a basic level, and for bringing
386 up EFI support on a new architecture.
388 source lib/efi_selftest/Kconfig
394 Add an ANSI terminal boot menu command.
399 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
400 image into RAM, dump image structure information, etc. Those dtb/dtbo
401 files should be merged in one dtb further, which needs to be passed to
402 the kernel, as part of a boot process.
406 depends on ANDROID_BOOT_IMAGE
408 Android Boot Image manipulation commands. Allows one to extract
409 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
410 obtain corresponding meta-information from boot.img.
412 See doc/android/boot-image.rst for details.
415 bool "bootelf, bootvx"
419 Boot an ELF/vxWorks image from the memory.
422 bool "Flattened Device Tree utility commands"
426 Do FDT related setup before booting into the Operating System.
432 Start an application at a given address.
438 Run the command in the given environment variable.
444 Print header information for application image.
449 List all images found in flash
455 Extract a part of a multi-image.
458 bool "spl export - Export boot information for Falcon boot"
461 Falcon mode allows booting directly from SPL into an Operating
462 System such as Linux, thus skipping U-Boot proper. See
463 doc/README.falcon for full information about how to use this
466 config CMD_SPL_NAND_OFS
467 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
468 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
471 This provides the offset of the command line arguments for Linux
472 when booting from NAND in Falcon mode. See doc/README.falcon
473 for full information about how to use this option (and also see
474 board/gateworks/gw_ventana/README for an example).
476 config CMD_SPL_NOR_OFS
477 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
478 depends on CMD_SPL && SPL_NOR_SUPPORT
481 This provides the offset of the command line arguments or dtb for
482 Linux when booting from NOR in Falcon mode.
484 config CMD_SPL_WRITE_SIZE
485 hex "Size of argument area"
489 This provides the size of the command-line argument area in NAND
490 flash used by Falcon-mode boot. See the documentation until CMD_SPL
493 config CMD_THOR_DOWNLOAD
494 bool "thor - TIZEN 'thor' download"
497 Implements the 'thor' download protocol. This is a way of
498 downloading a software update over USB from an attached host.
499 There is no documentation about this within the U-Boot source code
500 but you should be able to find something on the interwebs.
503 bool "zboot - x86 boot command"
505 With x86 machines it is common to boot a bzImage file which
506 contains both a kernel and a setup.bin file. The latter includes
507 configuration information from the dark ages which x86 boards still
508 need to pick things out of.
510 Consider using FIT in preference to this since it supports directly
511 booting both 32- and 64-bit kernels, as well as secure boot.
512 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
516 menu "Environment commands"
519 bool "ask for env variable"
521 Ask for environment variable
539 Edit environment variable.
544 Allow for searching environment variables
550 Save all environment variables into the compiled-in persistent
556 depends on CMD_SAVEENV
558 Erase environment variables from the compiled-in persistent
561 config CMD_ENV_EXISTS
565 Check if a variable is defined in the environment for use in
568 config CMD_ENV_CALLBACK
569 bool "env callbacks - print callbacks and their associated variables"
571 Some environment variable have callbacks defined by
572 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
573 For example changing "baudrate" adjust the serial baud rate. This
574 command lists the currently defined callbacks.
577 bool "env flags -print variables that have non-default flags"
579 Some environment variables have special flags that control their
580 behaviour. For example, serial# can only be written once and cannot
581 be deleted. This command shows the variables that have special
584 config CMD_NVEDIT_EFI
585 bool "env [set|print] -e - set/print UEFI variables"
586 depends on EFI_LOADER
589 UEFI variables are encoded as some form of U-Boot variables.
590 If enabled, we are allowed to set/print UEFI variables using
591 "env" command with "-e" option without knowing details.
593 config CMD_NVEDIT_INFO
594 bool "env info - print or evaluate environment information"
596 Print environment information:
597 - env_valid : is environment valid
598 - env_ready : is environment imported into hash table
599 - env_use_default : is default environment used
601 This command can be optionally used for evaluation in scripts:
602 [-d] : evaluate whether default environment is used
603 [-p] : evaluate whether environment can be persisted
605 The result of multiple evaluations will be combined with AND.
609 menu "Memory commands"
614 Compute binary operations (xor, or, and) of byte arrays of arbitrary
615 size from memory and store the result in memory or the environment.
628 Add -v option to verify data against a crc32 checksum.
631 bool "eeprom - EEPROM subsystem"
633 (deprecated, needs conversion to driver model)
634 Provides commands to read and write EEPROM (Electrically Erasable
635 Programmable Read Only Memory) chips that are connected over an
638 config CMD_EEPROM_LAYOUT
639 bool "Enable layout-aware eeprom commands"
640 depends on CMD_EEPROM
642 (deprecated, needs conversion to driver model)
643 When enabled, additional eeprom sub-commands become available.
645 eeprom print - prints the contents of the eeprom in a human-readable
646 way (eeprom layout fields, and data formatted to be fit for human
649 eeprom update - allows user to update eeprom fields by specifying
650 the field name, and providing the new data in a human readable format
651 (same format as displayed by the eeprom print command).
653 Both commands can either auto detect the layout, or be told which
657 __weak int parse_layout_version(char *str)
658 - override to provide your own layout name parsing
659 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
661 - override to setup the layout metadata based on the version
662 __weak int eeprom_layout_detect(unsigned char *data)
663 - override to provide your own algorithm for detecting layout
666 - contains various printing and updating functions for common
667 types of eeprom fields. Can be used for defining
670 config EEPROM_LAYOUT_HELP_STRING
671 string "Tells user what layout names are supported"
672 depends on CMD_EEPROM_LAYOUT
673 default "<not defined>"
675 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
681 Infinite write loop on address range
688 Compute MD5 checksum.
693 depends on CMD_MD5SUM
695 Add -v option to verify data against an MD5 checksum.
700 Display memory information.
703 bool "md, mm, nm, mw, cp, cmp, base, loop"
708 mm - memory modify (auto-incrementing address)
709 nm - memory modify (constant address)
710 mw - memory write (fill)
713 base - print or set address offset
714 loop - initialize loop on address range
717 bool "ms - Memory search"
719 Memory-search command
721 This allows searching through a region of memory looking for hex
722 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
723 support it). It is also possible to search for a string. The
724 command accepts a memory range and a list of values to search for.
725 The values need to appear in memory in the same order they are given
726 in the command. At most 10 matches can be returned at a time, but
727 pressing return will show the next 10 matches. Environment variables
728 are set for use with scripting (memmatches, memaddr, mempos).
731 bool "Enable cyclic md/mw commands"
732 depends on CMD_MEMORY
734 Add the "mdc" and "mwc" memory commands. These are cyclic
739 This command will print 4 bytes (10,11,12,13) each 500 ms.
741 => mwc.l 100 12345678 10
742 This command will write 12345678 to address 100 all 10 ms.
747 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
749 random - fill memory with random data
754 Simple RAM read/write test.
758 config SYS_ALT_MEMTEST
759 bool "Alternative test"
761 Use a more complete alternative memory test.
763 config SYS_MEMTEST_START
764 hex "default start address for mtest"
767 This is the default start address for mtest for simple read/write
768 test. If no arguments are given to mtest, default address is used
771 config SYS_MEMTEST_END
772 hex "default end address for mtest"
775 This is the default end address for mtest for simple read/write
776 test. If no arguments are given to mtest, default address is used
785 Compute SHA1 checksum.
787 config SHA1SUM_VERIFY
789 depends on CMD_SHA1SUM
791 Add -v option to verify data against a SHA1 checksum.
794 bool "strings - display strings in memory"
796 This works similarly to the Unix 'strings' command except that it
797 works with a memory range. String of printable characters found
798 within the range are displayed. The minimum number of characters
799 for a sequence to be considered a string can be provided.
803 menu "Compression commands"
807 default y if CMD_BOOTI
810 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
815 default y if CMD_BOOTI
818 Support decompressing an LZ4 image from memory region.
822 default y if CMD_BOOTI
825 Uncompress a zip-compressed memory region.
829 select GZIP_COMPRESSED
831 Compress a memory region with zlib deflate method.
835 menu "Device access commands"
838 #depends on FLASH_CFI_DRIVER
841 ARM Ltd reference designs flash partition access
844 bool "adc - Access Analog to Digital Converters info and data"
848 Shows ADC device info and permit printing one-shot analog converted
849 data from a named Analog to Digital Converter.
854 depends on PARTITIONS
856 Read/modify/write the fields of Bootloader Control Block, usually
857 stored on the flash "misc" partition with its structure defined in:
858 https://android.googlesource.com/platform/bootable/recovery/+/master/
859 bootloader_message/include/bootloader_message/bootloader_message.h
861 Some real-life use-cases include (but are not limited to):
862 - Determine the "boot reason" (and act accordingly):
863 https://source.android.com/devices/bootloader/boot-reason
864 - Get/pass a list of commands from/to recovery:
865 https://android.googlesource.com/platform/bootable/recovery
866 - Inspect/dump the contents of the BCB fields
869 bool "bind/unbind - Bind or unbind a device to/from a driver"
872 Bind or unbind a device to/from a driver from the command line.
873 This is useful in situations where a device may be handled by several
874 drivers. For example, this can be used to bind a UDC to the usb ether
875 gadget driver from the command line.
878 bool "clk - Show clock frequencies"
881 Shows clock frequences by calling a sock_clk_dump() hook function.
882 This is depreated in favour of using the CLK uclass and accessing
883 clock values from associated drivers. However currently no command
887 bool "demo - Demonstration commands for driver model"
890 Provides a 'demo' command which can be used to play around with
891 driver model. To use this properly you will need to enable one or
892 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
893 Otherwise you will always get an empty list of devices. The demo
894 devices are defined in the sandbox device tree, so the easiest
895 option is to use sandbox and pass the -d point to sandbox's
902 Enables the command "dfu" which is used to have U-Boot create a DFU
903 class device via USB. This command requires that the "dfu_alt_info"
904 environment variable be set and define the alt settings to expose to
908 bool "dm - Access to driver model information"
911 Provides access to driver model data structures and information,
912 such as a list of devices, list of uclasses and the state of each
913 device (e.g. activated). This is not required for operation, but
914 can be useful to see the state of driver model for debugging or
918 bool "fastboot - Android fastboot support"
921 This enables the command "fastboot" which enables the Android
922 fastboot mode for the platform. Fastboot is a protocol for
923 downloading images, flashing and device control used on
924 Android devices. Fastboot requires either the network stack
925 enabled or support for acting as a USB device.
927 See doc/android/fastboot.rst for more information.
930 bool "flinfo, erase, protect"
932 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
935 flinfo - print FLASH memory information
937 protect - enable or disable FLASH write protection
946 config CMD_FPGA_LOADBP
947 bool "fpga loadbp - load partial bitstream (Xilinx only)"
950 Supports loading an FPGA device from a bitstream buffer containing
953 config CMD_FPGA_LOADFS
954 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
957 Supports loading an FPGA device from a FAT filesystem.
959 config CMD_FPGA_LOADMK
960 bool "fpga loadmk - load bitstream from image"
963 Supports loading an FPGA device from a image generated by mkimage.
965 config CMD_FPGA_LOADP
966 bool "fpga loadp - load partial bitstream"
969 Supports loading an FPGA device from a bitstream buffer containing
972 config CMD_FPGA_LOAD_SECURE
973 bool "fpga loads - loads secure bitstreams (Xilinx only)"
976 Enables the fpga loads command which is used to load secure
977 (authenticated or encrypted or both) bitstreams on to FPGA.
980 bool "fpgad - dump FPGA registers"
982 (legacy, needs conversion to driver model)
983 Provides a way to dump FPGA registers by calling the board-specific
984 fpga_get_reg() function. This functions similarly to the 'md'
988 bool "fuse - support for the fuse subssystem"
990 (deprecated - needs conversion to driver model)
991 This allows reading, sensing, programming or overriding fuses
992 which control the behaviour of the device. The command uses the
1001 bool "GPT (GUID Partition Table) command"
1002 select EFI_PARTITION
1003 select HAVE_BLOCK_DEVICE
1004 select PARTITION_UUIDS
1007 Enable the 'gpt' command to ready and write GPT style partition
1011 bool "GPT Random UUID generation"
1014 Enable the generation of partitions with random UUIDs if none
1017 config CMD_GPT_RENAME
1018 bool "GPT partition renaming commands"
1021 Enables the 'gpt' command to interchange names on two GPT
1022 partitions via the 'gpt swap' command or to rename single
1023 partitions via the 'rename' command.
1026 bool "ide - Support for IDE drivers"
1029 Provides an 'ide' command which allows accessing the IDE drive,
1030 reseting the IDE interface, printing the partition table and
1031 geting device info. It also enables the 'diskboot' command which
1032 permits booting from an IDE drive.
1035 bool "io - Support for performing I/O accesses"
1037 Provides an 'iod' command to display I/O space and an 'iow' command
1038 to write values to the I/O space. This can be useful for manually
1039 checking the state of devices during boot when debugging device
1043 bool "iotrace - Support for tracing I/O activity"
1045 Provides an 'iotrace' command which supports recording I/O reads and
1046 writes in a trace buffer in memory . It also maintains a checksum
1047 of the trace records (even if space is exhausted) so that the
1048 sequence of I/O accesses can be verified.
1050 When debugging drivers it is useful to see what I/O accesses were
1051 done and in what order.
1053 Even if the individual accesses are of little interest it can be
1054 useful to verify that the access pattern is consistent each time
1055 an operation is performed. In this case a checksum can be used to
1056 characterise the operation of a driver. The checksum can be compared
1057 across different runs of the operation to verify that the driver is
1060 In particular, when performing major refactoring of the driver, where
1061 the access pattern should not change, the checksum provides assurance
1062 that the refactoring work has not broken the driver.
1064 This works by sneaking into the io.h heder for an architecture and
1065 redirecting I/O accesses through iotrace's tracing mechanism.
1067 For now no commands are provided to examine the trace buffer. The
1068 format is fairly simple, so 'md' is a reasonable substitute.
1070 Note: The checksum feature is only useful for I/O regions where the
1071 contents do not change outside of software control. Where this is not
1072 suitable you can fall back to manually comparing the addresses. It
1073 might be useful to enhance tracing to only checksum the accesses and
1074 not the data read/written.
1084 bool "w1 - Support for Dallas 1-Wire protocol"
1086 Dallas 1-wire protocol support
1092 Load a binary file over serial line.
1098 Load an S-Record file over serial line
1102 bool "lsblk - list block drivers and devices"
1104 Print list of available block device drivers, and for each, the list
1105 of known block devices.
1110 MMC memory mapped support.
1114 config CMD_BKOPS_ENABLE
1115 bool "mmc bkops enable"
1119 Enable command for setting manual background operations handshake
1120 on a eMMC device. The feature is optionally available on eMMC devices
1121 conforming to standard >= 4.41.
1124 bool "Enable support for RPMB in the mmc command"
1125 depends on SUPPORT_EMMC_RPMB
1127 Enable the commands for reading, writing and programming the
1128 key for the Replay Protection Memory Block partition in eMMC.
1130 config CMD_MMC_SWRITE
1132 depends on MMC_WRITE
1135 Enable support for the "mmc swrite" command to write Android sparse
1143 select MTD_PARTITIONS
1145 MTD commands support.
1149 default y if NAND_SUNXI
1150 depends on MTD_RAW_NAND
1155 config CMD_NAND_TRIMFFS
1156 bool "nand write.trimffs"
1157 default y if ARCH_SUNXI
1159 Allows one to skip empty pages when flashing something on a NAND.
1161 config CMD_NAND_LOCK_UNLOCK
1162 bool "nand lock/unlock"
1164 NAND locking support.
1166 config CMD_NAND_TORTURE
1169 NAND torture support.
1178 NVM Express device support
1181 bool "onenand - access to onenand device"
1184 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1185 various useful features. This command allows reading, writing,
1186 and erasing blocks. It allso provides a way to show and change
1187 bad blocks, and test the device.
1192 Enable the 'osd' command which allows to query information from and
1193 write text data to a on-screen display (OSD) device; a virtual device
1194 associated with a display capable of displaying a text overlay on the
1195 display it's associated with..
1199 select HAVE_BLOCK_DEVICE
1200 select PARTITION_UUIDS
1202 Read and display information about the partition table on
1206 bool "pci - Access PCI devices"
1208 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1209 used on some devices to allow the CPU to communicate with its
1210 peripherals. Sub-commands allow bus enumeration, displaying and
1211 changing configuration space and a few other features.
1214 bool "pinmux - show pins muxing"
1215 default y if PINCTRL
1217 Parse all available pin-controllers and show pins muxing. This
1218 is useful for debug purpoer to check the pin muxing and to know if
1219 a pin is configured as a GPIO or as an alternate function.
1224 Poweroff/Shutdown the system
1227 bool "read - Read binary data from a partition"
1229 Provides low-level access to the data in a partition.
1231 config CMD_REMOTEPROC
1233 depends on REMOTEPROC
1235 Support for Remote Processor control
1238 bool "sata - Access SATA subsystem"
1241 SATA (Serial Advanced Technology Attachment) is a serial bus
1242 standard for connecting to hard drives and other storage devices.
1243 This command provides information about attached devices and allows
1244 reading, writing and other operations.
1246 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1247 Attachment, where AT refers to an IBM AT (Advanced Technology)
1248 computer released in 1984.
1251 bool "saves - Save a file over serial in S-Record format"
1253 Provides a way to save a binary file using the Motorola S-Record
1254 format over the serial line.
1257 bool "scsi - Access to SCSI devices"
1260 This provides a 'scsi' command which provides access to SCSI (Small
1261 Computer System Interface) devices. The command provides a way to
1262 scan the bus, reset the bus, read and write data and get information
1266 bool "sdram - Print SDRAM configuration information"
1268 Provides information about attached SDRAM. This assumed that the
1269 SDRAM has an EEPROM with information that can be read using the
1270 I2C bus. This is only available on some boards.
1274 depends on DM_SPI_FLASH || SPI_FLASH
1275 default y if DM_SPI_FLASH
1280 bool "sf test - Allow testing of SPI flash"
1283 Provides a way to test that SPI flash is working correctly. The
1284 test is destructive, in that an area of SPI flash must be provided
1285 for the test to use. Performance information is also provided,
1286 measuring the performance of reading, writing and erasing in
1287 Mbps (Million Bits Per Second). This value should approximately
1288 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1289 everything is working properly.
1292 bool "sspi - Command to access spi device"
1295 SPI utility command.
1297 config DEFAULT_SPI_BUS
1298 int "default spi bus used by sspi command"
1302 config DEFAULT_SPI_MODE
1303 hex "default spi mode used by sspi command (see include/spi.h)"
1308 bool "tsi148 - Command to access tsi148 device"
1310 This provides various sub-commands to initialise and configure the
1311 Turndra tsi148 device. See the command help for full details.
1314 bool "Enable UFS - Universal Flash Subsystem commands"
1317 "This provides commands to initialise and configure universal flash
1321 bool "universe - Command to set up the Turndra Universe controller"
1323 This allows setting up the VMEbus provided by this controller.
1324 See the command help for full details.
1328 select HAVE_BLOCK_DEVICE
1334 select USB_FUNCTION_SDP
1336 Enables the command "sdp" which is used to have U-Boot emulating the
1337 Serial Download Protocol (SDP) via USB.
1341 depends on USB_FUNCTION_ROCKUSB
1343 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1344 read/write info, image to/from devices. This enable rockusb command
1345 support to communication with rockusb device. for more detail about
1346 this command, please read doc/README.rockusb.
1348 config CMD_USB_MASS_STORAGE
1349 bool "UMS usb mass storage"
1350 select USB_FUNCTION_MASS_STORAGE
1352 USB mass storage support
1359 VirtIO block device support
1365 This provides commands to control the watchdog timer devices.
1371 Enable the command "axi" for accessing AXI (Advanced eXtensible
1372 Interface) busses, a on-chip interconnect specification for managing
1373 functional blocks in SoC designs, which is also often used in designs
1374 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1378 menu "Shell scripting commands"
1384 Echo args to console
1390 Return true/false on integer compare.
1396 Run script from memory
1402 Evaluate boolean and math expressions and store the result in an env
1404 Also supports loading the value at a memory location into a variable.
1405 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1409 menu "Android support commands"
1411 config CMD_AB_SELECT
1414 depends on ANDROID_AB
1416 On Android devices with more than one boot slot (multiple copies of
1417 the kernel and system images) this provides a command to select which
1418 slot should be used to boot from and register the boot attempt. This
1419 is used by the new A/B update model where one slot is updated in the
1420 background while running from the other slot.
1427 bool "Network commands"
1437 bootp - boot image via network using BOOTP/TFTP protocol
1441 depends on CMD_BOOTP
1443 Boot image via network using DHCP/TFTP protocol
1445 config BOOTP_BOOTPATH
1446 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1448 depends on CMD_BOOTP
1450 Even though the config is called BOOTP_BOOTPATH, it stores the
1451 path in the variable 'rootpath'.
1454 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1456 depends on CMD_BOOTP
1458 The primary DNS server is stored as 'dnsip'. If two servers are
1459 returned, you must set BOOTP_DNS2 to store that second server IP
1463 bool "Store 'dnsip2' from BOOTP/DHCP server"
1464 depends on BOOTP_DNS
1466 If a DHCP client requests the DNS server IP from a DHCP server,
1467 it is possible that more than one DNS serverip is offered to the
1468 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1469 server IP will be stored in the additional environment
1470 variable "dnsip2". The first DNS serverip is always
1471 stored in the variable "dnsip", when BOOTP_DNS is defined.
1473 config BOOTP_GATEWAY
1474 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1476 depends on CMD_BOOTP
1478 config BOOTP_HOSTNAME
1479 bool "Request & store 'hostname' from BOOTP/DHCP server"
1481 depends on CMD_BOOTP
1483 The name may or may not be qualified with the local domain name.
1485 config BOOTP_PREFER_SERVERIP
1486 bool "serverip variable takes precedent over DHCP server IP."
1487 depends on CMD_BOOTP
1489 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1491 With this option enabled, the 'serverip' variable in the environment
1492 takes precedence over DHCP server IP and will only be set by the DHCP
1493 server if not already set in the environment.
1495 config BOOTP_SUBNETMASK
1496 bool "Request & store 'netmask' from BOOTP/DHCP server"
1498 depends on CMD_BOOTP
1500 config BOOTP_NTPSERVER
1501 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1502 depends on CMD_BOOTP
1507 Selecting this will allow capturing all Ethernet packets and store
1508 them in physical memory in a PCAP formated file,
1509 later to be analyzed by PCAP reader application (IE. WireShark).
1512 bool "Send PXE client arch to BOOTP/DHCP server"
1514 depends on CMD_BOOTP && CMD_PXE
1516 Supported for ARM, ARM64, and x86 for now.
1518 config BOOTP_PXE_CLIENTARCH
1520 depends on BOOTP_PXE
1521 default 0x16 if ARM64
1525 config BOOTP_VCI_STRING
1527 depends on CMD_BOOTP
1528 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1529 default "U-Boot.armv8" if ARM64
1530 default "U-Boot.arm" if ARM
1537 tftpboot - boot image via network using TFTP protocol
1541 depends on CMD_TFTPBOOT
1543 TFTP put command, for uploading files to a server
1547 depends on CMD_TFTPBOOT
1549 Act as a TFTP server and boot the first received file
1551 config NET_TFTP_VARS
1552 bool "Control TFTP timeout and count through environment"
1553 depends on CMD_TFTPBOOT
1556 If set, allows controlling the TFTP timeout through the
1557 environment variable tftptimeout, and the TFTP maximum
1558 timeout count through the variable tftptimeoutcountmax.
1559 If unset, timeout and maximum are hard-defined as 1 second
1560 and 10 timouts per TFTP transfer.
1565 Boot image via network using RARP/TFTP protocol
1571 Boot image via network using NFS protocol.
1577 If set, allows 802.3(clause 22) MII Management functions interface access
1578 The management interface specified in Clause 22 provides
1579 a simple, two signal, serial interface to connect a
1580 Station Management entity and a managed PHY for providing access
1581 to management parameters and services.
1582 The interface is referred to as the MII management interface.
1588 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1589 The MDIO interface is orthogonal to the MII interface and extends
1590 it by adding access to more registers through indirect addressing.
1595 Send ICMP ECHO_REQUEST to network host
1600 Perform CDP network configuration
1605 Synchronize RTC via network
1610 Lookup the IP of a hostname
1612 config CMD_LINK_LOCAL
1616 Acquire a network IP address using the link-local protocol
1623 Allow control of L2 Ethernet switch commands. These are supported
1624 by the vsc9953 Ethernet driver at present. Sub-commands allow
1625 operations such as enabling / disabling a port and
1626 viewing/maintaining the filtering database (FDB)
1632 Boot image via network using PXE protocol
1637 Wait for wake-on-lan Magic Packet
1641 menu "Misc commands"
1644 bool "Enable 'bmp' command"
1645 depends on LCD || DM_VIDEO || VIDEO
1647 This provides a way to obtain information about a BMP-format image
1648 and to display it. BMP (which presumably stands for BitMaP) is a
1649 file format defined by Microsoft which supports images of various
1650 depths, formats and compression methods. Headers on the file
1651 determine the formats used. This command can be used by first loading
1652 the image into RAM, then using this command to look at it or display
1655 config CMD_BOOTCOUNT
1657 depends on BOOTCOUNT_LIMIT
1659 Enable the bootcount command, which allows interrogation and
1660 reset of the bootcounter.
1663 bool "Enable board-specific commands"
1665 (deprecated: instead, please define a Kconfig option for each command)
1667 Some boards have board-specific commands which are only enabled
1668 during developemnt and need to be turned off for production. This
1669 option provides a way to control this. The commands that are enabled
1670 vary depending on the board.
1672 config CMD_BLOCK_CACHE
1673 bool "blkcache - control and stats for block cache"
1674 depends on BLOCK_CACHE
1675 default y if BLOCK_CACHE
1677 Enable the blkcache command, which can be used to control the
1678 operation of the cache functions.
1679 This is most useful when fine-tuning the operation of the cache
1680 during development, but also allows the cache to be disabled when
1681 it might hurt performance (e.g. when using the ums command).
1684 bool "icache or dcache"
1686 Enable the "icache" and "dcache" commands
1688 config CMD_CONITRACE
1689 bool "conitrace - trace console input codes"
1691 Enable the 'conitrace' command which displays the codes received
1692 from the console input as hexadecimal numbers.
1695 bool "Enable clear screen command 'cls'"
1696 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1699 Enable the 'cls' command which clears the screen contents
1700 on video frame buffer.
1703 bool "efidebug - display/configure UEFI environment"
1704 depends on EFI_LOADER
1705 select EFI_DEVICE_PATH_TO_TEXT
1708 Enable the 'efidebug' command which provides a subset of UEFI
1709 shell utility with simplified functionality. It will be useful
1710 particularly for managing boot parameters as well as examining
1711 various EFI status for debugging.
1713 config CMD_EXCEPTION
1714 bool "exception - raise exception"
1715 depends on ARM || RISCV || X86
1717 Enable the 'exception' command which allows to raise an exception.
1724 Enable the 'led' command which allows for control of LEDs supported
1725 by the board. The LEDs can be listed with 'led list' and controlled
1726 with led on/off/togle/blink. Any LED drivers can be controlled with
1727 this command, e.g. led_gpio.
1734 Enable the 'date' command for getting/setting the time/date in RTC
1741 Enable the 'rtc' command for low-level access to RTC devices.
1746 Run commands and summarize execution time.
1749 bool "gettime - read elapsed time"
1751 Enable the 'gettime' command which reads the elapsed time since
1752 U-Boot started running. This shows the time in seconds and
1753 milliseconds. See also the 'bootstage' command which provides more
1754 flexibility for boot timing.
1761 Print bytes from the hardware random number generator.
1763 # TODO: rename to CMD_SLEEP
1768 Delay execution for some time
1771 bool "support for multiprocessor"
1773 This provides an option to brinup
1774 different processors in multiprocessor
1780 Access the system timer.
1786 This provides basic access to the U-Boot's sound support. The main
1787 feature is to play a beep.
1789 sound init - set up sound system
1790 sound play - play a sound
1796 Boot image via local extlinux.conf file
1802 This provides access to the QEMU firmware interface. The main
1803 feature is to allow easy loading of files passed to qemu-system
1804 via -kernel / -initrd
1806 source "cmd/mvebu/Kconfig"
1809 bool "terminal - provides a way to attach a serial terminal"
1811 Provides a 'cu'-like serial terminal command. This can be used to
1812 access other serial ports from the system console. The terminal
1813 is very simple with no special processing of characters. As with
1814 cu, you can press ~. (tilde followed by period) to exit.
1817 bool "uuid, guid - generation of unique IDs"
1820 This enables two commands:
1822 uuid - generate random Universally Unique Identifier
1823 guid - generate Globally Unique Identifier based on random UUID
1825 The two commands are very similar except for the endianness of the
1830 source "cmd/ti/Kconfig"
1832 config CMD_BOOTSTAGE
1833 bool "Enable the 'bootstage' command"
1834 depends on BOOTSTAGE
1836 Add a 'bootstage' command which supports printing a report
1837 and un/stashing of bootstage data.
1839 menu "Power commands"
1841 bool "Enable Driver Model PMIC command"
1844 This is the pmic command, based on a driver model pmic's API.
1845 Command features are unchanged:
1846 - list - list pmic devices
1847 - pmic dev <id> - show or [set] operating pmic device (NEW)
1848 - pmic dump - dump registers
1849 - pmic read address - read byte of register at address
1850 - pmic write address - write byte to register at address
1851 The only one change for this command is 'dev' subcommand.
1853 config CMD_REGULATOR
1854 bool "Enable Driver Model REGULATOR command"
1855 depends on DM_REGULATOR
1857 This command is based on driver model regulator's API.
1858 User interface features:
1859 - list - list regulator devices
1860 - regulator dev <id> - show or [set] operating regulator device
1861 - regulator info - print constraints info
1862 - regulator status - print operating status
1863 - regulator value <val] <-f> - print/[set] voltage value [uV]
1864 - regulator current <val> - print/[set] current value [uA]
1865 - regulator mode <id> - print/[set] operating mode id
1866 - regulator enable - enable the regulator output
1867 - regulator disable - disable the regulator output
1869 The '-f' (force) option can be used for set the value which exceeds
1870 the limits, which are found in device-tree and are kept in regulator's
1871 uclass platdata structure.
1875 menu "Security commands"
1877 bool "Enable the 'aes' command"
1880 This provides a means to encrypt and decrypt data using the AES
1881 (Advanced Encryption Standard). This algorithm uses a symetric key
1882 and is widely used as a streaming cipher. Different key lengths are
1883 supported by the algorithm but this command only supports 128 bits
1887 bool "Enable the 'blob' command"
1889 This is used with the Freescale secure boot mechanism.
1891 Freescale's SEC block has built-in Blob Protocol which provides
1892 a method for protecting user-defined data across system power
1893 cycles. SEC block protects data in a data structure called a Blob,
1894 which provides both confidentiality and integrity protection.
1896 Encapsulating data as a blob
1897 Each time that the Blob Protocol is used to protect data, a
1898 different randomly generated key is used to encrypt the data.
1899 This random key is itself encrypted using a key which is derived
1900 from SoC's non-volatile secret key and a 16 bit Key identifier.
1901 The resulting encrypted key along with encrypted data is called a
1902 blob. The non-volatile secure key is available for use only during
1905 During decapsulation, the reverse process is performed to get back
1909 blob enc - encapsulating data as a cryptgraphic blob
1910 blob dec - decapsulating cryptgraphic blob to get the data
1914 blob enc src dst len km
1916 Encapsulate and create blob of data $len bytes long
1917 at address $src and store the result at address $dst.
1918 $km is the 16 byte key modifier is also required for
1919 generation/use as key for cryptographic operation. Key
1920 modifier should be 16 byte long.
1922 blob dec src dst len km
1924 Decapsulate the blob of data at address $src and
1925 store result of $len byte at addr $dst.
1926 $km is the 16 byte key modifier is also required for
1927 generation/use as key for cryptographic operation. Key
1928 modifier should be 16 byte long.
1931 bool "Support 'hash' command"
1934 This provides a way to hash data in memory using various supported
1935 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1936 saved to memory or to an environment variable. It is also possible
1937 to verify a hash against data in memory.
1940 bool "Support the 'hvc' command"
1941 depends on ARM_SMCCC
1943 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1944 development and testing.
1947 bool "Support the 'smc' command"
1948 depends on ARM_SMCCC
1950 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1951 development and testing.
1957 Add -v option to verify data against a hash.
1967 bool "Enable the 'tpm' command"
1968 depends on TPM_V1 || TPM_V2
1969 select CMD_TPM_V1 if TPM_V1
1970 select CMD_TPM_V2 if TPM_V2
1972 This provides a means to talk to a TPM from the command line. A wide
1973 range of commands if provided - see 'tpm help' for details. The
1974 command requires a suitable TPM on your board and the correct driver
1980 bool "Enable the 'tpm test' command"
1983 This provides a a series of tests to confirm that the TPMv1.x is
1984 working correctly. The tests cover initialisation, non-volatile RAM,
1985 extend, global lock and checking that timing is within expectations.
1986 The tests pass correctly on Infineon TPMs but may need to be adjusted
1993 menu "Firmware commands"
1995 bool "Enable crosec command"
1999 Enable command-line access to the Chrome OS EC (Embedded
2000 Controller). This provides the 'crosec' command which has
2001 a number of sub-commands for performing EC tasks such as
2002 updating its flash, accessing a small saved context area
2003 and talking to the I2C bus behind the EC (if there is one).
2006 menu "Filesystem commands"
2008 bool "Enable the 'btrsubvol' command"
2011 This enables the 'btrsubvol' command to list subvolumes
2012 of a BTRFS filesystem. There are no special commands for
2013 listing BTRFS directories or loading BTRFS files - this
2014 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2015 when BTRFS is enabled (see FS_BTRFS).
2018 bool "Enable the 'cbfs' command"
2021 Define this to enable support for reading from a Coreboot
2022 filesystem. This is a ROM-based filesystem used for accessing files
2023 on systems that use coreboot as the first boot-loader and then load
2024 U-Boot to actually boot the Operating System. Available commands are
2025 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2028 bool "Enable the 'cramfs' command"
2029 depends on FS_CRAMFS
2031 This provides commands for dealing with CRAMFS (Compressed ROM
2032 filesystem). CRAMFS is useful when space is tight since files are
2033 compressed. Two commands are provided:
2035 cramfsls - lists files in a cramfs image
2036 cramfsload - loads a file from a cramfs image
2039 bool "ext2 command support"
2042 Enables EXT2 FS command
2045 bool "ext4 command support"
2048 Enables EXT4 FS command
2050 config CMD_EXT4_WRITE
2052 bool "ext4 write command support"
2055 Enables EXT4 FS write command
2058 bool "FAT command support"
2061 Support for the FAT fs
2063 config CMD_FS_GENERIC
2064 bool "filesystem commands"
2066 Enables filesystem commands (e.g. load, ls) that work for multiple
2070 bool "fsuuid command"
2072 Enables fsuuid command for filesystem UUID.
2075 bool "jffs2 command"
2078 Enables commands to support the JFFS2 (Journalling Flash File System
2079 version 2) filesystem. This enables fsload, ls and fsinfo which
2080 provide the ability to load files, list directories and obtain
2081 filesystem information.
2084 bool "MTD partition support"
2087 MTD partitioning tool support.
2088 It is strongly encouraged to avoid using this command
2089 anymore along with 'sf', 'nand', 'onenand'. One can still
2090 declare the partitions in the mtdparts environment variable
2091 but better use the MTD stack and the 'mtd' command instead.
2093 config CMD_MTDPARTS_SPREAD
2094 bool "Padd partition size to take account of bad blocks"
2095 depends on CMD_MTDPARTS
2097 This enables the 'spread' sub-command of the mtdparts command.
2098 This command will modify the existing mtdparts variable by increasing
2099 the size of the partitions such that 1) each partition's net size is
2100 at least as large as the size specified in the mtdparts variable and
2101 2) each partition starts on a good block.
2103 config CMD_MTDPARTS_SHOW_NET_SIZES
2104 bool "Show net size (w/o bad blocks) of partitions"
2105 depends on CMD_MTDPARTS
2107 Adds two columns to the printed partition table showing the
2108 effective usable size of a partition, if bad blocks are taken
2111 config MTDIDS_DEFAULT
2112 string "Default MTD IDs"
2113 depends on MTD || SPI_FLASH
2115 Defines a default MTD IDs list for use with MTD partitions in the
2116 Linux MTD command line partitions format.
2118 config MTDPARTS_DEFAULT
2119 string "Default MTD partition scheme"
2120 depends on MTD || SPI_FLASH
2122 Defines a default MTD partitioning scheme in the Linux MTD command
2123 line partitions format
2126 bool "reiser - Access to reiserfs filesystems"
2128 This provides two commands which operate on a resierfs filesystem,
2129 commonly used some years ago:
2131 reiserls - list files
2132 reiserload - load a file
2135 bool "yaffs2 - Access of YAFFS2 filesystem"
2139 This provides commands for accessing a YAFFS2 filesystem. Yet
2140 Another Flash Filesystem 2 is a filesystem designed specifically
2141 for NAND flash. It incorporates bad-block management and ensures
2142 that device writes are sequential regardless of filesystem
2146 bool "zfs - Access of ZFS filesystem"
2148 This provides commands to accessing a ZFS filesystem, commonly used
2149 on Solaris systems. Two sub-commands are provided:
2151 zfsls - list files in a directory
2152 zfsload - load a file
2154 See doc/README.zfs for more details.
2158 menu "Debug commands"
2163 The bedbug (emBEDded deBUGger) command provides debugging features
2164 for some PowerPC processors. For details please see the
2165 documentation in doc/README.bedbug.
2168 bool "diag - Board diagnostics"
2170 This command provides access to board diagnostic tests. These are
2171 called Power-on Self Tests (POST). The command allows listing of
2172 available tests and running either all the tests, or specific tests
2176 bool "irq - Show information about interrupts"
2177 depends on !ARM && !MIPS && !SH
2179 This enables two commands:
2181 interrupts - enable or disable interrupts
2182 irqinfo - print device-specific interrupt information
2185 bool "kgdb - Allow debugging of U-Boot with gdb"
2188 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2189 over a serial link for debugging purposes. This allows
2190 single-stepping, inspecting variables, etc. This is supported only
2191 on PowerPC at present.
2194 bool "log - Generation, control and access to logging"
2197 This provides access to logging features. It allows the output of
2198 log data to be controlled to a limited extent (setting up the default
2199 maximum log level for emitting of records). It also provides access
2200 to a command used for testing the log system.
2203 bool "trace - Support tracing of function calls and timing"
2205 Enables a command to control using of function tracing within
2206 U-Boot. This allows recording of call traces including timing
2207 information. The command can write data to memory for exporting
2208 for analysis (e.g. using bootchart). See doc/README.trace for full
2212 bool "avb - Android Verified Boot 2.0 operations"
2213 depends on AVB_VERIFY
2216 Enables a "avb" command to perform verification of partitions using
2217 Android Verified Boot 2.0 functionality. It includes such subcommands:
2218 avb init - initialize avb2 subsystem
2219 avb read_rb - read rollback index
2220 avb write_rb - write rollback index
2221 avb is_unlocked - check device lock state
2222 avb get_uuid - read and print uuid of a partition
2223 avb read_part - read data from partition
2224 avb read_part_hex - read data from partition and output to stdout
2225 avb write_part - write data to partition
2226 avb verify - run full verification chain
2230 tristate "Enable UBI - Unsorted block images commands"
2233 UBI is a software layer above MTD layer which admits use of LVM-like
2234 logical volumes on top of MTD devices, hides some complexities of
2235 flash chips like wear and bad blocks and provides some other useful
2236 capabilities. Please, consult the MTD web site for more details
2237 (www.linux-mtd.infradead.org). Activate this option if you want
2238 to use U-Boot UBI commands.
2239 It is also strongly encouraged to also enable CONFIG_MTD to get full
2242 config CMD_UBI_RENAME
2243 bool "Enable rename"
2247 Enable a "ubi" command to rename ubi volume:
2248 ubi rename <oldname> <newname>
2251 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2253 default y if CMD_UBI
2256 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob