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.
140 source "cmd/fastboot/Kconfig"
160 Print ".config" contents.
162 If this option is enabled, the ".config" file contents are embedded
163 in the U-Boot image and can be printed on the console by the "config"
164 command. This provides information of which options are enabled on
171 Print console devices and information.
176 Print information about available CPUs. This normally shows the
177 number of CPUs, type (e.g. manufacturer, architecture, product or
178 internal name) and clock frequency. Other information may be
179 available depending on the CPU driver.
185 Print GPL license text
201 Run the command stored in the environment "bootcmd", i.e.
202 "bootd" does the same thing as "run bootcmd".
208 Boot an application image from the memory.
213 Boot the Linux zImage
220 Boot an AArch64 Linux Kernel image from memory.
224 depends on EFI_LOADER
227 Boot an EFI image from memory.
229 config CMD_BOOTEFI_HELLO_COMPILE
230 bool "Compile a standard EFI hello world binary for testing"
231 depends on CMD_BOOTEFI && (ARM || X86)
234 This compiles a standard EFI hello world application with U-Boot so
235 that it can be used with the test/py testing framework. This is useful
236 for testing that EFI is working at a basic level, and for bringing
237 up EFI support on a new architecture.
239 No additional space will be required in the resulting U-Boot binary
240 when this option is enabled.
242 config CMD_BOOTEFI_HELLO
243 bool "Allow booting a standard EFI hello world for testing"
244 depends on CMD_BOOTEFI_HELLO_COMPILE
246 This adds a standard EFI hello world application to U-Boot so that
247 it can be used with the 'bootefi hello' command. This is useful
248 for testing that EFI is working at a basic level, and for bringing
249 up EFI support on a new architecture.
251 source lib/efi_selftest/Kconfig
257 Add an ANSI terminal boot menu command.
260 bool "bootelf, bootvx"
263 Boot an ELF/vxWorks image from the memory.
266 bool "Flattened Device Tree utility commands"
270 Do FDT related setup before booting into the Operating System.
276 Start an application at a given address.
282 Run the command in the given environment variable.
288 Print header information for application image.
293 List all images found in flash
299 Extract a part of a multi-image.
304 Poweroff/Shutdown the system
307 bool "spl export - Export boot information for Falcon boot"
310 Falcon mode allows booting directly from SPL into an Operating
311 System such as Linux, thus skipping U-Boot proper. See
312 doc/README.falcon for full information about how to use this
315 config CMD_SPL_NAND_OFS
316 hex "Offset of OS command line args for Falcon-mode NAND boot"
320 This provides the offset of the command line arguments for Linux
321 when booting from NAND in Falcon mode. See doc/README.falcon
322 for full information about how to use this option (and also see
323 board/gateworks/gw_ventana/README for an example).
325 config CMD_SPL_WRITE_SIZE
326 hex "Size of argument area"
330 This provides the size of the command-line argument area in NAND
331 flash used by Falcon-mode boot. See the documentation until CMD_SPL
335 bool "fitImage update command"
337 Implements the 'fitupd' command, which allows to automatically
338 store software updates present on a TFTP server in NOR Flash
340 config CMD_THOR_DOWNLOAD
341 bool "thor - TIZEN 'thor' download"
343 Implements the 'thor' download protocol. This is a way of
344 downloading a software update over USB from an attached host.
345 There is no documentation about this within the U-Boot source code
346 but you should be able to find something on the interwebs.
349 bool "zboot - x86 boot command"
351 With x86 machines it is common to boot a bzImage file which
352 contains both a kernel and a setup.bin file. The latter includes
353 configuration information from the dark ages which x86 boards still
354 need to pick things out of.
356 Consider using FIT in preference to this since it supports directly
357 booting both 32- and 64-bit kernels, as well as secure boot.
358 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
362 menu "Environment commands"
365 bool "ask for env variable"
367 Ask for environment variable
385 Edit environment variable.
390 Allow for searching environment variables
396 Save all environment variables into the compiled-in persistent
399 config CMD_ENV_EXISTS
403 Check if a variable is defined in the environment for use in
406 config CMD_ENV_CALLBACK
407 bool "env callbacks - print callbacks and their associated variables"
409 Some environment variable have callbacks defined by
410 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
411 For example changing "baudrate" adjust the serial baud rate. This
412 command lists the currently defined callbacks.
415 bool "env flags -print variables that have non-default flags"
417 Some environment variables have special flags that control their
418 behaviour. For example, serial# can only be written once and cannot
419 be deleted. This command shows the variables that have special
424 menu "Memory commands"
429 Compute binary operations (xor, or, and) of byte arrays of arbitrary
430 size from memory and store the result in memory or the environment.
443 Add -v option to verify data against a crc32 checksum.
446 bool "eeprom - EEPROM subsystem"
448 (deprecated, needs conversion to driver model)
449 Provides commands to read and write EEPROM (Electrically Erasable
450 Programmable Read Only Memory) chips that are connected over an
453 config CMD_EEPROM_LAYOUT
454 bool "Enable layout-aware eeprom commands"
455 depends on CMD_EEPROM
457 (deprecated, needs conversion to driver model)
458 When enabled, additional eeprom sub-commands become available.
460 eeprom print - prints the contents of the eeprom in a human-readable
461 way (eeprom layout fields, and data formatted to be fit for human
464 eeprom update - allows user to update eeprom fields by specifying
465 the field name, and providing the new data in a human readable format
466 (same format as displayed by the eeprom print command).
468 Both commands can either auto detect the layout, or be told which
472 __weak int parse_layout_version(char *str)
473 - override to provide your own layout name parsing
474 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
476 - override to setup the layout metadata based on the version
477 __weak int eeprom_layout_detect(unsigned char *data)
478 - override to provide your own algorithm for detecting layout
481 - contains various printing and updating functions for common
482 types of eeprom fields. Can be used for defining
485 config EEPROM_LAYOUT_HELP_STRING
486 string "Tells user what layout names are supported"
487 depends on CMD_EEPROM_LAYOUT
488 default "<not defined>"
490 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
496 Infinite write loop on address range
503 Compute MD5 checksum.
508 depends on CMD_MD5SUM
510 Add -v option to verify data against an MD5 checksum.
515 Display memory information.
518 bool "md, mm, nm, mw, cp, cmp, base, loop"
523 mm - memory modify (auto-incrementing address)
524 nm - memory modify (constant address)
525 mw - memory write (fill)
528 base - print or set address offset
529 loop - initialize loop on address range
534 Simple RAM read/write test.
538 config SYS_ALT_MEMTEST
539 bool "Alternative test"
541 Use a more complete alternative memory test.
548 mdc - memory display cyclic
549 mwc - memory write cyclic
555 Compute SHA1 checksum.
557 config SHA1SUM_VERIFY
559 depends on CMD_SHA1SUM
561 Add -v option to verify data against a SHA1 checksum.
564 bool "strings - display strings in memory"
566 This works similarly to the Unix 'strings' command except that it
567 works with a memory range. String of printable characters found
568 within the range are displayed. The minimum number of characters
569 for a sequence to be considered a string can be provided.
573 menu "Compression commands"
577 default y if CMD_BOOTI
580 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
585 default y if CMD_BOOTI
587 Uncompress a zip-compressed memory region.
592 Compress a memory region with zlib deflate method.
596 menu "Device access commands"
599 #depends on FLASH_CFI_DRIVER
602 ARM Ltd reference designs flash partition access
605 bool "adc - Access Analog to Digital Converters info and data"
609 Shows ADC device info and permit printing one-shot analog converted
610 data from a named Analog to Digital Converter.
613 bool "clk - Show clock frequencies"
616 Shows clock frequences by calling a sock_clk_dump() hook function.
617 This is depreated in favour of using the CLK uclass and accessing
618 clock values from associated drivers. However currently no command
622 bool "demo - Demonstration commands for driver model"
625 Provides a 'demo' command which can be used to play around with
626 driver model. To use this properly you will need to enable one or
627 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
628 Otherwise you will always get an empty list of devices. The demo
629 devices are defined in the sandbox device tree, so the easiest
630 option is to use sandbox and pass the -d point to sandbox's
637 Enables the command "dfu" which is used to have U-Boot create a DFU
638 class device via USB. This command requires that the "dfu_alt_info"
639 environment variable be set and define the alt settings to expose to
643 bool "dm - Access to driver model information"
647 Provides access to driver model data structures and information,
648 such as a list of devices, list of uclasses and the state of each
649 device (e.g. activated). This is not required for operation, but
650 can be useful to see the state of driver model for debugging or
654 bool "fdcboot - Boot from floppy device"
656 The 'fdtboot' command allows booting an image from a floppy disk.
659 bool "flinfo, erase, protect"
663 flinfo - print FLASH memory information
665 protect - enable or disable FLASH write protection
674 config CMD_FPGA_LOADBP
675 bool "fpga loadbp - load partial bitstream (Xilinx only)"
678 Supports loading an FPGA device from a bitstream buffer containing
681 config CMD_FPGA_LOADFS
682 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
685 Supports loading an FPGA device from a FAT filesystem.
687 config CMD_FPGA_LOADMK
688 bool "fpga loadmk - load bitstream from image"
691 Supports loading an FPGA device from a image generated by mkimage.
693 config CMD_FPGA_LOADP
694 bool "fpga loadp - load partial bitstream"
697 Supports loading an FPGA device from a bitstream buffer containing
700 config CMD_FPGA_LOAD_SECURE
701 bool "fpga loads - loads secure bitstreams (Xilinx only)"
704 Enables the fpga loads command which is used to load secure
705 (authenticated or encrypted or both) bitstreams on to FPGA.
708 bool "fpgad - dump FPGA registers"
710 (legacy, needs conversion to driver model)
711 Provides a way to dump FPGA registers by calling the board-specific
712 fpga_get_reg() function. This functions similarly to the 'md'
716 bool "fuse - support for the fuse subssystem"
718 (deprecated - needs conversion to driver model)
719 This allows reading, sensing, programming or overriding fuses
720 which control the behaviour of the device. The command uses the
729 bool "GPT (GUID Partition Table) command"
730 select PARTITION_UUIDS
732 select HAVE_BLOCK_DEVICE
735 Enable the 'gpt' command to ready and write GPT style partition
739 bool "GPT Random UUID generation"
742 Enable the generation of partitions with random UUIDs if none
745 config CMD_GPT_RENAME
746 bool "GPT partition renaming commands"
749 Enables the 'gpt' command to interchange names on two GPT
750 partitions via the 'gpt swap' command or to rename single
751 partitions via the 'rename' command.
754 bool "ide - Support for IDE drivers"
757 Provides an 'ide' command which allows accessing the IDE drive,
758 reseting the IDE interface, printing the partition table and
759 geting device info. It also enables the 'diskboot' command which
760 permits booting from an IDE drive.
763 bool "io - Support for performing I/O accesses"
765 Provides an 'iod' command to display I/O space and an 'iow' command
766 to write values to the I/O space. This can be useful for manually
767 checking the state of devices during boot when debugging device
771 bool "iotrace - Support for tracing I/O activity"
773 Provides an 'iotrace' command which supports recording I/O reads and
774 writes in a trace buffer in memory . It also maintains a checksum
775 of the trace records (even if space is exhausted) so that the
776 sequence of I/O accesses can be verified.
778 When debugging drivers it is useful to see what I/O accesses were
779 done and in what order.
781 Even if the individual accesses are of little interest it can be
782 useful to verify that the access pattern is consistent each time
783 an operation is performed. In this case a checksum can be used to
784 characterise the operation of a driver. The checksum can be compared
785 across different runs of the operation to verify that the driver is
788 In particular, when performing major refactoring of the driver, where
789 the access pattern should not change, the checksum provides assurance
790 that the refactoring work has not broken the driver.
792 This works by sneaking into the io.h heder for an architecture and
793 redirecting I/O accesses through iotrace's tracing mechanism.
795 For now no commands are provided to examine the trace buffer. The
796 format is fairly simple, so 'md' is a reasonable substitute.
798 Note: The checksum feature is only useful for I/O regions where the
799 contents do not change outside of software control. Where this is not
800 suitable you can fall back to manually comparing the addresses. It
801 might be useful to enhance tracing to only checksum the accesses and
802 not the data read/written.
813 Load a binary file over serial line.
819 Load an S-Record file over serial line
824 MMC memory mapped support.
827 bool "Enable support for RPMB in the mmc command"
830 Enable the commands for reading, writing and programming the
831 key for the Replay Protection Memory Block partition in eMMC.
835 default y if NAND_SUNXI
840 config CMD_NAND_TRIMFFS
841 bool "nand write.trimffs"
842 default y if ARCH_SUNXI
844 Allows one to skip empty pages when flashing something on a NAND.
846 config CMD_NAND_LOCK_UNLOCK
847 bool "nand lock/unlock"
849 NAND locking support.
851 config CMD_NAND_TORTURE
854 NAND torture support.
863 NVM Express device support
866 bool "mmc_spi - Set up MMC SPI device"
868 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
869 Peripheral Interface) device. The device provides a means of
870 accessing an MMC device via SPI using a single data line, limited
871 to 20MHz. It is useful since it reduces the amount of protocol code
875 bool "onenand - access to onenand device"
877 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
878 various useful features. This command allows reading, writing,
879 and erasing blocks. It allso provides a way to show and change
880 bad blocks, and test the device.
884 select PARTITION_UUIDS
885 select HAVE_BLOCK_DEVICE
887 Read and display information about the partition table on
891 bool "pci - Access PCI devices"
893 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
894 used on some devices to allow the CPU to communicate with its
895 peripherals. Sub-commands allow bus enumeration, displaying and
896 changing configuration space and a few other features.
899 bool "pinit - Set up PCMCIA device"
901 Provides a means to initialise a PCMCIA (Personal Computer Memory
902 Card International Association) device. This is an old standard from
903 about 1990. These devices are typically removable memory or network
904 cards using a standard 68-pin connector.
907 bool "read - Read binary data from a partition"
909 Provides low-level access to the data in a partition.
911 config CMD_REMOTEPROC
913 depends on REMOTEPROC
915 Support for Remote Processor control
918 bool "sata - Access SATA subsystem"
921 SATA (Serial Advanced Technology Attachment) is a serial bus
922 standard for connecting to hard drives and other storage devices.
923 This command provides information about attached devices and allows
924 reading, writing and other operations.
926 SATA replaces PATA (originally just ATA), which stands for Parallel AT
927 Attachment, where AT refers to an IBM AT (Advanced Technology)
928 computer released in 1984.
931 bool "saves - Save a file over serial in S-Record format"
933 Provides a way to save a binary file using the Motorola S-Record
934 format over the serial line.
937 bool "scsi - Access to SCSI devices"
940 This provides a 'scsi' command which provides access to SCSI (Small
941 Computer System Interface) devices. The command provides a way to
942 scan the bus, reset the bus, read and write data and get information
946 bool "sdram - Print SDRAM configuration information"
948 Provides information about attached SDRAM. This assumed that the
949 SDRAM has an EEPROM with information that can be read using the
950 I2C bus. This is only available on some boards.
958 bool "sf test - Allow testing of SPI flash"
960 Provides a way to test that SPI flash is working correctly. The
961 test is destructive, in that an area of SPI flash must be provided
962 for the test to use. Performance information is also provided,
963 measuring the performance of reading, writing and erasing in
964 Mbps (Million Bits Per Second). This value should approximately
965 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
966 everything is working properly.
974 bool "tsi148 - Command to access tsi148 device"
976 This provides various sub-commands to initialise and configure the
977 Turndra tsi148 device. See the command help for full details.
980 bool "universe - Command to set up the Turndra Universe controller"
982 This allows setting up the VMEbus provided by this controller.
983 See the command help for full details.
987 select HAVE_BLOCK_DEVICE
993 select USB_FUNCTION_SDP
995 Enables the command "sdp" which is used to have U-Boot emulating the
996 Serial Download Protocol (SDP) via USB.
999 depends on USB_FUNCTION_ROCKUSB
1001 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1002 read/write info, image to/from devices. This enable rockusb command
1003 support to communication with rockusb device. for more detail about
1004 this command, please read doc/README.rockusb.
1006 config CMD_USB_MASS_STORAGE
1007 bool "UMS usb mass storage"
1008 select USB_FUNCTION_MASS_STORAGE
1010 USB mass storage support
1015 menu "Shell scripting commands"
1021 Echo args to console
1027 Return true/false on integer compare.
1033 Run script from memory
1039 Evaluate boolean and math expressions and store the result in an env
1041 Also supports loading the value at a memory location into a variable.
1042 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1049 bool "Network commands"
1058 bootp - boot image via network using BOOTP/TFTP protocol
1062 depends on CMD_BOOTP
1064 Boot image via network using DHCP/TFTP protocol
1066 config BOOTP_BOOTPATH
1067 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1069 depends on CMD_BOOTP
1071 Even though the config is called BOOTP_BOOTPATH, it stores the
1072 path in the variable 'rootpath'.
1075 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1077 depends on CMD_BOOTP
1079 The primary DNS server is stored as 'dnsip'. If two servers are
1080 returned, you must set BOOTP_DNS2 to store that second server IP
1084 bool "Store 'dnsip2' from BOOTP/DHCP server"
1085 depends on BOOTP_DNS
1087 If a DHCP client requests the DNS server IP from a DHCP server,
1088 it is possible that more than one DNS serverip is offered to the
1089 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1090 server IP will be stored in the additional environment
1091 variable "dnsip2". The first DNS serverip is always
1092 stored in the variable "dnsip", when BOOTP_DNS is defined.
1094 config BOOTP_GATEWAY
1095 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1097 depends on CMD_BOOTP
1099 config BOOTP_HOSTNAME
1100 bool "Request & store 'hostname' from BOOTP/DHCP server"
1102 depends on CMD_BOOTP
1104 The name may or may not be qualified with the local domain name.
1106 config BOOTP_SUBNETMASK
1107 bool "Request & store 'netmask' from BOOTP/DHCP server"
1109 depends on CMD_BOOTP
1111 config BOOTP_NTPSERVER
1112 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1113 depends on CMD_BOOTP
1116 bool "Send PXE client arch to BOOTP/DHCP server"
1118 depends on CMD_BOOTP && CMD_PXE
1120 Supported for ARM, ARM64, and x86 for now.
1122 config BOOTP_PXE_CLIENTARCH
1124 depends on BOOTP_PXE
1125 default 0x16 if ARM64
1129 config BOOTP_VCI_STRING
1131 depends on CMD_BOOTP
1132 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1133 default "U-Boot.armv8" if ARM64
1134 default "U-Boot.arm" if ARM
1141 tftpboot - boot image via network using TFTP protocol
1145 depends on CMD_TFTPBOOT
1147 TFTP put command, for uploading files to a server
1151 depends on CMD_TFTPBOOT
1153 Act as a TFTP server and boot the first received file
1155 config NET_TFTP_VARS
1156 bool "Control TFTP timeout and count through environment"
1157 depends on CMD_TFTPBOOT
1160 If set, allows controlling the TFTP timeout through the
1161 environment variable tftptimeout, and the TFTP maximum
1162 timeout count through the variable tftptimeoutcountmax.
1163 If unset, timeout and maximum are hard-defined as 1 second
1164 and 10 timouts per TFTP transfer.
1169 Boot image via network using RARP/TFTP protocol
1175 Boot image via network using NFS protocol.
1180 Enable MII utility commands.
1185 Send ICMP ECHO_REQUEST to network host
1190 Perform CDP network configuration
1195 Synchronize RTC via network
1200 Lookup the IP of a hostname
1202 config CMD_LINK_LOCAL
1205 Acquire a network IP address using the link-local protocol
1212 Allow control of L2 Ethernet switch commands. These are supported
1213 by the vsc9953 Ethernet driver at present. Sub-commands allow
1214 operations such as enabling / disabling a port and
1215 viewing/maintaining the filtering database (FDB)
1221 Boot image via network using PXE protocol
1225 menu "Misc commands"
1228 bool "Enable 'bmp' command"
1229 depends on LCD || DM_VIDEO || VIDEO
1231 This provides a way to obtain information about a BMP-format iamge
1232 and to display it. BMP (which presumably stands for BitMaP) is a
1233 file format defined by Microsoft which supports images of various
1234 depths, formats and compression methods. Headers on the file
1235 determine the formats used. This command can be used by first loading
1236 the image into RAM, then using this command to look at it or display
1239 config CMD_BOOTCOUNT
1241 depends on BOOTCOUNT_LIMIT
1243 Enable the bootcount command, which allows interrogation and
1244 reset of the bootcounter.
1247 bool "Enable board-specific commands"
1249 (deprecated: instead, please define a Kconfig option for each command)
1251 Some boards have board-specific commands which are only enabled
1252 during developemnt and need to be turned off for production. This
1253 option provides a way to control this. The commands that are enabled
1254 vary depending on the board.
1256 config CMD_BKOPS_ENABLE
1257 bool "mmc bkops enable"
1261 Enable command for setting manual background operations handshake
1262 on a eMMC device. The feature is optionally available on eMMC devices
1263 conforming to standard >= 4.41.
1265 config CMD_BLOCK_CACHE
1266 bool "blkcache - control and stats for block cache"
1267 depends on BLOCK_CACHE
1268 default y if BLOCK_CACHE
1270 Enable the blkcache command, which can be used to control the
1271 operation of the cache functions.
1272 This is most useful when fine-tuning the operation of the cache
1273 during development, but also allows the cache to be disabled when
1274 it might hurt performance (e.g. when using the ums command).
1277 bool "icache or dcache"
1279 Enable the "icache" and "dcache" commands
1282 bool "Enable the 'display' command, for character displays"
1284 (this needs porting to driver model)
1285 This enables the 'display' command which allows a string to be
1286 displayed on a simple board-specific display. Implement
1287 display_putc() to use it.
1293 Enable the 'led' command which allows for control of LEDs supported
1294 by the board. The LEDs can be listed with 'led list' and controlled
1295 with led on/off/togle/blink. Any LED drivers can be controlled with
1296 this command, e.g. led_gpio.
1302 Enable the 'date' command for getting/setting the time/date in RTC
1308 Run commands and summarize execution time.
1311 bool "gettime - read elapsed time"
1313 Enable the 'gettime' command which reads the elapsed time since
1314 U-Boot started running. This shows the time in seconds and
1315 milliseconds. See also the 'bootstage' command which provides more
1316 flexibility for boot timing.
1318 # TODO: rename to CMD_SLEEP
1323 Delay execution for some time
1328 Access the system timer.
1334 This provides basic access to the U-Boot's sound support. The main
1335 feature is to play a beep.
1337 sound init - set up sound system
1338 sound play - play a sound
1344 This provides access to the QEMU firmware interface. The main
1345 feature is to allow easy loading of files passed to qemu-system
1346 via -kernel / -initrd
1348 source "cmd/mvebu/Kconfig"
1351 bool "terminal - provides a way to attach a serial terminal"
1353 Provides a 'cu'-like serial terminal command. This can be used to
1354 access other serial ports from the system console. The terminal
1355 is very simple with no special processing of characters. As with
1356 cu, you can press ~. (tilde followed by period) to exit.
1359 bool "uuid, guid - generation of unique IDs"
1362 This enables two commands:
1364 uuid - generate random Universally Unique Identifier
1365 guid - generate Globally Unique Identifier based on random UUID
1367 The two commands are very similar except for the endianness of the
1372 source "cmd/ti/Kconfig"
1374 config CMD_BOOTSTAGE
1375 bool "Enable the 'bootstage' command"
1376 depends on BOOTSTAGE
1378 Add a 'bootstage' command which supports printing a report
1379 and un/stashing of bootstage data.
1381 menu "Power commands"
1383 bool "Enable Driver Model PMIC command"
1386 This is the pmic command, based on a driver model pmic's API.
1387 Command features are unchanged:
1388 - list - list pmic devices
1389 - pmic dev <id> - show or [set] operating pmic device (NEW)
1390 - pmic dump - dump registers
1391 - pmic read address - read byte of register at address
1392 - pmic write address - write byte to register at address
1393 The only one change for this command is 'dev' subcommand.
1395 config CMD_REGULATOR
1396 bool "Enable Driver Model REGULATOR command"
1397 depends on DM_REGULATOR
1399 This command is based on driver model regulator's API.
1400 User interface features:
1401 - list - list regulator devices
1402 - regulator dev <id> - show or [set] operating regulator device
1403 - regulator info - print constraints info
1404 - regulator status - print operating status
1405 - regulator value <val] <-f> - print/[set] voltage value [uV]
1406 - regulator current <val> - print/[set] current value [uA]
1407 - regulator mode <id> - print/[set] operating mode id
1408 - regulator enable - enable the regulator output
1409 - regulator disable - disable the regulator output
1411 The '-f' (force) option can be used for set the value which exceeds
1412 the limits, which are found in device-tree and are kept in regulator's
1413 uclass platdata structure.
1417 menu "Security commands"
1419 bool "Enable the 'aes' command"
1422 This provides a means to encrypt and decrypt data using the AES
1423 (Advanced Encryption Standard). This algorithm uses a symetric key
1424 and is widely used as a streaming cipher. Different key lengths are
1425 supported by the algorithm but this command only supports 128 bits
1429 bool "Enable the 'blob' command"
1431 This is used with the Freescale secure boot mechanism.
1433 Freescale's SEC block has built-in Blob Protocol which provides
1434 a method for protecting user-defined data across system power
1435 cycles. SEC block protects data in a data structure called a Blob,
1436 which provides both confidentiality and integrity protection.
1438 Encapsulating data as a blob
1439 Each time that the Blob Protocol is used to protect data, a
1440 different randomly generated key is used to encrypt the data.
1441 This random key is itself encrypted using a key which is derived
1442 from SoC's non-volatile secret key and a 16 bit Key identifier.
1443 The resulting encrypted key along with encrypted data is called a
1444 blob. The non-volatile secure key is available for use only during
1447 During decapsulation, the reverse process is performed to get back
1451 blob enc - encapsulating data as a cryptgraphic blob
1452 blob dec - decapsulating cryptgraphic blob to get the data
1456 blob enc src dst len km
1458 Encapsulate and create blob of data $len bytes long
1459 at address $src and store the result at address $dst.
1460 $km is the 16 byte key modifier is also required for
1461 generation/use as key for cryptographic operation. Key
1462 modifier should be 16 byte long.
1464 blob dec src dst len km
1466 Decapsulate the blob of data at address $src and
1467 store result of $len byte at addr $dst.
1468 $km is the 16 byte key modifier is also required for
1469 generation/use as key for cryptographic operation. Key
1470 modifier should be 16 byte long.
1473 bool "Support 'hash' command"
1476 This provides a way to hash data in memory using various supported
1477 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1478 saved to memory or to an environment variable. It is also possible
1479 to verify a hash against data in memory.
1482 bool "Support the 'hvc' command"
1483 depends on ARM_SMCCC
1485 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1486 development and testing.
1489 bool "Support the 'smc' command"
1490 depends on ARM_SMCCC
1492 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1493 development and testing.
1499 Add -v option to verify data against a hash.
1508 bool "Enable the 'tpm' command"
1509 depends on TPM_V1 || TPM_V2
1510 select CMD_TPM_V1 if TPM_V1
1511 select CMD_TPM_V2 if TPM_V2
1513 This provides a means to talk to a TPM from the command line. A wide
1514 range of commands if provided - see 'tpm help' for details. The
1515 command requires a suitable TPM on your board and the correct driver
1521 bool "Enable the 'tpm test' command"
1524 This provides a a series of tests to confirm that the TPMv1.x is
1525 working correctly. The tests cover initialisation, non-volatile RAM,
1526 extend, global lock and checking that timing is within expectations.
1527 The tests pass correctly on Infineon TPMs but may need to be adjusted
1534 menu "Firmware commands"
1536 bool "Enable crosec command"
1540 Enable command-line access to the Chrome OS EC (Embedded
1541 Controller). This provides the 'crosec' command which has
1542 a number of sub-commands for performing EC tasks such as
1543 updating its flash, accessing a small saved context area
1544 and talking to the I2C bus behind the EC (if there is one).
1547 menu "Filesystem commands"
1549 bool "Enable the 'btrsubvol' command"
1552 This enables the 'btrsubvol' command to list subvolumes
1553 of a BTRFS filesystem. There are no special commands for
1554 listing BTRFS directories or loading BTRFS files - this
1555 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1556 when BTRFS is enabled (see FS_BTRFS).
1559 bool "Enable the 'cbfs' command"
1562 Define this to enable support for reading from a Coreboot
1563 filesystem. This is a ROM-based filesystem used for accessing files
1564 on systems that use coreboot as the first boot-loader and then load
1565 U-Boot to actually boot the Operating System. Available commands are
1566 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1569 bool "Enable the 'cramfs' command"
1570 depends on FS_CRAMFS
1572 This provides commands for dealing with CRAMFS (Compressed ROM
1573 filesystem). CRAMFS is useful when space is tight since files are
1574 compressed. Two commands are provided:
1576 cramfsls - lists files in a cramfs image
1577 cramfsload - loads a file from a cramfs image
1580 bool "ext2 command support"
1583 Enables EXT2 FS command
1586 bool "ext4 command support"
1589 Enables EXT4 FS command
1591 config CMD_EXT4_WRITE
1593 bool "ext4 write command support"
1596 Enables EXT4 FS write command
1599 bool "FAT command support"
1602 Support for the FAT fs
1604 config CMD_FS_GENERIC
1605 bool "filesystem commands"
1607 Enables filesystem commands (e.g. load, ls) that work for multiple
1611 bool "fsuuid command"
1613 Enables fsuuid command for filesystem UUID.
1616 bool "jffs2 command"
1619 Enables commands to support the JFFS2 (Journalling Flash File System
1620 version 2) filesystem. This enables fsload, ls and fsinfo which
1621 provide the ability to load files, list directories and obtain
1622 filesystem information.
1625 bool "MTD partition support"
1627 MTD partition support
1629 config MTDIDS_DEFAULT
1630 string "Default MTD IDs"
1631 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1633 Defines a default MTD IDs list for use with MTD partitions in the
1634 Linux MTD command line partitions format.
1636 config MTDPARTS_DEFAULT
1637 string "Default MTD partition scheme"
1638 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1640 Defines a default MTD partitioning scheme in the Linux MTD command
1641 line partitions format
1643 config CMD_MTDPARTS_SPREAD
1644 bool "Padd partition size to take account of bad blocks"
1645 depends on CMD_MTDPARTS
1647 This enables the 'spread' sub-command of the mtdparts command.
1648 This command will modify the existing mtdparts variable by increasing
1649 the size of the partitions such that 1) each partition's net size is
1650 at least as large as the size specified in the mtdparts variable and
1651 2) each partition starts on a good block.
1654 bool "reiser - Access to reiserfs filesystems"
1656 This provides two commands which operate on a resierfs filesystem,
1657 commonly used some years ago:
1659 reiserls - list files
1660 reiserload - load a file
1663 bool "yaffs2 - Access of YAFFS2 filesystem"
1667 This provides commands for accessing a YAFFS2 filesystem. Yet
1668 Another Flash Filesystem 2 is a filesystem designed specifically
1669 for NAND flash. It incorporates bad-block management and ensures
1670 that device writes are sequential regardless of filesystem
1674 bool "zfs - Access of ZFS filesystem"
1676 This provides commands to accessing a ZFS filesystem, commonly used
1677 on Solaris systems. Two sub-commands are provided:
1679 zfsls - list files in a directory
1680 zfsload - load a file
1682 See doc/README.zfs for more details.
1686 menu "Debug commands"
1691 The bedbug (emBEDded deBUGger) command provides debugging features
1692 for some PowerPC processors. For details please see the
1693 docuemntation in doc/README.beddbug
1696 bool "diag - Board diagnostics"
1698 This command provides access to board diagnostic tests. These are
1699 called Power-on Self Tests (POST). The command allows listing of
1700 available tests and running either all the tests, or specific tests
1704 bool "irq - Show information about interrupts"
1705 depends on !ARM && !MIPS && !SH
1707 This enables two commands:
1709 interrupts - enable or disable interrupts
1710 irqinfo - print device-specific interrupt information
1713 bool "kgdb - Allow debugging of U-Boot with gdb"
1715 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1716 over a serial link for debugging purposes. This allows
1717 single-stepping, inspecting variables, etc. This is supported only
1718 on PowerPC at present.
1721 bool "log - Generation, control and access to logging"
1724 This provides access to logging features. It allows the output of
1725 log data to be controlled to a limited extent (setting up the default
1726 maximum log level for emitting of records). It also provides access
1727 to a command used for testing the log system.
1730 bool "trace - Support tracing of function calls and timing"
1732 Enables a command to control using of function tracing within
1733 U-Boot. This allows recording of call traces including timing
1734 information. The command can write data to memory for exporting
1735 for analsys (e.g. using bootchart). See doc/README.trace for full
1741 tristate "Enable UBI - Unsorted block images commands"
1745 default y if NAND_SUNXI
1747 UBI is a software layer above MTD layer which admits use of LVM-like
1748 logical volumes on top of MTD devices, hides some complexities of
1749 flash chips like wear and bad blocks and provides some other useful
1750 capabilities. Please, consult the MTD web site for more details
1751 (www.linux-mtd.infradead.org). Activate this option if you want
1752 to use U-Boot UBI commands.
1755 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1759 default y if CMD_UBI
1761 UBIFS is a file system for flash devices which works on top of UBI.
projects / u-boot / blob