By the way, I noticed this morning a post on the NanoVNA site
where a user had the same driver issue you did with DFU on his
NanoVNA and found the same solution (bootloader vs ST Micro in
DFU Mode) which fixed it with the correct selection. The driver
interface is the same for either the TinySA or the NanoVNA.
....Ted (KD7AQO)
-----------------------------------------
From: "Terry Perdue"
To:
[email protected]
Cc:
Sent: Friday August 27 2021 8:41:56AM
Subject: Re: [tinysa] Can't update firmware
Oh, cool! How would anyone know to right-click the grid? Is
there a
Help
file somewhere?
On 8/26/2021 10:24 PM, Ted Chesley wrote:
> Hi Terry, THX for the reply on the drivers, I remember I
had
to do that once. That info might help out someone with the
same
problem.
>
> As to the TinySA interface with the TinySA-app, when
connected, clicking on the four arrows next to the freq
setting
will set the application to agree with the TinySA, the
start/stop
freq , data points etc, but not the grid. You have to right
click
on the grid and enter the desired MIN/MAX settings with the
manual
set. The auto set can be used when there is a waveform in the
screen.
>
> Happy Hunting¡.Ted (KD7AQO)
>> On Aug 26, 2021, at 8:46 PM, Terry Perdue
<K8tp@...> wrote:
>>
>> ?That¡¯s precisely what I found out the hard way
today.
>>> On Aug 26, 2021, at 8:11 PM, Jim Shorney
<jshorney@...> wrote:
>>>
>>> ?
>>> The thing that seems to bite a lot of people is
that
the Tiny/Nano gadgets are different device when in DFU mode
and
need a different driver. When connected to the computer in DFU
mode
you should see a "STM Device in DFU Mode" device appear in
your USB
tree under Device Manager. This driver is part of the
DfuSe_Demo
package but is not installed automatically. You have to hunt
it
down in the DfuSe folders and install it manually if it is not
showing up. I've been told that it is needed for the app to
upload
firmware but I can't say because I already had it installed
before
the app came around.
>>>
>>> 73
>>>
>>> -Jim
>>> NU0C
>>>
>>>> On Wed, 25 Aug 2021 20:45:07 -0700
>>>> "Terry Perdue"
<K8tp@...>
wrote:
>>>>
>>>> I'm not sure I understand that, but I should
mention that I see that
>>>> when using the tinySA app, it /automatically
/puts
the device in DFU
>>>> mode. That works. But as you can see, it
appears
to be unable to 'open'
>>>> the device to write the file to it. I've
tried
many times.
>>>>
>>>>> On 8/25/2021 8:04 PM, Ted Chesley wrote:
>>>>> Hey Terry, also forgot to add: you must
be
connected to the TinySA app
>>>>> before you can use the upgrade. I think
that's
the case but I haven't
>>>>> tried it before connection.
>>>>>
>>>>> -----------------------------------------
>>>>>
>>>>> From: "Terry Perdue"
>>>>> To:
[email protected]
>>>>> Cc:
>>>>> Sent: Wednesday August 25 2021 7:05:52PM
>>>>> Subject: Re: [tinysa] Can't update
firmware
>>>>>
>>>>> ? I don¡¯t see anything in the upgrade
document
about renaming any
>>>>> file. Can you elaborate?
>>>>>
>>>>>
>>>>>
>>>>>> On Aug 25, 2021, at 5:08 PM, Larry
Acklin
<acklin@...> wrote:
>>>>> ?
>>>>> I had the same issues. I used dfu-util, a
bit
of a PITA but
>>>>> figured it out. You need to follow the
how to
and also rename the
>>>>> file to what the batch file expects. It¡¯s
a
DOS based process but
>>>>> mine is running latest and works- passes
self
test and Cal.
>>>>>
>>>>> And Windows 10 needed to recognize the
tinySA
as a usb device-
>>>>> running zadig helped get it recognized.
>>>>>
>>>>>
>>>>> Good Luck
>>>>> Larry
>>>>> KB3CUF
>>>>>
>>>>>>> On Wed, Aug 25, 2021 at 7:25 PM
<K8tp@...> wrote:
>>>>>> I've downloaded dfusedemo, version
3.0.6.
With it running, I
>>>>>> connect the TinySA and put it in DFU
mode,
but the application
>>>>>> doesn't find it. If it's any help,
when I
enter DFU mode I get
>>>>>> the 'USB disconnect' sound.
>>>>>>
>>>>>> I've viewed a couple of YouTube
videos,
and can't figure out
>>>>>> what I could be doing wrong. Also, if
I
click CHOOSE and
>>>>>> select the new .DFU file, the
application
reports that the
>>>>>> file doesn't have the correct format.
Seems I have two
>>>>>> different issues.
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>