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 bool "Command execution tracer"
79 This option enables the possiblity to print all commands before
80 executing them and after all variables are evaluated (similar
81 to Bash's xtrace/'set -x' feature).
82 To enable the tracer a variable "xtrace" needs to be defined in
97 List and dump ACPI tables. ACPI (Advanced Configuration and Power
98 Interface) is used mostly on x86 for providing information to the
99 Operating System about devices in the system. The tables are set up
100 by the firmware, typically U-Boot but possibly an earlier firmware
101 module, if U-Boot is chain-loaded from something else. ACPI tables
102 can also include code, to perform hardware-specific tasks required
103 by the Operating Systems. This allows some amount of separation
104 between the firmware and OS, and is particularly useful when you
105 want to make hardware changes without the OS needing to be adjusted.
112 List non-identity virtual-physical memory mappings for 32-bit CPUs.
125 Print ".config" contents.
127 If this option is enabled, the ".config" file contents are embedded
128 in the U-Boot image and can be printed on the console by the "config"
129 command. This provides information of which options are enabled on
136 Print console devices and information.
142 Print information about available CPUs. This normally shows the
143 number of CPUs, type (e.g. manufacturer, architecture, product or
144 internal name) and clock frequency. Other information may be
145 available depending on the CPU driver.
151 Print GPL license text
156 Provides access to the Intel Power-Management Controller (PMC) so
157 that its state can be examined. This does not currently support
158 changing the state but it is still useful for debugging and seeing
167 config CMD_TLV_EEPROM
169 depends on I2C_EEPROM
171 Display and program the system EEPROM data block in ONIE Tlvinfo
172 format. TLV stands for Type-Length-Value.
174 config SPL_CMD_TLV_EEPROM
175 bool "tlv_eeprom for SPL"
176 depends on SPL_I2C_EEPROM
177 select SPL_DRIVERS_MISC
179 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
183 depends on RISCV_SMODE && SBI_V02
185 Display information about the SBI implementation.
195 Run the command stored in the environment "bootcmd", i.e.
196 "bootd" does the same thing as "run bootcmd".
202 Boot an application image from the memory.
204 config CMD_BOOTM_PRE_LOAD
205 bool "enable pre-load on bootm"
207 depends on IMAGE_PRE_LOAD
210 Enable support of stage pre-load for the bootm command.
211 This stage allow to check or modify the image provided
212 to the bootm command.
217 default y if BOOTSTD_FULL
219 Support listing available bootdevs (boot devices) which can provide an
220 OS to boot, as well as showing information about a particular one.
222 This command is not necessary for bootstd to work.
229 Support scanning for bootflows available with the bootdevs. The
230 bootflows can optionally be booted.
232 config CMD_BOOTFLOW_FULL
233 bool "bootflow - extract subcommands"
234 depends on BOOTSTD_FULL
235 default y if BOOTSTD_FULL
237 Add the ability to list the available bootflows, select one and obtain
238 information about it.
240 This command is not necessary for bootstd to work.
245 default y if BOOTSTD_FULL
247 Support listing available bootmethds (methods used to boot an
248 Operating System), as well as selecting the order that the bootmeths
251 This command is not necessary for bootstd to work.
254 bool "Support booting UEFI FIT images"
255 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
258 Support booting UEFI FIT images via the bootm command.
263 Boot the Linux zImage
267 depends on ARM64 || RISCV
270 Boot an AArch64 Linux Kernel image from memory.
273 bool "Support booting Linux OS images"
274 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
277 Support booting the Linux kernel directly via a command such as bootm
281 bool "Support booting NetBSD (non-EFI) loader images"
285 Support booting NetBSD via the bootm command.
287 config BOOTM_OPENRTOS
288 bool "Support booting OPENRTOS / FreeRTOS images"
291 Support booting OPENRTOS / FreeRTOS via the bootm command.
294 bool "Support booting Enea OSE images"
295 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
298 Support booting Enea OSE images via the bootm command.
301 bool "Support booting Plan9 OS images"
305 Support booting Plan9 images via the bootm command.
308 bool "Support booting RTEMS OS images"
312 Support booting RTEMS images via the bootm command.
315 bool "Support booting VxWorks OS images"
319 Support booting VxWorks images via the bootm command.
323 depends on EFI_LOADER
326 Boot an EFI image from memory.
328 config CMD_BOOTEFI_HELLO_COMPILE
329 bool "Compile a standard EFI hello world binary for testing"
330 depends on CMD_BOOTEFI && !CPU_V7M
333 This compiles a standard EFI hello world application with U-Boot so
334 that it can be used with the test/py testing framework. This is useful
335 for testing that EFI is working at a basic level, and for bringing
336 up EFI support on a new architecture.
338 No additional space will be required in the resulting U-Boot binary
339 when this option is enabled.
341 config CMD_BOOTEFI_HELLO
342 bool "Allow booting a standard EFI hello world for testing"
343 depends on CMD_BOOTEFI_HELLO_COMPILE
344 default y if CMD_BOOTEFI_SELFTEST
346 This adds a standard EFI hello world application to U-Boot so that
347 it can be used with the 'bootefi hello' command. This is useful
348 for testing that EFI is working at a basic level, and for bringing
349 up EFI support on a new architecture.
351 source lib/efi_selftest/Kconfig
357 Add an ANSI terminal boot menu command.
362 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
363 image into RAM, dump image structure information, etc. Those dtb/dtbo
364 files should be merged in one dtb further, which needs to be passed to
365 the kernel, as part of a boot process.
369 depends on ANDROID_BOOT_IMAGE
371 Android Boot Image manipulation commands. Allows one to extract
372 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
373 obtain corresponding meta-information from boot.img.
375 See doc/android/boot-image.rst for details.
378 bool "bootelf, bootvx"
382 Boot an ELF/vxWorks image from the memory.
385 bool "Flattened Device Tree utility commands"
389 Do FDT related setup before booting into the Operating System.
391 config SUPPORT_EXTENSION_SCAN
395 bool "Extension board management command"
397 depends on SUPPORT_EXTENSION_SCAN
399 Enables the "extension" command, which allows to detect
400 extension boards connected to the system, and apply
401 corresponding Device Tree overlays.
407 Start an application at a given address.
413 Run the command in the given environment variable.
419 Print header information for application image.
424 List all images found in flash
430 Extract a part of a multi-image.
433 bool "spl export - Export boot information for Falcon boot"
436 Falcon mode allows booting directly from SPL into an Operating
437 System such as Linux, thus skipping U-Boot proper. See
438 doc/README.falcon for full information about how to use this
441 config CMD_SPL_NAND_OFS
442 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
443 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
446 This provides the offset of the command line arguments for Linux
447 when booting from NAND in Falcon mode. See doc/README.falcon
448 for full information about how to use this option (and also see
449 board/gateworks/gw_ventana/README for an example).
451 config CMD_SPL_NOR_OFS
452 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
453 depends on CMD_SPL && SPL_NOR_SUPPORT
456 This provides the offset of the command line arguments or dtb for
457 Linux when booting from NOR in Falcon mode.
459 config CMD_SPL_WRITE_SIZE
460 hex "Size of argument area"
464 This provides the size of the command-line argument area in NAND
465 flash used by Falcon-mode boot. See the documentation until CMD_SPL
468 config CMD_THOR_DOWNLOAD
469 bool "thor - TIZEN 'thor' download"
472 Implements the 'thor' download protocol. This is a way of
473 downloading a software update over USB from an attached host.
474 There is no documentation about this within the U-Boot source code
475 but you should be able to find something on the interwebs.
478 bool "zboot - x86 boot command"
480 With x86 machines it is common to boot a bzImage file which
481 contains both a kernel and a setup.bin file. The latter includes
482 configuration information from the dark ages which x86 boards still
483 need to pick things out of.
485 Consider using FIT in preference to this since it supports directly
486 booting both 32- and 64-bit kernels, as well as secure boot.
487 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
491 menu "Environment commands"
494 bool "ask for env variable"
496 Ask for environment variable
514 Edit environment variable.
519 Allow for searching environment variables
525 Save all environment variables into the compiled-in persistent
530 depends on CMD_SAVEENV
532 Erase environment variables from the compiled-in persistent
535 config CMD_ENV_EXISTS
539 Check if a variable is defined in the environment for use in
542 config CMD_ENV_CALLBACK
543 bool "env callbacks - print callbacks and their associated variables"
545 Some environment variable have callbacks defined by
546 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
547 For example changing "baudrate" adjust the serial baud rate. This
548 command lists the currently defined callbacks.
551 bool "env flags -print variables that have non-default flags"
553 Some environment variables have special flags that control their
554 behaviour. For example, serial# can only be written once and cannot
555 be deleted. This command shows the variables that have special
558 config CMD_NVEDIT_EFI
559 bool "env [set|print] -e - set/print UEFI variables"
560 depends on EFI_LOADER
563 UEFI variables are encoded as some form of U-Boot variables.
564 If enabled, we are allowed to set/print UEFI variables using
565 "env" command with "-e" option without knowing details.
567 config CMD_NVEDIT_INDIRECT
568 bool "env indirect - Sets environment value from another"
570 config CMD_NVEDIT_INFO
571 bool "env info - print or evaluate environment information"
573 Print environment information:
574 - env_valid : is environment valid
575 - env_ready : is environment imported into hash table
576 - env_use_default : is default environment used
578 This command can be optionally used for evaluation in scripts:
579 [-d] : evaluate whether default environment is used
580 [-p] : evaluate whether environment can be persisted
582 The result of multiple evaluations will be combined with AND.
584 config CMD_NVEDIT_LOAD
587 Load all environment variables from the compiled-in persistent
590 config CMD_NVEDIT_SELECT
593 Select the compiled-in persistent storage of environment variables.
597 menu "Memory commands"
602 Compute binary operations (xor, or, and) of byte arrays of arbitrary
603 size from memory and store the result in memory or the environment.
607 default y if BLOBLIST
609 Show information about the bloblist, a collection of binary blobs
610 held in memory that persist between SPL and U-Boot. In the case of
611 x86 devices the bloblist can be used to hold ACPI tables so that they
612 remain available in memory.
625 Add -v option to verify data against a crc32 checksum.
628 bool "eeprom - EEPROM subsystem"
630 (deprecated, needs conversion to driver model)
631 Provides commands to read and write EEPROM (Electrically Erasable
632 Programmable Read Only Memory) chips that are connected over an
635 config CMD_EEPROM_LAYOUT
636 bool "Enable layout-aware eeprom commands"
637 depends on CMD_EEPROM
639 (deprecated, needs conversion to driver model)
640 When enabled, additional eeprom sub-commands become available.
642 eeprom print - prints the contents of the eeprom in a human-readable
643 way (eeprom layout fields, and data formatted to be fit for human
646 eeprom update - allows user to update eeprom fields by specifying
647 the field name, and providing the new data in a human readable format
648 (same format as displayed by the eeprom print command).
650 Both commands can either auto detect the layout, or be told which
654 __weak int parse_layout_version(char *str)
655 - override to provide your own layout name parsing
656 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
658 - override to setup the layout metadata based on the version
659 __weak int eeprom_layout_detect(unsigned char *data)
660 - override to provide your own algorithm for detecting layout
663 - contains various printing and updating functions for common
664 types of eeprom fields. Can be used for defining
667 config EEPROM_LAYOUT_HELP_STRING
668 string "Tells user what layout names are supported"
669 depends on CMD_EEPROM_LAYOUT
670 default "<not defined>"
672 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
675 config SYS_I2C_EEPROM_BUS
676 int "I2C bus of the EEPROM device."
677 depends on CMD_EEPROM
680 config SYS_I2C_EEPROM_ADDR_LEN
681 int "Length in bytes of the EEPROM memory array address"
682 depends on CMD_EEPROM || ID_EEPROM
686 Note: This is NOT the chip address length!
688 config SYS_EEPROM_SIZE
689 depends on CMD_EEPROM
690 int "Size in bytes of the EEPROM device"
693 config SYS_EEPROM_PAGE_WRITE_BITS
694 int "Number of bits used to address bytes in a single page"
695 depends on CMD_EEPROM
698 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
699 A 64 byte page, for example would require six bits.
701 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
702 int "Number of milliseconds to delay between page writes"
703 depends on CMD_EEPROM || CMD_I2C
709 Infinite write loop on address range
715 Compute MD5 checksum.
719 depends on CMD_MD5SUM
721 Add -v option to verify data against an MD5 checksum.
726 Display memory information.
729 bool "md, mm, nm, mw, cp, cmp, base, loop"
734 mm - memory modify (auto-incrementing address)
735 nm - memory modify (constant address)
736 mw - memory write (fill)
739 base - print or set address offset
740 loop - initialize loop on address range
742 config CMD_MEM_SEARCH
743 bool "ms - Memory search"
745 Memory-search command
747 This allows searching through a region of memory looking for hex
748 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
749 support it). It is also possible to search for a string. The
750 command accepts a memory range and a list of values to search for.
751 The values need to appear in memory in the same order they are given
752 in the command. At most 10 matches can be returned at a time, but
753 pressing return will show the next 10 matches. Environment variables
754 are set for use with scripting (memmatches, memaddr, mempos).
757 bool "Enable cyclic md/mw commands"
758 depends on CMD_MEMORY
760 Add the "mdc" and "mwc" memory commands. These are cyclic
765 This command will print 4 bytes (10,11,12,13) each 500 ms.
767 => mwc.l 100 12345678 10
768 This command will write 12345678 to address 100 all 10 ms.
773 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
775 random - fill memory with random data
780 Simple RAM read/write test.
784 config SYS_ALT_MEMTEST
785 bool "Alternative test"
787 Use a more complete alternative memory test.
791 config SYS_ALT_MEMTEST_BITFLIP
795 The alternative memory test includes bitflip test since 2020.07.
796 The bitflip test significantly increases the overall test time.
797 Bitflip test can optionally be disabled here.
801 config SYS_MEMTEST_START
802 hex "default start address for mtest"
805 This is the default start address for mtest for simple read/write
806 test. If no arguments are given to mtest, default address is used
809 config SYS_MEMTEST_END
810 hex "default end address for mtest"
813 This is the default end address for mtest for simple read/write
814 test. If no arguments are given to mtest, default address is used
823 Compute SHA1 checksum.
825 config SHA1SUM_VERIFY
827 depends on CMD_SHA1SUM
829 Add -v option to verify data against a SHA1 checksum.
832 bool "strings - display strings in memory"
834 This works similarly to the Unix 'strings' command except that it
835 works with a memory range. String of printable characters found
836 within the range are displayed. The minimum number of characters
837 for a sequence to be considered a string can be provided.
841 menu "Compression commands"
845 default y if CMD_BOOTI
848 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
853 default y if CMD_BOOTI
856 Support decompressing an LZ4 image from memory region.
860 default y if CMD_BOOTI
863 Uncompress a zip-compressed memory region.
867 select GZIP_COMPRESSED
869 Compress a memory region with zlib deflate method.
873 menu "Device access commands"
876 #depends on FLASH_CFI_DRIVER
879 ARM Ltd reference designs flash partition access
882 bool "adc - Access Analog to Digital Converters info and data"
884 depends on DM_REGULATOR
886 Shows ADC device info and permit printing one-shot analog converted
887 data from a named Analog to Digital Converter.
892 depends on PARTITIONS
894 Read/modify/write the fields of Bootloader Control Block, usually
895 stored on the flash "misc" partition with its structure defined in:
896 https://android.googlesource.com/platform/bootable/recovery/+/master/
897 bootloader_message/include/bootloader_message/bootloader_message.h
899 Some real-life use-cases include (but are not limited to):
900 - Determine the "boot reason" (and act accordingly):
901 https://source.android.com/devices/bootloader/boot-reason
902 - Get/pass a list of commands from/to recovery:
903 https://android.googlesource.com/platform/bootable/recovery
904 - Inspect/dump the contents of the BCB fields
907 bool "bind/unbind - Bind or unbind a device to/from a driver"
910 Bind or unbind a device to/from a driver from the command line.
911 This is useful in situations where a device may be handled by several
912 drivers. For example, this can be used to bind a UDC to the usb ether
913 gadget driver from the command line.
916 bool "clk - Show clock frequencies"
919 Shows clock frequences by calling a sock_clk_dump() hook function.
920 This is depreated in favour of using the CLK uclass and accessing
921 clock values from associated drivers. However currently no command
925 bool "demo - Demonstration commands for driver model"
928 Provides a 'demo' command which can be used to play around with
929 driver model. To use this properly you will need to enable one or
930 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
931 Otherwise you will always get an empty list of devices. The demo
932 devices are defined in the sandbox device tree, so the easiest
933 option is to use sandbox and pass the -d point to sandbox's
940 Enables the command "dfu" which is used to have U-Boot create a DFU
941 class device via USB. This command requires that the "dfu_alt_info"
942 environment variable be set and define the alt settings to expose to
946 bool "dm - Access to driver model information"
949 Provides access to driver model data structures and information,
950 such as a list of devices, list of uclasses and the state of each
951 device (e.g. activated). This is not required for operation, but
952 can be useful to see the state of driver model for debugging or
956 bool "fastboot - Android fastboot support"
959 This enables the command "fastboot" which enables the Android
960 fastboot mode for the platform. Fastboot is a protocol for
961 downloading images, flashing and device control used on
962 Android devices. Fastboot requires either the network stack
963 enabled or support for acting as a USB device.
965 See doc/android/fastboot.rst for more information.
968 bool "flinfo, erase, protect"
970 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
973 flinfo - print FLASH memory information
975 protect - enable or disable FLASH write protection
984 config CMD_FPGA_LOADBP
985 bool "fpga loadbp - load partial bitstream (Xilinx only)"
988 Supports loading an FPGA device from a bitstream buffer containing
991 config CMD_FPGA_LOADFS
992 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
995 Supports loading an FPGA device from a FAT filesystem.
997 config CMD_FPGA_LOADMK
998 bool "fpga loadmk - load bitstream from image"
1001 Supports loading an FPGA device from a image generated by mkimage.
1003 config CMD_FPGA_LOADP
1004 bool "fpga loadp - load partial bitstream"
1007 Supports loading an FPGA device from a bitstream buffer containing
1008 a partial bitstream.
1010 config CMD_FPGA_LOAD_SECURE
1011 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1014 Enables the fpga loads command which is used to load secure
1015 (authenticated or encrypted or both) bitstreams on to FPGA.
1018 bool "fpgad - dump FPGA registers"
1020 (legacy, needs conversion to driver model)
1021 Provides a way to dump FPGA registers by calling the board-specific
1022 fpga_get_reg() function. This functions similarly to the 'md'
1026 bool "fuse - support for the fuse subssystem"
1028 (deprecated - needs conversion to driver model)
1029 This allows reading, sensing, programming or overriding fuses
1030 which control the behaviour of the device. The command uses the
1038 config CMD_GPIO_READ
1039 bool "gpio read - save GPIO value to variable"
1042 Enables the 'gpio read' command that saves the value
1043 of a GPIO pin to a variable.
1049 Control PWM channels, this allows invert/config/enable/disable PWM channels.
1052 bool "GPT (GUID Partition Table) command"
1053 select EFI_PARTITION
1054 select HAVE_BLOCK_DEVICE
1055 select PARTITION_UUIDS
1058 Enable the 'gpt' command to ready and write GPT style partition
1062 bool "GPT Random UUID generation"
1065 Enable the generation of partitions with random UUIDs if none
1068 config CMD_GPT_RENAME
1069 bool "GPT partition renaming commands"
1072 Enables the 'gpt' command to interchange names on two GPT
1073 partitions via the 'gpt swap' command or to rename single
1074 partitions via the 'rename' command.
1077 bool "ide - Support for IDE drivers"
1080 Provides an 'ide' command which allows accessing the IDE drive,
1081 resetting the IDE interface, printing the partition table and
1082 geting device info. It also enables the 'diskboot' command which
1083 permits booting from an IDE drive.
1086 bool "io - Support for performing I/O accesses"
1088 Provides an 'iod' command to display I/O space and an 'iow' command
1089 to write values to the I/O space. This can be useful for manually
1090 checking the state of devices during boot when debugging device
1094 bool "iotrace - Support for tracing I/O activity"
1096 Provides an 'iotrace' command which supports recording I/O reads and
1097 writes in a trace buffer in memory . It also maintains a checksum
1098 of the trace records (even if space is exhausted) so that the
1099 sequence of I/O accesses can be verified.
1101 When debugging drivers it is useful to see what I/O accesses were
1102 done and in what order.
1104 Even if the individual accesses are of little interest it can be
1105 useful to verify that the access pattern is consistent each time
1106 an operation is performed. In this case a checksum can be used to
1107 characterise the operation of a driver. The checksum can be compared
1108 across different runs of the operation to verify that the driver is
1111 In particular, when performing major refactoring of the driver, where
1112 the access pattern should not change, the checksum provides assurance
1113 that the refactoring work has not broken the driver.
1115 This works by sneaking into the io.h heder for an architecture and
1116 redirecting I/O accesses through iotrace's tracing mechanism.
1118 For now no commands are provided to examine the trace buffer. The
1119 format is fairly simple, so 'md' is a reasonable substitute.
1121 Note: The checksum feature is only useful for I/O regions where the
1122 contents do not change outside of software control. Where this is not
1123 suitable you can fall back to manually comparing the addresses. It
1124 might be useful to enhance tracing to only checksum the accesses and
1125 not the data read/written.
1135 bool "w1 - Support for Dallas 1-Wire protocol"
1137 Dallas 1-wire protocol support
1143 Load a binary file over serial line.
1149 Load an S-Record file over serial line
1153 bool "lsblk - list block drivers and devices"
1155 Print list of available block device drivers, and for each, the list
1156 of known block devices.
1159 bool "MBR (Master Boot Record) command"
1160 select DOS_PARTITION
1161 select HAVE_BLOCK_DEVICE
1163 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1164 style partition tables.
1170 Enable the command "misc" for accessing miscellaneous devices with
1171 a MISC uclass driver. The command provides listing all MISC devices
1172 as well as read and write functionalities via their drivers.
1178 MMC memory mapped support.
1182 config CMD_BKOPS_ENABLE
1183 bool "mmc bkops enable"
1186 Enable command for setting manual background operations handshake
1187 on a eMMC device. The feature is optionally available on eMMC devices
1188 conforming to standard >= 4.41.
1191 bool "Enable support for RPMB in the mmc command"
1192 depends on SUPPORT_EMMC_RPMB
1194 Enable the commands for reading, writing and programming the
1195 key for the Replay Protection Memory Block partition in eMMC.
1197 config CMD_MMC_SWRITE
1199 depends on MMC_WRITE
1202 Enable support for the "mmc swrite" command to write Android sparse
1211 Enable storage cloning over block devices, useful for
1212 initial flashing by external block device without network
1215 config CMD_OPTEE_RPMB
1216 bool "Enable read/write support on RPMB via OPTEE"
1217 depends on SUPPORT_EMMC_RPMB && OPTEE
1219 Enable the commands for reading, writing persistent named values
1220 in the Replay Protection Memory Block partition in eMMC by
1221 using Persistent Objects in OPTEE
1226 select MTD_PARTITIONS
1228 MTD commands support.
1232 depends on MULTIPLEXER
1234 List, select, and deselect mux controllers on the fly.
1238 default y if NAND_SUNXI
1239 depends on MTD_RAW_NAND
1244 config CMD_NAND_TRIMFFS
1245 bool "nand write.trimffs"
1246 default y if ARCH_SUNXI
1248 Allows one to skip empty pages when flashing something on a NAND.
1250 config CMD_NAND_LOCK_UNLOCK
1251 bool "nand lock/unlock"
1253 NAND locking support.
1255 config CMD_NAND_TORTURE
1258 NAND torture support.
1267 NVM Express device support
1270 bool "onenand - access to onenand device"
1273 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1274 various useful features. This command allows reading, writing,
1275 and erasing blocks. It allso provides a way to show and change
1276 bad blocks, and test the device.
1281 Enable the 'osd' command which allows to query information from and
1282 write text data to a on-screen display (OSD) device; a virtual device
1283 associated with a display capable of displaying a text overlay on the
1284 display it's associated with..
1288 select HAVE_BLOCK_DEVICE
1289 select PARTITION_UUIDS
1291 Read and display information about the partition table on
1295 bool "pci - Access PCI devices"
1297 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1298 used on some devices to allow the CPU to communicate with its
1299 peripherals. Sub-commands allow bus enumeration, displaying and
1300 changing configuration space and a few other features.
1303 bool "pinmux - show pins muxing"
1305 default y if PINCTRL
1307 Parse all available pin-controllers and show pins muxing. This
1308 is useful for debug purpoer to check the pin muxing and to know if
1309 a pin is configured as a GPIO or as an alternate function.
1314 Poweroff/Shutdown the system
1317 bool "read - Read binary data from a partition"
1319 Provides low-level access to the data in a partition.
1321 config CMD_REMOTEPROC
1323 depends on REMOTEPROC
1325 Support for Remote Processor control
1328 bool "sata - Access SATA subsystem"
1331 SATA (Serial Advanced Technology Attachment) is a serial bus
1332 standard for connecting to hard drives and other storage devices.
1333 This command provides information about attached devices and allows
1334 reading, writing and other operations.
1336 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1337 Attachment, where AT refers to an IBM AT (Advanced Technology)
1338 computer released in 1984.
1341 bool "saves - Save a file over serial in S-Record format"
1343 Provides a way to save a binary file using the Motorola S-Record
1344 format over the serial line.
1347 bool "scsi - Access to SCSI devices"
1350 This provides a 'scsi' command which provides access to SCSI (Small
1351 Computer System Interface) devices. The command provides a way to
1352 scan the bus, reset the bus, read and write data and get information
1356 bool "sdram - Print SDRAM configuration information"
1358 Provides information about attached SDRAM. This assumed that the
1359 SDRAM has an EEPROM with information that can be read using the
1360 I2C bus. This is only available on some boards.
1364 depends on DM_SPI_FLASH || SPI_FLASH
1365 default y if DM_SPI_FLASH
1370 bool "sf test - Allow testing of SPI flash"
1373 Provides a way to test that SPI flash is working correctly. The
1374 test is destructive, in that an area of SPI flash must be provided
1375 for the test to use. Performance information is also provided,
1376 measuring the performance of reading, writing and erasing in
1377 Mbps (Million Bits Per Second). This value should approximately
1378 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1379 everything is working properly.
1382 bool "sspi - Command to access spi device"
1385 SPI utility command.
1387 config DEFAULT_SPI_BUS
1388 int "default spi bus used by sspi command"
1392 config DEFAULT_SPI_MODE
1393 hex "default spi mode used by sspi command (see include/spi.h)"
1398 bool "tsi148 - Command to access tsi148 device"
1400 This provides various sub-commands to initialise and configure the
1401 Turndra tsi148 device. See the command help for full details.
1404 bool "Enable UFS - Universal Flash Subsystem commands"
1407 "This provides commands to initialise and configure universal flash
1411 bool "universe - Command to set up the Turndra Universe controller"
1413 This allows setting up the VMEbus provided by this controller.
1414 See the command help for full details.
1419 select HAVE_BLOCK_DEVICE
1425 select USB_FUNCTION_SDP
1427 Enables the command "sdp" which is used to have U-Boot emulating the
1428 Serial Download Protocol (SDP) via USB.
1432 depends on USB_FUNCTION_ROCKUSB
1434 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1435 read/write info, image to/from devices. This enable rockusb command
1436 support to communication with rockusb device. for more detail about
1437 this command, please read doc/README.rockusb.
1439 config CMD_USB_MASS_STORAGE
1440 bool "UMS usb mass storage"
1441 depends on USB_GADGET_DOWNLOAD
1442 select USB_FUNCTION_MASS_STORAGE
1443 depends on BLK && USB_GADGET
1445 Enables the command "ums" and the USB mass storage support to the
1446 export a block device: U-Boot, the USB device, acts as a simple
1447 external hard drive plugged on the host USB port.
1450 bool "Xen para-virtualized block device"
1454 Xen para-virtualized block device support
1459 depends on HAVE_BLOCK_DEVICE
1462 VirtIO block device support
1468 This provides commands to control the watchdog timer devices.
1474 Enable the command "axi" for accessing AXI (Advanced eXtensible
1475 Interface) busses, a on-chip interconnect specification for managing
1476 functional blocks in SoC designs, which is also often used in designs
1477 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1481 menu "Shell scripting commands"
1487 Echo args to console
1493 Return true/false on integer compare.
1499 Run script from memory
1505 Evaluate boolean and math expressions and store the result in an env
1507 Also supports loading the value at a memory location into a variable.
1508 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1510 config CMD_SETEXPR_FMT
1512 depends on CMD_SETEXPR
1514 Evaluate format string expression and store result in an environment
1519 menu "Android support commands"
1521 config CMD_AB_SELECT
1523 depends on ANDROID_AB
1525 On Android devices with more than one boot slot (multiple copies of
1526 the kernel and system images) this provides a command to select which
1527 slot should be used to boot from and register the boot attempt. This
1528 is used by the new A/B update model where one slot is updated in the
1529 background while running from the other slot.
1536 bool "Network commands"
1546 bootp - boot image via network using BOOTP/TFTP protocol
1550 depends on CMD_BOOTP
1552 Boot image via network using DHCP/TFTP protocol
1554 config BOOTP_MAY_FAIL
1555 bool "Allow for the BOOTP/DHCP server to not be found"
1556 depends on CMD_BOOTP
1558 If the DHCP server is not found after the configured retry count, the
1559 call will fail instead of starting over. This can be used to fail
1560 over to Link-local IP address configuration if the DHCP server is not
1563 config BOOTP_BOOTPATH
1564 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1566 depends on CMD_BOOTP
1568 Even though the config is called BOOTP_BOOTPATH, it stores the
1569 path in the variable 'rootpath'.
1571 config BOOTP_VENDOREX
1572 bool "Support vendor extensions from BOOTP/DHCP server"
1573 depends on CMD_BOOTP
1575 config BOOTP_BOOTFILESIZE
1576 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1577 depends on CMD_BOOTP
1580 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1582 depends on CMD_BOOTP
1584 The primary DNS server is stored as 'dnsip'. If two servers are
1585 returned, you must set BOOTP_DNS2 to store that second server IP
1589 bool "Store 'dnsip2' from BOOTP/DHCP server"
1590 depends on BOOTP_DNS
1592 If a DHCP client requests the DNS server IP from a DHCP server,
1593 it is possible that more than one DNS serverip is offered to the
1594 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1595 server IP will be stored in the additional environment
1596 variable "dnsip2". The first DNS serverip is always
1597 stored in the variable "dnsip", when BOOTP_DNS is defined.
1599 config BOOTP_GATEWAY
1600 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1602 depends on CMD_BOOTP
1604 config BOOTP_HOSTNAME
1605 bool "Request & store 'hostname' from BOOTP/DHCP server"
1607 depends on CMD_BOOTP
1609 The name may or may not be qualified with the local domain name.
1611 config BOOTP_PREFER_SERVERIP
1612 bool "serverip variable takes precedent over DHCP server IP."
1613 depends on CMD_BOOTP
1615 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1617 With this option enabled, the 'serverip' variable in the environment
1618 takes precedence over DHCP server IP and will only be set by the DHCP
1619 server if not already set in the environment.
1621 config BOOTP_SUBNETMASK
1622 bool "Request & store 'netmask' from BOOTP/DHCP server"
1624 depends on CMD_BOOTP
1626 config BOOTP_NISDOMAIN
1627 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1628 depends on CMD_BOOTP
1630 config BOOTP_NTPSERVER
1631 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1632 depends on CMD_BOOTP
1634 config BOOTP_TIMEOFFSET
1635 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1636 depends on CMD_BOOTP && CMD_SNTP
1641 Selecting this will allow capturing all Ethernet packets and store
1642 them in physical memory in a PCAP formated file,
1643 later to be analyzed by PCAP reader application (IE. WireShark).
1646 bool "Send PXE client arch to BOOTP/DHCP server"
1648 depends on CMD_BOOTP && CMD_PXE
1650 Supported for ARM, ARM64, and x86 for now.
1652 config BOOTP_PXE_CLIENTARCH
1654 depends on BOOTP_PXE
1655 default 0x16 if ARM64
1659 config BOOTP_VCI_STRING
1661 depends on CMD_BOOTP
1662 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1663 default "U-Boot.armv8" if ARM64
1664 default "U-Boot.arm" if ARM
1671 tftpboot - boot image via network using TFTP protocol
1675 depends on CMD_TFTPBOOT
1677 TFTP put command, for uploading files to a server
1681 depends on CMD_TFTPBOOT
1683 Act as a TFTP server and boot the first received file
1685 config NET_TFTP_VARS
1686 bool "Control TFTP timeout and count through environment"
1687 depends on CMD_TFTPBOOT
1690 If set, allows controlling the TFTP timeout through the
1691 environment variable tftptimeout, and the TFTP maximum
1692 timeout count through the variable tftptimeoutcountmax.
1693 If unset, timeout and maximum are hard-defined as 1 second
1694 and 10 timouts per TFTP transfer.
1699 Boot image via network using RARP/TFTP protocol
1705 Boot image via network using NFS protocol.
1708 int "Timeout in milliseconds for NFS mounts"
1712 Timeout in milliseconds used in NFS protocol. If you encounter
1713 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1720 If set, allows 802.3(clause 22) MII Management functions interface access
1721 The management interface specified in Clause 22 provides
1722 a simple, two signal, serial interface to connect a
1723 Station Management entity and a managed PHY for providing access
1724 to management parameters and services.
1725 The interface is referred to as the MII management interface.
1728 bool "Call mii_init() in the mii command"
1729 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1735 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1736 The MDIO interface is orthogonal to the MII interface and extends
1737 it by adding access to more registers through indirect addressing.
1742 Send ICMP ECHO_REQUEST to network host
1747 Perform CDP network configuration
1753 Synchronize RTC via network
1758 Lookup the IP of a hostname
1760 config CMD_LINK_LOCAL
1764 Acquire a network IP address using the link-local protocol
1771 Allow control of L2 Ethernet switch commands. These are supported
1772 by the vsc9953 Ethernet driver at present. Sub-commands allow
1773 operations such as enabling / disabling a port and
1774 viewing/maintaining the filtering database (FDB)
1780 Boot image via network using PXE protocol
1785 Wait for wake-on-lan Magic Packet
1789 menu "Misc commands"
1792 bool "Enable 'bmp' command"
1793 depends on LCD || DM_VIDEO || VIDEO
1795 This provides a way to obtain information about a BMP-format image
1796 and to display it. BMP (which presumably stands for BitMaP) is a
1797 file format defined by Microsoft which supports images of various
1798 depths, formats and compression methods. Headers on the file
1799 determine the formats used. This command can be used by first loading
1800 the image into RAM, then using this command to look at it or display
1803 config CMD_BOOTCOUNT
1805 depends on BOOTCOUNT_LIMIT
1807 Enable the bootcount command, which allows interrogation and
1808 reset of the bootcounter.
1811 bool "Enable board-specific commands"
1813 (deprecated: instead, please define a Kconfig option for each command)
1815 Some boards have board-specific commands which are only enabled
1816 during developemnt and need to be turned off for production. This
1817 option provides a way to control this. The commands that are enabled
1818 vary depending on the board.
1820 config CMD_BLOCK_CACHE
1821 bool "blkcache - control and stats for block cache"
1822 depends on BLOCK_CACHE
1823 default y if BLOCK_CACHE
1825 Enable the blkcache command, which can be used to control the
1826 operation of the cache functions.
1827 This is most useful when fine-tuning the operation of the cache
1828 during development, but also allows the cache to be disabled when
1829 it might hurt performance (e.g. when using the ums command).
1836 Enable the 'button' command which allows to get the status of
1837 buttons supported by the board. The buttonss can be listed with
1838 'button list' and state can be known with 'button <label>'.
1839 Any button drivers can be controlled with this command, e.g.
1843 bool "icache or dcache"
1845 Enable the "icache" and "dcache" commands
1847 config CMD_CONITRACE
1848 bool "conitrace - trace console input codes"
1850 Enable the 'conitrace' command which displays the codes received
1851 from the console input as hexadecimal numbers.
1854 bool "Enable clear screen command 'cls'"
1855 depends on DM_VIDEO || LCD || VIDEO
1858 Enable the 'cls' command which clears the screen contents
1859 on video frame buffer.
1862 bool "efidebug - display/configure UEFI environment"
1863 depends on EFI_LOADER
1864 select EFI_DEVICE_PATH_TO_TEXT
1866 Enable the 'efidebug' command which provides a subset of UEFI
1867 shell utility with simplified functionality. It will be useful
1868 particularly for managing boot parameters as well as examining
1869 various EFI status for debugging.
1871 config CMD_EXCEPTION
1872 bool "exception - raise exception"
1873 depends on ARM || RISCV || SANDBOX || X86
1875 Enable the 'exception' command which allows to raise an exception.
1882 Enable the 'led' command which allows for control of LEDs supported
1883 by the board. The LEDs can be listed with 'led list' and controlled
1884 with led on/off/togle/blink. Any LED drivers can be controlled with
1885 this command, e.g. led_gpio.
1892 Enable the 'date' command for getting/setting the time/date in RTC
1899 Enable the 'rtc' command for low-level access to RTC devices.
1904 Run commands and summarize execution time.
1907 bool "gettime - read elapsed time"
1909 Enable the 'gettime' command which reads the elapsed time since
1910 U-Boot started running. This shows the time in seconds and
1911 milliseconds. See also the 'bootstage' command which provides more
1912 flexibility for boot timing.
1919 Print bytes from the hardware random number generator.
1921 config CMD_KASLRSEED
1925 Set the kaslr-seed in the chosen node with entropy provided by a
1926 hardware random number generator.
1932 Delay execution for some time
1935 bool "support for multiprocessor commands"
1939 This enables commands to bringup different processors
1940 in multiprocessor cases.
1945 Access the system timer.
1951 This provides basic access to the U-Boot's sound support. The main
1952 feature is to play a beep.
1954 sound init - set up sound system
1955 sound play - play a sound
1961 Boot image via local extlinux.conf file
1967 This provides access to the QEMU firmware interface. The main
1968 feature is to allow easy loading of files passed to qemu-system
1969 via -kernel / -initrd
1974 This provides access to Linux PStore with Rammoops backend. The main
1975 feature is to allow to display or save PStore records.
1977 See doc/pstore.rst for more information.
1981 config CMD_PSTORE_MEM_ADDR
1982 hex "Memory Address"
1983 depends on CMD_PSTORE
1985 Base addr used for PStore ramoops memory, should be identical to
1986 ramoops.mem_address parameter used by kernel
1988 config CMD_PSTORE_MEM_SIZE
1990 depends on CMD_PSTORE
1993 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1994 parameter used by kernel, a power of 2 and larger than the sum of the
1997 config CMD_PSTORE_RECORD_SIZE
1998 hex "Dump record size"
1999 depends on CMD_PSTORE
2002 Size of each dump done on oops/panic, should be identical to
2003 ramoops.record_size parameter used by kernel and a power of 2
2006 config CMD_PSTORE_CONSOLE_SIZE
2007 hex "Kernel console log size"
2008 depends on CMD_PSTORE
2011 Size of kernel console log, should be identical to
2012 ramoops.console_size parameter used by kernel and a power of 2
2015 config CMD_PSTORE_FTRACE_SIZE
2016 hex "FTrace log size"
2017 depends on CMD_PSTORE
2020 Size of ftrace log, should be identical to ramoops.ftrace_size
2021 parameter used by kernel and a power of 2
2023 config CMD_PSTORE_PMSG_SIZE
2024 hex "User space message log size"
2025 depends on CMD_PSTORE
2028 Size of user space message log, should be identical to
2029 ramoops.pmsg_size parameter used by kernel and a power of 2
2031 config CMD_PSTORE_ECC_SIZE
2033 depends on CMD_PSTORE
2036 if non-zero, the option enables ECC support and specifies ECC buffer
2037 size in bytes (1 is a special value, means 16 bytes ECC), should be
2038 identical to ramoops.ramoops_ecc parameter used by kernel
2042 source "cmd/mvebu/Kconfig"
2045 bool "terminal - provides a way to attach a serial terminal"
2047 Provides a 'cu'-like serial terminal command. This can be used to
2048 access other serial ports from the system console. The terminal
2049 is very simple with no special processing of characters. As with
2050 cu, you can press ~. (tilde followed by period) to exit.
2053 bool "uuid, guid - generation of unique IDs"
2056 This enables two commands:
2058 uuid - generate random Universally Unique Identifier
2059 guid - generate Globally Unique Identifier based on random UUID
2061 The two commands are very similar except for the endianness of the
2066 source "cmd/ti/Kconfig"
2068 config CMD_BOOTSTAGE
2069 bool "Enable the 'bootstage' command"
2070 depends on BOOTSTAGE
2072 Add a 'bootstage' command which supports printing a report
2073 and un/stashing of bootstage data.
2075 menu "Power commands"
2077 bool "Enable Driver Model PMIC command"
2080 This is the pmic command, based on a driver model pmic's API.
2081 Command features are unchanged:
2082 - list - list pmic devices
2083 - pmic dev <id> - show or [set] operating pmic device (NEW)
2084 - pmic dump - dump registers
2085 - pmic read address - read byte of register at address
2086 - pmic write address - write byte to register at address
2087 The only one change for this command is 'dev' subcommand.
2089 config CMD_REGULATOR
2090 bool "Enable Driver Model REGULATOR command"
2091 depends on DM_REGULATOR
2093 This command is based on driver model regulator's API.
2094 User interface features:
2095 - list - list regulator devices
2096 - regulator dev <id> - show or [set] operating regulator device
2097 - regulator info - print constraints info
2098 - regulator status - print operating status
2099 - regulator value <val] <-f> - print/[set] voltage value [uV]
2100 - regulator current <val> - print/[set] current value [uA]
2101 - regulator mode <id> - print/[set] operating mode id
2102 - regulator enable - enable the regulator output
2103 - regulator disable - disable the regulator output
2105 The '-f' (force) option can be used for set the value which exceeds
2106 the limits, which are found in device-tree and are kept in regulator's
2107 uclass plat structure.
2111 menu "Security commands"
2113 bool "Enable the 'aes' command"
2116 This provides a means to encrypt and decrypt data using the AES
2117 (Advanced Encryption Standard). This algorithm uses a symetric key
2118 and is widely used as a streaming cipher. Different key lengths are
2119 supported by the algorithm but this command only supports 128 bits
2123 bool "Enable the 'blob' command"
2124 depends on !MX6ULL && !MX6SLL && !MX6SL
2125 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2127 This is used with the Freescale secure boot mechanism.
2129 Freescale's SEC block has built-in Blob Protocol which provides
2130 a method for protecting user-defined data across system power
2131 cycles. SEC block protects data in a data structure called a Blob,
2132 which provides both confidentiality and integrity protection.
2134 Encapsulating data as a blob
2135 Each time that the Blob Protocol is used to protect data, a
2136 different randomly generated key is used to encrypt the data.
2137 This random key is itself encrypted using a key which is derived
2138 from SoC's non-volatile secret key and a 16 bit Key identifier.
2139 The resulting encrypted key along with encrypted data is called a
2140 blob. The non-volatile secure key is available for use only during
2143 During decapsulation, the reverse process is performed to get back
2147 blob enc - encapsulating data as a cryptgraphic blob
2148 blob dec - decapsulating cryptgraphic blob to get the data
2152 blob enc src dst len km
2154 Encapsulate and create blob of data $len bytes long
2155 at address $src and store the result at address $dst.
2156 $km is the 16 byte key modifier is also required for
2157 generation/use as key for cryptographic operation. Key
2158 modifier should be 16 byte long.
2160 blob dec src dst len km
2162 Decapsulate the blob of data at address $src and
2163 store result of $len byte at addr $dst.
2164 $km is the 16 byte key modifier is also required for
2165 generation/use as key for cryptographic operation. Key
2166 modifier should be 16 byte long.
2169 bool "Support 'hash' command"
2172 This provides a way to hash data in memory using various supported
2173 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2174 saved to memory or to an environment variable. It is also possible
2175 to verify a hash against data in memory.
2178 bool "Support the 'hvc' command"
2179 depends on ARM_SMCCC
2181 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2182 development and testing.
2185 bool "Support the 'smc' command"
2186 depends on ARM_SMCCC
2188 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2189 development and testing.
2195 Add -v option to verify data against a hash.
2198 bool "scp03 - SCP03 enable and rotate/provision operations"
2201 This command provides access to a Trusted Application
2202 running in a TEE to request Secure Channel Protocol 03
2203 (SCP03) enablement and/or rotation of its SCP03 keys.
2212 bool "Enable the 'tpm' command"
2213 depends on TPM_V1 || TPM_V2
2214 select CMD_TPM_V1 if TPM_V1
2215 select CMD_TPM_V2 if TPM_V2
2217 This provides a means to talk to a TPM from the command line. A wide
2218 range of commands if provided - see 'tpm help' for details. The
2219 command requires a suitable TPM on your board and the correct driver
2225 bool "Enable the 'tpm test' command"
2228 This provides a a series of tests to confirm that the TPMv1.x is
2229 working correctly. The tests cover initialisation, non-volatile RAM,
2230 extend, global lock and checking that timing is within expectations.
2231 The tests pass correctly on Infineon TPMs but may need to be adjusted
2238 menu "Firmware commands"
2240 bool "Enable crosec command"
2244 Enable command-line access to the Chrome OS EC (Embedded
2245 Controller). This provides the 'crosec' command which has
2246 a number of sub-commands for performing EC tasks such as
2247 updating its flash, accessing a small saved context area
2248 and talking to the I2C bus behind the EC (if there is one).
2251 menu "Filesystem commands"
2253 bool "Enable the 'btrsubvol' command"
2256 This enables the 'btrsubvol' command to list subvolumes
2257 of a BTRFS filesystem. There are no special commands for
2258 listing BTRFS directories or loading BTRFS files - this
2259 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2260 when BTRFS is enabled (see FS_BTRFS).
2263 bool "Enable the 'cbfs' command"
2266 Define this to enable support for reading from a Coreboot
2267 filesystem. This is a ROM-based filesystem used for accessing files
2268 on systems that use coreboot as the first boot-loader and then load
2269 U-Boot to actually boot the Operating System. Available commands are
2270 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2273 bool "Enable the 'cramfs' command"
2274 depends on FS_CRAMFS
2276 This provides commands for dealing with CRAMFS (Compressed ROM
2277 filesystem). CRAMFS is useful when space is tight since files are
2278 compressed. Two commands are provided:
2280 cramfsls - lists files in a cramfs image
2281 cramfsload - loads a file from a cramfs image
2284 bool "EROFS command support"
2287 Support for the EROFS fs
2290 bool "ext2 command support"
2293 Enables EXT2 FS command
2296 bool "ext4 command support"
2299 Enables EXT4 FS command
2301 config CMD_EXT4_WRITE
2303 bool "ext4 write command support"
2306 Enables EXT4 FS write command
2309 bool "FAT command support"
2312 Support for the FAT fs
2315 bool "SquashFS command support"
2318 Enables SquashFS filesystem commands (e.g. load, ls).
2320 config CMD_FS_GENERIC
2321 bool "filesystem commands"
2323 Enables filesystem commands (e.g. load, ls) that work for multiple
2327 bool "fsuuid command"
2329 Enables fsuuid command for filesystem UUID.
2332 bool "jffs2 command"
2335 Enables commands to support the JFFS2 (Journalling Flash File System
2336 version 2) filesystem. This enables fsload, ls and fsinfo which
2337 provide the ability to load files, list directories and obtain
2338 filesystem information.
2341 string "Default device for JFFS2"
2342 depends on CMD_JFFS2
2345 The default device to use with the jffs2 command.
2347 config JFFS2_PART_OFFSET
2348 hex "Default offset within flash to locate the JFFS2 image"
2349 depends on CMD_JFFS2
2352 The default offset within flash to locate the JFFS2 image.
2354 config JFFS2_PART_SIZE
2355 hex "Default size of JFFS2 partition"
2356 depends on CMD_JFFS2
2359 The default size of the JFFS2 partition
2362 bool "MTD partition support"
2365 MTD partitioning tool support.
2366 It is strongly encouraged to avoid using this command
2367 anymore along with 'sf', 'nand', 'onenand'. One can still
2368 declare the partitions in the mtdparts environment variable
2369 but better use the MTD stack and the 'mtd' command instead.
2371 config CMD_MTDPARTS_SPREAD
2372 bool "Padd partition size to take account of bad blocks"
2373 depends on CMD_MTDPARTS
2375 This enables the 'spread' sub-command of the mtdparts command.
2376 This command will modify the existing mtdparts variable by increasing
2377 the size of the partitions such that 1) each partition's net size is
2378 at least as large as the size specified in the mtdparts variable and
2379 2) each partition starts on a good block.
2381 config CMD_MTDPARTS_SHOW_NET_SIZES
2382 bool "Show net size (w/o bad blocks) of partitions"
2383 depends on CMD_MTDPARTS
2385 Adds two columns to the printed partition table showing the
2386 effective usable size of a partition, if bad blocks are taken
2389 config MTDIDS_DEFAULT
2390 string "Default MTD IDs"
2391 depends on MTD || SPI_FLASH
2393 Defines a default MTD IDs list for use with MTD partitions in the
2394 Linux MTD command line partitions format.
2396 config MTDPARTS_DEFAULT
2397 string "Default MTD partition scheme"
2398 depends on MTD || SPI_FLASH
2400 Defines a default MTD partitioning scheme in the Linux MTD command
2401 line partitions format
2404 bool "reiser - Access to reiserfs filesystems"
2406 This provides two commands which operate on a resierfs filesystem,
2407 commonly used some years ago:
2409 reiserls - list files
2410 reiserload - load a file
2413 bool "yaffs2 - Access of YAFFS2 filesystem"
2417 This provides commands for accessing a YAFFS2 filesystem. Yet
2418 Another Flash Filesystem 2 is a filesystem designed specifically
2419 for NAND flash. It incorporates bad-block management and ensures
2420 that device writes are sequential regardless of filesystem
2424 bool "zfs - Access of ZFS filesystem"
2426 This provides commands to accessing a ZFS filesystem, commonly used
2427 on Solaris systems. Two sub-commands are provided:
2429 zfsls - list files in a directory
2430 zfsload - load a file
2432 See doc/README.zfs for more details.
2436 menu "Debug commands"
2438 config CMD_CBSYSINFO
2441 default y if SYS_COREBOOT
2443 This provides information about the coreboot sysinfo table stored in
2444 memory by coreboot before jumping to U-Boot. It can be useful for
2445 debugging the beaaviour of coreboot or U-Boot.
2448 bool "diag - Board diagnostics"
2450 This command provides access to board diagnostic tests. These are
2451 called Power-on Self Tests (POST). The command allows listing of
2452 available tests and running either all the tests, or specific tests
2456 bool "event - Show information about events"
2457 default y if EVENT_DEBUG
2459 This enables the 'event' command which provides information about
2460 events and event-handler routines. This can help to device event
2464 bool "irq - Show information about interrupts"
2465 depends on !ARM && !MIPS && !RISCV && !SH
2467 This enables two commands:
2469 interrupts - enable or disable interrupts
2470 irqinfo - print device-specific interrupt information
2473 bool "kgdb - Allow debugging of U-Boot with gdb"
2476 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2477 over a serial link for debugging purposes. This allows
2478 single-stepping, inspecting variables, etc. This is supported only
2479 on PowerPC at present.
2482 bool "log - Generation, control and access to logging"
2486 This provides access to logging features. It allows the output of
2487 log data to be controlled to a limited extent (setting up the default
2488 maximum log level for emitting of records). It also provides access
2489 to a command used for testing the log system.
2492 bool "trace - Support tracing of function calls and timing"
2496 Enables a command to control using of function tracing within
2497 U-Boot. This allows recording of call traces including timing
2498 information. The command can write data to memory for exporting
2499 for analysis (e.g. using bootchart). See doc/README.trace for full
2503 bool "avb - Android Verified Boot 2.0 operations"
2504 depends on AVB_VERIFY
2506 Enables a "avb" command to perform verification of partitions using
2507 Android Verified Boot 2.0 functionality. It includes such subcommands:
2508 avb init - initialize avb2 subsystem
2509 avb read_rb - read rollback index
2510 avb write_rb - write rollback index
2511 avb is_unlocked - check device lock state
2512 avb get_uuid - read and print uuid of a partition
2513 avb read_part - read data from partition
2514 avb read_part_hex - read data from partition and output to stdout
2515 avb write_part - write data to partition
2516 avb verify - run full verification chain
2518 config CMD_STACKPROTECTOR_TEST
2519 bool "Test command for stack protector"
2520 depends on STACKPROTECTOR
2522 Enable stackprot_test command
2523 The stackprot_test command will force a stack overrun to test
2524 the stack smashing detection mechanisms.
2529 tristate "Enable UBI - Unsorted block images commands"
2532 UBI is a software layer above MTD layer which admits use of LVM-like
2533 logical volumes on top of MTD devices, hides some complexities of
2534 flash chips like wear and bad blocks and provides some other useful
2535 capabilities. Please, consult the MTD web site for more details
2536 (www.linux-mtd.infradead.org). Activate this option if you want
2537 to use U-Boot UBI commands.
2538 It is also strongly encouraged to also enable CONFIG_MTD to get full
2541 config CMD_UBI_RENAME
2542 bool "Enable rename"
2545 Enable a "ubi" command to rename ubi volume:
2546 ubi rename <oldname> <newname>
2549 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2551 default y if CMD_UBI
2554 UBIFS is a file system for flash devices which works on top of UBI.
2556 config MMC_SPEED_MODE_SET
2557 bool "set speed mode using mmc command"
2561 Enable setting speed mode using mmc rescan and mmc dev commands.
2562 The speed mode is provided as the last argument in these commands
2563 and is indicated using the index from enum bus_mode in
2564 include/mmc.h. A speed mode can be set only if it has already
2565 been enabled in the device tree.
projects / platform / kernel / u-boot.git / blob