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
57 string "Command execution tracer"
61 This option enables the possiblity to print all commands before
62 executing them and after all variables are evaluated (similar
63 to Bash's xtrace/'set -x' feature).
64 To enable the tracer a variable "xtrace" needs to be defined in
67 menu "Autoboot options"
73 This enables the autoboot. See doc/README.autoboot for detail.
76 bool "Stop autobooting via specific input key / string"
79 This option enables stopping (aborting) of the automatic
80 boot feature only by issuing a specific input key or
81 string. If not enabled, any input key will abort the
82 U-Boot automatic booting process and bring the device
83 to the U-Boot prompt for user input.
85 config AUTOBOOT_PROMPT
86 string "Autoboot stop prompt"
87 depends on AUTOBOOT_KEYED
88 default "Autoboot in %d seconds\\n"
90 This string is displayed before the boot delay selected by
91 CONFIG_BOOTDELAY starts. If it is not defined there is no
92 output indicating that autoboot is in progress.
94 Note that this define is used as the (only) argument to a
95 printf() call, so it may contain '%' format specifications,
96 provided that it also includes, sepearated by commas exactly
97 like in a printf statement, the required arguments. It is
98 the responsibility of the user to select only such arguments
99 that are valid in the given context.
101 config AUTOBOOT_ENCRYPTION
102 bool "Enable encryption in autoboot stopping"
103 depends on AUTOBOOT_KEYED
106 config AUTOBOOT_DELAY_STR
107 string "Delay autobooting via specific input key / string"
108 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
110 This option delays the automatic boot feature by issuing
111 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
112 or the environment variable "bootdelaykey" is specified
113 and this string is received from console input before
114 autoboot starts booting, U-Boot gives a command prompt. The
115 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
116 used, otherwise it never times out.
118 config AUTOBOOT_STOP_STR
119 string "Stop autobooting via specific input key / string"
120 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
122 This option enables stopping (aborting) of the automatic
123 boot feature only by issuing a specific input key or
124 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
125 variable "bootstopkey" is specified and this string is
126 received from console input before autoboot starts booting,
127 U-Boot gives a command prompt. The U-Boot prompt never
128 times out, even if CONFIG_BOOT_RETRY_TIME is used.
130 config AUTOBOOT_KEYED_CTRLC
131 bool "Enable Ctrl-C autoboot interruption"
132 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
135 This option allows for the boot sequence to be interrupted
136 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
137 Setting this variable provides an escape sequence from the
138 limited "password" strings.
140 config AUTOBOOT_STOP_STR_SHA256
141 string "Stop autobooting via SHA256 encrypted password"
142 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
144 This option adds the feature to only stop the autobooting,
145 and therefore boot into the U-Boot prompt, when the input
146 string / password matches a values that is encypted via
147 a SHA256 hash and saved in the environment.
169 Print ".config" contents.
171 If this option is enabled, the ".config" file contents are embedded
172 in the U-Boot image and can be printed on the console by the "config"
173 command. This provides information of which options are enabled on
180 Print console devices and information.
185 Print information about available CPUs. This normally shows the
186 number of CPUs, type (e.g. manufacturer, architecture, product or
187 internal name) and clock frequency. Other information may be
188 available depending on the CPU driver.
194 Print GPL license text
210 Run the command stored in the environment "bootcmd", i.e.
211 "bootd" does the same thing as "run bootcmd".
217 Boot an application image from the memory.
222 Boot the Linux zImage
229 Boot an AArch64 Linux Kernel image from memory.
233 depends on EFI_LOADER
236 Boot an EFI image from memory.
238 config CMD_BOOTEFI_HELLO_COMPILE
239 bool "Compile a standard EFI hello world binary for testing"
240 depends on CMD_BOOTEFI && !CPU_V7M && !SANDBOX
243 This compiles a standard EFI hello world application with U-Boot so
244 that it can be used with the test/py testing framework. This is useful
245 for testing that EFI is working at a basic level, and for bringing
246 up EFI support on a new architecture.
248 No additional space will be required in the resulting U-Boot binary
249 when this option is enabled.
251 config CMD_BOOTEFI_HELLO
252 bool "Allow booting a standard EFI hello world for testing"
253 depends on CMD_BOOTEFI_HELLO_COMPILE
255 This adds a standard EFI hello world application to U-Boot so that
256 it can be used with the 'bootefi hello' command. This is useful
257 for testing that EFI is working at a basic level, and for bringing
258 up EFI support on a new architecture.
260 source lib/efi_selftest/Kconfig
266 Add an ANSI terminal boot menu command.
271 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
272 image into RAM, dump image structure information, etc. Those dtb/dtbo
273 files should be merged in one dtb further, which needs to be passed to
274 the kernel, as part of a boot process.
277 bool "bootelf, bootvx"
280 Boot an ELF/vxWorks image from the memory.
283 bool "Flattened Device Tree utility commands"
287 Do FDT related setup before booting into the Operating System.
293 Start an application at a given address.
299 Run the command in the given environment variable.
305 Print header information for application image.
310 List all images found in flash
316 Extract a part of a multi-image.
319 bool "spl export - Export boot information for Falcon boot"
322 Falcon mode allows booting directly from SPL into an Operating
323 System such as Linux, thus skipping U-Boot proper. See
324 doc/README.falcon for full information about how to use this
327 config CMD_SPL_NAND_OFS
328 hex "Offset of OS command line args for Falcon-mode NAND boot"
332 This provides the offset of the command line arguments for Linux
333 when booting from NAND in Falcon mode. See doc/README.falcon
334 for full information about how to use this option (and also see
335 board/gateworks/gw_ventana/README for an example).
337 config CMD_SPL_WRITE_SIZE
338 hex "Size of argument area"
342 This provides the size of the command-line argument area in NAND
343 flash used by Falcon-mode boot. See the documentation until CMD_SPL
347 bool "fitImage update command"
349 Implements the 'fitupd' command, which allows to automatically
350 store software updates present on a TFTP server in NOR Flash
352 config CMD_THOR_DOWNLOAD
353 bool "thor - TIZEN 'thor' download"
355 Implements the 'thor' download protocol. This is a way of
356 downloading a software update over USB from an attached host.
357 There is no documentation about this within the U-Boot source code
358 but you should be able to find something on the interwebs.
361 bool "zboot - x86 boot command"
363 With x86 machines it is common to boot a bzImage file which
364 contains both a kernel and a setup.bin file. The latter includes
365 configuration information from the dark ages which x86 boards still
366 need to pick things out of.
368 Consider using FIT in preference to this since it supports directly
369 booting both 32- and 64-bit kernels, as well as secure boot.
370 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
374 menu "Environment commands"
377 bool "ask for env variable"
379 Ask for environment variable
397 Edit environment variable.
402 Allow for searching environment variables
408 Save all environment variables into the compiled-in persistent
411 config CMD_ENV_EXISTS
415 Check if a variable is defined in the environment for use in
418 config CMD_ENV_CALLBACK
419 bool "env callbacks - print callbacks and their associated variables"
421 Some environment variable have callbacks defined by
422 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
423 For example changing "baudrate" adjust the serial baud rate. This
424 command lists the currently defined callbacks.
427 bool "env flags -print variables that have non-default flags"
429 Some environment variables have special flags that control their
430 behaviour. For example, serial# can only be written once and cannot
431 be deleted. This command shows the variables that have special
434 config CMD_NVEDIT_EFI
435 bool "env [set|print] -e - set/print UEFI variables"
436 depends on EFI_LOADER
440 UEFI variables are encoded as some form of U-Boot variables.
441 If enabled, we are allowed to set/print UEFI variables using
442 "env" command with "-e" option without knowing details.
446 menu "Memory commands"
451 Compute binary operations (xor, or, and) of byte arrays of arbitrary
452 size from memory and store the result in memory or the environment.
465 Add -v option to verify data against a crc32 checksum.
468 bool "eeprom - EEPROM subsystem"
469 depends on !DM_I2C || DM_I2C_COMPAT
471 (deprecated, needs conversion to driver model)
472 Provides commands to read and write EEPROM (Electrically Erasable
473 Programmable Read Only Memory) chips that are connected over an
476 config CMD_EEPROM_LAYOUT
477 bool "Enable layout-aware eeprom commands"
478 depends on CMD_EEPROM
480 (deprecated, needs conversion to driver model)
481 When enabled, additional eeprom sub-commands become available.
483 eeprom print - prints the contents of the eeprom in a human-readable
484 way (eeprom layout fields, and data formatted to be fit for human
487 eeprom update - allows user to update eeprom fields by specifying
488 the field name, and providing the new data in a human readable format
489 (same format as displayed by the eeprom print command).
491 Both commands can either auto detect the layout, or be told which
495 __weak int parse_layout_version(char *str)
496 - override to provide your own layout name parsing
497 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
499 - override to setup the layout metadata based on the version
500 __weak int eeprom_layout_detect(unsigned char *data)
501 - override to provide your own algorithm for detecting layout
504 - contains various printing and updating functions for common
505 types of eeprom fields. Can be used for defining
508 config EEPROM_LAYOUT_HELP_STRING
509 string "Tells user what layout names are supported"
510 depends on CMD_EEPROM_LAYOUT
511 default "<not defined>"
513 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
519 Infinite write loop on address range
526 Compute MD5 checksum.
531 depends on CMD_MD5SUM
533 Add -v option to verify data against an MD5 checksum.
538 Display memory information.
541 bool "md, mm, nm, mw, cp, cmp, base, loop"
546 mm - memory modify (auto-incrementing address)
547 nm - memory modify (constant address)
548 mw - memory write (fill)
551 base - print or set address offset
552 loop - initialize loop on address range
557 Simple RAM read/write test.
561 config SYS_ALT_MEMTEST
562 bool "Alternative test"
564 Use a more complete alternative memory test.
571 mdc - memory display cyclic
572 mwc - memory write cyclic
578 Compute SHA1 checksum.
580 config SHA1SUM_VERIFY
582 depends on CMD_SHA1SUM
584 Add -v option to verify data against a SHA1 checksum.
587 bool "strings - display strings in memory"
589 This works similarly to the Unix 'strings' command except that it
590 works with a memory range. String of printable characters found
591 within the range are displayed. The minimum number of characters
592 for a sequence to be considered a string can be provided.
596 menu "Compression commands"
600 default y if CMD_BOOTI
603 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
608 default y if CMD_BOOTI
610 Uncompress a zip-compressed memory region.
615 Compress a memory region with zlib deflate method.
619 menu "Device access commands"
622 #depends on FLASH_CFI_DRIVER
625 ARM Ltd reference designs flash partition access
628 bool "adc - Access Analog to Digital Converters info and data"
632 Shows ADC device info and permit printing one-shot analog converted
633 data from a named Analog to Digital Converter.
636 bool "bind/unbind - Bind or unbind a device to/from a driver"
639 Bind or unbind a device to/from a driver from the command line.
640 This is useful in situations where a device may be handled by several
641 drivers. For example, this can be used to bind a UDC to the usb ether
642 gadget driver from the command line.
645 bool "clk - Show clock frequencies"
648 Shows clock frequences by calling a sock_clk_dump() hook function.
649 This is depreated in favour of using the CLK uclass and accessing
650 clock values from associated drivers. However currently no command
654 bool "demo - Demonstration commands for driver model"
657 Provides a 'demo' command which can be used to play around with
658 driver model. To use this properly you will need to enable one or
659 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
660 Otherwise you will always get an empty list of devices. The demo
661 devices are defined in the sandbox device tree, so the easiest
662 option is to use sandbox and pass the -d point to sandbox's
669 Enables the command "dfu" which is used to have U-Boot create a DFU
670 class device via USB. This command requires that the "dfu_alt_info"
671 environment variable be set and define the alt settings to expose to
675 bool "dm - Access to driver model information"
678 Provides access to driver model data structures and information,
679 such as a list of devices, list of uclasses and the state of each
680 device (e.g. activated). This is not required for operation, but
681 can be useful to see the state of driver model for debugging or
685 bool "fastboot - Android fastboot support"
688 This enables the command "fastboot" which enables the Android
689 fastboot mode for the platform. Fastboot is a protocol for
690 downloading images, flashing and device control used on
691 Android devices. Fastboot requires either the network stack
692 enabled or support for acting as a USB device.
694 See doc/README.android-fastboot for more information.
697 bool "fdcboot - Boot from floppy device"
699 The 'fdtboot' command allows booting an image from a floppy disk.
702 bool "flinfo, erase, protect"
706 flinfo - print FLASH memory information
708 protect - enable or disable FLASH write protection
717 config CMD_FPGA_LOADBP
718 bool "fpga loadbp - load partial bitstream (Xilinx only)"
721 Supports loading an FPGA device from a bitstream buffer containing
724 config CMD_FPGA_LOADFS
725 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
728 Supports loading an FPGA device from a FAT filesystem.
730 config CMD_FPGA_LOADMK
731 bool "fpga loadmk - load bitstream from image"
734 Supports loading an FPGA device from a image generated by mkimage.
736 config CMD_FPGA_LOADP
737 bool "fpga loadp - load partial bitstream"
740 Supports loading an FPGA device from a bitstream buffer containing
743 config CMD_FPGA_LOAD_SECURE
744 bool "fpga loads - loads secure bitstreams (Xilinx only)"
747 Enables the fpga loads command which is used to load secure
748 (authenticated or encrypted or both) bitstreams on to FPGA.
751 bool "fpgad - dump FPGA registers"
753 (legacy, needs conversion to driver model)
754 Provides a way to dump FPGA registers by calling the board-specific
755 fpga_get_reg() function. This functions similarly to the 'md'
759 bool "fuse - support for the fuse subssystem"
761 (deprecated - needs conversion to driver model)
762 This allows reading, sensing, programming or overriding fuses
763 which control the behaviour of the device. The command uses the
772 bool "GPT (GUID Partition Table) command"
774 select HAVE_BLOCK_DEVICE
775 select PARTITION_UUIDS
778 Enable the 'gpt' command to ready and write GPT style partition
782 bool "GPT Random UUID generation"
785 Enable the generation of partitions with random UUIDs if none
788 config CMD_GPT_RENAME
789 bool "GPT partition renaming commands"
792 Enables the 'gpt' command to interchange names on two GPT
793 partitions via the 'gpt swap' command or to rename single
794 partitions via the 'rename' command.
797 bool "ide - Support for IDE drivers"
800 Provides an 'ide' command which allows accessing the IDE drive,
801 reseting the IDE interface, printing the partition table and
802 geting device info. It also enables the 'diskboot' command which
803 permits booting from an IDE drive.
806 bool "io - Support for performing I/O accesses"
808 Provides an 'iod' command to display I/O space and an 'iow' command
809 to write values to the I/O space. This can be useful for manually
810 checking the state of devices during boot when debugging device
814 bool "iotrace - Support for tracing I/O activity"
816 Provides an 'iotrace' command which supports recording I/O reads and
817 writes in a trace buffer in memory . It also maintains a checksum
818 of the trace records (even if space is exhausted) so that the
819 sequence of I/O accesses can be verified.
821 When debugging drivers it is useful to see what I/O accesses were
822 done and in what order.
824 Even if the individual accesses are of little interest it can be
825 useful to verify that the access pattern is consistent each time
826 an operation is performed. In this case a checksum can be used to
827 characterise the operation of a driver. The checksum can be compared
828 across different runs of the operation to verify that the driver is
831 In particular, when performing major refactoring of the driver, where
832 the access pattern should not change, the checksum provides assurance
833 that the refactoring work has not broken the driver.
835 This works by sneaking into the io.h heder for an architecture and
836 redirecting I/O accesses through iotrace's tracing mechanism.
838 For now no commands are provided to examine the trace buffer. The
839 format is fairly simple, so 'md' is a reasonable substitute.
841 Note: The checksum feature is only useful for I/O regions where the
842 contents do not change outside of software control. Where this is not
843 suitable you can fall back to manually comparing the addresses. It
844 might be useful to enhance tracing to only checksum the accesses and
845 not the data read/written.
855 bool "w1 - Support for Dallas 1-Wire protocol"
857 Dallas 1-wire protocol support
863 Load a binary file over serial line.
869 Load an S-Record file over serial line
874 MMC memory mapped support.
877 bool "Enable support for RPMB in the mmc command"
880 Enable the commands for reading, writing and programming the
881 key for the Replay Protection Memory Block partition in eMMC.
883 config CMD_MMC_SWRITE
885 depends on CMD_MMC && MMC_WRITE
888 Enable support for the "mmc swrite" command to write Android sparse
893 select MTD_PARTITIONS
895 MTD commands support.
899 default y if NAND_SUNXI
904 config CMD_NAND_TRIMFFS
905 bool "nand write.trimffs"
906 default y if ARCH_SUNXI
908 Allows one to skip empty pages when flashing something on a NAND.
910 config CMD_NAND_LOCK_UNLOCK
911 bool "nand lock/unlock"
913 NAND locking support.
915 config CMD_NAND_TORTURE
918 NAND torture support.
927 NVM Express device support
930 bool "mmc_spi - Set up MMC SPI device"
932 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
933 Peripheral Interface) device. The device provides a means of
934 accessing an MMC device via SPI using a single data line, limited
935 to 20MHz. It is useful since it reduces the amount of protocol code
939 bool "onenand - access to onenand device"
941 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
942 various useful features. This command allows reading, writing,
943 and erasing blocks. It allso provides a way to show and change
944 bad blocks, and test the device.
949 Enable the 'osd' command which allows to query information from and
950 write text data to a on-screen display (OSD) device; a virtual device
951 associated with a display capable of displaying a text overlay on the
952 display it's associated with..
956 select HAVE_BLOCK_DEVICE
957 select PARTITION_UUIDS
959 Read and display information about the partition table on
963 bool "pci - Access PCI devices"
965 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
966 used on some devices to allow the CPU to communicate with its
967 peripherals. Sub-commands allow bus enumeration, displaying and
968 changing configuration space and a few other features.
971 bool "pinit - Set up PCMCIA device"
973 Provides a means to initialise a PCMCIA (Personal Computer Memory
974 Card International Association) device. This is an old standard from
975 about 1990. These devices are typically removable memory or network
976 cards using a standard 68-pin connector.
979 bool "pinmux - show pins muxing"
982 Parse all available pin-controllers and show pins muxing. This
983 is useful for debug purpoer to check the pin muxing and to know if
984 a pin is configured as a GPIO or as an alternate function.
989 Poweroff/Shutdown the system
992 bool "read - Read binary data from a partition"
994 Provides low-level access to the data in a partition.
996 config CMD_REMOTEPROC
998 depends on REMOTEPROC
1000 Support for Remote Processor control
1003 bool "sata - Access SATA subsystem"
1006 SATA (Serial Advanced Technology Attachment) is a serial bus
1007 standard for connecting to hard drives and other storage devices.
1008 This command provides information about attached devices and allows
1009 reading, writing and other operations.
1011 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1012 Attachment, where AT refers to an IBM AT (Advanced Technology)
1013 computer released in 1984.
1016 bool "saves - Save a file over serial in S-Record format"
1018 Provides a way to save a binary file using the Motorola S-Record
1019 format over the serial line.
1022 bool "scsi - Access to SCSI devices"
1025 This provides a 'scsi' command which provides access to SCSI (Small
1026 Computer System Interface) devices. The command provides a way to
1027 scan the bus, reset the bus, read and write data and get information
1031 bool "sdram - Print SDRAM configuration information"
1033 Provides information about attached SDRAM. This assumed that the
1034 SDRAM has an EEPROM with information that can be read using the
1035 I2C bus. This is only available on some boards.
1043 bool "sf test - Allow testing of SPI flash"
1045 Provides a way to test that SPI flash is working correctly. The
1046 test is destructive, in that an area of SPI flash must be provided
1047 for the test to use. Performance information is also provided,
1048 measuring the performance of reading, writing and erasing in
1049 Mbps (Million Bits Per Second). This value should approximately
1050 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1051 everything is working properly.
1054 bool "sspi - Command to access spi device"
1056 SPI utility command.
1058 config DEFAULT_SPI_BUS
1059 int "default spi bus used by sspi command"
1063 config DEFAULT_SPI_MODE
1064 hex "default spi mode used by sspi command (see include/spi.h)"
1069 bool "tsi148 - Command to access tsi148 device"
1071 This provides various sub-commands to initialise and configure the
1072 Turndra tsi148 device. See the command help for full details.
1075 bool "universe - Command to set up the Turndra Universe controller"
1077 This allows setting up the VMEbus provided by this controller.
1078 See the command help for full details.
1082 select HAVE_BLOCK_DEVICE
1088 select USB_FUNCTION_SDP
1090 Enables the command "sdp" which is used to have U-Boot emulating the
1091 Serial Download Protocol (SDP) via USB.
1095 depends on USB_FUNCTION_ROCKUSB
1097 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1098 read/write info, image to/from devices. This enable rockusb command
1099 support to communication with rockusb device. for more detail about
1100 this command, please read doc/README.rockusb.
1102 config CMD_USB_MASS_STORAGE
1103 bool "UMS usb mass storage"
1104 select USB_FUNCTION_MASS_STORAGE
1106 USB mass storage support
1113 VirtIO block device support
1119 This provides commands to control the watchdog timer devices.
1125 Enable the command "axi" for accessing AXI (Advanced eXtensible
1126 Interface) busses, a on-chip interconnect specification for managing
1127 functional blocks in SoC designs, which is also often used in designs
1128 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1132 menu "Shell scripting commands"
1138 Echo args to console
1144 Return true/false on integer compare.
1150 Run script from memory
1156 Evaluate boolean and math expressions and store the result in an env
1158 Also supports loading the value at a memory location into a variable.
1159 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1166 bool "Network commands"
1176 bootp - boot image via network using BOOTP/TFTP protocol
1180 depends on CMD_BOOTP
1182 Boot image via network using DHCP/TFTP protocol
1184 config BOOTP_BOOTPATH
1185 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1187 depends on CMD_BOOTP
1189 Even though the config is called BOOTP_BOOTPATH, it stores the
1190 path in the variable 'rootpath'.
1193 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1195 depends on CMD_BOOTP
1197 The primary DNS server is stored as 'dnsip'. If two servers are
1198 returned, you must set BOOTP_DNS2 to store that second server IP
1202 bool "Store 'dnsip2' from BOOTP/DHCP server"
1203 depends on BOOTP_DNS
1205 If a DHCP client requests the DNS server IP from a DHCP server,
1206 it is possible that more than one DNS serverip is offered to the
1207 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1208 server IP will be stored in the additional environment
1209 variable "dnsip2". The first DNS serverip is always
1210 stored in the variable "dnsip", when BOOTP_DNS is defined.
1212 config BOOTP_GATEWAY
1213 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1215 depends on CMD_BOOTP
1217 config BOOTP_HOSTNAME
1218 bool "Request & store 'hostname' from BOOTP/DHCP server"
1220 depends on CMD_BOOTP
1222 The name may or may not be qualified with the local domain name.
1224 config BOOTP_PREFER_SERVERIP
1225 bool "serverip variable takes precedent over DHCP server IP."
1226 depends on CMD_BOOTP
1228 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1230 With this option enabled, the 'serverip' variable in the environment
1231 takes precedence over DHCP server IP and will only be set by the DHCP
1232 server if not already set in the environment.
1234 config BOOTP_SUBNETMASK
1235 bool "Request & store 'netmask' from BOOTP/DHCP server"
1237 depends on CMD_BOOTP
1239 config BOOTP_NTPSERVER
1240 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1241 depends on CMD_BOOTP
1244 bool "Send PXE client arch to BOOTP/DHCP server"
1246 depends on CMD_BOOTP && CMD_PXE
1248 Supported for ARM, ARM64, and x86 for now.
1250 config BOOTP_PXE_CLIENTARCH
1252 depends on BOOTP_PXE
1253 default 0x16 if ARM64
1257 config BOOTP_VCI_STRING
1259 depends on CMD_BOOTP
1260 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1261 default "U-Boot.armv8" if ARM64
1262 default "U-Boot.arm" if ARM
1269 tftpboot - boot image via network using TFTP protocol
1273 depends on CMD_TFTPBOOT
1275 TFTP put command, for uploading files to a server
1279 depends on CMD_TFTPBOOT
1281 Act as a TFTP server and boot the first received file
1283 config NET_TFTP_VARS
1284 bool "Control TFTP timeout and count through environment"
1285 depends on CMD_TFTPBOOT
1288 If set, allows controlling the TFTP timeout through the
1289 environment variable tftptimeout, and the TFTP maximum
1290 timeout count through the variable tftptimeoutcountmax.
1291 If unset, timeout and maximum are hard-defined as 1 second
1292 and 10 timouts per TFTP transfer.
1297 Boot image via network using RARP/TFTP protocol
1303 Boot image via network using NFS protocol.
1308 Enable MII utility commands.
1313 Send ICMP ECHO_REQUEST to network host
1318 Perform CDP network configuration
1323 Synchronize RTC via network
1328 Lookup the IP of a hostname
1330 config CMD_LINK_LOCAL
1334 Acquire a network IP address using the link-local protocol
1341 Allow control of L2 Ethernet switch commands. These are supported
1342 by the vsc9953 Ethernet driver at present. Sub-commands allow
1343 operations such as enabling / disabling a port and
1344 viewing/maintaining the filtering database (FDB)
1350 Boot image via network using PXE protocol
1355 Wait for wake-on-lan Magic Packet
1359 menu "Misc commands"
1362 bool "Enable 'bmp' command"
1363 depends on LCD || DM_VIDEO || VIDEO
1365 This provides a way to obtain information about a BMP-format iamge
1366 and to display it. BMP (which presumably stands for BitMaP) is a
1367 file format defined by Microsoft which supports images of various
1368 depths, formats and compression methods. Headers on the file
1369 determine the formats used. This command can be used by first loading
1370 the image into RAM, then using this command to look at it or display
1373 config CMD_BOOTCOUNT
1375 depends on BOOTCOUNT_LIMIT
1377 Enable the bootcount command, which allows interrogation and
1378 reset of the bootcounter.
1381 bool "Enable board-specific commands"
1383 (deprecated: instead, please define a Kconfig option for each command)
1385 Some boards have board-specific commands which are only enabled
1386 during developemnt and need to be turned off for production. This
1387 option provides a way to control this. The commands that are enabled
1388 vary depending on the board.
1390 config CMD_BKOPS_ENABLE
1391 bool "mmc bkops enable"
1395 Enable command for setting manual background operations handshake
1396 on a eMMC device. The feature is optionally available on eMMC devices
1397 conforming to standard >= 4.41.
1399 config CMD_BLOCK_CACHE
1400 bool "blkcache - control and stats for block cache"
1401 depends on BLOCK_CACHE
1402 default y if BLOCK_CACHE
1404 Enable the blkcache command, which can be used to control the
1405 operation of the cache functions.
1406 This is most useful when fine-tuning the operation of the cache
1407 during development, but also allows the cache to be disabled when
1408 it might hurt performance (e.g. when using the ums command).
1411 bool "icache or dcache"
1413 Enable the "icache" and "dcache" commands
1415 config CMD_CONITRACE
1416 bool "conitrace - trace console input codes"
1418 Enable the 'conitrace' command which displays the codes received
1419 from the console input as hexadecimal numbers.
1422 bool "Enable clear screen command 'cls'"
1423 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1426 Enable the 'cls' command which clears the screen contents
1427 on video frame buffer.
1430 bool "Enable the 'display' command, for character displays"
1432 (this needs porting to driver model)
1433 This enables the 'display' command which allows a string to be
1434 displayed on a simple board-specific display. Implement
1435 display_putc() to use it.
1438 bool "efidebug - display/configure UEFI environment"
1439 depends on EFI_LOADER
1442 Enable the 'efidebug' command which provides a subset of UEFI
1443 shell utility with simplified functionality. It will be useful
1444 particularly for managing boot parameters as well as examining
1445 various EFI status for debugging.
1452 Enable the 'led' command which allows for control of LEDs supported
1453 by the board. The LEDs can be listed with 'led list' and controlled
1454 with led on/off/togle/blink. Any LED drivers can be controlled with
1455 this command, e.g. led_gpio.
1461 Enable the 'date' command for getting/setting the time/date in RTC
1467 Run commands and summarize execution time.
1470 bool "gettime - read elapsed time"
1472 Enable the 'gettime' command which reads the elapsed time since
1473 U-Boot started running. This shows the time in seconds and
1474 milliseconds. See also the 'bootstage' command which provides more
1475 flexibility for boot timing.
1477 # TODO: rename to CMD_SLEEP
1482 Delay execution for some time
1485 bool "support for multiprocessor"
1487 This provides an option to brinup
1488 different processors in multiprocessor
1494 Access the system timer.
1500 This provides basic access to the U-Boot's sound support. The main
1501 feature is to play a beep.
1503 sound init - set up sound system
1504 sound play - play a sound
1510 This provides access to the QEMU firmware interface. The main
1511 feature is to allow easy loading of files passed to qemu-system
1512 via -kernel / -initrd
1514 source "cmd/mvebu/Kconfig"
1517 bool "terminal - provides a way to attach a serial terminal"
1519 Provides a 'cu'-like serial terminal command. This can be used to
1520 access other serial ports from the system console. The terminal
1521 is very simple with no special processing of characters. As with
1522 cu, you can press ~. (tilde followed by period) to exit.
1525 bool "uuid, guid - generation of unique IDs"
1528 This enables two commands:
1530 uuid - generate random Universally Unique Identifier
1531 guid - generate Globally Unique Identifier based on random UUID
1533 The two commands are very similar except for the endianness of the
1538 source "cmd/ti/Kconfig"
1540 config CMD_BOOTSTAGE
1541 bool "Enable the 'bootstage' command"
1542 depends on BOOTSTAGE
1544 Add a 'bootstage' command which supports printing a report
1545 and un/stashing of bootstage data.
1547 menu "Power commands"
1549 bool "Enable Driver Model PMIC command"
1552 This is the pmic command, based on a driver model pmic's API.
1553 Command features are unchanged:
1554 - list - list pmic devices
1555 - pmic dev <id> - show or [set] operating pmic device (NEW)
1556 - pmic dump - dump registers
1557 - pmic read address - read byte of register at address
1558 - pmic write address - write byte to register at address
1559 The only one change for this command is 'dev' subcommand.
1561 config CMD_REGULATOR
1562 bool "Enable Driver Model REGULATOR command"
1563 depends on DM_REGULATOR
1565 This command is based on driver model regulator's API.
1566 User interface features:
1567 - list - list regulator devices
1568 - regulator dev <id> - show or [set] operating regulator device
1569 - regulator info - print constraints info
1570 - regulator status - print operating status
1571 - regulator value <val] <-f> - print/[set] voltage value [uV]
1572 - regulator current <val> - print/[set] current value [uA]
1573 - regulator mode <id> - print/[set] operating mode id
1574 - regulator enable - enable the regulator output
1575 - regulator disable - disable the regulator output
1577 The '-f' (force) option can be used for set the value which exceeds
1578 the limits, which are found in device-tree and are kept in regulator's
1579 uclass platdata structure.
1583 menu "Security commands"
1585 bool "Enable the 'aes' command"
1588 This provides a means to encrypt and decrypt data using the AES
1589 (Advanced Encryption Standard). This algorithm uses a symetric key
1590 and is widely used as a streaming cipher. Different key lengths are
1591 supported by the algorithm but this command only supports 128 bits
1595 bool "Enable the 'blob' command"
1597 This is used with the Freescale secure boot mechanism.
1599 Freescale's SEC block has built-in Blob Protocol which provides
1600 a method for protecting user-defined data across system power
1601 cycles. SEC block protects data in a data structure called a Blob,
1602 which provides both confidentiality and integrity protection.
1604 Encapsulating data as a blob
1605 Each time that the Blob Protocol is used to protect data, a
1606 different randomly generated key is used to encrypt the data.
1607 This random key is itself encrypted using a key which is derived
1608 from SoC's non-volatile secret key and a 16 bit Key identifier.
1609 The resulting encrypted key along with encrypted data is called a
1610 blob. The non-volatile secure key is available for use only during
1613 During decapsulation, the reverse process is performed to get back
1617 blob enc - encapsulating data as a cryptgraphic blob
1618 blob dec - decapsulating cryptgraphic blob to get the data
1622 blob enc src dst len km
1624 Encapsulate and create blob of data $len bytes long
1625 at address $src and store the result at address $dst.
1626 $km is the 16 byte key modifier is also required for
1627 generation/use as key for cryptographic operation. Key
1628 modifier should be 16 byte long.
1630 blob dec src dst len km
1632 Decapsulate the blob of data at address $src and
1633 store result of $len byte at addr $dst.
1634 $km is the 16 byte key modifier is also required for
1635 generation/use as key for cryptographic operation. Key
1636 modifier should be 16 byte long.
1639 bool "Support 'hash' command"
1642 This provides a way to hash data in memory using various supported
1643 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1644 saved to memory or to an environment variable. It is also possible
1645 to verify a hash against data in memory.
1648 bool "Support the 'hvc' command"
1649 depends on ARM_SMCCC
1651 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1652 development and testing.
1655 bool "Support the 'smc' command"
1656 depends on ARM_SMCCC
1658 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1659 development and testing.
1665 Add -v option to verify data against a hash.
1675 bool "Enable the 'tpm' command"
1676 depends on TPM_V1 || TPM_V2
1677 select CMD_TPM_V1 if TPM_V1
1678 select CMD_TPM_V2 if TPM_V2
1680 This provides a means to talk to a TPM from the command line. A wide
1681 range of commands if provided - see 'tpm help' for details. The
1682 command requires a suitable TPM on your board and the correct driver
1688 bool "Enable the 'tpm test' command"
1691 This provides a a series of tests to confirm that the TPMv1.x is
1692 working correctly. The tests cover initialisation, non-volatile RAM,
1693 extend, global lock and checking that timing is within expectations.
1694 The tests pass correctly on Infineon TPMs but may need to be adjusted
1701 menu "Firmware commands"
1703 bool "Enable crosec command"
1707 Enable command-line access to the Chrome OS EC (Embedded
1708 Controller). This provides the 'crosec' command which has
1709 a number of sub-commands for performing EC tasks such as
1710 updating its flash, accessing a small saved context area
1711 and talking to the I2C bus behind the EC (if there is one).
1714 menu "Filesystem commands"
1716 bool "Enable the 'btrsubvol' command"
1719 This enables the 'btrsubvol' command to list subvolumes
1720 of a BTRFS filesystem. There are no special commands for
1721 listing BTRFS directories or loading BTRFS files - this
1722 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1723 when BTRFS is enabled (see FS_BTRFS).
1726 bool "Enable the 'cbfs' command"
1729 Define this to enable support for reading from a Coreboot
1730 filesystem. This is a ROM-based filesystem used for accessing files
1731 on systems that use coreboot as the first boot-loader and then load
1732 U-Boot to actually boot the Operating System. Available commands are
1733 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1736 bool "Enable the 'cramfs' command"
1737 depends on FS_CRAMFS
1739 This provides commands for dealing with CRAMFS (Compressed ROM
1740 filesystem). CRAMFS is useful when space is tight since files are
1741 compressed. Two commands are provided:
1743 cramfsls - lists files in a cramfs image
1744 cramfsload - loads a file from a cramfs image
1747 bool "ext2 command support"
1750 Enables EXT2 FS command
1753 bool "ext4 command support"
1756 Enables EXT4 FS command
1758 config CMD_EXT4_WRITE
1760 bool "ext4 write command support"
1763 Enables EXT4 FS write command
1766 bool "FAT command support"
1769 Support for the FAT fs
1771 config CMD_FS_GENERIC
1772 bool "filesystem commands"
1774 Enables filesystem commands (e.g. load, ls) that work for multiple
1778 bool "fsuuid command"
1780 Enables fsuuid command for filesystem UUID.
1783 bool "jffs2 command"
1786 Enables commands to support the JFFS2 (Journalling Flash File System
1787 version 2) filesystem. This enables fsload, ls and fsinfo which
1788 provide the ability to load files, list directories and obtain
1789 filesystem information.
1792 bool "MTD partition support"
1793 select MTD_DEVICE if (CMD_NAND || NAND)
1795 MTD partitioning tool support.
1796 It is strongly encouraged to avoid using this command
1797 anymore along with 'sf', 'nand', 'onenand'. One can still
1798 declare the partitions in the mtdparts environment variable
1799 but better use the MTD stack and the 'mtd' command instead.
1801 config MTDIDS_DEFAULT
1802 string "Default MTD IDs"
1803 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1805 Defines a default MTD IDs list for use with MTD partitions in the
1806 Linux MTD command line partitions format.
1808 config MTDPARTS_DEFAULT
1809 string "Default MTD partition scheme"
1810 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1812 Defines a default MTD partitioning scheme in the Linux MTD command
1813 line partitions format
1815 config CMD_MTDPARTS_SPREAD
1816 bool "Padd partition size to take account of bad blocks"
1817 depends on CMD_MTDPARTS
1819 This enables the 'spread' sub-command of the mtdparts command.
1820 This command will modify the existing mtdparts variable by increasing
1821 the size of the partitions such that 1) each partition's net size is
1822 at least as large as the size specified in the mtdparts variable and
1823 2) each partition starts on a good block.
1826 bool "reiser - Access to reiserfs filesystems"
1828 This provides two commands which operate on a resierfs filesystem,
1829 commonly used some years ago:
1831 reiserls - list files
1832 reiserload - load a file
1835 bool "yaffs2 - Access of YAFFS2 filesystem"
1839 This provides commands for accessing a YAFFS2 filesystem. Yet
1840 Another Flash Filesystem 2 is a filesystem designed specifically
1841 for NAND flash. It incorporates bad-block management and ensures
1842 that device writes are sequential regardless of filesystem
1846 bool "zfs - Access of ZFS filesystem"
1848 This provides commands to accessing a ZFS filesystem, commonly used
1849 on Solaris systems. Two sub-commands are provided:
1851 zfsls - list files in a directory
1852 zfsload - load a file
1854 See doc/README.zfs for more details.
1858 menu "Debug commands"
1863 The bedbug (emBEDded deBUGger) command provides debugging features
1864 for some PowerPC processors. For details please see the
1865 docuemntation in doc/README.beddbug
1868 bool "diag - Board diagnostics"
1870 This command provides access to board diagnostic tests. These are
1871 called Power-on Self Tests (POST). The command allows listing of
1872 available tests and running either all the tests, or specific tests
1876 bool "irq - Show information about interrupts"
1877 depends on !ARM && !MIPS && !SH
1879 This enables two commands:
1881 interrupts - enable or disable interrupts
1882 irqinfo - print device-specific interrupt information
1885 bool "kgdb - Allow debugging of U-Boot with gdb"
1888 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1889 over a serial link for debugging purposes. This allows
1890 single-stepping, inspecting variables, etc. This is supported only
1891 on PowerPC at present.
1894 bool "log - Generation, control and access to logging"
1897 This provides access to logging features. It allows the output of
1898 log data to be controlled to a limited extent (setting up the default
1899 maximum log level for emitting of records). It also provides access
1900 to a command used for testing the log system.
1903 bool "trace - Support tracing of function calls and timing"
1905 Enables a command to control using of function tracing within
1906 U-Boot. This allows recording of call traces including timing
1907 information. The command can write data to memory for exporting
1908 for analysis (e.g. using bootchart). See doc/README.trace for full
1912 bool "avb - Android Verified Boot 2.0 operations"
1913 depends on AVB_VERIFY
1916 Enables a "avb" command to perform verification of partitions using
1917 Android Verified Boot 2.0 functionality. It includes such subcommands:
1918 avb init - initialize avb2 subsystem
1919 avb read_rb - read rollback index
1920 avb write_rb - write rollback index
1921 avb is_unlocked - check device lock state
1922 avb get_uuid - read and print uuid of a partition
1923 avb read_part - read data from partition
1924 avb read_part_hex - read data from partition and output to stdout
1925 avb write_part - write data to partition
1926 avb verify - run full verification chain
1930 tristate "Enable UBI - Unsorted block images commands"
1934 UBI is a software layer above MTD layer which admits use of LVM-like
1935 logical volumes on top of MTD devices, hides some complexities of
1936 flash chips like wear and bad blocks and provides some other useful
1937 capabilities. Please, consult the MTD web site for more details
1938 (www.linux-mtd.infradead.org). Activate this option if you want
1939 to use U-Boot UBI commands.
1940 It is also strongly encouraged to also enable CONFIG_MTD to get full
1944 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1946 default y if CMD_UBI
1950 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob