# MangOH red board unable to update image

**URL:** <https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543>\
**Category:** mangOH Red\
**Created:** [June 1, 2020, 7:18am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543 "2020-06-01T07:18:04Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 1, 2020, 7:18am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/1 "2020-06-01T07:18:04Z")

</div>

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](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:~#

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 1, 2020, 7:26am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/2 "2020-06-01T07:26:44Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 1, 2020, 8:08am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/3 "2020-06-01T08:08:46Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 1, 2020, 8:19am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/4 "2020-06-01T08:19:38Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 1, 2020, 9:28am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/5 "2020-06-01T09:28:30Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 1, 2020, 9:40am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/6 "2020-06-01T09:40:00Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 1, 2020, 11:25am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/7 "2020-06-01T11:25:59Z")

</div>

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](https://mangoh.discourse.group/uploads/short-url/sUYyaDxpitP3BbHpql5jPOuuxA8.txt) (45.9 KB)

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 1, 2020, 11:41am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/8 "2020-06-01T11:41:26Z")

</div>

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

> [@Couldn't find file 'io.api'](https://mangoh.discourse.group/t/couldnt-find-file-io-api/4495):
>
> hello, Trying out sample app RedSensorToCloud on MangoH red for wp7608 with SDK for WP76 (Release 13.3 + Legato 20.04.0) while mkapp following error popping up myWorkspace/apps/RedSensorToCloud/components/avPublisher/Component.cdef:6:17: error: Couldn’t find file ‘io.api’. in my legatoAF I can locate io.api at apps/sample/datahub Pardon my understanding as I am just a beginner Thanks in advance.

Or you can use my update file based on R13.3.  
[red.wp76xx.part2.rar](https://mangoh.discourse.group/uploads/short-url/d9eSiOKkA98MEKGyZAnZ3kVg1o1.rar) (2.7 MB) [red.wp76xx.part1.rar](https://mangoh.discourse.group/uploads/short-url/z6HXb3b3mPqAIkOHXy30qhd2gNY.rar) (4 MB)

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 2, 2020, 10:56am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/9 "2020-06-02T10:56:09Z")

</div>

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](https://mangoh.discourse.group/uploads/short-url/fw5tHvzBcEC1TVVaDjsH32gDLRd.txt) (78.3 KB)

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 2, 2020, 11:27am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/10 "2020-06-02T11:27:52Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 2, 2020, 12:26pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/11 "2020-06-02T12:26:38Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 2, 2020, 12:34pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/12 "2020-06-02T12:34:20Z")

</div>

There is no way to update if no usb port

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 2, 2020, 12:58pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/13 "2020-06-02T12:58:30Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 2, 2020, 1:13pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/14 "2020-06-02T13:13:46Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 2, 2020, 1:26pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/15 "2020-06-02T13:26:42Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 2, 2020, 1:35pm UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/16 "2020-06-02T13:35:37Z")

</div>

You should get the uart debug log

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 4, 2020, 6:23am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/17 "2020-06-04T06:23:18Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 4, 2020, 6:49am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/18 "2020-06-04T06:49:26Z")

</div>

what do you see in the uart debug log?

---

<div class="post-metadata">

**Author:** ![tejaswisj](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@tejaswisj](https://mangoh.discourse.group/u/tejaswisj)\
**Post date:** [June 4, 2020, 7:43am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/19 "2020-06-04T07:43:08Z")

</div>

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](https://mangoh.discourse.group/uploads/short-url/fw5tHvzBcEC1TVVaDjsH32gDLRd.txt) (78.3 KB)

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)\
**Post date:** [June 4, 2020, 8:08am UTC](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543/20 "2020-06-04T08:08:23Z")

</div>

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

[Next page](https://mangoh.discourse.group/t/mangoh-red-board-unable-to-update-image/4543.md?page=2)