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
358 Add an ANSI terminal boot menu command.
363 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
364 image into RAM, dump image structure information, etc. Those dtb/dtbo
365 files should be merged in one dtb further, which needs to be passed to
366 the kernel, as part of a boot process.
370 depends on ANDROID_BOOT_IMAGE
372 Android Boot Image manipulation commands. Allows one to extract
373 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
374 obtain corresponding meta-information from boot.img.
376 See doc/android/boot-image.rst for details.
379 bool "bootelf, bootvx"
383 Boot an ELF/vxWorks image from the memory.
386 bool "Flattened Device Tree utility commands"
390 Do FDT related setup before booting into the Operating System.
392 config SUPPORT_EXTENSION_SCAN
396 bool "Extension board management command"
398 depends on SUPPORT_EXTENSION_SCAN
400 Enables the "extension" command, which allows to detect
401 extension boards connected to the system, and apply
402 corresponding Device Tree overlays.
408 Start an application at a given address.
414 Run the command in the given environment variable.
420 Print header information for application image.
425 List all images found in flash
431 Extract a part of a multi-image.
434 bool "spl export - Export boot information for Falcon boot"
437 Falcon mode allows booting directly from SPL into an Operating
438 System such as Linux, thus skipping U-Boot proper. See
439 doc/README.falcon for full information about how to use this
442 config CMD_SPL_NAND_OFS
443 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
444 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
447 This provides the offset of the command line arguments for Linux
448 when booting from NAND in Falcon mode. See doc/README.falcon
449 for full information about how to use this option (and also see
450 board/gateworks/gw_ventana/README for an example).
452 config CMD_SPL_NOR_OFS
453 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
454 depends on CMD_SPL && SPL_NOR_SUPPORT
457 This provides the offset of the command line arguments or dtb for
458 Linux when booting from NOR in Falcon mode.
460 config CMD_SPL_WRITE_SIZE
461 hex "Size of argument area"
465 This provides the size of the command-line argument area in NAND
466 flash used by Falcon-mode boot. See the documentation until CMD_SPL
469 config CMD_THOR_DOWNLOAD
470 bool "thor - TIZEN 'thor' download"
473 Implements the 'thor' download protocol. This is a way of
474 downloading a software update over USB from an attached host.
475 There is no documentation about this within the U-Boot source code
476 but you should be able to find something on the interwebs.
479 bool "zboot - x86 boot command"
481 With x86 machines it is common to boot a bzImage file which
482 contains both a kernel and a setup.bin file. The latter includes
483 configuration information from the dark ages which x86 boards still
484 need to pick things out of.
486 Consider using FIT in preference to this since it supports directly
487 booting both 32- and 64-bit kernels, as well as secure boot.
488 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
492 menu "Environment commands"
495 bool "ask for env variable"
497 Ask for environment variable
515 Edit environment variable.
520 Allow for searching environment variables
526 Save all environment variables into the compiled-in persistent
531 depends on CMD_SAVEENV
533 Erase environment variables from the compiled-in persistent
536 config CMD_ENV_EXISTS
540 Check if a variable is defined in the environment for use in
543 config CMD_ENV_CALLBACK
544 bool "env callbacks - print callbacks and their associated variables"
546 Some environment variable have callbacks defined by
547 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
548 For example changing "baudrate" adjust the serial baud rate. This
549 command lists the currently defined callbacks.
552 bool "env flags -print variables that have non-default flags"
554 Some environment variables have special flags that control their
555 behaviour. For example, serial# can only be written once and cannot
556 be deleted. This command shows the variables that have special
559 config CMD_NVEDIT_EFI
560 bool "env [set|print] -e - set/print UEFI variables"
561 depends on EFI_LOADER
564 UEFI variables are encoded as some form of U-Boot variables.
565 If enabled, we are allowed to set/print UEFI variables using
566 "env" command with "-e" option without knowing details.
568 config CMD_NVEDIT_INDIRECT
569 bool "env indirect - Sets environment value from another"
571 config CMD_NVEDIT_INFO
572 bool "env info - print or evaluate environment information"
574 Print environment information:
575 - env_valid : is environment valid
576 - env_ready : is environment imported into hash table
577 - env_use_default : is default environment used
579 This command can be optionally used for evaluation in scripts:
580 [-d] : evaluate whether default environment is used
581 [-p] : evaluate whether environment can be persisted
583 The result of multiple evaluations will be combined with AND.
585 config CMD_NVEDIT_LOAD
588 Load all environment variables from the compiled-in persistent
591 config CMD_NVEDIT_SELECT
594 Select the compiled-in persistent storage of environment variables.
598 menu "Memory commands"
603 Compute binary operations (xor, or, and) of byte arrays of arbitrary
604 size from memory and store the result in memory or the environment.
608 default y if BLOBLIST
610 Show information about the bloblist, a collection of binary blobs
611 held in memory that persist between SPL and U-Boot. In the case of
612 x86 devices the bloblist can be used to hold ACPI tables so that they
613 remain available in memory.
626 Add -v option to verify data against a crc32 checksum.
629 bool "eeprom - EEPROM subsystem"
631 (deprecated, needs conversion to driver model)
632 Provides commands to read and write EEPROM (Electrically Erasable
633 Programmable Read Only Memory) chips that are connected over an
636 config CMD_EEPROM_LAYOUT
637 bool "Enable layout-aware eeprom commands"
638 depends on CMD_EEPROM
640 (deprecated, needs conversion to driver model)
641 When enabled, additional eeprom sub-commands become available.
643 eeprom print - prints the contents of the eeprom in a human-readable
644 way (eeprom layout fields, and data formatted to be fit for human
647 eeprom update - allows user to update eeprom fields by specifying
648 the field name, and providing the new data in a human readable format
649 (same format as displayed by the eeprom print command).
651 Both commands can either auto detect the layout, or be told which
655 __weak int parse_layout_version(char *str)
656 - override to provide your own layout name parsing
657 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
659 - override to setup the layout metadata based on the version
660 __weak int eeprom_layout_detect(unsigned char *data)
661 - override to provide your own algorithm for detecting layout
664 - contains various printing and updating functions for common
665 types of eeprom fields. Can be used for defining
668 config EEPROM_LAYOUT_HELP_STRING
669 string "Tells user what layout names are supported"
670 depends on CMD_EEPROM_LAYOUT
671 default "<not defined>"
673 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
676 config SYS_I2C_EEPROM_BUS
677 int "I2C bus of the EEPROM device."
678 depends on CMD_EEPROM
681 config SYS_I2C_EEPROM_ADDR_LEN
682 int "Length in bytes of the EEPROM memory array address"
683 depends on CMD_EEPROM || ID_EEPROM
687 Note: This is NOT the chip address length!
689 config SYS_EEPROM_SIZE
690 depends on CMD_EEPROM
691 int "Size in bytes of the EEPROM device"
694 config SYS_EEPROM_PAGE_WRITE_BITS
695 int "Number of bits used to address bytes in a single page"
696 depends on CMD_EEPROM
699 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
700 A 64 byte page, for example would require six bits.
702 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
703 int "Number of milliseconds to delay between page writes"
704 depends on CMD_EEPROM || CMD_I2C
710 Infinite write loop on address range
716 Compute MD5 checksum.
720 depends on CMD_MD5SUM
722 Add -v option to verify data against an MD5 checksum.
727 Display memory information.
730 bool "md, mm, nm, mw, cp, cmp, base, loop"
735 mm - memory modify (auto-incrementing address)
736 nm - memory modify (constant address)
737 mw - memory write (fill)
740 base - print or set address offset
741 loop - initialize loop on address range
743 config CMD_MEM_SEARCH
744 bool "ms - Memory search"
746 Memory-search command
748 This allows searching through a region of memory looking for hex
749 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
750 support it). It is also possible to search for a string. The
751 command accepts a memory range and a list of values to search for.
752 The values need to appear in memory in the same order they are given
753 in the command. At most 10 matches can be returned at a time, but
754 pressing return will show the next 10 matches. Environment variables
755 are set for use with scripting (memmatches, memaddr, mempos).
758 bool "Enable cyclic md/mw commands"
759 depends on CMD_MEMORY
761 Add the "mdc" and "mwc" memory commands. These are cyclic
766 This command will print 4 bytes (10,11,12,13) each 500 ms.
768 => mwc.l 100 12345678 10
769 This command will write 12345678 to address 100 all 10 ms.
774 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
776 random - fill memory with random data
781 Simple RAM read/write test.
785 config SYS_ALT_MEMTEST
786 bool "Alternative test"
788 Use a more complete alternative memory test.
792 config SYS_ALT_MEMTEST_BITFLIP
796 The alternative memory test includes bitflip test since 2020.07.
797 The bitflip test significantly increases the overall test time.
798 Bitflip test can optionally be disabled here.
802 config SYS_MEMTEST_START
803 hex "default start address for mtest"
806 This is the default start address for mtest for simple read/write
807 test. If no arguments are given to mtest, default address is used
810 config SYS_MEMTEST_END
811 hex "default end address for mtest"
814 This is the default end address for mtest for simple read/write
815 test. If no arguments are given to mtest, default address is used
824 Compute SHA1 checksum.
826 config SHA1SUM_VERIFY
828 depends on CMD_SHA1SUM
830 Add -v option to verify data against a SHA1 checksum.
833 bool "strings - display strings in memory"
835 This works similarly to the Unix 'strings' command except that it
836 works with a memory range. String of printable characters found
837 within the range are displayed. The minimum number of characters
838 for a sequence to be considered a string can be provided.
842 menu "Compression commands"
846 default y if CMD_BOOTI
849 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
854 default y if CMD_BOOTI
857 Support decompressing an LZ4 image from memory region.
861 default y if CMD_BOOTI
864 Uncompress a zip-compressed memory region.
868 select GZIP_COMPRESSED
870 Compress a memory region with zlib deflate method.
874 menu "Device access commands"
877 #depends on FLASH_CFI_DRIVER
880 ARM Ltd reference designs flash partition access
883 bool "adc - Access Analog to Digital Converters info and data"
885 depends on DM_REGULATOR
887 Shows ADC device info and permit printing one-shot analog converted
888 data from a named Analog to Digital Converter.
893 depends on PARTITIONS
895 Read/modify/write the fields of Bootloader Control Block, usually
896 stored on the flash "misc" partition with its structure defined in:
897 https://android.googlesource.com/platform/bootable/recovery/+/master/
898 bootloader_message/include/bootloader_message/bootloader_message.h
900 Some real-life use-cases include (but are not limited to):
901 - Determine the "boot reason" (and act accordingly):
902 https://source.android.com/devices/bootloader/boot-reason
903 - Get/pass a list of commands from/to recovery:
904 https://android.googlesource.com/platform/bootable/recovery
905 - Inspect/dump the contents of the BCB fields
908 bool "bind/unbind - Bind or unbind a device to/from a driver"
911 Bind or unbind a device to/from a driver from the command line.
912 This is useful in situations where a device may be handled by several
913 drivers. For example, this can be used to bind a UDC to the usb ether
914 gadget driver from the command line.
917 bool "clk - Show clock frequencies"
920 Shows clock frequences by calling a sock_clk_dump() hook function.
921 This is depreated in favour of using the CLK uclass and accessing
922 clock values from associated drivers. However currently no command
926 bool "demo - Demonstration commands for driver model"
929 Provides a 'demo' command which can be used to play around with
930 driver model. To use this properly you will need to enable one or
931 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
932 Otherwise you will always get an empty list of devices. The demo
933 devices are defined in the sandbox device tree, so the easiest
934 option is to use sandbox and pass the -d point to sandbox's
941 Enables the command "dfu" which is used to have U-Boot create a DFU
942 class device via USB. This command requires that the "dfu_alt_info"
943 environment variable be set and define the alt settings to expose to
947 bool "dm - Access to driver model information"
950 Provides access to driver model data structures and information,
951 such as a list of devices, list of uclasses and the state of each
952 device (e.g. activated). This is not required for operation, but
953 can be useful to see the state of driver model for debugging or
957 bool "fastboot - Android fastboot support"
960 This enables the command "fastboot" which enables the Android
961 fastboot mode for the platform. Fastboot is a protocol for
962 downloading images, flashing and device control used on
963 Android devices. Fastboot requires either the network stack
964 enabled or support for acting as a USB device.
966 See doc/android/fastboot.rst for more information.
969 bool "flinfo, erase, protect"
971 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
974 flinfo - print FLASH memory information
976 protect - enable or disable FLASH write protection
985 config CMD_FPGA_LOADBP
986 bool "fpga loadbp - load partial bitstream (Xilinx only)"
989 Supports loading an FPGA device from a bitstream buffer containing
992 config CMD_FPGA_LOADFS
993 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
996 Supports loading an FPGA device from a FAT filesystem.
998 config CMD_FPGA_LOADMK
999 bool "fpga loadmk - load bitstream from image"
1002 Supports loading an FPGA device from a image generated by mkimage.
1004 config CMD_FPGA_LOADP
1005 bool "fpga loadp - load partial bitstream"
1008 Supports loading an FPGA device from a bitstream buffer containing
1009 a partial bitstream.
1011 config CMD_FPGA_LOAD_SECURE
1012 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1015 Enables the fpga loads command which is used to load secure
1016 (authenticated or encrypted or both) bitstreams on to FPGA.
1019 bool "fpgad - dump FPGA registers"
1021 (legacy, needs conversion to driver model)
1022 Provides a way to dump FPGA registers by calling the board-specific
1023 fpga_get_reg() function. This functions similarly to the 'md'
1027 bool "fuse - support for the fuse subssystem"
1029 (deprecated - needs conversion to driver model)
1030 This allows reading, sensing, programming or overriding fuses
1031 which control the behaviour of the device. The command uses the
1039 config CMD_GPIO_READ
1040 bool "gpio read - save GPIO value to variable"
1043 Enables the 'gpio read' command that saves the value
1044 of a GPIO pin to a variable.
1050 Control PWM channels, this allows invert/config/enable/disable PWM channels.
1053 bool "GPT (GUID Partition Table) command"
1054 select EFI_PARTITION
1055 select HAVE_BLOCK_DEVICE
1056 select PARTITION_UUIDS
1059 Enable the 'gpt' command to ready and write GPT style partition
1063 bool "GPT Random UUID generation"
1066 Enable the generation of partitions with random UUIDs if none
1069 config CMD_GPT_RENAME
1070 bool "GPT partition renaming commands"
1073 Enables the 'gpt' command to interchange names on two GPT
1074 partitions via the 'gpt swap' command or to rename single
1075 partitions via the 'rename' command.
1078 bool "ide - Support for IDE drivers"
1081 Provides an 'ide' command which allows accessing the IDE drive,
1082 resetting the IDE interface, printing the partition table and
1083 geting device info. It also enables the 'diskboot' command which
1084 permits booting from an IDE drive.
1087 bool "io - Support for performing I/O accesses"
1089 Provides an 'iod' command to display I/O space and an 'iow' command
1090 to write values to the I/O space. This can be useful for manually
1091 checking the state of devices during boot when debugging device
1095 bool "iotrace - Support for tracing I/O activity"
1097 Provides an 'iotrace' command which supports recording I/O reads and
1098 writes in a trace buffer in memory . It also maintains a checksum
1099 of the trace records (even if space is exhausted) so that the
1100 sequence of I/O accesses can be verified.
1102 When debugging drivers it is useful to see what I/O accesses were
1103 done and in what order.
1105 Even if the individual accesses are of little interest it can be
1106 useful to verify that the access pattern is consistent each time
1107 an operation is performed. In this case a checksum can be used to
1108 characterise the operation of a driver. The checksum can be compared
1109 across different runs of the operation to verify that the driver is
1112 In particular, when performing major refactoring of the driver, where
1113 the access pattern should not change, the checksum provides assurance
1114 that the refactoring work has not broken the driver.
1116 This works by sneaking into the io.h heder for an architecture and
1117 redirecting I/O accesses through iotrace's tracing mechanism.
1119 For now no commands are provided to examine the trace buffer. The
1120 format is fairly simple, so 'md' is a reasonable substitute.
1122 Note: The checksum feature is only useful for I/O regions where the
1123 contents do not change outside of software control. Where this is not
1124 suitable you can fall back to manually comparing the addresses. It
1125 might be useful to enhance tracing to only checksum the accesses and
1126 not the data read/written.
1136 bool "w1 - Support for Dallas 1-Wire protocol"
1138 Dallas 1-wire protocol support
1144 Load a binary file over serial line.
1150 Load an S-Record file over serial line
1154 bool "lsblk - list block drivers and devices"
1156 Print list of available block device drivers, and for each, the list
1157 of known block devices.
1160 bool "MBR (Master Boot Record) command"
1161 select DOS_PARTITION
1162 select HAVE_BLOCK_DEVICE
1164 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1165 style partition tables.
1171 Enable the command "misc" for accessing miscellaneous devices with
1172 a MISC uclass driver. The command provides listing all MISC devices
1173 as well as read and write functionalities via their drivers.
1179 MMC memory mapped support.
1183 config CMD_BKOPS_ENABLE
1184 bool "mmc bkops enable"
1187 Enable command for setting manual background operations handshake
1188 on a eMMC device. The feature is optionally available on eMMC devices
1189 conforming to standard >= 4.41.
1192 bool "Enable support for RPMB in the mmc command"
1193 depends on SUPPORT_EMMC_RPMB
1195 Enable the commands for reading, writing and programming the
1196 key for the Replay Protection Memory Block partition in eMMC.
1198 config CMD_MMC_SWRITE
1200 depends on MMC_WRITE
1203 Enable support for the "mmc swrite" command to write Android sparse
1212 Enable storage cloning over block devices, useful for
1213 initial flashing by external block device without network
1216 config CMD_OPTEE_RPMB
1217 bool "Enable read/write support on RPMB via OPTEE"
1218 depends on SUPPORT_EMMC_RPMB && OPTEE
1220 Enable the commands for reading, writing persistent named values
1221 in the Replay Protection Memory Block partition in eMMC by
1222 using Persistent Objects in OPTEE
1227 select MTD_PARTITIONS
1229 MTD commands support.
1233 depends on MULTIPLEXER
1235 List, select, and deselect mux controllers on the fly.
1239 default y if NAND_SUNXI
1240 depends on MTD_RAW_NAND
1245 config CMD_NAND_TRIMFFS
1246 bool "nand write.trimffs"
1247 default y if ARCH_SUNXI
1249 Allows one to skip empty pages when flashing something on a NAND.
1251 config CMD_NAND_LOCK_UNLOCK
1252 bool "nand lock/unlock"
1254 NAND locking support.
1256 config CMD_NAND_TORTURE
1259 NAND torture support.
1268 NVM Express device support
1271 bool "onenand - access to onenand device"
1274 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1275 various useful features. This command allows reading, writing,
1276 and erasing blocks. It allso provides a way to show and change
1277 bad blocks, and test the device.
1282 Enable the 'osd' command which allows to query information from and
1283 write text data to a on-screen display (OSD) device; a virtual device
1284 associated with a display capable of displaying a text overlay on the
1285 display it's associated with..
1289 depends on PARTITIONS
1290 select HAVE_BLOCK_DEVICE
1291 select PARTITION_UUIDS
1293 Read and display information about the partition table on
1297 bool "pci - Access PCI devices"
1299 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1300 used on some devices to allow the CPU to communicate with its
1301 peripherals. Sub-commands allow bus enumeration, displaying and
1302 changing configuration space and a few other features.
1305 bool "pinmux - show pins muxing"
1307 default y if PINCTRL
1309 Parse all available pin-controllers and show pins muxing. This
1310 is useful for debug purpoer to check the pin muxing and to know if
1311 a pin is configured as a GPIO or as an alternate function.
1316 Poweroff/Shutdown the system
1319 bool "read - Read binary data from a partition"
1321 Provides low-level access to the data in a partition.
1323 config CMD_REMOTEPROC
1325 depends on REMOTEPROC
1327 Support for Remote Processor control
1330 bool "sata - Access SATA subsystem"
1333 SATA (Serial Advanced Technology Attachment) is a serial bus
1334 standard for connecting to hard drives and other storage devices.
1335 This command provides information about attached devices and allows
1336 reading, writing and other operations.
1338 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1339 Attachment, where AT refers to an IBM AT (Advanced Technology)
1340 computer released in 1984.
1343 bool "saves - Save a file over serial in S-Record format"
1345 Provides a way to save a binary file using the Motorola S-Record
1346 format over the serial line.
1349 bool "scsi - Access to SCSI devices"
1352 This provides a 'scsi' command which provides access to SCSI (Small
1353 Computer System Interface) devices. The command provides a way to
1354 scan the bus, reset the bus, read and write data and get information
1358 bool "sdram - Print SDRAM configuration information"
1360 Provides information about attached SDRAM. This assumed that the
1361 SDRAM has an EEPROM with information that can be read using the
1362 I2C bus. This is only available on some boards.
1366 depends on DM_SPI_FLASH || SPI_FLASH
1367 default y if DM_SPI_FLASH
1372 bool "sf test - Allow testing of SPI flash"
1375 Provides a way to test that SPI flash is working correctly. The
1376 test is destructive, in that an area of SPI flash must be provided
1377 for the test to use. Performance information is also provided,
1378 measuring the performance of reading, writing and erasing in
1379 Mbps (Million Bits Per Second). This value should approximately
1380 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1381 everything is working properly.
1384 bool "sspi - Command to access spi device"
1387 SPI utility command.
1389 config DEFAULT_SPI_BUS
1390 int "default spi bus used by sspi command"
1394 config DEFAULT_SPI_MODE
1395 hex "default spi mode used by sspi command (see include/spi.h)"
1400 bool "tsi148 - Command to access tsi148 device"
1402 This provides various sub-commands to initialise and configure the
1403 Turndra tsi148 device. See the command help for full details.
1406 bool "Enable UFS - Universal Flash Subsystem commands"
1409 "This provides commands to initialise and configure universal flash
1413 bool "universe - Command to set up the Turndra Universe controller"
1415 This allows setting up the VMEbus provided by this controller.
1416 See the command help for full details.
1421 select HAVE_BLOCK_DEVICE
1427 select USB_FUNCTION_SDP
1429 Enables the command "sdp" which is used to have U-Boot emulating the
1430 Serial Download Protocol (SDP) via USB.
1434 depends on USB_FUNCTION_ROCKUSB
1436 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1437 read/write info, image to/from devices. This enable rockusb command
1438 support to communication with rockusb device. for more detail about
1439 this command, please read doc/README.rockusb.
1441 config CMD_USB_MASS_STORAGE
1442 bool "UMS usb mass storage"
1443 depends on USB_GADGET_DOWNLOAD
1444 select USB_FUNCTION_MASS_STORAGE
1445 depends on BLK && USB_GADGET
1447 Enables the command "ums" and the USB mass storage support to the
1448 export a block device: U-Boot, the USB device, acts as a simple
1449 external hard drive plugged on the host USB port.
1452 bool "Xen para-virtualized block device"
1456 Xen para-virtualized block device support
1461 depends on HAVE_BLOCK_DEVICE
1464 VirtIO block device support
1470 This provides commands to control the watchdog timer devices.
1476 Enable the command "axi" for accessing AXI (Advanced eXtensible
1477 Interface) busses, a on-chip interconnect specification for managing
1478 functional blocks in SoC designs, which is also often used in designs
1479 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1483 menu "Shell scripting commands"
1489 Echo args to console
1495 Return true/false on integer compare.
1501 Run script from memory
1507 Evaluate boolean and math expressions and store the result in an env
1509 Also supports loading the value at a memory location into a variable.
1510 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1512 config CMD_SETEXPR_FMT
1514 depends on CMD_SETEXPR
1516 Evaluate format string expression and store result in an environment
1521 menu "Android support commands"
1523 config CMD_AB_SELECT
1525 depends on ANDROID_AB
1527 On Android devices with more than one boot slot (multiple copies of
1528 the kernel and system images) this provides a command to select which
1529 slot should be used to boot from and register the boot attempt. This
1530 is used by the new A/B update model where one slot is updated in the
1531 background while running from the other slot.
1538 bool "Network commands"
1548 bootp - boot image via network using BOOTP/TFTP protocol
1552 depends on CMD_BOOTP
1554 Boot image via network using DHCP/TFTP protocol
1556 config BOOTP_MAY_FAIL
1557 bool "Allow for the BOOTP/DHCP server to not be found"
1558 depends on CMD_BOOTP
1560 If the DHCP server is not found after the configured retry count, the
1561 call will fail instead of starting over. This can be used to fail
1562 over to Link-local IP address configuration if the DHCP server is not
1565 config BOOTP_BOOTPATH
1566 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1568 depends on CMD_BOOTP
1570 Even though the config is called BOOTP_BOOTPATH, it stores the
1571 path in the variable 'rootpath'.
1573 config BOOTP_VENDOREX
1574 bool "Support vendor extensions from BOOTP/DHCP server"
1575 depends on CMD_BOOTP
1577 config BOOTP_BOOTFILESIZE
1578 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1579 depends on CMD_BOOTP
1582 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1584 depends on CMD_BOOTP
1586 The primary DNS server is stored as 'dnsip'. If two servers are
1587 returned, you must set BOOTP_DNS2 to store that second server IP
1591 bool "Store 'dnsip2' from BOOTP/DHCP server"
1592 depends on BOOTP_DNS
1594 If a DHCP client requests the DNS server IP from a DHCP server,
1595 it is possible that more than one DNS serverip is offered to the
1596 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1597 server IP will be stored in the additional environment
1598 variable "dnsip2". The first DNS serverip is always
1599 stored in the variable "dnsip", when BOOTP_DNS is defined.
1601 config BOOTP_GATEWAY
1602 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1604 depends on CMD_BOOTP
1606 config BOOTP_HOSTNAME
1607 bool "Request & store 'hostname' from BOOTP/DHCP server"
1609 depends on CMD_BOOTP
1611 The name may or may not be qualified with the local domain name.
1613 config BOOTP_PREFER_SERVERIP
1614 bool "serverip variable takes precedent over DHCP server IP."
1615 depends on CMD_BOOTP
1617 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1619 With this option enabled, the 'serverip' variable in the environment
1620 takes precedence over DHCP server IP and will only be set by the DHCP
1621 server if not already set in the environment.
1623 config BOOTP_SUBNETMASK
1624 bool "Request & store 'netmask' from BOOTP/DHCP server"
1626 depends on CMD_BOOTP
1628 config BOOTP_NISDOMAIN
1629 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1630 depends on CMD_BOOTP
1632 config BOOTP_NTPSERVER
1633 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1634 depends on CMD_BOOTP
1636 config BOOTP_TIMEOFFSET
1637 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1638 depends on CMD_BOOTP && CMD_SNTP
1643 Selecting this will allow capturing all Ethernet packets and store
1644 them in physical memory in a PCAP formated file,
1645 later to be analyzed by PCAP reader application (IE. WireShark).
1648 bool "Send PXE client arch to BOOTP/DHCP server"
1650 depends on CMD_BOOTP && CMD_PXE
1652 Supported for ARM, ARM64, and x86 for now.
1654 config BOOTP_PXE_CLIENTARCH
1656 depends on BOOTP_PXE
1657 default 0x16 if ARM64
1661 config BOOTP_VCI_STRING
1663 depends on CMD_BOOTP
1664 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1665 default "U-Boot.armv8" if ARM64
1666 default "U-Boot.arm" if ARM
1673 tftpboot - boot image via network using TFTP protocol
1677 depends on CMD_TFTPBOOT
1679 TFTP put command, for uploading files to a server
1683 depends on CMD_TFTPBOOT
1685 Act as a TFTP server and boot the first received file
1687 config NET_TFTP_VARS
1688 bool "Control TFTP timeout and count through environment"
1689 depends on CMD_TFTPBOOT
1692 If set, allows controlling the TFTP timeout through the
1693 environment variable tftptimeout, and the TFTP maximum
1694 timeout count through the variable tftptimeoutcountmax.
1695 If unset, timeout and maximum are hard-defined as 1 second
1696 and 10 timouts per TFTP transfer.
1701 Boot image via network using RARP/TFTP protocol
1707 Boot image via network using NFS protocol.
1710 int "Timeout in milliseconds for NFS mounts"
1714 Timeout in milliseconds used in NFS protocol. If you encounter
1715 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1722 If set, allows 802.3(clause 22) MII Management functions interface access
1723 The management interface specified in Clause 22 provides
1724 a simple, two signal, serial interface to connect a
1725 Station Management entity and a managed PHY for providing access
1726 to management parameters and services.
1727 The interface is referred to as the MII management interface.
1730 bool "Call mii_init() in the mii command"
1731 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1737 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1738 The MDIO interface is orthogonal to the MII interface and extends
1739 it by adding access to more registers through indirect addressing.
1744 Send ICMP ECHO_REQUEST to network host
1749 Perform CDP network configuration
1755 Synchronize RTC via network
1760 Lookup the IP of a hostname
1762 config CMD_LINK_LOCAL
1766 Acquire a network IP address using the link-local protocol
1773 Allow control of L2 Ethernet switch commands. These are supported
1774 by the vsc9953 Ethernet driver at present. Sub-commands allow
1775 operations such as enabling / disabling a port and
1776 viewing/maintaining the filtering database (FDB)
1782 Boot image via network using PXE protocol
1787 Wait for wake-on-lan Magic Packet
1791 menu "Misc commands"
1794 bool "Enable 'bmp' command"
1795 depends on LCD || DM_VIDEO || VIDEO
1797 This provides a way to obtain information about a BMP-format image
1798 and to display it. BMP (which presumably stands for BitMaP) is a
1799 file format defined by Microsoft which supports images of various
1800 depths, formats and compression methods. Headers on the file
1801 determine the formats used. This command can be used by first loading
1802 the image into RAM, then using this command to look at it or display
1805 config CMD_BOOTCOUNT
1807 depends on BOOTCOUNT_LIMIT
1809 Enable the bootcount command, which allows interrogation and
1810 reset of the bootcounter.
1813 bool "Enable board-specific commands"
1815 (deprecated: instead, please define a Kconfig option for each command)
1817 Some boards have board-specific commands which are only enabled
1818 during developemnt and need to be turned off for production. This
1819 option provides a way to control this. The commands that are enabled
1820 vary depending on the board.
1822 config CMD_BLOCK_CACHE
1823 bool "blkcache - control and stats for block cache"
1824 depends on BLOCK_CACHE
1825 default y if BLOCK_CACHE
1827 Enable the blkcache command, which can be used to control the
1828 operation of the cache functions.
1829 This is most useful when fine-tuning the operation of the cache
1830 during development, but also allows the cache to be disabled when
1831 it might hurt performance (e.g. when using the ums command).
1838 Enable the 'button' command which allows to get the status of
1839 buttons supported by the board. The buttonss can be listed with
1840 'button list' and state can be known with 'button <label>'.
1841 Any button drivers can be controlled with this command, e.g.
1845 bool "icache or dcache"
1847 Enable the "icache" and "dcache" commands
1849 config CMD_CONITRACE
1850 bool "conitrace - trace console input codes"
1852 Enable the 'conitrace' command which displays the codes received
1853 from the console input as hexadecimal numbers.
1856 bool "Enable clear screen command 'cls'"
1857 depends on DM_VIDEO || LCD || VIDEO
1860 Enable the 'cls' command which clears the screen contents
1861 on video frame buffer.
1864 bool "efidebug - display/configure UEFI environment"
1865 depends on EFI_LOADER
1866 select EFI_DEVICE_PATH_TO_TEXT
1868 Enable the 'efidebug' command which provides a subset of UEFI
1869 shell utility with simplified functionality. It will be useful
1870 particularly for managing boot parameters as well as examining
1871 various EFI status for debugging.
1873 config CMD_EXCEPTION
1874 bool "exception - raise exception"
1875 depends on ARM || RISCV || SANDBOX || X86
1877 Enable the 'exception' command which allows to raise an exception.
1884 Enable the 'led' command which allows for control of LEDs supported
1885 by the board. The LEDs can be listed with 'led list' and controlled
1886 with led on/off/togle/blink. Any LED drivers can be controlled with
1887 this command, e.g. led_gpio.
1894 Enable the 'date' command for getting/setting the time/date in RTC
1901 Enable the 'rtc' command for low-level access to RTC devices.
1906 Run commands and summarize execution time.
1909 bool "gettime - read elapsed time"
1911 Enable the 'gettime' command which reads the elapsed time since
1912 U-Boot started running. This shows the time in seconds and
1913 milliseconds. See also the 'bootstage' command which provides more
1914 flexibility for boot timing.
1921 Print bytes from the hardware random number generator.
1923 config CMD_KASLRSEED
1927 Set the kaslr-seed in the chosen node with entropy provided by a
1928 hardware random number generator.
1934 Delay execution for some time
1937 bool "support for multiprocessor commands"
1941 This enables commands to bringup different processors
1942 in multiprocessor cases.
1947 Access the system timer.
1953 This provides basic access to the U-Boot's sound support. The main
1954 feature is to play a beep.
1956 sound init - set up sound system
1957 sound play - play a sound
1963 Boot image via local extlinux.conf file
1969 This provides access to the QEMU firmware interface. The main
1970 feature is to allow easy loading of files passed to qemu-system
1971 via -kernel / -initrd
1976 This provides access to Linux PStore with Rammoops backend. The main
1977 feature is to allow to display or save PStore records.
1979 See doc/pstore.rst for more information.
1983 config CMD_PSTORE_MEM_ADDR
1984 hex "Memory Address"
1985 depends on CMD_PSTORE
1987 Base addr used for PStore ramoops memory, should be identical to
1988 ramoops.mem_address parameter used by kernel
1990 config CMD_PSTORE_MEM_SIZE
1992 depends on CMD_PSTORE
1995 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1996 parameter used by kernel, a power of 2 and larger than the sum of the
1999 config CMD_PSTORE_RECORD_SIZE
2000 hex "Dump record size"
2001 depends on CMD_PSTORE
2004 Size of each dump done on oops/panic, should be identical to
2005 ramoops.record_size parameter used by kernel and a power of 2
2008 config CMD_PSTORE_CONSOLE_SIZE
2009 hex "Kernel console log size"
2010 depends on CMD_PSTORE
2013 Size of kernel console log, should be identical to
2014 ramoops.console_size parameter used by kernel and a power of 2
2017 config CMD_PSTORE_FTRACE_SIZE
2018 hex "FTrace log size"
2019 depends on CMD_PSTORE
2022 Size of ftrace log, should be identical to ramoops.ftrace_size
2023 parameter used by kernel and a power of 2
2025 config CMD_PSTORE_PMSG_SIZE
2026 hex "User space message log size"
2027 depends on CMD_PSTORE
2030 Size of user space message log, should be identical to
2031 ramoops.pmsg_size parameter used by kernel and a power of 2
2033 config CMD_PSTORE_ECC_SIZE
2035 depends on CMD_PSTORE
2038 if non-zero, the option enables ECC support and specifies ECC buffer
2039 size in bytes (1 is a special value, means 16 bytes ECC), should be
2040 identical to ramoops.ramoops_ecc parameter used by kernel
2044 source "cmd/mvebu/Kconfig"
2047 bool "terminal - provides a way to attach a serial terminal"
2049 Provides a 'cu'-like serial terminal command. This can be used to
2050 access other serial ports from the system console. The terminal
2051 is very simple with no special processing of characters. As with
2052 cu, you can press ~. (tilde followed by period) to exit.
2055 bool "uuid, guid - generation of unique IDs"
2058 This enables two commands:
2060 uuid - generate random Universally Unique Identifier
2061 guid - generate Globally Unique Identifier based on random UUID
2063 The two commands are very similar except for the endianness of the
2068 source "cmd/ti/Kconfig"
2070 config CMD_BOOTSTAGE
2071 bool "Enable the 'bootstage' command"
2072 depends on BOOTSTAGE
2074 Add a 'bootstage' command which supports printing a report
2075 and un/stashing of bootstage data.
2077 menu "Power commands"
2079 bool "Enable Driver Model PMIC command"
2082 This is the pmic command, based on a driver model pmic's API.
2083 Command features are unchanged:
2084 - list - list pmic devices
2085 - pmic dev <id> - show or [set] operating pmic device (NEW)
2086 - pmic dump - dump registers
2087 - pmic read address - read byte of register at address
2088 - pmic write address - write byte to register at address
2089 The only one change for this command is 'dev' subcommand.
2091 config CMD_REGULATOR
2092 bool "Enable Driver Model REGULATOR command"
2093 depends on DM_REGULATOR
2095 This command is based on driver model regulator's API.
2096 User interface features:
2097 - list - list regulator devices
2098 - regulator dev <id> - show or [set] operating regulator device
2099 - regulator info - print constraints info
2100 - regulator status - print operating status
2101 - regulator value <val] <-f> - print/[set] voltage value [uV]
2102 - regulator current <val> - print/[set] current value [uA]
2103 - regulator mode <id> - print/[set] operating mode id
2104 - regulator enable - enable the regulator output
2105 - regulator disable - disable the regulator output
2107 The '-f' (force) option can be used for set the value which exceeds
2108 the limits, which are found in device-tree and are kept in regulator's
2109 uclass plat structure.
2113 menu "Security commands"
2115 bool "Enable the 'aes' command"
2118 This provides a means to encrypt and decrypt data using the AES
2119 (Advanced Encryption Standard). This algorithm uses a symetric key
2120 and is widely used as a streaming cipher. Different key lengths are
2121 supported by the algorithm but this command only supports 128 bits
2125 bool "Enable the 'blob' command"
2126 depends on !MX6ULL && !MX6SLL && !MX6SL
2127 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2129 This is used with the Freescale secure boot mechanism.
2131 Freescale's SEC block has built-in Blob Protocol which provides
2132 a method for protecting user-defined data across system power
2133 cycles. SEC block protects data in a data structure called a Blob,
2134 which provides both confidentiality and integrity protection.
2136 Encapsulating data as a blob
2137 Each time that the Blob Protocol is used to protect data, a
2138 different randomly generated key is used to encrypt the data.
2139 This random key is itself encrypted using a key which is derived
2140 from SoC's non-volatile secret key and a 16 bit Key identifier.
2141 The resulting encrypted key along with encrypted data is called a
2142 blob. The non-volatile secure key is available for use only during
2145 During decapsulation, the reverse process is performed to get back
2149 blob enc - encapsulating data as a cryptgraphic blob
2150 blob dec - decapsulating cryptgraphic blob to get the data
2154 blob enc src dst len km
2156 Encapsulate and create blob of data $len bytes long
2157 at address $src and store the result at address $dst.
2158 $km is the 16 byte key modifier is also required for
2159 generation/use as key for cryptographic operation. Key
2160 modifier should be 16 byte long.
2162 blob dec src dst len km
2164 Decapsulate the blob of data at address $src and
2165 store result of $len byte at addr $dst.
2166 $km is the 16 byte key modifier is also required for
2167 generation/use as key for cryptographic operation. Key
2168 modifier should be 16 byte long.
2171 bool "Support 'hash' command"
2174 This provides a way to hash data in memory using various supported
2175 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2176 saved to memory or to an environment variable. It is also possible
2177 to verify a hash against data in memory.
2180 bool "Support the 'hvc' command"
2181 depends on ARM_SMCCC
2183 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2184 development and testing.
2187 bool "Support the 'smc' command"
2188 depends on ARM_SMCCC
2190 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2191 development and testing.
2197 Add -v option to verify data against a hash.
2200 bool "scp03 - SCP03 enable and rotate/provision operations"
2203 This command provides access to a Trusted Application
2204 running in a TEE to request Secure Channel Protocol 03
2205 (SCP03) enablement and/or rotation of its SCP03 keys.
2214 bool "Enable the 'tpm' command"
2215 depends on TPM_V1 || TPM_V2
2216 select CMD_TPM_V1 if TPM_V1
2217 select CMD_TPM_V2 if TPM_V2
2219 This provides a means to talk to a TPM from the command line. A wide
2220 range of commands if provided - see 'tpm help' for details. The
2221 command requires a suitable TPM on your board and the correct driver
2227 bool "Enable the 'tpm test' command"
2230 This provides a a series of tests to confirm that the TPMv1.x is
2231 working correctly. The tests cover initialisation, non-volatile RAM,
2232 extend, global lock and checking that timing is within expectations.
2233 The tests pass correctly on Infineon TPMs but may need to be adjusted
2240 menu "Firmware commands"
2242 bool "Enable crosec command"
2246 Enable command-line access to the Chrome OS EC (Embedded
2247 Controller). This provides the 'crosec' command which has
2248 a number of sub-commands for performing EC tasks such as
2249 updating its flash, accessing a small saved context area
2250 and talking to the I2C bus behind the EC (if there is one).
2253 menu "Filesystem commands"
2255 bool "Enable the 'btrsubvol' command"
2258 This enables the 'btrsubvol' command to list subvolumes
2259 of a BTRFS filesystem. There are no special commands for
2260 listing BTRFS directories or loading BTRFS files - this
2261 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2262 when BTRFS is enabled (see FS_BTRFS).
2265 bool "Enable the 'cbfs' command"
2268 Define this to enable support for reading from a Coreboot
2269 filesystem. This is a ROM-based filesystem used for accessing files
2270 on systems that use coreboot as the first boot-loader and then load
2271 U-Boot to actually boot the Operating System. Available commands are
2272 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2275 bool "Enable the 'cramfs' command"
2276 depends on FS_CRAMFS
2278 This provides commands for dealing with CRAMFS (Compressed ROM
2279 filesystem). CRAMFS is useful when space is tight since files are
2280 compressed. Two commands are provided:
2282 cramfsls - lists files in a cramfs image
2283 cramfsload - loads a file from a cramfs image
2286 bool "EROFS command support"
2289 Support for the EROFS fs
2292 bool "ext2 command support"
2295 Enables EXT2 FS command
2298 bool "ext4 command support"
2301 Enables EXT4 FS command
2303 config CMD_EXT4_WRITE
2305 bool "ext4 write command support"
2308 Enables EXT4 FS write command
2311 bool "FAT command support"
2314 Support for the FAT fs
2317 bool "SquashFS command support"
2320 Enables SquashFS filesystem commands (e.g. load, ls).
2322 config CMD_FS_GENERIC
2323 bool "filesystem commands"
2325 Enables filesystem commands (e.g. load, ls) that work for multiple
2329 bool "fsuuid command"
2331 Enables fsuuid command for filesystem UUID.
2334 bool "jffs2 command"
2337 Enables commands to support the JFFS2 (Journalling Flash File System
2338 version 2) filesystem. This enables fsload, ls and fsinfo which
2339 provide the ability to load files, list directories and obtain
2340 filesystem information.
2343 string "Default device for JFFS2"
2344 depends on CMD_JFFS2
2347 The default device to use with the jffs2 command.
2349 config JFFS2_PART_OFFSET
2350 hex "Default offset within flash to locate the JFFS2 image"
2351 depends on CMD_JFFS2
2354 The default offset within flash to locate the JFFS2 image.
2356 config JFFS2_PART_SIZE
2357 hex "Default size of JFFS2 partition"
2358 depends on CMD_JFFS2
2361 The default size of the JFFS2 partition
2364 bool "MTD partition support"
2367 MTD partitioning tool support.
2368 It is strongly encouraged to avoid using this command
2369 anymore along with 'sf', 'nand', 'onenand'. One can still
2370 declare the partitions in the mtdparts environment variable
2371 but better use the MTD stack and the 'mtd' command instead.
2373 config CMD_MTDPARTS_SPREAD
2374 bool "Padd partition size to take account of bad blocks"
2375 depends on CMD_MTDPARTS
2377 This enables the 'spread' sub-command of the mtdparts command.
2378 This command will modify the existing mtdparts variable by increasing
2379 the size of the partitions such that 1) each partition's net size is
2380 at least as large as the size specified in the mtdparts variable and
2381 2) each partition starts on a good block.
2383 config CMD_MTDPARTS_SHOW_NET_SIZES
2384 bool "Show net size (w/o bad blocks) of partitions"
2385 depends on CMD_MTDPARTS
2387 Adds two columns to the printed partition table showing the
2388 effective usable size of a partition, if bad blocks are taken
2391 config MTDIDS_DEFAULT
2392 string "Default MTD IDs"
2393 depends on MTD || SPI_FLASH
2395 Defines a default MTD IDs list for use with MTD partitions in the
2396 Linux MTD command line partitions format.
2398 config MTDPARTS_DEFAULT
2399 string "Default MTD partition scheme"
2400 depends on MTD || SPI_FLASH
2402 Defines a default MTD partitioning scheme in the Linux MTD command
2403 line partitions format
2406 bool "reiser - Access to reiserfs filesystems"
2408 This provides two commands which operate on a resierfs filesystem,
2409 commonly used some years ago:
2411 reiserls - list files
2412 reiserload - load a file
2415 bool "yaffs2 - Access of YAFFS2 filesystem"
2419 This provides commands for accessing a YAFFS2 filesystem. Yet
2420 Another Flash Filesystem 2 is a filesystem designed specifically
2421 for NAND flash. It incorporates bad-block management and ensures
2422 that device writes are sequential regardless of filesystem
2426 bool "zfs - Access of ZFS filesystem"
2428 This provides commands to accessing a ZFS filesystem, commonly used
2429 on Solaris systems. Two sub-commands are provided:
2431 zfsls - list files in a directory
2432 zfsload - load a file
2434 See doc/README.zfs for more details.
2438 menu "Debug commands"
2440 config CMD_CBSYSINFO
2443 default y if SYS_COREBOOT
2445 This provides information about the coreboot sysinfo table stored in
2446 memory by coreboot before jumping to U-Boot. It can be useful for
2447 debugging the beaaviour of coreboot or U-Boot.
2450 bool "diag - Board diagnostics"
2452 This command provides access to board diagnostic tests. These are
2453 called Power-on Self Tests (POST). The command allows listing of
2454 available tests and running either all the tests, or specific tests
2458 bool "event - Show information about events"
2459 default y if EVENT_DEBUG
2461 This enables the 'event' command which provides information about
2462 events and event-handler routines. This can help to device event
2466 bool "irq - Show information about interrupts"
2467 depends on !ARM && !MIPS && !RISCV && !SH
2469 This enables two commands:
2471 interrupts - enable or disable interrupts
2472 irqinfo - print device-specific interrupt information
2475 bool "kgdb - Allow debugging of U-Boot with gdb"
2478 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2479 over a serial link for debugging purposes. This allows
2480 single-stepping, inspecting variables, etc. This is supported only
2481 on PowerPC at present.
2484 bool "log - Generation, control and access to logging"
2488 This provides access to logging features. It allows the output of
2489 log data to be controlled to a limited extent (setting up the default
2490 maximum log level for emitting of records). It also provides access
2491 to a command used for testing the log system.
2494 bool "trace - Support tracing of function calls and timing"
2498 Enables a command to control using of function tracing within
2499 U-Boot. This allows recording of call traces including timing
2500 information. The command can write data to memory for exporting
2501 for analysis (e.g. using bootchart). See doc/README.trace for full
2505 bool "avb - Android Verified Boot 2.0 operations"
2506 depends on AVB_VERIFY
2508 Enables a "avb" command to perform verification of partitions using
2509 Android Verified Boot 2.0 functionality. It includes such subcommands:
2510 avb init - initialize avb2 subsystem
2511 avb read_rb - read rollback index
2512 avb write_rb - write rollback index
2513 avb is_unlocked - check device lock state
2514 avb get_uuid - read and print uuid of a partition
2515 avb read_part - read data from partition
2516 avb read_part_hex - read data from partition and output to stdout
2517 avb write_part - write data to partition
2518 avb verify - run full verification chain
2520 config CMD_STACKPROTECTOR_TEST
2521 bool "Test command for stack protector"
2522 depends on STACKPROTECTOR
2524 Enable stackprot_test command
2525 The stackprot_test command will force a stack overrun to test
2526 the stack smashing detection mechanisms.
2531 tristate "Enable UBI - Unsorted block images commands"
2534 UBI is a software layer above MTD layer which admits use of LVM-like
2535 logical volumes on top of MTD devices, hides some complexities of
2536 flash chips like wear and bad blocks and provides some other useful
2537 capabilities. Please, consult the MTD web site for more details
2538 (www.linux-mtd.infradead.org). Activate this option if you want
2539 to use U-Boot UBI commands.
2540 It is also strongly encouraged to also enable CONFIG_MTD to get full
2543 config CMD_UBI_RENAME
2544 bool "Enable rename"
2547 Enable a "ubi" command to rename ubi volume:
2548 ubi rename <oldname> <newname>
2551 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2553 default y if CMD_UBI
2556 UBIFS is a file system for flash devices which works on top of UBI.
2558 config MMC_SPEED_MODE_SET
2559 bool "set speed mode using mmc command"
2563 Enable setting speed mode using mmc rescan and mmc dev commands.
2564 The speed mode is provided as the last argument in these commands
2565 and is indicated using the index from enum bus_mode in
2566 include/mmc.h. A speed mode can be set only if it has already
2567 been enabled in the device tree.
projects / platform / kernel / u-boot.git / blob