NanoVNA V2 / Forum

Note: this page is a mirror of https://groups.io/g/NanoVNAV2.
Click here to join and see most recent posts.

Update fail


Bepisat Betanelli 2020/10/07 02:10

Hello friends,
I bought the NanoVana-2 and I'm satisfied with it, I wanted to upgrade the firmware and so I put the vna in dfu mode connected to the computer and launched the QT program. Following the procedure for the upgrade, the program gave me fail update several times, I did not understand if it was a windows problem, the fact is that now I turn on the nanovna and it gives me a blank screen and connected to the usb it is no longer recognized. I ask you if there is another way to program the firmware, thanking you for your reply, my greetings Diego.

Dragan Milivojevic 2020/10/07 14:03

Get a st link programer,
cheapest clone from ali or ebay or the one usually
embedded on ST development boards would work.


On Wed, 7 Oct 2020 at 12:25, Bepisat Betanelli via groups.io <bepisat=
yahoo.it@groups.io> wrote:

Udo Richter DG8MCQ 2020/10/07 23:52

@Diego -
recently I also run into unknown flashing problems, and I was not able to figure out what the root cause was.
I can not say that Win10 is or was the bad guy, but at least it was involved ...
So - my recommendation would be => Try an other PC or OS.
Win-8.1 on my Laptop at least solved my flashing problems!
Set your nanoVNA into DFU mode by holding down the left button while switching on, unless the white screen appears, and try flashing again.
Don't worry, you did not brick your unit.
Regards, Udo

Siegfried Jackstien 2020/10/08 19:05

i guess (but remember its just guessing) that win10 had the security
setting NOT TO WRITE BIN FILES

that may have caused that problem with flashing on the w10

as udo reported ... he tried on a w8.1 laptop and it worked fine

greetz sigi dg9bfc

Am 08.10.2020 um 06:52 schrieb Udo Richter DG8MCQ:

David J Taylor 2020/10/09 08:54

i guess (but remember its just guessing) that win10 had the security setting
NOT TO WRITE BIN FILES

that may have caused that problem with flashing on the w10

as udo reported ... he tried on a w8.1 laptop and it worked fine

greetz sigi dg9bfc
===========================================

I think your guess was wrong. Security has been pretty similar since
Windows-7.

However, if the .ZIP archive hasn't been unblocked [right-click, properties,
unblock] before unzipping, it's possible that could cause a problem.

73,
David GM8ARV
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
Twitter: @gm8arv

Bepisat Betanelli 2020/10/17 02:49

Thanks Udo for your answer, the problem is that the processor has reset the firmware and now when I turn on the nano it shows me the white display and I can't give any command because it is without software. Now I try with the stm programmer but I have to check the settings because from the instructions read here on the forum it continually gives me "parameter out of range". Thanks again 73 de in3mcy Diego.

mce66 2020/10/17 04:32

Hello,

I had a similar problem. The Nano has the FW corrupted but may still have the bootloader intact. The problem is to put the Nano in DFU mode. Simpler way is to switch on Nano keeping pressed the left or right button (maybe you can press all three...). You will not notice any difference if DFU mode succedded (screen remains white) but if you now connect the usb, windows will recognize the device.

Now start NanoVNA-QT and connect to NanoVNA. It will recognoze the device is in DFU and propose you to upload new FW.

Use always good USB cables...

Best regards, Marco.

Clifford Heath 2021/02/09 14:54

For the benefit of anyone finding this message thread, the GD32F303 MCU does *not* have a DFU mode. It has a serial bootloader, which can only be put there originally with an ST-Link.

This bootloader mode calls itself DFU, but it is *not* DFU as defined in the USB specifications: <https://www.usb.org/sites/default/files/DFU_1.1.pdf>.

You cannot update the firmware using DFU. You can update it using an ST-Link or with one of the NanoVNA apps that supports the bootloader, as long as your bootloader is still intact.

Anyone using an ST-Link should know that the bootloader loads at address 0x8000000 and the firmware at 0x8004000 - this is an undocumented trap for young players. And for me :)

To reply to this topic, join https://groups.io/g/NanoVNAV2

View this thread on groups.io