开云体育

NanoVNA not connecting to DfuSeDem V3.06

stefan baartman All Messages By This Member #19228 I have a bricked nanovna with old firmware that I am trying to update. The brick seems to be that it picked up an electrostatic charge on CH0 and now the impedance trace is all over the place. Anyway. I am trying to update it. My PC recognizes the device on Com6 and I use the nanosaver app with it. The problem arises when I try to get DfuSeDem V3.06 (the latest version I could find from st.com. The app does not register my device, no matter if I short the boot contacts or not. When I short the boot contacts (I mounted a microswitch to these contacts) the white screen comes up. Any help in getting this unit updated would be appreciated. The firmware presently on it is old, and does not have facility for either Update/Dfu or Config.
Larry Rothman All Messages By This Member #19229 Stefan, when in dfu mode, the computer will not recognize the Nanovna as a com port. Connect the unit to your PC and place it into dfu mode. Now, check the Window's device manager under USB devices. You should see it there showing up in dfu mode.? If you see it, run the DeFuSe utilitiy and you should see it in the upper left corner as a dfu device. Note, the utility uses backwards terms for flashing and backup of the flash. You might want to use my modified DeFuSe exe file in the forum's file section. I changed the terms for upload and backup on the GUI.?? Btw, you can't brick a NanoVNA. As for the wild traces, make sure to press the RESET menu button before calibration.? ... Larry On Sat, 5 Dec 2020 at 5:46 PM, stefan baartman<seb21051@...> wrote: I have a bricked nanovna with old firmware that I am trying to update. The brick seems to be that it picked up an electrostatic charge on CH0 and now the impedance trace is all over the place. Anyway. I am trying to update it. My PC recognizes the device on Com6 and I use the nanosaver app with it. The problem arises when I try to get DfuSeDem V3.06 (the latest version I could find from st.com. The app does not register my device, no matter if I short the boot contacts or not. When I short the boot contacts (I mounted a microswitch to these contacts) the white screen comes up. Any help in getting this unit updated would be appreciated. The firmware presently on it is old, and does not have facility for either Update/Dfu or Config.
stefan baartman All Messages By This Member #19230 Thanks for the help, Larry. I was able to get the correct DFU driver to load after I deleted the original DFU Boot entry under the USB section in the Device Manager. As regards the bricking, I still get these symptoms after getting the update, resetting, then calibrating: toggle quoted message Show quoted text On Sat, Dec 5, 2020 at 10:51 PM Larry Rothman <nlroth@...> wrote: Stefan, when in dfu mode, the computer will not recognize the Nanovna as a com port. Connect the unit to your PC and place it into dfu mode. Now, check the Window's device manager under USB devices. You should see it there showing up in dfu mode. If you see it, run the DeFuSe utilitiy and you should see it in the upper left corner as a dfu device. Note, the utility uses backwards terms for flashing and backup of the flash. You might want to use my modified DeFuSe exe file in the forum's file section. I changed the terms for upload and backup on the GUI. Btw, you can't brick a NanoVNA. As for the wild traces, make sure to press the RESET menu button before calibration. ... Larry On Sat, 5 Dec 2020 at 5:46 PM, stefan baartman<seb21051@...> wrote: I have a bricked nanovna with old firmware that I am trying to update. The brick seems to be that it picked up an electrostatic charge on CH0 and now the impedance trace is all over the place. Anyway. I am trying to update it. My PC recognizes the device on Com6 and I use the nanosaver app with it. The problem arises when I try to get DfuSeDem V3.06 (the latest version I could find from st.com. The app does not register my device, no matter if I short the boot contacts or not. When I short the boot contacts (I mounted a microswitch to these contacts) the white screen comes up. Any help in getting this unit updated would be appreciated. The firmware presently on it is old, and does not have facility for either Update/Dfu or Config. NVNA doing strange things..docx NVNA doing strange things..docx
stefan baartman All Messages By This Member #19231 In the screenshots shown above, the top one is when it was OK, the bottom is what it looks like now.
Mark Besch All Messages By This Member #19243 FWIW I had the same problem. I moved back to the previous version and then it worked. I'm also using Win10. mark toggle quoted message Show quoted text On Sat, Dec 5, 2020 at 5:46 PM stefan baartman <seb21051@...> wrote: I have a bricked nanovna with old firmware that I am trying to update. The brick seems to be that it picked up an electrostatic charge on CH0 and now the impedance trace is all over the place. Anyway. I am trying to update it. My PC recognizes the device on Com6 and I use the nanosaver app with it. The problem arises when I try to get DfuSeDem V3.06 (the latest version I could find from st.com. The app does not register my device, no matter if I short the boot contacts or not. When I short the boot contacts (I mounted a microswitch to these contacts) the white screen comes up. Any help in getting this unit updated would be appreciated. The firmware presently on it is old, and does not have facility for either Update/Dfu or Config. -- "I can not bring myself to believe that if knowledge presents danger, the solution is ignorance" - Isaac Asimov
stefan baartman All Messages By This Member #19245 Hi Mark, What were the circumstances that seemed to trigger that particular response in your device? toggle quoted message Show quoted text On Sun, Dec 6, 2020 at 9:20 PM Mark Besch <beschm@...> wrote: FWIW I had the same problem. I moved back to the previous version and then it worked. I'm also using Win10. mark On Sat, Dec 5, 2020 at 5:46 PM stefan baartman <seb21051@...> wrote: I have a bricked nanovna with old firmware that I am trying to update. The brick seems to be that it picked up an electrostatic charge on CH0 and now the impedance trace is all over the place. Anyway. I am trying to update it. My PC recognizes the device on Com6 and I use the nanosaver app with it. The problem arises when I try to get DfuSeDem V3.06 (the latest version I could find from st.com. The app does not register my device, no matter if I short the boot contacts or not. When I short the boot contacts (I mounted a microswitch to these contacts) the white screen comes up. Any help in getting this unit updated would be appreciated. The firmware presently on it is old, and does not have facility for either Update/Dfu or Config. -- "I can not bring myself to believe that if knowledge presents danger, the solution is ignorance" - Isaac Asimov
Mark Besch All Messages By This Member #19250 Stefan, The software just could not find my device. Although I could terminal into the device, the software could not see it. Downloading, installing, and using the previous version resolved that issue. I installed the software, rebooted (it is Windoze) and Windows found it and installed the device driver. All things which had not happened previously regardless of how many times I installed, rebooted, and chanted. Once the software found my device it was just a simple pointing it at the new firmware and loading the firmware. I believe I ended up using en.stsw-stm32080. That is what I'm seeing in the directory but I'll boot into Windows 10 again tomorrow and see what version it was exactly. I normally run Linux, CENTOS 7.8. I boot into Windows 10 to update the firmware of my nanovna or tinysa. Does this help? mark NS1V
stefan baartman All Messages By This Member #19251 Hi Mark, I understand better now. I deleted the device driver that showed up in the USB Devices section when I booted into DFU mode. Once that was gone and the new one loaded, the device showed up in DfuDemo and I could update without problems. Thanks! toggle quoted message Show quoted text On Mon, Dec 7, 2020 at 12:16 AM Mark Besch <beschm@...> wrote: Stefan, The software just could not find my device. Although I could terminal into the device, the software could not see it. Downloading, installing, and using the previous version resolved that issue. I installed the software, rebooted (it is Windoze) and Windows found it and installed the device driver. All things which had not happened previously regardless of how many times I installed, rebooted, and chanted. Once the software found my device it was just a simple pointing it at the new firmware and loading the firmware. I believe I ended up using en.stsw-stm32080. That is what I'm seeing in the directory but I'll boot into Windows 10 again tomorrow and see what version it was exactly. I normally run Linux, CENTOS 7.8. I boot into Windows 10 to update the firmware of my nanovna or tinysa. Does this help? mark NS1V

Previous Topic Next Topic