Swi-fx30-catm_3.0.0 build error in swi-linux

But “make clean” will delete the bblayer.conf file.
which is required to add a new custom layer.
How can be add a custom layer without editing the bblayer.conf

How about adding your recipe in current existing layer?

Hi @ravishkrishnan.kunch

A couple things you can try to improve your build time:

  1. Try the bitbake command directly:
    Type:
    make dev
    bitbake -c build

  2. Implement yocto share state cache. Basically, once you build the image, move the cache to another location, and then point to it. The next time you build with sstate cache, only the packages that are required will be built.

BR,
Chris

Thanks @cchenry
How to point to the copied state cache? is this some configuration.

i was able to build
But now i am unable to flash the cwe file using swiflash
**swiflash -m “wp77xx” -i boot-yocto-legato_wp77xx.cwe **
Detecting USB of the target
DONE
Communicating with the target
DONE
Switching to firmware download mode
…DONE
Downloading the firmware
…ERROR: Firmware Download failed. Callback status 59399DONE
ERROR: Firmware Download Failed

You can transfer the cwe file to module and use fwupdate command in target module to update

[quote=“jyijyi, post:26, topic:25090, full:true”]
You can transfer the cwe file to module and use fwupdate command in target module to update
[/quote
fwupdate also not working
root@fx30s:~# fwupdate download boot-yocto-legato_wp77xx.cwe
Connecting to service …
Can’t open file ‘boot-yocto-legato_wp77xx.cwe’ : No such file or directory
root@fx30s:~# ls
boot-yocto-legato_wp77xx.cwe

swiflash -m "wp77xx" -r is also working after flashing Sierra Wireless FX30 Firmware CatM
https://downloads.sierrawireless.com/airlink/FX30/CatM/FX30_WP77xx_full_R14.1.1.002-sierra-SWI9X06Y_02.36.06.00.cwe
Will the swiflash tool not work with R14.1.1 based Firmware ?
we have been using the swiflash in our production for R9.1.1 based firmware.

You need to specify the absolute path

E.g.

fwupdate download /tmp/boot-yocto-legato_wp77xx.cwe

installation was not successful it got stuck at this point
root@fx30s:~# fwupdate download /home/root/boot-yocto-legato_wp77xx.cwe
Connecting to service …
Download started …
Download successful
Installing & Reboot …

But the Gateway got rebooted , but the changes are not visible in the rootfs

Probably the yocto image is too big, you can download just the yocto.cwe to confirm if it can upgrade

How big is your yocto.cwe image now?

With the Yocto.cwe file also it is failing to install.

What is response on

At!entercnd=“A710”
At!partition?
At!partition=?

With R14.1.1 microcom looks buggy, microcom -E /dev/ttyAT is not echoing the commands.

please find the response to the AT commands -
Mon Jan 10 04:58:07 UTC 2022
Manufacturer: Sierra Wireless, Incorporated
Model: FX30S(WP7702)
Revision: SWI9X06Y_02.36.06.00 63d944 jenkins 2020/12/10 19:12:28
IMEI: 354723090117127
IMEI SV: 6
FSN: VU847300341510
+GCAP: +CGSM,+DS

OK
Mon Jan 10 05:00:20 UTC 2022
OK
Mon Jan 10 05:02:33 UTC 2022
PART BLOCK SIZE
NAME OFFSET (KB)
0:SBL 00000000 2560
0:MIBIB 0000000A 2560
0:BACKUP 00000014 6656
0:SECURITY 0000002E 1024
0:PERSIST 00000032 2048
0:EFS2 0000003A 17920
0:SWIFOTA 00000080 81152
0:TZ 000001BD 1536
0:DEVCFG 000001C3 768
0:RPM 000001C6 768
0:modem 000001C9 32768
0:aboot 00000249 1024
0:boot 0000024D 15360
0:system 00000289 30720
0:LEFWKRO 00000301 8960
0:SWIRW 00000324 25600
0:USERAPP 00000388 134144
0:RESERVED 00000594 55808
0:SLOT_2 0000066E 34304
0:SLOT_1 000006F4 34304
0:SLOT_0 0000077A 34304

OK
root@fx30s:~# echo ‘At!partition=?’ > /tmp/input
root@fx30s:~# ./atinout /tmp/input /dev/ttyAT /tmp/output
root@fx30s:~# echo "date -u cat /tmp/output" >> /home/at_log
root@fx30s:~# cat /home/at_log
Mon Jan 10 04:58:07 UTC 2022
Manufacturer: Sierra Wireless, Incorporated
Model: FX30S(WP7702)
Revision: SWI9X06Y_02.36.06.00 63d944 jenkins 2020/12/10 19:12:28
IMEI: 354723090117127
IMEI SV: 6
FSN: VU847300341510
+GCAP: +CGSM,+DS

OK
Mon Jan 10 05:00:20 UTC 2022
OK
Mon Jan 10 05:02:33 UTC 2022
PART BLOCK SIZE
NAME OFFSET (KB)
0:SBL 00000000 2560
0:MIBIB 0000000A 2560
0:BACKUP 00000014 6656
0:SECURITY 0000002E 1024
0:PERSIST 00000032 2048
0:EFS2 0000003A 17920
0:SWIFOTA 00000080 81152
0:TZ 000001BD 1536
0:DEVCFG 000001C3 768
0:RPM 000001C6 768
0:modem 000001C9 32768
0:aboot 00000249 1024
0:boot 0000024D 15360
0:system 00000289 30720
0:LEFWKRO 00000301 8960
0:SWIRW 00000324 25600
0:USERAPP 00000388 134144
0:RESERVED 00000594 55808
0:SLOT_2 0000066E 34304
0:SLOT_1 000006F4 34304
0:SLOT_0 0000077A 34304

OK
Mon Jan 10 05:03:07 UTC 2022
To print partition table: AT!PARTITION?
To modify partition sizes: AT!PARTITION=,[,,…]
- name of the first partition to modify its size, can be blank
- new size in KB of the first partition
,… - new sizes of next partitions
for example: AT!PARTITION=0:boot,2560
List of partitions whose size can be modified:

None/Not Allowed

OK

your rootfs partition is not enough for storing this big yocto image…
And it seems it cannot let you modify the partition size…

Now the workaround is to store your executable in /home/root and run them in RAM.
You can see this as example:

i have a Native Linux Application which is sand boxed to a legato application.
In the Application i am using the Linux API localtime() to log the current time.
When i run the Application in the Native Linux env i can see the correct time.
But the same application after sand-boxing into a legato application and run it shows in incorrect time.
PS: with R9.1.1 i was not seeing this issue, After moving to R14.1.1 i see this issue.


how about using the legato API:

The current code with the native linux api’s with R9 is in production.
Due to FX30 memory chip change , we are forced to move to R14.
Can’t this be fixed without using the legato API.
The same legato app(with native linux api) was working with R9.1.1

does it work for unsandboxed app?

BTW, does “date” command work in terminal?

Yes, screenshot attached.

does it work for unsandboxed app?