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
59 string "Command execution tracer"
63 This option enables the possiblity to print all commands before
64 executing them and after all variables are evaluated (similar
65 to Bash's xtrace/'set -x' feature).
66 To enable the tracer a variable "xtrace" needs to be defined in
69 menu "Autoboot options"
75 This enables the autoboot. See doc/README.autoboot for detail.
78 bool "Stop autobooting via specific input key / string"
81 This option enables stopping (aborting) of the automatic
82 boot feature only by issuing a specific input key or
83 string. If not enabled, any input key will abort the
84 U-Boot automatic booting process and bring the device
85 to the U-Boot prompt for user input.
87 config AUTOBOOT_PROMPT
88 string "Autoboot stop prompt"
89 depends on AUTOBOOT_KEYED
90 default "Autoboot in %d seconds\\n"
92 This string is displayed before the boot delay selected by
93 CONFIG_BOOTDELAY starts. If it is not defined there is no
94 output indicating that autoboot is in progress.
96 Note that this define is used as the (only) argument to a
97 printf() call, so it may contain '%' format specifications,
98 provided that it also includes, sepearated by commas exactly
99 like in a printf statement, the required arguments. It is
100 the responsibility of the user to select only such arguments
101 that are valid in the given context.
103 config AUTOBOOT_ENCRYPTION
104 bool "Enable encryption in autoboot stopping"
105 depends on AUTOBOOT_KEYED
107 This option allows a string to be entered into U-Boot to stop the
108 autoboot. The string itself is hashed and compared against the hash
109 in the environment variable 'bootstopkeysha256'. If it matches then
110 boot stops and a command-line prompt is presented.
112 This provides a way to ship a secure production device which can also
113 be accessed at the U-Boot command line.
115 config AUTOBOOT_DELAY_STR
116 string "Delay autobooting via specific input key / string"
117 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
119 This option delays the automatic boot feature by issuing
120 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
121 or the environment variable "bootdelaykey" is specified
122 and this string is received from console input before
123 autoboot starts booting, U-Boot gives a command prompt. The
124 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
125 used, otherwise it never times out.
127 config AUTOBOOT_STOP_STR
128 string "Stop autobooting via specific input key / string"
129 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
131 This option enables stopping (aborting) of the automatic
132 boot feature only by issuing a specific input key or
133 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
134 variable "bootstopkey" is specified and this string is
135 received from console input before autoboot starts booting,
136 U-Boot gives a command prompt. The U-Boot prompt never
137 times out, even if CONFIG_BOOT_RETRY_TIME is used.
139 config AUTOBOOT_KEYED_CTRLC
140 bool "Enable Ctrl-C autoboot interruption"
141 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
144 This option allows for the boot sequence to be interrupted
145 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
146 Setting this variable provides an escape sequence from the
147 limited "password" strings.
149 config AUTOBOOT_STOP_STR_SHA256
150 string "Stop autobooting via SHA256 encrypted password"
151 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
153 This option adds the feature to only stop the autobooting,
154 and therefore boot into the U-Boot prompt, when the input
155 string / password matches a values that is encypted via
156 a SHA256 hash and saved in the environment.
158 config AUTOBOOT_USE_MENUKEY
159 bool "Allow a specify key to run a menu from the environment"
160 depends on !AUTOBOOT_KEYED
162 If a specific key is pressed to stop autoboot, then the commands in
163 the environment variable 'menucmd' are executed before boot starts.
165 config AUTOBOOT_MENUKEY
166 int "ASCII value of boot key to show a menu"
168 depends on AUTOBOOT_USE_MENUKEY
170 If this key is pressed to stop autoboot, then the commands in the
171 environment variable 'menucmd' will be executed before boot starts.
172 For example, 33 means "!" in ASCII, so pressing ! at boot would take
175 config AUTOBOOT_MENU_SHOW
176 bool "Show a menu on boot"
177 depends on CMD_BOOTMENU
179 This enables the boot menu, controlled by environment variables
180 defined by the board. The menu starts after running the 'preboot'
181 environmnent variable (if enabled) and before handling the boot delay.
182 See README.bootmenu for more details.
197 List and dump ACPI tables. ACPI (Advanced Configuration and Power
198 Interface) is used mostly on x86 for providing information to the
199 Operating System about devices in the system. The tables are set up
200 by the firmware, typically U-Boot but possibly an earlier firmware
201 module, if U-Boot is chain-loaded from something else. ACPI tables
202 can also include code, to perform hardware-specific tasks required
203 by the Operating Systems. This allows some amount of separation
204 between the firmware and OS, and is particularly useful when you
205 want to make hardware changes without the OS needing to be adjusted.
218 Print ".config" contents.
220 If this option is enabled, the ".config" file contents are embedded
221 in the U-Boot image and can be printed on the console by the "config"
222 command. This provides information of which options are enabled on
229 Print console devices and information.
234 Print information about available CPUs. This normally shows the
235 number of CPUs, type (e.g. manufacturer, architecture, product or
236 internal name) and clock frequency. Other information may be
237 available depending on the CPU driver.
243 Print GPL license text
248 Provides access to the Intel Power-Management Controller (PMC) so
249 that its state can be examined. This does not currently support
250 changing the state but it is still useful for debugging and seeing
259 config CMD_TLV_EEPROM
261 depends on I2C_EEPROM
263 Display and program the system EEPROM data block in ONIE Tlvinfo
264 format. TLV stands for Type-Length-Value.
266 config SPL_CMD_TLV_EEPROM
267 bool "tlv_eeprom for SPL"
268 depends on SPL_I2C_EEPROM
269 select SPL_DRIVERS_MISC_SUPPORT
271 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
281 Run the command stored in the environment "bootcmd", i.e.
282 "bootd" does the same thing as "run bootcmd".
288 Boot an application image from the memory.
291 bool "Support booting UEFI FIT images"
292 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
295 Support booting UEFI FIT images via the bootm command.
300 Boot the Linux zImage
304 depends on ARM64 || RISCV
307 Boot an AArch64 Linux Kernel image from memory.
310 bool "Support booting Linux OS images"
311 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
314 Support booting the Linux kernel directly via a command such as bootm
318 bool "Support booting NetBSD (non-EFI) loader images"
322 Support booting NetBSD via the bootm command.
324 config BOOTM_OPENRTOS
325 bool "Support booting OPENRTOS / FreeRTOS images"
328 Support booting OPENRTOS / FreeRTOS via the bootm command.
331 bool "Support booting Enea OSE images"
332 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
335 Support booting Enea OSE images via the bootm command.
338 bool "Support booting Plan9 OS images"
342 Support booting Plan9 images via the bootm command.
345 bool "Support booting RTEMS OS images"
349 Support booting RTEMS images via the bootm command.
352 bool "Support booting VxWorks OS images"
356 Support booting VxWorks images via the bootm command.
360 depends on EFI_LOADER
363 Boot an EFI image from memory.
365 config CMD_BOOTEFI_HELLO_COMPILE
366 bool "Compile a standard EFI hello world binary for testing"
367 depends on CMD_BOOTEFI && !CPU_V7M
370 This compiles a standard EFI hello world application with U-Boot so
371 that it can be used with the test/py testing framework. This is useful
372 for testing that EFI is working at a basic level, and for bringing
373 up EFI support on a new architecture.
375 No additional space will be required in the resulting U-Boot binary
376 when this option is enabled.
378 config CMD_BOOTEFI_HELLO
379 bool "Allow booting a standard EFI hello world for testing"
380 depends on CMD_BOOTEFI_HELLO_COMPILE
381 default y if CMD_BOOTEFI_SELFTEST
383 This adds a standard EFI hello world application to U-Boot so that
384 it can be used with the 'bootefi hello' command. This is useful
385 for testing that EFI is working at a basic level, and for bringing
386 up EFI support on a new architecture.
388 source lib/efi_selftest/Kconfig
394 Add an ANSI terminal boot menu command.
399 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
400 image into RAM, dump image structure information, etc. Those dtb/dtbo
401 files should be merged in one dtb further, which needs to be passed to
402 the kernel, as part of a boot process.
406 depends on ANDROID_BOOT_IMAGE
408 Android Boot Image manipulation commands. Allows one to extract
409 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
410 obtain corresponding meta-information from boot.img.
412 See doc/android/boot-image.rst for details.
415 bool "bootelf, bootvx"
419 Boot an ELF/vxWorks image from the memory.
422 bool "Flattened Device Tree utility commands"
426 Do FDT related setup before booting into the Operating System.
432 Start an application at a given address.
438 Run the command in the given environment variable.
444 Print header information for application image.
449 List all images found in flash
455 Extract a part of a multi-image.
458 bool "spl export - Export boot information for Falcon boot"
461 Falcon mode allows booting directly from SPL into an Operating
462 System such as Linux, thus skipping U-Boot proper. See
463 doc/README.falcon for full information about how to use this
466 config CMD_SPL_NAND_OFS
467 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
468 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
471 This provides the offset of the command line arguments for Linux
472 when booting from NAND in Falcon mode. See doc/README.falcon
473 for full information about how to use this option (and also see
474 board/gateworks/gw_ventana/README for an example).
476 config CMD_SPL_NOR_OFS
477 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
478 depends on CMD_SPL && SPL_NOR_SUPPORT
481 This provides the offset of the command line arguments or dtb for
482 Linux when booting from NOR in Falcon mode.
484 config CMD_SPL_WRITE_SIZE
485 hex "Size of argument area"
489 This provides the size of the command-line argument area in NAND
490 flash used by Falcon-mode boot. See the documentation until CMD_SPL
493 config CMD_THOR_DOWNLOAD
494 bool "thor - TIZEN 'thor' download"
497 Implements the 'thor' download protocol. This is a way of
498 downloading a software update over USB from an attached host.
499 There is no documentation about this within the U-Boot source code
500 but you should be able to find something on the interwebs.
503 bool "zboot - x86 boot command"
505 With x86 machines it is common to boot a bzImage file which
506 contains both a kernel and a setup.bin file. The latter includes
507 configuration information from the dark ages which x86 boards still
508 need to pick things out of.
510 Consider using FIT in preference to this since it supports directly
511 booting both 32- and 64-bit kernels, as well as secure boot.
512 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
516 menu "Environment commands"
519 bool "ask for env variable"
521 Ask for environment variable
539 Edit environment variable.
544 Allow for searching environment variables
550 Save all environment variables into the compiled-in persistent
556 depends on CMD_SAVEENV
558 Erase environment variables from the compiled-in persistent
561 config CMD_ENV_EXISTS
565 Check if a variable is defined in the environment for use in
568 config CMD_ENV_CALLBACK
569 bool "env callbacks - print callbacks and their associated variables"
571 Some environment variable have callbacks defined by
572 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
573 For example changing "baudrate" adjust the serial baud rate. This
574 command lists the currently defined callbacks.
577 bool "env flags -print variables that have non-default flags"
579 Some environment variables have special flags that control their
580 behaviour. For example, serial# can only be written once and cannot
581 be deleted. This command shows the variables that have special
584 config CMD_NVEDIT_EFI
585 bool "env [set|print] -e - set/print UEFI variables"
586 depends on EFI_LOADER
589 UEFI variables are encoded as some form of U-Boot variables.
590 If enabled, we are allowed to set/print UEFI variables using
591 "env" command with "-e" option without knowing details.
593 config CMD_NVEDIT_INFO
594 bool "env info - print or evaluate environment information"
596 Print environment information:
597 - env_valid : is environment valid
598 - env_ready : is environment imported into hash table
599 - env_use_default : is default environment used
601 This command can be optionally used for evaluation in scripts:
602 [-d] : evaluate whether default environment is used
603 [-p] : evaluate whether environment can be persisted
605 The result of multiple evaluations will be combined with AND.
607 config CMD_NVEDIT_LOAD
610 Load all environment variables from the compiled-in persistent
613 config CMD_NVEDIT_SELECT
616 Select the compiled-in persistent storage of environment variables.
620 menu "Memory commands"
625 Compute binary operations (xor, or, and) of byte arrays of arbitrary
626 size from memory and store the result in memory or the environment.
639 Add -v option to verify data against a crc32 checksum.
642 bool "eeprom - EEPROM subsystem"
644 (deprecated, needs conversion to driver model)
645 Provides commands to read and write EEPROM (Electrically Erasable
646 Programmable Read Only Memory) chips that are connected over an
649 config CMD_EEPROM_LAYOUT
650 bool "Enable layout-aware eeprom commands"
651 depends on CMD_EEPROM
653 (deprecated, needs conversion to driver model)
654 When enabled, additional eeprom sub-commands become available.
656 eeprom print - prints the contents of the eeprom in a human-readable
657 way (eeprom layout fields, and data formatted to be fit for human
660 eeprom update - allows user to update eeprom fields by specifying
661 the field name, and providing the new data in a human readable format
662 (same format as displayed by the eeprom print command).
664 Both commands can either auto detect the layout, or be told which
668 __weak int parse_layout_version(char *str)
669 - override to provide your own layout name parsing
670 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
672 - override to setup the layout metadata based on the version
673 __weak int eeprom_layout_detect(unsigned char *data)
674 - override to provide your own algorithm for detecting layout
677 - contains various printing and updating functions for common
678 types of eeprom fields. Can be used for defining
681 config EEPROM_LAYOUT_HELP_STRING
682 string "Tells user what layout names are supported"
683 depends on CMD_EEPROM_LAYOUT
684 default "<not defined>"
686 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
692 Infinite write loop on address range
699 Compute MD5 checksum.
704 depends on CMD_MD5SUM
706 Add -v option to verify data against an MD5 checksum.
711 Display memory information.
714 bool "md, mm, nm, mw, cp, cmp, base, loop"
719 mm - memory modify (auto-incrementing address)
720 nm - memory modify (constant address)
721 mw - memory write (fill)
724 base - print or set address offset
725 loop - initialize loop on address range
727 config CMD_MEM_SEARCH
728 bool "ms - Memory search"
730 Memory-search command
732 This allows searching through a region of memory looking for hex
733 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
734 support it). It is also possible to search for a string. The
735 command accepts a memory range and a list of values to search for.
736 The values need to appear in memory in the same order they are given
737 in the command. At most 10 matches can be returned at a time, but
738 pressing return will show the next 10 matches. Environment variables
739 are set for use with scripting (memmatches, memaddr, mempos).
742 bool "Enable cyclic md/mw commands"
743 depends on CMD_MEMORY
745 Add the "mdc" and "mwc" memory commands. These are cyclic
750 This command will print 4 bytes (10,11,12,13) each 500 ms.
752 => mwc.l 100 12345678 10
753 This command will write 12345678 to address 100 all 10 ms.
758 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
760 random - fill memory with random data
765 Simple RAM read/write test.
769 config SYS_ALT_MEMTEST
770 bool "Alternative test"
772 Use a more complete alternative memory test.
774 config SYS_MEMTEST_START
775 hex "default start address for mtest"
778 This is the default start address for mtest for simple read/write
779 test. If no arguments are given to mtest, default address is used
782 config SYS_MEMTEST_END
783 hex "default end address for mtest"
786 This is the default end address for mtest for simple read/write
787 test. If no arguments are given to mtest, default address is used
796 Compute SHA1 checksum.
798 config SHA1SUM_VERIFY
800 depends on CMD_SHA1SUM
802 Add -v option to verify data against a SHA1 checksum.
805 bool "strings - display strings in memory"
807 This works similarly to the Unix 'strings' command except that it
808 works with a memory range. String of printable characters found
809 within the range are displayed. The minimum number of characters
810 for a sequence to be considered a string can be provided.
814 menu "Compression commands"
818 default y if CMD_BOOTI
821 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
826 default y if CMD_BOOTI
829 Support decompressing an LZ4 image from memory region.
833 default y if CMD_BOOTI
836 Uncompress a zip-compressed memory region.
840 select GZIP_COMPRESSED
842 Compress a memory region with zlib deflate method.
846 menu "Device access commands"
849 #depends on FLASH_CFI_DRIVER
852 ARM Ltd reference designs flash partition access
855 bool "adc - Access Analog to Digital Converters info and data"
859 Shows ADC device info and permit printing one-shot analog converted
860 data from a named Analog to Digital Converter.
865 depends on PARTITIONS
867 Read/modify/write the fields of Bootloader Control Block, usually
868 stored on the flash "misc" partition with its structure defined in:
869 https://android.googlesource.com/platform/bootable/recovery/+/master/
870 bootloader_message/include/bootloader_message/bootloader_message.h
872 Some real-life use-cases include (but are not limited to):
873 - Determine the "boot reason" (and act accordingly):
874 https://source.android.com/devices/bootloader/boot-reason
875 - Get/pass a list of commands from/to recovery:
876 https://android.googlesource.com/platform/bootable/recovery
877 - Inspect/dump the contents of the BCB fields
880 bool "bind/unbind - Bind or unbind a device to/from a driver"
883 Bind or unbind a device to/from a driver from the command line.
884 This is useful in situations where a device may be handled by several
885 drivers. For example, this can be used to bind a UDC to the usb ether
886 gadget driver from the command line.
889 bool "clk - Show clock frequencies"
892 Shows clock frequences by calling a sock_clk_dump() hook function.
893 This is depreated in favour of using the CLK uclass and accessing
894 clock values from associated drivers. However currently no command
898 bool "demo - Demonstration commands for driver model"
901 Provides a 'demo' command which can be used to play around with
902 driver model. To use this properly you will need to enable one or
903 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
904 Otherwise you will always get an empty list of devices. The demo
905 devices are defined in the sandbox device tree, so the easiest
906 option is to use sandbox and pass the -d point to sandbox's
913 Enables the command "dfu" which is used to have U-Boot create a DFU
914 class device via USB. This command requires that the "dfu_alt_info"
915 environment variable be set and define the alt settings to expose to
919 bool "dm - Access to driver model information"
922 Provides access to driver model data structures and information,
923 such as a list of devices, list of uclasses and the state of each
924 device (e.g. activated). This is not required for operation, but
925 can be useful to see the state of driver model for debugging or
929 bool "fastboot - Android fastboot support"
932 This enables the command "fastboot" which enables the Android
933 fastboot mode for the platform. Fastboot is a protocol for
934 downloading images, flashing and device control used on
935 Android devices. Fastboot requires either the network stack
936 enabled or support for acting as a USB device.
938 See doc/android/fastboot.rst for more information.
941 bool "flinfo, erase, protect"
943 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
946 flinfo - print FLASH memory information
948 protect - enable or disable FLASH write protection
957 config CMD_FPGA_LOADBP
958 bool "fpga loadbp - load partial bitstream (Xilinx only)"
961 Supports loading an FPGA device from a bitstream buffer containing
964 config CMD_FPGA_LOADFS
965 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
968 Supports loading an FPGA device from a FAT filesystem.
970 config CMD_FPGA_LOADMK
971 bool "fpga loadmk - load bitstream from image"
974 Supports loading an FPGA device from a image generated by mkimage.
976 config CMD_FPGA_LOADP
977 bool "fpga loadp - load partial bitstream"
980 Supports loading an FPGA device from a bitstream buffer containing
983 config CMD_FPGA_LOAD_SECURE
984 bool "fpga loads - loads secure bitstreams (Xilinx only)"
987 Enables the fpga loads command which is used to load secure
988 (authenticated or encrypted or both) bitstreams on to FPGA.
991 bool "fpgad - dump FPGA registers"
993 (legacy, needs conversion to driver model)
994 Provides a way to dump FPGA registers by calling the board-specific
995 fpga_get_reg() function. This functions similarly to the 'md'
999 bool "fuse - support for the fuse subssystem"
1001 (deprecated - needs conversion to driver model)
1002 This allows reading, sensing, programming or overriding fuses
1003 which control the behaviour of the device. The command uses the
1012 bool "GPT (GUID Partition Table) command"
1013 select EFI_PARTITION
1014 select HAVE_BLOCK_DEVICE
1015 select PARTITION_UUIDS
1018 Enable the 'gpt' command to ready and write GPT style partition
1022 bool "GPT Random UUID generation"
1025 Enable the generation of partitions with random UUIDs if none
1028 config CMD_GPT_RENAME
1029 bool "GPT partition renaming commands"
1032 Enables the 'gpt' command to interchange names on two GPT
1033 partitions via the 'gpt swap' command or to rename single
1034 partitions via the 'rename' command.
1037 bool "ide - Support for IDE drivers"
1040 Provides an 'ide' command which allows accessing the IDE drive,
1041 reseting the IDE interface, printing the partition table and
1042 geting device info. It also enables the 'diskboot' command which
1043 permits booting from an IDE drive.
1046 bool "io - Support for performing I/O accesses"
1048 Provides an 'iod' command to display I/O space and an 'iow' command
1049 to write values to the I/O space. This can be useful for manually
1050 checking the state of devices during boot when debugging device
1054 bool "iotrace - Support for tracing I/O activity"
1056 Provides an 'iotrace' command which supports recording I/O reads and
1057 writes in a trace buffer in memory . It also maintains a checksum
1058 of the trace records (even if space is exhausted) so that the
1059 sequence of I/O accesses can be verified.
1061 When debugging drivers it is useful to see what I/O accesses were
1062 done and in what order.
1064 Even if the individual accesses are of little interest it can be
1065 useful to verify that the access pattern is consistent each time
1066 an operation is performed. In this case a checksum can be used to
1067 characterise the operation of a driver. The checksum can be compared
1068 across different runs of the operation to verify that the driver is
1071 In particular, when performing major refactoring of the driver, where
1072 the access pattern should not change, the checksum provides assurance
1073 that the refactoring work has not broken the driver.
1075 This works by sneaking into the io.h heder for an architecture and
1076 redirecting I/O accesses through iotrace's tracing mechanism.
1078 For now no commands are provided to examine the trace buffer. The
1079 format is fairly simple, so 'md' is a reasonable substitute.
1081 Note: The checksum feature is only useful for I/O regions where the
1082 contents do not change outside of software control. Where this is not
1083 suitable you can fall back to manually comparing the addresses. It
1084 might be useful to enhance tracing to only checksum the accesses and
1085 not the data read/written.
1095 bool "w1 - Support for Dallas 1-Wire protocol"
1097 Dallas 1-wire protocol support
1103 Load a binary file over serial line.
1109 Load an S-Record file over serial line
1113 bool "lsblk - list block drivers and devices"
1115 Print list of available block device drivers, and for each, the list
1116 of known block devices.
1121 MMC memory mapped support.
1125 config CMD_BKOPS_ENABLE
1126 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
1162 select MTD_PARTITIONS
1164 MTD commands support.
1168 default y if NAND_SUNXI
1169 depends on MTD_RAW_NAND
1174 config CMD_NAND_TRIMFFS
1175 bool "nand write.trimffs"
1176 default y if ARCH_SUNXI
1178 Allows one to skip empty pages when flashing something on a NAND.
1180 config CMD_NAND_LOCK_UNLOCK
1181 bool "nand lock/unlock"
1183 NAND locking support.
1185 config CMD_NAND_TORTURE
1188 NAND torture support.
1197 NVM Express device support
1200 bool "onenand - access to onenand device"
1203 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1204 various useful features. This command allows reading, writing,
1205 and erasing blocks. It allso provides a way to show and change
1206 bad blocks, and test the device.
1211 Enable the 'osd' command which allows to query information from and
1212 write text data to a on-screen display (OSD) device; a virtual device
1213 associated with a display capable of displaying a text overlay on the
1214 display it's associated with..
1218 select HAVE_BLOCK_DEVICE
1219 select PARTITION_UUIDS
1221 Read and display information about the partition table on
1225 bool "pci - Access PCI devices"
1227 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1228 used on some devices to allow the CPU to communicate with its
1229 peripherals. Sub-commands allow bus enumeration, displaying and
1230 changing configuration space and a few other features.
1233 bool "pinmux - show pins muxing"
1234 default y if PINCTRL
1236 Parse all available pin-controllers and show pins muxing. This
1237 is useful for debug purpoer to check the pin muxing and to know if
1238 a pin is configured as a GPIO or as an alternate function.
1243 Poweroff/Shutdown the system
1246 bool "read - Read binary data from a partition"
1248 Provides low-level access to the data in a partition.
1250 config CMD_REMOTEPROC
1252 depends on REMOTEPROC
1254 Support for Remote Processor control
1257 bool "sata - Access SATA subsystem"
1260 SATA (Serial Advanced Technology Attachment) is a serial bus
1261 standard for connecting to hard drives and other storage devices.
1262 This command provides information about attached devices and allows
1263 reading, writing and other operations.
1265 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1266 Attachment, where AT refers to an IBM AT (Advanced Technology)
1267 computer released in 1984.
1270 bool "saves - Save a file over serial in S-Record format"
1272 Provides a way to save a binary file using the Motorola S-Record
1273 format over the serial line.
1276 bool "scsi - Access to SCSI devices"
1279 This provides a 'scsi' command which provides access to SCSI (Small
1280 Computer System Interface) devices. The command provides a way to
1281 scan the bus, reset the bus, read and write data and get information
1285 bool "sdram - Print SDRAM configuration information"
1287 Provides information about attached SDRAM. This assumed that the
1288 SDRAM has an EEPROM with information that can be read using the
1289 I2C bus. This is only available on some boards.
1293 depends on DM_SPI_FLASH || SPI_FLASH
1294 default y if DM_SPI_FLASH
1299 bool "sf test - Allow testing of SPI flash"
1302 Provides a way to test that SPI flash is working correctly. The
1303 test is destructive, in that an area of SPI flash must be provided
1304 for the test to use. Performance information is also provided,
1305 measuring the performance of reading, writing and erasing in
1306 Mbps (Million Bits Per Second). This value should approximately
1307 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1308 everything is working properly.
1311 bool "sspi - Command to access spi device"
1314 SPI utility command.
1316 config DEFAULT_SPI_BUS
1317 int "default spi bus used by sspi command"
1321 config DEFAULT_SPI_MODE
1322 hex "default spi mode used by sspi command (see include/spi.h)"
1327 bool "tsi148 - Command to access tsi148 device"
1329 This provides various sub-commands to initialise and configure the
1330 Turndra tsi148 device. See the command help for full details.
1333 bool "Enable UFS - Universal Flash Subsystem commands"
1336 "This provides commands to initialise and configure universal flash
1340 bool "universe - Command to set up the Turndra Universe controller"
1342 This allows setting up the VMEbus provided by this controller.
1343 See the command help for full details.
1347 select HAVE_BLOCK_DEVICE
1353 select USB_FUNCTION_SDP
1355 Enables the command "sdp" which is used to have U-Boot emulating the
1356 Serial Download Protocol (SDP) via USB.
1360 depends on USB_FUNCTION_ROCKUSB
1362 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1363 read/write info, image to/from devices. This enable rockusb command
1364 support to communication with rockusb device. for more detail about
1365 this command, please read doc/README.rockusb.
1367 config CMD_USB_MASS_STORAGE
1368 bool "UMS usb mass storage"
1369 select USB_FUNCTION_MASS_STORAGE
1371 USB mass storage support
1374 bool "Xen para-virtualized block device"
1378 Xen para-virtualized block device support
1385 VirtIO block device support
1391 This provides commands to control the watchdog timer devices.
1397 Enable the command "axi" for accessing AXI (Advanced eXtensible
1398 Interface) busses, a on-chip interconnect specification for managing
1399 functional blocks in SoC designs, which is also often used in designs
1400 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1404 menu "Shell scripting commands"
1410 Echo args to console
1416 Return true/false on integer compare.
1422 Run script from memory
1428 Evaluate boolean and math expressions and store the result in an env
1430 Also supports loading the value at a memory location into a variable.
1431 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1435 menu "Android support commands"
1437 config CMD_AB_SELECT
1440 depends on ANDROID_AB
1442 On Android devices with more than one boot slot (multiple copies of
1443 the kernel and system images) this provides a command to select which
1444 slot should be used to boot from and register the boot attempt. This
1445 is used by the new A/B update model where one slot is updated in the
1446 background while running from the other slot.
1453 bool "Network commands"
1463 bootp - boot image via network using BOOTP/TFTP protocol
1467 depends on CMD_BOOTP
1469 Boot image via network using DHCP/TFTP protocol
1471 config BOOTP_BOOTPATH
1472 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1474 depends on CMD_BOOTP
1476 Even though the config is called BOOTP_BOOTPATH, it stores the
1477 path in the variable 'rootpath'.
1480 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1482 depends on CMD_BOOTP
1484 The primary DNS server is stored as 'dnsip'. If two servers are
1485 returned, you must set BOOTP_DNS2 to store that second server IP
1489 bool "Store 'dnsip2' from BOOTP/DHCP server"
1490 depends on BOOTP_DNS
1492 If a DHCP client requests the DNS server IP from a DHCP server,
1493 it is possible that more than one DNS serverip is offered to the
1494 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1495 server IP will be stored in the additional environment
1496 variable "dnsip2". The first DNS serverip is always
1497 stored in the variable "dnsip", when BOOTP_DNS is defined.
1499 config BOOTP_GATEWAY
1500 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1502 depends on CMD_BOOTP
1504 config BOOTP_HOSTNAME
1505 bool "Request & store 'hostname' from BOOTP/DHCP server"
1507 depends on CMD_BOOTP
1509 The name may or may not be qualified with the local domain name.
1511 config BOOTP_PREFER_SERVERIP
1512 bool "serverip variable takes precedent over DHCP server IP."
1513 depends on CMD_BOOTP
1515 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1517 With this option enabled, the 'serverip' variable in the environment
1518 takes precedence over DHCP server IP and will only be set by the DHCP
1519 server if not already set in the environment.
1521 config BOOTP_SUBNETMASK
1522 bool "Request & store 'netmask' from BOOTP/DHCP server"
1524 depends on CMD_BOOTP
1526 config BOOTP_NTPSERVER
1527 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1528 depends on CMD_BOOTP
1533 Selecting this will allow capturing all Ethernet packets and store
1534 them in physical memory in a PCAP formated file,
1535 later to be analyzed by PCAP reader application (IE. WireShark).
1538 bool "Send PXE client arch to BOOTP/DHCP server"
1540 depends on CMD_BOOTP && CMD_PXE
1542 Supported for ARM, ARM64, and x86 for now.
1544 config BOOTP_PXE_CLIENTARCH
1546 depends on BOOTP_PXE
1547 default 0x16 if ARM64
1551 config BOOTP_VCI_STRING
1553 depends on CMD_BOOTP
1554 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1555 default "U-Boot.armv8" if ARM64
1556 default "U-Boot.arm" if ARM
1563 tftpboot - boot image via network using TFTP protocol
1567 depends on CMD_TFTPBOOT
1569 TFTP put command, for uploading files to a server
1573 depends on CMD_TFTPBOOT
1575 Act as a TFTP server and boot the first received file
1577 config NET_TFTP_VARS
1578 bool "Control TFTP timeout and count through environment"
1579 depends on CMD_TFTPBOOT
1582 If set, allows controlling the TFTP timeout through the
1583 environment variable tftptimeout, and the TFTP maximum
1584 timeout count through the variable tftptimeoutcountmax.
1585 If unset, timeout and maximum are hard-defined as 1 second
1586 and 10 timouts per TFTP transfer.
1591 Boot image via network using RARP/TFTP protocol
1597 Boot image via network using NFS protocol.
1603 If set, allows 802.3(clause 22) MII Management functions interface access
1604 The management interface specified in Clause 22 provides
1605 a simple, two signal, serial interface to connect a
1606 Station Management entity and a managed PHY for providing access
1607 to management parameters and services.
1608 The interface is referred to as the MII management interface.
1614 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1615 The MDIO interface is orthogonal to the MII interface and extends
1616 it by adding access to more registers through indirect addressing.
1621 Send ICMP ECHO_REQUEST to network host
1626 Perform CDP network configuration
1631 Synchronize RTC via network
1636 Lookup the IP of a hostname
1638 config CMD_LINK_LOCAL
1642 Acquire a network IP address using the link-local protocol
1649 Allow control of L2 Ethernet switch commands. These are supported
1650 by the vsc9953 Ethernet driver at present. Sub-commands allow
1651 operations such as enabling / disabling a port and
1652 viewing/maintaining the filtering database (FDB)
1658 Boot image via network using PXE protocol
1663 Wait for wake-on-lan Magic Packet
1667 menu "Misc commands"
1670 bool "Enable 'bmp' command"
1671 depends on LCD || DM_VIDEO || VIDEO
1673 This provides a way to obtain information about a BMP-format image
1674 and to display it. BMP (which presumably stands for BitMaP) is a
1675 file format defined by Microsoft which supports images of various
1676 depths, formats and compression methods. Headers on the file
1677 determine the formats used. This command can be used by first loading
1678 the image into RAM, then using this command to look at it or display
1681 config CMD_BOOTCOUNT
1683 depends on BOOTCOUNT_LIMIT
1685 Enable the bootcount command, which allows interrogation and
1686 reset of the bootcounter.
1689 bool "Enable board-specific commands"
1691 (deprecated: instead, please define a Kconfig option for each command)
1693 Some boards have board-specific commands which are only enabled
1694 during developemnt and need to be turned off for production. This
1695 option provides a way to control this. The commands that are enabled
1696 vary depending on the board.
1698 config CMD_BLOCK_CACHE
1699 bool "blkcache - control and stats for block cache"
1700 depends on BLOCK_CACHE
1701 default y if BLOCK_CACHE
1703 Enable the blkcache command, which can be used to control the
1704 operation of the cache functions.
1705 This is most useful when fine-tuning the operation of the cache
1706 during development, but also allows the cache to be disabled when
1707 it might hurt performance (e.g. when using the ums command).
1714 Enable the 'button' command which allows to get the status of
1715 buttons supported by the board. The buttonss can be listed with
1716 'button list' and state can be known with 'button <label>'.
1717 Any button drivers can be controlled with this command, e.g.
1721 bool "icache or dcache"
1723 Enable the "icache" and "dcache" commands
1725 config CMD_CONITRACE
1726 bool "conitrace - trace console input codes"
1728 Enable the 'conitrace' command which displays the codes received
1729 from the console input as hexadecimal numbers.
1732 bool "Enable clear screen command 'cls'"
1733 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1736 Enable the 'cls' command which clears the screen contents
1737 on video frame buffer.
1740 bool "efidebug - display/configure UEFI environment"
1741 depends on EFI_LOADER
1742 select EFI_DEVICE_PATH_TO_TEXT
1745 Enable the 'efidebug' command which provides a subset of UEFI
1746 shell utility with simplified functionality. It will be useful
1747 particularly for managing boot parameters as well as examining
1748 various EFI status for debugging.
1750 config CMD_EXCEPTION
1751 bool "exception - raise exception"
1752 depends on ARM || RISCV || X86
1754 Enable the 'exception' command which allows to raise an exception.
1761 Enable the 'led' command which allows for control of LEDs supported
1762 by the board. The LEDs can be listed with 'led list' and controlled
1763 with led on/off/togle/blink. Any LED drivers can be controlled with
1764 this command, e.g. led_gpio.
1771 Enable the 'date' command for getting/setting the time/date in RTC
1778 Enable the 'rtc' command for low-level access to RTC devices.
1783 Run commands and summarize execution time.
1786 bool "gettime - read elapsed time"
1788 Enable the 'gettime' command which reads the elapsed time since
1789 U-Boot started running. This shows the time in seconds and
1790 milliseconds. See also the 'bootstage' command which provides more
1791 flexibility for boot timing.
1798 Print bytes from the hardware random number generator.
1800 # TODO: rename to CMD_SLEEP
1805 Delay execution for some time
1808 bool "support for multiprocessor"
1810 This provides an option to brinup
1811 different processors in multiprocessor
1817 Access the system timer.
1823 This provides basic access to the U-Boot's sound support. The main
1824 feature is to play a beep.
1826 sound init - set up sound system
1827 sound play - play a sound
1833 Boot image via local extlinux.conf file
1839 This provides access to the QEMU firmware interface. The main
1840 feature is to allow easy loading of files passed to qemu-system
1841 via -kernel / -initrd
1843 source "cmd/mvebu/Kconfig"
1846 bool "terminal - provides a way to attach a serial terminal"
1848 Provides a 'cu'-like serial terminal command. This can be used to
1849 access other serial ports from the system console. The terminal
1850 is very simple with no special processing of characters. As with
1851 cu, you can press ~. (tilde followed by period) to exit.
1854 bool "uuid, guid - generation of unique IDs"
1857 This enables two commands:
1859 uuid - generate random Universally Unique Identifier
1860 guid - generate Globally Unique Identifier based on random UUID
1862 The two commands are very similar except for the endianness of the
1867 source "cmd/ti/Kconfig"
1869 config CMD_BOOTSTAGE
1870 bool "Enable the 'bootstage' command"
1871 depends on BOOTSTAGE
1873 Add a 'bootstage' command which supports printing a report
1874 and un/stashing of bootstage data.
1876 menu "Power commands"
1878 bool "Enable Driver Model PMIC command"
1881 This is the pmic command, based on a driver model pmic's API.
1882 Command features are unchanged:
1883 - list - list pmic devices
1884 - pmic dev <id> - show or [set] operating pmic device (NEW)
1885 - pmic dump - dump registers
1886 - pmic read address - read byte of register at address
1887 - pmic write address - write byte to register at address
1888 The only one change for this command is 'dev' subcommand.
1890 config CMD_REGULATOR
1891 bool "Enable Driver Model REGULATOR command"
1892 depends on DM_REGULATOR
1894 This command is based on driver model regulator's API.
1895 User interface features:
1896 - list - list regulator devices
1897 - regulator dev <id> - show or [set] operating regulator device
1898 - regulator info - print constraints info
1899 - regulator status - print operating status
1900 - regulator value <val] <-f> - print/[set] voltage value [uV]
1901 - regulator current <val> - print/[set] current value [uA]
1902 - regulator mode <id> - print/[set] operating mode id
1903 - regulator enable - enable the regulator output
1904 - regulator disable - disable the regulator output
1906 The '-f' (force) option can be used for set the value which exceeds
1907 the limits, which are found in device-tree and are kept in regulator's
1908 uclass platdata structure.
1912 menu "Security commands"
1914 bool "Enable the 'aes' command"
1917 This provides a means to encrypt and decrypt data using the AES
1918 (Advanced Encryption Standard). This algorithm uses a symetric key
1919 and is widely used as a streaming cipher. Different key lengths are
1920 supported by the algorithm but this command only supports 128 bits
1924 bool "Enable the 'blob' command"
1926 This is used with the Freescale secure boot mechanism.
1928 Freescale's SEC block has built-in Blob Protocol which provides
1929 a method for protecting user-defined data across system power
1930 cycles. SEC block protects data in a data structure called a Blob,
1931 which provides both confidentiality and integrity protection.
1933 Encapsulating data as a blob
1934 Each time that the Blob Protocol is used to protect data, a
1935 different randomly generated key is used to encrypt the data.
1936 This random key is itself encrypted using a key which is derived
1937 from SoC's non-volatile secret key and a 16 bit Key identifier.
1938 The resulting encrypted key along with encrypted data is called a
1939 blob. The non-volatile secure key is available for use only during
1942 During decapsulation, the reverse process is performed to get back
1946 blob enc - encapsulating data as a cryptgraphic blob
1947 blob dec - decapsulating cryptgraphic blob to get the data
1951 blob enc src dst len km
1953 Encapsulate and create blob of data $len bytes long
1954 at address $src and store the result at address $dst.
1955 $km is the 16 byte key modifier is also required for
1956 generation/use as key for cryptographic operation. Key
1957 modifier should be 16 byte long.
1959 blob dec src dst len km
1961 Decapsulate the blob of data at address $src and
1962 store result of $len byte at addr $dst.
1963 $km is the 16 byte key modifier is also required for
1964 generation/use as key for cryptographic operation. Key
1965 modifier should be 16 byte long.
1968 bool "Support 'hash' command"
1971 This provides a way to hash data in memory using various supported
1972 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1973 saved to memory or to an environment variable. It is also possible
1974 to verify a hash against data in memory.
1977 bool "Support the 'hvc' command"
1978 depends on ARM_SMCCC
1980 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1981 development and testing.
1984 bool "Support the 'smc' command"
1985 depends on ARM_SMCCC
1987 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1988 development and testing.
1994 Add -v option to verify data against a hash.
2004 bool "Enable the 'tpm' command"
2005 depends on TPM_V1 || TPM_V2
2006 select CMD_TPM_V1 if TPM_V1
2007 select CMD_TPM_V2 if TPM_V2
2009 This provides a means to talk to a TPM from the command line. A wide
2010 range of commands if provided - see 'tpm help' for details. The
2011 command requires a suitable TPM on your board and the correct driver
2017 bool "Enable the 'tpm test' command"
2020 This provides a a series of tests to confirm that the TPMv1.x is
2021 working correctly. The tests cover initialisation, non-volatile RAM,
2022 extend, global lock and checking that timing is within expectations.
2023 The tests pass correctly on Infineon TPMs but may need to be adjusted
2030 menu "Firmware commands"
2032 bool "Enable crosec command"
2036 Enable command-line access to the Chrome OS EC (Embedded
2037 Controller). This provides the 'crosec' command which has
2038 a number of sub-commands for performing EC tasks such as
2039 updating its flash, accessing a small saved context area
2040 and talking to the I2C bus behind the EC (if there is one).
2043 menu "Filesystem commands"
2045 bool "Enable the 'btrsubvol' command"
2048 This enables the 'btrsubvol' command to list subvolumes
2049 of a BTRFS filesystem. There are no special commands for
2050 listing BTRFS directories or loading BTRFS files - this
2051 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2052 when BTRFS is enabled (see FS_BTRFS).
2055 bool "Enable the 'cbfs' command"
2058 Define this to enable support for reading from a Coreboot
2059 filesystem. This is a ROM-based filesystem used for accessing files
2060 on systems that use coreboot as the first boot-loader and then load
2061 U-Boot to actually boot the Operating System. Available commands are
2062 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2065 bool "Enable the 'cramfs' command"
2066 depends on FS_CRAMFS
2068 This provides commands for dealing with CRAMFS (Compressed ROM
2069 filesystem). CRAMFS is useful when space is tight since files are
2070 compressed. Two commands are provided:
2072 cramfsls - lists files in a cramfs image
2073 cramfsload - loads a file from a cramfs image
2076 bool "ext2 command support"
2079 Enables EXT2 FS command
2082 bool "ext4 command support"
2085 Enables EXT4 FS command
2087 config CMD_EXT4_WRITE
2089 bool "ext4 write command support"
2092 Enables EXT4 FS write command
2095 bool "FAT command support"
2098 Support for the FAT fs
2101 bool "SquashFS command support"
2104 Enables SquashFS filesystem commands (e.g. load, ls).
2106 config CMD_FS_GENERIC
2107 bool "filesystem commands"
2109 Enables filesystem commands (e.g. load, ls) that work for multiple
2113 bool "fsuuid command"
2115 Enables fsuuid command for filesystem UUID.
2118 bool "jffs2 command"
2121 Enables commands to support the JFFS2 (Journalling Flash File System
2122 version 2) filesystem. This enables fsload, ls and fsinfo which
2123 provide the ability to load files, list directories and obtain
2124 filesystem information.
2127 bool "MTD partition support"
2130 MTD partitioning tool support.
2131 It is strongly encouraged to avoid using this command
2132 anymore along with 'sf', 'nand', 'onenand'. One can still
2133 declare the partitions in the mtdparts environment variable
2134 but better use the MTD stack and the 'mtd' command instead.
2136 config CMD_MTDPARTS_SPREAD
2137 bool "Padd partition size to take account of bad blocks"
2138 depends on CMD_MTDPARTS
2140 This enables the 'spread' sub-command of the mtdparts command.
2141 This command will modify the existing mtdparts variable by increasing
2142 the size of the partitions such that 1) each partition's net size is
2143 at least as large as the size specified in the mtdparts variable and
2144 2) each partition starts on a good block.
2146 config CMD_MTDPARTS_SHOW_NET_SIZES
2147 bool "Show net size (w/o bad blocks) of partitions"
2148 depends on CMD_MTDPARTS
2150 Adds two columns to the printed partition table showing the
2151 effective usable size of a partition, if bad blocks are taken
2154 config MTDIDS_DEFAULT
2155 string "Default MTD IDs"
2156 depends on MTD || SPI_FLASH
2158 Defines a default MTD IDs list for use with MTD partitions in the
2159 Linux MTD command line partitions format.
2161 config MTDPARTS_DEFAULT
2162 string "Default MTD partition scheme"
2163 depends on MTD || SPI_FLASH
2165 Defines a default MTD partitioning scheme in the Linux MTD command
2166 line partitions format
2169 bool "reiser - Access to reiserfs filesystems"
2171 This provides two commands which operate on a resierfs filesystem,
2172 commonly used some years ago:
2174 reiserls - list files
2175 reiserload - load a file
2178 bool "yaffs2 - Access of YAFFS2 filesystem"
2182 This provides commands for accessing a YAFFS2 filesystem. Yet
2183 Another Flash Filesystem 2 is a filesystem designed specifically
2184 for NAND flash. It incorporates bad-block management and ensures
2185 that device writes are sequential regardless of filesystem
2189 bool "zfs - Access of ZFS filesystem"
2191 This provides commands to accessing a ZFS filesystem, commonly used
2192 on Solaris systems. Two sub-commands are provided:
2194 zfsls - list files in a directory
2195 zfsload - load a file
2197 See doc/README.zfs for more details.
2201 menu "Debug commands"
2206 The bedbug (emBEDded deBUGger) command provides debugging features
2207 for some PowerPC processors. For details please see the
2208 documentation in doc/README.bedbug.
2211 bool "diag - Board diagnostics"
2213 This command provides access to board diagnostic tests. These are
2214 called Power-on Self Tests (POST). The command allows listing of
2215 available tests and running either all the tests, or specific tests
2219 bool "irq - Show information about interrupts"
2220 depends on !ARM && !MIPS && !SH
2222 This enables two commands:
2224 interrupts - enable or disable interrupts
2225 irqinfo - print device-specific interrupt information
2228 bool "kgdb - Allow debugging of U-Boot with gdb"
2231 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2232 over a serial link for debugging purposes. This allows
2233 single-stepping, inspecting variables, etc. This is supported only
2234 on PowerPC at present.
2237 bool "log - Generation, control and access to logging"
2240 This provides access to logging features. It allows the output of
2241 log data to be controlled to a limited extent (setting up the default
2242 maximum log level for emitting of records). It also provides access
2243 to a command used for testing the log system.
2246 bool "trace - Support tracing of function calls and timing"
2248 Enables a command to control using of function tracing within
2249 U-Boot. This allows recording of call traces including timing
2250 information. The command can write data to memory for exporting
2251 for analysis (e.g. using bootchart). See doc/README.trace for full
2255 bool "avb - Android Verified Boot 2.0 operations"
2256 depends on AVB_VERIFY
2259 Enables a "avb" command to perform verification of partitions using
2260 Android Verified Boot 2.0 functionality. It includes such subcommands:
2261 avb init - initialize avb2 subsystem
2262 avb read_rb - read rollback index
2263 avb write_rb - write rollback index
2264 avb is_unlocked - check device lock state
2265 avb get_uuid - read and print uuid of a partition
2266 avb read_part - read data from partition
2267 avb read_part_hex - read data from partition and output to stdout
2268 avb write_part - write data to partition
2269 avb verify - run full verification chain
2273 tristate "Enable UBI - Unsorted block images commands"
2276 UBI is a software layer above MTD layer which admits use of LVM-like
2277 logical volumes on top of MTD devices, hides some complexities of
2278 flash chips like wear and bad blocks and provides some other useful
2279 capabilities. Please, consult the MTD web site for more details
2280 (www.linux-mtd.infradead.org). Activate this option if you want
2281 to use U-Boot UBI commands.
2282 It is also strongly encouraged to also enable CONFIG_MTD to get full
2285 config CMD_UBI_RENAME
2286 bool "Enable rename"
2290 Enable a "ubi" command to rename ubi volume:
2291 ubi rename <oldname> <newname>
2294 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2296 default y if CMD_UBI
2299 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob