I need some advice...

My Nano-VNA-H (Ver. 3.4) has operated well since I got it in 2020, and I've never had any problem either updating the f/w (the latest version in it is 1.2.20) or connecting to my laptop to operate Nano-VNA-Saver, although I haven't used it much lately (as one could tell from the f/w version).

I tried to connect it to my laptop the other day (Dell Inspiron with Win 11) to run Saver, but it wouldn't connect. I kinda figured that maybe the firmware needed updating, especially when I found out that the most recent DiSlord version was 1.2.40, so I d/l'ed NanoVNA-H.v1.2.40.dfu and went to  "https://www.st.com/en/development-tools/stsw-stm32080.html?s_searchtype=keyword", looking for STSW-STM32080 (DfuSe USB device firmware upgrade).  But there was a notice there that said:  "This product is NRND We recommend you that replacement part: STM32CubeProg".  So I went and d/l'ed that.  After trying to update the f/w with that, all of a sudden I have a bricked white-screen non-functional paperweight.  But under the Win 11 "Device Manager" I do see, under "Universal Serial Bus Devices", "STM32 Bootloader".

I tried the "fix a white screen" procedure, shorted Boot0 and VDD on power up, but I've got a broken paperweight. Should I just bite the bullet and buy a new 4" Nano-VNA-H or can anyone suggest a fix.  Please understand I'm almost illiterate regarding this stuff, and just got it for basic ham use.

Thanks.
Barry Leonard
KN4JRF
exusaf@...

Hi Barry,
I presume you read my prior response, and tried the ideas there. If not, please see https://groups.io/g/nanovna-users/message/38297 (under the prior topic).
The white screen is normally an indication that you are in DFU mode (on the -H; the -H4 has a black screen). So you likely had an incomplete/improper firmware download.
This is often caused by a bad cable, even if you see the device show up in Device Manager, or by using the wrong download file.
You do see the correct driver installed for STMCubeProgrammer. Good.
Since you are using the STMCubeProgrammer, and I presume you downloaded and installed it within the last couple of months, so you got version 2.17.0:
- you connect on the right-hand side of the programmer screen, selecting USB - you should be able to select a port and connect. When you do this successfully, it populates a bunch of stuff in the memory window.
- Did the memory window update with info?
- this programmer doesn't easily use the DFU files, so you need to go back to the github site and download the .bin file for nanovna-h (not H4).
- Did you get the .bin file? or did you try to use the .dfu?
- on the "Erasing and Programming" page, you need to "uncheck" the "skip flash erase before programming" box, so it clears the flash before programming. I check the "verify programming" box so it does a verification.
- then browse for the correct firmware .bin file in the download file path, and make sure start address is 0x8000000, then press "start programming".
- you should get lots of lines of info in the "log" section at the bottom, and a pop-up saying that programming completed successfully.
- Did this happen? If not, please try again, and see if the log messages tell you something, or save them and send them to me and I will look.
You can't brick your device, it is using a native bootloader inside the processor chip.
If it did successfully download, and you got the "Download verified successfully" line at the bottom of the log, and still only comes up with a white screen, then we need to look further.

If you want an excuse to get an H4 (which yes, is a much better device and my favorite), then ignore all this, say it is broken, and buy the H4. But odds are you can readily fix this with a proper download.

Stan, Thanks for the directions. You've given me some great options.
Being unfamiliar with the technology which makes the NanoVNA work AND the
details of the USB AND computer stuff in general, I need detailed
directions, which you supplied.

What I plan to do is fix my inop NanoVNA, sell it to someone who wants to
start learning about those things, and buy a 4" model.

Thanks again.

On Fri, Oct 11, 2024, 5:31 PM Stan Dye via groups.io <standye=
gmail.com@groups.io> wrote:

Hi Barry,
I presume you read my prior response, and tried the ideas there. If not,
please see https://groups.io/g/nanovna-users/message/38297 (under the
prior topic).
The white screen is normally an indication that you are in DFU mode (on
the -H; the -H4 has a black screen). So you likely had an
incomplete/improper firmware download.
This is often caused by a bad cable, even if you see the device show up in
Device Manager, or by using the wrong download file.
You do see the correct driver installed for STMCubeProgrammer. Good.
Since you are using the STMCubeProgrammer, and I presume you downloaded
and installed it within the last couple of months, so you got version
2.17.0:
- you connect on the right-hand side of the programmer screen, selecting
USB - you should be able to select a port and connect. When you do this
successfully, it populates a bunch of stuff in the memory window.
- Did the memory window update with info?
- this programmer doesn't easily use the DFU files, so you need to go back
to the github site and download the .bin file for nanovna-h (not H4).
- Did you get the .bin file? or did you try to use the .dfu?
- on the "Erasing and Programming" page, you need to "uncheck" the "skip
flash erase before programming" box, so it clears the flash before
programming. I check the "verify programming" box so it does a
verification.
- then browse for the correct firmware .bin file in the download file
path, and make sure start address is 0x8000000, then press "start
programming".
- you should get lots of lines of info in the "log" section at the bottom,
and a pop-up saying that programming completed successfully.
- Did this happen? If not, please try again, and see if the log
messages tell you something, or save them and send them to me and I will
look.
You can't brick your device, it is using a native bootloader inside the
processor chip.
If it did successfully download, and you got the "Download verified
successfully" line at the bottom of the log, and still only comes up with a
white screen, then we need to look further.

If you want an excuse to get an H4 (which yes, is a much better device and
my favorite), then ignore all this, say it is broken, and buy the H4. But
odds are you can readily fix this with a proper download.

IT WORKS!
The scan works, the correct version of firmware is in (1.2.40) and Saver
connects correctly.

I think it was d/l'ing the bin file, walking me through the STM32Cube
programmer and telling me that the thing can't be bricked.

Thanks again!

jbl

On Fri, Oct 11, 2024, 5:31 PM Stan Dye via groups.io <standye=
gmail.com@groups.io> wrote:

Hi Barry,
I presume you read my prior response, and tried the ideas there. If not,
please see https://groups.io/g/nanovna-users/message/38297 (under the
prior topic).
The white screen is normally an indication that you are in DFU mode (on
the -H; the -H4 has a black screen). So you likely had an
incomplete/improper firmware download.
This is often caused by a bad cable, even if you see the device show up in
Device Manager, or by using the wrong download file.
You do see the correct driver installed for STMCubeProgrammer. Good.
Since you are using the STMCubeProgrammer, and I presume you downloaded
and installed it within the last couple of months, so you got version
2.17.0:
- you connect on the right-hand side of the programmer screen, selecting
USB - you should be able to select a port and connect. When you do this
successfully, it populates a bunch of stuff in the memory window.
- Did the memory window update with info?
- this programmer doesn't easily use the DFU files, so you need to go back
to the github site and download the .bin file for nanovna-h (not H4).
- Did you get the .bin file? or did you try to use the .dfu?
- on the "Erasing and Programming" page, you need to "uncheck" the "skip
flash erase before programming" box, so it clears the flash before
programming. I check the "verify programming" box so it does a
verification.
- then browse for the correct firmware .bin file in the download file
path, and make sure start address is 0x8000000, then press "start
programming".
- you should get lots of lines of info in the "log" section at the bottom,
and a pop-up saying that programming completed successfully.
- Did this happen? If not, please try again, and see if the log
messages tell you something, or save them and send them to me and I will
look.
You can't brick your device, it is using a native bootloader inside the
processor chip.
If it did successfully download, and you got the "Download verified
successfully" line at the bottom of the log, and still only comes up with a
white screen, then we need to look further.

If you want an excuse to get an H4 (which yes, is a much better device and
my favorite), then ignore all this, say it is broken, and buy the H4. But
odds are you can readily fix this with a proper download.