1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
30 This string is displayed in the command line to the left of the
33 menu "Autoboot options"
39 This enables the autoboot. See doc/README.autoboot for detail.
42 bool "Stop autobooting via specific input key / string"
45 This option enables stopping (aborting) of the automatic
46 boot feature only by issuing a specific input key or
47 string. If not enabled, any input key will abort the
48 U-Boot automatic booting process and bring the device
49 to the U-Boot prompt for user input.
51 config AUTOBOOT_PROMPT
52 string "Autoboot stop prompt"
53 depends on AUTOBOOT_KEYED
54 default "Autoboot in %d seconds\\n"
56 This string is displayed before the boot delay selected by
57 CONFIG_BOOTDELAY starts. If it is not defined there is no
58 output indicating that autoboot is in progress.
60 Note that this define is used as the (only) argument to a
61 printf() call, so it may contain '%' format specifications,
62 provided that it also includes, sepearated by commas exactly
63 like in a printf statement, the required arguments. It is
64 the responsibility of the user to select only such arguments
65 that are valid in the given context.
67 config AUTOBOOT_ENCRYPTION
68 bool "Enable encryption in autoboot stopping"
69 depends on AUTOBOOT_KEYED
72 config AUTOBOOT_DELAY_STR
73 string "Delay autobooting via specific input key / string"
74 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
76 This option delays the automatic boot feature by issuing
77 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
78 or the environment variable "bootdelaykey" is specified
79 and this string is received from console input before
80 autoboot starts booting, U-Boot gives a command prompt. The
81 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
82 used, otherwise it never times out.
84 config AUTOBOOT_STOP_STR
85 string "Stop autobooting via specific input key / string"
86 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
88 This option enables stopping (aborting) of the automatic
89 boot feature only by issuing a specific input key or
90 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
91 variable "bootstopkey" is specified and this string is
92 received from console input before autoboot starts booting,
93 U-Boot gives a command prompt. The U-Boot prompt never
94 times out, even if CONFIG_BOOT_RETRY_TIME is used.
96 config AUTOBOOT_KEYED_CTRLC
97 bool "Enable Ctrl-C autoboot interruption"
98 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
101 This option allows for the boot sequence to be interrupted
102 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
103 Setting this variable provides an escape sequence from the
104 limited "password" strings.
106 config AUTOBOOT_STOP_STR_SHA256
107 string "Stop autobooting via SHA256 encrypted password"
108 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
110 This option adds the feature to only stop the autobooting,
111 and therefore boot into the U-Boot prompt, when the input
112 string / password matches a values that is encypted via
113 a SHA256 hash and saved in the environment.
117 source "cmd/fastboot/Kconfig"
134 Print ".config" contents.
136 If this option is enabled, the ".config" file contents are embedded
137 in the U-Boot image and can be printed on the console by the "config"
138 command. This provides information of which options are enabled on
145 Print console devices and information.
150 Print information about available CPUs. This normally shows the
151 number of CPUs, type (e.g. manufacturer, architecture, product or
152 internal name) and clock frequency. Other information may be
153 available depending on the CPU driver.
159 Print GPL license text
175 Run the command stored in the environment "bootcmd", i.e.
176 "bootd" does the same thing as "run bootcmd".
182 Boot an application image from the memory.
187 Boot the Linux zImage
194 Boot an AArch64 Linux Kernel image from memory.
198 depends on EFI_LOADER
201 Boot an EFI image from memory.
203 config CMD_BOOTEFI_HELLO_COMPILE
204 bool "Compile a standard EFI hello world binary for testing"
205 depends on CMD_BOOTEFI && (ARM || X86)
208 This compiles a standard EFI hello world application with U-Boot so
209 that it can be used with the test/py testing framework. This is useful
210 for testing that EFI is working at a basic level, and for bringing
211 up EFI support on a new architecture.
213 No additional space will be required in the resulting U-Boot binary
214 when this option is enabled.
216 config CMD_BOOTEFI_HELLO
217 bool "Allow booting a standard EFI hello world for testing"
218 depends on CMD_BOOTEFI_HELLO_COMPILE
220 This adds a standard EFI hello world application to U-Boot so that
221 it can be used with the 'bootefi hello' command. This is useful
222 for testing that EFI is working at a basic level, and for bringing
223 up EFI support on a new architecture.
225 source lib/efi_selftest/Kconfig
231 Add an ANSI terminal boot menu command.
234 bool "bootelf, bootvx"
237 Boot an ELF/vxWorks image from the memory.
240 bool "Flattened Device Tree utility commands"
244 Do FDT related setup before booting into the Operating System.
250 Start an application at a given address.
256 Run the command in the given environment variable.
262 Print header information for application image.
268 List all images found in flash
274 Extract a part of a multi-image.
279 Poweroff/Shutdown the system
282 bool "spl export - Export boot information for Falcon boot"
285 Falcon mode allows booting directly from SPL into an Operating
286 System such as Linux, thus skipping U-Boot proper. See
287 doc/README.falcon for full information about how to use this
290 config CMD_SPL_NAND_OFS
291 hex "Offset of OS command line args for Falcon-mode NAND boot"
295 This provides the offset of the command line arguments for Linux
296 when booting from NAND in Falcon mode. See doc/README.falcon
297 for full information about how to use this option (and also see
298 board/gateworks/gw_ventana/README for an example).
300 config CMD_SPL_WRITE_SIZE
301 hex "Size of argument area"
305 This provides the size of the command-line argument area in NAND
306 flash used by Falcon-mode boot. See the documentation until CMD_SPL
309 config CMD_THOR_DOWNLOAD
310 bool "thor - TIZEN 'thor' download"
312 Implements the 'thor' download protocol. This is a way of
313 downloading a software update over USB from an attached host.
314 There is no documentation about this within the U-Boot source code
315 but you should be able to find something on the interwebs.
318 bool "zboot - x86 boot command"
320 With x86 machines it is common to boot a bzImage file which
321 contains both a kernel and a setup.bin file. The latter includes
322 configuration information from the dark ages which x86 boards still
323 need to pick things out of.
325 Consider using FIT in preference to this since it supports directly
326 booting both 32- and 64-bit kernels, as well as secure boot.
327 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
331 menu "Environment commands"
334 bool "ask for env variable"
336 Ask for environment variable
354 Edit environment variable.
359 Allow for searching environment variables
365 Save all environment variables into the compiled-in persistent
368 config CMD_ENV_EXISTS
372 Check if a variable is defined in the environment for use in
375 config CMD_ENV_CALLBACK
376 bool "env callbacks - print callbacks and their associated variables"
378 Some environment variable have callbacks defined by
379 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
380 For example changing "baudrate" adjust the serial baud rate. This
381 command lists the currently defined callbacks.
384 bool "env flags -print variables that have non-default flags"
386 Some environment variables have special flags that control their
387 behaviour. For example, serial# can only be written once and cannot
388 be deleted. This command shows the variables that have special
393 menu "Memory commands"
406 Add -v option to verify data against a crc32 checksum.
409 bool "eeprom - EEPROM subsystem"
411 (deprecated, needs conversion to driver model)
412 Provides commands to read and write EEPROM (Electrically Erasable
413 Programmable Read Only Memory) chips that are connected over an
416 config CMD_EEPROM_LAYOUT
417 bool "Enable layout-aware eeprom commands"
418 depends on CMD_EEPROM
420 (deprecated, needs conversion to driver model)
421 When enabled, additional eeprom sub-commands become available.
423 eeprom print - prints the contents of the eeprom in a human-readable
424 way (eeprom layout fields, and data formatted to be fit for human
427 eeprom update - allows user to update eeprom fields by specifying
428 the field name, and providing the new data in a human readable format
429 (same format as displayed by the eeprom print command).
431 Both commands can either auto detect the layout, or be told which
435 __weak int parse_layout_version(char *str)
436 - override to provide your own layout name parsing
437 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
439 - override to setup the layout metadata based on the version
440 __weak int eeprom_layout_detect(unsigned char *data)
441 - override to provide your own algorithm for detecting layout
444 - contains various printing and updating functions for common
445 types of eeprom fields. Can be used for defining
448 config EEPROM_LAYOUT_HELP_STRING
449 string "Tells user what layout names are supported"
450 depends on CMD_EEPROM_LAYOUT
451 default "<not defined>"
453 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
459 Infinite write loop on address range
466 Compute MD5 checksum.
471 depends on CMD_MD5SUM
473 Add -v option to verify data against an MD5 checksum.
478 Display memory information.
481 bool "md, mm, nm, mw, cp, cmp, base, loop"
486 mm - memory modify (auto-incrementing address)
487 nm - memory modify (constant address)
488 mw - memory write (fill)
491 base - print or set address offset
492 loop - initialize loop on address range
497 Simple RAM read/write test.
502 mdc - memory display cyclic
503 mwc - memory write cyclic
509 Compute SHA1 checksum.
511 config SHA1SUM_VERIFY
513 depends on CMD_SHA1SUM
515 Add -v option to verify data against a SHA1 checksum.
518 bool "strings - display strings in memory"
520 This works similarly to the Unix 'strings' command except that it
521 works with a memory range. String of printable characters found
522 within the range are displayed. The minimum number of characters
523 for a sequence to be considered a string can be provided.
527 menu "Compression commands"
533 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
539 Uncompress a zip-compressed memory region.
544 Compress a memory region with zlib deflate method.
548 menu "Device access commands"
551 #depends on FLASH_CFI_DRIVER
554 ARM Ltd reference designs flash partition access
557 bool "clk - Show clock frequencies"
560 Shows clock frequences by calling a sock_clk_dump() hook function.
561 This is depreated in favour of using the CLK uclass and accessing
562 clock values from associated drivers. However currently no command
566 bool "demo - Demonstration commands for driver model"
569 Provides a 'demo' command which can be used to play around with
570 driver model. To use this properly you will need to enable one or
571 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
572 Otherwise you will always get an empty list of devices. The demo
573 devices are defined in the sandbox device tree, so the easiest
574 option is to use sandbox and pass the -d point to sandbox's
579 select USB_FUNCTION_DFU
581 Enables the command "dfu" which is used to have U-Boot create a DFU
582 class device via USB. This command requires that the "dfu_alt_info"
583 environment variable be set and define the alt settings to expose to
587 bool "dm - Access to driver model information"
591 Provides access to driver model data structures and information,
592 such as a list of devices, list of uclasses and the state of each
593 device (e.g. activated). This is not required for operation, but
594 can be useful to see the state of driver model for debugging or
598 bool "fdcboot - Boot from floppy device"
600 The 'fdtboot' command allows booting an image from a floppy disk.
603 bool "flinfo, erase, protect"
607 flinfo - print FLASH memory information
609 protect - enable or disable FLASH write protection
617 config CMD_FPGA_LOADBP
618 bool "fpga loadbp - load partial bitstream (Xilinx only)"
621 Supports loading an FPGA device from a bitstream buffer containing
624 config CMD_FPGA_LOADFS
625 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
628 Supports loading an FPGA device from a FAT filesystem.
630 config CMD_FPGA_LOADMK
631 bool "fpga loadmk - load bitstream from image"
634 Supports loading an FPGA device from a image generated by mkimage.
636 config CMD_FPGA_LOADP
637 bool "fpga loadp - load partial bitstream"
640 Supports loading an FPGA device from a bitstream buffer containing
644 bool "fpgad - dump FPGA registers"
646 (legacy, needs conversion to driver model)
647 Provides a way to dump FPGA registers by calling the board-specific
648 fpga_get_reg() function. This functions similarly to the 'md'
652 bool "fuse - support for the fuse subssystem"
654 (deprecated - needs conversion to driver model)
655 This allows reading, sensing, programming or overriding fuses
656 which control the behaviour of the device. The command uses the
665 bool "GPT (GUID Partition Table) command"
666 select PARTITION_UUIDS
670 Enable the 'gpt' command to ready and write GPT style partition
674 bool "GPT Random UUID generation"
676 Enable the generation of partitions with random UUIDs if none
679 config CMD_GPT_RENAME
680 bool "GPT partition renaming commands"
683 Enables the 'gpt' command to interchange names on two GPT
684 partitions via the 'gpt swap' command or to rename single
685 partitions via the 'rename' command.
688 bool "ide - Support for IDE drivers"
691 Provides an 'ide' command which allows accessing the IDE drive,
692 reseting the IDE interface, printing the partition table and
693 geting device info. It also enables the 'diskboot' command which
694 permits booting from an IDE drive.
697 bool "io - Support for performing I/O accesses"
699 Provides an 'iod' command to display I/O space and an 'iow' command
700 to write values to the I/O space. This can be useful for manually
701 checking the state of devices during boot when debugging device
705 bool "iotrace - Support for tracing I/O activity"
707 Provides an 'iotrace' command which supports recording I/O reads and
708 writes in a trace buffer in memory . It also maintains a checksum
709 of the trace records (even if space is exhausted) so that the
710 sequence of I/O accesses can be verified.
712 When debugging drivers it is useful to see what I/O accesses were
713 done and in what order.
715 Even if the individual accesses are of little interest it can be
716 useful to verify that the access pattern is consistent each time
717 an operation is performed. In this case a checksum can be used to
718 characterise the operation of a driver. The checksum can be compared
719 across different runs of the operation to verify that the driver is
722 In particular, when performing major refactoring of the driver, where
723 the access pattern should not change, the checksum provides assurance
724 that the refactoring work has not broken the driver.
726 This works by sneaking into the io.h heder for an architecture and
727 redirecting I/O accesses through iotrace's tracing mechanism.
729 For now no commands are provided to examine the trace buffer. The
730 format is fairly simple, so 'md' is a reasonable substitute.
732 Note: The checksum feature is only useful for I/O regions where the
733 contents do not change outside of software control. Where this is not
734 suitable you can fall back to manually comparing the addresses. It
735 might be useful to enhance tracing to only checksum the accesses and
736 not the data read/written.
747 Load a binary file over serial line.
753 Load an S-Record file over serial line
758 MMC memory mapped support.
762 default y if NAND_SUNXI
767 config CMD_NAND_TRIMFFS
768 bool "nand write.trimffs"
769 default y if ARCH_SUNXI
771 Allows one to skip empty pages when flashing something on a NAND.
773 config CMD_NAND_LOCK_UNLOCK
774 bool "nand lock/unlock"
776 NAND locking support.
778 config CMD_NAND_TORTURE
781 NAND torture support.
790 NVM Express device support
793 bool "mmc_spi - Set up MMC SPI device"
795 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
796 Peripheral Interface) device. The device provides a means of
797 accessing an MMC device via SPI using a single data line, limited
798 to 20MHz. It is useful since it reduces the amount of protocol code
802 bool "onenand - access to onenand device"
804 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
805 various useful features. This command allows reading, writing,
806 and erasing blocks. It allso provides a way to show and change
807 bad blocks, and test the device.
811 select PARTITION_UUIDS
813 Read and display information about the partition table on
817 bool "pci - Access PCI devices"
819 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
820 used on some devices to allow the CPU to communicate with its
821 peripherals. Sub-commands allow bus enumeration, displaying and
822 changing configuration space and a few other features.
825 bool "pinit - Set up PCMCIA device"
827 Provides a means to initialise a PCMCIA (Personal Computer Memory
828 Card International Association) device. This is an old standard from
829 about 1990. These devices are typically removable memory or network
830 cards using a standard 68-pin connector.
833 bool "read - Read binary data from a partition"
835 Provides low-level access to the data in a partition.
837 config CMD_REMOTEPROC
839 depends on REMOTEPROC
841 Support for Remote Processor control
844 bool "sata - Access SATA subsystem"
847 SATA (Serial Advanced Technology Attachment) is a serial bus
848 standard for connecting to hard drives and other storage devices.
849 This command provides information about attached devices and allows
850 reading, writing and other operations.
852 SATA replaces PATA (originally just ATA), which stands for Parallel AT
853 Attachment, where AT refers to an IBM AT (Advanced Technology)
854 computer released in 1984.
857 bool "saves - Save a file over serial in S-Record format"
859 Provides a way to save a binary file using the Motorola S-Record
860 format over the serial line.
863 bool "sdram - Print SDRAM configuration information"
865 Provides information about attached SDRAM. This assumed that the
866 SDRAM has an EEPROM with information that can be read using the
867 I2C bus. This is only available on some boards.
875 bool "sf test - Allow testing of SPI flash"
877 Provides a way to test that SPI flash is working correctly. The
878 test is destructive, in that an area of SPI flash must be provided
879 for the test to use. Performance information is also provided,
880 measuring the performance of reading, writing and erasing in
881 Mbps (Million Bits Per Second). This value should approximately
882 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
883 everything is working properly.
891 bool "tsi148 - Command to access tsi148 device"
893 This provides various sub-commands to initialise and configure the
894 Turndra tsi148 device. See the command help for full details.
897 bool "universe - Command to set up the Turndra Universe controller"
899 This allows setting up the VMEbus provided by this controller.
900 See the command help for full details.
909 select USB_FUNCTION_SDP
911 Enables the command "sdp" which is used to have U-Boot emulating the
912 Serial Download Protocol (SDP) via USB.
914 config CMD_USB_MASS_STORAGE
915 bool "UMS usb mass storage"
917 USB mass storage support
922 menu "Shell scripting commands"
934 Return true/false on integer compare.
940 Run script from memory
946 Evaluate boolean and math expressions and store the result in an env
948 Also supports loading the value at a memory location into a variable.
949 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
953 menu "Network commands"
956 bool "bootp, tftpboot"
961 bootp - boot image via network using BOOTP/TFTP protocol
962 tftpboot - boot image via network using TFTP protocol
967 TFTP put command, for uploading files to a server
972 Act as a TFTP server and boot the first received file
977 Boot image via network using RARP/TFTP protocol
982 Boot image via network using DHCP/TFTP protocol
988 Boot image via network using PXE protocol
994 Boot image via network using NFS protocol.
999 Enable MII utility commands.
1004 Send ICMP ECHO_REQUEST to network host
1009 Perform CDP network configuration
1014 Synchronize RTC via network
1019 Lookup the IP of a hostname
1021 config CMD_LINK_LOCAL
1024 Acquire a network IP address using the link-local protocol
1029 Allow control of L2 Ethernet switch commands. These are supported
1030 by the vsc9953 Ethernet driver at present. Sub-commands allow
1031 operations such as enabling / disabling a port and
1032 viewing/maintaining the filtering database (FDB)
1036 menu "Misc commands"
1039 bool "Enable 'bmp' command"
1040 depends on LCD || DM_VIDEO || VIDEO
1042 This provides a way to obtain information about a BMP-format iamge
1043 and to display it. BMP (which presumably stands for BitMaP) is a
1044 file format defined by Microsoft which supports images of various
1045 depths, formats and compression methods. Headers on the file
1046 determine the formats used. This command can be used by first loading
1047 the image into RAM, then using this command to look at it or display
1051 bool "Enable board-specific commands"
1053 (deprecated: instead, please define a Kconfig option for each command)
1055 Some boards have board-specific commands which are only enabled
1056 during developemnt and need to be turned off for production. This
1057 option provides a way to control this. The commands that are enabled
1058 vary depending on the board.
1060 config CMD_BKOPS_ENABLE
1061 bool "mmc bkops enable"
1065 Enable command for setting manual background operations handshake
1066 on a eMMC device. The feature is optionally available on eMMC devices
1067 conforming to standard >= 4.41.
1069 config CMD_BLOCK_CACHE
1070 bool "blkcache - control and stats for block cache"
1071 depends on BLOCK_CACHE
1072 default y if BLOCK_CACHE
1074 Enable the blkcache command, which can be used to control the
1075 operation of the cache functions.
1076 This is most useful when fine-tuning the operation of the cache
1077 during development, but also allows the cache to be disabled when
1078 it might hurt performance (e.g. when using the ums command).
1081 bool "icache or dcache"
1083 Enable the "icache" and "dcache" commands
1086 bool "Enable the 'display' command, for character displays"
1088 (this needs porting to driver model)
1089 This enables the 'display' command which allows a string to be
1090 displayed on a simple board-specific display. Implement
1091 display_putc() to use it.
1097 Enable the 'led' command which allows for control of LEDs supported
1098 by the board. The LEDs can be listed with 'led list' and controlled
1099 with led on/off/togle/blink. Any LED drivers can be controlled with
1100 this command, e.g. led_gpio.
1106 Enable the 'date' command for getting/setting the time/date in RTC
1112 Run commands and summarize execution time.
1115 bool "gettime - read elapsed time"
1117 Enable the 'gettime' command which reads the elapsed time since
1118 U-Boot started running. This shows the time in seconds and
1119 milliseconds. See also the 'bootstage' command which provides more
1120 flexibility for boot timing.
1122 # TODO: rename to CMD_SLEEP
1127 Delay execution for some time
1132 Access the system timer.
1138 This provides basic access to the U-Boot's sound support. The main
1139 feature is to play a beep.
1141 sound init - set up sound system
1142 sound play - play a sound
1148 This provides access to the QEMU firmware interface. The main
1149 feature is to allow easy loading of files passed to qemu-system
1150 via -kernel / -initrd
1152 source "cmd/mvebu/Kconfig"
1155 bool "terminal - provides a way to attach a serial terminal"
1157 Provides a 'cu'-like serial terminal command. This can be used to
1158 access other serial ports from the system console. The terminal
1159 is very simple with no special processing of characters. As with
1160 cu, you can press ~. (tilde followed by period) to exit.
1163 bool "uuid, guid - generation of unique IDs"
1165 This enables two commands:
1167 uuid - generate random Universally Unique Identifier
1168 guid - generate Globally Unique Identifier based on random UUID
1170 The two commands are very similar except for the endianness of the
1175 config CMD_BOOTSTAGE
1176 bool "Enable the 'bootstage' command"
1177 depends on BOOTSTAGE
1179 Add a 'bootstage' command which supports printing a report
1180 and un/stashing of bootstage data.
1182 menu "Power commands"
1184 bool "Enable Driver Model PMIC command"
1187 This is the pmic command, based on a driver model pmic's API.
1188 Command features are unchanged:
1189 - list - list pmic devices
1190 - pmic dev <id> - show or [set] operating pmic device (NEW)
1191 - pmic dump - dump registers
1192 - pmic read address - read byte of register at address
1193 - pmic write address - write byte to register at address
1194 The only one change for this command is 'dev' subcommand.
1196 config CMD_REGULATOR
1197 bool "Enable Driver Model REGULATOR command"
1198 depends on DM_REGULATOR
1200 This command is based on driver model regulator's API.
1201 User interface features:
1202 - list - list regulator devices
1203 - regulator dev <id> - show or [set] operating regulator device
1204 - regulator info - print constraints info
1205 - regulator status - print operating status
1206 - regulator value <val] <-f> - print/[set] voltage value [uV]
1207 - regulator current <val> - print/[set] current value [uA]
1208 - regulator mode <id> - print/[set] operating mode id
1209 - regulator enable - enable the regulator output
1210 - regulator disable - disable the regulator output
1212 The '-f' (force) option can be used for set the value which exceeds
1213 the limits, which are found in device-tree and are kept in regulator's
1214 uclass platdata structure.
1218 menu "Security commands"
1220 bool "Enable the 'aes' command"
1223 This provides a means to encrypt and decrypt data using the AES
1224 (Advanced Encryption Standard). This algorithm uses a symetric key
1225 and is widely used as a streaming cipher. Different key lengths are
1226 supported by the algorithm but this command only supports 128 bits
1230 bool "Enable the 'blob' command"
1232 This is used with the Freescale secure boot mechanism.
1234 Freescale's SEC block has built-in Blob Protocol which provides
1235 a method for protecting user-defined data across system power
1236 cycles. SEC block protects data in a data structure called a Blob,
1237 which provides both confidentiality and integrity protection.
1239 Encapsulating data as a blob
1240 Each time that the Blob Protocol is used to protect data, a
1241 different randomly generated key is used to encrypt the data.
1242 This random key is itself encrypted using a key which is derived
1243 from SoC's non-volatile secret key and a 16 bit Key identifier.
1244 The resulting encrypted key along with encrypted data is called a
1245 blob. The non-volatile secure key is available for use only during
1248 During decapsulation, the reverse process is performed to get back
1252 blob enc - encapsulating data as a cryptgraphic blob
1253 blob dec - decapsulating cryptgraphic blob to get the data
1257 blob enc src dst len km
1259 Encapsulate and create blob of data $len bytes long
1260 at address $src and store the result at address $dst.
1261 $km is the 16 byte key modifier is also required for
1262 generation/use as key for cryptographic operation. Key
1263 modifier should be 16 byte long.
1265 blob dec src dst len km
1267 Decapsulate the blob of data at address $src and
1268 store result of $len byte at addr $dst.
1269 $km is the 16 byte key modifier is also required for
1270 generation/use as key for cryptographic operation. Key
1271 modifier should be 16 byte long.
1274 bool "Support 'hash' command"
1277 This provides a way to hash data in memory using various supported
1278 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1279 saved to memory or to an environment variable. It is also possible
1280 to verify a hash against data in memory.
1286 Add -v option to verify data against a hash.
1289 bool "Enable the 'tpm' command"
1292 This provides a means to talk to a TPM from the command line. A wide
1293 range of commands if provided - see 'tpm help' for details. The
1294 command requires a suitable TPM on your board and the correct driver
1298 bool "Enable the 'tpm test' command"
1301 This provides a a series of tests to confirm that the TPM is working
1302 correctly. The tests cover initialisation, non-volatile RAM, extend,
1303 global lock and checking that timing is within expectations. The
1304 tests pass correctly on Infineon TPMs but may need to be adjusted
1309 menu "Firmware commands"
1311 bool "Enable crosec command"
1315 Enable command-line access to the Chrome OS EC (Embedded
1316 Controller). This provides the 'crosec' command which has
1317 a number of sub-commands for performing EC tasks such as
1318 updating its flash, accessing a small saved context area
1319 and talking to the I2C bus behind the EC (if there is one).
1322 menu "Filesystem commands"
1324 bool "Enable the 'btrsubvol' command"
1327 This enables the 'btrsubvol' command to list subvolumes
1328 of a BTRFS filesystem. There are no special commands for
1329 listing BTRFS directories or loading BTRFS files - this
1330 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1331 when BTRFS is enabled (see FS_BTRFS).
1334 bool "Enable the 'cbfs' command"
1337 Define this to enable support for reading from a Coreboot
1338 filesystem. This is a ROM-based filesystem used for accessing files
1339 on systems that use coreboot as the first boot-loader and then load
1340 U-Boot to actually boot the Operating System. Available commands are
1341 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1344 bool "Enable the 'cramfs' command"
1345 depends on FS_CRAMFS
1347 This provides commands for dealing with CRAMFS (Compressed ROM
1348 filesystem). CRAMFS is useful when space is tight since files are
1349 compressed. Two commands are provided:
1351 cramfsls - lists files in a cramfs image
1352 cramfsload - loads a file from a cramfs image
1355 bool "ext2 command support"
1357 Enables EXT2 FS command
1360 bool "ext4 command support"
1362 Enables EXT4 FS command
1364 config CMD_EXT4_WRITE
1366 bool "ext4 write command support"
1368 Enables EXT4 FS write command
1371 bool "FAT command support"
1374 Support for the FAT fs
1376 config CMD_FS_GENERIC
1377 bool "filesystem commands"
1379 Enables filesystem commands (e.g. load, ls) that work for multiple
1383 bool "fsuuid command"
1385 Enables fsuuid command for filesystem UUID.
1388 bool "jffs2 command"
1391 Enables commands to support the JFFS2 (Journalling Flash File System
1392 version 2) filesystem. This enables fsload, ls and fsinfo which
1393 provide the ability to load files, list directories and obtain
1394 filesystem information.
1397 bool "MTD partition support"
1399 MTD partition support
1401 config MTDIDS_DEFAULT
1402 string "Default MTD IDs"
1403 depends on CMD_MTDPARTS
1405 Defines a default MTD ID
1407 config MTDPARTS_DEFAULT
1408 string "Default MTD partition scheme"
1409 depends on CMD_MTDPARTS
1411 Defines a default MTD partitioning scheme in the Linux MTD command
1412 line partitions format
1414 config CMD_MTDPARTS_SPREAD
1415 bool "Padd partition size to take account of bad blocks"
1416 depends on CMD_MTDPARTS
1418 This enables the 'spread' sub-command of the mtdparts command.
1419 This command will modify the existing mtdparts variable by increasing
1420 the size of the partitions such that 1) each partition's net size is
1421 at least as large as the size specified in the mtdparts variable and
1422 2) each partition starts on a good block.
1425 bool "reiser - Access to reiserfs filesystems"
1427 This provides two commands which operate on a resierfs filesystem,
1428 commonly used some years ago:
1430 reiserls - list files
1431 reiserload - load a file
1434 bool "scsi - Access to SCSI devices"
1437 This provides a 'scsi' command which provides access to SCSI (Small
1438 Computer System Interface) devices. The command provides a way to
1439 scan the bus, reset the bus, read and write data and get information
1443 bool "yaffs2 - Access of YAFFS2 filesystem"
1447 This provides commands for accessing a YAFFS2 filesystem. Yet
1448 Another Flash Filesystem 2 is a filesystem designed specifically
1449 for NAND flash. It incorporates bad-block management and ensures
1450 that device writes are sequential regardless of filesystem
1454 bool "zfs - Access of ZFS filesystem"
1456 This provides commands to accessing a ZFS filesystem, commonly used
1457 on Solaris systems. Two sub-commands are provided:
1459 zfsls - list files in a directory
1460 zfsload - load a file
1462 See doc/README.zfs for more details.
1466 menu "Debug commands"
1471 The bedbug (emBEDded deBUGger) command provides debugging features
1472 for some PowerPC processors. For details please see the
1473 docuemntation in doc/README.beddbug
1476 bool "diag - Board diagnostics"
1478 This command provides access to board diagnostic tests. These are
1479 called Power-on Self Tests (POST). The command allows listing of
1480 available tests and running either all the tests, or specific tests
1484 bool "irq - Show information about interrupts"
1485 depends on !ARM && !MIPS && !SH
1487 This enables two commands:
1489 interrupts - enable or disable interrupts
1490 irqinfo - print device-specific interrupt information
1493 bool "kgdb - Allow debugging of U-Boot with gdb"
1495 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1496 over a serial link for debugging purposes. This allows
1497 single-stepping, inspecting variables, etc. This is supported only
1498 on PowerPC at present.
1501 bool "trace - Support tracing of function calls and timing"
1503 Enables a command to control using of function tracing within
1504 U-Boot. This allows recording of call traces including timing
1505 information. The command can write data to memory for exporting
1506 for analsys (e.g. using bootchart). See doc/README.trace for full
1512 tristate "Enable UBI - Unsorted block images commands"
1516 default y if NAND_SUNXI
1518 UBI is a software layer above MTD layer which admits use of LVM-like
1519 logical volumes on top of MTD devices, hides some complexities of
1520 flash chips like wear and bad blocks and provides some other useful
1521 capabilities. Please, consult the MTD web site for more details
1522 (www.linux-mtd.infradead.org). Activate this option if you want
1523 to use U-Boot UBI commands.
1526 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1530 default y if CMD_UBI
1532 UBIFS is a file system for flash devices which works on top of UBI.
projects / u-boot / blob