u-boot

History

Waldemar Brodkorb de19eddf6c add example for file on VFAT filesystem usage For example on a raspberry pi the u-boot environment can be saved in a file on the first VFAT partition. This example illustrates how to use it with fw_printenv/fw_setenv. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>		2015-02-17 06:27:44 -05:00
..
.gitignore	tools/env: cross-compile fw_printenv without setting HOSTCC	2014-02-19 11:10:04 -05:00
aes.c	tools: env: Add aes.c placeholder	2014-05-12 15:20:05 -04:00
crc32.c	tools: convert makefiles to kbuild style	2014-02-19 11:07:49 -05:00
ctype.c	tools: convert makefiles to kbuild style	2014-02-19 11:07:49 -05:00
env_attr.c	tools: convert makefiles to kbuild style	2014-02-19 11:07:49 -05:00
env_flags.c	tools: convert makefiles to kbuild style	2014-02-19 11:07:49 -05:00
fw_env_main.c	env: Implement support for AES encryption into fw_* tools	2014-03-21 16:44:08 -04:00
fw_env.c	tools/env: Fix environment size and CRC on 64-bit hosts	2014-11-07 16:27:07 -05:00
fw_env.config	add example for file on VFAT filesystem usage	2015-02-17 06:27:44 -05:00
fw_env.h	Coding Style cleanup: remove trailing white space	2013-10-14 16:06:53 -04:00
linux_string.c	tools: convert makefiles to kbuild style	2014-02-19 11:07:49 -05:00
Makefile	tools/env: change stripping strategy to allow no-stripping	2014-09-24 18:30:27 -04:00
README	tools/env: cross-compile fw_printenv without setting HOSTCC	2014-02-19 11:10:04 -05:00

README

This is a demo implementation of a Linux command line tool to access
the U-Boot's environment variables.

In order to cross-compile fw_printenv, run
    make CROSS_COMPILE=<your cross-compiler prefix> env
in the root directory of the U-Boot distribution. For example,
    make CROSS_COMPILE=arm-linux- env

For the run-time utility configuration uncomment the line
#define CONFIG_FILE  "/etc/fw_env.config"
in fw_env.h.

For building against older versions of the MTD headers (meaning before
v2.6.8-rc1) it is required to pass the argument "MTD_VERSION=old" to
make.

See comments in the fw_env.config file for definitions for the
particular board.

Configuration can also be done via #defines in the fw_env.h file. The
following lines are relevant:

#define HAVE_REDUND	/* For systems with 2 env sectors */
#define DEVICE1_NAME	"/dev/mtd1"
#define DEVICE2_NAME	"/dev/mtd2"
#define DEVICE1_OFFSET    0x0000
#define ENV1_SIZE         0x4000
#define DEVICE1_ESIZE     0x4000
#define DEVICE1_ENVSECTORS     2
#define DEVICE2_OFFSET    0x0000
#define ENV2_SIZE         0x4000
#define DEVICE2_ESIZE     0x4000
#define DEVICE2_ENVSECTORS     2

Un-define HAVE_REDUND, if you want to use the utilities on a system
that does not have support for redundant environment enabled.
If HAVE_REDUND is undefined, DEVICE2_NAME is ignored,
as is ENV2_SIZE and DEVICE2_ESIZE.

The DEVICEx_NAME constants define which MTD character devices are to
be used to access the environment.

The DEVICEx_OFFSET constants define the environment offset within the
MTD character device.

ENVx_SIZE defines the size in bytes taken by the environment, which
may be less then flash sector size, if the environment takes less
then 1 sector.

DEVICEx_ESIZE defines the size of the first sector in the flash
partition where the environment resides.

DEVICEx_ENVSECTORS defines the number of sectors that may be used for
this environment instance. On NAND this is used to limit the range
within which bad blocks are skipped, on NOR it is not used.

To prevent losing changes to the environment and to prevent confusing the MTD
drivers, a lock file at /var/lock/fw_printenv.lock is used to serialize access
to the environment.