开云体育

Yes, I put DFUdemo on my wife's laptop, and it too didn't find the tinySA, which was in DFU mode. In the folder shown below, I opened the *version.txt* file, and it said to double-click on

Hey Terry, apparently the DFU driver is not loading and showing up in the USB Devices section. This driver (two of them) are installed with the DFUdemo program from ST Micro. I’m not around my

Ted, I'm good until your step 3. Going into DFU mode clears the COM port line and adds the 'Universal Serial Bus devices' line, which has no drop-down. What next? And where do I find the driver I

Good Morning Terry, Take a look at this to see if the unit is setting up correct drivers as noted by Ignacio: 1. Go into Device Manager and look at the ports section. Connect the TinySA and turn ON. A

ok. what to do- in the search box of the PC type cmd <enter> then when it gives the suggestion rt click then run as administrator. you will get a black dos screen. then cd (change directory) to the

Is this what I'm looking for?

Ignacio, No, this is my first attempt at updating. I'll try to find the driver on the ST site. If I find it, where do I need to save it to? (Sorry not to be more computer savy.)

Larry - Looking at the batch file, it appears to only execute dfu-util-static.exe. Double-clicking that does nothing either.

Larry, I followed your instructions. (From the sourceforge website, I downloaded and unzipped dfu-util-0.9-win64.zip.) With all the files together in one folder as shown, I tried to run dfu-util.exe,

Hi Terry, a very basic question: Did you updated the firmware ever before? If not, probably you don't have the correct driver for the DFU mode, this is not the driver used to communicate with the PC

THis is what I did- Larry Get the tinySA_version_number.bin file from http://athome.kaashoek.com/tinySA/DFU/ and also download from there the files with names starting with DFU (so the latest is

Version is 1.3-111-gcb2fe54. The tinySA app works great, except for the upgrading function. After selecting the file, the app puts the tinySA into DFU mode automatically, but as you can see from the

Hugen manufactures the tinySA and he leveraged his experience and production capabilities with the nanoVNA to produce it.? I suspect he will do the same thing with any larger version of the tinySA.?

I believe the new tinySa that is being built in total secrecy will arrive very soon. I'm also looking forward to it and I already have the money set aside for this new device. Let's wait patiently.

Hey Terry, what FW version do you have loaded in the TinySA (menu=CONFIG/ VERSION)? And, when connecting to the TinySA app (before you try to update) does everything work Ok, you get a sweep and can

Same situation here with the eyes. Hoping for a 4.3 inch, with side buttons, similar to the NanoVNA-F (no flimsy Jog-wheel). Also, full featured Android software (connected via OTG USB-C cable) would

I use a NanoVNA-F, with side buttons, no Jog-Wheel. I hope the new not-so-TinySA 4.3 inch version (for my aging eyes, please), will use side buttons, like the the NanoVNA-F. Having an easily

I just tried both apps on my wife's laptop with the same failed results, so it must be the tinySA itself. Is there a way to reset it to factory settings? I saw something like that in the TinySA app,

I'm not sure I understand that, but I should mention that I see that when using the tinySA app, it /automatically /puts the device in DFU mode. That works. But as you can see, it appears to be unable

"Terry Perdue" <K8tp@...> wrote: The three cryptic choices are versions of NanoVNA firmware that were included in the original version of the program written for the NanoVNA. Ignore them.