USB driver problem

[Stylmast]

Hi guys,
I'm having a problem with the USB drivers - device manager is reporting Device descriptor request failed. Properties shows a Code 43.

I'm on a W10 machine.

Any idea's.

[angusgr]

Hi Stylmast,

On an EtherTen this would usually indicate a hardware problem with the Atmega16u2 that performs USB/Serial conversion. Or possibly bad firmware flashed to that microcontroller.

Does the EtherTen work on any computers? Is it brand new?


Angus

[Stylmast]

I have 2 units, 1 is new & the second 1 is a little older, also the same with a new mega

[angusgr]

So none of these three units are working with your computer? Do they work with other computers?

I'm afraid it sounds like it might be a problem with the computer's USB host hardware or drivers.

[Stylmast]

I think it's driver, my W7 machine is now doing the same thing after an update. I'm unable to use restore point to back date the driver install. Do you have the driver file I can use?

Scott

[Stylmast]

Update - I have found a couple of older boards Ver 1.1 & Ver 2 both of these boards show on the com port section of the device manager on my W7 machine which is also my w10 machine with a different hard drive.

The etherten is a ver 3

The mega installed its divers correctly on the W7 machine.

Scott

[Stylmast]

Update 2 - I switched back to my W10 drive and got the same results as above only the V3 board showed an error. The rest used the same W10 driver. 10.0.10586.306

Scott

[angusgr]

Hi Scot,

All 3 of these boards should be running identical USB/serial interface firmware, so from that point of view they should all appear as the same device.

Is it possible there's another factor involved - choice of USB cable, choice of USB port, position of onboard power selection jumper, etc.?


Angus