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.
583 bool "dm - Access to driver model information"
587 Provides access to driver model data structures and information,
588 such as a list of devices, list of uclasses and the state of each
589 device (e.g. activated). This is not required for operation, but
590 can be useful to see the state of driver model for debugging or
594 bool "fdcboot - Boot from floppy device"
596 The 'fdtboot' command allows booting an image from a floppy disk.
599 bool "flinfo, erase, protect"
603 flinfo - print FLASH memory information
605 protect - enable or disable FLASH write protection
613 config CMD_FPGA_LOADBP
614 bool "fpga loadbp - load partial bitstream (Xilinx only)"
617 Supports loading an FPGA device from a bitstream buffer containing
620 config CMD_FPGA_LOADFS
621 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
624 Supports loading an FPGA device from a FAT filesystem.
626 config CMD_FPGA_LOADMK
627 bool "fpga loadmk - load bitstream from image"
630 Supports loading an FPGA device from a image generated by mkimage.
632 config CMD_FPGA_LOADP
633 bool "fpga loadp - load partial bitstream"
636 Supports loading an FPGA device from a bitstream buffer containing
640 bool "fpgad - dump FPGA registers"
642 (legacy, needs conversion to driver model)
643 Provides a way to dump FPGA registers by calling the board-specific
644 fpga_get_reg() function. This functions similarly to the 'md'
648 bool "fuse - support for the fuse subssystem"
650 (deprecated - needs conversion to driver model)
651 This allows reading, sensing, programming or overriding fuses
652 which control the behaviour of the device. The command uses the
661 bool "GPT (GUID Partition Table) command"
662 select PARTITION_UUIDS
665 Enable the 'gpt' command to ready and write GPT style partition
668 config CMD_GPT_RENAME
669 bool "GPT partition renaming commands"
672 Enables the 'gpt' command to interchange names on two GPT
673 partitions via the 'gpt swap' command or to rename single
674 partitions via the 'rename' command.
677 bool "ide - Support for IDE drivers"
680 Provides an 'ide' command which allows accessing the IDE drive,
681 reseting the IDE interface, printing the partition table and
682 geting device info. It also enables the 'diskboot' command which
683 permits booting from an IDE drive.
686 bool "io - Support for performing I/O accesses"
688 Provides an 'iod' command to display I/O space and an 'iow' command
689 to write values to the I/O space. This can be useful for manually
690 checking the state of devices during boot when debugging device
694 bool "iotrace - Support for tracing I/O activity"
696 Provides an 'iotrace' command which supports recording I/O reads and
697 writes in a trace buffer in memory . It also maintains a checksum
698 of the trace records (even if space is exhausted) so that the
699 sequence of I/O accesses can be verified.
701 When debugging drivers it is useful to see what I/O accesses were
702 done and in what order.
704 Even if the individual accesses are of little interest it can be
705 useful to verify that the access pattern is consistent each time
706 an operation is performed. In this case a checksum can be used to
707 characterise the operation of a driver. The checksum can be compared
708 across different runs of the operation to verify that the driver is
711 In particular, when performing major refactoring of the driver, where
712 the access pattern should not change, the checksum provides assurance
713 that the refactoring work has not broken the driver.
715 This works by sneaking into the io.h heder for an architecture and
716 redirecting I/O accesses through iotrace's tracing mechanism.
718 For now no commands are provided to examine the trace buffer. The
719 format is fairly simple, so 'md' is a reasonable substitute.
721 Note: The checksum feature is only useful for I/O regions where the
722 contents do not change outside of software control. Where this is not
723 suitable you can fall back to manually comparing the addresses. It
724 might be useful to enhance tracing to only checksum the accesses and
725 not the data read/written.
736 Load a binary file over serial line.
742 Load an S-Record file over serial line
747 MMC memory mapped support.
751 default y if NAND_SUNXI
756 config CMD_NAND_TRIMFFS
757 bool "nand write.trimffs"
758 default y if ARCH_SUNXI
760 Allows one to skip empty pages when flashing something on a NAND.
762 config CMD_NAND_LOCK_UNLOCK
763 bool "nand lock/unlock"
765 NAND locking support.
767 config CMD_NAND_TORTURE
770 NAND torture support.
775 bool "mmc_spi - Set up MMC SPI device"
777 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
778 Peripheral Interface) device. The device provides a means of
779 accessing an MMC device via SPI using a single data line, limited
780 to 20MHz. It is useful since it reduces the amount of protocol code
784 bool "onenand - access to onenand device"
786 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
787 various useful features. This command allows reading, writing,
788 and erasing blocks. It allso provides a way to show and change
789 bad blocks, and test the device.
793 select PARTITION_UUIDS
795 Read and display information about the partition table on
799 bool "pci - Access PCI devices"
801 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
802 used on some devices to allow the CPU to communicate with its
803 peripherals. Sub-commands allow bus enumeration, displaying and
804 changing configuration space and a few other features.
807 bool "pinit - Set up PCMCIA device"
809 Provides a means to initialise a PCMCIA (Personal Computer Memory
810 Card International Association) device. This is an old standard from
811 about 1990. These devices are typically removable memory or network
812 cards using a standard 68-pin connector.
815 bool "read - Read binary data from a partition"
817 Provides low-level access to the data in a partition.
819 config CMD_REMOTEPROC
821 depends on REMOTEPROC
823 Support for Remote Processor control
826 bool "sata - Access SATA subsystem"
829 SATA (Serial Advanced Technology Attachment) is a serial bus
830 standard for connecting to hard drives and other storage devices.
831 This command provides information about attached devices and allows
832 reading, writing and other operations.
834 SATA replaces PATA (originally just ATA), which stands for Parallel AT
835 Attachment, where AT refers to an IBM AT (Advanced Technology)
836 computer released in 1984.
839 bool "saves - Save a file over serial in S-Record format"
841 Provides a way to save a binary file using the Motorola S-Record
842 format over the serial line.
845 bool "sdram - Print SDRAM configuration information"
847 Provides information about attached SDRAM. This assumed that the
848 SDRAM has an EEPROM with information that can be read using the
849 I2C bus. This is only available on some boards.
857 bool "sf test - Allow testing of SPI flash"
859 Provides a way to test that SPI flash is working correctly. The
860 test is destructive, in that an area of SPI flash must be provided
861 for the test to use. Performance information is also provided,
862 measuring the performance of reading, writing and erasing in
863 Mbps (Million Bits Per Second). This value should approximately
864 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
865 everything is working properly.
873 bool "tsi148 - Command to access tsi148 device"
875 This provides various sub-commands to initialise and configure the
876 Turndra tsi148 device. See the command help for full details.
879 bool "universe - Command to set up the Turndra Universe controller"
881 This allows setting up the VMEbus provided by this controller.
882 See the command help for full details.
889 config CMD_USB_MASS_STORAGE
890 bool "UMS usb mass storage"
892 USB mass storage support
897 menu "Shell scripting commands"
909 Return true/false on integer compare.
915 Run script from memory
921 Evaluate boolean and math expressions and store the result in an env
923 Also supports loading the value at a memory location into a variable.
924 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
928 menu "Network commands"
931 bool "bootp, tftpboot"
936 bootp - boot image via network using BOOTP/TFTP protocol
937 tftpboot - boot image via network using TFTP protocol
942 TFTP put command, for uploading files to a server
947 Act as a TFTP server and boot the first received file
952 Boot image via network using RARP/TFTP protocol
957 Boot image via network using DHCP/TFTP protocol
963 Boot image via network using PXE protocol
969 Boot image via network using NFS protocol.
974 Enable MII utility commands.
979 Send ICMP ECHO_REQUEST to network host
984 Perform CDP network configuration
989 Synchronize RTC via network
994 Lookup the IP of a hostname
996 config CMD_LINK_LOCAL
999 Acquire a network IP address using the link-local protocol
1004 Allow control of L2 Ethernet switch commands. These are supported
1005 by the vsc9953 Ethernet driver at present. Sub-commands allow
1006 operations such as enabling / disabling a port and
1007 viewing/maintaining the filtering database (FDB)
1011 menu "Misc commands"
1014 bool "Enable 'bmp' command"
1015 depends on LCD || DM_VIDEO || VIDEO
1017 This provides a way to obtain information about a BMP-format iamge
1018 and to display it. BMP (which presumably stands for BitMaP) is a
1019 file format defined by Microsoft which supports images of various
1020 depths, formats and compression methods. Headers on the file
1021 determine the formats used. This command can be used by first loading
1022 the image into RAM, then using this command to look at it or display
1026 bool "Enable board-specific commands"
1028 (deprecated: instead, please define a Kconfig option for each command)
1030 Some boards have board-specific commands which are only enabled
1031 during developemnt and need to be turned off for production. This
1032 option provides a way to control this. The commands that are enabled
1033 vary depending on the board.
1035 config CMD_BKOPS_ENABLE
1036 bool "mmc bkops enable"
1040 Enable command for setting manual background operations handshake
1041 on a eMMC device. The feature is optionally available on eMMC devices
1042 conforming to standard >= 4.41.
1044 config CMD_BLOCK_CACHE
1045 bool "blkcache - control and stats for block cache"
1046 depends on BLOCK_CACHE
1047 default y if BLOCK_CACHE
1049 Enable the blkcache command, which can be used to control the
1050 operation of the cache functions.
1051 This is most useful when fine-tuning the operation of the cache
1052 during development, but also allows the cache to be disabled when
1053 it might hurt performance (e.g. when using the ums command).
1056 bool "icache or dcache"
1058 Enable the "icache" and "dcache" commands
1061 bool "Enable the 'display' command, for character displays"
1063 (this needs porting to driver model)
1064 This enables the 'display' command which allows a string to be
1065 displayed on a simple board-specific display. Implement
1066 display_putc() to use it.
1072 Enable the 'led' command which allows for control of LEDs supported
1073 by the board. The LEDs can be listed with 'led list' and controlled
1074 with led on/off/togle/blink. Any LED drivers can be controlled with
1075 this command, e.g. led_gpio.
1081 Enable the 'date' command for getting/setting the time/date in RTC
1087 Run commands and summarize execution time.
1090 bool "gettime - read elapsed time"
1092 Enable the 'gettime' command which reads the elapsed time since
1093 U-Boot started running. This shows the time in seconds and
1094 milliseconds. See also the 'bootstage' command which provides more
1095 flexibility for boot timing.
1097 # TODO: rename to CMD_SLEEP
1102 Delay execution for some time
1107 Access the system timer.
1113 This provides basic access to the U-Boot's sound support. The main
1114 feature is to play a beep.
1116 sound init - set up sound system
1117 sound play - play a sound
1123 This provides access to the QEMU firmware interface. The main
1124 feature is to allow easy loading of files passed to qemu-system
1125 via -kernel / -initrd
1127 source "cmd/mvebu/Kconfig"
1130 bool "terminal - provides a way to attach a serial terminal"
1132 Provides a 'cu'-like serial terminal command. This can be used to
1133 access other serial ports from the system console. The terminal
1134 is very simple with no special processing of characters. As with
1135 cu, you can press ~. (tilde followed by period) to exit.
1138 bool "uuid, guid - generation of unique IDs"
1140 This enables two commands:
1142 uuid - generate random Universally Unique Identifier
1143 guid - generate Globally Unique Identifier based on random UUID
1145 The two commands are very similar except for the endianness of the
1150 config CMD_BOOTSTAGE
1151 bool "Enable the 'bootstage' command"
1152 depends on BOOTSTAGE
1154 Add a 'bootstage' command which supports printing a report
1155 and un/stashing of bootstage data.
1157 menu "Power commands"
1159 bool "Enable Driver Model PMIC command"
1162 This is the pmic command, based on a driver model pmic's API.
1163 Command features are unchanged:
1164 - list - list pmic devices
1165 - pmic dev <id> - show or [set] operating pmic device (NEW)
1166 - pmic dump - dump registers
1167 - pmic read address - read byte of register at address
1168 - pmic write address - write byte to register at address
1169 The only one change for this command is 'dev' subcommand.
1171 config CMD_REGULATOR
1172 bool "Enable Driver Model REGULATOR command"
1173 depends on DM_REGULATOR
1175 This command is based on driver model regulator's API.
1176 User interface features:
1177 - list - list regulator devices
1178 - regulator dev <id> - show or [set] operating regulator device
1179 - regulator info - print constraints info
1180 - regulator status - print operating status
1181 - regulator value <val] <-f> - print/[set] voltage value [uV]
1182 - regulator current <val> - print/[set] current value [uA]
1183 - regulator mode <id> - print/[set] operating mode id
1184 - regulator enable - enable the regulator output
1185 - regulator disable - disable the regulator output
1187 The '-f' (force) option can be used for set the value which exceeds
1188 the limits, which are found in device-tree and are kept in regulator's
1189 uclass platdata structure.
1193 menu "Security commands"
1195 bool "Enable the 'aes' command"
1198 This provides a means to encrypt and decrypt data using the AES
1199 (Advanced Encryption Standard). This algorithm uses a symetric key
1200 and is widely used as a streaming cipher. Different key lengths are
1201 supported by the algorithm but this command only supports 128 bits
1205 bool "Enable the 'blob' command"
1207 This is used with the Freescale secure boot mechanism.
1209 Freescale's SEC block has built-in Blob Protocol which provides
1210 a method for protecting user-defined data across system power
1211 cycles. SEC block protects data in a data structure called a Blob,
1212 which provides both confidentiality and integrity protection.
1214 Encapsulating data as a blob
1215 Each time that the Blob Protocol is used to protect data, a
1216 different randomly generated key is used to encrypt the data.
1217 This random key is itself encrypted using a key which is derived
1218 from SoC's non-volatile secret key and a 16 bit Key identifier.
1219 The resulting encrypted key along with encrypted data is called a
1220 blob. The non-volatile secure key is available for use only during
1223 During decapsulation, the reverse process is performed to get back
1227 blob enc - encapsulating data as a cryptgraphic blob
1228 blob dec - decapsulating cryptgraphic blob to get the data
1232 blob enc src dst len km
1234 Encapsulate and create blob of data $len bytes long
1235 at address $src and store the result at address $dst.
1236 $km is the 16 byte key modifier is also required for
1237 generation/use as key for cryptographic operation. Key
1238 modifier should be 16 byte long.
1240 blob dec src dst len km
1242 Decapsulate the blob of data at address $src and
1243 store result of $len byte at addr $dst.
1244 $km is the 16 byte key modifier is also required for
1245 generation/use as key for cryptographic operation. Key
1246 modifier should be 16 byte long.
1249 bool "Support 'hash' command"
1252 This provides a way to hash data in memory using various supported
1253 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1254 saved to memory or to an environment variable. It is also possible
1255 to verify a hash against data in memory.
1261 Add -v option to verify data against a hash.
1264 bool "Enable the 'tpm' command"
1267 This provides a means to talk to a TPM from the command line. A wide
1268 range of commands if provided - see 'tpm help' for details. The
1269 command requires a suitable TPM on your board and the correct driver
1273 bool "Enable the 'tpm test' command"
1276 This provides a a series of tests to confirm that the TPM is working
1277 correctly. The tests cover initialisation, non-volatile RAM, extend,
1278 global lock and checking that timing is within expectations. The
1279 tests pass correctly on Infineon TPMs but may need to be adjusted
1284 menu "Firmware commands"
1286 bool "Enable crosec command"
1290 Enable command-line access to the Chrome OS EC (Embedded
1291 Controller). This provides the 'crosec' command which has
1292 a number of sub-commands for performing EC tasks such as
1293 updating its flash, accessing a small saved context area
1294 and talking to the I2C bus behind the EC (if there is one).
1297 menu "Filesystem commands"
1299 bool "Enable the 'cbfs' command"
1302 Define this to enable support for reading from a Coreboot
1303 filesystem. This is a ROM-based filesystem used for accessing files
1304 on systems that use coreboot as the first boot-loader and then load
1305 U-Boot to actually boot the Operating System. Available commands are
1306 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1309 bool "Enable the 'cramfs' command"
1310 depends on FS_CRAMFS
1312 This provides commands for dealing with CRAMFS (Compressed ROM
1313 filesystem). CRAMFS is useful when space is tight since files are
1314 compressed. Two commands are provided:
1316 cramfsls - lists files in a cramfs image
1317 cramfsload - loads a file from a cramfs image
1320 bool "ext2 command support"
1322 Enables EXT2 FS command
1325 bool "ext4 command support"
1327 Enables EXT4 FS command
1329 config CMD_EXT4_WRITE
1331 bool "ext4 write command support"
1333 Enables EXT4 FS write command
1336 bool "FAT command support"
1339 Support for the FAT fs
1341 config CMD_FS_GENERIC
1342 bool "filesystem commands"
1344 Enables filesystem commands (e.g. load, ls) that work for multiple
1348 bool "fsuuid command"
1350 Enables fsuuid command for filesystem UUID.
1353 bool "jffs2 command"
1356 Enables commands to support the JFFS2 (Journalling Flash File System
1357 version 2) filesystem. This enables fsload, ls and fsinfo which
1358 provide the ability to load files, list directories and obtain
1359 filesystem information.
1362 bool "MTD partition support"
1364 MTD partition support
1366 config MTDIDS_DEFAULT
1367 string "Default MTD IDs"
1368 depends on CMD_MTDPARTS
1370 Defines a default MTD ID
1372 config MTDPARTS_DEFAULT
1373 string "Default MTD partition scheme"
1374 depends on CMD_MTDPARTS
1376 Defines a default MTD partitioning scheme in the Linux MTD command
1377 line partitions format
1379 config CMD_MTDPARTS_SPREAD
1380 bool "Padd partition size to take account of bad blocks"
1381 depends on CMD_MTDPARTS
1383 This enables the 'spread' sub-command of the mtdparts command.
1384 This command will modify the existing mtdparts variable by increasing
1385 the size of the partitions such that 1) each partition's net size is
1386 at least as large as the size specified in the mtdparts variable and
1387 2) each partition starts on a good block.
1390 bool "reiser - Access to reiserfs filesystems"
1392 This provides two commands which operate on a resierfs filesystem,
1393 commonly used some years ago:
1395 reiserls - list files
1396 reiserload - load a file
1399 bool "scsi - Access to SCSI devices"
1402 This provides a 'scsi' command which provides access to SCSI (Small
1403 Computer System Interface) devices. The command provides a way to
1404 scan the bus, reset the bus, read and write data and get information
1408 bool "yaffs2 - Access of YAFFS2 filesystem"
1412 This provides commands for accessing a YAFFS2 filesystem. Yet
1413 Another Flash Filesystem 2 is a filesystem designed specifically
1414 for NAND flash. It incorporates bad-block management and ensures
1415 that device writes are sequential regardless of filesystem
1420 menu "Debug commands"
1425 The bedbug (emBEDded deBUGger) command provides debugging features
1426 for some PowerPC processors. For details please see the
1427 docuemntation in doc/README.beddbug
1430 bool "diag - Board diagnostics"
1432 This command provides access to board diagnostic tests. These are
1433 called Power-on Self Tests (POST). The command allows listing of
1434 available tests and running either all the tests, or specific tests
1438 bool "irq - Show information about interrupts"
1439 depends on !ARM && !MIPS && !SH
1441 This enables two commands:
1443 interrupts - enable or disable interrupts
1444 irqinfo - print device-specific interrupt information
1447 bool "kgdb - Allow debugging of U-Boot with gdb"
1449 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1450 over a serial link for debugging purposes. This allows
1451 single-stepping, inspecting variables, etc. This is supported only
1452 on PowerPC at present.
1455 bool "trace - Support tracing of function calls and timing"
1457 Enables a command to control using of function tracing within
1458 U-Boot. This allows recording of call traces including timing
1459 information. The command can write data to memory for exporting
1460 for analsys (e.g. using bootchart). See doc/README.trace for full
1466 tristate "Enable UBI - Unsorted block images commands"
1470 default y if NAND_SUNXI
1472 UBI is a software layer above MTD layer which admits use of LVM-like
1473 logical volumes on top of MTD devices, hides some complexities of
1474 flash chips like wear and bad blocks and provides some other useful
1475 capabilities. Please, consult the MTD web site for more details
1476 (www.linux-mtd.infradead.org). Activate this option if you want
1477 to use U-Boot UBI commands.
1480 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1484 default y if CMD_UBI
1486 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob