# Firmware Update: Customer Config OK; Carrier Fails

**URL:** <https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80>\
**Category:** mangOH Green\
**Created:** [May 23, 2016, 9:06pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80 "2016-05-23T21:06:12Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\
**Post date:** [May 23, 2016, 9:06pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/1 "2016-05-23T21:06:12Z")

</div>

Continuing from earlier thread, as the forum won’t let me post any more in that thread - and suggests starting a new one:

> [@Firmware update](http://mangoh.discourse.group/t/firmware-update/54/13):
>
> at OK at!priid? PRI Part Number: 5501011 Revision: 01.15 Carrier PRI: 9999999\_9904559\_SWI9X15Y\_07.09.02.00\_00\_GENERIC\_001.019\_000 OK at!package? 9101011\_5501011\_WP8548-G\_06.03.55.00\_00\_DevKit\_001.006\_000 OK ati Manufacturer: Sierra Wireless, Incorporated Model: WP8548 Revision: SWI9X15Y\_07.09.02.00 r31541 CARMD-EV-FRMWR1 2016/03/31 20:05:28 IMEI: 359377060000865 IMEI SV: 41 FSN: LL516403850102 +GCAP: +CGSM OK At8 ERROR ati8 Legato Ver: 16.01.2\_9e91388c2b14980a4d419259910a4d…

Replies to questions from **asyal:**

> what version of mangoh are you using rev7 or rev8? Your module sku looks pretty old.  
> Can you do app status?

Yes, it’s quite old - one of the ones given out at the Sierra Wireless Developer Summit in Paris last year.

How would I check the mangOH Rev? Or “app status”?

> Can you download FW again and carrier again? This time with boot pin to ground for both the cases and post the image at completion at each time.

Sure - firmware:  
 ![](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/1X/9087e92774a644bd7e540289ce5c65b8c1bc92e3.png)

> Also post the at data I asked earlier again. Just want to double confirm everything is ok before you start

at  
OK

at!priid?  
PRI Part Number: 5501011  
Revision: 01.15

Carrier PRI: None

OK

at!package?  
9101011\_5501011\_WP8548\_07.09.02.00\_00\_DevKit\_001.015\_000

OK

ati  
Manufacturer: Sierra Wireless, Incorporated  
Model: WP8548  
Revision: SWI9X15Y\_07.09.02.00 r31541 CARMD-EV-FRMWR1 2016/03/31 20:05:28  
IMEI: 359377060000865  
IMEI SV: 41  
FSN: LL516403850102  
+GCAP: +CGSM

OK

ati8  
Legato Ver: 16.01.2\_9e91388c2b14980a4d419259910a4d65\_modified  
Yocto Ver: SWI9X15Y\_07.09.02.02 Fri Apr 15 02:39:24 PDT 2016  
OS Ver: Linux version 3.14.29ltsi-13c67b16ff\_922830eb31 (gsmbuild@CARMD-EV-FRMWR1) (gcc version 4.9.1 (GCC) ) #2 PREEMPT Fri Apr 15 02:38:16 PDT 2016  
LK Ver: 1.3.0\_a50272dbb2  
RootFS Ver: unknown  
UserFS Ver: unknown

OK

---

<div class="post-metadata">

**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\
**Post date:** [May 23, 2016, 9:06pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/2 "2016-05-23T21:06:57Z")

</div>

The forum would only allow me to put one image in the post. So here’s the 2nd screenshot

Carrier - still fails:  
 ![](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/1X/86dcd2850d97d5c0567018a54b142b858d5ee3e0.png)

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [May 23, 2016, 10:17pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/3 "2016-05-23T22:17:05Z")

</div>

Everything looks ok for both firmware and carrier download based on the at data you show here.  
I’ll need to check on that version of module as to the response we get for carrier download.

---

<div class="post-metadata">

**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\
**Post date:** [May 24, 2016, 9:37am UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/4 "2016-05-24T09:37:25Z")

</div>

OK - so it’s actually worked?

Great!

😁

---

<div class="post-metadata">

**Author:** ![svuong](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@svuong](https://mangoh.discourse.group/u/svuong)\
**Post date:** [May 25, 2016, 9:43pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/5 "2016-05-25T21:43:29Z")

</div>

FDT error code 4 means the tool failed to communicate with the module.

The boot pin appeared to be used to start the update (not sure why). The boot pin must be de-asserted to allow the module to start-up properly. If the pin assertion was not removed in time for FDT to perform a sanity check after update, the error will be thrown.

---

<div class="post-metadata">

**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\
**Post date:** [May 26, 2016, 5:26pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/6 "2016-05-26T17:26:10Z")

</div>

So if I had flipped the switch at the point where it said “Resetting device …” it might all have worked without reporting any error?

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [May 26, 2016, 6:08pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/7 "2016-05-26T18:08:17Z")

</div>

It should have but you reported it didnt. Either way, you are good to go.  
Can you connect to a cell network?

---

<div class="post-metadata">

**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\
**Post date:** [May 26, 2016, 6:41pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/8 "2016-05-26T18:41:37Z")

</div>

But I wasn’t flipping the switch back; if it was in the instructions, I missed that bit.

But, yes; it connects to the cell network - I have the SMS demo working.

😁

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [May 26, 2016, 6:42pm UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/9 "2016-05-26T18:42:55Z")

</div>

> [@awneil](#):
>
> g.

🙂 Everything seems to be working for you.

---

<div class="post-metadata">

**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\
**Post date:** [March 6, 2017, 5:19am UTC](https://mangoh.discourse.group/t/firmware-update-customer-config-ok-carrier-fails/80/10 "2017-03-06T05:19:46Z")

</div>


