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"
137 Print ".config" contents.
139 If this option is enabled, the ".config" file contents are embedded
140 in the U-Boot image and can be printed on the console by the "config"
141 command. This provides information of which options are enabled on
148 Print console devices and information.
153 Print information about available CPUs. This normally shows the
154 number of CPUs, type (e.g. manufacturer, architecture, product or
155 internal name) and clock frequency. Other information may be
156 available depending on the CPU driver.
162 Print GPL license text
178 Run the command stored in the environment "bootcmd", i.e.
179 "bootd" does the same thing as "run bootcmd".
185 Boot an application image from the memory.
190 Boot the Linux zImage
197 Boot an AArch64 Linux Kernel image from memory.
201 depends on EFI_LOADER
204 Boot an EFI image from memory.
206 config CMD_BOOTEFI_HELLO_COMPILE
207 bool "Compile a standard EFI hello world binary for testing"
208 depends on CMD_BOOTEFI && (ARM || X86)
211 This compiles a standard EFI hello world application with U-Boot so
212 that it can be used with the test/py testing framework. This is useful
213 for testing that EFI is working at a basic level, and for bringing
214 up EFI support on a new architecture.
216 No additional space will be required in the resulting U-Boot binary
217 when this option is enabled.
219 config CMD_BOOTEFI_HELLO
220 bool "Allow booting a standard EFI hello world for testing"
221 depends on CMD_BOOTEFI_HELLO_COMPILE
223 This adds a standard EFI hello world application to U-Boot so that
224 it can be used with the 'bootefi hello' command. This is useful
225 for testing that EFI is working at a basic level, and for bringing
226 up EFI support on a new architecture.
228 source lib/efi_selftest/Kconfig
234 Add an ANSI terminal boot menu command.
237 bool "bootelf, bootvx"
240 Boot an ELF/vxWorks image from the memory.
243 bool "Flattened Device Tree utility commands"
247 Do FDT related setup before booting into the Operating System.
253 Start an application at a given address.
259 Run the command in the given environment variable.
265 Print header information for application image.
271 List all images found in flash
277 Extract a part of a multi-image.
282 Poweroff/Shutdown the system
285 bool "spl export - Export boot information for Falcon boot"
288 Falcon mode allows booting directly from SPL into an Operating
289 System such as Linux, thus skipping U-Boot proper. See
290 doc/README.falcon for full information about how to use this
293 config CMD_SPL_NAND_OFS
294 hex "Offset of OS command line args for Falcon-mode NAND boot"
298 This provides the offset of the command line arguments for Linux
299 when booting from NAND in Falcon mode. See doc/README.falcon
300 for full information about how to use this option (and also see
301 board/gateworks/gw_ventana/README for an example).
303 config CMD_SPL_WRITE_SIZE
304 hex "Size of argument area"
308 This provides the size of the command-line argument area in NAND
309 flash used by Falcon-mode boot. See the documentation until CMD_SPL
312 config CMD_THOR_DOWNLOAD
313 bool "thor - TIZEN 'thor' download"
315 Implements the 'thor' download protocol. This is a way of
316 downloading a software update over USB from an attached host.
317 There is no documentation about this within the U-Boot source code
318 but you should be able to find something on the interwebs.
321 bool "zboot - x86 boot command"
323 With x86 machines it is common to boot a bzImage file which
324 contains both a kernel and a setup.bin file. The latter includes
325 configuration information from the dark ages which x86 boards still
326 need to pick things out of.
328 Consider using FIT in preference to this since it supports directly
329 booting both 32- and 64-bit kernels, as well as secure boot.
330 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
334 menu "Environment commands"
337 bool "ask for env variable"
339 Ask for environment variable
357 Edit environment variable.
362 Allow for searching environment variables
368 Save all environment variables into the compiled-in persistent
371 config CMD_ENV_EXISTS
375 Check if a variable is defined in the environment for use in
378 config CMD_ENV_CALLBACK
379 bool "env callbacks - print callbacks and their associated variables"
381 Some environment variable have callbacks defined by
382 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
383 For example changing "baudrate" adjust the serial baud rate. This
384 command lists the currently defined callbacks.
387 bool "env flags -print variables that have non-default flags"
389 Some environment variables have special flags that control their
390 behaviour. For example, serial# can only be written once and cannot
391 be deleted. This command shows the variables that have special
396 menu "Memory commands"
409 Add -v option to verify data against a crc32 checksum.
412 bool "eeprom - EEPROM subsystem"
414 (deprecated, needs conversion to driver model)
415 Provides commands to read and write EEPROM (Electrically Erasable
416 Programmable Read Only Memory) chips that are connected over an
419 config CMD_EEPROM_LAYOUT
420 bool "Enable layout-aware eeprom commands"
421 depends on CMD_EEPROM
423 (deprecated, needs conversion to driver model)
424 When enabled, additional eeprom sub-commands become available.
426 eeprom print - prints the contents of the eeprom in a human-readable
427 way (eeprom layout fields, and data formatted to be fit for human
430 eeprom update - allows user to update eeprom fields by specifying
431 the field name, and providing the new data in a human readable format
432 (same format as displayed by the eeprom print command).
434 Both commands can either auto detect the layout, or be told which
438 __weak int parse_layout_version(char *str)
439 - override to provide your own layout name parsing
440 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
442 - override to setup the layout metadata based on the version
443 __weak int eeprom_layout_detect(unsigned char *data)
444 - override to provide your own algorithm for detecting layout
447 - contains various printing and updating functions for common
448 types of eeprom fields. Can be used for defining
451 config EEPROM_LAYOUT_HELP_STRING
452 string "Tells user what layout names are supported"
453 depends on CMD_EEPROM_LAYOUT
454 default "<not defined>"
456 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
462 Infinite write loop on address range
469 Compute MD5 checksum.
474 depends on CMD_MD5SUM
476 Add -v option to verify data against an MD5 checksum.
481 Display memory information.
484 bool "md, mm, nm, mw, cp, cmp, base, loop"
489 mm - memory modify (auto-incrementing address)
490 nm - memory modify (constant address)
491 mw - memory write (fill)
494 base - print or set address offset
495 loop - initialize loop on address range
500 Simple RAM read/write test.
505 mdc - memory display cyclic
506 mwc - memory write cyclic
512 Compute SHA1 checksum.
514 config SHA1SUM_VERIFY
516 depends on CMD_SHA1SUM
518 Add -v option to verify data against a SHA1 checksum.
521 bool "strings - display strings in memory"
523 This works similarly to the Unix 'strings' command except that it
524 works with a memory range. String of printable characters found
525 within the range are displayed. The minimum number of characters
526 for a sequence to be considered a string can be provided.
530 menu "Compression commands"
536 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
542 Uncompress a zip-compressed memory region.
547 Compress a memory region with zlib deflate method.
551 menu "Device access commands"
554 #depends on FLASH_CFI_DRIVER
557 ARM Ltd reference designs flash partition access
560 bool "clk - Show clock frequencies"
563 Shows clock frequences by calling a sock_clk_dump() hook function.
564 This is depreated in favour of using the CLK uclass and accessing
565 clock values from associated drivers. However currently no command
569 bool "demo - Demonstration commands for driver model"
572 Provides a 'demo' command which can be used to play around with
573 driver model. To use this properly you will need to enable one or
574 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
575 Otherwise you will always get an empty list of devices. The demo
576 devices are defined in the sandbox device tree, so the easiest
577 option is to use sandbox and pass the -d point to sandbox's
582 select USB_FUNCTION_DFU
584 Enables the command "dfu" which is used to have U-Boot create a DFU
585 class device via USB. This command requires that the "dfu_alt_info"
586 environment variable be set and define the alt settings to expose to
590 bool "dm - Access to driver model information"
594 Provides access to driver model data structures and information,
595 such as a list of devices, list of uclasses and the state of each
596 device (e.g. activated). This is not required for operation, but
597 can be useful to see the state of driver model for debugging or
601 bool "fdcboot - Boot from floppy device"
603 The 'fdtboot' command allows booting an image from a floppy disk.
606 bool "flinfo, erase, protect"
610 flinfo - print FLASH memory information
612 protect - enable or disable FLASH write protection
620 config CMD_FPGA_LOADBP
621 bool "fpga loadbp - load partial bitstream (Xilinx only)"
624 Supports loading an FPGA device from a bitstream buffer containing
627 config CMD_FPGA_LOADFS
628 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
631 Supports loading an FPGA device from a FAT filesystem.
633 config CMD_FPGA_LOADMK
634 bool "fpga loadmk - load bitstream from image"
637 Supports loading an FPGA device from a image generated by mkimage.
639 config CMD_FPGA_LOADP
640 bool "fpga loadp - load partial bitstream"
643 Supports loading an FPGA device from a bitstream buffer containing
647 bool "fpgad - dump FPGA registers"
649 (legacy, needs conversion to driver model)
650 Provides a way to dump FPGA registers by calling the board-specific
651 fpga_get_reg() function. This functions similarly to the 'md'
655 bool "fuse - support for the fuse subssystem"
657 (deprecated - needs conversion to driver model)
658 This allows reading, sensing, programming or overriding fuses
659 which control the behaviour of the device. The command uses the
668 bool "GPT (GUID Partition Table) command"
669 select PARTITION_UUIDS
673 Enable the 'gpt' command to ready and write GPT style partition
677 bool "GPT Random UUID generation"
679 Enable the generation of partitions with random UUIDs if none
682 config CMD_GPT_RENAME
683 bool "GPT partition renaming commands"
686 Enables the 'gpt' command to interchange names on two GPT
687 partitions via the 'gpt swap' command or to rename single
688 partitions via the 'rename' command.
691 bool "ide - Support for IDE drivers"
694 Provides an 'ide' command which allows accessing the IDE drive,
695 reseting the IDE interface, printing the partition table and
696 geting device info. It also enables the 'diskboot' command which
697 permits booting from an IDE drive.
700 bool "io - Support for performing I/O accesses"
702 Provides an 'iod' command to display I/O space and an 'iow' command
703 to write values to the I/O space. This can be useful for manually
704 checking the state of devices during boot when debugging device
708 bool "iotrace - Support for tracing I/O activity"
710 Provides an 'iotrace' command which supports recording I/O reads and
711 writes in a trace buffer in memory . It also maintains a checksum
712 of the trace records (even if space is exhausted) so that the
713 sequence of I/O accesses can be verified.
715 When debugging drivers it is useful to see what I/O accesses were
716 done and in what order.
718 Even if the individual accesses are of little interest it can be
719 useful to verify that the access pattern is consistent each time
720 an operation is performed. In this case a checksum can be used to
721 characterise the operation of a driver. The checksum can be compared
722 across different runs of the operation to verify that the driver is
725 In particular, when performing major refactoring of the driver, where
726 the access pattern should not change, the checksum provides assurance
727 that the refactoring work has not broken the driver.
729 This works by sneaking into the io.h heder for an architecture and
730 redirecting I/O accesses through iotrace's tracing mechanism.
732 For now no commands are provided to examine the trace buffer. The
733 format is fairly simple, so 'md' is a reasonable substitute.
735 Note: The checksum feature is only useful for I/O regions where the
736 contents do not change outside of software control. Where this is not
737 suitable you can fall back to manually comparing the addresses. It
738 might be useful to enhance tracing to only checksum the accesses and
739 not the data read/written.
750 Load a binary file over serial line.
756 Load an S-Record file over serial line
761 MMC memory mapped support.
765 default y if NAND_SUNXI
770 config CMD_NAND_TRIMFFS
771 bool "nand write.trimffs"
772 default y if ARCH_SUNXI
774 Allows one to skip empty pages when flashing something on a NAND.
776 config CMD_NAND_LOCK_UNLOCK
777 bool "nand lock/unlock"
779 NAND locking support.
781 config CMD_NAND_TORTURE
784 NAND torture support.
793 NVM Express device support
796 bool "mmc_spi - Set up MMC SPI device"
798 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
799 Peripheral Interface) device. The device provides a means of
800 accessing an MMC device via SPI using a single data line, limited
801 to 20MHz. It is useful since it reduces the amount of protocol code
805 bool "onenand - access to onenand device"
807 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
808 various useful features. This command allows reading, writing,
809 and erasing blocks. It allso provides a way to show and change
810 bad blocks, and test the device.
814 select PARTITION_UUIDS
816 Read and display information about the partition table on
820 bool "pci - Access PCI devices"
822 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
823 used on some devices to allow the CPU to communicate with its
824 peripherals. Sub-commands allow bus enumeration, displaying and
825 changing configuration space and a few other features.
828 bool "pinit - Set up PCMCIA device"
830 Provides a means to initialise a PCMCIA (Personal Computer Memory
831 Card International Association) device. This is an old standard from
832 about 1990. These devices are typically removable memory or network
833 cards using a standard 68-pin connector.
836 bool "read - Read binary data from a partition"
838 Provides low-level access to the data in a partition.
840 config CMD_REMOTEPROC
842 depends on REMOTEPROC
844 Support for Remote Processor control
847 bool "sata - Access SATA subsystem"
850 SATA (Serial Advanced Technology Attachment) is a serial bus
851 standard for connecting to hard drives and other storage devices.
852 This command provides information about attached devices and allows
853 reading, writing and other operations.
855 SATA replaces PATA (originally just ATA), which stands for Parallel AT
856 Attachment, where AT refers to an IBM AT (Advanced Technology)
857 computer released in 1984.
860 bool "saves - Save a file over serial in S-Record format"
862 Provides a way to save a binary file using the Motorola S-Record
863 format over the serial line.
866 bool "sdram - Print SDRAM configuration information"
868 Provides information about attached SDRAM. This assumed that the
869 SDRAM has an EEPROM with information that can be read using the
870 I2C bus. This is only available on some boards.
878 bool "sf test - Allow testing of SPI flash"
880 Provides a way to test that SPI flash is working correctly. The
881 test is destructive, in that an area of SPI flash must be provided
882 for the test to use. Performance information is also provided,
883 measuring the performance of reading, writing and erasing in
884 Mbps (Million Bits Per Second). This value should approximately
885 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
886 everything is working properly.
894 bool "tsi148 - Command to access tsi148 device"
896 This provides various sub-commands to initialise and configure the
897 Turndra tsi148 device. See the command help for full details.
900 bool "universe - Command to set up the Turndra Universe controller"
902 This allows setting up the VMEbus provided by this controller.
903 See the command help for full details.
912 select USB_FUNCTION_SDP
914 Enables the command "sdp" which is used to have U-Boot emulating the
915 Serial Download Protocol (SDP) via USB.
917 config CMD_USB_MASS_STORAGE
918 bool "UMS usb mass storage"
920 USB mass storage support
925 menu "Shell scripting commands"
937 Return true/false on integer compare.
943 Run script from memory
949 Evaluate boolean and math expressions and store the result in an env
951 Also supports loading the value at a memory location into a variable.
952 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
956 menu "Network commands"
959 bool "bootp, tftpboot"
964 bootp - boot image via network using BOOTP/TFTP protocol
965 tftpboot - boot image via network using TFTP protocol
970 TFTP put command, for uploading files to a server
975 Act as a TFTP server and boot the first received file
980 Boot image via network using RARP/TFTP protocol
985 Boot image via network using DHCP/TFTP protocol
991 Boot image via network using PXE protocol
997 Boot image via network using NFS protocol.
1002 Enable MII utility commands.
1007 Send ICMP ECHO_REQUEST to network host
1012 Perform CDP network configuration
1017 Synchronize RTC via network
1022 Lookup the IP of a hostname
1024 config CMD_LINK_LOCAL
1027 Acquire a network IP address using the link-local protocol
1032 Allow control of L2 Ethernet switch commands. These are supported
1033 by the vsc9953 Ethernet driver at present. Sub-commands allow
1034 operations such as enabling / disabling a port and
1035 viewing/maintaining the filtering database (FDB)
1039 menu "Misc commands"
1042 bool "Enable 'bmp' command"
1043 depends on LCD || DM_VIDEO || VIDEO
1045 This provides a way to obtain information about a BMP-format iamge
1046 and to display it. BMP (which presumably stands for BitMaP) is a
1047 file format defined by Microsoft which supports images of various
1048 depths, formats and compression methods. Headers on the file
1049 determine the formats used. This command can be used by first loading
1050 the image into RAM, then using this command to look at it or display
1054 bool "Enable board-specific commands"
1056 (deprecated: instead, please define a Kconfig option for each command)
1058 Some boards have board-specific commands which are only enabled
1059 during developemnt and need to be turned off for production. This
1060 option provides a way to control this. The commands that are enabled
1061 vary depending on the board.
1063 config CMD_BKOPS_ENABLE
1064 bool "mmc bkops enable"
1068 Enable command for setting manual background operations handshake
1069 on a eMMC device. The feature is optionally available on eMMC devices
1070 conforming to standard >= 4.41.
1072 config CMD_BLOCK_CACHE
1073 bool "blkcache - control and stats for block cache"
1074 depends on BLOCK_CACHE
1075 default y if BLOCK_CACHE
1077 Enable the blkcache command, which can be used to control the
1078 operation of the cache functions.
1079 This is most useful when fine-tuning the operation of the cache
1080 during development, but also allows the cache to be disabled when
1081 it might hurt performance (e.g. when using the ums command).
1084 bool "icache or dcache"
1086 Enable the "icache" and "dcache" commands
1089 bool "Enable the 'display' command, for character displays"
1091 (this needs porting to driver model)
1092 This enables the 'display' command which allows a string to be
1093 displayed on a simple board-specific display. Implement
1094 display_putc() to use it.
1100 Enable the 'led' command which allows for control of LEDs supported
1101 by the board. The LEDs can be listed with 'led list' and controlled
1102 with led on/off/togle/blink. Any LED drivers can be controlled with
1103 this command, e.g. led_gpio.
1109 Enable the 'date' command for getting/setting the time/date in RTC
1115 Run commands and summarize execution time.
1118 bool "gettime - read elapsed time"
1120 Enable the 'gettime' command which reads the elapsed time since
1121 U-Boot started running. This shows the time in seconds and
1122 milliseconds. See also the 'bootstage' command which provides more
1123 flexibility for boot timing.
1125 # TODO: rename to CMD_SLEEP
1130 Delay execution for some time
1135 Access the system timer.
1141 This provides basic access to the U-Boot's sound support. The main
1142 feature is to play a beep.
1144 sound init - set up sound system
1145 sound play - play a sound
1151 This provides access to the QEMU firmware interface. The main
1152 feature is to allow easy loading of files passed to qemu-system
1153 via -kernel / -initrd
1155 source "cmd/mvebu/Kconfig"
1158 bool "terminal - provides a way to attach a serial terminal"
1160 Provides a 'cu'-like serial terminal command. This can be used to
1161 access other serial ports from the system console. The terminal
1162 is very simple with no special processing of characters. As with
1163 cu, you can press ~. (tilde followed by period) to exit.
1166 bool "uuid, guid - generation of unique IDs"
1168 This enables two commands:
1170 uuid - generate random Universally Unique Identifier
1171 guid - generate Globally Unique Identifier based on random UUID
1173 The two commands are very similar except for the endianness of the
1178 config CMD_BOOTSTAGE
1179 bool "Enable the 'bootstage' command"
1180 depends on BOOTSTAGE
1182 Add a 'bootstage' command which supports printing a report
1183 and un/stashing of bootstage data.
1185 menu "Power commands"
1187 bool "Enable Driver Model PMIC command"
1190 This is the pmic command, based on a driver model pmic's API.
1191 Command features are unchanged:
1192 - list - list pmic devices
1193 - pmic dev <id> - show or [set] operating pmic device (NEW)
1194 - pmic dump - dump registers
1195 - pmic read address - read byte of register at address
1196 - pmic write address - write byte to register at address
1197 The only one change for this command is 'dev' subcommand.
1199 config CMD_REGULATOR
1200 bool "Enable Driver Model REGULATOR command"
1201 depends on DM_REGULATOR
1203 This command is based on driver model regulator's API.
1204 User interface features:
1205 - list - list regulator devices
1206 - regulator dev <id> - show or [set] operating regulator device
1207 - regulator info - print constraints info
1208 - regulator status - print operating status
1209 - regulator value <val] <-f> - print/[set] voltage value [uV]
1210 - regulator current <val> - print/[set] current value [uA]
1211 - regulator mode <id> - print/[set] operating mode id
1212 - regulator enable - enable the regulator output
1213 - regulator disable - disable the regulator output
1215 The '-f' (force) option can be used for set the value which exceeds
1216 the limits, which are found in device-tree and are kept in regulator's
1217 uclass platdata structure.
1221 menu "Security commands"
1223 bool "Enable the 'aes' command"
1226 This provides a means to encrypt and decrypt data using the AES
1227 (Advanced Encryption Standard). This algorithm uses a symetric key
1228 and is widely used as a streaming cipher. Different key lengths are
1229 supported by the algorithm but this command only supports 128 bits
1233 bool "Enable the 'blob' command"
1235 This is used with the Freescale secure boot mechanism.
1237 Freescale's SEC block has built-in Blob Protocol which provides
1238 a method for protecting user-defined data across system power
1239 cycles. SEC block protects data in a data structure called a Blob,
1240 which provides both confidentiality and integrity protection.
1242 Encapsulating data as a blob
1243 Each time that the Blob Protocol is used to protect data, a
1244 different randomly generated key is used to encrypt the data.
1245 This random key is itself encrypted using a key which is derived
1246 from SoC's non-volatile secret key and a 16 bit Key identifier.
1247 The resulting encrypted key along with encrypted data is called a
1248 blob. The non-volatile secure key is available for use only during
1251 During decapsulation, the reverse process is performed to get back
1255 blob enc - encapsulating data as a cryptgraphic blob
1256 blob dec - decapsulating cryptgraphic blob to get the data
1260 blob enc src dst len km
1262 Encapsulate and create blob of data $len bytes long
1263 at address $src and store the result at address $dst.
1264 $km is the 16 byte key modifier is also required for
1265 generation/use as key for cryptographic operation. Key
1266 modifier should be 16 byte long.
1268 blob dec src dst len km
1270 Decapsulate the blob of data at address $src and
1271 store result of $len byte at addr $dst.
1272 $km is the 16 byte key modifier is also required for
1273 generation/use as key for cryptographic operation. Key
1274 modifier should be 16 byte long.
1277 bool "Support 'hash' command"
1280 This provides a way to hash data in memory using various supported
1281 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1282 saved to memory or to an environment variable. It is also possible
1283 to verify a hash against data in memory.
1289 Add -v option to verify data against a hash.
1292 bool "Enable the 'tpm' command"
1295 This provides a means to talk to a TPM from the command line. A wide
1296 range of commands if provided - see 'tpm help' for details. The
1297 command requires a suitable TPM on your board and the correct driver
1301 bool "Enable the 'tpm test' command"
1304 This provides a a series of tests to confirm that the TPM is working
1305 correctly. The tests cover initialisation, non-volatile RAM, extend,
1306 global lock and checking that timing is within expectations. The
1307 tests pass correctly on Infineon TPMs but may need to be adjusted
1312 menu "Firmware commands"
1314 bool "Enable crosec command"
1318 Enable command-line access to the Chrome OS EC (Embedded
1319 Controller). This provides the 'crosec' command which has
1320 a number of sub-commands for performing EC tasks such as
1321 updating its flash, accessing a small saved context area
1322 and talking to the I2C bus behind the EC (if there is one).
1325 menu "Filesystem commands"
1327 bool "Enable the 'btrsubvol' command"
1330 This enables the 'btrsubvol' command to list subvolumes
1331 of a BTRFS filesystem. There are no special commands for
1332 listing BTRFS directories or loading BTRFS files - this
1333 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1334 when BTRFS is enabled (see FS_BTRFS).
1337 bool "Enable the 'cbfs' command"
1340 Define this to enable support for reading from a Coreboot
1341 filesystem. This is a ROM-based filesystem used for accessing files
1342 on systems that use coreboot as the first boot-loader and then load
1343 U-Boot to actually boot the Operating System. Available commands are
1344 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1347 bool "Enable the 'cramfs' command"
1348 depends on FS_CRAMFS
1350 This provides commands for dealing with CRAMFS (Compressed ROM
1351 filesystem). CRAMFS is useful when space is tight since files are
1352 compressed. Two commands are provided:
1354 cramfsls - lists files in a cramfs image
1355 cramfsload - loads a file from a cramfs image
1358 bool "ext2 command support"
1360 Enables EXT2 FS command
1363 bool "ext4 command support"
1365 Enables EXT4 FS command
1367 config CMD_EXT4_WRITE
1369 bool "ext4 write command support"
1371 Enables EXT4 FS write command
1374 bool "FAT command support"
1377 Support for the FAT fs
1379 config CMD_FS_GENERIC
1380 bool "filesystem commands"
1382 Enables filesystem commands (e.g. load, ls) that work for multiple
1386 bool "fsuuid command"
1388 Enables fsuuid command for filesystem UUID.
1391 bool "jffs2 command"
1394 Enables commands to support the JFFS2 (Journalling Flash File System
1395 version 2) filesystem. This enables fsload, ls and fsinfo which
1396 provide the ability to load files, list directories and obtain
1397 filesystem information.
1400 bool "MTD partition support"
1402 MTD partition support
1404 config MTDIDS_DEFAULT
1405 string "Default MTD IDs"
1406 depends on CMD_MTDPARTS
1408 Defines a default MTD ID
1410 config MTDPARTS_DEFAULT
1411 string "Default MTD partition scheme"
1412 depends on CMD_MTDPARTS
1414 Defines a default MTD partitioning scheme in the Linux MTD command
1415 line partitions format
1417 config CMD_MTDPARTS_SPREAD
1418 bool "Padd partition size to take account of bad blocks"
1419 depends on CMD_MTDPARTS
1421 This enables the 'spread' sub-command of the mtdparts command.
1422 This command will modify the existing mtdparts variable by increasing
1423 the size of the partitions such that 1) each partition's net size is
1424 at least as large as the size specified in the mtdparts variable and
1425 2) each partition starts on a good block.
1428 bool "reiser - Access to reiserfs filesystems"
1430 This provides two commands which operate on a resierfs filesystem,
1431 commonly used some years ago:
1433 reiserls - list files
1434 reiserload - load a file
1437 bool "scsi - Access to SCSI devices"
1440 This provides a 'scsi' command which provides access to SCSI (Small
1441 Computer System Interface) devices. The command provides a way to
1442 scan the bus, reset the bus, read and write data and get information
1446 bool "yaffs2 - Access of YAFFS2 filesystem"
1450 This provides commands for accessing a YAFFS2 filesystem. Yet
1451 Another Flash Filesystem 2 is a filesystem designed specifically
1452 for NAND flash. It incorporates bad-block management and ensures
1453 that device writes are sequential regardless of filesystem
1457 bool "zfs - Access of ZFS filesystem"
1459 This provides commands to accessing a ZFS filesystem, commonly used
1460 on Solaris systems. Two sub-commands are provided:
1462 zfsls - list files in a directory
1463 zfsload - load a file
1465 See doc/README.zfs for more details.
1469 menu "Debug commands"
1474 The bedbug (emBEDded deBUGger) command provides debugging features
1475 for some PowerPC processors. For details please see the
1476 docuemntation in doc/README.beddbug
1479 bool "diag - Board diagnostics"
1481 This command provides access to board diagnostic tests. These are
1482 called Power-on Self Tests (POST). The command allows listing of
1483 available tests and running either all the tests, or specific tests
1487 bool "irq - Show information about interrupts"
1488 depends on !ARM && !MIPS && !SH
1490 This enables two commands:
1492 interrupts - enable or disable interrupts
1493 irqinfo - print device-specific interrupt information
1496 bool "kgdb - Allow debugging of U-Boot with gdb"
1498 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1499 over a serial link for debugging purposes. This allows
1500 single-stepping, inspecting variables, etc. This is supported only
1501 on PowerPC at present.
1504 bool "trace - Support tracing of function calls and timing"
1506 Enables a command to control using of function tracing within
1507 U-Boot. This allows recording of call traces including timing
1508 information. The command can write data to memory for exporting
1509 for analsys (e.g. using bootchart). See doc/README.trace for full
1515 tristate "Enable UBI - Unsorted block images commands"
1519 default y if NAND_SUNXI
1521 UBI is a software layer above MTD layer which admits use of LVM-like
1522 logical volumes on top of MTD devices, hides some complexities of
1523 flash chips like wear and bad blocks and provides some other useful
1524 capabilities. Please, consult the MTD web site for more details
1525 (www.linux-mtd.infradead.org). Activate this option if you want
1526 to use U-Boot UBI commands.
1529 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1533 default y if CMD_UBI
1535 UBIFS is a file system for flash devices which works on top of UBI.
projects / J-u-boot.git / blob