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"
133 Print console devices and information.
138 Print information about available CPUs. This normally shows the
139 number of CPUs, type (e.g. manufacturer, architecture, product or
140 internal name) and clock frequency. Other information may be
141 available depending on the CPU driver.
146 Print GPL license text
156 Run the command stored in the environment "bootcmd", i.e.
157 "bootd" does the same thing as "run bootcmd".
163 Boot an application image from the memory.
168 Boot the Linux zImage
175 Boot an AArch64 Linux Kernel image from memory.
179 depends on EFI_LOADER
182 Boot an EFI image from memory.
184 config CMD_BOOTEFI_HELLO_COMPILE
185 bool "Compile a standard EFI hello world binary for testing"
186 depends on CMD_BOOTEFI && (ARM || X86)
189 This compiles a standard EFI hello world application with U-Boot so
190 that it can be used with the test/py testing framework. This is useful
191 for testing that EFI is working at a basic level, and for bringing
192 up EFI support on a new architecture.
194 No additional space will be required in the resulting U-Boot binary
195 when this option is enabled.
197 config CMD_BOOTEFI_HELLO
198 bool "Allow booting a standard EFI hello world for testing"
199 depends on CMD_BOOTEFI_HELLO_COMPILE
201 This adds a standard EFI hello world application to U-Boot so that
202 it can be used with the 'bootefi hello' command. This is useful
203 for testing that EFI is working at a basic level, and for bringing
204 up EFI support on a new architecture.
207 bool "bootelf, bootvx"
210 Boot an ELF/vxWorks image from the memory.
213 bool "Flattened Device Tree utility commands"
217 Do FDT related setup before booting into the Operating System.
223 Start an application at a given address.
229 Run the command in the given environment variable.
235 Print header information for application image.
241 List all images found in flash
247 Extract a part of a multi-image.
254 menu "Environment commands"
257 bool "ask for env variable"
259 Ask for environment variable
277 Edit environment variable.
282 Allow for searching environment variables
288 Save all environment variables into the compiled-in persistent
291 config CMD_ENV_EXISTS
295 Check if a variable is defined in the environment for use in
300 menu "Memory commands"
303 bool "md, mm, nm, mw, cp, cmp, base, loop"
308 mm - memory modify (auto-incrementing address)
309 nm - memory modify (constant address)
310 mw - memory write (fill)
313 base - print or set address offset
314 loop - initinite loop on address range
325 Infinite write loop on address range
330 Simple RAM read/write test.
335 mdc - memory display cyclic
336 mwc - memory write cyclic
341 Display memory information.
345 menu "Device access commands"
348 bool "dm - Access to driver model information"
352 Provides access to driver model data structures and information,
353 such as a list of devices, list of uclasses and the state of each
354 device (e.g. activated). This is not required for operation, but
355 can be useful to see the state of driver model for debugging or
359 bool "demo - Demonstration commands for driver model"
362 Provides a 'demo' command which can be used to play around with
363 driver model. To use this properly you will need to enable one or
364 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
365 Otherwise you will always get an empty list of devices. The demo
366 devices are defined in the sandbox device tree, so the easiest
367 option is to use sandbox and pass the -d point to sandbox's
374 Load a binary file over serial line.
380 Load an S-Record file over serial line
383 bool "flinfo, erase, protect"
387 flinfo - print FLASH memory information
389 protect - enable or disable FLASH write protection
392 #depends on FLASH_CFI_DRIVER
395 ARM Ltd reference designs flash partition access
400 MMC memory mapped support.
429 select USB_FUNCTION_DFU
431 Enables the command "dfu" which is used to have U-Boot create a DFU
432 class device via USB.
434 config CMD_USB_MASS_STORAGE
435 bool "UMS usb mass storage"
437 USB mass storage support
445 config CMD_REMOTEPROC
447 depends on REMOTEPROC
449 Support for Remote Processor control
459 menu "Shell scripting commands"
471 Return true/false on integer compare.
477 Run script from memory
483 Evaluate boolean and math expressions and store the result in an env
485 Also supports loading the value at a memory location into a variable.
486 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
490 menu "Network commands"
493 bool "bootp, tftpboot"
498 bootp - boot image via network using BOOTP/TFTP protocol
499 tftpboot - boot image via network using TFTP protocol
504 TFTP put command, for uploading files to a server
509 Act as a TFTP server and boot the first received file
514 Boot image via network using RARP/TFTP protocol
519 Boot image via network using DHCP/TFTP protocol
525 Boot image via network using NFS protocol.
530 Enable MII utility commands.
535 Send ICMP ECHO_REQUEST to network host
540 Perform CDP network configuration
545 Synchronize RTC via network
550 Lookup the IP of a hostname
552 config CMD_LINK_LOCAL
555 Acquire a network IP address using the link-local protocol
566 Lists AMBA Plug-n-Play information.
568 config SYS_AMBAPP_PRINT_ON_STARTUP
569 bool "Show AMBA PnP info on startup"
570 depends on CMD_AMBAPP
573 Show AMBA Plug-n-Play information on startup.
575 config CMD_BLOCK_CACHE
576 bool "blkcache - control and stats for block cache"
577 depends on BLOCK_CACHE
578 default y if BLOCK_CACHE
580 Enable the blkcache command, which can be used to control the
581 operation of the cache functions.
582 This is most useful when fine-tuning the operation of the cache
583 during development, but also allows the cache to be disabled when
584 it might hurt performance (e.g. when using the ums command).
587 bool "icache or dcache"
589 Enable the "icache" and "dcache" commands
594 Run commands and summarize execution time.
596 # TODO: rename to CMD_SLEEP
601 Delay execution for some time
606 Access the system timer.
609 bool "getdcr, setdcr, getidcr, setidcr"
613 getdcr - Get an AMCC PPC 4xx DCR's value
614 setdcr - Set an AMCC PPC 4xx DCR's value
615 getidcr - Get a register value via indirect DCR addressing
616 setidcr - Set a register value via indirect DCR addressing
622 This provides basic access to the U-Boot's sound support. The main
623 feature is to play a beep.
625 sound init - set up sound system
626 sound play - play a sound
632 This provides access to the QEMU firmware interface. The main
633 feature is to allow easy loading of files passed to qemu-system
634 via -kernel / -initrd
638 bool "Enable the 'bootstage' command"
641 Add a 'bootstage' command which supports printing a report
642 and un/stashing of bootstage data.
644 menu "Power commands"
646 bool "Enable Driver Model PMIC command"
649 This is the pmic command, based on a driver model pmic's API.
650 Command features are unchanged:
651 - list - list pmic devices
652 - pmic dev <id> - show or [set] operating pmic device (NEW)
653 - pmic dump - dump registers
654 - pmic read address - read byte of register at address
655 - pmic write address - write byte to register at address
656 The only one change for this command is 'dev' subcommand.
659 bool "Enable Driver Model REGULATOR command"
660 depends on DM_REGULATOR
662 This command is based on driver model regulator's API.
663 User interface features:
664 - list - list regulator devices
665 - regulator dev <id> - show or [set] operating regulator device
666 - regulator info - print constraints info
667 - regulator status - print operating status
668 - regulator value <val] <-f> - print/[set] voltage value [uV]
669 - regulator current <val> - print/[set] current value [uA]
670 - regulator mode <id> - print/[set] operating mode id
671 - regulator enable - enable the regulator output
672 - regulator disable - disable the regulator output
674 The '-f' (force) option can be used for set the value which exceeds
675 the limits, which are found in device-tree and are kept in regulator's
676 uclass platdata structure.
680 menu "Security commands"
682 bool "Enable the 'tpm' command"
685 This provides a means to talk to a TPM from the command line. A wide
686 range of commands if provided - see 'tpm help' for details. The
687 command requires a suitable TPM on your board and the correct driver
691 bool "Enable the 'tpm test' command"
694 This provides a a series of tests to confirm that the TPM is working
695 correctly. The tests cover initialisation, non-volatile RAM, extend,
696 global lock and checking that timing is within expectations. The
697 tests pass correctly on Infineon TPMs but may need to be adjusted
702 menu "Firmware commands"
704 bool "Enable crosec command"
708 Enable command-line access to the Chrome OS EC (Embedded
709 Controller). This provides the 'crosec' command which has
710 a number of sub-commands for performing EC tasks such as
711 updating its flash, accessing a small saved context area
712 and talking to the I2C bus behind the EC (if there is one).
715 menu "Filesystem commands"
717 bool "ext2 command support"
719 Enables EXT2 FS command
722 bool "ext4 command support"
724 Enables EXT4 FS command
726 config CMD_EXT4_WRITE
728 bool "ext4 write command support"
730 Enables EXT4 FS write command
733 bool "FAT command support"
735 Support for the FAT fs
737 config CMD_FS_GENERIC
738 bool "filesystem commands"
740 Enables filesystem commands (e.g. load, ls) that work for multiple
745 tristate "Enable UBI - Unsorted block images commands"
749 UBI is a software layer above MTD layer which admits use of LVM-like
750 logical volumes on top of MTD devices, hides some complexities of
751 flash chips like wear and bad blocks and provides some other useful
752 capabilities. Please, consult the MTD web site for more details
753 (www.linux-mtd.infradead.org). Activate this option if you want
754 to use U-Boot UBI commands.