]>
Commit | Line | Data |
---|---|---|
0649cd0d SG |
1 | menu "Environment" |
2 | ||
c1c3fe23 SG |
3 | choice |
4 | prompt "Select the location of the environment" | |
5 | default ENV_IS_IN_MMC if ARCH_SUNXI | |
c1c3fe23 SG |
6 | default ENV_IS_IN_MMC if ARCH_EXYNOS4 |
7 | default ENV_IS_IN_MMC if MX6SX || MX7D | |
c1c3fe23 SG |
8 | default ENV_IS_IN_MMC if TEGRA30 || TEGRA124 |
9 | default ENV_IS_IN_MMC if TEGRA_ARMV8_COMMON | |
e94c1268 | 10 | default ENV_IS_IN_FLASH if ARCH_CINTEGRATOR |
c1c3fe23 SG |
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 | |
e94c1268 | 17 | default ENV_IS_IN_SPI_FLASH if ARMADA_XP |
c1c3fe23 | 18 | default ENV_IS_IN_SPI_FLASH if INTEL_BAYTRAIL |
3a856473 | 19 | default ENV_IS_IN_SPI_FLASH if INTEL_BRASWELL |
c1c3fe23 SG |
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 | |
e94c1268 | 24 | default ENV_IS_IN_FAT if ARCH_BCM283X |
c1c3fe23 SG |
25 | default ENV_IS_IN_FAT if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS |
26 | default ENV_IS_NOWHERE | |
27 | help | |
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). | |
33 | ||
34 | config ENV_IS_NOWHERE | |
35 | bool "Environment is not stored" | |
36 | help | |
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 | |
41 | environment. | |
42 | ||
0649cd0d SG |
43 | config ENV_IS_IN_EEPROM |
44 | bool "Environment in EEPROM" | |
45 | depends on !CHAIN_OF_TRUST | |
46 | help | |
47 | Use this if you have an EEPROM or similar serial access | |
48 | device and a driver for it. | |
49 | ||
50 | - CONFIG_ENV_OFFSET: | |
51 | - CONFIG_ENV_SIZE: | |
52 | ||
53 | These two #defines specify the offset and size of the | |
54 | environment area within the total memory of your EEPROM. | |
55 | ||
0649cd0d SG |
56 | Note that we consider the length of the address field to |
57 | still be one byte because the extra address bits are hidden | |
58 | in the chip address. | |
59 | ||
0649cd0d SG |
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. | |
63 | ||
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 | |
67 | EEPROM. For example: | |
68 | ||
69 | #define CONFIG_I2C_ENV_EEPROM_BUS 1 | |
70 | ||
71 | EEPROM which holds the environment, is reached over | |
72 | a pca9547 i2c mux with address 0x70, channel 3. | |
73 | ||
74 | config ENV_IS_IN_FAT | |
75 | bool "Environment is in a FAT filesystem" | |
76 | depends on !CHAIN_OF_TRUST | |
3cd084d3 | 77 | select FS_FAT |
0649cd0d SG |
78 | select FAT_WRITE |
79 | help | |
91d3aa05 | 80 | Define this if you want to use the FAT file system for the environment. |
0649cd0d | 81 | |
1087a794 JRO |
82 | config ENV_IS_IN_EXT4 |
83 | bool "Environment is in a EXT4 filesystem" | |
84 | depends on !CHAIN_OF_TRUST | |
85 | select EXT4_WRITE | |
86 | help | |
87 | Define this if you want to use the EXT4 file system for the environment. | |
88 | ||
0649cd0d SG |
89 | config ENV_IS_IN_FLASH |
90 | bool "Environment in flash memory" | |
91 | depends on !CHAIN_OF_TRUST | |
92 | help | |
93 | Define this if you have a flash device which you want to use for the | |
94 | environment. | |
95 | ||
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. | |
107 | ||
108 | CONFIG_ENV_OFFSET: | |
109 | ||
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. | |
114 | ||
115 | CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE. | |
116 | ||
117 | CONFIG_ENV_ADDR: | |
118 | ||
119 | This is just another way to specify the start address of | |
120 | the flash sector containing the environment (instead of | |
121 | CONFIG_ENV_OFFSET). | |
122 | ||
123 | CONFIG_ENV_SECT_SIZE: | |
124 | ||
125 | Size of the sector containing the environment. | |
126 | ||
127 | ||
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 | |
130 | the environment. | |
131 | ||
132 | CONFIG_ENV_SIZE: | |
133 | ||
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. | |
138 | ||
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. | |
148 | ||
149 | CONFIG_ENV_ADDR_REDUND | |
150 | CONFIG_ENV_SIZE_REDUND | |
151 | ||
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. | |
156 | ||
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* | |
159 | accordingly! | |
160 | ||
161 | config ENV_IS_IN_MMC | |
162 | bool "Environment in an MMC device" | |
163 | depends on !CHAIN_OF_TRUST | |
d282a1db | 164 | depends on MMC |
0649cd0d SG |
165 | help |
166 | Define this if you have an MMC device which you want to use for the | |
167 | environment. | |
168 | ||
169 | CONFIG_SYS_MMC_ENV_DEV: | |
170 | ||
171 | Specifies which MMC device the environment is stored in. | |
172 | ||
173 | CONFIG_SYS_MMC_ENV_PART (optional): | |
174 | ||
175 | Specifies which MMC partition the environment is stored in. If not | |
176 | set, defaults to partition 0, the user area. Common values might be | |
177 | 1 (first MMC boot partition), 2 (second MMC boot partition). | |
178 | ||
179 | CONFIG_ENV_OFFSET: | |
180 | CONFIG_ENV_SIZE: | |
181 | ||
182 | These two #defines specify the offset and size of the environment | |
183 | area within the specified MMC device. | |
184 | ||
185 | If offset is positive (the usual case), it is treated as relative to | |
186 | the start of the MMC partition. If offset is negative, it is treated | |
187 | as relative to the end of the MMC partition. This can be useful if | |
188 | your board may be fitted with different MMC devices, which have | |
189 | different sizes for the MMC partitions, and you always want the | |
190 | environment placed at the very end of the partition, to leave the | |
191 | maximum possible space before it, to store other data. | |
192 | ||
193 | These two values are in units of bytes, but must be aligned to an | |
194 | MMC sector boundary. | |
195 | ||
196 | CONFIG_ENV_OFFSET_REDUND (optional): | |
197 | ||
198 | Specifies a second storage area, of CONFIG_ENV_SIZE size, used to | |
199 | hold a redundant copy of the environment data. This provides a | |
200 | valid backup copy in case the other copy is corrupted, e.g. due | |
201 | to a power failure during a "saveenv" operation. | |
202 | ||
203 | This value may also be positive or negative; this is handled in the | |
204 | same way as CONFIG_ENV_OFFSET. | |
205 | ||
206 | This value is also in units of bytes, but must also be aligned to | |
207 | an MMC sector boundary. | |
208 | ||
209 | CONFIG_ENV_SIZE_REDUND (optional): | |
210 | ||
211 | This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is | |
212 | set. If this value is set, it must be set to the same value as | |
213 | CONFIG_ENV_SIZE. | |
214 | ||
215 | config ENV_IS_IN_NAND | |
216 | bool "Environment in a NAND device" | |
217 | depends on !CHAIN_OF_TRUST | |
218 | help | |
219 | Define this if you have a NAND device which you want to use for the | |
220 | environment. | |
221 | ||
222 | - CONFIG_ENV_OFFSET: | |
223 | - CONFIG_ENV_SIZE: | |
224 | ||
225 | These two #defines specify the offset and size of the environment | |
226 | area within the first NAND device. CONFIG_ENV_OFFSET must be | |
227 | aligned to an erase block boundary. | |
228 | ||
229 | - CONFIG_ENV_OFFSET_REDUND (optional): | |
230 | ||
231 | This setting describes a second storage area of CONFIG_ENV_SIZE | |
232 | size used to hold a redundant copy of the environment data, so | |
233 | that there is a valid backup copy in case there is a power failure | |
234 | during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be | |
235 | aligned to an erase block boundary. | |
236 | ||
237 | - CONFIG_ENV_RANGE (optional): | |
238 | ||
239 | Specifies the length of the region in which the environment | |
240 | can be written. This should be a multiple of the NAND device's | |
241 | block size. Specifying a range with more erase blocks than | |
242 | are needed to hold CONFIG_ENV_SIZE allows bad blocks within | |
243 | the range to be avoided. | |
244 | ||
245 | - CONFIG_ENV_OFFSET_OOB (optional): | |
246 | ||
247 | Enables support for dynamically retrieving the offset of the | |
248 | environment from block zero's out-of-band data. The | |
249 | "nand env.oob" command can be used to record this offset. | |
250 | Currently, CONFIG_ENV_OFFSET_REDUND is not supported when | |
251 | using CONFIG_ENV_OFFSET_OOB. | |
252 | ||
253 | config ENV_IS_IN_NVRAM | |
254 | bool "Environment in a non-volatile RAM" | |
255 | depends on !CHAIN_OF_TRUST | |
256 | help | |
257 | Define this if you have some non-volatile memory device | |
258 | (NVRAM, battery buffered SRAM) which you want to use for the | |
259 | environment. | |
260 | ||
261 | - CONFIG_ENV_ADDR: | |
262 | - CONFIG_ENV_SIZE: | |
263 | ||
264 | These two #defines are used to determine the memory area you | |
265 | want to use for environment. It is assumed that this memory | |
266 | can just be read and written to, without any special | |
267 | provision. | |
268 | ||
269 | config ENV_IS_IN_ONENAND | |
270 | bool "Environment is in OneNAND" | |
271 | depends on !CHAIN_OF_TRUST | |
272 | help | |
273 | Define this if you want to put your local device's environment in | |
274 | OneNAND. | |
275 | ||
276 | - CONFIG_ENV_ADDR: | |
277 | - CONFIG_ENV_SIZE: | |
278 | ||
279 | These two #defines are used to determine the device range you | |
280 | want to use for environment. It is assumed that this memory | |
281 | can just be read and written to, without any special | |
282 | provision. | |
283 | ||
284 | config ENV_IS_IN_REMOTE | |
285 | bool "Environment is in remove memory space" | |
286 | depends on !CHAIN_OF_TRUST | |
287 | help | |
288 | Define this if you have a remote memory space which you | |
289 | want to use for the local device's environment. | |
290 | ||
291 | - CONFIG_ENV_ADDR: | |
292 | - CONFIG_ENV_SIZE: | |
293 | ||
294 | These two #defines specify the address and size of the | |
295 | environment area within the remote memory space. The | |
296 | local device can get the environment from remote memory | |
297 | space by SRIO or PCIE links. | |
298 | ||
299 | config ENV_IS_IN_SPI_FLASH | |
300 | bool "Environment is in SPI flash" | |
301 | depends on !CHAIN_OF_TRUST | |
302 | help | |
303 | Define this if you have a SPI Flash memory device which you | |
304 | want to use for the environment. | |
305 | ||
306 | - CONFIG_ENV_OFFSET: | |
307 | - CONFIG_ENV_SIZE: | |
308 | ||
309 | These two #defines specify the offset and size of the | |
310 | environment area within the SPI Flash. CONFIG_ENV_OFFSET must be | |
311 | aligned to an erase sector boundary. | |
312 | ||
313 | - CONFIG_ENV_SECT_SIZE: | |
314 | ||
315 | Define the SPI flash's sector size. | |
316 | ||
317 | - CONFIG_ENV_OFFSET_REDUND (optional): | |
318 | ||
319 | This setting describes a second storage area of CONFIG_ENV_SIZE | |
320 | size used to hold a redundant copy of the environment data, so | |
321 | that there is a valid backup copy in case there is a power failure | |
322 | during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be | |
323 | aligned to an erase sector boundary. | |
324 | ||
325 | - CONFIG_ENV_SPI_BUS (optional): | |
326 | - CONFIG_ENV_SPI_CS (optional): | |
327 | ||
328 | Define the SPI bus and chip select. If not defined they will be 0. | |
329 | ||
330 | - CONFIG_ENV_SPI_MAX_HZ (optional): | |
331 | ||
332 | Define the SPI max work clock. If not defined then use 1MHz. | |
333 | ||
334 | - CONFIG_ENV_SPI_MODE (optional): | |
335 | ||
336 | Define the SPI work mode. If not defined then use SPI_MODE_3. | |
337 | ||
338 | config ENV_IS_IN_UBI | |
339 | bool "Environment in a UBI volume" | |
340 | depends on !CHAIN_OF_TRUST | |
341 | help | |
342 | Define this if you have an UBI volume that you want to use for the | |
343 | environment. This has the benefit of wear-leveling the environment | |
344 | accesses, which is important on NAND. | |
345 | ||
346 | - CONFIG_ENV_UBI_PART: | |
347 | ||
348 | Define this to a string that is the mtd partition containing the UBI. | |
349 | ||
350 | - CONFIG_ENV_UBI_VOLUME: | |
351 | ||
352 | Define this to the name of the volume that you want to store the | |
353 | environment in. | |
354 | ||
355 | - CONFIG_ENV_UBI_VOLUME_REDUND: | |
356 | ||
357 | Define this to the name of another volume to store a second copy of | |
358 | the environment in. This will enable redundant environments in UBI. | |
359 | It is assumed that both volumes are in the same MTD partition. | |
360 | ||
361 | - CONFIG_UBI_SILENCE_MSG | |
362 | - CONFIG_UBIFS_SILENCE_MSG | |
363 | ||
364 | You will probably want to define these to avoid a really noisy system | |
365 | when storing the env in UBI. | |
366 | ||
c1c3fe23 | 367 | endchoice |
0649cd0d SG |
368 | |
369 | config ENV_FAT_INTERFACE | |
370 | string "Name of the block device for the environment" | |
371 | depends on ENV_IS_IN_FAT | |
372 | default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91 | |
373 | help | |
374 | Define this to a string that is the name of the block device. | |
375 | ||
376 | config ENV_FAT_DEVICE_AND_PART | |
377 | string "Device and partition for where to store the environemt in FAT" | |
378 | depends on ENV_IS_IN_FAT | |
379 | default "0:1" if TI_COMMON_CMD_OPTIONS | |
380 | default "0:auto" if ARCH_ZYNQMP | |
381 | default "0" if ARCH_AT91 | |
382 | help | |
383 | Define this to a string to specify the partition of the device. It can | |
384 | be as following: | |
385 | ||
386 | "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1) | |
387 | - "D:P": device D partition P. Error occurs if device D has no | |
388 | partition table. | |
389 | - "D:0": device D. | |
390 | - "D" or "D:": device D partition 1 if device D has partition | |
391 | table, or the whole device D if has no partition | |
392 | table. | |
393 | - "D:auto": first partition in device D with bootable flag set. | |
394 | If none, first valid partition in device D. If no | |
395 | partition table then means device D. | |
396 | ||
397 | config ENV_FAT_FILE | |
398 | string "Name of the FAT file to use for the environemnt" | |
399 | depends on ENV_IS_IN_FAT | |
400 | default "uboot.env" | |
401 | help | |
402 | It's a string of the FAT file name. This file use to store the | |
403 | environment. | |
404 | ||
1087a794 JRO |
405 | config ENV_EXT4_INTERFACE |
406 | string "Name of the block device for the environment" | |
407 | depends on ENV_IS_IN_EXT4 | |
408 | help | |
409 | Define this to a string that is the name of the block device. | |
410 | ||
411 | config ENV_EXT4_DEVICE_AND_PART | |
412 | string "Device and partition for where to store the environemt in EXT4" | |
413 | depends on ENV_IS_IN_EXT4 | |
414 | help | |
415 | Define this to a string to specify the partition of the device. It can | |
416 | be as following: | |
417 | ||
418 | "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1) | |
419 | - "D:P": device D partition P. Error occurs if device D has no | |
420 | partition table. | |
421 | - "D:0": device D. | |
422 | - "D" or "D:": device D partition 1 if device D has partition | |
423 | table, or the whole device D if has no partition | |
424 | table. | |
425 | - "D:auto": first partition in device D with bootable flag set. | |
426 | If none, first valid partition in device D. If no | |
427 | partition table then means device D. | |
428 | ||
429 | config ENV_EXT4_FILE | |
430 | string "Name of the EXT4 file to use for the environemnt" | |
431 | depends on ENV_IS_IN_EXT4 | |
432 | default "uboot.env" | |
433 | help | |
434 | It's a string of the EXT4 file name. This file use to store the | |
435 | environment (explicit path to the file) | |
436 | ||
0649cd0d SG |
437 | if ARCH_SUNXI |
438 | ||
439 | config ENV_OFFSET | |
440 | hex "Environment Offset" | |
441 | depends on !ENV_IS_IN_UBI | |
442 | depends on !ENV_IS_NOWHERE | |
443 | default 0x88000 if ARCH_SUNXI | |
444 | help | |
445 | Offset from the start of the device (or partition) | |
446 | ||
447 | config ENV_SIZE | |
448 | hex "Environment Size" | |
449 | depends on !ENV_IS_NOWHERE | |
450 | default 0x20000 if ARCH_SUNXI | |
451 | help | |
452 | Size of the environment storage area | |
453 | ||
454 | config ENV_UBI_PART | |
455 | string "UBI partition name" | |
456 | depends on ENV_IS_IN_UBI | |
457 | help | |
458 | MTD partition containing the UBI device | |
459 | ||
460 | config ENV_UBI_VOLUME | |
461 | string "UBI volume name" | |
462 | depends on ENV_IS_IN_UBI | |
463 | help | |
464 | Name of the volume that you want to store the environment in. | |
465 | ||
466 | endif | |
467 | ||
81f53b0d KG |
468 | if ARCH_ROCKCHIP |
469 | ||
470 | config ENV_OFFSET | |
471 | hex | |
472 | depends on !ENV_IS_IN_UBI | |
473 | depends on !ENV_IS_NOWHERE | |
474 | default 0x3f8000 | |
475 | help | |
476 | Offset from the start of the device (or partition) | |
477 | ||
478 | config ENV_SIZE | |
479 | hex | |
480 | default 0x8000 | |
481 | help | |
482 | Size of the environment storage area | |
483 | ||
484 | endif | |
485 | ||
0649cd0d | 486 | endmenu |