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"
403 Boot an ELF/vxWorks image from the memory.
406 bool "Flattened Device Tree utility commands"
410 Do FDT related setup before booting into the Operating System.
416 Start an application at a given address.
422 Run the command in the given environment variable.
428 Print header information for application image.
433 List all images found in flash
439 Extract a part of a multi-image.
442 bool "spl export - Export boot information for Falcon boot"
445 Falcon mode allows booting directly from SPL into an Operating
446 System such as Linux, thus skipping U-Boot proper. See
447 doc/README.falcon for full information about how to use this
450 config CMD_SPL_NAND_OFS
451 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
452 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
455 This provides the offset of the command line arguments for Linux
456 when booting from NAND in Falcon mode. See doc/README.falcon
457 for full information about how to use this option (and also see
458 board/gateworks/gw_ventana/README for an example).
460 config CMD_SPL_NOR_OFS
461 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
462 depends on CMD_SPL && SPL_NOR_SUPPORT
465 This provides the offset of the command line arguments or dtb for
466 Linux when booting from NOR in Falcon mode.
468 config CMD_SPL_WRITE_SIZE
469 hex "Size of argument area"
473 This provides the size of the command-line argument area in NAND
474 flash used by Falcon-mode boot. See the documentation until CMD_SPL
478 bool "fitImage update command"
480 Implements the 'fitupd' command, which allows to automatically
481 store software updates present on a TFTP server in NOR Flash
483 config CMD_THOR_DOWNLOAD
484 bool "thor - TIZEN 'thor' download"
487 Implements the 'thor' download protocol. This is a way of
488 downloading a software update over USB from an attached host.
489 There is no documentation about this within the U-Boot source code
490 but you should be able to find something on the interwebs.
493 bool "zboot - x86 boot command"
495 With x86 machines it is common to boot a bzImage file which
496 contains both a kernel and a setup.bin file. The latter includes
497 configuration information from the dark ages which x86 boards still
498 need to pick things out of.
500 Consider using FIT in preference to this since it supports directly
501 booting both 32- and 64-bit kernels, as well as secure boot.
502 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
506 menu "Environment commands"
509 bool "ask for env variable"
511 Ask for environment variable
529 Edit environment variable.
534 Allow for searching environment variables
540 Save all environment variables into the compiled-in persistent
546 depends on CMD_SAVEENV
548 Erase environment variables from the compiled-in persistent
551 config CMD_ENV_EXISTS
555 Check if a variable is defined in the environment for use in
558 config CMD_ENV_CALLBACK
559 bool "env callbacks - print callbacks and their associated variables"
561 Some environment variable have callbacks defined by
562 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
563 For example changing "baudrate" adjust the serial baud rate. This
564 command lists the currently defined callbacks.
567 bool "env flags -print variables that have non-default flags"
569 Some environment variables have special flags that control their
570 behaviour. For example, serial# can only be written once and cannot
571 be deleted. This command shows the variables that have special
574 config CMD_NVEDIT_EFI
575 bool "env [set|print] -e - set/print UEFI variables"
576 depends on EFI_LOADER
579 UEFI variables are encoded as some form of U-Boot variables.
580 If enabled, we are allowed to set/print UEFI variables using
581 "env" command with "-e" option without knowing details.
583 config CMD_NVEDIT_INFO
584 bool "env info - print or evaluate environment information"
586 Print environment information:
587 - env_valid : is environment valid
588 - env_ready : is environment imported into hash table
589 - env_use_default : is default environment used
591 This command can be optionally used for evaluation in scripts:
592 [-d] : evaluate whether default environment is used
593 [-p] : evaluate whether environment can be persisted
594 The result of multiple evaluations will be combined with AND.
598 menu "Memory commands"
603 Compute binary operations (xor, or, and) of byte arrays of arbitrary
604 size from memory and store the result in memory or the environment.
617 Add -v option to verify data against a crc32 checksum.
620 bool "eeprom - EEPROM subsystem"
622 (deprecated, needs conversion to driver model)
623 Provides commands to read and write EEPROM (Electrically Erasable
624 Programmable Read Only Memory) chips that are connected over an
627 config CMD_EEPROM_LAYOUT
628 bool "Enable layout-aware eeprom commands"
629 depends on CMD_EEPROM
631 (deprecated, needs conversion to driver model)
632 When enabled, additional eeprom sub-commands become available.
634 eeprom print - prints the contents of the eeprom in a human-readable
635 way (eeprom layout fields, and data formatted to be fit for human
638 eeprom update - allows user to update eeprom fields by specifying
639 the field name, and providing the new data in a human readable format
640 (same format as displayed by the eeprom print command).
642 Both commands can either auto detect the layout, or be told which
646 __weak int parse_layout_version(char *str)
647 - override to provide your own layout name parsing
648 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
650 - override to setup the layout metadata based on the version
651 __weak int eeprom_layout_detect(unsigned char *data)
652 - override to provide your own algorithm for detecting layout
655 - contains various printing and updating functions for common
656 types of eeprom fields. Can be used for defining
659 config EEPROM_LAYOUT_HELP_STRING
660 string "Tells user what layout names are supported"
661 depends on CMD_EEPROM_LAYOUT
662 default "<not defined>"
664 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
670 Infinite write loop on address range
677 Compute MD5 checksum.
682 depends on CMD_MD5SUM
684 Add -v option to verify data against an MD5 checksum.
689 Display memory information.
692 bool "md, mm, nm, mw, cp, cmp, base, loop"
697 mm - memory modify (auto-incrementing address)
698 nm - memory modify (constant address)
699 mw - memory write (fill)
702 base - print or set address offset
703 loop - initialize loop on address range
706 bool "Enable cyclic md/mw commands"
707 depends on CMD_MEMORY
709 Add the "mdc" and "mwc" memory commands. These are cyclic
714 This command will print 4 bytes (10,11,12,13) each 500 ms.
716 => mwc.l 100 12345678 10
717 This command will write 12345678 to address 100 all 10 ms.
722 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
724 random - fill memory with random data
729 Simple RAM read/write test.
733 config SYS_ALT_MEMTEST
734 bool "Alternative test"
736 Use a more complete alternative memory test.
744 Compute SHA1 checksum.
746 config SHA1SUM_VERIFY
748 depends on CMD_SHA1SUM
750 Add -v option to verify data against a SHA1 checksum.
753 bool "strings - display strings in memory"
755 This works similarly to the Unix 'strings' command except that it
756 works with a memory range. String of printable characters found
757 within the range are displayed. The minimum number of characters
758 for a sequence to be considered a string can be provided.
762 menu "Compression commands"
766 default y if CMD_BOOTI
769 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
774 default y if CMD_BOOTI
776 Uncompress a zip-compressed memory region.
781 Compress a memory region with zlib deflate method.
785 menu "Device access commands"
788 #depends on FLASH_CFI_DRIVER
791 ARM Ltd reference designs flash partition access
794 bool "adc - Access Analog to Digital Converters info and data"
798 Shows ADC device info and permit printing one-shot analog converted
799 data from a named Analog to Digital Converter.
804 depends on PARTITIONS
806 Read/modify/write the fields of Bootloader Control Block, usually
807 stored on the flash "misc" partition with its structure defined in:
808 https://android.googlesource.com/platform/bootable/recovery/+/master/
809 bootloader_message/include/bootloader_message/bootloader_message.h
811 Some real-life use-cases include (but are not limited to):
812 - Determine the "boot reason" (and act accordingly):
813 https://source.android.com/devices/bootloader/boot-reason
814 - Get/pass a list of commands from/to recovery:
815 https://android.googlesource.com/platform/bootable/recovery
816 - Inspect/dump the contents of the BCB fields
819 bool "bind/unbind - Bind or unbind a device to/from a driver"
822 Bind or unbind a device to/from a driver from the command line.
823 This is useful in situations where a device may be handled by several
824 drivers. For example, this can be used to bind a UDC to the usb ether
825 gadget driver from the command line.
828 bool "clk - Show clock frequencies"
831 Shows clock frequences by calling a sock_clk_dump() hook function.
832 This is depreated in favour of using the CLK uclass and accessing
833 clock values from associated drivers. However currently no command
837 bool "demo - Demonstration commands for driver model"
840 Provides a 'demo' command which can be used to play around with
841 driver model. To use this properly you will need to enable one or
842 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
843 Otherwise you will always get an empty list of devices. The demo
844 devices are defined in the sandbox device tree, so the easiest
845 option is to use sandbox and pass the -d point to sandbox's
852 Enables the command "dfu" which is used to have U-Boot create a DFU
853 class device via USB. This command requires that the "dfu_alt_info"
854 environment variable be set and define the alt settings to expose to
858 bool "dm - Access to driver model information"
861 Provides access to driver model data structures and information,
862 such as a list of devices, list of uclasses and the state of each
863 device (e.g. activated). This is not required for operation, but
864 can be useful to see the state of driver model for debugging or
868 bool "fastboot - Android fastboot support"
871 This enables the command "fastboot" which enables the Android
872 fastboot mode for the platform. Fastboot is a protocol for
873 downloading images, flashing and device control used on
874 Android devices. Fastboot requires either the network stack
875 enabled or support for acting as a USB device.
877 See doc/android/fastboot.rst for more information.
880 bool "flinfo, erase, protect"
882 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
885 flinfo - print FLASH memory information
887 protect - enable or disable FLASH write protection
896 config CMD_FPGA_LOADBP
897 bool "fpga loadbp - load partial bitstream (Xilinx only)"
900 Supports loading an FPGA device from a bitstream buffer containing
903 config CMD_FPGA_LOADFS
904 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
907 Supports loading an FPGA device from a FAT filesystem.
909 config CMD_FPGA_LOADMK
910 bool "fpga loadmk - load bitstream from image"
913 Supports loading an FPGA device from a image generated by mkimage.
915 config CMD_FPGA_LOADP
916 bool "fpga loadp - load partial bitstream"
919 Supports loading an FPGA device from a bitstream buffer containing
922 config CMD_FPGA_LOAD_SECURE
923 bool "fpga loads - loads secure bitstreams (Xilinx only)"
926 Enables the fpga loads command which is used to load secure
927 (authenticated or encrypted or both) bitstreams on to FPGA.
930 bool "fpgad - dump FPGA registers"
932 (legacy, needs conversion to driver model)
933 Provides a way to dump FPGA registers by calling the board-specific
934 fpga_get_reg() function. This functions similarly to the 'md'
938 bool "fuse - support for the fuse subssystem"
940 (deprecated - needs conversion to driver model)
941 This allows reading, sensing, programming or overriding fuses
942 which control the behaviour of the device. The command uses the
951 bool "GPT (GUID Partition Table) command"
953 select HAVE_BLOCK_DEVICE
954 select PARTITION_UUIDS
957 Enable the 'gpt' command to ready and write GPT style partition
961 bool "GPT Random UUID generation"
964 Enable the generation of partitions with random UUIDs if none
967 config CMD_GPT_RENAME
968 bool "GPT partition renaming commands"
971 Enables the 'gpt' command to interchange names on two GPT
972 partitions via the 'gpt swap' command or to rename single
973 partitions via the 'rename' command.
976 bool "ide - Support for IDE drivers"
979 Provides an 'ide' command which allows accessing the IDE drive,
980 reseting the IDE interface, printing the partition table and
981 geting device info. It also enables the 'diskboot' command which
982 permits booting from an IDE drive.
985 bool "io - Support for performing I/O accesses"
987 Provides an 'iod' command to display I/O space and an 'iow' command
988 to write values to the I/O space. This can be useful for manually
989 checking the state of devices during boot when debugging device
993 bool "iotrace - Support for tracing I/O activity"
995 Provides an 'iotrace' command which supports recording I/O reads and
996 writes in a trace buffer in memory . It also maintains a checksum
997 of the trace records (even if space is exhausted) so that the
998 sequence of I/O accesses can be verified.
1000 When debugging drivers it is useful to see what I/O accesses were
1001 done and in what order.
1003 Even if the individual accesses are of little interest it can be
1004 useful to verify that the access pattern is consistent each time
1005 an operation is performed. In this case a checksum can be used to
1006 characterise the operation of a driver. The checksum can be compared
1007 across different runs of the operation to verify that the driver is
1010 In particular, when performing major refactoring of the driver, where
1011 the access pattern should not change, the checksum provides assurance
1012 that the refactoring work has not broken the driver.
1014 This works by sneaking into the io.h heder for an architecture and
1015 redirecting I/O accesses through iotrace's tracing mechanism.
1017 For now no commands are provided to examine the trace buffer. The
1018 format is fairly simple, so 'md' is a reasonable substitute.
1020 Note: The checksum feature is only useful for I/O regions where the
1021 contents do not change outside of software control. Where this is not
1022 suitable you can fall back to manually comparing the addresses. It
1023 might be useful to enhance tracing to only checksum the accesses and
1024 not the data read/written.
1034 bool "w1 - Support for Dallas 1-Wire protocol"
1036 Dallas 1-wire protocol support
1042 Load a binary file over serial line.
1048 Load an S-Record file over serial line
1053 MMC memory mapped support.
1056 bool "Enable support for RPMB in the mmc command"
1059 Enable the commands for reading, writing and programming the
1060 key for the Replay Protection Memory Block partition in eMMC.
1062 config CMD_MMC_SWRITE
1064 depends on CMD_MMC && MMC_WRITE
1067 Enable support for the "mmc swrite" command to write Android sparse
1073 select MTD_PARTITIONS
1075 MTD commands support.
1079 default y if NAND_SUNXI
1080 depends on MTD_RAW_NAND
1085 config CMD_NAND_TRIMFFS
1086 bool "nand write.trimffs"
1087 default y if ARCH_SUNXI
1089 Allows one to skip empty pages when flashing something on a NAND.
1091 config CMD_NAND_LOCK_UNLOCK
1092 bool "nand lock/unlock"
1094 NAND locking support.
1096 config CMD_NAND_TORTURE
1099 NAND torture support.
1108 NVM Express device support
1111 bool "onenand - access to onenand device"
1114 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1115 various useful features. This command allows reading, writing,
1116 and erasing blocks. It allso provides a way to show and change
1117 bad blocks, and test the device.
1122 Enable the 'osd' command which allows to query information from and
1123 write text data to a on-screen display (OSD) device; a virtual device
1124 associated with a display capable of displaying a text overlay on the
1125 display it's associated with..
1129 select HAVE_BLOCK_DEVICE
1130 select PARTITION_UUIDS
1132 Read and display information about the partition table on
1136 bool "pci - Access PCI devices"
1138 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1139 used on some devices to allow the CPU to communicate with its
1140 peripherals. Sub-commands allow bus enumeration, displaying and
1141 changing configuration space and a few other features.
1144 bool "pinmux - show pins muxing"
1145 default y if PINCTRL
1147 Parse all available pin-controllers and show pins muxing. This
1148 is useful for debug purpoer to check the pin muxing and to know if
1149 a pin is configured as a GPIO or as an alternate function.
1154 Poweroff/Shutdown the system
1157 bool "read - Read binary data from a partition"
1159 Provides low-level access to the data in a partition.
1161 config CMD_REMOTEPROC
1163 depends on REMOTEPROC
1165 Support for Remote Processor control
1168 bool "sata - Access SATA subsystem"
1171 SATA (Serial Advanced Technology Attachment) is a serial bus
1172 standard for connecting to hard drives and other storage devices.
1173 This command provides information about attached devices and allows
1174 reading, writing and other operations.
1176 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1177 Attachment, where AT refers to an IBM AT (Advanced Technology)
1178 computer released in 1984.
1181 bool "saves - Save a file over serial in S-Record format"
1183 Provides a way to save a binary file using the Motorola S-Record
1184 format over the serial line.
1187 bool "scsi - Access to SCSI devices"
1190 This provides a 'scsi' command which provides access to SCSI (Small
1191 Computer System Interface) devices. The command provides a way to
1192 scan the bus, reset the bus, read and write data and get information
1196 bool "sdram - Print SDRAM configuration information"
1198 Provides information about attached SDRAM. This assumed that the
1199 SDRAM has an EEPROM with information that can be read using the
1200 I2C bus. This is only available on some boards.
1204 depends on DM_SPI_FLASH || SPI_FLASH
1205 default y if DM_SPI_FLASH
1210 bool "sf test - Allow testing of SPI flash"
1213 Provides a way to test that SPI flash is working correctly. The
1214 test is destructive, in that an area of SPI flash must be provided
1215 for the test to use. Performance information is also provided,
1216 measuring the performance of reading, writing and erasing in
1217 Mbps (Million Bits Per Second). This value should approximately
1218 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1219 everything is working properly.
1222 bool "sspi - Command to access spi device"
1225 SPI utility command.
1227 config DEFAULT_SPI_BUS
1228 int "default spi bus used by sspi command"
1232 config DEFAULT_SPI_MODE
1233 hex "default spi mode used by sspi command (see include/spi.h)"
1238 bool "tsi148 - Command to access tsi148 device"
1240 This provides various sub-commands to initialise and configure the
1241 Turndra tsi148 device. See the command help for full details.
1244 bool "Enable UFS - Universal Flash Subsystem commands"
1247 "This provides commands to initialise and configure universal flash
1251 bool "universe - Command to set up the Turndra Universe controller"
1253 This allows setting up the VMEbus provided by this controller.
1254 See the command help for full details.
1258 select HAVE_BLOCK_DEVICE
1264 select USB_FUNCTION_SDP
1266 Enables the command "sdp" which is used to have U-Boot emulating the
1267 Serial Download Protocol (SDP) via USB.
1271 depends on USB_FUNCTION_ROCKUSB
1273 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1274 read/write info, image to/from devices. This enable rockusb command
1275 support to communication with rockusb device. for more detail about
1276 this command, please read doc/README.rockusb.
1278 config CMD_USB_MASS_STORAGE
1279 bool "UMS usb mass storage"
1280 select USB_FUNCTION_MASS_STORAGE
1282 USB mass storage support
1289 VirtIO block device support
1295 This provides commands to control the watchdog timer devices.
1301 Enable the command "axi" for accessing AXI (Advanced eXtensible
1302 Interface) busses, a on-chip interconnect specification for managing
1303 functional blocks in SoC designs, which is also often used in designs
1304 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1308 menu "Shell scripting commands"
1314 Echo args to console
1320 Return true/false on integer compare.
1326 Run script from memory
1332 Evaluate boolean and math expressions and store the result in an env
1334 Also supports loading the value at a memory location into a variable.
1335 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1339 menu "Android support commands"
1341 config CMD_AB_SELECT
1344 depends on ANDROID_AB
1346 On Android devices with more than one boot slot (multiple copies of
1347 the kernel and system images) this provides a command to select which
1348 slot should be used to boot from and register the boot attempt. This
1349 is used by the new A/B update model where one slot is updated in the
1350 background while running from the other slot.
1357 bool "Network commands"
1367 bootp - boot image via network using BOOTP/TFTP protocol
1371 depends on CMD_BOOTP
1373 Boot image via network using DHCP/TFTP protocol
1375 config BOOTP_BOOTPATH
1376 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1378 depends on CMD_BOOTP
1380 Even though the config is called BOOTP_BOOTPATH, it stores the
1381 path in the variable 'rootpath'.
1384 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1386 depends on CMD_BOOTP
1388 The primary DNS server is stored as 'dnsip'. If two servers are
1389 returned, you must set BOOTP_DNS2 to store that second server IP
1393 bool "Store 'dnsip2' from BOOTP/DHCP server"
1394 depends on BOOTP_DNS
1396 If a DHCP client requests the DNS server IP from a DHCP server,
1397 it is possible that more than one DNS serverip is offered to the
1398 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1399 server IP will be stored in the additional environment
1400 variable "dnsip2". The first DNS serverip is always
1401 stored in the variable "dnsip", when BOOTP_DNS is defined.
1403 config BOOTP_GATEWAY
1404 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1406 depends on CMD_BOOTP
1408 config BOOTP_HOSTNAME
1409 bool "Request & store 'hostname' from BOOTP/DHCP server"
1411 depends on CMD_BOOTP
1413 The name may or may not be qualified with the local domain name.
1415 config BOOTP_PREFER_SERVERIP
1416 bool "serverip variable takes precedent over DHCP server IP."
1417 depends on CMD_BOOTP
1419 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1421 With this option enabled, the 'serverip' variable in the environment
1422 takes precedence over DHCP server IP and will only be set by the DHCP
1423 server if not already set in the environment.
1425 config BOOTP_SUBNETMASK
1426 bool "Request & store 'netmask' from BOOTP/DHCP server"
1428 depends on CMD_BOOTP
1430 config BOOTP_NTPSERVER
1431 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1432 depends on CMD_BOOTP
1437 Selecting this will allow capturing all Ethernet packets and store
1438 them in physical memory in a PCAP formated file,
1439 later to be analyzed by PCAP reader application (IE. WireShark).
1442 bool "Send PXE client arch to BOOTP/DHCP server"
1444 depends on CMD_BOOTP && CMD_PXE
1446 Supported for ARM, ARM64, and x86 for now.
1448 config BOOTP_PXE_CLIENTARCH
1450 depends on BOOTP_PXE
1451 default 0x16 if ARM64
1455 config BOOTP_VCI_STRING
1457 depends on CMD_BOOTP
1458 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1459 default "U-Boot.armv8" if ARM64
1460 default "U-Boot.arm" if ARM
1467 tftpboot - boot image via network using TFTP protocol
1471 depends on CMD_TFTPBOOT
1473 TFTP put command, for uploading files to a server
1477 depends on CMD_TFTPBOOT
1479 Act as a TFTP server and boot the first received file
1481 config NET_TFTP_VARS
1482 bool "Control TFTP timeout and count through environment"
1483 depends on CMD_TFTPBOOT
1486 If set, allows controlling the TFTP timeout through the
1487 environment variable tftptimeout, and the TFTP maximum
1488 timeout count through the variable tftptimeoutcountmax.
1489 If unset, timeout and maximum are hard-defined as 1 second
1490 and 10 timouts per TFTP transfer.
1495 Boot image via network using RARP/TFTP protocol
1501 Boot image via network using NFS protocol.
1507 If set, allows 802.3(clause 22) MII Management functions interface access
1508 The management interface specified in Clause 22 provides
1509 a simple, two signal, serial interface to connect a
1510 Station Management entity and a managed PHY for providing access
1511 to management parameters and services.
1512 The interface is referred to as the MII management interface.
1518 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1519 The MDIO interface is orthogonal to the MII interface and extends
1520 it by adding access to more registers through indirect addressing.
1525 Send ICMP ECHO_REQUEST to network host
1530 Perform CDP network configuration
1535 Synchronize RTC via network
1540 Lookup the IP of a hostname
1542 config CMD_LINK_LOCAL
1546 Acquire a network IP address using the link-local protocol
1553 Allow control of L2 Ethernet switch commands. These are supported
1554 by the vsc9953 Ethernet driver at present. Sub-commands allow
1555 operations such as enabling / disabling a port and
1556 viewing/maintaining the filtering database (FDB)
1562 Boot image via network using PXE protocol
1567 Wait for wake-on-lan Magic Packet
1571 menu "Misc commands"
1574 bool "Enable 'bmp' command"
1575 depends on LCD || DM_VIDEO || VIDEO
1577 This provides a way to obtain information about a BMP-format image
1578 and to display it. BMP (which presumably stands for BitMaP) is a
1579 file format defined by Microsoft which supports images of various
1580 depths, formats and compression methods. Headers on the file
1581 determine the formats used. This command can be used by first loading
1582 the image into RAM, then using this command to look at it or display
1585 config CMD_BOOTCOUNT
1587 depends on BOOTCOUNT_LIMIT
1589 Enable the bootcount command, which allows interrogation and
1590 reset of the bootcounter.
1593 bool "Enable board-specific commands"
1595 (deprecated: instead, please define a Kconfig option for each command)
1597 Some boards have board-specific commands which are only enabled
1598 during developemnt and need to be turned off for production. This
1599 option provides a way to control this. The commands that are enabled
1600 vary depending on the board.
1602 config CMD_BKOPS_ENABLE
1603 bool "mmc bkops enable"
1607 Enable command for setting manual background operations handshake
1608 on a eMMC device. The feature is optionally available on eMMC devices
1609 conforming to standard >= 4.41.
1611 config CMD_BLOCK_CACHE
1612 bool "blkcache - control and stats for block cache"
1613 depends on BLOCK_CACHE
1614 default y if BLOCK_CACHE
1616 Enable the blkcache command, which can be used to control the
1617 operation of the cache functions.
1618 This is most useful when fine-tuning the operation of the cache
1619 during development, but also allows the cache to be disabled when
1620 it might hurt performance (e.g. when using the ums command).
1623 bool "icache or dcache"
1625 Enable the "icache" and "dcache" commands
1627 config CMD_CONITRACE
1628 bool "conitrace - trace console input codes"
1630 Enable the 'conitrace' command which displays the codes received
1631 from the console input as hexadecimal numbers.
1634 bool "Enable clear screen command 'cls'"
1635 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1638 Enable the 'cls' command which clears the screen contents
1639 on video frame buffer.
1642 bool "efidebug - display/configure UEFI environment"
1643 depends on EFI_LOADER
1644 select EFI_DEVICE_PATH_TO_TEXT
1647 Enable the 'efidebug' command which provides a subset of UEFI
1648 shell utility with simplified functionality. It will be useful
1649 particularly for managing boot parameters as well as examining
1650 various EFI status for debugging.
1652 config CMD_EXCEPTION
1653 bool "exception - raise exception"
1654 depends on ARM || RISCV || X86
1656 Enable the 'exception' command which allows to raise an exception.
1663 Enable the 'led' command which allows for control of LEDs supported
1664 by the board. The LEDs can be listed with 'led list' and controlled
1665 with led on/off/togle/blink. Any LED drivers can be controlled with
1666 this command, e.g. led_gpio.
1673 Enable the 'date' command for getting/setting the time/date in RTC
1679 Run commands and summarize execution time.
1682 bool "gettime - read elapsed time"
1684 Enable the 'gettime' command which reads the elapsed time since
1685 U-Boot started running. This shows the time in seconds and
1686 milliseconds. See also the 'bootstage' command which provides more
1687 flexibility for boot timing.
1694 Print bytes from the hardware random number generator.
1696 # TODO: rename to CMD_SLEEP
1701 Delay execution for some time
1704 bool "support for multiprocessor"
1706 This provides an option to brinup
1707 different processors in multiprocessor
1713 Access the system timer.
1719 This provides basic access to the U-Boot's sound support. The main
1720 feature is to play a beep.
1722 sound init - set up sound system
1723 sound play - play a sound
1729 Boot image via local extlinux.conf file
1735 This provides access to the QEMU firmware interface. The main
1736 feature is to allow easy loading of files passed to qemu-system
1737 via -kernel / -initrd
1739 source "cmd/mvebu/Kconfig"
1742 bool "terminal - provides a way to attach a serial terminal"
1744 Provides a 'cu'-like serial terminal command. This can be used to
1745 access other serial ports from the system console. The terminal
1746 is very simple with no special processing of characters. As with
1747 cu, you can press ~. (tilde followed by period) to exit.
1750 bool "uuid, guid - generation of unique IDs"
1753 This enables two commands:
1755 uuid - generate random Universally Unique Identifier
1756 guid - generate Globally Unique Identifier based on random UUID
1758 The two commands are very similar except for the endianness of the
1763 source "cmd/ti/Kconfig"
1765 config CMD_BOOTSTAGE
1766 bool "Enable the 'bootstage' command"
1767 depends on BOOTSTAGE
1769 Add a 'bootstage' command which supports printing a report
1770 and un/stashing of bootstage data.
1772 menu "Power commands"
1774 bool "Enable Driver Model PMIC command"
1777 This is the pmic command, based on a driver model pmic's API.
1778 Command features are unchanged:
1779 - list - list pmic devices
1780 - pmic dev <id> - show or [set] operating pmic device (NEW)
1781 - pmic dump - dump registers
1782 - pmic read address - read byte of register at address
1783 - pmic write address - write byte to register at address
1784 The only one change for this command is 'dev' subcommand.
1786 config CMD_REGULATOR
1787 bool "Enable Driver Model REGULATOR command"
1788 depends on DM_REGULATOR
1790 This command is based on driver model regulator's API.
1791 User interface features:
1792 - list - list regulator devices
1793 - regulator dev <id> - show or [set] operating regulator device
1794 - regulator info - print constraints info
1795 - regulator status - print operating status
1796 - regulator value <val] <-f> - print/[set] voltage value [uV]
1797 - regulator current <val> - print/[set] current value [uA]
1798 - regulator mode <id> - print/[set] operating mode id
1799 - regulator enable - enable the regulator output
1800 - regulator disable - disable the regulator output
1802 The '-f' (force) option can be used for set the value which exceeds
1803 the limits, which are found in device-tree and are kept in regulator's
1804 uclass platdata structure.
1808 menu "Security commands"
1810 bool "Enable the 'aes' command"
1813 This provides a means to encrypt and decrypt data using the AES
1814 (Advanced Encryption Standard). This algorithm uses a symetric key
1815 and is widely used as a streaming cipher. Different key lengths are
1816 supported by the algorithm but this command only supports 128 bits
1820 bool "Enable the 'blob' command"
1822 This is used with the Freescale secure boot mechanism.
1824 Freescale's SEC block has built-in Blob Protocol which provides
1825 a method for protecting user-defined data across system power
1826 cycles. SEC block protects data in a data structure called a Blob,
1827 which provides both confidentiality and integrity protection.
1829 Encapsulating data as a blob
1830 Each time that the Blob Protocol is used to protect data, a
1831 different randomly generated key is used to encrypt the data.
1832 This random key is itself encrypted using a key which is derived
1833 from SoC's non-volatile secret key and a 16 bit Key identifier.
1834 The resulting encrypted key along with encrypted data is called a
1835 blob. The non-volatile secure key is available for use only during
1838 During decapsulation, the reverse process is performed to get back
1842 blob enc - encapsulating data as a cryptgraphic blob
1843 blob dec - decapsulating cryptgraphic blob to get the data
1847 blob enc src dst len km
1849 Encapsulate and create blob of data $len bytes long
1850 at address $src and store the result at address $dst.
1851 $km is the 16 byte key modifier is also required for
1852 generation/use as key for cryptographic operation. Key
1853 modifier should be 16 byte long.
1855 blob dec src dst len km
1857 Decapsulate the blob of data at address $src and
1858 store result of $len byte at addr $dst.
1859 $km is the 16 byte key modifier is also required for
1860 generation/use as key for cryptographic operation. Key
1861 modifier should be 16 byte long.
1864 bool "Support 'hash' command"
1867 This provides a way to hash data in memory using various supported
1868 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1869 saved to memory or to an environment variable. It is also possible
1870 to verify a hash against data in memory.
1873 bool "Support the 'hvc' command"
1874 depends on ARM_SMCCC
1876 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1877 development and testing.
1880 bool "Support the 'smc' command"
1881 depends on ARM_SMCCC
1883 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1884 development and testing.
1890 Add -v option to verify data against a hash.
1900 bool "Enable the 'tpm' command"
1901 depends on TPM_V1 || TPM_V2
1902 select CMD_TPM_V1 if TPM_V1
1903 select CMD_TPM_V2 if TPM_V2
1905 This provides a means to talk to a TPM from the command line. A wide
1906 range of commands if provided - see 'tpm help' for details. The
1907 command requires a suitable TPM on your board and the correct driver
1913 bool "Enable the 'tpm test' command"
1916 This provides a a series of tests to confirm that the TPMv1.x is
1917 working correctly. The tests cover initialisation, non-volatile RAM,
1918 extend, global lock and checking that timing is within expectations.
1919 The tests pass correctly on Infineon TPMs but may need to be adjusted
1926 menu "Firmware commands"
1928 bool "Enable crosec command"
1932 Enable command-line access to the Chrome OS EC (Embedded
1933 Controller). This provides the 'crosec' command which has
1934 a number of sub-commands for performing EC tasks such as
1935 updating its flash, accessing a small saved context area
1936 and talking to the I2C bus behind the EC (if there is one).
1939 menu "Filesystem commands"
1941 bool "Enable the 'btrsubvol' command"
1944 This enables the 'btrsubvol' command to list subvolumes
1945 of a BTRFS filesystem. There are no special commands for
1946 listing BTRFS directories or loading BTRFS files - this
1947 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1948 when BTRFS is enabled (see FS_BTRFS).
1951 bool "Enable the 'cbfs' command"
1954 Define this to enable support for reading from a Coreboot
1955 filesystem. This is a ROM-based filesystem used for accessing files
1956 on systems that use coreboot as the first boot-loader and then load
1957 U-Boot to actually boot the Operating System. Available commands are
1958 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1961 bool "Enable the 'cramfs' command"
1962 depends on FS_CRAMFS
1964 This provides commands for dealing with CRAMFS (Compressed ROM
1965 filesystem). CRAMFS is useful when space is tight since files are
1966 compressed. Two commands are provided:
1968 cramfsls - lists files in a cramfs image
1969 cramfsload - loads a file from a cramfs image
1972 bool "ext2 command support"
1975 Enables EXT2 FS command
1978 bool "ext4 command support"
1981 Enables EXT4 FS command
1983 config CMD_EXT4_WRITE
1985 bool "ext4 write command support"
1988 Enables EXT4 FS write command
1991 bool "FAT command support"
1994 Support for the FAT fs
1996 config CMD_FS_GENERIC
1997 bool "filesystem commands"
1999 Enables filesystem commands (e.g. load, ls) that work for multiple
2003 bool "fsuuid command"
2005 Enables fsuuid command for filesystem UUID.
2008 bool "jffs2 command"
2011 Enables commands to support the JFFS2 (Journalling Flash File System
2012 version 2) filesystem. This enables fsload, ls and fsinfo which
2013 provide the ability to load files, list directories and obtain
2014 filesystem information.
2017 bool "MTD partition support"
2020 MTD partitioning tool support.
2021 It is strongly encouraged to avoid using this command
2022 anymore along with 'sf', 'nand', 'onenand'. One can still
2023 declare the partitions in the mtdparts environment variable
2024 but better use the MTD stack and the 'mtd' command instead.
2026 config CMD_MTDPARTS_SPREAD
2027 bool "Padd partition size to take account of bad blocks"
2028 depends on CMD_MTDPARTS
2030 This enables the 'spread' sub-command of the mtdparts command.
2031 This command will modify the existing mtdparts variable by increasing
2032 the size of the partitions such that 1) each partition's net size is
2033 at least as large as the size specified in the mtdparts variable and
2034 2) each partition starts on a good block.
2036 config CMD_MTDPARTS_SHOW_NET_SIZES
2037 bool "Show net size (w/o bad blocks) of partitions"
2038 depends on CMD_MTDPARTS
2040 Adds two columns to the printed partition table showing the
2041 effective usable size of a partition, if bad blocks are taken
2044 config MTDIDS_DEFAULT
2045 string "Default MTD IDs"
2046 depends on MTD || SPI_FLASH
2048 Defines a default MTD IDs list for use with MTD partitions in the
2049 Linux MTD command line partitions format.
2051 config MTDPARTS_DEFAULT
2052 string "Default MTD partition scheme"
2053 depends on MTD || SPI_FLASH
2055 Defines a default MTD partitioning scheme in the Linux MTD command
2056 line partitions format
2059 bool "reiser - Access to reiserfs filesystems"
2061 This provides two commands which operate on a resierfs filesystem,
2062 commonly used some years ago:
2064 reiserls - list files
2065 reiserload - load a file
2068 bool "yaffs2 - Access of YAFFS2 filesystem"
2072 This provides commands for accessing a YAFFS2 filesystem. Yet
2073 Another Flash Filesystem 2 is a filesystem designed specifically
2074 for NAND flash. It incorporates bad-block management and ensures
2075 that device writes are sequential regardless of filesystem
2079 bool "zfs - Access of ZFS filesystem"
2081 This provides commands to accessing a ZFS filesystem, commonly used
2082 on Solaris systems. Two sub-commands are provided:
2084 zfsls - list files in a directory
2085 zfsload - load a file
2087 See doc/README.zfs for more details.
2091 menu "Debug commands"
2096 The bedbug (emBEDded deBUGger) command provides debugging features
2097 for some PowerPC processors. For details please see the
2098 docuemntation in doc/README.beddbug
2101 bool "diag - Board diagnostics"
2103 This command provides access to board diagnostic tests. These are
2104 called Power-on Self Tests (POST). The command allows listing of
2105 available tests and running either all the tests, or specific tests
2109 bool "irq - Show information about interrupts"
2110 depends on !ARM && !MIPS && !SH
2112 This enables two commands:
2114 interrupts - enable or disable interrupts
2115 irqinfo - print device-specific interrupt information
2118 bool "kgdb - Allow debugging of U-Boot with gdb"
2121 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2122 over a serial link for debugging purposes. This allows
2123 single-stepping, inspecting variables, etc. This is supported only
2124 on PowerPC at present.
2127 bool "log - Generation, control and access to logging"
2130 This provides access to logging features. It allows the output of
2131 log data to be controlled to a limited extent (setting up the default
2132 maximum log level for emitting of records). It also provides access
2133 to a command used for testing the log system.
2136 bool "trace - Support tracing of function calls and timing"
2138 Enables a command to control using of function tracing within
2139 U-Boot. This allows recording of call traces including timing
2140 information. The command can write data to memory for exporting
2141 for analysis (e.g. using bootchart). See doc/README.trace for full
2145 bool "avb - Android Verified Boot 2.0 operations"
2146 depends on AVB_VERIFY
2149 Enables a "avb" command to perform verification of partitions using
2150 Android Verified Boot 2.0 functionality. It includes such subcommands:
2151 avb init - initialize avb2 subsystem
2152 avb read_rb - read rollback index
2153 avb write_rb - write rollback index
2154 avb is_unlocked - check device lock state
2155 avb get_uuid - read and print uuid of a partition
2156 avb read_part - read data from partition
2157 avb read_part_hex - read data from partition and output to stdout
2158 avb write_part - write data to partition
2159 avb verify - run full verification chain
2163 tristate "Enable UBI - Unsorted block images commands"
2166 UBI is a software layer above MTD layer which admits use of LVM-like
2167 logical volumes on top of MTD devices, hides some complexities of
2168 flash chips like wear and bad blocks and provides some other useful
2169 capabilities. Please, consult the MTD web site for more details
2170 (www.linux-mtd.infradead.org). Activate this option if you want
2171 to use U-Boot UBI commands.
2172 It is also strongly encouraged to also enable CONFIG_MTD to get full
2176 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2178 default y if CMD_UBI
2181 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob