wp7601-1 dev host to tgt (ecm) failure to communicate


#1

Working with a MangOH Red Board that I got with a WP-7504 module. Boots up and works like a charm for usb networking between the dev host (linux ubuntu) and target SW WP7504 as I get a usb0 interface for 192.168.2.3 on my linux dev host and can successfully ssh to the WP 7504 as root at 192.168.2.2.

My project requires a SW WP-7601-1 module instead. Can’t seem to get the wp 7601-1 module into a mode in which I can network via the target ecm device ip address 192.168.2.2 from my linux development host. My linux development host does not enumerate a usb-to-ethernet usb0 network device and hence no ip address either.

Reading on the forums which I have scrubbed for possible solutions, I’ve come up empty handed. Appears that the firmware that I have is too old to successfully begin with. Tried an iptables fix (did not work), a windows flash programming one-click update (does not succeed), as well as a dead end procedure (link that has no procedure).

Looking for some support or advice into getting successfully through the getting started documentation but this networking issue has me stalled. I have one WP7504 module and two WP7601-1 modules and have tried all of them. The WP7504 works but the two WP7601-1 modules fail to successfully network from the dev host to the target.

Output from the two WP 7601-1 modules from the ‘cm info’ command is as follows in the snippets below …

–snip
root@swi-mdm9x28:~# cm info
Device: WP7601-1
IMEI: 351709090002933
IMEISV:
FSN: WC729540171006
Firmware: SWI9X07Y_02.04.04.00 000000 jenkins 2017/07/01 01:17:25
Bootloader: SWI9X07Y_02.04.04.00 000000 jenkins 2017/07/01 01:17:25
PRI PN:
PRI Rev:
SKU: 1103728
–snip

–snip
root@swi-mdm9x28:~# cm info
Device: WP7601-1
IMEI: 351709090002982
IMEISV:
FSN: WC729540290206
Firmware: SWI9X07Y_02.04.04.00 000000 jenkins 2017/07/01 01:17:25
Bootloader: SWI9X07Y_02.04.04.00 000000 jenkins 2017/07/01 01:17:25
PRI PN:
PRI Rev:
SKU: 1103728
–snip


#2

Hi,

First step is to make sure you are using the latest greatest USB drivers.

https://source.sierrawireless.com/~/media/support_downloads/legato/wpdriver-usb-drivers-build-4773/genericdriversetup.ashx

This could allow the one click updater to see the unit and update the firmware successfully, also make sure you right click on the updater and ‘Run as administrator’.

https://source.sierrawireless.com/~/media/support_downloads/airprime/software/wp76xx/release8/wp76xx_release8_rc4_generic_exe.ashx?la=en

Regards

Matt


#3

I have already done that yesterday. For Windows 10 Pro, I have downloaded the latest USB drivers for my device WP7601-1 (driver has ‘generic’ in the name) and did also attempt to run this one-click application as the Windows administrator. Tried again today with both the files at the links you have provided for the Windows Driver and one-click updater .exe file running as administrator. The result was not successful. I have a attached a .png file of the console output from the one-click application.



#4

It sounds like your interface required for FW download is also not present, based on that Secondary error code: 5. To simplify the update process, you can force the device to stay in Bootloader upon reset by flipping the dip switch SW401, position 7, to the ON position. That switch is tied to the Service Pin (SVC_PIN) on WP. When you power cycle or reset in that configuration, the console should include a message like:
B - 2516067 - SVC PIN detected

And the console logs should stop before loading the kernel. In Windows you should see a DM Port serial interface, (from the CF3 USB interface, not the console), and the Windows One-click tool should now be able to use that for the update.

Note that the switch means it will always boot to Bootloader, so you need to flip it back either after the download starts, or after the download is complete, to boot the system back up and validate the download. The switch isn’t polled or tied to an interrupt, so if you toggle it after the download is complete, you’ll need to power cycle to reboot into normal operating mode. If you switch it during the download, the reboot cycle following the flash procedure will sense the change and automatically boot to normal operating mode. Just be careful not to power cycle during the download.

Hope that helps. Once you have updated from Release 4/4.1 to Release 8 I think your ECM problem should be resolved too.