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.
30 This string is displayed in the command line to the left of the
33 menu "Autoboot options"
39 This enables the autoboot. See doc/README.autoboot for detail.
42 bool "Stop autobooting via specific input key / string"
45 This option enables stopping (aborting) of the automatic
46 boot feature only by issuing a specific input key or
47 string. If not enabled, any input key will abort the
48 U-Boot automatic booting process and bring the device
49 to the U-Boot prompt for user input.
51 config AUTOBOOT_PROMPT
52 string "Autoboot stop prompt"
53 depends on AUTOBOOT_KEYED
54 default "Autoboot in %d seconds\\n"
56 This string is displayed before the boot delay selected by
57 CONFIG_BOOTDELAY starts. If it is not defined there is no
58 output indicating that autoboot is in progress.
60 Note that this define is used as the (only) argument to a
61 printf() call, so it may contain '%' format specifications,
62 provided that it also includes, sepearated by commas exactly
63 like in a printf statement, the required arguments. It is
64 the responsibility of the user to select only such arguments
65 that are valid in the given context.
67 config AUTOBOOT_ENCRYPTION
68 bool "Enable encryption in autoboot stopping"
69 depends on AUTOBOOT_KEYED
72 config AUTOBOOT_DELAY_STR
73 string "Delay autobooting via specific input key / string"
74 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
76 This option delays the automatic boot feature by issuing
77 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
78 or the environment variable "bootdelaykey" is specified
79 and this string is received from console input before
80 autoboot starts booting, U-Boot gives a command prompt. The
81 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
82 used, otherwise it never times out.
84 config AUTOBOOT_STOP_STR
85 string "Stop autobooting via specific input key / string"
86 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
88 This option enables stopping (aborting) of the automatic
89 boot feature only by issuing a specific input key or
90 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
91 variable "bootstopkey" is specified and this string is
92 received from console input before autoboot starts booting,
93 U-Boot gives a command prompt. The U-Boot prompt never
94 times out, even if CONFIG_BOOT_RETRY_TIME is used.
96 config AUTOBOOT_KEYED_CTRLC
97 bool "Enable Ctrl-C autoboot interruption"
98 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
101 This option allows for the boot sequence to be interrupted
102 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
103 Setting this variable provides an escape sequence from the
104 limited "password" strings.
106 config AUTOBOOT_STOP_STR_SHA256
107 string "Stop autobooting via SHA256 encrypted password"
108 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
110 This option adds the feature to only stop the autobooting,
111 and therefore boot into the U-Boot prompt, when the input
112 string / password matches a values that is encypted via
113 a SHA256 hash and saved in the environment.
117 source "cmd/fastboot/Kconfig"
137 Print ".config" contents.
139 If this option is enabled, the ".config" file contents are embedded
140 in the U-Boot image and can be printed on the console by the "config"
141 command. This provides information of which options are enabled on
148 Print console devices and information.
153 Print information about available CPUs. This normally shows the
154 number of CPUs, type (e.g. manufacturer, architecture, product or
155 internal name) and clock frequency. Other information may be
156 available depending on the CPU driver.
162 Print GPL license text
178 Run the command stored in the environment "bootcmd", i.e.
179 "bootd" does the same thing as "run bootcmd".
185 Boot an application image from the memory.
190 Boot the Linux zImage
197 Boot an AArch64 Linux Kernel image from memory.
201 depends on EFI_LOADER
204 Boot an EFI image from memory.
206 config CMD_BOOTEFI_HELLO_COMPILE
207 bool "Compile a standard EFI hello world binary for testing"
208 depends on CMD_BOOTEFI && (ARM || X86)
211 This compiles a standard EFI hello world application with U-Boot so
212 that it can be used with the test/py testing framework. This is useful
213 for testing that EFI is working at a basic level, and for bringing
214 up EFI support on a new architecture.
216 No additional space will be required in the resulting U-Boot binary
217 when this option is enabled.
219 config CMD_BOOTEFI_HELLO
220 bool "Allow booting a standard EFI hello world for testing"
221 depends on CMD_BOOTEFI_HELLO_COMPILE
223 This adds a standard EFI hello world application to U-Boot so that
224 it can be used with the 'bootefi hello' command. This is useful
225 for testing that EFI is working at a basic level, and for bringing
226 up EFI support on a new architecture.
228 source lib/efi_selftest/Kconfig
234 Add an ANSI terminal boot menu command.
237 bool "bootelf, bootvx"
240 Boot an ELF/vxWorks image from the memory.
243 bool "Flattened Device Tree utility commands"
247 Do FDT related setup before booting into the Operating System.
253 Start an application at a given address.
259 Run the command in the given environment variable.
265 Print header information for application image.
270 List all images found in flash
276 Extract a part of a multi-image.
281 Poweroff/Shutdown the system
284 bool "spl export - Export boot information for Falcon boot"
287 Falcon mode allows booting directly from SPL into an Operating
288 System such as Linux, thus skipping U-Boot proper. See
289 doc/README.falcon for full information about how to use this
292 config CMD_SPL_NAND_OFS
293 hex "Offset of OS command line args for Falcon-mode NAND boot"
297 This provides the offset of the command line arguments for Linux
298 when booting from NAND in Falcon mode. See doc/README.falcon
299 for full information about how to use this option (and also see
300 board/gateworks/gw_ventana/README for an example).
302 config CMD_SPL_WRITE_SIZE
303 hex "Size of argument area"
307 This provides the size of the command-line argument area in NAND
308 flash used by Falcon-mode boot. See the documentation until CMD_SPL
312 bool "fitImage update command"
314 Implements the 'fitupd' command, which allows to automatically
315 store software updates present on a TFTP server in NOR Flash
317 config CMD_THOR_DOWNLOAD
318 bool "thor - TIZEN 'thor' download"
320 Implements the 'thor' download protocol. This is a way of
321 downloading a software update over USB from an attached host.
322 There is no documentation about this within the U-Boot source code
323 but you should be able to find something on the interwebs.
326 bool "zboot - x86 boot command"
328 With x86 machines it is common to boot a bzImage file which
329 contains both a kernel and a setup.bin file. The latter includes
330 configuration information from the dark ages which x86 boards still
331 need to pick things out of.
333 Consider using FIT in preference to this since it supports directly
334 booting both 32- and 64-bit kernels, as well as secure boot.
335 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
339 menu "Environment commands"
342 bool "ask for env variable"
344 Ask for environment variable
362 Edit environment variable.
367 Allow for searching environment variables
373 Save all environment variables into the compiled-in persistent
376 config CMD_ENV_EXISTS
380 Check if a variable is defined in the environment for use in
383 config CMD_ENV_CALLBACK
384 bool "env callbacks - print callbacks and their associated variables"
386 Some environment variable have callbacks defined by
387 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
388 For example changing "baudrate" adjust the serial baud rate. This
389 command lists the currently defined callbacks.
392 bool "env flags -print variables that have non-default flags"
394 Some environment variables have special flags that control their
395 behaviour. For example, serial# can only be written once and cannot
396 be deleted. This command shows the variables that have special
401 menu "Memory commands"
406 default n if ARCH_SUNXI
415 Add -v option to verify data against a crc32 checksum.
418 bool "eeprom - EEPROM subsystem"
420 (deprecated, needs conversion to driver model)
421 Provides commands to read and write EEPROM (Electrically Erasable
422 Programmable Read Only Memory) chips that are connected over an
425 config CMD_EEPROM_LAYOUT
426 bool "Enable layout-aware eeprom commands"
427 depends on CMD_EEPROM
429 (deprecated, needs conversion to driver model)
430 When enabled, additional eeprom sub-commands become available.
432 eeprom print - prints the contents of the eeprom in a human-readable
433 way (eeprom layout fields, and data formatted to be fit for human
436 eeprom update - allows user to update eeprom fields by specifying
437 the field name, and providing the new data in a human readable format
438 (same format as displayed by the eeprom print command).
440 Both commands can either auto detect the layout, or be told which
444 __weak int parse_layout_version(char *str)
445 - override to provide your own layout name parsing
446 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
448 - override to setup the layout metadata based on the version
449 __weak int eeprom_layout_detect(unsigned char *data)
450 - override to provide your own algorithm for detecting layout
453 - contains various printing and updating functions for common
454 types of eeprom fields. Can be used for defining
457 config EEPROM_LAYOUT_HELP_STRING
458 string "Tells user what layout names are supported"
459 depends on CMD_EEPROM_LAYOUT
460 default "<not defined>"
462 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
468 Infinite write loop on address range
475 Compute MD5 checksum.
480 depends on CMD_MD5SUM
482 Add -v option to verify data against an MD5 checksum.
487 Display memory information.
490 bool "md, mm, nm, mw, cp, cmp, base, loop"
495 mm - memory modify (auto-incrementing address)
496 nm - memory modify (constant address)
497 mw - memory write (fill)
500 base - print or set address offset
501 loop - initialize loop on address range
506 Simple RAM read/write test.
511 mdc - memory display cyclic
512 mwc - memory write cyclic
518 Compute SHA1 checksum.
520 config SHA1SUM_VERIFY
522 depends on CMD_SHA1SUM
524 Add -v option to verify data against a SHA1 checksum.
527 bool "strings - display strings in memory"
529 This works similarly to the Unix 'strings' command except that it
530 works with a memory range. String of printable characters found
531 within the range are displayed. The minimum number of characters
532 for a sequence to be considered a string can be provided.
536 menu "Compression commands"
540 default y if CMD_BOOTI
543 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
548 default n if ARCH_SUNXI
549 default y if CMD_BOOTI
551 Uncompress a zip-compressed memory region.
556 Compress a memory region with zlib deflate method.
560 menu "Device access commands"
563 #depends on FLASH_CFI_DRIVER
566 ARM Ltd reference designs flash partition access
569 bool "clk - Show clock frequencies"
572 Shows clock frequences by calling a sock_clk_dump() hook function.
573 This is depreated in favour of using the CLK uclass and accessing
574 clock values from associated drivers. However currently no command
578 bool "demo - Demonstration commands for driver model"
581 Provides a 'demo' command which can be used to play around with
582 driver model. To use this properly you will need to enable one or
583 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
584 Otherwise you will always get an empty list of devices. The demo
585 devices are defined in the sandbox device tree, so the easiest
586 option is to use sandbox and pass the -d point to sandbox's
593 Enables the command "dfu" which is used to have U-Boot create a DFU
594 class device via USB. This command requires that the "dfu_alt_info"
595 environment variable be set and define the alt settings to expose to
599 bool "dm - Access to driver model information"
603 Provides access to driver model data structures and information,
604 such as a list of devices, list of uclasses and the state of each
605 device (e.g. activated). This is not required for operation, but
606 can be useful to see the state of driver model for debugging or
610 bool "fdcboot - Boot from floppy device"
612 The 'fdtboot' command allows booting an image from a floppy disk.
615 bool "flinfo, erase, protect"
619 flinfo - print FLASH memory information
621 protect - enable or disable FLASH write protection
630 config CMD_FPGA_LOADBP
631 bool "fpga loadbp - load partial bitstream (Xilinx only)"
634 Supports loading an FPGA device from a bitstream buffer containing
637 config CMD_FPGA_LOADFS
638 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
641 Supports loading an FPGA device from a FAT filesystem.
643 config CMD_FPGA_LOADMK
644 bool "fpga loadmk - load bitstream from image"
647 Supports loading an FPGA device from a image generated by mkimage.
649 config CMD_FPGA_LOADP
650 bool "fpga loadp - load partial bitstream"
653 Supports loading an FPGA device from a bitstream buffer containing
657 bool "fpgad - dump FPGA registers"
659 (legacy, needs conversion to driver model)
660 Provides a way to dump FPGA registers by calling the board-specific
661 fpga_get_reg() function. This functions similarly to the 'md'
665 bool "fuse - support for the fuse subssystem"
667 (deprecated - needs conversion to driver model)
668 This allows reading, sensing, programming or overriding fuses
669 which control the behaviour of the device. The command uses the
678 bool "GPT (GUID Partition Table) command"
679 select PARTITION_UUIDS
681 select HAVE_BLOCK_DEVICE
684 Enable the 'gpt' command to ready and write GPT style partition
688 bool "GPT Random UUID generation"
691 Enable the generation of partitions with random UUIDs if none
694 config CMD_GPT_RENAME
695 bool "GPT partition renaming commands"
698 Enables the 'gpt' command to interchange names on two GPT
699 partitions via the 'gpt swap' command or to rename single
700 partitions via the 'rename' command.
703 bool "ide - Support for IDE drivers"
706 Provides an 'ide' command which allows accessing the IDE drive,
707 reseting the IDE interface, printing the partition table and
708 geting device info. It also enables the 'diskboot' command which
709 permits booting from an IDE drive.
712 bool "io - Support for performing I/O accesses"
714 Provides an 'iod' command to display I/O space and an 'iow' command
715 to write values to the I/O space. This can be useful for manually
716 checking the state of devices during boot when debugging device
720 bool "iotrace - Support for tracing I/O activity"
722 Provides an 'iotrace' command which supports recording I/O reads and
723 writes in a trace buffer in memory . It also maintains a checksum
724 of the trace records (even if space is exhausted) so that the
725 sequence of I/O accesses can be verified.
727 When debugging drivers it is useful to see what I/O accesses were
728 done and in what order.
730 Even if the individual accesses are of little interest it can be
731 useful to verify that the access pattern is consistent each time
732 an operation is performed. In this case a checksum can be used to
733 characterise the operation of a driver. The checksum can be compared
734 across different runs of the operation to verify that the driver is
737 In particular, when performing major refactoring of the driver, where
738 the access pattern should not change, the checksum provides assurance
739 that the refactoring work has not broken the driver.
741 This works by sneaking into the io.h heder for an architecture and
742 redirecting I/O accesses through iotrace's tracing mechanism.
744 For now no commands are provided to examine the trace buffer. The
745 format is fairly simple, so 'md' is a reasonable substitute.
747 Note: The checksum feature is only useful for I/O regions where the
748 contents do not change outside of software control. Where this is not
749 suitable you can fall back to manually comparing the addresses. It
750 might be useful to enhance tracing to only checksum the accesses and
751 not the data read/written.
760 default n if ARCH_SUNXI
763 Load a binary file over serial line.
767 default n if ARCH_SUNXI
770 Load an S-Record file over serial line
775 MMC memory mapped support.
779 default y if NAND_SUNXI
784 config CMD_NAND_TRIMFFS
785 bool "nand write.trimffs"
786 default y if ARCH_SUNXI
788 Allows one to skip empty pages when flashing something on a NAND.
790 config CMD_NAND_LOCK_UNLOCK
791 bool "nand lock/unlock"
793 NAND locking support.
795 config CMD_NAND_TORTURE
798 NAND torture support.
807 NVM Express device support
810 bool "mmc_spi - Set up MMC SPI device"
812 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
813 Peripheral Interface) device. The device provides a means of
814 accessing an MMC device via SPI using a single data line, limited
815 to 20MHz. It is useful since it reduces the amount of protocol code
819 bool "onenand - access to onenand device"
821 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
822 various useful features. This command allows reading, writing,
823 and erasing blocks. It allso provides a way to show and change
824 bad blocks, and test the device.
828 select PARTITION_UUIDS
829 select HAVE_BLOCK_DEVICE
831 Read and display information about the partition table on
835 bool "pci - Access PCI devices"
837 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
838 used on some devices to allow the CPU to communicate with its
839 peripherals. Sub-commands allow bus enumeration, displaying and
840 changing configuration space and a few other features.
843 bool "pinit - Set up PCMCIA device"
845 Provides a means to initialise a PCMCIA (Personal Computer Memory
846 Card International Association) device. This is an old standard from
847 about 1990. These devices are typically removable memory or network
848 cards using a standard 68-pin connector.
851 bool "read - Read binary data from a partition"
853 Provides low-level access to the data in a partition.
855 config CMD_REMOTEPROC
857 depends on REMOTEPROC
859 Support for Remote Processor control
862 bool "sata - Access SATA subsystem"
865 SATA (Serial Advanced Technology Attachment) is a serial bus
866 standard for connecting to hard drives and other storage devices.
867 This command provides information about attached devices and allows
868 reading, writing and other operations.
870 SATA replaces PATA (originally just ATA), which stands for Parallel AT
871 Attachment, where AT refers to an IBM AT (Advanced Technology)
872 computer released in 1984.
875 bool "saves - Save a file over serial in S-Record format"
877 Provides a way to save a binary file using the Motorola S-Record
878 format over the serial line.
881 bool "scsi - Access to SCSI devices"
884 This provides a 'scsi' command which provides access to SCSI (Small
885 Computer System Interface) devices. The command provides a way to
886 scan the bus, reset the bus, read and write data and get information
890 bool "sdram - Print SDRAM configuration information"
892 Provides information about attached SDRAM. This assumed that the
893 SDRAM has an EEPROM with information that can be read using the
894 I2C bus. This is only available on some boards.
902 bool "sf test - Allow testing of SPI flash"
904 Provides a way to test that SPI flash is working correctly. The
905 test is destructive, in that an area of SPI flash must be provided
906 for the test to use. Performance information is also provided,
907 measuring the performance of reading, writing and erasing in
908 Mbps (Million Bits Per Second). This value should approximately
909 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
910 everything is working properly.
918 bool "tsi148 - Command to access tsi148 device"
920 This provides various sub-commands to initialise and configure the
921 Turndra tsi148 device. See the command help for full details.
924 bool "universe - Command to set up the Turndra Universe controller"
926 This allows setting up the VMEbus provided by this controller.
927 See the command help for full details.
931 select HAVE_BLOCK_DEVICE
937 select USB_FUNCTION_SDP
939 Enables the command "sdp" which is used to have U-Boot emulating the
940 Serial Download Protocol (SDP) via USB.
943 depends on USB_FUNCTION_ROCKUSB
945 Rockusb protocol is widely used by Rockchip SoC based devices. It can
946 read/write info, image to/from devices. This enable rockusb command
947 support to communication with rockusb device. for more detail about
948 this command, please read doc/README.rockusb.
950 config CMD_USB_MASS_STORAGE
951 bool "UMS usb mass storage"
952 select USB_FUNCTION_MASS_STORAGE
954 USB mass storage support
959 menu "Shell scripting commands"
971 Return true/false on integer compare.
977 Run script from memory
983 Evaluate boolean and math expressions and store the result in an env
985 Also supports loading the value at a memory location into a variable.
986 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
990 menu "Network commands"
993 bool "bootp, tftpboot"
998 bootp - boot image via network using BOOTP/TFTP protocol
999 tftpboot - boot image via network using TFTP protocol
1004 TFTP put command, for uploading files to a server
1009 Act as a TFTP server and boot the first received file
1014 Boot image via network using RARP/TFTP protocol
1019 Boot image via network using DHCP/TFTP protocol
1025 Boot image via network using PXE protocol
1031 Boot image via network using NFS protocol.
1036 Enable MII utility commands.
1041 Send ICMP ECHO_REQUEST to network host
1046 Perform CDP network configuration
1051 Synchronize RTC via network
1056 Lookup the IP of a hostname
1058 config CMD_LINK_LOCAL
1061 Acquire a network IP address using the link-local protocol
1066 Allow control of L2 Ethernet switch commands. These are supported
1067 by the vsc9953 Ethernet driver at present. Sub-commands allow
1068 operations such as enabling / disabling a port and
1069 viewing/maintaining the filtering database (FDB)
1073 menu "Misc commands"
1076 bool "Enable 'bmp' command"
1077 depends on LCD || DM_VIDEO || VIDEO
1079 This provides a way to obtain information about a BMP-format iamge
1080 and to display it. BMP (which presumably stands for BitMaP) is a
1081 file format defined by Microsoft which supports images of various
1082 depths, formats and compression methods. Headers on the file
1083 determine the formats used. This command can be used by first loading
1084 the image into RAM, then using this command to look at it or display
1088 bool "Enable board-specific commands"
1090 (deprecated: instead, please define a Kconfig option for each command)
1092 Some boards have board-specific commands which are only enabled
1093 during developemnt and need to be turned off for production. This
1094 option provides a way to control this. The commands that are enabled
1095 vary depending on the board.
1097 config CMD_BKOPS_ENABLE
1098 bool "mmc bkops enable"
1102 Enable command for setting manual background operations handshake
1103 on a eMMC device. The feature is optionally available on eMMC devices
1104 conforming to standard >= 4.41.
1106 config CMD_BLOCK_CACHE
1107 bool "blkcache - control and stats for block cache"
1108 depends on BLOCK_CACHE
1109 default y if BLOCK_CACHE
1111 Enable the blkcache command, which can be used to control the
1112 operation of the cache functions.
1113 This is most useful when fine-tuning the operation of the cache
1114 during development, but also allows the cache to be disabled when
1115 it might hurt performance (e.g. when using the ums command).
1118 bool "icache or dcache"
1120 Enable the "icache" and "dcache" commands
1123 bool "Enable the 'display' command, for character displays"
1125 (this needs porting to driver model)
1126 This enables the 'display' command which allows a string to be
1127 displayed on a simple board-specific display. Implement
1128 display_putc() to use it.
1134 Enable the 'led' command which allows for control of LEDs supported
1135 by the board. The LEDs can be listed with 'led list' and controlled
1136 with led on/off/togle/blink. Any LED drivers can be controlled with
1137 this command, e.g. led_gpio.
1143 Enable the 'date' command for getting/setting the time/date in RTC
1149 Run commands and summarize execution time.
1152 bool "gettime - read elapsed time"
1154 Enable the 'gettime' command which reads the elapsed time since
1155 U-Boot started running. This shows the time in seconds and
1156 milliseconds. See also the 'bootstage' command which provides more
1157 flexibility for boot timing.
1159 # TODO: rename to CMD_SLEEP
1162 default n if ARCH_SUNXI
1165 Delay execution for some time
1170 Access the system timer.
1176 This provides basic access to the U-Boot's sound support. The main
1177 feature is to play a beep.
1179 sound init - set up sound system
1180 sound play - play a sound
1186 This provides access to the QEMU firmware interface. The main
1187 feature is to allow easy loading of files passed to qemu-system
1188 via -kernel / -initrd
1190 source "cmd/mvebu/Kconfig"
1193 bool "terminal - provides a way to attach a serial terminal"
1195 Provides a 'cu'-like serial terminal command. This can be used to
1196 access other serial ports from the system console. The terminal
1197 is very simple with no special processing of characters. As with
1198 cu, you can press ~. (tilde followed by period) to exit.
1201 bool "uuid, guid - generation of unique IDs"
1204 This enables two commands:
1206 uuid - generate random Universally Unique Identifier
1207 guid - generate Globally Unique Identifier based on random UUID
1209 The two commands are very similar except for the endianness of the
1214 source "cmd/ti/Kconfig"
1216 config CMD_BOOTSTAGE
1217 bool "Enable the 'bootstage' command"
1218 depends on BOOTSTAGE
1220 Add a 'bootstage' command which supports printing a report
1221 and un/stashing of bootstage data.
1223 menu "Power commands"
1225 bool "Enable Driver Model PMIC command"
1228 This is the pmic command, based on a driver model pmic's API.
1229 Command features are unchanged:
1230 - list - list pmic devices
1231 - pmic dev <id> - show or [set] operating pmic device (NEW)
1232 - pmic dump - dump registers
1233 - pmic read address - read byte of register at address
1234 - pmic write address - write byte to register at address
1235 The only one change for this command is 'dev' subcommand.
1237 config CMD_REGULATOR
1238 bool "Enable Driver Model REGULATOR command"
1239 depends on DM_REGULATOR
1241 This command is based on driver model regulator's API.
1242 User interface features:
1243 - list - list regulator devices
1244 - regulator dev <id> - show or [set] operating regulator device
1245 - regulator info - print constraints info
1246 - regulator status - print operating status
1247 - regulator value <val] <-f> - print/[set] voltage value [uV]
1248 - regulator current <val> - print/[set] current value [uA]
1249 - regulator mode <id> - print/[set] operating mode id
1250 - regulator enable - enable the regulator output
1251 - regulator disable - disable the regulator output
1253 The '-f' (force) option can be used for set the value which exceeds
1254 the limits, which are found in device-tree and are kept in regulator's
1255 uclass platdata structure.
1259 menu "Security commands"
1261 bool "Enable the 'aes' command"
1264 This provides a means to encrypt and decrypt data using the AES
1265 (Advanced Encryption Standard). This algorithm uses a symetric key
1266 and is widely used as a streaming cipher. Different key lengths are
1267 supported by the algorithm but this command only supports 128 bits
1271 bool "Enable the 'blob' command"
1273 This is used with the Freescale secure boot mechanism.
1275 Freescale's SEC block has built-in Blob Protocol which provides
1276 a method for protecting user-defined data across system power
1277 cycles. SEC block protects data in a data structure called a Blob,
1278 which provides both confidentiality and integrity protection.
1280 Encapsulating data as a blob
1281 Each time that the Blob Protocol is used to protect data, a
1282 different randomly generated key is used to encrypt the data.
1283 This random key is itself encrypted using a key which is derived
1284 from SoC's non-volatile secret key and a 16 bit Key identifier.
1285 The resulting encrypted key along with encrypted data is called a
1286 blob. The non-volatile secure key is available for use only during
1289 During decapsulation, the reverse process is performed to get back
1293 blob enc - encapsulating data as a cryptgraphic blob
1294 blob dec - decapsulating cryptgraphic blob to get the data
1298 blob enc src dst len km
1300 Encapsulate and create blob of data $len bytes long
1301 at address $src and store the result at address $dst.
1302 $km is the 16 byte key modifier is also required for
1303 generation/use as key for cryptographic operation. Key
1304 modifier should be 16 byte long.
1306 blob dec src dst len km
1308 Decapsulate the blob of data at address $src and
1309 store result of $len byte at addr $dst.
1310 $km is the 16 byte key modifier is also required for
1311 generation/use as key for cryptographic operation. Key
1312 modifier should be 16 byte long.
1315 bool "Support 'hash' command"
1318 This provides a way to hash data in memory using various supported
1319 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1320 saved to memory or to an environment variable. It is also possible
1321 to verify a hash against data in memory.
1327 Add -v option to verify data against a hash.
1330 bool "Enable the 'tpm' command"
1333 This provides a means to talk to a TPM from the command line. A wide
1334 range of commands if provided - see 'tpm help' for details. The
1335 command requires a suitable TPM on your board and the correct driver
1339 bool "Enable the 'tpm test' command"
1342 This provides a a series of tests to confirm that the TPM is working
1343 correctly. The tests cover initialisation, non-volatile RAM, extend,
1344 global lock and checking that timing is within expectations. The
1345 tests pass correctly on Infineon TPMs but may need to be adjusted
1350 menu "Firmware commands"
1352 bool "Enable crosec command"
1356 Enable command-line access to the Chrome OS EC (Embedded
1357 Controller). This provides the 'crosec' command which has
1358 a number of sub-commands for performing EC tasks such as
1359 updating its flash, accessing a small saved context area
1360 and talking to the I2C bus behind the EC (if there is one).
1363 menu "Filesystem commands"
1365 bool "Enable the 'btrsubvol' command"
1368 This enables the 'btrsubvol' command to list subvolumes
1369 of a BTRFS filesystem. There are no special commands for
1370 listing BTRFS directories or loading BTRFS files - this
1371 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1372 when BTRFS is enabled (see FS_BTRFS).
1375 bool "Enable the 'cbfs' command"
1378 Define this to enable support for reading from a Coreboot
1379 filesystem. This is a ROM-based filesystem used for accessing files
1380 on systems that use coreboot as the first boot-loader and then load
1381 U-Boot to actually boot the Operating System. Available commands are
1382 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1385 bool "Enable the 'cramfs' command"
1386 depends on FS_CRAMFS
1388 This provides commands for dealing with CRAMFS (Compressed ROM
1389 filesystem). CRAMFS is useful when space is tight since files are
1390 compressed. Two commands are provided:
1392 cramfsls - lists files in a cramfs image
1393 cramfsload - loads a file from a cramfs image
1396 bool "ext2 command support"
1399 Enables EXT2 FS command
1402 bool "ext4 command support"
1405 Enables EXT4 FS command
1407 config CMD_EXT4_WRITE
1409 bool "ext4 write command support"
1412 Enables EXT4 FS write command
1415 bool "FAT command support"
1418 Support for the FAT fs
1420 config CMD_FS_GENERIC
1421 bool "filesystem commands"
1423 Enables filesystem commands (e.g. load, ls) that work for multiple
1427 bool "fsuuid command"
1429 Enables fsuuid command for filesystem UUID.
1432 bool "jffs2 command"
1435 Enables commands to support the JFFS2 (Journalling Flash File System
1436 version 2) filesystem. This enables fsload, ls and fsinfo which
1437 provide the ability to load files, list directories and obtain
1438 filesystem information.
1441 bool "MTD partition support"
1443 MTD partition support
1445 config MTDIDS_DEFAULT
1446 string "Default MTD IDs"
1447 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1449 Defines a default MTD IDs list for use with MTD partitions in the
1450 Linux MTD command line partitions format.
1452 config MTDPARTS_DEFAULT
1453 string "Default MTD partition scheme"
1454 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1456 Defines a default MTD partitioning scheme in the Linux MTD command
1457 line partitions format
1459 config CMD_MTDPARTS_SPREAD
1460 bool "Padd partition size to take account of bad blocks"
1461 depends on CMD_MTDPARTS
1463 This enables the 'spread' sub-command of the mtdparts command.
1464 This command will modify the existing mtdparts variable by increasing
1465 the size of the partitions such that 1) each partition's net size is
1466 at least as large as the size specified in the mtdparts variable and
1467 2) each partition starts on a good block.
1470 bool "reiser - Access to reiserfs filesystems"
1472 This provides two commands which operate on a resierfs filesystem,
1473 commonly used some years ago:
1475 reiserls - list files
1476 reiserload - load a file
1479 bool "yaffs2 - Access of YAFFS2 filesystem"
1483 This provides commands for accessing a YAFFS2 filesystem. Yet
1484 Another Flash Filesystem 2 is a filesystem designed specifically
1485 for NAND flash. It incorporates bad-block management and ensures
1486 that device writes are sequential regardless of filesystem
1490 bool "zfs - Access of ZFS filesystem"
1492 This provides commands to accessing a ZFS filesystem, commonly used
1493 on Solaris systems. Two sub-commands are provided:
1495 zfsls - list files in a directory
1496 zfsload - load a file
1498 See doc/README.zfs for more details.
1502 menu "Debug commands"
1507 The bedbug (emBEDded deBUGger) command provides debugging features
1508 for some PowerPC processors. For details please see the
1509 docuemntation in doc/README.beddbug
1512 bool "diag - Board diagnostics"
1514 This command provides access to board diagnostic tests. These are
1515 called Power-on Self Tests (POST). The command allows listing of
1516 available tests and running either all the tests, or specific tests
1520 bool "irq - Show information about interrupts"
1521 depends on !ARM && !MIPS && !SH
1523 This enables two commands:
1525 interrupts - enable or disable interrupts
1526 irqinfo - print device-specific interrupt information
1529 bool "kgdb - Allow debugging of U-Boot with gdb"
1531 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1532 over a serial link for debugging purposes. This allows
1533 single-stepping, inspecting variables, etc. This is supported only
1534 on PowerPC at present.
1537 bool "log - Generation, control and access to logging"
1539 This provides access to logging features. It allows the output of
1540 log data to be controlled to a limited extent (setting up the default
1541 maximum log level for emitting of records). It also provides access
1542 to a command used for testing the log system.
1545 bool "trace - Support tracing of function calls and timing"
1547 Enables a command to control using of function tracing within
1548 U-Boot. This allows recording of call traces including timing
1549 information. The command can write data to memory for exporting
1550 for analsys (e.g. using bootchart). See doc/README.trace for full
1556 tristate "Enable UBI - Unsorted block images commands"
1560 default y if NAND_SUNXI
1562 UBI is a software layer above MTD layer which admits use of LVM-like
1563 logical volumes on top of MTD devices, hides some complexities of
1564 flash chips like wear and bad blocks and provides some other useful
1565 capabilities. Please, consult the MTD web site for more details
1566 (www.linux-mtd.infradead.org). Activate this option if you want
1567 to use U-Boot UBI commands.
1570 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1574 default y if CMD_UBI
1576 UBIFS is a file system for flash devices which works on top of UBI.
projects / u-boot / blob