开云体育

I couldn't connect to the unit and somehow managed to wipe the processor.
I've tried resetting it to reconnect, but the only response I get is in
STM32Cube Programmer 'UR is set by HWrst' or something similar.

I tried shorting BOOT0 to VDD as noted, screen remains white, no connection.

Any suggestions would be appreciated!

Hello,
In the files section you will find a process to recover from "White Screen Recovery". Follow it PRECISELY STEP by STEP!.
If that does not work you could try, for the lack of a better term, a factory reset.
Push the jog switch down to the left and hold while turning the unit on. Then try the screen recovery.
Clyde KC7BJE

Thanks. Clyde - but my unit is not -H; I did try the BOOTP - VDD reset, no
good, and all the other sequences mentioned.

Nothing lets me connect to the unit via USB-C.

I do appreciate the response. ?

On Fri, Mar 14, 2025, 13:34 Clyde Lambert via groups.io <clyde.lambert=
[email protected]> wrote:

Hello,
In the files section you will find a process to recover from "White Screen
Recovery". Follow it PRECISELY STEP by STEP!.
If that does not work you could try, for the lack of a better term, a
factory reset.
Push the jog switch down to the left and hold while turning the unit on.
Then try the screen recovery.
Clyde KC7BJE

You wrote in the title that the unit is: NanoVNA-H v3.5 ?
If you have somehow managed to wipe the bootloader (highly unlikely) your
only
choice left is to connect to the micro directly, using a programer like
st-link (2-3 bucks and Ali, Ebay etc).

On Sat, 15 Mar 2025 at 15:38, Taracait via groups.io <tcdrennen=
[email protected]> wrote:

Thanks. Clyde - but my unit is not -H; I did try the BOOTP - VDD reset, no
good, and all the other sequences mentioned.

Nothing lets me connect to the unit via USB-C.

I do appreciate the response. ?

On Fri, Mar 14, 2025, 13:34 Clyde Lambert via groups.io <clyde.lambert=
[email protected]> wrote:

Hello,
In the files section you will find a process to recover from "White

Screen

Recovery". Follow it PRECISELY STEP by STEP!.
If that does not work you could try, for the lack of a better term, a
factory reset.
Push the jog switch down to the left and hold while turning the unit on.
Then try the screen recovery.
Clyde KC7BJE

Maybe you have a problem with the battery.
I would open the NanoVNA and disconnect the battery.
Check if it is working. Use a meter to check if there is voltage coming out of it and what it is.
Also check the battery socket.

ST-LINK info:
/g/nanovna-users/topic/nanovna_bricked/34149616

On Sat, Mar 15, 2025, 10:40 AM SP1RAC via groups.io <sp1rac@...>
wrote:

Maybe you have a problem with the battery.
I would open the NanoVNA and disconnect the battery.
Check if it is working. Use a meter to check if there is voltage coming
out of it and what it is.
Also check the battery socket.

Battery is fine, 3.7VDC; checked at the unit PCB.

And the screen is lighting up (white), so power isw not the problem

Sorry, it is indeed -H; but not '4'

I'll try with differeny connection - thanks!

maybe the case is pressing on the touch screen? ... or the screen cable is not well fitted

did you try to connect it to pc (example nanovna app)??

dg9bfc sigi

Am 16.03.2025 um 23:31 schrieb Taracait via groups.io:

Success!

1. Shorted BOOTP and VDD pins
2. Connected USB-C to PC (MacBook Pro 2016)
3. Started STM32CubeProgrammer
4. Loaded latest NanoVNA .HEX file
5. Started Download
6. Success! NanoVNA working as expected.

Thanks, for all the help; Dfu appears to be obsolete, STM32Cube works, and
I don't need to run it on Win10 via Parallels ?

On Sun, Mar 16, 2025, 17:37 Siegfried Jackstien via groups.io
<siegfried.jackstien@...> wrote:

maybe the case is pressing on the touch screen? ... or the screen cable
is not well fitted

did you try to connect it to pc (example nanovna app)??

dg9bfc sigi

Am 16.03.2025 um 23:31 schrieb Taracait via groups.io:

Battery is fine, 3.7VDC; checked at the unit PCB.

And the screen is lighting up (white), so power isw not the problem