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.
20 menu "Autoboot options"
23 bool "Stop autobooting via specific input key / string"
26 This option enables stopping (aborting) of the automatic
27 boot feature only by issuing a specific input key or
28 string. If not enabled, any input key will abort the
29 U-Boot automatic booting process and bring the device
30 to the U-Boot prompt for user input.
32 config AUTOBOOT_PROMPT
33 string "Autoboot stop prompt"
34 depends on AUTOBOOT_KEYED
35 default "Autoboot in %d seconds\\n"
37 This string is displayed before the boot delay selected by
38 CONFIG_BOOTDELAY starts. If it is not defined there is no
39 output indicating that autoboot is in progress.
41 Note that this define is used as the (only) argument to a
42 printf() call, so it may contain '%' format specifications,
43 provided that it also includes, sepearated by commas exactly
44 like in a printf statement, the required arguments. It is
45 the responsibility of the user to select only such arguments
46 that are valid in the given context.
48 config AUTOBOOT_ENCRYPTION
49 bool "Enable encryption in autoboot stopping"
50 depends on AUTOBOOT_KEYED
53 config AUTOBOOT_DELAY_STR
54 string "Delay autobooting via specific input key / string"
55 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
57 This option delays the automatic boot feature by issuing
58 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
59 or the environment variable "bootdelaykey" is specified
60 and this string is received from console input before
61 autoboot starts booting, U-Boot gives a command prompt. The
62 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
63 used, otherwise it never times out.
65 config AUTOBOOT_STOP_STR
66 string "Stop autobooting via specific input key / string"
67 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
69 This option enables stopping (aborting) of the automatic
70 boot feature only by issuing a specific input key or
71 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
72 variable "bootstopkey" is specified and this string is
73 received from console input before autoboot starts booting,
74 U-Boot gives a command prompt. The U-Boot prompt never
75 times out, even if CONFIG_BOOT_RETRY_TIME is used.
77 config AUTOBOOT_KEYED_CTRLC
78 bool "Enable Ctrl-C autoboot interruption"
79 depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
82 This option allows for the boot sequence to be interrupted
83 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
84 Setting this variable provides an escape sequence from the
85 limited "password" strings.
87 config AUTOBOOT_STOP_STR_SHA256
88 string "Stop autobooting via SHA256 encrypted password"
89 depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
91 This option adds the feature to only stop the autobooting,
92 and therefore boot into the U-Boot prompt, when the input
93 string / password matches a values that is encypted via
94 a SHA256 hash and saved in the environment.
112 Print console devices and information.
117 Print information about available CPUs. This normally shows the
118 number of CPUs, type (e.g. manufacturer, architecture, product or
119 internal name) and clock frequency. Other information may be
120 available depending on the CPU driver.
125 Print GPL license text
135 Run the command stored in the environment "bootcmd", i.e.
136 "bootd" does the same thing as "run bootcmd".
142 Boot an application image from the memory.
148 Start an application at a given address.
154 Run the command in the given environment variable.
160 Print header information for application image.
166 List all images found in flash
172 Extract a part of a multi-image.
176 menu "Environment commands"
194 Edit environment variable.
200 Save all environment variables into the compiled-in persistent
203 config CMD_ENV_EXISTS
207 Check if a variable is defined in the environment for use in
212 menu "Memory commands"
215 bool "md, mm, nm, mw, cp, cmp, base, loop"
220 mm - memory modify (auto-incrementing address)
221 nm - memory modify (constant address)
222 mw - memory write (fill)
225 base - print or set address offset
226 loop - initinite loop on address range
237 Infinite write loop on address range
242 Simple RAM read/write test.
247 mdc - memory display cyclic
248 mwc - memory write cyclic
253 Display memory information.
257 menu "Device access commands"
260 bool "dm - Access to driver model information"
264 Provides access to driver model data structures and information,
265 such as a list of devices, list of uclasses and the state of each
266 device (e.g. activated). This is not required for operation, but
267 can be useful to see the state of driver model for debugging or
271 bool "demo - Demonstration commands for driver model"
274 Provides a 'demo' command which can be used to play around with
275 driver model. To use this properly you will need to enable one or
276 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
277 Otherwise you will always get an empty list of devices. The demo
278 devices are defined in the sandbox device tree, so the easiest
279 option is to use sandbox and pass the -d point to sandbox's
286 Load a binary file over serial line.
292 Load an S-Record file over serial line
295 bool "flinfo, erase, protect"
299 flinfo - print FLASH memory information
301 protect - enable or disable FLASH write protection
304 depends on FLASH_CFI_DRIVER
307 ARM Ltd reference designs flash partition access
338 menu "Shell scripting commands"
350 Return true/false on integer compare.
356 Run script from memory
362 Evaluate boolean and math expressions and store the result in an env
364 Also supports loading the value at a memory location into a variable.
365 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
369 menu "Network commands"
372 bool "bootp, tftpboot"
377 bootp - boot image via network using BOOTP/TFTP protocol
378 tftpboot - boot image via network using TFTP protocol
383 TFTP put command, for uploading files to a server
388 Act as a TFTP server and boot the first received file
393 Boot image via network using RARP/TFTP protocol
398 Boot image via network using DHCP/TFTP protocol
404 Boot image via network using NFS protocol.
409 Send ICMP ECHO_REQUEST to network host
414 Perform CDP network configuration
419 Synchronize RTC via network
424 Lookup the IP of a hostname
426 config CMD_LINK_LOCAL
429 Acquire a network IP address using the link-local protocol
438 Run commands and summarize execution time.
440 # TODO: rename to CMD_SLEEP
445 Delay execution for some time
450 Access the system timer.
453 bool "getdcr, setdcr, getidcr, setidcr"
457 getdcr - Get an AMCC PPC 4xx DCR's value
458 setdcr - Set an AMCC PPC 4xx DCR's value
459 getidcr - Get a register value via indirect DCR addressing
460 setidcr - Set a register value via indirect DCR addressing
466 This provides basic access to the U-Boot's sound support. The main
467 feature is to play a beep.
469 sound init - set up sound system
470 sound play - play a sound
477 bool "Boot timing and reporting"
479 Enable recording of boot time while booting. To use it, insert
480 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
481 bootstage.h. Only a single entry is recorded for each ID. You can
482 give the entry a name with bootstage_mark_name(). You can also
483 record elapsed time in a particular stage using bootstage_start()
484 before starting and bootstage_accum() when finished. Bootstage will
485 add up all the accumated time and report it.
487 Normally, IDs are defined in bootstage.h but a small number of
488 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
491 Calls to show_boot_progress() wil also result in log entries but
492 these will not have names.
494 config BOOTSTAGE_REPORT
495 bool "Display a detailed boot timing report before booting the OS"
498 Enable output of a boot time report just before the OS is booted.
499 This shows how long it took U-Boot to go through each stage of the
500 boot process. The report looks something like this:
502 Timer summary in microseconds:
505 3,575,678 3,575,678 board_init_f start
506 3,575,695 17 arch_cpu_init A9
507 3,575,777 82 arch_cpu_init done
508 3,659,598 83,821 board_init_r start
509 3,910,375 250,777 main_loop
510 29,916,167 26,005,792 bootm_start
511 30,361,327 445,160 start_kernel
513 config BOOTSTAGE_USER_COUNT
514 hex "Number of boot ID numbers available for user use"
517 This is the number of available user bootstage records.
518 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
519 a new ID will be allocated from this stash. If you exceed
520 the limit, recording will stop.
523 bool "Enable the 'bootstage' command"
526 Add a 'bootstage' command which supports printing a report
527 and un/stashing of bootstage data.
530 bool "Store boot timing information in the OS device tree"
533 Stash the bootstage information in the FDT. A root 'bootstage'
534 node is created with each bootstage id as a child. Each child
535 has a 'name' property and either 'mark' containing the
536 mark time in microsecond, or 'accum' containing the
537 accumulated time for that bootstage id in microseconds.
542 name = "board_init_f";
551 Code in the Linux kernel can find this in /proc/devicetree.
553 config BOOTSTAGE_STASH
554 bool "Stash the boot timing information in memory before booting OS"
557 Some OSes do not support device tree. Bootstage can instead write
558 the boot timing information in a binary format at a given address.
559 This happens through a call to bootstage_stash(), typically in
560 the CPU's cleanup_before_linux() function. You can use the
561 'bootstage stash' and 'bootstage unstash' commands to do this on
564 config BOOTSTAGE_STASH_ADDR
565 hex "Address to stash boot timing information"
568 Provide an address which will not be overwritten by the OS when it
569 starts, so that it can read this information when ready.
571 config BOOTSTAGE_STASH_SIZE
572 hex "Size of boot timing stash region"
575 This should be large enough to hold the bootstage stash. A value of
576 4096 (4KiB) is normally plenty.
580 menu "Power commands"
582 bool "Enable Driver Model PMIC command"
585 This is the pmic command, based on a driver model pmic's API.
586 Command features are unchanged:
587 - list - list pmic devices
588 - pmic dev <id> - show or [set] operating pmic device (NEW)
589 - pmic dump - dump registers
590 - pmic read address - read byte of register at address
591 - pmic write address - write byte to register at address
592 The only one change for this command is 'dev' subcommand.
595 bool "Enable Driver Model REGULATOR command"
596 depends on DM_REGULATOR
598 This command is based on driver model regulator's API.
599 User interface features:
600 - list - list regulator devices
601 - regulator dev <id> - show or [set] operating regulator device
602 - regulator info - print constraints info
603 - regulator status - print operating status
604 - regulator value <val] <-f> - print/[set] voltage value [uV]
605 - regulator current <val> - print/[set] current value [uA]
606 - regulator mode <id> - print/[set] operating mode id
607 - regulator enable - enable the regulator output
608 - regulator disable - disable the regulator output
610 The '-f' (force) option can be used for set the value which exceeds
611 the limits, which are found in device-tree and are kept in regulator's
612 uclass platdata structure.