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
815 Uncompress a zip-compressed memory region.
819 select GZIP_COMPRESSED
821 Compress a memory region with zlib deflate method.
825 menu "Device access commands"
828 #depends on FLASH_CFI_DRIVER
831 ARM Ltd reference designs flash partition access
834 bool "adc - Access Analog to Digital Converters info and data"
838 Shows ADC device info and permit printing one-shot analog converted
839 data from a named Analog to Digital Converter.
844 depends on PARTITIONS
846 Read/modify/write the fields of Bootloader Control Block, usually
847 stored on the flash "misc" partition with its structure defined in:
848 https://android.googlesource.com/platform/bootable/recovery/+/master/
849 bootloader_message/include/bootloader_message/bootloader_message.h
851 Some real-life use-cases include (but are not limited to):
852 - Determine the "boot reason" (and act accordingly):
853 https://source.android.com/devices/bootloader/boot-reason
854 - Get/pass a list of commands from/to recovery:
855 https://android.googlesource.com/platform/bootable/recovery
856 - Inspect/dump the contents of the BCB fields
859 bool "bind/unbind - Bind or unbind a device to/from a driver"
862 Bind or unbind a device to/from a driver from the command line.
863 This is useful in situations where a device may be handled by several
864 drivers. For example, this can be used to bind a UDC to the usb ether
865 gadget driver from the command line.
868 bool "clk - Show clock frequencies"
871 Shows clock frequences by calling a sock_clk_dump() hook function.
872 This is depreated in favour of using the CLK uclass and accessing
873 clock values from associated drivers. However currently no command
877 bool "demo - Demonstration commands for driver model"
880 Provides a 'demo' command which can be used to play around with
881 driver model. To use this properly you will need to enable one or
882 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
883 Otherwise you will always get an empty list of devices. The demo
884 devices are defined in the sandbox device tree, so the easiest
885 option is to use sandbox and pass the -d point to sandbox's
892 Enables the command "dfu" which is used to have U-Boot create a DFU
893 class device via USB. This command requires that the "dfu_alt_info"
894 environment variable be set and define the alt settings to expose to
898 bool "dm - Access to driver model information"
901 Provides access to driver model data structures and information,
902 such as a list of devices, list of uclasses and the state of each
903 device (e.g. activated). This is not required for operation, but
904 can be useful to see the state of driver model for debugging or
908 bool "fastboot - Android fastboot support"
911 This enables the command "fastboot" which enables the Android
912 fastboot mode for the platform. Fastboot is a protocol for
913 downloading images, flashing and device control used on
914 Android devices. Fastboot requires either the network stack
915 enabled or support for acting as a USB device.
917 See doc/android/fastboot.rst for more information.
920 bool "flinfo, erase, protect"
922 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
925 flinfo - print FLASH memory information
927 protect - enable or disable FLASH write protection
936 config CMD_FPGA_LOADBP
937 bool "fpga loadbp - load partial bitstream (Xilinx only)"
940 Supports loading an FPGA device from a bitstream buffer containing
943 config CMD_FPGA_LOADFS
944 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
947 Supports loading an FPGA device from a FAT filesystem.
949 config CMD_FPGA_LOADMK
950 bool "fpga loadmk - load bitstream from image"
953 Supports loading an FPGA device from a image generated by mkimage.
955 config CMD_FPGA_LOADP
956 bool "fpga loadp - load partial bitstream"
959 Supports loading an FPGA device from a bitstream buffer containing
962 config CMD_FPGA_LOAD_SECURE
963 bool "fpga loads - loads secure bitstreams (Xilinx only)"
966 Enables the fpga loads command which is used to load secure
967 (authenticated or encrypted or both) bitstreams on to FPGA.
970 bool "fpgad - dump FPGA registers"
972 (legacy, needs conversion to driver model)
973 Provides a way to dump FPGA registers by calling the board-specific
974 fpga_get_reg() function. This functions similarly to the 'md'
978 bool "fuse - support for the fuse subssystem"
980 (deprecated - needs conversion to driver model)
981 This allows reading, sensing, programming or overriding fuses
982 which control the behaviour of the device. The command uses the
991 bool "GPT (GUID Partition Table) command"
993 select HAVE_BLOCK_DEVICE
994 select PARTITION_UUIDS
997 Enable the 'gpt' command to ready and write GPT style partition
1001 bool "GPT Random UUID generation"
1004 Enable the generation of partitions with random UUIDs if none
1007 config CMD_GPT_RENAME
1008 bool "GPT partition renaming commands"
1011 Enables the 'gpt' command to interchange names on two GPT
1012 partitions via the 'gpt swap' command or to rename single
1013 partitions via the 'rename' command.
1016 bool "ide - Support for IDE drivers"
1019 Provides an 'ide' command which allows accessing the IDE drive,
1020 reseting the IDE interface, printing the partition table and
1021 geting device info. It also enables the 'diskboot' command which
1022 permits booting from an IDE drive.
1025 bool "io - Support for performing I/O accesses"
1027 Provides an 'iod' command to display I/O space and an 'iow' command
1028 to write values to the I/O space. This can be useful for manually
1029 checking the state of devices during boot when debugging device
1033 bool "iotrace - Support for tracing I/O activity"
1035 Provides an 'iotrace' command which supports recording I/O reads and
1036 writes in a trace buffer in memory . It also maintains a checksum
1037 of the trace records (even if space is exhausted) so that the
1038 sequence of I/O accesses can be verified.
1040 When debugging drivers it is useful to see what I/O accesses were
1041 done and in what order.
1043 Even if the individual accesses are of little interest it can be
1044 useful to verify that the access pattern is consistent each time
1045 an operation is performed. In this case a checksum can be used to
1046 characterise the operation of a driver. The checksum can be compared
1047 across different runs of the operation to verify that the driver is
1050 In particular, when performing major refactoring of the driver, where
1051 the access pattern should not change, the checksum provides assurance
1052 that the refactoring work has not broken the driver.
1054 This works by sneaking into the io.h heder for an architecture and
1055 redirecting I/O accesses through iotrace's tracing mechanism.
1057 For now no commands are provided to examine the trace buffer. The
1058 format is fairly simple, so 'md' is a reasonable substitute.
1060 Note: The checksum feature is only useful for I/O regions where the
1061 contents do not change outside of software control. Where this is not
1062 suitable you can fall back to manually comparing the addresses. It
1063 might be useful to enhance tracing to only checksum the accesses and
1064 not the data read/written.
1074 bool "w1 - Support for Dallas 1-Wire protocol"
1076 Dallas 1-wire protocol support
1082 Load a binary file over serial line.
1088 Load an S-Record file over serial line
1093 MMC memory mapped support.
1097 config CMD_BKOPS_ENABLE
1098 bool "mmc bkops enable"
1102 Enable command for setting manual background operations handshake
1103 on a eMMC device. The feature is optionally available on eMMC devices
1104 conforming to standard >= 4.41.
1107 bool "Enable support for RPMB in the mmc command"
1108 depends on SUPPORT_EMMC_RPMB
1110 Enable the commands for reading, writing and programming the
1111 key for the Replay Protection Memory Block partition in eMMC.
1113 config CMD_MMC_SWRITE
1115 depends on MMC_WRITE
1118 Enable support for the "mmc swrite" command to write Android sparse
1126 select MTD_PARTITIONS
1128 MTD commands support.
1132 default y if NAND_SUNXI
1133 depends on MTD_RAW_NAND
1138 config CMD_NAND_TRIMFFS
1139 bool "nand write.trimffs"
1140 default y if ARCH_SUNXI
1142 Allows one to skip empty pages when flashing something on a NAND.
1144 config CMD_NAND_LOCK_UNLOCK
1145 bool "nand lock/unlock"
1147 NAND locking support.
1149 config CMD_NAND_TORTURE
1152 NAND torture support.
1161 NVM Express device support
1164 bool "onenand - access to onenand device"
1167 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1168 various useful features. This command allows reading, writing,
1169 and erasing blocks. It allso provides a way to show and change
1170 bad blocks, and test the device.
1175 Enable the 'osd' command which allows to query information from and
1176 write text data to a on-screen display (OSD) device; a virtual device
1177 associated with a display capable of displaying a text overlay on the
1178 display it's associated with..
1182 select HAVE_BLOCK_DEVICE
1183 select PARTITION_UUIDS
1185 Read and display information about the partition table on
1189 bool "pci - Access PCI devices"
1191 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1192 used on some devices to allow the CPU to communicate with its
1193 peripherals. Sub-commands allow bus enumeration, displaying and
1194 changing configuration space and a few other features.
1197 bool "pinmux - show pins muxing"
1198 default y if PINCTRL
1200 Parse all available pin-controllers and show pins muxing. This
1201 is useful for debug purpoer to check the pin muxing and to know if
1202 a pin is configured as a GPIO or as an alternate function.
1207 Poweroff/Shutdown the system
1210 bool "read - Read binary data from a partition"
1212 Provides low-level access to the data in a partition.
1214 config CMD_REMOTEPROC
1216 depends on REMOTEPROC
1218 Support for Remote Processor control
1221 bool "sata - Access SATA subsystem"
1224 SATA (Serial Advanced Technology Attachment) is a serial bus
1225 standard for connecting to hard drives and other storage devices.
1226 This command provides information about attached devices and allows
1227 reading, writing and other operations.
1229 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1230 Attachment, where AT refers to an IBM AT (Advanced Technology)
1231 computer released in 1984.
1234 bool "saves - Save a file over serial in S-Record format"
1236 Provides a way to save a binary file using the Motorola S-Record
1237 format over the serial line.
1240 bool "scsi - Access to SCSI devices"
1243 This provides a 'scsi' command which provides access to SCSI (Small
1244 Computer System Interface) devices. The command provides a way to
1245 scan the bus, reset the bus, read and write data and get information
1249 bool "sdram - Print SDRAM configuration information"
1251 Provides information about attached SDRAM. This assumed that the
1252 SDRAM has an EEPROM with information that can be read using the
1253 I2C bus. This is only available on some boards.
1257 depends on DM_SPI_FLASH || SPI_FLASH
1258 default y if DM_SPI_FLASH
1263 bool "sf test - Allow testing of SPI flash"
1266 Provides a way to test that SPI flash is working correctly. The
1267 test is destructive, in that an area of SPI flash must be provided
1268 for the test to use. Performance information is also provided,
1269 measuring the performance of reading, writing and erasing in
1270 Mbps (Million Bits Per Second). This value should approximately
1271 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1272 everything is working properly.
1275 bool "sspi - Command to access spi device"
1278 SPI utility command.
1280 config DEFAULT_SPI_BUS
1281 int "default spi bus used by sspi command"
1285 config DEFAULT_SPI_MODE
1286 hex "default spi mode used by sspi command (see include/spi.h)"
1291 bool "tsi148 - Command to access tsi148 device"
1293 This provides various sub-commands to initialise and configure the
1294 Turndra tsi148 device. See the command help for full details.
1297 bool "Enable UFS - Universal Flash Subsystem commands"
1300 "This provides commands to initialise and configure universal flash
1304 bool "universe - Command to set up the Turndra Universe controller"
1306 This allows setting up the VMEbus provided by this controller.
1307 See the command help for full details.
1311 select HAVE_BLOCK_DEVICE
1317 select USB_FUNCTION_SDP
1319 Enables the command "sdp" which is used to have U-Boot emulating the
1320 Serial Download Protocol (SDP) via USB.
1324 depends on USB_FUNCTION_ROCKUSB
1326 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1327 read/write info, image to/from devices. This enable rockusb command
1328 support to communication with rockusb device. for more detail about
1329 this command, please read doc/README.rockusb.
1331 config CMD_USB_MASS_STORAGE
1332 bool "UMS usb mass storage"
1333 select USB_FUNCTION_MASS_STORAGE
1335 USB mass storage support
1342 VirtIO block device support
1348 This provides commands to control the watchdog timer devices.
1354 Enable the command "axi" for accessing AXI (Advanced eXtensible
1355 Interface) busses, a on-chip interconnect specification for managing
1356 functional blocks in SoC designs, which is also often used in designs
1357 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1361 menu "Shell scripting commands"
1367 Echo args to console
1373 Return true/false on integer compare.
1379 Run script from memory
1385 Evaluate boolean and math expressions and store the result in an env
1387 Also supports loading the value at a memory location into a variable.
1388 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1392 menu "Android support commands"
1394 config CMD_AB_SELECT
1397 depends on ANDROID_AB
1399 On Android devices with more than one boot slot (multiple copies of
1400 the kernel and system images) this provides a command to select which
1401 slot should be used to boot from and register the boot attempt. This
1402 is used by the new A/B update model where one slot is updated in the
1403 background while running from the other slot.
1410 bool "Network commands"
1420 bootp - boot image via network using BOOTP/TFTP protocol
1424 depends on CMD_BOOTP
1426 Boot image via network using DHCP/TFTP protocol
1428 config BOOTP_BOOTPATH
1429 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1431 depends on CMD_BOOTP
1433 Even though the config is called BOOTP_BOOTPATH, it stores the
1434 path in the variable 'rootpath'.
1437 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1439 depends on CMD_BOOTP
1441 The primary DNS server is stored as 'dnsip'. If two servers are
1442 returned, you must set BOOTP_DNS2 to store that second server IP
1446 bool "Store 'dnsip2' from BOOTP/DHCP server"
1447 depends on BOOTP_DNS
1449 If a DHCP client requests the DNS server IP from a DHCP server,
1450 it is possible that more than one DNS serverip is offered to the
1451 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1452 server IP will be stored in the additional environment
1453 variable "dnsip2". The first DNS serverip is always
1454 stored in the variable "dnsip", when BOOTP_DNS is defined.
1456 config BOOTP_GATEWAY
1457 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1459 depends on CMD_BOOTP
1461 config BOOTP_HOSTNAME
1462 bool "Request & store 'hostname' from BOOTP/DHCP server"
1464 depends on CMD_BOOTP
1466 The name may or may not be qualified with the local domain name.
1468 config BOOTP_PREFER_SERVERIP
1469 bool "serverip variable takes precedent over DHCP server IP."
1470 depends on CMD_BOOTP
1472 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1474 With this option enabled, the 'serverip' variable in the environment
1475 takes precedence over DHCP server IP and will only be set by the DHCP
1476 server if not already set in the environment.
1478 config BOOTP_SUBNETMASK
1479 bool "Request & store 'netmask' from BOOTP/DHCP server"
1481 depends on CMD_BOOTP
1483 config BOOTP_NTPSERVER
1484 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1485 depends on CMD_BOOTP
1490 Selecting this will allow capturing all Ethernet packets and store
1491 them in physical memory in a PCAP formated file,
1492 later to be analyzed by PCAP reader application (IE. WireShark).
1495 bool "Send PXE client arch to BOOTP/DHCP server"
1497 depends on CMD_BOOTP && CMD_PXE
1499 Supported for ARM, ARM64, and x86 for now.
1501 config BOOTP_PXE_CLIENTARCH
1503 depends on BOOTP_PXE
1504 default 0x16 if ARM64
1508 config BOOTP_VCI_STRING
1510 depends on CMD_BOOTP
1511 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1512 default "U-Boot.armv8" if ARM64
1513 default "U-Boot.arm" if ARM
1520 tftpboot - boot image via network using TFTP protocol
1524 depends on CMD_TFTPBOOT
1526 TFTP put command, for uploading files to a server
1530 depends on CMD_TFTPBOOT
1532 Act as a TFTP server and boot the first received file
1534 config NET_TFTP_VARS
1535 bool "Control TFTP timeout and count through environment"
1536 depends on CMD_TFTPBOOT
1539 If set, allows controlling the TFTP timeout through the
1540 environment variable tftptimeout, and the TFTP maximum
1541 timeout count through the variable tftptimeoutcountmax.
1542 If unset, timeout and maximum are hard-defined as 1 second
1543 and 10 timouts per TFTP transfer.
1548 Boot image via network using RARP/TFTP protocol
1554 Boot image via network using NFS protocol.
1560 If set, allows 802.3(clause 22) MII Management functions interface access
1561 The management interface specified in Clause 22 provides
1562 a simple, two signal, serial interface to connect a
1563 Station Management entity and a managed PHY for providing access
1564 to management parameters and services.
1565 The interface is referred to as the MII management interface.
1571 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1572 The MDIO interface is orthogonal to the MII interface and extends
1573 it by adding access to more registers through indirect addressing.
1578 Send ICMP ECHO_REQUEST to network host
1583 Perform CDP network configuration
1588 Synchronize RTC via network
1593 Lookup the IP of a hostname
1595 config CMD_LINK_LOCAL
1599 Acquire a network IP address using the link-local protocol
1606 Allow control of L2 Ethernet switch commands. These are supported
1607 by the vsc9953 Ethernet driver at present. Sub-commands allow
1608 operations such as enabling / disabling a port and
1609 viewing/maintaining the filtering database (FDB)
1615 Boot image via network using PXE protocol
1620 Wait for wake-on-lan Magic Packet
1624 menu "Misc commands"
1627 bool "Enable 'bmp' command"
1628 depends on LCD || DM_VIDEO || VIDEO
1630 This provides a way to obtain information about a BMP-format image
1631 and to display it. BMP (which presumably stands for BitMaP) is a
1632 file format defined by Microsoft which supports images of various
1633 depths, formats and compression methods. Headers on the file
1634 determine the formats used. This command can be used by first loading
1635 the image into RAM, then using this command to look at it or display
1638 config CMD_BOOTCOUNT
1640 depends on BOOTCOUNT_LIMIT
1642 Enable the bootcount command, which allows interrogation and
1643 reset of the bootcounter.
1646 bool "Enable board-specific commands"
1648 (deprecated: instead, please define a Kconfig option for each command)
1650 Some boards have board-specific commands which are only enabled
1651 during developemnt and need to be turned off for production. This
1652 option provides a way to control this. The commands that are enabled
1653 vary depending on the board.
1655 config CMD_BLOCK_CACHE
1656 bool "blkcache - control and stats for block cache"
1657 depends on BLOCK_CACHE
1658 default y if BLOCK_CACHE
1660 Enable the blkcache command, which can be used to control the
1661 operation of the cache functions.
1662 This is most useful when fine-tuning the operation of the cache
1663 during development, but also allows the cache to be disabled when
1664 it might hurt performance (e.g. when using the ums command).
1667 bool "icache or dcache"
1669 Enable the "icache" and "dcache" commands
1671 config CMD_CONITRACE
1672 bool "conitrace - trace console input codes"
1674 Enable the 'conitrace' command which displays the codes received
1675 from the console input as hexadecimal numbers.
1678 bool "Enable clear screen command 'cls'"
1679 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1682 Enable the 'cls' command which clears the screen contents
1683 on video frame buffer.
1686 bool "efidebug - display/configure UEFI environment"
1687 depends on EFI_LOADER
1688 select EFI_DEVICE_PATH_TO_TEXT
1691 Enable the 'efidebug' command which provides a subset of UEFI
1692 shell utility with simplified functionality. It will be useful
1693 particularly for managing boot parameters as well as examining
1694 various EFI status for debugging.
1696 config CMD_EXCEPTION
1697 bool "exception - raise exception"
1698 depends on ARM || RISCV || X86
1700 Enable the 'exception' command which allows to raise an exception.
1707 Enable the 'led' command which allows for control of LEDs supported
1708 by the board. The LEDs can be listed with 'led list' and controlled
1709 with led on/off/togle/blink. Any LED drivers can be controlled with
1710 this command, e.g. led_gpio.
1717 Enable the 'date' command for getting/setting the time/date in RTC
1723 Run commands and summarize execution time.
1726 bool "gettime - read elapsed time"
1728 Enable the 'gettime' command which reads the elapsed time since
1729 U-Boot started running. This shows the time in seconds and
1730 milliseconds. See also the 'bootstage' command which provides more
1731 flexibility for boot timing.
1738 Print bytes from the hardware random number generator.
1740 # TODO: rename to CMD_SLEEP
1745 Delay execution for some time
1748 bool "support for multiprocessor"
1750 This provides an option to brinup
1751 different processors in multiprocessor
1757 Access the system timer.
1763 This provides basic access to the U-Boot's sound support. The main
1764 feature is to play a beep.
1766 sound init - set up sound system
1767 sound play - play a sound
1773 Boot image via local extlinux.conf file
1779 This provides access to the QEMU firmware interface. The main
1780 feature is to allow easy loading of files passed to qemu-system
1781 via -kernel / -initrd
1783 source "cmd/mvebu/Kconfig"
1786 bool "terminal - provides a way to attach a serial terminal"
1788 Provides a 'cu'-like serial terminal command. This can be used to
1789 access other serial ports from the system console. The terminal
1790 is very simple with no special processing of characters. As with
1791 cu, you can press ~. (tilde followed by period) to exit.
1794 bool "uuid, guid - generation of unique IDs"
1797 This enables two commands:
1799 uuid - generate random Universally Unique Identifier
1800 guid - generate Globally Unique Identifier based on random UUID
1802 The two commands are very similar except for the endianness of the
1807 source "cmd/ti/Kconfig"
1809 config CMD_BOOTSTAGE
1810 bool "Enable the 'bootstage' command"
1811 depends on BOOTSTAGE
1813 Add a 'bootstage' command which supports printing a report
1814 and un/stashing of bootstage data.
1816 menu "Power commands"
1818 bool "Enable Driver Model PMIC command"
1821 This is the pmic command, based on a driver model pmic's API.
1822 Command features are unchanged:
1823 - list - list pmic devices
1824 - pmic dev <id> - show or [set] operating pmic device (NEW)
1825 - pmic dump - dump registers
1826 - pmic read address - read byte of register at address
1827 - pmic write address - write byte to register at address
1828 The only one change for this command is 'dev' subcommand.
1830 config CMD_REGULATOR
1831 bool "Enable Driver Model REGULATOR command"
1832 depends on DM_REGULATOR
1834 This command is based on driver model regulator's API.
1835 User interface features:
1836 - list - list regulator devices
1837 - regulator dev <id> - show or [set] operating regulator device
1838 - regulator info - print constraints info
1839 - regulator status - print operating status
1840 - regulator value <val] <-f> - print/[set] voltage value [uV]
1841 - regulator current <val> - print/[set] current value [uA]
1842 - regulator mode <id> - print/[set] operating mode id
1843 - regulator enable - enable the regulator output
1844 - regulator disable - disable the regulator output
1846 The '-f' (force) option can be used for set the value which exceeds
1847 the limits, which are found in device-tree and are kept in regulator's
1848 uclass platdata structure.
1852 menu "Security commands"
1854 bool "Enable the 'aes' command"
1857 This provides a means to encrypt and decrypt data using the AES
1858 (Advanced Encryption Standard). This algorithm uses a symetric key
1859 and is widely used as a streaming cipher. Different key lengths are
1860 supported by the algorithm but this command only supports 128 bits
1864 bool "Enable the 'blob' command"
1866 This is used with the Freescale secure boot mechanism.
1868 Freescale's SEC block has built-in Blob Protocol which provides
1869 a method for protecting user-defined data across system power
1870 cycles. SEC block protects data in a data structure called a Blob,
1871 which provides both confidentiality and integrity protection.
1873 Encapsulating data as a blob
1874 Each time that the Blob Protocol is used to protect data, a
1875 different randomly generated key is used to encrypt the data.
1876 This random key is itself encrypted using a key which is derived
1877 from SoC's non-volatile secret key and a 16 bit Key identifier.
1878 The resulting encrypted key along with encrypted data is called a
1879 blob. The non-volatile secure key is available for use only during
1882 During decapsulation, the reverse process is performed to get back
1886 blob enc - encapsulating data as a cryptgraphic blob
1887 blob dec - decapsulating cryptgraphic blob to get the data
1891 blob enc src dst len km
1893 Encapsulate and create blob of data $len bytes long
1894 at address $src and store the result at address $dst.
1895 $km is the 16 byte key modifier is also required for
1896 generation/use as key for cryptographic operation. Key
1897 modifier should be 16 byte long.
1899 blob dec src dst len km
1901 Decapsulate the blob of data at address $src and
1902 store result of $len byte at addr $dst.
1903 $km is the 16 byte key modifier is also required for
1904 generation/use as key for cryptographic operation. Key
1905 modifier should be 16 byte long.
1908 bool "Support 'hash' command"
1911 This provides a way to hash data in memory using various supported
1912 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1913 saved to memory or to an environment variable. It is also possible
1914 to verify a hash against data in memory.
1917 bool "Support the 'hvc' command"
1918 depends on ARM_SMCCC
1920 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1921 development and testing.
1924 bool "Support the 'smc' command"
1925 depends on ARM_SMCCC
1927 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1928 development and testing.
1934 Add -v option to verify data against a hash.
1944 bool "Enable the 'tpm' command"
1945 depends on TPM_V1 || TPM_V2
1946 select CMD_TPM_V1 if TPM_V1
1947 select CMD_TPM_V2 if TPM_V2
1949 This provides a means to talk to a TPM from the command line. A wide
1950 range of commands if provided - see 'tpm help' for details. The
1951 command requires a suitable TPM on your board and the correct driver
1957 bool "Enable the 'tpm test' command"
1960 This provides a a series of tests to confirm that the TPMv1.x is
1961 working correctly. The tests cover initialisation, non-volatile RAM,
1962 extend, global lock and checking that timing is within expectations.
1963 The tests pass correctly on Infineon TPMs but may need to be adjusted
1970 menu "Firmware commands"
1972 bool "Enable crosec command"
1976 Enable command-line access to the Chrome OS EC (Embedded
1977 Controller). This provides the 'crosec' command which has
1978 a number of sub-commands for performing EC tasks such as
1979 updating its flash, accessing a small saved context area
1980 and talking to the I2C bus behind the EC (if there is one).
1983 menu "Filesystem commands"
1985 bool "Enable the 'btrsubvol' command"
1988 This enables the 'btrsubvol' command to list subvolumes
1989 of a BTRFS filesystem. There are no special commands for
1990 listing BTRFS directories or loading BTRFS files - this
1991 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1992 when BTRFS is enabled (see FS_BTRFS).
1995 bool "Enable the 'cbfs' command"
1998 Define this to enable support for reading from a Coreboot
1999 filesystem. This is a ROM-based filesystem used for accessing files
2000 on systems that use coreboot as the first boot-loader and then load
2001 U-Boot to actually boot the Operating System. Available commands are
2002 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2005 bool "Enable the 'cramfs' command"
2006 depends on FS_CRAMFS
2008 This provides commands for dealing with CRAMFS (Compressed ROM
2009 filesystem). CRAMFS is useful when space is tight since files are
2010 compressed. Two commands are provided:
2012 cramfsls - lists files in a cramfs image
2013 cramfsload - loads a file from a cramfs image
2016 bool "ext2 command support"
2019 Enables EXT2 FS command
2022 bool "ext4 command support"
2025 Enables EXT4 FS command
2027 config CMD_EXT4_WRITE
2029 bool "ext4 write command support"
2032 Enables EXT4 FS write command
2035 bool "FAT command support"
2038 Support for the FAT fs
2040 config CMD_FS_GENERIC
2041 bool "filesystem commands"
2043 Enables filesystem commands (e.g. load, ls) that work for multiple
2047 bool "fsuuid command"
2049 Enables fsuuid command for filesystem UUID.
2052 bool "jffs2 command"
2055 Enables commands to support the JFFS2 (Journalling Flash File System
2056 version 2) filesystem. This enables fsload, ls and fsinfo which
2057 provide the ability to load files, list directories and obtain
2058 filesystem information.
2061 bool "MTD partition support"
2064 MTD partitioning tool support.
2065 It is strongly encouraged to avoid using this command
2066 anymore along with 'sf', 'nand', 'onenand'. One can still
2067 declare the partitions in the mtdparts environment variable
2068 but better use the MTD stack and the 'mtd' command instead.
2070 config CMD_MTDPARTS_SPREAD
2071 bool "Padd partition size to take account of bad blocks"
2072 depends on CMD_MTDPARTS
2074 This enables the 'spread' sub-command of the mtdparts command.
2075 This command will modify the existing mtdparts variable by increasing
2076 the size of the partitions such that 1) each partition's net size is
2077 at least as large as the size specified in the mtdparts variable and
2078 2) each partition starts on a good block.
2080 config CMD_MTDPARTS_SHOW_NET_SIZES
2081 bool "Show net size (w/o bad blocks) of partitions"
2082 depends on CMD_MTDPARTS
2084 Adds two columns to the printed partition table showing the
2085 effective usable size of a partition, if bad blocks are taken
2088 config MTDIDS_DEFAULT
2089 string "Default MTD IDs"
2090 depends on MTD || SPI_FLASH
2092 Defines a default MTD IDs list for use with MTD partitions in the
2093 Linux MTD command line partitions format.
2095 config MTDPARTS_DEFAULT
2096 string "Default MTD partition scheme"
2097 depends on MTD || SPI_FLASH
2099 Defines a default MTD partitioning scheme in the Linux MTD command
2100 line partitions format
2103 bool "reiser - Access to reiserfs filesystems"
2105 This provides two commands which operate on a resierfs filesystem,
2106 commonly used some years ago:
2108 reiserls - list files
2109 reiserload - load a file
2112 bool "yaffs2 - Access of YAFFS2 filesystem"
2116 This provides commands for accessing a YAFFS2 filesystem. Yet
2117 Another Flash Filesystem 2 is a filesystem designed specifically
2118 for NAND flash. It incorporates bad-block management and ensures
2119 that device writes are sequential regardless of filesystem
2123 bool "zfs - Access of ZFS filesystem"
2125 This provides commands to accessing a ZFS filesystem, commonly used
2126 on Solaris systems. Two sub-commands are provided:
2128 zfsls - list files in a directory
2129 zfsload - load a file
2131 See doc/README.zfs for more details.
2135 menu "Debug commands"
2140 The bedbug (emBEDded deBUGger) command provides debugging features
2141 for some PowerPC processors. For details please see the
2142 documentation in doc/README.bedbug.
2145 bool "diag - Board diagnostics"
2147 This command provides access to board diagnostic tests. These are
2148 called Power-on Self Tests (POST). The command allows listing of
2149 available tests and running either all the tests, or specific tests
2153 bool "irq - Show information about interrupts"
2154 depends on !ARM && !MIPS && !SH
2156 This enables two commands:
2158 interrupts - enable or disable interrupts
2159 irqinfo - print device-specific interrupt information
2162 bool "kgdb - Allow debugging of U-Boot with gdb"
2165 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2166 over a serial link for debugging purposes. This allows
2167 single-stepping, inspecting variables, etc. This is supported only
2168 on PowerPC at present.
2171 bool "log - Generation, control and access to logging"
2174 This provides access to logging features. It allows the output of
2175 log data to be controlled to a limited extent (setting up the default
2176 maximum log level for emitting of records). It also provides access
2177 to a command used for testing the log system.
2180 bool "trace - Support tracing of function calls and timing"
2182 Enables a command to control using of function tracing within
2183 U-Boot. This allows recording of call traces including timing
2184 information. The command can write data to memory for exporting
2185 for analysis (e.g. using bootchart). See doc/README.trace for full
2189 bool "avb - Android Verified Boot 2.0 operations"
2190 depends on AVB_VERIFY
2193 Enables a "avb" command to perform verification of partitions using
2194 Android Verified Boot 2.0 functionality. It includes such subcommands:
2195 avb init - initialize avb2 subsystem
2196 avb read_rb - read rollback index
2197 avb write_rb - write rollback index
2198 avb is_unlocked - check device lock state
2199 avb get_uuid - read and print uuid of a partition
2200 avb read_part - read data from partition
2201 avb read_part_hex - read data from partition and output to stdout
2202 avb write_part - write data to partition
2203 avb verify - run full verification chain
2207 tristate "Enable UBI - Unsorted block images commands"
2210 UBI is a software layer above MTD layer which admits use of LVM-like
2211 logical volumes on top of MTD devices, hides some complexities of
2212 flash chips like wear and bad blocks and provides some other useful
2213 capabilities. Please, consult the MTD web site for more details
2214 (www.linux-mtd.infradead.org). Activate this option if you want
2215 to use U-Boot UBI commands.
2216 It is also strongly encouraged to also enable CONFIG_MTD to get full
2219 config CMD_UBI_RENAME
2220 bool "Enable rename"
2224 Enable a "ubi" command to rename ubi volume:
2225 ubi rename <oldname> <newname>
2228 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2230 default y if CMD_UBI
2233 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob