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.
260 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
261 image into RAM, dump image structure information, etc. Those dtb/dtbo
262 files should be merged in one dtb further, which needs to be passed to
263 the kernel, as part of a boot process.
266 bool "bootelf, bootvx"
269 Boot an ELF/vxWorks image from the memory.
272 bool "Flattened Device Tree utility commands"
276 Do FDT related setup before booting into the Operating System.
282 Start an application at a given address.
288 Run the command in the given environment variable.
294 Print header information for application image.
299 List all images found in flash
305 Extract a part of a multi-image.
308 bool "spl export - Export boot information for Falcon boot"
311 Falcon mode allows booting directly from SPL into an Operating
312 System such as Linux, thus skipping U-Boot proper. See
313 doc/README.falcon for full information about how to use this
316 config CMD_SPL_NAND_OFS
317 hex "Offset of OS command line args for Falcon-mode NAND boot"
321 This provides the offset of the command line arguments for Linux
322 when booting from NAND in Falcon mode. See doc/README.falcon
323 for full information about how to use this option (and also see
324 board/gateworks/gw_ventana/README for an example).
326 config CMD_SPL_WRITE_SIZE
327 hex "Size of argument area"
331 This provides the size of the command-line argument area in NAND
332 flash used by Falcon-mode boot. See the documentation until CMD_SPL
336 bool "fitImage update command"
338 Implements the 'fitupd' command, which allows to automatically
339 store software updates present on a TFTP server in NOR Flash
341 config CMD_THOR_DOWNLOAD
342 bool "thor - TIZEN 'thor' download"
344 Implements the 'thor' download protocol. This is a way of
345 downloading a software update over USB from an attached host.
346 There is no documentation about this within the U-Boot source code
347 but you should be able to find something on the interwebs.
350 bool "zboot - x86 boot command"
352 With x86 machines it is common to boot a bzImage file which
353 contains both a kernel and a setup.bin file. The latter includes
354 configuration information from the dark ages which x86 boards still
355 need to pick things out of.
357 Consider using FIT in preference to this since it supports directly
358 booting both 32- and 64-bit kernels, as well as secure boot.
359 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
363 menu "Environment commands"
366 bool "ask for env variable"
368 Ask for environment variable
386 Edit environment variable.
391 Allow for searching environment variables
397 Save all environment variables into the compiled-in persistent
400 config CMD_ENV_EXISTS
404 Check if a variable is defined in the environment for use in
407 config CMD_ENV_CALLBACK
408 bool "env callbacks - print callbacks and their associated variables"
410 Some environment variable have callbacks defined by
411 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
412 For example changing "baudrate" adjust the serial baud rate. This
413 command lists the currently defined callbacks.
416 bool "env flags -print variables that have non-default flags"
418 Some environment variables have special flags that control their
419 behaviour. For example, serial# can only be written once and cannot
420 be deleted. This command shows the variables that have special
425 menu "Memory commands"
430 Compute binary operations (xor, or, and) of byte arrays of arbitrary
431 size from memory and store the result in memory or the environment.
444 Add -v option to verify data against a crc32 checksum.
447 bool "eeprom - EEPROM subsystem"
449 (deprecated, needs conversion to driver model)
450 Provides commands to read and write EEPROM (Electrically Erasable
451 Programmable Read Only Memory) chips that are connected over an
454 config CMD_EEPROM_LAYOUT
455 bool "Enable layout-aware eeprom commands"
456 depends on CMD_EEPROM
458 (deprecated, needs conversion to driver model)
459 When enabled, additional eeprom sub-commands become available.
461 eeprom print - prints the contents of the eeprom in a human-readable
462 way (eeprom layout fields, and data formatted to be fit for human
465 eeprom update - allows user to update eeprom fields by specifying
466 the field name, and providing the new data in a human readable format
467 (same format as displayed by the eeprom print command).
469 Both commands can either auto detect the layout, or be told which
473 __weak int parse_layout_version(char *str)
474 - override to provide your own layout name parsing
475 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
477 - override to setup the layout metadata based on the version
478 __weak int eeprom_layout_detect(unsigned char *data)
479 - override to provide your own algorithm for detecting layout
482 - contains various printing and updating functions for common
483 types of eeprom fields. Can be used for defining
486 config EEPROM_LAYOUT_HELP_STRING
487 string "Tells user what layout names are supported"
488 depends on CMD_EEPROM_LAYOUT
489 default "<not defined>"
491 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
497 Infinite write loop on address range
504 Compute MD5 checksum.
509 depends on CMD_MD5SUM
511 Add -v option to verify data against an MD5 checksum.
516 Display memory information.
519 bool "md, mm, nm, mw, cp, cmp, base, loop"
524 mm - memory modify (auto-incrementing address)
525 nm - memory modify (constant address)
526 mw - memory write (fill)
529 base - print or set address offset
530 loop - initialize loop on address range
535 Simple RAM read/write test.
539 config SYS_ALT_MEMTEST
540 bool "Alternative test"
542 Use a more complete alternative memory test.
549 mdc - memory display cyclic
550 mwc - memory write cyclic
556 Compute SHA1 checksum.
558 config SHA1SUM_VERIFY
560 depends on CMD_SHA1SUM
562 Add -v option to verify data against a SHA1 checksum.
565 bool "strings - display strings in memory"
567 This works similarly to the Unix 'strings' command except that it
568 works with a memory range. String of printable characters found
569 within the range are displayed. The minimum number of characters
570 for a sequence to be considered a string can be provided.
574 menu "Compression commands"
578 default y if CMD_BOOTI
581 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
586 default y if CMD_BOOTI
588 Uncompress a zip-compressed memory region.
593 Compress a memory region with zlib deflate method.
597 menu "Device access commands"
600 #depends on FLASH_CFI_DRIVER
603 ARM Ltd reference designs flash partition access
606 bool "adc - Access Analog to Digital Converters info and data"
610 Shows ADC device info and permit printing one-shot analog converted
611 data from a named Analog to Digital Converter.
614 bool "bind/unbind - Bind or unbind a device to/from a driver"
617 Bind or unbind a device to/from a driver from the command line.
618 This is useful in situations where a device may be handled by several
619 drivers. For example, this can be used to bind a UDC to the usb ether
620 gadget driver from the command line.
623 bool "clk - Show clock frequencies"
626 Shows clock frequences by calling a sock_clk_dump() hook function.
627 This is depreated in favour of using the CLK uclass and accessing
628 clock values from associated drivers. However currently no command
632 bool "demo - Demonstration commands for driver model"
635 Provides a 'demo' command which can be used to play around with
636 driver model. To use this properly you will need to enable one or
637 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
638 Otherwise you will always get an empty list of devices. The demo
639 devices are defined in the sandbox device tree, so the easiest
640 option is to use sandbox and pass the -d point to sandbox's
647 Enables the command "dfu" which is used to have U-Boot create a DFU
648 class device via USB. This command requires that the "dfu_alt_info"
649 environment variable be set and define the alt settings to expose to
653 bool "dm - Access to driver model information"
656 Provides access to driver model data structures and information,
657 such as a list of devices, list of uclasses and the state of each
658 device (e.g. activated). This is not required for operation, but
659 can be useful to see the state of driver model for debugging or
663 bool "fastboot - Android fastboot support"
666 This enables the command "fastboot" which enables the Android
667 fastboot mode for the platform. Fastboot is a protocol for
668 downloading images, flashing and device control used on
669 Android devices. Fastboot requires either the network stack
670 enabled or support for acting as a USB device.
672 See doc/README.android-fastboot for more information.
675 bool "fdcboot - Boot from floppy device"
677 The 'fdtboot' command allows booting an image from a floppy disk.
680 bool "flinfo, erase, protect"
684 flinfo - print FLASH memory information
686 protect - enable or disable FLASH write protection
695 config CMD_FPGA_LOADBP
696 bool "fpga loadbp - load partial bitstream (Xilinx only)"
699 Supports loading an FPGA device from a bitstream buffer containing
702 config CMD_FPGA_LOADFS
703 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
706 Supports loading an FPGA device from a FAT filesystem.
708 config CMD_FPGA_LOADMK
709 bool "fpga loadmk - load bitstream from image"
712 Supports loading an FPGA device from a image generated by mkimage.
714 config CMD_FPGA_LOADP
715 bool "fpga loadp - load partial bitstream"
718 Supports loading an FPGA device from a bitstream buffer containing
721 config CMD_FPGA_LOAD_SECURE
722 bool "fpga loads - loads secure bitstreams (Xilinx only)"
725 Enables the fpga loads command which is used to load secure
726 (authenticated or encrypted or both) bitstreams on to FPGA.
729 bool "fpgad - dump FPGA registers"
731 (legacy, needs conversion to driver model)
732 Provides a way to dump FPGA registers by calling the board-specific
733 fpga_get_reg() function. This functions similarly to the 'md'
737 bool "fuse - support for the fuse subssystem"
739 (deprecated - needs conversion to driver model)
740 This allows reading, sensing, programming or overriding fuses
741 which control the behaviour of the device. The command uses the
750 bool "GPT (GUID Partition Table) command"
752 select HAVE_BLOCK_DEVICE
753 select PARTITION_UUIDS
756 Enable the 'gpt' command to ready and write GPT style partition
760 bool "GPT Random UUID generation"
763 Enable the generation of partitions with random UUIDs if none
766 config CMD_GPT_RENAME
767 bool "GPT partition renaming commands"
770 Enables the 'gpt' command to interchange names on two GPT
771 partitions via the 'gpt swap' command or to rename single
772 partitions via the 'rename' command.
775 bool "ide - Support for IDE drivers"
778 Provides an 'ide' command which allows accessing the IDE drive,
779 reseting the IDE interface, printing the partition table and
780 geting device info. It also enables the 'diskboot' command which
781 permits booting from an IDE drive.
784 bool "io - Support for performing I/O accesses"
786 Provides an 'iod' command to display I/O space and an 'iow' command
787 to write values to the I/O space. This can be useful for manually
788 checking the state of devices during boot when debugging device
792 bool "iotrace - Support for tracing I/O activity"
794 Provides an 'iotrace' command which supports recording I/O reads and
795 writes in a trace buffer in memory . It also maintains a checksum
796 of the trace records (even if space is exhausted) so that the
797 sequence of I/O accesses can be verified.
799 When debugging drivers it is useful to see what I/O accesses were
800 done and in what order.
802 Even if the individual accesses are of little interest it can be
803 useful to verify that the access pattern is consistent each time
804 an operation is performed. In this case a checksum can be used to
805 characterise the operation of a driver. The checksum can be compared
806 across different runs of the operation to verify that the driver is
809 In particular, when performing major refactoring of the driver, where
810 the access pattern should not change, the checksum provides assurance
811 that the refactoring work has not broken the driver.
813 This works by sneaking into the io.h heder for an architecture and
814 redirecting I/O accesses through iotrace's tracing mechanism.
816 For now no commands are provided to examine the trace buffer. The
817 format is fairly simple, so 'md' is a reasonable substitute.
819 Note: The checksum feature is only useful for I/O regions where the
820 contents do not change outside of software control. Where this is not
821 suitable you can fall back to manually comparing the addresses. It
822 might be useful to enhance tracing to only checksum the accesses and
823 not the data read/written.
833 bool "w1 - Support for Dallas 1-Wire protocol"
835 Dallas 1-wire protocol support
841 Load a binary file over serial line.
847 Load an S-Record file over serial line
852 MMC memory mapped support.
855 bool "Enable support for RPMB in the mmc command"
858 Enable the commands for reading, writing and programming the
859 key for the Replay Protection Memory Block partition in eMMC.
861 config CMD_MMC_SWRITE
863 depends on CMD_MMC && MMC_WRITE
866 Enable support for the "mmc swrite" command to write Android sparse
871 select MTD_PARTITIONS
873 MTD commands support.
877 default y if NAND_SUNXI
882 config CMD_NAND_TRIMFFS
883 bool "nand write.trimffs"
884 default y if ARCH_SUNXI
886 Allows one to skip empty pages when flashing something on a NAND.
888 config CMD_NAND_LOCK_UNLOCK
889 bool "nand lock/unlock"
891 NAND locking support.
893 config CMD_NAND_TORTURE
896 NAND torture support.
905 NVM Express device support
908 bool "mmc_spi - Set up MMC SPI device"
910 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
911 Peripheral Interface) device. The device provides a means of
912 accessing an MMC device via SPI using a single data line, limited
913 to 20MHz. It is useful since it reduces the amount of protocol code
917 bool "onenand - access to onenand device"
919 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
920 various useful features. This command allows reading, writing,
921 and erasing blocks. It allso provides a way to show and change
922 bad blocks, and test the device.
927 Enable the 'osd' command which allows to query information from and
928 write text data to a on-screen display (OSD) device; a virtual device
929 associated with a display capable of displaying a text overlay on the
930 display it's associated with..
934 select HAVE_BLOCK_DEVICE
935 select PARTITION_UUIDS
937 Read and display information about the partition table on
941 bool "pci - Access PCI devices"
943 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
944 used on some devices to allow the CPU to communicate with its
945 peripherals. Sub-commands allow bus enumeration, displaying and
946 changing configuration space and a few other features.
949 bool "pinit - Set up PCMCIA device"
951 Provides a means to initialise a PCMCIA (Personal Computer Memory
952 Card International Association) device. This is an old standard from
953 about 1990. These devices are typically removable memory or network
954 cards using a standard 68-pin connector.
957 bool "pinmux - show pins muxing"
960 Parse all available pin-controllers and show pins muxing. This
961 is useful for debug purpoer to check the pin muxing and to know if
962 a pin is configured as a GPIO or as an alternate function.
967 Poweroff/Shutdown the system
970 bool "read - Read binary data from a partition"
972 Provides low-level access to the data in a partition.
974 config CMD_REMOTEPROC
976 depends on REMOTEPROC
978 Support for Remote Processor control
981 bool "sata - Access SATA subsystem"
984 SATA (Serial Advanced Technology Attachment) is a serial bus
985 standard for connecting to hard drives and other storage devices.
986 This command provides information about attached devices and allows
987 reading, writing and other operations.
989 SATA replaces PATA (originally just ATA), which stands for Parallel AT
990 Attachment, where AT refers to an IBM AT (Advanced Technology)
991 computer released in 1984.
994 bool "saves - Save a file over serial in S-Record format"
996 Provides a way to save a binary file using the Motorola S-Record
997 format over the serial line.
1000 bool "scsi - Access to SCSI devices"
1003 This provides a 'scsi' command which provides access to SCSI (Small
1004 Computer System Interface) devices. The command provides a way to
1005 scan the bus, reset the bus, read and write data and get information
1009 bool "sdram - Print SDRAM configuration information"
1011 Provides information about attached SDRAM. This assumed that the
1012 SDRAM has an EEPROM with information that can be read using the
1013 I2C bus. This is only available on some boards.
1021 bool "sf test - Allow testing of SPI flash"
1023 Provides a way to test that SPI flash is working correctly. The
1024 test is destructive, in that an area of SPI flash must be provided
1025 for the test to use. Performance information is also provided,
1026 measuring the performance of reading, writing and erasing in
1027 Mbps (Million Bits Per Second). This value should approximately
1028 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1029 everything is working properly.
1034 SPI utility command.
1037 bool "tsi148 - Command to access tsi148 device"
1039 This provides various sub-commands to initialise and configure the
1040 Turndra tsi148 device. See the command help for full details.
1043 bool "universe - Command to set up the Turndra Universe controller"
1045 This allows setting up the VMEbus provided by this controller.
1046 See the command help for full details.
1050 select HAVE_BLOCK_DEVICE
1056 select USB_FUNCTION_SDP
1058 Enables the command "sdp" which is used to have U-Boot emulating the
1059 Serial Download Protocol (SDP) via USB.
1063 depends on USB_FUNCTION_ROCKUSB
1065 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1066 read/write info, image to/from devices. This enable rockusb command
1067 support to communication with rockusb device. for more detail about
1068 this command, please read doc/README.rockusb.
1070 config CMD_USB_MASS_STORAGE
1071 bool "UMS usb mass storage"
1072 select USB_FUNCTION_MASS_STORAGE
1074 USB mass storage support
1081 VirtIO block device support
1087 Enable the command "axi" for accessing AXI (Advanced eXtensible
1088 Interface) busses, a on-chip interconnect specification for managing
1089 functional blocks in SoC designs, which is also often used in designs
1090 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1094 menu "Shell scripting commands"
1100 Echo args to console
1106 Return true/false on integer compare.
1112 Run script from memory
1118 Evaluate boolean and math expressions and store the result in an env
1120 Also supports loading the value at a memory location into a variable.
1121 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1128 bool "Network commands"
1138 bootp - boot image via network using BOOTP/TFTP protocol
1142 depends on CMD_BOOTP
1144 Boot image via network using DHCP/TFTP protocol
1146 config BOOTP_BOOTPATH
1147 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1149 depends on CMD_BOOTP
1151 Even though the config is called BOOTP_BOOTPATH, it stores the
1152 path in the variable 'rootpath'.
1155 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1157 depends on CMD_BOOTP
1159 The primary DNS server is stored as 'dnsip'. If two servers are
1160 returned, you must set BOOTP_DNS2 to store that second server IP
1164 bool "Store 'dnsip2' from BOOTP/DHCP server"
1165 depends on BOOTP_DNS
1167 If a DHCP client requests the DNS server IP from a DHCP server,
1168 it is possible that more than one DNS serverip is offered to the
1169 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1170 server IP will be stored in the additional environment
1171 variable "dnsip2". The first DNS serverip is always
1172 stored in the variable "dnsip", when BOOTP_DNS is defined.
1174 config BOOTP_GATEWAY
1175 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1177 depends on CMD_BOOTP
1179 config BOOTP_HOSTNAME
1180 bool "Request & store 'hostname' from BOOTP/DHCP server"
1182 depends on CMD_BOOTP
1184 The name may or may not be qualified with the local domain name.
1186 config BOOTP_PREFER_SERVERIP
1187 bool "serverip variable takes precedent over DHCP server IP."
1188 depends on CMD_BOOTP
1190 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1192 With this option enabled, the 'serverip' variable in the environment
1193 takes precedence over DHCP server IP and will only be set by the DHCP
1194 server if not already set in the environment.
1196 config BOOTP_SUBNETMASK
1197 bool "Request & store 'netmask' from BOOTP/DHCP server"
1199 depends on CMD_BOOTP
1201 config BOOTP_NTPSERVER
1202 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1203 depends on CMD_BOOTP
1206 bool "Send PXE client arch to BOOTP/DHCP server"
1208 depends on CMD_BOOTP && CMD_PXE
1210 Supported for ARM, ARM64, and x86 for now.
1212 config BOOTP_PXE_CLIENTARCH
1214 depends on BOOTP_PXE
1215 default 0x16 if ARM64
1219 config BOOTP_VCI_STRING
1221 depends on CMD_BOOTP
1222 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1223 default "U-Boot.armv8" if ARM64
1224 default "U-Boot.arm" if ARM
1231 tftpboot - boot image via network using TFTP protocol
1235 depends on CMD_TFTPBOOT
1237 TFTP put command, for uploading files to a server
1241 depends on CMD_TFTPBOOT
1243 Act as a TFTP server and boot the first received file
1245 config NET_TFTP_VARS
1246 bool "Control TFTP timeout and count through environment"
1247 depends on CMD_TFTPBOOT
1250 If set, allows controlling the TFTP timeout through the
1251 environment variable tftptimeout, and the TFTP maximum
1252 timeout count through the variable tftptimeoutcountmax.
1253 If unset, timeout and maximum are hard-defined as 1 second
1254 and 10 timouts per TFTP transfer.
1259 Boot image via network using RARP/TFTP protocol
1265 Boot image via network using NFS protocol.
1270 Enable MII utility commands.
1275 Send ICMP ECHO_REQUEST to network host
1280 Perform CDP network configuration
1285 Synchronize RTC via network
1290 Lookup the IP of a hostname
1292 config CMD_LINK_LOCAL
1296 Acquire a network IP address using the link-local protocol
1303 Allow control of L2 Ethernet switch commands. These are supported
1304 by the vsc9953 Ethernet driver at present. Sub-commands allow
1305 operations such as enabling / disabling a port and
1306 viewing/maintaining the filtering database (FDB)
1312 Boot image via network using PXE protocol
1317 Wait for wake-on-lan Magic Packet
1321 menu "Misc commands"
1324 bool "Enable 'bmp' command"
1325 depends on LCD || DM_VIDEO || VIDEO
1327 This provides a way to obtain information about a BMP-format iamge
1328 and to display it. BMP (which presumably stands for BitMaP) is a
1329 file format defined by Microsoft which supports images of various
1330 depths, formats and compression methods. Headers on the file
1331 determine the formats used. This command can be used by first loading
1332 the image into RAM, then using this command to look at it or display
1335 config CMD_BOOTCOUNT
1337 depends on BOOTCOUNT_LIMIT
1339 Enable the bootcount command, which allows interrogation and
1340 reset of the bootcounter.
1343 bool "Enable board-specific commands"
1345 (deprecated: instead, please define a Kconfig option for each command)
1347 Some boards have board-specific commands which are only enabled
1348 during developemnt and need to be turned off for production. This
1349 option provides a way to control this. The commands that are enabled
1350 vary depending on the board.
1352 config CMD_BKOPS_ENABLE
1353 bool "mmc bkops enable"
1357 Enable command for setting manual background operations handshake
1358 on a eMMC device. The feature is optionally available on eMMC devices
1359 conforming to standard >= 4.41.
1361 config CMD_BLOCK_CACHE
1362 bool "blkcache - control and stats for block cache"
1363 depends on BLOCK_CACHE
1364 default y if BLOCK_CACHE
1366 Enable the blkcache command, which can be used to control the
1367 operation of the cache functions.
1368 This is most useful when fine-tuning the operation of the cache
1369 during development, but also allows the cache to be disabled when
1370 it might hurt performance (e.g. when using the ums command).
1373 bool "icache or dcache"
1375 Enable the "icache" and "dcache" commands
1377 config CMD_CONITRACE
1378 bool "conitrace - trace console input codes"
1380 Enable the 'conitrace' command which displays the codes received
1381 from the console input as hexadecimal numbers.
1384 bool "Enable the 'display' command, for character displays"
1386 (this needs porting to driver model)
1387 This enables the 'display' command which allows a string to be
1388 displayed on a simple board-specific display. Implement
1389 display_putc() to use it.
1395 Enable the 'led' command which allows for control of LEDs supported
1396 by the board. The LEDs can be listed with 'led list' and controlled
1397 with led on/off/togle/blink. Any LED drivers can be controlled with
1398 this command, e.g. led_gpio.
1404 Enable the 'date' command for getting/setting the time/date in RTC
1410 Run commands and summarize execution time.
1413 bool "gettime - read elapsed time"
1415 Enable the 'gettime' command which reads the elapsed time since
1416 U-Boot started running. This shows the time in seconds and
1417 milliseconds. See also the 'bootstage' command which provides more
1418 flexibility for boot timing.
1420 # TODO: rename to CMD_SLEEP
1425 Delay execution for some time
1428 bool "support for multiprocessor"
1430 This provides an option to brinup
1431 different processors in multiprocessor
1437 Access the system timer.
1443 This provides basic access to the U-Boot's sound support. The main
1444 feature is to play a beep.
1446 sound init - set up sound system
1447 sound play - play a sound
1453 This provides access to the QEMU firmware interface. The main
1454 feature is to allow easy loading of files passed to qemu-system
1455 via -kernel / -initrd
1457 source "cmd/mvebu/Kconfig"
1460 bool "terminal - provides a way to attach a serial terminal"
1462 Provides a 'cu'-like serial terminal command. This can be used to
1463 access other serial ports from the system console. The terminal
1464 is very simple with no special processing of characters. As with
1465 cu, you can press ~. (tilde followed by period) to exit.
1468 bool "uuid, guid - generation of unique IDs"
1471 This enables two commands:
1473 uuid - generate random Universally Unique Identifier
1474 guid - generate Globally Unique Identifier based on random UUID
1476 The two commands are very similar except for the endianness of the
1481 source "cmd/ti/Kconfig"
1483 config CMD_BOOTSTAGE
1484 bool "Enable the 'bootstage' command"
1485 depends on BOOTSTAGE
1487 Add a 'bootstage' command which supports printing a report
1488 and un/stashing of bootstage data.
1490 menu "Power commands"
1492 bool "Enable Driver Model PMIC command"
1495 This is the pmic command, based on a driver model pmic's API.
1496 Command features are unchanged:
1497 - list - list pmic devices
1498 - pmic dev <id> - show or [set] operating pmic device (NEW)
1499 - pmic dump - dump registers
1500 - pmic read address - read byte of register at address
1501 - pmic write address - write byte to register at address
1502 The only one change for this command is 'dev' subcommand.
1504 config CMD_REGULATOR
1505 bool "Enable Driver Model REGULATOR command"
1506 depends on DM_REGULATOR
1508 This command is based on driver model regulator's API.
1509 User interface features:
1510 - list - list regulator devices
1511 - regulator dev <id> - show or [set] operating regulator device
1512 - regulator info - print constraints info
1513 - regulator status - print operating status
1514 - regulator value <val] <-f> - print/[set] voltage value [uV]
1515 - regulator current <val> - print/[set] current value [uA]
1516 - regulator mode <id> - print/[set] operating mode id
1517 - regulator enable - enable the regulator output
1518 - regulator disable - disable the regulator output
1520 The '-f' (force) option can be used for set the value which exceeds
1521 the limits, which are found in device-tree and are kept in regulator's
1522 uclass platdata structure.
1526 menu "Security commands"
1528 bool "Enable the 'aes' command"
1531 This provides a means to encrypt and decrypt data using the AES
1532 (Advanced Encryption Standard). This algorithm uses a symetric key
1533 and is widely used as a streaming cipher. Different key lengths are
1534 supported by the algorithm but this command only supports 128 bits
1538 bool "Enable the 'blob' command"
1540 This is used with the Freescale secure boot mechanism.
1542 Freescale's SEC block has built-in Blob Protocol which provides
1543 a method for protecting user-defined data across system power
1544 cycles. SEC block protects data in a data structure called a Blob,
1545 which provides both confidentiality and integrity protection.
1547 Encapsulating data as a blob
1548 Each time that the Blob Protocol is used to protect data, a
1549 different randomly generated key is used to encrypt the data.
1550 This random key is itself encrypted using a key which is derived
1551 from SoC's non-volatile secret key and a 16 bit Key identifier.
1552 The resulting encrypted key along with encrypted data is called a
1553 blob. The non-volatile secure key is available for use only during
1556 During decapsulation, the reverse process is performed to get back
1560 blob enc - encapsulating data as a cryptgraphic blob
1561 blob dec - decapsulating cryptgraphic blob to get the data
1565 blob enc src dst len km
1567 Encapsulate and create blob of data $len bytes long
1568 at address $src and store the result at address $dst.
1569 $km is the 16 byte key modifier is also required for
1570 generation/use as key for cryptographic operation. Key
1571 modifier should be 16 byte long.
1573 blob dec src dst len km
1575 Decapsulate the blob of data at address $src and
1576 store result of $len byte at addr $dst.
1577 $km is the 16 byte key modifier is also required for
1578 generation/use as key for cryptographic operation. Key
1579 modifier should be 16 byte long.
1582 bool "Support 'hash' command"
1585 This provides a way to hash data in memory using various supported
1586 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1587 saved to memory or to an environment variable. It is also possible
1588 to verify a hash against data in memory.
1591 bool "Support the 'hvc' command"
1592 depends on ARM_SMCCC
1594 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1595 development and testing.
1598 bool "Support the 'smc' command"
1599 depends on ARM_SMCCC
1601 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1602 development and testing.
1608 Add -v option to verify data against a hash.
1618 bool "Enable the 'tpm' command"
1619 depends on TPM_V1 || TPM_V2
1620 select CMD_TPM_V1 if TPM_V1
1621 select CMD_TPM_V2 if TPM_V2
1623 This provides a means to talk to a TPM from the command line. A wide
1624 range of commands if provided - see 'tpm help' for details. The
1625 command requires a suitable TPM on your board and the correct driver
1631 bool "Enable the 'tpm test' command"
1634 This provides a a series of tests to confirm that the TPMv1.x is
1635 working correctly. The tests cover initialisation, non-volatile RAM,
1636 extend, global lock and checking that timing is within expectations.
1637 The tests pass correctly on Infineon TPMs but may need to be adjusted
1644 menu "Firmware commands"
1646 bool "Enable crosec command"
1650 Enable command-line access to the Chrome OS EC (Embedded
1651 Controller). This provides the 'crosec' command which has
1652 a number of sub-commands for performing EC tasks such as
1653 updating its flash, accessing a small saved context area
1654 and talking to the I2C bus behind the EC (if there is one).
1657 menu "Filesystem commands"
1659 bool "Enable the 'btrsubvol' command"
1662 This enables the 'btrsubvol' command to list subvolumes
1663 of a BTRFS filesystem. There are no special commands for
1664 listing BTRFS directories or loading BTRFS files - this
1665 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1666 when BTRFS is enabled (see FS_BTRFS).
1669 bool "Enable the 'cbfs' command"
1672 Define this to enable support for reading from a Coreboot
1673 filesystem. This is a ROM-based filesystem used for accessing files
1674 on systems that use coreboot as the first boot-loader and then load
1675 U-Boot to actually boot the Operating System. Available commands are
1676 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1679 bool "Enable the 'cramfs' command"
1680 depends on FS_CRAMFS
1682 This provides commands for dealing with CRAMFS (Compressed ROM
1683 filesystem). CRAMFS is useful when space is tight since files are
1684 compressed. Two commands are provided:
1686 cramfsls - lists files in a cramfs image
1687 cramfsload - loads a file from a cramfs image
1690 bool "ext2 command support"
1693 Enables EXT2 FS command
1696 bool "ext4 command support"
1699 Enables EXT4 FS command
1701 config CMD_EXT4_WRITE
1703 bool "ext4 write command support"
1706 Enables EXT4 FS write command
1709 bool "FAT command support"
1712 Support for the FAT fs
1714 config CMD_FS_GENERIC
1715 bool "filesystem commands"
1717 Enables filesystem commands (e.g. load, ls) that work for multiple
1721 bool "fsuuid command"
1723 Enables fsuuid command for filesystem UUID.
1726 bool "jffs2 command"
1729 Enables commands to support the JFFS2 (Journalling Flash File System
1730 version 2) filesystem. This enables fsload, ls and fsinfo which
1731 provide the ability to load files, list directories and obtain
1732 filesystem information.
1735 bool "MTD partition support"
1736 select MTD_DEVICE if (CMD_NAND || NAND)
1738 MTD partitioning tool support.
1739 It is strongly encouraged to avoid using this command
1740 anymore along with 'sf', 'nand', 'onenand'. One can still
1741 declare the partitions in the mtdparts environment variable
1742 but better use the MTD stack and the 'mtd' command instead.
1744 config MTDIDS_DEFAULT
1745 string "Default MTD IDs"
1746 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1748 Defines a default MTD IDs list for use with MTD partitions in the
1749 Linux MTD command line partitions format.
1751 config MTDPARTS_DEFAULT
1752 string "Default MTD partition scheme"
1753 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1755 Defines a default MTD partitioning scheme in the Linux MTD command
1756 line partitions format
1758 config CMD_MTDPARTS_SPREAD
1759 bool "Padd partition size to take account of bad blocks"
1760 depends on CMD_MTDPARTS
1762 This enables the 'spread' sub-command of the mtdparts command.
1763 This command will modify the existing mtdparts variable by increasing
1764 the size of the partitions such that 1) each partition's net size is
1765 at least as large as the size specified in the mtdparts variable and
1766 2) each partition starts on a good block.
1769 bool "reiser - Access to reiserfs filesystems"
1771 This provides two commands which operate on a resierfs filesystem,
1772 commonly used some years ago:
1774 reiserls - list files
1775 reiserload - load a file
1778 bool "yaffs2 - Access of YAFFS2 filesystem"
1782 This provides commands for accessing a YAFFS2 filesystem. Yet
1783 Another Flash Filesystem 2 is a filesystem designed specifically
1784 for NAND flash. It incorporates bad-block management and ensures
1785 that device writes are sequential regardless of filesystem
1789 bool "zfs - Access of ZFS filesystem"
1791 This provides commands to accessing a ZFS filesystem, commonly used
1792 on Solaris systems. Two sub-commands are provided:
1794 zfsls - list files in a directory
1795 zfsload - load a file
1797 See doc/README.zfs for more details.
1801 menu "Debug commands"
1806 The bedbug (emBEDded deBUGger) command provides debugging features
1807 for some PowerPC processors. For details please see the
1808 docuemntation in doc/README.beddbug
1811 bool "diag - Board diagnostics"
1813 This command provides access to board diagnostic tests. These are
1814 called Power-on Self Tests (POST). The command allows listing of
1815 available tests and running either all the tests, or specific tests
1819 bool "irq - Show information about interrupts"
1820 depends on !ARM && !MIPS && !SH
1822 This enables two commands:
1824 interrupts - enable or disable interrupts
1825 irqinfo - print device-specific interrupt information
1828 bool "kgdb - Allow debugging of U-Boot with gdb"
1831 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1832 over a serial link for debugging purposes. This allows
1833 single-stepping, inspecting variables, etc. This is supported only
1834 on PowerPC at present.
1837 bool "log - Generation, control and access to logging"
1840 This provides access to logging features. It allows the output of
1841 log data to be controlled to a limited extent (setting up the default
1842 maximum log level for emitting of records). It also provides access
1843 to a command used for testing the log system.
1846 bool "trace - Support tracing of function calls and timing"
1848 Enables a command to control using of function tracing within
1849 U-Boot. This allows recording of call traces including timing
1850 information. The command can write data to memory for exporting
1851 for analsys (e.g. using bootchart). See doc/README.trace for full
1855 bool "avb - Android Verified Boot 2.0 operations"
1856 depends on AVB_VERIFY
1859 Enables a "avb" command to perform verification of partitions using
1860 Android Verified Boot 2.0 functionality. It includes such subcommands:
1861 avb init - initialize avb2 subsystem
1862 avb read_rb - read rollback index
1863 avb write_rb - write rollback index
1864 avb is_unlocked - check device lock state
1865 avb get_uuid - read and print uuid of a partition
1866 avb read_part - read data from partition
1867 avb read_part_hex - read data from partition and output to stdout
1868 avb write_part - write data to partition
1869 avb verify - run full verification chain
1873 tristate "Enable UBI - Unsorted block images commands"
1877 UBI is a software layer above MTD layer which admits use of LVM-like
1878 logical volumes on top of MTD devices, hides some complexities of
1879 flash chips like wear and bad blocks and provides some other useful
1880 capabilities. Please, consult the MTD web site for more details
1881 (www.linux-mtd.infradead.org). Activate this option if you want
1882 to use U-Boot UBI commands.
1883 It is also strongly encouraged to also enable CONFIG_MTD to get full
1887 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1889 default y if CMD_UBI
1893 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob