Print

[N3KXZ]

I posted this on https://groups.io/g/nanovna-users/ but no one has responded yet, so I am trying here.  can't tell if this is the proper forum on eHam to post this.

Just bought a new nanvovna SAA2-N. Attempting to flash an updated firmware. I found it difficult to determine which firmware to use- I tried nanorfe-20220814-vna6000.bin then I tried nanovna-v2-20201013-v2_74.bin, but neither of them worked properly.

So I then I followed the instructions from DiSlord here: https://github.com/DiSlord/NanoVNA-V2-firmware and had some trouble: got an error message saying "Unterminated quoted string". I then followed a suggestion from here: https://github.com/nanovna-v2/NanoVNA2-firmware/issues/73 and then at least the compilation seemed to complete.

However, after uploading that binary.bin (using VNA_View-x86_64.AppImage) the device now just gives me a blank screen, regardless of whether or not I hold the button while turning it on. VNA_View now does not recognize the device.

When I plug the nanovna usb into my system Dmesg now reports:

[16007.201932] usb 2-1.8: new full-speed USB device number 8 using ehci-pci
[16007.617950] usb 2-1.8: device not accepting address 8, error -32
[16007.701947] usb 2-1.8: new full-speed USB device number 9 using ehci-pci
[16008.117962] usb 2-1.8: device not accepting address 9, error -32
[16008.118190] usb 2-1-port8: unable to enumerate USB device

Here is what I started with:
SAA-2N
SN: 3555144B-00043333-35343234
Hardware designed by OwOComm
Build Time: Jun 9 2021 -17:36:19
Compiler: gcc
Port Info: GD32F303
Board: SAA-2N

I am using an updated Debian system.

Can someone help me out of this predicament? Or did I just brick this new device?

Thanks if you can help,
Keith

[W9WQA]

cant help, only advice.  buy a new one and just enjoy it...dont mess.
i never update anything that does what it is supposed to...
i have at least 10 items that could update, some 6+ yrs old working fine.
sorry.
i had to fix my "f" vna but it was not blank. looked inside.  no reset.
wonder why??

[K6SDW]

Same thing happened to me and an Arduino-based wifi clock....I like W9WQA's advice, buy a new one and enjoy it. I'm no expert but I wonder if you could upload the new unit's firmware data then copy that over to the broken VNA? Again, I'm no expert here.

Or, use this as a learning experience while trying to troubleshoot the VNA

GL/73

[HA3FLT]

Upgrading a firmware is part of the life of many equipments, it is sometimes desirable or even inevitable for security or functionality, etc. - especially if it is in the users manual like in this case, except the troubles finding the right version(s).

If the bootloader does not come up anymore (no white screen?), it really does not mean any good, it might have been erased or overwritten, but something may still function from the old firmware, that is why it seems to start reacting to the enumeration process of USB. This might turn out to be a not-so-educated guess, hi, but there are too few information avaiable at this point.

These error messages above are usually written in the log when there are power problems with the device, the communication isn't stable (cables, connectors), etc., so it may worth a try to change something about them.

If the hardware is ok but the bootloader still won't work, won't respond, there might still be a way to program the processor itself using a different, built-in bus or adapter. I don't know which kind of a processor is used for it, I have and older NanoVNA, does it need a programmer hardware or not, but you may have luck, search for it.

73 ..... Tibor

[N3KXZ]

Thank you Tibor HA3FLT. Yes, it still comes up with a white screen, but since the USB isn't  initializing I guess there's now no easy way to access the bootloader. I will need to look around to see if there is some work-around I suppose. I have of course tried changing cables and USB ports etc. Maybe it will only respond to a particular USB port? At this point I don't have any clue...

[KK4GMU]

The first one I bought was DOA.  The screen lit up but the menus wouldn't do their thing.   I wrote or called (can't remember which) and they said it is common for the slightest static discharge to do that to them.  They sent me a new one for free.  Surprised the daylights out of me. (NANO VNA-H)

[VK6HP]

You might find it useful to read Owen Duffy's commentary on enabling the bootloader via hardware.  It's not pertaining exactly to your hardware or situation but there's a good overview of what can be done.  See https://owenduffy.net/blog/?p=16699 .

I might add that's it's absolutely essential to identify the correct firmware before you start.  While re-loading/flashing is a fact of modern life, my experience is that it's not something to be undertaken lightly.  Often there is a reason for doing it but my observation is that the standard of verification and curation frequently leaves a lot to be desired.  That's nowhere more apparent than in the nanoVNA world, which displays the best and worst of open source development.

Good luck!

73, Peter.

[N3KXZ]

Thank you VK6HP, Peter. That is a great article ( https://owenduffy.net/blog/?p=16699) which explains a lot! I will need to read it over several times to understand if I have the tools and experience to apply it to my particular device. Also I will need to translate much of it to the Linux toolchain. But that article is the best info I have seen so far, thanks you much.

Keith
N3KXZ

[N3KXZ]

I want to report that I have finally gotten my SAA-2N working! Yay! I could not use USB to upload firmware onto it because for whatever reason the device would not accept a USB connection. I then read _all_ of DiSLord's github page (https://github.com/DiSlord/NanoVNA-V2-firmware) and saw that he also describes how to use the _serial bootloader_ with python3-serial (I'm using Debian). That _did_ work and I was finally able to upload his latest binary ('V2 480x320 v1.1.00.bin').

Now the device works, VNA_View can connect, and the device is now using the usb bus, though it says "Cypress Semiconductor Corp. CDC-ACM Demo" which I guess is because it is a clone?

Thanks to all who commented and helped me with this! It was the blog entry by Owen Duffy that Peter VK6HP posted that got me to thinking about how I might use a serial connection to fix the problem.

Keith
N3KXZ

[HAMHOCK75]

Now the device works, VNA_View can connect, and the device is now using the usb bus, though it says "Cypress Semiconductor Corp. CDC-ACM Demo" which I guess is because it is a clone?

That message means the proper USB driver is not installed on your computer. I ran across that same message with another version of the nanoVNA. See link below,

https://www.eham.net/community/smf/index.php/topic,136813.msg1271880.html#msg1271880

[N3KXZ]

I am using Debian Linux, not any flavor of Windows, so the drivers are supposed to be already included in my Linux distribution, and the Cypress driver is for Windows. So... I don't know why I m getting that message!

[KC3TEC]

As is the case with many drivers, you can search through the list of drivesr that displays but unless you know exactly what hardware versin it is, it may very well be a crap shoot.
Im a debian user as well  and im qiite used to the foibles of different drivers in the list.
Debian will display a list of drivers to choose from, but may not tell you which one is correct
( installing a printer is usually pretty straight forward, but some can give you fits)

As the others have posted with the price of a nanovna as low as it is. Its a safer bet just to purchase a new one than it is to do a frmware update.

Besides as long as it works you can sell the old one or keep it as a backup.

[KC3TEC]

Damnable small buttons on the phone!
Between those and auto correct, quite often the spelling and some sentences don't make sense.
Anyhow the nanovna while not a kilobuck level  device is a useful and easily portable device.
Even being menu driven is not bad but the instructions for use leave out a lot of information.
But you can sort through the dross on you tube and find some real gems.
I am having a blast with mine, and it sure makes an easy job of tuning an antenna.

But for a lot of what we do, it's a good idea to get a variety of the sma adapters to keep in your kit.

[HAMHOCK75]

N3KXZ

I always wondered if there was anyone writing firmware for the SAA2 other than the originators. It sounds like DiSlord's firmware works with it. Does DiSlord's firmware allow interpolating the calibration data? That was one of the worst behaviors of the original firmware that any change in frequency would require a new calibration.