1 menu "Command line interface"
7 This option enables the "hush" shell (from Busybox) as command line
8 interpreter, thus enabling powerful command line syntax like
9 if...then...else...fi conditionals or `&&' and '||'
10 constructs ("shell scripts").
12 If disabled, you get the old, much simpler behaviour with a somewhat
13 smaller memory footprint.
15 config SYS_HUSH_PARSER
18 Backward compatibility.
24 This string is displayed in the command line to the left of the
27 menu "Autoboot options"
30 bool "Stop autobooting via specific input key / string"
33 This option enables stopping (aborting) of the automatic
34 boot feature only by issuing a specific input key or
35 string. If not enabled, any input key will abort the
36 U-Boot automatic booting process and bring the device
37 to the U-Boot prompt for user input.
39 config AUTOBOOT_PROMPT
40 string "Autoboot stop prompt"
41 depends on AUTOBOOT_KEYED
42 default "Autoboot in %d seconds\\n"
44 This string is displayed before the boot delay selected by
45 CONFIG_BOOTDELAY starts. If it is not defined there is no
46 output indicating that autoboot is in progress.
48 Note that this define is used as the (only) argument to a
49 printf() call, so it may contain '%' format specifications,
50 provided that it also includes, sepearated by commas exactly
51 like in a printf statement, the required arguments. It is
52 the responsibility of the user to select only such arguments
53 that are valid in the given context.
55 config AUTOBOOT_ENCRYPTION
56 bool "Enable encryption in autoboot stopping"
57 depends on AUTOBOOT_KEYED
60 config AUTOBOOT_DELAY_STR
61 string "Delay autobooting via specific input key / string"
62 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
64 This option delays the automatic boot feature by issuing
65 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
66 or the environment variable "bootdelaykey" is specified
67 and this string is received from console input before
68 autoboot starts booting, U-Boot gives a command prompt. The
69 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
70 used, otherwise it never times out.
72 config AUTOBOOT_STOP_STR
73 string "Stop autobooting via specific input key / string"
74 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
76 This option enables stopping (aborting) of the automatic
77 boot feature only by issuing a specific input key or
78 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
79 variable "bootstopkey" is specified and this string is
80 received from console input before autoboot starts booting,
81 U-Boot gives a command prompt. The U-Boot prompt never
82 times out, even if CONFIG_BOOT_RETRY_TIME is used.
84 config AUTOBOOT_KEYED_CTRLC
85 bool "Enable Ctrl-C autoboot interruption"
86 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
89 This option allows for the boot sequence to be interrupted
90 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
91 Setting this variable provides an escape sequence from the
92 limited "password" strings.
94 config AUTOBOOT_STOP_STR_SHA256
95 string "Stop autobooting via SHA256 encrypted password"
96 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
98 This option adds the feature to only stop the autobooting,
99 and therefore boot into the U-Boot prompt, when the input
100 string / password matches a values that is encypted via
101 a SHA256 hash and saved in the environment.
119 Print console devices and information.
124 Print information about available CPUs. This normally shows the
125 number of CPUs, type (e.g. manufacturer, architecture, product or
126 internal name) and clock frequency. Other information may be
127 available depending on the CPU driver.
132 Print GPL license text
142 Run the command stored in the environment "bootcmd", i.e.
143 "bootd" does the same thing as "run bootcmd".
149 Boot an application image from the memory.
152 bool "bootelf, bootvx"
155 Boot an ELF/vxWorks image from the memory.
161 Start an application at a given address.
167 Run the command in the given environment variable.
173 Print header information for application image.
179 List all images found in flash
185 Extract a part of a multi-image.
189 menu "Environment commands"
207 Edit environment variable.
213 Save all environment variables into the compiled-in persistent
216 config CMD_ENV_EXISTS
220 Check if a variable is defined in the environment for use in
225 menu "Memory commands"
228 bool "md, mm, nm, mw, cp, cmp, base, loop"
233 mm - memory modify (auto-incrementing address)
234 nm - memory modify (constant address)
235 mw - memory write (fill)
238 base - print or set address offset
239 loop - initinite loop on address range
250 Infinite write loop on address range
255 Simple RAM read/write test.
260 mdc - memory display cyclic
261 mwc - memory write cyclic
266 Display memory information.
270 menu "Device access commands"
273 bool "dm - Access to driver model information"
277 Provides access to driver model data structures and information,
278 such as a list of devices, list of uclasses and the state of each
279 device (e.g. activated). This is not required for operation, but
280 can be useful to see the state of driver model for debugging or
284 bool "demo - Demonstration commands for driver model"
287 Provides a 'demo' command which can be used to play around with
288 driver model. To use this properly you will need to enable one or
289 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
290 Otherwise you will always get an empty list of devices. The demo
291 devices are defined in the sandbox device tree, so the easiest
292 option is to use sandbox and pass the -d point to sandbox's
299 Load a binary file over serial line.
305 Load an S-Record file over serial line
308 bool "flinfo, erase, protect"
312 flinfo - print FLASH memory information
314 protect - enable or disable FLASH write protection
317 depends on FLASH_CFI_DRIVER
320 ARM Ltd reference designs flash partition access
356 menu "Shell scripting commands"
368 Return true/false on integer compare.
374 Run script from memory
380 Evaluate boolean and math expressions and store the result in an env
382 Also supports loading the value at a memory location into a variable.
383 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
387 menu "Network commands"
390 bool "bootp, tftpboot"
395 bootp - boot image via network using BOOTP/TFTP protocol
396 tftpboot - boot image via network using TFTP protocol
401 TFTP put command, for uploading files to a server
406 Act as a TFTP server and boot the first received file
411 Boot image via network using RARP/TFTP protocol
416 Boot image via network using DHCP/TFTP protocol
422 Boot image via network using NFS protocol.
427 Send ICMP ECHO_REQUEST to network host
432 Perform CDP network configuration
437 Synchronize RTC via network
442 Lookup the IP of a hostname
444 config CMD_LINK_LOCAL
447 Acquire a network IP address using the link-local protocol
456 Run commands and summarize execution time.
458 # TODO: rename to CMD_SLEEP
463 Delay execution for some time
468 Access the system timer.
471 bool "getdcr, setdcr, getidcr, setidcr"
475 getdcr - Get an AMCC PPC 4xx DCR's value
476 setdcr - Set an AMCC PPC 4xx DCR's value
477 getidcr - Get a register value via indirect DCR addressing
478 setidcr - Set a register value via indirect DCR addressing
484 This provides basic access to the U-Boot's sound support. The main
485 feature is to play a beep.
487 sound init - set up sound system
488 sound play - play a sound
495 bool "Boot timing and reporting"
497 Enable recording of boot time while booting. To use it, insert
498 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
499 bootstage.h. Only a single entry is recorded for each ID. You can
500 give the entry a name with bootstage_mark_name(). You can also
501 record elapsed time in a particular stage using bootstage_start()
502 before starting and bootstage_accum() when finished. Bootstage will
503 add up all the accumated time and report it.
505 Normally, IDs are defined in bootstage.h but a small number of
506 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
509 Calls to show_boot_progress() wil also result in log entries but
510 these will not have names.
512 config BOOTSTAGE_REPORT
513 bool "Display a detailed boot timing report before booting the OS"
516 Enable output of a boot time report just before the OS is booted.
517 This shows how long it took U-Boot to go through each stage of the
518 boot process. The report looks something like this:
520 Timer summary in microseconds:
523 3,575,678 3,575,678 board_init_f start
524 3,575,695 17 arch_cpu_init A9
525 3,575,777 82 arch_cpu_init done
526 3,659,598 83,821 board_init_r start
527 3,910,375 250,777 main_loop
528 29,916,167 26,005,792 bootm_start
529 30,361,327 445,160 start_kernel
531 config BOOTSTAGE_USER_COUNT
532 hex "Number of boot ID numbers available for user use"
535 This is the number of available user bootstage records.
536 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
537 a new ID will be allocated from this stash. If you exceed
538 the limit, recording will stop.
541 bool "Enable the 'bootstage' command"
544 Add a 'bootstage' command which supports printing a report
545 and un/stashing of bootstage data.
548 bool "Store boot timing information in the OS device tree"
551 Stash the bootstage information in the FDT. A root 'bootstage'
552 node is created with each bootstage id as a child. Each child
553 has a 'name' property and either 'mark' containing the
554 mark time in microsecond, or 'accum' containing the
555 accumulated time for that bootstage id in microseconds.
560 name = "board_init_f";
569 Code in the Linux kernel can find this in /proc/devicetree.
571 config BOOTSTAGE_STASH
572 bool "Stash the boot timing information in memory before booting OS"
575 Some OSes do not support device tree. Bootstage can instead write
576 the boot timing information in a binary format at a given address.
577 This happens through a call to bootstage_stash(), typically in
578 the CPU's cleanup_before_linux() function. You can use the
579 'bootstage stash' and 'bootstage unstash' commands to do this on
582 config BOOTSTAGE_STASH_ADDR
583 hex "Address to stash boot timing information"
586 Provide an address which will not be overwritten by the OS when it
587 starts, so that it can read this information when ready.
589 config BOOTSTAGE_STASH_SIZE
590 hex "Size of boot timing stash region"
593 This should be large enough to hold the bootstage stash. A value of
594 4096 (4KiB) is normally plenty.
598 menu "Power commands"
600 bool "Enable Driver Model PMIC command"
603 This is the pmic command, based on a driver model pmic's API.
604 Command features are unchanged:
605 - list - list pmic devices
606 - pmic dev <id> - show or [set] operating pmic device (NEW)
607 - pmic dump - dump registers
608 - pmic read address - read byte of register at address
609 - pmic write address - write byte to register at address
610 The only one change for this command is 'dev' subcommand.
613 bool "Enable Driver Model REGULATOR command"
614 depends on DM_REGULATOR
616 This command is based on driver model regulator's API.
617 User interface features:
618 - list - list regulator devices
619 - regulator dev <id> - show or [set] operating regulator device
620 - regulator info - print constraints info
621 - regulator status - print operating status
622 - regulator value <val] <-f> - print/[set] voltage value [uV]
623 - regulator current <val> - print/[set] current value [uA]
624 - regulator mode <id> - print/[set] operating mode id
625 - regulator enable - enable the regulator output
626 - regulator disable - disable the regulator output
628 The '-f' (force) option can be used for set the value which exceeds
629 the limits, which are found in device-tree and are kept in regulator's
630 uclass platdata structure.
634 menu "Security commands"
636 bool "Enable the 'tpm' command"
639 This provides a means to talk to a TPM from the command line. A wide
640 range of commands if provided - see 'tpm help' for details. The
641 command requires a suitable TPM on your board and the correct driver
645 bool "Enable the 'tpm test' command"
648 This provides a a series of tests to confirm that the TPM is working
649 correctly. The tests cover initialisation, non-volatile RAM, extend,
650 global lock and checking that timing is within expectations. The
651 tests pass correctly on Infineon TPMs but may need to be adjusted