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
778 Support decompressing an LZ4 image from memory region.
782 default y if CMD_BOOTI
784 Uncompress a zip-compressed memory region.
789 Compress a memory region with zlib deflate method.
793 menu "Device access commands"
796 #depends on FLASH_CFI_DRIVER
799 ARM Ltd reference designs flash partition access
802 bool "adc - Access Analog to Digital Converters info and data"
806 Shows ADC device info and permit printing one-shot analog converted
807 data from a named Analog to Digital Converter.
812 depends on PARTITIONS
814 Read/modify/write the fields of Bootloader Control Block, usually
815 stored on the flash "misc" partition with its structure defined in:
816 https://android.googlesource.com/platform/bootable/recovery/+/master/
817 bootloader_message/include/bootloader_message/bootloader_message.h
819 Some real-life use-cases include (but are not limited to):
820 - Determine the "boot reason" (and act accordingly):
821 https://source.android.com/devices/bootloader/boot-reason
822 - Get/pass a list of commands from/to recovery:
823 https://android.googlesource.com/platform/bootable/recovery
824 - Inspect/dump the contents of the BCB fields
827 bool "bind/unbind - Bind or unbind a device to/from a driver"
830 Bind or unbind a device to/from a driver from the command line.
831 This is useful in situations where a device may be handled by several
832 drivers. For example, this can be used to bind a UDC to the usb ether
833 gadget driver from the command line.
836 bool "clk - Show clock frequencies"
839 Shows clock frequences by calling a sock_clk_dump() hook function.
840 This is depreated in favour of using the CLK uclass and accessing
841 clock values from associated drivers. However currently no command
845 bool "demo - Demonstration commands for driver model"
848 Provides a 'demo' command which can be used to play around with
849 driver model. To use this properly you will need to enable one or
850 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
851 Otherwise you will always get an empty list of devices. The demo
852 devices are defined in the sandbox device tree, so the easiest
853 option is to use sandbox and pass the -d point to sandbox's
860 Enables the command "dfu" which is used to have U-Boot create a DFU
861 class device via USB. This command requires that the "dfu_alt_info"
862 environment variable be set and define the alt settings to expose to
866 bool "dm - Access to driver model information"
869 Provides access to driver model data structures and information,
870 such as a list of devices, list of uclasses and the state of each
871 device (e.g. activated). This is not required for operation, but
872 can be useful to see the state of driver model for debugging or
876 bool "fastboot - Android fastboot support"
879 This enables the command "fastboot" which enables the Android
880 fastboot mode for the platform. Fastboot is a protocol for
881 downloading images, flashing and device control used on
882 Android devices. Fastboot requires either the network stack
883 enabled or support for acting as a USB device.
885 See doc/android/fastboot.rst for more information.
888 bool "flinfo, erase, protect"
890 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
893 flinfo - print FLASH memory information
895 protect - enable or disable FLASH write protection
904 config CMD_FPGA_LOADBP
905 bool "fpga loadbp - load partial bitstream (Xilinx only)"
908 Supports loading an FPGA device from a bitstream buffer containing
911 config CMD_FPGA_LOADFS
912 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
915 Supports loading an FPGA device from a FAT filesystem.
917 config CMD_FPGA_LOADMK
918 bool "fpga loadmk - load bitstream from image"
921 Supports loading an FPGA device from a image generated by mkimage.
923 config CMD_FPGA_LOADP
924 bool "fpga loadp - load partial bitstream"
927 Supports loading an FPGA device from a bitstream buffer containing
930 config CMD_FPGA_LOAD_SECURE
931 bool "fpga loads - loads secure bitstreams (Xilinx only)"
934 Enables the fpga loads command which is used to load secure
935 (authenticated or encrypted or both) bitstreams on to FPGA.
938 bool "fpgad - dump FPGA registers"
940 (legacy, needs conversion to driver model)
941 Provides a way to dump FPGA registers by calling the board-specific
942 fpga_get_reg() function. This functions similarly to the 'md'
946 bool "fuse - support for the fuse subssystem"
948 (deprecated - needs conversion to driver model)
949 This allows reading, sensing, programming or overriding fuses
950 which control the behaviour of the device. The command uses the
959 bool "GPT (GUID Partition Table) command"
961 select HAVE_BLOCK_DEVICE
962 select PARTITION_UUIDS
965 Enable the 'gpt' command to ready and write GPT style partition
969 bool "GPT Random UUID generation"
972 Enable the generation of partitions with random UUIDs if none
975 config CMD_GPT_RENAME
976 bool "GPT partition renaming commands"
979 Enables the 'gpt' command to interchange names on two GPT
980 partitions via the 'gpt swap' command or to rename single
981 partitions via the 'rename' command.
984 bool "ide - Support for IDE drivers"
987 Provides an 'ide' command which allows accessing the IDE drive,
988 reseting the IDE interface, printing the partition table and
989 geting device info. It also enables the 'diskboot' command which
990 permits booting from an IDE drive.
993 bool "io - Support for performing I/O accesses"
995 Provides an 'iod' command to display I/O space and an 'iow' command
996 to write values to the I/O space. This can be useful for manually
997 checking the state of devices during boot when debugging device
1001 bool "iotrace - Support for tracing I/O activity"
1003 Provides an 'iotrace' command which supports recording I/O reads and
1004 writes in a trace buffer in memory . It also maintains a checksum
1005 of the trace records (even if space is exhausted) so that the
1006 sequence of I/O accesses can be verified.
1008 When debugging drivers it is useful to see what I/O accesses were
1009 done and in what order.
1011 Even if the individual accesses are of little interest it can be
1012 useful to verify that the access pattern is consistent each time
1013 an operation is performed. In this case a checksum can be used to
1014 characterise the operation of a driver. The checksum can be compared
1015 across different runs of the operation to verify that the driver is
1018 In particular, when performing major refactoring of the driver, where
1019 the access pattern should not change, the checksum provides assurance
1020 that the refactoring work has not broken the driver.
1022 This works by sneaking into the io.h heder for an architecture and
1023 redirecting I/O accesses through iotrace's tracing mechanism.
1025 For now no commands are provided to examine the trace buffer. The
1026 format is fairly simple, so 'md' is a reasonable substitute.
1028 Note: The checksum feature is only useful for I/O regions where the
1029 contents do not change outside of software control. Where this is not
1030 suitable you can fall back to manually comparing the addresses. It
1031 might be useful to enhance tracing to only checksum the accesses and
1032 not the data read/written.
1042 bool "w1 - Support for Dallas 1-Wire protocol"
1044 Dallas 1-wire protocol support
1050 Load a binary file over serial line.
1056 Load an S-Record file over serial line
1061 MMC memory mapped support.
1065 config CMD_BKOPS_ENABLE
1066 bool "mmc bkops enable"
1070 Enable command for setting manual background operations handshake
1071 on a eMMC device. The feature is optionally available on eMMC devices
1072 conforming to standard >= 4.41.
1075 bool "Enable support for RPMB in the mmc command"
1076 depends on SUPPORT_EMMC_RPMB
1078 Enable the commands for reading, writing and programming the
1079 key for the Replay Protection Memory Block partition in eMMC.
1081 config CMD_MMC_SWRITE
1083 depends on MMC_WRITE
1086 Enable support for the "mmc swrite" command to write Android sparse
1094 select MTD_PARTITIONS
1096 MTD commands support.
1100 default y if NAND_SUNXI
1101 depends on MTD_RAW_NAND
1106 config CMD_NAND_TRIMFFS
1107 bool "nand write.trimffs"
1108 default y if ARCH_SUNXI
1110 Allows one to skip empty pages when flashing something on a NAND.
1112 config CMD_NAND_LOCK_UNLOCK
1113 bool "nand lock/unlock"
1115 NAND locking support.
1117 config CMD_NAND_TORTURE
1120 NAND torture support.
1129 NVM Express device support
1132 bool "onenand - access to onenand device"
1135 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1136 various useful features. This command allows reading, writing,
1137 and erasing blocks. It allso provides a way to show and change
1138 bad blocks, and test the device.
1143 Enable the 'osd' command which allows to query information from and
1144 write text data to a on-screen display (OSD) device; a virtual device
1145 associated with a display capable of displaying a text overlay on the
1146 display it's associated with..
1150 select HAVE_BLOCK_DEVICE
1151 select PARTITION_UUIDS
1153 Read and display information about the partition table on
1157 bool "pci - Access PCI devices"
1159 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1160 used on some devices to allow the CPU to communicate with its
1161 peripherals. Sub-commands allow bus enumeration, displaying and
1162 changing configuration space and a few other features.
1165 bool "pinmux - show pins muxing"
1166 default y if PINCTRL
1168 Parse all available pin-controllers and show pins muxing. This
1169 is useful for debug purpoer to check the pin muxing and to know if
1170 a pin is configured as a GPIO or as an alternate function.
1175 Poweroff/Shutdown the system
1178 bool "read - Read binary data from a partition"
1180 Provides low-level access to the data in a partition.
1182 config CMD_REMOTEPROC
1184 depends on REMOTEPROC
1186 Support for Remote Processor control
1189 bool "sata - Access SATA subsystem"
1192 SATA (Serial Advanced Technology Attachment) is a serial bus
1193 standard for connecting to hard drives and other storage devices.
1194 This command provides information about attached devices and allows
1195 reading, writing and other operations.
1197 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1198 Attachment, where AT refers to an IBM AT (Advanced Technology)
1199 computer released in 1984.
1202 bool "saves - Save a file over serial in S-Record format"
1204 Provides a way to save a binary file using the Motorola S-Record
1205 format over the serial line.
1208 bool "scsi - Access to SCSI devices"
1211 This provides a 'scsi' command which provides access to SCSI (Small
1212 Computer System Interface) devices. The command provides a way to
1213 scan the bus, reset the bus, read and write data and get information
1217 bool "sdram - Print SDRAM configuration information"
1219 Provides information about attached SDRAM. This assumed that the
1220 SDRAM has an EEPROM with information that can be read using the
1221 I2C bus. This is only available on some boards.
1225 depends on DM_SPI_FLASH || SPI_FLASH
1226 default y if DM_SPI_FLASH
1231 bool "sf test - Allow testing of SPI flash"
1234 Provides a way to test that SPI flash is working correctly. The
1235 test is destructive, in that an area of SPI flash must be provided
1236 for the test to use. Performance information is also provided,
1237 measuring the performance of reading, writing and erasing in
1238 Mbps (Million Bits Per Second). This value should approximately
1239 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1240 everything is working properly.
1243 bool "sspi - Command to access spi device"
1246 SPI utility command.
1248 config DEFAULT_SPI_BUS
1249 int "default spi bus used by sspi command"
1253 config DEFAULT_SPI_MODE
1254 hex "default spi mode used by sspi command (see include/spi.h)"
1259 bool "tsi148 - Command to access tsi148 device"
1261 This provides various sub-commands to initialise and configure the
1262 Turndra tsi148 device. See the command help for full details.
1265 bool "Enable UFS - Universal Flash Subsystem commands"
1268 "This provides commands to initialise and configure universal flash
1272 bool "universe - Command to set up the Turndra Universe controller"
1274 This allows setting up the VMEbus provided by this controller.
1275 See the command help for full details.
1279 select HAVE_BLOCK_DEVICE
1285 select USB_FUNCTION_SDP
1287 Enables the command "sdp" which is used to have U-Boot emulating the
1288 Serial Download Protocol (SDP) via USB.
1292 depends on USB_FUNCTION_ROCKUSB
1294 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1295 read/write info, image to/from devices. This enable rockusb command
1296 support to communication with rockusb device. for more detail about
1297 this command, please read doc/README.rockusb.
1299 config CMD_USB_MASS_STORAGE
1300 bool "UMS usb mass storage"
1301 select USB_FUNCTION_MASS_STORAGE
1303 USB mass storage support
1310 VirtIO block device support
1316 This provides commands to control the watchdog timer devices.
1322 Enable the command "axi" for accessing AXI (Advanced eXtensible
1323 Interface) busses, a on-chip interconnect specification for managing
1324 functional blocks in SoC designs, which is also often used in designs
1325 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1329 menu "Shell scripting commands"
1335 Echo args to console
1341 Return true/false on integer compare.
1347 Run script from memory
1353 Evaluate boolean and math expressions and store the result in an env
1355 Also supports loading the value at a memory location into a variable.
1356 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1360 menu "Android support commands"
1362 config CMD_AB_SELECT
1365 depends on ANDROID_AB
1367 On Android devices with more than one boot slot (multiple copies of
1368 the kernel and system images) this provides a command to select which
1369 slot should be used to boot from and register the boot attempt. This
1370 is used by the new A/B update model where one slot is updated in the
1371 background while running from the other slot.
1378 bool "Network commands"
1388 bootp - boot image via network using BOOTP/TFTP protocol
1392 depends on CMD_BOOTP
1394 Boot image via network using DHCP/TFTP protocol
1396 config BOOTP_BOOTPATH
1397 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1399 depends on CMD_BOOTP
1401 Even though the config is called BOOTP_BOOTPATH, it stores the
1402 path in the variable 'rootpath'.
1405 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1407 depends on CMD_BOOTP
1409 The primary DNS server is stored as 'dnsip'. If two servers are
1410 returned, you must set BOOTP_DNS2 to store that second server IP
1414 bool "Store 'dnsip2' from BOOTP/DHCP server"
1415 depends on BOOTP_DNS
1417 If a DHCP client requests the DNS server IP from a DHCP server,
1418 it is possible that more than one DNS serverip is offered to the
1419 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1420 server IP will be stored in the additional environment
1421 variable "dnsip2". The first DNS serverip is always
1422 stored in the variable "dnsip", when BOOTP_DNS is defined.
1424 config BOOTP_GATEWAY
1425 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1427 depends on CMD_BOOTP
1429 config BOOTP_HOSTNAME
1430 bool "Request & store 'hostname' from BOOTP/DHCP server"
1432 depends on CMD_BOOTP
1434 The name may or may not be qualified with the local domain name.
1436 config BOOTP_PREFER_SERVERIP
1437 bool "serverip variable takes precedent over DHCP server IP."
1438 depends on CMD_BOOTP
1440 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1442 With this option enabled, the 'serverip' variable in the environment
1443 takes precedence over DHCP server IP and will only be set by the DHCP
1444 server if not already set in the environment.
1446 config BOOTP_SUBNETMASK
1447 bool "Request & store 'netmask' from BOOTP/DHCP server"
1449 depends on CMD_BOOTP
1451 config BOOTP_NTPSERVER
1452 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1453 depends on CMD_BOOTP
1458 Selecting this will allow capturing all Ethernet packets and store
1459 them in physical memory in a PCAP formated file,
1460 later to be analyzed by PCAP reader application (IE. WireShark).
1463 bool "Send PXE client arch to BOOTP/DHCP server"
1465 depends on CMD_BOOTP && CMD_PXE
1467 Supported for ARM, ARM64, and x86 for now.
1469 config BOOTP_PXE_CLIENTARCH
1471 depends on BOOTP_PXE
1472 default 0x16 if ARM64
1476 config BOOTP_VCI_STRING
1478 depends on CMD_BOOTP
1479 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1480 default "U-Boot.armv8" if ARM64
1481 default "U-Boot.arm" if ARM
1488 tftpboot - boot image via network using TFTP protocol
1492 depends on CMD_TFTPBOOT
1494 TFTP put command, for uploading files to a server
1498 depends on CMD_TFTPBOOT
1500 Act as a TFTP server and boot the first received file
1502 config NET_TFTP_VARS
1503 bool "Control TFTP timeout and count through environment"
1504 depends on CMD_TFTPBOOT
1507 If set, allows controlling the TFTP timeout through the
1508 environment variable tftptimeout, and the TFTP maximum
1509 timeout count through the variable tftptimeoutcountmax.
1510 If unset, timeout and maximum are hard-defined as 1 second
1511 and 10 timouts per TFTP transfer.
1516 Boot image via network using RARP/TFTP protocol
1522 Boot image via network using NFS protocol.
1528 If set, allows 802.3(clause 22) MII Management functions interface access
1529 The management interface specified in Clause 22 provides
1530 a simple, two signal, serial interface to connect a
1531 Station Management entity and a managed PHY for providing access
1532 to management parameters and services.
1533 The interface is referred to as the MII management interface.
1539 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1540 The MDIO interface is orthogonal to the MII interface and extends
1541 it by adding access to more registers through indirect addressing.
1546 Send ICMP ECHO_REQUEST to network host
1551 Perform CDP network configuration
1556 Synchronize RTC via network
1561 Lookup the IP of a hostname
1563 config CMD_LINK_LOCAL
1567 Acquire a network IP address using the link-local protocol
1574 Allow control of L2 Ethernet switch commands. These are supported
1575 by the vsc9953 Ethernet driver at present. Sub-commands allow
1576 operations such as enabling / disabling a port and
1577 viewing/maintaining the filtering database (FDB)
1583 Boot image via network using PXE protocol
1588 Wait for wake-on-lan Magic Packet
1592 menu "Misc commands"
1595 bool "Enable 'bmp' command"
1596 depends on LCD || DM_VIDEO || VIDEO
1598 This provides a way to obtain information about a BMP-format image
1599 and to display it. BMP (which presumably stands for BitMaP) is a
1600 file format defined by Microsoft which supports images of various
1601 depths, formats and compression methods. Headers on the file
1602 determine the formats used. This command can be used by first loading
1603 the image into RAM, then using this command to look at it or display
1606 config CMD_BOOTCOUNT
1608 depends on BOOTCOUNT_LIMIT
1610 Enable the bootcount command, which allows interrogation and
1611 reset of the bootcounter.
1614 bool "Enable board-specific commands"
1616 (deprecated: instead, please define a Kconfig option for each command)
1618 Some boards have board-specific commands which are only enabled
1619 during developemnt and need to be turned off for production. This
1620 option provides a way to control this. The commands that are enabled
1621 vary depending on the board.
1623 config CMD_BLOCK_CACHE
1624 bool "blkcache - control and stats for block cache"
1625 depends on BLOCK_CACHE
1626 default y if BLOCK_CACHE
1628 Enable the blkcache command, which can be used to control the
1629 operation of the cache functions.
1630 This is most useful when fine-tuning the operation of the cache
1631 during development, but also allows the cache to be disabled when
1632 it might hurt performance (e.g. when using the ums command).
1635 bool "icache or dcache"
1637 Enable the "icache" and "dcache" commands
1639 config CMD_CONITRACE
1640 bool "conitrace - trace console input codes"
1642 Enable the 'conitrace' command which displays the codes received
1643 from the console input as hexadecimal numbers.
1646 bool "Enable clear screen command 'cls'"
1647 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1650 Enable the 'cls' command which clears the screen contents
1651 on video frame buffer.
1654 bool "efidebug - display/configure UEFI environment"
1655 depends on EFI_LOADER
1656 select EFI_DEVICE_PATH_TO_TEXT
1659 Enable the 'efidebug' command which provides a subset of UEFI
1660 shell utility with simplified functionality. It will be useful
1661 particularly for managing boot parameters as well as examining
1662 various EFI status for debugging.
1664 config CMD_EXCEPTION
1665 bool "exception - raise exception"
1666 depends on ARM || RISCV || X86
1668 Enable the 'exception' command which allows to raise an exception.
1675 Enable the 'led' command which allows for control of LEDs supported
1676 by the board. The LEDs can be listed with 'led list' and controlled
1677 with led on/off/togle/blink. Any LED drivers can be controlled with
1678 this command, e.g. led_gpio.
1685 Enable the 'date' command for getting/setting the time/date in RTC
1691 Run commands and summarize execution time.
1694 bool "gettime - read elapsed time"
1696 Enable the 'gettime' command which reads the elapsed time since
1697 U-Boot started running. This shows the time in seconds and
1698 milliseconds. See also the 'bootstage' command which provides more
1699 flexibility for boot timing.
1706 Print bytes from the hardware random number generator.
1708 # TODO: rename to CMD_SLEEP
1713 Delay execution for some time
1716 bool "support for multiprocessor"
1718 This provides an option to brinup
1719 different processors in multiprocessor
1725 Access the system timer.
1731 This provides basic access to the U-Boot's sound support. The main
1732 feature is to play a beep.
1734 sound init - set up sound system
1735 sound play - play a sound
1741 Boot image via local extlinux.conf file
1747 This provides access to the QEMU firmware interface. The main
1748 feature is to allow easy loading of files passed to qemu-system
1749 via -kernel / -initrd
1751 source "cmd/mvebu/Kconfig"
1754 bool "terminal - provides a way to attach a serial terminal"
1756 Provides a 'cu'-like serial terminal command. This can be used to
1757 access other serial ports from the system console. The terminal
1758 is very simple with no special processing of characters. As with
1759 cu, you can press ~. (tilde followed by period) to exit.
1762 bool "uuid, guid - generation of unique IDs"
1765 This enables two commands:
1767 uuid - generate random Universally Unique Identifier
1768 guid - generate Globally Unique Identifier based on random UUID
1770 The two commands are very similar except for the endianness of the
1775 source "cmd/ti/Kconfig"
1777 config CMD_BOOTSTAGE
1778 bool "Enable the 'bootstage' command"
1779 depends on BOOTSTAGE
1781 Add a 'bootstage' command which supports printing a report
1782 and un/stashing of bootstage data.
1784 menu "Power commands"
1786 bool "Enable Driver Model PMIC command"
1789 This is the pmic command, based on a driver model pmic's API.
1790 Command features are unchanged:
1791 - list - list pmic devices
1792 - pmic dev <id> - show or [set] operating pmic device (NEW)
1793 - pmic dump - dump registers
1794 - pmic read address - read byte of register at address
1795 - pmic write address - write byte to register at address
1796 The only one change for this command is 'dev' subcommand.
1798 config CMD_REGULATOR
1799 bool "Enable Driver Model REGULATOR command"
1800 depends on DM_REGULATOR
1802 This command is based on driver model regulator's API.
1803 User interface features:
1804 - list - list regulator devices
1805 - regulator dev <id> - show or [set] operating regulator device
1806 - regulator info - print constraints info
1807 - regulator status - print operating status
1808 - regulator value <val] <-f> - print/[set] voltage value [uV]
1809 - regulator current <val> - print/[set] current value [uA]
1810 - regulator mode <id> - print/[set] operating mode id
1811 - regulator enable - enable the regulator output
1812 - regulator disable - disable the regulator output
1814 The '-f' (force) option can be used for set the value which exceeds
1815 the limits, which are found in device-tree and are kept in regulator's
1816 uclass platdata structure.
1820 menu "Security commands"
1822 bool "Enable the 'aes' command"
1825 This provides a means to encrypt and decrypt data using the AES
1826 (Advanced Encryption Standard). This algorithm uses a symetric key
1827 and is widely used as a streaming cipher. Different key lengths are
1828 supported by the algorithm but this command only supports 128 bits
1832 bool "Enable the 'blob' command"
1834 This is used with the Freescale secure boot mechanism.
1836 Freescale's SEC block has built-in Blob Protocol which provides
1837 a method for protecting user-defined data across system power
1838 cycles. SEC block protects data in a data structure called a Blob,
1839 which provides both confidentiality and integrity protection.
1841 Encapsulating data as a blob
1842 Each time that the Blob Protocol is used to protect data, a
1843 different randomly generated key is used to encrypt the data.
1844 This random key is itself encrypted using a key which is derived
1845 from SoC's non-volatile secret key and a 16 bit Key identifier.
1846 The resulting encrypted key along with encrypted data is called a
1847 blob. The non-volatile secure key is available for use only during
1850 During decapsulation, the reverse process is performed to get back
1854 blob enc - encapsulating data as a cryptgraphic blob
1855 blob dec - decapsulating cryptgraphic blob to get the data
1859 blob enc src dst len km
1861 Encapsulate and create blob of data $len bytes long
1862 at address $src and store the result at address $dst.
1863 $km is the 16 byte key modifier is also required for
1864 generation/use as key for cryptographic operation. Key
1865 modifier should be 16 byte long.
1867 blob dec src dst len km
1869 Decapsulate the blob of data at address $src and
1870 store result of $len byte at addr $dst.
1871 $km is the 16 byte key modifier is also required for
1872 generation/use as key for cryptographic operation. Key
1873 modifier should be 16 byte long.
1876 bool "Support 'hash' command"
1879 This provides a way to hash data in memory using various supported
1880 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1881 saved to memory or to an environment variable. It is also possible
1882 to verify a hash against data in memory.
1885 bool "Support the 'hvc' command"
1886 depends on ARM_SMCCC
1888 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1889 development and testing.
1892 bool "Support the 'smc' command"
1893 depends on ARM_SMCCC
1895 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1896 development and testing.
1902 Add -v option to verify data against a hash.
1912 bool "Enable the 'tpm' command"
1913 depends on TPM_V1 || TPM_V2
1914 select CMD_TPM_V1 if TPM_V1
1915 select CMD_TPM_V2 if TPM_V2
1917 This provides a means to talk to a TPM from the command line. A wide
1918 range of commands if provided - see 'tpm help' for details. The
1919 command requires a suitable TPM on your board and the correct driver
1925 bool "Enable the 'tpm test' command"
1928 This provides a a series of tests to confirm that the TPMv1.x is
1929 working correctly. The tests cover initialisation, non-volatile RAM,
1930 extend, global lock and checking that timing is within expectations.
1931 The tests pass correctly on Infineon TPMs but may need to be adjusted
1938 menu "Firmware commands"
1940 bool "Enable crosec command"
1944 Enable command-line access to the Chrome OS EC (Embedded
1945 Controller). This provides the 'crosec' command which has
1946 a number of sub-commands for performing EC tasks such as
1947 updating its flash, accessing a small saved context area
1948 and talking to the I2C bus behind the EC (if there is one).
1951 menu "Filesystem commands"
1953 bool "Enable the 'btrsubvol' command"
1956 This enables the 'btrsubvol' command to list subvolumes
1957 of a BTRFS filesystem. There are no special commands for
1958 listing BTRFS directories or loading BTRFS files - this
1959 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1960 when BTRFS is enabled (see FS_BTRFS).
1963 bool "Enable the 'cbfs' command"
1966 Define this to enable support for reading from a Coreboot
1967 filesystem. This is a ROM-based filesystem used for accessing files
1968 on systems that use coreboot as the first boot-loader and then load
1969 U-Boot to actually boot the Operating System. Available commands are
1970 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1973 bool "Enable the 'cramfs' command"
1974 depends on FS_CRAMFS
1976 This provides commands for dealing with CRAMFS (Compressed ROM
1977 filesystem). CRAMFS is useful when space is tight since files are
1978 compressed. Two commands are provided:
1980 cramfsls - lists files in a cramfs image
1981 cramfsload - loads a file from a cramfs image
1984 bool "ext2 command support"
1987 Enables EXT2 FS command
1990 bool "ext4 command support"
1993 Enables EXT4 FS command
1995 config CMD_EXT4_WRITE
1997 bool "ext4 write command support"
2000 Enables EXT4 FS write command
2003 bool "FAT command support"
2006 Support for the FAT fs
2008 config CMD_FS_GENERIC
2009 bool "filesystem commands"
2011 Enables filesystem commands (e.g. load, ls) that work for multiple
2015 bool "fsuuid command"
2017 Enables fsuuid command for filesystem UUID.
2020 bool "jffs2 command"
2023 Enables commands to support the JFFS2 (Journalling Flash File System
2024 version 2) filesystem. This enables fsload, ls and fsinfo which
2025 provide the ability to load files, list directories and obtain
2026 filesystem information.
2029 bool "MTD partition support"
2032 MTD partitioning tool support.
2033 It is strongly encouraged to avoid using this command
2034 anymore along with 'sf', 'nand', 'onenand'. One can still
2035 declare the partitions in the mtdparts environment variable
2036 but better use the MTD stack and the 'mtd' command instead.
2038 config CMD_MTDPARTS_SPREAD
2039 bool "Padd partition size to take account of bad blocks"
2040 depends on CMD_MTDPARTS
2042 This enables the 'spread' sub-command of the mtdparts command.
2043 This command will modify the existing mtdparts variable by increasing
2044 the size of the partitions such that 1) each partition's net size is
2045 at least as large as the size specified in the mtdparts variable and
2046 2) each partition starts on a good block.
2048 config CMD_MTDPARTS_SHOW_NET_SIZES
2049 bool "Show net size (w/o bad blocks) of partitions"
2050 depends on CMD_MTDPARTS
2052 Adds two columns to the printed partition table showing the
2053 effective usable size of a partition, if bad blocks are taken
2056 config MTDIDS_DEFAULT
2057 string "Default MTD IDs"
2058 depends on MTD || SPI_FLASH
2060 Defines a default MTD IDs list for use with MTD partitions in the
2061 Linux MTD command line partitions format.
2063 config MTDPARTS_DEFAULT
2064 string "Default MTD partition scheme"
2065 depends on MTD || SPI_FLASH
2067 Defines a default MTD partitioning scheme in the Linux MTD command
2068 line partitions format
2071 bool "reiser - Access to reiserfs filesystems"
2073 This provides two commands which operate on a resierfs filesystem,
2074 commonly used some years ago:
2076 reiserls - list files
2077 reiserload - load a file
2080 bool "yaffs2 - Access of YAFFS2 filesystem"
2084 This provides commands for accessing a YAFFS2 filesystem. Yet
2085 Another Flash Filesystem 2 is a filesystem designed specifically
2086 for NAND flash. It incorporates bad-block management and ensures
2087 that device writes are sequential regardless of filesystem
2091 bool "zfs - Access of ZFS filesystem"
2093 This provides commands to accessing a ZFS filesystem, commonly used
2094 on Solaris systems. Two sub-commands are provided:
2096 zfsls - list files in a directory
2097 zfsload - load a file
2099 See doc/README.zfs for more details.
2103 menu "Debug commands"
2108 The bedbug (emBEDded deBUGger) command provides debugging features
2109 for some PowerPC processors. For details please see the
2110 documentation in doc/README.bedbug.
2113 bool "diag - Board diagnostics"
2115 This command provides access to board diagnostic tests. These are
2116 called Power-on Self Tests (POST). The command allows listing of
2117 available tests and running either all the tests, or specific tests
2121 bool "irq - Show information about interrupts"
2122 depends on !ARM && !MIPS && !SH
2124 This enables two commands:
2126 interrupts - enable or disable interrupts
2127 irqinfo - print device-specific interrupt information
2130 bool "kgdb - Allow debugging of U-Boot with gdb"
2133 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2134 over a serial link for debugging purposes. This allows
2135 single-stepping, inspecting variables, etc. This is supported only
2136 on PowerPC at present.
2139 bool "log - Generation, control and access to logging"
2142 This provides access to logging features. It allows the output of
2143 log data to be controlled to a limited extent (setting up the default
2144 maximum log level for emitting of records). It also provides access
2145 to a command used for testing the log system.
2148 bool "trace - Support tracing of function calls and timing"
2150 Enables a command to control using of function tracing within
2151 U-Boot. This allows recording of call traces including timing
2152 information. The command can write data to memory for exporting
2153 for analysis (e.g. using bootchart). See doc/README.trace for full
2157 bool "avb - Android Verified Boot 2.0 operations"
2158 depends on AVB_VERIFY
2161 Enables a "avb" command to perform verification of partitions using
2162 Android Verified Boot 2.0 functionality. It includes such subcommands:
2163 avb init - initialize avb2 subsystem
2164 avb read_rb - read rollback index
2165 avb write_rb - write rollback index
2166 avb is_unlocked - check device lock state
2167 avb get_uuid - read and print uuid of a partition
2168 avb read_part - read data from partition
2169 avb read_part_hex - read data from partition and output to stdout
2170 avb write_part - write data to partition
2171 avb verify - run full verification chain
2175 tristate "Enable UBI - Unsorted block images commands"
2178 UBI is a software layer above MTD layer which admits use of LVM-like
2179 logical volumes on top of MTD devices, hides some complexities of
2180 flash chips like wear and bad blocks and provides some other useful
2181 capabilities. Please, consult the MTD web site for more details
2182 (www.linux-mtd.infradead.org). Activate this option if you want
2183 to use U-Boot UBI commands.
2184 It is also strongly encouraged to also enable CONFIG_MTD to get full
2187 config CMD_UBI_RENAME
2188 bool "Enable rename"
2192 Enable a "ubi" command to rename ubi volume:
2193 ubi rename <oldname> <newname>
2196 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2198 default y if CMD_UBI
2201 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob