1 menu "Command line interface"
4 bool "Support U-Boot commands"
7 Enable U-Boot's command-line functions. This provides a means
8 to enter commands into U-Boot for a wide variety of purposes. It
9 also allows scripts (containing commands) to be executed.
10 Various commands and command categorys can be indivdually enabled.
11 Depending on the number of commands enabled, this can add
12 substantially to the size of U-Boot.
18 This option enables the "hush" shell (from Busybox) as command line
19 interpreter, thus enabling powerful command line syntax like
20 if...then...else...fi conditionals or `&&' and '||'
21 constructs ("shell scripts").
23 If disabled, you get the old, much simpler behaviour with a somewhat
24 smaller memory footprint.
26 config CMDLINE_EDITING
27 bool "Enable command line editing"
31 Enable editing and History functions for interactive command line
35 bool "Enable auto complete using TAB"
39 Enable auto completion of commands using TAB.
42 bool "Enable long help messages"
46 Defined when you want long help messages included
47 Do not set this option when short of memory.
51 default "Zynq> " if ARCH_ZYNQ
52 default "ZynqMP> " if ARCH_ZYNQMP
55 This string is displayed in the command line to the left of the
58 config SYS_PROMPT_HUSH_PS2
59 string "Hush shell secondary prompt"
60 depends on HUSH_PARSER
63 This defines the secondary prompt string, which is
64 printed when the command interpreter needs more input
65 to complete a command. Usually "> ".
68 bool "Command execution tracer"
72 This option enables the possiblity to print all commands before
73 executing them and after all variables are evaluated (similar
74 to Bash's xtrace/'set -x' feature).
75 To enable the tracer a variable "xtrace" needs to be defined in
90 List and dump ACPI tables. ACPI (Advanced Configuration and Power
91 Interface) is used mostly on x86 for providing information to the
92 Operating System about devices in the system. The tables are set up
93 by the firmware, typically U-Boot but possibly an earlier firmware
94 module, if U-Boot is chain-loaded from something else. ACPI tables
95 can also include code, to perform hardware-specific tasks required
96 by the Operating Systems. This allows some amount of separation
97 between the firmware and OS, and is particularly useful when you
98 want to make hardware changes without the OS needing to be adjusted.
105 List non-identity virtual-physical memory mappings for 32-bit CPUs.
118 Print ".config" contents.
120 If this option is enabled, the ".config" file contents are embedded
121 in the U-Boot image and can be printed on the console by the "config"
122 command. This provides information of which options are enabled on
129 Print console devices and information.
135 Print information about available CPUs. This normally shows the
136 number of CPUs, type (e.g. manufacturer, architecture, product or
137 internal name) and clock frequency. Other information may be
138 available depending on the CPU driver.
144 Print GPL license text
149 Provides access to the Intel Power-Management Controller (PMC) so
150 that its state can be examined. This does not currently support
151 changing the state but it is still useful for debugging and seeing
160 config CMD_TLV_EEPROM
162 depends on I2C_EEPROM
164 Display and program the system EEPROM data block in ONIE Tlvinfo
165 format. TLV stands for Type-Length-Value.
167 config SPL_CMD_TLV_EEPROM
168 bool "tlv_eeprom for SPL"
169 depends on SPL_I2C_EEPROM
170 select SPL_DRIVERS_MISC_SUPPORT
172 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
176 depends on RISCV_SMODE && SBI_V02
178 Display information about the SBI implementation.
188 Run the command stored in the environment "bootcmd", i.e.
189 "bootd" does the same thing as "run bootcmd".
195 Boot an application image from the memory.
198 bool "Support booting UEFI FIT images"
199 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
202 Support booting UEFI FIT images via the bootm command.
207 Boot the Linux zImage
211 depends on ARM64 || RISCV
214 Boot an AArch64 Linux Kernel image from memory.
217 bool "Support booting Linux OS images"
218 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
221 Support booting the Linux kernel directly via a command such as bootm
225 bool "Support booting NetBSD (non-EFI) loader images"
229 Support booting NetBSD via the bootm command.
231 config BOOTM_OPENRTOS
232 bool "Support booting OPENRTOS / FreeRTOS images"
235 Support booting OPENRTOS / FreeRTOS via the bootm command.
238 bool "Support booting Enea OSE images"
239 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
242 Support booting Enea OSE images via the bootm command.
245 bool "Support booting Plan9 OS images"
249 Support booting Plan9 images via the bootm command.
252 bool "Support booting RTEMS OS images"
256 Support booting RTEMS images via the bootm command.
259 bool "Support booting VxWorks OS images"
263 Support booting VxWorks images via the bootm command.
267 depends on EFI_LOADER
270 Boot an EFI image from memory.
272 config CMD_BOOTEFI_HELLO_COMPILE
273 bool "Compile a standard EFI hello world binary for testing"
274 depends on CMD_BOOTEFI && !CPU_V7M
277 This compiles a standard EFI hello world application with U-Boot so
278 that it can be used with the test/py testing framework. This is useful
279 for testing that EFI is working at a basic level, and for bringing
280 up EFI support on a new architecture.
282 No additional space will be required in the resulting U-Boot binary
283 when this option is enabled.
285 config CMD_BOOTEFI_HELLO
286 bool "Allow booting a standard EFI hello world for testing"
287 depends on CMD_BOOTEFI_HELLO_COMPILE
288 default y if CMD_BOOTEFI_SELFTEST
290 This adds a standard EFI hello world application to U-Boot so that
291 it can be used with the 'bootefi hello' command. This is useful
292 for testing that EFI is working at a basic level, and for bringing
293 up EFI support on a new architecture.
295 source lib/efi_selftest/Kconfig
301 Add an ANSI terminal boot menu command.
306 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
307 image into RAM, dump image structure information, etc. Those dtb/dtbo
308 files should be merged in one dtb further, which needs to be passed to
309 the kernel, as part of a boot process.
313 depends on ANDROID_BOOT_IMAGE
315 Android Boot Image manipulation commands. Allows one to extract
316 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
317 obtain corresponding meta-information from boot.img.
319 See doc/android/boot-image.rst for details.
322 bool "bootelf, bootvx"
326 Boot an ELF/vxWorks image from the memory.
329 bool "Flattened Device Tree utility commands"
333 Do FDT related setup before booting into the Operating System.
339 Start an application at a given address.
345 Run the command in the given environment variable.
351 Print header information for application image.
356 List all images found in flash
362 Extract a part of a multi-image.
365 bool "spl export - Export boot information for Falcon boot"
368 Falcon mode allows booting directly from SPL into an Operating
369 System such as Linux, thus skipping U-Boot proper. See
370 doc/README.falcon for full information about how to use this
373 config CMD_SPL_NAND_OFS
374 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
375 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
378 This provides the offset of the command line arguments for Linux
379 when booting from NAND in Falcon mode. See doc/README.falcon
380 for full information about how to use this option (and also see
381 board/gateworks/gw_ventana/README for an example).
383 config CMD_SPL_NOR_OFS
384 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
385 depends on CMD_SPL && SPL_NOR_SUPPORT
388 This provides the offset of the command line arguments or dtb for
389 Linux when booting from NOR in Falcon mode.
391 config CMD_SPL_WRITE_SIZE
392 hex "Size of argument area"
396 This provides the size of the command-line argument area in NAND
397 flash used by Falcon-mode boot. See the documentation until CMD_SPL
400 config CMD_THOR_DOWNLOAD
401 bool "thor - TIZEN 'thor' download"
404 Implements the 'thor' download protocol. This is a way of
405 downloading a software update over USB from an attached host.
406 There is no documentation about this within the U-Boot source code
407 but you should be able to find something on the interwebs.
410 bool "zboot - x86 boot command"
412 With x86 machines it is common to boot a bzImage file which
413 contains both a kernel and a setup.bin file. The latter includes
414 configuration information from the dark ages which x86 boards still
415 need to pick things out of.
417 Consider using FIT in preference to this since it supports directly
418 booting both 32- and 64-bit kernels, as well as secure boot.
419 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
423 menu "Environment commands"
426 bool "ask for env variable"
428 Ask for environment variable
446 Edit environment variable.
451 Allow for searching environment variables
457 Save all environment variables into the compiled-in persistent
463 depends on CMD_SAVEENV
465 Erase environment variables from the compiled-in persistent
468 config CMD_ENV_EXISTS
472 Check if a variable is defined in the environment for use in
475 config CMD_ENV_CALLBACK
476 bool "env callbacks - print callbacks and their associated variables"
478 Some environment variable have callbacks defined by
479 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
480 For example changing "baudrate" adjust the serial baud rate. This
481 command lists the currently defined callbacks.
484 bool "env flags -print variables that have non-default flags"
486 Some environment variables have special flags that control their
487 behaviour. For example, serial# can only be written once and cannot
488 be deleted. This command shows the variables that have special
491 config CMD_NVEDIT_EFI
492 bool "env [set|print] -e - set/print UEFI variables"
493 depends on EFI_LOADER
496 UEFI variables are encoded as some form of U-Boot variables.
497 If enabled, we are allowed to set/print UEFI variables using
498 "env" command with "-e" option without knowing details.
500 config CMD_NVEDIT_INFO
501 bool "env info - print or evaluate environment information"
503 Print environment information:
504 - env_valid : is environment valid
505 - env_ready : is environment imported into hash table
506 - env_use_default : is default environment used
508 This command can be optionally used for evaluation in scripts:
509 [-d] : evaluate whether default environment is used
510 [-p] : evaluate whether environment can be persisted
512 The result of multiple evaluations will be combined with AND.
514 config CMD_NVEDIT_LOAD
517 Load all environment variables from the compiled-in persistent
520 config CMD_NVEDIT_SELECT
523 Select the compiled-in persistent storage of environment variables.
527 menu "Memory commands"
532 Compute binary operations (xor, or, and) of byte arrays of arbitrary
533 size from memory and store the result in memory or the environment.
537 default y if BLOBLIST
539 Show information about the bloblist, a collection of binary blobs
540 held in memory that persist between SPL and U-Boot. In the case of
541 x86 devices the bloblist can be used to hold ACPI tables so that they
542 remain available in memory.
555 Add -v option to verify data against a crc32 checksum.
558 bool "eeprom - EEPROM subsystem"
560 (deprecated, needs conversion to driver model)
561 Provides commands to read and write EEPROM (Electrically Erasable
562 Programmable Read Only Memory) chips that are connected over an
565 config CMD_EEPROM_LAYOUT
566 bool "Enable layout-aware eeprom commands"
567 depends on CMD_EEPROM
569 (deprecated, needs conversion to driver model)
570 When enabled, additional eeprom sub-commands become available.
572 eeprom print - prints the contents of the eeprom in a human-readable
573 way (eeprom layout fields, and data formatted to be fit for human
576 eeprom update - allows user to update eeprom fields by specifying
577 the field name, and providing the new data in a human readable format
578 (same format as displayed by the eeprom print command).
580 Both commands can either auto detect the layout, or be told which
584 __weak int parse_layout_version(char *str)
585 - override to provide your own layout name parsing
586 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
588 - override to setup the layout metadata based on the version
589 __weak int eeprom_layout_detect(unsigned char *data)
590 - override to provide your own algorithm for detecting layout
593 - contains various printing and updating functions for common
594 types of eeprom fields. Can be used for defining
597 config EEPROM_LAYOUT_HELP_STRING
598 string "Tells user what layout names are supported"
599 depends on CMD_EEPROM_LAYOUT
600 default "<not defined>"
602 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
608 Infinite write loop on address range
615 Compute MD5 checksum.
620 depends on CMD_MD5SUM
622 Add -v option to verify data against an MD5 checksum.
627 Display memory information.
630 bool "md, mm, nm, mw, cp, cmp, base, loop"
635 mm - memory modify (auto-incrementing address)
636 nm - memory modify (constant address)
637 mw - memory write (fill)
640 base - print or set address offset
641 loop - initialize loop on address range
643 config CMD_MEM_SEARCH
644 bool "ms - Memory search"
646 Memory-search command
648 This allows searching through a region of memory looking for hex
649 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
650 support it). It is also possible to search for a string. The
651 command accepts a memory range and a list of values to search for.
652 The values need to appear in memory in the same order they are given
653 in the command. At most 10 matches can be returned at a time, but
654 pressing return will show the next 10 matches. Environment variables
655 are set for use with scripting (memmatches, memaddr, mempos).
658 bool "Enable cyclic md/mw commands"
659 depends on CMD_MEMORY
661 Add the "mdc" and "mwc" memory commands. These are cyclic
666 This command will print 4 bytes (10,11,12,13) each 500 ms.
668 => mwc.l 100 12345678 10
669 This command will write 12345678 to address 100 all 10 ms.
674 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
676 random - fill memory with random data
681 Simple RAM read/write test.
685 config SYS_ALT_MEMTEST
686 bool "Alternative test"
688 Use a more complete alternative memory test.
692 config SYS_ALT_MEMTEST_BITFLIP
696 The alternative memory test includes bitflip test since 2020.07.
697 The bitflip test significantly increases the overall test time.
698 Bitflip test can optionally be disabled here.
702 config SYS_MEMTEST_START
703 hex "default start address for mtest"
706 This is the default start address for mtest for simple read/write
707 test. If no arguments are given to mtest, default address is used
710 config SYS_MEMTEST_END
711 hex "default end address for mtest"
714 This is the default end address for mtest for simple read/write
715 test. If no arguments are given to mtest, default address is used
724 Compute SHA1 checksum.
726 config SHA1SUM_VERIFY
728 depends on CMD_SHA1SUM
730 Add -v option to verify data against a SHA1 checksum.
733 bool "strings - display strings in memory"
735 This works similarly to the Unix 'strings' command except that it
736 works with a memory range. String of printable characters found
737 within the range are displayed. The minimum number of characters
738 for a sequence to be considered a string can be provided.
742 menu "Compression commands"
746 default y if CMD_BOOTI
749 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
754 default y if CMD_BOOTI
757 Support decompressing an LZ4 image from memory region.
761 default y if CMD_BOOTI
764 Uncompress a zip-compressed memory region.
768 select GZIP_COMPRESSED
770 Compress a memory region with zlib deflate method.
774 menu "Device access commands"
777 #depends on FLASH_CFI_DRIVER
780 ARM Ltd reference designs flash partition access
783 bool "adc - Access Analog to Digital Converters info and data"
785 depends on DM_REGULATOR
787 Shows ADC device info and permit printing one-shot analog converted
788 data from a named Analog to Digital Converter.
793 depends on PARTITIONS
795 Read/modify/write the fields of Bootloader Control Block, usually
796 stored on the flash "misc" partition with its structure defined in:
797 https://android.googlesource.com/platform/bootable/recovery/+/master/
798 bootloader_message/include/bootloader_message/bootloader_message.h
800 Some real-life use-cases include (but are not limited to):
801 - Determine the "boot reason" (and act accordingly):
802 https://source.android.com/devices/bootloader/boot-reason
803 - Get/pass a list of commands from/to recovery:
804 https://android.googlesource.com/platform/bootable/recovery
805 - Inspect/dump the contents of the BCB fields
808 bool "bind/unbind - Bind or unbind a device to/from a driver"
811 Bind or unbind a device to/from a driver from the command line.
812 This is useful in situations where a device may be handled by several
813 drivers. For example, this can be used to bind a UDC to the usb ether
814 gadget driver from the command line.
817 bool "clk - Show clock frequencies"
820 Shows clock frequences by calling a sock_clk_dump() hook function.
821 This is depreated in favour of using the CLK uclass and accessing
822 clock values from associated drivers. However currently no command
826 bool "demo - Demonstration commands for driver model"
829 Provides a 'demo' command which can be used to play around with
830 driver model. To use this properly you will need to enable one or
831 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
832 Otherwise you will always get an empty list of devices. The demo
833 devices are defined in the sandbox device tree, so the easiest
834 option is to use sandbox and pass the -d point to sandbox's
841 Enables the command "dfu" which is used to have U-Boot create a DFU
842 class device via USB. This command requires that the "dfu_alt_info"
843 environment variable be set and define the alt settings to expose to
847 bool "dm - Access to driver model information"
850 Provides access to driver model data structures and information,
851 such as a list of devices, list of uclasses and the state of each
852 device (e.g. activated). This is not required for operation, but
853 can be useful to see the state of driver model for debugging or
857 bool "fastboot - Android fastboot support"
860 This enables the command "fastboot" which enables the Android
861 fastboot mode for the platform. Fastboot is a protocol for
862 downloading images, flashing and device control used on
863 Android devices. Fastboot requires either the network stack
864 enabled or support for acting as a USB device.
866 See doc/android/fastboot.rst for more information.
869 bool "flinfo, erase, protect"
871 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
874 flinfo - print FLASH memory information
876 protect - enable or disable FLASH write protection
885 config CMD_FPGA_LOADBP
886 bool "fpga loadbp - load partial bitstream (Xilinx only)"
889 Supports loading an FPGA device from a bitstream buffer containing
892 config CMD_FPGA_LOADFS
893 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
896 Supports loading an FPGA device from a FAT filesystem.
898 config CMD_FPGA_LOADMK
899 bool "fpga loadmk - load bitstream from image"
902 Supports loading an FPGA device from a image generated by mkimage.
904 config CMD_FPGA_LOADP
905 bool "fpga loadp - load partial bitstream"
908 Supports loading an FPGA device from a bitstream buffer containing
911 config CMD_FPGA_LOAD_SECURE
912 bool "fpga loads - loads secure bitstreams (Xilinx only)"
915 Enables the fpga loads command which is used to load secure
916 (authenticated or encrypted or both) bitstreams on to FPGA.
919 bool "fpgad - dump FPGA registers"
921 (legacy, needs conversion to driver model)
922 Provides a way to dump FPGA registers by calling the board-specific
923 fpga_get_reg() function. This functions similarly to the 'md'
927 bool "fuse - support for the fuse subssystem"
929 (deprecated - needs conversion to driver model)
930 This allows reading, sensing, programming or overriding fuses
931 which control the behaviour of the device. The command uses the
943 Control PWM channels, this allows invert/config/enable/disable PWM channels.
946 bool "GPT (GUID Partition Table) command"
948 select HAVE_BLOCK_DEVICE
949 select PARTITION_UUIDS
952 Enable the 'gpt' command to ready and write GPT style partition
956 bool "GPT Random UUID generation"
959 Enable the generation of partitions with random UUIDs if none
962 config CMD_GPT_RENAME
963 bool "GPT partition renaming commands"
966 Enables the 'gpt' command to interchange names on two GPT
967 partitions via the 'gpt swap' command or to rename single
968 partitions via the 'rename' command.
971 bool "ide - Support for IDE drivers"
974 Provides an 'ide' command which allows accessing the IDE drive,
975 reseting the IDE interface, printing the partition table and
976 geting device info. It also enables the 'diskboot' command which
977 permits booting from an IDE drive.
980 bool "io - Support for performing I/O accesses"
982 Provides an 'iod' command to display I/O space and an 'iow' command
983 to write values to the I/O space. This can be useful for manually
984 checking the state of devices during boot when debugging device
988 bool "iotrace - Support for tracing I/O activity"
990 Provides an 'iotrace' command which supports recording I/O reads and
991 writes in a trace buffer in memory . It also maintains a checksum
992 of the trace records (even if space is exhausted) so that the
993 sequence of I/O accesses can be verified.
995 When debugging drivers it is useful to see what I/O accesses were
996 done and in what order.
998 Even if the individual accesses are of little interest it can be
999 useful to verify that the access pattern is consistent each time
1000 an operation is performed. In this case a checksum can be used to
1001 characterise the operation of a driver. The checksum can be compared
1002 across different runs of the operation to verify that the driver is
1005 In particular, when performing major refactoring of the driver, where
1006 the access pattern should not change, the checksum provides assurance
1007 that the refactoring work has not broken the driver.
1009 This works by sneaking into the io.h heder for an architecture and
1010 redirecting I/O accesses through iotrace's tracing mechanism.
1012 For now no commands are provided to examine the trace buffer. The
1013 format is fairly simple, so 'md' is a reasonable substitute.
1015 Note: The checksum feature is only useful for I/O regions where the
1016 contents do not change outside of software control. Where this is not
1017 suitable you can fall back to manually comparing the addresses. It
1018 might be useful to enhance tracing to only checksum the accesses and
1019 not the data read/written.
1029 bool "w1 - Support for Dallas 1-Wire protocol"
1031 Dallas 1-wire protocol support
1037 Load a binary file over serial line.
1043 Load an S-Record file over serial line
1047 bool "lsblk - list block drivers and devices"
1049 Print list of available block device drivers, and for each, the list
1050 of known block devices.
1053 bool "MBR (Master Boot Record) command"
1054 select DOS_PARTITION
1055 select HAVE_BLOCK_DEVICE
1057 Enable the 'mbr' command to ready and write MBR (Master Boot Record)
1058 style partition tables.
1064 Enable the command "misc" for accessing miscellaneous devices with
1065 a MISC uclass driver. The command provides listing all MISC devices
1066 as well as read and write functionalities via their drivers.
1072 MMC memory mapped support.
1076 config CMD_BKOPS_ENABLE
1077 bool "mmc bkops enable"
1081 Enable command for setting manual background operations handshake
1082 on a eMMC device. The feature is optionally available on eMMC devices
1083 conforming to standard >= 4.41.
1086 bool "Enable support for RPMB in the mmc command"
1087 depends on SUPPORT_EMMC_RPMB
1089 Enable the commands for reading, writing and programming the
1090 key for the Replay Protection Memory Block partition in eMMC.
1092 config CMD_MMC_SWRITE
1094 depends on MMC_WRITE
1097 Enable support for the "mmc swrite" command to write Android sparse
1106 Enable storage cloning over block devices, useful for
1107 initial flashing by external block device without network
1110 config CMD_OPTEE_RPMB
1111 bool "Enable read/write support on RPMB via OPTEE"
1112 depends on SUPPORT_EMMC_RPMB && OPTEE
1114 Enable the commands for reading, writing persistent named values
1115 in the Replay Protection Memory Block partition in eMMC by
1116 using Persistent Objects in OPTEE
1121 select MTD_PARTITIONS
1123 MTD commands support.
1127 depends on MULTIPLEXER
1129 List, select, and deselect mux controllers on the fly.
1133 default y if NAND_SUNXI
1134 depends on MTD_RAW_NAND
1139 config CMD_NAND_TRIMFFS
1140 bool "nand write.trimffs"
1141 default y if ARCH_SUNXI
1143 Allows one to skip empty pages when flashing something on a NAND.
1145 config CMD_NAND_LOCK_UNLOCK
1146 bool "nand lock/unlock"
1148 NAND locking support.
1150 config CMD_NAND_TORTURE
1153 NAND torture support.
1162 NVM Express device support
1165 bool "onenand - access to onenand device"
1168 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1169 various useful features. This command allows reading, writing,
1170 and erasing blocks. It allso provides a way to show and change
1171 bad blocks, and test the device.
1176 Enable the 'osd' command which allows to query information from and
1177 write text data to a on-screen display (OSD) device; a virtual device
1178 associated with a display capable of displaying a text overlay on the
1179 display it's associated with..
1183 select HAVE_BLOCK_DEVICE
1184 select PARTITION_UUIDS
1186 Read and display information about the partition table on
1190 bool "pci - Access PCI devices"
1192 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1193 used on some devices to allow the CPU to communicate with its
1194 peripherals. Sub-commands allow bus enumeration, displaying and
1195 changing configuration space and a few other features.
1198 bool "pinmux - show pins muxing"
1200 default y if PINCTRL
1202 Parse all available pin-controllers and show pins muxing. This
1203 is useful for debug purpoer to check the pin muxing and to know if
1204 a pin is configured as a GPIO or as an alternate function.
1209 Poweroff/Shutdown the system
1212 bool "read - Read binary data from a partition"
1214 Provides low-level access to the data in a partition.
1216 config CMD_REMOTEPROC
1218 depends on REMOTEPROC
1220 Support for Remote Processor control
1223 bool "sata - Access SATA subsystem"
1226 SATA (Serial Advanced Technology Attachment) is a serial bus
1227 standard for connecting to hard drives and other storage devices.
1228 This command provides information about attached devices and allows
1229 reading, writing and other operations.
1231 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1232 Attachment, where AT refers to an IBM AT (Advanced Technology)
1233 computer released in 1984.
1236 bool "saves - Save a file over serial in S-Record format"
1238 Provides a way to save a binary file using the Motorola S-Record
1239 format over the serial line.
1242 bool "scsi - Access to SCSI devices"
1245 This provides a 'scsi' command which provides access to SCSI (Small
1246 Computer System Interface) devices. The command provides a way to
1247 scan the bus, reset the bus, read and write data and get information
1251 bool "sdram - Print SDRAM configuration information"
1253 Provides information about attached SDRAM. This assumed that the
1254 SDRAM has an EEPROM with information that can be read using the
1255 I2C bus. This is only available on some boards.
1259 depends on DM_SPI_FLASH || SPI_FLASH
1260 default y if DM_SPI_FLASH
1265 bool "sf test - Allow testing of SPI flash"
1268 Provides a way to test that SPI flash is working correctly. The
1269 test is destructive, in that an area of SPI flash must be provided
1270 for the test to use. Performance information is also provided,
1271 measuring the performance of reading, writing and erasing in
1272 Mbps (Million Bits Per Second). This value should approximately
1273 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1274 everything is working properly.
1277 bool "sspi - Command to access spi device"
1280 SPI utility command.
1282 config DEFAULT_SPI_BUS
1283 int "default spi bus used by sspi command"
1287 config DEFAULT_SPI_MODE
1288 hex "default spi mode used by sspi command (see include/spi.h)"
1293 bool "tsi148 - Command to access tsi148 device"
1295 This provides various sub-commands to initialise and configure the
1296 Turndra tsi148 device. See the command help for full details.
1299 bool "Enable UFS - Universal Flash Subsystem commands"
1302 "This provides commands to initialise and configure universal flash
1306 bool "universe - Command to set up the Turndra Universe controller"
1308 This allows setting up the VMEbus provided by this controller.
1309 See the command help for full details.
1314 select HAVE_BLOCK_DEVICE
1320 select USB_FUNCTION_SDP
1322 Enables the command "sdp" which is used to have U-Boot emulating the
1323 Serial Download Protocol (SDP) via USB.
1327 depends on USB_FUNCTION_ROCKUSB
1329 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1330 read/write info, image to/from devices. This enable rockusb command
1331 support to communication with rockusb device. for more detail about
1332 this command, please read doc/README.rockusb.
1334 config CMD_USB_MASS_STORAGE
1335 bool "UMS usb mass storage"
1336 select USB_FUNCTION_MASS_STORAGE
1338 USB mass storage support
1341 bool "Xen para-virtualized block device"
1345 Xen para-virtualized block device support
1350 depends on HAVE_BLOCK_DEVICE
1353 VirtIO block device support
1359 This provides commands to control the watchdog timer devices.
1365 Enable the command "axi" for accessing AXI (Advanced eXtensible
1366 Interface) busses, a on-chip interconnect specification for managing
1367 functional blocks in SoC designs, which is also often used in designs
1368 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1372 menu "Shell scripting commands"
1378 Echo args to console
1384 Return true/false on integer compare.
1390 Run script from memory
1396 Evaluate boolean and math expressions and store the result in an env
1398 Also supports loading the value at a memory location into a variable.
1399 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1403 menu "Android support commands"
1405 config CMD_AB_SELECT
1408 depends on ANDROID_AB
1410 On Android devices with more than one boot slot (multiple copies of
1411 the kernel and system images) this provides a command to select which
1412 slot should be used to boot from and register the boot attempt. This
1413 is used by the new A/B update model where one slot is updated in the
1414 background while running from the other slot.
1421 bool "Network commands"
1431 bootp - boot image via network using BOOTP/TFTP protocol
1435 depends on CMD_BOOTP
1437 Boot image via network using DHCP/TFTP protocol
1439 config BOOTP_BOOTPATH
1440 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1442 depends on CMD_BOOTP
1444 Even though the config is called BOOTP_BOOTPATH, it stores the
1445 path in the variable 'rootpath'.
1448 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1450 depends on CMD_BOOTP
1452 The primary DNS server is stored as 'dnsip'. If two servers are
1453 returned, you must set BOOTP_DNS2 to store that second server IP
1457 bool "Store 'dnsip2' from BOOTP/DHCP server"
1458 depends on BOOTP_DNS
1460 If a DHCP client requests the DNS server IP from a DHCP server,
1461 it is possible that more than one DNS serverip is offered to the
1462 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1463 server IP will be stored in the additional environment
1464 variable "dnsip2". The first DNS serverip is always
1465 stored in the variable "dnsip", when BOOTP_DNS is defined.
1467 config BOOTP_GATEWAY
1468 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1470 depends on CMD_BOOTP
1472 config BOOTP_HOSTNAME
1473 bool "Request & store 'hostname' from BOOTP/DHCP server"
1475 depends on CMD_BOOTP
1477 The name may or may not be qualified with the local domain name.
1479 config BOOTP_PREFER_SERVERIP
1480 bool "serverip variable takes precedent over DHCP server IP."
1481 depends on CMD_BOOTP
1483 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1485 With this option enabled, the 'serverip' variable in the environment
1486 takes precedence over DHCP server IP and will only be set by the DHCP
1487 server if not already set in the environment.
1489 config BOOTP_SUBNETMASK
1490 bool "Request & store 'netmask' from BOOTP/DHCP server"
1492 depends on CMD_BOOTP
1494 config BOOTP_NTPSERVER
1495 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1496 depends on CMD_BOOTP
1501 Selecting this will allow capturing all Ethernet packets and store
1502 them in physical memory in a PCAP formated file,
1503 later to be analyzed by PCAP reader application (IE. WireShark).
1506 bool "Send PXE client arch to BOOTP/DHCP server"
1508 depends on CMD_BOOTP && CMD_PXE
1510 Supported for ARM, ARM64, and x86 for now.
1512 config BOOTP_PXE_CLIENTARCH
1514 depends on BOOTP_PXE
1515 default 0x16 if ARM64
1519 config BOOTP_VCI_STRING
1521 depends on CMD_BOOTP
1522 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1523 default "U-Boot.armv8" if ARM64
1524 default "U-Boot.arm" if ARM
1531 tftpboot - boot image via network using TFTP protocol
1535 depends on CMD_TFTPBOOT
1537 TFTP put command, for uploading files to a server
1541 depends on CMD_TFTPBOOT
1543 Act as a TFTP server and boot the first received file
1545 config NET_TFTP_VARS
1546 bool "Control TFTP timeout and count through environment"
1547 depends on CMD_TFTPBOOT
1550 If set, allows controlling the TFTP timeout through the
1551 environment variable tftptimeout, and the TFTP maximum
1552 timeout count through the variable tftptimeoutcountmax.
1553 If unset, timeout and maximum are hard-defined as 1 second
1554 and 10 timouts per TFTP transfer.
1559 Boot image via network using RARP/TFTP protocol
1565 Boot image via network using NFS protocol.
1571 If set, allows 802.3(clause 22) MII Management functions interface access
1572 The management interface specified in Clause 22 provides
1573 a simple, two signal, serial interface to connect a
1574 Station Management entity and a managed PHY for providing access
1575 to management parameters and services.
1576 The interface is referred to as the MII management interface.
1582 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1583 The MDIO interface is orthogonal to the MII interface and extends
1584 it by adding access to more registers through indirect addressing.
1589 Send ICMP ECHO_REQUEST to network host
1594 Perform CDP network configuration
1600 Synchronize RTC via network
1605 Lookup the IP of a hostname
1607 config CMD_LINK_LOCAL
1611 Acquire a network IP address using the link-local protocol
1618 Allow control of L2 Ethernet switch commands. These are supported
1619 by the vsc9953 Ethernet driver at present. Sub-commands allow
1620 operations such as enabling / disabling a port and
1621 viewing/maintaining the filtering database (FDB)
1627 Boot image via network using PXE protocol
1632 Wait for wake-on-lan Magic Packet
1636 menu "Misc commands"
1639 bool "Enable 'bmp' command"
1640 depends on LCD || DM_VIDEO || VIDEO
1642 This provides a way to obtain information about a BMP-format image
1643 and to display it. BMP (which presumably stands for BitMaP) is a
1644 file format defined by Microsoft which supports images of various
1645 depths, formats and compression methods. Headers on the file
1646 determine the formats used. This command can be used by first loading
1647 the image into RAM, then using this command to look at it or display
1650 config CMD_BOOTCOUNT
1652 depends on BOOTCOUNT_LIMIT
1654 Enable the bootcount command, which allows interrogation and
1655 reset of the bootcounter.
1658 bool "Enable board-specific commands"
1660 (deprecated: instead, please define a Kconfig option for each command)
1662 Some boards have board-specific commands which are only enabled
1663 during developemnt and need to be turned off for production. This
1664 option provides a way to control this. The commands that are enabled
1665 vary depending on the board.
1667 config CMD_BLOCK_CACHE
1668 bool "blkcache - control and stats for block cache"
1669 depends on BLOCK_CACHE
1670 default y if BLOCK_CACHE
1672 Enable the blkcache command, which can be used to control the
1673 operation of the cache functions.
1674 This is most useful when fine-tuning the operation of the cache
1675 during development, but also allows the cache to be disabled when
1676 it might hurt performance (e.g. when using the ums command).
1683 Enable the 'button' command which allows to get the status of
1684 buttons supported by the board. The buttonss can be listed with
1685 'button list' and state can be known with 'button <label>'.
1686 Any button drivers can be controlled with this command, e.g.
1690 bool "icache or dcache"
1692 Enable the "icache" and "dcache" commands
1694 config CMD_CONITRACE
1695 bool "conitrace - trace console input codes"
1697 Enable the 'conitrace' command which displays the codes received
1698 from the console input as hexadecimal numbers.
1701 bool "Enable clear screen command 'cls'"
1702 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1705 Enable the 'cls' command which clears the screen contents
1706 on video frame buffer.
1709 bool "efidebug - display/configure UEFI environment"
1710 depends on EFI_LOADER
1711 select EFI_DEVICE_PATH_TO_TEXT
1714 Enable the 'efidebug' command which provides a subset of UEFI
1715 shell utility with simplified functionality. It will be useful
1716 particularly for managing boot parameters as well as examining
1717 various EFI status for debugging.
1719 config CMD_EXCEPTION
1720 bool "exception - raise exception"
1721 depends on ARM || RISCV || SANDBOX || X86
1723 Enable the 'exception' command which allows to raise an exception.
1730 Enable the 'led' command which allows for control of LEDs supported
1731 by the board. The LEDs can be listed with 'led list' and controlled
1732 with led on/off/togle/blink. Any LED drivers can be controlled with
1733 this command, e.g. led_gpio.
1740 Enable the 'date' command for getting/setting the time/date in RTC
1747 Enable the 'rtc' command for low-level access to RTC devices.
1752 Run commands and summarize execution time.
1755 bool "gettime - read elapsed time"
1757 Enable the 'gettime' command which reads the elapsed time since
1758 U-Boot started running. This shows the time in seconds and
1759 milliseconds. See also the 'bootstage' command which provides more
1760 flexibility for boot timing.
1767 Print bytes from the hardware random number generator.
1773 Delay execution for some time
1776 bool "support for multiprocessor"
1778 This provides an option to brinup
1779 different processors in multiprocessor
1785 Access the system timer.
1791 This provides basic access to the U-Boot's sound support. The main
1792 feature is to play a beep.
1794 sound init - set up sound system
1795 sound play - play a sound
1801 Boot image via local extlinux.conf file
1807 This provides access to the QEMU firmware interface. The main
1808 feature is to allow easy loading of files passed to qemu-system
1809 via -kernel / -initrd
1814 This provides access to Linux PStore with Rammoops backend. The main
1815 feature is to allow to display or save PStore records.
1817 See doc/pstore.rst for more information.
1821 config CMD_PSTORE_MEM_ADDR
1822 hex "Memory Address"
1823 depends on CMD_PSTORE
1825 Base addr used for PStore ramoops memory, should be identical to
1826 ramoops.mem_address parameter used by kernel
1828 config CMD_PSTORE_MEM_SIZE
1830 depends on CMD_PSTORE
1833 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1834 parameter used by kernel, a power of 2 and larger than the sum of the
1837 config CMD_PSTORE_RECORD_SIZE
1838 hex "Dump record size"
1839 depends on CMD_PSTORE
1842 Size of each dump done on oops/panic, should be identical to
1843 ramoops.record_size parameter used by kernel and a power of 2
1846 config CMD_PSTORE_CONSOLE_SIZE
1847 hex "Kernel console log size"
1848 depends on CMD_PSTORE
1851 Size of kernel console log, should be identical to
1852 ramoops.console_size parameter used by kernel and a power of 2
1855 config CMD_PSTORE_FTRACE_SIZE
1856 hex "FTrace log size"
1857 depends on CMD_PSTORE
1860 Size of ftrace log, should be identical to ramoops.ftrace_size
1861 parameter used by kernel and a power of 2
1863 config CMD_PSTORE_PMSG_SIZE
1864 hex "User space message log size"
1865 depends on CMD_PSTORE
1868 Size of user space message log, should be identical to
1869 ramoops.pmsg_size parameter used by kernel and a power of 2
1871 config CMD_PSTORE_ECC_SIZE
1873 depends on CMD_PSTORE
1876 if non-zero, the option enables ECC support and specifies ECC buffer
1877 size in bytes (1 is a special value, means 16 bytes ECC), should be
1878 identical to ramoops.ramoops_ecc parameter used by kernel
1882 source "cmd/mvebu/Kconfig"
1885 bool "terminal - provides a way to attach a serial terminal"
1887 Provides a 'cu'-like serial terminal command. This can be used to
1888 access other serial ports from the system console. The terminal
1889 is very simple with no special processing of characters. As with
1890 cu, you can press ~. (tilde followed by period) to exit.
1893 bool "uuid, guid - generation of unique IDs"
1896 This enables two commands:
1898 uuid - generate random Universally Unique Identifier
1899 guid - generate Globally Unique Identifier based on random UUID
1901 The two commands are very similar except for the endianness of the
1906 source "cmd/ti/Kconfig"
1908 config CMD_BOOTSTAGE
1909 bool "Enable the 'bootstage' command"
1910 depends on BOOTSTAGE
1912 Add a 'bootstage' command which supports printing a report
1913 and un/stashing of bootstage data.
1915 menu "Power commands"
1917 bool "Enable Driver Model PMIC command"
1920 This is the pmic command, based on a driver model pmic's API.
1921 Command features are unchanged:
1922 - list - list pmic devices
1923 - pmic dev <id> - show or [set] operating pmic device (NEW)
1924 - pmic dump - dump registers
1925 - pmic read address - read byte of register at address
1926 - pmic write address - write byte to register at address
1927 The only one change for this command is 'dev' subcommand.
1929 config CMD_REGULATOR
1930 bool "Enable Driver Model REGULATOR command"
1931 depends on DM_REGULATOR
1933 This command is based on driver model regulator's API.
1934 User interface features:
1935 - list - list regulator devices
1936 - regulator dev <id> - show or [set] operating regulator device
1937 - regulator info - print constraints info
1938 - regulator status - print operating status
1939 - regulator value <val] <-f> - print/[set] voltage value [uV]
1940 - regulator current <val> - print/[set] current value [uA]
1941 - regulator mode <id> - print/[set] operating mode id
1942 - regulator enable - enable the regulator output
1943 - regulator disable - disable the regulator output
1945 The '-f' (force) option can be used for set the value which exceeds
1946 the limits, which are found in device-tree and are kept in regulator's
1947 uclass plat structure.
1951 menu "Security commands"
1953 bool "Enable the 'aes' command"
1956 This provides a means to encrypt and decrypt data using the AES
1957 (Advanced Encryption Standard). This algorithm uses a symetric key
1958 and is widely used as a streaming cipher. Different key lengths are
1959 supported by the algorithm but this command only supports 128 bits
1963 bool "Enable the 'blob' command"
1964 depends on !MX6ULL && !MX6SLL && !MX6SL
1965 select IMX_HAB if ARCH_MX6 || ARCH_MX7 || ARCH_MX7ULP || ARCH_IMX8M
1967 This is used with the Freescale secure boot mechanism.
1969 Freescale's SEC block has built-in Blob Protocol which provides
1970 a method for protecting user-defined data across system power
1971 cycles. SEC block protects data in a data structure called a Blob,
1972 which provides both confidentiality and integrity protection.
1974 Encapsulating data as a blob
1975 Each time that the Blob Protocol is used to protect data, a
1976 different randomly generated key is used to encrypt the data.
1977 This random key is itself encrypted using a key which is derived
1978 from SoC's non-volatile secret key and a 16 bit Key identifier.
1979 The resulting encrypted key along with encrypted data is called a
1980 blob. The non-volatile secure key is available for use only during
1983 During decapsulation, the reverse process is performed to get back
1987 blob enc - encapsulating data as a cryptgraphic blob
1988 blob dec - decapsulating cryptgraphic blob to get the data
1992 blob enc src dst len km
1994 Encapsulate and create blob of data $len bytes long
1995 at address $src and store the result at address $dst.
1996 $km is the 16 byte key modifier is also required for
1997 generation/use as key for cryptographic operation. Key
1998 modifier should be 16 byte long.
2000 blob dec src dst len km
2002 Decapsulate the blob of data at address $src and
2003 store result of $len byte at addr $dst.
2004 $km is the 16 byte key modifier is also required for
2005 generation/use as key for cryptographic operation. Key
2006 modifier should be 16 byte long.
2009 bool "Support 'hash' command"
2012 This provides a way to hash data in memory using various supported
2013 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
2014 saved to memory or to an environment variable. It is also possible
2015 to verify a hash against data in memory.
2018 bool "Support the 'hvc' command"
2019 depends on ARM_SMCCC
2021 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
2022 development and testing.
2025 bool "Support the 'smc' command"
2026 depends on ARM_SMCCC
2028 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
2029 development and testing.
2035 Add -v option to verify data against a hash.
2038 bool "scp03 - SCP03 enable and rotate/provision operations"
2041 This command provides access to a Trusted Application
2042 running in a TEE to request Secure Channel Protocol 03
2043 (SCP03) enablement and/or rotation of its SCP03 keys.
2052 bool "Enable the 'tpm' command"
2053 depends on TPM_V1 || TPM_V2
2054 select CMD_TPM_V1 if TPM_V1
2055 select CMD_TPM_V2 if TPM_V2
2057 This provides a means to talk to a TPM from the command line. A wide
2058 range of commands if provided - see 'tpm help' for details. The
2059 command requires a suitable TPM on your board and the correct driver
2065 bool "Enable the 'tpm test' command"
2068 This provides a a series of tests to confirm that the TPMv1.x is
2069 working correctly. The tests cover initialisation, non-volatile RAM,
2070 extend, global lock and checking that timing is within expectations.
2071 The tests pass correctly on Infineon TPMs but may need to be adjusted
2078 menu "Firmware commands"
2080 bool "Enable crosec command"
2084 Enable command-line access to the Chrome OS EC (Embedded
2085 Controller). This provides the 'crosec' command which has
2086 a number of sub-commands for performing EC tasks such as
2087 updating its flash, accessing a small saved context area
2088 and talking to the I2C bus behind the EC (if there is one).
2091 menu "Filesystem commands"
2093 bool "Enable the 'btrsubvol' command"
2096 This enables the 'btrsubvol' command to list subvolumes
2097 of a BTRFS filesystem. There are no special commands for
2098 listing BTRFS directories or loading BTRFS files - this
2099 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2100 when BTRFS is enabled (see FS_BTRFS).
2103 bool "Enable the 'cbfs' command"
2106 Define this to enable support for reading from a Coreboot
2107 filesystem. This is a ROM-based filesystem used for accessing files
2108 on systems that use coreboot as the first boot-loader and then load
2109 U-Boot to actually boot the Operating System. Available commands are
2110 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2113 bool "Enable the 'cramfs' command"
2114 depends on FS_CRAMFS
2116 This provides commands for dealing with CRAMFS (Compressed ROM
2117 filesystem). CRAMFS is useful when space is tight since files are
2118 compressed. Two commands are provided:
2120 cramfsls - lists files in a cramfs image
2121 cramfsload - loads a file from a cramfs image
2124 bool "ext2 command support"
2127 Enables EXT2 FS command
2130 bool "ext4 command support"
2133 Enables EXT4 FS command
2135 config CMD_EXT4_WRITE
2137 bool "ext4 write command support"
2140 Enables EXT4 FS write command
2143 bool "FAT command support"
2146 Support for the FAT fs
2149 bool "SquashFS command support"
2152 Enables SquashFS filesystem commands (e.g. load, ls).
2154 config CMD_FS_GENERIC
2155 bool "filesystem commands"
2157 Enables filesystem commands (e.g. load, ls) that work for multiple
2161 bool "fsuuid command"
2163 Enables fsuuid command for filesystem UUID.
2166 bool "jffs2 command"
2169 Enables commands to support the JFFS2 (Journalling Flash File System
2170 version 2) filesystem. This enables fsload, ls and fsinfo which
2171 provide the ability to load files, list directories and obtain
2172 filesystem information.
2175 bool "MTD partition support"
2178 MTD partitioning tool support.
2179 It is strongly encouraged to avoid using this command
2180 anymore along with 'sf', 'nand', 'onenand'. One can still
2181 declare the partitions in the mtdparts environment variable
2182 but better use the MTD stack and the 'mtd' command instead.
2184 config CMD_MTDPARTS_SPREAD
2185 bool "Padd partition size to take account of bad blocks"
2186 depends on CMD_MTDPARTS
2188 This enables the 'spread' sub-command of the mtdparts command.
2189 This command will modify the existing mtdparts variable by increasing
2190 the size of the partitions such that 1) each partition's net size is
2191 at least as large as the size specified in the mtdparts variable and
2192 2) each partition starts on a good block.
2194 config CMD_MTDPARTS_SHOW_NET_SIZES
2195 bool "Show net size (w/o bad blocks) of partitions"
2196 depends on CMD_MTDPARTS
2198 Adds two columns to the printed partition table showing the
2199 effective usable size of a partition, if bad blocks are taken
2202 config MTDIDS_DEFAULT
2203 string "Default MTD IDs"
2204 depends on MTD || SPI_FLASH
2206 Defines a default MTD IDs list for use with MTD partitions in the
2207 Linux MTD command line partitions format.
2209 config MTDPARTS_DEFAULT
2210 string "Default MTD partition scheme"
2211 depends on MTD || SPI_FLASH
2213 Defines a default MTD partitioning scheme in the Linux MTD command
2214 line partitions format
2217 bool "reiser - Access to reiserfs filesystems"
2219 This provides two commands which operate on a resierfs filesystem,
2220 commonly used some years ago:
2222 reiserls - list files
2223 reiserload - load a file
2226 bool "yaffs2 - Access of YAFFS2 filesystem"
2230 This provides commands for accessing a YAFFS2 filesystem. Yet
2231 Another Flash Filesystem 2 is a filesystem designed specifically
2232 for NAND flash. It incorporates bad-block management and ensures
2233 that device writes are sequential regardless of filesystem
2237 bool "zfs - Access of ZFS filesystem"
2239 This provides commands to accessing a ZFS filesystem, commonly used
2240 on Solaris systems. Two sub-commands are provided:
2242 zfsls - list files in a directory
2243 zfsload - load a file
2245 See doc/README.zfs for more details.
2249 menu "Debug commands"
2254 The bedbug (emBEDded deBUGger) command provides debugging features
2255 for some PowerPC processors. For details please see the
2256 documentation in doc/README.bedbug.
2258 config CMD_CBSYSINFO
2261 default y if SYS_COREBOOT
2263 This provides information about the coreboot sysinfo table stored in
2264 memory by coreboot before jumping to U-Boot. It can be useful for
2265 debugging the beaaviour of coreboot or U-Boot.
2268 bool "diag - Board diagnostics"
2270 This command provides access to board diagnostic tests. These are
2271 called Power-on Self Tests (POST). The command allows listing of
2272 available tests and running either all the tests, or specific tests
2276 bool "irq - Show information about interrupts"
2277 depends on !ARM && !MIPS && !RISCV && !SH
2279 This enables two commands:
2281 interrupts - enable or disable interrupts
2282 irqinfo - print device-specific interrupt information
2285 bool "kgdb - Allow debugging of U-Boot with gdb"
2288 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2289 over a serial link for debugging purposes. This allows
2290 single-stepping, inspecting variables, etc. This is supported only
2291 on PowerPC at present.
2294 bool "log - Generation, control and access to logging"
2298 This provides access to logging features. It allows the output of
2299 log data to be controlled to a limited extent (setting up the default
2300 maximum log level for emitting of records). It also provides access
2301 to a command used for testing the log system.
2304 bool "trace - Support tracing of function calls and timing"
2306 Enables a command to control using of function tracing within
2307 U-Boot. This allows recording of call traces including timing
2308 information. The command can write data to memory for exporting
2309 for analysis (e.g. using bootchart). See doc/README.trace for full
2313 bool "avb - Android Verified Boot 2.0 operations"
2314 depends on AVB_VERIFY
2317 Enables a "avb" command to perform verification of partitions using
2318 Android Verified Boot 2.0 functionality. It includes such subcommands:
2319 avb init - initialize avb2 subsystem
2320 avb read_rb - read rollback index
2321 avb write_rb - write rollback index
2322 avb is_unlocked - check device lock state
2323 avb get_uuid - read and print uuid of a partition
2324 avb read_part - read data from partition
2325 avb read_part_hex - read data from partition and output to stdout
2326 avb write_part - write data to partition
2327 avb verify - run full verification chain
2329 config CMD_STACKPROTECTOR_TEST
2330 bool "Test command for stack protector"
2331 depends on STACKPROTECTOR
2333 Enable stackprot_test command
2334 The stackprot_test command will force a stack overrun to test
2335 the stack smashing detection mechanisms.
2340 tristate "Enable UBI - Unsorted block images commands"
2343 UBI is a software layer above MTD layer which admits use of LVM-like
2344 logical volumes on top of MTD devices, hides some complexities of
2345 flash chips like wear and bad blocks and provides some other useful
2346 capabilities. Please, consult the MTD web site for more details
2347 (www.linux-mtd.infradead.org). Activate this option if you want
2348 to use U-Boot UBI commands.
2349 It is also strongly encouraged to also enable CONFIG_MTD to get full
2352 config CMD_UBI_RENAME
2353 bool "Enable rename"
2357 Enable a "ubi" command to rename ubi volume:
2358 ubi rename <oldname> <newname>
2361 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2363 default y if CMD_UBI
2366 UBIFS is a file system for flash devices which works on top of UBI.
git.openpandora.org / pandora-u-boot.git / blob