Edition??? Windows 10 Pro
Version??? 22H2
Installed on??? ?9/?28/?2020
OS build??? 19045.4046
Experience??? Windows Feature Experience Pack 1000.19053.1000.0

I was running Windows 7 in early 2020 and I upgraded to Windows 10 at the end-of-service of ver 7.

Thank you.

Looking at the code change, is the increased acceptable range for self-test 9 or is that actuality self-test 10? I ask because my occasional test 10 fails have gone away with this firmware update.

Peter

It is http vs. https. Any site not using https is considered to be insecure. Which does not necessarily mean unsafe.

73

-Jim
NU0C

On Mon, 26 Feb 2024 19:18:22 +0100
"Hans Boon" <pa2hbn@...> wrote:

Hello Erik,

I am always getting a message in Chrome about "insecure download" and
have click "keep" to download the file.

Could it be your website is on some Chrome blacklist.

Hans

A multi-band configuration when restored from SD does not restore RBW. Duplicate by changing the RBW followed by a restore. Oddly, the RBW field in the display shows the incorrect RBW actually being used but when you click on it to bring up the RBW setting the correct/desired value is checked, not the one actually in use.

NOTE: This is only a defect for configurations WITH multi-band AND when saved to SD, not one of the 4 in-memory slots.

If you prefer, I can open an issue in for this in github. Not sure of proper protocol.

Peter

Horace,

What version of Windows are you using on the laptop?

Roger

That's Great!? Thank you.

Yup - just had to read the CONFIG menu list....;-)
PULSE HIGH enables a trigger signal from the CAL output at the start of each low input sweep.

On 26/02/2024 18:18, Hans Boon via groups.io wrote:

Hello Erik,

I am always getting a message in Chrome about "insecure download" and
have click "keep" to download the file.

Could it be your website is on some Chrome blacklist.

Hans

Hans,

It's just Chrome being extra careful about the file type. From Erik's site,
it's OK so keep pressing keep!

Cheers.
David
--
SatSignal Software - Quality software for you
Web:
Email: davidtaylor@...
Twitter: @gm8arv

Thank you for the link.

1. Memory Integrity for both machines are already set to OFF. So this isn't the issue, in my case anyway.
2. Comm Port Driver - I don't see any new comm port being added when I turn ON or OFF the tinySA Ultra. I have however successfully installed the tinySA-App prior to my attempts to update the FW.
3. Firmware Upgrade driver - On my desktop, the only thing I see being added to the Device Manager when my tinySA Ultra is in DFU Mode is the STM BOOTLOADER under Unirversal Serial Bus devices. And the FW Update worked perfectly fine. So I'm a bit hesitant to uninstall it as suggested. However, on my laptop, the STM BOOTLOADER doesn't ever show up, no Comm Ports either. But I get a strange message when I try to run the STM32CubeProg. Clicking Refresh Port under USB Configuration doesn't bring up anything. This item was done automatically on my desktop.

I've checked and tried all 3 but nothing worked on my laptop. So I feel that it could be a driver issue, unless I missed something else.

I have kept a screenshot of the topic discussed on the link given for reference. I'm might come in handy later.

Thanks again.

Horace F

Yes
You may have to enable it in the config menu
--

Hello Erik,

I am always getting a message in Chrome about "insecure download" and have click "keep" to download the file.

Could it be your website is on some Chrome blacklist.

Hans

I took screenshots from the desktop and laptop (STM32_driver_versions.zip). The laptop does not have the STM32 BOOTLOADER under Universal Serial Bus Devices. I was able to get the Driver versions installed on the desktop but none for the laptop. I hope these are the correct drivers you're asking for.

I also tried to manually install the drivers for DfuSE as suggested by @Jim Shorney, which I found in my C:\Program Files (X86) folder. I also checked the drivers folder for the STM32CubeProg under my C:\Program Files folder with is installed during the install process. I also manual installed it again. Still the same issues for both.

The process went smoothly on my desktop. After I installed STM32CubeProg which also installed the drivers, it easily recognized the tinySA after I put it in DFU mode. I didn't even have to click the refresh button. So this could be a problem with the drivers for my laptop.

I hope that STM could come up with updated drivers. I sure would like to do my next FW updates on my laptop.

Thank you.

My bad.?

Erik,
I was browsing EEVBlog and came across this post:

The OP talks about a pulse generated at the HIGH output every time a new sweep starts on the LOW output.
I don't have my unit with me so I was wondering if you ported this (feature?) to the Ultra?

Thanks

Did you connect the cal output back to the input?

开云体育

Who did you buy it from? ?Send it back for a refund.

I Just received a new TinySA Ultra, gave it a full charge and it failed selftest #1 and stopped.
I turned it off and back on and now it passes #1 but fails #3 (Signal Level Failed).
I tried to run it again 7 times and each time it stops on #3.
What is my next step?
Geo

Here is a link to a discussion of this problem in this group a year ago.

/g/tinysa/message/10816

Roger

I wrote about Windows 8 drivers on the Nanovna group. It also applies to the tinysa.

/g/nanovna-users/message/31583

Roger

This has been discussed in various forums many times. The TSA can be one of two devices: STM Bootloader or DFU device. Thus two different device drivers. The DFU driver does not get installed automatically for whatever reason but it there in the STM folder tree for various Windows versions. It needs to be installed manually.

There is also a command line utility for Linux that seems to work with little fuss.

73

-Jim
NU0C


On Mon, 26 Feb 2024 06:35:47 -0800
"Horace F" <hgf3888@...> wrote:

So my question is what other alternatives do we have aside from using STM32Cube Programmer or the DfuSE apps? if they can't recognize the USB drive? Luckily I have my desktop that worked. But what if I didn't? I'm asking this on behalf of all those who posted about the failed FW Update. I read through it without a solution. Are there compatible drivers (non-STM) that could work with the STM32Cube Programmer and/or the DfuSE apps?