# Build Linux for wp76 **URL:** \ **Category:** Uncategorized\ **Created:** [January 16, 2018, 7:31pm UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084 "2018-01-16T19:31:48Z")\ **Posts on this page:** 9\ **Page:** 2
**Author:** ![Francis.duhaut](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/francis.duhaut/32/350_2.png) [@Francis.duhaut](https://mangoh.discourse.group/u/Francis.duhaut)\ **Post date:** [February 8, 2018, 4:52pm UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/21 "2018-02-08T16:52:05Z")
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… ---
**Author:** ![yogesh.tyagi](https://avatars.discourse-cdn.com/v4/letter/y/c89c15/32.png) [@yogesh.tyagi](https://mangoh.discourse.group/u/yogesh.tyagi)\ **Post date:** [February 13, 2018, 6:55am UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/22 "2018-02-13T06:55:47Z")
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 ---
**Author:** ![yogesh.tyagi](https://avatars.discourse-cdn.com/v4/letter/y/c89c15/32.png) [@yogesh.tyagi](https://mangoh.discourse.group/u/yogesh.tyagi)\ **Post date:** [February 13, 2018, 10:56am UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/23 "2018-02-13T10:56:22Z")
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 ---
**Author:** ![yogesh.tyagi](https://avatars.discourse-cdn.com/v4/letter/y/c89c15/32.png) [@yogesh.tyagi](https://mangoh.discourse.group/u/yogesh.tyagi)\ **Post date:** [February 13, 2018, 12:57pm UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/24 "2018-02-13T12:57:13Z")
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 ---
**Author:** ![Francis.duhaut](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/francis.duhaut/32/350_2.png) [@Francis.duhaut](https://mangoh.discourse.group/u/Francis.duhaut)\ **Post date:** [February 13, 2018, 7:03pm UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/25 "2018-02-13T19:03:59Z")
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 ---
**Author:** ![yogesh.tyagi](https://avatars.discourse-cdn.com/v4/letter/y/c89c15/32.png) [@yogesh.tyagi](https://mangoh.discourse.group/u/yogesh.tyagi)\ **Post date:** [February 14, 2018, 6:24am UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/26 "2018-02-14T06:24:48Z")
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 ---
**Author:** ![Blake](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@Blake](https://mangoh.discourse.group/u/Blake)\ **Post date:** [January 6, 2019, 7:40am UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/27 "2019-01-06T07:40:45Z")
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’ ---
**Author:** ![Blake](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@Blake](https://mangoh.discourse.group/u/Blake)\ **Post date:** [January 7, 2019, 11:45am UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/28 "2019-01-07T11:45:59Z")
I didn’t solve the problem by using VM Ubuntu but finally made it on my Ubuntu (16.04) PC. ---
**Author:** ![likhi](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@likhi](https://mangoh.discourse.group/u/likhi)\ **Post date:** [January 16, 2020, 5:56am UTC](https://mangoh.discourse.group/t/build-linux-for-wp76/1084/29 "2020-01-16T05:56:26Z")
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, [Previous page](https://mangoh.discourse.group/t/build-linux-for-wp76/1084.md?page=1)