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.
317 menu "Environment commands"
320 bool "ask for env variable"
322 Ask for environment variable
340 Edit environment variable.
345 Allow for searching environment variables
351 Save all environment variables into the compiled-in persistent
354 config CMD_ENV_EXISTS
358 Check if a variable is defined in the environment for use in
361 config CMD_ENV_CALLBACK
362 bool "env callbacks - print callbacks and their associated variables"
364 Some environment variable have callbacks defined by
365 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
366 For example changing "baudrate" adjust the serial baud rate. This
367 command lists the currently defined callbacks.
370 bool "env flags -print variables that have non-default flags"
372 Some environment variables have special flags that control their
373 behaviour. For example, serial# can only be written once and cannot
374 be deleted. This command shows the variables that have special
379 menu "Memory commands"
392 Add -v option to verify data against a crc32 checksum.
395 bool "eeprom - EEPROM subsystem"
397 (deprecated, needs conversion to driver model)
398 Provides commands to read and write EEPROM (Electrically Erasable
399 Programmable Read Only Memory) chips that are connected over an
402 config CMD_EEPROM_LAYOUT
403 bool "Enable layout-aware eeprom commands"
404 depends on CMD_EEPROM
406 (deprecated, needs conversion to driver model)
407 When enabled, additional eeprom sub-commands become available.
409 eeprom print - prints the contents of the eeprom in a human-readable
410 way (eeprom layout fields, and data formatted to be fit for human
413 eeprom update - allows user to update eeprom fields by specifying
414 the field name, and providing the new data in a human readable format
415 (same format as displayed by the eeprom print command).
417 Both commands can either auto detect the layout, or be told which
421 __weak int parse_layout_version(char *str)
422 - override to provide your own layout name parsing
423 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
425 - override to setup the layout metadata based on the version
426 __weak int eeprom_layout_detect(unsigned char *data)
427 - override to provide your own algorithm for detecting layout
430 - contains various printing and updating functions for common
431 types of eeprom fields. Can be used for defining
434 config EEPROM_LAYOUT_HELP_STRING
435 string "Tells user what layout names are supported"
436 depends on CMD_EEPROM_LAYOUT
437 default "<not defined>"
439 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
445 Infinite write loop on address range
452 Compute MD5 checksum.
457 depends on CMD_MD5SUM
459 Add -v option to verify data against an MD5 checksum.
464 Display memory information.
467 bool "md, mm, nm, mw, cp, cmp, base, loop"
472 mm - memory modify (auto-incrementing address)
473 nm - memory modify (constant address)
474 mw - memory write (fill)
477 base - print or set address offset
478 loop - initialize loop on address range
483 Simple RAM read/write test.
488 mdc - memory display cyclic
489 mwc - memory write cyclic
495 Compute SHA1 checksum.
497 config SHA1SUM_VERIFY
499 depends on CMD_SHA1SUM
501 Add -v option to verify data against a SHA1 checksum.
504 bool "strings - display strings in memory"
506 This works similarly to the Unix 'strings' command except that it
507 works with a memory range. String of printable characters found
508 within the range are displayed. The minimum number of characters
509 for a sequence to be considered a string can be provided.
513 menu "Compression commands"
519 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
525 Uncompress a zip-compressed memory region.
530 Compress a memory region with zlib deflate method.
534 menu "Device access commands"
537 #depends on FLASH_CFI_DRIVER
540 ARM Ltd reference designs flash partition access
543 bool "clk - Show clock frequencies"
546 Shows clock frequences by calling a sock_clk_dump() hook function.
547 This is depreated in favour of using the CLK uclass and accessing
548 clock values from associated drivers. However currently no command
552 bool "demo - Demonstration commands for driver model"
555 Provides a 'demo' command which can be used to play around with
556 driver model. To use this properly you will need to enable one or
557 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
558 Otherwise you will always get an empty list of devices. The demo
559 devices are defined in the sandbox device tree, so the easiest
560 option is to use sandbox and pass the -d point to sandbox's
565 select USB_FUNCTION_DFU
567 Enables the command "dfu" which is used to have U-Boot create a DFU
568 class device via USB.
571 bool "dm - Access to driver model information"
575 Provides access to driver model data structures and information,
576 such as a list of devices, list of uclasses and the state of each
577 device (e.g. activated). This is not required for operation, but
578 can be useful to see the state of driver model for debugging or
582 bool "fdcboot - Boot from floppy device"
584 The 'fdtboot' command allows booting an image from a floppy disk.
587 bool "flinfo, erase, protect"
591 flinfo - print FLASH memory information
593 protect - enable or disable FLASH write protection
601 config CMD_FPGA_LOADBP
602 bool "fpga loadbp - load partial bitstream (Xilinx only)"
605 Supports loading an FPGA device from a bitstream buffer containing
608 config CMD_FPGA_LOADFS
609 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
612 Supports loading an FPGA device from a FAT filesystem.
614 config CMD_FPGA_LOADMK
615 bool "fpga loadmk - load bitstream from image"
618 Supports loading an FPGA device from a image generated by mkimage.
620 config CMD_FPGA_LOADP
621 bool "fpga loadp - load partial bitstream"
624 Supports loading an FPGA device from a bitstream buffer containing
628 bool "fpgad - dump FPGA registers"
630 (legacy, needs conversion to driver model)
631 Provides a way to dump FPGA registers by calling the board-specific
632 fpga_get_reg() function. This functions similarly to the 'md'
636 bool "fuse - support for the fuse subssystem"
638 (deprecated - needs conversion to driver model)
639 This allows reading, sensing, programming or overriding fuses
640 which control the behaviour of the device. The command uses the
649 bool "GPT (GUID Partition Table) command"
650 select PARTITION_UUIDS
653 Enable the 'gpt' command to ready and write GPT style partition
656 config CMD_GPT_RENAME
657 bool "GPT partition renaming commands"
660 Enables the 'gpt' command to interchange names on two GPT
661 partitions via the 'gpt swap' command or to rename single
662 partitions via the 'rename' command.
665 bool "ide - Support for IDE drivers"
668 Provides an 'ide' command which allows accessing the IDE drive,
669 reseting the IDE interface, printing the partition table and
670 geting device info. It also enables the 'diskboot' command which
671 permits booting from an IDE drive.
674 bool "io - Support for performing I/O accesses"
676 Provides an 'iod' command to display I/O space and an 'iow' command
677 to write values to the I/O space. This can be useful for manually
678 checking the state of devices during boot when debugging device
682 bool "iotrace - Support for tracing I/O activity"
684 Provides an 'iotrace' command which supports recording I/O reads and
685 writes in a trace buffer in memory . It also maintains a checksum
686 of the trace records (even if space is exhausted) so that the
687 sequence of I/O accesses can be verified.
689 When debugging drivers it is useful to see what I/O accesses were
690 done and in what order.
692 Even if the individual accesses are of little interest it can be
693 useful to verify that the access pattern is consistent each time
694 an operation is performed. In this case a checksum can be used to
695 characterise the operation of a driver. The checksum can be compared
696 across different runs of the operation to verify that the driver is
699 In particular, when performing major refactoring of the driver, where
700 the access pattern should not change, the checksum provides assurance
701 that the refactoring work has not broken the driver.
703 This works by sneaking into the io.h heder for an architecture and
704 redirecting I/O accesses through iotrace's tracing mechanism.
706 For now no commands are provided to examine the trace buffer. The
707 format is fairly simple, so 'md' is a reasonable substitute.
709 Note: The checksum feature is only useful for I/O regions where the
710 contents do not change outside of software control. Where this is not
711 suitable you can fall back to manually comparing the addresses. It
712 might be useful to enhance tracing to only checksum the accesses and
713 not the data read/written.
724 Load a binary file over serial line.
730 Load an S-Record file over serial line
735 MMC memory mapped support.
739 default y if NAND_SUNXI
744 config CMD_NAND_TRIMFFS
745 bool "nand write.trimffs"
746 default y if ARCH_SUNXI
748 Allows one to skip empty pages when flashing something on a NAND.
750 config CMD_NAND_LOCK_UNLOCK
751 bool "nand lock/unlock"
753 NAND locking support.
755 config CMD_NAND_TORTURE
758 NAND torture support.
763 bool "mmc_spi - Set up MMC SPI device"
765 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
766 Peripheral Interface) device. The device provides a means of
767 accessing an MMC device via SPI using a single data line, limited
768 to 20MHz. It is useful since it reduces the amount of protocol code
772 bool "onenand - access to onenand device"
774 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
775 various useful features. This command allows reading, writing,
776 and erasing blocks. It allso provides a way to show and change
777 bad blocks, and test the device.
781 select PARTITION_UUIDS
783 Read and display information about the partition table on
787 bool "pci - Access PCI devices"
789 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
790 used on some devices to allow the CPU to communicate with its
791 peripherals. Sub-commands allow bus enumeration, displaying and
792 changing configuration space and a few other features.
795 bool "pinit - Set up PCMCIA device"
797 Provides a means to initialise a PCMCIA (Personal Computer Memory
798 Card International Association) device. This is an old standard from
799 about 1990. These devices are typically removable memory or network
800 cards using a standard 68-pin connector.
803 bool "read - Read binary data from a partition"
805 Provides low-level access to the data in a partition.
807 config CMD_REMOTEPROC
809 depends on REMOTEPROC
811 Support for Remote Processor control
814 bool "sata - Access SATA subsystem"
817 SATA (Serial Advanced Technology Attachment) is a serial bus
818 standard for connecting to hard drives and other storage devices.
819 This command provides information about attached devices and allows
820 reading, writing and other operations.
822 SATA replaces PATA (originally just ATA), which stands for Parallel AT
823 Attachment, where AT refers to an IBM AT (Advanced Technology)
824 computer released in 1984.
827 bool "saves - Save a file over serial in S-Record format"
829 Provides a way to save a binary file using the Motorola S-Record
830 format over the serial line.
833 bool "sdram - Print SDRAM configuration information"
835 Provides information about attached SDRAM. This assumed that the
836 SDRAM has an EEPROM with information that can be read using the
837 I2C bus. This is only available on some boards.
845 bool "sf test - Allow testing of SPI flash"
847 Provides a way to test that SPI flash is working correctly. The
848 test is destructive, in that an area of SPI flash must be provided
849 for the test to use. Performance information is also provided,
850 measuring the performance of reading, writing and erasing in
851 Mbps (Million Bits Per Second). This value should approximately
852 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
853 everything is working properly.
861 bool "tsi148 - Command to access tsi148 device"
863 This provides various sub-commands to initialise and configure the
864 Turndra tsi148 device. See the command help for full details.
871 config CMD_USB_MASS_STORAGE
872 bool "UMS usb mass storage"
874 USB mass storage support
879 menu "Shell scripting commands"
891 Return true/false on integer compare.
897 Run script from memory
903 Evaluate boolean and math expressions and store the result in an env
905 Also supports loading the value at a memory location into a variable.
906 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
910 menu "Network commands"
913 bool "bootp, tftpboot"
918 bootp - boot image via network using BOOTP/TFTP protocol
919 tftpboot - boot image via network using TFTP protocol
924 TFTP put command, for uploading files to a server
929 Act as a TFTP server and boot the first received file
934 Boot image via network using RARP/TFTP protocol
939 Boot image via network using DHCP/TFTP protocol
945 Boot image via network using PXE protocol
951 Boot image via network using NFS protocol.
956 Enable MII utility commands.
961 Send ICMP ECHO_REQUEST to network host
966 Perform CDP network configuration
971 Synchronize RTC via network
976 Lookup the IP of a hostname
978 config CMD_LINK_LOCAL
981 Acquire a network IP address using the link-local protocol
986 Allow control of L2 Ethernet switch commands. These are supported
987 by the vsc9953 Ethernet driver at present. Sub-commands allow
988 operations such as enabling / disabling a port and
989 viewing/maintaining the filtering database (FDB)
996 bool "Enable 'bmp' command"
997 depends on LCD || DM_VIDEO || VIDEO
999 This provides a way to obtain information about a BMP-format iamge
1000 and to display it. BMP (which presumably stands for BitMaP) is a
1001 file format defined by Microsoft which supports images of various
1002 depths, formats and compression methods. Headers on the file
1003 determine the formats used. This command can be used by first loading
1004 the image into RAM, then using this command to look at it or display
1008 bool "Enable board-specific commands"
1010 (deprecated: instead, please define a Kconfig option for each command)
1012 Some boards have board-specific commands which are only enabled
1013 during developemnt and need to be turned off for production. This
1014 option provides a way to control this. The commands that are enabled
1015 vary depending on the board.
1017 config CMD_BKOPS_ENABLE
1018 bool "mmc bkops enable"
1022 Enable command for setting manual background operations handshake
1023 on a eMMC device. The feature is optionally available on eMMC devices
1024 conforming to standard >= 4.41.
1026 config CMD_BLOCK_CACHE
1027 bool "blkcache - control and stats for block cache"
1028 depends on BLOCK_CACHE
1029 default y if BLOCK_CACHE
1031 Enable the blkcache command, which can be used to control the
1032 operation of the cache functions.
1033 This is most useful when fine-tuning the operation of the cache
1034 during development, but also allows the cache to be disabled when
1035 it might hurt performance (e.g. when using the ums command).
1038 bool "icache or dcache"
1040 Enable the "icache" and "dcache" commands
1043 bool "Enable the 'display' command, for character displays"
1045 (this needs porting to driver model)
1046 This enables the 'display' command which allows a string to be
1047 displayed on a simple board-specific display. Implement
1048 display_putc() to use it.
1054 Enable the 'led' command which allows for control of LEDs supported
1055 by the board. The LEDs can be listed with 'led list' and controlled
1056 with led on/off/togle/blink. Any LED drivers can be controlled with
1057 this command, e.g. led_gpio.
1063 Enable the 'date' command for getting/setting the time/date in RTC
1069 Run commands and summarize execution time.
1072 bool "gettime - read elapsed time"
1074 Enable the 'gettime' command which reads the elapsed time since
1075 U-Boot started running. This shows the time in seconds and
1076 milliseconds. See also the 'bootstage' command which provides more
1077 flexibility for boot timing.
1079 # TODO: rename to CMD_SLEEP
1084 Delay execution for some time
1089 Access the system timer.
1095 This provides basic access to the U-Boot's sound support. The main
1096 feature is to play a beep.
1098 sound init - set up sound system
1099 sound play - play a sound
1105 This provides access to the QEMU firmware interface. The main
1106 feature is to allow easy loading of files passed to qemu-system
1107 via -kernel / -initrd
1109 source "cmd/mvebu/Kconfig"
1112 bool "terminal - provides a way to attach a serial terminal"
1114 Provides a 'cu'-like serial terminal command. This can be used to
1115 access other serial ports from the system console. The terminal
1116 is very simple with no special processing of characters. As with
1117 cu, you can press ~. (tilde followed by period) to exit.
1121 config CMD_BOOTSTAGE
1122 bool "Enable the 'bootstage' command"
1123 depends on BOOTSTAGE
1125 Add a 'bootstage' command which supports printing a report
1126 and un/stashing of bootstage data.
1128 menu "Power commands"
1130 bool "Enable Driver Model PMIC command"
1133 This is the pmic command, based on a driver model pmic's API.
1134 Command features are unchanged:
1135 - list - list pmic devices
1136 - pmic dev <id> - show or [set] operating pmic device (NEW)
1137 - pmic dump - dump registers
1138 - pmic read address - read byte of register at address
1139 - pmic write address - write byte to register at address
1140 The only one change for this command is 'dev' subcommand.
1142 config CMD_REGULATOR
1143 bool "Enable Driver Model REGULATOR command"
1144 depends on DM_REGULATOR
1146 This command is based on driver model regulator's API.
1147 User interface features:
1148 - list - list regulator devices
1149 - regulator dev <id> - show or [set] operating regulator device
1150 - regulator info - print constraints info
1151 - regulator status - print operating status
1152 - regulator value <val] <-f> - print/[set] voltage value [uV]
1153 - regulator current <val> - print/[set] current value [uA]
1154 - regulator mode <id> - print/[set] operating mode id
1155 - regulator enable - enable the regulator output
1156 - regulator disable - disable the regulator output
1158 The '-f' (force) option can be used for set the value which exceeds
1159 the limits, which are found in device-tree and are kept in regulator's
1160 uclass platdata structure.
1164 menu "Security commands"
1166 bool "Enable the 'aes' command"
1169 This provides a means to encrypt and decrypt data using the AES
1170 (Advanced Encryption Standard). This algorithm uses a symetric key
1171 and is widely used as a streaming cipher. Different key lengths are
1172 supported by the algorithm but this command only supports 128 bits
1176 bool "Enable the 'blob' command"
1178 This is used with the Freescale secure boot mechanism.
1180 Freescale's SEC block has built-in Blob Protocol which provides
1181 a method for protecting user-defined data across system power
1182 cycles. SEC block protects data in a data structure called a Blob,
1183 which provides both confidentiality and integrity protection.
1185 Encapsulating data as a blob
1186 Each time that the Blob Protocol is used to protect data, a
1187 different randomly generated key is used to encrypt the data.
1188 This random key is itself encrypted using a key which is derived
1189 from SoC's non-volatile secret key and a 16 bit Key identifier.
1190 The resulting encrypted key along with encrypted data is called a
1191 blob. The non-volatile secure key is available for use only during
1194 During decapsulation, the reverse process is performed to get back
1198 blob enc - encapsulating data as a cryptgraphic blob
1199 blob dec - decapsulating cryptgraphic blob to get the data
1203 blob enc src dst len km
1205 Encapsulate and create blob of data $len bytes long
1206 at address $src and store the result at address $dst.
1207 $km is the 16 byte key modifier is also required for
1208 generation/use as key for cryptographic operation. Key
1209 modifier should be 16 byte long.
1211 blob dec src dst len km
1213 Decapsulate the blob of data at address $src and
1214 store result of $len byte at addr $dst.
1215 $km is the 16 byte key modifier is also required for
1216 generation/use as key for cryptographic operation. Key
1217 modifier should be 16 byte long.
1220 bool "Support 'hash' command"
1223 This provides a way to hash data in memory using various supported
1224 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1225 saved to memory or to an environment variable. It is also possible
1226 to verify a hash against data in memory.
1232 Add -v option to verify data against a hash.
1235 bool "Enable the 'tpm' command"
1238 This provides a means to talk to a TPM from the command line. A wide
1239 range of commands if provided - see 'tpm help' for details. The
1240 command requires a suitable TPM on your board and the correct driver
1244 bool "Enable the 'tpm test' command"
1247 This provides a a series of tests to confirm that the TPM is working
1248 correctly. The tests cover initialisation, non-volatile RAM, extend,
1249 global lock and checking that timing is within expectations. The
1250 tests pass correctly on Infineon TPMs but may need to be adjusted
1255 menu "Firmware commands"
1257 bool "Enable crosec command"
1261 Enable command-line access to the Chrome OS EC (Embedded
1262 Controller). This provides the 'crosec' command which has
1263 a number of sub-commands for performing EC tasks such as
1264 updating its flash, accessing a small saved context area
1265 and talking to the I2C bus behind the EC (if there is one).
1268 menu "Filesystem commands"
1270 bool "Enable the 'cbfs' command"
1273 Define this to enable support for reading from a Coreboot
1274 filesystem. This is a ROM-based filesystem used for accessing files
1275 on systems that use coreboot as the first boot-loader and then load
1276 U-Boot to actually boot the Operating System. Available commands are
1277 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1280 bool "Enable the 'cramfs' command"
1281 depends on FS_CRAMFS
1283 This provides commands for dealing with CRAMFS (Compressed ROM
1284 filesystem). CRAMFS is useful when space is tight since files are
1285 compressed. Two commands are provided:
1287 cramfsls - lists files in a cramfs image
1288 cramfsload - loads a file from a cramfs image
1291 bool "ext2 command support"
1293 Enables EXT2 FS command
1296 bool "ext4 command support"
1298 Enables EXT4 FS command
1300 config CMD_EXT4_WRITE
1302 bool "ext4 write command support"
1304 Enables EXT4 FS write command
1307 bool "FAT command support"
1310 Support for the FAT fs
1312 config CMD_FS_GENERIC
1313 bool "filesystem commands"
1315 Enables filesystem commands (e.g. load, ls) that work for multiple
1319 bool "fsuuid command"
1321 Enables fsuuid command for filesystem UUID.
1324 bool "jffs2 command"
1327 Enables commands to support the JFFS2 (Journalling Flash File System
1328 version 2) filesystem. This enables fsload, ls and fsinfo which
1329 provide the ability to load files, list directories and obtain
1330 filesystem information.
1333 bool "MTD partition support"
1335 MTD partition support
1337 config MTDIDS_DEFAULT
1338 string "Default MTD IDs"
1339 depends on CMD_MTDPARTS
1341 Defines a default MTD ID
1343 config MTDPARTS_DEFAULT
1344 string "Default MTD partition scheme"
1345 depends on CMD_MTDPARTS
1347 Defines a default MTD partitioning scheme in the Linux MTD command
1348 line partitions format
1350 config CMD_MTDPARTS_SPREAD
1351 bool "Padd partition size to take account of bad blocks"
1352 depends on CMD_MTDPARTS
1354 This enables the 'spread' sub-command of the mtdparts command.
1355 This command will modify the existing mtdparts variable by increasing
1356 the size of the partitions such that 1) each partition's net size is
1357 at least as large as the size specified in the mtdparts variable and
1358 2) each partition starts on a good block.
1361 bool "reiser - Access to reiserfs filesystems"
1363 This provides two commands which operate on a resierfs filesystem,
1364 commonly used some years ago:
1366 reiserls - list files
1367 reiserload - load a file
1370 bool "scsi - Access to SCSI devices"
1373 This provides a 'scsi' command which provides access to SCSI (Small
1374 Computer System Interface) devices. The command provides a way to
1375 scan the bus, reset the bus, read and write data and get information
1379 bool "yaffs2 - Access of YAFFS2 filesystem"
1383 This provides commands for accessing a YAFFS2 filesystem. Yet
1384 Another Flash Filesystem 2 is a filesystem designed specifically
1385 for NAND flash. It incorporates bad-block management and ensures
1386 that device writes are sequential regardless of filesystem
1391 menu "Debug commands"
1396 The bedbug (emBEDded deBUGger) command provides debugging features
1397 for some PowerPC processors. For details please see the
1398 docuemntation in doc/README.beddbug
1401 bool "diag - Board diagnostics"
1403 This command provides access to board diagnostic tests. These are
1404 called Power-on Self Tests (POST). The command allows listing of
1405 available tests and running either all the tests, or specific tests
1409 bool "irq - Show information about interrupts"
1410 depends on !ARM && !MIPS && !SH
1412 This enables two commands:
1414 interrupts - enable or disable interrupts
1415 irqinfo - print device-specific interrupt information
1418 bool "kgdb - Allow debugging of U-Boot with gdb"
1420 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1421 over a serial link for debugging purposes. This allows
1422 single-stepping, inspecting variables, etc. This is supported only
1423 on PowerPC at present.
1426 bool "trace - Support tracing of function calls and timing"
1428 Enables a command to control using of function tracing within
1429 U-Boot. This allows recording of call traces including timing
1430 information. The command can write data to memory for exporting
1431 for analsys (e.g. using bootchart). See doc/README.trace for full
1437 tristate "Enable UBI - Unsorted block images commands"
1441 default y if NAND_SUNXI
1443 UBI is a software layer above MTD layer which admits use of LVM-like
1444 logical volumes on top of MTD devices, hides some complexities of
1445 flash chips like wear and bad blocks and provides some other useful
1446 capabilities. Please, consult the MTD web site for more details
1447 (www.linux-mtd.infradead.org). Activate this option if you want
1448 to use U-Boot UBI commands.
1451 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1455 default y if CMD_UBI
1457 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob