¿ªÔÆÌåÓý

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

Missing driver for ChibiOS/RT Virtual COM port


 

I just received delivery of a NanoVNA-H and it works well stand-alone.

I tried to hook it up to my Windows 8.1 PC and ran unto problems. The driver is not able to install so I can't connect to NanoSaver.

Under device manger I find it under Other Devices as ChibiOS/RT Virtual COM port. When I right click under properties I get the following:

"The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver."

I tried updating the driver but no luck.

Anyone have an idea how to fix this or where to get the driver?


 

Roger,
Checkout the "Drivers" section of this group's "Wiki" page, /g/nanovna-users/wiki/home .

-Herb


 

Hi Roger,

The device manager shows the driver when it is working properly. There are more ways to see what's hidden. What I recommend is a utility called USBDeview, which shows you what driver programs have been installed on your computer since your operating system is running.
You can read the usage at the download site.

Green candidates at the beginning of the line are in use. Once selected, the right mouse button will bring up a menu and select what you want to do. It is advisable to remove any unknown drivers and then reinstall en.stsw-link004 (ST-Link Utility) or stsw-stm32080 (DfuSe), which will install the drivers as well. You may need these programs during firmware upgrade.
Successful use.

73, Gyula HA3HZ


Andy
 

On Sat, Nov 30, 2019 at 04:28 AM, Roger Need wrote:


I tried to hook it up to my Windows 8.1 PC and ran unto problems.

It's Windows, what else do you expect ?
Meanwhile in Linuxland...drivers..we don't need no stinkin' drivers ;-)

- Andy -


 

Use Zadig 2.4 to get USB STM32 downloader driver and STM32CubeProgrammer
for downloading the nanovna firmware 0.5.2 into the device.

Op za 30 nov. 2019 om 09:04 schreef Andy via Groups.Io <punkbiscuit=
[email protected]>:

On Sat, Nov 30, 2019 at 04:28 AM, Roger Need wrote:


I tried to hook it up to my Windows 8.1 PC and ran unto problems.

It's Windows, what else do you expect ?
Meanwhile in Linuxland...drivers..we don't need no stinkin' drivers ;-)

- Andy -




 

On Sat, Nov 30, 2019 at 09:04 AM, Andy wrote:


On Sat, Nov 30, 2019 at 04:28 AM, Roger Need wrote:


I tried to hook it up to my Windows 8.1 PC and ran unto problems.

It's Windows, what else do you expect ?
Meanwhile in Linuxland...drivers..we don't need no stinkin' drivers ;-)

- Andy -
yeah Andy,
do you think everyone is a pc guru?
people come here to ask for help, not education.
Successful use of linux until the first downfall. :D :D

73, Gyula


paul larner
 

well what a wank answer!!


 

On 11/30/19 1:02 AM, Gyula Molnar wrote:
do you think everyone is a pc guru?

???? I don't think everybody here is a PC guru, and because they aren't, they should be using Linux so they wouldn't have to worry about drivers.? Or rebuilding their computers after an update, or any of that other Windows stuff.


 

Thanks everybody. I got it working. I am leaving the answer here in case someone else with Windows 8.1 has the same problem.

When I plug in the USB you hear the Windows sound and see the driver trying to install but it fails. This can be seen in Device manager as an unknown device.

There are several ways to get the driver installed. One is by downloading Zadig. You run it and it finds the unknown device automatically. Then you select the Serial driver from the drop down list of driver options. Click install and now a virtual Com port driver is found under Ports.

The other way works very well too. Just run Windows Update manually and it finds the ST driver as an "Important Update". Click install and in a few seconds a virtual COM pot is ready for use. I think this is the same driver that is supplied built-in to the Windows 10 distribution.

To check that all is OK I ran NanoVNA Saver program and it found the device and I was able to connect and communicate with the NanoVNA.


 

On Sat, Nov 30, 2019 at 11:52 PM, Roger Need wrote:

¡­ I got it working. I am leaving the answer here in case
=============================================================

So installing the STM32 Virtual COM Port Driver from as suggested by this group's Wiki page did not work for you? If so then the Wiki needs to be updated by adding that Zadig is also required to properly install the serial driver for Windows versions below 10.

- Herb


 

So installing the STM32 Virtual COM Port Driver from
as suggested by
this group's Wiki page did not work for you? If so then the Wiki needs to be
updated by adding that Zadig is also required to properly install the serial
driver for Windows versions below 10.

- Herb
Herb,

I am new to this group and did not fully understand the driver reference in the Wiki when I made my original request for help. Since then I have made several driver install tests. I also tried downloading the driver from ST at the Wiki link and it did install correctly in Windows 8.1. It was exactly the same driver and version number (1.4) that Windows update installed. I checked to see what Zadig installed and it was a different driver called "libwdi" USB serial but it worked too.


 

On Sun, Dec 1, 2019 at 04:59 PM, Roger Need wrote:

I am new to this group and did not fully understand the driver reference in
the Wiki when I made my original request for help. Since then I have made
several driver install tests. I also tried downloading the driver from ST at
the Wiki link and it did install correctly in Windows 8.1. It was exactly the
same driver and version number (1.4) that Windows update installed. I checked
to see what Zadig installed and it was a different driver called "libwdi" USB
serial but it worked too.
==========================================================================

Roger,
Thanks for confirming that the driver located in the Wiki also works. You are not the only new member that has expressed difficulty initially locating the group's Wiki and Files section. In the future I will additionally provide a direct link when referring a member to either of those locations.

Once a member is familiar with the Wiki and Files sections they are able to do a lot of self-help on their own. Of course if you still have questions the more experienced users always seem glad to help out. I've found this group to offer mostly substance and very little pomp.

Enjoy using your NanoVNA!

- Herb


 

Hi Herb -

In the future I will additionally provide a direct link when referring a
member to either of those locations
Our Wiki main page has got rather long.
Breaking it into separate pages e.g. hardware vs firmware vs software vs documents vs drivers
might help for directing new folks, but then they might miss something useful in another page..?

I tried but failed to add headings for e.g. /g/nanovna-users/wiki#FIRMWARE
and don't know whether that Wiki trick is supported on groups.io or how to enable it...


 

Oristo,
You might want to browse a few other groups.io forums that have sub-pages and inspect their HTML to see how they are constructed.I have a feeling that feature costs $$ over the free version that is now in use.

On Monday, December 2, 2019, 10:55:52 a.m. GMT-5, Oristo <ormpoa@...> wrote:

Hi Herb -

In the future I will additionally provide a direct link when referring a
member to either of those locations
Our Wiki main page has got rather long.
Breaking it into separate pages e.g. hardware vs firmware vs software vs documents vs drivers
might help for directing new folks, but then they might miss something useful in another page..?

I tried but failed to add headings for e.g. /g/nanovna-users/wiki#FIRMWARE
and don't know whether that Wiki trick is supported on groups.io or how to enable it...


 

Hi Larry -

inspect their HTML
I can do that, but our Wiki pages seemingly do not support editing by html, only viewing.
If I figured out how edit the Wiki HTML, it would already be done.