¿ªÔÆÌåÓý

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

Firmware Won't Update


 

Hi All, had my VNA-H for a short while and decided it was time to update it, mine is board V3.3, firmware 0.2.3.2, using DFUse, I put my unit into DFU mode and uploaded the latest upgrade. As i have the DFU option in my config, i assume i did not need to short the 2 pins together, that said, the software showed success at every stage, but my device is still stuck on its original firmware, help please.

Dennis G8IMN


 

Hi Dennis,

I think the solution is written here:
/g/nanovna-users/topic/51160730

if not, use and read the wiki description
it seems to me that for the first time the lack of a driver between the computer and nano is the source of the problem.

73, Gyula HA3HZ


 

Hi Guyla, I'm sure it's connecting with the pc, it works with vnasaver, and when placed in dfu mode, shows up correctly in usb devices, also the upgrade software shows complete success.

Dennis G8IMN


 

This may be a stupid remark but:
The DFU "Upload" is for making a backup of your nanoVNA flash memory to you PC
Use the "Choose" and "Upgrade" keys to update the firmware

--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK


 

Hi Dennis,

To date, I've only upgraded the firmware once with the ST-Link dongle because it was in my account for a different reason.
I had no problem with that, otherwise someone would recommend it if DfuSE fails the upgrade.
You can also find a detailed description in the wiki or on my site (ha3hz.hu).
Hope I was able to help with upgrades.

73, Gyula HA3HZ


 

Hi Gyula
Eric provided the solution, I was basically saving and reusing my existing firmware, but all sorted now, so thanks to all for your help.

Dennis G8IMN


 

Is there a solution for this. Mine alwch> info
Board: NanoVNA-H
2019-2020 Copyright @hugen NANOVNA.COM
Based on @DiSlord @edy555 source, licensed under GPL.
Version: 1.0.45 [p:101, IF:12k, ADC:192k, Lcd:320x240]
Build Time: Jan 30 2021 - 21:59:04
Kernel: 4.0.0
Compiler: GCC 8.3.1 20190703 (release) [gcc-8-branch revision 273027]
Architecture: ARMv6-M Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
ch> version
1.0.45
ch>ays reports 1.0.45 even after firmware upgrade to 1.1.00 DfuSe shows a successful upgrade but after reboot the firmware back at 1.0.45


 

DfuSe uses weird terminology. "Upload" means to take a snapshot of the
device and save it on your PC (it uploads from the VNA to your computer?)
You have to use the box on the right to download to the VNA - not the
"Upload Action".
Pick the file using "Choose", then click on the button to the right to
download that, or install that, into the VNA.
(Some versions of the DfuSe utility changed the "Download" text to read
"Upgrade", making the right-hand box easier to understand.)

If an upgrade/download with the "Verify after download" is checked (and
doesn't get any errors!) doesn't result in a firmware update, then that's
pretty strange.

Also - if you did a Upload and chose the firmware file for 1.1.0, you've
just overwritten that file with the 1.0.45 code. That means that a
correctly done Update/Download just reinstalls the existing code. Pull a
new copy from the internet.

73,
-Rick

On Fri, Dec 31, 2021 at 1:01 AM Jim Barber <jimpbarber@...> wrote:

Is there a solution for this. Mine alwch> info
Board: NanoVNA-H
2019-2020 Copyright @hugen NANOVNA.COM
Based on @DiSlord @edy555 source, licensed under GPL.
Version: 1.0.45 [p:101, IF:12k, ADC:192k, Lcd:320x240]
Build Time: Jan 30 2021 - 21:59:04
Kernel: 4.0.0
Compiler: GCC 8.3.1 20190703 (release) [gcc-8-branch revision 273027]
Architecture: ARMv6-M Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
ch> version
1.0.45
ch>ays reports 1.0.45 even after firmware upgrade to 1.1.00 DfuSe shows a
successful upgrade but after reboot the firmware back at 1.0.45





--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA


 

The Dfuse issue you describe has been discussed many times

...and that is why it says in the forum's Wiki there is an alternate exe file I created that renames those buttons.
Unfortunately, many forum members don't read the Wiki. (Sigh)
.?


On Fri., 31 Dec. 2021 at 8:15 a.m., Rick Murphy<k1mu.nospam@...> wrote: DfuSe uses weird terminology. "Upload" means to take a snapshot of the
device and save it on your PC (it uploads from the VNA to your computer?)
You have to use the box on the right to download to the VNA - not the
"Upload Action".
Pick the file using "Choose", then click on the button to the right to
download that, or install that, into the VNA.
(Some versions of the DfuSe utility changed the "Download"? text to read
"Upgrade", making the right-hand box easier to understand.)

If an upgrade/download with the "Verify after download" is checked (and
doesn't get any errors!) doesn't result in a firmware update, then that's
pretty strange.

Also - if you did a Upload and chose the firmware file for 1.1.0, you've
just overwritten that file with the 1.0.45 code. That means that a
correctly done Update/Download just reinstalls the existing code.? Pull a
new copy from the internet.

73,
? ? -Rick

On Fri, Dec 31, 2021 at 1:01 AM Jim Barber <jimpbarber@...> wrote:

Is there a solution for this.? Mine alwch> info
Board: NanoVNA-H
2019-2020 Copyright @hugen? ? NANOVNA.COM
Based on @DiSlord @edy555 source, licensed under GPL.
Version: 1.0.45 [p:101, IF:12k, ADC:192k, Lcd:320x240]
Build Time: Jan 30 2021 - 21:59:04
Kernel: 4.0.0
Compiler: GCC 8.3.1 20190703 (release) [gcc-8-branch revision 273027]
Architecture: ARMv6-M Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
ch> version
1.0.45
ch>ays reports 1.0.45 even after firmware upgrade to 1.1.00? DfuSe shows a
successful upgrade but after reboot the firmware back at 1.0.45





--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA


 

Larry,
I'm using your patched DfuSe tool. Makes it a lot easier to understand what
you're doing.

It is unfortunate how many people clearly didn't bother to look at any of
the resources here.
-Rick

On Fri, Dec 31, 2021 at 10:15 AM Larry Rothman <nlroth@...> wrote:

The Dfuse issue you describe has been discussed many times

...and that is why it says in the forum's Wiki there is an alternate exe
file I created that renames those buttons.
Unfortunately, many forum members don't read the Wiki. (Sigh)
.


On Fri., 31 Dec. 2021 at 8:15 a.m., Rick Murphy<k1mu.nospam@...>
wrote: DfuSe uses weird terminology. "Upload" means to take a snapshot of
the
device and save it on your PC (it uploads from the VNA to your computer?)
You have to use the box on the right to download to the VNA - not the
"Upload Action".
Pick the file using "Choose", then click on the button to the right to
download that, or install that, into the VNA.
(Some versions of the DfuSe utility changed the "Download" text to read
"Upgrade", making the right-hand box easier to understand.)

If an upgrade/download with the "Verify after download" is checked (and
doesn't get any errors!) doesn't result in a firmware update, then that's
pretty strange.

Also - if you did a Upload and chose the firmware file for 1.1.0, you've
just overwritten that file with the 1.0.45 code. That means that a
correctly done Update/Download just reinstalls the existing code. Pull a
new copy from the internet.

73,
-Rick

On Fri, Dec 31, 2021 at 1:01 AM Jim Barber <jimpbarber@...> wrote:

Is there a solution for this. Mine alwch> info
Board: NanoVNA-H
2019-2020 Copyright @hugen NANOVNA.COM
Based on @DiSlord @edy555 source, licensed under GPL.
Version: 1.0.45 [p:101, IF:12k, ADC:192k, Lcd:320x240]
Build Time: Jan 30 2021 - 21:59:04
Kernel: 4.0.0
Compiler: GCC 8.3.1 20190703 (release) [gcc-8-branch revision 273027]
Architecture: ARMv6-M Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
ch> version
1.0.45
ch>ays reports 1.0.45 even after firmware upgrade to 1.1.00 DfuSe shows
a
successful upgrade but after reboot the firmware back at 1.0.45





--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA











--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA


 

"Clearly", and actually people do look at the resources.

However, the issue is not that the firmware was backed up because I actually followed the instructions. I have 3 of these and have never had issues using the DFUse tool before. The other two flashed fine. One before and one after.

I am experiencing something different and was just looking for some insight, not beratement.

I will try with a different unit. I have a few. I believe this one must be a bad clone or something as it is new.

Maybe I will try a different flash tool. I have flashed everything from Automotive computers up to high-end Core Internet routers and just find this a bit frustrating at the moment.


 

Jim,

I was actually speaking in general terms, and yes, there are quite a number of folk that do use the Wiki.

There is a simple way to verify if that 1.1.0 file you have is ok and that is to open it in Wordpad or a hex editor that can display ASCII strings. Look close to the end of the file and you will see the copyright strings and the version number.

The Dfuse utility has confusing names for its buttons and I changed their meanings to be more standardized.

The only time that anyone on the forum has described what you're saying, is when they backed up the FW from the device to the file they were trying to flash, overwriting it.

Download yourself a new copy of 1.1.0, install my modified dfuse exe file and flash.

Have a safe and Happy New Year