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.
391 depends on ANDROID_BOOT_IMAGE
393 Android Boot Image manipulation commands. Allows one to extract
394 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
395 obtain corresponding meta-information from boot.img.
398 bool "bootelf, bootvx"
401 Boot an ELF/vxWorks image from the memory.
404 bool "Flattened Device Tree utility commands"
408 Do FDT related setup before booting into the Operating System.
414 Start an application at a given address.
420 Run the command in the given environment variable.
426 Print header information for application image.
431 List all images found in flash
437 Extract a part of a multi-image.
440 bool "spl export - Export boot information for Falcon boot"
443 Falcon mode allows booting directly from SPL into an Operating
444 System such as Linux, thus skipping U-Boot proper. See
445 doc/README.falcon for full information about how to use this
448 config CMD_SPL_NAND_OFS
449 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
450 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
453 This provides the offset of the command line arguments for Linux
454 when booting from NAND in Falcon mode. See doc/README.falcon
455 for full information about how to use this option (and also see
456 board/gateworks/gw_ventana/README for an example).
458 config CMD_SPL_NOR_OFS
459 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
460 depends on CMD_SPL && SPL_NOR_SUPPORT
463 This provides the offset of the command line arguments or dtb for
464 Linux when booting from NOR in Falcon mode.
466 config CMD_SPL_WRITE_SIZE
467 hex "Size of argument area"
471 This provides the size of the command-line argument area in NAND
472 flash used by Falcon-mode boot. See the documentation until CMD_SPL
476 bool "fitImage update command"
478 Implements the 'fitupd' command, which allows to automatically
479 store software updates present on a TFTP server in NOR Flash
481 config CMD_THOR_DOWNLOAD
482 bool "thor - TIZEN 'thor' download"
485 Implements the 'thor' download protocol. This is a way of
486 downloading a software update over USB from an attached host.
487 There is no documentation about this within the U-Boot source code
488 but you should be able to find something on the interwebs.
491 bool "zboot - x86 boot command"
493 With x86 machines it is common to boot a bzImage file which
494 contains both a kernel and a setup.bin file. The latter includes
495 configuration information from the dark ages which x86 boards still
496 need to pick things out of.
498 Consider using FIT in preference to this since it supports directly
499 booting both 32- and 64-bit kernels, as well as secure boot.
500 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
504 menu "Environment commands"
507 bool "ask for env variable"
509 Ask for environment variable
527 Edit environment variable.
532 Allow for searching environment variables
538 Save all environment variables into the compiled-in persistent
544 depends on CMD_SAVEENV
546 Erase environment variables from the compiled-in persistent
549 config CMD_ENV_EXISTS
553 Check if a variable is defined in the environment for use in
556 config CMD_ENV_CALLBACK
557 bool "env callbacks - print callbacks and their associated variables"
559 Some environment variable have callbacks defined by
560 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
561 For example changing "baudrate" adjust the serial baud rate. This
562 command lists the currently defined callbacks.
565 bool "env flags -print variables that have non-default flags"
567 Some environment variables have special flags that control their
568 behaviour. For example, serial# can only be written once and cannot
569 be deleted. This command shows the variables that have special
572 config CMD_NVEDIT_EFI
573 bool "env [set|print] -e - set/print UEFI variables"
574 depends on EFI_LOADER
577 UEFI variables are encoded as some form of U-Boot variables.
578 If enabled, we are allowed to set/print UEFI variables using
579 "env" command with "-e" option without knowing details.
581 config CMD_NVEDIT_INFO
582 bool "env info - print or evaluate environment information"
584 Print environment information:
585 - env_valid : is environment valid
586 - env_ready : is environment imported into hash table
587 - env_use_default : is default environment used
589 This command can be optionally used for evaluation in scripts:
590 [-d] : evaluate whether default environment is used
591 [-p] : evaluate whether environment can be persisted
592 The result of multiple evaluations will be combined with AND.
596 menu "Memory commands"
601 Compute binary operations (xor, or, and) of byte arrays of arbitrary
602 size from memory and store the result in memory or the environment.
615 Add -v option to verify data against a crc32 checksum.
618 bool "eeprom - EEPROM subsystem"
620 (deprecated, needs conversion to driver model)
621 Provides commands to read and write EEPROM (Electrically Erasable
622 Programmable Read Only Memory) chips that are connected over an
625 config CMD_EEPROM_LAYOUT
626 bool "Enable layout-aware eeprom commands"
627 depends on CMD_EEPROM
629 (deprecated, needs conversion to driver model)
630 When enabled, additional eeprom sub-commands become available.
632 eeprom print - prints the contents of the eeprom in a human-readable
633 way (eeprom layout fields, and data formatted to be fit for human
636 eeprom update - allows user to update eeprom fields by specifying
637 the field name, and providing the new data in a human readable format
638 (same format as displayed by the eeprom print command).
640 Both commands can either auto detect the layout, or be told which
644 __weak int parse_layout_version(char *str)
645 - override to provide your own layout name parsing
646 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
648 - override to setup the layout metadata based on the version
649 __weak int eeprom_layout_detect(unsigned char *data)
650 - override to provide your own algorithm for detecting layout
653 - contains various printing and updating functions for common
654 types of eeprom fields. Can be used for defining
657 config EEPROM_LAYOUT_HELP_STRING
658 string "Tells user what layout names are supported"
659 depends on CMD_EEPROM_LAYOUT
660 default "<not defined>"
662 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
668 Infinite write loop on address range
675 Compute MD5 checksum.
680 depends on CMD_MD5SUM
682 Add -v option to verify data against an MD5 checksum.
687 Display memory information.
690 bool "md, mm, nm, mw, cp, cmp, base, loop"
695 mm - memory modify (auto-incrementing address)
696 nm - memory modify (constant address)
697 mw - memory write (fill)
700 base - print or set address offset
701 loop - initialize loop on address range
704 bool "Enable cyclic md/mw commands"
705 depends on CMD_MEMORY
707 Add the "mdc" and "mwc" memory commands. These are cyclic
712 This command will print 4 bytes (10,11,12,13) each 500 ms.
714 => mwc.l 100 12345678 10
715 This command will write 12345678 to address 100 all 10 ms.
720 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
722 random - fill memory with random data
727 Simple RAM read/write test.
731 config SYS_ALT_MEMTEST
732 bool "Alternative test"
734 Use a more complete alternative memory test.
741 mdc - memory display cyclic
742 mwc - memory write cyclic
748 Compute SHA1 checksum.
750 config SHA1SUM_VERIFY
752 depends on CMD_SHA1SUM
754 Add -v option to verify data against a SHA1 checksum.
757 bool "strings - display strings in memory"
759 This works similarly to the Unix 'strings' command except that it
760 works with a memory range. String of printable characters found
761 within the range are displayed. The minimum number of characters
762 for a sequence to be considered a string can be provided.
766 menu "Compression commands"
770 default y if CMD_BOOTI
773 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
778 default y if CMD_BOOTI
780 Uncompress a zip-compressed memory region.
785 Compress a memory region with zlib deflate method.
789 menu "Device access commands"
792 #depends on FLASH_CFI_DRIVER
795 ARM Ltd reference designs flash partition access
798 bool "adc - Access Analog to Digital Converters info and data"
802 Shows ADC device info and permit printing one-shot analog converted
803 data from a named Analog to Digital Converter.
808 depends on PARTITIONS
810 Read/modify/write the fields of Bootloader Control Block, usually
811 stored on the flash "misc" partition with its structure defined in:
812 https://android.googlesource.com/platform/bootable/recovery/+/master/
813 bootloader_message/include/bootloader_message/bootloader_message.h
815 Some real-life use-cases include (but are not limited to):
816 - Determine the "boot reason" (and act accordingly):
817 https://source.android.com/devices/bootloader/boot-reason
818 - Get/pass a list of commands from/to recovery:
819 https://android.googlesource.com/platform/bootable/recovery
820 - Inspect/dump the contents of the BCB fields
823 bool "bind/unbind - Bind or unbind a device to/from a driver"
826 Bind or unbind a device to/from a driver from the command line.
827 This is useful in situations where a device may be handled by several
828 drivers. For example, this can be used to bind a UDC to the usb ether
829 gadget driver from the command line.
832 bool "clk - Show clock frequencies"
835 Shows clock frequences by calling a sock_clk_dump() hook function.
836 This is depreated in favour of using the CLK uclass and accessing
837 clock values from associated drivers. However currently no command
841 bool "demo - Demonstration commands for driver model"
844 Provides a 'demo' command which can be used to play around with
845 driver model. To use this properly you will need to enable one or
846 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
847 Otherwise you will always get an empty list of devices. The demo
848 devices are defined in the sandbox device tree, so the easiest
849 option is to use sandbox and pass the -d point to sandbox's
856 Enables the command "dfu" which is used to have U-Boot create a DFU
857 class device via USB. This command requires that the "dfu_alt_info"
858 environment variable be set and define the alt settings to expose to
862 bool "dm - Access to driver model information"
865 Provides access to driver model data structures and information,
866 such as a list of devices, list of uclasses and the state of each
867 device (e.g. activated). This is not required for operation, but
868 can be useful to see the state of driver model for debugging or
872 bool "fastboot - Android fastboot support"
875 This enables the command "fastboot" which enables the Android
876 fastboot mode for the platform. Fastboot is a protocol for
877 downloading images, flashing and device control used on
878 Android devices. Fastboot requires either the network stack
879 enabled or support for acting as a USB device.
881 See doc/android/fastboot.txt for more information.
884 bool "flinfo, erase, protect"
886 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
889 flinfo - print FLASH memory information
891 protect - enable or disable FLASH write protection
900 config CMD_FPGA_LOADBP
901 bool "fpga loadbp - load partial bitstream (Xilinx only)"
904 Supports loading an FPGA device from a bitstream buffer containing
907 config CMD_FPGA_LOADFS
908 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
911 Supports loading an FPGA device from a FAT filesystem.
913 config CMD_FPGA_LOADMK
914 bool "fpga loadmk - load bitstream from image"
917 Supports loading an FPGA device from a image generated by mkimage.
919 config CMD_FPGA_LOADP
920 bool "fpga loadp - load partial bitstream"
923 Supports loading an FPGA device from a bitstream buffer containing
926 config CMD_FPGA_LOAD_SECURE
927 bool "fpga loads - loads secure bitstreams (Xilinx only)"
930 Enables the fpga loads command which is used to load secure
931 (authenticated or encrypted or both) bitstreams on to FPGA.
934 bool "fpgad - dump FPGA registers"
936 (legacy, needs conversion to driver model)
937 Provides a way to dump FPGA registers by calling the board-specific
938 fpga_get_reg() function. This functions similarly to the 'md'
942 bool "fuse - support for the fuse subssystem"
944 (deprecated - needs conversion to driver model)
945 This allows reading, sensing, programming or overriding fuses
946 which control the behaviour of the device. The command uses the
955 bool "GPT (GUID Partition Table) command"
957 select HAVE_BLOCK_DEVICE
958 select PARTITION_UUIDS
961 Enable the 'gpt' command to ready and write GPT style partition
965 bool "GPT Random UUID generation"
968 Enable the generation of partitions with random UUIDs if none
971 config CMD_GPT_RENAME
972 bool "GPT partition renaming commands"
975 Enables the 'gpt' command to interchange names on two GPT
976 partitions via the 'gpt swap' command or to rename single
977 partitions via the 'rename' command.
980 bool "ide - Support for IDE drivers"
983 Provides an 'ide' command which allows accessing the IDE drive,
984 reseting the IDE interface, printing the partition table and
985 geting device info. It also enables the 'diskboot' command which
986 permits booting from an IDE drive.
989 bool "io - Support for performing I/O accesses"
991 Provides an 'iod' command to display I/O space and an 'iow' command
992 to write values to the I/O space. This can be useful for manually
993 checking the state of devices during boot when debugging device
997 bool "iotrace - Support for tracing I/O activity"
999 Provides an 'iotrace' command which supports recording I/O reads and
1000 writes in a trace buffer in memory . It also maintains a checksum
1001 of the trace records (even if space is exhausted) so that the
1002 sequence of I/O accesses can be verified.
1004 When debugging drivers it is useful to see what I/O accesses were
1005 done and in what order.
1007 Even if the individual accesses are of little interest it can be
1008 useful to verify that the access pattern is consistent each time
1009 an operation is performed. In this case a checksum can be used to
1010 characterise the operation of a driver. The checksum can be compared
1011 across different runs of the operation to verify that the driver is
1014 In particular, when performing major refactoring of the driver, where
1015 the access pattern should not change, the checksum provides assurance
1016 that the refactoring work has not broken the driver.
1018 This works by sneaking into the io.h heder for an architecture and
1019 redirecting I/O accesses through iotrace's tracing mechanism.
1021 For now no commands are provided to examine the trace buffer. The
1022 format is fairly simple, so 'md' is a reasonable substitute.
1024 Note: The checksum feature is only useful for I/O regions where the
1025 contents do not change outside of software control. Where this is not
1026 suitable you can fall back to manually comparing the addresses. It
1027 might be useful to enhance tracing to only checksum the accesses and
1028 not the data read/written.
1038 bool "w1 - Support for Dallas 1-Wire protocol"
1040 Dallas 1-wire protocol support
1046 Load a binary file over serial line.
1052 Load an S-Record file over serial line
1057 MMC memory mapped support.
1060 bool "Enable support for RPMB in the mmc command"
1063 Enable the commands for reading, writing and programming the
1064 key for the Replay Protection Memory Block partition in eMMC.
1066 config CMD_MMC_SWRITE
1068 depends on CMD_MMC && MMC_WRITE
1071 Enable support for the "mmc swrite" command to write Android sparse
1077 select MTD_PARTITIONS
1079 MTD commands support.
1083 default y if NAND_SUNXI
1084 depends on MTD_RAW_NAND
1089 config CMD_NAND_TRIMFFS
1090 bool "nand write.trimffs"
1091 default y if ARCH_SUNXI
1093 Allows one to skip empty pages when flashing something on a NAND.
1095 config CMD_NAND_LOCK_UNLOCK
1096 bool "nand lock/unlock"
1098 NAND locking support.
1100 config CMD_NAND_TORTURE
1103 NAND torture support.
1112 NVM Express device support
1115 bool "onenand - access to onenand device"
1118 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1119 various useful features. This command allows reading, writing,
1120 and erasing blocks. It allso provides a way to show and change
1121 bad blocks, and test the device.
1126 Enable the 'osd' command which allows to query information from and
1127 write text data to a on-screen display (OSD) device; a virtual device
1128 associated with a display capable of displaying a text overlay on the
1129 display it's associated with..
1133 select HAVE_BLOCK_DEVICE
1134 select PARTITION_UUIDS
1136 Read and display information about the partition table on
1140 bool "pci - Access PCI devices"
1142 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1143 used on some devices to allow the CPU to communicate with its
1144 peripherals. Sub-commands allow bus enumeration, displaying and
1145 changing configuration space and a few other features.
1148 bool "pinmux - show pins muxing"
1149 default y if PINCTRL
1151 Parse all available pin-controllers and show pins muxing. This
1152 is useful for debug purpoer to check the pin muxing and to know if
1153 a pin is configured as a GPIO or as an alternate function.
1158 Poweroff/Shutdown the system
1161 bool "read - Read binary data from a partition"
1163 Provides low-level access to the data in a partition.
1165 config CMD_REMOTEPROC
1167 depends on REMOTEPROC
1169 Support for Remote Processor control
1172 bool "sata - Access SATA subsystem"
1175 SATA (Serial Advanced Technology Attachment) is a serial bus
1176 standard for connecting to hard drives and other storage devices.
1177 This command provides information about attached devices and allows
1178 reading, writing and other operations.
1180 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1181 Attachment, where AT refers to an IBM AT (Advanced Technology)
1182 computer released in 1984.
1185 bool "saves - Save a file over serial in S-Record format"
1187 Provides a way to save a binary file using the Motorola S-Record
1188 format over the serial line.
1191 bool "scsi - Access to SCSI devices"
1194 This provides a 'scsi' command which provides access to SCSI (Small
1195 Computer System Interface) devices. The command provides a way to
1196 scan the bus, reset the bus, read and write data and get information
1200 bool "sdram - Print SDRAM configuration information"
1202 Provides information about attached SDRAM. This assumed that the
1203 SDRAM has an EEPROM with information that can be read using the
1204 I2C bus. This is only available on some boards.
1208 depends on DM_SPI_FLASH || SPI_FLASH
1209 default y if DM_SPI_FLASH
1214 bool "sf test - Allow testing of SPI flash"
1217 Provides a way to test that SPI flash is working correctly. The
1218 test is destructive, in that an area of SPI flash must be provided
1219 for the test to use. Performance information is also provided,
1220 measuring the performance of reading, writing and erasing in
1221 Mbps (Million Bits Per Second). This value should approximately
1222 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1223 everything is working properly.
1226 bool "sspi - Command to access spi device"
1229 SPI utility command.
1231 config DEFAULT_SPI_BUS
1232 int "default spi bus used by sspi command"
1236 config DEFAULT_SPI_MODE
1237 hex "default spi mode used by sspi command (see include/spi.h)"
1242 bool "tsi148 - Command to access tsi148 device"
1244 This provides various sub-commands to initialise and configure the
1245 Turndra tsi148 device. See the command help for full details.
1248 bool "Enable UFS - Universal Flash Subsystem commands"
1251 "This provides commands to initialise and configure universal flash
1255 bool "universe - Command to set up the Turndra Universe controller"
1257 This allows setting up the VMEbus provided by this controller.
1258 See the command help for full details.
1262 select HAVE_BLOCK_DEVICE
1268 select USB_FUNCTION_SDP
1270 Enables the command "sdp" which is used to have U-Boot emulating the
1271 Serial Download Protocol (SDP) via USB.
1275 depends on USB_FUNCTION_ROCKUSB
1277 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1278 read/write info, image to/from devices. This enable rockusb command
1279 support to communication with rockusb device. for more detail about
1280 this command, please read doc/README.rockusb.
1282 config CMD_USB_MASS_STORAGE
1283 bool "UMS usb mass storage"
1284 select USB_FUNCTION_MASS_STORAGE
1286 USB mass storage support
1293 VirtIO block device support
1299 This provides commands to control the watchdog timer devices.
1305 Enable the command "axi" for accessing AXI (Advanced eXtensible
1306 Interface) busses, a on-chip interconnect specification for managing
1307 functional blocks in SoC designs, which is also often used in designs
1308 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1312 menu "Shell scripting commands"
1318 Echo args to console
1324 Return true/false on integer compare.
1330 Run script from memory
1336 Evaluate boolean and math expressions and store the result in an env
1338 Also supports loading the value at a memory location into a variable.
1339 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1343 menu "Android support commands"
1345 config CMD_AB_SELECT
1348 depends on ANDROID_AB
1350 On Android devices with more than one boot slot (multiple copies of
1351 the kernel and system images) this provides a command to select which
1352 slot should be used to boot from and register the boot attempt. This
1353 is used by the new A/B update model where one slot is updated in the
1354 background while running from the other slot.
1361 bool "Network commands"
1371 bootp - boot image via network using BOOTP/TFTP protocol
1375 depends on CMD_BOOTP
1377 Boot image via network using DHCP/TFTP protocol
1379 config BOOTP_BOOTPATH
1380 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1382 depends on CMD_BOOTP
1384 Even though the config is called BOOTP_BOOTPATH, it stores the
1385 path in the variable 'rootpath'.
1388 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1390 depends on CMD_BOOTP
1392 The primary DNS server is stored as 'dnsip'. If two servers are
1393 returned, you must set BOOTP_DNS2 to store that second server IP
1397 bool "Store 'dnsip2' from BOOTP/DHCP server"
1398 depends on BOOTP_DNS
1400 If a DHCP client requests the DNS server IP from a DHCP server,
1401 it is possible that more than one DNS serverip is offered to the
1402 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1403 server IP will be stored in the additional environment
1404 variable "dnsip2". The first DNS serverip is always
1405 stored in the variable "dnsip", when BOOTP_DNS is defined.
1407 config BOOTP_GATEWAY
1408 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1410 depends on CMD_BOOTP
1412 config BOOTP_HOSTNAME
1413 bool "Request & store 'hostname' from BOOTP/DHCP server"
1415 depends on CMD_BOOTP
1417 The name may or may not be qualified with the local domain name.
1419 config BOOTP_PREFER_SERVERIP
1420 bool "serverip variable takes precedent over DHCP server IP."
1421 depends on CMD_BOOTP
1423 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1425 With this option enabled, the 'serverip' variable in the environment
1426 takes precedence over DHCP server IP and will only be set by the DHCP
1427 server if not already set in the environment.
1429 config BOOTP_SUBNETMASK
1430 bool "Request & store 'netmask' from BOOTP/DHCP server"
1432 depends on CMD_BOOTP
1434 config BOOTP_NTPSERVER
1435 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1436 depends on CMD_BOOTP
1441 Selecting this will allow capturing all Ethernet packets and store
1442 them in physical memory in a PCAP formated file,
1443 later to be analyzed by PCAP reader application (IE. WireShark).
1446 bool "Send PXE client arch to BOOTP/DHCP server"
1448 depends on CMD_BOOTP && CMD_PXE
1450 Supported for ARM, ARM64, and x86 for now.
1452 config BOOTP_PXE_CLIENTARCH
1454 depends on BOOTP_PXE
1455 default 0x16 if ARM64
1459 config BOOTP_VCI_STRING
1461 depends on CMD_BOOTP
1462 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1463 default "U-Boot.armv8" if ARM64
1464 default "U-Boot.arm" if ARM
1471 tftpboot - boot image via network using TFTP protocol
1475 depends on CMD_TFTPBOOT
1477 TFTP put command, for uploading files to a server
1481 depends on CMD_TFTPBOOT
1483 Act as a TFTP server and boot the first received file
1485 config NET_TFTP_VARS
1486 bool "Control TFTP timeout and count through environment"
1487 depends on CMD_TFTPBOOT
1490 If set, allows controlling the TFTP timeout through the
1491 environment variable tftptimeout, and the TFTP maximum
1492 timeout count through the variable tftptimeoutcountmax.
1493 If unset, timeout and maximum are hard-defined as 1 second
1494 and 10 timouts per TFTP transfer.
1499 Boot image via network using RARP/TFTP protocol
1505 Boot image via network using NFS protocol.
1511 If set, allows 802.3(clause 22) MII Management functions interface access
1512 The management interface specified in Clause 22 provides
1513 a simple, two signal, serial interface to connect a
1514 Station Management entity and a managed PHY for providing access
1515 to management parameters and services.
1516 The interface is referred to as the MII management interface.
1522 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1523 The MDIO interface is orthogonal to the MII interface and extends
1524 it by adding access to more registers through indirect addressing.
1529 Send ICMP ECHO_REQUEST to network host
1534 Perform CDP network configuration
1539 Synchronize RTC via network
1544 Lookup the IP of a hostname
1546 config CMD_LINK_LOCAL
1550 Acquire a network IP address using the link-local protocol
1557 Allow control of L2 Ethernet switch commands. These are supported
1558 by the vsc9953 Ethernet driver at present. Sub-commands allow
1559 operations such as enabling / disabling a port and
1560 viewing/maintaining the filtering database (FDB)
1566 Boot image via network using PXE protocol
1571 Wait for wake-on-lan Magic Packet
1575 menu "Misc commands"
1578 bool "Enable 'bmp' command"
1579 depends on LCD || DM_VIDEO || VIDEO
1581 This provides a way to obtain information about a BMP-format image
1582 and to display it. BMP (which presumably stands for BitMaP) is a
1583 file format defined by Microsoft which supports images of various
1584 depths, formats and compression methods. Headers on the file
1585 determine the formats used. This command can be used by first loading
1586 the image into RAM, then using this command to look at it or display
1589 config CMD_BOOTCOUNT
1591 depends on BOOTCOUNT_LIMIT
1593 Enable the bootcount command, which allows interrogation and
1594 reset of the bootcounter.
1597 bool "Enable board-specific commands"
1599 (deprecated: instead, please define a Kconfig option for each command)
1601 Some boards have board-specific commands which are only enabled
1602 during developemnt and need to be turned off for production. This
1603 option provides a way to control this. The commands that are enabled
1604 vary depending on the board.
1606 config CMD_BKOPS_ENABLE
1607 bool "mmc bkops enable"
1611 Enable command for setting manual background operations handshake
1612 on a eMMC device. The feature is optionally available on eMMC devices
1613 conforming to standard >= 4.41.
1615 config CMD_BLOCK_CACHE
1616 bool "blkcache - control and stats for block cache"
1617 depends on BLOCK_CACHE
1618 default y if BLOCK_CACHE
1620 Enable the blkcache command, which can be used to control the
1621 operation of the cache functions.
1622 This is most useful when fine-tuning the operation of the cache
1623 during development, but also allows the cache to be disabled when
1624 it might hurt performance (e.g. when using the ums command).
1627 bool "icache or dcache"
1629 Enable the "icache" and "dcache" commands
1631 config CMD_CONITRACE
1632 bool "conitrace - trace console input codes"
1634 Enable the 'conitrace' command which displays the codes received
1635 from the console input as hexadecimal numbers.
1638 bool "Enable clear screen command 'cls'"
1639 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1642 Enable the 'cls' command which clears the screen contents
1643 on video frame buffer.
1646 bool "efidebug - display/configure UEFI environment"
1647 depends on EFI_LOADER
1648 select EFI_DEVICE_PATH_TO_TEXT
1651 Enable the 'efidebug' command which provides a subset of UEFI
1652 shell utility with simplified functionality. It will be useful
1653 particularly for managing boot parameters as well as examining
1654 various EFI status for debugging.
1656 config CMD_EXCEPTION
1657 bool "exception - raise exception"
1658 depends on ARM || RISCV || X86
1660 Enable the 'exception' command which allows to raise an exception.
1667 Enable the 'led' command which allows for control of LEDs supported
1668 by the board. The LEDs can be listed with 'led list' and controlled
1669 with led on/off/togle/blink. Any LED drivers can be controlled with
1670 this command, e.g. led_gpio.
1677 Enable the 'date' command for getting/setting the time/date in RTC
1683 Run commands and summarize execution time.
1686 bool "gettime - read elapsed time"
1688 Enable the 'gettime' command which reads the elapsed time since
1689 U-Boot started running. This shows the time in seconds and
1690 milliseconds. See also the 'bootstage' command which provides more
1691 flexibility for boot timing.
1698 Print bytes from the hardware random number generator.
1700 # TODO: rename to CMD_SLEEP
1705 Delay execution for some time
1708 bool "support for multiprocessor"
1710 This provides an option to brinup
1711 different processors in multiprocessor
1717 Access the system timer.
1723 This provides basic access to the U-Boot's sound support. The main
1724 feature is to play a beep.
1726 sound init - set up sound system
1727 sound play - play a sound
1733 Boot image via local extlinux.conf file
1739 This provides access to the QEMU firmware interface. The main
1740 feature is to allow easy loading of files passed to qemu-system
1741 via -kernel / -initrd
1743 source "cmd/mvebu/Kconfig"
1746 bool "terminal - provides a way to attach a serial terminal"
1748 Provides a 'cu'-like serial terminal command. This can be used to
1749 access other serial ports from the system console. The terminal
1750 is very simple with no special processing of characters. As with
1751 cu, you can press ~. (tilde followed by period) to exit.
1754 bool "uuid, guid - generation of unique IDs"
1757 This enables two commands:
1759 uuid - generate random Universally Unique Identifier
1760 guid - generate Globally Unique Identifier based on random UUID
1762 The two commands are very similar except for the endianness of the
1767 source "cmd/ti/Kconfig"
1769 config CMD_BOOTSTAGE
1770 bool "Enable the 'bootstage' command"
1771 depends on BOOTSTAGE
1773 Add a 'bootstage' command which supports printing a report
1774 and un/stashing of bootstage data.
1776 menu "Power commands"
1778 bool "Enable Driver Model PMIC command"
1781 This is the pmic command, based on a driver model pmic's API.
1782 Command features are unchanged:
1783 - list - list pmic devices
1784 - pmic dev <id> - show or [set] operating pmic device (NEW)
1785 - pmic dump - dump registers
1786 - pmic read address - read byte of register at address
1787 - pmic write address - write byte to register at address
1788 The only one change for this command is 'dev' subcommand.
1790 config CMD_REGULATOR
1791 bool "Enable Driver Model REGULATOR command"
1792 depends on DM_REGULATOR
1794 This command is based on driver model regulator's API.
1795 User interface features:
1796 - list - list regulator devices
1797 - regulator dev <id> - show or [set] operating regulator device
1798 - regulator info - print constraints info
1799 - regulator status - print operating status
1800 - regulator value <val] <-f> - print/[set] voltage value [uV]
1801 - regulator current <val> - print/[set] current value [uA]
1802 - regulator mode <id> - print/[set] operating mode id
1803 - regulator enable - enable the regulator output
1804 - regulator disable - disable the regulator output
1806 The '-f' (force) option can be used for set the value which exceeds
1807 the limits, which are found in device-tree and are kept in regulator's
1808 uclass platdata structure.
1812 menu "Security commands"
1814 bool "Enable the 'aes' command"
1817 This provides a means to encrypt and decrypt data using the AES
1818 (Advanced Encryption Standard). This algorithm uses a symetric key
1819 and is widely used as a streaming cipher. Different key lengths are
1820 supported by the algorithm but this command only supports 128 bits
1824 bool "Enable the 'blob' command"
1826 This is used with the Freescale secure boot mechanism.
1828 Freescale's SEC block has built-in Blob Protocol which provides
1829 a method for protecting user-defined data across system power
1830 cycles. SEC block protects data in a data structure called a Blob,
1831 which provides both confidentiality and integrity protection.
1833 Encapsulating data as a blob
1834 Each time that the Blob Protocol is used to protect data, a
1835 different randomly generated key is used to encrypt the data.
1836 This random key is itself encrypted using a key which is derived
1837 from SoC's non-volatile secret key and a 16 bit Key identifier.
1838 The resulting encrypted key along with encrypted data is called a
1839 blob. The non-volatile secure key is available for use only during
1842 During decapsulation, the reverse process is performed to get back
1846 blob enc - encapsulating data as a cryptgraphic blob
1847 blob dec - decapsulating cryptgraphic blob to get the data
1851 blob enc src dst len km
1853 Encapsulate and create blob of data $len bytes long
1854 at address $src and store the result at address $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.
1859 blob dec src dst len km
1861 Decapsulate the blob of data at address $src and
1862 store result of $len byte at addr $dst.
1863 $km is the 16 byte key modifier is also required for
1864 generation/use as key for cryptographic operation. Key
1865 modifier should be 16 byte long.
1868 bool "Support 'hash' command"
1871 This provides a way to hash data in memory using various supported
1872 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1873 saved to memory or to an environment variable. It is also possible
1874 to verify a hash against data in memory.
1877 bool "Support the 'hvc' command"
1878 depends on ARM_SMCCC
1880 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1881 development and testing.
1884 bool "Support the 'smc' command"
1885 depends on ARM_SMCCC
1887 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1888 development and testing.
1894 Add -v option to verify data against a hash.
1904 bool "Enable the 'tpm' command"
1905 depends on TPM_V1 || TPM_V2
1906 select CMD_TPM_V1 if TPM_V1
1907 select CMD_TPM_V2 if TPM_V2
1909 This provides a means to talk to a TPM from the command line. A wide
1910 range of commands if provided - see 'tpm help' for details. The
1911 command requires a suitable TPM on your board and the correct driver
1917 bool "Enable the 'tpm test' command"
1920 This provides a a series of tests to confirm that the TPMv1.x is
1921 working correctly. The tests cover initialisation, non-volatile RAM,
1922 extend, global lock and checking that timing is within expectations.
1923 The tests pass correctly on Infineon TPMs but may need to be adjusted
1930 menu "Firmware commands"
1932 bool "Enable crosec command"
1936 Enable command-line access to the Chrome OS EC (Embedded
1937 Controller). This provides the 'crosec' command which has
1938 a number of sub-commands for performing EC tasks such as
1939 updating its flash, accessing a small saved context area
1940 and talking to the I2C bus behind the EC (if there is one).
1943 menu "Filesystem commands"
1945 bool "Enable the 'btrsubvol' command"
1948 This enables the 'btrsubvol' command to list subvolumes
1949 of a BTRFS filesystem. There are no special commands for
1950 listing BTRFS directories or loading BTRFS files - this
1951 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1952 when BTRFS is enabled (see FS_BTRFS).
1955 bool "Enable the 'cbfs' command"
1958 Define this to enable support for reading from a Coreboot
1959 filesystem. This is a ROM-based filesystem used for accessing files
1960 on systems that use coreboot as the first boot-loader and then load
1961 U-Boot to actually boot the Operating System. Available commands are
1962 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1965 bool "Enable the 'cramfs' command"
1966 depends on FS_CRAMFS
1968 This provides commands for dealing with CRAMFS (Compressed ROM
1969 filesystem). CRAMFS is useful when space is tight since files are
1970 compressed. Two commands are provided:
1972 cramfsls - lists files in a cramfs image
1973 cramfsload - loads a file from a cramfs image
1976 bool "ext2 command support"
1979 Enables EXT2 FS command
1982 bool "ext4 command support"
1985 Enables EXT4 FS command
1987 config CMD_EXT4_WRITE
1989 bool "ext4 write command support"
1992 Enables EXT4 FS write command
1995 bool "FAT command support"
1998 Support for the FAT fs
2000 config CMD_FS_GENERIC
2001 bool "filesystem commands"
2003 Enables filesystem commands (e.g. load, ls) that work for multiple
2007 bool "fsuuid command"
2009 Enables fsuuid command for filesystem UUID.
2012 bool "jffs2 command"
2015 Enables commands to support the JFFS2 (Journalling Flash File System
2016 version 2) filesystem. This enables fsload, ls and fsinfo which
2017 provide the ability to load files, list directories and obtain
2018 filesystem information.
2021 bool "MTD partition support"
2024 MTD partitioning tool support.
2025 It is strongly encouraged to avoid using this command
2026 anymore along with 'sf', 'nand', 'onenand'. One can still
2027 declare the partitions in the mtdparts environment variable
2028 but better use the MTD stack and the 'mtd' command instead.
2030 config CMD_MTDPARTS_SPREAD
2031 bool "Padd partition size to take account of bad blocks"
2032 depends on CMD_MTDPARTS
2034 This enables the 'spread' sub-command of the mtdparts command.
2035 This command will modify the existing mtdparts variable by increasing
2036 the size of the partitions such that 1) each partition's net size is
2037 at least as large as the size specified in the mtdparts variable and
2038 2) each partition starts on a good block.
2040 config CMD_MTDPARTS_SHOW_NET_SIZES
2041 bool "Show net size (w/o bad blocks) of partitions"
2042 depends on CMD_MTDPARTS
2044 Adds two columns to the printed partition table showing the
2045 effective usable size of a partition, if bad blocks are taken
2048 config MTDIDS_DEFAULT
2049 string "Default MTD IDs"
2050 depends on MTD || SPI_FLASH
2052 Defines a default MTD IDs list for use with MTD partitions in the
2053 Linux MTD command line partitions format.
2055 config MTDPARTS_DEFAULT
2056 string "Default MTD partition scheme"
2057 depends on MTD || SPI_FLASH
2059 Defines a default MTD partitioning scheme in the Linux MTD command
2060 line partitions format
2063 bool "reiser - Access to reiserfs filesystems"
2065 This provides two commands which operate on a resierfs filesystem,
2066 commonly used some years ago:
2068 reiserls - list files
2069 reiserload - load a file
2072 bool "yaffs2 - Access of YAFFS2 filesystem"
2076 This provides commands for accessing a YAFFS2 filesystem. Yet
2077 Another Flash Filesystem 2 is a filesystem designed specifically
2078 for NAND flash. It incorporates bad-block management and ensures
2079 that device writes are sequential regardless of filesystem
2083 bool "zfs - Access of ZFS filesystem"
2085 This provides commands to accessing a ZFS filesystem, commonly used
2086 on Solaris systems. Two sub-commands are provided:
2088 zfsls - list files in a directory
2089 zfsload - load a file
2091 See doc/README.zfs for more details.
2095 menu "Debug commands"
2100 The bedbug (emBEDded deBUGger) command provides debugging features
2101 for some PowerPC processors. For details please see the
2102 docuemntation in doc/README.beddbug
2105 bool "diag - Board diagnostics"
2107 This command provides access to board diagnostic tests. These are
2108 called Power-on Self Tests (POST). The command allows listing of
2109 available tests and running either all the tests, or specific tests
2113 bool "irq - Show information about interrupts"
2114 depends on !ARM && !MIPS && !SH
2116 This enables two commands:
2118 interrupts - enable or disable interrupts
2119 irqinfo - print device-specific interrupt information
2122 bool "kgdb - Allow debugging of U-Boot with gdb"
2125 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2126 over a serial link for debugging purposes. This allows
2127 single-stepping, inspecting variables, etc. This is supported only
2128 on PowerPC at present.
2131 bool "log - Generation, control and access to logging"
2134 This provides access to logging features. It allows the output of
2135 log data to be controlled to a limited extent (setting up the default
2136 maximum log level for emitting of records). It also provides access
2137 to a command used for testing the log system.
2140 bool "trace - Support tracing of function calls and timing"
2142 Enables a command to control using of function tracing within
2143 U-Boot. This allows recording of call traces including timing
2144 information. The command can write data to memory for exporting
2145 for analysis (e.g. using bootchart). See doc/README.trace for full
2149 bool "avb - Android Verified Boot 2.0 operations"
2150 depends on AVB_VERIFY
2153 Enables a "avb" command to perform verification of partitions using
2154 Android Verified Boot 2.0 functionality. It includes such subcommands:
2155 avb init - initialize avb2 subsystem
2156 avb read_rb - read rollback index
2157 avb write_rb - write rollback index
2158 avb is_unlocked - check device lock state
2159 avb get_uuid - read and print uuid of a partition
2160 avb read_part - read data from partition
2161 avb read_part_hex - read data from partition and output to stdout
2162 avb write_part - write data to partition
2163 avb verify - run full verification chain
2167 tristate "Enable UBI - Unsorted block images commands"
2170 UBI is a software layer above MTD layer which admits use of LVM-like
2171 logical volumes on top of MTD devices, hides some complexities of
2172 flash chips like wear and bad blocks and provides some other useful
2173 capabilities. Please, consult the MTD web site for more details
2174 (www.linux-mtd.infradead.org). Activate this option if you want
2175 to use U-Boot UBI commands.
2176 It is also strongly encouraged to also enable CONFIG_MTD to get full
2180 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2182 default y if CMD_UBI
2185 UBIFS is a file system for flash devices which works on top of UBI.