|
Hello Vitaliy!
You need only?
TinySA-APP.exe and TinySA-APP.ini
Vladimir
|
On Sat, Mar 25, 2023 at 09:47 PM, <vitaliy_kh@...> wrote:
However using a control over Serial Link requires not only a Python script but
some additional SW components:
matplotlib
pillow
pyserial
Well, of course I don't have any of these extra components.
I have no idea where to get them.
Hello Vitaliy, You just have to type in the Windows Terminal: $ pip matplotlib $ pip pillow $ pip? pyserial I guess, that you have already installed python3. Rudi DL5FA
|
On Sat, Mar 25, 2023 at 09:47 PM, <vitaliy_kh@...> wrote:
However using a control over Serial Link requires not only a Python script but
some additional SW components:
matplotlib
pillow
pyserial
Well, of course I don't have any of these extra components.
I have no idea where to get them.
Hello Vitaliy, You just have to type in the Windows Terminal: $ pip install matplotlib $ pip install pillow $ pip install pyserial I guess, that you have already installed python3. Rudi DL5FA
|
Obviously, you have not paid attention to what is being discussed. You take part of a sentence and try to apply a response. READ, all the responses since the beginning of the question. All the help he has been given, and step by step guide lines given, has a response from him is he won't do anything on his computer in fear of screwing up his system, and still asking the same question. SO, read and use the full message, before you pick out a parcel part, and make a statement. Clyde KC7BJE?
On Sat, Mar 25, 2023, 1:42 PM Rudi < reuterr@...> wrote: On Sat, Mar 25, 2023 at 08:37 PM, Clyde Lambert wrote:
All your doing is crying about it and wasting everyone's time.
Hello Clyde,
You are in this group since about 2 years and 4 month.
I am in this group since about 2 years and 9 month.
The tinySA software was steadily improved by Erik in this time.
So, all the basics of a low cost Spectrum Analyser are covered after that time.
By the way Erik gives also a lot of support help in case of questions.
Now special wishes for software additions came up,
and Erik asked for help in this special case.
To shout "All your doing is crying about it and wasting everyone's time."
is very unfair in my opinion.
Rudi DL5FA
|
Hi Vitaliy,
At this point it might be best to follow the other instructions but I noticed something different in your setup compared to my use of the?DFU_LOAD_BIN.bat utility that would explain your error.
I found the hard part was to get the driver loaded in windows. I'm not sure you've got it loaded correctly, at least to use the?DFU_LOAD_BIN.bat file. Here's what mine looks like (nothing is under "Universal Serial Bus Controllers").?
I'm sorry but I can't recall exactly what I did to get the driver loaded. I installed the STM programmer software, somehow got the driver loaded, and then uninstalled the STM programmer software, leaving just this successfully working driver.
Once I got the driver loaded, the remaining steps were easy for me. From the F/W download page () I downloaded the firmware "bin" file, the bat file and the dfu-util-static.exe file. I ran these 2 commands:
mv .\tinySA4_v1.4-79-g0db995c.bin .\tinySA.bin .\DFU_LOAD_BIN.bat
I suspect it did not run for you because there's still something up with the driver.
Dave Have a look in the wiki: OK, looking more attentively into the above link I wound something ready to go for Windows and I am willing to try this one:  Again, there is no a single zipped file for download (usually it is one). I am sorry, I am not a SW person. I have a hard time to figure out what exactly I have to download and what is more important -? what executable to run?
--
Dave Koberstein keep in touch:
?
|
Ya it would have been great to follow any of the tutorials that just say to click on DFU in the config file.? I was a painless upgrade.
But if yours is like my unit, there is not DFU choice? in the config menu.
And Holding down the joy stick while turning on was not the simple answer.? IT may have turned DFU on but it was not seen in the ST32 app.
So at some point someone will figure out a easy upgrade for those of us who are not CMD literate.
I am a Ham Radio operator - not a computer? wize.
?Tried runningn the TinySA app..... but it did not detect my TinySA Ultra either.
|
The tinySA App should be able to detect the tinySA when in DFU mode Connect the tinySA, start tinySA app and click on the button with the two triangles A window should pop up and after "DFU Device" there should be a long string --
For more info on the tinySA go to https://tinysa.org/wiki/
|
On Sat, Mar 25, 2023 at 10:49 PM, ED Mellnik wrote:
Ya it would have been great to follow any of the tutorials that just say to click on DFU in the config file.? I was a painless upgrade.
But if yours is like my unit, there is not DFU choice? in the config menu.
And Holding down the joy stick while turning on was not the simple answer.? IT may have turned DFU on but it was not seen in the ST32 app.
So at some point someone will figure out a easy upgrade for those of us who are not CMD literate.
I am a Ham Radio operator - not a computer? wize.
?Tried runningn the TinySA app..... but it did not detect my TinySA Ultra either.
? ?Its been ages since my first tinySA installation and I didn't need to do anything extra after adding TinySA Ultra to the mix. I recently set up a new Windows 10 PC and documented the steps I used to establish connectivity with my tinySA Ultra. The attachment contains all the directories and latest firmware I used during my installation. 1. Extract the attached file to the C: drive.?? 2. After extraction, a top-level directory named TinySA Ultra with subdirectories named /DFU, TinySA-APP, and WIN10 Driver should have been created. 3. Connect the TinySA Ultra to a USB2.0 port on the PC (USB3.0 also works on my computer, but other users have reported connectivity issues). 4. Power on the TinySA Ultra and you should hear the Windows sound indicating a connection was detected.? A message should popup saying a new device was detected and Windows was installing a driver for it.? This message only appears the first time the tinySA Ultra is detected.? Wait until a message appears saying installation is complete. 5. Go to the?C:\TinySA Ultra\TinySA-App directory and run?tinySA-App.exe. 6.? Click on the drop down box with the "None" entry and select the COM port for the tinySA Ultra. The correct COM port is most likely the last entry in the drop down box. 7. After selecting the correct COM port, select the "Disconnect" button opposite the COM port drop down box and it should turn to "Connected".? To test connectivity, select the camera icon and a captured Image from the TinySA Ultra should appear in a separate window.? This confirms the serial port is working correctly. 8. Turn off the TinySA Ultra. 9. Load the DFU driver by going to?C:\TinySA Ultra\WIN10 Driver and right clicking on "STtube.inf" and selecting install. 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. 11. In TinySA-App click on the two up pointing arrows (^^). 12. A firmware update box should appear saying DFU Device opened and closed. 13. Select the upload firmware icon. When the file selector box appears, use it to select the DFU file at "C:\TinySA Ultra\DFU\tinySA4_v1.4-79-g0db995c.dfu".?? 14. After selecting the DFU file, updating to the selected version should begin. Wait for it to complete and select the "LEAVE DFU" button and the tinySA Ultra should reset and exit the DFU mode. This installation procedure worked for me. I hope this helps other users performing a first time Windows 10/11 installation.?? Herb
|
Hi
For what it is worth i also had issues using the ST32 programmer,
the solution for me in the end was to try it on a lap using the
same OS etc and it worked first time, i did not bother trying to
work out why my desk top could not see me device in DFU mode in
the end.
Regards
Mark
On 26/03/2023 08:38, hwalker wrote:
toggle quoted message
Show quoted text
On Sat, Mar 25, 2023 at 10:49 PM, ED Mellnik wrote:
Ya it would have been great to follow any of the
tutorials that just say to click on DFU in the config file.? I
was a painless upgrade.
But if yours is like my unit, there is not DFU choice? in the
config menu.
And Holding down the joy stick while turning on was not the
simple answer.? IT may have turned DFU on but it was not seen in
the ST32 app.
So at some point someone will figure out a easy upgrade for
those of us who are not CMD literate.
I am a Ham Radio operator - not a computer? wize.
?Tried runningn the TinySA app..... but it did not detect my
TinySA Ultra either.
? ?Its been ages since my first tinySA installation and I didn't
need to do anything extra after adding TinySA Ultra to the mix. I
recently set up a new Windows 10 PC and documented the steps I
used to establish connectivity with my tinySA Ultra. The
attachment contains all the directories and latest firmware I used
during my installation.
1. Extract the attached file to the C: drive.??
2. After extraction, a top-level directory named TinySA Ultra with
subdirectories named /DFU, TinySA-APP, and WIN10 Driver should
have been created.
3. Connect the TinySA Ultra to a USB2.0 port on the PC (USB3.0
also works on my computer, but other users have reported
connectivity issues).
4. Power on the TinySA Ultra and you should hear the Windows sound
indicating a connection was detected.? A message should popup
saying a new device was detected and Windows was installing a
driver for it.? This message only appears the first time the
tinySA Ultra is detected.? Wait until a message appears saying
installation is complete.
5. Go to the?C:\TinySA Ultra\TinySA-App directory and
run?tinySA-App.exe.
6.? Click on the drop down box with the "None" entry and select
the COM port for the tinySA Ultra. The correct COM port is most
likely the last entry in the drop down box.
7. After selecting the correct COM port, select the "Disconnect"
button opposite the COM port drop down box and it should turn to
"Connected".? To test connectivity, select the camera icon and a
captured Image from the TinySA Ultra should appear in a separate
window.? This confirms the serial port is working correctly.
8. Turn off the TinySA Ultra.
9. Load the DFU driver by going to?C:\TinySA Ultra\WIN10 Driver
and right clicking on "STtube.inf" and selecting install.
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.
11. In TinySA-App click on the two up pointing arrows (^^).
12. A firmware update box should appear saying DFU Device opened
and closed.
13. Select the upload firmware icon. When the file selector box
appears, use it to select the DFU file at "C:\TinySA
Ultra\DFU\tinySA4_v1.4-79-g0db995c.dfu".??
14. After selecting the DFU file, updating to the selected version
should begin. Wait for it to complete and select the "LEAVE DFU"
button and the tinySA Ultra should reset and exit the DFU mode.
This installation procedure worked for me. I hope this helps other
users performing a first time Windows 10/11 installation.??
Herb
|
I think I'm in a similar situation to OP. When I connect my TinySA Ultra in DFU mode to my Windows 10 x64 desktop, I see "STM32 BOOTLOADER" under "Other devices" in the device manager but there's no driver assigned. I downloaded STTub30.sys from but when I try to update the STM32 BOOTLOADER driver by pointing to my download folder, it isn't recognized. As a result, when I execute "dfu-util -a 0 -s 0x08000000:leave -D tinySA.bin" per the instructions at I get a string of errors reading "Invalid DFU suffix signature / Cannot open the device at 0483:df11 / No capable DFU device available".
I can certainly live with my TinySA Ultra as-is, but it would be nice if updating the firmware were more straight-forward (I've done so far more easily with my other devices, like my NanoVNA). Any pointers on what I'm missing are genuinely appreciated.
|
You can use the tool you used for the nanoVNA also for the tinySA --
For more info on the tinySA go to https://tinysa.org/wiki/
|
On Sat, Mar 25, 2023 at 04:42 PM, Rudi wrote:
All your doing is crying about it and wasting everyone's time.
Hello Group, No matter what I am/was trying to do is/was not working. As I mentioned, I installed the suggested Driver and the Device Manager can see tinySA?in the DFU mode. However?DFU_LOAD_BIN.bat still cannot see a device and of course, nothing was done. 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.) Now dear Clyde, tell me please whose time was washed out (6+ hours spent on restoring system)? Bottom line: The tinySA Ultra HW looks good specifically for the price/features options. However updating a firmware what must/should be just a mouse click in reality is a DISASTER. Many outdated and incompatible SW components not only doing their job but simply destroying otherwise stable Windows System. Things could be different for Linux OS (I don't have one around and?not planning to get one) but for Windows OS (10/11) the provides SW is nothing more than a giant creator of a problems.
|
On Sun, Mar 26, 2023 at 07:26 AM, allen KC2KLC wrote:
I think I'm in a similar situation to OP. When I connect my TinySA Ultra in DFU mode to my Windows 10 x64 desktop, I see "STM32 BOOTLOADER" under "Other devices" in the device manager but there's no driver assigned. I downloaded STTub30.sys from but when I try to update the STM32 BOOTLOADER driver by pointing to my download folder, it isn't recognized. As a result, when I execute "dfu-util -a 0 -s 0x08000000:leave -D tinySA.bin" per the instructions at I get a string of errors reading "Invalid DFU suffix signature / Cannot open the device at 0483:df11 / No capable DFU device available".
I can certainly live with my TinySA Ultra as-is, but it would be nice if updating the firmware were more straight-forward (I've done so far more easily with my other devices, like my NanoVNA). Any pointers on what I'm missing are genuinely appreciated.
? ?Did you see my earlier post at? /g/tinysa/message/10798? where I attached all the files and the procedure I used for installing TinySA-App and using it to update my TinySA Ultra to the latest firmware version on a Windows 10 PC.? I used the same procedure on a 2nd Windows 10 PC with the same successful results. ? Windows 10 automatically detected and installed the correct serial driver for the Ultra on both systems (I was connected to the Web so I'm not sure if found the driver locally or not).? I was able to run TinySA-App and use it to communicate with the TinySA Ultra after it was automatically detected by Windows 10. ? I was not able to update the TinySA Ultra firmware using TinySA-App until I installed the DFU driver manually as described in my post.? Both Windows 10 installations went smoothly, however they were clean installations where I hadn't tried any other methods of installing the serial and DFU drivers. Herb
|
Funny, I and many others have installed and use Windows and Macs without screwing up our computers. I even use my Android phone and or? Tablet to program not only program my TinySAs and NanoVNAs but also run Ham apps all without screwing up anything. At 79, next month, I still know how to follow "step by step" programs. Clyde KC7BJE?
On Sat, Mar 25, 2023 at 04:42 PM, Rudi wrote:
All your doing is crying about it and wasting everyone's time.
Hello Group,
No matter what I am/was trying to do is/was not working.
As I mentioned, I installed the suggested Driver and the Device Manager
can see tinySA?in the DFU mode.
However?DFU_LOAD_BIN.bat still cannot see a device and of course,
nothing was done.
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.)
Now dear Clyde, tell me please whose time was washed out (6+ hours
spent on restoring system)?
Bottom line:
The tinySA Ultra HW looks good specifically for the price/features options.
However updating a firmware what must/should be just a mouse click in
reality is a DISASTER. Many outdated and incompatible SW components
not only doing their job but simply destroying otherwise stable Windows
System. Things could be different for Linux OS (I don't have one around
and?not planning to get one) but for Windows OS (10/11) the provides SW
is nothing more than a giant creator of a problems.
|
It even works with my new Dell with Windows 11 and USB 3.01, only, ports.
No USB 2.0 adapters or special driver installation programs used either.
However, one does have to do an installation, precisely step by step, with no short cuts or missed steps. Clyde KC7BJE?
On Sun, Mar 26, 2023 at 07:26 AM, allen KC2KLC wrote:
I think I'm in a similar situation to OP. When I connect my TinySA Ultra in DFU mode to my Windows 10 x64 desktop, I see "STM32 BOOTLOADER" under "Other devices" in the device manager but there's no driver assigned. I downloaded STTub30.sys from but when I try to update the STM32 BOOTLOADER driver by pointing to my download folder, it isn't recognized. As a result, when I execute "dfu-util -a 0 -s 0x08000000:leave -D tinySA.bin" per the instructions at I get a string of errors reading "Invalid DFU suffix signature / Cannot open the device at 0483:df11 / No capable DFU device available".
I can certainly live with my TinySA Ultra as-is, but it would be nice if updating the firmware were more straight-forward (I've done so far more easily with my other devices, like my NanoVNA). Any pointers on what I'm missing are genuinely appreciated.
? ?Did you see my earlier post at? /g/tinysa/message/10798? where I attached all the files and the procedure I used for installing TinySA-App and using it to update my TinySA Ultra to the latest firmware version on a Windows 10 PC.? I used the same procedure on a 2nd Windows 10 PC with the same successful results.
? Windows 10 automatically detected and installed the correct serial driver for the Ultra on both systems (I was connected to the Web so I'm not sure if found the driver locally or not).? I was able to run TinySA-App and use it to communicate with the TinySA Ultra after it was automatically detected by Windows 10.
? I was not able to update the TinySA Ultra firmware using TinySA-App until I installed the DFU driver manually as described in my post.? Both Windows 10 installations went smoothly, however they were clean installations where I hadn't tried any other methods of installing the serial and DFU drivers.
Herb
|
On Sun, Mar 26, 2023 at 05:08 PM, Clyde Lambert wrote:
It even works with my new Dell with Windows 11 and USB 3.01, only, ports.
?
No USB 2.0 adapters or special driver installation programs used either.
?
However, one does have to do an installation, precisely step by step, with no short cuts or missed steps.
Clyde KC7BJE?
Clyde, did you have to turn off memory integrity on your Win 11 Dell? I haven’t yet updated my SA, but am following this thread with interest. My Dell Optiplex and Asus Vivobook both run Win 11 pro. Dave
|
On Sun, Mar 26, 2023 at 10:43 AM, G4AON wrote:
....did you have to turn off memory integrity on your Win 11 Dell? I haven’t yet updated my SA, but am following this thread with interest. My Dell Optiplex and Asus Vivobook both run Win 11 pro.
? On a new installation of Win 10/11 just follow the step-by-step instructions in?? /g/tinysa/message/10798?and you shouldn't have any problems. ? You'll have a working TinySA-App installation and additionally be able to update your firmware using either a .dfu or .bin file - without needing a separate program for the upgrade procedure.? During beta testing, I used TinySA-App to update my firmware extensively without a single failure. Herb
|
No I did not. I installed DfuSeDemo, STM32Cube and STM32ST-LINK utilities, TinySA-app and NanoVNA-app.exe on my Dell and started using each off and on, until I started using my Android phone to do all updates to? my Nanovna H, NanoVNA H4 and TinySA std. I use the STM32 ST-LINK mainly to program and FW updates, with my MINI-1300 VNA. Again I did not disable anything. Just load connect and run. 73's? Stay safe and healthy. Clyde KC7BJE?
On Sun, Mar 26, 2023 at 05:08 PM, Clyde Lambert wrote:
It even works with my new Dell with Windows 11 and USB 3.01, only, ports.
?
No USB 2.0 adapters or special driver installation programs used either.
?
However, one does have to do an installation, precisely step by step, with no short cuts or missed steps.
Clyde KC7BJE?
Clyde, did you have to turn off memory integrity on your Win 11 Dell? I haven’t yet updated my SA, but am following this thread with interest. My Dell Optiplex and Asus Vivobook both run Win 11 pro.
Dave
|
On Sun, Mar 26, 2023 at 02:18 PM, Clyde Lambert wrote:
No I did not. I installed DfuSeDemo, STM32Cube and STM32ST-LINK utilities, TinySA-app and NanoVNA-app.exe on my Dell and started using each off and on, until I started using my Android phone to do all updates to? my Nanovna H, NanoVNA H4 and TinySA std.
I use the STM32 ST-LINK mainly to program and FW updates, with my MINI-1300 VNA.
Again I did not disable anything. Just load connect and run.
Clyde could you check to see if Memory Integrity is On or Off on your machine.? Just enter "core isolation" in the Windows search box, select the answer and it will show you the status. Thanks - Roger
|
Hi,
Lots of trouble with your fragile Windows configuration. So use something else. A Raspberry Pi costs not very much. Too expensive. You can install your Windows on a USB stick or even on a second hard drive so as not use your finicky, delicate configuration. You can boot into any Linux OS the same way. Then you have an OS that will not use your present hard dive so it cannot wreck your work programs.
Instructions can be found all over the web.
73,
Bill ?KU8H Bark less - wag more
toggle quoted message
Show quoted text
On Mar 26, 2023, at 11:32 AM, vitaliy_kh via groups.io <vitaliy_kh@...> wrote:
?On Sat, Mar 25, 2023 at 04:42 PM, Rudi wrote:
All your doing is crying about it and wasting everyone's time.
Hello Group, No matter what I am/was trying to do is/was not working. As I mentioned, I installed the suggested Driver and the Device Manager can see tinySA?in the DFU mode. However?DFU_LOAD_BIN.bat still cannot see a device and of course, nothing was done. 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.) Now dear Clyde, tell me please whose time was washed out (6+ hours spent on restoring system)? Bottom line: The tinySA Ultra HW looks good specifically for the price/features options. However updating a firmware what must/should be just a mouse click in reality is a DISASTER. Many outdated and incompatible SW components not only doing their job but simply destroying otherwise stable Windows System. Things could be different for Linux OS (I don't have one around and?not planning to get one) but for Windows OS (10/11) the provides SW is nothing more than a giant creator of a problems.
|
Vladimir Lebedev
Clyde Lambert
G4AON
Roger Need