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.
34 Print console devices and information.
39 Print information about available CPUs. This normally shows the
40 number of CPUs, type (e.g. manufacturer, architecture, product or
41 internal name) and clock frequency. Other information may be
42 available depending on the CPU driver.
47 Print GPL license text
57 Run the command stored in the environment "bootcmd", i.e.
58 "bootd" does the same thing as "run bootcmd".
64 Boot an application image from the memory.
70 Boot a Linux kernel zImage.
75 Boot a WindowsCE image.
81 Start an application at a given address.
87 Run the command in the given environment variable.
93 Print header information for application image.
99 List all images found in flash
105 Extract a part of a multi-image.
112 bool "Enable FDT commands"
114 config OF_BOARD_SETUP
115 bool "Support DT modifications by board code"
120 menu "Environment commands"
138 Edit environment variable.
144 Run the command in the given environment variable.
148 menu "Memory commands"
151 bool "md, mm, nm, mw, cp, cmp, base, loop"
156 mm - memory modify (auto-incrementing address)
157 nm - memory modify (constant address)
158 mw - memory write (fill)
161 base - print or set address offset
162 loop - initinite loop on address range
173 Infinite write loop on address range
178 Simple RAM read/write test.
183 mdc - memory display cyclic
184 mwc - memory write cyclic
189 Display memory information.
193 menu "Device access commands"
196 bool "dm - Access to driver model information"
200 Provides access to driver model data structures and information,
201 such as a list of devices, list of uclasses and the state of each
202 device (e.g. activated). This is not required for operation, but
203 can be useful to see the state of driver model for debugging or
207 bool "demo - Demonstration commands for driver model"
210 Provides a 'demo' command which can be used to play around with
211 driver model. To use this properly you will need to enable one or
212 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
213 Otherwise you will always get an empty list of devices. The demo
214 devices are defined in the sandbox device tree, so the easiest
215 option is to use sandbox and pass the -d point to sandbox's
222 Load a binary file over serial line.
228 Load an S-Record file over serial line
231 bool "flinfo, erase, protect"
232 default y if !SYS_NO_FLASH
235 flinfo - print FLASH memory information
237 protect - enable or disable FLASH write protection
240 depends on FLASH_CFI_DRIVER
243 ARM Ltd reference designs flash partition access
246 bool "MTD device support"
249 bool "MTD partitioning support"
251 depends on MTD_DEVICE && (CMD_FLASH || CMD_NAND)
258 config CMD_NAND_TRIMFFS
259 bool "Enable nand write.trimffs command"
261 Enable command to leave page sized runs of 0xff patterns in
262 erased state rather than overwriting them. This is required
263 for using NAND flash filesystems on NAND controllers with
264 a non-0xff ECC code for all 0xff data.
300 menu "Shell scripting commands"
312 Return true/false on integer compare.
318 Run script from memory
323 Evaluate boolean and math expressions and store the result in an env
325 Also supports loading the value at a memory location into a variable.
326 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
330 menu "Network commands"
333 bool "bootp, tftpboot"
337 bootp - boot image via network using BOOTP/TFTP protocol
338 tftpboot - boot image via network using TFTP protocol
343 TFTP put command, for uploading files to a server
348 Act as a TFTP server and boot the first received file
353 Boot image via network using RARP/TFTP protocol
358 Boot image via network using DHCP/TFTP protocol
364 config BOOTP_BOOTFILESIZE
365 bool "obtain bootfile size from DHCP"
367 config BOOTP_BOOTPATH
368 bool "obtain bootfile path from DHCP"
371 bool "obtain DNS server IP address from DHCP"
374 bool "store secondary DNS IP address in dnsip2"
377 bool "obtain gateway IP address from DHCP"
379 config BOOTP_ID_CACHE_SIZE
380 int "DHCP transaction ID cache size"
383 BOOTP packets are uniquely identified using a 32-bit ID. The
384 server will copy the ID from client requests to responses and
385 U-Boot will use this to determine if it is the destination of
386 an incoming response. Some servers will check that addresses
387 aren't in use before handing them out (usually using an ARP
388 ping) and therefore take up to a few hundred milliseconds to
389 respond. Network congestion may also influence the time it
390 takes for a response to make it back to the client. If that
391 time is too long, U-Boot will retransmit requests. In order
392 to allow earlier responses to still be accepted after these
393 retransmissions, U-Boot's BOOTP client keeps a small cache of
394 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
395 cache. The default is to keep IDs for up to four outstanding
396 requests. Increasing this will allow U-Boot to accept offers
397 from a BOOTP client in networks with unusually high latency.
399 config BOOTP_MAY_FAIL
400 bool "Do not start over, if DHCP server is not available"
402 If the DHCP server is not found after the configured retry
403 count, the call will fail instead of starting over. This
404 can be used to fail over to Link-local IP address
405 configuration if the DHCP server is not available.
407 config BOOTP_NISDOMAIN
408 bool "obtain NIS domain from DHCP"
410 config BOOTP_NTPSERVER
411 bool "obtain NTP server IP address from DHCP"
413 config BOOTP_RANDOM_DELAY
414 bool "Use a (pseudo) random delay between DHCP retries"
417 config BOOTP_RANDOM_ID
418 bool "Generate a (pseudo) random transaction ID"
421 config BOOTP_SEND_HOSTNAME
422 bool "send hostname in DHCP request"
424 config BOOTP_SUBNETMASK
425 bool "obtain subnet mask from DHCP"
427 config BOOTP_TIMEOFFSET
428 bool "obtain from DHCP"
430 config BOOTP_VENDOREX
431 bool "obtain from DHCP"
441 Boot image via network using NFS protocol.
446 Send ICMP ECHO_REQUEST to network host
451 Perform CDP network configuration
456 Synchronize RTC via network
461 Lookup the IP of a hostname
463 config CMD_LINK_LOCAL
466 Acquire a network IP address using the link-local protocol
469 bool "MII register access"
471 Support reading/writing ETH PHY registers via MII bus
480 Enable commands to switch data cache on/off.
485 Run commands and summarize execution time.
488 bool "fuse read/write"
490 eFuse reading and programming support
492 # TODO: rename to CMD_SLEEP
497 Delay execution for some time
502 Access the system timer.
505 bool "getdcr, setdcr, getidcr, setidcr"
509 getdcr - Get an AMCC PPC 4xx DCR's value
510 setdcr - Set an AMCC PPC 4xx DCR's value
511 getidcr - Get a register value via indirect DCR addressing
512 setidcr - Set a register value via indirect DCR addressing
518 This provides basic access to the U-Boot's sound support. The main
519 feature is to play a beep.
521 sound init - set up sound system
522 sound play - play a sound
529 bool "Boot timing and reporting"
531 Enable recording of boot time while booting. To use it, insert
532 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
533 bootstage.h. Only a single entry is recorded for each ID. You can
534 give the entry a name with bootstage_mark_name(). You can also
535 record elapsed time in a particular stage using bootstage_start()
536 before starting and bootstage_accum() when finished. Bootstage will
537 add up all the accumated time and report it.
539 Normally, IDs are defined in bootstage.h but a small number of
540 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
543 Calls to show_boot_progress() wil also result in log entries but
544 these will not have names.
546 config BOOTSTAGE_REPORT
547 bool "Display a detailed boot timing report before booting the OS"
550 Enable output of a boot time report just before the OS is booted.
551 This shows how long it took U-Boot to go through each stage of the
552 boot process. The report looks something like this:
554 Timer summary in microseconds:
557 3,575,678 3,575,678 board_init_f start
558 3,575,695 17 arch_cpu_init A9
559 3,575,777 82 arch_cpu_init done
560 3,659,598 83,821 board_init_r start
561 3,910,375 250,777 main_loop
562 29,916,167 26,005,792 bootm_start
563 30,361,327 445,160 start_kernel
565 config BOOTSTAGE_USER_COUNT
566 hex "Number of boot ID numbers available for user use"
569 This is the number of available user bootstage records.
570 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
571 a new ID will be allocated from this stash. If you exceed
572 the limit, recording will stop.
575 bool "Enable the 'bootstage' command"
578 Add a 'bootstage' command which supports printing a report
579 and un/stashing of bootstage data.
582 bool "Store boot timing information in the OS device tree"
585 Stash the bootstage information in the FDT. A root 'bootstage'
586 node is created with each bootstage id as a child. Each child
587 has a 'name' property and either 'mark' containing the
588 mark time in microsecond, or 'accum' containing the
589 accumulated time for that bootstage id in microseconds.
594 name = "board_init_f";
603 Code in the Linux kernel can find this in /proc/devicetree.
605 config BOOTSTAGE_STASH
606 bool "Stash the boot timing information in memory before booting OS"
609 Some OSes do not support device tree. Bootstage can instead write
610 the boot timing information in a binary format at a given address.
611 This happens through a call to bootstage_stash(), typically in
612 the CPU's cleanup_before_linux() function. You can use the
613 'bootstage stash' and 'bootstage unstash' commands to do this on
616 config BOOTSTAGE_STASH_ADDR
617 hex "Address to stash boot timing information"
620 Provide an address which will not be overwritten by the OS when it
621 starts, so that it can read this information when ready.
623 config BOOTSTAGE_STASH_SIZE
624 hex "Size of boot timing stash region"
627 This should be large enough to hold the bootstage stash. A value of
628 4096 (4KiB) is normally plenty.
632 menu "Power commands"
634 bool "Enable Driver Model PMIC command"
637 This is the pmic command, based on a driver model pmic's API.
638 Command features are unchanged:
639 - list - list pmic devices
640 - pmic dev <id> - show or [set] operating pmic device (NEW)
641 - pmic dump - dump registers
642 - pmic read address - read byte of register at address
643 - pmic write address - write byte to register at address
644 The only one change for this command is 'dev' subcommand.
647 bool "Enable Driver Model REGULATOR command"
648 depends on DM_REGULATOR
650 This command is based on driver model regulator's API.
651 User interface features:
652 - list - list regulator devices
653 - regulator dev <id> - show or [set] operating regulator device
654 - regulator info - print constraints info
655 - regulator status - print operating status
656 - regulator value <val] <-f> - print/[set] voltage value [uV]
657 - regulator current <val> - print/[set] current value [uA]
658 - regulator mode <id> - print/[set] operating mode id
659 - regulator enable - enable the regulator output
660 - regulator disable - disable the regulator output
662 The '-f' (force) option can be used for set the value which exceeds
663 the limits, which are found in device-tree and are kept in regulator's
664 uclass platdata structure.
670 menu "Environment configuration settings"
673 prompt "Select environment non-volatile storage"
675 config ENV_IS_NOWHERE
676 bool "do not store environment"
678 config ENV_IS_IN_NAND
679 bool "store environment in NAND"
683 bool "store environment in MMC"
686 config ENV_IS_IN_SPI_FLASH
687 bool "store environment in SPI flash"
693 menu "Display configuration"
698 config DISPLAY_BOARDINFO
699 bool "Display board info"