开云体育

I followed the video of Erik Kaashoek to measure the noise figure of an amplifier I built. The outcome was 5.2dm/Hz. When I swapped the my amplifier with the LNa I was using, I got the same figure. I then change the bias of my amplifier to consume only 2mA, which as per Infineon should give the lowest noise figure, I got the same 5.2dbm/Hz again.
This repeated result may be due to to me doing wrong steps or missing something. So, I documented in the attached pdf file the test setup and the steps I followed.

Are these correct?

If only there was a way to slap a display and your amazing TinySA software on it!

I followed the steps explain in the link below to measure the noise level of an amplifier I built.


The outcome was 5.2dbm/Hz. When I switch the LNA and amplifier DUT to measure the noise level of the LNA, I got the same result (the LNA is a cheap one? with no noise figure specs!) Then I modified the biasing the DUT amplifier following the recommendation for lowest noise level from the manufacturer (current 2mA instead of 18mA), and redone the measurement, I got the same 5.2 dbm/Hz.
Having the same result every time made me suspicious about the steps I did being wrong or missing.

I documented the steps I followed in the attached PDF. Did I miss anything?

Thank you so very much all !!

Tried that one but "STM device in DFU Mode" did not appear

Anyway. I did find the solution bu searching for the driver in the PC:s Dirctory :
C: / Program Files (x86) > STMicroelectronics > Software > DfuSE v3.0.6 > Driver > Win 10

Now alls sorted out. B.r / tilman

True, but if the driver isn't installed first then every cable is bad. And the driver doesn't install by default with the commonly recommended DfuSe_Demo software. This is the most common firmware issue dating back to the early NanoVNA days. Therefore the first troubleshooting point is to check the driver. It is good practice to have more than one cable around anyway, and I have at least two originals and a couple eBay generics. All good. :)

73

-Jim
NU0C

On Sun, 24 Oct 2021 09:23:08 -0500
"Zack Widup" <w9sz.zack@...> wrote:

No, but if the problem IS with the cable, that won't solve it, either.

Zack

On Sun, Oct 24, 2021 at 8:30 AM Jim Shorney <jshorney@...> wrote:

The first check is to ensure the DFU mode driver is installed. This is a
very common problem as it does not install automatically and seems to be
poorly documented. Chances are if you haven't installed it manually then it
is not there. No amount of changing USB cables will solve this, only manual
installation of the driver. Once you are sure that Device Manger knows
about the DFU driver you can start checking USB cables.

73

-Jim
NU0C

On Sun, 24 Oct 2021 07:52:19 -0500
"Zack Widup" <w9sz.zack@...> wrote:

I keep saying you may have a bad USB to USB-C cable but everyone else

seems

to think it is something else. Both the cables that came with my TinySA

and

NanoVNA were bad and I had the same problem. I bought a better brand-name
cable and it's worked fine.

Zack

On Sun, Oct 24, 2021 at 2:08 AM Tilman D Thulesius <sm0jzt@...>

wrote:

I have followed the above. But I cannot see the "STM Device in DFU

Mode".

I only see STM32 Bootloader.

Please give me some advice on how to get that in

On Sun, Oct 24, 2021 at 03:35 AM, OneOfEleven wrote:

How to swap between the STM32 BootLoader driver and the STM32 DFU mode driver
====================================================================O

OneOfEleven's visual instruction should get you out of trouble, but here are some additional points that might affect you as well:

• In some cases you will need to reboot your windows after doing driver update
• Folder shown in his instructions might "look" differently - it's the one whit your DFUSe installation files, but do NOT go any deeper then the root of that folder structure as drivers are in different subfolders
• Make sure to check the box "Include subfolders" (as in his screen shot, but easy to miss :))
• DO NOT USE USB 3.0! Very often it does not work in DFU mode even when working fine as a COM port emulation! Or at least have USB 2.0 hub!

You can find the drivers in the bin / driver folder.
--
Gyula HA3HZ

The first check is to ensure the DFU mode driver is installed. This is a very common problem as it does not install automatically and seems to be poorly documented. Chances are if you haven't installed it manually then it is not there. No amount of changing USB cables will solve this, only manual installation of the driver. Once you are sure that Device Manger knows about the DFU driver you can start checking USB cables.

73

-Jim
NU0C

On Sun, 24 Oct 2021 07:52:19 -0500
"Zack Widup" <w9sz.zack@...> wrote:

I keep saying you may have a bad USB to USB-C cable but everyone else seems
to think it is something else. Both the cables that came with my TinySA and
NanoVNA were bad and I had the same problem. I bought a better brand-name
cable and it's worked fine.

Zack

On Sun, Oct 24, 2021 at 2:08 AM Tilman D Thulesius <sm0jzt@...> wrote:

I have followed the above. But I cannot see the "STM Device in DFU Mode".

I only see STM32 Bootloader.

Please give me some advice on how to get that in

If you don't have the drivers on your PC ..

you can find the DFU mode driver in this package ..



or if you prefer, you can find the STM32 bootloader driver in this package ..

How to swap between the STM32 BootLoader driver and the STM32 DFU mode driver
====================================================================

Open "Device Manager" and double click (or select it's properties) ..



Select the "Driver" tab ..



Select "Update Driver" ..



Select "Browse my computer for drivers" ..



Select "Let me pick from a list of available drivers on my computer" ..



Select the desired driver than you want to use and click "Next" ..



You should now have the desired driver loaded. Click "Close" ..

Try Cube programmer instead of dfuse demo

I have followed the above. But I cannot see the?"STM Device in DFU Mode".?

I only see STM32 Bootloader.

Please give me some advice on how to get that in

Hi there

When putting my TinySA in DFU-mode the driver/device "STM32 Bootloader" appears in my Win 10 Device manager.

Im struggling to find a way to get the "STM Device in DFU mode"?device appearing to be used for the "DFUse Demo" app so that I can do a FW upgrade.?

I have been looking out for hints in old topics in this forum, but cannot find any advice.?

I have been looking out for drivers to put on, but also have not found any.

Please advice. Thanks in advance / Tilman

/g/tinysa/message/4299

Eric,

I will be placing orders to Digi-Key and Mouser? for winter projects. I would like to add the ESD suppressors to my TinySA. Can you please provide manufacturer info and part numbers?

Thanks,

Mike N2MS

On Sat, Oct 23, 2021 at 12:41 AM, <sculacli@...> wrote:

1)?I can't find the history of hardware revisions anywhere. Thus far it seems the "hardware" V0.3 and V0.3.1_ are the versions showing up online. Are both of them legitimate? What are the hardware differences and the differences in their electrical performances?

Performance of both versions is identical. The V0.3.1_E version has additional protection against static electricity at the inputs

It's a 2 part question:
1)?I can't find the history of hardware revisions anywhere. Thus far it seems the "hardware" V0.3 and V0.3.1_ are the versions showing up online. Are both of them legitimate? What are the hardware differences and the differences in their electrical performances?

2) Are some of these versions clones:
For example, the RLelectronics (the recommended USA store) shows the V0.3 with white-ish sticker (image attached). Is that a legit copy? It seems to resemble the clone warning on the wiki.
Amazon on the other hand is full of V0.3.1_ with black sticker (see image attached) which seems like clones, as they have strange names. E.g. TinySA Karagas, TinySA AUSINC, TinySA SEESII, etc. Maybe those are store names but they strangely put them in the title.

Thanks in advance!