If you plug in a device, the vast majority of Windows users want the device to 'just work.' My non-technical parent doesn't want Generic USB drivers so they can flash the firmware on their mouse. I, however, as an aristocrat, sometimes want to do low-level stuff and flash an OS on a Microcontroller.
Driver STM Device In DFU Modefor Windows 10 64-bit
Zadig is a Windows application that installs generic USB drivers, such as WinUSB, libusb-win32/libusb0.sys or libusbK, to help you access USB devices. It can be especially useful for cases where: you want to access a device using a libusb-based application you want to upgrade a generic USB driver you want to access a device using WinUSB
If you follow the instructions when flashing a device and don't have the right USB driver installed you'll likely get an error like this:
Here you can see me finding the ST device within Zadig and replacing the driver with WinUSB. In my case the device was listened under STM32 Bootloader. Be aware that you can mess up your system if you select something like your WebCam instead of the hardware device you mean to select.
Now I can run dfu-util --list again. Note the before and after in the screenshot below. I run dfu-util --list and it finds nothing. I replace the bootloader with the generic WinUSB driver and run dfu-util again and it finds the devices.
With the board plugged in, go to your device manager and select the COM port the board is plugged into and simply uninstall the drivers there, cant recall off hand what the exact option is but its there under the properties menu.
For the firmware update to be successful, it is necessary that windows ten pro 64 bit 21H1 will install (when the interactive display is connected and after checking the windows ten update) the STM device in dfu mode update (see the picture below).
More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157242025, false) Igor - PY3IG $('#timedispmsg157249510').replaceWith(DisplayShortTime(1579456361450162973, false)); #9855 Everything works fine again. Bad USB cable lost connection.I used another USB cable and the DFU mode connected (jumper).Updated and nano FW back to life.73 !! More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157249510, false) MVS Sarma $('#timedispmsg157250221').replaceWith(DisplayShortTime(1579457186521255042, false)); #9856 Congrats toggle quoted messageShow quoted text On Sun, 19 Jan 2020, 11:22 pm , wrote:Everything works fine again. Bad USB cable lost connection.I used another USB cable and the DFU mode connected (jumper).Updated and nano FW back to life.73 !! $('#quoted-157250221').on('show.bs.collapse', function () $('#qlabel-157250221').text("Hide quoted text"); ) $('#quoted-157250221').on('hide.bs.collapse', function () $('#qlabel-157250221').text("Show quoted text"); ) More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157250221, false) Brian Garber $('#timedispmsg157271229').replaceWith(DisplayShortTime(1579487049698852242, false)); #9873 Hello all, I'm at a loss. I was able to update firmware by going into DFU mode on my nanoVNA, but now that is not working at all since firmware version 0.5.4. The DfuSe Demo (v3.0.6) is not recognizing the nanoVNA"c when I enter DFU mode either via "Config", "Reset and Enter DFU" or by putting the short across the pins to force DFU mode. My PC recognizes the difference between my virtual com port (normal mode) and Universal Serial Bus devices, STM32 BOOTLOADER mode (DFU) mode.I'm not sure what has changed. Any troubleshooting tips would be greatly appreciated!Thanks,Brian More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157271229, false) Gyula Molnar $('#timedispmsg157282884').replaceWith(DisplayShortTime(1579522664297967089, false)); #9889 On Mon, Jan 20, 2020 at 03:24 AM, wrote:Hello all, I'm at a loss. I was able to update firmware by going into DFU modeon my nanoVNA, but now that is not working at all since firmware version0.5.4. The DfuSe Demo (v3.0.6) is not recognizing the nanoVNA"c when I enterDFU mode either via "Config", "Reset and Enter DFU" or by putting the shortacross the pins to force DFU mode. My PC recognizes the difference between myvirtual com port (normal mode) and Universal Serial Bus devices, STM32BOOTLOADER mode (DFU) mode.I'm not sure what has changed. Any troubleshooting tips would be greatlyappreciated!Thanks,BrianThere are two ways to upgrade the firmware:1. DfuSe2. STM-Link which requires an STM-Link v2 dongleYou need to use the latter to recover.More descriptions on the wiki or my web page. ha3hz.huI wish you a successful fix.73, Gyula HA3HZ More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157282884, false) Oristo $('#timedispmsg157283151').replaceWith(DisplayShortTime(1579523183572730668, false)); #9890 1. DfuSe2. STM-Link which requires an STM-Link v2 dongleActually, ST-Link: -users/message/2447 More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157283151, false) Brian Garber $('#timedispmsg157289285').replaceWith(DisplayShortTime(1579532862572352615, false)); #9899 Thank you both for the information! I think my issue may be a bit different (maybe) because I am able to enter DFU mode on the nanoVNA, it's just that the DfuSe Demo software no longer recognizes the device once in that mode. Also, I can connect via the STM32CubeProgrammer program over USB (see attached png). Thankfully my nano isn't bricked, but I can't seem to update it over DfuSe Demo. More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157289285, false) Gyula Molnar $('#timedispmsg157290408').replaceWith(DisplayShortTime(1579534209785605751, false)); #9903 On Mon, Jan 20, 2020 at 04:07 PM, wrote:Thank you both for the information! I think my issue may be a bit different(maybe) because I am able to enter DFU mode on the nanoVNA, it's just that theDfuSe Demo software no longer recognizes the device once in that mode. Also, Ican connect via the STM32CubeProgrammer program over USB (see attached png).Thankfully my nano isn't bricked, but I can't seem to update it over DfuSeDemo.If you don't recognize it, you can use USBDeview Utility to see what's preventing it.If your mouse and keyboard are both usb, do not delete it!Delete and reinstall the troublesome or unnecessary driver.I hope this is the solution. _devices_view.html More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157290408, false) Gyula Molnar $('#timedispmsg157290544').replaceWith(DisplayShortTime(1579534373141378626, false)); #9904 Sorry, I think I got it wrong. Then the ST-Link v2 dongle remains. More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157290544, false) Brian Garber $('#timedispmsg157299859').replaceWith(DisplayShortTime(1579543948775144675, false)); #9932 Ok, so one last try with USBDeview. In the image you can see where I've highlighted a Port_#002.Hub, SMT32 Bootloader line. However, the very last line is what shows up when I reset and enable DFU on my nanoVNA. The serial number looks corrupted, does this mean that I must recover using the ST-Link v2 dongle? I think I saw where that is less than $2 USD on the Chinese website.73, Brian More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157299859, false) Brian Garber $('#timedispmsg157299911').replaceWith(DisplayShortTime(1579544004957770482, false)); #9935 Image attached. More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157299911, false) Gyula Molnar $('#timedispmsg157305837').replaceWith(DisplayShortTime(1579550997439618356, false)); #9945 delete the wrong line Right-click to see the delete option.then try DfuSE programming again. More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157305837, false) Brian Garber $('#timedispmsg157306742').replaceWith(DisplayShortTime(1579552007188931101, false)); #9948 Thank you so much for your patience with me! I wasn't able to get that to work on my laptop, however I tried a different computer and updated the nanoVNA without issue. So now I'm wondering if I need to delete the registry value on my laptop that corresponds to that device. This is strange, but I'll chock it up to Windows!Thanks again,Brian More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157306742, false) KV5R $('#timedispmsg157306971').replaceWith(DisplayShortTime(1579552290251173039, false)); #9949 It's a common problem. Search this forum for "STM device in DFU mode" using the Search box at top of page.For some reason Windows sometimes replaces the driver "STM device in DFU mode" (for DfuSe Demo software) with the driver "STM32 BOOTLOADER mode" (for the ST-Link dongle).The BOOTLOADER driver will not work with DFUse Demo.Delete the BOOTLOADER driver (with Device Manager or USBDview) and then reinstall DFUse Demo software, it should put the "STM device in DFU mode" driver back (I think).73, --kv5r More All Messages By This Member
displayLikeStats("/g/nanovna-users", 2, 157306971, false) Larry Rothman $('#timedispmsg157307285').replaceWith(DisplayShortTime(1579552647526455128, false)); #9950 Try this: - attach the nano to the problem pc and turn on in dfu mode- open Devices from the control panel - delete the nano usb device AND its driver that is showing it's in dfu mode- turn off the Nano and try dfu mode again - when Windows senses the device, it should request the dfu driver- point it to the STM driver files (mentioned in the wiki) you installed.NOTE: make sure you're using the right 32 or 64 bit drivers for your PC! toggle quoted messageShow quoted text On Monday, January 20, 2020, 3:28:15 p.m. GMT-5, brianbgarber via Groups.Io wrote: Thank you so much for your patience with me! I wasn't able to get that to work on my laptop, however I tried a different computer and updated the nanoVNA without issue. So now I'm wondering if I need to delete the registry value on my laptop that corresponds to that device. This is strange, but I'll chock it up to Windows!Thanks again,Brian $('#quoted-157307285').on('show.bs.collapse', function () $('#qlabel-157307285').text("Hide quoted text"); ) $('#quoted-157307285').on('hide.bs.collapse', function () $('#qlabel-157307285').text("Show quoted text"); ) More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157307285, false) Oristo $('#timedispmsg157315896').replaceWith(DisplayShortTime(1579562354480979881, false)); #9965 The BOOTLOADER driver will not work with DFUse Demo.linked in -users/wiki#Help More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157315896, false) Brian Garber $('#timedispmsg157409734').replaceWith(DisplayShortTime(1579718719778010426, false)); #10050 I wanted to document a solution to this problem that I found on the Wilderness Labs website. I will quote their steps directly so that we have an archive of the STM32 BOOTLOADER driver issue:1) Connect your device in bootloader mode.2) Open Device Manager3) Find Universal Serial Bus devices > STM32 BOOTLOADER4) Right-click STM32 BOOTLOADER and select Uninstall Device5) In the Uninstall Device window, check Delete the driver software for this device, and click Uninstall6) After uninstall is complete, the device will appear as STM Device in DFU mode under Universal Serial Bus controllers.7) Reconnect the device in bootloader mode.These instructions and photo came (with permission) from the following web page: _Basics/Troubleshooting/VisualStudio/73, Brian More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157409734, false) Oristo $('#timedispmsg157411821').replaceWith(DisplayShortTime(1579720787168955210, false)); #10053 Hi Brian -These instructions1) .. are incomplete, in that many will need to install the appropriate STM drive.2) There is already an entry at -users/wiki#Help "check for wrong driver" More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157411821, false) Oristo $('#timedispmsg157414945').replaceWith(DisplayShortTime(1579724058190439378, false)); #10056 Please review this Wiki page: -users/wiki/drivers#Cannot-load-new-firmware3AC2A0-STM32-BOOTLOADERAfter any recommended changes, the main Wiki page will be updated to point at it More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157414945, false) KV5R $('#timedispmsg157578360').replaceWith(DisplayShortTime(1579849151962189756, false)); #10113 Hi Oristo,Good work on the driver wiki page. For better new-user understanding, you might consider adding something like:"There are 3 possible drivers that may appear in Device Manager:1 - STMicroelectronics Virtual COM port (for normal communication, as with nanovna-saver, terminal, etc)2 - STM Device in DFU Mode (for DfuSE Demo software)3 - STM32 Bootloader (for the ST-Link dongle)User needs #1 & #2, not #3 (unless they are using the ST-Link dongle).Sometimes #2 gets replaced by #3."Why? Someone with this problem needs to test why and post repeatable results here. I thought maybe Windows is grabbing the bootloader driver because of user doing some wrong sequence, so just spent an hour plugging, powering, switching to DFU, and starting software, in many sequences. It didn't matter. If nano is in normal mode, Windows always started the COM driver. If it's in DFU mode, windows always switches to the DFU Mode driver. So now I think some users are searching for a driver online and finding the ST-Link bootloader driver (or some package that installs it) because it's confusing. There are too many (old) instructions for drivers and ways to install them; all Windows' users need is DfuSE Demo, it will bring the right drivers."Next, disconnect the nano and place it into DFU mode and connect to the computer again." On mine, when I switch to DFU mode (by nano menu), Windows makes noises; Device Manager shows the COM port driver disappear, and the DFU mode driver appears, without disconnecting or powering off/on. Of course, power off/on is needed to exit DFU mode, but not to enter it (unless using boot jumper, or new press button & power-on method.)"Connect your device in bootloader mode." I think you mean "... DFU mode." A new user will say "what's bootloader mode?" (The phrase from the site Brian found is not specific to the nanovna; to me, the "bootloader" phrase implies using the ST-link dongle, since DFU via DfuSE does not access the bootloader.)Hope this is helpful, and not too noisy :)--KV5R More All Messages By This Member
displayLikeStats("/g/nanovna-users", 0, 157578360, false) Close Verify Delete Are you sure you wish to delete this message from the message archives of nanovna-users@groups.io? This cannot be undone. Cancel Yes Close Verify Repost Are you sure you wish to repost this message? Cancel Yes CloseReport MessageReasonReport to ModeratorsI think this message isn't appropriate for our group. The Group moderators are responsible for maintaining their community and can address these issues.Report to Groups.io SupportI think this violates the Terms of Service. This includes: harm to minors, violence or threats, harassment or privacy invasion, impersonation or misrepresentation, fraud or phishing.Note:Your email address is included with the abuse report. 2ff7e9595c
Comments