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.
155 Start an application at a given address.
161 Run the command in the given environment variable.
167 Print header information for application image.
173 List all images found in flash
179 Extract a part of a multi-image.
183 menu "Environment commands"
201 Edit environment variable.
207 Save all environment variables into the compiled-in persistent
210 config CMD_ENV_EXISTS
214 Check if a variable is defined in the environment for use in
219 menu "Memory commands"
222 bool "md, mm, nm, mw, cp, cmp, base, loop"
227 mm - memory modify (auto-incrementing address)
228 nm - memory modify (constant address)
229 mw - memory write (fill)
232 base - print or set address offset
233 loop - initinite loop on address range
244 Infinite write loop on address range
249 Simple RAM read/write test.
254 mdc - memory display cyclic
255 mwc - memory write cyclic
260 Display memory information.
264 menu "Device access commands"
267 bool "dm - Access to driver model information"
271 Provides access to driver model data structures and information,
272 such as a list of devices, list of uclasses and the state of each
273 device (e.g. activated). This is not required for operation, but
274 can be useful to see the state of driver model for debugging or
278 bool "demo - Demonstration commands for driver model"
281 Provides a 'demo' command which can be used to play around with
282 driver model. To use this properly you will need to enable one or
283 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
284 Otherwise you will always get an empty list of devices. The demo
285 devices are defined in the sandbox device tree, so the easiest
286 option is to use sandbox and pass the -d point to sandbox's
293 Load a binary file over serial line.
299 Load an S-Record file over serial line
302 bool "flinfo, erase, protect"
306 flinfo - print FLASH memory information
308 protect - enable or disable FLASH write protection
311 depends on FLASH_CFI_DRIVER
314 ARM Ltd reference designs flash partition access
350 menu "Shell scripting commands"
362 Return true/false on integer compare.
368 Run script from memory
374 Evaluate boolean and math expressions and store the result in an env
376 Also supports loading the value at a memory location into a variable.
377 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
381 menu "Network commands"
384 bool "bootp, tftpboot"
389 bootp - boot image via network using BOOTP/TFTP protocol
390 tftpboot - boot image via network using TFTP protocol
395 TFTP put command, for uploading files to a server
400 Act as a TFTP server and boot the first received file
405 Boot image via network using RARP/TFTP protocol
410 Boot image via network using DHCP/TFTP protocol
416 Boot image via network using NFS protocol.
421 Send ICMP ECHO_REQUEST to network host
426 Perform CDP network configuration
431 Synchronize RTC via network
436 Lookup the IP of a hostname
438 config CMD_LINK_LOCAL
441 Acquire a network IP address using the link-local protocol
450 Run commands and summarize execution time.
452 # TODO: rename to CMD_SLEEP
457 Delay execution for some time
462 Access the system timer.
465 bool "getdcr, setdcr, getidcr, setidcr"
469 getdcr - Get an AMCC PPC 4xx DCR's value
470 setdcr - Set an AMCC PPC 4xx DCR's value
471 getidcr - Get a register value via indirect DCR addressing
472 setidcr - Set a register value via indirect DCR addressing
478 This provides basic access to the U-Boot's sound support. The main
479 feature is to play a beep.
481 sound init - set up sound system
482 sound play - play a sound
489 bool "Boot timing and reporting"
491 Enable recording of boot time while booting. To use it, insert
492 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
493 bootstage.h. Only a single entry is recorded for each ID. You can
494 give the entry a name with bootstage_mark_name(). You can also
495 record elapsed time in a particular stage using bootstage_start()
496 before starting and bootstage_accum() when finished. Bootstage will
497 add up all the accumated time and report it.
499 Normally, IDs are defined in bootstage.h but a small number of
500 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
503 Calls to show_boot_progress() wil also result in log entries but
504 these will not have names.
506 config BOOTSTAGE_REPORT
507 bool "Display a detailed boot timing report before booting the OS"
510 Enable output of a boot time report just before the OS is booted.
511 This shows how long it took U-Boot to go through each stage of the
512 boot process. The report looks something like this:
514 Timer summary in microseconds:
517 3,575,678 3,575,678 board_init_f start
518 3,575,695 17 arch_cpu_init A9
519 3,575,777 82 arch_cpu_init done
520 3,659,598 83,821 board_init_r start
521 3,910,375 250,777 main_loop
522 29,916,167 26,005,792 bootm_start
523 30,361,327 445,160 start_kernel
525 config BOOTSTAGE_USER_COUNT
526 hex "Number of boot ID numbers available for user use"
529 This is the number of available user bootstage records.
530 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
531 a new ID will be allocated from this stash. If you exceed
532 the limit, recording will stop.
535 bool "Enable the 'bootstage' command"
538 Add a 'bootstage' command which supports printing a report
539 and un/stashing of bootstage data.
542 bool "Store boot timing information in the OS device tree"
545 Stash the bootstage information in the FDT. A root 'bootstage'
546 node is created with each bootstage id as a child. Each child
547 has a 'name' property and either 'mark' containing the
548 mark time in microsecond, or 'accum' containing the
549 accumulated time for that bootstage id in microseconds.
554 name = "board_init_f";
563 Code in the Linux kernel can find this in /proc/devicetree.
565 config BOOTSTAGE_STASH
566 bool "Stash the boot timing information in memory before booting OS"
569 Some OSes do not support device tree. Bootstage can instead write
570 the boot timing information in a binary format at a given address.
571 This happens through a call to bootstage_stash(), typically in
572 the CPU's cleanup_before_linux() function. You can use the
573 'bootstage stash' and 'bootstage unstash' commands to do this on
576 config BOOTSTAGE_STASH_ADDR
577 hex "Address to stash boot timing information"
580 Provide an address which will not be overwritten by the OS when it
581 starts, so that it can read this information when ready.
583 config BOOTSTAGE_STASH_SIZE
584 hex "Size of boot timing stash region"
587 This should be large enough to hold the bootstage stash. A value of
588 4096 (4KiB) is normally plenty.
592 menu "Power commands"
594 bool "Enable Driver Model PMIC command"
597 This is the pmic command, based on a driver model pmic's API.
598 Command features are unchanged:
599 - list - list pmic devices
600 - pmic dev <id> - show or [set] operating pmic device (NEW)
601 - pmic dump - dump registers
602 - pmic read address - read byte of register at address
603 - pmic write address - write byte to register at address
604 The only one change for this command is 'dev' subcommand.
607 bool "Enable Driver Model REGULATOR command"
608 depends on DM_REGULATOR
610 This command is based on driver model regulator's API.
611 User interface features:
612 - list - list regulator devices
613 - regulator dev <id> - show or [set] operating regulator device
614 - regulator info - print constraints info
615 - regulator status - print operating status
616 - regulator value <val] <-f> - print/[set] voltage value [uV]
617 - regulator current <val> - print/[set] current value [uA]
618 - regulator mode <id> - print/[set] operating mode id
619 - regulator enable - enable the regulator output
620 - regulator disable - disable the regulator output
622 The '-f' (force) option can be used for set the value which exceeds
623 the limits, which are found in device-tree and are kept in regulator's
624 uclass platdata structure.
628 menu "Security commands"
630 bool "Enable the 'tpm' command"
633 This provides a means to talk to a TPM from the command line. A wide
634 range of commands if provided - see 'tpm help' for details. The
635 command requires a suitable TPM on your board and the correct driver
639 bool "Enable the 'tpm test' command"
642 This provides a a series of tests to confirm that the TPM is working
643 correctly. The tests cover initialisation, non-volatile RAM, extend,
644 global lock and checking that timing is within expectations. The
645 tests pass correctly on Infineon TPMs but may need to be adjusted