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
701 bool "fpgad - dump FPGA registers"
703 (legacy, needs conversion to driver model)
704 Provides a way to dump FPGA registers by calling the board-specific
705 fpga_get_reg() function. This functions similarly to the 'md'
709 bool "fuse - support for the fuse subssystem"
711 (deprecated - needs conversion to driver model)
712 This allows reading, sensing, programming or overriding fuses
713 which control the behaviour of the device. The command uses the
722 bool "GPT (GUID Partition Table) command"
723 select PARTITION_UUIDS
725 select HAVE_BLOCK_DEVICE
728 Enable the 'gpt' command to ready and write GPT style partition
732 bool "GPT Random UUID generation"
735 Enable the generation of partitions with random UUIDs if none
738 config CMD_GPT_RENAME
739 bool "GPT partition renaming commands"
742 Enables the 'gpt' command to interchange names on two GPT
743 partitions via the 'gpt swap' command or to rename single
744 partitions via the 'rename' command.
747 bool "ide - Support for IDE drivers"
750 Provides an 'ide' command which allows accessing the IDE drive,
751 reseting the IDE interface, printing the partition table and
752 geting device info. It also enables the 'diskboot' command which
753 permits booting from an IDE drive.
756 bool "io - Support for performing I/O accesses"
758 Provides an 'iod' command to display I/O space and an 'iow' command
759 to write values to the I/O space. This can be useful for manually
760 checking the state of devices during boot when debugging device
764 bool "iotrace - Support for tracing I/O activity"
766 Provides an 'iotrace' command which supports recording I/O reads and
767 writes in a trace buffer in memory . It also maintains a checksum
768 of the trace records (even if space is exhausted) so that the
769 sequence of I/O accesses can be verified.
771 When debugging drivers it is useful to see what I/O accesses were
772 done and in what order.
774 Even if the individual accesses are of little interest it can be
775 useful to verify that the access pattern is consistent each time
776 an operation is performed. In this case a checksum can be used to
777 characterise the operation of a driver. The checksum can be compared
778 across different runs of the operation to verify that the driver is
781 In particular, when performing major refactoring of the driver, where
782 the access pattern should not change, the checksum provides assurance
783 that the refactoring work has not broken the driver.
785 This works by sneaking into the io.h heder for an architecture and
786 redirecting I/O accesses through iotrace's tracing mechanism.
788 For now no commands are provided to examine the trace buffer. The
789 format is fairly simple, so 'md' is a reasonable substitute.
791 Note: The checksum feature is only useful for I/O regions where the
792 contents do not change outside of software control. Where this is not
793 suitable you can fall back to manually comparing the addresses. It
794 might be useful to enhance tracing to only checksum the accesses and
795 not the data read/written.
806 Load a binary file over serial line.
812 Load an S-Record file over serial line
817 MMC memory mapped support.
820 bool "Enable support for RPMB in the mmc command"
823 Enable the commands for reading, writing and programming the
824 key for the Replay Protection Memory Block partition in eMMC.
828 default y if NAND_SUNXI
833 config CMD_NAND_TRIMFFS
834 bool "nand write.trimffs"
835 default y if ARCH_SUNXI
837 Allows one to skip empty pages when flashing something on a NAND.
839 config CMD_NAND_LOCK_UNLOCK
840 bool "nand lock/unlock"
842 NAND locking support.
844 config CMD_NAND_TORTURE
847 NAND torture support.
856 NVM Express device support
859 bool "mmc_spi - Set up MMC SPI device"
861 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
862 Peripheral Interface) device. The device provides a means of
863 accessing an MMC device via SPI using a single data line, limited
864 to 20MHz. It is useful since it reduces the amount of protocol code
868 bool "onenand - access to onenand device"
870 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
871 various useful features. This command allows reading, writing,
872 and erasing blocks. It allso provides a way to show and change
873 bad blocks, and test the device.
877 select PARTITION_UUIDS
878 select HAVE_BLOCK_DEVICE
880 Read and display information about the partition table on
884 bool "pci - Access PCI devices"
886 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
887 used on some devices to allow the CPU to communicate with its
888 peripherals. Sub-commands allow bus enumeration, displaying and
889 changing configuration space and a few other features.
892 bool "pinit - Set up PCMCIA device"
894 Provides a means to initialise a PCMCIA (Personal Computer Memory
895 Card International Association) device. This is an old standard from
896 about 1990. These devices are typically removable memory or network
897 cards using a standard 68-pin connector.
900 bool "read - Read binary data from a partition"
902 Provides low-level access to the data in a partition.
904 config CMD_REMOTEPROC
906 depends on REMOTEPROC
908 Support for Remote Processor control
911 bool "sata - Access SATA subsystem"
914 SATA (Serial Advanced Technology Attachment) is a serial bus
915 standard for connecting to hard drives and other storage devices.
916 This command provides information about attached devices and allows
917 reading, writing and other operations.
919 SATA replaces PATA (originally just ATA), which stands for Parallel AT
920 Attachment, where AT refers to an IBM AT (Advanced Technology)
921 computer released in 1984.
924 bool "saves - Save a file over serial in S-Record format"
926 Provides a way to save a binary file using the Motorola S-Record
927 format over the serial line.
930 bool "scsi - Access to SCSI devices"
933 This provides a 'scsi' command which provides access to SCSI (Small
934 Computer System Interface) devices. The command provides a way to
935 scan the bus, reset the bus, read and write data and get information
939 bool "sdram - Print SDRAM configuration information"
941 Provides information about attached SDRAM. This assumed that the
942 SDRAM has an EEPROM with information that can be read using the
943 I2C bus. This is only available on some boards.
951 bool "sf test - Allow testing of SPI flash"
953 Provides a way to test that SPI flash is working correctly. The
954 test is destructive, in that an area of SPI flash must be provided
955 for the test to use. Performance information is also provided,
956 measuring the performance of reading, writing and erasing in
957 Mbps (Million Bits Per Second). This value should approximately
958 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
959 everything is working properly.
967 bool "tsi148 - Command to access tsi148 device"
969 This provides various sub-commands to initialise and configure the
970 Turndra tsi148 device. See the command help for full details.
973 bool "universe - Command to set up the Turndra Universe controller"
975 This allows setting up the VMEbus provided by this controller.
976 See the command help for full details.
980 select HAVE_BLOCK_DEVICE
986 select USB_FUNCTION_SDP
988 Enables the command "sdp" which is used to have U-Boot emulating the
989 Serial Download Protocol (SDP) via USB.
992 depends on USB_FUNCTION_ROCKUSB
994 Rockusb protocol is widely used by Rockchip SoC based devices. It can
995 read/write info, image to/from devices. This enable rockusb command
996 support to communication with rockusb device. for more detail about
997 this command, please read doc/README.rockusb.
999 config CMD_USB_MASS_STORAGE
1000 bool "UMS usb mass storage"
1001 select USB_FUNCTION_MASS_STORAGE
1003 USB mass storage support
1008 menu "Shell scripting commands"
1014 Echo args to console
1020 Return true/false on integer compare.
1026 Run script from memory
1032 Evaluate boolean and math expressions and store the result in an env
1034 Also supports loading the value at a memory location into a variable.
1035 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1042 bool "Network commands"
1051 bootp - boot image via network using BOOTP/TFTP protocol
1055 depends on CMD_BOOTP
1057 Boot image via network using DHCP/TFTP protocol
1059 config BOOTP_BOOTPATH
1060 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1062 depends on CMD_BOOTP
1064 Even though the config is called BOOTP_BOOTPATH, it stores the
1065 path in the variable 'rootpath'.
1068 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1070 depends on CMD_BOOTP
1072 The primary DNS server is stored as 'dnsip'. If two servers are
1073 returned, you must set BOOTP_DNS2 to store that second server IP
1077 bool "Store 'dnsip2' from BOOTP/DHCP server"
1078 depends on BOOTP_DNS
1080 If a DHCP client requests the DNS server IP from a DHCP server,
1081 it is possible that more than one DNS serverip is offered to the
1082 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1083 server IP will be stored in the additional environment
1084 variable "dnsip2". The first DNS serverip is always
1085 stored in the variable "dnsip", when BOOTP_DNS is defined.
1087 config BOOTP_GATEWAY
1088 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1090 depends on CMD_BOOTP
1092 config BOOTP_HOSTNAME
1093 bool "Request & store 'hostname' from BOOTP/DHCP server"
1095 depends on CMD_BOOTP
1097 The name may or may not be qualified with the local domain name.
1099 config BOOTP_SUBNETMASK
1100 bool "Request & store 'netmask' from BOOTP/DHCP server"
1102 depends on CMD_BOOTP
1104 config BOOTP_NTPSERVER
1105 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1106 depends on CMD_BOOTP
1109 bool "Send PXE client arch to BOOTP/DHCP server"
1111 depends on CMD_BOOTP && CMD_PXE
1113 Supported for ARM, ARM64, and x86 for now.
1115 config BOOTP_PXE_CLIENTARCH
1117 depends on BOOTP_PXE
1118 default 0x16 if ARM64
1122 config BOOTP_VCI_STRING
1124 depends on CMD_BOOTP
1125 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1126 default "U-Boot.armv8" if ARM64
1127 default "U-Boot.arm" if ARM
1134 tftpboot - boot image via network using TFTP protocol
1138 depends on CMD_TFTPBOOT
1140 TFTP put command, for uploading files to a server
1144 depends on CMD_TFTPBOOT
1146 Act as a TFTP server and boot the first received file
1148 config NET_TFTP_VARS
1149 bool "Control TFTP timeout and count through environment"
1150 depends on CMD_TFTPBOOT
1153 If set, allows controlling the TFTP timeout through the
1154 environment variable tftptimeout, and the TFTP maximum
1155 timeout count through the variable tftptimeoutcountmax.
1156 If unset, timeout and maximum are hard-defined as 1 second
1157 and 10 timouts per TFTP transfer.
1162 Boot image via network using RARP/TFTP protocol
1168 Boot image via network using NFS protocol.
1173 Enable MII utility commands.
1178 Send ICMP ECHO_REQUEST to network host
1183 Perform CDP network configuration
1188 Synchronize RTC via network
1193 Lookup the IP of a hostname
1195 config CMD_LINK_LOCAL
1198 Acquire a network IP address using the link-local protocol
1205 Allow control of L2 Ethernet switch commands. These are supported
1206 by the vsc9953 Ethernet driver at present. Sub-commands allow
1207 operations such as enabling / disabling a port and
1208 viewing/maintaining the filtering database (FDB)
1214 Boot image via network using PXE protocol
1218 menu "Misc commands"
1221 bool "Enable 'bmp' command"
1222 depends on LCD || DM_VIDEO || VIDEO
1224 This provides a way to obtain information about a BMP-format iamge
1225 and to display it. BMP (which presumably stands for BitMaP) is a
1226 file format defined by Microsoft which supports images of various
1227 depths, formats and compression methods. Headers on the file
1228 determine the formats used. This command can be used by first loading
1229 the image into RAM, then using this command to look at it or display
1232 config CMD_BOOTCOUNT
1234 depends on BOOTCOUNT_LIMIT
1236 Enable the bootcount command, which allows interrogation and
1237 reset of the bootcounter.
1240 bool "Enable board-specific commands"
1242 (deprecated: instead, please define a Kconfig option for each command)
1244 Some boards have board-specific commands which are only enabled
1245 during developemnt and need to be turned off for production. This
1246 option provides a way to control this. The commands that are enabled
1247 vary depending on the board.
1249 config CMD_BKOPS_ENABLE
1250 bool "mmc bkops enable"
1254 Enable command for setting manual background operations handshake
1255 on a eMMC device. The feature is optionally available on eMMC devices
1256 conforming to standard >= 4.41.
1258 config CMD_BLOCK_CACHE
1259 bool "blkcache - control and stats for block cache"
1260 depends on BLOCK_CACHE
1261 default y if BLOCK_CACHE
1263 Enable the blkcache command, which can be used to control the
1264 operation of the cache functions.
1265 This is most useful when fine-tuning the operation of the cache
1266 during development, but also allows the cache to be disabled when
1267 it might hurt performance (e.g. when using the ums command).
1270 bool "icache or dcache"
1272 Enable the "icache" and "dcache" commands
1275 bool "Enable the 'display' command, for character displays"
1277 (this needs porting to driver model)
1278 This enables the 'display' command which allows a string to be
1279 displayed on a simple board-specific display. Implement
1280 display_putc() to use it.
1286 Enable the 'led' command which allows for control of LEDs supported
1287 by the board. The LEDs can be listed with 'led list' and controlled
1288 with led on/off/togle/blink. Any LED drivers can be controlled with
1289 this command, e.g. led_gpio.
1295 Enable the 'date' command for getting/setting the time/date in RTC
1301 Run commands and summarize execution time.
1304 bool "gettime - read elapsed time"
1306 Enable the 'gettime' command which reads the elapsed time since
1307 U-Boot started running. This shows the time in seconds and
1308 milliseconds. See also the 'bootstage' command which provides more
1309 flexibility for boot timing.
1311 # TODO: rename to CMD_SLEEP
1316 Delay execution for some time
1321 Access the system timer.
1327 This provides basic access to the U-Boot's sound support. The main
1328 feature is to play a beep.
1330 sound init - set up sound system
1331 sound play - play a sound
1337 This provides access to the QEMU firmware interface. The main
1338 feature is to allow easy loading of files passed to qemu-system
1339 via -kernel / -initrd
1341 source "cmd/mvebu/Kconfig"
1344 bool "terminal - provides a way to attach a serial terminal"
1346 Provides a 'cu'-like serial terminal command. This can be used to
1347 access other serial ports from the system console. The terminal
1348 is very simple with no special processing of characters. As with
1349 cu, you can press ~. (tilde followed by period) to exit.
1352 bool "uuid, guid - generation of unique IDs"
1355 This enables two commands:
1357 uuid - generate random Universally Unique Identifier
1358 guid - generate Globally Unique Identifier based on random UUID
1360 The two commands are very similar except for the endianness of the
1365 source "cmd/ti/Kconfig"
1367 config CMD_BOOTSTAGE
1368 bool "Enable the 'bootstage' command"
1369 depends on BOOTSTAGE
1371 Add a 'bootstage' command which supports printing a report
1372 and un/stashing of bootstage data.
1374 menu "Power commands"
1376 bool "Enable Driver Model PMIC command"
1379 This is the pmic command, based on a driver model pmic's API.
1380 Command features are unchanged:
1381 - list - list pmic devices
1382 - pmic dev <id> - show or [set] operating pmic device (NEW)
1383 - pmic dump - dump registers
1384 - pmic read address - read byte of register at address
1385 - pmic write address - write byte to register at address
1386 The only one change for this command is 'dev' subcommand.
1388 config CMD_REGULATOR
1389 bool "Enable Driver Model REGULATOR command"
1390 depends on DM_REGULATOR
1392 This command is based on driver model regulator's API.
1393 User interface features:
1394 - list - list regulator devices
1395 - regulator dev <id> - show or [set] operating regulator device
1396 - regulator info - print constraints info
1397 - regulator status - print operating status
1398 - regulator value <val] <-f> - print/[set] voltage value [uV]
1399 - regulator current <val> - print/[set] current value [uA]
1400 - regulator mode <id> - print/[set] operating mode id
1401 - regulator enable - enable the regulator output
1402 - regulator disable - disable the regulator output
1404 The '-f' (force) option can be used for set the value which exceeds
1405 the limits, which are found in device-tree and are kept in regulator's
1406 uclass platdata structure.
1410 menu "Security commands"
1412 bool "Enable the 'aes' command"
1415 This provides a means to encrypt and decrypt data using the AES
1416 (Advanced Encryption Standard). This algorithm uses a symetric key
1417 and is widely used as a streaming cipher. Different key lengths are
1418 supported by the algorithm but this command only supports 128 bits
1422 bool "Enable the 'blob' command"
1424 This is used with the Freescale secure boot mechanism.
1426 Freescale's SEC block has built-in Blob Protocol which provides
1427 a method for protecting user-defined data across system power
1428 cycles. SEC block protects data in a data structure called a Blob,
1429 which provides both confidentiality and integrity protection.
1431 Encapsulating data as a blob
1432 Each time that the Blob Protocol is used to protect data, a
1433 different randomly generated key is used to encrypt the data.
1434 This random key is itself encrypted using a key which is derived
1435 from SoC's non-volatile secret key and a 16 bit Key identifier.
1436 The resulting encrypted key along with encrypted data is called a
1437 blob. The non-volatile secure key is available for use only during
1440 During decapsulation, the reverse process is performed to get back
1444 blob enc - encapsulating data as a cryptgraphic blob
1445 blob dec - decapsulating cryptgraphic blob to get the data
1449 blob enc src dst len km
1451 Encapsulate and create blob of data $len bytes long
1452 at address $src and store the result at address $dst.
1453 $km is the 16 byte key modifier is also required for
1454 generation/use as key for cryptographic operation. Key
1455 modifier should be 16 byte long.
1457 blob dec src dst len km
1459 Decapsulate the blob of data at address $src and
1460 store result of $len byte at addr $dst.
1461 $km is the 16 byte key modifier is also required for
1462 generation/use as key for cryptographic operation. Key
1463 modifier should be 16 byte long.
1466 bool "Support 'hash' command"
1469 This provides a way to hash data in memory using various supported
1470 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1471 saved to memory or to an environment variable. It is also possible
1472 to verify a hash against data in memory.
1475 bool "Support the 'hvc' command"
1476 depends on ARM_SMCCC
1478 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1479 development and testing.
1482 bool "Support the 'smc' command"
1483 depends on ARM_SMCCC
1485 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1486 development and testing.
1492 Add -v option to verify data against a hash.
1501 bool "Enable the 'tpm' command"
1502 depends on TPM_V1 || TPM_V2
1503 select CMD_TPM_V1 if TPM_V1
1504 select CMD_TPM_V2 if TPM_V2
1506 This provides a means to talk to a TPM from the command line. A wide
1507 range of commands if provided - see 'tpm help' for details. The
1508 command requires a suitable TPM on your board and the correct driver
1514 bool "Enable the 'tpm test' command"
1517 This provides a a series of tests to confirm that the TPMv1.x is
1518 working correctly. The tests cover initialisation, non-volatile RAM,
1519 extend, global lock and checking that timing is within expectations.
1520 The tests pass correctly on Infineon TPMs but may need to be adjusted
1527 menu "Firmware commands"
1529 bool "Enable crosec command"
1533 Enable command-line access to the Chrome OS EC (Embedded
1534 Controller). This provides the 'crosec' command which has
1535 a number of sub-commands for performing EC tasks such as
1536 updating its flash, accessing a small saved context area
1537 and talking to the I2C bus behind the EC (if there is one).
1540 menu "Filesystem commands"
1542 bool "Enable the 'btrsubvol' command"
1545 This enables the 'btrsubvol' command to list subvolumes
1546 of a BTRFS filesystem. There are no special commands for
1547 listing BTRFS directories or loading BTRFS files - this
1548 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1549 when BTRFS is enabled (see FS_BTRFS).
1552 bool "Enable the 'cbfs' command"
1555 Define this to enable support for reading from a Coreboot
1556 filesystem. This is a ROM-based filesystem used for accessing files
1557 on systems that use coreboot as the first boot-loader and then load
1558 U-Boot to actually boot the Operating System. Available commands are
1559 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1562 bool "Enable the 'cramfs' command"
1563 depends on FS_CRAMFS
1565 This provides commands for dealing with CRAMFS (Compressed ROM
1566 filesystem). CRAMFS is useful when space is tight since files are
1567 compressed. Two commands are provided:
1569 cramfsls - lists files in a cramfs image
1570 cramfsload - loads a file from a cramfs image
1573 bool "ext2 command support"
1576 Enables EXT2 FS command
1579 bool "ext4 command support"
1582 Enables EXT4 FS command
1584 config CMD_EXT4_WRITE
1586 bool "ext4 write command support"
1589 Enables EXT4 FS write command
1592 bool "FAT command support"
1595 Support for the FAT fs
1597 config CMD_FS_GENERIC
1598 bool "filesystem commands"
1600 Enables filesystem commands (e.g. load, ls) that work for multiple
1604 bool "fsuuid command"
1606 Enables fsuuid command for filesystem UUID.
1609 bool "jffs2 command"
1612 Enables commands to support the JFFS2 (Journalling Flash File System
1613 version 2) filesystem. This enables fsload, ls and fsinfo which
1614 provide the ability to load files, list directories and obtain
1615 filesystem information.
1618 bool "MTD partition support"
1620 MTD partition support
1622 config MTDIDS_DEFAULT
1623 string "Default MTD IDs"
1624 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1626 Defines a default MTD IDs list for use with MTD partitions in the
1627 Linux MTD command line partitions format.
1629 config MTDPARTS_DEFAULT
1630 string "Default MTD partition scheme"
1631 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1633 Defines a default MTD partitioning scheme in the Linux MTD command
1634 line partitions format
1636 config CMD_MTDPARTS_SPREAD
1637 bool "Padd partition size to take account of bad blocks"
1638 depends on CMD_MTDPARTS
1640 This enables the 'spread' sub-command of the mtdparts command.
1641 This command will modify the existing mtdparts variable by increasing
1642 the size of the partitions such that 1) each partition's net size is
1643 at least as large as the size specified in the mtdparts variable and
1644 2) each partition starts on a good block.
1647 bool "reiser - Access to reiserfs filesystems"
1649 This provides two commands which operate on a resierfs filesystem,
1650 commonly used some years ago:
1652 reiserls - list files
1653 reiserload - load a file
1656 bool "yaffs2 - Access of YAFFS2 filesystem"
1660 This provides commands for accessing a YAFFS2 filesystem. Yet
1661 Another Flash Filesystem 2 is a filesystem designed specifically
1662 for NAND flash. It incorporates bad-block management and ensures
1663 that device writes are sequential regardless of filesystem
1667 bool "zfs - Access of ZFS filesystem"
1669 This provides commands to accessing a ZFS filesystem, commonly used
1670 on Solaris systems. Two sub-commands are provided:
1672 zfsls - list files in a directory
1673 zfsload - load a file
1675 See doc/README.zfs for more details.
1679 menu "Debug commands"
1684 The bedbug (emBEDded deBUGger) command provides debugging features
1685 for some PowerPC processors. For details please see the
1686 docuemntation in doc/README.beddbug
1689 bool "diag - Board diagnostics"
1691 This command provides access to board diagnostic tests. These are
1692 called Power-on Self Tests (POST). The command allows listing of
1693 available tests and running either all the tests, or specific tests
1697 bool "irq - Show information about interrupts"
1698 depends on !ARM && !MIPS && !SH
1700 This enables two commands:
1702 interrupts - enable or disable interrupts
1703 irqinfo - print device-specific interrupt information
1706 bool "kgdb - Allow debugging of U-Boot with gdb"
1708 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1709 over a serial link for debugging purposes. This allows
1710 single-stepping, inspecting variables, etc. This is supported only
1711 on PowerPC at present.
1714 bool "log - Generation, control and access to logging"
1717 This provides access to logging features. It allows the output of
1718 log data to be controlled to a limited extent (setting up the default
1719 maximum log level for emitting of records). It also provides access
1720 to a command used for testing the log system.
1723 bool "trace - Support tracing of function calls and timing"
1725 Enables a command to control using of function tracing within
1726 U-Boot. This allows recording of call traces including timing
1727 information. The command can write data to memory for exporting
1728 for analsys (e.g. using bootchart). See doc/README.trace for full
1734 tristate "Enable UBI - Unsorted block images commands"
1738 default y if NAND_SUNXI
1740 UBI is a software layer above MTD layer which admits use of LVM-like
1741 logical volumes on top of MTD devices, hides some complexities of
1742 flash chips like wear and bad blocks and provides some other useful
1743 capabilities. Please, consult the MTD web site for more details
1744 (www.linux-mtd.infradead.org). Activate this option if you want
1745 to use U-Boot UBI commands.
1748 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1752 default y if CMD_UBI
1754 UBIFS is a file system for flash devices which works on top of UBI.
projects / u-boot / blob