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:
toggle quoted message
Show quoted text
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
