1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
58 config SYS_PROMPT_HUSH_PS2
59 string "Hush shell secondary prompt"
60 depends on HUSH_PARSER
63 This defines the secondary prompt string, which is
64 printed when the command interpreter needs more input
65 to complete a command. Usually "> ".
68 string "Command execution tracer"
72 This option enables the possiblity to print all commands before
73 executing them and after all variables are evaluated (similar
74 to Bash's xtrace/'set -x' feature).
75 To enable the tracer a variable "xtrace" needs to be defined in
89 List and dump ACPI tables. ACPI (Advanced Configuration and Power
90 Interface) is used mostly on x86 for providing information to the
91 Operating System about devices in the system. The tables are set up
92 by the firmware, typically U-Boot but possibly an earlier firmware
93 module, if U-Boot is chain-loaded from something else. ACPI tables
94 can also include code, to perform hardware-specific tasks required
95 by the Operating Systems. This allows some amount of separation
96 between the firmware and OS, and is particularly useful when you
97 want to make hardware changes without the OS needing to be adjusted.
110 Print ".config" contents.
112 If this option is enabled, the ".config" file contents are embedded
113 in the U-Boot image and can be printed on the console by the "config"
114 command. This provides information of which options are enabled on
121 Print console devices and information.
126 Print information about available CPUs. This normally shows the
127 number of CPUs, type (e.g. manufacturer, architecture, product or
128 internal name) and clock frequency. Other information may be
129 available depending on the CPU driver.
135 Print GPL license text
140 Provides access to the Intel Power-Management Controller (PMC) so
141 that its state can be examined. This does not currently support
142 changing the state but it is still useful for debugging and seeing
151 config CMD_TLV_EEPROM
153 depends on I2C_EEPROM
155 Display and program the system EEPROM data block in ONIE Tlvinfo
156 format. TLV stands for Type-Length-Value.
158 config SPL_CMD_TLV_EEPROM
159 bool "tlv_eeprom for SPL"
160 depends on SPL_I2C_EEPROM
161 select SPL_DRIVERS_MISC_SUPPORT
163 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
167 depends on RISCV_SMODE && SBI_V02
169 Display information about the SBI implementation.
179 Run the command stored in the environment "bootcmd", i.e.
180 "bootd" does the same thing as "run bootcmd".
186 Boot an application image from the memory.
189 bool "Support booting UEFI FIT images"
190 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
193 Support booting UEFI FIT images via the bootm command.
198 Boot the Linux zImage
202 depends on ARM64 || RISCV
205 Boot an AArch64 Linux Kernel image from memory.
208 bool "Support booting Linux OS images"
209 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
212 Support booting the Linux kernel directly via a command such as bootm
216 bool "Support booting NetBSD (non-EFI) loader images"
220 Support booting NetBSD via the bootm command.
222 config BOOTM_OPENRTOS
223 bool "Support booting OPENRTOS / FreeRTOS images"
226 Support booting OPENRTOS / FreeRTOS via the bootm command.
229 bool "Support booting Enea OSE images"
230 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
233 Support booting Enea OSE images via the bootm command.
236 bool "Support booting Plan9 OS images"
240 Support booting Plan9 images via the bootm command.
243 bool "Support booting RTEMS OS images"
247 Support booting RTEMS images via the bootm command.
250 bool "Support booting VxWorks OS images"
254 Support booting VxWorks images via the bootm command.
258 depends on EFI_LOADER
261 Boot an EFI image from memory.
263 config CMD_BOOTEFI_HELLO_COMPILE
264 bool "Compile a standard EFI hello world binary for testing"
265 depends on CMD_BOOTEFI && !CPU_V7M
268 This compiles a standard EFI hello world application with U-Boot so
269 that it can be used with the test/py testing framework. This is useful
270 for testing that EFI is working at a basic level, and for bringing
271 up EFI support on a new architecture.
273 No additional space will be required in the resulting U-Boot binary
274 when this option is enabled.
276 config CMD_BOOTEFI_HELLO
277 bool "Allow booting a standard EFI hello world for testing"
278 depends on CMD_BOOTEFI_HELLO_COMPILE
279 default y if CMD_BOOTEFI_SELFTEST
281 This adds a standard EFI hello world application to U-Boot so that
282 it can be used with the 'bootefi hello' command. This is useful
283 for testing that EFI is working at a basic level, and for bringing
284 up EFI support on a new architecture.
286 source lib/efi_selftest/Kconfig
292 Add an ANSI terminal boot menu command.
297 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
298 image into RAM, dump image structure information, etc. Those dtb/dtbo
299 files should be merged in one dtb further, which needs to be passed to
300 the kernel, as part of a boot process.
304 depends on ANDROID_BOOT_IMAGE
306 Android Boot Image manipulation commands. Allows one to extract
307 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
308 obtain corresponding meta-information from boot.img.
310 See doc/android/boot-image.rst for details.
313 bool "bootelf, bootvx"
317 Boot an ELF/vxWorks image from the memory.
320 bool "Flattened Device Tree utility commands"
324 Do FDT related setup before booting into the Operating System.
330 Start an application at a given address.
336 Run the command in the given environment variable.
342 Print header information for application image.
347 List all images found in flash
353 Extract a part of a multi-image.
356 bool "spl export - Export boot information for Falcon boot"
359 Falcon mode allows booting directly from SPL into an Operating
360 System such as Linux, thus skipping U-Boot proper. See
361 doc/README.falcon for full information about how to use this
364 config CMD_SPL_NAND_OFS
365 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
366 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
369 This provides the offset of the command line arguments for Linux
370 when booting from NAND in Falcon mode. See doc/README.falcon
371 for full information about how to use this option (and also see
372 board/gateworks/gw_ventana/README for an example).
374 config CMD_SPL_NOR_OFS
375 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
376 depends on CMD_SPL && SPL_NOR_SUPPORT
379 This provides the offset of the command line arguments or dtb for
380 Linux when booting from NOR in Falcon mode.
382 config CMD_SPL_WRITE_SIZE
383 hex "Size of argument area"
387 This provides the size of the command-line argument area in NAND
388 flash used by Falcon-mode boot. See the documentation until CMD_SPL
391 config CMD_THOR_DOWNLOAD
392 bool "thor - TIZEN 'thor' download"
395 Implements the 'thor' download protocol. This is a way of
396 downloading a software update over USB from an attached host.
397 There is no documentation about this within the U-Boot source code
398 but you should be able to find something on the interwebs.
401 bool "zboot - x86 boot command"
403 With x86 machines it is common to boot a bzImage file which
404 contains both a kernel and a setup.bin file. The latter includes
405 configuration information from the dark ages which x86 boards still
406 need to pick things out of.
408 Consider using FIT in preference to this since it supports directly
409 booting both 32- and 64-bit kernels, as well as secure boot.
410 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
414 menu "Environment commands"
417 bool "ask for env variable"
419 Ask for environment variable
437 Edit environment variable.
442 Allow for searching environment variables
448 Save all environment variables into the compiled-in persistent
454 depends on CMD_SAVEENV
456 Erase environment variables from the compiled-in persistent
459 config CMD_ENV_EXISTS
463 Check if a variable is defined in the environment for use in
466 config CMD_ENV_CALLBACK
467 bool "env callbacks - print callbacks and their associated variables"
469 Some environment variable have callbacks defined by
470 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
471 For example changing "baudrate" adjust the serial baud rate. This
472 command lists the currently defined callbacks.
475 bool "env flags -print variables that have non-default flags"
477 Some environment variables have special flags that control their
478 behaviour. For example, serial# can only be written once and cannot
479 be deleted. This command shows the variables that have special
482 config CMD_NVEDIT_EFI
483 bool "env [set|print] -e - set/print UEFI variables"
484 depends on EFI_LOADER
487 UEFI variables are encoded as some form of U-Boot variables.
488 If enabled, we are allowed to set/print UEFI variables using
489 "env" command with "-e" option without knowing details.
491 config CMD_NVEDIT_INFO
492 bool "env info - print or evaluate environment information"
494 Print environment information:
495 - env_valid : is environment valid
496 - env_ready : is environment imported into hash table
497 - env_use_default : is default environment used
499 This command can be optionally used for evaluation in scripts:
500 [-d] : evaluate whether default environment is used
501 [-p] : evaluate whether environment can be persisted
503 The result of multiple evaluations will be combined with AND.
505 config CMD_NVEDIT_LOAD
508 Load all environment variables from the compiled-in persistent
511 config CMD_NVEDIT_SELECT
514 Select the compiled-in persistent storage of environment variables.
518 menu "Memory commands"
523 Compute binary operations (xor, or, and) of byte arrays of arbitrary
524 size from memory and store the result in memory or the environment.
528 default y if BLOBLIST
530 Show information about the bloblist, a collection of binary blobs
531 held in memory that persist between SPL and U-Boot. In the case of
532 x86 devices the bloblist can be used to hold ACPI tables so that they
533 remain available in memory.
546 Add -v option to verify data against a crc32 checksum.
549 bool "eeprom - EEPROM subsystem"
551 (deprecated, needs conversion to driver model)
552 Provides commands to read and write EEPROM (Electrically Erasable
553 Programmable Read Only Memory) chips that are connected over an
556 config CMD_EEPROM_LAYOUT
557 bool "Enable layout-aware eeprom commands"
558 depends on CMD_EEPROM
560 (deprecated, needs conversion to driver model)
561 When enabled, additional eeprom sub-commands become available.
563 eeprom print - prints the contents of the eeprom in a human-readable
564 way (eeprom layout fields, and data formatted to be fit for human
567 eeprom update - allows user to update eeprom fields by specifying
568 the field name, and providing the new data in a human readable format
569 (same format as displayed by the eeprom print command).
571 Both commands can either auto detect the layout, or be told which
575 __weak int parse_layout_version(char *str)
576 - override to provide your own layout name parsing
577 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
579 - override to setup the layout metadata based on the version
580 __weak int eeprom_layout_detect(unsigned char *data)
581 - override to provide your own algorithm for detecting layout
584 - contains various printing and updating functions for common
585 types of eeprom fields. Can be used for defining
588 config EEPROM_LAYOUT_HELP_STRING
589 string "Tells user what layout names are supported"
590 depends on CMD_EEPROM_LAYOUT
591 default "<not defined>"
593 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
599 Infinite write loop on address range
606 Compute MD5 checksum.
611 depends on CMD_MD5SUM
613 Add -v option to verify data against an MD5 checksum.
618 Display memory information.
621 bool "md, mm, nm, mw, cp, cmp, base, loop"
626 mm - memory modify (auto-incrementing address)
627 nm - memory modify (constant address)
628 mw - memory write (fill)
631 base - print or set address offset
632 loop - initialize loop on address range
634 config CMD_MEM_SEARCH
635 bool "ms - Memory search"
637 Memory-search command
639 This allows searching through a region of memory looking for hex
640 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
641 support it). It is also possible to search for a string. The
642 command accepts a memory range and a list of values to search for.
643 The values need to appear in memory in the same order they are given
644 in the command. At most 10 matches can be returned at a time, but
645 pressing return will show the next 10 matches. Environment variables
646 are set for use with scripting (memmatches, memaddr, mempos).
649 bool "Enable cyclic md/mw commands"
650 depends on CMD_MEMORY
652 Add the "mdc" and "mwc" memory commands. These are cyclic
657 This command will print 4 bytes (10,11,12,13) each 500 ms.
659 => mwc.l 100 12345678 10
660 This command will write 12345678 to address 100 all 10 ms.
665 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
667 random - fill memory with random data
672 Simple RAM read/write test.
676 config SYS_ALT_MEMTEST
677 bool "Alternative test"
679 Use a more complete alternative memory test.
683 config SYS_ALT_MEMTEST_BITFLIP
687 The alternative memory test includes bitflip test since 2020.07.
688 The bitflip test significantly increases the overall test time.
689 Bitflip test can optionally be disabled here.
693 config SYS_MEMTEST_START
694 hex "default start address for mtest"
697 This is the default start address for mtest for simple read/write
698 test. If no arguments are given to mtest, default address is used
701 config SYS_MEMTEST_END
702 hex "default end address for mtest"
705 This is the default end address for mtest for simple read/write
706 test. If no arguments are given to mtest, default address is used
715 Compute SHA1 checksum.
717 config SHA1SUM_VERIFY
719 depends on CMD_SHA1SUM
721 Add -v option to verify data against a SHA1 checksum.
724 bool "strings - display strings in memory"
726 This works similarly to the Unix 'strings' command except that it
727 works with a memory range. String of printable characters found
728 within the range are displayed. The minimum number of characters
729 for a sequence to be considered a string can be provided.
733 menu "Compression commands"
737 default y if CMD_BOOTI
740 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
745 default y if CMD_BOOTI
748 Support decompressing an LZ4 image from memory region.
752 default y if CMD_BOOTI
755 Uncompress a zip-compressed memory region.
759 select GZIP_COMPRESSED
761 Compress a memory region with zlib deflate method.
765 menu "Device access commands"
768 #depends on FLASH_CFI_DRIVER
771 ARM Ltd reference designs flash partition access
774 bool "adc - Access Analog to Digital Converters info and data"
776 depends on DM_REGULATOR
778 Shows ADC device info and permit printing one-shot analog converted
779 data from a named Analog to Digital Converter.
784 depends on PARTITIONS
786 Read/modify/write the fields of Bootloader Control Block, usually
787 stored on the flash "misc" partition with its structure defined in:
788 https://android.googlesource.com/platform/bootable/recovery/+/master/
789 bootloader_message/include/bootloader_message/bootloader_message.h
791 Some real-life use-cases include (but are not limited to):
792 - Determine the "boot reason" (and act accordingly):
793 https://source.android.com/devices/bootloader/boot-reason
794 - Get/pass a list of commands from/to recovery:
795 https://android.googlesource.com/platform/bootable/recovery
796 - Inspect/dump the contents of the BCB fields
799 bool "bind/unbind - Bind or unbind a device to/from a driver"
802 Bind or unbind a device to/from a driver from the command line.
803 This is useful in situations where a device may be handled by several
804 drivers. For example, this can be used to bind a UDC to the usb ether
805 gadget driver from the command line.
808 bool "clk - Show clock frequencies"
811 Shows clock frequences by calling a sock_clk_dump() hook function.
812 This is depreated in favour of using the CLK uclass and accessing
813 clock values from associated drivers. However currently no command
817 bool "demo - Demonstration commands for driver model"
820 Provides a 'demo' command which can be used to play around with
821 driver model. To use this properly you will need to enable one or
822 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
823 Otherwise you will always get an empty list of devices. The demo
824 devices are defined in the sandbox device tree, so the easiest
825 option is to use sandbox and pass the -d point to sandbox's
832 Enables the command "dfu" which is used to have U-Boot create a DFU
833 class device via USB. This command requires that the "dfu_alt_info"
834 environment variable be set and define the alt settings to expose to
838 bool "dm - Access to driver model information"
841 Provides access to driver model data structures and information,
842 such as a list of devices, list of uclasses and the state of each
843 device (e.g. activated). This is not required for operation, but
844 can be useful to see the state of driver model for debugging or
848 bool "fastboot - Android fastboot support"
851 This enables the command "fastboot" which enables the Android
852 fastboot mode for the platform. Fastboot is a protocol for
853 downloading images, flashing and device control used on
854 Android devices. Fastboot requires either the network stack
855 enabled or support for acting as a USB device.
857 See doc/android/fastboot.rst for more information.
860 bool "flinfo, erase, protect"
862 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
865 flinfo - print FLASH memory information
867 protect - enable or disable FLASH write protection
876 config CMD_FPGA_LOADBP
877 bool "fpga loadbp - load partial bitstream (Xilinx only)"
880 Supports loading an FPGA device from a bitstream buffer containing
883 config CMD_FPGA_LOADFS
884 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
887 Supports loading an FPGA device from a FAT filesystem.
889 config CMD_FPGA_LOADMK
890 bool "fpga loadmk - load bitstream from image"
893 Supports loading an FPGA device from a image generated by mkimage.
895 config CMD_FPGA_LOADP
896 bool "fpga loadp - load partial bitstream"
899 Supports loading an FPGA device from a bitstream buffer containing
902 config CMD_FPGA_LOAD_SECURE
903 bool "fpga loads - loads secure bitstreams (Xilinx only)"
906 Enables the fpga loads command which is used to load secure
907 (authenticated or encrypted or both) bitstreams on to FPGA.
910 bool "fpgad - dump FPGA registers"
912 (legacy, needs conversion to driver model)
913 Provides a way to dump FPGA registers by calling the board-specific
914 fpga_get_reg() function. This functions similarly to the 'md'
918 bool "fuse - support for the fuse subssystem"
920 (deprecated - needs conversion to driver model)
921 This allows reading, sensing, programming or overriding fuses
922 which control the behaviour of the device. The command uses the
931 bool "GPT (GUID Partition Table) command"
933 select HAVE_BLOCK_DEVICE
934 select PARTITION_UUIDS
937 Enable the 'gpt' command to ready and write GPT style partition
941 bool "GPT Random UUID generation"
944 Enable the generation of partitions with random UUIDs if none
947 config CMD_GPT_RENAME
948 bool "GPT partition renaming commands"
951 Enables the 'gpt' command to interchange names on two GPT
952 partitions via the 'gpt swap' command or to rename single
953 partitions via the 'rename' command.
956 bool "ide - Support for IDE drivers"
959 Provides an 'ide' command which allows accessing the IDE drive,
960 reseting the IDE interface, printing the partition table and
961 geting device info. It also enables the 'diskboot' command which
962 permits booting from an IDE drive.
965 bool "io - Support for performing I/O accesses"
967 Provides an 'iod' command to display I/O space and an 'iow' command
968 to write values to the I/O space. This can be useful for manually
969 checking the state of devices during boot when debugging device
973 bool "iotrace - Support for tracing I/O activity"
975 Provides an 'iotrace' command which supports recording I/O reads and
976 writes in a trace buffer in memory . It also maintains a checksum
977 of the trace records (even if space is exhausted) so that the
978 sequence of I/O accesses can be verified.
980 When debugging drivers it is useful to see what I/O accesses were
981 done and in what order.
983 Even if the individual accesses are of little interest it can be
984 useful to verify that the access pattern is consistent each time
985 an operation is performed. In this case a checksum can be used to
986 characterise the operation of a driver. The checksum can be compared
987 across different runs of the operation to verify that the driver is
990 In particular, when performing major refactoring of the driver, where
991 the access pattern should not change, the checksum provides assurance
992 that the refactoring work has not broken the driver.
994 This works by sneaking into the io.h heder for an architecture and
995 redirecting I/O accesses through iotrace's tracing mechanism.
997 For now no commands are provided to examine the trace buffer. The
998 format is fairly simple, so 'md' is a reasonable substitute.
1000 Note: The checksum feature is only useful for I/O regions where the
1001 contents do not change outside of software control. Where this is not
1002 suitable you can fall back to manually comparing the addresses. It
1003 might be useful to enhance tracing to only checksum the accesses and
1004 not the data read/written.
1014 bool "w1 - Support for Dallas 1-Wire protocol"
1016 Dallas 1-wire protocol support
1022 Load a binary file over serial line.
1028 Load an S-Record file over serial line
1032 bool "lsblk - list block drivers and devices"
1034 Print list of available block device drivers, and for each, the list
1035 of known block devices.
1041 Enable the command "misc" for accessing miscellaneous devices with
1042 a MISC uclass driver. The command provides listing all MISC devices
1043 as well as read and write functionalities via their drivers.
1048 MMC memory mapped support.
1052 config CMD_BKOPS_ENABLE
1053 bool "mmc bkops enable"
1057 Enable command for setting manual background operations handshake
1058 on a eMMC device. The feature is optionally available on eMMC devices
1059 conforming to standard >= 4.41.
1062 bool "Enable support for RPMB in the mmc command"
1063 depends on SUPPORT_EMMC_RPMB
1065 Enable the commands for reading, writing and programming the
1066 key for the Replay Protection Memory Block partition in eMMC.
1068 config CMD_MMC_SWRITE
1070 depends on MMC_WRITE
1073 Enable support for the "mmc swrite" command to write Android sparse
1082 Enable storage cloning over block devices, useful for
1083 initial flashing by external block device without network
1086 config CMD_OPTEE_RPMB
1087 bool "Enable read/write support on RPMB via OPTEE"
1088 depends on SUPPORT_EMMC_RPMB && OPTEE
1090 Enable the commands for reading, writing persistent named values
1091 in the Replay Protection Memory Block partition in eMMC by
1092 using Persistent Objects in OPTEE
1097 select MTD_PARTITIONS
1099 MTD commands support.
1103 depends on MULTIPLEXER
1105 List, select, and deselect mux controllers on the fly.
1109 default y if NAND_SUNXI
1110 depends on MTD_RAW_NAND
1115 config CMD_NAND_TRIMFFS
1116 bool "nand write.trimffs"
1117 default y if ARCH_SUNXI
1119 Allows one to skip empty pages when flashing something on a NAND.
1121 config CMD_NAND_LOCK_UNLOCK
1122 bool "nand lock/unlock"
1124 NAND locking support.
1126 config CMD_NAND_TORTURE
1129 NAND torture support.
1138 NVM Express device support
1141 bool "onenand - access to onenand device"
1144 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1145 various useful features. This command allows reading, writing,
1146 and erasing blocks. It allso provides a way to show and change
1147 bad blocks, and test the device.
1152 Enable the 'osd' command which allows to query information from and
1153 write text data to a on-screen display (OSD) device; a virtual device
1154 associated with a display capable of displaying a text overlay on the
1155 display it's associated with..
1159 select HAVE_BLOCK_DEVICE
1160 select PARTITION_UUIDS
1162 Read and display information about the partition table on
1166 bool "pci - Access PCI devices"
1168 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1169 used on some devices to allow the CPU to communicate with its
1170 peripherals. Sub-commands allow bus enumeration, displaying and
1171 changing configuration space and a few other features.
1174 bool "pinmux - show pins muxing"
1175 default y if PINCTRL
1177 Parse all available pin-controllers and show pins muxing. This
1178 is useful for debug purpoer to check the pin muxing and to know if
1179 a pin is configured as a GPIO or as an alternate function.
1184 Poweroff/Shutdown the system
1187 bool "read - Read binary data from a partition"
1189 Provides low-level access to the data in a partition.
1191 config CMD_REMOTEPROC
1193 depends on REMOTEPROC
1195 Support for Remote Processor control
1198 bool "sata - Access SATA subsystem"
1201 SATA (Serial Advanced Technology Attachment) is a serial bus
1202 standard for connecting to hard drives and other storage devices.
1203 This command provides information about attached devices and allows
1204 reading, writing and other operations.
1206 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1207 Attachment, where AT refers to an IBM AT (Advanced Technology)
1208 computer released in 1984.
1211 bool "saves - Save a file over serial in S-Record format"
1213 Provides a way to save a binary file using the Motorola S-Record
1214 format over the serial line.
1217 bool "scsi - Access to SCSI devices"
1220 This provides a 'scsi' command which provides access to SCSI (Small
1221 Computer System Interface) devices. The command provides a way to
1222 scan the bus, reset the bus, read and write data and get information
1226 bool "sdram - Print SDRAM configuration information"
1228 Provides information about attached SDRAM. This assumed that the
1229 SDRAM has an EEPROM with information that can be read using the
1230 I2C bus. This is only available on some boards.
1234 depends on DM_SPI_FLASH || SPI_FLASH
1235 default y if DM_SPI_FLASH
1240 bool "sf test - Allow testing of SPI flash"
1243 Provides a way to test that SPI flash is working correctly. The
1244 test is destructive, in that an area of SPI flash must be provided
1245 for the test to use. Performance information is also provided,
1246 measuring the performance of reading, writing and erasing in
1247 Mbps (Million Bits Per Second). This value should approximately
1248 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1249 everything is working properly.
1252 bool "sspi - Command to access spi device"
1255 SPI utility command.
1257 config DEFAULT_SPI_BUS
1258 int "default spi bus used by sspi command"
1262 config DEFAULT_SPI_MODE
1263 hex "default spi mode used by sspi command (see include/spi.h)"
1268 bool "tsi148 - Command to access tsi148 device"
1270 This provides various sub-commands to initialise and configure the
1271 Turndra tsi148 device. See the command help for full details.
1274 bool "Enable UFS - Universal Flash Subsystem commands"
1277 "This provides commands to initialise and configure universal flash
1281 bool "universe - Command to set up the Turndra Universe controller"
1283 This allows setting up the VMEbus provided by this controller.
1284 See the command help for full details.
1288 select HAVE_BLOCK_DEVICE
1294 select USB_FUNCTION_SDP
1296 Enables the command "sdp" which is used to have U-Boot emulating the
1297 Serial Download Protocol (SDP) via USB.
1301 depends on USB_FUNCTION_ROCKUSB
1303 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1304 read/write info, image to/from devices. This enable rockusb command
1305 support to communication with rockusb device. for more detail about
1306 this command, please read doc/README.rockusb.
1308 config CMD_USB_MASS_STORAGE
1309 bool "UMS usb mass storage"
1310 select USB_FUNCTION_MASS_STORAGE
1312 USB mass storage support
1315 bool "Xen para-virtualized block device"
1319 Xen para-virtualized block device support
1326 VirtIO block device support
1332 This provides commands to control the watchdog timer devices.
1338 Enable the command "axi" for accessing AXI (Advanced eXtensible
1339 Interface) busses, a on-chip interconnect specification for managing
1340 functional blocks in SoC designs, which is also often used in designs
1341 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1345 menu "Shell scripting commands"
1351 Echo args to console
1357 Return true/false on integer compare.
1363 Run script from memory
1369 Evaluate boolean and math expressions and store the result in an env
1371 Also supports loading the value at a memory location into a variable.
1372 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1376 menu "Android support commands"
1378 config CMD_AB_SELECT
1381 depends on ANDROID_AB
1383 On Android devices with more than one boot slot (multiple copies of
1384 the kernel and system images) this provides a command to select which
1385 slot should be used to boot from and register the boot attempt. This
1386 is used by the new A/B update model where one slot is updated in the
1387 background while running from the other slot.
1394 bool "Network commands"
1404 bootp - boot image via network using BOOTP/TFTP protocol
1408 depends on CMD_BOOTP
1410 Boot image via network using DHCP/TFTP protocol
1412 config BOOTP_BOOTPATH
1413 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1415 depends on CMD_BOOTP
1417 Even though the config is called BOOTP_BOOTPATH, it stores the
1418 path in the variable 'rootpath'.
1421 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1423 depends on CMD_BOOTP
1425 The primary DNS server is stored as 'dnsip'. If two servers are
1426 returned, you must set BOOTP_DNS2 to store that second server IP
1430 bool "Store 'dnsip2' from BOOTP/DHCP server"
1431 depends on BOOTP_DNS
1433 If a DHCP client requests the DNS server IP from a DHCP server,
1434 it is possible that more than one DNS serverip is offered to the
1435 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1436 server IP will be stored in the additional environment
1437 variable "dnsip2". The first DNS serverip is always
1438 stored in the variable "dnsip", when BOOTP_DNS is defined.
1440 config BOOTP_GATEWAY
1441 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1443 depends on CMD_BOOTP
1445 config BOOTP_HOSTNAME
1446 bool "Request & store 'hostname' from BOOTP/DHCP server"
1448 depends on CMD_BOOTP
1450 The name may or may not be qualified with the local domain name.
1452 config BOOTP_PREFER_SERVERIP
1453 bool "serverip variable takes precedent over DHCP server IP."
1454 depends on CMD_BOOTP
1456 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1458 With this option enabled, the 'serverip' variable in the environment
1459 takes precedence over DHCP server IP and will only be set by the DHCP
1460 server if not already set in the environment.
1462 config BOOTP_SUBNETMASK
1463 bool "Request & store 'netmask' from BOOTP/DHCP server"
1465 depends on CMD_BOOTP
1467 config BOOTP_NTPSERVER
1468 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1469 depends on CMD_BOOTP
1474 Selecting this will allow capturing all Ethernet packets and store
1475 them in physical memory in a PCAP formated file,
1476 later to be analyzed by PCAP reader application (IE. WireShark).
1479 bool "Send PXE client arch to BOOTP/DHCP server"
1481 depends on CMD_BOOTP && CMD_PXE
1483 Supported for ARM, ARM64, and x86 for now.
1485 config BOOTP_PXE_CLIENTARCH
1487 depends on BOOTP_PXE
1488 default 0x16 if ARM64
1492 config BOOTP_VCI_STRING
1494 depends on CMD_BOOTP
1495 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1496 default "U-Boot.armv8" if ARM64
1497 default "U-Boot.arm" if ARM
1504 tftpboot - boot image via network using TFTP protocol
1508 depends on CMD_TFTPBOOT
1510 TFTP put command, for uploading files to a server
1514 depends on CMD_TFTPBOOT
1516 Act as a TFTP server and boot the first received file
1518 config NET_TFTP_VARS
1519 bool "Control TFTP timeout and count through environment"
1520 depends on CMD_TFTPBOOT
1523 If set, allows controlling the TFTP timeout through the
1524 environment variable tftptimeout, and the TFTP maximum
1525 timeout count through the variable tftptimeoutcountmax.
1526 If unset, timeout and maximum are hard-defined as 1 second
1527 and 10 timouts per TFTP transfer.
1532 Boot image via network using RARP/TFTP protocol
1538 Boot image via network using NFS protocol.
1544 If set, allows 802.3(clause 22) MII Management functions interface access
1545 The management interface specified in Clause 22 provides
1546 a simple, two signal, serial interface to connect a
1547 Station Management entity and a managed PHY for providing access
1548 to management parameters and services.
1549 The interface is referred to as the MII management interface.
1555 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1556 The MDIO interface is orthogonal to the MII interface and extends
1557 it by adding access to more registers through indirect addressing.
1562 Send ICMP ECHO_REQUEST to network host
1567 Perform CDP network configuration
1573 Synchronize RTC via network
1578 Lookup the IP of a hostname
1580 config CMD_LINK_LOCAL
1584 Acquire a network IP address using the link-local protocol
1591 Allow control of L2 Ethernet switch commands. These are supported
1592 by the vsc9953 Ethernet driver at present. Sub-commands allow
1593 operations such as enabling / disabling a port and
1594 viewing/maintaining the filtering database (FDB)
1600 Boot image via network using PXE protocol
1605 Wait for wake-on-lan Magic Packet
1609 menu "Misc commands"
1612 bool "Enable 'bmp' command"
1613 depends on LCD || DM_VIDEO || VIDEO
1615 This provides a way to obtain information about a BMP-format image
1616 and to display it. BMP (which presumably stands for BitMaP) is a
1617 file format defined by Microsoft which supports images of various
1618 depths, formats and compression methods. Headers on the file
1619 determine the formats used. This command can be used by first loading
1620 the image into RAM, then using this command to look at it or display
1623 config CMD_BOOTCOUNT
1625 depends on BOOTCOUNT_LIMIT
1627 Enable the bootcount command, which allows interrogation and
1628 reset of the bootcounter.
1631 bool "Enable board-specific commands"
1633 (deprecated: instead, please define a Kconfig option for each command)
1635 Some boards have board-specific commands which are only enabled
1636 during developemnt and need to be turned off for production. This
1637 option provides a way to control this. The commands that are enabled
1638 vary depending on the board.
1640 config CMD_BLOCK_CACHE
1641 bool "blkcache - control and stats for block cache"
1642 depends on BLOCK_CACHE
1643 default y if BLOCK_CACHE
1645 Enable the blkcache command, which can be used to control the
1646 operation of the cache functions.
1647 This is most useful when fine-tuning the operation of the cache
1648 during development, but also allows the cache to be disabled when
1649 it might hurt performance (e.g. when using the ums command).
1656 Enable the 'button' command which allows to get the status of
1657 buttons supported by the board. The buttonss can be listed with
1658 'button list' and state can be known with 'button <label>'.
1659 Any button drivers can be controlled with this command, e.g.
1663 bool "icache or dcache"
1665 Enable the "icache" and "dcache" commands
1667 config CMD_CONITRACE
1668 bool "conitrace - trace console input codes"
1670 Enable the 'conitrace' command which displays the codes received
1671 from the console input as hexadecimal numbers.
1674 bool "Enable clear screen command 'cls'"
1675 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1678 Enable the 'cls' command which clears the screen contents
1679 on video frame buffer.
1682 bool "efidebug - display/configure UEFI environment"
1683 depends on EFI_LOADER
1684 select EFI_DEVICE_PATH_TO_TEXT
1687 Enable the 'efidebug' command which provides a subset of UEFI
1688 shell utility with simplified functionality. It will be useful
1689 particularly for managing boot parameters as well as examining
1690 various EFI status for debugging.
1692 config CMD_EXCEPTION
1693 bool "exception - raise exception"
1694 depends on ARM || RISCV || SANDBOX || X86
1696 Enable the 'exception' command which allows to raise an exception.
1703 Enable the 'led' command which allows for control of LEDs supported
1704 by the board. The LEDs can be listed with 'led list' and controlled
1705 with led on/off/togle/blink. Any LED drivers can be controlled with
1706 this command, e.g. led_gpio.
1713 Enable the 'date' command for getting/setting the time/date in RTC
1720 Enable the 'rtc' command for low-level access to RTC devices.
1725 Run commands and summarize execution time.
1728 bool "gettime - read elapsed time"
1730 Enable the 'gettime' command which reads the elapsed time since
1731 U-Boot started running. This shows the time in seconds and
1732 milliseconds. See also the 'bootstage' command which provides more
1733 flexibility for boot timing.
1740 Print bytes from the hardware random number generator.
1746 Delay execution for some time
1749 bool "support for multiprocessor"
1751 This provides an option to brinup
1752 different processors in multiprocessor
1758 Access the system timer.
1764 This provides basic access to the U-Boot's sound support. The main
1765 feature is to play a beep.
1767 sound init - set up sound system
1768 sound play - play a sound
1774 Boot image via local extlinux.conf file
1780 This provides access to the QEMU firmware interface. The main
1781 feature is to allow easy loading of files passed to qemu-system
1782 via -kernel / -initrd
1787 This provides access to Linux PStore with Rammoops backend. The main
1788 feature is to allow to display or save PStore records.
1790 See doc/pstore.rst for more information.
1794 config CMD_PSTORE_MEM_ADDR
1795 hex "Memory Address"
1796 depends on CMD_PSTORE
1798 Base addr used for PStore ramoops memory, should be identical to
1799 ramoops.mem_address parameter used by kernel
1801 config CMD_PSTORE_MEM_SIZE
1803 depends on CMD_PSTORE
1806 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1807 parameter used by kernel, a power of 2 and larger than the sum of the
1810 config CMD_PSTORE_RECORD_SIZE
1811 hex "Dump record size"
1812 depends on CMD_PSTORE
1815 Size of each dump done on oops/panic, should be identical to
1816 ramoops.record_size parameter used by kernel and a power of 2
1819 config CMD_PSTORE_CONSOLE_SIZE
1820 hex "Kernel console log size"
1821 depends on CMD_PSTORE
1824 Size of kernel console log, should be identical to
1825 ramoops.console_size parameter used by kernel and a power of 2
1828 config CMD_PSTORE_FTRACE_SIZE
1829 hex "FTrace log size"
1830 depends on CMD_PSTORE
1833 Size of ftrace log, should be identical to ramoops.ftrace_size
1834 parameter used by kernel and a power of 2
1836 config CMD_PSTORE_PMSG_SIZE
1837 hex "User space message log size"
1838 depends on CMD_PSTORE
1841 Size of user space message log, should be identical to
1842 ramoops.pmsg_size parameter used by kernel and a power of 2
1844 config CMD_PSTORE_ECC_SIZE
1846 depends on CMD_PSTORE
1849 if non-zero, the option enables ECC support and specifies ECC buffer
1850 size in bytes (1 is a special value, means 16 bytes ECC), should be
1851 identical to ramoops.ramoops_ecc parameter used by kernel
1855 source "cmd/mvebu/Kconfig"
1858 bool "terminal - provides a way to attach a serial terminal"
1860 Provides a 'cu'-like serial terminal command. This can be used to
1861 access other serial ports from the system console. The terminal
1862 is very simple with no special processing of characters. As with
1863 cu, you can press ~. (tilde followed by period) to exit.
1866 bool "uuid, guid - generation of unique IDs"
1869 This enables two commands:
1871 uuid - generate random Universally Unique Identifier
1872 guid - generate Globally Unique Identifier based on random UUID
1874 The two commands are very similar except for the endianness of the
1879 source "cmd/ti/Kconfig"
1881 config CMD_BOOTSTAGE
1882 bool "Enable the 'bootstage' command"
1883 depends on BOOTSTAGE
1885 Add a 'bootstage' command which supports printing a report
1886 and un/stashing of bootstage data.
1888 menu "Power commands"
1890 bool "Enable Driver Model PMIC command"
1893 This is the pmic command, based on a driver model pmic's API.
1894 Command features are unchanged:
1895 - list - list pmic devices
1896 - pmic dev <id> - show or [set] operating pmic device (NEW)
1897 - pmic dump - dump registers
1898 - pmic read address - read byte of register at address
1899 - pmic write address - write byte to register at address
1900 The only one change for this command is 'dev' subcommand.
1902 config CMD_REGULATOR
1903 bool "Enable Driver Model REGULATOR command"
1904 depends on DM_REGULATOR
1906 This command is based on driver model regulator's API.
1907 User interface features:
1908 - list - list regulator devices
1909 - regulator dev <id> - show or [set] operating regulator device
1910 - regulator info - print constraints info
1911 - regulator status - print operating status
1912 - regulator value <val] <-f> - print/[set] voltage value [uV]
1913 - regulator current <val> - print/[set] current value [uA]
1914 - regulator mode <id> - print/[set] operating mode id
1915 - regulator enable - enable the regulator output
1916 - regulator disable - disable the regulator output
1918 The '-f' (force) option can be used for set the value which exceeds
1919 the limits, which are found in device-tree and are kept in regulator's
1920 uclass plat structure.
1924 menu "Security commands"
1926 bool "Enable the 'aes' command"
1929 This provides a means to encrypt and decrypt data using the AES
1930 (Advanced Encryption Standard). This algorithm uses a symetric key
1931 and is widely used as a streaming cipher. Different key lengths are
1932 supported by the algorithm but this command only supports 128 bits
1936 bool "Enable the 'blob' command"
1938 This is used with the Freescale secure boot mechanism.
1940 Freescale's SEC block has built-in Blob Protocol which provides
1941 a method for protecting user-defined data across system power
1942 cycles. SEC block protects data in a data structure called a Blob,
1943 which provides both confidentiality and integrity protection.
1945 Encapsulating data as a blob
1946 Each time that the Blob Protocol is used to protect data, a
1947 different randomly generated key is used to encrypt the data.
1948 This random key is itself encrypted using a key which is derived
1949 from SoC's non-volatile secret key and a 16 bit Key identifier.
1950 The resulting encrypted key along with encrypted data is called a
1951 blob. The non-volatile secure key is available for use only during
1954 During decapsulation, the reverse process is performed to get back
1958 blob enc - encapsulating data as a cryptgraphic blob
1959 blob dec - decapsulating cryptgraphic blob to get the data
1963 blob enc src dst len km
1965 Encapsulate and create blob of data $len bytes long
1966 at address $src and store the result at address $dst.
1967 $km is the 16 byte key modifier is also required for
1968 generation/use as key for cryptographic operation. Key
1969 modifier should be 16 byte long.
1971 blob dec src dst len km
1973 Decapsulate the blob of data at address $src and
1974 store result of $len byte at addr $dst.
1975 $km is the 16 byte key modifier is also required for
1976 generation/use as key for cryptographic operation. Key
1977 modifier should be 16 byte long.
1980 bool "Support 'hash' command"
1983 This provides a way to hash data in memory using various supported
1984 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1985 saved to memory or to an environment variable. It is also possible
1986 to verify a hash against data in memory.
1989 bool "Support the 'hvc' command"
1990 depends on ARM_SMCCC
1992 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1993 development and testing.
1996 bool "Support the 'smc' command"
1997 depends on ARM_SMCCC
1999 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2000 development and testing.
2006 Add -v option to verify data against a hash.
2016 bool "Enable the 'tpm' command"
2017 depends on TPM_V1 || TPM_V2
2018 select CMD_TPM_V1 if TPM_V1
2019 select CMD_TPM_V2 if TPM_V2
2021 This provides a means to talk to a TPM from the command line. A wide
2022 range of commands if provided - see 'tpm help' for details. The
2023 command requires a suitable TPM on your board and the correct driver
2029 bool "Enable the 'tpm test' command"
2032 This provides a a series of tests to confirm that the TPMv1.x is
2033 working correctly. The tests cover initialisation, non-volatile RAM,
2034 extend, global lock and checking that timing is within expectations.
2035 The tests pass correctly on Infineon TPMs but may need to be adjusted
2042 menu "Firmware commands"
2044 bool "Enable crosec command"
2048 Enable command-line access to the Chrome OS EC (Embedded
2049 Controller). This provides the 'crosec' command which has
2050 a number of sub-commands for performing EC tasks such as
2051 updating its flash, accessing a small saved context area
2052 and talking to the I2C bus behind the EC (if there is one).
2055 menu "Filesystem commands"
2057 bool "Enable the 'btrsubvol' command"
2060 This enables the 'btrsubvol' command to list subvolumes
2061 of a BTRFS filesystem. There are no special commands for
2062 listing BTRFS directories or loading BTRFS files - this
2063 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2064 when BTRFS is enabled (see FS_BTRFS).
2067 bool "Enable the 'cbfs' command"
2070 Define this to enable support for reading from a Coreboot
2071 filesystem. This is a ROM-based filesystem used for accessing files
2072 on systems that use coreboot as the first boot-loader and then load
2073 U-Boot to actually boot the Operating System. Available commands are
2074 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2077 bool "Enable the 'cramfs' command"
2078 depends on FS_CRAMFS
2080 This provides commands for dealing with CRAMFS (Compressed ROM
2081 filesystem). CRAMFS is useful when space is tight since files are
2082 compressed. Two commands are provided:
2084 cramfsls - lists files in a cramfs image
2085 cramfsload - loads a file from a cramfs image
2088 bool "ext2 command support"
2091 Enables EXT2 FS command
2094 bool "ext4 command support"
2097 Enables EXT4 FS command
2099 config CMD_EXT4_WRITE
2101 bool "ext4 write command support"
2104 Enables EXT4 FS write command
2107 bool "FAT command support"
2110 Support for the FAT fs
2113 bool "SquashFS command support"
2116 Enables SquashFS filesystem commands (e.g. load, ls).
2118 config CMD_FS_GENERIC
2119 bool "filesystem commands"
2121 Enables filesystem commands (e.g. load, ls) that work for multiple
2125 bool "fsuuid command"
2127 Enables fsuuid command for filesystem UUID.
2130 bool "jffs2 command"
2133 Enables commands to support the JFFS2 (Journalling Flash File System
2134 version 2) filesystem. This enables fsload, ls and fsinfo which
2135 provide the ability to load files, list directories and obtain
2136 filesystem information.
2139 bool "MTD partition support"
2142 MTD partitioning tool support.
2143 It is strongly encouraged to avoid using this command
2144 anymore along with 'sf', 'nand', 'onenand'. One can still
2145 declare the partitions in the mtdparts environment variable
2146 but better use the MTD stack and the 'mtd' command instead.
2148 config CMD_MTDPARTS_SPREAD
2149 bool "Padd partition size to take account of bad blocks"
2150 depends on CMD_MTDPARTS
2152 This enables the 'spread' sub-command of the mtdparts command.
2153 This command will modify the existing mtdparts variable by increasing
2154 the size of the partitions such that 1) each partition's net size is
2155 at least as large as the size specified in the mtdparts variable and
2156 2) each partition starts on a good block.
2158 config CMD_MTDPARTS_SHOW_NET_SIZES
2159 bool "Show net size (w/o bad blocks) of partitions"
2160 depends on CMD_MTDPARTS
2162 Adds two columns to the printed partition table showing the
2163 effective usable size of a partition, if bad blocks are taken
2166 config MTDIDS_DEFAULT
2167 string "Default MTD IDs"
2168 depends on MTD || SPI_FLASH
2170 Defines a default MTD IDs list for use with MTD partitions in the
2171 Linux MTD command line partitions format.
2173 config MTDPARTS_DEFAULT
2174 string "Default MTD partition scheme"
2175 depends on MTD || SPI_FLASH
2177 Defines a default MTD partitioning scheme in the Linux MTD command
2178 line partitions format
2181 bool "reiser - Access to reiserfs filesystems"
2183 This provides two commands which operate on a resierfs filesystem,
2184 commonly used some years ago:
2186 reiserls - list files
2187 reiserload - load a file
2190 bool "yaffs2 - Access of YAFFS2 filesystem"
2194 This provides commands for accessing a YAFFS2 filesystem. Yet
2195 Another Flash Filesystem 2 is a filesystem designed specifically
2196 for NAND flash. It incorporates bad-block management and ensures
2197 that device writes are sequential regardless of filesystem
2201 bool "zfs - Access of ZFS filesystem"
2203 This provides commands to accessing a ZFS filesystem, commonly used
2204 on Solaris systems. Two sub-commands are provided:
2206 zfsls - list files in a directory
2207 zfsload - load a file
2209 See doc/README.zfs for more details.
2213 menu "Debug commands"
2218 The bedbug (emBEDded deBUGger) command provides debugging features
2219 for some PowerPC processors. For details please see the
2220 documentation in doc/README.bedbug.
2223 bool "diag - Board diagnostics"
2225 This command provides access to board diagnostic tests. These are
2226 called Power-on Self Tests (POST). The command allows listing of
2227 available tests and running either all the tests, or specific tests
2231 bool "irq - Show information about interrupts"
2232 depends on !ARM && !MIPS && !RISCV && !SH
2234 This enables two commands:
2236 interrupts - enable or disable interrupts
2237 irqinfo - print device-specific interrupt information
2240 bool "kgdb - Allow debugging of U-Boot with gdb"
2243 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2244 over a serial link for debugging purposes. This allows
2245 single-stepping, inspecting variables, etc. This is supported only
2246 on PowerPC at present.
2249 bool "log - Generation, control and access to logging"
2253 This provides access to logging features. It allows the output of
2254 log data to be controlled to a limited extent (setting up the default
2255 maximum log level for emitting of records). It also provides access
2256 to a command used for testing the log system.
2259 bool "trace - Support tracing of function calls and timing"
2261 Enables a command to control using of function tracing within
2262 U-Boot. This allows recording of call traces including timing
2263 information. The command can write data to memory for exporting
2264 for analysis (e.g. using bootchart). See doc/README.trace for full
2268 bool "avb - Android Verified Boot 2.0 operations"
2269 depends on AVB_VERIFY
2272 Enables a "avb" command to perform verification of partitions using
2273 Android Verified Boot 2.0 functionality. It includes such subcommands:
2274 avb init - initialize avb2 subsystem
2275 avb read_rb - read rollback index
2276 avb write_rb - write rollback index
2277 avb is_unlocked - check device lock state
2278 avb get_uuid - read and print uuid of a partition
2279 avb read_part - read data from partition
2280 avb read_part_hex - read data from partition and output to stdout
2281 avb write_part - write data to partition
2282 avb verify - run full verification chain
2286 tristate "Enable UBI - Unsorted block images commands"
2289 UBI is a software layer above MTD layer which admits use of LVM-like
2290 logical volumes on top of MTD devices, hides some complexities of
2291 flash chips like wear and bad blocks and provides some other useful
2292 capabilities. Please, consult the MTD web site for more details
2293 (www.linux-mtd.infradead.org). Activate this option if you want
2294 to use U-Boot UBI commands.
2295 It is also strongly encouraged to also enable CONFIG_MTD to get full
2298 config CMD_UBI_RENAME
2299 bool "Enable rename"
2303 Enable a "ubi" command to rename ubi volume:
2304 ubi rename <oldname> <newname>
2307 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2309 default y if CMD_UBI
2312 UBIFS is a file system for flash devices which works on top of UBI.
git.openpandora.org / pandora-u-boot.git / blob