Problem with MDC API

how do I flash back the software now? with the fwupdate app not available anymore?
Is there anything like a .exe installation for the cwe directly from windows without using shell commands?

you can see here:

I could flash the firmware from windows, but now I can`t ssh into the target anymore even if I can ping with no problem:
(lsh:FX30S2) $ ping 192.168.2.2
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
64 bytes from 192.168.2.2: icmp_seq=1 ttl=63 time=2.10 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=63 time=2.14 ms
— 192.168.2.2 ping statistics —
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.101/2.118/2.136/0.017 ms

(lsh:FX30S2) $ ssh root@192.168.2.2

It hangs forever

do you have UART console?
You might need to shut down firewall by:

iptables -I INPUT -j ACCEPT

you can also downgrade to R11 and use swiflash to recover the module:

I am already using the R11, this is the firmware I am using:
R11.0.0.007 Firmware for Generic GCF

Factory reset the target, now the ssh is returning but it fails on setting new password:

No password defined : Changing password for root
Enter the new password (minimum of 5 characters)
Please use a combination of upper and lower case letters and numbers.
New password:
Re-enter new password:
passwd: failure while writing changes to /etc/shadow
Connection to 192.168.2.2 closed.

I am also using a virtual machine (ubuntu running o windows) so I am not sure the swi will work properly as the USB is mirrored from windows.
This is the reason why I am flashing the firmware from windows, which seems working somehow…

you might see if this helps:

The problem doesn`t seem to be only the login, but no space left on the device which seems to be the case.
so the ssh command occasionally works, but I still get errors like:

root@192.168.2.2’s password:
chsh: /etc/passwd.3460: No space left on device
chsh: cannot lock /etc/passwd; try again later.
root@fx30s:~#

which still goes through, but I can`t update the files anymore:

(lsh:FX30S2) $ app install mySystemAws.wp77xx.update 192.168.2.2
Applying update from file ‘mySystemAws.wp77xx.update’ to device at address ‘192.168.2.2’.
root@192.168.2.2’s password:
chsh: /etc/passwd.3565: No space left on device
chsh: cannot lock /etc/passwd; try again later.
Unpacking package: 0%
***Error: Security check failure. See log for details.

FAILED
cat: write error: Broken pipe
Update failed

So, how do I fresh clean all the files in the target? as I suspect there are unnecessary files possibly still stored in there from the different firmware updates…

you can use “df -h” to see if this is really no space.

Normally if you change the FW (e.g. R11 to R9), the legato partition will be erased and install the new one.

yes, did that, it seems I am using 100% for the space, even if I didn`t have this problem before:
root@fx30s:~# df -h
Filesystem Size Used Available Use% Mounted on
devtmpfs 256.0K 8.0K 248.0K 3% /dev
/dev/mapper/rt 17.3M 17.3M 0 100% /
mdev 256.0K 8.0K 248.0K 3% /dev
tmpfs 91.2M 0 91.2M 0% /dev/shm
tmpfs 91.2M 0 91.2M 0% /run
tmpfs 91.2M 40.0K 91.2M 0% /var
tmpfs 91.2M 2.0M 89.3M 2% /tmp
mdev 256.0K 8.0K 248.0K 3% /dev
tmpfs 91.2M 0 91.2M 0% /dev/shm
tmpfs 91.2M 0 91.2M 0% /run
tmpfs 91.2M 40.0K 91.2M 0% /var
tmpfs 91.2M 2.0M 89.3M 2% /tmp
/dev/ubi3_0 104.5M 104.5M 0 100% /mnt/flash
/dev/ubiblock2_0 4.0M 4.0M 0 100% /mnt/legato
/dev/ubi4_0 8.7M 72.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/mapper/rt 17.3M 17.3M 0 100% /usr/share/zoneinfo/localtime
/dev/ubi3_0 104.5M 104.5M 0 100% /home
/dev/ubiblock1_0 15.5M 15.5M 0 100% /firmware
/dev/ubi3_0 104.5M 104.5M 0 100% /legato
tmpfs 91.2M 2.0M 89.3M 2% /etc/ld.so.conf
tmpfs 91.2M 2.0M 89.3M 2% /etc/ld.so.cache
tmpfs 91.2M 2.0M 89.3M 2% /etc/hosts
cgroupsRoot 91.4M 0 91.4M 0% /sys/fs/cgroup
/dev/ubi3_0 104.5M 104.5M 0 100% /legato/systems/current

That is why I was asking what I can remove before breaking the legato or the linux fs

no idea, never see such issue before…
You might need to downgrade and see what happens

There is some sort of problem here, when I flash the firmware and then the ssh command is unresponsive, I have to trigger a factory reset with the button in front of the unit.
At this point I can log in but I can still see all the apps I have built ( I did build a system with multiple apps).
Is this what it should happen? Or all the apps and the system I have built should be removed?
I have ssh into the target and I still see the fs 100% loaded, how do I clean this if the device is not cleaning my pre-existing system?
Is there a FORCE command when flashing the firmware which will clean up any new app??

from my experience, if the new FW is having different legato version, then previously installed application will be removed when fwupdate a new firmware.

that is not my case, I can still see the apps I have built.
How do I revert from this?

how about “app remove”

tried to stop the app, then to remove it.
The target throw an error and then reboot:

root@fx30s:~# app remove mqttClient
Removing app ‘mqttClient’…
***Error: Couldn’t remove app ‘mqttClient’.
root@fx30s:~# Connection reset by 192.168.2.2 port 22

there is an app running on the legato factoryRecoveryService but I can`t see see anywhere how to run this API. It could be the answer as I believe the FW will not touch the installed apps.

factoryRecoveryService is only used to handle the event of the factory reset button, I also see that:

root@fx30s:~# fwupdate checkStatus
Connecting to service …
Bad status (Download failed), install not possible.

The firmware wasn`t installed properly, and possibly still caused by the fact the fs is full.
So how do I recover from this situation?

no idea, maybe install some very old WP77 FW and see if it will help

The problem with the flashing has been solved, had to factory reset the device to eliminate unecessary data in the fs uploaded during development.
Issue with the modem still persist, I will move the topic to the Sierra Wireless Forum which seems more appropriated for this case, as I really need to get this to work with the FX30S and knowing this works with the WP76 doesn`t solve my problem unforutnately.