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 "ms - Memory search"
724 Memory-search command
726 This allows searching through a region of memory looking for hex
727 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
728 support it). It is also possible to search for a string. The
729 command accepts a memory range and a list of values to search for.
730 The values need to appear in memory in the same order they are given
731 in the command. At most 10 matches can be returned at a time, but
732 pressing return will show the next 10 matches. Environment variables
733 are set for use with scripting (memmatches, memaddr, mempos).
736 bool "Enable cyclic md/mw commands"
737 depends on CMD_MEMORY
739 Add the "mdc" and "mwc" memory commands. These are cyclic
744 This command will print 4 bytes (10,11,12,13) each 500 ms.
746 => mwc.l 100 12345678 10
747 This command will write 12345678 to address 100 all 10 ms.
752 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
754 random - fill memory with random data
759 Simple RAM read/write test.
763 config SYS_ALT_MEMTEST
764 bool "Alternative test"
766 Use a more complete alternative memory test.
768 config SYS_MEMTEST_START
769 hex "default start address for mtest"
772 This is the default start address for mtest for simple read/write
773 test. If no arguments are given to mtest, default address is used
776 config SYS_MEMTEST_END
777 hex "default end address for mtest"
780 This is the default end address for mtest for simple read/write
781 test. If no arguments are given to mtest, default address is used
790 Compute SHA1 checksum.
792 config SHA1SUM_VERIFY
794 depends on CMD_SHA1SUM
796 Add -v option to verify data against a SHA1 checksum.
799 bool "strings - display strings in memory"
801 This works similarly to the Unix 'strings' command except that it
802 works with a memory range. String of printable characters found
803 within the range are displayed. The minimum number of characters
804 for a sequence to be considered a string can be provided.
808 menu "Compression commands"
812 default y if CMD_BOOTI
815 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
820 default y if CMD_BOOTI
823 Support decompressing an LZ4 image from memory region.
827 default y if CMD_BOOTI
830 Uncompress a zip-compressed memory region.
834 select GZIP_COMPRESSED
836 Compress a memory region with zlib deflate method.
840 menu "Device access commands"
843 #depends on FLASH_CFI_DRIVER
846 ARM Ltd reference designs flash partition access
849 bool "adc - Access Analog to Digital Converters info and data"
853 Shows ADC device info and permit printing one-shot analog converted
854 data from a named Analog to Digital Converter.
859 depends on PARTITIONS
861 Read/modify/write the fields of Bootloader Control Block, usually
862 stored on the flash "misc" partition with its structure defined in:
863 https://android.googlesource.com/platform/bootable/recovery/+/master/
864 bootloader_message/include/bootloader_message/bootloader_message.h
866 Some real-life use-cases include (but are not limited to):
867 - Determine the "boot reason" (and act accordingly):
868 https://source.android.com/devices/bootloader/boot-reason
869 - Get/pass a list of commands from/to recovery:
870 https://android.googlesource.com/platform/bootable/recovery
871 - Inspect/dump the contents of the BCB fields
874 bool "bind/unbind - Bind or unbind a device to/from a driver"
877 Bind or unbind a device to/from a driver from the command line.
878 This is useful in situations where a device may be handled by several
879 drivers. For example, this can be used to bind a UDC to the usb ether
880 gadget driver from the command line.
883 bool "clk - Show clock frequencies"
886 Shows clock frequences by calling a sock_clk_dump() hook function.
887 This is depreated in favour of using the CLK uclass and accessing
888 clock values from associated drivers. However currently no command
892 bool "demo - Demonstration commands for driver model"
895 Provides a 'demo' command which can be used to play around with
896 driver model. To use this properly you will need to enable one or
897 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
898 Otherwise you will always get an empty list of devices. The demo
899 devices are defined in the sandbox device tree, so the easiest
900 option is to use sandbox and pass the -d point to sandbox's
907 Enables the command "dfu" which is used to have U-Boot create a DFU
908 class device via USB. This command requires that the "dfu_alt_info"
909 environment variable be set and define the alt settings to expose to
913 bool "dm - Access to driver model information"
916 Provides access to driver model data structures and information,
917 such as a list of devices, list of uclasses and the state of each
918 device (e.g. activated). This is not required for operation, but
919 can be useful to see the state of driver model for debugging or
923 bool "fastboot - Android fastboot support"
926 This enables the command "fastboot" which enables the Android
927 fastboot mode for the platform. Fastboot is a protocol for
928 downloading images, flashing and device control used on
929 Android devices. Fastboot requires either the network stack
930 enabled or support for acting as a USB device.
932 See doc/android/fastboot.rst for more information.
935 bool "flinfo, erase, protect"
937 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
940 flinfo - print FLASH memory information
942 protect - enable or disable FLASH write protection
951 config CMD_FPGA_LOADBP
952 bool "fpga loadbp - load partial bitstream (Xilinx only)"
955 Supports loading an FPGA device from a bitstream buffer containing
958 config CMD_FPGA_LOADFS
959 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
962 Supports loading an FPGA device from a FAT filesystem.
964 config CMD_FPGA_LOADMK
965 bool "fpga loadmk - load bitstream from image"
968 Supports loading an FPGA device from a image generated by mkimage.
970 config CMD_FPGA_LOADP
971 bool "fpga loadp - load partial bitstream"
974 Supports loading an FPGA device from a bitstream buffer containing
977 config CMD_FPGA_LOAD_SECURE
978 bool "fpga loads - loads secure bitstreams (Xilinx only)"
981 Enables the fpga loads command which is used to load secure
982 (authenticated or encrypted or both) bitstreams on to FPGA.
985 bool "fpgad - dump FPGA registers"
987 (legacy, needs conversion to driver model)
988 Provides a way to dump FPGA registers by calling the board-specific
989 fpga_get_reg() function. This functions similarly to the 'md'
993 bool "fuse - support for the fuse subssystem"
995 (deprecated - needs conversion to driver model)
996 This allows reading, sensing, programming or overriding fuses
997 which control the behaviour of the device. The command uses the
1006 bool "GPT (GUID Partition Table) command"
1007 select EFI_PARTITION
1008 select HAVE_BLOCK_DEVICE
1009 select PARTITION_UUIDS
1012 Enable the 'gpt' command to ready and write GPT style partition
1016 bool "GPT Random UUID generation"
1019 Enable the generation of partitions with random UUIDs if none
1022 config CMD_GPT_RENAME
1023 bool "GPT partition renaming commands"
1026 Enables the 'gpt' command to interchange names on two GPT
1027 partitions via the 'gpt swap' command or to rename single
1028 partitions via the 'rename' command.
1031 bool "ide - Support for IDE drivers"
1034 Provides an 'ide' command which allows accessing the IDE drive,
1035 reseting the IDE interface, printing the partition table and
1036 geting device info. It also enables the 'diskboot' command which
1037 permits booting from an IDE drive.
1040 bool "io - Support for performing I/O accesses"
1042 Provides an 'iod' command to display I/O space and an 'iow' command
1043 to write values to the I/O space. This can be useful for manually
1044 checking the state of devices during boot when debugging device
1048 bool "iotrace - Support for tracing I/O activity"
1050 Provides an 'iotrace' command which supports recording I/O reads and
1051 writes in a trace buffer in memory . It also maintains a checksum
1052 of the trace records (even if space is exhausted) so that the
1053 sequence of I/O accesses can be verified.
1055 When debugging drivers it is useful to see what I/O accesses were
1056 done and in what order.
1058 Even if the individual accesses are of little interest it can be
1059 useful to verify that the access pattern is consistent each time
1060 an operation is performed. In this case a checksum can be used to
1061 characterise the operation of a driver. The checksum can be compared
1062 across different runs of the operation to verify that the driver is
1065 In particular, when performing major refactoring of the driver, where
1066 the access pattern should not change, the checksum provides assurance
1067 that the refactoring work has not broken the driver.
1069 This works by sneaking into the io.h heder for an architecture and
1070 redirecting I/O accesses through iotrace's tracing mechanism.
1072 For now no commands are provided to examine the trace buffer. The
1073 format is fairly simple, so 'md' is a reasonable substitute.
1075 Note: The checksum feature is only useful for I/O regions where the
1076 contents do not change outside of software control. Where this is not
1077 suitable you can fall back to manually comparing the addresses. It
1078 might be useful to enhance tracing to only checksum the accesses and
1079 not the data read/written.
1089 bool "w1 - Support for Dallas 1-Wire protocol"
1091 Dallas 1-wire protocol support
1097 Load a binary file over serial line.
1103 Load an S-Record file over serial line
1107 bool "lsblk - list block drivers and devices"
1109 Print list of available block device drivers, and for each, the list
1110 of known block devices.
1115 MMC memory mapped support.
1119 config CMD_BKOPS_ENABLE
1120 bool "mmc bkops enable"
1124 Enable command for setting manual background operations handshake
1125 on a eMMC device. The feature is optionally available on eMMC devices
1126 conforming to standard >= 4.41.
1129 bool "Enable support for RPMB in the mmc command"
1130 depends on SUPPORT_EMMC_RPMB
1132 Enable the commands for reading, writing and programming the
1133 key for the Replay Protection Memory Block partition in eMMC.
1135 config CMD_MMC_SWRITE
1137 depends on MMC_WRITE
1140 Enable support for the "mmc swrite" command to write Android sparse
1148 select MTD_PARTITIONS
1150 MTD commands support.
1154 default y if NAND_SUNXI
1155 depends on MTD_RAW_NAND
1160 config CMD_NAND_TRIMFFS
1161 bool "nand write.trimffs"
1162 default y if ARCH_SUNXI
1164 Allows one to skip empty pages when flashing something on a NAND.
1166 config CMD_NAND_LOCK_UNLOCK
1167 bool "nand lock/unlock"
1169 NAND locking support.
1171 config CMD_NAND_TORTURE
1174 NAND torture support.
1183 NVM Express device support
1186 bool "onenand - access to onenand device"
1189 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1190 various useful features. This command allows reading, writing,
1191 and erasing blocks. It allso provides a way to show and change
1192 bad blocks, and test the device.
1197 Enable the 'osd' command which allows to query information from and
1198 write text data to a on-screen display (OSD) device; a virtual device
1199 associated with a display capable of displaying a text overlay on the
1200 display it's associated with..
1204 select HAVE_BLOCK_DEVICE
1205 select PARTITION_UUIDS
1207 Read and display information about the partition table on
1211 bool "pci - Access PCI devices"
1213 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1214 used on some devices to allow the CPU to communicate with its
1215 peripherals. Sub-commands allow bus enumeration, displaying and
1216 changing configuration space and a few other features.
1219 bool "pinmux - show pins muxing"
1220 default y if PINCTRL
1222 Parse all available pin-controllers and show pins muxing. This
1223 is useful for debug purpoer to check the pin muxing and to know if
1224 a pin is configured as a GPIO or as an alternate function.
1229 Poweroff/Shutdown the system
1232 bool "read - Read binary data from a partition"
1234 Provides low-level access to the data in a partition.
1236 config CMD_REMOTEPROC
1238 depends on REMOTEPROC
1240 Support for Remote Processor control
1243 bool "sata - Access SATA subsystem"
1246 SATA (Serial Advanced Technology Attachment) is a serial bus
1247 standard for connecting to hard drives and other storage devices.
1248 This command provides information about attached devices and allows
1249 reading, writing and other operations.
1251 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1252 Attachment, where AT refers to an IBM AT (Advanced Technology)
1253 computer released in 1984.
1256 bool "saves - Save a file over serial in S-Record format"
1258 Provides a way to save a binary file using the Motorola S-Record
1259 format over the serial line.
1262 bool "scsi - Access to SCSI devices"
1265 This provides a 'scsi' command which provides access to SCSI (Small
1266 Computer System Interface) devices. The command provides a way to
1267 scan the bus, reset the bus, read and write data and get information
1271 bool "sdram - Print SDRAM configuration information"
1273 Provides information about attached SDRAM. This assumed that the
1274 SDRAM has an EEPROM with information that can be read using the
1275 I2C bus. This is only available on some boards.
1279 depends on DM_SPI_FLASH || SPI_FLASH
1280 default y if DM_SPI_FLASH
1285 bool "sf test - Allow testing of SPI flash"
1288 Provides a way to test that SPI flash is working correctly. The
1289 test is destructive, in that an area of SPI flash must be provided
1290 for the test to use. Performance information is also provided,
1291 measuring the performance of reading, writing and erasing in
1292 Mbps (Million Bits Per Second). This value should approximately
1293 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1294 everything is working properly.
1297 bool "sspi - Command to access spi device"
1300 SPI utility command.
1302 config DEFAULT_SPI_BUS
1303 int "default spi bus used by sspi command"
1307 config DEFAULT_SPI_MODE
1308 hex "default spi mode used by sspi command (see include/spi.h)"
1313 bool "tsi148 - Command to access tsi148 device"
1315 This provides various sub-commands to initialise and configure the
1316 Turndra tsi148 device. See the command help for full details.
1319 bool "Enable UFS - Universal Flash Subsystem commands"
1322 "This provides commands to initialise and configure universal flash
1326 bool "universe - Command to set up the Turndra Universe controller"
1328 This allows setting up the VMEbus provided by this controller.
1329 See the command help for full details.
1333 select HAVE_BLOCK_DEVICE
1339 select USB_FUNCTION_SDP
1341 Enables the command "sdp" which is used to have U-Boot emulating the
1342 Serial Download Protocol (SDP) via USB.
1346 depends on USB_FUNCTION_ROCKUSB
1348 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1349 read/write info, image to/from devices. This enable rockusb command
1350 support to communication with rockusb device. for more detail about
1351 this command, please read doc/README.rockusb.
1353 config CMD_USB_MASS_STORAGE
1354 bool "UMS usb mass storage"
1355 select USB_FUNCTION_MASS_STORAGE
1357 USB mass storage support
1364 VirtIO block device support
1370 This provides commands to control the watchdog timer devices.
1376 Enable the command "axi" for accessing AXI (Advanced eXtensible
1377 Interface) busses, a on-chip interconnect specification for managing
1378 functional blocks in SoC designs, which is also often used in designs
1379 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1383 menu "Shell scripting commands"
1389 Echo args to console
1395 Return true/false on integer compare.
1401 Run script from memory
1407 Evaluate boolean and math expressions and store the result in an env
1409 Also supports loading the value at a memory location into a variable.
1410 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1414 menu "Android support commands"
1416 config CMD_AB_SELECT
1419 depends on ANDROID_AB
1421 On Android devices with more than one boot slot (multiple copies of
1422 the kernel and system images) this provides a command to select which
1423 slot should be used to boot from and register the boot attempt. This
1424 is used by the new A/B update model where one slot is updated in the
1425 background while running from the other slot.
1432 bool "Network commands"
1442 bootp - boot image via network using BOOTP/TFTP protocol
1446 depends on CMD_BOOTP
1448 Boot image via network using DHCP/TFTP protocol
1450 config BOOTP_BOOTPATH
1451 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1453 depends on CMD_BOOTP
1455 Even though the config is called BOOTP_BOOTPATH, it stores the
1456 path in the variable 'rootpath'.
1459 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1461 depends on CMD_BOOTP
1463 The primary DNS server is stored as 'dnsip'. If two servers are
1464 returned, you must set BOOTP_DNS2 to store that second server IP
1468 bool "Store 'dnsip2' from BOOTP/DHCP server"
1469 depends on BOOTP_DNS
1471 If a DHCP client requests the DNS server IP from a DHCP server,
1472 it is possible that more than one DNS serverip is offered to the
1473 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1474 server IP will be stored in the additional environment
1475 variable "dnsip2". The first DNS serverip is always
1476 stored in the variable "dnsip", when BOOTP_DNS is defined.
1478 config BOOTP_GATEWAY
1479 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1481 depends on CMD_BOOTP
1483 config BOOTP_HOSTNAME
1484 bool "Request & store 'hostname' from BOOTP/DHCP server"
1486 depends on CMD_BOOTP
1488 The name may or may not be qualified with the local domain name.
1490 config BOOTP_PREFER_SERVERIP
1491 bool "serverip variable takes precedent over DHCP server IP."
1492 depends on CMD_BOOTP
1494 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1496 With this option enabled, the 'serverip' variable in the environment
1497 takes precedence over DHCP server IP and will only be set by the DHCP
1498 server if not already set in the environment.
1500 config BOOTP_SUBNETMASK
1501 bool "Request & store 'netmask' from BOOTP/DHCP server"
1503 depends on CMD_BOOTP
1505 config BOOTP_NTPSERVER
1506 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1507 depends on CMD_BOOTP
1512 Selecting this will allow capturing all Ethernet packets and store
1513 them in physical memory in a PCAP formated file,
1514 later to be analyzed by PCAP reader application (IE. WireShark).
1517 bool "Send PXE client arch to BOOTP/DHCP server"
1519 depends on CMD_BOOTP && CMD_PXE
1521 Supported for ARM, ARM64, and x86 for now.
1523 config BOOTP_PXE_CLIENTARCH
1525 depends on BOOTP_PXE
1526 default 0x16 if ARM64
1530 config BOOTP_VCI_STRING
1532 depends on CMD_BOOTP
1533 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1534 default "U-Boot.armv8" if ARM64
1535 default "U-Boot.arm" if ARM
1542 tftpboot - boot image via network using TFTP protocol
1546 depends on CMD_TFTPBOOT
1548 TFTP put command, for uploading files to a server
1552 depends on CMD_TFTPBOOT
1554 Act as a TFTP server and boot the first received file
1556 config NET_TFTP_VARS
1557 bool "Control TFTP timeout and count through environment"
1558 depends on CMD_TFTPBOOT
1561 If set, allows controlling the TFTP timeout through the
1562 environment variable tftptimeout, and the TFTP maximum
1563 timeout count through the variable tftptimeoutcountmax.
1564 If unset, timeout and maximum are hard-defined as 1 second
1565 and 10 timouts per TFTP transfer.
1570 Boot image via network using RARP/TFTP protocol
1576 Boot image via network using NFS protocol.
1582 If set, allows 802.3(clause 22) MII Management functions interface access
1583 The management interface specified in Clause 22 provides
1584 a simple, two signal, serial interface to connect a
1585 Station Management entity and a managed PHY for providing access
1586 to management parameters and services.
1587 The interface is referred to as the MII management interface.
1593 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1594 The MDIO interface is orthogonal to the MII interface and extends
1595 it by adding access to more registers through indirect addressing.
1600 Send ICMP ECHO_REQUEST to network host
1605 Perform CDP network configuration
1610 Synchronize RTC via network
1615 Lookup the IP of a hostname
1617 config CMD_LINK_LOCAL
1621 Acquire a network IP address using the link-local protocol
1628 Allow control of L2 Ethernet switch commands. These are supported
1629 by the vsc9953 Ethernet driver at present. Sub-commands allow
1630 operations such as enabling / disabling a port and
1631 viewing/maintaining the filtering database (FDB)
1637 Boot image via network using PXE protocol
1642 Wait for wake-on-lan Magic Packet
1646 menu "Misc commands"
1649 bool "Enable 'bmp' command"
1650 depends on LCD || DM_VIDEO || VIDEO
1652 This provides a way to obtain information about a BMP-format image
1653 and to display it. BMP (which presumably stands for BitMaP) is a
1654 file format defined by Microsoft which supports images of various
1655 depths, formats and compression methods. Headers on the file
1656 determine the formats used. This command can be used by first loading
1657 the image into RAM, then using this command to look at it or display
1660 config CMD_BOOTCOUNT
1662 depends on BOOTCOUNT_LIMIT
1664 Enable the bootcount command, which allows interrogation and
1665 reset of the bootcounter.
1668 bool "Enable board-specific commands"
1670 (deprecated: instead, please define a Kconfig option for each command)
1672 Some boards have board-specific commands which are only enabled
1673 during developemnt and need to be turned off for production. This
1674 option provides a way to control this. The commands that are enabled
1675 vary depending on the board.
1677 config CMD_BLOCK_CACHE
1678 bool "blkcache - control and stats for block cache"
1679 depends on BLOCK_CACHE
1680 default y if BLOCK_CACHE
1682 Enable the blkcache command, which can be used to control the
1683 operation of the cache functions.
1684 This is most useful when fine-tuning the operation of the cache
1685 during development, but also allows the cache to be disabled when
1686 it might hurt performance (e.g. when using the ums command).
1689 bool "icache or dcache"
1691 Enable the "icache" and "dcache" commands
1693 config CMD_CONITRACE
1694 bool "conitrace - trace console input codes"
1696 Enable the 'conitrace' command which displays the codes received
1697 from the console input as hexadecimal numbers.
1700 bool "Enable clear screen command 'cls'"
1701 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1704 Enable the 'cls' command which clears the screen contents
1705 on video frame buffer.
1708 bool "efidebug - display/configure UEFI environment"
1709 depends on EFI_LOADER
1710 select EFI_DEVICE_PATH_TO_TEXT
1713 Enable the 'efidebug' command which provides a subset of UEFI
1714 shell utility with simplified functionality. It will be useful
1715 particularly for managing boot parameters as well as examining
1716 various EFI status for debugging.
1718 config CMD_EXCEPTION
1719 bool "exception - raise exception"
1720 depends on ARM || RISCV || X86
1722 Enable the 'exception' command which allows to raise an exception.
1729 Enable the 'led' command which allows for control of LEDs supported
1730 by the board. The LEDs can be listed with 'led list' and controlled
1731 with led on/off/togle/blink. Any LED drivers can be controlled with
1732 this command, e.g. led_gpio.
1739 Enable the 'date' command for getting/setting the time/date in RTC
1745 Run commands and summarize execution time.
1748 bool "gettime - read elapsed time"
1750 Enable the 'gettime' command which reads the elapsed time since
1751 U-Boot started running. This shows the time in seconds and
1752 milliseconds. See also the 'bootstage' command which provides more
1753 flexibility for boot timing.
1760 Print bytes from the hardware random number generator.
1762 # TODO: rename to CMD_SLEEP
1767 Delay execution for some time
1770 bool "support for multiprocessor"
1772 This provides an option to brinup
1773 different processors in multiprocessor
1779 Access the system timer.
1785 This provides basic access to the U-Boot's sound support. The main
1786 feature is to play a beep.
1788 sound init - set up sound system
1789 sound play - play a sound
1795 Boot image via local extlinux.conf file
1801 This provides access to the QEMU firmware interface. The main
1802 feature is to allow easy loading of files passed to qemu-system
1803 via -kernel / -initrd
1805 source "cmd/mvebu/Kconfig"
1808 bool "terminal - provides a way to attach a serial terminal"
1810 Provides a 'cu'-like serial terminal command. This can be used to
1811 access other serial ports from the system console. The terminal
1812 is very simple with no special processing of characters. As with
1813 cu, you can press ~. (tilde followed by period) to exit.
1816 bool "uuid, guid - generation of unique IDs"
1819 This enables two commands:
1821 uuid - generate random Universally Unique Identifier
1822 guid - generate Globally Unique Identifier based on random UUID
1824 The two commands are very similar except for the endianness of the
1829 source "cmd/ti/Kconfig"
1831 config CMD_BOOTSTAGE
1832 bool "Enable the 'bootstage' command"
1833 depends on BOOTSTAGE
1835 Add a 'bootstage' command which supports printing a report
1836 and un/stashing of bootstage data.
1838 menu "Power commands"
1840 bool "Enable Driver Model PMIC command"
1843 This is the pmic command, based on a driver model pmic's API.
1844 Command features are unchanged:
1845 - list - list pmic devices
1846 - pmic dev <id> - show or [set] operating pmic device (NEW)
1847 - pmic dump - dump registers
1848 - pmic read address - read byte of register at address
1849 - pmic write address - write byte to register at address
1850 The only one change for this command is 'dev' subcommand.
1852 config CMD_REGULATOR
1853 bool "Enable Driver Model REGULATOR command"
1854 depends on DM_REGULATOR
1856 This command is based on driver model regulator's API.
1857 User interface features:
1858 - list - list regulator devices
1859 - regulator dev <id> - show or [set] operating regulator device
1860 - regulator info - print constraints info
1861 - regulator status - print operating status
1862 - regulator value <val] <-f> - print/[set] voltage value [uV]
1863 - regulator current <val> - print/[set] current value [uA]
1864 - regulator mode <id> - print/[set] operating mode id
1865 - regulator enable - enable the regulator output
1866 - regulator disable - disable the regulator output
1868 The '-f' (force) option can be used for set the value which exceeds
1869 the limits, which are found in device-tree and are kept in regulator's
1870 uclass platdata structure.
1874 menu "Security commands"
1876 bool "Enable the 'aes' command"
1879 This provides a means to encrypt and decrypt data using the AES
1880 (Advanced Encryption Standard). This algorithm uses a symetric key
1881 and is widely used as a streaming cipher. Different key lengths are
1882 supported by the algorithm but this command only supports 128 bits
1886 bool "Enable the 'blob' command"
1888 This is used with the Freescale secure boot mechanism.
1890 Freescale's SEC block has built-in Blob Protocol which provides
1891 a method for protecting user-defined data across system power
1892 cycles. SEC block protects data in a data structure called a Blob,
1893 which provides both confidentiality and integrity protection.
1895 Encapsulating data as a blob
1896 Each time that the Blob Protocol is used to protect data, a
1897 different randomly generated key is used to encrypt the data.
1898 This random key is itself encrypted using a key which is derived
1899 from SoC's non-volatile secret key and a 16 bit Key identifier.
1900 The resulting encrypted key along with encrypted data is called a
1901 blob. The non-volatile secure key is available for use only during
1904 During decapsulation, the reverse process is performed to get back
1908 blob enc - encapsulating data as a cryptgraphic blob
1909 blob dec - decapsulating cryptgraphic blob to get the data
1913 blob enc src dst len km
1915 Encapsulate and create blob of data $len bytes long
1916 at address $src and store the result at address $dst.
1917 $km is the 16 byte key modifier is also required for
1918 generation/use as key for cryptographic operation. Key
1919 modifier should be 16 byte long.
1921 blob dec src dst len km
1923 Decapsulate the blob of data at address $src and
1924 store result of $len byte at addr $dst.
1925 $km is the 16 byte key modifier is also required for
1926 generation/use as key for cryptographic operation. Key
1927 modifier should be 16 byte long.
1930 bool "Support 'hash' command"
1933 This provides a way to hash data in memory using various supported
1934 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1935 saved to memory or to an environment variable. It is also possible
1936 to verify a hash against data in memory.
1939 bool "Support the 'hvc' command"
1940 depends on ARM_SMCCC
1942 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1943 development and testing.
1946 bool "Support the 'smc' command"
1947 depends on ARM_SMCCC
1949 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1950 development and testing.
1956 Add -v option to verify data against a hash.
1966 bool "Enable the 'tpm' command"
1967 depends on TPM_V1 || TPM_V2
1968 select CMD_TPM_V1 if TPM_V1
1969 select CMD_TPM_V2 if TPM_V2
1971 This provides a means to talk to a TPM from the command line. A wide
1972 range of commands if provided - see 'tpm help' for details. The
1973 command requires a suitable TPM on your board and the correct driver
1979 bool "Enable the 'tpm test' command"
1982 This provides a a series of tests to confirm that the TPMv1.x is
1983 working correctly. The tests cover initialisation, non-volatile RAM,
1984 extend, global lock and checking that timing is within expectations.
1985 The tests pass correctly on Infineon TPMs but may need to be adjusted
1992 menu "Firmware commands"
1994 bool "Enable crosec command"
1998 Enable command-line access to the Chrome OS EC (Embedded
1999 Controller). This provides the 'crosec' command which has
2000 a number of sub-commands for performing EC tasks such as
2001 updating its flash, accessing a small saved context area
2002 and talking to the I2C bus behind the EC (if there is one).
2005 menu "Filesystem commands"
2007 bool "Enable the 'btrsubvol' command"
2010 This enables the 'btrsubvol' command to list subvolumes
2011 of a BTRFS filesystem. There are no special commands for
2012 listing BTRFS directories or loading BTRFS files - this
2013 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2014 when BTRFS is enabled (see FS_BTRFS).
2017 bool "Enable the 'cbfs' command"
2020 Define this to enable support for reading from a Coreboot
2021 filesystem. This is a ROM-based filesystem used for accessing files
2022 on systems that use coreboot as the first boot-loader and then load
2023 U-Boot to actually boot the Operating System. Available commands are
2024 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2027 bool "Enable the 'cramfs' command"
2028 depends on FS_CRAMFS
2030 This provides commands for dealing with CRAMFS (Compressed ROM
2031 filesystem). CRAMFS is useful when space is tight since files are
2032 compressed. Two commands are provided:
2034 cramfsls - lists files in a cramfs image
2035 cramfsload - loads a file from a cramfs image
2038 bool "ext2 command support"
2041 Enables EXT2 FS command
2044 bool "ext4 command support"
2047 Enables EXT4 FS command
2049 config CMD_EXT4_WRITE
2051 bool "ext4 write command support"
2054 Enables EXT4 FS write command
2057 bool "FAT command support"
2060 Support for the FAT fs
2062 config CMD_FS_GENERIC
2063 bool "filesystem commands"
2065 Enables filesystem commands (e.g. load, ls) that work for multiple
2069 bool "fsuuid command"
2071 Enables fsuuid command for filesystem UUID.
2074 bool "jffs2 command"
2077 Enables commands to support the JFFS2 (Journalling Flash File System
2078 version 2) filesystem. This enables fsload, ls and fsinfo which
2079 provide the ability to load files, list directories and obtain
2080 filesystem information.
2083 bool "MTD partition support"
2086 MTD partitioning tool support.
2087 It is strongly encouraged to avoid using this command
2088 anymore along with 'sf', 'nand', 'onenand'. One can still
2089 declare the partitions in the mtdparts environment variable
2090 but better use the MTD stack and the 'mtd' command instead.
2092 config CMD_MTDPARTS_SPREAD
2093 bool "Padd partition size to take account of bad blocks"
2094 depends on CMD_MTDPARTS
2096 This enables the 'spread' sub-command of the mtdparts command.
2097 This command will modify the existing mtdparts variable by increasing
2098 the size of the partitions such that 1) each partition's net size is
2099 at least as large as the size specified in the mtdparts variable and
2100 2) each partition starts on a good block.
2102 config CMD_MTDPARTS_SHOW_NET_SIZES
2103 bool "Show net size (w/o bad blocks) of partitions"
2104 depends on CMD_MTDPARTS
2106 Adds two columns to the printed partition table showing the
2107 effective usable size of a partition, if bad blocks are taken
2110 config MTDIDS_DEFAULT
2111 string "Default MTD IDs"
2112 depends on MTD || SPI_FLASH
2114 Defines a default MTD IDs list for use with MTD partitions in the
2115 Linux MTD command line partitions format.
2117 config MTDPARTS_DEFAULT
2118 string "Default MTD partition scheme"
2119 depends on MTD || SPI_FLASH
2121 Defines a default MTD partitioning scheme in the Linux MTD command
2122 line partitions format
2125 bool "reiser - Access to reiserfs filesystems"
2127 This provides two commands which operate on a resierfs filesystem,
2128 commonly used some years ago:
2130 reiserls - list files
2131 reiserload - load a file
2134 bool "yaffs2 - Access of YAFFS2 filesystem"
2138 This provides commands for accessing a YAFFS2 filesystem. Yet
2139 Another Flash Filesystem 2 is a filesystem designed specifically
2140 for NAND flash. It incorporates bad-block management and ensures
2141 that device writes are sequential regardless of filesystem
2145 bool "zfs - Access of ZFS filesystem"
2147 This provides commands to accessing a ZFS filesystem, commonly used
2148 on Solaris systems. Two sub-commands are provided:
2150 zfsls - list files in a directory
2151 zfsload - load a file
2153 See doc/README.zfs for more details.
2157 menu "Debug commands"
2162 The bedbug (emBEDded deBUGger) command provides debugging features
2163 for some PowerPC processors. For details please see the
2164 documentation in doc/README.bedbug.
2167 bool "diag - Board diagnostics"
2169 This command provides access to board diagnostic tests. These are
2170 called Power-on Self Tests (POST). The command allows listing of
2171 available tests and running either all the tests, or specific tests
2175 bool "irq - Show information about interrupts"
2176 depends on !ARM && !MIPS && !SH
2178 This enables two commands:
2180 interrupts - enable or disable interrupts
2181 irqinfo - print device-specific interrupt information
2184 bool "kgdb - Allow debugging of U-Boot with gdb"
2187 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2188 over a serial link for debugging purposes. This allows
2189 single-stepping, inspecting variables, etc. This is supported only
2190 on PowerPC at present.
2193 bool "log - Generation, control and access to logging"
2196 This provides access to logging features. It allows the output of
2197 log data to be controlled to a limited extent (setting up the default
2198 maximum log level for emitting of records). It also provides access
2199 to a command used for testing the log system.
2202 bool "trace - Support tracing of function calls and timing"
2204 Enables a command to control using of function tracing within
2205 U-Boot. This allows recording of call traces including timing
2206 information. The command can write data to memory for exporting
2207 for analysis (e.g. using bootchart). See doc/README.trace for full
2211 bool "avb - Android Verified Boot 2.0 operations"
2212 depends on AVB_VERIFY
2215 Enables a "avb" command to perform verification of partitions using
2216 Android Verified Boot 2.0 functionality. It includes such subcommands:
2217 avb init - initialize avb2 subsystem
2218 avb read_rb - read rollback index
2219 avb write_rb - write rollback index
2220 avb is_unlocked - check device lock state
2221 avb get_uuid - read and print uuid of a partition
2222 avb read_part - read data from partition
2223 avb read_part_hex - read data from partition and output to stdout
2224 avb write_part - write data to partition
2225 avb verify - run full verification chain
2229 tristate "Enable UBI - Unsorted block images commands"
2232 UBI is a software layer above MTD layer which admits use of LVM-like
2233 logical volumes on top of MTD devices, hides some complexities of
2234 flash chips like wear and bad blocks and provides some other useful
2235 capabilities. Please, consult the MTD web site for more details
2236 (www.linux-mtd.infradead.org). Activate this option if you want
2237 to use U-Boot UBI commands.
2238 It is also strongly encouraged to also enable CONFIG_MTD to get full
2241 config CMD_UBI_RENAME
2242 bool "Enable rename"
2246 Enable a "ubi" command to rename ubi volume:
2247 ubi rename <oldname> <newname>
2250 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2252 default y if CMD_UBI
2255 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob