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 Boot a Linux kernel zImage.
160 Boot a WindowsCE image.
166 Start an application at a given address.
172 Run the command in the given environment variable.
178 Print header information for application image.
182 default !SYS_NO_FLASH
184 List all images found in flash
190 Extract a part of a multi-image.
197 bool "Enable FDT commands"
199 config OF_BOARD_SETUP
200 bool "Support DT modifications by board code"
205 menu "Environment commands"
223 Edit environment variable.
229 Save all environment variables into the compiled-in persistent
232 config CMD_ENV_EXISTS
236 Check if a variable is defined in the environment for use in
241 menu "Memory commands"
244 bool "md, mm, nm, mw, cp, cmp, base, loop"
249 mm - memory modify (auto-incrementing address)
250 nm - memory modify (constant address)
251 mw - memory write (fill)
254 base - print or set address offset
255 loop - initinite loop on address range
266 Infinite write loop on address range
271 Simple RAM read/write test.
276 mdc - memory display cyclic
277 mwc - memory write cyclic
282 Display memory information.
286 menu "Device access commands"
289 bool "dm - Access to driver model information"
293 Provides access to driver model data structures and information,
294 such as a list of devices, list of uclasses and the state of each
295 device (e.g. activated). This is not required for operation, but
296 can be useful to see the state of driver model for debugging or
300 bool "demo - Demonstration commands for driver model"
303 Provides a 'demo' command which can be used to play around with
304 driver model. To use this properly you will need to enable one or
305 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
306 Otherwise you will always get an empty list of devices. The demo
307 devices are defined in the sandbox device tree, so the easiest
308 option is to use sandbox and pass the -d point to sandbox's
315 Load a binary file over serial line.
321 Load an S-Record file over serial line
324 bool "flinfo, erase, protect"
325 default y if !SYS_NO_FLASH
328 flinfo - print FLASH memory information
330 protect - enable or disable FLASH write protection
333 depends on FLASH_CFI_DRIVER
336 ARM Ltd reference designs flash partition access
339 bool "MTD device support"
342 bool "MTD partitioning support"
344 depends on MTD_DEVICE && (CMD_FLASH || CMD_NAND)
351 config CMD_NAND_TRIMFFS
352 bool "Enable nand write.trimffs command"
354 Enable command to leave page sized runs of 0xff patterns in
355 erased state rather than overwriting them. This is required
356 for using NAND flash filesystems on NAND controllers with
357 a non-0xff ECC code for all 0xff data.
398 menu "Shell scripting commands"
410 Return true/false on integer compare.
416 Run script from memory
422 Evaluate boolean and math expressions and store the result in an env
424 Also supports loading the value at a memory location into a variable.
425 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
429 menu "Network commands"
432 bool "bootp, tftpboot"
438 bootp - boot image via network using BOOTP/TFTP protocol
439 tftpboot - boot image via network using TFTP protocol
444 TFTP put command, for uploading files to a server
449 Act as a TFTP server and boot the first received file
454 Boot image via network using RARP/TFTP protocol
459 Boot image via network using DHCP/TFTP protocol
465 config BOOTP_BOOTFILESIZE
466 bool "obtain bootfile size from DHCP"
468 config BOOTP_BOOTPATH
469 bool "obtain bootfile path from DHCP"
472 bool "obtain DNS server IP address from DHCP"
475 bool "store secondary DNS IP address in dnsip2"
478 bool "obtain gateway IP address from DHCP"
480 config BOOTP_ID_CACHE_SIZE
481 int "DHCP transaction ID cache size"
484 BOOTP packets are uniquely identified using a 32-bit ID. The
485 server will copy the ID from client requests to responses and
486 U-Boot will use this to determine if it is the destination of
487 an incoming response. Some servers will check that addresses
488 aren't in use before handing them out (usually using an ARP
489 ping) and therefore take up to a few hundred milliseconds to
490 respond. Network congestion may also influence the time it
491 takes for a response to make it back to the client. If that
492 time is too long, U-Boot will retransmit requests. In order
493 to allow earlier responses to still be accepted after these
494 retransmissions, U-Boot's BOOTP client keeps a small cache of
495 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
496 cache. The default is to keep IDs for up to four outstanding
497 requests. Increasing this will allow U-Boot to accept offers
498 from a BOOTP client in networks with unusually high latency.
500 config BOOTP_MAY_FAIL
501 bool "Do not start over, if DHCP server is not available"
503 If the DHCP server is not found after the configured retry
504 count, the call will fail instead of starting over. This
505 can be used to fail over to Link-local IP address
506 configuration if the DHCP server is not available.
508 config BOOTP_NISDOMAIN
509 bool "obtain NIS domain from DHCP"
511 config BOOTP_NTPSERVER
512 bool "obtain NTP server IP address from DHCP"
514 config BOOTP_RANDOM_DELAY
515 bool "Use a (pseudo) random delay between DHCP retries"
518 config BOOTP_RANDOM_ID
519 bool "Generate a (pseudo) random transaction ID"
522 config BOOTP_SEND_HOSTNAME
523 bool "send hostname in DHCP request"
525 config BOOTP_SUBNETMASK
526 bool "obtain subnet mask from DHCP"
528 config BOOTP_TIMEOFFSET
529 bool "obtain from DHCP"
531 config BOOTP_VENDOREX
532 bool "obtain from DHCP"
542 Boot image via network using NFS protocol.
547 Send ICMP ECHO_REQUEST to network host
552 Perform CDP network configuration
557 Synchronize RTC via network
562 Lookup the IP of a hostname
564 config CMD_LINK_LOCAL
567 Acquire a network IP address using the link-local protocol
570 bool "MII register access"
572 Support reading/writing ETH PHY registers via MII bus
581 Enable commands to switch data cache on/off.
586 Run commands and summarize execution time.
589 bool "fuse read/write"
591 eFuse reading and programming support
593 # TODO: rename to CMD_SLEEP
598 Delay execution for some time
603 Access the system timer.
606 bool "getdcr, setdcr, getidcr, setidcr"
610 getdcr - Get an AMCC PPC 4xx DCR's value
611 setdcr - Set an AMCC PPC 4xx DCR's value
612 getidcr - Get a register value via indirect DCR addressing
613 setidcr - Set a register value via indirect DCR addressing
619 This provides basic access to the U-Boot's sound support. The main
620 feature is to play a beep.
622 sound init - set up sound system
623 sound play - play a sound
630 bool "Boot timing and reporting"
632 Enable recording of boot time while booting. To use it, insert
633 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
634 bootstage.h. Only a single entry is recorded for each ID. You can
635 give the entry a name with bootstage_mark_name(). You can also
636 record elapsed time in a particular stage using bootstage_start()
637 before starting and bootstage_accum() when finished. Bootstage will
638 add up all the accumated time and report it.
640 Normally, IDs are defined in bootstage.h but a small number of
641 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
644 Calls to show_boot_progress() wil also result in log entries but
645 these will not have names.
647 config BOOTSTAGE_REPORT
648 bool "Display a detailed boot timing report before booting the OS"
651 Enable output of a boot time report just before the OS is booted.
652 This shows how long it took U-Boot to go through each stage of the
653 boot process. The report looks something like this:
655 Timer summary in microseconds:
658 3,575,678 3,575,678 board_init_f start
659 3,575,695 17 arch_cpu_init A9
660 3,575,777 82 arch_cpu_init done
661 3,659,598 83,821 board_init_r start
662 3,910,375 250,777 main_loop
663 29,916,167 26,005,792 bootm_start
664 30,361,327 445,160 start_kernel
666 config BOOTSTAGE_USER_COUNT
667 hex "Number of boot ID numbers available for user use"
670 This is the number of available user bootstage records.
671 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
672 a new ID will be allocated from this stash. If you exceed
673 the limit, recording will stop.
676 bool "Enable the 'bootstage' command"
679 Add a 'bootstage' command which supports printing a report
680 and un/stashing of bootstage data.
683 bool "Store boot timing information in the OS device tree"
686 Stash the bootstage information in the FDT. A root 'bootstage'
687 node is created with each bootstage id as a child. Each child
688 has a 'name' property and either 'mark' containing the
689 mark time in microsecond, or 'accum' containing the
690 accumulated time for that bootstage id in microseconds.
695 name = "board_init_f";
704 Code in the Linux kernel can find this in /proc/devicetree.
706 config BOOTSTAGE_STASH
707 bool "Stash the boot timing information in memory before booting OS"
710 Some OSes do not support device tree. Bootstage can instead write
711 the boot timing information in a binary format at a given address.
712 This happens through a call to bootstage_stash(), typically in
713 the CPU's cleanup_before_linux() function. You can use the
714 'bootstage stash' and 'bootstage unstash' commands to do this on
717 config BOOTSTAGE_STASH_ADDR
718 hex "Address to stash boot timing information"
721 Provide an address which will not be overwritten by the OS when it
722 starts, so that it can read this information when ready.
724 config BOOTSTAGE_STASH_SIZE
725 hex "Size of boot timing stash region"
728 This should be large enough to hold the bootstage stash. A value of
729 4096 (4KiB) is normally plenty.
733 menu "Power commands"
735 bool "Enable Driver Model PMIC command"
738 This is the pmic command, based on a driver model pmic's API.
739 Command features are unchanged:
740 - list - list pmic devices
741 - pmic dev <id> - show or [set] operating pmic device (NEW)
742 - pmic dump - dump registers
743 - pmic read address - read byte of register at address
744 - pmic write address - write byte to register at address
745 The only one change for this command is 'dev' subcommand.
748 bool "Enable Driver Model REGULATOR command"
749 depends on DM_REGULATOR
751 This command is based on driver model regulator's API.
752 User interface features:
753 - list - list regulator devices
754 - regulator dev <id> - show or [set] operating regulator device
755 - regulator info - print constraints info
756 - regulator status - print operating status
757 - regulator value <val] <-f> - print/[set] voltage value [uV]
758 - regulator current <val> - print/[set] current value [uA]
759 - regulator mode <id> - print/[set] operating mode id
760 - regulator enable - enable the regulator output
761 - regulator disable - disable the regulator output
763 The '-f' (force) option can be used for set the value which exceeds
764 the limits, which are found in device-tree and are kept in regulator's
765 uclass platdata structure.
771 menu "Environment configuration settings"
774 prompt "Select environment non-volatile storage"
776 config ENV_IS_NOWHERE
777 bool "do not store environment"
779 config ENV_IS_IN_NAND
780 bool "store environment in NAND"
784 bool "store environment in MMC"
787 config ENV_IS_IN_SPI_FLASH
788 bool "store environment in SPI flash"
794 menu "Display configuration"
799 config DISPLAY_BOARDINFO
800 bool "Display board info"