Greetings, I apologize if my question is redundant. But, I am a bit confused, and I wonder if you would clarify for me.?Are you saying the vna doesn't appear in device manager at all, or is it listed but has an error (a yellow ? Question Mark as an example).?By the way, I very much agree that the cable could be bad. In fact, the USB cable that came with my NanoVna when it was new was?defective. This actually caused an issue similar to what you are experiencing when I first attached the device to my PC. But, even?after obtaining a good cable (an extra USB A to C cable that came with A Samsung Cellphone as I recall) I think I still had to use?Zaidig to get the driver situation corrected.
toggle quoted message
Show quoted text
On Tuesday, January 24, 2023 at 12:29:16 AM EST, Al Waschka <awaschka@...> wrote:
QUOTE
-----Original Message-----
From:
[email protected] <
[email protected]> On Behalf Of Tim Dawson
Sent: Tuesday, January 24, 2023 12:03 AM
To:
[email protected]Subject: Re: [nanovna-users] New Problem (Bricked?) Re: Trouble Setting Up DFuSE Driver
The firmware does *NOT* contain the bootloader, so the ability to det to dfu mode should not be altered or impeded by what you flashed . . .
UNQUOTE
Thanks Tim, but the scenario I was proposing was not that the firmware contained the bootloader, but that the nboot1 bit controls where in memory the processor goes to find boot code or an address to boot from, depending on what is stored in the location and how the fw responds to the data.? As I read it if a fw load has a different value for nboot1 than the original code, the machine will not boot as intended.
Whether this is my problem or not is unknown, but it seems that the value that a fw load sets the nboot1 bit at could change boot operations.
