Keyboard Shortcuts
Likes
- Tinysa
- Messages
Search
Re: tinySA Ultra firmware upgrade
#ultra
On Sun, Mar 26, 2023 at 05:08 PM, Clyde Lambert wrote:
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
|
Re: tinySA Ultra firmware upgrade
#ultra
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, 8:35 AM hwalker <herbwalker2476@...> wrote: On Sun, Mar 26, 2023 at 07:26 AM, allen KC2KLC wrote: |
Re: New FW release: Added option for fixed 10 gridlines
On Sun, Mar 26, 2023 at 08:00 AM, Brian Donaldson wrote:
Hi Erik, do you have a link to the release notes for previous versions? I can't seem to find them if they are available,See message? /g/tinysa/message/10590? Herb |
Re: tinySA Ultra firmware upgrade
#ultra
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 Sun, Mar 26, 2023, 8:32 AM vitaliy_kh via <vitaliy_kh=[email protected]> wrote: On Sat, Mar 25, 2023 at 04:42 PM, Rudi wrote: |
Re: tinySA Ultra firmware upgrade
#ultra
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".? ?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 |
Re: tinySA Ultra firmware upgrade
#ultra
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. |
Re: tinySA Ultra firmware upgrade
#ultra
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/ |
Re: tinySA Ultra firmware upgrade
#ultra
allen KC2KLC
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. |
Re: TinySA Ultra Frozen Screen, Unresponsive
Since it was running for some time could it have heated up resulting in an intermittent connection?
Does the display have a connector? If so can you reseat the connector?
Mike N2MS
|
Re: TinySA Ultra Frozen Screen, Unresponsive
This is all very weird. I have never seen this before.
Just to be sure, you did disconnect? the battery with the device not connected to USB and totally powered off? You could try to load an older FW that does not save settings so is less likely to get into a corrupt state. See:? Maybe go back in steps of a month till you get something that at least sweeps -- For more info on the tinySA go to https://tinysa.org/wiki/ |
Re: tinySA Ultra firmware upgrade
#ultra
开云体育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:
On Sat, Mar 25, 2023 at 10:49 PM, ED Mellnik wrote: |
Re: New FW release: Added option for fixed 10 gridlines
Hi Eric,
Tried today to update my Ultra but i get the black screen.? The connection and USB cables are checked and ok. I installed my backup i made before and the Ultra started again. This the current version of the firmware : tinySA ULTRA
2019-2022 Copyright @Erik Kaashoek
2016-2020 Copyright @edy555
SW licensed under GPL. See: https://github.com/erikkaashoek/tinySA
Version: tinySA4_v1.4-40-g2f63e1c
Build Time: Jan 13 2023 - 17:56:59
Kernel: 4.0.0
Compiler: GCC 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
Architecture: ARMv7E-M Core Variant: Cortex-M4F
Port Info: Advanced kernel mode
Platform: STM32F303xC Analog & DSP
?
Any idea why the update fails?Regards. André PD2AM |
Re: TinySA Ultra Frozen Screen, Unresponsive
I sent over the "scanraw 10M 20M" command, but I didn't get anything out on the terminal emulator. I also wasn't able to get the TinySA Ultra into generator mode. After trying to set the mode through the serial terminal, the TinySA ultra seems to freeze, i need to power cycle to get the serial monitor going again. I also tried getting the battery voltage, but no response from the TinySA
No Response after "scanraw 10M 20M" command |
Re: How to download captured display images
开云体育Hi Paul There is a much simpler way to get screen images saved on the PC Use the TinySA-App from and copy the TinySA-App.exe and TinySA-App.ini to a folder e.g- C://TinySA-App and create a shortcut for the TinySA-App.exe to the Desktop. When started connect to the TinySA (ultra) com port and click on the little Camera Icon and you have a nice image of the screen to save or directly copy to the clipboard. Just click on update for a new image Very handy application also for many other usages ? Kind regards Kurt Fra: [email protected] <[email protected]> P? vegne af psehorne ? Now, why didn't I think of that?? ... No, don't answer that. Thank you. ? ? ? Paul ? ? ? -------- Original message --------
From: hwalker <herbwalker2476@...> Date: 3/25/23 11:16 PM (GMT-06:00) Subject: Re: [tinysa] How to download captured display images ? On Sat, Mar 25, 2023 at 06:08 PM, psehorne wrote:
1. Power off the tinySA Ultra and remove the SanDisk card. |
Re: tinySA Ultra firmware upgrade
#ultra
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.? ?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 |
Re: tinySA Ultra firmware upgrade
#ultra
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/ |
Re: TinySA Ultra Frozen Screen, Unresponsive
First try to see if the generator mode work
Put in generator mode and see if you can get any output. If that works the? chips are OK but there may be something wrong with the scanning setup Or you can send over USB the command scanraw 10M 20M this should start outputting weird characters that even may mess up you terminal emulator but at least proves scanning works to some extend If you can observe power at frequencies around 1GHz you can try generator mode and try 1GHz output to test if one chip works and 1.3GHz in square wave output mode to test the other chip. -- For more info on the tinySA go to https://tinysa.org/wiki/ |