开云体育

Mine is not seen by Win 10 device manager. ( tried 2 cables and machines) I heard there is a way to get it out of DFU mode internally?
Mine did not die updating firmware, but it was hooked up to PC using "saver" program I think.
I installed the dfu se demo and file manager, but it's useless since PC can't see the device

On Wed, Feb 26, 2025 at 10:52 AM, Len Ward wrote:

Mine is not seen by Win 10 device manager. ( tried 2 cables and machines) I
heard there is a way to get it out of DFU mode internally?
Mine did not die updating firmware, but it was hooked up to PC using "saver"
program I think.
I installed the dfu se demo and file manager, but it's useless since PC can't
see the device

NanoVNA Saver does not touch your firmware so it could not have damaged your device. Your device cannot be "bricked" because the DFU loader is built into ROM on the microprocessor.

Does your device boot at all or is it just a black or white screen? Can you talk to it using the USB COM port and a serial program like Putty?

To get the H4 device into DFU mode you can do one of the following:
- Select DFU from the menu
- Push the jog switch down with the power off and then power on
- Open the case and short the VDD and Boot0 pins, then power on and remove the short

When you do one of the above and are connected to a Windows PC you should hear a "bing" in Windows. If you go into Device Manager you should see that your device is recognized. One of two drivers will be installed. One works with DFUse and nanoVNA app for firmware loading and the other works with STM Cube. You can search this group and the group Wiki for the many messages on how to install drivers and use these programs.

Also suggest you read the Absolute Beginners Guide to the NanoVNA in the Files section of this group.

Roger

Roger

Also ensure that the cable that you are using is a data cable and not just
one capable of only supplying power. Many cables can only supply power
unless specifically stated, so I use a cable tester to make sure that it is
capable of data.

The one supplied with your device should be a data cable as long as you got
it from a reputable seller.

<>
Virus-free.www.avast.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Feb 26, 2025 at 7:41?PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Wed, Feb 26, 2025 at 10:52 AM, Len Ward wrote:

Mine is not seen by Win 10 device manager. ( tried 2 cables and

machines) I

heard there is a way to get it out of DFU mode internally?
Mine did not die updating firmware, but it was hooked up to PC using

"saver"

program I think.
I installed the dfu se demo and file manager, but it's useless since PC

can't

see the device

NanoVNA Saver does not touch your firmware so it could not have damaged
your device. Your device cannot be "bricked" because the DFU loader is
built into ROM on the microprocessor.

Does your device boot at all or is it just a black or white screen? Can
you talk to it using the USB COM port and a serial program like Putty?

To get the H4 device into DFU mode you can do one of the following:
- Select DFU from the menu
- Push the jog switch down with the power off and then power on
- Open the case and short the VDD and Boot0 pins, then power on and remove
the short

When you do one of the above and are connected to a Windows PC you should
hear a "bing" in Windows. If you go into Device Manager you should see
that your device is recognized. One of two drivers will be installed. One
works with DFUse and nanoVNA app for firmware loading and the other works
with STM Cube. You can search this group and the group Wiki for the many
messages on how to install drivers and use these programs.

Also suggest you read the Absolute Beginners Guide to the NanoVNA in the
Files section of this group.

Roger

Roger