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 && !CPU_V7M && !SANDBOX
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
423 config CMD_NVEDIT_EFI
424 bool "env [set|print] -e - set/print UEFI variables"
425 depends on EFI_LOADER
429 UEFI variables are encoded as some form of U-Boot variables.
430 If enabled, we are allowed to set/print UEFI variables using
431 "env" command with "-e" option without knowing details.
435 menu "Memory commands"
440 Compute binary operations (xor, or, and) of byte arrays of arbitrary
441 size from memory and store the result in memory or the environment.
454 Add -v option to verify data against a crc32 checksum.
457 bool "eeprom - EEPROM subsystem"
458 depends on !DM_I2C || DM_I2C_COMPAT
460 (deprecated, needs conversion to driver model)
461 Provides commands to read and write EEPROM (Electrically Erasable
462 Programmable Read Only Memory) chips that are connected over an
465 config CMD_EEPROM_LAYOUT
466 bool "Enable layout-aware eeprom commands"
467 depends on CMD_EEPROM
469 (deprecated, needs conversion to driver model)
470 When enabled, additional eeprom sub-commands become available.
472 eeprom print - prints the contents of the eeprom in a human-readable
473 way (eeprom layout fields, and data formatted to be fit for human
476 eeprom update - allows user to update eeprom fields by specifying
477 the field name, and providing the new data in a human readable format
478 (same format as displayed by the eeprom print command).
480 Both commands can either auto detect the layout, or be told which
484 __weak int parse_layout_version(char *str)
485 - override to provide your own layout name parsing
486 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
488 - override to setup the layout metadata based on the version
489 __weak int eeprom_layout_detect(unsigned char *data)
490 - override to provide your own algorithm for detecting layout
493 - contains various printing and updating functions for common
494 types of eeprom fields. Can be used for defining
497 config EEPROM_LAYOUT_HELP_STRING
498 string "Tells user what layout names are supported"
499 depends on CMD_EEPROM_LAYOUT
500 default "<not defined>"
502 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
508 Infinite write loop on address range
515 Compute MD5 checksum.
520 depends on CMD_MD5SUM
522 Add -v option to verify data against an MD5 checksum.
527 Display memory information.
530 bool "md, mm, nm, mw, cp, cmp, base, loop"
535 mm - memory modify (auto-incrementing address)
536 nm - memory modify (constant address)
537 mw - memory write (fill)
540 base - print or set address offset
541 loop - initialize loop on address range
546 Simple RAM read/write test.
550 config SYS_ALT_MEMTEST
551 bool "Alternative test"
553 Use a more complete alternative memory test.
560 mdc - memory display cyclic
561 mwc - memory write cyclic
567 Compute SHA1 checksum.
569 config SHA1SUM_VERIFY
571 depends on CMD_SHA1SUM
573 Add -v option to verify data against a SHA1 checksum.
576 bool "strings - display strings in memory"
578 This works similarly to the Unix 'strings' command except that it
579 works with a memory range. String of printable characters found
580 within the range are displayed. The minimum number of characters
581 for a sequence to be considered a string can be provided.
585 menu "Compression commands"
589 default y if CMD_BOOTI
592 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
597 default y if CMD_BOOTI
599 Uncompress a zip-compressed memory region.
604 Compress a memory region with zlib deflate method.
608 menu "Device access commands"
611 #depends on FLASH_CFI_DRIVER
614 ARM Ltd reference designs flash partition access
617 bool "adc - Access Analog to Digital Converters info and data"
621 Shows ADC device info and permit printing one-shot analog converted
622 data from a named Analog to Digital Converter.
625 bool "bind/unbind - Bind or unbind a device to/from a driver"
628 Bind or unbind a device to/from a driver from the command line.
629 This is useful in situations where a device may be handled by several
630 drivers. For example, this can be used to bind a UDC to the usb ether
631 gadget driver from the command line.
634 bool "clk - Show clock frequencies"
637 Shows clock frequences by calling a sock_clk_dump() hook function.
638 This is depreated in favour of using the CLK uclass and accessing
639 clock values from associated drivers. However currently no command
643 bool "demo - Demonstration commands for driver model"
646 Provides a 'demo' command which can be used to play around with
647 driver model. To use this properly you will need to enable one or
648 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
649 Otherwise you will always get an empty list of devices. The demo
650 devices are defined in the sandbox device tree, so the easiest
651 option is to use sandbox and pass the -d point to sandbox's
658 Enables the command "dfu" which is used to have U-Boot create a DFU
659 class device via USB. This command requires that the "dfu_alt_info"
660 environment variable be set and define the alt settings to expose to
664 bool "dm - Access to driver model information"
667 Provides access to driver model data structures and information,
668 such as a list of devices, list of uclasses and the state of each
669 device (e.g. activated). This is not required for operation, but
670 can be useful to see the state of driver model for debugging or
674 bool "fastboot - Android fastboot support"
677 This enables the command "fastboot" which enables the Android
678 fastboot mode for the platform. Fastboot is a protocol for
679 downloading images, flashing and device control used on
680 Android devices. Fastboot requires either the network stack
681 enabled or support for acting as a USB device.
683 See doc/README.android-fastboot for more information.
686 bool "fdcboot - Boot from floppy device"
688 The 'fdtboot' command allows booting an image from a floppy disk.
691 bool "flinfo, erase, protect"
695 flinfo - print FLASH memory information
697 protect - enable or disable FLASH write protection
706 config CMD_FPGA_LOADBP
707 bool "fpga loadbp - load partial bitstream (Xilinx only)"
710 Supports loading an FPGA device from a bitstream buffer containing
713 config CMD_FPGA_LOADFS
714 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
717 Supports loading an FPGA device from a FAT filesystem.
719 config CMD_FPGA_LOADMK
720 bool "fpga loadmk - load bitstream from image"
723 Supports loading an FPGA device from a image generated by mkimage.
725 config CMD_FPGA_LOADP
726 bool "fpga loadp - load partial bitstream"
729 Supports loading an FPGA device from a bitstream buffer containing
732 config CMD_FPGA_LOAD_SECURE
733 bool "fpga loads - loads secure bitstreams (Xilinx only)"
736 Enables the fpga loads command which is used to load secure
737 (authenticated or encrypted or both) bitstreams on to FPGA.
740 bool "fpgad - dump FPGA registers"
742 (legacy, needs conversion to driver model)
743 Provides a way to dump FPGA registers by calling the board-specific
744 fpga_get_reg() function. This functions similarly to the 'md'
748 bool "fuse - support for the fuse subssystem"
750 (deprecated - needs conversion to driver model)
751 This allows reading, sensing, programming or overriding fuses
752 which control the behaviour of the device. The command uses the
761 bool "GPT (GUID Partition Table) command"
763 select HAVE_BLOCK_DEVICE
764 select PARTITION_UUIDS
767 Enable the 'gpt' command to ready and write GPT style partition
771 bool "GPT Random UUID generation"
774 Enable the generation of partitions with random UUIDs if none
777 config CMD_GPT_RENAME
778 bool "GPT partition renaming commands"
781 Enables the 'gpt' command to interchange names on two GPT
782 partitions via the 'gpt swap' command or to rename single
783 partitions via the 'rename' command.
786 bool "ide - Support for IDE drivers"
789 Provides an 'ide' command which allows accessing the IDE drive,
790 reseting the IDE interface, printing the partition table and
791 geting device info. It also enables the 'diskboot' command which
792 permits booting from an IDE drive.
795 bool "io - Support for performing I/O accesses"
797 Provides an 'iod' command to display I/O space and an 'iow' command
798 to write values to the I/O space. This can be useful for manually
799 checking the state of devices during boot when debugging device
803 bool "iotrace - Support for tracing I/O activity"
805 Provides an 'iotrace' command which supports recording I/O reads and
806 writes in a trace buffer in memory . It also maintains a checksum
807 of the trace records (even if space is exhausted) so that the
808 sequence of I/O accesses can be verified.
810 When debugging drivers it is useful to see what I/O accesses were
811 done and in what order.
813 Even if the individual accesses are of little interest it can be
814 useful to verify that the access pattern is consistent each time
815 an operation is performed. In this case a checksum can be used to
816 characterise the operation of a driver. The checksum can be compared
817 across different runs of the operation to verify that the driver is
820 In particular, when performing major refactoring of the driver, where
821 the access pattern should not change, the checksum provides assurance
822 that the refactoring work has not broken the driver.
824 This works by sneaking into the io.h heder for an architecture and
825 redirecting I/O accesses through iotrace's tracing mechanism.
827 For now no commands are provided to examine the trace buffer. The
828 format is fairly simple, so 'md' is a reasonable substitute.
830 Note: The checksum feature is only useful for I/O regions where the
831 contents do not change outside of software control. Where this is not
832 suitable you can fall back to manually comparing the addresses. It
833 might be useful to enhance tracing to only checksum the accesses and
834 not the data read/written.
844 bool "w1 - Support for Dallas 1-Wire protocol"
846 Dallas 1-wire protocol support
852 Load a binary file over serial line.
858 Load an S-Record file over serial line
863 MMC memory mapped support.
866 bool "Enable support for RPMB in the mmc command"
869 Enable the commands for reading, writing and programming the
870 key for the Replay Protection Memory Block partition in eMMC.
872 config CMD_MMC_SWRITE
874 depends on CMD_MMC && MMC_WRITE
877 Enable support for the "mmc swrite" command to write Android sparse
882 select MTD_PARTITIONS
884 MTD commands support.
888 default y if NAND_SUNXI
893 config CMD_NAND_TRIMFFS
894 bool "nand write.trimffs"
895 default y if ARCH_SUNXI
897 Allows one to skip empty pages when flashing something on a NAND.
899 config CMD_NAND_LOCK_UNLOCK
900 bool "nand lock/unlock"
902 NAND locking support.
904 config CMD_NAND_TORTURE
907 NAND torture support.
916 NVM Express device support
919 bool "mmc_spi - Set up MMC SPI device"
921 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
922 Peripheral Interface) device. The device provides a means of
923 accessing an MMC device via SPI using a single data line, limited
924 to 20MHz. It is useful since it reduces the amount of protocol code
928 bool "onenand - access to onenand device"
930 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
931 various useful features. This command allows reading, writing,
932 and erasing blocks. It allso provides a way to show and change
933 bad blocks, and test the device.
938 Enable the 'osd' command which allows to query information from and
939 write text data to a on-screen display (OSD) device; a virtual device
940 associated with a display capable of displaying a text overlay on the
941 display it's associated with..
945 select HAVE_BLOCK_DEVICE
946 select PARTITION_UUIDS
948 Read and display information about the partition table on
952 bool "pci - Access PCI devices"
954 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
955 used on some devices to allow the CPU to communicate with its
956 peripherals. Sub-commands allow bus enumeration, displaying and
957 changing configuration space and a few other features.
960 bool "pinit - Set up PCMCIA device"
962 Provides a means to initialise a PCMCIA (Personal Computer Memory
963 Card International Association) device. This is an old standard from
964 about 1990. These devices are typically removable memory or network
965 cards using a standard 68-pin connector.
968 bool "pinmux - show pins muxing"
971 Parse all available pin-controllers and show pins muxing. This
972 is useful for debug purpoer to check the pin muxing and to know if
973 a pin is configured as a GPIO or as an alternate function.
978 Poweroff/Shutdown the system
981 bool "read - Read binary data from a partition"
983 Provides low-level access to the data in a partition.
985 config CMD_REMOTEPROC
987 depends on REMOTEPROC
989 Support for Remote Processor control
992 bool "sata - Access SATA subsystem"
995 SATA (Serial Advanced Technology Attachment) is a serial bus
996 standard for connecting to hard drives and other storage devices.
997 This command provides information about attached devices and allows
998 reading, writing and other operations.
1000 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1001 Attachment, where AT refers to an IBM AT (Advanced Technology)
1002 computer released in 1984.
1005 bool "saves - Save a file over serial in S-Record format"
1007 Provides a way to save a binary file using the Motorola S-Record
1008 format over the serial line.
1011 bool "scsi - Access to SCSI devices"
1014 This provides a 'scsi' command which provides access to SCSI (Small
1015 Computer System Interface) devices. The command provides a way to
1016 scan the bus, reset the bus, read and write data and get information
1020 bool "sdram - Print SDRAM configuration information"
1022 Provides information about attached SDRAM. This assumed that the
1023 SDRAM has an EEPROM with information that can be read using the
1024 I2C bus. This is only available on some boards.
1032 bool "sf test - Allow testing of SPI flash"
1034 Provides a way to test that SPI flash is working correctly. The
1035 test is destructive, in that an area of SPI flash must be provided
1036 for the test to use. Performance information is also provided,
1037 measuring the performance of reading, writing and erasing in
1038 Mbps (Million Bits Per Second). This value should approximately
1039 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1040 everything is working properly.
1045 SPI utility command.
1048 bool "tsi148 - Command to access tsi148 device"
1050 This provides various sub-commands to initialise and configure the
1051 Turndra tsi148 device. See the command help for full details.
1054 bool "universe - Command to set up the Turndra Universe controller"
1056 This allows setting up the VMEbus provided by this controller.
1057 See the command help for full details.
1061 select HAVE_BLOCK_DEVICE
1067 select USB_FUNCTION_SDP
1069 Enables the command "sdp" which is used to have U-Boot emulating the
1070 Serial Download Protocol (SDP) via USB.
1074 depends on USB_FUNCTION_ROCKUSB
1076 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1077 read/write info, image to/from devices. This enable rockusb command
1078 support to communication with rockusb device. for more detail about
1079 this command, please read doc/README.rockusb.
1081 config CMD_USB_MASS_STORAGE
1082 bool "UMS usb mass storage"
1083 select USB_FUNCTION_MASS_STORAGE
1085 USB mass storage support
1092 VirtIO block device support
1098 Enable the command "axi" for accessing AXI (Advanced eXtensible
1099 Interface) busses, a on-chip interconnect specification for managing
1100 functional blocks in SoC designs, which is also often used in designs
1101 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1105 menu "Shell scripting commands"
1111 Echo args to console
1117 Return true/false on integer compare.
1123 Run script from memory
1129 Evaluate boolean and math expressions and store the result in an env
1131 Also supports loading the value at a memory location into a variable.
1132 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1139 bool "Network commands"
1149 bootp - boot image via network using BOOTP/TFTP protocol
1153 depends on CMD_BOOTP
1155 Boot image via network using DHCP/TFTP protocol
1157 config BOOTP_BOOTPATH
1158 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1160 depends on CMD_BOOTP
1162 Even though the config is called BOOTP_BOOTPATH, it stores the
1163 path in the variable 'rootpath'.
1166 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1168 depends on CMD_BOOTP
1170 The primary DNS server is stored as 'dnsip'. If two servers are
1171 returned, you must set BOOTP_DNS2 to store that second server IP
1175 bool "Store 'dnsip2' from BOOTP/DHCP server"
1176 depends on BOOTP_DNS
1178 If a DHCP client requests the DNS server IP from a DHCP server,
1179 it is possible that more than one DNS serverip is offered to the
1180 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1181 server IP will be stored in the additional environment
1182 variable "dnsip2". The first DNS serverip is always
1183 stored in the variable "dnsip", when BOOTP_DNS is defined.
1185 config BOOTP_GATEWAY
1186 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1188 depends on CMD_BOOTP
1190 config BOOTP_HOSTNAME
1191 bool "Request & store 'hostname' from BOOTP/DHCP server"
1193 depends on CMD_BOOTP
1195 The name may or may not be qualified with the local domain name.
1197 config BOOTP_PREFER_SERVERIP
1198 bool "serverip variable takes precedent over DHCP server IP."
1199 depends on CMD_BOOTP
1201 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1203 With this option enabled, the 'serverip' variable in the environment
1204 takes precedence over DHCP server IP and will only be set by the DHCP
1205 server if not already set in the environment.
1207 config BOOTP_SUBNETMASK
1208 bool "Request & store 'netmask' from BOOTP/DHCP server"
1210 depends on CMD_BOOTP
1212 config BOOTP_NTPSERVER
1213 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1214 depends on CMD_BOOTP
1217 bool "Send PXE client arch to BOOTP/DHCP server"
1219 depends on CMD_BOOTP && CMD_PXE
1221 Supported for ARM, ARM64, and x86 for now.
1223 config BOOTP_PXE_CLIENTARCH
1225 depends on BOOTP_PXE
1226 default 0x16 if ARM64
1230 config BOOTP_VCI_STRING
1232 depends on CMD_BOOTP
1233 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1234 default "U-Boot.armv8" if ARM64
1235 default "U-Boot.arm" if ARM
1242 tftpboot - boot image via network using TFTP protocol
1246 depends on CMD_TFTPBOOT
1248 TFTP put command, for uploading files to a server
1252 depends on CMD_TFTPBOOT
1254 Act as a TFTP server and boot the first received file
1256 config NET_TFTP_VARS
1257 bool "Control TFTP timeout and count through environment"
1258 depends on CMD_TFTPBOOT
1261 If set, allows controlling the TFTP timeout through the
1262 environment variable tftptimeout, and the TFTP maximum
1263 timeout count through the variable tftptimeoutcountmax.
1264 If unset, timeout and maximum are hard-defined as 1 second
1265 and 10 timouts per TFTP transfer.
1270 Boot image via network using RARP/TFTP protocol
1276 Boot image via network using NFS protocol.
1281 Enable MII utility commands.
1286 Send ICMP ECHO_REQUEST to network host
1291 Perform CDP network configuration
1296 Synchronize RTC via network
1301 Lookup the IP of a hostname
1303 config CMD_LINK_LOCAL
1307 Acquire a network IP address using the link-local protocol
1314 Allow control of L2 Ethernet switch commands. These are supported
1315 by the vsc9953 Ethernet driver at present. Sub-commands allow
1316 operations such as enabling / disabling a port and
1317 viewing/maintaining the filtering database (FDB)
1323 Boot image via network using PXE protocol
1328 Wait for wake-on-lan Magic Packet
1332 menu "Misc commands"
1335 bool "Enable 'bmp' command"
1336 depends on LCD || DM_VIDEO || VIDEO
1338 This provides a way to obtain information about a BMP-format iamge
1339 and to display it. BMP (which presumably stands for BitMaP) is a
1340 file format defined by Microsoft which supports images of various
1341 depths, formats and compression methods. Headers on the file
1342 determine the formats used. This command can be used by first loading
1343 the image into RAM, then using this command to look at it or display
1346 config CMD_BOOTCOUNT
1348 depends on BOOTCOUNT_LIMIT
1350 Enable the bootcount command, which allows interrogation and
1351 reset of the bootcounter.
1354 bool "Enable board-specific commands"
1356 (deprecated: instead, please define a Kconfig option for each command)
1358 Some boards have board-specific commands which are only enabled
1359 during developemnt and need to be turned off for production. This
1360 option provides a way to control this. The commands that are enabled
1361 vary depending on the board.
1363 config CMD_BKOPS_ENABLE
1364 bool "mmc bkops enable"
1368 Enable command for setting manual background operations handshake
1369 on a eMMC device. The feature is optionally available on eMMC devices
1370 conforming to standard >= 4.41.
1372 config CMD_BLOCK_CACHE
1373 bool "blkcache - control and stats for block cache"
1374 depends on BLOCK_CACHE
1375 default y if BLOCK_CACHE
1377 Enable the blkcache command, which can be used to control the
1378 operation of the cache functions.
1379 This is most useful when fine-tuning the operation of the cache
1380 during development, but also allows the cache to be disabled when
1381 it might hurt performance (e.g. when using the ums command).
1384 bool "icache or dcache"
1386 Enable the "icache" and "dcache" commands
1388 config CMD_CONITRACE
1389 bool "conitrace - trace console input codes"
1391 Enable the 'conitrace' command which displays the codes received
1392 from the console input as hexadecimal numbers.
1395 bool "Enable clear screen command 'cls'"
1396 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1399 Enable the 'cls' command which clears the screen contents
1400 on video frame buffer.
1403 bool "Enable the 'display' command, for character displays"
1405 (this needs porting to driver model)
1406 This enables the 'display' command which allows a string to be
1407 displayed on a simple board-specific display. Implement
1408 display_putc() to use it.
1411 bool "efidebug - display/configure UEFI environment"
1412 depends on EFI_LOADER
1415 Enable the 'efidebug' command which provides a subset of UEFI
1416 shell utility with simplified functionality. It will be useful
1417 particularly for managing boot parameters as well as examining
1418 various EFI status for debugging.
1425 Enable the 'led' command which allows for control of LEDs supported
1426 by the board. The LEDs can be listed with 'led list' and controlled
1427 with led on/off/togle/blink. Any LED drivers can be controlled with
1428 this command, e.g. led_gpio.
1434 Enable the 'date' command for getting/setting the time/date in RTC
1440 Run commands and summarize execution time.
1443 bool "gettime - read elapsed time"
1445 Enable the 'gettime' command which reads the elapsed time since
1446 U-Boot started running. This shows the time in seconds and
1447 milliseconds. See also the 'bootstage' command which provides more
1448 flexibility for boot timing.
1450 # TODO: rename to CMD_SLEEP
1455 Delay execution for some time
1458 bool "support for multiprocessor"
1460 This provides an option to brinup
1461 different processors in multiprocessor
1467 Access the system timer.
1473 This provides basic access to the U-Boot's sound support. The main
1474 feature is to play a beep.
1476 sound init - set up sound system
1477 sound play - play a sound
1483 This provides access to the QEMU firmware interface. The main
1484 feature is to allow easy loading of files passed to qemu-system
1485 via -kernel / -initrd
1487 source "cmd/mvebu/Kconfig"
1490 bool "terminal - provides a way to attach a serial terminal"
1492 Provides a 'cu'-like serial terminal command. This can be used to
1493 access other serial ports from the system console. The terminal
1494 is very simple with no special processing of characters. As with
1495 cu, you can press ~. (tilde followed by period) to exit.
1498 bool "uuid, guid - generation of unique IDs"
1501 This enables two commands:
1503 uuid - generate random Universally Unique Identifier
1504 guid - generate Globally Unique Identifier based on random UUID
1506 The two commands are very similar except for the endianness of the
1511 source "cmd/ti/Kconfig"
1513 config CMD_BOOTSTAGE
1514 bool "Enable the 'bootstage' command"
1515 depends on BOOTSTAGE
1517 Add a 'bootstage' command which supports printing a report
1518 and un/stashing of bootstage data.
1520 menu "Power commands"
1522 bool "Enable Driver Model PMIC command"
1525 This is the pmic command, based on a driver model pmic's API.
1526 Command features are unchanged:
1527 - list - list pmic devices
1528 - pmic dev <id> - show or [set] operating pmic device (NEW)
1529 - pmic dump - dump registers
1530 - pmic read address - read byte of register at address
1531 - pmic write address - write byte to register at address
1532 The only one change for this command is 'dev' subcommand.
1534 config CMD_REGULATOR
1535 bool "Enable Driver Model REGULATOR command"
1536 depends on DM_REGULATOR
1538 This command is based on driver model regulator's API.
1539 User interface features:
1540 - list - list regulator devices
1541 - regulator dev <id> - show or [set] operating regulator device
1542 - regulator info - print constraints info
1543 - regulator status - print operating status
1544 - regulator value <val] <-f> - print/[set] voltage value [uV]
1545 - regulator current <val> - print/[set] current value [uA]
1546 - regulator mode <id> - print/[set] operating mode id
1547 - regulator enable - enable the regulator output
1548 - regulator disable - disable the regulator output
1550 The '-f' (force) option can be used for set the value which exceeds
1551 the limits, which are found in device-tree and are kept in regulator's
1552 uclass platdata structure.
1556 menu "Security commands"
1558 bool "Enable the 'aes' command"
1561 This provides a means to encrypt and decrypt data using the AES
1562 (Advanced Encryption Standard). This algorithm uses a symetric key
1563 and is widely used as a streaming cipher. Different key lengths are
1564 supported by the algorithm but this command only supports 128 bits
1568 bool "Enable the 'blob' command"
1570 This is used with the Freescale secure boot mechanism.
1572 Freescale's SEC block has built-in Blob Protocol which provides
1573 a method for protecting user-defined data across system power
1574 cycles. SEC block protects data in a data structure called a Blob,
1575 which provides both confidentiality and integrity protection.
1577 Encapsulating data as a blob
1578 Each time that the Blob Protocol is used to protect data, a
1579 different randomly generated key is used to encrypt the data.
1580 This random key is itself encrypted using a key which is derived
1581 from SoC's non-volatile secret key and a 16 bit Key identifier.
1582 The resulting encrypted key along with encrypted data is called a
1583 blob. The non-volatile secure key is available for use only during
1586 During decapsulation, the reverse process is performed to get back
1590 blob enc - encapsulating data as a cryptgraphic blob
1591 blob dec - decapsulating cryptgraphic blob to get the data
1595 blob enc src dst len km
1597 Encapsulate and create blob of data $len bytes long
1598 at address $src and store the result at address $dst.
1599 $km is the 16 byte key modifier is also required for
1600 generation/use as key for cryptographic operation. Key
1601 modifier should be 16 byte long.
1603 blob dec src dst len km
1605 Decapsulate the blob of data at address $src and
1606 store result of $len byte at addr $dst.
1607 $km is the 16 byte key modifier is also required for
1608 generation/use as key for cryptographic operation. Key
1609 modifier should be 16 byte long.
1612 bool "Support 'hash' command"
1615 This provides a way to hash data in memory using various supported
1616 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1617 saved to memory or to an environment variable. It is also possible
1618 to verify a hash against data in memory.
1621 bool "Support the 'hvc' command"
1622 depends on ARM_SMCCC
1624 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1625 development and testing.
1628 bool "Support the 'smc' command"
1629 depends on ARM_SMCCC
1631 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1632 development and testing.
1638 Add -v option to verify data against a hash.
1648 bool "Enable the 'tpm' command"
1649 depends on TPM_V1 || TPM_V2
1650 select CMD_TPM_V1 if TPM_V1
1651 select CMD_TPM_V2 if TPM_V2
1653 This provides a means to talk to a TPM from the command line. A wide
1654 range of commands if provided - see 'tpm help' for details. The
1655 command requires a suitable TPM on your board and the correct driver
1661 bool "Enable the 'tpm test' command"
1664 This provides a a series of tests to confirm that the TPMv1.x is
1665 working correctly. The tests cover initialisation, non-volatile RAM,
1666 extend, global lock and checking that timing is within expectations.
1667 The tests pass correctly on Infineon TPMs but may need to be adjusted
1674 menu "Firmware commands"
1676 bool "Enable crosec command"
1680 Enable command-line access to the Chrome OS EC (Embedded
1681 Controller). This provides the 'crosec' command which has
1682 a number of sub-commands for performing EC tasks such as
1683 updating its flash, accessing a small saved context area
1684 and talking to the I2C bus behind the EC (if there is one).
1687 menu "Filesystem commands"
1689 bool "Enable the 'btrsubvol' command"
1692 This enables the 'btrsubvol' command to list subvolumes
1693 of a BTRFS filesystem. There are no special commands for
1694 listing BTRFS directories or loading BTRFS files - this
1695 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1696 when BTRFS is enabled (see FS_BTRFS).
1699 bool "Enable the 'cbfs' command"
1702 Define this to enable support for reading from a Coreboot
1703 filesystem. This is a ROM-based filesystem used for accessing files
1704 on systems that use coreboot as the first boot-loader and then load
1705 U-Boot to actually boot the Operating System. Available commands are
1706 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1709 bool "Enable the 'cramfs' command"
1710 depends on FS_CRAMFS
1712 This provides commands for dealing with CRAMFS (Compressed ROM
1713 filesystem). CRAMFS is useful when space is tight since files are
1714 compressed. Two commands are provided:
1716 cramfsls - lists files in a cramfs image
1717 cramfsload - loads a file from a cramfs image
1720 bool "ext2 command support"
1723 Enables EXT2 FS command
1726 bool "ext4 command support"
1729 Enables EXT4 FS command
1731 config CMD_EXT4_WRITE
1733 bool "ext4 write command support"
1736 Enables EXT4 FS write command
1739 bool "FAT command support"
1742 Support for the FAT fs
1744 config CMD_FS_GENERIC
1745 bool "filesystem commands"
1747 Enables filesystem commands (e.g. load, ls) that work for multiple
1751 bool "fsuuid command"
1753 Enables fsuuid command for filesystem UUID.
1756 bool "jffs2 command"
1759 Enables commands to support the JFFS2 (Journalling Flash File System
1760 version 2) filesystem. This enables fsload, ls and fsinfo which
1761 provide the ability to load files, list directories and obtain
1762 filesystem information.
1765 bool "MTD partition support"
1766 select MTD_DEVICE if (CMD_NAND || NAND)
1768 MTD partitioning tool support.
1769 It is strongly encouraged to avoid using this command
1770 anymore along with 'sf', 'nand', 'onenand'. One can still
1771 declare the partitions in the mtdparts environment variable
1772 but better use the MTD stack and the 'mtd' command instead.
1774 config MTDIDS_DEFAULT
1775 string "Default MTD IDs"
1776 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1778 Defines a default MTD IDs list for use with MTD partitions in the
1779 Linux MTD command line partitions format.
1781 config MTDPARTS_DEFAULT
1782 string "Default MTD partition scheme"
1783 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1785 Defines a default MTD partitioning scheme in the Linux MTD command
1786 line partitions format
1788 config CMD_MTDPARTS_SPREAD
1789 bool "Padd partition size to take account of bad blocks"
1790 depends on CMD_MTDPARTS
1792 This enables the 'spread' sub-command of the mtdparts command.
1793 This command will modify the existing mtdparts variable by increasing
1794 the size of the partitions such that 1) each partition's net size is
1795 at least as large as the size specified in the mtdparts variable and
1796 2) each partition starts on a good block.
1799 bool "reiser - Access to reiserfs filesystems"
1801 This provides two commands which operate on a resierfs filesystem,
1802 commonly used some years ago:
1804 reiserls - list files
1805 reiserload - load a file
1808 bool "yaffs2 - Access of YAFFS2 filesystem"
1812 This provides commands for accessing a YAFFS2 filesystem. Yet
1813 Another Flash Filesystem 2 is a filesystem designed specifically
1814 for NAND flash. It incorporates bad-block management and ensures
1815 that device writes are sequential regardless of filesystem
1819 bool "zfs - Access of ZFS filesystem"
1821 This provides commands to accessing a ZFS filesystem, commonly used
1822 on Solaris systems. Two sub-commands are provided:
1824 zfsls - list files in a directory
1825 zfsload - load a file
1827 See doc/README.zfs for more details.
1831 menu "Debug commands"
1836 The bedbug (emBEDded deBUGger) command provides debugging features
1837 for some PowerPC processors. For details please see the
1838 docuemntation in doc/README.beddbug
1841 bool "diag - Board diagnostics"
1843 This command provides access to board diagnostic tests. These are
1844 called Power-on Self Tests (POST). The command allows listing of
1845 available tests and running either all the tests, or specific tests
1849 bool "irq - Show information about interrupts"
1850 depends on !ARM && !MIPS && !SH
1852 This enables two commands:
1854 interrupts - enable or disable interrupts
1855 irqinfo - print device-specific interrupt information
1858 bool "kgdb - Allow debugging of U-Boot with gdb"
1861 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1862 over a serial link for debugging purposes. This allows
1863 single-stepping, inspecting variables, etc. This is supported only
1864 on PowerPC at present.
1867 bool "log - Generation, control and access to logging"
1870 This provides access to logging features. It allows the output of
1871 log data to be controlled to a limited extent (setting up the default
1872 maximum log level for emitting of records). It also provides access
1873 to a command used for testing the log system.
1876 bool "trace - Support tracing of function calls and timing"
1878 Enables a command to control using of function tracing within
1879 U-Boot. This allows recording of call traces including timing
1880 information. The command can write data to memory for exporting
1881 for analsys (e.g. using bootchart). See doc/README.trace for full
1885 bool "avb - Android Verified Boot 2.0 operations"
1886 depends on AVB_VERIFY
1889 Enables a "avb" command to perform verification of partitions using
1890 Android Verified Boot 2.0 functionality. It includes such subcommands:
1891 avb init - initialize avb2 subsystem
1892 avb read_rb - read rollback index
1893 avb write_rb - write rollback index
1894 avb is_unlocked - check device lock state
1895 avb get_uuid - read and print uuid of a partition
1896 avb read_part - read data from partition
1897 avb read_part_hex - read data from partition and output to stdout
1898 avb write_part - write data to partition
1899 avb verify - run full verification chain
1903 tristate "Enable UBI - Unsorted block images commands"
1907 UBI is a software layer above MTD layer which admits use of LVM-like
1908 logical volumes on top of MTD devices, hides some complexities of
1909 flash chips like wear and bad blocks and provides some other useful
1910 capabilities. Please, consult the MTD web site for more details
1911 (www.linux-mtd.infradead.org). Activate this option if you want
1912 to use U-Boot UBI commands.
1913 It is also strongly encouraged to also enable CONFIG_MTD to get full
1917 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1919 default y if CMD_UBI
1923 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob