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
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
58 config SYS_PROMPT_HUSH_PS2
59 string "Hush shell secondary prompt"
60 depends on HUSH_PARSER
63 This defines the secondary prompt string, which is
64 printed when the command interpreter needs more input
65 to complete a command. Usually "> ".
68 bool "Command execution tracer"
72 This option enables the possiblity to print all commands before
73 executing them and after all variables are evaluated (similar
74 to Bash's xtrace/'set -x' feature).
75 To enable the tracer a variable "xtrace" needs to be defined in
90 List and dump ACPI tables. ACPI (Advanced Configuration and Power
91 Interface) is used mostly on x86 for providing information to the
92 Operating System about devices in the system. The tables are set up
93 by the firmware, typically U-Boot but possibly an earlier firmware
94 module, if U-Boot is chain-loaded from something else. ACPI tables
95 can also include code, to perform hardware-specific tasks required
96 by the Operating Systems. This allows some amount of separation
97 between the firmware and OS, and is particularly useful when you
98 want to make hardware changes without the OS needing to be adjusted.
105 List non-identity virtual-physical memory mappings for 32-bit CPUs.
118 Print ".config" contents.
120 If this option is enabled, the ".config" file contents are embedded
121 in the U-Boot image and can be printed on the console by the "config"
122 command. This provides information of which options are enabled on
129 Print console devices and information.
135 Print information about available CPUs. This normally shows the
136 number of CPUs, type (e.g. manufacturer, architecture, product or
137 internal name) and clock frequency. Other information may be
138 available depending on the CPU driver.
144 Print GPL license text
149 Provides access to the Intel Power-Management Controller (PMC) so
150 that its state can be examined. This does not currently support
151 changing the state but it is still useful for debugging and seeing
160 config CMD_TLV_EEPROM
162 depends on I2C_EEPROM
164 Display and program the system EEPROM data block in ONIE Tlvinfo
165 format. TLV stands for Type-Length-Value.
167 config SPL_CMD_TLV_EEPROM
168 bool "tlv_eeprom for SPL"
169 depends on SPL_I2C_EEPROM
170 select SPL_DRIVERS_MISC
172 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
176 depends on RISCV_SMODE && SBI_V02
178 Display information about the SBI implementation.
188 Run the command stored in the environment "bootcmd", i.e.
189 "bootd" does the same thing as "run bootcmd".
195 Boot an application image from the memory.
197 config CMD_BOOTM_PRE_LOAD
198 bool "enable pre-load on bootm"
200 depends on IMAGE_PRE_LOAD
203 Enable support of stage pre-load for the bootm command.
204 This stage allow to check or modify the image provided
205 to the bootm command.
208 bool "Support booting UEFI FIT images"
209 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
212 Support booting UEFI FIT images via the bootm command.
217 Boot the Linux zImage
221 depends on ARM64 || RISCV
224 Boot an AArch64 Linux Kernel image from memory.
227 bool "Support booting Linux OS images"
228 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
231 Support booting the Linux kernel directly via a command such as bootm
235 bool "Support booting NetBSD (non-EFI) loader images"
239 Support booting NetBSD via the bootm command.
241 config BOOTM_OPENRTOS
242 bool "Support booting OPENRTOS / FreeRTOS images"
245 Support booting OPENRTOS / FreeRTOS via the bootm command.
248 bool "Support booting Enea OSE images"
249 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
252 Support booting Enea OSE images via the bootm command.
255 bool "Support booting Plan9 OS images"
259 Support booting Plan9 images via the bootm command.
262 bool "Support booting RTEMS OS images"
266 Support booting RTEMS images via the bootm command.
269 bool "Support booting VxWorks OS images"
273 Support booting VxWorks images via the bootm command.
277 depends on EFI_LOADER
280 Boot an EFI image from memory.
282 config CMD_BOOTEFI_HELLO_COMPILE
283 bool "Compile a standard EFI hello world binary for testing"
284 depends on CMD_BOOTEFI && !CPU_V7M
287 This compiles a standard EFI hello world application with U-Boot so
288 that it can be used with the test/py testing framework. This is useful
289 for testing that EFI is working at a basic level, and for bringing
290 up EFI support on a new architecture.
292 No additional space will be required in the resulting U-Boot binary
293 when this option is enabled.
295 config CMD_BOOTEFI_HELLO
296 bool "Allow booting a standard EFI hello world for testing"
297 depends on CMD_BOOTEFI_HELLO_COMPILE
298 default y if CMD_BOOTEFI_SELFTEST
300 This adds a standard EFI hello world application to U-Boot so that
301 it can be used with the 'bootefi hello' command. This is useful
302 for testing that EFI is working at a basic level, and for bringing
303 up EFI support on a new architecture.
305 source lib/efi_selftest/Kconfig
311 Add an ANSI terminal boot menu command.
316 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
317 image into RAM, dump image structure information, etc. Those dtb/dtbo
318 files should be merged in one dtb further, which needs to be passed to
319 the kernel, as part of a boot process.
323 depends on ANDROID_BOOT_IMAGE
325 Android Boot Image manipulation commands. Allows one to extract
326 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
327 obtain corresponding meta-information from boot.img.
329 See doc/android/boot-image.rst for details.
332 bool "bootelf, bootvx"
336 Boot an ELF/vxWorks image from the memory.
339 bool "Flattened Device Tree utility commands"
343 Do FDT related setup before booting into the Operating System.
345 config SUPPORT_EXTENSION_SCAN
349 bool "Extension board management command"
351 depends on SUPPORT_EXTENSION_SCAN
353 Enables the "extension" command, which allows to detect
354 extension boards connected to the system, and apply
355 corresponding Device Tree overlays.
361 Start an application at a given address.
367 Run the command in the given environment variable.
373 Print header information for application image.
378 List all images found in flash
384 Extract a part of a multi-image.
387 bool "spl export - Export boot information for Falcon boot"
390 Falcon mode allows booting directly from SPL into an Operating
391 System such as Linux, thus skipping U-Boot proper. See
392 doc/README.falcon for full information about how to use this
395 config CMD_SPL_NAND_OFS
396 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
397 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
400 This provides the offset of the command line arguments for Linux
401 when booting from NAND in Falcon mode. See doc/README.falcon
402 for full information about how to use this option (and also see
403 board/gateworks/gw_ventana/README for an example).
405 config CMD_SPL_NOR_OFS
406 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
407 depends on CMD_SPL && SPL_NOR_SUPPORT
410 This provides the offset of the command line arguments or dtb for
411 Linux when booting from NOR in Falcon mode.
413 config CMD_SPL_WRITE_SIZE
414 hex "Size of argument area"
418 This provides the size of the command-line argument area in NAND
419 flash used by Falcon-mode boot. See the documentation until CMD_SPL
422 config CMD_THOR_DOWNLOAD
423 bool "thor - TIZEN 'thor' download"
426 Implements the 'thor' download protocol. This is a way of
427 downloading a software update over USB from an attached host.
428 There is no documentation about this within the U-Boot source code
429 but you should be able to find something on the interwebs.
432 bool "zboot - x86 boot command"
434 With x86 machines it is common to boot a bzImage file which
435 contains both a kernel and a setup.bin file. The latter includes
436 configuration information from the dark ages which x86 boards still
437 need to pick things out of.
439 Consider using FIT in preference to this since it supports directly
440 booting both 32- and 64-bit kernels, as well as secure boot.
441 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
445 menu "Environment commands"
448 bool "ask for env variable"
450 Ask for environment variable
468 Edit environment variable.
473 Allow for searching environment variables
479 Save all environment variables into the compiled-in persistent
484 depends on CMD_SAVEENV
486 Erase environment variables from the compiled-in persistent
489 config CMD_ENV_EXISTS
493 Check if a variable is defined in the environment for use in
496 config CMD_ENV_CALLBACK
497 bool "env callbacks - print callbacks and their associated variables"
499 Some environment variable have callbacks defined by
500 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
501 For example changing "baudrate" adjust the serial baud rate. This
502 command lists the currently defined callbacks.
505 bool "env flags -print variables that have non-default flags"
507 Some environment variables have special flags that control their
508 behaviour. For example, serial# can only be written once and cannot
509 be deleted. This command shows the variables that have special
512 config CMD_NVEDIT_EFI
513 bool "env [set|print] -e - set/print UEFI variables"
514 depends on EFI_LOADER
517 UEFI variables are encoded as some form of U-Boot variables.
518 If enabled, we are allowed to set/print UEFI variables using
519 "env" command with "-e" option without knowing details.
521 config CMD_NVEDIT_INFO
522 bool "env info - print or evaluate environment information"
524 Print environment information:
525 - env_valid : is environment valid
526 - env_ready : is environment imported into hash table
527 - env_use_default : is default environment used
529 This command can be optionally used for evaluation in scripts:
530 [-d] : evaluate whether default environment is used
531 [-p] : evaluate whether environment can be persisted
533 The result of multiple evaluations will be combined with AND.
535 config CMD_NVEDIT_LOAD
538 Load all environment variables from the compiled-in persistent
541 config CMD_NVEDIT_SELECT
544 Select the compiled-in persistent storage of environment variables.
548 menu "Memory commands"
553 Compute binary operations (xor, or, and) of byte arrays of arbitrary
554 size from memory and store the result in memory or the environment.
558 default y if BLOBLIST
560 Show information about the bloblist, a collection of binary blobs
561 held in memory that persist between SPL and U-Boot. In the case of
562 x86 devices the bloblist can be used to hold ACPI tables so that they
563 remain available in memory.
576 Add -v option to verify data against a crc32 checksum.
579 bool "eeprom - EEPROM subsystem"
581 (deprecated, needs conversion to driver model)
582 Provides commands to read and write EEPROM (Electrically Erasable
583 Programmable Read Only Memory) chips that are connected over an
586 config CMD_EEPROM_LAYOUT
587 bool "Enable layout-aware eeprom commands"
588 depends on CMD_EEPROM
590 (deprecated, needs conversion to driver model)
591 When enabled, additional eeprom sub-commands become available.
593 eeprom print - prints the contents of the eeprom in a human-readable
594 way (eeprom layout fields, and data formatted to be fit for human
597 eeprom update - allows user to update eeprom fields by specifying
598 the field name, and providing the new data in a human readable format
599 (same format as displayed by the eeprom print command).
601 Both commands can either auto detect the layout, or be told which
605 __weak int parse_layout_version(char *str)
606 - override to provide your own layout name parsing
607 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
609 - override to setup the layout metadata based on the version
610 __weak int eeprom_layout_detect(unsigned char *data)
611 - override to provide your own algorithm for detecting layout
614 - contains various printing and updating functions for common
615 types of eeprom fields. Can be used for defining
618 config EEPROM_LAYOUT_HELP_STRING
619 string "Tells user what layout names are supported"
620 depends on CMD_EEPROM_LAYOUT
621 default "<not defined>"
623 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
626 config SYS_I2C_EEPROM_BUS
627 int "I2C bus of the EEPROM device."
628 depends on CMD_EEPROM
631 config SYS_I2C_EEPROM_ADDR_LEN
632 int "Length in bytes of the EEPROM memory array address"
633 depends on CMD_EEPROM || ID_EEPROM
637 Note: This is NOT the chip address length!
639 config SYS_EEPROM_SIZE
640 depends on CMD_EEPROM
641 int "Size in bytes of the EEPROM device"
644 config SYS_EEPROM_PAGE_WRITE_BITS
645 int "Number of bits used to address bytes in a single page"
646 depends on CMD_EEPROM
649 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
650 A 64 byte page, for example would require six bits.
652 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
653 int "Number of milliseconds to delay between page writes"
654 depends on CMD_EEPROM || CMD_I2C
660 Infinite write loop on address range
666 Compute MD5 checksum.
670 depends on CMD_MD5SUM
672 Add -v option to verify data against an MD5 checksum.
677 Display memory information.
680 bool "md, mm, nm, mw, cp, cmp, base, loop"
685 mm - memory modify (auto-incrementing address)
686 nm - memory modify (constant address)
687 mw - memory write (fill)
690 base - print or set address offset
691 loop - initialize loop on address range
693 config CMD_MEM_SEARCH
694 bool "ms - Memory search"
696 Memory-search command
698 This allows searching through a region of memory looking for hex
699 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
700 support it). It is also possible to search for a string. The
701 command accepts a memory range and a list of values to search for.
702 The values need to appear in memory in the same order they are given
703 in the command. At most 10 matches can be returned at a time, but
704 pressing return will show the next 10 matches. Environment variables
705 are set for use with scripting (memmatches, memaddr, mempos).
708 bool "Enable cyclic md/mw commands"
709 depends on CMD_MEMORY
711 Add the "mdc" and "mwc" memory commands. These are cyclic
716 This command will print 4 bytes (10,11,12,13) each 500 ms.
718 => mwc.l 100 12345678 10
719 This command will write 12345678 to address 100 all 10 ms.
724 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
726 random - fill memory with random data
731 Simple RAM read/write test.
735 config SYS_ALT_MEMTEST
736 bool "Alternative test"
738 Use a more complete alternative memory test.
742 config SYS_ALT_MEMTEST_BITFLIP
746 The alternative memory test includes bitflip test since 2020.07.
747 The bitflip test significantly increases the overall test time.
748 Bitflip test can optionally be disabled here.
752 config SYS_MEMTEST_START
753 hex "default start address for mtest"
756 This is the default start address for mtest for simple read/write
757 test. If no arguments are given to mtest, default address is used
760 config SYS_MEMTEST_END
761 hex "default end address for mtest"
764 This is the default end address for mtest for simple read/write
765 test. If no arguments are given to mtest, default address is used
774 Compute SHA1 checksum.
776 config SHA1SUM_VERIFY
778 depends on CMD_SHA1SUM
780 Add -v option to verify data against a SHA1 checksum.
783 bool "strings - display strings in memory"
785 This works similarly to the Unix 'strings' command except that it
786 works with a memory range. String of printable characters found
787 within the range are displayed. The minimum number of characters
788 for a sequence to be considered a string can be provided.
792 menu "Compression commands"
796 default y if CMD_BOOTI
799 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
804 default y if CMD_BOOTI
807 Support decompressing an LZ4 image from memory region.
811 default y if CMD_BOOTI
814 Uncompress a zip-compressed memory region.
818 select GZIP_COMPRESSED
820 Compress a memory region with zlib deflate method.
824 menu "Device access commands"
827 #depends on FLASH_CFI_DRIVER
830 ARM Ltd reference designs flash partition access
833 bool "adc - Access Analog to Digital Converters info and data"
835 depends on DM_REGULATOR
837 Shows ADC device info and permit printing one-shot analog converted
838 data from a named Analog to Digital Converter.
843 depends on PARTITIONS
845 Read/modify/write the fields of Bootloader Control Block, usually
846 stored on the flash "misc" partition with its structure defined in:
847 https://android.googlesource.com/platform/bootable/recovery/+/master/
848 bootloader_message/include/bootloader_message/bootloader_message.h
850 Some real-life use-cases include (but are not limited to):
851 - Determine the "boot reason" (and act accordingly):
852 https://source.android.com/devices/bootloader/boot-reason
853 - Get/pass a list of commands from/to recovery:
854 https://android.googlesource.com/platform/bootable/recovery
855 - Inspect/dump the contents of the BCB fields
858 bool "bind/unbind - Bind or unbind a device to/from a driver"
861 Bind or unbind a device to/from a driver from the command line.
862 This is useful in situations where a device may be handled by several
863 drivers. For example, this can be used to bind a UDC to the usb ether
864 gadget driver from the command line.
867 bool "clk - Show clock frequencies"
870 Shows clock frequences by calling a sock_clk_dump() hook function.
871 This is depreated in favour of using the CLK uclass and accessing
872 clock values from associated drivers. However currently no command
876 bool "demo - Demonstration commands for driver model"
879 Provides a 'demo' command which can be used to play around with
880 driver model. To use this properly you will need to enable one or
881 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
882 Otherwise you will always get an empty list of devices. The demo
883 devices are defined in the sandbox device tree, so the easiest
884 option is to use sandbox and pass the -d point to sandbox's
891 Enables the command "dfu" which is used to have U-Boot create a DFU
892 class device via USB. This command requires that the "dfu_alt_info"
893 environment variable be set and define the alt settings to expose to
897 bool "dm - Access to driver model information"
900 Provides access to driver model data structures and information,
901 such as a list of devices, list of uclasses and the state of each
902 device (e.g. activated). This is not required for operation, but
903 can be useful to see the state of driver model for debugging or
907 bool "fastboot - Android fastboot support"
910 This enables the command "fastboot" which enables the Android
911 fastboot mode for the platform. Fastboot is a protocol for
912 downloading images, flashing and device control used on
913 Android devices. Fastboot requires either the network stack
914 enabled or support for acting as a USB device.
916 See doc/android/fastboot.rst for more information.
919 bool "flinfo, erase, protect"
921 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
924 flinfo - print FLASH memory information
926 protect - enable or disable FLASH write protection
935 config CMD_FPGA_LOADBP
936 bool "fpga loadbp - load partial bitstream (Xilinx only)"
939 Supports loading an FPGA device from a bitstream buffer containing
942 config CMD_FPGA_LOADFS
943 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
946 Supports loading an FPGA device from a FAT filesystem.
948 config CMD_FPGA_LOADMK
949 bool "fpga loadmk - load bitstream from image"
952 Supports loading an FPGA device from a image generated by mkimage.
954 config CMD_FPGA_LOADP
955 bool "fpga loadp - load partial bitstream"
958 Supports loading an FPGA device from a bitstream buffer containing
961 config CMD_FPGA_LOAD_SECURE
962 bool "fpga loads - loads secure bitstreams (Xilinx only)"
965 Enables the fpga loads command which is used to load secure
966 (authenticated or encrypted or both) bitstreams on to FPGA.
969 bool "fpgad - dump FPGA registers"
971 (legacy, needs conversion to driver model)
972 Provides a way to dump FPGA registers by calling the board-specific
973 fpga_get_reg() function. This functions similarly to the 'md'
977 bool "fuse - support for the fuse subssystem"
979 (deprecated - needs conversion to driver model)
980 This allows reading, sensing, programming or overriding fuses
981 which control the behaviour of the device. The command uses the
993 Control PWM channels, this allows invert/config/enable/disable PWM channels.
996 bool "GPT (GUID Partition Table) command"
998 select HAVE_BLOCK_DEVICE
999 select PARTITION_UUIDS
1002 Enable the 'gpt' command to ready and write GPT style partition
1006 bool "GPT Random UUID generation"
1009 Enable the generation of partitions with random UUIDs if none
1012 config CMD_GPT_RENAME
1013 bool "GPT partition renaming commands"
1016 Enables the 'gpt' command to interchange names on two GPT
1017 partitions via the 'gpt swap' command or to rename single
1018 partitions via the 'rename' command.
1021 bool "ide - Support for IDE drivers"
1024 Provides an 'ide' command which allows accessing the IDE drive,
1025 resetting the IDE interface, printing the partition table and
1026 geting device info. It also enables the 'diskboot' command which
1027 permits booting from an IDE drive.
1030 bool "io - Support for performing I/O accesses"
1032 Provides an 'iod' command to display I/O space and an 'iow' command
1033 to write values to the I/O space. This can be useful for manually
1034 checking the state of devices during boot when debugging device
1038 bool "iotrace - Support for tracing I/O activity"
1040 Provides an 'iotrace' command which supports recording I/O reads and
1041 writes in a trace buffer in memory . It also maintains a checksum
1042 of the trace records (even if space is exhausted) so that the
1043 sequence of I/O accesses can be verified.
1045 When debugging drivers it is useful to see what I/O accesses were
1046 done and in what order.
1048 Even if the individual accesses are of little interest it can be
1049 useful to verify that the access pattern is consistent each time
1050 an operation is performed. In this case a checksum can be used to
1051 characterise the operation of a driver. The checksum can be compared
1052 across different runs of the operation to verify that the driver is
1055 In particular, when performing major refactoring of the driver, where
1056 the access pattern should not change, the checksum provides assurance
1057 that the refactoring work has not broken the driver.
1059 This works by sneaking into the io.h heder for an architecture and
1060 redirecting I/O accesses through iotrace's tracing mechanism.
1062 For now no commands are provided to examine the trace buffer. The
1063 format is fairly simple, so 'md' is a reasonable substitute.
1065 Note: The checksum feature is only useful for I/O regions where the
1066 contents do not change outside of software control. Where this is not
1067 suitable you can fall back to manually comparing the addresses. It
1068 might be useful to enhance tracing to only checksum the accesses and
1069 not the data read/written.
1079 bool "w1 - Support for Dallas 1-Wire protocol"
1081 Dallas 1-wire protocol support
1087 Load a binary file over serial line.
1093 Load an S-Record file over serial line
1097 bool "lsblk - list block drivers and devices"
1099 Print list of available block device drivers, and for each, the list
1100 of known block devices.
1103 bool "MBR (Master Boot Record) command"
1104 select DOS_PARTITION
1105 select HAVE_BLOCK_DEVICE
1107 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1108 style partition tables.
1114 Enable the command "misc" for accessing miscellaneous devices with
1115 a MISC uclass driver. The command provides listing all MISC devices
1116 as well as read and write functionalities via their drivers.
1122 MMC memory mapped support.
1126 config CMD_BKOPS_ENABLE
1127 bool "mmc bkops enable"
1130 Enable command for setting manual background operations handshake
1131 on a eMMC device. The feature is optionally available on eMMC devices
1132 conforming to standard >= 4.41.
1135 bool "Enable support for RPMB in the mmc command"
1136 depends on SUPPORT_EMMC_RPMB
1138 Enable the commands for reading, writing and programming the
1139 key for the Replay Protection Memory Block partition in eMMC.
1141 config CMD_MMC_SWRITE
1143 depends on MMC_WRITE
1146 Enable support for the "mmc swrite" command to write Android sparse
1155 Enable storage cloning over block devices, useful for
1156 initial flashing by external block device without network
1159 config CMD_OPTEE_RPMB
1160 bool "Enable read/write support on RPMB via OPTEE"
1161 depends on SUPPORT_EMMC_RPMB && OPTEE
1163 Enable the commands for reading, writing persistent named values
1164 in the Replay Protection Memory Block partition in eMMC by
1165 using Persistent Objects in OPTEE
1170 select MTD_PARTITIONS
1172 MTD commands support.
1176 depends on MULTIPLEXER
1178 List, select, and deselect mux controllers on the fly.
1182 default y if NAND_SUNXI
1183 depends on MTD_RAW_NAND
1188 config CMD_NAND_TRIMFFS
1189 bool "nand write.trimffs"
1190 default y if ARCH_SUNXI
1192 Allows one to skip empty pages when flashing something on a NAND.
1194 config CMD_NAND_LOCK_UNLOCK
1195 bool "nand lock/unlock"
1197 NAND locking support.
1199 config CMD_NAND_TORTURE
1202 NAND torture support.
1211 NVM Express device support
1214 bool "onenand - access to onenand device"
1217 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1218 various useful features. This command allows reading, writing,
1219 and erasing blocks. It allso provides a way to show and change
1220 bad blocks, and test the device.
1225 Enable the 'osd' command which allows to query information from and
1226 write text data to a on-screen display (OSD) device; a virtual device
1227 associated with a display capable of displaying a text overlay on the
1228 display it's associated with..
1232 select HAVE_BLOCK_DEVICE
1233 select PARTITION_UUIDS
1235 Read and display information about the partition table on
1239 bool "pci - Access PCI devices"
1241 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1242 used on some devices to allow the CPU to communicate with its
1243 peripherals. Sub-commands allow bus enumeration, displaying and
1244 changing configuration space and a few other features.
1247 bool "pinmux - show pins muxing"
1249 default y if PINCTRL
1251 Parse all available pin-controllers and show pins muxing. This
1252 is useful for debug purpoer to check the pin muxing and to know if
1253 a pin is configured as a GPIO or as an alternate function.
1258 Poweroff/Shutdown the system
1261 bool "read - Read binary data from a partition"
1263 Provides low-level access to the data in a partition.
1265 config CMD_REMOTEPROC
1267 depends on REMOTEPROC
1269 Support for Remote Processor control
1272 bool "sata - Access SATA subsystem"
1275 SATA (Serial Advanced Technology Attachment) is a serial bus
1276 standard for connecting to hard drives and other storage devices.
1277 This command provides information about attached devices and allows
1278 reading, writing and other operations.
1280 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1281 Attachment, where AT refers to an IBM AT (Advanced Technology)
1282 computer released in 1984.
1285 bool "saves - Save a file over serial in S-Record format"
1287 Provides a way to save a binary file using the Motorola S-Record
1288 format over the serial line.
1291 bool "scsi - Access to SCSI devices"
1294 This provides a 'scsi' command which provides access to SCSI (Small
1295 Computer System Interface) devices. The command provides a way to
1296 scan the bus, reset the bus, read and write data and get information
1300 bool "sdram - Print SDRAM configuration information"
1302 Provides information about attached SDRAM. This assumed that the
1303 SDRAM has an EEPROM with information that can be read using the
1304 I2C bus. This is only available on some boards.
1308 depends on DM_SPI_FLASH || SPI_FLASH
1309 default y if DM_SPI_FLASH
1314 bool "sf test - Allow testing of SPI flash"
1317 Provides a way to test that SPI flash is working correctly. The
1318 test is destructive, in that an area of SPI flash must be provided
1319 for the test to use. Performance information is also provided,
1320 measuring the performance of reading, writing and erasing in
1321 Mbps (Million Bits Per Second). This value should approximately
1322 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1323 everything is working properly.
1326 bool "sspi - Command to access spi device"
1329 SPI utility command.
1331 config DEFAULT_SPI_BUS
1332 int "default spi bus used by sspi command"
1336 config DEFAULT_SPI_MODE
1337 hex "default spi mode used by sspi command (see include/spi.h)"
1342 bool "tsi148 - Command to access tsi148 device"
1344 This provides various sub-commands to initialise and configure the
1345 Turndra tsi148 device. See the command help for full details.
1348 bool "Enable UFS - Universal Flash Subsystem commands"
1351 "This provides commands to initialise and configure universal flash
1355 bool "universe - Command to set up the Turndra Universe controller"
1357 This allows setting up the VMEbus provided by this controller.
1358 See the command help for full details.
1363 select HAVE_BLOCK_DEVICE
1369 select USB_FUNCTION_SDP
1371 Enables the command "sdp" which is used to have U-Boot emulating the
1372 Serial Download Protocol (SDP) via USB.
1376 depends on USB_FUNCTION_ROCKUSB
1378 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1379 read/write info, image to/from devices. This enable rockusb command
1380 support to communication with rockusb device. for more detail about
1381 this command, please read doc/README.rockusb.
1383 config CMD_USB_MASS_STORAGE
1384 bool "UMS usb mass storage"
1385 depends on USB_GADGET_DOWNLOAD
1386 select USB_FUNCTION_MASS_STORAGE
1387 depends on BLK && USB_GADGET
1389 Enables the command "ums" and the USB mass storage support to the
1390 export a block device: U-Boot, the USB device, acts as a simple
1391 external hard drive plugged on the host USB port.
1394 bool "Xen para-virtualized block device"
1398 Xen para-virtualized block device support
1403 depends on HAVE_BLOCK_DEVICE
1406 VirtIO block device support
1412 This provides commands to control the watchdog timer devices.
1418 Enable the command "axi" for accessing AXI (Advanced eXtensible
1419 Interface) busses, a on-chip interconnect specification for managing
1420 functional blocks in SoC designs, which is also often used in designs
1421 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1425 menu "Shell scripting commands"
1431 Echo args to console
1437 Return true/false on integer compare.
1443 Run script from memory
1449 Evaluate boolean and math expressions and store the result in an env
1451 Also supports loading the value at a memory location into a variable.
1452 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1454 config CMD_SETEXPR_FMT
1456 depends on CMD_SETEXPR
1458 Evaluate format string expression and store result in an environment
1463 menu "Android support commands"
1465 config CMD_AB_SELECT
1467 depends on ANDROID_AB
1469 On Android devices with more than one boot slot (multiple copies of
1470 the kernel and system images) this provides a command to select which
1471 slot should be used to boot from and register the boot attempt. This
1472 is used by the new A/B update model where one slot is updated in the
1473 background while running from the other slot.
1480 bool "Network commands"
1490 bootp - boot image via network using BOOTP/TFTP protocol
1494 depends on CMD_BOOTP
1496 Boot image via network using DHCP/TFTP protocol
1498 config BOOTP_MAY_FAIL
1499 bool "Allow for the BOOTP/DHCP server to not be found"
1500 depends on CMD_BOOTP
1502 If the DHCP server is not found after the configured retry count, the
1503 call will fail instead of starting over. This can be used to fail
1504 over to Link-local IP address configuration if the DHCP server is not
1507 config BOOTP_BOOTPATH
1508 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1510 depends on CMD_BOOTP
1512 Even though the config is called BOOTP_BOOTPATH, it stores the
1513 path in the variable 'rootpath'.
1515 config BOOTP_VENDOREX
1516 bool "Support vendor extensions from BOOTP/DHCP server"
1517 depends on CMD_BOOTP
1519 config BOOTP_BOOTFILESIZE
1520 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1521 depends on CMD_BOOTP
1524 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1526 depends on CMD_BOOTP
1528 The primary DNS server is stored as 'dnsip'. If two servers are
1529 returned, you must set BOOTP_DNS2 to store that second server IP
1533 bool "Store 'dnsip2' from BOOTP/DHCP server"
1534 depends on BOOTP_DNS
1536 If a DHCP client requests the DNS server IP from a DHCP server,
1537 it is possible that more than one DNS serverip is offered to the
1538 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1539 server IP will be stored in the additional environment
1540 variable "dnsip2". The first DNS serverip is always
1541 stored in the variable "dnsip", when BOOTP_DNS is defined.
1543 config BOOTP_GATEWAY
1544 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1546 depends on CMD_BOOTP
1548 config BOOTP_HOSTNAME
1549 bool "Request & store 'hostname' from BOOTP/DHCP server"
1551 depends on CMD_BOOTP
1553 The name may or may not be qualified with the local domain name.
1555 config BOOTP_PREFER_SERVERIP
1556 bool "serverip variable takes precedent over DHCP server IP."
1557 depends on CMD_BOOTP
1559 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1561 With this option enabled, the 'serverip' variable in the environment
1562 takes precedence over DHCP server IP and will only be set by the DHCP
1563 server if not already set in the environment.
1565 config BOOTP_SUBNETMASK
1566 bool "Request & store 'netmask' from BOOTP/DHCP server"
1568 depends on CMD_BOOTP
1570 config BOOTP_NISDOMAIN
1571 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1572 depends on CMD_BOOTP
1574 config BOOTP_NTPSERVER
1575 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1576 depends on CMD_BOOTP
1578 config BOOTP_TIMEOFFSET
1579 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1580 depends on CMD_BOOTP && CMD_SNTP
1585 Selecting this will allow capturing all Ethernet packets and store
1586 them in physical memory in a PCAP formated file,
1587 later to be analyzed by PCAP reader application (IE. WireShark).
1590 bool "Send PXE client arch to BOOTP/DHCP server"
1592 depends on CMD_BOOTP && CMD_PXE
1594 Supported for ARM, ARM64, and x86 for now.
1596 config BOOTP_PXE_CLIENTARCH
1598 depends on BOOTP_PXE
1599 default 0x16 if ARM64
1603 config BOOTP_VCI_STRING
1605 depends on CMD_BOOTP
1606 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1607 default "U-Boot.armv8" if ARM64
1608 default "U-Boot.arm" if ARM
1615 tftpboot - boot image via network using TFTP protocol
1619 depends on CMD_TFTPBOOT
1621 TFTP put command, for uploading files to a server
1625 depends on CMD_TFTPBOOT
1627 Act as a TFTP server and boot the first received file
1629 config NET_TFTP_VARS
1630 bool "Control TFTP timeout and count through environment"
1631 depends on CMD_TFTPBOOT
1634 If set, allows controlling the TFTP timeout through the
1635 environment variable tftptimeout, and the TFTP maximum
1636 timeout count through the variable tftptimeoutcountmax.
1637 If unset, timeout and maximum are hard-defined as 1 second
1638 and 10 timouts per TFTP transfer.
1643 Boot image via network using RARP/TFTP protocol
1649 Boot image via network using NFS protocol.
1652 int "Timeout in milliseconds for NFS mounts"
1656 Timeout in milliseconds used in NFS protocol. If you encounter
1657 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1664 If set, allows 802.3(clause 22) MII Management functions interface access
1665 The management interface specified in Clause 22 provides
1666 a simple, two signal, serial interface to connect a
1667 Station Management entity and a managed PHY for providing access
1668 to management parameters and services.
1669 The interface is referred to as the MII management interface.
1672 bool "Call mii_init() in the mii command"
1673 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1679 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1680 The MDIO interface is orthogonal to the MII interface and extends
1681 it by adding access to more registers through indirect addressing.
1686 Send ICMP ECHO_REQUEST to network host
1691 Perform CDP network configuration
1697 Synchronize RTC via network
1702 Lookup the IP of a hostname
1704 config CMD_LINK_LOCAL
1708 Acquire a network IP address using the link-local protocol
1715 Allow control of L2 Ethernet switch commands. These are supported
1716 by the vsc9953 Ethernet driver at present. Sub-commands allow
1717 operations such as enabling / disabling a port and
1718 viewing/maintaining the filtering database (FDB)
1724 Boot image via network using PXE protocol
1729 Wait for wake-on-lan Magic Packet
1733 menu "Misc commands"
1736 bool "Enable 'bmp' command"
1737 depends on LCD || DM_VIDEO || VIDEO
1739 This provides a way to obtain information about a BMP-format image
1740 and to display it. BMP (which presumably stands for BitMaP) is a
1741 file format defined by Microsoft which supports images of various
1742 depths, formats and compression methods. Headers on the file
1743 determine the formats used. This command can be used by first loading
1744 the image into RAM, then using this command to look at it or display
1747 config CMD_BOOTCOUNT
1749 depends on BOOTCOUNT_LIMIT
1751 Enable the bootcount command, which allows interrogation and
1752 reset of the bootcounter.
1755 bool "Enable board-specific commands"
1757 (deprecated: instead, please define a Kconfig option for each command)
1759 Some boards have board-specific commands which are only enabled
1760 during developemnt and need to be turned off for production. This
1761 option provides a way to control this. The commands that are enabled
1762 vary depending on the board.
1764 config CMD_BLOCK_CACHE
1765 bool "blkcache - control and stats for block cache"
1766 depends on BLOCK_CACHE
1767 default y if BLOCK_CACHE
1769 Enable the blkcache command, which can be used to control the
1770 operation of the cache functions.
1771 This is most useful when fine-tuning the operation of the cache
1772 during development, but also allows the cache to be disabled when
1773 it might hurt performance (e.g. when using the ums command).
1780 Enable the 'button' command which allows to get the status of
1781 buttons supported by the board. The buttonss can be listed with
1782 'button list' and state can be known with 'button <label>'.
1783 Any button drivers can be controlled with this command, e.g.
1787 bool "icache or dcache"
1789 Enable the "icache" and "dcache" commands
1791 config CMD_CONITRACE
1792 bool "conitrace - trace console input codes"
1794 Enable the 'conitrace' command which displays the codes received
1795 from the console input as hexadecimal numbers.
1798 bool "Enable clear screen command 'cls'"
1799 depends on DM_VIDEO || LCD || VIDEO
1802 Enable the 'cls' command which clears the screen contents
1803 on video frame buffer.
1806 bool "efidebug - display/configure UEFI environment"
1807 depends on EFI_LOADER
1808 select EFI_DEVICE_PATH_TO_TEXT
1810 Enable the 'efidebug' command which provides a subset of UEFI
1811 shell utility with simplified functionality. It will be useful
1812 particularly for managing boot parameters as well as examining
1813 various EFI status for debugging.
1815 config CMD_EXCEPTION
1816 bool "exception - raise exception"
1817 depends on ARM || RISCV || SANDBOX || X86
1819 Enable the 'exception' command which allows to raise an exception.
1826 Enable the 'led' command which allows for control of LEDs supported
1827 by the board. The LEDs can be listed with 'led list' and controlled
1828 with led on/off/togle/blink. Any LED drivers can be controlled with
1829 this command, e.g. led_gpio.
1836 Enable the 'date' command for getting/setting the time/date in RTC
1843 Enable the 'rtc' command for low-level access to RTC devices.
1848 Run commands and summarize execution time.
1851 bool "gettime - read elapsed time"
1853 Enable the 'gettime' command which reads the elapsed time since
1854 U-Boot started running. This shows the time in seconds and
1855 milliseconds. See also the 'bootstage' command which provides more
1856 flexibility for boot timing.
1863 Print bytes from the hardware random number generator.
1865 config CMD_KASLRSEED
1869 Set the kaslr-seed in the chosen node with entropy provided by a
1870 hardware random number generator.
1876 Delay execution for some time
1879 bool "support for multiprocessor commands"
1883 This enables commands to bringup different processors
1884 in multiprocessor cases.
1889 Access the system timer.
1895 This provides basic access to the U-Boot's sound support. The main
1896 feature is to play a beep.
1898 sound init - set up sound system
1899 sound play - play a sound
1905 Boot image via local extlinux.conf file
1911 This provides access to the QEMU firmware interface. The main
1912 feature is to allow easy loading of files passed to qemu-system
1913 via -kernel / -initrd
1918 This provides access to Linux PStore with Rammoops backend. The main
1919 feature is to allow to display or save PStore records.
1921 See doc/pstore.rst for more information.
1925 config CMD_PSTORE_MEM_ADDR
1926 hex "Memory Address"
1927 depends on CMD_PSTORE
1929 Base addr used for PStore ramoops memory, should be identical to
1930 ramoops.mem_address parameter used by kernel
1932 config CMD_PSTORE_MEM_SIZE
1934 depends on CMD_PSTORE
1937 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1938 parameter used by kernel, a power of 2 and larger than the sum of the
1941 config CMD_PSTORE_RECORD_SIZE
1942 hex "Dump record size"
1943 depends on CMD_PSTORE
1946 Size of each dump done on oops/panic, should be identical to
1947 ramoops.record_size parameter used by kernel and a power of 2
1950 config CMD_PSTORE_CONSOLE_SIZE
1951 hex "Kernel console log size"
1952 depends on CMD_PSTORE
1955 Size of kernel console log, should be identical to
1956 ramoops.console_size parameter used by kernel and a power of 2
1959 config CMD_PSTORE_FTRACE_SIZE
1960 hex "FTrace log size"
1961 depends on CMD_PSTORE
1964 Size of ftrace log, should be identical to ramoops.ftrace_size
1965 parameter used by kernel and a power of 2
1967 config CMD_PSTORE_PMSG_SIZE
1968 hex "User space message log size"
1969 depends on CMD_PSTORE
1972 Size of user space message log, should be identical to
1973 ramoops.pmsg_size parameter used by kernel and a power of 2
1975 config CMD_PSTORE_ECC_SIZE
1977 depends on CMD_PSTORE
1980 if non-zero, the option enables ECC support and specifies ECC buffer
1981 size in bytes (1 is a special value, means 16 bytes ECC), should be
1982 identical to ramoops.ramoops_ecc parameter used by kernel
1986 source "cmd/mvebu/Kconfig"
1989 bool "terminal - provides a way to attach a serial terminal"
1991 Provides a 'cu'-like serial terminal command. This can be used to
1992 access other serial ports from the system console. The terminal
1993 is very simple with no special processing of characters. As with
1994 cu, you can press ~. (tilde followed by period) to exit.
1997 bool "uuid, guid - generation of unique IDs"
2000 This enables two commands:
2002 uuid - generate random Universally Unique Identifier
2003 guid - generate Globally Unique Identifier based on random UUID
2005 The two commands are very similar except for the endianness of the
2010 source "cmd/ti/Kconfig"
2012 config CMD_BOOTSTAGE
2013 bool "Enable the 'bootstage' command"
2014 depends on BOOTSTAGE
2016 Add a 'bootstage' command which supports printing a report
2017 and un/stashing of bootstage data.
2019 menu "Power commands"
2021 bool "Enable Driver Model PMIC command"
2024 This is the pmic command, based on a driver model pmic's API.
2025 Command features are unchanged:
2026 - list - list pmic devices
2027 - pmic dev <id> - show or [set] operating pmic device (NEW)
2028 - pmic dump - dump registers
2029 - pmic read address - read byte of register at address
2030 - pmic write address - write byte to register at address
2031 The only one change for this command is 'dev' subcommand.
2033 config CMD_REGULATOR
2034 bool "Enable Driver Model REGULATOR command"
2035 depends on DM_REGULATOR
2037 This command is based on driver model regulator's API.
2038 User interface features:
2039 - list - list regulator devices
2040 - regulator dev <id> - show or [set] operating regulator device
2041 - regulator info - print constraints info
2042 - regulator status - print operating status
2043 - regulator value <val] <-f> - print/[set] voltage value [uV]
2044 - regulator current <val> - print/[set] current value [uA]
2045 - regulator mode <id> - print/[set] operating mode id
2046 - regulator enable - enable the regulator output
2047 - regulator disable - disable the regulator output
2049 The '-f' (force) option can be used for set the value which exceeds
2050 the limits, which are found in device-tree and are kept in regulator's
2051 uclass plat structure.
2055 menu "Security commands"
2057 bool "Enable the 'aes' command"
2060 This provides a means to encrypt and decrypt data using the AES
2061 (Advanced Encryption Standard). This algorithm uses a symetric key
2062 and is widely used as a streaming cipher. Different key lengths are
2063 supported by the algorithm but this command only supports 128 bits
2067 bool "Enable the 'blob' command"
2068 depends on !MX6ULL && !MX6SLL && !MX6SL
2069 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2071 This is used with the Freescale secure boot mechanism.
2073 Freescale's SEC block has built-in Blob Protocol which provides
2074 a method for protecting user-defined data across system power
2075 cycles. SEC block protects data in a data structure called a Blob,
2076 which provides both confidentiality and integrity protection.
2078 Encapsulating data as a blob
2079 Each time that the Blob Protocol is used to protect data, a
2080 different randomly generated key is used to encrypt the data.
2081 This random key is itself encrypted using a key which is derived
2082 from SoC's non-volatile secret key and a 16 bit Key identifier.
2083 The resulting encrypted key along with encrypted data is called a
2084 blob. The non-volatile secure key is available for use only during
2087 During decapsulation, the reverse process is performed to get back
2091 blob enc - encapsulating data as a cryptgraphic blob
2092 blob dec - decapsulating cryptgraphic blob to get the data
2096 blob enc src dst len km
2098 Encapsulate and create blob of data $len bytes long
2099 at address $src and store the result at address $dst.
2100 $km is the 16 byte key modifier is also required for
2101 generation/use as key for cryptographic operation. Key
2102 modifier should be 16 byte long.
2104 blob dec src dst len km
2106 Decapsulate the blob of data at address $src and
2107 store result of $len byte at addr $dst.
2108 $km is the 16 byte key modifier is also required for
2109 generation/use as key for cryptographic operation. Key
2110 modifier should be 16 byte long.
2113 bool "Support 'hash' command"
2116 This provides a way to hash data in memory using various supported
2117 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2118 saved to memory or to an environment variable. It is also possible
2119 to verify a hash against data in memory.
2122 bool "Support the 'hvc' command"
2123 depends on ARM_SMCCC
2125 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2126 development and testing.
2129 bool "Support the 'smc' command"
2130 depends on ARM_SMCCC
2132 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2133 development and testing.
2139 Add -v option to verify data against a hash.
2142 bool "scp03 - SCP03 enable and rotate/provision operations"
2145 This command provides access to a Trusted Application
2146 running in a TEE to request Secure Channel Protocol 03
2147 (SCP03) enablement and/or rotation of its SCP03 keys.
2156 bool "Enable the 'tpm' command"
2157 depends on TPM_V1 || TPM_V2
2158 select CMD_TPM_V1 if TPM_V1
2159 select CMD_TPM_V2 if TPM_V2
2161 This provides a means to talk to a TPM from the command line. A wide
2162 range of commands if provided - see 'tpm help' for details. The
2163 command requires a suitable TPM on your board and the correct driver
2169 bool "Enable the 'tpm test' command"
2172 This provides a a series of tests to confirm that the TPMv1.x is
2173 working correctly. The tests cover initialisation, non-volatile RAM,
2174 extend, global lock and checking that timing is within expectations.
2175 The tests pass correctly on Infineon TPMs but may need to be adjusted
2182 menu "Firmware commands"
2184 bool "Enable crosec command"
2188 Enable command-line access to the Chrome OS EC (Embedded
2189 Controller). This provides the 'crosec' command which has
2190 a number of sub-commands for performing EC tasks such as
2191 updating its flash, accessing a small saved context area
2192 and talking to the I2C bus behind the EC (if there is one).
2195 menu "Filesystem commands"
2197 bool "Enable the 'btrsubvol' command"
2200 This enables the 'btrsubvol' command to list subvolumes
2201 of a BTRFS filesystem. There are no special commands for
2202 listing BTRFS directories or loading BTRFS files - this
2203 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2204 when BTRFS is enabled (see FS_BTRFS).
2207 bool "Enable the 'cbfs' command"
2210 Define this to enable support for reading from a Coreboot
2211 filesystem. This is a ROM-based filesystem used for accessing files
2212 on systems that use coreboot as the first boot-loader and then load
2213 U-Boot to actually boot the Operating System. Available commands are
2214 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2217 bool "Enable the 'cramfs' command"
2218 depends on FS_CRAMFS
2220 This provides commands for dealing with CRAMFS (Compressed ROM
2221 filesystem). CRAMFS is useful when space is tight since files are
2222 compressed. Two commands are provided:
2224 cramfsls - lists files in a cramfs image
2225 cramfsload - loads a file from a cramfs image
2228 bool "EROFS command support"
2231 Support for the EROFS fs
2234 bool "ext2 command support"
2237 Enables EXT2 FS command
2240 bool "ext4 command support"
2243 Enables EXT4 FS command
2245 config CMD_EXT4_WRITE
2247 bool "ext4 write command support"
2250 Enables EXT4 FS write command
2253 bool "FAT command support"
2256 Support for the FAT fs
2259 bool "SquashFS command support"
2262 Enables SquashFS filesystem commands (e.g. load, ls).
2264 config CMD_FS_GENERIC
2265 bool "filesystem commands"
2267 Enables filesystem commands (e.g. load, ls) that work for multiple
2271 bool "fsuuid command"
2273 Enables fsuuid command for filesystem UUID.
2276 bool "jffs2 command"
2279 Enables commands to support the JFFS2 (Journalling Flash File System
2280 version 2) filesystem. This enables fsload, ls and fsinfo which
2281 provide the ability to load files, list directories and obtain
2282 filesystem information.
2285 string "Default device for JFFS2"
2286 depends on CMD_JFFS2
2289 The default device to use with the jffs2 command.
2291 config JFFS2_PART_OFFSET
2292 hex "Default offset within flash to locate the JFFS2 image"
2293 depends on CMD_JFFS2
2296 The default offset within flash to locate the JFFS2 image.
2298 config JFFS2_PART_SIZE
2299 hex "Default size of JFFS2 partition"
2300 depends on CMD_JFFS2
2303 The default size of the JFFS2 partition
2306 bool "MTD partition support"
2309 MTD partitioning tool support.
2310 It is strongly encouraged to avoid using this command
2311 anymore along with 'sf', 'nand', 'onenand'. One can still
2312 declare the partitions in the mtdparts environment variable
2313 but better use the MTD stack and the 'mtd' command instead.
2315 config CMD_MTDPARTS_SPREAD
2316 bool "Padd partition size to take account of bad blocks"
2317 depends on CMD_MTDPARTS
2319 This enables the 'spread' sub-command of the mtdparts command.
2320 This command will modify the existing mtdparts variable by increasing
2321 the size of the partitions such that 1) each partition's net size is
2322 at least as large as the size specified in the mtdparts variable and
2323 2) each partition starts on a good block.
2325 config CMD_MTDPARTS_SHOW_NET_SIZES
2326 bool "Show net size (w/o bad blocks) of partitions"
2327 depends on CMD_MTDPARTS
2329 Adds two columns to the printed partition table showing the
2330 effective usable size of a partition, if bad blocks are taken
2333 config MTDIDS_DEFAULT
2334 string "Default MTD IDs"
2335 depends on MTD || SPI_FLASH
2337 Defines a default MTD IDs list for use with MTD partitions in the
2338 Linux MTD command line partitions format.
2340 config MTDPARTS_DEFAULT
2341 string "Default MTD partition scheme"
2342 depends on MTD || SPI_FLASH
2344 Defines a default MTD partitioning scheme in the Linux MTD command
2345 line partitions format
2348 bool "reiser - Access to reiserfs filesystems"
2350 This provides two commands which operate on a resierfs filesystem,
2351 commonly used some years ago:
2353 reiserls - list files
2354 reiserload - load a file
2357 bool "yaffs2 - Access of YAFFS2 filesystem"
2361 This provides commands for accessing a YAFFS2 filesystem. Yet
2362 Another Flash Filesystem 2 is a filesystem designed specifically
2363 for NAND flash. It incorporates bad-block management and ensures
2364 that device writes are sequential regardless of filesystem
2368 bool "zfs - Access of ZFS filesystem"
2370 This provides commands to accessing a ZFS filesystem, commonly used
2371 on Solaris systems. Two sub-commands are provided:
2373 zfsls - list files in a directory
2374 zfsload - load a file
2376 See doc/README.zfs for more details.
2380 menu "Debug commands"
2382 config CMD_CBSYSINFO
2385 default y if SYS_COREBOOT
2387 This provides information about the coreboot sysinfo table stored in
2388 memory by coreboot before jumping to U-Boot. It can be useful for
2389 debugging the beaaviour of coreboot or U-Boot.
2392 bool "diag - Board diagnostics"
2394 This command provides access to board diagnostic tests. These are
2395 called Power-on Self Tests (POST). The command allows listing of
2396 available tests and running either all the tests, or specific tests
2400 bool "event - Show information about events"
2401 default y if EVENT_DEBUG
2403 This enables the 'event' command which provides information about
2404 events and event-handler routines. This can help to device event
2408 bool "irq - Show information about interrupts"
2409 depends on !ARM && !MIPS && !RISCV && !SH
2411 This enables two commands:
2413 interrupts - enable or disable interrupts
2414 irqinfo - print device-specific interrupt information
2417 bool "kgdb - Allow debugging of U-Boot with gdb"
2420 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2421 over a serial link for debugging purposes. This allows
2422 single-stepping, inspecting variables, etc. This is supported only
2423 on PowerPC at present.
2426 bool "log - Generation, control and access to logging"
2430 This provides access to logging features. It allows the output of
2431 log data to be controlled to a limited extent (setting up the default
2432 maximum log level for emitting of records). It also provides access
2433 to a command used for testing the log system.
2436 bool "trace - Support tracing of function calls and timing"
2440 Enables a command to control using of function tracing within
2441 U-Boot. This allows recording of call traces including timing
2442 information. The command can write data to memory for exporting
2443 for analysis (e.g. using bootchart). See doc/README.trace for full
2447 bool "avb - Android Verified Boot 2.0 operations"
2448 depends on AVB_VERIFY
2450 Enables a "avb" command to perform verification of partitions using
2451 Android Verified Boot 2.0 functionality. It includes such subcommands:
2452 avb init - initialize avb2 subsystem
2453 avb read_rb - read rollback index
2454 avb write_rb - write rollback index
2455 avb is_unlocked - check device lock state
2456 avb get_uuid - read and print uuid of a partition
2457 avb read_part - read data from partition
2458 avb read_part_hex - read data from partition and output to stdout
2459 avb write_part - write data to partition
2460 avb verify - run full verification chain
2462 config CMD_STACKPROTECTOR_TEST
2463 bool "Test command for stack protector"
2464 depends on STACKPROTECTOR
2466 Enable stackprot_test command
2467 The stackprot_test command will force a stack overrun to test
2468 the stack smashing detection mechanisms.
2473 tristate "Enable UBI - Unsorted block images commands"
2476 UBI is a software layer above MTD layer which admits use of LVM-like
2477 logical volumes on top of MTD devices, hides some complexities of
2478 flash chips like wear and bad blocks and provides some other useful
2479 capabilities. Please, consult the MTD web site for more details
2480 (www.linux-mtd.infradead.org). Activate this option if you want
2481 to use U-Boot UBI commands.
2482 It is also strongly encouraged to also enable CONFIG_MTD to get full
2485 config CMD_UBI_RENAME
2486 bool "Enable rename"
2489 Enable a "ubi" command to rename ubi volume:
2490 ubi rename <oldname> <newname>
2493 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2495 default y if CMD_UBI
2498 UBIFS is a file system for flash devices which works on top of UBI.
2500 config MMC_SPEED_MODE_SET
2501 bool "set speed mode using mmc command"
2505 Enable setting speed mode using mmc rescan and mmc dev commands.
2506 The speed mode is provided as the last argument in these commands
2507 and is indicated using the index from enum bus_mode in
2508 include/mmc.h. A speed mode can be set only if it has already
2509 been enabled in the device tree.
projects / platform / kernel / u-boot.git / blob