# Issue with Mender setting u-boot env on dunfell

**URL:** <https://hub.mender.io/t/issue-with-mender-setting-u-boot-env-on-dunfell/2225>\
**Category:** General Discussions\
**Tags:** yocto, nxp, dunfell\
**Created:** [July 23, 2020, 1:13am UTC](https://hub.mender.io/t/issue-with-mender-setting-u-boot-env-on-dunfell/2225 "2020-07-23T01:13:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevlan](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kevlan/32/695_2.png) [@kevlan](https://hub.mender.io/u/kevlan)\
**Post date:** [July 23, 2020, 1:13am UTC](https://hub.mender.io/t/issue-with-mender-setting-u-boot-env-on-dunfell/2225/1 "2020-07-23T01:13:46Z")

</div>

I am attempting to update our yocto to the dunfell release and I am seeing an issue during updates where mender is not updating the mender\_boot\_part during the update.

I have run through the u-boot integration checklist and using fw\_setenv I am able to change variables as expected and they persist across reboots. When I run a mender update I stop the boot during the reboot and check the environment in uboot and it is not updated correctly. mender\_boot\_part and upgrade\_available are still set to the old partition and no upgrade in progress.

If I manually change the variables in u-boot during the reboot, the system boots into the updated partition just fine.

What would be causing the manual test of fw\_setenv to work but when mender runs it, it fails?

Is there any way to debug what is going on here?

Thanks,

Kevin

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [July 23, 2020, 7:36am UTC](https://hub.mender.io/t/issue-with-mender-setting-u-boot-env-on-dunfell/2225/2 "2020-07-23T07:36:04Z")

</div>

I saw you posted in a different thread also, but probably you need to upgrade to Mender client 2.2.1 or later, which was released just a few days ago. Older clients are not compatible with libubootenv, which is used in dunfell.

---

<div class="post-metadata">

**Author:** ![kevlan](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kevlan/32/695_2.png) [@kevlan](https://hub.mender.io/u/kevlan)\
**Post date:** [July 23, 2020, 4:35pm UTC](https://hub.mender.io/t/issue-with-mender-setting-u-boot-env-on-dunfell/2225/3 "2020-07-23T16:35:07Z")

</div>

Thanks,

We had pulled the dunfell-next branch a few days ago and did not notice the update that had been made. We will retest this today with the new version.