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_SUPPORT
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'
620 Infinite write loop on address range
627 Compute MD5 checksum.
632 depends on CMD_MD5SUM
634 Add -v option to verify data against an MD5 checksum.
639 Display memory information.
642 bool "md, mm, nm, mw, cp, cmp, base, loop"
647 mm - memory modify (auto-incrementing address)
648 nm - memory modify (constant address)
649 mw - memory write (fill)
652 base - print or set address offset
653 loop - initialize loop on address range
655 config CMD_MEM_SEARCH
656 bool "ms - Memory search"
658 Memory-search command
660 This allows searching through a region of memory looking for hex
661 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
662 support it). It is also possible to search for a string. The
663 command accepts a memory range and a list of values to search for.
664 The values need to appear in memory in the same order they are given
665 in the command. At most 10 matches can be returned at a time, but
666 pressing return will show the next 10 matches. Environment variables
667 are set for use with scripting (memmatches, memaddr, mempos).
670 bool "Enable cyclic md/mw commands"
671 depends on CMD_MEMORY
673 Add the "mdc" and "mwc" memory commands. These are cyclic
678 This command will print 4 bytes (10,11,12,13) each 500 ms.
680 => mwc.l 100 12345678 10
681 This command will write 12345678 to address 100 all 10 ms.
686 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
688 random - fill memory with random data
693 Simple RAM read/write test.
697 config SYS_ALT_MEMTEST
698 bool "Alternative test"
700 Use a more complete alternative memory test.
704 config SYS_ALT_MEMTEST_BITFLIP
708 The alternative memory test includes bitflip test since 2020.07.
709 The bitflip test significantly increases the overall test time.
710 Bitflip test can optionally be disabled here.
714 config SYS_MEMTEST_START
715 hex "default start address for mtest"
718 This is the default start address for mtest for simple read/write
719 test. If no arguments are given to mtest, default address is used
722 config SYS_MEMTEST_END
723 hex "default end address for mtest"
726 This is the default end address for mtest for simple read/write
727 test. If no arguments are given to mtest, default address is used
736 Compute SHA1 checksum.
738 config SHA1SUM_VERIFY
740 depends on CMD_SHA1SUM
742 Add -v option to verify data against a SHA1 checksum.
745 bool "strings - display strings in memory"
747 This works similarly to the Unix 'strings' command except that it
748 works with a memory range. String of printable characters found
749 within the range are displayed. The minimum number of characters
750 for a sequence to be considered a string can be provided.
754 menu "Compression commands"
758 default y if CMD_BOOTI
761 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
766 default y if CMD_BOOTI
769 Support decompressing an LZ4 image from memory region.
773 default y if CMD_BOOTI
776 Uncompress a zip-compressed memory region.
780 select GZIP_COMPRESSED
782 Compress a memory region with zlib deflate method.
786 menu "Device access commands"
789 #depends on FLASH_CFI_DRIVER
792 ARM Ltd reference designs flash partition access
795 bool "adc - Access Analog to Digital Converters info and data"
797 depends on DM_REGULATOR
799 Shows ADC device info and permit printing one-shot analog converted
800 data from a named Analog to Digital Converter.
805 depends on PARTITIONS
807 Read/modify/write the fields of Bootloader Control Block, usually
808 stored on the flash "misc" partition with its structure defined in:
809 https://android.googlesource.com/platform/bootable/recovery/+/master/
810 bootloader_message/include/bootloader_message/bootloader_message.h
812 Some real-life use-cases include (but are not limited to):
813 - Determine the "boot reason" (and act accordingly):
814 https://source.android.com/devices/bootloader/boot-reason
815 - Get/pass a list of commands from/to recovery:
816 https://android.googlesource.com/platform/bootable/recovery
817 - Inspect/dump the contents of the BCB fields
820 bool "bind/unbind - Bind or unbind a device to/from a driver"
823 Bind or unbind a device to/from a driver from the command line.
824 This is useful in situations where a device may be handled by several
825 drivers. For example, this can be used to bind a UDC to the usb ether
826 gadget driver from the command line.
829 bool "clk - Show clock frequencies"
832 Shows clock frequences by calling a sock_clk_dump() hook function.
833 This is depreated in favour of using the CLK uclass and accessing
834 clock values from associated drivers. However currently no command
838 bool "demo - Demonstration commands for driver model"
841 Provides a 'demo' command which can be used to play around with
842 driver model. To use this properly you will need to enable one or
843 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
844 Otherwise you will always get an empty list of devices. The demo
845 devices are defined in the sandbox device tree, so the easiest
846 option is to use sandbox and pass the -d point to sandbox's
853 Enables the command "dfu" which is used to have U-Boot create a DFU
854 class device via USB. This command requires that the "dfu_alt_info"
855 environment variable be set and define the alt settings to expose to
859 bool "dm - Access to driver model information"
862 Provides access to driver model data structures and information,
863 such as a list of devices, list of uclasses and the state of each
864 device (e.g. activated). This is not required for operation, but
865 can be useful to see the state of driver model for debugging or
869 bool "fastboot - Android fastboot support"
872 This enables the command "fastboot" which enables the Android
873 fastboot mode for the platform. Fastboot is a protocol for
874 downloading images, flashing and device control used on
875 Android devices. Fastboot requires either the network stack
876 enabled or support for acting as a USB device.
878 See doc/android/fastboot.rst for more information.
881 bool "flinfo, erase, protect"
883 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
886 flinfo - print FLASH memory information
888 protect - enable or disable FLASH write protection
897 config CMD_FPGA_LOADBP
898 bool "fpga loadbp - load partial bitstream (Xilinx only)"
901 Supports loading an FPGA device from a bitstream buffer containing
904 config CMD_FPGA_LOADFS
905 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
908 Supports loading an FPGA device from a FAT filesystem.
910 config CMD_FPGA_LOADMK
911 bool "fpga loadmk - load bitstream from image"
914 Supports loading an FPGA device from a image generated by mkimage.
916 config CMD_FPGA_LOADP
917 bool "fpga loadp - load partial bitstream"
920 Supports loading an FPGA device from a bitstream buffer containing
923 config CMD_FPGA_LOAD_SECURE
924 bool "fpga loads - loads secure bitstreams (Xilinx only)"
927 Enables the fpga loads command which is used to load secure
928 (authenticated or encrypted or both) bitstreams on to FPGA.
931 bool "fpgad - dump FPGA registers"
933 (legacy, needs conversion to driver model)
934 Provides a way to dump FPGA registers by calling the board-specific
935 fpga_get_reg() function. This functions similarly to the 'md'
939 bool "fuse - support for the fuse subssystem"
941 (deprecated - needs conversion to driver model)
942 This allows reading, sensing, programming or overriding fuses
943 which control the behaviour of the device. The command uses the
955 Control PWM channels, this allows invert/config/enable/disable PWM channels.
958 bool "GPT (GUID Partition Table) command"
960 select HAVE_BLOCK_DEVICE
961 select PARTITION_UUIDS
964 Enable the 'gpt' command to ready and write GPT style partition
968 bool "GPT Random UUID generation"
971 Enable the generation of partitions with random UUIDs if none
974 config CMD_GPT_RENAME
975 bool "GPT partition renaming commands"
978 Enables the 'gpt' command to interchange names on two GPT
979 partitions via the 'gpt swap' command or to rename single
980 partitions via the 'rename' command.
983 bool "ide - Support for IDE drivers"
986 Provides an 'ide' command which allows accessing the IDE drive,
987 reseting the IDE interface, printing the partition table and
988 geting device info. It also enables the 'diskboot' command which
989 permits booting from an IDE drive.
992 bool "io - Support for performing I/O accesses"
994 Provides an 'iod' command to display I/O space and an 'iow' command
995 to write values to the I/O space. This can be useful for manually
996 checking the state of devices during boot when debugging device
1000 bool "iotrace - Support for tracing I/O activity"
1002 Provides an 'iotrace' command which supports recording I/O reads and
1003 writes in a trace buffer in memory . It also maintains a checksum
1004 of the trace records (even if space is exhausted) so that the
1005 sequence of I/O accesses can be verified.
1007 When debugging drivers it is useful to see what I/O accesses were
1008 done and in what order.
1010 Even if the individual accesses are of little interest it can be
1011 useful to verify that the access pattern is consistent each time
1012 an operation is performed. In this case a checksum can be used to
1013 characterise the operation of a driver. The checksum can be compared
1014 across different runs of the operation to verify that the driver is
1017 In particular, when performing major refactoring of the driver, where
1018 the access pattern should not change, the checksum provides assurance
1019 that the refactoring work has not broken the driver.
1021 This works by sneaking into the io.h heder for an architecture and
1022 redirecting I/O accesses through iotrace's tracing mechanism.
1024 For now no commands are provided to examine the trace buffer. The
1025 format is fairly simple, so 'md' is a reasonable substitute.
1027 Note: The checksum feature is only useful for I/O regions where the
1028 contents do not change outside of software control. Where this is not
1029 suitable you can fall back to manually comparing the addresses. It
1030 might be useful to enhance tracing to only checksum the accesses and
1031 not the data read/written.
1041 bool "w1 - Support for Dallas 1-Wire protocol"
1043 Dallas 1-wire protocol support
1049 Load a binary file over serial line.
1055 Load an S-Record file over serial line
1059 bool "lsblk - list block drivers and devices"
1061 Print list of available block device drivers, and for each, the list
1062 of known block devices.
1065 bool "MBR (Master Boot Record) command"
1066 select DOS_PARTITION
1067 select HAVE_BLOCK_DEVICE
1069 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1070 style partition tables.
1076 Enable the command "misc" for accessing miscellaneous devices with
1077 a MISC uclass driver. The command provides listing all MISC devices
1078 as well as read and write functionalities via their drivers.
1084 MMC memory mapped support.
1088 config CMD_BKOPS_ENABLE
1089 bool "mmc bkops enable"
1093 Enable command for setting manual background operations handshake
1094 on a eMMC device. The feature is optionally available on eMMC devices
1095 conforming to standard >= 4.41.
1098 bool "Enable support for RPMB in the mmc command"
1099 depends on SUPPORT_EMMC_RPMB
1101 Enable the commands for reading, writing and programming the
1102 key for the Replay Protection Memory Block partition in eMMC.
1104 config CMD_MMC_SWRITE
1106 depends on MMC_WRITE
1109 Enable support for the "mmc swrite" command to write Android sparse
1118 Enable storage cloning over block devices, useful for
1119 initial flashing by external block device without network
1122 config CMD_OPTEE_RPMB
1123 bool "Enable read/write support on RPMB via OPTEE"
1124 depends on SUPPORT_EMMC_RPMB && OPTEE
1126 Enable the commands for reading, writing persistent named values
1127 in the Replay Protection Memory Block partition in eMMC by
1128 using Persistent Objects in OPTEE
1133 select MTD_PARTITIONS
1135 MTD commands support.
1139 depends on MULTIPLEXER
1141 List, select, and deselect mux controllers on the fly.
1145 default y if NAND_SUNXI
1146 depends on MTD_RAW_NAND
1151 config CMD_NAND_TRIMFFS
1152 bool "nand write.trimffs"
1153 default y if ARCH_SUNXI
1155 Allows one to skip empty pages when flashing something on a NAND.
1157 config CMD_NAND_LOCK_UNLOCK
1158 bool "nand lock/unlock"
1160 NAND locking support.
1162 config CMD_NAND_TORTURE
1165 NAND torture support.
1174 NVM Express device support
1177 bool "onenand - access to onenand device"
1180 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1181 various useful features. This command allows reading, writing,
1182 and erasing blocks. It allso provides a way to show and change
1183 bad blocks, and test the device.
1188 Enable the 'osd' command which allows to query information from and
1189 write text data to a on-screen display (OSD) device; a virtual device
1190 associated with a display capable of displaying a text overlay on the
1191 display it's associated with..
1195 select HAVE_BLOCK_DEVICE
1196 select PARTITION_UUIDS
1198 Read and display information about the partition table on
1202 bool "pci - Access PCI devices"
1204 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1205 used on some devices to allow the CPU to communicate with its
1206 peripherals. Sub-commands allow bus enumeration, displaying and
1207 changing configuration space and a few other features.
1210 bool "pinmux - show pins muxing"
1212 default y if PINCTRL
1214 Parse all available pin-controllers and show pins muxing. This
1215 is useful for debug purpoer to check the pin muxing and to know if
1216 a pin is configured as a GPIO or as an alternate function.
1221 Poweroff/Shutdown the system
1224 bool "read - Read binary data from a partition"
1226 Provides low-level access to the data in a partition.
1228 config CMD_REMOTEPROC
1230 depends on REMOTEPROC
1232 Support for Remote Processor control
1235 bool "sata - Access SATA subsystem"
1238 SATA (Serial Advanced Technology Attachment) is a serial bus
1239 standard for connecting to hard drives and other storage devices.
1240 This command provides information about attached devices and allows
1241 reading, writing and other operations.
1243 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1244 Attachment, where AT refers to an IBM AT (Advanced Technology)
1245 computer released in 1984.
1248 bool "saves - Save a file over serial in S-Record format"
1250 Provides a way to save a binary file using the Motorola S-Record
1251 format over the serial line.
1254 bool "scsi - Access to SCSI devices"
1257 This provides a 'scsi' command which provides access to SCSI (Small
1258 Computer System Interface) devices. The command provides a way to
1259 scan the bus, reset the bus, read and write data and get information
1263 bool "sdram - Print SDRAM configuration information"
1265 Provides information about attached SDRAM. This assumed that the
1266 SDRAM has an EEPROM with information that can be read using the
1267 I2C bus. This is only available on some boards.
1271 depends on DM_SPI_FLASH || SPI_FLASH
1272 default y if DM_SPI_FLASH
1277 bool "sf test - Allow testing of SPI flash"
1280 Provides a way to test that SPI flash is working correctly. The
1281 test is destructive, in that an area of SPI flash must be provided
1282 for the test to use. Performance information is also provided,
1283 measuring the performance of reading, writing and erasing in
1284 Mbps (Million Bits Per Second). This value should approximately
1285 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1286 everything is working properly.
1289 bool "sspi - Command to access spi device"
1292 SPI utility command.
1294 config DEFAULT_SPI_BUS
1295 int "default spi bus used by sspi command"
1299 config DEFAULT_SPI_MODE
1300 hex "default spi mode used by sspi command (see include/spi.h)"
1305 bool "tsi148 - Command to access tsi148 device"
1307 This provides various sub-commands to initialise and configure the
1308 Turndra tsi148 device. See the command help for full details.
1311 bool "Enable UFS - Universal Flash Subsystem commands"
1314 "This provides commands to initialise and configure universal flash
1318 bool "universe - Command to set up the Turndra Universe controller"
1320 This allows setting up the VMEbus provided by this controller.
1321 See the command help for full details.
1326 select HAVE_BLOCK_DEVICE
1332 select USB_FUNCTION_SDP
1334 Enables the command "sdp" which is used to have U-Boot emulating the
1335 Serial Download Protocol (SDP) via USB.
1339 depends on USB_FUNCTION_ROCKUSB
1341 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1342 read/write info, image to/from devices. This enable rockusb command
1343 support to communication with rockusb device. for more detail about
1344 this command, please read doc/README.rockusb.
1346 config CMD_USB_MASS_STORAGE
1347 bool "UMS usb mass storage"
1348 depends on USB_GADGET_DOWNLOAD
1349 select USB_FUNCTION_MASS_STORAGE
1350 depends on BLK && USB_GADGET
1352 Enables the command "ums" and the USB mass storage support to the
1353 export a block device: U-Boot, the USB device, acts as a simple
1354 external hard drive plugged on the host USB port.
1357 bool "Xen para-virtualized block device"
1361 Xen para-virtualized block device support
1366 depends on HAVE_BLOCK_DEVICE
1369 VirtIO block device support
1375 This provides commands to control the watchdog timer devices.
1381 Enable the command "axi" for accessing AXI (Advanced eXtensible
1382 Interface) busses, a on-chip interconnect specification for managing
1383 functional blocks in SoC designs, which is also often used in designs
1384 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1388 menu "Shell scripting commands"
1394 Echo args to console
1400 Return true/false on integer compare.
1406 Run script from memory
1412 Evaluate boolean and math expressions and store the result in an env
1414 Also supports loading the value at a memory location into a variable.
1415 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1419 menu "Android support commands"
1421 config CMD_AB_SELECT
1424 depends on ANDROID_AB
1426 On Android devices with more than one boot slot (multiple copies of
1427 the kernel and system images) this provides a command to select which
1428 slot should be used to boot from and register the boot attempt. This
1429 is used by the new A/B update model where one slot is updated in the
1430 background while running from the other slot.
1437 bool "Network commands"
1447 bootp - boot image via network using BOOTP/TFTP protocol
1451 depends on CMD_BOOTP
1453 Boot image via network using DHCP/TFTP protocol
1455 config BOOTP_BOOTPATH
1456 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1458 depends on CMD_BOOTP
1460 Even though the config is called BOOTP_BOOTPATH, it stores the
1461 path in the variable 'rootpath'.
1464 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1466 depends on CMD_BOOTP
1468 The primary DNS server is stored as 'dnsip'. If two servers are
1469 returned, you must set BOOTP_DNS2 to store that second server IP
1473 bool "Store 'dnsip2' from BOOTP/DHCP server"
1474 depends on BOOTP_DNS
1476 If a DHCP client requests the DNS server IP from a DHCP server,
1477 it is possible that more than one DNS serverip is offered to the
1478 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1479 server IP will be stored in the additional environment
1480 variable "dnsip2". The first DNS serverip is always
1481 stored in the variable "dnsip", when BOOTP_DNS is defined.
1483 config BOOTP_GATEWAY
1484 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1486 depends on CMD_BOOTP
1488 config BOOTP_HOSTNAME
1489 bool "Request & store 'hostname' from BOOTP/DHCP server"
1491 depends on CMD_BOOTP
1493 The name may or may not be qualified with the local domain name.
1495 config BOOTP_PREFER_SERVERIP
1496 bool "serverip variable takes precedent over DHCP server IP."
1497 depends on CMD_BOOTP
1499 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1501 With this option enabled, the 'serverip' variable in the environment
1502 takes precedence over DHCP server IP and will only be set by the DHCP
1503 server if not already set in the environment.
1505 config BOOTP_SUBNETMASK
1506 bool "Request & store 'netmask' from BOOTP/DHCP server"
1508 depends on CMD_BOOTP
1510 config BOOTP_NTPSERVER
1511 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1512 depends on CMD_BOOTP
1517 Selecting this will allow capturing all Ethernet packets and store
1518 them in physical memory in a PCAP formated file,
1519 later to be analyzed by PCAP reader application (IE. WireShark).
1522 bool "Send PXE client arch to BOOTP/DHCP server"
1524 depends on CMD_BOOTP && CMD_PXE
1526 Supported for ARM, ARM64, and x86 for now.
1528 config BOOTP_PXE_CLIENTARCH
1530 depends on BOOTP_PXE
1531 default 0x16 if ARM64
1535 config BOOTP_VCI_STRING
1537 depends on CMD_BOOTP
1538 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1539 default "U-Boot.armv8" if ARM64
1540 default "U-Boot.arm" if ARM
1547 tftpboot - boot image via network using TFTP protocol
1551 depends on CMD_TFTPBOOT
1553 TFTP put command, for uploading files to a server
1557 depends on CMD_TFTPBOOT
1559 Act as a TFTP server and boot the first received file
1561 config NET_TFTP_VARS
1562 bool "Control TFTP timeout and count through environment"
1563 depends on CMD_TFTPBOOT
1566 If set, allows controlling the TFTP timeout through the
1567 environment variable tftptimeout, and the TFTP maximum
1568 timeout count through the variable tftptimeoutcountmax.
1569 If unset, timeout and maximum are hard-defined as 1 second
1570 and 10 timouts per TFTP transfer.
1575 Boot image via network using RARP/TFTP protocol
1581 Boot image via network using NFS protocol.
1587 If set, allows 802.3(clause 22) MII Management functions interface access
1588 The management interface specified in Clause 22 provides
1589 a simple, two signal, serial interface to connect a
1590 Station Management entity and a managed PHY for providing access
1591 to management parameters and services.
1592 The interface is referred to as the MII management interface.
1598 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1599 The MDIO interface is orthogonal to the MII interface and extends
1600 it by adding access to more registers through indirect addressing.
1605 Send ICMP ECHO_REQUEST to network host
1610 Perform CDP network configuration
1616 Synchronize RTC via network
1621 Lookup the IP of a hostname
1623 config CMD_LINK_LOCAL
1627 Acquire a network IP address using the link-local protocol
1634 Allow control of L2 Ethernet switch commands. These are supported
1635 by the vsc9953 Ethernet driver at present. Sub-commands allow
1636 operations such as enabling / disabling a port and
1637 viewing/maintaining the filtering database (FDB)
1643 Boot image via network using PXE protocol
1648 Wait for wake-on-lan Magic Packet
1652 menu "Misc commands"
1655 bool "Enable 'bmp' command"
1656 depends on LCD || DM_VIDEO || VIDEO
1658 This provides a way to obtain information about a BMP-format image
1659 and to display it. BMP (which presumably stands for BitMaP) is a
1660 file format defined by Microsoft which supports images of various
1661 depths, formats and compression methods. Headers on the file
1662 determine the formats used. This command can be used by first loading
1663 the image into RAM, then using this command to look at it or display
1666 config CMD_BOOTCOUNT
1668 depends on BOOTCOUNT_LIMIT
1670 Enable the bootcount command, which allows interrogation and
1671 reset of the bootcounter.
1674 bool "Enable board-specific commands"
1676 (deprecated: instead, please define a Kconfig option for each command)
1678 Some boards have board-specific commands which are only enabled
1679 during developemnt and need to be turned off for production. This
1680 option provides a way to control this. The commands that are enabled
1681 vary depending on the board.
1683 config CMD_BLOCK_CACHE
1684 bool "blkcache - control and stats for block cache"
1685 depends on BLOCK_CACHE
1686 default y if BLOCK_CACHE
1688 Enable the blkcache command, which can be used to control the
1689 operation of the cache functions.
1690 This is most useful when fine-tuning the operation of the cache
1691 during development, but also allows the cache to be disabled when
1692 it might hurt performance (e.g. when using the ums command).
1699 Enable the 'button' command which allows to get the status of
1700 buttons supported by the board. The buttonss can be listed with
1701 'button list' and state can be known with 'button <label>'.
1702 Any button drivers can be controlled with this command, e.g.
1706 bool "icache or dcache"
1708 Enable the "icache" and "dcache" commands
1710 config CMD_CONITRACE
1711 bool "conitrace - trace console input codes"
1713 Enable the 'conitrace' command which displays the codes received
1714 from the console input as hexadecimal numbers.
1717 bool "Enable clear screen command 'cls'"
1718 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1721 Enable the 'cls' command which clears the screen contents
1722 on video frame buffer.
1725 bool "efidebug - display/configure UEFI environment"
1726 depends on EFI_LOADER
1727 select EFI_DEVICE_PATH_TO_TEXT
1730 Enable the 'efidebug' command which provides a subset of UEFI
1731 shell utility with simplified functionality. It will be useful
1732 particularly for managing boot parameters as well as examining
1733 various EFI status for debugging.
1735 config CMD_EXCEPTION
1736 bool "exception - raise exception"
1737 depends on ARM || RISCV || SANDBOX || X86
1739 Enable the 'exception' command which allows to raise an exception.
1746 Enable the 'led' command which allows for control of LEDs supported
1747 by the board. The LEDs can be listed with 'led list' and controlled
1748 with led on/off/togle/blink. Any LED drivers can be controlled with
1749 this command, e.g. led_gpio.
1756 Enable the 'date' command for getting/setting the time/date in RTC
1763 Enable the 'rtc' command for low-level access to RTC devices.
1768 Run commands and summarize execution time.
1771 bool "gettime - read elapsed time"
1773 Enable the 'gettime' command which reads the elapsed time since
1774 U-Boot started running. This shows the time in seconds and
1775 milliseconds. See also the 'bootstage' command which provides more
1776 flexibility for boot timing.
1783 Print bytes from the hardware random number generator.
1789 Delay execution for some time
1792 bool "support for multiprocessor"
1794 This provides an option to brinup
1795 different processors in multiprocessor
1801 Access the system timer.
1807 This provides basic access to the U-Boot's sound support. The main
1808 feature is to play a beep.
1810 sound init - set up sound system
1811 sound play - play a sound
1817 Boot image via local extlinux.conf file
1823 This provides access to the QEMU firmware interface. The main
1824 feature is to allow easy loading of files passed to qemu-system
1825 via -kernel / -initrd
1830 This provides access to Linux PStore with Rammoops backend. The main
1831 feature is to allow to display or save PStore records.
1833 See doc/pstore.rst for more information.
1837 config CMD_PSTORE_MEM_ADDR
1838 hex "Memory Address"
1839 depends on CMD_PSTORE
1841 Base addr used for PStore ramoops memory, should be identical to
1842 ramoops.mem_address parameter used by kernel
1844 config CMD_PSTORE_MEM_SIZE
1846 depends on CMD_PSTORE
1849 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1850 parameter used by kernel, a power of 2 and larger than the sum of the
1853 config CMD_PSTORE_RECORD_SIZE
1854 hex "Dump record size"
1855 depends on CMD_PSTORE
1858 Size of each dump done on oops/panic, should be identical to
1859 ramoops.record_size parameter used by kernel and a power of 2
1862 config CMD_PSTORE_CONSOLE_SIZE
1863 hex "Kernel console log size"
1864 depends on CMD_PSTORE
1867 Size of kernel console log, should be identical to
1868 ramoops.console_size parameter used by kernel and a power of 2
1871 config CMD_PSTORE_FTRACE_SIZE
1872 hex "FTrace log size"
1873 depends on CMD_PSTORE
1876 Size of ftrace log, should be identical to ramoops.ftrace_size
1877 parameter used by kernel and a power of 2
1879 config CMD_PSTORE_PMSG_SIZE
1880 hex "User space message log size"
1881 depends on CMD_PSTORE
1884 Size of user space message log, should be identical to
1885 ramoops.pmsg_size parameter used by kernel and a power of 2
1887 config CMD_PSTORE_ECC_SIZE
1889 depends on CMD_PSTORE
1892 if non-zero, the option enables ECC support and specifies ECC buffer
1893 size in bytes (1 is a special value, means 16 bytes ECC), should be
1894 identical to ramoops.ramoops_ecc parameter used by kernel
1898 source "cmd/mvebu/Kconfig"
1901 bool "terminal - provides a way to attach a serial terminal"
1903 Provides a 'cu'-like serial terminal command. This can be used to
1904 access other serial ports from the system console. The terminal
1905 is very simple with no special processing of characters. As with
1906 cu, you can press ~. (tilde followed by period) to exit.
1909 bool "uuid, guid - generation of unique IDs"
1912 This enables two commands:
1914 uuid - generate random Universally Unique Identifier
1915 guid - generate Globally Unique Identifier based on random UUID
1917 The two commands are very similar except for the endianness of the
1922 source "cmd/ti/Kconfig"
1924 config CMD_BOOTSTAGE
1925 bool "Enable the 'bootstage' command"
1926 depends on BOOTSTAGE
1928 Add a 'bootstage' command which supports printing a report
1929 and un/stashing of bootstage data.
1931 menu "Power commands"
1933 bool "Enable Driver Model PMIC command"
1936 This is the pmic command, based on a driver model pmic's API.
1937 Command features are unchanged:
1938 - list - list pmic devices
1939 - pmic dev <id> - show or [set] operating pmic device (NEW)
1940 - pmic dump - dump registers
1941 - pmic read address - read byte of register at address
1942 - pmic write address - write byte to register at address
1943 The only one change for this command is 'dev' subcommand.
1945 config CMD_REGULATOR
1946 bool "Enable Driver Model REGULATOR command"
1947 depends on DM_REGULATOR
1949 This command is based on driver model regulator's API.
1950 User interface features:
1951 - list - list regulator devices
1952 - regulator dev <id> - show or [set] operating regulator device
1953 - regulator info - print constraints info
1954 - regulator status - print operating status
1955 - regulator value <val] <-f> - print/[set] voltage value [uV]
1956 - regulator current <val> - print/[set] current value [uA]
1957 - regulator mode <id> - print/[set] operating mode id
1958 - regulator enable - enable the regulator output
1959 - regulator disable - disable the regulator output
1961 The '-f' (force) option can be used for set the value which exceeds
1962 the limits, which are found in device-tree and are kept in regulator's
1963 uclass plat structure.
1967 menu "Security commands"
1969 bool "Enable the 'aes' command"
1972 This provides a means to encrypt and decrypt data using the AES
1973 (Advanced Encryption Standard). This algorithm uses a symetric key
1974 and is widely used as a streaming cipher. Different key lengths are
1975 supported by the algorithm but this command only supports 128 bits
1979 bool "Enable the 'blob' command"
1980 depends on !MX6ULL && !MX6SLL && !MX6SL
1981 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
1983 This is used with the Freescale secure boot mechanism.
1985 Freescale's SEC block has built-in Blob Protocol which provides
1986 a method for protecting user-defined data across system power
1987 cycles. SEC block protects data in a data structure called a Blob,
1988 which provides both confidentiality and integrity protection.
1990 Encapsulating data as a blob
1991 Each time that the Blob Protocol is used to protect data, a
1992 different randomly generated key is used to encrypt the data.
1993 This random key is itself encrypted using a key which is derived
1994 from SoC's non-volatile secret key and a 16 bit Key identifier.
1995 The resulting encrypted key along with encrypted data is called a
1996 blob. The non-volatile secure key is available for use only during
1999 During decapsulation, the reverse process is performed to get back
2003 blob enc - encapsulating data as a cryptgraphic blob
2004 blob dec - decapsulating cryptgraphic blob to get the data
2008 blob enc src dst len km
2010 Encapsulate and create blob of data $len bytes long
2011 at address $src and store the result at address $dst.
2012 $km is the 16 byte key modifier is also required for
2013 generation/use as key for cryptographic operation. Key
2014 modifier should be 16 byte long.
2016 blob dec src dst len km
2018 Decapsulate the blob of data at address $src and
2019 store result of $len byte at addr $dst.
2020 $km is the 16 byte key modifier is also required for
2021 generation/use as key for cryptographic operation. Key
2022 modifier should be 16 byte long.
2025 bool "Support 'hash' command"
2028 This provides a way to hash data in memory using various supported
2029 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2030 saved to memory or to an environment variable. It is also possible
2031 to verify a hash against data in memory.
2034 bool "Support the 'hvc' command"
2035 depends on ARM_SMCCC
2037 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2038 development and testing.
2041 bool "Support the 'smc' command"
2042 depends on ARM_SMCCC
2044 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2045 development and testing.
2051 Add -v option to verify data against a hash.
2054 bool "scp03 - SCP03 enable and rotate/provision operations"
2057 This command provides access to a Trusted Application
2058 running in a TEE to request Secure Channel Protocol 03
2059 (SCP03) enablement and/or rotation of its SCP03 keys.
2068 bool "Enable the 'tpm' command"
2069 depends on TPM_V1 || TPM_V2
2070 select CMD_TPM_V1 if TPM_V1
2071 select CMD_TPM_V2 if TPM_V2
2073 This provides a means to talk to a TPM from the command line. A wide
2074 range of commands if provided - see 'tpm help' for details. The
2075 command requires a suitable TPM on your board and the correct driver
2081 bool "Enable the 'tpm test' command"
2084 This provides a a series of tests to confirm that the TPMv1.x is
2085 working correctly. The tests cover initialisation, non-volatile RAM,
2086 extend, global lock and checking that timing is within expectations.
2087 The tests pass correctly on Infineon TPMs but may need to be adjusted
2094 menu "Firmware commands"
2096 bool "Enable crosec command"
2100 Enable command-line access to the Chrome OS EC (Embedded
2101 Controller). This provides the 'crosec' command which has
2102 a number of sub-commands for performing EC tasks such as
2103 updating its flash, accessing a small saved context area
2104 and talking to the I2C bus behind the EC (if there is one).
2107 menu "Filesystem commands"
2109 bool "Enable the 'btrsubvol' command"
2112 This enables the 'btrsubvol' command to list subvolumes
2113 of a BTRFS filesystem. There are no special commands for
2114 listing BTRFS directories or loading BTRFS files - this
2115 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2116 when BTRFS is enabled (see FS_BTRFS).
2119 bool "Enable the 'cbfs' command"
2122 Define this to enable support for reading from a Coreboot
2123 filesystem. This is a ROM-based filesystem used for accessing files
2124 on systems that use coreboot as the first boot-loader and then load
2125 U-Boot to actually boot the Operating System. Available commands are
2126 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2129 bool "Enable the 'cramfs' command"
2130 depends on FS_CRAMFS
2132 This provides commands for dealing with CRAMFS (Compressed ROM
2133 filesystem). CRAMFS is useful when space is tight since files are
2134 compressed. Two commands are provided:
2136 cramfsls - lists files in a cramfs image
2137 cramfsload - loads a file from a cramfs image
2140 bool "ext2 command support"
2143 Enables EXT2 FS command
2146 bool "ext4 command support"
2149 Enables EXT4 FS command
2151 config CMD_EXT4_WRITE
2153 bool "ext4 write command support"
2156 Enables EXT4 FS write command
2159 bool "FAT command support"
2162 Support for the FAT fs
2165 bool "SquashFS command support"
2168 Enables SquashFS filesystem commands (e.g. load, ls).
2170 config CMD_FS_GENERIC
2171 bool "filesystem commands"
2173 Enables filesystem commands (e.g. load, ls) that work for multiple
2177 bool "fsuuid command"
2179 Enables fsuuid command for filesystem UUID.
2182 bool "jffs2 command"
2185 Enables commands to support the JFFS2 (Journalling Flash File System
2186 version 2) filesystem. This enables fsload, ls and fsinfo which
2187 provide the ability to load files, list directories and obtain
2188 filesystem information.
2191 bool "MTD partition support"
2194 MTD partitioning tool support.
2195 It is strongly encouraged to avoid using this command
2196 anymore along with 'sf', 'nand', 'onenand'. One can still
2197 declare the partitions in the mtdparts environment variable
2198 but better use the MTD stack and the 'mtd' command instead.
2200 config CMD_MTDPARTS_SPREAD
2201 bool "Padd partition size to take account of bad blocks"
2202 depends on CMD_MTDPARTS
2204 This enables the 'spread' sub-command of the mtdparts command.
2205 This command will modify the existing mtdparts variable by increasing
2206 the size of the partitions such that 1) each partition's net size is
2207 at least as large as the size specified in the mtdparts variable and
2208 2) each partition starts on a good block.
2210 config CMD_MTDPARTS_SHOW_NET_SIZES
2211 bool "Show net size (w/o bad blocks) of partitions"
2212 depends on CMD_MTDPARTS
2214 Adds two columns to the printed partition table showing the
2215 effective usable size of a partition, if bad blocks are taken
2218 config MTDIDS_DEFAULT
2219 string "Default MTD IDs"
2220 depends on MTD || SPI_FLASH
2222 Defines a default MTD IDs list for use with MTD partitions in the
2223 Linux MTD command line partitions format.
2225 config MTDPARTS_DEFAULT
2226 string "Default MTD partition scheme"
2227 depends on MTD || SPI_FLASH
2229 Defines a default MTD partitioning scheme in the Linux MTD command
2230 line partitions format
2233 bool "reiser - Access to reiserfs filesystems"
2235 This provides two commands which operate on a resierfs filesystem,
2236 commonly used some years ago:
2238 reiserls - list files
2239 reiserload - load a file
2242 bool "yaffs2 - Access of YAFFS2 filesystem"
2246 This provides commands for accessing a YAFFS2 filesystem. Yet
2247 Another Flash Filesystem 2 is a filesystem designed specifically
2248 for NAND flash. It incorporates bad-block management and ensures
2249 that device writes are sequential regardless of filesystem
2253 bool "zfs - Access of ZFS filesystem"
2255 This provides commands to accessing a ZFS filesystem, commonly used
2256 on Solaris systems. Two sub-commands are provided:
2258 zfsls - list files in a directory
2259 zfsload - load a file
2261 See doc/README.zfs for more details.
2265 menu "Debug commands"
2270 The bedbug (emBEDded deBUGger) command provides debugging features
2271 for some PowerPC processors. For details please see the
2272 documentation in doc/README.bedbug.
2274 config CMD_CBSYSINFO
2277 default y if SYS_COREBOOT
2279 This provides information about the coreboot sysinfo table stored in
2280 memory by coreboot before jumping to U-Boot. It can be useful for
2281 debugging the beaaviour of coreboot or U-Boot.
2284 bool "diag - Board diagnostics"
2286 This command provides access to board diagnostic tests. These are
2287 called Power-on Self Tests (POST). The command allows listing of
2288 available tests and running either all the tests, or specific tests
2292 bool "irq - Show information about interrupts"
2293 depends on !ARM && !MIPS && !RISCV && !SH
2295 This enables two commands:
2297 interrupts - enable or disable interrupts
2298 irqinfo - print device-specific interrupt information
2301 bool "kgdb - Allow debugging of U-Boot with gdb"
2304 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2305 over a serial link for debugging purposes. This allows
2306 single-stepping, inspecting variables, etc. This is supported only
2307 on PowerPC at present.
2310 bool "log - Generation, control and access to logging"
2314 This provides access to logging features. It allows the output of
2315 log data to be controlled to a limited extent (setting up the default
2316 maximum log level for emitting of records). It also provides access
2317 to a command used for testing the log system.
2320 bool "trace - Support tracing of function calls and timing"
2322 Enables a command to control using of function tracing within
2323 U-Boot. This allows recording of call traces including timing
2324 information. The command can write data to memory for exporting
2325 for analysis (e.g. using bootchart). See doc/README.trace for full
2329 bool "avb - Android Verified Boot 2.0 operations"
2330 depends on AVB_VERIFY
2333 Enables a "avb" command to perform verification of partitions using
2334 Android Verified Boot 2.0 functionality. It includes such subcommands:
2335 avb init - initialize avb2 subsystem
2336 avb read_rb - read rollback index
2337 avb write_rb - write rollback index
2338 avb is_unlocked - check device lock state
2339 avb get_uuid - read and print uuid of a partition
2340 avb read_part - read data from partition
2341 avb read_part_hex - read data from partition and output to stdout
2342 avb write_part - write data to partition
2343 avb verify - run full verification chain
2345 config CMD_STACKPROTECTOR_TEST
2346 bool "Test command for stack protector"
2347 depends on STACKPROTECTOR
2349 Enable stackprot_test command
2350 The stackprot_test command will force a stack overrun to test
2351 the stack smashing detection mechanisms.
2356 tristate "Enable UBI - Unsorted block images commands"
2359 UBI is a software layer above MTD layer which admits use of LVM-like
2360 logical volumes on top of MTD devices, hides some complexities of
2361 flash chips like wear and bad blocks and provides some other useful
2362 capabilities. Please, consult the MTD web site for more details
2363 (www.linux-mtd.infradead.org). Activate this option if you want
2364 to use U-Boot UBI commands.
2365 It is also strongly encouraged to also enable CONFIG_MTD to get full
2368 config CMD_UBI_RENAME
2369 bool "Enable rename"
2373 Enable a "ubi" command to rename ubi volume:
2374 ubi rename <oldname> <newname>
2377 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2379 default y if CMD_UBI
2382 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob