On Sun, Mar 26, 2023 at 08:32 AM, <vitaliy_kh@...> wrote:

As a side effect this Driver did create me a very real disaster.
To begin with - all of my NAS Disks became invisible and inaccessible.
Plus System became extremely unstable.
I spent about 6 hours for restoring my System to the original state state.
(I hope, I did restore everything to the original point.)

This is the sort of thing that makes me wonder why people still use this unstable, flaky operating system: Windows.? This sort of thing just doesn't happen with Linux.

开云体育

Hi,

@hwalker - I had *not* seen your post #10798 - following it easily allowed me to upgrade my firmware - thanks! At step #13 I selected the file that I'd downloaded previously (and had renamed "tinySA.bin" per the instructions at tinysa.org) and it worked like a charm. I will have to make a copy of that post and keep it with my TinySA documentation for future reference :)

On Mon, Mar 27, 2023 at 06:38 AM, Bill Cromwell wrote:

Anything beyond a nonjudgmental suggestion should be left out

OK, here's my nonjudgmental suggestion: if vitaliy is worried - and, apparently rightly so, based on his report - that something as simple as installing a driver might trash his Windows system, maybe he should try running Linux from a USB stick, which makes no changes to any operating systems or files installed on the drives in the computer, and update his tinySA from there.? It's easy to do, and would only take a few minutes.? End of nonjudgmental suggestion.

开云体育

Hi Jim,

I have tried about everything proposed in this topic and others at the NanoVNA forum and have given up trying to use my WIN-11 tablet to update the Ultra. Lucky, I still have a WIN7 computer that I use to run some older test equipment and that one, combined with the tinySA-app works like a charm. New OS software is not always better.

John

I've been reading this thread and haven't put in my two-cents yet so, for what it's worth, here's my two cents . . .

I use both a Dell laptop with Windows 10 Pro and a Dell desktop with Windows 10 Pro.? I learned a long time ago to make backup image files of my C: drive for various computer configurations so I can reload the image if something gets corrupted installing new software or experimenting with system settings or a virus infects my computer.

One of my backup images is set up for my custom software I use for my part-time work supporting a custom product for a customer.? It also happens to work with zero problems with updating my TinySA Ultra using DfuSe Demo (v3.0.6).? Then I have another backup image configured for things not work related and is used for my video editing and other "fun" things.? And that configuration will not work with DfuSe Demo no matter how hard I try.? I have no idea why the difference and I really don't worry about it since I have a backup image that works with the DfuSe Demo utility program.

I also have a backup image of just a fresh install of Windows 10 Pro in case I want to try installing new software and not have to deal with the possibilities of other software drivers or configurations causing issues with a new software install.

I use Acronis for my backup images but there are other programs out there that will allow you to make an exact backup image too and boot off a thumb drive or CD instead of your hard drive to make images or recover images.

Don't rely on the Windows recovery utility built into the OS!? You'll not get reliable results like you will with an actual recovery image of a known working system.

Hi Vitaliy,

Your problem sounds somewhat similar to a problem I previously had, and below is the copy of my posting that documents my solution.
———————-
Thought I should close this post with the procedure that eventually worked great for me.? I posted this in a different post/thread but thought it might help others in the future that stumble upon this post/thread.

Sorry about the graphics not showing up in my post, and I believe you can find the graphics showing this in post #5577 by Steven Reed, and below is the process I used based on Steven Reeds graphics.

What finally worked for me is as follows.

I used device manager to see what device my TinySA was showing up as with my TinySA connected to my computers USB port and when I then selected the DFU mode on the TinySA.? In my case my device showed up under "Other devices, and under that it said STM BOOTLOADER"? Then using device manager I right clicked on "STM BOOTLOADER" and selected "Update driver", then I selected "Browse my computer for drivers", and then I gave it the following path for the search "C:\Program Files (x86)\STMicroelectronics" and told it to include subfolders for the search.? Windows then successfully found the correct deriver and then DfuSe Demo had no problem recognizing my TinySA when I put the TinySA in DFU mode and I was then able to update the firmware in my TinySA using DfuSe Demo.

The above procedure worked great, whereas everything else I tried failed.

Don (wd8dsb)
——————
Don

On Mon, Mar 27, 2023 at 03:38 PM, Bill Cromwell wrote:

Anything beyond a nonjudgmental suggestion should be left out. I am a long time Linux user and I can testify that Linux has its own pitfalls, just as the other popular operating systems.

Hi Jim and gang,

I ran into similar issue as Vitaliy (driver not found) using Windows and the only thing that worked for me was to tell windows the path to use to find the driver and I told it to include all subfolders.? The driver really existed but Windows was not smart enough to find it on its own.? Until I told it the correct path to use and to include all subfolders nothing would work and it was really a frustrating process, but since then all is well.

Just FYI,
Don

Hello Don!

Please download driver for NanoVNA here



This driver from program DfuSeDemo 3.0.6 for Win7, Win8. Windows 8.1 and Win10. I use this driver for NanoVNA-H, NanoVNA-H4 and TinySA 2.8. Setup program from DfuSeDemo install this driver not automatically.?
DfuSeDemo, NanoVNA-APP, TinySA-APP use this driver for work and FW update.

73 de Vladimir, dl7pga

Hi Vladimir,

My system is working fine but a year ago I had the problem similar to Vitaliy.? The problem was that the original path was too deep and Windows blew right past it while looking for it.? Here is a copy of more text from me that I posted a year ago that help explains it.
-----------------------------------------
Hi Will,

I figured it out after digging through some other posts.? Windows was finally able to find the correct drivers and install them after I gave it a less detailed path.? Originally I gave it a very detailed path based on another poster and it turns out the path was too deep within the STM software path.? I finally came upon a posting by Terry where he showed the path that I should use to allow Windows to update the driver and below is what he advised, and it worked great, and I was then able to use DfuSeDemo to upgrade my TinyVNA software, but it ate up all day to get there.

Thanks,
Don wd8dsb
-------------------------------------------------------

Terry,

Go through the process of updating the driver anyway.? Click on the STM32 Bootloader under USB Devices and find your way to the button to update the driver.? Then select the following location exactly like this "C:\Program Files (x86)\STMicroelectronics".? Be sure “Include subfolders” is checked.
--------------------------------------------------------

On Tue, Apr 4, 2023 at 06:50 AM, Donald Kirk wrote:

I ran into similar issue as Vitaliy (driver not found) using Windows

I'm not sure that Vitaliy's problem is simply "driver not found."? He has some concern - apparently justified - that installing the driver in Windows will cause other problems in his system.? When he installed the driver, he lost access to his network attached storage and had to spend hours getting his system back to a functioning state again.

Vitaliy, I have loaded antiX Linux onto a USB stick, installed dfu-util, and remastered the iso into something I could post on the web, you could download it and burn it to a USB stick, boot your computer to it, and do your tinySA updates from there.? The only thing you would have to do is point your computer to the USB stick at boot time.? A lot of computers automatically look for boot alternatives and would present the Linux USB stick as an option to boot to.? If your computer doesn't do that, it would probably show a message like "Hit F12 for boot options" or something like that.? I've been playing with this just to confirm that it works, if you're interested I can improve it a bit more.? As is, you'd have to open the browser (I can set the home page for the browser to the tinySA firmware download page), right click the .bin file to save it, connect the tinySA to the computer, then open a terminal (I can put an icon on the desktop for this) and enter this command:

dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D ./tinySA4_v1.4-72-gf8c2707.bin

I can put the command in a text file so you'd just have to copy/paste it into the terminal.? Currently, you would have to change the name of the file to the most recent .bin file, but I can probably make a short script/batch file that will automatically use the most recent .bin file, and all you'd have to do would be to click an icon on the desktop.? If you're interested, I can polish this up a bit and put the Linux iso up on the web for you to download and burn to a USB stick, or I could mail you a ready to use USB stick.

Anyway Vitaliy, there's my offer.? You want to keep doing battle with drivers on Windows, or you want to update your tinySA Ultra from Linux?

Oh, I chose antiX Linux for this because it's small and simple compared to most Linux distributions, and it has easy to use tools to add "persistence" to a Linux distribution on a USB stick (allows you to install programs and store files on the stick), and to "remaster" the files on the USB stick to include added programs - like dfu-util - as though they were part of the distribution as it came "from the factory."

The OP has solved his firmware update problem....

Vitaliy seems to have vanished after he got his problem fixed last week and was able to fix his problem.
He posted about it in a topic I started describing how the Win 10/11 Memory Integrity setting can block the STM DFU driver from being installed.? Here is a link to the discussion for those interested ...
/g/tinysa/topic/97866810#10816

Roger

On Wed, Apr 5, 2023 at 11:42 AM, Roger Need wrote:

The OP has solved his firmware update problem....

It would have been nice if he had announced in the original thread he started about his firmware update problem that the problem had been solved.? You know, like how he wanted all the files in one place, it would have been nice to have the announcement of the problem and "hey, the problem has been solved" all in one place.? Oh well, I had fun experimenting with persistence and remastering on Linux "live" USB sticks.? But I don't think I'd be very inclined to spend any time in the future trying to help the original poster.? One could waste a lot of one's time working on problems he doesn't bother to let us know have already been solved.

On Sun, Mar 26, 2023 at 03:38 AM, hwalker wrote:

10. After getting a message that the driver was installed, switch on theTinySA Ultra while holding down the thumb wheel switch. You should hear a connection detected sound from the PC and the TinySA's screen should remain dark indicating it is in the DFU mode.

Could you please give us a winziped? I couldn't unzip rar files on my pc.