# Adding configuration options to uboot in mender & yocto combination

**URL:** <https://hub.mender.io/t/adding-configuration-options-to-uboot-in-mender-yocto-combination/4174>\
**Category:** General Discussions\
**Tags:** yocto\
**Created:** [October 11, 2021, 11:32am UTC](https://hub.mender.io/t/adding-configuration-options-to-uboot-in-mender-yocto-combination/4174 "2021-10-11T11:32:57Z")\
**Posts on this page:** 1\
**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:** [October 11, 2021, 11:32am UTC](https://hub.mender.io/t/adding-configuration-options-to-uboot-in-mender-yocto-combination/4174/1 "2021-10-11T11:32:57Z")

</div>

Hi,

I’m currently attempting to add secure boot (hab) support on the coral dev board with yocto.

I’ve got the yocto build with mender running on the coral board setup according to these instructions: [mender hub link](https://hub.mender.io/t/google-coral-dev-board/1711)

However what I’m attempting to do requires setting some parameters into the uboot defconfig. For example:  
CONFIG\_SECURE\_BOOT=y

I’ve attempted to create a patch into the meta-coral layer to modify the defconfig file, but I’ve not yet been succesful. What I’ve tried is to clone google’s corresponding uboot repository ([here](https://coral.googlesource.com/uboot-imx/+/refs/heads/release-day)) And modifying the board specific defconfig file (this should be under configs/mx8mq\_phanbell\_defconfig)

After that I generated a git diff patch and added that next to the 3 patches defined in the meta-coral layer. More specifically meta-coral/meta-coral-bsp/recipes-bsp/uboot/uboot-coral\_2017.03.bb.

I also had to add PATCHTOOL=“git” into that file above the SRC\_URI, otherwise the build would not go through.

However after rebuilding the system image & flashing the bootloader & os into the dev board, it still seems that none of the secure boot related features are available (hab\_status in uboot console etc.)

Should patching the uboot configuration be done in some different way, or am I just doing something wrong here?
