tinysa@groups.io | Messages

Firmware update #tinysa

None of the instructions for firmware updating are either understandable or workable.

The first approach was to use the instructions for?Updating the firmware using a bin file and STM32CubeProgrammer(Windows) unfortunately the link is dead.

Next:?Updating the firmware using a bin file and dfu-util(Windows, Linux and Mac) I downloaded the bin file and renamed it to tinyAS.bin. However the step "Download dfu-util from http://dfu-util.sourceforge.net/releases/ and check you can execute it" is meaningless.? I downloded dfu-util-0.11.tar.gz?but none of the files contained in it are executable. Likewise?DFU_LOAD_BIN.bat cannot be run on Windows 11 due to security issues.

The step "The tinySA should now be updating with the tinySA.bin file using dfu-util-static.exe" does not work because dfu-util-static.exe does not execute.

I then copied the first command from the bat file and ran it in a Windows command window:

C:\Users\User\Downloads>.\dfu-util-static.exe? -a 0 -s 0x08000000:leave -D .\tinySA.bin

dfu-util 0.9

?

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

?

Invalid DFU suffix signature

A valid DFU suffix will be required in a future dfu-util release!!!

Cannot open DFU device 0483:df11

No DFU capable USB device available?

I then Googled tinysa firmware update and found the YouTube by Lockdown Electronics. This looked promising until discovering that dfuse demo is no longer available. All links go to STM32CubeProgrammer and the instructions are no longer valid.

I tried a few more YouTube video and gave up after about three hours of useless effort.

Are there any instructions for firmware updating that are relevant and understandable for Windows 11 in March 2022?

?

Re: Ability to save High and Low output mode configuration and automatically recall it on power up #feature_request

#6822

On Fri, Mar 25, 2022 at 04:52 PM, Erik Kaashoek wrote:

If I do not forget I may add this whenever I do a next release

Hi Erik,

That would be great if it is possible.

I hope your memory remains good :-)

Thanks,

Martin

Re: Is there peak hold option in SW

#6821

Thank you. I also realized, that my NanoVna should be able to do this with attenuators.

Re: Ability to save High and Low output mode configuration and automatically recall it on power up #feature_request

#6820

It is just an omission from my side that I forgot to add the preset load/store part in the output modes. If I do not forget I may add this whenever I do a next release as all the functionality exists
--

For more info on the tinySA go to https://tinysa.org/wiki/

Re: Ability to save High and Low output mode configuration and automatically recall it on power up #feature_request

#6819

<Toni Ciscar

But I'm referring to OUTPUT LOW/HIGH function.

Re: #bug_report #bug_report

#6818

I'm happy with the bug report as this revealed a bug in all fractional input that could have caused weird things.
If you calculate a frequency in MHz you often get more digits then needed and it's simpler to enter all instead of counting if you reached the tinySA resolution.

--

For more info on the tinySA go to https://tinysa.org/wiki/

Re: #bug_report #bug_report

#6817

On Fri, Mar 25, 2022 at 12:15 AM, @SleepingCat wrote:

There is indeed no practical use (at least for me) of entering a hundredth of a Hz. ;)

“It is the mark of an instructed mind to rest satisfied with that degree of precision which the nature of the subject admits, and not to seek exactness where only an approximation of the truth is possible.” - Aristotle

That said, I always feel that errors that occur in one place where they are not a problem can be potentially serious in another place.

I'm with SleepingCat.? Had I come across that bug/quirk, my mind would immediately jump to: "Hmm,? what else does that affect?"

Re: #bug_report #bug_report

#6816

I feel with both John and @SleepingCat.

John is right, especially when it concerns measurements.
People can be so seemingly pretentious, although in most cases it's ignorance I'm afraid.

But I think @SleepingCat has also a point, another point.
If something goes wrong in an otherwise useless case (but you don't know why), what else can happen?

It becomes almost philosophical.
Are you from the school "If it ain't broke, don't fix it" OR from "If it ain't broke, you're not trying"? ? ;)?

Just my 2±1 cents,
BenS

Re: #bug_report #bug_report

#6815

That is so common....
"More decimals = More accurate"
In my last job, people were entering GPS locations of field based equupment to ridiculous lengths. I challenged them, pointing out that their coordinates defined locations to the thickness of the paint coating , whilst their GPS equipment was only accurate to 3m. But it happens.
Just my 2.000000 cents worth..
John

Re: #bug_report #bug_report

#6814

Your question is absolutely justified. There is indeed no practical use (at least for me) of entering a hundredth of a Hz. ;)

That said, I always feel that errors that occur in one place where they are not a problem can be potentially serious in another place.

That's the reason I post things like this, even if they don't affect me at all. Please let me know if sharing the serious things is enough...

Re: Is there peak hold option in SW

#6813

TRACE/CALC/MAX HOLD
--

For more info on the tinySA go to https://tinysa.org/wiki/

Is there peak hold option in SW

#6812

I want test the bandwidth and output power of a small amplifier (with attenuators). I have a small signal generator from Ebay, which steps through some frequencies. But the SA and signal are not in sync, so I need a peak hold to see max level of each frequency.

Re: #bug_report #bug_report

#6811

It is nearly April 1st so here is a really dumb, stupid question.
Why do you need to enter a frequency to 8 decimal places. 6 decimal places is 1Hz, why do you need one hundredth of a Hz.
I did say it is a stupid question.

Re: Minor bug: Displayed frequency range in HIGH Out mode wrong #bug_report

#6810

It's in the Start, Stop and Center window.

tinysa_screen_2022-03-24_19-14-04.png

Re: Minor bug: Displayed frequency range in HIGH Out mode wrong #bug_report

#6809

Forgot to mention the affected firmware:?tinySA_v1.3-347-g31eb02e

Minor bug: Displayed frequency range in HIGH Out mode wrong #bug_report

#6808

When switching to HIGH Out mode and clicking on FREQ it shows

CENTER? ? ? ?0..720MHz

instead of

CENTER? ? ? ?240..960MHz

on the bottom of the screen. Although entering values from 240..960MHz is perfectly possible.

(actually it's not possible to make a screenshot with tinySA-App from the this "number pad menu")

Re: Freezing TRACE 1,2 & 3 causes traces to disappear #bug_report

#6805

On Mon, Feb 21, 2022 at 10:20 PM, @SleepingCat wrote:

Just as an idea... (but it's not so important to implement in software)
A possible solution could be to use the last reflevel value that the auto-reflevel function determined shortly before deactivating the 3rd trace.
And switch back to auto revlevel if at least one of the traces is reactivated...
(If reflevel was previously set to manual, this mechanism should of course not be active).

Implemented with?tinySA_v1.3-347-g31eb02e. Working!

Thanks Erik!

Re: Firmware bugs #bug_report

#6804

On Wed, Feb 23, 2022 at 03:36 PM, @SleepingCat wrote:

Alright, as a side note:
In the SWEEP menu ("HIGH out" mode) the SPAN is selectable from 240..960MHz.
Guess correct would be: 0..720MHz (= 960MHz - 240MHz)

Fixed with?tinySA_v1.3-347-g31eb02e

Thanks Erik!

Re: #bug_report #bug_report

#6803

Retested with?tinySA_v1.3-347-g31eb02e

It's almost fixed but there is still a problem when entering more than 8 decimal points.
(entered values are with unit "MHz")

Enter 10.000 000? ? ? ? --> 10.000 000 MHz? ? - OK

Enter 10.000 005? ? ? ? --> 10.000 005 MHz? ? - OK

Enter 10.000 000 0? ? ?--> 10.000 000 MHz? ? - OK (a maximum of 6 decimal places are displayed on the screen)

Enter 10.000 000 5? ? ?--> 10.000 000 MHz? ? - OK (a maximum of 6 decimal places are displayed?on the screen)

Enter 10.000 000 00? ?--> 10.000 000 MHz? ? - OK?(a maximum of 6 decimal places are displayed?on the screen)

Enter 10.000 000 000 --> 1.410065 MHz? ? ? ?- WRONG

Another finding:
START frequency unit is always fixed to MHz. (Guess just a typo - its fine for STOP and CENTER and SPAN)
- entering some value in Hz shows MHz
- entering some value in kHz shows kMHz
- entering some value in MHz shows MMHz

Example:

Re: Ability to save High and Low output mode configuration and automatically recall it on power up #feature_request

#6801

<Wander Lucio
I've missed this a few times. mainly the external attenuator that I always use fixed and I always have to reconfigure.>

Note than the EXTERNAL GAIN is a parameter saved in Startup and Store features

开云体育

?