Legato framework stopped

Legato Application Framework
1

Hi there ,
I came across a strange behavior where in the legato framework has stopped and if i try starting it using “legato start” command i have the below response

root@swi-mdm9x28-wp:~# legato start
Starting Legato…
tee:/dev/console: No such device
tee:/dev/console: No such device
tee:/dev/console: No such device
root@swi-mdm9x28-wp:~#

root@swi-mdm9x28-wp:~# legato status
Systems installed:
1 [good] ← current
Legato framework is NOT running.

Below is the memory availability details

root@swi-mdm9x28-wp:~# df -h
Filesystem Size Used Available Use% Mounted on
devtmpfs 256.0K 4.0K 252.0K 2% /dev
/dev/mapper/rt 25.4M 25.4M 0 100% /
mdev 256.0K 4.0K 252.0K 2% /dev
tmpfs 76.3M 0 76.3M 0% /dev/shm
tmpfs 76.3M 0 76.3M 0% /run
tmpfs 76.3M 36.0K 76.3M 0% /var
tmpfs 76.3M 32.0K 76.3M 0% /tmp
mdev 256.0K 4.0K 252.0K 2% /dev
tmpfs 76.3M 0 76.3M 0% /dev/shm
tmpfs 76.3M 0 76.3M 0% /run
tmpfs 76.3M 36.0K 76.3M 0% /var
tmpfs 76.3M 32.0K 76.3M 0% /tmp
/dev/ubi3_0 104.5M 104.5M 0 100% /mnt/flash
/dev/ubiblock2_0 5.8M 5.8M 0 100% /mnt/legato
/dev/ubi4_0 8.7M 84.0K 8.1M 1% /mnt/userrw
overlay 104.5M 104.5M 0 100% /etc
overlay 104.5M 104.5M 0 100% /data
overlay 104.5M 104.5M 0 100% /lib/firmware
/dev/ubi3_0 104.5M 104.5M 0 100% /home
/dev/mmcblk0p1 7.3G 4.0K 7.3G 0% /data/emmc
/dev/ubiblock1_0 24.6M 24.6M 0 100% /firmware
/dev/ubi3_0 104.5M 104.5M 0 100% /legato
tmpfs 76.3M 32.0K 76.3M 0% /etc/ld.so.conf
tmpfs 76.3M 32.0K 76.3M 0% /etc/ld.so.cache
tmpfs 76.3M 32.0K 76.3M 0% /etc/hosts
tmpfs 76.3M 32.0K 76.3M 0% /etc/resolv.conf

It could be great if somebody gives me some pointers to investigate this issue .

Thanks & Regards

  • Akshay
2

Which version are your testing? Original version or customized version?

3

Hi @JordanZhao Thanks for the response .
Its a customized version and I was able to find out the issue i.e the data was written in the location named /data/emmc2(utilizing internal memory) instead of /data/emmc (EMMC) .
But it was also observed that /data/emmc2 had files with size greater than 104 MB . Do you have any pointers on this ?

4

I saw the similar case reported in SF ticket, right?
If yes, we will continue to follow up there.

5

Yes . A SF ticket is raised on the same

6

Question:
The eMMC2 partition is not mounted to physical eMMC. As per your suggestion below customer is mounting the eMMC folder with the physical eMMC.

Also the mounting takes place from the /data directory in this case as the eMMC2 folder is not mounted to physical eMMC and is just a directory in the /data. It is seen that the size is around 350MB whereas the flash size of the WP7608 module is around 256MB.

Would like to understand how the file size greater than the memory size is created in the module? This stops the entire legato framework which can be restarted on deleting the eMMC2 directory.

Answer:
WP7 use UBIFS which support on-the-fly compression so it is possible the total written data is bigger that the actual flash space.
But the compression rate cannot guarantee as depends on the actual data written, i.e. more effective on text and repeat data.