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
- Nanovna-Users
- Messages
Search
Re: Bricked NanoVNA-H
This is the excellent and to date latest version of the Guide Richard.
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_5.pdf |
Re: Bricked NanoVNA-H
I've very little else to right now Richard, I'm one of the shielders in the Uk.
I got all my info from here Richard, /g/nanovna-users/topic/a_guide_for_absolute/78077375?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,78077375 There's a lot to read through but Like I say, I've lots of time on my hands right now. The NanoVNA-App software is really up to date and a huge improvement on other software that I've used in the past. This lets you upgrade the firmware from the program which might get you up and running. It sounds good that you're seeing a com port so that's a start. Kind regards, James. It can be hugely frustrating when thing don't go to plan but it looks like you're getting there. |
Re: Bricked NanoVNA-H
James thanks for all the help, almost like good old pre-covid lab work sitting next each other :P
ok, the NanoVNA is seen as Com 44, was a simple serial port but after updating the driver did see it as "STMicroelectronics STLink Virtual Com Port (Com44)" where did you download the PC software that you are using what is is called... let me load it so that we may compare apples and apples... 73 |
Re: Bricked NanoVNA-H
Richard,
I have just tried to connect my freshly upgraded NanoVNA device to the VNA-QT software but it keeps giving me this error. xavna_read_autosweep_failed: Resource deadlock avoided I know my NanoVNA is on com port 3 three as its in device manager. Using com port 3 it WILL connect to NanoVNA-App. Hope that helps. |
Re: Bricked NanoVNA-H
Hi Richard.
Have you tried the NanoVNA-App software to do the upgarde. I upgraded using the option from NanoVNA-App 1-of-11 LSI. Can you see the NanoVNA in device manager as STM Device in DFU mode within Universal serial bus "controllers"? This for me was critical to connect to the NanoVNA device. I know you've stated that you can see it as STM Device in bootloader mode but it has to be in STM Device in DFU mode in device manager within Universal serial bus controllers to get connected. If after that either works or doesn't work then I'm out as I can't think of anything else for now. I'm just checking out VNA-QT as I write. Kind regards, James. |
Re: Bricked NanoVNA-H
I'll have to check out what that VNA-QT is now Richard as I'm not familiar with that.
The only procedure that I did was as described and it worked for me after nearly launching the NanoVNA through the window Hi Hi. The NanoVNA that I have is a very old first edition I would say unit bought about three years ago so really needed upgrading. Hope you're getting there with it though. Regards, James. |
Re: Bricked NanoVNA-H
Here is an update at this point...
PLEASE! read the complete thing before responding! device : NanoVNA-H Screen: 2.8inch hardware version 3.4 Serial : 20051698 Problem: Unit powers up with white screen Red LED: Flash 1/s approx Blue LED : Flashing 1/s approx DFU Mode: was able to get unit in DFU mode by shorting BOOTO and VDD holes on pcb, note there was no jumpers. Win10 while in DFU Mode: Commes up as STM32 Bootloader. Firmware procedure: Using DfuSeDemo was able to find the STM32 Bootloader device, load the firmware ( NanoVNA-H_20210130.bin ), upgraded to NanoVNA-H properly, and ran verify that camme back ok. Rebooted the NanoVNA-H unit is still unable to display anything but blank WHITE Screen Hooked up the device to a USB Port, try connecting to proper comm port (Com44), would not connect to VNA-QT Hooked up any NanoVNA to same USB port could connect to VNA-QT without any problems 73 Richard VE2DX |
Re: Bricked NanoVNA-H
After pressing the two points you should be presented with this next screen.
And no problem Richard, this was driving me crazy yesterday trying to connect, but untill the driver is installed to make the computer "see" the NanoVNA in DFU mode, then you simply can't proceed. Hope it helps. Another picture for you as it tells a thousand words. Regards, James. |
Re: Nano VNA: An Antenna Stethoscope ( pdf file latest edition de k3eu )
You can all thank AJ3DI Jim, my benefactor, for introducing me to this gadget called Nano NVA.
It forced me to take another look at many concepts: resistance, reactance, impedance, PHASE, and of course, how useful (or bewildering) a Smith Chart can be. Of course, at my PhilMont Mobile Radio club presentation (over an hour) it was recorded, and although Jim missed the first couple of (very essential) slides, the talk can be viewed by anyone. Each time I give this talk, I learn more about what the hurdles are. I find, as a teacher, we can "say the words and answer multiple choice exams without any REAL understanding". My goal was to slow down enough for folks to see "resonance" and "phase" like a kid swinging on a swing and grampy (our feed line) giving the essential push to keep the current (kid) swinging. A crude analogy, of course, for resonance in an antenna. So have fun watching the video if you choose to spend an hour that way. I usually prepare for many more slides than I actually show (rookie error). Feedback is apprediated: K3euibarry at gmial.com 73 Barry |
Re: Bricked NanoVNA-H
James, thanks for the input, as I stated below l was able to get the device in DFU mode after shortening the pins (not a jumper on this version)
found the device... was able to load it but as I stated below, the unit boots up after power-up reset to a blank white screen the unit cannot be reached via the VNA-QT application note please I have another unit that CAN be reached with VNA-QT |
Re: Bricked NanoVNA-H
Here is a list that I've made with the steps that I took to get the device to be seen by my compute Richard.
Hopefully others can expand on this if I've missed any steps out. Hope it helps. Connect your NanoVNA to the computer via USB. Put the NanoVNA into DFU mode (Short out the Boot0 and VDD) NanoVNA screeb should be white. Open up device manager on the computer. Look down the list of items and look for Universal serial Bus Devices. Hopefully you will see STM Device in bootloader mode. Right click the device. Select update driver. Select browse my computer for drivers. Select Let me pick from a list of available drivers on my computer. Make sure show list of compatible drivers is ticked. You should be able to see an option listed as STM Device in DFU mode. Select this and install this driver. The STM Device should then show up in the Universal serial bus controllers as STM Device in DFU mode under Universal serial bus controllers. Run NanoVNA-App software and use this software to upgrade the firmware. There are two cogs at the top of the NnanoVNA-App software to run the upgrade process. Running these will show another window with available firmware for your NanoVNA. I selected the first option of firmware to choose from and went with that. Regards, James. |
Re: Bricked NanoVNA-H
Just to add to this Richard, i could only see STM Device in bootloader in Universal serial bus devices within device manager before doing a right click and update driver which let me select the driver for STM DFU mode.
After this it disappears from Universal serial bus devices and should only then appear in Universal serial bus controllers. Hope this helps, if not post again as to where your up to with it. Regards, James. |
Re: Bricked NanoVNA-H
Hello Richard.
It seems like you're having similar problems to me yesterday. It was diving me mad too. The advice about reading the Absolute Beginners Guide to NanoVNA v1_5.pdf helped me out but it was a little bit convoluted. For me, i went into device manager and could see that the STM32 was listed in Universal serial bus "devices" yet the device wasn't showing in the Universal serial bus controller as it should. Even though my nanovna WAS in DFU mode as it was just a white screen. I then right clicked on the device in Universal serial bus devices and selected update driver. I then searched Browse my computer for drivers which gave the option to select Let me pick from a list of available drivers on my computer. Here i found the driver for STM Device in DFU Mode which i selected and installed. This then made available the STM device within the Universal serial bus controllers. After this i was able to update the software with the NanoVNA-App as I could now connect to the software to run the firmware update. Hopefully I've attached a screen shot of my driver upgrade and how it should eventually look after you update the driver. I hope this helps and not add to your frustrations as I was ready to literally put a brick through my VNA yesterday morning HiHi. Regards, James. |
to navigate to use esc to dismiss