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.
397 See doc/android/boot-image.rst for details.
400 bool "bootelf, bootvx"
404 Boot an ELF/vxWorks image from the memory.
407 bool "Flattened Device Tree utility commands"
411 Do FDT related setup before booting into the Operating System.
417 Start an application at a given address.
423 Run the command in the given environment variable.
429 Print header information for application image.
434 List all images found in flash
440 Extract a part of a multi-image.
443 bool "spl export - Export boot information for Falcon boot"
446 Falcon mode allows booting directly from SPL into an Operating
447 System such as Linux, thus skipping U-Boot proper. See
448 doc/README.falcon for full information about how to use this
451 config CMD_SPL_NAND_OFS
452 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
453 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
456 This provides the offset of the command line arguments for Linux
457 when booting from NAND in Falcon mode. See doc/README.falcon
458 for full information about how to use this option (and also see
459 board/gateworks/gw_ventana/README for an example).
461 config CMD_SPL_NOR_OFS
462 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
463 depends on CMD_SPL && SPL_NOR_SUPPORT
466 This provides the offset of the command line arguments or dtb for
467 Linux when booting from NOR in Falcon mode.
469 config CMD_SPL_WRITE_SIZE
470 hex "Size of argument area"
474 This provides the size of the command-line argument area in NAND
475 flash used by Falcon-mode boot. See the documentation until CMD_SPL
479 bool "fitImage update command"
481 Implements the 'fitupd' command, which allows to automatically
482 store software updates present on a TFTP server in NOR Flash
484 config CMD_THOR_DOWNLOAD
485 bool "thor - TIZEN 'thor' download"
488 Implements the 'thor' download protocol. This is a way of
489 downloading a software update over USB from an attached host.
490 There is no documentation about this within the U-Boot source code
491 but you should be able to find something on the interwebs.
494 bool "zboot - x86 boot command"
496 With x86 machines it is common to boot a bzImage file which
497 contains both a kernel and a setup.bin file. The latter includes
498 configuration information from the dark ages which x86 boards still
499 need to pick things out of.
501 Consider using FIT in preference to this since it supports directly
502 booting both 32- and 64-bit kernels, as well as secure boot.
503 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
507 menu "Environment commands"
510 bool "ask for env variable"
512 Ask for environment variable
530 Edit environment variable.
535 Allow for searching environment variables
541 Save all environment variables into the compiled-in persistent
547 depends on CMD_SAVEENV
549 Erase environment variables from the compiled-in persistent
552 config CMD_ENV_EXISTS
556 Check if a variable is defined in the environment for use in
559 config CMD_ENV_CALLBACK
560 bool "env callbacks - print callbacks and their associated variables"
562 Some environment variable have callbacks defined by
563 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
564 For example changing "baudrate" adjust the serial baud rate. This
565 command lists the currently defined callbacks.
568 bool "env flags -print variables that have non-default flags"
570 Some environment variables have special flags that control their
571 behaviour. For example, serial# can only be written once and cannot
572 be deleted. This command shows the variables that have special
575 config CMD_NVEDIT_EFI
576 bool "env [set|print] -e - set/print UEFI variables"
577 depends on EFI_LOADER
580 UEFI variables are encoded as some form of U-Boot variables.
581 If enabled, we are allowed to set/print UEFI variables using
582 "env" command with "-e" option without knowing details.
584 config CMD_NVEDIT_INFO
585 bool "env info - print or evaluate environment information"
587 Print environment information:
588 - env_valid : is environment valid
589 - env_ready : is environment imported into hash table
590 - env_use_default : is default environment used
592 This command can be optionally used for evaluation in scripts:
593 [-d] : evaluate whether default environment is used
594 [-p] : evaluate whether environment can be persisted
595 The result of multiple evaluations will be combined with AND.
599 menu "Memory commands"
604 Compute binary operations (xor, or, and) of byte arrays of arbitrary
605 size from memory and store the result in memory or the environment.
618 Add -v option to verify data against a crc32 checksum.
621 bool "eeprom - EEPROM subsystem"
623 (deprecated, needs conversion to driver model)
624 Provides commands to read and write EEPROM (Electrically Erasable
625 Programmable Read Only Memory) chips that are connected over an
628 config CMD_EEPROM_LAYOUT
629 bool "Enable layout-aware eeprom commands"
630 depends on CMD_EEPROM
632 (deprecated, needs conversion to driver model)
633 When enabled, additional eeprom sub-commands become available.
635 eeprom print - prints the contents of the eeprom in a human-readable
636 way (eeprom layout fields, and data formatted to be fit for human
639 eeprom update - allows user to update eeprom fields by specifying
640 the field name, and providing the new data in a human readable format
641 (same format as displayed by the eeprom print command).
643 Both commands can either auto detect the layout, or be told which
647 __weak int parse_layout_version(char *str)
648 - override to provide your own layout name parsing
649 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
651 - override to setup the layout metadata based on the version
652 __weak int eeprom_layout_detect(unsigned char *data)
653 - override to provide your own algorithm for detecting layout
656 - contains various printing and updating functions for common
657 types of eeprom fields. Can be used for defining
660 config EEPROM_LAYOUT_HELP_STRING
661 string "Tells user what layout names are supported"
662 depends on CMD_EEPROM_LAYOUT
663 default "<not defined>"
665 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
671 Infinite write loop on address range
678 Compute MD5 checksum.
683 depends on CMD_MD5SUM
685 Add -v option to verify data against an MD5 checksum.
690 Display memory information.
693 bool "md, mm, nm, mw, cp, cmp, base, loop"
698 mm - memory modify (auto-incrementing address)
699 nm - memory modify (constant address)
700 mw - memory write (fill)
703 base - print or set address offset
704 loop - initialize loop on address range
707 bool "Enable cyclic md/mw commands"
708 depends on CMD_MEMORY
710 Add the "mdc" and "mwc" memory commands. These are cyclic
715 This command will print 4 bytes (10,11,12,13) each 500 ms.
717 => mwc.l 100 12345678 10
718 This command will write 12345678 to address 100 all 10 ms.
723 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
725 random - fill memory with random data
730 Simple RAM read/write test.
734 config SYS_ALT_MEMTEST
735 bool "Alternative test"
737 Use a more complete alternative memory test.
745 Compute SHA1 checksum.
747 config SHA1SUM_VERIFY
749 depends on CMD_SHA1SUM
751 Add -v option to verify data against a SHA1 checksum.
754 bool "strings - display strings in memory"
756 This works similarly to the Unix 'strings' command except that it
757 works with a memory range. String of printable characters found
758 within the range are displayed. The minimum number of characters
759 for a sequence to be considered a string can be provided.
763 menu "Compression commands"
767 default y if CMD_BOOTI
770 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
775 default y if CMD_BOOTI
777 Uncompress a zip-compressed memory region.
782 Compress a memory region with zlib deflate method.
786 menu "Device access commands"
789 #depends on FLASH_CFI_DRIVER
792 ARM Ltd reference designs flash partition access
795 bool "adc - Access Analog to Digital Converters info and data"
799 Shows ADC device info and permit printing one-shot analog converted
800 data from a named Analog to Digital Converter.
805 depends on PARTITIONS
807 Read/modify/write the fields of Bootloader Control Block, usually
808 stored on the flash "misc" partition with its structure defined in:
809 https://android.googlesource.com/platform/bootable/recovery/+/master/
810 bootloader_message/include/bootloader_message/bootloader_message.h
812 Some real-life use-cases include (but are not limited to):
813 - Determine the "boot reason" (and act accordingly):
814 https://source.android.com/devices/bootloader/boot-reason
815 - Get/pass a list of commands from/to recovery:
816 https://android.googlesource.com/platform/bootable/recovery
817 - Inspect/dump the contents of the BCB fields
820 bool "bind/unbind - Bind or unbind a device to/from a driver"
823 Bind or unbind a device to/from a driver from the command line.
824 This is useful in situations where a device may be handled by several
825 drivers. For example, this can be used to bind a UDC to the usb ether
826 gadget driver from the command line.
829 bool "clk - Show clock frequencies"
832 Shows clock frequences by calling a sock_clk_dump() hook function.
833 This is depreated in favour of using the CLK uclass and accessing
834 clock values from associated drivers. However currently no command
838 bool "demo - Demonstration commands for driver model"
841 Provides a 'demo' command which can be used to play around with
842 driver model. To use this properly you will need to enable one or
843 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
844 Otherwise you will always get an empty list of devices. The demo
845 devices are defined in the sandbox device tree, so the easiest
846 option is to use sandbox and pass the -d point to sandbox's
853 Enables the command "dfu" which is used to have U-Boot create a DFU
854 class device via USB. This command requires that the "dfu_alt_info"
855 environment variable be set and define the alt settings to expose to
859 bool "dm - Access to driver model information"
862 Provides access to driver model data structures and information,
863 such as a list of devices, list of uclasses and the state of each
864 device (e.g. activated). This is not required for operation, but
865 can be useful to see the state of driver model for debugging or
869 bool "fastboot - Android fastboot support"
872 This enables the command "fastboot" which enables the Android
873 fastboot mode for the platform. Fastboot is a protocol for
874 downloading images, flashing and device control used on
875 Android devices. Fastboot requires either the network stack
876 enabled or support for acting as a USB device.
878 See doc/android/fastboot.rst for more information.
881 bool "flinfo, erase, protect"
883 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
886 flinfo - print FLASH memory information
888 protect - enable or disable FLASH write protection
897 config CMD_FPGA_LOADBP
898 bool "fpga loadbp - load partial bitstream (Xilinx only)"
901 Supports loading an FPGA device from a bitstream buffer containing
904 config CMD_FPGA_LOADFS
905 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
908 Supports loading an FPGA device from a FAT filesystem.
910 config CMD_FPGA_LOADMK
911 bool "fpga loadmk - load bitstream from image"
914 Supports loading an FPGA device from a image generated by mkimage.
916 config CMD_FPGA_LOADP
917 bool "fpga loadp - load partial bitstream"
920 Supports loading an FPGA device from a bitstream buffer containing
923 config CMD_FPGA_LOAD_SECURE
924 bool "fpga loads - loads secure bitstreams (Xilinx only)"
927 Enables the fpga loads command which is used to load secure
928 (authenticated or encrypted or both) bitstreams on to FPGA.
931 bool "fpgad - dump FPGA registers"
933 (legacy, needs conversion to driver model)
934 Provides a way to dump FPGA registers by calling the board-specific
935 fpga_get_reg() function. This functions similarly to the 'md'
939 bool "fuse - support for the fuse subssystem"
941 (deprecated - needs conversion to driver model)
942 This allows reading, sensing, programming or overriding fuses
943 which control the behaviour of the device. The command uses the
952 bool "GPT (GUID Partition Table) command"
954 select HAVE_BLOCK_DEVICE
955 select PARTITION_UUIDS
958 Enable the 'gpt' command to ready and write GPT style partition
962 bool "GPT Random UUID generation"
965 Enable the generation of partitions with random UUIDs if none
968 config CMD_GPT_RENAME
969 bool "GPT partition renaming commands"
972 Enables the 'gpt' command to interchange names on two GPT
973 partitions via the 'gpt swap' command or to rename single
974 partitions via the 'rename' command.
977 bool "ide - Support for IDE drivers"
980 Provides an 'ide' command which allows accessing the IDE drive,
981 reseting the IDE interface, printing the partition table and
982 geting device info. It also enables the 'diskboot' command which
983 permits booting from an IDE drive.
986 bool "io - Support for performing I/O accesses"
988 Provides an 'iod' command to display I/O space and an 'iow' command
989 to write values to the I/O space. This can be useful for manually
990 checking the state of devices during boot when debugging device
994 bool "iotrace - Support for tracing I/O activity"
996 Provides an 'iotrace' command which supports recording I/O reads and
997 writes in a trace buffer in memory . It also maintains a checksum
998 of the trace records (even if space is exhausted) so that the
999 sequence of I/O accesses can be verified.
1001 When debugging drivers it is useful to see what I/O accesses were
1002 done and in what order.
1004 Even if the individual accesses are of little interest it can be
1005 useful to verify that the access pattern is consistent each time
1006 an operation is performed. In this case a checksum can be used to
1007 characterise the operation of a driver. The checksum can be compared
1008 across different runs of the operation to verify that the driver is
1011 In particular, when performing major refactoring of the driver, where
1012 the access pattern should not change, the checksum provides assurance
1013 that the refactoring work has not broken the driver.
1015 This works by sneaking into the io.h heder for an architecture and
1016 redirecting I/O accesses through iotrace's tracing mechanism.
1018 For now no commands are provided to examine the trace buffer. The
1019 format is fairly simple, so 'md' is a reasonable substitute.
1021 Note: The checksum feature is only useful for I/O regions where the
1022 contents do not change outside of software control. Where this is not
1023 suitable you can fall back to manually comparing the addresses. It
1024 might be useful to enhance tracing to only checksum the accesses and
1025 not the data read/written.
1035 bool "w1 - Support for Dallas 1-Wire protocol"
1037 Dallas 1-wire protocol support
1043 Load a binary file over serial line.
1049 Load an S-Record file over serial line
1054 MMC memory mapped support.
1057 bool "Enable support for RPMB in the mmc command"
1060 Enable the commands for reading, writing and programming the
1061 key for the Replay Protection Memory Block partition in eMMC.
1063 config CMD_MMC_SWRITE
1065 depends on CMD_MMC && MMC_WRITE
1068 Enable support for the "mmc swrite" command to write Android sparse
1074 select MTD_PARTITIONS
1076 MTD commands support.
1080 default y if NAND_SUNXI
1081 depends on MTD_RAW_NAND
1086 config CMD_NAND_TRIMFFS
1087 bool "nand write.trimffs"
1088 default y if ARCH_SUNXI
1090 Allows one to skip empty pages when flashing something on a NAND.
1092 config CMD_NAND_LOCK_UNLOCK
1093 bool "nand lock/unlock"
1095 NAND locking support.
1097 config CMD_NAND_TORTURE
1100 NAND torture support.
1109 NVM Express device support
1112 bool "onenand - access to onenand device"
1115 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1116 various useful features. This command allows reading, writing,
1117 and erasing blocks. It allso provides a way to show and change
1118 bad blocks, and test the device.
1123 Enable the 'osd' command which allows to query information from and
1124 write text data to a on-screen display (OSD) device; a virtual device
1125 associated with a display capable of displaying a text overlay on the
1126 display it's associated with..
1130 select HAVE_BLOCK_DEVICE
1131 select PARTITION_UUIDS
1133 Read and display information about the partition table on
1137 bool "pci - Access PCI devices"
1139 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1140 used on some devices to allow the CPU to communicate with its
1141 peripherals. Sub-commands allow bus enumeration, displaying and
1142 changing configuration space and a few other features.
1145 bool "pinmux - show pins muxing"
1146 default y if PINCTRL
1148 Parse all available pin-controllers and show pins muxing. This
1149 is useful for debug purpoer to check the pin muxing and to know if
1150 a pin is configured as a GPIO or as an alternate function.
1155 Poweroff/Shutdown the system
1158 bool "read - Read binary data from a partition"
1160 Provides low-level access to the data in a partition.
1162 config CMD_REMOTEPROC
1164 depends on REMOTEPROC
1166 Support for Remote Processor control
1169 bool "sata - Access SATA subsystem"
1172 SATA (Serial Advanced Technology Attachment) is a serial bus
1173 standard for connecting to hard drives and other storage devices.
1174 This command provides information about attached devices and allows
1175 reading, writing and other operations.
1177 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1178 Attachment, where AT refers to an IBM AT (Advanced Technology)
1179 computer released in 1984.
1182 bool "saves - Save a file over serial in S-Record format"
1184 Provides a way to save a binary file using the Motorola S-Record
1185 format over the serial line.
1188 bool "scsi - Access to SCSI devices"
1191 This provides a 'scsi' command which provides access to SCSI (Small
1192 Computer System Interface) devices. The command provides a way to
1193 scan the bus, reset the bus, read and write data and get information
1197 bool "sdram - Print SDRAM configuration information"
1199 Provides information about attached SDRAM. This assumed that the
1200 SDRAM has an EEPROM with information that can be read using the
1201 I2C bus. This is only available on some boards.
1205 depends on DM_SPI_FLASH || SPI_FLASH
1206 default y if DM_SPI_FLASH
1211 bool "sf test - Allow testing of SPI flash"
1214 Provides a way to test that SPI flash is working correctly. The
1215 test is destructive, in that an area of SPI flash must be provided
1216 for the test to use. Performance information is also provided,
1217 measuring the performance of reading, writing and erasing in
1218 Mbps (Million Bits Per Second). This value should approximately
1219 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1220 everything is working properly.
1223 bool "sspi - Command to access spi device"
1226 SPI utility command.
1228 config DEFAULT_SPI_BUS
1229 int "default spi bus used by sspi command"
1233 config DEFAULT_SPI_MODE
1234 hex "default spi mode used by sspi command (see include/spi.h)"
1239 bool "tsi148 - Command to access tsi148 device"
1241 This provides various sub-commands to initialise and configure the
1242 Turndra tsi148 device. See the command help for full details.
1245 bool "Enable UFS - Universal Flash Subsystem commands"
1248 "This provides commands to initialise and configure universal flash
1252 bool "universe - Command to set up the Turndra Universe controller"
1254 This allows setting up the VMEbus provided by this controller.
1255 See the command help for full details.
1259 select HAVE_BLOCK_DEVICE
1265 select USB_FUNCTION_SDP
1267 Enables the command "sdp" which is used to have U-Boot emulating the
1268 Serial Download Protocol (SDP) via USB.
1272 depends on USB_FUNCTION_ROCKUSB
1274 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1275 read/write info, image to/from devices. This enable rockusb command
1276 support to communication with rockusb device. for more detail about
1277 this command, please read doc/README.rockusb.
1279 config CMD_USB_MASS_STORAGE
1280 bool "UMS usb mass storage"
1281 select USB_FUNCTION_MASS_STORAGE
1283 USB mass storage support
1290 VirtIO block device support
1296 This provides commands to control the watchdog timer devices.
1302 Enable the command "axi" for accessing AXI (Advanced eXtensible
1303 Interface) busses, a on-chip interconnect specification for managing
1304 functional blocks in SoC designs, which is also often used in designs
1305 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1309 menu "Shell scripting commands"
1315 Echo args to console
1321 Return true/false on integer compare.
1327 Run script from memory
1333 Evaluate boolean and math expressions and store the result in an env
1335 Also supports loading the value at a memory location into a variable.
1336 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1340 menu "Android support commands"
1342 config CMD_AB_SELECT
1345 depends on ANDROID_AB
1347 On Android devices with more than one boot slot (multiple copies of
1348 the kernel and system images) this provides a command to select which
1349 slot should be used to boot from and register the boot attempt. This
1350 is used by the new A/B update model where one slot is updated in the
1351 background while running from the other slot.
1358 bool "Network commands"
1368 bootp - boot image via network using BOOTP/TFTP protocol
1372 depends on CMD_BOOTP
1374 Boot image via network using DHCP/TFTP protocol
1376 config BOOTP_BOOTPATH
1377 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1379 depends on CMD_BOOTP
1381 Even though the config is called BOOTP_BOOTPATH, it stores the
1382 path in the variable 'rootpath'.
1385 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1387 depends on CMD_BOOTP
1389 The primary DNS server is stored as 'dnsip'. If two servers are
1390 returned, you must set BOOTP_DNS2 to store that second server IP
1394 bool "Store 'dnsip2' from BOOTP/DHCP server"
1395 depends on BOOTP_DNS
1397 If a DHCP client requests the DNS server IP from a DHCP server,
1398 it is possible that more than one DNS serverip is offered to the
1399 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1400 server IP will be stored in the additional environment
1401 variable "dnsip2". The first DNS serverip is always
1402 stored in the variable "dnsip", when BOOTP_DNS is defined.
1404 config BOOTP_GATEWAY
1405 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1407 depends on CMD_BOOTP
1409 config BOOTP_HOSTNAME
1410 bool "Request & store 'hostname' from BOOTP/DHCP server"
1412 depends on CMD_BOOTP
1414 The name may or may not be qualified with the local domain name.
1416 config BOOTP_PREFER_SERVERIP
1417 bool "serverip variable takes precedent over DHCP server IP."
1418 depends on CMD_BOOTP
1420 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1422 With this option enabled, the 'serverip' variable in the environment
1423 takes precedence over DHCP server IP and will only be set by the DHCP
1424 server if not already set in the environment.
1426 config BOOTP_SUBNETMASK
1427 bool "Request & store 'netmask' from BOOTP/DHCP server"
1429 depends on CMD_BOOTP
1431 config BOOTP_NTPSERVER
1432 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1433 depends on CMD_BOOTP
1438 Selecting this will allow capturing all Ethernet packets and store
1439 them in physical memory in a PCAP formated file,
1440 later to be analyzed by PCAP reader application (IE. WireShark).
1443 bool "Send PXE client arch to BOOTP/DHCP server"
1445 depends on CMD_BOOTP && CMD_PXE
1447 Supported for ARM, ARM64, and x86 for now.
1449 config BOOTP_PXE_CLIENTARCH
1451 depends on BOOTP_PXE
1452 default 0x16 if ARM64
1456 config BOOTP_VCI_STRING
1458 depends on CMD_BOOTP
1459 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1460 default "U-Boot.armv8" if ARM64
1461 default "U-Boot.arm" if ARM
1468 tftpboot - boot image via network using TFTP protocol
1472 depends on CMD_TFTPBOOT
1474 TFTP put command, for uploading files to a server
1478 depends on CMD_TFTPBOOT
1480 Act as a TFTP server and boot the first received file
1482 config NET_TFTP_VARS
1483 bool "Control TFTP timeout and count through environment"
1484 depends on CMD_TFTPBOOT
1487 If set, allows controlling the TFTP timeout through the
1488 environment variable tftptimeout, and the TFTP maximum
1489 timeout count through the variable tftptimeoutcountmax.
1490 If unset, timeout and maximum are hard-defined as 1 second
1491 and 10 timouts per TFTP transfer.
1496 Boot image via network using RARP/TFTP protocol
1502 Boot image via network using NFS protocol.
1508 If set, allows 802.3(clause 22) MII Management functions interface access
1509 The management interface specified in Clause 22 provides
1510 a simple, two signal, serial interface to connect a
1511 Station Management entity and a managed PHY for providing access
1512 to management parameters and services.
1513 The interface is referred to as the MII management interface.
1519 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1520 The MDIO interface is orthogonal to the MII interface and extends
1521 it by adding access to more registers through indirect addressing.
1526 Send ICMP ECHO_REQUEST to network host
1531 Perform CDP network configuration
1536 Synchronize RTC via network
1541 Lookup the IP of a hostname
1543 config CMD_LINK_LOCAL
1547 Acquire a network IP address using the link-local protocol
1554 Allow control of L2 Ethernet switch commands. These are supported
1555 by the vsc9953 Ethernet driver at present. Sub-commands allow
1556 operations such as enabling / disabling a port and
1557 viewing/maintaining the filtering database (FDB)
1563 Boot image via network using PXE protocol
1568 Wait for wake-on-lan Magic Packet
1572 menu "Misc commands"
1575 bool "Enable 'bmp' command"
1576 depends on LCD || DM_VIDEO || VIDEO
1578 This provides a way to obtain information about a BMP-format image
1579 and to display it. BMP (which presumably stands for BitMaP) is a
1580 file format defined by Microsoft which supports images of various
1581 depths, formats and compression methods. Headers on the file
1582 determine the formats used. This command can be used by first loading
1583 the image into RAM, then using this command to look at it or display
1586 config CMD_BOOTCOUNT
1588 depends on BOOTCOUNT_LIMIT
1590 Enable the bootcount command, which allows interrogation and
1591 reset of the bootcounter.
1594 bool "Enable board-specific commands"
1596 (deprecated: instead, please define a Kconfig option for each command)
1598 Some boards have board-specific commands which are only enabled
1599 during developemnt and need to be turned off for production. This
1600 option provides a way to control this. The commands that are enabled
1601 vary depending on the board.
1603 config CMD_BKOPS_ENABLE
1604 bool "mmc bkops enable"
1608 Enable command for setting manual background operations handshake
1609 on a eMMC device. The feature is optionally available on eMMC devices
1610 conforming to standard >= 4.41.
1612 config CMD_BLOCK_CACHE
1613 bool "blkcache - control and stats for block cache"
1614 depends on BLOCK_CACHE
1615 default y if BLOCK_CACHE
1617 Enable the blkcache command, which can be used to control the
1618 operation of the cache functions.
1619 This is most useful when fine-tuning the operation of the cache
1620 during development, but also allows the cache to be disabled when
1621 it might hurt performance (e.g. when using the ums command).
1624 bool "icache or dcache"
1626 Enable the "icache" and "dcache" commands
1628 config CMD_CONITRACE
1629 bool "conitrace - trace console input codes"
1631 Enable the 'conitrace' command which displays the codes received
1632 from the console input as hexadecimal numbers.
1635 bool "Enable clear screen command 'cls'"
1636 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1639 Enable the 'cls' command which clears the screen contents
1640 on video frame buffer.
1643 bool "efidebug - display/configure UEFI environment"
1644 depends on EFI_LOADER
1645 select EFI_DEVICE_PATH_TO_TEXT
1648 Enable the 'efidebug' command which provides a subset of UEFI
1649 shell utility with simplified functionality. It will be useful
1650 particularly for managing boot parameters as well as examining
1651 various EFI status for debugging.
1653 config CMD_EXCEPTION
1654 bool "exception - raise exception"
1655 depends on ARM || RISCV || X86
1657 Enable the 'exception' command which allows to raise an exception.
1664 Enable the 'led' command which allows for control of LEDs supported
1665 by the board. The LEDs can be listed with 'led list' and controlled
1666 with led on/off/togle/blink. Any LED drivers can be controlled with
1667 this command, e.g. led_gpio.
1674 Enable the 'date' command for getting/setting the time/date in RTC
1680 Run commands and summarize execution time.
1683 bool "gettime - read elapsed time"
1685 Enable the 'gettime' command which reads the elapsed time since
1686 U-Boot started running. This shows the time in seconds and
1687 milliseconds. See also the 'bootstage' command which provides more
1688 flexibility for boot timing.
1695 Print bytes from the hardware random number generator.
1697 # TODO: rename to CMD_SLEEP
1702 Delay execution for some time
1705 bool "support for multiprocessor"
1707 This provides an option to brinup
1708 different processors in multiprocessor
1714 Access the system timer.
1720 This provides basic access to the U-Boot's sound support. The main
1721 feature is to play a beep.
1723 sound init - set up sound system
1724 sound play - play a sound
1730 Boot image via local extlinux.conf file
1736 This provides access to the QEMU firmware interface. The main
1737 feature is to allow easy loading of files passed to qemu-system
1738 via -kernel / -initrd
1740 source "cmd/mvebu/Kconfig"
1743 bool "terminal - provides a way to attach a serial terminal"
1745 Provides a 'cu'-like serial terminal command. This can be used to
1746 access other serial ports from the system console. The terminal
1747 is very simple with no special processing of characters. As with
1748 cu, you can press ~. (tilde followed by period) to exit.
1751 bool "uuid, guid - generation of unique IDs"
1754 This enables two commands:
1756 uuid - generate random Universally Unique Identifier
1757 guid - generate Globally Unique Identifier based on random UUID
1759 The two commands are very similar except for the endianness of the
1764 source "cmd/ti/Kconfig"
1766 config CMD_BOOTSTAGE
1767 bool "Enable the 'bootstage' command"
1768 depends on BOOTSTAGE
1770 Add a 'bootstage' command which supports printing a report
1771 and un/stashing of bootstage data.
1773 menu "Power commands"
1775 bool "Enable Driver Model PMIC command"
1778 This is the pmic command, based on a driver model pmic's API.
1779 Command features are unchanged:
1780 - list - list pmic devices
1781 - pmic dev <id> - show or [set] operating pmic device (NEW)
1782 - pmic dump - dump registers
1783 - pmic read address - read byte of register at address
1784 - pmic write address - write byte to register at address
1785 The only one change for this command is 'dev' subcommand.
1787 config CMD_REGULATOR
1788 bool "Enable Driver Model REGULATOR command"
1789 depends on DM_REGULATOR
1791 This command is based on driver model regulator's API.
1792 User interface features:
1793 - list - list regulator devices
1794 - regulator dev <id> - show or [set] operating regulator device
1795 - regulator info - print constraints info
1796 - regulator status - print operating status
1797 - regulator value <val] <-f> - print/[set] voltage value [uV]
1798 - regulator current <val> - print/[set] current value [uA]
1799 - regulator mode <id> - print/[set] operating mode id
1800 - regulator enable - enable the regulator output
1801 - regulator disable - disable the regulator output
1803 The '-f' (force) option can be used for set the value which exceeds
1804 the limits, which are found in device-tree and are kept in regulator's
1805 uclass platdata structure.
1809 menu "Security commands"
1811 bool "Enable the 'aes' command"
1814 This provides a means to encrypt and decrypt data using the AES
1815 (Advanced Encryption Standard). This algorithm uses a symetric key
1816 and is widely used as a streaming cipher. Different key lengths are
1817 supported by the algorithm but this command only supports 128 bits
1821 bool "Enable the 'blob' command"
1823 This is used with the Freescale secure boot mechanism.
1825 Freescale's SEC block has built-in Blob Protocol which provides
1826 a method for protecting user-defined data across system power
1827 cycles. SEC block protects data in a data structure called a Blob,
1828 which provides both confidentiality and integrity protection.
1830 Encapsulating data as a blob
1831 Each time that the Blob Protocol is used to protect data, a
1832 different randomly generated key is used to encrypt the data.
1833 This random key is itself encrypted using a key which is derived
1834 from SoC's non-volatile secret key and a 16 bit Key identifier.
1835 The resulting encrypted key along with encrypted data is called a
1836 blob. The non-volatile secure key is available for use only during
1839 During decapsulation, the reverse process is performed to get back
1843 blob enc - encapsulating data as a cryptgraphic blob
1844 blob dec - decapsulating cryptgraphic blob to get the data
1848 blob enc src dst len km
1850 Encapsulate and create blob of data $len bytes long
1851 at address $src and store the result at address $dst.
1852 $km is the 16 byte key modifier is also required for
1853 generation/use as key for cryptographic operation. Key
1854 modifier should be 16 byte long.
1856 blob dec src dst len km
1858 Decapsulate the blob of data at address $src and
1859 store result of $len byte at addr $dst.
1860 $km is the 16 byte key modifier is also required for
1861 generation/use as key for cryptographic operation. Key
1862 modifier should be 16 byte long.
1865 bool "Support 'hash' command"
1868 This provides a way to hash data in memory using various supported
1869 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1870 saved to memory or to an environment variable. It is also possible
1871 to verify a hash against data in memory.
1874 bool "Support the 'hvc' command"
1875 depends on ARM_SMCCC
1877 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1878 development and testing.
1881 bool "Support the 'smc' command"
1882 depends on ARM_SMCCC
1884 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1885 development and testing.
1891 Add -v option to verify data against a hash.
1901 bool "Enable the 'tpm' command"
1902 depends on TPM_V1 || TPM_V2
1903 select CMD_TPM_V1 if TPM_V1
1904 select CMD_TPM_V2 if TPM_V2
1906 This provides a means to talk to a TPM from the command line. A wide
1907 range of commands if provided - see 'tpm help' for details. The
1908 command requires a suitable TPM on your board and the correct driver
1914 bool "Enable the 'tpm test' command"
1917 This provides a a series of tests to confirm that the TPMv1.x is
1918 working correctly. The tests cover initialisation, non-volatile RAM,
1919 extend, global lock and checking that timing is within expectations.
1920 The tests pass correctly on Infineon TPMs but may need to be adjusted
1927 menu "Firmware commands"
1929 bool "Enable crosec command"
1933 Enable command-line access to the Chrome OS EC (Embedded
1934 Controller). This provides the 'crosec' command which has
1935 a number of sub-commands for performing EC tasks such as
1936 updating its flash, accessing a small saved context area
1937 and talking to the I2C bus behind the EC (if there is one).
1940 menu "Filesystem commands"
1942 bool "Enable the 'btrsubvol' command"
1945 This enables the 'btrsubvol' command to list subvolumes
1946 of a BTRFS filesystem. There are no special commands for
1947 listing BTRFS directories or loading BTRFS files - this
1948 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1949 when BTRFS is enabled (see FS_BTRFS).
1952 bool "Enable the 'cbfs' command"
1955 Define this to enable support for reading from a Coreboot
1956 filesystem. This is a ROM-based filesystem used for accessing files
1957 on systems that use coreboot as the first boot-loader and then load
1958 U-Boot to actually boot the Operating System. Available commands are
1959 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1962 bool "Enable the 'cramfs' command"
1963 depends on FS_CRAMFS
1965 This provides commands for dealing with CRAMFS (Compressed ROM
1966 filesystem). CRAMFS is useful when space is tight since files are
1967 compressed. Two commands are provided:
1969 cramfsls - lists files in a cramfs image
1970 cramfsload - loads a file from a cramfs image
1973 bool "ext2 command support"
1976 Enables EXT2 FS command
1979 bool "ext4 command support"
1982 Enables EXT4 FS command
1984 config CMD_EXT4_WRITE
1986 bool "ext4 write command support"
1989 Enables EXT4 FS write command
1992 bool "FAT command support"
1995 Support for the FAT fs
1997 config CMD_FS_GENERIC
1998 bool "filesystem commands"
2000 Enables filesystem commands (e.g. load, ls) that work for multiple
2004 bool "fsuuid command"
2006 Enables fsuuid command for filesystem UUID.
2009 bool "jffs2 command"
2012 Enables commands to support the JFFS2 (Journalling Flash File System
2013 version 2) filesystem. This enables fsload, ls and fsinfo which
2014 provide the ability to load files, list directories and obtain
2015 filesystem information.
2018 bool "MTD partition support"
2021 MTD partitioning tool support.
2022 It is strongly encouraged to avoid using this command
2023 anymore along with 'sf', 'nand', 'onenand'. One can still
2024 declare the partitions in the mtdparts environment variable
2025 but better use the MTD stack and the 'mtd' command instead.
2027 config CMD_MTDPARTS_SPREAD
2028 bool "Padd partition size to take account of bad blocks"
2029 depends on CMD_MTDPARTS
2031 This enables the 'spread' sub-command of the mtdparts command.
2032 This command will modify the existing mtdparts variable by increasing
2033 the size of the partitions such that 1) each partition's net size is
2034 at least as large as the size specified in the mtdparts variable and
2035 2) each partition starts on a good block.
2037 config CMD_MTDPARTS_SHOW_NET_SIZES
2038 bool "Show net size (w/o bad blocks) of partitions"
2039 depends on CMD_MTDPARTS
2041 Adds two columns to the printed partition table showing the
2042 effective usable size of a partition, if bad blocks are taken
2045 config MTDIDS_DEFAULT
2046 string "Default MTD IDs"
2047 depends on MTD || SPI_FLASH
2049 Defines a default MTD IDs list for use with MTD partitions in the
2050 Linux MTD command line partitions format.
2052 config MTDPARTS_DEFAULT
2053 string "Default MTD partition scheme"
2054 depends on MTD || SPI_FLASH
2056 Defines a default MTD partitioning scheme in the Linux MTD command
2057 line partitions format
2060 bool "reiser - Access to reiserfs filesystems"
2062 This provides two commands which operate on a resierfs filesystem,
2063 commonly used some years ago:
2065 reiserls - list files
2066 reiserload - load a file
2069 bool "yaffs2 - Access of YAFFS2 filesystem"
2073 This provides commands for accessing a YAFFS2 filesystem. Yet
2074 Another Flash Filesystem 2 is a filesystem designed specifically
2075 for NAND flash. It incorporates bad-block management and ensures
2076 that device writes are sequential regardless of filesystem
2080 bool "zfs - Access of ZFS filesystem"
2082 This provides commands to accessing a ZFS filesystem, commonly used
2083 on Solaris systems. Two sub-commands are provided:
2085 zfsls - list files in a directory
2086 zfsload - load a file
2088 See doc/README.zfs for more details.
2092 menu "Debug commands"
2097 The bedbug (emBEDded deBUGger) command provides debugging features
2098 for some PowerPC processors. For details please see the
2099 docuemntation in doc/README.beddbug
2102 bool "diag - Board diagnostics"
2104 This command provides access to board diagnostic tests. These are
2105 called Power-on Self Tests (POST). The command allows listing of
2106 available tests and running either all the tests, or specific tests
2110 bool "irq - Show information about interrupts"
2111 depends on !ARM && !MIPS && !SH
2113 This enables two commands:
2115 interrupts - enable or disable interrupts
2116 irqinfo - print device-specific interrupt information
2119 bool "kgdb - Allow debugging of U-Boot with gdb"
2122 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2123 over a serial link for debugging purposes. This allows
2124 single-stepping, inspecting variables, etc. This is supported only
2125 on PowerPC at present.
2128 bool "log - Generation, control and access to logging"
2131 This provides access to logging features. It allows the output of
2132 log data to be controlled to a limited extent (setting up the default
2133 maximum log level for emitting of records). It also provides access
2134 to a command used for testing the log system.
2137 bool "trace - Support tracing of function calls and timing"
2139 Enables a command to control using of function tracing within
2140 U-Boot. This allows recording of call traces including timing
2141 information. The command can write data to memory for exporting
2142 for analysis (e.g. using bootchart). See doc/README.trace for full
2146 bool "avb - Android Verified Boot 2.0 operations"
2147 depends on AVB_VERIFY
2150 Enables a "avb" command to perform verification of partitions using
2151 Android Verified Boot 2.0 functionality. It includes such subcommands:
2152 avb init - initialize avb2 subsystem
2153 avb read_rb - read rollback index
2154 avb write_rb - write rollback index
2155 avb is_unlocked - check device lock state
2156 avb get_uuid - read and print uuid of a partition
2157 avb read_part - read data from partition
2158 avb read_part_hex - read data from partition and output to stdout
2159 avb write_part - write data to partition
2160 avb verify - run full verification chain
2164 tristate "Enable UBI - Unsorted block images commands"
2167 UBI is a software layer above MTD layer which admits use of LVM-like
2168 logical volumes on top of MTD devices, hides some complexities of
2169 flash chips like wear and bad blocks and provides some other useful
2170 capabilities. Please, consult the MTD web site for more details
2171 (www.linux-mtd.infradead.org). Activate this option if you want
2172 to use U-Boot UBI commands.
2173 It is also strongly encouraged to also enable CONFIG_MTD to get full
2177 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2179 default y if CMD_UBI
2182 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob