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.
821 default y if NAND_SUNXI
826 config CMD_NAND_TRIMFFS
827 bool "nand write.trimffs"
828 default y if ARCH_SUNXI
830 Allows one to skip empty pages when flashing something on a NAND.
832 config CMD_NAND_LOCK_UNLOCK
833 bool "nand lock/unlock"
835 NAND locking support.
837 config CMD_NAND_TORTURE
840 NAND torture support.
849 NVM Express device support
852 bool "mmc_spi - Set up MMC SPI device"
854 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
855 Peripheral Interface) device. The device provides a means of
856 accessing an MMC device via SPI using a single data line, limited
857 to 20MHz. It is useful since it reduces the amount of protocol code
861 bool "onenand - access to onenand device"
863 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
864 various useful features. This command allows reading, writing,
865 and erasing blocks. It allso provides a way to show and change
866 bad blocks, and test the device.
870 select PARTITION_UUIDS
871 select HAVE_BLOCK_DEVICE
873 Read and display information about the partition table on
877 bool "pci - Access PCI devices"
879 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
880 used on some devices to allow the CPU to communicate with its
881 peripherals. Sub-commands allow bus enumeration, displaying and
882 changing configuration space and a few other features.
885 bool "pinit - Set up PCMCIA device"
887 Provides a means to initialise a PCMCIA (Personal Computer Memory
888 Card International Association) device. This is an old standard from
889 about 1990. These devices are typically removable memory or network
890 cards using a standard 68-pin connector.
893 bool "read - Read binary data from a partition"
895 Provides low-level access to the data in a partition.
897 config CMD_REMOTEPROC
899 depends on REMOTEPROC
901 Support for Remote Processor control
904 bool "sata - Access SATA subsystem"
907 SATA (Serial Advanced Technology Attachment) is a serial bus
908 standard for connecting to hard drives and other storage devices.
909 This command provides information about attached devices and allows
910 reading, writing and other operations.
912 SATA replaces PATA (originally just ATA), which stands for Parallel AT
913 Attachment, where AT refers to an IBM AT (Advanced Technology)
914 computer released in 1984.
917 bool "saves - Save a file over serial in S-Record format"
919 Provides a way to save a binary file using the Motorola S-Record
920 format over the serial line.
923 bool "scsi - Access to SCSI devices"
926 This provides a 'scsi' command which provides access to SCSI (Small
927 Computer System Interface) devices. The command provides a way to
928 scan the bus, reset the bus, read and write data and get information
932 bool "sdram - Print SDRAM configuration information"
934 Provides information about attached SDRAM. This assumed that the
935 SDRAM has an EEPROM with information that can be read using the
936 I2C bus. This is only available on some boards.
944 bool "sf test - Allow testing of SPI flash"
946 Provides a way to test that SPI flash is working correctly. The
947 test is destructive, in that an area of SPI flash must be provided
948 for the test to use. Performance information is also provided,
949 measuring the performance of reading, writing and erasing in
950 Mbps (Million Bits Per Second). This value should approximately
951 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
952 everything is working properly.
960 bool "tsi148 - Command to access tsi148 device"
962 This provides various sub-commands to initialise and configure the
963 Turndra tsi148 device. See the command help for full details.
966 bool "universe - Command to set up the Turndra Universe controller"
968 This allows setting up the VMEbus provided by this controller.
969 See the command help for full details.
973 select HAVE_BLOCK_DEVICE
979 select USB_FUNCTION_SDP
981 Enables the command "sdp" which is used to have U-Boot emulating the
982 Serial Download Protocol (SDP) via USB.
985 depends on USB_FUNCTION_ROCKUSB
987 Rockusb protocol is widely used by Rockchip SoC based devices. It can
988 read/write info, image to/from devices. This enable rockusb command
989 support to communication with rockusb device. for more detail about
990 this command, please read doc/README.rockusb.
992 config CMD_USB_MASS_STORAGE
993 bool "UMS usb mass storage"
994 select USB_FUNCTION_MASS_STORAGE
996 USB mass storage support
1001 menu "Shell scripting commands"
1007 Echo args to console
1013 Return true/false on integer compare.
1019 Run script from memory
1025 Evaluate boolean and math expressions and store the result in an env
1027 Also supports loading the value at a memory location into a variable.
1028 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1035 bool "Network commands"
1044 bootp - boot image via network using BOOTP/TFTP protocol
1048 depends on CMD_BOOTP
1050 Boot image via network using DHCP/TFTP protocol
1052 config BOOTP_BOOTPATH
1053 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1055 depends on CMD_BOOTP
1057 Even though the config is called BOOTP_BOOTPATH, it stores the
1058 path in the variable 'rootpath'.
1061 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1063 depends on CMD_BOOTP
1065 The primary DNS server is stored as 'dnsip'. If two servers are
1066 returned, you must set BOOTP_DNS2 to store that second server IP
1070 bool "Store 'dnsip2' from BOOTP/DHCP server"
1071 depends on BOOTP_DNS
1073 If a DHCP client requests the DNS server IP from a DHCP server,
1074 it is possible that more than one DNS serverip is offered to the
1075 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1076 server IP will be stored in the additional environment
1077 variable "dnsip2". The first DNS serverip is always
1078 stored in the variable "dnsip", when BOOTP_DNS is defined.
1080 config BOOTP_GATEWAY
1081 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1083 depends on CMD_BOOTP
1085 config BOOTP_HOSTNAME
1086 bool "Request & store 'hostname' from BOOTP/DHCP server"
1088 depends on CMD_BOOTP
1090 The name may or may not be qualified with the local domain name.
1092 config BOOTP_SUBNETMASK
1093 bool "Request & store 'netmask' from BOOTP/DHCP server"
1095 depends on CMD_BOOTP
1098 bool "Send PXE client arch to BOOTP/DHCP server"
1100 depends on CMD_BOOTP && CMD_PXE
1102 Supported for ARM, ARM64, and x86 for now.
1104 config BOOTP_PXE_CLIENTARCH
1106 depends on BOOTP_PXE
1107 default 0x16 if ARM64
1111 config BOOTP_VCI_STRING
1113 depends on CMD_BOOTP
1114 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1115 default "U-Boot.armv8" if ARM64
1116 default "U-Boot.arm" if ARM
1123 tftpboot - boot image via network using TFTP protocol
1127 depends on CMD_TFTPBOOT
1129 TFTP put command, for uploading files to a server
1133 depends on CMD_TFTPBOOT
1135 Act as a TFTP server and boot the first received file
1137 config NET_TFTP_VARS
1138 bool "Control TFTP timeout and count through environment"
1139 depends on CMD_TFTPBOOT
1142 If set, allows controlling the TFTP timeout through the
1143 environment variable tftptimeout, and the TFTP maximum
1144 timeout count through the variable tftptimeoutcountmax.
1145 If unset, timeout and maximum are hard-defined as 1 second
1146 and 10 timouts per TFTP transfer.
1151 Boot image via network using RARP/TFTP protocol
1157 Boot image via network using NFS protocol.
1162 Enable MII utility commands.
1167 Send ICMP ECHO_REQUEST to network host
1172 Perform CDP network configuration
1177 Synchronize RTC via network
1182 Lookup the IP of a hostname
1184 config CMD_LINK_LOCAL
1187 Acquire a network IP address using the link-local protocol
1194 Allow control of L2 Ethernet switch commands. These are supported
1195 by the vsc9953 Ethernet driver at present. Sub-commands allow
1196 operations such as enabling / disabling a port and
1197 viewing/maintaining the filtering database (FDB)
1203 Boot image via network using PXE protocol
1207 menu "Misc commands"
1210 bool "Enable 'bmp' command"
1211 depends on LCD || DM_VIDEO || VIDEO
1213 This provides a way to obtain information about a BMP-format iamge
1214 and to display it. BMP (which presumably stands for BitMaP) is a
1215 file format defined by Microsoft which supports images of various
1216 depths, formats and compression methods. Headers on the file
1217 determine the formats used. This command can be used by first loading
1218 the image into RAM, then using this command to look at it or display
1222 bool "Enable board-specific commands"
1224 (deprecated: instead, please define a Kconfig option for each command)
1226 Some boards have board-specific commands which are only enabled
1227 during developemnt and need to be turned off for production. This
1228 option provides a way to control this. The commands that are enabled
1229 vary depending on the board.
1231 config CMD_BKOPS_ENABLE
1232 bool "mmc bkops enable"
1236 Enable command for setting manual background operations handshake
1237 on a eMMC device. The feature is optionally available on eMMC devices
1238 conforming to standard >= 4.41.
1240 config CMD_BLOCK_CACHE
1241 bool "blkcache - control and stats for block cache"
1242 depends on BLOCK_CACHE
1243 default y if BLOCK_CACHE
1245 Enable the blkcache command, which can be used to control the
1246 operation of the cache functions.
1247 This is most useful when fine-tuning the operation of the cache
1248 during development, but also allows the cache to be disabled when
1249 it might hurt performance (e.g. when using the ums command).
1252 bool "icache or dcache"
1254 Enable the "icache" and "dcache" commands
1257 bool "Enable the 'display' command, for character displays"
1259 (this needs porting to driver model)
1260 This enables the 'display' command which allows a string to be
1261 displayed on a simple board-specific display. Implement
1262 display_putc() to use it.
1268 Enable the 'led' command which allows for control of LEDs supported
1269 by the board. The LEDs can be listed with 'led list' and controlled
1270 with led on/off/togle/blink. Any LED drivers can be controlled with
1271 this command, e.g. led_gpio.
1277 Enable the 'date' command for getting/setting the time/date in RTC
1283 Run commands and summarize execution time.
1286 bool "gettime - read elapsed time"
1288 Enable the 'gettime' command which reads the elapsed time since
1289 U-Boot started running. This shows the time in seconds and
1290 milliseconds. See also the 'bootstage' command which provides more
1291 flexibility for boot timing.
1293 # TODO: rename to CMD_SLEEP
1298 Delay execution for some time
1303 Access the system timer.
1309 This provides basic access to the U-Boot's sound support. The main
1310 feature is to play a beep.
1312 sound init - set up sound system
1313 sound play - play a sound
1319 This provides access to the QEMU firmware interface. The main
1320 feature is to allow easy loading of files passed to qemu-system
1321 via -kernel / -initrd
1323 source "cmd/mvebu/Kconfig"
1326 bool "terminal - provides a way to attach a serial terminal"
1328 Provides a 'cu'-like serial terminal command. This can be used to
1329 access other serial ports from the system console. The terminal
1330 is very simple with no special processing of characters. As with
1331 cu, you can press ~. (tilde followed by period) to exit.
1334 bool "uuid, guid - generation of unique IDs"
1337 This enables two commands:
1339 uuid - generate random Universally Unique Identifier
1340 guid - generate Globally Unique Identifier based on random UUID
1342 The two commands are very similar except for the endianness of the
1347 source "cmd/ti/Kconfig"
1349 config CMD_BOOTSTAGE
1350 bool "Enable the 'bootstage' command"
1351 depends on BOOTSTAGE
1353 Add a 'bootstage' command which supports printing a report
1354 and un/stashing of bootstage data.
1356 menu "Power commands"
1358 bool "Enable Driver Model PMIC command"
1361 This is the pmic command, based on a driver model pmic's API.
1362 Command features are unchanged:
1363 - list - list pmic devices
1364 - pmic dev <id> - show or [set] operating pmic device (NEW)
1365 - pmic dump - dump registers
1366 - pmic read address - read byte of register at address
1367 - pmic write address - write byte to register at address
1368 The only one change for this command is 'dev' subcommand.
1370 config CMD_REGULATOR
1371 bool "Enable Driver Model REGULATOR command"
1372 depends on DM_REGULATOR
1374 This command is based on driver model regulator's API.
1375 User interface features:
1376 - list - list regulator devices
1377 - regulator dev <id> - show or [set] operating regulator device
1378 - regulator info - print constraints info
1379 - regulator status - print operating status
1380 - regulator value <val] <-f> - print/[set] voltage value [uV]
1381 - regulator current <val> - print/[set] current value [uA]
1382 - regulator mode <id> - print/[set] operating mode id
1383 - regulator enable - enable the regulator output
1384 - regulator disable - disable the regulator output
1386 The '-f' (force) option can be used for set the value which exceeds
1387 the limits, which are found in device-tree and are kept in regulator's
1388 uclass platdata structure.
1392 menu "Security commands"
1394 bool "Enable the 'aes' command"
1397 This provides a means to encrypt and decrypt data using the AES
1398 (Advanced Encryption Standard). This algorithm uses a symetric key
1399 and is widely used as a streaming cipher. Different key lengths are
1400 supported by the algorithm but this command only supports 128 bits
1404 bool "Enable the 'blob' command"
1406 This is used with the Freescale secure boot mechanism.
1408 Freescale's SEC block has built-in Blob Protocol which provides
1409 a method for protecting user-defined data across system power
1410 cycles. SEC block protects data in a data structure called a Blob,
1411 which provides both confidentiality and integrity protection.
1413 Encapsulating data as a blob
1414 Each time that the Blob Protocol is used to protect data, a
1415 different randomly generated key is used to encrypt the data.
1416 This random key is itself encrypted using a key which is derived
1417 from SoC's non-volatile secret key and a 16 bit Key identifier.
1418 The resulting encrypted key along with encrypted data is called a
1419 blob. The non-volatile secure key is available for use only during
1422 During decapsulation, the reverse process is performed to get back
1426 blob enc - encapsulating data as a cryptgraphic blob
1427 blob dec - decapsulating cryptgraphic blob to get the data
1431 blob enc src dst len km
1433 Encapsulate and create blob of data $len bytes long
1434 at address $src and store the result at address $dst.
1435 $km is the 16 byte key modifier is also required for
1436 generation/use as key for cryptographic operation. Key
1437 modifier should be 16 byte long.
1439 blob dec src dst len km
1441 Decapsulate the blob of data at address $src and
1442 store result of $len byte at addr $dst.
1443 $km is the 16 byte key modifier is also required for
1444 generation/use as key for cryptographic operation. Key
1445 modifier should be 16 byte long.
1448 bool "Support 'hash' command"
1451 This provides a way to hash data in memory using various supported
1452 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1453 saved to memory or to an environment variable. It is also possible
1454 to verify a hash against data in memory.
1457 bool "Support the 'hvc' command"
1458 depends on ARM_SMCCC
1460 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1461 development and testing.
1464 bool "Support the 'smc' command"
1465 depends on ARM_SMCCC
1467 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1468 development and testing.
1474 Add -v option to verify data against a hash.
1477 bool "Enable the 'tpm' command"
1480 This provides a means to talk to a TPM from the command line. A wide
1481 range of commands if provided - see 'tpm help' for details. The
1482 command requires a suitable TPM on your board and the correct driver
1486 bool "Enable the 'tpm test' command"
1489 This provides a a series of tests to confirm that the TPM is working
1490 correctly. The tests cover initialisation, non-volatile RAM, extend,
1491 global lock and checking that timing is within expectations. The
1492 tests pass correctly on Infineon TPMs but may need to be adjusted
1497 menu "Firmware commands"
1499 bool "Enable crosec command"
1503 Enable command-line access to the Chrome OS EC (Embedded
1504 Controller). This provides the 'crosec' command which has
1505 a number of sub-commands for performing EC tasks such as
1506 updating its flash, accessing a small saved context area
1507 and talking to the I2C bus behind the EC (if there is one).
1510 menu "Filesystem commands"
1512 bool "Enable the 'btrsubvol' command"
1515 This enables the 'btrsubvol' command to list subvolumes
1516 of a BTRFS filesystem. There are no special commands for
1517 listing BTRFS directories or loading BTRFS files - this
1518 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1519 when BTRFS is enabled (see FS_BTRFS).
1522 bool "Enable the 'cbfs' command"
1525 Define this to enable support for reading from a Coreboot
1526 filesystem. This is a ROM-based filesystem used for accessing files
1527 on systems that use coreboot as the first boot-loader and then load
1528 U-Boot to actually boot the Operating System. Available commands are
1529 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1532 bool "Enable the 'cramfs' command"
1533 depends on FS_CRAMFS
1535 This provides commands for dealing with CRAMFS (Compressed ROM
1536 filesystem). CRAMFS is useful when space is tight since files are
1537 compressed. Two commands are provided:
1539 cramfsls - lists files in a cramfs image
1540 cramfsload - loads a file from a cramfs image
1543 bool "ext2 command support"
1546 Enables EXT2 FS command
1549 bool "ext4 command support"
1552 Enables EXT4 FS command
1554 config CMD_EXT4_WRITE
1556 bool "ext4 write command support"
1559 Enables EXT4 FS write command
1562 bool "FAT command support"
1565 Support for the FAT fs
1567 config CMD_FS_GENERIC
1568 bool "filesystem commands"
1570 Enables filesystem commands (e.g. load, ls) that work for multiple
1574 bool "fsuuid command"
1576 Enables fsuuid command for filesystem UUID.
1579 bool "jffs2 command"
1582 Enables commands to support the JFFS2 (Journalling Flash File System
1583 version 2) filesystem. This enables fsload, ls and fsinfo which
1584 provide the ability to load files, list directories and obtain
1585 filesystem information.
1588 bool "MTD partition support"
1590 MTD partition support
1592 config MTDIDS_DEFAULT
1593 string "Default MTD IDs"
1594 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1596 Defines a default MTD IDs list for use with MTD partitions in the
1597 Linux MTD command line partitions format.
1599 config MTDPARTS_DEFAULT
1600 string "Default MTD partition scheme"
1601 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1603 Defines a default MTD partitioning scheme in the Linux MTD command
1604 line partitions format
1606 config CMD_MTDPARTS_SPREAD
1607 bool "Padd partition size to take account of bad blocks"
1608 depends on CMD_MTDPARTS
1610 This enables the 'spread' sub-command of the mtdparts command.
1611 This command will modify the existing mtdparts variable by increasing
1612 the size of the partitions such that 1) each partition's net size is
1613 at least as large as the size specified in the mtdparts variable and
1614 2) each partition starts on a good block.
1617 bool "reiser - Access to reiserfs filesystems"
1619 This provides two commands which operate on a resierfs filesystem,
1620 commonly used some years ago:
1622 reiserls - list files
1623 reiserload - load a file
1626 bool "yaffs2 - Access of YAFFS2 filesystem"
1630 This provides commands for accessing a YAFFS2 filesystem. Yet
1631 Another Flash Filesystem 2 is a filesystem designed specifically
1632 for NAND flash. It incorporates bad-block management and ensures
1633 that device writes are sequential regardless of filesystem
1637 bool "zfs - Access of ZFS filesystem"
1639 This provides commands to accessing a ZFS filesystem, commonly used
1640 on Solaris systems. Two sub-commands are provided:
1642 zfsls - list files in a directory
1643 zfsload - load a file
1645 See doc/README.zfs for more details.
1649 menu "Debug commands"
1654 The bedbug (emBEDded deBUGger) command provides debugging features
1655 for some PowerPC processors. For details please see the
1656 docuemntation in doc/README.beddbug
1659 bool "diag - Board diagnostics"
1661 This command provides access to board diagnostic tests. These are
1662 called Power-on Self Tests (POST). The command allows listing of
1663 available tests and running either all the tests, or specific tests
1667 bool "irq - Show information about interrupts"
1668 depends on !ARM && !MIPS && !SH
1670 This enables two commands:
1672 interrupts - enable or disable interrupts
1673 irqinfo - print device-specific interrupt information
1676 bool "kgdb - Allow debugging of U-Boot with gdb"
1678 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1679 over a serial link for debugging purposes. This allows
1680 single-stepping, inspecting variables, etc. This is supported only
1681 on PowerPC at present.
1684 bool "log - Generation, control and access to logging"
1687 This provides access to logging features. It allows the output of
1688 log data to be controlled to a limited extent (setting up the default
1689 maximum log level for emitting of records). It also provides access
1690 to a command used for testing the log system.
1693 bool "trace - Support tracing of function calls and timing"
1695 Enables a command to control using of function tracing within
1696 U-Boot. This allows recording of call traces including timing
1697 information. The command can write data to memory for exporting
1698 for analsys (e.g. using bootchart). See doc/README.trace for full
1704 tristate "Enable UBI - Unsorted block images commands"
1708 default y if NAND_SUNXI
1710 UBI is a software layer above MTD layer which admits use of LVM-like
1711 logical volumes on top of MTD devices, hides some complexities of
1712 flash chips like wear and bad blocks and provides some other useful
1713 capabilities. Please, consult the MTD web site for more details
1714 (www.linux-mtd.infradead.org). Activate this option if you want
1715 to use U-Boot UBI commands.
1718 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1722 default y if CMD_UBI
1724 UBIFS is a file system for flash devices which works on top of UBI.
projects / u-boot / blob