# Yocto Thud release and Mender **URL:** \ **Category:** Announcements\ **Created:** [December 9, 2018, 7:43pm UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144 "2018-12-09T19:43:47Z")\ **Posts on this page:** 8\ **Page:** 1
**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:** [December 9, 2018, 7:43pm UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/1 "2018-12-09T19:43:47Z")
Hi, A few weeks back the Yocto project released Thud (2.6). The update to [meta-mender](https://github.com/mendersoftware/meta-mender) normally takes another few weeks to create and this is now the case. With above said it is time to start updating the integrations that we have in [meta-mender-community](https://github.com/mendersoftware/meta-mender-community) and I also the Mender Hub posts. A crucial part of Mender Hub is that the reference implementations and the posts that we have here are continuously updates which ensures a high quality platform. I have already created the [thud branch in meta-mender-community](https://github.com/mendersoftware/meta-mender-community/tree/thud) and updated the [Raspberry Pi 3](https://hub.mender.io/t/raspberry-pi-3-model-b-b/57) and [Asus Tinker Board](https://hub.mender.io/t/asus-tinker-board/45) integrations and posts and will continue working on the boards that I have added. **NOTE** that [meta-mender/thud](https://github.com/mendersoftware/meta-mender) by default uses GRUB integration on ARM boards instead of the previous U-boot integration. This still relies on U-boot being present but utilizes the `bootefi` command which can load and execute GRUB2 as an EFI application, where all the Mender parts are integrated. The `bootefi` command is something that is part of `config_distro_boot_cmd` meaning that if your board is utilizing this there is a high likelihood that you do not need any patches to U-boot to integrate Mender. If there is already an U-boot integration in place or if the GRUB integration does not work for some reason one can disable this new default by adding the following to `local.conf`, as I have done for Raspberry Pi boards because they have a somewhat “special” boot procedure. > In which case it will fall-back to the “standard” U-boot integration which we have been using up until `thud`. Happy updating 😃 @eystein @texierp @jorisoffouga @MarekBelisko @dwalkes ---
**Author:** ![texierp](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/texierp/32/45_2.png) [@texierp](https://hub.mender.io/u/texierp)\ **Post date:** [December 9, 2018, 8:09pm UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/2 "2018-12-09T20:09:48Z")
Thanks for the update @mirzak From my side, already planned 😉 I’m just waiting for the ‘thud’ branch for both meta-atmel and meta-freescale 😀 ---
**Author:** ![Ks89](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ks89/32/86_2.png) [@Ks89](https://hub.mender.io/u/Ks89)\ **Post date:** [December 12, 2018, 5:35pm UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/3 "2018-12-12T17:35:12Z")
Thank u. I already created a build with master branch of meta-freescale and it worked. Next week I’ll try to boot the system and follow integration checklist. However I removed path 007 (if I remember the right number) to be able to build ---
**Author:** ![Ks89](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ks89/32/86_2.png) [@Ks89](https://hub.mender.io/u/Ks89)\ **Post date:** [December 13, 2018, 12:14am UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/4 "2018-12-13T00:14:19Z")
mmm, no I made a mistake, because I was building without u-boot support, since It’s changed in version 1.7. Enabling MENDER\_FEATURES\_ENABLE\_append = " mender-uboot mender-image-sd" MENDER\_FEATURES\_DISABLE\_append = " mender-grub mender-image-uefi" I got this error: Applying patch 0003-Integration-of-Mender-boot-code-into-U-Boot.patch patching file include/env\_default.h Hunk #1 succeeded at 10 with fuzz 2 (offset 1 line). Hunk #2 FAILED at 23. 1 out of 2 hunks FAILED – rejects in file include/env\_default.h patching file scripts/Makefile.autoconf Hunk #1 succeeded at 111 (offset 2 lines). Patch 0003-Integration-of-Mender-boot-code-into-U-Boot.patch does not apply (enforce with -f) ERROR: u-boot-imx-2017.03-r0 do\_patch: Function failed: patch\_do\_patch I’m using u-boot-imx from meta-freescale master branch (because thud branch is still not available). ---
**Author:** ![Ks89](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ks89/32/86_2.png) [@Ks89](https://hub.mender.io/u/Ks89)\ **Post date:** [December 14, 2018, 10:23pm UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/5 "2018-12-14T22:23:03Z")
meta-freescale’s thud branch is finally available [https://github.com/Freescale/meta-freescale/tree/thud](https://github.com/Freescale/meta-freescale/tree/thud) ---
**Author:** ![dwalkes](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dwalkes/32/41_2.png) [@dwalkes](https://hub.mender.io/u/dwalkes)\ **Post date:** [December 17, 2018, 1:25am UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/6 "2018-12-17T01:25:19Z")
Thanks, will add this to my todo list over the holiday break 🙂 ---
**Author:** ![dwalkes](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dwalkes/32/41_2.png) [@dwalkes](https://hub.mender.io/u/dwalkes)\ **Post date:** [January 2, 2019, 2:05am UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/7 "2019-01-02T02:05:39Z")
@mirzak, the Thud release is working for me with the PR at [https://github.com/mendersoftware/meta-mender-community/pull/41](https://github.com/mendersoftware/meta-mender-community/pull/41) ---
**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:** [January 2, 2019, 10:11am UTC](https://hub.mender.io/t/yocto-thud-release-and-mender/144/8 "2019-01-02T10:11:21Z")
A big thanks to everyone who have updated the integrations and posts. This ensures a platform with high quality working with the latest Yocto releases.