CH340 not recognized on win 10

[vk5is]

Hi Team,
I have had the first my (tr)uSDX built for some months now (thanks Faraz) and having lots of fun on air. No difficulty loading the firmware then.
I have just built my second rig but when I try to load the firmware via USB, my win 10 system tells me the usb device is not recognized. I tried re-installing the ch341ser driver pointed too on Manuels site but still the same result. If I connect an arduino uno to my pc, it shows up as a CH340 serial port and works ok.
I guess I could load the firmware via the ISP connector.
best Ian VK5IS

[vk5is]

OK... just in case someone else has similar trouble...
I tried loading the firmware through ISP connection with usbasp and AVRDUDESS and it appeared to work according to the AVRDUDESS screen BUT the (tr)uSDX only displayed a different serial number.
I decided to reload the bootloader which was successful as it restored the original serial number
and now
when I connect the usb to my pc, the pc recognizes the (tr)uSDX as serial port and I can upload the firmware.
Oh boy... life wasn't meant tot be easy
BIG salute to Manuel and all of the others involved.
best Ian VK5IS

[DO1OKE]

Thanks for reporting back! I will try that too, since my device is not recognised by any of my computers either...

[DO1OKE]

Ok, so I have now tried on 6 different computers (Mac, Windows 10 and Linux) to connect the trusdx via USB, always without success, it is not recognized. So I reflashed the bootloader via ISP. But now I still can not upload the firmware, because the device is not recognized via USB. You can not flash the firmware via ISP, right?

[LILO]

You can

https://dl2man.de/wp-content/uploads/20 ... /beta.html

ISP check box at the bottom.

[DO1OKE]

You can

https://dl2man.de/wp-content/uploads/20 ... /beta.html

ISP check box at the bottom.

I didn't know that, thanks! Unfortunately, that didn't work either due to some mismatch after the final verification (after uploading). Then I tried to reinstall the bootloader and after a few tries I seem to have fried the chip (or at least somehow changed fuse settings in a way that the atmega is not accessible any longer)...

Code: Select all

avrdude: Device signature = 0xffffff (probably .xmega) (retrying)

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0xffffff (probably .xmega)
avrdude: Yikes!  Invalid device signature.
         Double check connections and try again, or use -F to override
         this check.


avrdude done.  Thank you.

[Ohwenzelph]

So…. If all else is lost maybe try -F