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
NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
|
This is the third Topic generated during my trip along the path to becoming a NanoVNA user.
toggle quoted message
Show quoted text
In the first I described a problem with getting the NanoVNA to be recognized by my laptop running W10, either in the normal NanoVNA operating mode or in DFU mode. With the Group's assistance I was able to get the device to respond to the USB port only in DFU mode. Unfortunately I upgraded to an older, less capable dfu without clearing the device or saving the originally dfu. So I decided to return to the original dfu which I neglected to save but have tentatively identified as DisLord's NanoVNA-H Version 1.1 dfu. Unfortunately I was unsuccessful in that attempt and generated the second Topic. In the second Topic I used the term "Bricked?" in the subject and repeatedly described the unit as bricked which was technically incorrect. Many users responded with helpful suggestions but I was unable to get the unit to work in any way other than to execute the loaded firmware to analyze the spectrum. I apologize for any confusion caused by describing the unit as bricked. I am generating this Topic to describe the current problem which is that the unit is detected but not recognized in its normal operating mode and will not allow me to change the driver, and it is not recognized at all in what appears to be the DFU mode. The question to be answered is whether the problem is in the unit, or in the computer I am trying to connect to. In the second thread, Ho-Ro has commented: QUOTE Ho-Ro 9:12am #31144 On Thu, Jan 26, 2023 at 05:19 PM, Al Waschka wrote:
will not recognize the device as being in dfu mode As a simple test you could connect the NanoVNA to a Linux computer, e.g. a Raspberry Pi and look what the command "lsusb" or "sudo dmesg" will tell you. If you do not have a Pi, just ask one of your friends, a lot of people with a technical hobby have these liitle boards in their drawer. Linux has the big advantage, that this nasty USB driver hell of Windows does not exist - USB just works out of the box. "lsusb" for normal mode (relevant line): Bus 006 Device 008: ID 0483:5740 STMicroelectronics Virtual COM Port "lsusb" for DFU mode (relevant line): Bus 006 Device 007: ID 0483:df11 STMicroelectronics STM Device in DFU Mode This is the output of "sudo dmesg" when switching the NanoVNA on in normal mode: [Jan26 06:05] usb 6-2: new full-speed USB device number 5 using uhci_hcd [ +0,181664] usb 6-2: New USB device found, idVendor=0483, idProduct=5740, bcdDevice= 2.00 [ +0,000009] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0,000006] usb 6-2: Product: NanoVNA-H [ +0,000004] usb 6-2: Manufacturer: nanovna.com [ +0,000004] usb 6-2: SerialNumber: 1.2.19_noSD [ +0,003171] cdc_acm 6-2:1.0: ttyACM0: USB ACM device And this is "sudo dmesg" for "Jog-press-switch-on": [ +4,991887] usb 6-2: new full-speed USB device number 7 using uhci_hcd [ +0,180616] usb 6-2: New USB device found, idVendor=0483, idProduct=df11, bcdDevice=22.00 [ +0,000010] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0,000005] usb 6-2: Product: STM32 BOOTLOADER [ +0,000005] usb 6-2: Manufacturer: STMicroelectronics [ +0,000004] usb 6-2: SerialNumber: FFFFFFFEFFFF HTH Martin UNQUOTE I am currently following that path, but I have to acquire a Linux capability first. |
|
Chronology of the Problem
1. Unpacked NanoVNA ordered from eBay vendor as a non-H unit, powered up and operated, including calibration, configuration, and testing an existing antenna system until the display started to dim. VERSION identified the dfu as NanoVNA-H Version 1;1 Build Time Dec 21 2021 2. Plugged the unit into a powered USB hub to charge the battery. The laptop powered up but not active. 3. After charging, played with it some more, including trying to install and operate VNA Saver on a laptop, with no success. The device would be detected by the laptop as an “Unidentified Device” and would not allow me to update the driver to the STM USB CommPort driver in the 32102(?) zip file. As a result, I decided to change the firmware load. I picked a load identified as nanoVNA_800_ch_20190920.dfu and after calibrating and configuring it realized it was substantially less capable than the original load. I decided to replace the dfu with another. 4. I went through the documented process for installing DfuSe demo on my laptop. When I tried to complete the verify drivers step, I found that the laptop was reporting “STM Bootloader” as the device, instead of the correct “STM Device in DFU Mode”. After several iterations I found that it might be necessary to manually install the proper driver. When I did that the proper designation appeared and I installed nanoVNA_800_ch：50K-900MHz dfu. 5. Immediately on started the new firmware I noticed the lack of features. There was no CONFIG menu. The list of parameters available for display in the FORMATS menu significantly less than in the original version and lacked the R and X values that I am particularly interested in. I decided to change back to the original version and immediately noticed there was no DFU option in the menus. After some research I discovered that pressing the jogwheel down while powering the device up might put in in DFU mode. When I did that, I got a white screen which is allegedly indicative of being in DFU mode. 6. When I connected the device to the laptop used to load the new firmware onto the device the computer did not react at all. When I went into device manager, I expected to see the “STM Device in DFU Mode” identified but it wasn’t there. Neither was the “STM Bootloader”. 7. When I posted these facts on Groups.io several members responded with suggestions including that the cable might be bad, or something changed in the computer. 8. I purchased and tried a new cable without success. The new cable came from the phone section and was identified as a charging cable, but the description said you could transfer data while charging. I tried the device on another computer with both cables with no success. Even on the new computer which did not have the DFU mode driver there was no indication of the “STM Bootloader”. 9. At various points during this process while testing DFU mode I would try powering on with the Vcc to Boot0 jumper in place, which also produced the white screen response but didn’t change the way the device enumerated on the laptop, i.e it didn’t show up in device manager. 10. Also at various points in the process I tried to update the driver with the device on normal operating mode, but was never able to successfully install the Com Port driver. 11. I am pursuing two paths to identify the guilty party, i.e. the device or the computer. I am trying to get my hands on a Liinux device to see how it responds in both modes to Linux commands and trying to locate an Android device capable of loading the NanaVNA app. 12. More as it happens…… |
|
Hi,
toggle quoted message
Show quoted text
In point 8 you say that the new cable is identified as a "charging cable" and this type of cable is only for charging but not for data transfer. After that you say that in the description they say that you can transfer data while charging, so this is not what a "charging cable does", this description applies to a "normal" cable.? I would check both cables with a phone for transferring files or images between the phone and a PC. It they work the cables are OK. Regards, Ignacio El 27/01/2023 a las 1:59, Al Waschka escribió:
Chronology of the Problem --
Este correo electrónico ha sido analizado en busca de virus por el software antivirus de Avast. www.avast.com |
|
Thanks,
The question is which statement in the manufacturer's brochure is incorrect. But the "other cable" is the one that came with the NanoVNA and it worked a few minutes prior to the point at which it didn't work. I have a ISB-A to USB-C adapter I bought yesterday, and a USB-A Male to Male cable coming tomorrow. That setup will implement a USB-A to USB-C cable that whould work. If it does then we will know the problem was the cable. I suspect it will not. |
|
On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote: Al, You could download a "live" image, no installation required. For your HW this small "rescue-linux" should be ok: - Select the "grml-small" "32-bit PC" version, currently this one: - Burn as ISO to a CD and boot the laptop from this CD. - Then just type "dmesg -Hw" and connect your NanoVNA. Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.). Martin |
|
Hope this isn’t considered off topic. It is about troubleshooting a NanoVNA.
toggle quoted message
Show quoted text
Finally got the greml distro working. When I enter the string you suggested it says -H is unrecognized. On Jan 27, 2023, at 6:07 AM, Ho-Ro <linuxaudio@...> wrote: |
|
Actual response is Invalid parameter, I think
toggle quoted message
Show quoted text
On Jan 27, 2023, at 6:00 PM, Al Waschka <awaschka@...> wrote: |
|
Looks like a distro with crippled dmesg . . . . the man page clearly states "-H: Human readable output" and "-w: wait" so the options *should* be valid.
toggle quoted message
Show quoted text
On January 27, 2023 6:17:49 PM CST, Al Waschka <awaschka@...> wrote:
Actual response is Invalid parameter, I thinkOn Jan 27, 2023, at 6:00 PM, Al Waschka <awaschka@...> wrote: --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
Thanks, I was wondering if that was the cause. I just picked up my ipad to check the syntax but saw your message first.
toggle quoted message
Show quoted text
Greml small was suggested so that is what I loaded. I am running on an old xp box with 1G ram and 1.7 ghz celeron. I’ll try to find another to load. On Jan 27, 2023, at 7:27 PM, Tim Dawson <tadawson@...> wrote: |
|
You can still see what is going on without the "-H" option, the output is just a little less clear. Basically, run "dmesg -w", and then plug the USB device in, and you should see the system react to it. (You can also see the same in syslog . . .)
toggle quoted message
Show quoted text
On January 27, 2023 6:33:23 PM CST, Al Waschka <awaschka@...> wrote:
Thanks, I was wondering if that was the cause. I just picked up my ipad to check the syntax but saw your message first. --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
Distro is very limited. Doesn't have -w either. I give up on Linux. I can't get the CD drive to load anything else or even to reload the Grml-small I had on there to begin with.
toggle quoted message
Show quoted text
I received my USB-A Male to Male cable. I connected it, with an A-C adapter between the original W10 laptop and the NanoVNA. It gave the same result as the other two cables. When I said the device was working properly in the analyzer mode I had only looked at boot behavior. I don't remember actually checking it on an antenna. When I connected it to my tuned antenna its readings are different from the SWR meter on my transceiver. It has also started flashing the white screen momentarily when turning on in the analyzer mode. I don't recall noticing that before. I think either the device is failing or possibly the hardware was not compatible with the firmware I loaded. I am officially giving up on trying to figure out what happened. I guess I'll have to take the risk that it won't happen with whatever replacement unit I get. Going back to vendor tomorrow. K5TAN ZZZZ Out -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Tim Dawson Sent: Friday, January 27, 2023 7:40 PM To: [email protected] Subject: Re: [nanovna-users] NanoVNA Not Recognized by Laptop over USB After dfu Upgrade You can still see what is going on without the "-H" option, the output is just a little less clear. Basically, run "dmesg -w", and then plug the USB device in, and you should see the system react to it. (You can also see the same in syslog . . .) On January 27, 2023 6:33:23 PM CST, Al Waschka <awaschka@...> wrote: Thanks, I was wondering if that was the cause. I just picked up my ipad to check the syntax but saw your message first.-- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
You can run "dmesg" alone and see what you see, then plug in and run it again, and if it saw the device, it will be at the end of the display, past what you saw the first time.
toggle quoted message
Show quoted text
On January 28, 2023 12:26:07 AM CST, Al Waschka <awaschka@...> wrote:
Distro is very limited. Doesn't have -w either. I give up on Linux. I can't get the CD drive to load anything else or even to reload the Grml-small I had on there to begin with. --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
I thought I might be able to see something in dmesg, as it worked before when I finally got grml-small loaded after several tries. Unfortunately I tried to load a better Linux distro but the CDROM drive was acting up. When I tried to reload greml-small again it wouldn't finish the install without errors.
toggle quoted message
Show quoted text
The unit is packed and going to the PO tomorrow. I ordered a -H4 from R&L. Looking forward to using it. Thanks to everyone who tried to help. Al K5TAN -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Tim Dawson Sent: Saturday, January 28, 2023 2:09 AM To: [email protected] Subject: Re: [nanovna-users] NanoVNA Not Recognized by Laptop over USB After dfu Upgrade You can run "dmesg" alone and see what you see, then plug in and run it again, and if it saw the device, it will be at the end of the display, past what you saw the first time. On January 28, 2023 12:26:07 AM CST, Al Waschka <awaschka@...> wrote: Distro is very limited. Doesn't have -w either. I give up on Linux. I can't get the CD drive to load anything else or even to reload the Grml-small I had on there to begin with.-- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
Sometimes I question my sanity - this thread is such an example. Before I recommended grml, I picked up my grml32-small CD and booted my laptop; typed "dmesg -Hw" and plugged in the NanoVNA-H, switched it on and off, with and without jog switch - great display, just as expected. But then this message
On Fri, Jan 27, 2023 at 11:59 PM, Al Waschka wrote: and later: What have I done wrong? I always have this rescue CD with me and also use it when a PC in the family stops working (with the description: "I didn't do anything") - ok, the grml version is older, approx. 2020. Crap, did the makers " castrate" the programs to save space? So I downloaded the latest version grml32-small-2022.11, (just like Al); took an old lab laptop, booted it - typed in "dmesg -Hw" - perfect - detected all USB actions etc. Even if it is no longer helpful for Al - maybe it will help someone else who really wants help. In short - if you distrust your Windows, boot a Linux live system (only boot from CD, don't install anything) and explore the HW with the numerous tools - especially for NanoVNA and tinySA: Watch system messages in real time: dmesg -Hw What's going on at the USB: lsusb Martin |
|
Thanks Martin, for the update, and your attempt to help this NanoVNA noob.
I did not watch the full boot sequence. When I tried to load Greml again after trying to load a Debian live distro that wouldn't load, it listed failures, but it stopped and never completed the startup. When Greml first loads, there is a menu there. Which option did you load? Down arrow to select the few highlighted options did not worlk for me. Perhaps I should have taken that bit of information as indication of a load problem. Good to know that it should have worked. I had several of these laptops. I think I cleaned the drives and tossed the others but if I can find one or a replacement CD drive, I will see what happens when I load the .iso. |
|
I have a box full of NOS laptop DVD drives if you need one. Mostly SATA but a few PATA as well.
73 -Jim NU0C On Sat, 28 Jan 2023 09:31:02 -0800 "Al Waschka" <awaschka@...> wrote: Good to know that it should have worked. I had several of these laptops. I think I cleaned the drives and tossed the others but if I can find one or a replacement CD drive, I will see what happens when I load the .iso. |
Ho-Ro
Jim Shorney
to navigate to use esc to dismiss