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.
229 Add an ANSI terminal boot menu command.
232 bool "bootelf, bootvx"
235 Boot an ELF/vxWorks image from the memory.
238 bool "Flattened Device Tree utility commands"
242 Do FDT related setup before booting into the Operating System.
248 Start an application at a given address.
254 Run the command in the given environment variable.
260 Print header information for application image.
266 List all images found in flash
272 Extract a part of a multi-image.
277 Poweroff/Shutdown the system
280 bool "spl export - Export boot information for Falcon boot"
283 Falcon mode allows booting directly from SPL into an Operating
284 System such as Linux, thus skipping U-Boot proper. See
285 doc/README.falcon for full information about how to use this
288 config CMD_SPL_NAND_OFS
289 hex "Offset of OS command line args for Falcon-mode NAND boot"
293 This provides the offset of the command line arguments for Linux
294 when booting from NAND in Falcon mode. See doc/README.falcon
295 for full information about how to use this option (and also see
296 board/gateworks/gw_ventana/README for an example).
298 config CMD_SPL_WRITE_SIZE
299 hex "Size of argument area"
303 This provides the size of the command-line argument area in NAND
304 flash used by Falcon-mode boot. See the documentation until CMD_SPL
307 config CMD_THOR_DOWNLOAD
308 bool "thor - TIZEN 'thor' download"
310 Implements the 'thor' download protocol. This is a way of
311 downloading a software update over USB from an attached host.
312 There is no documentation about this within the U-Boot source code
313 but you should be able to find something on the interwebs.
316 bool "zboot - x86 boot command"
318 With x86 machines it is common to boot a bzImage file which
319 contains both a kernel and a setup.bin file. The latter includes
320 configuration information from the dark ages which x86 boards still
321 need to pick things out of.
323 Consider using FIT in preference to this since it supports directly
324 booting both 32- and 64-bit kernels, as well as secure boot.
325 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
329 menu "Environment commands"
332 bool "ask for env variable"
334 Ask for environment variable
352 Edit environment variable.
357 Allow for searching environment variables
363 Save all environment variables into the compiled-in persistent
366 config CMD_ENV_EXISTS
370 Check if a variable is defined in the environment for use in
373 config CMD_ENV_CALLBACK
374 bool "env callbacks - print callbacks and their associated variables"
376 Some environment variable have callbacks defined by
377 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
378 For example changing "baudrate" adjust the serial baud rate. This
379 command lists the currently defined callbacks.
382 bool "env flags -print variables that have non-default flags"
384 Some environment variables have special flags that control their
385 behaviour. For example, serial# can only be written once and cannot
386 be deleted. This command shows the variables that have special
391 menu "Memory commands"
404 Add -v option to verify data against a crc32 checksum.
407 bool "eeprom - EEPROM subsystem"
409 (deprecated, needs conversion to driver model)
410 Provides commands to read and write EEPROM (Electrically Erasable
411 Programmable Read Only Memory) chips that are connected over an
414 config CMD_EEPROM_LAYOUT
415 bool "Enable layout-aware eeprom commands"
416 depends on CMD_EEPROM
418 (deprecated, needs conversion to driver model)
419 When enabled, additional eeprom sub-commands become available.
421 eeprom print - prints the contents of the eeprom in a human-readable
422 way (eeprom layout fields, and data formatted to be fit for human
425 eeprom update - allows user to update eeprom fields by specifying
426 the field name, and providing the new data in a human readable format
427 (same format as displayed by the eeprom print command).
429 Both commands can either auto detect the layout, or be told which
433 __weak int parse_layout_version(char *str)
434 - override to provide your own layout name parsing
435 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
437 - override to setup the layout metadata based on the version
438 __weak int eeprom_layout_detect(unsigned char *data)
439 - override to provide your own algorithm for detecting layout
442 - contains various printing and updating functions for common
443 types of eeprom fields. Can be used for defining
446 config EEPROM_LAYOUT_HELP_STRING
447 string "Tells user what layout names are supported"
448 depends on CMD_EEPROM_LAYOUT
449 default "<not defined>"
451 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
457 Infinite write loop on address range
464 Compute MD5 checksum.
469 depends on CMD_MD5SUM
471 Add -v option to verify data against an MD5 checksum.
476 Display memory information.
479 bool "md, mm, nm, mw, cp, cmp, base, loop"
484 mm - memory modify (auto-incrementing address)
485 nm - memory modify (constant address)
486 mw - memory write (fill)
489 base - print or set address offset
490 loop - initialize loop on address range
495 Simple RAM read/write test.
500 mdc - memory display cyclic
501 mwc - memory write cyclic
507 Compute SHA1 checksum.
509 config SHA1SUM_VERIFY
511 depends on CMD_SHA1SUM
513 Add -v option to verify data against a SHA1 checksum.
516 bool "strings - display strings in memory"
518 This works similarly to the Unix 'strings' command except that it
519 works with a memory range. String of printable characters found
520 within the range are displayed. The minimum number of characters
521 for a sequence to be considered a string can be provided.
525 menu "Compression commands"
531 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
537 Uncompress a zip-compressed memory region.
542 Compress a memory region with zlib deflate method.
546 menu "Device access commands"
549 #depends on FLASH_CFI_DRIVER
552 ARM Ltd reference designs flash partition access
555 bool "clk - Show clock frequencies"
558 Shows clock frequences by calling a sock_clk_dump() hook function.
559 This is depreated in favour of using the CLK uclass and accessing
560 clock values from associated drivers. However currently no command
564 bool "demo - Demonstration commands for driver model"
567 Provides a 'demo' command which can be used to play around with
568 driver model. To use this properly you will need to enable one or
569 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
570 Otherwise you will always get an empty list of devices. The demo
571 devices are defined in the sandbox device tree, so the easiest
572 option is to use sandbox and pass the -d point to sandbox's
577 select USB_FUNCTION_DFU
579 Enables the command "dfu" which is used to have U-Boot create a DFU
580 class device via USB. This command requires that the "dfu_alt_info"
581 environment variable be set and define the alt settings to expose to
585 bool "dm - Access to driver model information"
589 Provides access to driver model data structures and information,
590 such as a list of devices, list of uclasses and the state of each
591 device (e.g. activated). This is not required for operation, but
592 can be useful to see the state of driver model for debugging or
596 bool "fdcboot - Boot from floppy device"
598 The 'fdtboot' command allows booting an image from a floppy disk.
601 bool "flinfo, erase, protect"
605 flinfo - print FLASH memory information
607 protect - enable or disable FLASH write protection
615 config CMD_FPGA_LOADBP
616 bool "fpga loadbp - load partial bitstream (Xilinx only)"
619 Supports loading an FPGA device from a bitstream buffer containing
622 config CMD_FPGA_LOADFS
623 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
626 Supports loading an FPGA device from a FAT filesystem.
628 config CMD_FPGA_LOADMK
629 bool "fpga loadmk - load bitstream from image"
632 Supports loading an FPGA device from a image generated by mkimage.
634 config CMD_FPGA_LOADP
635 bool "fpga loadp - load partial bitstream"
638 Supports loading an FPGA device from a bitstream buffer containing
642 bool "fpgad - dump FPGA registers"
644 (legacy, needs conversion to driver model)
645 Provides a way to dump FPGA registers by calling the board-specific
646 fpga_get_reg() function. This functions similarly to the 'md'
650 bool "fuse - support for the fuse subssystem"
652 (deprecated - needs conversion to driver model)
653 This allows reading, sensing, programming or overriding fuses
654 which control the behaviour of the device. The command uses the
663 bool "GPT (GUID Partition Table) command"
664 select PARTITION_UUIDS
667 Enable the 'gpt' command to ready and write GPT style partition
670 config CMD_GPT_RENAME
671 bool "GPT partition renaming commands"
674 Enables the 'gpt' command to interchange names on two GPT
675 partitions via the 'gpt swap' command or to rename single
676 partitions via the 'rename' command.
679 bool "ide - Support for IDE drivers"
682 Provides an 'ide' command which allows accessing the IDE drive,
683 reseting the IDE interface, printing the partition table and
684 geting device info. It also enables the 'diskboot' command which
685 permits booting from an IDE drive.
688 bool "io - Support for performing I/O accesses"
690 Provides an 'iod' command to display I/O space and an 'iow' command
691 to write values to the I/O space. This can be useful for manually
692 checking the state of devices during boot when debugging device
696 bool "iotrace - Support for tracing I/O activity"
698 Provides an 'iotrace' command which supports recording I/O reads and
699 writes in a trace buffer in memory . It also maintains a checksum
700 of the trace records (even if space is exhausted) so that the
701 sequence of I/O accesses can be verified.
703 When debugging drivers it is useful to see what I/O accesses were
704 done and in what order.
706 Even if the individual accesses are of little interest it can be
707 useful to verify that the access pattern is consistent each time
708 an operation is performed. In this case a checksum can be used to
709 characterise the operation of a driver. The checksum can be compared
710 across different runs of the operation to verify that the driver is
713 In particular, when performing major refactoring of the driver, where
714 the access pattern should not change, the checksum provides assurance
715 that the refactoring work has not broken the driver.
717 This works by sneaking into the io.h heder for an architecture and
718 redirecting I/O accesses through iotrace's tracing mechanism.
720 For now no commands are provided to examine the trace buffer. The
721 format is fairly simple, so 'md' is a reasonable substitute.
723 Note: The checksum feature is only useful for I/O regions where the
724 contents do not change outside of software control. Where this is not
725 suitable you can fall back to manually comparing the addresses. It
726 might be useful to enhance tracing to only checksum the accesses and
727 not the data read/written.
738 Load a binary file over serial line.
744 Load an S-Record file over serial line
749 MMC memory mapped support.
753 default y if NAND_SUNXI
758 config CMD_NAND_TRIMFFS
759 bool "nand write.trimffs"
760 default y if ARCH_SUNXI
762 Allows one to skip empty pages when flashing something on a NAND.
764 config CMD_NAND_LOCK_UNLOCK
765 bool "nand lock/unlock"
767 NAND locking support.
769 config CMD_NAND_TORTURE
772 NAND torture support.
777 bool "mmc_spi - Set up MMC SPI device"
779 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
780 Peripheral Interface) device. The device provides a means of
781 accessing an MMC device via SPI using a single data line, limited
782 to 20MHz. It is useful since it reduces the amount of protocol code
786 bool "onenand - access to onenand device"
788 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
789 various useful features. This command allows reading, writing,
790 and erasing blocks. It allso provides a way to show and change
791 bad blocks, and test the device.
795 select PARTITION_UUIDS
797 Read and display information about the partition table on
801 bool "pci - Access PCI devices"
803 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
804 used on some devices to allow the CPU to communicate with its
805 peripherals. Sub-commands allow bus enumeration, displaying and
806 changing configuration space and a few other features.
809 bool "pinit - Set up PCMCIA device"
811 Provides a means to initialise a PCMCIA (Personal Computer Memory
812 Card International Association) device. This is an old standard from
813 about 1990. These devices are typically removable memory or network
814 cards using a standard 68-pin connector.
817 bool "read - Read binary data from a partition"
819 Provides low-level access to the data in a partition.
821 config CMD_REMOTEPROC
823 depends on REMOTEPROC
825 Support for Remote Processor control
828 bool "sata - Access SATA subsystem"
831 SATA (Serial Advanced Technology Attachment) is a serial bus
832 standard for connecting to hard drives and other storage devices.
833 This command provides information about attached devices and allows
834 reading, writing and other operations.
836 SATA replaces PATA (originally just ATA), which stands for Parallel AT
837 Attachment, where AT refers to an IBM AT (Advanced Technology)
838 computer released in 1984.
841 bool "saves - Save a file over serial in S-Record format"
843 Provides a way to save a binary file using the Motorola S-Record
844 format over the serial line.
847 bool "sdram - Print SDRAM configuration information"
849 Provides information about attached SDRAM. This assumed that the
850 SDRAM has an EEPROM with information that can be read using the
851 I2C bus. This is only available on some boards.
859 bool "sf test - Allow testing of SPI flash"
861 Provides a way to test that SPI flash is working correctly. The
862 test is destructive, in that an area of SPI flash must be provided
863 for the test to use. Performance information is also provided,
864 measuring the performance of reading, writing and erasing in
865 Mbps (Million Bits Per Second). This value should approximately
866 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
867 everything is working properly.
875 bool "tsi148 - Command to access tsi148 device"
877 This provides various sub-commands to initialise and configure the
878 Turndra tsi148 device. See the command help for full details.
881 bool "universe - Command to set up the Turndra Universe controller"
883 This allows setting up the VMEbus provided by this controller.
884 See the command help for full details.
891 config CMD_USB_MASS_STORAGE
892 bool "UMS usb mass storage"
894 USB mass storage support
899 menu "Shell scripting commands"
911 Return true/false on integer compare.
917 Run script from memory
923 Evaluate boolean and math expressions and store the result in an env
925 Also supports loading the value at a memory location into a variable.
926 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
930 menu "Network commands"
933 bool "bootp, tftpboot"
938 bootp - boot image via network using BOOTP/TFTP protocol
939 tftpboot - boot image via network using TFTP protocol
944 TFTP put command, for uploading files to a server
949 Act as a TFTP server and boot the first received file
954 Boot image via network using RARP/TFTP protocol
959 Boot image via network using DHCP/TFTP protocol
965 Boot image via network using PXE protocol
971 Boot image via network using NFS protocol.
976 Enable MII utility commands.
981 Send ICMP ECHO_REQUEST to network host
986 Perform CDP network configuration
991 Synchronize RTC via network
996 Lookup the IP of a hostname
998 config CMD_LINK_LOCAL
1001 Acquire a network IP address using the link-local protocol
1006 Allow control of L2 Ethernet switch commands. These are supported
1007 by the vsc9953 Ethernet driver at present. Sub-commands allow
1008 operations such as enabling / disabling a port and
1009 viewing/maintaining the filtering database (FDB)
1013 menu "Misc commands"
1016 bool "Enable 'bmp' command"
1017 depends on LCD || DM_VIDEO || VIDEO
1019 This provides a way to obtain information about a BMP-format iamge
1020 and to display it. BMP (which presumably stands for BitMaP) is a
1021 file format defined by Microsoft which supports images of various
1022 depths, formats and compression methods. Headers on the file
1023 determine the formats used. This command can be used by first loading
1024 the image into RAM, then using this command to look at it or display
1028 bool "Enable board-specific commands"
1030 (deprecated: instead, please define a Kconfig option for each command)
1032 Some boards have board-specific commands which are only enabled
1033 during developemnt and need to be turned off for production. This
1034 option provides a way to control this. The commands that are enabled
1035 vary depending on the board.
1037 config CMD_BKOPS_ENABLE
1038 bool "mmc bkops enable"
1042 Enable command for setting manual background operations handshake
1043 on a eMMC device. The feature is optionally available on eMMC devices
1044 conforming to standard >= 4.41.
1046 config CMD_BLOCK_CACHE
1047 bool "blkcache - control and stats for block cache"
1048 depends on BLOCK_CACHE
1049 default y if BLOCK_CACHE
1051 Enable the blkcache command, which can be used to control the
1052 operation of the cache functions.
1053 This is most useful when fine-tuning the operation of the cache
1054 during development, but also allows the cache to be disabled when
1055 it might hurt performance (e.g. when using the ums command).
1058 bool "icache or dcache"
1060 Enable the "icache" and "dcache" commands
1063 bool "Enable the 'display' command, for character displays"
1065 (this needs porting to driver model)
1066 This enables the 'display' command which allows a string to be
1067 displayed on a simple board-specific display. Implement
1068 display_putc() to use it.
1074 Enable the 'led' command which allows for control of LEDs supported
1075 by the board. The LEDs can be listed with 'led list' and controlled
1076 with led on/off/togle/blink. Any LED drivers can be controlled with
1077 this command, e.g. led_gpio.
1083 Enable the 'date' command for getting/setting the time/date in RTC
1089 Run commands and summarize execution time.
1092 bool "gettime - read elapsed time"
1094 Enable the 'gettime' command which reads the elapsed time since
1095 U-Boot started running. This shows the time in seconds and
1096 milliseconds. See also the 'bootstage' command which provides more
1097 flexibility for boot timing.
1099 # TODO: rename to CMD_SLEEP
1104 Delay execution for some time
1109 Access the system timer.
1115 This provides basic access to the U-Boot's sound support. The main
1116 feature is to play a beep.
1118 sound init - set up sound system
1119 sound play - play a sound
1125 This provides access to the QEMU firmware interface. The main
1126 feature is to allow easy loading of files passed to qemu-system
1127 via -kernel / -initrd
1129 source "cmd/mvebu/Kconfig"
1132 bool "terminal - provides a way to attach a serial terminal"
1134 Provides a 'cu'-like serial terminal command. This can be used to
1135 access other serial ports from the system console. The terminal
1136 is very simple with no special processing of characters. As with
1137 cu, you can press ~. (tilde followed by period) to exit.
1140 bool "uuid, guid - generation of unique IDs"
1142 This enables two commands:
1144 uuid - generate random Universally Unique Identifier
1145 guid - generate Globally Unique Identifier based on random UUID
1147 The two commands are very similar except for the endianness of the
1152 config CMD_BOOTSTAGE
1153 bool "Enable the 'bootstage' command"
1154 depends on BOOTSTAGE
1156 Add a 'bootstage' command which supports printing a report
1157 and un/stashing of bootstage data.
1159 menu "Power commands"
1161 bool "Enable Driver Model PMIC command"
1164 This is the pmic command, based on a driver model pmic's API.
1165 Command features are unchanged:
1166 - list - list pmic devices
1167 - pmic dev <id> - show or [set] operating pmic device (NEW)
1168 - pmic dump - dump registers
1169 - pmic read address - read byte of register at address
1170 - pmic write address - write byte to register at address
1171 The only one change for this command is 'dev' subcommand.
1173 config CMD_REGULATOR
1174 bool "Enable Driver Model REGULATOR command"
1175 depends on DM_REGULATOR
1177 This command is based on driver model regulator's API.
1178 User interface features:
1179 - list - list regulator devices
1180 - regulator dev <id> - show or [set] operating regulator device
1181 - regulator info - print constraints info
1182 - regulator status - print operating status
1183 - regulator value <val] <-f> - print/[set] voltage value [uV]
1184 - regulator current <val> - print/[set] current value [uA]
1185 - regulator mode <id> - print/[set] operating mode id
1186 - regulator enable - enable the regulator output
1187 - regulator disable - disable the regulator output
1189 The '-f' (force) option can be used for set the value which exceeds
1190 the limits, which are found in device-tree and are kept in regulator's
1191 uclass platdata structure.
1195 menu "Security commands"
1197 bool "Enable the 'aes' command"
1200 This provides a means to encrypt and decrypt data using the AES
1201 (Advanced Encryption Standard). This algorithm uses a symetric key
1202 and is widely used as a streaming cipher. Different key lengths are
1203 supported by the algorithm but this command only supports 128 bits
1207 bool "Enable the 'blob' command"
1209 This is used with the Freescale secure boot mechanism.
1211 Freescale's SEC block has built-in Blob Protocol which provides
1212 a method for protecting user-defined data across system power
1213 cycles. SEC block protects data in a data structure called a Blob,
1214 which provides both confidentiality and integrity protection.
1216 Encapsulating data as a blob
1217 Each time that the Blob Protocol is used to protect data, a
1218 different randomly generated key is used to encrypt the data.
1219 This random key is itself encrypted using a key which is derived
1220 from SoC's non-volatile secret key and a 16 bit Key identifier.
1221 The resulting encrypted key along with encrypted data is called a
1222 blob. The non-volatile secure key is available for use only during
1225 During decapsulation, the reverse process is performed to get back
1229 blob enc - encapsulating data as a cryptgraphic blob
1230 blob dec - decapsulating cryptgraphic blob to get the data
1234 blob enc src dst len km
1236 Encapsulate and create blob of data $len bytes long
1237 at address $src and store the result at address $dst.
1238 $km is the 16 byte key modifier is also required for
1239 generation/use as key for cryptographic operation. Key
1240 modifier should be 16 byte long.
1242 blob dec src dst len km
1244 Decapsulate the blob of data at address $src and
1245 store result of $len byte at addr $dst.
1246 $km is the 16 byte key modifier is also required for
1247 generation/use as key for cryptographic operation. Key
1248 modifier should be 16 byte long.
1251 bool "Support 'hash' command"
1254 This provides a way to hash data in memory using various supported
1255 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1256 saved to memory or to an environment variable. It is also possible
1257 to verify a hash against data in memory.
1263 Add -v option to verify data against a hash.
1266 bool "Enable the 'tpm' command"
1269 This provides a means to talk to a TPM from the command line. A wide
1270 range of commands if provided - see 'tpm help' for details. The
1271 command requires a suitable TPM on your board and the correct driver
1275 bool "Enable the 'tpm test' command"
1278 This provides a a series of tests to confirm that the TPM is working
1279 correctly. The tests cover initialisation, non-volatile RAM, extend,
1280 global lock and checking that timing is within expectations. The
1281 tests pass correctly on Infineon TPMs but may need to be adjusted
1286 menu "Firmware commands"
1288 bool "Enable crosec command"
1292 Enable command-line access to the Chrome OS EC (Embedded
1293 Controller). This provides the 'crosec' command which has
1294 a number of sub-commands for performing EC tasks such as
1295 updating its flash, accessing a small saved context area
1296 and talking to the I2C bus behind the EC (if there is one).
1299 menu "Filesystem commands"
1301 bool "Enable the 'cbfs' command"
1304 Define this to enable support for reading from a Coreboot
1305 filesystem. This is a ROM-based filesystem used for accessing files
1306 on systems that use coreboot as the first boot-loader and then load
1307 U-Boot to actually boot the Operating System. Available commands are
1308 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1311 bool "Enable the 'cramfs' command"
1312 depends on FS_CRAMFS
1314 This provides commands for dealing with CRAMFS (Compressed ROM
1315 filesystem). CRAMFS is useful when space is tight since files are
1316 compressed. Two commands are provided:
1318 cramfsls - lists files in a cramfs image
1319 cramfsload - loads a file from a cramfs image
1322 bool "ext2 command support"
1324 Enables EXT2 FS command
1327 bool "ext4 command support"
1329 Enables EXT4 FS command
1331 config CMD_EXT4_WRITE
1333 bool "ext4 write command support"
1335 Enables EXT4 FS write command
1338 bool "FAT command support"
1341 Support for the FAT fs
1343 config CMD_FS_GENERIC
1344 bool "filesystem commands"
1346 Enables filesystem commands (e.g. load, ls) that work for multiple
1350 bool "fsuuid command"
1352 Enables fsuuid command for filesystem UUID.
1355 bool "jffs2 command"
1358 Enables commands to support the JFFS2 (Journalling Flash File System
1359 version 2) filesystem. This enables fsload, ls and fsinfo which
1360 provide the ability to load files, list directories and obtain
1361 filesystem information.
1364 bool "MTD partition support"
1366 MTD partition support
1368 config MTDIDS_DEFAULT
1369 string "Default MTD IDs"
1370 depends on CMD_MTDPARTS
1372 Defines a default MTD ID
1374 config MTDPARTS_DEFAULT
1375 string "Default MTD partition scheme"
1376 depends on CMD_MTDPARTS
1378 Defines a default MTD partitioning scheme in the Linux MTD command
1379 line partitions format
1381 config CMD_MTDPARTS_SPREAD
1382 bool "Padd partition size to take account of bad blocks"
1383 depends on CMD_MTDPARTS
1385 This enables the 'spread' sub-command of the mtdparts command.
1386 This command will modify the existing mtdparts variable by increasing
1387 the size of the partitions such that 1) each partition's net size is
1388 at least as large as the size specified in the mtdparts variable and
1389 2) each partition starts on a good block.
1392 bool "reiser - Access to reiserfs filesystems"
1394 This provides two commands which operate on a resierfs filesystem,
1395 commonly used some years ago:
1397 reiserls - list files
1398 reiserload - load a file
1401 bool "scsi - Access to SCSI devices"
1404 This provides a 'scsi' command which provides access to SCSI (Small
1405 Computer System Interface) devices. The command provides a way to
1406 scan the bus, reset the bus, read and write data and get information
1410 bool "yaffs2 - Access of YAFFS2 filesystem"
1414 This provides commands for accessing a YAFFS2 filesystem. Yet
1415 Another Flash Filesystem 2 is a filesystem designed specifically
1416 for NAND flash. It incorporates bad-block management and ensures
1417 that device writes are sequential regardless of filesystem
1421 bool "zfs - Access of ZFS filesystem"
1423 This provides commands to accessing a ZFS filesystem, commonly used
1424 on Solaris systems. Two sub-commands are provided:
1426 zfsls - list files in a directory
1427 zfsload - load a file
1429 See doc/README.zfs for more details.
1433 menu "Debug commands"
1438 The bedbug (emBEDded deBUGger) command provides debugging features
1439 for some PowerPC processors. For details please see the
1440 docuemntation in doc/README.beddbug
1443 bool "diag - Board diagnostics"
1445 This command provides access to board diagnostic tests. These are
1446 called Power-on Self Tests (POST). The command allows listing of
1447 available tests and running either all the tests, or specific tests
1451 bool "irq - Show information about interrupts"
1452 depends on !ARM && !MIPS && !SH
1454 This enables two commands:
1456 interrupts - enable or disable interrupts
1457 irqinfo - print device-specific interrupt information
1460 bool "kgdb - Allow debugging of U-Boot with gdb"
1462 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1463 over a serial link for debugging purposes. This allows
1464 single-stepping, inspecting variables, etc. This is supported only
1465 on PowerPC at present.
1468 bool "trace - Support tracing of function calls and timing"
1470 Enables a command to control using of function tracing within
1471 U-Boot. This allows recording of call traces including timing
1472 information. The command can write data to memory for exporting
1473 for analsys (e.g. using bootchart). See doc/README.trace for full
1479 tristate "Enable UBI - Unsorted block images commands"
1483 default y if NAND_SUNXI
1485 UBI is a software layer above MTD layer which admits use of LVM-like
1486 logical volumes on top of MTD devices, hides some complexities of
1487 flash chips like wear and bad blocks and provides some other useful
1488 capabilities. Please, consult the MTD web site for more details
1489 (www.linux-mtd.infradead.org). Activate this option if you want
1490 to use U-Boot UBI commands.
1493 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1497 default y if CMD_UBI
1499 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob