Build Linux for wp76

I think you miss to build “image_bin” before o start…

cd yocto
export LEGATO_BUILD=0
make image_bin

Hi @Francis.duhaut,

I want to enable “USB Serial Converter Support” before starting the build? How can I do that? And How do I make sure that I am using the correct yocto(Legato/MangoH-Green) package/version? Linux Kernel version on my MangoH Green board is 3.18.44 .

Here is the output of modprobe:

lsusb | grep -i ft
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
root@swi-mdm9x28:~# modprobe ftdi_sio vendor=0x403 product=0x6001
modprobe: module ftdi_sio not found in modules.dep

Thanks,
Yogesh

Send me a private message I will send a small tuto to build the yocto.

Hi @Francis.duhaut,

Do I need to set some environment variable for cross compilation before running “make image_bin” because target board is ARM?

While running the “make image_bin” initially I am getting following error:

make image_bin
Makefile:30: “Legato: build disabled since ‘/home/warlord/legato_source/yocto/legato/’ does not exist”
“meta-swi-extras/build.sh” -p poky/ -o meta-openembedded/ -l meta-swi -x “kernel/.git” -j 9 -t 9 -a “LK_REPO=”/home/warlord/legato_source/yocto/lk"" -m swi-mdm9x28 -b build_bin -q
Poky dir: /home/warlord/legato_source/yocto/poky
OE meta: /home/warlord/legato_source/yocto/meta-openembedded
SWI meta dir: /home/warlord/legato_source/yocto/meta-swi
Linux repo dir: /home/warlord/legato_source/yocto/kernel/.git
Number of make threads 9
Number of bitbake tasks 9
Extra options added - LK_REPO=/home/warlord/legato_source/yocto/lk
SWI machine: swi-mdm9x28
Build dir: /home/warlord/legato_source/yocto/build_bin
Enable Qualcomm Proprietary bin
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to use a
different MACHINE (target hardware) or enable parallel build options to take
advantage of multiple cores for example. See the file for more information as
common configuration options are commented.

The Yocto Project has extensive documentation about OE including a reference manual
which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
//http://www.openembedded.org/

You had no conf/bblayers.conf file. The configuration file has been created for
you with some default values. To add additional metadata layers into your
configuration please add entries to this file.

The Yocto Project has extensive documentation about OE including a reference manual
which can be found at:
//http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
//http://www.openembedded.org/

/### Shell environment set up for builds. ###

You can now run 'bitbake ’

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
adt-installer
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86’
Error: bash is not set as default provider for /bin/sh
build is not guaranteed to work, aborting
make: *** [image_bin] Error 1

Thanks,
Yogesh

Hello,

To build Yocto and add FDTI driver

download yocto distro for WP76 and tool chain from sierra website (use the VM linux available on the Mangoh website)

remove old toolchain

sudo rm - R /opt/swi/*

install new toolchain
create a new folder ( ex yocto_wp76 )
cd yocto_cp76

untar the linux distro into a folder
-> tar -xvjf DistroName…

Setup the bitbake environment

cd yocto
make image_bin

… you have time to drink a lot of cofee this take around 3H…

Now you can set the bitbake environnement :

cd poky
source oe-init-build-env
cd …/…/build_bin
bitbake -c listtasks linux-quic
bitbake -c menuconfig linux-quic
Navigate to Device Drivers > USB Support > USB Serial Converter Support and press space to have * for module
Press enter to view the list of serial converters
Find USB FTDI Single Port Serial Driver and press space to have *
Save the config as .config (the default) and exit

Edit kernel/arch/arm/configs/mdm9607_defconfig and add
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_FTDI_SIO=y

Rebuild the yocto image
cd to the toplevel yocto directory
make image_bin

Now you can install build_bin/tmp/deploy/images/swi-mdm9x28/yocto_wp76xx.4k.cwe

cd /yocto/build_bin/tmp/deploy/images/swi-mdm9x28
cfglegato
fwupdate download yocto_wp76xx.4k.cwe 192.168.2.2

1 Like

I use the VM linux available on MangOH web site.

Please use it. Idon’t have the list of the packet to install on linux.

The VM image you are using, is arm or x86?

Thanks,
Yogesh

It’s a Ubuntu 16.04 LTS x86 64 bits

You can download the VM at :

http://mangoh.io/mangoh-red-resources-getting-started

HI @Francis.duhaut,

After extracting toolchain, how did you make sure that this toolchain was used to build linux distro ? By default bitbake builds linux disro for “x86” architecture?

By the way, when I run “make image_bin” in “yocto” folder, I get this error:

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
adt-installer
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86’
Error: bash is not set as default provider for /bin/sh
build is not guaranteed to work, aborting
make: *** [image_bin] Error 1

Thanks,
Yogesh

sorry the commande is :

make image (not image_bin)

Toolchain is not necessary to build yocto (but required to build legato and apps)

I get following error if I run “make image” from yocto folder:

make image
Makefile:30: “Legato: build disabled since ‘/home/warlord/legato_source/yocto/legato/’ does not exist”
“meta-swi-extras/build.sh” -p poky/ -o meta-openembedded/ -l meta-swi -x “kernel/.git” -j 9 -t 9 -a “LK_REPO=”/home/warlord/legato_source/yocto/lk"" -m swi-mdm9x28 -b build_bin -q
Poky dir: /home/warlord/legato_source/yocto/poky
OE meta: /home/warlord/legato_source/yocto/meta-openembedded
SWI meta dir: /home/warlord/legato_source/yocto/meta-swi
Linux repo dir: /home/warlord/legato_source/yocto/kernel/.git
Number of make threads 9
Number of bitbake tasks 9
Extra options added - LK_REPO=/home/warlord/legato_source/yocto/lk
SWI machine: swi-mdm9x28
Build dir: /home/warlord/legato_source/yocto/build_bin
Enable Qualcomm Proprietary bin

/### Shell environment set up for builds. ###

You can now run 'bitbake ’

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
adt-installer
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86’
Error: bash is not set as default provider for /bin/sh
build is not guaranteed to work, aborting
make: *** [image_bin] Error 1

Do you have any idea about this error?

1 Like

Do you start with clean Linux VM ??
Remove the yocto folder and retry.

Start by

cd yocto
make image

I was able to build yocto 2 weeks ago with same procedure…

Hi @Francis.duhaut,

I am able to built yocto linux distribution but can’t figure out which image should I flash to the board?
Following are the image in ~/yocto/build_bin/tmp/deploy/images/swi-mdm9x28 directory:

appsboot_ar758x.cwe
appsboot.mbn
appsboot.mbn.unsigned
appsboot_wp76xx.cwe
appsboot_wp77xx.cwe
boot_hash.2k
boot_hash.4k
boot_mbnhdr
boot-yocto-mdm9x28-20180213061253.2k.img
boot-yocto-mdm9x28-20180213061253.4k.img
boot-yocto-mdm9x28.2k.img
boot-yocto-mdm9x28.2k.unsigned.img
boot-yocto-mdm9x28.4k.img
boot-yocto-mdm9x28.4k.unsigned.img
boot-yocto-mdm9x28.img
build_package.version
kernel.version
lk.version
masterDTB.2k
masterDTB.4k
mdm9x28-image-initramfs-swi-mdm9x28-20180213061253.rootfs.cpio.gz
mdm9x28-image-initramfs-swi-mdm9x28-20180213061253.rootfs.manifest
mdm9x28-image-initramfs-swi-mdm9x28-20180213061253.rootfs.tar.bz2
mdm9x28-image-initramfs-swi-mdm9x28.cpio.gz
mdm9x28-image-initramfs-swi-mdm9x28.manifest
mdm9x28-image-initramfs-swi-mdm9x28.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180209131641.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180209131641.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180209131641.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180209131641.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180209131641.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180212063538.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212063538.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212063538.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180212063538.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180212063538.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180212081928.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212081928.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212081928.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180212081928.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180212081928.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180212094324.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212094324.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212094324.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180212094324.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180212094324.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180212095059.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212095059.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212095059.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180212095059.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180212095059.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.2k.ubifs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.4k.ubifs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.build_package.version
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.2k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.4k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.squashfs.hash
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.squashfs.hash.txt
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.version
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.squashfs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.squashfs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.squashfs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.ubifs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180213061253.ubifs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28.2k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28.4k.default
mdm9x28-image-minimal-swi-mdm9x28.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28.4k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28.build_package.version
mdm9x28-image-minimal-swi-mdm9x28.default
mdm9x28-image-minimal-swi-mdm9x28.manifest
mdm9x28-image-minimal-swi-mdm9x28.rootfs.version
mdm9x28-image-minimal-swi-mdm9x28.squashfs
mdm9x28-image-minimal-swi-mdm9x28.squashfs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28.squashfs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28.ubi
mdm9x28-image-minimal-swi-mdm9x28.ubifs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28.ubifs.4k.ubi
modules–3.18.20+git2a043e38a886e83a891d5e5a8a113d6ac6d0ab9a-r1-swi-mdm9x28-20180213061253.tgz
modules-swi-mdm9x28.tgz
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
rootfs
rootfs.rhash
rootfs.version
vmlinux
yocto_ar758x.4k.cwe
yocto_wp76xx.2k.cwe
yocto_wp76xx.4k.cwe
yocto_wp77xx.2k.cwe
yocto_wp77xx.4k.cwe
zImage
zImage–3.18.20+git2a043e38a886e83a891d5e5a8a113d6ac6d0ab9a-r1-swi-mdm9x28-20180213061253.bin
zImage-initramfs-3.18.20+git2a043e38a886e83a891d5e5a8a113d6ac6d0ab9a-r1-swi-mdm9x28-20180213061253.bin
zImage-initramfs-swi-mdm9x28.bin
zImage-swi-mdm9x28.bin
warlord@ubuntu:~/legato_source/yocto/build_bin/tmp/deploy/images/swi-mdm9x28$ pwd
/home/warlord/legato_source/yocto/build_bin/tmp/deploy/images/swi-mdm9x28

Any help would be highly appreciated.

Thanks,
Yogesh

I can see there are multiple files created in ~/build_bin/tmp/deploy/images/swi-mdm9x28 directory. I used yocto_wp76xx.4k.cwe to create firmware file using swicwe utility.

I copied the combined image to target board and ran fwupdate command from there.
This command never returns with following logs on the console:

"fwupdate install combined-firmware.spk 192.168.2.2
Connecting to service …
Install the firmware, the system will reboot …

So I tried installing firmware with swiflash command. Below is the command output:

swiflash -m “WP76XX” -i combined-firmware.spk

Detecting USB of the target
DONE
Communicating with the target
DONE
Switching to firmware download mode
…DONE
Downloading the firmware
…DONE
Rebooting the module
…DONE
Firmware Download SUCCESS

After this process, I am not able to ping the board though board is showing ecm0 interface:

bridge0 Link encap:Ethernet HWaddr 52:D9:D5:12:CB:CC
inet addr:192.168.225.1 Bcast:192.168.225.255 Mask:255.255.255.0
inet6 addr: fe80::50d9:d5ff:fe0f:c8c9/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:76 (76.0 B)

ecm0 Link encap:Ethernet HWaddr 7E:BF:C3:1B:07:93
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::7cbf:c3ff:fe1b:793/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:911 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:91037 (88.9 KiB) TX bytes:14832 (14.4 KiB)

After firmware update I can’t locate ftdi_sio.ko inside the target which means either the image I have flashed, doesn’t contain ftdi_sio module or I am somewhere missing some steps in flashing the firmware.

How can I make sure that the "combined-firmware.spk " image I created with yocto_wp76xx.4k.cwe file using swicwe utility with below command,

swicwe -o combined-firmware.spk -c yocto_wp76xx.4k.cwe

contains “ftdi_sio.ko” module?

ftdi_sio text only matches with following images:

grep -ir ftdi_sio *

Binary file mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.2k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.4k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.2k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.2k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.4k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.4k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.ubifs.2k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.ubifs.4k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.2k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.2k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.4k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.4k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.ubifs.2k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.ubifs.4k.ubi matches

Thanks in advance.

Thanks,
Yogesh

Hi @dfrey,

Do I need to create spk(combined) file from yocto_wp76xx.4k.cwe or I can directly flash yocto_wp76xx.4k.cwe using swiflash?

Thanks,
Yogesh

Hello

Just flash the Yocto 4K file (Linux with file system).

cfglegato

fwupdate download yocto4kfile 192.168.2.2

Sorry I travel this week.
Regards
Francis

Hi @dfrey

I followed all the steps you mentioned above to enable ftdi_sio/Serial driver in linux kernel but still this driver hasn’t build into the yocto image (yocto_wp76xx.4k.cwe) .

I grepped ftdi_sio in the image directory after build and it shows only following matches:

grep ftdi_sio *
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.2k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180212144526.rootfs.4k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.2k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.2k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.4k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.rootfs.4k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.ubifs.2k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213061253.ubifs.4k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213134948.rootfs.2k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213134948.rootfs.2k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213134948.rootfs.4k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213134948.rootfs.4k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213134948.ubifs.2k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28-20180213134948.ubifs.4k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.2k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.2k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.4k.ubifs matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.4k.yaffs2 matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.ubifs.2k.ubi matches
Binary file mdm9x28-image-minimal-swi-mdm9x28.ubifs.4k.ubi matches

I also flashed yocto_wp76xx.4k.cwe image to the target but it’s not creating /dev/ttyUSBx device on connecting usb to serial converter cable.

Am I missing something? Any help would be highly appreciated. Thanks in advance.

Thanks,
Yogesh

I am hitting the following errors while doing “make image”.
Is there anyone having this problem?


ERROR: glibc-2.24-r0 do_package: debugedit failed with exit code 1 (cmd was ‘/home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/build_bin/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit’ -i -l ‘/home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/build_bin/tmp/work/armv7a-neon-poky-linux-gnueabi/glibc/2.24-r0/debugsources.list’ ‘/home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/build_bin/tmp/work/armv7a-neon-poky-linux-gnueabi/glibc/2.24-r0/package/sbin/sln’):
/home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/build_bin/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit: /home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/build_bin/tmp/sysroots-uninative/x86_64-linux/lib/libc.so.6: version `GLIBC_2.27’ not found (required by /home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/build_bin/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/…/…/libpopt.so.0)
ERROR: glibc-2.24-r0 do_package: Function failed: split_and_strip_files
ERROR: Logfile of failure stored in: /home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/build_bin/tmp/work/armv7a-neon-poky-linux-gnueabi/glibc/2.24-r0/temp/log.do_package.20789
ERROR: Task (/home/mangoh/Downloads/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.18.06.00/yocto/poky/meta/recipes-core/glibc/glibc_2.24.bb:do_package) failed with exit code ‘1’

I didn’t solve the problem by using VM Ubuntu but finally made it on my Ubuntu (16.04) PC.

Hi,

I am using the Virtual machine, but getting same error, which was mention in above, did u have any solution to solve this problem in VM?

Regards,