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.
782 config SYS_ALT_MEMTEST_BITFLIP
786 The alternative memory test includes bitflip test since 2020.07.
787 The bitflip test significantly increases the overall test time.
788 Bitflip test can optionally be disabled here.
792 config SYS_MEMTEST_START
793 hex "default start address for mtest"
796 This is the default start address for mtest for simple read/write
797 test. If no arguments are given to mtest, default address is used
800 config SYS_MEMTEST_END
801 hex "default end address for mtest"
804 This is the default end address for mtest for simple read/write
805 test. If no arguments are given to mtest, default address is used
814 Compute SHA1 checksum.
816 config SHA1SUM_VERIFY
818 depends on CMD_SHA1SUM
820 Add -v option to verify data against a SHA1 checksum.
823 bool "strings - display strings in memory"
825 This works similarly to the Unix 'strings' command except that it
826 works with a memory range. String of printable characters found
827 within the range are displayed. The minimum number of characters
828 for a sequence to be considered a string can be provided.
832 menu "Compression commands"
836 default y if CMD_BOOTI
839 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
844 default y if CMD_BOOTI
847 Support decompressing an LZ4 image from memory region.
851 default y if CMD_BOOTI
854 Uncompress a zip-compressed memory region.
858 select GZIP_COMPRESSED
860 Compress a memory region with zlib deflate method.
864 menu "Device access commands"
867 #depends on FLASH_CFI_DRIVER
870 ARM Ltd reference designs flash partition access
873 bool "adc - Access Analog to Digital Converters info and data"
875 depends on DM_REGULATOR
877 Shows ADC device info and permit printing one-shot analog converted
878 data from a named Analog to Digital Converter.
883 depends on PARTITIONS
885 Read/modify/write the fields of Bootloader Control Block, usually
886 stored on the flash "misc" partition with its structure defined in:
887 https://android.googlesource.com/platform/bootable/recovery/+/master/
888 bootloader_message/include/bootloader_message/bootloader_message.h
890 Some real-life use-cases include (but are not limited to):
891 - Determine the "boot reason" (and act accordingly):
892 https://source.android.com/devices/bootloader/boot-reason
893 - Get/pass a list of commands from/to recovery:
894 https://android.googlesource.com/platform/bootable/recovery
895 - Inspect/dump the contents of the BCB fields
898 bool "bind/unbind - Bind or unbind a device to/from a driver"
901 Bind or unbind a device to/from a driver from the command line.
902 This is useful in situations where a device may be handled by several
903 drivers. For example, this can be used to bind a UDC to the usb ether
904 gadget driver from the command line.
907 bool "clk - Show clock frequencies"
910 Shows clock frequences by calling a sock_clk_dump() hook function.
911 This is depreated in favour of using the CLK uclass and accessing
912 clock values from associated drivers. However currently no command
916 bool "demo - Demonstration commands for driver model"
919 Provides a 'demo' command which can be used to play around with
920 driver model. To use this properly you will need to enable one or
921 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
922 Otherwise you will always get an empty list of devices. The demo
923 devices are defined in the sandbox device tree, so the easiest
924 option is to use sandbox and pass the -d point to sandbox's
931 Enables the command "dfu" which is used to have U-Boot create a DFU
932 class device via USB. This command requires that the "dfu_alt_info"
933 environment variable be set and define the alt settings to expose to
937 bool "dm - Access to driver model information"
940 Provides access to driver model data structures and information,
941 such as a list of devices, list of uclasses and the state of each
942 device (e.g. activated). This is not required for operation, but
943 can be useful to see the state of driver model for debugging or
947 bool "fastboot - Android fastboot support"
950 This enables the command "fastboot" which enables the Android
951 fastboot mode for the platform. Fastboot is a protocol for
952 downloading images, flashing and device control used on
953 Android devices. Fastboot requires either the network stack
954 enabled or support for acting as a USB device.
956 See doc/android/fastboot.rst for more information.
959 bool "flinfo, erase, protect"
961 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
964 flinfo - print FLASH memory information
966 protect - enable or disable FLASH write protection
975 config CMD_FPGA_LOADBP
976 bool "fpga loadbp - load partial bitstream (Xilinx only)"
979 Supports loading an FPGA device from a bitstream buffer containing
982 config CMD_FPGA_LOADFS
983 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
986 Supports loading an FPGA device from a FAT filesystem.
988 config CMD_FPGA_LOADMK
989 bool "fpga loadmk - load bitstream from image"
992 Supports loading an FPGA device from a image generated by mkimage.
994 config CMD_FPGA_LOADP
995 bool "fpga loadp - load partial bitstream"
998 Supports loading an FPGA device from a bitstream buffer containing
1001 config CMD_FPGA_LOAD_SECURE
1002 bool "fpga loads - loads secure bitstreams (Xilinx only)"
1005 Enables the fpga loads command which is used to load secure
1006 (authenticated or encrypted or both) bitstreams on to FPGA.
1009 bool "fpgad - dump FPGA registers"
1011 (legacy, needs conversion to driver model)
1012 Provides a way to dump FPGA registers by calling the board-specific
1013 fpga_get_reg() function. This functions similarly to the 'md'
1017 bool "fuse - support for the fuse subssystem"
1019 (deprecated - needs conversion to driver model)
1020 This allows reading, sensing, programming or overriding fuses
1021 which control the behaviour of the device. The command uses the
1030 bool "GPT (GUID Partition Table) command"
1031 select EFI_PARTITION
1032 select HAVE_BLOCK_DEVICE
1033 select PARTITION_UUIDS
1036 Enable the 'gpt' command to ready and write GPT style partition
1040 bool "GPT Random UUID generation"
1043 Enable the generation of partitions with random UUIDs if none
1046 config CMD_GPT_RENAME
1047 bool "GPT partition renaming commands"
1050 Enables the 'gpt' command to interchange names on two GPT
1051 partitions via the 'gpt swap' command or to rename single
1052 partitions via the 'rename' command.
1055 bool "ide - Support for IDE drivers"
1058 Provides an 'ide' command which allows accessing the IDE drive,
1059 reseting the IDE interface, printing the partition table and
1060 geting device info. It also enables the 'diskboot' command which
1061 permits booting from an IDE drive.
1064 bool "io - Support for performing I/O accesses"
1066 Provides an 'iod' command to display I/O space and an 'iow' command
1067 to write values to the I/O space. This can be useful for manually
1068 checking the state of devices during boot when debugging device
1072 bool "iotrace - Support for tracing I/O activity"
1074 Provides an 'iotrace' command which supports recording I/O reads and
1075 writes in a trace buffer in memory . It also maintains a checksum
1076 of the trace records (even if space is exhausted) so that the
1077 sequence of I/O accesses can be verified.
1079 When debugging drivers it is useful to see what I/O accesses were
1080 done and in what order.
1082 Even if the individual accesses are of little interest it can be
1083 useful to verify that the access pattern is consistent each time
1084 an operation is performed. In this case a checksum can be used to
1085 characterise the operation of a driver. The checksum can be compared
1086 across different runs of the operation to verify that the driver is
1089 In particular, when performing major refactoring of the driver, where
1090 the access pattern should not change, the checksum provides assurance
1091 that the refactoring work has not broken the driver.
1093 This works by sneaking into the io.h heder for an architecture and
1094 redirecting I/O accesses through iotrace's tracing mechanism.
1096 For now no commands are provided to examine the trace buffer. The
1097 format is fairly simple, so 'md' is a reasonable substitute.
1099 Note: The checksum feature is only useful for I/O regions where the
1100 contents do not change outside of software control. Where this is not
1101 suitable you can fall back to manually comparing the addresses. It
1102 might be useful to enhance tracing to only checksum the accesses and
1103 not the data read/written.
1113 bool "w1 - Support for Dallas 1-Wire protocol"
1115 Dallas 1-wire protocol support
1121 Load a binary file over serial line.
1127 Load an S-Record file over serial line
1131 bool "lsblk - list block drivers and devices"
1133 Print list of available block device drivers, and for each, the list
1134 of known block devices.
1139 MMC memory mapped support.
1143 config CMD_BKOPS_ENABLE
1144 bool "mmc bkops enable"
1148 Enable command for setting manual background operations handshake
1149 on a eMMC device. The feature is optionally available on eMMC devices
1150 conforming to standard >= 4.41.
1153 bool "Enable support for RPMB in the mmc command"
1154 depends on SUPPORT_EMMC_RPMB
1156 Enable the commands for reading, writing and programming the
1157 key for the Replay Protection Memory Block partition in eMMC.
1159 config CMD_MMC_SWRITE
1161 depends on MMC_WRITE
1164 Enable support for the "mmc swrite" command to write Android sparse
1173 Enable storage cloning over block devices, useful for
1174 initial flashing by external block device without network
1180 select MTD_PARTITIONS
1182 MTD commands support.
1186 default y if NAND_SUNXI
1187 depends on MTD_RAW_NAND
1192 config CMD_NAND_TRIMFFS
1193 bool "nand write.trimffs"
1194 default y if ARCH_SUNXI
1196 Allows one to skip empty pages when flashing something on a NAND.
1198 config CMD_NAND_LOCK_UNLOCK
1199 bool "nand lock/unlock"
1201 NAND locking support.
1203 config CMD_NAND_TORTURE
1206 NAND torture support.
1215 NVM Express device support
1218 bool "onenand - access to onenand device"
1221 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1222 various useful features. This command allows reading, writing,
1223 and erasing blocks. It allso provides a way to show and change
1224 bad blocks, and test the device.
1229 Enable the 'osd' command which allows to query information from and
1230 write text data to a on-screen display (OSD) device; a virtual device
1231 associated with a display capable of displaying a text overlay on the
1232 display it's associated with..
1236 select HAVE_BLOCK_DEVICE
1237 select PARTITION_UUIDS
1239 Read and display information about the partition table on
1243 bool "pci - Access PCI devices"
1245 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1246 used on some devices to allow the CPU to communicate with its
1247 peripherals. Sub-commands allow bus enumeration, displaying and
1248 changing configuration space and a few other features.
1251 bool "pinmux - show pins muxing"
1252 default y if PINCTRL
1254 Parse all available pin-controllers and show pins muxing. This
1255 is useful for debug purpoer to check the pin muxing and to know if
1256 a pin is configured as a GPIO or as an alternate function.
1261 Poweroff/Shutdown the system
1264 bool "read - Read binary data from a partition"
1266 Provides low-level access to the data in a partition.
1268 config CMD_REMOTEPROC
1270 depends on REMOTEPROC
1272 Support for Remote Processor control
1275 bool "sata - Access SATA subsystem"
1278 SATA (Serial Advanced Technology Attachment) is a serial bus
1279 standard for connecting to hard drives and other storage devices.
1280 This command provides information about attached devices and allows
1281 reading, writing and other operations.
1283 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1284 Attachment, where AT refers to an IBM AT (Advanced Technology)
1285 computer released in 1984.
1288 bool "saves - Save a file over serial in S-Record format"
1290 Provides a way to save a binary file using the Motorola S-Record
1291 format over the serial line.
1294 bool "scsi - Access to SCSI devices"
1297 This provides a 'scsi' command which provides access to SCSI (Small
1298 Computer System Interface) devices. The command provides a way to
1299 scan the bus, reset the bus, read and write data and get information
1303 bool "sdram - Print SDRAM configuration information"
1305 Provides information about attached SDRAM. This assumed that the
1306 SDRAM has an EEPROM with information that can be read using the
1307 I2C bus. This is only available on some boards.
1311 depends on DM_SPI_FLASH || SPI_FLASH
1312 default y if DM_SPI_FLASH
1317 bool "sf test - Allow testing of SPI flash"
1320 Provides a way to test that SPI flash is working correctly. The
1321 test is destructive, in that an area of SPI flash must be provided
1322 for the test to use. Performance information is also provided,
1323 measuring the performance of reading, writing and erasing in
1324 Mbps (Million Bits Per Second). This value should approximately
1325 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1326 everything is working properly.
1329 bool "sspi - Command to access spi device"
1332 SPI utility command.
1334 config DEFAULT_SPI_BUS
1335 int "default spi bus used by sspi command"
1339 config DEFAULT_SPI_MODE
1340 hex "default spi mode used by sspi command (see include/spi.h)"
1345 bool "tsi148 - Command to access tsi148 device"
1347 This provides various sub-commands to initialise and configure the
1348 Turndra tsi148 device. See the command help for full details.
1351 bool "Enable UFS - Universal Flash Subsystem commands"
1354 "This provides commands to initialise and configure universal flash
1358 bool "universe - Command to set up the Turndra Universe controller"
1360 This allows setting up the VMEbus provided by this controller.
1361 See the command help for full details.
1365 select HAVE_BLOCK_DEVICE
1371 select USB_FUNCTION_SDP
1373 Enables the command "sdp" which is used to have U-Boot emulating the
1374 Serial Download Protocol (SDP) via USB.
1378 depends on USB_FUNCTION_ROCKUSB
1380 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1381 read/write info, image to/from devices. This enable rockusb command
1382 support to communication with rockusb device. for more detail about
1383 this command, please read doc/README.rockusb.
1385 config CMD_USB_MASS_STORAGE
1386 bool "UMS usb mass storage"
1387 select USB_FUNCTION_MASS_STORAGE
1389 USB mass storage support
1392 bool "Xen para-virtualized block device"
1396 Xen para-virtualized block device support
1403 VirtIO block device support
1409 This provides commands to control the watchdog timer devices.
1415 Enable the command "axi" for accessing AXI (Advanced eXtensible
1416 Interface) busses, a on-chip interconnect specification for managing
1417 functional blocks in SoC designs, which is also often used in designs
1418 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1422 menu "Shell scripting commands"
1428 Echo args to console
1434 Return true/false on integer compare.
1440 Run script from memory
1446 Evaluate boolean and math expressions and store the result in an env
1448 Also supports loading the value at a memory location into a variable.
1449 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1453 menu "Android support commands"
1455 config CMD_AB_SELECT
1458 depends on ANDROID_AB
1460 On Android devices with more than one boot slot (multiple copies of
1461 the kernel and system images) this provides a command to select which
1462 slot should be used to boot from and register the boot attempt. This
1463 is used by the new A/B update model where one slot is updated in the
1464 background while running from the other slot.
1471 bool "Network commands"
1481 bootp - boot image via network using BOOTP/TFTP protocol
1485 depends on CMD_BOOTP
1487 Boot image via network using DHCP/TFTP protocol
1489 config BOOTP_BOOTPATH
1490 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1492 depends on CMD_BOOTP
1494 Even though the config is called BOOTP_BOOTPATH, it stores the
1495 path in the variable 'rootpath'.
1498 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1500 depends on CMD_BOOTP
1502 The primary DNS server is stored as 'dnsip'. If two servers are
1503 returned, you must set BOOTP_DNS2 to store that second server IP
1507 bool "Store 'dnsip2' from BOOTP/DHCP server"
1508 depends on BOOTP_DNS
1510 If a DHCP client requests the DNS server IP from a DHCP server,
1511 it is possible that more than one DNS serverip is offered to the
1512 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1513 server IP will be stored in the additional environment
1514 variable "dnsip2". The first DNS serverip is always
1515 stored in the variable "dnsip", when BOOTP_DNS is defined.
1517 config BOOTP_GATEWAY
1518 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1520 depends on CMD_BOOTP
1522 config BOOTP_HOSTNAME
1523 bool "Request & store 'hostname' from BOOTP/DHCP server"
1525 depends on CMD_BOOTP
1527 The name may or may not be qualified with the local domain name.
1529 config BOOTP_PREFER_SERVERIP
1530 bool "serverip variable takes precedent over DHCP server IP."
1531 depends on CMD_BOOTP
1533 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1535 With this option enabled, the 'serverip' variable in the environment
1536 takes precedence over DHCP server IP and will only be set by the DHCP
1537 server if not already set in the environment.
1539 config BOOTP_SUBNETMASK
1540 bool "Request & store 'netmask' from BOOTP/DHCP server"
1542 depends on CMD_BOOTP
1544 config BOOTP_NTPSERVER
1545 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1546 depends on CMD_BOOTP
1551 Selecting this will allow capturing all Ethernet packets and store
1552 them in physical memory in a PCAP formated file,
1553 later to be analyzed by PCAP reader application (IE. WireShark).
1556 bool "Send PXE client arch to BOOTP/DHCP server"
1558 depends on CMD_BOOTP && CMD_PXE
1560 Supported for ARM, ARM64, and x86 for now.
1562 config BOOTP_PXE_CLIENTARCH
1564 depends on BOOTP_PXE
1565 default 0x16 if ARM64
1569 config BOOTP_VCI_STRING
1571 depends on CMD_BOOTP
1572 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1573 default "U-Boot.armv8" if ARM64
1574 default "U-Boot.arm" if ARM
1581 tftpboot - boot image via network using TFTP protocol
1585 depends on CMD_TFTPBOOT
1587 TFTP put command, for uploading files to a server
1591 depends on CMD_TFTPBOOT
1593 Act as a TFTP server and boot the first received file
1595 config NET_TFTP_VARS
1596 bool "Control TFTP timeout and count through environment"
1597 depends on CMD_TFTPBOOT
1600 If set, allows controlling the TFTP timeout through the
1601 environment variable tftptimeout, and the TFTP maximum
1602 timeout count through the variable tftptimeoutcountmax.
1603 If unset, timeout and maximum are hard-defined as 1 second
1604 and 10 timouts per TFTP transfer.
1609 Boot image via network using RARP/TFTP protocol
1615 Boot image via network using NFS protocol.
1621 If set, allows 802.3(clause 22) MII Management functions interface access
1622 The management interface specified in Clause 22 provides
1623 a simple, two signal, serial interface to connect a
1624 Station Management entity and a managed PHY for providing access
1625 to management parameters and services.
1626 The interface is referred to as the MII management interface.
1632 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1633 The MDIO interface is orthogonal to the MII interface and extends
1634 it by adding access to more registers through indirect addressing.
1639 Send ICMP ECHO_REQUEST to network host
1644 Perform CDP network configuration
1650 Synchronize RTC via network
1655 Lookup the IP of a hostname
1657 config CMD_LINK_LOCAL
1661 Acquire a network IP address using the link-local protocol
1668 Allow control of L2 Ethernet switch commands. These are supported
1669 by the vsc9953 Ethernet driver at present. Sub-commands allow
1670 operations such as enabling / disabling a port and
1671 viewing/maintaining the filtering database (FDB)
1677 Boot image via network using PXE protocol
1682 Wait for wake-on-lan Magic Packet
1686 menu "Misc commands"
1689 bool "Enable 'bmp' command"
1690 depends on LCD || DM_VIDEO || VIDEO
1692 This provides a way to obtain information about a BMP-format image
1693 and to display it. BMP (which presumably stands for BitMaP) is a
1694 file format defined by Microsoft which supports images of various
1695 depths, formats and compression methods. Headers on the file
1696 determine the formats used. This command can be used by first loading
1697 the image into RAM, then using this command to look at it or display
1700 config CMD_BOOTCOUNT
1702 depends on BOOTCOUNT_LIMIT
1704 Enable the bootcount command, which allows interrogation and
1705 reset of the bootcounter.
1708 bool "Enable board-specific commands"
1710 (deprecated: instead, please define a Kconfig option for each command)
1712 Some boards have board-specific commands which are only enabled
1713 during developemnt and need to be turned off for production. This
1714 option provides a way to control this. The commands that are enabled
1715 vary depending on the board.
1717 config CMD_BLOCK_CACHE
1718 bool "blkcache - control and stats for block cache"
1719 depends on BLOCK_CACHE
1720 default y if BLOCK_CACHE
1722 Enable the blkcache command, which can be used to control the
1723 operation of the cache functions.
1724 This is most useful when fine-tuning the operation of the cache
1725 during development, but also allows the cache to be disabled when
1726 it might hurt performance (e.g. when using the ums command).
1733 Enable the 'button' command which allows to get the status of
1734 buttons supported by the board. The buttonss can be listed with
1735 'button list' and state can be known with 'button <label>'.
1736 Any button drivers can be controlled with this command, e.g.
1740 bool "icache or dcache"
1742 Enable the "icache" and "dcache" commands
1744 config CMD_CONITRACE
1745 bool "conitrace - trace console input codes"
1747 Enable the 'conitrace' command which displays the codes received
1748 from the console input as hexadecimal numbers.
1751 bool "Enable clear screen command 'cls'"
1752 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1755 Enable the 'cls' command which clears the screen contents
1756 on video frame buffer.
1759 bool "efidebug - display/configure UEFI environment"
1760 depends on EFI_LOADER
1761 select EFI_DEVICE_PATH_TO_TEXT
1764 Enable the 'efidebug' command which provides a subset of UEFI
1765 shell utility with simplified functionality. It will be useful
1766 particularly for managing boot parameters as well as examining
1767 various EFI status for debugging.
1769 config CMD_EXCEPTION
1770 bool "exception - raise exception"
1771 depends on ARM || RISCV || X86
1773 Enable the 'exception' command which allows to raise an exception.
1780 Enable the 'led' command which allows for control of LEDs supported
1781 by the board. The LEDs can be listed with 'led list' and controlled
1782 with led on/off/togle/blink. Any LED drivers can be controlled with
1783 this command, e.g. led_gpio.
1790 Enable the 'date' command for getting/setting the time/date in RTC
1797 Enable the 'rtc' command for low-level access to RTC devices.
1802 Run commands and summarize execution time.
1805 bool "gettime - read elapsed time"
1807 Enable the 'gettime' command which reads the elapsed time since
1808 U-Boot started running. This shows the time in seconds and
1809 milliseconds. See also the 'bootstage' command which provides more
1810 flexibility for boot timing.
1817 Print bytes from the hardware random number generator.
1819 # TODO: rename to CMD_SLEEP
1824 Delay execution for some time
1827 bool "support for multiprocessor"
1829 This provides an option to brinup
1830 different processors in multiprocessor
1836 Access the system timer.
1842 This provides basic access to the U-Boot's sound support. The main
1843 feature is to play a beep.
1845 sound init - set up sound system
1846 sound play - play a sound
1852 Boot image via local extlinux.conf file
1858 This provides access to the QEMU firmware interface. The main
1859 feature is to allow easy loading of files passed to qemu-system
1860 via -kernel / -initrd
1862 source "cmd/mvebu/Kconfig"
1865 bool "terminal - provides a way to attach a serial terminal"
1867 Provides a 'cu'-like serial terminal command. This can be used to
1868 access other serial ports from the system console. The terminal
1869 is very simple with no special processing of characters. As with
1870 cu, you can press ~. (tilde followed by period) to exit.
1873 bool "uuid, guid - generation of unique IDs"
1876 This enables two commands:
1878 uuid - generate random Universally Unique Identifier
1879 guid - generate Globally Unique Identifier based on random UUID
1881 The two commands are very similar except for the endianness of the
1886 source "cmd/ti/Kconfig"
1888 config CMD_BOOTSTAGE
1889 bool "Enable the 'bootstage' command"
1890 depends on BOOTSTAGE
1892 Add a 'bootstage' command which supports printing a report
1893 and un/stashing of bootstage data.
1895 menu "Power commands"
1897 bool "Enable Driver Model PMIC command"
1900 This is the pmic command, based on a driver model pmic's API.
1901 Command features are unchanged:
1902 - list - list pmic devices
1903 - pmic dev <id> - show or [set] operating pmic device (NEW)
1904 - pmic dump - dump registers
1905 - pmic read address - read byte of register at address
1906 - pmic write address - write byte to register at address
1907 The only one change for this command is 'dev' subcommand.
1909 config CMD_REGULATOR
1910 bool "Enable Driver Model REGULATOR command"
1911 depends on DM_REGULATOR
1913 This command is based on driver model regulator's API.
1914 User interface features:
1915 - list - list regulator devices
1916 - regulator dev <id> - show or [set] operating regulator device
1917 - regulator info - print constraints info
1918 - regulator status - print operating status
1919 - regulator value <val] <-f> - print/[set] voltage value [uV]
1920 - regulator current <val> - print/[set] current value [uA]
1921 - regulator mode <id> - print/[set] operating mode id
1922 - regulator enable - enable the regulator output
1923 - regulator disable - disable the regulator output
1925 The '-f' (force) option can be used for set the value which exceeds
1926 the limits, which are found in device-tree and are kept in regulator's
1927 uclass platdata structure.
1931 menu "Security commands"
1933 bool "Enable the 'aes' command"
1936 This provides a means to encrypt and decrypt data using the AES
1937 (Advanced Encryption Standard). This algorithm uses a symetric key
1938 and is widely used as a streaming cipher. Different key lengths are
1939 supported by the algorithm but this command only supports 128 bits
1943 bool "Enable the 'blob' command"
1945 This is used with the Freescale secure boot mechanism.
1947 Freescale's SEC block has built-in Blob Protocol which provides
1948 a method for protecting user-defined data across system power
1949 cycles. SEC block protects data in a data structure called a Blob,
1950 which provides both confidentiality and integrity protection.
1952 Encapsulating data as a blob
1953 Each time that the Blob Protocol is used to protect data, a
1954 different randomly generated key is used to encrypt the data.
1955 This random key is itself encrypted using a key which is derived
1956 from SoC's non-volatile secret key and a 16 bit Key identifier.
1957 The resulting encrypted key along with encrypted data is called a
1958 blob. The non-volatile secure key is available for use only during
1961 During decapsulation, the reverse process is performed to get back
1965 blob enc - encapsulating data as a cryptgraphic blob
1966 blob dec - decapsulating cryptgraphic blob to get the data
1970 blob enc src dst len km
1972 Encapsulate and create blob of data $len bytes long
1973 at address $src and store the result at address $dst.
1974 $km is the 16 byte key modifier is also required for
1975 generation/use as key for cryptographic operation. Key
1976 modifier should be 16 byte long.
1978 blob dec src dst len km
1980 Decapsulate the blob of data at address $src and
1981 store result of $len byte at addr $dst.
1982 $km is the 16 byte key modifier is also required for
1983 generation/use as key for cryptographic operation. Key
1984 modifier should be 16 byte long.
1987 bool "Support 'hash' command"
1990 This provides a way to hash data in memory using various supported
1991 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1992 saved to memory or to an environment variable. It is also possible
1993 to verify a hash against data in memory.
1996 bool "Support the 'hvc' command"
1997 depends on ARM_SMCCC
1999 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2000 development and testing.
2003 bool "Support the 'smc' command"
2004 depends on ARM_SMCCC
2006 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2007 development and testing.
2013 Add -v option to verify data against a hash.
2023 bool "Enable the 'tpm' command"
2024 depends on TPM_V1 || TPM_V2
2025 select CMD_TPM_V1 if TPM_V1
2026 select CMD_TPM_V2 if TPM_V2
2028 This provides a means to talk to a TPM from the command line. A wide
2029 range of commands if provided - see 'tpm help' for details. The
2030 command requires a suitable TPM on your board and the correct driver
2036 bool "Enable the 'tpm test' command"
2039 This provides a a series of tests to confirm that the TPMv1.x is
2040 working correctly. The tests cover initialisation, non-volatile RAM,
2041 extend, global lock and checking that timing is within expectations.
2042 The tests pass correctly on Infineon TPMs but may need to be adjusted
2049 menu "Firmware commands"
2051 bool "Enable crosec command"
2055 Enable command-line access to the Chrome OS EC (Embedded
2056 Controller). This provides the 'crosec' command which has
2057 a number of sub-commands for performing EC tasks such as
2058 updating its flash, accessing a small saved context area
2059 and talking to the I2C bus behind the EC (if there is one).
2062 menu "Filesystem commands"
2064 bool "Enable the 'btrsubvol' command"
2067 This enables the 'btrsubvol' command to list subvolumes
2068 of a BTRFS filesystem. There are no special commands for
2069 listing BTRFS directories or loading BTRFS files - this
2070 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2071 when BTRFS is enabled (see FS_BTRFS).
2074 bool "Enable the 'cbfs' command"
2077 Define this to enable support for reading from a Coreboot
2078 filesystem. This is a ROM-based filesystem used for accessing files
2079 on systems that use coreboot as the first boot-loader and then load
2080 U-Boot to actually boot the Operating System. Available commands are
2081 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2084 bool "Enable the 'cramfs' command"
2085 depends on FS_CRAMFS
2087 This provides commands for dealing with CRAMFS (Compressed ROM
2088 filesystem). CRAMFS is useful when space is tight since files are
2089 compressed. Two commands are provided:
2091 cramfsls - lists files in a cramfs image
2092 cramfsload - loads a file from a cramfs image
2095 bool "ext2 command support"
2098 Enables EXT2 FS command
2101 bool "ext4 command support"
2104 Enables EXT4 FS command
2106 config CMD_EXT4_WRITE
2108 bool "ext4 write command support"
2111 Enables EXT4 FS write command
2114 bool "FAT command support"
2117 Support for the FAT fs
2120 bool "SquashFS command support"
2123 Enables SquashFS filesystem commands (e.g. load, ls).
2125 config CMD_FS_GENERIC
2126 bool "filesystem commands"
2128 Enables filesystem commands (e.g. load, ls) that work for multiple
2132 bool "fsuuid command"
2134 Enables fsuuid command for filesystem UUID.
2137 bool "jffs2 command"
2140 Enables commands to support the JFFS2 (Journalling Flash File System
2141 version 2) filesystem. This enables fsload, ls and fsinfo which
2142 provide the ability to load files, list directories and obtain
2143 filesystem information.
2146 bool "MTD partition support"
2149 MTD partitioning tool support.
2150 It is strongly encouraged to avoid using this command
2151 anymore along with 'sf', 'nand', 'onenand'. One can still
2152 declare the partitions in the mtdparts environment variable
2153 but better use the MTD stack and the 'mtd' command instead.
2155 config CMD_MTDPARTS_SPREAD
2156 bool "Padd partition size to take account of bad blocks"
2157 depends on CMD_MTDPARTS
2159 This enables the 'spread' sub-command of the mtdparts command.
2160 This command will modify the existing mtdparts variable by increasing
2161 the size of the partitions such that 1) each partition's net size is
2162 at least as large as the size specified in the mtdparts variable and
2163 2) each partition starts on a good block.
2165 config CMD_MTDPARTS_SHOW_NET_SIZES
2166 bool "Show net size (w/o bad blocks) of partitions"
2167 depends on CMD_MTDPARTS
2169 Adds two columns to the printed partition table showing the
2170 effective usable size of a partition, if bad blocks are taken
2173 config MTDIDS_DEFAULT
2174 string "Default MTD IDs"
2175 depends on MTD || SPI_FLASH
2177 Defines a default MTD IDs list for use with MTD partitions in the
2178 Linux MTD command line partitions format.
2180 config MTDPARTS_DEFAULT
2181 string "Default MTD partition scheme"
2182 depends on MTD || SPI_FLASH
2184 Defines a default MTD partitioning scheme in the Linux MTD command
2185 line partitions format
2188 bool "reiser - Access to reiserfs filesystems"
2190 This provides two commands which operate on a resierfs filesystem,
2191 commonly used some years ago:
2193 reiserls - list files
2194 reiserload - load a file
2197 bool "yaffs2 - Access of YAFFS2 filesystem"
2201 This provides commands for accessing a YAFFS2 filesystem. Yet
2202 Another Flash Filesystem 2 is a filesystem designed specifically
2203 for NAND flash. It incorporates bad-block management and ensures
2204 that device writes are sequential regardless of filesystem
2208 bool "zfs - Access of ZFS filesystem"
2210 This provides commands to accessing a ZFS filesystem, commonly used
2211 on Solaris systems. Two sub-commands are provided:
2213 zfsls - list files in a directory
2214 zfsload - load a file
2216 See doc/README.zfs for more details.
2220 menu "Debug commands"
2225 The bedbug (emBEDded deBUGger) command provides debugging features
2226 for some PowerPC processors. For details please see the
2227 documentation in doc/README.bedbug.
2230 bool "diag - Board diagnostics"
2232 This command provides access to board diagnostic tests. These are
2233 called Power-on Self Tests (POST). The command allows listing of
2234 available tests and running either all the tests, or specific tests
2238 bool "irq - Show information about interrupts"
2239 depends on !ARM && !MIPS && !RISCV && !SH
2241 This enables two commands:
2243 interrupts - enable or disable interrupts
2244 irqinfo - print device-specific interrupt information
2247 bool "kgdb - Allow debugging of U-Boot with gdb"
2250 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2251 over a serial link for debugging purposes. This allows
2252 single-stepping, inspecting variables, etc. This is supported only
2253 on PowerPC at present.
2256 bool "log - Generation, control and access to logging"
2259 This provides access to logging features. It allows the output of
2260 log data to be controlled to a limited extent (setting up the default
2261 maximum log level for emitting of records). It also provides access
2262 to a command used for testing the log system.
2265 bool "trace - Support tracing of function calls and timing"
2267 Enables a command to control using of function tracing within
2268 U-Boot. This allows recording of call traces including timing
2269 information. The command can write data to memory for exporting
2270 for analysis (e.g. using bootchart). See doc/README.trace for full
2274 bool "avb - Android Verified Boot 2.0 operations"
2275 depends on AVB_VERIFY
2278 Enables a "avb" command to perform verification of partitions using
2279 Android Verified Boot 2.0 functionality. It includes such subcommands:
2280 avb init - initialize avb2 subsystem
2281 avb read_rb - read rollback index
2282 avb write_rb - write rollback index
2283 avb is_unlocked - check device lock state
2284 avb get_uuid - read and print uuid of a partition
2285 avb read_part - read data from partition
2286 avb read_part_hex - read data from partition and output to stdout
2287 avb write_part - write data to partition
2288 avb verify - run full verification chain
2292 tristate "Enable UBI - Unsorted block images commands"
2295 UBI is a software layer above MTD layer which admits use of LVM-like
2296 logical volumes on top of MTD devices, hides some complexities of
2297 flash chips like wear and bad blocks and provides some other useful
2298 capabilities. Please, consult the MTD web site for more details
2299 (www.linux-mtd.infradead.org). Activate this option if you want
2300 to use U-Boot UBI commands.
2301 It is also strongly encouraged to also enable CONFIG_MTD to get full
2304 config CMD_UBI_RENAME
2305 bool "Enable rename"
2309 Enable a "ubi" command to rename ubi volume:
2310 ubi rename <oldname> <newname>
2313 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2315 default y if CMD_UBI
2318 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob