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
59 string "Command execution tracer"
63 This option enables the possiblity to print all commands before
64 executing them and after all variables are evaluated (similar
65 to Bash's xtrace/'set -x' feature).
66 To enable the tracer a variable "xtrace" needs to be defined in
80 List and dump ACPI tables. ACPI (Advanced Configuration and Power
81 Interface) is used mostly on x86 for providing information to the
82 Operating System about devices in the system. The tables are set up
83 by the firmware, typically U-Boot but possibly an earlier firmware
84 module, if U-Boot is chain-loaded from something else. ACPI tables
85 can also include code, to perform hardware-specific tasks required
86 by the Operating Systems. This allows some amount of separation
87 between the firmware and OS, and is particularly useful when you
88 want to make hardware changes without the OS needing to be adjusted.
101 Print ".config" contents.
103 If this option is enabled, the ".config" file contents are embedded
104 in the U-Boot image and can be printed on the console by the "config"
105 command. This provides information of which options are enabled on
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.
126 Print GPL license text
131 Provides access to the Intel Power-Management Controller (PMC) so
132 that its state can be examined. This does not currently support
133 changing the state but it is still useful for debugging and seeing
142 config CMD_TLV_EEPROM
144 depends on I2C_EEPROM
146 Display and program the system EEPROM data block in ONIE Tlvinfo
147 format. TLV stands for Type-Length-Value.
149 config SPL_CMD_TLV_EEPROM
150 bool "tlv_eeprom for SPL"
151 depends on SPL_I2C_EEPROM
152 select SPL_DRIVERS_MISC_SUPPORT
154 Read system EEPROM data block in ONIE Tlvinfo format from SPL.
158 depends on RISCV_SMODE && SBI_V02
160 Display information about the SBI implementation.
170 Run the command stored in the environment "bootcmd", i.e.
171 "bootd" does the same thing as "run bootcmd".
177 Boot an application image from the memory.
180 bool "Support booting UEFI FIT images"
181 depends on CMD_BOOTEFI && CMD_BOOTM && FIT
184 Support booting UEFI FIT images via the bootm command.
189 Boot the Linux zImage
193 depends on ARM64 || RISCV
196 Boot an AArch64 Linux Kernel image from memory.
199 bool "Support booting Linux OS images"
200 depends on CMD_BOOTM || CMD_BOOTZ || CMD_BOOTI
203 Support booting the Linux kernel directly via a command such as bootm
207 bool "Support booting NetBSD (non-EFI) loader images"
211 Support booting NetBSD via the bootm command.
213 config BOOTM_OPENRTOS
214 bool "Support booting OPENRTOS / FreeRTOS images"
217 Support booting OPENRTOS / FreeRTOS via the bootm command.
220 bool "Support booting Enea OSE images"
221 depends on (ARM && (ARM64 || CPU_V7A || CPU_V7R) || SANDBOX || PPC || X86)
224 Support booting Enea OSE images via the bootm command.
227 bool "Support booting Plan9 OS images"
231 Support booting Plan9 images via the bootm command.
234 bool "Support booting RTEMS OS images"
238 Support booting RTEMS images via the bootm command.
241 bool "Support booting VxWorks OS images"
245 Support booting VxWorks images via the bootm command.
249 depends on EFI_LOADER
252 Boot an EFI image from memory.
254 config CMD_BOOTEFI_HELLO_COMPILE
255 bool "Compile a standard EFI hello world binary for testing"
256 depends on CMD_BOOTEFI && !CPU_V7M
259 This compiles a standard EFI hello world application with U-Boot so
260 that it can be used with the test/py testing framework. This is useful
261 for testing that EFI is working at a basic level, and for bringing
262 up EFI support on a new architecture.
264 No additional space will be required in the resulting U-Boot binary
265 when this option is enabled.
267 config CMD_BOOTEFI_HELLO
268 bool "Allow booting a standard EFI hello world for testing"
269 depends on CMD_BOOTEFI_HELLO_COMPILE
270 default y if CMD_BOOTEFI_SELFTEST
272 This adds a standard EFI hello world application to U-Boot so that
273 it can be used with the 'bootefi hello' command. This is useful
274 for testing that EFI is working at a basic level, and for bringing
275 up EFI support on a new architecture.
277 source lib/efi_selftest/Kconfig
283 Add an ANSI terminal boot menu command.
288 Android DTB/DTBO image manipulation commands. Read dtb/dtbo files from
289 image into RAM, dump image structure information, etc. Those dtb/dtbo
290 files should be merged in one dtb further, which needs to be passed to
291 the kernel, as part of a boot process.
295 depends on ANDROID_BOOT_IMAGE
297 Android Boot Image manipulation commands. Allows one to extract
298 images contained in boot.img, like kernel, ramdisk, dtb, etc, and
299 obtain corresponding meta-information from boot.img.
301 See doc/android/boot-image.rst for details.
304 bool "bootelf, bootvx"
308 Boot an ELF/vxWorks image from the memory.
311 bool "Flattened Device Tree utility commands"
315 Do FDT related setup before booting into the Operating System.
321 Start an application at a given address.
327 Run the command in the given environment variable.
333 Print header information for application image.
338 List all images found in flash
344 Extract a part of a multi-image.
347 bool "spl export - Export boot information for Falcon boot"
350 Falcon mode allows booting directly from SPL into an Operating
351 System such as Linux, thus skipping U-Boot proper. See
352 doc/README.falcon for full information about how to use this
355 config CMD_SPL_NAND_OFS
356 hex "Offset of OS args or dtb for Falcon-mode NAND boot"
357 depends on CMD_SPL && (TPL_NAND_SUPPORT || SPL_NAND_SUPPORT)
360 This provides the offset of the command line arguments for Linux
361 when booting from NAND in Falcon mode. See doc/README.falcon
362 for full information about how to use this option (and also see
363 board/gateworks/gw_ventana/README for an example).
365 config CMD_SPL_NOR_OFS
366 hex "Offset of OS args or dtb for Falcon-mode NOR boot"
367 depends on CMD_SPL && SPL_NOR_SUPPORT
370 This provides the offset of the command line arguments or dtb for
371 Linux when booting from NOR in Falcon mode.
373 config CMD_SPL_WRITE_SIZE
374 hex "Size of argument area"
378 This provides the size of the command-line argument area in NAND
379 flash used by Falcon-mode boot. See the documentation until CMD_SPL
382 config CMD_THOR_DOWNLOAD
383 bool "thor - TIZEN 'thor' download"
386 Implements the 'thor' download protocol. This is a way of
387 downloading a software update over USB from an attached host.
388 There is no documentation about this within the U-Boot source code
389 but you should be able to find something on the interwebs.
392 bool "zboot - x86 boot command"
394 With x86 machines it is common to boot a bzImage file which
395 contains both a kernel and a setup.bin file. The latter includes
396 configuration information from the dark ages which x86 boards still
397 need to pick things out of.
399 Consider using FIT in preference to this since it supports directly
400 booting both 32- and 64-bit kernels, as well as secure boot.
401 Documentation is available in doc/uImage.FIT/x86-fit-boot.txt
405 menu "Environment commands"
408 bool "ask for env variable"
410 Ask for environment variable
428 Edit environment variable.
433 Allow for searching environment variables
439 Save all environment variables into the compiled-in persistent
445 depends on CMD_SAVEENV
447 Erase environment variables from the compiled-in persistent
450 config CMD_ENV_EXISTS
454 Check if a variable is defined in the environment for use in
457 config CMD_ENV_CALLBACK
458 bool "env callbacks - print callbacks and their associated variables"
460 Some environment variable have callbacks defined by
461 U_BOOT_ENV_CALLBACK. These are called when the variable changes.
462 For example changing "baudrate" adjust the serial baud rate. This
463 command lists the currently defined callbacks.
466 bool "env flags -print variables that have non-default flags"
468 Some environment variables have special flags that control their
469 behaviour. For example, serial# can only be written once and cannot
470 be deleted. This command shows the variables that have special
473 config CMD_NVEDIT_EFI
474 bool "env [set|print] -e - set/print UEFI variables"
475 depends on EFI_LOADER
478 UEFI variables are encoded as some form of U-Boot variables.
479 If enabled, we are allowed to set/print UEFI variables using
480 "env" command with "-e" option without knowing details.
482 config CMD_NVEDIT_INFO
483 bool "env info - print or evaluate environment information"
485 Print environment information:
486 - env_valid : is environment valid
487 - env_ready : is environment imported into hash table
488 - env_use_default : is default environment used
490 This command can be optionally used for evaluation in scripts:
491 [-d] : evaluate whether default environment is used
492 [-p] : evaluate whether environment can be persisted
494 The result of multiple evaluations will be combined with AND.
496 config CMD_NVEDIT_LOAD
499 Load all environment variables from the compiled-in persistent
502 config CMD_NVEDIT_SELECT
505 Select the compiled-in persistent storage of environment variables.
509 menu "Memory commands"
514 Compute binary operations (xor, or, and) of byte arrays of arbitrary
515 size from memory and store the result in memory or the environment.
519 default y if BLOBLIST
521 Show information about the bloblist, a collection of binary blobs
522 held in memory that persist between SPL and U-Boot. In the case of
523 x86 devices the bloblist can be used to hold ACPI tables so that they
524 remain available in memory.
537 Add -v option to verify data against a crc32 checksum.
540 bool "eeprom - EEPROM subsystem"
542 (deprecated, needs conversion to driver model)
543 Provides commands to read and write EEPROM (Electrically Erasable
544 Programmable Read Only Memory) chips that are connected over an
547 config CMD_EEPROM_LAYOUT
548 bool "Enable layout-aware eeprom commands"
549 depends on CMD_EEPROM
551 (deprecated, needs conversion to driver model)
552 When enabled, additional eeprom sub-commands become available.
554 eeprom print - prints the contents of the eeprom in a human-readable
555 way (eeprom layout fields, and data formatted to be fit for human
558 eeprom update - allows user to update eeprom fields by specifying
559 the field name, and providing the new data in a human readable format
560 (same format as displayed by the eeprom print command).
562 Both commands can either auto detect the layout, or be told which
566 __weak int parse_layout_version(char *str)
567 - override to provide your own layout name parsing
568 __weak void __eeprom_layout_assign(struct eeprom_layout *layout,
570 - override to setup the layout metadata based on the version
571 __weak int eeprom_layout_detect(unsigned char *data)
572 - override to provide your own algorithm for detecting layout
575 - contains various printing and updating functions for common
576 types of eeprom fields. Can be used for defining
579 config EEPROM_LAYOUT_HELP_STRING
580 string "Tells user what layout names are supported"
581 depends on CMD_EEPROM_LAYOUT
582 default "<not defined>"
584 Help printed with the LAYOUT VERSIONS part of the 'eeprom'
590 Infinite write loop on address range
597 Compute MD5 checksum.
602 depends on CMD_MD5SUM
604 Add -v option to verify data against an MD5 checksum.
609 Display memory information.
612 bool "md, mm, nm, mw, cp, cmp, base, loop"
617 mm - memory modify (auto-incrementing address)
618 nm - memory modify (constant address)
619 mw - memory write (fill)
622 base - print or set address offset
623 loop - initialize loop on address range
625 config CMD_MEM_SEARCH
626 bool "ms - Memory search"
628 Memory-search command
630 This allows searching through a region of memory looking for hex
631 data (byte, 16-bit word, 32-bit long, also 64-bit on machines that
632 support it). It is also possible to search for a string. The
633 command accepts a memory range and a list of values to search for.
634 The values need to appear in memory in the same order they are given
635 in the command. At most 10 matches can be returned at a time, but
636 pressing return will show the next 10 matches. Environment variables
637 are set for use with scripting (memmatches, memaddr, mempos).
640 bool "Enable cyclic md/mw commands"
641 depends on CMD_MEMORY
643 Add the "mdc" and "mwc" memory commands. These are cyclic
648 This command will print 4 bytes (10,11,12,13) each 500 ms.
650 => mwc.l 100 12345678 10
651 This command will write 12345678 to address 100 all 10 ms.
656 depends on CMD_MEMORY && (LIB_RAND || LIB_HW_RAND)
658 random - fill memory with random data
663 Simple RAM read/write test.
667 config SYS_ALT_MEMTEST
668 bool "Alternative test"
670 Use a more complete alternative memory test.
674 config SYS_ALT_MEMTEST_BITFLIP
678 The alternative memory test includes bitflip test since 2020.07.
679 The bitflip test significantly increases the overall test time.
680 Bitflip test can optionally be disabled here.
684 config SYS_MEMTEST_START
685 hex "default start address for mtest"
688 This is the default start address for mtest for simple read/write
689 test. If no arguments are given to mtest, default address is used
692 config SYS_MEMTEST_END
693 hex "default end address for mtest"
696 This is the default end address for mtest for simple read/write
697 test. If no arguments are given to mtest, default address is used
706 Compute SHA1 checksum.
708 config SHA1SUM_VERIFY
710 depends on CMD_SHA1SUM
712 Add -v option to verify data against a SHA1 checksum.
715 bool "strings - display strings in memory"
717 This works similarly to the Unix 'strings' command except that it
718 works with a memory range. String of printable characters found
719 within the range are displayed. The minimum number of characters
720 for a sequence to be considered a string can be provided.
724 menu "Compression commands"
728 default y if CMD_BOOTI
731 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
736 default y if CMD_BOOTI
739 Support decompressing an LZ4 image from memory region.
743 default y if CMD_BOOTI
746 Uncompress a zip-compressed memory region.
750 select GZIP_COMPRESSED
752 Compress a memory region with zlib deflate method.
756 menu "Device access commands"
759 #depends on FLASH_CFI_DRIVER
762 ARM Ltd reference designs flash partition access
765 bool "adc - Access Analog to Digital Converters info and data"
767 depends on DM_REGULATOR
769 Shows ADC device info and permit printing one-shot analog converted
770 data from a named Analog to Digital Converter.
775 depends on PARTITIONS
777 Read/modify/write the fields of Bootloader Control Block, usually
778 stored on the flash "misc" partition with its structure defined in:
779 https://android.googlesource.com/platform/bootable/recovery/+/master/
780 bootloader_message/include/bootloader_message/bootloader_message.h
782 Some real-life use-cases include (but are not limited to):
783 - Determine the "boot reason" (and act accordingly):
784 https://source.android.com/devices/bootloader/boot-reason
785 - Get/pass a list of commands from/to recovery:
786 https://android.googlesource.com/platform/bootable/recovery
787 - Inspect/dump the contents of the BCB fields
790 bool "bind/unbind - Bind or unbind a device to/from a driver"
793 Bind or unbind a device to/from a driver from the command line.
794 This is useful in situations where a device may be handled by several
795 drivers. For example, this can be used to bind a UDC to the usb ether
796 gadget driver from the command line.
799 bool "clk - Show clock frequencies"
802 Shows clock frequences by calling a sock_clk_dump() hook function.
803 This is depreated in favour of using the CLK uclass and accessing
804 clock values from associated drivers. However currently no command
808 bool "demo - Demonstration commands for driver model"
811 Provides a 'demo' command which can be used to play around with
812 driver model. To use this properly you will need to enable one or
813 both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
814 Otherwise you will always get an empty list of devices. The demo
815 devices are defined in the sandbox device tree, so the easiest
816 option is to use sandbox and pass the -d point to sandbox's
823 Enables the command "dfu" which is used to have U-Boot create a DFU
824 class device via USB. This command requires that the "dfu_alt_info"
825 environment variable be set and define the alt settings to expose to
829 bool "dm - Access to driver model information"
832 Provides access to driver model data structures and information,
833 such as a list of devices, list of uclasses and the state of each
834 device (e.g. activated). This is not required for operation, but
835 can be useful to see the state of driver model for debugging or
839 bool "fastboot - Android fastboot support"
842 This enables the command "fastboot" which enables the Android
843 fastboot mode for the platform. Fastboot is a protocol for
844 downloading images, flashing and device control used on
845 Android devices. Fastboot requires either the network stack
846 enabled or support for acting as a USB device.
848 See doc/android/fastboot.rst for more information.
851 bool "flinfo, erase, protect"
853 depends on MTD || FLASH_CFI_DRIVER || MTD_NOR_FLASH
856 flinfo - print FLASH memory information
858 protect - enable or disable FLASH write protection
867 config CMD_FPGA_LOADBP
868 bool "fpga loadbp - load partial bitstream (Xilinx only)"
871 Supports loading an FPGA device from a bitstream buffer containing
874 config CMD_FPGA_LOADFS
875 bool "fpga loadfs - load bitstream from FAT filesystem (Xilinx only)"
878 Supports loading an FPGA device from a FAT filesystem.
880 config CMD_FPGA_LOADMK
881 bool "fpga loadmk - load bitstream from image"
884 Supports loading an FPGA device from a image generated by mkimage.
886 config CMD_FPGA_LOADP
887 bool "fpga loadp - load partial bitstream"
890 Supports loading an FPGA device from a bitstream buffer containing
893 config CMD_FPGA_LOAD_SECURE
894 bool "fpga loads - loads secure bitstreams (Xilinx only)"
897 Enables the fpga loads command which is used to load secure
898 (authenticated or encrypted or both) bitstreams on to FPGA.
901 bool "fpgad - dump FPGA registers"
903 (legacy, needs conversion to driver model)
904 Provides a way to dump FPGA registers by calling the board-specific
905 fpga_get_reg() function. This functions similarly to the 'md'
909 bool "fuse - support for the fuse subssystem"
911 (deprecated - needs conversion to driver model)
912 This allows reading, sensing, programming or overriding fuses
913 which control the behaviour of the device. The command uses the
922 bool "GPT (GUID Partition Table) command"
924 select HAVE_BLOCK_DEVICE
925 select PARTITION_UUIDS
928 Enable the 'gpt' command to ready and write GPT style partition
932 bool "GPT Random UUID generation"
935 Enable the generation of partitions with random UUIDs if none
938 config CMD_GPT_RENAME
939 bool "GPT partition renaming commands"
942 Enables the 'gpt' command to interchange names on two GPT
943 partitions via the 'gpt swap' command or to rename single
944 partitions via the 'rename' command.
947 bool "ide - Support for IDE drivers"
950 Provides an 'ide' command which allows accessing the IDE drive,
951 reseting the IDE interface, printing the partition table and
952 geting device info. It also enables the 'diskboot' command which
953 permits booting from an IDE drive.
956 bool "io - Support for performing I/O accesses"
958 Provides an 'iod' command to display I/O space and an 'iow' command
959 to write values to the I/O space. This can be useful for manually
960 checking the state of devices during boot when debugging device
964 bool "iotrace - Support for tracing I/O activity"
966 Provides an 'iotrace' command which supports recording I/O reads and
967 writes in a trace buffer in memory . It also maintains a checksum
968 of the trace records (even if space is exhausted) so that the
969 sequence of I/O accesses can be verified.
971 When debugging drivers it is useful to see what I/O accesses were
972 done and in what order.
974 Even if the individual accesses are of little interest it can be
975 useful to verify that the access pattern is consistent each time
976 an operation is performed. In this case a checksum can be used to
977 characterise the operation of a driver. The checksum can be compared
978 across different runs of the operation to verify that the driver is
981 In particular, when performing major refactoring of the driver, where
982 the access pattern should not change, the checksum provides assurance
983 that the refactoring work has not broken the driver.
985 This works by sneaking into the io.h heder for an architecture and
986 redirecting I/O accesses through iotrace's tracing mechanism.
988 For now no commands are provided to examine the trace buffer. The
989 format is fairly simple, so 'md' is a reasonable substitute.
991 Note: The checksum feature is only useful for I/O regions where the
992 contents do not change outside of software control. Where this is not
993 suitable you can fall back to manually comparing the addresses. It
994 might be useful to enhance tracing to only checksum the accesses and
995 not the data read/written.
1005 bool "w1 - Support for Dallas 1-Wire protocol"
1007 Dallas 1-wire protocol support
1013 Load a binary file over serial line.
1019 Load an S-Record file over serial line
1023 bool "lsblk - list block drivers and devices"
1025 Print list of available block device drivers, and for each, the list
1026 of known block devices.
1031 MMC memory mapped support.
1035 config CMD_BKOPS_ENABLE
1036 bool "mmc bkops enable"
1040 Enable command for setting manual background operations handshake
1041 on a eMMC device. The feature is optionally available on eMMC devices
1042 conforming to standard >= 4.41.
1045 bool "Enable support for RPMB in the mmc command"
1046 depends on SUPPORT_EMMC_RPMB
1048 Enable the commands for reading, writing and programming the
1049 key for the Replay Protection Memory Block partition in eMMC.
1051 config CMD_MMC_SWRITE
1053 depends on MMC_WRITE
1056 Enable support for the "mmc swrite" command to write Android sparse
1065 Enable storage cloning over block devices, useful for
1066 initial flashing by external block device without network
1069 config CMD_OPTEE_RPMB
1070 bool "Enable read/write support on RPMB via OPTEE"
1071 depends on SUPPORT_EMMC_RPMB && OPTEE
1073 Enable the commands for reading, writing persistent named values
1074 in the Replay Protection Memory Block partition in eMMC by
1075 using Persistent Objects in OPTEE
1080 select MTD_PARTITIONS
1082 MTD commands support.
1086 default y if NAND_SUNXI
1087 depends on MTD_RAW_NAND
1092 config CMD_NAND_TRIMFFS
1093 bool "nand write.trimffs"
1094 default y if ARCH_SUNXI
1096 Allows one to skip empty pages when flashing something on a NAND.
1098 config CMD_NAND_LOCK_UNLOCK
1099 bool "nand lock/unlock"
1101 NAND locking support.
1103 config CMD_NAND_TORTURE
1106 NAND torture support.
1115 NVM Express device support
1118 bool "onenand - access to onenand device"
1121 OneNAND is a brand of NAND ('Not AND' gate) flash which provides
1122 various useful features. This command allows reading, writing,
1123 and erasing blocks. It allso provides a way to show and change
1124 bad blocks, and test the device.
1129 Enable the 'osd' command which allows to query information from and
1130 write text data to a on-screen display (OSD) device; a virtual device
1131 associated with a display capable of displaying a text overlay on the
1132 display it's associated with..
1136 select HAVE_BLOCK_DEVICE
1137 select PARTITION_UUIDS
1139 Read and display information about the partition table on
1143 bool "pci - Access PCI devices"
1145 Provide access to PCI (Peripheral Interconnect Bus), a type of bus
1146 used on some devices to allow the CPU to communicate with its
1147 peripherals. Sub-commands allow bus enumeration, displaying and
1148 changing configuration space and a few other features.
1151 bool "pinmux - show pins muxing"
1152 default y if PINCTRL
1154 Parse all available pin-controllers and show pins muxing. This
1155 is useful for debug purpoer to check the pin muxing and to know if
1156 a pin is configured as a GPIO or as an alternate function.
1161 Poweroff/Shutdown the system
1164 bool "read - Read binary data from a partition"
1166 Provides low-level access to the data in a partition.
1168 config CMD_REMOTEPROC
1170 depends on REMOTEPROC
1172 Support for Remote Processor control
1175 bool "sata - Access SATA subsystem"
1178 SATA (Serial Advanced Technology Attachment) is a serial bus
1179 standard for connecting to hard drives and other storage devices.
1180 This command provides information about attached devices and allows
1181 reading, writing and other operations.
1183 SATA replaces PATA (originally just ATA), which stands for Parallel AT
1184 Attachment, where AT refers to an IBM AT (Advanced Technology)
1185 computer released in 1984.
1188 bool "saves - Save a file over serial in S-Record format"
1190 Provides a way to save a binary file using the Motorola S-Record
1191 format over the serial line.
1194 bool "scsi - Access to SCSI devices"
1197 This provides a 'scsi' command which provides access to SCSI (Small
1198 Computer System Interface) devices. The command provides a way to
1199 scan the bus, reset the bus, read and write data and get information
1203 bool "sdram - Print SDRAM configuration information"
1205 Provides information about attached SDRAM. This assumed that the
1206 SDRAM has an EEPROM with information that can be read using the
1207 I2C bus. This is only available on some boards.
1211 depends on DM_SPI_FLASH || SPI_FLASH
1212 default y if DM_SPI_FLASH
1217 bool "sf test - Allow testing of SPI flash"
1220 Provides a way to test that SPI flash is working correctly. The
1221 test is destructive, in that an area of SPI flash must be provided
1222 for the test to use. Performance information is also provided,
1223 measuring the performance of reading, writing and erasing in
1224 Mbps (Million Bits Per Second). This value should approximately
1225 equal the SPI bus speed for a single-bit-wide SPI bus, assuming
1226 everything is working properly.
1229 bool "sspi - Command to access spi device"
1232 SPI utility command.
1234 config DEFAULT_SPI_BUS
1235 int "default spi bus used by sspi command"
1239 config DEFAULT_SPI_MODE
1240 hex "default spi mode used by sspi command (see include/spi.h)"
1245 bool "tsi148 - Command to access tsi148 device"
1247 This provides various sub-commands to initialise and configure the
1248 Turndra tsi148 device. See the command help for full details.
1251 bool "Enable UFS - Universal Flash Subsystem commands"
1254 "This provides commands to initialise and configure universal flash
1258 bool "universe - Command to set up the Turndra Universe controller"
1260 This allows setting up the VMEbus provided by this controller.
1261 See the command help for full details.
1265 select HAVE_BLOCK_DEVICE
1271 select USB_FUNCTION_SDP
1273 Enables the command "sdp" which is used to have U-Boot emulating the
1274 Serial Download Protocol (SDP) via USB.
1278 depends on USB_FUNCTION_ROCKUSB
1280 Rockusb protocol is widely used by Rockchip SoC based devices. It can
1281 read/write info, image to/from devices. This enable rockusb command
1282 support to communication with rockusb device. for more detail about
1283 this command, please read doc/README.rockusb.
1285 config CMD_USB_MASS_STORAGE
1286 bool "UMS usb mass storage"
1287 select USB_FUNCTION_MASS_STORAGE
1289 USB mass storage support
1292 bool "Xen para-virtualized block device"
1296 Xen para-virtualized block device support
1303 VirtIO block device support
1309 This provides commands to control the watchdog timer devices.
1315 Enable the command "axi" for accessing AXI (Advanced eXtensible
1316 Interface) busses, a on-chip interconnect specification for managing
1317 functional blocks in SoC designs, which is also often used in designs
1318 involving FPGAs (e.g. communication with IP cores in Xilinx FPGAs).
1322 menu "Shell scripting commands"
1328 Echo args to console
1334 Return true/false on integer compare.
1340 Run script from memory
1346 Evaluate boolean and math expressions and store the result in an env
1348 Also supports loading the value at a memory location into a variable.
1349 If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
1353 menu "Android support commands"
1355 config CMD_AB_SELECT
1358 depends on ANDROID_AB
1360 On Android devices with more than one boot slot (multiple copies of
1361 the kernel and system images) this provides a command to select which
1362 slot should be used to boot from and register the boot attempt. This
1363 is used by the new A/B update model where one slot is updated in the
1364 background while running from the other slot.
1371 bool "Network commands"
1381 bootp - boot image via network using BOOTP/TFTP protocol
1385 depends on CMD_BOOTP
1387 Boot image via network using DHCP/TFTP protocol
1389 config BOOTP_BOOTPATH
1390 bool "Request & store 'rootpath' from BOOTP/DHCP server"
1392 depends on CMD_BOOTP
1394 Even though the config is called BOOTP_BOOTPATH, it stores the
1395 path in the variable 'rootpath'.
1398 bool "Request & store 'dnsip' from BOOTP/DHCP server"
1400 depends on CMD_BOOTP
1402 The primary DNS server is stored as 'dnsip'. If two servers are
1403 returned, you must set BOOTP_DNS2 to store that second server IP
1407 bool "Store 'dnsip2' from BOOTP/DHCP server"
1408 depends on BOOTP_DNS
1410 If a DHCP client requests the DNS server IP from a DHCP server,
1411 it is possible that more than one DNS serverip is offered to the
1412 client. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1413 server IP will be stored in the additional environment
1414 variable "dnsip2". The first DNS serverip is always
1415 stored in the variable "dnsip", when BOOTP_DNS is defined.
1417 config BOOTP_GATEWAY
1418 bool "Request & store 'gatewayip' from BOOTP/DHCP server"
1420 depends on CMD_BOOTP
1422 config BOOTP_HOSTNAME
1423 bool "Request & store 'hostname' from BOOTP/DHCP server"
1425 depends on CMD_BOOTP
1427 The name may or may not be qualified with the local domain name.
1429 config BOOTP_PREFER_SERVERIP
1430 bool "serverip variable takes precedent over DHCP server IP."
1431 depends on CMD_BOOTP
1433 By default a BOOTP/DHCP reply will overwrite the 'serverip' variable.
1435 With this option enabled, the 'serverip' variable in the environment
1436 takes precedence over DHCP server IP and will only be set by the DHCP
1437 server if not already set in the environment.
1439 config BOOTP_SUBNETMASK
1440 bool "Request & store 'netmask' from BOOTP/DHCP server"
1442 depends on CMD_BOOTP
1444 config BOOTP_NTPSERVER
1445 bool "Request & store 'ntpserverip' from BOOTP/DHCP server"
1446 depends on CMD_BOOTP
1451 Selecting this will allow capturing all Ethernet packets and store
1452 them in physical memory in a PCAP formated file,
1453 later to be analyzed by PCAP reader application (IE. WireShark).
1456 bool "Send PXE client arch to BOOTP/DHCP server"
1458 depends on CMD_BOOTP && CMD_PXE
1460 Supported for ARM, ARM64, and x86 for now.
1462 config BOOTP_PXE_CLIENTARCH
1464 depends on BOOTP_PXE
1465 default 0x16 if ARM64
1469 config BOOTP_VCI_STRING
1471 depends on CMD_BOOTP
1472 default "U-Boot.armv7" if CPU_V7A || CPU_V7M || CPU_V7R
1473 default "U-Boot.armv8" if ARM64
1474 default "U-Boot.arm" if ARM
1481 tftpboot - boot image via network using TFTP protocol
1485 depends on CMD_TFTPBOOT
1487 TFTP put command, for uploading files to a server
1491 depends on CMD_TFTPBOOT
1493 Act as a TFTP server and boot the first received file
1495 config NET_TFTP_VARS
1496 bool "Control TFTP timeout and count through environment"
1497 depends on CMD_TFTPBOOT
1500 If set, allows controlling the TFTP timeout through the
1501 environment variable tftptimeout, and the TFTP maximum
1502 timeout count through the variable tftptimeoutcountmax.
1503 If unset, timeout and maximum are hard-defined as 1 second
1504 and 10 timouts per TFTP transfer.
1509 Boot image via network using RARP/TFTP protocol
1515 Boot image via network using NFS protocol.
1521 If set, allows 802.3(clause 22) MII Management functions interface access
1522 The management interface specified in Clause 22 provides
1523 a simple, two signal, serial interface to connect a
1524 Station Management entity and a managed PHY for providing access
1525 to management parameters and services.
1526 The interface is referred to as the MII management interface.
1532 If set, allows Enable 802.3(clause 45) MDIO interface registers access
1533 The MDIO interface is orthogonal to the MII interface and extends
1534 it by adding access to more registers through indirect addressing.
1539 Send ICMP ECHO_REQUEST to network host
1544 Perform CDP network configuration
1550 Synchronize RTC via network
1555 Lookup the IP of a hostname
1557 config CMD_LINK_LOCAL
1561 Acquire a network IP address using the link-local protocol
1568 Allow control of L2 Ethernet switch commands. These are supported
1569 by the vsc9953 Ethernet driver at present. Sub-commands allow
1570 operations such as enabling / disabling a port and
1571 viewing/maintaining the filtering database (FDB)
1577 Boot image via network using PXE protocol
1582 Wait for wake-on-lan Magic Packet
1586 menu "Misc commands"
1589 bool "Enable 'bmp' command"
1590 depends on LCD || DM_VIDEO || VIDEO
1592 This provides a way to obtain information about a BMP-format image
1593 and to display it. BMP (which presumably stands for BitMaP) is a
1594 file format defined by Microsoft which supports images of various
1595 depths, formats and compression methods. Headers on the file
1596 determine the formats used. This command can be used by first loading
1597 the image into RAM, then using this command to look at it or display
1600 config CMD_BOOTCOUNT
1602 depends on BOOTCOUNT_LIMIT
1604 Enable the bootcount command, which allows interrogation and
1605 reset of the bootcounter.
1608 bool "Enable board-specific commands"
1610 (deprecated: instead, please define a Kconfig option for each command)
1612 Some boards have board-specific commands which are only enabled
1613 during developemnt and need to be turned off for production. This
1614 option provides a way to control this. The commands that are enabled
1615 vary depending on the board.
1617 config CMD_BLOCK_CACHE
1618 bool "blkcache - control and stats for block cache"
1619 depends on BLOCK_CACHE
1620 default y if BLOCK_CACHE
1622 Enable the blkcache command, which can be used to control the
1623 operation of the cache functions.
1624 This is most useful when fine-tuning the operation of the cache
1625 during development, but also allows the cache to be disabled when
1626 it might hurt performance (e.g. when using the ums command).
1633 Enable the 'button' command which allows to get the status of
1634 buttons supported by the board. The buttonss can be listed with
1635 'button list' and state can be known with 'button <label>'.
1636 Any button drivers can be controlled with this command, e.g.
1640 bool "icache or dcache"
1642 Enable the "icache" and "dcache" commands
1644 config CMD_CONITRACE
1645 bool "conitrace - trace console input codes"
1647 Enable the 'conitrace' command which displays the codes received
1648 from the console input as hexadecimal numbers.
1651 bool "Enable clear screen command 'cls'"
1652 depends on CFB_CONSOLE || DM_VIDEO || LCD || VIDEO
1655 Enable the 'cls' command which clears the screen contents
1656 on video frame buffer.
1659 bool "efidebug - display/configure UEFI environment"
1660 depends on EFI_LOADER
1661 select EFI_DEVICE_PATH_TO_TEXT
1664 Enable the 'efidebug' command which provides a subset of UEFI
1665 shell utility with simplified functionality. It will be useful
1666 particularly for managing boot parameters as well as examining
1667 various EFI status for debugging.
1669 config CMD_EXCEPTION
1670 bool "exception - raise exception"
1671 depends on ARM || RISCV || X86
1673 Enable the 'exception' command which allows to raise an exception.
1680 Enable the 'led' command which allows for control of LEDs supported
1681 by the board. The LEDs can be listed with 'led list' and controlled
1682 with led on/off/togle/blink. Any LED drivers can be controlled with
1683 this command, e.g. led_gpio.
1690 Enable the 'date' command for getting/setting the time/date in RTC
1697 Enable the 'rtc' command for low-level access to RTC devices.
1702 Run commands and summarize execution time.
1705 bool "gettime - read elapsed time"
1707 Enable the 'gettime' command which reads the elapsed time since
1708 U-Boot started running. This shows the time in seconds and
1709 milliseconds. See also the 'bootstage' command which provides more
1710 flexibility for boot timing.
1717 Print bytes from the hardware random number generator.
1719 # TODO: rename to CMD_SLEEP
1724 Delay execution for some time
1727 bool "support for multiprocessor"
1729 This provides an option to brinup
1730 different processors in multiprocessor
1736 Access the system timer.
1742 This provides basic access to the U-Boot's sound support. The main
1743 feature is to play a beep.
1745 sound init - set up sound system
1746 sound play - play a sound
1752 Boot image via local extlinux.conf file
1758 This provides access to the QEMU firmware interface. The main
1759 feature is to allow easy loading of files passed to qemu-system
1760 via -kernel / -initrd
1765 This provides access to Linux PStore with Rammoops backend. The main
1766 feature is to allow to display or save PStore records.
1768 See doc/pstore.rst for more information.
1772 config CMD_PSTORE_MEM_ADDR
1773 hex "Memory Address"
1774 depends on CMD_PSTORE
1776 Base addr used for PStore ramoops memory, should be identical to
1777 ramoops.mem_address parameter used by kernel
1779 config CMD_PSTORE_MEM_SIZE
1781 depends on CMD_PSTORE
1784 Size of PStore ramoops memory, should be identical to ramoops.mem_size
1785 parameter used by kernel, a power of 2 and larger than the sum of the
1788 config CMD_PSTORE_RECORD_SIZE
1789 hex "Dump record size"
1790 depends on CMD_PSTORE
1793 Size of each dump done on oops/panic, should be identical to
1794 ramoops.record_size parameter used by kernel and a power of 2
1797 config CMD_PSTORE_CONSOLE_SIZE
1798 hex "Kernel console log size"
1799 depends on CMD_PSTORE
1802 Size of kernel console log, should be identical to
1803 ramoops.console_size parameter used by kernel and a power of 2
1806 config CMD_PSTORE_FTRACE_SIZE
1807 hex "FTrace log size"
1808 depends on CMD_PSTORE
1811 Size of ftrace log, should be identical to ramoops.ftrace_size
1812 parameter used by kernel and a power of 2
1814 config CMD_PSTORE_PMSG_SIZE
1815 hex "User space message log size"
1816 depends on CMD_PSTORE
1819 Size of user space message log, should be identical to
1820 ramoops.pmsg_size parameter used by kernel and a power of 2
1822 config CMD_PSTORE_ECC_SIZE
1824 depends on CMD_PSTORE
1827 if non-zero, the option enables ECC support and specifies ECC buffer
1828 size in bytes (1 is a special value, means 16 bytes ECC), should be
1829 identical to ramoops.ramoops_ecc parameter used by kernel
1833 source "cmd/mvebu/Kconfig"
1836 bool "terminal - provides a way to attach a serial terminal"
1838 Provides a 'cu'-like serial terminal command. This can be used to
1839 access other serial ports from the system console. The terminal
1840 is very simple with no special processing of characters. As with
1841 cu, you can press ~. (tilde followed by period) to exit.
1844 bool "uuid, guid - generation of unique IDs"
1847 This enables two commands:
1849 uuid - generate random Universally Unique Identifier
1850 guid - generate Globally Unique Identifier based on random UUID
1852 The two commands are very similar except for the endianness of the
1857 source "cmd/ti/Kconfig"
1859 config CMD_BOOTSTAGE
1860 bool "Enable the 'bootstage' command"
1861 depends on BOOTSTAGE
1863 Add a 'bootstage' command which supports printing a report
1864 and un/stashing of bootstage data.
1866 menu "Power commands"
1868 bool "Enable Driver Model PMIC command"
1871 This is the pmic command, based on a driver model pmic's API.
1872 Command features are unchanged:
1873 - list - list pmic devices
1874 - pmic dev <id> - show or [set] operating pmic device (NEW)
1875 - pmic dump - dump registers
1876 - pmic read address - read byte of register at address
1877 - pmic write address - write byte to register at address
1878 The only one change for this command is 'dev' subcommand.
1880 config CMD_REGULATOR
1881 bool "Enable Driver Model REGULATOR command"
1882 depends on DM_REGULATOR
1884 This command is based on driver model regulator's API.
1885 User interface features:
1886 - list - list regulator devices
1887 - regulator dev <id> - show or [set] operating regulator device
1888 - regulator info - print constraints info
1889 - regulator status - print operating status
1890 - regulator value <val] <-f> - print/[set] voltage value [uV]
1891 - regulator current <val> - print/[set] current value [uA]
1892 - regulator mode <id> - print/[set] operating mode id
1893 - regulator enable - enable the regulator output
1894 - regulator disable - disable the regulator output
1896 The '-f' (force) option can be used for set the value which exceeds
1897 the limits, which are found in device-tree and are kept in regulator's
1898 uclass platdata structure.
1902 menu "Security commands"
1904 bool "Enable the 'aes' command"
1907 This provides a means to encrypt and decrypt data using the AES
1908 (Advanced Encryption Standard). This algorithm uses a symetric key
1909 and is widely used as a streaming cipher. Different key lengths are
1910 supported by the algorithm but this command only supports 128 bits
1914 bool "Enable the 'blob' command"
1916 This is used with the Freescale secure boot mechanism.
1918 Freescale's SEC block has built-in Blob Protocol which provides
1919 a method for protecting user-defined data across system power
1920 cycles. SEC block protects data in a data structure called a Blob,
1921 which provides both confidentiality and integrity protection.
1923 Encapsulating data as a blob
1924 Each time that the Blob Protocol is used to protect data, a
1925 different randomly generated key is used to encrypt the data.
1926 This random key is itself encrypted using a key which is derived
1927 from SoC's non-volatile secret key and a 16 bit Key identifier.
1928 The resulting encrypted key along with encrypted data is called a
1929 blob. The non-volatile secure key is available for use only during
1932 During decapsulation, the reverse process is performed to get back
1936 blob enc - encapsulating data as a cryptgraphic blob
1937 blob dec - decapsulating cryptgraphic blob to get the data
1941 blob enc src dst len km
1943 Encapsulate and create blob of data $len bytes long
1944 at address $src and store the result at address $dst.
1945 $km is the 16 byte key modifier is also required for
1946 generation/use as key for cryptographic operation. Key
1947 modifier should be 16 byte long.
1949 blob dec src dst len km
1951 Decapsulate the blob of data at address $src and
1952 store result of $len byte at addr $dst.
1953 $km is the 16 byte key modifier is also required for
1954 generation/use as key for cryptographic operation. Key
1955 modifier should be 16 byte long.
1958 bool "Support 'hash' command"
1961 This provides a way to hash data in memory using various supported
1962 algorithms (such as SHA1, MD5, CRC32). The computed digest can be
1963 saved to memory or to an environment variable. It is also possible
1964 to verify a hash against data in memory.
1967 bool "Support the 'hvc' command"
1968 depends on ARM_SMCCC
1970 Allows issuing Hypervisor Calls (HVCs). Mostly useful for
1971 development and testing.
1974 bool "Support the 'smc' command"
1975 depends on ARM_SMCCC
1977 Allows issuing Secure Monitor Calls (SMCs). Mostly useful for
1978 development and testing.
1984 Add -v option to verify data against a hash.
1994 bool "Enable the 'tpm' command"
1995 depends on TPM_V1 || TPM_V2
1996 select CMD_TPM_V1 if TPM_V1
1997 select CMD_TPM_V2 if TPM_V2
1999 This provides a means to talk to a TPM from the command line. A wide
2000 range of commands if provided - see 'tpm help' for details. The
2001 command requires a suitable TPM on your board and the correct driver
2007 bool "Enable the 'tpm test' command"
2010 This provides a a series of tests to confirm that the TPMv1.x is
2011 working correctly. The tests cover initialisation, non-volatile RAM,
2012 extend, global lock and checking that timing is within expectations.
2013 The tests pass correctly on Infineon TPMs but may need to be adjusted
2020 menu "Firmware commands"
2022 bool "Enable crosec command"
2026 Enable command-line access to the Chrome OS EC (Embedded
2027 Controller). This provides the 'crosec' command which has
2028 a number of sub-commands for performing EC tasks such as
2029 updating its flash, accessing a small saved context area
2030 and talking to the I2C bus behind the EC (if there is one).
2033 menu "Filesystem commands"
2035 bool "Enable the 'btrsubvol' command"
2038 This enables the 'btrsubvol' command to list subvolumes
2039 of a BTRFS filesystem. There are no special commands for
2040 listing BTRFS directories or loading BTRFS files - this
2041 can be done by the generic 'fs' commands (see CMD_FS_GENERIC)
2042 when BTRFS is enabled (see FS_BTRFS).
2045 bool "Enable the 'cbfs' command"
2048 Define this to enable support for reading from a Coreboot
2049 filesystem. This is a ROM-based filesystem used for accessing files
2050 on systems that use coreboot as the first boot-loader and then load
2051 U-Boot to actually boot the Operating System. Available commands are
2052 cbfsinit, cbfsinfo, cbfsls and cbfsload.
2055 bool "Enable the 'cramfs' command"
2056 depends on FS_CRAMFS
2058 This provides commands for dealing with CRAMFS (Compressed ROM
2059 filesystem). CRAMFS is useful when space is tight since files are
2060 compressed. Two commands are provided:
2062 cramfsls - lists files in a cramfs image
2063 cramfsload - loads a file from a cramfs image
2066 bool "ext2 command support"
2069 Enables EXT2 FS command
2072 bool "ext4 command support"
2075 Enables EXT4 FS command
2077 config CMD_EXT4_WRITE
2079 bool "ext4 write command support"
2082 Enables EXT4 FS write command
2085 bool "FAT command support"
2088 Support for the FAT fs
2091 bool "SquashFS command support"
2094 Enables SquashFS filesystem commands (e.g. load, ls).
2096 config CMD_FS_GENERIC
2097 bool "filesystem commands"
2099 Enables filesystem commands (e.g. load, ls) that work for multiple
2103 bool "fsuuid command"
2105 Enables fsuuid command for filesystem UUID.
2108 bool "jffs2 command"
2111 Enables commands to support the JFFS2 (Journalling Flash File System
2112 version 2) filesystem. This enables fsload, ls and fsinfo which
2113 provide the ability to load files, list directories and obtain
2114 filesystem information.
2117 bool "MTD partition support"
2120 MTD partitioning tool support.
2121 It is strongly encouraged to avoid using this command
2122 anymore along with 'sf', 'nand', 'onenand'. One can still
2123 declare the partitions in the mtdparts environment variable
2124 but better use the MTD stack and the 'mtd' command instead.
2126 config CMD_MTDPARTS_SPREAD
2127 bool "Padd partition size to take account of bad blocks"
2128 depends on CMD_MTDPARTS
2130 This enables the 'spread' sub-command of the mtdparts command.
2131 This command will modify the existing mtdparts variable by increasing
2132 the size of the partitions such that 1) each partition's net size is
2133 at least as large as the size specified in the mtdparts variable and
2134 2) each partition starts on a good block.
2136 config CMD_MTDPARTS_SHOW_NET_SIZES
2137 bool "Show net size (w/o bad blocks) of partitions"
2138 depends on CMD_MTDPARTS
2140 Adds two columns to the printed partition table showing the
2141 effective usable size of a partition, if bad blocks are taken
2144 config MTDIDS_DEFAULT
2145 string "Default MTD IDs"
2146 depends on MTD || SPI_FLASH
2148 Defines a default MTD IDs list for use with MTD partitions in the
2149 Linux MTD command line partitions format.
2151 config MTDPARTS_DEFAULT
2152 string "Default MTD partition scheme"
2153 depends on MTD || SPI_FLASH
2155 Defines a default MTD partitioning scheme in the Linux MTD command
2156 line partitions format
2159 bool "reiser - Access to reiserfs filesystems"
2161 This provides two commands which operate on a resierfs filesystem,
2162 commonly used some years ago:
2164 reiserls - list files
2165 reiserload - load a file
2168 bool "yaffs2 - Access of YAFFS2 filesystem"
2172 This provides commands for accessing a YAFFS2 filesystem. Yet
2173 Another Flash Filesystem 2 is a filesystem designed specifically
2174 for NAND flash. It incorporates bad-block management and ensures
2175 that device writes are sequential regardless of filesystem
2179 bool "zfs - Access of ZFS filesystem"
2181 This provides commands to accessing a ZFS filesystem, commonly used
2182 on Solaris systems. Two sub-commands are provided:
2184 zfsls - list files in a directory
2185 zfsload - load a file
2187 See doc/README.zfs for more details.
2191 menu "Debug commands"
2196 The bedbug (emBEDded deBUGger) command provides debugging features
2197 for some PowerPC processors. For details please see the
2198 documentation in doc/README.bedbug.
2201 bool "diag - Board diagnostics"
2203 This command provides access to board diagnostic tests. These are
2204 called Power-on Self Tests (POST). The command allows listing of
2205 available tests and running either all the tests, or specific tests
2209 bool "irq - Show information about interrupts"
2210 depends on !ARM && !MIPS && !RISCV && !SH
2212 This enables two commands:
2214 interrupts - enable or disable interrupts
2215 irqinfo - print device-specific interrupt information
2218 bool "kgdb - Allow debugging of U-Boot with gdb"
2221 This enables a 'kgdb' command which allows gdb to connect to U-Boot
2222 over a serial link for debugging purposes. This allows
2223 single-stepping, inspecting variables, etc. This is supported only
2224 on PowerPC at present.
2227 bool "log - Generation, control and access to logging"
2230 This provides access to logging features. It allows the output of
2231 log data to be controlled to a limited extent (setting up the default
2232 maximum log level for emitting of records). It also provides access
2233 to a command used for testing the log system.
2236 bool "trace - Support tracing of function calls and timing"
2238 Enables a command to control using of function tracing within
2239 U-Boot. This allows recording of call traces including timing
2240 information. The command can write data to memory for exporting
2241 for analysis (e.g. using bootchart). See doc/README.trace for full
2245 bool "avb - Android Verified Boot 2.0 operations"
2246 depends on AVB_VERIFY
2249 Enables a "avb" command to perform verification of partitions using
2250 Android Verified Boot 2.0 functionality. It includes such subcommands:
2251 avb init - initialize avb2 subsystem
2252 avb read_rb - read rollback index
2253 avb write_rb - write rollback index
2254 avb is_unlocked - check device lock state
2255 avb get_uuid - read and print uuid of a partition
2256 avb read_part - read data from partition
2257 avb read_part_hex - read data from partition and output to stdout
2258 avb write_part - write data to partition
2259 avb verify - run full verification chain
2263 tristate "Enable UBI - Unsorted block images commands"
2266 UBI is a software layer above MTD layer which admits use of LVM-like
2267 logical volumes on top of MTD devices, hides some complexities of
2268 flash chips like wear and bad blocks and provides some other useful
2269 capabilities. Please, consult the MTD web site for more details
2270 (www.linux-mtd.infradead.org). Activate this option if you want
2271 to use U-Boot UBI commands.
2272 It is also strongly encouraged to also enable CONFIG_MTD to get full
2275 config CMD_UBI_RENAME
2276 bool "Enable rename"
2280 Enable a "ubi" command to rename ubi volume:
2281 ubi rename <oldname> <newname>
2284 tristate "Enable UBIFS - Unsorted block images filesystem commands"
2286 default y if CMD_UBI
2289 UBIFS is a file system for flash devices which works on top of UBI.
projects / platform / kernel / u-boot.git / blob