He was referring to Linux and Windows versions of STM32CubeProgrammer, not
the firmware. However you get the firmware there, it's running on an ARM
microcontroller that doesn't run a full OS at all.
DfuSe Demo not working on modern machines is a known issue and STMicro
won't fix it. That software is no longer supported (though you can still
download it) and STM32CubeProgrammer is the recommended replacement.The new
software does not appear to have any problems with running on new
computers. Those of you who have a tinySA or a DMR radio from China will
encounter the same issue with those; they also use DfuSe Demo or
STM32CubeProgrammer to update their firmware.
toggle quoted message
Show quoted text
On Sun, Aug 21, 2022 at 5:15 PM Tim Dawson <tadawson@...> wrote:
Jeff -
I'm glad that my doc was useful to you! Please be aware, though, that
there is no "Linux" or "Windows" version of the firmware. The dfu is simply
an encapsulation of the same image that is in a .nin (or .hex) for that
matter. The different tools just jse the different packages - IE Cube on
Linux or Windows will want the .bin, and the various dfu based tools will
want a dfu, again, on either platform.
I'm not sure how many revisions you jumped, but the one thing that can
bite you is an incompatible config file. Try resetting the NanoVNA to
defaults and reconfigure, if you have not do e so already.
Oh, and can't say that I have seen that bug, but I have not used my unit
much since that upgrade either - others likely know more on the topic.
- Ti
On August 21, 2022 3:03:29 PM CDT, Jeff Peacock <km6nqx@...> wrote:
TL:DR I upgraded my NanoVNA-H to DiSlord 1.1.01 and now Marker min is max
and max is min. Is this a known bug or did I mess up the upgrade?
The details I know you'll want:
I'm running Windows 10 on a HP EliteBook. I tried every possible set of
instructions to upgrade with DfuSeDemo, but was never able to see the
NanoVNA in DFU mode. I mean, every possible variation. I've installed and
uninstalled DfuSeDemo and various versions of the driver so many times in
so many ways I could do it in my sleep. I would have asked for help except
I suspect you lot are sick and tired of newbies asking for help updating
firmware. But here I am...
Finally I noticed a comment that STM32CubeProgrammer has worked for Linux
and found a PDF from Tim Dawson (
/g/nanovna-users/message/28607) on how to do it and
decided to give it a try on the theory that if the Linux version worked
there's no reason why the Win10 version shouldn't work. I was able to find
a .bin file from Huygen ()
and loaded it following the instructions with no issues. I should probably
mention that I used the NanoVNA-H-SI version, not the NanoVNA-H-MS version.
My NanoVNA is a few years old and reading creatively between the lines it
seemed like MS might be some newer technology, so SI seemed the safer
route. No errors - I compared the file with the image, perfect match.
When I started the NanoVNA everything seemed to be working as expected,
with a few menu changes and wording modifications, but nothing I couldn't
figure out. Then I connected my antenna to run it through it's paces and I
noticed that when I select my SWR marker and select Marker -> Minimum it
work immediately move the marker to maximum SWR, and v.v.
So, the question is - is this a known bug or something I messed up in the
upgrade, or an advanced setting of some sort that I can change?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Shirley Dulcey KE1L