1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
59 string "Command execution tracer"
63 This option enables the possiblity to print all commands before
64 executing them and after all variables are evaluated (similar
65 to Bash's xtrace/'set -x' feature).
66 To enable the tracer a variable "xtrace" needs to be defined in
69 menu "Autoboot options"
75 This enables the autoboot. See doc/README.autoboot for detail.
78 bool "Stop autobooting via specific input key / string"
81 This option enables stopping (aborting) of the automatic
82 boot feature only by issuing a specific input key or
83 string. If not enabled, any input key will abort the
84 U-Boot automatic booting process and bring the device
85 to the U-Boot prompt for user input.
87 config AUTOBOOT_PROMPT
88 string "Autoboot stop prompt"
89 depends on AUTOBOOT_KEYED
90 default "Autoboot in %d seconds\\n"
92 This string is displayed before the boot delay selected by
93 CONFIG_BOOTDELAY starts. If it is not defined there is no
94 output indicating that autoboot is in progress.
96 Note that this define is used as the (only) argument to a
97 printf() call, so it may contain '%' format specifications,
98 provided that it also includes, sepearated by commas exactly
99 like in a printf statement, the required arguments. It is
100 the responsibility of the user to select only such arguments
101 that are valid in the given context.
103 config AUTOBOOT_ENCRYPTION
104 bool "Enable encryption in autoboot stopping"
105 depends on AUTOBOOT_KEYED
107 This option allows a string to be entered into U-Boot to stop the
108 autoboot. The string itself is hashed and compared against the hash
109 in the environment variable 'bootstopkeysha256'. If it matches then
110 boot stops and a command-line prompt is presented.
112 This provides a way to ship a secure production device which can also
113 be accessed at the U-Boot command line.
115 config AUTOBOOT_DELAY_STR
116 string "Delay autobooting via specific input key / string"
117 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
119 This option delays the automatic boot feature by issuing
120 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
121 or the environment variable "bootdelaykey" is specified
122 and this string is received from console input before
123 autoboot starts booting, U-Boot gives a command prompt. The
124 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
125 used, otherwise it never times out.
127 config AUTOBOOT_STOP_STR
128 string "Stop autobooting via specific input key / string"
129 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
131 This option enables stopping (aborting) of the automatic
132 boot feature only by issuing a specific input key or
133 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
134 variable "bootstopkey" is specified and this string is
135 received from console input before autoboot starts booting,
136 U-Boot gives a command prompt. The U-Boot prompt never
137 times out, even if CONFIG_BOOT_RETRY_TIME is used.
139 config AUTOBOOT_KEYED_CTRLC
140 bool "Enable Ctrl-C autoboot interruption"
141 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
144 This option allows for the boot sequence to be interrupted
145 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
146 Setting this variable provides an escape sequence from the
147 limited "password" strings.
149 config AUTOBOOT_STOP_STR_SHA256
150 string "Stop autobooting via SHA256 encrypted password"
151 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
153 This option adds the feature to only stop the autobooting,
154 and therefore boot into the U-Boot prompt, when the input
155 string / password matches a values that is encypted via
156 a SHA256 hash and saved in the environment.
158 config AUTOBOOT_USE_MENUKEY
159 bool "Allow a specify key to run a menu from the environment"
160 depends on !AUTOBOOT_KEYED
162 If a specific key is pressed to stop autoboot, then the commands in
163 the environment variable 'menucmd' are executed before boot starts.
165 config AUTOBOOT_MENUKEY
166 int "ASCII value of boot key to show a menu"
168 depends on AUTOBOOT_USE_MENUKEY
170 If this key is pressed to stop autoboot, then the commands in the
171 environment variable 'menucmd' will be executed before boot starts.
172 For example, 33 means "!" in ASCII, so pressing ! at boot would take
175 config AUTOBOOT_MENU_SHOW
176 bool "Show a menu on boot"
177 depends on CMD_BOOTMENU
179 This enables the boot menu, controlled by environment variables
180 defined by the board. The menu starts after running the 'preboot'
181 environmnent variable (if enabled) and before handling the boot delay.
182 See README.bootmenu for more details.
197 List and dump ACPI tables. ACPI (Advanced Configuration and Power
198 Interface) is used mostly on x86 for providing information to the
199 Operating System about devices in the system. The tables are set up
200 by the firmware, typically U-Boot but possibly an earlier firmware
201 module, if U-Boot is chain-loaded from something else. ACPI tables
202 can also include code, to perform hardware-specific tasks required
203 by the Operating Systems. This allows some amount of separation
204 between the firmware and OS, and is particularly useful when you
205 want to make hardware changes without the OS needing to be adjusted.
218 Print ".config" contents.
220 If this option is enabled, the ".config" file contents are embedded
221 in the U-Boot image and can be printed on the console by the "config"
222 command. This provides information of which options are enabled on
229 Print console devices and information.
234 Print information about available CPUs. This normally shows the
235 number of CPUs, type (e.g. manufacturer, architecture, product or
236 internal name) and clock frequency. Other information may be
237 available depending on the CPU driver.
243 Print GPL license text
248 Provides access to the Intel Power-Management Controller (PMC) so
249 that its state can be examined. This does not currently support
250 changing the state but it is still useful for debugging and seeing
259 config CMD_TLV_EEPROM
261 depends on I2C_EEPROM
263 Display and program the system EEPROM data block in ONIE Tlvinfo
264 format. TLV stands for Type-Length-Value.
266 config SPL_CMD_TLV_EEPROM
267 bool "tlv_eeprom for SPL"
268 depends on SPL_I2C_EEPROM
269 select SPL_DRIVERS_MISC_SUPPORT
271 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
281 Run the command stored in the environment "bootcmd", i.e.
282 "bootd" does the same thing as "run bootcmd".
288 Boot an application image from the memory.
291 bool "Support booting UEFI FIT images"
292 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
295 Support booting UEFI FIT images via the bootm command.
300 Boot the Linux zImage
304 depends on ARM64 || RISCV
307 Boot an AArch64 Linux Kernel image from memory.
310 bool "Support booting Linux OS images"
311 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
314 Support booting the Linux kernel directly via a command such as bootm
318 bool "Support booting NetBSD (non-EFI) loader images"
322 Support booting NetBSD via the bootm command.
324 config BOOTM_OPENRTOS
325 bool "Support booting OPENRTOS / FreeRTOS images"
328 Support booting OPENRTOS / FreeRTOS via the bootm command.
331 bool "Support booting Enea OSE images"
332 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
335 Support booting Enea OSE images via the bootm command.
338 bool "Support booting Plan9 OS images"
342 Support booting Plan9 images via the bootm command.
345 bool "Support booting RTEMS OS images"
349 Support booting RTEMS images via the bootm command.
352 bool "Support booting VxWorks OS images"
356 Support booting VxWorks images via the bootm command.
360 depends on EFI_LOADER
363 Boot an EFI image from memory.
365 config CMD_BOOTEFI_HELLO_COMPILE
366 bool "Compile a standard EFI hello world binary for testing"
367 depends on CMD_BOOTEFI && !CPU_V7M
370 This compiles a standard EFI hello world application with U-Boot so
371 that it can be used with the test/py testing framework. This is useful
372 for testing that EFI is working at a basic level, and for bringing
373 up EFI support on a new architecture.
375 No additional space will be required in the resulting U-Boot binary
376 when this option is enabled.
378 config CMD_BOOTEFI_HELLO
379 bool "Allow booting a standard EFI hello world for testing"
380 depends on CMD_BOOTEFI_HELLO_COMPILE
382 This adds a standard EFI hello world application to U-Boot so that
383 it can be used with the 'bootefi hello' command. This is useful
384 for testing that EFI is working at a basic level, and for bringing
385 up EFI support on a new architecture.
387 source lib/efi_selftest/Kconfig
393 Add an ANSI terminal boot menu command.
398 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
399 image into RAM, dump image structure information, etc. Those dtb/dtbo
400 files should be merged in one dtb further, which needs to be passed to
401 the kernel, as part of a boot process.
405 depends on ANDROID_BOOT_IMAGE
407 Android Boot Image manipulation commands. Allows one to extract
408 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
409 obtain corresponding meta-information from boot.img.
411 See doc/android/boot-image.rst for details.
414 bool "bootelf, bootvx"
418 Boot an ELF/vxWorks image from the memory.
421 bool "Flattened Device Tree utility commands"
425 Do FDT related setup before booting into the Operating System.
431 Start an application at a given address.
437 Run the command in the given environment variable.
443 Print header information for application image.
448 List all images found in flash
454 Extract a part of a multi-image.
457 bool "spl export - Export boot information for Falcon boot"
460 Falcon mode allows booting directly from SPL into an Operating
461 System such as Linux, thus skipping U-Boot proper. See
462 doc/README.falcon for full information about how to use this
465 config CMD_SPL_NAND_OFS
466 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
467 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
470 This provides the offset of the command line arguments for Linux
471 when booting from NAND in Falcon mode. See doc/README.falcon
472 for full information about how to use this option (and also see
473 board/gateworks/gw_ventana/README for an example).
475 config CMD_SPL_NOR_OFS
476 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
477 depends on CMD_SPL && SPL_NOR_SUPPORT
480 This provides the offset of the command line arguments or dtb for
481 Linux when booting from NOR in Falcon mode.
483 config CMD_SPL_WRITE_SIZE
484 hex "Size of argument area"
488 This provides the size of the command-line argument area in NAND
489 flash used by Falcon-mode boot. See the documentation until CMD_SPL
493 bool "fitImage update command"
495 Implements the 'fitupd' command, which allows to automatically
496 store software updates present on a TFTP server in NOR Flash
498 config CMD_THOR_DOWNLOAD
499 bool "thor - TIZEN 'thor' download"
502 Implements the 'thor' download protocol. This is a way of
503 downloading a software update over USB from an attached host.
504 There is no documentation about this within the U-Boot source code
505 but you should be able to find something on the interwebs.
508 bool "zboot - x86 boot command"
510 With x86 machines it is common to boot a bzImage file which
511 contains both a kernel and a setup.bin file. The latter includes
512 configuration information from the dark ages which x86 boards still
513 need to pick things out of.
515 Consider using FIT in preference to this since it supports directly
516 booting both 32- and 64-bit kernels, as well as secure boot.
517 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
521 menu "Environment commands"
524 bool "ask for env variable"
526 Ask for environment variable
544 Edit environment variable.
549 Allow for searching environment variables
555 Save all environment variables into the compiled-in persistent
561 depends on CMD_SAVEENV
563 Erase environment variables from the compiled-in persistent
566 config CMD_ENV_EXISTS
570 Check if a variable is defined in the environment for use in
573 config CMD_ENV_CALLBACK
574 bool "env callbacks - print callbacks and their associated variables"
576 Some environment variable have callbacks defined by
577 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
578 For example changing "baudrate" adjust the serial baud rate. This
579 command lists the currently defined callbacks.
582 bool "env flags -print variables that have non-default flags"
584 Some environment variables have special flags that control their
585 behaviour. For example, serial# can only be written once and cannot
586 be deleted. This command shows the variables that have special
589 config CMD_NVEDIT_EFI
590 bool "env [set|print] -e - set/print UEFI variables"
591 depends on EFI_LOADER
594 UEFI variables are encoded as some form of U-Boot variables.
595 If enabled, we are allowed to set/print UEFI variables using
596 "env" command with "-e" option without knowing details.
598 config CMD_NVEDIT_INFO
599 bool "env info - print or evaluate environment information"
601 Print environment information:
602 - env_valid : is environment valid
603 - env_ready : is environment imported into hash table
604 - env_use_default : is default environment used
606 This command can be optionally used for evaluation in scripts:
607 [-d] : evaluate whether default environment is used
608 [-p] : evaluate whether environment can be persisted
609 The result of multiple evaluations will be combined with AND.
613 menu "Memory commands"
618 Compute binary operations (xor, or, and) of byte arrays of arbitrary
619 size from memory and store the result in memory or the environment.
632 Add -v option to verify data against a crc32 checksum.
635 bool "eeprom - EEPROM subsystem"
637 (deprecated, needs conversion to driver model)
638 Provides commands to read and write EEPROM (Electrically Erasable
639 Programmable Read Only Memory) chips that are connected over an
642 config CMD_EEPROM_LAYOUT
643 bool "Enable layout-aware eeprom commands"
644 depends on CMD_EEPROM
646 (deprecated, needs conversion to driver model)
647 When enabled, additional eeprom sub-commands become available.
649 eeprom print - prints the contents of the eeprom in a human-readable
650 way (eeprom layout fields, and data formatted to be fit for human
653 eeprom update - allows user to update eeprom fields by specifying
654 the field name, and providing the new data in a human readable format
655 (same format as displayed by the eeprom print command).
657 Both commands can either auto detect the layout, or be told which
661 __weak int parse_layout_version(char *str)
662 - override to provide your own layout name parsing
663 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
665 - override to setup the layout metadata based on the version
666 __weak int eeprom_layout_detect(unsigned char *data)
667 - override to provide your own algorithm for detecting layout
670 - contains various printing and updating functions for common
671 types of eeprom fields. Can be used for defining
674 config EEPROM_LAYOUT_HELP_STRING
675 string "Tells user what layout names are supported"
676 depends on CMD_EEPROM_LAYOUT
677 default "<not defined>"
679 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
685 Infinite write loop on address range
692 Compute MD5 checksum.
697 depends on CMD_MD5SUM
699 Add -v option to verify data against an MD5 checksum.
704 Display memory information.
707 bool "md, mm, nm, mw, cp, cmp, base, loop"
712 mm - memory modify (auto-incrementing address)
713 nm - memory modify (constant address)
714 mw - memory write (fill)
717 base - print or set address offset
718 loop - initialize loop on address range
721 bool "Enable cyclic md/mw commands"
722 depends on CMD_MEMORY
724 Add the "mdc" and "mwc" memory commands. These are cyclic
729 This command will print 4 bytes (10,11,12,13) each 500 ms.
731 => mwc.l 100 12345678 10
732 This command will write 12345678 to address 100 all 10 ms.
737 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
739 random - fill memory with random data
744 Simple RAM read/write test.
748 config SYS_ALT_MEMTEST
749 bool "Alternative test"
751 Use a more complete alternative memory test.
753 config SYS_MEMTEST_START
754 hex "default start address for mtest"
757 This is the default start address for mtest for simple read/write
758 test. If no arguments are given to mtest, default address is used
761 config SYS_MEMTEST_END
762 hex "default end address for mtest"
765 This is the default end address for mtest for simple read/write
766 test. If no arguments are given to mtest, default address is used
775 Compute SHA1 checksum.
777 config SHA1SUM_VERIFY
779 depends on CMD_SHA1SUM
781 Add -v option to verify data against a SHA1 checksum.
784 bool "strings - display strings in memory"
786 This works similarly to the Unix 'strings' command except that it
787 works with a memory range. String of printable characters found
788 within the range are displayed. The minimum number of characters
789 for a sequence to be considered a string can be provided.
793 menu "Compression commands"
797 default y if CMD_BOOTI
800 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
805 default y if CMD_BOOTI
808 Support decompressing an LZ4 image from memory region.
812 default y if CMD_BOOTI
814 Uncompress a zip-compressed memory region.
819 Compress a memory region with zlib deflate method.
823 menu "Device access commands"
826 #depends on FLASH_CFI_DRIVER
829 ARM Ltd reference designs flash partition access
832 bool "adc - Access Analog to Digital Converters info and data"
836 Shows ADC device info and permit printing one-shot analog converted
837 data from a named Analog to Digital Converter.
842 depends on PARTITIONS
844 Read/modify/write the fields of Bootloader Control Block, usually
845 stored on the flash "misc" partition with its structure defined in:
846 https://android.googlesource.com/platform/bootable/recovery/+/master/
847 bootloader_message/include/bootloader_message/bootloader_message.h
849 Some real-life use-cases include (but are not limited to):
850 - Determine the "boot reason" (and act accordingly):
851 https://source.android.com/devices/bootloader/boot-reason
852 - Get/pass a list of commands from/to recovery:
853 https://android.googlesource.com/platform/bootable/recovery
854 - Inspect/dump the contents of the BCB fields
857 bool "bind/unbind - Bind or unbind a device to/from a driver"
860 Bind or unbind a device to/from a driver from the command line.
861 This is useful in situations where a device may be handled by several
862 drivers. For example, this can be used to bind a UDC to the usb ether
863 gadget driver from the command line.
866 bool "clk - Show clock frequencies"
869 Shows clock frequences by calling a sock_clk_dump() hook function.
870 This is depreated in favour of using the CLK uclass and accessing
871 clock values from associated drivers. However currently no command
875 bool "demo - Demonstration commands for driver model"
878 Provides a 'demo' command which can be used to play around with
879 driver model. To use this properly you will need to enable one or
880 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
881 Otherwise you will always get an empty list of devices. The demo
882 devices are defined in the sandbox device tree, so the easiest
883 option is to use sandbox and pass the -d point to sandbox's
890 Enables the command "dfu" which is used to have U-Boot create a DFU
891 class device via USB. This command requires that the "dfu_alt_info"
892 environment variable be set and define the alt settings to expose to
896 bool "dm - Access to driver model information"
899 Provides access to driver model data structures and information,
900 such as a list of devices, list of uclasses and the state of each
901 device (e.g. activated). This is not required for operation, but
902 can be useful to see the state of driver model for debugging or
906 bool "fastboot - Android fastboot support"
909 This enables the command "fastboot" which enables the Android
910 fastboot mode for the platform. Fastboot is a protocol for
911 downloading images, flashing and device control used on
912 Android devices. Fastboot requires either the network stack
913 enabled or support for acting as a USB device.
915 See doc/android/fastboot.rst for more information.
918 bool "flinfo, erase, protect"
920 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
923 flinfo - print FLASH memory information
925 protect - enable or disable FLASH write protection
934 config CMD_FPGA_LOADBP
935 bool "fpga loadbp - load partial bitstream (Xilinx only)"
938 Supports loading an FPGA device from a bitstream buffer containing
941 config CMD_FPGA_LOADFS
942 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
945 Supports loading an FPGA device from a FAT filesystem.
947 config CMD_FPGA_LOADMK
948 bool "fpga loadmk - load bitstream from image"
951 Supports loading an FPGA device from a image generated by mkimage.
953 config CMD_FPGA_LOADP
954 bool "fpga loadp - load partial bitstream"
957 Supports loading an FPGA device from a bitstream buffer containing
960 config CMD_FPGA_LOAD_SECURE
961 bool "fpga loads - loads secure bitstreams (Xilinx only)"
964 Enables the fpga loads command which is used to load secure
965 (authenticated or encrypted or both) bitstreams on to FPGA.
968 bool "fpgad - dump FPGA registers"
970 (legacy, needs conversion to driver model)
971 Provides a way to dump FPGA registers by calling the board-specific
972 fpga_get_reg() function. This functions similarly to the 'md'
976 bool "fuse - support for the fuse subssystem"
978 (deprecated - needs conversion to driver model)
979 This allows reading, sensing, programming or overriding fuses
980 which control the behaviour of the device. The command uses the
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
1091 MMC memory mapped support.
1095 config CMD_BKOPS_ENABLE
1096 bool "mmc bkops enable"
1100 Enable command for setting manual background operations handshake
1101 on a eMMC device. The feature is optionally available on eMMC devices
1102 conforming to standard >= 4.41.
1105 bool "Enable support for RPMB in the mmc command"
1106 depends on SUPPORT_EMMC_RPMB
1108 Enable the commands for reading, writing and programming the
1109 key for the Replay Protection Memory Block partition in eMMC.
1111 config CMD_MMC_SWRITE
1113 depends on MMC_WRITE
1116 Enable support for the "mmc swrite" command to write Android sparse
1124 select MTD_PARTITIONS
1126 MTD commands support.
1130 default y if NAND_SUNXI
1131 depends on MTD_RAW_NAND
1136 config CMD_NAND_TRIMFFS
1137 bool "nand write.trimffs"
1138 default y if ARCH_SUNXI
1140 Allows one to skip empty pages when flashing something on a NAND.
1142 config CMD_NAND_LOCK_UNLOCK
1143 bool "nand lock/unlock"
1145 NAND locking support.
1147 config CMD_NAND_TORTURE
1150 NAND torture support.
1159 NVM Express device support
1162 bool "onenand - access to onenand device"
1165 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1166 various useful features. This command allows reading, writing,
1167 and erasing blocks. It allso provides a way to show and change
1168 bad blocks, and test the device.
1173 Enable the 'osd' command which allows to query information from and
1174 write text data to a on-screen display (OSD) device; a virtual device
1175 associated with a display capable of displaying a text overlay on the
1176 display it's associated with..
1180 select HAVE_BLOCK_DEVICE
1181 select PARTITION_UUIDS
1183 Read and display information about the partition table on
1187 bool "pci - Access PCI devices"
1189 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1190 used on some devices to allow the CPU to communicate with its
1191 peripherals. Sub-commands allow bus enumeration, displaying and
1192 changing configuration space and a few other features.
1195 bool "pinmux - show pins muxing"
1196 default y if PINCTRL
1198 Parse all available pin-controllers and show pins muxing. This
1199 is useful for debug purpoer to check the pin muxing and to know if
1200 a pin is configured as a GPIO or as an alternate function.
1205 Poweroff/Shutdown the system
1208 bool "read - Read binary data from a partition"
1210 Provides low-level access to the data in a partition.
1212 config CMD_REMOTEPROC
1214 depends on REMOTEPROC
1216 Support for Remote Processor control
1219 bool "sata - Access SATA subsystem"
1222 SATA (Serial Advanced Technology Attachment) is a serial bus
1223 standard for connecting to hard drives and other storage devices.
1224 This command provides information about attached devices and allows
1225 reading, writing and other operations.
1227 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1228 Attachment, where AT refers to an IBM AT (Advanced Technology)
1229 computer released in 1984.
1232 bool "saves - Save a file over serial in S-Record format"
1234 Provides a way to save a binary file using the Motorola S-Record
1235 format over the serial line.
1238 bool "scsi - Access to SCSI devices"
1241 This provides a 'scsi' command which provides access to SCSI (Small
1242 Computer System Interface) devices. The command provides a way to
1243 scan the bus, reset the bus, read and write data and get information
1247 bool "sdram - Print SDRAM configuration information"
1249 Provides information about attached SDRAM. This assumed that the
1250 SDRAM has an EEPROM with information that can be read using the
1251 I2C bus. This is only available on some boards.
1255 depends on DM_SPI_FLASH || SPI_FLASH
1256 default y if DM_SPI_FLASH
1261 bool "sf test - Allow testing of SPI flash"
1264 Provides a way to test that SPI flash is working correctly. The
1265 test is destructive, in that an area of SPI flash must be provided
1266 for the test to use. Performance information is also provided,
1267 measuring the performance of reading, writing and erasing in
1268 Mbps (Million Bits Per Second). This value should approximately
1269 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1270 everything is working properly.
1273 bool "sspi - Command to access spi device"
1276 SPI utility command.
1278 config DEFAULT_SPI_BUS
1279 int "default spi bus used by sspi command"
1283 config DEFAULT_SPI_MODE
1284 hex "default spi mode used by sspi command (see include/spi.h)"
1289 bool "tsi148 - Command to access tsi148 device"
1291 This provides various sub-commands to initialise and configure the
1292 Turndra tsi148 device. See the command help for full details.
1295 bool "Enable UFS - Universal Flash Subsystem commands"
1298 "This provides commands to initialise and configure universal flash
1302 bool "universe - Command to set up the Turndra Universe controller"
1304 This allows setting up the VMEbus provided by this controller.
1305 See the command help for full details.
1309 select HAVE_BLOCK_DEVICE
1315 select USB_FUNCTION_SDP
1317 Enables the command "sdp" which is used to have U-Boot emulating the
1318 Serial Download Protocol (SDP) via USB.
1322 depends on USB_FUNCTION_ROCKUSB
1324 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1325 read/write info, image to/from devices. This enable rockusb command
1326 support to communication with rockusb device. for more detail about
1327 this command, please read doc/README.rockusb.
1329 config CMD_USB_MASS_STORAGE
1330 bool "UMS usb mass storage"
1331 select USB_FUNCTION_MASS_STORAGE
1333 USB mass storage support
1340 VirtIO block device support
1346 This provides commands to control the watchdog timer devices.
1352 Enable the command "axi" for accessing AXI (Advanced eXtensible
1353 Interface) busses, a on-chip interconnect specification for managing
1354 functional blocks in SoC designs, which is also often used in designs
1355 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1359 menu "Shell scripting commands"
1365 Echo args to console
1371 Return true/false on integer compare.
1377 Run script from memory
1383 Evaluate boolean and math expressions and store the result in an env
1385 Also supports loading the value at a memory location into a variable.
1386 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1390 menu "Android support commands"
1392 config CMD_AB_SELECT
1395 depends on ANDROID_AB
1397 On Android devices with more than one boot slot (multiple copies of
1398 the kernel and system images) this provides a command to select which
1399 slot should be used to boot from and register the boot attempt. This
1400 is used by the new A/B update model where one slot is updated in the
1401 background while running from the other slot.
1408 bool "Network commands"
1418 bootp - boot image via network using BOOTP/TFTP protocol
1422 depends on CMD_BOOTP
1424 Boot image via network using DHCP/TFTP protocol
1426 config BOOTP_BOOTPATH
1427 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1429 depends on CMD_BOOTP
1431 Even though the config is called BOOTP_BOOTPATH, it stores the
1432 path in the variable 'rootpath'.
1435 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1437 depends on CMD_BOOTP
1439 The primary DNS server is stored as 'dnsip'. If two servers are
1440 returned, you must set BOOTP_DNS2 to store that second server IP
1444 bool "Store 'dnsip2' from BOOTP/DHCP server"
1445 depends on BOOTP_DNS
1447 If a DHCP client requests the DNS server IP from a DHCP server,
1448 it is possible that more than one DNS serverip is offered to the
1449 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1450 server IP will be stored in the additional environment
1451 variable "dnsip2". The first DNS serverip is always
1452 stored in the variable "dnsip", when BOOTP_DNS is defined.
1454 config BOOTP_GATEWAY
1455 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1457 depends on CMD_BOOTP
1459 config BOOTP_HOSTNAME
1460 bool "Request & store 'hostname' from BOOTP/DHCP server"
1462 depends on CMD_BOOTP
1464 The name may or may not be qualified with the local domain name.
1466 config BOOTP_PREFER_SERVERIP
1467 bool "serverip variable takes precedent over DHCP server IP."
1468 depends on CMD_BOOTP
1470 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1472 With this option enabled, the 'serverip' variable in the environment
1473 takes precedence over DHCP server IP and will only be set by the DHCP
1474 server if not already set in the environment.
1476 config BOOTP_SUBNETMASK
1477 bool "Request & store 'netmask' from BOOTP/DHCP server"
1479 depends on CMD_BOOTP
1481 config BOOTP_NTPSERVER
1482 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1483 depends on CMD_BOOTP
1488 Selecting this will allow capturing all Ethernet packets and store
1489 them in physical memory in a PCAP formated file,
1490 later to be analyzed by PCAP reader application (IE. WireShark).
1493 bool "Send PXE client arch to BOOTP/DHCP server"
1495 depends on CMD_BOOTP && CMD_PXE
1497 Supported for ARM, ARM64, and x86 for now.
1499 config BOOTP_PXE_CLIENTARCH
1501 depends on BOOTP_PXE
1502 default 0x16 if ARM64
1506 config BOOTP_VCI_STRING
1508 depends on CMD_BOOTP
1509 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1510 default "U-Boot.armv8" if ARM64
1511 default "U-Boot.arm" if ARM
1518 tftpboot - boot image via network using TFTP protocol
1522 depends on CMD_TFTPBOOT
1524 TFTP put command, for uploading files to a server
1528 depends on CMD_TFTPBOOT
1530 Act as a TFTP server and boot the first received file
1532 config NET_TFTP_VARS
1533 bool "Control TFTP timeout and count through environment"
1534 depends on CMD_TFTPBOOT
1537 If set, allows controlling the TFTP timeout through the
1538 environment variable tftptimeout, and the TFTP maximum
1539 timeout count through the variable tftptimeoutcountmax.
1540 If unset, timeout and maximum are hard-defined as 1 second
1541 and 10 timouts per TFTP transfer.
1546 Boot image via network using RARP/TFTP protocol
1552 Boot image via network using NFS protocol.
1558 If set, allows 802.3(clause 22) MII Management functions interface access
1559 The management interface specified in Clause 22 provides
1560 a simple, two signal, serial interface to connect a
1561 Station Management entity and a managed PHY for providing access
1562 to management parameters and services.
1563 The interface is referred to as the MII management interface.
1569 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1570 The MDIO interface is orthogonal to the MII interface and extends
1571 it by adding access to more registers through indirect addressing.
1576 Send ICMP ECHO_REQUEST to network host
1581 Perform CDP network configuration
1586 Synchronize RTC via network
1591 Lookup the IP of a hostname
1593 config CMD_LINK_LOCAL
1597 Acquire a network IP address using the link-local protocol
1604 Allow control of L2 Ethernet switch commands. These are supported
1605 by the vsc9953 Ethernet driver at present. Sub-commands allow
1606 operations such as enabling / disabling a port and
1607 viewing/maintaining the filtering database (FDB)
1613 Boot image via network using PXE protocol
1618 Wait for wake-on-lan Magic Packet
1622 menu "Misc commands"
1625 bool "Enable 'bmp' command"
1626 depends on LCD || DM_VIDEO || VIDEO
1628 This provides a way to obtain information about a BMP-format image
1629 and to display it. BMP (which presumably stands for BitMaP) is a
1630 file format defined by Microsoft which supports images of various
1631 depths, formats and compression methods. Headers on the file
1632 determine the formats used. This command can be used by first loading
1633 the image into RAM, then using this command to look at it or display
1636 config CMD_BOOTCOUNT
1638 depends on BOOTCOUNT_LIMIT
1640 Enable the bootcount command, which allows interrogation and
1641 reset of the bootcounter.
1644 bool "Enable board-specific commands"
1646 (deprecated: instead, please define a Kconfig option for each command)
1648 Some boards have board-specific commands which are only enabled
1649 during developemnt and need to be turned off for production. This
1650 option provides a way to control this. The commands that are enabled
1651 vary depending on the board.
1653 config CMD_BLOCK_CACHE
1654 bool "blkcache - control and stats for block cache"
1655 depends on BLOCK_CACHE
1656 default y if BLOCK_CACHE
1658 Enable the blkcache command, which can be used to control the
1659 operation of the cache functions.
1660 This is most useful when fine-tuning the operation of the cache
1661 during development, but also allows the cache to be disabled when
1662 it might hurt performance (e.g. when using the ums command).
1665 bool "icache or dcache"
1667 Enable the "icache" and "dcache" commands
1669 config CMD_CONITRACE
1670 bool "conitrace - trace console input codes"
1672 Enable the 'conitrace' command which displays the codes received
1673 from the console input as hexadecimal numbers.
1676 bool "Enable clear screen command 'cls'"
1677 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1680 Enable the 'cls' command which clears the screen contents
1681 on video frame buffer.
1684 bool "efidebug - display/configure UEFI environment"
1685 depends on EFI_LOADER
1686 select EFI_DEVICE_PATH_TO_TEXT
1689 Enable the 'efidebug' command which provides a subset of UEFI
1690 shell utility with simplified functionality. It will be useful
1691 particularly for managing boot parameters as well as examining
1692 various EFI status for debugging.
1694 config CMD_EXCEPTION
1695 bool "exception - raise exception"
1696 depends on ARM || RISCV || X86
1698 Enable the 'exception' command which allows to raise an exception.
1705 Enable the 'led' command which allows for control of LEDs supported
1706 by the board. The LEDs can be listed with 'led list' and controlled
1707 with led on/off/togle/blink. Any LED drivers can be controlled with
1708 this command, e.g. led_gpio.
1715 Enable the 'date' command for getting/setting the time/date in RTC
1721 Run commands and summarize execution time.
1724 bool "gettime - read elapsed time"
1726 Enable the 'gettime' command which reads the elapsed time since
1727 U-Boot started running. This shows the time in seconds and
1728 milliseconds. See also the 'bootstage' command which provides more
1729 flexibility for boot timing.
1736 Print bytes from the hardware random number generator.
1738 # TODO: rename to CMD_SLEEP
1743 Delay execution for some time
1746 bool "support for multiprocessor"
1748 This provides an option to brinup
1749 different processors in multiprocessor
1755 Access the system timer.
1761 This provides basic access to the U-Boot's sound support. The main
1762 feature is to play a beep.
1764 sound init - set up sound system
1765 sound play - play a sound
1771 Boot image via local extlinux.conf file
1777 This provides access to the QEMU firmware interface. The main
1778 feature is to allow easy loading of files passed to qemu-system
1779 via -kernel / -initrd
1781 source "cmd/mvebu/Kconfig"
1784 bool "terminal - provides a way to attach a serial terminal"
1786 Provides a 'cu'-like serial terminal command. This can be used to
1787 access other serial ports from the system console. The terminal
1788 is very simple with no special processing of characters. As with
1789 cu, you can press ~. (tilde followed by period) to exit.
1792 bool "uuid, guid - generation of unique IDs"
1795 This enables two commands:
1797 uuid - generate random Universally Unique Identifier
1798 guid - generate Globally Unique Identifier based on random UUID
1800 The two commands are very similar except for the endianness of the
1805 source "cmd/ti/Kconfig"
1807 config CMD_BOOTSTAGE
1808 bool "Enable the 'bootstage' command"
1809 depends on BOOTSTAGE
1811 Add a 'bootstage' command which supports printing a report
1812 and un/stashing of bootstage data.
1814 menu "Power commands"
1816 bool "Enable Driver Model PMIC command"
1819 This is the pmic command, based on a driver model pmic's API.
1820 Command features are unchanged:
1821 - list - list pmic devices
1822 - pmic dev <id> - show or [set] operating pmic device (NEW)
1823 - pmic dump - dump registers
1824 - pmic read address - read byte of register at address
1825 - pmic write address - write byte to register at address
1826 The only one change for this command is 'dev' subcommand.
1828 config CMD_REGULATOR
1829 bool "Enable Driver Model REGULATOR command"
1830 depends on DM_REGULATOR
1832 This command is based on driver model regulator's API.
1833 User interface features:
1834 - list - list regulator devices
1835 - regulator dev <id> - show or [set] operating regulator device
1836 - regulator info - print constraints info
1837 - regulator status - print operating status
1838 - regulator value <val] <-f> - print/[set] voltage value [uV]
1839 - regulator current <val> - print/[set] current value [uA]
1840 - regulator mode <id> - print/[set] operating mode id
1841 - regulator enable - enable the regulator output
1842 - regulator disable - disable the regulator output
1844 The '-f' (force) option can be used for set the value which exceeds
1845 the limits, which are found in device-tree and are kept in regulator's
1846 uclass platdata structure.
1850 menu "Security commands"
1852 bool "Enable the 'aes' command"
1855 This provides a means to encrypt and decrypt data using the AES
1856 (Advanced Encryption Standard). This algorithm uses a symetric key
1857 and is widely used as a streaming cipher. Different key lengths are
1858 supported by the algorithm but this command only supports 128 bits
1862 bool "Enable the 'blob' command"
1864 This is used with the Freescale secure boot mechanism.
1866 Freescale's SEC block has built-in Blob Protocol which provides
1867 a method for protecting user-defined data across system power
1868 cycles. SEC block protects data in a data structure called a Blob,
1869 which provides both confidentiality and integrity protection.
1871 Encapsulating data as a blob
1872 Each time that the Blob Protocol is used to protect data, a
1873 different randomly generated key is used to encrypt the data.
1874 This random key is itself encrypted using a key which is derived
1875 from SoC's non-volatile secret key and a 16 bit Key identifier.
1876 The resulting encrypted key along with encrypted data is called a
1877 blob. The non-volatile secure key is available for use only during
1880 During decapsulation, the reverse process is performed to get back
1884 blob enc - encapsulating data as a cryptgraphic blob
1885 blob dec - decapsulating cryptgraphic blob to get the data
1889 blob enc src dst len km
1891 Encapsulate and create blob of data $len bytes long
1892 at address $src and store the result at address $dst.
1893 $km is the 16 byte key modifier is also required for
1894 generation/use as key for cryptographic operation. Key
1895 modifier should be 16 byte long.
1897 blob dec src dst len km
1899 Decapsulate the blob of data at address $src and
1900 store result of $len byte at addr $dst.
1901 $km is the 16 byte key modifier is also required for
1902 generation/use as key for cryptographic operation. Key
1903 modifier should be 16 byte long.
1906 bool "Support 'hash' command"
1909 This provides a way to hash data in memory using various supported
1910 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1911 saved to memory or to an environment variable. It is also possible
1912 to verify a hash against data in memory.
1915 bool "Support the 'hvc' command"
1916 depends on ARM_SMCCC
1918 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1919 development and testing.
1922 bool "Support the 'smc' command"
1923 depends on ARM_SMCCC
1925 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1926 development and testing.
1932 Add -v option to verify data against a hash.
1942 bool "Enable the 'tpm' command"
1943 depends on TPM_V1 || TPM_V2
1944 select CMD_TPM_V1 if TPM_V1
1945 select CMD_TPM_V2 if TPM_V2
1947 This provides a means to talk to a TPM from the command line. A wide
1948 range of commands if provided - see 'tpm help' for details. The
1949 command requires a suitable TPM on your board and the correct driver
1955 bool "Enable the 'tpm test' command"
1958 This provides a a series of tests to confirm that the TPMv1.x is
1959 working correctly. The tests cover initialisation, non-volatile RAM,
1960 extend, global lock and checking that timing is within expectations.
1961 The tests pass correctly on Infineon TPMs but may need to be adjusted
1968 menu "Firmware commands"
1970 bool "Enable crosec command"
1974 Enable command-line access to the Chrome OS EC (Embedded
1975 Controller). This provides the 'crosec' command which has
1976 a number of sub-commands for performing EC tasks such as
1977 updating its flash, accessing a small saved context area
1978 and talking to the I2C bus behind the EC (if there is one).
1981 menu "Filesystem commands"
1983 bool "Enable the 'btrsubvol' command"
1986 This enables the 'btrsubvol' command to list subvolumes
1987 of a BTRFS filesystem. There are no special commands for
1988 listing BTRFS directories or loading BTRFS files - this
1989 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1990 when BTRFS is enabled (see FS_BTRFS).
1993 bool "Enable the 'cbfs' command"
1996 Define this to enable support for reading from a Coreboot
1997 filesystem. This is a ROM-based filesystem used for accessing files
1998 on systems that use coreboot as the first boot-loader and then load
1999 U-Boot to actually boot the Operating System. Available commands are
2000 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2003 bool "Enable the 'cramfs' command"
2004 depends on FS_CRAMFS
2006 This provides commands for dealing with CRAMFS (Compressed ROM
2007 filesystem). CRAMFS is useful when space is tight since files are
2008 compressed. Two commands are provided:
2010 cramfsls - lists files in a cramfs image
2011 cramfsload - loads a file from a cramfs image
2014 bool "ext2 command support"
2017 Enables EXT2 FS command
2020 bool "ext4 command support"
2023 Enables EXT4 FS command
2025 config CMD_EXT4_WRITE
2027 bool "ext4 write command support"
2030 Enables EXT4 FS write command
2033 bool "FAT command support"
2036 Support for the FAT fs
2038 config CMD_FS_GENERIC
2039 bool "filesystem commands"
2041 Enables filesystem commands (e.g. load, ls) that work for multiple
2045 bool "fsuuid command"
2047 Enables fsuuid command for filesystem UUID.
2050 bool "jffs2 command"
2053 Enables commands to support the JFFS2 (Journalling Flash File System
2054 version 2) filesystem. This enables fsload, ls and fsinfo which
2055 provide the ability to load files, list directories and obtain
2056 filesystem information.
2059 bool "MTD partition support"
2062 MTD partitioning tool support.
2063 It is strongly encouraged to avoid using this command
2064 anymore along with 'sf', 'nand', 'onenand'. One can still
2065 declare the partitions in the mtdparts environment variable
2066 but better use the MTD stack and the 'mtd' command instead.
2068 config CMD_MTDPARTS_SPREAD
2069 bool "Padd partition size to take account of bad blocks"
2070 depends on CMD_MTDPARTS
2072 This enables the 'spread' sub-command of the mtdparts command.
2073 This command will modify the existing mtdparts variable by increasing
2074 the size of the partitions such that 1) each partition's net size is
2075 at least as large as the size specified in the mtdparts variable and
2076 2) each partition starts on a good block.
2078 config CMD_MTDPARTS_SHOW_NET_SIZES
2079 bool "Show net size (w/o bad blocks) of partitions"
2080 depends on CMD_MTDPARTS
2082 Adds two columns to the printed partition table showing the
2083 effective usable size of a partition, if bad blocks are taken
2086 config MTDIDS_DEFAULT
2087 string "Default MTD IDs"
2088 depends on MTD || SPI_FLASH
2090 Defines a default MTD IDs list for use with MTD partitions in the
2091 Linux MTD command line partitions format.
2093 config MTDPARTS_DEFAULT
2094 string "Default MTD partition scheme"
2095 depends on MTD || SPI_FLASH
2097 Defines a default MTD partitioning scheme in the Linux MTD command
2098 line partitions format
2101 bool "reiser - Access to reiserfs filesystems"
2103 This provides two commands which operate on a resierfs filesystem,
2104 commonly used some years ago:
2106 reiserls - list files
2107 reiserload - load a file
2110 bool "yaffs2 - Access of YAFFS2 filesystem"
2114 This provides commands for accessing a YAFFS2 filesystem. Yet
2115 Another Flash Filesystem 2 is a filesystem designed specifically
2116 for NAND flash. It incorporates bad-block management and ensures
2117 that device writes are sequential regardless of filesystem
2121 bool "zfs - Access of ZFS filesystem"
2123 This provides commands to accessing a ZFS filesystem, commonly used
2124 on Solaris systems. Two sub-commands are provided:
2126 zfsls - list files in a directory
2127 zfsload - load a file
2129 See doc/README.zfs for more details.
2133 menu "Debug commands"
2138 The bedbug (emBEDded deBUGger) command provides debugging features
2139 for some PowerPC processors. For details please see the
2140 documentation in doc/README.bedbug.
2143 bool "diag - Board diagnostics"
2145 This command provides access to board diagnostic tests. These are
2146 called Power-on Self Tests (POST). The command allows listing of
2147 available tests and running either all the tests, or specific tests
2151 bool "irq - Show information about interrupts"
2152 depends on !ARM && !MIPS && !SH
2154 This enables two commands:
2156 interrupts - enable or disable interrupts
2157 irqinfo - print device-specific interrupt information
2160 bool "kgdb - Allow debugging of U-Boot with gdb"
2163 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2164 over a serial link for debugging purposes. This allows
2165 single-stepping, inspecting variables, etc. This is supported only
2166 on PowerPC at present.
2169 bool "log - Generation, control and access to logging"
2172 This provides access to logging features. It allows the output of
2173 log data to be controlled to a limited extent (setting up the default
2174 maximum log level for emitting of records). It also provides access
2175 to a command used for testing the log system.
2178 bool "trace - Support tracing of function calls and timing"
2180 Enables a command to control using of function tracing within
2181 U-Boot. This allows recording of call traces including timing
2182 information. The command can write data to memory for exporting
2183 for analysis (e.g. using bootchart). See doc/README.trace for full
2187 bool "avb - Android Verified Boot 2.0 operations"
2188 depends on AVB_VERIFY
2191 Enables a "avb" command to perform verification of partitions using
2192 Android Verified Boot 2.0 functionality. It includes such subcommands:
2193 avb init - initialize avb2 subsystem
2194 avb read_rb - read rollback index
2195 avb write_rb - write rollback index
2196 avb is_unlocked - check device lock state
2197 avb get_uuid - read and print uuid of a partition
2198 avb read_part - read data from partition
2199 avb read_part_hex - read data from partition and output to stdout
2200 avb write_part - write data to partition
2201 avb verify - run full verification chain
2205 tristate "Enable UBI - Unsorted block images commands"
2208 UBI is a software layer above MTD layer which admits use of LVM-like
2209 logical volumes on top of MTD devices, hides some complexities of
2210 flash chips like wear and bad blocks and provides some other useful
2211 capabilities. Please, consult the MTD web site for more details
2212 (www.linux-mtd.infradead.org). Activate this option if you want
2213 to use U-Boot UBI commands.
2214 It is also strongly encouraged to also enable CONFIG_MTD to get full
2217 config CMD_UBI_RENAME
2218 bool "Enable rename"
2222 Enable a "ubi" command to rename ubi volume:
2223 ubi rename <oldname> <newname>
2226 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2228 default y if CMD_UBI
2231 UBIFS is a file system for flash devices which works on top of UBI.
projects / thirdparty / u-boot.git / blob