Keyboard Shortcuts
ctrl + shift + ? :
Показати всі комбінації клавіш
ctrl + g :
Не доступний для безкоштовних груп.
ctrl + shift + f :
Знайти
ctrl + / :
Сповіщення
esc to dismiss
Лайки
Пошук
VNA bricked.
|
Is there any way of getting the VNA back to normal?
I tried an update and the VNA just went white screen. It was a H version so decided to do an update to keep it fresh. All it does now is show a white screen and that is it. So is there any way of installing software maybe via SD card as it has a slot or via PC? Any help will be grateful. Will 2M0WHN |
|
Will,
I have a VNA that developed a white screen a couple of years ago for no apparent reason. I found that I can use NanoVNA-App with my PC and still have functionality. Another program is VNA Saver but I had trouble with that one. Hope this helps. Perry On Thu, Sep 19, 2024 at 3:28 PM william Northcote via groups.io <william.northcote@...> wrote: Is there any way of getting the VNA back to normal? |
|
Boot in the DFU mode and flash again (you probably flashed the H4 firmware).
If your device does not show up in DFU mode you will need to get a $5 programmer and flash it that way. On Thu, 19 Sept 2024 at 21:28, william Northcote via groups.io <william.northcote@...> wrote:
|
|
I'm new to the NanoVNA-H4 and am having difficulty upgrading its firmware. What is this $5 programmer you mentioned and how do you use it? Does anyone have instructions?
переключити цитоване повідомлення
Показати цитований текст
Thanks!Bruce JS2OLO On Friday, September 20, 2024 at 06:07:21 AM GMT+9, Dragan Milivojevic <d.milivojevic@...> wrote:
Boot in the DFU mode and flash again (you probably flashed the H4 firmware). If your device does not show up in DFU mode you will need to get a $5 programmer and flash it that way. On Thu, 19 Sept 2024 at 21:28, william Northcote via groups.io <william.northcote@...> wrote:
|
|
The programmer will likely require you to open the unit and attach a cable internally (possibly install a header - not sure if there is one in all -H4 devices or not).
переключити цитоване повідомлення
Показати цитований текст
What problem are you having programming? The -H4 is one of the easier ones to do, althoughnthere is a "gotcha" that hits a lot of folks that they fail to install the dfu driver if on a Windows box. On September 19, 2024 10:17:10 PM EDT, "Kmpres via groups.io" <kmpres03@...> wrote:
I'm new to the NanoVNA-H4 and am having difficulty upgrading its firmware. What is this $5 programmer you mentioned and how do you use it? Does anyone have instructions? --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
My NanoVNA-H4 came with FW v1.2.27 installed. The groups.io Files page listed the latest version as v1.2.29, so I downloaded and attempted to install it using my newly built Windows 11 PC with an Asus motherboard. Got as far as the DfuSeDemo_3.0.6_Setup program reading my device (which presumably indicates the correct driver is installed), but no matter what I do I can't get it to "choose" the dfu file and begin the install.
переключити цитоване повідомлення
Показати цитований текст
I now can't seem to find any dfu file newer than v1.0.69 which dates from 7/24/21. So, I'm confused. What exactly is the newest version, where is it, and how do I install it? Thanks,BruceJS2OLO On Friday, September 20, 2024 at 12:28:51 PM GMT+9, Tim Dawson <tadawson@...> wrote:
The programmer will likely require you to open the unit and attach a cable internally (possibly install a header - not sure if there is one in all -H4 devices or not). What problem are you having programming? The -H4 is one of the easier ones to do, althoughnthere is a "gotcha" that hits a lot of folks that they fail to install the dfu driver if on a Windows box. On September 19, 2024 10:17:10 PM EDT, "Kmpres via groups.io" <kmpres03@...> wrote: I'm new to the NanoVNA-H4 and am having difficulty upgrading its firmware. What is this $5 programmer you mentioned and how do you use it? Does anyone have instructions?-- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
Have you read the manual for DfuSeDemo? (If not, it's short, and I suggest that you do so . . . )
переключити цитоване повідомлення
Показати цитований текст
The direction of transfer is confusing . . . Despite 99.7% of the world thinking that an update would be an ipload, in this tool it's a download . . . So be sure that you are trying to select the dfu file in the correct place (the box bottom center, just above the status bar). Baring that, perhaps what you have downloaded is not actually a dfu file. One of the best sources for downloads is https://github.com/DiSlord/NanoVNA-D another is https://github.com/hugen79/NanoVNA-H/releases Select "Releases" on the right side, and all should be there. - Tim On September 20, 2024 10:45:39 AM EDT, "Kmpres via groups.io" <kmpres03@...> wrote:
My NanoVNA-H4 came with FW v1.2.27 installed. The groups.io Files page listed the latest version as v1.2.29, so I downloaded and attempted to install it using my newly built Windows 11 PC with an Asus motherboard. Got as far as the DfuSeDemo_3.0.6_Setup program reading my device (which presumably indicates the correct driver is installed), but no matter what I do I can't get it to "choose" the dfu file and begin the install. --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
Hello William,
If you check the file section, you will find a step by step guide I uploaded on how to recover the NanoVNA H from white screen. No, you did not brick your H. It is in a boot loop. Either you installed the wrong FW or missed a step while installing the FW. No problem. Just follow my guide. Clyde KC7BJE |
|
NanoVNA H WHITE SCREEN RECOVERY
First, this procedure is for white screen recovery due to installing the wrong FW, which is one of the main causes of white screen. 1. Turn nva off. 2. Remove back of case. 3. Short the "boot pad" to the "vcc pad" next to it. While holding the short, turn the nva on. NOTE; The following is done while the nva is still on after removing the short on boot and vcc pads. Make sure you have the correct FW!!! H for H!!!! 4. Leaving the nva on, remove the short. Your nva is now back to the DFU state and out of boot loop. 5. Reassemble the back case. 6. Connect the nva to the CPU or phone, if using Android app, proceed to update the FW. 7. After update, turn nva off then back on. If the white screen is off and nva turns on correctly, your done. 8. If your nva is still in white screen mode, again make sure you installed the correct version of FW. If so, you have a bigger problem that requires trouble shooting and physical repair. Clyde KC7BJE |
|
Note that Clyde's instructions in the prior post are for the H device, not
your H4. You don't need to open it and short the pads, just press the jog wheel while turning it on. And make sure you use the H4 code. And re-download it just in case you overwrote the original file using the wrong option in Dfusedemo. On Fri, Sep 20, 2024, 1:13 PM Clyde Lambert via groups.io <clyde.lambert= gmail.com@groups.io> wrote: NanoVNA H WHITE SCREEN RECOVERY |
|
Thanks, Tim. Through your links I found that the latest version is now V1.2.40. With the help of Alan Wolke's YT video I was finally able to get my unit updated to that version. I'm not really sure what the hangup was though switching to my old Win 10 PC and using its USB 2.0 port, as suggested by the Absolute Beginner Guide v1.6, probably helped. The Guide, BTW, could do with an update of its own as most of the file names have changed since it was last updated.
переключити цитоване повідомлення
Показати цитований текст
Thanks,Bruce JS2OLO On Saturday, September 21, 2024 at 12:02:14 AM GMT+9, Tim Dawson <tadawson@...> wrote:
Have you read the manual for DfuSeDemo? (If not, it's short, and I suggest that you do so . . . ) The direction of transfer is confusing . . . Despite 99.7% of the world thinking that an update would be an ipload, in this tool it's a download . . . So be sure that you are trying to select the dfu file in the correct place (the box bottom center, just above the status bar). Baring that, perhaps what you have downloaded is not actually a dfu file. One of the best sources for downloads is https://github.com/DiSlord/NanoVNA-D another is https://github.com/hugen79/NanoVNA-H/releases Select "Releases" on the right side, and all should be there. - Tim On September 20, 2024 10:45:39 AM EDT, "Kmpres via groups.io" <kmpres03@...> wrote: My NanoVNA-H4 came with FW v1.2.27 installed. The groups.io Files page listed the latest version as v1.2.29, so I downloaded and attempted to install it using my newly built Windows 11 PC with an Asus motherboard. Got as far as the DfuSeDemo_3.0.6_Setup program reading my device (which presumably indicates the correct driver is installed), but no matter what I do I can't get it to "choose" the dfu file and begin the install.-- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
I think I have a problem:
I have an NanoVNA-H, which has worked well as long as I've had it (2020, ver. 3.4). The other day I tried to connect it to Nano-VNA Saver. It wouldn't connect (I've got Windows 11) via any of the 3 USB ports I have. I suspected that my firmware, which was v. 1.2.20, was out of date. I found out that the current version is 1.2.40. I d/l'ed NanoVNA-H.v.1.2.40 (not H4) and attempted to update the f/w with Dfusedemo. ST.com said that "This product is NRND We recommend you that replacement part: STM32CubeProg". I d/l'ed that, attempted to load the firmware, but got a white screen. I tried Clyde Lambet's method for getting rid of a white screen, but the "boot pad" and "vcc pad" on mine was "VDD" and "Boot 0". I shorted them anyway, but now the device doesn't do anything but have a white screen. Can it be fixed, or do I just chalk it up to bad luck, and get another NanoVNA? |
|
You can't brick your nanovna with a firmware download. If properly loaded, that firmware file should work fine. And so should your older firmware, it is still a fine version - the problem was likely a cable or driver issue.
First check your cable, this is more often than not the problem. Make sure it is a good data cable, maybe by connecting to your smartphone or other storage device. These cables do break, or may be just charging cables. Also there are sometimes problems with USB-C ports on the computer side, so use a USB-A port, preferably a lower-speed one, with an A to C cable. Bring up Device Manager on your Win11 machine. Scroll down to where it has the USB Controllers item and expand it. Connect your nanovna via USB cable, and see if the devices update with a new entry, either "STM BOOTLOADER" or "STM Device in DFU mode". This may appear under USB Controllers, or perhaps in a new entry category directly under that of USB Devices. If one of those appear, your nanovna is OK and waiting for a good firmware download. If the driver is STM BOOTLOADER, you must use the new STMCubeProgrammer you downloaded to update the firmware. After selecting USB and connecting on the right side of the window, click the green "download arrow" icon on the far left of the window and use the Download function to update the firmware, using the default address. If your version of STMCubeProgrammer is 2.16.0 you must first click the "Full Chip Erase" button to the right in that window before doing the "Start Programming" button. Other versions (earlier and later) integrated that action, so there is no need to do it first. If the driver is STM Device in DFU mode, you must use your old DFuseDemo - it still works fine. Use the "Upgrade or Verify Action" part of the window to update the firmware. If you inadvertently used "Upload Action" before, re-download the firmware file from the web site, since you may have over-written it. If one of those two devices do not appear, start up your nanovna again by shorting the vdd and boot pins to force it into DFU mode. If a device appears with some other STM or DFU label, you need to install or update the driver. The Win11 default driver is the STM BOOTLOADER one. If you instead see a device appear under "Ports (COM & LPT)", your nanovna is running some firmware and has initialized the COM ports. You should be able to connect to nanovna-saver on the indicated com port, and your white screen may be another problem. Try updating the firmware again, and if it still has the white screen, search prior messages on this list for "white screen" and you will see other debugging methods. Good luck, Stan |
|
The problem is the version of STM Programmer. Roll back to version 2.15.0
and it should fix the issue. Last resort, you may need to jumper the "bootp" to supply of GND (as directed in the notes) to run the programmer. The roll back fixed the problem with my NanoVNA-H. Just my $0.02 worth..... On Fri, Oct 11, 2024 at 1:56 PM Stan Dye via groups.io <standye= gmail.com@groups.io> wrote: You can't brick your nanovna with a firmware download. If properly-- Michael L Robinson, KC0TA FREEDOM is NEVER given; It Is WON! “In the beginning of a change the Patriot is a scarce man, and brave, and hated and scorned. When his cause succeeds, the timid join him, for then it costs nothing to be a Patriot.” ― Mark Twain When Tyranny becomes Law, Revolution becomes Duty! |
Clyde Lambert
Barry Leonard KN4JRF
Повідомлення
Більше
Додаткові параметри
Більше
to navigate to use esc to dismiss