7 bool "Environment is not stored"
8 default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
9 !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
10 !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
11 !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
12 !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
15 Define this if you don't want to or can't have an environment stored
16 on a storage medium. In this case the environment will still exist
17 while U-Boot is running, but once U-Boot exits it will not be
18 stored. U-Boot will therefore always start up with a default
21 config ENV_IS_IN_EEPROM
22 bool "Environment in EEPROM"
23 depends on !CHAIN_OF_TRUST
25 Use this if you have an EEPROM or similar serial access
26 device and a driver for it.
31 These two #defines specify the offset and size of the
32 environment area within the total memory of your EEPROM.
34 Note that we consider the length of the address field to
35 still be one byte because the extra address bits are hidden
38 - CONFIG_ENV_EEPROM_IS_ON_I2C
39 define this, if you have I2C and SPI activated, and your
40 EEPROM, which holds the environment, is on the I2C bus.
42 - CONFIG_I2C_ENV_EEPROM_BUS
43 if you have an Environment on an EEPROM reached over
44 I2C muxes, you can define here, how to reach this
47 #define CONFIG_I2C_ENV_EEPROM_BUS 1
49 EEPROM which holds the environment, is reached over
50 a pca9547 i2c mux with address 0x70, channel 3.
53 bool "Environment is in a FAT filesystem"
54 depends on !CHAIN_OF_TRUST
55 default y if ARCH_BCM283X
56 default y if ARCH_SUNXI && MMC
57 default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
61 Define this if you want to use the FAT file system for the environment.
64 bool "Environment is in a EXT4 filesystem"
65 depends on !CHAIN_OF_TRUST
68 Define this if you want to use the EXT4 file system for the environment.
70 config ENV_IS_IN_FLASH
71 bool "Environment in flash memory"
72 depends on !CHAIN_OF_TRUST
73 default y if ARCH_CINTEGRATOR
74 default y if ARCH_INTEGRATOR_CP
75 default y if M548x || M547x || M5282 || MCF547x_8x
76 default y if MCF532x || MCF52x2
77 default y if MPC86xx || MPC83xx
78 default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
79 default y if SH && !CPU_SH4
81 Define this if you have a flash device which you want to use for the
84 a) The environment occupies one whole flash sector, which is
85 "embedded" in the text segment with the U-Boot code. This
86 happens usually with "bottom boot sector" or "top boot
87 sector" type flash chips, which have several smaller
88 sectors at the start or the end. For instance, such a
89 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
90 such a case you would place the environment in one of the
91 4 kB sectors - with U-Boot code before and after it. With
92 "top boot sector" type flash chips, you would put the
93 environment in one of the last sectors, leaving a gap
94 between U-Boot and the environment.
98 Offset of environment data (variable area) to the
99 beginning of flash memory; for instance, with bottom boot
100 type flash chips the second sector can be used: the offset
101 for this sector is given here.
103 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
107 This is just another way to specify the start address of
108 the flash sector containing the environment (instead of
111 CONFIG_ENV_SECT_SIZE:
113 Size of the sector containing the environment.
116 b) Sometimes flash chips have few, equal sized, BIG sectors.
117 In such a case you don't want to spend a whole sector for
122 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
123 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
124 of this flash sector for the environment. This saves
125 memory for the RAM copy of the environment.
127 It may also save flash memory if you decide to use this
128 when your environment is "embedded" within U-Boot code,
129 since then the remainder of the flash sector could be used
130 for U-Boot code. It should be pointed out that this is
131 STRONGLY DISCOURAGED from a robustness point of view:
132 updating the environment in flash makes it always
133 necessary to erase the WHOLE sector. If something goes
134 wrong before the contents has been restored from a copy in
135 RAM, your target system will be dead.
137 CONFIG_ENV_ADDR_REDUND
139 These settings describe a second storage area used to hold
140 a redundant copy of the environment data, so that there is
141 a valid backup copy in case there is a power failure during
142 a "saveenv" operation.
144 BE CAREFUL! Any changes to the flash layout, and some changes to the
145 source code will make it necessary to adapt <board>/u-boot.lds*
149 bool "Environment in an MMC device"
150 depends on !CHAIN_OF_TRUST
152 default y if ARCH_EXYNOS4
153 default y if MX6SX || MX7D
154 default y if TEGRA30 || TEGRA124
155 default y if TEGRA_ARMV8_COMMON
157 Define this if you have an MMC device which you want to use for the
160 CONFIG_SYS_MMC_ENV_DEV:
162 Specifies which MMC device the environment is stored in.
164 CONFIG_SYS_MMC_ENV_PART (optional):
166 Specifies which MMC partition the environment is stored in. If not
167 set, defaults to partition 0, the user area. Common values might be
168 1 (first MMC boot partition), 2 (second MMC boot partition).
173 These two #defines specify the offset and size of the environment
174 area within the specified MMC device.
176 If offset is positive (the usual case), it is treated as relative to
177 the start of the MMC partition. If offset is negative, it is treated
178 as relative to the end of the MMC partition. This can be useful if
179 your board may be fitted with different MMC devices, which have
180 different sizes for the MMC partitions, and you always want the
181 environment placed at the very end of the partition, to leave the
182 maximum possible space before it, to store other data.
184 These two values are in units of bytes, but must be aligned to an
187 CONFIG_ENV_OFFSET_REDUND (optional):
189 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
190 hold a redundant copy of the environment data. This provides a
191 valid backup copy in case the other copy is corrupted, e.g. due
192 to a power failure during a "saveenv" operation.
194 This value may also be positive or negative; this is handled in the
195 same way as CONFIG_ENV_OFFSET.
197 This value is also in units of bytes, but must also be aligned to
198 an MMC sector boundary.
200 config ENV_IS_IN_NAND
201 bool "Environment in a NAND device"
202 depends on !CHAIN_OF_TRUST
204 Define this if you have a NAND device which you want to use for the
210 These two #defines specify the offset and size of the environment
211 area within the first NAND device. CONFIG_ENV_OFFSET must be
212 aligned to an erase block boundary.
214 - CONFIG_ENV_OFFSET_REDUND (optional):
216 This setting describes a second storage area of CONFIG_ENV_SIZE
217 size used to hold a redundant copy of the environment data, so
218 that there is a valid backup copy in case there is a power failure
219 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
220 aligned to an erase block boundary.
222 - CONFIG_ENV_RANGE (optional):
224 Specifies the length of the region in which the environment
225 can be written. This should be a multiple of the NAND device's
226 block size. Specifying a range with more erase blocks than
227 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
228 the range to be avoided.
230 - CONFIG_ENV_OFFSET_OOB (optional):
232 Enables support for dynamically retrieving the offset of the
233 environment from block zero's out-of-band data. The
234 "nand env.oob" command can be used to record this offset.
235 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
236 using CONFIG_ENV_OFFSET_OOB.
238 config ENV_IS_IN_NVRAM
239 bool "Environment in a non-volatile RAM"
240 depends on !CHAIN_OF_TRUST
242 Define this if you have some non-volatile memory device
243 (NVRAM, battery buffered SRAM) which you want to use for the
249 These two #defines are used to determine the memory area you
250 want to use for environment. It is assumed that this memory
251 can just be read and written to, without any special
254 config ENV_IS_IN_ONENAND
255 bool "Environment is in OneNAND"
256 depends on !CHAIN_OF_TRUST
258 Define this if you want to put your local device's environment in
264 These two #defines are used to determine the device range you
265 want to use for environment. It is assumed that this memory
266 can just be read and written to, without any special
269 config ENV_IS_IN_REMOTE
270 bool "Environment is in remote memory space"
271 depends on !CHAIN_OF_TRUST
273 Define this if you have a remote memory space which you
274 want to use for the local device's environment.
279 These two #defines specify the address and size of the
280 environment area within the remote memory space. The
281 local device can get the environment from remote memory
282 space by SRIO or PCIE links.
284 config ENV_IS_IN_SPI_FLASH
285 bool "Environment is in SPI flash"
286 depends on !CHAIN_OF_TRUST && SPI
287 default y if ARMADA_XP
288 default y if INTEL_BAYTRAIL
289 default y if INTEL_BRASWELL
290 default y if INTEL_BROADWELL
291 default y if NORTHBRIDGE_INTEL_IVYBRIDGE
292 default y if INTEL_QUARK
293 default y if INTEL_QUEENSBAY
295 Define this if you have a SPI Flash memory device which you
296 want to use for the environment.
301 These two #defines specify the offset and size of the
302 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
303 aligned to an erase sector boundary.
305 - CONFIG_ENV_SECT_SIZE:
307 Define the SPI flash's sector size.
309 - CONFIG_ENV_OFFSET_REDUND (optional):
311 This setting describes a second storage area of CONFIG_ENV_SIZE
312 size used to hold a redundant copy of the environment data, so
313 that there is a valid backup copy in case there is a power failure
314 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
315 aligned to an erase sector boundary.
317 config USE_ENV_SPI_BUS
318 bool "SPI flash bus for environment"
319 depends on ENV_IS_IN_SPI_FLASH
321 Force the SPI bus for environment.
322 If not defined, use CONFIG_SF_DEFAULT_BUS.
325 int "Value of SPI flash bus for environment"
326 depends on USE_ENV_SPI_BUS
328 Value the SPI bus and chip select for environment.
330 config USE_ENV_SPI_CS
331 bool "SPI flash chip select for environment"
332 depends on ENV_IS_IN_SPI_FLASH
334 Force the SPI chip select for environment.
335 If not defined, use CONFIG_SF_DEFAULT_CS.
338 int "Value of SPI flash chip select for environment"
339 depends on USE_ENV_SPI_CS
341 Value of the SPI chip select for environment.
343 config USE_ENV_SPI_MAX_HZ
344 bool "SPI flash max frequency for environment"
345 depends on ENV_IS_IN_SPI_FLASH
347 Force the SPI max work clock for environment.
348 If not defined, use CONFIG_SF_DEFAULT_SPEED.
350 config ENV_SPI_MAX_HZ
351 int "Value of SPI flash max frequency for environment"
352 depends on USE_ENV_SPI_MAX_HZ
354 Value of the SPI max work clock for environment.
356 config USE_ENV_SPI_MODE
357 bool "SPI flash mode for environment"
358 depends on ENV_IS_IN_SPI_FLASH
360 Force the SPI work mode for environment.
363 hex "Value of SPI flash work mode for environment"
364 depends on USE_ENV_SPI_MODE
366 Value of the SPI work mode for environment.
367 See include/spi.h for value.
370 bool "Environment in a UBI volume"
371 depends on !CHAIN_OF_TRUST
375 Define this if you have an UBI volume that you want to use for the
376 environment. This has the benefit of wear-leveling the environment
377 accesses, which is important on NAND.
379 - CONFIG_ENV_UBI_PART:
381 Define this to a string that is the mtd partition containing the UBI.
383 - CONFIG_ENV_UBI_VOLUME:
385 Define this to the name of the volume that you want to store the
388 - CONFIG_ENV_UBI_VOLUME_REDUND:
390 Define this to the name of another volume to store a second copy of
391 the environment in. This will enable redundant environments in UBI.
392 It is assumed that both volumes are in the same MTD partition.
394 config SYS_REDUNDAND_ENVIRONMENT
395 bool "Enable redundant environment support"
396 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \
397 ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI
399 Normally, the environemt is stored in a single location. By
400 selecting this option, you can then define where to hold a redundant
401 copy of the environment data, so that there is a valid backup copy in
402 case there is a power failure during a "saveenv" operation.
404 config ENV_FAT_INTERFACE
405 string "Name of the block device for the environment"
406 depends on ENV_IS_IN_FAT
407 default "mmc" if ARCH_SUNXI
408 default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91
410 Define this to a string that is the name of the block device.
412 config ENV_FAT_DEVICE_AND_PART
413 string "Device and partition for where to store the environemt in FAT"
414 depends on ENV_IS_IN_FAT
415 default "0:1" if TI_COMMON_CMD_OPTIONS
416 default "0:auto" if ARCH_ZYNQMP
417 default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
418 default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
419 default "0" if ARCH_AT91
421 Define this to a string to specify the partition of the device. It can
424 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
425 - "D:P": device D partition P. Error occurs if device D has no
428 - "D" or "D:": device D partition 1 if device D has partition
429 table, or the whole device D if has no partition
431 - "D:auto": first partition in device D with bootable flag set.
432 If none, first valid partition in device D. If no
433 partition table then means device D.
436 string "Name of the FAT file to use for the environment"
437 depends on ENV_IS_IN_FAT
440 It's a string of the FAT file name. This file use to store the
443 config ENV_EXT4_INTERFACE
444 string "Name of the block device for the environment"
445 depends on ENV_IS_IN_EXT4
447 Define this to a string that is the name of the block device.
449 config ENV_EXT4_DEVICE_AND_PART
450 string "Device and partition for where to store the environemt in EXT4"
451 depends on ENV_IS_IN_EXT4
453 Define this to a string to specify the partition of the device. It can
456 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
457 - "D:P": device D partition P. Error occurs if device D has no
460 - "D" or "D:": device D partition 1 if device D has partition
461 table, or the whole device D if has no partition
463 - "D:auto": first partition in device D with bootable flag set.
464 If none, first valid partition in device D. If no
465 partition table then means device D.
468 string "Name of the EXT4 file to use for the environment"
469 depends on ENV_IS_IN_EXT4
472 It's a string of the EXT4 file name. This file use to store the
473 environment (explicit path to the file)
476 hex "Environment address"
477 depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
478 ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
479 default 0x0 if ENV_IS_IN_SPI_FLASH
481 Offset from the start of the device (or partition)
483 config ENV_ADDR_REDUND
484 hex "Redundant environment address"
485 depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
487 Offset from the start of the device (or partition) of the redundant
488 environment location.
491 hex "Environment offset"
492 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
494 default 0x3f8000 if ARCH_ROCKCHIP
495 default 0x88000 if ARCH_SUNXI
496 default 0xE0000 if ARCH_ZYNQ
497 default 0x1E00000 if ARCH_ZYNQMP
498 default 0x7F40000 if ARCH_VERSAL
500 default 0x140000 if ARCH_AT91
501 default 0x260000 if ARCH_OMAP2PLUS
503 Offset from the start of the device (or partition)
505 config ENV_OFFSET_REDUND
506 hex "Redundant environment offset"
507 depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
508 ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
510 Offset from the start of the device (or partition) of the redundant
511 environment location.
514 hex "Environment Size"
515 default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
516 default 0x20000 if ARCH_SUNXI || ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
517 default 0x8000 if ARCH_ROCKCHIP || ARCH_ZYNQMP || ARCH_VERSAL
518 default 0x4000 if ARC
521 Size of the environment storage area
524 hex "Environment Sector-Size"
525 depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
526 default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL
527 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
529 Size of the sector containing the environment.
532 string "UBI partition name"
533 depends on ENV_IS_IN_UBI
535 MTD partition containing the UBI device
537 config ENV_UBI_VOLUME
538 string "UBI volume name"
539 depends on ENV_IS_IN_UBI
541 Name of the volume that you want to store the environment in.
543 config ENV_UBI_VOLUME_REDUND
544 string "UBI redundant volume name"
545 depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
547 Name of the redundant volume that you want to store the environment in.
549 config ENV_UBI_VID_OFFSET
550 int "ubi environment VID offset"
551 depends on ENV_IS_IN_UBI
554 UBI VID offset for environment. If 0, no custom VID offset is used.
556 config SYS_RELOC_GD_ENV_ADDR
557 bool "Relocate gd->en_addr"
559 Relocate the early env_addr pointer so we know it is not inside
560 the binary. Some systems need this and for the rest, it doesn't hurt.
562 config USE_DEFAULT_ENV_FILE
563 bool "Create default environment from file"
565 Normally, the default environment is automatically generated
566 based on the settings of various CONFIG_* options, as well
567 as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
568 you can instead define the entire default environment in an
571 config DEFAULT_ENV_FILE
572 string "Path to default environment file"
573 depends on USE_DEFAULT_ENV_FILE
575 The path containing the default environment. The format is
576 the same as accepted by the mkenvimage tool: lines
577 containing key=value pairs, blank lines and lines beginning
580 config ENV_VARS_UBOOT_RUNTIME_CONFIG
581 bool "Add run-time information to the environment"
583 Enable this in order to add variables describing certain
584 run-time determined information about the hardware to the
585 environment. These will be named board_name, board_rev.
588 config SPL_ENV_IS_NOWHERE
589 bool "SPL Environment is not stored"
590 default y if ENV_IS_NOWHERE
592 Similar to ENV_IS_NOWHERE, used for SPL environment.
594 config SPL_ENV_IS_IN_MMC
595 bool "SPL Environment in an MMC device"
596 depends on !SPL_ENV_IS_NOWHERE
597 depends on ENV_IS_IN_MMC
600 Similar to ENV_IS_IN_MMC, used for SPL environment.
602 config SPL_ENV_IS_IN_FAT
603 bool "SPL Environment is in a FAT filesystem"
604 depends on !SPL_ENV_IS_NOWHERE
605 depends on ENV_IS_IN_FAT
608 Similar to ENV_IS_IN_FAT, used for SPL environment.
610 config SPL_ENV_IS_IN_EXT4
611 bool "SPL Environment is in a EXT4 filesystem"
612 depends on !SPL_ENV_IS_NOWHERE
613 depends on ENV_IS_IN_EXT4
616 Similar to ENV_IS_IN_EXT4, used for SPL environment.
618 config SPL_ENV_IS_IN_NAND
619 bool "SPL Environment in a NAND device"
620 depends on !SPL_ENV_IS_NOWHERE
621 depends on ENV_IS_IN_NAND
624 Similar to ENV_IS_IN_NAND, used for SPL environment.
626 config SPL_ENV_IS_IN_SPI_FLASH
627 bool "SPL Environment is in SPI flash"
628 depends on !SPL_ENV_IS_NOWHERE
629 depends on ENV_IS_IN_SPI_FLASH
632 Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
634 config SPL_ENV_IS_IN_FLASH
635 bool "SPL Environment in flash memory"
636 depends on !SPL_ENV_IS_NOWHERE
637 depends on ENV_IS_IN_FLASH
640 Similar to ENV_IS_IN_FLASH, used for SPL environment.
646 config TPL_ENV_IS_NOWHERE
647 bool "TPL Environment is not stored"
648 default y if ENV_IS_NOWHERE
650 Similar to ENV_IS_NOWHERE, used for TPL environment.
652 config TPL_ENV_IS_IN_MMC
653 bool "TPL Environment in an MMC device"
654 depends on !TPL_ENV_IS_NOWHERE
655 depends on ENV_IS_IN_MMC
658 Similar to ENV_IS_IN_MMC, used for TPL environment.
660 config TPL_ENV_IS_IN_FAT
661 bool "TPL Environment is in a FAT filesystem"
662 depends on !TPL_ENV_IS_NOWHERE
663 depends on ENV_IS_IN_FAT
666 Similar to ENV_IS_IN_FAT, used for TPL environment.
668 config TPL_ENV_IS_IN_EXT4
669 bool "TPL Environment is in a EXT4 filesystem"
670 depends on !TPL_ENV_IS_NOWHERE
671 depends on ENV_IS_IN_EXT4
674 Similar to ENV_IS_IN_EXT4, used for TPL environment.
676 config TPL_ENV_IS_IN_NAND
677 bool "TPL Environment in a NAND device"
678 depends on !TPL_ENV_IS_NOWHERE
679 depends on ENV_IS_IN_NAND
682 Similar to ENV_IS_IN_NAND, used for TPL environment.
684 config TPL_ENV_IS_IN_SPI_FLASH
685 bool "TPL Environment is in SPI flash"
686 depends on !TPL_ENV_IS_NOWHERE
687 depends on ENV_IS_IN_SPI_FLASH
690 Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
692 config TPL_ENV_IS_IN_FLASH
693 bool "TPL Environment in flash memory"
694 depends on !TPL_ENV_IS_NOWHERE
695 depends on ENV_IS_IN_FLASH
698 Similar to ENV_IS_IN_FLASH, used for TPL environment.