开云体育

Ok, after a couple of months on the shelve my 2.8inch NanoVNA-H Hardware version is bricked (I think!).

From my reading online, it sounds to be common, I just hope newer firmware will prevent this?

I downloaded NanoVNA-H4_20210131.HEX from one of your posts, hope it is the correct version, there seem to be many variations.

And I have an ST-Link V2 Mini STM8/STM32 unit coming from Amazon.

just a bit confused (a lot) as to what software I need to do this. Obviously, I can not do a DFU process, since I can not communicate with the unit even holding the select center switch during powerup using DFUSeDemo, can't find any devices. Tried the select key in all possible positions during power-up Nothing!

The exact symptoms, before I jump to a conclusion, are at power-up get white high raster screen with no data or graphics, battery led (RED) is flashing at approx 1 pulse/sec, upon power-up the Blue System LED does show some random activity and then starts flashing at approx 1 pulse/sec.

the unit is enclosed in a plastic enclosure, opening it the PCB is ided as NanoVNA-H V3.4

If this unit is NOT Bricked, then how do I bring it back? Hard reset?

hope you can help me

Thanks

73

Richard G. Desaulniers Sr., VE2DX

Possibly the H4 firmware is for the 4” version – not the 2.8”?


From: VE2DX<mailto:ve2dx@...>
Sent: Tuesday, February 23, 2021 10:44 AM
To: [email protected]<mailto:[email protected]>
Subject: [nanovna-users] Bricked NanoVNA-H

Ok, after a couple of months on the shelve my 2.8inch NanoVNA-H Hardware version is bricked (I think!).

From my reading online, it sounds to be common, I just hope newer firmware will prevent this?

I downloaded NanoVNA-H4_20210131.HEX from one of your posts, hope it is the correct version, there seem to be many variations.

And I have an ST-Link V2 Mini STM8/STM32 unit coming from Amazon.

just a bit confused (a lot) as to what software I need to do this. Obviously, I can not do a DFU process, since I can not communicate with the unit even holding the select center switch during powerup using DFUSeDemo, can't find any devices. Tried the select key in all possible positions during power-up Nothing!

The exact symptoms, before I jump to a conclusion, are at power-up get white high raster screen with no data or graphics, battery led (RED) is flashing at approx 1 pulse/sec, upon power-up the Blue System LED does show some random activity and then starts flashing at approx 1 pulse/sec.

the unit is enclosed in a plastic enclosure, opening it the PCB is ided as NanoVNA-H V3.4

If this unit is NOT Bricked, then how do I bring it back? Hard reset?

hope you can help me

Thanks

73

Richard G. Desaulniers Sr., VE2DX

Hi Richard,

The term "bricked" is commonly used when irreparable damage has turned a device useless. In the context of firmware upgrades it refers to a failed upgrade that not only renders the device non-functional but also prevents any subsequent to repeat the firmware upgrade or to install any other firmware. This type of failure is common on microcomputers where the bootloader and the application code are a single firmware image that are being replaced together. However in the NanoVNA (all variants as far as I know) this type of failure is impossible because even if someone insists on installing the wrong application firmware, the bootloader is protected and all you need to do to recover is install the correct firmware.

Any original NanoVNA and NanoVNA-H (but not -H4!) can use the same firmware versions.
NanoVNA-H4 requires firmware made for NanoVNA-H4.
NanoVNA-F requires firmware made for NanoVNA-F.
NanoVNA2 requires firmware made for NanoVNA2.

I have a NanoVNA-H4 and it can be put in DFU mode (to install new firmware) by simply holding the toggle switch while turning it on. I'm not sure whether this is also the case on the NanoVNA-H (some 2.8 inch models of the NanoVNA require a jumper to be installed in order to put them into boot/DFU mode).

Therefore, stop panicking since your NanoVNA-H is not bricked (you just installed the wrong firmware made for the -H4 with a 4 inch display which is why you don't see anything meaningful on your 2.8 inch display).

Start by reading the excellent "Absolute Beginner Guide to the NanoVNA" (available in the Files section) and pay particular attention to the sections dealing with "Putting NanoVNA in DFU mode" and of course "The Firmware Upgrade Procedure".

73,
Thomas

Hi Richard,

I’m glad I wasn’t the first to point out that this mistake isn’t called a “brick”. Stop causing panic, because in his position, when not in use, this will not happen unless he has dropped and broken his display or walked on with his car. Then you can say it's a brick.

It appears from your description that you downloaded a 4 "version firmware for the 2.8" version. This is not good! This is a bad choice.
It’s good to have a ST-Link v2 hardware, but put that aside for now.
My first question is, what exactly did you do? He found it wasn't working.
What to do: First, make sure that the device battery is not exhausted.
If discharged first recharge and then turn on when it works: glad.
If it doesn't work and your battery is charged, I have an additional question:
Have you ever tried to use your device while connected to your computer?
You can connect to the computer via a COM port using a driver, in which case the device is visible in the device manager.
Possible in DFU (i.e. Device Firmware Upgrade) mode where it is NOT VISIBLE between COM ports.
In this mode, it is possible to upload (or download) the operating firmware to the device's microprocessor.
You can do this by uploading a .dfu file using DfuSe.
Before I write about a lot of things here, please read the article Using NanoVNA on my website.
There is a lot of help here. If reading these doesn’t help, ask where you got stuck.

Please don’t give up on someone whose solution is unknown, in despair. But this is not the case. There is help.
The 2.8 "-H device would require the installation of the DiSlord 1.0.45 firmware, which is the current latest.
If you have switched the device to DFU mode and do not log in in the solo mode after the firmware has been loaded, it will still remain in DFU mode.
That is, dfu must be loaded until it logs in after on / off.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

If we have managed to find a solution, please write it down, because we all learn from it. Thanks
--
*** If you are not part of the solution, then you are the problem. ( ) ***

ok!... Let me be clear... the unit was NOT loaded with -H4 firmware...

The unit was sitting on a shelf for a couple of months and when I pulled it out to use it it was... DEAD... Bricked... NOT WORKING... call ot as you wish it stopped working by itself not because I load -H4 firmware in it...

I tried running the DFU procedure and can not detect the unit, and yes I did follow the process to get the unit in DFU mode holding the Select switch while powering up, tried in all 3 possible position...

No I do not see any Jumplers on the pcb

I got myself an ST-Link V2 from Amazon, and I am simply looking for;

1- Software to download firmware in NanoVNA-H (Not using DFU!)
2- Proper site do download latest NanoVNA-H Firmware HEX file.
3- good site for step by step of the procedure

thanks for the help

73

Richard VE2DX

OK, was finaly able to get the NanoVNA-H in DFU mode and was able to find it in DfuSeDemo...

loaded the proper firmware DFU file and loaded it correctly as per the procedure...

the unit is still dead!...

While in DFU mode the Blue LED stopped flashing and did comeup in win10 as STM32 Bootloader like it should be...

the DfuSeDemo found the unit, I was able to load the proper firmware even did a VERIFY and confirmed it was loaded.

removed the jumper

rebooted the NanoVNA-H, blue led started flashing again and... wait for it... NOTHING

Just a white screen!

looks to me like the unit is not having firmware issues... instead I think this is a HARDWARE display issue???

comments or suggestions please

73

Richard VE2DX

Not to be offensive but have verified 3 volt and 5 volt power? LEDs lit>

Unsolved the battery and see if it runs when connected by USB. Sometimes, a dead liion battery will prevent the inverter from starting up.?


On Wed., 24 Feb. 2021 at 4:47 p.m., Charlie N2MHS via groups.io<ucfargis1@...> wrote: Not to be offensive but have verified 3 volt and 5 volt power? LEDs lit>

Richard, verify you can access the unit via the console through a terminal app like putty or teraterm. If you can access that way, you have a display issue.?
Some forum members, including myself, have had to resolver the display ribbon to the PCB.?


On Wed., 24 Feb. 2021 at 3:56 p.m., VE2DX<ve2dx@...> wrote: OK, was finaly able to get the NanoVNA-H in DFU mode and was able to find it in DfuSeDemo...

loaded the proper firmware DFU file and loaded it correctly as per the procedure...

the unit is still dead!...

While in DFU mode the Blue LED stopped flashing and did comeup in win10 as STM32 Bootloader like it should be...

the DfuSeDemo found the unit, I was able to load the proper firmware even did a VERIFY and confirmed it was loaded.

removed the jumper

rebooted the NanoVNA-H, blue led started flashing again and... wait for it... NOTHING

Just a white screen!

looks to me like the unit is not having firmware issues...? instead I think this is a HARDWARE display issue???

comments or suggestions please

73

Richard VE2DX

Hi Richard,
Okay, I see you've gotten to the point where you have a white screen (if all is true, it's because your device is in DFU mode).
Please turn it on if the screen is still white and I assume that because the display is not damaged, the device is in DFU mode.
In the earlier versions, the white state on the 2.8 "screens indicates the DFU mode.
This changes in later versions so that you can switch from the menu to the DFU state.

Important: the device cannot be used in DFU mode only firmware upload or download!
When connected to a computer in DFU mode, you should see "STM Device in DFU mode" in the USB controllers in Device Manager.
If you see this, your computer will see the device.
You can only change this if you upload the .dfu file correctly, which is a prerequisite for the tool to work.
If you make a mistake here and there is no hardware error, DFU mode will remain and the device cannot be used to measure.

If it is not visible, you need to short-circuit BOOT0 and VDD in the corner next to the battery on the device's motherboard when the power is off.
You insert a small wire into the hole galvanized hole, then turn on the device. Your device is now in DFU mode. Nano VNA_ (hw-3.4) .jpg
You can only change this if you upload the .dfu file correctly, which is a prerequisite for the tool to work.
If you make a mistake here and there is no hardware error, DFU mode will remain and the device cannot be used.

I attach an image The "Choose ..." and "Upgrade" buttons at the bottom right of the DfuSe Demo program must be used to upload.
(the one on the left is used to read the .dfu in the device). DfuSe_Demo_upgrade.png
Before I wrote this message, I also uploaded Hugen's 1.0.45 firmware to my 2.8 "device.
In this version, the captions are larger than the ones made by the original author DiSlord - I think it will be more readable for you.
Hugen_v1.0.45_screenshot.png

Once the firmware upload is successful, the power must be disconnected and remove BOOT0-VDD short-circuit, then turned on.
You must then log in correctly.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

Richard,

maybe these instructions might help you?
Absolute Beginner's Guide to The NanoVNA ,
Chapter "NanoVNA FIRMWARE UPGRADE".

It is in the files section of this group.

73
Martin 9A2JK

Hello Richard.

It seems like you're having similar problems to me yesterday.

It was diving me mad too.

The advice about reading the Absolute Beginners Guide to NanoVNA v1_5.pdf helped me out but it was a little bit convoluted.

For me, i went into device manager and could see that the STM32 was listed in Universal serial bus "devices" yet the device wasn't showing in the Universal serial bus controller as it should.

Even though my nanovna WAS in DFU mode as it was just a white screen.

I then right clicked on the device in Universal serial bus devices and selected update driver.
I then searched Browse my computer for drivers which gave the option to select Let me pick from a list of available drivers on my computer.

Here i found the driver for STM Device in DFU Mode which i selected and installed.

This then made available the STM device within the Universal serial bus controllers.

After this i was able to update the software with the NanoVNA-App as I could now connect to the software to run the firmware update.

Hopefully I've attached a screen shot of my driver upgrade and how it should eventually look after you update the driver.

I hope this helps and not add to your frustrations as I was ready to literally put a brick through my VNA yesterday morning HiHi.

Regards, James.

Just to add to this Richard, i could only see STM Device in bootloader in Universal serial bus devices within device manager before doing a right click and update driver which let me select the driver for STM DFU mode.

After this it disappears from Universal serial bus devices and should only then appear in Universal serial bus controllers.

Hope this helps, if not post again as to where your up to with it.

Regards, James.

Here is a list that I've made with the steps that I took to get the device to be seen by my compute Richard.

Hopefully others can expand on this if I've missed any steps out.

Hope it helps.

Connect your NanoVNA to the computer via USB.

Put the NanoVNA into DFU mode (Short out the Boot0 and VDD)

NanoVNA screeb should be white.

Open up device manager on the computer.

Look down the list of items and look for Universal serial Bus Devices.

Hopefully you will see STM Device in bootloader mode.

Right click the device.

Select update driver.

Select browse my computer for drivers.

Select Let me pick from a list of available drivers on my computer.

Make sure show list of compatible drivers is ticked.

You should be able to see an option listed as STM Device in DFU mode.

Select this and install this driver.

The STM Device should then show up in the Universal serial bus controllers as STM Device in DFU mode under Universal serial bus controllers.

Run NanoVNA-App software and use this software to upgrade the firmware.

There are two cogs at the top of the NnanoVNA-App software to run the upgrade process.

Running these will show another window with available firmware for your NanoVNA.

I selected the first option of firmware to choose from and went with that.

Regards, James.

Larry Battery issuesw is a valid point, I had tried that alrady sorry to say! :( Next!

Larry also very good point about trying via the Win10 app did not work will try terratem to see and let you know

James, thanks for the input, as I stated below l was able to get the device in DFU mode after shortening the pins (not a jumper on this version)

found the device...

was able to load it

but as I stated below, the unit boots up after power-up reset to a blank white screen

the unit cannot be reached via the VNA-QT application

note please I have another unit that CAN be reached with VNA-QT

BTW James THANKS for the step by step...

this will help others a lot... the shorting of VDD and BOOTI was confusing since most procedures and comments talked of a JUMPER... there was none here...

Sorry Richard, its two points not two cogs in the NanoVNA-App software to upgrade the firmware. Hopefully there's a picture attached.