¿ªÔÆÌåÓý

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

New user looking for guidance on firmware


 

Hi all,

Just got my NanoVNA. It is supposedly the 900MHz version.

I downloaded all the files from this site:



Also found the Git repo here:



Questions:

1. Is there a way to determine the version of firmware currently loaded?
2. Is there a detailed, English language version of the "how to load firmware" instructions, or only the semi-English version from the Google Drive site?
3. Any common mistakes or pitfalls to watch out for when loading firmware so I don't wind up with a brick?
4. What firmware version do people recommend? I have no need to measure above 500MHz.

Thanks!


 

Questions:

1. Is there a way to determine the version of firmware currently loaded?
1. [CONFIG] -> [VERSION] (requires recent firmware)
2. "version" command on USB serial] (requires recent firmware)
3. "info" command on USB serial shows build time (available with all firmware)

2. Is there a detailed, English language version of the "how to load firmware"
instructions, or only the semi-English version from the Google Drive site?
(dfu-util is multiplatform tool)


3. Any common mistakes or pitfalls to watch out for when loading firmware so I
don't wind up with a brick?
STM32 has DFU updater written in independent memory called "system memory".
The system memory is not writable by user, so there is no worry with a brick. You can write firmware again and again.

4. What firmware version do people recommend? I have no need to measure above
500MHz.
latest one, absolutely.


 

I've had mine for just over a week now.

I'm hoping you downloaded "STSW_STM32080_V3.0.6.zip" and a DFU file. Unzip
and install this program; this is the program for pushing the firmware to
your device.

You will also need to prep your device for uploading the firmware by first,
turning it off. Look for the jumpers near where power from the battery
connects to the board. If you look at my photo "NanoVNA1.jpg" you will see
two contact points that need to be jumpered. Just because I had it laying
around I used two clips I use for a multimeter with little hooks on one end
and stackable banana plugs on the other. By plugging one banana plug into
the other, I've made a cable with two little hooks that I can grab onto the
little holes in the mainboard. You can see my wires in NanoVNA2.jpg and
them jumpering the connection in NanoVNA3.jpg.

Now, with the USB cable connected to your computer, turn it. Open up Device
Manager on Windows 10. Scroll down to Universal Serial Bus controllers and
look to see if you have "STM Device in DFU Mode"; I've highlighted it in
NanoVNA4.jpg. Once you have confirmed this, open up the program you
installed earlier, called DfuSeDemo. It should automatically detect it. See
NanoVNA5.jpg. In that image, as you should see on your own computer, it has
selected "STM Device in DFU Mode." Now, click on "Choose...", which will
bring up the file manager to find your .dfu file. Once selected, select the
"Upgrade" button. Now, turn off the device, un-jumper it, then you can turn
it back on. I would recalibrate it before going any further.

I have not had any issues changing the firmware. My original firmware was
from May 2019. I then upgraded it to August. I then decided to try out the
1500 Mhz firmware I saw here on this group. I have an ADSB base antenna
tuned for 1090 MHz, so I wanted to see what would happen. I set a center
point of 1090 MHz with a span of 20 MHz and 10100 data points. The Return
Loss display is a real scatter graph and the Smith Chart looks like a very
fuzzy snake coil. The range of the noise follows a general path, just not
very clear. I find that on all firmwares, the best resolution comes between
about 200 KHz to almost 300 MHz, then it it gets fuzzy.
_____________________________________
Ron Webb



On Tue, Sep 17, 2019 at 12:23 PM aa777888athotmaildotcom <
scott.traurig@...> wrote:

Hi all,

Just got my NanoVNA. It is supposedly the 900MHz version.

I downloaded all the files from this site:



Also found the Git repo here:



Questions:

1. Is there a way to determine the version of firmware currently loaded?
2. Is there a detailed, English language version of the "how to load
firmware" instructions, or only the semi-English version from the Google
Drive site?
3. Any common mistakes or pitfalls to watch out for when loading firmware
so I don't wind up with a brick?
4. What firmware version do people recommend? I have no need to measure
above 500MHz.

Thanks!




 

Thanks for the great responses, all.

I don't care to stand up any instance of Ubuntu, no machines, Dockers, whatever. I don't want to build source.

When I download the latest release .zip file (0.1.1) I see a ch.bin, ch.elf and ch.hex. Are any of those usable with Windows DfuSe?

Thanks!