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 int "Buffer size for console output"
83 bool "Command execution tracer"
87 This option enables the possiblity to print all commands before
88 executing them and after all variables are evaluated (similar
89 to Bash's xtrace/'set -x' feature).
90 To enable the tracer a variable "xtrace" needs to be defined in
105 List and dump ACPI tables. ACPI (Advanced Configuration and Power
106 Interface) is used mostly on x86 for providing information to the
107 Operating System about devices in the system. The tables are set up
108 by the firmware, typically U-Boot but possibly an earlier firmware
109 module, if U-Boot is chain-loaded from something else. ACPI tables
110 can also include code, to perform hardware-specific tasks required
111 by the Operating Systems. This allows some amount of separation
112 between the firmware and OS, and is particularly useful when you
113 want to make hardware changes without the OS needing to be adjusted.
120 List non-identity virtual-physical memory mappings for 32-bit CPUs.
133 Print ".config" contents.
135 If this option is enabled, the ".config" file contents are embedded
136 in the U-Boot image and can be printed on the console by the "config"
137 command. This provides information of which options are enabled on
144 Print console devices and information.
150 Print information about available CPUs. This normally shows the
151 number of CPUs, type (e.g. manufacturer, architecture, product or
152 internal name) and clock frequency. Other information may be
153 available depending on the CPU driver.
159 Print GPL license text
164 Provides access to the Intel Power-Management Controller (PMC) so
165 that its state can be examined. This does not currently support
166 changing the state but it is still useful for debugging and seeing
175 config CMD_TLV_EEPROM
177 depends on I2C_EEPROM
179 Display and program the system EEPROM data block in ONIE Tlvinfo
180 format. TLV stands for Type-Length-Value.
182 config SPL_CMD_TLV_EEPROM
183 bool "tlv_eeprom for SPL"
184 depends on SPL_I2C_EEPROM
185 select SPL_DRIVERS_MISC
187 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
191 depends on RISCV_SMODE && SBI_V02
193 Display information about the SBI implementation.
203 Run the command stored in the environment "bootcmd", i.e.
204 "bootd" does the same thing as "run bootcmd".
210 Boot an application image from the memory.
212 config CMD_BOOTM_PRE_LOAD
213 bool "enable pre-load on bootm"
215 depends on IMAGE_PRE_LOAD
218 Enable support of stage pre-load for the bootm command.
219 This stage allow to check or modify the image provided
220 to the bootm command.
225 default y if BOOTSTD_FULL
227 Support listing available bootdevs (boot devices) which can provide an
228 OS to boot, as well as showing information about a particular one.
230 This command is not necessary for bootstd to work.
237 Support scanning for bootflows available with the bootdevs. The
238 bootflows can optionally be booted.
240 config CMD_BOOTFLOW_FULL
241 bool "bootflow - extract subcommands"
242 depends on BOOTSTD_FULL
243 default y if BOOTSTD_FULL
245 Add the ability to list the available bootflows, select one and obtain
246 information about it.
248 This command is not necessary for bootstd to work.
253 default y if BOOTSTD_FULL
255 Support listing available bootmethds (methods used to boot an
256 Operating System), as well as selecting the order that the bootmeths
259 This command is not necessary for bootstd to work.
262 bool "Support booting UEFI FIT images"
263 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
266 Support booting UEFI FIT images via the bootm command.
271 Boot the Linux zImage
275 depends on ARM64 || RISCV
278 Boot an AArch64 Linux Kernel image from memory.
281 bool "Support booting Linux OS images"
282 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
285 Support booting the Linux kernel directly via a command such as bootm
289 bool "Support booting NetBSD (non-EFI) loader images"
293 Support booting NetBSD via the bootm command.
295 config BOOTM_OPENRTOS
296 bool "Support booting OPENRTOS / FreeRTOS images"
299 Support booting OPENRTOS / FreeRTOS via the bootm command.
302 bool "Support booting Enea OSE images"
303 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
306 Support booting Enea OSE images via the bootm command.
309 bool "Support booting Plan9 OS images"
313 Support booting Plan9 images via the bootm command.
316 bool "Support booting RTEMS OS images"
320 Support booting RTEMS images via the bootm command.
323 bool "Support booting VxWorks OS images"
327 Support booting VxWorks images via the bootm command.
331 depends on EFI_LOADER
334 Boot an EFI image from memory.
336 config CMD_BOOTEFI_HELLO_COMPILE
337 bool "Compile a standard EFI hello world binary for testing"
338 depends on CMD_BOOTEFI && !CPU_V7M
341 This compiles a standard EFI hello world application with U-Boot so
342 that it can be used with the test/py testing framework. This is useful
343 for testing that EFI is working at a basic level, and for bringing
344 up EFI support on a new architecture.
346 No additional space will be required in the resulting U-Boot binary
347 when this option is enabled.
349 config CMD_BOOTEFI_HELLO
350 bool "Allow booting a standard EFI hello world for testing"
351 depends on CMD_BOOTEFI_HELLO_COMPILE
352 default y if CMD_BOOTEFI_SELFTEST
354 This adds a standard EFI hello world application to U-Boot so that
355 it can be used with the 'bootefi hello' command. This is useful
356 for testing that EFI is working at a basic level, and for bringing
357 up EFI support on a new architecture.
359 source lib/efi_selftest/Kconfig
366 Add an ANSI terminal boot menu command.
371 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
372 image into RAM, dump image structure information, etc. Those dtb/dtbo
373 files should be merged in one dtb further, which needs to be passed to
374 the kernel, as part of a boot process.
378 depends on ANDROID_BOOT_IMAGE
380 Android Boot Image manipulation commands. Allows one to extract
381 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
382 obtain corresponding meta-information from boot.img.
384 See doc/android/boot-image.rst for details.
387 bool "bootelf, bootvx"
391 Boot an ELF/vxWorks image from the memory.
394 bool "Flattened Device Tree utility commands"
398 Do FDT related setup before booting into the Operating System.
400 config SUPPORT_EXTENSION_SCAN
404 bool "Extension board management command"
406 depends on SUPPORT_EXTENSION_SCAN
408 Enables the "extension" command, which allows to detect
409 extension boards connected to the system, and apply
410 corresponding Device Tree overlays.
416 Start an application at a given address.
422 Run the command in the given environment variable.
428 Print header information for application image.
433 List all images found in flash
439 Extract a part of a multi-image.
442 bool "spl export - Export boot information for Falcon boot"
445 Falcon mode allows booting directly from SPL into an Operating
446 System such as Linux, thus skipping U-Boot proper. See
447 doc/README.falcon for full information about how to use this
450 config CMD_SPL_NAND_OFS
451 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
452 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
455 This provides the offset of the command line arguments for Linux
456 when booting from NAND in Falcon mode. See doc/README.falcon
457 for full information about how to use this option (and also see
458 board/gateworks/gw_ventana/README for an example).
460 config CMD_SPL_NOR_OFS
461 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
462 depends on CMD_SPL && SPL_NOR_SUPPORT
465 This provides the offset of the command line arguments or dtb for
466 Linux when booting from NOR in Falcon mode.
468 config CMD_SPL_WRITE_SIZE
469 hex "Size of argument area"
473 This provides the size of the command-line argument area in NAND
474 flash used by Falcon-mode boot. See the documentation until CMD_SPL
477 config CMD_THOR_DOWNLOAD
478 bool "thor - TIZEN 'thor' download"
481 Implements the 'thor' download protocol. This is a way of
482 downloading a software update over USB from an attached host.
483 There is no documentation about this within the U-Boot source code
484 but you should be able to find something on the interwebs.
487 bool "zboot - x86 boot command"
489 With x86 machines it is common to boot a bzImage file which
490 contains both a kernel and a setup.bin file. The latter includes
491 configuration information from the dark ages which x86 boards still
492 need to pick things out of.
494 Consider using FIT in preference to this since it supports directly
495 booting both 32- and 64-bit kernels, as well as secure boot.
496 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
500 menu "Environment commands"
503 bool "ask for env variable"
505 Ask for environment variable
523 Edit environment variable.
528 Allow for searching environment variables
534 Save all environment variables into the compiled-in persistent
539 depends on CMD_SAVEENV
541 Erase environment variables from the compiled-in persistent
544 config CMD_ENV_EXISTS
548 Check if a variable is defined in the environment for use in
551 config CMD_ENV_CALLBACK
552 bool "env callbacks - print callbacks and their associated variables"
554 Some environment variable have callbacks defined by
555 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
556 For example changing "baudrate" adjust the serial baud rate. This
557 command lists the currently defined callbacks.
560 bool "env flags -print variables that have non-default flags"
562 Some environment variables have special flags that control their
563 behaviour. For example, serial# can only be written once and cannot
564 be deleted. This command shows the variables that have special
567 config CMD_NVEDIT_EFI
568 bool "env [set|print] -e - set/print UEFI variables"
569 depends on EFI_LOADER
572 UEFI variables are encoded as some form of U-Boot variables.
573 If enabled, we are allowed to set/print UEFI variables using
574 "env" command with "-e" option without knowing details.
576 config CMD_NVEDIT_INDIRECT
577 bool "env indirect - Sets environment value from another"
579 config CMD_NVEDIT_INFO
580 bool "env info - print or evaluate environment information"
582 Print environment information:
583 - env_valid : is environment valid
584 - env_ready : is environment imported into hash table
585 - env_use_default : is default environment used
587 This command can be optionally used for evaluation in scripts:
588 [-d] : evaluate whether default environment is used
589 [-p] : evaluate whether environment can be persisted
591 The result of multiple evaluations will be combined with AND.
593 config CMD_NVEDIT_LOAD
596 Load all environment variables from the compiled-in persistent
599 config CMD_NVEDIT_SELECT
602 Select the compiled-in persistent storage of environment variables.
606 menu "Memory commands"
611 Compute binary operations (xor, or, and) of byte arrays of arbitrary
612 size from memory and store the result in memory or the environment.
616 default y if BLOBLIST
618 Show information about the bloblist, a collection of binary blobs
619 held in memory that persist between SPL and U-Boot. In the case of
620 x86 devices the bloblist can be used to hold ACPI tables so that they
621 remain available in memory.
634 Add -v option to verify data against a crc32 checksum.
637 bool "eeprom - EEPROM subsystem"
639 (deprecated, needs conversion to driver model)
640 Provides commands to read and write EEPROM (Electrically Erasable
641 Programmable Read Only Memory) chips that are connected over an
644 config CMD_EEPROM_LAYOUT
645 bool "Enable layout-aware eeprom commands"
646 depends on CMD_EEPROM
648 (deprecated, needs conversion to driver model)
649 When enabled, additional eeprom sub-commands become available.
651 eeprom print - prints the contents of the eeprom in a human-readable
652 way (eeprom layout fields, and data formatted to be fit for human
655 eeprom update - allows user to update eeprom fields by specifying
656 the field name, and providing the new data in a human readable format
657 (same format as displayed by the eeprom print command).
659 Both commands can either auto detect the layout, or be told which
663 __weak int parse_layout_version(char *str)
664 - override to provide your own layout name parsing
665 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
667 - override to setup the layout metadata based on the version
668 __weak int eeprom_layout_detect(unsigned char *data)
669 - override to provide your own algorithm for detecting layout
672 - contains various printing and updating functions for common
673 types of eeprom fields. Can be used for defining
676 config EEPROM_LAYOUT_HELP_STRING
677 string "Tells user what layout names are supported"
678 depends on CMD_EEPROM_LAYOUT
679 default "<not defined>"
681 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
684 config SYS_I2C_EEPROM_BUS
685 int "I2C bus of the EEPROM device."
686 depends on CMD_EEPROM
689 config SYS_I2C_EEPROM_ADDR_LEN
690 int "Length in bytes of the EEPROM memory array address"
691 depends on CMD_EEPROM || ID_EEPROM
695 Note: This is NOT the chip address length!
697 config SYS_EEPROM_SIZE
698 depends on CMD_EEPROM
699 int "Size in bytes of the EEPROM device"
702 config SYS_EEPROM_PAGE_WRITE_BITS
703 int "Number of bits used to address bytes in a single page"
704 depends on CMD_EEPROM
707 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
708 A 64 byte page, for example would require six bits.
710 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
711 int "Number of milliseconds to delay between page writes"
712 depends on CMD_EEPROM || CMD_I2C
718 Infinite write loop on address range
724 Compute MD5 checksum.
728 depends on CMD_MD5SUM
730 Add -v option to verify data against an MD5 checksum.
735 Display memory information.
738 bool "md, mm, nm, mw, cp, cmp, base, loop"
743 mm - memory modify (auto-incrementing address)
744 nm - memory modify (constant address)
745 mw - memory write (fill)
748 base - print or set address offset
749 loop - initialize loop on address range
751 config CMD_MEM_SEARCH
752 bool "ms - Memory search"
754 Memory-search command
756 This allows searching through a region of memory looking for hex
757 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
758 support it). It is also possible to search for a string. The
759 command accepts a memory range and a list of values to search for.
760 The values need to appear in memory in the same order they are given
761 in the command. At most 10 matches can be returned at a time, but
762 pressing return will show the next 10 matches. Environment variables
763 are set for use with scripting (memmatches, memaddr, mempos).
766 bool "Enable cyclic md/mw commands"
767 depends on CMD_MEMORY
769 Add the "mdc" and "mwc" memory commands. These are cyclic
774 This command will print 4 bytes (10,11,12,13) each 500 ms.
776 => mwc.l 100 12345678 10
777 This command will write 12345678 to address 100 all 10 ms.
782 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
784 random - fill memory with random data
789 Simple RAM read/write test.
793 config SYS_ALT_MEMTEST
794 bool "Alternative test"
796 Use a more complete alternative memory test.
800 config SYS_ALT_MEMTEST_BITFLIP
804 The alternative memory test includes bitflip test since 2020.07.
805 The bitflip test significantly increases the overall test time.
806 Bitflip test can optionally be disabled here.
810 config SYS_MEMTEST_START
811 hex "default start address for mtest"
814 This is the default start address for mtest for simple read/write
815 test. If no arguments are given to mtest, default address is used
818 config SYS_MEMTEST_END
819 hex "default end address for mtest"
822 This is the default end address for mtest for simple read/write
823 test. If no arguments are given to mtest, default address is used
832 Compute SHA1 checksum.
834 config SHA1SUM_VERIFY
836 depends on CMD_SHA1SUM
838 Add -v option to verify data against a SHA1 checksum.
841 bool "strings - display strings in memory"
843 This works similarly to the Unix 'strings' command except that it
844 works with a memory range. String of printable characters found
845 within the range are displayed. The minimum number of characters
846 for a sequence to be considered a string can be provided.
850 menu "Compression commands"
854 default y if CMD_BOOTI
857 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
862 default y if CMD_BOOTI
865 Support decompressing an LZ4 image from memory region.
869 default y if CMD_BOOTI
872 Uncompress a zip-compressed memory region.
876 select GZIP_COMPRESSED
878 Compress a memory region with zlib deflate method.
882 menu "Device access commands"
885 #depends on FLASH_CFI_DRIVER
888 ARM Ltd reference designs flash partition access
891 bool "adc - Access Analog to Digital Converters info and data"
893 depends on DM_REGULATOR
895 Shows ADC device info and permit printing one-shot analog converted
896 data from a named Analog to Digital Converter.
901 depends on PARTITIONS
903 Read/modify/write the fields of Bootloader Control Block, usually
904 stored on the flash "misc" partition with its structure defined in:
905 https://android.googlesource.com/platform/bootable/recovery/+/master/
906 bootloader_message/include/bootloader_message/bootloader_message.h
908 Some real-life use-cases include (but are not limited to):
909 - Determine the "boot reason" (and act accordingly):
910 https://source.android.com/devices/bootloader/boot-reason
911 - Get/pass a list of commands from/to recovery:
912 https://android.googlesource.com/platform/bootable/recovery
913 - Inspect/dump the contents of the BCB fields
916 bool "bind/unbind - Bind or unbind a device to/from a driver"
919 Bind or unbind a device to/from a driver from the command line.
920 This is useful in situations where a device may be handled by several
921 drivers. For example, this can be used to bind a UDC to the usb ether
922 gadget driver from the command line.
925 bool "clk - Show clock frequencies"
928 Shows clock frequences by calling a sock_clk_dump() hook function.
929 This is depreated in favour of using the CLK uclass and accessing
930 clock values from associated drivers. However currently no command
934 bool "demo - Demonstration commands for driver model"
937 Provides a 'demo' command which can be used to play around with
938 driver model. To use this properly you will need to enable one or
939 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
940 Otherwise you will always get an empty list of devices. The demo
941 devices are defined in the sandbox device tree, so the easiest
942 option is to use sandbox and pass the -d point to sandbox's
949 Enables the command "dfu" which is used to have U-Boot create a DFU
950 class device via USB. This command requires that the "dfu_alt_info"
951 environment variable be set and define the alt settings to expose to
955 bool "dm - Access to driver model information"
958 Provides access to driver model data structures and information,
959 such as a list of devices, list of uclasses and the state of each
960 device (e.g. activated). This is not required for operation, but
961 can be useful to see the state of driver model for debugging or
965 bool "fastboot - Android fastboot support"
968 This enables the command "fastboot" which enables the Android
969 fastboot mode for the platform. Fastboot is a protocol for
970 downloading images, flashing and device control used on
971 Android devices. Fastboot requires either the network stack
972 enabled or support for acting as a USB device.
974 See doc/android/fastboot.rst for more information.
977 bool "flinfo, erase, protect"
979 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
982 flinfo - print FLASH memory information
984 protect - enable or disable FLASH write protection
993 config CMD_FPGA_LOADBP
994 bool "fpga loadbp - load partial bitstream (Xilinx only)"
997 Supports loading an FPGA device from a bitstream buffer containing
1000 config CMD_FPGA_LOADFS
1001 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
1004 Supports loading an FPGA device from a FAT filesystem.
1006 config CMD_FPGA_LOADMK
1007 bool "fpga loadmk - load bitstream from image"
1010 Supports loading an FPGA device from a image generated by mkimage.
1012 config CMD_FPGA_LOADP
1013 bool "fpga loadp - load partial bitstream"
1016 Supports loading an FPGA device from a bitstream buffer containing
1017 a partial bitstream.
1019 config CMD_FPGA_LOAD_SECURE
1020 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1023 Enables the fpga loads command which is used to load secure
1024 (authenticated or encrypted or both) bitstreams on to FPGA.
1027 bool "fpgad - dump FPGA registers"
1029 (legacy, needs conversion to driver model)
1030 Provides a way to dump FPGA registers by calling the board-specific
1031 fpga_get_reg() function. This functions similarly to the 'md'
1035 bool "fuse - support for the fuse subssystem"
1037 (deprecated - needs conversion to driver model)
1038 This allows reading, sensing, programming or overriding fuses
1039 which control the behaviour of the device. The command uses the
1047 config CMD_GPIO_READ
1048 bool "gpio read - save GPIO value to variable"
1051 Enables the 'gpio read' command that saves the value
1052 of a GPIO pin to a variable.
1058 Control PWM channels, this allows invert/config/enable/disable PWM channels.
1061 bool "GPT (GUID Partition Table) command"
1062 select EFI_PARTITION
1063 select HAVE_BLOCK_DEVICE
1064 select PARTITION_UUIDS
1067 Enable the 'gpt' command to ready and write GPT style partition
1071 bool "GPT Random UUID generation"
1074 Enable the generation of partitions with random UUIDs if none
1077 config CMD_GPT_RENAME
1078 bool "GPT partition renaming commands"
1081 Enables the 'gpt' command to interchange names on two GPT
1082 partitions via the 'gpt swap' command or to rename single
1083 partitions via the 'rename' command.
1086 bool "ide - Support for IDE drivers"
1089 Provides an 'ide' command which allows accessing the IDE drive,
1090 resetting the IDE interface, printing the partition table and
1091 geting device info. It also enables the 'diskboot' command which
1092 permits booting from an IDE drive.
1095 bool "io - Support for performing I/O accesses"
1097 Provides an 'iod' command to display I/O space and an 'iow' command
1098 to write values to the I/O space. This can be useful for manually
1099 checking the state of devices during boot when debugging device
1103 bool "iotrace - Support for tracing I/O activity"
1105 Provides an 'iotrace' command which supports recording I/O reads and
1106 writes in a trace buffer in memory . It also maintains a checksum
1107 of the trace records (even if space is exhausted) so that the
1108 sequence of I/O accesses can be verified.
1110 When debugging drivers it is useful to see what I/O accesses were
1111 done and in what order.
1113 Even if the individual accesses are of little interest it can be
1114 useful to verify that the access pattern is consistent each time
1115 an operation is performed. In this case a checksum can be used to
1116 characterise the operation of a driver. The checksum can be compared
1117 across different runs of the operation to verify that the driver is
1120 In particular, when performing major refactoring of the driver, where
1121 the access pattern should not change, the checksum provides assurance
1122 that the refactoring work has not broken the driver.
1124 This works by sneaking into the io.h heder for an architecture and
1125 redirecting I/O accesses through iotrace's tracing mechanism.
1127 For now no commands are provided to examine the trace buffer. The
1128 format is fairly simple, so 'md' is a reasonable substitute.
1130 Note: The checksum feature is only useful for I/O regions where the
1131 contents do not change outside of software control. Where this is not
1132 suitable you can fall back to manually comparing the addresses. It
1133 might be useful to enhance tracing to only checksum the accesses and
1134 not the data read/written.
1144 bool "w1 - Support for Dallas 1-Wire protocol"
1146 Dallas 1-wire protocol support
1152 Load a binary file over serial line.
1158 Load an S-Record file over serial line
1162 bool "lsblk - list block drivers and devices"
1164 Print list of available block device drivers, and for each, the list
1165 of known block devices.
1168 bool "MBR (Master Boot Record) command"
1169 select DOS_PARTITION
1170 select HAVE_BLOCK_DEVICE
1172 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1173 style partition tables.
1179 Enable the command "misc" for accessing miscellaneous devices with
1180 a MISC uclass driver. The command provides listing all MISC devices
1181 as well as read and write functionalities via their drivers.
1187 MMC memory mapped support.
1191 config CMD_BKOPS_ENABLE
1192 bool "mmc bkops enable"
1195 Enable command for setting manual background operations handshake
1196 on a eMMC device. The feature is optionally available on eMMC devices
1197 conforming to standard >= 4.41.
1200 bool "Enable support for RPMB in the mmc command"
1201 depends on SUPPORT_EMMC_RPMB
1203 Enable the commands for reading, writing and programming the
1204 key for the Replay Protection Memory Block partition in eMMC.
1206 config CMD_MMC_SWRITE
1208 depends on MMC_WRITE
1211 Enable support for the "mmc swrite" command to write Android sparse
1220 Enable storage cloning over block devices, useful for
1221 initial flashing by external block device without network
1224 config CMD_OPTEE_RPMB
1225 bool "Enable read/write support on RPMB via OPTEE"
1226 depends on SUPPORT_EMMC_RPMB && OPTEE
1228 Enable the commands for reading, writing persistent named values
1229 in the Replay Protection Memory Block partition in eMMC by
1230 using Persistent Objects in OPTEE
1235 select MTD_PARTITIONS
1237 MTD commands support.
1241 depends on MULTIPLEXER
1243 List, select, and deselect mux controllers on the fly.
1247 default y if NAND_SUNXI
1248 depends on MTD_RAW_NAND
1253 config CMD_NAND_TRIMFFS
1254 bool "nand write.trimffs"
1255 default y if ARCH_SUNXI
1257 Allows one to skip empty pages when flashing something on a NAND.
1259 config CMD_NAND_LOCK_UNLOCK
1260 bool "nand lock/unlock"
1262 NAND locking support.
1264 config CMD_NAND_TORTURE
1267 NAND torture support.
1276 NVM Express device support
1279 bool "onenand - access to onenand device"
1282 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1283 various useful features. This command allows reading, writing,
1284 and erasing blocks. It allso provides a way to show and change
1285 bad blocks, and test the device.
1290 Enable the 'osd' command which allows to query information from and
1291 write text data to a on-screen display (OSD) device; a virtual device
1292 associated with a display capable of displaying a text overlay on the
1293 display it's associated with..
1297 depends on PARTITIONS
1298 select HAVE_BLOCK_DEVICE
1299 select PARTITION_UUIDS
1301 Read and display information about the partition table on
1305 bool "pci - Access PCI devices"
1307 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1308 used on some devices to allow the CPU to communicate with its
1309 peripherals. Sub-commands allow bus enumeration, displaying and
1310 changing configuration space and a few other features.
1313 bool "pinmux - show pins muxing"
1315 default y if PINCTRL
1317 Parse all available pin-controllers and show pins muxing. This
1318 is useful for debug purpoer to check the pin muxing and to know if
1319 a pin is configured as a GPIO or as an alternate function.
1324 Poweroff/Shutdown the system
1327 bool "read - Read binary data from a partition"
1329 Provides low-level access to the data in a partition.
1331 config CMD_REMOTEPROC
1333 depends on REMOTEPROC
1335 Support for Remote Processor control
1338 bool "sata - Access SATA subsystem"
1341 SATA (Serial Advanced Technology Attachment) is a serial bus
1342 standard for connecting to hard drives and other storage devices.
1343 This command provides information about attached devices and allows
1344 reading, writing and other operations.
1346 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1347 Attachment, where AT refers to an IBM AT (Advanced Technology)
1348 computer released in 1984.
1351 bool "saves - Save a file over serial in S-Record format"
1353 Provides a way to save a binary file using the Motorola S-Record
1354 format over the serial line.
1357 bool "scsi - Access to SCSI devices"
1360 This provides a 'scsi' command which provides access to SCSI (Small
1361 Computer System Interface) devices. The command provides a way to
1362 scan the bus, reset the bus, read and write data and get information
1366 bool "sdram - Print SDRAM configuration information"
1368 Provides information about attached SDRAM. This assumed that the
1369 SDRAM has an EEPROM with information that can be read using the
1370 I2C bus. This is only available on some boards.
1374 depends on DM_SPI_FLASH || SPI_FLASH
1375 default y if DM_SPI_FLASH
1380 bool "sf test - Allow testing of SPI flash"
1383 Provides a way to test that SPI flash is working correctly. The
1384 test is destructive, in that an area of SPI flash must be provided
1385 for the test to use. Performance information is also provided,
1386 measuring the performance of reading, writing and erasing in
1387 Mbps (Million Bits Per Second). This value should approximately
1388 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1389 everything is working properly.
1392 bool "sspi - Command to access spi device"
1395 SPI utility command.
1397 config DEFAULT_SPI_BUS
1398 int "default spi bus used by sspi command"
1402 config DEFAULT_SPI_MODE
1403 hex "default spi mode used by sspi command (see include/spi.h)"
1408 bool "tsi148 - Command to access tsi148 device"
1410 This provides various sub-commands to initialise and configure the
1411 Turndra tsi148 device. See the command help for full details.
1414 bool "Enable UFS - Universal Flash Subsystem commands"
1417 "This provides commands to initialise and configure universal flash
1421 bool "universe - Command to set up the Turndra Universe controller"
1423 This allows setting up the VMEbus provided by this controller.
1424 See the command help for full details.
1429 select HAVE_BLOCK_DEVICE
1435 select USB_FUNCTION_SDP
1437 Enables the command "sdp" which is used to have U-Boot emulating the
1438 Serial Download Protocol (SDP) via USB.
1442 depends on USB_FUNCTION_ROCKUSB
1444 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1445 read/write info, image to/from devices. This enable rockusb command
1446 support to communication with rockusb device. for more detail about
1447 this command, please read doc/README.rockusb.
1449 config CMD_USB_MASS_STORAGE
1450 bool "UMS usb mass storage"
1451 depends on USB_GADGET_DOWNLOAD
1452 select USB_FUNCTION_MASS_STORAGE
1453 depends on BLK && USB_GADGET
1455 Enables the command "ums" and the USB mass storage support to the
1456 export a block device: U-Boot, the USB device, acts as a simple
1457 external hard drive plugged on the host USB port.
1460 bool "Xen para-virtualized block device"
1464 Xen para-virtualized block device support
1469 depends on HAVE_BLOCK_DEVICE
1472 VirtIO block device support
1478 This provides commands to control the watchdog timer devices.
1484 Enable the command "axi" for accessing AXI (Advanced eXtensible
1485 Interface) busses, a on-chip interconnect specification for managing
1486 functional blocks in SoC designs, which is also often used in designs
1487 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1491 menu "Shell scripting commands"
1497 Echo args to console
1503 Return true/false on integer compare.
1509 Run script from memory
1515 Evaluate boolean and math expressions and store the result in an env
1517 Also supports loading the value at a memory location into a variable.
1518 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1520 config CMD_SETEXPR_FMT
1522 depends on CMD_SETEXPR
1524 Evaluate format string expression and store result in an environment
1529 menu "Android support commands"
1531 config CMD_AB_SELECT
1533 depends on ANDROID_AB
1535 On Android devices with more than one boot slot (multiple copies of
1536 the kernel and system images) this provides a command to select which
1537 slot should be used to boot from and register the boot attempt. This
1538 is used by the new A/B update model where one slot is updated in the
1539 background while running from the other slot.
1546 bool "Network commands"
1556 bootp - boot image via network using BOOTP/TFTP protocol
1560 depends on CMD_BOOTP
1562 Boot image via network using DHCP/TFTP protocol
1564 config BOOTP_MAY_FAIL
1565 bool "Allow for the BOOTP/DHCP server to not be found"
1566 depends on CMD_BOOTP
1568 If the DHCP server is not found after the configured retry count, the
1569 call will fail instead of starting over. This can be used to fail
1570 over to Link-local IP address configuration if the DHCP server is not
1573 config BOOTP_BOOTPATH
1574 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1576 depends on CMD_BOOTP
1578 Even though the config is called BOOTP_BOOTPATH, it stores the
1579 path in the variable 'rootpath'.
1581 config BOOTP_VENDOREX
1582 bool "Support vendor extensions from BOOTP/DHCP server"
1583 depends on CMD_BOOTP
1585 config BOOTP_BOOTFILESIZE
1586 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1587 depends on CMD_BOOTP
1590 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1592 depends on CMD_BOOTP
1594 The primary DNS server is stored as 'dnsip'. If two servers are
1595 returned, you must set BOOTP_DNS2 to store that second server IP
1599 bool "Store 'dnsip2' from BOOTP/DHCP server"
1600 depends on BOOTP_DNS
1602 If a DHCP client requests the DNS server IP from a DHCP server,
1603 it is possible that more than one DNS serverip is offered to the
1604 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1605 server IP will be stored in the additional environment
1606 variable "dnsip2". The first DNS serverip is always
1607 stored in the variable "dnsip", when BOOTP_DNS is defined.
1609 config BOOTP_GATEWAY
1610 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1612 depends on CMD_BOOTP
1614 config BOOTP_HOSTNAME
1615 bool "Request & store 'hostname' from BOOTP/DHCP server"
1617 depends on CMD_BOOTP
1619 The name may or may not be qualified with the local domain name.
1621 config BOOTP_PREFER_SERVERIP
1622 bool "serverip variable takes precedent over DHCP server IP."
1623 depends on CMD_BOOTP
1625 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1627 With this option enabled, the 'serverip' variable in the environment
1628 takes precedence over DHCP server IP and will only be set by the DHCP
1629 server if not already set in the environment.
1631 config BOOTP_SUBNETMASK
1632 bool "Request & store 'netmask' from BOOTP/DHCP server"
1634 depends on CMD_BOOTP
1636 config BOOTP_NISDOMAIN
1637 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1638 depends on CMD_BOOTP
1640 config BOOTP_NTPSERVER
1641 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1642 depends on CMD_BOOTP
1644 config BOOTP_TIMEOFFSET
1645 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1646 depends on CMD_BOOTP && CMD_SNTP
1651 Selecting this will allow capturing all Ethernet packets and store
1652 them in physical memory in a PCAP formated file,
1653 later to be analyzed by PCAP reader application (IE. WireShark).
1656 bool "Send PXE client arch to BOOTP/DHCP server"
1658 depends on CMD_BOOTP && CMD_PXE
1660 Supported for ARM, ARM64, and x86 for now.
1662 config BOOTP_PXE_CLIENTARCH
1664 depends on BOOTP_PXE
1665 default 0x16 if ARM64
1669 config BOOTP_VCI_STRING
1671 depends on CMD_BOOTP
1672 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1673 default "U-Boot.armv8" if ARM64
1674 default "U-Boot.arm" if ARM
1681 tftpboot - boot image via network using TFTP protocol
1685 depends on CMD_TFTPBOOT
1687 TFTP put command, for uploading files to a server
1691 depends on CMD_TFTPBOOT
1693 Act as a TFTP server and boot the first received file
1695 config NET_TFTP_VARS
1696 bool "Control TFTP timeout and count through environment"
1697 depends on CMD_TFTPBOOT
1700 If set, allows controlling the TFTP timeout through the
1701 environment variable tftptimeout, and the TFTP maximum
1702 timeout count through the variable tftptimeoutcountmax.
1703 If unset, timeout and maximum are hard-defined as 1 second
1704 and 10 timouts per TFTP transfer.
1709 Boot image via network using RARP/TFTP protocol
1715 Boot image via network using NFS protocol.
1718 int "Timeout in milliseconds for NFS mounts"
1722 Timeout in milliseconds used in NFS protocol. If you encounter
1723 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1730 If set, allows 802.3(clause 22) MII Management functions interface access
1731 The management interface specified in Clause 22 provides
1732 a simple, two signal, serial interface to connect a
1733 Station Management entity and a managed PHY for providing access
1734 to management parameters and services.
1735 The interface is referred to as the MII management interface.
1738 bool "Call mii_init() in the mii command"
1739 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1745 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1746 The MDIO interface is orthogonal to the MII interface and extends
1747 it by adding access to more registers through indirect addressing.
1752 Send ICMP ECHO_REQUEST to network host
1757 Perform CDP network configuration
1763 Synchronize RTC via network
1768 Lookup the IP of a hostname
1770 config CMD_LINK_LOCAL
1774 Acquire a network IP address using the link-local protocol
1781 Allow control of L2 Ethernet switch commands. These are supported
1782 by the vsc9953 Ethernet driver at present. Sub-commands allow
1783 operations such as enabling / disabling a port and
1784 viewing/maintaining the filtering database (FDB)
1790 Boot image via network using PXE protocol
1795 Wait for wake-on-lan Magic Packet
1799 menu "Misc commands"
1802 bool "Enable 'bmp' command"
1803 depends on LCD || DM_VIDEO || VIDEO
1805 This provides a way to obtain information about a BMP-format image
1806 and to display it. BMP (which presumably stands for BitMaP) is a
1807 file format defined by Microsoft which supports images of various
1808 depths, formats and compression methods. Headers on the file
1809 determine the formats used. This command can be used by first loading
1810 the image into RAM, then using this command to look at it or display
1813 config CMD_BOOTCOUNT
1815 depends on BOOTCOUNT_LIMIT
1817 Enable the bootcount command, which allows interrogation and
1818 reset of the bootcounter.
1821 bool "Enable board-specific commands"
1823 (deprecated: instead, please define a Kconfig option for each command)
1825 Some boards have board-specific commands which are only enabled
1826 during developemnt and need to be turned off for production. This
1827 option provides a way to control this. The commands that are enabled
1828 vary depending on the board.
1830 config CMD_BLOCK_CACHE
1831 bool "blkcache - control and stats for block cache"
1832 depends on BLOCK_CACHE
1833 default y if BLOCK_CACHE
1835 Enable the blkcache command, which can be used to control the
1836 operation of the cache functions.
1837 This is most useful when fine-tuning the operation of the cache
1838 during development, but also allows the cache to be disabled when
1839 it might hurt performance (e.g. when using the ums command).
1846 Enable the 'button' command which allows to get the status of
1847 buttons supported by the board. The buttonss can be listed with
1848 'button list' and state can be known with 'button <label>'.
1849 Any button drivers can be controlled with this command, e.g.
1853 bool "icache or dcache"
1855 Enable the "icache" and "dcache" commands
1857 config CMD_CONITRACE
1858 bool "conitrace - trace console input codes"
1860 Enable the 'conitrace' command which displays the codes received
1861 from the console input as hexadecimal numbers.
1864 bool "Enable clear screen command 'cls'"
1865 depends on DM_VIDEO || LCD || VIDEO
1868 Enable the 'cls' command which clears the screen contents
1869 on video frame buffer.
1872 bool "efidebug - display/configure UEFI environment"
1873 depends on EFI_LOADER
1874 select EFI_DEVICE_PATH_TO_TEXT
1876 Enable the 'efidebug' command which provides a subset of UEFI
1877 shell utility with simplified functionality. It will be useful
1878 particularly for managing boot parameters as well as examining
1879 various EFI status for debugging.
1881 config CMD_EXCEPTION
1882 bool "exception - raise exception"
1883 depends on ARM || RISCV || SANDBOX || X86
1885 Enable the 'exception' command which allows to raise an exception.
1892 Enable the 'led' command which allows for control of LEDs supported
1893 by the board. The LEDs can be listed with 'led list' and controlled
1894 with led on/off/togle/blink. Any LED drivers can be controlled with
1895 this command, e.g. led_gpio.
1902 Enable the 'date' command for getting/setting the time/date in RTC
1909 Enable the 'rtc' command for low-level access to RTC devices.
1914 Run commands and summarize execution time.
1917 bool "gettime - read elapsed time"
1919 Enable the 'gettime' command which reads the elapsed time since
1920 U-Boot started running. This shows the time in seconds and
1921 milliseconds. See also the 'bootstage' command which provides more
1922 flexibility for boot timing.
1929 Print bytes from the hardware random number generator.
1931 config CMD_KASLRSEED
1935 Set the kaslr-seed in the chosen node with entropy provided by a
1936 hardware random number generator.
1942 Delay execution for some time
1945 bool "support for multiprocessor commands"
1949 This enables commands to bringup different processors
1950 in multiprocessor cases.
1955 Access the system timer.
1961 This provides basic access to the U-Boot's sound support. The main
1962 feature is to play a beep.
1964 sound init - set up sound system
1965 sound play - play a sound
1971 Boot image via local extlinux.conf file
1977 This provides access to the QEMU firmware interface. The main
1978 feature is to allow easy loading of files passed to qemu-system
1979 via -kernel / -initrd
1984 This provides access to Linux PStore with Rammoops backend. The main
1985 feature is to allow to display or save PStore records.
1987 See doc/pstore.rst for more information.
1991 config CMD_PSTORE_MEM_ADDR
1992 hex "Memory Address"
1993 depends on CMD_PSTORE
1995 Base addr used for PStore ramoops memory, should be identical to
1996 ramoops.mem_address parameter used by kernel
1998 config CMD_PSTORE_MEM_SIZE
2000 depends on CMD_PSTORE
2003 Size of PStore ramoops memory, should be identical to ramoops.mem_size
2004 parameter used by kernel, a power of 2 and larger than the sum of the
2007 config CMD_PSTORE_RECORD_SIZE
2008 hex "Dump record size"
2009 depends on CMD_PSTORE
2012 Size of each dump done on oops/panic, should be identical to
2013 ramoops.record_size parameter used by kernel and a power of 2
2016 config CMD_PSTORE_CONSOLE_SIZE
2017 hex "Kernel console log size"
2018 depends on CMD_PSTORE
2021 Size of kernel console log, should be identical to
2022 ramoops.console_size parameter used by kernel and a power of 2
2025 config CMD_PSTORE_FTRACE_SIZE
2026 hex "FTrace log size"
2027 depends on CMD_PSTORE
2030 Size of ftrace log, should be identical to ramoops.ftrace_size
2031 parameter used by kernel and a power of 2
2033 config CMD_PSTORE_PMSG_SIZE
2034 hex "User space message log size"
2035 depends on CMD_PSTORE
2038 Size of user space message log, should be identical to
2039 ramoops.pmsg_size parameter used by kernel and a power of 2
2041 config CMD_PSTORE_ECC_SIZE
2043 depends on CMD_PSTORE
2046 if non-zero, the option enables ECC support and specifies ECC buffer
2047 size in bytes (1 is a special value, means 16 bytes ECC), should be
2048 identical to ramoops.ramoops_ecc parameter used by kernel
2052 source "cmd/mvebu/Kconfig"
2055 bool "terminal - provides a way to attach a serial terminal"
2057 Provides a 'cu'-like serial terminal command. This can be used to
2058 access other serial ports from the system console. The terminal
2059 is very simple with no special processing of characters. As with
2060 cu, you can press ~. (tilde followed by period) to exit.
2063 bool "uuid, guid - generation of unique IDs"
2066 This enables two commands:
2068 uuid - generate random Universally Unique Identifier
2069 guid - generate Globally Unique Identifier based on random UUID
2071 The two commands are very similar except for the endianness of the
2076 source "cmd/ti/Kconfig"
2078 config CMD_BOOTSTAGE
2079 bool "Enable the 'bootstage' command"
2080 depends on BOOTSTAGE
2082 Add a 'bootstage' command which supports printing a report
2083 and un/stashing of bootstage data.
2085 menu "Power commands"
2087 bool "Enable Driver Model PMIC command"
2090 This is the pmic command, based on a driver model pmic's API.
2091 Command features are unchanged:
2092 - list - list pmic devices
2093 - pmic dev <id> - show or [set] operating pmic device (NEW)
2094 - pmic dump - dump registers
2095 - pmic read address - read byte of register at address
2096 - pmic write address - write byte to register at address
2097 The only one change for this command is 'dev' subcommand.
2099 config CMD_REGULATOR
2100 bool "Enable Driver Model REGULATOR command"
2101 depends on DM_REGULATOR
2103 This command is based on driver model regulator's API.
2104 User interface features:
2105 - list - list regulator devices
2106 - regulator dev <id> - show or [set] operating regulator device
2107 - regulator info - print constraints info
2108 - regulator status - print operating status
2109 - regulator value <val] <-f> - print/[set] voltage value [uV]
2110 - regulator current <val> - print/[set] current value [uA]
2111 - regulator mode <id> - print/[set] operating mode id
2112 - regulator enable - enable the regulator output
2113 - regulator disable - disable the regulator output
2115 The '-f' (force) option can be used for set the value which exceeds
2116 the limits, which are found in device-tree and are kept in regulator's
2117 uclass plat structure.
2121 menu "Security commands"
2123 bool "Enable the 'aes' command"
2126 This provides a means to encrypt and decrypt data using the AES
2127 (Advanced Encryption Standard). This algorithm uses a symetric key
2128 and is widely used as a streaming cipher. Different key lengths are
2129 supported by the algorithm but this command only supports 128 bits
2133 bool "Enable the 'blob' command"
2134 depends on !MX6ULL && !MX6SLL && !MX6SL
2135 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2137 This is used with the Freescale secure boot mechanism.
2139 Freescale's SEC block has built-in Blob Protocol which provides
2140 a method for protecting user-defined data across system power
2141 cycles. SEC block protects data in a data structure called a Blob,
2142 which provides both confidentiality and integrity protection.
2144 Encapsulating data as a blob
2145 Each time that the Blob Protocol is used to protect data, a
2146 different randomly generated key is used to encrypt the data.
2147 This random key is itself encrypted using a key which is derived
2148 from SoC's non-volatile secret key and a 16 bit Key identifier.
2149 The resulting encrypted key along with encrypted data is called a
2150 blob. The non-volatile secure key is available for use only during
2153 During decapsulation, the reverse process is performed to get back
2157 blob enc - encapsulating data as a cryptgraphic blob
2158 blob dec - decapsulating cryptgraphic blob to get the data
2162 blob enc src dst len km
2164 Encapsulate and create blob of data $len bytes long
2165 at address $src and store the result at address $dst.
2166 $km is the 16 byte key modifier is also required for
2167 generation/use as key for cryptographic operation. Key
2168 modifier should be 16 byte long.
2170 blob dec src dst len km
2172 Decapsulate the blob of data at address $src and
2173 store result of $len byte at addr $dst.
2174 $km is the 16 byte key modifier is also required for
2175 generation/use as key for cryptographic operation. Key
2176 modifier should be 16 byte long.
2179 bool "Support 'hash' command"
2182 This provides a way to hash data in memory using various supported
2183 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2184 saved to memory or to an environment variable. It is also possible
2185 to verify a hash against data in memory.
2188 bool "Support the 'hvc' command"
2189 depends on ARM_SMCCC
2191 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2192 development and testing.
2195 bool "Support the 'smc' command"
2196 depends on ARM_SMCCC
2198 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2199 development and testing.
2205 Add -v option to verify data against a hash.
2208 bool "scp03 - SCP03 enable and rotate/provision operations"
2211 This command provides access to a Trusted Application
2212 running in a TEE to request Secure Channel Protocol 03
2213 (SCP03) enablement and/or rotation of its SCP03 keys.
2222 bool "Enable the 'tpm' command"
2223 depends on TPM_V1 || TPM_V2
2224 select CMD_TPM_V1 if TPM_V1
2225 select CMD_TPM_V2 if TPM_V2
2227 This provides a means to talk to a TPM from the command line. A wide
2228 range of commands if provided - see 'tpm help' for details. The
2229 command requires a suitable TPM on your board and the correct driver
2235 bool "Enable the 'tpm test' command"
2238 This provides a a series of tests to confirm that the TPMv1.x is
2239 working correctly. The tests cover initialisation, non-volatile RAM,
2240 extend, global lock and checking that timing is within expectations.
2241 The tests pass correctly on Infineon TPMs but may need to be adjusted
2248 menu "Firmware commands"
2250 bool "Enable crosec command"
2254 Enable command-line access to the Chrome OS EC (Embedded
2255 Controller). This provides the 'crosec' command which has
2256 a number of sub-commands for performing EC tasks such as
2257 updating its flash, accessing a small saved context area
2258 and talking to the I2C bus behind the EC (if there is one).
2261 menu "Filesystem commands"
2263 bool "Enable the 'btrsubvol' command"
2266 This enables the 'btrsubvol' command to list subvolumes
2267 of a BTRFS filesystem. There are no special commands for
2268 listing BTRFS directories or loading BTRFS files - this
2269 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2270 when BTRFS is enabled (see FS_BTRFS).
2273 bool "Enable the 'cbfs' command"
2276 Define this to enable support for reading from a Coreboot
2277 filesystem. This is a ROM-based filesystem used for accessing files
2278 on systems that use coreboot as the first boot-loader and then load
2279 U-Boot to actually boot the Operating System. Available commands are
2280 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2283 bool "Enable the 'cramfs' command"
2284 depends on FS_CRAMFS
2286 This provides commands for dealing with CRAMFS (Compressed ROM
2287 filesystem). CRAMFS is useful when space is tight since files are
2288 compressed. Two commands are provided:
2290 cramfsls - lists files in a cramfs image
2291 cramfsload - loads a file from a cramfs image
2294 bool "EROFS command support"
2297 Support for the EROFS fs
2300 bool "ext2 command support"
2303 Enables EXT2 FS command
2306 bool "ext4 command support"
2309 Enables EXT4 FS command
2311 config CMD_EXT4_WRITE
2313 bool "ext4 write command support"
2316 Enables EXT4 FS write command
2319 bool "FAT command support"
2322 Support for the FAT fs
2325 bool "SquashFS command support"
2328 Enables SquashFS filesystem commands (e.g. load, ls).
2330 config CMD_FS_GENERIC
2331 bool "filesystem commands"
2333 Enables filesystem commands (e.g. load, ls) that work for multiple
2337 bool "fsuuid command"
2339 Enables fsuuid command for filesystem UUID.
2342 bool "jffs2 command"
2345 Enables commands to support the JFFS2 (Journalling Flash File System
2346 version 2) filesystem. This enables fsload, ls and fsinfo which
2347 provide the ability to load files, list directories and obtain
2348 filesystem information.
2351 string "Default device for JFFS2"
2352 depends on CMD_JFFS2
2355 The default device to use with the jffs2 command.
2357 config JFFS2_PART_OFFSET
2358 hex "Default offset within flash to locate the JFFS2 image"
2359 depends on CMD_JFFS2
2362 The default offset within flash to locate the JFFS2 image.
2364 config JFFS2_PART_SIZE
2365 hex "Default size of JFFS2 partition"
2366 depends on CMD_JFFS2
2369 The default size of the JFFS2 partition
2372 bool "MTD partition support"
2375 MTD partitioning tool support.
2376 It is strongly encouraged to avoid using this command
2377 anymore along with 'sf', 'nand', 'onenand'. One can still
2378 declare the partitions in the mtdparts environment variable
2379 but better use the MTD stack and the 'mtd' command instead.
2381 config CMD_MTDPARTS_SPREAD
2382 bool "Padd partition size to take account of bad blocks"
2383 depends on CMD_MTDPARTS
2385 This enables the 'spread' sub-command of the mtdparts command.
2386 This command will modify the existing mtdparts variable by increasing
2387 the size of the partitions such that 1) each partition's net size is
2388 at least as large as the size specified in the mtdparts variable and
2389 2) each partition starts on a good block.
2391 config CMD_MTDPARTS_SHOW_NET_SIZES
2392 bool "Show net size (w/o bad blocks) of partitions"
2393 depends on CMD_MTDPARTS
2395 Adds two columns to the printed partition table showing the
2396 effective usable size of a partition, if bad blocks are taken
2399 config MTDIDS_DEFAULT
2400 string "Default MTD IDs"
2401 depends on MTD || SPI_FLASH
2403 Defines a default MTD IDs list for use with MTD partitions in the
2404 Linux MTD command line partitions format.
2406 config MTDPARTS_DEFAULT
2407 string "Default MTD partition scheme"
2408 depends on MTD || SPI_FLASH
2410 Defines a default MTD partitioning scheme in the Linux MTD command
2411 line partitions format
2414 bool "reiser - Access to reiserfs filesystems"
2416 This provides two commands which operate on a resierfs filesystem,
2417 commonly used some years ago:
2419 reiserls - list files
2420 reiserload - load a file
2423 bool "yaffs2 - Access of YAFFS2 filesystem"
2427 This provides commands for accessing a YAFFS2 filesystem. Yet
2428 Another Flash Filesystem 2 is a filesystem designed specifically
2429 for NAND flash. It incorporates bad-block management and ensures
2430 that device writes are sequential regardless of filesystem
2434 bool "zfs - Access of ZFS filesystem"
2436 This provides commands to accessing a ZFS filesystem, commonly used
2437 on Solaris systems. Two sub-commands are provided:
2439 zfsls - list files in a directory
2440 zfsload - load a file
2442 See doc/README.zfs for more details.
2446 menu "Debug commands"
2448 config CMD_CBSYSINFO
2451 default y if SYS_COREBOOT
2453 This provides information about the coreboot sysinfo table stored in
2454 memory by coreboot before jumping to U-Boot. It can be useful for
2455 debugging the beaaviour of coreboot or U-Boot.
2458 bool "diag - Board diagnostics"
2460 This command provides access to board diagnostic tests. These are
2461 called Power-on Self Tests (POST). The command allows listing of
2462 available tests and running either all the tests, or specific tests
2466 bool "event - Show information about events"
2467 default y if EVENT_DEBUG
2469 This enables the 'event' command which provides information about
2470 events and event-handler routines. This can help to device event
2474 bool "irq - Show information about interrupts"
2475 depends on !ARM && !MIPS && !RISCV && !SH
2477 This enables two commands:
2479 interrupts - enable or disable interrupts
2480 irqinfo - print device-specific interrupt information
2483 bool "kgdb - Allow debugging of U-Boot with gdb"
2486 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2487 over a serial link for debugging purposes. This allows
2488 single-stepping, inspecting variables, etc. This is supported only
2489 on PowerPC at present.
2492 bool "log - Generation, control and access to logging"
2496 This provides access to logging features. It allows the output of
2497 log data to be controlled to a limited extent (setting up the default
2498 maximum log level for emitting of records). It also provides access
2499 to a command used for testing the log system.
2502 bool "trace - Support tracing of function calls and timing"
2506 Enables a command to control using of function tracing within
2507 U-Boot. This allows recording of call traces including timing
2508 information. The command can write data to memory for exporting
2509 for analysis (e.g. using bootchart). See doc/README.trace for full
2513 bool "avb - Android Verified Boot 2.0 operations"
2514 depends on AVB_VERIFY
2516 Enables a "avb" command to perform verification of partitions using
2517 Android Verified Boot 2.0 functionality. It includes such subcommands:
2518 avb init - initialize avb2 subsystem
2519 avb read_rb - read rollback index
2520 avb write_rb - write rollback index
2521 avb is_unlocked - check device lock state
2522 avb get_uuid - read and print uuid of a partition
2523 avb read_part - read data from partition
2524 avb read_part_hex - read data from partition and output to stdout
2525 avb write_part - write data to partition
2526 avb verify - run full verification chain
2528 config CMD_STACKPROTECTOR_TEST
2529 bool "Test command for stack protector"
2530 depends on STACKPROTECTOR
2532 Enable stackprot_test command
2533 The stackprot_test command will force a stack overrun to test
2534 the stack smashing detection mechanisms.
2539 tristate "Enable UBI - Unsorted block images commands"
2542 UBI is a software layer above MTD layer which admits use of LVM-like
2543 logical volumes on top of MTD devices, hides some complexities of
2544 flash chips like wear and bad blocks and provides some other useful
2545 capabilities. Please, consult the MTD web site for more details
2546 (www.linux-mtd.infradead.org). Activate this option if you want
2547 to use U-Boot UBI commands.
2548 It is also strongly encouraged to also enable CONFIG_MTD to get full
2551 config CMD_UBI_RENAME
2552 bool "Enable rename"
2555 Enable a "ubi" command to rename ubi volume:
2556 ubi rename <oldname> <newname>
2559 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2561 default y if CMD_UBI
2564 UBIFS is a file system for flash devices which works on top of UBI.
2566 config MMC_SPEED_MODE_SET
2567 bool "set speed mode using mmc command"
2571 Enable setting speed mode using mmc rescan and mmc dev commands.
2572 The speed mode is provided as the last argument in these commands
2573 and is indicated using the index from enum bus_mode in
2574 include/mmc.h. A speed mode can be set only if it has already
2575 been enabled in the device tree.
projects / platform / kernel / u-boot.git / blob