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.
215 bool "Support booting UEFI FIT images"
216 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
219 Support booting UEFI FIT images via the bootm command.
224 Boot the Linux zImage
228 depends on ARM64 || RISCV
231 Boot an AArch64 Linux Kernel image from memory.
234 bool "Support booting Linux OS images"
235 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
238 Support booting the Linux kernel directly via a command such as bootm
242 bool "Support booting NetBSD (non-EFI) loader images"
246 Support booting NetBSD via the bootm command.
248 config BOOTM_OPENRTOS
249 bool "Support booting OPENRTOS / FreeRTOS images"
252 Support booting OPENRTOS / FreeRTOS via the bootm command.
255 bool "Support booting Enea OSE images"
256 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
259 Support booting Enea OSE images via the bootm command.
262 bool "Support booting Plan9 OS images"
266 Support booting Plan9 images via the bootm command.
269 bool "Support booting RTEMS OS images"
273 Support booting RTEMS images via the bootm command.
276 bool "Support booting VxWorks OS images"
280 Support booting VxWorks images via the bootm command.
284 depends on EFI_LOADER
287 Boot an EFI image from memory.
289 config CMD_BOOTEFI_HELLO_COMPILE
290 bool "Compile a standard EFI hello world binary for testing"
291 depends on CMD_BOOTEFI && !CPU_V7M
294 This compiles a standard EFI hello world application with U-Boot so
295 that it can be used with the test/py testing framework. This is useful
296 for testing that EFI is working at a basic level, and for bringing
297 up EFI support on a new architecture.
299 No additional space will be required in the resulting U-Boot binary
300 when this option is enabled.
302 config CMD_BOOTEFI_HELLO
303 bool "Allow booting a standard EFI hello world for testing"
304 depends on CMD_BOOTEFI_HELLO_COMPILE
305 default y if CMD_BOOTEFI_SELFTEST
307 This adds a standard EFI hello world application to U-Boot so that
308 it can be used with the 'bootefi hello' command. This is useful
309 for testing that EFI is working at a basic level, and for bringing
310 up EFI support on a new architecture.
312 source lib/efi_selftest/Kconfig
318 Add an ANSI terminal boot menu command.
323 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
324 image into RAM, dump image structure information, etc. Those dtb/dtbo
325 files should be merged in one dtb further, which needs to be passed to
326 the kernel, as part of a boot process.
330 depends on ANDROID_BOOT_IMAGE
332 Android Boot Image manipulation commands. Allows one to extract
333 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
334 obtain corresponding meta-information from boot.img.
336 See doc/android/boot-image.rst for details.
339 bool "bootelf, bootvx"
343 Boot an ELF/vxWorks image from the memory.
346 bool "Flattened Device Tree utility commands"
350 Do FDT related setup before booting into the Operating System.
352 config SUPPORT_EXTENSION_SCAN
356 bool "Extension board management command"
358 depends on SUPPORT_EXTENSION_SCAN
360 Enables the "extension" command, which allows to detect
361 extension boards connected to the system, and apply
362 corresponding Device Tree overlays.
368 Start an application at a given address.
374 Run the command in the given environment variable.
380 Print header information for application image.
385 List all images found in flash
391 Extract a part of a multi-image.
394 bool "spl export - Export boot information for Falcon boot"
397 Falcon mode allows booting directly from SPL into an Operating
398 System such as Linux, thus skipping U-Boot proper. See
399 doc/README.falcon for full information about how to use this
402 config CMD_SPL_NAND_OFS
403 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
404 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
407 This provides the offset of the command line arguments for Linux
408 when booting from NAND in Falcon mode. See doc/README.falcon
409 for full information about how to use this option (and also see
410 board/gateworks/gw_ventana/README for an example).
412 config CMD_SPL_NOR_OFS
413 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
414 depends on CMD_SPL && SPL_NOR_SUPPORT
417 This provides the offset of the command line arguments or dtb for
418 Linux when booting from NOR in Falcon mode.
420 config CMD_SPL_WRITE_SIZE
421 hex "Size of argument area"
425 This provides the size of the command-line argument area in NAND
426 flash used by Falcon-mode boot. See the documentation until CMD_SPL
429 config CMD_THOR_DOWNLOAD
430 bool "thor - TIZEN 'thor' download"
433 Implements the 'thor' download protocol. This is a way of
434 downloading a software update over USB from an attached host.
435 There is no documentation about this within the U-Boot source code
436 but you should be able to find something on the interwebs.
439 bool "zboot - x86 boot command"
441 With x86 machines it is common to boot a bzImage file which
442 contains both a kernel and a setup.bin file. The latter includes
443 configuration information from the dark ages which x86 boards still
444 need to pick things out of.
446 Consider using FIT in preference to this since it supports directly
447 booting both 32- and 64-bit kernels, as well as secure boot.
448 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
452 menu "Environment commands"
455 bool "ask for env variable"
457 Ask for environment variable
475 Edit environment variable.
480 Allow for searching environment variables
486 Save all environment variables into the compiled-in persistent
491 depends on CMD_SAVEENV
493 Erase environment variables from the compiled-in persistent
496 config CMD_ENV_EXISTS
500 Check if a variable is defined in the environment for use in
503 config CMD_ENV_CALLBACK
504 bool "env callbacks - print callbacks and their associated variables"
506 Some environment variable have callbacks defined by
507 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
508 For example changing "baudrate" adjust the serial baud rate. This
509 command lists the currently defined callbacks.
512 bool "env flags -print variables that have non-default flags"
514 Some environment variables have special flags that control their
515 behaviour. For example, serial# can only be written once and cannot
516 be deleted. This command shows the variables that have special
519 config CMD_NVEDIT_EFI
520 bool "env [set|print] -e - set/print UEFI variables"
521 depends on EFI_LOADER
524 UEFI variables are encoded as some form of U-Boot variables.
525 If enabled, we are allowed to set/print UEFI variables using
526 "env" command with "-e" option without knowing details.
528 config CMD_NVEDIT_INDIRECT
529 bool "env indirect - Sets environment value from another"
531 config CMD_NVEDIT_INFO
532 bool "env info - print or evaluate environment information"
534 Print environment information:
535 - env_valid : is environment valid
536 - env_ready : is environment imported into hash table
537 - env_use_default : is default environment used
539 This command can be optionally used for evaluation in scripts:
540 [-d] : evaluate whether default environment is used
541 [-p] : evaluate whether environment can be persisted
543 The result of multiple evaluations will be combined with AND.
545 config CMD_NVEDIT_LOAD
548 Load all environment variables from the compiled-in persistent
551 config CMD_NVEDIT_SELECT
554 Select the compiled-in persistent storage of environment variables.
558 menu "Memory commands"
563 Compute binary operations (xor, or, and) of byte arrays of arbitrary
564 size from memory and store the result in memory or the environment.
568 default y if BLOBLIST
570 Show information about the bloblist, a collection of binary blobs
571 held in memory that persist between SPL and U-Boot. In the case of
572 x86 devices the bloblist can be used to hold ACPI tables so that they
573 remain available in memory.
586 Add -v option to verify data against a crc32 checksum.
589 bool "eeprom - EEPROM subsystem"
591 (deprecated, needs conversion to driver model)
592 Provides commands to read and write EEPROM (Electrically Erasable
593 Programmable Read Only Memory) chips that are connected over an
596 config CMD_EEPROM_LAYOUT
597 bool "Enable layout-aware eeprom commands"
598 depends on CMD_EEPROM
600 (deprecated, needs conversion to driver model)
601 When enabled, additional eeprom sub-commands become available.
603 eeprom print - prints the contents of the eeprom in a human-readable
604 way (eeprom layout fields, and data formatted to be fit for human
607 eeprom update - allows user to update eeprom fields by specifying
608 the field name, and providing the new data in a human readable format
609 (same format as displayed by the eeprom print command).
611 Both commands can either auto detect the layout, or be told which
615 __weak int parse_layout_version(char *str)
616 - override to provide your own layout name parsing
617 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
619 - override to setup the layout metadata based on the version
620 __weak int eeprom_layout_detect(unsigned char *data)
621 - override to provide your own algorithm for detecting layout
624 - contains various printing and updating functions for common
625 types of eeprom fields. Can be used for defining
628 config EEPROM_LAYOUT_HELP_STRING
629 string "Tells user what layout names are supported"
630 depends on CMD_EEPROM_LAYOUT
631 default "<not defined>"
633 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
636 config SYS_I2C_EEPROM_BUS
637 int "I2C bus of the EEPROM device."
638 depends on CMD_EEPROM
641 config SYS_I2C_EEPROM_ADDR_LEN
642 int "Length in bytes of the EEPROM memory array address"
643 depends on CMD_EEPROM || ID_EEPROM
647 Note: This is NOT the chip address length!
649 config SYS_EEPROM_SIZE
650 depends on CMD_EEPROM
651 int "Size in bytes of the EEPROM device"
654 config SYS_EEPROM_PAGE_WRITE_BITS
655 int "Number of bits used to address bytes in a single page"
656 depends on CMD_EEPROM
659 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
660 A 64 byte page, for example would require six bits.
662 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
663 int "Number of milliseconds to delay between page writes"
664 depends on CMD_EEPROM || CMD_I2C
670 Infinite write loop on address range
676 Compute MD5 checksum.
680 depends on CMD_MD5SUM
682 Add -v option to verify data against an MD5 checksum.
687 Display memory information.
690 bool "md, mm, nm, mw, cp, cmp, base, loop"
695 mm - memory modify (auto-incrementing address)
696 nm - memory modify (constant address)
697 mw - memory write (fill)
700 base - print or set address offset
701 loop - initialize loop on address range
703 config CMD_MEM_SEARCH
704 bool "ms - Memory search"
706 Memory-search command
708 This allows searching through a region of memory looking for hex
709 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
710 support it). It is also possible to search for a string. The
711 command accepts a memory range and a list of values to search for.
712 The values need to appear in memory in the same order they are given
713 in the command. At most 10 matches can be returned at a time, but
714 pressing return will show the next 10 matches. Environment variables
715 are set for use with scripting (memmatches, memaddr, mempos).
718 bool "Enable cyclic md/mw commands"
719 depends on CMD_MEMORY
721 Add the "mdc" and "mwc" memory commands. These are cyclic
726 This command will print 4 bytes (10,11,12,13) each 500 ms.
728 => mwc.l 100 12345678 10
729 This command will write 12345678 to address 100 all 10 ms.
734 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
736 random - fill memory with random data
741 Simple RAM read/write test.
745 config SYS_ALT_MEMTEST
746 bool "Alternative test"
748 Use a more complete alternative memory test.
752 config SYS_ALT_MEMTEST_BITFLIP
756 The alternative memory test includes bitflip test since 2020.07.
757 The bitflip test significantly increases the overall test time.
758 Bitflip test can optionally be disabled here.
762 config SYS_MEMTEST_START
763 hex "default start address for mtest"
766 This is the default start address for mtest for simple read/write
767 test. If no arguments are given to mtest, default address is used
770 config SYS_MEMTEST_END
771 hex "default end address for mtest"
774 This is the default end address for mtest for simple read/write
775 test. If no arguments are given to mtest, default address is used
784 Compute SHA1 checksum.
786 config SHA1SUM_VERIFY
788 depends on CMD_SHA1SUM
790 Add -v option to verify data against a SHA1 checksum.
793 bool "strings - display strings in memory"
795 This works similarly to the Unix 'strings' command except that it
796 works with a memory range. String of printable characters found
797 within the range are displayed. The minimum number of characters
798 for a sequence to be considered a string can be provided.
802 menu "Compression commands"
806 default y if CMD_BOOTI
809 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
814 default y if CMD_BOOTI
817 Support decompressing an LZ4 image from memory region.
821 default y if CMD_BOOTI
824 Uncompress a zip-compressed memory region.
828 select GZIP_COMPRESSED
830 Compress a memory region with zlib deflate method.
834 menu "Device access commands"
837 #depends on FLASH_CFI_DRIVER
840 ARM Ltd reference designs flash partition access
843 bool "adc - Access Analog to Digital Converters info and data"
845 depends on DM_REGULATOR
847 Shows ADC device info and permit printing one-shot analog converted
848 data from a named Analog to Digital Converter.
853 depends on PARTITIONS
855 Read/modify/write the fields of Bootloader Control Block, usually
856 stored on the flash "misc" partition with its structure defined in:
857 https://android.googlesource.com/platform/bootable/recovery/+/master/
858 bootloader_message/include/bootloader_message/bootloader_message.h
860 Some real-life use-cases include (but are not limited to):
861 - Determine the "boot reason" (and act accordingly):
862 https://source.android.com/devices/bootloader/boot-reason
863 - Get/pass a list of commands from/to recovery:
864 https://android.googlesource.com/platform/bootable/recovery
865 - Inspect/dump the contents of the BCB fields
868 bool "bind/unbind - Bind or unbind a device to/from a driver"
871 Bind or unbind a device to/from a driver from the command line.
872 This is useful in situations where a device may be handled by several
873 drivers. For example, this can be used to bind a UDC to the usb ether
874 gadget driver from the command line.
877 bool "clk - Show clock frequencies"
880 Shows clock frequences by calling a sock_clk_dump() hook function.
881 This is depreated in favour of using the CLK uclass and accessing
882 clock values from associated drivers. However currently no command
886 bool "demo - Demonstration commands for driver model"
889 Provides a 'demo' command which can be used to play around with
890 driver model. To use this properly you will need to enable one or
891 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
892 Otherwise you will always get an empty list of devices. The demo
893 devices are defined in the sandbox device tree, so the easiest
894 option is to use sandbox and pass the -d point to sandbox's
901 Enables the command "dfu" which is used to have U-Boot create a DFU
902 class device via USB. This command requires that the "dfu_alt_info"
903 environment variable be set and define the alt settings to expose to
907 bool "dm - Access to driver model information"
910 Provides access to driver model data structures and information,
911 such as a list of devices, list of uclasses and the state of each
912 device (e.g. activated). This is not required for operation, but
913 can be useful to see the state of driver model for debugging or
917 bool "fastboot - Android fastboot support"
920 This enables the command "fastboot" which enables the Android
921 fastboot mode for the platform. Fastboot is a protocol for
922 downloading images, flashing and device control used on
923 Android devices. Fastboot requires either the network stack
924 enabled or support for acting as a USB device.
926 See doc/android/fastboot.rst for more information.
929 bool "flinfo, erase, protect"
931 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
934 flinfo - print FLASH memory information
936 protect - enable or disable FLASH write protection
945 config CMD_FPGA_LOADBP
946 bool "fpga loadbp - load partial bitstream (Xilinx only)"
949 Supports loading an FPGA device from a bitstream buffer containing
952 config CMD_FPGA_LOADFS
953 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
956 Supports loading an FPGA device from a FAT filesystem.
958 config CMD_FPGA_LOADMK
959 bool "fpga loadmk - load bitstream from image"
962 Supports loading an FPGA device from a image generated by mkimage.
964 config CMD_FPGA_LOADP
965 bool "fpga loadp - load partial bitstream"
968 Supports loading an FPGA device from a bitstream buffer containing
971 config CMD_FPGA_LOAD_SECURE
972 bool "fpga loads - loads secure bitstreams (Xilinx only)"
975 Enables the fpga loads command which is used to load secure
976 (authenticated or encrypted or both) bitstreams on to FPGA.
979 bool "fpgad - dump FPGA registers"
981 (legacy, needs conversion to driver model)
982 Provides a way to dump FPGA registers by calling the board-specific
983 fpga_get_reg() function. This functions similarly to the 'md'
987 bool "fuse - support for the fuse subssystem"
989 (deprecated - needs conversion to driver model)
990 This allows reading, sensing, programming or overriding fuses
991 which control the behaviour of the device. The command uses the
1003 Control PWM channels, this allows invert/config/enable/disable PWM channels.
1006 bool "GPT (GUID Partition Table) command"
1007 select EFI_PARTITION
1008 select HAVE_BLOCK_DEVICE
1009 select PARTITION_UUIDS
1012 Enable the 'gpt' command to ready and write GPT style partition
1016 bool "GPT Random UUID generation"
1019 Enable the generation of partitions with random UUIDs if none
1022 config CMD_GPT_RENAME
1023 bool "GPT partition renaming commands"
1026 Enables the 'gpt' command to interchange names on two GPT
1027 partitions via the 'gpt swap' command or to rename single
1028 partitions via the 'rename' command.
1031 bool "ide - Support for IDE drivers"
1034 Provides an 'ide' command which allows accessing the IDE drive,
1035 resetting the IDE interface, printing the partition table and
1036 geting device info. It also enables the 'diskboot' command which
1037 permits booting from an IDE drive.
1040 bool "io - Support for performing I/O accesses"
1042 Provides an 'iod' command to display I/O space and an 'iow' command
1043 to write values to the I/O space. This can be useful for manually
1044 checking the state of devices during boot when debugging device
1048 bool "iotrace - Support for tracing I/O activity"
1050 Provides an 'iotrace' command which supports recording I/O reads and
1051 writes in a trace buffer in memory . It also maintains a checksum
1052 of the trace records (even if space is exhausted) so that the
1053 sequence of I/O accesses can be verified.
1055 When debugging drivers it is useful to see what I/O accesses were
1056 done and in what order.
1058 Even if the individual accesses are of little interest it can be
1059 useful to verify that the access pattern is consistent each time
1060 an operation is performed. In this case a checksum can be used to
1061 characterise the operation of a driver. The checksum can be compared
1062 across different runs of the operation to verify that the driver is
1065 In particular, when performing major refactoring of the driver, where
1066 the access pattern should not change, the checksum provides assurance
1067 that the refactoring work has not broken the driver.
1069 This works by sneaking into the io.h heder for an architecture and
1070 redirecting I/O accesses through iotrace's tracing mechanism.
1072 For now no commands are provided to examine the trace buffer. The
1073 format is fairly simple, so 'md' is a reasonable substitute.
1075 Note: The checksum feature is only useful for I/O regions where the
1076 contents do not change outside of software control. Where this is not
1077 suitable you can fall back to manually comparing the addresses. It
1078 might be useful to enhance tracing to only checksum the accesses and
1079 not the data read/written.
1089 bool "w1 - Support for Dallas 1-Wire protocol"
1091 Dallas 1-wire protocol support
1097 Load a binary file over serial line.
1103 Load an S-Record file over serial line
1107 bool "lsblk - list block drivers and devices"
1109 Print list of available block device drivers, and for each, the list
1110 of known block devices.
1113 bool "MBR (Master Boot Record) command"
1114 select DOS_PARTITION
1115 select HAVE_BLOCK_DEVICE
1117 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1118 style partition tables.
1124 Enable the command "misc" for accessing miscellaneous devices with
1125 a MISC uclass driver. The command provides listing all MISC devices
1126 as well as read and write functionalities via their drivers.
1132 MMC memory mapped support.
1136 config CMD_BKOPS_ENABLE
1137 bool "mmc bkops enable"
1140 Enable command for setting manual background operations handshake
1141 on a eMMC device. The feature is optionally available on eMMC devices
1142 conforming to standard >= 4.41.
1145 bool "Enable support for RPMB in the mmc command"
1146 depends on SUPPORT_EMMC_RPMB
1148 Enable the commands for reading, writing and programming the
1149 key for the Replay Protection Memory Block partition in eMMC.
1151 config CMD_MMC_SWRITE
1153 depends on MMC_WRITE
1156 Enable support for the "mmc swrite" command to write Android sparse
1165 Enable storage cloning over block devices, useful for
1166 initial flashing by external block device without network
1169 config CMD_OPTEE_RPMB
1170 bool "Enable read/write support on RPMB via OPTEE"
1171 depends on SUPPORT_EMMC_RPMB && OPTEE
1173 Enable the commands for reading, writing persistent named values
1174 in the Replay Protection Memory Block partition in eMMC by
1175 using Persistent Objects in OPTEE
1180 select MTD_PARTITIONS
1182 MTD commands support.
1186 depends on MULTIPLEXER
1188 List, select, and deselect mux controllers on the fly.
1192 default y if NAND_SUNXI
1193 depends on MTD_RAW_NAND
1198 config CMD_NAND_TRIMFFS
1199 bool "nand write.trimffs"
1200 default y if ARCH_SUNXI
1202 Allows one to skip empty pages when flashing something on a NAND.
1204 config CMD_NAND_LOCK_UNLOCK
1205 bool "nand lock/unlock"
1207 NAND locking support.
1209 config CMD_NAND_TORTURE
1212 NAND torture support.
1221 NVM Express device support
1224 bool "onenand - access to onenand device"
1227 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1228 various useful features. This command allows reading, writing,
1229 and erasing blocks. It allso provides a way to show and change
1230 bad blocks, and test the device.
1235 Enable the 'osd' command which allows to query information from and
1236 write text data to a on-screen display (OSD) device; a virtual device
1237 associated with a display capable of displaying a text overlay on the
1238 display it's associated with..
1242 select HAVE_BLOCK_DEVICE
1243 select PARTITION_UUIDS
1245 Read and display information about the partition table on
1249 bool "pci - Access PCI devices"
1251 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1252 used on some devices to allow the CPU to communicate with its
1253 peripherals. Sub-commands allow bus enumeration, displaying and
1254 changing configuration space and a few other features.
1257 bool "pinmux - show pins muxing"
1259 default y if PINCTRL
1261 Parse all available pin-controllers and show pins muxing. This
1262 is useful for debug purpoer to check the pin muxing and to know if
1263 a pin is configured as a GPIO or as an alternate function.
1268 Poweroff/Shutdown the system
1271 bool "read - Read binary data from a partition"
1273 Provides low-level access to the data in a partition.
1275 config CMD_REMOTEPROC
1277 depends on REMOTEPROC
1279 Support for Remote Processor control
1282 bool "sata - Access SATA subsystem"
1285 SATA (Serial Advanced Technology Attachment) is a serial bus
1286 standard for connecting to hard drives and other storage devices.
1287 This command provides information about attached devices and allows
1288 reading, writing and other operations.
1290 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1291 Attachment, where AT refers to an IBM AT (Advanced Technology)
1292 computer released in 1984.
1295 bool "saves - Save a file over serial in S-Record format"
1297 Provides a way to save a binary file using the Motorola S-Record
1298 format over the serial line.
1301 bool "scsi - Access to SCSI devices"
1304 This provides a 'scsi' command which provides access to SCSI (Small
1305 Computer System Interface) devices. The command provides a way to
1306 scan the bus, reset the bus, read and write data and get information
1310 bool "sdram - Print SDRAM configuration information"
1312 Provides information about attached SDRAM. This assumed that the
1313 SDRAM has an EEPROM with information that can be read using the
1314 I2C bus. This is only available on some boards.
1318 depends on DM_SPI_FLASH || SPI_FLASH
1319 default y if DM_SPI_FLASH
1324 bool "sf test - Allow testing of SPI flash"
1327 Provides a way to test that SPI flash is working correctly. The
1328 test is destructive, in that an area of SPI flash must be provided
1329 for the test to use. Performance information is also provided,
1330 measuring the performance of reading, writing and erasing in
1331 Mbps (Million Bits Per Second). This value should approximately
1332 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1333 everything is working properly.
1336 bool "sspi - Command to access spi device"
1339 SPI utility command.
1341 config DEFAULT_SPI_BUS
1342 int "default spi bus used by sspi command"
1346 config DEFAULT_SPI_MODE
1347 hex "default spi mode used by sspi command (see include/spi.h)"
1352 bool "tsi148 - Command to access tsi148 device"
1354 This provides various sub-commands to initialise and configure the
1355 Turndra tsi148 device. See the command help for full details.
1358 bool "Enable UFS - Universal Flash Subsystem commands"
1361 "This provides commands to initialise and configure universal flash
1365 bool "universe - Command to set up the Turndra Universe controller"
1367 This allows setting up the VMEbus provided by this controller.
1368 See the command help for full details.
1373 select HAVE_BLOCK_DEVICE
1379 select USB_FUNCTION_SDP
1381 Enables the command "sdp" which is used to have U-Boot emulating the
1382 Serial Download Protocol (SDP) via USB.
1386 depends on USB_FUNCTION_ROCKUSB
1388 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1389 read/write info, image to/from devices. This enable rockusb command
1390 support to communication with rockusb device. for more detail about
1391 this command, please read doc/README.rockusb.
1393 config CMD_USB_MASS_STORAGE
1394 bool "UMS usb mass storage"
1395 depends on USB_GADGET_DOWNLOAD
1396 select USB_FUNCTION_MASS_STORAGE
1397 depends on BLK && USB_GADGET
1399 Enables the command "ums" and the USB mass storage support to the
1400 export a block device: U-Boot, the USB device, acts as a simple
1401 external hard drive plugged on the host USB port.
1404 bool "Xen para-virtualized block device"
1408 Xen para-virtualized block device support
1413 depends on HAVE_BLOCK_DEVICE
1416 VirtIO block device support
1422 This provides commands to control the watchdog timer devices.
1428 Enable the command "axi" for accessing AXI (Advanced eXtensible
1429 Interface) busses, a on-chip interconnect specification for managing
1430 functional blocks in SoC designs, which is also often used in designs
1431 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1435 menu "Shell scripting commands"
1441 Echo args to console
1447 Return true/false on integer compare.
1453 Run script from memory
1459 Evaluate boolean and math expressions and store the result in an env
1461 Also supports loading the value at a memory location into a variable.
1462 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1464 config CMD_SETEXPR_FMT
1466 depends on CMD_SETEXPR
1468 Evaluate format string expression and store result in an environment
1473 menu "Android support commands"
1475 config CMD_AB_SELECT
1477 depends on ANDROID_AB
1479 On Android devices with more than one boot slot (multiple copies of
1480 the kernel and system images) this provides a command to select which
1481 slot should be used to boot from and register the boot attempt. This
1482 is used by the new A/B update model where one slot is updated in the
1483 background while running from the other slot.
1490 bool "Network commands"
1500 bootp - boot image via network using BOOTP/TFTP protocol
1504 depends on CMD_BOOTP
1506 Boot image via network using DHCP/TFTP protocol
1508 config BOOTP_MAY_FAIL
1509 bool "Allow for the BOOTP/DHCP server to not be found"
1510 depends on CMD_BOOTP
1512 If the DHCP server is not found after the configured retry count, the
1513 call will fail instead of starting over. This can be used to fail
1514 over to Link-local IP address configuration if the DHCP server is not
1517 config BOOTP_BOOTPATH
1518 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1520 depends on CMD_BOOTP
1522 Even though the config is called BOOTP_BOOTPATH, it stores the
1523 path in the variable 'rootpath'.
1525 config BOOTP_VENDOREX
1526 bool "Support vendor extensions from BOOTP/DHCP server"
1527 depends on CMD_BOOTP
1529 config BOOTP_BOOTFILESIZE
1530 bool "Request & store 'bootfilesize' from BOOTP/DHCP server"
1531 depends on CMD_BOOTP
1534 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1536 depends on CMD_BOOTP
1538 The primary DNS server is stored as 'dnsip'. If two servers are
1539 returned, you must set BOOTP_DNS2 to store that second server IP
1543 bool "Store 'dnsip2' from BOOTP/DHCP server"
1544 depends on BOOTP_DNS
1546 If a DHCP client requests the DNS server IP from a DHCP server,
1547 it is possible that more than one DNS serverip is offered to the
1548 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1549 server IP will be stored in the additional environment
1550 variable "dnsip2". The first DNS serverip is always
1551 stored in the variable "dnsip", when BOOTP_DNS is defined.
1553 config BOOTP_GATEWAY
1554 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1556 depends on CMD_BOOTP
1558 config BOOTP_HOSTNAME
1559 bool "Request & store 'hostname' from BOOTP/DHCP server"
1561 depends on CMD_BOOTP
1563 The name may or may not be qualified with the local domain name.
1565 config BOOTP_PREFER_SERVERIP
1566 bool "serverip variable takes precedent over DHCP server IP."
1567 depends on CMD_BOOTP
1569 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1571 With this option enabled, the 'serverip' variable in the environment
1572 takes precedence over DHCP server IP and will only be set by the DHCP
1573 server if not already set in the environment.
1575 config BOOTP_SUBNETMASK
1576 bool "Request & store 'netmask' from BOOTP/DHCP server"
1578 depends on CMD_BOOTP
1580 config BOOTP_NISDOMAIN
1581 bool "Request & store 'nisdomain' from BOOTP/DHCP server"
1582 depends on CMD_BOOTP
1584 config BOOTP_NTPSERVER
1585 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1586 depends on CMD_BOOTP
1588 config BOOTP_TIMEOFFSET
1589 bool "Request & store 'timeoffset' from BOOTP/DHCP server"
1590 depends on CMD_BOOTP && CMD_SNTP
1595 Selecting this will allow capturing all Ethernet packets and store
1596 them in physical memory in a PCAP formated file,
1597 later to be analyzed by PCAP reader application (IE. WireShark).
1600 bool "Send PXE client arch to BOOTP/DHCP server"
1602 depends on CMD_BOOTP && CMD_PXE
1604 Supported for ARM, ARM64, and x86 for now.
1606 config BOOTP_PXE_CLIENTARCH
1608 depends on BOOTP_PXE
1609 default 0x16 if ARM64
1613 config BOOTP_VCI_STRING
1615 depends on CMD_BOOTP
1616 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1617 default "U-Boot.armv8" if ARM64
1618 default "U-Boot.arm" if ARM
1625 tftpboot - boot image via network using TFTP protocol
1629 depends on CMD_TFTPBOOT
1631 TFTP put command, for uploading files to a server
1635 depends on CMD_TFTPBOOT
1637 Act as a TFTP server and boot the first received file
1639 config NET_TFTP_VARS
1640 bool "Control TFTP timeout and count through environment"
1641 depends on CMD_TFTPBOOT
1644 If set, allows controlling the TFTP timeout through the
1645 environment variable tftptimeout, and the TFTP maximum
1646 timeout count through the variable tftptimeoutcountmax.
1647 If unset, timeout and maximum are hard-defined as 1 second
1648 and 10 timouts per TFTP transfer.
1653 Boot image via network using RARP/TFTP protocol
1659 Boot image via network using NFS protocol.
1662 int "Timeout in milliseconds for NFS mounts"
1666 Timeout in milliseconds used in NFS protocol. If you encounter
1667 "ERROR: Cannot umount" in nfs command, try longer timeout such as
1674 If set, allows 802.3(clause 22) MII Management functions interface access
1675 The management interface specified in Clause 22 provides
1676 a simple, two signal, serial interface to connect a
1677 Station Management entity and a managed PHY for providing access
1678 to management parameters and services.
1679 The interface is referred to as the MII management interface.
1682 bool "Call mii_init() in the mii command"
1683 depends on CMD_MII && (MPC8XX_FEC || FSLDMAFE || MCFFEC)
1689 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1690 The MDIO interface is orthogonal to the MII interface and extends
1691 it by adding access to more registers through indirect addressing.
1696 Send ICMP ECHO_REQUEST to network host
1701 Perform CDP network configuration
1707 Synchronize RTC via network
1712 Lookup the IP of a hostname
1714 config CMD_LINK_LOCAL
1718 Acquire a network IP address using the link-local protocol
1725 Allow control of L2 Ethernet switch commands. These are supported
1726 by the vsc9953 Ethernet driver at present. Sub-commands allow
1727 operations such as enabling / disabling a port and
1728 viewing/maintaining the filtering database (FDB)
1734 Boot image via network using PXE protocol
1739 Wait for wake-on-lan Magic Packet
1743 menu "Misc commands"
1746 bool "Enable 'bmp' command"
1747 depends on LCD || DM_VIDEO || VIDEO
1749 This provides a way to obtain information about a BMP-format image
1750 and to display it. BMP (which presumably stands for BitMaP) is a
1751 file format defined by Microsoft which supports images of various
1752 depths, formats and compression methods. Headers on the file
1753 determine the formats used. This command can be used by first loading
1754 the image into RAM, then using this command to look at it or display
1757 config CMD_BOOTCOUNT
1759 depends on BOOTCOUNT_LIMIT
1761 Enable the bootcount command, which allows interrogation and
1762 reset of the bootcounter.
1765 bool "Enable board-specific commands"
1767 (deprecated: instead, please define a Kconfig option for each command)
1769 Some boards have board-specific commands which are only enabled
1770 during developemnt and need to be turned off for production. This
1771 option provides a way to control this. The commands that are enabled
1772 vary depending on the board.
1774 config CMD_BLOCK_CACHE
1775 bool "blkcache - control and stats for block cache"
1776 depends on BLOCK_CACHE
1777 default y if BLOCK_CACHE
1779 Enable the blkcache command, which can be used to control the
1780 operation of the cache functions.
1781 This is most useful when fine-tuning the operation of the cache
1782 during development, but also allows the cache to be disabled when
1783 it might hurt performance (e.g. when using the ums command).
1790 Enable the 'button' command which allows to get the status of
1791 buttons supported by the board. The buttonss can be listed with
1792 'button list' and state can be known with 'button <label>'.
1793 Any button drivers can be controlled with this command, e.g.
1797 bool "icache or dcache"
1799 Enable the "icache" and "dcache" commands
1801 config CMD_CONITRACE
1802 bool "conitrace - trace console input codes"
1804 Enable the 'conitrace' command which displays the codes received
1805 from the console input as hexadecimal numbers.
1808 bool "Enable clear screen command 'cls'"
1809 depends on DM_VIDEO || LCD || VIDEO
1812 Enable the 'cls' command which clears the screen contents
1813 on video frame buffer.
1816 bool "efidebug - display/configure UEFI environment"
1817 depends on EFI_LOADER
1818 select EFI_DEVICE_PATH_TO_TEXT
1820 Enable the 'efidebug' command which provides a subset of UEFI
1821 shell utility with simplified functionality. It will be useful
1822 particularly for managing boot parameters as well as examining
1823 various EFI status for debugging.
1825 config CMD_EXCEPTION
1826 bool "exception - raise exception"
1827 depends on ARM || RISCV || SANDBOX || X86
1829 Enable the 'exception' command which allows to raise an exception.
1836 Enable the 'led' command which allows for control of LEDs supported
1837 by the board. The LEDs can be listed with 'led list' and controlled
1838 with led on/off/togle/blink. Any LED drivers can be controlled with
1839 this command, e.g. led_gpio.
1846 Enable the 'date' command for getting/setting the time/date in RTC
1853 Enable the 'rtc' command for low-level access to RTC devices.
1858 Run commands and summarize execution time.
1861 bool "gettime - read elapsed time"
1863 Enable the 'gettime' command which reads the elapsed time since
1864 U-Boot started running. This shows the time in seconds and
1865 milliseconds. See also the 'bootstage' command which provides more
1866 flexibility for boot timing.
1873 Print bytes from the hardware random number generator.
1875 config CMD_KASLRSEED
1879 Set the kaslr-seed in the chosen node with entropy provided by a
1880 hardware random number generator.
1886 Delay execution for some time
1889 bool "support for multiprocessor commands"
1893 This enables commands to bringup different processors
1894 in multiprocessor cases.
1899 Access the system timer.
1905 This provides basic access to the U-Boot's sound support. The main
1906 feature is to play a beep.
1908 sound init - set up sound system
1909 sound play - play a sound
1915 Boot image via local extlinux.conf file
1921 This provides access to the QEMU firmware interface. The main
1922 feature is to allow easy loading of files passed to qemu-system
1923 via -kernel / -initrd
1928 This provides access to Linux PStore with Rammoops backend. The main
1929 feature is to allow to display or save PStore records.
1931 See doc/pstore.rst for more information.
1935 config CMD_PSTORE_MEM_ADDR
1936 hex "Memory Address"
1937 depends on CMD_PSTORE
1939 Base addr used for PStore ramoops memory, should be identical to
1940 ramoops.mem_address parameter used by kernel
1942 config CMD_PSTORE_MEM_SIZE
1944 depends on CMD_PSTORE
1947 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1948 parameter used by kernel, a power of 2 and larger than the sum of the
1951 config CMD_PSTORE_RECORD_SIZE
1952 hex "Dump record size"
1953 depends on CMD_PSTORE
1956 Size of each dump done on oops/panic, should be identical to
1957 ramoops.record_size parameter used by kernel and a power of 2
1960 config CMD_PSTORE_CONSOLE_SIZE
1961 hex "Kernel console log size"
1962 depends on CMD_PSTORE
1965 Size of kernel console log, should be identical to
1966 ramoops.console_size parameter used by kernel and a power of 2
1969 config CMD_PSTORE_FTRACE_SIZE
1970 hex "FTrace log size"
1971 depends on CMD_PSTORE
1974 Size of ftrace log, should be identical to ramoops.ftrace_size
1975 parameter used by kernel and a power of 2
1977 config CMD_PSTORE_PMSG_SIZE
1978 hex "User space message log size"
1979 depends on CMD_PSTORE
1982 Size of user space message log, should be identical to
1983 ramoops.pmsg_size parameter used by kernel and a power of 2
1985 config CMD_PSTORE_ECC_SIZE
1987 depends on CMD_PSTORE
1990 if non-zero, the option enables ECC support and specifies ECC buffer
1991 size in bytes (1 is a special value, means 16 bytes ECC), should be
1992 identical to ramoops.ramoops_ecc parameter used by kernel
1996 source "cmd/mvebu/Kconfig"
1999 bool "terminal - provides a way to attach a serial terminal"
2001 Provides a 'cu'-like serial terminal command. This can be used to
2002 access other serial ports from the system console. The terminal
2003 is very simple with no special processing of characters. As with
2004 cu, you can press ~. (tilde followed by period) to exit.
2007 bool "uuid, guid - generation of unique IDs"
2010 This enables two commands:
2012 uuid - generate random Universally Unique Identifier
2013 guid - generate Globally Unique Identifier based on random UUID
2015 The two commands are very similar except for the endianness of the
2020 source "cmd/ti/Kconfig"
2022 config CMD_BOOTSTAGE
2023 bool "Enable the 'bootstage' command"
2024 depends on BOOTSTAGE
2026 Add a 'bootstage' command which supports printing a report
2027 and un/stashing of bootstage data.
2029 menu "Power commands"
2031 bool "Enable Driver Model PMIC command"
2034 This is the pmic command, based on a driver model pmic's API.
2035 Command features are unchanged:
2036 - list - list pmic devices
2037 - pmic dev <id> - show or [set] operating pmic device (NEW)
2038 - pmic dump - dump registers
2039 - pmic read address - read byte of register at address
2040 - pmic write address - write byte to register at address
2041 The only one change for this command is 'dev' subcommand.
2043 config CMD_REGULATOR
2044 bool "Enable Driver Model REGULATOR command"
2045 depends on DM_REGULATOR
2047 This command is based on driver model regulator's API.
2048 User interface features:
2049 - list - list regulator devices
2050 - regulator dev <id> - show or [set] operating regulator device
2051 - regulator info - print constraints info
2052 - regulator status - print operating status
2053 - regulator value <val] <-f> - print/[set] voltage value [uV]
2054 - regulator current <val> - print/[set] current value [uA]
2055 - regulator mode <id> - print/[set] operating mode id
2056 - regulator enable - enable the regulator output
2057 - regulator disable - disable the regulator output
2059 The '-f' (force) option can be used for set the value which exceeds
2060 the limits, which are found in device-tree and are kept in regulator's
2061 uclass plat structure.
2065 menu "Security commands"
2067 bool "Enable the 'aes' command"
2070 This provides a means to encrypt and decrypt data using the AES
2071 (Advanced Encryption Standard). This algorithm uses a symetric key
2072 and is widely used as a streaming cipher. Different key lengths are
2073 supported by the algorithm but this command only supports 128 bits
2077 bool "Enable the 'blob' command"
2078 depends on !MX6ULL && !MX6SLL && !MX6SL
2079 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2081 This is used with the Freescale secure boot mechanism.
2083 Freescale's SEC block has built-in Blob Protocol which provides
2084 a method for protecting user-defined data across system power
2085 cycles. SEC block protects data in a data structure called a Blob,
2086 which provides both confidentiality and integrity protection.
2088 Encapsulating data as a blob
2089 Each time that the Blob Protocol is used to protect data, a
2090 different randomly generated key is used to encrypt the data.
2091 This random key is itself encrypted using a key which is derived
2092 from SoC's non-volatile secret key and a 16 bit Key identifier.
2093 The resulting encrypted key along with encrypted data is called a
2094 blob. The non-volatile secure key is available for use only during
2097 During decapsulation, the reverse process is performed to get back
2101 blob enc - encapsulating data as a cryptgraphic blob
2102 blob dec - decapsulating cryptgraphic blob to get the data
2106 blob enc src dst len km
2108 Encapsulate and create blob of data $len bytes long
2109 at address $src and store the result at address $dst.
2110 $km is the 16 byte key modifier is also required for
2111 generation/use as key for cryptographic operation. Key
2112 modifier should be 16 byte long.
2114 blob dec src dst len km
2116 Decapsulate the blob of data at address $src and
2117 store result of $len byte at addr $dst.
2118 $km is the 16 byte key modifier is also required for
2119 generation/use as key for cryptographic operation. Key
2120 modifier should be 16 byte long.
2123 bool "Support 'hash' command"
2126 This provides a way to hash data in memory using various supported
2127 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2128 saved to memory or to an environment variable. It is also possible
2129 to verify a hash against data in memory.
2132 bool "Support the 'hvc' command"
2133 depends on ARM_SMCCC
2135 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2136 development and testing.
2139 bool "Support the 'smc' command"
2140 depends on ARM_SMCCC
2142 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2143 development and testing.
2149 Add -v option to verify data against a hash.
2152 bool "scp03 - SCP03 enable and rotate/provision operations"
2155 This command provides access to a Trusted Application
2156 running in a TEE to request Secure Channel Protocol 03
2157 (SCP03) enablement and/or rotation of its SCP03 keys.
2166 bool "Enable the 'tpm' command"
2167 depends on TPM_V1 || TPM_V2
2168 select CMD_TPM_V1 if TPM_V1
2169 select CMD_TPM_V2 if TPM_V2
2171 This provides a means to talk to a TPM from the command line. A wide
2172 range of commands if provided - see 'tpm help' for details. The
2173 command requires a suitable TPM on your board and the correct driver
2179 bool "Enable the 'tpm test' command"
2182 This provides a a series of tests to confirm that the TPMv1.x is
2183 working correctly. The tests cover initialisation, non-volatile RAM,
2184 extend, global lock and checking that timing is within expectations.
2185 The tests pass correctly on Infineon TPMs but may need to be adjusted
2192 menu "Firmware commands"
2194 bool "Enable crosec command"
2198 Enable command-line access to the Chrome OS EC (Embedded
2199 Controller). This provides the 'crosec' command which has
2200 a number of sub-commands for performing EC tasks such as
2201 updating its flash, accessing a small saved context area
2202 and talking to the I2C bus behind the EC (if there is one).
2205 menu "Filesystem commands"
2207 bool "Enable the 'btrsubvol' command"
2210 This enables the 'btrsubvol' command to list subvolumes
2211 of a BTRFS filesystem. There are no special commands for
2212 listing BTRFS directories or loading BTRFS files - this
2213 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2214 when BTRFS is enabled (see FS_BTRFS).
2217 bool "Enable the 'cbfs' command"
2220 Define this to enable support for reading from a Coreboot
2221 filesystem. This is a ROM-based filesystem used for accessing files
2222 on systems that use coreboot as the first boot-loader and then load
2223 U-Boot to actually boot the Operating System. Available commands are
2224 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2227 bool "Enable the 'cramfs' command"
2228 depends on FS_CRAMFS
2230 This provides commands for dealing with CRAMFS (Compressed ROM
2231 filesystem). CRAMFS is useful when space is tight since files are
2232 compressed. Two commands are provided:
2234 cramfsls - lists files in a cramfs image
2235 cramfsload - loads a file from a cramfs image
2238 bool "EROFS command support"
2241 Support for the EROFS fs
2244 bool "ext2 command support"
2247 Enables EXT2 FS command
2250 bool "ext4 command support"
2253 Enables EXT4 FS command
2255 config CMD_EXT4_WRITE
2257 bool "ext4 write command support"
2260 Enables EXT4 FS write command
2263 bool "FAT command support"
2266 Support for the FAT fs
2269 bool "SquashFS command support"
2272 Enables SquashFS filesystem commands (e.g. load, ls).
2274 config CMD_FS_GENERIC
2275 bool "filesystem commands"
2277 Enables filesystem commands (e.g. load, ls) that work for multiple
2281 bool "fsuuid command"
2283 Enables fsuuid command for filesystem UUID.
2286 bool "jffs2 command"
2289 Enables commands to support the JFFS2 (Journalling Flash File System
2290 version 2) filesystem. This enables fsload, ls and fsinfo which
2291 provide the ability to load files, list directories and obtain
2292 filesystem information.
2295 string "Default device for JFFS2"
2296 depends on CMD_JFFS2
2299 The default device to use with the jffs2 command.
2301 config JFFS2_PART_OFFSET
2302 hex "Default offset within flash to locate the JFFS2 image"
2303 depends on CMD_JFFS2
2306 The default offset within flash to locate the JFFS2 image.
2308 config JFFS2_PART_SIZE
2309 hex "Default size of JFFS2 partition"
2310 depends on CMD_JFFS2
2313 The default size of the JFFS2 partition
2316 bool "MTD partition support"
2319 MTD partitioning tool support.
2320 It is strongly encouraged to avoid using this command
2321 anymore along with 'sf', 'nand', 'onenand'. One can still
2322 declare the partitions in the mtdparts environment variable
2323 but better use the MTD stack and the 'mtd' command instead.
2325 config CMD_MTDPARTS_SPREAD
2326 bool "Padd partition size to take account of bad blocks"
2327 depends on CMD_MTDPARTS
2329 This enables the 'spread' sub-command of the mtdparts command.
2330 This command will modify the existing mtdparts variable by increasing
2331 the size of the partitions such that 1) each partition's net size is
2332 at least as large as the size specified in the mtdparts variable and
2333 2) each partition starts on a good block.
2335 config CMD_MTDPARTS_SHOW_NET_SIZES
2336 bool "Show net size (w/o bad blocks) of partitions"
2337 depends on CMD_MTDPARTS
2339 Adds two columns to the printed partition table showing the
2340 effective usable size of a partition, if bad blocks are taken
2343 config MTDIDS_DEFAULT
2344 string "Default MTD IDs"
2345 depends on MTD || SPI_FLASH
2347 Defines a default MTD IDs list for use with MTD partitions in the
2348 Linux MTD command line partitions format.
2350 config MTDPARTS_DEFAULT
2351 string "Default MTD partition scheme"
2352 depends on MTD || SPI_FLASH
2354 Defines a default MTD partitioning scheme in the Linux MTD command
2355 line partitions format
2358 bool "reiser - Access to reiserfs filesystems"
2360 This provides two commands which operate on a resierfs filesystem,
2361 commonly used some years ago:
2363 reiserls - list files
2364 reiserload - load a file
2367 bool "yaffs2 - Access of YAFFS2 filesystem"
2371 This provides commands for accessing a YAFFS2 filesystem. Yet
2372 Another Flash Filesystem 2 is a filesystem designed specifically
2373 for NAND flash. It incorporates bad-block management and ensures
2374 that device writes are sequential regardless of filesystem
2378 bool "zfs - Access of ZFS filesystem"
2380 This provides commands to accessing a ZFS filesystem, commonly used
2381 on Solaris systems. Two sub-commands are provided:
2383 zfsls - list files in a directory
2384 zfsload - load a file
2386 See doc/README.zfs for more details.
2390 menu "Debug commands"
2392 config CMD_CBSYSINFO
2395 default y if SYS_COREBOOT
2397 This provides information about the coreboot sysinfo table stored in
2398 memory by coreboot before jumping to U-Boot. It can be useful for
2399 debugging the beaaviour of coreboot or U-Boot.
2402 bool "diag - Board diagnostics"
2404 This command provides access to board diagnostic tests. These are
2405 called Power-on Self Tests (POST). The command allows listing of
2406 available tests and running either all the tests, or specific tests
2410 bool "event - Show information about events"
2411 default y if EVENT_DEBUG
2413 This enables the 'event' command which provides information about
2414 events and event-handler routines. This can help to device event
2418 bool "irq - Show information about interrupts"
2419 depends on !ARM && !MIPS && !RISCV && !SH
2421 This enables two commands:
2423 interrupts - enable or disable interrupts
2424 irqinfo - print device-specific interrupt information
2427 bool "kgdb - Allow debugging of U-Boot with gdb"
2430 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2431 over a serial link for debugging purposes. This allows
2432 single-stepping, inspecting variables, etc. This is supported only
2433 on PowerPC at present.
2436 bool "log - Generation, control and access to logging"
2440 This provides access to logging features. It allows the output of
2441 log data to be controlled to a limited extent (setting up the default
2442 maximum log level for emitting of records). It also provides access
2443 to a command used for testing the log system.
2446 bool "trace - Support tracing of function calls and timing"
2450 Enables a command to control using of function tracing within
2451 U-Boot. This allows recording of call traces including timing
2452 information. The command can write data to memory for exporting
2453 for analysis (e.g. using bootchart). See doc/README.trace for full
2457 bool "avb - Android Verified Boot 2.0 operations"
2458 depends on AVB_VERIFY
2460 Enables a "avb" command to perform verification of partitions using
2461 Android Verified Boot 2.0 functionality. It includes such subcommands:
2462 avb init - initialize avb2 subsystem
2463 avb read_rb - read rollback index
2464 avb write_rb - write rollback index
2465 avb is_unlocked - check device lock state
2466 avb get_uuid - read and print uuid of a partition
2467 avb read_part - read data from partition
2468 avb read_part_hex - read data from partition and output to stdout
2469 avb write_part - write data to partition
2470 avb verify - run full verification chain
2472 config CMD_STACKPROTECTOR_TEST
2473 bool "Test command for stack protector"
2474 depends on STACKPROTECTOR
2476 Enable stackprot_test command
2477 The stackprot_test command will force a stack overrun to test
2478 the stack smashing detection mechanisms.
2483 tristate "Enable UBI - Unsorted block images commands"
2486 UBI is a software layer above MTD layer which admits use of LVM-like
2487 logical volumes on top of MTD devices, hides some complexities of
2488 flash chips like wear and bad blocks and provides some other useful
2489 capabilities. Please, consult the MTD web site for more details
2490 (www.linux-mtd.infradead.org). Activate this option if you want
2491 to use U-Boot UBI commands.
2492 It is also strongly encouraged to also enable CONFIG_MTD to get full
2495 config CMD_UBI_RENAME
2496 bool "Enable rename"
2499 Enable a "ubi" command to rename ubi volume:
2500 ubi rename <oldname> <newname>
2503 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2505 default y if CMD_UBI
2508 UBIFS is a file system for flash devices which works on top of UBI.
2510 config MMC_SPEED_MODE_SET
2511 bool "set speed mode using mmc command"
2515 Enable setting speed mode using mmc rescan and mmc dev commands.
2516 The speed mode is provided as the last argument in these commands
2517 and is indicated using the index from enum bus_mode in
2518 include/mmc.h. A speed mode can be set only if it has already
2519 been enabled in the device tree.
projects / J-u-boot.git / blob