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
492 config CMD_THOR_DOWNLOAD
493 bool "thor - TIZEN 'thor' download"
496 Implements the 'thor' download protocol. This is a way of
497 downloading a software update over USB from an attached host.
498 There is no documentation about this within the U-Boot source code
499 but you should be able to find something on the interwebs.
502 bool "zboot - x86 boot command"
504 With x86 machines it is common to boot a bzImage file which
505 contains both a kernel and a setup.bin file. The latter includes
506 configuration information from the dark ages which x86 boards still
507 need to pick things out of.
509 Consider using FIT in preference to this since it supports directly
510 booting both 32- and 64-bit kernels, as well as secure boot.
511 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
515 menu "Environment commands"
518 bool "ask for env variable"
520 Ask for environment variable
538 Edit environment variable.
543 Allow for searching environment variables
549 Save all environment variables into the compiled-in persistent
555 depends on CMD_SAVEENV
557 Erase environment variables from the compiled-in persistent
560 config CMD_ENV_EXISTS
564 Check if a variable is defined in the environment for use in
567 config CMD_ENV_CALLBACK
568 bool "env callbacks - print callbacks and their associated variables"
570 Some environment variable have callbacks defined by
571 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
572 For example changing "baudrate" adjust the serial baud rate. This
573 command lists the currently defined callbacks.
576 bool "env flags -print variables that have non-default flags"
578 Some environment variables have special flags that control their
579 behaviour. For example, serial# can only be written once and cannot
580 be deleted. This command shows the variables that have special
583 config CMD_NVEDIT_EFI
584 bool "env [set|print] -e - set/print UEFI variables"
585 depends on EFI_LOADER
588 UEFI variables are encoded as some form of U-Boot variables.
589 If enabled, we are allowed to set/print UEFI variables using
590 "env" command with "-e" option without knowing details.
592 config CMD_NVEDIT_INFO
593 bool "env info - print or evaluate environment information"
595 Print environment information:
596 - env_valid : is environment valid
597 - env_ready : is environment imported into hash table
598 - env_use_default : is default environment used
600 This command can be optionally used for evaluation in scripts:
601 [-d] : evaluate whether default environment is used
602 [-p] : evaluate whether environment can be persisted
603 The result of multiple evaluations will be combined with AND.
607 menu "Memory commands"
612 Compute binary operations (xor, or, and) of byte arrays of arbitrary
613 size from memory and store the result in memory or the environment.
626 Add -v option to verify data against a crc32 checksum.
629 bool "eeprom - EEPROM subsystem"
631 (deprecated, needs conversion to driver model)
632 Provides commands to read and write EEPROM (Electrically Erasable
633 Programmable Read Only Memory) chips that are connected over an
636 config CMD_EEPROM_LAYOUT
637 bool "Enable layout-aware eeprom commands"
638 depends on CMD_EEPROM
640 (deprecated, needs conversion to driver model)
641 When enabled, additional eeprom sub-commands become available.
643 eeprom print - prints the contents of the eeprom in a human-readable
644 way (eeprom layout fields, and data formatted to be fit for human
647 eeprom update - allows user to update eeprom fields by specifying
648 the field name, and providing the new data in a human readable format
649 (same format as displayed by the eeprom print command).
651 Both commands can either auto detect the layout, or be told which
655 __weak int parse_layout_version(char *str)
656 - override to provide your own layout name parsing
657 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
659 - override to setup the layout metadata based on the version
660 __weak int eeprom_layout_detect(unsigned char *data)
661 - override to provide your own algorithm for detecting layout
664 - contains various printing and updating functions for common
665 types of eeprom fields. Can be used for defining
668 config EEPROM_LAYOUT_HELP_STRING
669 string "Tells user what layout names are supported"
670 depends on CMD_EEPROM_LAYOUT
671 default "<not defined>"
673 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
679 Infinite write loop on address range
686 Compute MD5 checksum.
691 depends on CMD_MD5SUM
693 Add -v option to verify data against an MD5 checksum.
698 Display memory information.
701 bool "md, mm, nm, mw, cp, cmp, base, loop"
706 mm - memory modify (auto-incrementing address)
707 nm - memory modify (constant address)
708 mw - memory write (fill)
711 base - print or set address offset
712 loop - initialize loop on address range
715 bool "ms - Memory search"
717 Memory-search command
719 This allows searching through a region of memory looking for hex
720 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
721 support it). It is also possible to search for a string. The
722 command accepts a memory range and a list of values to search for.
723 The values need to appear in memory in the same order they are given
724 in the command. At most 10 matches can be returned at a time, but
725 pressing return will show the next 10 matches. Environment variables
726 are set for use with scripting (memmatches, memaddr, mempos).
729 bool "Enable cyclic md/mw commands"
730 depends on CMD_MEMORY
732 Add the "mdc" and "mwc" memory commands. These are cyclic
737 This command will print 4 bytes (10,11,12,13) each 500 ms.
739 => mwc.l 100 12345678 10
740 This command will write 12345678 to address 100 all 10 ms.
745 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
747 random - fill memory with random data
752 Simple RAM read/write test.
756 config SYS_ALT_MEMTEST
757 bool "Alternative test"
759 Use a more complete alternative memory test.
761 config SYS_MEMTEST_START
762 hex "default start address for mtest"
765 This is the default start address for mtest for simple read/write
766 test. If no arguments are given to mtest, default address is used
769 config SYS_MEMTEST_END
770 hex "default end address for mtest"
773 This is the default end address for mtest for simple read/write
774 test. If no arguments are given to mtest, default address is used
783 Compute SHA1 checksum.
785 config SHA1SUM_VERIFY
787 depends on CMD_SHA1SUM
789 Add -v option to verify data against a SHA1 checksum.
792 bool "strings - display strings in memory"
794 This works similarly to the Unix 'strings' command except that it
795 works with a memory range. String of printable characters found
796 within the range are displayed. The minimum number of characters
797 for a sequence to be considered a string can be provided.
801 menu "Compression commands"
805 default y if CMD_BOOTI
808 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
813 default y if CMD_BOOTI
816 Support decompressing an LZ4 image from memory region.
820 default y if CMD_BOOTI
823 Uncompress a zip-compressed memory region.
827 select GZIP_COMPRESSED
829 Compress a memory region with zlib deflate method.
833 menu "Device access commands"
836 #depends on FLASH_CFI_DRIVER
839 ARM Ltd reference designs flash partition access
842 bool "adc - Access Analog to Digital Converters info and data"
846 Shows ADC device info and permit printing one-shot analog converted
847 data from a named Analog to Digital Converter.
852 depends on PARTITIONS
854 Read/modify/write the fields of Bootloader Control Block, usually
855 stored on the flash "misc" partition with its structure defined in:
856 https://android.googlesource.com/platform/bootable/recovery/+/master/
857 bootloader_message/include/bootloader_message/bootloader_message.h
859 Some real-life use-cases include (but are not limited to):
860 - Determine the "boot reason" (and act accordingly):
861 https://source.android.com/devices/bootloader/boot-reason
862 - Get/pass a list of commands from/to recovery:
863 https://android.googlesource.com/platform/bootable/recovery
864 - Inspect/dump the contents of the BCB fields
867 bool "bind/unbind - Bind or unbind a device to/from a driver"
870 Bind or unbind a device to/from a driver from the command line.
871 This is useful in situations where a device may be handled by several
872 drivers. For example, this can be used to bind a UDC to the usb ether
873 gadget driver from the command line.
876 bool "clk - Show clock frequencies"
879 Shows clock frequences by calling a sock_clk_dump() hook function.
880 This is depreated in favour of using the CLK uclass and accessing
881 clock values from associated drivers. However currently no command
885 bool "demo - Demonstration commands for driver model"
888 Provides a 'demo' command which can be used to play around with
889 driver model. To use this properly you will need to enable one or
890 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
891 Otherwise you will always get an empty list of devices. The demo
892 devices are defined in the sandbox device tree, so the easiest
893 option is to use sandbox and pass the -d point to sandbox's
900 Enables the command "dfu" which is used to have U-Boot create a DFU
901 class device via USB. This command requires that the "dfu_alt_info"
902 environment variable be set and define the alt settings to expose to
906 bool "dm - Access to driver model information"
909 Provides access to driver model data structures and information,
910 such as a list of devices, list of uclasses and the state of each
911 device (e.g. activated). This is not required for operation, but
912 can be useful to see the state of driver model for debugging or
916 bool "fastboot - Android fastboot support"
919 This enables the command "fastboot" which enables the Android
920 fastboot mode for the platform. Fastboot is a protocol for
921 downloading images, flashing and device control used on
922 Android devices. Fastboot requires either the network stack
923 enabled or support for acting as a USB device.
925 See doc/android/fastboot.rst for more information.
928 bool "flinfo, erase, protect"
930 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
933 flinfo - print FLASH memory information
935 protect - enable or disable FLASH write protection
944 config CMD_FPGA_LOADBP
945 bool "fpga loadbp - load partial bitstream (Xilinx only)"
948 Supports loading an FPGA device from a bitstream buffer containing
951 config CMD_FPGA_LOADFS
952 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
955 Supports loading an FPGA device from a FAT filesystem.
957 config CMD_FPGA_LOADMK
958 bool "fpga loadmk - load bitstream from image"
961 Supports loading an FPGA device from a image generated by mkimage.
963 config CMD_FPGA_LOADP
964 bool "fpga loadp - load partial bitstream"
967 Supports loading an FPGA device from a bitstream buffer containing
970 config CMD_FPGA_LOAD_SECURE
971 bool "fpga loads - loads secure bitstreams (Xilinx only)"
974 Enables the fpga loads command which is used to load secure
975 (authenticated or encrypted or both) bitstreams on to FPGA.
978 bool "fpgad - dump FPGA registers"
980 (legacy, needs conversion to driver model)
981 Provides a way to dump FPGA registers by calling the board-specific
982 fpga_get_reg() function. This functions similarly to the 'md'
986 bool "fuse - support for the fuse subssystem"
988 (deprecated - needs conversion to driver model)
989 This allows reading, sensing, programming or overriding fuses
990 which control the behaviour of the device. The command uses the
999 bool "GPT (GUID Partition Table) command"
1000 select EFI_PARTITION
1001 select HAVE_BLOCK_DEVICE
1002 select PARTITION_UUIDS
1005 Enable the 'gpt' command to ready and write GPT style partition
1009 bool "GPT Random UUID generation"
1012 Enable the generation of partitions with random UUIDs if none
1015 config CMD_GPT_RENAME
1016 bool "GPT partition renaming commands"
1019 Enables the 'gpt' command to interchange names on two GPT
1020 partitions via the 'gpt swap' command or to rename single
1021 partitions via the 'rename' command.
1024 bool "ide - Support for IDE drivers"
1027 Provides an 'ide' command which allows accessing the IDE drive,
1028 reseting the IDE interface, printing the partition table and
1029 geting device info. It also enables the 'diskboot' command which
1030 permits booting from an IDE drive.
1033 bool "io - Support for performing I/O accesses"
1035 Provides an 'iod' command to display I/O space and an 'iow' command
1036 to write values to the I/O space. This can be useful for manually
1037 checking the state of devices during boot when debugging device
1041 bool "iotrace - Support for tracing I/O activity"
1043 Provides an 'iotrace' command which supports recording I/O reads and
1044 writes in a trace buffer in memory . It also maintains a checksum
1045 of the trace records (even if space is exhausted) so that the
1046 sequence of I/O accesses can be verified.
1048 When debugging drivers it is useful to see what I/O accesses were
1049 done and in what order.
1051 Even if the individual accesses are of little interest it can be
1052 useful to verify that the access pattern is consistent each time
1053 an operation is performed. In this case a checksum can be used to
1054 characterise the operation of a driver. The checksum can be compared
1055 across different runs of the operation to verify that the driver is
1058 In particular, when performing major refactoring of the driver, where
1059 the access pattern should not change, the checksum provides assurance
1060 that the refactoring work has not broken the driver.
1062 This works by sneaking into the io.h heder for an architecture and
1063 redirecting I/O accesses through iotrace's tracing mechanism.
1065 For now no commands are provided to examine the trace buffer. The
1066 format is fairly simple, so 'md' is a reasonable substitute.
1068 Note: The checksum feature is only useful for I/O regions where the
1069 contents do not change outside of software control. Where this is not
1070 suitable you can fall back to manually comparing the addresses. It
1071 might be useful to enhance tracing to only checksum the accesses and
1072 not the data read/written.
1082 bool "w1 - Support for Dallas 1-Wire protocol"
1084 Dallas 1-wire protocol support
1090 Load a binary file over serial line.
1096 Load an S-Record file over serial line
1100 bool "lsblk - list block drivers and devices"
1102 Print list of available block device drivers, and for each, the list
1103 of known block devices.
1108 MMC memory mapped support.
1112 config CMD_BKOPS_ENABLE
1113 bool "mmc bkops enable"
1117 Enable command for setting manual background operations handshake
1118 on a eMMC device. The feature is optionally available on eMMC devices
1119 conforming to standard >= 4.41.
1122 bool "Enable support for RPMB in the mmc command"
1123 depends on SUPPORT_EMMC_RPMB
1125 Enable the commands for reading, writing and programming the
1126 key for the Replay Protection Memory Block partition in eMMC.
1128 config CMD_MMC_SWRITE
1130 depends on MMC_WRITE
1133 Enable support for the "mmc swrite" command to write Android sparse
1141 select MTD_PARTITIONS
1143 MTD commands support.
1147 default y if NAND_SUNXI
1148 depends on MTD_RAW_NAND
1153 config CMD_NAND_TRIMFFS
1154 bool "nand write.trimffs"
1155 default y if ARCH_SUNXI
1157 Allows one to skip empty pages when flashing something on a NAND.
1159 config CMD_NAND_LOCK_UNLOCK
1160 bool "nand lock/unlock"
1162 NAND locking support.
1164 config CMD_NAND_TORTURE
1167 NAND torture support.
1176 NVM Express device support
1179 bool "onenand - access to onenand device"
1182 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1183 various useful features. This command allows reading, writing,
1184 and erasing blocks. It allso provides a way to show and change
1185 bad blocks, and test the device.
1190 Enable the 'osd' command which allows to query information from and
1191 write text data to a on-screen display (OSD) device; a virtual device
1192 associated with a display capable of displaying a text overlay on the
1193 display it's associated with..
1197 select HAVE_BLOCK_DEVICE
1198 select PARTITION_UUIDS
1200 Read and display information about the partition table on
1204 bool "pci - Access PCI devices"
1206 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1207 used on some devices to allow the CPU to communicate with its
1208 peripherals. Sub-commands allow bus enumeration, displaying and
1209 changing configuration space and a few other features.
1212 bool "pinmux - show pins muxing"
1213 default y if PINCTRL
1215 Parse all available pin-controllers and show pins muxing. This
1216 is useful for debug purpoer to check the pin muxing and to know if
1217 a pin is configured as a GPIO or as an alternate function.
1222 Poweroff/Shutdown the system
1225 bool "read - Read binary data from a partition"
1227 Provides low-level access to the data in a partition.
1229 config CMD_REMOTEPROC
1231 depends on REMOTEPROC
1233 Support for Remote Processor control
1236 bool "sata - Access SATA subsystem"
1239 SATA (Serial Advanced Technology Attachment) is a serial bus
1240 standard for connecting to hard drives and other storage devices.
1241 This command provides information about attached devices and allows
1242 reading, writing and other operations.
1244 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1245 Attachment, where AT refers to an IBM AT (Advanced Technology)
1246 computer released in 1984.
1249 bool "saves - Save a file over serial in S-Record format"
1251 Provides a way to save a binary file using the Motorola S-Record
1252 format over the serial line.
1255 bool "scsi - Access to SCSI devices"
1258 This provides a 'scsi' command which provides access to SCSI (Small
1259 Computer System Interface) devices. The command provides a way to
1260 scan the bus, reset the bus, read and write data and get information
1264 bool "sdram - Print SDRAM configuration information"
1266 Provides information about attached SDRAM. This assumed that the
1267 SDRAM has an EEPROM with information that can be read using the
1268 I2C bus. This is only available on some boards.
1272 depends on DM_SPI_FLASH || SPI_FLASH
1273 default y if DM_SPI_FLASH
1278 bool "sf test - Allow testing of SPI flash"
1281 Provides a way to test that SPI flash is working correctly. The
1282 test is destructive, in that an area of SPI flash must be provided
1283 for the test to use. Performance information is also provided,
1284 measuring the performance of reading, writing and erasing in
1285 Mbps (Million Bits Per Second). This value should approximately
1286 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1287 everything is working properly.
1290 bool "sspi - Command to access spi device"
1293 SPI utility command.
1295 config DEFAULT_SPI_BUS
1296 int "default spi bus used by sspi command"
1300 config DEFAULT_SPI_MODE
1301 hex "default spi mode used by sspi command (see include/spi.h)"
1306 bool "tsi148 - Command to access tsi148 device"
1308 This provides various sub-commands to initialise and configure the
1309 Turndra tsi148 device. See the command help for full details.
1312 bool "Enable UFS - Universal Flash Subsystem commands"
1315 "This provides commands to initialise and configure universal flash
1319 bool "universe - Command to set up the Turndra Universe controller"
1321 This allows setting up the VMEbus provided by this controller.
1322 See the command help for full details.
1326 select HAVE_BLOCK_DEVICE
1332 select USB_FUNCTION_SDP
1334 Enables the command "sdp" which is used to have U-Boot emulating the
1335 Serial Download Protocol (SDP) via USB.
1339 depends on USB_FUNCTION_ROCKUSB
1341 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1342 read/write info, image to/from devices. This enable rockusb command
1343 support to communication with rockusb device. for more detail about
1344 this command, please read doc/README.rockusb.
1346 config CMD_USB_MASS_STORAGE
1347 bool "UMS usb mass storage"
1348 select USB_FUNCTION_MASS_STORAGE
1350 USB mass storage support
1357 VirtIO block device support
1363 This provides commands to control the watchdog timer devices.
1369 Enable the command "axi" for accessing AXI (Advanced eXtensible
1370 Interface) busses, a on-chip interconnect specification for managing
1371 functional blocks in SoC designs, which is also often used in designs
1372 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1376 menu "Shell scripting commands"
1382 Echo args to console
1388 Return true/false on integer compare.
1394 Run script from memory
1400 Evaluate boolean and math expressions and store the result in an env
1402 Also supports loading the value at a memory location into a variable.
1403 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1407 menu "Android support commands"
1409 config CMD_AB_SELECT
1412 depends on ANDROID_AB
1414 On Android devices with more than one boot slot (multiple copies of
1415 the kernel and system images) this provides a command to select which
1416 slot should be used to boot from and register the boot attempt. This
1417 is used by the new A/B update model where one slot is updated in the
1418 background while running from the other slot.
1425 bool "Network commands"
1435 bootp - boot image via network using BOOTP/TFTP protocol
1439 depends on CMD_BOOTP
1441 Boot image via network using DHCP/TFTP protocol
1443 config BOOTP_BOOTPATH
1444 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1446 depends on CMD_BOOTP
1448 Even though the config is called BOOTP_BOOTPATH, it stores the
1449 path in the variable 'rootpath'.
1452 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1454 depends on CMD_BOOTP
1456 The primary DNS server is stored as 'dnsip'. If two servers are
1457 returned, you must set BOOTP_DNS2 to store that second server IP
1461 bool "Store 'dnsip2' from BOOTP/DHCP server"
1462 depends on BOOTP_DNS
1464 If a DHCP client requests the DNS server IP from a DHCP server,
1465 it is possible that more than one DNS serverip is offered to the
1466 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1467 server IP will be stored in the additional environment
1468 variable "dnsip2". The first DNS serverip is always
1469 stored in the variable "dnsip", when BOOTP_DNS is defined.
1471 config BOOTP_GATEWAY
1472 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1474 depends on CMD_BOOTP
1476 config BOOTP_HOSTNAME
1477 bool "Request & store 'hostname' from BOOTP/DHCP server"
1479 depends on CMD_BOOTP
1481 The name may or may not be qualified with the local domain name.
1483 config BOOTP_PREFER_SERVERIP
1484 bool "serverip variable takes precedent over DHCP server IP."
1485 depends on CMD_BOOTP
1487 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1489 With this option enabled, the 'serverip' variable in the environment
1490 takes precedence over DHCP server IP and will only be set by the DHCP
1491 server if not already set in the environment.
1493 config BOOTP_SUBNETMASK
1494 bool "Request & store 'netmask' from BOOTP/DHCP server"
1496 depends on CMD_BOOTP
1498 config BOOTP_NTPSERVER
1499 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1500 depends on CMD_BOOTP
1505 Selecting this will allow capturing all Ethernet packets and store
1506 them in physical memory in a PCAP formated file,
1507 later to be analyzed by PCAP reader application (IE. WireShark).
1510 bool "Send PXE client arch to BOOTP/DHCP server"
1512 depends on CMD_BOOTP && CMD_PXE
1514 Supported for ARM, ARM64, and x86 for now.
1516 config BOOTP_PXE_CLIENTARCH
1518 depends on BOOTP_PXE
1519 default 0x16 if ARM64
1523 config BOOTP_VCI_STRING
1525 depends on CMD_BOOTP
1526 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1527 default "U-Boot.armv8" if ARM64
1528 default "U-Boot.arm" if ARM
1535 tftpboot - boot image via network using TFTP protocol
1539 depends on CMD_TFTPBOOT
1541 TFTP put command, for uploading files to a server
1545 depends on CMD_TFTPBOOT
1547 Act as a TFTP server and boot the first received file
1549 config NET_TFTP_VARS
1550 bool "Control TFTP timeout and count through environment"
1551 depends on CMD_TFTPBOOT
1554 If set, allows controlling the TFTP timeout through the
1555 environment variable tftptimeout, and the TFTP maximum
1556 timeout count through the variable tftptimeoutcountmax.
1557 If unset, timeout and maximum are hard-defined as 1 second
1558 and 10 timouts per TFTP transfer.
1563 Boot image via network using RARP/TFTP protocol
1569 Boot image via network using NFS protocol.
1575 If set, allows 802.3(clause 22) MII Management functions interface access
1576 The management interface specified in Clause 22 provides
1577 a simple, two signal, serial interface to connect a
1578 Station Management entity and a managed PHY for providing access
1579 to management parameters and services.
1580 The interface is referred to as the MII management interface.
1586 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1587 The MDIO interface is orthogonal to the MII interface and extends
1588 it by adding access to more registers through indirect addressing.
1593 Send ICMP ECHO_REQUEST to network host
1598 Perform CDP network configuration
1603 Synchronize RTC via network
1608 Lookup the IP of a hostname
1610 config CMD_LINK_LOCAL
1614 Acquire a network IP address using the link-local protocol
1621 Allow control of L2 Ethernet switch commands. These are supported
1622 by the vsc9953 Ethernet driver at present. Sub-commands allow
1623 operations such as enabling / disabling a port and
1624 viewing/maintaining the filtering database (FDB)
1630 Boot image via network using PXE protocol
1635 Wait for wake-on-lan Magic Packet
1639 menu "Misc commands"
1642 bool "Enable 'bmp' command"
1643 depends on LCD || DM_VIDEO || VIDEO
1645 This provides a way to obtain information about a BMP-format image
1646 and to display it. BMP (which presumably stands for BitMaP) is a
1647 file format defined by Microsoft which supports images of various
1648 depths, formats and compression methods. Headers on the file
1649 determine the formats used. This command can be used by first loading
1650 the image into RAM, then using this command to look at it or display
1653 config CMD_BOOTCOUNT
1655 depends on BOOTCOUNT_LIMIT
1657 Enable the bootcount command, which allows interrogation and
1658 reset of the bootcounter.
1661 bool "Enable board-specific commands"
1663 (deprecated: instead, please define a Kconfig option for each command)
1665 Some boards have board-specific commands which are only enabled
1666 during developemnt and need to be turned off for production. This
1667 option provides a way to control this. The commands that are enabled
1668 vary depending on the board.
1670 config CMD_BLOCK_CACHE
1671 bool "blkcache - control and stats for block cache"
1672 depends on BLOCK_CACHE
1673 default y if BLOCK_CACHE
1675 Enable the blkcache command, which can be used to control the
1676 operation of the cache functions.
1677 This is most useful when fine-tuning the operation of the cache
1678 during development, but also allows the cache to be disabled when
1679 it might hurt performance (e.g. when using the ums command).
1682 bool "icache or dcache"
1684 Enable the "icache" and "dcache" commands
1686 config CMD_CONITRACE
1687 bool "conitrace - trace console input codes"
1689 Enable the 'conitrace' command which displays the codes received
1690 from the console input as hexadecimal numbers.
1693 bool "Enable clear screen command 'cls'"
1694 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1697 Enable the 'cls' command which clears the screen contents
1698 on video frame buffer.
1701 bool "efidebug - display/configure UEFI environment"
1702 depends on EFI_LOADER
1703 select EFI_DEVICE_PATH_TO_TEXT
1706 Enable the 'efidebug' command which provides a subset of UEFI
1707 shell utility with simplified functionality. It will be useful
1708 particularly for managing boot parameters as well as examining
1709 various EFI status for debugging.
1711 config CMD_EXCEPTION
1712 bool "exception - raise exception"
1713 depends on ARM || RISCV || X86
1715 Enable the 'exception' command which allows to raise an exception.
1722 Enable the 'led' command which allows for control of LEDs supported
1723 by the board. The LEDs can be listed with 'led list' and controlled
1724 with led on/off/togle/blink. Any LED drivers can be controlled with
1725 this command, e.g. led_gpio.
1732 Enable the 'date' command for getting/setting the time/date in RTC
1739 Enable the 'rtc' command for low-level access to RTC devices.
1744 Run commands and summarize execution time.
1747 bool "gettime - read elapsed time"
1749 Enable the 'gettime' command which reads the elapsed time since
1750 U-Boot started running. This shows the time in seconds and
1751 milliseconds. See also the 'bootstage' command which provides more
1752 flexibility for boot timing.
1759 Print bytes from the hardware random number generator.
1761 # TODO: rename to CMD_SLEEP
1766 Delay execution for some time
1769 bool "support for multiprocessor"
1771 This provides an option to brinup
1772 different processors in multiprocessor
1778 Access the system timer.
1784 This provides basic access to the U-Boot's sound support. The main
1785 feature is to play a beep.
1787 sound init - set up sound system
1788 sound play - play a sound
1794 Boot image via local extlinux.conf file
1800 This provides access to the QEMU firmware interface. The main
1801 feature is to allow easy loading of files passed to qemu-system
1802 via -kernel / -initrd
1804 source "cmd/mvebu/Kconfig"
1807 bool "terminal - provides a way to attach a serial terminal"
1809 Provides a 'cu'-like serial terminal command. This can be used to
1810 access other serial ports from the system console. The terminal
1811 is very simple with no special processing of characters. As with
1812 cu, you can press ~. (tilde followed by period) to exit.
1815 bool "uuid, guid - generation of unique IDs"
1818 This enables two commands:
1820 uuid - generate random Universally Unique Identifier
1821 guid - generate Globally Unique Identifier based on random UUID
1823 The two commands are very similar except for the endianness of the
1828 source "cmd/ti/Kconfig"
1830 config CMD_BOOTSTAGE
1831 bool "Enable the 'bootstage' command"
1832 depends on BOOTSTAGE
1834 Add a 'bootstage' command which supports printing a report
1835 and un/stashing of bootstage data.
1837 menu "Power commands"
1839 bool "Enable Driver Model PMIC command"
1842 This is the pmic command, based on a driver model pmic's API.
1843 Command features are unchanged:
1844 - list - list pmic devices
1845 - pmic dev <id> - show or [set] operating pmic device (NEW)
1846 - pmic dump - dump registers
1847 - pmic read address - read byte of register at address
1848 - pmic write address - write byte to register at address
1849 The only one change for this command is 'dev' subcommand.
1851 config CMD_REGULATOR
1852 bool "Enable Driver Model REGULATOR command"
1853 depends on DM_REGULATOR
1855 This command is based on driver model regulator's API.
1856 User interface features:
1857 - list - list regulator devices
1858 - regulator dev <id> - show or [set] operating regulator device
1859 - regulator info - print constraints info
1860 - regulator status - print operating status
1861 - regulator value <val] <-f> - print/[set] voltage value [uV]
1862 - regulator current <val> - print/[set] current value [uA]
1863 - regulator mode <id> - print/[set] operating mode id
1864 - regulator enable - enable the regulator output
1865 - regulator disable - disable the regulator output
1867 The '-f' (force) option can be used for set the value which exceeds
1868 the limits, which are found in device-tree and are kept in regulator's
1869 uclass platdata structure.
1873 menu "Security commands"
1875 bool "Enable the 'aes' command"
1878 This provides a means to encrypt and decrypt data using the AES
1879 (Advanced Encryption Standard). This algorithm uses a symetric key
1880 and is widely used as a streaming cipher. Different key lengths are
1881 supported by the algorithm but this command only supports 128 bits
1885 bool "Enable the 'blob' command"
1887 This is used with the Freescale secure boot mechanism.
1889 Freescale's SEC block has built-in Blob Protocol which provides
1890 a method for protecting user-defined data across system power
1891 cycles. SEC block protects data in a data structure called a Blob,
1892 which provides both confidentiality and integrity protection.
1894 Encapsulating data as a blob
1895 Each time that the Blob Protocol is used to protect data, a
1896 different randomly generated key is used to encrypt the data.
1897 This random key is itself encrypted using a key which is derived
1898 from SoC's non-volatile secret key and a 16 bit Key identifier.
1899 The resulting encrypted key along with encrypted data is called a
1900 blob. The non-volatile secure key is available for use only during
1903 During decapsulation, the reverse process is performed to get back
1907 blob enc - encapsulating data as a cryptgraphic blob
1908 blob dec - decapsulating cryptgraphic blob to get the data
1912 blob enc src dst len km
1914 Encapsulate and create blob of data $len bytes long
1915 at address $src and store the result at address $dst.
1916 $km is the 16 byte key modifier is also required for
1917 generation/use as key for cryptographic operation. Key
1918 modifier should be 16 byte long.
1920 blob dec src dst len km
1922 Decapsulate the blob of data at address $src and
1923 store result of $len byte at addr $dst.
1924 $km is the 16 byte key modifier is also required for
1925 generation/use as key for cryptographic operation. Key
1926 modifier should be 16 byte long.
1929 bool "Support 'hash' command"
1932 This provides a way to hash data in memory using various supported
1933 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1934 saved to memory or to an environment variable. It is also possible
1935 to verify a hash against data in memory.
1938 bool "Support the 'hvc' command"
1939 depends on ARM_SMCCC
1941 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1942 development and testing.
1945 bool "Support the 'smc' command"
1946 depends on ARM_SMCCC
1948 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1949 development and testing.
1955 Add -v option to verify data against a hash.
1965 bool "Enable the 'tpm' command"
1966 depends on TPM_V1 || TPM_V2
1967 select CMD_TPM_V1 if TPM_V1
1968 select CMD_TPM_V2 if TPM_V2
1970 This provides a means to talk to a TPM from the command line. A wide
1971 range of commands if provided - see 'tpm help' for details. The
1972 command requires a suitable TPM on your board and the correct driver
1978 bool "Enable the 'tpm test' command"
1981 This provides a a series of tests to confirm that the TPMv1.x is
1982 working correctly. The tests cover initialisation, non-volatile RAM,
1983 extend, global lock and checking that timing is within expectations.
1984 The tests pass correctly on Infineon TPMs but may need to be adjusted
1991 menu "Firmware commands"
1993 bool "Enable crosec command"
1997 Enable command-line access to the Chrome OS EC (Embedded
1998 Controller). This provides the 'crosec' command which has
1999 a number of sub-commands for performing EC tasks such as
2000 updating its flash, accessing a small saved context area
2001 and talking to the I2C bus behind the EC (if there is one).
2004 menu "Filesystem commands"
2006 bool "Enable the 'btrsubvol' command"
2009 This enables the 'btrsubvol' command to list subvolumes
2010 of a BTRFS filesystem. There are no special commands for
2011 listing BTRFS directories or loading BTRFS files - this
2012 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2013 when BTRFS is enabled (see FS_BTRFS).
2016 bool "Enable the 'cbfs' command"
2019 Define this to enable support for reading from a Coreboot
2020 filesystem. This is a ROM-based filesystem used for accessing files
2021 on systems that use coreboot as the first boot-loader and then load
2022 U-Boot to actually boot the Operating System. Available commands are
2023 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2026 bool "Enable the 'cramfs' command"
2027 depends on FS_CRAMFS
2029 This provides commands for dealing with CRAMFS (Compressed ROM
2030 filesystem). CRAMFS is useful when space is tight since files are
2031 compressed. Two commands are provided:
2033 cramfsls - lists files in a cramfs image
2034 cramfsload - loads a file from a cramfs image
2037 bool "ext2 command support"
2040 Enables EXT2 FS command
2043 bool "ext4 command support"
2046 Enables EXT4 FS command
2048 config CMD_EXT4_WRITE
2050 bool "ext4 write command support"
2053 Enables EXT4 FS write command
2056 bool "FAT command support"
2059 Support for the FAT fs
2061 config CMD_FS_GENERIC
2062 bool "filesystem commands"
2064 Enables filesystem commands (e.g. load, ls) that work for multiple
2068 bool "fsuuid command"
2070 Enables fsuuid command for filesystem UUID.
2073 bool "jffs2 command"
2076 Enables commands to support the JFFS2 (Journalling Flash File System
2077 version 2) filesystem. This enables fsload, ls and fsinfo which
2078 provide the ability to load files, list directories and obtain
2079 filesystem information.
2082 bool "MTD partition support"
2085 MTD partitioning tool support.
2086 It is strongly encouraged to avoid using this command
2087 anymore along with 'sf', 'nand', 'onenand'. One can still
2088 declare the partitions in the mtdparts environment variable
2089 but better use the MTD stack and the 'mtd' command instead.
2091 config CMD_MTDPARTS_SPREAD
2092 bool "Padd partition size to take account of bad blocks"
2093 depends on CMD_MTDPARTS
2095 This enables the 'spread' sub-command of the mtdparts command.
2096 This command will modify the existing mtdparts variable by increasing
2097 the size of the partitions such that 1) each partition's net size is
2098 at least as large as the size specified in the mtdparts variable and
2099 2) each partition starts on a good block.
2101 config CMD_MTDPARTS_SHOW_NET_SIZES
2102 bool "Show net size (w/o bad blocks) of partitions"
2103 depends on CMD_MTDPARTS
2105 Adds two columns to the printed partition table showing the
2106 effective usable size of a partition, if bad blocks are taken
2109 config MTDIDS_DEFAULT
2110 string "Default MTD IDs"
2111 depends on MTD || SPI_FLASH
2113 Defines a default MTD IDs list for use with MTD partitions in the
2114 Linux MTD command line partitions format.
2116 config MTDPARTS_DEFAULT
2117 string "Default MTD partition scheme"
2118 depends on MTD || SPI_FLASH
2120 Defines a default MTD partitioning scheme in the Linux MTD command
2121 line partitions format
2124 bool "reiser - Access to reiserfs filesystems"
2126 This provides two commands which operate on a resierfs filesystem,
2127 commonly used some years ago:
2129 reiserls - list files
2130 reiserload - load a file
2133 bool "yaffs2 - Access of YAFFS2 filesystem"
2137 This provides commands for accessing a YAFFS2 filesystem. Yet
2138 Another Flash Filesystem 2 is a filesystem designed specifically
2139 for NAND flash. It incorporates bad-block management and ensures
2140 that device writes are sequential regardless of filesystem
2144 bool "zfs - Access of ZFS filesystem"
2146 This provides commands to accessing a ZFS filesystem, commonly used
2147 on Solaris systems. Two sub-commands are provided:
2149 zfsls - list files in a directory
2150 zfsload - load a file
2152 See doc/README.zfs for more details.
2156 menu "Debug commands"
2161 The bedbug (emBEDded deBUGger) command provides debugging features
2162 for some PowerPC processors. For details please see the
2163 documentation in doc/README.bedbug.
2166 bool "diag - Board diagnostics"
2168 This command provides access to board diagnostic tests. These are
2169 called Power-on Self Tests (POST). The command allows listing of
2170 available tests and running either all the tests, or specific tests
2174 bool "irq - Show information about interrupts"
2175 depends on !ARM && !MIPS && !SH
2177 This enables two commands:
2179 interrupts - enable or disable interrupts
2180 irqinfo - print device-specific interrupt information
2183 bool "kgdb - Allow debugging of U-Boot with gdb"
2186 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2187 over a serial link for debugging purposes. This allows
2188 single-stepping, inspecting variables, etc. This is supported only
2189 on PowerPC at present.
2192 bool "log - Generation, control and access to logging"
2195 This provides access to logging features. It allows the output of
2196 log data to be controlled to a limited extent (setting up the default
2197 maximum log level for emitting of records). It also provides access
2198 to a command used for testing the log system.
2201 bool "trace - Support tracing of function calls and timing"
2203 Enables a command to control using of function tracing within
2204 U-Boot. This allows recording of call traces including timing
2205 information. The command can write data to memory for exporting
2206 for analysis (e.g. using bootchart). See doc/README.trace for full
2210 bool "avb - Android Verified Boot 2.0 operations"
2211 depends on AVB_VERIFY
2214 Enables a "avb" command to perform verification of partitions using
2215 Android Verified Boot 2.0 functionality. It includes such subcommands:
2216 avb init - initialize avb2 subsystem
2217 avb read_rb - read rollback index
2218 avb write_rb - write rollback index
2219 avb is_unlocked - check device lock state
2220 avb get_uuid - read and print uuid of a partition
2221 avb read_part - read data from partition
2222 avb read_part_hex - read data from partition and output to stdout
2223 avb write_part - write data to partition
2224 avb verify - run full verification chain
2228 tristate "Enable UBI - Unsorted block images commands"
2231 UBI is a software layer above MTD layer which admits use of LVM-like
2232 logical volumes on top of MTD devices, hides some complexities of
2233 flash chips like wear and bad blocks and provides some other useful
2234 capabilities. Please, consult the MTD web site for more details
2235 (www.linux-mtd.infradead.org). Activate this option if you want
2236 to use U-Boot UBI commands.
2237 It is also strongly encouraged to also enable CONFIG_MTD to get full
2240 config CMD_UBI_RENAME
2241 bool "Enable rename"
2245 Enable a "ubi" command to rename ubi volume:
2246 ubi rename <oldname> <newname>
2249 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2251 default y if CMD_UBI
2254 UBIFS is a file system for flash devices which works on top of UBI.
git.openpandora.org / pandora-u-boot.git / blob