7 def_bool y if CMD_SAVEENV
10 bool "Environment is not stored"
11 default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
12 !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
13 !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
14 !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
15 !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
18 Define this if you don't want to or can't have an environment stored
19 on a storage medium. In this case the environment will still exist
20 while U-Boot is running, but once U-Boot exits it will not be
21 stored. U-Boot will therefore always start up with a default
24 config ENV_IS_IN_EEPROM
25 bool "Environment in EEPROM"
26 depends on !CHAIN_OF_TRUST
28 Use this if you have an EEPROM or similar serial access
29 device and a driver for it.
34 These two #defines specify the offset and size of the
35 environment area within the total memory of your EEPROM.
37 Note that we consider the length of the address field to
38 still be one byte because the extra address bits are hidden
41 - CONFIG_ENV_EEPROM_IS_ON_I2C
42 define this, if you have I2C and SPI activated, and your
43 EEPROM, which holds the environment, is on the I2C bus.
45 - CONFIG_I2C_ENV_EEPROM_BUS
46 if you have an Environment on an EEPROM reached over
47 I2C muxes, you can define here, how to reach this
50 #define CONFIG_I2C_ENV_EEPROM_BUS 1
52 EEPROM which holds the environment, is reached over
53 a pca9547 i2c mux with address 0x70, channel 3.
56 bool "Environment is in a FAT filesystem"
57 depends on !CHAIN_OF_TRUST
58 default y if ARCH_BCM283X
59 default y if ARCH_SUNXI && MMC
60 default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
64 Define this if you want to use the FAT file system for the environment.
67 bool "Environment is in a EXT4 filesystem"
68 depends on !CHAIN_OF_TRUST
71 Define this if you want to use the EXT4 file system for the environment.
73 config ENV_IS_IN_FLASH
74 bool "Environment in flash memory"
75 depends on !CHAIN_OF_TRUST
76 default y if ARCH_CINTEGRATOR
77 default y if ARCH_INTEGRATOR_CP
78 default y if M548x || M547x || M5282 || MCF547x_8x
79 default y if MCF532x || MCF52x2
80 default y if MPC86xx || MPC83xx
81 default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
82 default y if SH && !CPU_SH4
84 Define this if you have a flash device which you want to use for the
87 a) The environment occupies one whole flash sector, which is
88 "embedded" in the text segment with the U-Boot code. This
89 happens usually with "bottom boot sector" or "top boot
90 sector" type flash chips, which have several smaller
91 sectors at the start or the end. For instance, such a
92 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
93 such a case you would place the environment in one of the
94 4 kB sectors - with U-Boot code before and after it. With
95 "top boot sector" type flash chips, you would put the
96 environment in one of the last sectors, leaving a gap
97 between U-Boot and the environment.
101 Offset of environment data (variable area) to the
102 beginning of flash memory; for instance, with bottom boot
103 type flash chips the second sector can be used: the offset
104 for this sector is given here.
106 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
110 This is just another way to specify the start address of
111 the flash sector containing the environment (instead of
114 CONFIG_ENV_SECT_SIZE:
116 Size of the sector containing the environment.
119 b) Sometimes flash chips have few, equal sized, BIG sectors.
120 In such a case you don't want to spend a whole sector for
125 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
126 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
127 of this flash sector for the environment. This saves
128 memory for the RAM copy of the environment.
130 It may also save flash memory if you decide to use this
131 when your environment is "embedded" within U-Boot code,
132 since then the remainder of the flash sector could be used
133 for U-Boot code. It should be pointed out that this is
134 STRONGLY DISCOURAGED from a robustness point of view:
135 updating the environment in flash makes it always
136 necessary to erase the WHOLE sector. If something goes
137 wrong before the contents has been restored from a copy in
138 RAM, your target system will be dead.
140 CONFIG_ENV_ADDR_REDUND
142 These settings describe a second storage area used to hold
143 a redundant copy of the environment data, so that there is
144 a valid backup copy in case there is a power failure during
145 a "saveenv" operation.
147 BE CAREFUL! Any changes to the flash layout, and some changes to the
148 source code will make it necessary to adapt <board>/u-boot.lds*
152 bool "Environment in an MMC device"
153 depends on !CHAIN_OF_TRUST
155 default y if ARCH_EXYNOS4
156 default y if MX6SX || MX7D
157 default y if TEGRA30 || TEGRA124
158 default y if TEGRA_ARMV8_COMMON
160 Define this if you have an MMC device which you want to use for the
163 CONFIG_SYS_MMC_ENV_DEV:
165 Specifies which MMC device the environment is stored in.
167 CONFIG_SYS_MMC_ENV_PART (optional):
169 Specifies which MMC partition the environment is stored in. If not
170 set, defaults to partition 0, the user area. Common values might be
171 1 (first MMC boot partition), 2 (second MMC boot partition).
176 These two #defines specify the offset and size of the environment
177 area within the specified MMC device.
179 If offset is positive (the usual case), it is treated as relative to
180 the start of the MMC partition. If offset is negative, it is treated
181 as relative to the end of the MMC partition. This can be useful if
182 your board may be fitted with different MMC devices, which have
183 different sizes for the MMC partitions, and you always want the
184 environment placed at the very end of the partition, to leave the
185 maximum possible space before it, to store other data.
187 These two values are in units of bytes, but must be aligned to an
190 CONFIG_ENV_OFFSET_REDUND (optional):
192 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
193 hold a redundant copy of the environment data. This provides a
194 valid backup copy in case the other copy is corrupted, e.g. due
195 to a power failure during a "saveenv" operation.
197 This value may also be positive or negative; this is handled in the
198 same way as CONFIG_ENV_OFFSET.
200 This value is also in units of bytes, but must also be aligned to
201 an MMC sector boundary.
203 config ENV_IS_IN_NAND
204 bool "Environment in a NAND device"
205 depends on !CHAIN_OF_TRUST
207 Define this if you have a NAND device which you want to use for the
213 These two #defines specify the offset and size of the environment
214 area within the first NAND device. CONFIG_ENV_OFFSET must be
215 aligned to an erase block boundary.
217 - CONFIG_ENV_OFFSET_REDUND (optional):
219 This setting describes a second storage area of CONFIG_ENV_SIZE
220 size used to hold a redundant copy of the environment data, so
221 that there is a valid backup copy in case there is a power failure
222 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
223 aligned to an erase block boundary.
225 - CONFIG_ENV_RANGE (optional):
227 Specifies the length of the region in which the environment
228 can be written. This should be a multiple of the NAND device's
229 block size. Specifying a range with more erase blocks than
230 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
231 the range to be avoided.
233 - CONFIG_ENV_OFFSET_OOB (optional):
235 Enables support for dynamically retrieving the offset of the
236 environment from block zero's out-of-band data. The
237 "nand env.oob" command can be used to record this offset.
238 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
239 using CONFIG_ENV_OFFSET_OOB.
241 config ENV_IS_IN_NVRAM
242 bool "Environment in a non-volatile RAM"
243 depends on !CHAIN_OF_TRUST
245 Define this if you have some non-volatile memory device
246 (NVRAM, battery buffered SRAM) which you want to use for the
252 These two #defines are used to determine the memory area you
253 want to use for environment. It is assumed that this memory
254 can just be read and written to, without any special
257 config ENV_IS_IN_ONENAND
258 bool "Environment is in OneNAND"
259 depends on !CHAIN_OF_TRUST
261 Define this if you want to put your local device's environment in
267 These two #defines are used to determine the device range you
268 want to use for environment. It is assumed that this memory
269 can just be read and written to, without any special
272 config ENV_IS_IN_REMOTE
273 bool "Environment is in remote memory space"
274 depends on !CHAIN_OF_TRUST
276 Define this if you have a remote memory space which you
277 want to use for the local device's environment.
282 These two #defines specify the address and size of the
283 environment area within the remote memory space. The
284 local device can get the environment from remote memory
285 space by SRIO or PCIE links.
287 config ENV_IS_IN_SPI_FLASH
288 bool "Environment is in SPI flash"
289 depends on !CHAIN_OF_TRUST && SPI
290 default y if ARMADA_XP
291 default y if INTEL_BAYTRAIL
292 default y if INTEL_BRASWELL
293 default y if INTEL_BROADWELL
294 default y if NORTHBRIDGE_INTEL_IVYBRIDGE
295 default y if INTEL_QUARK
296 default y if INTEL_QUEENSBAY
298 Define this if you have a SPI Flash memory device which you
299 want to use for the environment.
304 These two #defines specify the offset and size of the
305 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
306 aligned to an erase sector boundary.
308 - CONFIG_ENV_SECT_SIZE:
310 Define the SPI flash's sector size.
312 - CONFIG_ENV_OFFSET_REDUND (optional):
314 This setting describes a second storage area of CONFIG_ENV_SIZE
315 size used to hold a redundant copy of the environment data, so
316 that there is a valid backup copy in case there is a power failure
317 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
318 aligned to an erase sector boundary.
320 config USE_ENV_SPI_BUS
321 bool "SPI flash bus for environment"
322 depends on ENV_IS_IN_SPI_FLASH
324 Force the SPI bus for environment.
325 If not defined, use CONFIG_SF_DEFAULT_BUS.
328 int "Value of SPI flash bus for environment"
329 depends on USE_ENV_SPI_BUS
331 Value the SPI bus and chip select for environment.
333 config USE_ENV_SPI_CS
334 bool "SPI flash chip select for environment"
335 depends on ENV_IS_IN_SPI_FLASH
337 Force the SPI chip select for environment.
338 If not defined, use CONFIG_SF_DEFAULT_CS.
341 int "Value of SPI flash chip select for environment"
342 depends on USE_ENV_SPI_CS
344 Value of the SPI chip select for environment.
346 config USE_ENV_SPI_MAX_HZ
347 bool "SPI flash max frequency for environment"
348 depends on ENV_IS_IN_SPI_FLASH
350 Force the SPI max work clock for environment.
351 If not defined, use CONFIG_SF_DEFAULT_SPEED.
353 config ENV_SPI_MAX_HZ
354 int "Value of SPI flash max frequency for environment"
355 depends on USE_ENV_SPI_MAX_HZ
357 Value of the SPI max work clock for environment.
359 config USE_ENV_SPI_MODE
360 bool "SPI flash mode for environment"
361 depends on ENV_IS_IN_SPI_FLASH
363 Force the SPI work mode for environment.
366 hex "Value of SPI flash work mode for environment"
367 depends on USE_ENV_SPI_MODE
369 Value of the SPI work mode for environment.
370 See include/spi.h for value.
373 bool "Environment in a UBI volume"
374 depends on !CHAIN_OF_TRUST
378 Define this if you have an UBI volume that you want to use for the
379 environment. This has the benefit of wear-leveling the environment
380 accesses, which is important on NAND.
382 - CONFIG_ENV_UBI_PART:
384 Define this to a string that is the mtd partition containing the UBI.
386 - CONFIG_ENV_UBI_VOLUME:
388 Define this to the name of the volume that you want to store the
391 - CONFIG_ENV_UBI_VOLUME_REDUND:
393 Define this to the name of another volume to store a second copy of
394 the environment in. This will enable redundant environments in UBI.
395 It is assumed that both volumes are in the same MTD partition.
397 config SYS_REDUNDAND_ENVIRONMENT
398 bool "Enable redundant environment support"
399 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \
400 ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI
402 Normally, the environemt is stored in a single location. By
403 selecting this option, you can then define where to hold a redundant
404 copy of the environment data, so that there is a valid backup copy in
405 case there is a power failure during a "saveenv" operation.
407 config ENV_FAT_INTERFACE
408 string "Name of the block device for the environment"
409 depends on ENV_IS_IN_FAT
412 Define this to a string that is the name of the block device.
414 config ENV_FAT_DEVICE_AND_PART
415 string "Device and partition for where to store the environemt in FAT"
416 depends on ENV_IS_IN_FAT
417 default "0:1" if TI_COMMON_CMD_OPTIONS
418 default "0:auto" if ARCH_ZYNQMP
419 default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
420 default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
421 default "0" if ARCH_AT91
423 Define this to a string to specify the partition of the device. It can
426 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
427 - "D:P": device D partition P. Error occurs if device D has no
430 - "D" or "D:": device D partition 1 if device D has partition
431 table, or the whole device D if has no partition
433 - "D:auto": first partition in device D with bootable flag set.
434 If none, first valid partition in device D. If no
435 partition table then means device D.
438 string "Name of the FAT file to use for the environment"
439 depends on ENV_IS_IN_FAT
442 It's a string of the FAT file name. This file use to store the
445 config ENV_EXT4_INTERFACE
446 string "Name of the block device for the environment"
447 depends on ENV_IS_IN_EXT4
449 Define this to a string that is the name of the block device.
451 config ENV_EXT4_DEVICE_AND_PART
452 string "Device and partition for where to store the environemt in EXT4"
453 depends on ENV_IS_IN_EXT4
455 Define this to a string to specify the partition of the device. It can
458 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
459 - "D:P": device D partition P. Error occurs if device D has no
462 - "D" or "D:": device D partition 1 if device D has partition
463 table, or the whole device D if has no partition
465 - "D:auto": first partition in device D with bootable flag set.
466 If none, first valid partition in device D. If no
467 partition table then means device D.
470 string "Name of the EXT4 file to use for the environment"
471 depends on ENV_IS_IN_EXT4
474 It's a string of the EXT4 file name. This file use to store the
475 environment (explicit path to the file)
478 hex "Environment address"
479 depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
480 ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
481 default 0x0 if ENV_IS_IN_SPI_FLASH
483 Offset from the start of the device (or partition)
485 config ENV_ADDR_REDUND
486 hex "Redundant environment address"
487 depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
489 Offset from the start of the device (or partition) of the redundant
490 environment location.
493 hex "Environment offset"
494 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
496 default 0x3f8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
497 default 0x140000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
498 default 0x88000 if ARCH_SUNXI
499 default 0xE0000 if ARCH_ZYNQ
500 default 0x1E00000 if ARCH_ZYNQMP
501 default 0x7F40000 if ARCH_VERSAL
503 default 0x140000 if ARCH_AT91
504 default 0x260000 if ARCH_OMAP2PLUS
505 default 0x1080000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
507 Offset from the start of the device (or partition)
509 config ENV_OFFSET_REDUND
510 hex "Redundant environment offset"
511 depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
512 ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
514 Offset from the start of the device (or partition) of the redundant
515 environment location.
518 hex "Environment Size"
519 default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
520 default 0x20000 if ARCH_SUNXI || ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
521 default 0x8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
522 default 0x2000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
523 default 0x8000 if ARCH_ZYNQMP || ARCH_VERSAL
524 default 0x4000 if ARC
527 Size of the environment storage area
530 hex "Environment Sector-Size"
531 depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
532 default 0x2000 if ARCH_ROCKCHIP
533 default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL
534 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
535 default 0x20000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
537 Size of the sector containing the environment.
540 string "UBI partition name"
541 depends on ENV_IS_IN_UBI
543 MTD partition containing the UBI device
545 config ENV_UBI_VOLUME
546 string "UBI volume name"
547 depends on ENV_IS_IN_UBI
549 Name of the volume that you want to store the environment in.
551 config ENV_UBI_VOLUME_REDUND
552 string "UBI redundant volume name"
553 depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
555 Name of the redundant volume that you want to store the environment in.
557 config ENV_UBI_VID_OFFSET
558 int "ubi environment VID offset"
559 depends on ENV_IS_IN_UBI
562 UBI VID offset for environment. If 0, no custom VID offset is used.
564 config SYS_RELOC_GD_ENV_ADDR
565 bool "Relocate gd->env_addr"
567 Relocate the early env_addr pointer so we know it is not inside
568 the binary. Some systems need this and for the rest, it doesn't hurt.
570 config USE_DEFAULT_ENV_FILE
571 bool "Create default environment from file"
573 Normally, the default environment is automatically generated
574 based on the settings of various CONFIG_* options, as well
575 as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
576 you can instead define the entire default environment in an
579 config DEFAULT_ENV_FILE
580 string "Path to default environment file"
581 depends on USE_DEFAULT_ENV_FILE
583 The path containing the default environment. The format is
584 the same as accepted by the mkenvimage tool: lines
585 containing key=value pairs, blank lines and lines beginning
588 config ENV_VARS_UBOOT_RUNTIME_CONFIG
589 bool "Add run-time information to the environment"
591 Enable this in order to add variables describing certain
592 run-time determined information about the hardware to the
593 environment. These will be named board_name, board_rev.
595 config DELAY_ENVIRONMENT
596 bool "Delay environment loading"
597 depends on !OF_CONTROL
599 Enable this to inhibit loading the environment during board
600 initialization. This can address the security risk of untrusted data
601 being used during boot. Normally the environment is loaded when the
602 board is initialised so that it is available to U-Boot. This inhibits
603 that so that the environment is not available until explicitly loaded
604 later by U-Boot code. With CONFIG_OF_CONTROL this is instead
605 controlled by the value of /config/load-environment.
607 config ENV_ACCESS_IGNORE_FORCE
608 bool "Block forced environment operations"
611 If defined, don't allow the -f switch to env set override variable
615 config SPL_ENV_IS_NOWHERE
616 bool "SPL Environment is not stored"
617 default y if ENV_IS_NOWHERE
619 Similar to ENV_IS_NOWHERE, used for SPL environment.
621 config SPL_ENV_IS_IN_MMC
622 bool "SPL Environment in an MMC device"
623 depends on !SPL_ENV_IS_NOWHERE
624 depends on ENV_IS_IN_MMC
627 Similar to ENV_IS_IN_MMC, used for SPL environment.
629 config SPL_ENV_IS_IN_FAT
630 bool "SPL Environment is in a FAT filesystem"
631 depends on !SPL_ENV_IS_NOWHERE
632 depends on ENV_IS_IN_FAT
635 Similar to ENV_IS_IN_FAT, used for SPL environment.
637 config SPL_ENV_IS_IN_EXT4
638 bool "SPL Environment is in a EXT4 filesystem"
639 depends on !SPL_ENV_IS_NOWHERE
640 depends on ENV_IS_IN_EXT4
643 Similar to ENV_IS_IN_EXT4, used for SPL environment.
645 config SPL_ENV_IS_IN_NAND
646 bool "SPL Environment in a NAND device"
647 depends on !SPL_ENV_IS_NOWHERE
648 depends on ENV_IS_IN_NAND
651 Similar to ENV_IS_IN_NAND, used for SPL environment.
653 config SPL_ENV_IS_IN_SPI_FLASH
654 bool "SPL Environment is in SPI flash"
655 depends on !SPL_ENV_IS_NOWHERE
656 depends on ENV_IS_IN_SPI_FLASH
659 Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
661 config SPL_ENV_IS_IN_FLASH
662 bool "SPL Environment in flash memory"
663 depends on !SPL_ENV_IS_NOWHERE
664 depends on ENV_IS_IN_FLASH
667 Similar to ENV_IS_IN_FLASH, used for SPL environment.
673 config TPL_ENV_IS_NOWHERE
674 bool "TPL Environment is not stored"
675 default y if ENV_IS_NOWHERE
677 Similar to ENV_IS_NOWHERE, used for TPL environment.
679 config TPL_ENV_IS_IN_MMC
680 bool "TPL Environment in an MMC device"
681 depends on !TPL_ENV_IS_NOWHERE
682 depends on ENV_IS_IN_MMC
685 Similar to ENV_IS_IN_MMC, used for TPL environment.
687 config TPL_ENV_IS_IN_FAT
688 bool "TPL Environment is in a FAT filesystem"
689 depends on !TPL_ENV_IS_NOWHERE
690 depends on ENV_IS_IN_FAT
693 Similar to ENV_IS_IN_FAT, used for TPL environment.
695 config TPL_ENV_IS_IN_EXT4
696 bool "TPL Environment is in a EXT4 filesystem"
697 depends on !TPL_ENV_IS_NOWHERE
698 depends on ENV_IS_IN_EXT4
701 Similar to ENV_IS_IN_EXT4, used for TPL environment.
703 config TPL_ENV_IS_IN_NAND
704 bool "TPL Environment in a NAND device"
705 depends on !TPL_ENV_IS_NOWHERE
706 depends on ENV_IS_IN_NAND
709 Similar to ENV_IS_IN_NAND, used for TPL environment.
711 config TPL_ENV_IS_IN_SPI_FLASH
712 bool "TPL Environment is in SPI flash"
713 depends on !TPL_ENV_IS_NOWHERE
714 depends on ENV_IS_IN_SPI_FLASH
717 Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
719 config TPL_ENV_IS_IN_FLASH
720 bool "TPL Environment in flash memory"
721 depends on !TPL_ENV_IS_NOWHERE
722 depends on ENV_IS_IN_FLASH
725 Similar to ENV_IS_IN_FLASH, used for TPL environment.