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.
360 config CMD_BOOTMENU_ENTER_UBOOT_CONSOLE
361 bool "Allow Bootmenu to enter the U-Boot console"
362 depends on CMD_BOOTMENU
365 Add an entry to enter U-Boot console in bootmenu.
366 If this option is disabled, user can not enter
367 the U-Boot console from bootmenu. It increases
373 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
374 image into RAM, dump image structure information, etc. Those dtb/dtbo
375 files should be merged in one dtb further, which needs to be passed to
376 the kernel, as part of a boot process.
380 depends on ANDROID_BOOT_IMAGE
382 Android Boot Image manipulation commands. Allows one to extract
383 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
384 obtain corresponding meta-information from boot.img.
386 See doc/android/boot-image.rst for details.
389 bool "bootelf, bootvx"
393 Boot an ELF/vxWorks image from the memory.
396 bool "Flattened Device Tree utility commands"
400 Do FDT related setup before booting into the Operating System.
402 config SUPPORT_EXTENSION_SCAN
406 bool "Extension board management command"
408 depends on SUPPORT_EXTENSION_SCAN
410 Enables the "extension" command, which allows to detect
411 extension boards connected to the system, and apply
412 corresponding Device Tree overlays.
418 Start an application at a given address.
424 Run the command in the given environment variable.
430 Print header information for application image.
435 List all images found in flash
441 Extract a part of a multi-image.
444 bool "spl export - Export boot information for Falcon boot"
447 Falcon mode allows booting directly from SPL into an Operating
448 System such as Linux, thus skipping U-Boot proper. See
449 doc/README.falcon for full information about how to use this
452 config CMD_SPL_NAND_OFS
453 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
454 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
457 This provides the offset of the command line arguments for Linux
458 when booting from NAND in Falcon mode. See doc/README.falcon
459 for full information about how to use this option (and also see
460 board/gateworks/gw_ventana/README for an example).
462 config CMD_SPL_NOR_OFS
463 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
464 depends on CMD_SPL && SPL_NOR_SUPPORT
467 This provides the offset of the command line arguments or dtb for
468 Linux when booting from NOR in Falcon mode.
470 config CMD_SPL_WRITE_SIZE
471 hex "Size of argument area"
475 This provides the size of the command-line argument area in NAND
476 flash used by Falcon-mode boot. See the documentation until CMD_SPL
479 config CMD_THOR_DOWNLOAD
480 bool "thor - TIZEN 'thor' download"
483 Implements the 'thor' download protocol. This is a way of
484 downloading a software update over USB from an attached host.
485 There is no documentation about this within the U-Boot source code
486 but you should be able to find something on the interwebs.
489 bool "zboot - x86 boot command"
491 With x86 machines it is common to boot a bzImage file which
492 contains both a kernel and a setup.bin file. The latter includes
493 configuration information from the dark ages which x86 boards still
494 need to pick things out of.
496 Consider using FIT in preference to this since it supports directly
497 booting both 32- and 64-bit kernels, as well as secure boot.
498 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
502 menu "Environment commands"
505 bool "ask for env variable"
507 Ask for environment variable
525 Edit environment variable.
530 Allow for searching environment variables
536 Save all environment variables into the compiled-in persistent
541 depends on CMD_SAVEENV
543 Erase environment variables from the compiled-in persistent
546 config CMD_ENV_EXISTS
550 Check if a variable is defined in the environment for use in
553 config CMD_ENV_CALLBACK
554 bool "env callbacks - print callbacks and their associated variables"
556 Some environment variable have callbacks defined by
557 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
558 For example changing "baudrate" adjust the serial baud rate. This
559 command lists the currently defined callbacks.
562 bool "env flags -print variables that have non-default flags"
564 Some environment variables have special flags that control their
565 behaviour. For example, serial# can only be written once and cannot
566 be deleted. This command shows the variables that have special
569 config CMD_NVEDIT_EFI
570 bool "env [set|print] -e - set/print UEFI variables"
571 depends on EFI_LOADER
574 UEFI variables are encoded as some form of U-Boot variables.
575 If enabled, we are allowed to set/print UEFI variables using
576 "env" command with "-e" option without knowing details.
578 config CMD_NVEDIT_INDIRECT
579 bool "env indirect - Sets environment value from another"
581 config CMD_NVEDIT_INFO
582 bool "env info - print or evaluate environment information"
584 Print environment information:
585 - env_valid : is environment valid
586 - env_ready : is environment imported into hash table
587 - env_use_default : is default environment used
589 This command can be optionally used for evaluation in scripts:
590 [-d] : evaluate whether default environment is used
591 [-p] : evaluate whether environment can be persisted
593 The result of multiple evaluations will be combined with AND.
595 config CMD_NVEDIT_LOAD
598 Load all environment variables from the compiled-in persistent
601 config CMD_NVEDIT_SELECT
604 Select the compiled-in persistent storage of environment variables.
608 menu "Memory commands"
613 Compute binary operations (xor, or, and) of byte arrays of arbitrary
614 size from memory and store the result in memory or the environment.
618 default y if BLOBLIST
620 Show information about the bloblist, a collection of binary blobs
621 held in memory that persist between SPL and U-Boot. In the case of
622 x86 devices the bloblist can be used to hold ACPI tables so that they
623 remain available in memory.
636 Add -v option to verify data against a crc32 checksum.
639 bool "eeprom - EEPROM subsystem"
641 (deprecated, needs conversion to driver model)
642 Provides commands to read and write EEPROM (Electrically Erasable
643 Programmable Read Only Memory) chips that are connected over an
646 config CMD_EEPROM_LAYOUT
647 bool "Enable layout-aware eeprom commands"
648 depends on CMD_EEPROM
650 (deprecated, needs conversion to driver model)
651 When enabled, additional eeprom sub-commands become available.
653 eeprom print - prints the contents of the eeprom in a human-readable
654 way (eeprom layout fields, and data formatted to be fit for human
657 eeprom update - allows user to update eeprom fields by specifying
658 the field name, and providing the new data in a human readable format
659 (same format as displayed by the eeprom print command).
661 Both commands can either auto detect the layout, or be told which
665 __weak int parse_layout_version(char *str)
666 - override to provide your own layout name parsing
667 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
669 - override to setup the layout metadata based on the version
670 __weak int eeprom_layout_detect(unsigned char *data)
671 - override to provide your own algorithm for detecting layout
674 - contains various printing and updating functions for common
675 types of eeprom fields. Can be used for defining
678 config EEPROM_LAYOUT_HELP_STRING
679 string "Tells user what layout names are supported"
680 depends on CMD_EEPROM_LAYOUT
681 default "<not defined>"
683 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
686 config SYS_I2C_EEPROM_BUS
687 int "I2C bus of the EEPROM device."
688 depends on CMD_EEPROM
691 config SYS_I2C_EEPROM_ADDR_LEN
692 int "Length in bytes of the EEPROM memory array address"
693 depends on CMD_EEPROM || ID_EEPROM
697 Note: This is NOT the chip address length!
699 config SYS_EEPROM_SIZE
700 depends on CMD_EEPROM
701 int "Size in bytes of the EEPROM device"
704 config SYS_EEPROM_PAGE_WRITE_BITS
705 int "Number of bits used to address bytes in a single page"
706 depends on CMD_EEPROM
709 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
710 A 64 byte page, for example would require six bits.
712 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
713 int "Number of milliseconds to delay between page writes"
714 depends on CMD_EEPROM || CMD_I2C
720 Infinite write loop on address range
726 Compute MD5 checksum.
730 depends on CMD_MD5SUM
732 Add -v option to verify data against an MD5 checksum.
737 Display memory information.
740 bool "md, mm, nm, mw, cp, cmp, base, loop"
745 mm - memory modify (auto-incrementing address)
746 nm - memory modify (constant address)
747 mw - memory write (fill)
750 base - print or set address offset
751 loop - initialize loop on address range
753 config CMD_MEM_SEARCH
754 bool "ms - Memory search"
756 Memory-search command
758 This allows searching through a region of memory looking for hex
759 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
760 support it). It is also possible to search for a string. The
761 command accepts a memory range and a list of values to search for.
762 The values need to appear in memory in the same order they are given
763 in the command. At most 10 matches can be returned at a time, but
764 pressing return will show the next 10 matches. Environment variables
765 are set for use with scripting (memmatches, memaddr, mempos).
768 bool "Enable cyclic md/mw commands"
769 depends on CMD_MEMORY
771 Add the "mdc" and "mwc" memory commands. These are cyclic
776 This command will print 4 bytes (10,11,12,13) each 500 ms.
778 => mwc.l 100 12345678 10
779 This command will write 12345678 to address 100 all 10 ms.
784 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
786 random - fill memory with random data
791 Simple RAM read/write test.
795 config SYS_ALT_MEMTEST
796 bool "Alternative test"
798 Use a more complete alternative memory test.
802 config SYS_ALT_MEMTEST_BITFLIP
806 The alternative memory test includes bitflip test since 2020.07.
807 The bitflip test significantly increases the overall test time.
808 Bitflip test can optionally be disabled here.
812 config SYS_MEMTEST_START
813 hex "default start address for mtest"
816 This is the default start address for mtest for simple read/write
817 test. If no arguments are given to mtest, default address is used
820 config SYS_MEMTEST_END
821 hex "default end address for mtest"
824 This is the default end address for mtest for simple read/write
825 test. If no arguments are given to mtest, default address is used
834 Compute SHA1 checksum.
836 config SHA1SUM_VERIFY
838 depends on CMD_SHA1SUM
840 Add -v option to verify data against a SHA1 checksum.
843 bool "strings - display strings in memory"
845 This works similarly to the Unix 'strings' command except that it
846 works with a memory range. String of printable characters found
847 within the range are displayed. The minimum number of characters
848 for a sequence to be considered a string can be provided.
852 menu "Compression commands"
856 default y if CMD_BOOTI
859 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
864 default y if CMD_BOOTI
867 Support decompressing an LZ4 image from memory region.
871 default y if CMD_BOOTI
874 Uncompress a zip-compressed memory region.
878 select GZIP_COMPRESSED
880 Compress a memory region with zlib deflate method.
884 menu "Device access commands"
887 #depends on FLASH_CFI_DRIVER
890 ARM Ltd reference designs flash partition access
893 bool "adc - Access Analog to Digital Converters info and data"
895 depends on DM_REGULATOR
897 Shows ADC device info and permit printing one-shot analog converted
898 data from a named Analog to Digital Converter.
903 depends on PARTITIONS
905 Read/modify/write the fields of Bootloader Control Block, usually
906 stored on the flash "misc" partition with its structure defined in:
907 https://android.googlesource.com/platform/bootable/recovery/+/master/
908 bootloader_message/include/bootloader_message/bootloader_message.h
910 Some real-life use-cases include (but are not limited to):
911 - Determine the "boot reason" (and act accordingly):
912 https://source.android.com/devices/bootloader/boot-reason
913 - Get/pass a list of commands from/to recovery:
914 https://android.googlesource.com/platform/bootable/recovery
915 - Inspect/dump the contents of the BCB fields
918 bool "bind/unbind - Bind or unbind a device to/from a driver"
921 Bind or unbind a device to/from a driver from the command line.
922 This is useful in situations where a device may be handled by several
923 drivers. For example, this can be used to bind a UDC to the usb ether
924 gadget driver from the command line.
927 bool "clk - Show clock frequencies"
930 Shows clock frequences by calling a sock_clk_dump() hook function.
931 This is depreated in favour of using the CLK uclass and accessing
932 clock values from associated drivers. However currently no command
936 bool "demo - Demonstration commands for driver model"
939 Provides a 'demo' command which can be used to play around with
940 driver model. To use this properly you will need to enable one or
941 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
942 Otherwise you will always get an empty list of devices. The demo
943 devices are defined in the sandbox device tree, so the easiest
944 option is to use sandbox and pass the -d point to sandbox's
951 Enables the command "dfu" which is used to have U-Boot create a DFU
952 class device via USB. This command requires that the "dfu_alt_info"
953 environment variable be set and define the alt settings to expose to
957 bool "dm - Access to driver model information"
960 Provides access to driver model data structures and information,
961 such as a list of devices, list of uclasses and the state of each
962 device (e.g. activated). This is not required for operation, but
963 can be useful to see the state of driver model for debugging or
967 bool "fastboot - Android fastboot support"
970 This enables the command "fastboot" which enables the Android
971 fastboot mode for the platform. Fastboot is a protocol for
972 downloading images, flashing and device control used on
973 Android devices. Fastboot requires either the network stack
974 enabled or support for acting as a USB device.
976 See doc/android/fastboot.rst for more information.
979 bool "flinfo, erase, protect"
981 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
984 flinfo - print FLASH memory information
986 protect - enable or disable FLASH write protection
995 config CMD_FPGA_LOADBP
996 bool "fpga loadbp - load partial bitstream (Xilinx only)"
999 Supports loading an FPGA device from a bitstream buffer containing
1000 a partial bitstream.
1002 config CMD_FPGA_LOADFS
1003 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
1006 Supports loading an FPGA device from a FAT filesystem.
1008 config CMD_FPGA_LOADMK
1009 bool "fpga loadmk - load bitstream from image"
1012 Supports loading an FPGA device from a image generated by mkimage.
1014 config CMD_FPGA_LOADP
1015 bool "fpga loadp - load partial bitstream"
1018 Supports loading an FPGA device from a bitstream buffer containing
1019 a partial bitstream.
1021 config CMD_FPGA_LOAD_SECURE
1022 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1025 Enables the fpga loads command which is used to load secure
1026 (authenticated or encrypted or both) bitstreams on to FPGA.
1029 bool "fpgad - dump FPGA registers"
1031 (legacy, needs conversion to driver model)
1032 Provides a way to dump FPGA registers by calling the board-specific
1033 fpga_get_reg() function. This functions similarly to the 'md'
1037 bool "fuse - support for the fuse subssystem"
1039 (deprecated - needs conversion to driver model)
1040 This allows reading, sensing, programming or overriding fuses
1041 which control the behaviour of the device. The command uses the
1049 config CMD_GPIO_READ
1050 bool "gpio read - save GPIO value to variable"
1053 Enables the 'gpio read' command that saves the value
1054 of a GPIO pin to a variable.
1060 Control PWM channels, this allows invert/config/enable/disable PWM channels.
1063 bool "GPT (GUID Partition Table) command"
1064 select EFI_PARTITION
1065 select HAVE_BLOCK_DEVICE
1066 select PARTITION_UUIDS
1069 Enable the 'gpt' command to ready and write GPT style partition
1073 bool "GPT Random UUID generation"
1076 Enable the generation of partitions with random UUIDs if none
1079 config CMD_GPT_RENAME
1080 bool "GPT partition renaming commands"
1083 Enables the 'gpt' command to interchange names on two GPT
1084 partitions via the 'gpt swap' command or to rename single
1085 partitions via the 'rename' command.
1088 bool "ide - Support for IDE drivers"
1091 Provides an 'ide' command which allows accessing the IDE drive,
1092 resetting the IDE interface, printing the partition table and
1093 geting device info. It also enables the 'diskboot' command which
1094 permits booting from an IDE drive.
1097 bool "io - Support for performing I/O accesses"
1099 Provides an 'iod' command to display I/O space and an 'iow' command
1100 to write values to the I/O space. This can be useful for manually
1101 checking the state of devices during boot when debugging device
1105 bool "iotrace - Support for tracing I/O activity"
1107 Provides an 'iotrace' command which supports recording I/O reads and
1108 writes in a trace buffer in memory . It also maintains a checksum
1109 of the trace records (even if space is exhausted) so that the
1110 sequence of I/O accesses can be verified.
1112 When debugging drivers it is useful to see what I/O accesses were
1113 done and in what order.
1115 Even if the individual accesses are of little interest it can be
1116 useful to verify that the access pattern is consistent each time
1117 an operation is performed. In this case a checksum can be used to
1118 characterise the operation of a driver. The checksum can be compared
1119 across different runs of the operation to verify that the driver is
1122 In particular, when performing major refactoring of the driver, where
1123 the access pattern should not change, the checksum provides assurance
1124 that the refactoring work has not broken the driver.
1126 This works by sneaking into the io.h heder for an architecture and
1127 redirecting I/O accesses through iotrace's tracing mechanism.
1129 For now no commands are provided to examine the trace buffer. The
1130 format is fairly simple, so 'md' is a reasonable substitute.
1132 Note: The checksum feature is only useful for I/O regions where the
1133 contents do not change outside of software control. Where this is not
1134 suitable you can fall back to manually comparing the addresses. It
1135 might be useful to enhance tracing to only checksum the accesses and
1136 not the data read/written.
1146 bool "w1 - Support for Dallas 1-Wire protocol"
1148 Dallas 1-wire protocol support
1154 Load a binary file over serial line.
1160 Load an S-Record file over serial line
1164 bool "lsblk - list block drivers and devices"
1166 Print list of available block device drivers, and for each, the list
1167 of known block devices.
1170 bool "MBR (Master Boot Record) command"
1171 select DOS_PARTITION
1172 select HAVE_BLOCK_DEVICE
1174 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1175 style partition tables.
1181 Enable the command "misc" for accessing miscellaneous devices with
1182 a MISC uclass driver. The command provides listing all MISC devices
1183 as well as read and write functionalities via their drivers.
1189 MMC memory mapped support.
1193 config CMD_BKOPS_ENABLE
1194 bool "mmc bkops enable"
1197 Enable command for setting manual background operations handshake
1198 on a eMMC device. The feature is optionally available on eMMC devices
1199 conforming to standard >= 4.41.
1202 bool "Enable support for RPMB in the mmc command"
1203 depends on SUPPORT_EMMC_RPMB
1205 Enable the commands for reading, writing and programming the
1206 key for the Replay Protection Memory Block partition in eMMC.
1208 config CMD_MMC_SWRITE
1210 depends on MMC_WRITE
1213 Enable support for the "mmc swrite" command to write Android sparse
1222 Enable storage cloning over block devices, useful for
1223 initial flashing by external block device without network
1226 config CMD_OPTEE_RPMB
1227 bool "Enable read/write support on RPMB via OPTEE"
1228 depends on SUPPORT_EMMC_RPMB && OPTEE
1230 Enable the commands for reading, writing persistent named values
1231 in the Replay Protection Memory Block partition in eMMC by
1232 using Persistent Objects in OPTEE
1237 select MTD_PARTITIONS
1239 MTD commands support.
1243 depends on MULTIPLEXER
1245 List, select, and deselect mux controllers on the fly.
1249 default y if NAND_SUNXI
1250 depends on MTD_RAW_NAND
1255 config CMD_NAND_TRIMFFS
1256 bool "nand write.trimffs"
1257 default y if ARCH_SUNXI
1259 Allows one to skip empty pages when flashing something on a NAND.
1261 config CMD_NAND_LOCK_UNLOCK
1262 bool "nand lock/unlock"
1264 NAND locking support.
1266 config CMD_NAND_TORTURE
1269 NAND torture support.
1278 NVM Express device support
1281 bool "onenand - access to onenand device"
1284 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1285 various useful features. This command allows reading, writing,
1286 and erasing blocks. It allso provides a way to show and change
1287 bad blocks, and test the device.
1292 Enable the 'osd' command which allows to query information from and
1293 write text data to a on-screen display (OSD) device; a virtual device
1294 associated with a display capable of displaying a text overlay on the
1295 display it's associated with..
1299 depends on PARTITIONS
1300 select HAVE_BLOCK_DEVICE
1301 select PARTITION_UUIDS
1303 Read and display information about the partition table on
1307 bool "pci - Access PCI devices"
1309 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1310 used on some devices to allow the CPU to communicate with its
1311 peripherals. Sub-commands allow bus enumeration, displaying and
1312 changing configuration space and a few other features.
1315 bool "pinmux - show pins muxing"
1317 default y if PINCTRL
1319 Parse all available pin-controllers and show pins muxing. This
1320 is useful for debug purpoer to check the pin muxing and to know if
1321 a pin is configured as a GPIO or as an alternate function.
1326 Poweroff/Shutdown the system
1329 bool "read - Read binary data from a partition"
1331 Provides low-level access to the data in a partition.
1333 config CMD_REMOTEPROC
1335 depends on REMOTEPROC
1337 Support for Remote Processor control
1340 bool "sata - Access SATA subsystem"
1343 SATA (Serial Advanced Technology Attachment) is a serial bus
1344 standard for connecting to hard drives and other storage devices.
1345 This command provides information about attached devices and allows
1346 reading, writing and other operations.
1348 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1349 Attachment, where AT refers to an IBM AT (Advanced Technology)
1350 computer released in 1984.
1353 bool "saves - Save a file over serial in S-Record format"
1355 Provides a way to save a binary file using the Motorola S-Record
1356 format over the serial line.
1359 bool "scsi - Access to SCSI devices"
1362 This provides a 'scsi' command which provides access to SCSI (Small
1363 Computer System Interface) devices. The command provides a way to
1364 scan the bus, reset the bus, read and write data and get information
1368 bool "sdram - Print SDRAM configuration information"
1370 Provides information about attached SDRAM. This assumed that the
1371 SDRAM has an EEPROM with information that can be read using the
1372 I2C bus. This is only available on some boards.
1376 depends on DM_SPI_FLASH || SPI_FLASH
1377 default y if DM_SPI_FLASH
1382 bool "sf test - Allow testing of SPI flash"
1385 Provides a way to test that SPI flash is working correctly. The
1386 test is destructive, in that an area of SPI flash must be provided
1387 for the test to use. Performance information is also provided,
1388 measuring the performance of reading, writing and erasing in
1389 Mbps (Million Bits Per Second). This value should approximately
1390 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1391 everything is working properly.
1394 bool "sspi - Command to access spi device"
1397 SPI utility command.
1399 config DEFAULT_SPI_BUS
1400 int "default spi bus used by sspi command"
1404 config DEFAULT_SPI_MODE
1405 hex "default spi mode used by sspi command (see include/spi.h)"
1410 bool "tsi148 - Command to access tsi148 device"
1412 This provides various sub-commands to initialise and configure the
1413 Turndra tsi148 device. See the command help for full details.
1416 bool "Enable UFS - Universal Flash Subsystem commands"
1419 "This provides commands to initialise and configure universal flash
1423 bool "universe - Command to set up the Turndra Universe controller"
1425 This allows setting up the VMEbus provided by this controller.
1426 See the command help for full details.
1431 select HAVE_BLOCK_DEVICE
1437 select USB_FUNCTION_SDP
1439 Enables the command "sdp" which is used to have U-Boot emulating the
1440 Serial Download Protocol (SDP) via USB.
1444 depends on USB_FUNCTION_ROCKUSB
1446 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1447 read/write info, image to/from devices. This enable rockusb command
1448 support to communication with rockusb device. for more detail about
1449 this command, please read doc/README.rockusb.
1451 config CMD_USB_MASS_STORAGE
1452 bool "UMS usb mass storage"
1453 depends on USB_GADGET_DOWNLOAD
1454 select USB_FUNCTION_MASS_STORAGE
1455 depends on BLK && USB_GADGET
1457 Enables the command "ums" and the USB mass storage support to the
1458 export a block device: U-Boot, the USB device, acts as a simple
1459 external hard drive plugged on the host USB port.
1462 bool "Xen para-virtualized block device"
1466 Xen para-virtualized block device support
1471 depends on HAVE_BLOCK_DEVICE
1474 VirtIO block device support
1480 This provides commands to control the watchdog timer devices.
1486 Enable the command "axi" for accessing AXI (Advanced eXtensible
1487 Interface) busses, a on-chip interconnect specification for managing
1488 functional blocks in SoC designs, which is also often used in designs
1489 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1493 menu "Shell scripting commands"
1499 Echo args to console
1505 Return true/false on integer compare.
1511 Run script from memory
1517 Evaluate boolean and math expressions and store the result in an env
1519 Also supports loading the value at a memory location into a variable.
1520 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1522 config CMD_SETEXPR_FMT
1524 depends on CMD_SETEXPR
1526 Evaluate format string expression and store result in an environment
1531 menu "Android support commands"
1533 config CMD_AB_SELECT
1535 depends on ANDROID_AB
1537 On Android devices with more than one boot slot (multiple copies of
1538 the kernel and system images) this provides a command to select which
1539 slot should be used to boot from and register the boot attempt. This
1540 is used by the new A/B update model where one slot is updated in the
1541 background while running from the other slot.
1548 bool "Network commands"
1558 bootp - boot image via network using BOOTP/TFTP protocol
1562 depends on CMD_BOOTP
1564 Boot image via network using DHCP/TFTP protocol
1566 config BOOTP_MAY_FAIL
1567 bool "Allow for the BOOTP/DHCP server to not be found"
1568 depends on CMD_BOOTP
1570 If the DHCP server is not found after the configured retry count, the
1571 call will fail instead of starting over. This can be used to fail
1572 over to Link-local IP address configuration if the DHCP server is not
1575 config BOOTP_BOOTPATH
1576 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1578 depends on CMD_BOOTP
1580 Even though the config is called BOOTP_BOOTPATH, it stores the
1581 path in the variable 'rootpath'.
1583 config BOOTP_VENDOREX
1584 bool "Support vendor extensions from BOOTP/DHCP server"
1585 depends on CMD_BOOTP
1587 config BOOTP_BOOTFILESIZE
1588 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1589 depends on CMD_BOOTP
1592 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1594 depends on CMD_BOOTP
1596 The primary DNS server is stored as 'dnsip'. If two servers are
1597 returned, you must set BOOTP_DNS2 to store that second server IP
1601 bool "Store 'dnsip2' from BOOTP/DHCP server"
1602 depends on BOOTP_DNS
1604 If a DHCP client requests the DNS server IP from a DHCP server,
1605 it is possible that more than one DNS serverip is offered to the
1606 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1607 server IP will be stored in the additional environment
1608 variable "dnsip2". The first DNS serverip is always
1609 stored in the variable "dnsip", when BOOTP_DNS is defined.
1611 config BOOTP_GATEWAY
1612 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1614 depends on CMD_BOOTP
1616 config BOOTP_HOSTNAME
1617 bool "Request & store 'hostname' from BOOTP/DHCP server"
1619 depends on CMD_BOOTP
1621 The name may or may not be qualified with the local domain name.
1623 config BOOTP_PREFER_SERVERIP
1624 bool "serverip variable takes precedent over DHCP server IP."
1625 depends on CMD_BOOTP
1627 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1629 With this option enabled, the 'serverip' variable in the environment
1630 takes precedence over DHCP server IP and will only be set by the DHCP
1631 server if not already set in the environment.
1633 config BOOTP_SUBNETMASK
1634 bool "Request & store 'netmask' from BOOTP/DHCP server"
1636 depends on CMD_BOOTP
1638 config BOOTP_NISDOMAIN
1639 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1640 depends on CMD_BOOTP
1642 config BOOTP_NTPSERVER
1643 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1644 depends on CMD_BOOTP
1646 config BOOTP_TIMEOFFSET
1647 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1648 depends on CMD_BOOTP && CMD_SNTP
1653 Selecting this will allow capturing all Ethernet packets and store
1654 them in physical memory in a PCAP formated file,
1655 later to be analyzed by PCAP reader application (IE. WireShark).
1658 bool "Send PXE client arch to BOOTP/DHCP server"
1660 depends on CMD_BOOTP && CMD_PXE
1662 Supported for ARM, ARM64, and x86 for now.
1664 config BOOTP_PXE_CLIENTARCH
1666 depends on BOOTP_PXE
1667 default 0x16 if ARM64
1671 config BOOTP_VCI_STRING
1673 depends on CMD_BOOTP
1674 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1675 default "U-Boot.armv8" if ARM64
1676 default "U-Boot.arm" if ARM
1683 tftpboot - boot image via network using TFTP protocol
1687 depends on CMD_TFTPBOOT
1689 TFTP put command, for uploading files to a server
1693 depends on CMD_TFTPBOOT
1695 Act as a TFTP server and boot the first received file
1697 config NET_TFTP_VARS
1698 bool "Control TFTP timeout and count through environment"
1699 depends on CMD_TFTPBOOT
1702 If set, allows controlling the TFTP timeout through the
1703 environment variable tftptimeout, and the TFTP maximum
1704 timeout count through the variable tftptimeoutcountmax.
1705 If unset, timeout and maximum are hard-defined as 1 second
1706 and 10 timouts per TFTP transfer.
1711 Boot image via network using RARP/TFTP protocol
1717 Boot image via network using NFS protocol.
1720 int "Timeout in milliseconds for NFS mounts"
1724 Timeout in milliseconds used in NFS protocol. If you encounter
1725 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1732 If set, allows 802.3(clause 22) MII Management functions interface access
1733 The management interface specified in Clause 22 provides
1734 a simple, two signal, serial interface to connect a
1735 Station Management entity and a managed PHY for providing access
1736 to management parameters and services.
1737 The interface is referred to as the MII management interface.
1740 bool "Call mii_init() in the mii command"
1741 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1747 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1748 The MDIO interface is orthogonal to the MII interface and extends
1749 it by adding access to more registers through indirect addressing.
1754 Send ICMP ECHO_REQUEST to network host
1759 Perform CDP network configuration
1765 Synchronize RTC via network
1770 Lookup the IP of a hostname
1772 config CMD_LINK_LOCAL
1776 Acquire a network IP address using the link-local protocol
1783 Allow control of L2 Ethernet switch commands. These are supported
1784 by the vsc9953 Ethernet driver at present. Sub-commands allow
1785 operations such as enabling / disabling a port and
1786 viewing/maintaining the filtering database (FDB)
1792 Boot image via network using PXE protocol
1797 Wait for wake-on-lan Magic Packet
1801 menu "Misc commands"
1804 bool "Enable 'bmp' command"
1805 depends on LCD || DM_VIDEO || VIDEO
1807 This provides a way to obtain information about a BMP-format image
1808 and to display it. BMP (which presumably stands for BitMaP) is a
1809 file format defined by Microsoft which supports images of various
1810 depths, formats and compression methods. Headers on the file
1811 determine the formats used. This command can be used by first loading
1812 the image into RAM, then using this command to look at it or display
1815 config CMD_BOOTCOUNT
1817 depends on BOOTCOUNT_LIMIT
1819 Enable the bootcount command, which allows interrogation and
1820 reset of the bootcounter.
1823 bool "Enable board-specific commands"
1825 (deprecated: instead, please define a Kconfig option for each command)
1827 Some boards have board-specific commands which are only enabled
1828 during developemnt and need to be turned off for production. This
1829 option provides a way to control this. The commands that are enabled
1830 vary depending on the board.
1832 config CMD_BLOCK_CACHE
1833 bool "blkcache - control and stats for block cache"
1834 depends on BLOCK_CACHE
1835 default y if BLOCK_CACHE
1837 Enable the blkcache command, which can be used to control the
1838 operation of the cache functions.
1839 This is most useful when fine-tuning the operation of the cache
1840 during development, but also allows the cache to be disabled when
1841 it might hurt performance (e.g. when using the ums command).
1848 Enable the 'button' command which allows to get the status of
1849 buttons supported by the board. The buttonss can be listed with
1850 'button list' and state can be known with 'button <label>'.
1851 Any button drivers can be controlled with this command, e.g.
1855 bool "icache or dcache"
1857 Enable the "icache" and "dcache" commands
1859 config CMD_CONITRACE
1860 bool "conitrace - trace console input codes"
1862 Enable the 'conitrace' command which displays the codes received
1863 from the console input as hexadecimal numbers.
1866 bool "Enable clear screen command 'cls'"
1867 depends on DM_VIDEO || LCD || VIDEO
1870 Enable the 'cls' command which clears the screen contents
1871 on video frame buffer.
1874 bool "efidebug - display/configure UEFI environment"
1875 depends on EFI_LOADER
1876 select EFI_DEVICE_PATH_TO_TEXT
1878 Enable the 'efidebug' command which provides a subset of UEFI
1879 shell utility with simplified functionality. It will be useful
1880 particularly for managing boot parameters as well as examining
1881 various EFI status for debugging.
1883 config CMD_EXCEPTION
1884 bool "exception - raise exception"
1885 depends on ARM || RISCV || SANDBOX || X86
1887 Enable the 'exception' command which allows to raise an exception.
1894 Enable the 'led' command which allows for control of LEDs supported
1895 by the board. The LEDs can be listed with 'led list' and controlled
1896 with led on/off/togle/blink. Any LED drivers can be controlled with
1897 this command, e.g. led_gpio.
1904 Enable the 'date' command for getting/setting the time/date in RTC
1911 Enable the 'rtc' command for low-level access to RTC devices.
1916 Run commands and summarize execution time.
1919 bool "gettime - read elapsed time"
1921 Enable the 'gettime' command which reads the elapsed time since
1922 U-Boot started running. This shows the time in seconds and
1923 milliseconds. See also the 'bootstage' command which provides more
1924 flexibility for boot timing.
1931 Print bytes from the hardware random number generator.
1933 config CMD_KASLRSEED
1937 Set the kaslr-seed in the chosen node with entropy provided by a
1938 hardware random number generator.
1944 Delay execution for some time
1947 bool "support for multiprocessor commands"
1951 This enables commands to bringup different processors
1952 in multiprocessor cases.
1957 Access the system timer.
1963 This provides basic access to the U-Boot's sound support. The main
1964 feature is to play a beep.
1966 sound init - set up sound system
1967 sound play - play a sound
1973 Boot image via local extlinux.conf file
1979 This provides access to the QEMU firmware interface. The main
1980 feature is to allow easy loading of files passed to qemu-system
1981 via -kernel / -initrd
1986 This provides access to Linux PStore with Rammoops backend. The main
1987 feature is to allow to display or save PStore records.
1989 See doc/pstore.rst for more information.
1993 config CMD_PSTORE_MEM_ADDR
1994 hex "Memory Address"
1995 depends on CMD_PSTORE
1997 Base addr used for PStore ramoops memory, should be identical to
1998 ramoops.mem_address parameter used by kernel
2000 config CMD_PSTORE_MEM_SIZE
2002 depends on CMD_PSTORE
2005 Size of PStore ramoops memory, should be identical to ramoops.mem_size
2006 parameter used by kernel, a power of 2 and larger than the sum of the
2009 config CMD_PSTORE_RECORD_SIZE
2010 hex "Dump record size"
2011 depends on CMD_PSTORE
2014 Size of each dump done on oops/panic, should be identical to
2015 ramoops.record_size parameter used by kernel and a power of 2
2018 config CMD_PSTORE_CONSOLE_SIZE
2019 hex "Kernel console log size"
2020 depends on CMD_PSTORE
2023 Size of kernel console log, should be identical to
2024 ramoops.console_size parameter used by kernel and a power of 2
2027 config CMD_PSTORE_FTRACE_SIZE
2028 hex "FTrace log size"
2029 depends on CMD_PSTORE
2032 Size of ftrace log, should be identical to ramoops.ftrace_size
2033 parameter used by kernel and a power of 2
2035 config CMD_PSTORE_PMSG_SIZE
2036 hex "User space message log size"
2037 depends on CMD_PSTORE
2040 Size of user space message log, should be identical to
2041 ramoops.pmsg_size parameter used by kernel and a power of 2
2043 config CMD_PSTORE_ECC_SIZE
2045 depends on CMD_PSTORE
2048 if non-zero, the option enables ECC support and specifies ECC buffer
2049 size in bytes (1 is a special value, means 16 bytes ECC), should be
2050 identical to ramoops.ramoops_ecc parameter used by kernel
2054 source "cmd/mvebu/Kconfig"
2057 bool "terminal - provides a way to attach a serial terminal"
2059 Provides a 'cu'-like serial terminal command. This can be used to
2060 access other serial ports from the system console. The terminal
2061 is very simple with no special processing of characters. As with
2062 cu, you can press ~. (tilde followed by period) to exit.
2065 bool "uuid, guid - generation of unique IDs"
2068 This enables two commands:
2070 uuid - generate random Universally Unique Identifier
2071 guid - generate Globally Unique Identifier based on random UUID
2073 The two commands are very similar except for the endianness of the
2078 source "cmd/ti/Kconfig"
2080 config CMD_BOOTSTAGE
2081 bool "Enable the 'bootstage' command"
2082 depends on BOOTSTAGE
2084 Add a 'bootstage' command which supports printing a report
2085 and un/stashing of bootstage data.
2087 menu "Power commands"
2089 bool "Enable Driver Model PMIC command"
2092 This is the pmic command, based on a driver model pmic's API.
2093 Command features are unchanged:
2094 - list - list pmic devices
2095 - pmic dev <id> - show or [set] operating pmic device (NEW)
2096 - pmic dump - dump registers
2097 - pmic read address - read byte of register at address
2098 - pmic write address - write byte to register at address
2099 The only one change for this command is 'dev' subcommand.
2101 config CMD_REGULATOR
2102 bool "Enable Driver Model REGULATOR command"
2103 depends on DM_REGULATOR
2105 This command is based on driver model regulator's API.
2106 User interface features:
2107 - list - list regulator devices
2108 - regulator dev <id> - show or [set] operating regulator device
2109 - regulator info - print constraints info
2110 - regulator status - print operating status
2111 - regulator value <val] <-f> - print/[set] voltage value [uV]
2112 - regulator current <val> - print/[set] current value [uA]
2113 - regulator mode <id> - print/[set] operating mode id
2114 - regulator enable - enable the regulator output
2115 - regulator disable - disable the regulator output
2117 The '-f' (force) option can be used for set the value which exceeds
2118 the limits, which are found in device-tree and are kept in regulator's
2119 uclass plat structure.
2123 menu "Security commands"
2125 bool "Enable the 'aes' command"
2128 This provides a means to encrypt and decrypt data using the AES
2129 (Advanced Encryption Standard). This algorithm uses a symetric key
2130 and is widely used as a streaming cipher. Different key lengths are
2131 supported by the algorithm but this command only supports 128 bits
2135 bool "Enable the 'blob' command"
2136 depends on !MX6ULL && !MX6SLL && !MX6SL
2137 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2139 This is used with the Freescale secure boot mechanism.
2141 Freescale's SEC block has built-in Blob Protocol which provides
2142 a method for protecting user-defined data across system power
2143 cycles. SEC block protects data in a data structure called a Blob,
2144 which provides both confidentiality and integrity protection.
2146 Encapsulating data as a blob
2147 Each time that the Blob Protocol is used to protect data, a
2148 different randomly generated key is used to encrypt the data.
2149 This random key is itself encrypted using a key which is derived
2150 from SoC's non-volatile secret key and a 16 bit Key identifier.
2151 The resulting encrypted key along with encrypted data is called a
2152 blob. The non-volatile secure key is available for use only during
2155 During decapsulation, the reverse process is performed to get back
2159 blob enc - encapsulating data as a cryptgraphic blob
2160 blob dec - decapsulating cryptgraphic blob to get the data
2164 blob enc src dst len km
2166 Encapsulate and create blob of data $len bytes long
2167 at address $src and store the result at address $dst.
2168 $km is the 16 byte key modifier is also required for
2169 generation/use as key for cryptographic operation. Key
2170 modifier should be 16 byte long.
2172 blob dec src dst len km
2174 Decapsulate the blob of data at address $src and
2175 store result of $len byte at addr $dst.
2176 $km is the 16 byte key modifier is also required for
2177 generation/use as key for cryptographic operation. Key
2178 modifier should be 16 byte long.
2181 bool "Support 'hash' command"
2184 This provides a way to hash data in memory using various supported
2185 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2186 saved to memory or to an environment variable. It is also possible
2187 to verify a hash against data in memory.
2190 bool "Support the 'hvc' command"
2191 depends on ARM_SMCCC
2193 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2194 development and testing.
2197 bool "Support the 'smc' command"
2198 depends on ARM_SMCCC
2200 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2201 development and testing.
2207 Add -v option to verify data against a hash.
2210 bool "scp03 - SCP03 enable and rotate/provision operations"
2213 This command provides access to a Trusted Application
2214 running in a TEE to request Secure Channel Protocol 03
2215 (SCP03) enablement and/or rotation of its SCP03 keys.
2224 bool "Enable the 'tpm' command"
2225 depends on TPM_V1 || TPM_V2
2226 select CMD_TPM_V1 if TPM_V1
2227 select CMD_TPM_V2 if TPM_V2
2229 This provides a means to talk to a TPM from the command line. A wide
2230 range of commands if provided - see 'tpm help' for details. The
2231 command requires a suitable TPM on your board and the correct driver
2237 bool "Enable the 'tpm test' command"
2240 This provides a a series of tests to confirm that the TPMv1.x is
2241 working correctly. The tests cover initialisation, non-volatile RAM,
2242 extend, global lock and checking that timing is within expectations.
2243 The tests pass correctly on Infineon TPMs but may need to be adjusted
2250 menu "Firmware commands"
2252 bool "Enable crosec command"
2256 Enable command-line access to the Chrome OS EC (Embedded
2257 Controller). This provides the 'crosec' command which has
2258 a number of sub-commands for performing EC tasks such as
2259 updating its flash, accessing a small saved context area
2260 and talking to the I2C bus behind the EC (if there is one).
2263 menu "Filesystem commands"
2265 bool "Enable the 'btrsubvol' command"
2268 This enables the 'btrsubvol' command to list subvolumes
2269 of a BTRFS filesystem. There are no special commands for
2270 listing BTRFS directories or loading BTRFS files - this
2271 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2272 when BTRFS is enabled (see FS_BTRFS).
2275 bool "Enable the 'cbfs' command"
2278 Define this to enable support for reading from a Coreboot
2279 filesystem. This is a ROM-based filesystem used for accessing files
2280 on systems that use coreboot as the first boot-loader and then load
2281 U-Boot to actually boot the Operating System. Available commands are
2282 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2285 bool "Enable the 'cramfs' command"
2286 depends on FS_CRAMFS
2288 This provides commands for dealing with CRAMFS (Compressed ROM
2289 filesystem). CRAMFS is useful when space is tight since files are
2290 compressed. Two commands are provided:
2292 cramfsls - lists files in a cramfs image
2293 cramfsload - loads a file from a cramfs image
2296 bool "EROFS command support"
2299 Support for the EROFS fs
2302 bool "ext2 command support"
2305 Enables EXT2 FS command
2308 bool "ext4 command support"
2311 Enables EXT4 FS command
2313 config CMD_EXT4_WRITE
2315 bool "ext4 write command support"
2318 Enables EXT4 FS write command
2321 bool "FAT command support"
2324 Support for the FAT fs
2327 bool "SquashFS command support"
2330 Enables SquashFS filesystem commands (e.g. load, ls).
2332 config CMD_FS_GENERIC
2333 bool "filesystem commands"
2335 Enables filesystem commands (e.g. load, ls) that work for multiple
2339 bool "fsuuid command"
2341 Enables fsuuid command for filesystem UUID.
2344 bool "jffs2 command"
2347 Enables commands to support the JFFS2 (Journalling Flash File System
2348 version 2) filesystem. This enables fsload, ls and fsinfo which
2349 provide the ability to load files, list directories and obtain
2350 filesystem information.
2353 string "Default device for JFFS2"
2354 depends on CMD_JFFS2
2357 The default device to use with the jffs2 command.
2359 config JFFS2_PART_OFFSET
2360 hex "Default offset within flash to locate the JFFS2 image"
2361 depends on CMD_JFFS2
2364 The default offset within flash to locate the JFFS2 image.
2366 config JFFS2_PART_SIZE
2367 hex "Default size of JFFS2 partition"
2368 depends on CMD_JFFS2
2371 The default size of the JFFS2 partition
2374 bool "MTD partition support"
2377 MTD partitioning tool support.
2378 It is strongly encouraged to avoid using this command
2379 anymore along with 'sf', 'nand', 'onenand'. One can still
2380 declare the partitions in the mtdparts environment variable
2381 but better use the MTD stack and the 'mtd' command instead.
2383 config CMD_MTDPARTS_SPREAD
2384 bool "Padd partition size to take account of bad blocks"
2385 depends on CMD_MTDPARTS
2387 This enables the 'spread' sub-command of the mtdparts command.
2388 This command will modify the existing mtdparts variable by increasing
2389 the size of the partitions such that 1) each partition's net size is
2390 at least as large as the size specified in the mtdparts variable and
2391 2) each partition starts on a good block.
2393 config CMD_MTDPARTS_SHOW_NET_SIZES
2394 bool "Show net size (w/o bad blocks) of partitions"
2395 depends on CMD_MTDPARTS
2397 Adds two columns to the printed partition table showing the
2398 effective usable size of a partition, if bad blocks are taken
2401 config MTDIDS_DEFAULT
2402 string "Default MTD IDs"
2403 depends on MTD || SPI_FLASH
2405 Defines a default MTD IDs list for use with MTD partitions in the
2406 Linux MTD command line partitions format.
2408 config MTDPARTS_DEFAULT
2409 string "Default MTD partition scheme"
2410 depends on MTD || SPI_FLASH
2412 Defines a default MTD partitioning scheme in the Linux MTD command
2413 line partitions format
2416 bool "reiser - Access to reiserfs filesystems"
2418 This provides two commands which operate on a resierfs filesystem,
2419 commonly used some years ago:
2421 reiserls - list files
2422 reiserload - load a file
2425 bool "yaffs2 - Access of YAFFS2 filesystem"
2429 This provides commands for accessing a YAFFS2 filesystem. Yet
2430 Another Flash Filesystem 2 is a filesystem designed specifically
2431 for NAND flash. It incorporates bad-block management and ensures
2432 that device writes are sequential regardless of filesystem
2436 bool "zfs - Access of ZFS filesystem"
2438 This provides commands to accessing a ZFS filesystem, commonly used
2439 on Solaris systems. Two sub-commands are provided:
2441 zfsls - list files in a directory
2442 zfsload - load a file
2444 See doc/README.zfs for more details.
2448 menu "Debug commands"
2450 config CMD_CBSYSINFO
2453 default y if SYS_COREBOOT
2455 This provides information about the coreboot sysinfo table stored in
2456 memory by coreboot before jumping to U-Boot. It can be useful for
2457 debugging the beaaviour of coreboot or U-Boot.
2460 bool "diag - Board diagnostics"
2462 This command provides access to board diagnostic tests. These are
2463 called Power-on Self Tests (POST). The command allows listing of
2464 available tests and running either all the tests, or specific tests
2468 bool "event - Show information about events"
2469 default y if EVENT_DEBUG
2471 This enables the 'event' command which provides information about
2472 events and event-handler routines. This can help to device event
2476 bool "irq - Show information about interrupts"
2477 depends on !ARM && !MIPS && !RISCV && !SH
2479 This enables two commands:
2481 interrupts - enable or disable interrupts
2482 irqinfo - print device-specific interrupt information
2485 bool "kgdb - Allow debugging of U-Boot with gdb"
2488 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2489 over a serial link for debugging purposes. This allows
2490 single-stepping, inspecting variables, etc. This is supported only
2491 on PowerPC at present.
2494 bool "log - Generation, control and access to logging"
2498 This provides access to logging features. It allows the output of
2499 log data to be controlled to a limited extent (setting up the default
2500 maximum log level for emitting of records). It also provides access
2501 to a command used for testing the log system.
2504 bool "trace - Support tracing of function calls and timing"
2508 Enables a command to control using of function tracing within
2509 U-Boot. This allows recording of call traces including timing
2510 information. The command can write data to memory for exporting
2511 for analysis (e.g. using bootchart). See doc/README.trace for full
2515 bool "avb - Android Verified Boot 2.0 operations"
2516 depends on AVB_VERIFY
2518 Enables a "avb" command to perform verification of partitions using
2519 Android Verified Boot 2.0 functionality. It includes such subcommands:
2520 avb init - initialize avb2 subsystem
2521 avb read_rb - read rollback index
2522 avb write_rb - write rollback index
2523 avb is_unlocked - check device lock state
2524 avb get_uuid - read and print uuid of a partition
2525 avb read_part - read data from partition
2526 avb read_part_hex - read data from partition and output to stdout
2527 avb write_part - write data to partition
2528 avb verify - run full verification chain
2530 config CMD_STACKPROTECTOR_TEST
2531 bool "Test command for stack protector"
2532 depends on STACKPROTECTOR
2534 Enable stackprot_test command
2535 The stackprot_test command will force a stack overrun to test
2536 the stack smashing detection mechanisms.
2541 tristate "Enable UBI - Unsorted block images commands"
2544 UBI is a software layer above MTD layer which admits use of LVM-like
2545 logical volumes on top of MTD devices, hides some complexities of
2546 flash chips like wear and bad blocks and provides some other useful
2547 capabilities. Please, consult the MTD web site for more details
2548 (www.linux-mtd.infradead.org). Activate this option if you want
2549 to use U-Boot UBI commands.
2550 It is also strongly encouraged to also enable CONFIG_MTD to get full
2553 config CMD_UBI_RENAME
2554 bool "Enable rename"
2557 Enable a "ubi" command to rename ubi volume:
2558 ubi rename <oldname> <newname>
2561 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2563 default y if CMD_UBI
2566 UBIFS is a file system for flash devices which works on top of UBI.
2568 config MMC_SPEED_MODE_SET
2569 bool "set speed mode using mmc command"
2573 Enable setting speed mode using mmc rescan and mmc dev commands.
2574 The speed mode is provided as the last argument in these commands
2575 and is indicated using the index from enum bus_mode in
2576 include/mmc.h. A speed mode can be set only if it has already
2577 been enabled in the device tree.
projects / J-u-boot.git / blob