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.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
53 This string is displayed in the command line to the left of the
56 menu "Autoboot options"
62 This enables the autoboot. See doc/README.autoboot for detail.
65 bool "Stop autobooting via specific input key / string"
68 This option enables stopping (aborting) of the automatic
69 boot feature only by issuing a specific input key or
70 string. If not enabled, any input key will abort the
71 U-Boot automatic booting process and bring the device
72 to the U-Boot prompt for user input.
74 config AUTOBOOT_PROMPT
75 string "Autoboot stop prompt"
76 depends on AUTOBOOT_KEYED
77 default "Autoboot in %d seconds\\n"
79 This string is displayed before the boot delay selected by
80 CONFIG_BOOTDELAY starts. If it is not defined there is no
81 output indicating that autoboot is in progress.
83 Note that this define is used as the (only) argument to a
84 printf() call, so it may contain '%' format specifications,
85 provided that it also includes, sepearated by commas exactly
86 like in a printf statement, the required arguments. It is
87 the responsibility of the user to select only such arguments
88 that are valid in the given context.
90 config AUTOBOOT_ENCRYPTION
91 bool "Enable encryption in autoboot stopping"
92 depends on AUTOBOOT_KEYED
95 config AUTOBOOT_DELAY_STR
96 string "Delay autobooting via specific input key / string"
97 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
99 This option delays the automatic boot feature by issuing
100 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
101 or the environment variable "bootdelaykey" is specified
102 and this string is received from console input before
103 autoboot starts booting, U-Boot gives a command prompt. The
104 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
105 used, otherwise it never times out.
107 config AUTOBOOT_STOP_STR
108 string "Stop autobooting via specific input key / string"
109 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
111 This option enables stopping (aborting) of the automatic
112 boot feature only by issuing a specific input key or
113 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
114 variable "bootstopkey" is specified and this string is
115 received from console input before autoboot starts booting,
116 U-Boot gives a command prompt. The U-Boot prompt never
117 times out, even if CONFIG_BOOT_RETRY_TIME is used.
119 config AUTOBOOT_KEYED_CTRLC
120 bool "Enable Ctrl-C autoboot interruption"
121 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
124 This option allows for the boot sequence to be interrupted
125 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
126 Setting this variable provides an escape sequence from the
127 limited "password" strings.
129 config AUTOBOOT_STOP_STR_SHA256
130 string "Stop autobooting via SHA256 encrypted password"
131 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
133 This option adds the feature to only stop the autobooting,
134 and therefore boot into the U-Boot prompt, when the input
135 string / password matches a values that is encypted via
136 a SHA256 hash and saved in the environment.
140 source "cmd/fastboot/Kconfig"
160 Print ".config" contents.
162 If this option is enabled, the ".config" file contents are embedded
163 in the U-Boot image and can be printed on the console by the "config"
164 command. This provides information of which options are enabled on
171 Print console devices and information.
176 Print information about available CPUs. This normally shows the
177 number of CPUs, type (e.g. manufacturer, architecture, product or
178 internal name) and clock frequency. Other information may be
179 available depending on the CPU driver.
185 Print GPL license text
201 Run the command stored in the environment "bootcmd", i.e.
202 "bootd" does the same thing as "run bootcmd".
208 Boot an application image from the memory.
213 Boot the Linux zImage
220 Boot an AArch64 Linux Kernel image from memory.
224 depends on EFI_LOADER
227 Boot an EFI image from memory.
229 config CMD_BOOTEFI_HELLO_COMPILE
230 bool "Compile a standard EFI hello world binary for testing"
231 depends on CMD_BOOTEFI && (ARM || X86)
234 This compiles a standard EFI hello world application with U-Boot so
235 that it can be used with the test/py testing framework. This is useful
236 for testing that EFI is working at a basic level, and for bringing
237 up EFI support on a new architecture.
239 No additional space will be required in the resulting U-Boot binary
240 when this option is enabled.
242 config CMD_BOOTEFI_HELLO
243 bool "Allow booting a standard EFI hello world for testing"
244 depends on CMD_BOOTEFI_HELLO_COMPILE
246 This adds a standard EFI hello world application to U-Boot so that
247 it can be used with the 'bootefi hello' command. This is useful
248 for testing that EFI is working at a basic level, and for bringing
249 up EFI support on a new architecture.
251 source lib/efi_selftest/Kconfig
257 Add an ANSI terminal boot menu command.
260 bool "bootelf, bootvx"
263 Boot an ELF/vxWorks image from the memory.
266 bool "Flattened Device Tree utility commands"
270 Do FDT related setup before booting into the Operating System.
276 Start an application at a given address.
282 Run the command in the given environment variable.
288 Print header information for application image.
293 List all images found in flash
299 Extract a part of a multi-image.
304 Poweroff/Shutdown the system
307 bool "spl export - Export boot information for Falcon boot"
310 Falcon mode allows booting directly from SPL into an Operating
311 System such as Linux, thus skipping U-Boot proper. See
312 doc/README.falcon for full information about how to use this
315 config CMD_SPL_NAND_OFS
316 hex "Offset of OS command line args for Falcon-mode NAND boot"
320 This provides the offset of the command line arguments for Linux
321 when booting from NAND in Falcon mode. See doc/README.falcon
322 for full information about how to use this option (and also see
323 board/gateworks/gw_ventana/README for an example).
325 config CMD_SPL_WRITE_SIZE
326 hex "Size of argument area"
330 This provides the size of the command-line argument area in NAND
331 flash used by Falcon-mode boot. See the documentation until CMD_SPL
335 bool "fitImage update command"
337 Implements the 'fitupd' command, which allows to automatically
338 store software updates present on a TFTP server in NOR Flash
340 config CMD_THOR_DOWNLOAD
341 bool "thor - TIZEN 'thor' download"
343 Implements the 'thor' download protocol. This is a way of
344 downloading a software update over USB from an attached host.
345 There is no documentation about this within the U-Boot source code
346 but you should be able to find something on the interwebs.
349 bool "zboot - x86 boot command"
351 With x86 machines it is common to boot a bzImage file which
352 contains both a kernel and a setup.bin file. The latter includes
353 configuration information from the dark ages which x86 boards still
354 need to pick things out of.
356 Consider using FIT in preference to this since it supports directly
357 booting both 32- and 64-bit kernels, as well as secure boot.
358 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
362 menu "Environment commands"
365 bool "ask for env variable"
367 Ask for environment variable
385 Edit environment variable.
390 Allow for searching environment variables
396 Save all environment variables into the compiled-in persistent
399 config CMD_ENV_EXISTS
403 Check if a variable is defined in the environment for use in
406 config CMD_ENV_CALLBACK
407 bool "env callbacks - print callbacks and their associated variables"
409 Some environment variable have callbacks defined by
410 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
411 For example changing "baudrate" adjust the serial baud rate. This
412 command lists the currently defined callbacks.
415 bool "env flags -print variables that have non-default flags"
417 Some environment variables have special flags that control their
418 behaviour. For example, serial# can only be written once and cannot
419 be deleted. This command shows the variables that have special
424 menu "Memory commands"
437 Add -v option to verify data against a crc32 checksum.
440 bool "eeprom - EEPROM subsystem"
442 (deprecated, needs conversion to driver model)
443 Provides commands to read and write EEPROM (Electrically Erasable
444 Programmable Read Only Memory) chips that are connected over an
447 config CMD_EEPROM_LAYOUT
448 bool "Enable layout-aware eeprom commands"
449 depends on CMD_EEPROM
451 (deprecated, needs conversion to driver model)
452 When enabled, additional eeprom sub-commands become available.
454 eeprom print - prints the contents of the eeprom in a human-readable
455 way (eeprom layout fields, and data formatted to be fit for human
458 eeprom update - allows user to update eeprom fields by specifying
459 the field name, and providing the new data in a human readable format
460 (same format as displayed by the eeprom print command).
462 Both commands can either auto detect the layout, or be told which
466 __weak int parse_layout_version(char *str)
467 - override to provide your own layout name parsing
468 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
470 - override to setup the layout metadata based on the version
471 __weak int eeprom_layout_detect(unsigned char *data)
472 - override to provide your own algorithm for detecting layout
475 - contains various printing and updating functions for common
476 types of eeprom fields. Can be used for defining
479 config EEPROM_LAYOUT_HELP_STRING
480 string "Tells user what layout names are supported"
481 depends on CMD_EEPROM_LAYOUT
482 default "<not defined>"
484 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
490 Infinite write loop on address range
497 Compute MD5 checksum.
502 depends on CMD_MD5SUM
504 Add -v option to verify data against an MD5 checksum.
509 Display memory information.
512 bool "md, mm, nm, mw, cp, cmp, base, loop"
517 mm - memory modify (auto-incrementing address)
518 nm - memory modify (constant address)
519 mw - memory write (fill)
522 base - print or set address offset
523 loop - initialize loop on address range
528 Simple RAM read/write test.
533 mdc - memory display cyclic
534 mwc - memory write cyclic
540 Compute SHA1 checksum.
542 config SHA1SUM_VERIFY
544 depends on CMD_SHA1SUM
546 Add -v option to verify data against a SHA1 checksum.
549 bool "strings - display strings in memory"
551 This works similarly to the Unix 'strings' command except that it
552 works with a memory range. String of printable characters found
553 within the range are displayed. The minimum number of characters
554 for a sequence to be considered a string can be provided.
558 menu "Compression commands"
562 default y if CMD_BOOTI
565 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
570 default y if CMD_BOOTI
572 Uncompress a zip-compressed memory region.
577 Compress a memory region with zlib deflate method.
581 menu "Device access commands"
584 #depends on FLASH_CFI_DRIVER
587 ARM Ltd reference designs flash partition access
590 bool "clk - Show clock frequencies"
593 Shows clock frequences by calling a sock_clk_dump() hook function.
594 This is depreated in favour of using the CLK uclass and accessing
595 clock values from associated drivers. However currently no command
599 bool "demo - Demonstration commands for driver model"
602 Provides a 'demo' command which can be used to play around with
603 driver model. To use this properly you will need to enable one or
604 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
605 Otherwise you will always get an empty list of devices. The demo
606 devices are defined in the sandbox device tree, so the easiest
607 option is to use sandbox and pass the -d point to sandbox's
614 Enables the command "dfu" which is used to have U-Boot create a DFU
615 class device via USB. This command requires that the "dfu_alt_info"
616 environment variable be set and define the alt settings to expose to
620 bool "dm - Access to driver model information"
624 Provides access to driver model data structures and information,
625 such as a list of devices, list of uclasses and the state of each
626 device (e.g. activated). This is not required for operation, but
627 can be useful to see the state of driver model for debugging or
631 bool "fdcboot - Boot from floppy device"
633 The 'fdtboot' command allows booting an image from a floppy disk.
636 bool "flinfo, erase, protect"
640 flinfo - print FLASH memory information
642 protect - enable or disable FLASH write protection
651 config CMD_FPGA_LOADBP
652 bool "fpga loadbp - load partial bitstream (Xilinx only)"
655 Supports loading an FPGA device from a bitstream buffer containing
658 config CMD_FPGA_LOADFS
659 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
662 Supports loading an FPGA device from a FAT filesystem.
664 config CMD_FPGA_LOADMK
665 bool "fpga loadmk - load bitstream from image"
668 Supports loading an FPGA device from a image generated by mkimage.
670 config CMD_FPGA_LOADP
671 bool "fpga loadp - load partial bitstream"
674 Supports loading an FPGA device from a bitstream buffer containing
678 bool "fpgad - dump FPGA registers"
680 (legacy, needs conversion to driver model)
681 Provides a way to dump FPGA registers by calling the board-specific
682 fpga_get_reg() function. This functions similarly to the 'md'
686 bool "fuse - support for the fuse subssystem"
688 (deprecated - needs conversion to driver model)
689 This allows reading, sensing, programming or overriding fuses
690 which control the behaviour of the device. The command uses the
699 bool "GPT (GUID Partition Table) command"
700 select PARTITION_UUIDS
702 select HAVE_BLOCK_DEVICE
705 Enable the 'gpt' command to ready and write GPT style partition
709 bool "GPT Random UUID generation"
712 Enable the generation of partitions with random UUIDs if none
715 config CMD_GPT_RENAME
716 bool "GPT partition renaming commands"
719 Enables the 'gpt' command to interchange names on two GPT
720 partitions via the 'gpt swap' command or to rename single
721 partitions via the 'rename' command.
724 bool "ide - Support for IDE drivers"
727 Provides an 'ide' command which allows accessing the IDE drive,
728 reseting the IDE interface, printing the partition table and
729 geting device info. It also enables the 'diskboot' command which
730 permits booting from an IDE drive.
733 bool "io - Support for performing I/O accesses"
735 Provides an 'iod' command to display I/O space and an 'iow' command
736 to write values to the I/O space. This can be useful for manually
737 checking the state of devices during boot when debugging device
741 bool "iotrace - Support for tracing I/O activity"
743 Provides an 'iotrace' command which supports recording I/O reads and
744 writes in a trace buffer in memory . It also maintains a checksum
745 of the trace records (even if space is exhausted) so that the
746 sequence of I/O accesses can be verified.
748 When debugging drivers it is useful to see what I/O accesses were
749 done and in what order.
751 Even if the individual accesses are of little interest it can be
752 useful to verify that the access pattern is consistent each time
753 an operation is performed. In this case a checksum can be used to
754 characterise the operation of a driver. The checksum can be compared
755 across different runs of the operation to verify that the driver is
758 In particular, when performing major refactoring of the driver, where
759 the access pattern should not change, the checksum provides assurance
760 that the refactoring work has not broken the driver.
762 This works by sneaking into the io.h heder for an architecture and
763 redirecting I/O accesses through iotrace's tracing mechanism.
765 For now no commands are provided to examine the trace buffer. The
766 format is fairly simple, so 'md' is a reasonable substitute.
768 Note: The checksum feature is only useful for I/O regions where the
769 contents do not change outside of software control. Where this is not
770 suitable you can fall back to manually comparing the addresses. It
771 might be useful to enhance tracing to only checksum the accesses and
772 not the data read/written.
783 Load a binary file over serial line.
789 Load an S-Record file over serial line
794 MMC memory mapped support.
798 default y if NAND_SUNXI
803 config CMD_NAND_TRIMFFS
804 bool "nand write.trimffs"
805 default y if ARCH_SUNXI
807 Allows one to skip empty pages when flashing something on a NAND.
809 config CMD_NAND_LOCK_UNLOCK
810 bool "nand lock/unlock"
812 NAND locking support.
814 config CMD_NAND_TORTURE
817 NAND torture support.
826 NVM Express device support
829 bool "mmc_spi - Set up MMC SPI device"
831 Provides a way to set up an MMC (Multimedia Card) SPI (Serial
832 Peripheral Interface) device. The device provides a means of
833 accessing an MMC device via SPI using a single data line, limited
834 to 20MHz. It is useful since it reduces the amount of protocol code
838 bool "onenand - access to onenand device"
840 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
841 various useful features. This command allows reading, writing,
842 and erasing blocks. It allso provides a way to show and change
843 bad blocks, and test the device.
847 select PARTITION_UUIDS
848 select HAVE_BLOCK_DEVICE
850 Read and display information about the partition table on
854 bool "pci - Access PCI devices"
856 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
857 used on some devices to allow the CPU to communicate with its
858 peripherals. Sub-commands allow bus enumeration, displaying and
859 changing configuration space and a few other features.
862 bool "pinit - Set up PCMCIA device"
864 Provides a means to initialise a PCMCIA (Personal Computer Memory
865 Card International Association) device. This is an old standard from
866 about 1990. These devices are typically removable memory or network
867 cards using a standard 68-pin connector.
870 bool "read - Read binary data from a partition"
872 Provides low-level access to the data in a partition.
874 config CMD_REMOTEPROC
876 depends on REMOTEPROC
878 Support for Remote Processor control
881 bool "sata - Access SATA subsystem"
884 SATA (Serial Advanced Technology Attachment) is a serial bus
885 standard for connecting to hard drives and other storage devices.
886 This command provides information about attached devices and allows
887 reading, writing and other operations.
889 SATA replaces PATA (originally just ATA), which stands for Parallel AT
890 Attachment, where AT refers to an IBM AT (Advanced Technology)
891 computer released in 1984.
894 bool "saves - Save a file over serial in S-Record format"
896 Provides a way to save a binary file using the Motorola S-Record
897 format over the serial line.
900 bool "scsi - Access to SCSI devices"
903 This provides a 'scsi' command which provides access to SCSI (Small
904 Computer System Interface) devices. The command provides a way to
905 scan the bus, reset the bus, read and write data and get information
909 bool "sdram - Print SDRAM configuration information"
911 Provides information about attached SDRAM. This assumed that the
912 SDRAM has an EEPROM with information that can be read using the
913 I2C bus. This is only available on some boards.
921 bool "sf test - Allow testing of SPI flash"
923 Provides a way to test that SPI flash is working correctly. The
924 test is destructive, in that an area of SPI flash must be provided
925 for the test to use. Performance information is also provided,
926 measuring the performance of reading, writing and erasing in
927 Mbps (Million Bits Per Second). This value should approximately
928 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
929 everything is working properly.
937 bool "tsi148 - Command to access tsi148 device"
939 This provides various sub-commands to initialise and configure the
940 Turndra tsi148 device. See the command help for full details.
943 bool "universe - Command to set up the Turndra Universe controller"
945 This allows setting up the VMEbus provided by this controller.
946 See the command help for full details.
950 select HAVE_BLOCK_DEVICE
956 select USB_FUNCTION_SDP
958 Enables the command "sdp" which is used to have U-Boot emulating the
959 Serial Download Protocol (SDP) via USB.
962 depends on USB_FUNCTION_ROCKUSB
964 Rockusb protocol is widely used by Rockchip SoC based devices. It can
965 read/write info, image to/from devices. This enable rockusb command
966 support to communication with rockusb device. for more detail about
967 this command, please read doc/README.rockusb.
969 config CMD_USB_MASS_STORAGE
970 bool "UMS usb mass storage"
971 select USB_FUNCTION_MASS_STORAGE
973 USB mass storage support
978 menu "Shell scripting commands"
990 Return true/false on integer compare.
996 Run script from memory
1002 Evaluate boolean and math expressions and store the result in an env
1004 Also supports loading the value at a memory location into a variable.
1005 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1009 menu "Network commands"
1014 bool "bootp, tftpboot"
1018 bootp - boot image via network using BOOTP/TFTP protocol
1019 tftpboot - boot image via network using TFTP protocol
1024 TFTP put command, for uploading files to a server
1029 Act as a TFTP server and boot the first received file
1034 Boot image via network using RARP/TFTP protocol
1040 Boot image via network using DHCP/TFTP protocol
1047 Boot image via network using PXE protocol
1053 Boot image via network using NFS protocol.
1058 Enable MII utility commands.
1063 Send ICMP ECHO_REQUEST to network host
1068 Perform CDP network configuration
1073 Synchronize RTC via network
1078 Lookup the IP of a hostname
1080 config CMD_LINK_LOCAL
1083 Acquire a network IP address using the link-local protocol
1088 Allow control of L2 Ethernet switch commands. These are supported
1089 by the vsc9953 Ethernet driver at present. Sub-commands allow
1090 operations such as enabling / disabling a port and
1091 viewing/maintaining the filtering database (FDB)
1097 menu "Misc commands"
1100 bool "Enable 'bmp' command"
1101 depends on LCD || DM_VIDEO || VIDEO
1103 This provides a way to obtain information about a BMP-format iamge
1104 and to display it. BMP (which presumably stands for BitMaP) is a
1105 file format defined by Microsoft which supports images of various
1106 depths, formats and compression methods. Headers on the file
1107 determine the formats used. This command can be used by first loading
1108 the image into RAM, then using this command to look at it or display
1112 bool "Enable board-specific commands"
1114 (deprecated: instead, please define a Kconfig option for each command)
1116 Some boards have board-specific commands which are only enabled
1117 during developemnt and need to be turned off for production. This
1118 option provides a way to control this. The commands that are enabled
1119 vary depending on the board.
1121 config CMD_BKOPS_ENABLE
1122 bool "mmc bkops enable"
1126 Enable command for setting manual background operations handshake
1127 on a eMMC device. The feature is optionally available on eMMC devices
1128 conforming to standard >= 4.41.
1130 config CMD_BLOCK_CACHE
1131 bool "blkcache - control and stats for block cache"
1132 depends on BLOCK_CACHE
1133 default y if BLOCK_CACHE
1135 Enable the blkcache command, which can be used to control the
1136 operation of the cache functions.
1137 This is most useful when fine-tuning the operation of the cache
1138 during development, but also allows the cache to be disabled when
1139 it might hurt performance (e.g. when using the ums command).
1142 bool "icache or dcache"
1144 Enable the "icache" and "dcache" commands
1147 bool "Enable the 'display' command, for character displays"
1149 (this needs porting to driver model)
1150 This enables the 'display' command which allows a string to be
1151 displayed on a simple board-specific display. Implement
1152 display_putc() to use it.
1158 Enable the 'led' command which allows for control of LEDs supported
1159 by the board. The LEDs can be listed with 'led list' and controlled
1160 with led on/off/togle/blink. Any LED drivers can be controlled with
1161 this command, e.g. led_gpio.
1167 Enable the 'date' command for getting/setting the time/date in RTC
1173 Run commands and summarize execution time.
1176 bool "gettime - read elapsed time"
1178 Enable the 'gettime' command which reads the elapsed time since
1179 U-Boot started running. This shows the time in seconds and
1180 milliseconds. See also the 'bootstage' command which provides more
1181 flexibility for boot timing.
1183 # TODO: rename to CMD_SLEEP
1188 Delay execution for some time
1193 Access the system timer.
1199 This provides basic access to the U-Boot's sound support. The main
1200 feature is to play a beep.
1202 sound init - set up sound system
1203 sound play - play a sound
1209 This provides access to the QEMU firmware interface. The main
1210 feature is to allow easy loading of files passed to qemu-system
1211 via -kernel / -initrd
1213 source "cmd/mvebu/Kconfig"
1216 bool "terminal - provides a way to attach a serial terminal"
1218 Provides a 'cu'-like serial terminal command. This can be used to
1219 access other serial ports from the system console. The terminal
1220 is very simple with no special processing of characters. As with
1221 cu, you can press ~. (tilde followed by period) to exit.
1224 bool "uuid, guid - generation of unique IDs"
1227 This enables two commands:
1229 uuid - generate random Universally Unique Identifier
1230 guid - generate Globally Unique Identifier based on random UUID
1232 The two commands are very similar except for the endianness of the
1237 source "cmd/ti/Kconfig"
1239 config CMD_BOOTSTAGE
1240 bool "Enable the 'bootstage' command"
1241 depends on BOOTSTAGE
1243 Add a 'bootstage' command which supports printing a report
1244 and un/stashing of bootstage data.
1246 menu "Power commands"
1248 bool "Enable Driver Model PMIC command"
1251 This is the pmic command, based on a driver model pmic's API.
1252 Command features are unchanged:
1253 - list - list pmic devices
1254 - pmic dev <id> - show or [set] operating pmic device (NEW)
1255 - pmic dump - dump registers
1256 - pmic read address - read byte of register at address
1257 - pmic write address - write byte to register at address
1258 The only one change for this command is 'dev' subcommand.
1260 config CMD_REGULATOR
1261 bool "Enable Driver Model REGULATOR command"
1262 depends on DM_REGULATOR
1264 This command is based on driver model regulator's API.
1265 User interface features:
1266 - list - list regulator devices
1267 - regulator dev <id> - show or [set] operating regulator device
1268 - regulator info - print constraints info
1269 - regulator status - print operating status
1270 - regulator value <val] <-f> - print/[set] voltage value [uV]
1271 - regulator current <val> - print/[set] current value [uA]
1272 - regulator mode <id> - print/[set] operating mode id
1273 - regulator enable - enable the regulator output
1274 - regulator disable - disable the regulator output
1276 The '-f' (force) option can be used for set the value which exceeds
1277 the limits, which are found in device-tree and are kept in regulator's
1278 uclass platdata structure.
1282 menu "Security commands"
1284 bool "Enable the 'aes' command"
1287 This provides a means to encrypt and decrypt data using the AES
1288 (Advanced Encryption Standard). This algorithm uses a symetric key
1289 and is widely used as a streaming cipher. Different key lengths are
1290 supported by the algorithm but this command only supports 128 bits
1294 bool "Enable the 'blob' command"
1296 This is used with the Freescale secure boot mechanism.
1298 Freescale's SEC block has built-in Blob Protocol which provides
1299 a method for protecting user-defined data across system power
1300 cycles. SEC block protects data in a data structure called a Blob,
1301 which provides both confidentiality and integrity protection.
1303 Encapsulating data as a blob
1304 Each time that the Blob Protocol is used to protect data, a
1305 different randomly generated key is used to encrypt the data.
1306 This random key is itself encrypted using a key which is derived
1307 from SoC's non-volatile secret key and a 16 bit Key identifier.
1308 The resulting encrypted key along with encrypted data is called a
1309 blob. The non-volatile secure key is available for use only during
1312 During decapsulation, the reverse process is performed to get back
1316 blob enc - encapsulating data as a cryptgraphic blob
1317 blob dec - decapsulating cryptgraphic blob to get the data
1321 blob enc src dst len km
1323 Encapsulate and create blob of data $len bytes long
1324 at address $src and store the result at address $dst.
1325 $km is the 16 byte key modifier is also required for
1326 generation/use as key for cryptographic operation. Key
1327 modifier should be 16 byte long.
1329 blob dec src dst len km
1331 Decapsulate the blob of data at address $src and
1332 store result of $len byte at addr $dst.
1333 $km is the 16 byte key modifier is also required for
1334 generation/use as key for cryptographic operation. Key
1335 modifier should be 16 byte long.
1338 bool "Support 'hash' command"
1341 This provides a way to hash data in memory using various supported
1342 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1343 saved to memory or to an environment variable. It is also possible
1344 to verify a hash against data in memory.
1350 Add -v option to verify data against a hash.
1353 bool "Enable the 'tpm' command"
1356 This provides a means to talk to a TPM from the command line. A wide
1357 range of commands if provided - see 'tpm help' for details. The
1358 command requires a suitable TPM on your board and the correct driver
1362 bool "Enable the 'tpm test' command"
1365 This provides a a series of tests to confirm that the TPM is working
1366 correctly. The tests cover initialisation, non-volatile RAM, extend,
1367 global lock and checking that timing is within expectations. The
1368 tests pass correctly on Infineon TPMs but may need to be adjusted
1373 menu "Firmware commands"
1375 bool "Enable crosec command"
1379 Enable command-line access to the Chrome OS EC (Embedded
1380 Controller). This provides the 'crosec' command which has
1381 a number of sub-commands for performing EC tasks such as
1382 updating its flash, accessing a small saved context area
1383 and talking to the I2C bus behind the EC (if there is one).
1386 menu "Filesystem commands"
1388 bool "Enable the 'btrsubvol' command"
1391 This enables the 'btrsubvol' command to list subvolumes
1392 of a BTRFS filesystem. There are no special commands for
1393 listing BTRFS directories or loading BTRFS files - this
1394 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
1395 when BTRFS is enabled (see FS_BTRFS).
1398 bool "Enable the 'cbfs' command"
1401 Define this to enable support for reading from a Coreboot
1402 filesystem. This is a ROM-based filesystem used for accessing files
1403 on systems that use coreboot as the first boot-loader and then load
1404 U-Boot to actually boot the Operating System. Available commands are
1405 cbfsinit, cbfsinfo, cbfsls and cbfsload.
1408 bool "Enable the 'cramfs' command"
1409 depends on FS_CRAMFS
1411 This provides commands for dealing with CRAMFS (Compressed ROM
1412 filesystem). CRAMFS is useful when space is tight since files are
1413 compressed. Two commands are provided:
1415 cramfsls - lists files in a cramfs image
1416 cramfsload - loads a file from a cramfs image
1419 bool "ext2 command support"
1422 Enables EXT2 FS command
1425 bool "ext4 command support"
1428 Enables EXT4 FS command
1430 config CMD_EXT4_WRITE
1432 bool "ext4 write command support"
1435 Enables EXT4 FS write command
1438 bool "FAT command support"
1441 Support for the FAT fs
1443 config CMD_FS_GENERIC
1444 bool "filesystem commands"
1446 Enables filesystem commands (e.g. load, ls) that work for multiple
1450 bool "fsuuid command"
1452 Enables fsuuid command for filesystem UUID.
1455 bool "jffs2 command"
1458 Enables commands to support the JFFS2 (Journalling Flash File System
1459 version 2) filesystem. This enables fsload, ls and fsinfo which
1460 provide the ability to load files, list directories and obtain
1461 filesystem information.
1464 bool "MTD partition support"
1466 MTD partition support
1468 config MTDIDS_DEFAULT
1469 string "Default MTD IDs"
1470 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1472 Defines a default MTD IDs list for use with MTD partitions in the
1473 Linux MTD command line partitions format.
1475 config MTDPARTS_DEFAULT
1476 string "Default MTD partition scheme"
1477 depends on CMD_MTDPARTS || CMD_NAND || CMD_FLASH
1479 Defines a default MTD partitioning scheme in the Linux MTD command
1480 line partitions format
1482 config CMD_MTDPARTS_SPREAD
1483 bool "Padd partition size to take account of bad blocks"
1484 depends on CMD_MTDPARTS
1486 This enables the 'spread' sub-command of the mtdparts command.
1487 This command will modify the existing mtdparts variable by increasing
1488 the size of the partitions such that 1) each partition's net size is
1489 at least as large as the size specified in the mtdparts variable and
1490 2) each partition starts on a good block.
1493 bool "reiser - Access to reiserfs filesystems"
1495 This provides two commands which operate on a resierfs filesystem,
1496 commonly used some years ago:
1498 reiserls - list files
1499 reiserload - load a file
1502 bool "yaffs2 - Access of YAFFS2 filesystem"
1506 This provides commands for accessing a YAFFS2 filesystem. Yet
1507 Another Flash Filesystem 2 is a filesystem designed specifically
1508 for NAND flash. It incorporates bad-block management and ensures
1509 that device writes are sequential regardless of filesystem
1513 bool "zfs - Access of ZFS filesystem"
1515 This provides commands to accessing a ZFS filesystem, commonly used
1516 on Solaris systems. Two sub-commands are provided:
1518 zfsls - list files in a directory
1519 zfsload - load a file
1521 See doc/README.zfs for more details.
1525 menu "Debug commands"
1530 The bedbug (emBEDded deBUGger) command provides debugging features
1531 for some PowerPC processors. For details please see the
1532 docuemntation in doc/README.beddbug
1535 bool "diag - Board diagnostics"
1537 This command provides access to board diagnostic tests. These are
1538 called Power-on Self Tests (POST). The command allows listing of
1539 available tests and running either all the tests, or specific tests
1543 bool "irq - Show information about interrupts"
1544 depends on !ARM && !MIPS && !SH
1546 This enables two commands:
1548 interrupts - enable or disable interrupts
1549 irqinfo - print device-specific interrupt information
1552 bool "kgdb - Allow debugging of U-Boot with gdb"
1554 This enables a 'kgdb' command which allows gdb to connect to U-Boot
1555 over a serial link for debugging purposes. This allows
1556 single-stepping, inspecting variables, etc. This is supported only
1557 on PowerPC at present.
1560 bool "log - Generation, control and access to logging"
1562 This provides access to logging features. It allows the output of
1563 log data to be controlled to a limited extent (setting up the default
1564 maximum log level for emitting of records). It also provides access
1565 to a command used for testing the log system.
1568 bool "trace - Support tracing of function calls and timing"
1570 Enables a command to control using of function tracing within
1571 U-Boot. This allows recording of call traces including timing
1572 information. The command can write data to memory for exporting
1573 for analsys (e.g. using bootchart). See doc/README.trace for full
1579 tristate "Enable UBI - Unsorted block images commands"
1583 default y if NAND_SUNXI
1585 UBI is a software layer above MTD layer which admits use of LVM-like
1586 logical volumes on top of MTD devices, hides some complexities of
1587 flash chips like wear and bad blocks and provides some other useful
1588 capabilities. Please, consult the MTD web site for more details
1589 (www.linux-mtd.infradead.org). Activate this option if you want
1590 to use U-Boot UBI commands.
1593 tristate "Enable UBIFS - Unsorted block images filesystem commands"
1597 default y if CMD_UBI
1599 UBIFS is a file system for flash devices which works on top of UBI.
projects / u-boot / blob