Issue creating CWE and SPK files in WP7702 release 15 firmware

[shommersom]

We’ve been having a lot of issues getting the release 15 software to build for the WP7702, however with the download provided earlier and using a VM rather than WPF. We’re now at the final step to create the cwe & spk files for production.

However we’ve run into issues with that as well. With our own project when we load it using fwupdate it fails silently, when using FDT2 we get the following error with the CWE or SPK:

I’ve then made a test project from scratch which should only toggle a led on our board, this does not give an error when loading the CWE or SPK.

However when this is loaded all applications look to have disappeared:

This is the test project, we use the make_release.sh script to build the CWE and SPK files
Test.zip (5.1 KB)

What is going wrong here? How can it generate with incorrect image sizes? why do all the applications vanish when loading the test project?

[jyijyi]

have you tried to download legato.cwe built by “make wp77xx”?
If it can be downloaded, then you can see here to modify wifi.sdef in order to embed your application to the leagto.cwe:

Flash size wp7607

you can go to legato-19.02.0/modules/WiFi/wifi.sdef, under “apps:” section, add e.g. $LEGATO_ROOT/apps/sample/helloWorld/helloWorld.adef [image] Now the new app will be included in legato.cwe. Please also note that the max size for legato partition is 8MB.

You can also see here:

Legato not installed using fwupdate

not sure if swicwe can help on compressing the image: owner@ubuntu:~/Yocto/tools/swicwe/linux64$ ./swicwe --full-help swicwe (version 1.8.1) Copyright (C) Sierra Wireless Inc. Use of this work is subject to license. Usage: swicwe <--LCWE|--YCWE|--ACWE|--BCWE|--MCWE|--CONT|--REPL| -P> [-Z] [-F] [-R] [-X] [-x] [<image type>...] [<image name>...] [-o <output cwe file>] Commands and options: --LCWE: set to generate Legato CWE file. If no 'image type' specified will as…

[shommersom]

the CWE I’m using is the one copied from legato-squashfs.ubi.cwe which is the one legato.cwe links to. I’ve tried uploading legato.cwe using fwupdate and the result is the same:

Using your second link mentions using the -s option for the CWE generation and that looks like it might have fixed it for our application. We will be doing some more testing, but this looks promising.