# Create sdimg for platform efusA9 (NXP IMX.6 based)

**URL:** <https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981>\
**Category:** General Discussions\
**Created:** [September 4, 2019, 7:06am UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981 "2019-09-04T07:06:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ahmed](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@Ahmed](https://hub.mender.io/u/Ahmed)\
**Post date:** [September 4, 2019, 7:06am UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/1 "2019-09-04T07:06:52Z")

</div>

Hi everyone,

I have mostly integrated mender with efusA9 board which is based on NXP IMX.6. After integration I have generated the .mender artifact plus the root file system .ext4 and also the required changes in uboot as well to have mender variables.

My issue is I want to generate an sdimg instead of having only the root file system generated (.ext4).  
Here is the content of my local.conf

 ![conf](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/61307c8ab411e911761db3d6027017be09dfce52.jpeg)

If I only add “mender-image-sd” to INHERIT to local.conf

INHERIT += “mender-image mender-install mender-uboot mender-image-sd”

then I get the following error from the WIC tool:

```
+ wic create /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky- 
linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks --vars /home/aawad/BDSDK- 
QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/ -e fus-image-std -o 
/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image- 
std-fsimx6-20190904062426-sdimg/
| Error: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux- 
gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks:1: too few arguments

```

any idea please, Why would the WIC tool complain about the arguments ? I have not changed any thing in meta-mender. I picked meta-mender (morty)

Thanks  
Awad

---

<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:** [September 4, 2019, 7:11am UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/2 "2019-09-04T07:11:45Z")

</div>

Hi @Ahmed,

Welcome to Mender Hub.

A couple of followup questions,

- Which Yocto version and which branch of meta-mender are you using?
- Can you please share the full log of the `sdimg` failure?

---

<div class="post-metadata">

**Author:** ![Ahmed](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@Ahmed](https://hub.mender.io/u/Ahmed)\
**Post date:** [September 4, 2019, 7:46am UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/3 "2019-09-04T07:46:29Z")

</div>

Hi @Mirza,

Thanks for the speedy reply. The board efusA9 uses yocto branch “imx-4.1-krogoth” to fetch the mainstream yocto meta data plus poky and I fetched meta-mender from morty branch, somehow i get an error with meta-mender from krogoth. Everything builds fine and I can generate .mender and the root file system .ext4, only my issue is with generating the sdimg.

Here is please the full log:

 ![image1](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/29d66aead104516432f3263e36343b9db3743b12.jpeg)  
 ![image2](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/60adb2398db2ccc48f22c821c1187e96bb6ead66.jpeg)

Thanks  
Ahmed Awad

---

<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:** [September 4, 2019, 7:59am UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/4 "2019-09-04T07:59:03Z")

</div>

One more request :), can you please paste logs as text instead of images. Makes it a lot easier to inspect

---

<div class="post-metadata">

**Author:** ![Ahmed](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@Ahmed](https://hub.mender.io/u/Ahmed)\
**Post date:** [September 4, 2019, 8:08am UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/5 "2019-09-04T08:08:07Z")

</div>

Hi @Mirza ,

I wanted to paste it as text but the editor converts the ‘+’ sign into bullets ‘\*’ 🙂

```auto
DEBUG: Executing python function set_image_size
DEBUG: Python function set_image_size finished
DEBUG: Executing shell function do_image_sdimg
suffix=sdimg part_type=msdos
+mkdir -p /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0
+mkdir -p /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/rootfs
++expr 802816 / 1024
+mender_calc_rootfs_size_mb=784
+dd if=/dev/zero of=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/rootfs.ext4 count=0 seek=784 bs=1M
0+0 records in
0+0 records out
0 bytes copied, 1.0363e-05 s, 0.0 kB/s
+mkfs.ext4 -F -i 4096 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/rootfs.ext4 -d /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/rootfs
mke2fs 1.43-WIP (18-May-2015)
Discarding device blocks: 4096/200704 done                            
Creating filesystem with 200704 4k blocks and 200704 inodes
Filesystem UUID: 0d6d4627-a365-4a2a-8cce-c7b561818192
Superblock backups stored on blocks: 
	32768, 98304, 163840

Allocating group tables: 0/7 done                            
Writing inode tables: 0/7 done                            
Creating journal (4096 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: 0/7 done

+ln -sf /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/rootfs.ext4 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/active
+ln -sf /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/rootfs.ext4 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/inactive
+rm -rf /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data
+mkdir -p /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data
+echo 'MENDER_DATA_PART_DIR:: '
MENDER_DATA_PART_DIR:: 
+echo 'DEPLOY_DIR_IMAGE::: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6'
DEPLOY_DIR_IMAGE::: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6
+'[' -f /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/data.tar ']'
+cd /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0
+tar xf /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/data.tar
+mkdir -p /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data/mender
+echo device_type=fsimx6
+echo /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0
/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0
+chmod 0444 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data/mender/device_type
+dd if=/dev/zero of=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data.ext4 count=0 bs=1M seek=128
0+0 records in
0+0 records out
0 bytes copied, 1.9683e-05 s, 0.0 kB/s
+mkfs.ext4 -F /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data.ext4 -d /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data -L data
mke2fs 1.43-WIP (18-May-2015)
Discarding device blocks: 1024/131072 done                            
Creating filesystem with 131072 1k blocks and 32768 inodes
Filesystem UUID: 525991f8-6f32-493e-9682-95345b8c9923
Superblock backups stored on blocks: 
	8193, 24577, 40961, 57345, 73729

Allocating group tables: 0/16 done                            
Writing inode tables: 0/16 done                            
Creating journal (4096 blocks): done
Copying files into the device: done
Writing superblocks and filesystem accounting information: 0/16 done

+install -m 0644 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data.ext4 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/
+install -m 0644 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/uboot.env /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/
+wks=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks
+echo 'wks::: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks'
wks::: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks
+rm -f /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks
+'[' -n '' ']'
+true
+'[' -n 8388608 ']'
++ expr 8388608 / 1024
+boot_env_align_kb=8192
+cat
+cat
+echo '### Contents of wks file ###'
### Contents of wks file ###
+cat /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks
part --source rawcopy --sourceparams="file=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/uboot.env" --ondisk mmcblk0 --align 8192 --no-table
part --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --align 8192 --active --size 16
part --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/active" --ondisk mmcblk0 --label primary --align 8192
part --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/inactive" --ondisk mmcblk0 --label secondary --align 8192
part --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data.ext4" --ondisk mmcblk0 --fstype=ext4 --label data --align 8192
bootloader --ptable msdos
+echo '### End of contents of wks file ###'
### End of contents of wks file ###
+outimgname=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904062426.sdimg
+wicout=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904062426-sdimg
+BUILDDIR=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build
+wic create /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks --vars /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/ -e fus-image-std -o /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904062426-sdimg/
Error: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks:1: too few arguments
Checking basic build environment...
Done.

Creating image(s)...

+bb_exit_handler
+ret=1
+case $ret in
+case $BASH_VERSION in
+echo 'WARNING: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/temp/run.do_image_sdimg.1226:1 exit 1 from '\''BUILDDIR="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build" wic create "$wks" --vars "/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/" -e "fus-image-std" -o "$wicout/" ${WIC_CREATE_EXTRA_ARGS}'\'''
WARNING: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/temp/run.do_image_sdimg.1226:1 exit 1 from 'BUILDDIR="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build" wic create "$wks" --vars "/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/" -e "fus-image-std" -o "$wicout/" ${WIC_CREATE_EXTRA_ARGS}'
+exit 1
ERROR: Function failed: do_image_sdimg (log file is located at /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/temp/log.do_image_sdimg.1226)

```

Edit: @mirzak: Formatting

---

<div class="post-metadata">

**Author:** ![Ahmed](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@Ahmed](https://hub.mender.io/u/Ahmed)\
**Post date:** [September 4, 2019, 1:46pm UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/6 "2019-09-04T13:46:53Z")

</div>

Hi @mirzak

i tried to call only wic command inside the “build” directory, but it shows the same error:

```
$ wic create /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks --vars /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/ -e fus-image-std -o /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904130134-sdimg/
Checking basic build environment...
Done.

Creating image(s)...

Error: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks:1: too few arguments

```

any idea please what should be the correct arguments ?

I checked all the paths supplied to “wic create” and they are all seem ok.

This is also the content of mender-sdimg.wks

```
part --source rawcopy --sourceparams="file=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/uboot.env" --ondisk mmcblk0 --align 4096 --no-table
part --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --align 4096 --active --size 16
part --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/active" --ondisk mmcblk0 --label primary --align 4096
part --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/inactive" --ondisk mmcblk0 --label secondary --align 4096
part --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data.ext4" --ondisk mmcblk0 --fstype=ext4 --label data --align 4096
bootloader --ptable msdos

```

Thanks

---

<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 4, 2019, 2:22pm UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/7 "2019-09-04T14:22:06Z")

</div>

The upstream krogoth branch has not been run with Mender in quite some time. Additionally, the morty branch of meta-mender is not getting updates any more so you may be facing an uphill battle here.

Is there any chance to get a newer version?

---

<div class="post-metadata">

**Author:** ![Ahmed](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@Ahmed](https://hub.mender.io/u/Ahmed)\
**Post date:** [September 4, 2019, 2:46pm UTC](https://hub.mender.io/t/create-sdimg-for-platform-efusa9-nxp-imx-6-based/981/8 "2019-09-04T14:46:25Z")

</div>

Hi Drew,

The yocto sources of the efusA9 board is from krogoth and I fetched meta-mender from morty. This means that WIC tool expects different arguments of the “part” command. I tested the following to make sure:

I modified only some lines in “mender-part-images.bbclass” which writes the arguments to mender-sdimg.wks file.

I commented an “if” block and changed the “part” command so that it matches “mender-sdimg.bbclass” from krogoth

```
 #if ${@bb.utils.contains('DISTRO_FEATURES', 'mender-uboot', 'true', 'false', d)} && [-n "${MENDER_UBOOT_ENV_STORAGE_DEVICE_OFFSET}"]; then
        #boot_env_align_kb=$(expr ${MENDER_UBOOT_ENV_STORAGE_DEVICE_OFFSET} / 1024)
        #cat >> "$wks" <<EOF
#part --source rawcopy --sourceparams="file=${WORKDIR}/uboot.env" --ondisk mmcblk0 --align $boot_env_align_kb --no-table
#EOF
# fi

    cat >> "$wks" <<EOF
part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --align ${MENDER_PARTITION_ALIGNMENT_KB} --active --size ${MENDER_BOOT_PART_SIZE_MB}
part / --source fsimage --sourceparams=file="${WORKDIR}/active" --ondisk mmcblk0 --label primary --align ${MENDER_PARTITION_ALIGNMENT_KB}
part / --source fsimage --sourceparams=file="${WORKDIR}/inactive" --ondisk mmcblk0 --label secondary --align ${MENDER_PARTITION_ALIGNMENT_KB}
part /data --source fsimage --sourceparams=file="${WORKDIR}/data.$FSTYPE" --ondisk mmcblk0 --fstype=$FSTYPE --label data --align ${MENDER_PARTITION_ALIGNMENT_KB}
EOF

```

Now I get a different error:

```
| ### Contents of wks file ###
| + cat /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks
| part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --align 4096 --active --size 16
| part / --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/active" --ondisk mmcblk0 --label primary --align 4096
| part / --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/inactive" --ondisk mmcblk0 --label secondary --align 4096
| part /data --source fsimage --sourceparams=file="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/data." --ondisk mmcblk0 --fstype= --label data --align 4096
| + echo '### End of contents of wks file ###'
| ### End of contents of wks file ###
| + outimgname=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904143057.sdimg
| + wicout=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904143057-sdimg
| + BUILDDIR=/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build
| + wic create /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/mender-sdimg.wks --vars /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/ -e fus-image-std -o /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904143057-sdimg/
| Warning: bootloader config not specified, using defaults
| Error: exec_cmd: install -m 0644 -D /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/u-boot.nb0 /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/deploy/images/fsimx6/fus-image-std-fsimx6-20190904143057-sdimg/build/boot/u-boot.nb0 returned '1' instead of 0
| Checking basic build environment...
| Done.
|
| Creating image(s)...
|
| + bb_exit_handler
| + ret=1
| + case $ret in
| + case $BASH_VERSION in
| + echo 'WARNING: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/temp/run.do_image_sdimg.9870:1 exit 1 from '\''BUILDDIR="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build" wic create "$wks" --vars "/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/" -e "fus-image-std" -o "$wicout/" ${WIC_CREATE_EXTRA_ARGS}'\'''
| WARNING: /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/temp/run.do_image_sdimg.9870:1 exit 1 from 'BUILDDIR="/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build" wic create "$wks" --vars "/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/sysroots/fsimx6/imgdata/" -e "fus-image-std" -o "$wicout/" ${WIC_CREATE_EXTRA_ARGS}'
| + exit 1
| ERROR: Function failed: do_image_sdimg (log file is located at /home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/build/tmp/work/fsimx6-poky-linux-gnueabi/fus-image-std/1.0-r0/temp/log.do_image_sdimg.9870)
ERROR: Task 19 (/home/aawad/BDSDK-QuadCore/BDSDK/trunk/src/efusA9/sources/meta-fus/recipes-config/images/fus-image-std.bb, do_image_sdimg) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5805 tasks of which 5804 didn't need to be rerun and 1 failed.

```

It will be hard for me in the mean time to update the board BSP files to a newer yocto version so that I can use the same meta-mender which corresponds to the same yocto version. Yes you are right it is a battle :), !

Thanks