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
34 config CMDLINE_PS_SUPPORT
35 bool "Enable support for changing the command prompt string at run-time"
36 depends on HUSH_PARSER
38 Only static string in the prompt is supported so far. The string is
39 obtained from environment variables PS1 and PS2.
42 bool "Enable auto complete using TAB"
46 Enable auto completion of commands using TAB.
49 bool "Enable long help messages"
53 Defined when you want long help messages included
54 Do not set this option when short of memory.
58 default "Zynq> " if ARCH_ZYNQ
59 default "ZynqMP> " if ARCH_ZYNQMP
62 This string is displayed in the command line to the left of the
65 config SYS_PROMPT_HUSH_PS2
66 string "Hush shell secondary prompt"
67 depends on HUSH_PARSER
70 This defines the secondary prompt string, which is
71 printed when the command interpreter needs more input
72 to complete a command. Usually "> ".
75 int "Maximum number arguments accepted by commands"
79 bool "Command execution tracer"
83 This option enables the possiblity to print all commands before
84 executing them and after all variables are evaluated (similar
85 to Bash's xtrace/'set -x' feature).
86 To enable the tracer a variable "xtrace" needs to be defined in
101 List and dump ACPI tables. ACPI (Advanced Configuration and Power
102 Interface) is used mostly on x86 for providing information to the
103 Operating System about devices in the system. The tables are set up
104 by the firmware, typically U-Boot but possibly an earlier firmware
105 module, if U-Boot is chain-loaded from something else. ACPI tables
106 can also include code, to perform hardware-specific tasks required
107 by the Operating Systems. This allows some amount of separation
108 between the firmware and OS, and is particularly useful when you
109 want to make hardware changes without the OS needing to be adjusted.
116 List non-identity virtual-physical memory mappings for 32-bit CPUs.
129 Print ".config" contents.
131 If this option is enabled, the ".config" file contents are embedded
132 in the U-Boot image and can be printed on the console by the "config"
133 command. This provides information of which options are enabled on
140 Print console devices and information.
146 Print information about available CPUs. This normally shows the
147 number of CPUs, type (e.g. manufacturer, architecture, product or
148 internal name) and clock frequency. Other information may be
149 available depending on the CPU driver.
155 Print GPL license text
160 Provides access to the Intel Power-Management Controller (PMC) so
161 that its state can be examined. This does not currently support
162 changing the state but it is still useful for debugging and seeing
171 config CMD_TLV_EEPROM
173 depends on I2C_EEPROM
175 Display and program the system EEPROM data block in ONIE Tlvinfo
176 format. TLV stands for Type-Length-Value.
178 config SPL_CMD_TLV_EEPROM
179 bool "tlv_eeprom for SPL"
180 depends on SPL_I2C_EEPROM
181 select SPL_DRIVERS_MISC
183 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
187 depends on RISCV_SMODE && SBI_V02
189 Display information about the SBI implementation.
199 Run the command stored in the environment "bootcmd", i.e.
200 "bootd" does the same thing as "run bootcmd".
206 Boot an application image from the memory.
208 config CMD_BOOTM_PRE_LOAD
209 bool "enable pre-load on bootm"
211 depends on IMAGE_PRE_LOAD
214 Enable support of stage pre-load for the bootm command.
215 This stage allow to check or modify the image provided
216 to the bootm command.
221 default y if BOOTSTD_FULL
223 Support listing available bootdevs (boot devices) which can provide an
224 OS to boot, as well as showing information about a particular one.
226 This command is not necessary for bootstd to work.
233 Support scanning for bootflows available with the bootdevs. The
234 bootflows can optionally be booted.
236 config CMD_BOOTFLOW_FULL
237 bool "bootflow - extract subcommands"
238 depends on BOOTSTD_FULL
239 default y if BOOTSTD_FULL
241 Add the ability to list the available bootflows, select one and obtain
242 information about it.
244 This command is not necessary for bootstd to work.
249 default y if BOOTSTD_FULL
251 Support listing available bootmethds (methods used to boot an
252 Operating System), as well as selecting the order that the bootmeths
255 This command is not necessary for bootstd to work.
258 bool "Support booting UEFI FIT images"
259 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
262 Support booting UEFI FIT images via the bootm command.
267 Boot the Linux zImage
271 depends on ARM64 || RISCV
274 Boot an AArch64 Linux Kernel image from memory.
277 bool "Support booting Linux OS images"
278 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
281 Support booting the Linux kernel directly via a command such as bootm
285 bool "Support booting NetBSD (non-EFI) loader images"
289 Support booting NetBSD via the bootm command.
291 config BOOTM_OPENRTOS
292 bool "Support booting OPENRTOS / FreeRTOS images"
295 Support booting OPENRTOS / FreeRTOS via the bootm command.
298 bool "Support booting Enea OSE images"
299 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
302 Support booting Enea OSE images via the bootm command.
305 bool "Support booting Plan9 OS images"
309 Support booting Plan9 images via the bootm command.
312 bool "Support booting RTEMS OS images"
316 Support booting RTEMS images via the bootm command.
319 bool "Support booting VxWorks OS images"
323 Support booting VxWorks images via the bootm command.
327 depends on EFI_LOADER
330 Boot an EFI image from memory.
332 config CMD_BOOTEFI_HELLO_COMPILE
333 bool "Compile a standard EFI hello world binary for testing"
334 depends on CMD_BOOTEFI && !CPU_V7M
337 This compiles a standard EFI hello world application with U-Boot so
338 that it can be used with the test/py testing framework. This is useful
339 for testing that EFI is working at a basic level, and for bringing
340 up EFI support on a new architecture.
342 No additional space will be required in the resulting U-Boot binary
343 when this option is enabled.
345 config CMD_BOOTEFI_HELLO
346 bool "Allow booting a standard EFI hello world for testing"
347 depends on CMD_BOOTEFI_HELLO_COMPILE
348 default y if CMD_BOOTEFI_SELFTEST
350 This adds a standard EFI hello world application to U-Boot so that
351 it can be used with the 'bootefi hello' command. This is useful
352 for testing that EFI is working at a basic level, and for bringing
353 up EFI support on a new architecture.
355 source lib/efi_selftest/Kconfig
362 Add an ANSI terminal boot menu command.
367 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
368 image into RAM, dump image structure information, etc. Those dtb/dtbo
369 files should be merged in one dtb further, which needs to be passed to
370 the kernel, as part of a boot process.
374 depends on ANDROID_BOOT_IMAGE
376 Android Boot Image manipulation commands. Allows one to extract
377 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
378 obtain corresponding meta-information from boot.img.
380 See doc/android/boot-image.rst for details.
383 bool "bootelf, bootvx"
387 Boot an ELF/vxWorks image from the memory.
390 bool "Flattened Device Tree utility commands"
394 Do FDT related setup before booting into the Operating System.
396 config SUPPORT_EXTENSION_SCAN
400 bool "Extension board management command"
402 depends on SUPPORT_EXTENSION_SCAN
404 Enables the "extension" command, which allows to detect
405 extension boards connected to the system, and apply
406 corresponding Device Tree overlays.
412 Start an application at a given address.
418 Run the command in the given environment variable.
424 Print header information for application image.
429 List all images found in flash
435 Extract a part of a multi-image.
438 bool "spl export - Export boot information for Falcon boot"
441 Falcon mode allows booting directly from SPL into an Operating
442 System such as Linux, thus skipping U-Boot proper. See
443 doc/README.falcon for full information about how to use this
446 config CMD_SPL_NAND_OFS
447 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
448 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
451 This provides the offset of the command line arguments for Linux
452 when booting from NAND in Falcon mode. See doc/README.falcon
453 for full information about how to use this option (and also see
454 board/gateworks/gw_ventana/README for an example).
456 config CMD_SPL_NOR_OFS
457 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
458 depends on CMD_SPL && SPL_NOR_SUPPORT
461 This provides the offset of the command line arguments or dtb for
462 Linux when booting from NOR in Falcon mode.
464 config CMD_SPL_WRITE_SIZE
465 hex "Size of argument area"
469 This provides the size of the command-line argument area in NAND
470 flash used by Falcon-mode boot. See the documentation until CMD_SPL
473 config CMD_THOR_DOWNLOAD
474 bool "thor - TIZEN 'thor' download"
477 Implements the 'thor' download protocol. This is a way of
478 downloading a software update over USB from an attached host.
479 There is no documentation about this within the U-Boot source code
480 but you should be able to find something on the interwebs.
483 bool "zboot - x86 boot command"
485 With x86 machines it is common to boot a bzImage file which
486 contains both a kernel and a setup.bin file. The latter includes
487 configuration information from the dark ages which x86 boards still
488 need to pick things out of.
490 Consider using FIT in preference to this since it supports directly
491 booting both 32- and 64-bit kernels, as well as secure boot.
492 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
496 menu "Environment commands"
499 bool "ask for env variable"
501 Ask for environment variable
519 Edit environment variable.
524 Allow for searching environment variables
530 Save all environment variables into the compiled-in persistent
535 depends on CMD_SAVEENV
537 Erase environment variables from the compiled-in persistent
540 config CMD_ENV_EXISTS
544 Check if a variable is defined in the environment for use in
547 config CMD_ENV_CALLBACK
548 bool "env callbacks - print callbacks and their associated variables"
550 Some environment variable have callbacks defined by
551 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
552 For example changing "baudrate" adjust the serial baud rate. This
553 command lists the currently defined callbacks.
556 bool "env flags -print variables that have non-default flags"
558 Some environment variables have special flags that control their
559 behaviour. For example, serial# can only be written once and cannot
560 be deleted. This command shows the variables that have special
563 config CMD_NVEDIT_EFI
564 bool "env [set|print] -e - set/print UEFI variables"
565 depends on EFI_LOADER
568 UEFI variables are encoded as some form of U-Boot variables.
569 If enabled, we are allowed to set/print UEFI variables using
570 "env" command with "-e" option without knowing details.
572 config CMD_NVEDIT_INDIRECT
573 bool "env indirect - Sets environment value from another"
575 config CMD_NVEDIT_INFO
576 bool "env info - print or evaluate environment information"
578 Print environment information:
579 - env_valid : is environment valid
580 - env_ready : is environment imported into hash table
581 - env_use_default : is default environment used
583 This command can be optionally used for evaluation in scripts:
584 [-d] : evaluate whether default environment is used
585 [-p] : evaluate whether environment can be persisted
587 The result of multiple evaluations will be combined with AND.
589 config CMD_NVEDIT_LOAD
592 Load all environment variables from the compiled-in persistent
595 config CMD_NVEDIT_SELECT
598 Select the compiled-in persistent storage of environment variables.
602 menu "Memory commands"
607 Compute binary operations (xor, or, and) of byte arrays of arbitrary
608 size from memory and store the result in memory or the environment.
612 default y if BLOBLIST
614 Show information about the bloblist, a collection of binary blobs
615 held in memory that persist between SPL and U-Boot. In the case of
616 x86 devices the bloblist can be used to hold ACPI tables so that they
617 remain available in memory.
630 Add -v option to verify data against a crc32 checksum.
633 bool "eeprom - EEPROM subsystem"
635 (deprecated, needs conversion to driver model)
636 Provides commands to read and write EEPROM (Electrically Erasable
637 Programmable Read Only Memory) chips that are connected over an
640 config CMD_EEPROM_LAYOUT
641 bool "Enable layout-aware eeprom commands"
642 depends on CMD_EEPROM
644 (deprecated, needs conversion to driver model)
645 When enabled, additional eeprom sub-commands become available.
647 eeprom print - prints the contents of the eeprom in a human-readable
648 way (eeprom layout fields, and data formatted to be fit for human
651 eeprom update - allows user to update eeprom fields by specifying
652 the field name, and providing the new data in a human readable format
653 (same format as displayed by the eeprom print command).
655 Both commands can either auto detect the layout, or be told which
659 __weak int parse_layout_version(char *str)
660 - override to provide your own layout name parsing
661 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
663 - override to setup the layout metadata based on the version
664 __weak int eeprom_layout_detect(unsigned char *data)
665 - override to provide your own algorithm for detecting layout
668 - contains various printing and updating functions for common
669 types of eeprom fields. Can be used for defining
672 config EEPROM_LAYOUT_HELP_STRING
673 string "Tells user what layout names are supported"
674 depends on CMD_EEPROM_LAYOUT
675 default "<not defined>"
677 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
680 config SYS_I2C_EEPROM_BUS
681 int "I2C bus of the EEPROM device."
682 depends on CMD_EEPROM
685 config SYS_I2C_EEPROM_ADDR_LEN
686 int "Length in bytes of the EEPROM memory array address"
687 depends on CMD_EEPROM || ID_EEPROM
691 Note: This is NOT the chip address length!
693 config SYS_EEPROM_SIZE
694 depends on CMD_EEPROM
695 int "Size in bytes of the EEPROM device"
698 config SYS_EEPROM_PAGE_WRITE_BITS
699 int "Number of bits used to address bytes in a single page"
700 depends on CMD_EEPROM
703 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
704 A 64 byte page, for example would require six bits.
706 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
707 int "Number of milliseconds to delay between page writes"
708 depends on CMD_EEPROM || CMD_I2C
714 Infinite write loop on address range
720 Compute MD5 checksum.
724 depends on CMD_MD5SUM
726 Add -v option to verify data against an MD5 checksum.
731 Display memory information.
734 bool "md, mm, nm, mw, cp, cmp, base, loop"
739 mm - memory modify (auto-incrementing address)
740 nm - memory modify (constant address)
741 mw - memory write (fill)
744 base - print or set address offset
745 loop - initialize loop on address range
747 config CMD_MEM_SEARCH
748 bool "ms - Memory search"
750 Memory-search command
752 This allows searching through a region of memory looking for hex
753 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
754 support it). It is also possible to search for a string. The
755 command accepts a memory range and a list of values to search for.
756 The values need to appear in memory in the same order they are given
757 in the command. At most 10 matches can be returned at a time, but
758 pressing return will show the next 10 matches. Environment variables
759 are set for use with scripting (memmatches, memaddr, mempos).
762 bool "Enable cyclic md/mw commands"
763 depends on CMD_MEMORY
765 Add the "mdc" and "mwc" memory commands. These are cyclic
770 This command will print 4 bytes (10,11,12,13) each 500 ms.
772 => mwc.l 100 12345678 10
773 This command will write 12345678 to address 100 all 10 ms.
778 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
780 random - fill memory with random data
785 Simple RAM read/write test.
789 config SYS_ALT_MEMTEST
790 bool "Alternative test"
792 Use a more complete alternative memory test.
796 config SYS_ALT_MEMTEST_BITFLIP
800 The alternative memory test includes bitflip test since 2020.07.
801 The bitflip test significantly increases the overall test time.
802 Bitflip test can optionally be disabled here.
806 config SYS_MEMTEST_START
807 hex "default start address for mtest"
810 This is the default start address for mtest for simple read/write
811 test. If no arguments are given to mtest, default address is used
814 config SYS_MEMTEST_END
815 hex "default end address for mtest"
818 This is the default end address for mtest for simple read/write
819 test. If no arguments are given to mtest, default address is used
828 Compute SHA1 checksum.
830 config SHA1SUM_VERIFY
832 depends on CMD_SHA1SUM
834 Add -v option to verify data against a SHA1 checksum.
837 bool "strings - display strings in memory"
839 This works similarly to the Unix 'strings' command except that it
840 works with a memory range. String of printable characters found
841 within the range are displayed. The minimum number of characters
842 for a sequence to be considered a string can be provided.
846 menu "Compression commands"
850 default y if CMD_BOOTI
853 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
858 default y if CMD_BOOTI
861 Support decompressing an LZ4 image from memory region.
865 default y if CMD_BOOTI
868 Uncompress a zip-compressed memory region.
872 select GZIP_COMPRESSED
874 Compress a memory region with zlib deflate method.
878 menu "Device access commands"
881 #depends on FLASH_CFI_DRIVER
884 ARM Ltd reference designs flash partition access
887 bool "adc - Access Analog to Digital Converters info and data"
889 depends on DM_REGULATOR
891 Shows ADC device info and permit printing one-shot analog converted
892 data from a named Analog to Digital Converter.
897 depends on PARTITIONS
899 Read/modify/write the fields of Bootloader Control Block, usually
900 stored on the flash "misc" partition with its structure defined in:
901 https://android.googlesource.com/platform/bootable/recovery/+/master/
902 bootloader_message/include/bootloader_message/bootloader_message.h
904 Some real-life use-cases include (but are not limited to):
905 - Determine the "boot reason" (and act accordingly):
906 https://source.android.com/devices/bootloader/boot-reason
907 - Get/pass a list of commands from/to recovery:
908 https://android.googlesource.com/platform/bootable/recovery
909 - Inspect/dump the contents of the BCB fields
912 bool "bind/unbind - Bind or unbind a device to/from a driver"
915 Bind or unbind a device to/from a driver from the command line.
916 This is useful in situations where a device may be handled by several
917 drivers. For example, this can be used to bind a UDC to the usb ether
918 gadget driver from the command line.
921 bool "clk - Show clock frequencies"
924 Shows clock frequences by calling a sock_clk_dump() hook function.
925 This is depreated in favour of using the CLK uclass and accessing
926 clock values from associated drivers. However currently no command
930 bool "demo - Demonstration commands for driver model"
933 Provides a 'demo' command which can be used to play around with
934 driver model. To use this properly you will need to enable one or
935 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
936 Otherwise you will always get an empty list of devices. The demo
937 devices are defined in the sandbox device tree, so the easiest
938 option is to use sandbox and pass the -d point to sandbox's
945 Enables the command "dfu" which is used to have U-Boot create a DFU
946 class device via USB. This command requires that the "dfu_alt_info"
947 environment variable be set and define the alt settings to expose to
951 bool "dm - Access to driver model information"
954 Provides access to driver model data structures and information,
955 such as a list of devices, list of uclasses and the state of each
956 device (e.g. activated). This is not required for operation, but
957 can be useful to see the state of driver model for debugging or
961 bool "fastboot - Android fastboot support"
964 This enables the command "fastboot" which enables the Android
965 fastboot mode for the platform. Fastboot is a protocol for
966 downloading images, flashing and device control used on
967 Android devices. Fastboot requires either the network stack
968 enabled or support for acting as a USB device.
970 See doc/android/fastboot.rst for more information.
973 bool "flinfo, erase, protect"
975 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
978 flinfo - print FLASH memory information
980 protect - enable or disable FLASH write protection
989 config CMD_FPGA_LOADBP
990 bool "fpga loadbp - load partial bitstream (Xilinx only)"
993 Supports loading an FPGA device from a bitstream buffer containing
996 config CMD_FPGA_LOADFS
997 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
1000 Supports loading an FPGA device from a FAT filesystem.
1002 config CMD_FPGA_LOADMK
1003 bool "fpga loadmk - load bitstream from image"
1006 Supports loading an FPGA device from a image generated by mkimage.
1008 config CMD_FPGA_LOADP
1009 bool "fpga loadp - load partial bitstream"
1012 Supports loading an FPGA device from a bitstream buffer containing
1013 a partial bitstream.
1015 config CMD_FPGA_LOAD_SECURE
1016 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1019 Enables the fpga loads command which is used to load secure
1020 (authenticated or encrypted or both) bitstreams on to FPGA.
1023 bool "fpgad - dump FPGA registers"
1025 (legacy, needs conversion to driver model)
1026 Provides a way to dump FPGA registers by calling the board-specific
1027 fpga_get_reg() function. This functions similarly to the 'md'
1031 bool "fuse - support for the fuse subssystem"
1033 (deprecated - needs conversion to driver model)
1034 This allows reading, sensing, programming or overriding fuses
1035 which control the behaviour of the device. The command uses the
1043 config CMD_GPIO_READ
1044 bool "gpio read - save GPIO value to variable"
1047 Enables the 'gpio read' command that saves the value
1048 of a GPIO pin to a variable.
1054 Control PWM channels, this allows invert/config/enable/disable PWM channels.
1057 bool "GPT (GUID Partition Table) command"
1058 select EFI_PARTITION
1059 select HAVE_BLOCK_DEVICE
1060 select PARTITION_UUIDS
1063 Enable the 'gpt' command to ready and write GPT style partition
1067 bool "GPT Random UUID generation"
1070 Enable the generation of partitions with random UUIDs if none
1073 config CMD_GPT_RENAME
1074 bool "GPT partition renaming commands"
1077 Enables the 'gpt' command to interchange names on two GPT
1078 partitions via the 'gpt swap' command or to rename single
1079 partitions via the 'rename' command.
1082 bool "ide - Support for IDE drivers"
1085 Provides an 'ide' command which allows accessing the IDE drive,
1086 resetting the IDE interface, printing the partition table and
1087 geting device info. It also enables the 'diskboot' command which
1088 permits booting from an IDE drive.
1091 bool "io - Support for performing I/O accesses"
1093 Provides an 'iod' command to display I/O space and an 'iow' command
1094 to write values to the I/O space. This can be useful for manually
1095 checking the state of devices during boot when debugging device
1099 bool "iotrace - Support for tracing I/O activity"
1101 Provides an 'iotrace' command which supports recording I/O reads and
1102 writes in a trace buffer in memory . It also maintains a checksum
1103 of the trace records (even if space is exhausted) so that the
1104 sequence of I/O accesses can be verified.
1106 When debugging drivers it is useful to see what I/O accesses were
1107 done and in what order.
1109 Even if the individual accesses are of little interest it can be
1110 useful to verify that the access pattern is consistent each time
1111 an operation is performed. In this case a checksum can be used to
1112 characterise the operation of a driver. The checksum can be compared
1113 across different runs of the operation to verify that the driver is
1116 In particular, when performing major refactoring of the driver, where
1117 the access pattern should not change, the checksum provides assurance
1118 that the refactoring work has not broken the driver.
1120 This works by sneaking into the io.h heder for an architecture and
1121 redirecting I/O accesses through iotrace's tracing mechanism.
1123 For now no commands are provided to examine the trace buffer. The
1124 format is fairly simple, so 'md' is a reasonable substitute.
1126 Note: The checksum feature is only useful for I/O regions where the
1127 contents do not change outside of software control. Where this is not
1128 suitable you can fall back to manually comparing the addresses. It
1129 might be useful to enhance tracing to only checksum the accesses and
1130 not the data read/written.
1140 bool "w1 - Support for Dallas 1-Wire protocol"
1142 Dallas 1-wire protocol support
1148 Load a binary file over serial line.
1154 Load an S-Record file over serial line
1158 bool "lsblk - list block drivers and devices"
1160 Print list of available block device drivers, and for each, the list
1161 of known block devices.
1164 bool "MBR (Master Boot Record) command"
1165 select DOS_PARTITION
1166 select HAVE_BLOCK_DEVICE
1168 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1169 style partition tables.
1175 Enable the command "misc" for accessing miscellaneous devices with
1176 a MISC uclass driver. The command provides listing all MISC devices
1177 as well as read and write functionalities via their drivers.
1183 MMC memory mapped support.
1187 config CMD_BKOPS_ENABLE
1188 bool "mmc bkops enable"
1191 Enable command for setting manual background operations handshake
1192 on a eMMC device. The feature is optionally available on eMMC devices
1193 conforming to standard >= 4.41.
1196 bool "Enable support for RPMB in the mmc command"
1197 depends on SUPPORT_EMMC_RPMB
1199 Enable the commands for reading, writing and programming the
1200 key for the Replay Protection Memory Block partition in eMMC.
1202 config CMD_MMC_SWRITE
1204 depends on MMC_WRITE
1207 Enable support for the "mmc swrite" command to write Android sparse
1216 Enable storage cloning over block devices, useful for
1217 initial flashing by external block device without network
1220 config CMD_OPTEE_RPMB
1221 bool "Enable read/write support on RPMB via OPTEE"
1222 depends on SUPPORT_EMMC_RPMB && OPTEE
1224 Enable the commands for reading, writing persistent named values
1225 in the Replay Protection Memory Block partition in eMMC by
1226 using Persistent Objects in OPTEE
1231 select MTD_PARTITIONS
1233 MTD commands support.
1237 depends on MULTIPLEXER
1239 List, select, and deselect mux controllers on the fly.
1243 default y if NAND_SUNXI
1244 depends on MTD_RAW_NAND
1249 config CMD_NAND_TRIMFFS
1250 bool "nand write.trimffs"
1251 default y if ARCH_SUNXI
1253 Allows one to skip empty pages when flashing something on a NAND.
1255 config CMD_NAND_LOCK_UNLOCK
1256 bool "nand lock/unlock"
1258 NAND locking support.
1260 config CMD_NAND_TORTURE
1263 NAND torture support.
1272 NVM Express device support
1275 bool "onenand - access to onenand device"
1278 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1279 various useful features. This command allows reading, writing,
1280 and erasing blocks. It allso provides a way to show and change
1281 bad blocks, and test the device.
1286 Enable the 'osd' command which allows to query information from and
1287 write text data to a on-screen display (OSD) device; a virtual device
1288 associated with a display capable of displaying a text overlay on the
1289 display it's associated with..
1293 depends on PARTITIONS
1294 select HAVE_BLOCK_DEVICE
1295 select PARTITION_UUIDS
1297 Read and display information about the partition table on
1301 bool "pci - Access PCI devices"
1303 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1304 used on some devices to allow the CPU to communicate with its
1305 peripherals. Sub-commands allow bus enumeration, displaying and
1306 changing configuration space and a few other features.
1309 bool "pinmux - show pins muxing"
1311 default y if PINCTRL
1313 Parse all available pin-controllers and show pins muxing. This
1314 is useful for debug purpoer to check the pin muxing and to know if
1315 a pin is configured as a GPIO or as an alternate function.
1320 Poweroff/Shutdown the system
1323 bool "read - Read binary data from a partition"
1325 Provides low-level access to the data in a partition.
1327 config CMD_REMOTEPROC
1329 depends on REMOTEPROC
1331 Support for Remote Processor control
1334 bool "sata - Access SATA subsystem"
1337 SATA (Serial Advanced Technology Attachment) is a serial bus
1338 standard for connecting to hard drives and other storage devices.
1339 This command provides information about attached devices and allows
1340 reading, writing and other operations.
1342 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1343 Attachment, where AT refers to an IBM AT (Advanced Technology)
1344 computer released in 1984.
1347 bool "saves - Save a file over serial in S-Record format"
1349 Provides a way to save a binary file using the Motorola S-Record
1350 format over the serial line.
1353 bool "scsi - Access to SCSI devices"
1356 This provides a 'scsi' command which provides access to SCSI (Small
1357 Computer System Interface) devices. The command provides a way to
1358 scan the bus, reset the bus, read and write data and get information
1362 bool "sdram - Print SDRAM configuration information"
1364 Provides information about attached SDRAM. This assumed that the
1365 SDRAM has an EEPROM with information that can be read using the
1366 I2C bus. This is only available on some boards.
1370 depends on DM_SPI_FLASH || SPI_FLASH
1371 default y if DM_SPI_FLASH
1376 bool "sf test - Allow testing of SPI flash"
1379 Provides a way to test that SPI flash is working correctly. The
1380 test is destructive, in that an area of SPI flash must be provided
1381 for the test to use. Performance information is also provided,
1382 measuring the performance of reading, writing and erasing in
1383 Mbps (Million Bits Per Second). This value should approximately
1384 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1385 everything is working properly.
1388 bool "sspi - Command to access spi device"
1391 SPI utility command.
1393 config DEFAULT_SPI_BUS
1394 int "default spi bus used by sspi command"
1398 config DEFAULT_SPI_MODE
1399 hex "default spi mode used by sspi command (see include/spi.h)"
1404 bool "tsi148 - Command to access tsi148 device"
1406 This provides various sub-commands to initialise and configure the
1407 Turndra tsi148 device. See the command help for full details.
1410 bool "Enable UFS - Universal Flash Subsystem commands"
1413 "This provides commands to initialise and configure universal flash
1417 bool "universe - Command to set up the Turndra Universe controller"
1419 This allows setting up the VMEbus provided by this controller.
1420 See the command help for full details.
1425 select HAVE_BLOCK_DEVICE
1431 select USB_FUNCTION_SDP
1433 Enables the command "sdp" which is used to have U-Boot emulating the
1434 Serial Download Protocol (SDP) via USB.
1438 depends on USB_FUNCTION_ROCKUSB
1440 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1441 read/write info, image to/from devices. This enable rockusb command
1442 support to communication with rockusb device. for more detail about
1443 this command, please read doc/README.rockusb.
1445 config CMD_USB_MASS_STORAGE
1446 bool "UMS usb mass storage"
1447 depends on USB_GADGET_DOWNLOAD
1448 select USB_FUNCTION_MASS_STORAGE
1449 depends on BLK && USB_GADGET
1451 Enables the command "ums" and the USB mass storage support to the
1452 export a block device: U-Boot, the USB device, acts as a simple
1453 external hard drive plugged on the host USB port.
1456 bool "Xen para-virtualized block device"
1460 Xen para-virtualized block device support
1465 depends on HAVE_BLOCK_DEVICE
1468 VirtIO block device support
1474 This provides commands to control the watchdog timer devices.
1480 Enable the command "axi" for accessing AXI (Advanced eXtensible
1481 Interface) busses, a on-chip interconnect specification for managing
1482 functional blocks in SoC designs, which is also often used in designs
1483 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1487 menu "Shell scripting commands"
1493 Echo args to console
1499 Return true/false on integer compare.
1505 Run script from memory
1511 Evaluate boolean and math expressions and store the result in an env
1513 Also supports loading the value at a memory location into a variable.
1514 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1516 config CMD_SETEXPR_FMT
1518 depends on CMD_SETEXPR
1520 Evaluate format string expression and store result in an environment
1525 menu "Android support commands"
1527 config CMD_AB_SELECT
1529 depends on ANDROID_AB
1531 On Android devices with more than one boot slot (multiple copies of
1532 the kernel and system images) this provides a command to select which
1533 slot should be used to boot from and register the boot attempt. This
1534 is used by the new A/B update model where one slot is updated in the
1535 background while running from the other slot.
1542 bool "Network commands"
1552 bootp - boot image via network using BOOTP/TFTP protocol
1556 depends on CMD_BOOTP
1558 Boot image via network using DHCP/TFTP protocol
1560 config BOOTP_MAY_FAIL
1561 bool "Allow for the BOOTP/DHCP server to not be found"
1562 depends on CMD_BOOTP
1564 If the DHCP server is not found after the configured retry count, the
1565 call will fail instead of starting over. This can be used to fail
1566 over to Link-local IP address configuration if the DHCP server is not
1569 config BOOTP_BOOTPATH
1570 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1572 depends on CMD_BOOTP
1574 Even though the config is called BOOTP_BOOTPATH, it stores the
1575 path in the variable 'rootpath'.
1577 config BOOTP_VENDOREX
1578 bool "Support vendor extensions from BOOTP/DHCP server"
1579 depends on CMD_BOOTP
1581 config BOOTP_BOOTFILESIZE
1582 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1583 depends on CMD_BOOTP
1586 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1588 depends on CMD_BOOTP
1590 The primary DNS server is stored as 'dnsip'. If two servers are
1591 returned, you must set BOOTP_DNS2 to store that second server IP
1595 bool "Store 'dnsip2' from BOOTP/DHCP server"
1596 depends on BOOTP_DNS
1598 If a DHCP client requests the DNS server IP from a DHCP server,
1599 it is possible that more than one DNS serverip is offered to the
1600 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1601 server IP will be stored in the additional environment
1602 variable "dnsip2". The first DNS serverip is always
1603 stored in the variable "dnsip", when BOOTP_DNS is defined.
1605 config BOOTP_GATEWAY
1606 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1608 depends on CMD_BOOTP
1610 config BOOTP_HOSTNAME
1611 bool "Request & store 'hostname' from BOOTP/DHCP server"
1613 depends on CMD_BOOTP
1615 The name may or may not be qualified with the local domain name.
1617 config BOOTP_PREFER_SERVERIP
1618 bool "serverip variable takes precedent over DHCP server IP."
1619 depends on CMD_BOOTP
1621 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1623 With this option enabled, the 'serverip' variable in the environment
1624 takes precedence over DHCP server IP and will only be set by the DHCP
1625 server if not already set in the environment.
1627 config BOOTP_SUBNETMASK
1628 bool "Request & store 'netmask' from BOOTP/DHCP server"
1630 depends on CMD_BOOTP
1632 config BOOTP_NISDOMAIN
1633 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1634 depends on CMD_BOOTP
1636 config BOOTP_NTPSERVER
1637 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1638 depends on CMD_BOOTP
1640 config BOOTP_TIMEOFFSET
1641 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1642 depends on CMD_BOOTP && CMD_SNTP
1647 Selecting this will allow capturing all Ethernet packets and store
1648 them in physical memory in a PCAP formated file,
1649 later to be analyzed by PCAP reader application (IE. WireShark).
1652 bool "Send PXE client arch to BOOTP/DHCP server"
1654 depends on CMD_BOOTP && CMD_PXE
1656 Supported for ARM, ARM64, and x86 for now.
1658 config BOOTP_PXE_CLIENTARCH
1660 depends on BOOTP_PXE
1661 default 0x16 if ARM64
1665 config BOOTP_VCI_STRING
1667 depends on CMD_BOOTP
1668 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1669 default "U-Boot.armv8" if ARM64
1670 default "U-Boot.arm" if ARM
1677 tftpboot - boot image via network using TFTP protocol
1681 depends on CMD_TFTPBOOT
1683 TFTP put command, for uploading files to a server
1687 depends on CMD_TFTPBOOT
1689 Act as a TFTP server and boot the first received file
1691 config NET_TFTP_VARS
1692 bool "Control TFTP timeout and count through environment"
1693 depends on CMD_TFTPBOOT
1696 If set, allows controlling the TFTP timeout through the
1697 environment variable tftptimeout, and the TFTP maximum
1698 timeout count through the variable tftptimeoutcountmax.
1699 If unset, timeout and maximum are hard-defined as 1 second
1700 and 10 timouts per TFTP transfer.
1705 Boot image via network using RARP/TFTP protocol
1711 Boot image via network using NFS protocol.
1714 int "Timeout in milliseconds for NFS mounts"
1718 Timeout in milliseconds used in NFS protocol. If you encounter
1719 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1726 If set, allows 802.3(clause 22) MII Management functions interface access
1727 The management interface specified in Clause 22 provides
1728 a simple, two signal, serial interface to connect a
1729 Station Management entity and a managed PHY for providing access
1730 to management parameters and services.
1731 The interface is referred to as the MII management interface.
1734 bool "Call mii_init() in the mii command"
1735 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1741 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1742 The MDIO interface is orthogonal to the MII interface and extends
1743 it by adding access to more registers through indirect addressing.
1748 Send ICMP ECHO_REQUEST to network host
1753 Perform CDP network configuration
1759 Synchronize RTC via network
1764 Lookup the IP of a hostname
1766 config CMD_LINK_LOCAL
1770 Acquire a network IP address using the link-local protocol
1777 Allow control of L2 Ethernet switch commands. These are supported
1778 by the vsc9953 Ethernet driver at present. Sub-commands allow
1779 operations such as enabling / disabling a port and
1780 viewing/maintaining the filtering database (FDB)
1786 Boot image via network using PXE protocol
1791 Wait for wake-on-lan Magic Packet
1795 menu "Misc commands"
1798 bool "Enable 'bmp' command"
1799 depends on LCD || DM_VIDEO || VIDEO
1801 This provides a way to obtain information about a BMP-format image
1802 and to display it. BMP (which presumably stands for BitMaP) is a
1803 file format defined by Microsoft which supports images of various
1804 depths, formats and compression methods. Headers on the file
1805 determine the formats used. This command can be used by first loading
1806 the image into RAM, then using this command to look at it or display
1809 config CMD_BOOTCOUNT
1811 depends on BOOTCOUNT_LIMIT
1813 Enable the bootcount command, which allows interrogation and
1814 reset of the bootcounter.
1817 bool "Enable board-specific commands"
1819 (deprecated: instead, please define a Kconfig option for each command)
1821 Some boards have board-specific commands which are only enabled
1822 during developemnt and need to be turned off for production. This
1823 option provides a way to control this. The commands that are enabled
1824 vary depending on the board.
1826 config CMD_BLOCK_CACHE
1827 bool "blkcache - control and stats for block cache"
1828 depends on BLOCK_CACHE
1829 default y if BLOCK_CACHE
1831 Enable the blkcache command, which can be used to control the
1832 operation of the cache functions.
1833 This is most useful when fine-tuning the operation of the cache
1834 during development, but also allows the cache to be disabled when
1835 it might hurt performance (e.g. when using the ums command).
1842 Enable the 'button' command which allows to get the status of
1843 buttons supported by the board. The buttonss can be listed with
1844 'button list' and state can be known with 'button <label>'.
1845 Any button drivers can be controlled with this command, e.g.
1849 bool "icache or dcache"
1851 Enable the "icache" and "dcache" commands
1853 config CMD_CONITRACE
1854 bool "conitrace - trace console input codes"
1856 Enable the 'conitrace' command which displays the codes received
1857 from the console input as hexadecimal numbers.
1860 bool "Enable clear screen command 'cls'"
1861 depends on DM_VIDEO || LCD || VIDEO
1864 Enable the 'cls' command which clears the screen contents
1865 on video frame buffer.
1868 bool "efidebug - display/configure UEFI environment"
1869 depends on EFI_LOADER
1870 select EFI_DEVICE_PATH_TO_TEXT
1872 Enable the 'efidebug' command which provides a subset of UEFI
1873 shell utility with simplified functionality. It will be useful
1874 particularly for managing boot parameters as well as examining
1875 various EFI status for debugging.
1877 config CMD_EXCEPTION
1878 bool "exception - raise exception"
1879 depends on ARM || RISCV || SANDBOX || X86
1881 Enable the 'exception' command which allows to raise an exception.
1888 Enable the 'led' command which allows for control of LEDs supported
1889 by the board. The LEDs can be listed with 'led list' and controlled
1890 with led on/off/togle/blink. Any LED drivers can be controlled with
1891 this command, e.g. led_gpio.
1898 Enable the 'date' command for getting/setting the time/date in RTC
1905 Enable the 'rtc' command for low-level access to RTC devices.
1910 Run commands and summarize execution time.
1913 bool "gettime - read elapsed time"
1915 Enable the 'gettime' command which reads the elapsed time since
1916 U-Boot started running. This shows the time in seconds and
1917 milliseconds. See also the 'bootstage' command which provides more
1918 flexibility for boot timing.
1925 Print bytes from the hardware random number generator.
1927 config CMD_KASLRSEED
1931 Set the kaslr-seed in the chosen node with entropy provided by a
1932 hardware random number generator.
1938 Delay execution for some time
1941 bool "support for multiprocessor commands"
1945 This enables commands to bringup different processors
1946 in multiprocessor cases.
1951 Access the system timer.
1957 This provides basic access to the U-Boot's sound support. The main
1958 feature is to play a beep.
1960 sound init - set up sound system
1961 sound play - play a sound
1967 Boot image via local extlinux.conf file
1973 This provides access to the QEMU firmware interface. The main
1974 feature is to allow easy loading of files passed to qemu-system
1975 via -kernel / -initrd
1980 This provides access to Linux PStore with Rammoops backend. The main
1981 feature is to allow to display or save PStore records.
1983 See doc/pstore.rst for more information.
1987 config CMD_PSTORE_MEM_ADDR
1988 hex "Memory Address"
1989 depends on CMD_PSTORE
1991 Base addr used for PStore ramoops memory, should be identical to
1992 ramoops.mem_address parameter used by kernel
1994 config CMD_PSTORE_MEM_SIZE
1996 depends on CMD_PSTORE
1999 Size of PStore ramoops memory, should be identical to ramoops.mem_size
2000 parameter used by kernel, a power of 2 and larger than the sum of the
2003 config CMD_PSTORE_RECORD_SIZE
2004 hex "Dump record size"
2005 depends on CMD_PSTORE
2008 Size of each dump done on oops/panic, should be identical to
2009 ramoops.record_size parameter used by kernel and a power of 2
2012 config CMD_PSTORE_CONSOLE_SIZE
2013 hex "Kernel console log size"
2014 depends on CMD_PSTORE
2017 Size of kernel console log, should be identical to
2018 ramoops.console_size parameter used by kernel and a power of 2
2021 config CMD_PSTORE_FTRACE_SIZE
2022 hex "FTrace log size"
2023 depends on CMD_PSTORE
2026 Size of ftrace log, should be identical to ramoops.ftrace_size
2027 parameter used by kernel and a power of 2
2029 config CMD_PSTORE_PMSG_SIZE
2030 hex "User space message log size"
2031 depends on CMD_PSTORE
2034 Size of user space message log, should be identical to
2035 ramoops.pmsg_size parameter used by kernel and a power of 2
2037 config CMD_PSTORE_ECC_SIZE
2039 depends on CMD_PSTORE
2042 if non-zero, the option enables ECC support and specifies ECC buffer
2043 size in bytes (1 is a special value, means 16 bytes ECC), should be
2044 identical to ramoops.ramoops_ecc parameter used by kernel
2048 source "cmd/mvebu/Kconfig"
2051 bool "terminal - provides a way to attach a serial terminal"
2053 Provides a 'cu'-like serial terminal command. This can be used to
2054 access other serial ports from the system console. The terminal
2055 is very simple with no special processing of characters. As with
2056 cu, you can press ~. (tilde followed by period) to exit.
2059 bool "uuid, guid - generation of unique IDs"
2062 This enables two commands:
2064 uuid - generate random Universally Unique Identifier
2065 guid - generate Globally Unique Identifier based on random UUID
2067 The two commands are very similar except for the endianness of the
2072 source "cmd/ti/Kconfig"
2074 config CMD_BOOTSTAGE
2075 bool "Enable the 'bootstage' command"
2076 depends on BOOTSTAGE
2078 Add a 'bootstage' command which supports printing a report
2079 and un/stashing of bootstage data.
2081 menu "Power commands"
2083 bool "Enable Driver Model PMIC command"
2086 This is the pmic command, based on a driver model pmic's API.
2087 Command features are unchanged:
2088 - list - list pmic devices
2089 - pmic dev <id> - show or [set] operating pmic device (NEW)
2090 - pmic dump - dump registers
2091 - pmic read address - read byte of register at address
2092 - pmic write address - write byte to register at address
2093 The only one change for this command is 'dev' subcommand.
2095 config CMD_REGULATOR
2096 bool "Enable Driver Model REGULATOR command"
2097 depends on DM_REGULATOR
2099 This command is based on driver model regulator's API.
2100 User interface features:
2101 - list - list regulator devices
2102 - regulator dev <id> - show or [set] operating regulator device
2103 - regulator info - print constraints info
2104 - regulator status - print operating status
2105 - regulator value <val] <-f> - print/[set] voltage value [uV]
2106 - regulator current <val> - print/[set] current value [uA]
2107 - regulator mode <id> - print/[set] operating mode id
2108 - regulator enable - enable the regulator output
2109 - regulator disable - disable the regulator output
2111 The '-f' (force) option can be used for set the value which exceeds
2112 the limits, which are found in device-tree and are kept in regulator's
2113 uclass plat structure.
2117 menu "Security commands"
2119 bool "Enable the 'aes' command"
2122 This provides a means to encrypt and decrypt data using the AES
2123 (Advanced Encryption Standard). This algorithm uses a symetric key
2124 and is widely used as a streaming cipher. Different key lengths are
2125 supported by the algorithm but this command only supports 128 bits
2129 bool "Enable the 'blob' command"
2130 depends on !MX6ULL && !MX6SLL && !MX6SL
2131 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2133 This is used with the Freescale secure boot mechanism.
2135 Freescale's SEC block has built-in Blob Protocol which provides
2136 a method for protecting user-defined data across system power
2137 cycles. SEC block protects data in a data structure called a Blob,
2138 which provides both confidentiality and integrity protection.
2140 Encapsulating data as a blob
2141 Each time that the Blob Protocol is used to protect data, a
2142 different randomly generated key is used to encrypt the data.
2143 This random key is itself encrypted using a key which is derived
2144 from SoC's non-volatile secret key and a 16 bit Key identifier.
2145 The resulting encrypted key along with encrypted data is called a
2146 blob. The non-volatile secure key is available for use only during
2149 During decapsulation, the reverse process is performed to get back
2153 blob enc - encapsulating data as a cryptgraphic blob
2154 blob dec - decapsulating cryptgraphic blob to get the data
2158 blob enc src dst len km
2160 Encapsulate and create blob of data $len bytes long
2161 at address $src and store the result at address $dst.
2162 $km is the 16 byte key modifier is also required for
2163 generation/use as key for cryptographic operation. Key
2164 modifier should be 16 byte long.
2166 blob dec src dst len km
2168 Decapsulate the blob of data at address $src and
2169 store result of $len byte at addr $dst.
2170 $km is the 16 byte key modifier is also required for
2171 generation/use as key for cryptographic operation. Key
2172 modifier should be 16 byte long.
2175 bool "Support 'hash' command"
2178 This provides a way to hash data in memory using various supported
2179 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2180 saved to memory or to an environment variable. It is also possible
2181 to verify a hash against data in memory.
2184 bool "Support the 'hvc' command"
2185 depends on ARM_SMCCC
2187 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2188 development and testing.
2191 bool "Support the 'smc' command"
2192 depends on ARM_SMCCC
2194 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2195 development and testing.
2201 Add -v option to verify data against a hash.
2204 bool "scp03 - SCP03 enable and rotate/provision operations"
2207 This command provides access to a Trusted Application
2208 running in a TEE to request Secure Channel Protocol 03
2209 (SCP03) enablement and/or rotation of its SCP03 keys.
2218 bool "Enable the 'tpm' command"
2219 depends on TPM_V1 || TPM_V2
2220 select CMD_TPM_V1 if TPM_V1
2221 select CMD_TPM_V2 if TPM_V2
2223 This provides a means to talk to a TPM from the command line. A wide
2224 range of commands if provided - see 'tpm help' for details. The
2225 command requires a suitable TPM on your board and the correct driver
2231 bool "Enable the 'tpm test' command"
2234 This provides a a series of tests to confirm that the TPMv1.x is
2235 working correctly. The tests cover initialisation, non-volatile RAM,
2236 extend, global lock and checking that timing is within expectations.
2237 The tests pass correctly on Infineon TPMs but may need to be adjusted
2244 menu "Firmware commands"
2246 bool "Enable crosec command"
2250 Enable command-line access to the Chrome OS EC (Embedded
2251 Controller). This provides the 'crosec' command which has
2252 a number of sub-commands for performing EC tasks such as
2253 updating its flash, accessing a small saved context area
2254 and talking to the I2C bus behind the EC (if there is one).
2257 menu "Filesystem commands"
2259 bool "Enable the 'btrsubvol' command"
2262 This enables the 'btrsubvol' command to list subvolumes
2263 of a BTRFS filesystem. There are no special commands for
2264 listing BTRFS directories or loading BTRFS files - this
2265 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2266 when BTRFS is enabled (see FS_BTRFS).
2269 bool "Enable the 'cbfs' command"
2272 Define this to enable support for reading from a Coreboot
2273 filesystem. This is a ROM-based filesystem used for accessing files
2274 on systems that use coreboot as the first boot-loader and then load
2275 U-Boot to actually boot the Operating System. Available commands are
2276 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2279 bool "Enable the 'cramfs' command"
2280 depends on FS_CRAMFS
2282 This provides commands for dealing with CRAMFS (Compressed ROM
2283 filesystem). CRAMFS is useful when space is tight since files are
2284 compressed. Two commands are provided:
2286 cramfsls - lists files in a cramfs image
2287 cramfsload - loads a file from a cramfs image
2290 bool "EROFS command support"
2293 Support for the EROFS fs
2296 bool "ext2 command support"
2299 Enables EXT2 FS command
2302 bool "ext4 command support"
2305 Enables EXT4 FS command
2307 config CMD_EXT4_WRITE
2309 bool "ext4 write command support"
2312 Enables EXT4 FS write command
2315 bool "FAT command support"
2318 Support for the FAT fs
2321 bool "SquashFS command support"
2324 Enables SquashFS filesystem commands (e.g. load, ls).
2326 config CMD_FS_GENERIC
2327 bool "filesystem commands"
2329 Enables filesystem commands (e.g. load, ls) that work for multiple
2333 bool "fsuuid command"
2335 Enables fsuuid command for filesystem UUID.
2338 bool "jffs2 command"
2341 Enables commands to support the JFFS2 (Journalling Flash File System
2342 version 2) filesystem. This enables fsload, ls and fsinfo which
2343 provide the ability to load files, list directories and obtain
2344 filesystem information.
2347 string "Default device for JFFS2"
2348 depends on CMD_JFFS2
2351 The default device to use with the jffs2 command.
2353 config JFFS2_PART_OFFSET
2354 hex "Default offset within flash to locate the JFFS2 image"
2355 depends on CMD_JFFS2
2358 The default offset within flash to locate the JFFS2 image.
2360 config JFFS2_PART_SIZE
2361 hex "Default size of JFFS2 partition"
2362 depends on CMD_JFFS2
2365 The default size of the JFFS2 partition
2368 bool "MTD partition support"
2371 MTD partitioning tool support.
2372 It is strongly encouraged to avoid using this command
2373 anymore along with 'sf', 'nand', 'onenand'. One can still
2374 declare the partitions in the mtdparts environment variable
2375 but better use the MTD stack and the 'mtd' command instead.
2377 config CMD_MTDPARTS_SPREAD
2378 bool "Padd partition size to take account of bad blocks"
2379 depends on CMD_MTDPARTS
2381 This enables the 'spread' sub-command of the mtdparts command.
2382 This command will modify the existing mtdparts variable by increasing
2383 the size of the partitions such that 1) each partition's net size is
2384 at least as large as the size specified in the mtdparts variable and
2385 2) each partition starts on a good block.
2387 config CMD_MTDPARTS_SHOW_NET_SIZES
2388 bool "Show net size (w/o bad blocks) of partitions"
2389 depends on CMD_MTDPARTS
2391 Adds two columns to the printed partition table showing the
2392 effective usable size of a partition, if bad blocks are taken
2395 config MTDIDS_DEFAULT
2396 string "Default MTD IDs"
2397 depends on MTD || SPI_FLASH
2399 Defines a default MTD IDs list for use with MTD partitions in the
2400 Linux MTD command line partitions format.
2402 config MTDPARTS_DEFAULT
2403 string "Default MTD partition scheme"
2404 depends on MTD || SPI_FLASH
2406 Defines a default MTD partitioning scheme in the Linux MTD command
2407 line partitions format
2410 bool "reiser - Access to reiserfs filesystems"
2412 This provides two commands which operate on a resierfs filesystem,
2413 commonly used some years ago:
2415 reiserls - list files
2416 reiserload - load a file
2419 bool "yaffs2 - Access of YAFFS2 filesystem"
2423 This provides commands for accessing a YAFFS2 filesystem. Yet
2424 Another Flash Filesystem 2 is a filesystem designed specifically
2425 for NAND flash. It incorporates bad-block management and ensures
2426 that device writes are sequential regardless of filesystem
2430 bool "zfs - Access of ZFS filesystem"
2432 This provides commands to accessing a ZFS filesystem, commonly used
2433 on Solaris systems. Two sub-commands are provided:
2435 zfsls - list files in a directory
2436 zfsload - load a file
2438 See doc/README.zfs for more details.
2442 menu "Debug commands"
2444 config CMD_CBSYSINFO
2447 default y if SYS_COREBOOT
2449 This provides information about the coreboot sysinfo table stored in
2450 memory by coreboot before jumping to U-Boot. It can be useful for
2451 debugging the beaaviour of coreboot or U-Boot.
2454 bool "diag - Board diagnostics"
2456 This command provides access to board diagnostic tests. These are
2457 called Power-on Self Tests (POST). The command allows listing of
2458 available tests and running either all the tests, or specific tests
2462 bool "event - Show information about events"
2463 default y if EVENT_DEBUG
2465 This enables the 'event' command which provides information about
2466 events and event-handler routines. This can help to device event
2470 bool "irq - Show information about interrupts"
2471 depends on !ARM && !MIPS && !RISCV && !SH
2473 This enables two commands:
2475 interrupts - enable or disable interrupts
2476 irqinfo - print device-specific interrupt information
2479 bool "kgdb - Allow debugging of U-Boot with gdb"
2482 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2483 over a serial link for debugging purposes. This allows
2484 single-stepping, inspecting variables, etc. This is supported only
2485 on PowerPC at present.
2488 bool "log - Generation, control and access to logging"
2492 This provides access to logging features. It allows the output of
2493 log data to be controlled to a limited extent (setting up the default
2494 maximum log level for emitting of records). It also provides access
2495 to a command used for testing the log system.
2498 bool "trace - Support tracing of function calls and timing"
2502 Enables a command to control using of function tracing within
2503 U-Boot. This allows recording of call traces including timing
2504 information. The command can write data to memory for exporting
2505 for analysis (e.g. using bootchart). See doc/README.trace for full
2509 bool "avb - Android Verified Boot 2.0 operations"
2510 depends on AVB_VERIFY
2512 Enables a "avb" command to perform verification of partitions using
2513 Android Verified Boot 2.0 functionality. It includes such subcommands:
2514 avb init - initialize avb2 subsystem
2515 avb read_rb - read rollback index
2516 avb write_rb - write rollback index
2517 avb is_unlocked - check device lock state
2518 avb get_uuid - read and print uuid of a partition
2519 avb read_part - read data from partition
2520 avb read_part_hex - read data from partition and output to stdout
2521 avb write_part - write data to partition
2522 avb verify - run full verification chain
2524 config CMD_STACKPROTECTOR_TEST
2525 bool "Test command for stack protector"
2526 depends on STACKPROTECTOR
2528 Enable stackprot_test command
2529 The stackprot_test command will force a stack overrun to test
2530 the stack smashing detection mechanisms.
2535 tristate "Enable UBI - Unsorted block images commands"
2538 UBI is a software layer above MTD layer which admits use of LVM-like
2539 logical volumes on top of MTD devices, hides some complexities of
2540 flash chips like wear and bad blocks and provides some other useful
2541 capabilities. Please, consult the MTD web site for more details
2542 (www.linux-mtd.infradead.org). Activate this option if you want
2543 to use U-Boot UBI commands.
2544 It is also strongly encouraged to also enable CONFIG_MTD to get full
2547 config CMD_UBI_RENAME
2548 bool "Enable rename"
2551 Enable a "ubi" command to rename ubi volume:
2552 ubi rename <oldname> <newname>
2555 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2557 default y if CMD_UBI
2560 UBIFS is a file system for flash devices which works on top of UBI.
2562 config MMC_SPEED_MODE_SET
2563 bool "set speed mode using mmc command"
2567 Enable setting speed mode using mmc rescan and mmc dev commands.
2568 The speed mode is provided as the last argument in these commands
2569 and is indicated using the index from enum bus_mode in
2570 include/mmc.h. A speed mode can be set only if it has already
2571 been enabled in the device tree.
projects / platform / kernel / u-boot.git / blob