Thoughts for a firmware update
why on earth is it a must for many users to update the firmware and then cry because it went wrong? And then as a next step to annoy other users and especially Erik.
They should think about doing something productive and not tinkering with the TinySA - it works fine out of the box.
|
On Fri, Jun 14, 2024 at 03:08 AM, Erik Kaashoek wrote:
As clearly stated you should NOT use the latest Cube programmer but version 2.15
? The following was reported by a user on the NanoVNA group: "I have found that version 2.16.1 will indeed work, but you must do the 'full chip erase' before updating the firmware. Evidently in 2.16.x the erase function is no longer integrated with the programming."
If true, that would explain why users are having problems using the Wiki "Cube programmer" upgrade procedure with versions greater than 2.15.
Herb
|
Re: New FW release: Persistent external gain
|
As clearly stated you should NOT use the latest Cube programmer but version 2.15 --
Designer of the tinySA
For more info go to https://tinysa.org/wiki/
|
Repeat after me
Everything On line and everything on YouTube in particular is not always right
some is out of date
some omits important steps?
some is just flat out wrong?
The dudes ¡®showing you stuff¡¯ in a staged set on wrongly chosen/connected/adjusted test equipment and with no skill apart from liking talking are worst?
|
The latest STMcube app was the last straw for me?
Please someone, ?Make basic firmware flashing for end users a simple activity not a trip to a smoke filled starship¡¯s engine room?
|
It should be rated to handle the *dissipation* in that unit. So if you put 10 W total into a 3 dB attenuator then it needs to be rated for 5 W dissipation.
|
On Fri, Jun 14, 2024 at 07:34 AM, <valis@...> wrote:
Newbie attempt at updating the firmware. I was following someone's tutorial, everything seemed fine on STM32Cube, ...
Hello Valis,?
your attempt to follow an unknown tutorial has probably led you down the wrong path. ?It makes a lot of sense to trust the information in the wiki. e.g. ?
?
?
|
On the tinySA PCB there are connections for a serial interface labeled RX and TX. Connect these so a serial - wireless module and select the serial interface in the tinySA CONFIG/CONNECTION/SERIAL and set the serial speed --
Designer of the tinySA
For more info go to https://tinysa.org/wiki/
|
Now I want to add the function of wireless data transfer to the computer on tinysa, is there a better solution
Newbie attempt at updating the firmware. I was following someone's tutorial, everything seemed fine on STM32Cube, I pressed Start Programming, and instead of a long string of commands executing my process only took one second and when I went to restart there was....nothing but black screen. I don't recall the messaging at this point, but the result was the complete opposite of what I was aiming for. The power is present as can be seen by the red light indicator. But no boot...nada. I somehow managed to erase the firmware and the bios too? Now neither windows nor STM32 recognizes the device so I am a ship without a sail at this point.
Where do I go from here?
Thank you for whatever assistance you may be able to provide.
Valis
|
Re: No signal visible in IN ULTRA (LNA) CURVE calibration
#bug_report
±á¾±£¬ Now I want to add the function of wireless data transfer to the computer on tinysa, is there a better solution
Hi Erik,
when I do a input level calibration, via LEVEL CORRECTION -> INPUT CURVES -> IN ULTRA CURVE
everything is fine, except the last three frequency points, where just the regular noise but no signal
is visible on the screen. This happens only at the last three frequencies: 5.51 GHz, 5.85 GHz and 6.00 GHz.
In IN ULTRA LNA CURVE just the last frequency 6.00 GHz is affected.
I've checked, that the default calibration frequencies are rounded (here to 10 MHz). So, this should be
fine. As all the other frequencies show up correctly and also perfectly centered, I expect no
significant frequency shift due to production tolerances.
For IN HARM (LNA) CURVE everything is fine. It happens just for IN ULTRA (LNA) CURVE.
I've seen this reproduceable issue on both of my tinySA Ultra.
Firmware is the latest version.?
Best regards
Michael
?
|
Newbie attempt at updating the firmware. I was following someone's tutorial, everything seemed fine on STM32Cube, I pressed Start Programming, and instead of a long string of commands executing my process only took one second and when I went to restart there was....nothing but black screen. I don't recall the messaging at this point, but the result was the complete opposite of what I was aiming for. The power is present as can be seen by the red light indicator. But no boot...nada. I somehow managed to erase the firmware and the bios too? Now neither windows nor STM32 recognizes the device so I am a ship without a sail at this point.
Where do I go from here?
Thank you for whatever assistance you may be able to provide.
Valis
|
Re: Speaking of f/w updates...
It's not at all?uncommon DFU checks and verifications. It looks at the device, sees what's up, changes a few things and when all is good - does the do. Good utility doing it's job, well - just noisy about it.
Like Erik says, totally safe to ignore On Thu, Jun 13, 2024 at 12:26?PM Richard B. Emerson via <pavilion= [email protected]> wrote:
Well, went there, did that more'n once. Still am curious about what's going on, though. :)
73
Rick
KC3DOO
-- Tate Belden
A jack of all trades is a master of none, but oftentimes better than a master of one.
|
Re: Speaking of f/w updates...
Well, went there, did that more'n once. Still am curious about what's going on, though. :)
73
Rick
KC3DOO
|
Re: Speaking of f/w updates...
Just ignore --
Designer of the tinySA
For more info go to https://tinysa.org/wiki/
|
Speaking of f/w updates...
I just did the update for 170, which worked like a charm. But...? I'm curious about some of the info at the open of the run (on a patched to date Win 11 laptop).
C:\Users\pavil\Downloads\TinySA>dfu-util-static -a 0 -s 0x08000000:leave -D tinySA4_v1.4-170-g8e96644.bin
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
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 04f2:b7b6
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash ?"
Downloading to address = 0x08000000, size = 181408
Download ? ? ? ?[=========================] 100% ? ? ? 181408 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state
C:\Users\pavil\Downloads\TinySA>
The command is taken from the documentation (did C&P), and tweaked only for the right executable name and the .BIN name. Despite the seeming gripes, the u/l worked fine on both of my Ultras.? 73 Rick KC3DOO
|
>> The "centermost" conductor gives
the gender...except in reversed gender connectors!
>> John
>> at radio station VE7AOV
++++++++
On 2024-06-13 08:23, Prawlin via
groups.io wrote:
apart
from an unwritten convention that the 'male' plug end is the
source /high power end.?
Aha, but is that the male centre pin end, or the male thread end?
This gender description always gets me!
Peter
_._,_._,_
--
|
Oh my goodness
?
Perhaps this will help - my description of the high power 'SMA Male end' below complies with this convention? (pic attached)?
(Which includes RP options to illustrate that your native-logic is no help at all in this area)
?
|
On Thu, Jun 13, 2024 at 03:23 PM, Prawlin wrote:
Aha, but is that the male centre pin end, or the male thread end? This gender description always gets me!
Better stick with hermaphroditic connectors, such as the General Radio Type 874, but they are a bit bulky. Otherwise, this may (genuinely) help Regards, Martin
|
On 13/06/2024 16:23, Prawlin via
groups.io wrote:
toggle quoted message
Show quoted text
apart
from an unwritten convention that the 'male' plug end is the
source /high power end.?
Aha, but is that the male centre pin end, or the male thread end?
This gender description always gets me!
Peter
|
Wander Lucio
Bruce Akhurst
Tom_DG3NEO
WyoHam
Richard B. Emerson
mike