Yocto source build for wp7608

stirulaka · September 1, 2018, 7:47pm

Hi Olivier,

I had tried your suggestion. Looks like there is a progress in the build. But still with no luck as build fails at the do_image_swashfs

Please find the error log attached.
log.do_image_4k_yaffs2.87672.txt (1013 Bytes)
log.do_image_2k_yaffs2.87676.txt (998 Bytes)

Thanks,
Siva

stirulaka · September 3, 2018, 5:28pm

Hi Olivier,

This is a base package that was downloaded from the sierra-wireless website and I expect it has to work straight away with no modifications. Please do let us know if there is any build issues with the released package.

We were blocked on this topic since 3 weeks with no progress.
Please let us know can we expect the support from sierra-wireless to fix this build issue ?

Thanks,
Siva

stirulaka · September 4, 2018, 8:34am

Hi All,

From the log, it is evident that the build is not able to find the mkyaffs2image.
seems like the build scripts don’t know where to find mkyaffs2image.
Will work on this to fix this issue

Thanks,
Siva

opasco · September 5, 2018, 12:24am

Siva,

Sorry for the delayed response (yesterday was a day off in the US). I am working on your issue but not being able to reproduce it on my setup makes it more complicated.

I am working with our Yocto team to try and understand why your build machine is not behaving as expected. I forwarded them your new error message.

Regards,

Olivier

stirulaka · September 5, 2018, 3:17pm

Hi All,

I did the

bitbake yaffs2-utils
cd …/build_bin/
make image_bin

with this the build errors are gone and there is a list of image created in build_bin/tmp/deploy/images/swi-mdm9x28

In the generated list, I am not able to find the boot-yocto.cwe However, I can see the below list in the deploy directory

mdm9x28-image-minimal-swi-mdm9x28-20180903112254.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180903113029.rootfs.4k.ubifs
legato-image.wp76xx.default
legato-image.wp76xx.squashfs
legato-image.wp76xx.ubi
legato-image.wp76xx.cwe
legato-image.version
legato-image.wp77xx.default
legato-image.wp77xx.squashfs
legato-image.wp77xx.ubi
legato-image.wp77xx.cwe
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.rootfs.2k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.rootfs.4k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.2k.ubifs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.ubifs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.rootfs.squashfs.hash
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.rootfs.squashfs.hash.txt
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.squashfs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.4k.ubifs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.ubifs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.squashfs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180904090851.squashfs.4k.ubi
lk.version
appsboot.mbn.unsigned
appsboot.mbn
mdm9x28-image-minimal-swi-mdm9x28.manifest -> mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.manifest
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.manifest
rootfs -> mdm9x28-image-minimal-swi-mdm9x28.4k.default
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.2k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28.squashfs -> mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.squashfs
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.2k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.4k.ubifs
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28.tar.bz2 -> mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.tar.bz2
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.4k.yaffs2
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.2k.ubifs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.ubifs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28.ubifs.2k.ubi -> mdm9x28-image-minimal-swi-mdm9x28-20180905081417.ubifs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.squashfs.hash
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.rootfs.squashfs.hash.txt
rootfs.rhash
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.squashfs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28.squashfs.2k.ubi -> mdm9x28-image-minimal-swi-mdm9x28-20180905081417.squashfs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.4k.ubifs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.ubifs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.ubifs.4k.ubi -> mdm9x28-image-minimal-swi-mdm9x28-20180905081417.ubifs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.squashfs.ubinize.cfg
mdm9x28-image-minimal-swi-mdm9x28-20180905081417.squashfs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.squashfs.4k.ubi -> mdm9x28-image-minimal-swi-mdm9x28-20180905081417.squashfs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.4k.ubi -> mdm9x28-image-minimal-swi-mdm9x28.squashfs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.2k.ubi -> mdm9x28-image-minimal-swi-mdm9x28.squashfs.2k.ubi
mdm9x28-image-minimal-swi-mdm9x28.ubi -> mdm9x28-image-minimal-swi-mdm9x28.squashfs.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.4k.default -> mdm9x28-image-minimal-swi-mdm9x28.4k.ubi
mdm9x28-image-minimal-swi-mdm9x28.default -> mdm9x28-image-minimal-swi-mdm9x28.4k.default
mdm9x28-image-initramfs-swi-mdm9x28.manifest -> mdm9x28-image-initramfs-swi-mdm9x28-20180905081417.rootfs.manifest
mdm9x28-image-initramfs-swi-mdm9x28-20180905081417.rootfs.manifest
mdm9x28-image-initramfs-swi-mdm9x28-20180905081417.rootfs.tar.bz2
mdm9x28-image-initramfs-swi-mdm9x28.tar.bz2 -> mdm9x28-image-initramfs-swi-mdm9x28-20180905081417.rootfs.tar.bz2
mdm9x28-image-initramfs-swi-mdm9x28-20180905081417.rootfs.cpio.gz
mdm9x28-image-initramfs-swi-mdm9x28.cpio.gz -> mdm9x28-image-initramfs-swi-mdm9x28-20180905081417.rootfs.cpio.gz
zImage–3.18.44-r1-swi-mdm9x28-20180905081417.bin
modules–3.18.44-r1-swi-mdm9x28-20180905081417.tgz
modules-swi-mdm9x28.tgz -> modules–3.18.44-r1-swi-mdm9x28-20180905081417.tgz
zImage-swi-mdm9x28.bin -> zImage–3.18.44-r1-swi-mdm9x28-20180905081417.bin
zImage -> zImage–3.18.44-r1-swi-mdm9x28-20180905081417.bin
zImage-initramfs-swi-mdm9x28.bin -> zImage-initramfs-3.18.44-r1-swi-mdm9x28-20180905081417.bin
zImage-initramfs-3.18.44-r1-swi-mdm9x28-20180905081417.bin
masterDTB.2k
masterDTB.4k
vmlinux
boot-yocto-mdm9x28-@{DATETIME}.2k.img
boot-yocto-mdm9x28.2k.unsigned.img -> boot-yocto-mdm9x28-@{DATETIME}.2k.img
boot-yocto-mdm9x28-@{DATETIME}.4k.img
boot-yocto-mdm9x28.4k.unsigned.img -> boot-yocto-mdm9x28-@{DATETIME}.4k.img
kernel.version
boot-yocto-mdm9x28.img -> boot-yocto-mdm9x28.4k.img
boot_mbnhdr
boot_hash.2k
boot_hash.4k
boot-yocto-mdm9x28.2k.img
boot-yocto-mdm9x28.4k.img
appsboot_wp76xx.cwe
yocto_wp76xx.4k.cwe
appsboot_wp77xx.cwe
yocto_wp77xx.4k.cwe

From the https://source.sierrawireless.com/resources/legato/linuxoverview/

swicwe -o custom-firmware.spk -c modemFW.spk mcuFW.cwe boot-yocto.cwe legatoz.cwe

boot-yocto.cwe is the required component to generate the .spk file. So , how to get the boot-yocto.cwe file from the yocto source build ?

opasco · September 5, 2018, 7:04pm

Siva,

There is something very bizarre with your build. We are not using yaffs2 file system anymore, which is why the yaffs2-utils package is not installed by default. If you are compiling the Release9 Yocto image you should only get squashfs images. It looks like you are using some older build configuration.

Can you please make sure you have extracted the source from http://downloads.sierrawireless.com/AirPrime/WP76xx/Release9/Legato-Dist-Source-mdm9x28-SWI9X07Y_02.16.02.00.tar.bz2 in a new directory, you running the compilation process in a fresh new shell and that you haven’t set any environment variables pointing to older packages? Or maybe try to create a new user on your build machine.

Also, for WP76, the boot-yocto.cwe image is now called yocto_wp76xx.4k.cwe.

Regards,

Olivier

nayannick2000 · October 27, 2023, 4:59am

hello sir, i am also building yocto for mangOH yellow[wp7608],release 17 components,
what should i give machine name in local.conf ?, i am doing in ubuntu 20 LTS ,
i want to add mqtt lib. in my images how can i add

thanks

jyijyi · October 27, 2023, 6:20am

you can have a look on this document on how to put files in yocto image:

nayannick2000 · October 27, 2023, 6:53am

nayan@nayan:~/workspace/legatoAF/legato-21.05.2.rc2$ update build/wp76xx/system.wp76xx.update 192.168.2.2
Applying update from file ‘build/wp76xx/system.wp76xx.update’ to device at address ‘192.168.2.2’.
root@192.168.2.2’s password:
/legato/systems/current/bin/update: /lib/libc.so.6: version `GLIBC_2.28’ not found (required by /mnt/legato/system/bin/…/lib/liblegato.so)
Update failed

how can i solve this issue

jyijyi · October 27, 2023, 7:13am

have you tried to update a helloworld.update first?

nayannick2000 · October 27, 2023, 7:15am

in target device it is showing like this

root@swi-mdm9x28-wp:~# app status
app: /lib/libc.so.6: version GLIBC_2.28' not found (required by /mnt/legato/system/bin/../lib/liblegato.so) root@swi-mdm9x28-wp:~# fwupdate query /legato/systems/current/bin/app: /lib/libc.so.6: version GLIBC_2.28’ not found (required by /mnt/legato/system/bin/…/lib/liblegato.so)
root@swi-mdm9x28-wp:~# legato version
21.05.2.rc2_6c56d9d1af36f3ff5ce910d6b3c3a4c3

jyijyi · October 27, 2023, 7:39am

i don’t see this in my WP7605 R17.
How to reproduce?

does this happen before your update?

nayannick2000 · October 27, 2023, 7:42am

no, after i updated the .cwe file it is showing like this

jyijyi · October 27, 2023, 7:44am

then your system update file has problem…

nayannick2000 · October 27, 2023, 1:05pm

Oct 27 18:32:55 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[8581] | 20231027 130255.187 getaddrinfo failed for addr dev.rightech.io with rc -11
Oct 27 18:32:55 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[8581] | 20231027 130255.187 dev.rightech.io is not a valid IP address
Oct 27 18:32:55 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[8581] | 20231027 130255.187 getaddrinfo failed for addr dev.rightech.io with rc -11
Oct 27 18:32:55 swi-mdm9x28-wp user.info Legato: INFO | mqttClientService[8581] | 20231027 130255.187 dev.rightech.io is not a valid IP address
Oct 27 13:02:55 swi-mdm9x28-wp user.warn Legato: -WRN- | mqttClientService[8581]/mqttClientService T=main | mqttClientService.c mqtt_Connect() 361 | Socket error

sir what should i do

jyijyi · October 27, 2023, 1:22pm

Does it work if you use real ip address?

nayannick2000 · October 27, 2023, 1:37pm

that is the correct ip i have given
but still it is showing like this

jyijyi · October 27, 2023, 1:58pm

I mean not using dev.rightech.io
Use something like 123.123.123.123
e.g.


Pinging dev.rightech.io [89.108.112.87] with 32 bytes of data:
Reply from 89.108.112.87: bytes=32 time=191ms TTL=53
Reply from 89.108.112.87: bytes=32 time=191ms TTL=53

nayannick2000 · October 28, 2023, 5:42am

yes sir in board terminal it is pinging

root@swi-mdm9x28-wp:~# ping 89.108.112.87
PING 89.108.112.87 (89.108.112.87): 56 data bytes
64 bytes from 89.108.112.87: seq=0 ttl=53 time=371.687 ms
64 bytes from 89.108.112.87: seq=1 ttl=53 time=332.689 ms
64 bytes from 89.108.112.87: seq=2 ttl=53 time=291.770 ms

jyijyi · October 28, 2023, 9:21am

Then you can modify your app to use real ip address

Topic		Replies	Views
Linux Kernel support Development tools	1	933	October 24, 2018
WP76xx Yocto Build Error WP Series	1	507	March 15, 2023
Wp7608 device tree update WP Series	3	1179	September 28, 2018
Customize linux distrubtion for WP85	3	1363	November 10, 2015
Yocto complication problem WP Series	11	1642	November 5, 2018

Yocto source build for wp7608

Related topics