# Error executing mux

**URL:** <https://mangoh.discourse.group/t/error-executing-mux/61>\
**Category:** mangOH Green\
**Created:** [May 16, 2016, 6:58am UTC](https://mangoh.discourse.group/t/error-executing-mux/61 "2016-05-16T06:58:12Z")\
**Posts on this page:** 16\
**Page:** 2

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 19, 2016, 4:15am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/21 "2016-05-19T04:15:43Z")

</div>

Hello Ashish,  
Confirmed version 7 after rail removed.

root@swi-mdm9x15:~# dmesg|grep i2c  
[0.184800] unmatched machine ID in register\_i2c\_devices  
[0.971341] swimcu\_i2c\_init: start  
[0.974637] swimcu\_i2c\_probe: start 1  
[0.986906] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[0.993285] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.003448] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187  
[1.009064] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.025179] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.030795] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.046909] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.052495] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.068640] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.074256] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.090370] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.095956] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.743171] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.748878] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.758950] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187  
[1.764565] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.776010] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.781687] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.791545] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187  
[1.797161] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.808393] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.814008] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.825667] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187  
[1.831344] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[2.041873] wm8944\_i2c\_init  
[2.041965] wm8944\_i2c\_probe  
[2.049076] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187  
[2.058263] qup\_i2c qup\_i2c.0: I2C slave addr:0x1a not connected  
[2.088631] i2c-core: driver [tabla-i2c-core] using legacy suspend method  
[2.094368] i2c-core: driver [tabla-i2c-core] using legacy resume method  
[2.837356] i2c /dev entries driver  
[14.687501] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x11143c8, irq:187  
[14.694185] qup\_i2c qup\_i2c.0: I2C slave addr:0x10 not connected

root@swi-mdm9x15:~# app status  
[running] arduinoBridge  
[running] audioService  
[running] avcService  
[running] cellNetService  
[running] dataConnectionService  
[running] dataRouter  
[running] fwupdateService  
[stopped] gpioExpanderDemo  
[running] gpioService  
[running] modemService  
[running] mqttClient  
[running] muxCtrlService  
[stopped] muxCtrlTools  
[running] positioningService  
[running] powerMgr  
[running] secStore  
[stopped] smsInboxService  
[stopped] tools  
[stopped] voiceCallService  
[stopped] wifi  
[stopped] wifiApTest  
[stopped] wifiClientTest  
[running] wifiService  
[stopped] wifiWebAp  
root@swi-mdm9x15:~#

Seem like gpioExpanderService disappear again. ???

Best regards,  
CSLEE

---

<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 19, 2016, 9:19pm UTC](https://mangoh.discourse.group/t/error-executing-mux/61/22 "2016-05-19T21:19:46Z")

</div>

Here is the system file which works on my target. Please try this and lets take it from there:

[https://drive.google.com/file/d/0B0lsYcy39bEldWFocjZDeVNENGs/view?usp=sharing](https://drive.google.com/file/d/0B0lsYcy39bEldWFocjZDeVNENGs/view?usp=sharing)

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 12:15am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/23 "2016-05-20T00:15:52Z")

</div>

Hello Ashish,

Update my mangOH with your system file.

it rebooted 4 times, same as using my system file.

root@swi-mdm9x15:~# dmesg|grep i2c  
[0.185472] unmatched machine ID in register\_i2c\_devices  
[0.974149] swimcu\_i2c\_init: start  
[0.977414] swimcu\_i2c\_probe: start 1  
[0.989684] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[0.996093] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.006226] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c4, irq:187  
[1.016236] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.021852] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.037997] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187  
[1.043613] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.059728] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.065344] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.081458] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.087044] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.733740] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c4, irq:187  
[1.741095] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.746711] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.758187] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c4, irq:187  
[1.765542] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c4, irq:187  
[1.772867] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1343c8, irq:187  
[1.778483] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[1.789500] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187  
[1.795116] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected  
[2.023409] wm8944\_i2c\_init  
[2.023531] wm8944\_i2c\_probe  
[2.023805] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c4, irq:187  
[2.059667] i2c-core: driver [tabla-i2c-core] using legacy suspend method  
[2.065588] i2c-core: driver [tabla-i2c-core] using legacy resume method  
[2.808637] i2c /dev entries driver  
[14.710392] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x11143c8, irq:187  
[14.716282] qup\_i2c qup\_i2c.0: I2C slave addr:0x10 not connected

root@swi-mdm9x15:~# app status  
[running] arduinoBridge  
[running] audioService  
[running] avcService  
[running] cellNetService  
[running] dataConnectionService  
[running] dataRouter  
[running] fwupdateService  
[stopped] gpioExpanderDemo  
[running] gpioService  
[running] modemService  
[running] mqttClient  
[running] muxCtrlService  
[stopped] muxCtrlTools  
[running] positioningService  
[running] powerMgr  
[running] secStore  
[stopped] smsInboxService  
[stopped] tools  
[stopped] voiceCallService  
[stopped] wifi  
[stopped] wifiApTest  
[stopped] wifiClientTest  
[running] wifiService  
[stopped] wifiWebAp

gpioExpanderService still missing!!

Best regards,  
CSLEE

---

<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 20, 2016, 12:23am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/24 "2016-05-20T00:23:07Z")

</div>

ok…so obviously it is not system definition file.  
**There is no reason for 4 the times reboot. That shouldnt happen.**

Can you tell me the SKU# of your module?  
Can you attach your complete log file?  
Can you make sure that firmware is properly downloaded to your unit?

---

<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 20, 2016, 12:41am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/25 "2016-05-20T00:41:05Z")

</div>

can you also run the following AT commands:  
root@swi-mdm9x15:~# microcom -E /dev/ttyAT

AT!PACKAGE?  
AT!PRIID?  
ati  
ati8

ctrl+X to get out

also run in linux:  
root@swi-mdm9x15:~# ls /dev/i2c-0  
/dev/i2c-0

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 1:24am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/26 "2016-05-20T01:24:12Z")

</div>

Hello Ashish,

login as: root  
Linux swi-mdm9x15 3.14.29ltsi-13c67b16ff\_922830eb31 #2 PREEMPT Fri Apr 15 02:38:16 PDT 2016 armv7l GNU/Linux  
root@swi-mdm9x15:~# microcom -E /dev/ttyAT  
AT!ENTERCND="A710"  
OK  
AT!SKU?  
SKU: 1102816

OK  
AT!PACKAGE?  
1102816\_9905383\_WP8548\_07.08.02.00\_00\_Generic\_001.002\_000

OK  
AT!PRIID?  
PRI Part Number: 9905383  
Revision: 01.04

Carrier PRI: 9999999\_9904559\_SWI9X15Y\_07.09.02.00\_00\_GENERIC\_001.019\_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: 359377060011672  
IMEI SV: 41  
FSN: LL540300070203  
+GCAP: +CGSM,+DS,+ES

OK  
ati8  
Legato Ver: 16.01.2\_38e3f9b51e83d1f5347fec58e0ee6a52\_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

The download of FW is following the procedure that you’ve attached in your previous email.  
As for the log file, I do it later.  
Best regards,  
CSLEE

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 1:33am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/27 "2016-05-20T01:33:48Z")

</div>

Hello Ashish,

The log file:  
[https://drive.google.com/file/d/0BxmbKQmHXSZAdVlkTVNoMUJlcFE/view?usp=sharing](https://drive.google.com/file/d/0BxmbKQmHXSZAdVlkTVNoMUJlcFE/view?usp=sharing)

Best regards,  
CSLEE

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 1:47am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/28 "2016-05-20T01:47:01Z")

</div>

Hello Ashish,  
I am using a windows laptop to download my firmware via USB.  
I have another laptop running Ubuntu. Is there another way to download the firmware using Ubuntu?  
I want to eliminate the possibilities of corrupted file download by windows systems.  
Best regards,  
CSLEE

---

<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 20, 2016, 1:53am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/29 "2016-05-20T01:53:17Z")

</div>

Hi CS,  
Can you also do the following:  
a. power off the board  
b. use the removal tool, to remove the cover  
c. re-insert the module  
d. put back the cover  
I am wondering if the module is properly inserted or not.

Also, take a multimeter and check the impedance you measure on pins 9 & 11 of CN602 before removal and after re-inserting the module.

cheers,  
Ashish

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 2:28am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/30 "2016-05-20T02:28:10Z")

</div>

Ashish,  
Before removal is about 3.800KOhm and after removal is about 287KOhm and increasing.  
Power on, still reboot for 4 times. It did not solve the problem.  
Best regards,  
CSLEE

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 2:29am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/31 "2016-05-20T02:29:26Z")

</div>

Ashish,  
It seem like download firmware only using windows. Any alternative?  
Best regards,  
CSLEE

---

<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 20, 2016, 2:41am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/32 "2016-05-20T02:41:07Z")

</div>

looking at the log files, seem like cant find 0x71 I2C buffer (U701).  
Can you check if there is anything wrong in that area?

Based on what you sent Windows download looks fine to me.

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 5:00am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/33 "2016-05-20T05:00:13Z")

</div>

Hi Ashish,  
Found the IC see attached.

 ![](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/1X/66eeab72fbacc9c4aed515e70f8ceab8392e5aec.JPG)  
What can I do with it? Check short/open trace?  
Best regards,  
CSLEE

edit: Seem all solder ok under magnifying glass.

---

<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 20, 2016, 5:10am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/34 "2016-05-20T05:10:12Z")

</div>

Can you do a short test between:  
CN602-9 & U701-20  
CN602-11 & U701-19

It could be there is a problem with this part (whether improperly soldered, damaged by handling etc.).

---

<div class="post-metadata">

**Author:** ![cslee](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cslee](https://mangoh.discourse.group/u/cslee)\
**Post date:** [May 20, 2016, 5:27am UTC](https://mangoh.discourse.group/t/error-executing-mux/61/35 "2016-05-20T05:27:31Z")

</div>

Hi Ashish,  
Connection OK. (from a little help from a co-worker and tiny little pin).  
CN602-9 & U701-20 are connected (~2 Ohms)  
CN602-11 & U701-19 are connected (~2 Ohms)  
Both are not shorted together.  
Best regards,  
CSLEE

---

<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/error-executing-mux/61/36 "2017-03-06T05:19:26Z")

</div>

Closed on March 6, 2017, 5:19am UTC



[Previous page](https://mangoh.discourse.group/t/error-executing-mux/61.md?page=1)
