|
problem started when i attempted to upgrade, screen went black, foolishly did not save the old version.. now i can read the vna with stm32, it even appears to write the new firmware but still a black screen, how do i know if i am using the correct firmware for my vna? what are the correct steps to read and program with stm32? i must be missing something, any help would be appreciated.
thanks for any advice
Bob
VA4BG
|
Telling us what model Nano-VNA you have would be a good starting point.
toggle quoted message
Show quoted text
On March 1, 2025 11:12:20 PM EST, "VA4BG via groups.io" <bobgau@...> wrote: problem started when i attempted to upgrade, screen went black, foolishly did not save the old version.. now i can read the vna with stm32, it even appears to write the new firmware but still a black screen, how do i know if i am using the correct firmware for my vna? what are the correct steps to read and program with stm32? i must be missing something, any help would be appreciated.
thanks for any advice
Bob
VA4BG
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
shoot in the dark .. a nano vna H ??
dg9bfc sigi
Am 02.03.2025 um 16:21 schrieb Tim Dawson:
toggle quoted message
Show quoted text
Telling us what model Nano-VNA you have would be a good starting point.
On March 1, 2025 11:12:20 PM EST, "VA4BG via groups.io" <bobgau@...> wrote:
problem started when i attempted to upgrade, screen went black, foolishly did not save the old version.. now i can read the vna with stm32, it even appears to write the new firmware but still a black screen, how do i know if i am using the correct firmware for my vna? what are the correct steps to read and program with stm32? i must be missing something, any help would be appreciated.
thanks for any advice
Bob
VA4BG
|
I should have included in main body instead of just a lower case h in subject line, my apologies for poor description. Pic attached from board, thank you for the
toggle quoted message
Show quoted text
On Mar 2, 2025, at 9:23?AM, Siegfried Jackstien via groups.io <siegfried.jackstien@...> wrote:
?shoot in the dark .. a nano vna H ??
dg9bfc sigi
Am 02.03.2025 um 16:21 schrieb Tim Dawson:
Telling us what model Nano-VNA you have would be a good starting point.
On March 1, 2025 11:12:20 PM EST, "VA4BG via groups.io" <bobgau@...> wrote:
problem started when i attempted to upgrade, screen went black, foolishly did not save the old version.. now i can read the vna with stm32, it even appears to write the new firmware but still a black screen, how do i know if i am using the correct firmware for my vna? what are the correct steps to read and program with stm32? i must be missing something, any help would be appreciated.
thanks for any advice
Bob
VA4BG
|
reply. Much appreciated
toggle quoted message
Show quoted text
On Mar 2, 2025, at 9:59?AM, VA4BG via groups.io <bobgau@...> wrote:
?I should have included in main body instead of just a lower case h in subject line, my apologies for poor description. Pic attached from board, thank you for the
On Mar 2, 2025, at 9:23?AM, Siegfried Jackstien via groups.io <siegfried.jackstien@...> wrote:
?shoot in the dark .. a nano vna H ??
dg9bfc sigi
Am 02.03.2025 um 16:21 schrieb Tim Dawson: Telling us what model Nano-VNA you have would be a good starting point.
On March 1, 2025 11:12:20 PM EST, "VA4BG via groups.io" <bobgau@...> wrote:
problem started when i attempted to upgrade, screen went black, foolishly did not save the old version.. now i can read the vna with stm32, it even appears to write the new firmware but still a black screen, how do i know if i am using the correct firmware for my vna? what are the correct steps to read and program with stm32? i must be missing something, any help would be appreciated.
thanks for any advice
Bob
VA4BG
<image0.jpeg>
|
What firmware are you trying to use?
If you are using Hugen79's firmware then pay close attention to the image you downloaded. I ran into a black screen after upgrade as well caused by me mistakingly flashing my NanoVNA-H4 with the -H firmware. The H and H4 are different hardware and their firmware is incompatible. Furthermore check the back of your unit and make sure you've selected the right hardware variant of the H (MS, SI, ZK) not doing so will also result in a failure to boot.
Luckily recovering is easy, just boot into DFU mode and flash the right firmware for your H/H4. I hope that helps.
|
Thanks for the reply, nowhere on the board do i see any reference to ms,si or zk, where should i be looking? Also have installed dfuse demo but running cannot get the correct driver. Looked in the files section and on stm site but cannot find a driver for win 11.
toggle quoted message
Show quoted text
On Mar 2, 2025, at 3:06?PM, juancb via groups.io <juancb@...> wrote:
?What firmware are you trying to use?
If you are using Hugen79's firmware then pay close attention to the image you downloaded. I ran into a black screen after upgrade as well caused by me mistakingly flashing my NanoVNA-H4 with the -H firmware. The H and H4 are different hardware and their firmware is incompatible. Furthermore check the back of your unit and make sure you've selected the right hardware variant of the H (MS, SI, ZK) not doing so will also result in a failure to boot.
Luckily recovering is easy, just boot into DFU mode and flash the right firmware for your H/H4. I hope that helps.
|
Device manager just tells me best driver is already installed but all i get is stm bootloader showing up in USB devices
toggle quoted message
Show quoted text
On Mar 2, 2025, at 4:27?PM, Bob Gauthier <bobgau@...> wrote:
?Thanks for the reply, nowhere on the board do i see any reference to ms,si or zk, where should i be looking? Also have installed dfuse demo but running cannot get the correct driver. Looked in the files section and on stm site but cannot find a driver for win 11.
On Mar 2, 2025, at 3:06?PM, juancb via groups.io <juancb@...> wrote:
?What firmware are you trying to use?
If you are using Hugen79's firmware then pay close attention to the image you downloaded. I ran into a black screen after upgrade as well caused by me mistakingly flashing my NanoVNA-H4 with the -H firmware. The H and H4 are different hardware and their firmware is incompatible. Furthermore check the back of your unit and make sure you've selected the right hardware variant of the H (MS, SI, ZK) not doing so will also result in a failure to boot.
Luckily recovering is easy, just boot into DFU mode and flash the right firmware for your H/H4. I hope that helps.
|
From your photo it appears you have a NanoVNA-H4, (the 4 is for the 4" screen) hardware version 4.3, or perhaps a good clone. Did it come in a case, or was it just the card and screen? Most 'official' ones of these sold were in a case, and the back of the case had a sticker indicating the hardware version number, which was 4.3_MS for the MS version, and just 4.3 for the SI version. The ZK version is newest, and has different hardware - I think rev 4.4, so you likely don't have it. If you have a magnifier, you can look at the 5351 chip (it is the very small one with 5 tiny legs on each side) and see if its part number starts with MS or SI. If you use the wrong firmware file, you will likely get a black screen. Make sure that if your version of STM32CubeProgrammer ends in .16, you first do a "Full Chip Erase" function before upgrading the firmware (versions before and after .16 automatically include the erase). Regarding the firmware, you need the one with H4 in its name, from Hugen's website as previously linked, or from DiSlord's NanoVNA-D github. While it may be nicest to get the correct SI or MS version, either one will work, since they are the same except for the SI/MS initialization, but that setting is also in the Config->Expert Settings menu, and you can choose the correct one after firmware installation. The driver in Windows 11 that Windows reports as the best one for your device will work fine with the STM32CubeProgrammer, but not DfuseDemo or nanovna-app. Some time ago I did a writeup about the firmware update and drivers that may be of help to you, see the files at this link: /g/nanovna-users/files/Miscellaneous/DFU-mode%20Driver%20for%20Win10Win11
|
Thank you, will get back to this later this evening, it did come in a case, if the version is not on there i will check the chip. Will let you know how it goes
toggle quoted message
Show quoted text
On Mar 2, 2025, at 4:59?PM, Stan Dye via groups.io <standye@...> wrote:
?From your photo it appears you have a NanoVNA-H4, (the 4 is for the 4" screen) hardware version 4.3, or perhaps a good clone. Did it come in a case, or was it just the card and screen? Most 'official' ones of these sold were in a case, and the back of the case had a sticker indicating the hardware version number, which was 4.3_MS for the MS version, and just 4.3 for the SI version. The ZK version is newest, and has different hardware - I think rev 4.4, so you likely don't have it. If you have a magnifier, you can look at the 5351 chip (it is the very small one with 5 tiny legs on each side) and see if its part number starts with MS or SI.
If you use the wrong firmware file, you will likely get a black screen. Make sure that if your version of STM32CubeProgrammer ends in .16, you first do a "Full Chip Erase" function before upgrading the firmware (versions before and after .16 automatically include the erase).
Regarding the firmware, you need the one with H4 in its name, from Hugen's website as previously linked, or from DiSlord's NanoVNA-D github. While it may be nicest to get the correct SI or MS version, either one will work, since they are the same except for the SI/MS initialization, but that setting is also in the Config->Expert Settings menu, and you can choose the correct one after firmware installation.
The driver in Windows 11 that Windows reports as the best one for your device will work fine with the STM32CubeProgrammer, but not DfuseDemo or nanovna-app. Some time ago I did a writeup about the firmware update and drivers that may be of help to you, see the files at this link:
/g/nanovna-users/files/Miscellaneous/DFU-mode%20Driver%20for%20Win10Win11
|
The version is typically part of the model number on the sticker on the case. The PCB is the same for the MS and SI - only the chip vendor changes.
toggle quoted message
Show quoted text
On March 2, 2025 5:27:50 PM EST, "VA4BG via groups.io" <bobgau@...> wrote: Thanks for the reply, nowhere on the board do i see any reference to ms,si or zk, where should i be looking? Also have installed dfuse demo but running cannot get the correct driver. Looked in the files section and on stm site but cannot find a driver for win 11.
On Mar 2, 2025, at 3:06?PM, juancb via groups.io <juancb@...> wrote:
?What firmware are you trying to use?
If you are using Hugen79's firmware then pay close attention to the image you downloaded. I ran into a black screen after upgrade as well caused by me mistakingly flashing my NanoVNA-H4 with the -H firmware. The H and H4 are different hardware and their firmware is incompatible. Furthermore check the back of your unit and make sure you've selected the right hardware variant of the H (MS, SI, ZK) not doing so will also result in a failure to boot.
Luckily recovering is easy, just boot into DFU mode and flash the right firmware for your H/H4. I hope that helps.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
So.. i got the driver installed, showed up as “stm device in dfu mode”, stm cube programmer did not recognize the bna but the dfuse demo program did, the “upload action” part of the programer seemed to work but took only a second or two, the “upgrade or verify” section did an erase and upgrade and seemed to finish ok, screen shot attached, still no joy. Just a black screen..
toggle quoted message
Show quoted text
On Mar 2, 2025, at 5:35?PM, Tim Dawson <tadawson@...> wrote:
?The version is typically part of the model number on the sticker on the case. The PCB is the same for the MS and SI - only the chip vendor changes.
On March 2, 2025 5:27:50 PM EST, "VA4BG via groups.io" <bobgau@...> wrote:
Thanks for the reply, nowhere on the board do i see any reference to ms,si or zk, where should i be looking? Also have installed dfuse demo but running cannot get the correct driver. Looked in the files section and on stm site but cannot find a driver for win 11.
On Mar 2, 2025, at 3:06?PM, juancb via groups.io <juancb@...> wrote: ?What firmware are you trying to use?
If you are using Hugen79's firmware then pay close attention to the image you downloaded. I ran into a black screen after upgrade as well caused by me mistakingly flashing my NanoVNA-H4 with the -H firmware. The H and H4 are different hardware and their firmware is incompatible. Furthermore check the back of your unit and make sure you've selected the right hardware variant of the H (MS, SI, ZK) not doing so will also result in a failure to boot.
Luckily recovering is easy, just boot into DFU mode and flash the right firmware for your H/H4. I hope that helps.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Please use the firmware for -H4.
|
Thankyou for your help and especially your patience.. I didn’t realize i needed the H4, but same result.
toggle quoted message
Show quoted text
On Mar 2, 2025, at 7:09?PM, Hugen via groups.io <hugen@...> wrote:
?Please use the firmware for -H4.
|
You must use only the upgrade/verify portion of dfusedemo. If you first used the upload function, you overwrote your firmware file with the content of the nanovna, trashing it before you used it for the upgrade/verify function. [The dfusedemo program uses the "upload" term to refer to fetching data from the nanovna].
So it is worth trying again with a fresh copy the H4 file newly downloaded.
|
Thank you, Thank you… that did the trick. Your help and patience is much appreciated, I learned something today, now if i can just remember it. This technologically challenged old F er really appreciates you taking the time to help. Thanks again.
Cheers
toggle quoted message
Show quoted text
On Mar 2, 2025, at 8:07?PM, Stan Dye via groups.io <standye@...> wrote:
?You must use only the upgrade/verify portion of dfusedemo. If you first used the upload function, you overwrote your firmware file with the content of the nanovna, trashing it before you used it for the upgrade/verify function. [The dfusedemo program uses the "upload" term to refer to fetching data from the nanovna].
So it is worth trying again with a fresh copy the H4 file newly downloaded.
|
VA4BG
