# Yocto: Rockchip separate kernel/rootfs layout **URL:** \ **Category:** General Discussions\ **Tags:** yocto, partitioning, warrior\ **Created:** [October 22, 2020, 10:18pm UTC](https://hub.mender.io/t/yocto-rockchip-separate-kernel-rootfs-layout/2721 "2020-10-22T22:18:24Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![sherlock](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@sherlock](https://hub.mender.io/u/sherlock)\ **Post date:** [October 27, 2020, 10:09pm UTC](https://hub.mender.io/t/yocto-rockchip-separate-kernel-rootfs-layout/2721/11 "2020-10-27T22:09:45Z")
I think I solved the second problem, it looks like the rootfs/uboot partition was not being populated because IMAGE\_BOOT\_FILES was not defined. This topic helped me solve that problem: > [@Yocto Warrior build failing on do\_image\_sdimg for beaglebone](https://hub.mender.io/t/yocto-warrior-build-failing-on-do-image-sdimg-for-beaglebone/1706): > > Hi there, I’m trying to integrate Mender into a Yocto project based on Warrior. The target hardware is a BeagleBone Black. I was able to build the .sdimage following the tutorial on the Beaglebone Black board integration page. However, when I include the layers into my own project, I get the following error when it tries to generate the .sdimg: | DEBUG: Executing shell function do\_image\_sdimg | + mkdir -p /home/mikevoyt/ssd/Aclima/sundstrom-os/build/tmp-sundstrom-glibc/work/beaglebone-sunds… Though, it begs the question as to why the u-boot.bin file needs to be included in the rootfs? I suppose I’m confused by what is required and what is not based on the guide. Do I need to define these? MENDER\_UBOOT\_ENV\_STORAGE\_DEVICE\_OFFSET\_1 MENDER\_UBOOT\_ENV\_STORAGE\_DEVICE\_OFFSET\_2 If so, how does Mender use them? --- _[View the full topic](https://hub.mender.io/t/yocto-rockchip-separate-kernel-rootfs-layout/2721)._