# Unable to communicate with WP7603 **URL:** \ **Category:** WP Series\ **Created:** [March 7, 2018, 4:16pm UTC](https://forum.sierrawireless.com/t/unable-to-communicate-with-wp7603/12203 "2018-03-07T16:16:09Z")\ **Posts on this page:** 3\ **Page:** 1

**Author:** ![HDe2OA](https://avatars.discourse-cdn.com/v4/letter/h/8491ac/32.png) [@HDe2OA](https://forum.sierrawireless.com/u/HDe2OA)\ **Post date:** [March 7, 2018, 4:16pm UTC](https://forum.sierrawireless.com/t/unable-to-communicate-with-wp7603/12203/1 "2018-03-07T16:16:09Z")

Hi All, I recently received a mangOH Red, and installed a WP7603-1 module into it. I have been unable to ping or get any sort of response from the module while trying to build/update it. However, I did swap power over to the console, and saw the following read out during boot. Do these have different IP’s than the WPx5xx series? Or is there something else going on here? I appreciate the help. [code]Welcome to minicom 2.7 OPTIONS: I18n Compiled on Feb 7 2016, 13:37:27. Port /dev/ttyUSB0, 08:00:52 Press CTRL-A Z for help on special keys [930] DEBUG: cmdline has root= [1070] Channel alloc freed [0.000000] GIC CPU mask not found - kernel will fail to boot. [0.000000] GIC CPU mask not found - kernel will fail to boot. [0.000000] MPM 1 irq mapping errored -517 [0.071968] sierra:-sierra\_smem\_get\_factory\_mode-failed: smem have not initid [0.213723] spmi\_pmic\_arb 200f000.qcom,spmi: PMIC Arb Version-2 0x20010000 [0.227472] msm\_mpm\_dev\_probe(): Cannot get clk resource for XO: -517 [0.230395] smd\_channel\_probe\_now: allocation table not initialized [0.237533] msm\_thermal:msm\_thermal\_dev\_probe Failed reading node=/soc/qcom,7 [0.263752] msm\_mpm\_dev\_probe(): Cannot get clk resource for XO: -517 [0.266473] msm\_thermal:get\_kernel\_cluster\_info CPU0 topology not initialize. [0.267383] cpu cpu0: dev\_pm\_opp\_get\_opp\_count: device OPP not found (-19) [0.267401] msm\_thermal:get\_cpu\_freq\_plan\_len Error reading CPU0 freq table 9 [0.268112] cpu cpu0: dev\_pm\_opp\_get\_opp\_count: device OPP not found (-19) [0.268127] msm\_thermal:get\_cpu\_freq\_plan\_len Error reading CPU0 freq table 9 [0.268142] cpu cpu0: dev\_pm\_opp\_get\_opp\_count: device OPP not found (-19) [0.268154] msm\_thermal:get\_cpu\_freq\_plan\_len Error reading CPU0 freq table 9 [0.359437] AXI: msm\_bus\_scale\_register\_client(): msm\_bus\_scale\_register\_cli. [0.362016] AXI: msm\_bus\_scale\_register\_client(): msm\_bus\_scale\_register\_cli0 [0.412791] msm\_bus\_fabric\_init\_driver [0.600305] SWI ssmem\_framework\_init: SSMEM init OK [0.620963] scm\_call failed with error code -4 [0.620982] msm\_audio\_protect\_memory\_region: SCM call failed, scm\_call\_ret -0 [0.625621] uart\_tx\_gpio is not available [0.625640] uart\_rx\_gpio is not available [0.625659] uart\_cts\_gpio is not available [0.625677] uart\_rfr\_gpio is not available [0.626319] sps: BAM device 0x07884000 is not registered yet. [0.631535] AXI: get\_pdata(): Error: Client name not found [0.631545] AXI: msm\_bus\_cl\_get\_pdata(): client has to provide missing entryn [0.631553] msm\_serial\_hsl\_probe: Bus scaling is disabled [0.841812] mdm9607-pinctrl 1000000.pinctrl: pin GPIO\_4 already requested byl [0.852301] mdm9607-pinctrl 1000000.pinctrl: pin-4 (78b0000.serial) status -2 [0.859444] mdm9607-pinctrl 1000000.pinctrl: could not request pin 4 (GPIO\_4l [0.870417] msm\_serial\_hsl 78b0000.serial: Error applying setting, reverse tk [0.926675] sps: BAM device 0x07984000 is not registered yet. [1.011280] unable to find DT imem DLOAD mode node [1.015332] unable to find DT imem EDLOAD mode node [1.020293] unable to find DT imem dload-type node [1.024839] Failed to disable secure wdog debug: -4 [1.055910] devfreq soc:qcom,cpubw: Couldn’t update frequency transition inf. [1.063917] sdhci\_msm 7864900.sdhci: sdhci\_msm\_pm\_qos\_parse\_irq: error -22 ru [1.071928] i2c-msm-v2 78b8000.i2c: msm\_bus\_scale\_register\_client(mstr-id:86) [1.153575] bmi160 4-0068: BMI160 qpio number:78 [1.169178] mdm9607-pinctrl 1000000.pinctrl: pin GPIO\_79 already requested bc [1.215146] mdm9607-pinctrl 1000000.pinctrl: pin-79 (soc:qcom,msm-dai-mi2s:q2 [1.239769] mdm9607-pinctrl 1000000.pinctrl: could not request pin 79 (GPIO\_l [1.267317] msm-dai-q6-mi2s soc:qcom,msm-dai-mi2s:qcom,msm-dai-q6-mi2s-sec: k [1.316976] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm\_asoc\_machine\_pro0 [1.365267] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm\_asoc\_machine\_pro0 [1.408652] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm\_asoc\_machine\_pro0 [1.442210] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm\_asoc\_machine\_pro0 [1.451025] calculate\_residency: residency \< 0 for LPM [1.455126] parse\_cpu\_levels: idx 1 420 [1.458943] calculate\_residency: residency \< 0 for LPM [1.503918] parse\_cpu\_levels: idx 2 500 [1.506723] parse\_cpu\_levels: idx 2 3040 [1.532713] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm\_asoc\_machine\_pro0 [1.552015] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm\_asoc\_machine\_pro) Non-secure. UBI device number 0, total 120 LEBs (30474240 bytes, 29.1 MiB), available 5 LEB) [7.094052] device-mapper: table: 253:0: verity: Cannot initialize hash funcn device-mapper: reload ioctl failed: No such file or directory Device: rt ubiImgBlock:/dev/ubiblock0\_0 hashBlock:/dev/ubiblock0\_1 root\_hash:40636ee2e72095cf3974f93617bb07dc12cf9038a4a713b1261c7094c341114e Dm-verity partition creation failed. rootfs: dev ‘/dev/ubiblock0\_0’ ‘squashfs’ rootfs: mounting took 10ms init started: BusyBox v1.22.1 (2017-07-01 02:04:23 UTC) rcS: Executing mount\_essential\_fs… rcS: Executing simple\_network… rcS: Executing run\_S\_scripts… S02mount\_early: Executing mount\_early\_pseudo… S02mount\_early: Executing mount\_early\_other… S02mount\_early: Executing mount\_early\_create\_dirs… S02mount\_early: Executing mount\_early\_user\_start… S02mount\_early: User is forcing userapp file system to be ubifs. S02mount\_early: Trying to mount UBIFS on /mnt/flash using [usrquota,grpquota,rw. S02mount\_early: UBI: mtd 16 is UBI. UBI device number 3, total 524 LEBs (133070848 bytes, 126.9 MiB), available 5 L) S02mount\_early: Performing quota check on file system mounted at /mnt/flash S02mount\_early: UBIFS volume successfully mounted on /mnt/flash S02mount\_early: Executing mount\_early\_legato\_start… Can’t get valid SMEM, init DSSD SMEM Linux sub system 1 mount Legato from partition lefwkro UBI device number 2, total 35 LEBs (8888320 bytes, 8.5 MiB), available 0 LEBs () S02mount\_early: Non-secure ! S02mount\_early: UBI: mtd 14 is UBI. S02mount\_early: SQUASHFS successfully mounted on /mnt/legato S02mount\_early: Executing mount\_early\_userrw\_start… S02mount\_early: Mounting swirw file system as UBIFS S02mount\_early: Trying to mount UBIFS on /mnt/userrw using [usrquota,grpquota,r. S02mount\_early: UBI: mtd 15 is UBI. UBI device number 4, total 100 LEBs (25395200 bytes, 24.2 MiB), available 2 LEB) S02mount\_early: Performing quota check on file system mounted at /mnt/userrw S02mount\_early: UBIFS volume successfully mounted on /mnt/userrw S02mount\_early: swirw mounted to /mnt/userrw S03confighw.sh: Kernel internal entropy pool filler is available, increasing wr2 S04mount\_unionfs: RO rootfs fudge allowed. Mounting local filesystems… [15.199009] UBIFS error (pid: 433): cannot open “ubi0:usrfs”, error -19mounte MTD : Detected block device : /firmware for modem UBI device number 1, total 128 LEBs (32505856 bytes, 31.0 MiB), available 0 LEB) Initializing random number generator… Switching to composition sierra\_dev (1199:68C0) [16.033396] enable\_store: android\_usb: already disabled Configuring network interfaces… done. Starting syslogd/klogd: done ifconfig: SIOCGIFFLAGS: No such device Starting diagrebootapp: done $Starting qcom\_time: starting time-daemon Starting time\_services: done Legato start sequence restart\_at\_uart: Mapped UART1 for AT service Finished Legato start Sequence Starting reboot daemon: done Starting atreset: done Starting modem dependent daemons: [26.820989] M-Notify: General: 7 [26.863612] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ror [26.896865] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ror [26.927077] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ror [27.008516] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ror [27.023877] diag: In diag\_send\_feature\_mask\_update, control channel is not oc [27.185745] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ror [27.238051] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: no source widgetX [27.286511] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ro3 [27.332965] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ror [27.367045] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add ror [27.402773] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: no sink widget fX [27.427716] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add roX Load modem done Starting qmuxd: done Starting thermal-engine: done Starting irsc\_util: Starting irsc tool Failed to open file:/etc/sec\_config Absent/Invalid config,Default rules apply Ending irsc tool done Starting netmgrd: done Starting powerconfig for mdm9607: Starting fs-scrub-daemon: done net.ipv4.conf.default.rp\_filter = 1 net.ipv4.conf.all.rp\_filter = 1 [28.539606] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: mux SLIM\_0\_RX AAs rm: can’t remove ‘/var/log/wtmp’: No such file or directory Starting qmi\_ip: done [28.728441] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-dtmf-txX [28.785525] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its p0 [28.925492] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-dtmf-txX starting DNS forwarder and DHCP server: dnsmasq… [29.056932] msm-dai-stub-X [29.122426] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-rxX [29.189188] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-rxX done. [29.256558] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-rxK Starting Dropbear SSH server: [29.330458] msm-dai-stub-dev soc:qcom,msm-dai-X DONE [29.385035] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-txX [29.442684] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-txX dropbear. stopping DNS forwarder and DHCP server: dnsmasq… [29.510583] msm-dai-stub-K stopped /usr/bin/dnsmasq (pid 968) done. starting DNS forwarder and DHCP server: dnsmasq… done. run\_getty.sh: ttyHSL1 reserved for CONSOLE Poky (Yocto Project Reference Distro) 1.7.3 swi-mdm9x28 /dev/ttyHSL1 swi-mdm9x28 login:[/code] [Console\_Output.txt](https://forum.sierrawireless.com/uploads/short-url/hNCQlP7eu9ooRZf8Iu43n9M5JIP.txt) (9.72 KB) ---

**Author:** ![rkirk](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@rkirk](https://forum.sierrawireless.com/u/rkirk)\ **Post date:** [March 10, 2018, 12:32am UTC](https://forum.sierrawireless.com/t/unable-to-communicate-with-wp7603/12203/2 "2018-03-10T00:32:48Z")

I’m guessing you’re looking for the USB ECM interface, and it looks like you have an older release, with your Busybox compile date putting you back at around Release 4 (July 2017). There have been a few quirks in older releases, but in Release 6.1 and newer the interface should match WPx5 with 192.168.2.2 by default. Some of the issues with older releases, from the CRN (here [source.sierrawireless.com/resou … ase-notes/](https://source.sierrawireless.com/resources/airprime/software/release_notes/wp76xx-release-8-customer-release-notes/)) In release 6.0 and below there was a MAC address issue in the ECM gadget causing the ECM driver to not load for host kernels 4.4.x (e.g. Ubuntu 14.04 / 16.04), if you are using a Linux host. In even older releases, the default address was 192.168.225.1. In Release 4, the interface was unreachable, but a workaround was provided for the iptables, in the Release Notes (link above, section 15.4), to get routing working. The simplest method to upgrade from an older release, if you have one of the listed ECM issues, is to use the Windows one-click method from the release page. That uses USB, but doesn’t require the ECM interface. Hope that helps. ---

**Author:** ![HDe2OA](https://avatars.discourse-cdn.com/v4/letter/h/8491ac/32.png) [@HDe2OA](https://forum.sierrawireless.com/u/HDe2OA)\ **Post date:** [March 12, 2018, 4:25pm UTC](https://forum.sierrawireless.com/t/unable-to-communicate-with-wp7603/12203/3 "2018-03-12T16:25:29Z")

@rkirk That seems to have fixed the issue. I tried the Windows 1-click and it was able to reach the device, I then was able to at least ping the module for the first time. Now I’ll at least be able to get one step further in the Getting Started. Again, I appreciate your thoughtful reply and help.