1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
58 config SYS_PROMPT_HUSH_PS2
59 string "Hush shell secondary prompt"
60 depends on HUSH_PARSER
63 This defines the secondary prompt string, which is
64 printed when the command interpreter needs more input
65 to complete a command. Usually "> ".
68 bool "Command execution tracer"
72 This option enables the possiblity to print all commands before
73 executing them and after all variables are evaluated (similar
74 to Bash's xtrace/'set -x' feature).
75 To enable the tracer a variable "xtrace" needs to be defined in
90 List and dump ACPI tables. ACPI (Advanced Configuration and Power
91 Interface) is used mostly on x86 for providing information to the
92 Operating System about devices in the system. The tables are set up
93 by the firmware, typically U-Boot but possibly an earlier firmware
94 module, if U-Boot is chain-loaded from something else. ACPI tables
95 can also include code, to perform hardware-specific tasks required
96 by the Operating Systems. This allows some amount of separation
97 between the firmware and OS, and is particularly useful when you
98 want to make hardware changes without the OS needing to be adjusted.
105 List non-identity virtual-physical memory mappings for 32-bit CPUs.
118 Print ".config" contents.
120 If this option is enabled, the ".config" file contents are embedded
121 in the U-Boot image and can be printed on the console by the "config"
122 command. This provides information of which options are enabled on
129 Print console devices and information.
135 Print information about available CPUs. This normally shows the
136 number of CPUs, type (e.g. manufacturer, architecture, product or
137 internal name) and clock frequency. Other information may be
138 available depending on the CPU driver.
144 Print GPL license text
149 Provides access to the Intel Power-Management Controller (PMC) so
150 that its state can be examined. This does not currently support
151 changing the state but it is still useful for debugging and seeing
160 config CMD_TLV_EEPROM
162 depends on I2C_EEPROM
164 Display and program the system EEPROM data block in ONIE Tlvinfo
165 format. TLV stands for Type-Length-Value.
167 config SPL_CMD_TLV_EEPROM
168 bool "tlv_eeprom for SPL"
169 depends on SPL_I2C_EEPROM
170 select SPL_DRIVERS_MISC
172 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
176 depends on RISCV_SMODE && SBI_V02
178 Display information about the SBI implementation.
188 Run the command stored in the environment "bootcmd", i.e.
189 "bootd" does the same thing as "run bootcmd".
195 Boot an application image from the memory.
198 bool "Support booting UEFI FIT images"
199 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
202 Support booting UEFI FIT images via the bootm command.
207 Boot the Linux zImage
211 depends on ARM64 || RISCV
214 Boot an AArch64 Linux Kernel image from memory.
217 bool "Support booting Linux OS images"
218 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
221 Support booting the Linux kernel directly via a command such as bootm
225 bool "Support booting NetBSD (non-EFI) loader images"
229 Support booting NetBSD via the bootm command.
231 config BOOTM_OPENRTOS
232 bool "Support booting OPENRTOS / FreeRTOS images"
235 Support booting OPENRTOS / FreeRTOS via the bootm command.
238 bool "Support booting Enea OSE images"
239 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
242 Support booting Enea OSE images via the bootm command.
245 bool "Support booting Plan9 OS images"
249 Support booting Plan9 images via the bootm command.
252 bool "Support booting RTEMS OS images"
256 Support booting RTEMS images via the bootm command.
259 bool "Support booting VxWorks OS images"
263 Support booting VxWorks images via the bootm command.
267 depends on EFI_LOADER
270 Boot an EFI image from memory.
272 config CMD_BOOTEFI_HELLO_COMPILE
273 bool "Compile a standard EFI hello world binary for testing"
274 depends on CMD_BOOTEFI && !CPU_V7M
277 This compiles a standard EFI hello world application with U-Boot so
278 that it can be used with the test/py testing framework. This is useful
279 for testing that EFI is working at a basic level, and for bringing
280 up EFI support on a new architecture.
282 No additional space will be required in the resulting U-Boot binary
283 when this option is enabled.
285 config CMD_BOOTEFI_HELLO
286 bool "Allow booting a standard EFI hello world for testing"
287 depends on CMD_BOOTEFI_HELLO_COMPILE
288 default y if CMD_BOOTEFI_SELFTEST
290 This adds a standard EFI hello world application to U-Boot so that
291 it can be used with the 'bootefi hello' command. This is useful
292 for testing that EFI is working at a basic level, and for bringing
293 up EFI support on a new architecture.
295 source lib/efi_selftest/Kconfig
301 Add an ANSI terminal boot menu command.
306 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
307 image into RAM, dump image structure information, etc. Those dtb/dtbo
308 files should be merged in one dtb further, which needs to be passed to
309 the kernel, as part of a boot process.
313 depends on ANDROID_BOOT_IMAGE
315 Android Boot Image manipulation commands. Allows one to extract
316 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
317 obtain corresponding meta-information from boot.img.
319 See doc/android/boot-image.rst for details.
322 bool "bootelf, bootvx"
326 Boot an ELF/vxWorks image from the memory.
329 bool "Flattened Device Tree utility commands"
333 Do FDT related setup before booting into the Operating System.
335 config SUPPORT_EXTENSION_SCAN
339 bool "Extension board management command"
341 depends on SUPPORT_EXTENSION_SCAN
343 Enables the "extension" command, which allows to detect
344 extension boards connected to the system, and apply
345 corresponding Device Tree overlays.
351 Start an application at a given address.
357 Run the command in the given environment variable.
363 Print header information for application image.
368 List all images found in flash
374 Extract a part of a multi-image.
377 bool "spl export - Export boot information for Falcon boot"
380 Falcon mode allows booting directly from SPL into an Operating
381 System such as Linux, thus skipping U-Boot proper. See
382 doc/README.falcon for full information about how to use this
385 config CMD_SPL_NAND_OFS
386 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
387 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
390 This provides the offset of the command line arguments for Linux
391 when booting from NAND in Falcon mode. See doc/README.falcon
392 for full information about how to use this option (and also see
393 board/gateworks/gw_ventana/README for an example).
395 config CMD_SPL_NOR_OFS
396 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
397 depends on CMD_SPL && SPL_NOR_SUPPORT
400 This provides the offset of the command line arguments or dtb for
401 Linux when booting from NOR in Falcon mode.
403 config CMD_SPL_WRITE_SIZE
404 hex "Size of argument area"
408 This provides the size of the command-line argument area in NAND
409 flash used by Falcon-mode boot. See the documentation until CMD_SPL
412 config CMD_THOR_DOWNLOAD
413 bool "thor - TIZEN 'thor' download"
416 Implements the 'thor' download protocol. This is a way of
417 downloading a software update over USB from an attached host.
418 There is no documentation about this within the U-Boot source code
419 but you should be able to find something on the interwebs.
422 bool "zboot - x86 boot command"
424 With x86 machines it is common to boot a bzImage file which
425 contains both a kernel and a setup.bin file. The latter includes
426 configuration information from the dark ages which x86 boards still
427 need to pick things out of.
429 Consider using FIT in preference to this since it supports directly
430 booting both 32- and 64-bit kernels, as well as secure boot.
431 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
435 menu "Environment commands"
438 bool "ask for env variable"
440 Ask for environment variable
458 Edit environment variable.
463 Allow for searching environment variables
469 Save all environment variables into the compiled-in persistent
475 depends on CMD_SAVEENV
477 Erase environment variables from the compiled-in persistent
480 config CMD_ENV_EXISTS
484 Check if a variable is defined in the environment for use in
487 config CMD_ENV_CALLBACK
488 bool "env callbacks - print callbacks and their associated variables"
490 Some environment variable have callbacks defined by
491 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
492 For example changing "baudrate" adjust the serial baud rate. This
493 command lists the currently defined callbacks.
496 bool "env flags -print variables that have non-default flags"
498 Some environment variables have special flags that control their
499 behaviour. For example, serial# can only be written once and cannot
500 be deleted. This command shows the variables that have special
503 config CMD_NVEDIT_EFI
504 bool "env [set|print] -e - set/print UEFI variables"
505 depends on EFI_LOADER
508 UEFI variables are encoded as some form of U-Boot variables.
509 If enabled, we are allowed to set/print UEFI variables using
510 "env" command with "-e" option without knowing details.
512 config CMD_NVEDIT_INFO
513 bool "env info - print or evaluate environment information"
515 Print environment information:
516 - env_valid : is environment valid
517 - env_ready : is environment imported into hash table
518 - env_use_default : is default environment used
520 This command can be optionally used for evaluation in scripts:
521 [-d] : evaluate whether default environment is used
522 [-p] : evaluate whether environment can be persisted
524 The result of multiple evaluations will be combined with AND.
526 config CMD_NVEDIT_LOAD
529 Load all environment variables from the compiled-in persistent
532 config CMD_NVEDIT_SELECT
535 Select the compiled-in persistent storage of environment variables.
539 menu "Memory commands"
544 Compute binary operations (xor, or, and) of byte arrays of arbitrary
545 size from memory and store the result in memory or the environment.
549 default y if BLOBLIST
551 Show information about the bloblist, a collection of binary blobs
552 held in memory that persist between SPL and U-Boot. In the case of
553 x86 devices the bloblist can be used to hold ACPI tables so that they
554 remain available in memory.
567 Add -v option to verify data against a crc32 checksum.
570 bool "eeprom - EEPROM subsystem"
572 (deprecated, needs conversion to driver model)
573 Provides commands to read and write EEPROM (Electrically Erasable
574 Programmable Read Only Memory) chips that are connected over an
577 config CMD_EEPROM_LAYOUT
578 bool "Enable layout-aware eeprom commands"
579 depends on CMD_EEPROM
581 (deprecated, needs conversion to driver model)
582 When enabled, additional eeprom sub-commands become available.
584 eeprom print - prints the contents of the eeprom in a human-readable
585 way (eeprom layout fields, and data formatted to be fit for human
588 eeprom update - allows user to update eeprom fields by specifying
589 the field name, and providing the new data in a human readable format
590 (same format as displayed by the eeprom print command).
592 Both commands can either auto detect the layout, or be told which
596 __weak int parse_layout_version(char *str)
597 - override to provide your own layout name parsing
598 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
600 - override to setup the layout metadata based on the version
601 __weak int eeprom_layout_detect(unsigned char *data)
602 - override to provide your own algorithm for detecting layout
605 - contains various printing and updating functions for common
606 types of eeprom fields. Can be used for defining
609 config EEPROM_LAYOUT_HELP_STRING
610 string "Tells user what layout names are supported"
611 depends on CMD_EEPROM_LAYOUT
612 default "<not defined>"
614 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
617 config SYS_I2C_EEPROM_BUS
618 int "I2C bus of the EEPROM device."
619 depends on CMD_EEPROM
622 config SYS_I2C_EEPROM_ADDR_LEN
623 int "Length in bytes of the EEPROM memory array address"
624 depends on CMD_EEPROM || ID_EEPROM
628 Note: This is NOT the chip address length!
630 config SYS_EEPROM_SIZE
631 depends on CMD_EEPROM
632 int "Size in bytes of the EEPROM device"
635 config SYS_EEPROM_PAGE_WRITE_BITS
636 int "Number of bits used to address bytes in a single page"
637 depends on CMD_EEPROM
640 The EEPROM page size is 2^SYS_EEPROM_PAGE_WRITE_BITS.
641 A 64 byte page, for example would require six bits.
643 config SYS_EEPROM_PAGE_WRITE_DELAY_MS
644 int "Number of milliseconds to delay between page writes"
645 depends on CMD_EEPROM || CMD_I2C
651 Infinite write loop on address range
658 Compute MD5 checksum.
663 depends on CMD_MD5SUM
665 Add -v option to verify data against an MD5 checksum.
670 Display memory information.
673 bool "md, mm, nm, mw, cp, cmp, base, loop"
678 mm - memory modify (auto-incrementing address)
679 nm - memory modify (constant address)
680 mw - memory write (fill)
683 base - print or set address offset
684 loop - initialize loop on address range
686 config CMD_MEM_SEARCH
687 bool "ms - Memory search"
689 Memory-search command
691 This allows searching through a region of memory looking for hex
692 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
693 support it). It is also possible to search for a string. The
694 command accepts a memory range and a list of values to search for.
695 The values need to appear in memory in the same order they are given
696 in the command. At most 10 matches can be returned at a time, but
697 pressing return will show the next 10 matches. Environment variables
698 are set for use with scripting (memmatches, memaddr, mempos).
701 bool "Enable cyclic md/mw commands"
702 depends on CMD_MEMORY
704 Add the "mdc" and "mwc" memory commands. These are cyclic
709 This command will print 4 bytes (10,11,12,13) each 500 ms.
711 => mwc.l 100 12345678 10
712 This command will write 12345678 to address 100 all 10 ms.
717 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
719 random - fill memory with random data
724 Simple RAM read/write test.
728 config SYS_ALT_MEMTEST
729 bool "Alternative test"
731 Use a more complete alternative memory test.
735 config SYS_ALT_MEMTEST_BITFLIP
739 The alternative memory test includes bitflip test since 2020.07.
740 The bitflip test significantly increases the overall test time.
741 Bitflip test can optionally be disabled here.
745 config SYS_MEMTEST_START
746 hex "default start address for mtest"
749 This is the default start address for mtest for simple read/write
750 test. If no arguments are given to mtest, default address is used
753 config SYS_MEMTEST_END
754 hex "default end address for mtest"
757 This is the default end address for mtest for simple read/write
758 test. If no arguments are given to mtest, default address is used
767 Compute SHA1 checksum.
769 config SHA1SUM_VERIFY
771 depends on CMD_SHA1SUM
773 Add -v option to verify data against a SHA1 checksum.
776 bool "strings - display strings in memory"
778 This works similarly to the Unix 'strings' command except that it
779 works with a memory range. String of printable characters found
780 within the range are displayed. The minimum number of characters
781 for a sequence to be considered a string can be provided.
785 menu "Compression commands"
789 default y if CMD_BOOTI
792 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
797 default y if CMD_BOOTI
800 Support decompressing an LZ4 image from memory region.
804 default y if CMD_BOOTI
807 Uncompress a zip-compressed memory region.
811 select GZIP_COMPRESSED
813 Compress a memory region with zlib deflate method.
817 menu "Device access commands"
820 #depends on FLASH_CFI_DRIVER
823 ARM Ltd reference designs flash partition access
826 bool "adc - Access Analog to Digital Converters info and data"
828 depends on DM_REGULATOR
830 Shows ADC device info and permit printing one-shot analog converted
831 data from a named Analog to Digital Converter.
836 depends on PARTITIONS
838 Read/modify/write the fields of Bootloader Control Block, usually
839 stored on the flash "misc" partition with its structure defined in:
840 https://android.googlesource.com/platform/bootable/recovery/+/master/
841 bootloader_message/include/bootloader_message/bootloader_message.h
843 Some real-life use-cases include (but are not limited to):
844 - Determine the "boot reason" (and act accordingly):
845 https://source.android.com/devices/bootloader/boot-reason
846 - Get/pass a list of commands from/to recovery:
847 https://android.googlesource.com/platform/bootable/recovery
848 - Inspect/dump the contents of the BCB fields
851 bool "bind/unbind - Bind or unbind a device to/from a driver"
854 Bind or unbind a device to/from a driver from the command line.
855 This is useful in situations where a device may be handled by several
856 drivers. For example, this can be used to bind a UDC to the usb ether
857 gadget driver from the command line.
860 bool "clk - Show clock frequencies"
863 Shows clock frequences by calling a sock_clk_dump() hook function.
864 This is depreated in favour of using the CLK uclass and accessing
865 clock values from associated drivers. However currently no command
869 bool "demo - Demonstration commands for driver model"
872 Provides a 'demo' command which can be used to play around with
873 driver model. To use this properly you will need to enable one or
874 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
875 Otherwise you will always get an empty list of devices. The demo
876 devices are defined in the sandbox device tree, so the easiest
877 option is to use sandbox and pass the -d point to sandbox's
884 Enables the command "dfu" which is used to have U-Boot create a DFU
885 class device via USB. This command requires that the "dfu_alt_info"
886 environment variable be set and define the alt settings to expose to
890 bool "dm - Access to driver model information"
893 Provides access to driver model data structures and information,
894 such as a list of devices, list of uclasses and the state of each
895 device (e.g. activated). This is not required for operation, but
896 can be useful to see the state of driver model for debugging or
900 bool "fastboot - Android fastboot support"
903 This enables the command "fastboot" which enables the Android
904 fastboot mode for the platform. Fastboot is a protocol for
905 downloading images, flashing and device control used on
906 Android devices. Fastboot requires either the network stack
907 enabled or support for acting as a USB device.
909 See doc/android/fastboot.rst for more information.
912 bool "flinfo, erase, protect"
914 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
917 flinfo - print FLASH memory information
919 protect - enable or disable FLASH write protection
928 config CMD_FPGA_LOADBP
929 bool "fpga loadbp - load partial bitstream (Xilinx only)"
932 Supports loading an FPGA device from a bitstream buffer containing
935 config CMD_FPGA_LOADFS
936 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
939 Supports loading an FPGA device from a FAT filesystem.
941 config CMD_FPGA_LOADMK
942 bool "fpga loadmk - load bitstream from image"
945 Supports loading an FPGA device from a image generated by mkimage.
947 config CMD_FPGA_LOADP
948 bool "fpga loadp - load partial bitstream"
951 Supports loading an FPGA device from a bitstream buffer containing
954 config CMD_FPGA_LOAD_SECURE
955 bool "fpga loads - loads secure bitstreams (Xilinx only)"
958 Enables the fpga loads command which is used to load secure
959 (authenticated or encrypted or both) bitstreams on to FPGA.
962 bool "fpgad - dump FPGA registers"
964 (legacy, needs conversion to driver model)
965 Provides a way to dump FPGA registers by calling the board-specific
966 fpga_get_reg() function. This functions similarly to the 'md'
970 bool "fuse - support for the fuse subssystem"
972 (deprecated - needs conversion to driver model)
973 This allows reading, sensing, programming or overriding fuses
974 which control the behaviour of the device. The command uses the
986 Control PWM channels, this allows invert/config/enable/disable PWM channels.
989 bool "GPT (GUID Partition Table) command"
991 select HAVE_BLOCK_DEVICE
992 select PARTITION_UUIDS
995 Enable the 'gpt' command to ready and write GPT style partition
999 bool "GPT Random UUID generation"
1002 Enable the generation of partitions with random UUIDs if none
1005 config CMD_GPT_RENAME
1006 bool "GPT partition renaming commands"
1009 Enables the 'gpt' command to interchange names on two GPT
1010 partitions via the 'gpt swap' command or to rename single
1011 partitions via the 'rename' command.
1014 bool "ide - Support for IDE drivers"
1017 Provides an 'ide' command which allows accessing the IDE drive,
1018 reseting the IDE interface, printing the partition table and
1019 geting device info. It also enables the 'diskboot' command which
1020 permits booting from an IDE drive.
1023 bool "io - Support for performing I/O accesses"
1025 Provides an 'iod' command to display I/O space and an 'iow' command
1026 to write values to the I/O space. This can be useful for manually
1027 checking the state of devices during boot when debugging device
1031 bool "iotrace - Support for tracing I/O activity"
1033 Provides an 'iotrace' command which supports recording I/O reads and
1034 writes in a trace buffer in memory . It also maintains a checksum
1035 of the trace records (even if space is exhausted) so that the
1036 sequence of I/O accesses can be verified.
1038 When debugging drivers it is useful to see what I/O accesses were
1039 done and in what order.
1041 Even if the individual accesses are of little interest it can be
1042 useful to verify that the access pattern is consistent each time
1043 an operation is performed. In this case a checksum can be used to
1044 characterise the operation of a driver. The checksum can be compared
1045 across different runs of the operation to verify that the driver is
1048 In particular, when performing major refactoring of the driver, where
1049 the access pattern should not change, the checksum provides assurance
1050 that the refactoring work has not broken the driver.
1052 This works by sneaking into the io.h heder for an architecture and
1053 redirecting I/O accesses through iotrace's tracing mechanism.
1055 For now no commands are provided to examine the trace buffer. The
1056 format is fairly simple, so 'md' is a reasonable substitute.
1058 Note: The checksum feature is only useful for I/O regions where the
1059 contents do not change outside of software control. Where this is not
1060 suitable you can fall back to manually comparing the addresses. It
1061 might be useful to enhance tracing to only checksum the accesses and
1062 not the data read/written.
1072 bool "w1 - Support for Dallas 1-Wire protocol"
1074 Dallas 1-wire protocol support
1080 Load a binary file over serial line.
1086 Load an S-Record file over serial line
1090 bool "lsblk - list block drivers and devices"
1092 Print list of available block device drivers, and for each, the list
1093 of known block devices.
1096 bool "MBR (Master Boot Record) command"
1097 select DOS_PARTITION
1098 select HAVE_BLOCK_DEVICE
1100 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1101 style partition tables.
1107 Enable the command "misc" for accessing miscellaneous devices with
1108 a MISC uclass driver. The command provides listing all MISC devices
1109 as well as read and write functionalities via their drivers.
1115 MMC memory mapped support.
1119 config CMD_BKOPS_ENABLE
1120 bool "mmc bkops enable"
1124 Enable command for setting manual background operations handshake
1125 on a eMMC device. The feature is optionally available on eMMC devices
1126 conforming to standard >= 4.41.
1129 bool "Enable support for RPMB in the mmc command"
1130 depends on SUPPORT_EMMC_RPMB
1132 Enable the commands for reading, writing and programming the
1133 key for the Replay Protection Memory Block partition in eMMC.
1135 config CMD_MMC_SWRITE
1137 depends on MMC_WRITE
1140 Enable support for the "mmc swrite" command to write Android sparse
1149 Enable storage cloning over block devices, useful for
1150 initial flashing by external block device without network
1153 config CMD_OPTEE_RPMB
1154 bool "Enable read/write support on RPMB via OPTEE"
1155 depends on SUPPORT_EMMC_RPMB && OPTEE
1157 Enable the commands for reading, writing persistent named values
1158 in the Replay Protection Memory Block partition in eMMC by
1159 using Persistent Objects in OPTEE
1164 select MTD_PARTITIONS
1166 MTD commands support.
1170 depends on MULTIPLEXER
1172 List, select, and deselect mux controllers on the fly.
1176 default y if NAND_SUNXI
1177 depends on MTD_RAW_NAND
1182 config CMD_NAND_TRIMFFS
1183 bool "nand write.trimffs"
1184 default y if ARCH_SUNXI
1186 Allows one to skip empty pages when flashing something on a NAND.
1188 config CMD_NAND_LOCK_UNLOCK
1189 bool "nand lock/unlock"
1191 NAND locking support.
1193 config CMD_NAND_TORTURE
1196 NAND torture support.
1205 NVM Express device support
1208 bool "onenand - access to onenand device"
1211 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1212 various useful features. This command allows reading, writing,
1213 and erasing blocks. It allso provides a way to show and change
1214 bad blocks, and test the device.
1219 Enable the 'osd' command which allows to query information from and
1220 write text data to a on-screen display (OSD) device; a virtual device
1221 associated with a display capable of displaying a text overlay on the
1222 display it's associated with..
1226 select HAVE_BLOCK_DEVICE
1227 select PARTITION_UUIDS
1229 Read and display information about the partition table on
1233 bool "pci - Access PCI devices"
1235 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1236 used on some devices to allow the CPU to communicate with its
1237 peripherals. Sub-commands allow bus enumeration, displaying and
1238 changing configuration space and a few other features.
1241 bool "pinmux - show pins muxing"
1243 default y if PINCTRL
1245 Parse all available pin-controllers and show pins muxing. This
1246 is useful for debug purpoer to check the pin muxing and to know if
1247 a pin is configured as a GPIO or as an alternate function.
1252 Poweroff/Shutdown the system
1255 bool "read - Read binary data from a partition"
1257 Provides low-level access to the data in a partition.
1259 config CMD_REMOTEPROC
1261 depends on REMOTEPROC
1263 Support for Remote Processor control
1266 bool "sata - Access SATA subsystem"
1269 SATA (Serial Advanced Technology Attachment) is a serial bus
1270 standard for connecting to hard drives and other storage devices.
1271 This command provides information about attached devices and allows
1272 reading, writing and other operations.
1274 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1275 Attachment, where AT refers to an IBM AT (Advanced Technology)
1276 computer released in 1984.
1279 bool "saves - Save a file over serial in S-Record format"
1281 Provides a way to save a binary file using the Motorola S-Record
1282 format over the serial line.
1285 bool "scsi - Access to SCSI devices"
1288 This provides a 'scsi' command which provides access to SCSI (Small
1289 Computer System Interface) devices. The command provides a way to
1290 scan the bus, reset the bus, read and write data and get information
1294 bool "sdram - Print SDRAM configuration information"
1296 Provides information about attached SDRAM. This assumed that the
1297 SDRAM has an EEPROM with information that can be read using the
1298 I2C bus. This is only available on some boards.
1302 depends on DM_SPI_FLASH || SPI_FLASH
1303 default y if DM_SPI_FLASH
1308 bool "sf test - Allow testing of SPI flash"
1311 Provides a way to test that SPI flash is working correctly. The
1312 test is destructive, in that an area of SPI flash must be provided
1313 for the test to use. Performance information is also provided,
1314 measuring the performance of reading, writing and erasing in
1315 Mbps (Million Bits Per Second). This value should approximately
1316 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1317 everything is working properly.
1320 bool "sspi - Command to access spi device"
1323 SPI utility command.
1325 config DEFAULT_SPI_BUS
1326 int "default spi bus used by sspi command"
1330 config DEFAULT_SPI_MODE
1331 hex "default spi mode used by sspi command (see include/spi.h)"
1336 bool "tsi148 - Command to access tsi148 device"
1338 This provides various sub-commands to initialise and configure the
1339 Turndra tsi148 device. See the command help for full details.
1342 bool "Enable UFS - Universal Flash Subsystem commands"
1345 "This provides commands to initialise and configure universal flash
1349 bool "universe - Command to set up the Turndra Universe controller"
1351 This allows setting up the VMEbus provided by this controller.
1352 See the command help for full details.
1357 select HAVE_BLOCK_DEVICE
1363 select USB_FUNCTION_SDP
1365 Enables the command "sdp" which is used to have U-Boot emulating the
1366 Serial Download Protocol (SDP) via USB.
1370 depends on USB_FUNCTION_ROCKUSB
1372 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1373 read/write info, image to/from devices. This enable rockusb command
1374 support to communication with rockusb device. for more detail about
1375 this command, please read doc/README.rockusb.
1377 config CMD_USB_MASS_STORAGE
1378 bool "UMS usb mass storage"
1379 depends on USB_GADGET_DOWNLOAD
1380 select USB_FUNCTION_MASS_STORAGE
1381 depends on BLK && USB_GADGET
1383 Enables the command "ums" and the USB mass storage support to the
1384 export a block device: U-Boot, the USB device, acts as a simple
1385 external hard drive plugged on the host USB port.
1388 bool "Xen para-virtualized block device"
1392 Xen para-virtualized block device support
1397 depends on HAVE_BLOCK_DEVICE
1400 VirtIO block device support
1406 This provides commands to control the watchdog timer devices.
1412 Enable the command "axi" for accessing AXI (Advanced eXtensible
1413 Interface) busses, a on-chip interconnect specification for managing
1414 functional blocks in SoC designs, which is also often used in designs
1415 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1419 menu "Shell scripting commands"
1425 Echo args to console
1431 Return true/false on integer compare.
1437 Run script from memory
1443 Evaluate boolean and math expressions and store the result in an env
1445 Also supports loading the value at a memory location into a variable.
1446 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1448 config CMD_SETEXPR_FMT
1451 depends on CMD_SETEXPR
1453 Evaluate format string expression and store result in an environment
1458 menu "Android support commands"
1460 config CMD_AB_SELECT
1463 depends on ANDROID_AB
1465 On Android devices with more than one boot slot (multiple copies of
1466 the kernel and system images) this provides a command to select which
1467 slot should be used to boot from and register the boot attempt. This
1468 is used by the new A/B update model where one slot is updated in the
1469 background while running from the other slot.
1476 bool "Network commands"
1486 bootp - boot image via network using BOOTP/TFTP protocol
1490 depends on CMD_BOOTP
1492 Boot image via network using DHCP/TFTP protocol
1494 config BOOTP_BOOTPATH
1495 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1497 depends on CMD_BOOTP
1499 Even though the config is called BOOTP_BOOTPATH, it stores the
1500 path in the variable 'rootpath'.
1503 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1505 depends on CMD_BOOTP
1507 The primary DNS server is stored as 'dnsip'. If two servers are
1508 returned, you must set BOOTP_DNS2 to store that second server IP
1512 bool "Store 'dnsip2' from BOOTP/DHCP server"
1513 depends on BOOTP_DNS
1515 If a DHCP client requests the DNS server IP from a DHCP server,
1516 it is possible that more than one DNS serverip is offered to the
1517 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1518 server IP will be stored in the additional environment
1519 variable "dnsip2". The first DNS serverip is always
1520 stored in the variable "dnsip", when BOOTP_DNS is defined.
1522 config BOOTP_GATEWAY
1523 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1525 depends on CMD_BOOTP
1527 config BOOTP_HOSTNAME
1528 bool "Request & store 'hostname' from BOOTP/DHCP server"
1530 depends on CMD_BOOTP
1532 The name may or may not be qualified with the local domain name.
1534 config BOOTP_PREFER_SERVERIP
1535 bool "serverip variable takes precedent over DHCP server IP."
1536 depends on CMD_BOOTP
1538 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1540 With this option enabled, the 'serverip' variable in the environment
1541 takes precedence over DHCP server IP and will only be set by the DHCP
1542 server if not already set in the environment.
1544 config BOOTP_SUBNETMASK
1545 bool "Request & store 'netmask' from BOOTP/DHCP server"
1547 depends on CMD_BOOTP
1549 config BOOTP_NTPSERVER
1550 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1551 depends on CMD_BOOTP
1556 Selecting this will allow capturing all Ethernet packets and store
1557 them in physical memory in a PCAP formated file,
1558 later to be analyzed by PCAP reader application (IE. WireShark).
1561 bool "Send PXE client arch to BOOTP/DHCP server"
1563 depends on CMD_BOOTP && CMD_PXE
1565 Supported for ARM, ARM64, and x86 for now.
1567 config BOOTP_PXE_CLIENTARCH
1569 depends on BOOTP_PXE
1570 default 0x16 if ARM64
1574 config BOOTP_VCI_STRING
1576 depends on CMD_BOOTP
1577 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1578 default "U-Boot.armv8" if ARM64
1579 default "U-Boot.arm" if ARM
1586 tftpboot - boot image via network using TFTP protocol
1590 depends on CMD_TFTPBOOT
1592 TFTP put command, for uploading files to a server
1596 depends on CMD_TFTPBOOT
1598 Act as a TFTP server and boot the first received file
1600 config NET_TFTP_VARS
1601 bool "Control TFTP timeout and count through environment"
1602 depends on CMD_TFTPBOOT
1605 If set, allows controlling the TFTP timeout through the
1606 environment variable tftptimeout, and the TFTP maximum
1607 timeout count through the variable tftptimeoutcountmax.
1608 If unset, timeout and maximum are hard-defined as 1 second
1609 and 10 timouts per TFTP transfer.
1614 Boot image via network using RARP/TFTP protocol
1620 Boot image via network using NFS protocol.
1626 If set, allows 802.3(clause 22) MII Management functions interface access
1627 The management interface specified in Clause 22 provides
1628 a simple, two signal, serial interface to connect a
1629 Station Management entity and a managed PHY for providing access
1630 to management parameters and services.
1631 The interface is referred to as the MII management interface.
1637 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1638 The MDIO interface is orthogonal to the MII interface and extends
1639 it by adding access to more registers through indirect addressing.
1644 Send ICMP ECHO_REQUEST to network host
1649 Perform CDP network configuration
1655 Synchronize RTC via network
1660 Lookup the IP of a hostname
1662 config CMD_LINK_LOCAL
1666 Acquire a network IP address using the link-local protocol
1673 Allow control of L2 Ethernet switch commands. These are supported
1674 by the vsc9953 Ethernet driver at present. Sub-commands allow
1675 operations such as enabling / disabling a port and
1676 viewing/maintaining the filtering database (FDB)
1682 Boot image via network using PXE protocol
1687 Wait for wake-on-lan Magic Packet
1691 menu "Misc commands"
1694 bool "Enable 'bmp' command"
1695 depends on LCD || DM_VIDEO || VIDEO
1697 This provides a way to obtain information about a BMP-format image
1698 and to display it. BMP (which presumably stands for BitMaP) is a
1699 file format defined by Microsoft which supports images of various
1700 depths, formats and compression methods. Headers on the file
1701 determine the formats used. This command can be used by first loading
1702 the image into RAM, then using this command to look at it or display
1705 config CMD_BOOTCOUNT
1707 depends on BOOTCOUNT_LIMIT
1709 Enable the bootcount command, which allows interrogation and
1710 reset of the bootcounter.
1713 bool "Enable board-specific commands"
1715 (deprecated: instead, please define a Kconfig option for each command)
1717 Some boards have board-specific commands which are only enabled
1718 during developemnt and need to be turned off for production. This
1719 option provides a way to control this. The commands that are enabled
1720 vary depending on the board.
1722 config CMD_BLOCK_CACHE
1723 bool "blkcache - control and stats for block cache"
1724 depends on BLOCK_CACHE
1725 default y if BLOCK_CACHE
1727 Enable the blkcache command, which can be used to control the
1728 operation of the cache functions.
1729 This is most useful when fine-tuning the operation of the cache
1730 during development, but also allows the cache to be disabled when
1731 it might hurt performance (e.g. when using the ums command).
1738 Enable the 'button' command which allows to get the status of
1739 buttons supported by the board. The buttonss can be listed with
1740 'button list' and state can be known with 'button <label>'.
1741 Any button drivers can be controlled with this command, e.g.
1745 bool "icache or dcache"
1747 Enable the "icache" and "dcache" commands
1749 config CMD_CONITRACE
1750 bool "conitrace - trace console input codes"
1752 Enable the 'conitrace' command which displays the codes received
1753 from the console input as hexadecimal numbers.
1756 bool "Enable clear screen command 'cls'"
1757 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1760 Enable the 'cls' command which clears the screen contents
1761 on video frame buffer.
1764 bool "efidebug - display/configure UEFI environment"
1765 depends on EFI_LOADER
1766 select EFI_DEVICE_PATH_TO_TEXT
1769 Enable the 'efidebug' command which provides a subset of UEFI
1770 shell utility with simplified functionality. It will be useful
1771 particularly for managing boot parameters as well as examining
1772 various EFI status for debugging.
1774 config CMD_EXCEPTION
1775 bool "exception - raise exception"
1776 depends on ARM || RISCV || SANDBOX || X86
1778 Enable the 'exception' command which allows to raise an exception.
1785 Enable the 'led' command which allows for control of LEDs supported
1786 by the board. The LEDs can be listed with 'led list' and controlled
1787 with led on/off/togle/blink. Any LED drivers can be controlled with
1788 this command, e.g. led_gpio.
1795 Enable the 'date' command for getting/setting the time/date in RTC
1802 Enable the 'rtc' command for low-level access to RTC devices.
1807 Run commands and summarize execution time.
1810 bool "gettime - read elapsed time"
1812 Enable the 'gettime' command which reads the elapsed time since
1813 U-Boot started running. This shows the time in seconds and
1814 milliseconds. See also the 'bootstage' command which provides more
1815 flexibility for boot timing.
1822 Print bytes from the hardware random number generator.
1828 Delay execution for some time
1831 bool "support for multiprocessor"
1833 This provides an option to brinup
1834 different processors in multiprocessor
1840 Access the system timer.
1846 This provides basic access to the U-Boot's sound support. The main
1847 feature is to play a beep.
1849 sound init - set up sound system
1850 sound play - play a sound
1856 Boot image via local extlinux.conf file
1862 This provides access to the QEMU firmware interface. The main
1863 feature is to allow easy loading of files passed to qemu-system
1864 via -kernel / -initrd
1869 This provides access to Linux PStore with Rammoops backend. The main
1870 feature is to allow to display or save PStore records.
1872 See doc/pstore.rst for more information.
1876 config CMD_PSTORE_MEM_ADDR
1877 hex "Memory Address"
1878 depends on CMD_PSTORE
1880 Base addr used for PStore ramoops memory, should be identical to
1881 ramoops.mem_address parameter used by kernel
1883 config CMD_PSTORE_MEM_SIZE
1885 depends on CMD_PSTORE
1888 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1889 parameter used by kernel, a power of 2 and larger than the sum of the
1892 config CMD_PSTORE_RECORD_SIZE
1893 hex "Dump record size"
1894 depends on CMD_PSTORE
1897 Size of each dump done on oops/panic, should be identical to
1898 ramoops.record_size parameter used by kernel and a power of 2
1901 config CMD_PSTORE_CONSOLE_SIZE
1902 hex "Kernel console log size"
1903 depends on CMD_PSTORE
1906 Size of kernel console log, should be identical to
1907 ramoops.console_size parameter used by kernel and a power of 2
1910 config CMD_PSTORE_FTRACE_SIZE
1911 hex "FTrace log size"
1912 depends on CMD_PSTORE
1915 Size of ftrace log, should be identical to ramoops.ftrace_size
1916 parameter used by kernel and a power of 2
1918 config CMD_PSTORE_PMSG_SIZE
1919 hex "User space message log size"
1920 depends on CMD_PSTORE
1923 Size of user space message log, should be identical to
1924 ramoops.pmsg_size parameter used by kernel and a power of 2
1926 config CMD_PSTORE_ECC_SIZE
1928 depends on CMD_PSTORE
1931 if non-zero, the option enables ECC support and specifies ECC buffer
1932 size in bytes (1 is a special value, means 16 bytes ECC), should be
1933 identical to ramoops.ramoops_ecc parameter used by kernel
1937 source "cmd/mvebu/Kconfig"
1940 bool "terminal - provides a way to attach a serial terminal"
1942 Provides a 'cu'-like serial terminal command. This can be used to
1943 access other serial ports from the system console. The terminal
1944 is very simple with no special processing of characters. As with
1945 cu, you can press ~. (tilde followed by period) to exit.
1948 bool "uuid, guid - generation of unique IDs"
1951 This enables two commands:
1953 uuid - generate random Universally Unique Identifier
1954 guid - generate Globally Unique Identifier based on random UUID
1956 The two commands are very similar except for the endianness of the
1961 source "cmd/ti/Kconfig"
1963 config CMD_BOOTSTAGE
1964 bool "Enable the 'bootstage' command"
1965 depends on BOOTSTAGE
1967 Add a 'bootstage' command which supports printing a report
1968 and un/stashing of bootstage data.
1970 menu "Power commands"
1972 bool "Enable Driver Model PMIC command"
1975 This is the pmic command, based on a driver model pmic's API.
1976 Command features are unchanged:
1977 - list - list pmic devices
1978 - pmic dev <id> - show or [set] operating pmic device (NEW)
1979 - pmic dump - dump registers
1980 - pmic read address - read byte of register at address
1981 - pmic write address - write byte to register at address
1982 The only one change for this command is 'dev' subcommand.
1984 config CMD_REGULATOR
1985 bool "Enable Driver Model REGULATOR command"
1986 depends on DM_REGULATOR
1988 This command is based on driver model regulator's API.
1989 User interface features:
1990 - list - list regulator devices
1991 - regulator dev <id> - show or [set] operating regulator device
1992 - regulator info - print constraints info
1993 - regulator status - print operating status
1994 - regulator value <val] <-f> - print/[set] voltage value [uV]
1995 - regulator current <val> - print/[set] current value [uA]
1996 - regulator mode <id> - print/[set] operating mode id
1997 - regulator enable - enable the regulator output
1998 - regulator disable - disable the regulator output
2000 The '-f' (force) option can be used for set the value which exceeds
2001 the limits, which are found in device-tree and are kept in regulator's
2002 uclass plat structure.
2006 menu "Security commands"
2008 bool "Enable the 'aes' command"
2011 This provides a means to encrypt and decrypt data using the AES
2012 (Advanced Encryption Standard). This algorithm uses a symetric key
2013 and is widely used as a streaming cipher. Different key lengths are
2014 supported by the algorithm but this command only supports 128 bits
2018 bool "Enable the 'blob' command"
2019 depends on !MX6ULL && !MX6SLL && !MX6SL
2020 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
2022 This is used with the Freescale secure boot mechanism.
2024 Freescale's SEC block has built-in Blob Protocol which provides
2025 a method for protecting user-defined data across system power
2026 cycles. SEC block protects data in a data structure called a Blob,
2027 which provides both confidentiality and integrity protection.
2029 Encapsulating data as a blob
2030 Each time that the Blob Protocol is used to protect data, a
2031 different randomly generated key is used to encrypt the data.
2032 This random key is itself encrypted using a key which is derived
2033 from SoC's non-volatile secret key and a 16 bit Key identifier.
2034 The resulting encrypted key along with encrypted data is called a
2035 blob. The non-volatile secure key is available for use only during
2038 During decapsulation, the reverse process is performed to get back
2042 blob enc - encapsulating data as a cryptgraphic blob
2043 blob dec - decapsulating cryptgraphic blob to get the data
2047 blob enc src dst len km
2049 Encapsulate and create blob of data $len bytes long
2050 at address $src and store the result at address $dst.
2051 $km is the 16 byte key modifier is also required for
2052 generation/use as key for cryptographic operation. Key
2053 modifier should be 16 byte long.
2055 blob dec src dst len km
2057 Decapsulate the blob of data at address $src and
2058 store result of $len byte at addr $dst.
2059 $km is the 16 byte key modifier is also required for
2060 generation/use as key for cryptographic operation. Key
2061 modifier should be 16 byte long.
2064 bool "Support 'hash' command"
2067 This provides a way to hash data in memory using various supported
2068 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2069 saved to memory or to an environment variable. It is also possible
2070 to verify a hash against data in memory.
2073 bool "Support the 'hvc' command"
2074 depends on ARM_SMCCC
2076 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2077 development and testing.
2080 bool "Support the 'smc' command"
2081 depends on ARM_SMCCC
2083 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2084 development and testing.
2090 Add -v option to verify data against a hash.
2093 bool "scp03 - SCP03 enable and rotate/provision operations"
2096 This command provides access to a Trusted Application
2097 running in a TEE to request Secure Channel Protocol 03
2098 (SCP03) enablement and/or rotation of its SCP03 keys.
2107 bool "Enable the 'tpm' command"
2108 depends on TPM_V1 || TPM_V2
2109 select CMD_TPM_V1 if TPM_V1
2110 select CMD_TPM_V2 if TPM_V2
2112 This provides a means to talk to a TPM from the command line. A wide
2113 range of commands if provided - see 'tpm help' for details. The
2114 command requires a suitable TPM on your board and the correct driver
2120 bool "Enable the 'tpm test' command"
2123 This provides a a series of tests to confirm that the TPMv1.x is
2124 working correctly. The tests cover initialisation, non-volatile RAM,
2125 extend, global lock and checking that timing is within expectations.
2126 The tests pass correctly on Infineon TPMs but may need to be adjusted
2133 menu "Firmware commands"
2135 bool "Enable crosec command"
2139 Enable command-line access to the Chrome OS EC (Embedded
2140 Controller). This provides the 'crosec' command which has
2141 a number of sub-commands for performing EC tasks such as
2142 updating its flash, accessing a small saved context area
2143 and talking to the I2C bus behind the EC (if there is one).
2146 menu "Filesystem commands"
2148 bool "Enable the 'btrsubvol' command"
2151 This enables the 'btrsubvol' command to list subvolumes
2152 of a BTRFS filesystem. There are no special commands for
2153 listing BTRFS directories or loading BTRFS files - this
2154 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2155 when BTRFS is enabled (see FS_BTRFS).
2158 bool "Enable the 'cbfs' command"
2161 Define this to enable support for reading from a Coreboot
2162 filesystem. This is a ROM-based filesystem used for accessing files
2163 on systems that use coreboot as the first boot-loader and then load
2164 U-Boot to actually boot the Operating System. Available commands are
2165 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2168 bool "Enable the 'cramfs' command"
2169 depends on FS_CRAMFS
2171 This provides commands for dealing with CRAMFS (Compressed ROM
2172 filesystem). CRAMFS is useful when space is tight since files are
2173 compressed. Two commands are provided:
2175 cramfsls - lists files in a cramfs image
2176 cramfsload - loads a file from a cramfs image
2179 bool "ext2 command support"
2182 Enables EXT2 FS command
2185 bool "ext4 command support"
2188 Enables EXT4 FS command
2190 config CMD_EXT4_WRITE
2192 bool "ext4 write command support"
2195 Enables EXT4 FS write command
2198 bool "FAT command support"
2201 Support for the FAT fs
2204 bool "SquashFS command support"
2207 Enables SquashFS filesystem commands (e.g. load, ls).
2209 config CMD_FS_GENERIC
2210 bool "filesystem commands"
2212 Enables filesystem commands (e.g. load, ls) that work for multiple
2216 bool "fsuuid command"
2218 Enables fsuuid command for filesystem UUID.
2221 bool "jffs2 command"
2224 Enables commands to support the JFFS2 (Journalling Flash File System
2225 version 2) filesystem. This enables fsload, ls and fsinfo which
2226 provide the ability to load files, list directories and obtain
2227 filesystem information.
2230 bool "MTD partition support"
2233 MTD partitioning tool support.
2234 It is strongly encouraged to avoid using this command
2235 anymore along with 'sf', 'nand', 'onenand'. One can still
2236 declare the partitions in the mtdparts environment variable
2237 but better use the MTD stack and the 'mtd' command instead.
2239 config CMD_MTDPARTS_SPREAD
2240 bool "Padd partition size to take account of bad blocks"
2241 depends on CMD_MTDPARTS
2243 This enables the 'spread' sub-command of the mtdparts command.
2244 This command will modify the existing mtdparts variable by increasing
2245 the size of the partitions such that 1) each partition's net size is
2246 at least as large as the size specified in the mtdparts variable and
2247 2) each partition starts on a good block.
2249 config CMD_MTDPARTS_SHOW_NET_SIZES
2250 bool "Show net size (w/o bad blocks) of partitions"
2251 depends on CMD_MTDPARTS
2253 Adds two columns to the printed partition table showing the
2254 effective usable size of a partition, if bad blocks are taken
2257 config MTDIDS_DEFAULT
2258 string "Default MTD IDs"
2259 depends on MTD || SPI_FLASH
2261 Defines a default MTD IDs list for use with MTD partitions in the
2262 Linux MTD command line partitions format.
2264 config MTDPARTS_DEFAULT
2265 string "Default MTD partition scheme"
2266 depends on MTD || SPI_FLASH
2268 Defines a default MTD partitioning scheme in the Linux MTD command
2269 line partitions format
2272 bool "reiser - Access to reiserfs filesystems"
2274 This provides two commands which operate on a resierfs filesystem,
2275 commonly used some years ago:
2277 reiserls - list files
2278 reiserload - load a file
2281 bool "yaffs2 - Access of YAFFS2 filesystem"
2285 This provides commands for accessing a YAFFS2 filesystem. Yet
2286 Another Flash Filesystem 2 is a filesystem designed specifically
2287 for NAND flash. It incorporates bad-block management and ensures
2288 that device writes are sequential regardless of filesystem
2292 bool "zfs - Access of ZFS filesystem"
2294 This provides commands to accessing a ZFS filesystem, commonly used
2295 on Solaris systems. Two sub-commands are provided:
2297 zfsls - list files in a directory
2298 zfsload - load a file
2300 See doc/README.zfs for more details.
2304 menu "Debug commands"
2309 The bedbug (emBEDded deBUGger) command provides debugging features
2310 for some PowerPC processors. For details please see the
2311 documentation in doc/README.bedbug.
2313 config CMD_CBSYSINFO
2316 default y if SYS_COREBOOT
2318 This provides information about the coreboot sysinfo table stored in
2319 memory by coreboot before jumping to U-Boot. It can be useful for
2320 debugging the beaaviour of coreboot or U-Boot.
2323 bool "diag - Board diagnostics"
2325 This command provides access to board diagnostic tests. These are
2326 called Power-on Self Tests (POST). The command allows listing of
2327 available tests and running either all the tests, or specific tests
2331 bool "irq - Show information about interrupts"
2332 depends on !ARM && !MIPS && !RISCV && !SH
2334 This enables two commands:
2336 interrupts - enable or disable interrupts
2337 irqinfo - print device-specific interrupt information
2340 bool "kgdb - Allow debugging of U-Boot with gdb"
2343 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2344 over a serial link for debugging purposes. This allows
2345 single-stepping, inspecting variables, etc. This is supported only
2346 on PowerPC at present.
2349 bool "log - Generation, control and access to logging"
2353 This provides access to logging features. It allows the output of
2354 log data to be controlled to a limited extent (setting up the default
2355 maximum log level for emitting of records). It also provides access
2356 to a command used for testing the log system.
2359 bool "trace - Support tracing of function calls and timing"
2361 Enables a command to control using of function tracing within
2362 U-Boot. This allows recording of call traces including timing
2363 information. The command can write data to memory for exporting
2364 for analysis (e.g. using bootchart). See doc/README.trace for full
2368 bool "avb - Android Verified Boot 2.0 operations"
2369 depends on AVB_VERIFY
2372 Enables a "avb" command to perform verification of partitions using
2373 Android Verified Boot 2.0 functionality. It includes such subcommands:
2374 avb init - initialize avb2 subsystem
2375 avb read_rb - read rollback index
2376 avb write_rb - write rollback index
2377 avb is_unlocked - check device lock state
2378 avb get_uuid - read and print uuid of a partition
2379 avb read_part - read data from partition
2380 avb read_part_hex - read data from partition and output to stdout
2381 avb write_part - write data to partition
2382 avb verify - run full verification chain
2384 config CMD_STACKPROTECTOR_TEST
2385 bool "Test command for stack protector"
2386 depends on STACKPROTECTOR
2388 Enable stackprot_test command
2389 The stackprot_test command will force a stack overrun to test
2390 the stack smashing detection mechanisms.
2395 tristate "Enable UBI - Unsorted block images commands"
2398 UBI is a software layer above MTD layer which admits use of LVM-like
2399 logical volumes on top of MTD devices, hides some complexities of
2400 flash chips like wear and bad blocks and provides some other useful
2401 capabilities. Please, consult the MTD web site for more details
2402 (www.linux-mtd.infradead.org). Activate this option if you want
2403 to use U-Boot UBI commands.
2404 It is also strongly encouraged to also enable CONFIG_MTD to get full
2407 config CMD_UBI_RENAME
2408 bool "Enable rename"
2412 Enable a "ubi" command to rename ubi volume:
2413 ubi rename <oldname> <newname>
2416 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2418 default y if CMD_UBI
2421 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob