# Swiflash inconsistency **URL:** \ **Category:** Uncategorized\ **Created:** [October 15, 2018, 2:41pm UTC](https://forum.legato.io/t/swiflash-inconsistency/3771 "2018-10-15T14:41:50Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![deadpoolcode](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/deadpoolcode/32/382_2.png) [@deadpoolcode](https://forum.legato.io/u/deadpoolcode)\ **Post date:** [October 15, 2018, 2:41pm UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/1 "2018-10-15T14:41:50Z")
currently I can build Yocto from source and upgrade device for Sierra there are two update tools , swiflash which is for upgrading via USB (bricked device state) and fwupdate which is the standard tool to be used when system is active using fwupdate works great, however swiflash works terrible. I can get swiflash to work, but every time it takes many, many attempts the procedure: using mangoH red, setting sw 7 to “on”, I on PC I see created /dev/ttyUSB0 (this is created only when setting sw7 on as expected) but trying to update issues: $ sudo swiflash -m “WP76XX” -i build\_bin/tmp/deploy/images/swi-mdm9x2 8/yocto\_wp76xx.4k.cwe Detecting USB of the target No device connected this is extremely frustrating, can you assist? am am working on ubuntu 16.04, “real” PC not VM. even restarting the PC does not always help. I have installed swiflash via apt-get and I do have the current rules set ---
**Author:** ![daav](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/daav/32/64_2.png) [@daav](https://forum.legato.io/u/daav)\ **Post date:** [October 16, 2018, 5:19am UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/2 "2018-10-16T05:19:31Z")
Hi @deadpoolcode This has been reported a couple of times, and we work at having a reproducible process that would help for investigation. Will keep you updated. ---
**Author:** ![deadpoolcode](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/deadpoolcode/32/382_2.png) [@deadpoolcode](https://forum.legato.io/u/deadpoolcode)\ **Post date:** [October 18, 2018, 7:42am UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/3 "2018-10-18T07:42:07Z")
Thank you, this will assist a lot 🙂 ---
**Author:** ![nilsa](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@nilsa](https://forum.legato.io/u/nilsa)\ **Post date:** [November 6, 2019, 9:46pm UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/4 "2019-11-06T21:46:50Z")
Same issue here. WP7607-1 and swiflash fail rate at about 50%. Used to be about 5% fail rate or something earlier this year with WP8548. Maybe it got worse after upgrading swiflash to v5.1? Is it possible to download old swiflash versions from somewhere. ---
**Author:** ![dbeckwith](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/dbeckwith/32/663_2.png) [@dbeckwith](https://forum.legato.io/u/dbeckwith)\ **Post date:** [November 7, 2019, 12:26am UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/5 "2019-11-07T00:26:27Z")
I’m having similar issues with `swiflash` on our custom PCBA using a WP8548. When I run `swiflash` it just sits in the `connecting .......` ---
**Author:** ![nilsa](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@nilsa](https://forum.legato.io/u/nilsa)\ **Post date:** [November 7, 2019, 11:03am UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/6 "2019-11-07T11:03:46Z")
Hi @daav. This should be easy to reproduce. We set up a new computer yesterday and got the same issues there. mangoh Red with WP7607-1 On Ubuntu 18.04 computer: - wget [http://updatesite.sierrawireless.com/swiflash/swiflash\_latest.deb](http://updatesite.sierrawireless.com/swiflash/swiflash_latest.deb) -O /tmp/swiflash\_latest.deb - sudo apt-get install /tmp/swiflash\_latest.deb - sudo nano /etc/modprobe.d/blacklist-modem.conf \*\* blacklist qcserial \*\* blacklist qmi\_wwan - sudo apt-get remove modemmanager - Download [usb-drivers-linux-qmi-software-s2,-d-,37n2,-d-,58](https://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-s2,-d-,37n2,-d-,58/#sthash.GOMpEHri.dpbs) and install - Connect mangoh red to computer on CF3 USB (dmesg --follow and wait for it to enumerate) - program with **swiflash -m wp76xx -i firmwarefile.spk** 10 times. I’m sure at least one or two of them will fail. ---
**Author:** ![mehdiALL1](https://avatars.discourse-cdn.com/v4/letter/m/f6c823/32.png) [@mehdiALL1](https://forum.legato.io/u/mehdiALL1)\ **Post date:** [November 12, 2019, 2:41pm UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/7 "2019-11-12T14:41:45Z")
@nilsa, can you try to redownload swiflash! it seems that the 5.1 version was updated ---
**Author:** ![nilsa](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@nilsa](https://forum.legato.io/u/nilsa)\ **Post date:** [November 12, 2019, 2:45pm UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/8 "2019-11-12T14:45:22Z")
Yes I noticed this as well. It works better now with v5.1. Especially if I use TP1 pin as well. But would it not be nice if they called it v5.1.1 or 5.2 if there was a change… 😠 ---
**Author:** ![plu](https://avatars.discourse-cdn.com/v4/letter/p/e19b73/32.png) [@plu](https://forum.legato.io/u/plu)\ **Post date:** [November 21, 2019, 2:23pm UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/9 "2019-11-21T14:23:57Z")
hi @nilsa, we noticed this issue too, and raised the point internally, best regards, ---
**Author:** ![CoRfr](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.legato.io/corfr/32/69_2.png) [@CoRfr](https://forum.legato.io/u/CoRfr)\ **Post date:** [November 25, 2019, 11:28pm UTC](https://forum.legato.io/t/swiflash-inconsistency/3771/10 "2019-11-25T23:28:35Z")
So [http://updatesite.sierrawireless.com/swiflash/swiflash\_latest.deb](http://updatesite.sierrawireless.com/swiflash/swiflash_latest.deb) is not up-to-date (4.6) and was last updated on `Apr 25 2018`. However [https://downloads.sierrawireless.com/tools/swiflash/swiflash\_latest.deb](https://downloads.sierrawireless.com/tools/swiflash/swiflash_latest.deb) is up-to-date (5.1) and was last updated on `Nov 12 2018`. So confusion could have occurred because the two links are slightly similar but are not shipping the same version of swiflash .