开云体育

What is the optimum USB connection speed when using NanoVNA-Saver please? -- Mike

Al, please read the content on my website regarding the use of the nanoVNA. I can only enter a link this way (not hidden): http://ha3hz.hu/en/home/top-nav/12-seged-berendezesek/15-nanovna if you

A bad value in nboot1 would cause the nano to try to boot from RAM rather than the system ROM - but that bit is in the "options" registers, which cannot be written to by a normal flash load sequence

Just go straight to the W2AEW stuff, it's all top-notch: Smith Charts (8 videos): https://www.youtube.com/playlist?list=PL4ZSD4omd_AzQ7T0Dt4zTBW8sHLQHjqMQ NanoVNAs (17 videos)

The bootloader runs first, before you get to any of that . . . (that's kind of the point of having a bootloader). If you flash to he wrong offset, yeah, it won't run, but you should be able to reflash

controlled by separate hardware, making the units "unbrickable". Since you are a retired engineer, like me, perhaps this quote from introduction of the bootloader app note (AN2606) for the STM32 ARM

Greetings, I apologize if my question is redundant. But, I am a bit confused, and I wonder if you would clarify for me.?Are you saying the vna doesn't appear in device manager at all, or is it listed

QUOTE

The firmware does *NOT* contain the bootloader, so the ability to det to dfu mode should not be altered or impeded by what you flashed . . .

The time from working with the original fw load and not identifying as a DFU unit was literally minutes, on the same cable, computer, software and drivers. The Version Page of the hardware with its

I would first try a new cable. Often issues like this are caused by an intermittent cable or connector. Really, even if that cable often works, and works for charging. If you are using a usb-hub

Thanks, but when I set it to DFU mode by holding down the jogwheel or by shorting the VCC to Boot lands, each at power up, it doesn’t show up in device manager at all. The computer, which detected

Greetings, It is important to understand that the NanoVna shows up two different ways depending whether it is in DFU mode, or normal operating mode. In normal mode, it grabs a Comm Port. In DFU mode,

A reset and everything is back to normal. I remove the battery, wait for a few minutes and plug the battery back in. The nanonovna-H wakes up from its sleep. 73.

I apparently misstated where I got the recommendation for fw from, and now I can't find the reference, but the fw I uploaded was nanoVNA_800_ch_20190920.dfu.

Hi, Gyula. I tried that with no change. Chris VK5SA

Apparently you can brick one of these, even with a recommended firmware upload. As previously noted, I was able to get DFuSe to recognize the unit and uploaded the 800MHz firmware, which the

Well, I followed the directions, but when my indications didn't agree I quit reading. I finally realized (from the "you can’t brick it" note that the designation of STM Bootloader was correct. I had

The driver should be here if you installed to the default directory: C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver

Thanks for trying to help, but I think I followed the directions in the link explicitly. Comments below marked <<<<<xxxxx>>>>>>