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 Boot a Linux kernel zImage.
153 Boot a WindowsCE image.
159 Start an application at a given address.
165 Run the command in the given environment variable.
171 Print header information for application image.
175 default !SYS_NO_FLASH
177 List all images found in flash
183 Extract a part of a multi-image.
190 bool "Enable FDT commands"
192 config OF_BOARD_SETUP
193 bool "Support DT modifications by board code"
198 menu "Environment commands"
216 Edit environment variable.
222 Run the command in the given environment variable.
226 menu "Memory commands"
229 bool "md, mm, nm, mw, cp, cmp, base, loop"
234 mm - memory modify (auto-incrementing address)
235 nm - memory modify (constant address)
236 mw - memory write (fill)
239 base - print or set address offset
240 loop - initinite loop on address range
251 Infinite write loop on address range
256 Simple RAM read/write test.
261 mdc - memory display cyclic
262 mwc - memory write cyclic
267 Display memory information.
271 menu "Device access commands"
274 bool "dm - Access to driver model information"
278 Provides access to driver model data structures and information,
279 such as a list of devices, list of uclasses and the state of each
280 device (e.g. activated). This is not required for operation, but
281 can be useful to see the state of driver model for debugging or
285 bool "demo - Demonstration commands for driver model"
288 Provides a 'demo' command which can be used to play around with
289 driver model. To use this properly you will need to enable one or
290 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
291 Otherwise you will always get an empty list of devices. The demo
292 devices are defined in the sandbox device tree, so the easiest
293 option is to use sandbox and pass the -d point to sandbox's
300 Load a binary file over serial line.
306 Load an S-Record file over serial line
309 bool "flinfo, erase, protect"
310 default y if !SYS_NO_FLASH
313 flinfo - print FLASH memory information
315 protect - enable or disable FLASH write protection
318 depends on FLASH_CFI_DRIVER
321 ARM Ltd reference designs flash partition access
324 bool "MTD device support"
327 bool "MTD partitioning support"
329 depends on MTD_DEVICE && (CMD_FLASH || CMD_NAND)
336 config CMD_NAND_TRIMFFS
337 bool "Enable nand write.trimffs command"
339 Enable command to leave page sized runs of 0xff patterns in
340 erased state rather than overwriting them. This is required
341 for using NAND flash filesystems on NAND controllers with
342 a non-0xff ECC code for all 0xff data.
378 menu "Shell scripting commands"
390 Return true/false on integer compare.
396 Run script from memory
401 Evaluate boolean and math expressions and store the result in an env
403 Also supports loading the value at a memory location into a variable.
404 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
408 menu "Network commands"
411 bool "bootp, tftpboot"
416 bootp - boot image via network using BOOTP/TFTP protocol
417 tftpboot - boot image via network using TFTP protocol
422 TFTP put command, for uploading files to a server
427 Act as a TFTP server and boot the first received file
432 Boot image via network using RARP/TFTP protocol
437 Boot image via network using DHCP/TFTP protocol
443 config BOOTP_BOOTFILESIZE
444 bool "obtain bootfile size from DHCP"
446 config BOOTP_BOOTPATH
447 bool "obtain bootfile path from DHCP"
450 bool "obtain DNS server IP address from DHCP"
453 bool "store secondary DNS IP address in dnsip2"
456 bool "obtain gateway IP address from DHCP"
458 config BOOTP_ID_CACHE_SIZE
459 int "DHCP transaction ID cache size"
462 BOOTP packets are uniquely identified using a 32-bit ID. The
463 server will copy the ID from client requests to responses and
464 U-Boot will use this to determine if it is the destination of
465 an incoming response. Some servers will check that addresses
466 aren't in use before handing them out (usually using an ARP
467 ping) and therefore take up to a few hundred milliseconds to
468 respond. Network congestion may also influence the time it
469 takes for a response to make it back to the client. If that
470 time is too long, U-Boot will retransmit requests. In order
471 to allow earlier responses to still be accepted after these
472 retransmissions, U-Boot's BOOTP client keeps a small cache of
473 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
474 cache. The default is to keep IDs for up to four outstanding
475 requests. Increasing this will allow U-Boot to accept offers
476 from a BOOTP client in networks with unusually high latency.
478 config BOOTP_MAY_FAIL
479 bool "Do not start over, if DHCP server is not available"
481 If the DHCP server is not found after the configured retry
482 count, the call will fail instead of starting over. This
483 can be used to fail over to Link-local IP address
484 configuration if the DHCP server is not available.
486 config BOOTP_NISDOMAIN
487 bool "obtain NIS domain from DHCP"
489 config BOOTP_NTPSERVER
490 bool "obtain NTP server IP address from DHCP"
492 config BOOTP_RANDOM_DELAY
493 bool "Use a (pseudo) random delay between DHCP retries"
496 config BOOTP_RANDOM_ID
497 bool "Generate a (pseudo) random transaction ID"
500 config BOOTP_SEND_HOSTNAME
501 bool "send hostname in DHCP request"
503 config BOOTP_SUBNETMASK
504 bool "obtain subnet mask from DHCP"
506 config BOOTP_TIMEOFFSET
507 bool "obtain from DHCP"
509 config BOOTP_VENDOREX
510 bool "obtain from DHCP"
520 Boot image via network using NFS protocol.
525 Send ICMP ECHO_REQUEST to network host
530 Perform CDP network configuration
535 Synchronize RTC via network
540 Lookup the IP of a hostname
542 config CMD_LINK_LOCAL
545 Acquire a network IP address using the link-local protocol
548 bool "MII register access"
550 Support reading/writing ETH PHY registers via MII bus
559 Enable commands to switch data cache on/off.
564 Run commands and summarize execution time.
567 bool "fuse read/write"
569 eFuse reading and programming support
571 # TODO: rename to CMD_SLEEP
576 Delay execution for some time
581 Access the system timer.
584 bool "getdcr, setdcr, getidcr, setidcr"
588 getdcr - Get an AMCC PPC 4xx DCR's value
589 setdcr - Set an AMCC PPC 4xx DCR's value
590 getidcr - Get a register value via indirect DCR addressing
591 setidcr - Set a register value via indirect DCR addressing
597 This provides basic access to the U-Boot's sound support. The main
598 feature is to play a beep.
600 sound init - set up sound system
601 sound play - play a sound
608 bool "Boot timing and reporting"
610 Enable recording of boot time while booting. To use it, insert
611 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
612 bootstage.h. Only a single entry is recorded for each ID. You can
613 give the entry a name with bootstage_mark_name(). You can also
614 record elapsed time in a particular stage using bootstage_start()
615 before starting and bootstage_accum() when finished. Bootstage will
616 add up all the accumated time and report it.
618 Normally, IDs are defined in bootstage.h but a small number of
619 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
622 Calls to show_boot_progress() wil also result in log entries but
623 these will not have names.
625 config BOOTSTAGE_REPORT
626 bool "Display a detailed boot timing report before booting the OS"
629 Enable output of a boot time report just before the OS is booted.
630 This shows how long it took U-Boot to go through each stage of the
631 boot process. The report looks something like this:
633 Timer summary in microseconds:
636 3,575,678 3,575,678 board_init_f start
637 3,575,695 17 arch_cpu_init A9
638 3,575,777 82 arch_cpu_init done
639 3,659,598 83,821 board_init_r start
640 3,910,375 250,777 main_loop
641 29,916,167 26,005,792 bootm_start
642 30,361,327 445,160 start_kernel
644 config BOOTSTAGE_USER_COUNT
645 hex "Number of boot ID numbers available for user use"
648 This is the number of available user bootstage records.
649 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
650 a new ID will be allocated from this stash. If you exceed
651 the limit, recording will stop.
654 bool "Enable the 'bootstage' command"
657 Add a 'bootstage' command which supports printing a report
658 and un/stashing of bootstage data.
661 bool "Store boot timing information in the OS device tree"
664 Stash the bootstage information in the FDT. A root 'bootstage'
665 node is created with each bootstage id as a child. Each child
666 has a 'name' property and either 'mark' containing the
667 mark time in microsecond, or 'accum' containing the
668 accumulated time for that bootstage id in microseconds.
673 name = "board_init_f";
682 Code in the Linux kernel can find this in /proc/devicetree.
684 config BOOTSTAGE_STASH
685 bool "Stash the boot timing information in memory before booting OS"
688 Some OSes do not support device tree. Bootstage can instead write
689 the boot timing information in a binary format at a given address.
690 This happens through a call to bootstage_stash(), typically in
691 the CPU's cleanup_before_linux() function. You can use the
692 'bootstage stash' and 'bootstage unstash' commands to do this on
695 config BOOTSTAGE_STASH_ADDR
696 hex "Address to stash boot timing information"
699 Provide an address which will not be overwritten by the OS when it
700 starts, so that it can read this information when ready.
702 config BOOTSTAGE_STASH_SIZE
703 hex "Size of boot timing stash region"
706 This should be large enough to hold the bootstage stash. A value of
707 4096 (4KiB) is normally plenty.
711 menu "Power commands"
713 bool "Enable Driver Model PMIC command"
716 This is the pmic command, based on a driver model pmic's API.
717 Command features are unchanged:
718 - list - list pmic devices
719 - pmic dev <id> - show or [set] operating pmic device (NEW)
720 - pmic dump - dump registers
721 - pmic read address - read byte of register at address
722 - pmic write address - write byte to register at address
723 The only one change for this command is 'dev' subcommand.
726 bool "Enable Driver Model REGULATOR command"
727 depends on DM_REGULATOR
729 This command is based on driver model regulator's API.
730 User interface features:
731 - list - list regulator devices
732 - regulator dev <id> - show or [set] operating regulator device
733 - regulator info - print constraints info
734 - regulator status - print operating status
735 - regulator value <val] <-f> - print/[set] voltage value [uV]
736 - regulator current <val> - print/[set] current value [uA]
737 - regulator mode <id> - print/[set] operating mode id
738 - regulator enable - enable the regulator output
739 - regulator disable - disable the regulator output
741 The '-f' (force) option can be used for set the value which exceeds
742 the limits, which are found in device-tree and are kept in regulator's
743 uclass platdata structure.
749 menu "Environment configuration settings"
752 prompt "Select environment non-volatile storage"
754 config ENV_IS_NOWHERE
755 bool "do not store environment"
757 config ENV_IS_IN_NAND
758 bool "store environment in NAND"
762 bool "store environment in MMC"
765 config ENV_IS_IN_SPI_FLASH
766 bool "store environment in SPI flash"
772 menu "Display configuration"
777 config DISPLAY_BOARDINFO
778 bool "Display board info"