¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Nanovna-Users
  2. Topics

My NanoVNA is not recognised by DFUse when using V 0.2.3 firmware

 

Hi All,
Yesterday I flashed edy555's version 0.2.3 firmware,
I was not very happy, so I tried to flash some other firmware today.
But with the present firmware set in DFU mode DFUseDemo no more recognises my device.
So I can't flash no more !
Is there someone that had the same experience and/or has a solution ?
Thanks,
Jos
 

Hi Jos,

please read this:
#3416 msg is correct. /g/nanovna-users/message/3416

73, Gyula HA3HZ
 

Try reboot your PC.
 

I did , even de- re-installed DFUseDemo pavkage, cleaned register, resart PC? .... same result.

Windows evice manager reports : USB Devices -> STM32 bootloader

Thanks anyhow.

Jos

Op 10-11-2019 om 18:29 schreef QRP RX:

Try reboot your PC.
 

Thanks Hyula

I read the message, looks like I have to buy a STM-link device.

I de-installed DFUse Demo pack cleaned the register, re-installed DFU pack,? restarted the PC .......... device NOT recognised. by DFUse.

Windows device manager reports USB devices -----> STM32 Bootloader.

Use it with NanoVNA-SAVER, GREAT SOFTWARE.

Thanks very much es 73

Jos (PA3CCE)


Op 10-11-2019 om 18:28 schreef Gyula Molnar:

Hi Jos,

please read this:
#3416 msg is correct. /g/nanovna-users/message/3416

73, Gyula HA3HZ
 

i did more,

1) Un-installed DFUseDemo

2) Cleaned the registry.

3) Restarted the PC.

4) Re-injstalled DFUsePackage

5) Looked in Windows Device manager : USB Devices ----> STM32 bootloadeer.

6) Result : NONE, DFUSE does not see NanoVNA.


Op 10-11-2019 om 18:29 schreef QRP RX:

Try reboot your PC.
 

I *think* I had to use something called Zadig to change the USB driver used:



I certainly used it, at least, but quite *what* driver I had to change to I
don't remember - and this was on my Windows 7 machine, whereas my Window 10
machine just worked, as I remember it.

Maybe that's a place to start searching from.

--
Rune / 5Q5R

On Sun, 10 Nov 2019 at 19:31, Jos Stevens <jrs@...> wrote:

i did more,

1) Un-installed DFUseDemo

2) Cleaned the registry.

3) Restarted the PC.

4) Re-injstalled DFUsePackage

5) Looked in Windows Device manager : USB Devices ----> STM32 bootloadeer.

6) Result : NONE, DFUSE does not see NanoVNA.


Op 10-11-2019 om 18:29 schreef QRP RX:
Try reboot your PC.
 

Hi Rune,

Yes, I used Zadig to install the USB drivers like WinUSB for use with SDR hardware? (Software Defined Radio).

Besides, the PC recognises NanoVNA, you hear the sound when connecting and the device manager reports " USB Device STM32 bootloader" .

Thanks for you rerply

Jos

Op 10-11-2019 om 19:57 schreef Rune Broberg:

I *think* I had to use something called Zadig to change the USB driver used:



I certainly used it, at least, but quite *what* driver I had to change to I
don't remember - and this was on my Windows 7 machine, whereas my Window 10
machine just worked, as I remember it.

Maybe that's a place to start searching from.
 

Jos,

Did you install the STM drivers as described in the wiki at the end of the webpage?
 

Well, the PC regognises the device as "STM32 Bootloader" , is that not OK?

I have loaded several versions of version into my NanoVNA before, without any problem.

Thanks anyhow

Jos

Op 10-11-2019 om 20:08 schreef Larry Rothman:

Jos,

Did you install the STM drivers as described in the wiki at the end of the webpage?
 

Just a thought...
Have you tried doing the link on the nano vna to pop it into boot mode???
 

Hi Dean,

Yes I did, it makes no difference. Strange thing is that Windows device manager shows "STM32 in boot mode". So why does DFUseDemo not see it ???

Jos

Op 10-11-2019 om 22:07 schreef Dean Smith:

Just a thought...
Have you tried doing the link on the nano vna to pop it into boot mode???
 

ok, i use win7 here.
just turning the nano nva with c usb lead connected i see thus in device manager
this shows device as teensy.
on entering dfu mode under 0.4.3
i get stm message in usb devices!
i now if i load Dfuse demo i get the device in the top window filled.
i did once convert a hex file to dfu, and for some reason it failed...
i just ended up with white display, so turned off nanovna , did the link and re inserted firmware.
everything was then back to normal.
don't know if any of this will help...

teensy.PNG
stm.PNG

 

and just to add, v0.2.3 firmware is on the edge of not needing the link to induce thew bootloader of stm32.
Can't remember if needed or not on this version? if not then link has to be made.
what is happening on screen at the moment..is it white??
It sounds like the dfudemo is playing ball, but there is no handshake to the bootloader from the vna.
 

also if the link is connected.. power OFF the vna then back on again to get the stm into boot mode.
With dfusedemo running, this should make the handshake with the bootloader on stm32.
you should hear a couple of beeps and up it comes.
 

Jos,
Do have you another computer you can run the DFUseDemo app from? The reason I ask is because I ran into a similar situation on a PC where Windows device manager showed "STM32 in boot mode and I could connect to the NanoVNA using nanovna-saver, but DFUseDemo couldn't detect the NanoVNA in the DFU mode. I eventually tried running DFUseDemo on another computer and it recognized the NanoVNA in the DFU mode without any sweat.

I later tried to determine why my other computer (WIN10, i7, 12GB Ram) failed to run DFUseDemo and a web search said it could be a corrupted or out of date run-time problem (I believe it was one of the Visual C + runtimes). I found a file on the web named "aio-runtimes_v2.4.8.exe" which uninstalled the runtimes and reinstalled new ones. After re-booting, DFUseDemo ran fine and connected to the NanoVNA when it was in the DFU mode.

Good luck,

-Herb
 

Hi Herb,

Thanks for your reply,

Unfortunately I do not have another computer to do that, but as you describe it it looks very simular , I'm unning Win10 on a HP i7, 8 GB of RAM, NanoV.BNA runs OK using the NanoVNA-Saver software and DFUse dos not detect the device, touch the device manager shows STM32 " bootloader" so my gutfeeling says the problem is in the DFUseDemo installation, though it performed well before. I will do some more investigation tomorrow for now it's very late.

Thanks for your info best regards

Jos

Op 10-11-2019 om 23:26 schreef hwalker:

Jos,
Do have you another computer you can run the DFUseDemo app from? The reason I ask is because I ran into a similar situation on a PC where Windows device manager showed "STM32 in boot mode and I could connect to the NanoVNA using nanovna-saver, but DFUseDemo couldn't detect the NanoVNA in the DFU mode. I eventually tried running DFUseDemo on another computer and it recognized the NanoVNA in the DFU mode without any sweat.

I later tried to determine why my other computer (WIN10, i7, 12GB Ram) failed to run DFUseDemo and a web search said it could be a corrupted or out of date run-time problem (I believe it was one of the Visual C + runtimes). I found a file on the web named "aio-runtimes_v2.4.8.exe" which uninstalled the runtimes and reinstalled new ones. After re-booting, DFUseDemo ran fine and connected to the NanoVNA when it was in the DFU mode.

Good luck,

-Herb
 

Next time to reboot PC. If it doesn't helps and you don't hear USB connected device "ding" sound when you connect USB cable in DFU mode, then go to Control Panel => Device Manager, click on computer with rigth mouse button and select context menu "Scan for hardware changes".

In most case it will solve issue.
 

Unfortunately I do not have another computer to do that
I found this GitHub project for DFU installation by Android app
 

I've been trying to get this working - keeps coming back and saying the ID doesn't match even though it does.?

Since the last commit to this was several years ago - there is most likely some bugs introduced by newer version of Android.
It would be really nice if CHO45 could integrate this into his webUSB app
...Larry

On Monday, November 11, 2019, 8:13:50 a.m. GMT-5, Oristo <ormpoa@...> wrote:

> Unfortunately I do not have another computer to do that

I found this GitHub project for DFU installation by Android app

1 - 20 of 24