Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Can't update firmware
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 |
That¡¯s precisely what I found out the hard way today.
toggle quoted message
Show quoted text
On Aug 26, 2021, at 8:11 PM, Jim Shorney <jshorney@...> 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.
toggle quoted message
Show quoted text
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: |
Oh, cool! How would anyone know to right-click the grid? Is there a Help file somewhere?
toggle quoted message
Show quoted text
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. |
Terry, Yeah that's a problem with a lot of the software for these devices, you basically have to muddle through the program to gain familiarization with it. The TinySA app is a derivative from the parent application: NanoVNA-app, which has a lot more functions to support the VNA's. Also is the issue of the frequent firmware updates which generally don't have detailed explanations of the changes except as described in the rollout announcement messages from the group sites, and message queries from users? However, once relatively familiar with the programs use, it becomes second nature. It is useful to go through the wiki info and docs on the group sites, but much of the info is dated, and as the device FW is frequently updated, it's a chore to keep up.?
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. >>>>>> >>>>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> >> >> >> > > > > > |
¿ªÔÆÌåÓýThanks, Ted. I think the nanoVNA is next on my list, and it's good to know the proper driver is ready for it. You sure can carry a lot of decent test gear in your pocket now!On 8/27/2021 9:08 AM, Ted Chesley
wrote:
Terry, Yeah that's a problem with a lot of the software for these devices, you basically have to muddle through the program to gain familiarization with it. The TinySA app is a derivative from the parent application: NanoVNA-app, which has a lot more functions to support the VNA's. Also is the issue of the frequent firmware updates which generally don't have detailed explanations of the changes except as described in the rollout announcement messages from the group sites, and message queries from users? However, once relatively familiar with the programs use, it becomes second nature. It is useful to go through the wiki info and docs on the group sites, but much of the info is dated, and as the device FW is frequently updated, it's a chore to keep up.? |
I've been around computers long enough that I just know to try right-click when trying out software. As a former IBM OS/2 user right-click and I were good friends since long before Microsoft realized there was a right button....
73 -Jim NU0C On Fri, 27 Aug 2021 08:41:52 -0700 "Terry Perdue" <K8tp@...> wrote: Oh, cool! How would anyone know to right-click the grid? Is there a Help |
Arnie, go to the main TinySA site?https://tinysa.org/wiki/. Go down on home page to: Main Subjects in this wiki. Look in the table for Updating the Firmware and PC SW. Click on either and you will get a link to Erik's site, for the latest FW:??http://athome.kaashoek.com/tinySA/DFU/, and in PC SW for the TinySA app:?http://athome.kaashoek.com/tinySA/Windows/
For your DFU issue, this is a fairly common issue. You say your device is recognized when you power it on in windows. If so look in device manager/PORTS and see the STMicroelectronics Virtual COM Port (COM*) for the port your TinySA shows up on. This will appear and disappear as you turn the device off and on. Now go to DFU mode on the device, the previously showing port in PORTS will disappear and look now in Universal Serial Bus Controllers for "STM Device in DFU Mode". If you don't see this driver, then you are not loading the specific driver for the DFU link. The two drivers work together, one is for the normal interface and the other is for the DFU .interface. Take a look, if the DFU driver is missing there are links to install it either on ST Microelectronics website of in the group wiki. Good Luck ----------------------------------------- From: "W8DU_Arnie"To: [email protected] Cc: Sent: Saturday October 16 2021 12:23:11PM Subject: Re: [tinysa] Can't update firmware Where can I find the TinySA app? I looked in the wiki and don't see it. Tnx de Arnie W8DU |
Hey Arnie and others having this problem,? If you are missing the correct driver for the DFU mode when switched to DFU on the device, take a look on the NanoVNA site, message #24620,, from Dave W3MP and Don KB5QR, which addresses this issue and the fix. Apparently the computer loads STM Bootloader rather than the correct ST Device in DFU Mode so the driver has to be updated.?
NOTE: The NanoVNA and TinySA use the same ST Micro software so these instructions apply to both types of units.? It's a great idea to subscribe to both user groups as there are common operating issues between them. Also having both an NanoVNA and TinySA provides a wealth of complementary measurement capabilities especially for the ham or general RF engineer/tech. Good Luck ....Ted (KD7AQO) ----------------------------------------- From: "Ted Chesley"To: "[email protected]" Cc: Sent: Saturday October 16 2021 2:45:43PM Subject: Re: [tinysa] Can't update firmware Arnie, go to the main TinySA site? Go down on home page to: Main Subjects in this wiki. Look in the table for Updating the Firmware and PC SW. Click on either and you will get a link to Erik's site, for the latest FW:?? and in PC SW for the TinySA app:? For your DFU issue, this is a fairly common issue. You say
your device is recognized when you power it on in windows. If so
look in device manager/PORTS and see the STMicroelectronics Virtual
COM Port (COM*) for the port your TinySA shows up on. This will
appear and disappear as you turn the device off and on. Now go to
DFU mode on the device, the previously showing port in PORTS will
disappear and look now in Universal Serial Bus Controllers for "STM
Device in DFU Mode". If you don't see this driver, then you are not
loading the specific driver for the DFU link. The two drivers work
together, one is for the normal interface and the other is for the
DFU .interface.
Take a look, if the DFU driver is missing there are links to
install it either on ST Microelectronics website of in the group
wiki.
Good Luck
----------------------------------------- From: "W8DU_Arnie"To: [email protected] Cc: Sent: Saturday October 16 2021 12:23:11PM Subject: Re: [tinysa] Can't update firmware Where can I find the TinySA app? I looked in the wiki and don't see it. Tnx de Arnie W8DU |
On any of my recent laptops, I had to purchase a USB 2.0 hub to plug into any of the USB 3.0 ports on a recent PC, then plug the TinySA into the hub in order for it to be recognized correctly. It seems the TinySA was not correctly negotiating the the USB 3/2 connection and ¡°downshifting¡± into USB 2.0 mode.
Inserting the strictly USB 2.0 hub in the chain provided a USB 2.0 connection to the TinySA without having it struggle with whatever was failing with the negotiation process. This provided a reliable connection for me and I was able to do firmware updates without a problem. Steve |
to navigate to use esc to dismiss