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_DELAY_STR
49 string "Delay autobooting via specific input key / string"
50 depends on AUTOBOOT_KEYED
52 This option delays the automatic boot feature by issuing
53 a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
54 or the environment variable "bootdelaykey" is specified
55 and this string is received from console input before
56 autoboot starts booting, U-Boot gives a command prompt. The
57 U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
58 used, otherwise it never times out.
60 config AUTOBOOT_STOP_STR
61 string "Stop autobooting via specific input key / string"
62 depends on AUTOBOOT_KEYED
64 This option enables stopping (aborting) of the automatic
65 boot feature only by issuing a specific input key or
66 string. If CONFIG_AUTOBOOT_STOP_STR or the environment
67 variable "bootstopkey" is specified and this string is
68 received from console input before autoboot starts booting,
69 U-Boot gives a command prompt. The U-Boot prompt never
70 times out, even if CONFIG_BOOT_RETRY_TIME is used.
72 config AUTOBOOT_KEYED_CTRLC
73 bool "Enable Ctrl-C autoboot interruption"
74 depends on AUTOBOOT_KEYED
77 This option allows for the boot sequence to be interrupted
78 by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
79 Setting this variable provides an escape sequence from the
80 limited "password" strings.
98 Print console devices and information.
103 Print information about available CPUs. This normally shows the
104 number of CPUs, type (e.g. manufacturer, architecture, product or
105 internal name) and clock frequency. Other information may be
106 available depending on the CPU driver.
111 Print GPL license text
121 Run the command stored in the environment "bootcmd", i.e.
122 "bootd" does the same thing as "run bootcmd".
128 Boot an application image from the memory.
134 Boot a Linux kernel zImage.
139 Boot a WindowsCE image.
145 Start an application at a given address.
151 Run the command in the given environment variable.
157 Print header information for application image.
161 default !SYS_NO_FLASH
163 List all images found in flash
169 Extract a part of a multi-image.
176 bool "Enable FDT commands"
178 config OF_BOARD_SETUP
179 bool "Support DT modifications by board code"
184 menu "Environment commands"
202 Edit environment variable.
208 Run the command in the given environment variable.
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"
296 default y if !SYS_NO_FLASH
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
310 bool "MTD device support"
313 bool "MTD partitioning support"
315 depends on MTD_DEVICE && (CMD_FLASH || CMD_NAND)
322 config CMD_NAND_TRIMFFS
323 bool "Enable nand write.trimffs command"
325 Enable command to leave page sized runs of 0xff patterns in
326 erased state rather than overwriting them. This is required
327 for using NAND flash filesystems on NAND controllers with
328 a non-0xff ECC code for all 0xff data.
364 menu "Shell scripting commands"
376 Return true/false on integer compare.
382 Run script from memory
387 Evaluate boolean and math expressions and store the result in an env
389 Also supports loading the value at a memory location into a variable.
390 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
394 menu "Network commands"
397 bool "bootp, tftpboot"
402 bootp - boot image via network using BOOTP/TFTP protocol
403 tftpboot - boot image via network using TFTP protocol
408 TFTP put command, for uploading files to a server
413 Act as a TFTP server and boot the first received file
418 Boot image via network using RARP/TFTP protocol
423 Boot image via network using DHCP/TFTP protocol
429 config BOOTP_BOOTFILESIZE
430 bool "obtain bootfile size from DHCP"
432 config BOOTP_BOOTPATH
433 bool "obtain bootfile path from DHCP"
436 bool "obtain DNS server IP address from DHCP"
439 bool "store secondary DNS IP address in dnsip2"
442 bool "obtain gateway IP address from DHCP"
444 config BOOTP_ID_CACHE_SIZE
445 int "DHCP transaction ID cache size"
448 BOOTP packets are uniquely identified using a 32-bit ID. The
449 server will copy the ID from client requests to responses and
450 U-Boot will use this to determine if it is the destination of
451 an incoming response. Some servers will check that addresses
452 aren't in use before handing them out (usually using an ARP
453 ping) and therefore take up to a few hundred milliseconds to
454 respond. Network congestion may also influence the time it
455 takes for a response to make it back to the client. If that
456 time is too long, U-Boot will retransmit requests. In order
457 to allow earlier responses to still be accepted after these
458 retransmissions, U-Boot's BOOTP client keeps a small cache of
459 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
460 cache. The default is to keep IDs for up to four outstanding
461 requests. Increasing this will allow U-Boot to accept offers
462 from a BOOTP client in networks with unusually high latency.
464 config BOOTP_MAY_FAIL
465 bool "Do not start over, if DHCP server is not available"
467 If the DHCP server is not found after the configured retry
468 count, the call will fail instead of starting over. This
469 can be used to fail over to Link-local IP address
470 configuration if the DHCP server is not available.
472 config BOOTP_NISDOMAIN
473 bool "obtain NIS domain from DHCP"
475 config BOOTP_NTPSERVER
476 bool "obtain NTP server IP address from DHCP"
478 config BOOTP_RANDOM_DELAY
479 bool "Use a (pseudo) random delay between DHCP retries"
482 config BOOTP_RANDOM_ID
483 bool "Generate a (pseudo) random transaction ID"
486 config BOOTP_SEND_HOSTNAME
487 bool "send hostname in DHCP request"
489 config BOOTP_SUBNETMASK
490 bool "obtain subnet mask from DHCP"
492 config BOOTP_TIMEOFFSET
493 bool "obtain from DHCP"
495 config BOOTP_VENDOREX
496 bool "obtain from DHCP"
506 Boot image via network using NFS protocol.
511 Send ICMP ECHO_REQUEST to network host
516 Perform CDP network configuration
521 Synchronize RTC via network
526 Lookup the IP of a hostname
528 config CMD_LINK_LOCAL
531 Acquire a network IP address using the link-local protocol
534 bool "MII register access"
536 Support reading/writing ETH PHY registers via MII bus
545 Enable commands to switch data cache on/off.
550 Run commands and summarize execution time.
553 bool "fuse read/write"
555 eFuse reading and programming support
557 # TODO: rename to CMD_SLEEP
562 Delay execution for some time
567 Access the system timer.
570 bool "getdcr, setdcr, getidcr, setidcr"
574 getdcr - Get an AMCC PPC 4xx DCR's value
575 setdcr - Set an AMCC PPC 4xx DCR's value
576 getidcr - Get a register value via indirect DCR addressing
577 setidcr - Set a register value via indirect DCR addressing
583 This provides basic access to the U-Boot's sound support. The main
584 feature is to play a beep.
586 sound init - set up sound system
587 sound play - play a sound
594 bool "Boot timing and reporting"
596 Enable recording of boot time while booting. To use it, insert
597 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
598 bootstage.h. Only a single entry is recorded for each ID. You can
599 give the entry a name with bootstage_mark_name(). You can also
600 record elapsed time in a particular stage using bootstage_start()
601 before starting and bootstage_accum() when finished. Bootstage will
602 add up all the accumated time and report it.
604 Normally, IDs are defined in bootstage.h but a small number of
605 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
608 Calls to show_boot_progress() wil also result in log entries but
609 these will not have names.
611 config BOOTSTAGE_REPORT
612 bool "Display a detailed boot timing report before booting the OS"
615 Enable output of a boot time report just before the OS is booted.
616 This shows how long it took U-Boot to go through each stage of the
617 boot process. The report looks something like this:
619 Timer summary in microseconds:
622 3,575,678 3,575,678 board_init_f start
623 3,575,695 17 arch_cpu_init A9
624 3,575,777 82 arch_cpu_init done
625 3,659,598 83,821 board_init_r start
626 3,910,375 250,777 main_loop
627 29,916,167 26,005,792 bootm_start
628 30,361,327 445,160 start_kernel
630 config BOOTSTAGE_USER_COUNT
631 hex "Number of boot ID numbers available for user use"
634 This is the number of available user bootstage records.
635 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
636 a new ID will be allocated from this stash. If you exceed
637 the limit, recording will stop.
640 bool "Enable the 'bootstage' command"
643 Add a 'bootstage' command which supports printing a report
644 and un/stashing of bootstage data.
647 bool "Store boot timing information in the OS device tree"
650 Stash the bootstage information in the FDT. A root 'bootstage'
651 node is created with each bootstage id as a child. Each child
652 has a 'name' property and either 'mark' containing the
653 mark time in microsecond, or 'accum' containing the
654 accumulated time for that bootstage id in microseconds.
659 name = "board_init_f";
668 Code in the Linux kernel can find this in /proc/devicetree.
670 config BOOTSTAGE_STASH
671 bool "Stash the boot timing information in memory before booting OS"
674 Some OSes do not support device tree. Bootstage can instead write
675 the boot timing information in a binary format at a given address.
676 This happens through a call to bootstage_stash(), typically in
677 the CPU's cleanup_before_linux() function. You can use the
678 'bootstage stash' and 'bootstage unstash' commands to do this on
681 config BOOTSTAGE_STASH_ADDR
682 hex "Address to stash boot timing information"
685 Provide an address which will not be overwritten by the OS when it
686 starts, so that it can read this information when ready.
688 config BOOTSTAGE_STASH_SIZE
689 hex "Size of boot timing stash region"
692 This should be large enough to hold the bootstage stash. A value of
693 4096 (4KiB) is normally plenty.
697 menu "Power commands"
699 bool "Enable Driver Model PMIC command"
702 This is the pmic command, based on a driver model pmic's API.
703 Command features are unchanged:
704 - list - list pmic devices
705 - pmic dev <id> - show or [set] operating pmic device (NEW)
706 - pmic dump - dump registers
707 - pmic read address - read byte of register at address
708 - pmic write address - write byte to register at address
709 The only one change for this command is 'dev' subcommand.
712 bool "Enable Driver Model REGULATOR command"
713 depends on DM_REGULATOR
715 This command is based on driver model regulator's API.
716 User interface features:
717 - list - list regulator devices
718 - regulator dev <id> - show or [set] operating regulator device
719 - regulator info - print constraints info
720 - regulator status - print operating status
721 - regulator value <val] <-f> - print/[set] voltage value [uV]
722 - regulator current <val> - print/[set] current value [uA]
723 - regulator mode <id> - print/[set] operating mode id
724 - regulator enable - enable the regulator output
725 - regulator disable - disable the regulator output
727 The '-f' (force) option can be used for set the value which exceeds
728 the limits, which are found in device-tree and are kept in regulator's
729 uclass platdata structure.
735 menu "Environment configuration settings"
738 prompt "Select environment non-volatile storage"
740 config ENV_IS_NOWHERE
741 bool "do not store environment"
743 config ENV_IS_IN_NAND
744 bool "store environment in NAND"
748 bool "store environment in MMC"
751 config ENV_IS_IN_SPI_FLASH
752 bool "store environment in SPI flash"
758 menu "Display configuration"
763 config DISPLAY_BOARDINFO
764 bool "Display board info"