# Sdimg creation error - Yocto Zeus i.MX 8M mini EVK

**URL:** https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412
**Category:** General Discussions
**Tags:** yocto, nxp, zeus, imx8mm
**Created:** [September 9, 2020, 1:17pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412 "2020-09-09T13:17:03Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![danie](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/danie/32/620_2.png) [@danie](https://hub.mender.io/u/danie)
#### Post date: [September 9, 2020, 1:17pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/1 "2020-09-09T13:17:03Z")

</div>

I got this error: `ERROR: Actual rootfs size (29280 kB) is larger than allowed size 16384 kB` while building mender image. The contents of `wks` file is given below.

I’ve tried changing `MENDER_STORAGE_TOTAL_SIZE_MB` to various large values, still I’m getting the same errors(**ERROR: Actual rootfs size (29280 kB) is larger than allowed size 16384 kB**).

```auto
### Contents of wks file ###
cat /home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/mender-sdimg.wks
# embed bootloader
part --source rawcopy --sourceparams="file=/home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/u-boot-imx8mmevk.bin-sd" --ondisk "mmcblk1" --align 33 --no-table
part --source rawcopy --sourceparams="file=/home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/uboot.env" --ondisk "mmcblk1" --align 8192 --no-table
part --source rootfs --rootfs-dir /home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/bootfs.image_sdimg --ondisk "mmcblk1" --fstype=vfat --label boot --align 8192 --fixed-size 16 --active
part --source rawcopy --sourceparams="file=/home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/deploy-core-image-base-image-complete/core-image-base-imx8mmevk.ext4" --ondisk "mmcblk1" --align 8192 --fixed-size 3031040k
part --source rawcopy --sourceparams="file=/home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/deploy-core-image-base-image-complete/core-image-base-imx8mmevk.ext4" --ondisk "mmcblk1" --align 8192 --fixed-size 3031040k
part --source rawcopy --sourceparams="file=/home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/deploy-core-image-base-image-complete/core-image-base-imx8mmevk.dataimg" --ondisk "mmcblk1" --align 8192 --fixed-size 32 --mkfs-extraopts=''

bootloader --ptable msdos
### End of contents of wks file ###

```

Can you help me getting it right?

How can I control the wks file to only include `u-boot` image in the `FAT` partition?

---

<div class="post-metadata">

### Author: ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [September 9, 2020, 2:13pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/2 "2020-09-09T14:13:51Z")

</div>

Are you certain that your changes of the MENDER\_STORAGE\_TOTAL\_SIZE\_MB are in effect? I’ve had issues occasionally where I was setting that variable in local.conf but it was also set elsewhere and my changes were ignored.

If you run “bitbake -e core-image-base” and save the output, it will show you the value of that variable and exactly how it was set, by which layers, conf files, etc

Drew

---

<div class="post-metadata">

### Author: ![danie](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/danie/32/620_2.png) [@danie](https://hub.mender.io/u/danie)
#### Post date: [September 9, 2020, 2:50pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/3 "2020-09-09T14:50:11Z")

</div>

After further analysis, I found that the problem is caused by this line: `part --source rootfs --rootfs-dir /home/ux/imx8/yocto/zeusl/core-base-build/tmp/work/imx8mmevk-poky-linux/core-image-base/1.0-r0/bootfs.image_sdimg --ondisk "mmcblk1" --fstype=vfat --label boot --align 8192 --fixed-size 16 --active`

Here, it’s trying to copy whole directory to the 16MB FAT partition, where in the u-boot file is only required. Do you have any comments on this one?

---

<div class="post-metadata">

### Author: ![danie](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/danie/32/620_2.png) [@danie](https://hub.mender.io/u/danie)
#### Post date: [September 9, 2020, 2:53pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/4 "2020-09-09T14:53:07Z")

</div>

> [@drewmoseley](#):
>
> Are you certain that your changes of the MENDER\_STORAGE\_TOTAL\_SIZE\_MB are in effect?

Yes, if you look at the contents of `wks` file (on line 4 & 5) there are two partition of roughly 3GB as two root file systems. This indicates that the `MENDER_STORAGE_TOTAL_SIZE_MB = "6000"` took effect.

---

<div class="post-metadata">

### Author: ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [September 9, 2020, 3:25pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/5 "2020-09-09T15:25:58Z")

</div>

That directory is populated by the contents of the IMAGE\_BOOT\_FILES variable so you’ll need to trim that down.

Drew

---

<div class="post-metadata">

### Author: ![dvescovi](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dvescovi/32/287_2.png) [@dvescovi](https://hub.mender.io/u/dvescovi)
#### Post date: [September 28, 2020, 5:48pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/6 "2020-09-28T17:48:44Z")

</div>

danie  
I have been struggling porting the iMX8evk to zeus also.  
Seems mostly issues with boot loader.  
How far did you get?

---

<div class="post-metadata">

### Author: ![danie](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/danie/32/620_2.png) [@danie](https://hub.mender.io/u/danie)
#### Post date: [September 29, 2020, 6:04am UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/7 "2020-09-29T06:04:24Z")

</div>

Yes, we too faced issues in mender U-boot integration in Zeus. So, we’ve ported back to sumo branch.

---

<div class="post-metadata">

### Author: ![dvescovi](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dvescovi/32/287_2.png) [@dvescovi](https://hub.mender.io/u/dvescovi)
#### Post date: [September 29, 2020, 12:03pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/8 "2020-09-29T12:03:09Z")

</div>

I also have the sumo branch working just fine. NXP has released the zeus BSP for iMX8 a few months back but mender support seems to be lagging. I see a few people working on dunfell but nothing on iMX8 yet.

---

<div class="post-metadata">

### Author: ![danie](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/danie/32/620_2.png) [@danie](https://hub.mender.io/u/danie)
#### Post date: [September 29, 2020, 1:05pm UTC](https://hub.mender.io/t/sdimg-creation-error-yocto-zeus-i-mx-8m-mini-evk/2412/9 "2020-09-29T13:05:02Z")

</div>

Yes, Mender has general integration support for Zeus (I hope) and it’s up-to users for porting into specific board as it’s nearly impossible for mender to cover all the boards.  
I’m working on that (Zeus branch) and update here if something turns fruitful. Thank you.
