diff options
| author | zhanghaicheng <zhanghch05@inspur.com> | 2021-12-23 04:44:26 +0300 |
|---|---|---|
| committer | Patrick Williams <patrick@stwcx.xyz> | 2021-12-30 18:45:46 +0300 |
| commit | 851a10e54604704eabed9f565f29e98627521fc6 (patch) | |
| tree | c11544ceb16da867dd8255985ad79669b76cb5d1 /meta-aspeed/recipes-bsp/u-boot/files/u-boot_flash_64M.cfg | |
| parent | 0ee50bdd6b0ba3cd7da17fe0f6ccce2312521d0f (diff) | |
| download | openbmc-851a10e54604704eabed9f565f29e98627521fc6.tar.xz | |
Fix the config error of u-boot-env
When using 64M flash, the config of u-boot CONFIG_ENV_SIZE and
CONFIG_ENV_OFFSET is wrong. The config file fw_env.config is wrong, too.
Modify them according to the 64M flash dts file.
Before correcting these errors, when we used setenv to set environment
variables in u-boot, we could not use fw_printenv to get them. The
reverse is also the same. Because they set different offset and size.
Tested:
1. Use commands in u-boot:
setenv test value
saveenv
After BMC starts, use fw_printenv can get "test=value"
2. Use the command to change the value of "test"
fw_setenv test v
We can get "test=v" in u-boot by printenv.
Signed-off-by: zhanghaicheng <zhanghch05@inspur.com>
Change-Id: I9eccf6abe743253b6f8c344a8b8648e68ab52019
Diffstat (limited to 'meta-aspeed/recipes-bsp/u-boot/files/u-boot_flash_64M.cfg')
| -rw-r--r-- | meta-aspeed/recipes-bsp/u-boot/files/u-boot_flash_64M.cfg | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/meta-aspeed/recipes-bsp/u-boot/files/u-boot_flash_64M.cfg b/meta-aspeed/recipes-bsp/u-boot/files/u-boot_flash_64M.cfg new file mode 100644 index 000000000..b0f3f2891 --- /dev/null +++ b/meta-aspeed/recipes-bsp/u-boot/files/u-boot_flash_64M.cfg @@ -0,0 +1,2 @@ +CONFIG_ENV_SIZE=0x20000 +CONFIG_ENV_OFFSET=0xE0000 |