diff options
| author | Stephen Warren <swarren@nvidia.com> | 2012-07-30 10:55:45 +0000 |
|---|---|---|
| committer | Tom Warren <twarren@nvidia.com> | 2012-09-07 13:54:31 -0700 |
| commit | 573668a24e3e4ed5667332ea656e35021767ea6d (patch) | |
| tree | 8a21d01b0b9b1cb59cb215d246ebb3e83b44c410 /include/configs/paz00.h | |
| parent | 300feff3241def7a972a01915b75b7a1e1ec2d62 (diff) | |
| download | u-boot-imx-573668a24e3e4ed5667332ea656e35021767ea6d.zip u-boot-imx-573668a24e3e4ed5667332ea656e35021767ea6d.tar.gz u-boot-imx-573668a24e3e4ed5667332ea656e35021767ea6d.tar.bz2 | |
tegra: put eMMC environment into the boot sectors
When I set up Tegra's config files to put the environment into eMMC, I
assumed that CONFIG_ENV_OFFSET was a linearized address relative to the
start of the eMMC device, and spanning HW partitions boot0, boot1,
general* and the user area in order. However, it turns out that the
offset is actually relative to the beginning of the user area. Hence,
the environment block ended up in a different location to expected and
documented.
Set CONFIG_SYS_MMC_ENV_PART=2 (boot1) to solve this, and adjust
CONFIG_ENV_OFFSET to be relative to the start of boot1, not the entire
eMMC.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'include/configs/paz00.h')
| -rw-r--r-- | include/configs/paz00.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/include/configs/paz00.h b/include/configs/paz00.h index 0eb9f3b..99b8753 100644 --- a/include/configs/paz00.h +++ b/include/configs/paz00.h @@ -51,8 +51,9 @@ /* Environment in eMMC, at the end of 2nd "boot sector" */ #define CONFIG_ENV_IS_IN_MMC -#define CONFIG_ENV_OFFSET ((2 * 1024 * 1024) - CONFIG_ENV_SIZE) +#define CONFIG_ENV_OFFSET ((1024 * 1024) - CONFIG_ENV_SIZE) #define CONFIG_SYS_MMC_ENV_DEV 0 +#define CONFIG_SYS_MMC_ENV_PART 2 /* USB Host support */ #define CONFIG_USB_EHCI |