¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

DFUseDemo


 

I am running Windows10 Home 64 Bit, and had DFUsDemo running OK
After a firmware update (Erics Version 2.3) suddenly DFUSE Demo no more sees my NanoVNA-H .
Windows devicemanager shows the the device in DFU mode as "STM32 Bootloader" and when I run Zadig I can select "STM32 Bootloader" and install the drivers.
In the device manager I see for "STM32 bootloader" these drivers : WinUSB.sys, WdfCoinstaller01011.dll and WinUSBcoinstaller2.dll are these correct ??
I uninstalled and re-installed DFUseDemo, whatever i do, nothing helps.
So now I can no more.update the firmware !
Is there anyone who can help to solve this problem ?
Many thanks in advance
Jos


 

I never had to use Zadig in Windows 10 64bit to use DFUseDemo. This is probably a problem by you. Put your Hardware Device Manager window on and examinate following. Try uninstalling Zadig (actually a USB driver) until it no longer appears in Hardware Devive Manager window. This may have to be done multiple times. In the View menu, put the option "show hidden devices", you will see them grayed out in the list, and see if there is an earlier installation of Zadig (Zadig itself is not visible, but 'USB lib device' or something similar - i have not the exact names, but don't delete the 'Universal Serial-Bus Controllers'!) delete or uninstall all gray drivers until they are gone. The Wiki Files contains the manual of DFUseDemo and its installation. Follow it carefully. I test it again here, and you don't need Zadig. If you connect the Nano, with the boot button pressed, a "STM Device in DFU Mode" will first appear in Hardware Device Manager (with a yellow triangle). If you wait 20 seconds, the driver is automatically loaded in Windows, and the "STM Device in DFU Mode" is added to the list "Universal Serial-Bus Controllers". If you turn the Nano off, "STM Device in DFU Mode" will remain in the list, but then turn gray.
on1bes


 

Hello Herman,

Thank you so much Herman, I ow you a lot, you solved my problem !!!!!

I just had to delete the drivers in Windows Device manager under "USB devices/ DFU Bootloader".

After having done this, when I connected the NanoVNA in DFU mode to the USB port,? it did not show up in the device manager under "USB devices" but under? "USB Serial Bus-controllers", that solved it.

You were the only one that reacted on this message sofar, again I ow you a lot !!

Thanks many times.

Jos (pa3cce)


Op 12-11-2019 om 23:41 schreef Herman De Dauw:

I never had to use Zadig in Windows 10 64bit to use DFUseDemo. This is probably a problem by you. Put your Hardware Device Manager window on and examinate following. Try uninstalling Zadig (actually a USB driver) until it no longer appears in Hardware Devive Manager window. This may have to be done multiple times. In the View menu, put the option "show hidden devices", you will see them grayed out in the list, and see if there is an earlier installation of Zadig (Zadig itself is not visible, but 'USB lib device' or something similar - i have not the exact names, but don't delete the 'Universal Serial-Bus Controllers'!) delete or uninstall all gray drivers until they are gone. The Wiki Files contains the manual of DFUseDemo and its installation. Follow it carefully. I test it again here, and you don't need Zadig. If you connect the Nano, with the boot button pressed, a "STM Device in DFU Mode" will first appear in Hardware Device Manager (with a yellow triangle). If you wait 20 seconds, the driver is automatically loaded in Windows, and the "STM Device in DFU Mode" is added to the list "Universal Serial-Bus Controllers". If you turn the Nano off, "STM Device in DFU Mode" will remain in the list, but then turn gray.
on1bes


KEN G4APB
 

Hi, i'm a newby to this but have the same problem. i'm running Win7 and under device manager is shows 'STM32 Bootloader' If I delete this and plug in my Nanovna in DFU mode, the same driver gets reloaded. I can't get dFuSedemo to recognise it.
Any ideas what I am doing wrong please.

Ken G4APB


W5DXP
 

From: KEN G4APB: the same driver gets reloaded. I can't get dFuSedemo to recognise it. Any ideas what I am doing wrong please.
Use ZADIG to load the correct driver.


KEN G4APB
 

That¡¯s just the problem. When the Nanovna arrived it had a different driver pre-loaded and I overwrote it using Zadig because instructions I saw on various forums said to do this. The new driver loaded was something like ¡°WinUSB.....¡±. I could kick myself because when I first had a look under Windows ¡®control panel¡¯ it was showing as ¡®STM device in DFU mode¡¯ and now it says STM32 Bootloader.
It probably would have worked with the original driver but I mistakenly tried to follow set of instructions to upgrade my unit. ( I wanted to use a github programme that has the ¡®delta marker¡¯ option).

Ken g4apb


W5DXP
 

From: KEN G4APB: it was showing as ¡®STM device in DFU mode¡¯ and now it says STM32 Bootloader.
Would one of these inexpensive devices solve your problem? I bought one (just in case) but haven't needed to use it.


 

Just make sure not to "only" uninstall the driver, you must remove it too (there is a check box for that)

See /g/nanovna-users/message/9949