4 prompt "Select the location of the environment"
5 default ENV_IS_IN_MMC if ARCH_SUNXI
6 default ENV_IS_IN_MMC if ARCH_EXYNOS4
7 default ENV_IS_IN_MMC if MX6SX || MX7D
8 default ENV_IS_IN_MMC if TEGRA30 || TEGRA124
9 default ENV_IS_IN_MMC if TEGRA_ARMV8_COMMON
10 default ENV_IS_IN_FLASH if ARCH_CINTEGRATOR
11 default ENV_IS_IN_FLASH if ARCH_INTEGRATOR_CP
12 default ENV_IS_IN_FLASH if M548x || M547x || M5282 || MCF547x_8x
13 default ENV_IS_IN_FLASH if MCF532x || MCF52x2
14 default ENV_IS_IN_FLASH if MPC86xx || MPC83xx
15 default ENV_IS_IN_FLASH if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
16 default ENV_IS_IN_FLASH if SH && !CPU_SH4
17 default ENV_IS_IN_SPI_FLASH if ARMADA_XP
18 default ENV_IS_IN_SPI_FLASH if INTEL_BAYTRAIL
19 default ENV_IS_IN_SPI_FLASH if INTEL_BRASWELL
20 default ENV_IS_IN_SPI_FLASH if INTEL_BROADWELL
21 default ENV_IS_IN_SPI_FLASH if NORTHBRIDGE_INTEL_IVYBRIDGE
22 default ENV_IS_IN_SPI_FLASH if INTEL_QUARK
23 default ENV_IS_IN_SPI_FLASH if INTEL_QUEENSBAY
24 default ENV_IS_IN_FAT if ARCH_BCM283X
25 default ENV_IS_IN_FAT if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
26 default ENV_IS_NOWHERE
28 At present the environment can be stored in only one place. Use this
29 option to select the location. This is either a device (where the
30 environemnt information is simply written to a fixed location or
31 partition on the device) or a filesystem (where the environment
32 information is written to a file).
35 bool "Environment is not stored"
37 Define this if you don't want to or can't have an environment stored
38 on a storage medium. In this case the environemnt will still exist
39 while U-Boot is running, but once U-Boot exits it will not be
40 stored. U-Boot will therefore always start up with a default
43 config ENV_IS_IN_EEPROM
44 bool "Environment in EEPROM"
45 depends on !CHAIN_OF_TRUST
47 Use this if you have an EEPROM or similar serial access
48 device and a driver for it.
53 These two #defines specify the offset and size of the
54 environment area within the total memory of your EEPROM.
56 Note that we consider the length of the address field to
57 still be one byte because the extra address bits are hidden
60 - CONFIG_ENV_EEPROM_IS_ON_I2C
61 define this, if you have I2C and SPI activated, and your
62 EEPROM, which holds the environment, is on the I2C bus.
64 - CONFIG_I2C_ENV_EEPROM_BUS
65 if you have an Environment on an EEPROM reached over
66 I2C muxes, you can define here, how to reach this
69 #define CONFIG_I2C_ENV_EEPROM_BUS 1
71 EEPROM which holds the environment, is reached over
72 a pca9547 i2c mux with address 0x70, channel 3.
75 bool "Environment is in a FAT filesystem"
76 depends on !CHAIN_OF_TRUST
80 Define this if you want to use the FAT file system for the environment.
83 bool "Environment is in a EXT4 filesystem"
84 depends on !CHAIN_OF_TRUST
87 Define this if you want to use the EXT4 file system for the environment.
89 config ENV_IS_IN_FLASH
90 bool "Environment in flash memory"
91 depends on !CHAIN_OF_TRUST
93 Define this if you have a flash device which you want to use for the
96 a) The environment occupies one whole flash sector, which is
97 "embedded" in the text segment with the U-Boot code. This
98 happens usually with "bottom boot sector" or "top boot
99 sector" type flash chips, which have several smaller
100 sectors at the start or the end. For instance, such a
101 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
102 such a case you would place the environment in one of the
103 4 kB sectors - with U-Boot code before and after it. With
104 "top boot sector" type flash chips, you would put the
105 environment in one of the last sectors, leaving a gap
106 between U-Boot and the environment.
110 Offset of environment data (variable area) to the
111 beginning of flash memory; for instance, with bottom boot
112 type flash chips the second sector can be used: the offset
113 for this sector is given here.
115 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
119 This is just another way to specify the start address of
120 the flash sector containing the environment (instead of
123 CONFIG_ENV_SECT_SIZE:
125 Size of the sector containing the environment.
128 b) Sometimes flash chips have few, equal sized, BIG sectors.
129 In such a case you don't want to spend a whole sector for
134 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
135 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
136 of this flash sector for the environment. This saves
137 memory for the RAM copy of the environment.
139 It may also save flash memory if you decide to use this
140 when your environment is "embedded" within U-Boot code,
141 since then the remainder of the flash sector could be used
142 for U-Boot code. It should be pointed out that this is
143 STRONGLY DISCOURAGED from a robustness point of view:
144 updating the environment in flash makes it always
145 necessary to erase the WHOLE sector. If something goes
146 wrong before the contents has been restored from a copy in
147 RAM, your target system will be dead.
149 CONFIG_ENV_ADDR_REDUND
150 CONFIG_ENV_SIZE_REDUND
152 These settings describe a second storage area used to hold
153 a redundant copy of the environment data, so that there is
154 a valid backup copy in case there is a power failure during
155 a "saveenv" operation.
157 BE CAREFUL! Any changes to the flash layout, and some changes to the
158 source code will make it necessary to adapt <board>/u-boot.lds*
162 bool "Environment in an MMC device"
163 depends on !CHAIN_OF_TRUST
165 Define this if you have an MMC device which you want to use for the
168 CONFIG_SYS_MMC_ENV_DEV:
170 Specifies which MMC device the environment is stored in.
172 CONFIG_SYS_MMC_ENV_PART (optional):
174 Specifies which MMC partition the environment is stored in. If not
175 set, defaults to partition 0, the user area. Common values might be
176 1 (first MMC boot partition), 2 (second MMC boot partition).
181 These two #defines specify the offset and size of the environment
182 area within the specified MMC device.
184 If offset is positive (the usual case), it is treated as relative to
185 the start of the MMC partition. If offset is negative, it is treated
186 as relative to the end of the MMC partition. This can be useful if
187 your board may be fitted with different MMC devices, which have
188 different sizes for the MMC partitions, and you always want the
189 environment placed at the very end of the partition, to leave the
190 maximum possible space before it, to store other data.
192 These two values are in units of bytes, but must be aligned to an
195 CONFIG_ENV_OFFSET_REDUND (optional):
197 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
198 hold a redundant copy of the environment data. This provides a
199 valid backup copy in case the other copy is corrupted, e.g. due
200 to a power failure during a "saveenv" operation.
202 This value may also be positive or negative; this is handled in the
203 same way as CONFIG_ENV_OFFSET.
205 This value is also in units of bytes, but must also be aligned to
206 an MMC sector boundary.
208 CONFIG_ENV_SIZE_REDUND (optional):
210 This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
211 set. If this value is set, it must be set to the same value as
214 config ENV_IS_IN_NAND
215 bool "Environment in a NAND device"
216 depends on !CHAIN_OF_TRUST
218 Define this if you have a NAND device which you want to use for the
224 These two #defines specify the offset and size of the environment
225 area within the first NAND device. CONFIG_ENV_OFFSET must be
226 aligned to an erase block boundary.
228 - CONFIG_ENV_OFFSET_REDUND (optional):
230 This setting describes a second storage area of CONFIG_ENV_SIZE
231 size used to hold a redundant copy of the environment data, so
232 that there is a valid backup copy in case there is a power failure
233 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
234 aligned to an erase block boundary.
236 - CONFIG_ENV_RANGE (optional):
238 Specifies the length of the region in which the environment
239 can be written. This should be a multiple of the NAND device's
240 block size. Specifying a range with more erase blocks than
241 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
242 the range to be avoided.
244 - CONFIG_ENV_OFFSET_OOB (optional):
246 Enables support for dynamically retrieving the offset of the
247 environment from block zero's out-of-band data. The
248 "nand env.oob" command can be used to record this offset.
249 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
250 using CONFIG_ENV_OFFSET_OOB.
252 config ENV_IS_IN_NVRAM
253 bool "Environment in a non-volatile RAM"
254 depends on !CHAIN_OF_TRUST
256 Define this if you have some non-volatile memory device
257 (NVRAM, battery buffered SRAM) which you want to use for the
263 These two #defines are used to determine the memory area you
264 want to use for environment. It is assumed that this memory
265 can just be read and written to, without any special
268 config ENV_IS_IN_ONENAND
269 bool "Environment is in OneNAND"
270 depends on !CHAIN_OF_TRUST
272 Define this if you want to put your local device's environment in
278 These two #defines are used to determine the device range you
279 want to use for environment. It is assumed that this memory
280 can just be read and written to, without any special
283 config ENV_IS_IN_REMOTE
284 bool "Environment is in remove memory space"
285 depends on !CHAIN_OF_TRUST
287 Define this if you have a remote memory space which you
288 want to use for the local device's environment.
293 These two #defines specify the address and size of the
294 environment area within the remote memory space. The
295 local device can get the environment from remote memory
296 space by SRIO or PCIE links.
298 config ENV_IS_IN_SPI_FLASH
299 bool "Environment is in SPI flash"
300 depends on !CHAIN_OF_TRUST
302 Define this if you have a SPI Flash memory device which you
303 want to use for the environment.
308 These two #defines specify the offset and size of the
309 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
310 aligned to an erase sector boundary.
312 - CONFIG_ENV_SECT_SIZE:
314 Define the SPI flash's sector size.
316 - CONFIG_ENV_OFFSET_REDUND (optional):
318 This setting describes a second storage area of CONFIG_ENV_SIZE
319 size used to hold a redundant copy of the environment data, so
320 that there is a valid backup copy in case there is a power failure
321 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
322 aligned to an erase sector boundary.
324 - CONFIG_ENV_SPI_BUS (optional):
325 - CONFIG_ENV_SPI_CS (optional):
327 Define the SPI bus and chip select. If not defined they will be 0.
329 - CONFIG_ENV_SPI_MAX_HZ (optional):
331 Define the SPI max work clock. If not defined then use 1MHz.
333 - CONFIG_ENV_SPI_MODE (optional):
335 Define the SPI work mode. If not defined then use SPI_MODE_3.
338 bool "Environment in a UBI volume"
339 depends on !CHAIN_OF_TRUST
341 Define this if you have an UBI volume that you want to use for the
342 environment. This has the benefit of wear-leveling the environment
343 accesses, which is important on NAND.
345 - CONFIG_ENV_UBI_PART:
347 Define this to a string that is the mtd partition containing the UBI.
349 - CONFIG_ENV_UBI_VOLUME:
351 Define this to the name of the volume that you want to store the
354 - CONFIG_ENV_UBI_VOLUME_REDUND:
356 Define this to the name of another volume to store a second copy of
357 the environment in. This will enable redundant environments in UBI.
358 It is assumed that both volumes are in the same MTD partition.
360 - CONFIG_UBI_SILENCE_MSG
361 - CONFIG_UBIFS_SILENCE_MSG
363 You will probably want to define these to avoid a really noisy system
364 when storing the env in UBI.
368 config ENV_FAT_INTERFACE
369 string "Name of the block device for the environment"
370 depends on ENV_IS_IN_FAT
371 default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91
373 Define this to a string that is the name of the block device.
375 config ENV_FAT_DEVICE_AND_PART
376 string "Device and partition for where to store the environemt in FAT"
377 depends on ENV_IS_IN_FAT
378 default "0:1" if TI_COMMON_CMD_OPTIONS
379 default "0:auto" if ARCH_ZYNQMP
380 default "0" if ARCH_AT91
382 Define this to a string to specify the partition of the device. It can
385 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
386 - "D:P": device D partition P. Error occurs if device D has no
389 - "D" or "D:": device D partition 1 if device D has partition
390 table, or the whole device D if has no partition
392 - "D:auto": first partition in device D with bootable flag set.
393 If none, first valid partition in device D. If no
394 partition table then means device D.
397 string "Name of the FAT file to use for the environemnt"
398 depends on ENV_IS_IN_FAT
401 It's a string of the FAT file name. This file use to store the
404 config ENV_EXT4_INTERFACE
405 string "Name of the block device for the environment"
406 depends on ENV_IS_IN_EXT4
408 Define this to a string that is the name of the block device.
410 config ENV_EXT4_DEVICE_AND_PART
411 string "Device and partition for where to store the environemt in EXT4"
412 depends on ENV_IS_IN_EXT4
414 Define this to a string to specify the partition of the device. It can
417 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
418 - "D:P": device D partition P. Error occurs if device D has no
421 - "D" or "D:": device D partition 1 if device D has partition
422 table, or the whole device D if has no partition
424 - "D:auto": first partition in device D with bootable flag set.
425 If none, first valid partition in device D. If no
426 partition table then means device D.
429 string "Name of the EXT4 file to use for the environemnt"
430 depends on ENV_IS_IN_EXT4
433 It's a string of the EXT4 file name. This file use to store the
434 environment (explicit path to the file)
439 hex "Environment Offset"
440 depends on !ENV_IS_IN_UBI
441 depends on !ENV_IS_NOWHERE
442 default 0x88000 if ARCH_SUNXI
444 Offset from the start of the device (or partition)
447 hex "Environment Size"
448 depends on !ENV_IS_NOWHERE
449 default 0x20000 if ARCH_SUNXI
451 Size of the environment storage area
454 string "UBI partition name"
455 depends on ENV_IS_IN_UBI
457 MTD partition containing the UBI device
459 config ENV_UBI_VOLUME
460 string "UBI volume name"
461 depends on ENV_IS_IN_UBI
463 Name of the volume that you want to store the environment in.
471 depends on !ENV_IS_IN_UBI
472 depends on !ENV_IS_NOWHERE
475 Offset from the start of the device (or partition)
481 Size of the environment storage area