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 depends on PARTITIONS
1289 select HAVE_BLOCK_DEVICE
1290 select PARTITION_UUIDS
1292 Read and display information about the partition table on
1296 bool "pci - Access PCI devices"
1298 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1299 used on some devices to allow the CPU to communicate with its
1300 peripherals. Sub-commands allow bus enumeration, displaying and
1301 changing configuration space and a few other features.
1304 bool "pinmux - show pins muxing"
1306 default y if PINCTRL
1308 Parse all available pin-controllers and show pins muxing. This
1309 is useful for debug purpoer to check the pin muxing and to know if
1310 a pin is configured as a GPIO or as an alternate function.
1315 Poweroff/Shutdown the system
1318 bool "read - Read binary data from a partition"
1320 Provides low-level access to the data in a partition.
1322 config CMD_REMOTEPROC
1324 depends on REMOTEPROC
1326 Support for Remote Processor control
1329 bool "sata - Access SATA subsystem"
1332 SATA (Serial Advanced Technology Attachment) is a serial bus
1333 standard for connecting to hard drives and other storage devices.
1334 This command provides information about attached devices and allows
1335 reading, writing and other operations.
1337 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1338 Attachment, where AT refers to an IBM AT (Advanced Technology)
1339 computer released in 1984.
1342 bool "saves - Save a file over serial in S-Record format"
1344 Provides a way to save a binary file using the Motorola S-Record
1345 format over the serial line.
1348 bool "scsi - Access to SCSI devices"
1351 This provides a 'scsi' command which provides access to SCSI (Small
1352 Computer System Interface) devices. The command provides a way to
1353 scan the bus, reset the bus, read and write data and get information
1357 bool "sdram - Print SDRAM configuration information"
1359 Provides information about attached SDRAM. This assumed that the
1360 SDRAM has an EEPROM with information that can be read using the
1361 I2C bus. This is only available on some boards.
1365 depends on DM_SPI_FLASH || SPI_FLASH
1366 default y if DM_SPI_FLASH
1371 bool "sf test - Allow testing of SPI flash"
1374 Provides a way to test that SPI flash is working correctly. The
1375 test is destructive, in that an area of SPI flash must be provided
1376 for the test to use. Performance information is also provided,
1377 measuring the performance of reading, writing and erasing in
1378 Mbps (Million Bits Per Second). This value should approximately
1379 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1380 everything is working properly.
1383 bool "sspi - Command to access spi device"
1386 SPI utility command.
1388 config DEFAULT_SPI_BUS
1389 int "default spi bus used by sspi command"
1393 config DEFAULT_SPI_MODE
1394 hex "default spi mode used by sspi command (see include/spi.h)"
1399 bool "tsi148 - Command to access tsi148 device"
1401 This provides various sub-commands to initialise and configure the
1402 Turndra tsi148 device. See the command help for full details.
1405 bool "Enable UFS - Universal Flash Subsystem commands"
1408 "This provides commands to initialise and configure universal flash
1412 bool "universe - Command to set up the Turndra Universe controller"
1414 This allows setting up the VMEbus provided by this controller.
1415 See the command help for full details.
1420 select HAVE_BLOCK_DEVICE
1426 select USB_FUNCTION_SDP
1428 Enables the command "sdp" which is used to have U-Boot emulating the
1429 Serial Download Protocol (SDP) via USB.
1433 depends on USB_FUNCTION_ROCKUSB
1435 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1436 read/write info, image to/from devices. This enable rockusb command
1437 support to communication with rockusb device. for more detail about
1438 this command, please read doc/README.rockusb.
1440 config CMD_USB_MASS_STORAGE
1441 bool "UMS usb mass storage"
1442 depends on USB_GADGET_DOWNLOAD
1443 select USB_FUNCTION_MASS_STORAGE
1444 depends on BLK && USB_GADGET
1446 Enables the command "ums" and the USB mass storage support to the
1447 export a block device: U-Boot, the USB device, acts as a simple
1448 external hard drive plugged on the host USB port.
1451 bool "Xen para-virtualized block device"
1455 Xen para-virtualized block device support
1460 depends on HAVE_BLOCK_DEVICE
1463 VirtIO block device support
1469 This provides commands to control the watchdog timer devices.
1475 Enable the command "axi" for accessing AXI (Advanced eXtensible
1476 Interface) busses, a on-chip interconnect specification for managing
1477 functional blocks in SoC designs, which is also often used in designs
1478 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1482 menu "Shell scripting commands"
1488 Echo args to console
1494 Return true/false on integer compare.
1500 Run script from memory
1506 Evaluate boolean and math expressions and store the result in an env
1508 Also supports loading the value at a memory location into a variable.
1509 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1511 config CMD_SETEXPR_FMT
1513 depends on CMD_SETEXPR
1515 Evaluate format string expression and store result in an environment
1520 menu "Android support commands"
1522 config CMD_AB_SELECT
1524 depends on ANDROID_AB
1526 On Android devices with more than one boot slot (multiple copies of
1527 the kernel and system images) this provides a command to select which
1528 slot should be used to boot from and register the boot attempt. This
1529 is used by the new A/B update model where one slot is updated in the
1530 background while running from the other slot.
1537 bool "Network commands"
1547 bootp - boot image via network using BOOTP/TFTP protocol
1551 depends on CMD_BOOTP
1553 Boot image via network using DHCP/TFTP protocol
1555 config BOOTP_MAY_FAIL
1556 bool "Allow for the BOOTP/DHCP server to not be found"
1557 depends on CMD_BOOTP
1559 If the DHCP server is not found after the configured retry count, the
1560 call will fail instead of starting over. This can be used to fail
1561 over to Link-local IP address configuration if the DHCP server is not
1564 config BOOTP_BOOTPATH
1565 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1567 depends on CMD_BOOTP
1569 Even though the config is called BOOTP_BOOTPATH, it stores the
1570 path in the variable 'rootpath'.
1572 config BOOTP_VENDOREX
1573 bool "Support vendor extensions from BOOTP/DHCP server"
1574 depends on CMD_BOOTP
1576 config BOOTP_BOOTFILESIZE
1577 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1578 depends on CMD_BOOTP
1581 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1583 depends on CMD_BOOTP
1585 The primary DNS server is stored as 'dnsip'. If two servers are
1586 returned, you must set BOOTP_DNS2 to store that second server IP
1590 bool "Store 'dnsip2' from BOOTP/DHCP server"
1591 depends on BOOTP_DNS
1593 If a DHCP client requests the DNS server IP from a DHCP server,
1594 it is possible that more than one DNS serverip is offered to the
1595 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1596 server IP will be stored in the additional environment
1597 variable "dnsip2". The first DNS serverip is always
1598 stored in the variable "dnsip", when BOOTP_DNS is defined.
1600 config BOOTP_GATEWAY
1601 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1603 depends on CMD_BOOTP
1605 config BOOTP_HOSTNAME
1606 bool "Request & store 'hostname' from BOOTP/DHCP server"
1608 depends on CMD_BOOTP
1610 The name may or may not be qualified with the local domain name.
1612 config BOOTP_PREFER_SERVERIP
1613 bool "serverip variable takes precedent over DHCP server IP."
1614 depends on CMD_BOOTP
1616 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1618 With this option enabled, the 'serverip' variable in the environment
1619 takes precedence over DHCP server IP and will only be set by the DHCP
1620 server if not already set in the environment.
1622 config BOOTP_SUBNETMASK
1623 bool "Request & store 'netmask' from BOOTP/DHCP server"
1625 depends on CMD_BOOTP
1627 config BOOTP_NISDOMAIN
1628 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1629 depends on CMD_BOOTP
1631 config BOOTP_NTPSERVER
1632 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1633 depends on CMD_BOOTP
1635 config BOOTP_TIMEOFFSET
1636 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1637 depends on CMD_BOOTP && CMD_SNTP
1642 Selecting this will allow capturing all Ethernet packets and store
1643 them in physical memory in a PCAP formated file,
1644 later to be analyzed by PCAP reader application (IE. WireShark).
1647 bool "Send PXE client arch to BOOTP/DHCP server"
1649 depends on CMD_BOOTP && CMD_PXE
1651 Supported for ARM, ARM64, and x86 for now.
1653 config BOOTP_PXE_CLIENTARCH
1655 depends on BOOTP_PXE
1656 default 0x16 if ARM64
1660 config BOOTP_VCI_STRING
1662 depends on CMD_BOOTP
1663 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1664 default "U-Boot.armv8" if ARM64
1665 default "U-Boot.arm" if ARM
1672 tftpboot - boot image via network using TFTP protocol
1676 depends on CMD_TFTPBOOT
1678 TFTP put command, for uploading files to a server
1682 depends on CMD_TFTPBOOT
1684 Act as a TFTP server and boot the first received file
1686 config NET_TFTP_VARS
1687 bool "Control TFTP timeout and count through environment"
1688 depends on CMD_TFTPBOOT
1691 If set, allows controlling the TFTP timeout through the
1692 environment variable tftptimeout, and the TFTP maximum
1693 timeout count through the variable tftptimeoutcountmax.
1694 If unset, timeout and maximum are hard-defined as 1 second
1695 and 10 timouts per TFTP transfer.
1700 Boot image via network using RARP/TFTP protocol
1706 Boot image via network using NFS protocol.
1709 int "Timeout in milliseconds for NFS mounts"
1713 Timeout in milliseconds used in NFS protocol. If you encounter
1714 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1721 If set, allows 802.3(clause 22) MII Management functions interface access
1722 The management interface specified in Clause 22 provides
1723 a simple, two signal, serial interface to connect a
1724 Station Management entity and a managed PHY for providing access
1725 to management parameters and services.
1726 The interface is referred to as the MII management interface.
1729 bool "Call mii_init() in the mii command"
1730 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1736 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1737 The MDIO interface is orthogonal to the MII interface and extends
1738 it by adding access to more registers through indirect addressing.
1743 Send ICMP ECHO_REQUEST to network host
1748 Perform CDP network configuration
1754 Synchronize RTC via network
1759 Lookup the IP of a hostname
1761 config CMD_LINK_LOCAL
1765 Acquire a network IP address using the link-local protocol
1772 Allow control of L2 Ethernet switch commands. These are supported
1773 by the vsc9953 Ethernet driver at present. Sub-commands allow
1774 operations such as enabling / disabling a port and
1775 viewing/maintaining the filtering database (FDB)
1781 Boot image via network using PXE protocol
1786 Wait for wake-on-lan Magic Packet
1790 menu "Misc commands"
1793 bool "Enable 'bmp' command"
1794 depends on LCD || DM_VIDEO || VIDEO
1796 This provides a way to obtain information about a BMP-format image
1797 and to display it. BMP (which presumably stands for BitMaP) is a
1798 file format defined by Microsoft which supports images of various
1799 depths, formats and compression methods. Headers on the file
1800 determine the formats used. This command can be used by first loading
1801 the image into RAM, then using this command to look at it or display
1804 config CMD_BOOTCOUNT
1806 depends on BOOTCOUNT_LIMIT
1808 Enable the bootcount command, which allows interrogation and
1809 reset of the bootcounter.
1812 bool "Enable board-specific commands"
1814 (deprecated: instead, please define a Kconfig option for each command)
1816 Some boards have board-specific commands which are only enabled
1817 during developemnt and need to be turned off for production. This
1818 option provides a way to control this. The commands that are enabled
1819 vary depending on the board.
1821 config CMD_BLOCK_CACHE
1822 bool "blkcache - control and stats for block cache"
1823 depends on BLOCK_CACHE
1824 default y if BLOCK_CACHE
1826 Enable the blkcache command, which can be used to control the
1827 operation of the cache functions.
1828 This is most useful when fine-tuning the operation of the cache
1829 during development, but also allows the cache to be disabled when
1830 it might hurt performance (e.g. when using the ums command).
1837 Enable the 'button' command which allows to get the status of
1838 buttons supported by the board. The buttonss can be listed with
1839 'button list' and state can be known with 'button <label>'.
1840 Any button drivers can be controlled with this command, e.g.
1844 bool "icache or dcache"
1846 Enable the "icache" and "dcache" commands
1848 config CMD_CONITRACE
1849 bool "conitrace - trace console input codes"
1851 Enable the 'conitrace' command which displays the codes received
1852 from the console input as hexadecimal numbers.
1855 bool "Enable clear screen command 'cls'"
1856 depends on DM_VIDEO || LCD || VIDEO
1859 Enable the 'cls' command which clears the screen contents
1860 on video frame buffer.
1863 bool "efidebug - display/configure UEFI environment"
1864 depends on EFI_LOADER
1865 select EFI_DEVICE_PATH_TO_TEXT
1867 Enable the 'efidebug' command which provides a subset of UEFI
1868 shell utility with simplified functionality. It will be useful
1869 particularly for managing boot parameters as well as examining
1870 various EFI status for debugging.
1872 config CMD_EXCEPTION
1873 bool "exception - raise exception"
1874 depends on ARM || RISCV || SANDBOX || X86
1876 Enable the 'exception' command which allows to raise an exception.
1883 Enable the 'led' command which allows for control of LEDs supported
1884 by the board. The LEDs can be listed with 'led list' and controlled
1885 with led on/off/togle/blink. Any LED drivers can be controlled with
1886 this command, e.g. led_gpio.
1893 Enable the 'date' command for getting/setting the time/date in RTC
1900 Enable the 'rtc' command for low-level access to RTC devices.
1905 Run commands and summarize execution time.
1908 bool "gettime - read elapsed time"
1910 Enable the 'gettime' command which reads the elapsed time since
1911 U-Boot started running. This shows the time in seconds and
1912 milliseconds. See also the 'bootstage' command which provides more
1913 flexibility for boot timing.
1920 Print bytes from the hardware random number generator.
1922 config CMD_KASLRSEED
1926 Set the kaslr-seed in the chosen node with entropy provided by a
1927 hardware random number generator.
1933 Delay execution for some time
1936 bool "support for multiprocessor commands"
1940 This enables commands to bringup different processors
1941 in multiprocessor cases.
1946 Access the system timer.
1952 This provides basic access to the U-Boot's sound support. The main
1953 feature is to play a beep.
1955 sound init - set up sound system
1956 sound play - play a sound
1962 Boot image via local extlinux.conf file
1968 This provides access to the QEMU firmware interface. The main
1969 feature is to allow easy loading of files passed to qemu-system
1970 via -kernel / -initrd
1975 This provides access to Linux PStore with Rammoops backend. The main
1976 feature is to allow to display or save PStore records.
1978 See doc/pstore.rst for more information.
1982 config CMD_PSTORE_MEM_ADDR
1983 hex "Memory Address"
1984 depends on CMD_PSTORE
1986 Base addr used for PStore ramoops memory, should be identical to
1987 ramoops.mem_address parameter used by kernel
1989 config CMD_PSTORE_MEM_SIZE
1991 depends on CMD_PSTORE
1994 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1995 parameter used by kernel, a power of 2 and larger than the sum of the
1998 config CMD_PSTORE_RECORD_SIZE
1999 hex "Dump record size"
2000 depends on CMD_PSTORE
2003 Size of each dump done on oops/panic, should be identical to
2004 ramoops.record_size parameter used by kernel and a power of 2
2007 config CMD_PSTORE_CONSOLE_SIZE
2008 hex "Kernel console log size"
2009 depends on CMD_PSTORE
2012 Size of kernel console log, should be identical to
2013 ramoops.console_size parameter used by kernel and a power of 2
2016 config CMD_PSTORE_FTRACE_SIZE
2017 hex "FTrace log size"
2018 depends on CMD_PSTORE
2021 Size of ftrace log, should be identical to ramoops.ftrace_size
2022 parameter used by kernel and a power of 2
2024 config CMD_PSTORE_PMSG_SIZE
2025 hex "User space message log size"
2026 depends on CMD_PSTORE
2029 Size of user space message log, should be identical to
2030 ramoops.pmsg_size parameter used by kernel and a power of 2
2032 config CMD_PSTORE_ECC_SIZE
2034 depends on CMD_PSTORE
2037 if non-zero, the option enables ECC support and specifies ECC buffer
2038 size in bytes (1 is a special value, means 16 bytes ECC), should be
2039 identical to ramoops.ramoops_ecc parameter used by kernel
2043 source "cmd/mvebu/Kconfig"
2046 bool "terminal - provides a way to attach a serial terminal"
2048 Provides a 'cu'-like serial terminal command. This can be used to
2049 access other serial ports from the system console. The terminal
2050 is very simple with no special processing of characters. As with
2051 cu, you can press ~. (tilde followed by period) to exit.
2054 bool "uuid, guid - generation of unique IDs"
2057 This enables two commands:
2059 uuid - generate random Universally Unique Identifier
2060 guid - generate Globally Unique Identifier based on random UUID
2062 The two commands are very similar except for the endianness of the
2067 source "cmd/ti/Kconfig"
2069 config CMD_BOOTSTAGE
2070 bool "Enable the 'bootstage' command"
2071 depends on BOOTSTAGE
2073 Add a 'bootstage' command which supports printing a report
2074 and un/stashing of bootstage data.
2076 menu "Power commands"
2078 bool "Enable Driver Model PMIC command"
2081 This is the pmic command, based on a driver model pmic's API.
2082 Command features are unchanged:
2083 - list - list pmic devices
2084 - pmic dev <id> - show or [set] operating pmic device (NEW)
2085 - pmic dump - dump registers
2086 - pmic read address - read byte of register at address
2087 - pmic write address - write byte to register at address
2088 The only one change for this command is 'dev' subcommand.
2090 config CMD_REGULATOR
2091 bool "Enable Driver Model REGULATOR command"
2092 depends on DM_REGULATOR
2094 This command is based on driver model regulator's API.
2095 User interface features:
2096 - list - list regulator devices
2097 - regulator dev <id> - show or [set] operating regulator device
2098 - regulator info - print constraints info
2099 - regulator status - print operating status
2100 - regulator value <val] <-f> - print/[set] voltage value [uV]
2101 - regulator current <val> - print/[set] current value [uA]
2102 - regulator mode <id> - print/[set] operating mode id
2103 - regulator enable - enable the regulator output
2104 - regulator disable - disable the regulator output
2106 The '-f' (force) option can be used for set the value which exceeds
2107 the limits, which are found in device-tree and are kept in regulator's
2108 uclass plat structure.
2112 menu "Security commands"
2114 bool "Enable the 'aes' command"
2117 This provides a means to encrypt and decrypt data using the AES
2118 (Advanced Encryption Standard). This algorithm uses a symetric key
2119 and is widely used as a streaming cipher. Different key lengths are
2120 supported by the algorithm but this command only supports 128 bits
2124 bool "Enable the 'blob' command"
2125 depends on !MX6ULL && !MX6SLL && !MX6SL
2126 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2128 This is used with the Freescale secure boot mechanism.
2130 Freescale's SEC block has built-in Blob Protocol which provides
2131 a method for protecting user-defined data across system power
2132 cycles. SEC block protects data in a data structure called a Blob,
2133 which provides both confidentiality and integrity protection.
2135 Encapsulating data as a blob
2136 Each time that the Blob Protocol is used to protect data, a
2137 different randomly generated key is used to encrypt the data.
2138 This random key is itself encrypted using a key which is derived
2139 from SoC's non-volatile secret key and a 16 bit Key identifier.
2140 The resulting encrypted key along with encrypted data is called a
2141 blob. The non-volatile secure key is available for use only during
2144 During decapsulation, the reverse process is performed to get back
2148 blob enc - encapsulating data as a cryptgraphic blob
2149 blob dec - decapsulating cryptgraphic blob to get the data
2153 blob enc src dst len km
2155 Encapsulate and create blob of data $len bytes long
2156 at address $src and store the result at address $dst.
2157 $km is the 16 byte key modifier is also required for
2158 generation/use as key for cryptographic operation. Key
2159 modifier should be 16 byte long.
2161 blob dec src dst len km
2163 Decapsulate the blob of data at address $src and
2164 store result of $len byte at addr $dst.
2165 $km is the 16 byte key modifier is also required for
2166 generation/use as key for cryptographic operation. Key
2167 modifier should be 16 byte long.
2170 bool "Support 'hash' command"
2173 This provides a way to hash data in memory using various supported
2174 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2175 saved to memory or to an environment variable. It is also possible
2176 to verify a hash against data in memory.
2179 bool "Support the 'hvc' command"
2180 depends on ARM_SMCCC
2182 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2183 development and testing.
2186 bool "Support the 'smc' command"
2187 depends on ARM_SMCCC
2189 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2190 development and testing.
2196 Add -v option to verify data against a hash.
2199 bool "scp03 - SCP03 enable and rotate/provision operations"
2202 This command provides access to a Trusted Application
2203 running in a TEE to request Secure Channel Protocol 03
2204 (SCP03) enablement and/or rotation of its SCP03 keys.
2213 bool "Enable the 'tpm' command"
2214 depends on TPM_V1 || TPM_V2
2215 select CMD_TPM_V1 if TPM_V1
2216 select CMD_TPM_V2 if TPM_V2
2218 This provides a means to talk to a TPM from the command line. A wide
2219 range of commands if provided - see 'tpm help' for details. The
2220 command requires a suitable TPM on your board and the correct driver
2226 bool "Enable the 'tpm test' command"
2229 This provides a a series of tests to confirm that the TPMv1.x is
2230 working correctly. The tests cover initialisation, non-volatile RAM,
2231 extend, global lock and checking that timing is within expectations.
2232 The tests pass correctly on Infineon TPMs but may need to be adjusted
2239 menu "Firmware commands"
2241 bool "Enable crosec command"
2245 Enable command-line access to the Chrome OS EC (Embedded
2246 Controller). This provides the 'crosec' command which has
2247 a number of sub-commands for performing EC tasks such as
2248 updating its flash, accessing a small saved context area
2249 and talking to the I2C bus behind the EC (if there is one).
2252 menu "Filesystem commands"
2254 bool "Enable the 'btrsubvol' command"
2257 This enables the 'btrsubvol' command to list subvolumes
2258 of a BTRFS filesystem. There are no special commands for
2259 listing BTRFS directories or loading BTRFS files - this
2260 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2261 when BTRFS is enabled (see FS_BTRFS).
2264 bool "Enable the 'cbfs' command"
2267 Define this to enable support for reading from a Coreboot
2268 filesystem. This is a ROM-based filesystem used for accessing files
2269 on systems that use coreboot as the first boot-loader and then load
2270 U-Boot to actually boot the Operating System. Available commands are
2271 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2274 bool "Enable the 'cramfs' command"
2275 depends on FS_CRAMFS
2277 This provides commands for dealing with CRAMFS (Compressed ROM
2278 filesystem). CRAMFS is useful when space is tight since files are
2279 compressed. Two commands are provided:
2281 cramfsls - lists files in a cramfs image
2282 cramfsload - loads a file from a cramfs image
2285 bool "EROFS command support"
2288 Support for the EROFS fs
2291 bool "ext2 command support"
2294 Enables EXT2 FS command
2297 bool "ext4 command support"
2300 Enables EXT4 FS command
2302 config CMD_EXT4_WRITE
2304 bool "ext4 write command support"
2307 Enables EXT4 FS write command
2310 bool "FAT command support"
2313 Support for the FAT fs
2316 bool "SquashFS command support"
2319 Enables SquashFS filesystem commands (e.g. load, ls).
2321 config CMD_FS_GENERIC
2322 bool "filesystem commands"
2324 Enables filesystem commands (e.g. load, ls) that work for multiple
2328 bool "fsuuid command"
2330 Enables fsuuid command for filesystem UUID.
2333 bool "jffs2 command"
2336 Enables commands to support the JFFS2 (Journalling Flash File System
2337 version 2) filesystem. This enables fsload, ls and fsinfo which
2338 provide the ability to load files, list directories and obtain
2339 filesystem information.
2342 string "Default device for JFFS2"
2343 depends on CMD_JFFS2
2346 The default device to use with the jffs2 command.
2348 config JFFS2_PART_OFFSET
2349 hex "Default offset within flash to locate the JFFS2 image"
2350 depends on CMD_JFFS2
2353 The default offset within flash to locate the JFFS2 image.
2355 config JFFS2_PART_SIZE
2356 hex "Default size of JFFS2 partition"
2357 depends on CMD_JFFS2
2360 The default size of the JFFS2 partition
2363 bool "MTD partition support"
2366 MTD partitioning tool support.
2367 It is strongly encouraged to avoid using this command
2368 anymore along with 'sf', 'nand', 'onenand'. One can still
2369 declare the partitions in the mtdparts environment variable
2370 but better use the MTD stack and the 'mtd' command instead.
2372 config CMD_MTDPARTS_SPREAD
2373 bool "Padd partition size to take account of bad blocks"
2374 depends on CMD_MTDPARTS
2376 This enables the 'spread' sub-command of the mtdparts command.
2377 This command will modify the existing mtdparts variable by increasing
2378 the size of the partitions such that 1) each partition's net size is
2379 at least as large as the size specified in the mtdparts variable and
2380 2) each partition starts on a good block.
2382 config CMD_MTDPARTS_SHOW_NET_SIZES
2383 bool "Show net size (w/o bad blocks) of partitions"
2384 depends on CMD_MTDPARTS
2386 Adds two columns to the printed partition table showing the
2387 effective usable size of a partition, if bad blocks are taken
2390 config MTDIDS_DEFAULT
2391 string "Default MTD IDs"
2392 depends on MTD || SPI_FLASH
2394 Defines a default MTD IDs list for use with MTD partitions in the
2395 Linux MTD command line partitions format.
2397 config MTDPARTS_DEFAULT
2398 string "Default MTD partition scheme"
2399 depends on MTD || SPI_FLASH
2401 Defines a default MTD partitioning scheme in the Linux MTD command
2402 line partitions format
2405 bool "reiser - Access to reiserfs filesystems"
2407 This provides two commands which operate on a resierfs filesystem,
2408 commonly used some years ago:
2410 reiserls - list files
2411 reiserload - load a file
2414 bool "yaffs2 - Access of YAFFS2 filesystem"
2418 This provides commands for accessing a YAFFS2 filesystem. Yet
2419 Another Flash Filesystem 2 is a filesystem designed specifically
2420 for NAND flash. It incorporates bad-block management and ensures
2421 that device writes are sequential regardless of filesystem
2425 bool "zfs - Access of ZFS filesystem"
2427 This provides commands to accessing a ZFS filesystem, commonly used
2428 on Solaris systems. Two sub-commands are provided:
2430 zfsls - list files in a directory
2431 zfsload - load a file
2433 See doc/README.zfs for more details.
2437 menu "Debug commands"
2439 config CMD_CBSYSINFO
2442 default y if SYS_COREBOOT
2444 This provides information about the coreboot sysinfo table stored in
2445 memory by coreboot before jumping to U-Boot. It can be useful for
2446 debugging the beaaviour of coreboot or U-Boot.
2449 bool "diag - Board diagnostics"
2451 This command provides access to board diagnostic tests. These are
2452 called Power-on Self Tests (POST). The command allows listing of
2453 available tests and running either all the tests, or specific tests
2457 bool "event - Show information about events"
2458 default y if EVENT_DEBUG
2460 This enables the 'event' command which provides information about
2461 events and event-handler routines. This can help to device event
2465 bool "irq - Show information about interrupts"
2466 depends on !ARM && !MIPS && !RISCV && !SH
2468 This enables two commands:
2470 interrupts - enable or disable interrupts
2471 irqinfo - print device-specific interrupt information
2474 bool "kgdb - Allow debugging of U-Boot with gdb"
2477 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2478 over a serial link for debugging purposes. This allows
2479 single-stepping, inspecting variables, etc. This is supported only
2480 on PowerPC at present.
2483 bool "log - Generation, control and access to logging"
2487 This provides access to logging features. It allows the output of
2488 log data to be controlled to a limited extent (setting up the default
2489 maximum log level for emitting of records). It also provides access
2490 to a command used for testing the log system.
2493 bool "trace - Support tracing of function calls and timing"
2497 Enables a command to control using of function tracing within
2498 U-Boot. This allows recording of call traces including timing
2499 information. The command can write data to memory for exporting
2500 for analysis (e.g. using bootchart). See doc/README.trace for full
2504 bool "avb - Android Verified Boot 2.0 operations"
2505 depends on AVB_VERIFY
2507 Enables a "avb" command to perform verification of partitions using
2508 Android Verified Boot 2.0 functionality. It includes such subcommands:
2509 avb init - initialize avb2 subsystem
2510 avb read_rb - read rollback index
2511 avb write_rb - write rollback index
2512 avb is_unlocked - check device lock state
2513 avb get_uuid - read and print uuid of a partition
2514 avb read_part - read data from partition
2515 avb read_part_hex - read data from partition and output to stdout
2516 avb write_part - write data to partition
2517 avb verify - run full verification chain
2519 config CMD_STACKPROTECTOR_TEST
2520 bool "Test command for stack protector"
2521 depends on STACKPROTECTOR
2523 Enable stackprot_test command
2524 The stackprot_test command will force a stack overrun to test
2525 the stack smashing detection mechanisms.
2530 tristate "Enable UBI - Unsorted block images commands"
2533 UBI is a software layer above MTD layer which admits use of LVM-like
2534 logical volumes on top of MTD devices, hides some complexities of
2535 flash chips like wear and bad blocks and provides some other useful
2536 capabilities. Please, consult the MTD web site for more details
2537 (www.linux-mtd.infradead.org). Activate this option if you want
2538 to use U-Boot UBI commands.
2539 It is also strongly encouraged to also enable CONFIG_MTD to get full
2542 config CMD_UBI_RENAME
2543 bool "Enable rename"
2546 Enable a "ubi" command to rename ubi volume:
2547 ubi rename <oldname> <newname>
2550 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2552 default y if CMD_UBI
2555 UBIFS is a file system for flash devices which works on top of UBI.
2557 config MMC_SPEED_MODE_SET
2558 bool "set speed mode using mmc command"
2562 Enable setting speed mode using mmc rescan and mmc dev commands.
2563 The speed mode is provided as the last argument in these commands
2564 and is indicated using the index from enum bus_mode in
2565 include/mmc.h. A speed mode can be set only if it has already
2566 been enabled in the device tree.
projects / platform / kernel / u-boot.git / blob