as I was trying to explain, the latest firmware for the FX30S (official) is :
Included │ swi-fx30-catm_2.0.0 │ SDK for FX30-CATM (Release R11.0.0.007 + Legato 18.09.4)
which is what my leaf profile is setup to, and I have been told several time that downloading a generic wp77 firmware is very bad practice as it can create unexpected results.
will look for answers from our hardware supplier, we are not getting anywhere here.
Waiting for a new firmware release when this should already been working, I have no clue how this should help us
@cchenry I have tried again and the download from the airVantage worked once, problem could have been with the updating of the device on the server which took a while.
Problem is that now I am trying to download again and it will no go through.
I have tried to reset the modem to factory settings again, AT!RMARESET=1, and to run the:
at+wdss=1,1
OK
+WDSI: 4
+WDSI: 6
+WDSI: 23,0
+WDSI: 4
+WDSI: 6
+WDSI: 23,1
which will connect but will again return no update status, even if in the airVantage there is a pending installation.
At this point I have deleted the device from the airVantage once again, waited for 5 min and created a new one, selected the software to download to the unit.
Tried to trigger the connection with the AT command and I keep getting a Session failure bootstrap server, assume this once again is with the device not yet ready on the airVantage?
I have tried this morning again and I get the same result from yesterday:
at+wdsi?
+WDSI: 4479
OK
at+wdss=1,1
OK
+WDSI: 4
+WDSI: 6
+WDSI: 23,0
+WDSI: 7
+WDSI: 8
while the modem is connected, I have a third ssh session where I can ping the server:
root@fx30s:~# ping eu.airvantage.net
PING eu.airvantage.net (52.17.142.62): 56 data bytes
64 bytes from 52.17.142.62: seq=0 ttl=218 time=481.512 ms
64 bytes from 52.17.142.62: seq=1 ttl=218 time=434.681 ms
64 bytes from 52.17.142.62: seq=2 ttl=218 time=445.531 ms
so there is connection to the airvantage but I am definetely missing something, especially what is the meaning of the “Session failure on bootstrap server”?
@cchenry may be the bootstrap error related with the airVantage and the fact I didn`t wait long enough (thought 5 min were ok)? I have deleted the device, waited for 30min and created it again with a different name.
It would be nice to understand what is actually happening, it may save us some headaches later down the lines.
I have also made a bundle using the standard firmware ( and tried to download that from the airVantage, it does goes through even if is taking a while (50MB (CurrentImageSize: 17301504) in 1.5h!).
Was planning to try to upgrade/downgrade the firmware between R9 and R11 but it may take a while so will make a bundle with a simple app and try with that.
One question about the bundle.app file:
Is the target checking the revision and type and if this matches to the current installed it will not install the new download?
Or this is only evaluated when the bundle is released and not by the target itself?
@cchenry the problem with the bootstrap server was after I did reset the target and re-installed the R11 firmware. So at that point I wasn`t running our yocto and legato.
@cchenry would you have a bundle I could just use for testing this download?
Downloading the 50MB of the firmware is going to take the whole day, it still keeps going.
If you have a bundle I can just use for test, then I will move on using the system I have made and see the result.
moving some small steps forward, I can get a consistent result if I flash once again the FX30_WP77xx_full_R11.0.0.007-sierra-SWI9X06Y_02.22.12.00.cwe firmware to the unit, reboot and start the connection with airVantage where I am downloading my app which is the cwe image of my system built with legato.
Once my system is downloaded and installed, then after rebooting the unit, everything works but not the airVantage connection. Even if I remove the app which is starting the le_avc session. reboot and then try to connect with the AT+WDSS=1,1 the service will return the boostrap server error.
I can still ping the server from shell so the connection is available.
So the problem seems to be with the legato system, which makes me wonder why this is all happening as I am only starting the le_avc session where the avcDaemon should look after the connection and I haven`t touched that process. My system is including the default.sdef: #include “$LEGATO_ROOT/default.sdef”
according to legato docs and the leaf workspace is in sync.
leaf status:
│ Profile: FX30S [current] (sync) │
│ Packages │ Identifier │ Description │
│ Included │ swi-fx30-catm_2.0.0 │ SDK for FX30-CATM (Release R11.0.0.007 + Legato 18.09.4)
which should be the same of the firmware I have flashed to the target.
This is to say, if the problem is with the legato system, I have no clue what I have done wrong as according to what I know the environment and files are looked after by leaf.
ran the AT commands you have asked:
ati
Manufacturer: Sierra Wireless, Incorporated
Model: FX30(WP7702)
Revision: SWI9X06Y_02.22.12.00 eaf79c jenkins 2019/04/24 18:48:27
IMEI: 354723090144204
IMEI SV: 3
FSN: VU007185430210
+GCAP: +CGSM
OK
ati8
Legato Ver: 18.09.4_402ec3a4fd156c4e10356a401a86cec9_modified
Yocto Ver: SWI9X06Y_02.22.04.00 2020-06-18_02:43:58
OS Ver: Linux version 3.18.44 (jenkins@CAKEL-EV-ALBLD2) (gcc version 6.2.0 (GCC) ) #2 PREEMPT Thu Jun 18 02:45:08 UTC 2020
LK Ver: 1.3.0_da731a7332
RootFS Ver: SWI9X06Y_02.22.04.00 2020-06-18_02:43:58
UserFS Ver: unknown
MCU Ver: 002.011
OK
AT!FWD?ALVER
R11.0.0.007
OK
This is after I have downloaded my system app to the device.
@cchenry any help will be highly appreciated, either here or on the legato forum.
We can`t see how we may have done anything wrong which would interfere with the avcDaemon so if we could rule this out it would be fantastic.
The bundle.app file must have type field set to: FX30(WP7702)
The revision field is used by AV to validate the image is installed correctly. I suspect your revision string is not sufficient and will need a unique identifier. I recommend you use the FX30 R11.0.0.007 source code Leaf packages with identifier: swi-fx30-catm_2.0.0
When you build your full yocto image, the Legato version will automatically append a short hash that takes care of the unique revision number.
@cchenry sorry, what is fixing the problem with the AirVantage connection is not flashing the stock firmware but restoring the system to the golden legato.
legato stop
rm -rf /legato/*
and then will reboot.
I was doing both of these steps, but what is really making the difference is the first one and not flashing the stock firmware.
After I download my legato system, the connection to airVantage with AT commands will not longer work, this is the error I get:
avcDaemon[1278]/avcDaemon T=main | avcClient.c EventHandler() 632 | Authentication to BS failed
avcDaemon[1278]/avcDaemon T=main | avcClient.c EventHandler() 544 | Session failure
avcDaemon[1278]/avcDaemon T=main | avcClient.c EventHandler() 552 | Session failure on bootstrap server
avcDaemon[1278]/avcDaemon T=main | osTimer.c lwm2mcore_TimerStop() 173 | Unable to stop the timer
avcDaemon[1278]/avcDaemon T=main | osTimer.c lwm2mcore_TimerStop() 179 | Timer reference is NULL
avcDaemon[1278]/avcDaemon T=main | avcServer.c ProcessUserAgreement() 1472 | Broadcast notification to applications
avcDaemon[1278]/avcDaemon T=main | avcServer.c ProcessUserAgreement() 1472 | Broadcast notification to applications
dcsDaemon[1292]/dcsDaemon T=main | dcsServer.c TryStopDataSession() 1634 | Tearing down data session
dcsDaemon[1292]/le_pa_dcs T=main | pa_dcs_linux.c pa_dcs_SetDefaultGateway() 568 | Default gateway or interface is empty
atQmiLinker[1250]/atQmiLinker T=Reader | atForward.c SendUnsolicitedResponse() 458 | **^M +WDSI: 5^M **
atQmiLinker[1250]/atQmiLinker T=Reader | atForward.c SendUnsolicitedResponse() 458 | **^M +WDSI: 7^M **
atQmiLinker[1250]/atQmiLinker T=Reader | atForward.c SendUnsolicitedResponse() 458 | **^M +WDSI: 8^M **
secStore[1350]/swiQmi T=main | swiQmi.c swiQmi_CheckResponse() 795 | Sending QMI_SWI_SFS_BACKUP_REQ_V01 failed: rc=0 (), resp.result=1.[0x01], resp.error=3.[0x03]
secStore[1350]/le_pa_secStore T=main | pa_secStore_qmi.c BackupSfs() 1603 | Unexpected QMI response -6 (LE_FAULT)
The problem seems related with the legato system I have built, but for that reason I have removed all the extra apps and now I am just starting the modem data connection and trying to connect to the airVantage:
I have removed all my other apps and now I am just starting the modem and triggering a connection to the airVantage, modem start properly and I can ping the server, then I trigger the le_avc_StartSession() and wait for the handler to return.
@cchenry , correct, the stock legato 18.06.5 works but not the system I built.
AirVantage connection goes back to working once I restore the golden legato.
I am building the system by using leaf, so will setup the profile and then sync to the required package.
After I have setup the workspace I will create a profile and sync it a specific package
│ Workspace: /home/xxxxx
│ Profile: FX30 [current] (sync) │
│ Packages │ Identifier │ Description │
│ Included │ swi-fx30-catm_2.0.0 │ SDK for FX30-CATM (Release R11.0.0.007 + Legato 18.09.4) │
As you see the package I am syncing to is the swi-fx30-catm_2.0.0, then will run the mksys command which will build my system, in my system definition I am including the default.sdef which is mapped from the $LEGATO_ROOT
Only thing I can see is that for some reason leaf is no finding the swi-fx30-catm_2.0.0 anymore if I run the leaf search command, but I had that package downloaded and installed some time ago.
If I run the leaf profile sync shell will return without doing anything so I would expect there is not issue with the profile.