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 Save all environment variables into the compiled-in persistent
225 config CMD_ENV_EXISTS
229 Check if a variable is defined in the environment for use in
234 menu "Memory commands"
237 bool "md, mm, nm, mw, cp, cmp, base, loop"
242 mm - memory modify (auto-incrementing address)
243 nm - memory modify (constant address)
244 mw - memory write (fill)
247 base - print or set address offset
248 loop - initinite loop on address range
259 Infinite write loop on address range
264 Simple RAM read/write test.
269 mdc - memory display cyclic
270 mwc - memory write cyclic
275 Display memory information.
279 menu "Device access commands"
282 bool "dm - Access to driver model information"
286 Provides access to driver model data structures and information,
287 such as a list of devices, list of uclasses and the state of each
288 device (e.g. activated). This is not required for operation, but
289 can be useful to see the state of driver model for debugging or
293 bool "demo - Demonstration commands for driver model"
296 Provides a 'demo' command which can be used to play around with
297 driver model. To use this properly you will need to enable one or
298 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
299 Otherwise you will always get an empty list of devices. The demo
300 devices are defined in the sandbox device tree, so the easiest
301 option is to use sandbox and pass the -d point to sandbox's
308 Load a binary file over serial line.
314 Load an S-Record file over serial line
317 bool "flinfo, erase, protect"
318 default y if !SYS_NO_FLASH
321 flinfo - print FLASH memory information
323 protect - enable or disable FLASH write protection
326 depends on FLASH_CFI_DRIVER
329 ARM Ltd reference designs flash partition access
332 bool "MTD device support"
335 bool "MTD partitioning support"
337 depends on MTD_DEVICE && (CMD_FLASH || CMD_NAND)
344 config CMD_NAND_TRIMFFS
345 bool "Enable nand write.trimffs command"
347 Enable command to leave page sized runs of 0xff patterns in
348 erased state rather than overwriting them. This is required
349 for using NAND flash filesystems on NAND controllers with
350 a non-0xff ECC code for all 0xff data.
391 menu "Shell scripting commands"
403 Return true/false on integer compare.
409 Run script from memory
415 Evaluate boolean and math expressions and store the result in an env
417 Also supports loading the value at a memory location into a variable.
418 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
422 menu "Network commands"
425 bool "bootp, tftpboot"
431 bootp - boot image via network using BOOTP/TFTP protocol
432 tftpboot - boot image via network using TFTP protocol
437 TFTP put command, for uploading files to a server
442 Act as a TFTP server and boot the first received file
447 Boot image via network using RARP/TFTP protocol
452 Boot image via network using DHCP/TFTP protocol
458 config BOOTP_BOOTFILESIZE
459 bool "obtain bootfile size from DHCP"
461 config BOOTP_BOOTPATH
462 bool "obtain bootfile path from DHCP"
465 bool "obtain DNS server IP address from DHCP"
468 bool "store secondary DNS IP address in dnsip2"
471 bool "obtain gateway IP address from DHCP"
473 config BOOTP_ID_CACHE_SIZE
474 int "DHCP transaction ID cache size"
477 BOOTP packets are uniquely identified using a 32-bit ID. The
478 server will copy the ID from client requests to responses and
479 U-Boot will use this to determine if it is the destination of
480 an incoming response. Some servers will check that addresses
481 aren't in use before handing them out (usually using an ARP
482 ping) and therefore take up to a few hundred milliseconds to
483 respond. Network congestion may also influence the time it
484 takes for a response to make it back to the client. If that
485 time is too long, U-Boot will retransmit requests. In order
486 to allow earlier responses to still be accepted after these
487 retransmissions, U-Boot's BOOTP client keeps a small cache of
488 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
489 cache. The default is to keep IDs for up to four outstanding
490 requests. Increasing this will allow U-Boot to accept offers
491 from a BOOTP client in networks with unusually high latency.
493 config BOOTP_MAY_FAIL
494 bool "Do not start over, if DHCP server is not available"
496 If the DHCP server is not found after the configured retry
497 count, the call will fail instead of starting over. This
498 can be used to fail over to Link-local IP address
499 configuration if the DHCP server is not available.
501 config BOOTP_NISDOMAIN
502 bool "obtain NIS domain from DHCP"
504 config BOOTP_NTPSERVER
505 bool "obtain NTP server IP address from DHCP"
507 config BOOTP_RANDOM_DELAY
508 bool "Use a (pseudo) random delay between DHCP retries"
511 config BOOTP_RANDOM_ID
512 bool "Generate a (pseudo) random transaction ID"
515 config BOOTP_SEND_HOSTNAME
516 bool "send hostname in DHCP request"
518 config BOOTP_SUBNETMASK
519 bool "obtain subnet mask from DHCP"
521 config BOOTP_TIMEOFFSET
522 bool "obtain from DHCP"
524 config BOOTP_VENDOREX
525 bool "obtain from DHCP"
535 Boot image via network using NFS protocol.
540 Send ICMP ECHO_REQUEST to network host
545 Perform CDP network configuration
550 Synchronize RTC via network
555 Lookup the IP of a hostname
557 config CMD_LINK_LOCAL
560 Acquire a network IP address using the link-local protocol
563 bool "MII register access"
565 Support reading/writing ETH PHY registers via MII bus
574 Enable commands to switch data cache on/off.
579 Run commands and summarize execution time.
582 bool "fuse read/write"
584 eFuse reading and programming support
586 # TODO: rename to CMD_SLEEP
591 Delay execution for some time
596 Access the system timer.
599 bool "getdcr, setdcr, getidcr, setidcr"
603 getdcr - Get an AMCC PPC 4xx DCR's value
604 setdcr - Set an AMCC PPC 4xx DCR's value
605 getidcr - Get a register value via indirect DCR addressing
606 setidcr - Set a register value via indirect DCR addressing
612 This provides basic access to the U-Boot's sound support. The main
613 feature is to play a beep.
615 sound init - set up sound system
616 sound play - play a sound
623 bool "Boot timing and reporting"
625 Enable recording of boot time while booting. To use it, insert
626 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
627 bootstage.h. Only a single entry is recorded for each ID. You can
628 give the entry a name with bootstage_mark_name(). You can also
629 record elapsed time in a particular stage using bootstage_start()
630 before starting and bootstage_accum() when finished. Bootstage will
631 add up all the accumated time and report it.
633 Normally, IDs are defined in bootstage.h but a small number of
634 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
637 Calls to show_boot_progress() wil also result in log entries but
638 these will not have names.
640 config BOOTSTAGE_REPORT
641 bool "Display a detailed boot timing report before booting the OS"
644 Enable output of a boot time report just before the OS is booted.
645 This shows how long it took U-Boot to go through each stage of the
646 boot process. The report looks something like this:
648 Timer summary in microseconds:
651 3,575,678 3,575,678 board_init_f start
652 3,575,695 17 arch_cpu_init A9
653 3,575,777 82 arch_cpu_init done
654 3,659,598 83,821 board_init_r start
655 3,910,375 250,777 main_loop
656 29,916,167 26,005,792 bootm_start
657 30,361,327 445,160 start_kernel
659 config BOOTSTAGE_USER_COUNT
660 hex "Number of boot ID numbers available for user use"
663 This is the number of available user bootstage records.
664 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
665 a new ID will be allocated from this stash. If you exceed
666 the limit, recording will stop.
669 bool "Enable the 'bootstage' command"
672 Add a 'bootstage' command which supports printing a report
673 and un/stashing of bootstage data.
676 bool "Store boot timing information in the OS device tree"
679 Stash the bootstage information in the FDT. A root 'bootstage'
680 node is created with each bootstage id as a child. Each child
681 has a 'name' property and either 'mark' containing the
682 mark time in microsecond, or 'accum' containing the
683 accumulated time for that bootstage id in microseconds.
688 name = "board_init_f";
697 Code in the Linux kernel can find this in /proc/devicetree.
699 config BOOTSTAGE_STASH
700 bool "Stash the boot timing information in memory before booting OS"
703 Some OSes do not support device tree. Bootstage can instead write
704 the boot timing information in a binary format at a given address.
705 This happens through a call to bootstage_stash(), typically in
706 the CPU's cleanup_before_linux() function. You can use the
707 'bootstage stash' and 'bootstage unstash' commands to do this on
710 config BOOTSTAGE_STASH_ADDR
711 hex "Address to stash boot timing information"
714 Provide an address which will not be overwritten by the OS when it
715 starts, so that it can read this information when ready.
717 config BOOTSTAGE_STASH_SIZE
718 hex "Size of boot timing stash region"
721 This should be large enough to hold the bootstage stash. A value of
722 4096 (4KiB) is normally plenty.
726 menu "Power commands"
728 bool "Enable Driver Model PMIC command"
731 This is the pmic command, based on a driver model pmic's API.
732 Command features are unchanged:
733 - list - list pmic devices
734 - pmic dev <id> - show or [set] operating pmic device (NEW)
735 - pmic dump - dump registers
736 - pmic read address - read byte of register at address
737 - pmic write address - write byte to register at address
738 The only one change for this command is 'dev' subcommand.
741 bool "Enable Driver Model REGULATOR command"
742 depends on DM_REGULATOR
744 This command is based on driver model regulator's API.
745 User interface features:
746 - list - list regulator devices
747 - regulator dev <id> - show or [set] operating regulator device
748 - regulator info - print constraints info
749 - regulator status - print operating status
750 - regulator value <val] <-f> - print/[set] voltage value [uV]
751 - regulator current <val> - print/[set] current value [uA]
752 - regulator mode <id> - print/[set] operating mode id
753 - regulator enable - enable the regulator output
754 - regulator disable - disable the regulator output
756 The '-f' (force) option can be used for set the value which exceeds
757 the limits, which are found in device-tree and are kept in regulator's
758 uclass platdata structure.
764 menu "Environment configuration settings"
767 prompt "Select environment non-volatile storage"
769 config ENV_IS_NOWHERE
770 bool "do not store environment"
772 config ENV_IS_IN_NAND
773 bool "store environment in NAND"
777 bool "store environment in MMC"
780 config ENV_IS_IN_SPI_FLASH
781 bool "store environment in SPI flash"
787 menu "Display configuration"
792 config DISPLAY_BOARDINFO
793 bool "Display board info"