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
90 List and dump ACPI tables. ACPI (Advanced Configuration and Power
91 Interface) is used mostly on x86 for providing information to the
92 Operating System about devices in the system. The tables are set up
93 by the firmware, typically U-Boot but possibly an earlier firmware
94 module, if U-Boot is chain-loaded from something else. ACPI tables
95 can also include code, to perform hardware-specific tasks required
96 by the Operating Systems. This allows some amount of separation
97 between the firmware and OS, and is particularly useful when you
98 want to make hardware changes without the OS needing to be adjusted.
111 Print ".config" contents.
113 If this option is enabled, the ".config" file contents are embedded
114 in the U-Boot image and can be printed on the console by the "config"
115 command. This provides information of which options are enabled on
122 Print console devices and information.
128 Print information about available CPUs. This normally shows the
129 number of CPUs, type (e.g. manufacturer, architecture, product or
130 internal name) and clock frequency. Other information may be
131 available depending on the CPU driver.
137 Print GPL license text
142 Provides access to the Intel Power-Management Controller (PMC) so
143 that its state can be examined. This does not currently support
144 changing the state but it is still useful for debugging and seeing
153 config CMD_TLV_EEPROM
155 depends on I2C_EEPROM
157 Display and program the system EEPROM data block in ONIE Tlvinfo
158 format. TLV stands for Type-Length-Value.
160 config SPL_CMD_TLV_EEPROM
161 bool "tlv_eeprom for SPL"
162 depends on SPL_I2C_EEPROM
163 select SPL_DRIVERS_MISC_SUPPORT
165 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
169 depends on RISCV_SMODE && SBI_V02
171 Display information about the SBI implementation.
181 Run the command stored in the environment "bootcmd", i.e.
182 "bootd" does the same thing as "run bootcmd".
188 Boot an application image from the memory.
191 bool "Support booting UEFI FIT images"
192 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
195 Support booting UEFI FIT images via the bootm command.
200 Boot the Linux zImage
204 depends on ARM64 || RISCV
207 Boot an AArch64 Linux Kernel image from memory.
210 bool "Support booting Linux OS images"
211 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
214 Support booting the Linux kernel directly via a command such as bootm
218 bool "Support booting NetBSD (non-EFI) loader images"
222 Support booting NetBSD via the bootm command.
224 config BOOTM_OPENRTOS
225 bool "Support booting OPENRTOS / FreeRTOS images"
228 Support booting OPENRTOS / FreeRTOS via the bootm command.
231 bool "Support booting Enea OSE images"
232 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
235 Support booting Enea OSE images via the bootm command.
238 bool "Support booting Plan9 OS images"
242 Support booting Plan9 images via the bootm command.
245 bool "Support booting RTEMS OS images"
249 Support booting RTEMS images via the bootm command.
252 bool "Support booting VxWorks OS images"
256 Support booting VxWorks images via the bootm command.
260 depends on EFI_LOADER
263 Boot an EFI image from memory.
265 config CMD_BOOTEFI_HELLO_COMPILE
266 bool "Compile a standard EFI hello world binary for testing"
267 depends on CMD_BOOTEFI && !CPU_V7M
270 This compiles a standard EFI hello world application with U-Boot so
271 that it can be used with the test/py testing framework. This is useful
272 for testing that EFI is working at a basic level, and for bringing
273 up EFI support on a new architecture.
275 No additional space will be required in the resulting U-Boot binary
276 when this option is enabled.
278 config CMD_BOOTEFI_HELLO
279 bool "Allow booting a standard EFI hello world for testing"
280 depends on CMD_BOOTEFI_HELLO_COMPILE
281 default y if CMD_BOOTEFI_SELFTEST
283 This adds a standard EFI hello world application to U-Boot so that
284 it can be used with the 'bootefi hello' command. This is useful
285 for testing that EFI is working at a basic level, and for bringing
286 up EFI support on a new architecture.
288 source lib/efi_selftest/Kconfig
294 Add an ANSI terminal boot menu command.
299 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
300 image into RAM, dump image structure information, etc. Those dtb/dtbo
301 files should be merged in one dtb further, which needs to be passed to
302 the kernel, as part of a boot process.
306 depends on ANDROID_BOOT_IMAGE
308 Android Boot Image manipulation commands. Allows one to extract
309 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
310 obtain corresponding meta-information from boot.img.
312 See doc/android/boot-image.rst for details.
315 bool "bootelf, bootvx"
319 Boot an ELF/vxWorks image from the memory.
322 bool "Flattened Device Tree utility commands"
326 Do FDT related setup before booting into the Operating System.
332 Start an application at a given address.
338 Run the command in the given environment variable.
344 Print header information for application image.
349 List all images found in flash
355 Extract a part of a multi-image.
358 bool "spl export - Export boot information for Falcon boot"
361 Falcon mode allows booting directly from SPL into an Operating
362 System such as Linux, thus skipping U-Boot proper. See
363 doc/README.falcon for full information about how to use this
366 config CMD_SPL_NAND_OFS
367 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
368 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
371 This provides the offset of the command line arguments for Linux
372 when booting from NAND in Falcon mode. See doc/README.falcon
373 for full information about how to use this option (and also see
374 board/gateworks/gw_ventana/README for an example).
376 config CMD_SPL_NOR_OFS
377 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
378 depends on CMD_SPL && SPL_NOR_SUPPORT
381 This provides the offset of the command line arguments or dtb for
382 Linux when booting from NOR in Falcon mode.
384 config CMD_SPL_WRITE_SIZE
385 hex "Size of argument area"
389 This provides the size of the command-line argument area in NAND
390 flash used by Falcon-mode boot. See the documentation until CMD_SPL
393 config CMD_THOR_DOWNLOAD
394 bool "thor - TIZEN 'thor' download"
397 Implements the 'thor' download protocol. This is a way of
398 downloading a software update over USB from an attached host.
399 There is no documentation about this within the U-Boot source code
400 but you should be able to find something on the interwebs.
403 bool "zboot - x86 boot command"
405 With x86 machines it is common to boot a bzImage file which
406 contains both a kernel and a setup.bin file. The latter includes
407 configuration information from the dark ages which x86 boards still
408 need to pick things out of.
410 Consider using FIT in preference to this since it supports directly
411 booting both 32- and 64-bit kernels, as well as secure boot.
412 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
416 menu "Environment commands"
419 bool "ask for env variable"
421 Ask for environment variable
439 Edit environment variable.
444 Allow for searching environment variables
450 Save all environment variables into the compiled-in persistent
456 depends on CMD_SAVEENV
458 Erase environment variables from the compiled-in persistent
461 config CMD_ENV_EXISTS
465 Check if a variable is defined in the environment for use in
468 config CMD_ENV_CALLBACK
469 bool "env callbacks - print callbacks and their associated variables"
471 Some environment variable have callbacks defined by
472 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
473 For example changing "baudrate" adjust the serial baud rate. This
474 command lists the currently defined callbacks.
477 bool "env flags -print variables that have non-default flags"
479 Some environment variables have special flags that control their
480 behaviour. For example, serial# can only be written once and cannot
481 be deleted. This command shows the variables that have special
484 config CMD_NVEDIT_EFI
485 bool "env [set|print] -e - set/print UEFI variables"
486 depends on EFI_LOADER
489 UEFI variables are encoded as some form of U-Boot variables.
490 If enabled, we are allowed to set/print UEFI variables using
491 "env" command with "-e" option without knowing details.
493 config CMD_NVEDIT_INFO
494 bool "env info - print or evaluate environment information"
496 Print environment information:
497 - env_valid : is environment valid
498 - env_ready : is environment imported into hash table
499 - env_use_default : is default environment used
501 This command can be optionally used for evaluation in scripts:
502 [-d] : evaluate whether default environment is used
503 [-p] : evaluate whether environment can be persisted
505 The result of multiple evaluations will be combined with AND.
507 config CMD_NVEDIT_LOAD
510 Load all environment variables from the compiled-in persistent
513 config CMD_NVEDIT_SELECT
516 Select the compiled-in persistent storage of environment variables.
520 menu "Memory commands"
525 Compute binary operations (xor, or, and) of byte arrays of arbitrary
526 size from memory and store the result in memory or the environment.
530 default y if BLOBLIST
532 Show information about the bloblist, a collection of binary blobs
533 held in memory that persist between SPL and U-Boot. In the case of
534 x86 devices the bloblist can be used to hold ACPI tables so that they
535 remain available in memory.
548 Add -v option to verify data against a crc32 checksum.
551 bool "eeprom - EEPROM subsystem"
553 (deprecated, needs conversion to driver model)
554 Provides commands to read and write EEPROM (Electrically Erasable
555 Programmable Read Only Memory) chips that are connected over an
558 config CMD_EEPROM_LAYOUT
559 bool "Enable layout-aware eeprom commands"
560 depends on CMD_EEPROM
562 (deprecated, needs conversion to driver model)
563 When enabled, additional eeprom sub-commands become available.
565 eeprom print - prints the contents of the eeprom in a human-readable
566 way (eeprom layout fields, and data formatted to be fit for human
569 eeprom update - allows user to update eeprom fields by specifying
570 the field name, and providing the new data in a human readable format
571 (same format as displayed by the eeprom print command).
573 Both commands can either auto detect the layout, or be told which
577 __weak int parse_layout_version(char *str)
578 - override to provide your own layout name parsing
579 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
581 - override to setup the layout metadata based on the version
582 __weak int eeprom_layout_detect(unsigned char *data)
583 - override to provide your own algorithm for detecting layout
586 - contains various printing and updating functions for common
587 types of eeprom fields. Can be used for defining
590 config EEPROM_LAYOUT_HELP_STRING
591 string "Tells user what layout names are supported"
592 depends on CMD_EEPROM_LAYOUT
593 default "<not defined>"
595 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
601 Infinite write loop on address range
608 Compute MD5 checksum.
613 depends on CMD_MD5SUM
615 Add -v option to verify data against an MD5 checksum.
620 Display memory information.
623 bool "md, mm, nm, mw, cp, cmp, base, loop"
628 mm - memory modify (auto-incrementing address)
629 nm - memory modify (constant address)
630 mw - memory write (fill)
633 base - print or set address offset
634 loop - initialize loop on address range
636 config CMD_MEM_SEARCH
637 bool "ms - Memory search"
639 Memory-search command
641 This allows searching through a region of memory looking for hex
642 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
643 support it). It is also possible to search for a string. The
644 command accepts a memory range and a list of values to search for.
645 The values need to appear in memory in the same order they are given
646 in the command. At most 10 matches can be returned at a time, but
647 pressing return will show the next 10 matches. Environment variables
648 are set for use with scripting (memmatches, memaddr, mempos).
651 bool "Enable cyclic md/mw commands"
652 depends on CMD_MEMORY
654 Add the "mdc" and "mwc" memory commands. These are cyclic
659 This command will print 4 bytes (10,11,12,13) each 500 ms.
661 => mwc.l 100 12345678 10
662 This command will write 12345678 to address 100 all 10 ms.
667 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
669 random - fill memory with random data
674 Simple RAM read/write test.
678 config SYS_ALT_MEMTEST
679 bool "Alternative test"
681 Use a more complete alternative memory test.
685 config SYS_ALT_MEMTEST_BITFLIP
689 The alternative memory test includes bitflip test since 2020.07.
690 The bitflip test significantly increases the overall test time.
691 Bitflip test can optionally be disabled here.
695 config SYS_MEMTEST_START
696 hex "default start address for mtest"
699 This is the default start address for mtest for simple read/write
700 test. If no arguments are given to mtest, default address is used
703 config SYS_MEMTEST_END
704 hex "default end address for mtest"
707 This is the default end address for mtest for simple read/write
708 test. If no arguments are given to mtest, default address is used
717 Compute SHA1 checksum.
719 config SHA1SUM_VERIFY
721 depends on CMD_SHA1SUM
723 Add -v option to verify data against a SHA1 checksum.
726 bool "strings - display strings in memory"
728 This works similarly to the Unix 'strings' command except that it
729 works with a memory range. String of printable characters found
730 within the range are displayed. The minimum number of characters
731 for a sequence to be considered a string can be provided.
735 menu "Compression commands"
739 default y if CMD_BOOTI
742 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
747 default y if CMD_BOOTI
750 Support decompressing an LZ4 image from memory region.
754 default y if CMD_BOOTI
757 Uncompress a zip-compressed memory region.
761 select GZIP_COMPRESSED
763 Compress a memory region with zlib deflate method.
767 menu "Device access commands"
770 #depends on FLASH_CFI_DRIVER
773 ARM Ltd reference designs flash partition access
776 bool "adc - Access Analog to Digital Converters info and data"
778 depends on DM_REGULATOR
780 Shows ADC device info and permit printing one-shot analog converted
781 data from a named Analog to Digital Converter.
786 depends on PARTITIONS
788 Read/modify/write the fields of Bootloader Control Block, usually
789 stored on the flash "misc" partition with its structure defined in:
790 https://android.googlesource.com/platform/bootable/recovery/+/master/
791 bootloader_message/include/bootloader_message/bootloader_message.h
793 Some real-life use-cases include (but are not limited to):
794 - Determine the "boot reason" (and act accordingly):
795 https://source.android.com/devices/bootloader/boot-reason
796 - Get/pass a list of commands from/to recovery:
797 https://android.googlesource.com/platform/bootable/recovery
798 - Inspect/dump the contents of the BCB fields
801 bool "bind/unbind - Bind or unbind a device to/from a driver"
804 Bind or unbind a device to/from a driver from the command line.
805 This is useful in situations where a device may be handled by several
806 drivers. For example, this can be used to bind a UDC to the usb ether
807 gadget driver from the command line.
810 bool "clk - Show clock frequencies"
813 Shows clock frequences by calling a sock_clk_dump() hook function.
814 This is depreated in favour of using the CLK uclass and accessing
815 clock values from associated drivers. However currently no command
819 bool "demo - Demonstration commands for driver model"
822 Provides a 'demo' command which can be used to play around with
823 driver model. To use this properly you will need to enable one or
824 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
825 Otherwise you will always get an empty list of devices. The demo
826 devices are defined in the sandbox device tree, so the easiest
827 option is to use sandbox and pass the -d point to sandbox's
834 Enables the command "dfu" which is used to have U-Boot create a DFU
835 class device via USB. This command requires that the "dfu_alt_info"
836 environment variable be set and define the alt settings to expose to
840 bool "dm - Access to driver model information"
843 Provides access to driver model data structures and information,
844 such as a list of devices, list of uclasses and the state of each
845 device (e.g. activated). This is not required for operation, but
846 can be useful to see the state of driver model for debugging or
850 bool "fastboot - Android fastboot support"
853 This enables the command "fastboot" which enables the Android
854 fastboot mode for the platform. Fastboot is a protocol for
855 downloading images, flashing and device control used on
856 Android devices. Fastboot requires either the network stack
857 enabled or support for acting as a USB device.
859 See doc/android/fastboot.rst for more information.
862 bool "flinfo, erase, protect"
864 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
867 flinfo - print FLASH memory information
869 protect - enable or disable FLASH write protection
878 config CMD_FPGA_LOADBP
879 bool "fpga loadbp - load partial bitstream (Xilinx only)"
882 Supports loading an FPGA device from a bitstream buffer containing
885 config CMD_FPGA_LOADFS
886 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
889 Supports loading an FPGA device from a FAT filesystem.
891 config CMD_FPGA_LOADMK
892 bool "fpga loadmk - load bitstream from image"
895 Supports loading an FPGA device from a image generated by mkimage.
897 config CMD_FPGA_LOADP
898 bool "fpga loadp - load partial bitstream"
901 Supports loading an FPGA device from a bitstream buffer containing
904 config CMD_FPGA_LOAD_SECURE
905 bool "fpga loads - loads secure bitstreams (Xilinx only)"
908 Enables the fpga loads command which is used to load secure
909 (authenticated or encrypted or both) bitstreams on to FPGA.
912 bool "fpgad - dump FPGA registers"
914 (legacy, needs conversion to driver model)
915 Provides a way to dump FPGA registers by calling the board-specific
916 fpga_get_reg() function. This functions similarly to the 'md'
920 bool "fuse - support for the fuse subssystem"
922 (deprecated - needs conversion to driver model)
923 This allows reading, sensing, programming or overriding fuses
924 which control the behaviour of the device. The command uses the
936 Control PWM channels, this allows invert/config/enable/disable PWM channels.
939 bool "GPT (GUID Partition Table) command"
941 select HAVE_BLOCK_DEVICE
942 select PARTITION_UUIDS
945 Enable the 'gpt' command to ready and write GPT style partition
949 bool "GPT Random UUID generation"
952 Enable the generation of partitions with random UUIDs if none
955 config CMD_GPT_RENAME
956 bool "GPT partition renaming commands"
959 Enables the 'gpt' command to interchange names on two GPT
960 partitions via the 'gpt swap' command or to rename single
961 partitions via the 'rename' command.
964 bool "ide - Support for IDE drivers"
967 Provides an 'ide' command which allows accessing the IDE drive,
968 reseting the IDE interface, printing the partition table and
969 geting device info. It also enables the 'diskboot' command which
970 permits booting from an IDE drive.
973 bool "io - Support for performing I/O accesses"
975 Provides an 'iod' command to display I/O space and an 'iow' command
976 to write values to the I/O space. This can be useful for manually
977 checking the state of devices during boot when debugging device
981 bool "iotrace - Support for tracing I/O activity"
983 Provides an 'iotrace' command which supports recording I/O reads and
984 writes in a trace buffer in memory . It also maintains a checksum
985 of the trace records (even if space is exhausted) so that the
986 sequence of I/O accesses can be verified.
988 When debugging drivers it is useful to see what I/O accesses were
989 done and in what order.
991 Even if the individual accesses are of little interest it can be
992 useful to verify that the access pattern is consistent each time
993 an operation is performed. In this case a checksum can be used to
994 characterise the operation of a driver. The checksum can be compared
995 across different runs of the operation to verify that the driver is
998 In particular, when performing major refactoring of the driver, where
999 the access pattern should not change, the checksum provides assurance
1000 that the refactoring work has not broken the driver.
1002 This works by sneaking into the io.h heder for an architecture and
1003 redirecting I/O accesses through iotrace's tracing mechanism.
1005 For now no commands are provided to examine the trace buffer. The
1006 format is fairly simple, so 'md' is a reasonable substitute.
1008 Note: The checksum feature is only useful for I/O regions where the
1009 contents do not change outside of software control. Where this is not
1010 suitable you can fall back to manually comparing the addresses. It
1011 might be useful to enhance tracing to only checksum the accesses and
1012 not the data read/written.
1022 bool "w1 - Support for Dallas 1-Wire protocol"
1024 Dallas 1-wire protocol support
1030 Load a binary file over serial line.
1036 Load an S-Record file over serial line
1040 bool "lsblk - list block drivers and devices"
1042 Print list of available block device drivers, and for each, the list
1043 of known block devices.
1046 bool "MBR (Master Boot Record) command"
1047 select DOS_PARTITION
1048 select HAVE_BLOCK_DEVICE
1050 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1051 style partition tables.
1057 Enable the command "misc" for accessing miscellaneous devices with
1058 a MISC uclass driver. The command provides listing all MISC devices
1059 as well as read and write functionalities via their drivers.
1064 MMC memory mapped support.
1068 config CMD_BKOPS_ENABLE
1069 bool "mmc bkops enable"
1073 Enable command for setting manual background operations handshake
1074 on a eMMC device. The feature is optionally available on eMMC devices
1075 conforming to standard >= 4.41.
1078 bool "Enable support for RPMB in the mmc command"
1079 depends on SUPPORT_EMMC_RPMB
1081 Enable the commands for reading, writing and programming the
1082 key for the Replay Protection Memory Block partition in eMMC.
1084 config CMD_MMC_SWRITE
1086 depends on MMC_WRITE
1089 Enable support for the "mmc swrite" command to write Android sparse
1098 Enable storage cloning over block devices, useful for
1099 initial flashing by external block device without network
1102 config CMD_OPTEE_RPMB
1103 bool "Enable read/write support on RPMB via OPTEE"
1104 depends on SUPPORT_EMMC_RPMB && OPTEE
1106 Enable the commands for reading, writing persistent named values
1107 in the Replay Protection Memory Block partition in eMMC by
1108 using Persistent Objects in OPTEE
1113 select MTD_PARTITIONS
1115 MTD commands support.
1119 depends on MULTIPLEXER
1121 List, select, and deselect mux controllers on the fly.
1125 default y if NAND_SUNXI
1126 depends on MTD_RAW_NAND
1131 config CMD_NAND_TRIMFFS
1132 bool "nand write.trimffs"
1133 default y if ARCH_SUNXI
1135 Allows one to skip empty pages when flashing something on a NAND.
1137 config CMD_NAND_LOCK_UNLOCK
1138 bool "nand lock/unlock"
1140 NAND locking support.
1142 config CMD_NAND_TORTURE
1145 NAND torture support.
1154 NVM Express device support
1157 bool "onenand - access to onenand device"
1160 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1161 various useful features. This command allows reading, writing,
1162 and erasing blocks. It allso provides a way to show and change
1163 bad blocks, and test the device.
1168 Enable the 'osd' command which allows to query information from and
1169 write text data to a on-screen display (OSD) device; a virtual device
1170 associated with a display capable of displaying a text overlay on the
1171 display it's associated with..
1175 select HAVE_BLOCK_DEVICE
1176 select PARTITION_UUIDS
1178 Read and display information about the partition table on
1182 bool "pci - Access PCI devices"
1184 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1185 used on some devices to allow the CPU to communicate with its
1186 peripherals. Sub-commands allow bus enumeration, displaying and
1187 changing configuration space and a few other features.
1190 bool "pinmux - show pins muxing"
1192 default y if PINCTRL
1194 Parse all available pin-controllers and show pins muxing. This
1195 is useful for debug purpoer to check the pin muxing and to know if
1196 a pin is configured as a GPIO or as an alternate function.
1201 Poweroff/Shutdown the system
1204 bool "read - Read binary data from a partition"
1206 Provides low-level access to the data in a partition.
1208 config CMD_REMOTEPROC
1210 depends on REMOTEPROC
1212 Support for Remote Processor control
1215 bool "sata - Access SATA subsystem"
1218 SATA (Serial Advanced Technology Attachment) is a serial bus
1219 standard for connecting to hard drives and other storage devices.
1220 This command provides information about attached devices and allows
1221 reading, writing and other operations.
1223 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1224 Attachment, where AT refers to an IBM AT (Advanced Technology)
1225 computer released in 1984.
1228 bool "saves - Save a file over serial in S-Record format"
1230 Provides a way to save a binary file using the Motorola S-Record
1231 format over the serial line.
1234 bool "scsi - Access to SCSI devices"
1237 This provides a 'scsi' command which provides access to SCSI (Small
1238 Computer System Interface) devices. The command provides a way to
1239 scan the bus, reset the bus, read and write data and get information
1243 bool "sdram - Print SDRAM configuration information"
1245 Provides information about attached SDRAM. This assumed that the
1246 SDRAM has an EEPROM with information that can be read using the
1247 I2C bus. This is only available on some boards.
1251 depends on DM_SPI_FLASH || SPI_FLASH
1252 default y if DM_SPI_FLASH
1257 bool "sf test - Allow testing of SPI flash"
1260 Provides a way to test that SPI flash is working correctly. The
1261 test is destructive, in that an area of SPI flash must be provided
1262 for the test to use. Performance information is also provided,
1263 measuring the performance of reading, writing and erasing in
1264 Mbps (Million Bits Per Second). This value should approximately
1265 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1266 everything is working properly.
1269 bool "sspi - Command to access spi device"
1272 SPI utility command.
1274 config DEFAULT_SPI_BUS
1275 int "default spi bus used by sspi command"
1279 config DEFAULT_SPI_MODE
1280 hex "default spi mode used by sspi command (see include/spi.h)"
1285 bool "tsi148 - Command to access tsi148 device"
1287 This provides various sub-commands to initialise and configure the
1288 Turndra tsi148 device. See the command help for full details.
1291 bool "Enable UFS - Universal Flash Subsystem commands"
1294 "This provides commands to initialise and configure universal flash
1298 bool "universe - Command to set up the Turndra Universe controller"
1300 This allows setting up the VMEbus provided by this controller.
1301 See the command help for full details.
1305 select HAVE_BLOCK_DEVICE
1311 select USB_FUNCTION_SDP
1313 Enables the command "sdp" which is used to have U-Boot emulating the
1314 Serial Download Protocol (SDP) via USB.
1318 depends on USB_FUNCTION_ROCKUSB
1320 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1321 read/write info, image to/from devices. This enable rockusb command
1322 support to communication with rockusb device. for more detail about
1323 this command, please read doc/README.rockusb.
1325 config CMD_USB_MASS_STORAGE
1326 bool "UMS usb mass storage"
1327 select USB_FUNCTION_MASS_STORAGE
1329 USB mass storage support
1332 bool "Xen para-virtualized block device"
1336 Xen para-virtualized block device support
1343 VirtIO block device support
1349 This provides commands to control the watchdog timer devices.
1355 Enable the command "axi" for accessing AXI (Advanced eXtensible
1356 Interface) busses, a on-chip interconnect specification for managing
1357 functional blocks in SoC designs, which is also often used in designs
1358 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1362 menu "Shell scripting commands"
1368 Echo args to console
1374 Return true/false on integer compare.
1380 Run script from memory
1386 Evaluate boolean and math expressions and store the result in an env
1388 Also supports loading the value at a memory location into a variable.
1389 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1393 menu "Android support commands"
1395 config CMD_AB_SELECT
1398 depends on ANDROID_AB
1400 On Android devices with more than one boot slot (multiple copies of
1401 the kernel and system images) this provides a command to select which
1402 slot should be used to boot from and register the boot attempt. This
1403 is used by the new A/B update model where one slot is updated in the
1404 background while running from the other slot.
1411 bool "Network commands"
1421 bootp - boot image via network using BOOTP/TFTP protocol
1425 depends on CMD_BOOTP
1427 Boot image via network using DHCP/TFTP protocol
1429 config BOOTP_BOOTPATH
1430 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1432 depends on CMD_BOOTP
1434 Even though the config is called BOOTP_BOOTPATH, it stores the
1435 path in the variable 'rootpath'.
1438 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1440 depends on CMD_BOOTP
1442 The primary DNS server is stored as 'dnsip'. If two servers are
1443 returned, you must set BOOTP_DNS2 to store that second server IP
1447 bool "Store 'dnsip2' from BOOTP/DHCP server"
1448 depends on BOOTP_DNS
1450 If a DHCP client requests the DNS server IP from a DHCP server,
1451 it is possible that more than one DNS serverip is offered to the
1452 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1453 server IP will be stored in the additional environment
1454 variable "dnsip2". The first DNS serverip is always
1455 stored in the variable "dnsip", when BOOTP_DNS is defined.
1457 config BOOTP_GATEWAY
1458 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1460 depends on CMD_BOOTP
1462 config BOOTP_HOSTNAME
1463 bool "Request & store 'hostname' from BOOTP/DHCP server"
1465 depends on CMD_BOOTP
1467 The name may or may not be qualified with the local domain name.
1469 config BOOTP_PREFER_SERVERIP
1470 bool "serverip variable takes precedent over DHCP server IP."
1471 depends on CMD_BOOTP
1473 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1475 With this option enabled, the 'serverip' variable in the environment
1476 takes precedence over DHCP server IP and will only be set by the DHCP
1477 server if not already set in the environment.
1479 config BOOTP_SUBNETMASK
1480 bool "Request & store 'netmask' from BOOTP/DHCP server"
1482 depends on CMD_BOOTP
1484 config BOOTP_NTPSERVER
1485 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1486 depends on CMD_BOOTP
1491 Selecting this will allow capturing all Ethernet packets and store
1492 them in physical memory in a PCAP formated file,
1493 later to be analyzed by PCAP reader application (IE. WireShark).
1496 bool "Send PXE client arch to BOOTP/DHCP server"
1498 depends on CMD_BOOTP && CMD_PXE
1500 Supported for ARM, ARM64, and x86 for now.
1502 config BOOTP_PXE_CLIENTARCH
1504 depends on BOOTP_PXE
1505 default 0x16 if ARM64
1509 config BOOTP_VCI_STRING
1511 depends on CMD_BOOTP
1512 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1513 default "U-Boot.armv8" if ARM64
1514 default "U-Boot.arm" if ARM
1521 tftpboot - boot image via network using TFTP protocol
1525 depends on CMD_TFTPBOOT
1527 TFTP put command, for uploading files to a server
1531 depends on CMD_TFTPBOOT
1533 Act as a TFTP server and boot the first received file
1535 config NET_TFTP_VARS
1536 bool "Control TFTP timeout and count through environment"
1537 depends on CMD_TFTPBOOT
1540 If set, allows controlling the TFTP timeout through the
1541 environment variable tftptimeout, and the TFTP maximum
1542 timeout count through the variable tftptimeoutcountmax.
1543 If unset, timeout and maximum are hard-defined as 1 second
1544 and 10 timouts per TFTP transfer.
1549 Boot image via network using RARP/TFTP protocol
1555 Boot image via network using NFS protocol.
1561 If set, allows 802.3(clause 22) MII Management functions interface access
1562 The management interface specified in Clause 22 provides
1563 a simple, two signal, serial interface to connect a
1564 Station Management entity and a managed PHY for providing access
1565 to management parameters and services.
1566 The interface is referred to as the MII management interface.
1572 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1573 The MDIO interface is orthogonal to the MII interface and extends
1574 it by adding access to more registers through indirect addressing.
1579 Send ICMP ECHO_REQUEST to network host
1584 Perform CDP network configuration
1590 Synchronize RTC via network
1595 Lookup the IP of a hostname
1597 config CMD_LINK_LOCAL
1601 Acquire a network IP address using the link-local protocol
1608 Allow control of L2 Ethernet switch commands. These are supported
1609 by the vsc9953 Ethernet driver at present. Sub-commands allow
1610 operations such as enabling / disabling a port and
1611 viewing/maintaining the filtering database (FDB)
1617 Boot image via network using PXE protocol
1622 Wait for wake-on-lan Magic Packet
1626 menu "Misc commands"
1629 bool "Enable 'bmp' command"
1630 depends on LCD || DM_VIDEO || VIDEO
1632 This provides a way to obtain information about a BMP-format image
1633 and to display it. BMP (which presumably stands for BitMaP) is a
1634 file format defined by Microsoft which supports images of various
1635 depths, formats and compression methods. Headers on the file
1636 determine the formats used. This command can be used by first loading
1637 the image into RAM, then using this command to look at it or display
1640 config CMD_BOOTCOUNT
1642 depends on BOOTCOUNT_LIMIT
1644 Enable the bootcount command, which allows interrogation and
1645 reset of the bootcounter.
1648 bool "Enable board-specific commands"
1650 (deprecated: instead, please define a Kconfig option for each command)
1652 Some boards have board-specific commands which are only enabled
1653 during developemnt and need to be turned off for production. This
1654 option provides a way to control this. The commands that are enabled
1655 vary depending on the board.
1657 config CMD_BLOCK_CACHE
1658 bool "blkcache - control and stats for block cache"
1659 depends on BLOCK_CACHE
1660 default y if BLOCK_CACHE
1662 Enable the blkcache command, which can be used to control the
1663 operation of the cache functions.
1664 This is most useful when fine-tuning the operation of the cache
1665 during development, but also allows the cache to be disabled when
1666 it might hurt performance (e.g. when using the ums command).
1673 Enable the 'button' command which allows to get the status of
1674 buttons supported by the board. The buttonss can be listed with
1675 'button list' and state can be known with 'button <label>'.
1676 Any button drivers can be controlled with this command, e.g.
1680 bool "icache or dcache"
1682 Enable the "icache" and "dcache" commands
1684 config CMD_CONITRACE
1685 bool "conitrace - trace console input codes"
1687 Enable the 'conitrace' command which displays the codes received
1688 from the console input as hexadecimal numbers.
1691 bool "Enable clear screen command 'cls'"
1692 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1695 Enable the 'cls' command which clears the screen contents
1696 on video frame buffer.
1699 bool "efidebug - display/configure UEFI environment"
1700 depends on EFI_LOADER
1701 select EFI_DEVICE_PATH_TO_TEXT
1704 Enable the 'efidebug' command which provides a subset of UEFI
1705 shell utility with simplified functionality. It will be useful
1706 particularly for managing boot parameters as well as examining
1707 various EFI status for debugging.
1709 config CMD_EXCEPTION
1710 bool "exception - raise exception"
1711 depends on ARM || RISCV || SANDBOX || X86
1713 Enable the 'exception' command which allows to raise an exception.
1720 Enable the 'led' command which allows for control of LEDs supported
1721 by the board. The LEDs can be listed with 'led list' and controlled
1722 with led on/off/togle/blink. Any LED drivers can be controlled with
1723 this command, e.g. led_gpio.
1730 Enable the 'date' command for getting/setting the time/date in RTC
1737 Enable the 'rtc' command for low-level access to RTC devices.
1742 Run commands and summarize execution time.
1745 bool "gettime - read elapsed time"
1747 Enable the 'gettime' command which reads the elapsed time since
1748 U-Boot started running. This shows the time in seconds and
1749 milliseconds. See also the 'bootstage' command which provides more
1750 flexibility for boot timing.
1757 Print bytes from the hardware random number generator.
1763 Delay execution for some time
1766 bool "support for multiprocessor"
1768 This provides an option to brinup
1769 different processors in multiprocessor
1775 Access the system timer.
1781 This provides basic access to the U-Boot's sound support. The main
1782 feature is to play a beep.
1784 sound init - set up sound system
1785 sound play - play a sound
1791 Boot image via local extlinux.conf file
1797 This provides access to the QEMU firmware interface. The main
1798 feature is to allow easy loading of files passed to qemu-system
1799 via -kernel / -initrd
1804 This provides access to Linux PStore with Rammoops backend. The main
1805 feature is to allow to display or save PStore records.
1807 See doc/pstore.rst for more information.
1811 config CMD_PSTORE_MEM_ADDR
1812 hex "Memory Address"
1813 depends on CMD_PSTORE
1815 Base addr used for PStore ramoops memory, should be identical to
1816 ramoops.mem_address parameter used by kernel
1818 config CMD_PSTORE_MEM_SIZE
1820 depends on CMD_PSTORE
1823 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1824 parameter used by kernel, a power of 2 and larger than the sum of the
1827 config CMD_PSTORE_RECORD_SIZE
1828 hex "Dump record size"
1829 depends on CMD_PSTORE
1832 Size of each dump done on oops/panic, should be identical to
1833 ramoops.record_size parameter used by kernel and a power of 2
1836 config CMD_PSTORE_CONSOLE_SIZE
1837 hex "Kernel console log size"
1838 depends on CMD_PSTORE
1841 Size of kernel console log, should be identical to
1842 ramoops.console_size parameter used by kernel and a power of 2
1845 config CMD_PSTORE_FTRACE_SIZE
1846 hex "FTrace log size"
1847 depends on CMD_PSTORE
1850 Size of ftrace log, should be identical to ramoops.ftrace_size
1851 parameter used by kernel and a power of 2
1853 config CMD_PSTORE_PMSG_SIZE
1854 hex "User space message log size"
1855 depends on CMD_PSTORE
1858 Size of user space message log, should be identical to
1859 ramoops.pmsg_size parameter used by kernel and a power of 2
1861 config CMD_PSTORE_ECC_SIZE
1863 depends on CMD_PSTORE
1866 if non-zero, the option enables ECC support and specifies ECC buffer
1867 size in bytes (1 is a special value, means 16 bytes ECC), should be
1868 identical to ramoops.ramoops_ecc parameter used by kernel
1872 source "cmd/mvebu/Kconfig"
1875 bool "terminal - provides a way to attach a serial terminal"
1877 Provides a 'cu'-like serial terminal command. This can be used to
1878 access other serial ports from the system console. The terminal
1879 is very simple with no special processing of characters. As with
1880 cu, you can press ~. (tilde followed by period) to exit.
1883 bool "uuid, guid - generation of unique IDs"
1886 This enables two commands:
1888 uuid - generate random Universally Unique Identifier
1889 guid - generate Globally Unique Identifier based on random UUID
1891 The two commands are very similar except for the endianness of the
1896 source "cmd/ti/Kconfig"
1898 config CMD_BOOTSTAGE
1899 bool "Enable the 'bootstage' command"
1900 depends on BOOTSTAGE
1902 Add a 'bootstage' command which supports printing a report
1903 and un/stashing of bootstage data.
1905 menu "Power commands"
1907 bool "Enable Driver Model PMIC command"
1910 This is the pmic command, based on a driver model pmic's API.
1911 Command features are unchanged:
1912 - list - list pmic devices
1913 - pmic dev <id> - show or [set] operating pmic device (NEW)
1914 - pmic dump - dump registers
1915 - pmic read address - read byte of register at address
1916 - pmic write address - write byte to register at address
1917 The only one change for this command is 'dev' subcommand.
1919 config CMD_REGULATOR
1920 bool "Enable Driver Model REGULATOR command"
1921 depends on DM_REGULATOR
1923 This command is based on driver model regulator's API.
1924 User interface features:
1925 - list - list regulator devices
1926 - regulator dev <id> - show or [set] operating regulator device
1927 - regulator info - print constraints info
1928 - regulator status - print operating status
1929 - regulator value <val] <-f> - print/[set] voltage value [uV]
1930 - regulator current <val> - print/[set] current value [uA]
1931 - regulator mode <id> - print/[set] operating mode id
1932 - regulator enable - enable the regulator output
1933 - regulator disable - disable the regulator output
1935 The '-f' (force) option can be used for set the value which exceeds
1936 the limits, which are found in device-tree and are kept in regulator's
1937 uclass plat structure.
1941 menu "Security commands"
1943 bool "Enable the 'aes' command"
1946 This provides a means to encrypt and decrypt data using the AES
1947 (Advanced Encryption Standard). This algorithm uses a symetric key
1948 and is widely used as a streaming cipher. Different key lengths are
1949 supported by the algorithm but this command only supports 128 bits
1953 bool "Enable the 'blob' command"
1955 This is used with the Freescale secure boot mechanism.
1957 Freescale's SEC block has built-in Blob Protocol which provides
1958 a method for protecting user-defined data across system power
1959 cycles. SEC block protects data in a data structure called a Blob,
1960 which provides both confidentiality and integrity protection.
1962 Encapsulating data as a blob
1963 Each time that the Blob Protocol is used to protect data, a
1964 different randomly generated key is used to encrypt the data.
1965 This random key is itself encrypted using a key which is derived
1966 from SoC's non-volatile secret key and a 16 bit Key identifier.
1967 The resulting encrypted key along with encrypted data is called a
1968 blob. The non-volatile secure key is available for use only during
1971 During decapsulation, the reverse process is performed to get back
1975 blob enc - encapsulating data as a cryptgraphic blob
1976 blob dec - decapsulating cryptgraphic blob to get the data
1980 blob enc src dst len km
1982 Encapsulate and create blob of data $len bytes long
1983 at address $src and store the result at address $dst.
1984 $km is the 16 byte key modifier is also required for
1985 generation/use as key for cryptographic operation. Key
1986 modifier should be 16 byte long.
1988 blob dec src dst len km
1990 Decapsulate the blob of data at address $src and
1991 store result of $len byte at addr $dst.
1992 $km is the 16 byte key modifier is also required for
1993 generation/use as key for cryptographic operation. Key
1994 modifier should be 16 byte long.
1997 bool "Support 'hash' command"
2000 This provides a way to hash data in memory using various supported
2001 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2002 saved to memory or to an environment variable. It is also possible
2003 to verify a hash against data in memory.
2006 bool "Support the 'hvc' command"
2007 depends on ARM_SMCCC
2009 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2010 development and testing.
2013 bool "Support the 'smc' command"
2014 depends on ARM_SMCCC
2016 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2017 development and testing.
2023 Add -v option to verify data against a hash.
2032 bool "Enable the 'tpm' command"
2033 depends on TPM_V1 || TPM_V2
2034 select CMD_TPM_V1 if TPM_V1
2035 select CMD_TPM_V2 if TPM_V2
2037 This provides a means to talk to a TPM from the command line. A wide
2038 range of commands if provided - see 'tpm help' for details. The
2039 command requires a suitable TPM on your board and the correct driver
2045 bool "Enable the 'tpm test' command"
2048 This provides a a series of tests to confirm that the TPMv1.x is
2049 working correctly. The tests cover initialisation, non-volatile RAM,
2050 extend, global lock and checking that timing is within expectations.
2051 The tests pass correctly on Infineon TPMs but may need to be adjusted
2058 menu "Firmware commands"
2060 bool "Enable crosec command"
2064 Enable command-line access to the Chrome OS EC (Embedded
2065 Controller). This provides the 'crosec' command which has
2066 a number of sub-commands for performing EC tasks such as
2067 updating its flash, accessing a small saved context area
2068 and talking to the I2C bus behind the EC (if there is one).
2071 menu "Filesystem commands"
2073 bool "Enable the 'btrsubvol' command"
2076 This enables the 'btrsubvol' command to list subvolumes
2077 of a BTRFS filesystem. There are no special commands for
2078 listing BTRFS directories or loading BTRFS files - this
2079 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2080 when BTRFS is enabled (see FS_BTRFS).
2083 bool "Enable the 'cbfs' command"
2086 Define this to enable support for reading from a Coreboot
2087 filesystem. This is a ROM-based filesystem used for accessing files
2088 on systems that use coreboot as the first boot-loader and then load
2089 U-Boot to actually boot the Operating System. Available commands are
2090 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2093 bool "Enable the 'cramfs' command"
2094 depends on FS_CRAMFS
2096 This provides commands for dealing with CRAMFS (Compressed ROM
2097 filesystem). CRAMFS is useful when space is tight since files are
2098 compressed. Two commands are provided:
2100 cramfsls - lists files in a cramfs image
2101 cramfsload - loads a file from a cramfs image
2104 bool "ext2 command support"
2107 Enables EXT2 FS command
2110 bool "ext4 command support"
2113 Enables EXT4 FS command
2115 config CMD_EXT4_WRITE
2117 bool "ext4 write command support"
2120 Enables EXT4 FS write command
2123 bool "FAT command support"
2126 Support for the FAT fs
2129 bool "SquashFS command support"
2132 Enables SquashFS filesystem commands (e.g. load, ls).
2134 config CMD_FS_GENERIC
2135 bool "filesystem commands"
2137 Enables filesystem commands (e.g. load, ls) that work for multiple
2141 bool "fsuuid command"
2143 Enables fsuuid command for filesystem UUID.
2146 bool "jffs2 command"
2149 Enables commands to support the JFFS2 (Journalling Flash File System
2150 version 2) filesystem. This enables fsload, ls and fsinfo which
2151 provide the ability to load files, list directories and obtain
2152 filesystem information.
2155 bool "MTD partition support"
2158 MTD partitioning tool support.
2159 It is strongly encouraged to avoid using this command
2160 anymore along with 'sf', 'nand', 'onenand'. One can still
2161 declare the partitions in the mtdparts environment variable
2162 but better use the MTD stack and the 'mtd' command instead.
2164 config CMD_MTDPARTS_SPREAD
2165 bool "Padd partition size to take account of bad blocks"
2166 depends on CMD_MTDPARTS
2168 This enables the 'spread' sub-command of the mtdparts command.
2169 This command will modify the existing mtdparts variable by increasing
2170 the size of the partitions such that 1) each partition's net size is
2171 at least as large as the size specified in the mtdparts variable and
2172 2) each partition starts on a good block.
2174 config CMD_MTDPARTS_SHOW_NET_SIZES
2175 bool "Show net size (w/o bad blocks) of partitions"
2176 depends on CMD_MTDPARTS
2178 Adds two columns to the printed partition table showing the
2179 effective usable size of a partition, if bad blocks are taken
2182 config MTDIDS_DEFAULT
2183 string "Default MTD IDs"
2184 depends on MTD || SPI_FLASH
2186 Defines a default MTD IDs list for use with MTD partitions in the
2187 Linux MTD command line partitions format.
2189 config MTDPARTS_DEFAULT
2190 string "Default MTD partition scheme"
2191 depends on MTD || SPI_FLASH
2193 Defines a default MTD partitioning scheme in the Linux MTD command
2194 line partitions format
2197 bool "reiser - Access to reiserfs filesystems"
2199 This provides two commands which operate on a resierfs filesystem,
2200 commonly used some years ago:
2202 reiserls - list files
2203 reiserload - load a file
2206 bool "yaffs2 - Access of YAFFS2 filesystem"
2210 This provides commands for accessing a YAFFS2 filesystem. Yet
2211 Another Flash Filesystem 2 is a filesystem designed specifically
2212 for NAND flash. It incorporates bad-block management and ensures
2213 that device writes are sequential regardless of filesystem
2217 bool "zfs - Access of ZFS filesystem"
2219 This provides commands to accessing a ZFS filesystem, commonly used
2220 on Solaris systems. Two sub-commands are provided:
2222 zfsls - list files in a directory
2223 zfsload - load a file
2225 See doc/README.zfs for more details.
2229 menu "Debug commands"
2234 The bedbug (emBEDded deBUGger) command provides debugging features
2235 for some PowerPC processors. For details please see the
2236 documentation in doc/README.bedbug.
2239 bool "diag - Board diagnostics"
2241 This command provides access to board diagnostic tests. These are
2242 called Power-on Self Tests (POST). The command allows listing of
2243 available tests and running either all the tests, or specific tests
2247 bool "irq - Show information about interrupts"
2248 depends on !ARM && !MIPS && !RISCV && !SH
2250 This enables two commands:
2252 interrupts - enable or disable interrupts
2253 irqinfo - print device-specific interrupt information
2256 bool "kgdb - Allow debugging of U-Boot with gdb"
2259 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2260 over a serial link for debugging purposes. This allows
2261 single-stepping, inspecting variables, etc. This is supported only
2262 on PowerPC at present.
2265 bool "log - Generation, control and access to logging"
2269 This provides access to logging features. It allows the output of
2270 log data to be controlled to a limited extent (setting up the default
2271 maximum log level for emitting of records). It also provides access
2272 to a command used for testing the log system.
2275 bool "trace - Support tracing of function calls and timing"
2277 Enables a command to control using of function tracing within
2278 U-Boot. This allows recording of call traces including timing
2279 information. The command can write data to memory for exporting
2280 for analysis (e.g. using bootchart). See doc/README.trace for full
2284 bool "avb - Android Verified Boot 2.0 operations"
2285 depends on AVB_VERIFY
2288 Enables a "avb" command to perform verification of partitions using
2289 Android Verified Boot 2.0 functionality. It includes such subcommands:
2290 avb init - initialize avb2 subsystem
2291 avb read_rb - read rollback index
2292 avb write_rb - write rollback index
2293 avb is_unlocked - check device lock state
2294 avb get_uuid - read and print uuid of a partition
2295 avb read_part - read data from partition
2296 avb read_part_hex - read data from partition and output to stdout
2297 avb write_part - write data to partition
2298 avb verify - run full verification chain
2302 tristate "Enable UBI - Unsorted block images commands"
2305 UBI is a software layer above MTD layer which admits use of LVM-like
2306 logical volumes on top of MTD devices, hides some complexities of
2307 flash chips like wear and bad blocks and provides some other useful
2308 capabilities. Please, consult the MTD web site for more details
2309 (www.linux-mtd.infradead.org). Activate this option if you want
2310 to use U-Boot UBI commands.
2311 It is also strongly encouraged to also enable CONFIG_MTD to get full
2314 config CMD_UBI_RENAME
2315 bool "Enable rename"
2319 Enable a "ubi" command to rename ubi volume:
2320 ubi rename <oldname> <newname>
2323 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2325 default y if CMD_UBI
2328 UBIFS is a file system for flash devices which works on top of UBI.
projects / J-u-boot.git / blob