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 && (ARM || X86 || RISCV)
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.
310 Poweroff/Shutdown the system
313 bool "spl export - Export boot information for Falcon boot"
316 Falcon mode allows booting directly from SPL into an Operating
317 System such as Linux, thus skipping U-Boot proper. See
318 doc/README.falcon for full information about how to use this
321 config CMD_SPL_NAND_OFS
322 hex "Offset of OS command line args for Falcon-mode NAND boot"
326 This provides the offset of the command line arguments for Linux
327 when booting from NAND in Falcon mode. See doc/README.falcon
328 for full information about how to use this option (and also see
329 board/gateworks/gw_ventana/README for an example).
331 config CMD_SPL_WRITE_SIZE
332 hex "Size of argument area"
336 This provides the size of the command-line argument area in NAND
337 flash used by Falcon-mode boot. See the documentation until CMD_SPL
341 bool "fitImage update command"
343 Implements the 'fitupd' command, which allows to automatically
344 store software updates present on a TFTP server in NOR Flash
346 config CMD_THOR_DOWNLOAD
347 bool "thor - TIZEN 'thor' download"
349 Implements the 'thor' download protocol. This is a way of
350 downloading a software update over USB from an attached host.
351 There is no documentation about this within the U-Boot source code
352 but you should be able to find something on the interwebs.
355 bool "zboot - x86 boot command"
357 With x86 machines it is common to boot a bzImage file which
358 contains both a kernel and a setup.bin file. The latter includes
359 configuration information from the dark ages which x86 boards still
360 need to pick things out of.
362 Consider using FIT in preference to this since it supports directly
363 booting both 32- and 64-bit kernels, as well as secure boot.
364 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
368 menu "Environment commands"
371 bool "ask for env variable"
373 Ask for environment variable
391 Edit environment variable.
396 Allow for searching environment variables
402 Save all environment variables into the compiled-in persistent
405 config CMD_ENV_EXISTS
409 Check if a variable is defined in the environment for use in
412 config CMD_ENV_CALLBACK
413 bool "env callbacks - print callbacks and their associated variables"
415 Some environment variable have callbacks defined by
416 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
417 For example changing "baudrate" adjust the serial baud rate. This
418 command lists the currently defined callbacks.
421 bool "env flags -print variables that have non-default flags"
423 Some environment variables have special flags that control their
424 behaviour. For example, serial# can only be written once and cannot
425 be deleted. This command shows the variables that have special
430 menu "Memory commands"
435 Compute binary operations (xor, or, and) of byte arrays of arbitrary
436 size from memory and store the result in memory or the environment.
449 Add -v option to verify data against a crc32 checksum.
452 bool "eeprom - EEPROM subsystem"
454 (deprecated, needs conversion to driver model)
455 Provides commands to read and write EEPROM (Electrically Erasable
456 Programmable Read Only Memory) chips that are connected over an
459 config CMD_EEPROM_LAYOUT
460 bool "Enable layout-aware eeprom commands"
461 depends on CMD_EEPROM
463 (deprecated, needs conversion to driver model)
464 When enabled, additional eeprom sub-commands become available.
466 eeprom print - prints the contents of the eeprom in a human-readable
467 way (eeprom layout fields, and data formatted to be fit for human
470 eeprom update - allows user to update eeprom fields by specifying
471 the field name, and providing the new data in a human readable format
472 (same format as displayed by the eeprom print command).
474 Both commands can either auto detect the layout, or be told which
478 __weak int parse_layout_version(char *str)
479 - override to provide your own layout name parsing
480 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
482 - override to setup the layout metadata based on the version
483 __weak int eeprom_layout_detect(unsigned char *data)
484 - override to provide your own algorithm for detecting layout
487 - contains various printing and updating functions for common
488 types of eeprom fields. Can be used for defining
491 config EEPROM_LAYOUT_HELP_STRING
492 string "Tells user what layout names are supported"
493 depends on CMD_EEPROM_LAYOUT
494 default "<not defined>"
496 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
502 Infinite write loop on address range
509 Compute MD5 checksum.
514 depends on CMD_MD5SUM
516 Add -v option to verify data against an MD5 checksum.
521 Display memory information.
524 bool "md, mm, nm, mw, cp, cmp, base, loop"
529 mm - memory modify (auto-incrementing address)
530 nm - memory modify (constant address)
531 mw - memory write (fill)
534 base - print or set address offset
535 loop - initialize loop on address range
540 Simple RAM read/write test.
544 config SYS_ALT_MEMTEST
545 bool "Alternative test"
547 Use a more complete alternative memory test.
554 mdc - memory display cyclic
555 mwc - memory write cyclic
561 Compute SHA1 checksum.
563 config SHA1SUM_VERIFY
565 depends on CMD_SHA1SUM
567 Add -v option to verify data against a SHA1 checksum.
570 bool "strings - display strings in memory"
572 This works similarly to the Unix 'strings' command except that it
573 works with a memory range. String of printable characters found
574 within the range are displayed. The minimum number of characters
575 for a sequence to be considered a string can be provided.
579 menu "Compression commands"
583 default y if CMD_BOOTI
586 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
591 default y if CMD_BOOTI
593 Uncompress a zip-compressed memory region.
598 Compress a memory region with zlib deflate method.
602 menu "Device access commands"
605 #depends on FLASH_CFI_DRIVER
608 ARM Ltd reference designs flash partition access
611 bool "adc - Access Analog to Digital Converters info and data"
615 Shows ADC device info and permit printing one-shot analog converted
616 data from a named Analog to Digital Converter.
619 bool "clk - Show clock frequencies"
622 Shows clock frequences by calling a sock_clk_dump() hook function.
623 This is depreated in favour of using the CLK uclass and accessing
624 clock values from associated drivers. However currently no command
628 bool "demo - Demonstration commands for driver model"
631 Provides a 'demo' command which can be used to play around with
632 driver model. To use this properly you will need to enable one or
633 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
634 Otherwise you will always get an empty list of devices. The demo
635 devices are defined in the sandbox device tree, so the easiest
636 option is to use sandbox and pass the -d point to sandbox's
643 Enables the command "dfu" which is used to have U-Boot create a DFU
644 class device via USB. This command requires that the "dfu_alt_info"
645 environment variable be set and define the alt settings to expose to
649 bool "dm - Access to driver model information"
652 Provides access to driver model data structures and information,
653 such as a list of devices, list of uclasses and the state of each
654 device (e.g. activated). This is not required for operation, but
655 can be useful to see the state of driver model for debugging or
659 bool "fastboot - Android fastboot support"
662 This enables the command "fastboot" which enables the Android
663 fastboot mode for the platform. Fastboot is a protocol for
664 downloading images, flashing and device control used on
665 Android devices. Fastboot requires either the network stack
666 enabled or support for acting as a USB device.
668 See doc/README.android-fastboot for more information.
671 bool "fdcboot - Boot from floppy device"
673 The 'fdtboot' command allows booting an image from a floppy disk.
676 bool "flinfo, erase, protect"
680 flinfo - print FLASH memory information
682 protect - enable or disable FLASH write protection
691 config CMD_FPGA_LOADBP
692 bool "fpga loadbp - load partial bitstream (Xilinx only)"
695 Supports loading an FPGA device from a bitstream buffer containing
698 config CMD_FPGA_LOADFS
699 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
702 Supports loading an FPGA device from a FAT filesystem.
704 config CMD_FPGA_LOADMK
705 bool "fpga loadmk - load bitstream from image"
708 Supports loading an FPGA device from a image generated by mkimage.
710 config CMD_FPGA_LOADP
711 bool "fpga loadp - load partial bitstream"
714 Supports loading an FPGA device from a bitstream buffer containing
717 config CMD_FPGA_LOAD_SECURE
718 bool "fpga loads - loads secure bitstreams (Xilinx only)"
721 Enables the fpga loads command which is used to load secure
722 (authenticated or encrypted or both) bitstreams on to FPGA.
725 bool "fpgad - dump FPGA registers"
727 (legacy, needs conversion to driver model)
728 Provides a way to dump FPGA registers by calling the board-specific
729 fpga_get_reg() function. This functions similarly to the 'md'
733 bool "fuse - support for the fuse subssystem"
735 (deprecated - needs conversion to driver model)
736 This allows reading, sensing, programming or overriding fuses
737 which control the behaviour of the device. The command uses the
746 bool "GPT (GUID Partition Table) command"
748 select HAVE_BLOCK_DEVICE
749 select PARTITION_UUIDS
752 Enable the 'gpt' command to ready and write GPT style partition
756 bool "GPT Random UUID generation"
759 Enable the generation of partitions with random UUIDs if none
762 config CMD_GPT_RENAME
763 bool "GPT partition renaming commands"
766 Enables the 'gpt' command to interchange names on two GPT
767 partitions via the 'gpt swap' command or to rename single
768 partitions via the 'rename' command.
771 bool "ide - Support for IDE drivers"
774 Provides an 'ide' command which allows accessing the IDE drive,
775 reseting the IDE interface, printing the partition table and
776 geting device info. It also enables the 'diskboot' command which
777 permits booting from an IDE drive.
780 bool "io - Support for performing I/O accesses"
782 Provides an 'iod' command to display I/O space and an 'iow' command
783 to write values to the I/O space. This can be useful for manually
784 checking the state of devices during boot when debugging device
788 bool "iotrace - Support for tracing I/O activity"
790 Provides an 'iotrace' command which supports recording I/O reads and
791 writes in a trace buffer in memory . It also maintains a checksum
792 of the trace records (even if space is exhausted) so that the
793 sequence of I/O accesses can be verified.
795 When debugging drivers it is useful to see what I/O accesses were
796 done and in what order.
798 Even if the individual accesses are of little interest it can be
799 useful to verify that the access pattern is consistent each time
800 an operation is performed. In this case a checksum can be used to
801 characterise the operation of a driver. The checksum can be compared
802 across different runs of the operation to verify that the driver is
805 In particular, when performing major refactoring of the driver, where
806 the access pattern should not change, the checksum provides assurance
807 that the refactoring work has not broken the driver.
809 This works by sneaking into the io.h heder for an architecture and
810 redirecting I/O accesses through iotrace's tracing mechanism.
812 For now no commands are provided to examine the trace buffer. The
813 format is fairly simple, so 'md' is a reasonable substitute.
815 Note: The checksum feature is only useful for I/O regions where the
816 contents do not change outside of software control. Where this is not
817 suitable you can fall back to manually comparing the addresses. It
818 might be useful to enhance tracing to only checksum the accesses and
819 not the data read/written.
830 Load a binary file over serial line.
836 Load an S-Record file over serial line
841 MMC memory mapped support.
844 bool "Enable support for RPMB in the mmc command"
847 Enable the commands for reading, writing and programming the
848 key for the Replay Protection Memory Block partition in eMMC.
850 config CMD_MMC_SWRITE
852 depends on CMD_MMC && MMC_WRITE
855 Enable support for the "mmc swrite" command to write Android sparse
860 default y if NAND_SUNXI
865 config CMD_NAND_TRIMFFS
866 bool "nand write.trimffs"
867 default y if ARCH_SUNXI
869 Allows one to skip empty pages when flashing something on a NAND.
871 config CMD_NAND_LOCK_UNLOCK
872 bool "nand lock/unlock"
874 NAND locking support.
876 config CMD_NAND_TORTURE
879 NAND torture support.
888 NVM Express device support
891 bool "mmc_spi - Set up MMC SPI device"
893 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
894 Peripheral Interface) device. The device provides a means of
895 accessing an MMC device via SPI using a single data line, limited
896 to 20MHz. It is useful since it reduces the amount of protocol code
900 bool "onenand - access to onenand device"
902 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
903 various useful features. This command allows reading, writing,
904 and erasing blocks. It allso provides a way to show and change
905 bad blocks, and test the device.
909 select HAVE_BLOCK_DEVICE
910 select PARTITION_UUIDS
912 Read and display information about the partition table on
916 bool "pci - Access PCI devices"
918 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
919 used on some devices to allow the CPU to communicate with its
920 peripherals. Sub-commands allow bus enumeration, displaying and
921 changing configuration space and a few other features.
924 bool "pinit - Set up PCMCIA device"
926 Provides a means to initialise a PCMCIA (Personal Computer Memory
927 Card International Association) device. This is an old standard from
928 about 1990. These devices are typically removable memory or network
929 cards using a standard 68-pin connector.
932 bool "read - Read binary data from a partition"
934 Provides low-level access to the data in a partition.
936 config CMD_REMOTEPROC
938 depends on REMOTEPROC
940 Support for Remote Processor control
943 bool "sata - Access SATA subsystem"
946 SATA (Serial Advanced Technology Attachment) is a serial bus
947 standard for connecting to hard drives and other storage devices.
948 This command provides information about attached devices and allows
949 reading, writing and other operations.
951 SATA replaces PATA (originally just ATA), which stands for Parallel AT
952 Attachment, where AT refers to an IBM AT (Advanced Technology)
953 computer released in 1984.
956 bool "saves - Save a file over serial in S-Record format"
958 Provides a way to save a binary file using the Motorola S-Record
959 format over the serial line.
962 bool "scsi - Access to SCSI devices"
965 This provides a 'scsi' command which provides access to SCSI (Small
966 Computer System Interface) devices. The command provides a way to
967 scan the bus, reset the bus, read and write data and get information
971 bool "sdram - Print SDRAM configuration information"
973 Provides information about attached SDRAM. This assumed that the
974 SDRAM has an EEPROM with information that can be read using the
975 I2C bus. This is only available on some boards.
983 bool "sf test - Allow testing of SPI flash"
985 Provides a way to test that SPI flash is working correctly. The
986 test is destructive, in that an area of SPI flash must be provided
987 for the test to use. Performance information is also provided,
988 measuring the performance of reading, writing and erasing in
989 Mbps (Million Bits Per Second). This value should approximately
990 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
991 everything is working properly.
999 bool "tsi148 - Command to access tsi148 device"
1001 This provides various sub-commands to initialise and configure the
1002 Turndra tsi148 device. See the command help for full details.
1005 bool "universe - Command to set up the Turndra Universe controller"
1007 This allows setting up the VMEbus provided by this controller.
1008 See the command help for full details.
1012 select HAVE_BLOCK_DEVICE
1018 select USB_FUNCTION_SDP
1020 Enables the command "sdp" which is used to have U-Boot emulating the
1021 Serial Download Protocol (SDP) via USB.
1025 depends on USB_FUNCTION_ROCKUSB
1027 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1028 read/write info, image to/from devices. This enable rockusb command
1029 support to communication with rockusb device. for more detail about
1030 this command, please read doc/README.rockusb.
1032 config CMD_USB_MASS_STORAGE
1033 bool "UMS usb mass storage"
1034 select USB_FUNCTION_MASS_STORAGE
1036 USB mass storage support
1042 Enable the command "axi" for accessing AXI (Advanced eXtensible
1043 Interface) busses, a on-chip interconnect specification for managing
1044 functional blocks in SoC designs, which is also often used in designs
1045 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1049 menu "Shell scripting commands"
1055 Echo args to console
1061 Return true/false on integer compare.
1067 Run script from memory
1073 Evaluate boolean and math expressions and store the result in an env
1075 Also supports loading the value at a memory location into a variable.
1076 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1083 bool "Network commands"
1093 bootp - boot image via network using BOOTP/TFTP protocol
1097 depends on CMD_BOOTP
1099 Boot image via network using DHCP/TFTP protocol
1101 config BOOTP_BOOTPATH
1102 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1104 depends on CMD_BOOTP
1106 Even though the config is called BOOTP_BOOTPATH, it stores the
1107 path in the variable 'rootpath'.
1110 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1112 depends on CMD_BOOTP
1114 The primary DNS server is stored as 'dnsip'. If two servers are
1115 returned, you must set BOOTP_DNS2 to store that second server IP
1119 bool "Store 'dnsip2' from BOOTP/DHCP server"
1120 depends on BOOTP_DNS
1122 If a DHCP client requests the DNS server IP from a DHCP server,
1123 it is possible that more than one DNS serverip is offered to the
1124 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1125 server IP will be stored in the additional environment
1126 variable "dnsip2". The first DNS serverip is always
1127 stored in the variable "dnsip", when BOOTP_DNS is defined.
1129 config BOOTP_GATEWAY
1130 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1132 depends on CMD_BOOTP
1134 config BOOTP_HOSTNAME
1135 bool "Request & store 'hostname' from BOOTP/DHCP server"
1137 depends on CMD_BOOTP
1139 The name may or may not be qualified with the local domain name.
1141 config BOOTP_PREFER_SERVERIP
1142 bool "serverip variable takes precedent over DHCP server IP."
1143 depends on CMD_BOOTP
1145 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1147 With this option enabled, the 'serverip' variable in the environment
1148 takes precedence over DHCP server IP and will only be set by the DHCP
1149 server if not already set in the environment.
1151 config BOOTP_SUBNETMASK
1152 bool "Request & store 'netmask' from BOOTP/DHCP server"
1154 depends on CMD_BOOTP
1156 config BOOTP_NTPSERVER
1157 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1158 depends on CMD_BOOTP
1161 bool "Send PXE client arch to BOOTP/DHCP server"
1163 depends on CMD_BOOTP && CMD_PXE
1165 Supported for ARM, ARM64, and x86 for now.
1167 config BOOTP_PXE_CLIENTARCH
1169 depends on BOOTP_PXE
1170 default 0x16 if ARM64
1174 config BOOTP_VCI_STRING
1176 depends on CMD_BOOTP
1177 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1178 default "U-Boot.armv8" if ARM64
1179 default "U-Boot.arm" if ARM
1186 tftpboot - boot image via network using TFTP protocol
1190 depends on CMD_TFTPBOOT
1192 TFTP put command, for uploading files to a server
1196 depends on CMD_TFTPBOOT
1198 Act as a TFTP server and boot the first received file
1200 config NET_TFTP_VARS
1201 bool "Control TFTP timeout and count through environment"
1202 depends on CMD_TFTPBOOT
1205 If set, allows controlling the TFTP timeout through the
1206 environment variable tftptimeout, and the TFTP maximum
1207 timeout count through the variable tftptimeoutcountmax.
1208 If unset, timeout and maximum are hard-defined as 1 second
1209 and 10 timouts per TFTP transfer.
1214 Boot image via network using RARP/TFTP protocol
1220 Boot image via network using NFS protocol.
1225 Enable MII utility commands.
1230 Send ICMP ECHO_REQUEST to network host
1235 Perform CDP network configuration
1240 Synchronize RTC via network
1245 Lookup the IP of a hostname
1247 config CMD_LINK_LOCAL
1251 Acquire a network IP address using the link-local protocol
1258 Allow control of L2 Ethernet switch commands. These are supported
1259 by the vsc9953 Ethernet driver at present. Sub-commands allow
1260 operations such as enabling / disabling a port and
1261 viewing/maintaining the filtering database (FDB)
1267 Boot image via network using PXE protocol
1272 Wait for wake-on-lan Magic Packet
1276 menu "Misc commands"
1279 bool "Enable 'bmp' command"
1280 depends on LCD || DM_VIDEO || VIDEO
1282 This provides a way to obtain information about a BMP-format iamge
1283 and to display it. BMP (which presumably stands for BitMaP) is a
1284 file format defined by Microsoft which supports images of various
1285 depths, formats and compression methods. Headers on the file
1286 determine the formats used. This command can be used by first loading
1287 the image into RAM, then using this command to look at it or display
1290 config CMD_BOOTCOUNT
1292 depends on BOOTCOUNT_LIMIT
1294 Enable the bootcount command, which allows interrogation and
1295 reset of the bootcounter.
1298 bool "Enable board-specific commands"
1300 (deprecated: instead, please define a Kconfig option for each command)
1302 Some boards have board-specific commands which are only enabled
1303 during developemnt and need to be turned off for production. This
1304 option provides a way to control this. The commands that are enabled
1305 vary depending on the board.
1307 config CMD_BKOPS_ENABLE
1308 bool "mmc bkops enable"
1312 Enable command for setting manual background operations handshake
1313 on a eMMC device. The feature is optionally available on eMMC devices
1314 conforming to standard >= 4.41.
1316 config CMD_BLOCK_CACHE
1317 bool "blkcache - control and stats for block cache"
1318 depends on BLOCK_CACHE
1319 default y if BLOCK_CACHE
1321 Enable the blkcache command, which can be used to control the
1322 operation of the cache functions.
1323 This is most useful when fine-tuning the operation of the cache
1324 during development, but also allows the cache to be disabled when
1325 it might hurt performance (e.g. when using the ums command).
1328 bool "icache or dcache"
1330 Enable the "icache" and "dcache" commands
1333 bool "Enable the 'display' command, for character displays"
1335 (this needs porting to driver model)
1336 This enables the 'display' command which allows a string to be
1337 displayed on a simple board-specific display. Implement
1338 display_putc() to use it.
1344 Enable the 'led' command which allows for control of LEDs supported
1345 by the board. The LEDs can be listed with 'led list' and controlled
1346 with led on/off/togle/blink. Any LED drivers can be controlled with
1347 this command, e.g. led_gpio.
1353 Enable the 'date' command for getting/setting the time/date in RTC
1359 Run commands and summarize execution time.
1362 bool "gettime - read elapsed time"
1364 Enable the 'gettime' command which reads the elapsed time since
1365 U-Boot started running. This shows the time in seconds and
1366 milliseconds. See also the 'bootstage' command which provides more
1367 flexibility for boot timing.
1369 # TODO: rename to CMD_SLEEP
1374 Delay execution for some time
1377 bool "support for multiprocessor"
1379 This provides an option to brinup
1380 different processors in multiprocessor
1386 Access the system timer.
1392 This provides basic access to the U-Boot's sound support. The main
1393 feature is to play a beep.
1395 sound init - set up sound system
1396 sound play - play a sound
1402 This provides access to the QEMU firmware interface. The main
1403 feature is to allow easy loading of files passed to qemu-system
1404 via -kernel / -initrd
1406 source "cmd/mvebu/Kconfig"
1409 bool "terminal - provides a way to attach a serial terminal"
1411 Provides a 'cu'-like serial terminal command. This can be used to
1412 access other serial ports from the system console. The terminal
1413 is very simple with no special processing of characters. As with
1414 cu, you can press ~. (tilde followed by period) to exit.
1417 bool "uuid, guid - generation of unique IDs"
1420 This enables two commands:
1422 uuid - generate random Universally Unique Identifier
1423 guid - generate Globally Unique Identifier based on random UUID
1425 The two commands are very similar except for the endianness of the
1430 source "cmd/ti/Kconfig"
1432 config CMD_BOOTSTAGE
1433 bool "Enable the 'bootstage' command"
1434 depends on BOOTSTAGE
1436 Add a 'bootstage' command which supports printing a report
1437 and un/stashing of bootstage data.
1439 menu "Power commands"
1441 bool "Enable Driver Model PMIC command"
1444 This is the pmic command, based on a driver model pmic's API.
1445 Command features are unchanged:
1446 - list - list pmic devices
1447 - pmic dev <id> - show or [set] operating pmic device (NEW)
1448 - pmic dump - dump registers
1449 - pmic read address - read byte of register at address
1450 - pmic write address - write byte to register at address
1451 The only one change for this command is 'dev' subcommand.
1453 config CMD_REGULATOR
1454 bool "Enable Driver Model REGULATOR command"
1455 depends on DM_REGULATOR
1457 This command is based on driver model regulator's API.
1458 User interface features:
1459 - list - list regulator devices
1460 - regulator dev <id> - show or [set] operating regulator device
1461 - regulator info - print constraints info
1462 - regulator status - print operating status
1463 - regulator value <val] <-f> - print/[set] voltage value [uV]
1464 - regulator current <val> - print/[set] current value [uA]
1465 - regulator mode <id> - print/[set] operating mode id
1466 - regulator enable - enable the regulator output
1467 - regulator disable - disable the regulator output
1469 The '-f' (force) option can be used for set the value which exceeds
1470 the limits, which are found in device-tree and are kept in regulator's
1471 uclass platdata structure.
1475 menu "Security commands"
1477 bool "Enable the 'aes' command"
1480 This provides a means to encrypt and decrypt data using the AES
1481 (Advanced Encryption Standard). This algorithm uses a symetric key
1482 and is widely used as a streaming cipher. Different key lengths are
1483 supported by the algorithm but this command only supports 128 bits
1487 bool "Enable the 'blob' command"
1489 This is used with the Freescale secure boot mechanism.
1491 Freescale's SEC block has built-in Blob Protocol which provides
1492 a method for protecting user-defined data across system power
1493 cycles. SEC block protects data in a data structure called a Blob,
1494 which provides both confidentiality and integrity protection.
1496 Encapsulating data as a blob
1497 Each time that the Blob Protocol is used to protect data, a
1498 different randomly generated key is used to encrypt the data.
1499 This random key is itself encrypted using a key which is derived
1500 from SoC's non-volatile secret key and a 16 bit Key identifier.
1501 The resulting encrypted key along with encrypted data is called a
1502 blob. The non-volatile secure key is available for use only during
1505 During decapsulation, the reverse process is performed to get back
1509 blob enc - encapsulating data as a cryptgraphic blob
1510 blob dec - decapsulating cryptgraphic blob to get the data
1514 blob enc src dst len km
1516 Encapsulate and create blob of data $len bytes long
1517 at address $src and store the result at address $dst.
1518 $km is the 16 byte key modifier is also required for
1519 generation/use as key for cryptographic operation. Key
1520 modifier should be 16 byte long.
1522 blob dec src dst len km
1524 Decapsulate the blob of data at address $src and
1525 store result of $len byte at addr $dst.
1526 $km is the 16 byte key modifier is also required for
1527 generation/use as key for cryptographic operation. Key
1528 modifier should be 16 byte long.
1531 bool "Support 'hash' command"
1534 This provides a way to hash data in memory using various supported
1535 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1536 saved to memory or to an environment variable. It is also possible
1537 to verify a hash against data in memory.
1540 bool "Support the 'hvc' command"
1541 depends on ARM_SMCCC
1543 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1544 development and testing.
1547 bool "Support the 'smc' command"
1548 depends on ARM_SMCCC
1550 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1551 development and testing.
1557 Add -v option to verify data against a hash.
1567 bool "Enable the 'tpm' command"
1568 depends on TPM_V1 || TPM_V2
1569 select CMD_TPM_V1 if TPM_V1
1570 select CMD_TPM_V2 if TPM_V2
1572 This provides a means to talk to a TPM from the command line. A wide
1573 range of commands if provided - see 'tpm help' for details. The
1574 command requires a suitable TPM on your board and the correct driver
1580 bool "Enable the 'tpm test' command"
1583 This provides a a series of tests to confirm that the TPMv1.x is
1584 working correctly. The tests cover initialisation, non-volatile RAM,
1585 extend, global lock and checking that timing is within expectations.
1586 The tests pass correctly on Infineon TPMs but may need to be adjusted
1593 menu "Firmware commands"
1595 bool "Enable crosec command"
1599 Enable command-line access to the Chrome OS EC (Embedded
1600 Controller). This provides the 'crosec' command which has
1601 a number of sub-commands for performing EC tasks such as
1602 updating its flash, accessing a small saved context area
1603 and talking to the I2C bus behind the EC (if there is one).
1606 menu "Filesystem commands"
1608 bool "Enable the 'btrsubvol' command"
1611 This enables the 'btrsubvol' command to list subvolumes
1612 of a BTRFS filesystem. There are no special commands for
1613 listing BTRFS directories or loading BTRFS files - this
1614 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1615 when BTRFS is enabled (see FS_BTRFS).
1618 bool "Enable the 'cbfs' command"
1621 Define this to enable support for reading from a Coreboot
1622 filesystem. This is a ROM-based filesystem used for accessing files
1623 on systems that use coreboot as the first boot-loader and then load
1624 U-Boot to actually boot the Operating System. Available commands are
1625 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1628 bool "Enable the 'cramfs' command"
1629 depends on FS_CRAMFS
1631 This provides commands for dealing with CRAMFS (Compressed ROM
1632 filesystem). CRAMFS is useful when space is tight since files are
1633 compressed. Two commands are provided:
1635 cramfsls - lists files in a cramfs image
1636 cramfsload - loads a file from a cramfs image
1639 bool "ext2 command support"
1642 Enables EXT2 FS command
1645 bool "ext4 command support"
1648 Enables EXT4 FS command
1650 config CMD_EXT4_WRITE
1652 bool "ext4 write command support"
1655 Enables EXT4 FS write command
1658 bool "FAT command support"
1661 Support for the FAT fs
1663 config CMD_FS_GENERIC
1664 bool "filesystem commands"
1666 Enables filesystem commands (e.g. load, ls) that work for multiple
1670 bool "fsuuid command"
1672 Enables fsuuid command for filesystem UUID.
1675 bool "jffs2 command"
1678 Enables commands to support the JFFS2 (Journalling Flash File System
1679 version 2) filesystem. This enables fsload, ls and fsinfo which
1680 provide the ability to load files, list directories and obtain
1681 filesystem information.
1684 bool "MTD partition support"
1685 select MTD_DEVICE if (CMD_NAND || NAND)
1687 MTD partition support
1689 config MTDIDS_DEFAULT
1690 string "Default MTD IDs"
1691 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1693 Defines a default MTD IDs list for use with MTD partitions in the
1694 Linux MTD command line partitions format.
1696 config MTDPARTS_DEFAULT
1697 string "Default MTD partition scheme"
1698 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1700 Defines a default MTD partitioning scheme in the Linux MTD command
1701 line partitions format
1703 config CMD_MTDPARTS_SPREAD
1704 bool "Padd partition size to take account of bad blocks"
1705 depends on CMD_MTDPARTS
1707 This enables the 'spread' sub-command of the mtdparts command.
1708 This command will modify the existing mtdparts variable by increasing
1709 the size of the partitions such that 1) each partition's net size is
1710 at least as large as the size specified in the mtdparts variable and
1711 2) each partition starts on a good block.
1714 bool "reiser - Access to reiserfs filesystems"
1716 This provides two commands which operate on a resierfs filesystem,
1717 commonly used some years ago:
1719 reiserls - list files
1720 reiserload - load a file
1723 bool "yaffs2 - Access of YAFFS2 filesystem"
1727 This provides commands for accessing a YAFFS2 filesystem. Yet
1728 Another Flash Filesystem 2 is a filesystem designed specifically
1729 for NAND flash. It incorporates bad-block management and ensures
1730 that device writes are sequential regardless of filesystem
1734 bool "zfs - Access of ZFS filesystem"
1736 This provides commands to accessing a ZFS filesystem, commonly used
1737 on Solaris systems. Two sub-commands are provided:
1739 zfsls - list files in a directory
1740 zfsload - load a file
1742 See doc/README.zfs for more details.
1746 menu "Debug commands"
1751 The bedbug (emBEDded deBUGger) command provides debugging features
1752 for some PowerPC processors. For details please see the
1753 docuemntation in doc/README.beddbug
1756 bool "diag - Board diagnostics"
1758 This command provides access to board diagnostic tests. These are
1759 called Power-on Self Tests (POST). The command allows listing of
1760 available tests and running either all the tests, or specific tests
1764 bool "irq - Show information about interrupts"
1765 depends on !ARM && !MIPS && !SH
1767 This enables two commands:
1769 interrupts - enable or disable interrupts
1770 irqinfo - print device-specific interrupt information
1773 bool "kgdb - Allow debugging of U-Boot with gdb"
1775 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1776 over a serial link for debugging purposes. This allows
1777 single-stepping, inspecting variables, etc. This is supported only
1778 on PowerPC at present.
1781 bool "log - Generation, control and access to logging"
1784 This provides access to logging features. It allows the output of
1785 log data to be controlled to a limited extent (setting up the default
1786 maximum log level for emitting of records). It also provides access
1787 to a command used for testing the log system.
1790 bool "trace - Support tracing of function calls and timing"
1792 Enables a command to control using of function tracing within
1793 U-Boot. This allows recording of call traces including timing
1794 information. The command can write data to memory for exporting
1795 for analsys (e.g. using bootchart). See doc/README.trace for full
1799 bool "avb - Android Verified Boot 2.0 operations"
1800 depends on AVB_VERIFY
1803 Enables a "avb" command to perform verification of partitions using
1804 Android Verified Boot 2.0 functionality. It includes such subcommands:
1805 avb init - initialize avb2 subsystem
1806 avb read_rb - read rollback index
1807 avb write_rb - write rollback index
1808 avb is_unlocked - check device lock state
1809 avb get_uuid - read and print uuid of a partition
1810 avb read_part - read data from partition
1811 avb read_part_hex - read data from partition and output to stdout
1812 avb write_part - write data to partition
1813 avb verify - run full verification chain
1817 tristate "Enable UBI - Unsorted block images commands"
1818 default y if NAND_SUNXI
1823 UBI is a software layer above MTD layer which admits use of LVM-like
1824 logical volumes on top of MTD devices, hides some complexities of
1825 flash chips like wear and bad blocks and provides some other useful
1826 capabilities. Please, consult the MTD web site for more details
1827 (www.linux-mtd.infradead.org). Activate this option if you want
1828 to use U-Boot UBI commands.
1831 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1833 default y if CMD_UBI
1837 UBIFS is a file system for flash devices which works on top of UBI.
projects / oweals / u-boot.git / blob