# WP7504 Keeps reseting on mangOH Red but not on mangOH Green **URL:** \ **Category:** mangOH Red\ **Created:** [September 28, 2017, 3:25pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771 "2017-09-28T15:25:47Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![hjordan](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@hjordan](https://mangoh.discourse.group/u/hjordan)\ **Post date:** [September 28, 2017, 3:25pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/1 "2017-09-28T15:25:47Z")
I am trying to use a WP7504 with the Red mangOH board. When I power up the board, the USB ports load on the PC, but after about 5 seconds they disconnect and reconnect after about 5 more seconds. This cycle continues until I remove power. I am seeing all this in Device Manager. The chip has the latest firmware, as I just loaded it using a Green mangOH board. It works fine with the Green board and the same PC. I have tried a WP8548 on both the Red and Green boards and it works fine. Is there something different with the Red board that would make the chip continually reset? Any suggestion or help would be appreciated. Thanks. ---
**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\ **Post date:** [September 28, 2017, 8:52pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/2 "2017-09-28T20:52:51Z")
Try connecting the console USB port when you are booting the mangOH Red board so that you can observe the boot messages. Paste them into this post if you see anything suspicious. ---
**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:** [September 28, 2017, 10:39pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/3 "2017-09-28T22:39:08Z")
There is no reason for this issue, so as David said we will need to look at the logs. we have used WP7504 over mangoh red with no issues ---
**Author:** ![hjordan](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@hjordan](https://mangoh.discourse.group/u/hjordan)\ **Post date:** [September 29, 2017, 7:47pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/4 "2017-09-29T19:47:01Z")
Thanks for your replys. I connected to the console USB port and compared the boot messages of the WP8548 and the WP7504. Everything is similar until it gets to the “Legato start sequence”. The WP7504 is displaying the following Starting qmuxd… [19.199633] mangoh: created device for board green dv4 [19.227651] mangoh mangoh green dv4: Probing mangOH platform device [19.403815] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c8, irq:187 [19.409552] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected Finished Legato start Sequence After this, the WP7504 tries to handle a multiplexed I2C bus and fails. I have since loaded the the latest firmware (Release 14) from Sierra using the Windows EXE on the Red board. The boot sequence is still displaying that it was created for the Green board. Any ideas how to change this? ---
**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\ **Post date:** [September 29, 2017, 7:52pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/5 "2017-09-29T19:52:30Z")
The 0x3a not connected message is a red herring. Can you show me more logs after this. Specifically you said that the multiplexed i2c bus fails. ---
**Author:** ![hjordan](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@hjordan](https://mangoh.discourse.group/u/hjordan)\ **Post date:** [September 29, 2017, 9:00pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/6 "2017-09-29T21:00:40Z")
Here is the latest boot sequence that I recorded. It continues with an additional couple of pages starting with \_UNKNOWN Starting netmgrd: done Starting pm: done net.ipv4.conf.default.rp\_filter = 1 net.ipv4.conf.all.rp\_filter = 1 starting DNS forwarder and DHCP server: dnsmasq… done. Starting Dropbear SSH server: DONE dropbear. Starting adbd: stopping DNS forwarder and DHCP server: dnsmasq… stopped /usr/bin/dnsmasq (pid 552) done. done starting DNS forwarder and DHCP server: dnsmasq… Starting mbimd: [22.141065] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c8, irq:187 [22.146772] qup\_i2c qup\_i2c.0: I2C slave addr:0x3a not connected done Starting linkmon: done. [22.302029] adb\_open [22.317533] IPv6: ADDRCONF(NETDEV\_UP): usb0: link is not ready done run\_getty.sh: ttyHSL1 reserved for CONSOLE Poky (Yocto Project Reference Distro) 1.7.3 swi-mdm9x15 /dev/ttyHSL1 swi-mdm9x15 login: [22.623622] mbim\_open: Open mbim driver [22.626461] mbim\_open: Lock mbim\_dev-\>open\_excl for open [22.633236] mbim\_open: USB cable not connected [22.636654] mbim\_open: Exit, mbim file opened [22.645170] mbim\_read: Requests list is empty. Wait. [25.080909] i2c i2c-0: Added multiplexed i2c bus 1 [25.101083] i2c i2c-0: Added multiplexed i2c bus 2 [25.130932] i2c i2c-0: Added multiplexed i2c bus 3 [25.146101] i2c i2c-0: Added multiplexed i2c bus 4 [25.200885] i2c i2c-0: Added multiplexed i2c bus 5 [25.227437] i2c i2c-0: Added multiplexed i2c bus 6 [25.250633] i2c i2c-0: Added multiplexed i2c bus 7 [25.270837] i2c i2c-0: Added multiplexed i2c bus 8 [25.274652] pca954x 0-0071: registered 8 multiplexed busses for I2C switch pca9548 [25.297115] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187 [25.302914] qup\_i2c qup\_i2c.0: I2C slave addr:0x6a not connected [25.308713] lsm6ds3 0-006a: failed to read Who-Am-I register. [25.315244] lsm6ds3: probe of 0-006a failed with error -107 [28.744208] gpio\_sync\_ri: RI owner is Modem [28.800549] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1363c8, irq:187 [28.806256] qup\_i2c qup\_i2c.0: I2C slave addr:0x3f not connected [32.364748] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c8, irq:187 [32.370975] qup\_i2c qup\_i2c.0: I2C slave addr:0x3f not connected [35.660247] smd\_pkt\_open: wait on smd\_pkt\_dev\_msm id:0 allocation failed rc:-110 Sep 29 17:51:51 swi-mdm9x15 user.warn Legato: -WRN- | _UNKNOWN_[741]/framework T=main | LE\_FILENAME le\_ref\_CreateMap() 149 | Map name ‘refmangoh\_gpioExp3Pin3\_ServerHandlers’ truncated to ‘refmangoh\_gpioExp3Pin3\_ServerHa’. Sep 29 17:51:51 swi-mdm9x15 user.warn Legato: -WRN- | _UNKNOWN_[741]/framework T=main | LE\_FILENAME VerifyUniquenessOfName() 489 | Multiple memory pools share the same name ‘framework.hashMap\_refmangoh\_gpi’. This will become illegal in future releases. Sep 29 17:51:51 swi-mdm9x15 user.warn Legato: -WRN- | _UNKNOWN_[741]/framework T=main | LE\_FILENAME le\_ref\_CreateMap() 149 | Map name ‘refmangoh\_gpioExp3Pin4\_ServerHandlers’ truncated to ‘refmangoh\_gpioExp3Pin4\_ServerHa’. Sep 29 17:51:51 swi-mdm9x15 user.warn Legato: -WRN- | _UNKNOWN_[741]/framework T=main | LE\_FILENAME VerifyUniquenessOfName() 489 | Multiple memory pools share the same name ‘framework.hashMap\_refmangoh\_gpi’. This will become illegal in future releases. Sep 29 17:51:51 swi-mdm9x15 user.warn Legato: -WRN- | _UNKNOWN_[741]/framework T=main | LE\_FILENAME le\_ref\_CreateMap() 149 | Map name ‘refmangoh\_gpioExp3Pin5\_ServerHandlers’ truncated to ‘refmangoh\_gpioExp3Pin5\_ServerHa’. ---
**Author:** ![hjordan](https://avatars.discourse-cdn.com/v4/letter/h/ba8739/32.png) [@hjordan](https://mangoh.discourse.group/u/hjordan)\ **Post date:** [September 29, 2017, 9:01pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/7 "2017-09-29T21:01:12Z")
After the last \_UKNOWN it has this Sep 29 17:51:52 swi-mdm9x15 [user.info](http://user.info) Legato: INFO | gpioService[684]/sysfsGpio T=main | gpioSysfsUtils.c gpioSysfs\_SessionOpenHandlerFunc() 1104 | Assigning GPIO 2 Sep 29 17:51:52 swi-mdm9x15 user.warn Legato: -WRN- | _UNKNOWN_[741]/framework T=main | LE\_FILENAME le\_fdMonitor\_Create() 672 | FD Monitor object name ‘gpioExpanderService.gpioExpanderGreen.expander2Interrupt’ truncated to ‘gpioExpanderService.gpioExpande’. Sep 29 17:51:52 swi-mdm9x15 user.err kernel: [32.364748] qup\_i2c qup\_i2c.0: QUP: I2C status flags :0x1300c8, irq:187 Sep 29 17:51:52 swi-mdm9x15 user.err Legato: =ERR= | gpioExpanderService[741]/gpioExpanderCommon T=main | gpioExpander.c SmbusWriteReg() 1002 | smbus write failed with error -1 Sep 29 17:51:52 swi-mdm9x15 user.emerg Legato: _EMR_ | gpioExpanderService[741]/gpioExpanderCommon T=main | gpioExpander.c gpioExpander\_Reset() 779 | Failed to reset GPIO expander on I2C bus 6 at address 0x3f Sep 29 17:51:52 swi-mdm9x15 user.err kernel: [32.370975] qup\_i2c qup\_i2c.0: I2C slave addr:0x3f not connected Sep 29 17:51:53 swi-mdm9x15 [user.info](http://user.info) Legato: INFO | gpioService[684]/sysfsGpio T=main | gpioSysfsUtils.c gpioSysfs\_SessionCloseHandlerFunc() 1143 | Releasing GPIO 2 Sep 29 17:51:53 swi-mdm9x15 [user.info](http://user.info) Legato: INFO | supervisor[452]/supervisor T=main | proc.c proc\_SigChildHandler() 1986 | Pro[36.775400] reboot: Restarting system cess ‘gpioExpanderService’ (PID: 741) has exited with exit code [36.781535] Going down for rest ---
**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\ **Post date:** [September 29, 2017, 9:43pm UTC](https://mangoh.discourse.group/t/wp7504-keeps-reseting-on-mangoh-red-but-not-on-mangoh-green/771/8 "2017-09-29T21:43:07Z")
The module has the mangOH Green SDEF on it. I can tell because it’s creating 8 virtual i2c buses rather than 4 (expected on the red) also it’s loading the lsm6ds3 module for the accelerometer which is on the green and not the red. If it’s stuck in a loop, you can revert back to the WP team’s release 14 by using swiflash (from linux) or the EXE upgrade file from [source.sierrawireless.com](http://source.sierrawireless.com) under the wp85 or 75 page. Once that’s done, you can build and install the mangOH Red sdef and install that system.