MangOH red board unable to update image

Hi,

Main aim of building and flashing the MangOH board was to test Talon Mirage IoT card.

Downloaded the MangOH source, Legato source and built as per the steps in link : https://github.com/mangOH/mangOH On ubuntu 14.04 machine.

Image was built successfully and also flashed. But the board does not update with new image, while falls back to the existing one.

Below are the are the logs of the image and the build flashing logs.
Default image info. :
root@swi-mdm9x28:~# cm info
Device: WP7607
IMEI: 359779080125194
IMEISV: 4
FSN: VN842200670510
Firmware Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
Bootloader Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
MCU Version: 002.009
PRI Part Number (PN): 9907327
PRI Revision: 001.004
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.032_000
SKU: 1103511
Last Reset Cause: Reset, User Requested
Resets Count: Expected: 16 Unexpected: 0
root@swi-mdm9x28:~#

Flashing steps :
IM-RT-LP-037:~/sierra$ sudo ./bin/update red.wp76xx.update 192.168.2.2
Applying update from file ‘red.wp76xx.update’ to device at address ‘192.168.2.2’.
Unpacking package: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
Applying update: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
SUCCESS
Done
@IM-RT-LP-037:~/sierra$

Image info after reboot:
root@swi-mdm9x28:~# cm info
Device: WP7607
IMEI: 359779080125194
IMEISV: 4
FSN: VN842200670510
Firmware Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
Bootloader Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
MCU Version: 002.009
PRI Part Number (PN): 9907327
PRI Revision: 001.004
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.032_000
SKU: 1103511
Last Reset Cause: Reset, User Requested
Resets Count: Expected: 17 Unexpected: 0
root@swi-mdm9x28:~#

update command will not change the info in “cm info”.
you can check “app status” if the new app has been installed

Oh so i was presuming few things wrong. Thanks for the info.

I have hooked the Talon Mirage IoT card (WL18xx)to the board, want to disable the default wifi on the board by commenting the LEGATO_WIFI_PA in the red.sdef file.

How do i verify if i have changed the image.

can you check if “legato version” and “legato status” has been changed?

For building, i am using Legato 19.02.0, latest mangOH source from git, and toolchain poky-swi-ext-glibc-x86_64-meta-toolchain-swi-armv7a-neon-toolchain-swi-SWI9X07Y_02.28.03.05.sh.

Below is the legato o/p from the board:
root@swi-mdm9x28:~# legato status
Systems installed:
0 [good] <-- current
Legato framework is running.
root@swi-mdm9x28:~# legato version
18.03.0_b463e04cf08fb8d8f1ea5ee00d7894c0

I had not checked the default setting on the board.

my test shows that legato version will be changed:

root@swi-mdm9x28-wp:/tmp/valgrind# legato status
Systems installed:
45 [good] <-- current
Legato framework is running.
root@swi-mdm9x28-wp:/tmp/valgrind#
root@swi-mdm9x28-wp:/tmp/valgrind# cm info
Device: WP7607
IMEI: 359779081234565
IMEISV: 6
FSN: VN730485080103
[ 8298.653181] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
Firmware Version: SWI9X07Y_02.28.03.03 000000 jenki[ 8298.668902] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
ns 2019/05/21 03:33:04
Bootloader Version: SWI9X07Y_02.28.03.03 000000 jenkins 2019/05/21 03:33:04
MCU Version: 002.011
PRI Part Number (PN): 9908958
PRI Revision: 001.000
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.068_000
SKU: 1104301
Last Reset Cause: Reset, User Requested
Resets Count: Expected: 163 Unexpected: 13
root@swi-mdm9x28-wp:/tmp/valgrind#
root@swi-mdm9x28-wp:/tmp/valgrind# legato version
19.02.0_cf7c704124f14adfeb3f8595be4b0772_modified
root@swi-mdm9x28-wp:/tmp/valgrind#
root@swi-mdm9x28-wp:/tmp/valgrind# app status
[running] atAirVantage
[running] atQmiLinker
[running] atService
[running] audioService
[running] avcService
[running] cellNetService
[running] dataConnectionService
[running] fwupdateService
[running] gpioService
[running] modemService
[running] portService
[running] positioningService
[running] powerMgr
[running] qmiAirVantage
[running] secStore
[stopped] smsInboxService
[stopped] spiService
[stopped] tools
[stopped] voiceCallService
[stopped] wifi
[stopped] wifiApTest
[stopped] wifiClientTest
[running] wifiService
[stopped] wifiWebAp
[stopped] hello4
[running] wakeup_app
[running] http_get_WP76
root@swi-mdm9x28-wp:~# update /tmp/red.wp76xx.update
Unpacking package: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
Unpacking package: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
Applying update: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
SUCCESS
root@swi-mdm9x28-wp:~#
root@swi-mdm9x28-wp:~# update-ld-cache: Updating ld.so.cache using [/legato/systems/current/lib]…
update-ld-cache: Updating /etc/ld.so.cache …
update-ld-cache: Removing stale mount [/etc/ld.so.cache]…
[ 147.381478] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv_addr:0x64 MSTR_STS:0x0d1343c8 OPER:0x00000010
[ 147.396295] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:1 tx:1) mode:FIFO slv_addr:0x64 MSTR_STS:0x0d1343c8 OPER:0x00000010
[ 147.412638] LTC2941 6-0064: ltc2941 read_reg failed!
[ 147.416870] LTC2941 6-0064: Could not read status register

root@swi-mdm9x28-wp:~#
root@swi-mdm9x28-wp:~# legato version
19.02.0_285ced22f832292409408d3849455278
root@swi-mdm9x28-wp:~#
root@swi-mdm9x28-wp:~# app status
[running] atAirVantage
[running] atQmiLinker
[running] atService
[running] audioService
[running] avcService
[running] battery
[running] cellNetService
[running] dataConnectionService
[running] dataHub
[running] fwupdateService
[running] gpioService
[running] ledService
[running] modemService
[running] portService
[running] positioningService
[running] powerMgr
[running] qmiAirVantage
[stopped] redSensorToCloud
[running] secStore
[stopped] smsInboxService
[stopped] spiService
[stopped] tools
[stopped] voiceCallService
[stopped] wifi
[stopped] wifiApTest
[stopped] wifiClientTest
[running] wifiService
[stopped] wifiWebAp
root@swi-mdm9x28-wp:~#
root@swi-mdm9x28-wp:~# legato status
Systems installed:
45 [good]
46 [tried 1] <-- current
Legato framework is running.

Ok so after checking of logs, found out that the new image is rebooting and going back to old one.

Logs attached in txt file. red.wp76xx.update_failed.txt (45.9 KB)

I suggest you upgrade the fw of your module to R13.3 and then follow the steps below to build the mangoh update file

Or you can use my update file based on R13.3.
red.wp76xx.part2.rar (2.7 MB) red.wp76xx.part1.rar (4 MB)

Ok here is what i did.
I did not use the attached images, as i had to modify the legato for using the Talon Mirage IOT based board with MangOH Red board.

  1. Updated the board with R13.3 image with the step below succesfully. Verified using “cm info” & “legato version”
    a. Created the .spk file with command “swicwe -o new_1.spk -c 9999999_9907152_SWI9X07Y_02.28.03.05_00_GENERIC_002.073_000.spk yocto_wp76xx.4k.cwe legato-19.02.0.cwe”
    b. Flashed using the command "swiflash -m “wp76xx” -i new_1.spk "

  2. Modified the legato source to disable the default wifi driver in that. Built as per the steps in the link provided.

  3. On the board bootup with the default image, flashed the updated legato source using the command “sudo ./bin/update red.wp76xx.update 192.168.2.2”. . the flashing was sucessful.

  4. After this board does not come up. It crashes continously and does not even go back to previously worked image.

Reboot / Crash Logs attached.

Request your help here. red.wp76xx.update_failed.txt (78.3 KB)

How about the image i attached?
If it still resets, you need to check if HSICENABLE is enabled in at!custom?

I dont get the board up at all. How to update the firmware if i dont get usb0 port.

There is no way to update if no usb port

Ok i got it up using the default 13.3 image.

Now tried to update with ur image, part1.rar. No luck.
Command :
sudo ./bin/update red.wp76xx.part1.update 192.168.2.2
[sudo] password for tjayaprakash:
Applying update from file ‘red.wp76xx.part1.update’ to device at address ‘192.168.2.2’.
Unpacking package: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
Unpacking package: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
Applying update: 100% ++++++++++++++++++++++++++++++++++++++++++++++++++
SUCCESS
Done

You mean it resets??? Or what???
Did you check if HSICENABLE is enabled in at!custom?

Not reset, the board does not come up, nor i get any interfaces other than USB0 to see the logs. The last log i sent was the log of the USB0 interface which has all the crash msgs.
Now i loaded back the 13.3 version of the image. Will check for the at command setting and post it in sometime.

You should get the uart debug log

HSICENABLE is 0x01 on the 13.3 version of image flashed.

!CUSTOM:
GPSENABLE 0x01
GPSLPM 0x01
IPV6ENABLE 0x01
UIM2ENABLE 0x01
SIMLPM 0x01
USBSERIALENABLE 0x01
SINGLEAPNSWITCH 0x01
TXONINDICATION 0x01
HSICENABLE 0x01
SCRUBEN 0x01
EXTGPSLNAEN 0x01
UIMAUTOSWITCH 0x01

OK

Manufacturer: Sierra Wireless, Incorporated
Model: WP7607
Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
IMEI: 359779080125194
IMEI SV: 6
FSN: VN842200670510
+GCAP: +CGSM

what do you see in the uart debug log?

This is the status of the 13.3 build. It boots up completely.

I have issue when i flash red.update file. There is no command prompt obtained over the debug uart port, hence i cant check the AT!CUSTOM output.

Log attached. red.wp76xx.update_failed.txt (78.3 KB)

you can type it in AT command port after it rolls back to original FW.

Not sure if this is crash reason:


Jan 6 00:00:29 swi-mdm9x28-wp user.err kernel: [ 27.238292] mangoh red mangoh red: battery gauge is missing
Jan 6 00:00:29 swi-mdm9x28-wp user.info kernel: [ 27.244402] mangoh red mangoh red: Removing mangoh red platform device


I don’t see such issue on my board, maybe you can try to debug in /linux_kernel_modules/mangoh/mangoh_red_board.c