# Quick query on "Rocko - Mender 1.6" CONFIG\_ENV\_SIZE variable **URL:** \ **Category:** General Discussions\ **Created:** [March 19, 2019, 1:04pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389 "2019-03-19T13:04:39Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![ajithpv](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ajithpv/32/728_2.png) [@ajithpv](https://hub.mender.io/u/ajithpv)\ **Post date:** [March 19, 2019, 1:04pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/1 "2019-03-19T13:04:39Z")
Hi, AFAIK, The CONFIG\_ENV\_SIZE value depends on the BOOTENV\_SIZE. I have configured the BOOTENV\_SIZE as below in the machine config file: > MENDER\_UBOOT\_ENV\_STORAGE\_DEVICE\_OFFSET\_1 = “0x400000” > MENDER\_UBOOT\_ENV\_STORAGE\_DEVICE\_OFFSET\_2 = “0x800000” > BOOTENV\_SIZE = “0x1000” But, during the Yocto build, I’m getting the below error: > error ‘CONFIG\_ENV\_SIZE’ define must be equal to bitbake variable ‘BOOTENV\_SIZE’ set in U-Boot build recipe. When I checked the “_config\_mender\_defines.h_”, the **BOOTENV\_SIZE = “0x1000”** but, the u-boot header file shows the “ **#define CONFIG\_ENV\_SIZE 0x20000** ” Whatever value I put for the _BOOTENV\_SIZE_, the _#define CONFIG\_ENV\_SIZE_ remains _0x20000_ only. This is happening only with Mender 1.6 and Rocko. I have a similar set-up with Mender 1.7 and Sumo where this is working as expected. Any idea why this is happening? I know the default value in mender source for _BOOTENV\_SIZE_ is _0x20000_ but, not sure how to change it to required one (to change the _CONFIG\_ENV\_SIZE_) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [March 19, 2019, 1:06pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/2 "2019-03-19T13:06:41Z")
Which package fails? u-boot or u-boot-fw-utils? ---
**Author:** ![ajithpv](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ajithpv/32/728_2.png) [@ajithpv](https://hub.mender.io/u/ajithpv)\ **Post date:** [March 19, 2019, 1:21pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/3 "2019-03-19T13:21:12Z")
I’m not sure but, getting both are failed as shown below: > Summary: 2 tasks failed: > /sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx\_2017.03.bb:do\_compile > /sources/meta-mender/meta-mender-core/recipes-bsp/u-boot/u-boot-fw-utils-mender-auto-provided\_1.0.bb:do\_compile Please let me know more detailed log is required or not. ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [March 19, 2019, 1:22pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/4 "2019-03-19T13:22:35Z")
Can you run: ``` bitbake u-boot -e | grep ^BOOTENV_SIZE ``` and ``` bitbake u-boot-fw-utils -e | grep ^BOOTENV_SIZE ``` ---
**Author:** ![ajithpv](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ajithpv/32/728_2.png) [@ajithpv](https://hub.mender.io/u/ajithpv)\ **Post date:** [March 19, 2019, 1:25pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/5 "2019-03-19T13:25:54Z")
Please see the output below: > $ bitbake u-boot -e | grep ^BOOTENV\_SIZE > BOOTENV\_SIZE=“0x1000” > $ bitbake u-boot-fw-utils -e | grep ^BOOTENV\_SIZE > BOOTENV\_SIZE=“0x1000” ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [March 19, 2019, 1:26pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/6 "2019-03-19T13:26:56Z")
Then the problem is probably in your U-boot source as it might not defined to `0x1000` ---
**Author:** ![ajithpv](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ajithpv/32/728_2.png) [@ajithpv](https://hub.mender.io/u/ajithpv)\ **Post date:** [March 19, 2019, 1:29pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/7 "2019-03-19T13:29:36Z")
I will check it. But, _CONFIG\_ENV\_SIZE_ value usually modified by the Mender with BOOTENV\_SIZE right? ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [March 19, 2019, 1:31pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/8 "2019-03-19T13:31:44Z")
> I will check it. But, _CONFIG\_ENV\_SIZE_ value usually modified by the Mender with BOOTENV\_SIZE right? Nope, meta-mender does not modify the `CONFIG_ENV_SIZE`. They just have be equally defined because meta-mender uses this value to perform sanity checks and other calculations. ---
**Author:** ![ajithpv](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ajithpv/32/728_2.png) [@ajithpv](https://hub.mender.io/u/ajithpv)\ **Post date:** [March 19, 2019, 1:33pm UTC](https://hub.mender.io/t/quick-query-on-rocko-mender-1-6-config-env-size-variable/389/9 "2019-03-19T13:33:52Z")
I see…then I will check in the U-boot source. Thank you very much for the help…I will keep you update the progress 🙂