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.
243 bool "Support booting UEFI FIT images"
244 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
247 Support booting UEFI FIT images via the bootm command.
252 Boot the Linux zImage
256 depends on ARM64 || RISCV
259 Boot an AArch64 Linux Kernel image from memory.
262 bool "Support booting Linux OS images"
263 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
266 Support booting the Linux kernel directly via a command such as bootm
270 bool "Support booting NetBSD (non-EFI) loader images"
274 Support booting NetBSD via the bootm command.
276 config BOOTM_OPENRTOS
277 bool "Support booting OPENRTOS / FreeRTOS images"
280 Support booting OPENRTOS / FreeRTOS via the bootm command.
283 bool "Support booting Enea OSE images"
284 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
287 Support booting Enea OSE images via the bootm command.
290 bool "Support booting Plan9 OS images"
294 Support booting Plan9 images via the bootm command.
297 bool "Support booting RTEMS OS images"
301 Support booting RTEMS images via the bootm command.
304 bool "Support booting VxWorks OS images"
308 Support booting VxWorks images via the bootm command.
312 depends on EFI_LOADER
315 Boot an EFI image from memory.
317 config CMD_BOOTEFI_HELLO_COMPILE
318 bool "Compile a standard EFI hello world binary for testing"
319 depends on CMD_BOOTEFI && !CPU_V7M
322 This compiles a standard EFI hello world application with U-Boot so
323 that it can be used with the test/py testing framework. This is useful
324 for testing that EFI is working at a basic level, and for bringing
325 up EFI support on a new architecture.
327 No additional space will be required in the resulting U-Boot binary
328 when this option is enabled.
330 config CMD_BOOTEFI_HELLO
331 bool "Allow booting a standard EFI hello world for testing"
332 depends on CMD_BOOTEFI_HELLO_COMPILE
333 default y if CMD_BOOTEFI_SELFTEST
335 This adds a standard EFI hello world application to U-Boot so that
336 it can be used with the 'bootefi hello' command. This is useful
337 for testing that EFI is working at a basic level, and for bringing
338 up EFI support on a new architecture.
340 source lib/efi_selftest/Kconfig
346 Add an ANSI terminal boot menu command.
351 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
352 image into RAM, dump image structure information, etc. Those dtb/dtbo
353 files should be merged in one dtb further, which needs to be passed to
354 the kernel, as part of a boot process.
358 depends on ANDROID_BOOT_IMAGE
360 Android Boot Image manipulation commands. Allows one to extract
361 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
362 obtain corresponding meta-information from boot.img.
364 See doc/android/boot-image.rst for details.
367 bool "bootelf, bootvx"
371 Boot an ELF/vxWorks image from the memory.
374 bool "Flattened Device Tree utility commands"
378 Do FDT related setup before booting into the Operating System.
380 config SUPPORT_EXTENSION_SCAN
384 bool "Extension board management command"
386 depends on SUPPORT_EXTENSION_SCAN
388 Enables the "extension" command, which allows to detect
389 extension boards connected to the system, and apply
390 corresponding Device Tree overlays.
396 Start an application at a given address.
402 Run the command in the given environment variable.
408 Print header information for application image.
413 List all images found in flash
419 Extract a part of a multi-image.
422 bool "spl export - Export boot information for Falcon boot"
425 Falcon mode allows booting directly from SPL into an Operating
426 System such as Linux, thus skipping U-Boot proper. See
427 doc/README.falcon for full information about how to use this
430 config CMD_SPL_NAND_OFS
431 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
432 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
435 This provides the offset of the command line arguments for Linux
436 when booting from NAND in Falcon mode. See doc/README.falcon
437 for full information about how to use this option (and also see
438 board/gateworks/gw_ventana/README for an example).
440 config CMD_SPL_NOR_OFS
441 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
442 depends on CMD_SPL && SPL_NOR_SUPPORT
445 This provides the offset of the command line arguments or dtb for
446 Linux when booting from NOR in Falcon mode.
448 config CMD_SPL_WRITE_SIZE
449 hex "Size of argument area"
453 This provides the size of the command-line argument area in NAND
454 flash used by Falcon-mode boot. See the documentation until CMD_SPL
457 config CMD_THOR_DOWNLOAD
458 bool "thor - TIZEN 'thor' download"
461 Implements the 'thor' download protocol. This is a way of
462 downloading a software update over USB from an attached host.
463 There is no documentation about this within the U-Boot source code
464 but you should be able to find something on the interwebs.
467 bool "zboot - x86 boot command"
469 With x86 machines it is common to boot a bzImage file which
470 contains both a kernel and a setup.bin file. The latter includes
471 configuration information from the dark ages which x86 boards still
472 need to pick things out of.
474 Consider using FIT in preference to this since it supports directly
475 booting both 32- and 64-bit kernels, as well as secure boot.
476 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
480 menu "Environment commands"
483 bool "ask for env variable"
485 Ask for environment variable
503 Edit environment variable.
508 Allow for searching environment variables
514 Save all environment variables into the compiled-in persistent
519 depends on CMD_SAVEENV
521 Erase environment variables from the compiled-in persistent
524 config CMD_ENV_EXISTS
528 Check if a variable is defined in the environment for use in
531 config CMD_ENV_CALLBACK
532 bool "env callbacks - print callbacks and their associated variables"
534 Some environment variable have callbacks defined by
535 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
536 For example changing "baudrate" adjust the serial baud rate. This
537 command lists the currently defined callbacks.
540 bool "env flags -print variables that have non-default flags"
542 Some environment variables have special flags that control their
543 behaviour. For example, serial# can only be written once and cannot
544 be deleted. This command shows the variables that have special
547 config CMD_NVEDIT_EFI
548 bool "env [set|print] -e - set/print UEFI variables"
549 depends on EFI_LOADER
552 UEFI variables are encoded as some form of U-Boot variables.
553 If enabled, we are allowed to set/print UEFI variables using
554 "env" command with "-e" option without knowing details.
556 config CMD_NVEDIT_INDIRECT
557 bool "env indirect - Sets environment value from another"
559 config CMD_NVEDIT_INFO
560 bool "env info - print or evaluate environment information"
562 Print environment information:
563 - env_valid : is environment valid
564 - env_ready : is environment imported into hash table
565 - env_use_default : is default environment used
567 This command can be optionally used for evaluation in scripts:
568 [-d] : evaluate whether default environment is used
569 [-p] : evaluate whether environment can be persisted
571 The result of multiple evaluations will be combined with AND.
573 config CMD_NVEDIT_LOAD
576 Load all environment variables from the compiled-in persistent
579 config CMD_NVEDIT_SELECT
582 Select the compiled-in persistent storage of environment variables.
586 menu "Memory commands"
591 Compute binary operations (xor, or, and) of byte arrays of arbitrary
592 size from memory and store the result in memory or the environment.
596 default y if BLOBLIST
598 Show information about the bloblist, a collection of binary blobs
599 held in memory that persist between SPL and U-Boot. In the case of
600 x86 devices the bloblist can be used to hold ACPI tables so that they
601 remain available in memory.
614 Add -v option to verify data against a crc32 checksum.
617 bool "eeprom - EEPROM subsystem"
619 (deprecated, needs conversion to driver model)
620 Provides commands to read and write EEPROM (Electrically Erasable
621 Programmable Read Only Memory) chips that are connected over an
624 config CMD_EEPROM_LAYOUT
625 bool "Enable layout-aware eeprom commands"
626 depends on CMD_EEPROM
628 (deprecated, needs conversion to driver model)
629 When enabled, additional eeprom sub-commands become available.
631 eeprom print - prints the contents of the eeprom in a human-readable
632 way (eeprom layout fields, and data formatted to be fit for human
635 eeprom update - allows user to update eeprom fields by specifying
636 the field name, and providing the new data in a human readable format
637 (same format as displayed by the eeprom print command).
639 Both commands can either auto detect the layout, or be told which
643 __weak int parse_layout_version(char *str)
644 - override to provide your own layout name parsing
645 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
647 - override to setup the layout metadata based on the version
648 __weak int eeprom_layout_detect(unsigned char *data)
649 - override to provide your own algorithm for detecting layout
652 - contains various printing and updating functions for common
653 types of eeprom fields. Can be used for defining
656 config EEPROM_LAYOUT_HELP_STRING
657 string "Tells user what layout names are supported"
658 depends on CMD_EEPROM_LAYOUT
659 default "<not defined>"
661 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
664 config SYS_I2C_EEPROM_BUS
665 int "I2C bus of the EEPROM device."
666 depends on CMD_EEPROM
669 config SYS_I2C_EEPROM_ADDR_LEN
670 int "Length in bytes of the EEPROM memory array address"
671 depends on CMD_EEPROM || ID_EEPROM
675 Note: This is NOT the chip address length!
677 config SYS_EEPROM_SIZE
678 depends on CMD_EEPROM
679 int "Size in bytes of the EEPROM device"
682 config SYS_EEPROM_PAGE_WRITE_BITS
683 int "Number of bits used to address bytes in a single page"
684 depends on CMD_EEPROM
687 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
688 A 64 byte page, for example would require six bits.
690 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
691 int "Number of milliseconds to delay between page writes"
692 depends on CMD_EEPROM || CMD_I2C
698 Infinite write loop on address range
704 Compute MD5 checksum.
708 depends on CMD_MD5SUM
710 Add -v option to verify data against an MD5 checksum.
715 Display memory information.
718 bool "md, mm, nm, mw, cp, cmp, base, loop"
723 mm - memory modify (auto-incrementing address)
724 nm - memory modify (constant address)
725 mw - memory write (fill)
728 base - print or set address offset
729 loop - initialize loop on address range
731 config CMD_MEM_SEARCH
732 bool "ms - Memory search"
734 Memory-search command
736 This allows searching through a region of memory looking for hex
737 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
738 support it). It is also possible to search for a string. The
739 command accepts a memory range and a list of values to search for.
740 The values need to appear in memory in the same order they are given
741 in the command. At most 10 matches can be returned at a time, but
742 pressing return will show the next 10 matches. Environment variables
743 are set for use with scripting (memmatches, memaddr, mempos).
746 bool "Enable cyclic md/mw commands"
747 depends on CMD_MEMORY
749 Add the "mdc" and "mwc" memory commands. These are cyclic
754 This command will print 4 bytes (10,11,12,13) each 500 ms.
756 => mwc.l 100 12345678 10
757 This command will write 12345678 to address 100 all 10 ms.
762 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
764 random - fill memory with random data
769 Simple RAM read/write test.
773 config SYS_ALT_MEMTEST
774 bool "Alternative test"
776 Use a more complete alternative memory test.
780 config SYS_ALT_MEMTEST_BITFLIP
784 The alternative memory test includes bitflip test since 2020.07.
785 The bitflip test significantly increases the overall test time.
786 Bitflip test can optionally be disabled here.
790 config SYS_MEMTEST_START
791 hex "default start address for mtest"
794 This is the default start address for mtest for simple read/write
795 test. If no arguments are given to mtest, default address is used
798 config SYS_MEMTEST_END
799 hex "default end address for mtest"
802 This is the default end address for mtest for simple read/write
803 test. If no arguments are given to mtest, default address is used
812 Compute SHA1 checksum.
814 config SHA1SUM_VERIFY
816 depends on CMD_SHA1SUM
818 Add -v option to verify data against a SHA1 checksum.
821 bool "strings - display strings in memory"
823 This works similarly to the Unix 'strings' command except that it
824 works with a memory range. String of printable characters found
825 within the range are displayed. The minimum number of characters
826 for a sequence to be considered a string can be provided.
830 menu "Compression commands"
834 default y if CMD_BOOTI
837 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
842 default y if CMD_BOOTI
845 Support decompressing an LZ4 image from memory region.
849 default y if CMD_BOOTI
852 Uncompress a zip-compressed memory region.
856 select GZIP_COMPRESSED
858 Compress a memory region with zlib deflate method.
862 menu "Device access commands"
865 #depends on FLASH_CFI_DRIVER
868 ARM Ltd reference designs flash partition access
871 bool "adc - Access Analog to Digital Converters info and data"
873 depends on DM_REGULATOR
875 Shows ADC device info and permit printing one-shot analog converted
876 data from a named Analog to Digital Converter.
881 depends on PARTITIONS
883 Read/modify/write the fields of Bootloader Control Block, usually
884 stored on the flash "misc" partition with its structure defined in:
885 https://android.googlesource.com/platform/bootable/recovery/+/master/
886 bootloader_message/include/bootloader_message/bootloader_message.h
888 Some real-life use-cases include (but are not limited to):
889 - Determine the "boot reason" (and act accordingly):
890 https://source.android.com/devices/bootloader/boot-reason
891 - Get/pass a list of commands from/to recovery:
892 https://android.googlesource.com/platform/bootable/recovery
893 - Inspect/dump the contents of the BCB fields
896 bool "bind/unbind - Bind or unbind a device to/from a driver"
899 Bind or unbind a device to/from a driver from the command line.
900 This is useful in situations where a device may be handled by several
901 drivers. For example, this can be used to bind a UDC to the usb ether
902 gadget driver from the command line.
905 bool "clk - Show clock frequencies"
908 Shows clock frequences by calling a sock_clk_dump() hook function.
909 This is depreated in favour of using the CLK uclass and accessing
910 clock values from associated drivers. However currently no command
914 bool "demo - Demonstration commands for driver model"
917 Provides a 'demo' command which can be used to play around with
918 driver model. To use this properly you will need to enable one or
919 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
920 Otherwise you will always get an empty list of devices. The demo
921 devices are defined in the sandbox device tree, so the easiest
922 option is to use sandbox and pass the -d point to sandbox's
929 Enables the command "dfu" which is used to have U-Boot create a DFU
930 class device via USB. This command requires that the "dfu_alt_info"
931 environment variable be set and define the alt settings to expose to
935 bool "dm - Access to driver model information"
938 Provides access to driver model data structures and information,
939 such as a list of devices, list of uclasses and the state of each
940 device (e.g. activated). This is not required for operation, but
941 can be useful to see the state of driver model for debugging or
945 bool "fastboot - Android fastboot support"
948 This enables the command "fastboot" which enables the Android
949 fastboot mode for the platform. Fastboot is a protocol for
950 downloading images, flashing and device control used on
951 Android devices. Fastboot requires either the network stack
952 enabled or support for acting as a USB device.
954 See doc/android/fastboot.rst for more information.
957 bool "flinfo, erase, protect"
959 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
962 flinfo - print FLASH memory information
964 protect - enable or disable FLASH write protection
973 config CMD_FPGA_LOADBP
974 bool "fpga loadbp - load partial bitstream (Xilinx only)"
977 Supports loading an FPGA device from a bitstream buffer containing
980 config CMD_FPGA_LOADFS
981 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
984 Supports loading an FPGA device from a FAT filesystem.
986 config CMD_FPGA_LOADMK
987 bool "fpga loadmk - load bitstream from image"
990 Supports loading an FPGA device from a image generated by mkimage.
992 config CMD_FPGA_LOADP
993 bool "fpga loadp - load partial bitstream"
996 Supports loading an FPGA device from a bitstream buffer containing
999 config CMD_FPGA_LOAD_SECURE
1000 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1003 Enables the fpga loads command which is used to load secure
1004 (authenticated or encrypted or both) bitstreams on to FPGA.
1007 bool "fpgad - dump FPGA registers"
1009 (legacy, needs conversion to driver model)
1010 Provides a way to dump FPGA registers by calling the board-specific
1011 fpga_get_reg() function. This functions similarly to the 'md'
1015 bool "fuse - support for the fuse subssystem"
1017 (deprecated - needs conversion to driver model)
1018 This allows reading, sensing, programming or overriding fuses
1019 which control the behaviour of the device. The command uses the
1027 config CMD_GPIO_READ
1028 bool "gpio read - save GPIO value to variable"
1031 Enables the 'gpio read' command that saves the value
1032 of a GPIO pin to a variable.
1038 Control PWM channels, this allows invert/config/enable/disable PWM channels.
1041 bool "GPT (GUID Partition Table) command"
1042 select EFI_PARTITION
1043 select HAVE_BLOCK_DEVICE
1044 select PARTITION_UUIDS
1047 Enable the 'gpt' command to ready and write GPT style partition
1051 bool "GPT Random UUID generation"
1054 Enable the generation of partitions with random UUIDs if none
1057 config CMD_GPT_RENAME
1058 bool "GPT partition renaming commands"
1061 Enables the 'gpt' command to interchange names on two GPT
1062 partitions via the 'gpt swap' command or to rename single
1063 partitions via the 'rename' command.
1066 bool "ide - Support for IDE drivers"
1069 Provides an 'ide' command which allows accessing the IDE drive,
1070 resetting the IDE interface, printing the partition table and
1071 geting device info. It also enables the 'diskboot' command which
1072 permits booting from an IDE drive.
1075 bool "io - Support for performing I/O accesses"
1077 Provides an 'iod' command to display I/O space and an 'iow' command
1078 to write values to the I/O space. This can be useful for manually
1079 checking the state of devices during boot when debugging device
1083 bool "iotrace - Support for tracing I/O activity"
1085 Provides an 'iotrace' command which supports recording I/O reads and
1086 writes in a trace buffer in memory . It also maintains a checksum
1087 of the trace records (even if space is exhausted) so that the
1088 sequence of I/O accesses can be verified.
1090 When debugging drivers it is useful to see what I/O accesses were
1091 done and in what order.
1093 Even if the individual accesses are of little interest it can be
1094 useful to verify that the access pattern is consistent each time
1095 an operation is performed. In this case a checksum can be used to
1096 characterise the operation of a driver. The checksum can be compared
1097 across different runs of the operation to verify that the driver is
1100 In particular, when performing major refactoring of the driver, where
1101 the access pattern should not change, the checksum provides assurance
1102 that the refactoring work has not broken the driver.
1104 This works by sneaking into the io.h heder for an architecture and
1105 redirecting I/O accesses through iotrace's tracing mechanism.
1107 For now no commands are provided to examine the trace buffer. The
1108 format is fairly simple, so 'md' is a reasonable substitute.
1110 Note: The checksum feature is only useful for I/O regions where the
1111 contents do not change outside of software control. Where this is not
1112 suitable you can fall back to manually comparing the addresses. It
1113 might be useful to enhance tracing to only checksum the accesses and
1114 not the data read/written.
1124 bool "w1 - Support for Dallas 1-Wire protocol"
1126 Dallas 1-wire protocol support
1132 Load a binary file over serial line.
1138 Load an S-Record file over serial line
1142 bool "lsblk - list block drivers and devices"
1144 Print list of available block device drivers, and for each, the list
1145 of known block devices.
1148 bool "MBR (Master Boot Record) command"
1149 select DOS_PARTITION
1150 select HAVE_BLOCK_DEVICE
1152 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1153 style partition tables.
1159 Enable the command "misc" for accessing miscellaneous devices with
1160 a MISC uclass driver. The command provides listing all MISC devices
1161 as well as read and write functionalities via their drivers.
1167 MMC memory mapped support.
1171 config CMD_BKOPS_ENABLE
1172 bool "mmc bkops enable"
1175 Enable command for setting manual background operations handshake
1176 on a eMMC device. The feature is optionally available on eMMC devices
1177 conforming to standard >= 4.41.
1180 bool "Enable support for RPMB in the mmc command"
1181 depends on SUPPORT_EMMC_RPMB
1183 Enable the commands for reading, writing and programming the
1184 key for the Replay Protection Memory Block partition in eMMC.
1186 config CMD_MMC_SWRITE
1188 depends on MMC_WRITE
1191 Enable support for the "mmc swrite" command to write Android sparse
1200 Enable storage cloning over block devices, useful for
1201 initial flashing by external block device without network
1204 config CMD_OPTEE_RPMB
1205 bool "Enable read/write support on RPMB via OPTEE"
1206 depends on SUPPORT_EMMC_RPMB && OPTEE
1208 Enable the commands for reading, writing persistent named values
1209 in the Replay Protection Memory Block partition in eMMC by
1210 using Persistent Objects in OPTEE
1215 select MTD_PARTITIONS
1217 MTD commands support.
1221 depends on MULTIPLEXER
1223 List, select, and deselect mux controllers on the fly.
1227 default y if NAND_SUNXI
1228 depends on MTD_RAW_NAND
1233 config CMD_NAND_TRIMFFS
1234 bool "nand write.trimffs"
1235 default y if ARCH_SUNXI
1237 Allows one to skip empty pages when flashing something on a NAND.
1239 config CMD_NAND_LOCK_UNLOCK
1240 bool "nand lock/unlock"
1242 NAND locking support.
1244 config CMD_NAND_TORTURE
1247 NAND torture support.
1256 NVM Express device support
1259 bool "onenand - access to onenand device"
1262 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1263 various useful features. This command allows reading, writing,
1264 and erasing blocks. It allso provides a way to show and change
1265 bad blocks, and test the device.
1270 Enable the 'osd' command which allows to query information from and
1271 write text data to a on-screen display (OSD) device; a virtual device
1272 associated with a display capable of displaying a text overlay on the
1273 display it's associated with..
1277 select HAVE_BLOCK_DEVICE
1278 select PARTITION_UUIDS
1280 Read and display information about the partition table on
1284 bool "pci - Access PCI devices"
1286 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1287 used on some devices to allow the CPU to communicate with its
1288 peripherals. Sub-commands allow bus enumeration, displaying and
1289 changing configuration space and a few other features.
1292 bool "pinmux - show pins muxing"
1294 default y if PINCTRL
1296 Parse all available pin-controllers and show pins muxing. This
1297 is useful for debug purpoer to check the pin muxing and to know if
1298 a pin is configured as a GPIO or as an alternate function.
1303 Poweroff/Shutdown the system
1306 bool "read - Read binary data from a partition"
1308 Provides low-level access to the data in a partition.
1310 config CMD_REMOTEPROC
1312 depends on REMOTEPROC
1314 Support for Remote Processor control
1317 bool "sata - Access SATA subsystem"
1320 SATA (Serial Advanced Technology Attachment) is a serial bus
1321 standard for connecting to hard drives and other storage devices.
1322 This command provides information about attached devices and allows
1323 reading, writing and other operations.
1325 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1326 Attachment, where AT refers to an IBM AT (Advanced Technology)
1327 computer released in 1984.
1330 bool "saves - Save a file over serial in S-Record format"
1332 Provides a way to save a binary file using the Motorola S-Record
1333 format over the serial line.
1336 bool "scsi - Access to SCSI devices"
1339 This provides a 'scsi' command which provides access to SCSI (Small
1340 Computer System Interface) devices. The command provides a way to
1341 scan the bus, reset the bus, read and write data and get information
1345 bool "sdram - Print SDRAM configuration information"
1347 Provides information about attached SDRAM. This assumed that the
1348 SDRAM has an EEPROM with information that can be read using the
1349 I2C bus. This is only available on some boards.
1353 depends on DM_SPI_FLASH || SPI_FLASH
1354 default y if DM_SPI_FLASH
1359 bool "sf test - Allow testing of SPI flash"
1362 Provides a way to test that SPI flash is working correctly. The
1363 test is destructive, in that an area of SPI flash must be provided
1364 for the test to use. Performance information is also provided,
1365 measuring the performance of reading, writing and erasing in
1366 Mbps (Million Bits Per Second). This value should approximately
1367 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1368 everything is working properly.
1371 bool "sspi - Command to access spi device"
1374 SPI utility command.
1376 config DEFAULT_SPI_BUS
1377 int "default spi bus used by sspi command"
1381 config DEFAULT_SPI_MODE
1382 hex "default spi mode used by sspi command (see include/spi.h)"
1387 bool "tsi148 - Command to access tsi148 device"
1389 This provides various sub-commands to initialise and configure the
1390 Turndra tsi148 device. See the command help for full details.
1393 bool "Enable UFS - Universal Flash Subsystem commands"
1396 "This provides commands to initialise and configure universal flash
1400 bool "universe - Command to set up the Turndra Universe controller"
1402 This allows setting up the VMEbus provided by this controller.
1403 See the command help for full details.
1408 select HAVE_BLOCK_DEVICE
1414 select USB_FUNCTION_SDP
1416 Enables the command "sdp" which is used to have U-Boot emulating the
1417 Serial Download Protocol (SDP) via USB.
1421 depends on USB_FUNCTION_ROCKUSB
1423 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1424 read/write info, image to/from devices. This enable rockusb command
1425 support to communication with rockusb device. for more detail about
1426 this command, please read doc/README.rockusb.
1428 config CMD_USB_MASS_STORAGE
1429 bool "UMS usb mass storage"
1430 depends on USB_GADGET_DOWNLOAD
1431 select USB_FUNCTION_MASS_STORAGE
1432 depends on BLK && USB_GADGET
1434 Enables the command "ums" and the USB mass storage support to the
1435 export a block device: U-Boot, the USB device, acts as a simple
1436 external hard drive plugged on the host USB port.
1439 bool "Xen para-virtualized block device"
1443 Xen para-virtualized block device support
1448 depends on HAVE_BLOCK_DEVICE
1451 VirtIO block device support
1457 This provides commands to control the watchdog timer devices.
1463 Enable the command "axi" for accessing AXI (Advanced eXtensible
1464 Interface) busses, a on-chip interconnect specification for managing
1465 functional blocks in SoC designs, which is also often used in designs
1466 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1470 menu "Shell scripting commands"
1476 Echo args to console
1482 Return true/false on integer compare.
1488 Run script from memory
1494 Evaluate boolean and math expressions and store the result in an env
1496 Also supports loading the value at a memory location into a variable.
1497 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1499 config CMD_SETEXPR_FMT
1501 depends on CMD_SETEXPR
1503 Evaluate format string expression and store result in an environment
1508 menu "Android support commands"
1510 config CMD_AB_SELECT
1512 depends on ANDROID_AB
1514 On Android devices with more than one boot slot (multiple copies of
1515 the kernel and system images) this provides a command to select which
1516 slot should be used to boot from and register the boot attempt. This
1517 is used by the new A/B update model where one slot is updated in the
1518 background while running from the other slot.
1525 bool "Network commands"
1535 bootp - boot image via network using BOOTP/TFTP protocol
1539 depends on CMD_BOOTP
1541 Boot image via network using DHCP/TFTP protocol
1543 config BOOTP_MAY_FAIL
1544 bool "Allow for the BOOTP/DHCP server to not be found"
1545 depends on CMD_BOOTP
1547 If the DHCP server is not found after the configured retry count, the
1548 call will fail instead of starting over. This can be used to fail
1549 over to Link-local IP address configuration if the DHCP server is not
1552 config BOOTP_BOOTPATH
1553 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1555 depends on CMD_BOOTP
1557 Even though the config is called BOOTP_BOOTPATH, it stores the
1558 path in the variable 'rootpath'.
1560 config BOOTP_VENDOREX
1561 bool "Support vendor extensions from BOOTP/DHCP server"
1562 depends on CMD_BOOTP
1564 config BOOTP_BOOTFILESIZE
1565 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1566 depends on CMD_BOOTP
1569 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1571 depends on CMD_BOOTP
1573 The primary DNS server is stored as 'dnsip'. If two servers are
1574 returned, you must set BOOTP_DNS2 to store that second server IP
1578 bool "Store 'dnsip2' from BOOTP/DHCP server"
1579 depends on BOOTP_DNS
1581 If a DHCP client requests the DNS server IP from a DHCP server,
1582 it is possible that more than one DNS serverip is offered to the
1583 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1584 server IP will be stored in the additional environment
1585 variable "dnsip2". The first DNS serverip is always
1586 stored in the variable "dnsip", when BOOTP_DNS is defined.
1588 config BOOTP_GATEWAY
1589 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1591 depends on CMD_BOOTP
1593 config BOOTP_HOSTNAME
1594 bool "Request & store 'hostname' from BOOTP/DHCP server"
1596 depends on CMD_BOOTP
1598 The name may or may not be qualified with the local domain name.
1600 config BOOTP_PREFER_SERVERIP
1601 bool "serverip variable takes precedent over DHCP server IP."
1602 depends on CMD_BOOTP
1604 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1606 With this option enabled, the 'serverip' variable in the environment
1607 takes precedence over DHCP server IP and will only be set by the DHCP
1608 server if not already set in the environment.
1610 config BOOTP_SUBNETMASK
1611 bool "Request & store 'netmask' from BOOTP/DHCP server"
1613 depends on CMD_BOOTP
1615 config BOOTP_NISDOMAIN
1616 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1617 depends on CMD_BOOTP
1619 config BOOTP_NTPSERVER
1620 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1621 depends on CMD_BOOTP
1623 config BOOTP_TIMEOFFSET
1624 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1625 depends on CMD_BOOTP && CMD_SNTP
1630 Selecting this will allow capturing all Ethernet packets and store
1631 them in physical memory in a PCAP formated file,
1632 later to be analyzed by PCAP reader application (IE. WireShark).
1635 bool "Send PXE client arch to BOOTP/DHCP server"
1637 depends on CMD_BOOTP && CMD_PXE
1639 Supported for ARM, ARM64, and x86 for now.
1641 config BOOTP_PXE_CLIENTARCH
1643 depends on BOOTP_PXE
1644 default 0x16 if ARM64
1648 config BOOTP_VCI_STRING
1650 depends on CMD_BOOTP
1651 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1652 default "U-Boot.armv8" if ARM64
1653 default "U-Boot.arm" if ARM
1660 tftpboot - boot image via network using TFTP protocol
1664 depends on CMD_TFTPBOOT
1666 TFTP put command, for uploading files to a server
1670 depends on CMD_TFTPBOOT
1672 Act as a TFTP server and boot the first received file
1674 config NET_TFTP_VARS
1675 bool "Control TFTP timeout and count through environment"
1676 depends on CMD_TFTPBOOT
1679 If set, allows controlling the TFTP timeout through the
1680 environment variable tftptimeout, and the TFTP maximum
1681 timeout count through the variable tftptimeoutcountmax.
1682 If unset, timeout and maximum are hard-defined as 1 second
1683 and 10 timouts per TFTP transfer.
1688 Boot image via network using RARP/TFTP protocol
1694 Boot image via network using NFS protocol.
1697 int "Timeout in milliseconds for NFS mounts"
1701 Timeout in milliseconds used in NFS protocol. If you encounter
1702 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1709 If set, allows 802.3(clause 22) MII Management functions interface access
1710 The management interface specified in Clause 22 provides
1711 a simple, two signal, serial interface to connect a
1712 Station Management entity and a managed PHY for providing access
1713 to management parameters and services.
1714 The interface is referred to as the MII management interface.
1717 bool "Call mii_init() in the mii command"
1718 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1724 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1725 The MDIO interface is orthogonal to the MII interface and extends
1726 it by adding access to more registers through indirect addressing.
1731 Send ICMP ECHO_REQUEST to network host
1736 Perform CDP network configuration
1742 Synchronize RTC via network
1747 Lookup the IP of a hostname
1749 config CMD_LINK_LOCAL
1753 Acquire a network IP address using the link-local protocol
1760 Allow control of L2 Ethernet switch commands. These are supported
1761 by the vsc9953 Ethernet driver at present. Sub-commands allow
1762 operations such as enabling / disabling a port and
1763 viewing/maintaining the filtering database (FDB)
1769 Boot image via network using PXE protocol
1774 Wait for wake-on-lan Magic Packet
1778 menu "Misc commands"
1781 bool "Enable 'bmp' command"
1782 depends on LCD || DM_VIDEO || VIDEO
1784 This provides a way to obtain information about a BMP-format image
1785 and to display it. BMP (which presumably stands for BitMaP) is a
1786 file format defined by Microsoft which supports images of various
1787 depths, formats and compression methods. Headers on the file
1788 determine the formats used. This command can be used by first loading
1789 the image into RAM, then using this command to look at it or display
1792 config CMD_BOOTCOUNT
1794 depends on BOOTCOUNT_LIMIT
1796 Enable the bootcount command, which allows interrogation and
1797 reset of the bootcounter.
1800 bool "Enable board-specific commands"
1802 (deprecated: instead, please define a Kconfig option for each command)
1804 Some boards have board-specific commands which are only enabled
1805 during developemnt and need to be turned off for production. This
1806 option provides a way to control this. The commands that are enabled
1807 vary depending on the board.
1809 config CMD_BLOCK_CACHE
1810 bool "blkcache - control and stats for block cache"
1811 depends on BLOCK_CACHE
1812 default y if BLOCK_CACHE
1814 Enable the blkcache command, which can be used to control the
1815 operation of the cache functions.
1816 This is most useful when fine-tuning the operation of the cache
1817 during development, but also allows the cache to be disabled when
1818 it might hurt performance (e.g. when using the ums command).
1825 Enable the 'button' command which allows to get the status of
1826 buttons supported by the board. The buttonss can be listed with
1827 'button list' and state can be known with 'button <label>'.
1828 Any button drivers can be controlled with this command, e.g.
1832 bool "icache or dcache"
1834 Enable the "icache" and "dcache" commands
1836 config CMD_CONITRACE
1837 bool "conitrace - trace console input codes"
1839 Enable the 'conitrace' command which displays the codes received
1840 from the console input as hexadecimal numbers.
1843 bool "Enable clear screen command 'cls'"
1844 depends on DM_VIDEO || LCD || VIDEO
1847 Enable the 'cls' command which clears the screen contents
1848 on video frame buffer.
1851 bool "efidebug - display/configure UEFI environment"
1852 depends on EFI_LOADER
1853 select EFI_DEVICE_PATH_TO_TEXT
1855 Enable the 'efidebug' command which provides a subset of UEFI
1856 shell utility with simplified functionality. It will be useful
1857 particularly for managing boot parameters as well as examining
1858 various EFI status for debugging.
1860 config CMD_EXCEPTION
1861 bool "exception - raise exception"
1862 depends on ARM || RISCV || SANDBOX || X86
1864 Enable the 'exception' command which allows to raise an exception.
1871 Enable the 'led' command which allows for control of LEDs supported
1872 by the board. The LEDs can be listed with 'led list' and controlled
1873 with led on/off/togle/blink. Any LED drivers can be controlled with
1874 this command, e.g. led_gpio.
1881 Enable the 'date' command for getting/setting the time/date in RTC
1888 Enable the 'rtc' command for low-level access to RTC devices.
1893 Run commands and summarize execution time.
1896 bool "gettime - read elapsed time"
1898 Enable the 'gettime' command which reads the elapsed time since
1899 U-Boot started running. This shows the time in seconds and
1900 milliseconds. See also the 'bootstage' command which provides more
1901 flexibility for boot timing.
1908 Print bytes from the hardware random number generator.
1910 config CMD_KASLRSEED
1914 Set the kaslr-seed in the chosen node with entropy provided by a
1915 hardware random number generator.
1921 Delay execution for some time
1924 bool "support for multiprocessor commands"
1928 This enables commands to bringup different processors
1929 in multiprocessor cases.
1934 Access the system timer.
1940 This provides basic access to the U-Boot's sound support. The main
1941 feature is to play a beep.
1943 sound init - set up sound system
1944 sound play - play a sound
1950 Boot image via local extlinux.conf file
1956 This provides access to the QEMU firmware interface. The main
1957 feature is to allow easy loading of files passed to qemu-system
1958 via -kernel / -initrd
1963 This provides access to Linux PStore with Rammoops backend. The main
1964 feature is to allow to display or save PStore records.
1966 See doc/pstore.rst for more information.
1970 config CMD_PSTORE_MEM_ADDR
1971 hex "Memory Address"
1972 depends on CMD_PSTORE
1974 Base addr used for PStore ramoops memory, should be identical to
1975 ramoops.mem_address parameter used by kernel
1977 config CMD_PSTORE_MEM_SIZE
1979 depends on CMD_PSTORE
1982 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1983 parameter used by kernel, a power of 2 and larger than the sum of the
1986 config CMD_PSTORE_RECORD_SIZE
1987 hex "Dump record size"
1988 depends on CMD_PSTORE
1991 Size of each dump done on oops/panic, should be identical to
1992 ramoops.record_size parameter used by kernel and a power of 2
1995 config CMD_PSTORE_CONSOLE_SIZE
1996 hex "Kernel console log size"
1997 depends on CMD_PSTORE
2000 Size of kernel console log, should be identical to
2001 ramoops.console_size parameter used by kernel and a power of 2
2004 config CMD_PSTORE_FTRACE_SIZE
2005 hex "FTrace log size"
2006 depends on CMD_PSTORE
2009 Size of ftrace log, should be identical to ramoops.ftrace_size
2010 parameter used by kernel and a power of 2
2012 config CMD_PSTORE_PMSG_SIZE
2013 hex "User space message log size"
2014 depends on CMD_PSTORE
2017 Size of user space message log, should be identical to
2018 ramoops.pmsg_size parameter used by kernel and a power of 2
2020 config CMD_PSTORE_ECC_SIZE
2022 depends on CMD_PSTORE
2025 if non-zero, the option enables ECC support and specifies ECC buffer
2026 size in bytes (1 is a special value, means 16 bytes ECC), should be
2027 identical to ramoops.ramoops_ecc parameter used by kernel
2031 source "cmd/mvebu/Kconfig"
2034 bool "terminal - provides a way to attach a serial terminal"
2036 Provides a 'cu'-like serial terminal command. This can be used to
2037 access other serial ports from the system console. The terminal
2038 is very simple with no special processing of characters. As with
2039 cu, you can press ~. (tilde followed by period) to exit.
2042 bool "uuid, guid - generation of unique IDs"
2045 This enables two commands:
2047 uuid - generate random Universally Unique Identifier
2048 guid - generate Globally Unique Identifier based on random UUID
2050 The two commands are very similar except for the endianness of the
2055 source "cmd/ti/Kconfig"
2057 config CMD_BOOTSTAGE
2058 bool "Enable the 'bootstage' command"
2059 depends on BOOTSTAGE
2061 Add a 'bootstage' command which supports printing a report
2062 and un/stashing of bootstage data.
2064 menu "Power commands"
2066 bool "Enable Driver Model PMIC command"
2069 This is the pmic command, based on a driver model pmic's API.
2070 Command features are unchanged:
2071 - list - list pmic devices
2072 - pmic dev <id> - show or [set] operating pmic device (NEW)
2073 - pmic dump - dump registers
2074 - pmic read address - read byte of register at address
2075 - pmic write address - write byte to register at address
2076 The only one change for this command is 'dev' subcommand.
2078 config CMD_REGULATOR
2079 bool "Enable Driver Model REGULATOR command"
2080 depends on DM_REGULATOR
2082 This command is based on driver model regulator's API.
2083 User interface features:
2084 - list - list regulator devices
2085 - regulator dev <id> - show or [set] operating regulator device
2086 - regulator info - print constraints info
2087 - regulator status - print operating status
2088 - regulator value <val] <-f> - print/[set] voltage value [uV]
2089 - regulator current <val> - print/[set] current value [uA]
2090 - regulator mode <id> - print/[set] operating mode id
2091 - regulator enable - enable the regulator output
2092 - regulator disable - disable the regulator output
2094 The '-f' (force) option can be used for set the value which exceeds
2095 the limits, which are found in device-tree and are kept in regulator's
2096 uclass plat structure.
2100 menu "Security commands"
2102 bool "Enable the 'aes' command"
2105 This provides a means to encrypt and decrypt data using the AES
2106 (Advanced Encryption Standard). This algorithm uses a symetric key
2107 and is widely used as a streaming cipher. Different key lengths are
2108 supported by the algorithm but this command only supports 128 bits
2112 bool "Enable the 'blob' command"
2113 depends on !MX6ULL && !MX6SLL && !MX6SL
2114 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2116 This is used with the Freescale secure boot mechanism.
2118 Freescale's SEC block has built-in Blob Protocol which provides
2119 a method for protecting user-defined data across system power
2120 cycles. SEC block protects data in a data structure called a Blob,
2121 which provides both confidentiality and integrity protection.
2123 Encapsulating data as a blob
2124 Each time that the Blob Protocol is used to protect data, a
2125 different randomly generated key is used to encrypt the data.
2126 This random key is itself encrypted using a key which is derived
2127 from SoC's non-volatile secret key and a 16 bit Key identifier.
2128 The resulting encrypted key along with encrypted data is called a
2129 blob. The non-volatile secure key is available for use only during
2132 During decapsulation, the reverse process is performed to get back
2136 blob enc - encapsulating data as a cryptgraphic blob
2137 blob dec - decapsulating cryptgraphic blob to get the data
2141 blob enc src dst len km
2143 Encapsulate and create blob of data $len bytes long
2144 at address $src and store the result at address $dst.
2145 $km is the 16 byte key modifier is also required for
2146 generation/use as key for cryptographic operation. Key
2147 modifier should be 16 byte long.
2149 blob dec src dst len km
2151 Decapsulate the blob of data at address $src and
2152 store result of $len byte at addr $dst.
2153 $km is the 16 byte key modifier is also required for
2154 generation/use as key for cryptographic operation. Key
2155 modifier should be 16 byte long.
2158 bool "Support 'hash' command"
2161 This provides a way to hash data in memory using various supported
2162 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2163 saved to memory or to an environment variable. It is also possible
2164 to verify a hash against data in memory.
2167 bool "Support the 'hvc' command"
2168 depends on ARM_SMCCC
2170 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2171 development and testing.
2174 bool "Support the 'smc' command"
2175 depends on ARM_SMCCC
2177 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2178 development and testing.
2184 Add -v option to verify data against a hash.
2187 bool "scp03 - SCP03 enable and rotate/provision operations"
2190 This command provides access to a Trusted Application
2191 running in a TEE to request Secure Channel Protocol 03
2192 (SCP03) enablement and/or rotation of its SCP03 keys.
2201 bool "Enable the 'tpm' command"
2202 depends on TPM_V1 || TPM_V2
2203 select CMD_TPM_V1 if TPM_V1
2204 select CMD_TPM_V2 if TPM_V2
2206 This provides a means to talk to a TPM from the command line. A wide
2207 range of commands if provided - see 'tpm help' for details. The
2208 command requires a suitable TPM on your board and the correct driver
2214 bool "Enable the 'tpm test' command"
2217 This provides a a series of tests to confirm that the TPMv1.x is
2218 working correctly. The tests cover initialisation, non-volatile RAM,
2219 extend, global lock and checking that timing is within expectations.
2220 The tests pass correctly on Infineon TPMs but may need to be adjusted
2227 menu "Firmware commands"
2229 bool "Enable crosec command"
2233 Enable command-line access to the Chrome OS EC (Embedded
2234 Controller). This provides the 'crosec' command which has
2235 a number of sub-commands for performing EC tasks such as
2236 updating its flash, accessing a small saved context area
2237 and talking to the I2C bus behind the EC (if there is one).
2240 menu "Filesystem commands"
2242 bool "Enable the 'btrsubvol' command"
2245 This enables the 'btrsubvol' command to list subvolumes
2246 of a BTRFS filesystem. There are no special commands for
2247 listing BTRFS directories or loading BTRFS files - this
2248 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2249 when BTRFS is enabled (see FS_BTRFS).
2252 bool "Enable the 'cbfs' command"
2255 Define this to enable support for reading from a Coreboot
2256 filesystem. This is a ROM-based filesystem used for accessing files
2257 on systems that use coreboot as the first boot-loader and then load
2258 U-Boot to actually boot the Operating System. Available commands are
2259 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2262 bool "Enable the 'cramfs' command"
2263 depends on FS_CRAMFS
2265 This provides commands for dealing with CRAMFS (Compressed ROM
2266 filesystem). CRAMFS is useful when space is tight since files are
2267 compressed. Two commands are provided:
2269 cramfsls - lists files in a cramfs image
2270 cramfsload - loads a file from a cramfs image
2273 bool "EROFS command support"
2276 Support for the EROFS fs
2279 bool "ext2 command support"
2282 Enables EXT2 FS command
2285 bool "ext4 command support"
2288 Enables EXT4 FS command
2290 config CMD_EXT4_WRITE
2292 bool "ext4 write command support"
2295 Enables EXT4 FS write command
2298 bool "FAT command support"
2301 Support for the FAT fs
2304 bool "SquashFS command support"
2307 Enables SquashFS filesystem commands (e.g. load, ls).
2309 config CMD_FS_GENERIC
2310 bool "filesystem commands"
2312 Enables filesystem commands (e.g. load, ls) that work for multiple
2316 bool "fsuuid command"
2318 Enables fsuuid command for filesystem UUID.
2321 bool "jffs2 command"
2324 Enables commands to support the JFFS2 (Journalling Flash File System
2325 version 2) filesystem. This enables fsload, ls and fsinfo which
2326 provide the ability to load files, list directories and obtain
2327 filesystem information.
2330 string "Default device for JFFS2"
2331 depends on CMD_JFFS2
2334 The default device to use with the jffs2 command.
2336 config JFFS2_PART_OFFSET
2337 hex "Default offset within flash to locate the JFFS2 image"
2338 depends on CMD_JFFS2
2341 The default offset within flash to locate the JFFS2 image.
2343 config JFFS2_PART_SIZE
2344 hex "Default size of JFFS2 partition"
2345 depends on CMD_JFFS2
2348 The default size of the JFFS2 partition
2351 bool "MTD partition support"
2354 MTD partitioning tool support.
2355 It is strongly encouraged to avoid using this command
2356 anymore along with 'sf', 'nand', 'onenand'. One can still
2357 declare the partitions in the mtdparts environment variable
2358 but better use the MTD stack and the 'mtd' command instead.
2360 config CMD_MTDPARTS_SPREAD
2361 bool "Padd partition size to take account of bad blocks"
2362 depends on CMD_MTDPARTS
2364 This enables the 'spread' sub-command of the mtdparts command.
2365 This command will modify the existing mtdparts variable by increasing
2366 the size of the partitions such that 1) each partition's net size is
2367 at least as large as the size specified in the mtdparts variable and
2368 2) each partition starts on a good block.
2370 config CMD_MTDPARTS_SHOW_NET_SIZES
2371 bool "Show net size (w/o bad blocks) of partitions"
2372 depends on CMD_MTDPARTS
2374 Adds two columns to the printed partition table showing the
2375 effective usable size of a partition, if bad blocks are taken
2378 config MTDIDS_DEFAULT
2379 string "Default MTD IDs"
2380 depends on MTD || SPI_FLASH
2382 Defines a default MTD IDs list for use with MTD partitions in the
2383 Linux MTD command line partitions format.
2385 config MTDPARTS_DEFAULT
2386 string "Default MTD partition scheme"
2387 depends on MTD || SPI_FLASH
2389 Defines a default MTD partitioning scheme in the Linux MTD command
2390 line partitions format
2393 bool "reiser - Access to reiserfs filesystems"
2395 This provides two commands which operate on a resierfs filesystem,
2396 commonly used some years ago:
2398 reiserls - list files
2399 reiserload - load a file
2402 bool "yaffs2 - Access of YAFFS2 filesystem"
2406 This provides commands for accessing a YAFFS2 filesystem. Yet
2407 Another Flash Filesystem 2 is a filesystem designed specifically
2408 for NAND flash. It incorporates bad-block management and ensures
2409 that device writes are sequential regardless of filesystem
2413 bool "zfs - Access of ZFS filesystem"
2415 This provides commands to accessing a ZFS filesystem, commonly used
2416 on Solaris systems. Two sub-commands are provided:
2418 zfsls - list files in a directory
2419 zfsload - load a file
2421 See doc/README.zfs for more details.
2425 menu "Debug commands"
2427 config CMD_CBSYSINFO
2430 default y if SYS_COREBOOT
2432 This provides information about the coreboot sysinfo table stored in
2433 memory by coreboot before jumping to U-Boot. It can be useful for
2434 debugging the beaaviour of coreboot or U-Boot.
2437 bool "diag - Board diagnostics"
2439 This command provides access to board diagnostic tests. These are
2440 called Power-on Self Tests (POST). The command allows listing of
2441 available tests and running either all the tests, or specific tests
2445 bool "event - Show information about events"
2446 default y if EVENT_DEBUG
2448 This enables the 'event' command which provides information about
2449 events and event-handler routines. This can help to device event
2453 bool "irq - Show information about interrupts"
2454 depends on !ARM && !MIPS && !RISCV && !SH
2456 This enables two commands:
2458 interrupts - enable or disable interrupts
2459 irqinfo - print device-specific interrupt information
2462 bool "kgdb - Allow debugging of U-Boot with gdb"
2465 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2466 over a serial link for debugging purposes. This allows
2467 single-stepping, inspecting variables, etc. This is supported only
2468 on PowerPC at present.
2471 bool "log - Generation, control and access to logging"
2475 This provides access to logging features. It allows the output of
2476 log data to be controlled to a limited extent (setting up the default
2477 maximum log level for emitting of records). It also provides access
2478 to a command used for testing the log system.
2481 bool "trace - Support tracing of function calls and timing"
2485 Enables a command to control using of function tracing within
2486 U-Boot. This allows recording of call traces including timing
2487 information. The command can write data to memory for exporting
2488 for analysis (e.g. using bootchart). See doc/README.trace for full
2492 bool "avb - Android Verified Boot 2.0 operations"
2493 depends on AVB_VERIFY
2495 Enables a "avb" command to perform verification of partitions using
2496 Android Verified Boot 2.0 functionality. It includes such subcommands:
2497 avb init - initialize avb2 subsystem
2498 avb read_rb - read rollback index
2499 avb write_rb - write rollback index
2500 avb is_unlocked - check device lock state
2501 avb get_uuid - read and print uuid of a partition
2502 avb read_part - read data from partition
2503 avb read_part_hex - read data from partition and output to stdout
2504 avb write_part - write data to partition
2505 avb verify - run full verification chain
2507 config CMD_STACKPROTECTOR_TEST
2508 bool "Test command for stack protector"
2509 depends on STACKPROTECTOR
2511 Enable stackprot_test command
2512 The stackprot_test command will force a stack overrun to test
2513 the stack smashing detection mechanisms.
2518 tristate "Enable UBI - Unsorted block images commands"
2521 UBI is a software layer above MTD layer which admits use of LVM-like
2522 logical volumes on top of MTD devices, hides some complexities of
2523 flash chips like wear and bad blocks and provides some other useful
2524 capabilities. Please, consult the MTD web site for more details
2525 (www.linux-mtd.infradead.org). Activate this option if you want
2526 to use U-Boot UBI commands.
2527 It is also strongly encouraged to also enable CONFIG_MTD to get full
2530 config CMD_UBI_RENAME
2531 bool "Enable rename"
2534 Enable a "ubi" command to rename ubi volume:
2535 ubi rename <oldname> <newname>
2538 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2540 default y if CMD_UBI
2543 UBIFS is a file system for flash devices which works on top of UBI.
2545 config MMC_SPEED_MODE_SET
2546 bool "set speed mode using mmc command"
2550 Enable setting speed mode using mmc rescan and mmc dev commands.
2551 The speed mode is provided as the last argument in these commands
2552 and is indicated using the index from enum bus_mode in
2553 include/mmc.h. A speed mode can be set only if it has already
2554 been enabled in the device tree.
projects / platform / kernel / u-boot.git / blob