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 GPL license text
49 Run the command stored in the environment "bootcmd", i.e.
50 "bootd" does the same thing as "run bootcmd".
56 Boot an application image from the memory.
62 Boot a Linux kernel zImage.
67 Boot a WindowsCE image.
73 Start an application at a given address.
79 Run the command in the given environment variable.
85 Print header information for application image.
91 List all images found in flash
97 Extract a part of a multi-image.
104 bool "Enable FDT commands"
106 config OF_BOARD_SETUP
107 bool "Support DT modifications by board code"
112 menu "Environment commands"
130 Edit environment variable.
136 Run the command in the given environment variable.
140 menu "Memory commands"
143 bool "md, mm, nm, mw, cp, cmp, base, loop"
148 mm - memory modify (auto-incrementing address)
149 nm - memory modify (constant address)
150 mw - memory write (fill)
153 base - print or set address offset
154 loop - initinite loop on address range
165 Infinite write loop on address range
170 Simple RAM read/write test.
175 mdc - memory display cyclic
176 mwc - memory write cyclic
181 Display memory information.
185 menu "Device access commands"
188 bool "dm - Access to driver model information"
192 Provides access to driver model data structures and information,
193 such as a list of devices, list of uclasses and the state of each
194 device (e.g. activated). This is not required for operation, but
195 can be useful to see the state of driver model for debugging or
199 bool "demo - Demonstration commands for driver model"
202 Provides a 'demo' command which can be used to play around with
203 driver model. To use this properly you will need to enable one or
204 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
205 Otherwise you will always get an empty list of devices. The demo
206 devices are defined in the sandbox device tree, so the easiest
207 option is to use sandbox and pass the -d point to sandbox's
214 Load a binary file over serial line.
220 Load an S-Record file over serial line
223 bool "flinfo, erase, protect"
224 default y if !SYS_NO_FLASH
227 flinfo - print FLASH memory information
229 protect - enable or disable FLASH write protection
232 depends on FLASH_CFI_DRIVER
235 ARM Ltd reference designs flash partition access
238 bool "MTD device support"
241 bool "MTD partitioning support"
243 depends on MTD_DEVICE && (CMD_FLASH || CMD_NAND)
250 config CMD_NAND_TRIMFFS
251 bool "Enable nand write.trimffs command"
253 Enable command to leave page sized runs of 0xff patterns in
254 erased state rather than overwriting them. This is required
255 for using NAND flash filesystems on NAND controllers with
256 a non-0xff ECC code for all 0xff data.
292 menu "Shell scripting commands"
304 Return true/false on integer compare.
310 Run script from memory
314 menu "Network commands"
317 bool "bootp, tftpboot"
321 bootp - boot image via network using BOOTP/TFTP protocol
322 tftpboot - boot image via network using TFTP protocol
327 TFTP put command, for uploading files to a server
332 Act as a TFTP server and boot the first received file
337 Boot image via network using RARP/TFTP protocol
342 Boot image via network using DHCP/TFTP protocol
348 config BOOTP_BOOTFILESIZE
349 bool "obtain bootfile size from DHCP"
351 config BOOTP_BOOTPATH
352 bool "obtain bootfile path from DHCP"
355 bool "obtain DNS server IP address from DHCP"
358 bool "store secondary DNS IP address in dnsip2"
361 bool "obtain gateway IP address from DHCP"
363 config BOOTP_ID_CACHE_SIZE
364 int "DHCP transaction ID cache size"
367 BOOTP packets are uniquely identified using a 32-bit ID. The
368 server will copy the ID from client requests to responses and
369 U-Boot will use this to determine if it is the destination of
370 an incoming response. Some servers will check that addresses
371 aren't in use before handing them out (usually using an ARP
372 ping) and therefore take up to a few hundred milliseconds to
373 respond. Network congestion may also influence the time it
374 takes for a response to make it back to the client. If that
375 time is too long, U-Boot will retransmit requests. In order
376 to allow earlier responses to still be accepted after these
377 retransmissions, U-Boot's BOOTP client keeps a small cache of
378 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
379 cache. The default is to keep IDs for up to four outstanding
380 requests. Increasing this will allow U-Boot to accept offers
381 from a BOOTP client in networks with unusually high latency.
383 config BOOTP_MAY_FAIL
384 bool "Do not start over, if DHCP server is not available"
386 If the DHCP server is not found after the configured retry
387 count, the call will fail instead of starting over. This
388 can be used to fail over to Link-local IP address
389 configuration if the DHCP server is not available.
391 config BOOTP_NISDOMAIN
392 bool "obtain NIS domain from DHCP"
394 config BOOTP_NTPSERVER
395 bool "obtain NTP server IP address from DHCP"
397 config BOOTP_RANDOM_DELAY
398 bool "Use a (pseudo) random delay between DHCP retries"
401 config BOOTP_RANDOM_ID
402 bool "Generate a (pseudo) random transaction ID"
405 config BOOTP_SEND_HOSTNAME
406 bool "send hostname in DHCP request"
408 config BOOTP_SUBNETMASK
409 bool "obtain subnet mask from DHCP"
411 config BOOTP_TIMEOFFSET
412 bool "obtain from DHCP"
414 config BOOTP_VENDOREX
415 bool "obtain from DHCP"
425 Boot image via network using NFS protocol.
430 Send ICMP ECHO_REQUEST to network host
435 Perform CDP network configuration
440 Synchronize RTC via network
445 Lookup the IP of a hostname
447 config CMD_LINK_LOCAL
450 Acquire a network IP address using the link-local protocol
453 bool "MII register access"
455 Support reading/writing ETH PHY registers via MII bus
464 Enable commands to switch data cache on/off.
469 Run commands and summarize execution time.
472 bool "fuse read/write"
474 eFuse reading and programming support
476 # TODO: rename to CMD_SLEEP
481 Delay execution for some time
486 Access the system timer.
489 bool "getdcr, setdcr, getidcr, setidcr"
493 getdcr - Get an AMCC PPC 4xx DCR's value
494 setdcr - Set an AMCC PPC 4xx DCR's value
495 getidcr - Get a register value via indirect DCR addressing
496 setidcr - Set a register value via indirect DCR addressing
503 bool "Boot timing and reporting"
505 Enable recording of boot time while booting. To use it, insert
506 calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
507 bootstage.h. Only a single entry is recorded for each ID. You can
508 give the entry a name with bootstage_mark_name(). You can also
509 record elapsed time in a particular stage using bootstage_start()
510 before starting and bootstage_accum() when finished. Bootstage will
511 add up all the accumated time and report it.
513 Normally, IDs are defined in bootstage.h but a small number of
514 additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
517 Calls to show_boot_progress() wil also result in log entries but
518 these will not have names.
520 config BOOTSTAGE_REPORT
521 bool "Display a detailed boot timing report before booting the OS"
524 Enable output of a boot time report just before the OS is booted.
525 This shows how long it took U-Boot to go through each stage of the
526 boot process. The report looks something like this:
528 Timer summary in microseconds:
531 3,575,678 3,575,678 board_init_f start
532 3,575,695 17 arch_cpu_init A9
533 3,575,777 82 arch_cpu_init done
534 3,659,598 83,821 board_init_r start
535 3,910,375 250,777 main_loop
536 29,916,167 26,005,792 bootm_start
537 30,361,327 445,160 start_kernel
539 config BOOTSTAGE_USER_COUNT
540 hex "Number of boot ID numbers available for user use"
543 This is the number of available user bootstage records.
544 Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
545 a new ID will be allocated from this stash. If you exceed
546 the limit, recording will stop.
549 bool "Enable the 'bootstage' command"
552 Add a 'bootstage' command which supports printing a report
553 and un/stashing of bootstage data.
556 bool "Store boot timing information in the OS device tree"
559 Stash the bootstage information in the FDT. A root 'bootstage'
560 node is created with each bootstage id as a child. Each child
561 has a 'name' property and either 'mark' containing the
562 mark time in microsecond, or 'accum' containing the
563 accumulated time for that bootstage id in microseconds.
568 name = "board_init_f";
577 Code in the Linux kernel can find this in /proc/devicetree.
579 config BOOTSTAGE_STASH
580 bool "Stash the boot timing information in memory before booting OS"
583 Some OSes do not support device tree. Bootstage can instead write
584 the boot timing information in a binary format at a given address.
585 This happens through a call to bootstage_stash(), typically in
586 the CPU's cleanup_before_linux() function. You can use the
587 'bootstage stash' and 'bootstage unstash' commands to do this on
590 config BOOTSTAGE_STASH_ADDR
591 hex "Address to stash boot timing information"
594 Provide an address which will not be overwritten by the OS when it
595 starts, so that it can read this information when ready.
597 config BOOTSTAGE_STASH_SIZE
598 hex "Size of boot timing stash region"
601 This should be large enough to hold the bootstage stash. A value of
602 4096 (4KiB) is normally plenty.
608 menu "Environment configuration settings"
611 prompt "Select environment non-volatile storage"
613 config ENV_IS_NOWHERE
614 bool "do not store environment"
616 config ENV_IS_IN_NAND
617 bool "store environment in NAND"
621 bool "store environment in MMC"
624 config ENV_IS_IN_SPI_FLASH
625 bool "store environment in SPI flash"
631 menu "Display configuration"
636 config DISPLAY_BOARDINFO
637 bool "Display board info"