4 bool "Environment is not stored"
5 default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
6 !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
7 !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
8 !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
9 !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
12 Define this if you don't want to or can't have an environment stored
13 on a storage medium. In this case the environment will still exist
14 while U-Boot is running, but once U-Boot exits it will not be
15 stored. U-Boot will therefore always start up with a default
18 config ENV_IS_IN_EEPROM
19 bool "Environment in EEPROM"
20 depends on !CHAIN_OF_TRUST
22 Use this if you have an EEPROM or similar serial access
23 device and a driver for it.
28 These two #defines specify the offset and size of the
29 environment area within the total memory of your EEPROM.
31 Note that we consider the length of the address field to
32 still be one byte because the extra address bits are hidden
35 - CONFIG_ENV_EEPROM_IS_ON_I2C
36 define this, if you have I2C and SPI activated, and your
37 EEPROM, which holds the environment, is on the I2C bus.
39 - CONFIG_I2C_ENV_EEPROM_BUS
40 if you have an Environment on an EEPROM reached over
41 I2C muxes, you can define here, how to reach this
44 #define CONFIG_I2C_ENV_EEPROM_BUS 1
46 EEPROM which holds the environment, is reached over
47 a pca9547 i2c mux with address 0x70, channel 3.
50 bool "Environment is in a FAT filesystem"
51 depends on !CHAIN_OF_TRUST
52 default y if ARCH_BCM283X
53 default y if ARCH_SUNXI && MMC
54 default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
58 Define this if you want to use the FAT file system for the environment.
61 bool "Environment is in a EXT4 filesystem"
62 depends on !CHAIN_OF_TRUST
65 Define this if you want to use the EXT4 file system for the environment.
67 config ENV_IS_IN_FLASH
68 bool "Environment in flash memory"
69 depends on !CHAIN_OF_TRUST
70 default y if ARCH_CINTEGRATOR
71 default y if ARCH_INTEGRATOR_CP
72 default y if M548x || M547x || M5282 || MCF547x_8x
73 default y if MCF532x || MCF52x2
74 default y if MPC86xx || MPC83xx
75 default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
76 default y if SH && !CPU_SH4
78 Define this if you have a flash device which you want to use for the
81 a) The environment occupies one whole flash sector, which is
82 "embedded" in the text segment with the U-Boot code. This
83 happens usually with "bottom boot sector" or "top boot
84 sector" type flash chips, which have several smaller
85 sectors at the start or the end. For instance, such a
86 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
87 such a case you would place the environment in one of the
88 4 kB sectors - with U-Boot code before and after it. With
89 "top boot sector" type flash chips, you would put the
90 environment in one of the last sectors, leaving a gap
91 between U-Boot and the environment.
95 Offset of environment data (variable area) to the
96 beginning of flash memory; for instance, with bottom boot
97 type flash chips the second sector can be used: the offset
98 for this sector is given here.
100 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
104 This is just another way to specify the start address of
105 the flash sector containing the environment (instead of
108 CONFIG_ENV_SECT_SIZE:
110 Size of the sector containing the environment.
113 b) Sometimes flash chips have few, equal sized, BIG sectors.
114 In such a case you don't want to spend a whole sector for
119 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
120 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
121 of this flash sector for the environment. This saves
122 memory for the RAM copy of the environment.
124 It may also save flash memory if you decide to use this
125 when your environment is "embedded" within U-Boot code,
126 since then the remainder of the flash sector could be used
127 for U-Boot code. It should be pointed out that this is
128 STRONGLY DISCOURAGED from a robustness point of view:
129 updating the environment in flash makes it always
130 necessary to erase the WHOLE sector. If something goes
131 wrong before the contents has been restored from a copy in
132 RAM, your target system will be dead.
134 CONFIG_ENV_ADDR_REDUND
136 These settings describe a second storage area used to hold
137 a redundant copy of the environment data, so that there is
138 a valid backup copy in case there is a power failure during
139 a "saveenv" operation.
141 BE CAREFUL! Any changes to the flash layout, and some changes to the
142 source code will make it necessary to adapt <board>/u-boot.lds*
146 bool "Environment in an MMC device"
147 depends on !CHAIN_OF_TRUST
149 default y if ARCH_EXYNOS4
150 default y if MX6SX || MX7D
151 default y if TEGRA30 || TEGRA124
152 default y if TEGRA_ARMV8_COMMON
154 Define this if you have an MMC device which you want to use for the
157 CONFIG_SYS_MMC_ENV_DEV:
159 Specifies which MMC device the environment is stored in.
161 CONFIG_SYS_MMC_ENV_PART (optional):
163 Specifies which MMC partition the environment is stored in. If not
164 set, defaults to partition 0, the user area. Common values might be
165 1 (first MMC boot partition), 2 (second MMC boot partition).
170 These two #defines specify the offset and size of the environment
171 area within the specified MMC device.
173 If offset is positive (the usual case), it is treated as relative to
174 the start of the MMC partition. If offset is negative, it is treated
175 as relative to the end of the MMC partition. This can be useful if
176 your board may be fitted with different MMC devices, which have
177 different sizes for the MMC partitions, and you always want the
178 environment placed at the very end of the partition, to leave the
179 maximum possible space before it, to store other data.
181 These two values are in units of bytes, but must be aligned to an
184 CONFIG_ENV_OFFSET_REDUND (optional):
186 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
187 hold a redundant copy of the environment data. This provides a
188 valid backup copy in case the other copy is corrupted, e.g. due
189 to a power failure during a "saveenv" operation.
191 This value may also be positive or negative; this is handled in the
192 same way as CONFIG_ENV_OFFSET.
194 This value is also in units of bytes, but must also be aligned to
195 an MMC sector boundary.
197 config ENV_IS_IN_NAND
198 bool "Environment in a NAND device"
199 depends on !CHAIN_OF_TRUST
201 Define this if you have a NAND device which you want to use for the
207 These two #defines specify the offset and size of the environment
208 area within the first NAND device. CONFIG_ENV_OFFSET must be
209 aligned to an erase block boundary.
211 - CONFIG_ENV_OFFSET_REDUND (optional):
213 This setting describes a second storage area of CONFIG_ENV_SIZE
214 size used to hold a redundant copy of the environment data, so
215 that there is a valid backup copy in case there is a power failure
216 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
217 aligned to an erase block boundary.
219 - CONFIG_ENV_RANGE (optional):
221 Specifies the length of the region in which the environment
222 can be written. This should be a multiple of the NAND device's
223 block size. Specifying a range with more erase blocks than
224 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
225 the range to be avoided.
227 - CONFIG_ENV_OFFSET_OOB (optional):
229 Enables support for dynamically retrieving the offset of the
230 environment from block zero's out-of-band data. The
231 "nand env.oob" command can be used to record this offset.
232 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
233 using CONFIG_ENV_OFFSET_OOB.
235 config ENV_IS_IN_NVRAM
236 bool "Environment in a non-volatile RAM"
237 depends on !CHAIN_OF_TRUST
239 Define this if you have some non-volatile memory device
240 (NVRAM, battery buffered SRAM) which you want to use for the
246 These two #defines are used to determine the memory area you
247 want to use for environment. It is assumed that this memory
248 can just be read and written to, without any special
251 config ENV_IS_IN_ONENAND
252 bool "Environment is in OneNAND"
253 depends on !CHAIN_OF_TRUST
255 Define this if you want to put your local device's environment in
261 These two #defines are used to determine the device range you
262 want to use for environment. It is assumed that this memory
263 can just be read and written to, without any special
266 config ENV_IS_IN_REMOTE
267 bool "Environment is in remote memory space"
268 depends on !CHAIN_OF_TRUST
270 Define this if you have a remote memory space which you
271 want to use for the local device's environment.
276 These two #defines specify the address and size of the
277 environment area within the remote memory space. The
278 local device can get the environment from remote memory
279 space by SRIO or PCIE links.
281 config ENV_IS_IN_SPI_FLASH
282 bool "Environment is in SPI flash"
283 depends on !CHAIN_OF_TRUST && SPI
284 default y if ARMADA_XP
285 default y if INTEL_BAYTRAIL
286 default y if INTEL_BRASWELL
287 default y if INTEL_BROADWELL
288 default y if NORTHBRIDGE_INTEL_IVYBRIDGE
289 default y if INTEL_QUARK
290 default y if INTEL_QUEENSBAY
292 Define this if you have a SPI Flash memory device which you
293 want to use for the environment.
298 These two #defines specify the offset and size of the
299 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
300 aligned to an erase sector boundary.
302 - CONFIG_ENV_SECT_SIZE:
304 Define the SPI flash's sector size.
306 - CONFIG_ENV_OFFSET_REDUND (optional):
308 This setting describes a second storage area of CONFIG_ENV_SIZE
309 size used to hold a redundant copy of the environment data, so
310 that there is a valid backup copy in case there is a power failure
311 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
312 aligned to an erase sector boundary.
314 config USE_ENV_SPI_BUS
315 bool "SPI flash bus for environment"
316 depends on ENV_IS_IN_SPI_FLASH
318 Force the SPI bus for environment.
319 If not defined, use CONFIG_SF_DEFAULT_BUS.
322 int "Value of SPI flash bus for environment"
323 depends on USE_ENV_SPI_BUS
325 Value the SPI bus and chip select for environment.
327 config USE_ENV_SPI_CS
328 bool "SPI flash chip select for environment"
329 depends on ENV_IS_IN_SPI_FLASH
331 Force the SPI chip select for environment.
332 If not defined, use CONFIG_SF_DEFAULT_CS.
335 int "Value of SPI flash chip select for environment"
336 depends on USE_ENV_SPI_CS
338 Value of the SPI chip select for environment.
340 config USE_ENV_SPI_MAX_HZ
341 bool "SPI flash max frequency for environment"
342 depends on ENV_IS_IN_SPI_FLASH
344 Force the SPI max work clock for environment.
345 If not defined, use CONFIG_SF_DEFAULT_SPEED.
347 config ENV_SPI_MAX_HZ
348 int "Value of SPI flash max frequency for environment"
349 depends on USE_ENV_SPI_MAX_HZ
351 Value of the SPI max work clock for environment.
353 config USE_ENV_SPI_MODE
354 bool "SPI flash mode for environment"
355 depends on ENV_IS_IN_SPI_FLASH
357 Force the SPI work mode for environment.
360 hex "Value of SPI flash work mode for environment"
361 depends on USE_ENV_SPI_MODE
363 Value of the SPI work mode for environment.
364 See include/spi.h for value.
367 bool "Environment in a UBI volume"
368 depends on !CHAIN_OF_TRUST
372 Define this if you have an UBI volume that you want to use for the
373 environment. This has the benefit of wear-leveling the environment
374 accesses, which is important on NAND.
376 - CONFIG_ENV_UBI_PART:
378 Define this to a string that is the mtd partition containing the UBI.
380 - CONFIG_ENV_UBI_VOLUME:
382 Define this to the name of the volume that you want to store the
385 - CONFIG_ENV_UBI_VOLUME_REDUND:
387 Define this to the name of another volume to store a second copy of
388 the environment in. This will enable redundant environments in UBI.
389 It is assumed that both volumes are in the same MTD partition.
391 config SYS_REDUNDAND_ENVIRONMENT
392 bool "Enable redundant environment support"
393 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \
394 ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI
396 Normally, the environemt is stored in a single location. By
397 selecting this option, you can then define where to hold a redundant
398 copy of the environment data, so that there is a valid backup copy in
399 case there is a power failure during a "saveenv" operation.
401 config ENV_FAT_INTERFACE
402 string "Name of the block device for the environment"
403 depends on ENV_IS_IN_FAT
404 default "mmc" if ARCH_SUNXI
405 default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91
407 Define this to a string that is the name of the block device.
409 config ENV_FAT_DEVICE_AND_PART
410 string "Device and partition for where to store the environemt in FAT"
411 depends on ENV_IS_IN_FAT
412 default "0:1" if TI_COMMON_CMD_OPTIONS
413 default "0:auto" if ARCH_ZYNQMP
414 default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
415 default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
416 default "0" if ARCH_AT91
418 Define this to a string to specify the partition of the device. It can
421 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
422 - "D:P": device D partition P. Error occurs if device D has no
425 - "D" or "D:": device D partition 1 if device D has partition
426 table, or the whole device D if has no partition
428 - "D:auto": first partition in device D with bootable flag set.
429 If none, first valid partition in device D. If no
430 partition table then means device D.
433 string "Name of the FAT file to use for the environment"
434 depends on ENV_IS_IN_FAT
437 It's a string of the FAT file name. This file use to store the
440 config ENV_EXT4_INTERFACE
441 string "Name of the block device for the environment"
442 depends on ENV_IS_IN_EXT4
444 Define this to a string that is the name of the block device.
446 config ENV_EXT4_DEVICE_AND_PART
447 string "Device and partition for where to store the environemt in EXT4"
448 depends on ENV_IS_IN_EXT4
450 Define this to a string to specify the partition of the device. It can
453 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
454 - "D:P": device D partition P. Error occurs if device D has no
457 - "D" or "D:": device D partition 1 if device D has partition
458 table, or the whole device D if has no partition
460 - "D:auto": first partition in device D with bootable flag set.
461 If none, first valid partition in device D. If no
462 partition table then means device D.
465 string "Name of the EXT4 file to use for the environment"
466 depends on ENV_IS_IN_EXT4
469 It's a string of the EXT4 file name. This file use to store the
470 environment (explicit path to the file)
473 hex "Environment address"
474 depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
475 ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
476 default 0x0 if ENV_IS_IN_SPI_FLASH
478 Offset from the start of the device (or partition)
480 config ENV_ADDR_REDUND
481 hex "Redundant environment address"
482 depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
484 Offset from the start of the device (or partition) of the redundant
485 environment location.
488 hex "Environment offset"
489 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
491 default 0x3f8000 if ARCH_ROCKCHIP
492 default 0x88000 if ARCH_SUNXI
493 default 0xE0000 if ARCH_ZYNQ
494 default 0x1E00000 if ARCH_ZYNQMP
495 default 0x7F40000 if ARCH_VERSAL
497 default 0x140000 if ARCH_AT91
498 default 0x260000 if ARCH_OMAP2PLUS
500 Offset from the start of the device (or partition)
502 config ENV_OFFSET_REDUND
503 hex "Redundant environment offset"
504 depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
505 ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
507 Offset from the start of the device (or partition) of the redundant
508 environment location.
511 hex "Environment Size"
512 default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
513 default 0x20000 if ARCH_SUNXI || ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
514 default 0x8000 if ARCH_ROCKCHIP || ARCH_ZYNQMP || ARCH_VERSAL
515 default 0x4000 if ARC
518 Size of the environment storage area
521 hex "Environment Sector-Size"
522 depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
523 default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL
524 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
526 Size of the sector containing the environment.
529 string "UBI partition name"
530 depends on ENV_IS_IN_UBI
532 MTD partition containing the UBI device
534 config ENV_UBI_VOLUME
535 string "UBI volume name"
536 depends on ENV_IS_IN_UBI
538 Name of the volume that you want to store the environment in.
540 config ENV_UBI_VOLUME_REDUND
541 string "UBI redundant volume name"
542 depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
544 Name of the redundant volume that you want to store the environment in.
546 config ENV_UBI_VID_OFFSET
547 int "ubi environment VID offset"
548 depends on ENV_IS_IN_UBI
551 UBI VID offset for environment. If 0, no custom VID offset is used.
553 config SYS_RELOC_GD_ENV_ADDR
554 bool "Relocate gd->en_addr"
556 Relocate the early env_addr pointer so we know it is not inside
557 the binary. Some systems need this and for the rest, it doesn't hurt.
559 config USE_DEFAULT_ENV_FILE
560 bool "Create default environment from file"
562 Normally, the default environment is automatically generated
563 based on the settings of various CONFIG_* options, as well
564 as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
565 you can instead define the entire default environment in an
568 config DEFAULT_ENV_FILE
569 string "Path to default environment file"
570 depends on USE_DEFAULT_ENV_FILE
572 The path containing the default environment. The format is
573 the same as accepted by the mkenvimage tool: lines
574 containing key=value pairs, blank lines and lines beginning
577 config ENV_VARS_UBOOT_RUNTIME_CONFIG
578 bool "Add run-time information to the environment"
580 Enable this in order to add variables describing certain
581 run-time determined information about the hardware to the
582 environment. These will be named board_name, board_rev.
585 config SPL_ENV_IS_NOWHERE
586 bool "SPL Environment is not stored"
587 default y if ENV_IS_NOWHERE
589 Similar to ENV_IS_NOWHERE, used for SPL environment.
591 config SPL_ENV_IS_IN_MMC
592 bool "SPL Environment in an MMC device"
593 depends on !SPL_ENV_IS_NOWHERE
594 depends on ENV_IS_IN_MMC
597 Similar to ENV_IS_IN_MMC, used for SPL environment.
599 config SPL_ENV_IS_IN_FAT
600 bool "SPL Environment is in a FAT filesystem"
601 depends on !SPL_ENV_IS_NOWHERE
602 depends on ENV_IS_IN_FAT
605 Similar to ENV_IS_IN_FAT, used for SPL environment.
607 config SPL_ENV_IS_IN_EXT4
608 bool "SPL Environment is in a EXT4 filesystem"
609 depends on !SPL_ENV_IS_NOWHERE
610 depends on ENV_IS_IN_EXT4
613 Similar to ENV_IS_IN_EXT4, used for SPL environment.
615 config SPL_ENV_IS_IN_NAND
616 bool "SPL Environment in a NAND device"
617 depends on !SPL_ENV_IS_NOWHERE
618 depends on ENV_IS_IN_NAND
621 Similar to ENV_IS_IN_NAND, used for SPL environment.
623 config SPL_ENV_IS_IN_SPI_FLASH
624 bool "SPL Environment is in SPI flash"
625 depends on !SPL_ENV_IS_NOWHERE
626 depends on ENV_IS_IN_SPI_FLASH
629 Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
631 config SPL_ENV_IS_IN_FLASH
632 bool "SPL Environment in flash memory"
633 depends on !SPL_ENV_IS_NOWHERE
634 depends on ENV_IS_IN_FLASH
637 Similar to ENV_IS_IN_FLASH, used for SPL environment.
643 config TPL_ENV_IS_NOWHERE
644 bool "TPL Environment is not stored"
645 default y if ENV_IS_NOWHERE
647 Similar to ENV_IS_NOWHERE, used for TPL environment.
649 config TPL_ENV_IS_IN_MMC
650 bool "TPL Environment in an MMC device"
651 depends on !TPL_ENV_IS_NOWHERE
652 depends on ENV_IS_IN_MMC
655 Similar to ENV_IS_IN_MMC, used for TPL environment.
657 config TPL_ENV_IS_IN_FAT
658 bool "TPL Environment is in a FAT filesystem"
659 depends on !TPL_ENV_IS_NOWHERE
660 depends on ENV_IS_IN_FAT
663 Similar to ENV_IS_IN_FAT, used for TPL environment.
665 config TPL_ENV_IS_IN_EXT4
666 bool "TPL Environment is in a EXT4 filesystem"
667 depends on !TPL_ENV_IS_NOWHERE
668 depends on ENV_IS_IN_EXT4
671 Similar to ENV_IS_IN_EXT4, used for TPL environment.
673 config TPL_ENV_IS_IN_NAND
674 bool "TPL Environment in a NAND device"
675 depends on !TPL_ENV_IS_NOWHERE
676 depends on ENV_IS_IN_NAND
679 Similar to ENV_IS_IN_NAND, used for TPL environment.
681 config TPL_ENV_IS_IN_SPI_FLASH
682 bool "TPL Environment is in SPI flash"
683 depends on !TPL_ENV_IS_NOWHERE
684 depends on ENV_IS_IN_SPI_FLASH
687 Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
689 config TPL_ENV_IS_IN_FLASH
690 bool "TPL Environment in flash memory"
691 depends on !TPL_ENV_IS_NOWHERE
692 depends on ENV_IS_IN_FLASH
695 Similar to ENV_IS_IN_FLASH, used for TPL environment.