# Swiflash does not work **URL:** \ **Category:** Uncategorized\ **Created:** [July 10, 2018, 7:02pm UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695 "2018-07-10T19:02:37Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![ktanikel](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@ktanikel](https://mangoh.discourse.group/u/ktanikel)\ **Post date:** [July 10, 2018, 7:02pm UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/1 "2018-07-10T19:02:38Z")
Hi, I’m attempting to flash my mangOH Red with WP7603 using swiflash on Ubuntu 16.04, but it says > [ERROR] > No ttyUSB ports detected; please make sure your device is connected and the udev rule is enabled, or try to power cycle the device. I can flash using fwupdate and also fdt2 on Windows. Any idea why swiflash does not work? ---
**Author:** ![lotam](https://avatars.discourse-cdn.com/v4/letter/l/958977/32.png) [@lotam](https://mangoh.discourse.group/u/lotam)\ **Post date:** [July 11, 2018, 1:43am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/2 "2018-07-11T01:43:32Z")
Hi ktanikel, Refer to swiflash guide: [https://source.sierrawireless.com/resources/airprime/software/swiflash/](https://source.sierrawireless.com/resources/airprime/software/swiflash/) > Check that a /dev/ttyUSBX serial port is mounted on your system: this will be the DM port, necessary to handle the download. Are you able to find /dev/ttyUSBx on your Ubuntu PC after plug mangOH red USB? If unable to find the driver, may worth to try install: [https://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-s2,-d-,31n2,-d-,50/](https://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-s2,-d-,31n2,-d-,50/) Hope it helps. ---
**Author:** ![daav](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/daav/32/79_2.png) [@daav](https://mangoh.discourse.group/u/daav)\ **Post date:** [July 11, 2018, 6:19am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/3 "2018-07-11T06:19:04Z")
Hi @ktanikel Did you install **swiflash** using **apt**? If not, you’ll need to install the udev rules manually (check **swiflash --help** for the instructions). Another though: if you install **swiflash** (or setup the udev rules as explained above) while the device is already plugged in, you’ll need to plug it out and back in (or power-cycle it), to get the **/dev/ttyUSBx** ports correctly configured. ---
**Author:** ![ktanikel](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@ktanikel](https://mangoh.discourse.group/u/ktanikel)\ **Post date:** [July 11, 2018, 5:47pm UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/4 "2018-07-11T17:47:25Z")
@daav, yes I installed swiflash using apt and I can see that the udev rules are in place. But there is no /dev/ttyUSBx device. @lotam There is no /dev/ttyUSBx. I tried your link, but are there any instructions I can find on how to build and install those drivers? I’m able to build ‘GobiSerial’ but not ‘GobiNet’. ---
**Author:** ![lotam](https://avatars.discourse-cdn.com/v4/letter/l/958977/32.png) [@lotam](https://mangoh.discourse.group/u/lotam)\ **Post date:** [July 12, 2018, 1:59am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/5 "2018-07-12T01:59:00Z")
Hi @ktanikel Please try install GobiSerial which is the driver for /dev/ttyUSBx. > cd GobiSerial > make > sudo make install On next power cycle, it should enumerate the /dev/ttyUSBx port. Thx ---
**Author:** ![daav](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/daav/32/79_2.png) [@daav](https://mangoh.discourse.group/u/daav)\ **Post date:** [July 12, 2018, 6:23am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/6 "2018-07-12T06:23:28Z")
Mmm, I’m not sure adding the device drivers would help in any sense if there are not already /dev/ttyUSB ports enumerated. I mean, this is proven to work on a default Ubuntu setup without custom drivers. So to me: - either your host system is specific in any way… Did you tried the board on another computer? - or your device has some troubles… Can you ssh to it? Which FW/Legato version is actually running on it? ---
**Author:** ![ktanikel](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@ktanikel](https://mangoh.discourse.group/u/ktanikel)\ **Post date:** [July 12, 2018, 6:13pm UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/7 "2018-07-12T18:13:17Z")
@lotam , I was able to install GobiSerial and now can see /dev/ttyUSBx. swiflash also works now! @daav, my host system is a standard Ubuntu 16.04 installation. As mentioned, I tried the board on a Windows computer using fdt2 which worked. I installed the VM from mangOH on that same Windows computer but couldn’t use swiflash from within the VM. I can ssh into it and its running Legato 18.04 with the latest firmware from Sierra Wireless. > Firmware Version: SWI9X07Y\_02.16.02.00 000000 jenkins 2018/04/19 19:59:02 Thank you for your help. ---
**Author:** ![daav](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/daav/32/79_2.png) [@daav](https://mangoh.discourse.group/u/daav)\ **Post date:** [July 13, 2018, 7:02am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/8 "2018-07-13T07:02:39Z")
Hi @ktanikel ok, I didn’t catch that you were running in a VM! Indeed, **swiflash** is not supposed to run from within a VM, as it implies a device reset (which leads to a new enumeration) and this is kind of a risky operation when sharing the USB connection from the Windows host to the Linux guest. That being said, it’s good to know that it (unexpectedly!) works when you install the GobiSerial driver. ---
**Author:** ![ktanikel](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@ktanikel](https://mangoh.discourse.group/u/ktanikel)\ **Post date:** [July 13, 2018, 7:15am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/9 "2018-07-13T07:15:32Z")
No, it doesn’t work on the VM. It works on my native Ubuntu machine. To be clear, Native Ubuntu 16. 04 before installing GobiSerial -\> Does not work. MangOH VM on a Windows host -\> Does not work. Windows with fdt2 -\> Works. Native Ubuntu 16.04 after installing GobiSerial -\> Works. ---
**Author:** ![daav](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/daav/32/79_2.png) [@daav](https://mangoh.discourse.group/u/daav)\ **Post date:** [July 16, 2018, 7:07am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/10 "2018-07-16T07:07:23Z")
Hi @ktanikel ok, so it’s really an unexpected behavior on your native host… If at anytime you reproduce the issue again (so **without** the GobiSerial driver installed), please post content of **/var/log/syslog** to help for better understanding of the issue… Thanks! ---
**Author:** ![mango](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@mango](https://mangoh.discourse.group/u/mango)\ **Post date:** [May 31, 2019, 10:47am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/11 "2019-05-31T10:47:10Z")
I use mangOH red WP7702 and mint Ubuntu 16, and also see no /dev/ttyUSB devices. but can ping 192.168.2.2 ---
**Author:** ![mango](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@mango](https://mangoh.discourse.group/u/mango)\ **Post date:** [May 31, 2019, 10:51am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/12 "2019-05-31T10:51:31Z")
May 31 13:50:02 miniITX kernel: [1652.791626] usb 1-5.3: new high-speed USB device number 7 using xhci\_hcd May 31 13:50:02 miniITX kernel: [1652.896943] usb 1-5.3: config 1 has an invalid interface number: 8 but max is 5 May 31 13:50:02 miniITX kernel: [1652.896958] usb 1-5.3: config 1 has an invalid interface number: 19 but max is 5 May 31 13:50:02 miniITX kernel: [1652.896967] usb 1-5.3: config 1 has an invalid interface number: 20 but max is 5 May 31 13:50:02 miniITX kernel: [1652.896976] usb 1-5.3: config 1 has an invalid interface number: 20 but max is 5 May 31 13:50:02 miniITX kernel: [1652.896985] usb 1-5.3: config 1 has no interface number 1 May 31 13:50:02 miniITX kernel: [1652.896993] usb 1-5.3: config 1 has no interface number 4 May 31 13:50:02 miniITX kernel: [1652.897001] usb 1-5.3: config 1 has no interface number 5 May 31 13:50:02 miniITX kernel: [1652.905037] usb 1-5.3: New USB device found, idVendor=1199, idProduct=68c0 May 31 13:50:02 miniITX kernel: [1652.905048] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 31 13:50:02 miniITX kernel: [1652.905053] usb 1-5.3: Product: Sierra Wireless WP7702 May 31 13:50:02 miniITX kernel: [1652.905061] usb 1-5.3: Manufacturer: Sierra Wireless, Incorporated May 31 13:50:02 miniITX kernel: [1652.905065] usb 1-5.3: SerialNumber: VU81038515151013 May 31 13:50:02 miniITX kernel: [1652.917992] qmi\_wwan 1-5.3:1.8: cdc-wdm0: USB WDM device May 31 13:50:02 miniITX kernel: [1652.920237] qmi\_wwan 1-5.3:1.8 wwan0: register ‘qmi\_wwan’ at usb-0000:00:14.0-5.3, WWAN/QMI device, 36:6a:f7:66:a4:fc May 31 13:50:02 miniITX kernel: [1652.926247] cdc\_ether 1-5.3:1.19 usb0: register ‘cdc\_ether’ at usb-0000:00:14.0-5.3, CDC Ethernet Device, c2:50:64:88:54:60 May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.7200] device (usb0): failed to find device 9 ‘usb0’ with udev May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.7231] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/5) May 31 13:50:02 miniITX mtp-probe: checking bus 1, device 7: “/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.3” May 31 13:50:02 miniITX mtp-probe: bus: 1, device: 7 was not an MTP device May 31 13:50:02 miniITX kernel: [1652.984787] cdc\_ether 1-5.3:1.19 enp0s20u5u3i19: renamed from usb0 May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.7981] device (usb0): interface index 9 renamed iface from ‘usb0’ to ‘enp0s20u5u3i19’ May 31 13:50:02 miniITX kernel: [1653.015550] qmi\_wwan 1-5.3:1.8 wwp0s20u5u3i8: renamed from wwan0 May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8206] devices added (path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.3/1-5.3:1.19/net/enp0s20u5u3i19, iface: enp0s20u5u3i19) May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8207] device added (path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.3/1-5.3:1.19/net/enp0s20u5u3i19, iface: enp0s20u5u3i19): no ifupdown configuration found. May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8228] device (enp0s20u5u3i19): state change: unmanaged -\> unavailable (reason ‘managed’) [10 20 2] May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8464] device (enp0s20u5u3i19): link connected May 31 13:50:02 miniITX kernel: [1653.052566] IPv6: ADDRCONF(NETDEV\_UP): enp0s20u5u3i19: link is not ready May 31 13:50:02 miniITX kernel: [1653.052791] cdc\_ether 1-5.3:1.19 enp0s20u5u3i19: kevent 12 may have been dropped May 31 13:50:02 miniITX kernel: [1653.052804] cdc\_ether 1-5.3:1.19 enp0s20u5u3i19: kevent 12 may have been dropped May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8513] keyfile: add connection in-memory (e14490fc-ab46-37cf-a714-801d38db0d3c,“Wired connection 2”) May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8536] settings: (enp0s20u5u3i19): created default wired connection ‘Wired connection 2’ May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8606] device (enp0s20u5u3i19): state change: unavailable -\> disconnected (reason ‘none’) [20 30 0] May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8647] policy: auto-activating connection ‘Wired connection 2’ May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8680] device (enp0s20u5u3i19): Activation: starting connection ‘Wired connection 2’ (e14490fc-ab46-37cf-a714-801d38db0d3c) May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8698] device (enp0s20u5u3i19): state change: disconnected -\> prepare (reason ‘none’) [30 40 0] May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8746] devices added (path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.3/1-5.3:1.8/net/wwp0s20u5u3i8, iface: wwp0s20u5u3i8) May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8755] device added (path: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.3/1-5.3:1.8/net/wwp0s20u5u3i8, iface: wwp0s20u5u3i8): no ifupdown configuration found. May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8772] device (enp0s20u5u3i19): state change: prepare -\> config (reason ‘none’) [40 50 0] May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8792] device (enp0s20u5u3i19): link disconnected (deferring action for 4 seconds) May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8810] device (enp0s20u5u3i19): state change: config -\> ip-config (reason ‘none’) [50 70 0] May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8830] dhcp4 (enp0s20u5u3i19): activation: beginning transaction (timeout in 45 seconds) May 31 13:50:02 miniITX NetworkManager[756]: [1559299802.8878] dhcp4 (enp0s20u5u3i19): dhclient started with pid 2539 May 31 13:50:02 miniITX kernel: [1653.099688] IPv6: ADDRCONF(NETDEV\_UP): enp0s20u5u3i19: link is not ready May 31 13:50:02 miniITX colord-sane: [bjnp] create\_broadcast\_socket: ERROR - bind socket to local address failed - Cannot assign requested address May 31 13:50:02 miniITX dhclient[2539]: DHCPDISCOVER on enp0s20u5u3i19 to 255.255.255.255 port 67 interval 3 (xid=0x1d21d16b) May 31 13:50:05 miniITX dhclient[2539]: DHCPDISCOVER on enp0s20u5u3i19 to 255.255.255.255 port 67 interval 8 (xid=0x1d21d16b) May 31 13:50:06 miniITX NetworkManager[756]: [1559299806.7650] device (enp0s20u5u3i19): link disconnected (calling deferred action) May 31 13:50:06 miniITX NetworkManager[756]: [1559299806.7656] device (enp0s20u5u3i19): state change: ip-config -\> unavailable (reason ‘carrier-changed’) [70 20 40] May 31 13:50:06 miniITX NetworkManager[756]: [1559299806.8002] dhcp4 (enp0s20u5u3i19): canceled DHCP transaction, DHCP client pid 2539 May 31 13:50:06 miniITX NetworkManager[756]: [1559299806.8004] dhcp4 (enp0s20u5u3i19): state changed unknown -\> done May 31 13:50:07 miniITX colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1 May 31 13:50:14 miniITX kernel: [1665.046123] IPv6: ADDRCONF(NETDEV\_CHANGE): enp0s20u5u3i19: link becomes ready May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8406] device (enp0s20u5u3i19): link connected May 31 13:50:14 miniITX kernel: [1665.053355] cdc\_ether 1-5.3:1.19 enp0s20u5u3i19: kevent 12 may have been dropped May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8436] device (enp0s20u5u3i19): state change: unavailable -\> disconnected (reason ‘carrier-changed’) [20 30 40] May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8512] policy: auto-activating connection ‘Wired connection 2’ May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8574] device (enp0s20u5u3i19): Activation: starting connection ‘Wired connection 2’ (e14490fc-ab46-37cf-a714-801d38db0d3c) May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8590] device (enp0s20u5u3i19): state change: disconnected -\> prepare (reason ‘none’) [30 40 0] May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8608] device (enp0s20u5u3i19): state change: prepare -\> config (reason ‘none’) [40 50 0] May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8617] device (enp0s20u5u3i19): state change: config -\> ip-config (reason ‘none’) [50 70 0] May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8624] dhcp4 (enp0s20u5u3i19): activation: beginning transaction (timeout in 45 seconds) May 31 13:50:14 miniITX NetworkManager[756]: [1559299814.8674] dhcp4 (enp0s20u5u3i19): dhclient started with pid 2551 May 31 13:50:14 miniITX dhclient[2551]: DHCPDISCOVER on enp0s20u5u3i19 to 255.255.255.255 port 67 interval 3 (xid=0x1fc99778) May 31 13:50:16 miniITX avahi-daemon[775]: Joining mDNS multicast group on interface enp0s20u5u3i19.IPv6 with address fe80::4174:d4e9:1afd:f10f. May 31 13:50:16 miniITX avahi-daemon[775]: New relevant interface enp0s20u5u3i19.IPv6 for mDNS. May 31 13:50:16 miniITX avahi-daemon[775]: Registering new address record for fe80::4174:d4e9:1afd:f10f on enp0s20u5u3i19.\*. May 31 13:50:17 miniITX dhclient[2551]: DHCPDISCOVER on enp0s20u5u3i19 to 255.255.255.255 port 67 interval 3 (xid=0x1fc99778) May 31 13:50:18 miniITX dhclient[2551]: DHCPREQUEST of 192.168.2.3 on enp0s20u5u3i19 to 255.255.255.255 port 67 (xid=0x7897c91f) May 31 13:50:18 miniITX dhclient[2551]: DHCPOFFER of 192.168.2.3 from 192.168.2.2 May 31 13:50:18 miniITX dhclient[2551]: DHCPACK of 192.168.2.3 from 192.168.2.2 May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1749] address 192.168.2.3 May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1750] plen 24 (255.255.255.0) May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1750] server identifier 192.168.2.2 May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1751] lease time 43200 May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1752] hostname ‘miniITX’ May 31 13:50:18 miniITX avahi-daemon[775]: Joining mDNS multicast group on interface enp0s20u5u3i19.IPv4 with address 192.168.2.3. May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1753] dhcp4 (enp0s20u5u3i19): state changed unknown -\> bound May 31 13:50:18 miniITX avahi-daemon[775]: New relevant interface enp0s20u5u3i19.IPv4 for mDNS. May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1810] device (enp0s20u5u3i19): state change: ip-config -\> ip-check (reason ‘none’) [70 80 0] May 31 13:50:18 miniITX avahi-daemon[775]: Registering new address record for 192.168.2.3 on enp0s20u5u3i19.IPv4. May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1832] device (enp0s20u5u3i19): state change: ip-check -\> secondaries (reason ‘none’) [80 90 0] May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1841] device (enp0s20u5u3i19): state change: secondaries -\> activated (reason ‘none’) [90 100 0] May 31 13:50:18 miniITX dhclient[2551]: bound to 192.168.2.3 – renewal in 20342 seconds. May 31 13:50:18 miniITX NetworkManager[756]: [1559299818.1955] device (enp0s20u5u3i19): Activation: successful, device activated. May 31 13:50:18 miniITX dbus[748]: [system] Activating via systemd: service name=‘org.freedesktop.nm\_dispatcher’ unit=‘dbus-org.freedesktop.nm-dispatcher.service’ May 31 13:50:18 miniITX systemd[1]: Starting Network Manager Script Dispatcher Service… May 31 13:50:18 miniITX dbus[748]: [system] Successfully activated service ‘org.freedesktop.nm\_dispatcher’ May 31 13:50:18 miniITX systemd[1]: Started Network Manager Script Dispatcher Service. May 31 13:50:18 miniITX nm-dispatcher: req:1 ‘up’ [enp0s20u5u3i19]: new request (1 scripts) May 31 13:50:18 miniITX nm-dispatcher: req:1 ‘up’ [enp0s20u5u3i19]: start running ordered scripts… ---
**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 31, 2019, 4:51pm UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/13 "2019-05-31T16:51:57Z")
please open new question and not on a solved question. ---
**Author:** ![mango](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@mango](https://mangoh.discourse.group/u/mango)\ **Post date:** [June 3, 2019, 5:47am UTC](https://mangoh.discourse.group/t/swiflash-does-not-work/1695/14 "2019-06-03T05:47:58Z")
ok, not sure who and why has set this thread as ‘sovled’