6mainmenu "U-Boot $UBOOTVERSION Configuration"
10 option env="UBOOTVERSION"
15menu "General setup"
20 This option cannot be enabled. It is used as dependency
21 for broken and incomplete features.
24 string "Local version - append to U-Boot release"
26 Append an extra string to the end of your U-Boot version.
27 This will show up in your boot log, for example.
28 The string you set here will be appended after the contents of
29 any files with a filename matching localversion* in your
30 object and source tree, in that order. Your total string can
31 be a maximum of 64 characters.
34 bool "Automatically append version information to the version string"
35 default y
37 This will try to automatically determine if the current tree is a
38 release tree by looking for Git tags that belong to the current
39 top of tree revision.
41 A string of the format -gxxxxxxxx will be added to the localversion
42 if a Git-based tree is found. The string generated by this will be
43 appended after any matching localversion* files, and after the value
44 set in CONFIG_LOCALVERSION.
46 (The actual string used here is the first eight characters produced
47 by running the command:
49 $ git rev-parse --verify HEAD
51 which is done within the script "scripts/setlocalversion".)
54 bool "Optimize for size"
55 default y
57 Enabling this option will pass "-Os" instead of "-O2" to gcc
58 resulting in a smaller U-Boot image.
60 This option is enabled by default for U-Boot.
63 bool "Enable code coverage analysis"
64 depends on SANDBOX
66 Enabling this option will pass "--coverage" to gcc to compile
67 and link code instrumented for coverage analysis.
70 bool "Select defaults suitable for booting general purpose Linux distributions"
71 select AUTO_COMPLETE
72 select CMDLINE_EDITING
73 select CMD_BOOTI if ARM64
74 select CMD_BOOTZ if ARM && !ARM64
75 select CMD_DHCP if CMD_NET
76 select CMD_ENV_EXISTS
77 select CMD_EXT2
78 select CMD_EXT4
79 select CMD_FAT
80 select CMD_FS_GENERIC
81 select CMD_PART if PARTITIONS
82 select CMD_PING if CMD_NET
83 select CMD_PXE if NET
84 select ENV_VARS_UBOOT_CONFIG
85 select HUSH_PARSER
86 select SUPPORT_RAW_INITRD
87 select SYS_LONGHELP
88 imply CMD_MII if NET
89 imply USB_STORAGE
90 imply USE_BOOTCOMMAND
92 Select this to enable various options and commands which are suitable
93 for building u-boot for booting general purpose Linux distributions.
96 bool "Add arch, board, vendor and soc variables to default environment"
98 Define this in order to add variables describing the
99 U-Boot build configuration to the default environment.
100 These will be named arch, cpu, board, vendor, and soc.
101 Enabling this option will cause the following to be defined:
102 - CONFIG_SYS_ARCH
103 - CONFIG_SYS_CPU
104 - CONFIG_SYS_BOARD
105 - CONFIG_SYS_VENDOR
106 - CONFIG_SYS_SOC
109 int "Number of DRAM banks"
110 default 4
112 This defines the number of DRAM banks.
115 bool "Enable kernel command line setup"
117 Enables allocating and saving kernel cmdline in space between
118 "bootm_low" and "bootm_low" + BOOTMAPSZ.
121 bool "Enable kernel board information setup"
123 Enables allocating and saving a kernel copy of the bd_info in
124 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
127 bool "Enable malloc() pool before relocation"
128 default y if DM
131 Before relocation, memory is very limited on many platforms. Still,
132 we can provide a small malloc() pool if needed. Driver model in
133 particular needs this to operate, so that it can allocate the
134 initial serial device and any others that are needed.
137 hex "Size of malloc() pool before relocation"
138 depends on SYS_MALLOC_F
139 default 0x1000 if AM33XX
140 default 0x2800 if SANDBOX
141 default 0x400
143 Before relocation, memory is very limited on many platforms. Still,
144 we can provide a small malloc() pool if needed. Driver model in
145 particular needs this to operate, so that it can allocate the
146 initial serial device and any others that are needed.
149 hex "Define memory for Dynamic allocation"
150 depends on ARCH_ZYNQ || ARCH_VERSAL
152 This defines memory to be allocated for Dynamic allocation
153 TODO: Use for other architectures
156 hex "Size of malloc() pool in SPL before relocation"
157 depends on SYS_MALLOC_F
158 default SYS_MALLOC_F_LEN
160 Before relocation, memory is very limited on many platforms. Still,
161 we can provide a small malloc() pool if needed. Driver model in
162 particular needs this to operate, so that it can allocate the
163 initial serial device and any others that are needed.
166 hex "Size of malloc() pool in TPL before relocation"
167 depends on SYS_MALLOC_F
168 default SYS_MALLOC_F_LEN
170 Before relocation, memory is very limited on many platforms. Still,
171 we can provide a small malloc() pool if needed. Driver model in
172 particular needs this to operate, so that it can allocate the
173 initial serial device and any others that are needed.
176 bool "Configure standard U-Boot features (expert users)"
177 default y
179 This option allows certain base U-Boot options and settings
180 to be disabled or tweaked. This is for specialized
181 environments which can tolerate a "non-standard" U-Boot.
182 Use this only if you really know what you are doing.
185 config SYS_MALLOC_CLEAR_ON_INIT
186 bool "Init with zeros the memory reserved for malloc (slow)"
187 default y
189 This setting is enabled by default. The reserved malloc
190 memory is initialized with zeros, so first malloc calls
191 will return the pointer to the zeroed memory. But this
192 slows the boot time.
194 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
195 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
196 Then the boot time can be significantly reduced.
198 When disabling this, please check if malloc calls, maybe
199 should be replaced by calloc - if one expects zeroed memory.
202 bool "Enable debug information for tools"
204 Enable generation of debug information for tools such as mkimage.
205 This can be used for debugging purposes. With debug information
206 it is possible to set breakpoints on particular lines, single-step
207 debug through the source code, etc.
212 bool "64bit physical address support"
214 Say Y here to support 64bit physical memory address.
215 This can be used not only for 64bit SoCs, but also for
216 large physical address extention on 32bit SoCs.
219 bool "Build U-Boot as BIOS replacement"
220 depends on X86
222 This option allows to build a ROM version of U-Boot.
223 The build process generally requires several binary blobs
224 which are not shipped in the U-Boot source tree.
225 Please, see doc/README.x86 for details.
229menu "Boot images"
232 bool "Enable support for Android Boot Images"
233 default y if FASTBOOT
235 This enables support for booting images which use the Android
236 image format header.
239 bool "Support Flattened Image Tree"
240 select MD5
241 select SHA1
243 This option allows you to boot the new uImage structure,
244 Flattened Image Tree. FIT is formally a FDT, which can include
245 images of various types (kernel, FDT blob, ramdisk, etc.)
246 in a single blob. To boot this new uImage structure,
247 pass the address of the blob to the "bootm" command.
248 FIT is very flexible, supporting compression, multiple images,
249 multiple configurations, verification through hashing and also
250 verified boot (secure boot using RSA).
255 hex "Text Base"
256 default 0x0
258 This specifies a data offset in fit image.
259 The offset is from data payload offset to the beginning of
260 fit image header. When specifies a offset, specific data
261 could be put in the hole between data payload and fit image
262 header, such as CSF data on i.MX platform.
265 bool "Support SHA256 checksum of FIT image contents"
266 default y
267 select SHA256
269 Enable this to support SHA256 checksum of FIT image contents. A
270 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
271 the image contents have not been corrupted. SHA256 is recommended
272 for use in secure applications since (as at 2016) there is no known
273 feasible attack that could produce a 'collision' with differing
274 input data. Use this for the highest security. Note that only the
275 SHA256 variant is supported: SHA512 and others are not currently
276 supported in U-Boot.
279 bool "Enable signature verification of FIT uImages"
280 depends on DM
281 select HASH
282 select RSA
284 This option enables signature verification of FIT uImages,
285 using a hash signed and verified using RSA. If
286 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
287 hashing is available using hardware, then the RSA library will use
288 it. See doc/uImage.FIT/signature.txt for more details.
290 WARNING: When relying on signed FIT images with a required signature
291 check the legacy image format is disabled by default, so that
292 unsigned images cannot be loaded. If a board needs the legacy image
293 format support in this case, enable it using
297 hex "Max size of signed FIT structures"
298 depends on FIT_SIGNATURE
299 default 0x10000000
301 This option sets a max size in bytes for verified FIT uImages.
302 A sane value of 256MB protects corrupted DTB structures from overlapping
303 device memory. Assure this size does not extend past expected storage
307 bool "Support rsassa-pss signature scheme of FIT image contents"
308 depends on FIT_SIGNATURE
309 default n
311 Enable this to support the pss padding algorithm as described
312 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
315 bool "Show verbose messages when FIT images fail"
317 Generally a system will have valid FIT images so debug messages
318 are a waste of code space. If you are debugging your images then
319 you can enable this option to get more verbose information about
323 bool "Select the best match for the kernel device tree"
325 When no configuration is explicitly selected, default to the
326 one whose fdt's compatibility field best matches that of
327 U-Boot itself. A match is considered "best" if it matches the
328 most specific compatibility entry of U-Boot's fdt's root node.
329 The order of entries in the configuration's fdt is ignored.
332 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
333 depends on TI_SECURE_DEVICE
335 Allows doing any sort of manipulation to blobs after they got extracted
336 from FIT images like stripping off headers or modifying the size of the
337 blob, verification, authentication, decryption etc. in a platform or
338 board specific way. In order to use this feature a platform or board-
339 specific implementation of board_fit_image_post_process() must be
340 provided. Also, anything done during this post-processing step would
341 need to be comprehended in how the images were prepared before being
342 injected into the FIT creation (i.e. the blobs would have been pre-
343 processed before being added to the FIT image).
348 bool "Support Flattened Image Tree within SPL"
349 depends on SPL
350 select SPL_OF_LIBFDT
353 bool "Support FIT printing within SPL"
354 depends on SPL_FIT
356 Support printing the content of the fitImage in a verbose manner in SPL.
359 bool "Enable signature verification of FIT firmware within SPL"
360 depends on SPL_DM
361 select SPL_FIT
362 select SPL_RSA
365 bool "Enable SPL loading U-Boot as a FIT"
366 select SPL_FIT
368 Normally with the SPL framework a legacy image is generated as part
369 of the build. This contains U-Boot along with information as to
370 where it should be loaded. This option instead enables generation
371 of a FIT (Flat Image Tree) which provides more flexibility. In
372 particular it can handle selecting from multiple device tree
373 and passing the correct one to U-Boot.
376 bool "Enable SPL loading U-Boot as a FIT"
377 select SPL_FIT
379 Normally with the SPL framework a legacy image is generated as part
380 of the build. This contains U-Boot along with information as to
381 where it should be loaded. This option instead enables generation
382 of a FIT (Flat Image Tree) which provides more flexibility. In
383 particular it can handle selecting from multiple device tree
384 and passing the correct one to U-Boot.
387 bool "Enable post-processing of FIT artifacts after loading by the SPL"
388 depends on SPL_LOAD_FIT
390 Allows doing any sort of manipulation to blobs after they got extracted
391 from the U-Boot FIT image like stripping off headers or modifying the
392 size of the blob, verification, authentication, decryption etc. in a
393 platform or board specific way. In order to use this feature a platform
394 or board-specific implementation of board_fit_image_post_process() must
395 be provided. Also, anything done during this post-processing step would
396 need to be comprehended in how the images were prepared before being
397 injected into the FIT creation (i.e. the blobs would have been pre-
398 processed before being added to the FIT image).
401 string ".its source file for U-Boot FIT image"
402 depends on SPL_FIT
404 Specifies a (platform specific) FIT source file to generate the
405 U-Boot FIT image. This could specify further image to load and/or
409 string ".its file generator script for U-Boot FIT image"
410 depends on SPL_FIT
411 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
413 Specifies a (platform specific) script file to generate the FIT
414 source file used to build the U-Boot FIT image file. This gets
415 passed a list of supported device tree file stub names to
416 include in the generated image.
423 bool "Enable support for the legacy image format"
424 default y if !FIT_SIGNATURE
426 This option enables the legacy image format. It is enabled by
427 default for backward compatibility, unless FIT_SIGNATURE is
428 set where it is disabled so that unsigned images cannot be
429 loaded. If a board needs the legacy image format support in this
430 case, enable it here.
433 bool "Set up board-specific details in device tree before boot"
434 depends on OF_LIBFDT
436 This causes U-Boot to call ft_board_setup() before booting into
437 the Operating System. This function can set up various
438 board-specific information in the device tree for use by the OS.
439 The device tree is then passed to the OS.
442 bool "Set up system-specific details in device tree before boot"
443 depends on OF_LIBFDT
445 This causes U-Boot to call ft_system_setup() before booting into
446 the Operating System. This function can set up various
447 system-specific information in the device tree for use by the OS.
448 The device tree is then passed to the OS.
451 bool "Update the device-tree stdout alias from U-Boot"
452 depends on OF_LIBFDT
454 This uses U-Boot's serial alias from the aliases node to update
455 the device tree passed to the OS. The "linux,stdout-path" property
456 in the chosen node is set to point to the correct serial node.
457 This option currently references CONFIG_CONS_INDEX, which is
458 incorrect when used with device tree as this option does not
459 exist / should not be used.
462 string "Extra Options (DEPRECATED)"
464 The old configuration infrastructure (= mkconfig + boards.cfg)
465 provided the extra options field. If you have something like
466 "HAS_BAR,BAZ=64", the optional options
467 #define CONFIG_HAS
468 #define CONFIG_BAZ 64
469 will be defined in include/config.h.
470 This option was prepared for the smooth migration from the old
471 configuration to Kconfig. Since this option will be removed sometime,
472 new boards should not use this option.
475 depends on !NIOS2 && !XTENSA
476 depends on !EFI_APP
477 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
478 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
479 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
480 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
481 hex "Text Base"
483 The address in memory that U-Boot will be running from, initially.
488 depends on ARC || ARCH_SUNXI
489 int "CPU clock frequency"
491 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
494 bool "Enable arch_fixup_memory_banks() call"
495 default y
497 Enable FDT memory map syncup before OS boot. This feature can be
498 used for booting OS with different memory setup where the part of
499 the memory location should be used for different purpose.