开云体育

Can anyone explain this problem? I'm afraid to proceed on my H4. I FAFO and
bricked my 2.8" H.

RJ K8CYK



Attachments:

- dfu.PNG <>

Not familiar with windoze tools but it seems that it is complaining that the
firmware is in the wrong format. Try the .dfu firmware file?

Anyway you can't brick these devices, even in the worst case scenario you can
always connect to it with a $3 ST Link clone and flash it.

On Mon, 3 Feb 2025 at 04:06, Richard Jamsek via groups.io
<K8cyk56@...> wrote:

Can anyone explain this problem? I'm afraid to proceed on my H4. I FAFO and
bricked my 2.8" H.

RJ K8CYK



Attachments:

- dfu.PNG <>

What software are you referring to?

Dave - W?LEV

On Mon, Feb 3, 2025 at 3:06?AM Richard Jamsek via groups.io <K8cyk56=
[email protected]> wrote:

Can anyone explain this problem? I'm afraid to proceed on my H4. I FAFO and
bricked my 2.8" H.

RJ K8CYK



Attachments:

- dfu.PNG <>

--

*Dave - W?LEV*


--
Dave - W?LEV

I am using STMicroelectronics: DfuSeDemo.exe
The Dfu file is DIsLord Version 1.2.27 see the image below. My NanoVNA H4
is: HW version 4.3_MS. I reloaded the Dfu file once again. I've tried
several different WH versions with the same results. Once the 2.8" went
south I refuse to proceed with the download because of the message in the
second image.

Thanks for your interest.

[image: DfuFile.PNG]
[image: dfu.PNG]

On Mon, Feb 3, 2025 at 11:51?AM W0LEV via groups.io <davearea51a=
[email protected]> wrote:

What software are you referring to?

Dave - W?LEV

On Mon, Feb 3, 2025 at 3:06?AM Richard Jamsek via groups.io <K8cyk56=
[email protected]> wrote:

Can anyone explain this problem? I'm afraid to proceed on my H4. I FAFO

and

bricked my 2.8" H.

RJ K8CYK



Attachments:

- dfu.PNG <

>

--

*Dave - W?LEV*


--
Dave - W?LEV

Richard, it is safe to continue and update with that message. I think it is a feature of the final DFuseDemo version.
It also appears on my Win10 computer, and I proceed and update and it works fine. I just tried it again now to verify.

Stan KC7XE

Stan,

I have the same unit as Richard, v4.3-MS. Is dfuse the best way to update
to 1.2.40 or is it better to use the .bin file? Also, I was under the
impression that there were two versions, one for Si5351 and a different one
for MS5351 but I don’t see separate ones on DiSLord’s GitHub. Somewhat
肠辞苍蹿耻蝉颈苍驳…

Thanks,

Tony AC9QY (also hesitant lol)

On Mon, Feb 3, 2025 at 6:21?PM Stan Dye via groups.io <standye=
[email protected]> wrote:

Richard, it is safe to continue and update with that message. I think it
is a feature of the final DFuseDemo version.
It also appears on my Win10 computer, and I proceed and update and it
works fine. I just tried it again now to verify.

Stan KC7XE

You use the DFU file with DfuseDemo
You use the bin file with STMCubeProgrammer (current downloadable version)
I think either version works with nanovna-app (but I don't remember for sure).

DfuseDemo and nanovna-app require the driver that shows up in Device Manager under "Universal Serial Bus Controllers" as "STM Device in DFU mode". This driver needs loaded into Win10 or Win11 if you haven't already done it, and is part of the DfuseDemo package.

STMCubeProgrammer requires the driver that shows up in Device Manager under "Universal Serial Bus Controllers" or "Universal Serial Bus Devices" as "STM BOOTLOADER". This one is the standard driver in Win10 and Win11.

If you do not already have the driver set up for nanovna-app and DfuseDemo, I recommend using STMCubeProgrammer, which you can download from the ST.com site - simply because you don't need to deal with windows driver issues.

Regarding the MS vs SI version: they both use the same firmware build. Just go into the Config - Expert Settings menu and select the SI or MS mode. [At one time DiSlord and others were making separate builds for the two, but the only difference was the initialization of the processor mode parameter.]

Thanks for the well-worded clarification Stan. I think I’ll go with
STMCubeProgrammer since I already have too many other custom drivers
installed for FPGA tools and dev boards.

Tony

On Tue, Feb 4, 2025 at 12:24?AM Stan Dye via groups.io <standye=
[email protected]> wrote:

You use the DFU file with DfuseDemo
You use the bin file with STMCubeProgrammer (current downloadable version)
I think either version works with nanovna-app (but I don't remember for
sure).

DfuseDemo and nanovna-app require the driver that shows up in Device
Manager under "Universal Serial Bus Controllers" as "STM Device in DFU
mode". This driver needs loaded into Win10 or Win11 if you haven't already
done it, and is part of the DfuseDemo package.

STMCubeProgrammer requires the driver that shows up in Device Manager
under "Universal Serial Bus Controllers" or "Universal Serial Bus Devices"
as "STM BOOTLOADER". This one is the standard driver in Win10 and Win11.

If you do not already have the driver set up for nanovna-app and
DfuseDemo, I recommend using STMCubeProgrammer, which you can download
from the ST.com site - simply because you don't need to deal with windows
driver issues.

Regarding the MS vs SI version: they both use the same firmware build.
Just go into the Config - Expert Settings menu and select the SI or MS
mode. [At one time DiSlord and others were making separate builds for the
two, but the only difference was the initialization of the processor mode
parameter.]