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.
204 Print ".config" contents.
206 If this option is enabled, the ".config" file contents are embedded
207 in the U-Boot image and can be printed on the console by the "config"
208 command. This provides information of which options are enabled on
215 Print console devices and information.
220 Print information about available CPUs. This normally shows the
221 number of CPUs, type (e.g. manufacturer, architecture, product or
222 internal name) and clock frequency. Other information may be
223 available depending on the CPU driver.
229 Print GPL license text
234 Provides access to the Intel Power-Management Controller (PMC) so
235 that its state can be examined. This does not currently support
236 changing the state but it is still useful for debugging and seeing
245 config CMD_TLV_EEPROM
247 depends on I2C_EEPROM
249 Display and program the system EEPROM data block in ONIE Tlvinfo
250 format. TLV stands for Type-Length-Value.
252 config SPL_CMD_TLV_EEPROM
253 bool "tlv_eeprom for SPL"
254 depends on SPL_I2C_EEPROM
255 select SPL_DRIVERS_MISC_SUPPORT
257 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
267 Run the command stored in the environment "bootcmd", i.e.
268 "bootd" does the same thing as "run bootcmd".
274 Boot an application image from the memory.
277 bool "Support booting UEFI FIT images"
278 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
281 Support booting UEFI FIT images via the bootm command.
286 Boot the Linux zImage
290 depends on ARM64 || RISCV
293 Boot an AArch64 Linux Kernel image from memory.
296 bool "Support booting Linux OS images"
297 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
300 Support booting the Linux kernel directly via a command such as bootm
304 bool "Support booting NetBSD (non-EFI) loader images"
308 Support booting NetBSD via the bootm command.
310 config BOOTM_OPENRTOS
311 bool "Support booting OPENRTOS / FreeRTOS images"
314 Support booting OPENRTOS / FreeRTOS via the bootm command.
317 bool "Support booting Enea OSE images"
318 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
321 Support booting Enea OSE images via the bootm command.
324 bool "Support booting Plan9 OS images"
328 Support booting Plan9 images via the bootm command.
331 bool "Support booting RTEMS OS images"
335 Support booting RTEMS images via the bootm command.
338 bool "Support booting VxWorks OS images"
342 Support booting VxWorks images via the bootm command.
346 depends on EFI_LOADER
349 Boot an EFI image from memory.
351 config CMD_BOOTEFI_HELLO_COMPILE
352 bool "Compile a standard EFI hello world binary for testing"
353 depends on CMD_BOOTEFI && !CPU_V7M
356 This compiles a standard EFI hello world application with U-Boot so
357 that it can be used with the test/py testing framework. This is useful
358 for testing that EFI is working at a basic level, and for bringing
359 up EFI support on a new architecture.
361 No additional space will be required in the resulting U-Boot binary
362 when this option is enabled.
364 config CMD_BOOTEFI_HELLO
365 bool "Allow booting a standard EFI hello world for testing"
366 depends on CMD_BOOTEFI_HELLO_COMPILE
368 This adds a standard EFI hello world application to U-Boot so that
369 it can be used with the 'bootefi hello' command. This is useful
370 for testing that EFI is working at a basic level, and for bringing
371 up EFI support on a new architecture.
373 source lib/efi_selftest/Kconfig
379 Add an ANSI terminal boot menu command.
384 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
385 image into RAM, dump image structure information, etc. Those dtb/dtbo
386 files should be merged in one dtb further, which needs to be passed to
387 the kernel, as part of a boot process.
390 bool "bootelf, bootvx"
393 Boot an ELF/vxWorks image from the memory.
396 bool "Flattened Device Tree utility commands"
400 Do FDT related setup before booting into the Operating System.
406 Start an application at a given address.
412 Run the command in the given environment variable.
418 Print header information for application image.
423 List all images found in flash
429 Extract a part of a multi-image.
432 bool "spl export - Export boot information for Falcon boot"
435 Falcon mode allows booting directly from SPL into an Operating
436 System such as Linux, thus skipping U-Boot proper. See
437 doc/README.falcon for full information about how to use this
440 config CMD_SPL_NAND_OFS
441 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
442 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
445 This provides the offset of the command line arguments for Linux
446 when booting from NAND in Falcon mode. See doc/README.falcon
447 for full information about how to use this option (and also see
448 board/gateworks/gw_ventana/README for an example).
450 config CMD_SPL_NOR_OFS
451 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
452 depends on CMD_SPL && SPL_NOR_SUPPORT
455 This provides the offset of the command line arguments or dtb for
456 Linux when booting from NOR in Falcon mode.
458 config CMD_SPL_WRITE_SIZE
459 hex "Size of argument area"
463 This provides the size of the command-line argument area in NAND
464 flash used by Falcon-mode boot. See the documentation until CMD_SPL
468 bool "fitImage update command"
470 Implements the 'fitupd' command, which allows to automatically
471 store software updates present on a TFTP server in NOR Flash
473 config CMD_THOR_DOWNLOAD
474 bool "thor - TIZEN 'thor' download"
477 Implements the 'thor' download protocol. This is a way of
478 downloading a software update over USB from an attached host.
479 There is no documentation about this within the U-Boot source code
480 but you should be able to find something on the interwebs.
483 bool "zboot - x86 boot command"
485 With x86 machines it is common to boot a bzImage file which
486 contains both a kernel and a setup.bin file. The latter includes
487 configuration information from the dark ages which x86 boards still
488 need to pick things out of.
490 Consider using FIT in preference to this since it supports directly
491 booting both 32- and 64-bit kernels, as well as secure boot.
492 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
496 menu "Environment commands"
499 bool "ask for env variable"
501 Ask for environment variable
519 Edit environment variable.
524 Allow for searching environment variables
530 Save all environment variables into the compiled-in persistent
536 depends on CMD_SAVEENV
538 Erase environment variables from the compiled-in persistent
541 config CMD_ENV_EXISTS
545 Check if a variable is defined in the environment for use in
548 config CMD_ENV_CALLBACK
549 bool "env callbacks - print callbacks and their associated variables"
551 Some environment variable have callbacks defined by
552 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
553 For example changing "baudrate" adjust the serial baud rate. This
554 command lists the currently defined callbacks.
557 bool "env flags -print variables that have non-default flags"
559 Some environment variables have special flags that control their
560 behaviour. For example, serial# can only be written once and cannot
561 be deleted. This command shows the variables that have special
564 config CMD_NVEDIT_EFI
565 bool "env [set|print] -e - set/print UEFI variables"
566 depends on EFI_LOADER
569 UEFI variables are encoded as some form of U-Boot variables.
570 If enabled, we are allowed to set/print UEFI variables using
571 "env" command with "-e" option without knowing details.
573 config CMD_NVEDIT_INFO
574 bool "env info - print or evaluate environment information"
576 Print environment information:
577 - env_valid : is environment valid
578 - env_ready : is environment imported into hash table
579 - env_use_default : is default environment used
581 This command can be optionally used for evaluation in scripts:
582 [-d] : evaluate whether default environment is used
583 [-p] : evaluate whether environment can be persisted
584 The result of multiple evaluations will be combined with AND.
588 menu "Memory commands"
593 Compute binary operations (xor, or, and) of byte arrays of arbitrary
594 size from memory and store the result in memory or the environment.
607 Add -v option to verify data against a crc32 checksum.
610 bool "eeprom - EEPROM subsystem"
612 (deprecated, needs conversion to driver model)
613 Provides commands to read and write EEPROM (Electrically Erasable
614 Programmable Read Only Memory) chips that are connected over an
617 config CMD_EEPROM_LAYOUT
618 bool "Enable layout-aware eeprom commands"
619 depends on CMD_EEPROM
621 (deprecated, needs conversion to driver model)
622 When enabled, additional eeprom sub-commands become available.
624 eeprom print - prints the contents of the eeprom in a human-readable
625 way (eeprom layout fields, and data formatted to be fit for human
628 eeprom update - allows user to update eeprom fields by specifying
629 the field name, and providing the new data in a human readable format
630 (same format as displayed by the eeprom print command).
632 Both commands can either auto detect the layout, or be told which
636 __weak int parse_layout_version(char *str)
637 - override to provide your own layout name parsing
638 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
640 - override to setup the layout metadata based on the version
641 __weak int eeprom_layout_detect(unsigned char *data)
642 - override to provide your own algorithm for detecting layout
645 - contains various printing and updating functions for common
646 types of eeprom fields. Can be used for defining
649 config EEPROM_LAYOUT_HELP_STRING
650 string "Tells user what layout names are supported"
651 depends on CMD_EEPROM_LAYOUT
652 default "<not defined>"
654 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
660 Infinite write loop on address range
667 Compute MD5 checksum.
672 depends on CMD_MD5SUM
674 Add -v option to verify data against an MD5 checksum.
679 Display memory information.
682 bool "md, mm, nm, mw, cp, cmp, base, loop"
687 mm - memory modify (auto-incrementing address)
688 nm - memory modify (constant address)
689 mw - memory write (fill)
692 base - print or set address offset
693 loop - initialize loop on address range
696 bool "Enable cyclic md/mw commands"
697 depends on CMD_MEMORY
699 Add the "mdc" and "mwc" memory commands. These are cyclic
704 This command will print 4 bytes (10,11,12,13) each 500 ms.
706 => mwc.l 100 12345678 10
707 This command will write 12345678 to address 100 all 10 ms.
712 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
714 random - fill memory with random data
719 Simple RAM read/write test.
723 config SYS_ALT_MEMTEST
724 bool "Alternative test"
726 Use a more complete alternative memory test.
733 mdc - memory display cyclic
734 mwc - memory write cyclic
740 Compute SHA1 checksum.
742 config SHA1SUM_VERIFY
744 depends on CMD_SHA1SUM
746 Add -v option to verify data against a SHA1 checksum.
749 bool "strings - display strings in memory"
751 This works similarly to the Unix 'strings' command except that it
752 works with a memory range. String of printable characters found
753 within the range are displayed. The minimum number of characters
754 for a sequence to be considered a string can be provided.
758 menu "Compression commands"
762 default y if CMD_BOOTI
765 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
770 default y if CMD_BOOTI
772 Uncompress a zip-compressed memory region.
777 Compress a memory region with zlib deflate method.
781 menu "Device access commands"
784 #depends on FLASH_CFI_DRIVER
787 ARM Ltd reference designs flash partition access
790 bool "adc - Access Analog to Digital Converters info and data"
794 Shows ADC device info and permit printing one-shot analog converted
795 data from a named Analog to Digital Converter.
800 depends on PARTITIONS
802 Read/modify/write the fields of Bootloader Control Block, usually
803 stored on the flash "misc" partition with its structure defined in:
804 https://android.googlesource.com/platform/bootable/recovery/+/master/
805 bootloader_message/include/bootloader_message/bootloader_message.h
807 Some real-life use-cases include (but are not limited to):
808 - Determine the "boot reason" (and act accordingly):
809 https://source.android.com/devices/bootloader/boot-reason
810 - Get/pass a list of commands from/to recovery:
811 https://android.googlesource.com/platform/bootable/recovery
812 - Inspect/dump the contents of the BCB fields
815 bool "bind/unbind - Bind or unbind a device to/from a driver"
818 Bind or unbind a device to/from a driver from the command line.
819 This is useful in situations where a device may be handled by several
820 drivers. For example, this can be used to bind a UDC to the usb ether
821 gadget driver from the command line.
824 bool "clk - Show clock frequencies"
827 Shows clock frequences by calling a sock_clk_dump() hook function.
828 This is depreated in favour of using the CLK uclass and accessing
829 clock values from associated drivers. However currently no command
833 bool "demo - Demonstration commands for driver model"
836 Provides a 'demo' command which can be used to play around with
837 driver model. To use this properly you will need to enable one or
838 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
839 Otherwise you will always get an empty list of devices. The demo
840 devices are defined in the sandbox device tree, so the easiest
841 option is to use sandbox and pass the -d point to sandbox's
848 Enables the command "dfu" which is used to have U-Boot create a DFU
849 class device via USB. This command requires that the "dfu_alt_info"
850 environment variable be set and define the alt settings to expose to
854 bool "dm - Access to driver model information"
857 Provides access to driver model data structures and information,
858 such as a list of devices, list of uclasses and the state of each
859 device (e.g. activated). This is not required for operation, but
860 can be useful to see the state of driver model for debugging or
864 bool "fastboot - Android fastboot support"
867 This enables the command "fastboot" which enables the Android
868 fastboot mode for the platform. Fastboot is a protocol for
869 downloading images, flashing and device control used on
870 Android devices. Fastboot requires either the network stack
871 enabled or support for acting as a USB device.
873 See doc/android/fastboot.txt for more information.
876 bool "flinfo, erase, protect"
878 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
881 flinfo - print FLASH memory information
883 protect - enable or disable FLASH write protection
892 config CMD_FPGA_LOADBP
893 bool "fpga loadbp - load partial bitstream (Xilinx only)"
896 Supports loading an FPGA device from a bitstream buffer containing
899 config CMD_FPGA_LOADFS
900 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
903 Supports loading an FPGA device from a FAT filesystem.
905 config CMD_FPGA_LOADMK
906 bool "fpga loadmk - load bitstream from image"
909 Supports loading an FPGA device from a image generated by mkimage.
911 config CMD_FPGA_LOADP
912 bool "fpga loadp - load partial bitstream"
915 Supports loading an FPGA device from a bitstream buffer containing
918 config CMD_FPGA_LOAD_SECURE
919 bool "fpga loads - loads secure bitstreams (Xilinx only)"
922 Enables the fpga loads command which is used to load secure
923 (authenticated or encrypted or both) bitstreams on to FPGA.
926 bool "fpgad - dump FPGA registers"
928 (legacy, needs conversion to driver model)
929 Provides a way to dump FPGA registers by calling the board-specific
930 fpga_get_reg() function. This functions similarly to the 'md'
934 bool "fuse - support for the fuse subssystem"
936 (deprecated - needs conversion to driver model)
937 This allows reading, sensing, programming or overriding fuses
938 which control the behaviour of the device. The command uses the
947 bool "GPT (GUID Partition Table) command"
949 select HAVE_BLOCK_DEVICE
950 select PARTITION_UUIDS
953 Enable the 'gpt' command to ready and write GPT style partition
957 bool "GPT Random UUID generation"
960 Enable the generation of partitions with random UUIDs if none
963 config CMD_GPT_RENAME
964 bool "GPT partition renaming commands"
967 Enables the 'gpt' command to interchange names on two GPT
968 partitions via the 'gpt swap' command or to rename single
969 partitions via the 'rename' command.
972 bool "ide - Support for IDE drivers"
975 Provides an 'ide' command which allows accessing the IDE drive,
976 reseting the IDE interface, printing the partition table and
977 geting device info. It also enables the 'diskboot' command which
978 permits booting from an IDE drive.
981 bool "io - Support for performing I/O accesses"
983 Provides an 'iod' command to display I/O space and an 'iow' command
984 to write values to the I/O space. This can be useful for manually
985 checking the state of devices during boot when debugging device
989 bool "iotrace - Support for tracing I/O activity"
991 Provides an 'iotrace' command which supports recording I/O reads and
992 writes in a trace buffer in memory . It also maintains a checksum
993 of the trace records (even if space is exhausted) so that the
994 sequence of I/O accesses can be verified.
996 When debugging drivers it is useful to see what I/O accesses were
997 done and in what order.
999 Even if the individual accesses are of little interest it can be
1000 useful to verify that the access pattern is consistent each time
1001 an operation is performed. In this case a checksum can be used to
1002 characterise the operation of a driver. The checksum can be compared
1003 across different runs of the operation to verify that the driver is
1006 In particular, when performing major refactoring of the driver, where
1007 the access pattern should not change, the checksum provides assurance
1008 that the refactoring work has not broken the driver.
1010 This works by sneaking into the io.h heder for an architecture and
1011 redirecting I/O accesses through iotrace's tracing mechanism.
1013 For now no commands are provided to examine the trace buffer. The
1014 format is fairly simple, so 'md' is a reasonable substitute.
1016 Note: The checksum feature is only useful for I/O regions where the
1017 contents do not change outside of software control. Where this is not
1018 suitable you can fall back to manually comparing the addresses. It
1019 might be useful to enhance tracing to only checksum the accesses and
1020 not the data read/written.
1030 bool "w1 - Support for Dallas 1-Wire protocol"
1032 Dallas 1-wire protocol support
1038 Load a binary file over serial line.
1044 Load an S-Record file over serial line
1049 MMC memory mapped support.
1052 bool "Enable support for RPMB in the mmc command"
1055 Enable the commands for reading, writing and programming the
1056 key for the Replay Protection Memory Block partition in eMMC.
1058 config CMD_MMC_SWRITE
1060 depends on CMD_MMC && MMC_WRITE
1063 Enable support for the "mmc swrite" command to write Android sparse
1069 select MTD_PARTITIONS
1071 MTD commands support.
1075 default y if NAND_SUNXI
1076 depends on MTD_RAW_NAND
1081 config CMD_NAND_TRIMFFS
1082 bool "nand write.trimffs"
1083 default y if ARCH_SUNXI
1085 Allows one to skip empty pages when flashing something on a NAND.
1087 config CMD_NAND_LOCK_UNLOCK
1088 bool "nand lock/unlock"
1090 NAND locking support.
1092 config CMD_NAND_TORTURE
1095 NAND torture support.
1104 NVM Express device support
1107 bool "onenand - access to onenand device"
1110 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1111 various useful features. This command allows reading, writing,
1112 and erasing blocks. It allso provides a way to show and change
1113 bad blocks, and test the device.
1118 Enable the 'osd' command which allows to query information from and
1119 write text data to a on-screen display (OSD) device; a virtual device
1120 associated with a display capable of displaying a text overlay on the
1121 display it's associated with..
1125 select HAVE_BLOCK_DEVICE
1126 select PARTITION_UUIDS
1128 Read and display information about the partition table on
1132 bool "pci - Access PCI devices"
1134 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1135 used on some devices to allow the CPU to communicate with its
1136 peripherals. Sub-commands allow bus enumeration, displaying and
1137 changing configuration space and a few other features.
1140 bool "pinmux - show pins muxing"
1141 default y if PINCTRL
1143 Parse all available pin-controllers and show pins muxing. This
1144 is useful for debug purpoer to check the pin muxing and to know if
1145 a pin is configured as a GPIO or as an alternate function.
1150 Poweroff/Shutdown the system
1153 bool "read - Read binary data from a partition"
1155 Provides low-level access to the data in a partition.
1157 config CMD_REMOTEPROC
1159 depends on REMOTEPROC
1161 Support for Remote Processor control
1164 bool "sata - Access SATA subsystem"
1167 SATA (Serial Advanced Technology Attachment) is a serial bus
1168 standard for connecting to hard drives and other storage devices.
1169 This command provides information about attached devices and allows
1170 reading, writing and other operations.
1172 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1173 Attachment, where AT refers to an IBM AT (Advanced Technology)
1174 computer released in 1984.
1177 bool "saves - Save a file over serial in S-Record format"
1179 Provides a way to save a binary file using the Motorola S-Record
1180 format over the serial line.
1183 bool "scsi - Access to SCSI devices"
1186 This provides a 'scsi' command which provides access to SCSI (Small
1187 Computer System Interface) devices. The command provides a way to
1188 scan the bus, reset the bus, read and write data and get information
1192 bool "sdram - Print SDRAM configuration information"
1194 Provides information about attached SDRAM. This assumed that the
1195 SDRAM has an EEPROM with information that can be read using the
1196 I2C bus. This is only available on some boards.
1200 depends on DM_SPI_FLASH || SPI_FLASH
1201 default y if DM_SPI_FLASH
1206 bool "sf test - Allow testing of SPI flash"
1209 Provides a way to test that SPI flash is working correctly. The
1210 test is destructive, in that an area of SPI flash must be provided
1211 for the test to use. Performance information is also provided,
1212 measuring the performance of reading, writing and erasing in
1213 Mbps (Million Bits Per Second). This value should approximately
1214 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1215 everything is working properly.
1218 bool "sspi - Command to access spi device"
1221 SPI utility command.
1223 config DEFAULT_SPI_BUS
1224 int "default spi bus used by sspi command"
1228 config DEFAULT_SPI_MODE
1229 hex "default spi mode used by sspi command (see include/spi.h)"
1234 bool "tsi148 - Command to access tsi148 device"
1236 This provides various sub-commands to initialise and configure the
1237 Turndra tsi148 device. See the command help for full details.
1240 bool "Enable UFS - Universal Flash Subsystem commands"
1243 "This provides commands to initialise and configure universal flash
1247 bool "universe - Command to set up the Turndra Universe controller"
1249 This allows setting up the VMEbus provided by this controller.
1250 See the command help for full details.
1254 select HAVE_BLOCK_DEVICE
1260 select USB_FUNCTION_SDP
1262 Enables the command "sdp" which is used to have U-Boot emulating the
1263 Serial Download Protocol (SDP) via USB.
1267 depends on USB_FUNCTION_ROCKUSB
1269 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1270 read/write info, image to/from devices. This enable rockusb command
1271 support to communication with rockusb device. for more detail about
1272 this command, please read doc/README.rockusb.
1274 config CMD_USB_MASS_STORAGE
1275 bool "UMS usb mass storage"
1276 select USB_FUNCTION_MASS_STORAGE
1278 USB mass storage support
1285 VirtIO block device support
1291 This provides commands to control the watchdog timer devices.
1297 Enable the command "axi" for accessing AXI (Advanced eXtensible
1298 Interface) busses, a on-chip interconnect specification for managing
1299 functional blocks in SoC designs, which is also often used in designs
1300 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1304 menu "Shell scripting commands"
1310 Echo args to console
1316 Return true/false on integer compare.
1322 Run script from memory
1328 Evaluate boolean and math expressions and store the result in an env
1330 Also supports loading the value at a memory location into a variable.
1331 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1335 menu "Android support commands"
1337 config CMD_AB_SELECT
1340 depends on ANDROID_AB
1342 On Android devices with more than one boot slot (multiple copies of
1343 the kernel and system images) this provides a command to select which
1344 slot should be used to boot from and register the boot attempt. This
1345 is used by the new A/B update model where one slot is updated in the
1346 background while running from the other slot.
1353 bool "Network commands"
1363 bootp - boot image via network using BOOTP/TFTP protocol
1367 depends on CMD_BOOTP
1369 Boot image via network using DHCP/TFTP protocol
1371 config BOOTP_BOOTPATH
1372 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1374 depends on CMD_BOOTP
1376 Even though the config is called BOOTP_BOOTPATH, it stores the
1377 path in the variable 'rootpath'.
1380 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1382 depends on CMD_BOOTP
1384 The primary DNS server is stored as 'dnsip'. If two servers are
1385 returned, you must set BOOTP_DNS2 to store that second server IP
1389 bool "Store 'dnsip2' from BOOTP/DHCP server"
1390 depends on BOOTP_DNS
1392 If a DHCP client requests the DNS server IP from a DHCP server,
1393 it is possible that more than one DNS serverip is offered to the
1394 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1395 server IP will be stored in the additional environment
1396 variable "dnsip2". The first DNS serverip is always
1397 stored in the variable "dnsip", when BOOTP_DNS is defined.
1399 config BOOTP_GATEWAY
1400 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1402 depends on CMD_BOOTP
1404 config BOOTP_HOSTNAME
1405 bool "Request & store 'hostname' from BOOTP/DHCP server"
1407 depends on CMD_BOOTP
1409 The name may or may not be qualified with the local domain name.
1411 config BOOTP_PREFER_SERVERIP
1412 bool "serverip variable takes precedent over DHCP server IP."
1413 depends on CMD_BOOTP
1415 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1417 With this option enabled, the 'serverip' variable in the environment
1418 takes precedence over DHCP server IP and will only be set by the DHCP
1419 server if not already set in the environment.
1421 config BOOTP_SUBNETMASK
1422 bool "Request & store 'netmask' from BOOTP/DHCP server"
1424 depends on CMD_BOOTP
1426 config BOOTP_NTPSERVER
1427 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1428 depends on CMD_BOOTP
1433 Selecting this will allow capturing all Ethernet packets and store
1434 them in physical memory in a PCAP formated file,
1435 later to be analyzed by PCAP reader application (IE. WireShark).
1438 bool "Send PXE client arch to BOOTP/DHCP server"
1440 depends on CMD_BOOTP && CMD_PXE
1442 Supported for ARM, ARM64, and x86 for now.
1444 config BOOTP_PXE_CLIENTARCH
1446 depends on BOOTP_PXE
1447 default 0x16 if ARM64
1451 config BOOTP_VCI_STRING
1453 depends on CMD_BOOTP
1454 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1455 default "U-Boot.armv8" if ARM64
1456 default "U-Boot.arm" if ARM
1463 tftpboot - boot image via network using TFTP protocol
1467 depends on CMD_TFTPBOOT
1469 TFTP put command, for uploading files to a server
1473 depends on CMD_TFTPBOOT
1475 Act as a TFTP server and boot the first received file
1477 config NET_TFTP_VARS
1478 bool "Control TFTP timeout and count through environment"
1479 depends on CMD_TFTPBOOT
1482 If set, allows controlling the TFTP timeout through the
1483 environment variable tftptimeout, and the TFTP maximum
1484 timeout count through the variable tftptimeoutcountmax.
1485 If unset, timeout and maximum are hard-defined as 1 second
1486 and 10 timouts per TFTP transfer.
1491 Boot image via network using RARP/TFTP protocol
1497 Boot image via network using NFS protocol.
1503 If set, allows 802.3(clause 22) MII Management functions interface access
1504 The management interface specified in Clause 22 provides
1505 a simple, two signal, serial interface to connect a
1506 Station Management entity and a managed PHY for providing access
1507 to management parameters and services.
1508 The interface is referred to as the MII management interface.
1514 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1515 The MDIO interface is orthogonal to the MII interface and extends
1516 it by adding access to more registers through indirect addressing.
1521 Send ICMP ECHO_REQUEST to network host
1526 Perform CDP network configuration
1531 Synchronize RTC via network
1536 Lookup the IP of a hostname
1538 config CMD_LINK_LOCAL
1542 Acquire a network IP address using the link-local protocol
1549 Allow control of L2 Ethernet switch commands. These are supported
1550 by the vsc9953 Ethernet driver at present. Sub-commands allow
1551 operations such as enabling / disabling a port and
1552 viewing/maintaining the filtering database (FDB)
1558 Boot image via network using PXE protocol
1563 Wait for wake-on-lan Magic Packet
1567 menu "Misc commands"
1570 bool "Enable 'bmp' command"
1571 depends on LCD || DM_VIDEO || VIDEO
1573 This provides a way to obtain information about a BMP-format image
1574 and to display it. BMP (which presumably stands for BitMaP) is a
1575 file format defined by Microsoft which supports images of various
1576 depths, formats and compression methods. Headers on the file
1577 determine the formats used. This command can be used by first loading
1578 the image into RAM, then using this command to look at it or display
1581 config CMD_BOOTCOUNT
1583 depends on BOOTCOUNT_LIMIT
1585 Enable the bootcount command, which allows interrogation and
1586 reset of the bootcounter.
1589 bool "Enable board-specific commands"
1591 (deprecated: instead, please define a Kconfig option for each command)
1593 Some boards have board-specific commands which are only enabled
1594 during developemnt and need to be turned off for production. This
1595 option provides a way to control this. The commands that are enabled
1596 vary depending on the board.
1598 config CMD_BKOPS_ENABLE
1599 bool "mmc bkops enable"
1603 Enable command for setting manual background operations handshake
1604 on a eMMC device. The feature is optionally available on eMMC devices
1605 conforming to standard >= 4.41.
1607 config CMD_BLOCK_CACHE
1608 bool "blkcache - control and stats for block cache"
1609 depends on BLOCK_CACHE
1610 default y if BLOCK_CACHE
1612 Enable the blkcache command, which can be used to control the
1613 operation of the cache functions.
1614 This is most useful when fine-tuning the operation of the cache
1615 during development, but also allows the cache to be disabled when
1616 it might hurt performance (e.g. when using the ums command).
1619 bool "icache or dcache"
1621 Enable the "icache" and "dcache" commands
1623 config CMD_CONITRACE
1624 bool "conitrace - trace console input codes"
1626 Enable the 'conitrace' command which displays the codes received
1627 from the console input as hexadecimal numbers.
1630 bool "Enable clear screen command 'cls'"
1631 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1634 Enable the 'cls' command which clears the screen contents
1635 on video frame buffer.
1638 bool "efidebug - display/configure UEFI environment"
1639 depends on EFI_LOADER
1640 select EFI_DEVICE_PATH_TO_TEXT
1643 Enable the 'efidebug' command which provides a subset of UEFI
1644 shell utility with simplified functionality. It will be useful
1645 particularly for managing boot parameters as well as examining
1646 various EFI status for debugging.
1648 config CMD_EXCEPTION
1649 bool "exception - raise exception"
1650 depends on ARM || RISCV || X86
1652 Enable the 'exception' command which allows to raise an exception.
1659 Enable the 'led' command which allows for control of LEDs supported
1660 by the board. The LEDs can be listed with 'led list' and controlled
1661 with led on/off/togle/blink. Any LED drivers can be controlled with
1662 this command, e.g. led_gpio.
1669 Enable the 'date' command for getting/setting the time/date in RTC
1675 Run commands and summarize execution time.
1678 bool "gettime - read elapsed time"
1680 Enable the 'gettime' command which reads the elapsed time since
1681 U-Boot started running. This shows the time in seconds and
1682 milliseconds. See also the 'bootstage' command which provides more
1683 flexibility for boot timing.
1690 Print bytes from the hardware random number generator.
1692 # TODO: rename to CMD_SLEEP
1697 Delay execution for some time
1700 bool "support for multiprocessor"
1702 This provides an option to brinup
1703 different processors in multiprocessor
1709 Access the system timer.
1715 This provides basic access to the U-Boot's sound support. The main
1716 feature is to play a beep.
1718 sound init - set up sound system
1719 sound play - play a sound
1725 Boot image via local extlinux.conf file
1731 This provides access to the QEMU firmware interface. The main
1732 feature is to allow easy loading of files passed to qemu-system
1733 via -kernel / -initrd
1735 source "cmd/mvebu/Kconfig"
1738 bool "terminal - provides a way to attach a serial terminal"
1740 Provides a 'cu'-like serial terminal command. This can be used to
1741 access other serial ports from the system console. The terminal
1742 is very simple with no special processing of characters. As with
1743 cu, you can press ~. (tilde followed by period) to exit.
1746 bool "uuid, guid - generation of unique IDs"
1749 This enables two commands:
1751 uuid - generate random Universally Unique Identifier
1752 guid - generate Globally Unique Identifier based on random UUID
1754 The two commands are very similar except for the endianness of the
1759 source "cmd/ti/Kconfig"
1761 config CMD_BOOTSTAGE
1762 bool "Enable the 'bootstage' command"
1763 depends on BOOTSTAGE
1765 Add a 'bootstage' command which supports printing a report
1766 and un/stashing of bootstage data.
1768 menu "Power commands"
1770 bool "Enable Driver Model PMIC command"
1773 This is the pmic command, based on a driver model pmic's API.
1774 Command features are unchanged:
1775 - list - list pmic devices
1776 - pmic dev <id> - show or [set] operating pmic device (NEW)
1777 - pmic dump - dump registers
1778 - pmic read address - read byte of register at address
1779 - pmic write address - write byte to register at address
1780 The only one change for this command is 'dev' subcommand.
1782 config CMD_REGULATOR
1783 bool "Enable Driver Model REGULATOR command"
1784 depends on DM_REGULATOR
1786 This command is based on driver model regulator's API.
1787 User interface features:
1788 - list - list regulator devices
1789 - regulator dev <id> - show or [set] operating regulator device
1790 - regulator info - print constraints info
1791 - regulator status - print operating status
1792 - regulator value <val] <-f> - print/[set] voltage value [uV]
1793 - regulator current <val> - print/[set] current value [uA]
1794 - regulator mode <id> - print/[set] operating mode id
1795 - regulator enable - enable the regulator output
1796 - regulator disable - disable the regulator output
1798 The '-f' (force) option can be used for set the value which exceeds
1799 the limits, which are found in device-tree and are kept in regulator's
1800 uclass platdata structure.
1804 menu "Security commands"
1806 bool "Enable the 'aes' command"
1809 This provides a means to encrypt and decrypt data using the AES
1810 (Advanced Encryption Standard). This algorithm uses a symetric key
1811 and is widely used as a streaming cipher. Different key lengths are
1812 supported by the algorithm but this command only supports 128 bits
1816 bool "Enable the 'blob' command"
1818 This is used with the Freescale secure boot mechanism.
1820 Freescale's SEC block has built-in Blob Protocol which provides
1821 a method for protecting user-defined data across system power
1822 cycles. SEC block protects data in a data structure called a Blob,
1823 which provides both confidentiality and integrity protection.
1825 Encapsulating data as a blob
1826 Each time that the Blob Protocol is used to protect data, a
1827 different randomly generated key is used to encrypt the data.
1828 This random key is itself encrypted using a key which is derived
1829 from SoC's non-volatile secret key and a 16 bit Key identifier.
1830 The resulting encrypted key along with encrypted data is called a
1831 blob. The non-volatile secure key is available for use only during
1834 During decapsulation, the reverse process is performed to get back
1838 blob enc - encapsulating data as a cryptgraphic blob
1839 blob dec - decapsulating cryptgraphic blob to get the data
1843 blob enc src dst len km
1845 Encapsulate and create blob of data $len bytes long
1846 at address $src and store the result at address $dst.
1847 $km is the 16 byte key modifier is also required for
1848 generation/use as key for cryptographic operation. Key
1849 modifier should be 16 byte long.
1851 blob dec src dst len km
1853 Decapsulate the blob of data at address $src and
1854 store result of $len byte at addr $dst.
1855 $km is the 16 byte key modifier is also required for
1856 generation/use as key for cryptographic operation. Key
1857 modifier should be 16 byte long.
1860 bool "Support 'hash' command"
1863 This provides a way to hash data in memory using various supported
1864 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1865 saved to memory or to an environment variable. It is also possible
1866 to verify a hash against data in memory.
1869 bool "Support the 'hvc' command"
1870 depends on ARM_SMCCC
1872 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1873 development and testing.
1876 bool "Support the 'smc' command"
1877 depends on ARM_SMCCC
1879 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1880 development and testing.
1886 Add -v option to verify data against a hash.
1896 bool "Enable the 'tpm' command"
1897 depends on TPM_V1 || TPM_V2
1898 select CMD_TPM_V1 if TPM_V1
1899 select CMD_TPM_V2 if TPM_V2
1901 This provides a means to talk to a TPM from the command line. A wide
1902 range of commands if provided - see 'tpm help' for details. The
1903 command requires a suitable TPM on your board and the correct driver
1909 bool "Enable the 'tpm test' command"
1912 This provides a a series of tests to confirm that the TPMv1.x is
1913 working correctly. The tests cover initialisation, non-volatile RAM,
1914 extend, global lock and checking that timing is within expectations.
1915 The tests pass correctly on Infineon TPMs but may need to be adjusted
1922 menu "Firmware commands"
1924 bool "Enable crosec command"
1928 Enable command-line access to the Chrome OS EC (Embedded
1929 Controller). This provides the 'crosec' command which has
1930 a number of sub-commands for performing EC tasks such as
1931 updating its flash, accessing a small saved context area
1932 and talking to the I2C bus behind the EC (if there is one).
1935 menu "Filesystem commands"
1937 bool "Enable the 'btrsubvol' command"
1940 This enables the 'btrsubvol' command to list subvolumes
1941 of a BTRFS filesystem. There are no special commands for
1942 listing BTRFS directories or loading BTRFS files - this
1943 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1944 when BTRFS is enabled (see FS_BTRFS).
1947 bool "Enable the 'cbfs' command"
1950 Define this to enable support for reading from a Coreboot
1951 filesystem. This is a ROM-based filesystem used for accessing files
1952 on systems that use coreboot as the first boot-loader and then load
1953 U-Boot to actually boot the Operating System. Available commands are
1954 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1957 bool "Enable the 'cramfs' command"
1958 depends on FS_CRAMFS
1960 This provides commands for dealing with CRAMFS (Compressed ROM
1961 filesystem). CRAMFS is useful when space is tight since files are
1962 compressed. Two commands are provided:
1964 cramfsls - lists files in a cramfs image
1965 cramfsload - loads a file from a cramfs image
1968 bool "ext2 command support"
1971 Enables EXT2 FS command
1974 bool "ext4 command support"
1977 Enables EXT4 FS command
1979 config CMD_EXT4_WRITE
1981 bool "ext4 write command support"
1984 Enables EXT4 FS write command
1987 bool "FAT command support"
1990 Support for the FAT fs
1992 config CMD_FS_GENERIC
1993 bool "filesystem commands"
1995 Enables filesystem commands (e.g. load, ls) that work for multiple
1999 bool "fsuuid command"
2001 Enables fsuuid command for filesystem UUID.
2004 bool "jffs2 command"
2007 Enables commands to support the JFFS2 (Journalling Flash File System
2008 version 2) filesystem. This enables fsload, ls and fsinfo which
2009 provide the ability to load files, list directories and obtain
2010 filesystem information.
2013 bool "MTD partition support"
2016 MTD partitioning tool support.
2017 It is strongly encouraged to avoid using this command
2018 anymore along with 'sf', 'nand', 'onenand'. One can still
2019 declare the partitions in the mtdparts environment variable
2020 but better use the MTD stack and the 'mtd' command instead.
2022 config CMD_MTDPARTS_SPREAD
2023 bool "Padd partition size to take account of bad blocks"
2024 depends on CMD_MTDPARTS
2026 This enables the 'spread' sub-command of the mtdparts command.
2027 This command will modify the existing mtdparts variable by increasing
2028 the size of the partitions such that 1) each partition's net size is
2029 at least as large as the size specified in the mtdparts variable and
2030 2) each partition starts on a good block.
2032 config CMD_MTDPARTS_SHOW_NET_SIZES
2033 bool "Show net size (w/o bad blocks) of partitions"
2034 depends on CMD_MTDPARTS
2036 Adds two columns to the printed partition table showing the
2037 effective usable size of a partition, if bad blocks are taken
2040 config MTDIDS_DEFAULT
2041 string "Default MTD IDs"
2042 depends on MTD || SPI_FLASH
2044 Defines a default MTD IDs list for use with MTD partitions in the
2045 Linux MTD command line partitions format.
2047 config MTDPARTS_DEFAULT
2048 string "Default MTD partition scheme"
2049 depends on MTD || SPI_FLASH
2051 Defines a default MTD partitioning scheme in the Linux MTD command
2052 line partitions format
2055 bool "reiser - Access to reiserfs filesystems"
2057 This provides two commands which operate on a resierfs filesystem,
2058 commonly used some years ago:
2060 reiserls - list files
2061 reiserload - load a file
2064 bool "yaffs2 - Access of YAFFS2 filesystem"
2068 This provides commands for accessing a YAFFS2 filesystem. Yet
2069 Another Flash Filesystem 2 is a filesystem designed specifically
2070 for NAND flash. It incorporates bad-block management and ensures
2071 that device writes are sequential regardless of filesystem
2075 bool "zfs - Access of ZFS filesystem"
2077 This provides commands to accessing a ZFS filesystem, commonly used
2078 on Solaris systems. Two sub-commands are provided:
2080 zfsls - list files in a directory
2081 zfsload - load a file
2083 See doc/README.zfs for more details.
2087 menu "Debug commands"
2092 The bedbug (emBEDded deBUGger) command provides debugging features
2093 for some PowerPC processors. For details please see the
2094 docuemntation in doc/README.beddbug
2097 bool "diag - Board diagnostics"
2099 This command provides access to board diagnostic tests. These are
2100 called Power-on Self Tests (POST). The command allows listing of
2101 available tests and running either all the tests, or specific tests
2105 bool "irq - Show information about interrupts"
2106 depends on !ARM && !MIPS && !SH
2108 This enables two commands:
2110 interrupts - enable or disable interrupts
2111 irqinfo - print device-specific interrupt information
2114 bool "kgdb - Allow debugging of U-Boot with gdb"
2117 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2118 over a serial link for debugging purposes. This allows
2119 single-stepping, inspecting variables, etc. This is supported only
2120 on PowerPC at present.
2123 bool "log - Generation, control and access to logging"
2126 This provides access to logging features. It allows the output of
2127 log data to be controlled to a limited extent (setting up the default
2128 maximum log level for emitting of records). It also provides access
2129 to a command used for testing the log system.
2132 bool "trace - Support tracing of function calls and timing"
2134 Enables a command to control using of function tracing within
2135 U-Boot. This allows recording of call traces including timing
2136 information. The command can write data to memory for exporting
2137 for analysis (e.g. using bootchart). See doc/README.trace for full
2141 bool "avb - Android Verified Boot 2.0 operations"
2142 depends on AVB_VERIFY
2145 Enables a "avb" command to perform verification of partitions using
2146 Android Verified Boot 2.0 functionality. It includes such subcommands:
2147 avb init - initialize avb2 subsystem
2148 avb read_rb - read rollback index
2149 avb write_rb - write rollback index
2150 avb is_unlocked - check device lock state
2151 avb get_uuid - read and print uuid of a partition
2152 avb read_part - read data from partition
2153 avb read_part_hex - read data from partition and output to stdout
2154 avb write_part - write data to partition
2155 avb verify - run full verification chain
2159 tristate "Enable UBI - Unsorted block images commands"
2162 UBI is a software layer above MTD layer which admits use of LVM-like
2163 logical volumes on top of MTD devices, hides some complexities of
2164 flash chips like wear and bad blocks and provides some other useful
2165 capabilities. Please, consult the MTD web site for more details
2166 (www.linux-mtd.infradead.org). Activate this option if you want
2167 to use U-Boot UBI commands.
2168 It is also strongly encouraged to also enable CONFIG_MTD to get full
2172 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2174 default y if CMD_UBI
2177 UBIFS is a file system for flash devices which works on top of UBI.