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"
459 (deprecated, needs conversion to driver model)
460 Provides commands to read and write EEPROM (Electrically Erasable
461 Programmable Read Only Memory) chips that are connected over an
464 config CMD_EEPROM_LAYOUT
465 bool "Enable layout-aware eeprom commands"
466 depends on CMD_EEPROM
468 (deprecated, needs conversion to driver model)
469 When enabled, additional eeprom sub-commands become available.
471 eeprom print - prints the contents of the eeprom in a human-readable
472 way (eeprom layout fields, and data formatted to be fit for human
475 eeprom update - allows user to update eeprom fields by specifying
476 the field name, and providing the new data in a human readable format
477 (same format as displayed by the eeprom print command).
479 Both commands can either auto detect the layout, or be told which
483 __weak int parse_layout_version(char *str)
484 - override to provide your own layout name parsing
485 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
487 - override to setup the layout metadata based on the version
488 __weak int eeprom_layout_detect(unsigned char *data)
489 - override to provide your own algorithm for detecting layout
492 - contains various printing and updating functions for common
493 types of eeprom fields. Can be used for defining
496 config EEPROM_LAYOUT_HELP_STRING
497 string "Tells user what layout names are supported"
498 depends on CMD_EEPROM_LAYOUT
499 default "<not defined>"
501 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
507 Infinite write loop on address range
514 Compute MD5 checksum.
519 depends on CMD_MD5SUM
521 Add -v option to verify data against an MD5 checksum.
526 Display memory information.
529 bool "md, mm, nm, mw, cp, cmp, base, loop"
534 mm - memory modify (auto-incrementing address)
535 nm - memory modify (constant address)
536 mw - memory write (fill)
539 base - print or set address offset
540 loop - initialize loop on address range
545 Simple RAM read/write test.
549 config SYS_ALT_MEMTEST
550 bool "Alternative test"
552 Use a more complete alternative memory test.
559 mdc - memory display cyclic
560 mwc - memory write cyclic
566 Compute SHA1 checksum.
568 config SHA1SUM_VERIFY
570 depends on CMD_SHA1SUM
572 Add -v option to verify data against a SHA1 checksum.
575 bool "strings - display strings in memory"
577 This works similarly to the Unix 'strings' command except that it
578 works with a memory range. String of printable characters found
579 within the range are displayed. The minimum number of characters
580 for a sequence to be considered a string can be provided.
584 menu "Compression commands"
588 default y if CMD_BOOTI
591 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
596 default y if CMD_BOOTI
598 Uncompress a zip-compressed memory region.
603 Compress a memory region with zlib deflate method.
607 menu "Device access commands"
610 #depends on FLASH_CFI_DRIVER
613 ARM Ltd reference designs flash partition access
616 bool "adc - Access Analog to Digital Converters info and data"
620 Shows ADC device info and permit printing one-shot analog converted
621 data from a named Analog to Digital Converter.
624 bool "bind/unbind - Bind or unbind a device to/from a driver"
627 Bind or unbind a device to/from a driver from the command line.
628 This is useful in situations where a device may be handled by several
629 drivers. For example, this can be used to bind a UDC to the usb ether
630 gadget driver from the command line.
633 bool "clk - Show clock frequencies"
636 Shows clock frequences by calling a sock_clk_dump() hook function.
637 This is depreated in favour of using the CLK uclass and accessing
638 clock values from associated drivers. However currently no command
642 bool "demo - Demonstration commands for driver model"
645 Provides a 'demo' command which can be used to play around with
646 driver model. To use this properly you will need to enable one or
647 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
648 Otherwise you will always get an empty list of devices. The demo
649 devices are defined in the sandbox device tree, so the easiest
650 option is to use sandbox and pass the -d point to sandbox's
657 Enables the command "dfu" which is used to have U-Boot create a DFU
658 class device via USB. This command requires that the "dfu_alt_info"
659 environment variable be set and define the alt settings to expose to
663 bool "dm - Access to driver model information"
666 Provides access to driver model data structures and information,
667 such as a list of devices, list of uclasses and the state of each
668 device (e.g. activated). This is not required for operation, but
669 can be useful to see the state of driver model for debugging or
673 bool "fastboot - Android fastboot support"
676 This enables the command "fastboot" which enables the Android
677 fastboot mode for the platform. Fastboot is a protocol for
678 downloading images, flashing and device control used on
679 Android devices. Fastboot requires either the network stack
680 enabled or support for acting as a USB device.
682 See doc/README.android-fastboot for more information.
685 bool "fdcboot - Boot from floppy device"
687 The 'fdtboot' command allows booting an image from a floppy disk.
690 bool "flinfo, erase, protect"
694 flinfo - print FLASH memory information
696 protect - enable or disable FLASH write protection
705 config CMD_FPGA_LOADBP
706 bool "fpga loadbp - load partial bitstream (Xilinx only)"
709 Supports loading an FPGA device from a bitstream buffer containing
712 config CMD_FPGA_LOADFS
713 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
716 Supports loading an FPGA device from a FAT filesystem.
718 config CMD_FPGA_LOADMK
719 bool "fpga loadmk - load bitstream from image"
722 Supports loading an FPGA device from a image generated by mkimage.
724 config CMD_FPGA_LOADP
725 bool "fpga loadp - load partial bitstream"
728 Supports loading an FPGA device from a bitstream buffer containing
731 config CMD_FPGA_LOAD_SECURE
732 bool "fpga loads - loads secure bitstreams (Xilinx only)"
735 Enables the fpga loads command which is used to load secure
736 (authenticated or encrypted or both) bitstreams on to FPGA.
739 bool "fpgad - dump FPGA registers"
741 (legacy, needs conversion to driver model)
742 Provides a way to dump FPGA registers by calling the board-specific
743 fpga_get_reg() function. This functions similarly to the 'md'
747 bool "fuse - support for the fuse subssystem"
749 (deprecated - needs conversion to driver model)
750 This allows reading, sensing, programming or overriding fuses
751 which control the behaviour of the device. The command uses the
760 bool "GPT (GUID Partition Table) command"
762 select HAVE_BLOCK_DEVICE
763 select PARTITION_UUIDS
766 Enable the 'gpt' command to ready and write GPT style partition
770 bool "GPT Random UUID generation"
773 Enable the generation of partitions with random UUIDs if none
776 config CMD_GPT_RENAME
777 bool "GPT partition renaming commands"
780 Enables the 'gpt' command to interchange names on two GPT
781 partitions via the 'gpt swap' command or to rename single
782 partitions via the 'rename' command.
785 bool "ide - Support for IDE drivers"
788 Provides an 'ide' command which allows accessing the IDE drive,
789 reseting the IDE interface, printing the partition table and
790 geting device info. It also enables the 'diskboot' command which
791 permits booting from an IDE drive.
794 bool "io - Support for performing I/O accesses"
796 Provides an 'iod' command to display I/O space and an 'iow' command
797 to write values to the I/O space. This can be useful for manually
798 checking the state of devices during boot when debugging device
802 bool "iotrace - Support for tracing I/O activity"
804 Provides an 'iotrace' command which supports recording I/O reads and
805 writes in a trace buffer in memory . It also maintains a checksum
806 of the trace records (even if space is exhausted) so that the
807 sequence of I/O accesses can be verified.
809 When debugging drivers it is useful to see what I/O accesses were
810 done and in what order.
812 Even if the individual accesses are of little interest it can be
813 useful to verify that the access pattern is consistent each time
814 an operation is performed. In this case a checksum can be used to
815 characterise the operation of a driver. The checksum can be compared
816 across different runs of the operation to verify that the driver is
819 In particular, when performing major refactoring of the driver, where
820 the access pattern should not change, the checksum provides assurance
821 that the refactoring work has not broken the driver.
823 This works by sneaking into the io.h heder for an architecture and
824 redirecting I/O accesses through iotrace's tracing mechanism.
826 For now no commands are provided to examine the trace buffer. The
827 format is fairly simple, so 'md' is a reasonable substitute.
829 Note: The checksum feature is only useful for I/O regions where the
830 contents do not change outside of software control. Where this is not
831 suitable you can fall back to manually comparing the addresses. It
832 might be useful to enhance tracing to only checksum the accesses and
833 not the data read/written.
843 bool "w1 - Support for Dallas 1-Wire protocol"
845 Dallas 1-wire protocol support
851 Load a binary file over serial line.
857 Load an S-Record file over serial line
862 MMC memory mapped support.
865 bool "Enable support for RPMB in the mmc command"
868 Enable the commands for reading, writing and programming the
869 key for the Replay Protection Memory Block partition in eMMC.
871 config CMD_MMC_SWRITE
873 depends on CMD_MMC && MMC_WRITE
876 Enable support for the "mmc swrite" command to write Android sparse
881 select MTD_PARTITIONS
883 MTD commands support.
887 default y if NAND_SUNXI
892 config CMD_NAND_TRIMFFS
893 bool "nand write.trimffs"
894 default y if ARCH_SUNXI
896 Allows one to skip empty pages when flashing something on a NAND.
898 config CMD_NAND_LOCK_UNLOCK
899 bool "nand lock/unlock"
901 NAND locking support.
903 config CMD_NAND_TORTURE
906 NAND torture support.
915 NVM Express device support
918 bool "mmc_spi - Set up MMC SPI device"
920 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
921 Peripheral Interface) device. The device provides a means of
922 accessing an MMC device via SPI using a single data line, limited
923 to 20MHz. It is useful since it reduces the amount of protocol code
927 bool "onenand - access to onenand device"
929 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
930 various useful features. This command allows reading, writing,
931 and erasing blocks. It allso provides a way to show and change
932 bad blocks, and test the device.
937 Enable the 'osd' command which allows to query information from and
938 write text data to a on-screen display (OSD) device; a virtual device
939 associated with a display capable of displaying a text overlay on the
940 display it's associated with..
944 select HAVE_BLOCK_DEVICE
945 select PARTITION_UUIDS
947 Read and display information about the partition table on
951 bool "pci - Access PCI devices"
953 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
954 used on some devices to allow the CPU to communicate with its
955 peripherals. Sub-commands allow bus enumeration, displaying and
956 changing configuration space and a few other features.
959 bool "pinit - Set up PCMCIA device"
961 Provides a means to initialise a PCMCIA (Personal Computer Memory
962 Card International Association) device. This is an old standard from
963 about 1990. These devices are typically removable memory or network
964 cards using a standard 68-pin connector.
967 bool "pinmux - show pins muxing"
970 Parse all available pin-controllers and show pins muxing. This
971 is useful for debug purpoer to check the pin muxing and to know if
972 a pin is configured as a GPIO or as an alternate function.
977 Poweroff/Shutdown the system
980 bool "read - Read binary data from a partition"
982 Provides low-level access to the data in a partition.
984 config CMD_REMOTEPROC
986 depends on REMOTEPROC
988 Support for Remote Processor control
991 bool "sata - Access SATA subsystem"
994 SATA (Serial Advanced Technology Attachment) is a serial bus
995 standard for connecting to hard drives and other storage devices.
996 This command provides information about attached devices and allows
997 reading, writing and other operations.
999 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1000 Attachment, where AT refers to an IBM AT (Advanced Technology)
1001 computer released in 1984.
1004 bool "saves - Save a file over serial in S-Record format"
1006 Provides a way to save a binary file using the Motorola S-Record
1007 format over the serial line.
1010 bool "scsi - Access to SCSI devices"
1013 This provides a 'scsi' command which provides access to SCSI (Small
1014 Computer System Interface) devices. The command provides a way to
1015 scan the bus, reset the bus, read and write data and get information
1019 bool "sdram - Print SDRAM configuration information"
1021 Provides information about attached SDRAM. This assumed that the
1022 SDRAM has an EEPROM with information that can be read using the
1023 I2C bus. This is only available on some boards.
1031 bool "sf test - Allow testing of SPI flash"
1033 Provides a way to test that SPI flash is working correctly. The
1034 test is destructive, in that an area of SPI flash must be provided
1035 for the test to use. Performance information is also provided,
1036 measuring the performance of reading, writing and erasing in
1037 Mbps (Million Bits Per Second). This value should approximately
1038 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1039 everything is working properly.
1042 bool "sspi - Command to access spi device"
1044 SPI utility command.
1046 config DEFAULT_SPI_BUS
1047 int "default spi bus used by sspi command"
1051 config DEFAULT_SPI_MODE
1052 hex "default spi mode used by sspi command (see include/spi.h)"
1057 bool "tsi148 - Command to access tsi148 device"
1059 This provides various sub-commands to initialise and configure the
1060 Turndra tsi148 device. See the command help for full details.
1063 bool "universe - Command to set up the Turndra Universe controller"
1065 This allows setting up the VMEbus provided by this controller.
1066 See the command help for full details.
1070 select HAVE_BLOCK_DEVICE
1076 select USB_FUNCTION_SDP
1078 Enables the command "sdp" which is used to have U-Boot emulating the
1079 Serial Download Protocol (SDP) via USB.
1083 depends on USB_FUNCTION_ROCKUSB
1085 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1086 read/write info, image to/from devices. This enable rockusb command
1087 support to communication with rockusb device. for more detail about
1088 this command, please read doc/README.rockusb.
1090 config CMD_USB_MASS_STORAGE
1091 bool "UMS usb mass storage"
1092 select USB_FUNCTION_MASS_STORAGE
1094 USB mass storage support
1101 VirtIO block device support
1107 This provides commands to control the watchdog timer devices.
1113 Enable the command "axi" for accessing AXI (Advanced eXtensible
1114 Interface) busses, a on-chip interconnect specification for managing
1115 functional blocks in SoC designs, which is also often used in designs
1116 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1120 menu "Shell scripting commands"
1126 Echo args to console
1132 Return true/false on integer compare.
1138 Run script from memory
1144 Evaluate boolean and math expressions and store the result in an env
1146 Also supports loading the value at a memory location into a variable.
1147 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1154 bool "Network commands"
1164 bootp - boot image via network using BOOTP/TFTP protocol
1168 depends on CMD_BOOTP
1170 Boot image via network using DHCP/TFTP protocol
1172 config BOOTP_BOOTPATH
1173 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1175 depends on CMD_BOOTP
1177 Even though the config is called BOOTP_BOOTPATH, it stores the
1178 path in the variable 'rootpath'.
1181 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1183 depends on CMD_BOOTP
1185 The primary DNS server is stored as 'dnsip'. If two servers are
1186 returned, you must set BOOTP_DNS2 to store that second server IP
1190 bool "Store 'dnsip2' from BOOTP/DHCP server"
1191 depends on BOOTP_DNS
1193 If a DHCP client requests the DNS server IP from a DHCP server,
1194 it is possible that more than one DNS serverip is offered to the
1195 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1196 server IP will be stored in the additional environment
1197 variable "dnsip2". The first DNS serverip is always
1198 stored in the variable "dnsip", when BOOTP_DNS is defined.
1200 config BOOTP_GATEWAY
1201 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1203 depends on CMD_BOOTP
1205 config BOOTP_HOSTNAME
1206 bool "Request & store 'hostname' from BOOTP/DHCP server"
1208 depends on CMD_BOOTP
1210 The name may or may not be qualified with the local domain name.
1212 config BOOTP_PREFER_SERVERIP
1213 bool "serverip variable takes precedent over DHCP server IP."
1214 depends on CMD_BOOTP
1216 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1218 With this option enabled, the 'serverip' variable in the environment
1219 takes precedence over DHCP server IP and will only be set by the DHCP
1220 server if not already set in the environment.
1222 config BOOTP_SUBNETMASK
1223 bool "Request & store 'netmask' from BOOTP/DHCP server"
1225 depends on CMD_BOOTP
1227 config BOOTP_NTPSERVER
1228 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1229 depends on CMD_BOOTP
1232 bool "Send PXE client arch to BOOTP/DHCP server"
1234 depends on CMD_BOOTP && CMD_PXE
1236 Supported for ARM, ARM64, and x86 for now.
1238 config BOOTP_PXE_CLIENTARCH
1240 depends on BOOTP_PXE
1241 default 0x16 if ARM64
1245 config BOOTP_VCI_STRING
1247 depends on CMD_BOOTP
1248 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1249 default "U-Boot.armv8" if ARM64
1250 default "U-Boot.arm" if ARM
1257 tftpboot - boot image via network using TFTP protocol
1261 depends on CMD_TFTPBOOT
1263 TFTP put command, for uploading files to a server
1267 depends on CMD_TFTPBOOT
1269 Act as a TFTP server and boot the first received file
1271 config NET_TFTP_VARS
1272 bool "Control TFTP timeout and count through environment"
1273 depends on CMD_TFTPBOOT
1276 If set, allows controlling the TFTP timeout through the
1277 environment variable tftptimeout, and the TFTP maximum
1278 timeout count through the variable tftptimeoutcountmax.
1279 If unset, timeout and maximum are hard-defined as 1 second
1280 and 10 timouts per TFTP transfer.
1285 Boot image via network using RARP/TFTP protocol
1291 Boot image via network using NFS protocol.
1296 Enable MII utility commands.
1301 Send ICMP ECHO_REQUEST to network host
1306 Perform CDP network configuration
1311 Synchronize RTC via network
1316 Lookup the IP of a hostname
1318 config CMD_LINK_LOCAL
1322 Acquire a network IP address using the link-local protocol
1329 Allow control of L2 Ethernet switch commands. These are supported
1330 by the vsc9953 Ethernet driver at present. Sub-commands allow
1331 operations such as enabling / disabling a port and
1332 viewing/maintaining the filtering database (FDB)
1338 Boot image via network using PXE protocol
1343 Wait for wake-on-lan Magic Packet
1347 menu "Misc commands"
1350 bool "Enable 'bmp' command"
1351 depends on LCD || DM_VIDEO || VIDEO
1353 This provides a way to obtain information about a BMP-format iamge
1354 and to display it. BMP (which presumably stands for BitMaP) is a
1355 file format defined by Microsoft which supports images of various
1356 depths, formats and compression methods. Headers on the file
1357 determine the formats used. This command can be used by first loading
1358 the image into RAM, then using this command to look at it or display
1361 config CMD_BOOTCOUNT
1363 depends on BOOTCOUNT_LIMIT
1365 Enable the bootcount command, which allows interrogation and
1366 reset of the bootcounter.
1369 bool "Enable board-specific commands"
1371 (deprecated: instead, please define a Kconfig option for each command)
1373 Some boards have board-specific commands which are only enabled
1374 during developemnt and need to be turned off for production. This
1375 option provides a way to control this. The commands that are enabled
1376 vary depending on the board.
1378 config CMD_BKOPS_ENABLE
1379 bool "mmc bkops enable"
1383 Enable command for setting manual background operations handshake
1384 on a eMMC device. The feature is optionally available on eMMC devices
1385 conforming to standard >= 4.41.
1387 config CMD_BLOCK_CACHE
1388 bool "blkcache - control and stats for block cache"
1389 depends on BLOCK_CACHE
1390 default y if BLOCK_CACHE
1392 Enable the blkcache command, which can be used to control the
1393 operation of the cache functions.
1394 This is most useful when fine-tuning the operation of the cache
1395 during development, but also allows the cache to be disabled when
1396 it might hurt performance (e.g. when using the ums command).
1399 bool "icache or dcache"
1401 Enable the "icache" and "dcache" commands
1403 config CMD_CONITRACE
1404 bool "conitrace - trace console input codes"
1406 Enable the 'conitrace' command which displays the codes received
1407 from the console input as hexadecimal numbers.
1410 bool "Enable clear screen command 'cls'"
1411 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1414 Enable the 'cls' command which clears the screen contents
1415 on video frame buffer.
1418 bool "Enable the 'display' command, for character displays"
1420 (this needs porting to driver model)
1421 This enables the 'display' command which allows a string to be
1422 displayed on a simple board-specific display. Implement
1423 display_putc() to use it.
1426 bool "efidebug - display/configure UEFI environment"
1427 depends on EFI_LOADER
1430 Enable the 'efidebug' command which provides a subset of UEFI
1431 shell utility with simplified functionality. It will be useful
1432 particularly for managing boot parameters as well as examining
1433 various EFI status for debugging.
1435 config CMD_EXCEPTION
1436 bool "exception - raise exception"
1437 depends on ARM || RISCV || X86
1439 Enable the 'exception' command which allows to raise an exception.
1446 Enable the 'led' command which allows for control of LEDs supported
1447 by the board. The LEDs can be listed with 'led list' and controlled
1448 with led on/off/togle/blink. Any LED drivers can be controlled with
1449 this command, e.g. led_gpio.
1455 Enable the 'date' command for getting/setting the time/date in RTC
1461 Run commands and summarize execution time.
1464 bool "gettime - read elapsed time"
1466 Enable the 'gettime' command which reads the elapsed time since
1467 U-Boot started running. This shows the time in seconds and
1468 milliseconds. See also the 'bootstage' command which provides more
1469 flexibility for boot timing.
1471 # TODO: rename to CMD_SLEEP
1476 Delay execution for some time
1479 bool "support for multiprocessor"
1481 This provides an option to brinup
1482 different processors in multiprocessor
1488 Access the system timer.
1494 This provides basic access to the U-Boot's sound support. The main
1495 feature is to play a beep.
1497 sound init - set up sound system
1498 sound play - play a sound
1504 This provides access to the QEMU firmware interface. The main
1505 feature is to allow easy loading of files passed to qemu-system
1506 via -kernel / -initrd
1508 source "cmd/mvebu/Kconfig"
1511 bool "terminal - provides a way to attach a serial terminal"
1513 Provides a 'cu'-like serial terminal command. This can be used to
1514 access other serial ports from the system console. The terminal
1515 is very simple with no special processing of characters. As with
1516 cu, you can press ~. (tilde followed by period) to exit.
1519 bool "uuid, guid - generation of unique IDs"
1522 This enables two commands:
1524 uuid - generate random Universally Unique Identifier
1525 guid - generate Globally Unique Identifier based on random UUID
1527 The two commands are very similar except for the endianness of the
1532 source "cmd/ti/Kconfig"
1534 config CMD_BOOTSTAGE
1535 bool "Enable the 'bootstage' command"
1536 depends on BOOTSTAGE
1538 Add a 'bootstage' command which supports printing a report
1539 and un/stashing of bootstage data.
1541 menu "Power commands"
1543 bool "Enable Driver Model PMIC command"
1546 This is the pmic command, based on a driver model pmic's API.
1547 Command features are unchanged:
1548 - list - list pmic devices
1549 - pmic dev <id> - show or [set] operating pmic device (NEW)
1550 - pmic dump - dump registers
1551 - pmic read address - read byte of register at address
1552 - pmic write address - write byte to register at address
1553 The only one change for this command is 'dev' subcommand.
1555 config CMD_REGULATOR
1556 bool "Enable Driver Model REGULATOR command"
1557 depends on DM_REGULATOR
1559 This command is based on driver model regulator's API.
1560 User interface features:
1561 - list - list regulator devices
1562 - regulator dev <id> - show or [set] operating regulator device
1563 - regulator info - print constraints info
1564 - regulator status - print operating status
1565 - regulator value <val] <-f> - print/[set] voltage value [uV]
1566 - regulator current <val> - print/[set] current value [uA]
1567 - regulator mode <id> - print/[set] operating mode id
1568 - regulator enable - enable the regulator output
1569 - regulator disable - disable the regulator output
1571 The '-f' (force) option can be used for set the value which exceeds
1572 the limits, which are found in device-tree and are kept in regulator's
1573 uclass platdata structure.
1577 menu "Security commands"
1579 bool "Enable the 'aes' command"
1582 This provides a means to encrypt and decrypt data using the AES
1583 (Advanced Encryption Standard). This algorithm uses a symetric key
1584 and is widely used as a streaming cipher. Different key lengths are
1585 supported by the algorithm but this command only supports 128 bits
1589 bool "Enable the 'blob' command"
1591 This is used with the Freescale secure boot mechanism.
1593 Freescale's SEC block has built-in Blob Protocol which provides
1594 a method for protecting user-defined data across system power
1595 cycles. SEC block protects data in a data structure called a Blob,
1596 which provides both confidentiality and integrity protection.
1598 Encapsulating data as a blob
1599 Each time that the Blob Protocol is used to protect data, a
1600 different randomly generated key is used to encrypt the data.
1601 This random key is itself encrypted using a key which is derived
1602 from SoC's non-volatile secret key and a 16 bit Key identifier.
1603 The resulting encrypted key along with encrypted data is called a
1604 blob. The non-volatile secure key is available for use only during
1607 During decapsulation, the reverse process is performed to get back
1611 blob enc - encapsulating data as a cryptgraphic blob
1612 blob dec - decapsulating cryptgraphic blob to get the data
1616 blob enc src dst len km
1618 Encapsulate and create blob of data $len bytes long
1619 at address $src and store the result at address $dst.
1620 $km is the 16 byte key modifier is also required for
1621 generation/use as key for cryptographic operation. Key
1622 modifier should be 16 byte long.
1624 blob dec src dst len km
1626 Decapsulate the blob of data at address $src and
1627 store result of $len byte at addr $dst.
1628 $km is the 16 byte key modifier is also required for
1629 generation/use as key for cryptographic operation. Key
1630 modifier should be 16 byte long.
1633 bool "Support 'hash' command"
1636 This provides a way to hash data in memory using various supported
1637 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1638 saved to memory or to an environment variable. It is also possible
1639 to verify a hash against data in memory.
1642 bool "Support the 'hvc' command"
1643 depends on ARM_SMCCC
1645 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1646 development and testing.
1649 bool "Support the 'smc' command"
1650 depends on ARM_SMCCC
1652 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1653 development and testing.
1659 Add -v option to verify data against a hash.
1669 bool "Enable the 'tpm' command"
1670 depends on TPM_V1 || TPM_V2
1671 select CMD_TPM_V1 if TPM_V1
1672 select CMD_TPM_V2 if TPM_V2
1674 This provides a means to talk to a TPM from the command line. A wide
1675 range of commands if provided - see 'tpm help' for details. The
1676 command requires a suitable TPM on your board and the correct driver
1682 bool "Enable the 'tpm test' command"
1685 This provides a a series of tests to confirm that the TPMv1.x is
1686 working correctly. The tests cover initialisation, non-volatile RAM,
1687 extend, global lock and checking that timing is within expectations.
1688 The tests pass correctly on Infineon TPMs but may need to be adjusted
1695 menu "Firmware commands"
1697 bool "Enable crosec command"
1701 Enable command-line access to the Chrome OS EC (Embedded
1702 Controller). This provides the 'crosec' command which has
1703 a number of sub-commands for performing EC tasks such as
1704 updating its flash, accessing a small saved context area
1705 and talking to the I2C bus behind the EC (if there is one).
1708 menu "Filesystem commands"
1710 bool "Enable the 'btrsubvol' command"
1713 This enables the 'btrsubvol' command to list subvolumes
1714 of a BTRFS filesystem. There are no special commands for
1715 listing BTRFS directories or loading BTRFS files - this
1716 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1717 when BTRFS is enabled (see FS_BTRFS).
1720 bool "Enable the 'cbfs' command"
1723 Define this to enable support for reading from a Coreboot
1724 filesystem. This is a ROM-based filesystem used for accessing files
1725 on systems that use coreboot as the first boot-loader and then load
1726 U-Boot to actually boot the Operating System. Available commands are
1727 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1730 bool "Enable the 'cramfs' command"
1731 depends on FS_CRAMFS
1733 This provides commands for dealing with CRAMFS (Compressed ROM
1734 filesystem). CRAMFS is useful when space is tight since files are
1735 compressed. Two commands are provided:
1737 cramfsls - lists files in a cramfs image
1738 cramfsload - loads a file from a cramfs image
1741 bool "ext2 command support"
1744 Enables EXT2 FS command
1747 bool "ext4 command support"
1750 Enables EXT4 FS command
1752 config CMD_EXT4_WRITE
1754 bool "ext4 write command support"
1757 Enables EXT4 FS write command
1760 bool "FAT command support"
1763 Support for the FAT fs
1765 config CMD_FS_GENERIC
1766 bool "filesystem commands"
1768 Enables filesystem commands (e.g. load, ls) that work for multiple
1772 bool "fsuuid command"
1774 Enables fsuuid command for filesystem UUID.
1777 bool "jffs2 command"
1780 Enables commands to support the JFFS2 (Journalling Flash File System
1781 version 2) filesystem. This enables fsload, ls and fsinfo which
1782 provide the ability to load files, list directories and obtain
1783 filesystem information.
1786 bool "MTD partition support"
1787 select MTD_DEVICE if (CMD_NAND || NAND)
1789 MTD partitioning tool support.
1790 It is strongly encouraged to avoid using this command
1791 anymore along with 'sf', 'nand', 'onenand'. One can still
1792 declare the partitions in the mtdparts environment variable
1793 but better use the MTD stack and the 'mtd' command instead.
1795 config MTDIDS_DEFAULT
1796 string "Default MTD IDs"
1797 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1799 Defines a default MTD IDs list for use with MTD partitions in the
1800 Linux MTD command line partitions format.
1802 config MTDPARTS_DEFAULT
1803 string "Default MTD partition scheme"
1804 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1806 Defines a default MTD partitioning scheme in the Linux MTD command
1807 line partitions format
1809 config CMD_MTDPARTS_SPREAD
1810 bool "Padd partition size to take account of bad blocks"
1811 depends on CMD_MTDPARTS
1813 This enables the 'spread' sub-command of the mtdparts command.
1814 This command will modify the existing mtdparts variable by increasing
1815 the size of the partitions such that 1) each partition's net size is
1816 at least as large as the size specified in the mtdparts variable and
1817 2) each partition starts on a good block.
1820 bool "reiser - Access to reiserfs filesystems"
1822 This provides two commands which operate on a resierfs filesystem,
1823 commonly used some years ago:
1825 reiserls - list files
1826 reiserload - load a file
1829 bool "yaffs2 - Access of YAFFS2 filesystem"
1833 This provides commands for accessing a YAFFS2 filesystem. Yet
1834 Another Flash Filesystem 2 is a filesystem designed specifically
1835 for NAND flash. It incorporates bad-block management and ensures
1836 that device writes are sequential regardless of filesystem
1840 bool "zfs - Access of ZFS filesystem"
1842 This provides commands to accessing a ZFS filesystem, commonly used
1843 on Solaris systems. Two sub-commands are provided:
1845 zfsls - list files in a directory
1846 zfsload - load a file
1848 See doc/README.zfs for more details.
1852 menu "Debug commands"
1857 The bedbug (emBEDded deBUGger) command provides debugging features
1858 for some PowerPC processors. For details please see the
1859 docuemntation in doc/README.beddbug
1862 bool "diag - Board diagnostics"
1864 This command provides access to board diagnostic tests. These are
1865 called Power-on Self Tests (POST). The command allows listing of
1866 available tests and running either all the tests, or specific tests
1870 bool "irq - Show information about interrupts"
1871 depends on !ARM && !MIPS && !SH
1873 This enables two commands:
1875 interrupts - enable or disable interrupts
1876 irqinfo - print device-specific interrupt information
1879 bool "kgdb - Allow debugging of U-Boot with gdb"
1882 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1883 over a serial link for debugging purposes. This allows
1884 single-stepping, inspecting variables, etc. This is supported only
1885 on PowerPC at present.
1888 bool "log - Generation, control and access to logging"
1891 This provides access to logging features. It allows the output of
1892 log data to be controlled to a limited extent (setting up the default
1893 maximum log level for emitting of records). It also provides access
1894 to a command used for testing the log system.
1897 bool "trace - Support tracing of function calls and timing"
1899 Enables a command to control using of function tracing within
1900 U-Boot. This allows recording of call traces including timing
1901 information. The command can write data to memory for exporting
1902 for analsys (e.g. using bootchart). See doc/README.trace for full
1906 bool "avb - Android Verified Boot 2.0 operations"
1907 depends on AVB_VERIFY
1910 Enables a "avb" command to perform verification of partitions using
1911 Android Verified Boot 2.0 functionality. It includes such subcommands:
1912 avb init - initialize avb2 subsystem
1913 avb read_rb - read rollback index
1914 avb write_rb - write rollback index
1915 avb is_unlocked - check device lock state
1916 avb get_uuid - read and print uuid of a partition
1917 avb read_part - read data from partition
1918 avb read_part_hex - read data from partition and output to stdout
1919 avb write_part - write data to partition
1920 avb verify - run full verification chain
1924 tristate "Enable UBI - Unsorted block images commands"
1928 UBI is a software layer above MTD layer which admits use of LVM-like
1929 logical volumes on top of MTD devices, hides some complexities of
1930 flash chips like wear and bad blocks and provides some other useful
1931 capabilities. Please, consult the MTD web site for more details
1932 (www.linux-mtd.infradead.org). Activate this option if you want
1933 to use U-Boot UBI commands.
1934 It is also strongly encouraged to also enable CONFIG_MTD to get full
1938 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1940 default y if CMD_UBI
1944 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob