Can you check if the .update file already compiled in TARGET_Legato_Debug folder?
Then you can ignore those errors if the .update file is newly generated
No it is not newly generated. It was before. Actually, I cannot make it run. Once i make it run the project name “textLoc” is not there.
then why you can build it before but not for now?
i did not get it. But i am able to build it now but it is crashing once it starts.
is it a problem of compatibility or something else?
you need to upgrade your module FW to R12 which is having legato 18.10.3 matching with the app:
i am following this to upgrade
I don’t know, i am getting this error !!!
How about using the exe in R13?
The same as firmware R12
you can download the .SPK file and transfer to module by WINSCP through USB ECM port.
After that , you can type "fwupdate download xxx.spk " in module to upgrade FW.
I am following 5.2
and have got the followings
mangoh@mangoh-dev:~/Downloads$ fwupdate download WP76xx_Release12_SIERRA_PTCRB.spk
Command ‘fwupdate’ not found, but can be installed with:
sudo apt install fwupdate
mangoh@mangoh-dev:~/Downloads$ ls
Workplace WP76xx_Release12_SIERRA_PTCRB.spk
mangoh@mangoh-dev:~/Downloads$ ssh root@192.168.2.2
root@192.168.2.2’s password:
It is strongly recommended to setup credentials for remote login.
Please select one of the following options:
- Setup ssh keys and disable passwords-based authentication via ssh
(the most secure) - Setup password (better than nothing)
- Do nothing
^C
root@swi-mdm9x28:~# cminfo
-sh: cminfo: not found
root@swi-mdm9x28:~# cm info
Device: WP7601
IMEI: 357408080103686
IMEISV: 1
FSN: U1744586131410
Firmware Version: SWI9X07Y_02.10.00.00 000000 jenkins 2017/11/02 23:09:00
Bootloader Version: SWI9X07Y_02.10.00.00 000000 jenkins 2017/11/02 23:09:00
MCU Version: 002.006
PRI Part Number (PN): 9907166
PRI Revision: 002.004
Carrier PRI Name: VERIZON
Carrier PRI Revision: 002.014_002
SKU: 1103193
Last Reset Cause: Crash
Resets Count: Expected: 465 Unexpected: 65
what could be the problem?
You did not follow 5.1.
You need to first go to legato source folder, and type “. bin/confinglegatoenv”
I am following 5.1 but got errors, the file is cmds_1 (9.8 KB) attached.
What do you see for
source .bin/configlegatoenv
Please see the attched file. cmds_2 (4.3 KB)
I don’t see you enter the command
which command?
“source .bin/configlegatoenv”
and where, at 192.168.2.2 or MangOH linux?
if i enter the command source .bin/configlegatoenv into bin folder, it shows no such file or directory
In linux pc, i can see you have the file there
dev:~/legato_framework/legato/bin$ ls
app ima-sign.sh mkexe shlib
av-pack instapp mkinfo simu
cextgenerator.py instlegato mklegatoimg splitdebug
checkpa instsys mklegatotreero startlegato
configlegatoenv