Al,
Just to verify: if you turn the device on, it's working with some version
of NanoVNA firmware.
It's not dead or bricked, it's just running firmware that's missing
features and you're trying to re-flash it.
The way you've been describing this has all of us assuming that it's
bricked because you keep using that word, but "bricked" means completely
dead, nonfunctional, where the only thing it's good for is a paperweight.
If it's running some level of NanoVNA, has a good display, then it's
working OK. The chances that this isn't able to get into DFU mode is
pretty low.
Please verify that it's in fact working.
73,
-Rick
toggle quoted message
Show quoted text
On Thu, Jan 26, 2023 at 2:47 PM Al Waschka <awaschka@...> wrote:
I didn't answer your question about the source of my firmware. I can't
find the specific download site, but it was listed in "NanoVNA Very tiny
handheld Vector Network Analyzer User Guide" by gen111.taobao.com:
The 800MHz firmware works better at higher temperatures.
nanoVNA_800_ch£º50K-900MHz£¬5*7 Bitmap font£¬4 tracks(Recommended)
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Stan
Dye
Sent: Thursday, January 26, 2023 1:21 PM
To: [email protected]
Subject: Re: [nanovna-users] New Problem (Bricked?) Re: Trouble Setting Up
DFuSE Driver
So based on your detailed description, there are two other possibilities I
see in addition to what Gyula and others have noted:
1 - Infant mortality. Sometimes electrical components fail. If this all
happened within the first several hours of power-on of your nano, something
inside could have gone kaput. It would have to be the STM-32 processor or
some of the discrete logic forming the USB interface to the processor.
2 - Bad firmware, i.e not made for your device. It is conceivable, though
rare, that an incorrect firmware could put the hardware in a mode that
would cause it physical damage. For example, putting two gpio pins in
output mode that were externally connected together, or externally driven.
Or a firmware that was purposely created to make havoc. So that would beg
the question, where did you get this "800" firmware that you used from? (I
personally have never heard of it.) Are you sure it was created for a
nanovna-H model?
Sidenotes:
1 - I would personally do the linux test that was suggested, it may reveal
something.
2 - The 0.50 Hugen firmware that I think you said was in your device was
excellent firmware, stable and with a good set of features which may have
given you lots of good service (I used it for many months before
updating). We are often encouraged to upgrade when there is no real reason
for our use case to do so.
3 - Other than the intellectual challenge, how many hours of effort is a
$50 part worth? It may be better to give more value to your time, and get
a new nanovna-H4 (or maybe a litevna64 if you need accuracy on >>1.5GHz
frequencies) - these have hardware advantages, and are not much more
expensive.
Stan
On Thu, Jan 26, 2023 at 9:46 AM Al Waschka <awaschka@...> wrote:
You are telling me to use DFU mode to fix the problem and I have
repeatedly said I can't get into DFU mode and told what I have done to
try.
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of
HA3HZ
Sent: Thursday, January 26, 2023 12:28 PM
To: [email protected]
Subject: Re: [nanovna-users] New Problem (Bricked?) Re: Trouble
Setting Up DFuSE Driver
I'm starting to feel like I want to help a person cross the busy road,
but he doesn't want to cross. While he was asking for help.
--
Gyula HA3HZ ( )
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA
