# Google coral uboot environment location

**URL:** <https://hub.mender.io/t/google-coral-uboot-environment-location/2844>\
**Category:** General Discussions\
**Created:** [November 17, 2020, 2:35pm UTC](https://hub.mender.io/t/google-coral-uboot-environment-location/2844 "2020-11-17T14:35:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mender-coral](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mender-coral](https://hub.mender.io/u/mender-coral)\
**Post date:** [November 17, 2020, 2:35pm UTC](https://hub.mender.io/t/google-coral-uboot-environment-location/2844/1 "2020-11-17T14:35:18Z")

</div>

Hi,

I’m attempting to use mender to update a google coral board that uses mendel os. I have managed to use mender-convert to make a bootable image of the mendel system and have configured the mender client to connect to the mender hosted cloud.

However when the system starts and I run:  
journalctl -u mender-client  
I get see an error message:  
ERRO[0000] Failed to read the current active partition: No match between boot and root partitions.: exit status 1

I think the error is with the fw\_printenv/setenv commands not finding the uboot environment as I don’t have the correct parameters of device/offset/env size defined in the fw\_env.config file.

If I have understood correctly those parameters are specific to the board? Are those known for the coral or are they in any way related to the values that might be used with the yocto version for coral?

---

<div class="post-metadata">

**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:** [November 17, 2020, 2:57pm UTC](https://hub.mender.io/t/google-coral-uboot-environment-location/2844/2 "2020-11-17T14:57:28Z")

</div>

> [@mender-coral](#):
>
> If I have understood correctly those parameters are specific to the board?

Yes, typically this is specific to the board but primarily related to what values you have in U-Boot because `fw_setenv/fw_getenv` interacts with the same environment as U-Boot.

But you also need to do a U-Boot integration similar to what is done in Yocto to integrate the Mender logic in the bootcmd.