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.
275 depends on RISCV_SMODE && SBI_V02
277 Display information about the SBI implementation.
287 Run the command stored in the environment "bootcmd", i.e.
288 "bootd" does the same thing as "run bootcmd".
294 Boot an application image from the memory.
297 bool "Support booting UEFI FIT images"
298 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
301 Support booting UEFI FIT images via the bootm command.
306 Boot the Linux zImage
310 depends on ARM64 || RISCV
313 Boot an AArch64 Linux Kernel image from memory.
316 bool "Support booting Linux OS images"
317 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
320 Support booting the Linux kernel directly via a command such as bootm
324 bool "Support booting NetBSD (non-EFI) loader images"
328 Support booting NetBSD via the bootm command.
330 config BOOTM_OPENRTOS
331 bool "Support booting OPENRTOS / FreeRTOS images"
334 Support booting OPENRTOS / FreeRTOS via the bootm command.
337 bool "Support booting Enea OSE images"
338 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
341 Support booting Enea OSE images via the bootm command.
344 bool "Support booting Plan9 OS images"
348 Support booting Plan9 images via the bootm command.
351 bool "Support booting RTEMS OS images"
355 Support booting RTEMS images via the bootm command.
358 bool "Support booting VxWorks OS images"
362 Support booting VxWorks images via the bootm command.
366 depends on EFI_LOADER
369 Boot an EFI image from memory.
371 config CMD_BOOTEFI_HELLO_COMPILE
372 bool "Compile a standard EFI hello world binary for testing"
373 depends on CMD_BOOTEFI && !CPU_V7M
376 This compiles a standard EFI hello world application with U-Boot so
377 that it can be used with the test/py testing framework. This is useful
378 for testing that EFI is working at a basic level, and for bringing
379 up EFI support on a new architecture.
381 No additional space will be required in the resulting U-Boot binary
382 when this option is enabled.
384 config CMD_BOOTEFI_HELLO
385 bool "Allow booting a standard EFI hello world for testing"
386 depends on CMD_BOOTEFI_HELLO_COMPILE
387 default y if CMD_BOOTEFI_SELFTEST
389 This adds a standard EFI hello world application to U-Boot so that
390 it can be used with the 'bootefi hello' command. This is useful
391 for testing that EFI is working at a basic level, and for bringing
392 up EFI support on a new architecture.
394 source lib/efi_selftest/Kconfig
400 Add an ANSI terminal boot menu command.
405 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
406 image into RAM, dump image structure information, etc. Those dtb/dtbo
407 files should be merged in one dtb further, which needs to be passed to
408 the kernel, as part of a boot process.
412 depends on ANDROID_BOOT_IMAGE
414 Android Boot Image manipulation commands. Allows one to extract
415 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
416 obtain corresponding meta-information from boot.img.
418 See doc/android/boot-image.rst for details.
421 bool "bootelf, bootvx"
425 Boot an ELF/vxWorks image from the memory.
428 bool "Flattened Device Tree utility commands"
432 Do FDT related setup before booting into the Operating System.
438 Start an application at a given address.
444 Run the command in the given environment variable.
450 Print header information for application image.
455 List all images found in flash
461 Extract a part of a multi-image.
464 bool "spl export - Export boot information for Falcon boot"
467 Falcon mode allows booting directly from SPL into an Operating
468 System such as Linux, thus skipping U-Boot proper. See
469 doc/README.falcon for full information about how to use this
472 config CMD_SPL_NAND_OFS
473 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
474 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
477 This provides the offset of the command line arguments for Linux
478 when booting from NAND in Falcon mode. See doc/README.falcon
479 for full information about how to use this option (and also see
480 board/gateworks/gw_ventana/README for an example).
482 config CMD_SPL_NOR_OFS
483 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
484 depends on CMD_SPL && SPL_NOR_SUPPORT
487 This provides the offset of the command line arguments or dtb for
488 Linux when booting from NOR in Falcon mode.
490 config CMD_SPL_WRITE_SIZE
491 hex "Size of argument area"
495 This provides the size of the command-line argument area in NAND
496 flash used by Falcon-mode boot. See the documentation until CMD_SPL
499 config CMD_THOR_DOWNLOAD
500 bool "thor - TIZEN 'thor' download"
503 Implements the 'thor' download protocol. This is a way of
504 downloading a software update over USB from an attached host.
505 There is no documentation about this within the U-Boot source code
506 but you should be able to find something on the interwebs.
509 bool "zboot - x86 boot command"
511 With x86 machines it is common to boot a bzImage file which
512 contains both a kernel and a setup.bin file. The latter includes
513 configuration information from the dark ages which x86 boards still
514 need to pick things out of.
516 Consider using FIT in preference to this since it supports directly
517 booting both 32- and 64-bit kernels, as well as secure boot.
518 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
522 menu "Environment commands"
525 bool "ask for env variable"
527 Ask for environment variable
545 Edit environment variable.
550 Allow for searching environment variables
556 Save all environment variables into the compiled-in persistent
562 depends on CMD_SAVEENV
564 Erase environment variables from the compiled-in persistent
567 config CMD_ENV_EXISTS
571 Check if a variable is defined in the environment for use in
574 config CMD_ENV_CALLBACK
575 bool "env callbacks - print callbacks and their associated variables"
577 Some environment variable have callbacks defined by
578 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
579 For example changing "baudrate" adjust the serial baud rate. This
580 command lists the currently defined callbacks.
583 bool "env flags -print variables that have non-default flags"
585 Some environment variables have special flags that control their
586 behaviour. For example, serial# can only be written once and cannot
587 be deleted. This command shows the variables that have special
590 config CMD_NVEDIT_EFI
591 bool "env [set|print] -e - set/print UEFI variables"
592 depends on EFI_LOADER
595 UEFI variables are encoded as some form of U-Boot variables.
596 If enabled, we are allowed to set/print UEFI variables using
597 "env" command with "-e" option without knowing details.
599 config CMD_NVEDIT_INFO
600 bool "env info - print or evaluate environment information"
602 Print environment information:
603 - env_valid : is environment valid
604 - env_ready : is environment imported into hash table
605 - env_use_default : is default environment used
607 This command can be optionally used for evaluation in scripts:
608 [-d] : evaluate whether default environment is used
609 [-p] : evaluate whether environment can be persisted
611 The result of multiple evaluations will be combined with AND.
613 config CMD_NVEDIT_LOAD
616 Load all environment variables from the compiled-in persistent
619 config CMD_NVEDIT_SELECT
622 Select the compiled-in persistent storage of environment variables.
626 menu "Memory commands"
631 Compute binary operations (xor, or, and) of byte arrays of arbitrary
632 size from memory and store the result in memory or the environment.
645 Add -v option to verify data against a crc32 checksum.
648 bool "eeprom - EEPROM subsystem"
650 (deprecated, needs conversion to driver model)
651 Provides commands to read and write EEPROM (Electrically Erasable
652 Programmable Read Only Memory) chips that are connected over an
655 config CMD_EEPROM_LAYOUT
656 bool "Enable layout-aware eeprom commands"
657 depends on CMD_EEPROM
659 (deprecated, needs conversion to driver model)
660 When enabled, additional eeprom sub-commands become available.
662 eeprom print - prints the contents of the eeprom in a human-readable
663 way (eeprom layout fields, and data formatted to be fit for human
666 eeprom update - allows user to update eeprom fields by specifying
667 the field name, and providing the new data in a human readable format
668 (same format as displayed by the eeprom print command).
670 Both commands can either auto detect the layout, or be told which
674 __weak int parse_layout_version(char *str)
675 - override to provide your own layout name parsing
676 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
678 - override to setup the layout metadata based on the version
679 __weak int eeprom_layout_detect(unsigned char *data)
680 - override to provide your own algorithm for detecting layout
683 - contains various printing and updating functions for common
684 types of eeprom fields. Can be used for defining
687 config EEPROM_LAYOUT_HELP_STRING
688 string "Tells user what layout names are supported"
689 depends on CMD_EEPROM_LAYOUT
690 default "<not defined>"
692 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
698 Infinite write loop on address range
705 Compute MD5 checksum.
710 depends on CMD_MD5SUM
712 Add -v option to verify data against an MD5 checksum.
717 Display memory information.
720 bool "md, mm, nm, mw, cp, cmp, base, loop"
725 mm - memory modify (auto-incrementing address)
726 nm - memory modify (constant address)
727 mw - memory write (fill)
730 base - print or set address offset
731 loop - initialize loop on address range
733 config CMD_MEM_SEARCH
734 bool "ms - Memory search"
736 Memory-search command
738 This allows searching through a region of memory looking for hex
739 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
740 support it). It is also possible to search for a string. The
741 command accepts a memory range and a list of values to search for.
742 The values need to appear in memory in the same order they are given
743 in the command. At most 10 matches can be returned at a time, but
744 pressing return will show the next 10 matches. Environment variables
745 are set for use with scripting (memmatches, memaddr, mempos).
748 bool "Enable cyclic md/mw commands"
749 depends on CMD_MEMORY
751 Add the "mdc" and "mwc" memory commands. These are cyclic
756 This command will print 4 bytes (10,11,12,13) each 500 ms.
758 => mwc.l 100 12345678 10
759 This command will write 12345678 to address 100 all 10 ms.
764 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
766 random - fill memory with random data
771 Simple RAM read/write test.
775 config SYS_ALT_MEMTEST
776 bool "Alternative test"
778 Use a more complete alternative memory test.
780 config SYS_MEMTEST_START
781 hex "default start address for mtest"
784 This is the default start address for mtest for simple read/write
785 test. If no arguments are given to mtest, default address is used
788 config SYS_MEMTEST_END
789 hex "default end address for mtest"
792 This is the default end address for mtest for simple read/write
793 test. If no arguments are given to mtest, default address is used
802 Compute SHA1 checksum.
804 config SHA1SUM_VERIFY
806 depends on CMD_SHA1SUM
808 Add -v option to verify data against a SHA1 checksum.
811 bool "strings - display strings in memory"
813 This works similarly to the Unix 'strings' command except that it
814 works with a memory range. String of printable characters found
815 within the range are displayed. The minimum number of characters
816 for a sequence to be considered a string can be provided.
820 menu "Compression commands"
824 default y if CMD_BOOTI
827 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
832 default y if CMD_BOOTI
835 Support decompressing an LZ4 image from memory region.
839 default y if CMD_BOOTI
842 Uncompress a zip-compressed memory region.
846 select GZIP_COMPRESSED
848 Compress a memory region with zlib deflate method.
852 menu "Device access commands"
855 #depends on FLASH_CFI_DRIVER
858 ARM Ltd reference designs flash partition access
861 bool "adc - Access Analog to Digital Converters info and data"
865 Shows ADC device info and permit printing one-shot analog converted
866 data from a named Analog to Digital Converter.
871 depends on PARTITIONS
873 Read/modify/write the fields of Bootloader Control Block, usually
874 stored on the flash "misc" partition with its structure defined in:
875 https://android.googlesource.com/platform/bootable/recovery/+/master/
876 bootloader_message/include/bootloader_message/bootloader_message.h
878 Some real-life use-cases include (but are not limited to):
879 - Determine the "boot reason" (and act accordingly):
880 https://source.android.com/devices/bootloader/boot-reason
881 - Get/pass a list of commands from/to recovery:
882 https://android.googlesource.com/platform/bootable/recovery
883 - Inspect/dump the contents of the BCB fields
886 bool "bind/unbind - Bind or unbind a device to/from a driver"
889 Bind or unbind a device to/from a driver from the command line.
890 This is useful in situations where a device may be handled by several
891 drivers. For example, this can be used to bind a UDC to the usb ether
892 gadget driver from the command line.
895 bool "clk - Show clock frequencies"
898 Shows clock frequences by calling a sock_clk_dump() hook function.
899 This is depreated in favour of using the CLK uclass and accessing
900 clock values from associated drivers. However currently no command
904 bool "demo - Demonstration commands for driver model"
907 Provides a 'demo' command which can be used to play around with
908 driver model. To use this properly you will need to enable one or
909 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
910 Otherwise you will always get an empty list of devices. The demo
911 devices are defined in the sandbox device tree, so the easiest
912 option is to use sandbox and pass the -d point to sandbox's
919 Enables the command "dfu" which is used to have U-Boot create a DFU
920 class device via USB. This command requires that the "dfu_alt_info"
921 environment variable be set and define the alt settings to expose to
925 bool "dm - Access to driver model information"
928 Provides access to driver model data structures and information,
929 such as a list of devices, list of uclasses and the state of each
930 device (e.g. activated). This is not required for operation, but
931 can be useful to see the state of driver model for debugging or
935 bool "fastboot - Android fastboot support"
938 This enables the command "fastboot" which enables the Android
939 fastboot mode for the platform. Fastboot is a protocol for
940 downloading images, flashing and device control used on
941 Android devices. Fastboot requires either the network stack
942 enabled or support for acting as a USB device.
944 See doc/android/fastboot.rst for more information.
947 bool "flinfo, erase, protect"
949 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
952 flinfo - print FLASH memory information
954 protect - enable or disable FLASH write protection
963 config CMD_FPGA_LOADBP
964 bool "fpga loadbp - load partial bitstream (Xilinx only)"
967 Supports loading an FPGA device from a bitstream buffer containing
970 config CMD_FPGA_LOADFS
971 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
974 Supports loading an FPGA device from a FAT filesystem.
976 config CMD_FPGA_LOADMK
977 bool "fpga loadmk - load bitstream from image"
980 Supports loading an FPGA device from a image generated by mkimage.
982 config CMD_FPGA_LOADP
983 bool "fpga loadp - load partial bitstream"
986 Supports loading an FPGA device from a bitstream buffer containing
989 config CMD_FPGA_LOAD_SECURE
990 bool "fpga loads - loads secure bitstreams (Xilinx only)"
993 Enables the fpga loads command which is used to load secure
994 (authenticated or encrypted or both) bitstreams on to FPGA.
997 bool "fpgad - dump FPGA registers"
999 (legacy, needs conversion to driver model)
1000 Provides a way to dump FPGA registers by calling the board-specific
1001 fpga_get_reg() function. This functions similarly to the 'md'
1005 bool "fuse - support for the fuse subssystem"
1007 (deprecated - needs conversion to driver model)
1008 This allows reading, sensing, programming or overriding fuses
1009 which control the behaviour of the device. The command uses the
1018 bool "GPT (GUID Partition Table) command"
1019 select EFI_PARTITION
1020 select HAVE_BLOCK_DEVICE
1021 select PARTITION_UUIDS
1024 Enable the 'gpt' command to ready and write GPT style partition
1028 bool "GPT Random UUID generation"
1031 Enable the generation of partitions with random UUIDs if none
1034 config CMD_GPT_RENAME
1035 bool "GPT partition renaming commands"
1038 Enables the 'gpt' command to interchange names on two GPT
1039 partitions via the 'gpt swap' command or to rename single
1040 partitions via the 'rename' command.
1043 bool "ide - Support for IDE drivers"
1046 Provides an 'ide' command which allows accessing the IDE drive,
1047 reseting the IDE interface, printing the partition table and
1048 geting device info. It also enables the 'diskboot' command which
1049 permits booting from an IDE drive.
1052 bool "io - Support for performing I/O accesses"
1054 Provides an 'iod' command to display I/O space and an 'iow' command
1055 to write values to the I/O space. This can be useful for manually
1056 checking the state of devices during boot when debugging device
1060 bool "iotrace - Support for tracing I/O activity"
1062 Provides an 'iotrace' command which supports recording I/O reads and
1063 writes in a trace buffer in memory . It also maintains a checksum
1064 of the trace records (even if space is exhausted) so that the
1065 sequence of I/O accesses can be verified.
1067 When debugging drivers it is useful to see what I/O accesses were
1068 done and in what order.
1070 Even if the individual accesses are of little interest it can be
1071 useful to verify that the access pattern is consistent each time
1072 an operation is performed. In this case a checksum can be used to
1073 characterise the operation of a driver. The checksum can be compared
1074 across different runs of the operation to verify that the driver is
1077 In particular, when performing major refactoring of the driver, where
1078 the access pattern should not change, the checksum provides assurance
1079 that the refactoring work has not broken the driver.
1081 This works by sneaking into the io.h heder for an architecture and
1082 redirecting I/O accesses through iotrace's tracing mechanism.
1084 For now no commands are provided to examine the trace buffer. The
1085 format is fairly simple, so 'md' is a reasonable substitute.
1087 Note: The checksum feature is only useful for I/O regions where the
1088 contents do not change outside of software control. Where this is not
1089 suitable you can fall back to manually comparing the addresses. It
1090 might be useful to enhance tracing to only checksum the accesses and
1091 not the data read/written.
1101 bool "w1 - Support for Dallas 1-Wire protocol"
1103 Dallas 1-wire protocol support
1109 Load a binary file over serial line.
1115 Load an S-Record file over serial line
1119 bool "lsblk - list block drivers and devices"
1121 Print list of available block device drivers, and for each, the list
1122 of known block devices.
1127 MMC memory mapped support.
1131 config CMD_BKOPS_ENABLE
1132 bool "mmc bkops enable"
1136 Enable command for setting manual background operations handshake
1137 on a eMMC device. The feature is optionally available on eMMC devices
1138 conforming to standard >= 4.41.
1141 bool "Enable support for RPMB in the mmc command"
1142 depends on SUPPORT_EMMC_RPMB
1144 Enable the commands for reading, writing and programming the
1145 key for the Replay Protection Memory Block partition in eMMC.
1147 config CMD_MMC_SWRITE
1149 depends on MMC_WRITE
1152 Enable support for the "mmc swrite" command to write Android sparse
1161 Enable storage cloning over block devices, useful for
1162 initial flashing by external block device without network
1168 select MTD_PARTITIONS
1170 MTD commands support.
1174 default y if NAND_SUNXI
1175 depends on MTD_RAW_NAND
1180 config CMD_NAND_TRIMFFS
1181 bool "nand write.trimffs"
1182 default y if ARCH_SUNXI
1184 Allows one to skip empty pages when flashing something on a NAND.
1186 config CMD_NAND_LOCK_UNLOCK
1187 bool "nand lock/unlock"
1189 NAND locking support.
1191 config CMD_NAND_TORTURE
1194 NAND torture support.
1203 NVM Express device support
1206 bool "onenand - access to onenand device"
1209 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1210 various useful features. This command allows reading, writing,
1211 and erasing blocks. It allso provides a way to show and change
1212 bad blocks, and test the device.
1217 Enable the 'osd' command which allows to query information from and
1218 write text data to a on-screen display (OSD) device; a virtual device
1219 associated with a display capable of displaying a text overlay on the
1220 display it's associated with..
1224 select HAVE_BLOCK_DEVICE
1225 select PARTITION_UUIDS
1227 Read and display information about the partition table on
1231 bool "pci - Access PCI devices"
1233 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1234 used on some devices to allow the CPU to communicate with its
1235 peripherals. Sub-commands allow bus enumeration, displaying and
1236 changing configuration space and a few other features.
1239 bool "pinmux - show pins muxing"
1240 default y if PINCTRL
1242 Parse all available pin-controllers and show pins muxing. This
1243 is useful for debug purpoer to check the pin muxing and to know if
1244 a pin is configured as a GPIO or as an alternate function.
1249 Poweroff/Shutdown the system
1252 bool "read - Read binary data from a partition"
1254 Provides low-level access to the data in a partition.
1256 config CMD_REMOTEPROC
1258 depends on REMOTEPROC
1260 Support for Remote Processor control
1263 bool "sata - Access SATA subsystem"
1266 SATA (Serial Advanced Technology Attachment) is a serial bus
1267 standard for connecting to hard drives and other storage devices.
1268 This command provides information about attached devices and allows
1269 reading, writing and other operations.
1271 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1272 Attachment, where AT refers to an IBM AT (Advanced Technology)
1273 computer released in 1984.
1276 bool "saves - Save a file over serial in S-Record format"
1278 Provides a way to save a binary file using the Motorola S-Record
1279 format over the serial line.
1282 bool "scsi - Access to SCSI devices"
1285 This provides a 'scsi' command which provides access to SCSI (Small
1286 Computer System Interface) devices. The command provides a way to
1287 scan the bus, reset the bus, read and write data and get information
1291 bool "sdram - Print SDRAM configuration information"
1293 Provides information about attached SDRAM. This assumed that the
1294 SDRAM has an EEPROM with information that can be read using the
1295 I2C bus. This is only available on some boards.
1299 depends on DM_SPI_FLASH || SPI_FLASH
1300 default y if DM_SPI_FLASH
1305 bool "sf test - Allow testing of SPI flash"
1308 Provides a way to test that SPI flash is working correctly. The
1309 test is destructive, in that an area of SPI flash must be provided
1310 for the test to use. Performance information is also provided,
1311 measuring the performance of reading, writing and erasing in
1312 Mbps (Million Bits Per Second). This value should approximately
1313 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1314 everything is working properly.
1317 bool "sspi - Command to access spi device"
1320 SPI utility command.
1322 config DEFAULT_SPI_BUS
1323 int "default spi bus used by sspi command"
1327 config DEFAULT_SPI_MODE
1328 hex "default spi mode used by sspi command (see include/spi.h)"
1333 bool "tsi148 - Command to access tsi148 device"
1335 This provides various sub-commands to initialise and configure the
1336 Turndra tsi148 device. See the command help for full details.
1339 bool "Enable UFS - Universal Flash Subsystem commands"
1342 "This provides commands to initialise and configure universal flash
1346 bool "universe - Command to set up the Turndra Universe controller"
1348 This allows setting up the VMEbus provided by this controller.
1349 See the command help for full details.
1353 select HAVE_BLOCK_DEVICE
1359 select USB_FUNCTION_SDP
1361 Enables the command "sdp" which is used to have U-Boot emulating the
1362 Serial Download Protocol (SDP) via USB.
1366 depends on USB_FUNCTION_ROCKUSB
1368 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1369 read/write info, image to/from devices. This enable rockusb command
1370 support to communication with rockusb device. for more detail about
1371 this command, please read doc/README.rockusb.
1373 config CMD_USB_MASS_STORAGE
1374 bool "UMS usb mass storage"
1375 select USB_FUNCTION_MASS_STORAGE
1377 USB mass storage support
1380 bool "Xen para-virtualized block device"
1384 Xen para-virtualized block device support
1391 VirtIO block device support
1397 This provides commands to control the watchdog timer devices.
1403 Enable the command "axi" for accessing AXI (Advanced eXtensible
1404 Interface) busses, a on-chip interconnect specification for managing
1405 functional blocks in SoC designs, which is also often used in designs
1406 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1410 menu "Shell scripting commands"
1416 Echo args to console
1422 Return true/false on integer compare.
1428 Run script from memory
1434 Evaluate boolean and math expressions and store the result in an env
1436 Also supports loading the value at a memory location into a variable.
1437 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1441 menu "Android support commands"
1443 config CMD_AB_SELECT
1446 depends on ANDROID_AB
1448 On Android devices with more than one boot slot (multiple copies of
1449 the kernel and system images) this provides a command to select which
1450 slot should be used to boot from and register the boot attempt. This
1451 is used by the new A/B update model where one slot is updated in the
1452 background while running from the other slot.
1459 bool "Network commands"
1469 bootp - boot image via network using BOOTP/TFTP protocol
1473 depends on CMD_BOOTP
1475 Boot image via network using DHCP/TFTP protocol
1477 config BOOTP_BOOTPATH
1478 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1480 depends on CMD_BOOTP
1482 Even though the config is called BOOTP_BOOTPATH, it stores the
1483 path in the variable 'rootpath'.
1486 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1488 depends on CMD_BOOTP
1490 The primary DNS server is stored as 'dnsip'. If two servers are
1491 returned, you must set BOOTP_DNS2 to store that second server IP
1495 bool "Store 'dnsip2' from BOOTP/DHCP server"
1496 depends on BOOTP_DNS
1498 If a DHCP client requests the DNS server IP from a DHCP server,
1499 it is possible that more than one DNS serverip is offered to the
1500 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1501 server IP will be stored in the additional environment
1502 variable "dnsip2". The first DNS serverip is always
1503 stored in the variable "dnsip", when BOOTP_DNS is defined.
1505 config BOOTP_GATEWAY
1506 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1508 depends on CMD_BOOTP
1510 config BOOTP_HOSTNAME
1511 bool "Request & store 'hostname' from BOOTP/DHCP server"
1513 depends on CMD_BOOTP
1515 The name may or may not be qualified with the local domain name.
1517 config BOOTP_PREFER_SERVERIP
1518 bool "serverip variable takes precedent over DHCP server IP."
1519 depends on CMD_BOOTP
1521 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1523 With this option enabled, the 'serverip' variable in the environment
1524 takes precedence over DHCP server IP and will only be set by the DHCP
1525 server if not already set in the environment.
1527 config BOOTP_SUBNETMASK
1528 bool "Request & store 'netmask' from BOOTP/DHCP server"
1530 depends on CMD_BOOTP
1532 config BOOTP_NTPSERVER
1533 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1534 depends on CMD_BOOTP
1539 Selecting this will allow capturing all Ethernet packets and store
1540 them in physical memory in a PCAP formated file,
1541 later to be analyzed by PCAP reader application (IE. WireShark).
1544 bool "Send PXE client arch to BOOTP/DHCP server"
1546 depends on CMD_BOOTP && CMD_PXE
1548 Supported for ARM, ARM64, and x86 for now.
1550 config BOOTP_PXE_CLIENTARCH
1552 depends on BOOTP_PXE
1553 default 0x16 if ARM64
1557 config BOOTP_VCI_STRING
1559 depends on CMD_BOOTP
1560 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1561 default "U-Boot.armv8" if ARM64
1562 default "U-Boot.arm" if ARM
1569 tftpboot - boot image via network using TFTP protocol
1573 depends on CMD_TFTPBOOT
1575 TFTP put command, for uploading files to a server
1579 depends on CMD_TFTPBOOT
1581 Act as a TFTP server and boot the first received file
1583 config NET_TFTP_VARS
1584 bool "Control TFTP timeout and count through environment"
1585 depends on CMD_TFTPBOOT
1588 If set, allows controlling the TFTP timeout through the
1589 environment variable tftptimeout, and the TFTP maximum
1590 timeout count through the variable tftptimeoutcountmax.
1591 If unset, timeout and maximum are hard-defined as 1 second
1592 and 10 timouts per TFTP transfer.
1597 Boot image via network using RARP/TFTP protocol
1603 Boot image via network using NFS protocol.
1609 If set, allows 802.3(clause 22) MII Management functions interface access
1610 The management interface specified in Clause 22 provides
1611 a simple, two signal, serial interface to connect a
1612 Station Management entity and a managed PHY for providing access
1613 to management parameters and services.
1614 The interface is referred to as the MII management interface.
1620 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1621 The MDIO interface is orthogonal to the MII interface and extends
1622 it by adding access to more registers through indirect addressing.
1627 Send ICMP ECHO_REQUEST to network host
1632 Perform CDP network configuration
1637 Synchronize RTC via network
1642 Lookup the IP of a hostname
1644 config CMD_LINK_LOCAL
1648 Acquire a network IP address using the link-local protocol
1655 Allow control of L2 Ethernet switch commands. These are supported
1656 by the vsc9953 Ethernet driver at present. Sub-commands allow
1657 operations such as enabling / disabling a port and
1658 viewing/maintaining the filtering database (FDB)
1664 Boot image via network using PXE protocol
1669 Wait for wake-on-lan Magic Packet
1673 menu "Misc commands"
1676 bool "Enable 'bmp' command"
1677 depends on LCD || DM_VIDEO || VIDEO
1679 This provides a way to obtain information about a BMP-format image
1680 and to display it. BMP (which presumably stands for BitMaP) is a
1681 file format defined by Microsoft which supports images of various
1682 depths, formats and compression methods. Headers on the file
1683 determine the formats used. This command can be used by first loading
1684 the image into RAM, then using this command to look at it or display
1687 config CMD_BOOTCOUNT
1689 depends on BOOTCOUNT_LIMIT
1691 Enable the bootcount command, which allows interrogation and
1692 reset of the bootcounter.
1695 bool "Enable board-specific commands"
1697 (deprecated: instead, please define a Kconfig option for each command)
1699 Some boards have board-specific commands which are only enabled
1700 during developemnt and need to be turned off for production. This
1701 option provides a way to control this. The commands that are enabled
1702 vary depending on the board.
1704 config CMD_BLOCK_CACHE
1705 bool "blkcache - control and stats for block cache"
1706 depends on BLOCK_CACHE
1707 default y if BLOCK_CACHE
1709 Enable the blkcache command, which can be used to control the
1710 operation of the cache functions.
1711 This is most useful when fine-tuning the operation of the cache
1712 during development, but also allows the cache to be disabled when
1713 it might hurt performance (e.g. when using the ums command).
1720 Enable the 'button' command which allows to get the status of
1721 buttons supported by the board. The buttonss can be listed with
1722 'button list' and state can be known with 'button <label>'.
1723 Any button drivers can be controlled with this command, e.g.
1727 bool "icache or dcache"
1729 Enable the "icache" and "dcache" commands
1731 config CMD_CONITRACE
1732 bool "conitrace - trace console input codes"
1734 Enable the 'conitrace' command which displays the codes received
1735 from the console input as hexadecimal numbers.
1738 bool "Enable clear screen command 'cls'"
1739 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1742 Enable the 'cls' command which clears the screen contents
1743 on video frame buffer.
1746 bool "efidebug - display/configure UEFI environment"
1747 depends on EFI_LOADER
1748 select EFI_DEVICE_PATH_TO_TEXT
1751 Enable the 'efidebug' command which provides a subset of UEFI
1752 shell utility with simplified functionality. It will be useful
1753 particularly for managing boot parameters as well as examining
1754 various EFI status for debugging.
1756 config CMD_EXCEPTION
1757 bool "exception - raise exception"
1758 depends on ARM || RISCV || X86
1760 Enable the 'exception' command which allows to raise an exception.
1767 Enable the 'led' command which allows for control of LEDs supported
1768 by the board. The LEDs can be listed with 'led list' and controlled
1769 with led on/off/togle/blink. Any LED drivers can be controlled with
1770 this command, e.g. led_gpio.
1777 Enable the 'date' command for getting/setting the time/date in RTC
1784 Enable the 'rtc' command for low-level access to RTC devices.
1789 Run commands and summarize execution time.
1792 bool "gettime - read elapsed time"
1794 Enable the 'gettime' command which reads the elapsed time since
1795 U-Boot started running. This shows the time in seconds and
1796 milliseconds. See also the 'bootstage' command which provides more
1797 flexibility for boot timing.
1804 Print bytes from the hardware random number generator.
1806 # TODO: rename to CMD_SLEEP
1811 Delay execution for some time
1814 bool "support for multiprocessor"
1816 This provides an option to brinup
1817 different processors in multiprocessor
1823 Access the system timer.
1829 This provides basic access to the U-Boot's sound support. The main
1830 feature is to play a beep.
1832 sound init - set up sound system
1833 sound play - play a sound
1839 Boot image via local extlinux.conf file
1845 This provides access to the QEMU firmware interface. The main
1846 feature is to allow easy loading of files passed to qemu-system
1847 via -kernel / -initrd
1849 source "cmd/mvebu/Kconfig"
1852 bool "terminal - provides a way to attach a serial terminal"
1854 Provides a 'cu'-like serial terminal command. This can be used to
1855 access other serial ports from the system console. The terminal
1856 is very simple with no special processing of characters. As with
1857 cu, you can press ~. (tilde followed by period) to exit.
1860 bool "uuid, guid - generation of unique IDs"
1863 This enables two commands:
1865 uuid - generate random Universally Unique Identifier
1866 guid - generate Globally Unique Identifier based on random UUID
1868 The two commands are very similar except for the endianness of the
1873 source "cmd/ti/Kconfig"
1875 config CMD_BOOTSTAGE
1876 bool "Enable the 'bootstage' command"
1877 depends on BOOTSTAGE
1879 Add a 'bootstage' command which supports printing a report
1880 and un/stashing of bootstage data.
1882 menu "Power commands"
1884 bool "Enable Driver Model PMIC command"
1887 This is the pmic command, based on a driver model pmic's API.
1888 Command features are unchanged:
1889 - list - list pmic devices
1890 - pmic dev <id> - show or [set] operating pmic device (NEW)
1891 - pmic dump - dump registers
1892 - pmic read address - read byte of register at address
1893 - pmic write address - write byte to register at address
1894 The only one change for this command is 'dev' subcommand.
1896 config CMD_REGULATOR
1897 bool "Enable Driver Model REGULATOR command"
1898 depends on DM_REGULATOR
1900 This command is based on driver model regulator's API.
1901 User interface features:
1902 - list - list regulator devices
1903 - regulator dev <id> - show or [set] operating regulator device
1904 - regulator info - print constraints info
1905 - regulator status - print operating status
1906 - regulator value <val] <-f> - print/[set] voltage value [uV]
1907 - regulator current <val> - print/[set] current value [uA]
1908 - regulator mode <id> - print/[set] operating mode id
1909 - regulator enable - enable the regulator output
1910 - regulator disable - disable the regulator output
1912 The '-f' (force) option can be used for set the value which exceeds
1913 the limits, which are found in device-tree and are kept in regulator's
1914 uclass platdata structure.
1918 menu "Security commands"
1920 bool "Enable the 'aes' command"
1923 This provides a means to encrypt and decrypt data using the AES
1924 (Advanced Encryption Standard). This algorithm uses a symetric key
1925 and is widely used as a streaming cipher. Different key lengths are
1926 supported by the algorithm but this command only supports 128 bits
1930 bool "Enable the 'blob' command"
1932 This is used with the Freescale secure boot mechanism.
1934 Freescale's SEC block has built-in Blob Protocol which provides
1935 a method for protecting user-defined data across system power
1936 cycles. SEC block protects data in a data structure called a Blob,
1937 which provides both confidentiality and integrity protection.
1939 Encapsulating data as a blob
1940 Each time that the Blob Protocol is used to protect data, a
1941 different randomly generated key is used to encrypt the data.
1942 This random key is itself encrypted using a key which is derived
1943 from SoC's non-volatile secret key and a 16 bit Key identifier.
1944 The resulting encrypted key along with encrypted data is called a
1945 blob. The non-volatile secure key is available for use only during
1948 During decapsulation, the reverse process is performed to get back
1952 blob enc - encapsulating data as a cryptgraphic blob
1953 blob dec - decapsulating cryptgraphic blob to get the data
1957 blob enc src dst len km
1959 Encapsulate and create blob of data $len bytes long
1960 at address $src and store the result at address $dst.
1961 $km is the 16 byte key modifier is also required for
1962 generation/use as key for cryptographic operation. Key
1963 modifier should be 16 byte long.
1965 blob dec src dst len km
1967 Decapsulate the blob of data at address $src and
1968 store result of $len byte at addr $dst.
1969 $km is the 16 byte key modifier is also required for
1970 generation/use as key for cryptographic operation. Key
1971 modifier should be 16 byte long.
1974 bool "Support 'hash' command"
1977 This provides a way to hash data in memory using various supported
1978 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1979 saved to memory or to an environment variable. It is also possible
1980 to verify a hash against data in memory.
1983 bool "Support the 'hvc' command"
1984 depends on ARM_SMCCC
1986 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1987 development and testing.
1990 bool "Support the 'smc' command"
1991 depends on ARM_SMCCC
1993 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1994 development and testing.
2000 Add -v option to verify data against a hash.
2010 bool "Enable the 'tpm' command"
2011 depends on TPM_V1 || TPM_V2
2012 select CMD_TPM_V1 if TPM_V1
2013 select CMD_TPM_V2 if TPM_V2
2015 This provides a means to talk to a TPM from the command line. A wide
2016 range of commands if provided - see 'tpm help' for details. The
2017 command requires a suitable TPM on your board and the correct driver
2023 bool "Enable the 'tpm test' command"
2026 This provides a a series of tests to confirm that the TPMv1.x is
2027 working correctly. The tests cover initialisation, non-volatile RAM,
2028 extend, global lock and checking that timing is within expectations.
2029 The tests pass correctly on Infineon TPMs but may need to be adjusted
2036 menu "Firmware commands"
2038 bool "Enable crosec command"
2042 Enable command-line access to the Chrome OS EC (Embedded
2043 Controller). This provides the 'crosec' command which has
2044 a number of sub-commands for performing EC tasks such as
2045 updating its flash, accessing a small saved context area
2046 and talking to the I2C bus behind the EC (if there is one).
2049 menu "Filesystem commands"
2051 bool "Enable the 'btrsubvol' command"
2054 This enables the 'btrsubvol' command to list subvolumes
2055 of a BTRFS filesystem. There are no special commands for
2056 listing BTRFS directories or loading BTRFS files - this
2057 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2058 when BTRFS is enabled (see FS_BTRFS).
2061 bool "Enable the 'cbfs' command"
2064 Define this to enable support for reading from a Coreboot
2065 filesystem. This is a ROM-based filesystem used for accessing files
2066 on systems that use coreboot as the first boot-loader and then load
2067 U-Boot to actually boot the Operating System. Available commands are
2068 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2071 bool "Enable the 'cramfs' command"
2072 depends on FS_CRAMFS
2074 This provides commands for dealing with CRAMFS (Compressed ROM
2075 filesystem). CRAMFS is useful when space is tight since files are
2076 compressed. Two commands are provided:
2078 cramfsls - lists files in a cramfs image
2079 cramfsload - loads a file from a cramfs image
2082 bool "ext2 command support"
2085 Enables EXT2 FS command
2088 bool "ext4 command support"
2091 Enables EXT4 FS command
2093 config CMD_EXT4_WRITE
2095 bool "ext4 write command support"
2098 Enables EXT4 FS write command
2101 bool "FAT command support"
2104 Support for the FAT fs
2107 bool "SquashFS command support"
2110 Enables SquashFS filesystem commands (e.g. load, ls).
2112 config CMD_FS_GENERIC
2113 bool "filesystem commands"
2115 Enables filesystem commands (e.g. load, ls) that work for multiple
2119 bool "fsuuid command"
2121 Enables fsuuid command for filesystem UUID.
2124 bool "jffs2 command"
2127 Enables commands to support the JFFS2 (Journalling Flash File System
2128 version 2) filesystem. This enables fsload, ls and fsinfo which
2129 provide the ability to load files, list directories and obtain
2130 filesystem information.
2133 bool "MTD partition support"
2136 MTD partitioning tool support.
2137 It is strongly encouraged to avoid using this command
2138 anymore along with 'sf', 'nand', 'onenand'. One can still
2139 declare the partitions in the mtdparts environment variable
2140 but better use the MTD stack and the 'mtd' command instead.
2142 config CMD_MTDPARTS_SPREAD
2143 bool "Padd partition size to take account of bad blocks"
2144 depends on CMD_MTDPARTS
2146 This enables the 'spread' sub-command of the mtdparts command.
2147 This command will modify the existing mtdparts variable by increasing
2148 the size of the partitions such that 1) each partition's net size is
2149 at least as large as the size specified in the mtdparts variable and
2150 2) each partition starts on a good block.
2152 config CMD_MTDPARTS_SHOW_NET_SIZES
2153 bool "Show net size (w/o bad blocks) of partitions"
2154 depends on CMD_MTDPARTS
2156 Adds two columns to the printed partition table showing the
2157 effective usable size of a partition, if bad blocks are taken
2160 config MTDIDS_DEFAULT
2161 string "Default MTD IDs"
2162 depends on MTD || SPI_FLASH
2164 Defines a default MTD IDs list for use with MTD partitions in the
2165 Linux MTD command line partitions format.
2167 config MTDPARTS_DEFAULT
2168 string "Default MTD partition scheme"
2169 depends on MTD || SPI_FLASH
2171 Defines a default MTD partitioning scheme in the Linux MTD command
2172 line partitions format
2175 bool "reiser - Access to reiserfs filesystems"
2177 This provides two commands which operate on a resierfs filesystem,
2178 commonly used some years ago:
2180 reiserls - list files
2181 reiserload - load a file
2184 bool "yaffs2 - Access of YAFFS2 filesystem"
2188 This provides commands for accessing a YAFFS2 filesystem. Yet
2189 Another Flash Filesystem 2 is a filesystem designed specifically
2190 for NAND flash. It incorporates bad-block management and ensures
2191 that device writes are sequential regardless of filesystem
2195 bool "zfs - Access of ZFS filesystem"
2197 This provides commands to accessing a ZFS filesystem, commonly used
2198 on Solaris systems. Two sub-commands are provided:
2200 zfsls - list files in a directory
2201 zfsload - load a file
2203 See doc/README.zfs for more details.
2207 menu "Debug commands"
2212 The bedbug (emBEDded deBUGger) command provides debugging features
2213 for some PowerPC processors. For details please see the
2214 documentation in doc/README.bedbug.
2217 bool "diag - Board diagnostics"
2219 This command provides access to board diagnostic tests. These are
2220 called Power-on Self Tests (POST). The command allows listing of
2221 available tests and running either all the tests, or specific tests
2225 bool "irq - Show information about interrupts"
2226 depends on !ARM && !MIPS && !SH
2228 This enables two commands:
2230 interrupts - enable or disable interrupts
2231 irqinfo - print device-specific interrupt information
2234 bool "kgdb - Allow debugging of U-Boot with gdb"
2237 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2238 over a serial link for debugging purposes. This allows
2239 single-stepping, inspecting variables, etc. This is supported only
2240 on PowerPC at present.
2243 bool "log - Generation, control and access to logging"
2246 This provides access to logging features. It allows the output of
2247 log data to be controlled to a limited extent (setting up the default
2248 maximum log level for emitting of records). It also provides access
2249 to a command used for testing the log system.
2252 bool "trace - Support tracing of function calls and timing"
2254 Enables a command to control using of function tracing within
2255 U-Boot. This allows recording of call traces including timing
2256 information. The command can write data to memory for exporting
2257 for analysis (e.g. using bootchart). See doc/README.trace for full
2261 bool "avb - Android Verified Boot 2.0 operations"
2262 depends on AVB_VERIFY
2265 Enables a "avb" command to perform verification of partitions using
2266 Android Verified Boot 2.0 functionality. It includes such subcommands:
2267 avb init - initialize avb2 subsystem
2268 avb read_rb - read rollback index
2269 avb write_rb - write rollback index
2270 avb is_unlocked - check device lock state
2271 avb get_uuid - read and print uuid of a partition
2272 avb read_part - read data from partition
2273 avb read_part_hex - read data from partition and output to stdout
2274 avb write_part - write data to partition
2275 avb verify - run full verification chain
2279 tristate "Enable UBI - Unsorted block images commands"
2282 UBI is a software layer above MTD layer which admits use of LVM-like
2283 logical volumes on top of MTD devices, hides some complexities of
2284 flash chips like wear and bad blocks and provides some other useful
2285 capabilities. Please, consult the MTD web site for more details
2286 (www.linux-mtd.infradead.org). Activate this option if you want
2287 to use U-Boot UBI commands.
2288 It is also strongly encouraged to also enable CONFIG_MTD to get full
2291 config CMD_UBI_RENAME
2292 bool "Enable rename"
2296 Enable a "ubi" command to rename ubi volume:
2297 ubi rename <oldname> <newname>
2300 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2302 default y if CMD_UBI
2305 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob