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.
53 This string is displayed in the command line to the left of the
56 menu "Autoboot options"
62 This enables the autoboot. See doc/README.autoboot for detail.
65 bool "Stop autobooting via specific input key / string"
68 This option enables stopping (aborting) of the automatic
69 boot feature only by issuing a specific input key or
70 string. If not enabled, any input key will abort the
71 U-Boot automatic booting process and bring the device
72 to the U-Boot prompt for user input.
74 config AUTOBOOT_PROMPT
75 string "Autoboot stop prompt"
76 depends on AUTOBOOT_KEYED
77 default "Autoboot in %d seconds\\n"
79 This string is displayed before the boot delay selected by
80 CONFIG_BOOTDELAY starts. If it is not defined there is no
81 output indicating that autoboot is in progress.
83 Note that this define is used as the (only) argument to a
84 printf() call, so it may contain '%' format specifications,
85 provided that it also includes, sepearated by commas exactly
86 like in a printf statement, the required arguments. It is
87 the responsibility of the user to select only such arguments
88 that are valid in the given context.
90 config AUTOBOOT_ENCRYPTION
91 bool "Enable encryption in autoboot stopping"
92 depends on AUTOBOOT_KEYED
95 config AUTOBOOT_DELAY_STR
96 string "Delay autobooting via specific input key / string"
97 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
99 This option delays the automatic boot feature by issuing
100 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
101 or the environment variable "bootdelaykey" is specified
102 and this string is received from console input before
103 autoboot starts booting, U-Boot gives a command prompt. The
104 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
105 used, otherwise it never times out.
107 config AUTOBOOT_STOP_STR
108 string "Stop autobooting via specific input key / string"
109 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
111 This option enables stopping (aborting) of the automatic
112 boot feature only by issuing a specific input key or
113 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
114 variable "bootstopkey" is specified and this string is
115 received from console input before autoboot starts booting,
116 U-Boot gives a command prompt. The U-Boot prompt never
117 times out, even if CONFIG_BOOT_RETRY_TIME is used.
119 config AUTOBOOT_KEYED_CTRLC
120 bool "Enable Ctrl-C autoboot interruption"
121 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
124 This option allows for the boot sequence to be interrupted
125 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
126 Setting this variable provides an escape sequence from the
127 limited "password" strings.
129 config AUTOBOOT_STOP_STR_SHA256
130 string "Stop autobooting via SHA256 encrypted password"
131 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
133 This option adds the feature to only stop the autobooting,
134 and therefore boot into the U-Boot prompt, when the input
135 string / password matches a values that is encypted via
136 a SHA256 hash and saved in the environment.
158 Print ".config" contents.
160 If this option is enabled, the ".config" file contents are embedded
161 in the U-Boot image and can be printed on the console by the "config"
162 command. This provides information of which options are enabled on
169 Print console devices and information.
174 Print information about available CPUs. This normally shows the
175 number of CPUs, type (e.g. manufacturer, architecture, product or
176 internal name) and clock frequency. Other information may be
177 available depending on the CPU driver.
183 Print GPL license text
199 Run the command stored in the environment "bootcmd", i.e.
200 "bootd" does the same thing as "run bootcmd".
206 Boot an application image from the memory.
211 Boot the Linux zImage
218 Boot an AArch64 Linux Kernel image from memory.
222 depends on EFI_LOADER
225 Boot an EFI image from memory.
227 config CMD_BOOTEFI_HELLO_COMPILE
228 bool "Compile a standard EFI hello world binary for testing"
229 depends on CMD_BOOTEFI && (ARM || X86 || RISCV)
232 This compiles a standard EFI hello world application with U-Boot so
233 that it can be used with the test/py testing framework. This is useful
234 for testing that EFI is working at a basic level, and for bringing
235 up EFI support on a new architecture.
237 No additional space will be required in the resulting U-Boot binary
238 when this option is enabled.
240 config CMD_BOOTEFI_HELLO
241 bool "Allow booting a standard EFI hello world for testing"
242 depends on CMD_BOOTEFI_HELLO_COMPILE
244 This adds a standard EFI hello world application to U-Boot so that
245 it can be used with the 'bootefi hello' command. This is useful
246 for testing that EFI is working at a basic level, and for bringing
247 up EFI support on a new architecture.
249 source lib/efi_selftest/Kconfig
255 Add an ANSI terminal boot menu command.
258 bool "bootelf, bootvx"
261 Boot an ELF/vxWorks image from the memory.
264 bool "Flattened Device Tree utility commands"
268 Do FDT related setup before booting into the Operating System.
274 Start an application at a given address.
280 Run the command in the given environment variable.
286 Print header information for application image.
291 List all images found in flash
297 Extract a part of a multi-image.
302 Poweroff/Shutdown the system
305 bool "spl export - Export boot information for Falcon boot"
308 Falcon mode allows booting directly from SPL into an Operating
309 System such as Linux, thus skipping U-Boot proper. See
310 doc/README.falcon for full information about how to use this
313 config CMD_SPL_NAND_OFS
314 hex "Offset of OS command line args for Falcon-mode NAND boot"
318 This provides the offset of the command line arguments for Linux
319 when booting from NAND in Falcon mode. See doc/README.falcon
320 for full information about how to use this option (and also see
321 board/gateworks/gw_ventana/README for an example).
323 config CMD_SPL_WRITE_SIZE
324 hex "Size of argument area"
328 This provides the size of the command-line argument area in NAND
329 flash used by Falcon-mode boot. See the documentation until CMD_SPL
333 bool "fitImage update command"
335 Implements the 'fitupd' command, which allows to automatically
336 store software updates present on a TFTP server in NOR Flash
338 config CMD_THOR_DOWNLOAD
339 bool "thor - TIZEN 'thor' download"
341 Implements the 'thor' download protocol. This is a way of
342 downloading a software update over USB from an attached host.
343 There is no documentation about this within the U-Boot source code
344 but you should be able to find something on the interwebs.
347 bool "zboot - x86 boot command"
349 With x86 machines it is common to boot a bzImage file which
350 contains both a kernel and a setup.bin file. The latter includes
351 configuration information from the dark ages which x86 boards still
352 need to pick things out of.
354 Consider using FIT in preference to this since it supports directly
355 booting both 32- and 64-bit kernels, as well as secure boot.
356 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
360 menu "Environment commands"
363 bool "ask for env variable"
365 Ask for environment variable
383 Edit environment variable.
388 Allow for searching environment variables
394 Save all environment variables into the compiled-in persistent
397 config CMD_ENV_EXISTS
401 Check if a variable is defined in the environment for use in
404 config CMD_ENV_CALLBACK
405 bool "env callbacks - print callbacks and their associated variables"
407 Some environment variable have callbacks defined by
408 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
409 For example changing "baudrate" adjust the serial baud rate. This
410 command lists the currently defined callbacks.
413 bool "env flags -print variables that have non-default flags"
415 Some environment variables have special flags that control their
416 behaviour. For example, serial# can only be written once and cannot
417 be deleted. This command shows the variables that have special
422 menu "Memory commands"
427 Compute binary operations (xor, or, and) of byte arrays of arbitrary
428 size from memory and store the result in memory or the environment.
441 Add -v option to verify data against a crc32 checksum.
444 bool "eeprom - EEPROM subsystem"
446 (deprecated, needs conversion to driver model)
447 Provides commands to read and write EEPROM (Electrically Erasable
448 Programmable Read Only Memory) chips that are connected over an
451 config CMD_EEPROM_LAYOUT
452 bool "Enable layout-aware eeprom commands"
453 depends on CMD_EEPROM
455 (deprecated, needs conversion to driver model)
456 When enabled, additional eeprom sub-commands become available.
458 eeprom print - prints the contents of the eeprom in a human-readable
459 way (eeprom layout fields, and data formatted to be fit for human
462 eeprom update - allows user to update eeprom fields by specifying
463 the field name, and providing the new data in a human readable format
464 (same format as displayed by the eeprom print command).
466 Both commands can either auto detect the layout, or be told which
470 __weak int parse_layout_version(char *str)
471 - override to provide your own layout name parsing
472 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
474 - override to setup the layout metadata based on the version
475 __weak int eeprom_layout_detect(unsigned char *data)
476 - override to provide your own algorithm for detecting layout
479 - contains various printing and updating functions for common
480 types of eeprom fields. Can be used for defining
483 config EEPROM_LAYOUT_HELP_STRING
484 string "Tells user what layout names are supported"
485 depends on CMD_EEPROM_LAYOUT
486 default "<not defined>"
488 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
494 Infinite write loop on address range
501 Compute MD5 checksum.
506 depends on CMD_MD5SUM
508 Add -v option to verify data against an MD5 checksum.
513 Display memory information.
516 bool "md, mm, nm, mw, cp, cmp, base, loop"
521 mm - memory modify (auto-incrementing address)
522 nm - memory modify (constant address)
523 mw - memory write (fill)
526 base - print or set address offset
527 loop - initialize loop on address range
532 Simple RAM read/write test.
536 config SYS_ALT_MEMTEST
537 bool "Alternative test"
539 Use a more complete alternative memory test.
546 mdc - memory display cyclic
547 mwc - memory write cyclic
553 Compute SHA1 checksum.
555 config SHA1SUM_VERIFY
557 depends on CMD_SHA1SUM
559 Add -v option to verify data against a SHA1 checksum.
562 bool "strings - display strings in memory"
564 This works similarly to the Unix 'strings' command except that it
565 works with a memory range. String of printable characters found
566 within the range are displayed. The minimum number of characters
567 for a sequence to be considered a string can be provided.
571 menu "Compression commands"
575 default y if CMD_BOOTI
578 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
583 default y if CMD_BOOTI
585 Uncompress a zip-compressed memory region.
590 Compress a memory region with zlib deflate method.
594 menu "Device access commands"
597 #depends on FLASH_CFI_DRIVER
600 ARM Ltd reference designs flash partition access
603 bool "adc - Access Analog to Digital Converters info and data"
607 Shows ADC device info and permit printing one-shot analog converted
608 data from a named Analog to Digital Converter.
611 bool "clk - Show clock frequencies"
614 Shows clock frequences by calling a sock_clk_dump() hook function.
615 This is depreated in favour of using the CLK uclass and accessing
616 clock values from associated drivers. However currently no command
620 bool "demo - Demonstration commands for driver model"
623 Provides a 'demo' command which can be used to play around with
624 driver model. To use this properly you will need to enable one or
625 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
626 Otherwise you will always get an empty list of devices. The demo
627 devices are defined in the sandbox device tree, so the easiest
628 option is to use sandbox and pass the -d point to sandbox's
635 Enables the command "dfu" which is used to have U-Boot create a DFU
636 class device via USB. This command requires that the "dfu_alt_info"
637 environment variable be set and define the alt settings to expose to
641 bool "dm - Access to driver model information"
644 Provides access to driver model data structures and information,
645 such as a list of devices, list of uclasses and the state of each
646 device (e.g. activated). This is not required for operation, but
647 can be useful to see the state of driver model for debugging or
651 bool "fastboot - Android fastboot support"
654 This enables the command "fastboot" which enables the Android
655 fastboot mode for the platform. Fastboot is a protocol for
656 downloading images, flashing and device control used on
657 Android devices. Fastboot requires either the network stack
658 enabled or support for acting as a USB device.
660 See doc/README.android-fastboot for more information.
663 bool "fdcboot - Boot from floppy device"
665 The 'fdtboot' command allows booting an image from a floppy disk.
668 bool "flinfo, erase, protect"
672 flinfo - print FLASH memory information
674 protect - enable or disable FLASH write protection
683 config CMD_FPGA_LOADBP
684 bool "fpga loadbp - load partial bitstream (Xilinx only)"
687 Supports loading an FPGA device from a bitstream buffer containing
690 config CMD_FPGA_LOADFS
691 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
694 Supports loading an FPGA device from a FAT filesystem.
696 config CMD_FPGA_LOADMK
697 bool "fpga loadmk - load bitstream from image"
700 Supports loading an FPGA device from a image generated by mkimage.
702 config CMD_FPGA_LOADP
703 bool "fpga loadp - load partial bitstream"
706 Supports loading an FPGA device from a bitstream buffer containing
709 config CMD_FPGA_LOAD_SECURE
710 bool "fpga loads - loads secure bitstreams (Xilinx only)"
713 Enables the fpga loads command which is used to load secure
714 (authenticated or encrypted or both) bitstreams on to FPGA.
717 bool "fpgad - dump FPGA registers"
719 (legacy, needs conversion to driver model)
720 Provides a way to dump FPGA registers by calling the board-specific
721 fpga_get_reg() function. This functions similarly to the 'md'
725 bool "fuse - support for the fuse subssystem"
727 (deprecated - needs conversion to driver model)
728 This allows reading, sensing, programming or overriding fuses
729 which control the behaviour of the device. The command uses the
738 bool "GPT (GUID Partition Table) command"
740 select HAVE_BLOCK_DEVICE
741 select PARTITION_UUIDS
744 Enable the 'gpt' command to ready and write GPT style partition
748 bool "GPT Random UUID generation"
751 Enable the generation of partitions with random UUIDs if none
754 config CMD_GPT_RENAME
755 bool "GPT partition renaming commands"
758 Enables the 'gpt' command to interchange names on two GPT
759 partitions via the 'gpt swap' command or to rename single
760 partitions via the 'rename' command.
763 bool "ide - Support for IDE drivers"
766 Provides an 'ide' command which allows accessing the IDE drive,
767 reseting the IDE interface, printing the partition table and
768 geting device info. It also enables the 'diskboot' command which
769 permits booting from an IDE drive.
772 bool "io - Support for performing I/O accesses"
774 Provides an 'iod' command to display I/O space and an 'iow' command
775 to write values to the I/O space. This can be useful for manually
776 checking the state of devices during boot when debugging device
780 bool "iotrace - Support for tracing I/O activity"
782 Provides an 'iotrace' command which supports recording I/O reads and
783 writes in a trace buffer in memory . It also maintains a checksum
784 of the trace records (even if space is exhausted) so that the
785 sequence of I/O accesses can be verified.
787 When debugging drivers it is useful to see what I/O accesses were
788 done and in what order.
790 Even if the individual accesses are of little interest it can be
791 useful to verify that the access pattern is consistent each time
792 an operation is performed. In this case a checksum can be used to
793 characterise the operation of a driver. The checksum can be compared
794 across different runs of the operation to verify that the driver is
797 In particular, when performing major refactoring of the driver, where
798 the access pattern should not change, the checksum provides assurance
799 that the refactoring work has not broken the driver.
801 This works by sneaking into the io.h heder for an architecture and
802 redirecting I/O accesses through iotrace's tracing mechanism.
804 For now no commands are provided to examine the trace buffer. The
805 format is fairly simple, so 'md' is a reasonable substitute.
807 Note: The checksum feature is only useful for I/O regions where the
808 contents do not change outside of software control. Where this is not
809 suitable you can fall back to manually comparing the addresses. It
810 might be useful to enhance tracing to only checksum the accesses and
811 not the data read/written.
822 Load a binary file over serial line.
828 Load an S-Record file over serial line
833 MMC memory mapped support.
836 bool "Enable support for RPMB in the mmc command"
839 Enable the commands for reading, writing and programming the
840 key for the Replay Protection Memory Block partition in eMMC.
842 config CMD_MMC_SWRITE
844 depends on CMD_MMC && MMC_WRITE
847 Enable support for the "mmc swrite" command to write Android sparse
852 default y if NAND_SUNXI
857 config CMD_NAND_TRIMFFS
858 bool "nand write.trimffs"
859 default y if ARCH_SUNXI
861 Allows one to skip empty pages when flashing something on a NAND.
863 config CMD_NAND_LOCK_UNLOCK
864 bool "nand lock/unlock"
866 NAND locking support.
868 config CMD_NAND_TORTURE
871 NAND torture support.
880 NVM Express device support
883 bool "mmc_spi - Set up MMC SPI device"
885 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
886 Peripheral Interface) device. The device provides a means of
887 accessing an MMC device via SPI using a single data line, limited
888 to 20MHz. It is useful since it reduces the amount of protocol code
892 bool "onenand - access to onenand device"
894 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
895 various useful features. This command allows reading, writing,
896 and erasing blocks. It allso provides a way to show and change
897 bad blocks, and test the device.
901 select HAVE_BLOCK_DEVICE
902 select PARTITION_UUIDS
904 Read and display information about the partition table on
908 bool "pci - Access PCI devices"
910 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
911 used on some devices to allow the CPU to communicate with its
912 peripherals. Sub-commands allow bus enumeration, displaying and
913 changing configuration space and a few other features.
916 bool "pinit - Set up PCMCIA device"
918 Provides a means to initialise a PCMCIA (Personal Computer Memory
919 Card International Association) device. This is an old standard from
920 about 1990. These devices are typically removable memory or network
921 cards using a standard 68-pin connector.
924 bool "read - Read binary data from a partition"
926 Provides low-level access to the data in a partition.
928 config CMD_REMOTEPROC
930 depends on REMOTEPROC
932 Support for Remote Processor control
935 bool "sata - Access SATA subsystem"
938 SATA (Serial Advanced Technology Attachment) is a serial bus
939 standard for connecting to hard drives and other storage devices.
940 This command provides information about attached devices and allows
941 reading, writing and other operations.
943 SATA replaces PATA (originally just ATA), which stands for Parallel AT
944 Attachment, where AT refers to an IBM AT (Advanced Technology)
945 computer released in 1984.
948 bool "saves - Save a file over serial in S-Record format"
950 Provides a way to save a binary file using the Motorola S-Record
951 format over the serial line.
954 bool "scsi - Access to SCSI devices"
957 This provides a 'scsi' command which provides access to SCSI (Small
958 Computer System Interface) devices. The command provides a way to
959 scan the bus, reset the bus, read and write data and get information
963 bool "sdram - Print SDRAM configuration information"
965 Provides information about attached SDRAM. This assumed that the
966 SDRAM has an EEPROM with information that can be read using the
967 I2C bus. This is only available on some boards.
975 bool "sf test - Allow testing of SPI flash"
977 Provides a way to test that SPI flash is working correctly. The
978 test is destructive, in that an area of SPI flash must be provided
979 for the test to use. Performance information is also provided,
980 measuring the performance of reading, writing and erasing in
981 Mbps (Million Bits Per Second). This value should approximately
982 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
983 everything is working properly.
991 bool "tsi148 - Command to access tsi148 device"
993 This provides various sub-commands to initialise and configure the
994 Turndra tsi148 device. See the command help for full details.
997 bool "universe - Command to set up the Turndra Universe controller"
999 This allows setting up the VMEbus provided by this controller.
1000 See the command help for full details.
1004 select HAVE_BLOCK_DEVICE
1010 select USB_FUNCTION_SDP
1012 Enables the command "sdp" which is used to have U-Boot emulating the
1013 Serial Download Protocol (SDP) via USB.
1017 depends on USB_FUNCTION_ROCKUSB
1019 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1020 read/write info, image to/from devices. This enable rockusb command
1021 support to communication with rockusb device. for more detail about
1022 this command, please read doc/README.rockusb.
1024 config CMD_USB_MASS_STORAGE
1025 bool "UMS usb mass storage"
1026 select USB_FUNCTION_MASS_STORAGE
1028 USB mass storage support
1034 Enable the command "axi" for accessing AXI (Advanced eXtensible
1035 Interface) busses, a on-chip interconnect specification for managing
1036 functional blocks in SoC designs, which is also often used in designs
1037 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1041 menu "Shell scripting commands"
1047 Echo args to console
1053 Return true/false on integer compare.
1059 Run script from memory
1065 Evaluate boolean and math expressions and store the result in an env
1067 Also supports loading the value at a memory location into a variable.
1068 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1075 bool "Network commands"
1085 bootp - boot image via network using BOOTP/TFTP protocol
1089 depends on CMD_BOOTP
1091 Boot image via network using DHCP/TFTP protocol
1093 config BOOTP_BOOTPATH
1094 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1096 depends on CMD_BOOTP
1098 Even though the config is called BOOTP_BOOTPATH, it stores the
1099 path in the variable 'rootpath'.
1102 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1104 depends on CMD_BOOTP
1106 The primary DNS server is stored as 'dnsip'. If two servers are
1107 returned, you must set BOOTP_DNS2 to store that second server IP
1111 bool "Store 'dnsip2' from BOOTP/DHCP server"
1112 depends on BOOTP_DNS
1114 If a DHCP client requests the DNS server IP from a DHCP server,
1115 it is possible that more than one DNS serverip is offered to the
1116 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1117 server IP will be stored in the additional environment
1118 variable "dnsip2". The first DNS serverip is always
1119 stored in the variable "dnsip", when BOOTP_DNS is defined.
1121 config BOOTP_GATEWAY
1122 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1124 depends on CMD_BOOTP
1126 config BOOTP_HOSTNAME
1127 bool "Request & store 'hostname' from BOOTP/DHCP server"
1129 depends on CMD_BOOTP
1131 The name may or may not be qualified with the local domain name.
1133 config BOOTP_PREFER_SERVERIP
1134 bool "serverip variable takes precedent over DHCP server IP."
1135 depends on CMD_BOOTP
1137 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1139 With this option enabled, the 'serverip' variable in the environment
1140 takes precedence over DHCP server IP and will only be set by the DHCP
1141 server if not already set in the environment.
1143 config BOOTP_SUBNETMASK
1144 bool "Request & store 'netmask' from BOOTP/DHCP server"
1146 depends on CMD_BOOTP
1148 config BOOTP_NTPSERVER
1149 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1150 depends on CMD_BOOTP
1153 bool "Send PXE client arch to BOOTP/DHCP server"
1155 depends on CMD_BOOTP && CMD_PXE
1157 Supported for ARM, ARM64, and x86 for now.
1159 config BOOTP_PXE_CLIENTARCH
1161 depends on BOOTP_PXE
1162 default 0x16 if ARM64
1166 config BOOTP_VCI_STRING
1168 depends on CMD_BOOTP
1169 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1170 default "U-Boot.armv8" if ARM64
1171 default "U-Boot.arm" if ARM
1178 tftpboot - boot image via network using TFTP protocol
1182 depends on CMD_TFTPBOOT
1184 TFTP put command, for uploading files to a server
1188 depends on CMD_TFTPBOOT
1190 Act as a TFTP server and boot the first received file
1192 config NET_TFTP_VARS
1193 bool "Control TFTP timeout and count through environment"
1194 depends on CMD_TFTPBOOT
1197 If set, allows controlling the TFTP timeout through the
1198 environment variable tftptimeout, and the TFTP maximum
1199 timeout count through the variable tftptimeoutcountmax.
1200 If unset, timeout and maximum are hard-defined as 1 second
1201 and 10 timouts per TFTP transfer.
1206 Boot image via network using RARP/TFTP protocol
1212 Boot image via network using NFS protocol.
1217 Enable MII utility commands.
1222 Send ICMP ECHO_REQUEST to network host
1227 Perform CDP network configuration
1232 Synchronize RTC via network
1237 Lookup the IP of a hostname
1239 config CMD_LINK_LOCAL
1243 Acquire a network IP address using the link-local protocol
1250 Allow control of L2 Ethernet switch commands. These are supported
1251 by the vsc9953 Ethernet driver at present. Sub-commands allow
1252 operations such as enabling / disabling a port and
1253 viewing/maintaining the filtering database (FDB)
1259 Boot image via network using PXE protocol
1264 Wait for wake-on-lan Magic Packet
1268 menu "Misc commands"
1271 bool "Enable 'bmp' command"
1272 depends on LCD || DM_VIDEO || VIDEO
1274 This provides a way to obtain information about a BMP-format iamge
1275 and to display it. BMP (which presumably stands for BitMaP) is a
1276 file format defined by Microsoft which supports images of various
1277 depths, formats and compression methods. Headers on the file
1278 determine the formats used. This command can be used by first loading
1279 the image into RAM, then using this command to look at it or display
1282 config CMD_BOOTCOUNT
1284 depends on BOOTCOUNT_LIMIT
1286 Enable the bootcount command, which allows interrogation and
1287 reset of the bootcounter.
1290 bool "Enable board-specific commands"
1292 (deprecated: instead, please define a Kconfig option for each command)
1294 Some boards have board-specific commands which are only enabled
1295 during developemnt and need to be turned off for production. This
1296 option provides a way to control this. The commands that are enabled
1297 vary depending on the board.
1299 config CMD_BKOPS_ENABLE
1300 bool "mmc bkops enable"
1304 Enable command for setting manual background operations handshake
1305 on a eMMC device. The feature is optionally available on eMMC devices
1306 conforming to standard >= 4.41.
1308 config CMD_BLOCK_CACHE
1309 bool "blkcache - control and stats for block cache"
1310 depends on BLOCK_CACHE
1311 default y if BLOCK_CACHE
1313 Enable the blkcache command, which can be used to control the
1314 operation of the cache functions.
1315 This is most useful when fine-tuning the operation of the cache
1316 during development, but also allows the cache to be disabled when
1317 it might hurt performance (e.g. when using the ums command).
1320 bool "icache or dcache"
1322 Enable the "icache" and "dcache" commands
1325 bool "Enable the 'display' command, for character displays"
1327 (this needs porting to driver model)
1328 This enables the 'display' command which allows a string to be
1329 displayed on a simple board-specific display. Implement
1330 display_putc() to use it.
1336 Enable the 'led' command which allows for control of LEDs supported
1337 by the board. The LEDs can be listed with 'led list' and controlled
1338 with led on/off/togle/blink. Any LED drivers can be controlled with
1339 this command, e.g. led_gpio.
1345 Enable the 'date' command for getting/setting the time/date in RTC
1351 Run commands and summarize execution time.
1354 bool "gettime - read elapsed time"
1356 Enable the 'gettime' command which reads the elapsed time since
1357 U-Boot started running. This shows the time in seconds and
1358 milliseconds. See also the 'bootstage' command which provides more
1359 flexibility for boot timing.
1361 # TODO: rename to CMD_SLEEP
1366 Delay execution for some time
1369 bool "support for multiprocessor"
1371 This provides an option to brinup
1372 different processors in multiprocessor
1378 Access the system timer.
1384 This provides basic access to the U-Boot's sound support. The main
1385 feature is to play a beep.
1387 sound init - set up sound system
1388 sound play - play a sound
1394 This provides access to the QEMU firmware interface. The main
1395 feature is to allow easy loading of files passed to qemu-system
1396 via -kernel / -initrd
1398 source "cmd/mvebu/Kconfig"
1401 bool "terminal - provides a way to attach a serial terminal"
1403 Provides a 'cu'-like serial terminal command. This can be used to
1404 access other serial ports from the system console. The terminal
1405 is very simple with no special processing of characters. As with
1406 cu, you can press ~. (tilde followed by period) to exit.
1409 bool "uuid, guid - generation of unique IDs"
1412 This enables two commands:
1414 uuid - generate random Universally Unique Identifier
1415 guid - generate Globally Unique Identifier based on random UUID
1417 The two commands are very similar except for the endianness of the
1422 source "cmd/ti/Kconfig"
1424 config CMD_BOOTSTAGE
1425 bool "Enable the 'bootstage' command"
1426 depends on BOOTSTAGE
1428 Add a 'bootstage' command which supports printing a report
1429 and un/stashing of bootstage data.
1431 menu "Power commands"
1433 bool "Enable Driver Model PMIC command"
1436 This is the pmic command, based on a driver model pmic's API.
1437 Command features are unchanged:
1438 - list - list pmic devices
1439 - pmic dev <id> - show or [set] operating pmic device (NEW)
1440 - pmic dump - dump registers
1441 - pmic read address - read byte of register at address
1442 - pmic write address - write byte to register at address
1443 The only one change for this command is 'dev' subcommand.
1445 config CMD_REGULATOR
1446 bool "Enable Driver Model REGULATOR command"
1447 depends on DM_REGULATOR
1449 This command is based on driver model regulator's API.
1450 User interface features:
1451 - list - list regulator devices
1452 - regulator dev <id> - show or [set] operating regulator device
1453 - regulator info - print constraints info
1454 - regulator status - print operating status
1455 - regulator value <val] <-f> - print/[set] voltage value [uV]
1456 - regulator current <val> - print/[set] current value [uA]
1457 - regulator mode <id> - print/[set] operating mode id
1458 - regulator enable - enable the regulator output
1459 - regulator disable - disable the regulator output
1461 The '-f' (force) option can be used for set the value which exceeds
1462 the limits, which are found in device-tree and are kept in regulator's
1463 uclass platdata structure.
1467 menu "Security commands"
1469 bool "Enable the 'aes' command"
1472 This provides a means to encrypt and decrypt data using the AES
1473 (Advanced Encryption Standard). This algorithm uses a symetric key
1474 and is widely used as a streaming cipher. Different key lengths are
1475 supported by the algorithm but this command only supports 128 bits
1479 bool "Enable the 'blob' command"
1481 This is used with the Freescale secure boot mechanism.
1483 Freescale's SEC block has built-in Blob Protocol which provides
1484 a method for protecting user-defined data across system power
1485 cycles. SEC block protects data in a data structure called a Blob,
1486 which provides both confidentiality and integrity protection.
1488 Encapsulating data as a blob
1489 Each time that the Blob Protocol is used to protect data, a
1490 different randomly generated key is used to encrypt the data.
1491 This random key is itself encrypted using a key which is derived
1492 from SoC's non-volatile secret key and a 16 bit Key identifier.
1493 The resulting encrypted key along with encrypted data is called a
1494 blob. The non-volatile secure key is available for use only during
1497 During decapsulation, the reverse process is performed to get back
1501 blob enc - encapsulating data as a cryptgraphic blob
1502 blob dec - decapsulating cryptgraphic blob to get the data
1506 blob enc src dst len km
1508 Encapsulate and create blob of data $len bytes long
1509 at address $src and store the result at address $dst.
1510 $km is the 16 byte key modifier is also required for
1511 generation/use as key for cryptographic operation. Key
1512 modifier should be 16 byte long.
1514 blob dec src dst len km
1516 Decapsulate the blob of data at address $src and
1517 store result of $len byte at addr $dst.
1518 $km is the 16 byte key modifier is also required for
1519 generation/use as key for cryptographic operation. Key
1520 modifier should be 16 byte long.
1523 bool "Support 'hash' command"
1526 This provides a way to hash data in memory using various supported
1527 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1528 saved to memory or to an environment variable. It is also possible
1529 to verify a hash against data in memory.
1532 bool "Support the 'hvc' command"
1533 depends on ARM_SMCCC
1535 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1536 development and testing.
1539 bool "Support the 'smc' command"
1540 depends on ARM_SMCCC
1542 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1543 development and testing.
1549 Add -v option to verify data against a hash.
1559 bool "Enable the 'tpm' command"
1560 depends on TPM_V1 || TPM_V2
1561 select CMD_TPM_V1 if TPM_V1
1562 select CMD_TPM_V2 if TPM_V2
1564 This provides a means to talk to a TPM from the command line. A wide
1565 range of commands if provided - see 'tpm help' for details. The
1566 command requires a suitable TPM on your board and the correct driver
1572 bool "Enable the 'tpm test' command"
1575 This provides a a series of tests to confirm that the TPMv1.x is
1576 working correctly. The tests cover initialisation, non-volatile RAM,
1577 extend, global lock and checking that timing is within expectations.
1578 The tests pass correctly on Infineon TPMs but may need to be adjusted
1585 menu "Firmware commands"
1587 bool "Enable crosec command"
1591 Enable command-line access to the Chrome OS EC (Embedded
1592 Controller). This provides the 'crosec' command which has
1593 a number of sub-commands for performing EC tasks such as
1594 updating its flash, accessing a small saved context area
1595 and talking to the I2C bus behind the EC (if there is one).
1598 menu "Filesystem commands"
1600 bool "Enable the 'btrsubvol' command"
1603 This enables the 'btrsubvol' command to list subvolumes
1604 of a BTRFS filesystem. There are no special commands for
1605 listing BTRFS directories or loading BTRFS files - this
1606 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1607 when BTRFS is enabled (see FS_BTRFS).
1610 bool "Enable the 'cbfs' command"
1613 Define this to enable support for reading from a Coreboot
1614 filesystem. This is a ROM-based filesystem used for accessing files
1615 on systems that use coreboot as the first boot-loader and then load
1616 U-Boot to actually boot the Operating System. Available commands are
1617 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1620 bool "Enable the 'cramfs' command"
1621 depends on FS_CRAMFS
1623 This provides commands for dealing with CRAMFS (Compressed ROM
1624 filesystem). CRAMFS is useful when space is tight since files are
1625 compressed. Two commands are provided:
1627 cramfsls - lists files in a cramfs image
1628 cramfsload - loads a file from a cramfs image
1631 bool "ext2 command support"
1634 Enables EXT2 FS command
1637 bool "ext4 command support"
1640 Enables EXT4 FS command
1642 config CMD_EXT4_WRITE
1644 bool "ext4 write command support"
1647 Enables EXT4 FS write command
1650 bool "FAT command support"
1653 Support for the FAT fs
1655 config CMD_FS_GENERIC
1656 bool "filesystem commands"
1658 Enables filesystem commands (e.g. load, ls) that work for multiple
1662 bool "fsuuid command"
1664 Enables fsuuid command for filesystem UUID.
1667 bool "jffs2 command"
1670 Enables commands to support the JFFS2 (Journalling Flash File System
1671 version 2) filesystem. This enables fsload, ls and fsinfo which
1672 provide the ability to load files, list directories and obtain
1673 filesystem information.
1676 bool "MTD partition support"
1677 select MTD_DEVICE if (CMD_NAND || NAND)
1679 MTD partition support
1681 config MTDIDS_DEFAULT
1682 string "Default MTD IDs"
1683 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1685 Defines a default MTD IDs list for use with MTD partitions in the
1686 Linux MTD command line partitions format.
1688 config MTDPARTS_DEFAULT
1689 string "Default MTD partition scheme"
1690 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1692 Defines a default MTD partitioning scheme in the Linux MTD command
1693 line partitions format
1695 config CMD_MTDPARTS_SPREAD
1696 bool "Padd partition size to take account of bad blocks"
1697 depends on CMD_MTDPARTS
1699 This enables the 'spread' sub-command of the mtdparts command.
1700 This command will modify the existing mtdparts variable by increasing
1701 the size of the partitions such that 1) each partition's net size is
1702 at least as large as the size specified in the mtdparts variable and
1703 2) each partition starts on a good block.
1706 bool "reiser - Access to reiserfs filesystems"
1708 This provides two commands which operate on a resierfs filesystem,
1709 commonly used some years ago:
1711 reiserls - list files
1712 reiserload - load a file
1715 bool "yaffs2 - Access of YAFFS2 filesystem"
1719 This provides commands for accessing a YAFFS2 filesystem. Yet
1720 Another Flash Filesystem 2 is a filesystem designed specifically
1721 for NAND flash. It incorporates bad-block management and ensures
1722 that device writes are sequential regardless of filesystem
1726 bool "zfs - Access of ZFS filesystem"
1728 This provides commands to accessing a ZFS filesystem, commonly used
1729 on Solaris systems. Two sub-commands are provided:
1731 zfsls - list files in a directory
1732 zfsload - load a file
1734 See doc/README.zfs for more details.
1738 menu "Debug commands"
1743 The bedbug (emBEDded deBUGger) command provides debugging features
1744 for some PowerPC processors. For details please see the
1745 docuemntation in doc/README.beddbug
1748 bool "diag - Board diagnostics"
1750 This command provides access to board diagnostic tests. These are
1751 called Power-on Self Tests (POST). The command allows listing of
1752 available tests and running either all the tests, or specific tests
1756 bool "irq - Show information about interrupts"
1757 depends on !ARM && !MIPS && !SH
1759 This enables two commands:
1761 interrupts - enable or disable interrupts
1762 irqinfo - print device-specific interrupt information
1765 bool "kgdb - Allow debugging of U-Boot with gdb"
1767 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1768 over a serial link for debugging purposes. This allows
1769 single-stepping, inspecting variables, etc. This is supported only
1770 on PowerPC at present.
1773 bool "log - Generation, control and access to logging"
1776 This provides access to logging features. It allows the output of
1777 log data to be controlled to a limited extent (setting up the default
1778 maximum log level for emitting of records). It also provides access
1779 to a command used for testing the log system.
1782 bool "trace - Support tracing of function calls and timing"
1784 Enables a command to control using of function tracing within
1785 U-Boot. This allows recording of call traces including timing
1786 information. The command can write data to memory for exporting
1787 for analsys (e.g. using bootchart). See doc/README.trace for full
1791 bool "avb - Android Verified Boot 2.0 operations"
1792 depends on AVB_VERIFY
1795 Enables a "avb" command to perform verification of partitions using
1796 Android Verified Boot 2.0 functionality. It includes such subcommands:
1797 avb init - initialize avb2 subsystem
1798 avb read_rb - read rollback index
1799 avb write_rb - write rollback index
1800 avb is_unlocked - check device lock state
1801 avb get_uuid - read and print uuid of a partition
1802 avb read_part - read data from partition
1803 avb read_part_hex - read data from partition and output to stdout
1804 avb write_part - write data to partition
1805 avb verify - run full verification chain
1809 tristate "Enable UBI - Unsorted block images commands"
1810 default y if NAND_SUNXI
1815 UBI is a software layer above MTD layer which admits use of LVM-like
1816 logical volumes on top of MTD devices, hides some complexities of
1817 flash chips like wear and bad blocks and provides some other useful
1818 capabilities. Please, consult the MTD web site for more details
1819 (www.linux-mtd.infradead.org). Activate this option if you want
1820 to use U-Boot UBI commands.
1823 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1825 default y if CMD_UBI
1829 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob