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.
110 Print console devices and information.
115 Print information about available CPUs. This normally shows the
116 number of CPUs, type (e.g. manufacturer, architecture, product or
117 internal name) and clock frequency. Other information may be
118 available depending on the CPU driver.
123 Print GPL license text
132 Run the command stored in the environment "bootcmd", i.e.
133 "bootd" does the same thing as "run bootcmd".
139 Boot an application image from the memory.
145 Start an application at a given address.
150 Run the command in the given environment variable.
155 Print header information for application image.
160 List all images found in flash
165 Extract a part of a multi-image.
169 menu "Environment commands"
186 Edit environment variable.
191 Save all environment variables into the compiled-in persistent
194 config CMD_ENV_EXISTS
197 Check if a variable is defined in the environment for use in
202 menu "Memory commands"
205 bool "md, mm, nm, mw, cp, cmp, base, loop"
209 mm - memory modify (auto-incrementing address)
210 nm - memory modify (constant address)
211 mw - memory write (fill)
214 base - print or set address offset
215 loop - initinite loop on address range
226 Infinite write loop on address range
231 Simple RAM read/write test.
236 mdc - memory display cyclic
237 mwc - memory write cyclic
242 Display memory information.
246 menu "Device access commands"
249 bool "dm - Access to driver model information"
253 Provides access to driver model data structures and information,
254 such as a list of devices, list of uclasses and the state of each
255 device (e.g. activated). This is not required for operation, but
256 can be useful to see the state of driver model for debugging or
260 bool "demo - Demonstration commands for driver model"
263 Provides a 'demo' command which can be used to play around with
264 driver model. To use this properly you will need to enable one or
265 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
266 Otherwise you will always get an empty list of devices. The demo
267 devices are defined in the sandbox device tree, so the easiest
268 option is to use sandbox and pass the -d point to sandbox's
274 Load a binary file over serial line.
279 Load an S-Record file over serial line
282 bool "flinfo, erase, protect"
285 flinfo - print FLASH memory information
287 protect - enable or disable FLASH write protection
290 depends on FLASH_CFI_DRIVER
293 ARM Ltd reference designs flash partition access
323 menu "Shell scripting commands"
333 Return true/false on integer compare.
338 Run script from memory
343 Evaluate boolean and math expressions and store the result in an env
345 Also supports loading the value at a memory location into a variable.
346 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
350 menu "Network commands"
353 bool "bootp, tftpboot"
357 bootp - boot image via network using BOOTP/TFTP protocol
358 tftpboot - boot image via network using TFTP protocol
363 TFTP put command, for uploading files to a server
368 Act as a TFTP server and boot the first received file
373 Boot image via network using RARP/TFTP protocol
378 Boot image via network using DHCP/TFTP protocol
383 Boot image via network using NFS protocol.
388 Send ICMP ECHO_REQUEST to network host
393 Perform CDP network configuration
398 Synchronize RTC via network
403 Lookup the IP of a hostname
405 config CMD_LINK_LOCAL
408 Acquire a network IP address using the link-local protocol
417 Run commands and summarize execution time.
419 # TODO: rename to CMD_SLEEP
423 Delay execution for some time
428 Access the system timer.
431 bool "getdcr, setdcr, getidcr, setidcr"
434 getdcr - Get an AMCC PPC 4xx DCR's value
435 setdcr - Set an AMCC PPC 4xx DCR's value
436 getidcr - Get a register value via indirect DCR addressing
437 setidcr - Set a register value via indirect DCR addressing
443 This provides basic access to the U-Boot's sound support. The main
444 feature is to play a beep.
446 sound init - set up sound system
447 sound play - play a sound
454 bool "Boot timing and reporting"
456 Enable recording of boot time while booting. To use it, insert
457 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
458 bootstage.h. Only a single entry is recorded for each ID. You can
459 give the entry a name with bootstage_mark_name(). You can also
460 record elapsed time in a particular stage using bootstage_start()
461 before starting and bootstage_accum() when finished. Bootstage will
462 add up all the accumated time and report it.
464 Normally, IDs are defined in bootstage.h but a small number of
465 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
468 Calls to show_boot_progress() wil also result in log entries but
469 these will not have names.
471 config BOOTSTAGE_REPORT
472 bool "Display a detailed boot timing report before booting the OS"
475 Enable output of a boot time report just before the OS is booted.
476 This shows how long it took U-Boot to go through each stage of the
477 boot process. The report looks something like this:
479 Timer summary in microseconds:
482 3,575,678 3,575,678 board_init_f start
483 3,575,695 17 arch_cpu_init A9
484 3,575,777 82 arch_cpu_init done
485 3,659,598 83,821 board_init_r start
486 3,910,375 250,777 main_loop
487 29,916,167 26,005,792 bootm_start
488 30,361,327 445,160 start_kernel
490 config BOOTSTAGE_USER_COUNT
491 hex "Number of boot ID numbers available for user use"
494 This is the number of available user bootstage records.
495 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
496 a new ID will be allocated from this stash. If you exceed
497 the limit, recording will stop.
500 bool "Enable the 'bootstage' command"
503 Add a 'bootstage' command which supports printing a report
504 and un/stashing of bootstage data.
507 bool "Store boot timing information in the OS device tree"
510 Stash the bootstage information in the FDT. A root 'bootstage'
511 node is created with each bootstage id as a child. Each child
512 has a 'name' property and either 'mark' containing the
513 mark time in microsecond, or 'accum' containing the
514 accumulated time for that bootstage id in microseconds.
519 name = "board_init_f";
528 Code in the Linux kernel can find this in /proc/devicetree.
530 config BOOTSTAGE_STASH
531 bool "Stash the boot timing information in memory before booting OS"
534 Some OSes do not support device tree. Bootstage can instead write
535 the boot timing information in a binary format at a given address.
536 This happens through a call to bootstage_stash(), typically in
537 the CPU's cleanup_before_linux() function. You can use the
538 'bootstage stash' and 'bootstage unstash' commands to do this on
541 config BOOTSTAGE_STASH_ADDR
542 hex "Address to stash boot timing information"
545 Provide an address which will not be overwritten by the OS when it
546 starts, so that it can read this information when ready.
548 config BOOTSTAGE_STASH_SIZE
549 hex "Size of boot timing stash region"
552 This should be large enough to hold the bootstage stash. A value of
553 4096 (4KiB) is normally plenty.
557 menu "Power commands"
559 bool "Enable Driver Model PMIC command"
562 This is the pmic command, based on a driver model pmic's API.
563 Command features are unchanged:
564 - list - list pmic devices
565 - pmic dev <id> - show or [set] operating pmic device (NEW)
566 - pmic dump - dump registers
567 - pmic read address - read byte of register at address
568 - pmic write address - write byte to register at address
569 The only one change for this command is 'dev' subcommand.
572 bool "Enable Driver Model REGULATOR command"
573 depends on DM_REGULATOR
575 This command is based on driver model regulator's API.
576 User interface features:
577 - list - list regulator devices
578 - regulator dev <id> - show or [set] operating regulator device
579 - regulator info - print constraints info
580 - regulator status - print operating status
581 - regulator value <val] <-f> - print/[set] voltage value [uV]
582 - regulator current <val> - print/[set] current value [uA]
583 - regulator mode <id> - print/[set] operating mode id
584 - regulator enable - enable the regulator output
585 - regulator disable - disable the regulator output
587 The '-f' (force) option can be used for set the value which exceeds
588 the limits, which are found in device-tree and are kept in regulator's
589 uclass platdata structure.