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"
134 Print ".config" contents.
136 If this option is enabled, the ".config" file contents are embedded
137 in the U-Boot image and can be printed on the console by the "config"
138 command. This provides information of which options are enabled on
145 Print console devices and information.
150 Print information about available CPUs. This normally shows the
151 number of CPUs, type (e.g. manufacturer, architecture, product or
152 internal name) and clock frequency. Other information may be
153 available depending on the CPU driver.
159 Print GPL license text
175 Run the command stored in the environment "bootcmd", i.e.
176 "bootd" does the same thing as "run bootcmd".
182 Boot an application image from the memory.
187 Boot the Linux zImage
194 Boot an AArch64 Linux Kernel image from memory.
198 depends on EFI_LOADER
201 Boot an EFI image from memory.
203 config CMD_BOOTEFI_HELLO_COMPILE
204 bool "Compile a standard EFI hello world binary for testing"
205 depends on CMD_BOOTEFI && (ARM || X86)
208 This compiles a standard EFI hello world application with U-Boot so
209 that it can be used with the test/py testing framework. This is useful
210 for testing that EFI is working at a basic level, and for bringing
211 up EFI support on a new architecture.
213 No additional space will be required in the resulting U-Boot binary
214 when this option is enabled.
216 config CMD_BOOTEFI_HELLO
217 bool "Allow booting a standard EFI hello world for testing"
218 depends on CMD_BOOTEFI_HELLO_COMPILE
220 This adds a standard EFI hello world application to U-Boot so that
221 it can be used with the 'bootefi hello' command. This is useful
222 for testing that EFI is working at a basic level, and for bringing
223 up EFI support on a new architecture.
225 source lib/efi_selftest/Kconfig
231 Add an ANSI terminal boot menu command.
234 bool "bootelf, bootvx"
237 Boot an ELF/vxWorks image from the memory.
240 bool "Flattened Device Tree utility commands"
244 Do FDT related setup before booting into the Operating System.
250 Start an application at a given address.
256 Run the command in the given environment variable.
262 Print header information for application image.
268 List all images found in flash
274 Extract a part of a multi-image.
279 Poweroff/Shutdown the system
282 bool "spl export - Export boot information for Falcon boot"
285 Falcon mode allows booting directly from SPL into an Operating
286 System such as Linux, thus skipping U-Boot proper. See
287 doc/README.falcon for full information about how to use this
290 config CMD_SPL_NAND_OFS
291 hex "Offset of OS command line args for Falcon-mode NAND boot"
295 This provides the offset of the command line arguments for Linux
296 when booting from NAND in Falcon mode. See doc/README.falcon
297 for full information about how to use this option (and also see
298 board/gateworks/gw_ventana/README for an example).
300 config CMD_SPL_WRITE_SIZE
301 hex "Size of argument area"
305 This provides the size of the command-line argument area in NAND
306 flash used by Falcon-mode boot. See the documentation until CMD_SPL
309 config CMD_THOR_DOWNLOAD
310 bool "thor - TIZEN 'thor' download"
312 Implements the 'thor' download protocol. This is a way of
313 downloading a software update over USB from an attached host.
314 There is no documentation about this within the U-Boot source code
315 but you should be able to find something on the interwebs.
318 bool "zboot - x86 boot command"
320 With x86 machines it is common to boot a bzImage file which
321 contains both a kernel and a setup.bin file. The latter includes
322 configuration information from the dark ages which x86 boards still
323 need to pick things out of.
325 Consider using FIT in preference to this since it supports directly
326 booting both 32- and 64-bit kernels, as well as secure boot.
327 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
331 menu "Environment commands"
334 bool "ask for env variable"
336 Ask for environment variable
354 Edit environment variable.
359 Allow for searching environment variables
365 Save all environment variables into the compiled-in persistent
368 config CMD_ENV_EXISTS
372 Check if a variable is defined in the environment for use in
375 config CMD_ENV_CALLBACK
376 bool "env callbacks - print callbacks and their associated variables"
378 Some environment variable have callbacks defined by
379 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
380 For example changing "baudrate" adjust the serial baud rate. This
381 command lists the currently defined callbacks.
384 bool "env flags -print variables that have non-default flags"
386 Some environment variables have special flags that control their
387 behaviour. For example, serial# can only be written once and cannot
388 be deleted. This command shows the variables that have special
393 menu "Memory commands"
406 Add -v option to verify data against a crc32 checksum.
409 bool "eeprom - EEPROM subsystem"
411 (deprecated, needs conversion to driver model)
412 Provides commands to read and write EEPROM (Electrically Erasable
413 Programmable Read Only Memory) chips that are connected over an
416 config CMD_EEPROM_LAYOUT
417 bool "Enable layout-aware eeprom commands"
418 depends on CMD_EEPROM
420 (deprecated, needs conversion to driver model)
421 When enabled, additional eeprom sub-commands become available.
423 eeprom print - prints the contents of the eeprom in a human-readable
424 way (eeprom layout fields, and data formatted to be fit for human
427 eeprom update - allows user to update eeprom fields by specifying
428 the field name, and providing the new data in a human readable format
429 (same format as displayed by the eeprom print command).
431 Both commands can either auto detect the layout, or be told which
435 __weak int parse_layout_version(char *str)
436 - override to provide your own layout name parsing
437 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
439 - override to setup the layout metadata based on the version
440 __weak int eeprom_layout_detect(unsigned char *data)
441 - override to provide your own algorithm for detecting layout
444 - contains various printing and updating functions for common
445 types of eeprom fields. Can be used for defining
448 config EEPROM_LAYOUT_HELP_STRING
449 string "Tells user what layout names are supported"
450 depends on CMD_EEPROM_LAYOUT
451 default "<not defined>"
453 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
459 Infinite write loop on address range
466 Compute MD5 checksum.
471 depends on CMD_MD5SUM
473 Add -v option to verify data against an MD5 checksum.
478 Display memory information.
481 bool "md, mm, nm, mw, cp, cmp, base, loop"
486 mm - memory modify (auto-incrementing address)
487 nm - memory modify (constant address)
488 mw - memory write (fill)
491 base - print or set address offset
492 loop - initialize loop on address range
497 Simple RAM read/write test.
502 mdc - memory display cyclic
503 mwc - memory write cyclic
509 Compute SHA1 checksum.
511 config SHA1SUM_VERIFY
513 depends on CMD_SHA1SUM
515 Add -v option to verify data against a SHA1 checksum.
518 bool "strings - display strings in memory"
520 This works similarly to the Unix 'strings' command except that it
521 works with a memory range. String of printable characters found
522 within the range are displayed. The minimum number of characters
523 for a sequence to be considered a string can be provided.
527 menu "Compression commands"
533 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
539 Uncompress a zip-compressed memory region.
544 Compress a memory region with zlib deflate method.
548 menu "Device access commands"
551 #depends on FLASH_CFI_DRIVER
554 ARM Ltd reference designs flash partition access
557 bool "clk - Show clock frequencies"
560 Shows clock frequences by calling a sock_clk_dump() hook function.
561 This is depreated in favour of using the CLK uclass and accessing
562 clock values from associated drivers. However currently no command
566 bool "demo - Demonstration commands for driver model"
569 Provides a 'demo' command which can be used to play around with
570 driver model. To use this properly you will need to enable one or
571 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
572 Otherwise you will always get an empty list of devices. The demo
573 devices are defined in the sandbox device tree, so the easiest
574 option is to use sandbox and pass the -d point to sandbox's
579 select USB_FUNCTION_DFU
581 Enables the command "dfu" which is used to have U-Boot create a DFU
582 class device via USB. This command requires that the "dfu_alt_info"
583 environment variable be set and define the alt settings to expose to
587 bool "dm - Access to driver model information"
591 Provides access to driver model data structures and information,
592 such as a list of devices, list of uclasses and the state of each
593 device (e.g. activated). This is not required for operation, but
594 can be useful to see the state of driver model for debugging or
598 bool "fdcboot - Boot from floppy device"
600 The 'fdtboot' command allows booting an image from a floppy disk.
603 bool "flinfo, erase, protect"
607 flinfo - print FLASH memory information
609 protect - enable or disable FLASH write protection
617 config CMD_FPGA_LOADBP
618 bool "fpga loadbp - load partial bitstream (Xilinx only)"
621 Supports loading an FPGA device from a bitstream buffer containing
624 config CMD_FPGA_LOADFS
625 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
628 Supports loading an FPGA device from a FAT filesystem.
630 config CMD_FPGA_LOADMK
631 bool "fpga loadmk - load bitstream from image"
634 Supports loading an FPGA device from a image generated by mkimage.
636 config CMD_FPGA_LOADP
637 bool "fpga loadp - load partial bitstream"
640 Supports loading an FPGA device from a bitstream buffer containing
644 bool "fpgad - dump FPGA registers"
646 (legacy, needs conversion to driver model)
647 Provides a way to dump FPGA registers by calling the board-specific
648 fpga_get_reg() function. This functions similarly to the 'md'
652 bool "fuse - support for the fuse subssystem"
654 (deprecated - needs conversion to driver model)
655 This allows reading, sensing, programming or overriding fuses
656 which control the behaviour of the device. The command uses the
665 bool "GPT (GUID Partition Table) command"
666 select PARTITION_UUIDS
669 Enable the 'gpt' command to ready and write GPT style partition
672 config CMD_GPT_RENAME
673 bool "GPT partition renaming commands"
676 Enables the 'gpt' command to interchange names on two GPT
677 partitions via the 'gpt swap' command or to rename single
678 partitions via the 'rename' command.
681 bool "ide - Support for IDE drivers"
684 Provides an 'ide' command which allows accessing the IDE drive,
685 reseting the IDE interface, printing the partition table and
686 geting device info. It also enables the 'diskboot' command which
687 permits booting from an IDE drive.
690 bool "io - Support for performing I/O accesses"
692 Provides an 'iod' command to display I/O space and an 'iow' command
693 to write values to the I/O space. This can be useful for manually
694 checking the state of devices during boot when debugging device
698 bool "iotrace - Support for tracing I/O activity"
700 Provides an 'iotrace' command which supports recording I/O reads and
701 writes in a trace buffer in memory . It also maintains a checksum
702 of the trace records (even if space is exhausted) so that the
703 sequence of I/O accesses can be verified.
705 When debugging drivers it is useful to see what I/O accesses were
706 done and in what order.
708 Even if the individual accesses are of little interest it can be
709 useful to verify that the access pattern is consistent each time
710 an operation is performed. In this case a checksum can be used to
711 characterise the operation of a driver. The checksum can be compared
712 across different runs of the operation to verify that the driver is
715 In particular, when performing major refactoring of the driver, where
716 the access pattern should not change, the checksum provides assurance
717 that the refactoring work has not broken the driver.
719 This works by sneaking into the io.h heder for an architecture and
720 redirecting I/O accesses through iotrace's tracing mechanism.
722 For now no commands are provided to examine the trace buffer. The
723 format is fairly simple, so 'md' is a reasonable substitute.
725 Note: The checksum feature is only useful for I/O regions where the
726 contents do not change outside of software control. Where this is not
727 suitable you can fall back to manually comparing the addresses. It
728 might be useful to enhance tracing to only checksum the accesses and
729 not the data read/written.
740 Load a binary file over serial line.
746 Load an S-Record file over serial line
751 MMC memory mapped support.
755 default y if NAND_SUNXI
760 config CMD_NAND_TRIMFFS
761 bool "nand write.trimffs"
762 default y if ARCH_SUNXI
764 Allows one to skip empty pages when flashing something on a NAND.
766 config CMD_NAND_LOCK_UNLOCK
767 bool "nand lock/unlock"
769 NAND locking support.
771 config CMD_NAND_TORTURE
774 NAND torture support.
783 NVM Express device support
786 bool "mmc_spi - Set up MMC SPI device"
788 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
789 Peripheral Interface) device. The device provides a means of
790 accessing an MMC device via SPI using a single data line, limited
791 to 20MHz. It is useful since it reduces the amount of protocol code
795 bool "onenand - access to onenand device"
797 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
798 various useful features. This command allows reading, writing,
799 and erasing blocks. It allso provides a way to show and change
800 bad blocks, and test the device.
804 select PARTITION_UUIDS
806 Read and display information about the partition table on
810 bool "pci - Access PCI devices"
812 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
813 used on some devices to allow the CPU to communicate with its
814 peripherals. Sub-commands allow bus enumeration, displaying and
815 changing configuration space and a few other features.
818 bool "pinit - Set up PCMCIA device"
820 Provides a means to initialise a PCMCIA (Personal Computer Memory
821 Card International Association) device. This is an old standard from
822 about 1990. These devices are typically removable memory or network
823 cards using a standard 68-pin connector.
826 bool "read - Read binary data from a partition"
828 Provides low-level access to the data in a partition.
830 config CMD_REMOTEPROC
832 depends on REMOTEPROC
834 Support for Remote Processor control
837 bool "sata - Access SATA subsystem"
840 SATA (Serial Advanced Technology Attachment) is a serial bus
841 standard for connecting to hard drives and other storage devices.
842 This command provides information about attached devices and allows
843 reading, writing and other operations.
845 SATA replaces PATA (originally just ATA), which stands for Parallel AT
846 Attachment, where AT refers to an IBM AT (Advanced Technology)
847 computer released in 1984.
850 bool "saves - Save a file over serial in S-Record format"
852 Provides a way to save a binary file using the Motorola S-Record
853 format over the serial line.
856 bool "sdram - Print SDRAM configuration information"
858 Provides information about attached SDRAM. This assumed that the
859 SDRAM has an EEPROM with information that can be read using the
860 I2C bus. This is only available on some boards.
868 bool "sf test - Allow testing of SPI flash"
870 Provides a way to test that SPI flash is working correctly. The
871 test is destructive, in that an area of SPI flash must be provided
872 for the test to use. Performance information is also provided,
873 measuring the performance of reading, writing and erasing in
874 Mbps (Million Bits Per Second). This value should approximately
875 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
876 everything is working properly.
884 bool "tsi148 - Command to access tsi148 device"
886 This provides various sub-commands to initialise and configure the
887 Turndra tsi148 device. See the command help for full details.
890 bool "universe - Command to set up the Turndra Universe controller"
892 This allows setting up the VMEbus provided by this controller.
893 See the command help for full details.
902 select USB_FUNCTION_SDP
904 Enables the command "sdp" which is used to have U-Boot emulating the
905 Serial Download Protocol (SDP) via USB.
907 config CMD_USB_MASS_STORAGE
908 bool "UMS usb mass storage"
910 USB mass storage support
915 menu "Shell scripting commands"
927 Return true/false on integer compare.
933 Run script from memory
939 Evaluate boolean and math expressions and store the result in an env
941 Also supports loading the value at a memory location into a variable.
942 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
946 menu "Network commands"
949 bool "bootp, tftpboot"
954 bootp - boot image via network using BOOTP/TFTP protocol
955 tftpboot - boot image via network using TFTP protocol
960 TFTP put command, for uploading files to a server
965 Act as a TFTP server and boot the first received file
970 Boot image via network using RARP/TFTP protocol
975 Boot image via network using DHCP/TFTP protocol
981 Boot image via network using PXE protocol
987 Boot image via network using NFS protocol.
992 Enable MII utility commands.
997 Send ICMP ECHO_REQUEST to network host
1002 Perform CDP network configuration
1007 Synchronize RTC via network
1012 Lookup the IP of a hostname
1014 config CMD_LINK_LOCAL
1017 Acquire a network IP address using the link-local protocol
1022 Allow control of L2 Ethernet switch commands. These are supported
1023 by the vsc9953 Ethernet driver at present. Sub-commands allow
1024 operations such as enabling / disabling a port and
1025 viewing/maintaining the filtering database (FDB)
1029 menu "Misc commands"
1032 bool "Enable 'bmp' command"
1033 depends on LCD || DM_VIDEO || VIDEO
1035 This provides a way to obtain information about a BMP-format iamge
1036 and to display it. BMP (which presumably stands for BitMaP) is a
1037 file format defined by Microsoft which supports images of various
1038 depths, formats and compression methods. Headers on the file
1039 determine the formats used. This command can be used by first loading
1040 the image into RAM, then using this command to look at it or display
1044 bool "Enable board-specific commands"
1046 (deprecated: instead, please define a Kconfig option for each command)
1048 Some boards have board-specific commands which are only enabled
1049 during developemnt and need to be turned off for production. This
1050 option provides a way to control this. The commands that are enabled
1051 vary depending on the board.
1053 config CMD_BKOPS_ENABLE
1054 bool "mmc bkops enable"
1058 Enable command for setting manual background operations handshake
1059 on a eMMC device. The feature is optionally available on eMMC devices
1060 conforming to standard >= 4.41.
1062 config CMD_BLOCK_CACHE
1063 bool "blkcache - control and stats for block cache"
1064 depends on BLOCK_CACHE
1065 default y if BLOCK_CACHE
1067 Enable the blkcache command, which can be used to control the
1068 operation of the cache functions.
1069 This is most useful when fine-tuning the operation of the cache
1070 during development, but also allows the cache to be disabled when
1071 it might hurt performance (e.g. when using the ums command).
1074 bool "icache or dcache"
1076 Enable the "icache" and "dcache" commands
1079 bool "Enable the 'display' command, for character displays"
1081 (this needs porting to driver model)
1082 This enables the 'display' command which allows a string to be
1083 displayed on a simple board-specific display. Implement
1084 display_putc() to use it.
1090 Enable the 'led' command which allows for control of LEDs supported
1091 by the board. The LEDs can be listed with 'led list' and controlled
1092 with led on/off/togle/blink. Any LED drivers can be controlled with
1093 this command, e.g. led_gpio.
1099 Enable the 'date' command for getting/setting the time/date in RTC
1105 Run commands and summarize execution time.
1108 bool "gettime - read elapsed time"
1110 Enable the 'gettime' command which reads the elapsed time since
1111 U-Boot started running. This shows the time in seconds and
1112 milliseconds. See also the 'bootstage' command which provides more
1113 flexibility for boot timing.
1115 # TODO: rename to CMD_SLEEP
1120 Delay execution for some time
1125 Access the system timer.
1131 This provides basic access to the U-Boot's sound support. The main
1132 feature is to play a beep.
1134 sound init - set up sound system
1135 sound play - play a sound
1141 This provides access to the QEMU firmware interface. The main
1142 feature is to allow easy loading of files passed to qemu-system
1143 via -kernel / -initrd
1145 source "cmd/mvebu/Kconfig"
1148 bool "terminal - provides a way to attach a serial terminal"
1150 Provides a 'cu'-like serial terminal command. This can be used to
1151 access other serial ports from the system console. The terminal
1152 is very simple with no special processing of characters. As with
1153 cu, you can press ~. (tilde followed by period) to exit.
1156 bool "uuid, guid - generation of unique IDs"
1158 This enables two commands:
1160 uuid - generate random Universally Unique Identifier
1161 guid - generate Globally Unique Identifier based on random UUID
1163 The two commands are very similar except for the endianness of the
1168 config CMD_BOOTSTAGE
1169 bool "Enable the 'bootstage' command"
1170 depends on BOOTSTAGE
1172 Add a 'bootstage' command which supports printing a report
1173 and un/stashing of bootstage data.
1175 menu "Power commands"
1177 bool "Enable Driver Model PMIC command"
1180 This is the pmic command, based on a driver model pmic's API.
1181 Command features are unchanged:
1182 - list - list pmic devices
1183 - pmic dev <id> - show or [set] operating pmic device (NEW)
1184 - pmic dump - dump registers
1185 - pmic read address - read byte of register at address
1186 - pmic write address - write byte to register at address
1187 The only one change for this command is 'dev' subcommand.
1189 config CMD_REGULATOR
1190 bool "Enable Driver Model REGULATOR command"
1191 depends on DM_REGULATOR
1193 This command is based on driver model regulator's API.
1194 User interface features:
1195 - list - list regulator devices
1196 - regulator dev <id> - show or [set] operating regulator device
1197 - regulator info - print constraints info
1198 - regulator status - print operating status
1199 - regulator value <val] <-f> - print/[set] voltage value [uV]
1200 - regulator current <val> - print/[set] current value [uA]
1201 - regulator mode <id> - print/[set] operating mode id
1202 - regulator enable - enable the regulator output
1203 - regulator disable - disable the regulator output
1205 The '-f' (force) option can be used for set the value which exceeds
1206 the limits, which are found in device-tree and are kept in regulator's
1207 uclass platdata structure.
1211 menu "Security commands"
1213 bool "Enable the 'aes' command"
1216 This provides a means to encrypt and decrypt data using the AES
1217 (Advanced Encryption Standard). This algorithm uses a symetric key
1218 and is widely used as a streaming cipher. Different key lengths are
1219 supported by the algorithm but this command only supports 128 bits
1223 bool "Enable the 'blob' command"
1225 This is used with the Freescale secure boot mechanism.
1227 Freescale's SEC block has built-in Blob Protocol which provides
1228 a method for protecting user-defined data across system power
1229 cycles. SEC block protects data in a data structure called a Blob,
1230 which provides both confidentiality and integrity protection.
1232 Encapsulating data as a blob
1233 Each time that the Blob Protocol is used to protect data, a
1234 different randomly generated key is used to encrypt the data.
1235 This random key is itself encrypted using a key which is derived
1236 from SoC's non-volatile secret key and a 16 bit Key identifier.
1237 The resulting encrypted key along with encrypted data is called a
1238 blob. The non-volatile secure key is available for use only during
1241 During decapsulation, the reverse process is performed to get back
1245 blob enc - encapsulating data as a cryptgraphic blob
1246 blob dec - decapsulating cryptgraphic blob to get the data
1250 blob enc src dst len km
1252 Encapsulate and create blob of data $len bytes long
1253 at address $src and store the result at address $dst.
1254 $km is the 16 byte key modifier is also required for
1255 generation/use as key for cryptographic operation. Key
1256 modifier should be 16 byte long.
1258 blob dec src dst len km
1260 Decapsulate the blob of data at address $src and
1261 store result of $len byte at addr $dst.
1262 $km is the 16 byte key modifier is also required for
1263 generation/use as key for cryptographic operation. Key
1264 modifier should be 16 byte long.
1267 bool "Support 'hash' command"
1270 This provides a way to hash data in memory using various supported
1271 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1272 saved to memory or to an environment variable. It is also possible
1273 to verify a hash against data in memory.
1279 Add -v option to verify data against a hash.
1282 bool "Enable the 'tpm' command"
1285 This provides a means to talk to a TPM from the command line. A wide
1286 range of commands if provided - see 'tpm help' for details. The
1287 command requires a suitable TPM on your board and the correct driver
1291 bool "Enable the 'tpm test' command"
1294 This provides a a series of tests to confirm that the TPM is working
1295 correctly. The tests cover initialisation, non-volatile RAM, extend,
1296 global lock and checking that timing is within expectations. The
1297 tests pass correctly on Infineon TPMs but may need to be adjusted
1302 menu "Firmware commands"
1304 bool "Enable crosec command"
1308 Enable command-line access to the Chrome OS EC (Embedded
1309 Controller). This provides the 'crosec' command which has
1310 a number of sub-commands for performing EC tasks such as
1311 updating its flash, accessing a small saved context area
1312 and talking to the I2C bus behind the EC (if there is one).
1315 menu "Filesystem commands"
1317 bool "Enable the 'cbfs' command"
1320 Define this to enable support for reading from a Coreboot
1321 filesystem. This is a ROM-based filesystem used for accessing files
1322 on systems that use coreboot as the first boot-loader and then load
1323 U-Boot to actually boot the Operating System. Available commands are
1324 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1327 bool "Enable the 'cramfs' command"
1328 depends on FS_CRAMFS
1330 This provides commands for dealing with CRAMFS (Compressed ROM
1331 filesystem). CRAMFS is useful when space is tight since files are
1332 compressed. Two commands are provided:
1334 cramfsls - lists files in a cramfs image
1335 cramfsload - loads a file from a cramfs image
1338 bool "ext2 command support"
1340 Enables EXT2 FS command
1343 bool "ext4 command support"
1345 Enables EXT4 FS command
1347 config CMD_EXT4_WRITE
1349 bool "ext4 write command support"
1351 Enables EXT4 FS write command
1354 bool "FAT command support"
1357 Support for the FAT fs
1359 config CMD_FS_GENERIC
1360 bool "filesystem commands"
1362 Enables filesystem commands (e.g. load, ls) that work for multiple
1366 bool "fsuuid command"
1368 Enables fsuuid command for filesystem UUID.
1371 bool "jffs2 command"
1374 Enables commands to support the JFFS2 (Journalling Flash File System
1375 version 2) filesystem. This enables fsload, ls and fsinfo which
1376 provide the ability to load files, list directories and obtain
1377 filesystem information.
1380 bool "MTD partition support"
1382 MTD partition support
1384 config MTDIDS_DEFAULT
1385 string "Default MTD IDs"
1386 depends on CMD_MTDPARTS
1388 Defines a default MTD ID
1390 config MTDPARTS_DEFAULT
1391 string "Default MTD partition scheme"
1392 depends on CMD_MTDPARTS
1394 Defines a default MTD partitioning scheme in the Linux MTD command
1395 line partitions format
1397 config CMD_MTDPARTS_SPREAD
1398 bool "Padd partition size to take account of bad blocks"
1399 depends on CMD_MTDPARTS
1401 This enables the 'spread' sub-command of the mtdparts command.
1402 This command will modify the existing mtdparts variable by increasing
1403 the size of the partitions such that 1) each partition's net size is
1404 at least as large as the size specified in the mtdparts variable and
1405 2) each partition starts on a good block.
1408 bool "reiser - Access to reiserfs filesystems"
1410 This provides two commands which operate on a resierfs filesystem,
1411 commonly used some years ago:
1413 reiserls - list files
1414 reiserload - load a file
1417 bool "scsi - Access to SCSI devices"
1420 This provides a 'scsi' command which provides access to SCSI (Small
1421 Computer System Interface) devices. The command provides a way to
1422 scan the bus, reset the bus, read and write data and get information
1426 bool "yaffs2 - Access of YAFFS2 filesystem"
1430 This provides commands for accessing a YAFFS2 filesystem. Yet
1431 Another Flash Filesystem 2 is a filesystem designed specifically
1432 for NAND flash. It incorporates bad-block management and ensures
1433 that device writes are sequential regardless of filesystem
1437 bool "zfs - Access of ZFS filesystem"
1439 This provides commands to accessing a ZFS filesystem, commonly used
1440 on Solaris systems. Two sub-commands are provided:
1442 zfsls - list files in a directory
1443 zfsload - load a file
1445 See doc/README.zfs for more details.
1449 menu "Debug commands"
1454 The bedbug (emBEDded deBUGger) command provides debugging features
1455 for some PowerPC processors. For details please see the
1456 docuemntation in doc/README.beddbug
1459 bool "diag - Board diagnostics"
1461 This command provides access to board diagnostic tests. These are
1462 called Power-on Self Tests (POST). The command allows listing of
1463 available tests and running either all the tests, or specific tests
1467 bool "irq - Show information about interrupts"
1468 depends on !ARM && !MIPS && !SH
1470 This enables two commands:
1472 interrupts - enable or disable interrupts
1473 irqinfo - print device-specific interrupt information
1476 bool "kgdb - Allow debugging of U-Boot with gdb"
1478 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1479 over a serial link for debugging purposes. This allows
1480 single-stepping, inspecting variables, etc. This is supported only
1481 on PowerPC at present.
1484 bool "trace - Support tracing of function calls and timing"
1486 Enables a command to control using of function tracing within
1487 U-Boot. This allows recording of call traces including timing
1488 information. The command can write data to memory for exporting
1489 for analsys (e.g. using bootchart). See doc/README.trace for full
1495 tristate "Enable UBI - Unsorted block images commands"
1499 default y if NAND_SUNXI
1501 UBI is a software layer above MTD layer which admits use of LVM-like
1502 logical volumes on top of MTD devices, hides some complexities of
1503 flash chips like wear and bad blocks and provides some other useful
1504 capabilities. Please, consult the MTD web site for more details
1505 (www.linux-mtd.infradead.org). Activate this option if you want
1506 to use U-Boot UBI commands.
1509 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1513 default y if CMD_UBI
1515 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob