开云体育

I'm trying to install new firmware using DfuSeDemo.
When I start up NanoVNA in DFU mode (with the white screen), and then connect the device to a USB port, Device Manager shows a new Directory is added named "Universal Serial Bus devices", and inside that is a single file, STM32 BOOTLOADER. But I was expecting a file named STM Device in DFU Mode.

When I start up DfuSeDemo, and Choose... the dfu file "NanoVNA-H_AA_20191009.dfu", the file gets loaded alright (green bar says "File correctly loaded"), but the Available DFU Devices in the dropdown menu at the top left is still blank.

I'd appreciate some help. Right now, I can't make any changes to the firmware.

Here's another user with the same problem:
/g/nanovna-users/topic/firmware_update_smt_device/34522854?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,34522854

You need to install the st32 serial port drivers.?
There is a 24MB zip file on Hugen's Google drive with the drivers.?
Link to the drive should be in the wiki.?
After installing, connect device and wait for driver to load.

Thanks, Larry. I've tried these steps many times with no success.
Let me trace the path I've been taking and see if you can spot where I'm going wrong.

I followed your pointer to GenHu site

Read through his instructions titled Upgrade NanoVNA use DFU.pdf

Clicked on my desired .dfu, and download the file NanoVNA-H_AA_20191009.dfu, which I stored in the same folder as DfuSeDemo.exe.

Connected NanoVNA to Windows 10 USB port and started up NanoVNA in programming mode.
This generates a new directory named Universal Serial Bus devices, and it contains a driver named STM32 BOOTLOADER

I've seen screen shots of successful firmware updates, and they show this new file to be in the Universal Serial Bus controllers directory, and the driver is named STM Device in DFU Mode.

If I could get past this driver problem then I think the rest would fall into place.

If I could get past this driver problem then I think the rest would fall into place.

The windows operating system needs an STMicroelectronics driver installed.

'DfuSeDemo.exe' installed for me in a folder that also includes a 'Driver' folder,
in which are folders for Win7-10, in each of which are subfolders for x64 and x86 (AKA 32-bit).
In each of those driver subfolders is an installer .exe
Run >>only<< the one that matches your Windows version and bit-depth.

Alternatively:
* right-click on "My PC" icon, select 'Properties'
* select 'Device Manager'
* attach and turn on nanoVNA, open:
> Ports (COM & LPT)
* select the appropriate COM port
- if you do not know which one, simply turn nanoVNA off/on to see which disappears and reappears
* right-click and select "Update Driver Software..."
* browse that back to the DfuSeDemo.exe installation folder

Thanks, Oristo. That fixed it. The key thing that finally made it work was when I Uninstalled the old driver before starting up Driver Wizard. Otherwise it just kept telling me I already had the best driver for my device.

As with re-calibration or after a firmware upgrade, you will first perform a Reset and then perform a calibration step by step (if you make a mistake, it will start over again).

So here too, the faulty driver must be removed first and then the new driver installed. (or use the installation wizard.)

Anyone who can ask well knows the answer already :-)

Did you ever figure this out. I'm in the same condition. Prior to installing the driver both the basic and WCID drivers via zadig-2.5.exe, I saw a USB device in the Windows 10 Device Manager, as STM32 Bootloader... but it appeared to have no driver. Not the device appears in the USB Devices root of the Device Manager. In dfusedemo, the dropdown for "Available DFU Devices" is active, but contains no entries.

I've attempted all of the normal things. Reboot, plug and unplug the device. Restart the device. No luck.

According to both the NanoVNA screen and Windows Device Manager, the device is in DFU mode.

Environment: Windows 10 x64, Defuse Demo v3.0.6, NanoVNA H v 3.4

For me, this is not helpful. The device is populated correctly and without fault, in the Device Manager USB Devices folder as STM32 BOOTLOADER... the device does not appear in the Defuse Demo dropdown list; the list is blank.

Any recommendations will be warmly received.

Had a similar problem.

You need to install the driver for the defuse demo program so that communications can be established between the program and the nanovna.

This driver is DIFFERENT from the one used to establish communications between the nanovna and various display programs like nanovna-saver and other similar ones.

The needed driver can be downloaded from the STM website where the dfuse demo program came from.

Ray
WB6TPU

The proper driver should be downloadable from here:

I had the same problem. This guide helps you through it. /g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA

@mirskym thank you for you thoughtful response. I will give it a try and let everyone know the results. 73 de W6MGV Coxsackie, NY, USA

On Mon, Feb 22, 2021 at 05:19 AM, Marc Verdi wrote:

@mirskym thank you for you thoughtful response. I will give it a try and let
everyone know the results. 73 de W6MGV Coxsackie, NY, USA

=============================================================================

I ran into the same problem with Windows 10 not seeing my NanoVNA in DFU mode. I found the fix via a Google search that led me to forum on www.deviationtx.com. One of the members by the handle of "Nuggetz" suggested that the driver in use was not the DFU version. This is what he did, and it worked for me:

Connect the NanoVNA and put it in DFU mode. Go into device manager and find the STM device under "Universal Serial Bus devices" (at the very bottom of the window). Expand this item and you will probably see "Hub Controller" and "STM32 BOOTLOADER". Right Click on "STM32 BOOTLOADER" and select update driver then choose "Browse my computer for drivers". After that, select "Let me pick from a list of available drivers on my computer".

The driver choices you see there should include "STM device in DFU mode". Select the DFU mode one and that'll do it.

If you don't see both "STM32 BOOTLOADER" and "STM device in DFU mode", then you probably need to install the driver using the dpinst_amd64.exe utility, found in the Win10 folder under Program Files(x86)/STMicroelectronics/Software/DfuSe v3.0.6/Bin/Driver.

Hope this Helps.
73,
Don, KB5QR

Don:

You were spot-on. I opened Windows Device Manager, manually updated the driver to the DFU-capable driver. NanoVNA H is now running version 1.x build from Jan 2021.

72,

Marc, W6MGV

Hi everyone

Thank You Don, for msg #20899
A little addition for those who run into this problem under Windows XP.
The STM Bootloader driver is not automatically installed on this operating system when installing the DfuSe demo, so you must do so as above (exclamation point in yellow triangle for USB contorollers in Device Manager) after placing NanoVNA in DFU mode and PC USB connection in Device Manager.
So look for the error message, click on it, and after unpacking, mark the STM Bootloader Driver package so that the system can install it.
If you have already installed something, delete it and install it. This package also solves the problem on XP.
Link:
If you still get stuck, visit my website as well.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

I certainly will give this a try. I knew that this would wind up being a driver issue.

Let you know tomorrow.

Fred - N4CLA

Is this an STM problem or does the nano world develop these drivers?

Fred - N4CLA

On Sun, Feb 21, 2021 at 5:16 PM Marc Verdi <marc@...>
wrote:

For me, this is not helpful. The device is populated correctly and without
fault, in the Device Manager USB Devices folder as STM32 BOOTLOADER... the
device does not appear in the Defuse Demo dropdown list; the list is blank.

Any recommendations will be warmly received.

I also Had issues that turned out to be due to a BAD USB Cable that came with the NanoVNA H4.
The way I got my unit updated was to boot up my MINT Linux machine AND looked for the USB port using the 'lsusb' command in the command window.
As the machine did not see the VNA under Linux, I tried a different USB cable and tried again and presto it appeared - bad cable.
Next I search for the instructions for installing under Linux and found them - FOLLOW THE process from the below link and the steps for putting your VNA into DFU mode to update:


It was very painless as you DID NOT have to go through the process of registering and installing the software for windows.
All you have to do is be attached to the internet and install the DFU package "sudo apt install dfu-util" in the command window and the software tool is installed.

As I said this is what I did, and I'm not a Linux power use.

On Tue, May 25, 2021 at 11:39 PM, Fred Moore wrote:

Is this an STM problem or does the nano world develop these drivers?

Fred - N4CLA

On Sun, Feb 21, 2021 at 5:16 PM Marc Verdi <marc@...>
wrote:

For me, this is not helpful. The device is populated correctly and without

fault, in the Device Manager USB Devices folder as STM32 BOOTLOADER... the

device does not appear in the Defuse Demo dropdown list; the list is
blank.

Any recommendations will be warmly received.

This is a user error in answering your question.
When you connect an external device to your computer and want to communicate with it, you usually need a so-called driver.
In many cases, you don’t even notice this because the operating system automatically finds and installs one.
The problem will be visible if this installation does not want to work or the device is not recognized and communicating through it.
Therefore, in many cases, it is recommended to install the driver program separately.
In this case, you also need a driver for communication, which you must search for in the COM ports in Device Manager after connection.
You will need an additional driver to use .dfu (i.e. Device Firmware Upgrade), which will NOT appear among the COM ports but as another USB driver as a bootloader when you put your device in dfu mode.
I mastered it in practice, I don’t have a computer qualification.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

Don, KB5QR..... YOU ARE THE MAN!! This worked first time for me!

73
Rick KA2PBO