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
425 menu "Memory commands"
430 Compute binary operations (xor, or, and) of byte arrays of arbitrary
431 size from memory and store the result in memory or the environment.
444 Add -v option to verify data against a crc32 checksum.
447 bool "eeprom - EEPROM subsystem"
448 depends on !DM_I2C || DM_I2C_COMPAT
450 (deprecated, needs conversion to driver model)
451 Provides commands to read and write EEPROM (Electrically Erasable
452 Programmable Read Only Memory) chips that are connected over an
455 config CMD_EEPROM_LAYOUT
456 bool "Enable layout-aware eeprom commands"
457 depends on CMD_EEPROM
459 (deprecated, needs conversion to driver model)
460 When enabled, additional eeprom sub-commands become available.
462 eeprom print - prints the contents of the eeprom in a human-readable
463 way (eeprom layout fields, and data formatted to be fit for human
466 eeprom update - allows user to update eeprom fields by specifying
467 the field name, and providing the new data in a human readable format
468 (same format as displayed by the eeprom print command).
470 Both commands can either auto detect the layout, or be told which
474 __weak int parse_layout_version(char *str)
475 - override to provide your own layout name parsing
476 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
478 - override to setup the layout metadata based on the version
479 __weak int eeprom_layout_detect(unsigned char *data)
480 - override to provide your own algorithm for detecting layout
483 - contains various printing and updating functions for common
484 types of eeprom fields. Can be used for defining
487 config EEPROM_LAYOUT_HELP_STRING
488 string "Tells user what layout names are supported"
489 depends on CMD_EEPROM_LAYOUT
490 default "<not defined>"
492 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
498 Infinite write loop on address range
505 Compute MD5 checksum.
510 depends on CMD_MD5SUM
512 Add -v option to verify data against an MD5 checksum.
517 Display memory information.
520 bool "md, mm, nm, mw, cp, cmp, base, loop"
525 mm - memory modify (auto-incrementing address)
526 nm - memory modify (constant address)
527 mw - memory write (fill)
530 base - print or set address offset
531 loop - initialize loop on address range
536 Simple RAM read/write test.
540 config SYS_ALT_MEMTEST
541 bool "Alternative test"
543 Use a more complete alternative memory test.
550 mdc - memory display cyclic
551 mwc - memory write cyclic
557 Compute SHA1 checksum.
559 config SHA1SUM_VERIFY
561 depends on CMD_SHA1SUM
563 Add -v option to verify data against a SHA1 checksum.
566 bool "strings - display strings in memory"
568 This works similarly to the Unix 'strings' command except that it
569 works with a memory range. String of printable characters found
570 within the range are displayed. The minimum number of characters
571 for a sequence to be considered a string can be provided.
575 menu "Compression commands"
579 default y if CMD_BOOTI
582 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
587 default y if CMD_BOOTI
589 Uncompress a zip-compressed memory region.
594 Compress a memory region with zlib deflate method.
598 menu "Device access commands"
601 #depends on FLASH_CFI_DRIVER
604 ARM Ltd reference designs flash partition access
607 bool "adc - Access Analog to Digital Converters info and data"
611 Shows ADC device info and permit printing one-shot analog converted
612 data from a named Analog to Digital Converter.
615 bool "bind/unbind - Bind or unbind a device to/from a driver"
618 Bind or unbind a device to/from a driver from the command line.
619 This is useful in situations where a device may be handled by several
620 drivers. For example, this can be used to bind a UDC to the usb ether
621 gadget driver from the command line.
624 bool "clk - Show clock frequencies"
627 Shows clock frequences by calling a sock_clk_dump() hook function.
628 This is depreated in favour of using the CLK uclass and accessing
629 clock values from associated drivers. However currently no command
633 bool "demo - Demonstration commands for driver model"
636 Provides a 'demo' command which can be used to play around with
637 driver model. To use this properly you will need to enable one or
638 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
639 Otherwise you will always get an empty list of devices. The demo
640 devices are defined in the sandbox device tree, so the easiest
641 option is to use sandbox and pass the -d point to sandbox's
648 Enables the command "dfu" which is used to have U-Boot create a DFU
649 class device via USB. This command requires that the "dfu_alt_info"
650 environment variable be set and define the alt settings to expose to
654 bool "dm - Access to driver model information"
657 Provides access to driver model data structures and information,
658 such as a list of devices, list of uclasses and the state of each
659 device (e.g. activated). This is not required for operation, but
660 can be useful to see the state of driver model for debugging or
664 bool "fastboot - Android fastboot support"
667 This enables the command "fastboot" which enables the Android
668 fastboot mode for the platform. Fastboot is a protocol for
669 downloading images, flashing and device control used on
670 Android devices. Fastboot requires either the network stack
671 enabled or support for acting as a USB device.
673 See doc/README.android-fastboot for more information.
676 bool "fdcboot - Boot from floppy device"
678 The 'fdtboot' command allows booting an image from a floppy disk.
681 bool "flinfo, erase, protect"
685 flinfo - print FLASH memory information
687 protect - enable or disable FLASH write protection
696 config CMD_FPGA_LOADBP
697 bool "fpga loadbp - load partial bitstream (Xilinx only)"
700 Supports loading an FPGA device from a bitstream buffer containing
703 config CMD_FPGA_LOADFS
704 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
707 Supports loading an FPGA device from a FAT filesystem.
709 config CMD_FPGA_LOADMK
710 bool "fpga loadmk - load bitstream from image"
713 Supports loading an FPGA device from a image generated by mkimage.
715 config CMD_FPGA_LOADP
716 bool "fpga loadp - load partial bitstream"
719 Supports loading an FPGA device from a bitstream buffer containing
722 config CMD_FPGA_LOAD_SECURE
723 bool "fpga loads - loads secure bitstreams (Xilinx only)"
726 Enables the fpga loads command which is used to load secure
727 (authenticated or encrypted or both) bitstreams on to FPGA.
730 bool "fpgad - dump FPGA registers"
732 (legacy, needs conversion to driver model)
733 Provides a way to dump FPGA registers by calling the board-specific
734 fpga_get_reg() function. This functions similarly to the 'md'
738 bool "fuse - support for the fuse subssystem"
740 (deprecated - needs conversion to driver model)
741 This allows reading, sensing, programming or overriding fuses
742 which control the behaviour of the device. The command uses the
751 bool "GPT (GUID Partition Table) command"
753 select HAVE_BLOCK_DEVICE
754 select PARTITION_UUIDS
757 Enable the 'gpt' command to ready and write GPT style partition
761 bool "GPT Random UUID generation"
764 Enable the generation of partitions with random UUIDs if none
767 config CMD_GPT_RENAME
768 bool "GPT partition renaming commands"
771 Enables the 'gpt' command to interchange names on two GPT
772 partitions via the 'gpt swap' command or to rename single
773 partitions via the 'rename' command.
776 bool "ide - Support for IDE drivers"
779 Provides an 'ide' command which allows accessing the IDE drive,
780 reseting the IDE interface, printing the partition table and
781 geting device info. It also enables the 'diskboot' command which
782 permits booting from an IDE drive.
785 bool "io - Support for performing I/O accesses"
787 Provides an 'iod' command to display I/O space and an 'iow' command
788 to write values to the I/O space. This can be useful for manually
789 checking the state of devices during boot when debugging device
793 bool "iotrace - Support for tracing I/O activity"
795 Provides an 'iotrace' command which supports recording I/O reads and
796 writes in a trace buffer in memory . It also maintains a checksum
797 of the trace records (even if space is exhausted) so that the
798 sequence of I/O accesses can be verified.
800 When debugging drivers it is useful to see what I/O accesses were
801 done and in what order.
803 Even if the individual accesses are of little interest it can be
804 useful to verify that the access pattern is consistent each time
805 an operation is performed. In this case a checksum can be used to
806 characterise the operation of a driver. The checksum can be compared
807 across different runs of the operation to verify that the driver is
810 In particular, when performing major refactoring of the driver, where
811 the access pattern should not change, the checksum provides assurance
812 that the refactoring work has not broken the driver.
814 This works by sneaking into the io.h heder for an architecture and
815 redirecting I/O accesses through iotrace's tracing mechanism.
817 For now no commands are provided to examine the trace buffer. The
818 format is fairly simple, so 'md' is a reasonable substitute.
820 Note: The checksum feature is only useful for I/O regions where the
821 contents do not change outside of software control. Where this is not
822 suitable you can fall back to manually comparing the addresses. It
823 might be useful to enhance tracing to only checksum the accesses and
824 not the data read/written.
834 bool "w1 - Support for Dallas 1-Wire protocol"
836 Dallas 1-wire protocol support
842 Load a binary file over serial line.
848 Load an S-Record file over serial line
853 MMC memory mapped support.
856 bool "Enable support for RPMB in the mmc command"
859 Enable the commands for reading, writing and programming the
860 key for the Replay Protection Memory Block partition in eMMC.
862 config CMD_MMC_SWRITE
864 depends on CMD_MMC && MMC_WRITE
867 Enable support for the "mmc swrite" command to write Android sparse
872 select MTD_PARTITIONS
874 MTD commands support.
878 default y if NAND_SUNXI
883 config CMD_NAND_TRIMFFS
884 bool "nand write.trimffs"
885 default y if ARCH_SUNXI
887 Allows one to skip empty pages when flashing something on a NAND.
889 config CMD_NAND_LOCK_UNLOCK
890 bool "nand lock/unlock"
892 NAND locking support.
894 config CMD_NAND_TORTURE
897 NAND torture support.
906 NVM Express device support
909 bool "mmc_spi - Set up MMC SPI device"
911 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
912 Peripheral Interface) device. The device provides a means of
913 accessing an MMC device via SPI using a single data line, limited
914 to 20MHz. It is useful since it reduces the amount of protocol code
918 bool "onenand - access to onenand device"
920 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
921 various useful features. This command allows reading, writing,
922 and erasing blocks. It allso provides a way to show and change
923 bad blocks, and test the device.
928 Enable the 'osd' command which allows to query information from and
929 write text data to a on-screen display (OSD) device; a virtual device
930 associated with a display capable of displaying a text overlay on the
931 display it's associated with..
935 select HAVE_BLOCK_DEVICE
936 select PARTITION_UUIDS
938 Read and display information about the partition table on
942 bool "pci - Access PCI devices"
944 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
945 used on some devices to allow the CPU to communicate with its
946 peripherals. Sub-commands allow bus enumeration, displaying and
947 changing configuration space and a few other features.
950 bool "pinit - Set up PCMCIA device"
952 Provides a means to initialise a PCMCIA (Personal Computer Memory
953 Card International Association) device. This is an old standard from
954 about 1990. These devices are typically removable memory or network
955 cards using a standard 68-pin connector.
958 bool "pinmux - show pins muxing"
961 Parse all available pin-controllers and show pins muxing. This
962 is useful for debug purpoer to check the pin muxing and to know if
963 a pin is configured as a GPIO or as an alternate function.
968 Poweroff/Shutdown the system
971 bool "read - Read binary data from a partition"
973 Provides low-level access to the data in a partition.
975 config CMD_REMOTEPROC
977 depends on REMOTEPROC
979 Support for Remote Processor control
982 bool "sata - Access SATA subsystem"
985 SATA (Serial Advanced Technology Attachment) is a serial bus
986 standard for connecting to hard drives and other storage devices.
987 This command provides information about attached devices and allows
988 reading, writing and other operations.
990 SATA replaces PATA (originally just ATA), which stands for Parallel AT
991 Attachment, where AT refers to an IBM AT (Advanced Technology)
992 computer released in 1984.
995 bool "saves - Save a file over serial in S-Record format"
997 Provides a way to save a binary file using the Motorola S-Record
998 format over the serial line.
1001 bool "scsi - Access to SCSI devices"
1004 This provides a 'scsi' command which provides access to SCSI (Small
1005 Computer System Interface) devices. The command provides a way to
1006 scan the bus, reset the bus, read and write data and get information
1010 bool "sdram - Print SDRAM configuration information"
1012 Provides information about attached SDRAM. This assumed that the
1013 SDRAM has an EEPROM with information that can be read using the
1014 I2C bus. This is only available on some boards.
1022 bool "sf test - Allow testing of SPI flash"
1024 Provides a way to test that SPI flash is working correctly. The
1025 test is destructive, in that an area of SPI flash must be provided
1026 for the test to use. Performance information is also provided,
1027 measuring the performance of reading, writing and erasing in
1028 Mbps (Million Bits Per Second). This value should approximately
1029 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1030 everything is working properly.
1035 SPI utility command.
1038 bool "tsi148 - Command to access tsi148 device"
1040 This provides various sub-commands to initialise and configure the
1041 Turndra tsi148 device. See the command help for full details.
1044 bool "universe - Command to set up the Turndra Universe controller"
1046 This allows setting up the VMEbus provided by this controller.
1047 See the command help for full details.
1051 select HAVE_BLOCK_DEVICE
1057 select USB_FUNCTION_SDP
1059 Enables the command "sdp" which is used to have U-Boot emulating the
1060 Serial Download Protocol (SDP) via USB.
1064 depends on USB_FUNCTION_ROCKUSB
1066 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1067 read/write info, image to/from devices. This enable rockusb command
1068 support to communication with rockusb device. for more detail about
1069 this command, please read doc/README.rockusb.
1071 config CMD_USB_MASS_STORAGE
1072 bool "UMS usb mass storage"
1073 select USB_FUNCTION_MASS_STORAGE
1075 USB mass storage support
1082 VirtIO block device support
1088 Enable the command "axi" for accessing AXI (Advanced eXtensible
1089 Interface) busses, a on-chip interconnect specification for managing
1090 functional blocks in SoC designs, which is also often used in designs
1091 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1095 menu "Shell scripting commands"
1101 Echo args to console
1107 Return true/false on integer compare.
1113 Run script from memory
1119 Evaluate boolean and math expressions and store the result in an env
1121 Also supports loading the value at a memory location into a variable.
1122 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1129 bool "Network commands"
1139 bootp - boot image via network using BOOTP/TFTP protocol
1143 depends on CMD_BOOTP
1145 Boot image via network using DHCP/TFTP protocol
1147 config BOOTP_BOOTPATH
1148 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1150 depends on CMD_BOOTP
1152 Even though the config is called BOOTP_BOOTPATH, it stores the
1153 path in the variable 'rootpath'.
1156 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1158 depends on CMD_BOOTP
1160 The primary DNS server is stored as 'dnsip'. If two servers are
1161 returned, you must set BOOTP_DNS2 to store that second server IP
1165 bool "Store 'dnsip2' from BOOTP/DHCP server"
1166 depends on BOOTP_DNS
1168 If a DHCP client requests the DNS server IP from a DHCP server,
1169 it is possible that more than one DNS serverip is offered to the
1170 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1171 server IP will be stored in the additional environment
1172 variable "dnsip2". The first DNS serverip is always
1173 stored in the variable "dnsip", when BOOTP_DNS is defined.
1175 config BOOTP_GATEWAY
1176 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1178 depends on CMD_BOOTP
1180 config BOOTP_HOSTNAME
1181 bool "Request & store 'hostname' from BOOTP/DHCP server"
1183 depends on CMD_BOOTP
1185 The name may or may not be qualified with the local domain name.
1187 config BOOTP_PREFER_SERVERIP
1188 bool "serverip variable takes precedent over DHCP server IP."
1189 depends on CMD_BOOTP
1191 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1193 With this option enabled, the 'serverip' variable in the environment
1194 takes precedence over DHCP server IP and will only be set by the DHCP
1195 server if not already set in the environment.
1197 config BOOTP_SUBNETMASK
1198 bool "Request & store 'netmask' from BOOTP/DHCP server"
1200 depends on CMD_BOOTP
1202 config BOOTP_NTPSERVER
1203 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1204 depends on CMD_BOOTP
1207 bool "Send PXE client arch to BOOTP/DHCP server"
1209 depends on CMD_BOOTP && CMD_PXE
1211 Supported for ARM, ARM64, and x86 for now.
1213 config BOOTP_PXE_CLIENTARCH
1215 depends on BOOTP_PXE
1216 default 0x16 if ARM64
1220 config BOOTP_VCI_STRING
1222 depends on CMD_BOOTP
1223 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1224 default "U-Boot.armv8" if ARM64
1225 default "U-Boot.arm" if ARM
1232 tftpboot - boot image via network using TFTP protocol
1236 depends on CMD_TFTPBOOT
1238 TFTP put command, for uploading files to a server
1242 depends on CMD_TFTPBOOT
1244 Act as a TFTP server and boot the first received file
1246 config NET_TFTP_VARS
1247 bool "Control TFTP timeout and count through environment"
1248 depends on CMD_TFTPBOOT
1251 If set, allows controlling the TFTP timeout through the
1252 environment variable tftptimeout, and the TFTP maximum
1253 timeout count through the variable tftptimeoutcountmax.
1254 If unset, timeout and maximum are hard-defined as 1 second
1255 and 10 timouts per TFTP transfer.
1260 Boot image via network using RARP/TFTP protocol
1266 Boot image via network using NFS protocol.
1271 Enable MII utility commands.
1276 Send ICMP ECHO_REQUEST to network host
1281 Perform CDP network configuration
1286 Synchronize RTC via network
1291 Lookup the IP of a hostname
1293 config CMD_LINK_LOCAL
1297 Acquire a network IP address using the link-local protocol
1304 Allow control of L2 Ethernet switch commands. These are supported
1305 by the vsc9953 Ethernet driver at present. Sub-commands allow
1306 operations such as enabling / disabling a port and
1307 viewing/maintaining the filtering database (FDB)
1313 Boot image via network using PXE protocol
1318 Wait for wake-on-lan Magic Packet
1322 menu "Misc commands"
1325 bool "Enable 'bmp' command"
1326 depends on LCD || DM_VIDEO || VIDEO
1328 This provides a way to obtain information about a BMP-format iamge
1329 and to display it. BMP (which presumably stands for BitMaP) is a
1330 file format defined by Microsoft which supports images of various
1331 depths, formats and compression methods. Headers on the file
1332 determine the formats used. This command can be used by first loading
1333 the image into RAM, then using this command to look at it or display
1336 config CMD_BOOTCOUNT
1338 depends on BOOTCOUNT_LIMIT
1340 Enable the bootcount command, which allows interrogation and
1341 reset of the bootcounter.
1344 bool "Enable board-specific commands"
1346 (deprecated: instead, please define a Kconfig option for each command)
1348 Some boards have board-specific commands which are only enabled
1349 during developemnt and need to be turned off for production. This
1350 option provides a way to control this. The commands that are enabled
1351 vary depending on the board.
1353 config CMD_BKOPS_ENABLE
1354 bool "mmc bkops enable"
1358 Enable command for setting manual background operations handshake
1359 on a eMMC device. The feature is optionally available on eMMC devices
1360 conforming to standard >= 4.41.
1362 config CMD_BLOCK_CACHE
1363 bool "blkcache - control and stats for block cache"
1364 depends on BLOCK_CACHE
1365 default y if BLOCK_CACHE
1367 Enable the blkcache command, which can be used to control the
1368 operation of the cache functions.
1369 This is most useful when fine-tuning the operation of the cache
1370 during development, but also allows the cache to be disabled when
1371 it might hurt performance (e.g. when using the ums command).
1374 bool "icache or dcache"
1376 Enable the "icache" and "dcache" commands
1378 config CMD_CONITRACE
1379 bool "conitrace - trace console input codes"
1381 Enable the 'conitrace' command which displays the codes received
1382 from the console input as hexadecimal numbers.
1385 bool "Enable clear screen command 'cls'"
1386 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1389 Enable the 'cls' command which clears the screen contents
1390 on video frame buffer.
1393 bool "Enable the 'display' command, for character displays"
1395 (this needs porting to driver model)
1396 This enables the 'display' command which allows a string to be
1397 displayed on a simple board-specific display. Implement
1398 display_putc() to use it.
1404 Enable the 'led' command which allows for control of LEDs supported
1405 by the board. The LEDs can be listed with 'led list' and controlled
1406 with led on/off/togle/blink. Any LED drivers can be controlled with
1407 this command, e.g. led_gpio.
1413 Enable the 'date' command for getting/setting the time/date in RTC
1419 Run commands and summarize execution time.
1422 bool "gettime - read elapsed time"
1424 Enable the 'gettime' command which reads the elapsed time since
1425 U-Boot started running. This shows the time in seconds and
1426 milliseconds. See also the 'bootstage' command which provides more
1427 flexibility for boot timing.
1429 # TODO: rename to CMD_SLEEP
1434 Delay execution for some time
1437 bool "support for multiprocessor"
1439 This provides an option to brinup
1440 different processors in multiprocessor
1446 Access the system timer.
1452 This provides basic access to the U-Boot's sound support. The main
1453 feature is to play a beep.
1455 sound init - set up sound system
1456 sound play - play a sound
1462 This provides access to the QEMU firmware interface. The main
1463 feature is to allow easy loading of files passed to qemu-system
1464 via -kernel / -initrd
1466 source "cmd/mvebu/Kconfig"
1469 bool "terminal - provides a way to attach a serial terminal"
1471 Provides a 'cu'-like serial terminal command. This can be used to
1472 access other serial ports from the system console. The terminal
1473 is very simple with no special processing of characters. As with
1474 cu, you can press ~. (tilde followed by period) to exit.
1477 bool "uuid, guid - generation of unique IDs"
1480 This enables two commands:
1482 uuid - generate random Universally Unique Identifier
1483 guid - generate Globally Unique Identifier based on random UUID
1485 The two commands are very similar except for the endianness of the
1490 source "cmd/ti/Kconfig"
1492 config CMD_BOOTSTAGE
1493 bool "Enable the 'bootstage' command"
1494 depends on BOOTSTAGE
1496 Add a 'bootstage' command which supports printing a report
1497 and un/stashing of bootstage data.
1499 menu "Power commands"
1501 bool "Enable Driver Model PMIC command"
1504 This is the pmic command, based on a driver model pmic's API.
1505 Command features are unchanged:
1506 - list - list pmic devices
1507 - pmic dev <id> - show or [set] operating pmic device (NEW)
1508 - pmic dump - dump registers
1509 - pmic read address - read byte of register at address
1510 - pmic write address - write byte to register at address
1511 The only one change for this command is 'dev' subcommand.
1513 config CMD_REGULATOR
1514 bool "Enable Driver Model REGULATOR command"
1515 depends on DM_REGULATOR
1517 This command is based on driver model regulator's API.
1518 User interface features:
1519 - list - list regulator devices
1520 - regulator dev <id> - show or [set] operating regulator device
1521 - regulator info - print constraints info
1522 - regulator status - print operating status
1523 - regulator value <val] <-f> - print/[set] voltage value [uV]
1524 - regulator current <val> - print/[set] current value [uA]
1525 - regulator mode <id> - print/[set] operating mode id
1526 - regulator enable - enable the regulator output
1527 - regulator disable - disable the regulator output
1529 The '-f' (force) option can be used for set the value which exceeds
1530 the limits, which are found in device-tree and are kept in regulator's
1531 uclass platdata structure.
1535 menu "Security commands"
1537 bool "Enable the 'aes' command"
1540 This provides a means to encrypt and decrypt data using the AES
1541 (Advanced Encryption Standard). This algorithm uses a symetric key
1542 and is widely used as a streaming cipher. Different key lengths are
1543 supported by the algorithm but this command only supports 128 bits
1547 bool "Enable the 'blob' command"
1549 This is used with the Freescale secure boot mechanism.
1551 Freescale's SEC block has built-in Blob Protocol which provides
1552 a method for protecting user-defined data across system power
1553 cycles. SEC block protects data in a data structure called a Blob,
1554 which provides both confidentiality and integrity protection.
1556 Encapsulating data as a blob
1557 Each time that the Blob Protocol is used to protect data, a
1558 different randomly generated key is used to encrypt the data.
1559 This random key is itself encrypted using a key which is derived
1560 from SoC's non-volatile secret key and a 16 bit Key identifier.
1561 The resulting encrypted key along with encrypted data is called a
1562 blob. The non-volatile secure key is available for use only during
1565 During decapsulation, the reverse process is performed to get back
1569 blob enc - encapsulating data as a cryptgraphic blob
1570 blob dec - decapsulating cryptgraphic blob to get the data
1574 blob enc src dst len km
1576 Encapsulate and create blob of data $len bytes long
1577 at address $src and store the result at address $dst.
1578 $km is the 16 byte key modifier is also required for
1579 generation/use as key for cryptographic operation. Key
1580 modifier should be 16 byte long.
1582 blob dec src dst len km
1584 Decapsulate the blob of data at address $src and
1585 store result of $len byte at addr $dst.
1586 $km is the 16 byte key modifier is also required for
1587 generation/use as key for cryptographic operation. Key
1588 modifier should be 16 byte long.
1591 bool "Support 'hash' command"
1594 This provides a way to hash data in memory using various supported
1595 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1596 saved to memory or to an environment variable. It is also possible
1597 to verify a hash against data in memory.
1600 bool "Support the 'hvc' command"
1601 depends on ARM_SMCCC
1603 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1604 development and testing.
1607 bool "Support the 'smc' command"
1608 depends on ARM_SMCCC
1610 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1611 development and testing.
1617 Add -v option to verify data against a hash.
1627 bool "Enable the 'tpm' command"
1628 depends on TPM_V1 || TPM_V2
1629 select CMD_TPM_V1 if TPM_V1
1630 select CMD_TPM_V2 if TPM_V2
1632 This provides a means to talk to a TPM from the command line. A wide
1633 range of commands if provided - see 'tpm help' for details. The
1634 command requires a suitable TPM on your board and the correct driver
1640 bool "Enable the 'tpm test' command"
1643 This provides a a series of tests to confirm that the TPMv1.x is
1644 working correctly. The tests cover initialisation, non-volatile RAM,
1645 extend, global lock and checking that timing is within expectations.
1646 The tests pass correctly on Infineon TPMs but may need to be adjusted
1653 menu "Firmware commands"
1655 bool "Enable crosec command"
1659 Enable command-line access to the Chrome OS EC (Embedded
1660 Controller). This provides the 'crosec' command which has
1661 a number of sub-commands for performing EC tasks such as
1662 updating its flash, accessing a small saved context area
1663 and talking to the I2C bus behind the EC (if there is one).
1666 menu "Filesystem commands"
1668 bool "Enable the 'btrsubvol' command"
1671 This enables the 'btrsubvol' command to list subvolumes
1672 of a BTRFS filesystem. There are no special commands for
1673 listing BTRFS directories or loading BTRFS files - this
1674 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1675 when BTRFS is enabled (see FS_BTRFS).
1678 bool "Enable the 'cbfs' command"
1681 Define this to enable support for reading from a Coreboot
1682 filesystem. This is a ROM-based filesystem used for accessing files
1683 on systems that use coreboot as the first boot-loader and then load
1684 U-Boot to actually boot the Operating System. Available commands are
1685 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1688 bool "Enable the 'cramfs' command"
1689 depends on FS_CRAMFS
1691 This provides commands for dealing with CRAMFS (Compressed ROM
1692 filesystem). CRAMFS is useful when space is tight since files are
1693 compressed. Two commands are provided:
1695 cramfsls - lists files in a cramfs image
1696 cramfsload - loads a file from a cramfs image
1699 bool "ext2 command support"
1702 Enables EXT2 FS command
1705 bool "ext4 command support"
1708 Enables EXT4 FS command
1710 config CMD_EXT4_WRITE
1712 bool "ext4 write command support"
1715 Enables EXT4 FS write command
1718 bool "FAT command support"
1721 Support for the FAT fs
1723 config CMD_FS_GENERIC
1724 bool "filesystem commands"
1726 Enables filesystem commands (e.g. load, ls) that work for multiple
1730 bool "fsuuid command"
1732 Enables fsuuid command for filesystem UUID.
1735 bool "jffs2 command"
1738 Enables commands to support the JFFS2 (Journalling Flash File System
1739 version 2) filesystem. This enables fsload, ls and fsinfo which
1740 provide the ability to load files, list directories and obtain
1741 filesystem information.
1744 bool "MTD partition support"
1745 select MTD_DEVICE if (CMD_NAND || NAND)
1747 MTD partitioning tool support.
1748 It is strongly encouraged to avoid using this command
1749 anymore along with 'sf', 'nand', 'onenand'. One can still
1750 declare the partitions in the mtdparts environment variable
1751 but better use the MTD stack and the 'mtd' command instead.
1753 config MTDIDS_DEFAULT
1754 string "Default MTD IDs"
1755 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1757 Defines a default MTD IDs list for use with MTD partitions in the
1758 Linux MTD command line partitions format.
1760 config MTDPARTS_DEFAULT
1761 string "Default MTD partition scheme"
1762 depends on MTD_PARTITIONS || CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1764 Defines a default MTD partitioning scheme in the Linux MTD command
1765 line partitions format
1767 config CMD_MTDPARTS_SPREAD
1768 bool "Padd partition size to take account of bad blocks"
1769 depends on CMD_MTDPARTS
1771 This enables the 'spread' sub-command of the mtdparts command.
1772 This command will modify the existing mtdparts variable by increasing
1773 the size of the partitions such that 1) each partition's net size is
1774 at least as large as the size specified in the mtdparts variable and
1775 2) each partition starts on a good block.
1778 bool "reiser - Access to reiserfs filesystems"
1780 This provides two commands which operate on a resierfs filesystem,
1781 commonly used some years ago:
1783 reiserls - list files
1784 reiserload - load a file
1787 bool "yaffs2 - Access of YAFFS2 filesystem"
1791 This provides commands for accessing a YAFFS2 filesystem. Yet
1792 Another Flash Filesystem 2 is a filesystem designed specifically
1793 for NAND flash. It incorporates bad-block management and ensures
1794 that device writes are sequential regardless of filesystem
1798 bool "zfs - Access of ZFS filesystem"
1800 This provides commands to accessing a ZFS filesystem, commonly used
1801 on Solaris systems. Two sub-commands are provided:
1803 zfsls - list files in a directory
1804 zfsload - load a file
1806 See doc/README.zfs for more details.
1810 menu "Debug commands"
1815 The bedbug (emBEDded deBUGger) command provides debugging features
1816 for some PowerPC processors. For details please see the
1817 docuemntation in doc/README.beddbug
1820 bool "diag - Board diagnostics"
1822 This command provides access to board diagnostic tests. These are
1823 called Power-on Self Tests (POST). The command allows listing of
1824 available tests and running either all the tests, or specific tests
1828 bool "irq - Show information about interrupts"
1829 depends on !ARM && !MIPS && !SH
1831 This enables two commands:
1833 interrupts - enable or disable interrupts
1834 irqinfo - print device-specific interrupt information
1837 bool "kgdb - Allow debugging of U-Boot with gdb"
1840 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1841 over a serial link for debugging purposes. This allows
1842 single-stepping, inspecting variables, etc. This is supported only
1843 on PowerPC at present.
1846 bool "log - Generation, control and access to logging"
1849 This provides access to logging features. It allows the output of
1850 log data to be controlled to a limited extent (setting up the default
1851 maximum log level for emitting of records). It also provides access
1852 to a command used for testing the log system.
1855 bool "trace - Support tracing of function calls and timing"
1857 Enables a command to control using of function tracing within
1858 U-Boot. This allows recording of call traces including timing
1859 information. The command can write data to memory for exporting
1860 for analsys (e.g. using bootchart). See doc/README.trace for full
1864 bool "avb - Android Verified Boot 2.0 operations"
1865 depends on AVB_VERIFY
1868 Enables a "avb" command to perform verification of partitions using
1869 Android Verified Boot 2.0 functionality. It includes such subcommands:
1870 avb init - initialize avb2 subsystem
1871 avb read_rb - read rollback index
1872 avb write_rb - write rollback index
1873 avb is_unlocked - check device lock state
1874 avb get_uuid - read and print uuid of a partition
1875 avb read_part - read data from partition
1876 avb read_part_hex - read data from partition and output to stdout
1877 avb write_part - write data to partition
1878 avb verify - run full verification chain
1882 tristate "Enable UBI - Unsorted block images commands"
1886 UBI is a software layer above MTD layer which admits use of LVM-like
1887 logical volumes on top of MTD devices, hides some complexities of
1888 flash chips like wear and bad blocks and provides some other useful
1889 capabilities. Please, consult the MTD web site for more details
1890 (www.linux-mtd.infradead.org). Activate this option if you want
1891 to use U-Boot UBI commands.
1892 It is also strongly encouraged to also enable CONFIG_MTD to get full
1896 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1898 default y if CMD_UBI
1902 UBIFS is a file system for flash devices which works on top of UBI.
git.openpandora.org / pandora-u-boot.git / blob