|
New FW release Version V1.4137 Ultra Only Changes: - Correct the version number inconsistency - Small change to calibration routine. - Small extension of selftest. --
For more info on the tinySA go to https://tinysa.org/wiki/
|
Erik,
The changelog file on the site for SA4 needs to be updated.
Also, can you list change numbers according to firmware filenames, like "v1.4-137", instead of "V1.4049"
The firmware # itself is in the format "tinySA4_v1.X-XXX-[hash]" when getting version from CONFIG --> VERSION on device.
For we end users, its better to keep things consitent and easy to follow.
btw, took me just 3min to update firmware using dfu bat file.
For readers here, open the BAT and look at the commands, notice the defaults, uses filename "tinySA.bin". If your new firmware files does not match then the dfu util will say it cannot open device, in this case the device is the new firmware file, etc.
|
I always rely on the displayed build date as the final answer. It's not likely that the computer will typo that. :D My update was less than thirty seconds using TinySA-app. 73 -Jim NU0C On Wed, 20 Dec 2023 10:37:57 -0800 "Akai Moto via groups.io" <akai.moto@...> wrote: Erik,
The changelog file on the site for SA4 needs to be updated.
Also, can you list change numbers according to firmware filenames, like "v1.4-137", instead of "V1.4049"
The firmware # itself is in the format "tinySA4_v1.X-XXX-[hash]" when getting version from CONFIG --> VERSION on device.
For we end users, its better to keep things consitent and easy to follow.
btw, took me just 3min to update firmware using dfu bat file.
For readers here, open the BAT and look at the commands, notice the defaults, uses filename "tinySA.bin". If your new firmware files does not match then the dfu util will say it cannot open device, in this case the device is the new firmware file, etc.
-- 73 -Jim NU0C
|
Jim,
You mean you had everything connected and app already running, with bin ready to go? lol
My less than 3min was getting SA4 out of the box, attaching USB cable, power up to dfu mode, downloading that latest bin & renaming it, running dfu command line (bat), watching the firmware upload.
That time does not include doing another calibration. You re-did cal, yes?
But yes, my point was/is, super easy and fast to update these devices.
|
Akai, Feel free to collect all my release posts and create an updated change log file so I can use it The version number mentioned in the post is in the format used in the status panel due to width limitations. Relevant digits are the same as in the file name or the long version id --
For more info on the tinySA go to https://tinysa.org/wiki/
|
Here is Your release posts...
Istvan
|
Let's see... Go to bookmark of Erik's download site Right-click DFU file and save as... Grab SA and plug it in Turn on in DFU mode Fire up NanoVNA-app Click, click, navigate to SA4 folder (if necessary), double-click Done. That's about right.... Maybe 45 seconds if I haven't had my coffee yet. :D I didn't see any red calibration flags but I ran the self-test and re-calibrated anyway because I had planned doing some NanoVNA-related measurements with it later. Normally I don't re-cal if nothing in red pops up. I normally don't count it in upgrade time anyway because I consider it something that could be done for whatever reason in the normal course of any day. 73 -Jim NU0C On Wed, 20 Dec 2023 12:58:06 -0800 "Akai Moto via groups.io" <akai.moto@...> wrote: Jim,
You mean you had everything connected and app already running, with bin ready to go? lol
My less than 3min was getting SA4 out of the box, attaching USB cable, power up to dfu mode, downloading that latest bin & renaming it, running dfu command line (bat), watching the firmware upload.
That time does not include doing another calibration. You re-did cal, yes?
But yes, my point was/is, super easy and fast to update these devices.
-- 73 -Jim NU0C
|
Thanks Istvan for the SA4 changelog file.
Attached here is the modified file (my edits for just version syntax). They now match the filenames.
It's just me from being in world of code versions, I don't like use of mixed chars, like the dot and the dash "v1.4-137", etc. Just use dots "v1.4.137", no need to use the dash.
[MAJOR] dot [minor] dot [updates/fixes]
Cheers.
|
(since topic is about updates)
I would like to ask if it is possible to make an general name f.e. latest.bin latest.dfu etc in the server.
This would be very easy to get update scripted on client side.
p.s. Thank you for the great tool!
|
On Thu, Dec 21, 2023 at 11:20 PM, Akai Moto wrote:
Just use dots "v1.4.137", no need to use the dash.
This mixed format comes directly from the git --describe command, which is the most correct versioning b/c it increments the part after the dash with every commit, no need to do it manually (with the danger of forgetting etc.) in an extra edit.
|
On 22/12/2023 05:10, Zilvinas, LY2SS wrote: (since topic is about updates)
I would like to ask if it is possible to make an general name f.e. latest.bin
latest.dfu etc in the server.
This would be very easy to get update scripted on client side.
p.s. Thank you for the great tool! I see no need for that. The TinySA app accepts the full file name as downloaded. I always use the .bin. David -- SatSignal Software - Quality software for you Web: Email: davidtaylor@... Twitter: @gm8arv
|
Dear David,
How to automatically (bash/wget) fetch file from the server when it's name changes with every release then?
|
On 22/12/2023 08:56, Zilvinas, LY2SS wrote: Dear David,
How to automatically (bash/wget) fetch file from the server when it's name
changes with every release then? Good point I always do manual updates. There's (usually) just one copy of the files at that URL, so download all the files (or just the .bin or whatever) into a local archive directory, check if you now have either a more recent one or one with a higher version number (sort by name?), and use that? tinySA4_v1.4-126-gad1d783.bin tinySA4_v1.4-128-ge95e79c.bin tinySA4_v1.4-129-g95d48eb.bin tinySA4_v1.4-134-g3c20a9c.bin tinySA4_v1.4-137-g1806825.bin Keeping a few archive versions allows you to go back if needed. Cheers, David -- SatSignal Software - Quality software for you Web: Email: davidtaylor@... Twitter: @gm8arv
|
Maybe it would be enough to make a soft link on the server to the actual files.
|
bash script to retrive whatever bin is there in DFU folder.
This for SA4 only, but you can mod it to get from the SA folder too by taking out the "4"
This assumes the DFU folder holds whatever the latest bin is. If you want dfu and hex files too, then just make a loop for bin dfu hex, etc.
#!/bin/bash
RESULT="`wget -qO- -e robots=off http://athome.kaashoek.com/tinySA4/DFU/ | sed -e 's/<[^>]*>//g' | grep bin | awk -F '\\.bin' '{print $1".bin"}'`"
Link="http://athome.kaashoek.com/tinySA4/DFU/"$RESULT
wget -e robots=off $Link
|
Quick note about filenames and update utilities.
The app does not care about filename, because you have to select it, so that's the file it pushes in.
dfu util however uses filename as arg, so it needs to match the actual filename you wish to push (dfu util has to "find" the file, etc). In the dfu bat file it uses default name of "tinySA.bin"
I have several tiny devices, and the app didn't work on all of them, but dfu util does, so I stick with dfu util.
|
I like this. Makes me want to do my next upgrade in Linux. :) Thank you. NB The reason I don't use Linux for upgrades now is simply a convenience of laziness. Most of my toys are in the same room as the Windoze box where I do most of my web surfing. They only walk to the shack/lab when I need them there for a task. 73 -Jim NU0C On Fri, 22 Dec 2023 12:10:06 -0800 "Akai Moto via groups.io" <akai.moto@...> wrote: bash script to retrive whatever bin is there in DFU folder.
This for SA4 only, but you can mod it to get from the SA folder too by taking out the "4"
This assumes the DFU folder holds whatever the latest bin is. If you want dfu and hex files too, then just make a loop for bin dfu hex, etc.
#!/bin/bash
RESULT="`wget -qO- -e robots=off | sed -e 's/<[^>]*>//g' | grep bin | awk -F '\\.bin' '{print $1".bin"}'`"
Link="
wget -e robots=off $Link
-- 73 -Jim NU0C
|
Hello Erik,
Is it necessary to do a Clear All when doing a Calibration on the
Ultra?
Regards...Bob VK2ZRE
On 21/12/2023 3:10 am, Erik Kaashoek
wrote:
toggle quoted message
Show quoted text
New FW release
Version V1.4137
Ultra Only
Changes:
- Correct the version number inconsistency
- Small change to calibration routine.
- Small extension of selftest.
--
For more info on the tinySA go to
|
No Only when you have loaded new firmware it is best to do a clear config --
For more info on the tinySA go to https://tinysa.org/wiki/
|
Jim Shorney
Ho-Ro
David J Taylor