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.
275 depends on RISCV_SMODE && SBI_V02
277 Display information about the SBI implementation.
287 Run the command stored in the environment "bootcmd", i.e.
288 "bootd" does the same thing as "run bootcmd".
294 Boot an application image from the memory.
297 bool "Support booting UEFI FIT images"
298 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
301 Support booting UEFI FIT images via the bootm command.
306 Boot the Linux zImage
310 depends on ARM64 || RISCV
313 Boot an AArch64 Linux Kernel image from memory.
316 bool "Support booting Linux OS images"
317 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
320 Support booting the Linux kernel directly via a command such as bootm
324 bool "Support booting NetBSD (non-EFI) loader images"
328 Support booting NetBSD via the bootm command.
330 config BOOTM_OPENRTOS
331 bool "Support booting OPENRTOS / FreeRTOS images"
334 Support booting OPENRTOS / FreeRTOS via the bootm command.
337 bool "Support booting Enea OSE images"
338 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
341 Support booting Enea OSE images via the bootm command.
344 bool "Support booting Plan9 OS images"
348 Support booting Plan9 images via the bootm command.
351 bool "Support booting RTEMS OS images"
355 Support booting RTEMS images via the bootm command.
358 bool "Support booting VxWorks OS images"
362 Support booting VxWorks images via the bootm command.
366 depends on EFI_LOADER
369 Boot an EFI image from memory.
371 config CMD_BOOTEFI_HELLO_COMPILE
372 bool "Compile a standard EFI hello world binary for testing"
373 depends on CMD_BOOTEFI && !CPU_V7M
376 This compiles a standard EFI hello world application with U-Boot so
377 that it can be used with the test/py testing framework. This is useful
378 for testing that EFI is working at a basic level, and for bringing
379 up EFI support on a new architecture.
381 No additional space will be required in the resulting U-Boot binary
382 when this option is enabled.
384 config CMD_BOOTEFI_HELLO
385 bool "Allow booting a standard EFI hello world for testing"
386 depends on CMD_BOOTEFI_HELLO_COMPILE
387 default y if CMD_BOOTEFI_SELFTEST
389 This adds a standard EFI hello world application to U-Boot so that
390 it can be used with the 'bootefi hello' command. This is useful
391 for testing that EFI is working at a basic level, and for bringing
392 up EFI support on a new architecture.
394 source lib/efi_selftest/Kconfig
400 Add an ANSI terminal boot menu command.
405 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
406 image into RAM, dump image structure information, etc. Those dtb/dtbo
407 files should be merged in one dtb further, which needs to be passed to
408 the kernel, as part of a boot process.
412 depends on ANDROID_BOOT_IMAGE
414 Android Boot Image manipulation commands. Allows one to extract
415 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
416 obtain corresponding meta-information from boot.img.
418 See doc/android/boot-image.rst for details.
421 bool "bootelf, bootvx"
425 Boot an ELF/vxWorks image from the memory.
428 bool "Flattened Device Tree utility commands"
432 Do FDT related setup before booting into the Operating System.
438 Start an application at a given address.
444 Run the command in the given environment variable.
450 Print header information for application image.
455 List all images found in flash
461 Extract a part of a multi-image.
464 bool "spl export - Export boot information for Falcon boot"
467 Falcon mode allows booting directly from SPL into an Operating
468 System such as Linux, thus skipping U-Boot proper. See
469 doc/README.falcon for full information about how to use this
472 config CMD_SPL_NAND_OFS
473 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
474 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
477 This provides the offset of the command line arguments for Linux
478 when booting from NAND in Falcon mode. See doc/README.falcon
479 for full information about how to use this option (and also see
480 board/gateworks/gw_ventana/README for an example).
482 config CMD_SPL_NOR_OFS
483 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
484 depends on CMD_SPL && SPL_NOR_SUPPORT
487 This provides the offset of the command line arguments or dtb for
488 Linux when booting from NOR in Falcon mode.
490 config CMD_SPL_WRITE_SIZE
491 hex "Size of argument area"
495 This provides the size of the command-line argument area in NAND
496 flash used by Falcon-mode boot. See the documentation until CMD_SPL
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
611 The result of multiple evaluations will be combined with AND.
613 config CMD_NVEDIT_LOAD
616 Load all environment variables from the compiled-in persistent
619 config CMD_NVEDIT_SELECT
622 Select the compiled-in persistent storage of environment variables.
626 menu "Memory commands"
631 Compute binary operations (xor, or, and) of byte arrays of arbitrary
632 size from memory and store the result in memory or the environment.
636 default y if BLOBLIST
638 Show information about the bloblist, a collection of binary blobs
639 held in memory that persist between SPL and U-Boot. In the case of
640 x86 devices the bloblist can be used to hold ACPI tables so that they
641 remain available in memory.
654 Add -v option to verify data against a crc32 checksum.
657 bool "eeprom - EEPROM subsystem"
659 (deprecated, needs conversion to driver model)
660 Provides commands to read and write EEPROM (Electrically Erasable
661 Programmable Read Only Memory) chips that are connected over an
664 config CMD_EEPROM_LAYOUT
665 bool "Enable layout-aware eeprom commands"
666 depends on CMD_EEPROM
668 (deprecated, needs conversion to driver model)
669 When enabled, additional eeprom sub-commands become available.
671 eeprom print - prints the contents of the eeprom in a human-readable
672 way (eeprom layout fields, and data formatted to be fit for human
675 eeprom update - allows user to update eeprom fields by specifying
676 the field name, and providing the new data in a human readable format
677 (same format as displayed by the eeprom print command).
679 Both commands can either auto detect the layout, or be told which
683 __weak int parse_layout_version(char *str)
684 - override to provide your own layout name parsing
685 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
687 - override to setup the layout metadata based on the version
688 __weak int eeprom_layout_detect(unsigned char *data)
689 - override to provide your own algorithm for detecting layout
692 - contains various printing and updating functions for common
693 types of eeprom fields. Can be used for defining
696 config EEPROM_LAYOUT_HELP_STRING
697 string "Tells user what layout names are supported"
698 depends on CMD_EEPROM_LAYOUT
699 default "<not defined>"
701 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
707 Infinite write loop on address range
714 Compute MD5 checksum.
719 depends on CMD_MD5SUM
721 Add -v option to verify data against an MD5 checksum.
726 Display memory information.
729 bool "md, mm, nm, mw, cp, cmp, base, loop"
734 mm - memory modify (auto-incrementing address)
735 nm - memory modify (constant address)
736 mw - memory write (fill)
739 base - print or set address offset
740 loop - initialize loop on address range
742 config CMD_MEM_SEARCH
743 bool "ms - Memory search"
745 Memory-search command
747 This allows searching through a region of memory looking for hex
748 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
749 support it). It is also possible to search for a string. The
750 command accepts a memory range and a list of values to search for.
751 The values need to appear in memory in the same order they are given
752 in the command. At most 10 matches can be returned at a time, but
753 pressing return will show the next 10 matches. Environment variables
754 are set for use with scripting (memmatches, memaddr, mempos).
757 bool "Enable cyclic md/mw commands"
758 depends on CMD_MEMORY
760 Add the "mdc" and "mwc" memory commands. These are cyclic
765 This command will print 4 bytes (10,11,12,13) each 500 ms.
767 => mwc.l 100 12345678 10
768 This command will write 12345678 to address 100 all 10 ms.
773 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
775 random - fill memory with random data
780 Simple RAM read/write test.
784 config SYS_ALT_MEMTEST
785 bool "Alternative test"
787 Use a more complete alternative memory test.
791 config SYS_ALT_MEMTEST_BITFLIP
795 The alternative memory test includes bitflip test since 2020.07.
796 The bitflip test significantly increases the overall test time.
797 Bitflip test can optionally be disabled here.
801 config SYS_MEMTEST_START
802 hex "default start address for mtest"
805 This is the default start address for mtest for simple read/write
806 test. If no arguments are given to mtest, default address is used
809 config SYS_MEMTEST_END
810 hex "default end address for mtest"
813 This is the default end address for mtest for simple read/write
814 test. If no arguments are given to mtest, default address is used
823 Compute SHA1 checksum.
825 config SHA1SUM_VERIFY
827 depends on CMD_SHA1SUM
829 Add -v option to verify data against a SHA1 checksum.
832 bool "strings - display strings in memory"
834 This works similarly to the Unix 'strings' command except that it
835 works with a memory range. String of printable characters found
836 within the range are displayed. The minimum number of characters
837 for a sequence to be considered a string can be provided.
841 menu "Compression commands"
845 default y if CMD_BOOTI
848 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
853 default y if CMD_BOOTI
856 Support decompressing an LZ4 image from memory region.
860 default y if CMD_BOOTI
863 Uncompress a zip-compressed memory region.
867 select GZIP_COMPRESSED
869 Compress a memory region with zlib deflate method.
873 menu "Device access commands"
876 #depends on FLASH_CFI_DRIVER
879 ARM Ltd reference designs flash partition access
882 bool "adc - Access Analog to Digital Converters info and data"
884 depends on DM_REGULATOR
886 Shows ADC device info and permit printing one-shot analog converted
887 data from a named Analog to Digital Converter.
892 depends on PARTITIONS
894 Read/modify/write the fields of Bootloader Control Block, usually
895 stored on the flash "misc" partition with its structure defined in:
896 https://android.googlesource.com/platform/bootable/recovery/+/master/
897 bootloader_message/include/bootloader_message/bootloader_message.h
899 Some real-life use-cases include (but are not limited to):
900 - Determine the "boot reason" (and act accordingly):
901 https://source.android.com/devices/bootloader/boot-reason
902 - Get/pass a list of commands from/to recovery:
903 https://android.googlesource.com/platform/bootable/recovery
904 - Inspect/dump the contents of the BCB fields
907 bool "bind/unbind - Bind or unbind a device to/from a driver"
910 Bind or unbind a device to/from a driver from the command line.
911 This is useful in situations where a device may be handled by several
912 drivers. For example, this can be used to bind a UDC to the usb ether
913 gadget driver from the command line.
916 bool "clk - Show clock frequencies"
919 Shows clock frequences by calling a sock_clk_dump() hook function.
920 This is depreated in favour of using the CLK uclass and accessing
921 clock values from associated drivers. However currently no command
925 bool "demo - Demonstration commands for driver model"
928 Provides a 'demo' command which can be used to play around with
929 driver model. To use this properly you will need to enable one or
930 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
931 Otherwise you will always get an empty list of devices. The demo
932 devices are defined in the sandbox device tree, so the easiest
933 option is to use sandbox and pass the -d point to sandbox's
940 Enables the command "dfu" which is used to have U-Boot create a DFU
941 class device via USB. This command requires that the "dfu_alt_info"
942 environment variable be set and define the alt settings to expose to
946 bool "dm - Access to driver model information"
949 Provides access to driver model data structures and information,
950 such as a list of devices, list of uclasses and the state of each
951 device (e.g. activated). This is not required for operation, but
952 can be useful to see the state of driver model for debugging or
956 bool "fastboot - Android fastboot support"
959 This enables the command "fastboot" which enables the Android
960 fastboot mode for the platform. Fastboot is a protocol for
961 downloading images, flashing and device control used on
962 Android devices. Fastboot requires either the network stack
963 enabled or support for acting as a USB device.
965 See doc/android/fastboot.rst for more information.
968 bool "flinfo, erase, protect"
970 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
973 flinfo - print FLASH memory information
975 protect - enable or disable FLASH write protection
984 config CMD_FPGA_LOADBP
985 bool "fpga loadbp - load partial bitstream (Xilinx only)"
988 Supports loading an FPGA device from a bitstream buffer containing
991 config CMD_FPGA_LOADFS
992 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
995 Supports loading an FPGA device from a FAT filesystem.
997 config CMD_FPGA_LOADMK
998 bool "fpga loadmk - load bitstream from image"
1001 Supports loading an FPGA device from a image generated by mkimage.
1003 config CMD_FPGA_LOADP
1004 bool "fpga loadp - load partial bitstream"
1007 Supports loading an FPGA device from a bitstream buffer containing
1008 a partial bitstream.
1010 config CMD_FPGA_LOAD_SECURE
1011 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1014 Enables the fpga loads command which is used to load secure
1015 (authenticated or encrypted or both) bitstreams on to FPGA.
1018 bool "fpgad - dump FPGA registers"
1020 (legacy, needs conversion to driver model)
1021 Provides a way to dump FPGA registers by calling the board-specific
1022 fpga_get_reg() function. This functions similarly to the 'md'
1026 bool "fuse - support for the fuse subssystem"
1028 (deprecated - needs conversion to driver model)
1029 This allows reading, sensing, programming or overriding fuses
1030 which control the behaviour of the device. The command uses the
1039 bool "GPT (GUID Partition Table) command"
1040 select EFI_PARTITION
1041 select HAVE_BLOCK_DEVICE
1042 select PARTITION_UUIDS
1045 Enable the 'gpt' command to ready and write GPT style partition
1049 bool "GPT Random UUID generation"
1052 Enable the generation of partitions with random UUIDs if none
1055 config CMD_GPT_RENAME
1056 bool "GPT partition renaming commands"
1059 Enables the 'gpt' command to interchange names on two GPT
1060 partitions via the 'gpt swap' command or to rename single
1061 partitions via the 'rename' command.
1064 bool "ide - Support for IDE drivers"
1067 Provides an 'ide' command which allows accessing the IDE drive,
1068 reseting the IDE interface, printing the partition table and
1069 geting device info. It also enables the 'diskboot' command which
1070 permits booting from an IDE drive.
1073 bool "io - Support for performing I/O accesses"
1075 Provides an 'iod' command to display I/O space and an 'iow' command
1076 to write values to the I/O space. This can be useful for manually
1077 checking the state of devices during boot when debugging device
1081 bool "iotrace - Support for tracing I/O activity"
1083 Provides an 'iotrace' command which supports recording I/O reads and
1084 writes in a trace buffer in memory . It also maintains a checksum
1085 of the trace records (even if space is exhausted) so that the
1086 sequence of I/O accesses can be verified.
1088 When debugging drivers it is useful to see what I/O accesses were
1089 done and in what order.
1091 Even if the individual accesses are of little interest it can be
1092 useful to verify that the access pattern is consistent each time
1093 an operation is performed. In this case a checksum can be used to
1094 characterise the operation of a driver. The checksum can be compared
1095 across different runs of the operation to verify that the driver is
1098 In particular, when performing major refactoring of the driver, where
1099 the access pattern should not change, the checksum provides assurance
1100 that the refactoring work has not broken the driver.
1102 This works by sneaking into the io.h heder for an architecture and
1103 redirecting I/O accesses through iotrace's tracing mechanism.
1105 For now no commands are provided to examine the trace buffer. The
1106 format is fairly simple, so 'md' is a reasonable substitute.
1108 Note: The checksum feature is only useful for I/O regions where the
1109 contents do not change outside of software control. Where this is not
1110 suitable you can fall back to manually comparing the addresses. It
1111 might be useful to enhance tracing to only checksum the accesses and
1112 not the data read/written.
1122 bool "w1 - Support for Dallas 1-Wire protocol"
1124 Dallas 1-wire protocol support
1130 Load a binary file over serial line.
1136 Load an S-Record file over serial line
1140 bool "lsblk - list block drivers and devices"
1142 Print list of available block device drivers, and for each, the list
1143 of known block devices.
1148 MMC memory mapped support.
1152 config CMD_BKOPS_ENABLE
1153 bool "mmc bkops enable"
1157 Enable command for setting manual background operations handshake
1158 on a eMMC device. The feature is optionally available on eMMC devices
1159 conforming to standard >= 4.41.
1162 bool "Enable support for RPMB in the mmc command"
1163 depends on SUPPORT_EMMC_RPMB
1165 Enable the commands for reading, writing and programming the
1166 key for the Replay Protection Memory Block partition in eMMC.
1168 config CMD_MMC_SWRITE
1170 depends on MMC_WRITE
1173 Enable support for the "mmc swrite" command to write Android sparse
1182 Enable storage cloning over block devices, useful for
1183 initial flashing by external block device without network
1189 select MTD_PARTITIONS
1191 MTD commands support.
1195 default y if NAND_SUNXI
1196 depends on MTD_RAW_NAND
1201 config CMD_NAND_TRIMFFS
1202 bool "nand write.trimffs"
1203 default y if ARCH_SUNXI
1205 Allows one to skip empty pages when flashing something on a NAND.
1207 config CMD_NAND_LOCK_UNLOCK
1208 bool "nand lock/unlock"
1210 NAND locking support.
1212 config CMD_NAND_TORTURE
1215 NAND torture support.
1224 NVM Express device support
1227 bool "onenand - access to onenand device"
1230 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1231 various useful features. This command allows reading, writing,
1232 and erasing blocks. It allso provides a way to show and change
1233 bad blocks, and test the device.
1238 Enable the 'osd' command which allows to query information from and
1239 write text data to a on-screen display (OSD) device; a virtual device
1240 associated with a display capable of displaying a text overlay on the
1241 display it's associated with..
1245 select HAVE_BLOCK_DEVICE
1246 select PARTITION_UUIDS
1248 Read and display information about the partition table on
1252 bool "pci - Access PCI devices"
1254 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1255 used on some devices to allow the CPU to communicate with its
1256 peripherals. Sub-commands allow bus enumeration, displaying and
1257 changing configuration space and a few other features.
1260 bool "pinmux - show pins muxing"
1261 default y if PINCTRL
1263 Parse all available pin-controllers and show pins muxing. This
1264 is useful for debug purpoer to check the pin muxing and to know if
1265 a pin is configured as a GPIO or as an alternate function.
1270 Poweroff/Shutdown the system
1273 bool "read - Read binary data from a partition"
1275 Provides low-level access to the data in a partition.
1277 config CMD_REMOTEPROC
1279 depends on REMOTEPROC
1281 Support for Remote Processor control
1284 bool "sata - Access SATA subsystem"
1287 SATA (Serial Advanced Technology Attachment) is a serial bus
1288 standard for connecting to hard drives and other storage devices.
1289 This command provides information about attached devices and allows
1290 reading, writing and other operations.
1292 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1293 Attachment, where AT refers to an IBM AT (Advanced Technology)
1294 computer released in 1984.
1297 bool "saves - Save a file over serial in S-Record format"
1299 Provides a way to save a binary file using the Motorola S-Record
1300 format over the serial line.
1303 bool "scsi - Access to SCSI devices"
1306 This provides a 'scsi' command which provides access to SCSI (Small
1307 Computer System Interface) devices. The command provides a way to
1308 scan the bus, reset the bus, read and write data and get information
1312 bool "sdram - Print SDRAM configuration information"
1314 Provides information about attached SDRAM. This assumed that the
1315 SDRAM has an EEPROM with information that can be read using the
1316 I2C bus. This is only available on some boards.
1320 depends on DM_SPI_FLASH || SPI_FLASH
1321 default y if DM_SPI_FLASH
1326 bool "sf test - Allow testing of SPI flash"
1329 Provides a way to test that SPI flash is working correctly. The
1330 test is destructive, in that an area of SPI flash must be provided
1331 for the test to use. Performance information is also provided,
1332 measuring the performance of reading, writing and erasing in
1333 Mbps (Million Bits Per Second). This value should approximately
1334 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1335 everything is working properly.
1338 bool "sspi - Command to access spi device"
1341 SPI utility command.
1343 config DEFAULT_SPI_BUS
1344 int "default spi bus used by sspi command"
1348 config DEFAULT_SPI_MODE
1349 hex "default spi mode used by sspi command (see include/spi.h)"
1354 bool "tsi148 - Command to access tsi148 device"
1356 This provides various sub-commands to initialise and configure the
1357 Turndra tsi148 device. See the command help for full details.
1360 bool "Enable UFS - Universal Flash Subsystem commands"
1363 "This provides commands to initialise and configure universal flash
1367 bool "universe - Command to set up the Turndra Universe controller"
1369 This allows setting up the VMEbus provided by this controller.
1370 See the command help for full details.
1374 select HAVE_BLOCK_DEVICE
1380 select USB_FUNCTION_SDP
1382 Enables the command "sdp" which is used to have U-Boot emulating the
1383 Serial Download Protocol (SDP) via USB.
1387 depends on USB_FUNCTION_ROCKUSB
1389 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1390 read/write info, image to/from devices. This enable rockusb command
1391 support to communication with rockusb device. for more detail about
1392 this command, please read doc/README.rockusb.
1394 config CMD_USB_MASS_STORAGE
1395 bool "UMS usb mass storage"
1396 select USB_FUNCTION_MASS_STORAGE
1398 USB mass storage support
1401 bool "Xen para-virtualized block device"
1405 Xen para-virtualized block device support
1412 VirtIO block device support
1418 This provides commands to control the watchdog timer devices.
1424 Enable the command "axi" for accessing AXI (Advanced eXtensible
1425 Interface) busses, a on-chip interconnect specification for managing
1426 functional blocks in SoC designs, which is also often used in designs
1427 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1431 menu "Shell scripting commands"
1437 Echo args to console
1443 Return true/false on integer compare.
1449 Run script from memory
1455 Evaluate boolean and math expressions and store the result in an env
1457 Also supports loading the value at a memory location into a variable.
1458 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1462 menu "Android support commands"
1464 config CMD_AB_SELECT
1467 depends on ANDROID_AB
1469 On Android devices with more than one boot slot (multiple copies of
1470 the kernel and system images) this provides a command to select which
1471 slot should be used to boot from and register the boot attempt. This
1472 is used by the new A/B update model where one slot is updated in the
1473 background while running from the other slot.
1480 bool "Network commands"
1490 bootp - boot image via network using BOOTP/TFTP protocol
1494 depends on CMD_BOOTP
1496 Boot image via network using DHCP/TFTP protocol
1498 config BOOTP_BOOTPATH
1499 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1501 depends on CMD_BOOTP
1503 Even though the config is called BOOTP_BOOTPATH, it stores the
1504 path in the variable 'rootpath'.
1507 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1509 depends on CMD_BOOTP
1511 The primary DNS server is stored as 'dnsip'. If two servers are
1512 returned, you must set BOOTP_DNS2 to store that second server IP
1516 bool "Store 'dnsip2' from BOOTP/DHCP server"
1517 depends on BOOTP_DNS
1519 If a DHCP client requests the DNS server IP from a DHCP server,
1520 it is possible that more than one DNS serverip is offered to the
1521 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1522 server IP will be stored in the additional environment
1523 variable "dnsip2". The first DNS serverip is always
1524 stored in the variable "dnsip", when BOOTP_DNS is defined.
1526 config BOOTP_GATEWAY
1527 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1529 depends on CMD_BOOTP
1531 config BOOTP_HOSTNAME
1532 bool "Request & store 'hostname' from BOOTP/DHCP server"
1534 depends on CMD_BOOTP
1536 The name may or may not be qualified with the local domain name.
1538 config BOOTP_PREFER_SERVERIP
1539 bool "serverip variable takes precedent over DHCP server IP."
1540 depends on CMD_BOOTP
1542 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1544 With this option enabled, the 'serverip' variable in the environment
1545 takes precedence over DHCP server IP and will only be set by the DHCP
1546 server if not already set in the environment.
1548 config BOOTP_SUBNETMASK
1549 bool "Request & store 'netmask' from BOOTP/DHCP server"
1551 depends on CMD_BOOTP
1553 config BOOTP_NTPSERVER
1554 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1555 depends on CMD_BOOTP
1560 Selecting this will allow capturing all Ethernet packets and store
1561 them in physical memory in a PCAP formated file,
1562 later to be analyzed by PCAP reader application (IE. WireShark).
1565 bool "Send PXE client arch to BOOTP/DHCP server"
1567 depends on CMD_BOOTP && CMD_PXE
1569 Supported for ARM, ARM64, and x86 for now.
1571 config BOOTP_PXE_CLIENTARCH
1573 depends on BOOTP_PXE
1574 default 0x16 if ARM64
1578 config BOOTP_VCI_STRING
1580 depends on CMD_BOOTP
1581 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1582 default "U-Boot.armv8" if ARM64
1583 default "U-Boot.arm" if ARM
1590 tftpboot - boot image via network using TFTP protocol
1594 depends on CMD_TFTPBOOT
1596 TFTP put command, for uploading files to a server
1600 depends on CMD_TFTPBOOT
1602 Act as a TFTP server and boot the first received file
1604 config NET_TFTP_VARS
1605 bool "Control TFTP timeout and count through environment"
1606 depends on CMD_TFTPBOOT
1609 If set, allows controlling the TFTP timeout through the
1610 environment variable tftptimeout, and the TFTP maximum
1611 timeout count through the variable tftptimeoutcountmax.
1612 If unset, timeout and maximum are hard-defined as 1 second
1613 and 10 timouts per TFTP transfer.
1618 Boot image via network using RARP/TFTP protocol
1624 Boot image via network using NFS protocol.
1630 If set, allows 802.3(clause 22) MII Management functions interface access
1631 The management interface specified in Clause 22 provides
1632 a simple, two signal, serial interface to connect a
1633 Station Management entity and a managed PHY for providing access
1634 to management parameters and services.
1635 The interface is referred to as the MII management interface.
1641 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1642 The MDIO interface is orthogonal to the MII interface and extends
1643 it by adding access to more registers through indirect addressing.
1648 Send ICMP ECHO_REQUEST to network host
1653 Perform CDP network configuration
1659 Synchronize RTC via network
1664 Lookup the IP of a hostname
1666 config CMD_LINK_LOCAL
1670 Acquire a network IP address using the link-local protocol
1677 Allow control of L2 Ethernet switch commands. These are supported
1678 by the vsc9953 Ethernet driver at present. Sub-commands allow
1679 operations such as enabling / disabling a port and
1680 viewing/maintaining the filtering database (FDB)
1686 Boot image via network using PXE protocol
1691 Wait for wake-on-lan Magic Packet
1695 menu "Misc commands"
1698 bool "Enable 'bmp' command"
1699 depends on LCD || DM_VIDEO || VIDEO
1701 This provides a way to obtain information about a BMP-format image
1702 and to display it. BMP (which presumably stands for BitMaP) is a
1703 file format defined by Microsoft which supports images of various
1704 depths, formats and compression methods. Headers on the file
1705 determine the formats used. This command can be used by first loading
1706 the image into RAM, then using this command to look at it or display
1709 config CMD_BOOTCOUNT
1711 depends on BOOTCOUNT_LIMIT
1713 Enable the bootcount command, which allows interrogation and
1714 reset of the bootcounter.
1717 bool "Enable board-specific commands"
1719 (deprecated: instead, please define a Kconfig option for each command)
1721 Some boards have board-specific commands which are only enabled
1722 during developemnt and need to be turned off for production. This
1723 option provides a way to control this. The commands that are enabled
1724 vary depending on the board.
1726 config CMD_BLOCK_CACHE
1727 bool "blkcache - control and stats for block cache"
1728 depends on BLOCK_CACHE
1729 default y if BLOCK_CACHE
1731 Enable the blkcache command, which can be used to control the
1732 operation of the cache functions.
1733 This is most useful when fine-tuning the operation of the cache
1734 during development, but also allows the cache to be disabled when
1735 it might hurt performance (e.g. when using the ums command).
1742 Enable the 'button' command which allows to get the status of
1743 buttons supported by the board. The buttonss can be listed with
1744 'button list' and state can be known with 'button <label>'.
1745 Any button drivers can be controlled with this command, e.g.
1749 bool "icache or dcache"
1751 Enable the "icache" and "dcache" commands
1753 config CMD_CONITRACE
1754 bool "conitrace - trace console input codes"
1756 Enable the 'conitrace' command which displays the codes received
1757 from the console input as hexadecimal numbers.
1760 bool "Enable clear screen command 'cls'"
1761 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1764 Enable the 'cls' command which clears the screen contents
1765 on video frame buffer.
1768 bool "efidebug - display/configure UEFI environment"
1769 depends on EFI_LOADER
1770 select EFI_DEVICE_PATH_TO_TEXT
1773 Enable the 'efidebug' command which provides a subset of UEFI
1774 shell utility with simplified functionality. It will be useful
1775 particularly for managing boot parameters as well as examining
1776 various EFI status for debugging.
1778 config CMD_EXCEPTION
1779 bool "exception - raise exception"
1780 depends on ARM || RISCV || X86
1782 Enable the 'exception' command which allows to raise an exception.
1789 Enable the 'led' command which allows for control of LEDs supported
1790 by the board. The LEDs can be listed with 'led list' and controlled
1791 with led on/off/togle/blink. Any LED drivers can be controlled with
1792 this command, e.g. led_gpio.
1799 Enable the 'date' command for getting/setting the time/date in RTC
1806 Enable the 'rtc' command for low-level access to RTC devices.
1811 Run commands and summarize execution time.
1814 bool "gettime - read elapsed time"
1816 Enable the 'gettime' command which reads the elapsed time since
1817 U-Boot started running. This shows the time in seconds and
1818 milliseconds. See also the 'bootstage' command which provides more
1819 flexibility for boot timing.
1826 Print bytes from the hardware random number generator.
1828 # TODO: rename to CMD_SLEEP
1833 Delay execution for some time
1836 bool "support for multiprocessor"
1838 This provides an option to brinup
1839 different processors in multiprocessor
1845 Access the system timer.
1851 This provides basic access to the U-Boot's sound support. The main
1852 feature is to play a beep.
1854 sound init - set up sound system
1855 sound play - play a sound
1861 Boot image via local extlinux.conf file
1867 This provides access to the QEMU firmware interface. The main
1868 feature is to allow easy loading of files passed to qemu-system
1869 via -kernel / -initrd
1871 source "cmd/mvebu/Kconfig"
1874 bool "terminal - provides a way to attach a serial terminal"
1876 Provides a 'cu'-like serial terminal command. This can be used to
1877 access other serial ports from the system console. The terminal
1878 is very simple with no special processing of characters. As with
1879 cu, you can press ~. (tilde followed by period) to exit.
1882 bool "uuid, guid - generation of unique IDs"
1885 This enables two commands:
1887 uuid - generate random Universally Unique Identifier
1888 guid - generate Globally Unique Identifier based on random UUID
1890 The two commands are very similar except for the endianness of the
1895 source "cmd/ti/Kconfig"
1897 config CMD_BOOTSTAGE
1898 bool "Enable the 'bootstage' command"
1899 depends on BOOTSTAGE
1901 Add a 'bootstage' command which supports printing a report
1902 and un/stashing of bootstage data.
1904 menu "Power commands"
1906 bool "Enable Driver Model PMIC command"
1909 This is the pmic command, based on a driver model pmic's API.
1910 Command features are unchanged:
1911 - list - list pmic devices
1912 - pmic dev <id> - show or [set] operating pmic device (NEW)
1913 - pmic dump - dump registers
1914 - pmic read address - read byte of register at address
1915 - pmic write address - write byte to register at address
1916 The only one change for this command is 'dev' subcommand.
1918 config CMD_REGULATOR
1919 bool "Enable Driver Model REGULATOR command"
1920 depends on DM_REGULATOR
1922 This command is based on driver model regulator's API.
1923 User interface features:
1924 - list - list regulator devices
1925 - regulator dev <id> - show or [set] operating regulator device
1926 - regulator info - print constraints info
1927 - regulator status - print operating status
1928 - regulator value <val] <-f> - print/[set] voltage value [uV]
1929 - regulator current <val> - print/[set] current value [uA]
1930 - regulator mode <id> - print/[set] operating mode id
1931 - regulator enable - enable the regulator output
1932 - regulator disable - disable the regulator output
1934 The '-f' (force) option can be used for set the value which exceeds
1935 the limits, which are found in device-tree and are kept in regulator's
1936 uclass platdata structure.
1940 menu "Security commands"
1942 bool "Enable the 'aes' command"
1945 This provides a means to encrypt and decrypt data using the AES
1946 (Advanced Encryption Standard). This algorithm uses a symetric key
1947 and is widely used as a streaming cipher. Different key lengths are
1948 supported by the algorithm but this command only supports 128 bits
1952 bool "Enable the 'blob' command"
1954 This is used with the Freescale secure boot mechanism.
1956 Freescale's SEC block has built-in Blob Protocol which provides
1957 a method for protecting user-defined data across system power
1958 cycles. SEC block protects data in a data structure called a Blob,
1959 which provides both confidentiality and integrity protection.
1961 Encapsulating data as a blob
1962 Each time that the Blob Protocol is used to protect data, a
1963 different randomly generated key is used to encrypt the data.
1964 This random key is itself encrypted using a key which is derived
1965 from SoC's non-volatile secret key and a 16 bit Key identifier.
1966 The resulting encrypted key along with encrypted data is called a
1967 blob. The non-volatile secure key is available for use only during
1970 During decapsulation, the reverse process is performed to get back
1974 blob enc - encapsulating data as a cryptgraphic blob
1975 blob dec - decapsulating cryptgraphic blob to get the data
1979 blob enc src dst len km
1981 Encapsulate and create blob of data $len bytes long
1982 at address $src and store the result at address $dst.
1983 $km is the 16 byte key modifier is also required for
1984 generation/use as key for cryptographic operation. Key
1985 modifier should be 16 byte long.
1987 blob dec src dst len km
1989 Decapsulate the blob of data at address $src and
1990 store result of $len byte at addr $dst.
1991 $km is the 16 byte key modifier is also required for
1992 generation/use as key for cryptographic operation. Key
1993 modifier should be 16 byte long.
1996 bool "Support 'hash' command"
1999 This provides a way to hash data in memory using various supported
2000 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2001 saved to memory or to an environment variable. It is also possible
2002 to verify a hash against data in memory.
2005 bool "Support the 'hvc' command"
2006 depends on ARM_SMCCC
2008 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2009 development and testing.
2012 bool "Support the 'smc' command"
2013 depends on ARM_SMCCC
2015 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2016 development and testing.
2022 Add -v option to verify data against a hash.
2032 bool "Enable the 'tpm' command"
2033 depends on TPM_V1 || TPM_V2
2034 select CMD_TPM_V1 if TPM_V1
2035 select CMD_TPM_V2 if TPM_V2
2037 This provides a means to talk to a TPM from the command line. A wide
2038 range of commands if provided - see 'tpm help' for details. The
2039 command requires a suitable TPM on your board and the correct driver
2045 bool "Enable the 'tpm test' command"
2048 This provides a a series of tests to confirm that the TPMv1.x is
2049 working correctly. The tests cover initialisation, non-volatile RAM,
2050 extend, global lock and checking that timing is within expectations.
2051 The tests pass correctly on Infineon TPMs but may need to be adjusted
2058 menu "Firmware commands"
2060 bool "Enable crosec command"
2064 Enable command-line access to the Chrome OS EC (Embedded
2065 Controller). This provides the 'crosec' command which has
2066 a number of sub-commands for performing EC tasks such as
2067 updating its flash, accessing a small saved context area
2068 and talking to the I2C bus behind the EC (if there is one).
2071 menu "Filesystem commands"
2073 bool "Enable the 'btrsubvol' command"
2076 This enables the 'btrsubvol' command to list subvolumes
2077 of a BTRFS filesystem. There are no special commands for
2078 listing BTRFS directories or loading BTRFS files - this
2079 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2080 when BTRFS is enabled (see FS_BTRFS).
2083 bool "Enable the 'cbfs' command"
2086 Define this to enable support for reading from a Coreboot
2087 filesystem. This is a ROM-based filesystem used for accessing files
2088 on systems that use coreboot as the first boot-loader and then load
2089 U-Boot to actually boot the Operating System. Available commands are
2090 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2093 bool "Enable the 'cramfs' command"
2094 depends on FS_CRAMFS
2096 This provides commands for dealing with CRAMFS (Compressed ROM
2097 filesystem). CRAMFS is useful when space is tight since files are
2098 compressed. Two commands are provided:
2100 cramfsls - lists files in a cramfs image
2101 cramfsload - loads a file from a cramfs image
2104 bool "ext2 command support"
2107 Enables EXT2 FS command
2110 bool "ext4 command support"
2113 Enables EXT4 FS command
2115 config CMD_EXT4_WRITE
2117 bool "ext4 write command support"
2120 Enables EXT4 FS write command
2123 bool "FAT command support"
2126 Support for the FAT fs
2129 bool "SquashFS command support"
2132 Enables SquashFS filesystem commands (e.g. load, ls).
2134 config CMD_FS_GENERIC
2135 bool "filesystem commands"
2137 Enables filesystem commands (e.g. load, ls) that work for multiple
2141 bool "fsuuid command"
2143 Enables fsuuid command for filesystem UUID.
2146 bool "jffs2 command"
2149 Enables commands to support the JFFS2 (Journalling Flash File System
2150 version 2) filesystem. This enables fsload, ls and fsinfo which
2151 provide the ability to load files, list directories and obtain
2152 filesystem information.
2155 bool "MTD partition support"
2158 MTD partitioning tool support.
2159 It is strongly encouraged to avoid using this command
2160 anymore along with 'sf', 'nand', 'onenand'. One can still
2161 declare the partitions in the mtdparts environment variable
2162 but better use the MTD stack and the 'mtd' command instead.
2164 config CMD_MTDPARTS_SPREAD
2165 bool "Padd partition size to take account of bad blocks"
2166 depends on CMD_MTDPARTS
2168 This enables the 'spread' sub-command of the mtdparts command.
2169 This command will modify the existing mtdparts variable by increasing
2170 the size of the partitions such that 1) each partition's net size is
2171 at least as large as the size specified in the mtdparts variable and
2172 2) each partition starts on a good block.
2174 config CMD_MTDPARTS_SHOW_NET_SIZES
2175 bool "Show net size (w/o bad blocks) of partitions"
2176 depends on CMD_MTDPARTS
2178 Adds two columns to the printed partition table showing the
2179 effective usable size of a partition, if bad blocks are taken
2182 config MTDIDS_DEFAULT
2183 string "Default MTD IDs"
2184 depends on MTD || SPI_FLASH
2186 Defines a default MTD IDs list for use with MTD partitions in the
2187 Linux MTD command line partitions format.
2189 config MTDPARTS_DEFAULT
2190 string "Default MTD partition scheme"
2191 depends on MTD || SPI_FLASH
2193 Defines a default MTD partitioning scheme in the Linux MTD command
2194 line partitions format
2197 bool "reiser - Access to reiserfs filesystems"
2199 This provides two commands which operate on a resierfs filesystem,
2200 commonly used some years ago:
2202 reiserls - list files
2203 reiserload - load a file
2206 bool "yaffs2 - Access of YAFFS2 filesystem"
2210 This provides commands for accessing a YAFFS2 filesystem. Yet
2211 Another Flash Filesystem 2 is a filesystem designed specifically
2212 for NAND flash. It incorporates bad-block management and ensures
2213 that device writes are sequential regardless of filesystem
2217 bool "zfs - Access of ZFS filesystem"
2219 This provides commands to accessing a ZFS filesystem, commonly used
2220 on Solaris systems. Two sub-commands are provided:
2222 zfsls - list files in a directory
2223 zfsload - load a file
2225 See doc/README.zfs for more details.
2229 menu "Debug commands"
2234 The bedbug (emBEDded deBUGger) command provides debugging features
2235 for some PowerPC processors. For details please see the
2236 documentation in doc/README.bedbug.
2239 bool "diag - Board diagnostics"
2241 This command provides access to board diagnostic tests. These are
2242 called Power-on Self Tests (POST). The command allows listing of
2243 available tests and running either all the tests, or specific tests
2247 bool "irq - Show information about interrupts"
2248 depends on !ARM && !MIPS && !RISCV && !SH
2250 This enables two commands:
2252 interrupts - enable or disable interrupts
2253 irqinfo - print device-specific interrupt information
2256 bool "kgdb - Allow debugging of U-Boot with gdb"
2259 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2260 over a serial link for debugging purposes. This allows
2261 single-stepping, inspecting variables, etc. This is supported only
2262 on PowerPC at present.
2265 bool "log - Generation, control and access to logging"
2268 This provides access to logging features. It allows the output of
2269 log data to be controlled to a limited extent (setting up the default
2270 maximum log level for emitting of records). It also provides access
2271 to a command used for testing the log system.
2274 bool "trace - Support tracing of function calls and timing"
2276 Enables a command to control using of function tracing within
2277 U-Boot. This allows recording of call traces including timing
2278 information. The command can write data to memory for exporting
2279 for analysis (e.g. using bootchart). See doc/README.trace for full
2283 bool "avb - Android Verified Boot 2.0 operations"
2284 depends on AVB_VERIFY
2287 Enables a "avb" command to perform verification of partitions using
2288 Android Verified Boot 2.0 functionality. It includes such subcommands:
2289 avb init - initialize avb2 subsystem
2290 avb read_rb - read rollback index
2291 avb write_rb - write rollback index
2292 avb is_unlocked - check device lock state
2293 avb get_uuid - read and print uuid of a partition
2294 avb read_part - read data from partition
2295 avb read_part_hex - read data from partition and output to stdout
2296 avb write_part - write data to partition
2297 avb verify - run full verification chain
2301 tristate "Enable UBI - Unsorted block images commands"
2304 UBI is a software layer above MTD layer which admits use of LVM-like
2305 logical volumes on top of MTD devices, hides some complexities of
2306 flash chips like wear and bad blocks and provides some other useful
2307 capabilities. Please, consult the MTD web site for more details
2308 (www.linux-mtd.infradead.org). Activate this option if you want
2309 to use U-Boot UBI commands.
2310 It is also strongly encouraged to also enable CONFIG_MTD to get full
2313 config CMD_UBI_RENAME
2314 bool "Enable rename"
2318 Enable a "ubi" command to rename ubi volume:
2319 ubi rename <oldname> <newname>
2322 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2324 default y if CMD_UBI
2327 UBIFS is a file system for flash devices which works on top of UBI.