TinySA Ultra Firmware Update

[@TS-qd2uj]

Thank you very much for a clear cut, no bs explanation on navigating this firmware update on the Ultra. You have truly saved me a bunch of time.

[@TheSmokinApe]

Glad it was helpful TS, thanks for watching 👍

[@yornotelppa]

Thank you so much for all the work you do making these videos. I followed your instructions and updated the firmware on my TinySA Ultra without a single problem! 👍

[@TheSmokinApe]

Hey Roy, glad to hear it worked out for you 👍

[@acestudioscouk-Ace-G0ACE]

I'm really glad to have this video, I doubt I would update my unit without it. Thank-you, Ape. 😃👍

[@TheSmokinApe]

Thanks Ace, glad you liked it.

[@ThePrawlin]

Super useful and clearly explained. Just done my first ultra update. No problems. Perfect instructions thanks!

[@TheSmokinApe]

Hey TP, glad it worked out for you!

[@button-puncher]

Thanks! When I originally got mine, I wanted to update the FW. I read through the instructions and got spooked. I can't remember if they were worded oddly or what. I didn't want to brick my new toy.

[@TheSmokinApe]

Bricking is bad, this process is pretty straight forward though

[@karlbesser1696]

Good to know if you want to update the firmware. But what I would like more is a good manual that can be downloaded in PDF form and that explains all the possibilities of the T SA ultra in detail.

[@TheSmokinApe]

You and me both, a "how to" guide would be nice. Thanks for watching Karl

[@DonDegidio]

Hi Ape, Thanks for the video. Will be updating my TinySA Ultra firmware later. 73 WJ3U

[@TheSmokinApe]

Thanks Don, good luck with the update 👍

[@davidanddavidstrading]

waiting for mine to come in next week! thanks for this!

[@TheSmokinApe]

Awesome! Thanks for watching David!

[@DonzLockz]

TY Mr Ape, I get mine delivered next week. I will follow your stucktions.😅 Thnx buddy, super helpful.😊

[@TheSmokinApe]

Good luck with it 👍

[@survivalcomms]

Great instructions ! Thanks for sharing !

[@TheSmokinApe]

Thanks SC 👍

[@danielgrafflin9689]

I used the STM DfuSe_Demo V. 3.0.6. Once installed, I had to upgrade the drivers in Win device manager, but after that, hardly what you cal complicated. I did this for the Nano VNA H4 and that upgrade went flawless, and just did the upgrade for my Tiny SA ultra. Both in under an hour. So easy, it seemed scary. Your video is a very good guide, TNX

[@TheSmokinApe]

Hey Daniel, glad it worked out for you 👍

[@tmiller9099]

When you click erase, does it erase the curretly install Firmware? I notice a window that seemed to allow you to select things to erase but you went right to the file path for the newer version. I was curious if you had to remove the old version before adding the newer one. Thanks and nice video!!!

[@TheSmokinApe]

The instructions calls it erase but it really overwrites.

[@HamTechRadioScannerDrones]

Thanks is there a change log ?

[@TheSmokinApe]

athome.kaashoek.com/tinySA4/DFU/changelog.txt

[@n1kkri]

have you done a video comparing the different mfg of the tinySA telling us what we need to know about the differences as well as what firmware would be used. Same goes for the nanoVNA. Thinking about buying one of them but would hate to buy something that might be buggy or not compatible with certain firmware. thanks

[@TheSmokinApe]

I have not

[@HOAHamRadio]

I didn't see the "SEND IT TO TheSmokinApe FOR UPDATE" options in any drop down menus; did I miss it?

[@TheSmokinApe]

That's in the next release!

[@HOAHamRadio]

@@TheSmokinApe Perfect. Sign me up!

[@TheSmokinApe]

lol

[@ornithopterindia]

👍Thank you for the video.

[@TheSmokinApe]

Thanks for watching 👍

[@tateantrim2203]

I followed the instructions to update my Tiny Ultra to the latest but it was unsuccessful. I noticed in the log that while programming it said "Sector 0000 does not exist" and this went all the way through to sector 0088 does not exist. I've tried reflashing, it but same results...of course it won't turn on now. Any ideas?

[@TheSmokinApe]

What app are you using and what version of windows?

[@tateantrim2203]

@@TheSmokinApe Windows 11/64 and the STM application. It seems to work and doesn't give me any errors except that the log has these weird entries. The end result is a pure black screen and it was working fine prior to the firware upgrade. I have the TinySA Ultra (I got it from R and L Electronics and figured it would be legit) and downloaded the latest firmware from the authorized site.

[@TheSmokinApe]

The RnL ones are legit. There is aTinySA groups.io and many folks have been reporting this issue over there, I believe it to be a driver issue. You should check it out 👍

[@tateantrim2203]

@@TheSmokinApe Turns out version 2.16 of the STM32 programmer has a bug in it. I dropped down to version 2.15 and it loaded the new firmware without issue (there was an entry in the NanoVNA forum about it). Took all of about 10 seconds to do. I even did the VDD -> BOOT short and that did nothing. So anyone having issues with their TinySA Ultra and version 2.16 of the programmer, just download version 2.15, install it and follow the video here to update the firmware to the latest.

[@TheSmokinApe]

Glad to hear you are back in business!

[@Ezzell_]

Have you noticed any improvements or new features with the new FW?

[@TheSmokinApe]

Here is the change log: athome.kaashoek.com/tinySA4/DFU/changelog.txt

[@danielfafik7661]

Thanks a lot for useful video. I can conform because I did it!:) WARNING: "STM32CubeProgrammer version 2.16 has a bug and is NOT able to update the tinySA. Use version 2.15!!" . Of course who reading instructions.... TinyAS after update with STMv2.16 looks like bricked but older version 2.15 fixing it.

[@TheSmokinApe]

Yeah, this is a good point 👍

[@JosephofWalton]

I wish I would have seen this earlier. I have been trying to find data as to why my TinySA ultra went to black screen after update. I am up and running now.

[@robertmeyer4744]

great info. can be important to update firmware on devices like that. I have the nano VNA-H4 . I have the Icom IC 7300 and there is a new firmware update for that on Icom website. hard read mostly in Japanize . the new feature is TX lockout. and some rig control for a Icom amp. and a hard reset but pushing buttons if screen lock up . I downloaded the file but waiting to see some video's on the new firmware for the 7300. mine working great. 73's

[@TheSmokinApe]

Hey Rob, it seems like we are always updating firmware these days.

[@robertmeyer4744]

@@TheSmokinApe even the Talk pod has a update . I just ordered one for my self. if dirty I send it back . amazon .

[@TheSmokinApe]

@@robertmeyer4744 lol, good luck with it 👍

[@nighthawkflyer]

I updatet the Firmware of a tiny sa ultra. The first flashing was succesful with no errors. But after switch off and on the Tiny SA ultra the screen stayed black. The STM32 programmer is able to connect the tiny. But now no Data ist displayed after connect to the tiny ultra. The programmer shows all sectors not exists during the flash process. It seems the device is brigged. Any idea how to fix this problem ? OK, my fault. With the 2.15 version of the programming software it was no problem.

[@TheSmokinApe]

Hey NHF, apparently the 2.16 version of the software has a bug 🪳

[@chriscutting5773]

great vid but a word of warning use stm32cube 2015 as there seems to be a problem with the 2016 version you end up with a blank screen and the tinysa won't reboot just reflash with 2015 version then it reboots with no problem just thought i'd let you know for those that don't know 😊😊😊

[@TheSmokinApe]

This is good advise, a number of people have reported this issue 👍

[@ronaldraymond7037]

I did the update and something went wrong, it wouldn’t startup again so I started to play with my new paperweight after a while I checked the box erase the chip and got lucky it worked. After I restarted and sent the bin file. I think with the hassle of getting the software and bin file I had duplicate files that had number differences I fixed that by naming it what it should be then got lucky

[@TheSmokinApe]

Glad you got it sorted out 👍

[@zandanshah]

STMicroelectronics S/W Application LHS button is called "“Erasing & Programming” icon one icon does two things.

[@TheSmokinApe]

Thanks for the info 👍

[@ThatLoudF-150]

You might have mentioned it and I didn't catch it, but you also have to re unlock ultra mode after updating. Sad to say it took me a few minutes to figure out why I couldn't display above 800MHz 😂.

[@TheSmokinApe]

You do and thanks for catching that 👍

[@KO4VNX]

You, good Sir, are a smart bastard!

[@TheSmokinApe]

lol, thanks DeWayne 🍻

[@juhaszpeter4796]

I also tried to update my TinySA ultra based on the videos for the first time with the STM32 program. In the end, this indicated that it was successful. There is an error report in the log. 88 memory addresses could not be deleted because they do not exist or something similar. After the update everything went black. The TinySa app has not seen the device. The STM32 saw it, connected, at the end it said that the update was successful, but it still remained black. After half a day of struggle, I gave up and tried the "Full chip earse" option. I updated it again. When the update failed it was done in less than 2 seconds. Now at the last one, when everything was fine with the update, it took more than 5 seconds. I don't know why it didn't work the first time and I had to suffer with it.

[@TheSmokinApe]

No idea either but I’m glad you got it worked out 👍

[@kinglouis6974]

Hey !!!! I’m 44 and I’m buying my first laptop top this week Because I need firmware Updates ! And I’m a complete novice

[@TheSmokinApe]

Good luck with it KL 👍

[@D4vesgrill]

Everything seemed to work perfectly until I tried rebooting my tinySA. Just a black screen. Nothing. Any ideas. Using a Mac, but still everything looked like it worked exactly as in your video.

[@TheSmokinApe]

That doesn't sounds good, I would try to apply an older firmware and see if the process works?

[@D4vesgrill]

@@TheSmokinApe Good news is the seller via Amazon agreed to do a one for one swap for a new one. I read a lot of weird info that the update is not for the ultra. I could try again on a Windows laptop, but I might just enjoy it awhile as is before I try again. But yes, that attempt hard broke it.

[@TheSmokinApe]

@@D4vesgrill glad to hear they will swap it out 👍

[@atsmadane2575]

Can the device pick up the frequency of 5 kHz? Thank you, dear sir

[@TheSmokinApe]

No, it goes down to 100kHz

[@atsmadane2575]

@@TheSmokinApe Is there a device to detect the VLF spectrum?? Greetings sir

[@TheSmokinApe]

I am sure but I don't know which

[@atsmadane2575]

@@TheSmokinApe Good day

[@LeeMcc_KI5YPR]

So far no need for tinySA but maybe one day.

[@TheSmokinApe]

I’ll be waiting by the phone ☎️

[@tomstrum6259]

Holly crap.....Gotta be joking.....Absolutely No way I could get 1/10th the Complexity of all this Incomprehensible million Click confusion....Thx anyways....

[@TheSmokinApe]

I have faith I you Tom 👍

[@Thump2030]

lol if it ain't broke don't flash it.... well in most cases. 😀

[@TheSmokinApe]

lol, they have been releasing an ton of updates for this thing

[@temporarilyoffline]

Easy as

[@TheSmokinApe]

Right, I fell like I am always updating firmware these days.

[@WR3ND]

You'd be amazed at how problematic software can be at installing itself sometimes... 😏

[@WR3ND]

...but yes, it did go smoothly for me in this case. Though for now, I have not elected to have the firmware updater (Programmer) have network access to check for updates to itself. Cheers.

[@TheSmokinApe]

Nah man, I get it as I’ve been in IT for almost 30 years. This software was a pretty straight forward install. Thanks for checking out the video 👍

[@shuntera]

I detest this kind of software. I just got my TinySA Ultra and want to upgrade the firmware. You have to register to download the software but then you don't get an email so you can't download it. Ughhhh, so ridiculous.

[@TheSmokinApe]

The horror…

[@tomstrum6259]

I hear ya but I Never attempt updates or flash Anything like these NanoVNA or TinySA units that Are functioning Perfectly.....My luck,....It will Immediately Die a weird Non-recovery Useless death 'cause digitals & computerized stuff doesn't like me....Would rather just buy a new Latest version if needed

[@TheSmokinApe]

Once you get used to updating firmware, you get used to it 👍

[@pege63]

After firmware update version tinySA4_v1.4-171-g393022c.bin with the STMCube programmer the screen stays black on my TinyDA Ultra. I did exactly what you did in the video 17:25:09 : STM32CubeProgrammer API v2.16.0 | Windows-64Bits 17:34:48 : UR connection mode is defined with the HWrst reset mode 17:34:49 : USB speed : Full Speed (12MBit/s) 17:34:49 : Manuf. ID : STMicroelectronics 17:34:49 : Product ID : STM32 BOOTLOADER 17:34:49 : SN : 2060326Axxxx 17:34:49 : DFU protocol: 1.1 17:34:49 : Board : -- 17:34:49 : Device ID : 0x0422 17:34:52 : UPLOADING OPTION BYTES DATA ... 17:34:52 : Bank : 0x00 17:34:52 : Address : 0x1ffff800 17:34:52 : Size : 16 Bytes 17:34:53 : UPLOADING ... 17:34:53 : Size : 1024 Bytes 17:34:53 : Address : 0x8000000 17:34:53 : Read progress: 17:34:53 : Data read successfully 17:34:53 : Time elapsed during the read operation is: 00:00:00.242 17:37:32 : Read File: C:\Temp\TinySA Ultra\tinySA4_v1.4-171-g393022c.bin 17:37:32 : Number of segments: 1 17:37:32 : segment[0]: address= 0x0, size= 0x2C4D8 17:37:51 : Memory Programming ... 17:37:51 : Opening and parsing file: tinySA4_v1.4-171-g393022c.bin 17:37:51 : File : tinySA4_v1.4-171-g393022c.bin 17:37:51 : Size : 177.21 KB 17:37:51 : Address : 0x08000000 17:37:51 : Erasing memory corresponding to segment 0: 17:37:51 : Erasing internal memory sectors [0 88] 17:37:51 : sector 0000 does not exist 17:37:51 : sector 0001 does not exist 17:37:51 : sector 0002 does not exist 17:37:51 : sector 0003 does not exist 17:37:51 : sector 0004 does not exist 17:37:51 : sector 0005 does not exist 17:37:51 : sector 0006 does not exist 17:37:51 : sector 0007 does not exist 17:37:51 : sector 0008 does not exist 17:37:51 : sector 0009 does not exist 17:37:51 : sector 0010 does not exist 17:37:51 : sector 0011 does not exist 17:37:51 : sector 0012 does not exist 17:37:51 : sector 0013 does not exist 17:37:51 : sector 0014 does not exist 17:37:51 : sector 0015 does not exist 17:37:51 : sector 0016 does not exist 17:37:51 : sector 0017 does not exist 17:37:51 : sector 0018 does not exist 17:37:51 : sector 0019 does not exist 17:37:51 : sector 0020 does not exist 17:37:51 : sector 0021 does not exist 17:37:51 : sector 0022 does not exist 17:37:51 : sector 0023 does not exist 17:37:51 : sector 0024 does not exist 17:37:51 : sector 0025 does not exist 17:37:51 : sector 0026 does not exist 17:37:51 : sector 0027 does not exist 17:37:51 : sector 0028 does not exist 17:37:51 : sector 0029 does not exist 17:37:51 : sector 0030 does not exist 17:37:51 : sector 0031 does not exist 17:37:51 : sector 0032 does not exist 17:37:51 : sector 0033 does not exist 17:37:51 : sector 0034 does not exist 17:37:51 : sector 0035 does not exist 17:37:51 : sector 0036 does not exist 17:37:51 : sector 0037 does not exist 17:37:51 : sector 0038 does not exist 17:37:51 : sector 0039 does not exist 17:37:51 : sector 0040 does not exist 17:37:51 : sector 0041 does not exist 17:37:51 : sector 0042 does not exist 17:37:51 : sector 0043 does not exist 17:37:51 : sector 0044 does not exist 17:37:51 : sector 0045 does not exist 17:37:51 : sector 0046 does not exist 17:37:51 : sector 0047 does not exist 17:37:51 : sector 0048 does not exist 17:37:51 : sector 0049 does not exist 17:37:51 : sector 0050 does not exist 17:37:51 : sector 0051 does not exist 17:37:51 : sector 0052 does not exist 17:37:51 : sector 0053 does not exist 17:37:51 : sector 0054 does not exist 17:37:51 : sector 0055 does not exist 17:37:51 : sector 0056 does not exist 17:37:51 : sector 0057 does not exist 17:37:51 : sector 0058 does not exist 17:37:51 : sector 0059 does not exist 17:37:51 : sector 0060 does not exist 17:37:51 : sector 0061 does not exist 17:37:51 : sector 0062 does not exist 17:37:51 : sector 0063 does not exist 17:37:51 : sector 0064 does not exist 17:37:51 : sector 0065 does not exist 17:37:51 : sector 0066 does not exist 17:37:51 : sector 0067 does not exist 17:37:51 : sector 0068 does not exist 17:37:51 : sector 0069 does not exist 17:37:51 : sector 0070 does not exist 17:37:51 : sector 0071 does not exist 17:37:51 : sector 0072 does not exist 17:37:51 : sector 0073 does not exist 17:37:51 : sector 0074 does not exist 17:37:51 : sector 0075 does not exist 17:37:51 : sector 0076 does not exist 17:37:51 : sector 0077 does not exist 17:37:52 : sector 0078 does not exist 17:37:52 : sector 0079 does not exist 17:37:52 : sector 0080 does not exist 17:37:52 : sector 0081 does not exist 17:37:52 : sector 0082 does not exist 17:37:52 : sector 0083 does not exist 17:37:52 : sector 0084 does not exist 17:37:52 : sector 0085 does not exist 17:37:52 : sector 0086 does not exist 17:37:52 : sector 0087 does not exist 17:37:52 : sector 0088 does not exist 17:37:52 : Download in Progress: 17:37:56 : File download complete 17:37:56 : Time elapsed during download operation: 00:00:05.089

[@TheSmokinApe]

STM32CubeProgrammer version 2.16 has a bug and is NOT able to update the tinySA. Use version 2.15

[@pege63]

@@TheSmokinApe I have TinySA Ultra i saw there where a new version 2.17 now, do that one work on TinySA Ultra?

[@TheSmokinApe]

@@pege63 I’m not sure, haven’t tried

[@pege63]

@@TheSmokinApe Thanks m8, it worked am good to go now!

[@TheSmokinApe]

Apparently the 2.17 will work